1 Changes in version 0.4.1.2-alpha - 2019-06-05
2 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
3 previous alpha, and some much older. It also contains minor testing
4 improvements, and an improvement to the security of our authenticated
7 o Major bugfixes (bridges):
8 - Consider our directory information to have changed when our list
9 of bridges changes. Previously, Tor would not re-compute the
10 status of its directory information when bridges changed, and
11 therefore would not realize that it was no longer able to build
12 circuits. Fixes part of bug 29875.
13 - Do not count previously configured working bridges towards our
14 total of working bridges. Previously, when Tor's list of bridges
15 changed, it would think that the old bridges were still usable,
16 and delay fetching router descriptors for the new ones. Fixes part
17 of bug 29875; bugfix on 0.3.0.1-alpha.
19 o Major bugfixes (Flow Control, SENDME):
20 - The decrement of the stream-level package window was done in a
21 log_debug() statement meaning that if the debug logs were not
22 enabled, the decrement would never happen and thus the window
23 would be out of sync with the other end point. Fixes bug 30628;
24 bugfix on 0.4.1.1-alpha.
26 o Major bugfixes (Onion service reachability):
27 - Properly clean up the introduction point map and associated state
28 when circuits change purpose from onion service circuits to
29 pathbias, measurement, or other circuit types. This should fix
30 some instances of introduction point failure. Fixes bug 29034;
31 bugfix on 0.3.2.1-alpha.
33 o Minor features (authenticated SENDME):
34 - Ensure that there is enough randomness on every circuit to prevent
35 an attacker from successfully predicting what SENDME cells they
36 will need to send: at a random interval, if we have not send
37 randomness already, leave some extra space at the end of a cell
38 that we can fill with random bytes. Closes ticket 26846.
40 o Minor features (continuous integration):
41 - When running coverage builds on Travis, we now set
42 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
45 o Minor features (maintenance):
46 - Add a new "make autostyle" target that developers can use to apply
47 all automatic Tor style and consistency conversions to the
48 codebase. Closes ticket 30539.
50 o Minor features (testing):
51 - The circuitpadding tests now use a reproducible RNG implementation,
52 so that if a test fails, we can learn why. Part of ticket 28878.
53 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
54 to set the RNG seed for tests that use a reproducible RNG. Part of
56 - When running tests in coverage mode, take additional care to make
57 our coverage deterministic, so that we can accurately track
58 changes in code coverage. Closes ticket 30519.
60 o Minor bugfixes (configuration, proxies):
61 - Fix a bug that prevented us from supporting SOCKS5 proxies that
62 want authentication along with configured (but unused!)
63 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
65 o Minor bugfixes (controller):
66 - POSTDESCRIPTOR requests should work again. Previously, they were
67 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
69 - Repair the HSFETCH command so that it works again. Previously, it
70 expected a body when it shouldn't have. Fixes bug 30646; bugfix
73 o Minor bugfixes (developer tooling):
74 - Fix pre-push hook to refrain from rejecting fixup and squash
75 commits when pushing to non-upstream git remote. Fixes bug 30286;
76 bugfix on 0.4.0.1-alpha.
78 o Minor bugfixes (directory authority):
79 - Move the "bandwidth-file-headers" line in directory authority
80 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
83 o Minor bugfixes (NetBSD):
84 - Fix usage of minherit() on NetBSD and other platforms that define
85 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
86 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
88 o Minor bugfixes (out-of-memory handler):
89 - When purging the DNS cache because of an out-of-memory condition,
90 try purging just the older entries at first. Previously, we would
91 purge the whole thing. Fixes bug 29617; bugfix on 0.3.5.1-alpha.
93 o Minor bugfixes (portability):
94 - Avoid crashing in our tor_vasprintf() implementation on systems
95 that define neither vasprintf() nor _vscprintf(). (This bug has
96 been here long enough that we question whether people are running
97 Tor on such systems, but we're applying the fix out of caution.)
98 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
101 o Minor bugfixes (shutdown, libevent, memory safety):
102 - Avoid use-after-free bugs when shutting down, by making sure that
103 we shut down libevent only after shutting down all of its users.
104 We believe these are harmless in practice, since they only occur
105 on the shutdown path, and do not involve any attacker-controlled
106 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
108 o Minor bugfixes (static analysis):
109 - Fix several spurious Coverity warnings about the unit tests, to
110 lower our chances of missing any real warnings in the future.
111 Fixes bug 30150; bugfix on 0.3.5.1-alpha and various other
115 - Specify torrc paths (with empty files) when launching tor in
116 integration tests; refrain from reading user and system torrcs.
117 Resolves issue 29702.
120 Changes in version 0.4.1.1-alpha - 2019-05-22
121 This is the first alpha in the 0.4.1.x series. It introduces
122 lightweight circuit padding to make some onion-service circuits harder
123 to distinguish, includes a new "authenticated SENDME" feature to make
124 certain denial-of-service attacks more difficult, and improves
125 performance in several areas.
127 o Major features (circuit padding):
128 - Onion service clients now add padding cells at the start of their
129 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
130 look more like general purpose Exit traffic. The overhead for this
131 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
132 extra upstream cell and 10 downstream cells for INTRODUCE
133 circuits. This feature is only enabled when also supported by the
134 circuit's middle node. (Clients may specify fixed middle nodes
135 with the MiddleNodes option, and may force-disable this feature
136 with the CircuitPadding torrc.) Closes ticket 28634.
138 o Major features (code organization):
139 - Tor now includes a generic publish-subscribe message-passing
140 subsystem that we can use to organize intermodule dependencies. We
141 hope to use this to reduce dependencies between modules that don't
142 need to be related, and to generally simplify our codebase. Closes
145 o Major features (controller protocol):
146 - Controller commands are now parsed using a generalized parsing
147 subsystem. Previously, each controller command was responsible for
148 parsing its own input, which led to strange inconsistencies.
151 o Major features (flow control):
152 - Implement authenticated SENDMEs as detailed in proposal 289. A
153 SENDME cell now includes the digest of the traffic that it
154 acknowledges, so that once an end point receives the SENDME, it
155 can confirm the other side's knowledge of the previous cells that
156 were sent, and prevent certain types of denial-of-service attacks.
157 This behavior is controlled by two new consensus parameters: see
158 the proposal for more details. Fixes ticket 26288.
160 o Major features (performance):
161 - Our node selection algorithm now excludes nodes in linear time.
162 Previously, the algorithm was quadratic, which could slow down
163 heavily used onion services. Closes ticket 30307.
165 o Major features (performance, RNG):
166 - Tor now constructs a fast secure pseudorandom number generator for
167 each thread, to use when performance is critical. This PRNG is
168 based on AES-CTR, using a buffering construction similar to
169 libottery and the (newer) OpenBSD arc4random() code. It
170 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
171 small outputs. Although we believe it to be cryptographically
172 strong, we are only using it when necessary for performance.
173 Implements tickets 29023 and 29536.
175 o Major bugfixes (onion service v3):
176 - Fix an unreachable bug in which an introduction point could try to
177 send an INTRODUCE_ACK with a status code that Trunnel would refuse
178 to encode, leading the relay to assert(). We've consolidated the
179 ABI values into Trunnel now. Fixes bug 30454; bugfix
181 - Clients can now handle unknown status codes from INTRODUCE_ACK
182 cells. (The NACK behavior will stay the same.) This will allow us
183 to extend status codes in the future without breaking the normal
184 client behavior. Fixes another part of bug 30454; bugfix
187 o Minor features (circuit padding):
188 - We now use a fast PRNG when scheduling circuit padding. Part of
190 - Allow the padding machine designer to pick the edges of their
191 histogram instead of trying to compute them automatically using an
192 exponential formula. Resolves some undefined behavior in the case
193 of small histograms and allows greater flexibility on machine
194 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
195 - Allow circuit padding machines to hold a circuit open until they
196 are done padding it. Closes ticket 28780.
198 o Minor features (compile-time modules):
199 - Add a "--list-modules" command to print a list of which compile-
200 time modules are enabled. Closes ticket 30452.
202 o Minor features (continuous integration):
203 - Remove sudo configuration lines from .travis.yml as they are no
204 longer needed with current Travis build environment. Resolves
206 - In Travis, show stem's tor log after failure. Closes ticket 30234.
208 o Minor features (controller):
209 - Add onion service version 3 support to the HSFETCH command.
210 Previously, only version 2 onion services were supported. Closes
211 ticket 25417. Patch by Neel Chauhan.
213 o Minor features (debugging):
214 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
215 logging of additional information during assert failure. Now we
216 can use format strings to include information for trouble
217 shooting. Resolves ticket 29662.
219 o Minor features (defense in depth):
220 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
221 case a bug causes them to be used later. Closes ticket 30176.
222 Patch from Tobias Stoeckmann.
223 - Tor now uses a cryptographically strong PRNG even for decisions
224 that we do not believe are security-sensitive. Previously, for
225 performance reasons, we had used a trivially predictable linear
226 congruential generator algorithm for certain load-balancing and
227 statistical sampling decisions. Now we use our fast RNG in those
228 cases. Closes ticket 29542.
230 o Minor features (developer tools):
231 - Tor's "practracker" test script now checks for files and functions
232 that seem too long and complicated. Existing overlong functions
233 and files are accepted for now, but should eventually be
234 refactored. Closes ticket 29221.
235 - Add some scripts used for git maintenance to scripts/git. Closes
237 - Call practracker from pre-push and pre-commit git hooks to let
238 developers know if they made any code style violations. Closes
240 - Add a script to check that each header has a well-formed and
241 unique guard macro. Closes ticket 29756.
243 o Minor features (geoip):
244 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
245 Country database. Closes ticket 30522.
247 o Minor features (HTTP tunnel):
248 - Return an informative web page when the HTTPTunnelPort is used as
249 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
251 o Minor features (IPv6, v3 onion services):
252 - Make v3 onion services put IPv6 addresses in service descriptors.
253 Before this change, service descriptors only contained IPv4
254 addresses. Implements 26992.
256 o Minor features (modularity):
257 - The "--disable-module-dirauth" compile-time option now disables
258 even more dirauth-only code. Closes ticket 30345.
260 o Minor features (performance):
261 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
262 1.1.1 and later), since they tend to be faster than tiny-keccak.
265 o Minor features (testing):
266 - Tor's unit test code now contains helper functions to replace the
267 PRNG with a deterministic or reproducible version for testing.
268 Previously, various tests implemented this in various ways.
269 Implements ticket 29732.
270 - We now have a script, cov-test-determinism.sh, to identify places
271 where our unit test coverage has become nondeterministic. Closes
273 - Check that representative subsets of values of `int` and `unsigned
274 int` can be represented by `void *`. Resolves issue 29537.
276 o Minor bugfixes (bridge authority):
277 - Bridge authorities now set bridges as running or non-running when
278 about to dump their status to a file. Previously, they set bridges
279 as running in response to a GETINFO command, but those shouldn't
280 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
281 Patch by Neel Chauhan.
283 o Minor bugfixes (channel padding statistics):
284 - Channel padding write totals and padding-enabled totals are now
285 counted properly in relay extrainfo descriptors. Fixes bug 29231;
286 bugfix on 0.3.1.1-alpha.
288 o Minor bugfixes (circuit padding):
289 - Add a "CircuitPadding" torrc option to disable circuit padding.
290 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
291 - Allow circuit padding machines to specify that they do not
292 contribute much overhead, and provide consensus flags and torrc
293 options to force clients to only use these low overhead machines.
294 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
295 - Provide a consensus parameter to fully disable circuit padding, to
296 be used in emergency network overload situations. Fixes bug 30173;
297 bugfix on 0.4.0.1-alpha.
298 - The circuit padding subsystem will no longer schedule padding if
299 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
300 - Inspect a circuit-level cell queue before sending padding, to
301 avoid sending padding while too much data is already queued. Fixes
302 bug 29204; bugfix on 0.4.0.1-alpha.
303 - Avoid calling monotime_absolute_usec() in circuit padding machines
304 that do not use token removal or circuit RTT estimation. Fixes bug
305 29085; bugfix on 0.4.0.1-alpha.
307 o Minor bugfixes (compilation, unusual configurations):
308 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
309 due to missing declarations of abort(), and prevent other such
310 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
312 o Minor bugfixes (controller protocol):
313 - Teach the controller parser to distinguish an object preceded by
314 an argument list from one without. Previously, it couldn't
315 distinguish an argument list from the first line of a multiline
316 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
318 o Minor bugfixes (directory authority, ipv6):
319 - Directory authorities with IPv6 support now always mark themselves
320 as reachable via IPv6. Fixes bug 24338; bugfix on 0.4.0.2-alpha.
321 Patch by Neel Chauhan.
323 o Minor bugfixes (documentation):
324 - Improve the documentation for using MapAddress with ".exit". Fixes
325 bug 30109; bugfix on 0.1.0.1-rc.
326 - Improve the monotonic time module and function documentation to
327 explain what "monotonic" actually means, and document some results
328 that have surprised people. Fixes bug 29640; bugfix
330 - Use proper formatting when providing an example on quoting options
331 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
333 o Minor bugfixes (logging):
334 - Do not log a warning when running with an OpenSSL version other
335 than the one Tor was compiled with, if the two versions should be
336 compatible. Previously, we would warn whenever the version was
337 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
338 - Warn operators when the MyFamily option is set but ContactInfo is
339 missing, as the latter should be set too. Fixes bug 25110; bugfix
342 o Minor bugfixes (memory leak):
343 - Avoid a minor memory leak that could occur on relays when failing
344 to create a "keys" directory. Fixes bug 30148; bugfix
347 o Minor bugfixes (onion services):
348 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
349 implemenation) when failing to load an onion service client
350 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
351 - When refusing to launch a controller's HSFETCH request because of
352 rate-limiting, respond to the controller with a new response,
353 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
354 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
356 - When relaunching a circuit to a rendezvous service, mark the
357 circuit as needing high-uptime routers as appropriate. Fixes bug
358 17357; bugfix on 0.4.0.2-alpha. Patch by Neel Chauhan.
359 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
360 (IPv6 support for v3 onion services is still incomplete: see
361 ticket 23493 for details.) Fixes bug 23588; bugfix on
362 0.3.2.1-alpha. Patch by Neel Chauhan.
364 o Minor bugfixes (onion services, performance):
365 - When building circuits to onion services, call tor_addr_parse()
366 less often. Previously, we called tor_addr_parse() in
367 circuit_is_acceptable() even if its output wasn't used. This
368 change should improve performance when building circuits. Fixes
369 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
371 o Minor bugfixes (performance):
372 - When checking whether a node is a bridge, use a fast check to make
373 sure that its identity is set. Previously, we used a constant-time
374 check, which is not necessary in this case. Fixes bug 30308;
375 bugfix on 0.3.5.1-alpha.
377 o Minor bugfixes (pluggable transports):
378 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
379 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
381 o Minor bugfixes (probability distributions):
382 - Refactor and improve parts of the probability distribution code
383 that made Coverity complain. Fixes bug 29805; bugfix
386 o Minor bugfixes (python):
387 - Stop assuming that /usr/bin/python3 exists. For scripts that work
388 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
389 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
391 o Minor bugfixes (relay):
392 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
393 is auto, act as if ExitRelay is 1. Previously, we would ignore
394 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
395 0.3.5.1-alpha. Patch by Neel Chauhan.
397 o Minor bugfixes (stats):
398 - When ExtraInfoStatistics is 0, stop including bandwidth usage
399 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
400 bridge statistics by country in extra-info documents. Fixes bug
401 29018; bugfix on 0.2.4.1-alpha.
403 o Minor bugfixes (testing):
404 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
405 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
406 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
407 - Fix some incorrect code in the v3 onion service unit tests. Fixes
408 bug 29243; bugfix on 0.3.2.1-alpha.
409 - In the "routerkeys/*" tests, check the return values of mkdir()
410 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
411 Found by Coverity as CID 1444254.
412 - Split test_utils_general() into several smaller test functions.
413 This makes it easier to perform resource deallocation on assert
414 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
415 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
417 o Minor bugfixes (tor-resolve):
418 - Fix a memory leak in tor-resolve that could happen if Tor gave it
419 a malformed SOCKS response. (Memory leaks in tor-resolve don't
420 actually matter, but it's good to fix them anyway.) Fixes bug
421 30151; bugfix on 0.4.0.1-alpha.
423 o Code simplification and refactoring:
424 - Abstract out the low-level formatting of replies on the control
425 port. Implements ticket 30007.
426 - Add several assertions in an attempt to fix some Coverity
427 warnings. Closes ticket 30149.
428 - Introduce a connection_dir_buf_add() helper function that checks
429 for compress_state of dir_connection_t and automatically writes a
430 string to directory connection with or without compression.
431 Resolves issue 28816.
432 - Make the base32_decode() API return the number of bytes written,
433 for consistency with base64_decode(). Closes ticket 28913.
434 - Move most relay-only periodic events out of mainloop.c into the
435 relay subsystem. Closes ticket 30414.
436 - Refactor and encapsulate parts of the codebase that manipulate
437 crypt_path_t objects. Resolves issue 30236.
438 - Refactor several places in our code that Coverity incorrectly
439 believed might have memory leaks. Closes ticket 30147.
440 - Remove redundant return values in crypto_format, and the
441 associated return value checks elsewhere in the code. Make the
442 implementations in crypto_format consistent, and remove redundant
443 code. Resolves ticket 29660.
444 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
445 it is not a constant-time function. Closes ticket 30309.
446 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
447 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
448 bugfix on 0.3.2.1-alpha.
449 - Simplify v3 onion service link specifier handling code. Fixes bug
450 23576; bugfix on 0.3.2.1-alpha.
451 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
452 code. Resolves ticket 29108.
453 - Split control.c into several submodules, in preparation for
454 distributing its current responsibilities throughout the codebase.
456 - Start to move responsibility for knowing about periodic events to
457 the appropriate subsystems, so that the mainloop doesn't need to
458 know all the periodic events in the rest of the codebase.
459 Implements tickets 30293 and 30294.
462 - Document how to find git commits and tags for bug fixes in
463 CodingStandards.md. Update some file documentation. Closes
467 - Remove the linux-tor-prio.sh script from contrib/operator-tools
468 directory. Resolves issue 29434.
469 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
470 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
473 o Code simplification and refactoring (shell scripts):
474 - Clean up many of our shell scripts to fix shellcheck warnings.
475 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
476 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
477 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
478 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
479 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
480 nagios-check-tor-authority-cert (ticket 29071),
481 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
482 (ticket 29060), test_key_expiration.sh (ticket 30002),
483 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
487 - In "make test-network-all", test IPv6-only v3 single onion
488 services, using the chutney network single-onion-v23-ipv6-md.
492 Changes in version 0.4.0.5 - 2019-05-02
493 This is the first stable release in the 0.4.0.x series. It contains
494 improvements for power management and bootstrap reporting, as well as
495 preliminary backend support for circuit padding to prevent some kinds
496 of traffic analysis. It also continues our work in refactoring Tor for
497 long-term maintainability.
499 Per our support policy, we will support the 0.4.0.x series for nine
500 months, or until three months after the release of a stable 0.4.1.x:
501 whichever is longer. If you need longer-term support, please stick
502 with 0.3.5.x, which will we plan to support until Feb 2022.
504 Below are the changes since 0.4.0.4-rc. For a complete list of changes
505 since 0.3.5.7, see the ReleaseNotes file.
507 o Minor features (continuous integration):
508 - In Travis, tell timelimit to use stem's backtrace signals, and
509 launch python directly from timelimit, so python receives the
510 signals from timelimit, rather than make. Closes ticket 30117.
512 o Minor features (diagnostic):
513 - Add more diagnostic log messages in an attempt to solve the issue
514 of NUL bytes appearing in a microdescriptor cache. Related to
517 o Minor features (testing):
518 - Use the approx_time() function when setting the "Expires" header
519 in directory replies, to make them more testable. Needed for
522 o Minor bugfixes (rust):
523 - Abort on panic in all build profiles, instead of potentially
524 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
526 o Minor bugfixes (shellcheck):
527 - Look for scripts in their correct locations during "make
528 shellcheck". Previously we had looked in the wrong place during
529 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
531 o Minor bugfixes (testing):
532 - Check the time in the "Expires" header using approx_time(). Fixes
533 bug 30001; bugfix on 0.4.0.4-rc.
535 o Minor bugfixes (UI):
536 - Lower log level of unlink() errors during bootstrap. Fixes bug
537 29930; bugfix on 0.4.0.1-alpha.
540 Changes in version 0.4.0.4-rc - 2019-04-11
541 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
542 several bugs from earlier versions, including some that had affected
543 stability, and one that prevented relays from working with NSS.
545 o Major bugfixes (NSS, relay):
546 - When running with NSS, disable TLS 1.2 ciphersuites that use
547 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
548 these ciphersuites don't work -- which caused relays to fail to
549 handshake with one another when these ciphersuites were enabled.
550 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
552 o Minor features (bandwidth authority):
553 - Make bandwidth authorities ignore relays that are reported in the
554 bandwidth file with the flag "vote=0". This change allows us to
555 report unmeasured relays for diagnostic reasons without including
556 their bandwidth in the bandwidth authorities' vote. Closes
558 - When a directory authority is using a bandwidth file to obtain the
559 bandwidth values that will be included in the next vote, serve
560 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
563 o Minor features (circuit padding):
564 - Stop warning about undefined behavior in the probability
565 distribution tests. Float division by zero may technically be
566 undefined behavior in C, but it's well defined in IEEE 754.
567 Partial backport of 29298. Closes ticket 29527; bugfix
570 o Minor features (continuous integration):
571 - On Travis Rust builds, cleanup Rust registry and refrain from
572 caching the "target/" directory to speed up builds. Resolves
575 o Minor features (dormant mode):
576 - Add a DormantCanceledByStartup option to tell Tor that it should
577 treat a startup event as cancelling any previous dormant state.
578 Integrators should use this option with caution: it should only be
579 used if Tor is being started because of something that the user
580 did, and not if Tor is being automatically started in the
581 background. Closes ticket 29357.
583 o Minor features (geoip):
584 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
585 Country database. Closes ticket 29992.
587 o Minor features (NSS, diagnostic):
588 - Try to log an error from NSS (if there is any) and a more useful
589 description of our situation if we are using NSS and a call to
590 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
592 o Minor bugfixes (security):
593 - Fix a potential double free bug when reading huge bandwidth files.
594 The issue is not exploitable in the current Tor network because
595 the vulnerable code is only reached when directory authorities
596 read bandwidth files, but bandwidth files come from a trusted
597 source (usually the authorities themselves). Furthermore, the
598 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
599 which are not used by any of the current authorities. Fixes bug
600 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
602 - Verify in more places that we are not about to create a buffer
603 with more than INT_MAX bytes, to avoid possible OOB access in the
604 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
605 fixed by Tobias Stoeckmann.
607 o Minor bugfix (continuous integration):
608 - Reset coverage state on disk after Travis CI has finished. This
609 should prevent future coverage merge errors from causing the test
610 suite for the "process" subsystem to fail. The process subsystem
611 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
613 - Terminate test-stem if it takes more than 9.5 minutes to run.
614 (Travis terminates the job after 10 minutes of no output.)
615 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
617 o Minor bugfixes (bootstrap reporting):
618 - During bootstrap reporting, correctly distinguish pluggable
619 transports from plain proxies. Fixes bug 28925; bugfix
622 o Minor bugfixes (C correctness):
623 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
624 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
627 o Minor bugfixes (circuitpadding testing):
628 - Minor tweaks to avoid rare test failures related to timers and
629 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
631 o Minor bugfixes (directory authorities):
632 - Actually include the bandwidth-file-digest line in directory
633 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
635 o Minor bugfixes (logging):
636 - On Windows, when errors cause us to reload a consensus from disk,
637 tell the user that we are retrying at log level "notice".
638 Previously we only logged this information at "info", which was
639 confusing because the errors themselves were logged at "warning".
640 Improves previous fix for 28614. Fixes bug 30004; bugfix
643 o Minor bugfixes (pluggable transports):
644 - Restore old behavior when it comes to discovering the path of a
645 given Pluggable Transport executable file. A change in
646 0.4.0.1-alpha had broken this behavior on paths containing a
647 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
649 o Minor bugfixes (testing):
650 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
651 recent test-network.sh to use new chutney features in CI. Fixes
652 bug 29703; bugfix on 0.2.9.1-alpha.
653 - Fix a test failure on Windows caused by an unexpected "BUG"
654 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
657 o Minor bugfixes (TLS protocol):
658 - When classifying a client's selection of TLS ciphers, if the
659 client ciphers are not yet available, do not cache the result.
660 Previously, we had cached the unavailability of the cipher list
661 and never looked again, which in turn led us to assume that the
662 client only supported the ancient V1 link protocol. This, in turn,
663 was causing Stem integration tests to stall in some cases. Fixes
664 bug 30021; bugfix on 0.2.4.8-alpha.
666 o Code simplification and refactoring:
667 - Introduce a connection_dir_buf_add() helper function that detects
668 whether compression is in use, and adds a string accordingly.
669 Resolves issue 28816.
670 - Refactor handle_get_next_bandwidth() to use
671 connection_dir_buf_add(). Implements ticket 29897.
674 - Clarify that Tor performs stream isolation among *Port listeners
675 by default. Resolves issue 29121.
678 Changes in version 0.4.0.3-alpha - 2019-03-22
679 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
680 bugs from earlier versions.
682 o Minor features (address selection):
683 - Treat the subnet 100.64.0.0/10 as public for some purposes;
684 private for others. This subnet is the RFC 6598 (Carrier Grade
685 NAT) IP range, and is deployed by many ISPs as an alternative to
686 RFC 1918 that does not break existing internal networks. Tor now
687 blocks SOCKS and control ports on these addresses and warns users
688 if client ports or ExtORPorts are listening on a RFC 6598 address.
689 Closes ticket 28525. Patch by Neel Chauhan.
691 o Minor features (geoip):
692 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
693 Country database. Closes ticket 29666.
695 o Minor bugfixes (circuitpadding):
696 - Inspect the circuit-level cell queue before sending padding, to
697 avoid sending padding when too much data is queued. Fixes bug
698 29204; bugfix on 0.4.0.1-alpha.
700 o Minor bugfixes (logging):
701 - Correct a misleading error message when IPv4Only or IPv6Only is
702 used but the resolved address can not be interpreted as an address
703 of the specified IP version. Fixes bug 13221; bugfix on
704 0.2.3.9-alpha. Patch from Kris Katterjohn.
705 - Log the correct port number for listening sockets when "auto" is
706 used to let Tor pick the port number. Previously, port 0 was
707 logged instead of the actual port number. Fixes bug 29144; bugfix
708 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
709 - Stop logging a BUG() warning when Tor is waiting for exit
710 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
712 o Minor bugfixes (memory management):
713 - Refactor the shared random state's memory management so that it
714 actually takes ownership of the shared random value pointers.
715 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
717 o Minor bugfixes (memory management, testing):
718 - Stop leaking parts of the shared random state in the shared-random
719 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
721 o Minor bugfixes (pluggable transports):
722 - Fix an assertion failure crash bug when a pluggable transport is
723 terminated during the bootstrap phase. Fixes bug 29562; bugfix
726 o Minor bugfixes (Rust, protover):
727 - Add a missing "Padding" value to the Rust implementation of
728 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
730 o Minor bugfixes (single onion services):
731 - Allow connections to single onion services to remain idle without
732 being disconnected. Previously, relays acting as rendezvous points
733 for single onion services were mistakenly closing idle rendezvous
734 circuits after 60 seconds, thinking that they were unused
735 directory-fetching circuits that had served their purpose. Fixes
736 bug 29665; bugfix on 0.2.1.26.
738 o Minor bugfixes (stats):
739 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
740 relay and bridge extra-info documents. Fixes bug 29017; bugfix
743 o Minor bugfixes (testing):
744 - Downgrade some LOG_ERR messages in the address/* tests to
745 warnings. The LOG_ERR messages were occurring when we had no
746 configured network. We were failing the unit tests, because we
747 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
748 29530; bugfix on 0.3.5.8.
749 - Fix our gcov wrapper script to look for object files at the
750 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
751 - Decrease the false positive rate of stochastic probability
752 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
754 o Minor bugfixes (Windows, CI):
755 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
756 Windows Server 2012 R2 job. The remaining 2 jobs still provide
757 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
758 fast_finish, so failed jobs terminate the build immediately. Fixes
759 bug 29601; bugfix on 0.3.5.4-alpha.
762 Changes in version 0.3.5.8 - 2019-02-21
763 Tor 0.3.5.8 backports several fixes from later releases, including fixes
764 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
767 It also includes a fix for a medium-severity security bug affecting Tor
768 0.3.2.1-alpha and later. All Tor instances running an affected release
769 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
771 o Major bugfixes (cell scheduler, KIST, security):
772 - Make KIST consider the outbuf length when computing what it can
773 put in the outbuf. Previously, KIST acted as though the outbuf
774 were empty, which could lead to the outbuf becoming too full. It
775 is possible that an attacker could exploit this bug to cause a Tor
776 client or relay to run out of memory and crash. Fixes bug 29168;
777 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
778 TROVE-2019-001 and CVE-2019-8955.
780 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
781 - Gracefully handle empty username/password fields in SOCKS5
782 username/password auth message and allow SOCKS5 handshake to
783 continue. Previously, we had rejected these handshakes, breaking
784 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
786 o Minor features (compilation, backport from 0.4.0.2-alpha):
787 - Compile correctly when OpenSSL is built with engine support
788 disabled, or with deprecated APIs disabled. Closes ticket 29026.
789 Patches from "Mangix".
791 o Minor features (geoip):
792 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
793 Country database. Closes ticket 29478.
795 o Minor features (testing, backport from 0.4.0.2-alpha):
796 - Treat all unexpected ERR and BUG messages as test failures. Closes
799 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
800 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
801 connection waiting for a descriptor that we actually have in the
802 cache. It turns out that this can actually happen, though it is
803 rare. Now, tor will recover and retry the descriptor. Fixes bug
804 28669; bugfix on 0.3.2.4-alpha.
806 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
807 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
808 IPv6 socket was bound using an address family of AF_INET instead
809 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
812 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
813 - Update Cargo.lock file to match the version made by the latest
814 version of Rust, so that "make distcheck" will pass again. Fixes
815 bug 29244; bugfix on 0.3.3.4-alpha.
817 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
818 - Select guards even if the consensus has expired, as long as the
819 consensus is still reasonably live. Fixes bug 24661; bugfix
822 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
823 - Compile correctly on OpenBSD; previously, we were missing some
824 headers required in order to detect it properly. Fixes bug 28938;
825 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
827 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
828 - Describe the contents of the v3 onion service client authorization
829 files correctly: They hold public keys, not private keys. Fixes
830 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
832 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
833 - Rework rep_hist_log_link_protocol_counts() to iterate through all
834 link protocol versions when logging incoming/outgoing connection
835 counts. Tor no longer skips version 5, and we won't have to
836 remember to update this function when new link protocol version is
837 developed. Fixes bug 28920; bugfix on 0.2.6.10.
839 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
840 - Log more information at "warning" level when unable to read a
841 private key; log more information at "info" level when unable to
842 read a public key. We had warnings here before, but they were lost
843 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
845 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
846 - The amount of total available physical memory is now determined
847 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
848 when it is defined and a 64-bit variant is not available. Fixes
849 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
851 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
852 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
853 than one private key for a hidden service. Fixes bug 29040; bugfix
855 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
856 "debug" level. Tor used to log it as a warning, which caused very
857 long log lines to appear for some users. Fixes bug 29135; bugfix
859 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
860 as a warning. Instead, log it as a protocol warning, because there
861 is nothing that relay operators can do to fix it. Fixes bug 29029;
862 bugfix on 0.2.5.7-rc.
864 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
865 - Mark outdated dirservers when Tor only has a reasonably live
866 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
868 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
869 - Detect and suppress "bug" warnings from the util/time test on
870 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
871 - Do not log an error-level message if we fail to find an IPv6
872 network interface from the unit tests. Fixes bug 29160; bugfix
875 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
876 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
877 Some users took this phrasing to mean that the mentioned guard was
878 under their control or responsibility, which it is not. Fixes bug
879 28895; bugfix on Tor 0.3.0.1-alpha.
882 Changes in version 0.3.4.11 - 2019-02-21
883 Tor 0.3.4.11 is the third stable release in its series. It includes
884 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
885 later. All Tor instances running an affected release should upgrade to
886 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
888 o Major bugfixes (cell scheduler, KIST, security):
889 - Make KIST consider the outbuf length when computing what it can
890 put in the outbuf. Previously, KIST acted as though the outbuf
891 were empty, which could lead to the outbuf becoming too full. It
892 is possible that an attacker could exploit this bug to cause a Tor
893 client or relay to run out of memory and crash. Fixes bug 29168;
894 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
895 TROVE-2019-001 and CVE-2019-8955.
897 o Minor features (geoip):
898 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
899 Country database. Closes ticket 29478.
901 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
902 - Update Cargo.lock file to match the version made by the latest
903 version of Rust, so that "make distcheck" will pass again. Fixes
904 bug 29244; bugfix on 0.3.3.4-alpha.
906 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
907 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
908 as a warning. Instead, log it as a protocol warning, because there
909 is nothing that relay operators can do to fix it. Fixes bug 29029;
910 bugfix on 0.2.5.7-rc.
913 Changes in version 0.3.3.12 - 2019-02-21
914 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
915 0.3.2.1-alpha and later. All Tor instances running an affected release
916 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
918 This release marks the end of support for the Tor 0.3.3.x series. We
919 recommend that users switch to either the Tor 0.3.4 series (supported
920 until at least 10 June 2019), or the Tor 0.3.5 series, which will
921 receive long-term support until at least 1 Feb 2022.
923 o Major bugfixes (cell scheduler, KIST, security):
924 - Make KIST consider the outbuf length when computing what it can
925 put in the outbuf. Previously, KIST acted as though the outbuf
926 were empty, which could lead to the outbuf becoming too full. It
927 is possible that an attacker could exploit this bug to cause a Tor
928 client or relay to run out of memory and crash. Fixes bug 29168;
929 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
930 TROVE-2019-001 and CVE-2019-8955.
932 o Minor features (geoip):
933 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
934 Country database. Closes ticket 29478.
936 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
937 - Update Cargo.lock file to match the version made by the latest
938 version of Rust, so that "make distcheck" will pass again. Fixes
939 bug 29244; bugfix on 0.3.3.4-alpha.
941 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
942 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
943 as a warning. Instead, log it as a protocol warning, because there
944 is nothing that relay operators can do to fix it. Fixes bug 29029;
945 bugfix on 0.2.5.7-rc.
948 Changes in version 0.4.0.2-alpha - 2019-02-21
949 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
950 bugs from earlier versions, including several that had broken
951 backward compatibility.
953 It also includes a fix for a medium-severity security bug affecting Tor
954 0.3.2.1-alpha and later. All Tor instances running an affected release
955 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
957 o Major bugfixes (cell scheduler, KIST, security):
958 - Make KIST consider the outbuf length when computing what it can
959 put in the outbuf. Previously, KIST acted as though the outbuf
960 were empty, which could lead to the outbuf becoming too full. It
961 is possible that an attacker could exploit this bug to cause a Tor
962 client or relay to run out of memory and crash. Fixes bug 29168;
963 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
964 TROVE-2019-001 and CVE-2019-8955.
966 o Major bugfixes (networking):
967 - Gracefully handle empty username/password fields in SOCKS5
968 username/password auth messsage and allow SOCKS5 handshake to
969 continue. Previously, we had rejected these handshakes, breaking
970 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
972 o Major bugfixes (windows, startup):
973 - When reading a consensus file from disk, detect whether it was
974 written in text mode, and re-read it in text mode if so. Always
975 write consensus files in binary mode so that we can map them into
976 memory later. Previously, we had written in text mode, which
977 confused us when we tried to map the file on windows. Fixes bug
978 28614; bugfix on 0.4.0.1-alpha.
980 o Minor features (compilation):
981 - Compile correctly when OpenSSL is built with engine support
982 disabled, or with deprecated APIs disabled. Closes ticket 29026.
983 Patches from "Mangix".
985 o Minor features (developer tooling):
986 - Check that bugfix versions in changes files look like Tor versions
987 from the versions spec. Warn when bugfixes claim to be on a future
988 release. Closes ticket 27761.
989 - Provide a git pre-commit hook that disallows committing if we have
990 any failures in our code and changelog formatting checks. It is
991 now available in scripts/maint/pre-commit.git-hook. Implements
994 o Minor features (directory authority):
995 - When a directory authority is using a bandwidth file to obtain
996 bandwidth values, include the digest of that file in the vote.
999 o Minor features (geoip):
1000 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1001 Country database. Closes ticket 29478.
1003 o Minor features (testing):
1004 - Treat all unexpected ERR and BUG messages as test failures. Closes
1007 o Minor bugfixes (build, compatibility, rust):
1008 - Update Cargo.lock file to match the version made by the latest
1009 version of Rust, so that "make distcheck" will pass again. Fixes
1010 bug 29244; bugfix on 0.3.3.4-alpha.
1012 o Minor bugfixes (compilation):
1013 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
1014 29169; bugfix on 0.4.0.1-alpha.
1015 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1016 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1018 o Minor bugfixes (documentation):
1019 - Describe the contents of the v3 onion service client authorization
1020 files correctly: They hold public keys, not private keys. Fixes
1021 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1023 o Minor bugfixes (linux seccomp sandbox):
1024 - Fix startup crash when experimental sandbox support is enabled.
1025 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
1027 o Minor bugfixes (logging):
1028 - Avoid logging that we are relaxing a circuit timeout when that
1029 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1030 - Log more information at "warning" level when unable to read a
1031 private key; log more information at "info" level when unable to
1032 read a public key. We had warnings here before, but they were lost
1033 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1035 o Minor bugfixes (misc):
1036 - The amount of total available physical memory is now determined
1037 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1038 when it is defined and a 64-bit variant is not available. Fixes
1039 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1041 o Minor bugfixes (onion services):
1042 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1043 than one private key for a hidden service. Fixes bug 29040; bugfix
1045 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1046 "debug" level. Tor used to log it as a warning, which caused very
1047 long log lines to appear for some users. Fixes bug 29135; bugfix
1049 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1050 as a warning. Instead, log it as a protocol warning, because there
1051 is nothing that relay operators can do to fix it. Fixes bug 29029;
1052 bugfix on 0.2.5.7-rc.
1054 o Minor bugfixes (scheduler):
1055 - When re-adding channels to the pending list, check the correct
1056 channel's sched_heap_idx. This issue has had no effect in mainline
1057 Tor, but could have led to bugs down the road in improved versions
1058 of our circuit scheduling code. Fixes bug 29508; bugfix
1061 o Minor bugfixes (tests):
1062 - Fix intermittent failures on an adaptive padding test. Fixes one
1063 case of bug 29122; bugfix on 0.4.0.1-alpha.
1064 - Disable an unstable circuit-padding test that was failing
1065 intermittently because of an ill-defined small histogram. Such
1066 histograms will be allowed again after 29298 is implemented. Fixes
1067 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
1068 - Detect and suppress "bug" warnings from the util/time test on
1069 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1070 - Do not log an error-level message if we fail to find an IPv6
1071 network interface from the unit tests. Fixes bug 29160; bugfix
1075 - In the manpage entry describing MapAddress torrc setting, use
1076 example IP addresses from ranges specified for use in documentation
1077 by RFC 5737. Resolves issue 28623.
1080 - Remove the old check-tor script. Resolves issue 29072.
1083 Changes in version 0.4.0.1-alpha - 2019-01-18
1084 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
1085 introduces improved features for power and bandwidth conservation,
1086 more accurate reporting of bootstrap progress for user interfaces, and
1087 an experimental backend for an exciting new adaptive padding feature.
1088 There is also the usual assortment of bugfixes and minor features, all
1091 o Major features (battery management, client, dormant mode):
1092 - When Tor is running as a client, and it is unused for a long time,
1093 it can now enter a "dormant" state. When Tor is dormant, it avoids
1094 network and CPU activity until it is reawoken either by a user
1095 request or by a controller command. For more information, see the
1096 configuration options starting with "Dormant". Implements tickets
1098 - The client's memory of whether it is "dormant", and how long it
1099 has spent idle, persists across invocations. Implements
1101 - There is a DormantOnFirstStartup option that integrators can use
1102 if they expect that in many cases, Tor will be installed but
1105 o Major features (bootstrap reporting):
1106 - When reporting bootstrap progress, report the first connection
1107 uniformly, regardless of whether it's a connection for building
1108 application circuits. This allows finer-grained reporting of early
1109 progress than previously possible, with the improvements of ticket
1110 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
1111 - When reporting bootstrap progress, treat connecting to a proxy or
1112 pluggable transport as separate from having successfully used that
1113 proxy or pluggable transport to connect to a relay. Closes tickets
1116 o Major features (circuit padding):
1117 - Implement preliminary support for the circuit padding portion of
1118 Proposal 254. The implementation supports Adaptive Padding (aka
1119 WTF-PAD) state machines for use between experimental clients and
1120 relays. Support is also provided for APE-style state machines that
1121 use probability distributions instead of histograms to specify
1122 inter-packet delay. At the moment, Tor does not provide any
1123 padding state machines that are used in normal operation: for now,
1124 this feature exists solely for experimentation. Closes
1127 o Major features (refactoring):
1128 - Tor now uses an explicit list of its own subsystems when
1129 initializing and shutting down. Previously, these systems were
1130 managed implicitly in various places throughout the codebase.
1131 (There may still be some subsystems using the old system.) Closes
1134 o Minor features (bootstrap reporting):
1135 - When reporting bootstrap progress, stop distinguishing between
1136 situations where only internal paths are available and situations
1137 where external paths are available. Previously, Tor would often
1138 erroneously report that it had only internal paths. Closes
1141 o Minor features (continuous integration):
1142 - Log Python version during each Travis CI job. Resolves
1145 o Minor features (controller):
1146 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
1147 Implements ticket 28843.
1149 o Minor features (developer tooling):
1150 - Provide a git hook script to prevent "fixup!" and "squash!"
1151 commits from ending up in the master branch, as scripts/main/pre-
1152 push.git-hook. Closes ticket 27993.
1154 o Minor features (directory authority):
1155 - Directory authorities support a new consensus algorithm, under
1156 which the family lines in microdescriptors are encoded in a
1157 canonical form. This change makes family lines more compressible
1158 in transit, and on the client. Closes ticket 28266; implements
1161 o Minor features (directory authority, relay):
1162 - Authorities now vote on a "StaleDesc" flag to indicate that a
1163 relay's descriptor is so old that the relay should upload again
1164 soon. Relays treat this flag as a signal to upload a new
1165 descriptor. This flag will eventually let us remove the
1166 'published' date from routerstatus entries, and make our consensus
1167 diffs much smaller. Closes ticket 26770; implements proposal 293.
1169 o Minor features (fallback directory mirrors):
1170 - Update the fallback whitelist based on operator opt-ins and opt-
1171 outs. Closes ticket 24805, patch by Phoul.
1173 o Minor features (FreeBSD):
1174 - On FreeBSD-based systems, warn relay operators if the
1175 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
1176 Closes ticket 28518.
1178 o Minor features (HTTP standards compliance):
1179 - Stop sending the header "Content-type: application/octet-stream"
1180 along with transparently compressed documents: this confused
1181 browsers. Closes ticket 28100.
1183 o Minor features (IPv6):
1184 - We add an option ClientAutoIPv6ORPort, to make clients randomly
1185 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
1186 every time a node is loaded from a new consensus or bridge config.
1187 We expect that this option will enable clients to bootstrap more
1188 quickly without having to determine whether they support IPv4,
1189 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
1190 - When using addrs_in_same_network_family(), avoid choosing circuit
1191 paths that pass through the same IPv6 subnet more than once.
1192 Previously, we only checked IPv4 subnets. Closes ticket 24393.
1193 Patch by Neel Chauhan.
1195 o Minor features (log messages):
1196 - Improve log message in v3 onion services that could print out
1197 negative revision counters. Closes ticket 27707. Patch
1200 o Minor features (memory usage):
1201 - Save memory by storing microdescriptor family lists with a more
1202 compact representation. Closes ticket 27359.
1203 - Tor clients now use mmap() to read consensus files from disk, so
1204 that they no longer need keep the full text of a consensus in
1205 memory when parsing it or applying a diff. Closes ticket 27244.
1207 o Minor features (parsing):
1208 - Directory authorities now validate that router descriptors and
1209 ExtraInfo documents are in a valid subset of UTF-8, and reject
1210 them if they are not. Closes ticket 27367.
1212 o Minor features (performance):
1213 - Cache the results of summarize_protocol_flags(), so that we don't
1214 have to parse the same protocol-versions string over and over.
1215 This should save us a huge number of malloc calls on startup, and
1216 may reduce memory fragmentation with some allocators. Closes
1218 - Remove a needless memset() call from get_token_arguments, thereby
1219 speeding up the tokenization of directory objects by about 20%.
1220 Closes ticket 28852.
1221 - Replace parse_short_policy() with a faster implementation, to
1222 improve microdescriptor parsing time. Closes ticket 28853.
1223 - Speed up directory parsing a little by avoiding use of the non-
1224 inlined strcmp_len() function. Closes ticket 28856.
1225 - Speed up microdescriptor parsing by about 30%, to help improve
1226 startup time. Closes ticket 28839.
1228 o Minor features (pluggable transports):
1229 - Add support for emitting STATUS updates to Tor's control port from
1230 a pluggable transport process. Closes ticket 28846.
1231 - Add support for logging to Tor's logging subsystem from a
1232 pluggable transport process. Closes ticket 28180.
1234 o Minor features (process management):
1235 - Add a new process API for handling child processes. This new API
1236 allows Tor to have bi-directional communication with child
1237 processes on both Unix and Windows. Closes ticket 28179.
1238 - Use the subsystem manager to initialize and shut down the process
1239 module. Closes ticket 28847.
1241 o Minor features (relay):
1242 - When listing relay families, list them in canonical form including
1243 the relay's own identity, and try to give a more useful set of
1244 warnings. Part of ticket 28266 and proposal 298.
1246 o Minor features (required protocols):
1247 - Before exiting because of a missing required protocol, Tor will
1248 now check the publication time of the consensus, and not exit
1249 unless the consensus is newer than the Tor program's own release
1250 date. Previously, Tor would not check the consensus publication
1251 time, and so might exit because of a missing protocol that might
1252 no longer be required in a current consensus. Implements proposal
1253 297; closes ticket 27735.
1255 o Minor features (testing):
1256 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
1257 networks. Closes ticket 28840. Patch by Rob Jansen.
1259 o Minor bugfixes (client, clock skew):
1260 - Bootstrap successfully even when Tor's clock is behind the clocks
1261 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
1262 - Select guards even if the consensus has expired, as long as the
1263 consensus is still reasonably live. Fixes bug 24661; bugfix
1266 o Minor bugfixes (compilation):
1267 - Compile correctly on OpenBSD; previously, we were missing some
1268 headers required in order to detect it properly. Fixes bug 28938;
1269 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1271 o Minor bugfixes (directory clients):
1272 - Mark outdated dirservers when Tor only has a reasonably live
1273 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1275 o Minor bugfixes (directory mirrors):
1276 - Even when a directory mirror's clock is behind the clocks on the
1277 authorities, we now allow the mirror to serve "future"
1278 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
1280 o Minor bugfixes (DNS):
1281 - Gracefully handle an empty or absent resolve.conf file by falling
1282 back to using "localhost" as a DNS server (and hoping it works).
1283 Previously, we would just stop running as an exit. Fixes bug
1284 21900; bugfix on 0.2.1.10-alpha.
1286 o Minor bugfixes (guards):
1287 - In count_acceptable_nodes(), the minimum number is now one bridge
1288 or guard node, and two non-guard nodes for a circuit. Previously,
1289 we had added up the sum of all nodes with a descriptor, but that
1290 could cause us to build failing circuits when we had either too
1291 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
1292 0.3.6.1-alpha. Patch by Neel Chauhan.
1294 o Minor bugfixes (IPv6):
1295 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1296 IPv6 socket was bound using an address family of AF_INET instead
1297 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1300 o Minor bugfixes (logging):
1301 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1302 link protocol versions when logging incoming/outgoing connection
1303 counts. Tor no longer skips version 5, and we won't have to
1304 remember to update this function when new link protocol version is
1305 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1307 o Minor bugfixes (networking):
1308 - Introduce additional checks into tor_addr_parse() to reject
1309 certain incorrect inputs that previously were not detected. Fixes
1310 bug 23082; bugfix on 0.2.0.10-alpha.
1312 o Minor bugfixes (onion service v3, client):
1313 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1314 connection waiting for a descriptor that we actually have in the
1315 cache. It turns out that this can actually happen, though it is
1316 rare. Now, tor will recover and retry the descriptor. Fixes bug
1317 28669; bugfix on 0.3.2.4-alpha.
1319 o Minor bugfixes (periodic events):
1320 - Refrain from calling routerlist_remove_old_routers() from
1321 check_descriptor_callback(). Instead, create a new hourly periodic
1322 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1324 o Minor bugfixes (pluggable transports):
1325 - Make sure that data is continously read from standard output and
1326 standard error pipes of a pluggable transport child-process, to
1327 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1328 bugfix on 0.2.3.6-alpha.
1330 o Minor bugfixes (unit tests):
1331 - Instead of relying on hs_free_all() to clean up all onion service
1332 objects in test_build_descriptors(), we now deallocate them one by
1333 one. This lets Coverity know that we are not leaking memory there
1334 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1336 o Minor bugfixes (usability):
1337 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1338 Some users took this phrasing to mean that the mentioned guard was
1339 under their control or responsibility, which it is not. Fixes bug
1340 28895; bugfix on Tor 0.3.0.1-alpha.
1342 o Code simplification and refactoring:
1343 - Reimplement NETINFO cell parsing and generation to rely on
1344 trunnel-generated wire format handling code. Closes ticket 27325.
1345 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1347 - Rework SOCKS wire format handling to rely on trunnel-generated
1348 parsing/generation code. Resolves ticket 27620.
1349 - Split out bootstrap progress reporting from control.c into a
1350 separate file. Part of ticket 27402.
1351 - The .may_include files that we use to describe our directory-by-
1352 directory dependency structure now describe a noncircular
1353 dependency graph over the directories that they cover. Our
1354 checkIncludes.py tool now enforces this noncircularity. Closes
1358 - Mention that you cannot add a new onion service if Tor is already
1359 running with Sandbox enabled. Closes ticket 28560.
1360 - Improve ControlPort documentation. Mention that it accepts
1361 address:port pairs, and can be used multiple times. Closes
1363 - Document the exact output of "tor --version". Closes ticket 28889.
1366 - Stop responding to the 'GETINFO status/version/num-concurring' and
1367 'GETINFO status/version/num-versioning' control port commands, as
1368 those were deprecated back in 0.2.0.30. Also stop listing them in
1369 output of 'GETINFO info/names'. Resolves ticket 28757.
1370 - The scripts used to generate and maintain the list of fallback
1371 directories have been extracted into a new "fallback-scripts"
1372 repository. Closes ticket 27914.
1375 - Run shellcheck for scripts in the in scripts/ directory. Closes
1377 - Add unit tests for tokenize_string() and get_next_token()
1378 functions. Resolves ticket 27625.
1380 o Code simplification and refactoring (onion service v3):
1381 - Consolidate the authorized client descriptor cookie computation
1382 code from client and service into one function. Closes
1385 o Code simplification and refactoring (shell scripts):
1386 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1388 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1389 Resolves ticket 28006.
1390 - Fix issues that shellcheck found in updateRustDependencies.sh.
1391 Resolves ticket 28012.
1392 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1393 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1394 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1395 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1399 Changes in version 0.3.3.11 - 2019-01-07
1400 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1401 numerous fixes, including an important fix for anyone using OpenSSL
1402 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1403 to this version, or to a later series.
1405 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1406 We anticipate that this will be the last release of Tor 0.3.3, unless
1407 some major bug is before then. Some time between now and then, users
1408 should switch to either the Tor 0.3.4 series (supported until at least
1409 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1410 support until at least 1 Feb 2022.
1412 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1413 - Fix our usage of named groups when running as a TLS 1.3 client in
1414 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1415 running as a relay, which caused clients to fail to negotiate TLS
1416 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1419 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1420 - Fix a use-after-free error that could be caused by passing Tor an
1421 impossible set of options that would fail during options_act().
1422 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1424 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1425 - Only run one online rust build in Travis, to reduce network
1426 errors. Skip offline rust builds on Travis for Linux gcc, because
1427 they're redundant. Implements ticket 27252.
1428 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1429 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1430 Linux with default settings, because all the non-default builds
1431 use gcc on Linux. Implements ticket 27252.
1433 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1434 - Use the Travis Homebrew addon to install packages on macOS during
1435 Travis CI. The package list is the same, but the Homebrew addon
1436 does not do a `brew update` by default. Implements ticket 27738.
1438 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1439 - Replace the 150 fallbacks originally introduced in Tor
1440 0.3.3.1-alpha in January 2018 (of which ~115 were still
1441 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1442 removed) generated in December 2018. Closes ticket 24803.
1444 o Minor features (geoip):
1445 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1446 Country database. Closes ticket 29012.
1448 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1449 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1450 key export function from handling long labels. When this bug is
1451 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1452 version of OpenSSL without this bug when it becomes available.
1453 Closes ticket 28973.
1455 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1456 - Update relay descriptor on bandwidth changes only when the uptime
1457 is smaller than 24h, in order to reduce the efficiency of guard
1458 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1460 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1461 - Avoid undefined behavior in an end-of-string check when parsing
1462 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1465 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1466 - Rewrite our assertion macros so that they no longer suppress the
1467 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1469 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1470 - Initialize a variable unconditionally in aes_new_cipher(), since
1471 some compilers cannot tell that we always initialize it before
1472 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1474 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1475 - Log additional info when we get a relay that shares an ed25519 ID
1476 with a different relay, instead making a BUG() warning. Fixes bug
1477 27800; bugfix on 0.3.2.1-alpha.
1479 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1480 - When a user requests a group-readable DataDirectory, give it to
1481 them. Previously, when the DataDirectory and the CacheDirectory
1482 were the same, the default setting (0) for
1483 CacheDirectoryGroupReadable would override the setting for
1484 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1487 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1488 - When the onion service directory can't be created or has the wrong
1489 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1492 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1493 - Close all SOCKS request (for the same .onion) if the newly fetched
1494 descriptor is unusable. Before that, we would close only the first
1495 one leaving the other hanging and let to time out by themselves.
1496 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1498 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1499 - Don't warn so loudly when Tor is unable to decode an onion
1500 descriptor. This can now happen as a normal use case if a client
1501 gets a descriptor with client authorization but the client is not
1502 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1504 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1505 - When deleting an ephemeral onion service (DEL_ONION), do not close
1506 any rendezvous circuits in order to let the existing client
1507 connections finish by themselves or closed by the application. The
1508 HS v2 is doing that already so now we have the same behavior for
1509 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1511 o Minor bugfixes (HTTP tunnel):
1512 - Fix a bug warning when closing an HTTP tunnel connection due to
1513 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1516 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1517 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1518 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1520 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1521 - Ensure circuitmux queues are empty before scheduling or sending
1522 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1524 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1525 - Reject protocol names containing bytes other than alphanumeric
1526 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1529 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1530 - Compute protover votes correctly in the rust version of the
1531 protover code. Previously, the protover rewrite in 24031 allowed
1532 repeated votes from the same voter for the same protocol version
1533 to be counted multiple times in protover_compute_vote(). Fixes bug
1534 27649; bugfix on 0.3.3.5-rc.
1535 - Reject protover names that contain invalid characters. Fixes bug
1536 27687; bugfix on 0.3.3.1-alpha.
1538 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1539 - protover_all_supported() would attempt to allocate up to 16GB on
1540 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1541 bugfix on 0.3.3.5-rc.
1543 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1544 - Fix a potential null dereference in protover_all_supported(). Add
1545 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1546 - Return a string that can be safely freed by C code, not one
1547 created by the rust allocator, in protover_all_supported(). Fixes
1548 bug 27740; bugfix on 0.3.3.1-alpha.
1549 - Fix an API mismatch in the rust implementation of
1550 protover_compute_vote(). This bug could have caused crashes on any
1551 directory authorities running Tor with Rust (which we do not yet
1552 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1554 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1555 - If a unit test running in a subprocess exits abnormally or with a
1556 nonzero status code, treat the test as having failed, even if the
1557 test reported success. Without this fix, memory leaks don't cause
1558 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1559 bugfix on 0.2.2.4-alpha.
1561 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1562 - Treat backtrace test failures as expected on BSD-derived systems
1563 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1564 (FreeBSD failures have been treated as expected since 18204 in
1565 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1567 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1568 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1569 bugfix on 0.3.0.1-alpha.
1572 Changes in version 0.3.4.10 - 2019-01-07
1573 Tor 0.3.4.9 is the second stable release in its series; it backports
1574 numerous fixes, including an important fix for relays, and for anyone
1575 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1578 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1579 2019. Some time between now and then, users should switch to the Tor
1580 0.3.5 series, which will receive long-term support until at least 1
1583 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1584 - Fix our usage of named groups when running as a TLS 1.3 client in
1585 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1586 running as a relay, which caused clients to fail to negotiate TLS
1587 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1590 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1591 - Always reactivate linked connections in the main loop so long as
1592 any linked connection has been active. Previously, connections
1593 serving directory information wouldn't get reactivated after the
1594 first chunk of data was sent (usually 32KB), which would prevent
1595 clients from bootstrapping. Fixes bug 28912; bugfix on
1596 0.3.4.1-alpha. Patch by "cypherpunks3".
1598 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1599 - Always show the configure and test logs, and upload them as build
1600 artifacts, when building for Windows using Appveyor CI.
1603 o Minor features (controller, backport from 0.3.5.1-alpha):
1604 - For purposes of CIRC_BW-based dropped cell detection, track half-
1605 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1606 bias check cells to arrive without counting it as dropped until
1607 either the END arrives, or the windows are empty. Closes
1610 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1611 - Replace the 150 fallbacks originally introduced in Tor
1612 0.3.3.1-alpha in January 2018 (of which ~115 were still
1613 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1614 removed) generated in December 2018. Closes ticket 24803.
1616 o Minor features (geoip):
1617 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1618 Country database. Closes ticket 28395.
1620 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1621 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1622 key export function from handling long labels. When this bug is
1623 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1624 version of OpenSSL without this bug when it becomes available.
1625 Closes ticket 28973.
1627 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1628 - Initialize a variable unconditionally in aes_new_cipher(), since
1629 some compilers cannot tell that we always initialize it before
1630 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1632 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1633 - Avoid a logging a BUG() stacktrace when closing connection held
1634 open because the write side is rate limited but not the read side.
1635 Now, the connection read side is simply shut down until Tor is
1636 able to flush the connection and close it. Fixes bug 27750; bugfix
1639 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1640 - Manually configure the zstd compiler options, when building using
1641 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1642 not come with a pkg-config file. Fixes bug 28454; bugfix
1644 - Stop using an external OpenSSL install, and stop installing MSYS2
1645 packages, when building using mingw on Appveyor Windows CI. Fixes
1646 bug 28399; bugfix on 0.3.4.1-alpha.
1648 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1649 - Explicitly specify the path to the OpenSSL library and do not
1650 download OpenSSL from Pacman, but instead use the library that is
1651 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1653 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1654 - When a user requests a group-readable DataDirectory, give it to
1655 them. Previously, when the DataDirectory and the CacheDirectory
1656 were the same, the default setting (0) for
1657 CacheDirectoryGroupReadable would override the setting for
1658 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1661 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1662 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1663 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1665 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1666 - Don't warn so loudly when Tor is unable to decode an onion
1667 descriptor. This can now happen as a normal use case if a client
1668 gets a descriptor with client authorization but the client is not
1669 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1671 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1672 - When deleting an ephemeral onion service (DEL_ONION), do not close
1673 any rendezvous circuits in order to let the existing client
1674 connections finish by themselves or closed by the application. The
1675 HS v2 is doing that already so now we have the same behavior for
1676 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1678 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1679 - Update relay descriptor on bandwidth changes only when the uptime
1680 is smaller than 24h, in order to reduce the efficiency of guard
1681 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1683 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1684 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1685 bugfix on 0.3.0.1-alpha.
1688 Changes in version 0.3.5.7 - 2019-01-07
1689 Tor 0.3.5.7 is the first stable release in its series; it includes
1690 compilation and portability fixes, and a fix for a severe problem
1691 affecting directory caches.
1693 The Tor 0.3.5 series includes several new features and performance
1694 improvements, including client authorization for v3 onion services,
1695 cleanups to bootstrap reporting, support for improved bandwidth-
1696 measurement tools, experimental support for NSS in place of OpenSSL,
1697 and much more. It also begins a full reorganization of Tor's code
1698 layout, for improved modularity and maintainability in the future.
1699 Finally, there is the usual set of performance improvements and
1700 bugfixes that we try to do in every release series.
1702 There are a couple of changes in the 0.3.5 that may affect
1703 compatibility. First, the default version for newly created onion
1704 services is now v3. Use the HiddenServiceVersion option if you want to
1705 override this. Second, some log messages related to bootstrapping have
1706 changed; if you use stem, you may need to update to the latest version
1707 so it will recognize them.
1709 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1710 will continue to patch major bugs in typical configurations of 0.3.5
1711 until at least 1 Feb 2022. (We do not plan to provide long-term
1712 support for embedding, Rust support, NSS support, running a directory
1713 authority, or unsupported platforms. For these, you will need to stick
1714 with the latest stable release.)
1716 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1717 since 0.3.4.9, see the ReleaseNotes file.
1719 o Major bugfixes (relay, directory):
1720 - Always reactivate linked connections in the main loop so long as
1721 any linked connection has been active. Previously, connections
1722 serving directory information wouldn't get reactivated after the
1723 first chunk of data was sent (usually 32KB), which would prevent
1724 clients from bootstrapping. Fixes bug 28912; bugfix on
1725 0.3.4.1-alpha. Patch by "cypherpunks3".
1727 o Minor features (compilation):
1728 - When possible, place our warning flags in a separate file, to
1729 avoid flooding verbose build logs. Closes ticket 28924.
1731 o Minor features (geoip):
1732 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1733 Country database. Closes ticket 29012.
1735 o Minor features (OpenSSL bug workaround):
1736 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1737 key export function from handling long labels. When this bug is
1738 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1739 version of OpenSSL without this bug when it becomes available.
1740 Closes ticket 28973.
1742 o Minor features (performance):
1743 - Remove about 96% of the work from the function that we run at
1744 startup to test our curve25519_basepoint implementation. Since
1745 this function has yet to find an actual failure, we now only run
1746 it for 8 iterations instead of 200. Based on our profile
1747 information, this change should save around 8% of our startup time
1748 on typical desktops, and may have a similar effect on other
1749 platforms. Closes ticket 28838.
1750 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1751 every startup. Doing this wasted time and cycles, especially on
1752 low-powered devices. Closes ticket 28851.
1754 o Minor bugfixes (compilation):
1755 - Fix compilation for Android by adding a missing header to
1756 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
1758 o Minor bugfixes (correctness):
1759 - Fix an unreached code path where we checked the value of
1760 "hostname" inside send_resolved_hostname_cell(). Previously, we
1761 used it before checking it; now we check it first. Fixes bug
1762 28879; bugfix on 0.1.2.7-alpha.
1764 o Minor bugfixes (testing):
1765 - Make sure that test_rebind.py actually obeys its timeout, even
1766 when it receives a large number of log messages. Fixes bug 28883;
1767 bugfix on 0.3.5.4-alpha.
1768 - Stop running stem's unit tests as part of "make test-stem", but
1769 continue to run stem's unit and online tests during "make test-
1770 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1772 o Minor bugfixes (windows services):
1773 - Make Tor start correctly as an NT service again: previously it was
1774 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
1776 o Code simplification and refactoring:
1777 - When parsing a port configuration, make it more obvious to static
1778 analyzer tools that we always initialize the address. Closes
1782 Changes in version 0.3.5.6-rc - 2018-12-18
1783 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
1784 It is the first release candidate in the 0.3.5.x series; if no further
1785 huge bugs are found, our next release may be the stable 0.3.5.x.
1787 o Minor features (continuous integration, Windows):
1788 - Always show the configure and test logs, and upload them as build
1789 artifacts, when building for Windows using Appveyor CI.
1792 o Minor features (fallback directory list):
1793 - Replace the 150 fallbacks originally introduced in Tor
1794 0.3.3.1-alpha in January 2018 (of which ~115 were still
1795 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1796 removed) generated in December 2018. Closes ticket 24803.
1798 o Minor features (geoip):
1799 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
1800 Country database. Closes ticket 28744.
1802 o Minor bugfixes (compilation):
1803 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
1804 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
1806 o Minor bugfixes (continuous integration, Windows):
1807 - Explicitly specify the path to the OpenSSL library and do not
1808 download OpenSSL from Pacman, but instead use the library that is
1809 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1811 o Minor bugfixes (onion service v3):
1812 - When deleting an ephemeral onion service (DEL_ONION), do not close
1813 any rendezvous circuits in order to let the existing client
1814 connections finish by themselves or closed by the application. The
1815 HS v2 is doing that already so now we have the same behavior for
1816 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1818 o Minor bugfixes (restart-in-process, boostrap):
1819 - Add missing resets of bootstrap tracking state when shutting down
1820 (regression caused by ticket 27169). Fixes bug 28524; bugfix
1823 o Minor bugfixes (testing):
1824 - Use a separate DataDirectory for the test_rebind script.
1825 Previously, this script would run using the default DataDirectory,
1826 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
1827 Patch from Taylor R Campbell.
1828 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1829 bugfix on 0.3.0.1-alpha.
1831 o Minor bugfixes (Windows):
1832 - Correctly identify Windows 8.1, Windows 10, and Windows Server
1833 2008 and later from their NT versions. Fixes bug 28096; bugfix on
1834 0.2.2.34; reported by Keifer Bly.
1835 - On recent Windows versions, the GetVersionEx() function may report
1836 an earlier Windows version than the running OS. To avoid user
1837 confusion, add "[or later]" to Tor's version string on affected
1838 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
1840 - Remove Windows versions that were never supported by the
1841 GetVersionEx() function. Stop duplicating the latest Windows
1842 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
1843 reported by Keifer Bly.
1846 - Increase logging and tag all log entries with timestamps in
1847 test_rebind.py. Provides diagnostics for issue 28229.
1849 o Code simplification and refactoring (shared random, dirauth):
1850 - Change many tor_assert() to use BUG() instead. The idea is to not
1851 crash a dirauth but rather scream loudly with a stacktrace and let
1852 it continue run. The shared random subsystem is very resilient and
1853 if anything wrong happens with it, at worst a non coherent value
1854 will be put in the vote and discarded by the other authorities.
1855 Closes ticket 19566.
1857 o Documentation (onion services):
1858 - Document in the man page that changing ClientOnionAuthDir value or
1859 adding a new file in the directory will not work at runtime upon
1860 sending a HUP if Sandbox 1. Closes ticket 28128.
1861 - Note in the man page that the only real way to fully revoke an
1862 onion service v3 client authorization is by restarting the tor
1863 process. Closes ticket 28275.
1866 Changes in version 0.3.5.5-alpha - 2018-11-16
1867 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
1868 including several that we hope to backport to older release series in
1871 o Major bugfixes (OpenSSL, portability):
1872 - Fix our usage of named groups when running as a TLS 1.3 client in
1873 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1874 running as a relay, which caused clients to fail to negotiate TLS
1875 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1878 o Minor features (geoip):
1879 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1880 Country database. Closes ticket 28395.
1882 o Minor bugfixes (compilation):
1883 - Initialize a variable unconditionally in aes_new_cipher(), since
1884 some compilers cannot tell that we always initialize it before
1885 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1887 o Minor bugfixes (connection, relay):
1888 - Avoid a logging a BUG() stacktrace when closing connection held
1889 open because the write side is rate limited but not the read side.
1890 Now, the connection read side is simply shut down until Tor is
1891 able to flush the connection and close it. Fixes bug 27750; bugfix
1894 o Minor bugfixes (continuous integration, Windows):
1895 - Manually configure the zstd compiler options, when building using
1896 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1897 not come with a pkg-config file. Fixes bug 28454; bugfix
1899 - Stop using an external OpenSSL install, and stop installing MSYS2
1900 packages, when building using mingw on Appveyor Windows CI. Fixes
1901 bug 28399; bugfix on 0.3.4.1-alpha.
1903 o Minor bugfixes (documentation):
1904 - Make Doxygen work again after the code movement in the 0.3.5
1905 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
1907 o Minor bugfixes (Linux seccomp2 sandbox):
1908 - Permit the "shutdown()" system call, which is apparently used by
1909 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1912 o Minor bugfixes (logging):
1913 - Stop talking about the Named flag in log messages. Clients have
1914 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1917 o Minor bugfixes (memory leaks):
1918 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1919 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1921 o Minor bugfixes (onion services):
1922 - On an intro point for a version 3 onion service, stop closing
1923 introduction circuits on an NACK. This lets the client decide
1924 whether to reuse the circuit or discard it. Previously, we closed
1925 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1926 0.3.2.1-alpha. Patch by Neel Chaunan.
1927 - When replacing a descriptor in the client cache, make sure to
1928 close all client introduction circuits for the old descriptor, so
1929 we don't end up with unusable leftover circuits. Fixes bug 27471;
1930 bugfix on 0.3.2.1-alpha.
1933 Changes in version 0.3.5.4-alpha - 2018-11-08
1934 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
1935 improves our continuous integration support. It continues our attempts
1936 to stabilize this alpha branch and build it into a foundation for an
1937 acceptable long-term-support release.
1939 o Major bugfixes (compilation, rust):
1940 - Rust tests can now build and run successfully with the
1941 --enable-fragile-hardening option enabled. Doing this currently
1942 requires the rust beta channel; it will be possible with stable
1943 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1944 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1946 o Major bugfixes (embedding, main loop):
1947 - When DisableNetwork becomes set, actually disable periodic events
1948 that are already enabled. (Previously, we would refrain from
1949 enabling new ones, but we would leave the old ones turned on.)
1950 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
1952 o Minor features (continuous integration):
1953 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
1955 - Add new CI job to Travis configuration to run stem-based
1956 integration tests. Closes ticket 27913.
1958 o Minor features (Windows, continuous integration):
1959 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1960 Appveyor's CI. Closes ticket 28318.
1962 o Minor bugfixes (C correctness, also in 0.3.4.9):
1963 - Avoid undefined behavior in an end-of-string check when parsing
1964 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1967 o Minor bugfixes (compilation):
1968 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
1969 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1971 o Minor bugfixes (compilation, OpenSolaris):
1972 - Fix compilation on OpenSolaris and its descendants by adding a
1973 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
1976 o Minor bugfixes (configuration):
1977 - Refuse to start with relative file paths and RunAsDaemon set
1978 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1981 o Minor bugfixes (directory authority, also in 0.3.4.9):
1982 - Log additional info when we get a relay that shares an ed25519 ID
1983 with a different relay, instead of a BUG() warning with a
1984 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
1986 o Minor bugfixes (onion service v3):
1987 - Build the service descriptor's signing key certificate before
1988 uploading, so we always have a fresh one: leaving no chances for
1989 it to expire service side. Fixes bug 27838; bugfix
1992 o Minor bugfixes (onion service v3, client authorization):
1993 - Fix an assert() when adding a client authorization for the first
1994 time and then sending a HUP signal to the service. Before that,
1995 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
1997 o Minor bugfixes (onion services):
1998 - Unless we have explicitly set HiddenServiceVersion, detect the
1999 onion service version and then look for invalid options.
2000 Previously, we did the reverse, but that broke existing configs
2001 which were pointed to a v2 service and had options like
2002 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
2003 0.3.5.1-alpha. Patch by Neel Chauhan.
2005 o Minor bugfixes (portability):
2006 - Make the OPE code (which is used for v3 onion services) run
2007 correctly on big-endian platforms. Fixes bug 28115; bugfix
2010 o Minor bugfixes (protover, rust):
2011 - Reject extra commas in version strings. Fixes bug 27197; bugfix
2014 o Minor bugfixes (relay shutdown, systemd):
2015 - Notify systemd of ShutdownWaitLength so it can be set to longer
2016 than systemd's TimeoutStopSec. In Tor's systemd service file, set
2017 TimeoutSec to 60 seconds to allow Tor some time to shut down.
2018 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
2020 o Minor bugfixes (rust, also in 0.3.4.9):
2021 - Fix a potential null dereference in protover_all_supported(). Add
2022 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2023 - Return a string that can be safely freed by C code, not one
2024 created by the rust allocator, in protover_all_supported(). Fixes
2025 bug 27740; bugfix on 0.3.3.1-alpha.
2027 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
2028 - Fix an API mismatch in the rust implementation of
2029 protover_compute_vote(). This bug could have caused crashes on any
2030 directory authorities running Tor with Rust (which we do not yet
2031 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2033 o Minor bugfixes (testing):
2034 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
2035 27968; bugfix on 0.3.5.1-alpha.
2037 o Minor bugfixes (testing, also in 0.3.4.9):
2038 - Treat backtrace test failures as expected on BSD-derived systems
2039 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2040 (FreeBSD failures have been treated as expected since 18204 in
2041 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2043 o Documentation (onion service manpage):
2044 - Improve HSv3 client authorization by making some options more
2045 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
2048 Changes in version 0.3.4.9 - 2018-11-02
2049 Tor 0.3.4.9 is the second stable release in its series; it backports
2050 numerous fixes, including a fix for a bandwidth management bug that
2051 was causing memory exhaustion on relays. Anyone running an earlier
2052 version of Tor 0.3.4.9 should upgrade.
2054 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
2055 - Fix compilation on ARM (and other less-used CPUs) when compiling
2056 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2058 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
2059 - Make sure Tor bootstraps and works properly if only the
2060 ControlPort is set. Prior to this fix, Tor would only bootstrap
2061 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2062 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2064 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
2065 - When our write bandwidth limit is exhausted, stop writing on the
2066 connection. Previously, we had a typo in the code that would make
2067 us stop reading instead, leading to relay connections being stuck
2068 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2071 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
2072 - Fix a use-after-free error that could be caused by passing Tor an
2073 impossible set of options that would fail during options_act().
2074 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2076 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
2077 - Don't do a distcheck with --disable-module-dirauth in Travis.
2078 Implements ticket 27252.
2079 - Only run one online rust build in Travis, to reduce network
2080 errors. Skip offline rust builds on Travis for Linux gcc, because
2081 they're redundant. Implements ticket 27252.
2082 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2083 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2084 Linux with default settings, because all the non-default builds
2085 use gcc on Linux. Implements ticket 27252.
2087 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
2088 - Use the Travis Homebrew addon to install packages on macOS during
2089 Travis CI. The package list is the same, but the Homebrew addon
2090 does not do a `brew update` by default. Implements ticket 27738.
2092 o Minor features (geoip):
2093 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2094 Country database. Closes ticket 27991.
2096 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
2097 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2098 difference algorithm for 32-bit Apple platforms. Previously, it
2099 would overflow when calculating the difference between two times
2100 more than 47 days apart. Fixes part of bug 27139; bugfix
2102 - Improve the precision of our 32-bit millisecond difference
2103 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2104 bugfix on 0.3.4.1-alpha.
2105 - Relax the tolerance on the mainloop/update_time_jumps test when
2106 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2109 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
2110 - Avoid undefined behavior in an end-of-string check when parsing
2111 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2114 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
2115 - Only install the necessary mingw packages during our appveyor
2116 builds. This change makes the build a little faster, and prevents
2117 a conflict with a preinstalled mingw openssl that appveyor now
2118 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2120 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2121 - Rewrite our assertion macros so that they no longer suppress the
2122 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2124 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2125 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2126 27464; bugfix on 0.3.4.1-alpha.
2128 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2129 - Log additional info when we get a relay that shares an ed25519 ID
2130 with a different relay, instead making a BUG() warning. Fixes bug
2131 27800; bugfix on 0.3.2.1-alpha.
2133 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2134 - Avoid a double-close when shutting down a stalled directory
2135 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2137 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2138 - Fix a bug warning when closing an HTTP tunnel connection due to an
2139 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2142 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2143 - Ensure circuitmux queues are empty before scheduling or sending
2144 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2146 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2147 - When the onion service directory can't be created or has the wrong
2148 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2151 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2152 - Close all SOCKS request (for the same .onion) if the newly fetched
2153 descriptor is unusable. Before that, we would close only the first
2154 one leaving the other hanging and let to time out by themselves.
2155 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2157 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2158 - When selecting a v3 rendezvous point, don't only look at the
2159 protover, but also check whether the curve25519 onion key is
2160 present. This way we avoid picking a relay that supports the v3
2161 rendezvous but for which we don't have the microdescriptor. Fixes
2162 bug 27797; bugfix on 0.3.2.1-alpha.
2164 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2165 - Reject protocol names containing bytes other than alphanumeric
2166 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2169 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2170 - Compute protover votes correctly in the rust version of the
2171 protover code. Previously, the protover rewrite in 24031 allowed
2172 repeated votes from the same voter for the same protocol version
2173 to be counted multiple times in protover_compute_vote(). Fixes bug
2174 27649; bugfix on 0.3.3.5-rc.
2175 - Reject protover names that contain invalid characters. Fixes bug
2176 27687; bugfix on 0.3.3.1-alpha.
2178 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2179 - protover_all_supported() would attempt to allocate up to 16GB on
2180 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2181 bugfix on 0.3.3.5-rc.
2183 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2184 - Fix an API mismatch in the rust implementation of
2185 protover_compute_vote(). This bug could have caused crashes on any
2186 directory authorities running Tor with Rust (which we do not yet
2187 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2189 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2190 - Fix a potential null dereference in protover_all_supported(). Add
2191 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2192 - Return a string that can be safely freed by C code, not one
2193 created by the rust allocator, in protover_all_supported(). Fixes
2194 bug 27740; bugfix on 0.3.3.1-alpha.
2196 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2197 - If a unit test running in a subprocess exits abnormally or with a
2198 nonzero status code, treat the test as having failed, even if the
2199 test reported success. Without this fix, memory leaks don't cause
2200 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2201 bugfix on 0.2.2.4-alpha.
2203 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2204 - Make the hs_service tests use the same time source when creating
2205 the introduction point and when testing it. Now tests work better
2206 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2209 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2210 - Treat backtrace test failures as expected on BSD-derived systems
2211 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2212 (FreeBSD failures have been treated as expected since 18204 in
2213 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2216 Changes in version 0.3.5.3-alpha - 2018-10-17
2217 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
2218 versions. One important fix for relays addresses a problem with rate-
2219 limiting code from back in 0.3.4.x: If the fix works out, we'll be
2220 backporting it soon. This release is still an alpha, but we hope it's
2221 getting closer and closer to stability.
2223 o Major features (onion services):
2224 - Version 3 onion services can now use the per-service
2225 HiddenServiceExportCircuitID option to differentiate client
2226 circuits. It communicates with the service by using the HAProxy
2227 protocol to assign virtual IP addresses to inbound client
2228 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
2230 o Major bugfixes (compilation):
2231 - Fix compilation on ARM (and other less-used CPUs) when compiling
2232 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2234 o Major bugfixes (initialization, crash):
2235 - Fix an assertion crash that would stop Tor from starting up if it
2236 tried to activate a periodic event too early. Fixes bug 27861;
2237 bugfix on 0.3.5.1-alpha.
2239 o Major bugfixes (mainloop, bootstrap):
2240 - Make sure Tor bootstraps and works properly if only the
2241 ControlPort is set. Prior to this fix, Tor would only bootstrap
2242 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2243 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2245 o Major bugfixes (relay):
2246 - When our write bandwidth limit is exhausted, stop writing on the
2247 connection. Previously, we had a typo in the code that would make
2248 us stop reading instead, leading to relay connections being stuck
2249 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2252 o Minor features (continuous integration):
2253 - Use the Travis Homebrew addon to install packages on macOS during
2254 Travis CI. The package list is the same, but the Homebrew addon
2255 does not do a `brew update` by default. Implements ticket 27738.
2256 - Report what program produced the mysterious core file that we
2257 occasionally see on Travis CI during make distcheck. Closes
2260 o Minor features (geoip):
2261 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2262 Country database. Closes ticket 27991.
2264 o Minor bugfixes (code safety):
2265 - Rewrite our assertion macros so that they no longer suppress the
2266 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2269 o Minor bugfixes (compilation):
2270 - Compile the ed25519-donna code with a correct declaration of
2271 crypto_strongest_rand(). Previously, we built it with one type,
2272 but linked it against another in the unit tests, which caused
2273 compilation failures with LTO enabled. This could have caused
2274 other undefined behavior in the tests. Fixes bug 27728; bugfix
2277 o Minor bugfixes (compilation, netbsd):
2278 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
2281 o Minor bugfixes (continuous integration, appveyor):
2282 - Install only the necessary mingw packages during our appveyor
2283 builds. This change makes the build a little faster, and prevents
2284 a conflict with a preinstalled mingw openssl that appveyor now
2285 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2287 o Minor bugfixes (directory permissions):
2288 - When a user requests a group-readable DataDirectory, give it to
2289 them. Previously, when the DataDirectory and the CacheDirectory
2290 were the same, the default setting (0) for
2291 CacheDirectoryGroupReadable would override the setting for
2292 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2295 o Minor bugfixes (memory leaks):
2296 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2297 bug 27893; bugfix on 0.3.2.1-alpha.
2299 o Minor bugfixes (networking):
2300 - In retry_listeners_ports(), make sure that we're removing a member
2301 of old_conns smartlist at most once. Fixes bug 27808; bugfix
2303 - Refrain from attempting socket rebinding when old and new
2304 listeners are in different address families. Fixes bug 27928;
2305 bugfix on 0.3.5.1-alpha.
2307 o Minor bugfixes (onion service v3):
2308 - Stop dumping a stack trace when trying to connect to an intro
2309 point without having a descriptor for it. Fixes bug 27774; bugfix
2311 - Don't warn so loudly when Tor is unable to decode an onion
2312 descriptor. This can now happen as a normal use case if a client
2313 gets a descriptor with client authorization but the client is not
2314 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
2315 - When selecting a v3 rendezvous point, don't only look at the
2316 protover, but also check whether the curve25519 onion key is
2317 present. This way we avoid picking a relay that supports the v3
2318 rendezvous but for which we don't have the microdescriptor. Fixes
2319 bug 27797; bugfix on 0.3.2.1-alpha.
2321 o Minor bugfixes (protover):
2322 - Reject protocol names containing bytes other than alphanumeric
2323 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2326 o Minor bugfixes (testing):
2327 - Make the hs_service tests use the same time source when creating
2328 the introduction point and when testing it. Now tests work better
2329 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2331 - In test_rebind.py, check if the Python version is in the supported
2332 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
2334 o Code simplification and refactoring:
2335 - Divide more large Tor source files -- especially ones that span
2336 multiple areas of functionality -- into smaller parts, including
2337 onion.c and main.c. Closes ticket 26747.
2338 - Divide the "routerparse.c" module into separate modules for each
2339 group of parsed objects. Closes ticket 27924.
2340 - Move protover_rust.c to the same place protover.c was moved to.
2341 Closes ticket 27814.
2342 - Split directory.c into separate pieces for client, server, and
2343 common functionality. Closes ticket 26744.
2344 - Split the non-statistics-related parts from the rephist.c and
2345 geoip.c modules. Closes ticket 27892.
2346 - Split the router.c file into relay-only and shared components, to
2347 help with future modularization. Closes ticket 27864.
2350 - In the tor-resolve(1) manpage, fix the reference to socks-
2351 extensions.txt by adding a web URL. Resolves ticket 27853.
2352 - Mention that we require Python to be 2.7 or newer for some
2353 integration tests that we ship with Tor. Resolves ticket 27677.
2356 Changes in version 0.3.5.2-alpha - 2018-09-21
2357 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
2358 that made Tor think it had run out of sockets. Anybody running a relay
2359 or an onion service on 0.3.5.1-alpha should upgrade.
2361 o Major bugfixes (relay bandwidth statistics):
2362 - When we close relayed circuits, report the data in the circuit
2363 queues as being written in our relay bandwidth stats. This
2364 mitigates guard discovery and other attacks that close circuits
2365 for the explicit purpose of noticing this discrepancy in
2366 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
2368 o Major bugfixes (socket accounting):
2369 - In our socket accounting code, count a socket as closed even when
2370 it is closed indirectly by the TLS layer. Previously, we would
2371 count these sockets as still in use, and incorrectly believe that
2372 we had run out of sockets. Fixes bug 27795; bugfix
2375 o Minor bugfixes (32-bit OSX and iOS, timing):
2376 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2377 difference algorithm for 32-bit Apple platforms. Previously, it
2378 would overflow when calculating the difference between two times
2379 more than 47 days apart. Fixes part of bug 27139; bugfix
2381 - Improve the precision of our 32-bit millisecond difference
2382 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2383 bugfix on 0.3.4.1-alpha.
2384 - Relax the tolerance on the mainloop/update_time_jumps test when
2385 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2388 o Minor bugfixes (onion service v3):
2389 - Close all SOCKS request (for the same .onion) if the newly fetched
2390 descriptor is unusable. Before that, we would close only the first
2391 one leaving the other hanging and let to time out by themselves.
2392 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2394 o Minor bugfixes (memory leak):
2395 - Fix an unlikely memory leak when trying to read a private key from
2396 a ridiculously large file. Fixes bug 27764; bugfix on
2397 0.3.5.1-alpha. This is CID 1439488.
2399 o Minor bugfixes (NSS):
2400 - Correctly detect failure to open a dummy TCP socket when stealing
2401 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
2404 o Minor bugfixes (rust):
2405 - protover_all_supported() would attempt to allocate up to 16GB on
2406 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2407 bugfix on 0.3.3.5-rc.
2409 o Minor bugfixes (testing):
2410 - Revise the "conditionvar_timeout" test so that it succeeds even on
2411 heavily loaded systems where the test threads are not scheduled
2412 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2414 o Code simplification and refactoring:
2415 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2416 Closes ticket 27799.
2419 Changes in version 0.3.5.1-alpha - 2018-09-18
2420 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
2421 client authorization for modern (v3) onion services, improves
2422 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
2423 support for NSS in place of OpenSSL, and much more.
2425 o Major features (onion services, UI change):
2426 - For a newly created onion service, the default version is now 3.
2427 Tor still supports existing version 2 services, but the operator
2428 now needs to set "HiddenServiceVersion 2" in order to create a new
2429 version 2 service. For existing services, Tor now learns the
2430 version by reading the key file. Closes ticket 27215.
2432 o Major features (relay, UI change):
2433 - Relays no longer run as exits by default. If the "ExitRelay"
2434 option is auto (or unset), and no exit policy is specified with
2435 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
2436 Previously in this case, we allowed exit traffic and logged a
2437 warning message. Closes ticket 21530. Patch by Neel Chauhan.
2438 - Tor now validates that the ContactInfo config option is valid UTF-
2439 8 when parsing torrc. Closes ticket 27428.
2441 o Major features (bootstrap):
2442 - Don't report directory progress until after a connection to a
2443 relay or bridge has succeeded. Previously, we'd report 80%
2444 progress based on cached directory information when we couldn't
2445 even connect to the network. Closes ticket 27169.
2447 o Major features (new code layout):
2448 - Nearly all of Tor's source code has been moved around into more
2449 logical places. The "common" directory is now divided into a set
2450 of libraries in "lib", and files in the "or" directory have been
2451 split into "core" (logic absolutely needed for onion routing),
2452 "feature" (independent modules in Tor), and "app" (to configure
2453 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
2454 more information. Closes ticket 26481.
2456 This refactoring is not complete: although the libraries have been
2457 refactored to be acyclic, the main body of Tor is still too
2458 interconnected. We will attempt to improve this in the future.
2460 o Major features (onion services v3):
2461 - Implement onion service client authorization at the descriptor
2462 level: only authorized clients can decrypt a service's descriptor
2463 to find out how to contact it. A new torrc option was added to
2464 control this client side: ClientOnionAuthDir <path>. On the
2465 service side, if the "authorized_clients/" directory exists in the
2466 onion service directory path, client configurations are read from
2467 the files within. See the manpage for more details. Closes ticket
2468 27547. Patch done by Suphanat Chunhapanya (haxxpop).
2469 - Improve revision counter generation in next-gen onion services.
2470 Onion services can now scale by hosting multiple instances on
2471 different hosts without synchronization between them, which was
2472 previously impossible because descriptors would get rejected by
2473 HSDirs. Addresses ticket 25552.
2475 o Major features (portability, cryptography, experimental, TLS):
2476 - Tor now has the option to compile with the NSS library instead of
2477 OpenSSL. This feature is experimental, and we expect that bugs may
2478 remain. It is mainly intended for environments where Tor's
2479 performance is not CPU-bound, and where NSS is already known to be
2480 installed. To try it out, configure Tor with the --enable-nss
2481 flag. Closes tickets 26631, 26815, and 26816.
2483 If you are experimenting with this option and using an old cached
2484 consensus, Tor may fail to start. To solve this, delete your
2485 "cached-consensus" and "cached-microdesc-consensus" files,
2486 (if present), and restart Tor.
2488 o Major bugfixes (directory authority):
2489 - Actually check that the address we get from DirAuthority
2490 configuration line is valid IPv4. Explicitly disallow DirAuthority
2491 address to be a DNS hostname. Fixes bug 26488; bugfix
2494 o Major bugfixes (restart-in-process):
2495 - Fix a use-after-free error that could be caused by passing Tor an
2496 impossible set of options that would fail during options_act().
2497 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2499 o Minor features (admin tools):
2500 - Add a new --key-expiration option to print the expiration date of
2501 the signing cert in an ed25519_signing_cert file. Resolves
2504 o Minor features (build):
2505 - If you pass the "--enable-pic" option to configure, Tor will try
2506 to tell the compiler to build position-independent code suitable
2507 to link into a dynamic library. (The default remains -fPIE, for
2508 code suitable for a relocatable executable.) Closes ticket 23846.
2510 o Minor features (code correctness, testing):
2511 - Tor's build process now includes a "check-includes" make target to
2512 verify that no module of Tor relies on any headers from a higher-
2513 level module. We hope to use this feature over time to help
2514 refactor our codebase. Closes ticket 26447.
2516 o Minor features (code layout):
2517 - We have a new "lowest-level" error-handling API for use by code
2518 invoked from within the logging module. With this interface, the
2519 logging code is no longer at risk of calling into itself if a
2520 failure occurs while it is trying to log something. Closes
2523 o Minor features (compilation):
2524 - Tor's configure script now supports a --with-malloc= option to
2525 select your malloc implementation. Supported options are
2526 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
2527 default). Addresses part of ticket 20424. Based on a patch from
2530 o Minor features (config):
2531 - The "auto" keyword in torrc is now case-insensitive. Closes
2534 o Minor features (continuous integration):
2535 - Don't do a distcheck with --disable-module-dirauth in Travis.
2536 Implements ticket 27252.
2537 - Install libcap-dev and libseccomp2-dev so these optional
2538 dependencies get tested on Travis CI. Closes ticket 26560.
2539 - Only run one online rust build in Travis, to reduce network
2540 errors. Skip offline rust builds on Travis for Linux gcc, because
2541 they're redundant. Implements ticket 27252.
2542 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2543 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2544 Linux with default settings, because all the non-default builds
2545 use gcc on Linux. Implements ticket 27252.
2547 o Minor features (controller):
2548 - Emit CIRC_BW events as soon as we detect that we processed an
2549 invalid or otherwise dropped cell on a circuit. This allows
2550 vanguards and other controllers to react more quickly to dropped
2551 cells. Closes ticket 27678.
2552 - For purposes of CIRC_BW-based dropped cell detection, track half-
2553 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2554 bias check cells to arrive without counting it as dropped until
2555 either the END arrives, or the windows are empty. Closes
2557 - Implement a 'GETINFO md/all' controller command to enable getting
2558 all known microdescriptors. Closes ticket 8323.
2559 - The GETINFO command now support an "uptime" argument, to return
2560 Tor's uptime in seconds. Closes ticket 25132.
2562 o Minor features (denial-of-service avoidance):
2563 - Make our OOM handler aware of the DNS cache so that it doesn't
2564 fill up the memory. This check is important for our DoS mitigation
2565 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2567 o Minor features (development):
2568 - Tor's makefile now supports running the "clippy" Rust style tool
2569 on our Rust code. Closes ticket 22156.
2571 o Minor features (directory authority):
2572 - There is no longer an artificial upper limit on the length of
2573 bandwidth lines. Closes ticket 26223.
2574 - When a bandwidth file is used to obtain the bandwidth measurements,
2575 include this bandwidth file headers in the votes. Closes
2577 - Improved support for networks with only a single authority or a
2578 single fallback directory. Patch from Gabriel Somlo. Closes
2581 o Minor features (embedding API):
2582 - The Tor controller API now supports a function to launch Tor with
2583 a preconstructed owning controller FD, so that embedding
2584 applications don't need to manage controller ports and
2585 authentication. Closes ticket 24204.
2586 - The Tor controller API now has a function that returns the name
2587 and version of the backend implementing the API. Closes
2590 o Minor features (geoip):
2591 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2592 Country database. Closes ticket 27631.
2594 o Minor features (memory management):
2595 - Get Libevent to use the same memory allocator as Tor, by calling
2596 event_set_mem_functions() during initialization. Resolves
2599 o Minor features (memory usage):
2600 - When not using them, store legacy TAP public onion keys in DER-
2601 encoded format, rather than as expanded public keys. This should
2602 save several megabytes on typical clients. Closes ticket 27246.
2604 o Minor features (OpenSSL):
2605 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2606 than our own. Resolves ticket 19979.
2608 o Minor features (Rust, code quality):
2609 - Improve rust code quality in the rust protover implementation by
2610 making it more idiomatic. Includes changing an internal API to
2611 take &str instead of &String. Closes ticket 26492.
2613 o Minor features (testing):
2614 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2615 chutney. Implements ticket 27211.
2617 o Minor features (tor-resolve):
2618 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2619 Side-effect of the refactoring for ticket 26526.
2621 o Minor features (UI):
2622 - Log each included configuration file or directory as we read it,
2623 to provide more visibility about where Tor is reading from. Patch
2624 from Unto Sten; closes ticket 27186.
2625 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2626 Closes ticket 26703.
2628 o Minor bugfixes (bootstrap):
2629 - Try harder to get descriptors in non-exit test networks, by using
2630 the mid weight for the third hop when there are no exits. Fixes
2631 bug 27237; bugfix on 0.2.6.2-alpha.
2633 o Minor bugfixes (C correctness):
2634 - Avoid casting smartlist index to int implicitly, as it may trigger
2635 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2636 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2637 - Use time_t for all values in
2638 predicted_ports_prediction_time_remaining(). Rework the code that
2639 computes difference between durations/timestamps. Fixes bug 27165;
2640 bugfix on 0.3.1.1-alpha.
2642 o Minor bugfixes (client, memory usage):
2643 - When not running as a directory cache, there is no need to store
2644 the text of the current consensus networkstatus in RAM.
2645 Previously, however, clients would store it anyway, at a cost of
2646 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2649 o Minor bugfixes (client, reachableaddresses):
2650 - Instead of adding a "reject *:*" line to ReachableAddresses when
2651 loading the configuration, add one to the policy after parsing it
2652 in parse_reachable_addresses(). This prevents extra "reject *.*"
2653 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2654 0.1.1.5-alpha. Patch by Neel Chauhan.
2656 o Minor bugfixes (code quality):
2657 - Rename sandbox_getaddrinfo() and other functions to no longer
2658 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2659 bugfix on 0.2.7.1-alpha.
2661 o Minor bugfixes (configuration, Onion Services):
2662 - In rend_service_parse_port_config(), disallow any input to remain
2663 after address-port pair was parsed. This will catch address and
2664 port being whitespace-separated by mistake of the user. Fixes bug
2665 27044; bugfix on 0.2.9.10.
2667 o Minor bugfixes (continuous integration):
2668 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2669 27464; bugfix on 0.3.4.1-alpha.
2671 o Minor bugfixes (controller):
2672 - Consider all routerinfo errors other than "not a server" to be
2673 transient for the purpose of "GETINFO exit-policy/*" controller
2674 request. Print stacktrace in the unlikely case of failing to
2675 recompute routerinfo digest. Fixes bug 27034; bugfix
2678 o Minor bugfixes (directory connection shutdown):
2679 - Avoid a double-close when shutting down a stalled directory
2680 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2682 o Minor bugfixes (HTTP tunnel):
2683 - Fix a bug warning when closing an HTTP tunnel connection due to an
2684 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2687 o Minor bugfixes (ipv6):
2688 - In addrs_in_same_network_family(), we choose the subnet size based
2689 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2690 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2691 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2693 o Minor bugfixes (logging):
2694 - As a precaution, do an early return from log_addr_has_changed() if
2695 Tor is running as client. Also, log a stack trace for debugging as
2696 this function should only be called when Tor runs as server. Fixes
2697 bug 26892; bugfix on 0.1.1.9-alpha.
2698 - Refrain from mentioning bug 21018 in the logs, as it is already
2699 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2701 o Minor bugfixes (logging, documentation):
2702 - When SafeLogging is enabled, scrub IP address in
2703 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2704 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2705 bug 26882; bugfix on 0.2.4.10-alpha.
2707 o Minor bugfixes (netflow padding):
2708 - Ensure circuitmux queues are empty before scheduling or sending
2709 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2711 o Minor bugfixes (onion service v2):
2712 - Log at level "info", not "warning", in the case that we do not
2713 have a consensus when a .onion request comes in. This can happen
2714 normally while bootstrapping. Fixes bug 27040; bugfix
2717 o Minor bugfixes (onion service v3):
2718 - When the onion service directory can't be created or has the wrong
2719 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2722 o Minor bugfixes (OS compatibility):
2723 - Properly handle configuration changes that move a listener to/from
2724 wildcard IP address. If the first attempt to bind a socket fails,
2725 close the old listener and try binding the socket again. Fixes bug
2726 17873; bugfix on 0.0.8pre-1.
2728 o Minor bugfixes (performance)::
2729 - Rework node_is_a_configured_bridge() to no longer call
2730 node_get_all_orports(), which was performing too many memory
2731 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2733 o Minor bugfixes (relay statistics):
2734 - Update relay descriptor on bandwidth changes only when the uptime
2735 is smaller than 24h, in order to reduce the efficiency of guard
2736 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2738 o Minor bugfixes (relays):
2739 - Consider the fact that we'll be making direct connections to our
2740 entry and guard nodes when computing the fraction of nodes that
2741 have their descriptors. Also, if we are using bridges and there is
2742 at least one bridge with a full descriptor, treat the fraction of
2743 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2744 Patch by Neel Chauhan.
2745 - Update the message logged on relays when DirCache is disabled.
2746 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2747 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2749 o Minor bugfixes (rust, protover):
2750 - Compute protover votes correctly in the rust version of the
2751 protover code. Previously, the protover rewrite in 24031 allowed
2752 repeated votes from the same voter for the same protocol version
2753 to be counted multiple times in protover_compute_vote(). Fixes bug
2754 27649; bugfix on 0.3.3.5-rc.
2755 - Reject protover names that contain invalid characters. Fixes bug
2756 27687; bugfix on 0.3.3.1-alpha.
2758 o Minor bugfixes (testing):
2759 - Fix two unit tests to work when HOME environment variable is not
2760 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2761 - If a unit test running in a subprocess exits abnormally or with a
2762 nonzero status code, treat the test as having failed, even if the
2763 test reported success. Without this fix, memory leaks don't cause
2764 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2765 bugfix on 0.2.2.4-alpha.
2766 - When logging a version mismatch in our openssl_version tests,
2767 report the actual offending version strings. Fixes bug 26152;
2768 bugfix on 0.2.9.1-alpha.
2769 - Fix forking tests on Windows when there is a space somewhere in
2770 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2772 o Code simplification and refactoring:
2773 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2774 longer needed. Closes ticket 26502.
2775 - Include paths to header files within Tor are now qualified by
2776 directory within the top-level src directory.
2777 - Many structures have been removed from the centralized "or.h"
2778 header, and moved into their own headers. This will allow us to
2779 reduce the number of places in the code that rely on each
2780 structure's contents and layout. Closes ticket 26383.
2781 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2782 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2783 removed as part of the 26481 refactor. Closes ticket 27467.
2784 - Rework Tor SOCKS server code to use Trunnel and benefit from
2785 autogenerated functions for parsing and generating SOCKS wire
2786 format. New implementation is cleaner, more maintainable and
2787 should be less prone to heartbleed-style vulnerabilities.
2788 Implements a significant fraction of ticket 3569.
2789 - Split sampled_guards_update_from_consensus() and
2790 select_entry_guard_for_circuit() into subfunctions. In
2791 entry_guards_update_primary() unite three smartlist enumerations
2792 into one and move smartlist comparison code out of the function.
2793 Closes ticket 21349.
2794 - Tor now assumes that you have standards-conformant stdint.h and
2795 inttypes.h headers when compiling. Closes ticket 26626.
2796 - Unify our bloom filter logic. Previously we had two copies of this
2797 code: one for routerlist filtering, and one for address set
2798 calculations. Closes ticket 26510.
2799 - Use the simpler strcmpstart() helper in
2800 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2802 - Utility functions that can perform a DNS lookup are now wholly
2803 separated from those that can't, in separate headers and C
2804 modules. Closes ticket 26526.
2807 - Copy paragraph and URL to Tor's code of conduct document from
2808 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2809 - Remove old instructions from INSTALL document. Closes ticket 26588.
2810 - Warn users that they should not include MyFamily line(s) in their
2811 torrc when running Tor bridge. Closes ticket 26908.
2814 - Tor no longer supports building with the dmalloc library. For
2815 debugging memory issues, we suggest using gperftools or msan
2816 instead. Closes ticket 26426.
2817 - Tor no longer attempts to run on Windows environments without the
2818 GetAdaptersAddresses() function. This function has existed since
2819 Windows XP, which is itself already older than we support.
2820 - Remove Tor2web functionality for version 2 onion services. The
2821 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2822 (This feature was never shipped in vanilla Tor and it was only
2823 possible to use this feature by building the support at compile
2824 time. Tor2webMode is not implemented for version 3 onion services.)
2825 Closes ticket 26367.
2828 Changes in version 0.2.9.17 - 2018-09-10
2829 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
2831 o Minor features (compatibility, backport from 0.3.4.8):
2832 - Tell OpenSSL to maintain backward compatibility with previous
2833 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2834 ciphers are disabled by default. Closes ticket 27344.
2836 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2837 - Enable macOS builds in our Travis CI configuration. Closes
2839 - Install libcap-dev and libseccomp2-dev so these optional
2840 dependencies get tested on Travis CI. Closes ticket 26560.
2841 - Run asciidoc during Travis CI. Implements ticket 27087.
2842 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2844 o Minor features (geoip):
2845 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2846 Country database. Closes ticket 27089.
2848 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2849 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2850 tell the compiler not to include the system malloc implementation.
2851 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2853 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2854 - Silence a spurious compiler warning on the GetAdaptersAddresses
2855 function pointer cast. This issue is already fixed by 26481 in
2856 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2857 bugfix on 0.2.3.11-alpha.
2858 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2859 supported, and always fails. Some compilers warn about the
2860 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2863 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2864 - Don't link or search for pthreads when building for Windows, even
2865 if we are using build environment (like mingw) that provides a
2866 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2868 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2869 - Skip a pair of unreliable key generation tests on Windows, until
2870 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2871 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2873 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2874 - Pass the module flags to distcheck configure, and log the flags
2875 before running configure. (Backported to 0.2.9 and later as a
2876 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2878 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2879 - When a Travis build fails, and showing a log fails, keep trying to
2880 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2881 - When we use echo in Travis, don't pass a --flag as the first
2882 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2884 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2885 - When voting for recommended versions, make sure that all of the
2886 versions are well-formed and parsable. Fixes bug 26485; bugfix
2889 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2890 - Fix a bug in out sandboxing rules for the openat() syscall.
2891 Previously, no openat() call would be permitted, which would break
2892 filesystem operations on recent glibc versions. Fixes bug 25440;
2893 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2895 o Minor bugfixes (onion services, backport from 0.3.4.8):
2896 - Silence a spurious compiler warning in
2897 rend_client_send_introduction(). Fixes bug 27463; bugfix
2900 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2901 - Log a protocol warning when single onion services or Tor2web clients
2902 fail to authenticate direct connections to relays.
2903 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2905 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2906 - Disable core dumps in test_bt.sh, to avoid failures in "make
2907 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2909 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2910 - Before running make test-network-all, delete old logs and test
2911 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2914 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2915 - Our "tortls/cert_matches_key" unit test no longer relies on
2916 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2917 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2918 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2920 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2921 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2922 27185; bugfix on 0.2.2.2-alpha.
2925 Changes in version 0.3.2.12 - 2018-09-10
2926 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2928 o Minor features (compatibility, backport from 0.3.4.8):
2929 - Tell OpenSSL to maintain backward compatibility with previous
2930 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2931 ciphers are disabled by default. Closes ticket 27344.
2933 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2934 - Enable macOS builds in our Travis CI configuration. Closes
2936 - Install libcap-dev and libseccomp2-dev so these optional
2937 dependencies get tested on Travis CI. Closes ticket 26560.
2938 - Run asciidoc during Travis CI. Implements ticket 27087.
2939 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2941 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2942 - Use cargo cache in our Travis CI configuration. Closes
2945 o Minor features (controller, backport from 0.3.4.6-rc):
2946 - The control port now exposes the list of HTTPTunnelPorts and
2947 ExtOrPorts via GETINFO net/listeners/httptunnel and
2948 net/listeners/extor respectively. Closes ticket 26647.
2950 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2951 - Authorities no longer vote to make the subprotocol version
2952 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2953 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2955 o Minor features (geoip):
2956 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2957 Country database. Closes ticket 27089.
2959 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2960 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2961 tell the compiler not to include the system malloc implementation.
2962 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2963 - Don't try to use a pragma to temporarily disable the
2964 -Wunused-const-variable warning if the compiler doesn't support
2965 it. Fixes bug 26785; bugfix on 0.3.2.11.
2967 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2968 - Silence a spurious compiler warning on the GetAdaptersAddresses
2969 function pointer cast. This issue is already fixed by 26481 in
2970 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2971 bugfix on 0.2.3.11-alpha.
2972 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2973 supported, and always fails. Some compilers warn about the
2974 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2977 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2978 - Don't link or search for pthreads when building for Windows, even
2979 if we are using build environment (like mingw) that provides a
2980 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2982 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2983 - Skip a pair of unreliable key generation tests on Windows, until
2984 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2985 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2987 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2988 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2989 - Pass the module flags to distcheck configure, and log the flags
2990 before running configure. (Backported to 0.2.9 and later as a
2991 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2993 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2994 - When a Travis build fails, and showing a log fails, keep trying to
2995 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2996 - When we use echo in Travis, don't pass a --flag as the first
2997 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2999 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3000 - When voting for recommended versions, make sure that all of the
3001 versions are well-formed and parsable. Fixes bug 26485; bugfix
3004 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3005 - Fix a bug in out sandboxing rules for the openat() syscall.
3006 Previously, no openat() call would be permitted, which would break
3007 filesystem operations on recent glibc versions. Fixes bug 25440;
3008 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3010 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3011 - Improve the log message when connection initiators fail to
3012 authenticate direct connections to relays. Fixes bug 26927; bugfix
3015 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3016 - Fix bug that causes services to not ever rotate their descriptors
3017 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3020 o Minor bugfixes (onion services, backport from 0.3.4.8):
3021 - Silence a spurious compiler warning in
3022 rend_client_send_introduction(). Fixes bug 27463; bugfix
3025 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3026 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3028 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3029 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3030 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3031 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3033 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3034 - Log a protocol warning when single onion services or Tor2web clients
3035 fail to authenticate direct connections to relays.
3036 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3038 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3039 - Disable core dumps in test_bt.sh, to avoid failures in "make
3040 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3042 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3043 - When running make test-network-all, use the mixed+hs-v2 network.
3044 (A previous fix to chutney removed v3 onion services from the
3045 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3046 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3047 - Before running make test-network-all, delete old logs and test
3048 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3051 o Minor bugfixes (testing, openssl compatibility):
3052 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
3053 internals. Previously, it relied on unsupported OpenSSL behavior in
3054 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
3055 bugfix on 0.2.5.1-alpha.
3057 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3058 - Our "tortls/cert_matches_key" unit test no longer relies on
3059 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3060 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3061 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3063 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3064 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3065 27185; bugfix on 0.2.2.2-alpha.
3068 Changes in version 0.3.3.10 - 2018-09-10
3069 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
3071 o Minor features (bug workaround, backport from 0.3.4.7-rc):
3072 - Compile correctly on systems that provide the C11 stdatomic.h
3073 header, but where C11 atomic functions don't actually compile.
3074 Closes ticket 26779; workaround for Debian issue 903709.
3076 o Minor features (compatibility, backport from 0.3.4.8):
3077 - Tell OpenSSL to maintain backward compatibility with previous
3078 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3079 ciphers are disabled by default. Closes ticket 27344.
3081 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3082 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3083 - Enable macOS builds in our Travis CI configuration. Closes
3085 - Install libcap-dev and libseccomp2-dev so these optional
3086 dependencies get tested on Travis CI. Closes ticket 26560.
3087 - Run asciidoc during Travis CI. Implements ticket 27087.
3088 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3090 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3091 - Use cargo cache in our Travis CI configuration. Closes
3094 o Minor features (controller, backport from 0.3.4.6-rc):
3095 - The control port now exposes the list of HTTPTunnelPorts and
3096 ExtOrPorts via GETINFO net/listeners/httptunnel and
3097 net/listeners/extor respectively. Closes ticket 26647.
3099 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3100 - Authorities no longer vote to make the subprotocol version
3101 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3102 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3104 o Minor features (geoip):
3105 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3106 Country database. Closes ticket 27089.
3108 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3109 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3110 tell the compiler not to include the system malloc implementation.
3111 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3112 - Don't try to use a pragma to temporarily disable the
3113 -Wunused-const-variable warning if the compiler doesn't support
3114 it. Fixes bug 26785; bugfix on 0.3.2.11.
3116 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3117 - Silence a spurious compiler warning on the GetAdaptersAddresses
3118 function pointer cast. This issue is already fixed by 26481 in
3119 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3120 bugfix on 0.2.3.11-alpha.
3121 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3122 supported, and always fails. Some compilers warn about the
3123 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3126 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3127 - Don't link or search for pthreads when building for Windows, even
3128 if we are using build environment (like mingw) that provides a
3129 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3131 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3132 - Skip a pair of unreliable key generation tests on Windows, until
3133 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3134 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3136 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3137 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3138 - Pass the module flags to distcheck configure, and log the flags
3139 before running configure. (Backported to 0.2.9 and later as a
3140 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3142 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3143 - When a Travis build fails, and showing a log fails, keep trying to
3144 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3145 - When we use echo in Travis, don't pass a --flag as the first
3146 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3148 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3149 - When voting for recommended versions, make sure that all of the
3150 versions are well-formed and parsable. Fixes bug 26485; bugfix
3153 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
3154 - Always call tor_free_all() when leaving tor_run_main(). When we
3155 did not, restarting tor in-process would cause an assertion
3156 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3158 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3159 - Fix a bug in our sandboxing rules for the openat() syscall.
3160 Previously, no openat() call would be permitted, which would break
3161 filesystem operations on recent glibc versions. Fixes bug 25440;
3162 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3164 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3165 - Improve the log message when connection initiators fail to
3166 authenticate direct connections to relays. Fixes bug 26927; bugfix
3169 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3170 - Fix bug that causes services to not ever rotate their descriptors
3171 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3174 o Minor bugfixes (onion services, backport from 0.3.4.8):
3175 - Silence a spurious compiler warning in
3176 rend_client_send_introduction(). Fixes bug 27463; bugfix
3179 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
3180 - Work around two different bugs in the OS X 10.10 and later SDKs
3181 that would prevent us from successfully targeting earlier versions
3182 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3184 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
3185 - Fix compilation of the unit tests on GNU/Hurd, which does not
3186 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3189 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3190 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3192 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3193 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3194 - Protover parsing was accepting the presence of whitespace in
3195 version strings, which the C implementation would choke on, e.g.
3196 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3197 - Protover parsing was ignoring a 2nd hyphen and everything after
3198 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3200 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3201 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3202 - cd to ${abs_top_builddir}/src/rust before running cargo in
3203 src/test/test_rust.sh. This makes the working directory consistent
3204 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3206 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3207 - Log a protocol warning when single onion services or Tor2web clients
3208 fail to authenticate direct connections to relays.
3209 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3211 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3212 - Disable core dumps in test_bt.sh, to avoid failures in "make
3213 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3215 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3216 - When running make test-network-all, use the mixed+hs-v2 network.
3217 (A previous fix to chutney removed v3 onion services from the
3218 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3219 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3220 - Before running make test-network-all, delete old logs and test
3221 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3224 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3225 - Our "tortls/cert_matches_key" unit test no longer relies on
3226 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3227 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3228 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3230 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3231 - Stop sending ed25519 link specifiers in v3 onion service introduce
3232 cells and descriptors, when the rendezvous or introduction point
3233 doesn't support ed25519 link authentication. Fixes bug 26627;
3234 bugfix on 0.3.2.4-alpha.
3236 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3237 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3238 27185; bugfix on 0.2.2.2-alpha.
3241 Changes in version 0.3.4.8 - 2018-09-10
3242 Tor 0.3.4.8 is the first stable release in its series; it includes
3243 compilation and portability fixes.
3245 The Tor 0.3.4 series includes improvements for running Tor in
3246 low-power and embedded environments, which should help performance in
3247 general. We've begun work on better modularity, and included preliminary
3248 changes on the directory authority side to accommodate a new bandwidth
3249 measurement system. We've also integrated more continuous-integration
3250 systems into our development process, and made corresponding changes to
3251 Tor's testing infrastructure. Finally, we've continued to refine
3252 our anti-denial-of-service code.
3254 Below are the changes since 0.3.4.7-rc. For a complete list of changes
3255 since 0.3.3.9, see the ReleaseNotes file.
3257 o Minor features (compatibility):
3258 - Tell OpenSSL to maintain backward compatibility with previous
3259 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3260 ciphers are disabled by default. Closes ticket 27344.
3262 o Minor features (continuous integration):
3263 - Log the compiler path and version during Appveyor builds.
3264 Implements ticket 27449.
3265 - Show config.log and test-suite.log after failed Appveyor builds.
3266 Also upload the zipped full logs as a build artifact. Implements
3269 o Minor bugfixes (compilation):
3270 - Silence a spurious compiler warning on the GetAdaptersAddresses
3271 function pointer cast. This issue is already fixed by 26481 in
3272 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3273 bugfix on 0.2.3.11-alpha.
3274 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3275 supported, and always fails. Some compilers warn about the
3276 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3279 o Minor bugfixes (continuous integration):
3280 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
3281 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
3282 Executables compiled for 64-bit Windows with this version of gcc
3283 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
3284 27460; bugfix on 0.3.4.1-alpha.
3285 - When a Travis build fails, and showing a log fails, keep trying to
3286 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3287 - When we use echo in Travis, don't pass a --flag as the first
3288 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3290 o Minor bugfixes (onion services):
3291 - Silence a spurious compiler warning in
3292 rend_client_send_introduction(). Fixes bug 27463; bugfix
3295 o Minor bugfixes (testing, chutney):
3296 - When running make test-network-all, use the mixed+hs-v2 network.
3297 (A previous fix to chutney removed v3 onion services from the
3298 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3299 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3300 - Before running make test-network-all, delete old logs and test
3301 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3304 Changes in version 0.3.4.7-rc - 2018-08-24
3305 Tor 0.3.4.7-rc fixes several small compilation, portability, and
3306 correctness issues in previous versions of Tor. This version is a
3307 release candidate: if no serious bugs are found, we expect that the
3308 stable 0.3.4 release will be (almost) the same as this release.
3310 o Minor features (bug workaround):
3311 - Compile correctly on systems that provide the C11 stdatomic.h
3312 header, but where C11 atomic functions don't actually compile.
3313 Closes ticket 26779; workaround for Debian issue 903709.
3315 o Minor features (continuous integration):
3316 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3317 - Enable macOS builds in our Travis CI configuration. Closes
3319 - Install libcap-dev and libseccomp2-dev so these optional
3320 dependencies get tested on Travis CI. Closes ticket 26560.
3321 - Only post Appveyor IRC notifications when the build fails.
3322 Implements ticket 27275.
3323 - Run asciidoc during Travis CI. Implements ticket 27087.
3324 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3326 o Minor features (continuous integration, rust):
3327 - Use cargo cache in our Travis CI configuration. Closes
3330 o Minor features (directory authorities):
3331 - Authorities no longer vote to make the subprotocol version
3332 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3333 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3335 o Minor features (geoip):
3336 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3337 Country database. Closes ticket 27089.
3339 o Minor bugfixes (compilation, windows):
3340 - Don't link or search for pthreads when building for Windows, even
3341 if we are using build environment (like mingw) that provides a
3342 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3344 o Minor bugfixes (continuous integration):
3345 - Improve Appveyor CI IRC logging. Generate correct branches and
3346 URLs for pull requests and tags. Use unambiguous short commits.
3347 Fixes bug 26979; bugfix on master.
3348 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3349 - Pass the module flags to distcheck configure, and log the flags
3350 before running configure. (Backported to 0.2.9 and later as a
3351 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3353 o Minor bugfixes (in-process restart):
3354 - Always call tor_free_all() when leaving tor_run_main(). When we
3355 did not, restarting tor in-process would cause an assertion
3356 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3358 o Minor bugfixes (linux seccomp2 sandbox):
3359 - Fix a bug in out sandboxing rules for the openat() syscall.
3360 Previously, no openat() call would be permitted, which would break
3361 filesystem operations on recent glibc versions. Fixes bug 25440;
3362 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3364 o Minor bugfixes (onion services):
3365 - Fix bug that causes services to not ever rotate their descriptors
3366 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3369 o Minor bugfixes (portability):
3370 - Fix compilation of the unit tests on GNU/Hurd, which does not
3371 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3374 o Minor bugfixes (rust):
3375 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3377 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3378 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3379 - Protover parsing was accepting the presence of whitespace in
3380 version strings, which the C implementation would choke on, e.g.
3381 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3382 - Protover parsing was ignoring a 2nd hyphen and everything after
3383 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3385 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3386 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3387 - cd to ${abs_top_builddir}/src/rust before running cargo in
3388 src/test/test_rust.sh. This makes the working directory consistent
3389 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3391 o Minor bugfixes (testing, bootstrap):
3392 - When calculating bootstrap progress, check exit policies and the
3393 exit flag. Previously, Tor would only check the exit flag, which
3394 caused race conditions in small and fast networks like chutney.
3395 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3397 o Minor bugfixes (testing, openssl compatibility):
3398 - Our "tortls/cert_matches_key" unit test no longer relies on
3399 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3400 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3401 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3403 o Minor bugfixes (Windows, compilation):
3404 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3405 27185; bugfix on 0.2.2.2-alpha.
3408 Changes in version 0.3.4.6-rc - 2018-08-06
3409 Tor 0.3.4.6-rc fixes several small compilation, portability, and
3410 correctness issues in previous versions of Tor. This version is a
3411 release candidate: if no serious bugs are found, we expect that the
3412 stable 0.3.4 release will be (almost) the same as this release.
3414 o Major bugfixes (event scheduler):
3415 - When we enable a periodic event, schedule it in the event loop
3416 rather than running it immediately. Previously, we would re-run
3417 periodic events immediately in the middle of (for example)
3418 changing our options, with unpredictable effects. Fixes bug 27003;
3419 bugfix on 0.3.4.1-alpha.
3421 o Minor features (compilation):
3422 - When building Tor, prefer to use Python 3 over Python 2, and more
3423 recent (contemplated) versions over older ones. Closes
3425 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3426 tell the compiler not to include the system malloc implementation.
3427 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3428 - Don't try to use a pragma to temporarily disable the
3429 -Wunused-const-variable warning if the compiler doesn't support
3430 it. Fixes bug 26785; bugfix on 0.3.2.11.
3432 o Minor bugfixes (continuous integration):
3433 - Skip a pair of unreliable key generation tests on Windows, until
3434 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3435 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3437 o Minor features (controller):
3438 - The control port now exposes the list of HTTPTunnelPorts and
3439 ExtOrPorts via GETINFO net/listeners/httptunnel and
3440 net/listeners/extor respectively. Closes ticket 26647.
3442 o Minor bugfixes (directory authority):
3443 - When voting for recommended versions, make sure that all of the
3444 versions are well-formed and parsable. Fixes bug 26485; bugfix
3447 o Minor features (geoip):
3448 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3449 Country database. Closes ticket 26674.
3451 o Minor features (Rust, portability):
3452 - Rust cross-compilation is now supported. Closes ticket 25895.
3454 o Minor bugfixes (compilation):
3455 - Update build system so that tor builds again with --disable-unittests
3456 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
3457 - Fix a compilation warning on some versions of GCC when building
3458 code that calls routerinfo_get_my_routerinfo() twice, assuming
3459 that the second call will succeed if the first one did. Fixes bug
3460 26269; bugfix on 0.2.8.2-alpha.
3462 o Minor bugfixes (controller):
3463 - Report the port correctly when a port is configured to bind to
3464 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3465 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3466 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3467 on 0.3.3.1-alpha. Patch by "akwizgran".
3469 o Minor bugfixes (correctness, flow control):
3470 - Upon receiving a stream-level SENDME cell, verify that our window
3471 has not grown too large. Fixes bug 26214; bugfix on svn
3474 o Minor bugfixes (memory, correctness):
3475 - Fix a number of small memory leaks identified by coverity. Fixes
3476 bug 26467; bugfix on numerous Tor versions.
3478 o Minor bugfixes (logging):
3479 - Improve the log message when connection initiators fail to
3480 authenticate direct connections to relays. Fixes bug 26927; bugfix
3483 o Minor bugfixes (portability):
3484 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
3485 26994; bugfix on 0.3.4.1-alpha.
3486 - Work around two different bugs in the OS X 10.10 and later SDKs
3487 that would prevent us from successfully targeting earlier versions
3488 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3490 o Minor bugfixes (single onion services, Tor2web):
3491 - Log a protocol warning when single onion services or Tor2web
3492 clients fail to authenticate direct connections to relays. Fixes
3493 bug 26924; bugfix on 0.2.9.1-alpha.
3495 o Minor bugfixes (testing):
3496 - Disable core dumps in test_bt.sh, to avoid failures in "make
3497 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3499 o Minor bugfixes (testing, compatibility):
3500 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
3501 only to pass strings (rather than "bytes" objects) to the Python
3502 subprocess module. Python 3 on Windows seems to require this.
3503 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
3504 0.3.1.1-alpha (for hs_ntor_ref.py).
3506 o Minor bugfixes (v3 onion services):
3507 - Stop sending ed25519 link specifiers in v3 onion service introduce
3508 cells and descriptors, when the rendezvous or introduction point
3509 doesn't support ed25519 link authentication. Fixes bug 26627;
3510 bugfix on 0.3.2.4-alpha.
3513 Changes in version 0.3.4.5-rc - 2018-07-13
3514 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
3515 bridge relays should upgrade.
3517 o Directory authority changes:
3518 - The "Bifroest" bridge authority has been retired; the new bridge
3519 authority is "Serge", and it is operated by George from the
3520 TorBSD project. Closes ticket 26771.
3523 Changes in version 0.3.3.9 - 2018-07-13
3524 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3525 bridge relays should upgrade.
3527 o Directory authority changes:
3528 - The "Bifroest" bridge authority has been retired; the new bridge
3529 authority is "Serge", and it is operated by George from the
3530 TorBSD project. Closes ticket 26771.
3533 Changes in version 0.3.2.11 - 2018-07-13
3534 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3535 bridge relays should upgrade. We also take this opportunity to backport
3538 o Directory authority changes:
3539 - The "Bifroest" bridge authority has been retired; the new bridge
3540 authority is "Serge", and it is operated by George from the
3541 TorBSD project. Closes ticket 26771.
3543 o Directory authority changes (backport from 0.3.3.7):
3544 - Add an IPv6 address for the "dannenberg" directory authority.
3545 Closes ticket 26343.
3547 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3548 - When directory authorities read a zero-byte bandwidth file, they
3549 would previously log a warning with the contents of an
3550 uninitialised buffer. They now log a warning about the empty file
3551 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3553 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3554 - Correctly detect when onion services get disabled after HUP. Fixes
3555 bug 25761; bugfix on 0.3.2.1.
3557 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3558 - Explicitly permit the poll() system call when the Linux
3559 seccomp2-based sandbox is enabled: apparently, some versions of
3560 libc use poll() when calling getpwnam(). Closes ticket 25313.
3562 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3563 - Update the Travis CI configuration to use the stable Rust channel,
3564 now that we have decided to require that. Closes ticket 25714.
3566 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3567 - Our .travis.yml configuration now includes support for testing the
3568 results of "make distcheck". (It's not uncommon for "make check"
3569 to pass but "make distcheck" to fail.) Closes ticket 25814.
3570 - Our Travis CI configuration now integrates with the Coveralls
3571 coverage analysis tool. Closes ticket 25818.
3573 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3574 - Add several checks to detect whether Tor relays are uploading
3575 their descriptors without specifying why they regenerated them.
3576 Diagnostic for ticket 25686.
3578 o Minor features (compilation, backport from 0.3.4.4-rc):
3579 - When building Tor, prefer to use Python 3 over Python 2, and more
3580 recent (contemplated) versions over older ones. Closes
3583 o Minor features (geoip):
3584 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3585 Country database. Closes ticket 26674.
3587 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3588 - Upon receiving a malformed connected cell, stop processing the
3589 cell immediately. Previously we would mark the connection for
3590 close, but continue processing the cell as if the connection were
3591 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3593 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3594 - Allow the nanosleep() system call, which glibc uses to implement
3595 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3597 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3598 - When running the hs_ntor_ref.py test, make sure only to pass
3599 strings (rather than "bytes" objects) to the Python subprocess
3600 module. Python 3 on Windows seems to require this. Fixes bug
3601 26535; bugfix on 0.3.1.1-alpha.
3602 - When running the ntor_ref.py test, make sure only to pass strings
3603 (rather than "bytes" objects) to the Python subprocess module.
3604 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3607 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3608 - Work around a change in OpenSSL 1.1.1 where return values that
3609 would previously indicate "no password" now indicate an empty
3610 password. Without this workaround, Tor instances running with
3611 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3612 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3614 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3615 - Document that the PerConnBW{Rate,Burst} options will fall back to
3616 their corresponding consensus parameters only if those parameters
3617 are set. Previously we had claimed that these values would always
3618 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3620 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3621 - Fix a compilation warning on some versions of GCC when building
3622 code that calls routerinfo_get_my_routerinfo() twice, assuming
3623 that the second call will succeed if the first one did. Fixes bug
3624 26269; bugfix on 0.2.8.2-alpha.
3626 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3627 - Don't consider Tor running as a client if the ControlPort is open,
3628 but no actual client ports are open. Fixes bug 26062; bugfix
3631 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3632 - Prevent a possible out-of-bounds smartlist read in
3633 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3635 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3636 - Fix a very unlikely (impossible, we believe) null pointer
3637 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3638 Coverity; this is CID 1430932.
3640 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3641 - Fix a memory leak when a v3 onion service is configured and gets a
3642 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3643 - When parsing the descriptor signature, look for the token plus an
3644 extra white-space at the end. This is more correct but also will
3645 allow us to support new fields that might start with "signature".
3646 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3648 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3649 - Relays now correctly block attempts to re-extend to the previous
3650 relay by Ed25519 identity. Previously they would warn in this
3651 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3654 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3655 - Avoid a crash when running with DirPort set but ORPort turned off.
3656 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3658 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3659 - Silence unused-const-variable warnings in zstd.h with some GCC
3660 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3662 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3663 - Avoid intermittent test failures due to a test that had relied on
3664 onion service introduction point creation finishing within 5
3665 seconds of real clock time. Fixes bug 25450; bugfix
3668 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3669 - Fix a C99 compliance issue in our configuration script that caused
3670 compilation issues when compiling Tor with certain versions of
3671 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3673 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3674 - Fix a number of small memory leaks identified by coverity. Fixes
3675 bug 26467; bugfix on numerous Tor versions.
3677 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3678 - Move the list of default directory authorities to its own file.
3679 Closes ticket 24854. Patch by "beastr0".
3682 Changes in version 0.2.9.16 - 2018-07-13
3683 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3684 bridge relays should upgrade. We also take this opportunity to backport
3687 o Directory authority changes:
3688 - The "Bifroest" bridge authority has been retired; the new bridge
3689 authority is "Serge", and it is operated by George from the
3690 TorBSD project. Closes ticket 26771.
3692 o Directory authority changes (backport from 0.3.3.7):
3693 - Add an IPv6 address for the "dannenberg" directory authority.
3694 Closes ticket 26343.
3696 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3697 - When directory authorities read a zero-byte bandwidth file, they
3698 would previously log a warning with the contents of an
3699 uninitialised buffer. They now log a warning about the empty file
3700 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3702 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3703 - Explicitly permit the poll() system call when the Linux
3704 seccomp2-based sandbox is enabled: apparently, some versions of
3705 libc use poll() when calling getpwnam(). Closes ticket 25313.
3707 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3708 - Our .travis.yml configuration now includes support for testing the
3709 results of "make distcheck". (It's not uncommon for "make check"
3710 to pass but "make distcheck" to fail.) Closes ticket 25814.
3711 - Our Travis CI configuration now integrates with the Coveralls
3712 coverage analysis tool. Closes ticket 25818.
3714 o Minor features (compilation, backport from 0.3.4.4-rc):
3715 - When building Tor, prefer to use Python 3 over Python 2, and more
3716 recent (contemplated) versions over older ones. Closes
3719 o Minor features (geoip):
3720 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3721 Country database. Closes ticket 26674.
3723 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3724 - Upon receiving a malformed connected cell, stop processing the
3725 cell immediately. Previously we would mark the connection for
3726 close, but continue processing the cell as if the connection were
3727 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3729 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3730 - Allow the nanosleep() system call, which glibc uses to implement
3731 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3733 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3734 - When running the ntor_ref.py test, make sure only to pass strings
3735 (rather than "bytes" objects) to the Python subprocess module.
3736 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3739 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3740 - Work around a change in OpenSSL 1.1.1 where return values that
3741 would previously indicate "no password" now indicate an empty
3742 password. Without this workaround, Tor instances running with
3743 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3744 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3746 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3747 - Fix a compilation warning on some versions of GCC when building
3748 code that calls routerinfo_get_my_routerinfo() twice, assuming
3749 that the second call will succeed if the first one did. Fixes bug
3750 26269; bugfix on 0.2.8.2-alpha.
3752 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3753 - Don't consider Tor running as a client if the ControlPort is open,
3754 but no actual client ports are open. Fixes bug 26062; bugfix
3757 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3758 - Prevent a possible out-of-bounds smartlist read in
3759 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3761 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3762 - Fix a very unlikely (impossible, we believe) null pointer
3763 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3764 Coverity; this is CID 1430932.
3766 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3767 - Fix a number of small memory leaks identified by coverity. Fixes
3768 bug 26467; bugfix on numerous Tor versions.
3770 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3771 - Move the list of default directory authorities to its own file.
3772 Closes ticket 24854. Patch by "beastr0".
3775 Changes in version 0.3.4.4-rc - 2018-07-09
3776 Tor 0.3.4.4-rc fixes several small compilation, portability, and
3777 correctness issues in previous versions of Tor. This version is a
3778 release candidate: if no serious bugs are found, we expect that the
3779 stable 0.3.4 release will be (almost) the same as this release.
3781 o Minor features (compilation):
3782 - When building Tor, prefer to use Python 3 over Python 2, and more
3783 recent (contemplated) versions over older ones. Closes
3786 o Minor features (geoip):
3787 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3788 Country database. Closes ticket 26674.
3790 o Minor features (Rust, portability):
3791 - Rust cross-compilation is now supported. Closes ticket 25895.
3793 o Minor bugfixes (compilation):
3794 - Fix a compilation warning on some versions of GCC when building
3795 code that calls routerinfo_get_my_routerinfo() twice, assuming
3796 that the second call will succeed if the first one did. Fixes bug
3797 26269; bugfix on 0.2.8.2-alpha.
3799 o Minor bugfixes (control port):
3800 - Report the port correctly when a port is configured to bind to
3801 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3802 - Handle the HSADDRESS= argument to the HSPOST command properly.
3803 (Previously, this argument was misparsed and thus ignored.) Fixes
3804 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3806 o Minor bugfixes (correctness, flow control):
3807 - Upon receiving a stream-level SENDME cell, verify that our window
3808 has not grown too large. Fixes bug 26214; bugfix on svn
3811 o Minor bugfixes (memory, correctness):
3812 - Fix a number of small memory leaks identified by coverity. Fixes
3813 bug 26467; bugfix on numerous Tor versions.
3815 o Minor bugfixes (testing, compatibility):
3816 - When running the hs_ntor_ref.py test, make sure only to pass
3817 strings (rather than "bytes" objects) to the Python subprocess
3818 module. Python 3 on Windows seems to require this. Fixes bug
3819 26535; bugfix on 0.3.1.1-alpha.
3820 - When running the ntor_ref.py test, make sure only to pass strings
3821 (rather than "bytes" objects) to the Python subprocess module.
3822 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3826 Changes in version 0.3.3.8 - 2018-07-09
3827 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3828 fixes for a memory leak affecting directory authorities.
3830 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
3831 - Stop leaking memory on directory authorities when planning to
3832 vote. This bug was crashing authorities by exhausting their
3833 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3835 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
3836 - Make sure that failing tests in Rust will actually cause the build
3837 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3840 o Minor features (compilation, backport from 0.3.4.4-rc):
3841 - When building Tor, prefer to use Python 3 over Python 2, and more
3842 recent (contemplated) versions over older ones. Closes
3845 o Minor features (geoip):
3846 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3847 Country database. Closes ticket 26674.
3849 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3850 - Add several checks to detect whether Tor relays are uploading
3851 their descriptors without specifying why they regenerated them.
3852 Diagnostic for ticket 25686.
3854 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
3855 - Don't count path selection failures as circuit build failures.
3856 This change should eliminate cases where Tor blames its guard or
3857 the network for situations like insufficient microdescriptors
3858 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3861 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3862 - Fix a compilation warning on some versions of GCC when building
3863 code that calls routerinfo_get_my_routerinfo() twice, assuming
3864 that the second call will succeed if the first one did. Fixes bug
3865 26269; bugfix on 0.2.8.2-alpha.
3867 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
3868 - Handle the HSADDRESS= argument to the HSPOST command properly.
3869 (Previously, this argument was misparsed and thus ignored.) Fixes
3870 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3872 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3873 - Fix a number of small memory leaks identified by coverity. Fixes
3874 bug 26467; bugfix on numerous Tor versions.
3876 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3877 - Relays now correctly block attempts to re-extend to the previous
3878 relay by Ed25519 identity. Previously they would warn in this
3879 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3882 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
3883 - When shutting down, Tor now clears all the flags in the control.c
3884 module. This should prevent a bug where authentication cookies are
3885 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3887 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3888 - When running the hs_ntor_ref.py test, make sure only to pass
3889 strings (rather than "bytes" objects) to the Python subprocess
3890 module. Python 3 on Windows seems to require this. Fixes bug
3891 26535; bugfix on 0.3.1.1-alpha.
3892 - When running the ntor_ref.py test, make sure only to pass strings
3893 (rather than "bytes" objects) to the Python subprocess module.
3894 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3898 Changes in version 0.3.4.3-alpha - 2018-06-26
3899 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
3900 one that was causing stability issues on directory authorities.
3902 o Major bugfixes (directory authority):
3903 - Stop leaking memory on directory authorities when planning to
3904 vote. This bug was crashing authorities by exhausting their
3905 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3907 o Major bugfixes (rust, testing):
3908 - Make sure that failing tests in Rust will actually cause the build
3909 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3912 o Minor feature (directory authorities):
3913 - Stop warning about incomplete bw lines before the first complete
3914 bw line has been found, so that additional header lines can be
3915 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3917 o Minor features (relay, diagnostic):
3918 - Add several checks to detect whether Tor relays are uploading
3919 their descriptors without specifying why they regenerated them.
3920 Diagnostic for ticket 25686.
3922 o Minor features (unit tests):
3923 - Test complete bandwidth measurements files, and test that
3924 incomplete bandwidth lines only give warnings when the end of the
3925 header has not been detected. Fixes bug 25947; bugfix
3928 o Minor bugfixes (compilation):
3929 - Refrain from compiling unit testing related object files when
3930 --disable-unittests is set to configure script. Fixes bug 24891;
3931 bugfix on 0.2.5.1-alpha.
3932 - When linking the libtor_testing.a library, only include the
3933 dirauth object files once. Previously, they were getting added
3934 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
3935 - The --enable-fatal-warnings flag now affects Rust code as well.
3936 Closes ticket 26245.
3938 o Minor bugfixes (onion services):
3939 - Recompute some consensus information after detecting a clock jump,
3940 or after transitioning from a non-live consensus to a live
3941 consensus. We do this to avoid having an outdated state, and
3942 miscalculating the index for next-generation onion services. Fixes
3943 bug 24977; bugfix on 0.3.2.1-alpha.
3945 o Minor bugfixes (relay):
3946 - Relays now correctly block attempts to re-extend to the previous
3947 relay by Ed25519 identity. Previously they would warn in this
3948 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3951 o Minor bugfixes (testing):
3952 - Fix compilation of the doctests in the Rust crypto crate. Fixes
3953 bug 26415; bugfix on 0.3.4.1-alpha.
3954 - Instead of trying to read the geoip configuration files from
3955 within the unit tests, instead create our own ersatz files with
3956 just enough geoip data in the format we expect. Trying to read
3957 from the source directory created problems on Windows with mingw,
3958 where the build system's paths are not the same as the platform's
3959 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
3960 - Refrain from trying to get an item from an empty smartlist in
3961 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
3962 to catch improper smartlist usage. Furthermore, enable
3963 DEBUG_SMARTLIST globally when build is configured with fragile
3964 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
3967 Changes in version 0.3.3.7 - 2018-06-12
3968 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3969 fixes for bugs affecting compatibility and stability.
3971 o Directory authority changes:
3972 - Add an IPv6 address for the "dannenberg" directory authority.
3973 Closes ticket 26343.
3975 o Minor features (geoip):
3976 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3977 Country database. Closes ticket 26351.
3979 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3980 - Work around a change in OpenSSL 1.1.1 where return values that
3981 would previously indicate "no password" now indicate an empty
3982 password. Without this workaround, Tor instances running with
3983 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3984 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3986 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3987 - Silence unused-const-variable warnings in zstd.h with some GCC
3988 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3990 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3991 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3992 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3993 miscounting the total number of circuits for these field values.)
3994 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3996 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3997 - Prevent a possible out-of-bounds smartlist read in
3998 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4000 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
4001 - Only select relays when they have the descriptors we prefer to use
4002 for them. This change fixes a bug where we could select a relay
4003 because it had _some_ descriptor, but reject it later with a
4004 nonfatal assertion error because it didn't have the exact one we
4005 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4008 Changes in version 0.3.4.2-alpha - 2018-06-12
4009 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
4010 release, and forward-ports an authority-only security fix from 0.3.3.6.
4012 o Directory authority changes:
4013 - Add an IPv6 address for the "dannenberg" directory authority.
4014 Closes ticket 26343.
4016 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
4017 - Fix a bug that could have allowed an attacker to force a directory
4018 authority to use up all its RAM by passing it a maliciously
4019 crafted protocol versions string. Fixes bug 25517; bugfix on
4020 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4022 o Minor features (continuous integration):
4023 - Add the necessary configuration files for continuous integration
4024 testing on Windows, via the Appveyor platform. Closes ticket
4025 25549. Patches from Marcin Cieślak and Isis Lovecruft.
4027 o Minor features (geoip):
4028 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4029 Country database. Closes ticket 26351.
4031 o Minor bugfixes (compatibility, openssl):
4032 - Work around a change in OpenSSL 1.1.1 where return values that
4033 would previously indicate "no password" now indicate an empty
4034 password. Without this workaround, Tor instances running with
4035 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4036 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4038 o Minor bugfixes (compilation):
4039 - Silence unused-const-variable warnings in zstd.h with some GCC
4040 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4041 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
4042 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
4043 - Avoid a compiler warning when casting the return value of
4044 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
4045 26283; bugfix on 0.2.4.10-alpha.
4047 o Minor bugfixes (control port):
4048 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
4049 CIRC_BW events. Previously, such cells were counted entirely in
4050 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
4053 o Minor bugfixes (controller):
4054 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4055 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4056 miscounting the total number of circuits for these field values.)
4057 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4059 o Minor bugfixes (hardening):
4060 - Prevent a possible out-of-bounds smartlist read in
4061 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4063 o Minor bugfixes (onion services):
4064 - Fix a bug that blocked the creation of ephemeral v3 onion
4065 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
4067 o Minor bugfixes (test coverage tools):
4068 - Update our "cov-diff" script to handle output from the latest
4069 version of gcov, and to remove extraneous timestamp information
4070 from its output. Fixes bugs 26101 and 26102; bugfix
4074 Changes in version 0.3.3.6 - 2018-05-22
4075 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
4076 backports several important fixes from the 0.3.4.1-alpha.
4078 The Tor 0.3.3 series includes controller support and other
4079 improvements for v3 onion services, official support for embedding Tor
4080 within other applications, and our first non-trivial module written in
4081 the Rust programming language. (Rust is still not enabled by default
4082 when building Tor.) And as usual, there are numerous other smaller
4083 bugfixes, features, and improvements.
4085 Below are the changes since 0.3.3.5-rc. For a list of all changes
4086 since 0.3.2.10, see the ReleaseNotes file.
4088 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
4089 - When directory authorities read a zero-byte bandwidth file, they
4090 would previously log a warning with the contents of an
4091 uninitialised buffer. They now log a warning about the empty file
4092 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4094 o Major bugfixes (security, directory authority, denial-of-service):
4095 - Fix a bug that could have allowed an attacker to force a directory
4096 authority to use up all its RAM by passing it a maliciously
4097 crafted protocol versions string. Fixes bug 25517; bugfix on
4098 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4100 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
4101 - Avoid a rare assertion failure in the circuit build timeout code
4102 if we fail to allow any circuits to actually complete. Fixes bug
4103 25733; bugfix on 0.2.2.2-alpha.
4105 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
4106 - Avoid a crash when testing router reachability on a router that
4107 could have an ed25519 ID, but which does not. Fixes bug 25415;
4108 bugfix on 0.3.3.2-alpha.
4110 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
4111 - Correctly detect when onion services get disabled after HUP. Fixes
4112 bug 25761; bugfix on 0.3.2.1.
4114 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
4115 - Impose a limit on circuit cell queue size. The limit can be
4116 controlled by a consensus parameter. Fixes bug 25226; bugfix
4119 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4120 - Avoid some compilation warnings with recent versions of LibreSSL.
4121 Closes ticket 26006.
4123 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4124 - Our .travis.yml configuration now includes support for testing the
4125 results of "make distcheck". (It's not uncommon for "make check"
4126 to pass but "make distcheck" to fail.) Closes ticket 25814.
4127 - Our Travis CI configuration now integrates with the Coveralls
4128 coverage analysis tool. Closes ticket 25818.
4130 o Minor features (geoip):
4131 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4132 database. Closes ticket 26104.
4134 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4135 - Don't consider Tor running as a client if the ControlPort is open,
4136 but no actual client ports are open. Fixes bug 26062; bugfix
4139 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4140 - Upon receiving a malformed connected cell, stop processing the
4141 cell immediately. Previously we would mark the connection for
4142 close, but continue processing the cell as if the connection were
4143 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4145 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4146 - Stop saying in the manual that clients cache ipv4 dns answers from
4147 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4148 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4149 we forgot to say so in the man page. Fixes bug 26052; bugfix
4152 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4153 - Allow the nanosleep() system call, which glibc uses to implement
4154 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4156 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4157 - Fix a memory leak when a v3 onion service is configured and gets a
4158 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4159 - When parsing the descriptor signature, look for the token plus an
4160 extra white-space at the end. This is more correct but also will
4161 allow us to support new fields that might start with "signature".
4162 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4164 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4165 - Avoid a crash when running with DirPort set but ORPort turned off.
4166 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4168 o Documentation (backport from 0.3.4.1-alpha):
4169 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4170 ticket 25857. Patch from "CTassisF".
4173 Changes in version 0.3.4.1-alpha - 2018-05-17
4174 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
4175 includes refactoring to begin reducing Tor's binary size and idle CPU
4176 usage on mobile, along with prep work for new bandwidth scanners,
4177 improvements to the experimental "vanguards" feature, and numerous
4178 other small features and bugfixes.
4180 o New system requirements:
4181 - Tor no longer tries to support old operating systems without
4182 mmap() or some local equivalent. Apparently, compilation on such
4183 systems has been broken for some time, without anybody noticing or
4184 complaining. Closes ticket 25398.
4186 o Major feature (directory authority, modularization):
4187 - The directory authority subsystem has been modularized. The code
4188 is now located in src/or/dirauth/, and is compiled in by default.
4189 To disable the module, the configure option
4190 --disable-module-dirauth has been added. This module may be
4191 disabled by default in some future release. Closes ticket 25610.
4193 o Major features (main loop, CPU usage):
4194 - When Tor is disabled (via DisableNetwork or via hibernation), it
4195 no longer needs to run any per-second events. This change should
4196 make it easier for mobile applications to disable Tor while the
4197 device is sleeping, or Tor is not running. Closes ticket 26063.
4198 - Tor no longer enables all of its periodic events by default.
4199 Previously, Tor would enable all possible main loop events,
4200 regardless of whether it needed them. Furthermore, many of these
4201 events are now disabled with Tor is hibernating or DisableNetwork
4202 is set. This is a big step towards reducing client CPU usage by
4203 reducing the amount of wake-ups the daemon does. Closes ticket
4205 - The bandwidth-limitation logic has been refactored so that
4206 bandwidth calculations are performed on-demand, rather than every
4207 TokenBucketRefillInterval milliseconds. This change should improve
4208 the granularity of our bandwidth calculations, and limit the
4209 number of times that the Tor process needs to wake up when it is
4210 idle. Closes ticket 25373.
4211 - Move responsibility for many operations from a once-per-second
4212 callback to a callback that is only scheduled as needed. Moving
4213 this functionality has allowed us to disable the callback when
4214 Tor's network is disabled. Once enough items are removed from our
4215 once-per-second callback, we can eliminate it entirely to conserve
4216 CPU when idle. The functionality removed includes: closing
4217 connections, circuits, and channels (ticket 25932); consensus
4218 voting (25937); flushing log callbacks (25951); honoring delayed
4219 SIGNEWNYM requests (25949); rescanning the consensus cache
4220 (25931); saving the state file to disk (25948); warning relay
4221 operators about unreachable ports (25952); and keeping track of
4222 Tor's uptime (26009).
4224 o Major bugfixes (directory authorities, security):
4225 - When directory authorities read a zero-byte bandwidth file, they
4226 would previously log a warning with the contents of an
4227 uninitialised buffer. They now log a warning about the empty file
4228 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4230 o Major bugfixes (crash):
4231 - Avoid a rare assertion failure in the circuit build timeout code
4232 if we fail to allow any circuits to actually complete. Fixes bug
4233 25733; bugfix on 0.2.2.2-alpha.
4235 o Major bugfixes (directory authority):
4236 - Avoid a crash when testing router reachability on a router that
4237 could have an ed25519 ID, but which does not. Fixes bug 25415;
4238 bugfix on 0.3.3.2-alpha.
4240 o Major bugfixes (onion service):
4241 - Correctly detect when onion services get disabled after HUP. Fixes
4242 bug 25761; bugfix on 0.3.2.1.
4244 o Major bugfixes (protover, voting):
4245 - Revise Rust implementation of protover to use a more memory-
4246 efficient voting algorithm and corresponding data structures, thus
4247 avoiding a potential (but small impact) DoS attack where specially
4248 crafted protocol strings would expand to several potential
4249 megabytes in memory. In the process, several portions of code were
4250 revised to be methods on new, custom types, rather than functions
4251 taking interchangeable types, thus increasing type safety of the
4252 module. Custom error types and handling were added as well, in
4253 order to facilitate better error dismissal/handling in outside
4254 crates and avoid mistakenly passing an internal error string to C
4255 over the FFI boundary. Many tests were added, and some previous
4256 differences between the C and Rust implementations have been
4257 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4259 o Major bugfixes (relay, denial of service):
4260 - Impose a limit on circuit cell queue size. The limit can be
4261 controlled by a consensus parameter. Fixes bug 25226; bugfix
4264 o Minor features (accounting):
4265 - When Tor becomes dormant, it now uses a scheduled event to wake up
4266 at the right time. Previously, we would use the per-second timer
4267 to check whether to wake up, but we no longer have any per-second
4268 timers enabled when the network is disabled. Closes ticket 26064.
4270 o Minor features (code quality):
4271 - Add optional spell-checking for the Tor codebase, using the
4272 "misspell" program. To use this feature, run "make check-typos".
4273 Closes ticket 25024.
4275 o Minor features (compatibility):
4276 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
4277 the no-deprecated option, and builds correctly with them. Closes
4278 tickets 19429, 19981, and 25353.
4279 - Avoid some compilation warnings with recent versions of LibreSSL.
4280 Closes ticket 26006.
4282 o Minor features (compression, zstd):
4283 - When running with zstd, Tor now considers using advanced functions
4284 that the zstd maintainers have labeled as potentially unstable. To
4285 prevent breakage, Tor will only use this functionality when the
4286 runtime version of the zstd library matches the version with which
4287 Tor was compiled. Closes ticket 25162.
4289 o Minor features (configuration):
4290 - The "DownloadSchedule" options have been renamed to end with
4291 "DownloadInitialDelay". The old names are still allowed, but will
4292 produce a warning. Comma-separated lists are still permitted for
4293 these options, but all values after the first are ignored (as they
4294 have been since 0.2.9). Closes ticket 23354.
4296 o Minor features (continuous integration):
4297 - Our .travis.yml configuration now includes support for testing the
4298 results of "make distcheck". (It's not uncommon for "make check"
4299 to pass but "make distcheck" to fail.) Closes ticket 25814.
4300 - Our Travis CI configuration now integrates with the Coveralls
4301 coverage analysis tool. Closes ticket 25818.
4303 o Minor features (control port):
4304 - Introduce GETINFO "current-time/{local,utc}" to return the local
4305 and UTC times respectively in ISO format. This helps a controller
4306 like Tor Browser detect a time-related error. Closes ticket 25511.
4307 Patch by Neel Chauhan.
4308 - Introduce new fields to the CIRC_BW event. There are two new
4309 fields in each of the read and written directions. The DELIVERED
4310 fields report the total valid data on the circuit, as measured by
4311 the payload sizes of verified and error-checked relay command
4312 cells. The OVERHEAD fields report the total unused bytes in each
4313 of these cells. Closes ticket 25903.
4315 o Minor features (directory authority):
4316 - Directory authorities now open their key-pinning files as O_SYNC,
4317 to limit their chances of accidentally writing partial lines.
4318 Closes ticket 23909.
4320 o Minor features (directory authority, forward compatibility):
4321 - Make the lines of the measured bandwidth file able to contain
4322 their entries in any order. Previously, the node_id entry needed
4323 to come first. Closes ticket 26004.
4325 o Minor features (entry guards):
4326 - Introduce a new torrc option NumPrimaryGuards for controlling the
4327 number of primary guards. Closes ticket 25843.
4329 o Minor features (geoip):
4330 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4331 database. Closes ticket 26104.
4333 o Minor features (performance):
4334 - Avoid a needless call to malloc() when processing an incoming
4335 relay cell. Closes ticket 24914.
4336 - Make our timing-wheel code run a tiny bit faster on 32-bit
4337 platforms, by preferring 32-bit math to 64-bit. Closes
4339 - Avoid a needless malloc()/free() pair every time we handle an ntor
4340 handshake. Closes ticket 25150.
4342 o Minor features (testing):
4343 - Add a unit test for voting_schedule_get_start_of_next_interval().
4344 Closes ticket 26014, and helps make unit test coverage
4346 - A new unittests module specifically for testing the functions in
4347 the (new-ish) bridges.c module has been created with new
4348 unittests, raising the code coverage percentages. Closes 25425.
4349 - We now have improved testing for addressmap_get_virtual_address()
4350 function. This should improve our test coverage, and make our test
4351 coverage more deterministic. Closes ticket 25993.
4353 o Minor features (timekeeping, circuit scheduling):
4354 - When keeping track of how busy each circuit have been recently on
4355 a given connection, use coarse-grained monotonic timers rather
4356 than gettimeofday(). This change should marginally increase
4357 accuracy and performance. Implements part of ticket 25927.
4359 o Minor bugfixes (bandwidth management):
4360 - Consider ourselves "low on write bandwidth" if we have exhausted
4361 our write bandwidth some time in the last second. This was the
4362 documented behavior before, but the actual behavior was to change
4363 this value every TokenBucketRefillInterval. Fixes bug 25828;
4364 bugfix on 0.2.3.5-alpha.
4366 o Minor bugfixes (C correctness):
4367 - Add a missing lock acquisition in the shutdown code of the control
4368 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
4369 Coverity; this is CID 1433643.
4371 o Minor bugfixes (circuit path selection):
4372 - Don't count path selection failures as circuit build failures.
4373 This change should eliminate cases where Tor blames its guard or
4374 the network for situations like insufficient microdescriptors
4375 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4378 o Minor bugfixes (client):
4379 - Don't consider Tor running as a client if the ControlPort is open,
4380 but no actual client ports are open. Fixes bug 26062; bugfix
4383 o Minor bugfixes (code style):
4384 - Fixed multiple includes of transports.h in src/or/connection.c
4385 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
4386 - Remove the unused variable n_possible from the function
4387 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
4389 o Minor bugfixes (control interface):
4390 - Respond with more human-readable error messages to GETINFO exit-
4391 policy/* requests. Also, let controller know if an error is
4392 transient (response code 551) or not (response code 552). Fixes
4393 bug 25852; bugfix on 0.2.8.1-alpha.
4395 o Minor bugfixes (controller):
4396 - Make CIRC_BW event reflect the total of all data sent on a
4397 circuit, including padding and dropped cells. Also fix a mis-
4398 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
4399 bugfix on 0.2.5.2-alpha.
4401 o Minor bugfixes (correctness, client):
4402 - Upon receiving a malformed connected cell, stop processing the cell
4403 immediately. Previously we would mark the connection for close, but
4404 continue processing the cell as if the connection were open. Fixes bug
4405 26072; bugfix on 0.2.4.7-alpha.
4407 o Minor bugfixes (directory client):
4408 - When unverified-consensus is verified, rename it to cached-
4409 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
4410 - Fixed launching a certificate fetch always during the scheduled
4411 periodic consensus fetch by fetching only in those cases when
4412 consensus are waiting for certs. Fixes bug 24740; bugfix
4415 o Minor bugfixes (documentation):
4416 - Stop saying in the manual that clients cache ipv4 dns answers from
4417 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4418 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4419 we forgot to say so in the man page. Fixes bug 26052; bugfix
4422 o Minor bugfixes (error reporting):
4423 - Improve tolerance for directory authorities with skewed clocks.
4424 Previously, an authority with a clock more than 60 seconds ahead
4425 could cause a client with a correct clock to warn that the
4426 client's clock was behind. Now the clocks of a majority of
4427 directory authorities have to be ahead of the client before this
4428 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
4430 o Minor bugfixes (Linux seccomp2 sandbox):
4431 - Allow the nanosleep() system call, which glibc uses to implement
4432 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4434 o Minor bugfixes (onion service):
4435 - Fix a memory leak when a v3 onion service is configured and gets a
4436 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4437 - When parsing the descriptor signature, look for the token plus an
4438 extra white-space at the end. This is more correct but also will
4439 allow us to support new fields that might start with "signature".
4440 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4442 o Minor bugfixes (path selection):
4443 - Only select relays when they have the descriptors we prefer to use
4444 for them. This change fixes a bug where we could select a relay
4445 because it had _some_ descriptor, but reject it later with a
4446 nonfatal assertion error because it didn't have the exact one we
4447 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4449 o Minor bugfixes (portability):
4450 - Do not align mmap length, as it is not required by POSIX, and the
4451 getpagesize function is deprecated. Fixes bug 25399; bugfix
4454 o Minor bugfixes (portability, FreeBSD):
4455 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
4456 does not stringify on FreeBSD, so we switch to tor_asprintf().
4457 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
4459 o Minor bugfixes (relay statistics):
4460 - When a relay is collecting internal statistics about how many
4461 create cell requests it has seen of each type, accurately count
4462 the requests from relays that temporarily fall out of the
4463 consensus. (To be extra conservative, we were already ignoring
4464 requests from clients in our counts, and we continue ignoring them
4465 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
4467 o Minor bugfixes (relay, crash):
4468 - Avoid a crash when running with DirPort set but ORPort turned off.
4469 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4471 o Minor bugfixes (restart-in-process):
4472 - When shutting down, Tor now clears all the flags in the control.c
4473 module. This should prevent a bug where authentication cookies are
4474 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4476 o Minor bugfixes (testing):
4477 - When testing workqueue event-cancellation, make sure that we
4478 actually cancel an event, and that cancel each event with equal
4479 probability. (It was previously possible, though extremely
4480 unlikely, for our event-canceling test not to cancel any events.)
4481 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
4482 - Repeat part of the test in test_client_pick_intro() a number of
4483 times, to give it consistent coverage. Fixes bug 25996; bugfix
4485 - Remove randomness from the hs_common/responsible_hsdirs test, so
4486 that it always takes the same path through the function it tests.
4487 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
4488 - Change the behavior of the "channel/outbound" test so that it
4489 never causes a 10-second rollover for the EWMA circuitmux code.
4490 Previously, this behavior would happen randomly, and result in
4491 fluctuating test coverage. Fixes bug 25994; bugfix
4493 - Use X509_new() to allocate certificates that will be freed later
4494 with X509_free(). Previously, some parts of the unit tests had
4495 used tor_malloc_zero(), which is incorrect, and which caused test
4496 failures on Windows when they were built with extra hardening.
4497 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
4499 - While running the circuit_timeout test, fix the PRNG to a
4500 deterministic AES stream, so that the test coverage from this test
4501 will itself be deterministic. Fixes bug 25995; bugfix
4504 o Minor bugfixes (vanguards):
4505 - Allow the last hop in a vanguard circuit to be the same as our
4506 first, to prevent the adversary from influencing guard node choice
4507 by choice of last hop. Also prevent the creation of A - B - A
4508 paths, or A - A paths, which are forbidden by relays. Fixes bug
4509 25870; bugfix on 0.3.3.1-alpha.
4511 o Code simplification and refactoring:
4512 - Remove duplicate code in parse_{c,s}method_line and bootstrap
4513 their functionalities into a single function. Fixes bug 6236;
4514 bugfix on 0.2.3.6-alpha.
4515 - We remove the PortForwsrding and PortForwardingHelper options,
4516 related functions, and the port_forwarding tests. These options
4517 were used by the now-deprecated Vidalia to help ordinary users
4518 become Tor relays or bridges. Closes ticket 25409. Patch by
4520 - In order to make the OR and dir checking function in router.c less
4521 confusing we renamed some functions and
4522 consider_testing_reachability() has been split into
4523 router_should_check_reachability() and
4524 router_do_reachability_checks(). Also we improved the documentation
4525 in some functions. Closes ticket 18918.
4526 - Initial work to isolate Libevent usage to a handful of modules in
4527 our codebase, to simplify our call structure, and so that we can
4528 more easily change event loops in the future if needed. Closes
4530 - Introduce a function to call getsockname() and return tor_addr_t,
4531 to save a little complexity throughout the codebase. Closes
4533 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
4534 as hsdir_index is always present. Also, we move hsdir_index_t into
4535 or.h. Closes ticket 23094. Patch by Neel Chauhan.
4536 - Merge functions used for describing nodes and suppress the
4537 functions that do not allocate memory for the output buffer
4538 string. NODE_DESC_BUF_LEN constant and format_node_description()
4539 function cannot be used externally from router.c module anymore.
4540 Closes ticket 25432. Patch by valentecaio.
4541 - Our main loop has been simplified so that all important operations
4542 happen inside events. Previously, some operations had to happen
4543 outside the event loop, to prevent infinite sequences of event
4544 activations. Closes ticket 25374.
4545 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4546 it in register_intro_circ() and service_intro_point_new(). This
4547 prevents the digest from being re-calculated each time. Closes
4548 ticket 23107. Patch by Neel Chauhan.
4549 - Refactor token-bucket implementations to use a common backend.
4550 Closes ticket 25766.
4551 - Remove extern declaration of stats_n_seconds_working variable from
4552 main, protecting its accesses with get_uptime() and reset_uptime()
4553 functions. Closes ticket 25081, patch by “valentecaio”.
4554 - Remove our previous logic for "cached gettimeofday()" -- our
4555 coarse monotonic timers are fast enough for this purpose, and far
4556 less error-prone. Implements part of ticket 25927.
4557 - Remove the return value for fascist_firewall_choose_address_base(),
4558 and sister functions such as fascist_firewall_choose_address_node()
4559 and fascist_firewall_choose_address_rs(). Also, while we're here,
4560 initialize the ap argument as leaving it uninitialized can pose a
4561 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4562 - Rename two fields of connection_t struct. timestamp_lastwritten is
4563 renamed to timestamp_last_write_allowed and timestamp_lastread is
4564 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4566 - Since Tor requires C99, remove our old workaround code for libc
4567 implementations where free(NULL) doesn't work. Closes ticket 24484.
4568 - Use our standard rate-limiting code to deal with excessive
4569 libevent failures, rather than the hand-rolled logic we had
4570 before. Closes ticket 26016.
4571 - We remove the return value of node_get_prim_orport() and
4572 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4573 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4574 check for a null address. Closes ticket 23873. Patch by
4576 - We switch to should_record_bridge_info() in
4577 geoip_note_client_seen() and options_need_geoip_info() instead of
4578 accessing the configuration values directly. Fixes bug 25290;
4579 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4581 o Deprecated features:
4582 - As we are not recommending 0.2.5 anymore, we require relays that
4583 once had an ed25519 key associated with their RSA key to always
4584 have that key, instead of allowing them to drop back to a version
4585 that didn't support ed25519. This means they need to use a new RSA
4586 key if they want to downgrade to an older version of tor without
4587 ed25519. Closes ticket 20522.
4590 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4591 ticket 25857. Patch from "CTassisF".
4594 - Directory authorities will no longer support voting according to
4595 any consensus method before consensus method 25. This keeps
4596 authorities compatible with all authorities running 0.2.9.8 and
4597 later, and does not break any clients or relays. Implements ticket
4598 24378 and proposal 290.
4599 - The PortForwarding and PortForwardingHelper features have been
4600 removed. The reasoning is, given that implementations of NAT
4601 traversal protocols within common consumer grade routers are
4602 frequently buggy, and that the target audience for a NAT punching
4603 feature is a perhaps less-technically-inclined relay operator,
4604 when the helper fails to setup traversal the problems are usually
4605 deep, ugly, and very router specific, making them horrendously
4606 impossible for technical support to reliable assist with, and thus
4607 resulting in frustration all around. Unfortunately, relay
4608 operators who would like to run relays behind NATs will need to
4609 become more familiar with the port forwarding configurations on
4610 their local router. Closes 25409.
4611 - The TestingEnableTbEmptyEvent option has been removed. It was used
4612 in testing simulations to measure how often connection buckets
4613 were emptied, in order to improve our scheduling, but it has not
4614 been actively used in years. Closes ticket 25760.
4615 - The old "round-robin" circuit multiplexer (circuitmux)
4616 implementation has been removed, along with a fairly large set of
4617 code that existed to support it. It has not been the default
4618 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4619 but it still required an unreasonable amount of memory and CPU.
4620 Closes ticket 25268.
4623 Changes in version 0.3.3.5-rc - 2018-04-15
4624 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4625 including some that could affect reliability or correctness.
4627 This is the first release candidate in the 0.3.3 series. If we find no
4628 new bugs or regression here, then the first stable 0.3.3 release will
4629 be nearly identical to this one.
4631 o Major bugfixes (security, protover, voting):
4632 - Revise Rust implementation of protover to use a more memory-
4633 efficient voting algorithm and corresponding data structures, thus
4634 avoiding a potential memory-based DoS attack where specially
4635 crafted protocol strings would expand to fill available memory.
4636 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4638 o Major bugfixes (performance, load balancing):
4639 - Directory authorities no longer vote in favor of the Guard flag
4640 for relays without directory support. Starting in Tor
4641 0.3.0.1-alpha, clients have been avoiding using such relays in the
4642 Guard position, leading to increasingly broken load balancing for
4643 the 5%-or-so of Guards that don't advertise directory support.
4644 Fixes bug 22310; bugfix on 0.3.0.6.
4646 o Minor feature (continuous integration):
4647 - Update the Travis CI configuration to use the stable Rust channel,
4648 now that we have decided to require that. Closes ticket 25714.
4650 o Minor features (config options):
4651 - Change the way the default value for MaxMemInQueues is calculated.
4652 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4653 more. Otherwise we use the former value of 75%. Closes
4656 o Minor features (geoip):
4657 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4658 Country database. Closes ticket 25718.
4660 o Minor bugfixes (client):
4661 - When using a listed relay as a bridge, and also using
4662 microdescriptors, and considering that relay as a non-bridge in a
4663 circuit, treat its microdescriptor as a valid source of
4664 information about that relay. This change should prevent a non-
4665 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4667 o Minor bugfixes (controller):
4668 - Restore the correct operation of the RESOLVE command, which had
4669 been broken since we added the ability to enable/disable DNS on
4670 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4672 o Minor bugfixes (distribution, compilation, rust):
4673 - Build correctly when the rust dependencies submodule is loaded,
4674 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4675 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4676 - Actually include all of our Rust source in our source
4677 distributions. (Previously, a few of the files were accidentally
4678 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4680 o Minor bugfixes (documentation):
4681 - Document that the PerConnBW{Rate,Burst} options will fall back to
4682 their corresponding consensus parameters only if those parameters
4683 are set. Previously we had claimed that these values would always
4684 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4685 - Revert a misformatting issue in the ExitPolicy documentation.
4686 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4688 o Minor bugfixes (exit relay DNS retries):
4689 - Re-attempt timed-out DNS queries 3 times before failure, since our
4690 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4691 slightly more timeouts per resolver when an exit has multiple
4692 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4694 o Minor bugfixes (onion services):
4695 - Re-instate counting the client HSDir fetch circuits against the
4696 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4698 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4699 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4700 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4702 o Code simplification and refactoring:
4703 - Move the list of default directory authorities to its own file.
4704 Closes ticket 24854. Patch by "beastr0".
4706 o Documentation (manpage, denial of service):
4707 - Provide more detail about the denial-of-service options, by
4708 listing each mitigation and explaining how they relate. Closes
4712 Changes in version 0.3.3.4-alpha - 2018-03-29
4713 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4714 the alpha testing of earlier releases in its series. We are
4715 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4717 o New system requirements:
4718 - When built with Rust, Tor now depends on version 0.2.39 of the
4719 libc crate. Closes tickets 25310 and 25664.
4721 o Major bugfixes (relay, connection):
4722 - If we have failed to connect to a relay and received a connection
4723 refused, timeout, or similar error (at the TCP level), do not try
4724 that same address/port again for 60 seconds after the failure has
4725 occurred. Fixes bug 24767; bugfix on 0.0.6.
4727 o Minor features (geoip):
4728 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4729 Country database. Closes ticket 25469.
4731 o Minor features (log messages):
4732 - Improve log message in the out-of-memory handler to include
4733 information about memory usage from the different compression
4734 backends. Closes ticket 25372.
4736 o Minor features (sandbox):
4737 - Explicitly permit the poll() system call when the Linux
4738 seccomp2-based sandbox is enabled: apparently, some versions of
4739 libc use poll() when calling getpwnam(). Closes ticket 25313.
4741 o Minor bugfixes (C correctness):
4742 - Fix a very unlikely (impossible, we believe) null pointer
4743 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4744 Coverity; this is CID 1430932.
4746 o Minor bugfixes (channel, client):
4747 - Better identify client connection when reporting to the geoip
4748 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4750 o Minor bugfixes (compilation):
4751 - Fix a C99 compliance issue in our configuration script that caused
4752 compilation issues when compiling Tor with certain versions of
4753 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4755 o Minor bugfixes (controller, reliability):
4756 - Avoid a (nonfatal) assertion failure when extending a one-hop
4757 circuit from the controller to become a multihop circuit. Fixes
4758 bug 24903; bugfix on 0.2.5.2-alpha.
4760 o Major bugfixes (networking):
4761 - Tor will no longer reject IPv6 address strings from Tor Browser
4762 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4763 25036, bugfix on Tor 0.3.1.2.
4765 o Minor bugfixes (networking):
4766 - string_is_valid_hostname() will not consider IP strings to be
4767 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4769 o Minor bugfixes (onion service v3):
4770 - Avoid an assertion failure when the next onion service
4771 descriptor rotation type is out of sync with the consensus's
4772 valid-after time. Instead, log a warning message with extra
4773 information, so we can better hunt down the cause of this
4774 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
4776 o Minor bugfixes (testing):
4777 - Avoid intermittent test failures due to a test that had relied on
4778 onion service introduction point creation finishing within 5
4779 seconds of real clock time. Fixes bug 25450; bugfix
4781 - Rust crates are now automatically detected and tested. Previously,
4782 some crates were not tested by `make test-rust` due to a static
4783 string in the `src/test/test_rust.sh` script specifying which
4784 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
4786 o Minor bugfixes (testing, benchmarks):
4787 - Fix a crash when running benchmark tests on win32 systems. The
4788 crash was due to a mutex that wasn't initialized before logging
4789 and options were initialized. Fixes bug 25479; bugfix
4792 o Minor bugfixes (warnings, ipv6):
4793 - Avoid a bug warning that could occur when trying to connect to a
4794 relay over IPv6. This warning would occur on a Tor instance that
4795 downloads router descriptors, but prefers to use microdescriptors.
4796 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
4798 o Code simplification and refactoring:
4799 - Remove the old (deterministic) directory retry logic entirely:
4800 We've used exponential backoff exclusively for some time. Closes
4804 - Improved the documentation of AccountingStart parameter. Closes
4806 - Update the documentation for "Log" to include the current list of
4807 logging domains. Closes ticket 25378.
4810 Changes in version 0.3.1.10 - 2018-03-03
4811 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4814 It includes an important security fix for a remote crash attack
4815 against directory authorities, tracked as TROVE-2018-001.
4817 This release also backports our new system for improved resistance to
4818 denial-of-service attacks against relays.
4820 This release also fixes several minor bugs and annoyances from
4823 All directory authorities should upgrade to one of the versions
4824 released today. Relays running 0.3.1.x may wish to update to one of
4825 the versions released today, for the DoS mitigations.
4827 Please note: according to our release calendar, Tor 0.3.1 will no
4828 longer be supported after 1 July 2018. If you will be running Tor
4829 after that date, you should make sure to plan to upgrade to the latest
4830 stable version, or downgrade to 0.2.9 (which will receive long-term
4833 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4834 - Fix a protocol-list handling bug that could be used to remotely crash
4835 directory authorities with a null-pointer exception. Fixes bug 25074;
4836 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4839 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4840 - Give relays some defenses against the recent network overload. We
4841 start with three defenses (default parameters in parentheses).
4842 First: if a single client address makes too many concurrent
4843 connections (>100), hang up on further connections. Second: if a
4844 single client address makes circuits too quickly (more than 3 per
4845 second, with an allowed burst of 90) while also having too many
4846 connections open (3), refuse new create cells for the next while
4847 (1-2 hours). Third: if a client asks to establish a rendezvous
4848 point to you directly, ignore the request. These defenses can be
4849 manually controlled by new torrc options, but relays will also
4850 take guidance from consensus parameters, so there's no need to
4851 configure anything manually. Implements ticket 24902.
4853 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4854 - Update the sandbox rules so that they should now work correctly
4855 with Glibc 2.26. Closes ticket 24315.
4857 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4858 - Fix an "off by 2" error in counting rendezvous failures on the
4859 onion service side. While we thought we would stop the rendezvous
4860 attempt after one failed circuit, we were actually making three
4861 circuit attempts before giving up. Now switch to a default of 2,
4862 and allow the consensus parameter "hs_service_max_rdv_failures" to
4863 override. Fixes bug 24895; bugfix on 0.0.6.
4865 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4866 - Add Link protocol version 5 to the supported protocols list. Fixes
4867 bug 25070; bugfix on 0.3.1.1-alpha.
4869 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4870 - Fix a set of false positives where relays would consider
4871 connections to other relays as being client-only connections (and
4872 thus e.g. deserving different link padding schemes) if those
4873 relays fell out of the consensus briefly. Now we look only at the
4874 initial handshake and whether the connection authenticated as a
4875 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4877 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4878 - Make our OOM handler aware of the geoip client history cache so it
4879 doesn't fill up the memory. This check is important for IPv6 and
4880 our DoS mitigation subsystem. Closes ticket 25122.
4882 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
4883 - Change relay bandwidth reporting stats interval from 4 hours to 24
4884 hours in order to reduce the efficiency of guard discovery
4885 attacks. Fixes ticket 23856.
4887 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4888 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4889 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4890 since they neither disabled TLS 1.3 nor enabled any of the
4891 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4892 Closes ticket 24978.
4894 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
4895 - The fallback directory list has been re-generated based on the
4896 current status of the network. Tor uses fallback directories to
4897 bootstrap when it doesn't yet have up-to-date directory
4898 information. Closes ticket 24801.
4899 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4900 prefer to bootstrap from fallback directory mirrors. This is a
4901 follow-up to 24679, which removed weights from the default
4902 fallbacks. Implements ticket 24681.
4904 o Minor features (geoip):
4905 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4908 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4909 - Use the actual observed address of an incoming relay connection,
4910 not the canonical address of the relay from its descriptor, when
4911 making decisions about how to handle the incoming connection.
4912 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4914 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4915 - Directory authorities, when refusing a descriptor from a rejected
4916 relay, now explicitly tell the relay (in its logs) to set a valid
4917 ContactInfo address and contact the bad-relays@ mailing list.
4918 Fixes bug 25170; bugfix on 0.2.9.1.
4920 o Minor bugfixes (address selection, backport from 0.3.2.9):
4921 - When the fascist_firewall_choose_address_ functions don't find a
4922 reachable address, set the returned address to the null address
4923 and port. This is a precautionary measure, because some callers do
4924 not check the return value. Fixes bug 24736; bugfix
4927 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4928 - Fetch descriptors aggressively whenever we lack enough to build
4929 circuits, regardless of how many descriptors we are missing.
4930 Previously, we would delay launching the fetch when we had fewer
4931 than 15 missing descriptors, even if some of those descriptors
4932 were blocking circuits from building. Fixes bug 23985; bugfix on
4933 0.1.1.11-alpha. The effects of this bug became worse in
4934 0.3.0.3-alpha, when we began treating missing descriptors from our
4935 primary guards as a reason to delay circuits.
4936 - Don't try fetching microdescriptors from relays that have failed
4937 to deliver them in the past. Fixes bug 23817; bugfix
4940 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4941 - Fix a signed/unsigned comparison warning introduced by our fix to
4942 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4944 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4945 - Avoid a crash when attempting to use the seccomp2 sandbox together
4946 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4949 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4950 - Fix a possible crash on malformed consensus. If a consensus had
4951 contained an unparseable protocol line, it could have made clients
4952 and relays crash with a null-pointer exception. To exploit this
4953 issue, however, an attacker would need to be able to subvert the
4954 directory authority system. Fixes bug 25251; bugfix on
4955 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4957 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
4958 - Recover better from empty or corrupt files in the consensus cache
4959 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4960 - When a consensus diff calculation is only partially successful,
4961 only record the successful parts as having succeeded. Partial
4962 success can happen if (for example) one compression method fails
4963 but the others succeed. Previously we misrecorded all the
4964 calculations as having succeeded, which would later cause a
4965 nonfatal assertion failure. Fixes bug 24086; bugfix
4968 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4969 - Tor now updates its guard state when it reads a consensus
4970 regardless of whether it's missing descriptors. That makes tor use
4971 its primary guards to fetch descriptors in some edge cases where
4972 it would previously have used fallback directories. Fixes bug
4973 23862; bugfix on 0.3.0.1-alpha.
4975 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4976 - Don't treat inability to store a cached consensus object as a bug:
4977 it can happen normally when we are out of disk space. Fixes bug
4978 24859; bugfix on 0.3.1.1-alpha.
4980 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4981 - When queuing DESTROY cells on a channel, only queue the circuit-id
4982 and reason fields: not the entire 514-byte cell. This fix should
4983 help mitigate any bugs or attacks that fill up these queues, and
4984 free more RAM for other uses. Fixes bug 24666; bugfix
4987 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4988 - When closing a connection via close_connection_immediately(), we
4989 mark it as "not blocked on bandwidth", to prevent later calls from
4990 trying to unblock it, and give it permission to read. This fixes a
4991 backtrace warning that can happen on relays under various
4992 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4994 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4995 - When selecting relays by bandwidth, avoid a rounding error that
4996 could sometimes cause load to be imbalanced incorrectly.
4997 Previously, we would always round upwards; now, we round towards
4998 the nearest integer. This had the biggest effect when a relay's
4999 weight adjustments should have given it weight 0, but it got
5000 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5001 - When calculating the fraction of nodes that have descriptors, and
5002 all nodes in the network have zero bandwidths, count the number of
5003 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5004 - Actually log the total bandwidth in compute_weighted_bandwidths().
5005 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5007 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5008 - Improve the performance of our consensus-diff application code
5009 when Tor is built with the --enable-fragile-hardening option set.
5010 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5012 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5013 - Don't exit the Tor process if setrlimit() fails to change the file
5014 limit (which can happen sometimes on some versions of OSX). Fixes
5015 bug 21074; bugfix on 0.0.9pre5.
5017 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
5018 - Fix a bug in the bit-counting parts of our timing-wheel code on
5019 MSVC. (Note that MSVC is still not a supported build platform, due
5020 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
5023 o Minor bugfixes (relay, partial backport):
5024 - Make the internal channel_is_client() function look at what sort
5025 of connection handshake the other side used, rather than whether
5026 the other side ever sent a create_fast cell to us. Backports part
5027 of the fixes from bugs 22805 and 24898.
5029 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5030 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5032 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5033 bugfix on 0.2.9.4-alpha.
5035 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5036 - Update the "rust dependencies" submodule to be a project-level
5037 repository, rather than a user repository. Closes ticket 25323.
5040 Changes in version 0.2.9.15 - 2018-03-03
5041 Tor 0.2.9.15 backports important security and stability bugfixes from
5044 It includes an important security fix for a remote crash attack
5045 against directory authorities, tracked as TROVE-2018-001.
5047 This release also backports our new system for improved resistance to
5048 denial-of-service attacks against relays.
5050 This release also fixes several minor bugs and annoyances from
5053 All directory authorities should upgrade to one of the versions
5054 released today. Relays running 0.2.9.x may wish to update to one of
5055 the versions released today, for the DoS mitigations.
5057 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5058 - Fix a protocol-list handling bug that could be used to remotely crash
5059 directory authorities with a null-pointer exception. Fixes bug 25074;
5060 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5063 o Major features (denial-of-service mitigation):
5064 - Give relays some defenses against the recent network overload. We
5065 start with three defenses (default parameters in parentheses).
5066 First: if a single client address makes too many concurrent
5067 connections (>100), hang up on further connections. Second: if a
5068 single client address makes circuits too quickly (more than 3 per
5069 second, with an allowed burst of 90) while also having too many
5070 connections open (3), refuse new create cells for the next while
5071 (1-2 hours). Third: if a client asks to establish a rendezvous
5072 point to you directly, ignore the request. These defenses can be
5073 manually controlled by new torrc options, but relays will also
5074 take guidance from consensus parameters, so there's no need to
5075 configure anything manually. Implements ticket 24902.
5077 o Major bugfixes (bootstrapping):
5078 - Fetch descriptors aggressively whenever we lack enough to build
5079 circuits, regardless of how many descriptors we are missing.
5080 Previously, we would delay launching the fetch when we had fewer
5081 than 15 missing descriptors, even if some of those descriptors
5082 were blocking circuits from building. Fixes bug 23985; bugfix on
5083 0.1.1.11-alpha. The effects of this bug became worse in
5084 0.3.0.3-alpha, when we began treating missing descriptors from our
5085 primary guards as a reason to delay circuits.
5087 o Major bugfixes (onion services, retry behavior):
5088 - Fix an "off by 2" error in counting rendezvous failures on the
5089 onion service side. While we thought we would stop the rendezvous
5090 attempt after one failed circuit, we were actually making three
5091 circuit attempts before giving up. Now switch to a default of 2,
5092 and allow the consensus parameter "hs_service_max_rdv_failures" to
5093 override. Fixes bug 24895; bugfix on 0.0.6.
5095 o Minor feature (relay statistics):
5096 - Change relay bandwidth reporting stats interval from 4 hours to 24
5097 hours in order to reduce the efficiency of guard discovery
5098 attacks. Fixes ticket 23856.
5100 o Minor features (compatibility, OpenSSL):
5101 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5102 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5103 since they neither disabled TLS 1.3 nor enabled any of the
5104 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5105 Closes ticket 24978.
5107 o Minor features (denial-of-service avoidance):
5108 - Make our OOM handler aware of the geoip client history cache so it
5109 doesn't fill up the memory. This check is important for IPv6 and
5110 our DoS mitigation subsystem. Closes ticket 25122.
5112 o Minor features (fallback directory mirrors):
5113 - The fallback directory list has been re-generated based on the
5114 current status of the network. Tor uses fallback directories to
5115 bootstrap when it doesn't yet have up-to-date directory
5116 information. Closes ticket 24801.
5117 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5118 prefer to bootstrap from fallback directory mirrors. This is a
5119 follow-up to 24679, which removed weights from the default
5120 fallbacks. Implements ticket 24681.
5122 o Minor features (geoip):
5123 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5126 o Minor features (linux seccomp2 sandbox):
5127 - Update the sandbox rules so that they should now work correctly
5128 with Glibc 2.26. Closes ticket 24315.
5130 o Minor bugfix (channel connection):
5131 - Use the actual observed address of an incoming relay connection,
5132 not the canonical address of the relay from its descriptor, when
5133 making decisions about how to handle the incoming connection.
5134 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5136 o Minor bugfix (directory authority):
5137 - Directory authorities, when refusing a descriptor from a rejected
5138 relay, now explicitly tell the relay (in its logs) to set a valid
5139 ContactInfo address and contact the bad-relays@ mailing list.
5140 Fixes bug 25170; bugfix on 0.2.9.1.
5142 o Minor bugfixes (address selection):
5143 - When the fascist_firewall_choose_address_ functions don't find a
5144 reachable address, set the returned address to the null address
5145 and port. This is a precautionary measure, because some callers do
5146 not check the return value. Fixes bug 24736; bugfix
5149 o Minor bugfixes (compilation):
5150 - Fix a signed/unsigned comparison warning introduced by our fix to
5151 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5153 o Minor bugfixes (control port, linux seccomp2 sandbox):
5154 - Avoid a crash when attempting to use the seccomp2 sandbox together
5155 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5158 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5159 - Fix a possible crash on malformed consensus. If a consensus had
5160 contained an unparseable protocol line, it could have made clients
5161 and relays crash with a null-pointer exception. To exploit this
5162 issue, however, an attacker would need to be able to subvert the
5163 directory authority system. Fixes bug 25251; bugfix on
5164 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5166 o Minor bugfixes (memory usage):
5167 - When queuing DESTROY cells on a channel, only queue the circuit-id
5168 and reason fields: not the entire 514-byte cell. This fix should
5169 help mitigate any bugs or attacks that fill up these queues, and
5170 free more RAM for other uses. Fixes bug 24666; bugfix
5173 o Minor bugfixes (network layer):
5174 - When closing a connection via close_connection_immediately(), we
5175 mark it as "not blocked on bandwidth", to prevent later calls from
5176 trying to unblock it, and give it permission to read. This fixes a
5177 backtrace warning that can happen on relays under various
5178 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5180 o Minor bugfixes (OSX):
5181 - Don't exit the Tor process if setrlimit() fails to change the file
5182 limit (which can happen sometimes on some versions of OSX). Fixes
5183 bug 21074; bugfix on 0.0.9pre5.
5185 o Minor bugfixes (path selection):
5186 - When selecting relays by bandwidth, avoid a rounding error that
5187 could sometimes cause load to be imbalanced incorrectly.
5188 Previously, we would always round upwards; now, we round towards
5189 the nearest integer. This had the biggest effect when a relay's
5190 weight adjustments should have given it weight 0, but it got
5191 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5192 - When calculating the fraction of nodes that have descriptors, and
5193 all nodes in the network have zero bandwidths, count the number of
5194 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5195 - Actually log the total bandwidth in compute_weighted_bandwidths().
5196 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5198 o Minor bugfixes (portability, msvc):
5199 - Fix a bug in the bit-counting parts of our timing-wheel code on
5200 MSVC. (Note that MSVC is still not a supported build platform, due
5201 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5204 o Minor bugfixes (relay):
5205 - Make the internal channel_is_client() function look at what sort
5206 of connection handshake the other side used, rather than whether
5207 the other side ever sent a create_fast cell to us. Backports part
5208 of the fixes from bugs 22805 and 24898.
5210 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5211 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5213 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5214 bugfix on 0.2.9.4-alpha.
5217 Changes in version 0.3.2.10 - 2018-03-03
5218 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
5219 backports a number of bugfixes, including important fixes for security
5222 It includes an important security fix for a remote crash attack
5223 against directory authorities, tracked as TROVE-2018-001.
5225 Additionally, it backports a fix for a bug whose severity we have
5226 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
5227 triggered in order to crash relays with a use-after-free pattern. As
5228 such, we are now tracking that bug as TROVE-2018-002 and
5229 CVE-2018-0491, and backporting it to earlier releases. This bug
5230 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
5233 This release also backports our new system for improved resistance to
5234 denial-of-service attacks against relays.
5236 This release also fixes several minor bugs and annoyances from
5239 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5240 today, for the fix to TROVE-2018-002. Directory authorities should
5241 also upgrade. (Relays on earlier versions might want to update too for
5242 the DoS mitigations.)
5244 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5245 - Fix a protocol-list handling bug that could be used to remotely crash
5246 directory authorities with a null-pointer exception. Fixes bug 25074;
5247 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5250 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5251 - Avoid adding the same channel twice in the KIST scheduler pending
5252 list, which could lead to remote denial-of-service use-after-free
5253 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5255 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5256 - Give relays some defenses against the recent network overload. We
5257 start with three defenses (default parameters in parentheses).
5258 First: if a single client address makes too many concurrent
5259 connections (>100), hang up on further connections. Second: if a
5260 single client address makes circuits too quickly (more than 3 per
5261 second, with an allowed burst of 90) while also having too many
5262 connections open (3), refuse new create cells for the next while
5263 (1-2 hours). Third: if a client asks to establish a rendezvous
5264 point to you directly, ignore the request. These defenses can be
5265 manually controlled by new torrc options, but relays will also
5266 take guidance from consensus parameters, so there's no need to
5267 configure anything manually. Implements ticket 24902.
5269 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5270 - Fix an "off by 2" error in counting rendezvous failures on the
5271 onion service side. While we thought we would stop the rendezvous
5272 attempt after one failed circuit, we were actually making three
5273 circuit attempts before giving up. Now switch to a default of 2,
5274 and allow the consensus parameter "hs_service_max_rdv_failures" to
5275 override. Fixes bug 24895; bugfix on 0.0.6.
5276 - New-style (v3) onion services now obey the "max rendezvous circuit
5277 attempts" logic. Previously they would make as many rendezvous
5278 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5279 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5281 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5282 - Add Link protocol version 5 to the supported protocols list. Fixes
5283 bug 25070; bugfix on 0.3.1.1-alpha.
5285 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5286 - Fix a set of false positives where relays would consider
5287 connections to other relays as being client-only connections (and
5288 thus e.g. deserving different link padding schemes) if those
5289 relays fell out of the consensus briefly. Now we look only at the
5290 initial handshake and whether the connection authenticated as a
5291 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5293 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5294 - The scheduler subsystem was failing to promptly notice changes in
5295 consensus parameters, making it harder to switch schedulers
5296 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5298 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5299 - Make our OOM handler aware of the geoip client history cache so it
5300 doesn't fill up the memory. This check is important for IPv6 and
5301 our DoS mitigation subsystem. Closes ticket 25122.
5303 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5304 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5305 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5306 since they neither disabled TLS 1.3 nor enabled any of the
5307 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5308 Closes ticket 24978.
5310 o Minor features (geoip):
5311 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5314 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5315 - When logging a failure to create an onion service's descriptor,
5316 also log what the problem with the descriptor was. Diagnostic
5319 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5320 - Use the actual observed address of an incoming relay connection,
5321 not the canonical address of the relay from its descriptor, when
5322 making decisions about how to handle the incoming connection.
5323 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5325 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5326 - Fix a possible crash on malformed consensus. If a consensus had
5327 contained an unparseable protocol line, it could have made clients
5328 and relays crash with a null-pointer exception. To exploit this
5329 issue, however, an attacker would need to be able to subvert the
5330 directory authority system. Fixes bug 25251; bugfix on
5331 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5333 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5334 - Directory authorities, when refusing a descriptor from a rejected
5335 relay, now explicitly tell the relay (in its logs) to set a valid
5336 ContactInfo address and contact the bad-relays@ mailing list.
5337 Fixes bug 25170; bugfix on 0.2.9.1.
5339 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5340 - When building with Rust on OSX, link against libresolv, to work
5341 around the issue at https://github.com/rust-lang/rust/issues/46797.
5342 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5344 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5345 - Remove a BUG() statement when a client fetches an onion descriptor
5346 that has a lower revision counter than the one in its cache. This
5347 can happen in normal circumstances due to HSDir desync. Fixes bug
5348 24976; bugfix on 0.3.2.1-alpha.
5350 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5351 - Don't treat inability to store a cached consensus object as a bug:
5352 it can happen normally when we are out of disk space. Fixes bug
5353 24859; bugfix on 0.3.1.1-alpha.
5355 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5356 - Improve the performance of our consensus-diff application code
5357 when Tor is built with the --enable-fragile-hardening option set.
5358 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5360 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5361 - Don't exit the Tor process if setrlimit() fails to change the file
5362 limit (which can happen sometimes on some versions of OSX). Fixes
5363 bug 21074; bugfix on 0.0.9pre5.
5365 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5366 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5368 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5369 bugfix on 0.2.9.4-alpha.
5371 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5372 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5373 25005; bugfix on 0.3.2.7-rc.
5375 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5376 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5377 version, when deciding whether a consensus entry can support the
5378 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5379 bugfix on 0.3.2.1-alpha.
5381 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5382 - Update the "rust dependencies" submodule to be a project-level
5383 repository, rather than a user repository. Closes ticket 25323.
5385 o Documentation (backport from 0.3.3.1-alpha)
5386 - Document that operators who run more than one relay or bridge are
5387 expected to set MyFamily and ContactInfo correctly. Closes
5391 Changes in version 0.3.3.3-alpha - 2018-03-03
5392 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
5393 It includes an important security fix for a remote crash attack
5394 against directory authorities tracked as TROVE-2018-001.
5396 Additionally, with this release, we are upgrading the severity of a
5397 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
5398 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
5399 a use-after-free pattern. As such, we are now tracking that bug as
5400 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
5401 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
5403 This release also fixes several minor bugs and annoyances from
5406 Relays running 0.3.2.x should upgrade to one of the versions released
5407 today, for the fix to TROVE-2018-002. Directory authorities should
5408 also upgrade. (Relays on earlier versions might want to update too for
5409 the DoS mitigations.)
5411 o Major bugfixes (denial-of-service, directory authority):
5412 - Fix a protocol-list handling bug that could be used to remotely crash
5413 directory authorities with a null-pointer exception. Fixes bug 25074;
5414 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5417 o Minor features (compatibility, OpenSSL):
5418 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5419 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5420 since they neither disabled TLS 1.3 nor enabled any of the
5421 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5422 Closes ticket 24978.
5424 o Minor features (logging):
5425 - Clarify the log messages produced when getrandom() or a related
5426 entropy-generation mechanism gives an error. Closes ticket 25120.
5428 o Minor features (testing):
5429 - Add a "make test-rust" target to run the rust tests only. Closes
5432 o Minor bugfixes (denial-of-service):
5433 - Fix a possible crash on malformed consensus. If a consensus had
5434 contained an unparseable protocol line, it could have made clients
5435 and relays crash with a null-pointer exception. To exploit this
5436 issue, however, an attacker would need to be able to subvert the
5437 directory authority system. Fixes bug 25251; bugfix on
5438 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5440 o Minor bugfixes (DoS mitigation):
5441 - Add extra safety checks when refilling the circuit creation bucket
5442 to ensure we never set a value above the allowed maximum burst.
5443 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
5444 - When a new consensus arrives, don't update our DoS-mitigation
5445 parameters if we aren't a public relay. Fixes bug 25223; bugfix
5448 o Minor bugfixes (man page, SocksPort):
5449 - Remove dead code from the old "SocksSocket" option, and rename
5450 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
5451 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
5453 o Minor bugfixes (performance):
5454 - Reduce the number of circuits that will be opened at once during
5455 the circuit build timeout phase. This is done by increasing the
5456 idle timeout to 3 minutes, and lowering the maximum number of
5457 concurrent learning circuits to 10. Fixes bug 24769; bugfix
5460 o Minor bugfixes (spec conformance):
5461 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5463 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5464 bugfix on 0.2.9.4-alpha.
5466 o Minor bugfixes (spec conformance, rust):
5467 - Resolve a denial-of-service issue caused by an infinite loop in
5468 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
5469 Also tracked as TROVE-2018-003.
5471 o Code simplification and refactoring:
5472 - Update the "rust dependencies" submodule to be a project-level
5473 repository, rather than a user repository. Closes ticket 25323.
5476 Changes in version 0.3.3.2-alpha - 2018-02-10
5477 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
5478 introduces a mechanism to handle the high loads that many relay
5479 operators have been reporting recently. It also fixes several bugs in
5480 older releases. If this new code proves reliable, we plan to backport
5481 it to older supported release series.
5483 o Major features (denial-of-service mitigation):
5484 - Give relays some defenses against the recent network overload. We
5485 start with three defenses (default parameters in parentheses).
5486 First: if a single client address makes too many concurrent
5487 connections (>100), hang up on further connections. Second: if a
5488 single client address makes circuits too quickly (more than 3 per
5489 second, with an allowed burst of 90) while also having too many
5490 connections open (3), refuse new create cells for the next while
5491 (1-2 hours). Third: if a client asks to establish a rendezvous
5492 point to you directly, ignore the request. These defenses can be
5493 manually controlled by new torrc options, but relays will also
5494 take guidance from consensus parameters, so there's no need to
5495 configure anything manually. Implements ticket 24902.
5497 o Major bugfixes (netflow padding):
5498 - Stop adding unneeded channel padding right after we finish
5499 flushing to a connection that has been trying to flush for many
5500 seconds. Instead, treat all partial or complete flushes as
5501 activity on the channel, which will defer the time until we need
5502 to add padding. This fix should resolve confusing and scary log
5503 messages like "Channel padding timeout scheduled 221453ms in the
5504 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5506 o Major bugfixes (protocol versions):
5507 - Add Link protocol version 5 to the supported protocols list. Fixes
5508 bug 25070; bugfix on 0.3.1.1-alpha.
5510 o Major bugfixes (scheduler, consensus):
5511 - The scheduler subsystem was failing to promptly notice changes in
5512 consensus parameters, making it harder to switch schedulers
5513 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5515 o Minor features (denial-of-service avoidance):
5516 - Make our OOM handler aware of the geoip client history cache so it
5517 doesn't fill up the memory. This check is important for IPv6 and
5518 our DoS mitigation subsystem. Closes ticket 25122.
5520 o Minor features (directory authority):
5521 - When directory authorities are unable to add signatures to a
5522 pending consensus, log the reason why. Closes ticket 24849.
5524 o Minor features (geoip):
5525 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5528 o Minor features (logging, diagnostic):
5529 - When logging a failure to create an onion service's descriptor,
5530 also log what the problem with the descriptor was. Diagnostic for
5533 o Minor bugfix (channel connection):
5534 - Use the actual observed address of an incoming relay connection,
5535 not the canonical address of the relay from its descriptor, when
5536 making decisions about how to handle the incoming connection.
5537 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5539 o Minor bugfix (directory authority):
5540 - Directory authorities, when refusing a descriptor from a rejected
5541 relay, now explicitly tell the relay (in its logs) to set a valid
5542 ContactInfo address and contact the bad-relays@ mailing list.
5543 Fixes bug 25170; bugfix on 0.2.9.1.
5545 o Minor bugfixes (all versions of Tor):
5546 - Use the "misspell" tool to detect and fix typos throughout the
5547 source code. Fixes bug 23650; bugfix on various versions of Tor.
5548 Patch from Deepesh Pathak.
5550 o Minor bugfixes (circuit, cannibalization):
5551 - Don't cannibalize preemptively-built circuits if we no longer
5552 recognize their first hop. This situation can happen if our Guard
5553 relay went off the consensus after the circuit was created. Fixes
5554 bug 24469; bugfix on 0.0.6.
5556 o Minor bugfixes (correctness):
5557 - Remove a nonworking, unnecessary check to see whether a circuit
5558 hop's identity digest was set when the circuit failed. Fixes bug
5559 24927; bugfix on 0.2.4.4-alpha.
5561 o Minor bugfixes (logging):
5562 - Don't treat inability to store a cached consensus object as a bug:
5563 it can happen normally when we are out of disk space. Fixes bug
5564 24859; bugfix on 0.3.1.1-alpha.
5565 - Fix a (mostly harmless) race condition when invoking
5566 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5567 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5569 o Minor bugfixes (onion services):
5570 - Remove a BUG() statement when a client fetches an onion descriptor
5571 that has a lower revision counter than the one in its cache. This
5572 can happen in normal circumstances due to HSDir desync. Fixes bug
5573 24976; bugfix on 0.3.2.1-alpha.
5574 - If we are configured to offer a single onion service, don't log
5575 long-term established one hop rendezvous points in the heartbeat.
5576 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5578 o Minor bugfixes (performance):
5579 - Avoid calling protocol_list_supports_protocol() from inside tight
5580 loops when running with cached routerinfo_t objects. Instead,
5581 summarize the relevant protocols as flags in the routerinfo_t, as
5582 we do for routerstatus_t objects. This change simplifies our code
5583 a little, and saves a large amount of short-term memory allocation
5584 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5586 o Minor bugfixes (Rust FFI):
5587 - Fix a minor memory leak which would happen whenever the C code
5588 would call the Rust implementation of
5589 protover_get_supported_protocols(). This was due to the C version
5590 returning a static string, whereas the Rust version newly allocated
5591 a CString to pass across the FFI boundary. Consequently, the C
5592 code was not expecting to need to free() what it was given. Fixes
5593 bug 25127; bugfix on 0.3.2.1-alpha.
5595 o Minor bugfixes (scheduler, KIST):
5596 - Avoid adding the same channel twice in the KIST scheduler pending
5597 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5600 o Minor bugfixes (unit test, monotonic time):
5601 - Increase a constant (1msec to 10msec) in the monotonic time test
5602 that makes sure the nsec/usec/msec times read are synchronized.
5603 This change was needed to accommodate slow systems like armel or
5604 when the clock_gettime() is not a VDSO on the running kernel.
5605 Fixes bug 25113; bugfix on 0.2.9.1.
5607 o Minor bugfixes (v3 onion services):
5608 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5609 version, when deciding whether a consensus entry can support the
5610 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5611 bugfix on 0.3.2.1-alpha.
5613 o Code simplification and refactoring:
5614 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5616 - Remove a series of counters used to track circuit extend attempts
5617 and connection status but that in reality we aren't using for
5618 anything other than stats logged by a SIGUSR1 signal. Closes
5621 o Documentation (man page):
5622 - The HiddenServiceVersion torrc option accepts only one number:
5623 either version 2 or 3. Closes ticket 25026; bugfix
5627 Changes in version 0.3.3.1-alpha - 2018-01-25
5628 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5629 several new features to Tor, including several improvements to
5630 bootstrapping, and support for an experimental "vanguards" feature to
5631 resist guard discovery attacks. This series also includes better
5632 support for applications that need to embed Tor or manage v3
5635 o Major features (embedding):
5636 - There is now a documented stable API for programs that need to
5637 embed Tor. See tor_api.h for full documentation and known bugs.
5638 Closes ticket 23684.
5639 - Tor now has support for restarting in the same process.
5640 Controllers that run Tor using the "tor_api.h" interface can now
5641 restart Tor after Tor has exited. This support is incomplete,
5642 however: we fixed crash bugs that prevented it from working at
5643 all, but many bugs probably remain, including a possibility of
5644 security issues. Implements ticket 24581.
5646 o Major features (IPv6, directory documents):
5647 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5648 consensus. This information makes it easier for IPv6 clients to
5649 bootstrap and choose reachable entry guards. Implements ticket 23826.
5650 - Add consensus method 28, which removes IPv6 ORPorts from
5651 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5652 are redundant in microdescs. This change will be used by Tor clients
5653 on 0.2.8.x and later. (That is to say, with all Tor clients that
5654 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5655 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5656 set by different numbers of authorities. Fixes 23870
5659 o Major features (onion service v3, control port):
5660 - The control port now supports commands and events for v3 onion
5661 services. It is now possible to create ephemeral v3 services using
5662 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5663 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5664 DEL_ONION) have been extended to support v3 onion services. Closes
5665 ticket 20699; implements proposal 284.
5667 o Major features (onion services):
5668 - Provide torrc options to pin the second and third hops of onion
5669 service circuits to a list of nodes. The option HSLayer2Guards
5670 pins the second hop, and the option HSLayer3Guards pins the third
5671 hop. These options are for use in conjunction with experiments
5672 with "vanguards" for preventing guard enumeration attacks. Closes
5675 o Major features (rust, portability, experimental):
5676 - Tor now ships with an optional implementation of one of its
5677 smaller modules (protover.c) in the Rust programming language. To
5678 try it out, install a Rust build environment, and configure Tor
5679 with "--enable-rust --enable-cargo-online-mode". This should not
5680 cause any user-visible changes, but should help us gain more
5681 experience with Rust, and plan future Rust integration work.
5682 Implementation by Chelsea Komlo. Closes ticket 22840.
5684 o Minor features (storage, configuration):
5685 - Users can store cached directory documents somewhere other than
5686 the DataDirectory by using the CacheDirectory option. Similarly,
5687 the storage location for relay's keys can be overridden with the
5688 KeyDirectory option. Closes ticket 22703.
5690 o Major features (v3 onion services, ipv6):
5691 - When v3 onion service clients send introduce cells, they now
5692 include the IPv6 address of the rendezvous point, if it has one.
5693 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5694 in future Tor versions, IPv6-only v3 single onion services will be
5695 able to use IPv6 addresses to connect directly to the rendezvous
5696 point. Closes ticket 23577. Patch by Neel Chauhan.
5698 o Major bugfixes (onion services, retry behavior):
5699 - Fix an "off by 2" error in counting rendezvous failures on the
5700 onion service side. While we thought we would stop the rendezvous
5701 attempt after one failed circuit, we were actually making three
5702 circuit attempts before giving up. Now switch to a default of 2,
5703 and allow the consensus parameter "hs_service_max_rdv_failures" to
5704 override. Fixes bug 24895; bugfix on 0.0.6.
5705 - New-style (v3) onion services now obey the "max rendezvous circuit
5706 attempts" logic. Previously they would make as many rendezvous
5707 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5708 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5710 o Major bugfixes (relays):
5711 - Fix a set of false positives where relays would consider
5712 connections to other relays as being client-only connections (and
5713 thus e.g. deserving different link padding schemes) if those
5714 relays fell out of the consensus briefly. Now we look only at the
5715 initial handshake and whether the connection authenticated as a
5716 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5718 o Minor feature (IPv6):
5719 - Make IPv6-only clients wait for microdescs for relays, even if we
5720 were previously using descriptors (or were using them as a bridge)
5721 and have a cached descriptor for them. Implements ticket 23827.
5722 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5723 them, rather than waiting to download microdescriptors.
5724 Implements ticket 23827.
5726 o Minor features (cleanup):
5727 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5728 when it stops. Closes ticket 23271.
5730 o Minor features (defensive programming):
5731 - Most of the functions in Tor that free objects have been replaced
5732 with macros that free the objects and set the corresponding
5733 pointers to NULL. This change should help prevent a large class of
5734 dangling pointer bugs. Closes ticket 24337.
5735 - Where possible, the tor_free() macro now only evaluates its input
5736 once. Part of ticket 24337.
5737 - Check that microdesc ed25519 ids are non-zero in
5738 node_get_ed25519_id() before returning them. Implements ticket
5739 24001, patch by "aruna1234".
5741 o Minor features (embedding):
5742 - Tor can now start with a preauthenticated control connection
5743 created by the process that launched it. This feature is meant for
5744 use by programs that want to launch and manage a Tor process
5745 without allowing other programs to manage it as well. For more
5746 information, see the __OwningControllerFD option documented in
5747 control-spec.txt. Closes ticket 23900.
5748 - On most errors that would cause Tor to exit, it now tries to
5749 return from the tor_main() function, rather than calling the
5750 system exit() function. Most users won't notice a difference here,
5751 but it should be significant for programs that run Tor inside
5752 a separate thread: they should now be able to survive Tor's exit
5753 conditions rather than having Tor shut down the entire process.
5754 Closes ticket 23848.
5755 - Applications that want to embed Tor can now tell Tor not to
5756 register any of its own POSIX signal handlers, using the
5757 __DisableSignalHandlers option. Closes ticket 24588.
5759 o Minor features (fallback directory list):
5760 - Avoid selecting fallbacks that change their IP addresses too
5761 often. Select more fallbacks by ignoring the Guard flag, and
5762 allowing lower cutoffs for the Running and V2Dir flags. Also allow
5763 a lower bandwidth, and a higher number of fallbacks per operator
5764 (5% of the list). Implements ticket 24785.
5765 - Update the fallback whitelist and blacklist based on opt-ins and
5766 relay changes. Closes tickets 22321, 24678, 22527, 24135,
5769 o Minor features (fallback directory mirror configuration):
5770 - Add a nickname to each fallback in a C comment. This makes it
5771 easier for operators to find their relays, and allows stem to use
5772 nicknames to identify fallbacks. Implements ticket 24600.
5773 - Add a type and version header to the fallback directory mirror
5774 file. Also add a delimiter to the end of each fallback entry. This
5775 helps external parsers like stem and Relay Search. Implements
5777 - Add an extrainfo cache flag for each fallback in a C comment. This
5778 allows stem to use fallbacks to fetch extra-info documents, rather
5779 than using authorities. Implements ticket 22759.
5780 - Add the generateFallbackDirLine.py script for automatically
5781 generating fallback directory mirror lines from relay fingerprints.
5782 No more typos! Add the lookupFallbackDirContact.py script for
5783 automatically looking up operator contact info from relay
5784 fingerprints. Implements ticket 24706, patch by teor and atagar.
5785 - Reject any fallback directory mirror that serves an expired
5786 consensus. Implements ticket 20942, patch by "minik".
5787 - Remove commas and equals signs from external string inputs to the
5788 fallback list. This avoids format confusion attacks. Implements
5790 - Remove the "weight=10" line from fallback directory mirror
5791 entries. Ticket 24681 will maintain the current fallback weights
5792 by changing Tor's default fallback weight to 10. Implements
5794 - Stop logging excessive information about fallback netblocks.
5795 Implements ticket 24791.
5797 o Minor features (forward-compatibility):
5798 - If a relay supports some link authentication protocol that we do
5799 not recognize, then include that relay's ed25519 key when telling
5800 other relays to extend to it. Previously, we treated future
5801 versions as if they were too old to support ed25519 link
5802 authentication. Closes ticket 20895.
5804 o Minor features (heartbeat):
5805 - Add onion service information to our heartbeat logs, displaying
5806 stats about the activity of configured onion services. Closes
5809 o Minor features (instrumentation, development):
5810 - Add the MainloopStats option to allow developers to get
5811 instrumentation information from the main event loop via the
5812 heartbeat messages. We hope to use this to improve Tor's behavior
5813 when it's trying to sleep. Closes ticket 24605.
5815 o Minor features (log messages):
5816 - Improve a warning message that happens when we fail to re-parse an
5817 old router because of an expired certificate. Closes ticket 20020.
5818 - Make the log more quantitative when we hit MaxMemInQueues
5819 threshold exposing some values. Closes ticket 24501.
5821 o Minor features (logging, android):
5822 - Added support for the Android logging subsystem. Closes
5825 o Minor features (performance):
5826 - Support predictive circuit building for onion service circuits
5827 with multiple layers of guards. Closes ticket 23101.
5828 - Use stdatomic.h where available, rather than mutexes, to implement
5829 atomic_counter_t. Closes ticket 23953.
5831 o Minor features (performance, 32-bit):
5832 - Improve performance on 32-bit systems by avoiding 64-bit division
5833 when calculating the timestamp in milliseconds for channel padding
5834 computations. Implements ticket 24613.
5835 - Improve performance on 32-bit systems by avoiding 64-bit division
5836 when timestamping cells and buffer chunks for OOM calculations.
5837 Implements ticket 24374.
5839 o Minor features (performance, OSX, iOS):
5840 - Use the mach_approximate_time() function (when available) to
5841 implement coarse monotonic time. Having a coarse time function
5842 should avoid a large number of system calls, and improve
5843 performance slightly, especially under load. Closes ticket 24427.
5845 o Minor features (performance, windows):
5846 - Improve performance on Windows Vista and Windows 7 by adjusting
5847 TCP send window size according to the recommendation from
5848 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
5851 o Major features (relay):
5852 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
5853 operator to use a more reasonable ("reduced") exit policy, rather
5854 than the default one. If you want to run an exit node without
5855 thinking too hard about which ports to allow, this one is for you.
5856 Closes ticket 13605. Patch from Neel Chauhan.
5858 o Minor features (testing, debugging, embedding):
5859 - For development purposes, Tor now has a mode in which it runs for
5860 a few seconds, then stops, and starts again without exiting the
5861 process. This mode is meant to help us debug various issues with
5862 ticket 23847. To use this feature, compile with
5863 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
5864 environment variable. This is expected to crash a lot, and is
5865 really meant for developers only. It will likely be removed in a
5866 future release. Implements ticket 24583.
5868 o Minor bugfix (network IPv6 test):
5869 - Tor's test scripts now check if "ping -6 ::1" works when the user
5870 runs "make test-network-all". Fixes bug 24677; bugfix on
5871 0.2.9.3-alpha. Patch by "ffmancera".
5873 o Minor bugfixes (build, rust):
5874 - Fix output of autoconf checks to display success messages for Rust
5875 dependencies and a suitable rustc compiler version. Fixes bug
5876 24612; bugfix on 0.3.1.3-alpha.
5877 - When building with Rust on OSX, link against libresolv, to work
5878 around the issue at https://github.com/rust-lang/rust/issues/46797.
5879 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5880 - Don't pass the --quiet option to cargo: it seems to suppress some
5881 errors, which is not what we want to do when building. Fixes bug
5882 24518; bugfix on 0.3.1.7.
5883 - Build correctly when building from outside Tor's source tree with
5884 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
5887 o Minor bugfixes (directory authorities, IPv6):
5888 - When creating a routerstatus (vote) from a routerinfo (descriptor),
5889 set the IPv6 address to the unspecified IPv6 address, and
5890 explicitly initialize the port to zero. Fixes bug 24488; bugfix
5893 o Minor bugfixes (fallback directory mirrors):
5894 - Make updateFallbackDirs.py search harder for python. (Some OSs
5895 don't put it in /usr/bin.) Fixes bug 24708; bugfix
5898 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
5899 - When hibernating, close connections normally and allow them to
5900 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
5902 - Do not attempt to launch self-reachability tests when entering
5903 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5904 - Resolve several bugs related to descriptor fetching on bridge
5905 clients with bandwidth accounting enabled. (This combination is
5906 not recommended!) Fixes a case of bug 12062; bugfix
5908 - When hibernating, do not attempt to launch DNS checks. Fixes a
5909 case of bug 12062; bugfix on 0.1.2.2-alpha.
5910 - When hibernating, do not try to upload or download descriptors.
5911 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5913 o Minor bugfixes (IPv6, bridges):
5914 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
5915 bugfix on 0.2.8.2-alpha.
5916 - Tor now sets IPv6 address in the routerstatus as well as in the
5917 router descriptors when updating addresses for a bridge. Closes
5918 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
5920 o Minor bugfixes (linux seccomp2 sandbox):
5921 - When running with the sandbox enabled, reload configuration files
5922 correctly even when %include was used. Previously we would crash.
5923 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
5925 o Minor bugfixes (memory leaks):
5926 - Avoid possible at-exit memory leaks related to use of Libevent's
5927 event_base_once() function. (This function tends to leak memory if
5928 the event_base is closed before the event fires.) Fixes bug 24584;
5929 bugfix on 0.2.8.1-alpha.
5930 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
5933 o Minor bugfixes (OSX):
5934 - Don't exit the Tor process if setrlimit() fails to change the file
5935 limit (which can happen sometimes on some versions of OSX). Fixes
5936 bug 21074; bugfix on 0.0.9pre5.
5938 o Minor bugfixes (performance, fragile-hardening):
5939 - Improve the performance of our consensus-diff application code
5940 when Tor is built with the --enable-fragile-hardening option set.
5941 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5943 o Minor bugfixes (performance, timeouts):
5944 - Consider circuits for timeout as soon as they complete a hop. This
5945 is more accurate than applying the timeout in
5946 circuit_expire_building() because that function is only called
5947 once per second, which is now too slow for typical timeouts on the
5948 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
5949 - Use onion service circuits (and other circuits longer than 3 hops)
5950 to calculate a circuit build timeout. Previously, Tor only
5951 calculated its build timeout based on circuits that planned to be
5952 exactly 3 hops long. With this change, we include measurements
5953 from all circuits at the point where they complete their third
5954 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
5956 o Minor bugfixes (testing):
5957 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
5958 bugfix on 0.2.3.1-alpha.
5959 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5960 25005; bugfix on 0.3.2.7-rc.
5962 o Code simplification and refactoring:
5963 - Remove /usr/athena from search path in configure.ac. Closes
5965 - Remove duplicate code in node_has_curve25519_onion_key() and
5966 node_get_curve25519_onion_key(), and add a check for a zero
5967 microdesc curve25519 onion key. Closes ticket 23966, patch by
5968 "aruna1234" and teor.
5969 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
5970 memory allocations with large numbers of OR connections (e.g.
5971 relays). Closes ticket 24119.
5972 - Separate the function that deletes ephemeral files when Tor
5974 - Small changes to Tor's buf_t API to make it suitable for use as a
5975 general-purpose safe string constructor. Closes ticket 22342.
5976 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
5977 avoid source code identifier confusion. Closes ticket 24467.
5978 - The tor_git_revision[] constant no longer needs to be redeclared
5979 by everything that links against the rest of Tor. Done as part of
5980 ticket 23845, to simplify our external API.
5981 - We make extend_info_from_node() use node_get_curve25519_onion_key()
5982 introduced in ticket 23577 to access the curve25519 public keys
5983 rather than accessing it directly. Closes ticket 23760. Patch by
5985 - Add a function to log channels' scheduler state changes to aid
5986 debugging efforts. Closes ticket 24531.
5989 - Add documentation on how to build tor with Rust dependencies
5990 without having to be online. Closes ticket 22907; bugfix
5992 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
5993 traffic. Closes ticket 24318.
5994 - Document that OutboundBindAddress doesn't apply to DNS requests.
5995 Closes ticket 22145. Patch from Aruna Maurya.
5996 - Document that operators who run more than one relay or bridge are
5997 expected to set MyFamily and ContactInfo correctly. Closes
6000 o Code simplification and refactoring (channels):
6001 - Remove the incoming and outgoing channel queues. These were never
6002 used, but still took up a step in our fast path.
6003 - The majority of the channel unit tests have been rewritten and the
6004 code coverage has now been raised to 83.6% for channel.c. Closes
6006 - Remove other dead code from the channel subsystem: All together,
6007 this cleanup has removed more than 1500 lines of code overall and
6008 adding very little except for unit test.
6010 o Code simplification and refactoring (circuit rendezvous):
6011 - Split the client-side rendezvous circuit lookup into two
6012 functions: one that returns only established circuits and another
6013 that returns all kinds of circuits. Closes ticket 23459.
6015 o Code simplification and refactoring (controller):
6016 - Make most of the variables in networkstatus_getinfo_by_purpose()
6017 const. Implements ticket 24489.
6020 Changes in version 0.3.2.9 - 2018-01-09
6021 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
6023 The 0.3.2 series includes our long-anticipated new onion service
6024 design, with numerous security features. (For more information, see
6025 our blog post at https://blog.torproject.org/fall-harvest.) We also
6026 have a new circuit scheduler algorithm for improved performance on
6027 relays everywhere (see https://blog.torproject.org/kist-and-tell),
6028 along with many smaller features and bugfixes.
6030 Per our stable release policy, we plan to support each stable release
6031 series for at least the next nine months, or for three months after
6032 the first stable release of the next series: whichever is longer. If
6033 you need a release with long-term support, we recommend that you stay
6034 with the 0.2.9 series.
6036 Below is a list of the changes since 0.3.2.8-rc. For a list of all
6037 changes since 0.3.1, see the ReleaseNotes file.
6039 o Minor features (fallback directory mirrors):
6040 - The fallback directory list has been re-generated based on the
6041 current status of the network. Tor uses fallback directories to
6042 bootstrap when it doesn't yet have up-to-date directory
6043 information. Closes ticket 24801.
6044 - Make the default DirAuthorityFallbackRate 0.1, so that clients
6045 prefer to bootstrap from fallback directory mirrors. This is a
6046 follow-up to 24679, which removed weights from the default
6047 fallbacks. Implements ticket 24681.
6049 o Minor features (geoip):
6050 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
6053 o Minor bugfixes (address selection):
6054 - When the fascist_firewall_choose_address_ functions don't find a
6055 reachable address, set the returned address to the null address
6056 and port. This is a precautionary measure, because some callers do
6057 not check the return value. Fixes bug 24736; bugfix
6060 o Minor bugfixes (compilation):
6061 - Resolve a few shadowed-variable warnings in the onion service
6062 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
6064 o Minor bugfixes (portability, msvc):
6065 - Fix a bug in the bit-counting parts of our timing-wheel code on
6066 MSVC. (Note that MSVC is still not a supported build platform, due
6067 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
6071 Changes in version 0.3.2.8-rc - 2017-12-21
6072 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
6073 schedulers that had led servers under heavy load to overload their
6074 outgoing connections. All relay operators running earlier 0.3.2.x
6075 versions should upgrade. This version also includes a mitigation for
6076 over-full DESTROY queues leading to out-of-memory conditions: if it
6077 works, we will soon backport it to earlier release series.
6079 This is the second release candidate in the 0.3.2 series. If we find
6080 no new bugs or regression here, then the first stable 0.3.2 release
6081 will be nearly identical to this.
6083 o Major bugfixes (KIST, scheduler):
6084 - The KIST scheduler did not correctly account for data already
6085 enqueued in each connection's send socket buffer, particularly in
6086 cases when the TCP/IP congestion window was reduced between
6087 scheduler calls. This situation lead to excessive per-connection
6088 buffering in the kernel, and a potential memory DoS. Fixes bug
6089 24665; bugfix on 0.3.2.1-alpha.
6091 o Minor features (geoip):
6092 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
6095 o Minor bugfixes (hidden service v3):
6096 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
6097 the probability of reaching a service for a client missing
6098 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
6100 o Minor bugfixes (memory usage):
6101 - When queuing DESTROY cells on a channel, only queue the circuit-id
6102 and reason fields: not the entire 514-byte cell. This fix should
6103 help mitigate any bugs or attacks that fill up these queues, and
6104 free more RAM for other uses. Fixes bug 24666; bugfix
6107 o Minor bugfixes (scheduler, KIST):
6108 - Use a sane write limit for KISTLite when writing onto a connection
6109 buffer instead of using INT_MAX and shoving as much as it can.
6110 Because the OOM handler cleans up circuit queues, we are better
6111 off at keeping them in that queue instead of the connection's
6112 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
6115 Changes in version 0.3.2.7-rc - 2017-12-14
6116 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
6117 including some that could affect reliability or correctness.
6119 This is the first release candidate in the 0.3.2 series. If we find no
6120 new bugs or regression here, then the first stable 0.3.2. release will
6121 be nearly identical to this.
6123 o Major bugfixes (circuit prediction):
6124 - Fix circuit prediction logic so that a client doesn't treat a port
6125 as being "handled" by a circuit if that circuit already has
6126 isolation settings on it. This change should make Tor clients more
6127 responsive by improving their chances of having a pre-created
6128 circuit ready for use when a request arrives. Fixes bug 18859;
6129 bugfix on 0.2.3.3-alpha.
6131 o Minor features (logging):
6132 - Provide better warnings when the getrandom() syscall fails. Closes
6135 o Minor features (portability):
6136 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
6137 (It doesn't yet work with the sandbox enabled.) Closes
6140 o Minor bugfixes (bridge clients, bootstrap):
6141 - Retry directory downloads when we get our first bridge descriptor
6142 during bootstrap or while reconnecting to the network. Keep
6143 retrying every time we get a bridge descriptor, until we have a
6144 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
6145 - Stop delaying bridge descriptor fetches when we have cached bridge
6146 descriptors. Instead, only delay bridge descriptor fetches when we
6147 have at least one reachable bridge. Fixes part of bug 24367;
6148 bugfix on 0.2.0.3-alpha.
6149 - Stop delaying directory fetches when we have cached bridge
6150 descriptors. Instead, only delay bridge descriptor fetches when
6151 all our bridges are definitely unreachable. Fixes part of bug
6152 24367; bugfix on 0.2.0.3-alpha.
6154 o Minor bugfixes (compilation):
6155 - Fix a signed/unsigned comparison warning introduced by our fix to
6156 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6158 o Minor bugfixes (correctness):
6159 - Fix several places in our codebase where a C compiler would be
6160 likely to eliminate a check, based on assuming that undefined
6161 behavior had not happened elsewhere in the code. These cases are
6162 usually a sign of redundant checking or dubious arithmetic. Found
6163 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
6164 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
6167 o Minor bugfixes (onion service v3):
6168 - Fix a race where an onion service would launch a new intro circuit
6169 after closing an old one, but fail to register it before freeing
6170 the previously closed circuit. This bug was making the service
6171 unable to find the established intro circuit and thus not upload
6172 its descriptor, thus making a service unavailable for up to 24
6173 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
6175 o Minor bugfixes (scheduler, KIST):
6176 - Properly set the scheduler state of an unopened channel in the
6177 KIST scheduler main loop. This prevents a harmless but annoying
6178 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
6179 - Avoid a possible integer overflow when computing the available
6180 space on the TCP buffer of a channel. This had no security
6181 implications; but could make KIST allow too many cells on a
6182 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
6183 - Downgrade to "info" a harmless warning about the monotonic time
6184 moving backwards: This can happen on platform not supporting
6185 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6188 Changes in version 0.3.2.6-alpha - 2017-12-01
6189 This version of Tor is the latest in the 0.3.2 alpha series. It
6190 includes fixes for several important security issues. All Tor users
6191 should upgrade to this release, or to one of the other releases coming
6194 o Major bugfixes (security):
6195 - Fix a denial of service bug where an attacker could use a
6196 malformed directory object to cause a Tor instance to pause while
6197 OpenSSL would try to read a passphrase from the terminal. (Tor
6198 instances run without a terminal, which is the case for most Tor
6199 packages, are not impacted.) Fixes bug 24246; bugfix on every
6200 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6201 Found by OSS-Fuzz as testcase 6360145429790720.
6202 - Fix a denial of service issue where an attacker could crash a
6203 directory authority using a malformed router descriptor. Fixes bug
6204 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6206 - When checking for replays in the INTRODUCE1 cell data for a
6207 (legacy) onion service, correctly detect replays in the RSA-
6208 encrypted part of the cell. We were previously checking for
6209 replays on the entire cell, but those can be circumvented due to
6210 the malleability of Tor's legacy hybrid encryption. This fix helps
6211 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6212 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6215 o Major bugfixes (security, onion service v2):
6216 - Fix a use-after-free error that could crash v2 Tor onion services
6217 when they failed to open circuits while expiring introduction
6218 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6219 also tracked as TROVE-2017-013 and CVE-2017-8823.
6221 o Major bugfixes (security, relay):
6222 - When running as a relay, make sure that we never build a path
6223 through ourselves, even in the case where we have somehow lost the
6224 version of our descriptor appearing in the consensus. Fixes part
6225 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6226 as TROVE-2017-012 and CVE-2017-8822.
6227 - When running as a relay, make sure that we never choose ourselves
6228 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6229 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6231 o Minor feature (relay statistics):
6232 - Change relay bandwidth reporting stats interval from 4 hours to 24
6233 hours in order to reduce the efficiency of guard discovery
6234 attacks. Fixes ticket 23856.
6236 o Minor features (directory authority):
6237 - Add an IPv6 address for the "bastet" directory authority. Closes
6240 o Minor bugfixes (client):
6241 - By default, do not enable storage of client-side DNS values. These
6242 values were unused by default previously, but they should not have
6243 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
6246 Changes in version 0.3.1.9 - 2017-12-01:
6247 Tor 0.3.1.9 backports important security and stability fixes from the
6248 0.3.2 development series. All Tor users should upgrade to this
6249 release, or to another of the releases coming out today.
6251 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6252 - Fix a denial of service bug where an attacker could use a
6253 malformed directory object to cause a Tor instance to pause while
6254 OpenSSL would try to read a passphrase from the terminal. (Tor
6255 instances run without a terminal, which is the case for most Tor
6256 packages, are not impacted.) Fixes bug 24246; bugfix on every
6257 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6258 Found by OSS-Fuzz as testcase 6360145429790720.
6259 - Fix a denial of service issue where an attacker could crash a
6260 directory authority using a malformed router descriptor. Fixes bug
6261 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6263 - When checking for replays in the INTRODUCE1 cell data for a
6264 (legacy) onion service, correctly detect replays in the RSA-
6265 encrypted part of the cell. We were previously checking for
6266 replays on the entire cell, but those can be circumvented due to
6267 the malleability of Tor's legacy hybrid encryption. This fix helps
6268 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6269 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6272 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6273 - Fix a use-after-free error that could crash v2 Tor onion services
6274 when they failed to open circuits while expiring introduction
6275 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6276 also tracked as TROVE-2017-013 and CVE-2017-8823.
6278 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6279 - When running as a relay, make sure that we never build a path
6280 through ourselves, even in the case where we have somehow lost the
6281 version of our descriptor appearing in the consensus. Fixes part
6282 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6283 as TROVE-2017-012 and CVE-2017-8822.
6284 - When running as a relay, make sure that we never choose ourselves
6285 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6286 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6288 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6289 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6290 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6291 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6292 identifying and finding a workaround to this bug and to Moritz,
6293 Arthur Edelstein, and Roger for helping to track it down and
6296 o Minor features (bridge):
6297 - Bridges now include notice in their descriptors that they are
6298 bridges, and notice of their distribution status, based on their
6299 publication settings. Implements ticket 18329. For more fine-
6300 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6303 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6304 - Add an IPv6 address for the "bastet" directory authority. Closes
6307 o Minor features (geoip):
6308 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6311 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6312 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6313 relays, to prevent spurious address resolutions and descriptor
6314 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6315 bugfix on in 0.2.8.1-alpha.
6317 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6318 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6319 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6321 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6322 - When a circuit is marked for close, do not attempt to package any
6323 cells for channels on that circuit. Previously, we would detect
6324 this condition lower in the call stack, when we noticed that the
6325 circuit had no attached channel, and log an annoying message.
6326 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6328 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
6329 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6330 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6333 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6334 - Avoid a crash when transitioning from client mode to bridge mode.
6335 Previously, we would launch the worker threads whenever our
6336 "public server" mode changed, but not when our "server" mode
6337 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6340 Changes in version 0.3.0.13 - 2017-12-01
6341 Tor 0.3.0.13 backports important security and stability bugfixes from
6342 later Tor releases. All Tor users should upgrade to this release, or
6343 to another of the releases coming out today.
6345 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6346 2018. If you need a release with long-term support, please stick with
6347 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6349 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6350 - Fix a denial of service bug where an attacker could use a
6351 malformed directory object to cause a Tor instance to pause while
6352 OpenSSL would try to read a passphrase from the terminal. (Tor
6353 instances run without a terminal, which is the case for most Tor
6354 packages, are not impacted.) Fixes bug 24246; bugfix on every
6355 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6356 Found by OSS-Fuzz as testcase 6360145429790720.
6357 - Fix a denial of service issue where an attacker could crash a
6358 directory authority using a malformed router descriptor. Fixes bug
6359 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6361 - When checking for replays in the INTRODUCE1 cell data for a
6362 (legacy) onion service, correctly detect replays in the RSA-
6363 encrypted part of the cell. We were previously checking for
6364 replays on the entire cell, but those can be circumvented due to
6365 the malleability of Tor's legacy hybrid encryption. This fix helps
6366 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6367 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6370 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6371 - Fix a use-after-free error that could crash v2 Tor onion services
6372 when they failed to open circuits while expiring introduction
6373 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6374 also tracked as TROVE-2017-013 and CVE-2017-8823.
6376 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6377 - When running as a relay, make sure that we never build a path
6378 through ourselves, even in the case where we have somehow lost the
6379 version of our descriptor appearing in the consensus. Fixes part
6380 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6381 as TROVE-2017-012 and CVE-2017-8822.
6382 - When running as a relay, make sure that we never choose ourselves
6383 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6384 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6386 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6387 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6388 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6389 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6390 identifying and finding a workaround to this bug and to Moritz,
6391 Arthur Edelstein, and Roger for helping to track it down and
6394 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6395 - Enable a couple of pieces of Windows hardening: one
6396 (HeapEnableTerminationOnCorruption) that has been on-by-default
6397 since Windows 8, and unavailable before Windows 7; and one
6398 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6399 affect us, but shouldn't do any harm. Closes ticket 21953.
6401 o Minor features (bridge, backport from 0.3.1.9):
6402 - Bridges now include notice in their descriptors that they are
6403 bridges, and notice of their distribution status, based on their
6404 publication settings. Implements ticket 18329. For more fine-
6405 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6408 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6409 - Add an IPv6 address for the "bastet" directory authority. Closes
6412 o Minor features (geoip):
6413 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6416 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6417 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6418 relays, to prevent spurious address resolutions and descriptor
6419 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6420 bugfix on in 0.2.8.1-alpha.
6422 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6423 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6424 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6426 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6427 - When a circuit is marked for close, do not attempt to package any
6428 cells for channels on that circuit. Previously, we would detect
6429 this condition lower in the call stack, when we noticed that the
6430 circuit had no attached channel, and log an annoying message.
6431 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6433 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6434 - Avoid a crash when transitioning from client mode to bridge mode.
6435 Previously, we would launch the worker threads whenever our
6436 "public server" mode changed, but not when our "server" mode
6437 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6439 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6440 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6441 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6444 Changes in version 0.2.9.14 - 2017-12-01
6445 Tor 0.3.0.13 backports important security and stability bugfixes from
6446 later Tor releases. All Tor users should upgrade to this release, or
6447 to another of the releases coming out today.
6449 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6450 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6451 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6452 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6453 identifying and finding a workaround to this bug and to Moritz,
6454 Arthur Edelstein, and Roger for helping to track it down and
6457 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6458 - Fix a denial of service bug where an attacker could use a
6459 malformed directory object to cause a Tor instance to pause while
6460 OpenSSL would try to read a passphrase from the terminal. (Tor
6461 instances run without a terminal, which is the case for most Tor
6462 packages, are not impacted.) Fixes bug 24246; bugfix on every
6463 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6464 Found by OSS-Fuzz as testcase 6360145429790720.
6465 - Fix a denial of service issue where an attacker could crash a
6466 directory authority using a malformed router descriptor. Fixes bug
6467 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6469 - When checking for replays in the INTRODUCE1 cell data for a
6470 (legacy) onion service, correctly detect replays in the RSA-
6471 encrypted part of the cell. We were previously checking for
6472 replays on the entire cell, but those can be circumvented due to
6473 the malleability of Tor's legacy hybrid encryption. This fix helps
6474 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6475 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6478 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6479 - Fix a use-after-free error that could crash v2 Tor onion services
6480 when they failed to open circuits while expiring introduction
6481 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6482 also tracked as TROVE-2017-013 and CVE-2017-8823.
6484 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6485 - When running as a relay, make sure that we never build a path
6486 through ourselves, even in the case where we have somehow lost the
6487 version of our descriptor appearing in the consensus. Fixes part
6488 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6489 as TROVE-2017-012 and CVE-2017-8822.
6491 o Minor features (bridge, backport from 0.3.1.9):
6492 - Bridges now include notice in their descriptors that they are
6493 bridges, and notice of their distribution status, based on their
6494 publication settings. Implements ticket 18329. For more fine-
6495 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6498 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6499 - Add an IPv6 address for the "bastet" directory authority. Closes
6502 o Minor features (geoip):
6503 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6506 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6507 - Enable a couple of pieces of Windows hardening: one
6508 (HeapEnableTerminationOnCorruption) that has been on-by-default
6509 since Windows 8, and unavailable before Windows 7; and one
6510 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6511 affect us, but shouldn't do any harm. Closes ticket 21953.
6513 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6514 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6515 relays, to prevent spurious address resolutions and descriptor
6516 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6517 bugfix on in 0.2.8.1-alpha.
6519 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6520 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6521 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6523 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6524 - When a circuit is marked for close, do not attempt to package any
6525 cells for channels on that circuit. Previously, we would detect
6526 this condition lower in the call stack, when we noticed that the
6527 circuit had no attached channel, and log an annoying message.
6528 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6530 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6531 - Avoid a crash when transitioning from client mode to bridge mode.
6532 Previously, we would launch the worker threads whenever our
6533 "public server" mode changed, but not when our "server" mode
6534 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6536 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6537 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6538 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6541 Changes in version 0.2.8.17 - 2017-12-01
6542 Tor 0.2.8.17 backports important security and stability bugfixes from
6543 later Tor releases. All Tor users should upgrade to this release, or
6544 to another of the releases coming out today.
6546 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6547 2018. If you need a release with long-term support, please upgrade with
6548 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6550 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6551 - Fix a denial of service bug where an attacker could use a
6552 malformed directory object to cause a Tor instance to pause while
6553 OpenSSL would try to read a passphrase from the terminal. (Tor
6554 instances run without a terminal, which is the case for most Tor
6555 packages, are not impacted.) Fixes bug 24246; bugfix on every
6556 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6557 Found by OSS-Fuzz as testcase 6360145429790720.
6558 - When checking for replays in the INTRODUCE1 cell data for a
6559 (legacy) onion service, correctly detect replays in the RSA-
6560 encrypted part of the cell. We were previously checking for
6561 replays on the entire cell, but those can be circumvented due to
6562 the malleability of Tor's legacy hybrid encryption. This fix helps
6563 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6564 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6567 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6568 - Fix a use-after-free error that could crash v2 Tor onion services
6569 when they failed to open circuits while expiring introduction
6570 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6571 also tracked as TROVE-2017-013 and CVE-2017-8823.
6573 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6574 - When running as a relay, make sure that we never build a path through
6575 ourselves, even in the case where we have somehow lost the version of
6576 our descriptor appearing in the consensus. Fixes part of bug 21534;
6577 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6580 o Minor features (bridge, backport from 0.3.1.9):
6581 - Bridges now include notice in their descriptors that they are
6582 bridges, and notice of their distribution status, based on their
6583 publication settings. Implements ticket 18329. For more fine-
6584 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6587 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6588 - Add an IPv6 address for the "bastet" directory authority. Closes
6591 o Minor features (geoip):
6592 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6595 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6596 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6597 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6600 Changes in version 0.2.5.16 - 2017-12-01
6601 Tor 0.2.5.13 backports important security and stability bugfixes from
6602 later Tor releases. All Tor users should upgrade to this release, or
6603 to another of the releases coming out today.
6605 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6606 2018. If you need a release with long-term support, please upgrade to
6607 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6609 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6610 - Fix a denial of service bug where an attacker could use a
6611 malformed directory object to cause a Tor instance to pause while
6612 OpenSSL would try to read a passphrase from the terminal. (Tor
6613 instances run without a terminal, which is the case for most Tor
6614 packages, are not impacted.) Fixes bug 24246; bugfix on every
6615 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6616 Found by OSS-Fuzz as testcase 6360145429790720.
6617 - When checking for replays in the INTRODUCE1 cell data for a
6618 (legacy) onion service, correctly detect replays in the RSA-
6619 encrypted part of the cell. We were previously checking for
6620 replays on the entire cell, but those can be circumvented due to
6621 the malleability of Tor's legacy hybrid encryption. This fix helps
6622 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6623 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6626 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6627 - When running as a relay, make sure that we never build a path
6628 through ourselves, even in the case where we have somehow lost the
6629 version of our descriptor appearing in the consensus. Fixes part
6630 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6631 as TROVE-2017-012 and CVE-2017-8822.
6633 o Minor features (bridge, backport from 0.3.1.9):
6634 - Bridges now include notice in their descriptors that they are
6635 bridges, and notice of their distribution status, based on their
6636 publication settings. Implements ticket 18329. For more fine-
6637 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6640 o Minor features (geoip):
6641 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6645 Changes in version 0.3.2.5-alpha - 2017-11-22
6646 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6647 fixes several stability and reliability bugs, including a fix for
6648 intermittent bootstrapping failures that some people have been seeing
6649 since the 0.3.0.x series.
6651 Please test this alpha out -- many of these fixes will soon be
6652 backported to stable Tor versions if no additional bugs are found
6655 o Major bugfixes (bootstrapping):
6656 - Fetch descriptors aggressively whenever we lack enough to build
6657 circuits, regardless of how many descriptors we are missing.
6658 Previously, we would delay launching the fetch when we had fewer
6659 than 15 missing descriptors, even if some of those descriptors
6660 were blocking circuits from building. Fixes bug 23985; bugfix on
6661 0.1.1.11-alpha. The effects of this bug became worse in
6662 0.3.0.3-alpha, when we began treating missing descriptors from our
6663 primary guards as a reason to delay circuits.
6664 - Don't try fetching microdescriptors from relays that have failed
6665 to deliver them in the past. Fixes bug 23817; bugfix
6668 o Minor features (directory authority):
6669 - Make the "Exit" flag assignment only depend on whether the exit
6670 policy allows connections to ports 80 and 443. Previously relays
6671 would get the Exit flag if they allowed connections to one of
6672 these ports and also port 6667. Resolves ticket 23637.
6674 o Minor features (geoip):
6675 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6678 o Minor features (linux seccomp2 sandbox):
6679 - Update the sandbox rules so that they should now work correctly
6680 with Glibc 2.26. Closes ticket 24315.
6682 o Minor features (logging):
6683 - Downgrade a pair of log messages that could occur when an exit's
6684 resolver gave us an unusual (but not forbidden) response. Closes
6686 - Improve the message we log when re-enabling circuit build timeouts
6687 after having received a consensus. Closes ticket 20963.
6689 o Minor bugfixes (compilation):
6690 - Fix a memory leak warning in one of the libevent-related
6691 configuration tests that could occur when manually specifying
6692 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6693 Found and patched by Alex Xu.
6694 - When detecting OpenSSL on Windows from our configure script, make
6695 sure to try linking with the ws2_32 library. Fixes bug 23783;
6696 bugfix on 0.3.2.2-alpha.
6698 o Minor bugfixes (control port, linux seccomp2 sandbox):
6699 - Avoid a crash when attempting to use the seccomp2 sandbox together
6700 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6703 o Minor bugfixes (control port, onion services):
6704 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6705 HS_DESC event when a service is not able to upload a descriptor.
6706 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6708 o Minor bugfixes (directory cache):
6709 - Recover better from empty or corrupt files in the consensus cache
6710 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6711 - When a consensus diff calculation is only partially successful,
6712 only record the successful parts as having succeeded. Partial
6713 success can happen if (for example) one compression method fails
6714 but the others succeed. Previously we misrecorded all the
6715 calculations as having succeeded, which would later cause a
6716 nonfatal assertion failure. Fixes bug 24086; bugfix
6719 o Minor bugfixes (logging):
6720 - Only log once if we notice that KIST support is gone. Fixes bug
6721 24158; bugfix on 0.3.2.1-alpha.
6722 - Suppress a log notice when relay descriptors arrive. We already
6723 have a bootstrap progress for this so no need to log notice
6724 everytime tor receives relay descriptors. Microdescriptors behave
6725 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6727 o Minor bugfixes (network layer):
6728 - When closing a connection via close_connection_immediately(), we
6729 mark it as "not blocked on bandwidth", to prevent later calls from
6730 trying to unblock it, and give it permission to read. This fixes a
6731 backtrace warning that can happen on relays under various
6732 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6734 o Minor bugfixes (onion services):
6735 - The introduction circuit was being timed out too quickly while
6736 waiting for the rendezvous circuit to complete. Keep the intro
6737 circuit around longer instead of timing out and reopening new ones
6738 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6739 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6740 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6742 - Silence a warning about failed v3 onion descriptor uploads that
6743 can happen naturally under certain edge cases. Fixes part of bug
6744 23662; bugfix on 0.3.2.1-alpha.
6746 o Minor bugfixes (tests):
6747 - Fix a memory leak in one of the bridge-distribution test cases.
6748 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
6749 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
6750 to correctly handle cases where a caller gives it an RSA key of
6751 under 160 bits. (This is not actually a bug in Tor itself, but
6752 rather in our fuzzing code.) Fixes bug 24247; bugfix on
6753 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
6756 - Add notes in man page regarding OS support for the various
6757 scheduler types. Attempt to use less jargon in the scheduler
6758 section. Closes ticket 24254.
6761 Changes in version 0.3.2.4-alpha - 2017-11-08
6762 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
6763 It fixes several stability and reliability bugs, especially including
6764 a major reliability issue that has been plaguing fast exit relays in
6767 o Major bugfixes (exit relays, DNS):
6768 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6769 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6770 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6771 identifying and finding a workaround to this bug and to Moritz,
6772 Arthur Edelstein, and Roger for helping to track it down and
6775 o Major bugfixes (scheduler, channel):
6776 - Stop processing scheduled channels if they closed while flushing
6777 cells. This can happen if the write on the connection fails
6778 leading to the channel being closed while in the scheduler loop.
6779 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
6781 o Minor features (logging, scheduler):
6782 - Introduce a SCHED_BUG() function to log extra information about
6783 the scheduler state if we ever catch a bug in the scheduler.
6784 Closes ticket 23753.
6786 o Minor features (removed deprecations):
6787 - The ClientDNSRejectInternalAddresses flag can once again be set in
6788 non-testing Tor networks, so long as they do not use the default
6789 directory authorities. This change also removes the deprecation of
6790 this flag from 0.2.9.2-alpha. Closes ticket 21031.
6792 o Minor features (testing):
6793 - Our fuzzing tests now test the encrypted portions of v3 onion
6794 service descriptors. Implements more of 21509.
6796 o Minor bugfixes (directory client):
6797 - On failure to download directory information, delay retry attempts
6798 by a random amount based on the "decorrelated jitter" algorithm.
6799 Our previous delay algorithm tended to produce extra-long delays
6800 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
6802 o Minor bugfixes (IPv6, v3 single onion services):
6803 - Remove buggy code for IPv6-only v3 single onion services, and
6804 reject attempts to configure them. This release supports IPv4,
6805 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
6806 stack v3 single onion services. Fixes bug 23820; bugfix
6809 o Minor bugfixes (logging, relay):
6810 - Give only a protocol warning when the ed25519 key is not
6811 consistent between the descriptor and microdescriptor of a relay.
6812 This can happen, for instance, if the relay has been flagged
6813 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
6815 o Minor bugfixes (manpage, onion service):
6816 - Document that the HiddenServiceNumIntroductionPoints option is
6817 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
6818 bugfix on 0.3.2.1-alpha.
6820 o Minor bugfixes (memory leaks):
6821 - Fix a minor memory leak at exit in the KIST scheduler. This bug
6822 should have no user-visible impact. Fixes bug 23774; bugfix
6824 - Fix a memory leak when decrypting a badly formatted v3 onion
6825 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
6826 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
6828 o Minor bugfixes (onion services):
6829 - Cache some needed onion service client information instead of
6830 constantly computing it over and over again. Fixes bug 23623;
6831 bugfix on 0.3.2.1-alpha.
6832 - Properly retry HSv3 descriptor fetches when missing required
6833 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
6835 o Minor bugfixes (path selection):
6836 - When selecting relays by bandwidth, avoid a rounding error that
6837 could sometimes cause load to be imbalanced incorrectly.
6838 Previously, we would always round upwards; now, we round towards
6839 the nearest integer. This had the biggest effect when a relay's
6840 weight adjustments should have given it weight 0, but it got
6841 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
6842 - When calculating the fraction of nodes that have descriptors, and
6843 all nodes in the network have zero bandwidths, count the number of
6844 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
6845 - Actually log the total bandwidth in compute_weighted_bandwidths().
6846 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
6848 o Minor bugfixes (relay, crash):
6849 - Avoid a crash when transitioning from client mode to bridge mode.
6850 Previously, we would launch the worker threads whenever our
6851 "public server" mode changed, but not when our "server" mode
6852 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6854 o Minor bugfixes (testing):
6855 - Fix a spurious fuzzing-only use of an uninitialized value. Found
6856 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
6857 - Test that IPv6-only clients can use microdescriptors when running
6858 "make test-network-all". Requires chutney master 61c28b9 or later.
6859 Closes ticket 24109.
6862 Changes in version 0.3.2.3-alpha - 2017-10-27
6863 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
6864 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
6865 directory authority, Bastet.
6867 o Directory authority changes:
6868 - Add "Bastet" as a ninth directory authority to the default list.
6869 Closes ticket 23910.
6870 - The directory authority "Longclaw" has changed its IP address.
6871 Closes ticket 23592.
6873 o Minor features (bridge):
6874 - Bridge relays can now set the BridgeDistribution config option to
6875 add a "bridge-distribution-request" line to their bridge
6876 descriptor, which tells BridgeDB how they'd like their bridge
6877 address to be given out. (Note that as of Oct 2017, BridgeDB does
6878 not yet implement this feature.) As a side benefit, this feature
6879 provides a way to distinguish bridge descriptors from non-bridge
6880 descriptors. Implements tickets 18329.
6882 o Minor features (client, entry guards):
6883 - Improve log messages when missing descriptors for primary guards.
6884 Resolves ticket 23670.
6886 o Minor features (geoip):
6887 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6890 o Minor bugfixes (bridge):
6891 - Overwrite the bridge address earlier in the process of retrieving
6892 its descriptor, to make sure we reach it on the configured
6893 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
6895 o Minor bugfixes (documentation):
6896 - Document better how to read gcov, and what our gcov postprocessing
6897 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
6899 o Minor bugfixes (entry guards):
6900 - Tor now updates its guard state when it reads a consensus
6901 regardless of whether it's missing descriptors. That makes tor use
6902 its primary guards to fetch descriptors in some edge cases where
6903 it would previously have used fallback directories. Fixes bug
6904 23862; bugfix on 0.3.0.1-alpha.
6906 o Minor bugfixes (hidden service client):
6907 - When handling multiple SOCKS request for the same .onion address,
6908 only fetch the service descriptor once.
6909 - When a descriptor fetch fails with a non-recoverable error, close
6910 all pending SOCKS requests for that .onion. Fixes bug 23653;
6911 bugfix on 0.3.2.1-alpha.
6913 o Minor bugfixes (hidden service):
6914 - Always regenerate missing hidden service public key files. Prior
6915 to this, if the public key was deleted from disk, it wouldn't get
6916 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
6918 - Make sure that we have a usable ed25519 key when the intro point
6919 relay supports ed25519 link authentication. Fixes bug 24002;
6920 bugfix on 0.3.2.1-alpha.
6922 o Minor bugfixes (hidden service, v2):
6923 - When reloading configured hidden services, copy all information
6924 from the old service object. Previously, some data was omitted,
6925 causing delays in descriptor upload, and other bugs. Fixes bug
6926 23790; bugfix on 0.2.1.9-alpha.
6928 o Minor bugfixes (memory safety, defensive programming):
6929 - Clear the target address when node_get_prim_orport() returns
6930 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6932 o Minor bugfixes (relay):
6933 - Avoid a BUG warning when receiving a dubious CREATE cell while an
6934 option transition is in progress. Fixes bug 23952; bugfix
6937 o Minor bugfixes (testing):
6938 - Adjust the GitLab CI configuration to more closely match that of
6939 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
6940 - Prevent scripts/test/coverage from attempting to move gcov output
6941 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
6942 - When running unit tests as root, skip a test that would fail
6943 because it expects a permissions error. This affects some
6944 continuous integration setups. Fixes bug 23758; bugfix
6946 - Stop unconditionally mirroring the tor repository in GitLab CI.
6947 This prevented developers from enabling GitLab CI on master. Fixes
6948 bug 23755; bugfix on 0.3.2.2-alpha.
6949 - Fix the hidden service v3 descriptor decoding fuzzing to use the
6950 latest decoding API correctly. Fixes bug 21509; bugfix
6953 o Minor bugfixes (warnings):
6954 - When we get an HTTP request on a SOCKS port, tell the user about
6955 the new HTTPTunnelPort option. Previously, we would give a "Tor is
6956 not an HTTP Proxy" message, which stopped being true when
6957 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
6961 Changes in version 0.2.5.15 - 2017-10-25
6962 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6963 series. It also adds a new directory authority, Bastet.
6965 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6966 2018. If you need a release with long-term support, please upgrade to
6967 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6969 o Directory authority changes:
6970 - Add "Bastet" as a ninth directory authority to the default list.
6971 Closes ticket 23910.
6972 - The directory authority "Longclaw" has changed its IP address.
6973 Closes ticket 23592.
6975 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6976 - Avoid an assertion failure bug affecting our implementation of
6977 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6978 handling of "0xx" differs from what we had expected. Fixes bug
6979 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6981 o Minor features (geoip):
6982 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6985 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6986 - Fix a memset() off the end of an array when packing cells. This
6987 bug should be harmless in practice, since the corrupted bytes are
6988 still in the same structure, and are always padding bytes,
6989 ignored, or immediately overwritten, depending on compiler
6990 behavior. Nevertheless, because the memset()'s purpose is to make
6991 sure that any other cell-handling bugs can't expose bytes to the
6992 network, we need to fix it. Fixes bug 22737; bugfix on
6993 0.2.4.11-alpha. Fixes CID 1401591.
6995 o Build features (backport from 0.3.1.5-alpha):
6996 - Tor's repository now includes a Travis Continuous Integration (CI)
6997 configuration file (.travis.yml). This is meant to help new
6998 developers and contributors who fork Tor to a Github repository be
6999 better able to test their changes, and understand what we expect
7000 to pass. To use this new build feature, you must fork Tor to your
7001 Github account, then go into the "Integrations" menu in the
7002 repository settings for your fork and enable Travis, then push
7003 your changes. Closes ticket 22636.
7006 Changes in version 0.2.8.16 - 2017-10-25
7007 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
7008 series, including a bugfix for a crash issue that had affected relays
7009 under memory pressure. It also adds a new directory authority, Bastet.
7011 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
7012 2018. If you need a release with long-term support, please stick with
7013 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7015 o Directory authority changes:
7016 - Add "Bastet" as a ninth directory authority to the default list.
7017 Closes ticket 23910.
7018 - The directory authority "Longclaw" has changed its IP address.
7019 Closes ticket 23592.
7021 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7022 - Fix a timing-based assertion failure that could occur when the
7023 circuit out-of-memory handler freed a connection's output buffer.
7024 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7026 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7027 - Remove longclaw's IPv6 address, as it will soon change. Authority
7028 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7029 3/8 directory authorities with IPv6 addresses, but there are also
7030 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7032 o Minor features (geoip):
7033 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7037 Changes in version 0.2.9.13 - 2017-10-25
7038 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
7039 series, including a bugfix for a crash issue that had affected relays
7040 under memory pressure. It also adds a new directory authority, Bastet.
7042 o Directory authority changes:
7043 - Add "Bastet" as a ninth directory authority to the default list.
7044 Closes ticket 23910.
7045 - The directory authority "Longclaw" has changed its IP address.
7046 Closes ticket 23592.
7048 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7049 - Fix a timing-based assertion failure that could occur when the
7050 circuit out-of-memory handler freed a connection's output buffer.
7051 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7053 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7054 - Remove longclaw's IPv6 address, as it will soon change. Authority
7055 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7056 3/8 directory authorities with IPv6 addresses, but there are also
7057 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7059 o Minor features (geoip):
7060 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7063 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7064 - When a directory authority rejects a descriptor or extrainfo with
7065 a given digest, mark that digest as undownloadable, so that we do
7066 not attempt to download it again over and over. We previously
7067 tried to avoid downloading such descriptors by other means, but we
7068 didn't notice if we accidentally downloaded one anyway. This
7069 behavior became problematic in 0.2.7.2-alpha, when authorities
7070 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7073 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7074 - Clear the address when node_get_prim_orport() returns early.
7075 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7077 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7078 - When running as a Windows service, set the ID of the main thread
7079 correctly. Failure to do so made us fail to send log messages to
7080 the controller in 0.2.1.16-rc, slowed down controller event
7081 delivery in 0.2.7.3-rc and later, and crash with an assertion
7082 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7083 Patch and diagnosis from "Vort".
7086 Changes in version 0.3.0.12 - 2017-10-25
7087 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
7088 series, including a bugfix for a crash issue that had affected relays
7089 under memory pressure. It also adds a new directory authority, Bastet.
7091 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
7092 2018. If you need a release with long-term support, please stick with
7093 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7095 o Directory authority changes:
7096 - Add "Bastet" as a ninth directory authority to the default list.
7097 Closes ticket 23910.
7098 - The directory authority "Longclaw" has changed its IP address.
7099 Closes ticket 23592.
7101 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7102 - Fix a timing-based assertion failure that could occur when the
7103 circuit out-of-memory handler freed a connection's output buffer.
7104 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7106 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7107 - Remove longclaw's IPv6 address, as it will soon change. Authority
7108 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7109 3/8 directory authorities with IPv6 addresses, but there are also
7110 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7112 o Minor features (geoip):
7113 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7116 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7117 - When a directory authority rejects a descriptor or extrainfo with
7118 a given digest, mark that digest as undownloadable, so that we do
7119 not attempt to download it again over and over. We previously
7120 tried to avoid downloading such descriptors by other means, but we
7121 didn't notice if we accidentally downloaded one anyway. This
7122 behavior became problematic in 0.2.7.2-alpha, when authorities
7123 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7126 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7127 - Avoid a possible double close of a circuit by the intro point on
7128 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7129 bugfix on 0.3.0.1-alpha.
7131 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7132 - Clear the address when node_get_prim_orport() returns early.
7133 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7135 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7136 - When running as a Windows service, set the ID of the main thread
7137 correctly. Failure to do so made us fail to send log messages to
7138 the controller in 0.2.1.16-rc, slowed down controller event
7139 delivery in 0.2.7.3-rc and later, and crash with an assertion
7140 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7141 Patch and diagnosis from "Vort".
7144 Changes in version 0.3.1.8 - 2017-10-25
7145 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7146 It includes several bugfixes, including a bugfix for a crash issue
7147 that had affected relays under memory pressure. It also adds
7148 a new directory authority, Bastet.
7150 o Directory authority changes:
7151 - Add "Bastet" as a ninth directory authority to the default list.
7152 Closes ticket 23910.
7153 - The directory authority "Longclaw" has changed its IP address.
7154 Closes ticket 23592.
7156 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7157 - Fix a timing-based assertion failure that could occur when the
7158 circuit out-of-memory handler freed a connection's output buffer.
7159 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7161 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7162 - Remove longclaw's IPv6 address, as it will soon change. Authority
7163 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7164 3/8 directory authorities with IPv6 addresses, but there are also
7165 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7167 o Minor features (geoip):
7168 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7171 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
7172 - Fix a compilation warning when building with zstd support on
7173 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7174 and fixed by Andreas Stieger.
7176 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
7177 - Handle a pathological case when decompressing Zstandard data when
7178 the output buffer size is zero. Fixes bug 23551; bugfix
7181 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
7182 - Remove the length limit on HTTP status lines that authorities can
7183 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
7185 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7186 - Avoid a possible double close of a circuit by the intro point on
7187 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7188 bugfix on 0.3.0.1-alpha.
7190 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7191 - Clear the address when node_get_prim_orport() returns early.
7192 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7194 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
7195 - Fix additional channelpadding unit test failures by using mocked
7196 time instead of actual time for all tests. Fixes bug 23608; bugfix
7200 Changes in version 0.3.2.2-alpha - 2017-09-29
7201 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
7202 release fixes several minor bugs in the new scheduler and next-
7203 generation onion services; both features were newly added in the 0.3.2
7204 series. Other fixes in this alpha include several fixes for non-fatal
7205 tracebacks which would appear in logs.
7207 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
7208 alpha does not contain any substantial new features. Minor features
7209 include better testing and logging.
7211 The following comprises the complete list of changes included
7214 o Major bugfixes (relay, crash, assertion failure):
7215 - Fix a timing-based assertion failure that could occur when the
7216 circuit out-of-memory handler freed a connection's output buffer.
7217 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7219 o Major bugfixes (scheduler):
7220 - If a channel is put into the scheduler's pending list, then it
7221 starts closing, and then if the scheduler runs before it finishes
7222 closing, the scheduler will get stuck trying to flush its cells
7223 while the lower layers refuse to cooperate. Fix that race
7224 condition by giving the scheduler an escape method. Fixes bug
7225 23676; bugfix on 0.3.2.1-alpha.
7227 o Minor features (build, compilation):
7228 - The "check-changes" feature is now part of the "make check" tests;
7229 we'll use it to try to prevent misformed changes files from
7230 accumulating. Closes ticket 23564.
7231 - Tor builds should now fail if there are any mismatches between the
7232 C type representing a configuration variable and the C type the
7233 data-driven parser uses to store a value there. Previously, we
7234 needed to check these by hand, which sometimes led to mistakes.
7235 Closes ticket 23643.
7237 o Minor features (directory authorities):
7238 - Remove longclaw's IPv6 address, as it will soon change. Authority
7239 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7240 3/8 directory authorities with IPv6 addresses, but there are also
7241 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7243 o Minor features (hidden service, circuit, logging):
7244 - Improve logging of many callsite in the circuit subsystem to print
7245 the circuit identifier(s).
7246 - Log when we cleanup an intro point from a service so we know when
7247 and for what reason it happened. Closes ticket 23604.
7249 o Minor features (logging):
7250 - Log more circuit information whenever we are about to try to
7251 package a relay cell on a circuit with a nonexistent n_chan.
7252 Attempt to diagnose ticket 8185.
7253 - Improve info-level log identification of particular circuits, to
7254 help with debugging. Closes ticket 23645.
7256 o Minor features (relay):
7257 - When choosing which circuits can be expired as unused, consider
7258 circuits from clients even if those clients used regular CREATE
7259 cells to make them; and do not consider circuits from relays even
7260 if they were made with CREATE_FAST. Part of ticket 22805.
7262 o Minor features (robustness):
7263 - Change several fatal assertions when flushing buffers into non-
7264 fatal assertions, to prevent any recurrence of 23690.
7266 o Minor features (spec conformance, bridge, diagnostic):
7267 - When handling the USERADDR command on an ExtOrPort, warn when the
7268 transports provides a USERADDR with no port. In a future version,
7269 USERADDR commands of this format may be rejected. Detects problems
7270 related to ticket 23080.
7272 o Minor features (testing):
7273 - Add a unit test to make sure that our own generated platform
7274 string will be accepted by directory authorities. Closes
7277 o Minor bugfixes (bootstrapping):
7278 - When warning about state file clock skew, report the correct
7279 direction for the detected skew. Fixes bug 23606; bugfix
7281 - Avoid an assertion failure when logging a state file clock skew
7282 very early in bootstrapping. Fixes bug 23607; bugfix
7285 o Minor bugfixes (build, compilation):
7286 - Fix a compilation warning when building with zstd support on
7287 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7288 and fixed by Andreas Stieger.
7289 - When searching for OpenSSL, don't accept any OpenSSL library that
7290 lacks TLSv1_1_method(): Tor doesn't build with those versions.
7291 Additionally, look in /usr/local/opt/openssl, if it's present.
7292 These changes together repair the default build on OSX systems
7293 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
7295 o Minor bugfixes (compression):
7296 - Handle a pathological case when decompressing Zstandard data when
7297 the output buffer size is zero. Fixes bug 23551; bugfix
7300 o Minor bugfixes (documentation):
7301 - Fix manpage to not refer to the obsolete (and misspelled)
7302 UseEntryGuardsAsDirectoryGuards parameter in the description of
7303 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
7305 o Minor bugfixes (hidden service v3):
7306 - Don't log an assertion failure when we can't find the right
7307 information to extend to an introduction point. In rare cases,
7308 this could happen, causing a warning, even though tor would
7309 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
7310 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
7311 much bigger so the rendezvous point can't distinguish which hidden
7312 service protocol is being used. Fixes bug 23420; bugfix
7315 o Minor bugfixes (hidden service, relay):
7316 - Avoid a possible double close of a circuit by the intro point on
7317 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7318 bugfix on 0.3.0.1-alpha.
7320 o Minor bugfixes (logging, relay shutdown, annoyance):
7321 - When a circuit is marked for close, do not attempt to package any
7322 cells for channels on that circuit. Previously, we would detect
7323 this condition lower in the call stack, when we noticed that the
7324 circuit had no attached channel, and log an annoying message.
7325 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
7327 o Minor bugfixes (scheduler):
7328 - When switching schedulers due to a consensus change, we didn't
7329 give the new scheduler a chance to react to the consensus. Fix
7330 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
7331 - Make the KISTSchedRunInterval option a non negative value. With
7332 this, the way to disable KIST through the consensus is to set it
7333 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
7334 - Only notice log the selected scheduler when we switch scheduler
7335 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
7336 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
7337 by a different tv_usec data type. Fixes bug 23575; bugfix
7339 - Make a hard exit if tor is unable to pick a scheduler which can
7340 happen if the user specifies a scheduler type that is not
7341 supported and not other types in Schedulers. Fixes bug 23581;
7342 bugfix on 0.3.2.1-alpha.
7343 - Properly initialize the scheduler last run time counter so it is
7344 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
7346 o Minor bugfixes (testing):
7347 - Capture and detect several "Result does not fit" warnings in unit
7348 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
7350 - Fix additional channelpadding unit test failures by using mocked
7351 time instead of actual time for all tests. Fixes bug 23608; bugfix
7353 - The removal of some old scheduler options caused some tests to
7354 fail on BSD systems. Assume current behavior is correct and make
7355 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
7357 o Code simplification and refactoring:
7358 - Remove various ways of testing circuits and connections for
7359 "clientness"; instead, favor channel_is_client(). Part of
7362 o Deprecated features:
7363 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
7364 now deprecated; they do not apply to relays, and they have had no
7365 effect on clients since 0.2.8.x. Closes ticket 19704.
7368 - HiddenServiceVersion man page entry wasn't mentioning the now
7369 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
7370 - Clarify that the Address option is entirely about setting an
7371 advertised IPv4 address. Closes ticket 18891.
7372 - Clarify the manpage's use of the term "address" to clarify what
7373 kind of address is intended. Closes ticket 21405.
7374 - Document that onion service subdomains are allowed, and ignored.
7375 Closes ticket 18736.
7378 Changes in version 0.3.2.1-alpha - 2017-09-18
7379 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
7380 includes support for our next-generation ("v3") onion service
7381 protocol, and adds a new circuit scheduler for more responsive
7382 forwarding decisions from relays. There are also numerous other small
7383 features and bugfixes here.
7385 Below are the changes since Tor 0.3.1.7.
7387 o Major feature (scheduler, channel):
7388 - Tor now uses new schedulers to decide which circuits should
7389 deliver cells first, in order to improve congestion at relays. The
7390 first type is called "KIST" ("Kernel Informed Socket Transport"),
7391 and is only available on Linux-like systems: it uses feedback from
7392 the kernel to prevent the kernel's TCP buffers from growing too
7393 full. The second new scheduler type is called "KISTLite": it
7394 behaves the same as KIST, but runs on systems without kernel
7395 support for inspecting TCP implementation details. The old
7396 scheduler is still available, under the name "Vanilla". To change
7397 the default scheduler preference order, use the new "Schedulers"
7398 option. (The default preference order is "KIST,KISTLite,Vanilla".)
7400 Matt Traudt implemented KIST, based on research by Rob Jansen,
7401 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
7402 more information, see the design paper at
7403 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
7404 followup implementation paper at https://arxiv.org/abs/1709.01044.
7405 Closes ticket 12541.
7407 o Major features (next-generation onion services):
7408 - Tor now supports the next-generation onion services protocol for
7409 clients and services! As part of this release, the core of
7410 proposal 224 has been implemented and is available for
7411 experimentation and testing by our users. This newer version of
7412 onion services ("v3") features many improvements over the legacy
7415 a) Better crypto (replaced SHA1/DH/RSA1024
7416 with SHA3/ed25519/curve25519)
7418 b) Improved directory protocol, leaking much less information to
7421 c) Improved directory protocol, with smaller surface for
7424 d) Better onion address security against impersonation.
7426 e) More extensible introduction/rendezvous protocol.
7428 f) A cleaner and more modular codebase.
7430 You can identify a next-generation onion address by its length:
7431 they are 56 characters long, as in
7432 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
7434 In the future, we will release more options and features for v3
7435 onion services, but we first need a testing period, so that the
7436 current codebase matures and becomes more robust. Planned features
7437 include: offline keys, advanced client authorization, improved
7438 guard algorithms, and statistics. For full details, see
7441 Legacy ("v2") onion services will still work for the foreseeable
7442 future, and will remain the default until this new codebase gets
7443 tested and hardened. Service operators who want to experiment with
7444 the new system can use the 'HiddenServiceVersion 3' torrc
7445 directive along with the regular onion service configuration
7446 options. We will publish a blog post about this new feature
7449 o Major bugfixes (usability, control port):
7450 - Report trusted clock skew indications as bootstrap errors, so
7451 controllers can more easily alert users when their clocks are
7452 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
7454 o Minor features (bug detection):
7455 - Log a warning message with a stack trace for any attempt to call
7456 get_options() during option validation. This pattern has caused
7457 subtle bugs in the past. Closes ticket 22281.
7459 o Minor features (client):
7460 - You can now use Tor as a tunneled HTTP proxy: use the new
7461 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
7462 requests. Closes ticket 22407.
7463 - Add an extra check to make sure that we always use the newer guard
7464 selection code for picking our guards. Closes ticket 22779.
7465 - When downloading (micro)descriptors, don't split the list into
7466 multiple requests unless we want at least 32 descriptors.
7467 Previously, we split at 4, not 32, which led to significant
7468 overhead in HTTP request size and degradation in compression
7469 performance. Closes ticket 23220.
7471 o Minor features (command line):
7472 - Add a new commandline option, --key-expiration, which prints when
7473 the current signing key is going to expire. Implements ticket
7474 17639; patch by Isis Lovecruft.
7476 o Minor features (control port):
7477 - If an application tries to use the control port as an HTTP proxy,
7478 respond with a meaningful "This is the Tor control port" message,
7479 and log the event. Closes ticket 1667. Patch from Ravi
7481 - Provide better error message for GETINFO desc/(id|name) when not
7482 fetching router descriptors. Closes ticket 5847. Patch by
7484 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
7485 whether Tor will try to download router descriptors and
7486 microdescriptors respectively. Closes ticket 22684.
7487 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
7488 so controllers can tell whether the geoip databases are loaded.
7489 Closes ticket 23237.
7490 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
7491 events. Closes ticket 19254. Patch by "DonnchaC".
7493 o Minor features (development support):
7494 - Developers can now generate a call-graph for Tor using the
7495 "calltool" python program, which post-processes object dumps. It
7496 should work okay on many Linux and OSX platforms, and might work
7497 elsewhere too. To run it, install calltool from
7498 https://gitweb.torproject.org/user/nickm/calltool.git and run
7499 "make callgraph". Closes ticket 19307.
7501 o Minor features (ed25519):
7502 - Add validation function to checks for torsion components in
7503 ed25519 public keys, used by prop224 client-side code. Closes
7504 ticket 22006. Math help by Ian Goldberg.
7506 o Minor features (exit relay, DNS):
7507 - Improve the clarity and safety of the log message from evdns when
7508 receiving an apparently spoofed DNS reply. Closes ticket 3056.
7510 o Minor features (integration, hardening):
7511 - Add a new NoExec option to prevent Tor from running other
7512 programs. When this option is set to 1, Tor will never try to run
7513 another program, regardless of the settings of
7514 PortForwardingHelper, ClientTransportPlugin, or
7515 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
7516 without restarting Tor. Closes ticket 22976.
7518 o Minor features (logging):
7519 - Improve the warning message for specifying a relay by nickname.
7520 The previous message implied that nickname registration was still
7521 part of the Tor network design, which it isn't. Closes
7523 - If the sandbox filter fails to load, suggest to the user that
7524 their kernel might not support seccomp2. Closes ticket 23090.
7526 o Minor features (portability):
7527 - Check at configure time whether uint8_t is the same type as
7528 unsigned char. Lots of existing code already makes this
7529 assumption, and there could be strict aliasing issues if the
7530 assumption is violated. Closes ticket 22410.
7532 o Minor features (relay, configuration):
7533 - Reject attempts to use relative file paths when RunAsDaemon is
7534 set. Previously, Tor would accept these, but the directory-
7535 changing step of RunAsDaemon would give strange and/or confusing
7536 results. Closes ticket 22731.
7538 o Minor features (startup, safety):
7539 - When configured to write a PID file, Tor now exits if it is unable
7540 to do so. Previously, it would warn and continue. Closes
7543 o Minor features (static analysis):
7544 - The BUG() macro has been changed slightly so that Coverity no
7545 longer complains about dead code if the bug is impossible. Closes
7548 o Minor features (testing):
7549 - The default chutney network tests now include tests for the v3
7550 hidden service design. Make sure you have the latest version of
7551 chutney if you want to run these. Closes ticket 22437.
7552 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7553 service descriptor. Closes ticket 15554.
7555 o Minor bugfixes (certificate handling):
7556 - Fix a time handling bug in Tor certificates set to expire after
7557 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7558 Coverity as CID 1415728.
7560 o Minor bugfixes (client, usability):
7561 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7562 SOCKS4a requests that contain IP address strings, even when
7563 SafeSocks in enabled, as this prevents user from connecting to
7564 known IP addresses without relying on DNS for resolving. SafeSocks
7565 still rejects SOCKS connections that connect to IP addresses when
7566 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7567 bugfix on Tor 0.2.6.2-alpha.
7569 o Minor bugfixes (code correctness):
7570 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7571 Previously we used ntohs(), which happens to behave the same on
7572 all the platforms we support, but which isn't really correct.
7573 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7574 - For defense-in-depth, make the controller's write_escaped_data()
7575 function robust to extremely long inputs. Fixes bug 19281; bugfix
7576 on 0.1.1.1-alpha. Reported by Guido Vranken.
7578 o Minor bugfixes (compilation):
7579 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7580 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7582 o Minor bugfixes (consensus expiry):
7583 - Check for adequate directory information correctly. Previously, Tor
7584 would reconsider whether it had sufficient directory information
7585 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7587 o Minor bugfixes (directory protocol):
7588 - Directory servers now include a "Date:" http header for response
7589 codes other than 200. Clients starting with a skewed clock and a
7590 recent consensus were getting "304 Not modified" responses from
7591 directory authorities, so without the Date header, the client
7592 would never hear about a wrong clock. Fixes bug 23499; bugfix
7594 - Make clients wait for 6 seconds before trying to download a
7595 consensus from an authority. Fixes bug 17750; bugfix
7598 o Minor bugfixes (DoS-resistance):
7599 - If future code asks if there are any running bridges, without
7600 checking if bridges are enabled, log a BUG warning rather than
7601 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7603 o Minor bugfixes (format strictness):
7604 - Restrict several data formats to decimal. Previously, the
7605 BuildTimeHistogram entries in the state file, the "bw=" entries in
7606 the bandwidth authority file, and the process IDs passed to the
7607 __OwningControllerProcess option could all be specified in hex or
7608 octal as well as in decimal. This was not an intentional feature.
7609 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7612 o Minor bugfixes (heartbeat):
7613 - If we fail to write a heartbeat message, schedule a retry for the
7614 minimum heartbeat interval number of seconds in the future. Fixes
7615 bug 19476; bugfix on 0.2.3.1-alpha.
7617 o Minor bugfixes (linux seccomp2 sandbox, logging):
7618 - Fix some messages on unexpected errors from the seccomp2 library.
7619 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7621 o Minor bugfixes (logging):
7622 - Remove duplicate log messages regarding opening non-local
7623 SocksPorts upon parsing config and opening listeners at startup.
7624 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7625 - Use a more comprehensible log message when telling the user
7626 they've excluded every running exit node. Fixes bug 7890; bugfix
7628 - When logging the number of descriptors we intend to download per
7629 directory request, do not log a number higher than then the number
7630 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7632 - When warning about a directory owned by the wrong user, log the
7633 actual name of the user owning the directory. Previously, we'd log
7634 the name of the process owner twice. Fixes bug 23487; bugfix
7636 - The tor specification says hop counts are 1-based, so fix two log
7637 messages that mistakenly logged 0-based hop counts. Fixes bug
7638 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7639 Credit to Xiaofan Li for reporting this issue.
7641 o Minor bugfixes (portability):
7642 - Stop using the PATH_MAX variable, which is not defined on GNU
7643 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7645 o Minor bugfixes (relay):
7646 - When uploading our descriptor for the first time after startup,
7647 report the reason for uploading as "Tor just started" rather than
7648 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7649 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7650 relays, to prevent spurious address resolutions and descriptor
7651 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7652 bugfix on in 0.2.8.1-alpha.
7654 o Minor bugfixes (tests):
7655 - Fix a broken unit test for the OutboundAddress option: the parsing
7656 function was never returning an error on failure. Fixes bug 23366;
7657 bugfix on 0.3.0.3-alpha.
7658 - Fix a signed-integer overflow in the unit tests for
7659 dir/download_status_random_backoff, which was untriggered until we
7660 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7662 o Minor bugfixes (usability, control port):
7663 - Stop making an unnecessary routerlist check in NETINFO clock skew
7664 detection; this was preventing clients from reporting NETINFO clock
7665 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7667 o Code simplification and refactoring:
7668 - Extract the code for handling newly-open channels into a separate
7669 function from the general code to handle channel state
7670 transitions. This change simplifies our callgraph, reducing the
7671 size of the largest strongly connected component by roughly a
7672 factor of two. Closes ticket 22608.
7673 - Remove dead code for largely unused statistics on the number of
7674 times we've attempted various public key operations. Fixes bug
7675 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7676 - Remove several now-obsolete functions for asking about old
7677 variants directory authority status. Closes ticket 22311; patch
7679 - Remove some of the code that once supported "Named" and "Unnamed"
7680 routers. Authorities no longer vote for these flags. Closes
7682 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7683 and old hidden services, to indicate that they aren't suitable for
7684 new protocols or formats. Closes ticket 23026.
7685 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7686 22521. Patch from Neel Chauhan.
7687 - Split the enormous circuit_send_next_onion_skin() function into
7688 multiple subfunctions. Closes ticket 22804.
7689 - Split the portions of the buffer.c module that handle particular
7690 protocols into separate modules. Part of ticket 23149.
7691 - Use our test macros more consistently, to produce more useful
7692 error messages when our unit tests fail. Add coccinelle patches to
7693 allow us to re-check for test macro uses. Closes ticket 22497.
7695 o Deprecated features:
7696 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7697 only applies to direct unencrypted HTTP connections to your
7698 directory server, which your Tor probably isn't using. Closes
7702 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7703 kernels. Closes ticket 22677.
7704 - Document all values of PublishServerDescriptor in the manpage.
7705 Closes ticket 15645.
7706 - Improve the documentation for the directory port part of the
7707 DirAuthority line. Closes ticket 20152.
7708 - Restore documentation for the authorities' "approved-routers"
7709 file. Closes ticket 21148.
7712 - The AllowDotExit option has been removed as unsafe. It has been
7713 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7714 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7715 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7716 Closes ticket 21031.
7717 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7718 nobody was using it any longer. Closes ticket 22377.
7721 Changes in version 0.2.8.15 - 2017-09-18
7722 Tor 0.2.8.15 backports a collection of bugfixes from later
7725 Most significantly, it includes a fix for TROVE-2017-008, a
7726 security bug that affects hidden services running with the
7727 SafeLogging option disabled. For more information, see
7728 https://trac.torproject.org/projects/tor/ticket/23490
7730 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7731 2018. We suggest that you upgrade to the latest stable release if
7732 possible. If you can't, we recommend that you upgrade at least to
7733 0.2.9, which will be supported until 2020.
7735 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7736 - Avoid an assertion failure bug affecting our implementation of
7737 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7738 handling of "0xx" differs from what we had expected. Fixes bug
7739 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7742 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7745 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7746 - Backport a fix for an "unused variable" warning that appeared
7747 in some versions of mingw. Fixes bug 22838; bugfix on
7750 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7751 - Fix a memset() off the end of an array when packing cells. This
7752 bug should be harmless in practice, since the corrupted bytes are
7753 still in the same structure, and are always padding bytes,
7754 ignored, or immediately overwritten, depending on compiler
7755 behavior. Nevertheless, because the memset()'s purpose is to make
7756 sure that any other cell-handling bugs can't expose bytes to the
7757 network, we need to fix it. Fixes bug 22737; bugfix on
7758 0.2.4.11-alpha. Fixes CID 1401591.
7760 o Build features (backport from 0.3.1.5-alpha):
7761 - Tor's repository now includes a Travis Continuous Integration (CI)
7762 configuration file (.travis.yml). This is meant to help new
7763 developers and contributors who fork Tor to a Github repository be
7764 better able to test their changes, and understand what we expect
7765 to pass. To use this new build feature, you must fork Tor to your
7766 Github account, then go into the "Integrations" menu in the
7767 repository settings for your fork and enable Travis, then push
7768 your changes. Closes ticket 22636.
7771 Changes in version 0.2.9.12 - 2017-09-18
7772 Tor 0.2.9.12 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 o Major features (security, backport from 0.3.0.2-alpha):
7781 - Change the algorithm used to decide DNS TTLs on client and server
7782 side, to better resist DNS-based correlation attacks like the
7783 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7784 Feamster. Now relays only return one of two possible DNS TTL
7785 values, and clients are willing to believe DNS TTL values up to 3
7786 hours long. Closes ticket 19769.
7788 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
7789 - Fix a rare crash when sending a begin cell on a circuit whose
7790 linked directory connection had already been closed. Fixes bug
7791 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7793 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
7794 - Fix a bug that prevented exit nodes from caching DNS records for
7795 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7797 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7798 - Fix a typo that had prevented TPROXY-based transparent proxying
7799 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7800 Patch from "d4fq0fQAgoJ".
7802 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7803 - Avoid an assertion failure bug affecting our implementation of
7804 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7805 handling of "0xx" differs from what we had expected. Fixes bug
7806 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7808 o Minor features (code style, backport from 0.3.1.3-alpha):
7809 - Add "Falls through" comments to our codebase, in order to silence
7810 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7811 Stieger. Closes ticket 22446.
7813 o Minor features (geoip):
7814 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7817 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
7818 - Roll over monthly accounting at the configured hour and minute,
7819 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7820 Found by Andrey Karpov with PVS-Studio.
7822 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
7823 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7824 bugfix on 0.2.8.1-alpha.
7825 - Fix warnings when building with libscrypt and openssl scrypt support
7826 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7827 - When building with certain versions the mingw C header files, avoid
7828 float-conversion warnings when calling the C functions isfinite(),
7829 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
7831 o Minor bugfixes (compilation, backport from 0.3.1.7):
7832 - Avoid compiler warnings in the unit tests for running tor_sscanf()
7833 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7835 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7836 - Backport a fix for an "unused variable" warning that appeared
7837 in some versions of mingw. Fixes bug 22838; bugfix on
7840 o Minor bugfixes (controller, backport from 0.3.1.7):
7841 - Do not crash when receiving a HSPOST command with an empty body.
7842 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7843 - Do not crash when receiving a POSTDESCRIPTOR command with an
7844 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7846 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7847 - Avoid Coverity build warnings related to our BUG() macro. By
7848 default, Coverity treats BUG() as the Linux kernel does: an
7849 instant abort(). We need to override that so our BUG() macro
7850 doesn't prevent Coverity from analyzing functions that use it.
7851 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7853 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7854 - Fix a memset() off the end of an array when packing cells. This
7855 bug should be harmless in practice, since the corrupted bytes are
7856 still in the same structure, and are always padding bytes,
7857 ignored, or immediately overwritten, depending on compiler
7858 behavior. Nevertheless, because the memset()'s purpose is to make
7859 sure that any other cell-handling bugs can't expose bytes to the
7860 network, we need to fix it. Fixes bug 22737; bugfix on
7861 0.2.4.11-alpha. Fixes CID 1401591.
7863 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7864 - When setting the maximum number of connections allowed by the OS,
7865 always allow some extra file descriptors for other files. Fixes
7866 bug 22797; bugfix on 0.2.0.10-alpha.
7868 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7869 - Avoid a sandbox failure when trying to re-bind to a socket and
7870 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7872 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7873 - Permit the fchmod system call, to avoid crashing on startup when
7874 starting with the seccomp2 sandbox and an unexpected set of
7875 permissions on the data directory or its contents. Fixes bug
7876 22516; bugfix on 0.2.5.4-alpha.
7878 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
7879 - Avoid a double-marked-circuit warning that could happen when we
7880 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7883 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7884 - Reject version numbers with non-numeric prefixes (such as +, -, or
7885 whitespace). Disallowing whitespace prevents differential version
7886 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7887 and part of 21508; bugfix on 0.0.8pre1.
7889 o Build features (backport from 0.3.1.5-alpha):
7890 - Tor's repository now includes a Travis Continuous Integration (CI)
7891 configuration file (.travis.yml). This is meant to help new
7892 developers and contributors who fork Tor to a Github repository be
7893 better able to test their changes, and understand what we expect
7894 to pass. To use this new build feature, you must fork Tor to your
7895 Github account, then go into the "Integrations" menu in the
7896 repository settings for your fork and enable Travis, then push
7897 your changes. Closes ticket 22636.
7900 Changes in version 0.3.0.11 - 2017-09-18
7901 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
7904 Most significantly, it includes a fix for TROVE-2017-008, a
7905 security bug that affects hidden services running with the
7906 SafeLogging option disabled. For more information, see
7907 https://trac.torproject.org/projects/tor/ticket/23490
7909 o Minor features (code style, backport from 0.3.1.7):
7910 - Add "Falls through" comments to our codebase, in order to silence
7911 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7912 Stieger. Closes ticket 22446.
7915 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7918 o Minor bugfixes (compilation, backport from 0.3.1.7):
7919 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7920 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7922 o Minor bugfixes (controller, backport from 0.3.1.7):
7923 - Do not crash when receiving a HSPOST command with an empty body.
7924 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7925 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7926 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7928 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7929 - When setting the maximum number of connections allowed by the OS,
7930 always allow some extra file descriptors for other files. Fixes
7931 bug 22797; bugfix on 0.2.0.10-alpha.
7933 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
7934 - Remove a forgotten debugging message when an introduction point
7935 successfully establishes a hidden service prop224 circuit with
7937 - Change three other log_warn() for an introduction point to
7938 protocol warnings, because they can be failure from the network
7939 and are not relevant to the operator. Fixes bug 23078; bugfix on
7940 0.3.0.1-alpha and 0.3.0.2-alpha.
7943 Changes in version 0.3.1.7 - 2017-09-18
7944 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
7946 With the 0.3.1 series, Tor now serves and downloads directory
7947 information in more compact formats, to save on bandwidth overhead. It
7948 also contains a new padding system to resist netflow-based traffic
7949 analysis, and experimental support for building parts of Tor in Rust
7950 (though no parts of Tor are in Rust yet). There are also numerous
7951 small features, bugfixes on earlier release series, and groundwork for
7952 the hidden services revamp of 0.3.2.
7954 This release also includes a fix for TROVE-2017-008, a security bug
7955 that affects hidden services running with the SafeLogging option
7956 disabled. For more information, see
7957 https://trac.torproject.org/projects/tor/ticket/23490
7959 Per our stable release policy, we plan to support each stable release
7960 series for at least the next nine months, or for three months after
7961 the first stable release of the next series: whichever is longer. If
7962 you need a release with long-term support, we recommend that you stay
7963 with the 0.2.9 series.
7965 Below is a list of the changes since 0.3.1.6-rc. For a list of all
7966 changes since 0.3.0, see the ReleaseNotes file.
7968 o Major bugfixes (security, hidden services, loggging):
7969 - Fix a bug where we could log uninitialized stack when a certain
7970 hidden service error occurred while SafeLogging was disabled.
7971 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
7972 TROVE-2017-008 and CVE-2017-0380.
7974 o Minor features (defensive programming):
7975 - Create a pair of consensus parameters, nf_pad_tor2web and
7976 nf_pad_single_onion, to disable netflow padding in the consensus
7977 for non-anonymous connections in case the overhead is high. Closes
7980 o Minor features (diagnostic):
7981 - Add a stack trace to the bug warnings that can be logged when
7982 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
7983 attempt for bug 23105.
7985 o Minor features (geoip):
7986 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7989 o Minor bugfixes (compilation):
7990 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7991 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7993 o Minor bugfixes (controller):
7994 - Do not crash when receiving a HSPOST command with an empty body.
7995 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7996 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7997 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7999 o Minor bugfixes (relay):
8000 - Inform the geoip and rephist modules about all requests, even on
8001 relays that are only fetching microdescriptors. Fixes a bug
8002 related to 21585; bugfix on 0.3.0.1-alpha.
8004 o Minor bugfixes (unit tests):
8005 - Fix a channelpadding unit test failure on slow systems by using
8006 mocked time instead of actual time. Fixes bug 23077; bugfix
8010 Changes in version 0.3.1.6-rc - 2017-09-05
8011 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
8012 release series, including a bug that produced weird behavior on
8013 Windows directory caches.
8015 This is the first release candidate in the Tor 0.3.1 series. If we
8016 find no new bugs or regressions here, the first stable 0.3.1 release
8017 will be nearly identical to it.
8019 o Major bugfixes (windows, directory cache):
8020 - On Windows, do not try to delete cached consensus documents and
8021 diffs before they are unmapped from memory--Windows won't allow
8022 that. Instead, allow the consensus cache directory to grow larger,
8023 to hold files that might need to stay around longer. Fixes bug
8024 22752; bugfix on 0.3.1.1-alpha.
8026 o Minor features (directory authority):
8027 - Improve the message that authorities report to relays that present
8028 RSA/Ed25519 keypairs that conflict with previously pinned keys.
8029 Closes ticket 22348.
8031 o Minor features (geoip):
8032 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
8035 o Minor features (testing):
8036 - Add more tests for compression backend initialization. Closes
8039 o Minor bugfixes (directory cache):
8040 - Fix a memory leak when recovering space in the consensus cache.
8041 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
8043 o Minor bugfixes (hidden service):
8044 - Increase the number of circuits that a service is allowed to
8045 open over a specific period of time. The value was lower than it
8046 should be (8 vs 12) in the normal case of 3 introduction points.
8047 Fixes bug 22159; bugfix on 0.3.0.5-rc.
8048 - Fix a BUG warning during HSv3 descriptor decoding that could be
8049 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
8050 on 0.3.0.1-alpha. Bug found by "haxxpop".
8051 - Rate-limit the log messages if we exceed the maximum number of
8052 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
8054 o Minor bugfixes (logging, relay):
8055 - Remove a forgotten debugging message when an introduction point
8056 successfully establishes a hidden service prop224 circuit with
8058 - Change three other log_warn() for an introduction point to
8059 protocol warnings, because they can be failure from the network
8060 and are not relevant to the operator. Fixes bug 23078; bugfix on
8061 0.3.0.1-alpha and 0.3.0.2-alpha.
8063 o Minor bugfixes (relay):
8064 - When a relay is not running as a directory cache, it will no
8065 longer generate compressed consensuses and consensus diff
8066 information. Previously, this was a waste of disk and CPU. Fixes
8067 bug 23275; bugfix on 0.3.1.1-alpha.
8069 o Minor bugfixes (robustness, error handling):
8070 - Improve our handling of the cases where OpenSSL encounters a
8071 memory error while encoding keys and certificates. We haven't
8072 observed these errors in the wild, but if they do happen, we now
8073 detect and respond better. Fixes bug 19418; bugfix on all versions
8074 of Tor. Reported by Guido Vranken.
8076 o Minor bugfixes (stability):
8077 - Avoid crashing on a double-free when unable to load or process an
8078 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
8079 with the clang static analyzer.
8081 o Minor bugfixes (testing):
8082 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8083 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8084 - Port the hs_ntor handshake test to work correctly with recent
8085 versions of the pysha3 module. Fixes bug 23071; bugfix
8088 o Minor bugfixes (Windows service):
8089 - When running as a Windows service, set the ID of the main thread
8090 correctly. Failure to do so made us fail to send log messages to
8091 the controller in 0.2.1.16-rc, slowed down controller event
8092 delivery in 0.2.7.3-rc and later, and crash with an assertion
8093 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
8094 Patch and diagnosis from "Vort".
8097 Changes in version 0.3.0.10 - 2017-08-02
8098 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
8099 from the current Tor alpha series. OpenBSD users and TPROXY users
8100 should upgrade; others are probably okay sticking with 0.3.0.9.
8102 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
8103 - Tor's repository now includes a Travis Continuous Integration (CI)
8104 configuration file (.travis.yml). This is meant to help new
8105 developers and contributors who fork Tor to a Github repository be
8106 better able to test their changes, and understand what we expect
8107 to pass. To use this new build feature, you must fork Tor to your
8108 Github account, then go into the "Integrations" menu in the
8109 repository settings for your fork and enable Travis, then push
8110 your changes. Closes ticket 22636.
8112 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
8113 - Fix a typo that had prevented TPROXY-based transparent proxying
8114 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8115 Patch from "d4fq0fQAgoJ".
8117 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8118 - Avoid an assertion failure bug affecting our implementation of
8119 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8120 handling of "0xbar" differs from what we had expected. Fixes bug
8121 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8123 o Minor features (backport from 0.3.1.5-alpha):
8124 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8127 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
8128 - Roll over monthly accounting at the configured hour and minute,
8129 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8130 Found by Andrey Karpov with PVS-Studio.
8132 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
8133 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8134 bugfix on 0.2.8.1-alpha.
8135 - Fix warnings when building with libscrypt and openssl scrypt
8136 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8137 - When building with certain versions of the mingw C header files,
8138 avoid float-conversion warnings when calling the C functions
8139 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8142 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8143 - Backport a fix for an "unused variable" warning that appeared
8144 in some versions of mingw. Fixes bug 22838; bugfix on
8147 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8148 - Avoid Coverity build warnings related to our BUG() macro. By
8149 default, Coverity treats BUG() as the Linux kernel does: an
8150 instant abort(). We need to override that so our BUG() macro
8151 doesn't prevent Coverity from analyzing functions that use it.
8152 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8154 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
8155 - When rejecting a router descriptor for running an obsolete version
8156 of Tor without ntor support, warn about the obsolete tor version,
8157 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8159 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8160 - Avoid a sandbox failure when trying to re-bind to a socket and
8161 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8163 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
8164 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8165 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8168 Changes in version 0.3.1.5-alpha - 2017-08-01
8169 Tor 0.3.1.5-alpha improves the performance of consensus diff
8170 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
8171 several other bugs. If no serious bugs are found in this version, the
8172 next version will be a release candidate.
8174 This release also marks the end of support for the Tor 0.2.4.x,
8175 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
8176 further bug or security fixes. Anyone still running or distributing
8177 one of those versions should upgrade.
8179 o Major features (build system, continuous integration):
8180 - Tor's repository now includes a Travis Continuous Integration (CI)
8181 configuration file (.travis.yml). This is meant to help new
8182 developers and contributors who fork Tor to a Github repository be
8183 better able to test their changes, and understand what we expect
8184 to pass. To use this new build feature, you must fork Tor to your
8185 Github account, then go into the "Integrations" menu in the
8186 repository settings for your fork and enable Travis, then push
8187 your changes. Closes ticket 22636.
8189 o Major bugfixes (openbsd, denial-of-service):
8190 - Avoid an assertion failure bug affecting our implementation of
8191 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8192 handling of "0xbar" differs from what we had expected. Fixes bug
8193 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8195 o Major bugfixes (relay, performance):
8196 - Perform circuit handshake operations at a higher priority than we
8197 use for consensus diff creation and compression. This should
8198 prevent circuits from starving when a relay or bridge receives a
8199 new consensus, especially on lower-powered machines. Fixes bug
8200 22883; bugfix on 0.3.1.1-alpha.
8202 o Minor features (bridge authority):
8203 - Add "fingerprint" lines to the networkstatus-bridges file produced
8204 by bridge authorities. Closes ticket 22207.
8206 o Minor features (directory cache, consensus diff):
8207 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
8208 operators with low-resource environments to adjust the number of
8209 consensuses they'll store and generate diffs from. Most cache
8210 operators should leave it unchanged. Helps to work around
8213 o Minor features (geoip):
8214 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8217 o Minor features (relay, performance):
8218 - Always start relays with at least two worker threads, to prevent
8219 priority inversion on slow tasks. Part of the fix for bug 22883.
8220 - Allow background work to be queued with different priorities, so
8221 that a big pile of slow low-priority jobs will not starve out
8222 higher priority jobs. This lays the groundwork for a fix for
8225 o Minor bugfixes (build system, rust):
8226 - Fix a problem where Rust toolchains were not being found when
8227 building without --enable-cargo-online-mode, due to setting the
8228 $HOME environment variable instead of $CARGO_HOME. Fixes bug
8229 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
8231 o Minor bugfixes (compatibility, zstd):
8232 - Write zstd epilogues correctly when the epilogue requires
8233 reallocation of the output buffer, even with zstd 1.3.0.
8234 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
8235 22927; bugfix on 0.3.1.1-alpha.
8237 o Minor bugfixes (compilation warnings):
8238 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
8239 22915; bugfix on 0.2.8.1-alpha.
8240 - Fix warnings when building with libscrypt and openssl scrypt
8241 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8242 - Compile correctly when both openssl 1.1.0 and libscrypt are
8243 detected. Previously this would cause an error. Fixes bug 22892;
8244 bugfix on 0.3.1.1-alpha.
8245 - When building with certain versions of the mingw C header files,
8246 avoid float-conversion warnings when calling the C functions
8247 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8250 o Minor bugfixes (coverity build support):
8251 - Avoid Coverity build warnings related to our BUG() macro. By
8252 default, Coverity treats BUG() as the Linux kernel does: an
8253 instant abort(). We need to override that so our BUG() macro
8254 doesn't prevent Coverity from analyzing functions that use it.
8255 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8257 o Minor bugfixes (directory authority):
8258 - When a directory authority rejects a descriptor or extrainfo with
8259 a given digest, mark that digest as undownloadable, so that we do
8260 not attempt to download it again over and over. We previously
8261 tried to avoid downloading such descriptors by other means, but we
8262 didn't notice if we accidentally downloaded one anyway. This
8263 behavior became problematic in 0.2.7.2-alpha, when authorities
8264 began pinning Ed25519 keys. Fixes bug 22349; bugfix
8267 o Minor bugfixes (error reporting, windows):
8268 - When formatting Windows error messages, use the English format to
8269 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
8272 o Minor bugfixes (file limits, osx):
8273 - When setting the maximum number of connections allowed by the OS,
8274 always allow some extra file descriptors for other files. Fixes
8275 bug 22797; bugfix on 0.2.0.10-alpha.
8277 o Minor bugfixes (linux seccomp2 sandbox):
8278 - Avoid a sandbox failure when trying to re-bind to a socket and
8279 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8281 o Minor bugfixes (memory leaks):
8282 - Fix a small memory leak when validating a configuration that uses
8283 two or more AF_UNIX sockets for the same port type. Fixes bug
8284 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
8286 o Minor bugfixes (unit tests):
8287 - test_consdiff_base64cmp would fail on OS X because while OS X
8288 follows the standard of (less than zero/zero/greater than zero),
8289 it doesn't follow the convention of (-1/0/+1). Make the test
8290 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
8291 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8292 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8295 Changes in version 0.3.1.4-alpha - 2017-06-29
8296 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
8297 to use a guard that was in the same network family as a chosen exit
8298 relay. This is a security regression; all clients running earlier
8299 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8302 This release also fixes several other bugs introduced in 0.3.0.x
8303 and 0.3.1.x, including others that can affect bandwidth usage
8307 - To build with zstd and lzma support, Tor now requires the
8308 pkg-config tool at build time. (This requirement was new in
8309 0.3.1.1-alpha, but was not noted at the time. Noting it here to
8310 close ticket 22623.)
8312 o Major bugfixes (path selection, security):
8313 - When choosing which guard to use for a circuit, avoid the exit's
8314 family along with the exit itself. Previously, the new guard
8315 selection logic avoided the exit, but did not consider its family.
8316 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8317 006 and CVE-2017-0377.
8319 o Major bugfixes (compression, zstd):
8320 - Correctly detect a full buffer when decompressing a large zstd-
8321 compressed input. Previously, we would sometimes treat a full
8322 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
8324 o Major bugfixes (directory protocol):
8325 - Ensure that we send "304 Not modified" as HTTP status code when a
8326 client is attempting to fetch a consensus or consensus diff, and
8327 the best one we can send them is one they already have. Fixes bug
8328 22702; bugfix on 0.3.1.1-alpha.
8330 o Major bugfixes (entry guards):
8331 - When starting with an old consensus, do not add new entry guards
8332 unless the consensus is "reasonably live" (under 1 day old). Fixes
8333 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8335 o Minor features (bug mitigation, diagnostics, logging):
8336 - Avoid an assertion failure, and log a better error message, when
8337 unable to remove a file from the consensus cache on Windows.
8338 Attempts to mitigate and diagnose bug 22752.
8340 o Minor features (geoip):
8341 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8344 o Minor bugfixes (compression):
8345 - When compressing or decompressing a buffer, check for a failure to
8346 create a compression object. Fixes bug 22626; bugfix
8348 - When decompressing a buffer, check for extra data after the end of
8349 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
8350 - When decompressing an object received over an anonymous directory
8351 connection, if we have already decompressed it using an acceptable
8352 compression method, do not reject it for looking like an
8353 unacceptable compression method. Fixes part of bug 22670; bugfix
8355 - When serving directory votes compressed with zlib, do not claim to
8356 have compressed them with zstd. Fixes bug 22669; bugfix
8358 - When spooling compressed data to an output buffer, don't try to
8359 spool more data when there is no more data to spool and we are not
8360 trying to flush the input. Previously, we would sometimes launch
8361 compression requests with nothing to do, which interferes with our
8362 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
8364 o Minor bugfixes (defensive programming):
8365 - Detect and break out of infinite loops in our compression code. We
8366 don't think that any such loops exist now, but it's best to be
8367 safe. Closes ticket 22672.
8368 - Fix a memset() off the end of an array when packing cells. This
8369 bug should be harmless in practice, since the corrupted bytes are
8370 still in the same structure, and are always padding bytes,
8371 ignored, or immediately overwritten, depending on compiler
8372 behavior. Nevertheless, because the memset()'s purpose is to make
8373 sure that any other cell-handling bugs can't expose bytes to the
8374 network, we need to fix it. Fixes bug 22737; bugfix on
8375 0.2.4.11-alpha. Fixes CID 1401591.
8377 o Minor bugfixes (linux seccomp2 sandbox):
8378 - Permit the fchmod system call, to avoid crashing on startup when
8379 starting with the seccomp2 sandbox and an unexpected set of
8380 permissions on the data directory or its contents. Fixes bug
8381 22516; bugfix on 0.2.5.4-alpha.
8382 - Fix a crash in the LZMA module, when the sandbox was enabled, and
8383 liblzma would allocate more than 16 MB of memory. We solve this by
8384 bumping the mprotect() limit in the sandbox module from 16 MB to
8385 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
8387 o Minor bugfixes (logging):
8388 - When decompressing, do not warn if we fail to decompress using a
8389 compression method that we merely guessed. Fixes part of bug
8390 22670; bugfix on 0.1.1.14-alpha.
8391 - When decompressing, treat mismatch between content-encoding and
8392 actual compression type as a protocol warning. Fixes part of bug
8393 22670; bugfix on 0.1.1.9-alpha.
8394 - Downgrade "assigned_to_cpuworker failed" message to info-level
8395 severity. In every case that can reach it, either a better warning
8396 has already been logged, or no warning is warranted. Fixes bug
8397 22356; bugfix on 0.2.6.3-alpha.
8398 - Demote a warn that was caused by libevent delays to info if
8399 netflow padding is less than 4.5 seconds late, or to notice
8400 if it is more (4.5 seconds is the amount of time that a netflow
8401 record might be emitted after, if we chose the maximum timeout).
8402 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8404 o Minor bugfixes (process behavior):
8405 - When exiting because of an error, always exit with a nonzero exit
8406 status. Previously, we would fail to report an error in our exit
8407 status in cases related to __OwningControllerProcess failure,
8408 lockfile contention, and Ed25519 key initialization. Fixes bug
8409 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
8410 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
8414 - Add a manpage description for the key-pinning-journal file. Closes
8416 - Correctly note that bandwidth accounting values are stored in the
8417 state file, and the bw_accounting file is now obsolete. Closes
8419 - Document more of the files in the Tor data directory, including
8420 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
8421 approved-routers, sr-random, and diff-cache. Found while fixing
8425 Changes in version 0.3.0.9 - 2017-06-29
8426 Tor 0.3.0.9 fixes a path selection bug that would allow a client
8427 to use a guard that was in the same network family as a chosen exit
8428 relay. This is a security regression; all clients running earlier
8429 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
8432 This release also backports several other bugfixes from the 0.3.1.x
8435 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
8436 - When choosing which guard to use for a circuit, avoid the exit's
8437 family along with the exit itself. Previously, the new guard
8438 selection logic avoided the exit, but did not consider its family.
8439 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8440 006 and CVE-2017-0377.
8442 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
8443 - Don't block bootstrapping when a primary bridge is offline and we
8444 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8445 21969; bugfix on 0.3.0.3-alpha.
8447 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
8448 - When starting with an old consensus, do not add new entry guards
8449 unless the consensus is "reasonably live" (under 1 day old). Fixes
8450 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8452 o Minor features (geoip):
8453 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8456 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8457 - Reject version numbers with non-numeric prefixes (such as +, -, or
8458 whitespace). Disallowing whitespace prevents differential version
8459 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8460 and part of 21508; bugfix on 0.0.8pre1.
8462 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8463 - Permit the fchmod system call, to avoid crashing on startup when
8464 starting with the seccomp2 sandbox and an unexpected set of
8465 permissions on the data directory or its contents. Fixes bug
8466 22516; bugfix on 0.2.5.4-alpha.
8468 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
8469 - Fix a memset() off the end of an array when packing cells. This
8470 bug should be harmless in practice, since the corrupted bytes are
8471 still in the same structure, and are always padding bytes,
8472 ignored, or immediately overwritten, depending on compiler
8473 behavior. Nevertheless, because the memset()'s purpose is to make
8474 sure that any other cell-handling bugs can't expose bytes to the
8475 network, we need to fix it. Fixes bug 22737; bugfix on
8476 0.2.4.11-alpha. Fixes CID 1401591.
8479 Changes in version 0.3.1.3-alpha - 2017-06-08
8480 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
8481 remotely crash a hidden service with an assertion failure. Anyone
8482 running a hidden service should upgrade to this version, or to some
8483 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8485 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
8486 that sometimes made relays unreliable, as well as several other
8487 bugfixes described below.
8489 o Major bugfixes (hidden service, relay, security):
8490 - Fix a remotely triggerable assertion failure when a hidden service
8491 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8492 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8493 - Fix a remotely triggerable assertion failure caused by receiving a
8494 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8495 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8498 o Major bugfixes (relay, link handshake):
8499 - When performing the v3 link handshake on a TLS connection, report
8500 that we have the x509 certificate that we actually used on that
8501 connection, even if we have changed certificates since that
8502 connection was first opened. Previously, we would claim to have
8503 used our most recent x509 link certificate, which would sometimes
8504 make the link handshake fail. Fixes one case of bug 22460; bugfix
8507 o Major bugfixes (relays, key management):
8508 - Regenerate link and authentication certificates whenever the key
8509 that signs them changes; also, regenerate link certificates
8510 whenever the signed key changes. Previously, these processes were
8511 only weakly coupled, and we relays could (for minutes to hours)
8512 wind up with an inconsistent set of keys and certificates, which
8513 other relays would not accept. Fixes two cases of bug 22460;
8514 bugfix on 0.3.0.1-alpha.
8515 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8516 send the certificate that matches the x509 certificate that we
8517 used on the TLS connection. Previously, there was a race condition
8518 if the TLS context rotated after we began the TLS handshake but
8519 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8522 o Major bugfixes (torrc, crash):
8523 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
8524 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
8526 o Minor features (code style):
8527 - Add "Falls through" comments to our codebase, in order to silence
8528 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8529 Stieger. Closes ticket 22446.
8531 o Minor features (diagnostic):
8532 - Add logging messages to try to diagnose a rare bug that seems to
8533 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
8534 think this is happening because of incorrect system clocks, but
8535 we'd like to know for certain. Diagnostic for bug 22466.
8537 o Minor bugfixes (correctness):
8538 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8539 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8541 o Minor bugfixes (directory protocol):
8542 - Check for libzstd >= 1.1, because older versions lack the
8543 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8545 o Minor bugfixes (link handshake):
8546 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8547 months, and regenerate it when it is within one month of expiring.
8548 Previously, we had generated this certificate at startup with a
8549 ten-year lifetime, but that could lead to weird behavior when Tor
8550 was started with a grossly inaccurate clock. Mitigates bug 22466;
8551 mitigation on 0.3.0.1-alpha.
8553 o Minor bugfixes (storage directories):
8554 - Always check for underflows in the cached storage directory usage.
8555 If the usage does underflow, re-calculate it. Also, avoid a
8556 separate underflow when the usage is not known. Fixes bug 22424;
8557 bugfix on 0.3.1.1-alpha.
8559 o Minor bugfixes (unit tests):
8560 - The unit tests now pass on systems where localhost is misconfigured
8561 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8565 - Clarify the manpage for the (deprecated) torify script. Closes
8568 Changes in version 0.3.0.8 - 2017-06-08
8569 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8570 remotely crash a hidden service with an assertion failure. Anyone
8571 running a hidden service should upgrade to this version, or to some
8572 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8574 Tor 0.3.0.8 also includes fixes for several key management bugs
8575 that sometimes made relays unreliable, as well as several other
8576 bugfixes described below.
8578 o Major bugfixes (hidden service, relay, security, backport
8579 from 0.3.1.3-alpha):
8580 - Fix a remotely triggerable assertion failure when a hidden service
8581 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8582 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8583 - Fix a remotely triggerable assertion failure caused by receiving a
8584 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8585 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8588 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8589 - When performing the v3 link handshake on a TLS connection, report
8590 that we have the x509 certificate that we actually used on that
8591 connection, even if we have changed certificates since that
8592 connection was first opened. Previously, we would claim to have
8593 used our most recent x509 link certificate, which would sometimes
8594 make the link handshake fail. Fixes one case of bug 22460; bugfix
8597 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8598 - Regenerate link and authentication certificates whenever the key
8599 that signs them changes; also, regenerate link certificates
8600 whenever the signed key changes. Previously, these processes were
8601 only weakly coupled, and we relays could (for minutes to hours)
8602 wind up with an inconsistent set of keys and certificates, which
8603 other relays would not accept. Fixes two cases of bug 22460;
8604 bugfix on 0.3.0.1-alpha.
8605 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8606 send the certificate that matches the x509 certificate that we
8607 used on the TLS connection. Previously, there was a race condition
8608 if the TLS context rotated after we began the TLS handshake but
8609 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8612 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8613 - Stop rejecting v3 hidden service descriptors because their size
8614 did not match an old padding rule. Fixes bug 22447; bugfix on
8617 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8618 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8619 December 2016 (of which ~126 were still functional) with a list of
8620 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8621 2017. Resolves ticket 21564.
8623 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8624 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8625 bug 22252; bugfix on 0.2.9.3-alpha.
8627 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8628 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8629 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8631 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8632 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8633 months, and regenerate it when it is within one month of expiring.
8634 Previously, we had generated this certificate at startup with a
8635 ten-year lifetime, but that could lead to weird behavior when Tor
8636 was started with a grossly inaccurate clock. Mitigates bug 22466;
8637 mitigation on 0.3.0.1-alpha.
8639 o Minor bugfixes (memory leak, directory authority, backport from
8641 - When directory authorities reject a router descriptor due to
8642 keypinning, free the router descriptor rather than leaking the
8643 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8646 Changes in version 0.2.9.11 - 2017-06-08
8647 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8648 remotely crash a hidden service with an assertion failure. Anyone
8649 running a hidden service should upgrade to this version, or to some
8650 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8651 are not affected by TROVE-2017-004.)
8653 Tor 0.2.9.11 also backports fixes for several key management bugs
8654 that sometimes made relays unreliable, as well as several other
8655 bugfixes described below.
8657 o Major bugfixes (hidden service, relay, security, backport
8658 from 0.3.1.3-alpha):
8659 - Fix a remotely triggerable assertion failure caused by receiving a
8660 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8661 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8664 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8665 - When performing the v3 link handshake on a TLS connection, report
8666 that we have the x509 certificate that we actually used on that
8667 connection, even if we have changed certificates since that
8668 connection was first opened. Previously, we would claim to have
8669 used our most recent x509 link certificate, which would sometimes
8670 make the link handshake fail. Fixes one case of bug 22460; bugfix
8673 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8674 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8675 December 2016 (of which ~126 were still functional) with a list of
8676 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8677 2017. Resolves ticket 21564.
8679 o Minor features (future-proofing, backport from 0.3.0.7):
8680 - Tor no longer refuses to download microdescriptors or descriptors if
8681 they are listed as "published in the future". This change will
8682 eventually allow us to stop listing meaningful "published" dates
8683 in microdescriptor consensuses, and thereby allow us to reduce the
8684 resources required to download consensus diffs by over 50%.
8685 Implements part of ticket 21642; implements part of proposal 275.
8687 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8688 - Directory authorities now reject relays running versions
8689 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8690 suffer from bug 20499 and don't keep their consensus cache
8691 up-to-date. Resolves ticket 20509.
8693 o Minor features (geoip):
8694 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8697 o Minor bugfixes (control port, backport from 0.3.0.6):
8698 - The GETINFO extra-info/digest/<digest> command was broken because
8699 of a wrong base16 decode return value check, introduced when
8700 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8702 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8703 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8704 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8706 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8707 - The getpid() system call is now permitted under the Linux seccomp2
8708 sandbox, to avoid crashing with versions of OpenSSL (and other
8709 libraries) that attempt to learn the process's PID by using the
8710 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8713 o Minor bugfixes (memory leak, directory authority, backport
8714 from 0.3.1.2-alpha):
8715 - When directory authorities reject a router descriptor due to
8716 keypinning, free the router descriptor rather than leaking the
8717 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8719 Changes in version 0.2.8.14 - 2017-06-08
8720 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8721 remotely crash a hidden service with an assertion failure. Anyone
8722 running a hidden service should upgrade to this version, or to some
8723 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8724 are not affected by TROVE-2017-004.)
8726 o Major bugfixes (hidden service, relay, security):
8727 - Fix a remotely triggerable assertion failure caused by receiving a
8728 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8729 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8732 o Minor features (geoip):
8733 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8736 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8737 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8738 December 2016 (of which ~126 were still functional) with a list of
8739 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8740 2017. Resolves ticket 21564.
8742 o Minor bugfixes (correctness):
8743 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8744 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8746 Changes in version 0.2.7.8 - 2017-06-08
8747 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8748 remotely crash a hidden service with an assertion failure. Anyone
8749 running a hidden service should upgrade to this version, or to some
8750 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8751 are not affected by TROVE-2017-004.)
8753 o Major bugfixes (hidden service, relay, security):
8754 - Fix a remotely triggerable assertion failure caused by receiving a
8755 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8756 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8759 o Minor features (geoip):
8760 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8763 o Minor bugfixes (correctness):
8764 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8765 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8768 Changes in version 0.2.6.12 - 2017-06-08
8769 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
8770 remotely crash a hidden service with an assertion failure. Anyone
8771 running a hidden service should upgrade to this version, or to some
8772 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8773 are not affected by TROVE-2017-004.)
8775 o Major bugfixes (hidden service, relay, security):
8776 - Fix a remotely triggerable assertion failure caused by receiving a
8777 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8778 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8781 o Minor features (geoip):
8782 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8785 o Minor bugfixes (correctness):
8786 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8787 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8789 Changes in version 0.2.5.14 - 2017-06-08
8790 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
8791 remotely crash a hidden service with an assertion failure. Anyone
8792 running a hidden service should upgrade to this version, or to some
8793 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8794 are not affected by TROVE-2017-004.)
8796 o Major bugfixes (hidden service, relay, security):
8797 - Fix a remotely triggerable assertion failure caused by receiving a
8798 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8799 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8802 o Minor features (geoip):
8803 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8806 o Minor bugfixes (correctness):
8807 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8808 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8810 Changes in version 0.2.4.29 - 2017-06-08
8811 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
8812 remotely crash a hidden service with an assertion failure. Anyone
8813 running a hidden service should upgrade to this version, or to some
8814 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8815 are not affected by TROVE-2017-004.)
8817 o Major bugfixes (hidden service, relay, security):
8818 - Fix a remotely triggerable assertion failure caused by receiving a
8819 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8820 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8823 o Minor features (geoip):
8824 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8827 o Minor bugfixes (correctness):
8828 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8829 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8832 Changes in version 0.3.1.2-alpha - 2017-05-26
8833 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
8834 fixes a few bugs found while testing 0.3.1.1-alpha, including a
8835 memory corruption bug that affected relay stability.
8837 o Major bugfixes (crash, relay):
8838 - Fix a memory-corruption bug in relays that set MyFamily.
8839 Previously, they would double-free MyFamily elements when making
8840 the next descriptor or when changing their configuration. Fixes
8841 bug 22368; bugfix on 0.3.1.1-alpha.
8843 o Minor bugfixes (logging):
8844 - Log a better message when a directory authority replies to an
8845 upload with an unexpected status code. Fixes bug 11121; bugfix
8848 o Minor bugfixes (memory leak, directory authority):
8849 - When directory authorities reject a router descriptor due to
8850 keypinning, free the router descriptor rather than leaking the
8851 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8854 Changes in version 0.3.1.1-alpha - 2017-05-22
8855 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
8856 reduces the bandwidth usage for Tor's directory protocol, adds some
8857 basic padding to resist netflow-based traffic analysis and to serve as
8858 the basis of other padding in the future, and adds rust support to the
8861 It also contains numerous other small features and improvements to
8862 security, correctness, and performance.
8864 Below are the changes since 0.3.0.7.
8866 o Major features (directory protocol):
8867 - Tor relays and authorities can now serve clients an abbreviated
8868 version of the consensus document, containing only the changes
8869 since an older consensus document that the client holds. Clients
8870 now request these documents when available. When both client and
8871 server use this new protocol, they will use far less bandwidth (up
8872 to 94% less) to keep the client's consensus up-to-date. Implements
8873 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
8874 - Tor can now compress directory traffic with lzma or with zstd
8875 compression algorithms, which can deliver better bandwidth
8876 performance. Because lzma is computationally expensive, it's only
8877 used for documents that can be compressed once and served many
8878 times. Support for these algorithms requires that tor is built
8879 with the libzstd and/or liblzma libraries available. Implements
8880 proposal 278; closes ticket 21662.
8881 - Relays now perform the more expensive compression operations, and
8882 consensus diff generation, in worker threads. This separation
8883 avoids delaying the main thread when a new consensus arrives.
8885 o Major features (experimental):
8886 - Tor can now build modules written in Rust. To turn this on, pass
8887 the "--enable-rust" flag to the configure script. It's not time to
8888 get excited yet: currently, there is no actual Rust functionality
8889 beyond some simple glue code, and a notice at startup to tell you
8890 that Rust is running. Still, we hope that programmers and
8891 packagers will try building Tor with Rust support, so that we can
8892 find issues and solve portability problems. Closes ticket 22106.
8894 o Major features (traffic analysis resistance):
8895 - Connections between clients and relays now send a padding cell in
8896 each direction every 1.5 to 9.5 seconds (tunable via consensus
8897 parameters). This padding will not resist specialized
8898 eavesdroppers, but it should be enough to make many ISPs' routine
8899 network flow logging less useful in traffic analysis against
8902 Padding is negotiated using Tor's link protocol, so both relays
8903 and clients must upgrade for this to take effect. Clients may
8904 still send padding despite the relay's version by setting
8905 ConnectionPadding 1 in torrc, and may disable padding by setting
8906 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
8907 users with the torrc option ReducedConnectionPadding. Implements
8908 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
8909 - Relays will publish 24 hour totals of padding and non-padding cell
8910 counts to their extra-info descriptors, unless PaddingStatistics 0
8911 is set in torrc. These 24 hour totals are also rounded to
8914 o Major bugfixes (connection usage):
8915 - We use NETINFO cells to try to determine if both relays involved
8916 in a connection will agree on the canonical status of that
8917 connection. We prefer the connections where this is the case for
8918 extend cells, and try to close connections where relays disagree
8919 on their canonical status early. Also, we now prefer the oldest
8920 valid connection for extend cells. These two changes should reduce
8921 the number of long-term connections that are kept open between
8922 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
8923 - Relays now log hourly statistics (look for
8924 "channel_check_for_duplicates" lines) on the total number of
8925 connections to other relays. If the number of connections per
8926 relay is unexpectedly large, this log message is at notice level.
8927 Otherwise it is at info.
8929 o Major bugfixes (entry guards):
8930 - Don't block bootstrapping when a primary bridge is offline and we
8931 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8932 21969; bugfix on 0.3.0.3-alpha.
8934 o Major bugfixes (linux TPROXY support):
8935 - Fix a typo that had prevented TPROXY-based transparent proxying
8936 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8937 Patch from "d4fq0fQAgoJ".
8939 o Minor features (security, windows):
8940 - Enable a couple of pieces of Windows hardening: one
8941 (HeapEnableTerminationOnCorruption) that has been on-by-default
8942 since Windows 8, and unavailable before Windows 7; and one
8943 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8944 affect us, but shouldn't do any harm. Closes ticket 21953.
8946 o Minor features (config options):
8947 - Allow "%include" directives in torrc configuration files. These
8948 directives import the settings from other files, or from all the
8949 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
8950 - Make SAVECONF return an error when overwriting a torrc that has
8951 includes. Using SAVECONF with the FORCE option will allow it to
8952 overwrite torrc even if includes are used. Related to ticket 1922.
8953 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
8954 will work without the FORCE option. Related to ticket 1922.
8956 o Minor features (controller):
8957 - Warn the first time that a controller requests data in the long-
8958 deprecated 'GETINFO network-status' format. Closes ticket 21703.
8960 o Minor features (defaults):
8961 - The default value for UseCreateFast is now 0: clients which
8962 haven't yet received a consensus document will now use a proper
8963 ntor handshake to talk to their directory servers whenever they
8964 can. Closes ticket 21407.
8965 - Onion key rotation and expiry intervals are now defined as a
8966 network consensus parameter, per proposal 274. The default
8967 lifetime of an onion key is increased from 7 to 28 days. Old onion
8968 keys will expire after 7 days by default. This change will make
8969 consensus diffs much smaller, and save significant bandwidth.
8970 Closes ticket 21641.
8972 o Minor features (fallback directory list):
8973 - Update the fallback directory mirror whitelist and blacklist based
8974 on operator emails. Closes task 21121.
8975 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8976 December 2016 (of which ~126 were still functional) with a list of
8977 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8978 2017. Resolves ticket 21564.
8980 o Minor features (hidden services, logging):
8981 - Log a message when a hidden service descriptor has fewer
8982 introduction points than specified in
8983 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
8984 - Log a message when a hidden service reaches its introduction point
8985 circuit limit, and when that limit is reset. Follow up to ticket
8986 21594; closes ticket 21622.
8987 - Warn user if multiple entries in EntryNodes and at least one
8988 HiddenService are used together. Pinning EntryNodes along with a
8989 hidden service can be possibly harmful; for instance see ticket
8990 14917 or 21155. Closes ticket 21155.
8992 o Minor features (linux seccomp2 sandbox):
8993 - We now have a document storage backend compatible with the Linux
8994 seccomp2 sandbox. This backend is used for consensus documents and
8995 diffs between them; in the long term, we'd like to use it for
8996 unparseable directory material too. Closes ticket 21645
8997 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
8998 from 1MB to 16MB. This was necessary with the glibc allocator in
8999 order to allow worker threads to allocate more memory -- which in
9000 turn is necessary because of our new use of worker threads for
9001 compression. Closes ticket 22096.
9003 o Minor features (logging):
9004 - Log files are no longer created world-readable by default.
9005 (Previously, most distributors would store the logs in a non-
9006 world-readable location to prevent inappropriate access. This
9007 change is an extra precaution.) Closes ticket 21729; patch
9010 o Minor features (performance):
9011 - Our Keccak (SHA-3) implementation now accesses memory more
9012 efficiently, especially on little-endian systems. Closes
9014 - Add an O(1) implementation of channel_find_by_global_id(), to
9015 speed some controller functions.
9017 o Minor features (relay, configuration):
9018 - The MyFamily option may now be repeated as many times as desired,
9019 for relays that want to configure large families. Closes ticket
9020 4998; patch by Daniel Pinto.
9022 o Minor features (safety):
9023 - Add an explicit check to extrainfo_parse_entry_from_string() for
9024 NULL inputs. We don't believe this can actually happen, but it may
9025 help silence a warning from the Clang analyzer. Closes
9028 o Minor features (testing):
9029 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
9030 When Tor is compiled with this option, we disable a number of
9031 redundant memory-safety failsafes that are intended to stop bugs
9032 from becoming security issues. This makes it easier to hunt for
9033 bugs that would be security issues without the failsafes turned
9034 on. Closes ticket 21439.
9035 - Add a general event-tracing instrumentation support to Tor. This
9036 subsystem will enable developers and researchers to add fine-
9037 grained instrumentation to their Tor instances, for use when
9038 examining Tor network performance issues. There are no trace
9039 events yet, and event-tracing is off by default unless enabled at
9040 compile time. Implements ticket 13802.
9041 - Improve our version parsing tests: add tests for typical version
9042 components, add tests for invalid versions, including numeric
9043 range and non-numeric prefixes. Unit tests 21278, 21450, and
9044 21507. Partially implements 21470.
9046 o Minor bugfixes (bandwidth accounting):
9047 - Roll over monthly accounting at the configured hour and minute,
9048 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9049 Found by Andrey Karpov with PVS-Studio.
9051 o Minor bugfixes (code correctness):
9052 - Accurately identify client connections by their lack of peer
9053 authentication. This means that we bail out earlier if asked to
9054 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
9057 o Minor bugfixes (configuration):
9058 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
9059 bug 22252; bugfix on 0.2.9.3-alpha.
9061 o Minor bugfixes (connection lifespan):
9062 - Allow more control over how long TLS connections are kept open:
9063 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
9064 single option called CircuitsAvailableTimeout. Also, allow the
9065 consensus to control the default values for both this preference
9066 and the lifespan of relay-to-relay connections. Fixes bug 17592;
9067 bugfix on 0.2.5.5-alpha.
9068 - Increase the initial circuit build timeout testing frequency, to
9069 help ensure that ReducedConnectionPadding clients finish learning
9070 a timeout before their orconn would expire. The initial testing
9071 rate was set back in the days of TAP and before the Tor Browser
9072 updater, when we had to be much more careful about new clients
9073 making lots of circuits. With this change, a circuit build timeout
9074 is learned in about 15-20 minutes, instead of 100-120 minutes.
9076 o Minor bugfixes (controller):
9077 - GETINFO onions/current and onions/detached no longer respond with
9078 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
9079 - Trigger HS descriptor events on the control port when the client
9080 fails to pick a hidden service directory for a hidden service.
9081 This can happen if all the hidden service directories are in
9082 ExcludeNodes, or they have all been queried within the last 15
9083 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
9085 o Minor bugfixes (directory authority):
9086 - When rejecting a router descriptor for running an obsolete version
9087 of Tor without ntor support, warn about the obsolete tor version,
9088 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
9089 - Prevent the shared randomness subsystem from asserting when
9090 initialized by a bridge authority with an incomplete configuration
9091 file. Fixes bug 21586; bugfix on 0.2.9.8.
9093 o Minor bugfixes (exit-side DNS):
9094 - Fix an untriggerable assertion that checked the output of a
9095 libevent DNS error, so that the assertion actually behaves as
9096 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
9097 Karpov using PVS-Studio.
9099 o Minor bugfixes (fallback directories):
9100 - Make the usage example in updateFallbackDirs.py actually work, and
9101 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
9102 - Decrease the guard flag average required to be a fallback. This
9103 allows us to keep relays that have their guard flag removed when
9104 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9105 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
9106 bugfix on 0.2.8.1-alpha.
9107 - Make sure fallback directory mirrors have the same address, port,
9108 and relay identity key for at least 30 days before they are
9109 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9111 o Minor bugfixes (hidden services):
9112 - Stop printing a cryptic warning when a hidden service gets a
9113 request to connect to a virtual port that it hasn't configured.
9114 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
9115 - Simplify hidden service descriptor creation by using an existing
9116 flag to check if an introduction point is established. Fixes bug
9117 21599; bugfix on 0.2.7.2-alpha.
9119 o Minor bugfixes (memory leak):
9120 - Fix a small memory leak at exit from the backtrace handler code.
9121 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
9123 o Minor bugfixes (protocol, logging):
9124 - Downgrade a log statement about unexpected relay cells from "bug"
9125 to "protocol warning", because there is at least one use case
9126 where it can be triggered by a buggy tor implementation. Fixes bug
9127 21293; bugfix on 0.1.1.14-alpha.
9129 o Minor bugfixes (testing):
9130 - Use unbuffered I/O for utility functions around the
9131 process_handle_t type. This fixes unit test failures reported on
9132 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
9133 - Make display of captured unit test log messages consistent. Fixes
9134 bug 21510; bugfix on 0.2.9.3-alpha.
9135 - Make test-network.sh always call chutney's test-network.sh.
9136 Previously, this only worked on systems which had bash installed,
9137 due to some bash-specific code in the script. Fixes bug 19699;
9138 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
9140 o Minor bugfixes (voting consistency):
9141 - Reject version numbers with non-numeric prefixes (such as +, -, or
9142 whitespace). Disallowing whitespace prevents differential version
9143 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9144 and part of 21508; bugfix on 0.0.8pre1.
9146 o Minor bugfixes (windows, relay):
9147 - Resolve "Failure from drain_fd: No error" warnings on Windows
9148 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
9150 o Code simplification and refactoring:
9151 - Break up the 630-line function connection_dir_client_reached_eof()
9152 into a dozen smaller functions. This change should help
9153 maintainability and readability of the client directory code.
9154 - Isolate our use of the openssl headers so that they are only
9155 included from our crypto wrapper modules, and from tests that
9156 examine those modules' internals. Closes ticket 21841.
9157 - Simplify our API to launch directory requests, making it more
9158 extensible and less error-prone. Now it's easier to add extra
9159 headers to directory requests. Closes ticket 21646.
9160 - Our base64 decoding functions no longer overestimate the output
9161 space that they need when parsing unpadded inputs. Closes
9163 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
9164 Resolves ticket 22213.
9165 - The logic that directory caches use to spool request to clients,
9166 serving them one part at a time so as not to allocate too much
9167 memory, has been refactored for consistency. Previously there was
9168 a separate spooling implementation per type of spoolable data. Now
9169 there is one common spooling implementation, with extensible data
9170 types. Closes ticket 21651.
9171 - Tor's compression module now supports multiple backends. Part of
9172 the implementation for proposal 278; closes ticket 21663.
9175 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
9176 Closes ticket 21873.
9177 - Correct documentation about the default DataDirectory value.
9178 Closes ticket 21151.
9179 - Document the default behavior of NumEntryGuards and
9180 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
9182 - Document key=value pluggable transport arguments for Bridge lines
9183 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
9184 - Note that bandwidth-limiting options don't affect TCP headers or
9185 DNS. Closes ticket 17170.
9187 o Removed features (configuration options, all in ticket 22060):
9188 - These configuration options are now marked Obsolete, and no longer
9189 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
9190 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
9191 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
9192 in 0.2.9.2-alpha and have now been removed. The previous default
9193 behavior is now always chosen; the previous (less secure) non-
9194 default behavior is now unavailable.
9195 - CloseHSClientCircuitsImmediatelyOnTimeout and
9196 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
9197 0.2.9.2-alpha and now have been removed. HS circuits never close
9198 on circuit build timeout; they have a longer timeout period.
9199 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
9200 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
9201 (and others) to configure listen-only and advertise-only addresses.
9203 o Removed features (tools):
9204 - We've removed the tor-checkkey tool from src/tools. Long ago, we
9205 used it to help people detect RSA keys that were generated by
9206 versions of Debian affected by CVE-2008-0166. But those keys have
9207 been out of circulation for ages, and this tool is no longer
9208 required. Closes ticket 21842.
9211 Changes in version 0.3.0.7 - 2017-05-15
9212 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
9213 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
9214 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
9215 clients are not affected.
9217 o Major bugfixes (hidden service directory, security):
9218 - Fix an assertion failure in the hidden service directory code, which
9219 could be used by an attacker to remotely cause a Tor relay process to
9220 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
9221 should upgrade. This security issue is tracked as TROVE-2017-002.
9222 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
9225 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9228 o Minor features (future-proofing):
9229 - Tor no longer refuses to download microdescriptors or descriptors
9230 if they are listed as "published in the future". This change will
9231 eventually allow us to stop listing meaningful "published" dates
9232 in microdescriptor consensuses, and thereby allow us to reduce the
9233 resources required to download consensus diffs by over 50%.
9234 Implements part of ticket 21642; implements part of proposal 275.
9236 o Minor bugfixes (Linux seccomp2 sandbox):
9237 - The getpid() system call is now permitted under the Linux seccomp2
9238 sandbox, to avoid crashing with versions of OpenSSL (and other
9239 libraries) that attempt to learn the process's PID by using the
9240 syscall rather than the VDSO code. Fixes bug 21943; bugfix
9244 Changes in version 0.3.0.6 - 2017-04-26
9245 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
9247 With the 0.3.0 series, clients and relays now use Ed25519 keys to
9248 authenticate their link connections to relays, rather than the old
9249 RSA1024 keys that they used before. (Circuit crypto has been
9250 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
9251 the guard selection and replacement algorithm to behave more robustly
9252 in the presence of unreliable networks, and to resist guard-
9255 This series also includes numerous other small features and bugfixes,
9256 along with more groundwork for the upcoming hidden-services revamp.
9258 Per our stable release policy, we plan to support the Tor 0.3.0
9259 release series for at least the next nine months, or for three months
9260 after the first stable release of the 0.3.1 series: whichever is
9261 longer. If you need a release with long-term support, we recommend
9262 that you stay with the 0.2.9 series.
9264 Below are the changes since 0.3.0.5-rc. For a list of all changes
9265 since 0.2.9, see the ReleaseNotes file.
9267 o Minor features (geoip):
9268 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
9271 o Minor bugfixes (control port):
9272 - The GETINFO extra-info/digest/<digest> command was broken because
9273 of a wrong base16 decode return value check, introduced when
9274 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
9276 o Minor bugfixes (crash prevention):
9277 - Fix a (currently untriggerable, but potentially dangerous) crash
9278 bug when base32-encoding inputs whose sizes are not a multiple of
9279 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
9282 Changes in version 0.3.0.5-rc - 2017-04-05
9283 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
9284 0.3.0 release series.
9286 This is the second release candidate in the Tor 0.3.0 series, and has
9287 much fewer changes than the first. If we find no new bugs or
9288 regressions here, the first stable 0.3.0 release will be nearly
9291 o Major bugfixes (crash, directory connections):
9292 - Fix a rare crash when sending a begin cell on a circuit whose
9293 linked directory connection had already been closed. Fixes bug
9294 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9296 o Major bugfixes (guard selection):
9297 - Fix a guard selection bug where Tor would refuse to bootstrap in
9298 some cases if the user swapped a bridge for another bridge in
9299 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
9300 Reported by "torvlnt33r".
9302 o Minor features (geoip):
9303 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
9306 o Minor bugfix (compilation):
9307 - Fix a warning when compiling hs_service.c. Previously, it had no
9308 exported symbols when compiled for libor.a, resulting in a
9309 compilation warning from clang. Fixes bug 21825; bugfix
9312 o Minor bugfixes (hidden services):
9313 - Make hidden services check for failed intro point connections,
9314 even when they have exceeded their intro point creation limit.
9315 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
9316 - Make hidden services with 8 to 10 introduction points check for
9317 failed circuits immediately after startup. Previously, they would
9318 wait for 5 minutes before performing their first checks. Fixes bug
9319 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
9321 o Minor bugfixes (memory leaks):
9322 - Fix a memory leak when using GETCONF on a port option. Fixes bug
9323 21682; bugfix on 0.3.0.3-alpha.
9325 o Minor bugfixes (relay):
9326 - Avoid a double-marked-circuit warning that could happen when we
9327 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9330 o Minor bugfixes (tests):
9331 - Run the entry_guard_parse_from_state_full() test with the time set
9332 to a specific date. (The guard state that this test was parsing
9333 contained guards that had expired since the test was first
9334 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
9337 - Update the description of the directory server options in the
9338 manual page, to clarify that a relay no longer needs to set
9339 DirPort in order to be a directory cache. Closes ticket 21720.
9343 Changes in version 0.2.8.13 - 2017-03-03
9344 Tor 0.2.8.13 backports a security fix from later Tor
9345 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9346 this release, if for some reason they cannot upgrade to a later
9347 release series, and if they build Tor with the --enable-expensive-hardening
9350 Note that support for Tor 0.2.8.x is ending next year: we will not issue
9351 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
9352 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9354 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9355 - Fix an integer underflow bug when comparing malformed Tor
9356 versions. This bug could crash Tor when built with
9357 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9358 0.2.9.8, which were built with -ftrapv by default. In other cases
9359 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9360 on 0.0.8pre1. Found by OSS-Fuzz.
9362 o Minor features (geoip):
9363 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9367 Changes in version 0.2.7.7 - 2017-03-03
9368 Tor 0.2.7.7 backports a number of security fixes from later Tor
9369 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
9370 this release, if for some reason they cannot upgrade to a later
9373 Note that support for Tor 0.2.7.x is ending this year: we will not issue
9374 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
9375 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9377 o Directory authority changes (backport from 0.2.8.5-rc):
9378 - Urras is no longer a directory authority. Closes ticket 19271.
9380 o Directory authority changes (backport from 0.2.9.2-alpha):
9381 - The "Tonga" bridge authority has been retired; the new bridge
9382 authority is "Bifroest". Closes tickets 19728 and 19690.
9384 o Directory authority key updates (backport from 0.2.8.1-alpha):
9385 - Update the V3 identity key for the dannenberg directory authority:
9386 it was changed on 18 November 2015. Closes task 17906. Patch
9389 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9390 - Fix a bug in parsing that could cause clients to read a single
9391 byte past the end of an allocated region. This bug could be used
9392 to cause hardened clients (built with --enable-expensive-hardening)
9393 to crash if they tried to visit a hostile hidden service. Non-
9394 hardened clients are only affected depending on the details of
9395 their platform's memory allocator. Fixes bug 21018; bugfix on
9396 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9397 2016-12-002 and as CVE-2016-1254.
9399 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9400 - Stop a crash that could occur when a client running with DNSPort
9401 received a query with multiple address types, and the first
9402 address type was not supported. Found and fixed by Scott Dial.
9403 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9404 - Prevent a class of security bugs caused by treating the contents
9405 of a buffer chunk as if they were a NUL-terminated string. At
9406 least one such bug seems to be present in all currently used
9407 versions of Tor, and would allow an attacker to remotely crash
9408 most Tor instances, especially those compiled with extra compiler
9409 hardening. With this defense in place, such bugs can't crash Tor,
9410 though we should still fix them as they occur. Closes ticket
9411 20384 (TROVE-2016-10-001).
9413 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9414 - Avoid a difficult-to-trigger heap corruption attack when extending
9415 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9416 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9417 Reported by Guido Vranken.
9419 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9420 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9421 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9423 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9424 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9425 pointer to the previous (uninitialized) key value. The impact here
9426 should be limited to a difficult-to-trigger crash, if OpenSSL is
9427 running an engine that makes key generation failures possible, or
9428 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9429 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9432 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9433 - Fix an integer underflow bug when comparing malformed Tor
9434 versions. This bug could crash Tor when built with
9435 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9436 0.2.9.8, which were built with -ftrapv by default. In other cases
9437 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9438 on 0.0.8pre1. Found by OSS-Fuzz.
9440 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9441 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9442 zero size. Check size argument to memwipe() for underflow. Fixes
9443 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9446 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9447 - Make Tor survive errors involving connections without a
9448 corresponding event object. Previously we'd fail with an
9449 assertion; now we produce a log message. Related to bug 16248.
9451 o Minor features (geoip):
9452 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9456 Changes in version 0.2.6.11 - 2017-03-03
9457 Tor 0.2.6.11 backports a number of security fixes from later Tor
9458 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
9459 this release, if for some reason they cannot upgrade to a later
9462 Note that support for Tor 0.2.6.x is ending this year: we will not issue
9463 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
9464 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9466 o Directory authority changes (backport from 0.2.8.5-rc):
9467 - Urras is no longer a directory authority. Closes ticket 19271.
9469 o Directory authority changes (backport from 0.2.9.2-alpha):
9470 - The "Tonga" bridge authority has been retired; the new bridge
9471 authority is "Bifroest". Closes tickets 19728 and 19690.
9473 o Directory authority key updates (backport from 0.2.8.1-alpha):
9474 - Update the V3 identity key for the dannenberg directory authority:
9475 it was changed on 18 November 2015. Closes task 17906. Patch
9478 o Major features (security fixes, backport from 0.2.9.4-alpha):
9479 - Prevent a class of security bugs caused by treating the contents
9480 of a buffer chunk as if they were a NUL-terminated string. At
9481 least one such bug seems to be present in all currently used
9482 versions of Tor, and would allow an attacker to remotely crash
9483 most Tor instances, especially those compiled with extra compiler
9484 hardening. With this defense in place, such bugs can't crash Tor,
9485 though we should still fix them as they occur. Closes ticket
9486 20384 (TROVE-2016-10-001).
9488 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9489 - Fix a bug in parsing that could cause clients to read a single
9490 byte past the end of an allocated region. This bug could be used
9491 to cause hardened clients (built with --enable-expensive-hardening)
9492 to crash if they tried to visit a hostile hidden service. Non-
9493 hardened clients are only affected depending on the details of
9494 their platform's memory allocator. Fixes bug 21018; bugfix on
9495 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9496 2016-12-002 and as CVE-2016-1254.
9498 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9499 - Stop a crash that could occur when a client running with DNSPort
9500 received a query with multiple address types, and the first
9501 address type was not supported. Found and fixed by Scott Dial.
9502 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9504 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9505 - Fix an error that could cause us to read 4 bytes before the
9506 beginning of an openssl string. This bug could be used to cause
9507 Tor to crash on systems with unusual malloc implementations, or
9508 systems with unusual hardening installed. Fixes bug 17404; bugfix
9511 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9512 - Avoid a difficult-to-trigger heap corruption attack when extending
9513 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9514 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9515 Reported by Guido Vranken.
9517 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9518 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9519 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9521 o Major bugfixes (guard selection, backport from 0.2.7.6):
9522 - Actually look at the Guard flag when selecting a new directory
9523 guard. When we implemented the directory guard design, we
9524 accidentally started treating all relays as if they have the Guard
9525 flag during guard selection, leading to weaker anonymity and worse
9526 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9529 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9530 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9531 pointer to the previous (uninitialized) key value. The impact here
9532 should be limited to a difficult-to-trigger crash, if OpenSSL is
9533 running an engine that makes key generation failures possible, or
9534 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9535 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9538 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9539 - Fix an integer underflow bug when comparing malformed Tor
9540 versions. This bug could crash Tor when built with
9541 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9542 0.2.9.8, which were built with -ftrapv by default. In other cases
9543 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9544 on 0.0.8pre1. Found by OSS-Fuzz.
9546 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9547 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9548 zero size. Check size argument to memwipe() for underflow. Fixes
9549 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9552 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9553 - Make Tor survive errors involving connections without a
9554 corresponding event object. Previously we'd fail with an
9555 assertion; now we produce a log message. Related to bug 16248.
9557 o Minor features (geoip):
9558 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9561 o Minor bugfixes (compilation, backport from 0.2.7.6):
9562 - Fix a compilation warning with Clang 3.6: Do not check the
9563 presence of an address which can never be NULL. Fixes bug 17781.
9566 Changes in version 0.2.5.13 - 2017-03-03
9567 Tor 0.2.5.13 backports a number of security fixes from later Tor
9568 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9569 this release, if for some reason they cannot upgrade to a later
9572 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9573 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9574 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9576 o Directory authority changes (backport from 0.2.8.5-rc):
9577 - Urras is no longer a directory authority. Closes ticket 19271.
9579 o Directory authority changes (backport from 0.2.9.2-alpha):
9580 - The "Tonga" bridge authority has been retired; the new bridge
9581 authority is "Bifroest". Closes tickets 19728 and 19690.
9583 o Directory authority key updates (backport from 0.2.8.1-alpha):
9584 - Update the V3 identity key for the dannenberg directory authority:
9585 it was changed on 18 November 2015. Closes task 17906. Patch
9588 o Major features (security fixes, backport from 0.2.9.4-alpha):
9589 - Prevent a class of security bugs caused by treating the contents
9590 of a buffer chunk as if they were a NUL-terminated string. At
9591 least one such bug seems to be present in all currently used
9592 versions of Tor, and would allow an attacker to remotely crash
9593 most Tor instances, especially those compiled with extra compiler
9594 hardening. With this defense in place, such bugs can't crash Tor,
9595 though we should still fix them as they occur. Closes ticket
9596 20384 (TROVE-2016-10-001).
9598 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9599 - Fix a bug in parsing that could cause clients to read a single
9600 byte past the end of an allocated region. This bug could be used
9601 to cause hardened clients (built with --enable-expensive-hardening)
9602 to crash if they tried to visit a hostile hidden service. Non-
9603 hardened clients are only affected depending on the details of
9604 their platform's memory allocator. Fixes bug 21018; bugfix on
9605 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9606 2016-12-002 and as CVE-2016-1254.
9608 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9609 - Stop a crash that could occur when a client running with DNSPort
9610 received a query with multiple address types, and the first
9611 address type was not supported. Found and fixed by Scott Dial.
9612 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9614 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9615 - Fix an error that could cause us to read 4 bytes before the
9616 beginning of an openssl string. This bug could be used to cause
9617 Tor to crash on systems with unusual malloc implementations, or
9618 systems with unusual hardening installed. Fixes bug 17404; bugfix
9621 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9622 - Avoid a difficult-to-trigger heap corruption attack when extending
9623 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9624 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9625 Reported by Guido Vranken.
9627 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9628 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9629 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9631 o Major bugfixes (guard selection, backport from 0.2.7.6):
9632 - Actually look at the Guard flag when selecting a new directory
9633 guard. When we implemented the directory guard design, we
9634 accidentally started treating all relays as if they have the Guard
9635 flag during guard selection, leading to weaker anonymity and worse
9636 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9639 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9640 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9641 pointer to the previous (uninitialized) key value. The impact here
9642 should be limited to a difficult-to-trigger crash, if OpenSSL is
9643 running an engine that makes key generation failures possible, or
9644 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9645 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9648 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9649 - Fix an integer underflow bug when comparing malformed Tor
9650 versions. This bug could crash Tor when built with
9651 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9652 0.2.9.8, which were built with -ftrapv by default. In other cases
9653 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9654 on 0.0.8pre1. Found by OSS-Fuzz.
9656 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9657 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9658 zero size. Check size argument to memwipe() for underflow. Fixes
9659 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9662 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9663 - Make Tor survive errors involving connections without a
9664 corresponding event object. Previously we'd fail with an
9665 assertion; now we produce a log message. Related to bug 16248.
9667 o Minor features (geoip):
9668 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9671 o Minor bugfixes (compilation, backport from 0.2.7.6):
9672 - Fix a compilation warning with Clang 3.6: Do not check the
9673 presence of an address which can never be NULL. Fixes bug 17781.
9675 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9676 - Check for failures from crypto_early_init, and refuse to continue.
9677 A previous typo meant that we could keep going with an
9678 uninitialized crypto library, and would have OpenSSL initialize
9679 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9680 when implementing ticket 4900. Patch by "teor".
9682 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9683 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9684 a client authorized hidden service. Fixes bug 15823; bugfix
9688 Changes in version 0.2.4.28 - 2017-03-03
9689 Tor 0.2.4.28 backports a number of security fixes from later Tor
9690 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9691 this release, if for some reason they cannot upgrade to a later
9694 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9695 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9696 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9698 o Directory authority changes (backport from 0.2.8.5-rc):
9699 - Urras is no longer a directory authority. Closes ticket 19271.
9701 o Directory authority changes (backport from 0.2.9.2-alpha):
9702 - The "Tonga" bridge authority has been retired; the new bridge
9703 authority is "Bifroest". Closes tickets 19728 and 19690.
9705 o Directory authority key updates (backport from 0.2.8.1-alpha):
9706 - Update the V3 identity key for the dannenberg directory authority:
9707 it was changed on 18 November 2015. Closes task 17906. Patch
9710 o Major features (security fixes, backport from 0.2.9.4-alpha):
9711 - Prevent a class of security bugs caused by treating the contents
9712 of a buffer chunk as if they were a NUL-terminated string. At
9713 least one such bug seems to be present in all currently used
9714 versions of Tor, and would allow an attacker to remotely crash
9715 most Tor instances, especially those compiled with extra compiler
9716 hardening. With this defense in place, such bugs can't crash Tor,
9717 though we should still fix them as they occur. Closes ticket
9718 20384 (TROVE-2016-10-001).
9720 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9721 - Fix a bug in parsing that could cause clients to read a single
9722 byte past the end of an allocated region. This bug could be used
9723 to cause hardened clients (built with --enable-expensive-hardening)
9724 to crash if they tried to visit a hostile hidden service. Non-
9725 hardened clients are only affected depending on the details of
9726 their platform's memory allocator. Fixes bug 21018; bugfix on
9727 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9728 2016-12-002 and as CVE-2016-1254.
9730 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9731 - Fix an error that could cause us to read 4 bytes before the
9732 beginning of an openssl string. This bug could be used to cause
9733 Tor to crash on systems with unusual malloc implementations, or
9734 systems with unusual hardening installed. Fixes bug 17404; bugfix
9737 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9738 - Avoid a difficult-to-trigger heap corruption attack when extending
9739 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9740 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9741 Reported by Guido Vranken.
9743 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9744 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9745 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9747 o Major bugfixes (guard selection, backport from 0.2.7.6):
9748 - Actually look at the Guard flag when selecting a new directory
9749 guard. When we implemented the directory guard design, we
9750 accidentally started treating all relays as if they have the Guard
9751 flag during guard selection, leading to weaker anonymity and worse
9752 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9755 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9756 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9757 pointer to the previous (uninitialized) key value. The impact here
9758 should be limited to a difficult-to-trigger crash, if OpenSSL is
9759 running an engine that makes key generation failures possible, or
9760 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9761 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9764 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9765 - Fix an integer underflow bug when comparing malformed Tor
9766 versions. This bug could crash Tor when built with
9767 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9768 0.2.9.8, which were built with -ftrapv by default. In other cases
9769 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9770 on 0.0.8pre1. Found by OSS-Fuzz.
9772 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9773 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9774 zero size. Check size argument to memwipe() for underflow. Fixes
9775 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9778 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9779 - Make Tor survive errors involving connections without a
9780 corresponding event object. Previously we'd fail with an
9781 assertion; now we produce a log message. Related to bug 16248.
9783 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
9784 - Make it harder for attackers to overload hidden services with
9785 introductions, by blocking multiple introduction requests on the
9786 same circuit. Resolves ticket 15515.
9788 o Minor features (geoip):
9789 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9792 o Minor bugfixes (compilation, backport from 0.2.7.6):
9793 - Fix a compilation warning with Clang 3.6: Do not check the
9794 presence of an address which can never be NULL. Fixes bug 17781.
9796 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9797 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9798 a client authorized hidden service. Fixes bug 15823; bugfix
9802 Changes in version 0.3.0.4-rc - 2017-03-01
9803 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
9804 0.3.0 release series, and introduces a few reliability features to
9805 keep them from coming back.
9807 This is the first release candidate in the Tor 0.3.0 series. If we
9808 find no new bugs or regressions here, the first stable 0.3.0 release
9809 will be nearly identical to it.
9811 o Major bugfixes (bridges):
9812 - When the same bridge is configured multiple times with the same
9813 identity, but at different address:port combinations, treat those
9814 bridge instances as separate guards. This fix restores the ability
9815 of clients to configure the same bridge with multiple pluggable
9816 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
9818 o Major bugfixes (hidden service directory v3):
9819 - Stop crashing on a failed v3 hidden service descriptor lookup
9820 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
9822 o Major bugfixes (parsing):
9823 - When parsing a malformed content-length field from an HTTP
9824 message, do not read off the end of the buffer. This bug was a
9825 potential remote denial-of-service attack against Tor clients and
9826 relays. A workaround was released in October 2016, to prevent this
9827 bug from crashing Tor. This is a fix for the underlying issue,
9828 which should no longer matter (if you applied the earlier patch).
9829 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
9830 using AFL (http://lcamtuf.coredump.cx/afl/).
9831 - Fix an integer underflow bug when comparing malformed Tor
9832 versions. This bug could crash Tor when built with
9833 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9834 0.2.9.8, which were built with -ftrapv by default. In other cases
9835 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9836 on 0.0.8pre1. Found by OSS-Fuzz.
9838 o Minor feature (protocol versioning):
9839 - Add new protocol version for proposal 224. HSIntro now advertises
9840 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
9842 o Minor features (directory authorities):
9843 - Directory authorities now reject descriptors that claim to be
9844 malformed versions of Tor. Helps prevent exploitation of
9846 - Reject version numbers with components that exceed INT32_MAX.
9847 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9848 Fixes bug 21450; bugfix on 0.0.8pre1.
9849 - Directory authorities now reject relays running versions
9850 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
9851 suffer from bug 20499 and don't keep their consensus cache
9852 up-to-date. Resolves ticket 20509.
9854 o Minor features (geoip):
9855 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9858 o Minor features (reliability, crash):
9859 - Try better to detect problems in buffers where they might grow (or
9860 think they have grown) over 2 GB in size. Diagnostic for
9863 o Minor features (testing):
9864 - During 'make test-network-all', if tor logs any warnings, ask
9865 chutney to output them. Requires a recent version of chutney with
9866 the 21572 patch. Implements 21570.
9868 o Minor bugfixes (certificate expiration time):
9869 - Avoid using link certificates that don't become valid till some
9870 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
9872 o Minor bugfixes (code correctness):
9873 - Repair a couple of (unreachable or harmless) cases of the risky
9874 comparison-by-subtraction pattern that caused bug 21278.
9875 - Remove a redundant check for the UseEntryGuards option from the
9876 options_transition_affects_guards() function. Fixes bug 21492;
9877 bugfix on 0.3.0.1-alpha.
9879 o Minor bugfixes (directory mirrors):
9880 - Allow relays to use directory mirrors without a DirPort: these
9881 relays need to be contacted over their ORPorts using a begindir
9882 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
9883 - Clarify the message logged when a remote relay is unexpectedly
9884 missing an ORPort or DirPort: users were confusing this with a
9885 local port. Fixes another case of bug 20711; bugfix
9888 o Minor bugfixes (guards):
9889 - Don't warn about a missing guard state on timeout-measurement
9890 circuits: they aren't supposed to be using guards. Fixes an
9891 instance of bug 21007; bugfix on 0.3.0.1-alpha.
9892 - Silence a BUG() warning when attempting to use a guard whose
9893 descriptor we don't know, and make this scenario less likely to
9894 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
9896 o Minor bugfixes (hidden service):
9897 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
9898 cells. Previously, we were using sizeof() on a pointer, instead of
9899 the real destination buffer. Fortunately, that value was only used
9900 to double-check that there was enough room--which was already
9901 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
9903 o Minor bugfixes (testing):
9904 - Fix Raspbian build issues related to missing socket errno in
9905 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
9907 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
9908 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
9909 - Use bash in src/test/test-network.sh. This ensures we reliably
9910 call chutney's newer tools/test-network.sh when available. Fixes
9911 bug 21562; bugfix on 0.2.9.1-alpha.
9914 - Small fixes to the fuzzing documentation. Closes ticket 21472.
9917 Changes in version 0.2.9.10 - 2017-03-01
9918 Tor 0.2.9.10 backports a security fix from later Tor release. It also
9919 includes fixes for some major issues affecting directory authorities,
9920 LibreSSL compatibility, and IPv6 correctness.
9922 The Tor 0.2.9.x release series is now marked as a long-term-support
9923 series. We intend to backport security fixes to 0.2.9.x until at
9924 least January of 2020.
9926 o Major bugfixes (directory authority, 0.3.0.3-alpha):
9927 - During voting, when marking a relay as a probable sybil, do not
9928 clear its BadExit flag: sybils can still be bad in other ways
9929 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9932 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
9933 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9934 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9935 exit policy rejects that port on more than an IPv6 /16 of
9936 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9937 which rejected a relay's own IPv6 address by default. Fixes bug
9938 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9940 o Major bugfixes (parsing, also in 0.3.0.4-rc):
9941 - Fix an integer underflow bug when comparing malformed Tor
9942 versions. This bug could crash Tor when built with
9943 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9944 0.2.9.8, which were built with -ftrapv by default. In other cases
9945 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9946 on 0.0.8pre1. Found by OSS-Fuzz.
9948 o Minor features (directory authorities, also in 0.3.0.4-rc):
9949 - Directory authorities now reject descriptors that claim to be
9950 malformed versions of Tor. Helps prevent exploitation of
9952 - Reject version numbers with components that exceed INT32_MAX.
9953 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9954 Fixes bug 21450; bugfix on 0.0.8pre1.
9956 o Minor features (geoip):
9957 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9960 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
9961 - Autoconf now checks to determine if OpenSSL structures are opaque,
9962 instead of explicitly checking for OpenSSL version numbers. Part
9964 - Support building with recent LibreSSL code that uses opaque
9965 structures. Closes ticket 21359.
9967 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
9968 - Repair a couple of (unreachable or harmless) cases of the risky
9969 comparison-by-subtraction pattern that caused bug 21278.
9971 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
9972 - The tor-resolve command line tool now rejects hostnames over 255
9973 characters in length. Previously, it would silently truncate them,
9974 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9975 Patch by "junglefowl".
9978 Changes in version 0.3.0.3-alpha - 2017-02-03
9979 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
9980 0.3.0.x development series, including some that could cause
9981 authorities to behave badly. There is also a fix for a longstanding
9982 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
9983 includes some smaller features and bugfixes.
9985 The Tor 0.3.0.x release series is now in patch-freeze: no additional
9986 features will be considered for inclusion in 0.3.0.x. We suspect that
9987 some bugs will probably remain, however, and we encourage people to
9990 o Major bugfixes (directory authority):
9991 - During voting, when marking a relay as a probable sybil, do not
9992 clear its BadExit flag: sybils can still be bad in other ways
9993 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9995 - When deciding whether we have just found a router to be reachable,
9996 do not penalize it for not having performed an Ed25519 link
9997 handshake if it does not claim to support an Ed25519 handshake.
9998 Previously, we would treat such relays as non-running. Fixes bug
9999 21107; bugfix on 0.3.0.1-alpha.
10001 o Major bugfixes (entry guards):
10002 - Stop trying to build circuits through entry guards for which we
10003 have no descriptor. Also, stop crashing in the case that we *do*
10004 accidentally try to build a circuit in such a state. Fixes bug
10005 21242; bugfix on 0.3.0.1-alpha.
10007 o Major bugfixes (IPv6 Exits):
10008 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10009 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10010 exit policy rejects that port on more than an IPv6 /16 of
10011 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10012 which rejected a relay's own IPv6 address by default. Fixes bug
10013 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10015 o Minor feature (client):
10016 - Enable IPv6 traffic on the SocksPort by default. To disable this,
10017 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
10019 o Minor feature (fallback scripts):
10020 - Add a check_existing mode to updateFallbackDirs.py, which checks
10021 if fallbacks in the hard-coded list are working. Closes ticket
10022 20174. Patch by haxxpop.
10024 o Minor features (ciphersuite selection):
10025 - Clients now advertise a list of ciphersuites closer to the ones
10026 preferred by Firefox. Closes part of ticket 15426.
10027 - Allow relays to accept a wider range of ciphersuites, including
10028 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
10030 o Minor features (controller, configuration):
10031 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
10032 and so on, now comes with a __*Port variant that will not be saved
10033 to the torrc file by the controller's SAVECONF command. This
10034 change allows TorBrowser to set up a single-use domain socket for
10035 each time it launches Tor. Closes ticket 20956.
10036 - The GETCONF command can now query options that may only be
10037 meaningful in context-sensitive lists. This allows the controller
10038 to query the mixed SocksPort/__SocksPort style options introduced
10039 in feature 20956. Implements ticket 21300.
10041 o Minor features (portability, compilation):
10042 - Autoconf now checks to determine if OpenSSL structures are opaque,
10043 instead of explicitly checking for OpenSSL version numbers. Part
10045 - Support building with recent LibreSSL code that uses opaque
10046 structures. Closes ticket 21359.
10048 o Minor features (relay):
10049 - We now allow separation of exit and relay traffic to different
10050 source IP addresses, using the OutboundBindAddressExit and
10051 OutboundBindAddressOR options respectively. Closes ticket 17975.
10052 Written by Michael Sonntag.
10054 o Minor bugfix (logging):
10055 - Don't recommend the use of Tor2web in non-anonymous mode.
10056 Recommending Tor2web is a bad idea because the client loses all
10057 anonymity. Tor2web should only be used in specific cases by users
10058 who *know* and understand the issues. Fixes bug 21294; bugfix
10061 o Minor bugfixes (client):
10062 - Always recover from failures in extend_info_from_node(), in an
10063 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
10064 bugfix on 0.2.3.1-alpha.
10066 o Minor bugfixes (client, entry guards):
10067 - Fix a bug warning (with backtrace) when we fail a channel that
10068 circuits to fallback directories on it. Fixes bug 21128; bugfix
10070 - Fix a spurious bug warning (with backtrace) when removing an
10071 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
10072 - Fix a bug of the new guard algorithm where tor could stall for up
10073 to 10 minutes before retrying a guard after a long period of no
10074 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
10075 - Do not try to build circuits until we have descriptors for our
10076 primary entry guards. Related to fix for bug 21242.
10078 o Minor bugfixes (configure, autoconf):
10079 - Rename the configure option --enable-expensive-hardening to
10080 --enable-fragile-hardening. Expensive hardening makes the tor
10081 daemon abort when some kinds of issues are detected. Thus, it
10082 makes tor more at risk of remote crashes but safer against RCE or
10083 heartbleed bug category. We now try to explain this issue in a
10084 message from the configure script. Fixes bug 21290; bugfix
10087 o Minor bugfixes (controller):
10088 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
10089 20824; bugfix on 0.3.0.1-alpha.
10091 o Minor bugfixes (hidden service):
10092 - Clean up the code for expiring intro points with no associated
10093 circuits. It was causing, rarely, a service with some expiring
10094 introduction points to not open enough additional introduction
10095 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
10096 - Stop setting the torrc option HiddenServiceStatistics to "0" just
10097 because we're not a bridge or relay. Instead, we preserve whatever
10098 value the user set (or didn't set). Fixes bug 21150; bugfix
10100 - Resolve two possible underflows which could lead to creating and
10101 closing a lot of introduction point circuits in a non-stop loop.
10102 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
10104 o Minor bugfixes (portability):
10105 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
10106 It is supported by OpenBSD itself, and also by most OpenBSD
10107 variants (such as Bitrig). Fixes bug 20980; bugfix
10109 - When mapping a file of length greater than SIZE_MAX, do not
10110 silently truncate its contents. This issue could occur on 32 bit
10111 systems with large file support and files which are larger than 4
10112 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
10114 o Minor bugfixes (tor-resolve):
10115 - The tor-resolve command line tool now rejects hostnames over 255
10116 characters in length. Previously, it would silently truncate them,
10117 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10118 Patch by "junglefowl".
10120 o Minor bugfixes (Windows services):
10121 - Be sure to initialize the monotonic time subsystem before using
10122 it, even when running as an NT service. Fixes bug 21356; bugfix
10126 Changes in version 0.3.0.2-alpha - 2017-01-23
10127 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
10128 cause relays and clients to crash, even if they were not built with
10129 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10130 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10131 version should upgrade.
10133 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
10134 time-to-live values, makes directory authorities enforce the 1-to-1
10135 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
10136 client-side onion service reachability bug, does better at selecting
10137 the set of fallback directories, and more.
10139 o Major bugfixes (security, also in 0.2.9.9):
10140 - Downgrade the "-ftrapv" option from "always on" to "only on when
10141 --enable-expensive-hardening is provided." This hardening option, like
10142 others, can turn survivable bugs into crashes--and having it on by
10143 default made a (relatively harmless) integer overflow bug into a
10144 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
10147 o Major features (security):
10148 - Change the algorithm used to decide DNS TTLs on client and server
10149 side, to better resist DNS-based correlation attacks like the
10150 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10151 Feamster. Now relays only return one of two possible DNS TTL
10152 values, and clients are willing to believe DNS TTL values up to 3
10153 hours long. Closes ticket 19769.
10155 o Major features (directory authority, security):
10156 - The default for AuthDirPinKeys is now 1: directory authorities
10157 will reject relays where the RSA identity key matches a previously
10158 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10160 o Major bugfixes (client, guard, crash):
10161 - In circuit_get_global_origin_list(), return the actual list of
10162 origin circuits. The previous version of this code returned the
10163 list of all the circuits, and could have caused strange bugs,
10164 including possible crashes. Fixes bug 21118; bugfix
10167 o Major bugfixes (client, onion service, also in 0.2.9.9):
10168 - Fix a client-side onion service reachability bug, where multiple
10169 socks requests to an onion service (or a single slow request)
10170 could cause us to mistakenly mark some of the service's
10171 introduction points as failed, and we cache that failure so
10172 eventually we run out and can't reach the service. Also resolves a
10173 mysterious "Remote server sent bogus reason code 65021" log
10174 warning. The bug was introduced in ticket 17218, where we tried to
10175 remember the circuit end reason as a uint16_t, which mangled
10176 negative values. Partially fixes bug 21056 and fixes bug 20307;
10177 bugfix on 0.2.8.1-alpha.
10179 o Major bugfixes (DNS):
10180 - Fix a bug that prevented exit nodes from caching DNS records for
10181 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10183 o Minor features (controller):
10184 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10185 shared-random values to the controller. Closes ticket 19925.
10187 o Minor features (entry guards):
10188 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10189 break regression tests.
10190 - Require UseEntryGuards when UseBridges is set, in order to make
10191 sure bridges aren't bypassed. Resolves ticket 20502.
10193 o Minor features (fallback directories):
10194 - Select 200 fallback directories for each release. Closes
10196 - Allow 3 fallback relays per operator, which is safe now that we
10197 are choosing 200 fallback relays. Closes ticket 20912.
10198 - Exclude relays affected by bug 20499 from the fallback list.
10199 Exclude relays from the fallback list if they are running versions
10200 known to be affected by bug 20499, or if in our tests they deliver
10201 a stale consensus (i.e. one that expired more than 24 hours ago).
10202 Closes ticket 20539.
10203 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10205 - Require fallback directories to have the same address and port for
10206 7 days (now that we have enough relays with this stability).
10207 Relays whose OnionOO stability timer is reset on restart by bug
10208 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10209 this issue. Closes ticket 20880; maintains short-term fix
10211 - Require fallbacks to have flags for 90% of the time (weighted
10212 decaying average), rather than 95%. This allows at least 73% of
10213 clients to bootstrap in the first 5 seconds without contacting an
10214 authority. Part of ticket 18828.
10215 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10216 weight for each candidate fallback. Closes ticket 20878.
10217 - Make it easier to change the output sort order of fallbacks.
10218 Closes ticket 20822.
10219 - Display the relay fingerprint when downloading consensuses from
10220 fallbacks. Closes ticket 20908.
10222 o Minor features (geoip, also in 0.2.9.9):
10223 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10226 o Minor features (next-gen onion service directories):
10227 - Remove the "EnableOnionServicesV3" consensus parameter that we
10228 introduced in 0.3.0.1-alpha: relays are now always willing to act
10229 as v3 onion service directories. Resolves ticket 19899.
10231 o Minor features (linting):
10232 - Enhance the changes file linter to warn on Tor versions that are
10233 prefixed with "tor-". Closes ticket 21096.
10235 o Minor features (logging):
10236 - In several places, describe unset ed25519 keys as "<unset>",
10237 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10239 o Minor bugfix (control protocol):
10240 - The reply to a "GETINFO config/names" request via the control
10241 protocol now spells the type "Dependent" correctly. This is a
10242 breaking change in the control protocol. (The field seems to be
10243 ignored by the most common known controllers.) Fixes bug 18146;
10244 bugfix on 0.1.1.4-alpha.
10246 o Minor bugfixes (bug resilience):
10247 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
10248 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
10249 Hans Jerry Illikainen.
10251 o Minor bugfixes (build):
10252 - Replace obsolete Autoconf macros with their modern equivalent and
10253 prevent similar issues in the future. Fixes bug 20990; bugfix
10256 o Minor bugfixes (client, guards):
10257 - Fix bug where Tor would think that there are circuits waiting for
10258 better guards even though those circuits have been freed. Fixes
10259 bug 21142; bugfix on 0.3.0.1-alpha.
10261 o Minor bugfixes (config):
10262 - Don't assert on startup when trying to get the options list and
10263 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
10264 options so of course they aren't ready yet. Fixes bug 21062;
10265 bugfix on 0.2.9.3-alpha.
10267 o Minor bugfixes (controller):
10268 - Make the GETINFO interface for inquiring about entry guards
10269 support the new guards backend. Fixes bug 20823; bugfix
10272 o Minor bugfixes (dead code):
10273 - Remove a redundant check for PidFile changes at runtime in
10274 options_transition_allowed(): this check is already performed
10275 regardless of whether the sandbox is active. Fixes bug 21123;
10276 bugfix on 0.2.5.4-alpha.
10278 o Minor bugfixes (documentation):
10279 - Update the tor manual page to document every option that can not
10280 be changed while tor is running. Fixes bug 21122.
10282 o Minor bugfixes (fallback directories):
10283 - Stop failing when a relay has no uptime data in
10284 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
10285 - Avoid checking fallback candidates' DirPorts if they are down in
10286 OnionOO. When a relay operator has multiple relays, this
10287 prioritizes relays that are up over relays that are down. Fixes
10288 bug 20926; bugfix on 0.2.8.3-alpha.
10289 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
10290 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
10292 o Minor bugfixes (guards, bootstrapping):
10293 - When connecting to a directory guard during bootstrap, do not mark
10294 the guard as successful until we receive a good-looking directory
10295 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
10297 o Minor bugfixes (onion services):
10298 - Fix the config reload pruning of old vs new services so it
10299 actually works when both ephemeral and non-ephemeral services are
10300 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
10301 - Allow the number of introduction points to be as low as 0, rather
10302 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
10304 o Minor bugfixes (IPv6):
10305 - Make IPv6-using clients try harder to find an IPv6 directory
10306 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
10307 - When IPv6 addresses have not been downloaded yet (microdesc
10308 consensus documents don't list relay IPv6 addresses), use hard-
10309 coded addresses for authorities, fallbacks, and configured
10310 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
10311 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
10313 o Minor bugfixes (memory leaks):
10314 - Fix a memory leak when configuring hidden services. Fixes bug
10315 20987; bugfix on 0.3.0.1-alpha.
10317 o Minor bugfixes (portability, also in 0.2.9.9):
10318 - Avoid crashing when Tor is built using headers that contain
10319 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10320 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10322 - Fix Libevent detection on platforms without Libevent 1 headers
10323 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10325 o Minor bugfixes (relay):
10326 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
10327 initializing the keys would reset the DataDirectory to 0700
10328 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
10329 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
10331 o Minor bugfixes (testing):
10332 - Remove undefined behavior from the backtrace generator by removing
10333 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
10335 o Minor bugfixes (unit tests):
10336 - Allow the unit tests to pass even when DNS lookups of bogus
10337 addresses do not fail as expected. Fixes bug 20862 and 20863;
10338 bugfix on unit tests introduced in 0.2.8.1-alpha
10339 through 0.2.9.4-alpha.
10341 o Code simplification and refactoring:
10342 - Refactor code to manipulate global_origin_circuit_list into
10343 separate functions. Closes ticket 20921.
10345 o Documentation (formatting):
10346 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
10347 blocks were incorrectly appearing. Closes ticket 20885.
10349 o Documentation (man page):
10350 - Clarify many options in tor.1 and add some min/max values for
10351 HiddenService options. Closes ticket 21058.
10354 Changes in version 0.2.9.9 - 2017-01-23
10355 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
10356 cause relays and clients to crash, even if they were not built with
10357 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10358 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10359 version should upgrade.
10361 This release also resolves a client-side onion service reachability
10362 bug, and resolves a pair of small portability issues.
10364 o Major bugfixes (security):
10365 - Downgrade the "-ftrapv" option from "always on" to "only on when
10366 --enable-expensive-hardening is provided." This hardening option,
10367 like others, can turn survivable bugs into crashes -- and having
10368 it on by default made a (relatively harmless) integer overflow bug
10369 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10370 bugfix on 0.2.9.1-alpha.
10372 o Major bugfixes (client, onion service):
10373 - Fix a client-side onion service reachability bug, where multiple
10374 socks requests to an onion service (or a single slow request)
10375 could cause us to mistakenly mark some of the service's
10376 introduction points as failed, and we cache that failure so
10377 eventually we run out and can't reach the service. Also resolves a
10378 mysterious "Remote server sent bogus reason code 65021" log
10379 warning. The bug was introduced in ticket 17218, where we tried to
10380 remember the circuit end reason as a uint16_t, which mangled
10381 negative values. Partially fixes bug 21056 and fixes bug 20307;
10382 bugfix on 0.2.8.1-alpha.
10384 o Minor features (geoip):
10385 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10388 o Minor bugfixes (portability):
10389 - Avoid crashing when Tor is built using headers that contain
10390 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10391 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10393 - Fix Libevent detection on platforms without Libevent 1 headers
10394 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10397 Changes in version 0.3.0.1-alpha - 2016-12-19
10398 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
10399 series. It strengthens Tor's link and circuit handshakes by
10400 identifying relays by their Ed25519 keys, improves the algorithm that
10401 clients use to choose and maintain their list of guards, and includes
10402 additional backend support for the next-generation hidden service
10403 design. It also contains numerous other small features and
10404 improvements to security, correctness, and performance.
10406 Below are the changes since 0.2.9.8.
10408 o Major features (guard selection algorithm):
10409 - Tor's guard selection algorithm has been redesigned from the
10410 ground up, to better support unreliable networks and restrictive
10411 sets of entry nodes, and to better resist guard-capture attacks by
10412 hostile local networks. Implements proposal 271; closes
10415 o Major features (next-generation hidden services):
10416 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10417 prop224 aka "Next Generation Hidden Services". Service and clients
10418 don't use this functionality yet. Closes ticket 19043. Based on
10419 initial code by Alec Heifetz.
10420 - Relays now support the HSDir version 3 protocol, so that they can
10421 can store and serve v3 descriptors. This is part of the next-
10422 generation onion service work detailed in proposal 224. Closes
10425 o Major features (protocol, ed25519 identity keys):
10426 - Relays now use Ed25519 to prove their Ed25519 identities and to
10427 one another, and to clients. This algorithm is faster and more
10428 secure than the RSA-based handshake we've been doing until now.
10429 Implements the second big part of proposal 220; Closes
10431 - Clients now support including Ed25519 identity keys in the EXTEND2
10432 cells they generate. By default, this is controlled by a consensus
10433 parameter, currently disabled. You can turn this feature on for
10434 testing by setting ExtendByEd25519ID in your configuration. This
10435 might make your traffic appear different than the traffic
10436 generated by other users, however. Implements part of ticket
10437 15056; part of proposal 220.
10438 - Relays now understand requests to extend to other relays by their
10439 Ed25519 identity keys. When an Ed25519 identity key is included in
10440 an EXTEND2 cell, the relay will only extend the circuit if the
10441 other relay can prove ownership of that identity. Implements part
10442 of ticket 15056; part of proposal 220.
10444 o Major bugfixes (scheduler):
10445 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10446 caused the channel scheduler to behave more or less randomly,
10447 rather than preferring channels with higher-priority circuits.
10448 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10450 o Minor features (controller):
10451 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10452 rather than "unrecognized." Closes ticket 20389; patch from
10455 o Minor features (diagnostic, directory client):
10456 - Warn when we find an unexpected inconsistency in directory
10457 download status objects. Prevents some negative consequences of
10460 o Minor features (directory authority):
10461 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10462 default) to control whether authorities should try to probe relays
10463 by their Ed25519 link keys. This option will go away in a few
10464 releases--unless we encounter major trouble in our ed25519 link
10465 protocol rollout, in which case it will serve as a safety option.
10467 o Minor features (directory cache):
10468 - Relays and bridges will now refuse to serve the consensus they
10469 have if they know it is too old for a client to use. Closes
10472 o Minor features (ed25519 link handshake):
10473 - Advertise support for the ed25519 link handshake using the
10474 subprotocol-versions mechanism, so that clients can tell which
10475 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10477 o Minor features (fingerprinting resistance, authentication):
10478 - Extend the length of RSA keys used for TLS link authentication to
10479 2048 bits. (These weren't used for forward secrecy; for forward
10480 secrecy, we used P256.) Closes ticket 13752.
10482 o Minor features (infrastructure):
10483 - Implement smartlist_add_strdup() function. Replaces the use of
10484 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10486 o Minor bugfixes (client):
10487 - When clients that use bridges start up with a cached consensus on
10488 disk, they were ignoring it and downloading a new one. Now they
10489 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
10491 o Minor bugfixes (configuration):
10492 - Accept non-space whitespace characters after the severity level in
10493 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
10494 - Support "TByte" and "TBytes" units in options given in bytes.
10495 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
10496 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
10498 o Minor bugfixes (consensus weight):
10499 - Add new consensus method that initializes bw weights to 1 instead
10500 of 0. This prevents a zero weight from making it all the way to
10501 the end (happens in small testing networks) and causing an error.
10502 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
10504 o Minor bugfixes (descriptors):
10505 - Correctly recognise downloaded full descriptors as valid, even
10506 when using microdescriptors as circuits. This affects clients with
10507 FetchUselessDescriptors set, and may affect directory authorities.
10508 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
10510 o Minor bugfixes (directory system):
10511 - Download all consensus flavors, descriptors, and authority
10512 certificates when FetchUselessDescriptors is set, regardless of
10513 whether tor is a directory cache or not. Fixes bug 20667; bugfix
10514 on all recent tor versions.
10515 - Bridges and relays now use microdescriptors (like clients do)
10516 rather than old-style router descriptors. Now bridges will blend
10517 in with clients in terms of the circuits they build. Fixes bug
10518 6769; bugfix on 0.2.3.2-alpha.
10520 o Minor bugfixes (ed25519 certificates):
10521 - Correctly interpret ed25519 certificates that would expire some
10522 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
10524 o Minor bugfixes (hidden services):
10525 - Stop ignoring misconfigured hidden services. Instead, refuse to
10526 start tor until the misconfigurations have been corrected. Fixes
10527 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
10530 o Minor bugfixes (memory leak at exit):
10531 - Fix a small harmless memory leak at exit of the previously unused
10532 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
10535 o Minor bugfixes (util):
10536 - When finishing writing a file to disk, if we were about to replace
10537 the file with the temporary file created before and we fail to
10538 replace it, remove the temporary file so it doesn't stay on disk.
10539 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10541 o Minor bugfixes (Windows):
10542 - Check for getpagesize before using it to mmap files. This fixes
10543 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10544 0.1.2.1-alpha. Reported by "ice".
10546 o Code simplification and refactoring:
10547 - Abolish all global guard context in entrynodes.c; replace with new
10548 guard_selection_t structure as preparation for proposal 271.
10549 Closes ticket 19858.
10550 - Introduce rend_service_is_ephemeral() that tells if given onion
10551 service is ephemeral. Replace unclear NULL-checkings for service
10552 directory with this function. Closes ticket 20526.
10553 - Extract magic numbers in circuituse.c into defined variables.
10554 - Refactor circuit_is_available_for_use to remove unnecessary check.
10555 - Refactor circuit_predict_and_launch_new for readability and
10556 testability. Closes ticket 18873.
10557 - Refactor large if statement in purpose_needs_anonymity to use
10558 switch statement instead. Closes part of ticket 20077.
10559 - Refactor the hashing API to return negative values for errors, as
10560 is done as throughout the codebase. Closes ticket 20717.
10561 - Remove data structures that were used to index or_connection
10562 objects by their RSA identity digests. These structures are fully
10563 redundant with the similar structures used in the
10564 channel abstraction.
10565 - Remove duplicate code in the channel_write_*cell() functions.
10566 Closes ticket 13827; patch from Pingl.
10567 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10568 use only purpose_needs_anonymity. Closes part of ticket 20077.
10569 - The code to generate and parse EXTEND and EXTEND2 cells has been
10570 replaced with code automatically generated by the
10574 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10575 20622; bugfix on 0.2.5.1-alpha.
10576 - Change '1' to 'weight_scale' in consensus bw weights calculation
10577 comments, as that is reality. Closes ticket 20273. Patch
10579 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10580 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10582 - Stop the man page from incorrectly stating that HiddenServiceDir
10583 must already exist. Fixes 20486.
10584 - Clarify that when ClientRejectInternalAddresses is enabled (which
10585 is the default), multicast DNS hostnames for machines on the local
10586 network (of the form *.local) are also rejected. Closes
10589 o Removed features:
10590 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10591 limit for relays running on a single IP applies to authority IP
10592 addresses as well as to non-authority IP addresses. Closes
10594 - The UseDirectoryGuards torrc option no longer exists: all users
10595 that use entry guards will also use directory guards. Related to
10596 proposal 271; implements part of ticket 20831.
10599 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10600 from "overcaffeinated".
10601 - Perform the coding style checks when running the tests and fail
10602 when coding style violations are found. Closes ticket 5500.
10603 - Add tests for networkstatus_compute_bw_weights_v10.
10604 - Add unit tests circuit_predict_and_launch_new.
10605 - Extract dummy_origin_circuit_new so it can be used by other
10609 Changes in version 0.2.8.12 - 2016-12-19
10610 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10611 below) where Tor clients could crash when attempting to visit a
10612 hostile hidden service. Clients are recommended to upgrade as packages
10613 become available for their systems.
10615 It also includes an updated list of fallback directories, backported
10618 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10619 backported to 0.2.8 in the future.
10621 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10622 - Fix a bug in parsing that could cause clients to read a single
10623 byte past the end of an allocated region. This bug could be used
10624 to cause hardened clients (built with --enable-expensive-hardening)
10625 to crash if they tried to visit a hostile hidden service. Non-
10626 hardened clients are only affected depending on the details of
10627 their platform's memory allocator. Fixes bug 21018; bugfix on
10628 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10629 2016-12-002 and as CVE-2016-1254.
10631 o Minor features (fallback directory list, backported from 0.2.9.8):
10632 - Replace the 81 remaining fallbacks of the 100 originally
10633 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10634 fallbacks (123 new, 54 existing, 27 removed) generated in December
10635 2016. Resolves ticket 20170.
10637 o Minor features (geoip, backported from 0.2.9.7-rc):
10638 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10642 Changes in version 0.2.9.8 - 2016-12-19
10643 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10645 The Tor 0.2.9 series makes mandatory a number of security features
10646 that were formerly optional. It includes support for a new shared-
10647 randomness protocol that will form the basis for next generation
10648 hidden services, includes a single-hop hidden service mode for
10649 optimizing .onion services that don't actually want to be hidden,
10650 tries harder not to overload the directory authorities with excessive
10651 downloads, and supports a better protocol versioning scheme for
10652 improved compatibility with other implementations of the Tor protocol.
10654 And of course, there are numerous other bugfixes and improvements.
10656 This release also includes a fix for a medium-severity issue (bug
10657 21018 below) where Tor clients could crash when attempting to visit a
10658 hostile hidden service. Clients are recommended to upgrade as packages
10659 become available for their systems.
10661 Below are the changes since 0.2.9.7-rc. For a list of all changes
10662 since 0.2.8, see the ReleaseNotes file.
10664 o Major bugfixes (parsing, security):
10665 - Fix a bug in parsing that could cause clients to read a single
10666 byte past the end of an allocated region. This bug could be used
10667 to cause hardened clients (built with --enable-expensive-hardening)
10668 to crash if they tried to visit a hostile hidden service. Non-
10669 hardened clients are only affected depending on the details of
10670 their platform's memory allocator. Fixes bug 21018; bugfix on
10671 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10672 2016-12-002 and as CVE-2016-1254.
10674 o Minor features (fallback directory list):
10675 - Replace the 81 remaining fallbacks of the 100 originally
10676 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10677 fallbacks (123 new, 54 existing, 27 removed) generated in December
10678 2016. Resolves ticket 20170.
10681 Changes in version 0.2.9.7-rc - 2016-12-12
10682 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10683 including a few that had prevented tests from passing on
10686 o Minor features (geoip):
10687 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10690 o Minor bugfix (build):
10691 - The current Git revision when building from a local repository is
10692 now detected correctly when using git worktrees. Fixes bug 20492;
10693 bugfix on 0.2.3.9-alpha.
10695 o Minor bugfixes (directory authority):
10696 - When computing old Tor protocol line version in protover, we were
10697 looking at 0.2.7.5 twice instead of a specific case for
10698 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10700 o Minor bugfixes (download scheduling):
10701 - Resolve a "bug" warning when considering a download schedule whose
10702 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10704 o Minor bugfixes (logging):
10705 - Downgrade a harmless log message about the
10706 pending_entry_connections list from "warn" to "info". Mitigates
10709 o Minor bugfixes (memory leak):
10710 - Fix a small memory leak when receiving AF_UNIX connections on a
10711 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10712 - When moving a signed descriptor object from a source to an
10713 existing destination, free the allocated memory inside that
10714 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10716 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10717 - Fix a memory leak and use-after-free error when removing entries
10718 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10719 0.2.5.5-alpha. Patch from "cypherpunks".
10721 o Minor bugfixes (portability):
10722 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10723 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10725 o Minor bugfixes (unit tests):
10726 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10727 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10728 - Fix tolerances in unit tests for monotonic time comparisons
10729 between nanoseconds and microseconds. Previously, we accepted a 10
10730 us difference only, which is not realistic on every platform's
10731 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10732 - Remove a double-free in the single onion service unit test. Stop
10733 ignoring a return value. Make future changes less error-prone.
10734 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10737 Changes in version 0.2.8.11 - 2016-12-08
10738 Tor 0.2.8.11 backports fixes for additional portability issues that
10739 could prevent Tor from building correctly on OSX Sierra, or with
10740 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10743 o Minor bugfixes (portability):
10744 - Avoid compilation errors when building on OSX Sierra. Sierra began
10745 to support the getentropy() and clock_gettime() APIs, but created
10746 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10747 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
10748 monotonic time interfaces. Fixes bug 20865. Bugfix
10751 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10752 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10753 architectures. Closes ticket 20588.
10756 Changes in version 0.2.8.10 - 2016-12-02
10757 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
10758 unusable after they left standby mode. It also backports fixes for
10759 a few portability issues and a small but problematic memory leak.
10761 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
10762 - When Tor leaves standby because of a new application request, open
10763 circuits as needed to serve that request. Previously, we would
10764 potentially wait a very long time. Fixes part of bug 19969; bugfix
10767 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
10768 - Clients now respond to new application stream requests immediately
10769 when they arrive, rather than waiting up to one second before
10770 starting to handle them. Fixes part of bug 19969; bugfix
10773 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
10774 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10775 successfully targeting earlier versions of OSX. Resolves
10778 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10779 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10780 20551; bugfix on 0.2.1.1-alpha.
10782 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
10783 - Work around a memory leak in OpenSSL 1.1 when encoding public
10784 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10786 o Minor features (geoip):
10787 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10790 Changes in version 0.2.9.6-rc - 2016-12-02
10791 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
10792 version. We hope that it will be ready to become stable soon, and we
10793 encourage everyone to test this release. If no showstopper bugs are
10794 found here, the next 0.2.9 release will be stable.
10796 o Major bugfixes (relay, resolver, logging):
10797 - For relays that don't know their own address, avoid attempting a
10798 local hostname resolve for each descriptor we download. This
10799 will cut down on the number of "Success: chose address 'x.x.x.x'"
10800 log lines, and also avoid confusing clock jumps if the resolver
10801 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
10803 o Minor bugfixes (client, fascistfirewall):
10804 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
10805 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
10807 o Minor bugfixes (hidden services):
10808 - Stop ignoring the anonymity status of saved keys for hidden
10809 services and single onion services when first starting tor.
10810 Instead, refuse to start tor if any hidden service key has been
10811 used in a different hidden service anonymity mode. Fixes bug
10812 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
10814 o Minor bugfixes (portability):
10815 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10816 successfully targeting earlier versions of OSX. Resolves
10818 - Run correctly when built on Windows build environments that
10819 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
10821 o Minor bugfixes (single onion services, Tor2web):
10822 - Stop complaining about long-term one-hop circuits deliberately
10823 created by single onion services and Tor2web. These log messages
10824 are intended to diagnose issue 8387, which relates to circuits
10825 hanging around forever for no reason. Fixes bug 20613; bugfix on
10826 0.2.9.1-alpha. Reported by "pastly".
10828 o Minor bugfixes (unit tests):
10829 - Stop spurious failures in the local interface address discovery
10830 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
10834 - Correct the minimum bandwidth value in torrc.sample, and queue a
10835 corresponding change for torrc.minimal. Closes ticket 20085.
10838 Changes in version 0.2.9.5-alpha - 2016-11-08
10839 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
10840 version. We believe one or two probably remain, and we encourage
10841 everyone to test this release.
10843 o Major bugfixes (client performance):
10844 - Clients now respond to new application stream requests immediately
10845 when they arrive, rather than waiting up to one second before
10846 starting to handle them. Fixes part of bug 19969; bugfix
10849 o Major bugfixes (client reliability):
10850 - When Tor leaves standby because of a new application request, open
10851 circuits as needed to serve that request. Previously, we would
10852 potentially wait a very long time. Fixes part of bug 19969; bugfix
10855 o Major bugfixes (download scheduling):
10856 - When using an exponential backoff schedule, do not give up on
10857 downloading just because we have failed a bunch of times. Since
10858 each delay is longer than the last, retrying indefinitely won't
10859 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
10860 - If a consensus expires while we are waiting for certificates to
10861 download, stop waiting for certificates.
10862 - If we stop waiting for certificates less than a minute after we
10863 started downloading them, do not consider the certificate download
10864 failure a separate failure. Fixes bug 20533; bugfix
10866 - Remove the maximum delay on exponential-backoff scheduling. Since
10867 we now allow an infinite number of failures (see ticket 20536), we
10868 must now allow the time to grow longer on each failure. Fixes part
10869 of bug 20534; bugfix on 0.2.9.1-alpha.
10870 - Make our initial download delays closer to those from 0.2.8. Fixes
10871 another part of bug 20534; bugfix on 0.2.9.1-alpha.
10872 - When determining when to download a directory object, handle times
10873 after 2038 if the operating system supports them. (Someday this
10874 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
10875 - When using exponential backoff in test networks, use a lower
10876 exponent, so the delays do not vary as much. This helps test
10877 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
10879 o Minor features (geoip):
10880 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10883 o Minor bugfixes (client directory scheduling):
10884 - Treat "relay too busy to answer request" as a failed request and a
10885 reason to back off on our retry frequency. This is safe now that
10886 exponential backoffs retry indefinitely, and avoids a bug where we
10887 would reset our download schedule erroneously. Fixes bug 20593;
10888 bugfix on 0.2.9.1-alpha.
10890 o Minor bugfixes (client, logging):
10891 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
10892 assume all nodes support EXTEND2. Use ntor whenever a key is
10893 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
10894 - On DNSPort, stop logging a BUG warning on a failed hostname
10895 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
10897 o Minor bugfixes (hidden services):
10898 - When configuring hidden services, check every hidden service
10899 directory's permissions. Previously, we only checked the last
10900 hidden service. Fixes bug 20529; bugfix the work to fix 13942
10903 o Minor bugfixes (portability):
10904 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10905 architectures. Closes ticket 20588.
10906 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
10907 removed the ECDH ciphers which caused the tests to fail on
10908 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
10909 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10910 20551; bugfix on 0.2.1.1-alpha.
10912 o Minor bugfixes (relay bootstrap):
10913 - Ensure relays don't make multiple connections during bootstrap.
10914 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
10916 o Minor bugfixes (relay):
10917 - Work around a memory leak in OpenSSL 1.1 when encoding public
10918 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10919 - Avoid a small memory leak when informing worker threads about
10920 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
10921 - Do not try to parallelize workers more than 16x without the user
10922 explicitly configuring us to do so, even if we do detect more than
10923 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10925 o Minor bugfixes (single onion services):
10926 - Start correctly when creating a single onion service in a
10927 directory that did not previously exist. Fixes bug 20484; bugfix
10930 o Minor bugfixes (testing):
10931 - Avoid a unit test failure on systems with over 16 detectable CPU
10932 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10935 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
10936 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
10937 - Module-level documentation for several more modules. Closes
10938 tickets 19287 and 19290.
10941 Changes in version 0.2.8.9 - 2016-10-17
10942 Tor 0.2.8.9 backports a fix for a security hole in previous versions
10943 of Tor that would allow a remote attacker to crash a Tor client,
10944 hidden service, relay, or authority. All Tor users should upgrade to
10945 this version, or to 0.2.9.4-alpha. Patches will be released for older
10948 o Major features (security fixes, also in 0.2.9.4-alpha):
10949 - Prevent a class of security bugs caused by treating the contents
10950 of a buffer chunk as if they were a NUL-terminated string. At
10951 least one such bug seems to be present in all currently used
10952 versions of Tor, and would allow an attacker to remotely crash
10953 most Tor instances, especially those compiled with extra compiler
10954 hardening. With this defense in place, such bugs can't crash Tor,
10955 though we should still fix them as they occur. Closes ticket
10956 20384 (TROVE-2016-10-001).
10958 o Minor features (geoip):
10959 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10963 Changes in version 0.2.9.4-alpha - 2016-10-17
10964 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
10965 that would allow a remote attacker to crash a Tor client, hidden
10966 service, relay, or authority. All Tor users should upgrade to this
10967 version, or to 0.2.8.9. Patches will be released for older versions
10970 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
10971 previous versions of Tor, including the implementation of a feature to
10972 future- proof the Tor ecosystem against protocol changes, some bug
10973 fixes necessary for Tor Browser to use unix domain sockets correctly,
10974 and several portability improvements. We anticipate that this will be
10975 the last alpha in the Tor 0.2.9 series, and that the next release will
10976 be a release candidate.
10978 o Major features (security fixes):
10979 - Prevent a class of security bugs caused by treating the contents
10980 of a buffer chunk as if they were a NUL-terminated string. At
10981 least one such bug seems to be present in all currently used
10982 versions of Tor, and would allow an attacker to remotely crash
10983 most Tor instances, especially those compiled with extra compiler
10984 hardening. With this defense in place, such bugs can't crash Tor,
10985 though we should still fix them as they occur. Closes ticket
10986 20384 (TROVE-2016-10-001).
10988 o Major features (subprotocol versions):
10989 - Tor directory authorities now vote on a set of recommended
10990 subprotocol versions, and on a set of required subprotocol
10991 versions. Clients and relays that lack support for a _required_
10992 subprotocol version will not start; those that lack support for a
10993 _recommended_ subprotocol version will warn the user to upgrade.
10994 Closes ticket 19958; implements part of proposal 264.
10995 - Tor now uses "subprotocol versions" to indicate compatibility.
10996 Previously, versions of Tor looked at the declared Tor version of
10997 a relay to tell whether they could use a given feature. Now, they
10998 should be able to rely on its declared subprotocol versions. This
10999 change allows compatible implementations of the Tor protocol(s) to
11000 exist without pretending to be 100% bug-compatible with particular
11001 releases of Tor itself. Closes ticket 19958; implements part of
11004 o Minor feature (fallback directories):
11005 - Remove broken fallbacks from the hard-coded fallback directory
11006 list. Closes ticket 20190; patch by teor.
11008 o Minor features (client, directory):
11009 - Since authorities now omit all routers that lack the Running and
11010 Valid flags, we assume that any relay listed in the consensus must
11011 have those flags. Closes ticket 20001; implements part of
11014 o Minor features (compilation, portability):
11015 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
11018 o Minor features (development tools, etags):
11019 - Teach the "make tags" Makefile target how to correctly find
11020 "MOCK_IMPL" function definitions. Patch from nherring; closes
11023 o Minor features (geoip):
11024 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11027 o Minor features (unix domain sockets):
11028 - When configuring a unix domain socket for a SocksPort,
11029 ControlPort, or Hidden service, you can now wrap the address in
11030 quotes, using C-style escapes inside the quotes. This allows unix
11031 domain socket paths to contain spaces.
11033 o Minor features (virtual addresses):
11034 - Increase the maximum number of bits for the IPv6 virtual network
11035 prefix from 16 to 104. In this way, the condition for address
11036 allocation is less restrictive. Closes ticket 20151; feature
11039 o Minor bugfixes (address discovery):
11040 - Stop reordering IP addresses returned by the OS. This makes it
11041 more likely that Tor will guess the same relay IP address every
11042 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
11043 Reported by René Mayrhofer, patch by "cypherpunks".
11045 o Minor bugfixes (client, unix domain sockets):
11046 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
11047 the client address is meaningless. Fixes bug 20261; bugfix
11050 o Minor bugfixes (compilation, OpenBSD):
11051 - Detect Libevent2 functions correctly on systems that provide
11052 libevent2, but where libevent1 is linked with -levent. Fixes bug
11053 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
11055 o Minor bugfixes (configuration):
11056 - When parsing quoted configuration values from the torrc file,
11057 handle windows line endings correctly. Fixes bug 19167; bugfix on
11058 0.2.0.16-alpha. Patch from "Pingl".
11060 o Minor bugfixes (getpass):
11061 - Defensively fix a non-triggerable heap corruption at do_getpass()
11062 to protect ourselves from mistakes in the future. Fixes bug
11063 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
11066 o Minor bugfixes (hidden service):
11067 - Allow hidden services to run on IPv6 addresses even when the
11068 IPv6Exit option is not set. Fixes bug 18357; bugfix
11072 - Add module-level internal documentation for 36 C files that
11073 previously didn't have a high-level overview. Closes ticket #20385.
11075 o Required libraries:
11076 - When building with OpenSSL, Tor now requires version 1.0.1 or
11077 later. OpenSSL 1.0.0 and earlier are no longer supported by the
11078 OpenSSL team, and should not be used. Closes ticket 20303.
11081 Changes in version 0.2.9.3-alpha - 2016-09-23
11082 Tor 0.2.9.3-alpha adds improved support for entities that want to make
11083 high-performance services available through the Tor .onion mechanism
11084 without themselves receiving anonymity as they host those services. It
11085 also tries harder to ensure that all steps on a circuit are using the
11086 strongest crypto possible, strengthens some TLS properties, and
11087 resolves several bugs -- including a pair of crash bugs from the 0.2.8
11088 series. Anybody running an earlier version of 0.2.9.x should upgrade.
11090 o Major bugfixes (crash, also in 0.2.8.8):
11091 - Fix a complicated crash bug that could affect Tor clients
11092 configured to use bridges when replacing a networkstatus consensus
11093 in which one of their bridges was mentioned. OpenBSD users saw
11094 more crashes here, but all platforms were potentially affected.
11095 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11097 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
11098 - Fix a timing-dependent assertion failure that could occur when we
11099 tried to flush from a circuit after having freed its cells because
11100 of an out-of-memory condition. Fixes bug 20203; bugfix on
11101 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11104 o Major features (circuit building, security):
11105 - Authorities, relays and clients now require ntor keys in all
11106 descriptors, for all hops (except for rare hidden service protocol
11107 cases), for all circuits, and for all other roles. Part of
11109 - Tor authorities, relays, and clients only use ntor, except for
11110 rare cases in the hidden service protocol. Part of ticket 19163.
11112 o Major features (single-hop "hidden" services):
11113 - Add experimental HiddenServiceSingleHopMode and
11114 HiddenServiceNonAnonymousMode options. When both are set to 1,
11115 every hidden service on a Tor instance becomes a non-anonymous
11116 Single Onion Service. Single Onions make one-hop (direct)
11117 connections to their introduction and renzedvous points. One-hop
11118 circuits make Single Onion servers easily locatable, but clients
11119 remain location-anonymous. This is compatible with the existing
11120 hidden service implementation, and works on the current tor
11121 network without any changes to older relays or clients. Implements
11122 proposal 260, completes ticket 17178. Patch by teor and asn.
11124 o Major features (resource management):
11125 - Tor can now notice it is about to run out of sockets, and
11126 preemptively close connections of lower priority. (This feature is
11127 off by default for now, since the current prioritizing method is
11128 yet not mature enough. You can enable it by setting
11129 "DisableOOSCheck 0", but watch out: it might close some sockets
11130 you would rather have it keep.) Closes ticket 18640.
11132 o Major bugfixes (circuit building):
11133 - Hidden service client-to-intro-point and service-to-rendezvous-
11134 point circuits use the TAP key supplied by the protocol, to avoid
11135 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
11137 o Major bugfixes (compilation, OpenBSD):
11138 - Fix a Libevent-detection bug in our autoconf script that would
11139 prevent Tor from linking successfully on OpenBSD. Patch from
11140 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
11142 o Major bugfixes (hidden services):
11143 - Clients now require hidden services to include the TAP keys for
11144 their intro points in the hidden service descriptor. This prevents
11145 an inadvertent upgrade to ntor, which a malicious hidden service
11146 could use to distinguish clients by consensus version. Fixes bug
11147 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
11149 o Minor features (security, TLS):
11150 - Servers no longer support clients that without AES ciphersuites.
11151 (3DES is no longer considered an acceptable cipher.) We believe
11152 that no such Tor clients currently exist, since Tor has required
11153 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
11155 o Minor feature (fallback directories):
11156 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11157 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11158 2016. Closes ticket 20190; patch by teor.
11160 o Minor features (geoip, also in 0.2.8.8):
11161 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11164 o Minor feature (port flags):
11165 - Add new flags to the *Port options to finer control over which
11166 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
11167 and the synthetic flag OnionTrafficOnly, which is equivalent to
11168 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
11169 18693; patch by "teor".
11171 o Minor features (directory authority):
11172 - After voting, if the authorities decide that a relay is not
11173 "Valid", they no longer include it in the consensus at all. Closes
11174 ticket 20002; implements part of proposal 272.
11176 o Minor features (testing):
11177 - Disable memory protections on OpenBSD when performing our unit
11178 tests for memwipe(). The test deliberately invokes undefined
11179 behavior, and the OpenBSD protections interfere with this. Patch
11180 from "rubiate". Closes ticket 20066.
11182 o Minor features (testing, ipv6):
11183 - Add the single-onion and single-onion-ipv6 chutney targets to
11184 "make test-network-all". This requires a recent chutney version
11185 with the single onion network flavours (git c72a652 or later).
11186 Closes ticket 20072; patch by teor.
11187 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
11188 tests. Remove bridges+hs, as it's somewhat redundant. This
11189 requires a recent chutney version that supports IPv6 clients,
11190 relays, and authorities. Closes ticket 20069; patch by teor.
11192 o Minor features (Tor2web):
11193 - Make Tor2web clients respect ReachableAddresses. This feature was
11194 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
11195 0.2.8.7. Implements feature 20034. Patch by teor.
11197 o Minor features (unit tests):
11198 - We've done significant work to make the unit tests run faster.
11199 - Our link-handshake unit tests now check that when invalid
11200 handshakes fail, they fail with the error messages we expected.
11201 - Our unit testing code that captures log messages no longer
11202 prevents them from being written out if the user asked for them
11203 (by passing --debug or --info or or --notice --warn to the "test"
11204 binary). This change prevents us from missing unexpected log
11205 messages simply because we were looking for others. Related to
11207 - The unit tests now log all warning messages with the "BUG" flag.
11208 Previously, they only logged errors by default. This change will
11209 help us make our testing code more correct, and make sure that we
11210 only hit this code when we mean to. In the meantime, however,
11211 there will be more warnings in the unit test logs than before.
11212 This is preparatory work for ticket 19999.
11213 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
11214 assertion as a test failure.
11216 o Minor bug fixes (circuits):
11217 - Use the CircuitBuildTimeout option whenever
11218 LearnCircuitBuildTimeout is disabled. Previously, we would respect
11219 the option when a user disabled it, but not when it was disabled
11220 because some other option was set. Fixes bug 20073; bugfix on
11221 0.2.4.12-alpha. Patch by teor.
11223 o Minor bugfixes (allocation):
11224 - Change how we allocate memory for large chunks on buffers, to
11225 avoid a (currently impossible) integer overflow, and to waste less
11226 space when allocating unusually large chunks. Fixes bug 20081;
11227 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
11228 - Always include orconfig.h before including any other C headers.
11229 Sometimes, it includes macros that affect the behavior of the
11230 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
11231 first version to use AC_USE_SYSTEM_EXTENSIONS).
11232 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
11233 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
11234 Patch from Gisle Vanem.
11235 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
11236 They apparently require a set of annotations that we aren't
11237 currently using, and they create false positives in our pthreads
11238 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
11240 o Minor bugfixes (directory authority):
11241 - Die with a more useful error when the operator forgets to place
11242 the authority_signing_key file into the keys directory. This
11243 avoids an uninformative assert & traceback about having an invalid
11244 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
11245 - When allowing private addresses, mark Exits that only exit to
11246 private locations as such. Fixes bug 20064; bugfix
11249 o Minor bugfixes (documentation):
11250 - Document the default PathsNeededToBuildCircuits value that's used
11251 by clients when the directory authorities don't set
11252 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
11253 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
11254 - Fix manual for the User option: it takes a username, not a UID.
11255 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
11258 o Minor bugfixes (hidden services):
11259 - Stop logging intro point details to the client log on certain
11260 error conditions. Fixed as part of bug 20012; bugfix on
11261 0.2.4.8-alpha. Patch by teor.
11263 o Minor bugfixes (IPv6, testing):
11264 - Check for IPv6 correctly on Linux when running test networks.
11265 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
11267 o Minor bugfixes (Linux seccomp2 sandbox):
11268 - Add permission to run the sched_yield() and sigaltstack() system
11269 calls, in order to support versions of Tor compiled with asan or
11270 ubsan code that use these calls. Now "sandbox 1" and
11271 "--enable-expensive-hardening" should be compatible on more
11272 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
11274 o Minor bugfixes (logging):
11275 - When logging a message from the BUG() macro, be explicit about
11276 what we were asserting. Previously we were confusing what we were
11277 asserting with what the bug was. Fixes bug 20093; bugfix
11279 - When we are unable to remove the bw_accounting file, do not warn
11280 if the reason we couldn't remove it was that it didn't exist.
11281 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
11283 o Minor bugfixes (option parsing):
11284 - Count unix sockets when counting client listeners (SOCKS, Trans,
11285 NATD, and DNS). This has no user-visible behaviour changes: these
11286 options are set once, and never read. Required for correct
11287 behaviour in ticket 17178. Fixes bug 19677; bugfix on
11288 0.2.6.3-alpha. Patch by teor.
11290 o Minor bugfixes (options):
11291 - Check the consistency of UseEntryGuards and EntryNodes more
11292 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
11294 - Stop changing the configured value of UseEntryGuards on
11295 authorities and Tor2web clients. Fixes bug 20074; bugfix on
11296 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
11299 o Minor bugfixes (Tor2web):
11300 - Prevent Tor2web clients running hidden services, these services
11301 are not anonymous due to the one-hop client paths. Fixes bug
11302 19678. Patch by teor.
11304 o Minor bugfixes (unit tests):
11305 - Fix a shared-random unit test that was failing on big endian
11306 architectures due to internal representation of a integer copied
11307 to a buffer. The test is changed to take a full 32 bytes of data
11308 and use the output of a python script that make the COMMIT and
11309 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
11311 - The tor_tls_server_info_callback unit test no longer crashes when
11312 debug-level logging is turned on. Fixes bug 20041; bugfix
11316 Changes in version 0.2.8.8 - 2016-09-23
11317 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
11318 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
11319 who select public relays as their bridges.
11321 o Major bugfixes (crash):
11322 - Fix a complicated crash bug that could affect Tor clients
11323 configured to use bridges when replacing a networkstatus consensus
11324 in which one of their bridges was mentioned. OpenBSD users saw
11325 more crashes here, but all platforms were potentially affected.
11326 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11328 o Major bugfixes (relay, OOM handler):
11329 - Fix a timing-dependent assertion failure that could occur when we
11330 tried to flush from a circuit after having freed its cells because
11331 of an out-of-memory condition. Fixes bug 20203; bugfix on
11332 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11335 o Minor feature (fallback directories):
11336 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11337 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11338 2016. Closes ticket 20190; patch by teor.
11340 o Minor features (geoip):
11341 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11345 Changes in version 0.2.9.2-alpha - 2016-08-24
11346 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
11347 several new features and bugfixes. It also includes an important
11348 authority update and an important bugfix from 0.2.8.7. Everyone who
11349 sets the ReachableAddresses option, and all bridges, are strongly
11350 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
11352 o Directory authority changes (also in 0.2.8.7):
11353 - The "Tonga" bridge authority has been retired; the new bridge
11354 authority is "Bifroest". Closes tickets 19728 and 19690.
11356 o Major bugfixes (client, security, also in 0.2.8.7):
11357 - Only use the ReachableAddresses option to restrict the first hop
11358 in a path. In earlier versions of 0.2.8.x, it would apply to
11359 every hop in the path, with a possible degradation in anonymity
11360 for anyone using an uncommon ReachableAddress setting. Fixes bug
11361 19973; bugfix on 0.2.8.2-alpha.
11363 o Major features (user interface):
11364 - Tor now supports the ability to declare options deprecated, so
11365 that we can recommend that people stop using them. Previously,
11366 this was done in an ad-hoc way. Closes ticket 19820.
11368 o Major bugfixes (directory downloads):
11369 - Avoid resetting download status for consensuses hourly, since we
11370 already have another, smarter retry mechanism. Fixes bug 8625;
11371 bugfix on 0.2.0.9-alpha.
11373 o Minor features (config):
11374 - Warn users when descriptor and port addresses are inconsistent.
11375 Mitigates bug 13953; patch by teor.
11377 o Minor features (geoip):
11378 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11381 o Minor features (user interface):
11382 - There is a new --list-deprecated-options command-line option to
11383 list all of the deprecated options. Implemented as part of
11386 o Minor bugfixes (code style):
11387 - Fix an integer signedness conversion issue in the case conversion
11388 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
11390 o Minor bugfixes (compilation):
11391 - Build correctly on versions of libevent2 without support for
11392 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
11394 - Fix a compilation warning on GCC versions before 4.6. Our
11395 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
11396 when it is also required as an argument to the compiler pragma.
11397 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
11399 o Minor bugfixes (compilation, also in 0.2.8.7):
11400 - Remove an inappropriate "inline" in tortls.c that was causing
11401 warnings on older versions of GCC. Fixes bug 19903; bugfix
11404 o Minor bugfixes (fallback directories, also in 0.2.8.7):
11405 - Avoid logging a NULL string pointer when loading fallback
11406 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11407 and 0.2.8.1-alpha. Report and patch by "rubiate".
11409 o Minor bugfixes (logging):
11410 - Log a more accurate message when we fail to dump a microdescriptor.
11411 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
11413 o Minor bugfixes (memory leak):
11414 - Fix a series of slow memory leaks related to parsing torrc files
11415 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
11417 o Deprecated features:
11418 - A number of DNS-cache-related sub-options for client ports are now
11419 deprecated for security reasons, and may be removed in a future
11420 version of Tor. (We believe that client-side DNS caching is a bad
11421 idea for anonymity, and you should not turn it on.) The options
11422 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11423 UseIPv4Cache, and UseIPv6Cache.
11424 - A number of options are deprecated for security reasons, and may
11425 be removed in a future version of Tor. The options are:
11426 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11427 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11428 CloseHSClientCircuitsImmediatelyOnTimeout,
11429 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11430 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11431 UseNTorHandshake, and WarnUnsafeSocks.
11432 - The *ListenAddress options are now deprecated as unnecessary: the
11433 corresponding *Port options should be used instead. These options
11434 may someday be removed. The affected options are:
11435 ControlListenAddress, DNSListenAddress, DirListenAddress,
11436 NATDListenAddress, ORListenAddress, SocksListenAddress,
11437 and TransListenAddress.
11440 - Correct the IPv6 syntax in our documentation for the
11441 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
11444 - We no longer include the (dead, deprecated) bufferevent code in
11445 Tor. Closes ticket 19450. Based on a patch from U+039b.
11448 Changes in version 0.2.8.7 - 2016-08-24
11449 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
11450 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
11451 who sets the ReachableAddresses option, and all bridges, are strongly
11452 encouraged to upgrade.
11454 o Directory authority changes:
11455 - The "Tonga" bridge authority has been retired; the new bridge
11456 authority is "Bifroest". Closes tickets 19728 and 19690.
11458 o Major bugfixes (client, security):
11459 - Only use the ReachableAddresses option to restrict the first hop
11460 in a path. In earlier versions of 0.2.8.x, it would apply to
11461 every hop in the path, with a possible degradation in anonymity
11462 for anyone using an uncommon ReachableAddress setting. Fixes bug
11463 19973; bugfix on 0.2.8.2-alpha.
11465 o Minor features (geoip):
11466 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11469 o Minor bugfixes (compilation):
11470 - Remove an inappropriate "inline" in tortls.c that was causing
11471 warnings on older versions of GCC. Fixes bug 19903; bugfix
11474 o Minor bugfixes (fallback directories):
11475 - Avoid logging a NULL string pointer when loading fallback
11476 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11477 and 0.2.8.1-alpha. Report and patch by "rubiate".
11480 Changes in version 0.2.9.1-alpha - 2016-08-08
11481 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
11482 series. It improves our support for hardened builds and compiler
11483 warnings, deploys some critical infrastructure for improvements to
11484 hidden services, includes a new timing backend that we hope to use for
11485 better support for traffic padding, makes it easier for programmers to
11486 log unexpected events, and contains other small improvements to
11487 security, correctness, and performance.
11489 Below are the changes since 0.2.8.6.
11491 o New system requirements:
11492 - Tor now requires Libevent version 2.0.10-stable or later. Older
11493 versions of Libevent have less efficient backends for several
11494 platforms, and lack the DNS code that we use for our server-side
11495 DNS support. This implements ticket 19554.
11496 - Tor now requires zlib version 1.2 or later, for security,
11497 efficiency, and (eventually) gzip support. (Back when we started,
11498 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11499 released in 2003. We recommend the latest version.)
11501 o Major features (build, hardening):
11502 - Tor now builds with -ftrapv by default on compilers that support
11503 it. This option detects signed integer overflow (which C forbids),
11504 and turns it into a hard-failure. We do not apply this option to
11505 code that needs to run in constant time to avoid side-channels;
11506 instead, we use -fwrapv in that code. Closes ticket 17983.
11507 - When --enable-expensive-hardening is selected, stop applying the
11508 clang/gcc sanitizers to code that needs to run in constant time.
11509 Although we are aware of no introduced side-channels, we are not
11510 able to prove that there are none. Related to ticket 17983.
11512 o Major features (compilation):
11513 - Our big list of extra GCC warnings is now enabled by default when
11514 building with GCC (or with anything like Clang that claims to be
11515 GCC-compatible). To make all warnings into fatal compilation
11516 errors, pass --enable-fatal-warnings to configure. Closes
11518 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11519 turn on C and POSIX extensions. (Previously, we attempted to do
11520 this on an ad hoc basis.) Closes ticket 19139.
11522 o Major features (directory authorities, hidden services):
11523 - Directory authorities can now perform the shared randomness
11524 protocol specified by proposal 250. Using this protocol, directory
11525 authorities generate a global fresh random value every day. In the
11526 future, this value will be used by hidden services to select
11527 HSDirs. This release implements the directory authority feature;
11528 the hidden service side will be implemented in the future as part
11529 of proposal 224. Resolves ticket 16943; implements proposal 250.
11531 o Major features (downloading, random exponential backoff):
11532 - When we fail to download an object from a directory service, wait
11533 for an (exponentially increasing) randomized amount of time before
11534 retrying, rather than a fixed interval as we did before. This
11535 prevents a group of Tor instances from becoming too synchronized,
11536 or a single Tor instance from becoming too predictable, in its
11537 download schedule. Closes ticket 15942.
11539 o Major bugfixes (exit policies):
11540 - Avoid disclosing exit outbound bind addresses, configured port
11541 bind addresses, and local interface addresses in relay descriptors
11542 by default under ExitPolicyRejectPrivate. Instead, only reject
11543 these (otherwise unlisted) addresses if
11544 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11545 0.2.7.2-alpha. Patch by teor.
11547 o Major bugfixes (hidden service client):
11548 - Allow Tor clients with appropriate controllers to work with
11549 FetchHidServDescriptors set to 0. Previously, this option also
11550 disabled descriptor cache lookup, thus breaking hidden services
11551 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11553 o Minor features (build, hardening):
11554 - Detect and work around a libclang_rt problem that would prevent
11555 clang from finding __mulodi4() on some 32-bit platforms, and thus
11556 keep -ftrapv from linking on those systems. Closes ticket 19079.
11557 - When building on a system without runtime support for the runtime
11558 hardening options, try to log a useful warning at configuration
11559 time, rather than an incomprehensible warning at link time. If
11560 expensive hardening was requested, this warning becomes an error.
11561 Closes ticket 18895.
11563 o Minor features (code safety):
11564 - In our integer-parsing functions, ensure that maxiumum value we
11565 give is no smaller than the minimum value. Closes ticket 19063;
11568 o Minor features (controller):
11569 - Implement new GETINFO queries for all downloads that use
11570 download_status_t to schedule retries. This allows controllers to
11571 examine the schedule for pending downloads. Closes ticket 19323.
11572 - Allow controllers to configure basic client authorization on
11573 hidden services when they create them with the ADD_ONION control
11574 command. Implements ticket 15588. Patch by "special".
11575 - Fire a STATUS_SERVER controller event whenever the hibernation
11576 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11578 o Minor features (directory authority):
11579 - Directory authorities now only give the Guard flag to a relay if
11580 they are also giving it the Stable flag. This change allows us to
11581 simplify path selection for clients. It should have minimal effect
11582 in practice, since >99% of Guards already have the Stable flag.
11583 Implements ticket 18624.
11584 - Directory authorities now write their v3-status-votes file out to
11585 disk earlier in the consensus process, so we have a record of the
11586 votes even if we abort the consensus process. Resolves
11589 o Minor features (hidden service):
11590 - Stop being so strict about the payload length of "rendezvous1"
11591 cells. We used to be locked in to the "TAP" handshake length, and
11592 now we can handle better handshakes like "ntor". Resolves
11595 o Minor features (infrastructure, time):
11596 - Tor now uses the operating system's monotonic timers (where
11597 available) for internal fine-grained timing. Previously we would
11598 look at the system clock, and then attempt to compensate for the
11599 clock running backwards. Closes ticket 18908.
11600 - Tor now includes an improved timer backend, so that we can
11601 efficiently support tens or hundreds of thousands of concurrent
11602 timers, as will be needed for some of our planned anti-traffic-
11603 analysis work. This code is based on William Ahern's "timeout.c"
11604 project, which implements a "tickless hierarchical timing wheel".
11605 Closes ticket 18365.
11607 o Minor features (logging):
11608 - Provide a more useful warning message when configured with an
11609 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11610 - When dumping unparseable router descriptors, optionally store them
11611 in separate files, named by digest, up to a configurable size
11612 limit. You can change the size limit by setting the
11613 MaxUnparseableDescSizeToLog option, and disable this feature by
11614 setting that option to 0. Closes ticket 18322.
11615 - Add a set of macros to check nonfatal assertions, for internal
11616 use. Migrating more of our checks to these should help us avoid
11617 needless crash bugs. Closes ticket 18613.
11619 o Minor features (performance):
11620 - Changer the "optimistic data" extension from "off by default" to
11621 "on by default". The default was ordinarily overridden by a
11622 consensus option, but when clients were bootstrapping for the
11623 first time, they would not have a consensus to get the option
11624 from. Changing this default When fetching a consensus for the
11625 first time, use optimistic data. This saves a round-trip during
11626 startup. Closes ticket 18815.
11628 o Minor features (relay, usability):
11629 - When the directory authorities refuse a bad relay's descriptor,
11630 encourage the relay operator to contact us. Many relay operators
11631 won't notice this line in their logs, but it's a win if even a few
11632 learn why we don't like what their relay was doing. Resolves
11635 o Minor features (testing):
11636 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11637 part of bug 18934; bugfix on 0.2.5.2-alpha.
11638 - Move the test-network.sh script to chutney, and modify tor's test-
11639 network.sh to call the (newer) chutney version when available.
11640 Resolves ticket 19116. Patch by teor.
11641 - Use the lcov convention for marking lines as unreachable, so that
11642 we don't count them when we're generating test coverage data.
11643 Update our coverage tools to understand this convention. Closes
11646 o Minor bugfixes (bootstrap):
11647 - Remember the directory we fetched the consensus or previous
11648 certificates from, and use it to fetch future authority
11649 certificates. This change improves bootstrapping performance.
11650 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11652 o Minor bugfixes (build):
11653 - The test-stem and test-network makefile targets now depend only on
11654 the tor binary that they are testing. Previously, they depended on
11655 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11656 patch from "cypherpunks".
11658 o Minor bugfixes (circuits):
11659 - Make sure extend_info_from_router() is only called on servers.
11660 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11662 o Minor bugfixes (compilation):
11663 - When building with Clang, use a full set of GCC warnings.
11664 (Previously, we included only a subset, because of the way we
11665 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11667 o Minor bugfixes (directory authority):
11668 - Authorities now sort the "package" lines in their votes, for ease
11669 of debugging. (They are already sorted in consensus documents.)
11670 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11671 - When parsing a detached signature, make sure we use the length of
11672 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11673 order to avoid comparing bytes out-of-bounds with a smaller digest
11674 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11676 o Minor bugfixes (documentation):
11677 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11678 19504; bugfix on 0.2.7.3-rc.
11679 - Fix the description of the --passphrase-fd option in the
11680 tor-gencert manpage. The option is used to pass the number of a
11681 file descriptor to read the passphrase from, not to read the file
11682 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11684 o Minor bugfixes (ephemeral hidden service):
11685 - When deleting an ephemeral hidden service, close its intro points
11686 even if they are not completely open. Fixes bug 18604; bugfix
11689 o Minor bugfixes (guard selection):
11690 - Use a single entry guard even if the NumEntryGuards consensus
11691 parameter is not provided. Fixes bug 17688; bugfix
11693 - Don't mark guards as unreachable if connection_connect() fails.
11694 That function fails for local reasons, so it shouldn't reveal
11695 anything about the status of the guard. Fixes bug 14334; bugfix
11698 o Minor bugfixes (hidden service client):
11699 - Increase the minimum number of internal circuits we preemptively
11700 build from 2 to 3, so a circuit is available when a client
11701 connects to another onion service. Fixes bug 13239; bugfix
11704 o Minor bugfixes (logging):
11705 - When logging a directory ownership mismatch, log the owning
11706 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11708 o Minor bugfixes (memory leaks):
11709 - Fix a small, uncommon memory leak that could occur when reading a
11710 truncated ed25519 key file. Fixes bug 18956; bugfix
11713 o Minor bugfixes (testing):
11714 - Allow clients to retry HSDirs much faster in test networks. Fixes
11715 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11716 - Disable ASAN's detection of segmentation faults while running
11717 test_bt.sh, so that we can make sure that our own backtrace
11718 generation code works. Fixes another aspect of bug 18934; bugfix
11719 on 0.2.5.2-alpha. Patch from "cypherpunks".
11720 - Fix the test-network-all target on out-of-tree builds by using the
11721 correct path to the test driver script. Fixes bug 19421; bugfix
11724 o Minor bugfixes (time):
11725 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11726 bugfix on all released tor versions.
11727 - When computing the difference between two times in milliseconds,
11728 we now round to the nearest millisecond correctly. Previously, we
11729 could sometimes round in the wrong direction. Fixes bug 19428;
11730 bugfix on 0.2.2.2-alpha.
11732 o Minor bugfixes (user interface):
11733 - Display a more accurate number of suppressed messages in the log
11734 rate-limiter. Previously, there was a potential integer overflow
11735 in the counter. Now, if the number of messages hits a maximum, the
11736 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11738 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11739 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11741 o Code simplification and refactoring:
11742 - Remove redundant declarations of the MIN macro. Closes
11744 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11745 Closes ticket 18462; patch from "icanhasaccount".
11746 - Split the 600-line directory_handle_command_get function into
11747 separate functions for different URL types. Closes ticket 16698.
11750 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
11751 ticket 19153. Patch from "U+039b".
11753 o Removed features:
11754 - Remove support for "GET /tor/bytes.txt" DirPort request, and
11755 "GETINFO dir-usage" controller request, which were only available
11756 via a compile-time option in Tor anyway. Feature was added in
11757 0.2.2.1-alpha. Resolves ticket 19035.
11758 - There is no longer a compile-time option to disable support for
11759 TransPort. (If you don't want TransPort; just don't use it.) Patch
11760 from "U+039b". Closes ticket 19449.
11763 - Run more workqueue tests as part of "make check". These had
11764 previously been implemented, but you needed to know special
11765 command-line options to enable them.
11766 - We now have unit tests for our code to reject zlib "compression
11767 bombs". (Fortunately, the code works fine.)
11770 Changes in version 0.2.8.6 - 2016-08-02
11772 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
11774 The Tor 0.2.8 series improves client bootstrapping performance,
11775 completes the authority-side implementation of improved identity
11776 keys for relays, and includes numerous bugfixes and performance
11777 improvements throughout the program. This release continues to
11778 improve the coverage of Tor's test suite. For a full list of
11779 changes since Tor 0.2.7, see the ReleaseNotes file.
11781 Changes since 0.2.8.5-rc:
11783 o Minor features (geoip):
11784 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
11787 o Minor bugfixes (compilation):
11788 - Fix a compilation warning in the unit tests on systems where char
11789 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
11791 o Minor bugfixes (fallback directories):
11792 - Remove 1 fallback that was on the hardcoded list, then opted-out,
11793 leaving 89 of the 100 fallbacks originally introduced in Tor
11794 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
11796 o Minor bugfixes (Linux seccomp2 sandbox):
11797 - Allow more syscalls when running with "Sandbox 1" enabled:
11798 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
11799 some systems, these are required for Tor to start. Fixes bug
11800 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
11801 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
11802 so that get_interface_address6_via_udp_socket_hack() can work.
11803 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
11806 Changes in version 0.2.8.5-rc - 2016-07-07
11807 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
11808 series. If we find no new bugs or regressions here, the first stable
11809 0.2.8 release will be identical to it. It has a few small bugfixes
11810 against previous versions.
11812 o Directory authority changes:
11813 - Urras is no longer a directory authority. Closes ticket 19271.
11815 o Major bugfixes (heartbeat):
11816 - Fix a regression that would crash Tor when the periodic
11817 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
11818 0.2.8.1-alpha. Reported by "kubaku".
11820 o Minor features (build):
11821 - Tor now again builds with the recent OpenSSL 1.1 development
11822 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
11823 - When building manual pages, set the timezone to "UTC", so that the
11824 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
11825 Patch from intrigeri.
11827 o Minor bugfixes (fallback directory selection):
11828 - Avoid errors during fallback selection if there are no eligible
11829 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
11832 o Minor bugfixes (IPv6, microdescriptors):
11833 - Don't check node addresses when we only have a routerstatus. This
11834 allows IPv6-only clients to bootstrap by fetching microdescriptors
11835 from fallback directory mirrors. (The microdescriptor consensus
11836 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
11839 o Minor bugfixes (logging):
11840 - Reduce pointlessly verbose log messages when directory servers
11841 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
11842 0.2.8.1-alpha. Patch by teor.
11843 - When a fallback directory changes its fingerprint from the hard-
11844 coded fingerprint, log a less severe, more explanatory log
11845 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
11847 o Minor bugfixes (Linux seccomp2 sandboxing):
11848 - Allow statistics to be written to disk when "Sandbox 1" is
11849 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
11850 0.2.6.1-alpha respectively.
11852 o Minor bugfixes (user interface):
11853 - Remove a warning message "Service [scrubbed] not found after
11854 descriptor upload". This message appears when one uses HSPOST
11855 control command to upload a service descriptor. Since there is
11856 only a descriptor and no service, showing this message is
11857 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
11859 o Fallback directory list:
11860 - Add a comment to the generated fallback directory list that
11861 explains how to comment out unsuitable fallbacks in a way that's
11862 compatible with the stem fallback parser.
11863 - Update fallback whitelist and blacklist based on relay operator
11864 emails. Blacklist unsuitable (non-working, over-volatile)
11865 fallbacks. Resolves ticket 19071. Patch by teor.
11866 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
11867 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
11868 ticket 19071; patch by teor.
11871 Changes in version 0.2.8.4-rc - 2016-06-15
11872 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
11873 If we find no new bugs or regressions here, the first stable 0.2.8
11874 release will be identical to it. It has a few small bugfixes against
11877 o Major bugfixes (user interface):
11878 - Correctly give a warning in the cases where a relay is specified
11879 by nickname, and one such relay is found, but it is not officially
11880 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
11882 o Minor features (build):
11883 - Tor now builds once again with the recent OpenSSL 1.1 development
11884 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
11886 o Minor features (geoip):
11887 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
11890 o Minor bugfixes (compilation):
11891 - Cause the unit tests to compile correctly on mingw64 versions that
11892 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
11894 o Minor bugfixes (downloading):
11895 - Predict more correctly whether we'll be downloading over HTTP when
11896 we determine the maximum length of a URL. This should avoid a
11897 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
11901 Changes in version 0.2.8.3-alpha - 2016-05-26
11902 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
11903 the course of the 0.2.8 development cycle. It improves the behavior of
11904 directory clients, fixes several crash bugs, fixes a gap in compiler
11905 hardening, and allows the full integration test suite to run on
11908 o Major bugfixes (security, client, DNS proxy):
11909 - Stop a crash that could occur when a client running with DNSPort
11910 received a query with multiple address types, and the first
11911 address type was not supported. Found and fixed by Scott Dial.
11912 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11914 o Major bugfixes (security, compilation):
11915 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
11916 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
11917 cause a compiler warning, thereby making other checks fail, and
11918 needlessly disabling compiler-hardening support. Fixes one case of
11919 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
11921 o Major bugfixes (security, directory authorities):
11922 - Fix a crash and out-of-bounds write during authority voting, when
11923 the list of relays includes duplicate ed25519 identity keys. Fixes
11924 bug 19032; bugfix on 0.2.8.2-alpha.
11926 o Major bugfixes (client, bootstrapping):
11927 - Check if bootstrap consensus downloads are still needed when the
11928 linked connection attaches. This prevents tor making unnecessary
11929 begindir-style connections, which are the only directory
11930 connections tor clients make since the fix for 18483 was merged.
11931 - Fix some edge cases where consensus download connections may not
11932 have been closed, even though they were not needed. Related to fix
11934 - Make relays retry consensus downloads the correct number of times,
11935 rather than the more aggressive client retry count. Fixes part of
11937 - Stop downloading consensuses when we have a consensus, even if we
11938 don't have all the certificates for it yet. Fixes bug 18809;
11939 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
11941 o Major bugfixes (directory mirrors):
11942 - Decide whether to advertise begindir support in the the same way
11943 we decide whether to advertise our DirPort. Allowing these
11944 decisions to become out-of-sync led to surprising behavior like
11945 advertising begindir support when hibernation made us not
11946 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
11949 o Major bugfixes (IPv6 bridges, client):
11950 - Actually use IPv6 addresses when selecting directory addresses for
11951 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
11954 o Major bugfixes (key management):
11955 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11956 pointer to the previous (uninitialized) key value. The impact here
11957 should be limited to a difficult-to-trigger crash, if OpenSSL is
11958 running an engine that makes key generation failures possible, or
11959 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11960 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11963 o Major bugfixes (testing):
11964 - Fix a bug that would block 'make test-network-all' on systems where
11965 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
11966 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
11967 bugfix on 0.2.8.1-alpha.
11969 o Minor features (clients):
11970 - Make clients, onion services, and bridge relays always use an
11971 encrypted begindir connection for directory requests. Resolves
11972 ticket 18483. Patch by "teor".
11974 o Minor features (fallback directory mirrors):
11975 - Give each fallback the same weight for client selection; restrict
11976 fallbacks to one per operator; report fallback directory detail
11977 changes when rebuilding list; add new fallback directory mirrors
11978 to the whitelist; and many other minor simplifications and fixes.
11979 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
11980 0.2.8.1-alpha; patch by "teor".
11981 - Replace the 21 fallbacks generated in January 2016 and included in
11982 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
11983 2016. Closes task 17158; patch by "teor".
11985 o Minor features (geoip):
11986 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
11989 o Minor bugfixes (assert, portability):
11990 - Fix an assertion failure in memarea.c on systems where "long" is
11991 shorter than the size of a pointer. Fixes bug 18716; bugfix
11994 o Minor bugfixes (bootstrap):
11995 - Consistently use the consensus download schedule for authority
11996 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
11998 o Minor bugfixes (build):
11999 - Remove a pair of redundant AM_CONDITIONAL declarations from
12000 configure.ac. Fixes one final case of bug 17744; bugfix
12002 - Resolve warnings when building on systems that are concerned with
12003 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
12005 - When libscrypt.h is found, but no libscrypt library can be linked,
12006 treat libscrypt as absent. Fixes bug 19161; bugfix
12009 o Minor bugfixes (client):
12010 - Turn all TestingClientBootstrap* into non-testing torrc options.
12011 This changes simply renames them by removing "Testing" in front of
12012 them and they do not require TestingTorNetwork to be enabled
12013 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
12014 - Make directory node selection more reliable, mainly for IPv6-only
12015 clients and clients with few reachable addresses. Fixes bug 18929;
12016 bugfix on 0.2.8.1-alpha. Patch by "teor".
12018 o Minor bugfixes (controller, microdescriptors):
12019 - Make GETINFO dir/status-vote/current/consensus conform to the
12020 control specification by returning "551 Could not open cached
12021 consensus..." when not caching consensuses. Fixes bug 18920;
12022 bugfix on 0.2.2.6-alpha.
12024 o Minor bugfixes (crypto, portability):
12025 - The SHA3 and SHAKE routines now produce the correct output on Big
12026 Endian systems. No code calls either algorithm yet, so this is
12027 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
12028 - Tor now builds again with the recent OpenSSL 1.1 development
12029 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
12032 o Minor bugfixes (directories):
12033 - When fetching extrainfo documents, compare their SHA256 digests
12034 and Ed25519 signing key certificates with the routerinfo that led
12035 us to fetch them, rather than with the most recent routerinfo.
12036 Otherwise we generate many spurious warnings about mismatches.
12037 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
12039 o Minor bugfixes (logging):
12040 - When we can't generate a signing key because OfflineMasterKey is
12041 set, do not imply that we should have been able to load it. Fixes
12042 bug 18133; bugfix on 0.2.7.2-alpha.
12043 - Stop periodic_event_dispatch() from blasting twelve lines per
12044 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
12045 - When rejecting a misformed INTRODUCE2 cell, only log at
12046 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
12048 o Minor bugfixes (pluggable transports):
12049 - Avoid reporting a spurious error when we decide that we don't need
12050 to terminate a pluggable transport because it has already exited.
12051 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
12053 o Minor bugfixes (pointer arithmetic):
12054 - Fix a bug in memarea_alloc() that could have resulted in remote
12055 heap write access, if Tor had ever passed an unchecked size to
12056 memarea_alloc(). Fortunately, all the sizes we pass to
12057 memarea_alloc() are pre-checked to be less than 128 kilobytes.
12058 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
12061 o Minor bugfixes (relays):
12062 - Consider more config options when relays decide whether to
12063 regenerate their descriptor. Fixes more of bug 12538; bugfix
12065 - Resolve some edge cases where we might launch an ORPort
12066 reachability check even when DisableNetwork is set. Noticed while
12067 fixing bug 18616; bugfix on 0.2.3.9-alpha.
12069 o Minor bugfixes (statistics):
12070 - We now include consensus downloads via IPv6 in our directory-
12071 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
12073 o Minor bugfixes (testing):
12074 - Allow directories in small networks to bootstrap by skipping
12075 DirPort checks when the consensus has no exits. Fixes bug 19003;
12076 bugfix on 0.2.8.1-alpha. Patch by teor.
12077 - Fix a small memory leak that would occur when the
12078 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
12079 bugfix on 0.2.5.2-alpha.
12081 o Minor bugfixes (time handling):
12082 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
12083 field. Otherwise, our unit tests crash on Windows. Fixes bug
12084 18977; bugfix on 0.2.2.25-alpha.
12087 - Document the contents of the 'datadir/keys' subdirectory in the
12088 manual page. Closes ticket 17621.
12089 - Stop recommending use of nicknames to identify relays in our
12090 MapAddress documentation. Closes ticket 18312.
12093 Changes in version 0.2.8.2-alpha - 2016-03-28
12094 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
12095 bugs in earlier versions of Tor, including some that prevented
12096 authorities using Tor 0.2.7.x from running correctly. IPv6 and
12097 directory support should also be much improved.
12099 o New system requirements:
12100 - Tor no longer supports versions of OpenSSL with a broken
12101 implementation of counter mode. (This bug was present in OpenSSL
12102 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
12103 longer runs with, these versions.
12104 - Tor no longer attempts to support platforms where the "time_t"
12105 type is unsigned. (To the best of our knowledge, only OpenVMS does
12106 this, and Tor has never actually built on OpenVMS.) Closes
12108 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
12109 later (released in 2008 and 2009 respectively). If you are
12110 building Tor from the git repository instead of from the source
12111 distribution, and your tools are older than this, you will need to
12112 upgrade. Closes ticket 17732.
12114 o Major bugfixes (security, pointers):
12115 - Avoid a difficult-to-trigger heap corruption attack when extending
12116 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12117 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12118 Reported by Guido Vranken.
12120 o Major bugfixes (bridges, pluggable transports):
12121 - Modify the check for OR connections to private addresses. Allow
12122 bridges on private addresses, including pluggable transports that
12123 ignore the (potentially private) address in the bridge line. Fixes
12124 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
12126 o Major bugfixes (compilation):
12127 - Repair hardened builds under the clang compiler. Previously, our
12128 use of _FORTIFY_SOURCE would conflict with clang's address
12129 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12131 o Major bugfixes (crash on shutdown):
12132 - Correctly handle detaching circuits from muxes when shutting down.
12133 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
12134 - Fix an assert-on-exit bug related to counting memory usage in
12135 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
12137 o Major bugfixes (crash on startup):
12138 - Fix a segfault during startup: If a Unix domain socket was
12139 configured as listener (such as a ControlSocket or a SocksPort
12140 "unix:" socket), and tor was started as root but not configured to
12141 switch to another user, tor would segfault while trying to string
12142 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
12145 o Major bugfixes (dns proxy mode, crash):
12146 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12147 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12149 o Major bugfixes (relays, bridge clients):
12150 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
12151 bridge clients use the address configured in the bridge line.
12152 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
12155 o Major bugfixes (voting):
12156 - Actually enable support for authorities to match routers by their
12157 Ed25519 identities. Previously, the code had been written, but
12158 some debugging code that had accidentally been left in the
12159 codebase made it stay turned off. Fixes bug 17702; bugfix
12161 - When collating votes by Ed25519 identities, authorities now
12162 include a "NoEdConsensus" flag if the ed25519 value (or lack
12163 thereof) for a server does not reflect the majority consensus.
12164 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12165 - When generating a vote with keypinning disabled, never include two
12166 entries for the same ed25519 identity. This bug was causing
12167 authorities to generate votes that they could not parse when a
12168 router violated key pinning by changing its RSA identity but
12169 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12170 18318. Bugfix on 0.2.7.2-alpha.
12172 o Minor features (security, win32):
12173 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
12174 attack. Fixes bug 18123; bugfix on all tor versions. Patch
12177 o Minor features (bug-resistance):
12178 - Make Tor survive errors involving connections without a
12179 corresponding event object. Previously we'd fail with an
12180 assertion; now we produce a log message. Related to bug 16248.
12182 o Minor features (build):
12183 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12184 as having possible IPFW support. Closes ticket 18448. Patch from
12185 Steven Chamberlain.
12187 o Minor features (code hardening):
12188 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12189 level code, to harden against accidental failures to NUL-
12190 terminate. Part of ticket 17852. Patch from jsturgix. Found
12193 o Minor features (crypto):
12194 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12195 p is a safe prime, and g is a suitable generator. Closes
12198 o Minor features (geoip):
12199 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
12202 o Minor features (hidden service directory):
12203 - Streamline relay-side hsdir handling: when relays consider whether
12204 to accept an uploaded hidden service descriptor, they no longer
12205 check whether they are one of the relays in the network that is
12206 "supposed" to handle that descriptor. Implements ticket 18332.
12208 o Minor features (IPv6):
12209 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12210 to 1, tor prefers IPv6 directory addresses.
12211 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12212 avoids using IPv4 for client OR and directory connections.
12213 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12214 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12215 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12217 o Minor features (linux seccomp2 sandbox):
12218 - Reject attempts to change our Address with "Sandbox 1" enabled.
12219 Changing Address with Sandbox turned on would never actually work,
12220 but previously it would fail in strange and confusing ways. Found
12221 while fixing 18548.
12223 o Minor features (robustness):
12224 - Exit immediately with an error message if the code attempts to use
12225 Libevent without having initialized it. This should resolve some
12226 frequently-made mistakes in our unit tests. Closes ticket 18241.
12228 o Minor features (unix domain sockets):
12229 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
12230 Unix domain sockets without checking the permissions on the parent
12231 directory. (Tor checks permissions by default because some
12232 operating systems only check permissions on the parent directory.
12233 However, some operating systems do look at permissions on the
12234 socket, and tor's default check is unneeded.) Closes ticket 18458.
12237 o Minor bugfixes (exit policies, security):
12238 - Refresh an exit relay's exit policy when interface addresses
12239 change. Previously, tor only refreshed the exit policy when the
12240 configured external address changed. Fixes bug 18208; bugfix on
12241 0.2.7.3-rc. Patch by teor.
12243 o Minor bugfixes (security, hidden services):
12244 - Prevent hidden services connecting to client-supplied rendezvous
12245 addresses that are reserved as internal or multicast. Fixes bug
12246 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
12248 o Minor bugfixes (build):
12249 - Do not link the unit tests against both the testing and non-
12250 testing versions of the static libraries. Fixes bug 18490; bugfix
12252 - Avoid spurious failures from configure files related to calling
12253 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
12254 0.2.0.1-alpha. Patch from "cypherpunks".
12255 - Silence spurious clang-scan warnings in the ed25519_donna code by
12256 explicitly initializing some objects. Fixes bug 18384; bugfix on
12257 0.2.7.2-alpha. Patch by teor.
12259 o Minor bugfixes (client, bootstrap):
12260 - Count receipt of new microdescriptors as progress towards
12261 bootstrapping. Previously, with EntryNodes set, Tor might not
12262 successfully repopulate the guard set on bootstrapping. Fixes bug
12263 16825; bugfix on 0.2.3.1-alpha.
12265 o Minor bugfixes (code correctness):
12266 - Update to the latest version of Trunnel, which tries harder to
12267 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
12268 by clang address sanitizer. Fixes bug 18373; bugfix
12271 o Minor bugfixes (configuration):
12272 - Fix a tiny memory leak when parsing a port configuration ending in
12273 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
12275 o Minor bugfixes (containers):
12276 - If we somehow attempt to construct a heap with more than
12277 1073741822 elements, avoid an integer overflow when maintaining
12278 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
12280 o Minor bugfixes (correctness):
12281 - Fix a bad memory handling bug that would occur if we had queued a
12282 cell on a channel's incoming queue. Fortunately, we can't actually
12283 queue a cell like that as our code is constructed today, but it's
12284 best to avoid this kind of error, even if there isn't any code
12285 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
12287 o Minor bugfixes (directory):
12288 - When generating a URL for a directory server on an IPv6 address,
12289 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
12290 on 0.2.3.9-alpha. Patch from Malek.
12292 o Minor bugfixes (fallback directory mirrors):
12293 - When requesting extrainfo descriptors from a trusted directory
12294 server, check whether it is an authority or a fallback directory
12295 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
12296 0.2.4.7-alpha. Reported by atagar, patch by teor.
12298 o Minor bugfixes (hidden service, client):
12299 - Handle the case where the user makes several fast consecutive
12300 requests to the same .onion address. Previously, the first six
12301 requests would each trigger a descriptor fetch, each picking a
12302 directory (there are 6 overall) and the seventh one would fail
12303 because no directories were left, thereby triggering a close on
12304 all current directory connections asking for the hidden service.
12305 The solution here is to not close the connections if we have
12306 pending directory fetches. Fixes bug 15937; bugfix
12309 o Minor bugfixes (hidden service, control port):
12310 - Add the onion address to the HS_DESC event for the UPLOADED action
12311 both on success or failure. It was previously hardcoded with
12312 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
12314 o Minor bugfixes (hidden service, directory):
12315 - Bridges now refuse "rendezvous2" (hidden service descriptor)
12316 publish attempts. Suggested by ticket 18332.
12318 o Minor bugfixes (linux seccomp2 sandbox):
12319 - Allow the setrlimit syscall, and the prlimit and prlimit64
12320 syscalls, which some libc implementations use under the hood.
12321 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
12322 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
12323 enabled and no DNS resolvers configured. This should help TAILS
12324 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
12325 - Fix the sandbox's interoperability with unix domain sockets under
12326 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
12328 o Minor bugfixes (logging):
12329 - When logging information about an unparsable networkstatus vote or
12330 consensus, do not say "vote" when we mean consensus. Fixes bug
12331 18368; bugfix on 0.2.0.8-alpha.
12332 - Scrub service name in "unrecognized service ID" log messages.
12333 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
12334 - Downgrade logs and backtraces about IP versions to info-level.
12335 Only log backtraces once each time tor runs. Assists in diagnosing
12336 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
12337 Christian, patch by teor.
12339 o Minor bugfixes (memory safety):
12340 - Avoid freeing an uninitialized pointer when opening a socket fails
12341 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
12342 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
12344 - Correctly duplicate addresses in get_interface_address6_list().
12345 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
12346 patch by "cypherpunks".
12347 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
12349 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
12350 18672; bugfix on 0.2.5.1-alpha.
12352 o Minor bugfixes (private directory):
12353 - Prevent a race condition when creating private directories. Fixes
12354 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
12355 Patch from jsturgix. Found with Flawfinder.
12357 o Minor bugfixes (test networks, IPv6):
12358 - Allow internal IPv6 addresses in descriptors in test networks.
12359 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
12362 o Minor bugfixes (testing):
12363 - We no longer disable assertions in the unit tests when coverage is
12364 enabled. Instead, we require you to say --disable-asserts-in-tests
12365 to the configure script if you need assertions disabled in the
12366 unit tests (for example, if you want to perform branch coverage).
12367 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
12369 o Minor bugfixes (time parsing):
12370 - Avoid overflow in tor_timegm when parsing dates in and after 2038
12371 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
12372 0.0.2pre14. Patch by teor.
12374 o Minor bugfixes (tor-gencert):
12375 - Correctly handle the case where an authority operator enters a
12376 passphrase but sends an EOF before sending a newline. Fixes bug
12377 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
12379 o Code simplification and refactoring:
12380 - Quote all the string interpolations in configure.ac -- even those
12381 which we are pretty sure can't contain spaces. Closes ticket
12382 17744. Patch from zerosion.
12383 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
12384 inplace, so there's no need to have a separate implementation for
12385 the non-inplace code. Closes ticket 18258. Patch from Malek.
12386 - Simplify return types for some crypto functions that can't
12387 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
12390 - Change build messages to refer to "Fedora" instead of "Fedora
12391 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
12392 Patches from "icanhasaccount" and "cypherpunks".
12394 o Removed features:
12395 - We no longer maintain an internal freelist in memarea.c.
12396 Allocators should be good enough to make this code unnecessary,
12397 and it's doubtful that it ever had any performance benefit.
12400 - Fix several warnings from clang's address sanitizer produced in
12402 - Treat backtrace test failures as expected on FreeBSD until we
12403 solve bug 17808. Closes ticket 18204.
12406 Changes in version 0.2.8.1-alpha - 2016-02-04
12407 Tor 0.2.8.1-alpha is the first alpha release in its series. It
12408 includes numerous small features and bugfixes against previous Tor
12409 versions, and numerous small infrastructure improvements. The most
12410 notable features are a set of improvements to the directory subsystem.
12412 o Major features (security, Linux):
12413 - When Tor starts as root on Linux and is told to switch user ID, it
12414 can now retain the capability to bind to low ports. By default,
12415 Tor will do this only when it's switching user ID and some low
12416 ports have been configured. You can change this behavior with the
12417 new option KeepBindCapabilities. Closes ticket 8195.
12419 o Major features (directory system):
12420 - When bootstrapping multiple consensus downloads at a time, use the
12421 first one that starts downloading, and close the rest. This
12422 reduces failures when authorities or fallback directories are slow
12423 or down. Together with the code for feature 15775, this feature
12424 should reduces failures due to fallback churn. Implements ticket
12425 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
12426 "mikeperry" and "teor".
12427 - Include a trial list of 21 default fallback directories, generated
12428 in January 2016, based on an opt-in survey of suitable relays.
12429 Doing this should make clients bootstrap more quickly and reliably,
12430 and reduce the load on the directory authorities. Closes ticket
12431 15775. Patch by "teor".
12432 Candidates identified using an OnionOO script by "weasel", "teor",
12433 "gsathya", and "karsten".
12434 - Previously only relays that explicitly opened a directory port
12435 (DirPort) accepted directory requests from clients. Now all
12436 relays, with and without a DirPort, accept and serve tunneled
12437 directory requests that they receive through their ORPort. You can
12438 disable this behavior using the new DirCache option. Closes
12441 o Major key updates:
12442 - Update the V3 identity key for the dannenberg directory authority:
12443 it was changed on 18 November 2015. Closes task 17906. Patch
12446 o Minor features (security, clock):
12447 - Warn when the system clock appears to move back in time (when the
12448 state file was last written in the future). Tor doesn't know that
12449 consensuses have expired if the clock is in the past. Patch by
12450 "teor". Implements ticket 17188.
12452 o Minor features (security, exit policies):
12453 - ExitPolicyRejectPrivate now rejects more private addresses by
12454 default. Specifically, it now rejects the relay's outbound bind
12455 addresses (if configured), and the relay's configured port
12456 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12457 0.2.0.11-alpha. Patch by "teor".
12459 o Minor features (security, memory erasure):
12460 - Set the unused entries in a smartlist to NULL. This helped catch
12461 a (harmless) bug, and shouldn't affect performance too much.
12462 Implements ticket 17026.
12463 - Use SecureMemoryWipe() function to securely clean memory on
12464 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12465 Implements feature 17986.
12466 - Use explicit_bzero or memset_s when present. Previously, we'd use
12467 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
12468 from <logan@hackers.mu> and <selven@hackers.mu>.
12469 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12470 zero size. Check size argument to memwipe() for underflow. Fixes
12471 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12474 o Minor features (security, RNG):
12475 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
12476 positively are not allowed to fail. Previously we depended on
12477 internal details of OpenSSL's behavior. Closes ticket 17686.
12478 - Never use the system entropy output directly for anything besides
12479 seeding the PRNG. When we want to generate important keys, instead
12480 of using system entropy directly, we now hash it with the PRNG
12481 stream. This may help resist certain attacks based on broken OS
12482 entropy implementations. Closes part of ticket 17694.
12483 - Use modern system calls (like getentropy() or getrandom()) to
12484 generate strong entropy on platforms that have them. Closes
12487 o Minor features (accounting):
12488 - Added two modes to the AccountingRule option: One for limiting
12489 only the number of bytes sent ("AccountingRule out"), and one for
12490 limiting only the number of bytes received ("AccountingRule in").
12491 Closes ticket 15989; patch from "unixninja92".
12493 o Minor features (build):
12494 - Since our build process now uses "make distcheck", we no longer
12495 force "make dist" to depend on "make check". Closes ticket 17893;
12496 patch from "cypherpunks."
12497 - Tor now builds successfully with the recent OpenSSL 1.1
12498 development branch, and with the latest LibreSSL. Closes tickets
12499 17549, 17921, and 17984.
12501 o Minor features (controller):
12502 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12503 tickets 16774 and 17817. Patch by George Tankersley.
12504 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12505 service descriptor from a service's local hidden service
12506 descriptor cache. Closes ticket 14846.
12507 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12508 controllers can examine the the reject rules added by
12509 ExitPolicyRejectPrivate. This makes it easier for stem to display
12512 o Minor features (crypto):
12513 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12515 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12516 - When allocating a digest state object, allocate no more space than
12517 we actually need. Previously, we would allocate as much space as
12518 the state for the largest algorithm would need. This change saves
12519 up to 672 bytes per circuit. Closes ticket 17796.
12520 - Improve performance when hashing non-multiple of 8 sized buffers,
12521 based on Andrew Moon's public domain SipHash-2-4 implementation.
12522 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12524 o Minor features (directory downloads):
12525 - Wait for busy authorities and fallback directories to become non-
12526 busy when bootstrapping. (A similar change was made in 6c443e987d
12527 for directory caches chosen from the consensus.) Closes ticket
12528 17864; patch by "teor".
12529 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12530 directory mirrors. The default is 1; set it to 0 to disable
12531 fallbacks. Implements ticket 17576. Patch by "teor".
12533 o Minor features (geoip):
12534 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
12537 o Minor features (IPv6):
12538 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12539 FallbackDir torrc options, to specify an IPv6 address for an
12540 authority or fallback directory. Add hard-coded ipv6 addresses for
12541 directory authorities that have them. Closes ticket 17327; patch
12542 from Nick Mathewson and "teor".
12543 - Add address policy assume_action support for IPv6 addresses.
12544 - Limit IPv6 mask bits to 128.
12545 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12546 almost always a bug. Closes ticket 17863; patch by "teor".
12547 - Allow users to configure directory authorities and fallback
12548 directory servers with IPv6 addresses and ORPorts. Resolves
12550 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12551 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12552 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12553 17638; bugfix on 0.0.2pre8. Patch by "teor".
12555 o Minor features (logging):
12556 - When logging to syslog, allow a tag to be added to the syslog
12557 identity (the string prepended to every log message). The tag can
12558 be configured with SyslogIdentityTag and defaults to none. Setting
12559 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12562 o Minor features (portability):
12563 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12564 patch from <logan@hackers.mu>.
12566 o Minor features (relay, address discovery):
12567 - Add a family argument to get_interface_addresses_raw() and
12568 subfunctions to make network interface address interogation more
12569 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12570 types of interfaces from the operating system. Resolves
12572 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12573 fails to enumerate interface addresses using the platform-specific
12574 API, have it rely on the UDP socket fallback technique to try and
12575 find out what IP addresses (both IPv4 and IPv6) our machine has.
12576 Resolves ticket 17951.
12578 o Minor features (replay cache):
12579 - The replay cache now uses SHA256 instead of SHA1. Implements
12580 feature 8961. Patch by "teor", issue reported by "rransom".
12582 o Minor features (unix file permissions):
12583 - Defer creation of Unix sockets until after setuid. This avoids
12584 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12585 CapabilityBoundingSet, or chown and fowner when using SELinux.
12586 Implements part of ticket 17562. Patch from Jamie Nguyen.
12587 - If any directory created by Tor is marked as group readable, the
12588 filesystem group is allowed to be either the default GID or the
12589 root user. Allowing root to read the DataDirectory prevents the
12590 need for CAP_READ_SEARCH when using systemd's
12591 CapabilityBoundingSet, or dac_read_search when using SELinux.
12592 Implements part of ticket 17562. Patch from Jamie Nguyen.
12593 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12594 1, the DataDirectory will be made readable by the default GID.
12595 Implements part of ticket 17562. Patch from Jamie Nguyen.
12597 o Minor bugfixes (accounting):
12598 - The max bandwidth when using 'AccountRule sum' is now correctly
12599 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12600 from "unixninja92".
12602 o Minor bugfixes (code correctness):
12603 - When closing an entry connection, generate a warning if we should
12604 have sent an end cell for it but we haven't. Fixes bug 17876;
12605 bugfix on 0.2.3.2-alpha.
12606 - Assert that allocated memory held by the reputation code is freed
12607 according to its internal counters. Fixes bug 17753; bugfix
12609 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12612 o Minor bugfixes (compilation):
12613 - Mark all object files that include micro-revision.i as depending
12614 on it, so as to make parallel builds more reliable. Fixes bug
12615 17826; bugfix on 0.2.5.1-alpha.
12616 - Don't try to use the pthread_condattr_setclock() function unless
12617 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12618 17819; bugfix on 0.2.6.3-alpha.
12619 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12621 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12622 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12623 - Fix search for libevent libraries on OpenBSD (and other systems
12624 that install libevent 1 and libevent 2 in parallel). Fixes bug
12625 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12626 - Isolate environment variables meant for tests from the rest of the
12627 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12628 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12630 - Remove config.log only from make distclean, not from make clean.
12631 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12633 o Minor bugfixes (crypto):
12634 - Check the return value of HMAC() and assert on failure. Fixes bug
12635 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12637 o Minor bugfixes (fallback directories):
12638 - Mark fallbacks as "too busy" when they return a 503 response,
12639 rather than just marking authorities. Fixes bug 17572; bugfix on
12640 0.2.4.7-alpha. Patch by "teor".
12642 o Minor bugfixes (IPv6):
12643 - Update the limits in max_dl_per_request for IPv6 address length.
12644 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12646 o Minor bugfixes (linux seccomp2 sandbox):
12647 - Fix a crash when using offline master ed25519 keys with the Linux
12648 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12650 o Minor bugfixes (logging):
12651 - In log messages that include a function name, use __FUNCTION__
12652 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12653 with clang __PRETTY_FUNCTION__ has extra information we don't
12654 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12656 - Remove needless quotes from a log message about unparseable
12657 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12659 o Minor bugfixes (portability):
12660 - Remove an #endif from configure.ac so that we correctly detect the
12661 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12664 o Minor bugfixes (relays):
12665 - Check that both the ORPort and DirPort (if present) are reachable
12666 before publishing a relay descriptor. Otherwise, relays publish a
12667 descriptor with DirPort 0 when the DirPort reachability test takes
12668 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12669 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12671 o Minor bugfixes (relays, hidden services):
12672 - Refuse connection requests to private OR addresses unless
12673 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12674 then refuse to send any cells to a private address. Fixes bugs
12675 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12677 o Minor bugfixes (safe logging):
12678 - When logging a malformed hostname received through socks4, scrub
12679 it if SafeLogging says we should. Fixes bug 17419; bugfix
12682 o Minor bugfixes (statistics code):
12683 - Consistently check for overflow in round_*_to_next_multiple_of
12684 functions, and add unit tests with additional and maximal values.
12685 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12686 - Handle edge cases in the laplace functions: avoid division by
12687 zero, avoid taking the log of zero, and silence clang type
12688 conversion warnings using round and trunc. Add unit tests for edge
12689 cases with maximal values. Fixes part of bug 13192; bugfix
12692 o Minor bugfixes (testing):
12693 - The test for log_heartbeat was incorrectly failing in timezones
12694 with non-integer offsets. Instead of comparing the end of the time
12695 string against a constant, compare it to the output of
12696 format_local_iso_time when given the correct input. Fixes bug
12697 18039; bugfix on 0.2.5.4-alpha.
12698 - Make unit tests pass on IPv6-only systems, and systems without
12699 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12700 bugfix on 0.2.7.3-rc. Patch by "teor".
12701 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12703 - Check the full results of SHA256 and SHA512 digests in the unit
12704 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12706 o Code simplification and refactoring:
12707 - Move logging of redundant policy entries in
12708 policies_parse_exit_policy_internal into its own function. Closes
12709 ticket 17608; patch from "juce".
12710 - Extract the more complicated parts of circuit_mark_for_close()
12711 into a new function that we run periodically before circuits are
12712 freed. This change removes more than half of the functions
12713 currently in the "blob". Closes ticket 17218.
12714 - Clean up a little duplicated code in
12715 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12717 - Decouple the list of streams waiting to be attached to circuits
12718 from the overall connection list. This change makes it possible to
12719 attach streams quickly while simplifying Tor's callgraph and
12720 avoiding O(N) scans of the entire connection list. Closes
12722 - When a direct directory request fails immediately on launch,
12723 instead of relaunching that request from inside the code that
12724 launches it, instead mark the connection for teardown. This change
12725 simplifies Tor's callback and prevents the directory-request
12726 launching code from invoking itself recursively. Closes
12728 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12729 use them. Closes ticket 17926.
12732 - Add a description of the correct use of the '--keygen' command-
12733 line option. Closes ticket 17583; based on text by 's7r'.
12734 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12735 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12736 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12737 - Mention torspec URL in the manpage and point the reader to it
12738 whenever we mention a document that belongs in torspce. Fixes
12741 o Removed features:
12742 - Remove client-side support for connecting to Tor relays running
12743 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12744 the v3 TLS handshake protocol, and are no longer allowed on the
12745 Tor network. Implements the client side of ticket 11150. Based on
12746 patches by Tom van der Woerdt.
12749 - Add unit tests to check for common RNG failure modes, such as
12750 returning all zeroes, identical values, or incrementing values
12751 (OpenSSL's rand_predictable feature). Patch by "teor".
12752 - Log more information when the backtrace tests fail. Closes ticket
12753 17892. Patch from "cypherpunks."
12754 - Always test both ed25519 backends, so that we can be sure that our
12755 batch-open replacement code works. Part of ticket 16794.
12756 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
12757 portion of ticket 16831.
12758 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
12759 util_format.c, directory.c, and options_validate.c. Closes tickets
12760 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
12762 - Unit tests for directory_handle_command_get. Closes ticket 17004.
12763 Patch from Reinaldo de Souza Jr.
12766 Changes in version 0.2.7.6 - 2015-12-10
12767 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
12768 well as a minor bug in hidden service reliability.
12770 o Major bugfixes (guard selection):
12771 - Actually look at the Guard flag when selecting a new directory
12772 guard. When we implemented the directory guard design, we
12773 accidentally started treating all relays as if they have the Guard
12774 flag during guard selection, leading to weaker anonymity and worse
12775 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12778 o Minor features (geoip):
12779 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
12782 o Minor bugfixes (compilation):
12783 - When checking for net/pfvar.h, include netinet/in.h if possible.
12784 This fixes transparent proxy detection on OpenBSD. Fixes bug
12785 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
12786 - Fix a compilation warning with Clang 3.6: Do not check the
12787 presence of an address which can never be NULL. Fixes bug 17781.
12789 o Minor bugfixes (correctness):
12790 - When displaying an IPv6 exit policy, include the mask bits
12791 correctly even when the number is greater than 31. Fixes bug
12792 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
12793 - The wrong list was used when looking up expired intro points in a
12794 rend service object, causing what we think could be reachability
12795 issues for hidden services, and triggering a BUG log. Fixes bug
12796 16702; bugfix on 0.2.7.2-alpha.
12797 - Fix undefined behavior in the tor_cert_checksig function. Fixes
12798 bug 17722; bugfix on 0.2.7.2-alpha.
12801 Changes in version 0.2.7.5 - 2015-11-20
12802 The Tor 0.2.7 release series is dedicated to the memory of Tor user
12803 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
12804 tirelessly to advocate human rights regardless of national borders,
12805 and oppose the encroachments of mass surveillance. He opposed national
12806 exceptionalism, he brought clarity to legal and policy debates, he
12807 understood and predicted the impact of mass surveillance on the world,
12808 and he laid the groundwork for resisting it. While serving on the Tor
12809 Project's board of directors, he brought us his uncompromising focus
12810 on technical excellence in the service of humankind. Caspar was an
12811 inimitable force for good and a wonderful friend. He was kind,
12812 humorous, generous, gallant, and believed we should protect one
12813 another without exception. We honor him here for his ideals, his
12814 efforts, and his accomplishments. Please honor his memory with works
12815 that would make him proud.
12817 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
12819 The 0.2.7 series adds a more secure identity key type for relays,
12820 improves cryptography performance, resolves several longstanding
12821 hidden-service performance issues, improves controller support for
12822 hidden services, and includes small bugfixes and performance
12823 improvements throughout the program. This release series also includes
12824 more tests than before, and significant simplifications to which parts
12825 of Tor invoke which others.
12827 (This release contains no code changes since 0.2.7.4-rc.)
12830 Changes in version 0.2.7.4-rc - 2015-10-21
12831 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
12832 fixes some important memory leaks, and a scary-looking (but mostly
12833 harmless in practice) invalid-read bug. It also has a few small
12834 bugfixes, notably fixes for compilation and portability on different
12835 platforms. If no further significant bounds are found, the next
12836 release will the the official stable release.
12838 o Major bugfixes (security, correctness):
12839 - Fix an error that could cause us to read 4 bytes before the
12840 beginning of an openssl string. This bug could be used to cause
12841 Tor to crash on systems with unusual malloc implementations, or
12842 systems with unusual hardening installed. Fixes bug 17404; bugfix
12845 o Major bugfixes (correctness):
12846 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
12847 bug 17401; bugfix on 0.2.7.3-rc.
12849 o Major bugfixes (memory leaks):
12850 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
12851 17398; bugfix on 0.2.6.1-alpha.
12852 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
12853 17402; bugfix on 0.2.7.3-rc.
12854 - Fix a memory leak when reading an expired signing key from disk.
12855 Fixes bug 17403; bugfix on 0.2.7.2-rc.
12857 o Minor features (geoIP):
12858 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
12861 o Minor bugfixes (compilation):
12862 - Repair compilation with the most recent (unreleased, alpha)
12863 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
12864 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
12865 17251; bugfix on 0.2.7.2-alpha.
12866 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12867 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12869 o Minor bugfixes (portability):
12870 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
12871 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
12874 o Minor bugfixes (sandbox):
12875 - Add the "hidserv-stats" filename to our sandbox filter for the
12876 HiddenServiceStatistics option to work properly. Fixes bug 17354;
12877 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
12879 o Minor bugfixes (testing):
12880 - Add unit tests for get_interface_address* failure cases. Fixes bug
12881 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
12882 - Fix breakage when running 'make check' with BSD make. Fixes bug
12883 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
12884 - Make the get_ifaddrs_* unit tests more tolerant of different
12885 network configurations. (Don't assume every test box has an IPv4
12886 address, and don't assume every test box has a non-localhost
12887 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
12888 - Skip backtrace tests when backtrace support is not compiled in.
12889 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
12893 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
12894 - Note that HiddenServicePorts can take a unix domain socket. Closes
12898 Changes in version 0.2.7.3-rc - 2015-09-25
12899 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
12900 contains numerous usability fixes for Ed25519 keys, safeguards against
12901 several misconfiguration problems, significant simplifications to
12902 Tor's callgraph, and numerous bugfixes and small features.
12904 This is the most tested release of Tor to date. The unit tests cover
12905 39.40% of the code, and the integration tests (accessible with "make
12906 test-full-online", requiring stem and chutney and a network
12907 connection) raise the coverage to 64.49%.
12909 o Major features (security, hidden services):
12910 - Hidden services, if using the EntryNodes option, are required to
12911 use more than one EntryNode, in order to avoid a guard discovery
12912 attack. (This would only affect people who had configured hidden
12913 services and manually specified the EntryNodes option with a
12914 single entry-node. The impact was that it would be easy to
12915 remotely identify the guard node used by such a hidden service.
12916 See ticket for more information.) Fixes ticket 14917.
12918 o Major features (Ed25519 keys, keypinning):
12919 - The key-pinning option on directory authorities is now advisory-
12920 only by default. In a future version, or when the AuthDirPinKeys
12921 option is set, pins are enforced again. Disabling key-pinning
12922 seemed like a good idea so that we can survive the fallout of any
12923 usability problems associated with Ed25519 keys. Closes
12926 o Major features (Ed25519 performance):
12927 - Improve the speed of Ed25519 operations and Curve25519 keypair
12928 generation when built targeting 32 bit x86 platforms with SSE2
12929 available. Implements ticket 16535.
12930 - Improve the runtime speed of Ed25519 signature verification by
12931 using Ed25519-donna's batch verification support. Implements
12934 o Major features (performance testing):
12935 - The test-network.sh script now supports performance testing.
12936 Requires corresponding chutney performance testing changes. Patch
12937 by "teor". Closes ticket 14175.
12939 o Major features (relay, Ed25519):
12940 - Significant usability improvements for Ed25519 key management. Log
12941 messages are better, and the code can recover from far more
12942 failure conditions. Thanks to "s7r" for reporting and diagnosing
12944 - Add a new OfflineMasterKey option to tell Tor never to try loading
12945 or generating a secret Ed25519 identity key. You can use this in
12946 combination with tor --keygen to manage offline and/or encrypted
12947 Ed25519 keys. Implements ticket 16944.
12948 - Add a --newpass option to allow changing or removing the
12949 passphrase of an encrypted key with tor --keygen. Implements part
12951 - On receiving a HUP signal, check to see whether the Ed25519
12952 signing key has changed, and reload it if so. Closes ticket 16790.
12954 o Major bugfixes (relay, Ed25519):
12955 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
12956 0.2.7.2-alpha. Reported by "s7r".
12957 - Improve handling of expired signing keys with offline master keys.
12958 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
12960 o Minor features (client-side privacy):
12961 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
12962 lifespan when IsolateSOCKSAuth and streams with SOCKS
12963 authentication are attached to the circuit. This allows
12964 applications like TorBrowser to manage circuit lifetime on their
12965 own. Implements feature 15482.
12966 - When logging malformed hostnames from SOCKS5 requests, respect
12967 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
12969 o Minor features (compilation):
12970 - Give a warning as early as possible when trying to build with an
12971 unsupported OpenSSL version. Closes ticket 16901.
12972 - Fail during configure if we're trying to build against an OpenSSL
12973 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
12974 which started requiring ECC.
12976 o Minor features (geoip):
12977 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
12980 o Minor features (hidden services):
12981 - Relays need to have the Fast flag to get the HSDir flag. As this
12982 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
12983 drop. This change should make some attacks against the hidden
12984 service directory system harder. Fixes ticket 15963.
12985 - Turn on hidden service statistics collection by setting the torrc
12986 option HiddenServiceStatistics to "1" by default. (This keeps
12987 track only of the fraction of traffic used by hidden services, and
12988 the total number of hidden services in existence.) Closes
12990 - Client now uses an introduction point failure cache to know when
12991 to fetch or keep a descriptor in their cache. Previously, failures
12992 were recorded implicitly, but not explicitly remembered. Closes
12995 o Minor features (testing, authorities, documentation):
12996 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
12997 explicitly manage consensus flags in testing networks. Patch by
12998 "robgjansen", modified by "teor". Implements part of ticket 14882.
13000 o Minor bugfixes (security, exit policies):
13001 - ExitPolicyRejectPrivate now also rejects the relay's published
13002 IPv6 address (if any), and any publicly routable IPv4 or IPv6
13003 addresses on any local interfaces. ticket 17027. Patch by "teor".
13004 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
13006 o Minor bug fixes (torrc exit policies):
13007 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
13008 produce IPv6 wildcard addresses. Previously they would produce
13009 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
13010 of bug 16069; bugfix on 0.2.4.7-alpha.
13011 - When parsing torrc ExitPolicies, we now warn for a number of cases
13012 where the user's intent is likely to differ from Tor's actual
13013 behavior. These include: using an IPv4 address with an accept6 or
13014 reject6 line; using "private" on an accept6 or reject6 line; and
13015 including any ExitPolicy lines after accept *:* or reject *:*.
13016 Related to ticket 16069.
13017 - When parsing torrc ExitPolicies, we now issue an info-level
13018 message when expanding an "accept/reject *" line to include both
13019 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
13020 - In each instance above, usage advice is provided to avoid the
13021 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
13022 16069; bugfix on 0.2.4.7-alpha.
13024 o Minor bugfixes (authority):
13025 - Don't assign "HSDir" to a router if it isn't Valid and Running.
13026 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
13027 - Downgrade log messages about Ed25519 key issues if they are in old
13028 cached router descriptors. Fixes part of bug 16286; bugfix
13030 - When we find an Ed25519 key issue in a cached descriptor, stop
13031 saying the descriptor was just "uploaded". Fixes another part of
13032 bug 16286; bugfix on 0.2.7.2-alpha.
13034 o Minor bugfixes (control port):
13035 - Repair a warning and a spurious result when getting the maximum
13036 number of file descriptors from the controller. Fixes bug 16697;
13037 bugfix on 0.2.7.2-alpha.
13039 o Minor bugfixes (correctness):
13040 - When calling channel_free_list(), avoid calling smartlist_remove()
13041 while inside a FOREACH loop. This partially reverts commit
13042 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
13043 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
13045 o Minor bugfixes (documentation):
13046 - Advise users on how to configure separate IPv4 and IPv6 exit
13047 policies in the manpage and sample torrcs. Related to ticket 16069.
13048 - Fix the usage message of tor-resolve(1) so that it no longer lists
13049 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
13050 - Fix an error in the manual page and comments for
13051 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
13052 required "ORPort connectivity". While this is true, it is in no
13053 way unique to the HSDir flag. Of all the flags, only HSDirs need a
13054 DirPort configured in order for the authorities to assign that
13055 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
13058 o Minor bugfixes (Ed25519):
13059 - Fix a memory leak when reading router descriptors with expired
13060 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
13062 o Minor bugfixes (linux seccomp2 sandbox):
13063 - Allow bridge authorities to run correctly under the seccomp2
13064 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
13065 - Allow routers with ed25519 keys to run correctly under the
13066 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
13068 o Minor bugfixes (open file limit):
13069 - Fix set_max_file_descriptors() to set by default the max open file
13070 limit to the current limit when setrlimit() fails. Fixes bug
13071 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
13073 o Minor bugfixes (portability):
13074 - Try harder to normalize the exit status of the Tor process to the
13075 standard-provided range. Fixes bug 16975; bugfix on every version
13077 - Check correctly for Windows socket errors in the workqueue
13078 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
13079 - Fix the behavior of crypto_rand_time_range() when told to consider
13080 times before 1970. (These times were possible when running in a
13081 simulated network environment where time()'s output starts at
13082 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
13083 - Restore correct operation of TLS client-cipher detection on
13084 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
13086 o Minor bugfixes (relay):
13087 - Ensure that worker threads actually exit when a fatal error or
13088 shutdown is indicated. This fix doesn't currently affect the
13089 behavior of Tor, because Tor workers never indicates fatal error
13090 or shutdown except in the unit tests. Fixes bug 16868; bugfix
13092 - Unblock threads before releasing the work queue mutex to ensure
13093 predictable scheduling behavior. Fixes bug 16644; bugfix
13096 o Code simplification and refactoring:
13097 - Change the function that's called when we need to retry all
13098 downloads so that it only reschedules the downloads to happen
13099 immediately, rather than launching them all at once itself. This
13100 further simplifies Tor's callgraph.
13101 - Move some format-parsing functions out of crypto.c and
13102 crypto_curve25519.c into crypto_format.c and/or util_format.c.
13103 - Move the client-only parts of init_keys() into a separate
13104 function. Closes ticket 16763.
13105 - Simplify the microdesc_free() implementation so that it no longer
13106 appears (to code analysis tools) to potentially invoke a huge
13107 suite of other microdesc functions.
13108 - Simply the control graph further by deferring the inner body of
13109 directory_all_unreachable() into a callback. Closes ticket 16762.
13110 - Treat the loss of an owning controller as equivalent to a SIGTERM
13111 signal. This removes a tiny amount of duplicated code, and
13112 simplifies our callgraph. Closes ticket 16788.
13113 - When generating an event to send to the controller, we no longer
13114 put the event over the network immediately. Instead, we queue
13115 these events, and use a Libevent callback to deliver them. This
13116 change simplifies Tor's callgraph by reducing the number of
13117 functions from which all other Tor functions are reachable. Closes
13119 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13120 that try to scan or compile every file on Unix won't decide that
13122 - Remove the unused "nulterminate" argument from buf_pullup().
13125 - Recommend a 40 GB example AccountingMax in torrc.sample rather
13126 than a 4 GB max. Closes ticket 16742.
13127 - Include the TUNING document in our source tarball. It is referred
13128 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13132 - The internal pure-C tor-fw-helper tool is now removed from the Tor
13133 distribution, in favor of the pure-Go clone available from
13134 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
13135 used by the C tor-fw-helper are not, in our opinion, very
13136 confidence- inspiring in their secure-programming techniques.
13137 Closes ticket 13338.
13138 - Remove the code that would try to aggressively flush controller
13139 connections while writing to them. This code was introduced in
13140 0.1.2.7-alpha, in order to keep output buffers from exceeding
13141 their limits. But there is no longer a maximum output buffer size,
13142 and flushing data in this way caused some undesirable recursions
13143 in our call graph. Closes ticket 16480.
13146 - Make "bridges+hs" the default test network. This tests almost all
13147 tor functionality during make test-network, while allowing tests
13148 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
13149 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
13150 (chutney). Patches by "teor".
13151 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
13152 by-side in the same parent directory. Closes ticket 16903. Patch
13154 - Use environment variables rather than autoconf substitutions to
13155 send variables from the build system to the test scripts. This
13156 change should be easier to maintain, and cause 'make distcheck' to
13157 work better than before. Fixes bug 17148.
13158 - Add a new set of callgraph analysis scripts that use clang to
13159 produce a list of which Tor functions are reachable from which
13160 other Tor functions. We're planning to use these to help simplify
13161 our code structure by identifying illogical dependencies.
13162 - Add new 'test-full' and 'test-full-online' targets to run all
13163 tests, including integration tests with stem and chutney.
13164 - Make the test-workqueue test work on Windows by initializing the
13165 network before we begin.
13166 - New make target (make test-network-all) to run multiple applicable
13167 chutney test cases. Patch from Teor; closes 16953.
13168 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
13169 functions in dns.c. Implements a portion of ticket 16831.
13170 - When building Tor with testing coverage enabled, run Chutney tests
13171 (if any) using the 'tor-cov' coverage binary.
13172 - When running test-network or test-stem, check for the absence of
13173 stem/chutney before doing any build operations.
13176 Changes in version 0.2.7.2-alpha - 2015-07-27
13177 This, the second alpha in the Tor 0.2.7 series, has a number of new
13178 features, including a way to manually pick the number of introduction
13179 points for hidden services, and the much stronger Ed25519 signing key
13180 algorithm for regular Tor relays (including support for encrypted
13181 offline identity keys in the new algorithm).
13183 Support for Ed25519 on relays is currently limited to signing router
13184 descriptors; later alphas in this series will extend Ed25519 key
13185 support to more parts of the Tor protocol.
13187 o Major features (Ed25519 identity keys, Proposal 220):
13188 - All relays now maintain a stronger identity key, using the Ed25519
13189 elliptic curve signature format. This master key is designed so
13190 that it can be kept offline. Relays also generate an online
13191 signing key, and a set of other Ed25519 keys and certificates.
13192 These are all automatically regenerated and rotated as needed.
13193 Implements part of ticket 12498.
13194 - Directory authorities now vote on Ed25519 identity keys along with
13195 RSA1024 keys. Implements part of ticket 12498.
13196 - Directory authorities track which Ed25519 identity keys have been
13197 used with which RSA1024 identity keys, and do not allow them to
13198 vary freely. Implements part of ticket 12498.
13199 - Microdescriptors now include Ed25519 identity keys. Implements
13200 part of ticket 12498.
13201 - Add support for offline encrypted Ed25519 master keys. To use this
13202 feature on your tor relay, run "tor --keygen" to make a new master
13203 key (or to make a new signing key if you already have a master
13204 key). Closes ticket 13642.
13206 o Major features (Hidden services):
13207 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13208 specify a fixed number of introduction points. Its maximum value
13209 is 10 and default is 3. Using this option can increase a hidden
13210 service's reliability under load, at the cost of making it more
13211 visible that the hidden service is facing extra load. Closes
13213 - Remove the adaptive algorithm for choosing the number of
13214 introduction points, which used to change the number of
13215 introduction points (poorly) depending on the number of
13216 connections the HS sees. Closes ticket 4862.
13218 o Major features (onion key cross-certification):
13219 - Relay descriptors now include signatures of their own identity
13220 keys, made using the TAP and ntor onion keys. These signatures
13221 allow relays to prove ownership of their own onion keys. Because
13222 of this change, microdescriptors will no longer need to include
13223 RSA identity keys. Implements proposal 228; closes ticket 12499.
13225 o Major features (performance):
13226 - Improve the runtime speed of Ed25519 operations by using the
13227 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13228 Implements ticket 16467.
13229 - Improve the runtime speed of the ntor handshake by using an
13230 optimized curve25519 basepoint scalarmult implementation from the
13231 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13232 ideas by Adam Langley. Implements ticket 9663.
13234 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13235 - Properly separate out each SOCKSPort when applying stream
13236 isolation. The error occurred because each port's session group
13237 was being overwritten by a default value when the listener
13238 connection was initialized. Fixes bug 16247; bugfix on
13239 0.2.6.3-alpha. Patch by "jojelino".
13241 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13242 - Stop refusing to store updated hidden service descriptors on a
13243 client. This reverts commit 9407040c59218 (which indeed fixed bug
13244 14219, but introduced a major hidden service reachability
13245 regression detailed in bug 16381). This is a temporary fix since
13246 we can live with the minor issue in bug 14219 (it just results in
13247 some load on the network) but the regression of 16381 is too much
13248 of a setback. First-round fix for bug 16381; bugfix
13251 o Major bugfixes (hidden services):
13252 - When cannibalizing a circuit for an introduction point, always
13253 extend to the chosen exit node (creating a 4 hop circuit).
13254 Previously Tor would use the current circuit exit node, which
13255 changed the original choice of introduction point, and could cause
13256 the hidden service to skip excluded introduction points or
13257 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13260 o Major bugfixes (open file limit):
13261 - The open file limit wasn't checked before calling
13262 tor_accept_socket_nonblocking(), which would make Tor exceed the
13263 limit. Now, before opening a new socket, Tor validates the open
13264 file limit just before, and if the max has been reached, return an
13265 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13267 o Major bugfixes (stability, also in 0.2.6.10):
13268 - Stop crashing with an assertion failure when parsing certain kinds
13269 of malformed or truncated microdescriptors. Fixes bug 16400;
13270 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13271 by "cypherpunks_backup".
13272 - Stop random client-side assertion failures that could occur when
13273 connecting to a busy hidden service, or connecting to a hidden
13274 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13277 o Minor features (directory authorities, security, also in 0.2.6.9):
13278 - The HSDir flag given by authorities now requires the Stable flag.
13279 For the current network, this results in going from 2887 to 2806
13280 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13281 attack by raising the effort for a relay to become Stable to
13282 require at the very least 7 days, while maintaining the 96 hours
13283 uptime requirement for HSDir. Implements ticket 8243.
13285 o Minor features (client):
13286 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13287 character '_' to appear, in order to cope with domains observed in
13288 the wild that are serving non-RFC compliant records. Resolves
13290 - Relax the validation done to hostnames in SOCKS5 requests, and
13291 allow a single trailing '.' to cope with clients that pass FQDNs
13292 using that syntax to explicitly indicate that the domain name is
13293 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13294 - Add GroupWritable and WorldWritable options to unix-socket based
13295 SocksPort and ControlPort options. These options apply to a single
13296 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13299 o Minor features (control protocol):
13300 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13301 the control protocol. Resolves ticket 15358.
13303 o Minor features (directory authorities):
13304 - Directory authorities no longer vote against the "Fast", "Stable",
13305 and "HSDir" flags just because they were going to vote against
13306 "Running": if the consensus turns out to be that the router was
13307 running, then the authority's vote should count. Patch from Peter
13308 Retzlaff; closes issue 8712.
13310 o Minor features (geoip, also in 0.2.6.10):
13311 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13312 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13314 o Minor features (hidden services):
13315 - Add the new options "HiddenServiceMaxStreams" and
13316 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13317 limit the maximum number of simultaneous streams per circuit, and
13318 optionally tear down the circuit when the limit is exceeded. Part
13321 o Minor features (portability):
13322 - Use C99 variadic macros when the compiler is not GCC. This avoids
13323 failing compilations on MSVC, and fixes a log-file-based race
13324 condition in our old workarounds. Original patch from Gisle Vanem.
13326 o Minor bugfixes (compilation, also in 0.2.6.9):
13327 - Build with --enable-systemd correctly when libsystemd is
13328 installed, but systemd is not. Fixes bug 16164; bugfix on
13329 0.2.6.3-alpha. Patch from Peter Palfrader.
13331 o Minor bugfixes (controller):
13332 - Add the descriptor ID in each HS_DESC control event. It was
13333 missing, but specified in control-spec.txt. Fixes bug 15881;
13334 bugfix on 0.2.5.2-alpha.
13336 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13337 - Check for failures from crypto_early_init, and refuse to continue.
13338 A previous typo meant that we could keep going with an
13339 uninitialized crypto library, and would have OpenSSL initialize
13340 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13341 when implementing ticket 4900. Patch by "teor".
13343 o Minor bugfixes (hidden services):
13344 - Fix a crash when reloading configuration while at least one
13345 configured and one ephemeral hidden service exists. Fixes bug
13346 16060; bugfix on 0.2.7.1-alpha.
13347 - Avoid crashing with a double-free bug when we create an ephemeral
13348 hidden service but adding it fails for some reason. Fixes bug
13349 16228; bugfix on 0.2.7.1-alpha.
13351 o Minor bugfixes (Linux seccomp2 sandbox):
13352 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13353 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13355 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13356 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13357 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13358 on 0.2.6.3-alpha. Patch from "teor".
13360 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13361 - Fix sandboxing to work when running as a relay, by allowing the
13362 renaming of secret_id_key, and allowing the eventfd2 and futex
13363 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13365 - Allow systemd connections to work with the Linux seccomp2 sandbox
13366 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13369 o Minor bugfixes (relay):
13370 - Fix a rarely-encountered memory leak when failing to initialize
13371 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13372 from "cypherpunks".
13374 o Minor bugfixes (systemd):
13375 - Fix an accidental formatting error that broke the systemd
13376 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
13377 - Tor's systemd unit file no longer contains extraneous spaces.
13378 These spaces would sometimes confuse tools like deb-systemd-
13379 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13381 o Minor bugfixes (tests):
13382 - Use the configured Python executable when running test-stem-full.
13383 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
13385 o Minor bugfixes (tests, also in 0.2.6.9):
13386 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13387 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13389 o Minor bugfixes (threads, comments):
13390 - Always initialize return value in compute_desc_id in rendcommon.c
13391 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13392 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
13393 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13394 - Remove undefined directive-in-macro in test_util_writepid clang
13395 3.7 complains that using a preprocessor directive inside a macro
13396 invocation in test_util_writepid in test_util.c is undefined.
13397 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13399 o Code simplification and refactoring:
13400 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13401 to ensure they remain consistent and visible everywhere.
13402 - Remove some vestigial workarounds for the MSVC6 compiler. We
13403 haven't supported that in ages.
13404 - The link authentication code has been refactored for better
13405 testability and reliability. It now uses code generated with the
13406 "trunnel" binary encoding generator, to reduce the risk of bugs
13407 due to programmer error. Done as part of ticket 12498.
13410 - Include a specific and (hopefully) accurate documentation of the
13411 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13412 of interest to people writing programs to parse or generate torrc
13413 files. This document is not a commitment to long-term
13414 compatibility; some aspects of the current format are a bit
13415 ridiculous. Closes ticket 2325.
13417 o Removed features:
13418 - Tor no longer supports copies of OpenSSL that are missing support
13419 for Elliptic Curve Cryptography. (We began using ECC when
13420 available in 0.2.4.8-alpha, for more safe and efficient key
13421 negotiation.) In particular, support for at least one of P256 or
13422 P224 is now required, with manual configuration needed if only
13423 P224 is available. Resolves ticket 16140.
13424 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13425 on an operating system that has not upgraded to OpenSSL 1.0 or
13426 later, and you compile Tor from source, you will need to install a
13427 more recent OpenSSL to link Tor against.) These versions of
13428 OpenSSL are still supported by the OpenSSL, but the numerous
13429 cryptographic improvements in later OpenSSL releases makes them a
13430 clear choice. Resolves ticket 16034.
13431 - Remove the HidServDirectoryV2 option. Now all relays offer to
13432 store hidden service descriptors. Related to 16543.
13433 - Remove the VoteOnHidServDirectoriesV2 option, since all
13434 authorities have long set it to 1. Closes ticket 16543.
13437 - Document use of coverity, clang static analyzer, and clang dynamic
13438 undefined behavior and address sanitizers in doc/HACKING. Include
13439 detailed usage instructions in the blacklist. Patch by "teor".
13440 Closes ticket 15817.
13441 - The link authentication protocol code now has extensive tests.
13442 - The relay descriptor signature testing code now has
13444 - The test_workqueue program now runs faster, and is enabled by
13445 default as a part of "make check".
13446 - Now that OpenSSL has its own scrypt implementation, add an unit
13447 test that checks for interoperability between libscrypt_scrypt()
13448 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
13449 and rely on EVP_PBE_scrypt() whenever possible. Resolves
13453 Changes in version 0.2.6.10 - 2015-07-12
13454 Tor version 0.2.6.10 fixes some significant stability and hidden
13455 service client bugs, bulletproofs the cryptography init process, and
13456 fixes a bug when using the sandbox code with some older versions of
13457 Linux. Everyone running an older version, especially an older version
13458 of 0.2.6, should upgrade.
13460 o Major bugfixes (hidden service clients, stability):
13461 - Stop refusing to store updated hidden service descriptors on a
13462 client. This reverts commit 9407040c59218 (which indeed fixed bug
13463 14219, but introduced a major hidden service reachability
13464 regression detailed in bug 16381). This is a temporary fix since
13465 we can live with the minor issue in bug 14219 (it just results in
13466 some load on the network) but the regression of 16381 is too much
13467 of a setback. First-round fix for bug 16381; bugfix
13470 o Major bugfixes (stability):
13471 - Stop crashing with an assertion failure when parsing certain kinds
13472 of malformed or truncated microdescriptors. Fixes bug 16400;
13473 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13474 by "cypherpunks_backup".
13475 - Stop random client-side assertion failures that could occur when
13476 connecting to a busy hidden service, or connecting to a hidden
13477 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13480 o Minor features (geoip):
13481 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13482 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13484 o Minor bugfixes (crypto error-handling):
13485 - Check for failures from crypto_early_init, and refuse to continue.
13486 A previous typo meant that we could keep going with an
13487 uninitialized crypto library, and would have OpenSSL initialize
13488 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13489 when implementing ticket 4900. Patch by "teor".
13491 o Minor bugfixes (Linux seccomp2 sandbox):
13492 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13493 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13494 on 0.2.6.3-alpha. Patch from "teor".
13497 Changes in version 0.2.6.9 - 2015-06-11
13498 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
13499 requirements for receiving an HSDir flag, and addresses some other small
13500 bugs in the systemd and sandbox code. Clients using circuit isolation
13501 should upgrade; all directory authorities should upgrade.
13503 o Major bugfixes (client-side privacy):
13504 - Properly separate out each SOCKSPort when applying stream
13505 isolation. The error occurred because each port's session group was
13506 being overwritten by a default value when the listener connection
13507 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
13510 o Minor feature (directory authorities, security):
13511 - The HSDir flag given by authorities now requires the Stable flag.
13512 For the current network, this results in going from 2887 to 2806
13513 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13514 attack by raising the effort for a relay to become Stable which
13515 takes at the very least 7 days to do so and by keeping the 96
13516 hours uptime requirement for HSDir. Implements ticket 8243.
13518 o Minor bugfixes (compilation):
13519 - Build with --enable-systemd correctly when libsystemd is
13520 installed, but systemd is not. Fixes bug 16164; bugfix on
13521 0.2.6.3-alpha. Patch from Peter Palfrader.
13523 o Minor bugfixes (Linux seccomp2 sandbox):
13524 - Fix sandboxing to work when running as a relaymby renaming of
13525 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
13526 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
13527 - Allow systemd connections to work with the Linux seccomp2 sandbox
13528 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13531 o Minor bugfixes (tests):
13532 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13533 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13536 Changes in version 0.2.6.8 - 2015-05-21
13537 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
13538 fixes an authority-side bug in assigning the HSDir flag. All directory
13539 authorities should upgrade.
13541 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13542 - Revert commit that made directory authorities assign the HSDir
13543 flag to relays without a DirPort; this was bad because such relays
13544 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13547 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13548 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13549 a client authorized hidden service. Fixes bug 15823; bugfix
13552 o Minor features (geoip):
13553 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13554 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13558 Changes in version 0.2.7.1-alpha - 2015-05-12
13559 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13560 includes numerous small features and bugfixes against previous Tor
13561 versions, and numerous small infrastructure improvements. The most
13562 notable features are several new ways for controllers to interact with
13563 the hidden services subsystem.
13565 o New system requirements:
13566 - Tor no longer includes workarounds to support Libevent versions
13567 before 1.3e. Libevent 2.0 or later is recommended. Closes
13570 o Major features (controller):
13571 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13572 and management of hidden services via the controller. Closes
13574 - New "GETINFO onions/current" and "GETINFO onions/detached"
13575 commands to get information about hidden services created via the
13576 controller. Part of ticket 6411.
13577 - New HSFETCH command to launch a request for a hidden service
13578 descriptor. Closes ticket 14847.
13579 - New HSPOST command to upload a hidden service descriptor. Closes
13580 ticket 3523. Patch by "DonnchaC".
13582 o Major bugfixes (hidden services):
13583 - Revert commit that made directory authorities assign the HSDir
13584 flag to relays without a DirPort; this was bad because such relays
13585 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13588 o Minor features (clock-jump tolerance):
13589 - Recover better when our clock jumps back many hours, like might
13590 happen for Tails or Whonix users who start with a very wrong
13591 hardware clock, use Tor to discover a more accurate time, and then
13592 fix their clock. Resolves part of ticket 8766.
13594 o Minor features (command-line interface):
13595 - Make --hash-password imply --hush to prevent unnecessary noise.
13596 Closes ticket 15542. Patch from "cypherpunks".
13597 - Print a warning whenever we find a relative file path being used
13598 as torrc option. Resolves issue 14018.
13600 o Minor features (controller):
13601 - Add DirAuthority lines for default directory authorities to the
13602 output of the "GETINFO config/defaults" command if not already
13603 present. Implements ticket 14840.
13604 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13605 retrieve items from the client's hidden service descriptor cache.
13606 Closes ticket 14845.
13607 - Implement a new controller command "GETINFO status/fresh-relay-
13608 descs" to fetch a descriptor/extrainfo pair that was generated on
13609 demand just for the controller's use. Implements ticket 14784.
13611 o Minor features (DoS-resistance):
13612 - Make it harder for attackers to overload hidden services with
13613 introductions, by blocking multiple introduction requests on the
13614 same circuit. Resolves ticket 15515.
13616 o Minor features (geoip):
13617 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13618 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13621 o Minor features (HS popularity countermeasure):
13622 - To avoid leaking HS popularity, don't cycle the introduction point
13623 when we've handled a fixed number of INTRODUCE2 cells but instead
13624 cycle it when a random number of introductions is reached, thus
13625 making it more difficult for an attacker to find out the amount of
13626 clients that have used the introduction point for a specific HS.
13627 Closes ticket 15745.
13629 o Minor features (logging):
13630 - Include the Tor version in all LD_BUG log messages, since people
13631 tend to cut and paste those into the bugtracker. Implements
13634 o Minor features (pluggable transports):
13635 - When launching managed pluggable transports on Linux systems,
13636 attempt to have the kernel deliver a SIGTERM on tor exit if the
13637 pluggable transport process is still running. Resolves
13639 - When launching managed pluggable transports, setup a valid open
13640 stdin in the child process that can be used to detect if tor has
13641 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13642 can be used by implementations to detect this new behavior.
13643 Resolves ticket 15435.
13645 o Minor features (testing):
13646 - Add a test to verify that the compiler does not eliminate our
13647 memwipe() implementation. Closes ticket 15377.
13648 - Add make rule `check-changes` to verify the format of changes
13649 files. Closes ticket 15180.
13650 - Add unit tests for control_event_is_interesting(). Add a compile-
13651 time check that the number of events doesn't exceed the capacity
13652 of control_event_t.event_mask. Closes ticket 15431, checks for
13653 bugs similar to 13085. Patch by "teor".
13654 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13655 - Integrate the ntor, backtrace, and zero-length keys tests into the
13656 automake test suite. Closes ticket 15344.
13657 - Remove assertions during builds to determine Tor's test coverage.
13658 We don't want to trigger these even in assertions, so including
13659 them artificially makes our branch coverage look worse than it is.
13660 This patch provides the new test-stem-full and coverage-html-full
13661 configure options. Implements ticket 15400.
13663 o Minor bugfixes (build):
13664 - Improve out-of-tree builds by making non-standard rules work and
13665 clean up additional files and directories. Fixes bug 15053; bugfix
13668 o Minor bugfixes (command-line interface):
13669 - When "--quiet" is provided along with "--validate-config", do not
13670 write anything to stdout on success. Fixes bug 14994; bugfix
13672 - When complaining about bad arguments to "--dump-config", use
13673 stderr, not stdout.
13675 o Minor bugfixes (configuration, unit tests):
13676 - Only add the default fallback directories when the DirAuthorities,
13677 AlternateDirAuthority, and FallbackDir directory config options
13678 are set to their defaults. The default fallback directory list is
13679 currently empty, this fix will only change tor's behavior when it
13680 has default fallback directories. Includes unit tests for
13681 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13682 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13684 o Minor bugfixes (correctness):
13685 - For correctness, avoid modifying a constant string in
13686 handle_control_postdescriptor. Fixes bug 15546; bugfix
13688 - Remove side-effects from tor_assert() calls. This was harmless,
13689 because we never disable assertions, but it is bad style and
13690 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13693 o Minor bugfixes (hidden service):
13694 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13695 a client authorized hidden service. Fixes bug 15823; bugfix
13697 - Remove an extraneous newline character from the end of hidden
13698 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13700 o Minor bugfixes (interface):
13701 - Print usage information for --dump-config when it is used without
13702 an argument. Also, fix the error message to use different wording
13703 and add newline at the end. Fixes bug 15541; bugfix
13706 o Minor bugfixes (logs):
13707 - When building Tor under Clang, do not include an extra set of
13708 parentheses in log messages that include function names. Fixes bug
13709 15269; bugfix on every released version of Tor when compiled with
13710 recent enough Clang.
13712 o Minor bugfixes (network):
13713 - When attempting to use fallback technique for network interface
13714 lookup, disregard loopback and multicast addresses since they are
13715 unsuitable for public communications.
13717 o Minor bugfixes (statistics):
13718 - Disregard the ConnDirectionStatistics torrc options when Tor is
13719 not a relay since in that mode of operation no sensible data is
13720 being collected and because Tor might run into measurement hiccups
13721 when running as a client for some time, then becoming a relay.
13722 Fixes bug 15604; bugfix on 0.2.2.35.
13724 o Minor bugfixes (test networks):
13725 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13726 determine if local/private addresses imply reachability. The
13727 previous fix used TestingTorNetwork, which implies
13728 ExtendAllowPrivateAddresses, but this excluded rare configurations
13729 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13730 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13731 issue discovered by CJ Ess.
13733 o Minor bugfixes (testing):
13734 - Check for matching value in server response in ntor_ref.py. Fixes
13735 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13737 - Set the severity correctly when testing
13738 get_interface_addresses_ifaddrs() and
13739 get_interface_addresses_win32(), so that the tests fail gracefully
13740 instead of triggering an assertion. Fixes bug 15759; bugfix on
13741 0.2.6.3-alpha. Reported by Nicolas Derive.
13743 o Code simplification and refactoring:
13744 - Move the hacky fallback code out of get_interface_address6() into
13745 separate function and get it covered with unit-tests. Resolves
13747 - Refactor hidden service client-side cache lookup to intelligently
13748 report its various failure cases, and disentangle failure cases
13749 involving a lack of introduction points. Closes ticket 14391.
13750 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13751 control over the output. Part of ticket 15652.
13754 - Improve the descriptions of statistics-related torrc options in
13755 the manpage to describe rationale and possible uses cases. Fixes
13757 - Improve the layout and formatting of ./configure --help messages.
13758 Closes ticket 15024. Patch from "cypherpunks".
13759 - Standardize on the term "server descriptor" in the manual page.
13760 Previously, we had used "router descriptor", "server descriptor",
13761 and "relay descriptor" interchangeably. Part of ticket 14987.
13764 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
13765 and always use the internal Base64 decoder. The internal decoder
13766 has been part of tor since 0.2.0.10-alpha, and no one should
13767 be using the OpenSSL one. Part of ticket 15652.
13768 - Remove the 'tor_strclear()' function; use memwipe() instead.
13769 Closes ticket 14922.
13771 o Removed features:
13772 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
13773 fingerprinting we now recommend pluggable transports; for forward-
13774 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
13775 - Remove the undocumented "--digests" command-line option. It
13776 complicated our build process, caused subtle build issues on
13777 multiple platforms, and is now redundant since we started
13778 including git version identifiers. Closes ticket 14742.
13779 - Tor no longer contains checks for ancient directory cache versions
13780 that didn't know about microdescriptors.
13781 - Tor no longer contains workarounds for stat files generated by
13782 super-old versions of Tor that didn't choose guards sensibly.
13785 Changes in version 0.2.4.27 - 2015-04-06
13786 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
13787 could be used by an attacker to crash hidden services, or crash clients
13788 visiting hidden services. Hidden services should upgrade as soon as
13789 possible; clients should upgrade whenever packages become available.
13791 This release also backports a simple improvement to make hidden
13792 services a bit less vulnerable to denial-of-service attacks.
13794 o Major bugfixes (security, hidden service):
13795 - Fix an issue that would allow a malicious client to trigger an
13796 assertion failure and halt a hidden service. Fixes bug 15600;
13797 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13798 - Fix a bug that could cause a client to crash with an assertion
13799 failure when parsing a malformed hidden service descriptor. Fixes
13800 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13802 o Minor features (DoS-resistance, hidden service):
13803 - Introduction points no longer allow multiple INTRODUCE1 cells to
13804 arrive on the same circuit. This should make it more expensive for
13805 attackers to overwhelm hidden services with introductions.
13806 Resolves ticket 15515.
13809 Changes in version 0.2.5.12 - 2015-04-06
13810 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
13811 could be used by an attacker to crash hidden services, or crash clients
13812 visiting hidden services. Hidden services should upgrade as soon as
13813 possible; clients should upgrade whenever packages become available.
13815 This release also backports a simple improvement to make hidden
13816 services a bit less vulnerable to denial-of-service attacks.
13818 o Major bugfixes (security, hidden service):
13819 - Fix an issue that would allow a malicious client to trigger an
13820 assertion failure and halt a hidden service. Fixes bug 15600;
13821 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13822 - Fix a bug that could cause a client to crash with an assertion
13823 failure when parsing a malformed hidden service descriptor. Fixes
13824 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13826 o Minor features (DoS-resistance, hidden service):
13827 - Introduction points no longer allow multiple INTRODUCE1 cells to
13828 arrive on the same circuit. This should make it more expensive for
13829 attackers to overwhelm hidden services with introductions.
13830 Resolves ticket 15515.
13833 Changes in version 0.2.6.7 - 2015-04-06
13834 Tor 0.2.6.7 fixes two security issues that could be used by an
13835 attacker to crash hidden services, or crash clients visiting hidden
13836 services. Hidden services should upgrade as soon as possible; clients
13837 should upgrade whenever packages become available.
13839 This release also contains two simple improvements to make hidden
13840 services a bit less vulnerable to denial-of-service attacks.
13842 o Major bugfixes (security, hidden service):
13843 - Fix an issue that would allow a malicious client to trigger an
13844 assertion failure and halt a hidden service. Fixes bug 15600;
13845 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13846 - Fix a bug that could cause a client to crash with an assertion
13847 failure when parsing a malformed hidden service descriptor. Fixes
13848 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13850 o Minor features (DoS-resistance, hidden service):
13851 - Introduction points no longer allow multiple INTRODUCE1 cells to
13852 arrive on the same circuit. This should make it more expensive for
13853 attackers to overwhelm hidden services with introductions.
13854 Resolves ticket 15515.
13855 - Decrease the amount of reattempts that a hidden service performs
13856 when its rendezvous circuits fail. This reduces the computational
13857 cost for running a hidden service under heavy load. Resolves
13861 Changes in version 0.2.6.6 - 2015-03-24
13862 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
13864 It adds numerous safety, security, correctness, and performance
13865 improvements. Client programs can be configured to use more kinds of
13866 sockets, AutomapHosts works better, the multithreading backend is
13867 improved, cell transmission is refactored, test coverage is much
13868 higher, more denial-of-service attacks are handled, guard selection is
13869 improved to handle long-term guards better, pluggable transports
13870 should work a bit better, and some annoying hidden service performance
13871 bugs should be addressed.
13873 o Minor bugfixes (portability):
13874 - Use the correct datatype in the SipHash-2-4 function to prevent
13875 compilers from assuming any sort of alignment. Fixes bug 15436;
13876 bugfix on 0.2.5.3-alpha.
13878 Changes in version 0.2.6.5-rc - 2015-03-18
13879 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
13880 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
13882 o Major bugfixes (client):
13883 - Avoid crashing when making certain configuration option changes on
13884 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
13887 o Major bugfixes (pluggable transports):
13888 - Initialize the extended OR Port authentication cookie before
13889 launching pluggable transports. This prevents a race condition
13890 that occurred when server-side pluggable transports would cache the
13891 authentication cookie before it has been (re)generated. Fixes bug
13892 15240; bugfix on 0.2.5.1-alpha.
13894 o Major bugfixes (portability):
13895 - Do not crash on startup when running on Solaris. Fixes a bug
13896 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
13899 o Minor features (heartbeat):
13900 - On relays, report how many connections we negotiated using each
13901 version of the Tor link protocols. This information will let us
13902 know if removing support for very old versions of the Tor
13903 protocols is harming the network. Closes ticket 15212.
13905 o Code simplification and refactoring:
13906 - Refactor main loop to extract the 'loop' part. This makes it
13907 easier to run Tor under Shadow. Closes ticket 15176.
13910 Changes in version 0.2.5.11 - 2015-03-17
13911 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
13913 It backports several bugfixes from the 0.2.6 branch, including a
13914 couple of medium-level security fixes for relays and exit nodes.
13915 It also updates the list of directory authorities.
13917 o Directory authority changes:
13918 - Remove turtles as a directory authority.
13919 - Add longclaw as a new (v3) directory authority. This implements
13920 ticket 13296. This keeps the directory authority count at 9.
13921 - The directory authority Faravahar has a new IP address. This
13922 closes ticket 14487.
13924 o Major bugfixes (crash, OSX, security):
13925 - Fix a remote denial-of-service opportunity caused by a bug in
13926 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13929 o Major bugfixes (relay, stability, possible security):
13930 - Fix a bug that could lead to a relay crashing with an assertion
13931 failure if a buffer of exactly the wrong layout was passed to
13932 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13933 0.2.0.10-alpha. Patch from 'cypherpunks'.
13934 - Do not assert if the 'data' pointer on a buffer is advanced to the
13935 very end of the buffer; log a BUG message instead. Only assert if
13936 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13938 o Major bugfixes (exit node stability):
13939 - Fix an assertion failure that could occur under high DNS load.
13940 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13941 diagnosed and fixed by "cypherpunks".
13943 o Major bugfixes (Linux seccomp2 sandbox):
13944 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13945 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13946 0.2.5.1-alpha. Patch from "sanic".
13948 o Minor features (controller):
13949 - New "GETINFO bw-event-cache" to get information about recent
13950 bandwidth events. Closes ticket 14128. Useful for controllers to
13951 get recent bandwidth history after the fix for ticket 13988.
13953 o Minor features (geoip):
13954 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13955 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13958 o Minor bugfixes (client, automapping):
13959 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13960 no value follows the option. Fixes bug 14142; bugfix on
13961 0.2.4.7-alpha. Patch by "teor".
13962 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13963 14195; bugfix on 0.1.0.1-rc.
13965 o Minor bugfixes (compilation):
13966 - Build without warnings with the stock OpenSSL srtp.h header, which
13967 has a duplicate declaration of SSL_get_selected_srtp_profile().
13968 Fixes bug 14220; this is OpenSSL's bug, not ours.
13970 o Minor bugfixes (directory authority):
13971 - Allow directory authorities to fetch more data from one another if
13972 they find themselves missing lots of votes. Previously, they had
13973 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13974 bugfix on 0.1.2.5-alpha.
13975 - Enlarge the buffer to read bwauth generated files to avoid an
13976 issue when parsing the file in dirserv_read_measured_bandwidths().
13977 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13979 o Minor bugfixes (statistics):
13980 - Increase period over which bandwidth observations are aggregated
13981 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13983 o Minor bugfixes (preventative security, C safety):
13984 - When reading a hexadecimal, base-32, or base-64 encoded value from
13985 a string, always overwrite the whole output buffer. This prevents
13986 some bugs where we would look at (but fortunately, not reveal)
13987 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13991 Changes in version 0.2.4.26 - 2015-03-17
13992 Tor 0.2.4.26 includes an updated list of directory authorities. It
13993 also backports a couple of stability and security bugfixes from 0.2.5
13996 o Directory authority changes:
13997 - Remove turtles as a directory authority.
13998 - Add longclaw as a new (v3) directory authority. This implements
13999 ticket 13296. This keeps the directory authority count at 9.
14000 - The directory authority Faravahar has a new IP address. This
14001 closes ticket 14487.
14003 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
14004 - Fix an assertion failure that could occur under high DNS load.
14005 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14006 diagnosed and fixed by "cypherpunks".
14008 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
14009 - Fix a bug that could lead to a relay crashing with an assertion
14010 failure if a buffer of exactly the wrong layout was passed to
14011 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14012 0.2.0.10-alpha. Patch from 'cypherpunks'.
14013 - Do not assert if the 'data' pointer on a buffer is advanced to the
14014 very end of the buffer; log a BUG message instead. Only assert if
14015 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14017 o Minor features (geoip):
14018 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14019 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14022 Changes in version 0.2.6.4-rc - 2015-03-09
14023 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
14024 attacker might be able to use in order to crash certain Tor
14025 directories. It also resolves some minor issues left over from, or
14026 introduced in, Tor 0.2.6.3-alpha or earlier.
14028 o Major bugfixes (crash, OSX, security):
14029 - Fix a remote denial-of-service opportunity caused by a bug in
14030 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14033 o Major bugfixes (relay, stability, possible security):
14034 - Fix a bug that could lead to a relay crashing with an assertion
14035 failure if a buffer of exactly the wrong layout is passed to
14036 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14037 0.2.0.10-alpha. Patch from "cypherpunks".
14038 - Do not assert if the 'data' pointer on a buffer is advanced to the
14039 very end of the buffer; log a BUG message instead. Only assert if
14040 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14042 o Major bugfixes (FreeBSD IPFW transparent proxy):
14043 - Fix address detection with FreeBSD transparent proxies, when
14044 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14047 o Major bugfixes (Linux seccomp2 sandbox):
14048 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
14049 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
14051 - Allow AF_UNIX hidden services to be used with the seccomp2
14052 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
14053 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14054 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14055 0.2.5.1-alpha. Patch from "sanic".
14057 o Minor features (controller):
14058 - Messages about problems in the bootstrap process now include
14059 information about the server we were trying to connect to when we
14060 noticed the problem. Closes ticket 15006.
14062 o Minor features (geoip):
14063 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14064 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14067 o Minor features (logs):
14068 - Quiet some log messages in the heartbeat and at startup. Closes
14071 o Minor bugfixes (certificate handling):
14072 - If an authority operator accidentally makes a signing certificate
14073 with a future publication time, do not discard its real signing
14074 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
14075 - Remove any old authority certificates that have been superseded
14076 for at least two days. Previously, we would keep superseded
14077 certificates until they expired, if they were published close in
14078 time to the certificate that superseded them. Fixes bug 11454;
14079 bugfix on 0.2.1.8-alpha.
14081 o Minor bugfixes (compilation):
14082 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
14084 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
14087 o Minor bugfixes (testing):
14088 - Fix endianness issues in unit test for resolve_my_address() to
14089 have it pass on big endian systems. Fixes bug 14980; bugfix on
14091 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
14092 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
14093 - When running the new 'make test-stem' target, use the configured
14094 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
14095 from "cypherpunks".
14096 - When running the zero-length-keys tests, do not use the default
14097 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
14100 o Directory authority IP change:
14101 - The directory authority Faravahar has a new IP address. This
14102 closes ticket 14487.
14105 - Remove some lingering dead code that once supported mempools.
14106 Mempools were disabled by default in 0.2.5, and removed entirely
14107 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
14111 Changes in version 0.2.6.3-alpha - 2015-02-19
14112 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
14113 the 0.2.6.x series. It introduces support for more kinds of sockets,
14114 makes it harder to accidentally run an exit, improves our
14115 multithreading backend, incorporates several fixes for the
14116 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
14118 If no major regressions or security holes are found in this version,
14119 the next version will be a release candidate.
14121 o Deprecated versions:
14122 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14123 advertise themselves on the network. Closes ticket 13555.
14125 o Major features (security, unix domain sockets):
14126 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14127 applications can reach Tor without having to create AF_INET or
14128 AF_INET6 sockets, meaning they can completely disable their
14129 ability to make non-Tor network connections. To create a socket of
14130 this type, use "SocksPort unix:/path/to/socket". Implements
14132 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14133 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14134 Implements ticket 11485.
14136 o Major features (changed defaults):
14137 - Prevent relay operators from unintentionally running exits: When a
14138 relay is configured as an exit node, we now warn the user unless
14139 the "ExitRelay" option is set to 1. We warn even more loudly if
14140 the relay is configured with the default exit policy, since this
14141 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14142 stops Tor from running as an exit relay. Closes ticket 10067.
14144 o Major features (directory system):
14145 - When downloading server- or microdescriptors from a directory
14146 server, we no longer launch multiple simultaneous requests to the
14147 same server. This reduces load on the directory servers,
14148 especially when directory guards are in use. Closes ticket 9969.
14149 - When downloading server- or microdescriptors over a tunneled
14150 connection, do not limit the length of our requests to what the
14151 Squid proxy is willing to handle. Part of ticket 9969.
14152 - Authorities can now vote on the correct digests and latest
14153 versions for different software packages. This allows packages
14154 that include Tor to use the Tor authority system as a way to get
14155 notified of updates and their correct digests. Implements proposal
14156 227. Closes ticket 10395.
14158 o Major features (guards):
14159 - Introduce the Guardfraction feature to improves load balancing on
14160 guard nodes. Specifically, it aims to reduce the traffic gap that
14161 guard nodes experience when they first get the Guard flag. This is
14162 a required step if we want to increase the guard lifetime to 9
14163 months or greater. Closes ticket 9321.
14165 o Major features (performance):
14166 - Make the CPU worker implementation more efficient by avoiding the
14167 kernel and lengthening pipelines. The original implementation used
14168 sockets to transfer data from the main thread to the workers, and
14169 didn't allow any thread to be assigned more than a single piece of
14170 work at once. The new implementation avoids communications
14171 overhead by making requests in shared memory, avoiding kernel IO
14172 where possible, and keeping more requests in flight at once.
14173 Implements ticket 9682.
14175 o Major features (relay):
14176 - Raise the minimum acceptable configured bandwidth rate for bridges
14177 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14178 20 KiB/sec.) Closes ticket 13822.
14180 o Major bugfixes (exit node stability):
14181 - Fix an assertion failure that could occur under high DNS load.
14182 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14183 diagnosed and fixed by "cypherpunks".
14185 o Major bugfixes (mixed relay-client operation):
14186 - When running as a relay and client at the same time (not
14187 recommended), if we decide not to use a new guard because we want
14188 to retry older guards, only close the locally-originating circuits
14189 passing through that guard. Previously we would close all the
14190 circuits through that guard. Fixes bug 9819; bugfix on
14191 0.2.1.1-alpha. Reported by "skruffy".
14193 o Minor features (build):
14194 - New --disable-system-torrc compile-time option to prevent Tor from
14195 looking for the system-wide torrc or torrc-defaults files.
14196 Resolves ticket 13037.
14198 o Minor features (controller):
14199 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14200 events so controllers can observe circuit isolation inputs. Closes
14202 - ControlPort now supports the unix:/path/to/socket syntax as an
14203 alternative to the ControlSocket option, for consistency with
14204 SocksPort and HiddenServicePort. Closes ticket 14451.
14205 - New "GETINFO bw-event-cache" to get information about recent
14206 bandwidth events. Closes ticket 14128. Useful for controllers to
14207 get recent bandwidth history after the fix for ticket 13988.
14209 o Minor features (Denial of service resistance):
14210 - Count the total number of bytes used storing hidden service
14211 descriptors against the value of MaxMemInQueues. If we're low on
14212 memory, and more than 20% of our memory is used holding hidden
14213 service descriptors, free them until no more than 10% of our
14214 memory holds hidden service descriptors. Free the least recently
14215 fetched descriptors first. Resolves ticket 13806.
14216 - When we have recently been under memory pressure (over 3/4 of
14217 MaxMemInQueues is allocated), then allocate smaller zlib objects
14218 for small requests. Closes ticket 11791.
14220 o Minor features (geoip):
14221 - Update geoip and geoip6 files to the January 7 2015 Maxmind
14222 GeoLite2 Country database.
14224 o Minor features (guard nodes):
14225 - Reduce the time delay before saving guard status to disk from 10
14226 minutes to 30 seconds (or from one hour to 10 minutes if
14227 AvoidDiskWrites is set). Closes ticket 12485.
14229 o Minor features (hidden service):
14230 - Make Sybil attacks against hidden services harder by changing the
14231 minimum time required to get the HSDir flag from 25 hours up to 96
14232 hours. Addresses ticket 14149.
14233 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14234 services to disable the anti-scanning feature introduced in
14235 0.2.6.2-alpha. With this option not set, a connection to an
14236 unlisted port closes the circuit. With this option set, only a
14237 RELAY_DONE cell is sent. Closes ticket 14084.
14239 o Minor features (interface):
14240 - Implement "-f -" command-line option to read torrc configuration
14241 from standard input, if you don't want to store the torrc file in
14242 the file system. Implements feature 13865.
14244 o Minor features (logging):
14245 - Add a count of unique clients to the bridge heartbeat message.
14246 Resolves ticket 6852.
14247 - Suppress "router info incompatible with extra info" message when
14248 reading extrainfo documents from cache. (This message got loud
14249 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14251 - Elevate hidden service authorized-client message from DEBUG to
14252 INFO. Closes ticket 14015.
14254 o Minor features (stability):
14255 - Add assertions in our hash-table iteration code to check for
14256 corrupted values that could cause infinite loops. Closes
14259 o Minor features (systemd):
14260 - Various improvements and modernizations in systemd hardening
14261 support. Closes ticket 13805. Patch from Craig Andrews.
14263 o Minor features (testing networks):
14264 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14265 and the default on a testing network to 2 minutes. Drop the
14266 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14267 keep the default on a testing network at 30 seconds. This reduces
14268 HS bootstrap time to around 25 seconds. Also, change the default
14269 time in test-network.sh to match. Closes ticket 13401. Patch
14271 - Create TestingDirAuthVoteHSDir to correspond to
14272 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14273 HSDir flag for the listed relays regardless of uptime or ORPort
14274 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14275 Partial implementation for ticket 14067. Patch by "teor".
14277 o Minor features (tor2web mode):
14278 - Introduce the config option Tor2webRendezvousPoints, which allows
14279 clients in Tor2webMode to select a specific Rendezvous Point to be
14280 used in HS circuits. This might allow better performance for
14281 Tor2Web nodes. Implements ticket 12844.
14283 o Minor bugfixes (client DNS):
14284 - Report the correct cached DNS expiration times on SOCKS port or in
14285 DNS replies. Previously, we would report everything as "never
14286 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14287 - Avoid a small memory leak when we find a cached answer for a
14288 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14289 side DNS caching is off by default, and is not recommended.) Fixes
14290 bug 14259; bugfix on 0.2.0.1-alpha.
14292 o Minor bugfixes (client, automapping):
14293 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14294 no value follows the option. Fixes bug 14142; bugfix on
14295 0.2.4.7-alpha. Patch by "teor".
14296 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14297 14195; bugfix on 0.1.0.1-rc.
14298 - Prevent changes to other options from removing the wildcard value
14299 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14301 - Allow MapAddress and AutomapHostsOnResolve to work together when
14302 an address is mapped into another address type (like .onion) that
14303 must be automapped at resolve time. Fixes bug 7555; bugfix
14306 o Minor bugfixes (client, bridges):
14307 - When we are using bridges and we had a network connectivity
14308 problem, only retry connecting to our currently configured
14309 bridges, not all bridges we know about and remember using. Fixes
14310 bug 14216; bugfix on 0.2.2.17-alpha.
14312 o Minor bugfixes (client, IPv6):
14313 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14314 flag is not set; and not because the NoIPv4Traffic flag was set.
14315 Previously we'd looked at the NoIPv4Traffic flag for both types of
14316 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14318 o Minor bugfixes (compilation):
14319 - The address of an array in the middle of a structure will always
14320 be non-NULL. clang recognises this and complains. Disable the
14321 tautologous and redundant check to silence this warning. Fixes bug
14322 14001; bugfix on 0.2.1.2-alpha.
14323 - Avoid warnings when building with systemd 209 or later. Fixes bug
14324 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
14325 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14326 Addresses ticket 14188.
14327 - Build without warnings with the stock OpenSSL srtp.h header, which
14328 has a duplicate declaration of SSL_get_selected_srtp_profile().
14329 Fixes bug 14220; this is OpenSSL's bug, not ours.
14330 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14331 is not enabled at compile time. Previously, this code was included
14332 in a disabled state. See discussion on ticket 12844.
14333 - Remove the --disable-threads configure option again. It was
14334 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
14335 14819; bugfix on 0.2.6.2-alpha.
14337 o Minor bugfixes (controller):
14338 - Report "down" in response to the "GETINFO entry-guards" command
14339 when relays are down with an unreachable_since value. Previously,
14340 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14341 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14342 14116; bugfix on 0.2.2.9-alpha.
14343 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
14344 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
14346 o Minor bugfixes (directory authority):
14347 - Allow directory authorities to fetch more data from one another if
14348 they find themselves missing lots of votes. Previously, they had
14349 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14350 bugfix on 0.1.2.5-alpha.
14351 - Do not attempt to download extrainfo documents which we will be
14352 unable to validate with a matching server descriptor. Fixes bug
14353 13762; bugfix on 0.2.0.1-alpha.
14354 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14355 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14356 - Enlarge the buffer to read bwauth generated files to avoid an
14357 issue when parsing the file in dirserv_read_measured_bandwidths().
14358 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14360 o Minor bugfixes (file handling):
14361 - Stop failing when key files are zero-length. Instead, generate new
14362 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14363 on all versions of Tor. Patch by "teor".
14364 - Stop generating a fresh .old RSA onion key file when the .old file
14365 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14366 - Avoid overwriting .old key files with empty key files.
14367 - Skip loading zero-length extrainfo store, router store, stats,
14368 state, and key files.
14369 - Avoid crashing when trying to reload a torrc specified as a
14370 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14373 o Minor bugfixes (hidden services):
14374 - Close the introduction circuit when we have no more usable intro
14375 points, instead of waiting for it to time out. This also ensures
14376 that no follow-up HS descriptor fetch is triggered when the
14377 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14378 - When fetching a hidden service descriptor for a down service that
14379 was recently up, do not keep refetching until we try the same
14380 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14381 - Successfully launch Tor with a nonexistent hidden service
14382 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
14383 14106; bugfix on 0.2.6.2-alpha.
14385 o Minor bugfixes (logging):
14386 - Avoid crashing when there are more log domains than entries in
14387 domain_list. Bugfix on 0.2.3.1-alpha.
14388 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
14390 - Don't log messages to stdout twice when starting up. Fixes bug
14391 13993; bugfix on 0.2.6.1-alpha.
14393 o Minor bugfixes (parsing):
14394 - Stop accepting milliseconds (or other junk) at the end of
14395 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14396 - Support two-number and three-number version numbers correctly, in
14397 case we change the Tor versioning system in the future. Fixes bug
14398 13661; bugfix on 0.0.8pre1.
14400 o Minor bugfixes (path counting):
14401 - When deciding whether the consensus lists any exit nodes, count
14402 the number listed in the consensus, not the number we have
14403 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
14404 - When deciding whether we have any exit nodes, only examine
14405 ExitNodes when the ExitNodes option is actually set. Fixes part of
14406 bug 14918; bugfix on 0.2.6.2-alpha.
14407 - Get rid of redundant and possibly scary warnings that we are
14408 missing directory information while we bootstrap. Fixes part of
14409 bug 14918; bugfix on 0.2.6.2-alpha.
14411 o Minor bugfixes (portability):
14412 - Fix the ioctl()-based network interface lookup code so that it
14413 will work on systems that have variable-length struct ifreq, for
14415 - Fix scheduler compilation on targets where char is unsigned. Fixes
14416 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
14418 o Minor bugfixes (sandbox):
14419 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14420 Previously, glibc would try to write them to /dev/tty, and the
14421 sandbox would trap the call and make Tor exit prematurely. Fixes
14422 bug 14759; bugfix on 0.2.5.1-alpha.
14424 o Minor bugfixes (shutdown):
14425 - When shutting down, always call event_del() on lingering read or
14426 write events before freeing them. Otherwise, we risk double-frees
14427 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
14430 o Minor bugfixes (small memory leaks):
14431 - Avoid leaking memory when using IPv6 virtual address mappings.
14432 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
14435 o Minor bugfixes (statistics):
14436 - Increase period over which bandwidth observations are aggregated
14437 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14439 o Minor bugfixes (systemd support):
14440 - Fix detection and operation of systemd watchdog. Fixes part of bug
14441 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
14442 - Run correctly under systemd with the RunAsDaemon option set. Fixes
14443 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
14444 - Inform the systemd supervisor about more changes in the Tor
14445 process status. Implements part of ticket 14141. Patch from
14447 - Cause the "--disable-systemd" option to actually disable systemd
14448 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
14451 o Minor bugfixes (TLS):
14452 - Check more thoroughly throughout the TLS code for possible
14453 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
14455 o Minor bugfixes (transparent proxy):
14456 - Use getsockname, not getsockopt, to retrieve the address for a
14457 TPROXY-redirected connection. Fixes bug 13796; bugfix
14460 o Code simplification and refactoring:
14461 - Move fields related to isolating and configuring client ports into
14462 a shared structure. Previously, they were duplicated across
14463 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
14464 to copy them correctly had been the cause of at least one bug in
14465 the past. Closes ticket 8546.
14466 - Refactor the get_interface_addresses_raw() doom-function into
14467 multiple smaller and simpler subfunctions. Cover the resulting
14468 subfunctions with unit-tests. Fixes a significant portion of
14470 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
14471 only for version <= 0.2.2.24 which is now deprecated. Closes
14473 - Remove a test for a long-defunct broken version-one
14477 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
14478 for writing the OpenBSD-specific tips. Resolves ticket 13702.
14479 - Make the tor-resolve documentation match its help string and its
14480 options. Resolves part of ticket 14325.
14481 - Log a more useful error message from tor-resolve when failing to
14482 look up a hidden service address. Resolves part of ticket 14325.
14484 o Downgraded warnings:
14485 - Don't warn when we've attempted to contact a relay using the wrong
14486 ntor onion key. Closes ticket 9635.
14488 o Removed features:
14489 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
14490 longer silently accepted as an alias for "ExitNodes".
14491 - The --enable-mempool and --enable-buf-freelists options, which
14492 were originally created to work around bad malloc implementations,
14493 no longer exist. They were off-by-default in 0.2.5. Closes
14497 - Make the checkdir/perms test complete successfully even if the
14498 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
14499 - Test that tor does not fail when key files are zero-length. Check
14500 that tor generates new keys, and overwrites the empty key files.
14501 - Test that tor generates new keys when keys are missing
14502 (existing behavior).
14503 - Test that tor does not overwrite key files that already contain
14504 data (existing behavior). Tests bug 13111. Patch by "teor".
14505 - New "make test-stem" target to run stem integration tests.
14506 Requires that the "STEM_SOURCE_DIR" environment variable be set.
14507 Closes ticket 14107.
14508 - Make the test_cmdline_args.py script work correctly on Windows.
14509 Patch from Gisle Vanem.
14510 - Move the slower unit tests into a new "./src/test/test-slow"
14511 binary that can be run independently of the other tests. Closes
14513 - Avoid undefined behavior when sampling huge values from the
14514 Laplace distribution. This made unittests fail on Raspberry Pi.
14515 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
14518 Changes in version 0.2.6.2-alpha - 2014-12-31
14519 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
14520 It introduces a major new backend for deciding when to send cells on
14521 channels, which should lead down the road to big performance
14522 increases. It contains security and statistics features for better
14523 work on hidden services, and numerous bugfixes.
14525 This release contains many new unit tests, along with major
14526 performance improvements for running testing networks using Chutney.
14527 Thanks to a series of patches contributed by "teor", testing networks
14528 should now bootstrap in seconds, rather than minutes.
14530 o Major features (relay, infrastructure):
14531 - Complete revision of the code that relays use to decide which cell
14532 to send next. Formerly, we selected the best circuit to write on
14533 each channel, but we didn't select among channels in any
14534 sophisticated way. Now, we choose the best circuits globally from
14535 among those whose channels are ready to deliver traffic.
14537 This patch implements a new inter-cmux comparison API, a global
14538 high/low watermark mechanism and a global scheduler loop for
14539 transmission prioritization across all channels as well as among
14540 circuits on one channel. This schedule is currently tuned to
14541 (tolerantly) avoid making changes in network performance, but it
14542 should form the basis for major circuit performance increases in
14543 the future. Code by Andrea; tuning by Rob Jansen; implements
14546 o Major features (hidden services):
14547 - Make HS port scanning more difficult by immediately closing the
14548 circuit when a user attempts to connect to a nonexistent port.
14549 Closes ticket 13667.
14550 - Add a HiddenServiceStatistics option that allows Tor relays to
14551 gather and publish statistics about the overall size and volume of
14552 hidden service usage. Specifically, when this option is turned on,
14553 an HSDir will publish an approximate number of hidden services
14554 that have published descriptors to it the past 24 hours. Also, if
14555 a relay has acted as a hidden service rendezvous point, it will
14556 publish the approximate amount of rendezvous cells it has relayed
14557 the past 24 hours. The statistics themselves are obfuscated so
14558 that the exact values cannot be derived. For more details see
14559 proposal 238, "Better hidden service stats from Tor relays". This
14560 feature is currently disabled by default. Implements feature 13192.
14562 o Major bugfixes (client, automap):
14563 - Repair automapping with IPv6 addresses. This automapping should
14564 have worked previously, but one piece of debugging code that we
14565 inserted to detect a regression actually caused the regression to
14566 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14567 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14570 o Major bugfixes (hidden services):
14571 - When closing an introduction circuit that was opened in parallel
14572 with others, don't mark the introduction point as unreachable.
14573 Previously, the first successful connection to an introduction
14574 point would make the other introduction points get marked as
14575 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14577 o Directory authority changes:
14578 - Remove turtles as a directory authority.
14579 - Add longclaw as a new (v3) directory authority. This implements
14580 ticket 13296. This keeps the directory authority count at 9.
14582 o Major removed features:
14583 - Tor clients no longer support connecting to hidden services
14584 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14585 option has been removed. (There shouldn't be any hidden services
14586 running these versions on the network.) Closes ticket 7803.
14588 o Minor features (client):
14589 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14590 is enabled, reject requests with IP addresses as hostnames.
14591 Resolves ticket 13315.
14593 o Minor features (controller):
14594 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14595 write an unscheduled heartbeat message to the log. Implements
14598 o Minor features (geoip):
14599 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14602 o Minor features (hidden services):
14603 - When re-enabling the network, don't try to build introduction
14604 circuits until we have successfully built a circuit. This makes
14605 hidden services come up faster when the network is re-enabled.
14606 Patch from "akwizgran". Closes ticket 13447.
14607 - When we fail to retrieve a hidden service descriptor, send the
14608 controller an "HS_DESC FAILED" controller event. Implements
14610 - New HiddenServiceDirGroupReadable option to cause hidden service
14611 directories and hostname files to be created group-readable. Patch
14612 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14614 o Minor features (systemd):
14615 - Where supported, when running with systemd, report successful
14616 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14617 - When running with systemd, support systemd watchdog messages. Part
14618 of ticket 11016. Patch by Michael Scherer.
14620 o Minor features (transparent proxy):
14621 - Update the transparent proxy option checks to allow for both ipfw
14622 and pf on OS X. Closes ticket 14002.
14623 - Use the correct option when using IPv6 with transparent proxy
14624 support on Linux. Resolves 13808. Patch by Francisco Blas
14627 o Minor bugfixes (preventative security, C safety):
14628 - When reading a hexadecimal, base-32, or base-64 encoded value from
14629 a string, always overwrite the whole output buffer. This prevents
14630 some bugs where we would look at (but fortunately, not reveal)
14631 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14633 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14634 just the part that's used. This makes it harder for data leak bugs
14635 to occur in the event of other programming failures. Resolves
14638 o Minor bugfixes (client, microdescriptors):
14639 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14640 computing which microdescriptors to download. This keeps us from
14641 erroneous download behavior if two microdescriptor digests ever
14642 have the same first 160 bits. Fixes part of bug 13399; bugfix
14644 - Reset a router's status if its microdescriptor digest changes,
14645 even if the first 160 bits remain the same. Fixes part of bug
14646 13399; bugfix on 0.2.3.1-alpha.
14648 o Minor bugfixes (compilation):
14649 - Silence clang warnings under --enable-expensive-hardening,
14650 including implicit truncation of 64 bit values to 32 bit, const
14651 char assignment to self, tautological compare, and additional
14652 parentheses around equality tests. Fixes bug 13577; bugfix
14654 - Fix a clang warning about checking whether an address in the
14655 middle of a structure is NULL. Fixes bug 14001; bugfix
14658 o Minor bugfixes (hidden services):
14659 - Correctly send a controller event when we find that a rendezvous
14660 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14661 - Pre-check directory permissions for new hidden-services to avoid
14662 at least one case of "Bug: Acting on config options left us in a
14663 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14664 - When adding a new hidden service (for example, via SETCONF), Tor
14665 no longer congratulates the user for running a relay. Fixes bug
14666 13941; bugfix on 0.2.6.1-alpha.
14667 - When fetching hidden service descriptors, we now check not only
14668 for whether we got the hidden service we had in mind, but also
14669 whether we got the particular descriptors we wanted. This prevents
14670 a class of inefficient but annoying DoS attacks by hidden service
14671 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14674 o Minor bugfixes (Linux seccomp2 sandbox):
14675 - Make transparent proxy support work along with the seccomp2
14676 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14677 by Francisco Blas Izquierdo Riera.
14678 - Fix a memory leak in tor-resolve when running with the sandbox
14679 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14681 o Minor bugfixes (logging):
14682 - Downgrade warnings about RSA signature failures to info log level.
14683 Emit a warning when an extra info document is found incompatible
14684 with a corresponding router descriptor. Fixes bug 9812; bugfix
14686 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14687 correctly. Fixes bug 13701; bugfix on 0.0.6.
14689 o Minor bugfixes (misc):
14690 - Stop allowing invalid address patterns like "*/24" that contain
14691 both a wildcard address and a bit prefix length. This affects all
14692 our address-range parsing code. Fixes bug 7484; bugfix
14695 o Minor bugfixes (testing networks, fast startup):
14696 - Allow Tor to build circuits using a consensus with no exits. If
14697 the consensus has no exits (typical of a bootstrapping test
14698 network), allow Tor to build circuits once enough descriptors have
14699 been downloaded. This assists in bootstrapping a testing Tor
14700 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14702 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14703 header to directory servers. This allows us to obtain consensuses
14704 promptly when the consensus interval is very short. This assists
14705 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14706 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14707 - Stop assuming that private addresses are local when checking
14708 reachability in a TestingTorNetwork. Instead, when testing, assume
14709 all OR connections are remote. (This is necessary due to many test
14710 scenarios running all relays on localhost.) This assists in
14711 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14712 0.1.0.1-rc. Patch by "teor".
14713 - Avoid building exit circuits from a consensus with no exits. Now
14714 thanks to our fix for 13718, we accept a no-exit network as not
14715 wholly lost, but we need to remember not to try to build exit
14716 circuits on it. Closes ticket 13814; patch by "teor".
14717 - Stop requiring exits to have non-zero bandwithcapacity in a
14718 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14719 ignore exit bandwidthcapacity. This assists in bootstrapping a
14720 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14721 on 0.2.0.3-alpha. Patch by "teor".
14722 - Add "internal" to some bootstrap statuses when no exits are
14723 available. If the consensus does not contain Exits, Tor will only
14724 build internal circuits. In this case, relevant statuses will
14725 contain the word "internal" as indicated in the Tor control-
14726 spec.txt. When bootstrap completes, Tor will be ready to build
14727 internal circuits. If a future consensus contains Exits, exit
14728 circuits may become available. Fixes part of bug 13718; bugfix on
14729 0.2.4.10-alpha. Patch by "teor".
14730 - Decrease minimum consensus interval to 10 seconds when
14731 TestingTorNetwork is set, or 5 seconds for the first consensus.
14732 Fix assumptions throughout the code that assume larger intervals.
14733 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14735 - Avoid excluding guards from path building in minimal test
14736 networks, when we're in a test network and excluding guards would
14737 exclude all relays. This typically occurs in incredibly small tor
14738 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14739 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14741 o Code simplification and refactoring:
14742 - Stop using can_complete_circuits as a global variable; access it
14743 with a function instead.
14744 - Avoid using operators directly as macro arguments: this lets us
14745 apply coccinelle transformations to our codebase more directly.
14746 Closes ticket 13172.
14747 - Combine the functions used to parse ClientTransportPlugin and
14748 ServerTransportPlugin into a single function. Closes ticket 6456.
14749 - Add inline functions and convenience macros for inspecting channel
14750 state. Refactor the code to use convenience macros instead of
14751 checking channel state directly. Fixes issue 7356.
14752 - Document all members of was_router_added_t and rename
14753 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
14754 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
14755 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
14756 constant instead of hardcoded value. Fixes issue 13840.
14757 - Refactor our generic strmap and digestmap types into a single
14758 implementation, so that we can add a new digest256map
14762 - Document the bridge-authority-only 'networkstatus-bridges' file.
14763 Closes ticket 13713; patch from "tom".
14764 - Fix typo in PredictedPortsRelevanceTime option description in
14765 manpage. Resolves issue 13707.
14766 - Stop suggesting that users specify relays by nickname: it isn't a
14767 good idea. Also, properly cross-reference how to specify relays in
14768 all parts of manual documenting options that take a list of
14769 relays. Closes ticket 13381.
14770 - Clarify the HiddenServiceDir option description in manpage to make
14771 it clear that relative paths are taken with respect to the current
14772 working directory. Also clarify that this behavior is not
14773 guaranteed to remain indefinitely. Fixes issue 13913.
14776 - New tests for many parts of channel, relay, and circuitmux
14777 functionality. Code by Andrea; part of 9262.
14778 - New tests for parse_transport_line(). Part of ticket 6456.
14779 - In the unit tests, use chgrp() to change the group of the unit
14780 test temporary directory to the current user, so that the sticky
14781 bit doesn't interfere with tests that check directory groups.
14783 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
14787 Changes in version 0.2.6.1-alpha - 2014-10-30
14788 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
14789 includes numerous code cleanups and new tests, and fixes a large
14790 number of annoying bugs. Out-of-memory conditions are handled better
14791 than in 0.2.5, pluggable transports have improved proxy support, and
14792 clients now use optimistic data for contacting hidden services. Also,
14793 we are now more robust to changes in what we consider a parseable
14794 directory object, so that tightening restrictions does not have a risk
14795 of introducing infinite download loops.
14797 This is the first alpha release in a new series, so expect there to be
14798 bugs. Users who would rather test out a more stable branch should stay
14799 with 0.2.5.x for now.
14801 o New compiler and system requirements:
14802 - Tor 0.2.6.x requires that your compiler support more of the C99
14803 language standard than before. The 'configure' script now detects
14804 whether your compiler supports C99 mid-block declarations and
14805 designated initializers. If it does not, Tor will not compile.
14807 We may revisit this requirement if it turns out that a significant
14808 number of people need to build Tor with compilers that don't
14809 bother implementing a 15-year-old standard. Closes ticket 13233.
14810 - Tor no longer supports systems without threading support. When we
14811 began working on Tor, there were several systems that didn't have
14812 threads, or where the thread support wasn't able to run the
14813 threads of a single process on multiple CPUs. That no longer
14814 holds: every system where Tor needs to run well now has threading
14815 support. Resolves ticket 12439.
14817 o Removed platform support:
14818 - We no longer include special code to build on Windows CE; as far
14819 as we know, nobody has used Tor on Windows CE in a very long time.
14820 Closes ticket 11446.
14822 o Major features (bridges):
14823 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14824 transports if they are configured via the "TOR_PT_PROXY"
14825 environment variable. Implements proposal 232. Resolves
14828 o Major features (client performance, hidden services):
14829 - Allow clients to use optimistic data when connecting to a hidden
14830 service, which should remove a round-trip from hidden service
14831 initialization. See proposal 181 for details. Implements
14834 o Major features (directory system):
14835 - Upon receiving an unparseable directory object, if its digest
14836 matches what we expected, then don't try to download it again.
14837 Previously, when we got a descriptor we didn't like, we would keep
14838 trying to download it over and over. Closes ticket 11243.
14840 o Major features (sample torrc):
14841 - Add a new, infrequently-changed "torrc.minimal". This file is
14842 similar to torrc.sample, but it will change as infrequently as
14843 possible, for the benefit of users whose systems prompt them for
14844 intervention whenever a default configuration file is changed.
14845 Making this change allows us to update torrc.sample to be a more
14846 generally useful "sample torrc".
14848 o Major bugfixes (directory authorities):
14849 - Do not assign the HSDir flag to relays if they are not Valid, or
14850 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14852 o Major bugfixes (directory bandwidth performance):
14853 - Don't flush the zlib buffer aggressively when compressing
14854 directory information for clients. This should save about 7% of
14855 the bandwidth currently used for compressed descriptors and
14856 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14858 o Minor features (security, memory wiping):
14859 - Ensure we securely wipe keys from memory after
14860 crypto_digest_get_digest and init_curve25519_keypair_from_file
14861 have finished using them. Resolves ticket 13477.
14863 o Minor features (security, out-of-memory handling):
14864 - When handling an out-of-memory condition, allocate less memory for
14865 temporary data structures. Fixes issue 10115.
14866 - When handling an out-of-memory condition, consider more types of
14867 buffers, including those on directory connections, and zlib
14868 buffers. Resolves ticket 11792.
14871 - When identity keypair is generated for first time, log a
14872 congratulatory message that links to the new relay lifecycle
14873 document. Implements feature 10427.
14875 o Minor features (client):
14876 - Clients are now willing to send optimistic data (before they
14877 receive a 'connected' cell) to relays of any version. (Relays
14878 without support for optimistic data are no longer supported on the
14879 Tor network.) Resolves ticket 13153.
14881 o Minor features (directory authorities):
14882 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14883 Implements a feature proposed during discussion of bug 13000.
14884 - In tor-gencert, report an error if the user provides the same
14885 argument more than once.
14886 - If a directory authority can't find a best consensus method in the
14887 votes that it holds, it now falls back to its favorite consensus
14888 method. Previously, it fell back to method 1. Neither of these is
14889 likely to get enough signatures, but "fall back to favorite"
14890 doesn't require us to maintain support an obsolete consensus
14891 method. Implements part of proposal 215.
14893 o Minor features (logging):
14894 - On Unix-like systems, you can now use named pipes as the target of
14895 the Log option, and other options that try to append to files.
14896 Closes ticket 12061. Patch from "carlo von lynX".
14897 - When opening a log file at startup, send it every log message that
14898 we generated between startup and opening it. Previously, log
14899 messages that were generated before opening the log file were only
14900 logged to stdout. Closes ticket 6938.
14901 - Add a TruncateLogFile option to overwrite logs instead of
14902 appending to them. Closes ticket 5583.
14904 o Minor features (portability, Solaris):
14905 - Threads are no longer disabled by default on Solaris; we believe
14906 that the versions of Solaris with broken threading support are all
14907 obsolete by now. Resolves ticket 9495.
14909 o Minor features (relay):
14910 - Re-check our address after we detect a changed IP address from
14911 getsockname(). This ensures that the controller command "GETINFO
14912 address" will report the correct value. Resolves ticket 11582.
14914 - A new AccountingRule option lets Relays set whether they'd like
14915 AccountingMax to be applied separately to inbound and outbound
14916 traffic, or applied to the sum of inbound and outbound traffic.
14917 Resolves ticket 961. Patch by "chobe".
14919 o Minor features (testing networks):
14920 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14921 the "Exit" flag regardless of their uptime, bandwidth, or exit
14922 policy. TestingTorNetwork must be set for this option to have any
14923 effect. Previously, authorities would take up to 35 minutes to
14924 give nodes the Exit flag in a test network. Partially implements
14927 o Minor features (validation):
14928 - Check all date/time values passed to tor_timegm and
14929 parse_rfc1123_time for validity, taking leap years into account.
14930 Improves HTTP header validation. Implemented with bug 13476.
14931 - In correct_tm(), limit the range of values returned by system
14932 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14933 This means we don't have to deal with negative or too large dates,
14934 even if a clock is wrong. Otherwise we might fail to read a file
14935 written by us which includes such a date. Fixes bug 13476.
14937 o Minor bugfixes (bridge clients):
14938 - When configured to use a bridge without an identity digest (not
14939 recommended), avoid launching an extra channel to it when
14940 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14942 o Minor bugfixes (bridges):
14943 - When DisableNetwork is set, do not launch pluggable transport
14944 plugins, and if any are running, terminate them. Fixes bug 13213;
14945 bugfix on 0.2.3.6-alpha.
14947 o Minor bugfixes (C correctness):
14948 - Fix several instances of possible integer overflow/underflow/NaN.
14949 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
14951 - In circuit_build_times_calculate_timeout() in circuitstats.c,
14952 avoid dividing by zero in the pareto calculations. This traps
14953 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
14955 - Fix an integer overflow in format_time_interval(). Fixes bug
14956 13393; bugfix on 0.2.0.10-alpha.
14957 - Set the correct day of year value when the system's localtime(_r)
14958 or gmtime(_r) functions fail to set struct tm. Not externally
14959 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14960 - Avoid unlikely signed integer overflow in tor_timegm on systems
14961 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14963 o Minor bugfixes (client):
14964 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14965 BadExit flag are not considered worthy candidates. Fixes bug
14966 13066; bugfix on 0.1.2.3-alpha.
14967 - Use the consensus schedule for downloading consensuses, and not
14968 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14969 - Handle unsupported or malformed SOCKS5 requests properly by
14970 responding with the appropriate error message before closing the
14971 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14973 o Minor bugfixes (client, torrc):
14974 - Stop modifying the value of our DirReqStatistics torrc option just
14975 because we're not a bridge or relay. This bug was causing Tor
14976 Browser users to write "DirReqStatistics 0" in their torrc files
14977 as if they had chosen to change the config. Fixes bug 4244; bugfix
14979 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14980 that our options have changed every time we SIGHUP. Fixes bug
14981 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14983 o Minor bugfixes (controller):
14984 - Return an error when the second or later arguments of the
14985 "setevents" controller command are invalid events. Previously we
14986 would return success while silently skipping invalid events. Fixes
14987 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14989 o Minor bugfixes (directory system):
14990 - Always believe that v3 directory authorities serve extra-info
14991 documents, whether they advertise "caches-extra-info" or not.
14992 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14993 - When running as a v3 directory authority, advertise that you serve
14994 extra-info documents so that clients who want them can find them
14995 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14996 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14997 Previously, directories offering BRIDGE_DIRINFO and some other
14998 flag (i.e. microdescriptors or extrainfo) would be ignored when
14999 looking for bridges. Partially fixes bug 13163; bugfix
15002 o Minor bugfixes (networking):
15003 - Check for orconns and use connection_or_close_for_error() rather
15004 than connection_mark_for_close() directly in the getsockopt()
15005 failure case of connection_handle_write_impl(). Fixes bug 11302;
15006 bugfix on 0.2.4.4-alpha.
15008 o Minor bugfixes (relay):
15009 - When generating our family list, remove spaces from around the
15010 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
15011 - If our previous bandwidth estimate was 0 bytes, allow publishing a
15012 new relay descriptor immediately. Fixes bug 13000; bugfix
15015 o Minor bugfixes (testing networks):
15016 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15017 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15018 - Stop using the default authorities in networks which provide both
15019 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15020 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15022 o Minor bugfixes (testing):
15023 - Stop spawn test failures due to a race condition between the
15024 SIGCHLD handler updating the process status, and the test reading
15025 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15027 o Minor bugfixes (testing, Windows):
15028 - Avoid passing an extra backslash when creating a temporary
15029 directory for running the unit tests on Windows. Fixes bug 12392;
15030 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15032 o Minor bugfixes (windows):
15033 - Remove code to special-case handling of NTE_BAD_KEYSET when
15034 acquiring windows CryptoAPI context. This error can't actually
15035 occur for the parameters we're providing. Fixes bug 10816; bugfix
15038 o Minor bugfixes (zlib):
15039 - Avoid truncating a zlib stream when trying to finalize it with an
15040 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15043 - Allow our configure script to build correctly with autoconf 2.62
15044 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
15045 - Improve the error message from ./configure to make it clear that
15046 when asciidoc has not been found, the user will have to either add
15047 --disable-asciidoc argument or install asciidoc. Resolves
15050 o Code simplification and refactoring:
15051 - Change the entry_is_live() function to take named bitfield
15052 elements instead of an unnamed list of booleans. Closes
15054 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15055 Resolves ticket 12205.
15056 - Use calloc and reallocarray functions instead of multiply-
15057 then-malloc. This makes it less likely for us to fall victim to an
15058 integer overflow attack when allocating. Resolves ticket 12855.
15059 - Use the standard macro name SIZE_MAX, instead of our
15061 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15062 functions which take them as arguments. Replace 0 with NO_DIRINFO
15063 in a function call for clarity. Seeks to prevent future issues
15065 - Avoid 4 null pointer errors under clang static analysis by using
15066 tor_assert() to prove that the pointers aren't null. Fixes
15068 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15069 represent parsing options, instead of a confusing mess of
15070 booleans. Resolves ticket 8197.
15071 - Introduce a helper function to parse ExitPolicy in
15072 or_options_t structure.
15075 - Add a doc/TUNING document with tips for handling large numbers of
15076 TCP connections when running busy Tor relay. Update the warning
15077 message to point to this file when running out of sockets
15078 operating system is allowing to use simultaneously. Resolves
15081 o Removed features:
15082 - We no longer remind the user about configuration options that have
15083 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15084 - Remove our old, non-weighted bandwidth-based node selection code.
15085 Previously, we used it as a fallback when we couldn't perform
15086 weighted bandwidth-based node selection. But that would only
15087 happen in the cases where we had no consensus, or when we had a
15088 consensus generated by buggy or ancient directory authorities. In
15089 either case, it's better to use the more modern, better maintained
15090 algorithm, with reasonable defaults for the weights. Closes
15092 - Remove the --disable-curve25519 configure option. Relays and
15093 clients now are required to support curve25519 and the
15095 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15096 used to be deprecated synonyms for "StrictNodes", are now marked
15097 obsolete. Resolves ticket 12226.
15098 - Clients don't understand the BadDirectory flag in the consensus
15099 anymore, and ignore it.
15102 - Refactor the function that chooses guard nodes so that it can more
15103 easily be tested; write some tests for it.
15104 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15105 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15106 - Create unit tests for format_time_interval(). With bug 13393.
15107 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15108 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15109 tests (visible) fixes in bug 13476.
15110 - Add a "coverage-html" make target to generate HTML-visualized
15111 coverage results when building with --enable-coverage. (Requires
15112 lcov.) Patch from Kevin Murray.
15113 - Enable the backtrace handler (where supported) when running the
15115 - Revise all unit tests that used the legacy test_* macros to
15116 instead use the recommended tt_* macros. This patch was generated
15117 with coccinelle, to avoid manual errors. Closes ticket 13119.
15119 o Distribution (systemd):
15120 - systemd unit file: only allow tor to write to /var/lib/tor and
15121 /var/log/tor. The rest of the filesystem is accessible for reading
15122 only. Patch by intrigeri; resolves ticket 12751.
15123 - systemd unit file: ensure that the process and all its children
15124 can never gain new privileges. Patch by intrigeri; resolves
15126 - systemd unit file: set up /var/run/tor as writable for the Tor
15127 service. Patch by intrigeri; resolves ticket 13196.
15129 o Removed features (directory authorities):
15130 - Remove code that prevented authorities from listing Tor relays
15131 affected by CVE-2011-2769 as guards. These relays are already
15132 rejected altogether due to the minimum version requirement of
15133 0.2.3.16-alpha. Closes ticket 13152.
15134 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15135 the fingerprints file (approved-routers) has been deprecated.
15136 - Directory authorities do not support being Naming dirauths anymore.
15137 The "NamingAuthoritativeDir" config option is now obsolete.
15138 - Directory authorities do not support giving out the BadDirectory
15140 - Directory authorities no longer advertise or support consensus
15141 methods 1 through 12 inclusive. These consensus methods were
15142 obsolete and/or insecure: maintaining the ability to support them
15143 served no good purpose. Implements part of proposal 215; closes
15146 o Testing (test-network.sh):
15147 - Stop using "echo -n", as some shells' built-in echo doesn't
15148 support "-n". Instead, use "/bin/echo -n". Partially fixes
15150 - Stop an apparent test-network hang when used with make -j2. Fixes
15152 - Add a --delay option to test-network.sh, which configures the
15153 delay before the chutney network tests for data transmission.
15154 Partially implements ticket 13161.
15157 Changes in version 0.2.5.10 - 2014-10-24
15158 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15160 It adds several new security features, including improved
15161 denial-of-service resistance for relays, new compiler hardening
15162 options, and a system-call sandbox for hardened installations on Linux
15163 (requires seccomp2). The controller protocol has several new features,
15164 resolving IPv6 addresses should work better than before, and relays
15165 should be a little more CPU-efficient. We've added support for more
15166 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15167 system and testing infrastructure to allow unit testing of more parts
15168 of the Tor codebase. Finally, we've addressed several nagging pluggable
15169 transport usability issues, and included numerous other small bugfixes
15170 and features mentioned below.
15172 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15173 have accumulated many known flaws; everyone should upgrade.
15175 o Deprecated versions:
15176 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15177 attention for some while.
15180 Changes in version 0.2.5.9-rc - 2014-10-20
15181 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
15182 series. It disables SSL3 in response to the recent "POODLE" attack
15183 (even though POODLE does not affect Tor). It also works around a crash
15184 bug caused by some operating systems' response to the "POODLE" attack
15185 (which does affect Tor). It also contains a few miscellaneous fixes.
15187 o Major security fixes:
15188 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15189 today support TLS 1.0 or later, so we can safely turn off support
15190 for this old (and insecure) protocol. Fixes bug 13426.
15192 o Major bugfixes (openssl bug workaround):
15193 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15194 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15195 13471. This is a workaround for an OpenSSL bug.
15198 - Disable the sandbox name resolver cache when running tor-resolve:
15199 tor-resolve doesn't use the sandbox code, and turning it on was
15200 breaking attempts to do tor-resolve on a non-default server on
15201 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
15203 o Compilation fixes:
15204 - Build and run correctly on systems like OpenBSD-current that have
15205 patched OpenSSL to remove get_cipher_by_char and/or its
15206 implementations. Fixes issue 13325.
15208 o Downgraded warnings:
15209 - Downgrade the severity of the 'unexpected sendme cell from client'
15210 from 'warn' to 'protocol warning'. Closes ticket 8093.
15213 Changes in version 0.2.4.25 - 2014-10-20
15214 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
15215 (even though POODLE does not affect Tor). It also works around a crash
15216 bug caused by some operating systems' response to the "POODLE" attack
15217 (which does affect Tor).
15219 o Major security fixes (also in 0.2.5.9-rc):
15220 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15221 today support TLS 1.0 or later, so we can safely turn off support
15222 for this old (and insecure) protocol. Fixes bug 13426.
15224 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
15225 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15226 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15227 13471. This is a workaround for an OpenSSL bug.
15230 Changes in version 0.2.5.8-rc - 2014-09-22
15231 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
15232 series. It fixes a bug that affects consistency and speed when
15233 connecting to hidden services, and it updates the location of one of
15234 the directory authorities.
15237 - Clients now send the correct address for their chosen rendezvous
15238 point when trying to access a hidden service. They used to send
15239 the wrong address, which would still work some of the time because
15240 they also sent the identity digest of the rendezvous point, and if
15241 the hidden service happened to try connecting to the rendezvous
15242 point from a relay that already had a connection open to it,
15243 the relay would reuse that connection. Now connections to hidden
15244 services should be more robust and faster. Also, this bug meant
15245 that clients were leaking to the hidden service whether they were
15246 on a little-endian (common) or big-endian (rare) system, which for
15247 some users might have reduced their anonymity. Fixes bug 13151;
15248 bugfix on 0.2.1.5-alpha.
15250 o Directory authority changes:
15251 - Change IP address for gabelmoo (v3 directory authority).
15254 Changes in version 0.2.4.24 - 2014-09-22
15255 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
15256 connecting to hidden services, and it updates the location of one of
15257 the directory authorities.
15260 - Clients now send the correct address for their chosen rendezvous
15261 point when trying to access a hidden service. They used to send
15262 the wrong address, which would still work some of the time because
15263 they also sent the identity digest of the rendezvous point, and if
15264 the hidden service happened to try connecting to the rendezvous
15265 point from a relay that already had a connection open to it,
15266 the relay would reuse that connection. Now connections to hidden
15267 services should be more robust and faster. Also, this bug meant
15268 that clients were leaking to the hidden service whether they were
15269 on a little-endian (common) or big-endian (rare) system, which for
15270 some users might have reduced their anonymity. Fixes bug 13151;
15271 bugfix on 0.2.1.5-alpha.
15273 o Directory authority changes:
15274 - Change IP address for gabelmoo (v3 directory authority).
15276 o Minor features (geoip):
15277 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15281 Changes in version 0.2.5.7-rc - 2014-09-11
15282 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
15283 release series, and some long-standing bugs related to ORPort reachability
15284 testing and failure to send CREATE cells. It is the first release
15285 candidate for the Tor 0.2.5.x series.
15287 o Major bugfixes (client, startup):
15288 - Start making circuits as soon as DisabledNetwork is turned off.
15289 When Tor started with DisabledNetwork set, it would correctly
15290 conclude that it shouldn't build circuits, but it would mistakenly
15291 cache this conclusion, and continue believing it even when
15292 DisableNetwork is set to 0. Fixes the bug introduced by the fix
15293 for bug 11200; bugfix on 0.2.5.4-alpha.
15294 - Resume expanding abbreviations for command-line options. The fix
15295 for bug 4647 accidentally removed our hack from bug 586 that
15296 rewrote HashedControlPassword to __HashedControlSessionPassword
15297 when it appears on the commandline (which allowed the user to set
15298 her own HashedControlPassword in the torrc file while the
15299 controller generates a fresh session password for each run). Fixes
15300 bug 12948; bugfix on 0.2.5.1-alpha.
15301 - Warn about attempts to run hidden services and relays in the same
15302 process: that's probably not a good idea. Closes ticket 12908.
15304 o Major bugfixes (relay):
15305 - Avoid queuing or sending destroy cells for circuit ID zero when we
15306 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15307 Found and fixed by "cypherpunks".
15308 - Fix ORPort reachability detection on relays running behind a
15309 proxy, by correctly updating the "local" mark on the controlling
15310 channel when changing the address of an or_connection_t after the
15311 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15313 o Minor features (bridge):
15314 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15315 cookie file for the ExtORPort g+r by default.
15317 o Minor features (geoip):
15318 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15321 o Minor bugfixes (logging):
15322 - Reduce the log severity of the "Pluggable transport proxy does not
15323 provide any needed transports and will not be launched." message,
15324 since Tor Browser includes several ClientTransportPlugin lines in
15325 its torrc-defaults file, leading every Tor Browser user who looks
15326 at her logs to see these notices and wonder if they're dangerous.
15327 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
15328 - Downgrade "Unexpected onionskin length after decryption" warning
15329 to a protocol-warn, since there's nothing relay operators can do
15330 about a client that sends them a malformed create cell. Resolves
15331 bug 12996; bugfix on 0.0.6rc1.
15332 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15333 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15334 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15335 their names correctly. Fixes part of bug 12700; bugfix
15337 - When logging information about a relay cell whose command we don't
15338 recognize, log its command as an integer. Fixes part of bug 12700;
15339 bugfix on 0.2.1.10-alpha.
15340 - Escape all strings from the directory connection before logging
15341 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
15343 o Minor bugfixes (controller):
15344 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
15345 bug 12864; bugfix on 0.2.5.1-alpha.
15346 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
15347 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
15350 o Minor bugfixes (compilation):
15351 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
15352 bugfix on 0.2.5.5-alpha.
15353 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
15354 0.2.5.1-alpha. Patch from "NewEraCracker".
15355 - In routerlist_assert_ok(), don't take the address of a
15356 routerinfo's cache_info member unless that routerinfo is non-NULL.
15357 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15358 - Fix a large number of false positive warnings from the clang
15359 analyzer static analysis tool. This should make real warnings
15360 easier for clang analyzer to find. Patch from "teor". Closes
15363 o Distribution (systemd):
15364 - Verify configuration file via ExecStartPre in the systemd unit
15365 file. Patch from intrigeri; resolves ticket 12730.
15366 - Explicitly disable RunAsDaemon in the systemd unit file. Our
15367 current systemd unit uses "Type = simple", so systemd does not
15368 expect tor to fork. If the user has "RunAsDaemon 1" in their
15369 torrc, then things won't work as expected. This is e.g. the case
15370 on Debian (and derivatives), since there we pass "--defaults-torrc
15371 /usr/share/tor/tor-service-defaults-torrc" (that contains
15372 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
15376 - Adjust the URLs in the README to refer to the new locations of
15377 several documents on the website. Fixes bug 12830. Patch from
15379 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
15383 Changes in version 0.2.5.6-alpha - 2014-07-28
15384 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
15385 risk from guard rotation, and fixes a variety of other issues to get
15386 us closer to a release candidate.
15388 o Major features (also in 0.2.4.23):
15389 - Make the number of entry guards configurable via a new
15390 NumEntryGuards consensus parameter, and the number of directory
15391 guards configurable via a new NumDirectoryGuards consensus
15392 parameter. Implements ticket 12688.
15394 o Major bugfixes (also in 0.2.4.23):
15395 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15396 implementation that caused incorrect results on 32-bit
15397 implementations when certain malformed inputs were used along with
15398 a small class of private ntor keys. This bug does not currently
15399 appear to allow an attacker to learn private keys or impersonate a
15400 Tor server, but it could provide a means to distinguish 32-bit Tor
15401 implementations from 64-bit Tor implementations. Fixes bug 12694;
15402 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15406 - Perform circuit cleanup operations even when circuit
15407 construction operations are disabled (because the network is
15408 disabled, or because there isn't enough directory information).
15409 Previously, when we were not building predictive circuits, we
15410 were not closing expired circuits either. Fixes bug 8387; bugfix on
15411 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15412 became more strict about when we have "enough directory information
15413 to build circuits".
15416 - Authorities now assign the Guard flag to the fastest 25% of the
15417 network (it used to be the fastest 50%). Also raise the consensus
15418 weight that guarantees the Guard flag from 250 to 2000. For the
15419 current network, this results in about 1100 guards, down from 2500.
15420 This step paves the way for moving the number of entry guards
15421 down to 1 (proposal 236) while still providing reasonable expected
15422 performance for most users. Implements ticket 12690.
15423 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15425 - Slightly enhance the diagnostic message for bug 12184.
15427 o Minor bugfixes (also in 0.2.4.23):
15428 - Warn and drop the circuit if we receive an inbound 'relay early'
15429 cell. Those used to be normal to receive on hidden service circuits
15430 due to bug 1038, but the buggy Tor versions are long gone from
15431 the network so we can afford to resume watching for them. Resolves
15432 the rest of bug 1038; bugfix on 0.2.1.19.
15433 - Correct a confusing error message when trying to extend a circuit
15434 via the control protocol but we don't know a descriptor or
15435 microdescriptor for one of the specified relays. Fixes bug 12718;
15436 bugfix on 0.2.3.1-alpha.
15439 - Fix compilation when building with bufferevents enabled. (This
15440 configuration is still not expected to work, however.)
15441 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
15442 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
15444 - Compile correctly with builds and forks of OpenSSL (such as
15445 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15446 0.2.1.1-alpha. Patch from "dhill".
15449 Changes in version 0.2.4.23 - 2014-07-28
15450 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
15451 guard rotation, and also backports several important fixes from the
15452 Tor 0.2.5 alpha release series.
15455 - Clients now look at the "usecreatefast" consensus parameter to
15456 decide whether to use CREATE_FAST or CREATE cells for the first hop
15457 of their circuit. This approach can improve security on connections
15458 where Tor's circuit handshake is stronger than the available TLS
15459 connection security levels, but the tradeoff is more computational
15460 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15461 - Make the number of entry guards configurable via a new
15462 NumEntryGuards consensus parameter, and the number of directory
15463 guards configurable via a new NumDirectoryGuards consensus
15464 parameter. Implements ticket 12688.
15467 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15468 implementation that caused incorrect results on 32-bit
15469 implementations when certain malformed inputs were used along with
15470 a small class of private ntor keys. This bug does not currently
15471 appear to allow an attacker to learn private keys or impersonate a
15472 Tor server, but it could provide a means to distinguish 32-bit Tor
15473 implementations from 64-bit Tor implementations. Fixes bug 12694;
15474 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
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.
15487 - Avoid an illegal read from stack when initializing the TLS
15488 module using a version of OpenSSL without all of the ciphers
15489 used by the v2 link handshake. Fixes bug 12227; bugfix on
15490 0.2.4.8-alpha. Found by "starlight".
15493 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15497 Changes in version 0.2.5.5-alpha - 2014-06-18
15498 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
15499 0.2.5.x release series, including a couple of DoS issues, some
15500 performance regressions, a large number of bugs affecting the Linux
15501 seccomp2 sandbox code, and various other bugfixes. It also adds
15502 diagnostic bugfixes for a few tricky issues that we're trying to
15505 o Major features (security, traffic analysis resistance):
15506 - Several major improvements to the algorithm used to decide when to
15507 close TLS connections. Previous versions of Tor closed connections
15508 at a fixed interval after the last time a non-padding cell was
15509 sent over the connection, regardless of the target of the
15510 connection. Now, we randomize the intervals by adding up to 50% of
15511 their base value, we measure the length of time since connection
15512 last had at least one circuit, and we allow connections to known
15513 ORs to remain open a little longer (15 minutes instead of 3
15514 minutes minimum). These changes should improve Tor's resistance
15515 against some kinds of traffic analysis, and lower some overhead
15516 from needlessly closed connections. Fixes ticket 6799.
15517 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
15519 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
15520 - Fix a memory leak that could occur if a microdescriptor parse
15521 fails during the tokenizing step. This bug could enable a memory
15522 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15525 o Major bugfixes (security, directory authorities):
15526 - Directory authorities now include a digest of each relay's
15527 identity key as a part of its microdescriptor.
15529 This is a workaround for bug 11743 (reported by "cypherpunks"),
15530 where Tor clients do not support receiving multiple
15531 microdescriptors with the same SHA256 digest in the same
15532 consensus. When clients receive a consensus like this, they only
15533 use one of the relays. Without this fix, a hostile relay could
15534 selectively disable some client use of target relays by
15535 constructing a router descriptor with a different identity and the
15536 same microdescriptor parameters and getting the authorities to
15537 list it in a microdescriptor consensus. This fix prevents an
15538 attacker from causing a microdescriptor collision, because the
15539 router's identity is not forgeable.
15541 o Major bugfixes (relay):
15542 - Use a direct dirport connection when uploading non-anonymous
15543 descriptors to the directory authorities. Previously, relays would
15544 incorrectly use tunnel connections under a fairly wide variety of
15545 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15546 - When a circuit accidentally has the same circuit ID for its
15547 forward and reverse direction, correctly detect the direction of
15548 cells using that circuit. Previously, this bug made roughly one
15549 circuit in a million non-functional. Fixes bug 12195; this is a
15550 bugfix on every version of Tor.
15552 o Major bugfixes (client, pluggable transports):
15553 - When managing pluggable transports, use OS notification facilities
15554 to learn if they have crashed, and don't attempt to kill any
15555 process that has already exited. Fixes bug 8746; bugfix
15558 o Minor features (diagnostic):
15559 - When logging a warning because of bug 7164, additionally check the
15560 hash table for consistency (as proposed on ticket 11737). This may
15561 help diagnose bug 7164.
15562 - When we log a heartbeat, log how many one-hop circuits we have
15563 that are at least 30 minutes old, and log status information about
15564 a few of them. This is an attempt to track down bug 8387.
15565 - When encountering an unexpected CR while writing text to a file on
15566 Windows, log the name of the file. Should help diagnosing
15568 - Give more specific warnings when a client notices that an onion
15569 handshake has failed. Fixes ticket 9635.
15570 - Add significant new logging code to attempt to diagnose bug 12184,
15571 where relays seem to run out of available circuit IDs.
15572 - Improve the diagnostic log message for bug 8387 even further to
15573 try to improve our odds of figuring out why one-hop directory
15574 circuits sometimes do not get closed.
15576 o Minor features (security, memory management):
15577 - Memory allocation tricks (mempools and buffer freelists) are now
15578 disabled by default. You can turn them back on with
15579 --enable-mempools and --enable-buf-freelists respectively. We're
15580 disabling these features because malloc performance is good enough
15581 on most platforms, and a similar feature in OpenSSL exacerbated
15582 exploitation of the Heartbleed attack. Resolves ticket 11476.
15584 o Minor features (security):
15585 - Apply the secure SipHash-2-4 function to the hash table mapping
15586 circuit IDs and channels to circuits. We missed this one when we
15587 were converting all the other hash functions to use SipHash back
15588 in 0.2.5.3-alpha. Resolves ticket 11750.
15590 o Minor features (build):
15591 - The configure script has a --disable-seccomp option to turn off
15592 support for libseccomp on systems that have it, in case it (or
15593 Tor's use of it) is broken. Resolves ticket 11628.
15595 o Minor features (other):
15596 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15599 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15600 - When running a hidden service, do not allow TunneledDirConns 0;
15601 this will keep the hidden service from running, and also
15602 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15603 bugfix on 0.2.1.1-alpha.
15605 o Minor bugfixes (performance):
15606 - Avoid a bug where every successful connection made us recompute
15607 the flag telling us whether we have sufficient information to
15608 build circuits. Previously, we would forget our cached value
15609 whenever we successfully opened a channel (or marked a router as
15610 running or not running for any other reason), regardless of
15611 whether we had previously believed the router to be running. This
15612 forced us to run an expensive update operation far too often.
15613 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15614 - Avoid using tor_memeq() for checking relay cell integrity. This
15615 removes a possible performance bottleneck. Fixes part of bug
15616 12169; bugfix on 0.2.1.31.
15618 o Minor bugfixes (compilation):
15619 - Fix compilation of test_status.c when building with MVSC. Bugfix
15620 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15621 - Resolve GCC complaints on OpenBSD about discarding constness in
15622 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15623 on 0.1.1.23. Patch from Dana Koch.
15624 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15625 treatment of long and time_t as comparable types. Fixes part of
15626 bug 11633. Patch from Dana Koch.
15627 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15628 11623; bugfix on 0.2.5.3-alpha.
15629 - When deciding whether to build the 64-bit curve25519
15630 implementation, detect platforms where we can compile 128-bit
15631 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15632 0.2.4.8-alpha. Patch from "conradev".
15633 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15634 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15635 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15638 o Minor bugfixes (Directory server):
15639 - When sending a compressed set of descriptors or microdescriptors,
15640 make sure to finalize the zlib stream. Previously, we would write
15641 all the compressed data, but if the last descriptor we wanted to
15642 send was missing or too old, we would not mark the stream as
15643 finished. This caused problems for decompression tools. Fixes bug
15644 11648; bugfix on 0.1.1.23.
15646 o Minor bugfixes (Linux seccomp sandbox):
15647 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15648 11622; bugfix on 0.2.5.1-alpha.
15649 - Avoid crashing when re-opening listener ports with the seccomp
15650 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15651 - Avoid crashing with the seccomp sandbox enabled along with
15652 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15653 - When we receive a SIGHUP with the sandbox enabled, correctly
15654 support rotating our log files. Fixes bug 12032; bugfix
15656 - Avoid crash when running with sandboxing enabled and
15657 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15659 - Fix a "BUG" warning when trying to write bridge-stats files with
15660 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15662 - Prevent the sandbox from crashing on startup when run with the
15663 --enable-expensive-hardening configuration option. Fixes bug
15664 11477; bugfix on 0.2.5.4-alpha.
15665 - When running with DirPortFrontPage and sandboxing both enabled,
15666 reload the DirPortFrontPage correctly when restarting. Fixes bug
15667 12028; bugfix on 0.2.5.1-alpha.
15668 - Don't try to enable the sandbox when using the Tor binary to check
15669 its configuration, hash a passphrase, or so on. Doing so was
15670 crashing on startup for some users. Fixes bug 11609; bugfix
15672 - Avoid warnings when running with sandboxing and node statistics
15673 enabled at the same time. Fixes part of 12064; bugfix on
15674 0.2.5.1-alpha. Patch from Michael Wolf.
15675 - Avoid warnings when running with sandboxing enabled at the same
15676 time as cookie authentication, hidden services, or directory
15677 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15678 - Do not allow options that require calls to exec to be enabled
15679 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15680 bug 12043; bugfix on 0.2.5.1-alpha.
15681 - Handle failures in getpwnam()/getpwuid() when running with the
15682 User option set and the Linux syscall sandbox enabled. Fixes bug
15683 11946; bugfix on 0.2.5.1-alpha.
15684 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15685 to avoid calling getaddrinfo() after installing the sandbox
15686 filters. Previously, it preloaded a cache with the IPv4 address
15687 for our hostname, and nothing else. Now, it loads the cache with
15688 every address that it used to initialize the Tor process. Fixes
15689 bug 11970; bugfix on 0.2.5.1-alpha.
15691 o Minor bugfixes (pluggable transports):
15692 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15693 default location of the authentication token for the extended OR
15694 Port as used by sever-side pluggable transports. We had
15695 implemented this option before, but the code to make it settable
15696 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15697 - Avoid another 60-second delay when starting Tor in a pluggable-
15698 transport-using configuration when we already have cached
15699 descriptors for our bridges. Fixes bug 11965; bugfix
15702 o Minor bugfixes (client):
15703 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15704 when starting a client with bridges configured and DisableNetwork
15705 set. (Tor launcher starts Tor with DisableNetwork set the first
15706 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15708 o Minor bugfixes (testing):
15709 - The Python parts of the test scripts now work on Python 3 as well
15710 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15711 no longer have the tests break. Fixes bug 11608; bugfix
15713 - When looking for versions of python that we could run the tests
15714 with, check for "python2.7" and "python3.3"; previously we were
15715 only looking for "python", "python2", and "python3". Patch from
15716 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15717 - Fix all valgrind warnings produced by the unit tests. There were
15718 over a thousand memory leak warnings previously, mostly produced
15719 by forgetting to free things in the unit test code. Fixes bug
15720 11618, bugfixes on many versions of Tor.
15722 o Minor bugfixes (tor-fw-helper):
15723 - Give a correct log message when tor-fw-helper fails to launch.
15724 (Previously, we would say something like "tor-fw-helper sent us a
15725 string we could not parse".) Fixes bug 9781; bugfix
15728 o Minor bugfixes (relay, threading):
15729 - Check return code on spawn_func() in cpuworker code, so that we
15730 don't think we've spawned a nonworking cpuworker and write junk to
15731 it forever. Fix related to bug 4345; bugfix on all released Tor
15732 versions. Found by "skruffy".
15733 - Use a pthread_attr to make sure that spawn_func() cannot return an
15734 error while at the same time launching a thread. Fix related to
15735 bug 4345; bugfix on all released Tor versions. Reported
15738 o Minor bugfixes (relay, oom prevention):
15739 - Correctly detect the total available system memory. We tried to do
15740 this in 0.2.5.4-alpha, but the code was set up to always return an
15741 error value, even on success. Fixes bug 11805; bugfix
15744 o Minor bugfixes (relay, other):
15745 - We now drop CREATE cells for already-existent circuit IDs and for
15746 zero-valued circuit IDs, regardless of other factors that might
15747 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
15749 - Avoid an illegal read from stack when initializing the TLS module
15750 using a version of OpenSSL without all of the ciphers used by the
15751 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
15753 - When rejecting DATA cells for stream_id zero, still count them
15754 against the circuit's deliver window so that we don't fail to send
15755 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
15757 o Minor bugfixes (logging):
15758 - Fix a misformatted log message about delayed directory fetches.
15759 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
15760 - Squelch a spurious LD_BUG message "No origin circuit for
15761 successful SOCKS stream" in certain hidden service failure cases;
15765 - Include a tor.service file in contrib/dist for use with systemd.
15766 Some distributions will be able to use this file unmodified;
15767 others will need to tweak it, or write their own. Patch from Jamie
15768 Nguyen; resolves ticket 8368.
15771 - Clean up several option names in the manpage to match their real
15772 names, add the missing documentation for a couple of testing and
15773 directory authority options, remove the documentation for a
15774 V2-directory fetching option that no longer exists. Resolves
15776 - Correct the documentation so that it lists the correct directory
15777 for the stats files. (They are in a subdirectory called "stats",
15779 - In the manpage, move more authority-only options into the
15780 directory authority section so that operators of regular directory
15781 caches don't get confused.
15784 - The contrib directory has been sorted and tidied. Before, it was
15785 an unsorted dumping ground for useful and not-so-useful things.
15786 Now, it is divided based on functionality, and the items which
15787 seemed to be nonfunctional or useless have been removed. Resolves
15788 ticket 8966; based on patches from "rl1987".
15791 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
15792 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
15793 - The TunnelDirConns and PreferTunnelledDirConns options no longer
15794 exist; tunneled directory connections have been available since
15795 0.1.2.5-alpha, and turning them off is not a good idea. This is a
15796 brute-force fix for 10849, where "TunnelDirConns 0" would break
15800 Changes in version 0.2.4.22 - 2014-05-16
15801 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
15802 alpha release series. These include blocking all authority signing
15803 keys that may have been affected by the OpenSSL "heartbleed" bug,
15804 choosing a far more secure set of TLS ciphersuites by default, closing
15805 a couple of memory leaks that could be used to run a target relay out
15806 of RAM, and several others.
15808 o Major features (security, backport from 0.2.5.4-alpha):
15809 - Block authority signing keys that were used on authorities
15810 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15811 don't have any evidence that these keys _were_ compromised; we're
15812 doing this to be prudent.) Resolves ticket 11464.
15814 o Major bugfixes (security, OOM):
15815 - Fix a memory leak that could occur if a microdescriptor parse
15816 fails during the tokenizing step. This bug could enable a memory
15817 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15820 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
15821 - The relay ciphersuite list is now generated automatically based on
15822 uniform criteria, and includes all OpenSSL ciphersuites with
15823 acceptable strength and forward secrecy. Previously, we had left
15824 some perfectly fine ciphersuites unsupported due to omission or
15825 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15826 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15827 - Relays now trust themselves to have a better view than clients of
15828 which TLS ciphersuites are better than others. (Thanks to bug
15829 11513, the relay list is now well-considered, whereas the client
15830 list has been chosen mainly for anti-fingerprinting purposes.)
15831 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15832 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15833 AES128. Resolves ticket 11528.
15834 - Clients now try to advertise the same list of ciphersuites as
15835 Firefox 28. This change enables selection of (fast) GCM
15836 ciphersuites, disables some strange old ciphers, and stops
15837 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15838 Resolves ticket 11438.
15840 o Minor bugfixes (configuration, security):
15841 - When running a hidden service, do not allow TunneledDirConns 0:
15842 trying to set that option together with a hidden service would
15843 otherwise prevent the hidden service from running, and also make
15844 it publish its descriptors directly over HTTP. Fixes bug 10849;
15845 bugfix on 0.2.1.1-alpha.
15847 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
15848 - Avoid sending a garbage value to the controller when a circuit is
15849 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15851 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
15852 - Stop leaking memory when we successfully resolve a PTR record.
15853 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15855 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
15856 - Avoid 60-second delays in the bootstrapping process when Tor is
15857 launching for a second time while using bridges. Fixes bug 9229;
15858 bugfix on 0.2.0.3-alpha.
15860 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
15861 - Give the correct URL in the warning message when trying to run a
15862 relay on an ancient version of Windows. Fixes bug 9393.
15864 o Minor bugfixes (compilation):
15865 - Fix a compilation error when compiling with --disable-curve25519.
15866 Fixes bug 9700; bugfix on 0.2.4.17-rc.
15869 - Downgrade the warning severity for the the "md was still
15870 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
15871 for trying to diagnose this bug, and the current warning in
15872 earlier versions of tor achieves nothing useful. Addresses warning
15875 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
15876 - When we run out of usable circuit IDs on a channel, log only one
15877 warning for the whole channel, and describe how many circuits
15878 there were on the channel. Fixes part of ticket 11553.
15880 o Minor features (security, backport from 0.2.5.4-alpha):
15881 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
15882 leave the default at 8GBytes), to better support Raspberry Pi
15883 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
15885 o Documentation (backport from 0.2.5.4-alpha):
15886 - Correctly document that we search for a system torrc file before
15887 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15891 Changes in version 0.2.5.4-alpha - 2014-04-25
15892 Tor 0.2.5.4-alpha includes several security and performance
15893 improvements for clients and relays, including blacklisting authority
15894 signing keys that were used while susceptible to the OpenSSL
15895 "heartbleed" bug, fixing two expensive functions on busy relays,
15896 improved TLS ciphersuite preference lists, support for run-time
15897 hardening on compilers that support AddressSanitizer, and more work on
15898 the Linux sandbox code.
15900 There are also several usability fixes for clients (especially clients
15901 that use bridges), two new TransPort protocols supported (one on
15902 OpenBSD, one on FreeBSD), and various other bugfixes.
15904 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
15905 have accumulated many known flaws; everyone should upgrade.
15907 o Major features (security):
15908 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15909 pick a good value based on your total system memory. Previously,
15910 the default was always 8 GB. You can still override the default by
15911 setting MaxMemInQueues yourself. Resolves ticket 11396.
15912 - Block authority signing keys that were used on authorities
15913 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15914 don't have any evidence that these keys _were_ compromised; we're
15915 doing this to be prudent.) Resolves ticket 11464.
15917 o Major features (relay performance):
15918 - Speed up server-side lookups of rendezvous and introduction point
15919 circuits by using hashtables instead of linear searches. These
15920 functions previously accounted between 3 and 7% of CPU usage on
15921 some busy relays. Resolves ticket 9841.
15922 - Avoid wasting CPU when extending a circuit over a channel that is
15923 nearly out of circuit IDs. Previously, we would do a linear scan
15924 over possible circuit IDs before finding one or deciding that we
15925 had exhausted our possibilities. Now, we try at most 64 random
15926 circuit IDs before deciding that we probably won't succeed. Fixes
15927 a possible root cause of ticket 11553.
15929 o Major features (seccomp2 sandbox, Linux only):
15930 - The seccomp2 sandbox can now run a test network for multiple hours
15931 without crashing. The sandbox is still experimental, and more bugs
15932 will probably turn up. To try it, enable "Sandbox 1" on a Linux
15933 host. Resolves ticket 11351.
15934 - Strengthen sandbox code: the sandbox can now test the arguments
15935 for rename(), and blocks _sysctl() entirely. Resolves another part
15937 - When the sandbox blocks a system call, it now tries to log a stack
15938 trace before exiting. Resolves ticket 11465.
15940 o Major bugfixes (TLS cipher selection):
15941 - The relay ciphersuite list is now generated automatically based on
15942 uniform criteria, and includes all OpenSSL ciphersuites with
15943 acceptable strength and forward secrecy. Previously, we had left
15944 some perfectly fine ciphersuites unsupported due to omission or
15945 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15946 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15947 - Relays now trust themselves to have a better view than clients of
15948 which TLS ciphersuites are better than others. (Thanks to bug
15949 11513, the relay list is now well-considered, whereas the client
15950 list has been chosen mainly for anti-fingerprinting purposes.)
15951 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15952 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15953 AES128. Resolves ticket 11528.
15954 - Clients now try to advertise the same list of ciphersuites as
15955 Firefox 28. This change enables selection of (fast) GCM
15956 ciphersuites, disables some strange old ciphers, and stops
15957 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15958 Resolves ticket 11438.
15960 o Major bugfixes (bridge client):
15961 - Avoid 60-second delays in the bootstrapping process when Tor is
15962 launching for a second time while using bridges. Fixes bug 9229;
15963 bugfix on 0.2.0.3-alpha.
15965 o Minor features (transparent proxy, *BSD):
15966 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15967 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15968 10267; patch from "yurivict".
15969 - Support OpenBSD's divert-to rules with the pf firewall for
15970 transparent proxy ports. To enable it, set "TransProxyType
15971 pf-divert". This allows Tor to run a TransPort transparent proxy
15972 port on OpenBSD 4.4 or later without root privileges. See the
15973 pf.conf(5) manual page for information on configuring pf to use
15974 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15976 o Minor features (security):
15977 - New --enable-expensive-hardening option to enable security
15978 hardening options that consume nontrivial amounts of CPU and
15979 memory. Right now, this includes AddressSanitizer and UbSan, which
15980 are supported in newer versions of GCC and Clang. Closes ticket
15983 o Minor features (log verbosity):
15984 - Demote the message that we give when a flushing connection times
15985 out for too long from NOTICE to INFO. It was usually meaningless.
15986 Resolves ticket 5286.
15987 - Don't log so many notice-level bootstrapping messages at startup
15988 about downloading descriptors. Previously, we'd log a notice
15989 whenever we learned about more routers. Now, we only log a notice
15990 at every 5% of progress. Fixes bug 9963.
15991 - Warn less verbosely when receiving a malformed
15992 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15993 - When we run out of usable circuit IDs on a channel, log only one
15994 warning for the whole channel, and describe how many circuits
15995 there were on the channel. Fixes part of ticket 11553.
15997 o Minor features (relay):
15998 - If a circuit timed out for at least 3 minutes, check if we have a
15999 new external IP address, and publish a new descriptor with the new
16000 IP address if it changed. Resolves ticket 2454.
16002 o Minor features (controller):
16003 - Make the entire exit policy available from the control port via
16004 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16006 - Because of the fix for ticket 11396, the real limit for memory
16007 usage may no longer match the configured MaxMemInQueues value. The
16008 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16010 o Minor features (bridge client):
16011 - Report a more useful failure message when we can't connect to a
16012 bridge because we don't have the right pluggable transport
16013 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16015 o Minor features (diagnostic):
16016 - Add more log messages to diagnose bug 7164, which causes
16017 intermittent "microdesc_free() called but md was still referenced"
16018 warnings. We now include more information, to figure out why we
16019 might be cleaning a microdescriptor for being too old if it's
16020 still referenced by a live node_t object.
16022 o Minor bugfixes (client, DNSPort):
16023 - When using DNSPort, try to respond to AAAA requests with AAAA
16024 answers. Previously, we hadn't looked at the request type when
16025 deciding which answer type to prefer. Fixes bug 10468; bugfix on
16027 - When receiving a DNS query for an unsupported record type, reply
16028 with no answer rather than with a NOTIMPL error. This behavior
16029 isn't correct either, but it will break fewer client programs, we
16030 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
16033 o Minor bugfixes (exit relay):
16034 - Stop leaking memory when we successfully resolve a PTR record.
16035 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16037 o Minor bugfixes (bridge client):
16038 - Stop accepting bridge lines containing hostnames. Doing so would
16039 cause clients to perform DNS requests on the hostnames, which was
16040 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
16041 - Avoid a 60-second delay in the bootstrapping process when a Tor
16042 client with pluggable transports re-reads its configuration at
16043 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
16045 o Minor bugfixes (client, logging during bootstrap):
16046 - Warn only once if we start logging in an unsafe way. Previously,
16047 we complain as many times as we had problems. Fixes bug 9870;
16048 bugfix on 0.2.5.1-alpha.
16049 - Only report the first fatal bootstrap error on a given OR
16050 connection. This stops us from telling the controller bogus error
16051 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
16052 - Be more helpful when trying to run sandboxed on Linux without
16053 libseccomp. Instead of saying "Sandbox is not implemented on this
16054 platform", we now explain that we need to be built with
16055 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
16056 - Avoid generating spurious warnings when starting with
16057 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
16060 o Minor bugfixes (closing OR connections):
16061 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
16062 check if it's an or_connection_t and correctly call
16063 connection_or_close_for_error() rather than
16064 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
16066 - When closing all connections on setting DisableNetwork to 1, use
16067 connection_or_close_normally() rather than closing OR connections
16068 out from under the channel layer. Fixes bug 11306; bugfix on
16071 o Minor bugfixes (controller):
16072 - Avoid sending a garbage value to the controller when a circuit is
16073 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16075 o Minor bugfixes (tor-fw-helper):
16076 - Allow tor-fw-helper to build again by adding src/ext to its
16077 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
16079 o Minor bugfixes (bridges):
16080 - Avoid potential crashes or bad behavior when launching a
16081 server-side managed proxy with ORPort or ExtORPort temporarily
16082 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
16084 o Minor bugfixes (platform-specific):
16085 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
16086 bug 11426; bugfix on 0.2.5.3-alpha.
16087 - When dumping a malformed directory object to disk, save it in
16088 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16090 - Don't report failures from make_socket_reuseable() on incoming
16091 sockets on OSX: this can happen when incoming connections close
16092 early. Fixes bug 10081.
16094 o Minor bugfixes (trivial memory leaks):
16095 - Fix a small memory leak when signing a directory object. Fixes bug
16096 11275; bugfix on 0.2.4.13-alpha.
16097 - Free placeholder entries in our circuit table at exit; fixes a
16098 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
16099 - Don't re-initialize a second set of OpenSSL mutexes when starting
16100 up. Previously, we'd make one set of mutexes, and then immediately
16101 replace them with another. Fixes bug 11726; bugfix on
16103 - Resolve some memory leaks found by coverity in the unit tests, on
16104 exit in tor-gencert, and on a failure to compute digests for our
16105 own keys when generating a v3 networkstatus vote. These leaks
16106 should never have affected anyone in practice.
16108 o Minor bugfixes (hidden service):
16109 - Only retry attempts to connect to a chosen rendezvous point 8
16110 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
16112 o Minor bugfixes (misc code correctness):
16113 - Fix various instances of undefined behavior in channeltls.c,
16114 tor_memmem(), and eventdns.c that would cause us to construct
16115 pointers to memory outside an allocated object. (These invalid
16116 pointers were not accessed, but C does not even allow them to
16117 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16118 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16119 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16120 fix some miscellaneous errors in our tests and codebase. Fixes bug
16121 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16122 - Always check return values for unlink, munmap, UnmapViewOfFile;
16123 check strftime return values more often. In some cases all we can
16124 do is report a warning, but this may help prevent deeper bugs from
16125 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16127 - Fix numerous warnings from the clang "scan-build" static analyzer.
16128 Some of these are programming style issues; some of them are false
16129 positives that indicated awkward code; some are undefined behavior
16130 cases related to constructing (but not using) invalid pointers;
16131 some are assumptions about API behavior; some are (harmlessly)
16132 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16133 correct; and one or two are genuine bugs that weren't reachable
16134 from the rest of the program. Fixes bug 8793; bugfixes on many,
16138 - Build the torify.1 manpage again. Previously, we were only trying
16139 to build it when also building tor-fw-helper. That's why we didn't
16140 notice that we'd broken the ability to build it. Fixes bug 11321;
16141 bugfix on 0.2.5.1-alpha.
16142 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16143 11061; bugfix on 0.2.4.7-alpha.
16144 - Correctly document that we search for a system torrc file before
16145 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16147 - Resolve warnings from Doxygen.
16149 o Code simplifications and refactoring:
16150 - Remove is_internal_IP() function. Resolves ticket 4645.
16151 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16152 Closes issue 9107; patch from "marek".
16153 - Change our use of the ENUM_BF macro to avoid declarations that
16156 o Deprecated versions:
16157 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
16158 attention for some while. Directory authorities no longer accept
16159 descriptors from relays running any version of Tor prior to Tor
16160 0.2.3.16-alpha. Resolves ticket 11149.
16163 - New macros in test.h to simplify writing mock-functions for unit
16164 tests. Part of ticket 11507. Patch from Dana Koch.
16165 - Complete tests for the status.c module. Resolves ticket 11507.
16166 Patch from Dana Koch.
16169 - Remove all code for the long unused v1 directory protocol.
16170 Resolves ticket 11070.
16173 Changes in version 0.2.5.3-alpha - 2014-03-22
16174 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
16175 two new anti-DoS features for Tor relays, resolves a bug that kept
16176 SOCKS5 support for IPv6 from working, fixes several annoying usability
16177 issues for bridge users, and removes more old code for unused
16180 The Tor 0.2.5.x release series is now in patch-freeze: no feature
16181 patches not already written will be considered for inclusion in 0.2.5.x.
16183 o Major features (relay security, DoS-resistance):
16184 - When deciding whether we have run out of memory and we need to
16185 close circuits, also consider memory allocated in buffers for
16186 streams attached to each circuit.
16188 This change, which extends an anti-DoS feature introduced in
16189 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16190 better resist more memory-based DoS attacks than before. Since the
16191 MaxMemInCellQueues option now applies to all queues, it is renamed
16192 to MaxMemInQueues. This feature fixes bug 10169.
16193 - Avoid hash-flooding denial-of-service attacks by using the secure
16194 SipHash-2-4 hash function for our hashtables. Without this
16195 feature, an attacker could degrade performance of a targeted
16196 client or server by flooding their data structures with a large
16197 number of entries to be stored at the same hash table position,
16198 thereby slowing down the Tor instance. With this feature, hash
16199 table positions are derived from a randomized cryptographic key,
16200 and an attacker cannot predict which entries will collide. Closes
16202 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
16203 the default at 8GBytes), to better support Raspberry Pi users. Fixes
16204 bug 9686; bugfix on 0.2.4.14-alpha.
16206 o Minor features (bridges, pluggable transports):
16207 - Bridges now write the SHA1 digest of their identity key
16208 fingerprint (that is, a hash of a hash of their public key) to
16209 notice-level logs, and to a new hashed-fingerprint file. This
16210 information will help bridge operators look up their bridge in
16211 Globe and similar tools. Resolves ticket 10884.
16212 - Improve the message that Tor displays when running as a bridge
16213 using pluggable transports without an Extended ORPort listener.
16214 Also, log the message in the log file too. Resolves ticket 11043.
16216 o Minor features (other):
16217 - Add a new option, PredictedPortsRelevanceTime, to control how long
16218 after having received a request to connect to a given port Tor
16219 will try to keep circuits ready in anticipation of future requests
16220 for that port. Patch from "unixninja92"; implements ticket 9176.
16221 - Generate a warning if any ports are listed in the SocksPolicy,
16222 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16223 AuthDirBadExit options. (These options only support address
16224 ranges.) Fixes part of ticket 11108.
16225 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
16228 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
16229 - Build without warnings under clang 3.4. (We have some macros that
16230 define static functions only some of which will get used later in
16231 the module. Starting with clang 3.4, these give a warning unless the
16232 unused attribute is set on them.) Resolves ticket 10904.
16233 - Fix build warnings about missing "a2x" comment when building the
16234 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16235 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16237 o Minor bugfixes (client):
16238 - Improve the log message when we can't connect to a hidden service
16239 because all of the hidden service directory nodes hosting its
16240 descriptor are excluded. Improves on our fix for bug 10722, which
16241 was a bugfix on 0.2.0.10-alpha.
16242 - Raise a control port warning when we fail to connect to all of
16243 our bridges. Previously, we didn't inform the controller, and
16244 the bootstrap process would stall. Fixes bug 11069; bugfix on
16246 - Exit immediately when a process-owning controller exits.
16247 Previously, tor relays would wait for a little while after their
16248 controller exited, as if they had gotten an INT signal -- but this
16249 was problematic, since there was no feedback for the user. To do a
16250 clean shutdown, controllers should send an INT signal and give Tor
16251 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16252 - Stop attempting to connect to bridges before our pluggable
16253 transports are configured (harmless but resulted in some erroneous
16254 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16255 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16256 generating incorrect SOCKS5 responses, and confusing client
16257 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16259 o Minor bugfixes (relays and bridges):
16260 - Avoid crashing on a malformed resolv.conf file when running a
16261 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16262 - Non-exit relays no longer launch mock DNS requests to check for
16263 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16264 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16265 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16266 - Bridges now report complete directory request statistics. Related
16267 to bug 5824; bugfix on 0.2.2.1-alpha.
16268 - Bridges now never collect statistics that were designed for
16269 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16270 - Stop giving annoying warning messages when we decide not to launch
16271 a pluggable transport proxy that we don't need (because there are
16272 no bridges configured to use it). Resolves ticket 5018; bugfix
16274 - Give the correct URL in the warning message when trying to run a
16275 relay on an ancient version of Windows. Fixes bug 9393.
16277 o Minor bugfixes (backtrace support):
16278 - Support automatic backtraces on more platforms by using the
16279 "-fasynchronous-unwind-tables" compiler option. This option is
16280 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
16281 is on by default and table generation is not. This doesn't yet
16282 add Windows support; only Linux, OSX, and some BSDs are affected.
16283 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
16284 - Avoid strange behavior if two threads hit failed assertions at the
16285 same time and both try to log backtraces at once. (Previously, if
16286 this had happened, both threads would have stored their intermediate
16287 results in the same buffer, and generated junk outputs.) Reported by
16288 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
16289 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
16290 0.2.5.2-alpha; patch from Nick Hopper.
16292 o Minor bugfixes (unit tests):
16293 - Fix a small bug in the unit tests that might have made the tests
16294 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
16295 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
16298 - Remove all remaining code related to version-0 hidden service
16299 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16300 the rest of bug 10841.
16303 - Document in the manpage that "KBytes" may also be written as
16304 "kilobytes" or "KB", that "Kbits" may also be written as
16305 "kilobits", and so forth. Closes ticket 9222.
16306 - Document that the ClientOnly config option overrides ORPort.
16307 Our old explanation made ClientOnly sound as though it did
16308 nothing at all. Resolves bug 9059.
16309 - Explain that SocksPolicy, DirPolicy, and similar options don't
16310 take port arguments. Fixes the other part of ticket 11108.
16311 - Fix a comment about the rend_server_descriptor_t.protocols field
16312 to more accurately describe its range. Also, make that field
16313 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16314 bugfix on 0.2.1.5-alpha.
16315 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16316 the maximum client name length is 16, not 19. Fixes bug 11118;
16317 bugfix on 0.2.1.6-alpha.
16319 o Code simplifications and refactoring:
16320 - Get rid of router->address, since in all cases it was just the
16321 string representation of router->addr. Resolves ticket 5528.
16323 o Test infrastructure:
16324 - Update to the latest version of tinytest.
16325 - Improve the tinytest implementation of string operation tests so
16326 that comparisons with NULL strings no longer crash the tests; they
16327 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16330 Changes in version 0.2.4.21 - 2014-02-28
16331 Tor 0.2.4.21 further improves security against potential adversaries who
16332 find breaking 1024-bit crypto doable, and backports several stability
16333 and robustness patches from the 0.2.5 branch.
16335 o Major features (client security):
16336 - When we choose a path for a 3-hop circuit, make sure it contains
16337 at least one relay that supports the NTor circuit extension
16338 handshake. Otherwise, there is a chance that we're building
16339 a circuit that's worth attacking by an adversary who finds
16340 breaking 1024-bit crypto doable, and that chance changes the game
16341 theory. Implements ticket 9777.
16344 - Do not treat streams that fail with reason
16345 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16346 since it could also indicate an ENETUNREACH connection error. Fixes
16347 part of bug 10777; bugfix on 0.2.4.8-alpha.
16349 o Code simplification and refactoring:
16350 - Remove data structures which were introduced to implement the
16351 CellStatistics option: they are now redundant with the new timestamp
16352 field in the regular packed_cell_t data structure, which we did
16353 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16356 - Always clear OpenSSL bignums before freeing them -- even bignums
16357 that don't contain secrets. Resolves ticket 10793. Patch by
16359 - Build without warnings under clang 3.4. (We have some macros that
16360 define static functions only some of which will get used later in
16361 the module. Starting with clang 3.4, these give a warning unless the
16362 unused attribute is set on them.) Resolves ticket 10904.
16363 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16364 GeoLite2 Country database.
16367 - Set the listen() backlog limit to the largest actually supported
16368 on the system, not to the value in a header file. Fixes bug 9716;
16369 bugfix on every released Tor.
16370 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16371 exit node as a NOROUTE error, not an INTERNAL error, since they
16372 can apparently happen when trying to connect to the wrong sort
16373 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16374 - Fix build warnings about missing "a2x" comment when building the
16375 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16376 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16377 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16378 not entirely remove it from the connection lists. Fixes bug 9602;
16379 bugfix on 0.2.4.4-alpha.
16380 - Fix a segmentation fault in our benchmark code when running with
16381 Fedora's OpenSSL package, or any other OpenSSL that provides
16382 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16383 - Turn "circuit handshake stats since last time" log messages into a
16384 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16386 o Documentation fixes:
16387 - Document that all but one DirPort entry must have the NoAdvertise
16388 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16391 Changes in version 0.2.5.2-alpha - 2014-02-13
16392 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
16393 like the "poor random number generation" fix and the "building too many
16394 circuits" fix. It also further improves security against potential
16395 adversaries who find breaking 1024-bit crypto doable, and launches
16396 pluggable transports on demand (which gets us closer to integrating
16397 pluggable transport support by default -- not to be confused with Tor
16398 bundles enabling pluggable transports and bridges by default).
16400 o Major features (client security):
16401 - When we choose a path for a 3-hop circuit, make sure it contains
16402 at least one relay that supports the NTor circuit extension
16403 handshake. Otherwise, there is a chance that we're building
16404 a circuit that's worth attacking by an adversary who finds
16405 breaking 1024-bit crypto doable, and that chance changes the game
16406 theory. Implements ticket 9777.
16407 - Clients now look at the "usecreatefast" consensus parameter to
16408 decide whether to use CREATE_FAST or CREATE cells for the first hop
16409 of their circuit. This approach can improve security on connections
16410 where Tor's circuit handshake is stronger than the available TLS
16411 connection security levels, but the tradeoff is more computational
16412 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16414 o Major features (bridges):
16415 - Don't launch pluggable transport proxies if we don't have any
16416 bridges configured that would use them. Now we can list many
16417 pluggable transports, and Tor will dynamically start one when it
16418 hears a bridge address that needs it. Resolves ticket 5018.
16419 - The bridge directory authority now assigns status flags (Stable,
16420 Guard, etc) to bridges based on thresholds calculated over all
16421 Running bridges. Now bridgedb can finally make use of its features
16422 to e.g. include at least one Stable bridge in its answers. Fixes
16425 o Major features (other):
16426 - Extend ORCONN controller event to include an "ID" parameter,
16427 and add four new controller event types CONN_BW, CIRC_BW,
16428 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16429 The new events are emitted in private Tor networks only, with the
16430 goal of being able to better track performance and load during
16431 full-network simulations. Implements proposal 218 and ticket 7359.
16432 - On some platforms (currently: recent OSX versions, glibc-based
16433 platforms that support the ELF format, and a few other
16434 Unix-like operating systems), Tor can now dump stack traces
16435 when a crash occurs or an assertion fails. By default, traces
16436 are dumped to stderr (if possible) and to any logs that are
16437 reporting errors. Implements ticket 9299.
16440 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16441 not entirely remove it from the connection lists. Fixes bug 9602;
16442 bugfix on 0.2.4.4-alpha.
16443 - Do not treat streams that fail with reason
16444 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16445 since it could also indicate an ENETUNREACH connection error. Fixes
16446 part of bug 10777; bugfix on 0.2.4.8-alpha.
16448 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16449 - Do not allow OpenSSL engines to replace the PRNG, even when
16450 HardwareAccel is set. The only default builtin PRNG engine uses
16451 the Intel RDRAND instruction to replace the entire PRNG, and
16452 ignores all attempts to seed it with more entropy. That's
16453 cryptographically stupid: the right response to a new alleged
16454 entropy source is never to discard all previously used entropy
16455 sources. Fixes bug 10402; works around behavior introduced in
16456 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16458 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16459 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16460 - Avoid launching spurious extra circuits when a stream is pending.
16461 This fixes a bug where any circuit that _wasn't_ unusable for new
16462 streams would be treated as if it were, causing extra circuits to
16463 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16465 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16466 - No longer stop reading or writing on cpuworker connections when
16467 our rate limiting buckets go empty. Now we should handle circuit
16468 handshake requests more promptly. Resolves bug 9731.
16469 - Stop trying to bootstrap all our directory information from
16470 only our first guard. Discovered while fixing bug 9946; bugfix
16473 o Minor features (bridges, pluggable transports):
16474 - Add threshold cutoffs to the networkstatus document created by
16475 the Bridge Authority. Fixes bug 1117.
16476 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16477 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16478 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16479 Vidalia set this option for us.) Implements ticket 10297.
16481 o Minor features (security):
16482 - Always clear OpenSSL bignums before freeing them -- even bignums
16483 that don't contain secrets. Resolves ticket 10793. Patch by
16486 o Minor features (config options and command line):
16487 - Add an --allow-missing-torrc commandline option that tells Tor to
16488 run even if the configuration file specified by -f is not available.
16489 Implements ticket 10060.
16490 - Add support for the TPROXY transparent proxying facility on Linux.
16491 See documentation for the new TransProxyType option for more
16492 details. Implementation by "thomo". Closes ticket 10582.
16494 o Minor features (controller):
16495 - Add a new "HS_DESC" controller event that reports activities
16496 related to hidden service descriptors. Resolves ticket 8510.
16497 - New "DROPGUARDS" controller command to forget all current entry
16498 guards. Not recommended for ordinary use, since replacing guards
16499 too frequently makes several attacks easier. Resolves ticket 9934;
16502 o Minor features (build):
16503 - Assume that a user using ./configure --host wants to cross-compile,
16504 and give an error if we cannot find a properly named
16505 tool-chain. Add a --disable-tool-name-check option to proceed
16506 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16507 - If we run ./configure and the compiler recognizes -fstack-protector
16508 but the linker rejects it, warn the user about a potentially missing
16509 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16511 o Minor features (testing):
16512 - If Python is installed, "make check" now runs extra tests beyond
16513 the unit test scripts.
16514 - When bootstrapping a test network, sometimes very few relays get
16515 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16516 specify a set of relays which should be voted Guard regardless of
16517 their uptime or bandwidth. Addresses ticket 9206.
16519 o Minor features (log messages):
16520 - When ServerTransportPlugin is set on a bridge, Tor can write more
16521 useful statistics about bridge use in its extrainfo descriptors,
16522 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16523 log message to inform the user in this case. Resolves ticket 9651.
16524 - When receiving a new controller connection, log the origin address.
16525 Resolves ticket 9698; patch from "sigpipe".
16526 - When logging OpenSSL engine status at startup, log the status of
16527 more engines. Fixes ticket 10043; patch from Joshua Datko.
16528 - Turn "circuit handshake stats since last time" log messages into a
16529 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16531 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16532 - Improve the circuit queue out-of-memory handler. Previously, when
16533 we ran low on memory, we'd close whichever circuits had the most
16534 queued cells. Now, we close those that have the *oldest* queued
16535 cells, on the theory that those are most responsible for us
16536 running low on memory. Based on analysis from a forthcoming paper
16537 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16538 - Generate bootstrapping status update events correctly when fetching
16539 microdescriptors. Fixes bug 9927.
16540 - Update to the October 2 2013 Maxmind GeoLite Country database.
16542 o Minor bugfixes (clients):
16543 - When closing a channel that has already been open, do not close
16544 pending circuits that were waiting to connect to the same relay.
16545 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16548 o Minor bugfixes (relays):
16549 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16550 exit node as a NOROUTE error, not an INTERNAL error, since they
16551 can apparently happen when trying to connect to the wrong sort
16552 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16554 o Minor bugfixes (bridges):
16555 - Fix a bug where the first connection works to a bridge that uses a
16556 pluggable transport with client-side parameters, but we don't send
16557 the client-side parameters on subsequent connections. (We don't
16558 use any pluggable transports with client-side parameters yet,
16559 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16560 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16562 o Minor bugfixes (node selection):
16563 - If ExcludeNodes is set, consider non-excluded hidden service
16564 directory servers before excluded ones. Do not consider excluded
16565 hidden service directory servers at all if StrictNodes is
16566 set. (Previously, we would sometimes decide to connect to those
16567 servers, and then realize before we initiated a connection that
16568 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16569 Reported by "mr-4".
16570 - If we set the ExitNodes option but it doesn't include any nodes
16571 that have the Exit flag, we would choose not to bootstrap. Now we
16572 bootstrap so long as ExitNodes includes nodes which can exit to
16573 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16575 o Minor bugfixes (controller and command-line):
16576 - If changing a config option via "setconf" fails in a recoverable
16577 way, we used to nonetheless write our new control ports to the
16578 file described by the "ControlPortWriteToFile" option. Now we only
16579 write out that file if we successfully switch to the new config
16580 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16581 - When a command-line option such as --version or --help that
16582 ordinarily implies --hush appears on the command line along with
16583 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16584 only if it appeared later on the command line. Fixes bug 9578;
16585 bugfix on 0.2.5.1-alpha.
16587 o Minor bugfixes (code correctness):
16588 - Previously we used two temporary files when writing descriptors to
16589 disk; now we only use one. Fixes bug 1376.
16590 - Remove an erroneous (but impossible and thus harmless) pointer
16591 comparison that would have allowed compilers to skip a bounds
16592 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16593 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16594 - Fix an always-true assertion in pluggable transports code so it
16595 actually checks what it was trying to check. Fixes bug 10046;
16596 bugfix on 0.2.3.9-alpha. Found by "dcb".
16598 o Minor bugfixes (protocol correctness):
16599 - When receiving a VERSIONS cell with an odd number of bytes, close
16600 the connection immediately since the cell is malformed. Fixes bug
16601 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16604 o Minor bugfixes (build):
16605 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16606 turned off (that is, without support for v2 link handshakes). Fixes
16607 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16608 - Fix compilation warnings and startup issues when running with
16609 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16611 - Fix compilation on Solaris 9, which didn't like us having an
16612 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16614 o Minor bugfixes (testing):
16615 - Fix a segmentation fault in our benchmark code when running with
16616 Fedora's OpenSSL package, or any other OpenSSL that provides
16617 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16619 o Minor bugfixes (log messages):
16620 - Fix a bug where clients using bridges would report themselves
16621 as 50% bootstrapped even without a live consensus document.
16622 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16623 - Suppress a warning where, if there's only one directory authority
16624 in the network, we would complain that votes and signatures cannot
16625 be uploaded to other directory authorities. Fixes bug 10842;
16626 bugfix on 0.2.2.26-beta.
16627 - Report bootstrapping progress correctly when we're downloading
16628 microdescriptors. We had updated our "do we have enough microdescs
16629 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16630 (see bug 5956), but we left the bootstrap status event logic at
16631 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16632 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16634 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16635 - Avoid a crash bug when starting with a corrupted microdescriptor
16636 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16637 - If we fail to dump a previously cached microdescriptor to disk, avoid
16638 freeing duplicate data later on. Fixes bug 10423; bugfix on
16639 0.2.4.13-alpha. Spotted by "bobnomnom".
16641 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16642 - Correctly log long IPv6 exit policies, instead of truncating them
16643 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16644 - Our default TLS ecdhe groups were backwards: we meant to be using
16645 P224 for relays (for performance win) and P256 for bridges (since
16646 it is more common in the wild). Instead we had it backwards. After
16647 reconsideration, we decided that the default should be P256 on all
16648 hosts, since its security is probably better, and since P224 is
16649 reportedly used quite little in the wild. Found by "skruffy" on
16650 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16651 - Free directory authority certificate download statuses on exit
16652 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16654 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16655 - If the guard we choose first doesn't answer, we would try the
16656 second guard, but once we connected to the second guard we would
16657 abandon it and retry the first one, slowing down bootstrapping.
16658 The fix is to treat all our initially chosen guards as acceptable
16659 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16660 - Fix an assertion failure that would occur when disabling the
16661 ORPort setting on a running Tor process while accounting was
16662 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16663 - When examining the list of network interfaces to find our address,
16664 do not consider non-running or disabled network interfaces. Fixes
16665 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16666 - Avoid an off-by-one error when checking buffer boundaries when
16667 formatting the exit status of a pluggable transport helper.
16668 This is probably not an exploitable bug, but better safe than
16669 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16672 o Removed code and features:
16673 - Clients now reject any directory authority certificates lacking
16674 a dir-key-crosscert element. These have been included since
16675 0.2.1.9-alpha, so there's no real reason for them to be optional
16676 any longer. Completes proposal 157. Resolves ticket 10162.
16677 - Remove all code that existed to support the v2 directory system,
16678 since there are no longer any v2 directory authorities. Resolves
16680 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16681 options, which were used for designating authorities as "Hidden
16682 service authorities". There has been no use of hidden service
16683 authorities since 0.2.2.1-alpha, when we stopped uploading or
16684 downloading v0 hidden service descriptors. Fixes bug 10881; also
16685 part of a fix for bug 10841.
16687 o Code simplification and refactoring:
16688 - Remove some old fallback code designed to keep Tor clients working
16689 in a network with only two working relays. Elsewhere in the code we
16690 have long since stopped supporting such networks, so there wasn't
16691 much point in keeping it around. Addresses ticket 9926.
16692 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16693 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16694 - Remove data structures which were introduced to implement the
16695 CellStatistics option: they are now redundant with the addition
16696 of a timestamp to the regular packed_cell_t data structure, which
16697 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16700 o Documentation (man page) fixes:
16701 - Update manpage to describe some of the files you can expect to
16702 find in Tor's DataDirectory. Addresses ticket 9839.
16703 - Document that all but one DirPort entry must have the NoAdvertise
16704 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16706 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16707 - Clarify the usage and risks of setting the ContactInfo torrc line
16708 for your relay or bridge. Resolves ticket 9854.
16709 - Add anchors to the manpage so we can link to the html version of
16710 the documentation for specific options. Resolves ticket 9866.
16711 - Replace remaining references to DirServer in man page and
16712 log entries. Resolves ticket 10124.
16715 - Make the "tor-gencert" tool used by directory authority operators
16716 create 2048-bit signing keys by default (rather than 1024-bit, since
16717 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16720 Changes in version 0.2.4.20 - 2013-12-22
16721 Tor 0.2.4.20 fixes potentially poor random number generation for users
16722 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16723 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16724 and 4) have no state file in their DataDirectory (as would happen on
16725 first start). Users who generated relay or hidden service identity
16726 keys in such a situation should discard them and generate new ones.
16728 This release also fixes a logic error that caused Tor clients to build
16729 many more preemptive circuits than they actually need.
16732 - Do not allow OpenSSL engines to replace the PRNG, even when
16733 HardwareAccel is set. The only default builtin PRNG engine uses
16734 the Intel RDRAND instruction to replace the entire PRNG, and
16735 ignores all attempts to seed it with more entropy. That's
16736 cryptographically stupid: the right response to a new alleged
16737 entropy source is never to discard all previously used entropy
16738 sources. Fixes bug 10402; works around behavior introduced in
16739 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16741 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16742 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16743 - Avoid launching spurious extra circuits when a stream is pending.
16744 This fixes a bug where any circuit that _wasn't_ unusable for new
16745 streams would be treated as if it were, causing extra circuits to
16746 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16749 - Avoid a crash bug when starting with a corrupted microdescriptor
16750 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16751 - If we fail to dump a previously cached microdescriptor to disk, avoid
16752 freeing duplicate data later on. Fixes bug 10423; bugfix on
16753 0.2.4.13-alpha. Spotted by "bobnomnom".
16756 Changes in version 0.2.4.19 - 2013-12-11
16757 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16758 (1986-2013). Aaron worked on diverse projects including helping to guide
16759 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16760 transparency to the U.S government's PACER documents, and contributing
16761 design and development for Tor and Tor2Web. Aaron was one of the latest
16762 martyrs in our collective fight for civil liberties and human rights,
16763 and his death is all the more painful because he was one of us.
16765 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16766 a new circuit handshake and link encryption that use ECC to provide
16767 better security and efficiency; makes relays better manage circuit
16768 creation requests; uses "directory guards" to reduce client enumeration
16769 risks; makes bridges collect and report statistics about the pluggable
16770 transports they support; cleans up and improves our geoip database;
16771 gets much closer to IPv6 support for clients, bridges, and relays; makes
16772 directory authorities use measured bandwidths rather than advertised
16773 ones when computing flags and thresholds; disables client-side DNS
16774 caching to reduce tracking risks; and fixes a big bug in bridge
16775 reachability testing. This release introduces two new design
16776 abstractions in the code: a new "channel" abstraction between circuits
16777 and or_connections to allow for implementing alternate relay-to-relay
16778 transports, and a new "circuitmux" abstraction storing the queue of
16779 circuits for a channel. The release also includes many stability,
16780 security, and privacy fixes.
16783 Changes in version 0.2.4.18-rc - 2013-11-16
16784 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
16785 series. It takes a variety of fixes from the 0.2.5.x branch to improve
16786 stability, performance, and better handling of edge cases.
16789 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16790 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16791 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16792 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16793 them to solve bug 6033.)
16796 - No longer stop reading or writing on cpuworker connections when
16797 our rate limiting buckets go empty. Now we should handle circuit
16798 handshake requests more promptly. Resolves bug 9731.
16799 - If we are unable to save a microdescriptor to the journal, do not
16800 drop it from memory and then reattempt downloading it. Fixes bug
16801 9645; bugfix on 0.2.2.6-alpha.
16802 - Stop trying to bootstrap all our directory information from
16803 only our first guard. Discovered while fixing bug 9946; bugfix
16805 - The new channel code sometimes lost track of in-progress circuits,
16806 causing long-running clients to stop building new circuits. The
16807 fix is to always call circuit_n_chan_done(chan, 0) from
16808 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16810 o Minor bugfixes (on 0.2.4.x):
16811 - Correctly log long IPv6 exit policies, instead of truncating them
16812 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16813 - Our default TLS ecdhe groups were backwards: we meant to be using
16814 P224 for relays (for performance win) and P256 for bridges (since
16815 it is more common in the wild). Instead we had it backwards. After
16816 reconsideration, we decided that the default should be P256 on all
16817 hosts, since its security is probably better, and since P224 is
16818 reportedly used quite little in the wild. Found by "skruffy" on
16819 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16820 - Free directory authority certificate download statuses on exit
16821 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16823 o Minor bugfixes (on 0.2.3.x and earlier):
16824 - If the guard we choose first doesn't answer, we would try the
16825 second guard, but once we connected to the second guard we would
16826 abandon it and retry the first one, slowing down bootstrapping.
16827 The fix is to treat all our initially chosen guards as acceptable
16828 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16829 - Fix an assertion failure that would occur when disabling the
16830 ORPort setting on a running Tor process while accounting was
16831 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16832 - When examining the list of network interfaces to find our address,
16833 do not consider non-running or disabled network interfaces. Fixes
16834 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16835 - Avoid an off-by-one error when checking buffer boundaries when
16836 formatting the exit status of a pluggable transport helper.
16837 This is probably not an exploitable bug, but better safe than
16838 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16841 o Minor features (protecting client timestamps):
16842 - Clients no longer send timestamps in their NETINFO cells. These were
16843 not used for anything, and they provided one small way for clients
16844 to be distinguished from each other as they moved from network to
16845 network or behind NAT. Implements part of proposal 222.
16846 - Clients now round timestamps in INTRODUCE cells down to the nearest
16847 10 minutes. If a new Support022HiddenServices option is set to 0, or
16848 if it's set to "auto" and the feature is disabled in the consensus,
16849 the timestamp is sent as 0 instead. Implements part of proposal 222.
16850 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16851 a big deal from a security point of view, but it achieves no actual
16852 good purpose, and isn't needed. Implements part of proposal 222.
16853 - Reduce down accuracy of timestamps in hidden service descriptors.
16854 Implements part of proposal 222.
16856 o Minor features (other):
16857 - Improve the circuit queue out-of-memory handler. Previously, when
16858 we ran low on memory, we'd close whichever circuits had the most
16859 queued cells. Now, we close those that have the *oldest* queued
16860 cells, on the theory that those are most responsible for us
16861 running low on memory. Based on analysis from a forthcoming paper
16862 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16863 - Generate bootstrapping status update events correctly when fetching
16864 microdescriptors. Fixes bug 9927.
16865 - Update to the October 2 2013 Maxmind GeoLite Country database.
16867 o Documentation fixes:
16868 - Clarify the usage and risks of setting the ContactInfo torrc line
16869 for your relay or bridge. Resolves ticket 9854.
16870 - Add anchors to the manpage so we can link to the html version of
16871 the documentation for specific options. Resolves ticket 9866.
16872 - Replace remaining references to DirServer in man page and
16873 log entries. Resolves ticket 10124.
16876 Changes in version 0.2.5.1-alpha - 2013-10-02
16877 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
16878 on Linux, allows bridges that offer pluggable transports to report usage
16879 statistics, fixes many issues to make testing easier, and provides
16880 a pile of minor features and bugfixes that have been waiting for a
16881 release of the new branch.
16883 This is the first alpha release in a new series, so expect there to
16884 be bugs. Users who would rather test out a more stable branch should
16885 stay with 0.2.4.x for now.
16887 o Major features (security):
16888 - Use the seccomp2 syscall filtering facility on Linux to limit
16889 which system calls Tor can invoke. This is an experimental,
16890 Linux-only feature to provide defense-in-depth against unknown
16891 attacks. To try turning it on, set "Sandbox 1" in your torrc
16892 file. Please be ready to report bugs. We hope to add support
16893 for better sandboxing in the future, including more fine-grained
16894 filters, better division of responsibility, and support for more
16895 platforms. This work has been done by Cristian-Matei Toader for
16896 Google Summer of Code.
16897 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16898 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16899 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16900 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16901 them to solve bug 6033.)
16903 o Major features (other):
16904 - Add support for passing arguments to managed pluggable transport
16905 proxies. Implements ticket 3594.
16906 - Bridges now track GeoIP information and the number of their users
16907 even when pluggable transports are in use, and report usage
16908 statistics in their extra-info descriptors. Resolves tickets 4773
16910 - Make testing Tor networks bootstrap better: lower directory fetch
16911 retry schedules and maximum interval without directory requests,
16912 and raise maximum download tries. Implements ticket 6752.
16913 - Add make target 'test-network' to run tests on a Chutney network.
16914 Implements ticket 8530.
16915 - The ntor handshake is now on-by-default, no matter what the
16916 directory authorities recommend. Implements ticket 8561.
16919 - Instead of writing destroy cells directly to outgoing connection
16920 buffers, queue them and intersperse them with other outgoing cells.
16921 This can prevent a set of resource starvation conditions where too
16922 many pending destroy cells prevent data cells from actually getting
16923 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16924 bugfix on 0.2.0.1-alpha.
16925 - If we are unable to save a microdescriptor to the journal, do not
16926 drop it from memory and then reattempt downloading it. Fixes bug
16927 9645; bugfix on 0.2.2.6-alpha.
16928 - The new channel code sometimes lost track of in-progress circuits,
16929 causing long-running clients to stop building new circuits. The
16930 fix is to always call circuit_n_chan_done(chan, 0) from
16931 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16934 - Tor now builds each source file in two modes: a mode that avoids
16935 exposing identifiers needlessly, and another mode that exposes
16936 more identifiers for testing. This lets the compiler do better at
16937 optimizing the production code, while enabling us to take more
16938 radical measures to let the unit tests test things.
16939 - The production builds no longer include functions used only in
16940 the unit tests; all functions exposed from a module only for
16941 unit-testing are now static in production builds.
16942 - Add an --enable-coverage configuration option to make the unit
16943 tests (and a new src/or/tor-cov target) to build with gcov test
16947 - We now have rudimentary function mocking support that our unit
16948 tests can use to test functions in isolation. Function mocking
16949 lets the tests temporarily replace a function's dependencies with
16950 stub functions, so that the tests can check the function without
16951 invoking the other functions it calls.
16952 - Add more unit tests for the <circid,channel>->circuit map, and
16953 the destroy-cell-tracking code to fix bug 7912.
16954 - Unit tests for failing cases of the TAP onion handshake.
16955 - More unit tests for address-manipulation functions.
16957 o Minor features (protecting client timestamps):
16958 - Clients no longer send timestamps in their NETINFO cells. These were
16959 not used for anything, and they provided one small way for clients
16960 to be distinguished from each other as they moved from network to
16961 network or behind NAT. Implements part of proposal 222.
16962 - Clients now round timestamps in INTRODUCE cells down to the nearest
16963 10 minutes. If a new Support022HiddenServices option is set to 0, or
16964 if it's set to "auto" and the feature is disabled in the consensus,
16965 the timestamp is sent as 0 instead. Implements part of proposal 222.
16966 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16967 a big deal from a security point of view, but it achieves no actual
16968 good purpose, and isn't needed. Implements part of proposal 222.
16969 - Reduce down accuracy of timestamps in hidden service descriptors.
16970 Implements part of proposal 222.
16972 o Minor features (config options):
16973 - Config (torrc) lines now handle fingerprints which are missing
16974 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16975 - Support a --dump-config option to print some or all of the
16976 configured options. Mainly useful for debugging the command-line
16977 option parsing code. Helps resolve ticket 4647.
16978 - Raise awareness of safer logging: notify user of potentially
16979 unsafe config options, like logging more verbosely than severity
16980 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16981 - Add a new configuration option TestingV3AuthVotingStartOffset
16982 that bootstraps a network faster by changing the timing for
16983 consensus votes. Addresses ticket 8532.
16984 - Add a new torrc option "ServerTransportOptions" that allows
16985 bridge operators to pass configuration parameters to their
16986 pluggable transports. Resolves ticket 8929.
16987 - The config (torrc) file now accepts bandwidth and space limits in
16988 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16989 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16992 o Minor features (build):
16993 - Add support for `--library-versions` flag. Implements ticket 6384.
16994 - Return the "unexpected sendme" warnings to a warn severity, but make
16995 them rate limited, to help diagnose ticket 8093.
16996 - Detect a missing asciidoc, and warn the user about it, during
16997 configure rather than at build time. Fixes issue 6506. Patch from
17000 o Minor features (other):
17001 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17002 sockets in a single system call. Implements ticket 5129.
17003 - Log current accounting state (bytes sent and received + remaining
17004 time for the current accounting period) in the relay's heartbeat
17005 message. Implements ticket 5526; patch from Peter Retzlaff.
17006 - Implement the TRANSPORT_LAUNCHED control port event that
17007 notifies controllers about new launched pluggable
17008 transports. Resolves ticket 5609.
17009 - If we're using the pure-C 32-bit curve25519_donna implementation
17010 of curve25519, build it with the -fomit-frame-pointer option to
17011 make it go faster on register-starved hosts. This improves our
17012 handshake performance by about 6% on i386 hosts without nacl.
17013 Closes ticket 8109.
17014 - Update to the September 4 2013 Maxmind GeoLite Country database.
17017 - Set the listen() backlog limit to the largest actually supported
17018 on the system, not to the value in a header file. Fixes bug 9716;
17019 bugfix on every released Tor.
17020 - No longer accept malformed http headers when parsing urls from
17021 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17022 bugfix on 0.0.6pre1.
17023 - In munge_extrainfo_into_routerinfo(), check the return value of
17024 memchr(). This would have been a serious issue if we ever passed
17025 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17027 - On the chance that somebody manages to build Tor on a
17028 platform where time_t is unsigned, correct the way that
17029 microdesc_add_to_cache() handles negative time arguments.
17030 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17031 - Reject relative control socket paths and emit a warning. Previously,
17032 single-component control socket paths would be rejected, but Tor
17033 would not log why it could not validate the config. Fixes bug 9258;
17034 bugfix on 0.2.3.16-alpha.
17036 o Minor bugfixes (command line):
17037 - Use a single command-line parser for parsing torrc options on the
17038 command line and for finding special command-line options to avoid
17039 inconsistent behavior for torrc option arguments that have the same
17040 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17042 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17043 9573; bugfix on 0.0.9pre5.
17045 o Minor fixes (build, auxiliary programs):
17046 - Stop preprocessing the "torify" script with autoconf, since
17047 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17049 - The tor-fw-helper program now follows the standard convention and
17050 exits with status code "0" on success. Fixes bug 9030; bugfix on
17051 0.2.3.1-alpha. Patch by Arlo Breault.
17052 - Corrected ./configure advice for what openssl dev package you should
17053 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17055 o Minor code improvements:
17056 - Remove constants and tests for PKCS1 padding; it's insecure and
17057 shouldn't be used for anything new. Fixes bug 8792; patch
17059 - Remove instances of strcpy() from the unit tests. They weren't
17060 hurting anything, since they were only in the unit tests, but it's
17061 embarrassing to have strcpy() in the code at all, and some analysis
17062 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17063 0.2.3.8-alpha. Patch from Arlo Breault.
17065 o Removed features:
17066 - Remove migration code from when we renamed the "cached-routers"
17067 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17068 incidentally resolves ticket 6502 by cleaning up the related code
17069 a bit. Patch from Akshay Hebbar.
17071 o Code simplification and refactoring:
17072 - Extract the common duplicated code for creating a subdirectory
17073 of the data directory and writing to a file in it. Fixes ticket
17074 4282; patch from Peter Retzlaff.
17075 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17076 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17077 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17078 - Add a set of accessor functions for the circuit timeout data
17079 structure. Fixes ticket 6153; patch from "piet".
17080 - Clean up exit paths from connection_listener_new(). Closes ticket
17081 8789. Patch from Arlo Breault.
17082 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17083 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17084 - Use a doubly-linked list to implement the global circuit list.
17085 Resolves ticket 9108. Patch from Marek Majkowski.
17086 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17089 Changes in version 0.2.4.17-rc - 2013-09-05
17090 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
17091 series. It adds an emergency step to help us tolerate the massive
17092 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
17093 circuit-level handshakes now effectively jump the queue compared to
17094 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
17095 big bug hindering bridge reachability tests.
17098 - Relays now process the new "NTor" circuit-level handshake requests
17099 with higher priority than the old "TAP" circuit-level handshake
17100 requests. We still process some TAP requests to not totally starve
17101 0.2.3 clients when NTor becomes popular. A new consensus parameter
17102 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17103 Implements ticket 9574.
17106 - If the circuit build timeout logic is disabled (via the consensus,
17107 or because we are an authority), then don't build testing circuits.
17108 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
17109 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
17110 previously they did not, which prevented them from receiving
17111 successful connections from relays for self-test or bandwidth
17112 testing. Also, when a relay is extending a circuit to a bridge,
17113 it needs to send a NETINFO cell, even when the bridge hasn't sent
17114 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
17115 - If the time to download the next old-style networkstatus is in
17116 the future, do not decline to consider whether to download the
17117 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17121 - Avoid double-closing the listener socket in our socketpair()
17122 replacement (used on Windows) in the case where the addresses on
17123 our opened sockets don't match what we expected. Fixes bug 9400;
17124 bugfix on 0.0.2pre7. Found by Coverity.
17126 o Minor fixes (config options):
17127 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17128 ridiculously high value, by imposing a (ridiculously high) 30-day
17129 maximum on MaxCircuitDirtiness.
17130 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17131 message is logged at notice, not at info.
17132 - Warn and fail if a server is configured not to advertise any
17133 ORPorts at all. (We need *something* to put in our descriptor,
17134 or we just won't work.)
17137 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17138 and how many we complete, and log it every hour to help relay
17139 operators follow trends in network load. Addresses ticket 9658.
17140 - Update to the August 7 2013 Maxmind GeoLite Country database.
17143 Changes in version 0.2.4.16-rc - 2013-08-10
17144 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
17145 series. It fixes several crash bugs in the 0.2.4 branch.
17148 - Fix a bug in the voting algorithm that could yield incorrect results
17149 when a non-naming authority declared too many flags. Fixes bug 9200;
17150 bugfix on 0.2.0.3-alpha.
17151 - Fix an uninitialized read that could in some cases lead to a remote
17152 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
17153 Anybody running a hidden service on the experimental 0.2.4.x
17154 branch should upgrade. (This is, so far as we know, unrelated to
17156 - Avoid an assertion failure when processing DNS replies without the
17157 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
17158 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
17159 0.2.4.15-rc. Found by stem integration tests.
17162 - Fix an invalid memory read that occurred when a pluggable
17163 transport proxy failed its configuration protocol.
17164 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
17165 - When evaluating whether to use a connection that we haven't
17166 decided is canonical using a recent link protocol version,
17167 decide that it's canonical only if it used address _does_
17168 match the desired address. Fixes bug 9309; bugfix on
17169 0.2.4.4-alpha. Reported by skruffy.
17170 - Make the default behavior of NumDirectoryGuards be to track
17171 NumEntryGuards. Now a user who changes only NumEntryGuards will get
17172 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
17173 - Fix a spurious compilation warning with some older versions of
17174 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
17177 - Update to the July 3 2013 Maxmind GeoLite Country database.
17180 Changes in version 0.2.4.15-rc - 2013-07-01
17181 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
17182 series. It fixes a few smaller bugs, but generally appears stable.
17183 Please test it and let us know whether it is!
17186 - When receiving a new configuration file via the control port's
17187 LOADCONF command, do not treat the defaults file as absent.
17188 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17191 - Issue a warning when running with the bufferevents backend enabled.
17192 It's still not stable, and people should know that they're likely
17193 to hit unexpected problems. Closes ticket 9147.
17196 Changes in version 0.2.4.14-alpha - 2013-06-18
17197 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
17198 present in 0.2.4.13-alpha.
17201 - When we have too much memory queued in circuits (according to a new
17202 MaxMemInCellQueues option), close the circuits consuming the most
17203 memory. This prevents us from running out of memory as a relay if
17204 circuits fill up faster than they can be drained. Fixes bug 9063;
17205 bugfix on the 54th commit of Tor. This bug is a further fix beyond
17206 bug 6252, whose fix was merged into 0.2.3.21-rc.
17208 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
17209 where we tried to solve this issue simply by imposing an upper limit
17210 on the number of queued cells for a single circuit. That approach
17211 proved to be problematic, since there are ways to provoke clients to
17212 send a number of cells in excess of any such reasonable limit. Fixes
17213 bug 9072; bugfix on 0.2.4.13-alpha.
17215 - Limit hidden service descriptors to at most ten introduction
17216 points, to slow one kind of guard enumeration. Fixes bug 9002;
17217 bugfix on 0.1.1.11-alpha.
17220 Changes in version 0.2.4.13-alpha - 2013-06-14
17221 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
17222 vulnerabilities, makes socks5 username/password circuit isolation
17223 actually actually work (this time for sure!), and cleans up a bunch
17224 of other issues in preparation for a release candidate.
17226 o Major bugfixes (robustness):
17227 - Close any circuit that has too many cells queued on it. Fixes
17228 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
17229 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
17230 - Prevent the get_freelists() function from running off the end of
17231 the list of freelists if it somehow gets an unrecognized
17232 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17234 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17235 when an exit connection with optimistic data succeeds immediately
17236 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17238 - Fix a directory authority crash bug when building a consensus
17239 using an older consensus as its basis. Fixes bug 8833. Bugfix
17243 - Avoid a memory leak where we would leak a consensus body when we
17244 find that a consensus which we couldn't previously verify due to
17245 missing certificates is now verifiable. Fixes bug 8719; bugfix
17247 - We used to always request authority certificates by identity digest,
17248 meaning we'd get the newest one even when we wanted one with a
17249 different signing key. Then we would complain about being given
17250 a certificate we already had, and never get the one we really
17251 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17252 resource to request the one we want. Fixes bug 5595; bugfix on
17254 - Follow the socks5 protocol when offering username/password
17255 authentication. The fix for bug 8117 exposed this bug, and it
17256 turns out real-world applications like Pidgin do care. Bugfix on
17257 0.2.3.2-alpha; fixes bug 8879.
17258 - Prevent failures on Windows Vista and later when rebuilding the
17259 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
17260 bugfix on 0.2.4.12-alpha.
17263 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17264 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17265 - If for some reason we fail to write a microdescriptor while
17266 rebuilding the cache, do not let the annotations from that
17267 microdescriptor linger in the cache file, and do not let the
17268 microdescriptor stay recorded as present in its old location.
17269 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17270 - Fix a memory leak that would occur whenever a configuration
17271 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17272 - Paste the description for PathBias parameters from the man
17273 page into or.h, so the code documents them too. Fixes bug 7982;
17274 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
17275 - Relays now treat a changed IPv6 ORPort as sufficient reason to
17276 publish an updated descriptor. Fixes bug 6026; bugfix on
17278 - When launching a resolve request on behalf of an AF_UNIX control
17279 socket, omit the address field of the new entry connection, used in
17280 subsequent controller events, rather than letting tor_dup_addr()
17281 set it to "<unknown address type>". Fixes bug 8639; bugfix on
17284 o Minor bugfixes (log messages):
17285 - Fix a scaling issue in the path bias accounting code that
17286 resulted in "Bug:" log messages from either
17287 pathbias_scale_close_rates() or pathbias_count_build_success().
17288 This represents a bugfix on a previous bugfix: the original fix
17289 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
17291 - Give a less useless error message when the user asks for an IPv4
17292 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
17296 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
17297 to tolerate bug 8093 for now.
17298 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17299 in directory authority votes to describe whether they have enough
17300 measured bandwidths to ignore advertised (relay descriptor)
17301 bandwidth claims. Resolves ticket 8711.
17302 - Update to the June 5 2013 Maxmind GeoLite Country database.
17304 o Removed documentation:
17305 - Remove some of the older contents of doc/ as obsolete; move others
17306 to torspec.git. Fixes bug 8965.
17308 o Code simplification and refactoring:
17309 - Avoid using character buffers when constructing most directory
17310 objects: this approach was unwieldy and error-prone. Instead,
17311 build smartlists of strings, and concatenate them when done.
17314 Changes in version 0.2.4.12-alpha - 2013-04-18
17315 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
17316 process for lengthening the guard rotation period, makes directory
17317 authority opinions in the consensus a bit less gameable, makes socks5
17318 username/password circuit isolation actually work, and fixes a wide
17319 variety of other issues.
17322 - Raise the default time that a client keeps an entry guard from
17323 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17324 2012 paper. (We would make it even longer, but we need better client
17325 load balancing first.) Also, make the guard lifetime controllable
17326 via a new GuardLifetime torrc option and a GuardLifetime consensus
17327 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17328 - Directory authorities now prefer using measured bandwidths to
17329 advertised ones when computing flags and thresholds. Resolves
17331 - Directory authorities that have more than a threshold number
17332 of relays with measured bandwidths now treat relays with unmeasured
17333 bandwidths as having bandwidth 0. Resolves ticket 8435.
17335 o Major bugfixes (assert / resource use):
17336 - Avoid a bug where our response to TLS renegotiation under certain
17337 network conditions could lead to a busy-loop, with 100% CPU
17338 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17339 - Avoid an assertion when we discover that we'd like to write a cell
17340 onto a closing connection: just discard the cell. Fixes another
17341 case of bug 7350; bugfix on 0.2.4.4-alpha.
17343 o Major bugfixes (client-side privacy):
17344 - When we mark a circuit as unusable for new circuits, have it
17345 continue to be unusable for new circuits even if MaxCircuitDirtiness
17346 is increased too much at the wrong time, or the system clock jumps
17347 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17348 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17349 which have resolved to internal addresses") is set, apply that
17350 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17351 - When an exit relay rejects a stream with reason "exit policy", but
17352 we only know an exit policy summary (e.g. from the microdesc
17353 consensus) for it, do not mark the relay as useless for all exiting.
17354 Instead, mark just the circuit as unsuitable for that particular
17355 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17356 - Allow applications to get proper stream isolation with
17357 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17358 username/password authentication also offer "no authentication". Tor
17359 had previously preferred "no authentication", so the applications
17360 never actually sent Tor their auth details. Now Tor selects
17361 username/password authentication if it's offered. You can disable
17362 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17363 bug 8117; bugfix on 0.2.3.3-alpha.
17365 o Major bugfixes (other):
17366 - When unable to find any working directory nodes to use as a
17367 directory guard, give up rather than adding the same non-working
17368 nodes to the directory guard list over and over. Fixes bug 8231;
17369 bugfix on 0.2.4.8-alpha.
17372 - Reject as invalid most directory objects containing a NUL.
17373 Belt-and-suspender fix for bug 8037.
17374 - In our testsuite, create temporary directories with a bit more
17375 entropy in their name to make name collisions less likely. Fixes
17377 - Add CACHED keyword to ADDRMAP events in the control protocol
17378 to indicate whether a DNS result will be cached or not. Resolves
17380 - Update to the April 3 2013 Maxmind GeoLite Country database.
17382 o Minor features (build):
17383 - Detect and reject attempts to build Tor with threading support
17384 when OpenSSL has been compiled without threading support.
17386 - Clarify that when autoconf is checking for nacl, it is checking
17387 specifically for nacl with a fast curve25519 implementation.
17389 - Warn if building on a platform with an unsigned time_t: there
17390 are too many places where Tor currently assumes that time_t can
17391 hold negative values. We'd like to fix them all, but probably
17394 o Minor bugfixes (build):
17395 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17396 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17397 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17398 - Add the old src/or/micro-revision.i filename to CLEANFILES.
17399 On the off chance that somebody has one, it will go away as soon
17400 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
17401 - Build Tor correctly on 32-bit platforms where the compiler can build
17402 but not run code using the "uint128_t" construction. Fixes bug 8587;
17403 bugfix on 0.2.4.8-alpha.
17404 - Fix compilation warning with some versions of clang that would
17405 prefer the -Wswitch-enum compiler flag to warn about switch
17406 statements with missing enum values, even if those switch
17407 statements have a "default:" statement. Fixes bug 8598; bugfix
17410 o Minor bugfixes (protocol):
17411 - Fix the handling of a TRUNCATE cell when it arrives while the
17412 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17413 - Fix a misframing issue when reading the version numbers in a
17414 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17415 'version 1, version 2, and version 0x100', when it should have
17416 only included versions 1 and 2. Fixes bug 8059; bugfix on
17417 0.2.0.10-alpha. Reported pseudonymously.
17418 - Make the format and order of STREAM events for DNS lookups
17419 consistent among the various ways to launch DNS lookups. Fixes
17420 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17421 - Correct our check for which versions of Tor support the EXTEND2
17422 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
17423 later, when support was really added in version 0.2.4.8-alpha.
17424 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
17426 o Minor bugfixes (other):
17427 - Correctly store microdescriptors and extrainfo descriptors with
17428 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
17429 Bug reported by "cypherpunks".
17430 - Increase the width of the field used to remember a connection's
17431 link protocol version to two bytes. Harmless for now, since the
17432 only currently recognized versions are one byte long. Reported
17433 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17434 - If the state file's path bias counts are invalid (presumably from a
17435 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17436 additional checks and log messages to the scaling of Path Bias
17437 counts, in case there still are remaining issues with scaling.
17438 Should help resolve bug 8235.
17439 - Eliminate several instances where we use "Nickname=ID" to refer to
17440 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17441 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17442 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
17444 o Minor bugfixes (syscalls):
17445 - Always check the return values of functions fcntl() and
17446 setsockopt(). We don't believe these are ever actually failing in
17447 practice, but better safe than sorry. Also, checking these return
17448 values should please analysis tools like Coverity. Patch from
17449 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17450 - Use direct writes rather than stdio when building microdescriptor
17451 caches, in an attempt to mitigate bug 8031, or at least make it
17454 o Minor bugfixes (config):
17455 - When rejecting a configuration because we were unable to parse a
17456 quoted string, log an actual error message. Fixes bug 7950; bugfix
17458 - Behave correctly when the user disables LearnCircuitBuildTimeout
17459 but doesn't tell us what they would like the timeout to be. Fixes
17460 bug 6304; bugfix on 0.2.2.14-alpha.
17461 - When autodetecting the number of CPUs, use the number of available
17462 CPUs in preference to the number of configured CPUs. Inform the
17463 user if this reduces the number of available CPUs. Fixes bug 8002;
17464 bugfix on 0.2.3.1-alpha.
17465 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17466 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17467 bug 8180; bugfix on 0.2.3.11-alpha.
17468 - Allow TestingTorNetworks to override the 4096-byte minimum for
17469 the Fast threshold. Otherwise they can't bootstrap until they've
17470 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
17471 - Fix some logic errors when the user manually overrides the
17472 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
17475 o Minor bugfixes (log messages to help diagnose bugs):
17476 - If we fail to free a microdescriptor because of bug 7164, log
17477 the filename and line number from which we tried to free it.
17478 - Add another diagnostic to the heartbeat message: track and log
17479 overhead that TLS is adding to the data we write. If this is
17480 high, we are sending too little data to SSL_write at a time.
17481 Diagnostic for bug 7707.
17482 - Add more detail to a log message about relaxed timeouts, to help
17484 - Warn more aggressively when flushing microdescriptors to a
17485 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17486 or at least make it more diagnosable.
17487 - Improve debugging output to help track down bug 8185 ("Bug:
17488 outgoing relay cell has n_chan==NULL. Dropping.")
17489 - Log the purpose of a path-bias testing circuit correctly.
17490 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
17492 o Minor bugfixes (0.2.4.x log messages that were too noisy):
17493 - Don't attempt to relax the timeout of already opened 1-hop circuits.
17494 They might never timeout. This should eliminate some/all cases of
17495 the relaxed timeout log message.
17496 - Use circuit creation time for network liveness evaluation. This
17497 should eliminate warning log messages about liveness caused
17498 by changes in timeout evaluation. Fixes bug 6572; bugfix on
17500 - Reduce a path bias length check from notice to info. The message
17501 is triggered when creating controller circuits. Fixes bug 8196;
17502 bugfix on 0.2.4.8-alpha.
17503 - Fix a path state issue that triggered a notice during relay startup.
17504 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
17505 - Reduce occurrences of warns about circuit purpose in
17506 connection_ap_expire_building(). Fixes bug 8477; bugfix on
17509 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
17510 - If we encounter a write failure on a SOCKS connection before we
17511 finish our SOCKS handshake, don't warn that we closed the
17512 connection before we could send a SOCKS reply. Fixes bug 8427;
17513 bugfix on 0.1.0.1-rc.
17514 - Correctly recognize that [::1] is a loopback address. Fixes
17515 bug 8377; bugfix on 0.2.1.3-alpha.
17516 - Fix a directory authority warn caused when we have a large amount
17517 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17518 - Don't log inappropriate heartbeat messages when hibernating: a
17519 hibernating node is _expected_ to drop out of the consensus,
17520 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17521 bugfix on 0.2.3.1-alpha.
17522 - Don't complain about bootstrapping problems while hibernating.
17523 These complaints reflect a general code problem, but not one
17524 with any problematic effects (no connections are actually
17525 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17527 o Documentation fixes:
17528 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17529 names match. Fixes bug 7768.
17530 - Make the torify manpage no longer refer to tsocks; torify hasn't
17531 supported tsocks since 0.2.3.14-alpha.
17532 - Make the tor manpage no longer reference tsocks.
17533 - Fix the GeoIPExcludeUnknown documentation to refer to
17534 ExcludeExitNodes rather than the currently nonexistent
17535 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17538 - The tor-tsocks.conf is no longer distributed or installed. We
17539 recommend that tsocks users use torsocks instead. Resolves
17543 Changes in version 0.2.4.11-alpha - 2013-03-11
17544 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17545 more robust, makes hidden service authentication work again, and
17546 resolves a DPI fingerprint for Tor's SSL transport.
17548 o Major features (directory authorities):
17549 - Directory authorities now support a new consensus method (17)
17550 where they cap the published bandwidth of servers for which
17551 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17552 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17553 serve any v2 directory information. Now we can test disabling the
17554 old deprecated v2 directory format, and see whether doing so has
17555 any effect on network load. Begins to fix bug 6783.
17556 - Directory authorities now include inside each vote a statement of
17557 the performance thresholds they used when assigning flags.
17558 Implements ticket 8151.
17560 o Major bugfixes (directory authorities):
17561 - Stop marking every relay as having been down for one hour every
17562 time we restart a directory authority. These artificial downtimes
17563 were messing with our Stable and Guard flag calculations. Fixes
17564 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17566 o Major bugfixes (hidden services):
17567 - Allow hidden service authentication to succeed again. When we
17568 refactored the hidden service introduction code back
17569 in 0.2.4.1-alpha, we didn't update the code that checks
17570 whether authentication information is present, causing all
17571 authentication checks to return "false". Fix for bug 8207; bugfix
17572 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17574 o Minor features (relays, bridges):
17575 - Make bridge relays check once a minute for whether their IP
17576 address has changed, rather than only every 15 minutes. Resolves
17577 bugs 1913 and 1992.
17578 - Refactor resolve_my_address() so it returns the method by which we
17579 decided our public IP address (explicitly configured, resolved from
17580 explicit hostname, guessed from interfaces, learned by gethostname).
17581 Now we can provide more helpful log messages when a relay guesses
17582 its IP address incorrectly (e.g. due to unexpected lines in
17583 /etc/hosts). Resolves ticket 2267.
17584 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17585 microdescriptor-related dir requests, and only fall back to normal
17586 descriptors if none of their bridges can handle microdescriptors
17587 (as opposed to the fix in ticket 4013, which caused them to fall
17588 back to normal descriptors if *any* of their bridges preferred
17589 them). Resolves ticket 4994.
17590 - Randomize the lifetime of our SSL link certificate, so censors can't
17591 use the static value for filtering Tor flows. Resolves ticket 8443;
17592 related to ticket 4014 which was included in 0.2.2.33.
17593 - Support a new version of the link protocol that allows 4-byte circuit
17594 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17595 a possible resource exhaustion issue. Closes ticket 7351; implements
17598 o Minor features (portability):
17599 - Tweak the curve25519-donna*.c implementations to tolerate systems
17600 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17601 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17602 the signs of types during autoconf. This is better than our old
17603 approach, which didn't work when cross-compiling.
17604 - Detect the sign of enum values, rather than assuming that MSC is the
17605 only compiler where enum types are all signed. Fixes bug 7727;
17606 bugfix on 0.2.4.10-alpha.
17608 o Minor features (other):
17609 - Say "KBytes" rather than "KB" in the man page (for various values
17610 of K), to further reduce confusion about whether Tor counts in
17611 units of memory or fractions of units of memory. Resolves ticket 7054.
17612 - Clear the high bit on curve25519 public keys before passing them to
17613 our backend, in case we ever wind up using a backend that doesn't do
17614 so itself. If we used such a backend, and *didn't* clear the high bit,
17615 we could wind up in a situation where users with such backends would
17616 be distinguishable from users without. Fixes bug 8121; bugfix on
17618 - Update to the March 6 2013 Maxmind GeoLite Country database.
17620 o Minor bugfixes (clients):
17621 - When we receive a RELAY_END cell with the reason DONE, or with no
17622 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17623 status as "connection refused". Previously we reported these cases
17624 as success but then immediately closed the connection. Fixes bug
17625 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17626 - Downgrade an assertion in connection_ap_expire_beginning to an
17627 LD_BUG message. The fix for bug 8024 should prevent this message
17628 from displaying, but just in case, a warn that we can diagnose
17629 is better than more assert crashes. Fixes bug 8065; bugfix on
17631 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17632 Also make the rate limiting flags for the path use bias log messages
17633 independent from the original path bias flags. Fixes bug 8161;
17634 bugfix on 0.2.4.10-alpha.
17636 o Minor bugfixes (relays):
17637 - Stop trying to resolve our hostname so often (e.g. every time we
17638 think about doing a directory fetch). Now we reuse the cached
17639 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17640 and 2410 (bugfix on 0.1.2.2-alpha).
17641 - Stop sending a stray "(null)" in some cases for the server status
17642 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17644 - When choosing which stream on a formerly stalled circuit to wake
17645 first, make better use of the platform's weak RNG. Previously,
17646 we had been using the % ("modulo") operator to try to generate a
17647 1/N chance of picking each stream, but this behaves badly with
17648 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17650 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17651 Irix's random() only return 15 bits; Solaris's random() returns more
17652 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17653 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17655 o Minor bugfixes (directory authorities):
17656 - Directory authorities now use less space when formatting identical
17657 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17660 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17661 - Avoid leaking memory if we fail to compute a consensus signature
17662 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17663 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17665 - Fix a memory leak during safe-cookie controller authentication.
17666 Bugfix on 0.2.3.13-alpha.
17667 - Avoid memory leak of IPv6 policy content if we fail to format it into
17668 a router descriptor. Bugfix on 0.2.4.7-alpha.
17670 o Minor bugfixes (other code correctness issues):
17671 - Avoid a crash if we fail to generate an extrainfo descriptor.
17672 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17673 this is CID 718634.
17674 - When detecting the largest possible file descriptor (in order to
17675 close all file descriptors when launching a new program), actually
17676 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17677 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17679 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17680 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17681 Bugfix on 0.2.4.10-alpha.
17682 - Fix an impossible-to-trigger integer overflow when estimating how
17683 long our onionskin queue would take. (This overflow would require us
17684 to accept 4 million onionskins before processing 100 of them.) Fixes
17685 bug 8210; bugfix on 0.2.4.10-alpha.
17687 o Code simplification and refactoring:
17688 - Add a wrapper function for the common "log a message with a
17692 Changes in version 0.2.4.10-alpha - 2013-02-04
17693 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17694 certain attacks that flood the network with relays; changes the queue
17695 for circuit create requests from a sized-based limit to a time-based
17696 limit; resumes building with MSVC on Windows; and fixes a wide variety
17699 o Major bugfixes (directory authority):
17700 - When computing directory thresholds, ignore any rejected-as-sybil
17701 nodes during the computation so that they can't influence Fast,
17702 Guard, etc. (We should have done this for proposal 109.) Fixes
17704 - When marking a node as a likely sybil, reset its uptime metrics
17705 to zero, so that it cannot time towards getting marked as Guard,
17706 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17710 - When a TLS write is partially successful but incomplete, remember
17711 that the flushed part has been flushed, and notice that bytes were
17712 actually written. Reported and fixed pseudonymously. Fixes bug
17713 7708; bugfix on Tor 0.1.0.5-rc.
17714 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17715 ID: these could be used to create unexpected streams and circuits
17716 which would count as "present" to some parts of Tor but "absent"
17717 to others, leading to zombie circuits and streams or to a bandwidth
17718 denial-of-service. Fixes bug 7889; bugfix on every released version
17719 of Tor. Reported by "oftc_must_be_destroyed".
17720 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17721 This change seems the only good way to permanently prevent conflicts
17722 with queue.h on various operating systems. Fixes bug 8107; bugfix
17725 o Major features (relay):
17726 - Instead of limiting the number of queued onionskins (aka circuit
17727 create requests) to a fixed, hard-to-configure number, we limit
17728 the size of the queue based on how many we expect to be able to
17729 process in a given amount of time. We estimate the time it will
17730 take to process an onionskin based on average processing time
17731 of previous onionskins. Closes ticket 7291. You'll never have to
17732 configure MaxOnionsPending again.
17734 o Major features (portability):
17735 - Resume building correctly with MSVC and Makefile.nmake. This patch
17736 resolves numerous bugs and fixes reported by ultramage, including
17737 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17738 - Make the ntor and curve25519 code build correctly with MSVC.
17739 Fix on 0.2.4.8-alpha.
17742 - When directory authorities are computing thresholds for flags,
17743 never let the threshold for the Fast flag fall below 4096
17744 bytes. Also, do not consider nodes with extremely low bandwidths
17745 when deciding thresholds for various directory flags. This change
17746 should raise our threshold for Fast relays, possibly in turn
17747 improving overall network performance; see ticket 1854. Resolves
17749 - The Tor client now ignores sub-domain components of a .onion
17750 address. This change makes HTTP "virtual" hosting
17751 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17752 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17753 hosted on the same hidden service. Implements proposal 204.
17754 - We compute the overhead from passing onionskins back and forth to
17755 cpuworkers, and report it when dumping statistics in response to
17756 SIGUSR1. Supports ticket 7291.
17758 o Minor features (path selection):
17759 - When deciding whether we have enough descriptors to build circuits,
17760 instead of looking at raw relay counts, look at which fraction
17761 of (bandwidth-weighted) paths we're able to build. This approach
17762 keeps clients from building circuits if their paths are likely to
17763 stand out statistically. The default fraction of paths needed is
17764 taken from the consensus directory; you can override it with the
17765 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17766 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17767 and we have GeoIP information, also exclude all nodes with unknown
17768 countries "??" and "A1". This behavior is controlled by the
17769 new GeoIPExcludeUnknown option: you can make such nodes always
17770 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17771 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17772 gets you the default behavior. Implements feature 7706.
17773 - Path Use Bias: Perform separate accounting for successful circuit
17774 use. Keep separate statistics on stream attempt rates versus stream
17775 success rates for each guard. Provide configurable thresholds to
17776 determine when to emit log messages or disable use of guards that
17777 fail too many stream attempts. Resolves ticket 7802.
17779 o Minor features (log messages):
17780 - When learning a fingerprint for a bridge, log its corresponding
17781 transport type. Implements ticket 7896.
17782 - Improve the log message when "Bug/attack: unexpected sendme cell
17783 from client" occurs, to help us track bug 8093.
17786 - Remove a couple of extraneous semicolons that were upsetting the
17787 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17788 bugfix on 0.2.2.1-alpha.
17789 - Remove a source of rounding error during path bias count scaling;
17790 don't count cannibalized circuits as used for path bias until we
17791 actually try to use them; and fix a circuit_package_relay_cell()
17792 warning message about n_chan==NULL. Fixes bug 7802.
17793 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
17794 actually link against nacl when we're configured to use it. Fixes
17795 bug 7972; bugfix on 0.2.4.8-alpha.
17796 - Compile correctly with the --disable-curve25519 option. Fixes
17797 bug 8153; bugfix on 0.2.4.8-alpha.
17799 o Build improvements:
17800 - Do not report status verbosely from autogen.sh unless the -v flag
17801 is specified. Fixes issue 4664. Patch from Onizuka.
17802 - Replace all calls to snprintf() outside of src/ext with
17803 tor_snprintf(). Also remove the #define to replace snprintf with
17804 _snprintf on Windows; they have different semantics, and all of
17805 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17806 - Try to detect if we are ever building on a platform where
17807 memset(...,0,...) does not set the value of a double to 0.0. Such
17808 platforms are permitted by the C standard, though in practice
17809 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17810 currently support them, but it's better to detect them and fail
17811 than to perform erroneously.
17813 o Removed features:
17814 - Stop exporting estimates of v2 and v3 directory traffic shares
17815 in extrainfo documents. They were unneeded and sometimes inaccurate.
17816 Also stop exporting any v2 directory request statistics. Resolves
17818 - Drop support for detecting and warning about versions of Libevent
17819 before 1.3e. Nothing reasonable ships with them any longer;
17820 warning the user about them shouldn't be needed. Resolves ticket
17823 o Code simplifications and refactoring:
17824 - Rename "isin" functions to "contains", for grammar. Resolves
17826 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17827 with the natural logarithm function from the system libm. Resolves
17831 Changes in version 0.2.4.9-alpha - 2013-01-15
17832 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
17833 work more robustly.
17836 - Fix backward compatibility logic when receiving an embedded ntor
17837 handshake tunneled in a CREATE cell. This clears up the "Bug:
17838 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
17842 Changes in version 0.2.4.8-alpha - 2013-01-14
17843 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
17844 risks, adds a new stronger and faster circuit handshake, and offers
17845 stronger and faster link encryption when both sides support it.
17848 - Preliminary support for directory guards (proposal 207): when
17849 possible, clients now use their entry guards for non-anonymous
17850 directory requests. This can help prevent client enumeration. Note
17851 that this behavior only works when we have a usable consensus
17852 directory, and when options about what to download are more or less
17853 standard. In the future we should re-bootstrap from our guards,
17854 rather than re-bootstrapping from the preconfigured list of
17855 directory sources that ships with Tor. Resolves ticket 6526.
17856 - Tor relays and clients now support a better CREATE/EXTEND cell
17857 format, allowing the sender to specify multiple address, identity,
17858 and handshake types. Implements Robert Ransom's proposal 200;
17859 closes ticket 7199.
17861 o Major features (new circuit handshake):
17862 - Tor now supports a new circuit extension handshake designed by Ian
17863 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17864 circuit extension handshake, later called "TAP", was a bit slow
17865 (especially on the relay side), had a fragile security proof, and
17866 used weaker keys than we'd now prefer. The new circuit handshake
17867 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17868 function, making it significantly more secure than the older
17869 handshake, and significantly faster. Tor can use one of two built-in
17870 pure-C curve25519-donna implementations by Adam Langley, or it
17871 can link against the "nacl" library for a tuned version if present.
17873 The built-in version is very fast for 64-bit systems when building
17874 with GCC. The built-in 32-bit version is still faster than the
17875 old TAP protocol, but using libnacl is better on most such hosts.
17877 Clients don't currently use this protocol by default, since
17878 comparatively few clients support it so far. To try it, set
17879 UseNTorHandshake to 1.
17881 Implements proposal 216; closes ticket 7202.
17883 o Major features (better link encryption):
17884 - Relays can now enable the ECDHE TLS ciphersuites when available
17885 and appropriate. These ciphersuites let us negotiate forward-secure
17886 TLS secret keys more safely and more efficiently than with our
17887 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17888 public relays prefer the (faster) P224 group, and bridges prefer
17889 the (more common) P256 group; you can override this with the
17892 Enabling these ciphers was a little tricky, since for a long time,
17893 clients had been claiming to support them without actually doing
17894 so, in order to foil fingerprinting. But with the client-side
17895 implementation of proposal 198 in 0.2.3.17-beta, clients can now
17896 match the ciphers from recent Firefox versions *and* list the
17897 ciphers they actually mean, so relays can believe such clients
17898 when they advertise ECDHE support in their TLS ClientHello messages.
17900 This feature requires clients running 0.2.3.17-beta or later,
17901 and requires both sides to be running OpenSSL 1.0.0 or later
17902 with ECC support. OpenSSL 1.0.1, with the compile-time option
17903 "enable-ec_nistp_64_gcc_128", is highly recommended.
17905 Implements the relay side of proposal 198; closes ticket 7200.
17908 - Avoid crashing when, as a relay without IPv6-exit support, a
17909 client insists on getting an IPv6 address or nothing. Fixes bug
17910 7814; bugfix on 0.2.4.7-alpha.
17913 - Improve circuit build timeout handling for hidden services.
17914 In particular: adjust build timeouts more accurately depending
17915 upon the number of hop-RTTs that a particular circuit type
17916 undergoes. Additionally, launch intro circuits in parallel
17917 if they timeout, and take the first one to reply as valid.
17918 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17919 separate error codes; or at least, don't break for that reason.
17920 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17921 - Update to the January 2 2013 Maxmind GeoLite Country database.
17923 o Minor features (testing):
17924 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17925 (P-256) Diffie-Hellman handshakes to src/or/bench.
17926 - Add benchmark functions to test onion handshake performance.
17928 o Minor features (path bias detection):
17929 - Alter the Path Bias log messages to be more descriptive in terms
17930 of reporting timeouts and other statistics.
17931 - Create three levels of Path Bias log messages, as opposed to just
17932 two. These are configurable via consensus as well as via the torrc
17933 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17934 The default values are 0.70, 0.50, and 0.30 respectively.
17935 - Separate the log message levels from the decision to drop guards,
17936 which also is available via torrc option PathBiasDropGuards.
17937 PathBiasDropGuards still defaults to 0 (off).
17938 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17939 in combination with PathBiasExtremeRate.
17940 - Increase the default values for PathBiasScaleThreshold and
17941 PathBiasCircThreshold from (200, 20) to (300, 150).
17942 - Add in circuit usage accounting to path bias. If we try to use a
17943 built circuit but fail for any reason, it counts as path bias.
17944 Certain classes of circuits where the adversary gets to pick your
17945 destination node are exempt from this accounting. Usage accounting
17946 can be specifically disabled via consensus parameter or torrc.
17947 - Convert all internal path bias state to double-precision floating
17948 point, to avoid roundoff error and other issues.
17949 - Only record path bias information for circuits that have completed
17950 *two* hops. Assuming end-to-end tagging is the attack vector, this
17951 makes us more resilient to ambient circuit failure without any
17952 detection capability loss.
17954 o Minor bugfixes (log messages):
17955 - Rate-limit the "No circuits are opened. Relaxed timeout for a
17956 circuit with channel state open..." message to once per hour to
17957 keep it from filling the notice logs. Mitigates bug 7799 but does
17958 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
17959 - Avoid spurious warnings when configuring multiple client ports of
17960 which only some are nonlocal. Previously, we had claimed that some
17961 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17964 o Code simplifications and refactoring:
17965 - Get rid of a couple of harmless clang warnings, where we compared
17966 enums to ints. These warnings are newly introduced in clang 3.2.
17967 - Split the onion.c file into separate modules for the onion queue
17968 and the different handshakes it supports.
17969 - Remove the marshalling/unmarshalling code for sending requests to
17970 cpuworkers over a socket, and instead just send structs. The
17971 recipient will always be the same Tor binary as the sender, so
17972 any encoding is overkill.
17975 Changes in version 0.2.4.7-alpha - 2012-12-24
17976 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
17977 directory mirrors for more robust bootstrapping; fixes more issues where
17978 clients with changing network conditions refuse to make any circuits;
17979 adds initial support for exiting to IPv6 addresses; resumes being able
17980 to update our GeoIP database, and includes the geoip6 file this time;
17981 turns off the client-side DNS cache by default due to privacy risks;
17982 and fixes a variety of other issues.
17984 o Major features (client resilience):
17985 - Add a new "FallbackDir" torrc option to use when we can't use
17986 a directory mirror from the consensus (either because we lack a
17987 consensus, or because they're all down). Currently, all authorities
17988 are fallbacks by default, and there are no other default fallbacks,
17989 but that will change. This option will allow us to give clients a
17990 longer list of servers to try to get a consensus from when first
17991 connecting to the Tor network, and thereby reduce load on the
17992 directory authorities. Implements proposal 206, "Preconfigured
17993 directory sources for bootstrapping". We also removed the old
17994 "FallbackNetworkstatus" option, since we never got it working well
17995 enough to use it. Closes bug 572.
17996 - If we have no circuits open, use a relaxed timeout (the
17997 95-percentile cutoff) until a circuit succeeds. This heuristic
17998 should allow Tor to succeed at building circuits even when the
17999 network connection drastically changes. Should help with bug 3443.
18001 o Major features (IPv6):
18002 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18003 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18004 exit policy reads as you would like: the address * applies to all
18005 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18006 addresses only. On the client side, you'll need to wait until the
18007 authorities have upgraded, wait for enough exits to support IPv6,
18008 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
18009 ticket 5547, implements proposal 117 as revised in proposal 208.
18011 We DO NOT recommend that clients with actual anonymity needs start
18012 using IPv6 over Tor yet, since not enough exits support it yet.
18014 o Major features (geoip database):
18015 - Maxmind began labelling Tor relays as being in country "A1",
18016 which breaks by-country node selection inside Tor. Now we use a
18017 script to replace "A1" ("Anonymous Proxy") entries in our geoip
18018 file with real country codes. This script fixes about 90% of "A1"
18019 entries automatically and uses manual country code assignments to
18020 fix the remaining 10%. See src/config/README.geoip for details.
18021 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
18022 Country database, as modified above.
18024 o Major bugfixes (client-side DNS):
18025 - Turn off the client-side DNS cache by default. Updating and using
18026 the DNS cache is now configurable on a per-client-port
18027 level. SOCKSPort, DNSPort, etc lines may now contain
18028 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18029 cache these types of DNS answers when we receive them from an
18030 exit node in response to an application request on this port, and
18031 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18032 cached DNS answers of these types, we shouldn't use them. It's
18033 potentially risky to use cached DNS answers at the client, since
18034 doing so can indicate to one exit what answers we've gotten
18035 for DNS lookups in the past. With IPv6, this becomes especially
18036 problematic. Using cached DNS answers for requests on the same
18037 circuit would present less linkability risk, since all traffic
18038 on a circuit is already linkable, but it would also provide
18039 little performance benefit: the exit node caches DNS replies
18040 too. Implements a simplified version of Proposal 205. Implements
18043 o Major bugfixes (other):
18044 - Alter circuit build timeout measurement to start at the point
18045 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18046 initialization). This should make our timeout measurements more
18047 uniform. Previously, we were sometimes including ORconn setup time
18048 in our circuit build time measurements. Should resolve bug 3443.
18049 - Fix an assertion that could trigger in hibernate_go_dormant() when
18050 closing an or_connection_t: call channel_mark_for_close() rather
18051 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
18053 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
18054 7655; bugfix on 0.2.4.6-alpha.
18057 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18058 operators select the address where their pluggable transports will
18059 listen for connections. Resolves ticket 7013.
18060 - Allow an optional $ before the node identity digest in the
18061 controller command GETINFO ns/id/<identity>, for consistency with
18062 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18063 - Log packaged cell fullness as part of the heartbeat message.
18064 Diagnosis to try to determine the extent of bug 7743.
18066 o Minor features (IPv6):
18067 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18068 prefer to hand out virtual IPv6 addresses, since there are more of
18069 them and we can't run out. To override this behavior and make IPv4
18070 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18071 or DNSPort you're using for resolving. Implements ticket 7571.
18072 - AutomapHostsOnResolve responses are now randomized, to avoid
18073 annoying situations where Tor is restarted and applications
18074 connect to the wrong addresses.
18075 - Never try more than 1000 times to pick a new virtual address when
18076 AutomapHostsOnResolve is set. That's good enough so long as we
18077 aren't close to handing out our entire virtual address space;
18078 if you're getting there, it's best to switch to IPv6 virtual
18082 - The ADDRMAP command can no longer generate an ill-formed error
18083 code on a failed MAPADDRESS. It now says "internal" rather than
18084 an English sentence fragment with spaces in the middle. Bugfix on
18085 Tor 0.2.0.19-alpha.
18086 - Fix log messages and comments to avoid saying "GMT" when we mean
18087 "UTC". Fixes bug 6113.
18088 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18090 - Fix a crash when debugging unit tests on Windows: deallocate a
18091 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
18092 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
18095 - The DirServer option is now DirAuthority, for consistency with
18096 current naming patterns. You can still use the old DirServer form.
18098 o Code simplification and refactoring:
18099 - Move the client-side address-map/virtual-address/DNS-cache code
18100 out of connection_edge.c into a new addressmap.c module.
18101 - Remove unused code for parsing v1 directories and "running routers"
18102 documents. Fixes bug 6887.
18105 Changes in version 0.2.3.25 - 2012-11-19
18106 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18107 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18108 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18109 programmer, and friend. Unstinting in his dedication to the cause of
18110 freedom, he inspired and helped many of us as we began our work on
18111 anonymity, and inspires us still. Please honor his memory by writing
18112 software to protect people's freedoms, and by helping others to do so.
18114 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18115 significantly reduced directory overhead (via microdescriptors),
18116 enormous crypto performance improvements for fast relays on new
18117 enough hardware, a new v3 TLS handshake protocol that can better
18118 resist fingerprinting, support for protocol obfuscation plugins (aka
18119 pluggable transports), better scalability for hidden services, IPv6
18120 support for bridges, performance improvements like allowing clients
18121 to skip the first round-trip on the circuit ("optimistic data") and
18122 refilling token buckets more often, a new "stream isolation" design
18123 to isolate different applications on different circuits, and many
18124 stability, security, and privacy fixes.
18127 - Tor tries to wipe potentially sensitive data after using it, so
18128 that if some subsequent security failure exposes Tor's memory,
18129 the damage will be limited. But we had a bug where the compiler
18130 was eliminating these wipe operations when it decided that the
18131 memory was no longer visible to a (correctly running) program,
18132 hence defeating our attempt at defense in depth. We fix that
18133 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18134 is unlikely to optimize away. Future versions of Tor may use
18135 a less ridiculously heavy approach for this. Fixes bug 7352.
18136 Reported in an article by Andrey Karpov.
18139 - Fix a harmless bug when opting against publishing a relay descriptor
18140 because DisableNetwork is set. Fixes bug 7464; bugfix on
18144 Changes in version 0.2.4.6-alpha - 2012-11-13
18145 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
18146 makes our defense-in-depth memory wiping more reliable, and begins to
18147 count IPv6 addresses in bridge statistics,
18150 - Fix an assertion failure that could occur when closing a connection
18151 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
18153 - Tor tries to wipe potentially sensitive data after using it, so
18154 that if some subsequent security failure exposes Tor's memory,
18155 the damage will be limited. But we had a bug where the compiler
18156 was eliminating these wipe operations when it decided that the
18157 memory was no longer visible to a (correctly running) program,
18158 hence defeating our attempt at defense in depth. We fix that
18159 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18160 is unlikely to optimize away. Future versions of Tor may use
18161 a less ridiculously heavy approach for this. Fixes bug 7352.
18162 Reported in an article by Andrey Karpov.
18165 - Add GeoIP database for IPv6 addresses. The new config option
18167 - Bridge statistics now count bridge clients connecting over IPv6:
18168 bridge statistics files now list "bridge-ip-versions" and
18169 extra-info documents list "geoip6-db-digest". The control protocol
18170 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18171 implementation by "shkoo", addressing ticket 5055.
18174 - Warn when we are binding low ports when hibernation is enabled;
18175 previously we had warned when we were _advertising_ low ports with
18176 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18177 - Fix a harmless bug when opting against publishing a relay descriptor
18178 because DisableNetwork is set. Fixes bug 7464; bugfix on
18180 - Add warning message when a managed proxy dies during configuration.
18181 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
18182 - Fix a linking error when building tor-fw-helper without miniupnp.
18183 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
18184 - Check for closing an or_connection_t without going through correct
18185 channel functions; emit a warning and then call
18186 connection_or_close_for_error() so we don't assert as in bugs 7212
18188 - Compile correctly on compilers without C99 designated initializer
18189 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
18190 - Avoid a possible assert that can occur when channel_send_destroy() is
18191 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
18192 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
18193 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
18194 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
18195 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
18197 o Code simplification and refactoring:
18198 - Start using OpenBSD's implementation of queue.h, so that we don't
18199 need to hand-roll our own pointer and list structures whenever we
18200 need them. (We can't rely on a sys/queue.h, since some operating
18201 systems don't have them, and the ones that do have them don't all
18202 present the same extensions.)
18205 Changes in version 0.2.4.5-alpha - 2012-10-25
18206 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
18207 two important security vulnerabilities that could lead to remotely
18208 triggerable relay crashes, fix a major bug that was preventing clients
18209 from choosing suitable exit nodes, and refactor some of our code.
18211 o Major bugfixes (security, also in 0.2.3.24-rc):
18212 - Fix a group of remotely triggerable assertion failures related to
18213 incorrect link protocol negotiation. Found, diagnosed, and fixed
18214 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18216 - Fix a denial of service attack by which any directory authority
18217 could crash all the others, or by which a single v2 directory
18218 authority could crash everybody downloading v2 directory
18219 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18221 o Major bugfixes (also in 0.2.3.24-rc):
18222 - When parsing exit policy summaries from microdescriptors, we had
18223 previously been ignoring the last character in each one, so that
18224 "accept 80,443,8080" would be treated by clients as indicating
18225 a node that allows access to ports 80, 443, and 808. That would
18226 lead to clients attempting connections that could never work,
18227 and ignoring exit nodes that would support their connections. Now
18228 clients parse these exit policy summaries correctly. Fixes bug 7192;
18229 bugfix on 0.2.3.1-alpha.
18231 o Minor bugfixes (also in 0.2.3.24-rc):
18232 - Clients now consider the ClientRejectInternalAddresses config option
18233 when using a microdescriptor consensus stanza to decide whether
18234 an exit relay would allow exiting to an internal address. Fixes
18235 bug 7190; bugfix on 0.2.3.1-alpha.
18238 - Only disable TLS session ticket support when running as a TLS
18239 server. Now clients will blend better with regular Firefox
18240 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18242 o Code simplification and refactoring:
18243 - Start using OpenBSD's implementation of queue.h (originally by
18245 - Move the entry node code from circuitbuild.c to its own file.
18246 - Move the circuit build timeout tracking code from circuitbuild.c
18250 Changes in version 0.2.3.24-rc - 2012-10-25
18251 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
18252 could lead to remotely triggerable relay crashes, and fixes
18253 a major bug that was preventing clients from choosing suitable exit
18256 o Major bugfixes (security):
18257 - Fix a group of remotely triggerable assertion failures related to
18258 incorrect link protocol negotiation. Found, diagnosed, and fixed
18259 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18261 - Fix a denial of service attack by which any directory authority
18262 could crash all the others, or by which a single v2 directory
18263 authority could crash everybody downloading v2 directory
18264 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18267 - When parsing exit policy summaries from microdescriptors, we had
18268 previously been ignoring the last character in each one, so that
18269 "accept 80,443,8080" would be treated by clients as indicating
18270 a node that allows access to ports 80, 443, and 808. That would
18271 lead to clients attempting connections that could never work,
18272 and ignoring exit nodes that would support their connections. Now
18273 clients parse these exit policy summaries correctly. Fixes bug 7192;
18274 bugfix on 0.2.3.1-alpha.
18277 - Clients now consider the ClientRejectInternalAddresses config option
18278 when using a microdescriptor consensus stanza to decide whether
18279 an exit relay would allow exiting to an internal address. Fixes
18280 bug 7190; bugfix on 0.2.3.1-alpha.
18283 Changes in version 0.2.4.4-alpha - 2012-10-20
18284 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
18285 vulnerability introduced by a change in OpenSSL, fixes a remotely
18286 triggerable assert, and adds new channel_t and circuitmux_t abstractions
18287 that will make it easier to test new connection transport and cell
18288 scheduling algorithms.
18290 o New directory authorities (also in 0.2.3.23-rc):
18291 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18292 authority. Closes ticket 5749.
18294 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
18295 - Disable TLS session tickets. OpenSSL's implementation was giving
18296 our TLS session keys the lifetime of our TLS context objects, when
18297 perfect forward secrecy would want us to discard anything that
18298 could decrypt a link connection as soon as the link connection
18299 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18300 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18301 - Discard extraneous renegotiation attempts once the V3 link
18302 protocol has been initiated. Failure to do so left us open to
18303 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18304 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18306 o Internal abstraction features:
18307 - Introduce new channel_t abstraction between circuits and
18308 or_connection_t to allow for implementing alternate OR-to-OR
18309 transports. A channel_t is an abstract object which can either be a
18310 cell-bearing channel, which is responsible for authenticating and
18311 handshaking with the remote OR and transmitting cells to and from
18312 it, or a listening channel, which spawns new cell-bearing channels
18313 at the request of remote ORs. Implements part of ticket 6465.
18314 - Also new is the channel_tls_t subclass of channel_t, adapting it
18315 to the existing or_connection_t code. The V2/V3 protocol handshaking
18316 code which formerly resided in command.c has been moved below the
18317 channel_t abstraction layer and may be found in channeltls.c now.
18318 Implements the rest of ticket 6465.
18319 - Introduce new circuitmux_t storing the queue of circuits for
18320 a channel; this encapsulates and abstracts the queue logic and
18321 circuit selection policy, and allows the latter to be overridden
18322 easily by switching out a policy object. The existing EWMA behavior
18323 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18325 o Required libraries:
18326 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18327 strongly recommended.
18330 - Warn users who run hidden services on a Tor client with
18331 UseEntryGuards disabled that their hidden services will be
18332 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18333 attack which motivated Tor to support entry guards in the first
18334 place). Resolves ticket 6889.
18335 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18336 dhill. Resolves ticket 6982.
18337 - Option OutboundBindAddress can be specified multiple times and
18338 accepts IPv6 addresses. Resolves ticket 6876.
18340 o Minor bugfixes (also in 0.2.3.23-rc):
18341 - Don't serve or accept v2 hidden service descriptors over a
18342 relay's DirPort. It's never correct to do so, and disabling it
18343 might make it more annoying to exploit any bugs that turn up in the
18344 descriptor-parsing code. Fixes bug 7149.
18345 - Fix two cases in src/or/transports.c where we were calling
18346 fmt_addr() twice in a parameter list. Bug found by David
18347 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18348 - Fix memory leaks whenever we logged any message about the "path
18349 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18350 - When relays refuse a "create" cell because their queue of pending
18351 create cells is too big (typically because their cpu can't keep up
18352 with the arrival rate), send back reason "resource limit" rather
18353 than reason "internal", so network measurement scripts can get a
18354 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
18357 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18358 - Free some more still-in-use memory at exit, to make hunting for
18359 memory leaks easier. Resolves bug 7029.
18360 - When a Tor client gets a "truncated" relay cell, the first byte of
18361 its payload specifies why the circuit was truncated. We were
18362 ignoring this 'reason' byte when tearing down the circuit, resulting
18363 in the controller not being told why the circuit closed. Now we
18364 pass the reason from the truncated cell to the controller. Bugfix
18365 on 0.1.2.3-alpha; fixes bug 7039.
18366 - Downgrade "Failed to hand off onionskin" messages to "debug"
18367 severity, since they're typically redundant with the "Your computer
18368 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18369 - Make clients running with IPv6 bridges connect over IPv6 again,
18370 even without setting new config options ClientUseIPv6 and
18371 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
18372 - Use square brackets around IPv6 addresses in numerous places
18373 that needed them, including log messages, HTTPS CONNECT proxy
18374 requests, TransportProxy statefile entries, and pluggable transport
18375 extra-info lines. Fixes bug 7011; patch by David Fifield.
18377 o Code refactoring and cleanup:
18378 - Source files taken from other packages now reside in src/ext;
18379 previously they were scattered around the rest of Tor.
18380 - Avoid use of reserved identifiers in our C code. The C standard
18381 doesn't like us declaring anything that starts with an
18382 underscore, so let's knock it off before we get in trouble. Fix
18383 for bug 1031; bugfix on the first Tor commit.
18386 Changes in version 0.2.3.23-rc - 2012-10-20
18387 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
18388 vulnerability introduced by a change in OpenSSL, and fixes a variety
18389 of smaller bugs in preparation for the release.
18391 o New directory authorities:
18392 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18393 authority. Closes ticket 5749.
18395 o Major bugfixes (security/privacy):
18396 - Disable TLS session tickets. OpenSSL's implementation was giving
18397 our TLS session keys the lifetime of our TLS context objects, when
18398 perfect forward secrecy would want us to discard anything that
18399 could decrypt a link connection as soon as the link connection
18400 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18401 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18402 - Discard extraneous renegotiation attempts once the V3 link
18403 protocol has been initiated. Failure to do so left us open to
18404 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18405 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18408 - Fix a possible crash bug when checking for deactivated circuits
18409 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18410 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18412 o Minor bugfixes (on 0.2.3.x):
18413 - Fix two cases in src/or/transports.c where we were calling
18414 fmt_addr() twice in a parameter list. Bug found by David
18415 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18416 - Convert an assert in the pathbias code to a log message. The assert
18417 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18418 bugfix on 0.2.3.17-beta.
18419 - Fix memory leaks whenever we logged any message about the "path
18420 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18422 o Minor bugfixes (on 0.2.2.x and earlier):
18423 - Don't serve or accept v2 hidden service descriptors over a relay's
18424 DirPort. It's never correct to do so, and disabling it might
18425 make it more annoying to exploit any bugs that turn up in the
18426 descriptor-parsing code. Fixes bug 7149.
18427 - When relays refuse a "create" cell because their queue of pending
18428 create cells is too big (typically because their cpu can't keep up
18429 with the arrival rate), send back reason "resource limit" rather
18430 than reason "internal", so network measurement scripts can get a
18431 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18432 - Correct file sizes when reading binary files on Cygwin, to avoid
18433 a bug where Tor would fail to read its state file. Fixes bug 6844;
18434 bugfix on 0.1.2.7-alpha.
18435 - Avoid undefined behavior when parsing the list of supported
18436 rendezvous/introduction protocols in a hidden service descriptor.
18437 Previously, Tor would have confused (as-yet-unused) protocol version
18438 numbers greater than 32 with lower ones on many platforms. Fixes
18439 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18441 o Documentation fixes:
18442 - Clarify that hidden services are TCP only. Fixes bug 6024.
18445 Changes in version 0.2.4.3-alpha - 2012-09-22
18446 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
18447 assertion, resumes letting relays test reachability of their DirPort,
18448 and cleans up a bunch of smaller bugs.
18451 - Fix an assertion failure in tor_timegm() that could be triggered
18452 by a badly formatted directory object. Bug found by fuzzing with
18453 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18456 - Fix a possible crash bug when checking for deactivated circuits
18457 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18458 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18459 - Allow routers to detect that their own DirPorts are running. When
18460 we removed support for versions_supports_begindir, we also
18461 accidentally removed the mechanism we used to self-test our
18462 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
18463 bugfix on 0.2.4.2-alpha.
18465 o Security features:
18466 - Switch to a completely time-invariant approach for picking nodes
18467 weighted by bandwidth. Our old approach would run through the
18468 part of the loop after it had made its choice slightly slower
18469 than it ran through the part of the loop before it had made its
18470 choice. Addresses ticket 6538.
18471 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18472 by tor2web clients allows hidden services to identify tor2web
18473 clients through their repeated selection of the same rendezvous
18474 and introduction point circuit endpoints (their guards). Resolves
18478 - Enable Tor to read configuration, state, and key information from
18479 a FIFO. Previously Tor would only read from files with a positive
18480 stat.st_size. Code from meejah; fixes bug 6044.
18483 - Correct file sizes when reading binary files on Cygwin, to avoid
18484 a bug where Tor would fail to read its state file. Fixes bug 6844;
18485 bugfix on 0.1.2.7-alpha.
18486 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18487 bugfix on 0.2.0.3-alpha.
18488 - When complaining about a client port on a public address, log
18489 which address we're complaining about. Fixes bug 4020; bugfix on
18490 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18491 - Convert an assert in the pathbias code to a log message. The assert
18492 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18493 bugfix on 0.2.3.17-beta.
18494 - Our new buildsystem was overzealous about rebuilding manpages: it
18495 would rebuild them all whenever any one of them changed. Now our
18496 dependency checking should be correct. Fixes bug 6843; bugfix on
18498 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
18499 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
18500 - Correct log printout about which address family is preferred
18501 when connecting to a bridge with both an IPv4 and IPv6 OR port.
18502 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
18504 o Minor bugfixes (code cleanliness):
18505 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18506 with large values. This situation was untriggered, but nevertheless
18507 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18508 - Reject consensus votes with more than 64 known-flags. We aren't even
18509 close to that limit yet, and our code doesn't handle it correctly.
18510 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18511 - Avoid undefined behavior when parsing the list of supported
18512 rendezvous/introduction protocols in a hidden service descriptor.
18513 Previously, Tor would have confused (as-yet-unused) protocol version
18514 numbers greater than 32 with lower ones on many platforms. Fixes
18515 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18516 - Fix handling of rendezvous client authorization types over 8.
18517 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18518 - Fix building with older versions of GCC (2.95, for one) that don't
18519 like preprocessor directives inside macro arguments. Found by
18520 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
18521 - Switch weighted node selection rule from using a list of doubles
18522 to using a list of int64_t. This change should make the process
18523 slightly easier to debug and maintain. Needed to finish ticket 6538.
18525 o Code simplification and refactoring:
18526 - Move the generic "config" code into a new file, and have "config.c"
18527 hold only torrc- and state-related code. Resolves ticket 6823.
18528 - Move the core of our "choose a weighted element at random" logic
18529 into its own function, and give it unit tests. Now the logic is
18530 testable, and a little less fragile too.
18531 - Removed the testing_since field of node_t, which hasn't been used
18532 for anything since 0.2.0.9-alpha.
18534 o Documentation fixes:
18535 - Clarify that hidden services are TCP only. Fixes bug 6024.
18536 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18540 Changes in version 0.2.3.22-rc - 2012-09-11
18541 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18545 - Fix an assertion failure in tor_timegm() that could be triggered
18546 by a badly formatted directory object. Bug found by fuzzing with
18547 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18550 - Avoid segfault when starting up having run with an extremely old
18551 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18555 Changes in version 0.2.2.39 - 2012-09-11
18556 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18560 - Fix an assertion failure in tor_timegm() that could be triggered
18561 by a badly formatted directory object. Bug found by fuzzing with
18562 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18563 - Do not crash when comparing an address with port value 0 to an
18564 address policy. This bug could have been used to cause a remote
18565 assertion failure by or against directory authorities, or to
18566 allow some applications to crash clients. Fixes bug 6690; bugfix
18570 Changes in version 0.2.4.2-alpha - 2012-09-10
18571 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18572 raises the default rate limiting even more, and makes the bootstrapping
18573 log messages less noisy.
18576 - Automatically forward the TCP ports of pluggable transport
18577 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18581 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18582 to 1GB/1GB. The previous defaults were intended to be "basically
18583 infinite", but it turns out they're now limiting our 100mbit+
18584 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18585 last time we raised it).
18588 - Detect when we're running with a version of OpenSSL other than the
18589 one we compiled with. This has occasionally given people hard-to-
18591 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18592 versions and capabilities when everything is going right. Resolves
18593 part of ticket 6736.
18594 - Directory authorities no long accept descriptors for any version of
18595 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18596 These versions are insecure, unsupported, or both. Implements
18600 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18601 to start with a triple-underscore so the controller won't touch it.
18602 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18603 - Avoid segfault when starting up having run with an extremely old
18604 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18606 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18607 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18608 - Don't follow the NULL pointer if microdescriptor generation fails.
18609 (This does not appear to be triggerable, but it's best to be safe.)
18610 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18611 - Fix mis-declared dependencies on src/common/crypto.c and
18612 src/or/tor_main.c that could break out-of-tree builds under some
18613 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18614 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18615 6778; bugfix on 0.2.4.1-alpha.
18616 - Fix a harmless (in this case) build warning for implicitly
18617 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18619 o Removed features:
18620 - Now that all versions before 0.2.2.x are disallowed, we no longer
18621 need to work around their missing features. Thus we can remove a
18622 bunch of compatibility code.
18624 o Code refactoring:
18625 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18626 TCP ports to forward. In the past it only accepted two ports:
18627 the ORPort and the DirPort.
18630 Changes in version 0.2.4.1-alpha - 2012-09-05
18631 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18632 bridgedb; lets relays use IPv6 addresses and directory authorities
18633 advertise them; and switches to a cleaner build interface.
18635 This is the first alpha release in a new series, so expect there to
18636 be bugs. Users who would rather test out a more stable branch should
18637 stay with 0.2.3.x for now.
18639 o Major features (bridges):
18640 - Bridges now report the pluggable transports they support to the
18641 bridge authority, so it can pass the supported transports on to
18642 bridgedb and/or eventually do reachability testing. Implements
18645 o Major features (IPv6):
18646 - Bridge authorities now accept IPv6 bridge addresses and include
18647 them in network status documents. Implements ticket 5534.
18648 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18649 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18650 to happen. Implements ticket 5535.
18651 - All kind of relays, not just bridges, can now advertise an IPv6
18652 OR port. Implements ticket 6362.
18653 - Directory authorities vote on IPv6 OR ports using the new consensus
18654 method 14. Implements ticket 6363.
18656 o Major features (build):
18657 - Switch to a nonrecursive Makefile structure. Now instead of each
18658 Makefile.am invoking other Makefile.am's, there is a master
18659 Makefile.am that includes the others. This change makes our build
18660 process slightly more maintainable, and improves parallelism for
18661 building with make -j. Original patch by Stewart Smith; various
18662 fixes by Jim Meyering.
18663 - Where available, we now use automake's "silent" make rules by
18664 default, so that warnings are easier to spot. You can get the old
18665 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18667 o Minor features (code security and spec conformance):
18668 - Clear keys and key-derived material left on the stack in
18669 rendservice.c and rendclient.c. Check return value of
18670 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18671 These fixes should make us more forward-secure against cold-boot
18672 attacks and the like. Fixes bug 2385.
18673 - Reject EXTEND cells sent to nonexistent streams. According to the
18674 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18675 we were only checking for stream IDs that were currently in use.
18676 Found while hunting for more instances of bug 6271. Bugfix on
18677 0.0.2pre8, which introduced incremental circuit construction.
18679 o Minor features (streamlining);
18680 - No longer include the "opt" prefix when generating routerinfos
18681 or v2 directories: it has been needless since Tor 0.1.2. Closes
18683 - Remove some now-needless code that tried to aggressively flush
18684 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18685 cell queue logic has saved us from the failure mode that this code
18686 was supposed to prevent. Removing this code will limit the number
18687 of baroque control flow paths through Tor's network logic. Reported
18688 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18690 o Minor features (controller):
18691 - Add a "GETINFO signal/names" control port command. Implements
18693 - Provide default values for all options via "GETINFO config/defaults".
18694 Implements ticket 4971.
18696 o Minor features (IPv6):
18697 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18698 authorities should set if they have IPv6 connectivity and want to
18699 do reachability tests for IPv6 relays. Implements feature 5974.
18700 - A relay with an IPv6 OR port now sends that address in NETINFO
18701 cells (in addition to its other address). Implements ticket 6364.
18703 o Minor features (log messages):
18704 - Omit the first heartbeat log message, because it never has anything
18705 useful to say, and it clutters up the bootstrapping messages.
18706 Resolves ticket 6758.
18707 - Don't log about reloading the microdescriptor cache at startup. Our
18708 bootstrap warnings are supposed to tell the user when there's a
18709 problem, and our bootstrap notices say when there isn't. Resolves
18710 ticket 6759; bugfix on 0.2.2.6-alpha.
18711 - Don't log "I learned some more directory information" when we're
18712 reading cached directory information. Reserve it for when new
18713 directory information arrives in response to a fetch. Resolves
18715 - Prevent rounding error in path bias counts when scaling
18716 them down, and use the correct scale factor default. Also demote
18717 some path bias related log messages down a level and make others
18718 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18719 - We no longer warn so much when generating manpages from their
18722 o Code simplifications and refactoring:
18723 - Enhance our internal sscanf replacement so that we can eliminate
18724 the last remaining uses of the system sscanf. (Though those uses
18725 of sscanf were safe, sscanf itself is generally error prone, so
18726 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18728 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18729 - Move last_reachable and testing_since from routerinfo_t to node_t.
18730 Implements ticket 5529.
18731 - Add replaycache_t structure, functions and unit tests, then refactor
18732 rend_service_introduce() to be more clear to read, improve, debug,
18733 and test. Resolves bug 6177.
18734 - Finally remove support for malloc_good_size and malloc_usable_size.
18735 We had hoped that these functions would let us eke a little more
18736 memory out of our malloc implementation. Unfortunately, the only
18737 implementations that provided these functions are also ones that
18738 are already efficient about not overallocation: they never got us
18739 more than 7 or so bytes per allocation. Removing them saves us a
18740 little code complexity and a nontrivial amount of build complexity.
18742 o New requirements:
18743 - Tor maintainers now require Automake version 1.9 or later to build
18744 Tor from the Git repository. (Automake is not required when building
18745 from a source distribution.)
18748 Changes in version 0.2.3.21-rc - 2012-09-05
18749 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
18750 series. It fixes a trio of potential security bugs, fixes a bug where
18751 we were leaving some of the fast relays out of the microdescriptor
18752 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
18753 and cleans up other smaller issues.
18755 o Major bugfixes (security):
18756 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18757 could use this trick to make their circuits receive cells faster
18758 than our flow control would have allowed, or to gum up the network,
18759 or possibly to do targeted memory denial-of-service attacks on
18760 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18761 from July 2002, before the release of Tor 0.0.0. We had committed
18762 this patch previously, but we had to revert it because of bug 6271.
18763 Now that 6271 is fixed, this patch appears to work.
18764 - Reject any attempt to extend to an internal address. Without
18765 this fix, a router could be used to probe addresses on an internal
18766 network to see whether they were accepting connections. Fixes bug
18767 6710; bugfix on 0.0.8pre1.
18768 - Do not crash when comparing an address with port value 0 to an
18769 address policy. This bug could have been used to cause a remote
18770 assertion failure by or against directory authorities, or to
18771 allow some applications to crash clients. Fixes bug 6690; bugfix
18775 - Remove the upper bound on microdescriptor length. We were hitting
18776 the limit for routers with complex exit policies or family
18777 declarations, causing clients to not use them. Fixes the first
18778 piece of bug 6404; fix on 0.2.2.6-alpha.
18779 - Detect "ORPort 0" as meaning, uniformly, that we're not running
18780 as a relay. Previously, some of our code would treat the presence
18781 of any ORPort line as meaning that we should act like a relay,
18782 even though our new listener code would correctly not open any
18783 ORPorts for ORPort 0. Similar bugs in other Port options are also
18784 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
18787 - Avoid a pair of double-free and use-after-mark bugs that can
18788 occur with certain timings in canceled and re-received DNS
18789 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18790 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18791 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18792 - Allow one-hop directory fetching circuits the full "circuit build
18793 timeout" period, rather than just half of it, before failing them
18794 and marking the relay down. This fix should help reduce cases where
18795 clients declare relays (or worse, bridges) unreachable because
18796 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18797 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18799 - Authorities no longer include any router in their microdescriptor
18800 consensuses for which they couldn't generate or agree on a
18801 microdescriptor. Fixes the second piece of bug 6404; fix on
18803 - Detect and reject attempts to specify both "FooPort" and
18804 "FooPort 0" in the same configuration domain. (It's still okay
18805 to have a FooPort in your configuration file, and use "FooPort 0"
18806 on the command line to disable it.) Fixes the second half of bug
18807 6507; bugfix on 0.2.3.3-alpha.
18808 - Make wildcarded addresses (that is, ones beginning with "*.") work
18809 when provided via the controller's MapAddress command. Previously,
18810 they were accepted, but we never actually noticed that they were
18811 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
18812 - Avoid crashing on a malformed state file where EntryGuardPathBias
18813 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
18814 - Add a (probably redundant) memory clear between iterations of
18815 the router status voting loop, to prevent future coding errors
18816 where data might leak between iterations of the loop. Resolves
18819 o Minor bugfixes (log messages):
18820 - Downgrade "set buildtimeout to low value" messages to "info"
18821 severity; they were never an actual problem, there was never
18822 anything reasonable to do about them, and they tended to spam logs
18823 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18824 - Downgrade path-bias warning messages to "info". We'll try to get
18825 them working better in 0.2.4. Add internal circuit construction
18826 state to protect against the noisy warn message "Unexpectedly high
18827 circuit_successes". Also add some additional rate-limited notice
18828 messages to help determine the root cause of the warn. Fixes bug
18829 6475. Bugfix against 0.2.3.17-beta.
18830 - Move log message when unable to find a microdesc in a routerstatus
18831 entry to parse time. Previously we'd spam this warning every time
18832 we tried to figure out which microdescriptors to download. Fixes
18833 the third piece of bug 6404; fix on 0.2.3.18-rc.
18836 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
18837 change when the authority is deciding whether to accept a newly
18838 uploaded descriptor. Implements ticket 6423.
18839 - Add missing documentation for consensus and microdesc files.
18840 Resolves ticket 6732.
18843 Changes in version 0.2.2.38 - 2012-08-12
18844 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
18845 attack that could in theory leak path information.
18848 - Avoid an uninitialized memory read when reading a vote or consensus
18849 document that has an unrecognized flavor name. This read could
18850 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18851 - Try to leak less information about what relays a client is
18852 choosing to a side-channel attacker. Previously, a Tor client would
18853 stop iterating through the list of available relays as soon as it
18854 had chosen one, thus finishing a little earlier when it picked
18855 a router earlier in the list. If an attacker can recover this
18856 timing information (nontrivial but not proven to be impossible),
18857 they could learn some coarse-grained information about which relays
18858 a client was picking (middle nodes in particular are likelier to
18859 be affected than exits). The timing attack might be mitigated by
18860 other factors (see bug 6537 for some discussion), but it's best
18861 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18864 Changes in version 0.2.3.20-rc - 2012-08-05
18865 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
18866 series. It fixes a pair of code security bugs and a potential anonymity
18867 issue, updates our RPM spec files, and cleans up other smaller issues.
18870 - Avoid read-from-freed-memory and double-free bugs that could occur
18871 when a DNS request fails while launching it. Fixes bug 6480;
18872 bugfix on 0.2.0.1-alpha.
18873 - Avoid an uninitialized memory read when reading a vote or consensus
18874 document that has an unrecognized flavor name. This read could
18875 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18876 - Try to leak less information about what relays a client is
18877 choosing to a side-channel attacker. Previously, a Tor client would
18878 stop iterating through the list of available relays as soon as it
18879 had chosen one, thus finishing a little earlier when it picked
18880 a router earlier in the list. If an attacker can recover this
18881 timing information (nontrivial but not proven to be impossible),
18882 they could learn some coarse-grained information about which relays
18883 a client was picking (middle nodes in particular are likelier to
18884 be affected than exits). The timing attack might be mitigated by
18885 other factors (see bug 6537 for some discussion), but it's best
18886 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18889 - Try to make the warning when giving an obsolete SOCKSListenAddress
18890 a little more useful.
18891 - Terminate active server managed proxies if Tor stops being a
18892 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
18893 - Provide a better error message about possible OSX Asciidoc failure
18894 reasons. Fixes bug 6436.
18895 - Warn when Tor is configured to use accounting in a way that can
18896 link a hidden service to some other hidden service or public
18897 address. Resolves ticket 6490.
18900 - Check return value of fputs() when writing authority certificate
18901 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18902 - Ignore ServerTransportPlugin lines when Tor is not configured as
18903 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
18904 - When disabling guards for having too high a proportion of failed
18905 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
18909 - Update our default RPM spec files to work with mock and rpmbuild
18910 on RHEL/Fedora. They have an updated set of dependencies and
18911 conflicts, a fix for an ancient typo when creating the "_tor"
18912 user, and better instructions. Thanks to Ondrej Mikle for the
18913 patch series. Fixes bug 6043.
18916 - Make it possible to set the TestingTorNetwork configuration
18917 option using AlternateDirAuthority and AlternateBridgeAuthority
18918 as an alternative to setting DirServer. Addresses ticket 6377.
18921 - Clarify the documentation for the Alternate*Authority options.
18923 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18925 o Code simplification and refactoring:
18926 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18927 10 lines. Also, don't nest them. Doing so in the past has
18928 led to hard-to-debug code. The new style is to use the
18929 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18932 Changes in version 0.2.3.19-rc - 2012-07-06
18933 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
18934 series. It fixes the compile on Windows, reverts to a GeoIP database
18935 that isn't as broken, and fixes a flow control bug that has been around
18936 since the beginning of Tor.
18939 - Fix a bug handling SENDME cells on nonexistent streams that could
18940 result in bizarre window values. Report and patch contributed
18941 pseudonymously. Fixes part of bug 6271. This bug was introduced
18942 before the first Tor release, in svn commit r152.
18943 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
18944 June 2012 database, Maxmind marked many Tor relays as country "A1",
18945 which will cause risky behavior for clients that set EntryNodes
18946 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
18947 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
18948 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
18951 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18952 bugfix on 0.2.1.10-alpha.
18955 Changes in version 0.2.3.18-rc - 2012-06-28
18956 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
18957 series. It fixes a few smaller bugs, but generally appears stable.
18958 Please test it and let us know whether it is!
18961 - Allow wildcarded mapaddress targets to be specified on the
18962 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
18963 - Make our linker option detection code more robust against linkers
18964 such as on FreeBSD 8, where a bad combination of options completes
18965 successfully but makes an unrunnable binary. Fixes bug 6173;
18966 bugfix on 0.2.3.17-beta.
18968 o Minor bugfixes (on 0.2.2.x and earlier):
18969 - Avoid a false positive in the util/threads unit test by increasing
18970 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18971 - Replace "Sending publish request" log messages with "Launching
18972 upload", so that they no longer confusingly imply that we're
18973 sending something to a directory we might not even be connected
18974 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18975 - Make sure to set *socket_error in all error cases in
18976 connection_connect(), so it can't produce a warning about
18977 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18978 0.2.1.1-alpha; resolves ticket 6028.
18979 - Downgrade "Got a certificate, but we already have it" log messages
18980 from warning to info, except when we're a dirauth. Fixes bug 5238;
18981 bugfix on 0.2.1.7-alpha.
18982 - When checking for requested signatures on the latest consensus
18983 before serving it to a client, make sure to check the right
18984 consensus flavor. Bugfix on 0.2.2.6-alpha.
18985 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18986 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18988 o Minor bugfixes (on 0.2.3.x):
18989 - Make format_helper_exit_status() avoid unnecessary space padding
18990 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
18992 - Downgrade a message about cleaning the microdescriptor cache to
18993 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
18994 - Log a BUG message at severity INFO if we have a networkstatus with
18995 a missing entry for some microdescriptor. Continues on a patch
18997 - Improve the log message when a managed proxy fails to launch. Fixes
18998 bug 5099; bugfix on 0.2.3.6-alpha.
18999 - Don't do DNS lookups when parsing corrupted managed proxy protocol
19000 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
19001 - When formatting wildcarded address mappings for the controller,
19002 be sure to include "*." as appropriate. Partially fixes bug 6244;
19003 bugfix on 0.2.3.9-alpha.
19004 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
19005 Bugfix on 0.2.3.13-alpha.
19006 - Stop logging messages about running with circuit timeout learning
19007 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
19008 - Disable a spurious warning about reading on a marked and flushing
19009 connection. We shouldn't be doing that, but apparently we
19010 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
19011 - Fix a bug that stopped AllowDotExit from working on addresses
19012 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
19015 o Code simplification, refactoring, unit tests:
19016 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
19017 Libevent's notion of cached time when possible.
19018 - Remove duplicate code for invoking getrlimit() from control.c.
19019 - Add a unit test for the environment_variable_names_equal function.
19022 - Document the --defaults-torrc option, and the new (in 0.2.3)
19023 semantics for overriding, extending, and clearing lists of
19024 options. Closes bug 4748.
19027 Changes in version 0.2.3.17-beta - 2012-06-15
19028 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
19029 gets our TLS handshake back on track for being able to blend in with
19030 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
19031 with Vidalia, and otherwise continues to get us closer to a release
19035 - Enable gcc and ld hardening by default. Resolves ticket 5210.
19036 - Update TLS cipher list to match Firefox 8 and later. Resolves
19038 - Implement the client side of proposal 198: remove support for
19039 clients falsely claiming to support standard ciphersuites that
19040 they can actually provide. As of modern OpenSSL versions, it's not
19041 necessary to fake any standard ciphersuite, and doing so prevents
19042 us from using better ciphersuites in the future, since servers
19043 can't know whether an advertised ciphersuite is really supported or
19044 not. Some hosts -- notably, ones with very old versions of OpenSSL
19045 or where OpenSSL has been built with ECC disabled -- will stand
19046 out because of this change; TBB users should not be affected.
19049 - Change the default value for DynamicDHGroups (introduced in
19050 0.2.3.9-alpha) to 0. This feature can make Tor relays less
19051 identifiable by their use of the mod_ssl DH group, but at
19052 the cost of some usability (#4721) and bridge tracing (#6087)
19053 regressions. Resolves ticket 5598.
19054 - Send a CRLF at the end of each STATUS_* control protocol event. This
19055 bug tickled a bug in Vidalia which would make it freeze. Fixes
19056 bug 6094; bugfix on 0.2.3.16-alpha.
19059 - Disable writing on marked-for-close connections when they are
19060 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
19061 bug 5263; bugfix on 0.0.2pre13, where we first added a special
19062 case for flushing marked connections.
19063 - Detect SSL handshake even when the initial attempt to write the
19064 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
19065 - Change the AllowDotExit rules so they should actually work.
19066 We now enforce AllowDotExit only immediately after receiving an
19067 address via SOCKS or DNSPort: other sources are free to provide
19068 .exit addresses after the resolution occurs. Fixes bug 3940;
19069 bugfix on 0.2.2.1-alpha.
19070 - Fix a (harmless) integer overflow in cell statistics reported by
19071 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19072 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
19073 right places and never depends on the consensus parameters or
19074 computes adaptive timeouts when it is disabled. Fixes bug 5049;
19075 bugfix on 0.2.2.14-alpha.
19076 - When building Tor on Windows with -DUNICODE (not default), ensure
19077 that error messages, filenames, and DNS server names are always
19078 NUL-terminated when we convert them to a single-byte encoding.
19079 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19080 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
19081 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
19082 - Fix an edge case where TestingTorNetwork is set but the authorities
19083 and relays all have an uptime of zero, where the private Tor network
19084 could briefly lack support for hidden services. Fixes bug 3886;
19085 bugfix on 0.2.2.18-alpha.
19086 - Correct the manpage's descriptions for the default values of
19087 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
19089 - Fix the documentation for the --hush and --quiet command line
19090 options, which changed their behavior back in 0.2.3.3-alpha.
19091 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
19095 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
19096 more information to it, so that we can track it down in case it
19097 returns again. Mitigates bug 5235.
19098 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
19099 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
19100 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
19101 - Warn the user when HTTPProxy, but no other proxy type, is
19102 configured. This can cause surprising behavior: it doesn't send
19103 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19104 directory traffic only. Resolves ticket 4663.
19105 - Issue a notice if a guard completes less than 40% of your circuits.
19106 Threshold is configurable by torrc option PathBiasNoticeRate and
19107 consensus parameter pb_noticepct. There is additional, off-by-
19108 default code to disable guards which fail too many circuits.
19109 Addresses ticket 5458.
19110 - Update to the June 6 2012 Maxmind GeoLite Country database.
19112 o Code simplifications and refactoring:
19113 - Remove validate_pluggable_transports_config(): its warning
19114 message is now handled by connection_or_connect().
19117 Changes in version 0.2.2.37 - 2012-06-06
19118 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19119 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19123 - Work around a bug in OpenSSL that broke renegotiation with TLS
19124 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19125 the v2 Tor connection protocol when both sides were using OpenSSL
19126 1.0.1 would fail. Resolves ticket 6033.
19127 - When waiting for a client to renegotiate, don't allow it to add
19128 any bytes to the input buffer. This fixes a potential DoS issue.
19129 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19130 - Fix an edge case where if we fetch or publish a hidden service
19131 descriptor, we might build a 4-hop circuit and then use that circuit
19132 for exiting afterwards -- even if the new last hop doesn't obey our
19133 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19136 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19137 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19140 - Tell GCC and Clang to check for any errors in format strings passed
19141 to the tor_v*(print|scan)f functions.
19144 Changes in version 0.2.3.16-alpha - 2012-06-05
19145 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
19146 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19147 currently). It also fixes a variety of smaller bugs and other cleanups
19148 that get us closer to a release candidate.
19150 o Major bugfixes (general):
19151 - Work around a bug in OpenSSL that broke renegotiation with TLS
19152 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19153 the v2 Tor connection protocol when both sides were using OpenSSL
19154 1.0.1 would fail. Resolves ticket 6033.
19155 - When waiting for a client to renegotiate, don't allow it to add
19156 any bytes to the input buffer. This fixes a potential DoS issue.
19157 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19158 - Pass correct OR address to managed proxies (like obfsproxy),
19159 even when ORListenAddress is used. Fixes bug 4865; bugfix on
19161 - The advertised platform of a router now includes only its operating
19162 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
19163 service pack level (for Windows) or its CPU architecture (for Unix).
19164 We also no longer include the "git-XYZ" tag in the version. Resolves
19167 o Major bugfixes (clients):
19168 - If we are unable to find any exit that supports our predicted ports,
19169 stop calling them predicted, so that we don't loop and build
19170 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19171 which introduced predicted ports.
19172 - Fix an edge case where if we fetch or publish a hidden service
19173 descriptor, we might build a 4-hop circuit and then use that circuit
19174 for exiting afterwards -- even if the new last hop doesn't obey our
19175 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19176 - Check at each new consensus whether our entry guards were picked
19177 long enough ago that we should rotate them. Previously, we only
19178 did this check at startup, which could lead to us holding a guard
19179 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19180 - When fetching a bridge descriptor from a bridge authority,
19181 always do so anonymously, whether we have been able to open
19182 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19183 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19184 but we'll need to wait for bug 6010 before it's actually usable.
19186 o Major bugfixes (directory authorities):
19187 - When computing weight parameters, behave more robustly in the
19188 presence of a bad bwweightscale value. Previously, the authorities
19189 would crash if they agreed on a sufficiently broken weight_scale
19190 value: now, they use a reasonable default and carry on. Partial
19191 fix for 5786; bugfix on 0.2.2.17-alpha.
19192 - Check more thoroughly to prevent a rogue authority from
19193 double-voting on any consensus directory parameter. Previously,
19194 authorities would crash in this case if the total number of
19195 votes for any parameter exceeded the number of active voters,
19196 but would let it pass otherwise. Partial fix for bug 5786; bugfix
19200 - Rate-limit log messages when asked to connect anonymously to
19201 a private address. When these hit, they tended to hit fast and
19202 often. Also, don't bother trying to connect to addresses that we
19203 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19204 reply makes us think we have been lied to, even when the address the
19205 client tried to connect to was "localhost." Resolves ticket 2822.
19206 - Allow packagers to insert an extra string in server descriptor
19207 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
19208 Resolves the rest of ticket 2988.
19209 - Raise the threshold of server descriptors needed (75%) and exit
19210 server descriptors needed (50%) before we will declare ourselves
19211 bootstrapped. This will make clients start building circuits a
19212 little later, but makes the initially constructed circuits less
19213 skewed and less in conflict with further directory fetches. Fixes
19215 - Close any connection that sends unrecognized junk before the
19216 handshake. Solves an issue noted in bug 4369.
19217 - Improve log messages about managed transports. Resolves ticket 5070.
19218 - Tag a bridge's descriptor as "never to be sent unencrypted".
19219 This shouldn't matter, since bridges don't open non-anonymous
19220 connections to the bridge authority and don't allow unencrypted
19221 directory connections from clients, but we might as well make
19222 sure. Closes bug 5139.
19223 - Expose our view of whether we have gone dormant to the controller,
19224 via a new "GETINFO dormant" value. Torbutton and other controllers
19225 can use this to avoid doing periodic requests through Tor while
19226 it's dormant (bug 4718). Fixes bug 5954.
19227 - Tell GCC and Clang to check for any errors in format strings passed
19228 to the tor_v*(print|scan)f functions.
19229 - Update to the May 1 2012 Maxmind GeoLite Country database.
19231 o Minor bugfixes (already included in 0.2.2.36):
19232 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19233 Fixes bug 5346; bugfix on 0.0.8pre3.
19234 - Correct parsing of certain date types in parse_http_time().
19235 Without this patch, If-Modified-Since would behave
19236 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19237 Esteban Manchado Velázques.
19238 - Make our number-parsing functions always treat too-large values
19239 as an error, even when those values exceed the width of the
19240 underlying type. Previously, if the caller provided these
19241 functions with minima or maxima set to the extreme values of the
19242 underlying integer type, these functions would return those
19243 values on overflow rather than treating overflow as an error.
19244 Fixes part of bug 5786; bugfix on 0.0.9.
19245 - If we hit the error case where routerlist_insert() replaces an
19246 existing (old) server descriptor, make sure to remove that
19247 server descriptor from the old_routers list. Fix related to bug
19248 1776. Bugfix on 0.2.2.18-alpha.
19249 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19250 circuits. Fixes issue 5259.
19252 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
19253 - Prevent a null-pointer dereference when receiving a data cell
19254 for a nonexistent stream when the circuit in question has an
19255 empty deliver window. We don't believe this is triggerable,
19256 since we don't currently allow deliver windows to become empty,
19257 but the logic is tricky enough that it's better to make the code
19258 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19259 - Fix a memory leak when trying to launch a DNS request when the
19260 network is disabled or the nameservers are unconfigurable. Fixes
19261 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
19262 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
19263 - Don't hold a Windows file handle open for every file mapping;
19264 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19266 - Avoid O(n^2) performance characteristics when parsing a large
19267 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19268 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19269 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19271 - Make our replacement implementation of strtok_r() compatible with
19272 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19273 bugfix on 0.2.2.1-alpha.
19274 - Fix a NULL-pointer dereference on a badly formed
19275 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
19276 bugfix on 0.2.2.9-alpha.
19277 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19278 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19279 - Defensively refactor rend_mid_rendezvous() so that protocol
19280 violations and length checks happen in the beginning. Fixes
19282 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19283 that IPv6 stuff will compile on MSVC, and compilation issues
19284 will be easier to track down. Fixes bug 5861.
19286 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
19287 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19288 resource exhaustion, so that clients can adjust their load to
19289 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19290 started using END_STREAM_REASON_RESOURCELIMIT.
19291 - Don't check for whether the address we're using for outbound
19292 connections has changed until after the outbound connection has
19293 completed. On Windows, getsockname() doesn't succeed until the
19294 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19295 - If the configuration tries to set MyFamily on a bridge, refuse to
19296 do so, and warn about the security implications. Fixes bug 4657;
19297 bugfix on 0.2.0.3-alpha.
19298 - If the client fails to set a reasonable set of ciphersuites
19299 during its v2 handshake renegotiation, allow the renegotiation to
19300 continue nevertheless (i.e. send all the required certificates).
19301 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19302 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19303 option is set to 0 (which Vidalia version 0.2.16 now does when
19304 a SAVECONF attempt fails), perform other actions that SIGHUP
19305 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19307 - If we fail to write a microdescriptor to the disk cache, do not
19308 continue replacing the old microdescriptor file. Fixes bug 2954;
19309 bugfix on 0.2.2.6-alpha.
19310 - Exit nodes don't need to fetch certificates for authorities that
19311 they don't recognize; only directory authorities, bridges,
19312 and caches need to do that. Fixes part of bug 2297; bugfix on
19314 - Correctly handle checking the permissions on the parent
19315 directory of a control socket in the root directory. Bug found
19316 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19318 - When told to add a bridge with the same digest as a preexisting
19319 bridge but a different addr:port, change the addr:port as
19320 requested. Previously we would not notice the change. Fixes half
19321 of bug 5603; fix on 0.2.2.26-beta.
19322 - End AUTHCHALLENGE error messages (in the control protocol) with
19323 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
19325 o Minor bugfixes (on 0.2.3.x):
19326 - Turn an assertion (that the number of handshakes received as a
19327 server is not < 1) into a warning. Fixes bug 4873; bugfix on
19329 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
19330 we had reversed them when the answer was cached.) Fixes bug
19331 5723; bugfix on 0.2.3.1-alpha.
19332 - Work correctly on Linux systems with accept4 support advertised in
19333 their headers, but without accept4 support in the kernel. Fix
19334 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
19335 - When told to add a bridge with the same addr:port as a preexisting
19336 bridge but a different transport, change the transport as
19337 requested. Previously we would not notice the change. Fixes half
19338 of bug 5603; fix on 0.2.3.2-alpha.
19339 - Avoid a "double-reply" warning when replying to a SOCKS request
19340 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
19341 bugfix on 0.2.3.4-alpha.
19342 - Fix a bug where a bridge authority crashes if it has seen no
19343 directory requests when it's time to write statistics to disk.
19344 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
19346 - Don't try to open non-control listeners when DisableNetwork is set.
19347 Previously, we'd open all listeners, then immediately close them.
19348 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
19349 - Don't abort the managed proxy protocol if the managed proxy
19350 sends us an unrecognized line; ignore it instead. Fixes bug
19351 5910; bugfix on 0.2.3.9-alpha.
19352 - Fix a compile warning in crypto.c when compiling with clang 3.1.
19353 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
19354 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
19355 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
19356 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
19357 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
19358 - Resolve numerous small warnings and build issues with MSVC. Resolves
19361 o Documentation fixes:
19362 - Improve the manual's documentation for the NT Service command-line
19363 options. Addresses ticket 3964.
19364 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19365 - Document the changes to the ORPort and DirPort options, and the
19366 fact that {OR/Dir}ListenAddress is now unnecessary (and
19367 therefore deprecated). Resolves ticket 5597.
19370 - Remove the torrc.bridge file: we don't use it for anything, and
19371 it had become badly desynchronized from torrc.sample. Resolves
19375 Changes in version 0.2.2.36 - 2012-05-24
19376 Tor 0.2.2.36 updates the addresses for two of the eight directory
19377 authorities, fixes some potential anonymity and security issues,
19378 and fixes several crash bugs.
19380 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19381 known flaws, and nobody should be using them. You should upgrade. If
19382 you're using a Linux or BSD and its packages are obsolete, stop using
19383 those packages and upgrade anyway.
19385 o Directory authority changes:
19386 - Change IP address for maatuska (v3 directory authority).
19387 - Change IP address for ides (v3 directory authority), and rename
19391 - When building or running with any version of OpenSSL earlier
19392 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19393 versions have a bug (CVE-2011-4576) in which their block cipher
19394 padding includes uninitialized data, potentially leaking sensitive
19395 information to any peer with whom they make a SSLv3 connection. Tor
19396 does not use SSL v3 by default, but a hostile client or server
19397 could force an SSLv3 connection in order to gain information that
19398 they shouldn't have been able to get. The best solution here is to
19399 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19400 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19401 to make sure that the bug can't happen.
19402 - Never use a bridge or a controller-supplied node as an exit, even
19403 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19404 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19405 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19406 - Only build circuits if we have a sufficient threshold of the total
19407 descriptors that are marked in the consensus with the "Exit"
19408 flag. This mitigates an attack proposed by wanoskarnet, in which
19409 all of a client's bridges collude to restrict the exit nodes that
19410 the client knows about. Fixes bug 5343.
19411 - Provide controllers with a safer way to implement the cookie
19412 authentication mechanism. With the old method, if another locally
19413 running program could convince a controller that it was the Tor
19414 process, then that program could trick the controller into telling
19415 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19416 authentication method uses a challenge-response approach to prevent
19417 this attack. Fixes bug 5185; implements proposal 193.
19420 - Avoid logging uninitialized data when unable to decode a hidden
19421 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19422 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19423 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19425 - Fix builds when the path to sed, openssl, or sha1sum contains
19426 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19428 - Correct our replacements for the timeradd() and timersub() functions
19429 on platforms that lack them (for example, Windows). The timersub()
19430 function is used when expiring circuits, while timeradd() is
19431 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19432 bugfix on 0.2.2.24-alpha.
19433 - Fix the SOCKET_OK test that we use to tell when socket
19434 creation fails so that it works on Win64. Fixes part of bug 4533;
19435 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19438 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19439 Fixes bug 5346; bugfix on 0.0.8pre3.
19440 - Make our number-parsing functions always treat too-large values
19441 as an error, even when those values exceed the width of the
19442 underlying type. Previously, if the caller provided these
19443 functions with minima or maxima set to the extreme values of the
19444 underlying integer type, these functions would return those
19445 values on overflow rather than treating overflow as an error.
19446 Fixes part of bug 5786; bugfix on 0.0.9.
19447 - Older Linux kernels erroneously respond to strange nmap behavior
19448 by having accept() return successfully with a zero-length
19449 socket. When this happens, just close the connection. Previously,
19450 we would try harder to learn the remote address: but there was
19451 no such remote address to learn, and our method for trying to
19452 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19453 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19454 - Correct parsing of certain date types in parse_http_time().
19455 Without this patch, If-Modified-Since would behave
19456 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19457 Esteban Manchado Velázques.
19458 - Change the BridgePassword feature (part of the "bridge community"
19459 design, which is not yet implemented) to use a time-independent
19460 comparison. The old behavior might have allowed an adversary
19461 to use timing to guess the BridgePassword value. Fixes bug 5543;
19462 bugfix on 0.2.0.14-alpha.
19463 - Detect and reject certain misformed escape sequences in
19464 configuration values. Previously, these values would cause us
19465 to crash if received in a torrc file or over an authenticated
19466 control port. Bug found by Esteban Manchado Velázquez, and
19467 independently by Robert Connolly from Matta Consulting who further
19468 noted that it allows a post-authentication heap overflow. Patch
19469 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19470 bugfix on 0.2.0.16-alpha.
19471 - Fix a compile warning when using the --enable-openbsd-malloc
19472 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19473 - During configure, detect when we're building with clang version
19474 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19475 CFLAGS. clang doesn't support them yet.
19476 - When sending an HTTP/1.1 proxy request, include a Host header.
19477 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19478 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19479 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19480 - If we hit the error case where routerlist_insert() replaces an
19481 existing (old) server descriptor, make sure to remove that
19482 server descriptor from the old_routers list. Fix related to bug
19483 1776. Bugfix on 0.2.2.18-alpha.
19485 o Minor bugfixes (documentation and log messages):
19486 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19487 Fixes bug 4856; bugfix on Tor 0.0.6.
19488 - Update "ClientOnly" man page entry to explain that there isn't
19489 really any point to messing with it. Resolves ticket 5005.
19490 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19491 directory authority option (introduced in Tor 0.2.2.34).
19492 - Downgrade the "We're missing a certificate" message from notice
19493 to info: people kept mistaking it for a real problem, whereas it
19494 is seldom the problem even when we are failing to bootstrap. Fixes
19495 bug 5067; bugfix on 0.2.0.10-alpha.
19496 - Correctly spell "connect" in a log message on failure to create a
19497 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19498 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19499 circuits. Fixes issue 5259.
19502 - Directory authorities now reject versions of Tor older than
19503 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19504 inclusive. These versions accounted for only a small fraction of
19505 the Tor network, and have numerous known security issues. Resolves
19507 - Update to the May 1 2012 Maxmind GeoLite Country database.
19510 - When sending or relaying a RELAY_EARLY cell, we used to convert
19511 it to a RELAY cell if the connection was using the v1 link
19512 protocol. This was a workaround for older versions of Tor, which
19513 didn't handle RELAY_EARLY cells properly. Now that all supported
19514 versions can handle RELAY_EARLY cells, and now that we're enforcing
19515 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19516 remove this workaround. Addresses bug 4786.
19519 Changes in version 0.2.3.15-alpha - 2012-04-30
19520 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
19521 the development branch build on Windows again.
19523 o Minor bugfixes (on 0.2.2.x and earlier):
19524 - Make sure that there are no unhandled pending TLS errors before
19525 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19526 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19527 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19528 - Fix an assert that directory authorities could trigger on sighup
19529 during some configuration state transitions. We now don't treat
19530 it as a fatal error when the new descriptor we just generated in
19531 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19532 - After we pick a directory mirror, we would refuse to use it if
19533 it's in our ExcludeExitNodes list, resulting in mysterious failures
19534 to bootstrap for people who just wanted to avoid exiting from
19535 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19536 - When building with --enable-static-tor on OpenBSD, do not
19537 erroneously attempt to link -lrt. Fixes bug 5103.
19539 o Minor bugfixes (on 0.2.3.x):
19540 - When Tor is built with kernel headers from a recent (last few
19541 years) Linux kernel, do not fail to run on older (pre-2.6.28
19542 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19543 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19544 and 0.2.3.12-alpha.
19545 - Fix compilation with miniupnpc version 1.6; patch from
19546 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19547 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19548 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19549 - Fix compilation on platforms without unistd.h, or where environ
19550 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19553 - Directory authorities are now a little more lenient at accepting
19554 older router descriptors, or newer router descriptors that don't
19555 make big changes. This should help ameliorate past and future
19556 issues where routers think they have uploaded valid descriptors,
19557 but the authorities don't think so. Fix for ticket 2479.
19558 - Make the code that clients use to detect an address change be
19559 IPv6-aware, so that it won't fill clients' logs with error
19560 messages when trying to get the IPv4 address of an IPv6
19561 connection. Implements ticket 5537.
19563 o Removed features:
19564 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19565 authorities needed to use it for a while to keep the network working
19566 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19567 that was six months ago. As of now, it should no longer be needed
19571 Changes in version 0.2.3.14-alpha - 2012-04-23
19572 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19573 candidate. It also dramatically speeds up AES: fast relays should
19574 consider switching to the newer OpenSSL library.
19576 o Directory authority changes:
19577 - Change IP address for ides (v3 directory authority), and rename
19581 - Avoid logging uninitialized data when unable to decode a hidden
19582 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19583 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19584 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19586 - If authorities are unable to get a v2 consensus document from other
19587 directory authorities, they no longer fall back to fetching
19588 them from regular directory caches. Fixes bug 5635; bugfix on
19589 0.2.2.26-beta, where routers stopped downloading v2 consensus
19590 documents entirely.
19591 - When we start a Tor client with a normal consensus already cached,
19592 be willing to download a microdescriptor consensus. Fixes bug 4011;
19593 fix on 0.2.3.1-alpha.
19595 o Major features (performance):
19596 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19597 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19598 vectorized AES implementations as appropriate. These can be much,
19599 much faster than other AES implementations.
19601 o Minor bugfixes (0.2.2.x and earlier):
19602 - Don't launch more than 10 service-side introduction-point circuits
19603 for a hidden service in five minutes. Previously, we would consider
19604 launching more introduction-point circuits if at least one second
19605 had passed without any introduction-point circuits failing. Fixes
19606 bug 4607; bugfix on 0.0.7pre1.
19607 - Change the BridgePassword feature (part of the "bridge community"
19608 design, which is not yet implemented) to use a time-independent
19609 comparison. The old behavior might have allowed an adversary
19610 to use timing to guess the BridgePassword value. Fixes bug 5543;
19611 bugfix on 0.2.0.14-alpha.
19612 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19613 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19614 - When sending an HTTP/1.1 proxy request, include a Host header.
19615 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19616 - Don't log that we have "decided to publish new relay descriptor"
19617 unless we are actually publishing a descriptor. Fixes bug 3942;
19618 bugfix on 0.2.2.28-beta.
19620 o Minor bugfixes (0.2.3.x):
19621 - Fix a bug where a bridge authority crashes (on a failed assert)
19622 if it has seen no directory requests when it's time to write
19623 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19624 - Fix bug stomping on ORPort option NoListen and ignoring option
19625 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19626 - In the testsuite, provide a large enough buffer in the tor_sscanf
19627 unit test. Otherwise we'd overrun that buffer and crash during
19628 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19630 - Make sure we create the keys directory if it doesn't exist and we're
19631 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19632 5572; bugfix on 0.2.3.13-alpha.
19633 - Fix a small memory leak when trying to decode incorrect base16
19634 authenticator during SAFECOOKIE authentication. Found by
19635 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19638 - Add more information to a log statement that might help track down
19639 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19640 non-IP address" messages (or any Bug messages, for that matter!),
19641 please let us know about it.
19642 - Relays now understand an IPv6 address when they get one from a
19643 directory server. Resolves ticket 4875.
19644 - Resolve IPv6 addresses in bridge and entry statistics to country
19645 code "??" which means we at least count them. Resolves ticket 5053;
19646 improves on 0.2.3.9-alpha.
19647 - Update to the April 3 2012 Maxmind GeoLite Country database.
19648 - Begin a doc/state-contents.txt file to explain the contents of
19649 the Tor state file. Fixes bug 2987.
19651 o Default torrc changes:
19652 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19653 port on 9050 by default anyway, so this should not change anything
19655 - Stop mentioning the deprecated *ListenAddress options in
19656 torrc.sample. Fixes bug 5438.
19657 - Document unit of bandwidth related options in sample torrc.
19660 o Removed features:
19661 - The "torify" script no longer supports the "tsocks" socksifier
19662 tool, since tsocks doesn't support DNS and UDP right for Tor.
19663 Everyone should be using torsocks instead. Fixes bugs 3530 and
19664 5180. Based on a patch by "ugh".
19666 o Code refactoring:
19667 - Change the symmetric cipher interface so that creating and
19668 initializing a stream cipher are no longer separate functions.
19669 - Remove all internal support for unpadded RSA. We never used it, and
19670 it would be a bad idea to start.
19673 Changes in version 0.2.3.13-alpha - 2012-03-26
19674 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19675 in managed pluggable transports, as well as providing other cleanups
19676 that get us closer to a release candidate.
19678 o Directory authority changes:
19679 - Change IP address for maatuska (v3 directory authority).
19682 - Provide controllers with a safer way to implement the cookie
19683 authentication mechanism. With the old method, if another locally
19684 running program could convince a controller that it was the Tor
19685 process, then that program could trick the controller into telling
19686 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19687 authentication method uses a challenge-response approach to prevent
19688 this attack. Fixes bug 5185, implements proposal 193.
19689 - Never use a bridge or a controller-supplied node as an exit, even
19690 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19691 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19692 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19693 - Only build circuits if we have a sufficient threshold of the total
19694 descriptors that are marked in the consensus with the "Exit"
19695 flag. This mitigates an attack proposed by wanoskarnet, in which
19696 all of a client's bridges collude to restrict the exit nodes that
19697 the client knows about. Fixes bug 5343.
19699 o Major bugfixes (on Tor 0.2.3.x):
19700 - Avoid an assert when managed proxies like obfsproxy are configured,
19701 and we receive HUP signals or setconf attempts too rapidly. This
19702 situation happens most commonly when Vidalia tries to attach to
19703 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19704 bugfix on 0.2.3.6-alpha.
19705 - Fix a relay-side pluggable transports bug where managed proxies were
19706 unreachable from the Internet, because Tor asked them to bind on
19707 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19708 - Stop discarding command-line arguments when TestingTorNetwork
19709 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19710 0.2.3.9-alpha, where task 4552 added support for two layers of
19712 - Resume allowing the unit tests to run in gdb. This was accidentally
19713 made impossible when the DisableDebuggerAttachment option was
19714 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19715 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19716 0.2.3.11-alpha. Reported by Anthony G. Basile.
19718 o Minor bugfixes (on 0.2.2.x and earlier):
19719 - Ensure we don't cannibalize circuits that are longer than three hops
19720 already, so we don't end up making circuits with 5 or more
19721 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19722 0.1.0.1-rc which introduced cannibalization.
19723 - Detect and reject certain misformed escape sequences in
19724 configuration values. Previously, these values would cause us
19725 to crash if received in a torrc file or over an authenticated
19726 control port. Bug found by Esteban Manchado Velázquez, and
19727 independently by Robert Connolly from Matta Consulting who further
19728 noted that it allows a post-authentication heap overflow. Patch
19729 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19730 bugfix on 0.2.0.16-alpha.
19731 - Fix a compile warning when using the --enable-openbsd-malloc
19732 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19733 - Directory caches no longer refuse to clean out descriptors because
19734 of missing v2 networkstatus documents, unless they're configured
19735 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19736 0.2.2.26-beta. Patch by Daniel Bryg.
19737 - Update to the latest version of the tinytest unit testing framework.
19738 This includes a couple of bugfixes that can be relevant for
19739 running forked unit tests on Windows, and removes all reserved
19742 o Minor bugfixes (on 0.2.3.x):
19743 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19744 4296; bugfix on 0.2.3.1-alpha.
19745 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19746 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19747 on 0.2.3.6-alpha. Patch by "frosty".
19748 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
19749 option, so that the IP stack doesn't decide to use it for IPv4
19750 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
19751 - Ensure that variables set in Tor's environment cannot override
19752 environment variables that Tor passes to a managed
19753 pluggable-transport proxy. Previously, Tor would pass every
19754 variable in its environment to managed proxies along with the new
19755 ones, in such a way that on many operating systems, the inherited
19756 environment variables would override those which Tor tried to
19757 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
19758 bugfix on 0.2.3.9-alpha for Windows.
19761 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19762 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19763 - Update to the March 6 2012 Maxmind GeoLite Country database.
19766 Changes in version 0.2.3.12-alpha - 2012-02-13
19767 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
19768 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
19769 when Tor is configured to use a pluggable transport like obfsproxy.
19772 - Fix builds when the path to sed, openssl, or sha1sum contains
19773 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19775 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19776 connections. This change should allow busy exit relays to stop
19777 running out of available sockets as quickly. Fixes bug 4950;
19778 bugfix on 0.2.2.26-beta.
19779 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
19780 would ask the bridge for microdescriptors, which are only supported
19781 in 0.2.3.x, and then fail to bootstrap when it didn't get the
19782 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
19783 - Properly set up obfsproxy's environment when in managed mode. The
19784 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
19785 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
19786 5076 and 5082; bugfix on 0.2.3.6-alpha.
19789 - Use the dead_strip option when building Tor on OS X. This reduces
19790 binary size by almost 19% when linking openssl and libevent
19791 statically, which we do for Tor Browser Bundle.
19792 - Fix broken URLs in the sample torrc file, and tell readers about
19793 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19794 PublishServerDescriptor options. Addresses bug 4652.
19795 - Update to the February 7 2012 Maxmind GeoLite Country database.
19798 - Downgrade the "We're missing a certificate" message from notice
19799 to info: people kept mistaking it for a real problem, whereas it
19800 is seldom the problem even when we are failing to bootstrap. Fixes
19801 bug 5067; bugfix on 0.2.0.10-alpha.
19802 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
19803 managed pluggable transport server proxy's environment.
19804 Previously, we would put it there, even though Tor doesn't
19805 implement an 'extended server port' yet, and even though Tor
19806 almost certainly isn't listening at that address. For now, we set
19807 it to an empty string to avoid crashing older obfsproxies. Bugfix
19809 - Log the heartbeat message every HeartbeatPeriod seconds, not every
19810 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
19811 0.2.3.1-alpha. Bug reported by Scott Bennett.
19812 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
19813 bugfix on 0.2.3.11-alpha.
19814 - Update "ClientOnly" man page entry to explain that there isn't
19815 really any point to messing with it. Resolves ticket 5005.
19816 - Use the correct CVE number for CVE-2011-4576 in our comments and
19817 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
19820 o Code simplifications and refactoring:
19821 - Use the _WIN32 macro throughout our code to detect Windows.
19822 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19826 Changes in version 0.2.3.11-alpha - 2012-01-22
19827 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
19828 the last step of the plan to limit maximum circuit length, includes
19829 a wide variety of hidden service performance and correctness fixes,
19830 works around an OpenSSL security flaw if your distro is too stubborn
19831 to upgrade, and fixes a bunch of smaller issues.
19834 - Now that Tor 0.2.0.x is completely deprecated, enable the final
19835 part of "Proposal 110: Avoiding infinite length circuits" by
19836 refusing all circuit-extend requests that do not use a relay_early
19837 cell. This change helps Tor resist a class of denial-of-service
19838 attacks by limiting the maximum circuit length.
19839 - Adjust the number of introduction points that a hidden service
19840 will try to maintain based on how long its introduction points
19841 remain in use and how many introductions they handle. Fixes
19843 - Try to use system facilities for enumerating local interface
19844 addresses, before falling back to our old approach (which was
19845 binding a UDP socket, and calling getsockname() on it). That
19846 approach was scaring OS X users whose draconian firewall
19847 software warned about binding to UDP sockets, regardless of
19848 whether packets were sent. Now we try to use getifaddrs(),
19849 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19850 system supports. Resolves ticket 1827.
19852 o Major security workaround:
19853 - When building or running with any version of OpenSSL earlier
19854 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19855 versions have a bug (CVE-2011-4576) in which their block cipher
19856 padding includes uninitialized data, potentially leaking sensitive
19857 information to any peer with whom they make a SSLv3 connection. Tor
19858 does not use SSL v3 by default, but a hostile client or server
19859 could force an SSLv3 connection in order to gain information that
19860 they shouldn't have been able to get. The best solution here is to
19861 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19862 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19863 to make sure that the bug can't happen.
19866 - Fix the SOCKET_OK test that we use to tell when socket
19867 creation fails so that it works on Win64. Fixes part of bug 4533;
19868 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19869 - Correct our replacements for the timeradd() and timersub() functions
19870 on platforms that lack them (for example, Windows). The timersub()
19871 function is used when expiring circuits, while timeradd() is
19872 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19873 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
19874 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
19875 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
19876 bug at runtime, not compile time, because some distributions hack
19877 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
19878 on 0.2.3.9-alpha. Found by Pascal.
19880 o Minor features (controller):
19881 - Use absolute path names when reporting the torrc filename in the
19882 control protocol, so a controller can more easily find the torrc
19883 file. Resolves bug 1101.
19884 - Extend the control protocol to report flags that control a circuit's
19885 path selection in CIRC events and in replies to 'GETINFO
19886 circuit-status'. Implements part of ticket 2411.
19887 - Extend the control protocol to report the hidden service address
19888 and current state of a hidden-service-related circuit in CIRC
19889 events and in replies to 'GETINFO circuit-status'. Implements part
19891 - When reporting the path to the cookie file to the controller,
19892 give an absolute path. Resolves ticket 4881.
19893 - Allow controllers to request an event notification whenever a
19894 circuit is cannibalized or its purpose is changed. Implements
19895 part of ticket 3457.
19896 - Include the creation time of a circuit in CIRC and CIRC2
19897 control-port events and the list produced by the 'GETINFO
19898 circuit-status' control-port command.
19900 o Minor features (directory authorities):
19901 - Directory authorities now reject versions of Tor older than
19902 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19903 inclusive. These versions accounted for only a small fraction of
19904 the Tor network, and have numerous known security issues. Resolves
19906 - Authority operators can now vote for all relays in a given
19907 set of countries to be BadDir/BadExit/Invalid/Rejected.
19908 - Provide two consensus parameters (FastFlagMinThreshold and
19909 FastFlagMaxThreshold) to control the range of allowable bandwidths
19910 for the Fast directory flag. These allow authorities to run
19911 experiments on appropriate requirements for being a "Fast" node.
19912 The AuthDirFastGuarantee config value still applies. Implements
19914 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19915 directory authority option (introduced in Tor 0.2.2.34).
19917 o Minor features (other):
19918 - Don't disable the DirPort when we cannot exceed our AccountingMax
19919 limit during this interval because the effective bandwidthrate is
19920 low enough. This is useful in a situation where AccountMax is only
19921 used as an additional safeguard or to provide statistics.
19922 - Prepend an informative header to generated dynamic_dh_params files.
19923 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19924 EntryNodes will have no effect. Resolves issue 2571.
19925 - Log more useful messages when we fail to disable debugger
19927 - Log which authority we're missing votes from when we go to fetch
19928 them from the other auths.
19929 - Log (at debug level) whenever a circuit's purpose is changed.
19930 - Add missing documentation for the MaxClientCircuitsPending,
19931 UseMicrodescriptors, UserspaceIOCPBuffers, and
19932 _UseFilteringSSLBufferevents options, all introduced during
19933 the 0.2.3.x series.
19934 - Update to the January 3 2012 Maxmind GeoLite Country database.
19936 o Minor bugfixes (hidden services):
19937 - Don't close hidden service client circuits which have almost
19938 finished connecting to their destination when they reach
19939 the normal circuit-build timeout. Previously, we would close
19940 introduction circuits which are waiting for an acknowledgement
19941 from the introduction point, and rendezvous circuits which have
19942 been specified in an INTRODUCE1 cell sent to a hidden service,
19943 after the normal CBT. Now, we mark them as 'timed out', and launch
19944 another rendezvous attempt in parallel. This behavior change can
19945 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19946 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19947 - Don't close hidden-service-side rendezvous circuits when they
19948 reach the normal circuit-build timeout. This behavior change can
19949 be disabled using the new
19950 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
19951 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
19952 - Make sure we never mark the wrong rendezvous circuit as having
19953 had its introduction cell acknowledged by the introduction-point
19954 relay. Previously, when we received an INTRODUCE_ACK cell on a
19955 client-side hidden-service introduction circuit, we might have
19956 marked a rendezvous circuit other than the one we specified in
19957 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
19958 a warning message and interfered with the hidden service
19959 connection-establishment process. Fixes bug 4759; bugfix on
19960 0.2.3.3-alpha, when we added the stream-isolation feature which
19961 might cause Tor to open multiple rendezvous circuits for the same
19963 - Don't trigger an assertion failure when we mark a new client-side
19964 hidden-service introduction circuit for close during the process
19965 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
19968 o Minor bugfixes (log messages):
19969 - Correctly spell "connect" in a log message on failure to create a
19970 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
19972 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19973 Fixes bug 4856; bugfix on Tor 0.0.6.
19974 - Fix the log message describing how we work around discovering
19975 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19976 4837; bugfix on 0.2.2.9-alpha.
19977 - When logging about a disallowed .exit name, do not also call it
19978 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19980 o Minor bugfixes (build fixes):
19981 - During configure, detect when we're building with clang version
19982 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19983 CFLAGS. clang doesn't support them yet.
19984 - During configure, search for library containing cos function as
19985 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19986 against libm was hard-coded before. Fixes the first part of bug
19987 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19989 - Detect attempts to build Tor on (as yet hypothetical) versions
19990 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19991 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19992 - Preprocessor directives should not be put inside the arguments
19993 of a macro. This would break compilation with GCC releases prior
19994 to version 3.3. We would never recommend such an old GCC version,
19995 but it is apparently required for binary compatibility on some
19996 platforms (namely, certain builds of Haiku). Fixes the other part
19997 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
20000 o Minor bugfixes (other):
20001 - Older Linux kernels erroneously respond to strange nmap behavior
20002 by having accept() return successfully with a zero-length
20003 socket. When this happens, just close the connection. Previously,
20004 we would try harder to learn the remote address: but there was
20005 no such remote address to learn, and our method for trying to
20006 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20007 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20008 - Fix null-pointer access that could occur if TLS allocation failed.
20009 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
20010 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
20011 accidentally been reverted.
20012 - Fix our implementation of crypto_random_hostname() so it can't
20013 overflow on ridiculously large inputs. (No Tor version has ever
20014 provided this kind of bad inputs, but let's be correct in depth.)
20015 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
20016 - Find more places in the code that should have been testing for
20017 invalid sockets using the SOCKET_OK macro. Required for a fix
20018 for bug 4533. Bugfix on 0.2.2.28-beta.
20019 - Fix an assertion failure when, while running with bufferevents, a
20020 connection finishes connecting after it is marked for close, but
20021 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
20022 - test_util_spawn_background_ok() hardcoded the expected value
20023 for ENOENT to 2. This isn't portable as error numbers are
20024 platform specific, and particularly the hurd has ENOENT at
20025 0x40000002. Construct expected string at runtime, using the correct
20026 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
20027 - Reject attempts to disable DisableDebuggerAttachment while Tor is
20028 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
20029 - Use an appropriate-width type for sockets in tor-fw-helper on
20030 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
20033 - When sending or relaying a RELAY_EARLY cell, we used to convert
20034 it to a RELAY cell if the connection was using the v1 link
20035 protocol. This was a workaround for older versions of Tor, which
20036 didn't handle RELAY_EARLY cells properly. Now that all supported
20037 versions can handle RELAY_EARLY cells, and now that we're enforcing
20038 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20039 remove this workaround. Addresses bug 4786.
20041 o Code simplifications and refactoring:
20042 - Use OpenSSL's built-in SSL_state_string_long() instead of our
20043 own homebrewed ssl_state_to_string() replacement. Patch from
20044 Emile Snyder. Fixes bug 4653.
20045 - Use macros to indicate OpenSSL versions, so we don't need to worry
20046 about accidental hexadecimal bit shifts.
20047 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
20049 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
20050 - Use the smartlist_add_asprintf() alias more consistently.
20051 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
20052 invalid value, rather than just -1.
20053 - Rename a handful of old identifiers, mostly related to crypto
20054 structures and crypto functions. By convention, our "create an
20055 object" functions are called "type_new()", our "free an object"
20056 functions are called "type_free()", and our types indicate that
20057 they are types only with a final "_t". But a handful of older
20058 types and functions broke these rules, with function names like
20059 "type_create" or "subsystem_op_type", or with type names like
20063 Changes in version 0.2.3.10-alpha - 2011-12-16
20064 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
20065 Tor's buffers code. Absolutely everybody should upgrade.
20067 The bug relied on an incorrect calculation when making data continuous
20068 in one of our IO buffers, if the first chunk of the buffer was
20069 misaligned by just the wrong amount. The miscalculation would allow an
20070 attacker to overflow a piece of heap-allocated memory. To mount this
20071 attack, the attacker would need to either open a SOCKS connection to
20072 Tor's SocksPort (usually restricted to localhost), or target a Tor
20073 instance configured to make its connections through a SOCKS proxy
20074 (which Tor does not do by default).
20076 Good security practice requires that all heap-overflow bugs should be
20077 presumed to be exploitable until proven otherwise, so we are treating
20078 this as a potential code execution attack. Please upgrade immediately!
20079 This bug does not affect bufferevents-based builds of Tor. Special
20080 thanks to "Vektor" for reporting this issue to us!
20082 This release also contains a few minor bugfixes for issues discovered
20086 - Fix a heap overflow bug that could occur when trying to pull
20087 data into the first chunk of a buffer, when that chunk had
20088 already had some data drained from it. Fixes CVE-2011-2778;
20089 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20092 - If we can't attach streams to a rendezvous circuit when we
20093 finish connecting to a hidden service, clear the rendezvous
20094 circuit's stream-isolation state and try to attach streams
20095 again. Previously, we cleared rendezvous circuits' isolation
20096 state either too early (if they were freshly built) or not at all
20097 (if they had been built earlier and were cannibalized). Bugfix on
20098 0.2.3.3-alpha; fixes bug 4655.
20099 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
20100 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
20101 - Fix an assertion failure when a relay with accounting enabled
20102 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
20105 - Update to the December 6 2011 Maxmind GeoLite Country database.
20108 Changes in version 0.2.2.35 - 2011-12-16
20109 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20110 buffers code. Absolutely everybody should upgrade.
20112 The bug relied on an incorrect calculation when making data continuous
20113 in one of our IO buffers, if the first chunk of the buffer was
20114 misaligned by just the wrong amount. The miscalculation would allow an
20115 attacker to overflow a piece of heap-allocated memory. To mount this
20116 attack, the attacker would need to either open a SOCKS connection to
20117 Tor's SocksPort (usually restricted to localhost), or target a Tor
20118 instance configured to make its connections through a SOCKS proxy
20119 (which Tor does not do by default).
20121 Good security practice requires that all heap-overflow bugs should be
20122 presumed to be exploitable until proven otherwise, so we are treating
20123 this as a potential code execution attack. Please upgrade immediately!
20124 This bug does not affect bufferevents-based builds of Tor. Special
20125 thanks to "Vektor" for reporting this issue to us!
20127 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20128 crash bugs for unusual configurations, and a long-term bug that
20129 would prevent Tor from starting on Windows machines with draconian
20132 With this release, we remind everyone that 0.2.0.x has reached its
20133 formal end-of-life. Those Tor versions have many known flaws, and
20134 nobody should be using them. You should upgrade -- ideally to the
20135 0.2.2.x series. If you're using a Linux or BSD and its packages are
20136 obsolete, stop using those packages and upgrade anyway.
20138 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20139 longer receive support after some time in early 2012.
20142 - Fix a heap overflow bug that could occur when trying to pull
20143 data into the first chunk of a buffer, when that chunk had
20144 already had some data drained from it. Fixes CVE-2011-2778;
20145 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20146 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20147 that it doesn't attempt to allocate a socketpair. This could cause
20148 some problems on Windows systems with overzealous firewalls. Fix for
20149 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20151 - If we mark an OR connection for close based on a cell we process,
20152 don't process any further cells on it. We already avoid further
20153 reads on marked-for-close connections, but now we also discard the
20154 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20155 which was the first version where we might mark a connection for
20156 close based on processing a cell on it.
20157 - Correctly sanity-check that we don't underflow on a memory
20158 allocation (and then assert) for hidden service introduction
20159 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20160 bugfix on 0.2.1.5-alpha.
20161 - Fix a memory leak when we check whether a hidden service
20162 descriptor has any usable introduction points left. Fixes bug
20163 4424. Bugfix on 0.2.2.25-alpha.
20164 - Don't crash when we're running as a relay and don't have a GeoIP
20165 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20166 we've had in the 0.2.3.x branch already.
20167 - When running as a client, do not print a misleading (and plain
20168 wrong) log message that we're collecting "directory request"
20169 statistics: clients don't collect statistics. Also don't create a
20170 useless (because empty) stats file in the stats/ directory. Fixes
20171 bug 4353; bugfix on 0.2.2.34.
20174 - Detect failure to initialize Libevent. This fix provides better
20175 detection for future instances of bug 4457.
20176 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20177 function. This was eating up hideously large amounts of time on some
20178 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20179 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20180 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20182 - Don't warn about unused log_mutex in log.c when building with
20183 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20184 0.1.0.6-rc which introduced --disable-threads.
20185 - When configuring, starting, or stopping an NT service, stop
20186 immediately after the service configuration attempt has succeeded
20187 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20188 - When sending a NETINFO cell, include the original address
20189 received for the other side, not its canonical address. Found
20190 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20191 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20192 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20193 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20194 occurred when a client tried to fetch a descriptor for a bridge
20195 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20196 - Backport fixes for a pair of compilation warnings on Windows.
20197 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20198 - If we had ever tried to call tor_addr_to_str on an address of
20199 unknown type, we would have done a strdup on an uninitialized
20200 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20201 Reported by "troll_un".
20202 - Correctly detect and handle transient lookup failures from
20203 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20204 Reported by "troll_un".
20205 - Fix null-pointer access that could occur if TLS allocation failed.
20206 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20207 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20208 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20211 - Add two new config options for directory authorities:
20212 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20213 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20214 that is always sufficient to satisfy the bandwidth requirement for
20215 the Guard flag. Now it will be easier for researchers to simulate
20216 Tor networks with different values. Resolves ticket 4484.
20217 - When Tor ignores a hidden service specified in its configuration,
20218 include the hidden service's directory in the warning message.
20219 Previously, we would only tell the user that some hidden service
20220 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20221 - Update to the December 6 2011 Maxmind GeoLite Country database.
20223 o Packaging changes:
20224 - Make it easier to automate expert package builds on Windows,
20225 by removing an absolute path from makensis.exe command.
20228 Changes in version 0.2.1.32 - 2011-12-16
20229 Tor 0.2.1.32 backports important security and privacy fixes for
20230 oldstable. This release is intended only for package maintainers and
20231 others who cannot use the 0.2.2 stable series. All others should be
20232 using Tor 0.2.2.x or newer.
20234 The Tor 0.2.1.x series will reach formal end-of-life some time in
20235 early 2012; we will stop releasing patches for it then.
20237 o Major bugfixes (also included in 0.2.2.x):
20238 - Correctly sanity-check that we don't underflow on a memory
20239 allocation (and then assert) for hidden service introduction
20240 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20241 bugfix on 0.2.1.5-alpha.
20242 - Fix a heap overflow bug that could occur when trying to pull
20243 data into the first chunk of a buffer, when that chunk had
20244 already had some data drained from it. Fixes CVE-2011-2778;
20245 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20248 - Update to the December 6 2011 Maxmind GeoLite Country database.
20251 Changes in version 0.2.3.9-alpha - 2011-12-08
20252 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
20253 a "DisableNetwork" security feature that bundles can use to avoid
20254 touching the network until bridges are configured, moves forward on
20255 the pluggable transport design, fixes a flaw in the hidden service
20256 design that unnecessarily prevented clients with wrong clocks from
20257 reaching hidden services, and fixes a wide variety of other issues.
20260 - Clients can now connect to private bridges over IPv6. Bridges
20261 still need at least one IPv4 address in order to connect to
20262 other relays. Note that we don't yet handle the case where the
20263 user has two bridge lines for the same bridge (one IPv4, one
20264 IPv6). Implements parts of proposal 186.
20265 - New "DisableNetwork" config option to prevent Tor from launching any
20266 connections or accepting any connections except on a control port.
20267 Bundles and controllers can set this option before letting Tor talk
20268 to the rest of the network, for example to prevent any connections
20269 to a non-bridge address. Packages like Orbot can also use this
20270 option to instruct Tor to save power when the network is off.
20271 - Clients and bridges can now be configured to use a separate
20272 "transport" proxy. This approach makes the censorship arms race
20273 easier by allowing bridges to use protocol obfuscation plugins. It
20274 implements the "managed proxy" part of proposal 180 (ticket 3472).
20275 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20276 implementation. It makes AES_CTR about 7% faster than our old one
20277 (which was about 10% faster than the one OpenSSL used to provide).
20278 Resolves ticket 4526.
20279 - Add a "tor2web mode" for clients that want to connect to hidden
20280 services non-anonymously (and possibly more quickly). As a safety
20281 measure to try to keep users from turning this on without knowing
20282 what they are doing, tor2web mode must be explicitly enabled at
20283 compile time, and a copy of Tor compiled to run in tor2web mode
20284 cannot be used as a normal Tor client. Implements feature 2553.
20285 - Add experimental support for running on Windows with IOCP and no
20286 kernel-space socket buffers. This feature is controlled by a new
20287 "UserspaceIOCPBuffers" config option (off by default), which has
20288 no effect unless Tor has been built with support for bufferevents,
20289 is running on Windows, and has enabled IOCP. This may, in the long
20290 run, help solve or mitigate bug 98.
20291 - Use a more secure consensus parameter voting algorithm. Now at
20292 least three directory authorities or a majority of them must
20293 vote on a given parameter before it will be included in the
20294 consensus. Implements proposal 178.
20297 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20298 They used to check that the timestamp was within 30 minutes
20299 of their system clock, so they could cap the size of their
20300 replay-detection cache, but that approach unnecessarily refused
20301 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20302 the v3 intro-point protocol (the first one which sent a timestamp
20303 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20304 - Only use the EVP interface when AES acceleration is enabled,
20305 to avoid a 5-7% performance regression. Resolves issue 4525;
20306 bugfix on 0.2.3.8-alpha.
20308 o Privacy/anonymity features (bridge detection):
20309 - Make bridge SSL certificates a bit more stealthy by using random
20310 serial numbers, in the same fashion as OpenSSL when generating
20311 self-signed certificates. Implements ticket 4584.
20312 - Introduce a new config option "DynamicDHGroups", enabled by
20313 default, which provides each bridge with a unique prime DH modulus
20314 to be used during SSL handshakes. This option attempts to help
20315 against censors who might use the Apache DH modulus as a static
20316 identifier for bridges. Addresses ticket 4548.
20318 o Minor features (new/different config options):
20319 - New configuration option "DisableDebuggerAttachment" (on by default)
20320 to prevent basic debugging attachment attempts by other processes.
20321 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20322 - Allow MapAddress directives to specify matches against super-domains,
20323 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20324 Implements issue 933.
20325 - Slightly change behavior of "list" options (that is, config
20326 options that can appear more than once) when they appear both in
20327 torrc and on the command line. Previously, the command-line options
20328 would be appended to the ones from torrc. Now, the command-line
20329 options override the torrc options entirely. This new behavior
20330 allows the user to override list options (like exit policies and
20331 ports to listen on) from the command line, rather than simply
20332 appending to the list.
20333 - You can get the old (appending) command-line behavior for "list"
20334 options by prefixing the option name with a "+".
20335 - You can remove all the values for a "list" option from the command
20336 line without adding any new ones by prefixing the option name
20338 - Add experimental support for a "defaults" torrc file to be parsed
20339 before the regular torrc. Torrc options override the defaults file's
20340 options in the same way that the command line overrides the torrc.
20341 The SAVECONF controller command saves only those options which
20342 differ between the current configuration and the defaults file. HUP
20343 reloads both files. (Note: This is an experimental feature; its
20344 behavior will probably be refined in future 0.2.3.x-alpha versions
20345 to better meet packagers' needs.) Implements task 4552.
20348 - Try to make the introductory warning message that Tor prints on
20349 startup more useful for actually finding help and information.
20350 Resolves ticket 2474.
20351 - Running "make version" now displays the version of Tor that
20352 we're about to build. Idea from katmagic; resolves issue 4400.
20353 - Expire old or over-used hidden service introduction points.
20354 Required by fix for bug 3460.
20355 - Move the replay-detection cache for the RSA-encrypted parts of
20356 INTRODUCE2 cells to the introduction point data structures.
20357 Previously, we would use one replay-detection cache per hidden
20358 service. Required by fix for bug 3460.
20359 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20360 public key replay-detection cache from 60 minutes to 5 minutes. This
20361 replay-detection cache is now used only to detect multiple
20362 INTRODUCE2 cells specifying the same rendezvous point, so we can
20363 avoid launching multiple simultaneous attempts to connect to it.
20365 o Minor bugfixes (on Tor 0.2.2.x and earlier):
20366 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20367 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20369 - Fix a minor formatting issue in one of tor-gencert's error messages.
20371 - Prevent a false positive from the check-spaces script, by disabling
20372 the "whitespace between function name and (" check for functions
20374 - Fix a log message suggesting that people contact a non-existent
20375 email address. Fixes bug 3448.
20376 - Fix null-pointer access that could occur if TLS allocation failed.
20377 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20378 - Report a real bootstrap problem to the controller on router
20379 identity mismatch. Previously we just said "foo", which probably
20380 made a lot of sense at the time. Fixes bug 4169; bugfix on
20382 - If we had ever tried to call tor_addr_to_str() on an address of
20383 unknown type, we would have done a strdup() on an uninitialized
20384 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20385 Reported by "troll_un".
20386 - Correctly detect and handle transient lookup failures from
20387 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20388 Reported by "troll_un".
20389 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20390 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20391 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20392 bug 4532; found by "troll_un".
20394 o Minor bugfixes (on Tor 0.2.3.x):
20395 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
20397 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
20398 circuit for use as a hidden service client's rendezvous point.
20399 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
20400 with help from wanoskarnet.
20401 - Restore behavior of overriding SocksPort, ORPort, and similar
20402 options from the command line. Bugfix on 0.2.3.3-alpha.
20405 - Properly handle the case where the build-tree is not the same
20406 as the source tree when generating src/common/common_sha1.i,
20407 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20408 bugfix on 0.2.0.1-alpha.
20410 o Code simplifications, cleanups, and refactorings:
20411 - Remove the pure attribute from all functions that used it
20412 previously. In many cases we assigned it incorrectly, because the
20413 functions might assert or call impure functions, and we don't have
20414 evidence that keeping the pure attribute is worthwhile. Implements
20415 changes suggested in ticket 4421.
20416 - Remove some dead code spotted by coverity. Fixes cid 432.
20417 Bugfix on 0.2.3.1-alpha, closes bug 4637.
20420 Changes in version 0.2.3.8-alpha - 2011-11-22
20421 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
20422 socketpair-related bug that has been bothering Windows users. It adds
20423 support to serve microdescriptors to controllers, so Vidalia's network
20424 map can resume listing relays (once Vidalia implements its side),
20425 and adds better support for hardware AES acceleration. Finally, it
20426 starts the process of adjusting the bandwidth cutoff for getting the
20427 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
20428 that tiny relays harm performance more than they help network capacity.
20431 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20432 that it doesn't attempt to allocate a socketpair. This could cause
20433 some problems on Windows systems with overzealous firewalls. Fix for
20434 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20436 - Correctly sanity-check that we don't underflow on a memory
20437 allocation (and then assert) for hidden service introduction
20438 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20439 bugfix on 0.2.1.5-alpha.
20440 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20441 flag. In the past few years the average relay speed has picked
20442 up, and while the "top 7/8 of the network get the Fast flag" and
20443 "all relays with 20KB or more of capacity get the Fast flag" rules
20444 used to have the same result, now the top 7/8 of the network has
20445 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20446 - Fix a rare assertion failure when checking whether a v0 hidden
20447 service descriptor has any usable introduction points left, and
20448 we don't have enough information to build a circuit to the first
20449 intro point named in the descriptor. The HS client code in
20450 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
20451 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
20452 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
20453 - Make bridge authorities not crash when they are asked for their own
20454 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
20455 - When running as a client, do not print a misleading (and plain
20456 wrong) log message that we're collecting "directory request"
20457 statistics: clients don't collect statistics. Also don't create a
20458 useless (because empty) stats file in the stats/ directory. Fixes
20459 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
20462 - Allow Tor controllers like Vidalia to obtain the microdescriptor
20463 for a relay by identity digest or nickname. Previously,
20464 microdescriptors were only available by their own digests, so a
20465 controller would have to ask for and parse the whole microdescriptor
20466 consensus in order to look up a single relay's microdesc. Fixes
20467 bug 3832; bugfix on 0.2.3.1-alpha.
20468 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20469 operations can use hardware acceleration (if present). Resolves
20472 o Minor bugfixes (on 0.2.2.x and earlier):
20473 - Detect failure to initialize Libevent. This fix provides better
20474 detection for future instances of bug 4457.
20475 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20476 function. This was eating up hideously large amounts of time on some
20477 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20478 - Don't warn about unused log_mutex in log.c when building with
20479 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20480 0.1.0.6-rc which introduced --disable-threads.
20481 - Allow manual 'authenticate' commands to the controller interface
20482 from netcat (nc) as well as telnet. We were rejecting them because
20483 they didn't come with the expected whitespace at the end of the
20484 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20485 - Fix some (not actually triggerable) buffer size checks in usage of
20486 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20488 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20489 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20490 - When configuring, starting, or stopping an NT service, stop
20491 immediately after the service configuration attempt has succeeded
20492 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20493 - When sending a NETINFO cell, include the original address
20494 received for the other side, not its canonical address. Found
20495 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20496 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20497 can pick them up when the tests aren't disabled. Bugfix on
20498 0.2.2.4-alpha which introduced tinytest.
20499 - Fix a memory leak when we check whether a hidden service
20500 descriptor has any usable introduction points left. Fixes bug
20501 4424. Bugfix on 0.2.2.25-alpha.
20502 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20503 occurred when a client tried to fetch a descriptor for a bridge
20504 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20506 o Minor bugfixes (on 0.2.3.x):
20507 - Make util unit tests build correctly with MSVC. Bugfix on
20508 0.2.3.3-alpha. Patch by Gisle Vanem.
20509 - Successfully detect AUTH_CHALLENGE cells with no recognized
20510 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
20511 Found by frosty_un.
20512 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
20513 it should still send a NETINFO cell to allow the connection to
20514 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
20516 - Log less loudly when we get an invalid authentication certificate
20517 from a source other than a directory authority: it's not unusual
20518 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
20520 - Tolerate servers with more clock skew in their authentication
20521 certificates than previously. Fixes bug 4371; bugfix on
20523 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
20524 on 0.2.3.4-alpha and 0.2.3.6-alpha.
20527 - Add two new config options for directory authorities:
20528 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20529 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20530 that is always sufficient to satisfy the bandwidth requirement for
20531 the Guard flag. Now it will be easier for researchers to simulate
20532 Tor networks with different values. Resolves ticket 4484.
20533 - When Tor ignores a hidden service specified in its configuration,
20534 include the hidden service's directory in the warning message.
20535 Previously, we would only tell the user that some hidden service
20536 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20537 - When we fail to initialize Libevent, retry with IOCP disabled so we
20538 don't need to turn on multi-threading support in Libevent, which in
20539 turn requires a working socketpair(). This is a workaround for bug
20540 4457, which affects Libevent versions from 2.0.1-alpha through
20542 - Detect when we try to build on a platform that doesn't define
20543 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20544 - Update to the November 1 2011 Maxmind GeoLite Country database.
20546 o Packaging changes:
20547 - Make it easier to automate expert package builds on Windows,
20548 by removing an absolute path from makensis.exe command.
20550 o Code simplifications and refactoring:
20551 - Remove some redundant #include directives throughout the code.
20552 Patch from Andrea Gelmini.
20553 - Unconditionally use OpenSSL's AES implementation instead of our
20554 old built-in one. OpenSSL's AES has been better for a while, and
20555 relatively few servers should still be on any version of OpenSSL
20556 that doesn't have good optimized assembly AES.
20557 - Use the name "CERTS" consistently to refer to the new cell type;
20558 we were calling it CERT in some places and CERTS in others.
20561 - Numerous new unit tests for functions in util.c and address.c by
20563 - The long-disabled benchmark tests are now split into their own
20564 ./src/test/bench binary.
20565 - The benchmark tests can now use more accurate timers than
20566 gettimeofday() when such timers are available.
20569 Changes in version 0.2.3.7-alpha - 2011-10-30
20570 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20571 the new v3 handshake. It also resolves yet another bridge address
20575 - If we mark an OR connection for close based on a cell we process,
20576 don't process any further cells on it. We already avoid further
20577 reads on marked-for-close connections, but now we also discard the
20578 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20579 which was the first version where we might mark a connection for
20580 close based on processing a cell on it.
20581 - Fix a double-free bug that would occur when we received an invalid
20582 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20583 bugfix on 0.2.3.6-alpha.
20584 - Bridges no longer include their address in NETINFO cells on outgoing
20585 OR connections, to allow them to blend in better with clients.
20586 Removes another avenue for enumerating bridges. Reported by
20587 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20588 cells were introduced.
20591 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20592 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20595 Changes in version 0.2.3.6-alpha - 2011-10-26
20596 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20597 anonymity vulnerability where an attacker can deanonymize Tor
20598 users. Everybody should upgrade.
20600 This release also features support for a new v3 connection handshake
20601 protocol, and fixes to make hidden service connections more robust.
20604 - Implement a new handshake protocol (v3) for authenticating Tors to
20605 each other over TLS. It should be more resistant to fingerprinting
20606 than previous protocols, and should require less TLS hacking for
20607 future Tor implementations. Implements proposal 176.
20608 - Allow variable-length padding cells to disguise the length of
20609 Tor's TLS records. Implements part of proposal 184.
20611 o Privacy/anonymity fixes (clients):
20612 - Clients and bridges no longer send TLS certificate chains on
20613 outgoing OR connections. Previously, each client or bridge would
20614 use the same cert chain for all outgoing OR connections until
20615 its IP address changes, which allowed any relay that the client
20616 or bridge contacted to determine which entry guards it is using.
20617 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20618 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20619 no longer considers that connection as suitable for satisfying a
20620 circuit EXTEND request. Now relays can protect clients from the
20621 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20622 - Directory authorities no longer assign the Guard flag to relays
20623 that haven't upgraded to the above "refuse EXTEND requests
20624 to client connections" fix. Now directory authorities can
20625 protect clients from the CVE-2011-2768 issue even if neither
20626 the clients nor the relays have upgraded yet. There's a new
20627 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20628 to let us transition smoothly, else tomorrow there would be no
20631 o Major bugfixes (hidden services):
20632 - Improve hidden service robustness: when an attempt to connect to
20633 a hidden service ends, be willing to refetch its hidden service
20634 descriptors from each of the HSDir relays responsible for them
20635 immediately. Previously, we would not consider refetching the
20636 service's descriptors from each HSDir for 15 minutes after the last
20637 fetch, which was inconvenient if the hidden service was not running
20638 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20639 - When one of a hidden service's introduction points appears to be
20640 unreachable, stop trying it. Previously, we would keep trying
20641 to build circuits to the introduction point until we lost the
20642 descriptor, usually because the user gave up and restarted Tor.
20643 Partly fixes bug 3825.
20644 - Don't launch a useless circuit after failing to use one of a
20645 hidden service's introduction points. Previously, we would
20646 launch a new introduction circuit, but not set the hidden service
20647 which that circuit was intended to connect to, so it would never
20648 actually be used. A different piece of code would then create a
20649 new introduction circuit correctly. Bug reported by katmagic and
20650 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20652 o Major bugfixes (other):
20653 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20654 that they initiated. Relays could distinguish incoming bridge
20655 connections from client connections, creating another avenue for
20656 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20657 Found by "frosty_un".
20658 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20659 tor gets started. This prevents a wrong average bandwidth
20660 estimate, which would cause relays to always start a new accounting
20661 interval at the earliest possible moment. Fixes bug 2003; bugfix
20662 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20663 immensely in tracking this bug down.
20664 - Fix a crash bug when changing node restrictions while a DNS lookup
20665 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20668 o Minor bugfixes (on 0.2.2.x and earlier):
20669 - When a hidden service turns an extra service-side introduction
20670 circuit into a general-purpose circuit, free the rend_data and
20671 intro_key fields first, so we won't leak memory if the circuit
20672 is cannibalized for use as another service-side introduction
20673 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20674 - Rephrase the log message emitted if the TestSocks check is
20675 successful. Patch from Fabian Keil; fixes bug 4094.
20676 - Bridges now skip DNS self-tests, to act a little more stealthily.
20677 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20678 bridges. Patch by "warms0x".
20679 - Remove a confusing dollar sign from the example fingerprint in the
20680 man page, and also make the example fingerprint a valid one. Fixes
20681 bug 4309; bugfix on 0.2.1.3-alpha.
20682 - Fix internal bug-checking logic that was supposed to catch
20683 failures in digest generation so that it will fail more robustly
20684 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20685 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20686 - Report any failure in init_keys() calls launched because our
20687 IP address has changed. Spotted by Coverity Scan. Bugfix on
20688 0.1.1.4-alpha; fixes CID 484.
20690 o Minor bugfixes (on 0.2.3.x):
20691 - Fix a bug in configure.in that kept it from building a configure
20692 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20693 bugfix on 0.2.3.1-alpha.
20694 - Don't warn users that they are exposing a client port to the
20695 Internet if they have specified an RFC1918 address. Previously,
20696 we would warn if the user had specified any non-loopback
20697 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20698 - Fix memory leaks in the failing cases of the new SocksPort and
20699 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20700 fixes coverity CIDs 485, 486, and 487.
20703 - When a hidden service's introduction point times out, consider
20704 trying it again during the next attempt to connect to the
20705 HS. Previously, we would not try it again unless a newly fetched
20706 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20707 - The next version of Windows will be called Windows 8, and it has
20708 a major version of 6, minor version of 2. Correctly identify that
20709 version instead of calling it "Very recent version". Resolves
20710 ticket 4153; reported by funkstar.
20711 - The Bridge Authority now writes statistics on how many bridge
20712 descriptors it gave out in total, and how many unique descriptors
20713 it gave out. It also lists how often the most and least commonly
20714 fetched descriptors were given out, as well as the median and
20715 25th/75th percentile. Implements tickets 4200 and 4294.
20716 - Update to the October 4 2011 Maxmind GeoLite Country database.
20718 o Code simplifications and refactoring:
20719 - Remove some old code to remember statistics about which descriptors
20720 we've served as a directory mirror. The feature wasn't used and
20721 is outdated now that microdescriptors are around.
20722 - Rename Tor functions that turn strings into addresses, so that
20723 "parse" indicates that no hostname resolution occurs, and
20724 "lookup" indicates that hostname resolution may occur. This
20725 should help prevent mistakes in the future. Fixes bug 3512.
20728 Changes in version 0.2.2.34 - 2011-10-26
20729 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20730 can deanonymize Tor users. Everybody should upgrade.
20732 The attack relies on four components: 1) Clients reuse their TLS cert
20733 when talking to different relays, so relays can recognize a user by
20734 the identity key in her cert. 2) An attacker who knows the client's
20735 identity key can probe each guard relay to see if that identity key
20736 is connected to that guard relay right now. 3) A variety of active
20737 attacks in the literature (starting from "Low-Cost Traffic Analysis
20738 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20739 discover the guard relays that a Tor user visiting the website is using.
20740 4) Clients typically pick three guards at random, so the set of guards
20741 for a given user could well be a unique fingerprint for her. This
20742 release fixes components #1 and #2, which is enough to block the attack;
20743 the other two remain as open research problems. Special thanks to
20744 "frosty_un" for reporting the issue to us!
20746 Clients should upgrade so they are no longer recognizable by the TLS
20747 certs they present. Relays should upgrade so they no longer allow a
20748 remote attacker to probe them to test whether unpatched clients are
20749 currently connected to them.
20751 This release also fixes several vulnerabilities that allow an attacker
20752 to enumerate bridge relays. Some bridge enumeration attacks still
20753 remain; see for example proposal 188.
20755 o Privacy/anonymity fixes (clients):
20756 - Clients and bridges no longer send TLS certificate chains on
20757 outgoing OR connections. Previously, each client or bridge would
20758 use the same cert chain for all outgoing OR connections until
20759 its IP address changes, which allowed any relay that the client
20760 or bridge contacted to determine which entry guards it is using.
20761 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20762 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20763 no longer considers that connection as suitable for satisfying a
20764 circuit EXTEND request. Now relays can protect clients from the
20765 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20766 - Directory authorities no longer assign the Guard flag to relays
20767 that haven't upgraded to the above "refuse EXTEND requests
20768 to client connections" fix. Now directory authorities can
20769 protect clients from the CVE-2011-2768 issue even if neither
20770 the clients nor the relays have upgraded yet. There's a new
20771 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20772 to let us transition smoothly, else tomorrow there would be no
20775 o Privacy/anonymity fixes (bridge enumeration):
20776 - Bridge relays now do their directory fetches inside Tor TLS
20777 connections, like all the other clients do, rather than connecting
20778 directly to the DirPort like public relays do. Removes another
20779 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20780 - Bridges relays now build circuits for themselves in a more similar
20781 way to how clients build them. Removes another avenue for
20782 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20783 when bridges were introduced.
20784 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20785 that they initiated. Relays could distinguish incoming bridge
20786 connections from client connections, creating another avenue for
20787 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20788 Found by "frosty_un".
20791 - Fix a crash bug when changing node restrictions while a DNS lookup
20792 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20794 - Don't launch a useless circuit after failing to use one of a
20795 hidden service's introduction points. Previously, we would
20796 launch a new introduction circuit, but not set the hidden service
20797 which that circuit was intended to connect to, so it would never
20798 actually be used. A different piece of code would then create a
20799 new introduction circuit correctly. Bug reported by katmagic and
20800 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20803 - Change an integer overflow check in the OpenBSD_Malloc code so
20804 that GCC is less likely to eliminate it as impossible. Patch
20805 from Mansour Moufid. Fixes bug 4059.
20806 - When a hidden service turns an extra service-side introduction
20807 circuit into a general-purpose circuit, free the rend_data and
20808 intro_key fields first, so we won't leak memory if the circuit
20809 is cannibalized for use as another service-side introduction
20810 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20811 - Bridges now skip DNS self-tests, to act a little more stealthily.
20812 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20813 bridges. Patch by "warms0x".
20814 - Fix internal bug-checking logic that was supposed to catch
20815 failures in digest generation so that it will fail more robustly
20816 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20817 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20818 - Report any failure in init_keys() calls launched because our
20819 IP address has changed. Spotted by Coverity Scan. Bugfix on
20820 0.1.1.4-alpha; fixes CID 484.
20822 o Minor bugfixes (log messages and documentation):
20823 - Remove a confusing dollar sign from the example fingerprint in the
20824 man page, and also make the example fingerprint a valid one. Fixes
20825 bug 4309; bugfix on 0.2.1.3-alpha.
20826 - The next version of Windows will be called Windows 8, and it has
20827 a major version of 6, minor version of 2. Correctly identify that
20828 version instead of calling it "Very recent version". Resolves
20829 ticket 4153; reported by funkstar.
20830 - Downgrade log messages about circuit timeout calibration from
20831 "notice" to "info": they don't require or suggest any human
20832 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20833 bugfix on 0.2.2.14-alpha.
20836 - Turn on directory request statistics by default and include them in
20837 extra-info descriptors. Don't break if we have no GeoIP database.
20838 Backported from 0.2.3.1-alpha; implements ticket 3951.
20839 - Update to the October 4 2011 Maxmind GeoLite Country database.
20842 Changes in version 0.2.1.31 - 2011-10-26
20843 Tor 0.2.1.31 backports important security and privacy fixes for
20844 oldstable. This release is intended only for package maintainers and
20845 others who cannot use the 0.2.2 stable series. All others should be
20846 using Tor 0.2.2.x or newer.
20848 o Security fixes (also included in 0.2.2.x):
20849 - Replace all potentially sensitive memory comparison operations
20850 with versions whose runtime does not depend on the data being
20851 compared. This will help resist a class of attacks where an
20852 adversary can use variations in timing information to learn
20853 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20854 implementation by Robert Ransom based partially on code by DJB.)
20855 - Fix an assert in parsing router descriptors containing IPv6
20856 addresses. This one took down the directory authorities when
20857 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20859 o Privacy/anonymity fixes (also included in 0.2.2.x):
20860 - Clients and bridges no longer send TLS certificate chains on
20861 outgoing OR connections. Previously, each client or bridge would
20862 use the same cert chain for all outgoing OR connections until
20863 its IP address changes, which allowed any relay that the client
20864 or bridge contacted to determine which entry guards it is using.
20865 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20866 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20867 no longer considers that connection as suitable for satisfying a
20868 circuit EXTEND request. Now relays can protect clients from the
20869 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20870 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20871 that they initiated. Relays could distinguish incoming bridge
20872 connections from client connections, creating another avenue for
20873 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20874 Found by "frosty_un".
20875 - When receiving a hidden service descriptor, check that it is for
20876 the hidden service we wanted. Previously, Tor would store any
20877 hidden service descriptors that a directory gave it, whether it
20878 wanted them or not. This wouldn't have let an attacker impersonate
20879 a hidden service, but it did let directories pre-seed a client
20880 with descriptors that it didn't want. Bugfix on 0.0.6.
20881 - Avoid linkability based on cached hidden service descriptors: forget
20882 all hidden service descriptors cached as a client when processing a
20883 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20884 - Make the bridge directory authority refuse to answer directory
20885 requests for "all" descriptors. It used to include bridge
20886 descriptors in its answer, which was a major information leak.
20887 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20888 - Don't attach new streams to old rendezvous circuits after SIGNAL
20889 NEWNYM. Previously, we would keep using an existing rendezvous
20890 circuit if it remained open (i.e. if it were kept open by a
20891 long-lived stream, or if a new stream were attached to it before
20892 Tor could notice that it was old and no longer in use). Bugfix on
20893 0.1.1.15-rc; fixes bug 3375.
20895 o Minor bugfixes (also included in 0.2.2.x):
20896 - When we restart our relay, we might get a successful connection
20897 from the outside before we've started our reachability tests,
20898 triggering a warning: "ORPort found reachable, but I have no
20899 routerinfo yet. Failing to inform controller of success." This
20900 bug was harmless unless Tor is running under a controller
20901 like Vidalia, in which case the controller would never get a
20902 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20904 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20905 enabled. Fixes bug 1526.
20906 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20907 anything since 0.2.1.16-rc.
20908 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20909 None of the cases where we did this before were wrong, but by making
20910 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20911 - Fix a rare crash bug that could occur when a client was configured
20912 with a large number of bridges. Fixes bug 2629; bugfix on
20913 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20914 - Correct the warning displayed when a rendezvous descriptor exceeds
20915 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20917 - Fix an uncommon assertion failure when running with DNSPort under
20918 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20919 - When warning about missing zlib development packages during compile,
20920 give the correct package names. Bugfix on 0.2.0.1-alpha.
20921 - Require that introduction point keys and onion keys have public
20922 exponent 65537. Bugfix on 0.2.0.10-alpha.
20923 - Do not crash when our configuration file becomes unreadable, for
20924 example due to a permissions change, between when we start up
20925 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20927 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20929 - Always NUL-terminate the sun_path field of a sockaddr_un before
20930 passing it to the kernel. (Not a security issue: kernels are
20931 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20932 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20933 - Don't stack-allocate the list of supplementary GIDs when we're
20934 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20935 could take up to 256K, which is way too much stack. Found by
20936 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20938 o Minor bugfixes (only in 0.2.1.x):
20939 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20940 rely on them. Bugfix on 0.2.1.30.
20941 - Use git revisions instead of svn revisions when generating our
20942 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20944 o Minor features (also included in 0.2.2.x):
20945 - Adjust the expiration time on our SSL session certificates to
20946 better match SSL certs seen in the wild. Resolves ticket 4014.
20947 - Allow nameservers with IPv6 address. Resolves bug 2574.
20948 - Update to the October 4 2011 Maxmind GeoLite Country database.
20951 Changes in version 0.2.3.5-alpha - 2011-09-28
20952 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
20953 bridge relays; fixes an assertion error that many users started hitting
20954 today; and adds the ability to refill token buckets more often than
20955 once per second, allowing significant performance improvements.
20958 - Bridge relays now do their directory fetches inside Tor TLS
20959 connections, like all the other clients do, rather than connecting
20960 directly to the DirPort like public relays do. Removes another
20961 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20962 - Bridges relays now build circuits for themselves in a more similar
20963 way to how clients build them. Removes another avenue for
20964 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20965 when bridges were introduced.
20968 - Fix an "Assertion md->held_by_node == 1 failed" error that could
20969 occur when the same microdescriptor was referenced by two node_t
20970 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
20972 o Major features (networking):
20973 - Add a new TokenBucketRefillInterval option to refill token buckets
20974 more frequently than once per second. This should improve network
20975 performance, alleviate queueing problems, and make traffic less
20976 bursty. Implements proposal 183; closes ticket 3630. Design by
20977 Florian Tschorsch and Björn Scheuermann; implementation by
20981 - Change an integer overflow check in the OpenBSD_Malloc code so
20982 that GCC is less likely to eliminate it as impossible. Patch
20983 from Mansour Moufid. Fixes bug 4059.
20985 o Minor bugfixes (usability):
20986 - Downgrade log messages about circuit timeout calibration from
20987 "notice" to "info": they don't require or suggest any human
20988 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20989 bugfix on 0.2.2.14-alpha.
20991 o Minor features (diagnostics):
20992 - When the system call to create a listener socket fails, log the
20993 error message explaining why. This may help diagnose bug 4027.
20996 Changes in version 0.2.3.4-alpha - 2011-09-13
20997 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
20998 tweak to Tor's TLS handshake that makes relays and bridges that run
20999 this new version reachable from Iran again. It also fixes a few new
21000 bugs in 0.2.3.x, and teaches relays to recognize when they're not
21001 listed in the network consensus and republish.
21003 o Major bugfixes (also part of 0.2.2.33):
21004 - Avoid an assertion failure when reloading a configuration with
21005 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21006 3923; bugfix on 0.2.2.25-alpha.
21008 o Minor features (security, also part of 0.2.2.33):
21009 - Check for replays of the public-key encrypted portion of an
21010 INTRODUCE1 cell, in addition to the current check for replays of
21011 the g^x value. This prevents a possible class of active attacks
21012 by an attacker who controls both an introduction point and a
21013 rendezvous point, and who uses the malleability of AES-CTR to
21014 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21015 that these attacks are infeasible (requiring the attacker to send
21016 on the order of zettabytes of altered cells in a short interval),
21017 but we'd rather block them off in case there are any classes of
21018 this attack that we missed. Reported by Willem Pinckaers.
21020 o Minor features (also part of 0.2.2.33):
21021 - Adjust the expiration time on our SSL session certificates to
21022 better match SSL certs seen in the wild. Resolves ticket 4014.
21023 - Change the default required uptime for a relay to be accepted as
21024 a HSDir (hidden service directory) from 24 hours to 25 hours.
21025 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21026 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21027 authorities to abstain from voting on assignment of the HSDir
21028 consensus flag. Related to bug 2649.
21029 - Update to the September 6 2011 Maxmind GeoLite Country database.
21031 o Minor bugfixes (also part of 0.2.2.33):
21032 - Demote the 'replay detected' log message emitted when a hidden
21033 service receives the same Diffie-Hellman public key in two different
21034 INTRODUCE2 cells to info level. A normal Tor client can cause that
21035 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21036 fixes part of bug 2442.
21037 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21038 level. There is nothing that a hidden service's operator can do
21039 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21041 - Clarify a log message specifying the characters permitted in
21042 HiddenServiceAuthorizeClient client names. Previously, the log
21043 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21044 given the impression that every ASCII character between "+" and "_"
21045 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21047 o Build fixes (also part of 0.2.2.33):
21048 - Clean up some code issues that prevented Tor from building on older
21049 BSDs. Fixes bug 3894; reported by "grarpamp".
21050 - Search for a platform-specific version of "ar" when cross-compiling.
21051 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21054 - Fix a bug where the SocksPort option (for example) would get
21055 ignored and replaced by the default if a SocksListenAddress
21056 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
21060 - Relays now try regenerating and uploading their descriptor more
21061 frequently if they are not listed in the consensus, or if the
21062 version of their descriptor listed in the consensus is too
21063 old. This fix should prevent situations where a server declines
21064 to re-publish itself because it has done so too recently, even
21065 though the authorities decided not to list its recent-enough
21066 descriptor. Fix for bug 3327.
21069 - Relays now include a reason for regenerating their descriptors
21070 in an HTTP header when uploading to the authorities. This will
21071 make it easier to debug descriptor-upload issues in the future.
21072 - When starting as root and then changing our UID via the User
21073 control option, and we have a ControlSocket configured, make sure
21074 that the ControlSocket is owned by the same account that Tor will
21075 run under. Implements ticket 3421; fix by Jérémy Bobbio.
21078 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
21079 utility function used in the control-port code). This shouldn't
21080 ever happen unless Tor is completely out of memory, but if it did
21081 happen and Tor somehow recovered from it, Tor could have sent a log
21082 message to a control port in the middle of a reply to a controller
21083 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
21084 - Make 'FetchUselessDescriptors' cause all descriptor types and
21085 all consensus types (including microdescriptors) to get fetched.
21086 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
21088 o Code refactoring:
21089 - Make a new "entry connection" struct as an internal subtype of "edge
21090 connection", to simplify the code and make exit connections smaller.
21093 Changes in version 0.2.2.33 - 2011-09-13
21094 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21095 TLS handshake that makes relays and bridges that run this new version
21096 reachable from Iran again.
21099 - Avoid an assertion failure when reloading a configuration with
21100 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21101 3923; bugfix on 0.2.2.25-alpha.
21103 o Minor features (security):
21104 - Check for replays of the public-key encrypted portion of an
21105 INTRODUCE1 cell, in addition to the current check for replays of
21106 the g^x value. This prevents a possible class of active attacks
21107 by an attacker who controls both an introduction point and a
21108 rendezvous point, and who uses the malleability of AES-CTR to
21109 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21110 that these attacks are infeasible (requiring the attacker to send
21111 on the order of zettabytes of altered cells in a short interval),
21112 but we'd rather block them off in case there are any classes of
21113 this attack that we missed. Reported by Willem Pinckaers.
21116 - Adjust the expiration time on our SSL session certificates to
21117 better match SSL certs seen in the wild. Resolves ticket 4014.
21118 - Change the default required uptime for a relay to be accepted as
21119 a HSDir (hidden service directory) from 24 hours to 25 hours.
21120 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21121 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21122 authorities to abstain from voting on assignment of the HSDir
21123 consensus flag. Related to bug 2649.
21124 - Update to the September 6 2011 Maxmind GeoLite Country database.
21126 o Minor bugfixes (documentation and log messages):
21127 - Correct the man page to explain that HashedControlPassword and
21128 CookieAuthentication can both be set, in which case either method
21129 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21130 when we decided to allow these config options to both be set. Issue
21131 raised by bug 3898.
21132 - Demote the 'replay detected' log message emitted when a hidden
21133 service receives the same Diffie-Hellman public key in two different
21134 INTRODUCE2 cells to info level. A normal Tor client can cause that
21135 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21136 fixes part of bug 2442.
21137 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21138 level. There is nothing that a hidden service's operator can do
21139 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21141 - Clarify a log message specifying the characters permitted in
21142 HiddenServiceAuthorizeClient client names. Previously, the log
21143 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21144 given the impression that every ASCII character between "+" and "_"
21145 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21148 - Provide a substitute implementation of lround() for MSVC, which
21149 apparently lacks it. Patch from Gisle Vanem.
21150 - Clean up some code issues that prevented Tor from building on older
21151 BSDs. Fixes bug 3894; reported by "grarpamp".
21152 - Search for a platform-specific version of "ar" when cross-compiling.
21153 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21156 Changes in version 0.2.3.3-alpha - 2011-09-01
21157 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
21158 security, and provides client-side support for the microdescriptor
21159 and optimistic data features introduced earlier in the 0.2.3.x
21160 series. It also includes numerous critical bugfixes in the (optional)
21161 bufferevent-based networking backend.
21163 o Major features (stream isolation):
21164 - You can now configure Tor so that streams from different
21165 applications are isolated on different circuits, to prevent an
21166 attacker who sees your streams as they leave an exit node from
21167 linking your sessions to one another. To do this, choose some way
21168 to distinguish the applications: have them connect to different
21169 SocksPorts, or have one of them use SOCKS4 while the other uses
21170 SOCKS5, or have them pass different authentication strings to the
21171 SOCKS proxy. Then, use the new SocksPort syntax to configure the
21172 degree of isolation you need. This implements Proposal 171.
21173 - There's a new syntax for specifying multiple client ports (such as
21174 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
21175 multiple *Port entries with full addr:port syntax on each.
21176 The old *ListenAddress format is still supported, but you can't
21177 mix it with the new *Port syntax.
21179 o Major features (other):
21180 - Enable microdescriptor fetching by default for clients. This allows
21181 clients to download a much smaller amount of directory information.
21182 To disable it (and go back to the old-style consensus and
21183 descriptors), set "UseMicrodescriptors 0" in your torrc file.
21184 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
21185 "PortForwarding" config option), now supports Windows.
21186 - When using an exit relay running 0.2.3.x, clients can now
21187 "optimistically" send data before the exit relay reports that
21188 the stream has opened. This saves a round trip when starting
21189 connections where the client speaks first (such as web browsing).
21190 This behavior is controlled by a consensus parameter (currently
21191 disabled). To turn it on or off manually, use the "OptimisticData"
21192 torrc option. Implements proposal 181; code by Ian Goldberg.
21194 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
21195 - When using IOCP on Windows, we need to enable Libevent windows
21197 - The IOCP backend now works even when the user has not specified
21198 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
21199 Fixes part of bug 3752.
21200 - Correctly record the bytes we've read and written when using
21201 bufferevents, so that we can include them in our bandwidth history
21202 and advertised bandwidth. Fixes bug 3803.
21203 - Apply rate-limiting only at the bottom of a chain of filtering
21204 bufferevents. This prevents us from filling up internal read
21205 buffers and violating rate-limits when filtering bufferevents
21206 are enabled. Fixes part of bug 3804.
21207 - Add high-watermarks to the output buffers for filtered
21208 bufferevents. This prevents us from filling up internal write
21209 buffers and wasting CPU cycles when filtering bufferevents are
21210 enabled. Fixes part of bug 3804.
21211 - Correctly notice when data has been written from a bufferevent
21212 without flushing it completely. Fixes bug 3805.
21213 - Fix a bug where server-side tunneled bufferevent-based directory
21214 streams would get closed prematurely. Fixes bug 3814.
21215 - Fix a use-after-free error with per-connection rate-limiting
21216 buckets. Fixes bug 3888.
21218 o Major bugfixes (also part of 0.2.2.31-rc):
21219 - If we're configured to write our ControlPorts to disk, only write
21220 them after switching UID and creating the data directory. This way,
21221 we don't fail when starting up with a nonexistent DataDirectory
21222 and a ControlPortWriteToFile setting based on that directory. Fixes
21223 bug 3747; bugfix on Tor 0.2.2.26-beta.
21226 - Added a new CONF_CHANGED event so that controllers can be notified
21227 of any configuration changes made by other controllers, or by the
21228 user. Implements ticket 1692.
21229 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
21230 leak when using bufferevents, and lets Libevent worry about how to
21231 best copy data out of a buffer.
21232 - Replace files in stats/ rather than appending to them. Now that we
21233 include statistics in extra-info descriptors, it makes no sense to
21234 keep old statistics forever. Implements ticket 2930.
21236 o Minor features (build compatibility):
21237 - Limited, experimental support for building with nmake and MSVC.
21238 - Provide a substitute implementation of lround() for MSVC, which
21239 apparently lacks it. Patch from Gisle Vanem.
21241 o Minor features (also part of 0.2.2.31-rc):
21242 - Update to the August 2 2011 Maxmind GeoLite Country database.
21244 o Minor bugfixes (on 0.2.3.x-alpha):
21245 - Fix a spurious warning when parsing SOCKS requests with
21246 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
21247 - Get rid of a harmless warning that could happen on relays running
21248 with bufferevents. The warning was caused by someone doing an http
21249 request to a relay's orport. Also don't warn for a few related
21250 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
21252 o Minor bugfixes (on 2.2.x and earlier):
21253 - Correct the man page to explain that HashedControlPassword and
21254 CookieAuthentication can both be set, in which case either method
21255 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21256 when we decided to allow these config options to both be set. Issue
21257 raised by bug 3898.
21258 - The "--quiet" and "--hush" options now apply not only to Tor's
21259 behavior before logs are configured, but also to Tor's behavior in
21260 the absence of configured logs. Fixes bug 3550; bugfix on
21263 o Minor bugfixes (also part of 0.2.2.31-rc):
21264 - Write several files in text mode, on OSes that distinguish text
21265 mode from binary mode (namely, Windows). These files are:
21266 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21267 that collect those statistics; 'client_keys' and 'hostname' for
21268 hidden services that use authentication; and (in the tor-gencert
21269 utility) newly generated identity and signing keys. Previously,
21270 we wouldn't specify text mode or binary mode, leading to an
21271 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21272 the DirRecordUsageByCountry option which would have triggered
21273 the assertion failure was added), although this assertion failure
21274 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21275 - Selectively disable deprecation warnings on OS X because Lion
21276 started deprecating the shipped copy of openssl. Fixes bug 3643.
21277 - Remove an extra pair of quotation marks around the error
21278 message in control-port STATUS_GENERAL BUG events. Bugfix on
21279 0.1.2.6-alpha; fixes bug 3732.
21280 - When unable to format an address as a string, report its value
21281 as "???" rather than reusing the last formatted address. Bugfix
21284 o Code simplifications and refactoring:
21285 - Rewrite the listener-selection logic so that parsing which ports
21286 we want to listen on is now separate from binding to the ports
21290 - Building Tor with bufferevent support now requires Libevent
21291 2.0.13-stable or later. Previous versions of Libevent had bugs in
21292 SSL-related bufferevents and related issues that would make Tor
21293 work badly with bufferevents. Requiring 2.0.13-stable also allows
21294 Tor with bufferevents to take advantage of Libevent APIs
21295 introduced after 2.0.8-rc.
21298 Changes in version 0.2.2.32 - 2011-08-27
21299 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21300 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21301 a founder of the PETS community, a leader in our field, a mentor,
21302 and a friend. He left us with these words: "I had the possibility
21303 to contribute to this world that is not as it should be. I hope I
21304 could help in some areas to make the world a better place, and that
21305 I could also encourage other people to be engaged in improving the
21306 world. Please, stay engaged. This world needs you, your love, your
21307 initiative -- now I cannot be part of that anymore."
21309 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21310 ready. More than two years in the making, this release features improved
21311 client performance and hidden service reliability, better compatibility
21312 for Android, correct behavior for bridges that listen on more than
21313 one address, more extensible and flexible directory object handling,
21314 better reporting of network statistics, improved code security, and
21315 many many other features and bugfixes.
21318 Changes in version 0.2.2.31-rc - 2011-08-17
21319 Tor 0.2.2.31-rc is the second and hopefully final release candidate
21320 for the Tor 0.2.2.x series.
21323 - Remove an extra pair of quotation marks around the error
21324 message in control-port STATUS_GENERAL BUG events. Bugfix on
21325 0.1.2.6-alpha; fixes bug 3732.
21326 - If we're configured to write our ControlPorts to disk, only write
21327 them after switching UID and creating the data directory. This way,
21328 we don't fail when starting up with a nonexistent DataDirectory
21329 and a ControlPortWriteToFile setting based on that directory. Fixes
21330 bug 3747; bugfix on Tor 0.2.2.26-beta.
21333 - Update to the August 2 2011 Maxmind GeoLite Country database.
21336 - Allow GETINFO fingerprint to return a fingerprint even when
21337 we have not yet built a router descriptor. Fixes bug 3577;
21338 bugfix on 0.2.0.1-alpha.
21339 - Write several files in text mode, on OSes that distinguish text
21340 mode from binary mode (namely, Windows). These files are:
21341 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21342 that collect those statistics; 'client_keys' and 'hostname' for
21343 hidden services that use authentication; and (in the tor-gencert
21344 utility) newly generated identity and signing keys. Previously,
21345 we wouldn't specify text mode or binary mode, leading to an
21346 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21347 the DirRecordUsageByCountry option which would have triggered
21348 the assertion failure was added), although this assertion failure
21349 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21350 - Selectively disable deprecation warnings on OS X because Lion
21351 started deprecating the shipped copy of openssl. Fixes bug 3643.
21352 - When unable to format an address as a string, report its value
21353 as "???" rather than reusing the last formatted address. Bugfix
21357 Changes in version 0.2.3.2-alpha - 2011-07-18
21358 Tor 0.2.3.2-alpha introduces two new experimental features:
21359 microdescriptors and pluggable transports. It also continues cleaning
21360 up a variety of recently introduced features.
21363 - Clients can now use microdescriptors instead of regular descriptors
21364 to build circuits. Microdescriptors are authority-generated
21365 summaries of regular descriptors' contents, designed to change
21366 very rarely (see proposal 158 for details). This feature is
21367 designed to save bandwidth, especially for clients on slow internet
21368 connections. It's off by default for now, since nearly no caches
21369 support it, but it will be on-by-default for clients in a future
21370 version. You can use the UseMicrodescriptors option to turn it on.
21371 - Tor clients using bridges can now be configured to use a separate
21372 'transport' proxy for each bridge. This approach helps to resist
21373 censorship by allowing bridges to use protocol obfuscation
21374 plugins. It implements part of proposal 180. Implements ticket 2841.
21375 - While we're trying to bootstrap, record how many TLS connections
21376 fail in each state, and report which states saw the most failures
21377 in response to any bootstrap failures. This feature may speed up
21378 diagnosis of censorship events. Implements ticket 3116.
21380 o Major bugfixes (on 0.2.3.1-alpha):
21381 - When configuring a large set of nodes in EntryNodes (as with
21382 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
21383 random subset to be guards, and choose them in random
21384 order. Fixes bug 2798.
21385 - Tor could crash when remembering a consensus in a non-used consensus
21386 flavor without having a current consensus set. Fixes bug 3361.
21387 - Comparing an unknown address to a microdescriptor's shortened exit
21388 policy would always give a "rejected" result. Fixes bug 3599.
21389 - Using microdescriptors as a client no longer prevents Tor from
21390 uploading and downloading hidden service descriptors. Fixes
21394 - Allow nameservers with IPv6 address. Resolves bug 2574.
21395 - Accept attempts to include a password authenticator in the
21396 handshake, as supported by SOCKS5. This handles SOCKS clients that
21397 don't know how to omit a password when authenticating. Resolves
21399 - When configuring a large set of nodes in EntryNodes, and there are
21400 enough of them listed as Guard so that we don't need to consider
21401 the non-guard entries, prefer the ones listed with the Guard flag.
21402 - Check for and recover from inconsistency in the microdescriptor
21403 cache. This will make it harder for us to accidentally free a
21404 microdescriptor without removing it from the appropriate data
21405 structures. Fixes issue 3135; issue noted by "wanoskarnet".
21406 - Log SSL state transitions at log level DEBUG, log domain
21407 HANDSHAKE. This can be useful for debugging censorship events.
21408 Implements ticket 3264.
21409 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
21410 implements ticket 3439.
21412 o Minor bugfixes (on 0.2.3.1-alpha):
21413 - Do not free all general-purpose regular descriptors just
21414 because microdescriptor use is enabled. Fixes bug 3113.
21415 - Correctly link libevent_openssl when --enable-static-libevent
21416 is passed to configure. Fixes bug 3118.
21417 - Bridges should not complain during their heartbeat log messages that
21418 they are unlisted in the consensus: that's more or less the point
21419 of being a bridge. Fixes bug 3183.
21420 - Report a SIGNAL event to controllers when acting on a delayed
21421 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
21422 event to the controller if we acted on a SIGNAL NEWNYM command
21423 immediately, and otherwise not report a SIGNAL event for the
21424 command at all. Fixes bug 3349.
21425 - Fix a crash when handling the SIGNAL controller command or
21426 reporting ERR-level status events with bufferevents enabled. Found
21427 by Robert Ransom. Fixes bug 3367.
21428 - Always ship the tor-fw-helper manpage in our release tarballs.
21429 Fixes bug 3389. Reported by Stephen Walker.
21430 - Fix a class of double-mark-for-close bugs when bufferevents
21431 are enabled. Fixes bug 3403.
21432 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
21433 - Add SIGNAL to the list returned by the 'GETINFO events/names'
21434 control-port command. Fixes part of bug 3465.
21435 - Prevent using negative indices during unit test runs when read_all()
21436 fails. Spotted by coverity.
21437 - Fix a rare memory leak when checking the nodelist without it being
21438 present. Found by coverity.
21439 - Only try to download a microdescriptor-flavored consensus from
21440 a directory cache that provides them.
21442 o Minor bugfixes (on 0.2.2.x and earlier):
21443 - Assert that hidden-service-related operations are not performed
21444 using single-hop circuits. Previously, Tor would assert that
21445 client-side streams are not attached to single-hop circuits,
21446 but not that other sensitive operations on the client and service
21447 side are not performed using single-hop circuits. Fixes bug 3332;
21449 - Don't publish a new relay descriptor when we reload our onion key,
21450 unless the onion key has actually changed. Fixes bug 3263 and
21451 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
21452 - Allow GETINFO fingerprint to return a fingerprint even when
21453 we have not yet built a router descriptor. Fixes bug 3577;
21454 bugfix on 0.2.0.1-alpha.
21455 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
21456 on 0.2.2.4-alpha; fixes bug 3427.
21458 o Code simplification and refactoring:
21459 - Use tor_sscanf() in place of scanf() in more places through the
21460 code. This makes us a little more locale-independent, and
21461 should help shut up code-analysis tools that can't tell
21462 a safe sscanf string from a dangerous one.
21463 - Use tt_assert(), not tor_assert(), for checking for test failures.
21464 This makes the unit tests more able to go on in the event that
21466 - Split connection_about_to_close() into separate functions for each
21470 - On Windows, we now define the _WIN32_WINNT macros only if they
21471 are not already defined. This lets the person building Tor decide,
21472 if they want, to require a later version of Windows.
21475 Changes in version 0.2.2.30-rc - 2011-07-07
21476 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
21477 series. It fixes a few smaller bugs, but generally appears stable.
21478 Please test it and let us know whether it is!
21481 - Send a SUCCEEDED stream event to the controller when a reverse
21482 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21483 discovered by katmagic.
21484 - Always NUL-terminate the sun_path field of a sockaddr_un before
21485 passing it to the kernel. (Not a security issue: kernels are
21486 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21487 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21488 - Don't stack-allocate the list of supplementary GIDs when we're
21489 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21490 could take up to 256K, which is way too much stack. Found by
21491 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21492 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
21493 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
21494 fixes part of bug 3465.
21495 - Fix a memory leak when receiving a descriptor for a hidden
21496 service we didn't ask for. Found by Coverity; CID #30. Bugfix
21500 - Update to the July 1 2011 Maxmind GeoLite Country database.
21503 Changes in version 0.2.2.29-beta - 2011-06-20
21504 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
21505 have bridge lines in their torrc but don't want to use them; gets
21506 us closer to having the control socket feature working on Debian;
21507 and fixes a variety of smaller bugs.
21510 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
21511 When we changed the default behavior to "use bridges if any
21512 are listed in the torrc", we surprised users who had bridges
21513 in their torrc files but who didn't actually want to use them.
21514 Partial resolution for bug 3354.
21517 - Don't attach new streams to old rendezvous circuits after SIGNAL
21518 NEWNYM. Previously, we would keep using an existing rendezvous
21519 circuit if it remained open (i.e. if it were kept open by a
21520 long-lived stream, or if a new stream were attached to it before
21521 Tor could notice that it was old and no longer in use). Bugfix on
21522 0.1.1.15-rc; fixes bug 3375.
21525 - Fix a bug when using ControlSocketsGroupWritable with User. The
21526 directory's group would be checked against the current group, not
21527 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
21528 bugfix on 0.2.2.26-beta.
21529 - Make connection_printf_to_buf()'s behavior sane. Its callers
21530 expect it to emit a CRLF iff the format string ends with CRLF;
21531 it actually emitted a CRLF iff (a) the format string ended with
21532 CRLF or (b) the resulting string was over 1023 characters long or
21533 (c) the format string did not end with CRLF *and* the resulting
21534 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21535 fixes part of bug 3407.
21536 - Make send_control_event_impl()'s behavior sane. Its callers
21537 expect it to always emit a CRLF at the end of the string; it
21538 might have emitted extra control characters as well. Bugfix on
21539 0.1.1.9-alpha; fixes another part of bug 3407.
21540 - Make crypto_rand_int() check the value of its input correctly.
21541 Previously, it accepted values up to UINT_MAX, but could return a
21542 negative number if given a value above INT_MAX+1. Found by George
21543 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21544 - Avoid a segfault when reading a malformed circuit build state
21545 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21547 - When asked about a DNS record type we don't support via a
21548 client DNSPort, reply with NOTIMPL rather than an empty
21549 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21550 - Fix a rare memory leak during stats writing. Found by coverity.
21553 - Update to the June 1 2011 Maxmind GeoLite Country database.
21555 o Code simplifications and refactoring:
21556 - Remove some dead code as indicated by coverity.
21557 - Remove a few dead assignments during router parsing. Found by
21559 - Add some forgotten return value checks during unit tests. Found
21561 - Don't use 1-bit wide signed bit fields. Found by coverity.
21564 Changes in version 0.2.2.28-beta - 2011-06-04
21565 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21566 fixed a big bug in whether relays stay in the consensus consistently,
21567 we moved closer to handling bridges and hidden services correctly,
21568 and we started the process of better handling the dreaded "my Vidalia
21569 died, and now my Tor demands a password when I try to reconnect to it"
21573 - Don't decide to make a new descriptor when receiving a HUP signal.
21574 This bug has caused a lot of 0.2.2.x relays to disappear from the
21575 consensus periodically. Fixes the most common case of triggering
21576 bug 1810; bugfix on 0.2.2.7-alpha.
21577 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21578 - Don't try to build descriptors if "ORPort auto" is set and we
21579 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21581 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21582 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21583 - Apply circuit timeouts to opened hidden-service-related circuits
21584 based on the correct start time. Previously, we would apply the
21585 circuit build timeout based on time since the circuit's creation;
21586 it was supposed to be applied based on time since the circuit
21587 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21588 - Use the same circuit timeout for client-side introduction
21589 circuits as for other four-hop circuits, rather than the timeout
21590 for single-hop directory-fetch circuits; the shorter timeout may
21591 have been appropriate with the static circuit build timeout in
21592 0.2.1.x and earlier, but caused many hidden service access attempts
21593 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21594 on 0.2.2.2-alpha; fixes another part of bug 1297.
21595 - In ticket 2511 we fixed a case where you could use an unconfigured
21596 bridge if you had configured it as a bridge the last time you ran
21597 Tor. Now fix another edge case: if you had configured it as a bridge
21598 but then switched to a different bridge via the controller, you
21599 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21603 - Add an __OwningControllerProcess configuration option and a
21604 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21605 that when it exits, Tor will shut down. Implements feature 3049.
21606 - If "UseBridges 1" is set and no bridges are configured, Tor will
21607 now refuse to build any circuits until some bridges are set.
21608 If "UseBridges auto" is set, Tor will use bridges if they are
21609 configured and we are not running as a server, but otherwise will
21610 make circuits as usual. The new default is "auto". Patch by anonym,
21611 so the Tails LiveCD can stop automatically revealing you as a Tor
21615 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21616 - Remove a trailing asterisk from "exit-policy/default" in the
21617 output of the control port command "GETINFO info/names". Bugfix
21619 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21621 - Warn when the user configures two HiddenServiceDir lines that point
21622 to the same directory. Bugfix on 0.0.6 (the version introducing
21623 HiddenServiceDir); fixes bug 3289.
21624 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21625 part of bug 2748; bugfix on 0.2.0.10-alpha.
21626 - Log malformed requests for rendezvous descriptors as protocol
21627 warnings, not warnings. Also, use a more informative log message
21628 in case someone sees it at log level warning without prior
21629 info-level messages. Fixes the other part of bug 2748; bugfix
21631 - Clear the table recording the time of the last request for each
21632 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21633 Previously, we would clear our HS descriptor cache on SIGNAL
21634 NEWNYM, but if we had previously retrieved a descriptor (or tried
21635 to) from every directory responsible for it, we would refuse to
21636 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21638 - Fix a log message that said "bits" while displaying a value in
21639 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21641 - When checking for 1024-bit keys, check for 1024 bits, not 128
21642 bytes. This allows Tor to correctly discard keys of length 1017
21643 through 1023. Bugfix on 0.0.9pre5.
21646 - Relays now log the reason for publishing a new relay descriptor,
21647 so we have a better chance of hunting down instances of bug 1810.
21648 Resolves ticket 3252.
21649 - Revise most log messages that refer to nodes by nickname to
21650 instead use the "$key=nickname at address" format. This should be
21651 more useful, especially since nicknames are less and less likely
21652 to be unique. Resolves ticket 3045.
21653 - Log (at info level) when purging pieces of hidden-service-client
21654 state because of SIGNAL NEWNYM.
21657 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21658 anything since 0.2.1.16-rc.
21661 Changes in version 0.2.2.27-beta - 2011-05-18
21662 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21663 release, and also adds a few more general bugfixes.
21666 - Fix a crash bug when changing bridges in a running Tor process.
21667 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21668 - When the controller configures a new bridge, don't wait 10 to 60
21669 seconds before trying to fetch its descriptor. Bugfix on
21670 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21673 - Require that onion keys have exponent 65537 in microdescriptors too.
21674 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21675 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21676 Changed the limit to 512 characters by removing base64 newlines.
21677 Fixes bug 2752. Fix by Michael Yakubovich.
21678 - When a client starts or stops using bridges, never use a circuit
21679 that was built before the configuration change. This behavior could
21680 put at risk a user who uses bridges to ensure that her traffic
21681 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21685 Changes in version 0.2.2.26-beta - 2011-05-17
21686 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21687 also introduces a new "socksport auto" approach that should make it
21688 easier to run multiple Tors on the same system, and does a lot of
21689 cleanup to get us closer to a release candidate.
21691 o Security/privacy fixes:
21692 - Replace all potentially sensitive memory comparison operations
21693 with versions whose runtime does not depend on the data being
21694 compared. This will help resist a class of attacks where an
21695 adversary can use variations in timing information to learn
21696 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21697 implementation by Robert Ransom based partially on code by DJB.)
21698 - When receiving a hidden service descriptor, check that it is for
21699 the hidden service we wanted. Previously, Tor would store any
21700 hidden service descriptors that a directory gave it, whether it
21701 wanted them or not. This wouldn't have let an attacker impersonate
21702 a hidden service, but it did let directories pre-seed a client
21703 with descriptors that it didn't want. Bugfix on 0.0.6.
21704 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21705 DNS cache entries, and virtual address mappings: that's what
21706 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21709 - The options SocksPort, ControlPort, and so on now all accept a
21710 value "auto" that opens a socket on an OS-selected port. A
21711 new ControlPortWriteToFile option tells Tor to write its
21712 actual control port or ports to a chosen file. If the option
21713 ControlPortFileGroupReadable is set, the file is created as
21714 group-readable. Now users can run two Tor clients on the same
21715 system without needing to manually mess with parameters. Resolves
21716 part of ticket 3076.
21717 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21718 help busy exit nodes avoid running out of useable ports just
21719 because all the ports have been used in the near past. Resolves
21723 - New "GETINFO net/listeners/(type)" controller command to return
21724 a list of addresses and ports that are bound for listeners for a
21725 given connection type. This is useful when the user has configured
21726 "SocksPort auto" and the controller needs to know which port got
21727 chosen. Resolves another part of ticket 3076.
21728 - Add a new ControlSocketsGroupWritable configuration option: when
21729 it is turned on, ControlSockets are group-writeable by the default
21730 group of the current user. Patch by Jérémy Bobbio; implements
21732 - Tor now refuses to create a ControlSocket in a directory that is
21733 world-readable (or group-readable if ControlSocketsGroupWritable
21734 is 0). This is necessary because some operating systems do not
21735 enforce permissions on an AF_UNIX sockets. Permissions on the
21736 directory holding the socket, however, seems to work everywhere.
21737 - Rate-limit a warning about failures to download v2 networkstatus
21738 documents. Resolves part of bug 1352.
21739 - Backport code from 0.2.3.x that allows directory authorities to
21740 clean their microdescriptor caches. Needed to resolve bug 2230.
21741 - When an HTTPS proxy reports "403 Forbidden", we now explain
21742 what it means rather than calling it an unexpected status code.
21743 Closes bug 2503. Patch from Michael Yakubovich.
21744 - Update to the May 1 2011 Maxmind GeoLite Country database.
21747 - Authorities now clean their microdesc cache periodically and when
21748 reading from disk initially, not only when adding new descriptors.
21749 This prevents a bug where we could lose microdescriptors. Bugfix
21750 on 0.2.2.6-alpha. Fixes bug 2230.
21751 - Do not crash when our configuration file becomes unreadable, for
21752 example due to a permissions change, between when we start up
21753 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21755 - Avoid a bug that would keep us from replacing a microdescriptor
21756 cache on Windows. (We would try to replace the file while still
21757 holding it open. That's fine on Unix, but Windows doesn't let us
21758 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
21759 - Add missing explanations for the authority-related torrc options
21760 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
21761 man page. Resolves issue 2379.
21762 - As an authority, do not upload our own vote or signature set to
21763 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
21764 it would get flagged as a duplicate. Resolves bug 3026.
21765 - Accept hidden service descriptors if we think we might be a hidden
21766 service directory, regardless of what our consensus says. This
21767 helps robustness, since clients and hidden services can sometimes
21768 have a more up-to-date view of the network consensus than we do,
21769 and if they think that the directory authorities list us a HSDir,
21770 we might actually be one. Related to bug 2732; bugfix on
21772 - When a controller changes TrackHostExits, remove mappings for
21773 hosts that should no longer have their exits tracked. Bugfix on
21775 - When a controller changes VirtualAddrNetwork, remove any mappings
21776 for hosts that were automapped to the old network. Bugfix on
21778 - When a controller changes one of the AutomapHosts* options, remove
21779 any mappings for hosts that should no longer be automapped. Bugfix
21781 - Do not reset the bridge descriptor download status every time we
21782 re-parse our configuration or get a configuration change. Fixes
21783 bug 3019; bugfix on 0.2.0.3-alpha.
21785 o Minor bugfixes (code cleanup):
21786 - When loading the microdesc journal, remember its current size.
21787 In 0.2.2, this helps prevent the microdesc journal from growing
21788 without limit on authorities (who are the only ones to use it in
21789 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21790 Fix posted by "cypherpunks."
21791 - The microdesc journal is supposed to get rebuilt only if it is
21792 at least _half_ the length of the store, not _twice_ the length
21793 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21794 - Fix a potential null-pointer dereference while computing a
21795 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21797 - Avoid a possible null-pointer dereference when rebuilding the mdesc
21798 cache without actually having any descriptors to cache. Bugfix on
21799 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
21800 - If we fail to compute the identity digest of a v3 legacy keypair,
21801 warn, and don't use a buffer-full of junk instead. Bugfix on
21802 0.2.1.1-alpha; fixes bug 3106.
21803 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21804 where if the function had ever in the future been used to check
21805 for the presence of a too-large number, it would have given an
21806 incorrect result. (Fortunately, we only used it for 16-bit
21807 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21808 - Require that introduction point keys and onion handshake keys
21809 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21812 o Removed features:
21813 - Caches no longer download and serve v2 networkstatus documents
21814 unless FetchV2Networkstatus flag is set: these documents haven't
21815 haven't been used by clients or relays since 0.2.0.x. Resolves
21819 Changes in version 0.2.3.1-alpha - 2011-05-05
21820 Tor 0.2.3.1-alpha adds some new experimental features, including support
21821 for an improved network IO backend, IOCP networking on Windows,
21822 microdescriptor caching, "fast-start" support for streams, and automatic
21823 home router configuration. There are also numerous internal improvements
21824 to try to make the code easier for developers to work with.
21826 This is the first alpha release in a new series, so expect there to be
21827 bugs. Users who would rather test out a more stable branch should
21828 stay with 0.2.2.x for now.
21831 - Tor can now optionally build with the "bufferevents" buffered IO
21832 backend provided by Libevent 2. To use this feature, make sure you
21833 have the latest possible version of Libevent, and pass the
21834 --enable-bufferevents flag to configure when building Tor from
21835 source. This feature will make our networking code more flexible,
21836 let us stack layers on each other, and let us use more efficient
21837 zero-copy transports where available.
21838 - As an experimental feature, Tor can use IOCP for networking on Windows.
21839 Once this code is tuned and optimized, it promises much better
21840 performance than the select-based backend we've used in the past. To
21841 try this feature, you must build Tor with Libevent 2, configure Tor
21842 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
21843 your torrc. There are known bugs here: only try this if you can help
21844 debug it as it breaks.
21845 - The EntryNodes option can now include country codes like {de} or IP
21846 addresses or network masks. Previously we had disallowed these options
21847 because we didn't have an efficient way to keep the list up to
21848 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
21849 - Exit nodes now accept and queue data on not-yet-connected streams.
21850 Previously, the client wasn't allowed to send data until the stream was
21851 connected, which slowed down all connections. This change will enable
21852 clients to perform a "fast-start" on streams and send data without
21853 having to wait for a confirmation that the stream has opened. (Patch
21854 from Ian Goldberg; implements the server side of Proposal 174.)
21855 - Tor now has initial support for automatic port mapping on the many
21856 home routers that support NAT-PMP or UPnP. (Not yet supported on
21857 Windows). To build the support code, you'll need to have libnatpnp
21858 library and/or the libminiupnpc library, and you'll need to enable the
21859 feature specifically by passing "--enable-upnp" and/or
21860 "--enable-natpnp" to configure. To turn it on, use the new
21861 PortForwarding option.
21862 - Caches now download, cache, and serve multiple "flavors" of the
21863 consensus, including a flavor that describes microdescriptors.
21864 - Caches now download, cache, and serve microdescriptors -- small
21865 summaries of router descriptors that are authenticated by all of the
21866 directory authorities. Once enough caches are running this code,
21867 clients will be able to save significant amounts of directory bandwidth
21868 by downloading microdescriptors instead of router descriptors.
21871 - Make logging resolution configurable with a new LogTimeGranularity
21872 option, and change the default from 1 millisecond to 1 second.
21873 Implements enhancement 1668.
21874 - We log which torrc file we're using on startup. Implements ticket
21876 - Ordinarily, Tor does not count traffic from private addresses (like
21877 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
21878 There is now a new option, CountPrivateBandwidth, to disable this
21879 behavior. Patch from Daniel Cagara.
21880 - New --enable-static-tor configure option for building Tor as
21881 statically as possible. Idea, general hackery and thoughts from
21882 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
21884 - If you set the NumCPUs option to 0, Tor will now try to detect how
21885 many CPUs you have. This is the new default behavior.
21886 - Turn on directory request statistics by default and include them in
21887 extra-info descriptors. Don't break if we have no GeoIP database.
21888 - Relays that set "ConnDirectionStatistics 1" write statistics on the
21889 bidirectional use of connections to disk every 24 hours.
21890 - Add a GeoIP file digest to the extra-info descriptor. Implements
21892 - The NodeFamily option -- which let you declare that you want to
21893 consider nodes to be part of a family whether they list themselves
21894 that way or not -- now allows IP address ranges and country codes.
21895 - Add a new 'Heartbeat' log message type to periodically log a message
21896 describing Tor's status at level Notice. This feature is meant for
21897 operators who log at notice, and want to make sure that their Tor
21898 server is still working. Implementation by George Kadianakis.
21900 o Minor bugfixes (on 0.2.2.25-alpha):
21901 - When loading the microdesc journal, remember its current size.
21902 In 0.2.2, this helps prevent the microdesc journal from growing
21903 without limit on authorities (who are the only ones to use it in
21904 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21905 Fix posted by "cypherpunks."
21906 - The microdesc journal is supposed to get rebuilt only if it is
21907 at least _half_ the length of the store, not _twice_ the length
21908 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21909 - If as an authority we fail to compute the identity digest of a v3
21910 legacy keypair, warn, and don't use a buffer-full of junk instead.
21911 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
21912 - Authorities now clean their microdesc cache periodically and when
21913 reading from disk initially, not only when adding new descriptors.
21914 This prevents a bug where we could lose microdescriptors. Bugfix
21917 o Minor features (controller):
21918 - Add a new SIGNAL event to the controller interface so that
21919 controllers can be notified when Tor handles a signal. Resolves
21920 issue 1955. Patch by John Brooks.
21921 - Add a new GETINFO option to get total bytes read and written. Patch
21922 from pipe, revised by atagar. Resolves ticket 2345.
21923 - Implement some GETINFO controller fields to provide information about
21924 the Tor process's pid, euid, username, and resource limits.
21927 - Our build system requires automake 1.6 or later to create the
21928 Makefile.in files. Previously, you could have used 1.4.
21929 This only affects developers and people building Tor from git;
21930 people who build Tor from the source distribution without changing
21931 the Makefile.am files should be fine.
21932 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
21933 so on. This is more robust against some of the failure modes
21934 associated with running the autotools pieces on their own.
21936 o Minor packaging issues:
21937 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
21938 already created. Patch from Andreas Stieger. Fixes bug 2573.
21940 o Code simplifications and refactoring:
21941 - A major revision to our internal node-selecting and listing logic.
21942 Tor already had at least two major ways to look at the question of
21943 "which Tor servers do we know about": a list of router descriptors,
21944 and a list of entries in the current consensus. With
21945 microdescriptors, we're adding a third. Having so many systems
21946 without an abstraction layer over them was hurting the codebase.
21947 Now, we have a new "node_t" abstraction that presents a consistent
21948 interface to a client's view of a Tor node, and holds (nearly) all
21949 of the mutable state formerly in routerinfo_t and routerstatus_t.
21950 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
21951 no longer link against Libevent: they never used it, but
21952 our library structure used to force them to link it.
21954 o Removed features:
21955 - Remove some old code to work around even older versions of Tor that
21956 used forked processes to handle DNS requests. Such versions of Tor
21957 are no longer in use as servers.
21959 o Documentation fixes:
21960 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21961 - Add missing documentation for the authority-related torrc options
21962 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
21966 Changes in version 0.2.2.25-alpha - 2011-04-29
21967 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
21968 robust, routers no longer overreport their bandwidth, Win7 should crash
21969 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
21970 now prevents hidden service-related activity from being linkable. It
21971 provides more information to Vidalia so you can see if your bridge is
21972 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
21973 StrictNodes configuration options to make them more reliable, more
21974 understandable, and more regularly applied. If you use those options,
21975 please see the revised documentation for them in the manual page.
21978 - Relays were publishing grossly inflated bandwidth values because
21979 they were writing their state files wrong--now they write the
21980 correct value. Also, resume reading bandwidth history from the
21981 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
21982 - Improve hidden service robustness: When we find that we have
21983 extended a hidden service's introduction circuit to a relay not
21984 listed as an introduction point in the HS descriptor we currently
21985 have, retry with an introduction point from the current
21986 descriptor. Previously we would just give up. Fixes bugs 1024 and
21987 1930; bugfix on 0.2.0.10-alpha.
21988 - Clients now stop trying to use an exit node associated with a given
21989 destination by TrackHostExits if they fail to reach that exit node.
21990 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21991 - Fix crash bug on platforms where gmtime and localtime can return
21992 NULL. Windows 7 users were running into this one. Fixes part of bug
21993 2077. Bugfix on all versions of Tor. Found by boboper.
21995 o Security and stability fixes:
21996 - Don't double-free a parsable, but invalid, microdescriptor, even if
21997 it is followed in the blob we're parsing by an unparsable
21998 microdescriptor. Fixes an issue reported in a comment on bug 2954.
21999 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
22000 - If the Nickname configuration option isn't given, Tor would pick a
22001 nickname based on the local hostname as the nickname for a relay.
22002 Because nicknames are not very important in today's Tor and the
22003 "Unnamed" nickname has been implemented, this is now problematic
22004 behavior: It leaks information about the hostname without being
22005 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
22006 introduced the Unnamed nickname. Reported by tagnaq.
22007 - Fix an uncommon assertion failure when running with DNSPort under
22008 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22009 - Avoid linkability based on cached hidden service descriptors: forget
22010 all hidden service descriptors cached as a client when processing a
22011 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22014 - Export GeoIP information on bridge usage to controllers even if we
22015 have not yet been running for 24 hours. Now Vidalia bridge operators
22016 can get more accurate and immediate feedback about their
22017 contributions to the network.
22019 o Major features and bugfixes (node selection):
22020 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
22021 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
22022 options. Previously, we had been ambiguous in describing what
22023 counted as an "exit" node, and what operations exactly "StrictNodes
22024 0" would permit. This created confusion when people saw nodes built
22025 through unexpected circuits, and made it hard to tell real bugs from
22026 surprises. Now the intended behavior is:
22027 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
22028 a node that delivers user traffic outside the Tor network.
22029 . "Entry", in the context of EntryNodes, means a node used as the
22030 first hop of a multihop circuit. It doesn't include direct
22031 connections to directory servers.
22032 . "ExcludeNodes" applies to all nodes.
22033 . "StrictNodes" changes the behavior of ExcludeNodes only. When
22034 StrictNodes is set, Tor should avoid all nodes listed in
22035 ExcludeNodes, even when it will make user requests fail. When
22036 StrictNodes is *not* set, then Tor should follow ExcludeNodes
22037 whenever it can, except when it must use an excluded node to
22038 perform self-tests, connect to a hidden service, provide a
22039 hidden service, fulfill a .exit request, upload directory
22040 information, or fetch directory information.
22041 Collectively, the changes to implement the behavior fix bug 1090.
22042 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
22043 a node is listed in both, it's treated as excluded.
22044 - ExcludeNodes now applies to directory nodes -- as a preference if
22045 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
22046 Don't exclude all the directory authorities and set StrictNodes to 1
22047 unless you really want your Tor to break.
22048 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
22049 - ExcludeExitNodes now overrides .exit requests.
22050 - We don't use bridges listed in ExcludeNodes.
22051 - When StrictNodes is 1:
22052 . We now apply ExcludeNodes to hidden service introduction points
22053 and to rendezvous points selected by hidden service users. This
22054 can make your hidden service less reliable: use it with caution!
22055 . If we have used ExcludeNodes on ourself, do not try relay
22056 reachability self-tests.
22057 . If we have excluded all the directory authorities, we will not
22058 even try to upload our descriptor if we're a relay.
22059 . Do not honor .exit requests to an excluded node.
22060 - Remove a misfeature that caused us to ignore the Fast/Stable flags
22061 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
22062 - When the set of permitted nodes changes, we now remove any mappings
22063 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
22065 - We never cannibalize a circuit that had excluded nodes on it, even
22066 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
22067 - Revert a change where we would be laxer about attaching streams to
22068 circuits than when building the circuits. This was meant to prevent
22069 a set of bugs where streams were never attachable, but our improved
22070 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
22071 - Keep track of how many times we launch a new circuit to handle a
22072 given stream. Too many launches could indicate an inconsistency
22073 between our "launch a circuit to handle this stream" logic and our
22074 "attach this stream to one of the available circuits" logic.
22075 - Improve log messages related to excluded nodes.
22078 - Fix a spurious warning when moving from a short month to a long
22079 month on relays with month-based BandwidthAccounting. Bugfix on
22080 0.2.2.17-alpha; fixes bug 3020.
22081 - When a client finds that an origin circuit has run out of 16-bit
22082 stream IDs, we now mark it as unusable for new streams. Previously,
22083 we would try to close the entire circuit. Bugfix on 0.0.6.
22084 - Add a forgotten cast that caused a compile warning on OS X 10.6.
22085 Bugfix on 0.2.2.24-alpha.
22086 - Be more careful about reporting the correct error from a failed
22087 connect() system call. Under some circumstances, it was possible to
22088 look at an incorrect value for errno when sending the end reason.
22089 Bugfix on 0.1.0.1-rc.
22090 - Correctly handle an "impossible" overflow cases in connection byte
22091 counting, where we write or read more than 4GB on an edge connection
22092 in a single second. Bugfix on 0.1.2.8-beta.
22093 - Correct the warning displayed when a rendezvous descriptor exceeds
22094 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22096 - Clients and hidden services now use HSDir-flagged relays for hidden
22097 service descriptor downloads and uploads even if the relays have no
22098 DirPort set and the client has disabled TunnelDirConns. This will
22099 eventually allow us to give the HSDir flag to relays with no
22100 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
22101 - Downgrade "no current certificates known for authority" message from
22102 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22103 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
22104 2917. Bugfix on 0.1.1.1-alpha.
22105 - Only limit the lengths of single HS descriptors, even when multiple
22106 HS descriptors are published to an HSDir relay in a single POST
22107 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
22108 - Write the current time into the LastWritten line in our state file,
22109 rather than the time from the previous write attempt. Also, stop
22110 trying to use a time of -1 in our log statements. Fixes bug 3039;
22111 bugfix on 0.2.2.14-alpha.
22112 - Be more consistent in our treatment of file system paths. "~" should
22113 get expanded to the user's home directory in the Log config option.
22114 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
22115 feature for the -f and --DataDirectory options.
22118 - Make sure every relay writes a state file at least every 12 hours.
22119 Previously, a relay could go for weeks without writing its state
22120 file, and on a crash could lose its bandwidth history, capacity
22121 estimates, client country statistics, and so on. Addresses bug 3012.
22122 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22123 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22124 clients are already deprecated because of security bugs.
22125 - Don't allow v0 hidden service authorities to act as clients.
22126 Required by fix for bug 3000.
22127 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22128 by fix for bug 3000.
22129 - Ensure that no empty [dirreq-](read|write)-history lines are added
22130 to an extrainfo document. Implements ticket 2497.
22132 o Code simplification and refactoring:
22133 - Remove workaround code to handle directory responses from servers
22134 that had bug 539 (they would send HTTP status 503 responses _and_
22135 send a body too). Since only server versions before
22136 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22137 keep the workaround in place.
22138 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22139 handling calculations where we have a known amount of clock skew and
22140 an allowed amount of unknown skew. But we only used it in three
22141 places, and we never adjusted the known/unknown skew values. This is
22142 still something we might want to do someday, but if we do, we'll
22143 want to do it differently.
22144 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22145 None of the cases where we did this before were wrong, but by making
22146 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22147 - Use GetTempDir to find the proper temporary directory location on
22148 Windows when generating temporary files for the unit tests. Patch by
22152 Changes in version 0.2.2.24-alpha - 2011-04-08
22153 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
22154 prevented Tor clients from effectively using "multihomed" bridges,
22155 that is, bridges that listen on multiple ports or IP addresses so users
22156 can continue to use some of their addresses even if others get blocked.
22159 - Fix a bug where bridge users who configure the non-canonical
22160 address of a bridge automatically switch to its canonical
22161 address. If a bridge listens at more than one address, it should be
22162 able to advertise those addresses independently and any non-blocked
22163 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
22165 - If you configured Tor to use bridge A, and then quit and
22166 configured Tor to use bridge B instead, it would happily continue
22167 to use bridge A if it's still reachable. While this behavior is
22168 a feature if your goal is connectivity, in some scenarios it's a
22169 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22170 - Directory authorities now use data collected from their own
22171 uptime observations when choosing whether to assign the HSDir flag
22172 to relays, instead of trusting the uptime value the relay reports in
22173 its descriptor. This change helps prevent an attack where a small
22174 set of nodes with frequently-changing identity keys can blackhole
22175 a hidden service. (Only authorities need upgrade; others will be
22176 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22179 - When we restart our relay, we might get a successful connection
22180 from the outside before we've started our reachability tests,
22181 triggering a warning: "ORPort found reachable, but I have no
22182 routerinfo yet. Failing to inform controller of success." This
22183 bug was harmless unless Tor is running under a controller
22184 like Vidalia, in which case the controller would never get a
22185 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22187 - Make directory authorities more accurate at recording when
22188 relays that have failed several reachability tests became
22189 unreachable, so we can provide more accuracy at assigning Stable,
22190 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22191 - Fix an issue that prevented static linking of libevent on
22192 some platforms (notably Linux). Fixes bug 2698; bugfix on
22193 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
22194 the --with-static-libevent configure option).
22195 - We now ask the other side of a stream (the client or the exit)
22196 for more data on that stream when the amount of queued data on
22197 that stream dips low enough. Previously, we wouldn't ask the
22198 other side for more data until either it sent us more data (which
22199 it wasn't supposed to do if it had exhausted its window!) or we
22200 had completely flushed all our queued data. This flow control fix
22201 should improve throughput. Fixes bug 2756; bugfix on the earliest
22202 released versions of Tor (svn commit r152).
22203 - Avoid a double-mark-for-free warning when failing to attach a
22204 transparent proxy connection. (We thought we had fixed this in
22205 0.2.2.23-alpha, but it turns out our fix was checking the wrong
22206 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
22207 bug) and 0.2.2.23-alpha (the incorrect fix).
22208 - When warning about missing zlib development packages during compile,
22209 give the correct package names. Bugfix on 0.2.0.1-alpha.
22212 - Directory authorities now log the source of a rejected POSTed v3
22213 networkstatus vote.
22214 - Make compilation with clang possible when using
22215 --enable-gcc-warnings by removing two warning options that clang
22216 hasn't implemented yet and by fixing a few warnings. Implements
22218 - When expiring circuits, use microsecond timers rather than
22219 one-second timers. This can avoid an unpleasant situation where a
22220 circuit is launched near the end of one second and expired right
22221 near the beginning of the next, and prevent fluctuations in circuit
22223 - Use computed circuit-build timeouts to decide when to launch
22224 parallel introduction circuits for hidden services. (Previously,
22225 we would retry after 15 seconds.)
22226 - Update to the April 1 2011 Maxmind GeoLite Country database.
22229 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22230 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22232 o Documentation changes:
22233 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22234 - Resolve all doxygen warnings except those for missing documentation.
22236 - Add doxygen documentation for more functions, fields, and types.
22239 Changes in version 0.2.2.23-alpha - 2011-03-08
22240 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
22241 they restart they don't lose their bandwidth capacity estimate. This
22242 release also fixes a diverse set of user-facing bugs, ranging from
22243 relays overrunning their rate limiting to clients falsely warning about
22244 clock skew to bridge descriptor leaks by our bridge directory authority.
22247 - Stop sending a CLOCK_SKEW controller status event whenever
22248 we fetch directory information from a relay that has a wrong clock.
22249 Instead, only inform the controller when it's a trusted authority
22250 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22251 the rest of bug 1074.
22252 - Fix an assert in parsing router descriptors containing IPv6
22253 addresses. This one took down the directory authorities when
22254 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22255 - Make the bridge directory authority refuse to answer directory
22256 requests for "all" descriptors. It used to include bridge
22257 descriptors in its answer, which was a major information leak.
22258 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22259 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22260 Tor would ignore their RelayBandwidthBurst setting,
22261 potentially using more bandwidth than expected. Bugfix on
22262 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22263 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22264 hidserv" in her torrc. The 'hidserv' argument never controlled
22265 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22268 - Relays now save observed peak bandwidth throughput rates to their
22269 state file (along with total usage, which was already saved)
22270 so that they can determine their correct estimated bandwidth on
22271 restart. Resolves bug 1863, where Tor relays would reset their
22272 estimated bandwidth to 0 after restarting.
22273 - Directory authorities now take changes in router IP address and
22274 ORPort into account when determining router stability. Previously,
22275 if a router changed its IP or ORPort, the authorities would not
22276 treat it as having any downtime for the purposes of stability
22277 calculation, whereas clients would experience downtime since the
22278 change could take a while to propagate to them. Resolves issue 1035.
22279 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22280 Prevention (DEP) by default on Windows to make it harder for
22281 attackers to exploit vulnerabilities. Patch from John Brooks.
22283 o Minor bugfixes (on 0.2.1.x and earlier):
22284 - Fix a rare crash bug that could occur when a client was configured
22285 with a large number of bridges. Fixes bug 2629; bugfix on
22286 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22287 - Avoid a double mark-for-free warning when failing to attach a
22288 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22290 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22291 found by "cypherpunks". This bug was introduced before the first
22292 Tor release, in svn commit r110.
22293 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
22294 don't mention them in the manpage. Fixes bug 2450; issue
22295 spotted by keb and G-Lo.
22296 - Fix a bug in bandwidth history state parsing that could have been
22297 triggered if a future version of Tor ever changed the timing
22298 granularity at which bandwidth history is measured. Bugfix on
22299 Tor 0.1.1.11-alpha.
22300 - When a relay decides that its DNS is too broken for it to serve
22301 as an exit server, it advertised itself as a non-exit, but
22302 continued to act as an exit. This could create accidental
22303 partitioning opportunities for users. Instead, if a relay is
22304 going to advertise reject *:* as its exit policy, it should
22305 really act with exit policy "reject *:*". Fixes bug 2366.
22306 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22307 - In the special case where you configure a public exit relay as your
22308 bridge, Tor would be willing to use that exit relay as the last
22309 hop in your circuit as well. Now we fail that circuit instead.
22310 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22311 - Fix a bug with our locking implementation on Windows that couldn't
22312 correctly detect when a file was already locked. Fixes bug 2504,
22313 bugfix on 0.2.1.6-alpha.
22314 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22315 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22317 - Set target port in get_interface_address6() correctly. Bugfix
22318 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22319 - Directory authorities are now more robust to hops back in time
22320 when calculating router stability. Previously, if a run of uptime
22321 or downtime appeared to be negative, the calculation could give
22322 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22324 - Fix an assert that got triggered when using the TestingTorNetwork
22325 configuration option and then issuing a GETINFO config-text control
22326 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22328 o Minor bugfixes (on 0.2.2.x):
22329 - Clients should not weight BadExit nodes as Exits in their node
22330 selection. Similarly, directory authorities should not count BadExit
22331 bandwidth as Exit bandwidth when computing bandwidth-weights.
22332 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
22333 - Correctly clear our dir_read/dir_write history when there is an
22334 error parsing any bw history value from the state file. Bugfix on
22335 Tor 0.2.2.15-alpha.
22336 - Resolve a bug in verifying signatures of directory objects
22337 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
22338 Fixes bug 2409. Found by "piebeer".
22339 - Bridge authorities no longer crash on SIGHUP when they try to
22340 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
22344 - Log less aggressively about circuit timeout changes, and improve
22345 some other circuit timeout messages. Resolves bug 2004.
22346 - Log a little more clearly about the times at which we're no longer
22347 accepting new connections. Resolves bug 2181.
22348 - Reject attempts at the client side to open connections to private
22349 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22350 a randomly chosen exit node. Attempts to do so are always
22351 ill-defined, generally prevented by exit policies, and usually
22352 in error. This will also help to detect loops in transparent
22353 proxy configurations. You can disable this feature by setting
22354 "ClientRejectInternalAddresses 0" in your torrc.
22355 - Always treat failure to allocate an RSA key as an unrecoverable
22357 - Update to the March 1 2011 Maxmind GeoLite Country database.
22359 o Minor features (log subsystem):
22360 - Add documentation for configuring logging at different severities in
22361 different log domains. We've had this feature since 0.2.1.1-alpha,
22362 but for some reason it never made it into the manpage. Fixes
22364 - Make it simpler to specify "All log domains except for A and B".
22365 Previously you needed to say "[*,~A,~B]". Now you can just say
22367 - Add a "LogMessageDomains 1" option to include the domains of log
22368 messages along with the messages. Without this, there's no way
22369 to use log domains without reading the source or doing a lot
22372 o Packaging changes:
22373 - Stop shipping the Tor specs files and development proposal documents
22374 in the tarball. They are now in a separate git repository at
22375 git://git.torproject.org/torspec.git
22378 Changes in version 0.2.1.30 - 2011-02-23
22379 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22380 change is a slight tweak to Tor's TLS handshake that makes relays
22381 and bridges that run this new version reachable from Iran again.
22382 We don't expect this tweak will win the arms race long-term, but it
22383 buys us time until we roll out a better solution.
22386 - Stop sending a CLOCK_SKEW controller status event whenever
22387 we fetch directory information from a relay that has a wrong clock.
22388 Instead, only inform the controller when it's a trusted authority
22389 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22390 the rest of bug 1074.
22391 - Fix a bounds-checking error that could allow an attacker to
22392 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22393 Found by "piebeer".
22394 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22395 Tor would ignore their RelayBandwidthBurst setting,
22396 potentially using more bandwidth than expected. Bugfix on
22397 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22398 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22399 hidserv" in her torrc. The 'hidserv' argument never controlled
22400 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22403 - Adjust our TLS Diffie-Hellman parameters to match those used by
22405 - Update to the February 1 2011 Maxmind GeoLite Country database.
22408 - Check for and reject overly long directory certificates and
22409 directory tokens before they have a chance to hit any assertions.
22410 Bugfix on 0.2.1.28. Found by "doorss".
22411 - Bring the logic that gathers routerinfos and assesses the
22412 acceptability of circuits into line. This prevents a Tor OP from
22413 getting locked in a cycle of choosing its local OR as an exit for a
22414 path (due to a .exit request) and then rejecting the circuit because
22415 its OR is not listed yet. It also prevents Tor clients from using an
22416 OR running in the same instance as an exit (due to a .exit request)
22417 if the OR does not meet the same requirements expected of an OR
22418 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22420 o Packaging changes:
22421 - Stop shipping the Tor specs files and development proposal documents
22422 in the tarball. They are now in a separate git repository at
22423 git://git.torproject.org/torspec.git
22424 - Do not include Git version tags as though they are SVN tags when
22425 generating a tarball from inside a repository that has switched
22426 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22429 Changes in version 0.2.2.22-alpha - 2011-01-25
22430 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
22431 main other change is a slight tweak to Tor's TLS handshake that makes
22432 relays and bridges that run this new version reachable from Iran again.
22433 We don't expect this tweak will win the arms race long-term, but it
22434 will buy us a bit more time until we roll out a better solution.
22437 - Fix a bounds-checking error that could allow an attacker to
22438 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22439 Found by "piebeer".
22440 - Don't assert when changing from bridge to relay or vice versa
22441 via the controller. The assert happened because we didn't properly
22442 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
22443 bug 2433. Reported by bastik.
22446 - Adjust our TLS Diffie-Hellman parameters to match those used by
22448 - Provide a log message stating which geoip file we're parsing
22449 instead of just stating that we're parsing the geoip file.
22450 Implements ticket 2432.
22453 - Check for and reject overly long directory certificates and
22454 directory tokens before they have a chance to hit any assertions.
22455 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
22458 Changes in version 0.2.2.21-alpha - 2011-01-15
22459 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
22460 continues our recent code security audit work. The main fix resolves
22461 a remote heap overflow vulnerability that can allow remote code
22462 execution (CVE-2011-0427). Other fixes address a variety of assert
22463 and crash bugs, most of which we think are hard to exploit remotely.
22465 o Major bugfixes (security), also included in 0.2.1.29:
22466 - Fix a heap overflow bug where an adversary could cause heap
22467 corruption. This bug probably allows remote code execution
22468 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22470 - Prevent a denial-of-service attack by disallowing any
22471 zlib-compressed data whose compression factor is implausibly
22472 high. Fixes part of bug 2324; reported by "doorss".
22473 - Zero out a few more keys in memory before freeing them. Fixes
22474 bug 2384 and part of bug 2385. These key instances found by
22475 "cypherpunks", based on Andrew Case's report about being able
22476 to find sensitive data in Tor's memory space if you have enough
22477 permissions. Bugfix on 0.0.2pre9.
22479 o Major bugfixes (crashes), also included in 0.2.1.29:
22480 - Prevent calls to Libevent from inside Libevent log handlers.
22481 This had potential to cause a nasty set of crashes, especially
22482 if running Libevent with debug logging enabled, and running
22483 Tor with a controller watching for low-severity log messages.
22484 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22485 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22486 underflow errors there too. Fixes the other part of bug 2324.
22487 - Fix a bug where we would assert if we ever had a
22488 cached-descriptors.new file (or another file read directly into
22489 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22490 on 0.2.1.25. Found by doorss.
22491 - Fix some potential asserts and parsing issues with grossly
22492 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22495 o Minor bugfixes (other), also included in 0.2.1.29:
22496 - Fix a bug with handling misformed replies to reverse DNS lookup
22497 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22498 bug reported by doorss.
22499 - Fix compilation on mingw when a pthreads compatibility library
22500 has been installed. (We don't want to use it, so we shouldn't
22501 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22502 - Fix a bug where we would declare that we had run out of virtual
22503 addresses when the address space was only half-exhausted. Bugfix
22505 - Correctly handle the case where AutomapHostsOnResolve is set but
22506 no virtual addresses are available. Fixes bug 2328; bugfix on
22507 0.1.2.1-alpha. Bug found by doorss.
22508 - Correctly handle wrapping around when we run out of virtual
22509 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22511 o Minor features, also included in 0.2.1.29:
22512 - Update to the January 1 2011 Maxmind GeoLite Country database.
22513 - Introduce output size checks on all of our decryption functions.
22515 o Build changes, also included in 0.2.1.29:
22516 - Tor does not build packages correctly with Automake 1.6 and earlier;
22517 added a check to Makefile.am to make sure that we're building with
22518 Automake 1.7 or later.
22519 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22520 because we built it with a too-old version of automake. Thus that
22521 release broke ./configure --enable-openbsd-malloc, which is popular
22522 among really fast exit relays on Linux.
22524 o Major bugfixes, new in 0.2.2.21-alpha:
22525 - Prevent crash/heap corruption when the cbtnummodes consensus
22526 parameter is set to 0 or large values. Fixes bug 2317; bugfix
22529 o Major features, new in 0.2.2.21-alpha:
22530 - Introduce minimum/maximum values that clients will believe
22531 from the consensus. Now we'll have a better chance to avoid crashes
22532 or worse when a consensus param has a weird value.
22534 o Minor features, new in 0.2.2.21-alpha:
22535 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22536 used on bridges, and it makes bridge scanning somewhat easier.
22537 - If writing the state file to disk fails, wait up to an hour before
22538 retrying again, rather than trying again each second. Fixes bug
22539 2346; bugfix on Tor 0.1.1.3-alpha.
22540 - Make Libevent log messages get delivered to controllers later,
22541 and not from inside the Libevent log handler. This prevents unsafe
22542 reentrant Libevent calls while still letting the log messages
22544 - Detect platforms that brokenly use a signed size_t, and refuse to
22545 build there. Found and analyzed by doorss and rransom.
22546 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22549 o Minor bugfixes, new in 0.2.2.21-alpha:
22550 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22551 than waiting forever for them to finish. Fixes bug 2330; bugfix
22552 on 0.2.0.16-alpha. Found by doorss.
22553 - Add assertions to check for overflow in arguments to
22554 base32_encode() and base32_decode(); fix a signed-unsigned
22555 comparison there too. These bugs are not actually reachable in Tor,
22556 but it's good to prevent future errors too. Found by doorss.
22557 - Correctly detect failures to create DNS requests when using Libevent
22558 versions before v2. (Before Libevent 2, we used our own evdns
22559 implementation. Its return values for Libevent's evdns_resolve_*()
22560 functions are not consistent with those from Libevent.) Fixes bug
22561 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22563 o Documentation, new in 0.2.2.21-alpha:
22564 - Document the default socks host and port (127.0.0.1:9050) for
22568 Changes in version 0.2.1.29 - 2011-01-15
22569 Tor 0.2.1.29 continues our recent code security audit work. The main
22570 fix resolves a remote heap overflow vulnerability that can allow remote
22571 code execution. Other fixes address a variety of assert and crash bugs,
22572 most of which we think are hard to exploit remotely.
22574 o Major bugfixes (security):
22575 - Fix a heap overflow bug where an adversary could cause heap
22576 corruption. This bug probably allows remote code execution
22577 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22579 - Prevent a denial-of-service attack by disallowing any
22580 zlib-compressed data whose compression factor is implausibly
22581 high. Fixes part of bug 2324; reported by "doorss".
22582 - Zero out a few more keys in memory before freeing them. Fixes
22583 bug 2384 and part of bug 2385. These key instances found by
22584 "cypherpunks", based on Andrew Case's report about being able
22585 to find sensitive data in Tor's memory space if you have enough
22586 permissions. Bugfix on 0.0.2pre9.
22588 o Major bugfixes (crashes):
22589 - Prevent calls to Libevent from inside Libevent log handlers.
22590 This had potential to cause a nasty set of crashes, especially
22591 if running Libevent with debug logging enabled, and running
22592 Tor with a controller watching for low-severity log messages.
22593 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22594 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22595 underflow errors there too. Fixes the other part of bug 2324.
22596 - Fix a bug where we would assert if we ever had a
22597 cached-descriptors.new file (or another file read directly into
22598 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22599 on 0.2.1.25. Found by doorss.
22600 - Fix some potential asserts and parsing issues with grossly
22601 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22604 o Minor bugfixes (other):
22605 - Fix a bug with handling misformed replies to reverse DNS lookup
22606 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22607 bug reported by doorss.
22608 - Fix compilation on mingw when a pthreads compatibility library
22609 has been installed. (We don't want to use it, so we shouldn't
22610 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22611 - Fix a bug where we would declare that we had run out of virtual
22612 addresses when the address space was only half-exhausted. Bugfix
22614 - Correctly handle the case where AutomapHostsOnResolve is set but
22615 no virtual addresses are available. Fixes bug 2328; bugfix on
22616 0.1.2.1-alpha. Bug found by doorss.
22617 - Correctly handle wrapping around to when we run out of virtual
22618 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22619 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22620 because we built it with a too-old version of automake. Thus that
22621 release broke ./configure --enable-openbsd-malloc, which is popular
22622 among really fast exit relays on Linux.
22625 - Update to the January 1 2011 Maxmind GeoLite Country database.
22626 - Introduce output size checks on all of our decryption functions.
22629 - Tor does not build packages correctly with Automake 1.6 and earlier;
22630 added a check to Makefile.am to make sure that we're building with
22631 Automake 1.7 or later.
22634 Changes in version 0.2.2.20-alpha - 2010-12-17
22635 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22636 exploitable bugs. We also fix a variety of other significant bugs,
22637 change the IP address for one of our directory authorities, and update
22638 the minimum version that Tor relays must run to join the network.
22641 - Fix a remotely exploitable bug that could be used to crash instances
22642 of Tor remotely by overflowing on the heap. Remote-code execution
22643 hasn't been confirmed, but can't be ruled out. Everyone should
22644 upgrade. Bugfix on the 0.1.1 series and later.
22645 - Fix a bug that could break accounting on 64-bit systems with large
22646 time_t values, making them hibernate for impossibly long intervals.
22647 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22648 - Fix a logic error in directory_fetches_from_authorities() that
22649 would cause all _non_-exits refusing single-hop-like circuits
22650 to fetch from authorities, when we wanted to have _exits_ fetch
22651 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22653 - Fix a stream fairness bug that would cause newer streams on a given
22654 circuit to get preference when reading bytes from the origin or
22655 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22656 introduced before the first Tor release, in svn revision r152.
22658 o Directory authority changes:
22659 - Change IP address and ports for gabelmoo (v3 directory authority).
22662 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22663 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22664 - Fix an off-by-one error in calculating some controller command
22665 argument lengths. Fortunately, this mistake is harmless since
22666 the controller code does redundant NUL termination too. Found by
22667 boboper. Bugfix on 0.1.1.1-alpha.
22668 - Do not dereference NULL if a bridge fails to build its
22669 extra-info descriptor. Found by an anonymous commenter on
22670 Trac. Bugfix on 0.2.2.19-alpha.
22673 - Update to the December 1 2010 Maxmind GeoLite Country database.
22674 - Directory authorities now reject relays running any versions of
22675 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22676 known bugs that keep RELAY_EARLY cells from working on rendezvous
22677 circuits. Followup to fix for bug 2081.
22678 - Directory authorities now reject relays running any version of Tor
22679 older than 0.2.0.26-rc. That version is the earliest that fetches
22680 current directory information correctly. Fixes bug 2156.
22681 - Report only the top 10 ports in exit-port stats in order not to
22682 exceed the maximum extra-info descriptor length of 50 KB. Implements
22686 Changes in version 0.2.1.28 - 2010-12-17
22687 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22688 exploitable bugs. We also took this opportunity to change the IP address
22689 for one of our directory authorities, and to update the geoip database
22693 - Fix a remotely exploitable bug that could be used to crash instances
22694 of Tor remotely by overflowing on the heap. Remote-code execution
22695 hasn't been confirmed, but can't be ruled out. Everyone should
22696 upgrade. Bugfix on the 0.1.1 series and later.
22698 o Directory authority changes:
22699 - Change IP address and ports for gabelmoo (v3 directory authority).
22702 - Update to the December 1 2010 Maxmind GeoLite Country database.
22705 Changes in version 0.2.1.27 - 2010-11-23
22706 Yet another OpenSSL security patch broke its compatibility with Tor:
22707 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22708 also took this opportunity to fix several crash bugs, integrate a new
22709 directory authority, and update the bundled GeoIP database.
22712 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22713 No longer set the tlsext_host_name extension on server SSL objects;
22714 but continue to set it on client SSL objects. Our goal in setting
22715 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22716 bugfix on 0.2.1.1-alpha.
22717 - Do not log messages to the controller while shrinking buffer
22718 freelists. Doing so would sometimes make the controller connection
22719 try to allocate a buffer chunk, which would mess up the internals
22720 of the freelist and cause an assertion failure. Fixes bug 1125;
22721 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22722 - Learn our external IP address when we're a relay or bridge, even if
22723 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22724 where we introduced bridge relays that don't need to publish to
22725 be useful. Fixes bug 2050.
22726 - Do even more to reject (and not just ignore) annotations on
22727 router descriptors received anywhere but from the cache. Previously
22728 we would ignore such annotations at first, but cache them to disk
22729 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22730 - When you're using bridges and your network goes away and your
22731 bridges get marked as down, recover when you attempt a new socks
22732 connection (if the network is back), rather than waiting up to an
22733 hour to try fetching new descriptors for your bridges. Bugfix on
22734 0.2.0.3-alpha; fixes bug 1981.
22737 - Move to the November 2010 Maxmind GeoLite country db (rather
22738 than the June 2009 ip-to-country GeoIP db) for our statistics that
22739 count how many users relays are seeing from each country. Now we'll
22740 have more accurate data, especially for many African countries.
22742 o New directory authorities:
22743 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22747 - Fix an assertion failure that could occur in directory caches or
22748 bridge users when using a very short voting interval on a testing
22749 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22751 - Enforce multiplicity rules when parsing annotations. Bugfix on
22752 0.2.0.8-alpha. Found by piebeer.
22753 - Allow handshaking OR connections to take a full KeepalivePeriod
22754 seconds to handshake. Previously, we would close them after
22755 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22756 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22758 - When building with --enable-gcc-warnings on OpenBSD, disable
22759 warnings in system headers. This makes --enable-gcc-warnings
22760 pass on OpenBSD 4.8.
22763 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22764 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22765 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22766 Servers can start sending this code when enough clients recognize
22767 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22768 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22769 Patch from mingw-san.
22772 - Remove the old debian/ directory from the main Tor distribution.
22773 The official Tor-for-debian git repository lives at the URL
22774 https://git.torproject.org/debian/tor.git
22775 - Stop shipping the old doc/website/ directory in the tarball. We
22776 changed the website format in late 2010, and what we shipped in
22777 0.2.1.26 really wasn't that useful anyway.
22780 Changes in version 0.2.2.19-alpha - 2010-11-22
22781 Yet another OpenSSL security patch broke its compatibility with Tor:
22782 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
22785 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22786 No longer set the tlsext_host_name extension on server SSL objects;
22787 but continue to set it on client SSL objects. Our goal in setting
22788 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22789 bugfix on 0.2.1.1-alpha.
22792 - Try harder not to exceed the maximum length of 50 KB when writing
22793 statistics to extra-info descriptors. This bug was triggered by very
22794 fast relays reporting exit-port, entry, and dirreq statistics.
22795 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
22796 - Publish a router descriptor even if generating an extra-info
22797 descriptor fails. Previously we would not publish a router
22798 descriptor without an extra-info descriptor; this can cause fast
22799 exit relays collecting exit-port statistics to drop from the
22800 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22803 Changes in version 0.2.2.18-alpha - 2010-11-16
22804 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
22805 us lately, makes unpublished bridge relays able to detect their IP
22806 address, and fixes a wide variety of other bugs to get us much closer
22807 to a stable release.
22810 - Do even more to reject (and not just ignore) annotations on
22811 router descriptors received anywhere but from the cache. Previously
22812 we would ignore such annotations at first, but cache them to disk
22813 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22814 - Do not log messages to the controller while shrinking buffer
22815 freelists. Doing so would sometimes make the controller connection
22816 try to allocate a buffer chunk, which would mess up the internals
22817 of the freelist and cause an assertion failure. Fixes bug 1125;
22818 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22819 - Learn our external IP address when we're a relay or bridge, even if
22820 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22821 where we introduced bridge relays that don't need to publish to
22822 be useful. Fixes bug 2050.
22823 - Maintain separate TLS contexts and certificates for incoming and
22824 outgoing connections in bridge relays. Previously we would use the
22825 same TLS contexts and certs for incoming and outgoing connections.
22826 Bugfix on 0.2.0.3-alpha; addresses bug 988.
22827 - Maintain separate identity keys for incoming and outgoing TLS
22828 contexts in bridge relays. Previously we would use the same
22829 identity keys for incoming and outgoing TLS contexts. Bugfix on
22830 0.2.0.3-alpha; addresses the other half of bug 988.
22831 - Avoid an assertion failure when we as an authority receive a
22832 duplicate upload of a router descriptor that we already have,
22833 but which we previously considered an obsolete descriptor.
22834 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
22835 - Avoid a crash bug triggered by looking at a dangling pointer while
22836 setting the network status consensus. Found by Robert Ransom.
22837 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
22838 - Fix a logic error where servers that _didn't_ act as exits would
22839 try to keep their server lists more aggressively up to date than
22840 exits, when it was supposed to be the other way around. Bugfix
22843 o Minor bugfixes (on Tor 0.2.1.x and earlier):
22844 - When we're trying to guess whether we know our IP address as
22845 a relay, we would log various ways that we failed to guess
22846 our address, but never log that we ended up guessing it
22847 successfully. Now add a log line to help confused and anxious
22848 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
22849 - Bring the logic that gathers routerinfos and assesses the
22850 acceptability of circuits into line. This prevents a Tor OP from
22851 getting locked in a cycle of choosing its local OR as an exit for a
22852 path (due to a .exit request) and then rejecting the circuit because
22853 its OR is not listed yet. It also prevents Tor clients from using an
22854 OR running in the same instance as an exit (due to a .exit request)
22855 if the OR does not meet the same requirements expected of an OR
22856 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22857 - Correctly describe errors that occur when generating a TLS object.
22858 Previously we would attribute them to a failure while generating a
22859 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22861 - Enforce multiplicity rules when parsing annotations. Bugfix on
22862 0.2.0.8-alpha. Found by piebeer.
22863 - Fix warnings that newer versions of autoconf produced during
22864 ./autogen.sh. These warnings appear to be harmless in our case,
22865 but they were extremely verbose. Fixes bug 2020.
22867 o Minor bugfixes (on Tor 0.2.2.x):
22868 - Enable protection of small arrays whenever we build with gcc
22869 hardening features, not only when also building with warnings
22870 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
22873 - Make hidden services work better in private Tor networks by not
22874 requiring any uptime to join the hidden service descriptor
22875 DHT. Implements ticket 2088.
22876 - Rate-limit the "your application is giving Tor only an IP address"
22877 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
22878 - When AllowSingleHopExits is set, print a warning to explain to the
22879 relay operator why most clients are avoiding her relay.
22880 - Update to the November 1 2010 Maxmind GeoLite Country database.
22882 o Code simplifications and refactoring:
22883 - When we fixed bug 1038 we had to put in a restriction not to send
22884 RELAY_EARLY cells on rend circuits. This was necessary as long
22885 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22886 active. Now remove this obsolete check. Resolves bug 2081.
22887 - Some options used different conventions for uppercasing of acronyms
22888 when comparing manpage and source. Fix those in favor of the
22889 manpage, as it makes sense to capitalize acronyms.
22890 - Remove the torrc.complete file. It hasn't been kept up to date
22891 and users will have better luck checking out the manpage.
22892 - Remove the obsolete "NoPublish" option; it has been flagged
22893 as obsolete and has produced a warning since 0.1.1.18-rc.
22894 - Remove everything related to building the expert bundle for OS X.
22895 It has confused many users, doesn't work right on OS X 10.6,
22896 and is hard to get rid of once installed. Resolves bug 1274.
22899 Changes in version 0.2.2.17-alpha - 2010-09-30
22900 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
22901 to use one-hop circuits (which can put the exit relays at higher risk,
22902 plus unbalance the network); fixes a big bug in bandwidth accounting
22903 for relays that want to limit their monthly bandwidth use; fixes a
22904 big pile of bugs in how clients tolerate temporary network failure;
22905 and makes our adaptive circuit build timeout feature (which improves
22906 client performance if your network is fast while not breaking things
22907 if your network is slow) better handle bad networks.
22910 - Exit relays now try harder to block exit attempts from unknown
22911 relays, to make it harder for people to use them as one-hop proxies
22912 a la tortunnel. Controlled by the refuseunknownexits consensus
22913 parameter (currently enabled), or you can override it on your
22914 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
22916 o Major bugfixes (0.2.1.x and earlier):
22917 - Fix a bug in bandwidth accounting that could make us use twice
22918 the intended bandwidth when our interval start changes due to
22919 daylight saving time. Now we tolerate skew in stored vs computed
22920 interval starts: if the start of the period changes by no more than
22921 50% of the period's duration, we remember bytes that we transferred
22922 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22923 - Always search the Windows system directory for system DLLs, and
22924 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22925 - When you're using bridges and your network goes away and your
22926 bridges get marked as down, recover when you attempt a new socks
22927 connection (if the network is back), rather than waiting up to an
22928 hour to try fetching new descriptors for your bridges. Bugfix on
22929 0.2.0.3-alpha; fixes bug 1981.
22931 o Major bugfixes (on 0.2.2.x):
22932 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
22934 - Fix a segfault that could happen when operating a bridge relay with
22935 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
22936 - The consensus bandwidth-weights (used by clients to choose fast
22937 relays) entered an unexpected edge case in September where
22938 Exits were much scarcer than Guards, resulting in bad weight
22939 recommendations. Now we compute them using new constraints that
22940 should succeed in all cases. Also alter directory authorities to
22941 not include the bandwidth-weights line if they fail to produce
22942 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
22943 - When weighting bridges during path selection, we used to trust
22944 the bandwidths they provided in their descriptor, only capping them
22945 at 10MB/s. This turned out to be problematic for two reasons:
22946 Bridges could claim to handle a lot more traffic then they
22947 actually would, thus making more clients pick them and have a
22948 pretty effective DoS attack. The other issue is that new bridges
22949 that might not have a good estimate for their bw capacity yet
22950 would not get used at all unless no other bridges are available
22951 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
22953 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
22954 - Ignore cannibalized circuits when recording circuit build times.
22955 This should provide for a minor performance improvement for hidden
22956 service users using 0.2.2.14-alpha, and should remove two spurious
22957 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
22958 - Simplify the logic that causes us to decide if the network is
22959 unavailable for purposes of recording circuit build times. If we
22960 receive no cells whatsoever for the entire duration of a circuit's
22961 full measured lifetime, the network is probably down. Also ignore
22962 one-hop directory fetching circuit timeouts when calculating our
22963 circuit build times. These changes should hopefully reduce the
22964 cases where we see ridiculous circuit build timeouts for people
22965 with spotty wireless connections. Fixes part of bug 1772; bugfix
22967 - Prevent the circuit build timeout from becoming larger than
22968 the maximum build time we have ever seen. Also, prevent the time
22969 period for measurement circuits from becoming larger than twice that
22970 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
22973 - When we run out of directory information such that we can't build
22974 circuits, but then get enough that we can build circuits, log when
22975 we actually construct a circuit, so the user has a better chance of
22976 knowing what's going on. Fixes bug 1362.
22977 - Be more generous with how much bandwidth we'd use up (with
22978 accounting enabled) before entering "soft hibernation". Previously,
22979 we'd refuse new connections and circuits once we'd used up 95% of
22980 our allotment. Now, we use up 95% of our allotment, AND make sure
22981 that we have no more than 500MB (or 3 hours of expected traffic,
22982 whichever is lower) remaining before we enter soft hibernation.
22983 - If we've configured EntryNodes and our network goes away and/or all
22984 our entrynodes get marked down, optimistically retry them all when
22985 a new socks application request appears. Fixes bug 1882.
22986 - Add some more defensive programming for architectures that can't
22987 handle unaligned integer accesses. We don't know of any actual bugs
22988 right now, but that's the best time to fix them. Fixes bug 1943.
22989 - Support line continuations in the torrc config file. If a line
22990 ends with a single backslash character, the newline is ignored, and
22991 the configuration value is treated as continuing on the next line.
22994 o Minor bugfixes (on 0.2.1.x and earlier):
22995 - For bandwidth accounting, calculate our expected bandwidth rate
22996 based on the time during which we were active and not in
22997 soft-hibernation during the last interval. Previously, we were
22998 also considering the time spent in soft-hibernation. If this
22999 was a long time, we would wind up underestimating our bandwidth
23000 by a lot, and skewing our wakeup time towards the start of the
23001 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
23003 o Minor bugfixes (on 0.2.2.x):
23004 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
23005 which were disabled by the circuit build timeout changes in
23006 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
23007 - Make sure we don't warn about missing bandwidth weights when
23008 choosing bridges or other relays not in the consensus. Bugfix on
23009 0.2.2.10-alpha; fixes bug 1805.
23010 - In our logs, do not double-report signatures from unrecognized
23011 authorities both as "from unknown authority" and "not
23012 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
23015 Changes in version 0.2.2.16-alpha - 2010-09-17
23016 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
23017 evident at exit relays), and also continues to resolve all the little
23018 bugs that have been filling up trac lately.
23020 o Major bugfixes (stream-level fairness):
23021 - When receiving a circuit-level SENDME for a blocked circuit, try
23022 to package cells fairly from all the streams that had previously
23023 been blocked on that circuit. Previously, we had started with the
23024 oldest stream, and allowed each stream to potentially exhaust
23025 the circuit's package window. This gave older streams on any
23026 given circuit priority over newer ones. Fixes bug 1937. Detected
23027 originally by Camilo Viecco. This bug was introduced before the
23028 first Tor release, in svn commit r152: it is the new winner of
23029 the longest-lived bug prize.
23030 - When the exit relay got a circuit-level sendme cell, it started
23031 reading on the exit streams, even if had 500 cells queued in the
23032 circuit queue already, so the circuit queue just grew and grew in
23033 some cases. We fix this by not re-enabling reading on receipt of a
23034 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
23035 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
23037 - Newly created streams were allowed to read cells onto circuits,
23038 even if the circuit's cell queue was blocked and waiting to drain.
23039 This created potential unfairness, as older streams would be
23040 blocked, but newer streams would gladly fill the queue completely.
23041 We add code to detect this situation and prevent any stream from
23042 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
23046 - Update to the September 1 2010 Maxmind GeoLite Country database.
23047 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
23048 not. This would lead to a cookie that is still not group readable.
23049 Closes bug 1843. Suggested by katmagic.
23050 - When logging a rate-limited warning, we now mention how many messages
23051 got suppressed since the last warning.
23052 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
23053 do individual connection-level rate limiting of clients. The torrc
23054 config options with the same names trump the consensus params, if
23055 both are present. Replaces the old "bwconnrate" and "bwconnburst"
23056 consensus params which were broken from 0.2.2.7-alpha through
23057 0.2.2.14-alpha. Closes bug 1947.
23058 - When a router changes IP address or port, authorities now launch
23059 a new reachability test for it. Implements ticket 1899.
23060 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
23061 2 no signature, 4 required" messages about consensus signatures
23062 easier to read, and make sure they get logged at the same severity
23063 as the messages explaining which keys are which. Fixes bug 1290.
23064 - Don't warn when we have a consensus that we can't verify because
23065 of missing certificates, unless those certificates are ones
23066 that we have been trying and failing to download. Fixes bug 1145.
23067 - If you configure your bridge with a known identity fingerprint,
23068 and the bridge authority is unreachable (as it is in at least
23069 one country now), fall back to directly requesting the descriptor
23070 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
23072 - When building with --enable-gcc-warnings on OpenBSD, disable
23073 warnings in system headers. This makes --enable-gcc-warnings
23074 pass on OpenBSD 4.8.
23076 o Minor bugfixes (on 0.2.1.x and earlier):
23077 - Authorities will now attempt to download consensuses if their
23078 own efforts to make a live consensus have failed. This change
23079 means authorities that restart will fetch a valid consensus, and
23080 it means authorities that didn't agree with the current consensus
23081 will still fetch and serve it if it has enough signatures. Bugfix
23082 on 0.2.0.9-alpha; fixes bug 1300.
23083 - Ensure DNS requests launched by "RESOLVE" commands from the
23084 controller respect the __LeaveStreamsUnattached setconf options. The
23085 same goes for requests launched via DNSPort or transparent
23086 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
23087 - Allow handshaking OR connections to take a full KeepalivePeriod
23088 seconds to handshake. Previously, we would close them after
23089 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23090 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23092 - Rate-limit "Failed to hand off onionskin" warnings.
23093 - Never relay a cell for a circuit we have already destroyed.
23094 Between marking a circuit as closeable and finally closing it,
23095 it may have been possible for a few queued cells to get relayed,
23096 even though they would have been immediately dropped by the next
23097 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
23098 - Never queue a cell for a circuit that's already been marked
23100 - Never vote for a server as "Running" if we have a descriptor for
23101 it claiming to be hibernating, and that descriptor was published
23102 more recently than our last contact with the server. Bugfix on
23103 0.2.0.3-alpha; fixes bug 911.
23104 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
23107 o Minor bugfixes (on 0.2.2.x):
23108 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
23109 down if a directory fetch fails and you've configured either
23110 bridges or EntryNodes. The intent was to mark the relay as down
23111 _unless_ you're using bridges or EntryNodes, since if you are
23112 then you could quickly run out of entry points.
23113 - Fix the Windows directory-listing code. A bug introduced in
23114 0.2.2.14-alpha could make Windows directory servers forget to load
23115 some of their cached v2 networkstatus files.
23116 - Really allow clients to use relays as bridges. Fixes bug 1776;
23117 bugfix on 0.2.2.15-alpha.
23118 - Demote a warn to info that happens when the CellStatistics option
23119 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
23120 Reported by Moritz Bartl.
23121 - On Windows, build correctly either with or without Unicode support.
23122 This is necessary so that Tor can support fringe platforms like
23123 Windows 98 (which has no Unicode), or Windows CE (which has no
23124 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
23127 - Add a unit test for cross-platform directory-listing code.
23130 Changes in version 0.2.2.15-alpha - 2010-08-18
23131 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
23132 fixes a variety of other bugs that were preventing performance
23133 experiments from moving forward, fixes several bothersome memory leaks,
23134 and generally closes a lot of smaller bugs that have been filling up
23138 - Stop assigning the HSDir flag to relays that disable their
23139 DirPort (and thus will refuse to answer directory requests). This
23140 fix should dramatically improve the reachability of hidden services:
23141 hidden services and hidden service clients pick six HSDir relays
23142 to store and retrieve the hidden service descriptor, and currently
23143 about half of the HSDir relays will refuse to work. Bugfix on
23144 0.2.0.10-alpha; fixes part of bug 1693.
23145 - The PerConnBWRate and Burst config options, along with the
23146 bwconnrate and bwconnburst consensus params, initialized each conn's
23147 token bucket values only when the connection is established. Now we
23148 update them if the config options change, and update them every time
23149 we get a new consensus. Otherwise we can encounter an ugly edge
23150 case where we initialize an OR conn to client-level bandwidth,
23151 but then later the relay joins the consensus and we leave it
23152 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
23153 - Fix a regression that caused Tor to rebind its ports if it receives
23154 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
23157 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23158 should give us approximately 40-50% more Guard-flagged nodes,
23159 improving the anonymity the Tor network can provide and also
23160 decreasing the dropoff in throughput that relays experience when
23161 they first get the Guard flag.
23162 - Allow enabling or disabling the *Statistics config options while
23166 - Update to the August 1 2010 Maxmind GeoLite Country database.
23167 - Have the controller interface give a more useful message than
23168 "Internal Error" in response to failed GETINFO requests.
23169 - Warn when the same option is provided more than once in a torrc
23170 file, on the command line, or in a single SETCONF statement, and
23171 the option is one that only accepts a single line. Closes bug 1384.
23172 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23173 Patch from mingw-san.
23174 - Add support for the country code "{??}" in torrc options like
23175 ExcludeNodes, to indicate all routers of unknown country. Closes
23177 - Relays report the number of bytes spent on answering directory
23178 requests in extra-info descriptors similar to {read,write}-history.
23179 Implements enhancement 1790.
23181 o Minor bugfixes (on 0.2.1.x and earlier):
23182 - Complain if PublishServerDescriptor is given multiple arguments that
23183 include 0 or 1. This configuration will be rejected in the future.
23184 Bugfix on 0.2.0.1-alpha; closes bug 1107.
23185 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
23186 Bugfix on 0.2.0.13-alpha; closes bug 928.
23187 - Change "Application request when we're believed to be offline."
23188 notice to "Application request when we haven't used client
23189 functionality lately.", to clarify that it's not an error. Bugfix
23190 on 0.0.9.3; fixes bug 1222.
23191 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
23192 would return "551 Internal error" rather than "552 Unrecognized key
23193 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
23194 - Users can't configure a regular relay to be their bridge. It didn't
23195 work because when Tor fetched the bridge descriptor, it found
23196 that it already had it, and didn't realize that the purpose of the
23197 descriptor had changed. Now we replace routers with a purpose other
23198 than bridge with bridge descriptors when fetching them. Bugfix on
23199 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
23200 refetch the descriptor with router purpose 'general', disabling
23202 - Fix a rare bug in rend_fn unit tests: we would fail a test when
23203 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
23204 on 0.2.0.10-alpha; fixes bug 1808.
23205 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23206 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23207 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23208 Servers can start sending this code when enough clients recognize
23209 it. Also update the spec to reflect this new reason. Bugfix on
23210 0.1.0.1-rc; fixes part of bug 1793.
23211 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
23212 when we switch from being a public relay to a bridge. Otherwise
23213 there will still be clients that see the relay in their consensus,
23214 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
23216 - Instead of giving an assertion failure on an internal mismatch
23217 on estimated freelist size, just log a BUG warning and try later.
23218 Mitigates but does not fix bug 1125.
23219 - Fix an assertion failure that could occur in caches or bridge users
23220 when using a very short voting interval on a testing network.
23221 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
23223 o Minor bugfixes (on 0.2.2.x):
23224 - Alter directory authorities to always consider Exit-flagged nodes
23225 as potential Guard nodes in their votes. The actual decision to
23226 use Exits as Guards is done in the consensus bandwidth weights.
23227 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
23228 - When the controller is reporting the purpose of circuits that
23229 didn't finish building before the circuit build timeout, it was
23230 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
23231 - Our libevent version parsing code couldn't handle versions like
23232 1.4.14b-stable and incorrectly warned the user about using an
23233 old and broken version of libevent. Treat 1.4.14b-stable like
23234 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
23236 - Don't use substitution references like $(VAR:MOD) when
23237 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
23238 '$(:x)' to 'x' rather than the empty string. This bites us in
23239 doc/ when configured with --disable-asciidoc. Bugfix on
23240 0.2.2.9-alpha; fixes bug 1773.
23241 - Remove a spurious hidden service server-side log notice about
23242 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
23244 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
23246 - Correctly report written bytes on linked connections. Found while
23247 implementing 1790. Bugfix on 0.2.2.4-alpha.
23248 - Fix three memory leaks: one in circuit_build_times_parse_state(),
23249 one in dirvote_add_signatures_to_pending_consensus(), and one every
23250 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
23251 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
23253 o Code simplifications and refactoring:
23254 - Take a first step towards making or.h smaller by splitting out
23255 function definitions for all source files in src/or/. Leave
23256 structures and defines in or.h for now.
23257 - Remove a bunch of unused function declarations as well as a block of
23258 #if 0'd code from the unit tests. Closes bug 1824.
23259 - New unit tests for exit-port history statistics; refactored exit
23260 statistics code to be more easily tested.
23261 - Remove the old debian/ directory from the main Tor distribution.
23262 The official Tor-for-debian git repository lives at the URL
23263 https://git.torproject.org/debian/tor.git
23266 Changes in version 0.2.2.14-alpha - 2010-07-12
23267 Tor 0.2.2.14-alpha greatly improves client-side handling of
23268 circuit build timeouts, which are used to estimate speed and improve
23269 performance. We also move to a much better GeoIP database, port Tor to
23270 Windows CE, introduce new compile flags that improve code security,
23271 add an eighth v3 directory authority, and address a lot of more
23275 - Tor directory authorities no longer crash when started with a
23276 cached-microdesc-consensus file in their data directory. Bugfix
23277 on 0.2.2.6-alpha; fixes bug 1532.
23278 - Treat an unset $HOME like an empty $HOME rather than triggering an
23279 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
23280 - Ignore negative and large circuit build timeout values that can
23281 happen during a suspend or hibernate. These values caused various
23282 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
23283 - Alter calculation of Pareto distribution parameter 'Xm' for
23284 Circuit Build Timeout learning to use the weighted average of the
23285 top N=3 modes (because we have three entry guards). Considering
23286 multiple modes should improve the timeout calculation in some cases,
23287 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
23289 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
23290 right censored distribution model. This approach improves over the
23291 synthetic timeout generation approach that was producing insanely
23292 high timeout values. Now we calculate build timeouts using truncated
23293 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
23294 - Do not close circuits that are under construction when they reach
23295 the circuit build timeout. Instead, leave them building (but do not
23296 use them) for up until the time corresponding to the 95th percentile
23297 on the Pareto CDF or 60 seconds, whichever is greater. This is done
23298 to provide better data for the new Pareto model. This percentile
23299 can be controlled by the consensus.
23302 - Move to the June 2010 Maxmind GeoLite country db (rather than the
23303 June 2009 ip-to-country GeoIP db) for our statistics that count
23304 how many users relays are seeing from each country. Now we have
23305 more accurate data for many African countries.
23306 - Port Tor to build and run correctly on Windows CE systems, using
23307 the wcecompat library. Contributed by Valerio Lupi.
23308 - New "--enable-gcc-hardening" ./configure flag (off by default)
23309 to turn on gcc compile time hardening options. It ensures
23310 that signed ints have defined behavior (-fwrapv), enables
23311 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
23312 with canaries (-fstack-protector-all), turns on ASLR protection if
23313 supported by the kernel (-fPIE, -pie), and adds additional security
23314 related warnings. Verified to work on Mac OS X and Debian Lenny.
23315 - New "--enable-linker-hardening" ./configure flag (off by default)
23316 to turn on ELF specific hardening features (relro, now). This does
23317 not work with Mac OS X or any other non-ELF binary format.
23319 o New directory authorities:
23320 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23324 - New config option "WarnUnsafeSocks 0" disables the warning that
23325 occurs whenever Tor receives a socks handshake using a version of
23326 the socks protocol that can only provide an IP address (rather
23327 than a hostname). Setups that do DNS locally over Tor are fine,
23328 and we shouldn't spam the logs in that case.
23329 - Convert the HACKING file to asciidoc, and add a few new sections
23330 to it, explaining how we use Git, how we make changelogs, and
23331 what should go in a patch.
23332 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
23333 event, to give information on the current rate of circuit timeouts
23334 over our stored history.
23335 - Add ability to disable circuit build time learning via consensus
23336 parameter and via a LearnCircuitBuildTimeout config option. Also
23337 automatically disable circuit build time calculation if we are
23338 either a AuthoritativeDirectory, or if we fail to write our state
23339 file. Fixes bug 1296.
23340 - More gracefully handle corrupt state files, removing asserts
23341 in favor of saving a backup and resetting state.
23342 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
23346 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23348 - When a2x fails, mention that the user could disable manpages instead
23349 of trying to fix their asciidoc installation.
23350 - Where available, use Libevent 2.0's periodic timers so that our
23351 once-per-second cleanup code gets called even more closely to
23352 once per second than it would otherwise. Fixes bug 943.
23353 - If you run a bridge that listens on multiple IP addresses, and
23354 some user configures a bridge address that uses a different IP
23355 address than your bridge writes in its router descriptor, and the
23356 user doesn't specify an identity key, their Tor would discard the
23357 descriptor because "it isn't one of our configured bridges", and
23358 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
23359 Bugfix on 0.2.0.3-alpha.
23360 - If OpenSSL fails to make a duplicate of a private or public key, log
23361 an error message and try to exit cleanly. May help with debugging
23362 if bug 1209 ever remanifests.
23363 - Save a couple bytes in memory allocation every time we escape
23364 certain characters in a string. Patch from Florian Zumbiehl.
23365 - Make it explicit that we don't cannibalize one-hop circuits. This
23366 happens in the wild, but doesn't turn out to be a problem because
23367 we fortunately don't use those circuits. Many thanks to outofwords
23368 for the initial analysis and to swissknife who confirmed that
23369 two-hop circuits are actually created.
23370 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
23371 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
23372 - Eliminate a case where a circuit build time warning was displayed
23373 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
23376 Changes in version 0.2.1.26 - 2010-05-02
23377 Tor 0.2.1.26 addresses the recent connection and memory overload
23378 problems we've been seeing on relays, especially relays with their
23379 DirPort open. If your relay has been crashing, or you turned it off
23380 because it used too many resources, give this release a try.
23382 This release also fixes yet another instance of broken OpenSSL libraries
23383 that was causing some relays to drop out of the consensus.
23386 - Teach relays to defend themselves from connection overload. Relays
23387 now close idle circuits early if it looks like they were intended
23388 for directory fetches. Relays are also more aggressive about closing
23389 TLS connections that have no circuits on them. Such circuits are
23390 unlikely to be re-used, and tens of thousands of them were piling
23391 up at the fast relays, causing the relays to run out of sockets
23392 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23393 their directory fetches over TLS).
23394 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23395 that claim to be earlier than 0.9.8m, but which have in reality
23396 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23397 behavior. Possible fix for some cases of bug 1346.
23398 - Directory mirrors were fetching relay descriptors only from v2
23399 directory authorities, rather than v3 authorities like they should.
23400 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23401 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23404 - Finally get rid of the deprecated and now harmful notion of "clique
23405 mode", where directory authorities maintain TLS connections to
23409 - In the util/threads test, no longer free the test_mutex before all
23410 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23411 - The master thread could starve the worker threads quite badly on
23412 certain systems, causing them to run only partially in the allowed
23413 window. This resulted in test failures. Now the master thread sleeps
23414 occasionally for a few microseconds while the two worker-threads
23415 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23418 Changes in version 0.2.2.13-alpha - 2010-04-24
23419 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
23420 problems we've been seeing on relays, especially relays with their
23421 DirPort open. If your relay has been crashing, or you turned it off
23422 because it used too many resources, give this release a try.
23425 - Teach relays to defend themselves from connection overload. Relays
23426 now close idle circuits early if it looks like they were intended
23427 for directory fetches. Relays are also more aggressive about closing
23428 TLS connections that have no circuits on them. Such circuits are
23429 unlikely to be re-used, and tens of thousands of them were piling
23430 up at the fast relays, causing the relays to run out of sockets
23431 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23432 their directory fetches over TLS).
23435 - Finally get rid of the deprecated and now harmful notion of "clique
23436 mode", where directory authorities maintain TLS connections to
23438 - Directory authorities now do an immediate reachability check as soon
23439 as they hear about a new relay. This change should slightly reduce
23440 the time between setting up a relay and getting listed as running
23441 in the consensus. It should also improve the time between setting
23442 up a bridge and seeing use by bridge users.
23443 - Directory authorities no longer launch a TLS connection to every
23444 relay as they startup. Now that we have 2k+ descriptors cached,
23445 the resulting network hiccup is becoming a burden. Besides,
23446 authorities already avoid voting about Running for the first half
23447 hour of their uptime.
23450 Changes in version 0.2.2.12-alpha - 2010-04-20
23451 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
23452 handle and vote on descriptors. It was causing relays to drop out of
23456 - Many relays have been falling out of the consensus lately because
23457 not enough authorities know about their descriptor for them to get
23458 a majority of votes. When we deprecated the v2 directory protocol,
23459 we got rid of the only way that v3 authorities can hear from each
23460 other about other descriptors. Now authorities examine every v3
23461 vote for new descriptors, and fetch them from that authority. Bugfix
23463 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
23464 and a warning in or.h related to bandwidth_weight_rule_t that
23465 prevented clean compile on OS X. Fixes bug 1363; bugfix on
23467 - Fix a segfault on relays when DirReqStatistics is enabled
23468 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
23472 - Demote a confusing TLS warning that relay operators might get when
23473 someone tries to talk to their OrPort. It is neither the operator's
23474 fault nor can they do anything about it. Fixes bug 1364; bugfix
23478 Changes in version 0.2.2.11-alpha - 2010-04-15
23479 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
23480 libraries that was causing some relays to drop out of the consensus.
23483 - Directory mirrors were fetching relay descriptors only from v2
23484 directory authorities, rather than v3 authorities like they should.
23485 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23486 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23487 - Fix a parsing error that made every possible value of
23488 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
23489 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
23490 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
23491 about the option without breaking older ones.
23492 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23493 that claim to be earlier than 0.9.8m, but which have in reality
23494 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23495 behavior. Possible fix for some cases of bug 1346.
23498 - Experiment with a more aggressive approach to preventing clients
23499 from making one-hop exit streams. Exit relays who want to try it
23500 out can set "RefuseUnknownExits 1" in their torrc, and then look
23501 for "Attempt by %s to open a stream" log messages. Let us know
23503 - Add support for statically linking zlib by specifying
23504 --enable-static-zlib, to go with our support for statically linking
23505 openssl and libevent. Resolves bug 1358.
23508 - Fix a segfault that happens whenever a Tor client that is using
23509 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
23511 - When we cleaned up the contrib/tor-exit-notice.html file, we left
23512 out the first line. Fixes bug 1295.
23513 - When building the manpage from a tarball, we required asciidoc, but
23514 the asciidoc -> roff/html conversion was already done for the
23515 tarball. Make 'make' complain only when we need asciidoc (either
23516 because we're compiling directly from git, or because we altered
23517 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
23518 - When none of the directory authorities vote on any params, Tor
23519 segfaulted when trying to make the consensus from the votes. We
23520 didn't trigger the bug in practice, because authorities do include
23521 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
23524 - In the util/threads test, no longer free the test_mutex before all
23525 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23526 - The master thread could starve the worker threads quite badly on
23527 certain systems, causing them to run only partially in the allowed
23528 window. This resulted in test failures. Now the master thread sleeps
23529 occasionally for a few microseconds while the two worker-threads
23530 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23533 Changes in version 0.2.2.10-alpha - 2010-03-07
23534 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
23535 could prevent relays from guessing their IP address correctly. It also
23536 starts the groundwork for another client-side performance boost, since
23537 currently we're not making efficient use of relays that have both the
23538 Guard flag and the Exit flag.
23541 - Fix a regression from our patch for bug 1244 that caused relays
23542 to guess their IP address incorrectly if they didn't set Address
23543 in their torrc and/or their address fails to resolve. Bugfix on
23544 0.2.2.9-alpha; fixes bug 1269.
23546 o Major features (performance):
23547 - Directory authorities now compute consensus weightings that instruct
23548 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23549 and no flag. Clients that use these weightings will distribute
23550 network load more evenly across these different relay types. The
23551 weightings are in the consensus so we can change them globally in
23552 the future. Extra thanks to "outofwords" for finding some nasty
23553 security bugs in the first implementation of this feature.
23555 o Minor features (performance):
23556 - Always perform router selections using weighted relay bandwidth,
23557 even if we don't need a high capacity circuit at the time. Non-fast
23558 circuits now only differ from fast ones in that they can use relays
23559 not marked with the Fast flag. This "feature" could turn out to
23560 be a horrible bug; we should investigate more before it goes into
23564 - Allow disabling building of the manpages. Skipping the manpage
23565 speeds up the build considerably.
23567 o Minor bugfixes (on 0.2.2.x):
23568 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23569 Bugfix on 0.2.2.9-alpha.
23570 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23571 config option. Bugfix on 0.2.2.7-alpha.
23572 - Ship the asciidoc-helper file in the tarball, so that people can
23573 build from source if they want to, and touching the .1.txt files
23574 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23576 o Minor bugfixes (on 0.2.1.x or earlier):
23577 - Fix a dereference-then-NULL-check sequence when publishing
23578 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23580 - Fix another dereference-then-NULL-check sequence. Bugfix on
23581 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23582 - Make sure we treat potentially not NUL-terminated strings correctly.
23583 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23585 o Code simplifications and refactoring:
23586 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23587 compliant. Based on a patch from Christian Kujau.
23588 - Don't use sed in asciidoc-helper anymore.
23589 - Make the build process fail if asciidoc cannot be found and
23590 building with asciidoc isn't disabled.
23593 Changes in version 0.2.2.9-alpha - 2010-02-22
23594 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23595 location of a directory authority, and cleans up a bunch of small bugs.
23597 o Directory authority changes:
23598 - Change IP address for dannenberg (v3 directory authority), and
23599 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23600 service directory authority) from the list.
23603 - Make Tor work again on the latest OS X: when deciding whether to
23604 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23605 version at run-time, not compile time. We need to do this because
23606 Apple doesn't update its dev-tools headers when it updates its
23607 libraries in a security patch.
23608 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23609 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23610 a memory leak when requesting a hidden service descriptor we've
23611 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23613 - Authorities could be tricked into giving out the Exit flag to relays
23614 that didn't allow exiting to any ports. This bug could screw
23615 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23616 1238. Bug discovered by Martin Kowalczyk.
23617 - When freeing a session key, zero it out completely. We only zeroed
23618 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23619 patched by ekir. Fixes bug 1254.
23622 - Fix static compilation by listing the openssl libraries in the right
23623 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23624 - Resume handling .exit hostnames in a special way: originally we
23625 stripped the .exit part and used the requested exit relay. In
23626 0.2.2.1-alpha we stopped treating them in any special way, meaning
23627 if you use a .exit address then Tor will pass it on to the exit
23628 relay. Now we reject the .exit stream outright, since that behavior
23629 might be more expected by the user. Found and diagnosed by Scott
23630 Bennett and Downie on or-talk.
23631 - Don't spam the controller with events when we have no file
23632 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23633 for log messages was already solved from bug 748.)
23634 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23636 - Make the DNSPort option work with libevent 2.x. Don't alter the
23637 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23638 - Emit a GUARD DROPPED controller event for a case we missed.
23639 - Make more fields in the controller protocol case-insensitive, since
23640 control-spec.txt said they were.
23641 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23642 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23643 - Fix a spec conformance issue: the network-status-version token
23644 must be the first token in a v3 consensus or vote. Discovered by
23645 parakeep. Bugfix on 0.2.0.3-alpha.
23647 o Code simplifications and refactoring:
23648 - Generate our manpage and HTML documentation using Asciidoc. This
23649 change should make it easier to maintain the documentation, and
23650 produce nicer HTML.
23651 - Remove the --enable-iphone option. According to reports from Marco
23652 Bonetti, Tor builds fine without any special tweaking on recent
23653 iPhone SDK versions.
23654 - Removed some unnecessary files from the source distribution. The
23655 AUTHORS file has now been merged into the people page on the
23656 website. The roadmaps and design doc can now be found in the
23657 projects directory in svn.
23658 - Enabled various circuit build timeout constants to be controlled
23659 by consensus parameters. Also set better defaults for these
23660 parameters based on experimentation on broadband and simulated
23661 high latency links.
23664 - The 'EXTENDCIRCUIT' control port command can now be used with
23665 a circ id of 0 and no path. This feature will cause Tor to build
23666 a new 'fast' general purpose circuit using its own path selection
23668 - Added a BUILDTIMEOUT_SET controller event to describe changes
23669 to the circuit build timeout.
23670 - Future-proof the controller protocol a bit by ignoring keyword
23671 arguments we do not recognize.
23672 - Expand homedirs passed to tor-checkkey. This should silence a
23673 coverity complaint about passing a user-supplied string into
23674 open() without checking it.
23677 Changes in version 0.2.1.25 - 2010-03-16
23678 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23679 prevent relays from guessing their IP address correctly. It also fixes
23680 several minor potential security bugs.
23683 - Fix a regression from our patch for bug 1244 that caused relays
23684 to guess their IP address incorrectly if they didn't set Address
23685 in their torrc and/or their address fails to resolve. Bugfix on
23686 0.2.1.23; fixes bug 1269.
23687 - When freeing a session key, zero it out completely. We only zeroed
23688 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23689 patched by ekir. Fixes bug 1254.
23692 - Fix a dereference-then-NULL-check sequence when publishing
23693 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23695 - Fix another dereference-then-NULL-check sequence. Bugfix on
23696 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23697 - Make sure we treat potentially not NUL-terminated strings correctly.
23698 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23702 Changes in version 0.2.1.24 - 2010-02-21
23703 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23707 - Work correctly out-of-the-box with even more vendor-patched versions
23708 of OpenSSL. In particular, make it so Debian and OS X don't need
23709 customized patches to run/build.
23712 Changes in version 0.2.1.23 - 2010-02-13
23713 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23714 again on the latest OS X, and updates the location of a directory
23717 o Major bugfixes (performance):
23718 - We were selecting our guards uniformly at random, and then weighting
23719 which of our guards we'd use uniformly at random. This imbalance
23720 meant that Tor clients were severely limited on throughput (and
23721 probably latency too) by the first hop in their circuit. Now we
23722 select guards weighted by currently advertised bandwidth. We also
23723 automatically discard guards picked using the old algorithm. Fixes
23724 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23727 - Make Tor work again on the latest OS X: when deciding whether to
23728 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23729 version at run-time, not compile time. We need to do this because
23730 Apple doesn't update its dev-tools headers when it updates its
23731 libraries in a security patch.
23732 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23733 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23734 a memory leak when requesting a hidden service descriptor we've
23735 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23738 o Directory authority changes:
23739 - Change IP address for dannenberg (v3 directory authority), and
23740 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23741 service directory authority) from the list.
23744 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23745 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23748 - Avoid a mad rush at the beginning of each month when each client
23749 rotates half of its guards. Instead we spread the rotation out
23750 throughout the month, but we still avoid leaving a precise timestamp
23751 in the state file about when we first picked the guard. Improves
23752 over the behavior introduced in 0.1.2.17.
23755 Changes in version 0.2.2.8-alpha - 2010-01-26
23756 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
23757 causing bridge relays to disappear. If you're running a bridge,
23761 - Fix a memory corruption bug on bridges that occurred during the
23762 inclusion of stats data in extra-info descriptors. Also fix the
23763 interface for geoip_get_bridge_stats* to prevent similar bugs in
23764 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
23765 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
23768 - Ignore OutboundBindAddress when connecting to localhost.
23769 Connections to localhost need to come _from_ localhost, or else
23770 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
23774 Changes in version 0.2.2.7-alpha - 2010-01-19
23775 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
23776 as laying the groundwork for further relay-side performance fixes. It
23777 also starts cleaning up client behavior with respect to the EntryNodes,
23778 ExitNodes, and StrictNodes config options.
23780 This release also rotates two directory authority keys, due to a
23781 security breach of some of the Torproject servers.
23783 o Directory authority changes:
23784 - Rotate keys (both v3 identity and relay identity) for moria1
23787 o Major features (performance):
23788 - We were selecting our guards uniformly at random, and then weighting
23789 which of our guards we'd use uniformly at random. This imbalance
23790 meant that Tor clients were severely limited on throughput (and
23791 probably latency too) by the first hop in their circuit. Now we
23792 select guards weighted by currently advertised bandwidth. We also
23793 automatically discard guards picked using the old algorithm. Fixes
23794 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23795 - When choosing which cells to relay first, relays can now favor
23796 circuits that have been quiet recently, to provide lower latency
23797 for low-volume circuits. By default, relays enable or disable this
23798 feature based on a setting in the consensus. You can override
23799 this default by using the new "CircuitPriorityHalflife" config
23800 option. Design and code by Ian Goldberg, Can Tang, and Chris
23802 - Add separate per-conn write limiting to go with the per-conn read
23803 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
23804 but never per-conn write limits.
23805 - New consensus params "bwconnrate" and "bwconnburst" to let us
23806 rate-limit client connections as they enter the network. It's
23807 controlled in the consensus so we can turn it on and off for
23808 experiments. It's starting out off. Based on proposal 163.
23810 o Major features (relay selection options):
23811 - Switch to a StrictNodes config option, rather than the previous
23812 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
23813 "StrictExcludeNodes" option.
23814 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
23815 change during a config reload, mark and discard all our origin
23816 circuits. This fix should address edge cases where we change the
23817 config options and but then choose a circuit that we created before
23819 - If EntryNodes or ExitNodes are set, be more willing to use an
23820 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
23822 - Make EntryNodes config option much more aggressive even when
23823 StrictNodes is not set. Before it would prepend your requested
23824 entrynodes to your list of guard nodes, but feel free to use others
23825 after that. Now it chooses only from your EntryNodes if any of
23826 those are available, and only falls back to others if a) they're
23827 all down and b) StrictNodes is not set.
23828 - Now we refresh your entry guards from EntryNodes at each consensus
23829 fetch -- rather than just at startup and then they slowly rot as
23830 the network changes.
23833 - Stop bridge directory authorities from answering dbg-stability.txt
23834 directory queries, which would let people fetch a list of all
23835 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23838 - Log a notice when we get a new control connection. Now it's easier
23839 for security-conscious users to recognize when a local application
23840 is knocking on their controller door. Suggested by bug 1196.
23841 - New config option "CircuitStreamTimeout" to override our internal
23842 timeout schedule for how many seconds until we detach a stream from
23843 a circuit and try a new circuit. If your network is particularly
23844 slow, you might want to set this to a number like 60.
23845 - New controller command "getinfo config-text". It returns the
23846 contents that Tor would write if you send it a SAVECONF command,
23847 so the controller can write the file to disk itself.
23848 - New options for SafeLogging to allow scrubbing only log messages
23849 generated while acting as a relay.
23850 - Ship the bridges spec file in the tarball too.
23851 - Avoid a mad rush at the beginning of each month when each client
23852 rotates half of its guards. Instead we spread the rotation out
23853 throughout the month, but we still avoid leaving a precise timestamp
23854 in the state file about when we first picked the guard. Improves
23855 over the behavior introduced in 0.1.2.17.
23857 o Minor bugfixes (compiling):
23858 - Fix compilation on OS X 10.3, which has a stub mlockall() but
23859 hides it. Bugfix on 0.2.2.6-alpha.
23860 - Fix compilation on Solaris by removing support for the
23861 DisableAllSwap config option. Solaris doesn't have an rlimit for
23862 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
23865 o Minor bugfixes (crashes):
23866 - Do not segfault when writing buffer stats when we haven't observed
23867 a single circuit to report about. Found by Fabian Lanze. Bugfix on
23869 - If we're in the pathological case where there's no exit bandwidth
23870 but there is non-exit bandwidth, or no guard bandwidth but there
23871 is non-guard bandwidth, don't crash during path selection. Bugfix
23873 - Fix an impossible-to-actually-trigger buffer overflow in relay
23874 descriptor generation. Bugfix on 0.1.0.15.
23876 o Minor bugfixes (privacy):
23877 - Fix an instance where a Tor directory mirror might accidentally
23878 log the IP address of a misbehaving Tor client. Bugfix on
23880 - Don't list Windows capabilities in relay descriptors. We never made
23881 use of them, and maybe it's a bad idea to publish them. Bugfix
23884 o Minor bugfixes (other):
23885 - Resolve an edge case in path weighting that could make us misweight
23886 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
23887 - Fix statistics on client numbers by country as seen by bridges that
23888 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
23889 intervals instead of variable 12-to-48-hour intervals.
23890 - After we free an internal connection structure, overwrite it
23891 with a different memory value than we use for overwriting a freed
23892 internal circuit structure. Should help with debugging. Suggested
23894 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
23897 o Removed features:
23898 - Remove the HSAuthorityRecordStats option that version 0 hidden
23899 service authorities could have used to track statistics of overall
23900 hidden service usage.
23903 Changes in version 0.2.1.22 - 2010-01-19
23904 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
23905 authorities -- it would tell you its whole history of bridge descriptors
23906 if you make the right directory request. This stable update also
23907 rotates two of the seven v3 directory authority keys and locations.
23909 o Directory authority changes:
23910 - Rotate keys (both v3 identity and relay identity) for moria1
23914 - Stop bridge directory authorities from answering dbg-stability.txt
23915 directory queries, which would let people fetch a list of all
23916 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23919 Changes in version 0.2.1.21 - 2009-12-21
23920 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23921 library. If you use Tor on Linux / Unix and you're getting SSL
23922 renegotiation errors, upgrading should help. We also recommend an
23923 upgrade if you're an exit relay.
23926 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23927 handshake from working unless we explicitly tell OpenSSL that we
23928 are using SSL renegotiation safely. We are, of course, but OpenSSL
23929 0.9.8l won't work unless we say we are.
23930 - Avoid crashing if the client is trying to upload many bytes and the
23931 circuit gets torn down at the same time, or if the flip side
23932 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23935 - Do not refuse to learn about authority certs and v2 networkstatus
23936 documents that are older than the latest consensus. This bug might
23937 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23938 Spotted and fixed by xmux.
23939 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23940 trigger platform-specific option misparsing case found by Coverity
23942 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23943 trigger assert. Fixes bug 1173.
23946 Changes in version 0.2.2.6-alpha - 2009-11-19
23947 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
23948 support for the new lower-footprint "microdescriptor" directory design,
23949 future-proofing our consensus format against new hash functions or
23950 other changes, and an Android port. It also makes Tor compatible with
23951 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
23954 - Directory authorities can now create, vote on, and serve multiple
23955 parallel formats of directory data as part of their voting process.
23956 Partially implements Proposal 162: "Publish the consensus in
23958 - Directory authorities can now agree on and publish small summaries
23959 of router information that clients can use in place of regular
23960 server descriptors. This transition will eventually allow clients
23961 to use far less bandwidth for downloading information about the
23962 network. Begins the implementation of Proposal 158: "Clients
23963 download consensus + microdescriptors".
23964 - The directory voting system is now extensible to use multiple hash
23965 algorithms for signatures and resource selection. Newer formats
23966 are signed with SHA256, with a possibility for moving to a better
23967 hash algorithm in the future.
23968 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
23969 current and future memory pages via mlockall(). On supported
23970 platforms (modern Linux and probably BSD but not Windows or OS X),
23971 this should effectively disable any and all attempts to page out
23972 memory. This option requires that you start your Tor as root --
23973 if you use DisableAllSwap, please consider using the User option
23974 to properly reduce the privileges of your Tor.
23975 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
23976 to help Tor build correctly for Android phones.
23979 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23980 handshake from working unless we explicitly tell OpenSSL that we
23981 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
23982 won't work unless we say we are.
23985 - Fix a crash bug when trying to initialize the evdns module in
23986 Libevent 2. Bugfix on 0.2.1.16-rc.
23987 - Stop logging at severity 'warn' when some other Tor client tries
23988 to establish a circuit with us using weak DH keys. It's a protocol
23989 violation, but that doesn't mean ordinary users need to hear about
23990 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
23991 - Do not refuse to learn about authority certs and v2 networkstatus
23992 documents that are older than the latest consensus. This bug might
23993 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23994 Spotted and fixed by xmux.
23995 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
23996 - If all authorities restart at once right before a consensus vote,
23997 nobody will vote about "Running", and clients will get a consensus
23998 with no usable relays. Instead, authorities refuse to build a
23999 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
24000 - If your relay can't keep up with the number of incoming create
24001 cells, it would log one warning per failure into your logs. Limit
24002 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
24003 - Bridges now use "reject *:*" as their default exit policy. Bugfix
24004 on 0.2.0.3-alpha; fixes bug 1113.
24005 - Fix a memory leak on directory authorities during voting that was
24006 introduced in 0.2.2.1-alpha. Found via valgrind.
24009 Changes in version 0.2.1.20 - 2009-10-15
24010 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
24011 services at once, prepares for more performance improvements, and
24012 fixes a bunch of smaller bugs.
24014 The Windows and OS X bundles also include a more recent Vidalia,
24015 and switch from Privoxy to Polipo.
24017 The OS X installers are now drag and drop. It's best to un-install
24018 Tor/Vidalia and then install this new bundle, rather than upgrade. If
24019 you want to upgrade, you'll need to update the paths for Tor and Polipo
24020 in the Vidalia Settings window.
24023 - Send circuit or stream sendme cells when our window has decreased
24024 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24025 by Karsten when testing the "reduce circuit window" performance
24026 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24027 before the release of Tor 0.0.0. This is the new winner of the
24029 - Fix a remotely triggerable memory leak when a consensus document
24030 contains more than one signature from the same voter. Bugfix on
24032 - Avoid segfault in rare cases when finishing an introduction circuit
24033 as a client and finding out that we don't have an introduction key
24034 for it. Fixes bug 1073. Reported by Aaron Swartz.
24037 - Tor now reads the "circwindow" parameter out of the consensus,
24038 and uses that value for its circuit package window rather than the
24039 default of 1000 cells. Begins the implementation of proposal 168.
24041 o New directory authorities:
24042 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24044 - Move moria1 and tonga to alternate IP addresses.
24047 - Fix a signed/unsigned compile warning in 0.2.1.19.
24048 - Fix possible segmentation fault on directory authorities. Bugfix on
24050 - Fix an extremely rare infinite recursion bug that could occur if
24051 we tried to log a message after shutting down the log subsystem.
24052 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24053 - Fix an obscure bug where hidden services on 64-bit big-endian
24054 systems might mis-read the timestamp in v3 introduce cells, and
24055 refuse to connect back to the client. Discovered by "rotor".
24056 Bugfix on 0.2.1.6-alpha.
24057 - We were triggering a CLOCK_SKEW controller status event whenever
24058 we connect via the v2 connection protocol to any relay that has
24059 a wrong clock. Instead, we should only inform the controller when
24060 it's a trusted authority that claims our clock is wrong. Bugfix
24061 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24062 - We were telling the controller about CHECKING_REACHABILITY and
24063 REACHABILITY_FAILED status events whenever we launch a testing
24064 circuit or notice that one has failed. Instead, only tell the
24065 controller when we want to inform the user of overall success or
24066 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24068 - Don't warn when we're using a circuit that ends with a node
24069 excluded in ExcludeExitNodes, but the circuit is not used to access
24070 the outside world. This should help fix bug 1090. Bugfix on
24072 - Work around a small memory leak in some versions of OpenSSL that
24073 stopped the memory used by the hostname TLS extension from being
24077 - Add a "getinfo status/accepted-server-descriptor" controller
24078 command, which is the recommended way for controllers to learn
24079 whether our server descriptor has been successfully received by at
24080 least on directory authority. Un-recommend good-server-descriptor
24081 getinfo and status events until we have a better design for them.
24084 Changes in version 0.2.2.5-alpha - 2009-10-11
24085 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
24088 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
24090 o Directory authorities:
24091 - Temporarily (just for this release) move dizum to an alternate
24095 Changes in version 0.2.2.4-alpha - 2009-10-10
24096 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
24097 introduces a new unit test framework, shifts directry authority
24098 addresses around to reduce the impact from recent blocking events,
24099 and fixes a few smaller bugs.
24102 - Fix several more asserts in the circuit_build_times code, for
24103 example one that causes Tor to fail to start once we have
24104 accumulated 5000 build times in the state file. Bugfixes on
24105 0.2.2.2-alpha; fixes bug 1108.
24107 o New directory authorities:
24108 - Move moria1 and Tonga to alternate IP addresses.
24111 - Log SSL state transitions at debug level during handshake, and
24112 include SSL states in error messages. This may help debug future
24113 SSL handshake issues.
24114 - Add a new "Handshake" log domain for activities that happen
24115 during the TLS handshake.
24116 - Revert to the "June 3 2009" ip-to-country file. The September one
24117 seems to have removed most US IP addresses.
24118 - Directory authorities now reject Tor relays with versions less than
24119 0.1.2.14. This step cuts out four relays from the current network,
24120 none of which are very big.
24123 - Fix a couple of smaller issues with gathering statistics. Bugfixes
24125 - Fix two memory leaks in the error case of
24126 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
24127 - Don't count one-hop circuits when we're estimating how long it
24128 takes circuits to build on average. Otherwise we'll set our circuit
24129 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
24130 - Directory authorities no longer change their opinion of, or vote on,
24131 whether a router is Running, unless they have themselves been
24132 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
24135 o Code simplifications and refactoring:
24136 - Revise our unit tests to use the "tinytest" framework, so we
24137 can run tests in their own processes, have smarter setup/teardown
24138 code, and so on. The unit test code has moved to its own
24139 subdirectory, and has been split into multiple modules.
24142 Changes in version 0.2.2.3-alpha - 2009-09-23
24143 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
24146 - Fix an overzealous assert in our new circuit build timeout code.
24147 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
24150 - If the networkstatus consensus tells us that we should use a
24151 negative circuit package window, ignore it. Otherwise we'll
24152 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
24155 Changes in version 0.2.2.2-alpha - 2009-09-21
24156 Tor 0.2.2.2-alpha introduces our latest performance improvement for
24157 clients: Tor tracks the average time it takes to build a circuit, and
24158 avoids using circuits that take too long to build. For fast connections,
24159 this feature can cut your expected latency in half. For slow or flaky
24160 connections, it could ruin your Tor experience. Let us know if it does!
24163 - Tor now tracks how long it takes to build client-side circuits
24164 over time, and adapts its timeout to local network performance.
24165 Since a circuit that takes a long time to build will also provide
24166 bad performance, we get significant latency improvements by
24167 discarding the slowest 20% of circuits. Specifically, Tor creates
24168 circuits more aggressively than usual until it has enough data
24169 points for a good timeout estimate. Implements proposal 151.
24170 We are especially looking for reports (good and bad) from users with
24171 both EDGE and broadband connections that can move from broadband
24172 to EDGE and find out if the build-time data in the .tor/state gets
24173 reset without loss of Tor usability. You should also see a notice
24174 log message telling you that Tor has reset its timeout.
24175 - Directory authorities can now vote on arbitrary integer values as
24176 part of the consensus process. This is designed to help set
24177 network-wide parameters. Implements proposal 167.
24178 - Tor now reads the "circwindow" parameter out of the consensus,
24179 and uses that value for its circuit package window rather than the
24180 default of 1000 cells. Begins the implementation of proposal 168.
24183 - Fix a remotely triggerable memory leak when a consensus document
24184 contains more than one signature from the same voter. Bugfix on
24188 - Fix an extremely rare infinite recursion bug that could occur if
24189 we tried to log a message after shutting down the log subsystem.
24190 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24191 - Fix parsing for memory or time units given without a space between
24192 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
24193 - A networkstatus vote must contain exactly one signature. Spec
24194 conformance issue. Bugfix on 0.2.0.3-alpha.
24195 - Fix an obscure bug where hidden services on 64-bit big-endian
24196 systems might mis-read the timestamp in v3 introduce cells, and
24197 refuse to connect back to the client. Discovered by "rotor".
24198 Bugfix on 0.2.1.6-alpha.
24199 - We were triggering a CLOCK_SKEW controller status event whenever
24200 we connect via the v2 connection protocol to any relay that has
24201 a wrong clock. Instead, we should only inform the controller when
24202 it's a trusted authority that claims our clock is wrong. Bugfix
24203 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24204 - We were telling the controller about CHECKING_REACHABILITY and
24205 REACHABILITY_FAILED status events whenever we launch a testing
24206 circuit or notice that one has failed. Instead, only tell the
24207 controller when we want to inform the user of overall success or
24208 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24210 - Don't warn when we're using a circuit that ends with a node
24211 excluded in ExcludeExitNodes, but the circuit is not used to access
24212 the outside world. This should help fix bug 1090, but more problems
24213 remain. Bugfix on 0.2.1.6-alpha.
24214 - Work around a small memory leak in some versions of OpenSSL that
24215 stopped the memory used by the hostname TLS extension from being
24217 - Make our 'torify' script more portable; if we have only one of
24218 'torsocks' or 'tsocks' installed, don't complain to the user;
24219 and explain our warning about tsocks better.
24222 - Add a "getinfo status/accepted-server-descriptor" controller
24223 command, which is the recommended way for controllers to learn
24224 whether our server descriptor has been successfully received by at
24225 least on directory authority. Un-recommend good-server-descriptor
24226 getinfo and status events until we have a better design for them.
24227 - Update to the "September 4 2009" ip-to-country file.
24230 Changes in version 0.2.2.1-alpha - 2009-08-26
24231 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
24232 Tor clients to bootstrap on networks where only port 80 is reachable,
24233 makes it more straightforward to support hardware crypto accelerators,
24234 and starts the groundwork for gathering stats safely at relays.
24237 - Start the process of disabling ".exit" address notation, since it
24238 can be used for a variety of esoteric application-level attacks
24239 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
24242 o New directory authorities:
24243 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24247 - New AccelName and AccelDir options add support for dynamic OpenSSL
24248 hardware crypto acceleration engines.
24249 - Tor now supports tunneling all of its outgoing connections over
24250 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
24251 configuration options. Code by Christopher Davis.
24254 - Send circuit or stream sendme cells when our window has decreased
24255 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24256 by Karsten when testing the "reduce circuit window" performance
24257 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24258 before the release of Tor 0.0.0. This is the new winner of the
24261 o New options for gathering stats safely:
24262 - Directory mirrors that set "DirReqStatistics 1" write statistics
24263 about directory requests to disk every 24 hours. As compared to the
24264 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
24265 1) stats are written to disk exactly every 24 hours; 2) estimated
24266 shares of v2 and v3 requests are determined as mean values, not at
24267 the end of a measurement period; 3) unresolved requests are listed
24268 with country code '??'; 4) directories also measure download times.
24269 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
24270 number of exit streams and transferred bytes per port to disk every
24272 - Relays that set "CellStatistics 1" write statistics on how long
24273 cells spend in their circuit queues to disk every 24 hours.
24274 - Entry nodes that set "EntryStatistics 1" write statistics on the
24275 rough number and origins of connecting clients to disk every 24
24277 - Relays that write any of the above statistics to disk and set
24278 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
24279 their extra-info documents.
24282 - New --digests command-line switch to output the digests of the
24283 source files Tor was built with.
24284 - The "torify" script now uses torsocks where available.
24285 - The memarea code now uses a sentinel value at the end of each area
24286 to make sure nothing writes beyond the end of an area. This might
24287 help debug some conceivable causes of bug 930.
24288 - Time and memory units in the configuration file can now be set to
24289 fractional units. For example, "2.5 GB" is now a valid value for
24291 - Certain Tor clients (such as those behind check.torproject.org) may
24292 want to fetch the consensus in an extra early manner. To enable this
24293 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
24294 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
24295 as only certain clients who must have this information sooner should
24297 - Instead of adding the svn revision to the Tor version string, report
24298 the git commit (when we're building from a git checkout).
24301 - If any of the v3 certs we download are unparseable, we should
24302 actually notice the failure so we don't retry indefinitely. Bugfix
24303 on 0.2.0.x; reported by "rotator".
24304 - If the cached cert file is unparseable, warn but don't exit.
24305 - Fix possible segmentation fault on directory authorities. Bugfix on
24307 - When Tor fails to parse a descriptor of any kind, dump it to disk.
24308 Might help diagnosing bug 1051.
24310 o Deprecated and removed features:
24311 - The controller no longer accepts the old obsolete "addr-mappings/"
24312 or "unregistered-servers-" GETINFO values.
24313 - Hidden services no longer publish version 0 descriptors, and clients
24314 do not request or use version 0 descriptors. However, the old hidden
24315 service authorities still accept and serve version 0 descriptors
24316 when contacted by older hidden services/clients.
24317 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
24318 always on; using them is necessary for correct forward-compatible
24320 - Remove support for .noconnect style addresses. Nobody was using
24321 them, and they provided another avenue for detecting Tor users
24322 via application-level web tricks.
24324 o Packaging changes:
24325 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
24326 installer bundles. See
24327 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
24328 for details of what's new in Vidalia 0.2.3.
24329 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
24330 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
24331 configuration file, rather than the old Privoxy.
24332 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
24333 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
24334 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
24335 better compatibility with OS X 10.6, aka Snow Leopard.
24336 - OS X Vidalia Bundle: The multi-package installer is now replaced
24337 by a simple drag and drop to the /Applications folder. This change
24338 occurred with the upgrade to Vidalia 0.2.3.
24341 Changes in version 0.2.1.19 - 2009-07-28
24342 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
24343 services on Tor 0.2.1.3-alpha through 0.2.1.18.
24346 - Make accessing hidden services on 0.2.1.x work right again.
24347 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
24348 part of patch provided by "optimist".
24351 - When a relay/bridge is writing out its identity key fingerprint to
24352 the "fingerprint" file and to its logs, write it without spaces. Now
24353 it will look like the fingerprints in our bridges documentation,
24354 and confuse fewer users.
24357 - Relays no longer publish a new server descriptor if they change
24358 their MaxAdvertisedBandwidth config option but it doesn't end up
24359 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
24360 fixes bug 1026. Patch from Sebastian.
24361 - Avoid leaking memory every time we get a create cell but we have
24362 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
24363 fixes bug 1034. Reported by BarkerJr.
24366 Changes in version 0.2.1.18 - 2009-07-24
24367 Tor 0.2.1.18 lays the foundations for performance improvements,
24368 adds status events to help users diagnose bootstrap problems, adds
24369 optional authentication/authorization for hidden services, fixes a
24370 variety of potential anonymity problems, and includes a huge pile of
24371 other features and bug fixes.
24374 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
24377 Changes in version 0.2.1.17-rc - 2009-07-07
24378 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
24379 candidate for the 0.2.1.x series. It lays the groundwork for further
24380 client performance improvements, and also fixes a big bug with directory
24381 authorities that were causing them to assign Guard and Stable flags
24384 The Windows bundles also finally include the geoip database that we
24385 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
24386 should actually install Torbutton rather than giving you a cryptic
24387 failure message (oops).
24390 - Clients now use the bandwidth values in the consensus, rather than
24391 the bandwidth values in each relay descriptor. This approach opens
24392 the door to more accurate bandwidth estimates once the directory
24393 authorities start doing active measurements. Implements more of
24397 - When Tor clients restart after 1-5 days, they discard all their
24398 cached descriptors as too old, but they still use the cached
24399 consensus document. This approach is good for robustness, but
24400 bad for performance: since they don't know any bandwidths, they
24401 end up choosing at random rather than weighting their choice by
24402 speed. Fixed by the above feature of putting bandwidths in the
24403 consensus. Bugfix on 0.2.0.x.
24404 - Directory authorities were neglecting to mark relays down in their
24405 internal histories if the relays fall off the routerlist without
24406 ever being found unreachable. So there were relays in the histories
24407 that haven't been seen for eight months, and are listed as being
24408 up for eight months. This wreaked havoc on the "median wfu"
24409 and "median mtbf" calculations, in turn making Guard and Stable
24410 flags very wrong, hurting network performance. Fixes bugs 696 and
24411 969. Bugfix on 0.2.0.6-alpha.
24414 - Serve the DirPortFrontPage page even when we have been approaching
24415 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
24416 - The control port would close the connection before flushing long
24417 replies, such as the network consensus, if a QUIT command was issued
24418 before the reply had completed. Now, the control port flushes all
24419 pending replies before closing the connection. Also fixed a spurious
24420 warning when a QUIT command is issued after a malformed or rejected
24421 AUTHENTICATE command, but before the connection was closed. Patch
24422 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
24423 - When we can't find an intro key for a v2 hidden service descriptor,
24424 fall back to the v0 hidden service descriptor and log a bug message.
24425 Workaround for bug 1024.
24426 - Fix a log message that did not respect the SafeLogging option.
24430 - If we're a relay and we change our IP address, be more verbose
24431 about the reason that made us change. Should help track down
24432 further bugs for relays on dynamic IP addresses.
24435 Changes in version 0.2.0.35 - 2009-06-24
24437 - Avoid crashing in the presence of certain malformed descriptors.
24438 Found by lark, and by automated fuzzing.
24439 - Fix an edge case where a malicious exit relay could convince a
24440 controller that the client's DNS question resolves to an internal IP
24441 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24444 - Finally fix the bug where dynamic-IP relays disappear when their
24445 IP address changes: directory mirrors were mistakenly telling
24446 them their old address if they asked via begin_dir, so they
24447 never got an accurate answer about their new address, so they
24448 just vanished after a day. For belt-and-suspenders, relays that
24449 don't set Address in their config now avoid using begin_dir for
24450 all direct connections. Should fix bugs 827, 883, and 900.
24451 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24452 that would occur on some exit nodes when DNS failures and timeouts
24453 occurred in certain patterns. Fix for bug 957.
24456 - When starting with a cache over a few days old, do not leak
24457 memory for the obsolete router descriptors in it. Bugfix on
24458 0.2.0.33; fixes bug 672.
24459 - Hidden service clients didn't use a cached service descriptor that
24460 was older than 15 minutes, but wouldn't fetch a new one either,
24461 because there was already one in the cache. Now, fetch a v2
24462 descriptor unless the same descriptor was added to the cache within
24463 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24466 Changes in version 0.2.1.16-rc - 2009-06-20
24467 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
24468 a bunch of minor bugs.
24471 - Fix an edge case where a malicious exit relay could convince a
24472 controller that the client's DNS question resolves to an internal IP
24473 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24475 o Major performance improvements (on 0.2.0.x):
24476 - Disable and refactor some debugging checks that forced a linear scan
24477 over the whole server-side DNS cache. These accounted for over 50%
24478 of CPU time on a relatively busy exit node's gprof profile. Found
24480 - Disable some debugging checks that appeared in exit node profile
24484 - Update to the "June 3 2009" ip-to-country file.
24485 - Do not have tor-resolve automatically refuse all .onion addresses;
24486 if AutomapHostsOnResolve is set in your torrc, this will work fine.
24488 o Minor bugfixes (on 0.2.0.x):
24489 - Log correct error messages for DNS-related network errors on
24491 - Fix a race condition that could cause crashes or memory corruption
24492 when running as a server with a controller listening for log
24494 - Avoid crashing when we have a policy specified in a DirPolicy or
24495 SocksPolicy or ReachableAddresses option with ports set on it,
24496 and we re-load the policy. May fix bug 996.
24497 - Hidden service clients didn't use a cached service descriptor that
24498 was older than 15 minutes, but wouldn't fetch a new one either,
24499 because there was already one in the cache. Now, fetch a v2
24500 descriptor unless the same descriptor was added to the cache within
24501 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24503 o Minor bugfixes (on 0.2.1.x):
24504 - Don't warn users about low port and hibernation mix when they
24505 provide a *ListenAddress directive to fix that. Bugfix on
24507 - When switching back and forth between bridge mode, do not start
24508 gathering GeoIP data until two hours have passed.
24509 - Do not complain that the user has requested an excluded node as
24510 an exit when the node is not really an exit. This could happen
24511 because the circuit was for testing, or an introduction point.
24515 Changes in version 0.2.1.15-rc - 2009-05-25
24516 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
24517 series. It fixes a major bug on fast exit relays, as well as a variety
24518 of more minor bugs.
24520 o Major bugfixes (on 0.2.0.x):
24521 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24522 that would occur on some exit nodes when DNS failures and timeouts
24523 occurred in certain patterns. Fix for bug 957.
24525 o Minor bugfixes (on 0.2.0.x):
24526 - Actually return -1 in the error case for read_bandwidth_usage().
24527 Harmless bug, since we currently don't care about the return value
24528 anywhere. Bugfix on 0.2.0.9-alpha.
24529 - Provide a more useful log message if bug 977 (related to buffer
24530 freelists) ever reappears, and do not crash right away.
24531 - Fix an assertion failure on 64-bit platforms when we allocated
24532 memory right up to the end of a memarea, then realigned the memory
24533 one step beyond the end. Fixes a possible cause of bug 930.
24534 - Protect the count of open sockets with a mutex, so we can't
24535 corrupt it when two threads are closing or opening sockets at once.
24536 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
24537 - Don't allow a bridge to publish its router descriptor to a
24538 non-bridge directory authority. Fixes part of bug 932.
24539 - When we change to or from being a bridge, reset our counts of
24540 client usage by country. Fixes bug 932.
24541 - Fix a bug that made stream bandwidth get misreported to the
24543 - Stop using malloc_usable_size() to use more area than we had
24544 actually allocated: it was safe, but made valgrind really unhappy.
24545 - Fix a memory leak when v3 directory authorities load their keys
24546 and cert from disk. Bugfix on 0.2.0.1-alpha.
24548 o Minor bugfixes (on 0.2.1.x):
24549 - Fix use of freed memory when deciding to mark a non-addable
24550 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24553 Changes in version 0.2.1.14-rc - 2009-04-12
24554 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24555 series. It begins fixing some major performance problems, and also
24556 finally addresses the bug that was causing relays on dynamic IP
24557 addresses to fall out of the directory.
24560 - Clients replace entry guards that were chosen more than a few months
24561 ago. This change should significantly improve client performance,
24562 especially once more people upgrade, since relays that have been
24563 a guard for a long time are currently overloaded.
24565 o Major bugfixes (on 0.2.0):
24566 - Finally fix the bug where dynamic-IP relays disappear when their
24567 IP address changes: directory mirrors were mistakenly telling
24568 them their old address if they asked via begin_dir, so they
24569 never got an accurate answer about their new address, so they
24570 just vanished after a day. For belt-and-suspenders, relays that
24571 don't set Address in their config now avoid using begin_dir for
24572 all direct connections. Should fix bugs 827, 883, and 900.
24573 - Relays were falling out of the networkstatus consensus for
24574 part of a day if they changed their local config but the
24575 authorities discarded their new descriptor as "not sufficiently
24576 different". Now directory authorities accept a descriptor as changed
24577 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24578 patch by Sebastian.
24579 - Avoid crashing in the presence of certain malformed descriptors.
24580 Found by lark, and by automated fuzzing.
24583 - When generating circuit events with verbose nicknames for
24584 controllers, try harder to look up nicknames for routers on a
24585 circuit. (Previously, we would look in the router descriptors we had
24586 for nicknames, but not in the consensus.) Partial fix for bug 941.
24587 - If the bridge config line doesn't specify a port, assume 443.
24588 This makes bridge lines a bit smaller and easier for users to
24590 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24591 bytes (aka 20KB/s), to match our documentation. Also update
24592 directory authorities so they always assign the Fast flag to relays
24593 with 20KB/s of capacity. Now people running relays won't suddenly
24594 find themselves not seeing any use, if the network gets faster
24596 - Update to the "April 3 2009" ip-to-country file.
24599 - Avoid trying to print raw memory to the logs when we decide to
24600 give up on downloading a given relay descriptor. Bugfix on
24602 - In tor-resolve, when the Tor client to use is specified by
24603 <hostname>:<port>, actually use the specified port rather than
24604 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24605 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24606 - When starting with a cache over a few days old, do not leak
24607 memory for the obsolete router descriptors in it. Bugfix on
24609 - Avoid double-free on list of successfully uploaded hidden
24610 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24611 - Change memarea_strndup() implementation to work even when
24612 duplicating a string at the end of a page. This bug was
24613 harmless for now, but could have meant crashes later. Fix by
24614 lark. Bugfix on 0.2.1.1-alpha.
24615 - Limit uploaded directory documents to be 16M rather than 500K.
24616 The directory authorities were refusing v3 consensus votes from
24617 other authorities, since the votes are now 504K. Fixes bug 959;
24618 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24619 - Directory authorities should never send a 503 "busy" response to
24620 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24624 Changes in version 0.2.1.13-alpha - 2009-03-09
24625 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24626 cleanups. We're finally getting close to a release candidate.
24629 - Correctly update the list of which countries we exclude as
24630 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24631 lark. Bugfix on 0.2.1.6-alpha.
24633 o Minor bugfixes (on 0.2.0.x and earlier):
24634 - Automatically detect MacOSX versions earlier than 10.4.0, and
24635 disable kqueue from inside Tor when running with these versions.
24636 We previously did this from the startup script, but that was no
24637 help to people who didn't use the startup script. Resolves bug 863.
24638 - When we had picked an exit node for a connection, but marked it as
24639 "optional", and it turned out we had no onion key for the exit,
24640 stop wanting that exit and try again. This situation may not
24641 be possible now, but will probably become feasible with proposal
24642 158. Spotted by rovv. Fixes another case of bug 752.
24643 - Clients no longer cache certificates for authorities they do not
24644 recognize. Bugfix on 0.2.0.9-alpha.
24645 - When we can't transmit a DNS request due to a network error, retry
24646 it after a while, and eventually transmit a failing response to
24647 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24648 - If the controller claimed responsibility for a stream, but that
24649 stream never finished making its connection, it would live
24650 forever in circuit_wait state. Now we close it after SocksTimeout
24651 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24652 - Drop begin cells to a hidden service if they come from the middle
24653 of a circuit. Patch from lark.
24654 - When we erroneously receive two EXTEND cells for the same circuit
24655 ID on the same connection, drop the second. Patch from lark.
24656 - Fix a crash that occurs on exit nodes when a nameserver request
24657 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24658 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24660 - Do not assume that a stack-allocated character array will be
24661 64-bit aligned on platforms that demand that uint64_t access is
24662 aligned. Possible fix for bug 604.
24663 - Parse dates and IPv4 addresses in a locale- and libc-independent
24664 manner, to avoid platform-dependent behavior on malformed input.
24665 - Build correctly when configured to build outside the main source
24666 path. Patch from Michael Gold.
24667 - We were already rejecting relay begin cells with destination port
24668 of 0. Now also reject extend cells with destination port or address
24669 of 0. Suggested by lark.
24671 o Minor bugfixes (on 0.2.1.x):
24672 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24673 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24674 - If we're an exit node, scrub the IP address to which we are exiting
24675 in the logs. Bugfix on 0.2.1.8-alpha.
24678 - On Linux, use the prctl call to re-enable core dumps when the user
24680 - New controller event NEWCONSENSUS that lists the networkstatus
24681 lines for every recommended relay. Now controllers like Torflow
24682 can keep up-to-date on which relays they should be using.
24683 - Update to the "February 26 2009" ip-to-country file.
24686 Changes in version 0.2.0.34 - 2009-02-08
24687 Tor 0.2.0.34 features several more security-related fixes. You should
24688 upgrade, especially if you run an exit relay (remote crash) or a
24689 directory authority (remote infinite loop), or you're on an older
24690 (pre-XP) or not-recently-patched Windows (remote exploit).
24692 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24693 have many known flaws, and nobody should be using them. You should
24694 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24695 stop using those packages and upgrade anyway.
24698 - Fix an infinite-loop bug on handling corrupt votes under certain
24699 circumstances. Bugfix on 0.2.0.8-alpha.
24700 - Fix a temporary DoS vulnerability that could be performed by
24701 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24702 - Avoid a potential crash on exit nodes when processing malformed
24703 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24704 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24705 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24708 - Fix compilation on systems where time_t is a 64-bit integer.
24709 Patch from Matthias Drochner.
24710 - Don't consider expiring already-closed client connections. Fixes
24711 bug 893. Bugfix on 0.0.2pre20.
24714 Changes in version 0.2.1.12-alpha - 2009-02-08
24715 Tor 0.2.1.12-alpha features several more security-related fixes. You
24716 should upgrade, especially if you run an exit relay (remote crash) or
24717 a directory authority (remote infinite loop), or you're on an older
24718 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24719 includes a big pile of minor bugfixes and cleanups.
24722 - Fix an infinite-loop bug on handling corrupt votes under certain
24723 circumstances. Bugfix on 0.2.0.8-alpha.
24724 - Fix a temporary DoS vulnerability that could be performed by
24725 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24726 - Avoid a potential crash on exit nodes when processing malformed
24727 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24730 - Let controllers actually ask for the "clients_seen" event for
24731 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24732 reported by Matt Edman.
24733 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24735 - Fix a bug in address parsing that was preventing bridges or hidden
24736 service targets from being at IPv6 addresses.
24737 - Solve a bug that kept hardware crypto acceleration from getting
24738 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24740 - Remove a bash-ism from configure.in to build properly on non-Linux
24741 platforms. Bugfix on 0.2.1.1-alpha.
24742 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24743 headers. Bugfix on 0.2.0.10-alpha.
24744 - Don't consider expiring already-closed client connections. Fixes
24745 bug 893. Bugfix on 0.0.2pre20.
24746 - Fix another interesting corner-case of bug 891 spotted by rovv:
24747 Previously, if two hosts had different amounts of clock drift, and
24748 one of them created a new connection with just the wrong timing,
24749 the other might decide to deprecate the new connection erroneously.
24750 Bugfix on 0.1.1.13-alpha.
24751 - Resolve a very rare crash bug that could occur when the user forced
24752 a nameserver reconfiguration during the middle of a nameserver
24753 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
24754 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
24755 Bugfix on 0.2.1.7-alpha.
24756 - If we're using bridges and our network goes away, be more willing
24757 to forgive our bridges and try again when we get an application
24758 request. Bugfix on 0.2.0.x.
24761 - Support platforms where time_t is 64 bits long. (Congratulations,
24762 NetBSD!) Patch from Matthias Drochner.
24763 - Add a 'getinfo status/clients-seen' controller command, in case
24764 controllers want to hear clients_seen events but connect late.
24767 - Disable GCC's strict alias optimization by default, to avoid the
24768 likelihood of its introducing subtle bugs whenever our code violates
24769 the letter of C99's alias rules.
24772 Changes in version 0.2.0.33 - 2009-01-21
24773 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24774 useful to users. It also finally fixes a bug where a relay or client
24775 that's been off for many days would take a long time to bootstrap.
24777 This update also fixes an important security-related bug reported by
24778 Ilja van Sprundel. You should upgrade. (We'll send out more details
24779 about the bug once people have had some time to upgrade.)
24782 - Fix a heap-corruption bug that may be remotely triggerable on
24783 some platforms. Reported by Ilja van Sprundel.
24786 - When a stream at an exit relay is in state "resolving" or
24787 "connecting" and it receives an "end" relay cell, the exit relay
24788 would silently ignore the end cell and not close the stream. If
24789 the client never closes the circuit, then the exit relay never
24790 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24791 reported by "wood".
24792 - When sending CREATED cells back for a given circuit, use a 64-bit
24793 connection ID to find the right connection, rather than an addr:port
24794 combination. Now that we can have multiple OR connections between
24795 the same ORs, it is no longer possible to use addr:port to uniquely
24796 identify a connection.
24797 - Bridge relays that had DirPort set to 0 would stop fetching
24798 descriptors shortly after startup, and then briefly resume
24799 after a new bandwidth test and/or after publishing a new bridge
24800 descriptor. Bridge users that try to bootstrap from them would
24801 get a recent networkstatus but would get descriptors from up to
24802 18 hours earlier, meaning most of the descriptors were obsolete
24803 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24804 - Prevent bridge relays from serving their 'extrainfo' document
24805 to anybody who asks, now that extrainfo docs include potentially
24806 sensitive aggregated client geoip summaries. Bugfix on
24808 - If the cached networkstatus consensus is more than five days old,
24809 discard it rather than trying to use it. In theory it could be
24810 useful because it lists alternate directory mirrors, but in practice
24811 it just means we spend many minutes trying directory mirrors that
24812 are long gone from the network. Also discard router descriptors as
24813 we load them if they are more than five days old, since the onion
24814 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24817 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24818 could make gcc generate non-functional binary search code. Bugfix
24820 - Build correctly on platforms without socklen_t.
24821 - Compile without warnings on solaris.
24822 - Avoid potential crash on internal error during signature collection.
24823 Fixes bug 864. Patch from rovv.
24824 - Correct handling of possible malformed authority signing key
24825 certificates with internal signature types. Fixes bug 880.
24826 Bugfix on 0.2.0.3-alpha.
24827 - Fix a hard-to-trigger resource leak when logging credential status.
24829 - When we can't initialize DNS because the network is down, do not
24830 automatically stop Tor from starting. Instead, we retry failed
24831 dns_init() every 10 minutes, and change the exit policy to reject
24832 *:* until one succeeds. Fixes bug 691.
24833 - Use 64 bits instead of 32 bits for connection identifiers used with
24834 the controller protocol, to greatly reduce risk of identifier reuse.
24835 - When we're choosing an exit node for a circuit, and we have
24836 no pending streams, choose a good general exit rather than one that
24837 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24838 - Fix another case of assuming, when a specific exit is requested,
24839 that we know more than the user about what hosts it allows.
24840 Fixes one case of bug 752. Patch from rovv.
24841 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24842 seconds. Warn the user if lower values are given in the
24843 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24844 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24845 user if lower values are given in the configuration. Bugfix on
24846 0.1.1.17-rc. Patch by Sebastian.
24847 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
24848 the cache because we already had a v0 descriptor with the same ID.
24849 Bugfix on 0.2.0.18-alpha.
24850 - Fix a race condition when freeing keys shared between main thread
24851 and CPU workers that could result in a memory leak. Bugfix on
24852 0.1.0.1-rc. Fixes bug 889.
24853 - Send a valid END cell back when a client tries to connect to a
24854 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24855 840. Patch from rovv.
24856 - Check which hops rendezvous stream cells are associated with to
24857 prevent possible guess-the-streamid injection attacks from
24858 intermediate hops. Fixes another case of bug 446. Based on patch
24860 - If a broken client asks a non-exit router to connect somewhere,
24861 do not even do the DNS lookup before rejecting the connection.
24862 Fixes another case of bug 619. Patch from rovv.
24863 - When a relay gets a create cell it can't decrypt (e.g. because it's
24864 using the wrong onion key), we were dropping it and letting the
24865 client time out. Now actually answer with a destroy cell. Fixes
24866 bug 904. Bugfix on 0.0.2pre8.
24868 o Minor bugfixes (hidden services):
24869 - Do not throw away existing introduction points on SIGHUP. Bugfix on
24870 0.0.6pre1. Patch by Karsten. Fixes bug 874.
24873 - Report the case where all signatures in a detached set are rejected
24874 differently than the case where there is an error handling the
24876 - When we realize that another process has modified our cached
24877 descriptors, print out a more useful error message rather than
24878 triggering an assertion. Fixes bug 885. Patch from Karsten.
24879 - Implement the 0x20 hack to better resist DNS poisoning: set the
24880 case on outgoing DNS requests randomly, and reject responses that do
24881 not match the case correctly. This logic can be disabled with the
24882 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
24883 of servers that do not reliably preserve case in replies. See
24884 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24886 - Check DNS replies for more matching fields to better resist DNS
24888 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24889 compress cells, which are basically all encrypted, compressed, or
24893 Changes in version 0.2.1.11-alpha - 2009-01-20
24894 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
24895 week it will take a long time to bootstrap again" bug. It also fixes
24896 an important security-related bug reported by Ilja van Sprundel. You
24897 should upgrade. (We'll send out more details about the bug once people
24898 have had some time to upgrade.)
24901 - Fix a heap-corruption bug that may be remotely triggerable on
24902 some platforms. Reported by Ilja van Sprundel.
24905 - Discard router descriptors as we load them if they are more than
24906 five days old. Otherwise if Tor is off for a long time and then
24907 starts with cached descriptors, it will try to use the onion
24908 keys in those obsolete descriptors when building circuits. Bugfix
24909 on 0.2.0.x. Fixes bug 887.
24912 - Try to make sure that the version of Libevent we're running with
24913 is binary-compatible with the one we built with. May address bug
24915 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
24916 for bug 905. Bugfix on 0.2.1.7-alpha.
24917 - Add a new --enable-local-appdata configuration switch to change
24918 the default location of the datadir on win32 from APPDATA to
24919 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
24920 entirely. Patch from coderman.
24923 - Make outbound DNS packets respect the OutboundBindAddress setting.
24924 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
24925 - When our circuit fails at the first hop (e.g. we get a destroy
24926 cell back), avoid using that OR connection anymore, and also
24927 tell all the one-hop directory requests waiting for it that they
24928 should fail. Bugfix on 0.2.1.3-alpha.
24929 - In the torify(1) manpage, mention that tsocks will leak your
24933 Changes in version 0.2.1.10-alpha - 2009-01-06
24934 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
24935 would make the bridge relay not so useful if it had DirPort set to 0,
24936 and one that could let an attacker learn a little bit of information
24937 about the bridge's users), and a bug that would cause your Tor relay
24938 to ignore a circuit create request it can't decrypt (rather than reply
24939 with an error). It also fixes a wide variety of other bugs.
24942 - If the cached networkstatus consensus is more than five days old,
24943 discard it rather than trying to use it. In theory it could
24944 be useful because it lists alternate directory mirrors, but in
24945 practice it just means we spend many minutes trying directory
24946 mirrors that are long gone from the network. Helps bug 887 a bit;
24948 - Bridge relays that had DirPort set to 0 would stop fetching
24949 descriptors shortly after startup, and then briefly resume
24950 after a new bandwidth test and/or after publishing a new bridge
24951 descriptor. Bridge users that try to bootstrap from them would
24952 get a recent networkstatus but would get descriptors from up to
24953 18 hours earlier, meaning most of the descriptors were obsolete
24954 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24955 - Prevent bridge relays from serving their 'extrainfo' document
24956 to anybody who asks, now that extrainfo docs include potentially
24957 sensitive aggregated client geoip summaries. Bugfix on
24961 - New controller event "clients_seen" to report a geoip-based summary
24962 of which countries we've seen clients from recently. Now controllers
24963 like Vidalia can show bridge operators that they're actually making
24965 - Build correctly against versions of OpenSSL 0.9.8 or later built
24966 without support for deprecated functions.
24967 - Update to the "December 19 2008" ip-to-country file.
24969 o Minor bugfixes (on 0.2.0.x):
24970 - Authorities now vote for the Stable flag for any router whose
24971 weighted MTBF is at least 5 days, regardless of the mean MTBF.
24972 - Do not remove routers as too old if we do not have any consensus
24973 document. Bugfix on 0.2.0.7-alpha.
24974 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24975 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24976 - When an exit relay resolves a stream address to a local IP address,
24977 do not just keep retrying that same exit relay over and
24978 over. Instead, just close the stream. Addresses bug 872. Bugfix
24979 on 0.2.0.32. Patch from rovv.
24980 - If a hidden service sends us an END cell, do not consider
24981 retrying the connection; just close it. Patch from rovv.
24982 - When we made bridge authorities stop serving bridge descriptors over
24983 unencrypted links, we also broke DirPort reachability testing for
24984 bridges. So bridges with a non-zero DirPort were printing spurious
24985 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
24986 - When a relay gets a create cell it can't decrypt (e.g. because it's
24987 using the wrong onion key), we were dropping it and letting the
24988 client time out. Now actually answer with a destroy cell. Fixes
24989 bug 904. Bugfix on 0.0.2pre8.
24990 - Squeeze 2-5% out of client performance (according to oprofile) by
24991 improving the implementation of some policy-manipulation functions.
24993 o Minor bugfixes (on 0.2.1.x):
24994 - Make get_interface_address() function work properly again; stop
24995 guessing the wrong parts of our address as our address.
24996 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
24997 send on that circuit. Otherwise we might violate the proposal-110
24998 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
25000 - When we're sending non-EXTEND cells to the first hop in a circuit,
25001 for example to use an encrypted directory connection, we don't need
25002 to use RELAY_EARLY cells: the first hop knows what kind of cell
25003 it is, and nobody else can even see the cell type. Conserving
25004 RELAY_EARLY cells makes it easier to cannibalize circuits like
25006 - Stop logging nameserver addresses in reverse order.
25007 - If we are retrying a directory download slowly over and over, do
25008 not automatically give up after the 254th failure. Bugfix on
25010 - Resume reporting accurate "stream end" reasons to the local control
25011 port. They were lost in the changes for Proposal 148. Bugfix on
25014 o Deprecated and removed features:
25015 - The old "tor --version --version" command, which would print out
25016 the subversion "Id" of most of the source files, is now removed. It
25017 turned out to be less useful than we'd expected, and harder to
25020 o Code simplifications and refactoring:
25021 - Change our header file guard macros to be less likely to conflict
25022 with system headers. Adam Langley noticed that we were conflicting
25023 with log.h on Android.
25024 - Tool-assisted documentation cleanup. Nearly every function or
25025 static variable in Tor should have its own documentation now.
25028 Changes in version 0.2.1.9-alpha - 2008-12-25
25029 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
25031 o New directory authorities:
25032 - gabelmoo (the authority run by Karsten Loesing) now has a new
25036 - Never use a connection with a mismatched address to extend a
25037 circuit, unless that connection is canonical. A canonical
25038 connection is one whose address is authenticated by the router's
25039 identity key, either in a NETINFO cell or in a router descriptor.
25040 - Avoid a possible memory corruption bug when receiving hidden service
25041 descriptors. Bugfix on 0.2.1.6-alpha.
25044 - Fix a logic error that would automatically reject all but the first
25045 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
25046 part of bug 813/868. Bug spotted by coderman.
25047 - When a stream at an exit relay is in state "resolving" or
25048 "connecting" and it receives an "end" relay cell, the exit relay
25049 would silently ignore the end cell and not close the stream. If
25050 the client never closes the circuit, then the exit relay never
25051 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
25052 reported by "wood".
25053 - When we can't initialize DNS because the network is down, do not
25054 automatically stop Tor from starting. Instead, retry failed
25055 dns_init() every 10 minutes, and change the exit policy to reject
25056 *:* until one succeeds. Fixes bug 691.
25059 - Give a better error message when an overzealous init script says
25060 "sudo -u username tor --user username". Makes Bug 882 easier for
25062 - When a directory authority gives us a new guess for our IP address,
25063 log which authority we used. Hopefully this will help us debug
25064 the recent complaints about bad IP address guesses.
25065 - Detect svn revision properly when we're using git-svn.
25066 - Try not to open more than one descriptor-downloading connection
25067 to an authority at once. This should reduce load on directory
25068 authorities. Fixes bug 366.
25069 - Add cross-certification to newly generated certificates, so that
25070 a signing key is enough information to look up a certificate.
25071 Partial implementation of proposal 157.
25072 - Start serving certificates by <identity digest, signing key digest>
25073 pairs. Partial implementation of proposal 157.
25074 - Clients now never report any stream end reason except 'MISC'.
25075 Implements proposal 148.
25076 - On platforms with a maximum syslog string length, truncate syslog
25077 messages to that length ourselves, rather than relying on the
25078 system to do it for us.
25079 - Optimize out calls to time(NULL) that occur for every IO operation,
25080 or for every cell. On systems where time() is a slow syscall,
25081 this fix will be slightly helpful.
25082 - Exit servers can now answer resolve requests for ip6.arpa addresses.
25083 - When we download a descriptor that we then immediately (as
25084 a directory authority) reject, do not retry downloading it right
25085 away. Should save some bandwidth on authorities. Fix for bug
25086 888. Patch by Sebastian Hahn.
25087 - When a download gets us zero good descriptors, do not notify
25088 Tor that new directory information has arrived.
25089 - Avoid some nasty corner cases in the logic for marking connections
25090 as too old or obsolete or noncanonical for circuits. Partial
25093 o Minor features (controller):
25094 - New CONSENSUS_ARRIVED event to note when a new consensus has
25095 been fetched and validated.
25096 - When we realize that another process has modified our cached
25097 descriptors file, print out a more useful error message rather
25098 than triggering an assertion. Fixes bug 885. Patch from Karsten.
25099 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
25100 controllers to prevent SIGHUP from reloading the
25101 configuration. Fixes bug 856.
25104 - Resume using the correct "REASON=" stream when telling the
25105 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
25106 - When a canonical connection appears later in our internal list
25107 than a noncanonical one for a given OR ID, always use the
25108 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
25110 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25111 seconds. Warn the user if lower values are given in the
25112 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25113 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25114 user if lower values are given in the configuration. Bugfix on
25115 0.1.1.17-rc. Patch by Sebastian.
25116 - Fix a race condition when freeing keys shared between main thread
25117 and CPU workers that could result in a memory leak. Bugfix on
25118 0.1.0.1-rc. Fixes bug 889.
25120 o Minor bugfixes (hidden services):
25121 - Do not throw away existing introduction points on SIGHUP (bugfix on
25122 0.0.6pre1); also, do not stall hidden services because we're
25123 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
25124 by John Brooks. Patch by Karsten. Fixes bug 874.
25125 - Fix a memory leak when we decline to add a v2 rendezvous
25126 descriptor to the cache because we already had a v0 descriptor
25127 with the same ID. Bugfix on 0.2.0.18-alpha.
25129 o Deprecated and removed features:
25130 - RedirectExits has been removed. It was deprecated since
25132 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
25133 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
25134 - Cell pools are now always enabled; --disable-cell-pools is ignored.
25136 o Code simplifications and refactoring:
25137 - Rename the confusing or_is_obsolete field to the more appropriate
25138 is_bad_for_new_circs, and move it to or_connection_t where it
25140 - Move edge-only flags from connection_t to edge_connection_t: not
25141 only is this better coding, but on machines of plausible alignment,
25142 it should save 4-8 bytes per connection_t. "Every little bit helps."
25143 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
25144 for consistency; keep old option working for backward compatibility.
25145 - Simplify the code for finding connections to use for a circuit.
25148 Changes in version 0.2.1.8-alpha - 2008-12-08
25149 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
25150 builds better on unusual platforms like Solaris and old OS X, and
25151 fixes a variety of other issues.
25154 - New DirPortFrontPage option that takes an html file and publishes
25155 it as "/" on the DirPort. Now relay operators can provide a
25156 disclaimer without needing to set up a separate webserver. There's
25157 a sample disclaimer in contrib/tor-exit-notice.html.
25160 - When the client is choosing entry guards, now it selects at most
25161 one guard from a given relay family. Otherwise we could end up with
25162 all of our entry points into the network run by the same operator.
25163 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
25166 - Fix a DOS opportunity during the voting signature collection process
25167 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25168 - Fix a possible segfault when establishing an exit connection. Bugfix
25172 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
25174 - Made Tor a little less aggressive about deleting expired
25175 certificates. Partial fix for bug 854.
25176 - Stop doing unaligned memory access that generated bus errors on
25177 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
25178 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
25179 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
25180 - Make USR2 log-level switch take effect immediately. Bugfix on
25182 - If one win32 nameserver fails to get added, continue adding the
25183 rest, and don't automatically fail.
25184 - Use fcntl() for locking when flock() is not available. Should fix
25185 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
25186 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25187 could make gcc generate non-functional binary search code. Bugfix
25189 - Build correctly on platforms without socklen_t.
25190 - Avoid potential crash on internal error during signature collection.
25191 Fixes bug 864. Patch from rovv.
25192 - Do not use C's stdio library for writing to log files. This will
25193 improve logging performance by a minute amount, and will stop
25194 leaking fds when our disk is full. Fixes bug 861.
25195 - Stop erroneous use of O_APPEND in cases where we did not in fact
25196 want to re-seek to the end of a file before every last write().
25197 - Correct handling of possible malformed authority signing key
25198 certificates with internal signature types. Fixes bug 880. Bugfix
25200 - Fix a hard-to-trigger resource leak when logging credential status.
25204 - Directory mirrors no longer fetch the v1 directory or
25205 running-routers files. They are obsolete, and nobody asks for them
25206 anymore. This is the first step to making v1 authorities obsolete.
25208 o Minor features (controller):
25209 - Return circuit purposes in response to GETINFO circuit-status. Fixes
25213 Changes in version 0.2.0.32 - 2008-11-20
25214 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
25215 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25216 a smaller security flaw that might allow an attacker to access local
25217 services, further improves hidden service performance, and fixes a
25218 variety of other issues.
25221 - The "User" and "Group" config options did not clear the
25222 supplementary group entries for the Tor process. The "User" option
25223 is now more robust, and we now set the groups to the specified
25224 user's primary group. The "Group" option is now ignored. For more
25225 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25226 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25227 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
25228 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25229 consistently obeyed: if an exit relay refuses a stream because its
25230 exit policy doesn't allow it, we would remember what IP address
25231 the relay said the destination address resolves to, even if it's
25232 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25235 - Fix a DOS opportunity during the voting signature collection process
25236 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25238 o Major bugfixes (hidden services):
25239 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25240 we were failing the whole hidden service request when the v0
25241 descriptor fetch fails, even if the v2 fetch is still pending and
25242 might succeed. Similarly, if the last v2 fetch fails, we were
25243 failing the whole hidden service request even if a v0 fetch is
25244 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25245 - When extending a circuit to a hidden service directory to upload a
25246 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25247 requests failed, because the router descriptor has not been
25248 downloaded yet. In these cases, do not attempt to upload the
25249 rendezvous descriptor, but wait until the router descriptor is
25250 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
25251 descriptor from a hidden service directory for which the router
25252 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
25256 - Fix several infrequent memory leaks spotted by Coverity.
25257 - When testing for libevent functions, set the LDFLAGS variable
25258 correctly. Found by Riastradh.
25259 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25260 bootstrapping with tunneled directory connections. Bugfix on
25261 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25262 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25263 and we know that server B rejects most-but-not all connections to
25264 port 80, we would previously reject the connection. Now, we assume
25265 the user knows what they were asking for. Fixes bug 752. Bugfix
25266 on 0.0.9rc5. Diagnosed by BarkerJr.
25267 - If we overrun our per-second write limits a little, count this as
25268 having used up our write allocation for the second, and choke
25269 outgoing directory writes. Previously, we had only counted this when
25270 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
25271 Bugfix on 0.2.0.x (??).
25272 - Remove the old v2 directory authority 'lefkada' from the default
25273 list. It has been gone for many months.
25274 - Stop doing unaligned memory access that generated bus errors on
25275 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
25276 - Make USR2 log-level switch take effect immediately. Bugfix on
25279 o Minor bugfixes (controller):
25280 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
25281 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
25284 Changes in version 0.2.1.7-alpha - 2008-11-08
25285 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
25286 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25287 a smaller security flaw that might allow an attacker to access local
25288 services, adds better defense against DNS poisoning attacks on exit
25289 relays, further improves hidden service performance, and fixes a
25290 variety of other issues.
25293 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25294 consistently obeyed: if an exit relay refuses a stream because its
25295 exit policy doesn't allow it, we would remember what IP address
25296 the relay said the destination address resolves to, even if it's
25297 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25298 - The "User" and "Group" config options did not clear the
25299 supplementary group entries for the Tor process. The "User" option
25300 is now more robust, and we now set the groups to the specified
25301 user's primary group. The "Group" option is now ignored. For more
25302 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25303 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25304 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
25305 - Do not use or believe expired v3 authority certificates. Patch
25306 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
25309 - Now NodeFamily and MyFamily config options allow spaces in
25310 identity fingerprints, so it's easier to paste them in.
25311 Suggested by Lucky Green.
25312 - Implement the 0x20 hack to better resist DNS poisoning: set the
25313 case on outgoing DNS requests randomly, and reject responses that do
25314 not match the case correctly. This logic can be disabled with the
25315 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
25316 of servers that do not reliably preserve case in replies. See
25317 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25319 - Preserve case in replies to DNSPort requests in order to support
25320 the 0x20 hack for resisting DNS poisoning attacks.
25322 o Hidden service performance improvements:
25323 - When the client launches an introduction circuit, retry with a
25324 new circuit after 30 seconds rather than 60 seconds.
25325 - Launch a second client-side introduction circuit in parallel
25326 after a delay of 15 seconds (based on work by Christian Wilms).
25327 - Hidden services start out building five intro circuits rather
25328 than three, and when the first three finish they publish a service
25329 descriptor using those. Now we publish our service descriptor much
25330 faster after restart.
25333 - Minor fix in the warning messages when you're having problems
25334 bootstrapping; also, be more forgiving of bootstrap problems when
25335 we're still making incremental progress on a given bootstrap phase.
25336 - When we're choosing an exit node for a circuit, and we have
25337 no pending streams, choose a good general exit rather than one that
25338 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25339 - Send a valid END cell back when a client tries to connect to a
25340 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25341 840. Patch from rovv.
25342 - If a broken client asks a non-exit router to connect somewhere,
25343 do not even do the DNS lookup before rejecting the connection.
25344 Fixes another case of bug 619. Patch from rovv.
25345 - Fix another case of assuming, when a specific exit is requested,
25346 that we know more than the user about what hosts it allows.
25347 Fixes another case of bug 752. Patch from rovv.
25348 - Check which hops rendezvous stream cells are associated with to
25349 prevent possible guess-the-streamid injection attacks from
25350 intermediate hops. Fixes another case of bug 446. Based on patch
25352 - Avoid using a negative right-shift when comparing 32-bit
25353 addresses. Possible fix for bug 845 and bug 811.
25354 - Make the assert_circuit_ok() function work correctly on circuits that
25355 have already been marked for close.
25356 - Fix read-off-the-end-of-string error in unit tests when decoding
25357 introduction points.
25358 - Fix uninitialized size field for memory area allocation: may improve
25359 memory performance during directory parsing.
25360 - Treat duplicate certificate fetches as failures, so that we do
25361 not try to re-fetch an expired certificate over and over and over.
25362 - Do not say we're fetching a certificate when we'll in fact skip it
25363 because of a pending download.
25366 Changes in version 0.2.1.6-alpha - 2008-09-30
25367 Tor 0.2.1.6-alpha further improves performance and robustness of
25368 hidden services, starts work on supporting per-country relay selection,
25369 and fixes a variety of smaller issues.
25372 - Implement proposal 121: make it possible to build hidden services
25373 that only certain clients are allowed to connect to. This is
25374 enforced at several points, so that unauthorized clients are unable
25375 to send INTRODUCE cells to the service, or even (depending on the
25376 type of authentication) to learn introduction points. This feature
25377 raises the bar for certain kinds of active attacks against hidden
25378 services. Code by Karsten Loesing.
25379 - Relays now store and serve v2 hidden service descriptors by default,
25380 i.e., the new default value for HidServDirectoryV2 is 1. This is
25381 the last step in proposal 114, which aims to make hidden service
25382 lookups more reliable.
25383 - Start work to allow node restrictions to include country codes. The
25384 syntax to exclude nodes in a country with country code XX is
25385 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
25386 refinement to decide what config options should take priority if
25387 you ask to both use a particular node and exclude it.
25388 - Allow ExitNodes list to include IP ranges and country codes, just
25389 like the Exclude*Nodes lists. Patch from Robert Hogan.
25392 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
25393 Tor to fail to start if you had it configured to use a bridge
25394 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
25395 - When extending a circuit to a hidden service directory to upload a
25396 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25397 requests failed, because the router descriptor had not been
25398 downloaded yet. In these cases, we now wait until the router
25399 descriptor is downloaded, and then retry. Likewise, clients
25400 now skip over a hidden service directory if they don't yet have
25401 its router descriptor, rather than futilely requesting it and
25402 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
25404 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25405 we were failing the whole hidden service request when the v0
25406 descriptor fetch fails, even if the v2 fetch is still pending and
25407 might succeed. Similarly, if the last v2 fetch fails, we were
25408 failing the whole hidden service request even if a v0 fetch is
25409 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25410 - DNS replies need to have names matching their requests, but
25411 these names should be in the questions section, not necessarily
25412 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
25415 - Update to the "September 1 2008" ip-to-country file.
25416 - Allow ports 465 and 587 in the default exit policy again. We had
25417 rejected them in 0.1.0.15, because back in 2005 they were commonly
25418 misconfigured and ended up as spam targets. We hear they are better
25419 locked down these days.
25420 - Use a lockfile to make sure that two Tor processes are not
25421 simultaneously running with the same datadir.
25422 - Serve the latest v3 networkstatus consensus via the control
25423 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
25424 - Better logging about stability/reliability calculations on directory
25426 - Drop the requirement to have an open dir port for storing and
25427 serving v2 hidden service descriptors.
25428 - Directory authorities now serve a /tor/dbg-stability.txt URL to
25429 help debug WFU and MTBF calculations.
25430 - Implement most of Proposal 152: allow specialized servers to permit
25431 single-hop circuits, and clients to use those servers to build
25432 single-hop circuits when using a specialized controller. Patch
25433 from Josh Albrecht. Resolves feature request 768.
25434 - Add a -p option to tor-resolve for specifying the SOCKS port: some
25435 people find host:port too confusing.
25436 - Make TrackHostExit mappings expire a while after their last use, not
25437 after their creation. Patch from Robert Hogan.
25438 - Provide circuit purposes along with circuit events to the controller.
25441 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
25443 - Fixed some memory leaks -- some quite frequent, some almost
25444 impossible to trigger -- based on results from Coverity.
25445 - When testing for libevent functions, set the LDFLAGS variable
25446 correctly. Found by Riastradh.
25447 - Fix an assertion bug in parsing policy-related options; possible fix
25449 - Catch and report a few more bootstrapping failure cases when Tor
25450 fails to establish a TCP connection. Cleanup on 0.2.1.x.
25451 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25452 bootstrapping with tunneled directory connections. Bugfix on
25453 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25454 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25455 and we know that server B rejects most-but-not all connections to
25456 port 80, we would previously reject the connection. Now, we assume
25457 the user knows what they were asking for. Fixes bug 752. Bugfix
25458 on 0.0.9rc5. Diagnosed by BarkerJr.
25459 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
25460 service directories if they have no advertised dir port. Bugfix
25462 - If we overrun our per-second write limits a little, count this as
25463 having used up our write allocation for the second, and choke
25464 outgoing directory writes. Previously, we had only counted this when
25465 we had met our limits precisely. Fixes bug 824. Patch by rovv.
25466 Bugfix on 0.2.0.x (??).
25467 - Avoid a "0 divided by 0" calculation when calculating router uptime
25468 at directory authorities. Bugfix on 0.2.0.8-alpha.
25469 - Make DNS resolved controller events into "CLOSED", not
25470 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
25472 - Fix a bug where an unreachable relay would establish enough
25473 reachability testing circuits to do a bandwidth test -- if
25474 we already have a connection to the middle hop of the testing
25475 circuit, then it could establish the last hop by using the existing
25476 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
25477 circuits no longer use entry guards in 0.2.1.3-alpha.
25478 - If we have correct permissions on $datadir, we complain to stdout
25479 and fail to start. But dangerous permissions on
25480 $datadir/cached-status/ would cause us to open a log and complain
25481 there. Now complain to stdout and fail to start in both cases. Fixes
25482 bug 820, reported by seeess.
25483 - Remove the old v2 directory authority 'lefkada' from the default
25484 list. It has been gone for many months.
25486 o Code simplifications and refactoring:
25487 - Revise the connection_new functions so that a more typesafe variant
25488 exists. This will work better with Coverity, and let us find any
25489 actual mistakes we're making here.
25490 - Refactor unit testing logic so that dmalloc can be used sensibly
25491 with unit tests to check for memory leaks.
25492 - Move all hidden-service related fields from connection and circuit
25493 structure to substructures: this way they won't eat so much memory.
25496 Changes in version 0.2.0.31 - 2008-09-03
25497 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
25498 a big bug we're seeing where in rare cases traffic from one Tor stream
25499 gets mixed into another stream, and fixes a variety of smaller issues.
25502 - Make sure that two circuits can never exist on the same connection
25503 with the same circuit ID, even if one is marked for close. This
25504 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
25505 - Relays now reject risky extend cells: if the extend cell includes
25506 a digest of all zeroes, or asks to extend back to the relay that
25507 sent the extend cell, tear down the circuit. Ideas suggested
25509 - If not enough of our entry guards are available so we add a new
25510 one, we might use the new one even if it overlapped with the
25511 current circuit's exit relay (or its family). Anonymity bugfix
25512 pointed out by rovv.
25515 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25516 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25517 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25518 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25519 - Pick size of default geoip filename string correctly on windows.
25520 Fixes bug 806. Bugfix on 0.2.0.30.
25521 - Make the autoconf script accept the obsolete --with-ssl-dir
25522 option as an alias for the actually-working --with-openssl-dir
25523 option. Fix the help documentation to recommend --with-openssl-dir.
25524 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25525 - When using the TransPort option on OpenBSD, and using the User
25526 option to change UID and drop privileges, make sure to open
25527 /dev/pf before dropping privileges. Fixes bug 782. Patch from
25528 Christopher Davis. Bugfix on 0.1.2.1-alpha.
25529 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25530 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25531 on the client side when connecting to a hidden service. Bugfix
25532 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25533 - When closing an application-side connection because its circuit is
25534 getting torn down, generate the stream event correctly. Bugfix on
25535 0.1.2.x. Anonymous patch.
25538 Changes in version 0.2.1.5-alpha - 2008-08-31
25539 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25540 in a lot of the infrastructure for adding authorization to hidden
25541 services, lays the groundwork for having clients read their load
25542 balancing information out of the networkstatus consensus rather than
25543 the individual router descriptors, addresses two potential anonymity
25544 issues, and fixes a variety of smaller issues.
25547 - Convert many internal address representations to optionally hold
25549 - Generate and accept IPv6 addresses in many protocol elements.
25550 - Make resolver code handle nameservers located at ipv6 addresses.
25551 - Begin implementation of proposal 121 ("Client authorization for
25552 hidden services"): configure hidden services with client
25553 authorization, publish descriptors for them, and configure
25554 authorization data for hidden services at clients. The next
25555 step is to actually access hidden services that perform client
25557 - More progress toward proposal 141: Network status consensus
25558 documents and votes now contain bandwidth information for each
25559 router and a summary of that router's exit policy. Eventually this
25560 will be used by clients so that they do not have to download every
25561 known descriptor before building circuits.
25563 o Major bugfixes (on 0.2.0.x and before):
25564 - When sending CREATED cells back for a given circuit, use a 64-bit
25565 connection ID to find the right connection, rather than an addr:port
25566 combination. Now that we can have multiple OR connections between
25567 the same ORs, it is no longer possible to use addr:port to uniquely
25568 identify a connection.
25569 - Relays now reject risky extend cells: if the extend cell includes
25570 a digest of all zeroes, or asks to extend back to the relay that
25571 sent the extend cell, tear down the circuit. Ideas suggested
25573 - If not enough of our entry guards are available so we add a new
25574 one, we might use the new one even if it overlapped with the
25575 current circuit's exit relay (or its family). Anonymity bugfix
25576 pointed out by rovv.
25579 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25580 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25581 - When using the TransPort option on OpenBSD, and using the User
25582 option to change UID and drop privileges, make sure to open /dev/pf
25583 before dropping privileges. Fixes bug 782. Patch from Christopher
25584 Davis. Bugfix on 0.1.2.1-alpha.
25585 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25586 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25587 - Add a missing safe_str() call for a debug log message.
25588 - Use 64 bits instead of 32 bits for connection identifiers used with
25589 the controller protocol, to greatly reduce risk of identifier reuse.
25590 - Make the autoconf script accept the obsolete --with-ssl-dir
25591 option as an alias for the actually-working --with-openssl-dir
25592 option. Fix the help documentation to recommend --with-openssl-dir.
25593 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25596 - Rate-limit too-many-sockets messages: when they happen, they happen
25597 a lot. Resolves bug 748.
25598 - Resist DNS poisoning a little better by making sure that names in
25599 answer sections match.
25600 - Print the SOCKS5 error message string as well as the error code
25601 when a tor-resolve request fails. Patch from Jacob.
25604 Changes in version 0.2.1.4-alpha - 2008-08-04
25605 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25608 - The address part of exit policies was not correctly written
25609 to router descriptors. This generated router descriptors that failed
25610 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25612 - Tor triggered a false assert when extending a circuit to a relay
25613 but we already have a connection open to that relay. Noticed by
25614 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25617 - Fix a hidden service logging bug: in some edge cases, the router
25618 descriptor of a previously picked introduction point becomes
25619 obsolete and we need to give up on it rather than continually
25620 complaining that it has become obsolete. Observed by xiando. Bugfix
25623 o Removed features:
25624 - Take out the TestVia config option, since it was a workaround for
25625 a bug that was fixed in Tor 0.1.1.21.
25628 Changes in version 0.2.1.3-alpha - 2008-08-03
25629 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25630 infinite-length circuit attacks (see proposal 110); fixes a bug that
25631 might cause exit relays to corrupt streams they send back; allows
25632 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25633 ExcludeExitNodes config options; and fixes a big pile of bugs.
25635 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25636 - Send a bootstrap problem "warn" event on the first problem if the
25637 reason is NO_ROUTE (that is, our network is down).
25640 - Implement most of proposal 110: The first K cells to be sent
25641 along a circuit are marked as special "early" cells; only K "early"
25642 cells will be allowed. Once this code is universal, we can block
25643 certain kinds of DOS attack by requiring that EXTEND commands must
25644 be sent using an "early" cell.
25647 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25648 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25649 on the client side when connecting to a hidden service. Bugfix
25650 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25651 - Ensure that two circuits can never exist on the same connection
25652 with the same circuit ID, even if one is marked for close. This
25653 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25656 - When relays do their initial bandwidth measurement, don't limit
25657 to just our entry guards for the test circuits. Otherwise we tend
25658 to have multiple test circuits going through a single entry guard,
25659 which makes our bandwidth test less accurate. Fixes part of bug 654;
25660 patch contributed by Josh Albrecht.
25661 - Add an ExcludeExitNodes option so users can list a set of nodes
25662 that should be be excluded from the exit node position, but
25663 allowed elsewhere. Implements proposal 151.
25664 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25665 ExcludeNodes and ExcludeExitNodes lists.
25666 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25667 be more efficient. Formerly it was quadratic in the number of
25668 servers; now it should be linear. Fixes bug 509.
25669 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25670 and n_conn_id_digest fields into a separate structure that's
25671 only needed when the circuit has not yet attached to an n_conn.
25674 - Change the contrib/tor.logrotate script so it makes the new
25675 logs as "_tor:_tor" rather than the default, which is generally
25676 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25677 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25678 warnings (occasionally), but it can also cause the compiler to
25679 eliminate error-checking code. Suggested by Peter Gutmann.
25680 - When a hidden service is giving up on an introduction point candidate
25681 that was not included in the last published rendezvous descriptor,
25682 don't reschedule publication of the next descriptor. Fixes bug 763.
25684 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25685 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25686 and nobody claims to be using them. Fixes bug 754. Bugfix on
25687 0.1.0.1-rc. Patch from Christian Wilms.
25688 - Fix a small alignment and memory-wasting bug on buffer chunks.
25691 o Minor bugfixes (controller):
25692 - When closing an application-side connection because its circuit
25693 is getting torn down, generate the stream event correctly.
25694 Bugfix on 0.1.2.x. Anonymous patch.
25696 o Removed features:
25697 - Remove all backward-compatibility code to support relays running
25698 versions of Tor so old that they no longer work at all on the
25702 Changes in version 0.2.0.30 - 2008-07-15
25704 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25705 warnings (occasionally), but it can also cause the compiler to
25706 eliminate error-checking code. Suggested by Peter Gutmann.
25709 Changes in version 0.2.0.29-rc - 2008-07-08
25710 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25711 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25714 - If you have more than one bridge but don't know their keys,
25715 you would only launch a request for the descriptor of the first one
25716 on your list. (Tor considered launching requests for the others, but
25717 found that it already had a connection on the way for $0000...0000
25718 so it didn't open another.) Bugfix on 0.2.0.x.
25719 - If you have more than one bridge but don't know their keys, and the
25720 connection to one of the bridges failed, you would cancel all
25721 pending bridge connections. (After all, they all have the same
25722 digest.) Bugfix on 0.2.0.x.
25723 - When a hidden service was trying to establish an introduction point,
25724 and Tor had built circuits preemptively for such purposes, we
25725 were ignoring all the preemptive circuits and launching a new one
25726 instead. Bugfix on 0.2.0.14-alpha.
25727 - When a hidden service was trying to establish an introduction point,
25728 and Tor *did* manage to reuse one of the preemptively built
25729 circuits, it didn't correctly remember which one it used,
25730 so it asked for another one soon after, until there were no
25731 more preemptive circuits, at which point it launched one from
25732 scratch. Bugfix on 0.0.9.x.
25733 - Make directory servers include the X-Your-Address-Is: http header in
25734 their responses even for begin_dir conns. Now clients who only
25735 ever use begin_dir connections still have a way to learn their IP
25736 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25739 - Fix a macro/CPP interaction that was confusing some compilers:
25740 some GCCs don't like #if/#endif pairs inside macro arguments.
25742 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25743 Fixes bug 704; fix from Steven Murdoch.
25744 - When opening /dev/null in finish_daemonize(), do not pass the
25745 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25746 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25747 - Correctly detect transparent proxy support on Linux hosts that
25748 require in.h to be included before netfilter_ipv4.h. Patch
25750 - Disallow session resumption attempts during the renegotiation
25751 stage of the v2 handshake protocol. Clients should never be trying
25752 session resumption at this point, but apparently some did, in
25753 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
25754 found by Geoff Goodell.
25757 Changes in version 0.2.1.2-alpha - 2008-06-20
25758 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
25759 make it easier to set up your own private Tor network; fixes several
25760 big bugs with using more than one bridge relay; fixes a big bug with
25761 offering hidden services quickly after Tor starts; and uses a better
25762 API for reporting potential bootstrapping problems to the controller.
25765 - New TestingTorNetwork config option to allow adjustment of
25766 previously constant values that, while reasonable, could slow
25767 bootstrapping. Implements proposal 135. Patch from Karsten.
25770 - If you have more than one bridge but don't know their digests,
25771 you would only learn a request for the descriptor of the first one
25772 on your list. (Tor considered launching requests for the others, but
25773 found that it already had a connection on the way for $0000...0000
25774 so it didn't open another.) Bugfix on 0.2.0.x.
25775 - If you have more than one bridge but don't know their digests,
25776 and the connection to one of the bridges failed, you would cancel
25777 all pending bridge connections. (After all, they all have the
25778 same digest.) Bugfix on 0.2.0.x.
25779 - When establishing a hidden service, introduction points that
25780 originate from cannibalized circuits are completely ignored and not
25781 included in rendezvous service descriptors. This might be another
25782 reason for delay in making a hidden service available. Bugfix
25783 from long ago (0.0.9.x?)
25786 - Allow OpenSSL to use dynamic locks if it wants.
25787 - When building a consensus, do not include routers that are down.
25788 This will cut down 30% to 40% on consensus size. Implements
25790 - In directory authorities' approved-routers files, allow
25791 fingerprints with or without space.
25792 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
25793 controller can query our current bootstrap state in case it attaches
25794 partway through and wants to catch up.
25795 - Send an initial "Starting" bootstrap status event, so we have a
25796 state to start out in.
25799 - Asking for a conditional consensus at .../consensus/<fingerprints>
25800 would crash a dirserver if it did not already have a
25801 consensus. Bugfix on 0.2.1.1-alpha.
25802 - Clean up some macro/CPP interactions: some GCC versions don't like
25803 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
25806 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
25807 - Directory authorities shouldn't complain about bootstrapping
25808 problems just because they do a lot of reachability testing and
25809 some of the connection attempts fail.
25810 - Start sending "count" and "recommendation" key/value pairs in
25811 bootstrap problem status events, so the controller can hear about
25812 problems even before Tor decides they're worth reporting for sure.
25813 - If you're using bridges, generate "bootstrap problem" warnings
25814 as soon as you run out of working bridges, rather than waiting
25815 for ten failures -- which will never happen if you have less than
25817 - If we close our OR connection because there's been a circuit
25818 pending on it for too long, we were telling our bootstrap status
25819 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
25822 Changes in version 0.2.1.1-alpha - 2008-06-13
25823 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
25824 were making the Tor process bloat especially on Linux; makes our TLS
25825 handshake blend in better; sends "bootstrap phase" status events to
25826 the controller, so it can keep the user informed of progress (and
25827 problems) fetching directory information and establishing circuits;
25828 and adds a variety of smaller features.
25831 - More work on making our TLS handshake blend in: modify the list
25832 of ciphers advertised by OpenSSL in client mode to even more
25833 closely resemble a common web browser. We cheat a little so that
25834 we can advertise ciphers that the locally installed OpenSSL doesn't
25836 - Start sending "bootstrap phase" status events to the controller,
25837 so it can keep the user informed of progress fetching directory
25838 information and establishing circuits. Also inform the controller
25839 if we think we're stuck at a particular bootstrap phase. Implements
25841 - Resume using OpenSSL's RAND_poll() for better (and more portable)
25842 cross-platform entropy collection again. We used to use it, then
25843 stopped using it because of a bug that could crash systems that
25844 called RAND_poll when they had a lot of fds open. It looks like the
25845 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
25846 at startup, and to call RAND_poll() when we reseed later only if
25847 we have a non-buggy OpenSSL version.
25850 - When we choose to abandon a new entry guard because we think our
25851 older ones might be better, close any circuits pending on that
25852 new entry guard connection. This fix should make us recover much
25853 faster when our network is down and then comes back. Bugfix on
25854 0.1.2.8-beta; found by lodger.
25856 o Memory fixes and improvements:
25857 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
25858 to avoid unused RAM in buffer chunks and memory pools.
25859 - Speed up parsing and cut down on memory fragmentation by using
25860 stack-style allocations for parsing directory objects. Previously,
25861 this accounted for over 40% of allocations from within Tor's code
25862 on a typical directory cache.
25863 - Use a Bloom filter rather than a digest-based set to track which
25864 descriptors we need to keep around when we're cleaning out old
25865 router descriptors. This speeds up the computation significantly,
25866 and may reduce fragmentation.
25867 - Reduce the default smartlist size from 32 to 16; it turns out that
25868 most smartlists hold around 8-12 elements tops.
25869 - Make dumpstats() log the fullness and size of openssl-internal
25871 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
25872 patch to their OpenSSL, turn it on to save memory on servers. This
25873 patch will (with any luck) get included in a mainline distribution
25875 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25876 compress cells, which are basically all encrypted, compressed,
25880 - Stop reloading the router list from disk for no reason when we
25881 run out of reachable directory mirrors. Once upon a time reloading
25882 it would set the 'is_running' flag back to 1 for them. It hasn't
25883 done that for a long time.
25884 - In very rare situations new hidden service descriptors were
25885 published earlier than 30 seconds after the last change to the
25886 service. (We currently think that a hidden service descriptor
25887 that's been stable for 30 seconds is worth publishing.)
25890 - Allow separate log levels to be configured for different logging
25891 domains. For example, this allows one to log all notices, warnings,
25892 or errors, plus all memory management messages of level debug or
25893 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
25894 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
25895 and stop using a warning that had become unfixably verbose under
25897 - New --hush command-line option similar to --quiet. While --quiet
25898 disables all logging to the console on startup, --hush limits the
25899 output to messages of warning and error severity.
25900 - Servers support a new URL scheme for consensus downloads that
25901 allows the client to specify which authorities are trusted.
25902 The server then only sends the consensus if the client will trust
25903 it. Otherwise a 404 error is sent back. Clients use this
25904 new scheme when the server supports it (meaning it's running
25905 0.2.1.1-alpha or later). Implements proposal 134.
25906 - New configure/torrc options (--enable-geoip-stats,
25907 DirRecordUsageByCountry) to record how many IPs we've served
25908 directory info to in each country code, how many status documents
25909 total we've sent to each country code, and what share of the total
25910 directory requests we should expect to see.
25911 - Use the TLS1 hostname extension to more closely resemble browser
25913 - Lots of new unit tests.
25914 - Add a macro to implement the common pattern of iterating through
25915 two parallel lists in lockstep.
25918 Changes in version 0.2.0.28-rc - 2008-06-13
25919 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
25920 performance bug, and fixes a bunch of smaller bugs.
25923 - Fix a bug where, when we were choosing the 'end stream reason' to
25924 put in our relay end cell that we send to the exit relay, Tor
25925 clients on Windows were sometimes sending the wrong 'reason'. The
25926 anonymity problem is that exit relays may be able to guess whether
25927 the client is running Windows, thus helping partition the anonymity
25928 set. Down the road we should stop sending reasons to exit relays,
25929 or otherwise prevent future versions of this bug.
25932 - While setting up a hidden service, some valid introduction circuits
25933 were overlooked and abandoned. This might be the reason for
25934 the long delay in making a hidden service available. Bugfix on
25938 - Update to the "June 9 2008" ip-to-country file.
25939 - Run 'make test' as part of 'make dist', so we stop releasing so
25940 many development snapshots that fail their unit tests.
25943 - When we're checking if we have enough dir info for each relay
25944 to begin establishing circuits, make sure that we actually have
25945 the descriptor listed in the consensus, not just any descriptor.
25947 - Bridge relays no longer print "xx=0" in their extrainfo document
25948 for every single country code in the geoip db. Bugfix on
25950 - Only warn when we fail to load the geoip file if we were planning to
25951 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
25952 - If we change our MaxAdvertisedBandwidth and then reload torrc,
25953 Tor won't realize it should publish a new relay descriptor. Fixes
25954 bug 688, reported by mfr. Bugfix on 0.1.2.x.
25955 - When we haven't had any application requests lately, don't bother
25956 logging that we have expired a bunch of descriptors. Bugfix
25958 - Make relay cells written on a connection count as non-padding when
25959 tracking how long a connection has been in use. Bugfix on
25960 0.2.0.1-alpha. Spotted by lodger.
25961 - Fix unit tests in 0.2.0.27-rc.
25962 - Fix compile on Windows.
25965 Changes in version 0.2.0.27-rc - 2008-06-03
25966 Tor 0.2.0.27-rc adds a few features we left out of the earlier
25967 release candidates. In particular, we now include an IP-to-country
25968 GeoIP database, so controllers can easily look up what country a
25969 given relay is in, and so bridge relays can give us some sanitized
25970 summaries about which countries are making use of bridges. (See proposal
25971 126-geoip-fetching.txt for details.)
25974 - Include an IP-to-country GeoIP file in the tarball, so bridge
25975 relays can report sanitized summaries of the usage they're seeing.
25978 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
25979 Robert Hogan. Fixes the first part of bug 681.
25980 - Make bridge authorities never serve extrainfo docs.
25981 - Add support to detect Libevent versions in the 1.4.x series
25983 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
25984 - Include a new contrib/tor-exit-notice.html file that exit relay
25985 operators can put on their website to help reduce abuse queries.
25988 - When tunneling an encrypted directory connection, and its first
25989 circuit fails, do not leave it unattached and ask the controller
25990 to deal. Fixes the second part of bug 681.
25991 - Make bridge authorities correctly expire old extrainfo documents
25995 Changes in version 0.2.0.26-rc - 2008-05-13
25996 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
25997 in Debian's OpenSSL packages. All users running any 0.2.0.x version
25998 should upgrade, whether they're running Debian or not.
26000 o Major security fixes:
26001 - Use new V3 directory authority keys on the tor26, gabelmoo, and
26002 moria1 V3 directory authorities. The old keys were generated with
26003 a vulnerable version of Debian's OpenSSL package, and must be
26004 considered compromised. Other authorities' keys were not generated
26005 with an affected version of OpenSSL.
26008 - List authority signatures as "unrecognized" based on DirServer
26009 lines, not on cert cache. Bugfix on 0.2.0.x.
26012 - Add a new V3AuthUseLegacyKey option to make it easier for
26013 authorities to change their identity keys if they have to.
26016 Changes in version 0.2.0.25-rc - 2008-04-23
26017 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
26020 - Remember to initialize threading before initializing logging.
26021 Otherwise, many BSD-family implementations will crash hard on
26022 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
26025 - Authorities correctly free policies on bad servers on
26026 exit. Fixes bug 672. Bugfix on 0.2.0.x.
26029 Changes in version 0.2.0.24-rc - 2008-04-22
26030 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
26031 v3 directory authority, makes relays with dynamic IP addresses and no
26032 DirPort notice more quickly when their IP address changes, fixes a few
26033 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
26035 o New directory authorities:
26036 - Take lefkada out of the list of v3 directory authorities, since
26037 it has been down for months.
26038 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
26042 - Detect address changes more quickly on non-directory mirror
26043 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
26045 o Minor features (security):
26046 - Reject requests for reverse-dns lookup of names that are in
26047 a private address space. Patch from lodger.
26048 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
26051 o Minor bugfixes (crashes):
26052 - Avoid a rare assert that can trigger when Tor doesn't have much
26053 directory information yet and it tries to fetch a v2 hidden
26054 service descriptor. Fixes bug 651, reported by nwf.
26055 - Initialize log mutex before initializing dmalloc. Otherwise,
26056 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
26057 - Use recursive pthread mutexes in order to avoid deadlock when
26058 logging debug-level messages to a controller. Bug spotted by nwf,
26059 bugfix on 0.2.0.16-alpha.
26061 o Minor bugfixes (resource management):
26062 - Keep address policies from leaking memory: start their refcount
26063 at 1, not 2. Bugfix on 0.2.0.16-alpha.
26064 - Free authority certificates on exit, so they don't look like memory
26065 leaks. Bugfix on 0.2.0.19-alpha.
26066 - Free static hashtables for policy maps and for TLS connections on
26067 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
26068 - Avoid allocating extra space when computing consensuses on 64-bit
26069 platforms. Bug spotted by aakova.
26071 o Minor bugfixes (misc):
26072 - Do not read the configuration file when we've only been told to
26073 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
26074 based on patch from Sebastian Hahn.
26075 - Exit relays that are used as a client can now reach themselves
26076 using the .exit notation, rather than just launching an infinite
26077 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
26078 - When attempting to open a logfile fails, tell us why.
26079 - Fix a dumb bug that was preventing us from knowing that we should
26080 preemptively build circuits to handle expected directory requests.
26081 Fixes bug 660. Bugfix on 0.1.2.x.
26082 - Warn less verbosely about clock skew from netinfo cells from
26083 untrusted sources. Fixes bug 663.
26084 - Make controller stream events for DNS requests more consistent,
26085 by adding "new stream" events for DNS requests, and removing
26086 spurious "stream closed" events" for cached reverse resolves.
26087 Patch from mwenge. Fixes bug 646.
26088 - Correctly notify one-hop connections when a circuit build has
26089 failed. Possible fix for bug 669. Found by lodger.
26092 Changes in version 0.2.0.23-rc - 2008-03-24
26093 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
26094 makes bootstrapping faster if the first directory mirror you contact
26095 is down. The bundles also include the new Vidalia 0.1.2 release.
26098 - When a tunneled directory request is made to a directory server
26099 that's down, notice after 30 seconds rather than 120 seconds. Also,
26100 fail any begindir streams that are pending on it, so they can
26101 retry elsewhere. This was causing multi-minute delays on bootstrap.
26104 Changes in version 0.2.0.22-rc - 2008-03-18
26105 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
26106 enables encrypted directory connections by default for non-relays, fixes
26107 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
26108 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
26111 - Enable encrypted directory connections by default for non-relays,
26112 so censor tools that block Tor directory connections based on their
26113 plaintext patterns will no longer work. This means Tor works in
26114 certain censored countries by default again.
26117 - Make sure servers always request certificates from clients during
26118 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
26119 - Do not enter a CPU-eating loop when a connection is closed in
26120 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
26121 diagnosed by lodger; bugfix on 0.2.0.20-rc.
26122 - Fix assertion failure that could occur when a blocked circuit
26123 became unblocked, and it had pending client DNS requests. Bugfix
26124 on 0.2.0.1-alpha. Fixes bug 632.
26126 o Minor bugfixes (on 0.1.2.x):
26127 - Generate "STATUS_SERVER" events rather than misspelled
26128 "STATUS_SEVER" events. Caught by mwenge.
26129 - When counting the number of bytes written on a TLS connection,
26130 look at the BIO actually used for writing to the network, not
26131 at the BIO used (sometimes) to buffer data for the network.
26132 Looking at different BIOs could result in write counts on the
26133 order of ULONG_MAX. Fixes bug 614.
26134 - On Windows, correctly detect errors when listing the contents of
26135 a directory. Fix from lodger.
26137 o Minor bugfixes (on 0.2.0.x):
26138 - Downgrade "sslv3 alert handshake failure" message to INFO.
26139 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
26140 left BandwidthRate and BandwidthBurst at the default, we would be
26141 silently limited by those defaults. Now raise them to match the
26142 RelayBandwidth* values.
26143 - Fix the SVK version detection logic to work correctly on a branch.
26144 - Make --enable-openbsd-malloc work correctly on Linux with alpha
26145 CPUs. Fixes bug 625.
26146 - Logging functions now check that the passed severity is sane.
26147 - Use proper log levels in the testsuite call of
26148 get_interface_address6().
26149 - When using a nonstandard malloc, do not use the platform values for
26150 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
26151 - Make the openbsd malloc code use 8k pages on alpha CPUs and
26153 - Detect mismatched page sizes when using --enable-openbsd-malloc.
26154 - Avoid double-marked-for-close warning when certain kinds of invalid
26155 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
26156 for bug 617. Bugfix on 0.2.0.1-alpha.
26157 - Make sure that the "NULL-means-reject *:*" convention is followed by
26158 all the policy manipulation functions, avoiding some possible crash
26159 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
26160 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
26161 actually works, and doesn't warn about every single reverse lookup.
26162 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
26165 - Only log guard node status when guard node status has changed.
26166 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
26167 make "INFO" 75% less verbose.
26170 Changes in version 0.2.0.21-rc - 2008-03-02
26171 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
26172 makes Tor work well with Vidalia again, fixes a rare assert bug,
26173 and fixes a pair of more minor bugs. The bundles also include Vidalia
26174 0.1.0 and Torbutton 1.1.16.
26177 - The control port should declare that it requires password auth
26178 when HashedControlSessionPassword is set too. Patch from Matt Edman;
26179 bugfix on 0.2.0.20-rc. Fixes bug 615.
26180 - Downgrade assert in connection_buckets_decrement() to a log message.
26181 This may help us solve bug 614, and in any case will make its
26182 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
26183 - We were sometimes miscounting the number of bytes read from the
26184 network, causing our rate limiting to not be followed exactly.
26185 Bugfix on 0.2.0.16-alpha. Reported by lodger.
26188 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
26189 OpenSSL versions should have been working fine. Diagnosis and patch
26190 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
26191 Bugfix on 0.2.0.20-rc.
26194 Changes in version 0.2.0.20-rc - 2008-02-24
26195 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
26196 makes more progress towards normalizing Tor's TLS handshake, makes
26197 hidden services work better again, helps relays bootstrap if they don't
26198 know their IP address, adds optional support for linking in openbsd's
26199 allocator or tcmalloc, allows really fast relays to scale past 15000
26200 sockets, and fixes a bunch of minor bugs reported by Veracode.
26203 - Enable the revised TLS handshake based on the one designed by
26204 Steven Murdoch in proposal 124, as revised in proposal 130. It
26205 includes version negotiation for OR connections as described in
26206 proposal 105. The new handshake is meant to be harder for censors
26207 to fingerprint, and it adds the ability to detect certain kinds of
26208 man-in-the-middle traffic analysis attacks. The version negotiation
26209 feature will allow us to improve Tor's link protocol more safely
26211 - Choose which bridge to use proportional to its advertised bandwidth,
26212 rather than uniformly at random. This should speed up Tor for
26213 bridge users. Also do this for people who set StrictEntryNodes.
26214 - When a TrackHostExits-chosen exit fails too many times in a row,
26215 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
26218 - Resolved problems with (re-)fetching hidden service descriptors.
26219 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
26220 and 0.2.0.19-alpha.
26221 - If we only ever used Tor for hidden service lookups or posts, we
26222 would stop building circuits and start refusing connections after
26223 24 hours, since we falsely believed that Tor was dormant. Reported
26224 by nwf; bugfix on 0.1.2.x.
26225 - Servers that don't know their own IP address should go to the
26226 authorities for their first directory fetch, even if their DirPort
26227 is off or if they don't know they're reachable yet. This will help
26228 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
26229 - When counting the number of open sockets, count not only the number
26230 of sockets we have received from the socket() call, but also
26231 the number we've gotten from accept() and socketpair(). This bug
26232 made us fail to count all sockets that we were using for incoming
26233 connections. Bugfix on 0.2.0.x.
26234 - Fix code used to find strings within buffers, when those strings
26235 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
26236 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
26237 - Add a new __HashedControlSessionPassword option for controllers
26238 to use for one-off session password hashes that shouldn't get
26239 saved to disk by SAVECONF --- Vidalia users were accumulating a
26240 pile of HashedControlPassword lines in their torrc files, one for
26241 each time they had restarted Tor and then clicked Save. Make Tor
26242 automatically convert "HashedControlPassword" to this new option but
26243 only when it's given on the command line. Partial fix for bug 586.
26245 o Minor features (performance):
26246 - Tune parameters for cell pool allocation to minimize amount of
26248 - Add OpenBSD malloc code from phk as an optional malloc
26249 replacement on Linux: some glibc libraries do very poorly
26250 with Tor's memory allocation patterns. Pass
26251 --enable-openbsd-malloc to get the replacement malloc code.
26252 - Add a --with-tcmalloc option to the configure script to link
26253 against tcmalloc (if present). Does not yet search for
26254 non-system include paths.
26255 - Stop imposing an arbitrary maximum on the number of file descriptors
26256 used for busy servers. Bug reported by Olaf Selke; patch from
26259 o Minor features (other):
26260 - When SafeLogging is disabled, log addresses along with all TLS
26262 - When building with --enable-gcc-warnings, check for whether Apple's
26263 warning "-Wshorten-64-to-32" is available.
26264 - Add a --passphrase-fd argument to the tor-gencert command for
26267 o Minor bugfixes (memory leaks and code problems):
26268 - We were leaking a file descriptor if Tor started with a zero-length
26269 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
26270 - Detect size overflow in zlib code. Reported by Justin Ferguson and
26272 - We were comparing the raw BridgePassword entry with a base64'ed
26273 version of it, when handling a "/tor/networkstatus-bridges"
26274 directory request. Now compare correctly. Noticed by Veracode.
26275 - Recover from bad tracked-since value in MTBF-history file.
26276 Should fix bug 537.
26277 - Alter the code that tries to recover from unhandled write
26278 errors, to not try to flush onto a socket that's given us
26279 unhandled errors. Bugfix on 0.1.2.x.
26280 - Make Unix controlsockets work correctly on OpenBSD. Patch from
26281 tup. Bugfix on 0.2.0.3-alpha.
26283 o Minor bugfixes (other):
26284 - If we have an extra-info document for our server, always make
26285 it available on the control port, even if we haven't gotten
26286 a copy of it from an authority yet. Patch from mwenge.
26287 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
26288 - Directory mirrors no longer include a guess at the client's IP
26289 address if the connection appears to be coming from the same /24
26290 network; it was producing too many wrong guesses.
26291 - Make the new hidden service code respect the SafeLogging setting.
26292 Bugfix on 0.2.0.x. Patch from Karsten.
26293 - When starting as an authority, do not overwrite all certificates
26294 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
26295 - If we're trying to flush the last bytes on a connection (for
26296 example, when answering a directory request), reset the
26297 time-to-give-up timeout every time we manage to write something
26298 on the socket. Bugfix on 0.1.2.x.
26299 - Change the behavior of "getinfo status/good-server-descriptor"
26300 so it doesn't return failure when any authority disappears.
26301 - Even though the man page said that "TrackHostExits ." should
26302 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
26303 - Report TLS "zero return" case as a "clean close" and "IO error"
26304 as a "close". Stop calling closes "unexpected closes": existing
26305 Tors don't use SSL_close(), so having a connection close without
26306 the TLS shutdown handshake is hardly unexpected.
26307 - Send NAMESERVER_STATUS messages for a single failed nameserver
26310 o Code simplifications and refactoring:
26311 - Remove the tor_strpartition function: its logic was confused,
26312 and it was only used for one thing that could be implemented far
26316 Changes in version 0.2.0.19-alpha - 2008-02-09
26317 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
26318 handshake, makes path selection for relays more secure and IP address
26319 guessing more robust, and generally fixes a lot of bugs in preparation
26320 for calling the 0.2.0 branch stable.
26323 - Do not include recognizeable strings in the commonname part of
26324 Tor's x509 certificates.
26327 - If we're a relay, avoid picking ourselves as an introduction point,
26328 a rendezvous point, or as the final hop for internal circuits. Bug
26329 reported by taranis and lodger. Bugfix on 0.1.2.x.
26330 - Patch from "Andrew S. Lists" to catch when we contact a directory
26331 mirror at IP address X and he says we look like we're coming from
26332 IP address X. Bugfix on 0.1.2.x.
26334 o Minor features (security):
26335 - Be more paranoid about overwriting sensitive memory on free(),
26336 as a defensive programming tactic to ensure forward secrecy.
26338 o Minor features (directory authority):
26339 - Actually validate the options passed to AuthDirReject,
26340 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
26341 - Reject router descriptors with out-of-range bandwidthcapacity or
26342 bandwidthburst values.
26344 o Minor features (controller):
26345 - Reject controller commands over 1MB in length. This keeps rogue
26346 processes from running us out of memory.
26348 o Minor features (misc):
26349 - Give more descriptive well-formedness errors for out-of-range
26350 hidden service descriptor/protocol versions.
26351 - Make memory debugging information describe more about history
26352 of cell allocation, so we can help reduce our memory use.
26354 o Deprecated features (controller):
26355 - The status/version/num-versioning and status/version/num-concurring
26356 GETINFO options are no longer useful in the v3 directory protocol:
26357 treat them as deprecated, and warn when they're used.
26360 - When our consensus networkstatus has been expired for a while, stop
26361 being willing to build circuits using it. Fixes bug 401. Bugfix
26363 - Directory caches now fetch certificates from all authorities
26364 listed in a networkstatus consensus, even when they do not
26365 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
26366 - When connecting to a bridge without specifying its key, insert
26367 the connection into the identity-to-connection map as soon as
26368 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
26369 - Detect versions of OS X where malloc_good_size() is present in the
26370 library but never actually declared. Resolves bug 587. Bugfix
26372 - Stop incorrectly truncating zlib responses to directory authority
26373 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
26374 - Stop recommending that every server operator send mail to tor-ops.
26375 Resolves bug 597. Bugfix on 0.1.2.x.
26376 - Don't trigger an assert if we start a directory authority with a
26377 private IP address (like 127.0.0.1).
26378 - Avoid possible failures when generating a directory with routers
26379 with over-long versions strings, or too many flags set. Bugfix
26381 - If an attempt to launch a DNS resolve request over the control
26382 port fails because we have overrun the limit on the number of
26383 connections, tell the controller that the request has failed.
26384 - Avoid using too little bandwidth when our clock skips a few
26385 seconds. Bugfix on 0.1.2.x.
26386 - Fix shell error when warning about missing packages in configure
26387 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
26388 - Do not become confused when receiving a spurious VERSIONS-like
26389 cell from a confused v1 client. Bugfix on 0.2.0.x.
26390 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
26391 introduction points for a hidden service have failed. Patch from
26392 Karsten Loesing. Bugfix on 0.2.0.x.
26394 o Code simplifications and refactoring:
26395 - Remove some needless generality from cpuworker code, for improved
26397 - Stop overloading the circuit_t.onionskin field for both "onionskin
26398 from a CREATE cell that we are waiting for a cpuworker to be
26399 assigned" and "onionskin from an EXTEND cell that we are going to
26400 send to an OR as soon as we are connected". Might help with bug 600.
26401 - Add an in-place version of aes_crypt() so that we can avoid doing a
26402 needless memcpy() call on each cell payload.
26405 Changes in version 0.2.0.18-alpha - 2008-01-25
26406 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
26407 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
26408 that can warn or reject connections to ports generally associated with
26409 vulnerable-plaintext protocols.
26411 o New directory authorities:
26412 - Set up dannenberg (run by CCC) as the sixth v3 directory
26416 - Fix a major memory leak when attempting to use the v2 TLS
26417 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
26418 - We accidentally enabled the under-development v2 TLS handshake
26419 code, which was causing log entries like "TLS error while
26420 renegotiating handshake". Disable it again. Resolves bug 590.
26421 - We were computing the wrong Content-Length: header for directory
26422 responses that need to be compressed on the fly, causing clients
26423 asking for those items to always fail. Bugfix on 0.2.0.x; partially
26427 - Avoid going directly to the directory authorities even if you're a
26428 relay, if you haven't found yourself reachable yet or if you've
26429 decided not to advertise your dirport yet. Addresses bug 556.
26430 - If we've gone 12 hours since our last bandwidth check, and we
26431 estimate we have less than 50KB bandwidth capacity but we could
26432 handle more, do another bandwidth test.
26433 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
26434 Tor can warn and/or refuse connections to ports commonly used with
26435 vulnerable-plaintext protocols. Currently we warn on ports 23,
26436 109, 110, and 143, but we don't reject any.
26439 - When we setconf ClientOnly to 1, close any current OR and Dir
26440 listeners. Reported by mwenge.
26441 - When we get a consensus that's been signed by more people than
26442 we expect, don't log about it; it's not a big deal. Reported
26446 - Don't answer "/tor/networkstatus-bridges" directory requests if
26447 the request isn't encrypted.
26448 - Make "ClientOnly 1" config option disable directory ports too.
26449 - Patches from Karsten Loesing to make v2 hidden services more
26450 robust: work even when there aren't enough HSDir relays available;
26451 retry when a v2 rend desc fetch fails; but don't retry if we
26452 already have a usable v0 rend desc.
26455 Changes in version 0.2.0.17-alpha - 2008-01-17
26456 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
26459 - Make the tor-gencert man page get included correctly in the tarball.
26462 Changes in version 0.2.0.16-alpha - 2008-01-17
26463 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
26464 Loesing, and generally cleans up a lot of features and minor bugs.
26466 o New directory authorities:
26467 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
26470 o Major performance improvements:
26471 - Switch our old ring buffer implementation for one more like that
26472 used by free Unix kernels. The wasted space in a buffer with 1mb
26473 of data will now be more like 8k than 1mb. The new implementation
26474 also avoids realloc();realloc(); patterns that can contribute to
26475 memory fragmentation.
26478 - Configuration files now accept C-style strings as values. This
26479 helps encode characters not allowed in the current configuration
26480 file format, such as newline or #. Addresses bug 557.
26481 - Although we fixed bug 539 (where servers would send HTTP status 503
26482 responses _and_ send a body too), there are still servers out
26483 there that haven't upgraded. Therefore, make clients parse such
26484 bodies when they receive them.
26485 - When we're not serving v2 directory information, there is no reason
26486 to actually keep any around. Remove the obsolete files and directory
26487 on startup if they are very old and we aren't going to serve them.
26489 o Minor performance improvements:
26490 - Reference-count and share copies of address policy entries; only 5%
26491 of them were actually distinct.
26492 - Never walk through the list of logs if we know that no log is
26493 interested in a given message.
26496 - When an authority has not signed a consensus, do not try to
26497 download a nonexistent "certificate with key 00000000". Bugfix
26498 on 0.2.0.x. Fixes bug 569.
26499 - Fix a rare assert error when we're closing one of our threads:
26500 use a mutex to protect the list of logs, so we never write to the
26501 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
26502 bug 575, which is kind of the revenge of bug 222.
26503 - Patch from Karsten Loesing to complain less at both the client
26504 and the relay when a relay used to have the HSDir flag but doesn't
26505 anymore, and we try to upload a hidden service descriptor.
26506 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
26508 - Do not try to download missing certificates until we have tried
26509 to check our fallback consensus. Fixes bug 583.
26510 - Make bridges round reported GeoIP stats info up to the nearest
26511 estimate, not down. Now we can distinguish between "0 people from
26512 this country" and "1 person from this country".
26513 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
26514 - Avoid possible segfault if key generation fails in
26515 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
26516 - Avoid segfault in the case where a badly behaved v2 versioning
26517 directory sends a signed networkstatus with missing client-versions.
26519 - Avoid segfaults on certain complex invocations of
26520 router_get_by_hexdigest(). Bugfix on 0.1.2.
26521 - Correct bad index on array access in parse_http_time(). Bugfix
26523 - Fix possible bug in vote generation when server versions are present
26524 but client versions are not.
26525 - Fix rare bug on REDIRECTSTREAM control command when called with no
26526 port set: it could erroneously report an error when none had
26528 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
26529 compressing large objects and find ourselves with more than 4k
26530 left over. Bugfix on 0.2.0.
26531 - Fix a small memory leak when setting up a hidden service.
26532 - Fix a few memory leaks that could in theory happen under bizarre
26534 - Fix an assert if we post a general-purpose descriptor via the
26535 control port but that descriptor isn't mentioned in our current
26536 network consensus. Bug reported by Jon McLachlan; bugfix on
26539 o Minor features (controller):
26540 - Get NS events working again. Patch from tup.
26541 - The GETCONF command now escapes and quotes configuration values
26542 that don't otherwise fit into the torrc file.
26543 - The SETCONF command now handles quoted values correctly.
26545 o Minor features (directory authorities):
26546 - New configuration options to override default maximum number of
26547 servers allowed on a single IP address. This is important for
26548 running a test network on a single host.
26549 - Actually implement the -s option to tor-gencert.
26550 - Add a manual page for tor-gencert.
26552 o Minor features (bridges):
26553 - Bridge authorities no longer serve bridge descriptors over
26554 unencrypted connections.
26556 o Minor features (other):
26557 - Add hidden services and DNSPorts to the list of things that make
26558 Tor accept that it has running ports. Change starting Tor with no
26559 ports from a fatal error to a warning; we might change it back if
26560 this turns out to confuse anybody. Fixes bug 579.
26563 Changes in version 0.1.2.19 - 2008-01-17
26564 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26565 exit policy a little bit more conservative so it's safer to run an
26566 exit relay on a home system, and fixes a variety of smaller issues.
26569 - Exit policies now reject connections that are addressed to a
26570 relay's public (external) IP address too, unless
26571 ExitPolicyRejectPrivate is turned off. We do this because too
26572 many relays are running nearby to services that trust them based
26573 on network address.
26576 - When the clock jumps forward a lot, do not allow the bandwidth
26577 buckets to become negative. Fixes bug 544.
26578 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26579 on every successful resolve. Reported by Mike Perry.
26580 - Purge old entries from the "rephist" database and the hidden
26581 service descriptor database even when DirPort is zero.
26582 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26583 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26584 crashing or mis-answering these requests.
26585 - When we decide to send a 503 response to a request for servers, do
26586 not then also send the server descriptors: this defeats the whole
26587 purpose. Fixes bug 539.
26590 - Changing the ExitPolicyRejectPrivate setting should cause us to
26591 rebuild our server descriptor.
26592 - Fix handling of hex nicknames when answering controller requests for
26593 networkstatus by name, or when deciding whether to warn about
26594 unknown routers in a config option. (Patch from mwenge.)
26595 - Fix a couple of hard-to-trigger autoconf problems that could result
26596 in really weird results on platforms whose sys/types.h files define
26597 nonstandard integer types.
26598 - Don't try to create the datadir when running --verify-config or
26599 --hash-password. Resolves bug 540.
26600 - If we were having problems getting a particular descriptor from the
26601 directory caches, and then we learned about a new descriptor for
26602 that router, we weren't resetting our failure count. Reported
26604 - Although we fixed bug 539 (where servers would send HTTP status 503
26605 responses _and_ send a body too), there are still servers out there
26606 that haven't upgraded. Therefore, make clients parse such bodies
26607 when they receive them.
26608 - Run correctly on systems where rlim_t is larger than unsigned long.
26609 This includes some 64-bit systems.
26610 - Run correctly on platforms (like some versions of OS X 10.5) where
26611 the real limit for number of open files is OPEN_FILES, not rlim_max
26612 from getrlimit(RLIMIT_NOFILES).
26613 - Avoid a spurious free on base64 failure.
26614 - Avoid segfaults on certain complex invocations of
26615 router_get_by_hexdigest().
26616 - Fix rare bug on REDIRECTSTREAM control command when called with no
26617 port set: it could erroneously report an error when none had
26621 Changes in version 0.2.0.15-alpha - 2007-12-25
26622 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26623 features added in 0.2.0.13-alpha.
26626 - Fix several remotely triggerable asserts based on DirPort requests
26627 for a v2 or v3 networkstatus object before we were prepared. This
26628 was particularly bad for 0.2.0.13 and later bridge relays, who
26629 would never have a v2 networkstatus and would thus always crash
26630 when used. Bugfixes on 0.2.0.x.
26631 - Estimate the v3 networkstatus size more accurately, rather than
26632 estimating it at zero bytes and giving it artificially high priority
26633 compared to other directory requests. Bugfix on 0.2.0.x.
26636 - Fix configure.in logic for cross-compilation.
26637 - When we load a bridge descriptor from the cache, and it was
26638 previously unreachable, mark it as retriable so we won't just
26639 ignore it. Also, try fetching a new copy immediately. Bugfixes
26641 - The bridge GeoIP stats were counting other relays, for example
26642 self-reachability and authority-reachability tests.
26645 - Support compilation to target iPhone; patch from cjacker huang.
26646 To build for iPhone, pass the --enable-iphone option to configure.
26649 Changes in version 0.2.0.14-alpha - 2007-12-23
26651 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26652 without a datadirectory from a previous Tor install. Reported
26654 - Fix a crash when we fetch a descriptor that turns out to be
26655 unexpected (it used to be in our networkstatus when we started
26656 fetching it, but it isn't in our current networkstatus), and we
26657 aren't using bridges. Bugfix on 0.2.0.x.
26658 - Fix a crash when accessing hidden services: it would work the first
26659 time you use a given introduction point for your service, but
26660 on subsequent requests we'd be using garbage memory. Fixed by
26661 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26662 - Fix a crash when we load a bridge descriptor from disk but we don't
26663 currently have a Bridge line for it in our torrc. Bugfix on
26667 - If bridge authorities set BridgePassword, they will serve a
26668 snapshot of known bridge routerstatuses from their DirPort to
26669 anybody who knows that password. Unset by default.
26672 - Make the unit tests build again.
26673 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26674 - Make PublishServerDescriptor default to 1, so the default doesn't
26675 have to change as we invent new directory protocol versions.
26676 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26677 be included unless sys/time.h is already included. Fixes
26678 bug 553. Bugfix on 0.2.0.x.
26679 - If we receive a general-purpose descriptor and then receive an
26680 identical bridge-purpose descriptor soon after, don't discard
26681 the next one as a duplicate.
26684 - If BridgeRelay is set to 1, then the default for
26685 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26686 - If the user sets RelayBandwidthRate but doesn't set
26687 RelayBandwidthBurst, then make them equal rather than erroring out.
26690 Changes in version 0.2.0.13-alpha - 2007-12-21
26691 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26692 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26695 o New directory authorities:
26696 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26700 - Only update guard status (usable / not usable) once we have
26701 enough directory information. This was causing us to always pick
26702 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26703 causing us to discard all our guards on startup if we hadn't been
26704 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26705 - Purge old entries from the "rephist" database and the hidden
26706 service descriptor databases even when DirPort is zero. Bugfix
26708 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26709 after opening a circuit -- even a relayed circuit. Bugfix on
26711 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26712 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26713 crashing or mis-answering these types of requests.
26714 - Relays were publishing their server descriptor to v1 and v2
26715 directory authorities, but they didn't try publishing to v3-only
26716 authorities. Fix this; and also stop publishing to v1 authorities.
26718 - When we were reading router descriptors from cache, we were ignoring
26719 the annotations -- so for example we were reading in bridge-purpose
26720 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26721 - When we decided to send a 503 response to a request for servers, we
26722 were then also sending the server descriptors: this defeats the
26723 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26726 - Bridge relays now behave like clients with respect to time
26727 intervals for downloading new consensus documents -- otherwise they
26728 stand out. Bridge users now wait until the end of the interval,
26729 so their bridge relay will be sure to have a new consensus document.
26730 - Three new config options (AlternateDirAuthority,
26731 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26732 user selectively replace the default directory authorities by type,
26733 rather than the all-or-nothing replacement that DirServer offers.
26734 - Tor can now be configured to read a GeoIP file from disk in one
26735 of two formats. This can be used by controllers to map IP addresses
26736 to countries. Eventually, it may support exit-by-country.
26737 - When possible, bridge relays remember which countries users
26738 are coming from, and report aggregate information in their
26739 extra-info documents, so that the bridge authorities can learn
26740 where Tor is blocked.
26741 - Bridge directory authorities now do reachability testing on the
26742 bridges they know. They provide router status summaries to the
26743 controller via "getinfo ns/purpose/bridge", and also dump summaries
26744 to a file periodically.
26745 - Stop fetching directory info so aggressively if your DirPort is
26746 on but your ORPort is off; stop fetching v2 dir info entirely.
26747 You can override these choices with the new FetchDirInfoEarly
26751 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
26752 consensus documents when there are too many relays at a single
26753 IP address. Now clear it in v2 network status documents too, and
26754 also clear it in routerinfo_t when the relay is no longer listed
26755 in the relevant networkstatus document.
26756 - Don't crash if we get an unexpected value for the
26757 PublishServerDescriptor config option. Reported by Matt Edman;
26758 bugfix on 0.2.0.9-alpha.
26759 - Our new v2 hidden service descriptor format allows descriptors
26760 that have no introduction points. But Tor crashed when we tried
26761 to build a descriptor with no intro points (and it would have
26762 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
26763 by Karsten Loesing.
26764 - Fix building with dmalloc 5.5.2 with glibc.
26765 - Reject uploaded descriptors and extrainfo documents if they're
26766 huge. Otherwise we'll cache them all over the network and it'll
26767 clog everything up. Reported by Aljosha Judmayer.
26768 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
26769 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
26770 - When the DANGEROUS_VERSION controller status event told us we're
26771 running an obsolete version, it used the string "OLD" to describe
26772 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
26773 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
26774 - If we can't expand our list of entry guards (e.g. because we're
26775 using bridges or we have StrictEntryNodes set), don't mark relays
26776 down when they fail a directory request. Otherwise we're too quick
26777 to mark all our entry points down. Bugfix on 0.1.2.x.
26778 - Fix handling of hex nicknames when answering controller requests for
26779 networkstatus by name, or when deciding whether to warn about unknown
26780 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
26781 - Fix a couple of hard-to-trigger autoconf problems that could result
26782 in really weird results on platforms whose sys/types.h files define
26783 nonstandard integer types. Bugfix on 0.1.2.x.
26784 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
26785 - Don't crash on name lookup when we have no current consensus. Fixes
26786 bug 538; bugfix on 0.2.0.x.
26787 - Only Tors that want to mirror the v2 directory info should
26788 create the "cached-status" directory in their datadir. (All Tors
26789 used to create it.) Bugfix on 0.2.0.9-alpha.
26790 - Directory authorities should only automatically download Extra Info
26791 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
26794 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
26795 consumers. (We already do this on HUP.)
26796 - Authorities and caches fetch the v2 networkstatus documents
26797 less often, now that v3 is encouraged.
26798 - Add a new config option BridgeRelay that specifies you want to
26799 be a bridge relay. Right now the only difference is that it makes
26800 you answer begin_dir requests, and it makes you cache dir info,
26801 even if your DirPort isn't on.
26802 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
26803 ask about source, timestamp of arrival, purpose, etc. We need
26804 something like this to help Vidalia not do GeoIP lookups on bridge
26806 - Allow multiple HashedControlPassword config lines, to support
26807 multiple controller passwords.
26808 - Authorities now decide whether they're authoritative for a given
26809 router based on the router's purpose.
26810 - New config options AuthDirBadDir and AuthDirListBadDirs for
26811 authorities to mark certain relays as "bad directories" in the
26812 networkstatus documents. Also supports the "!baddir" directive in
26813 the approved-routers file.
26816 Changes in version 0.2.0.12-alpha - 2007-11-16
26817 This twelfth development snapshot fixes some more build problems as
26818 well as a few minor bugs.
26821 - Make it build on OpenBSD again. Patch from tup.
26822 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
26823 package-building for Red Hat, OS X, etc.
26825 o Minor bugfixes (on 0.1.2.x):
26826 - Changing the ExitPolicyRejectPrivate setting should cause us to
26827 rebuild our server descriptor.
26829 o Minor bugfixes (on 0.2.0.x):
26830 - When we're lacking a consensus, don't try to perform rendezvous
26831 operations. Reported by Karsten Loesing.
26832 - Fix a small memory leak whenever we decide against using a
26833 newly picked entry guard. Reported by Mike Perry.
26834 - When authorities detected more than two relays running on the same
26835 IP address, they were clearing all the status flags but forgetting
26836 to clear the "hsdir" flag. So clients were being told that a
26837 given relay was the right choice for a v2 hsdir lookup, yet they
26838 never had its descriptor because it was marked as 'not running'
26840 - If we're trying to fetch a bridge descriptor and there's no way
26841 the bridge authority could help us (for example, we don't know
26842 a digest, or there is no bridge authority), don't be so eager to
26843 fall back to asking the bridge authority.
26844 - If we're using bridges or have strictentrynodes set, and our
26845 chosen exit is in the same family as all our bridges/entry guards,
26846 then be flexible about families.
26849 - When we negotiate a v2 link-layer connection (not yet implemented),
26850 accept RELAY_EARLY cells and turn them into RELAY cells if we've
26851 negotiated a v1 connection for their next step. Initial code for
26855 Changes in version 0.2.0.11-alpha - 2007-11-12
26856 This eleventh development snapshot fixes some build problems with
26857 the previous snapshot. It also includes a more secure-by-default exit
26858 policy for relays, fixes an enormous memory leak for exit relays, and
26859 fixes another bug where servers were falling out of the directory list.
26862 - Exit policies now reject connections that are addressed to a
26863 relay's public (external) IP address too, unless
26864 ExitPolicyRejectPrivate is turned off. We do this because too
26865 many relays are running nearby to services that trust them based
26866 on network address. Bugfix on 0.1.2.x.
26869 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26870 on every successful resolve. Reported by Mike Perry; bugfix
26872 - On authorities, never downgrade to old router descriptors simply
26873 because they're listed in the consensus. This created a catch-22
26874 where we wouldn't list a new descriptor because there was an
26875 old one in the consensus, and we couldn't get the new one in the
26876 consensus because we wouldn't list it. Possible fix for bug 548.
26877 Also, this might cause bug 543 to appear on authorities; if so,
26878 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
26880 o Packaging fixes on 0.2.0.10-alpha:
26881 - We were including instructions about what to do with the
26882 src/config/fallback-consensus file, but we weren't actually
26883 including it in the tarball. Disable all of that for now.
26886 - Allow people to say PreferTunnelledDirConns rather than
26887 PreferTunneledDirConns, for those alternate-spellers out there.
26890 - Don't reevaluate all the information from our consensus document
26891 just because we've downloaded a v2 networkstatus that we intend
26892 to cache. Fixes bug 545; bugfix on 0.2.0.x.
26895 Changes in version 0.2.0.10-alpha - 2007-11-10
26896 This tenth development snapshot adds a third v3 directory authority
26897 run by Mike Perry, adds most of Karsten Loesing's new hidden service
26898 descriptor format, fixes a bad crash bug and new bridge bugs introduced
26899 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
26900 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
26901 addresses many more minor issues.
26903 o New directory authorities:
26904 - Set up ides (run by Mike Perry) as the third v3 directory authority.
26907 - Allow tunnelled directory connections to ask for an encrypted
26908 "begin_dir" connection or an anonymized "uses a full Tor circuit"
26909 connection independently. Now we can make anonymized begin_dir
26910 connections for (e.g.) more secure hidden service posting and
26912 - More progress on proposal 114: code from Karsten Loesing to
26913 implement new hidden service descriptor format.
26914 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
26915 accommodate the growing number of servers that use the default
26916 and are reaching it.
26917 - Directory authorities use a new formula for selecting which nodes
26918 to advertise as Guards: they must be in the top 7/8 in terms of
26919 how long we have known about them, and above the median of those
26920 nodes in terms of weighted fractional uptime.
26921 - Make "not enough dir info yet" warnings describe *why* Tor feels
26922 it doesn't have enough directory info yet.
26925 - Stop servers from crashing if they set a Family option (or
26926 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
26928 - Make bridge users work again -- the move to v3 directories in
26929 0.2.0.9-alpha had introduced a number of bugs that made bridges
26930 no longer work for clients.
26931 - When the clock jumps forward a lot, do not allow the bandwidth
26932 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
26934 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
26935 - When the consensus lists a router descriptor that we previously were
26936 mirroring, but that we considered non-canonical, reload the
26937 descriptor as canonical. This fixes bug 543 where Tor servers
26938 would start complaining after a few days that they don't have
26939 enough directory information to build a circuit.
26940 - Consider replacing the current consensus when certificates arrive
26941 that make the pending consensus valid. Previously, we were only
26942 considering replacement when the new certs _didn't_ help.
26943 - Fix an assert error on startup if we didn't already have the
26944 consensus and certs cached in our datadirectory: we were caching
26945 the consensus in consensus_waiting_for_certs but then free'ing it
26947 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
26948 Request) if we need more v3 certs but we've already got pending
26949 requests for all of them.
26950 - Correctly back off from failing certificate downloads. Fixes
26952 - Authorities don't vote on the Running flag if they have been running
26953 for less than 30 minutes themselves. Fixes bug 547, where a newly
26954 started authority would vote that everyone was down.
26956 o New requirements:
26957 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
26958 it, it had no AES, and it hasn't seen any security patches since
26962 - Clients now hold circuitless TLS connections open for 1.5 times
26963 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
26964 rebuild a new circuit over them within that timeframe. Previously,
26965 they held them open only for KeepalivePeriod (5 minutes).
26966 - Use "If-Modified-Since" to avoid retrieving consensus
26967 networkstatuses that we already have.
26968 - When we have no consensus, check FallbackNetworkstatusFile (defaults
26969 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
26970 we start knowing some directory caches.
26971 - When we receive a consensus from the future, warn about skew.
26972 - Improve skew reporting: try to give the user a better log message
26973 about how skewed they are, and how much this matters.
26974 - When we have a certificate for an authority, believe that
26975 certificate's claims about the authority's IP address.
26976 - New --quiet command-line option to suppress the default console log.
26977 Good in combination with --hash-password.
26978 - Authorities send back an X-Descriptor-Not-New header in response to
26979 an accepted-but-discarded descriptor upload. Partially implements
26981 - Make the log message for "tls error. breaking." more useful.
26982 - Better log messages about certificate downloads, to attempt to
26983 track down the second incarnation of bug 546.
26985 o Minor features (bridges):
26986 - If bridge users set UpdateBridgesFromAuthority, but the digest
26987 they ask for is a 404 from the bridge authority, they now fall
26988 back to trying the bridge directly.
26989 - Bridges now use begin_dir to publish their server descriptor to
26990 the bridge authority, even when they haven't set TunnelDirConns.
26992 o Minor features (controller):
26993 - When reporting clock skew, and we know that the clock is _at least
26994 as skewed_ as some value, but we don't know the actual value,
26995 report the value as a "minimum skew."
26998 - Update linux-tor-prio.sh script to allow QoS based on the uid of
26999 the Tor process. Patch from Marco Bonetti with tweaks from Mike
27003 - Refuse to start if both ORPort and UseBridges are set. Bugfix
27004 on 0.2.0.x, suggested by Matt Edman.
27005 - Don't stop fetching descriptors when FetchUselessDescriptors is
27006 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
27007 reported by tup and ioerror.
27008 - Better log message on vote from unknown authority.
27009 - Don't log "Launching 0 request for 0 router" message.
27011 o Minor bugfixes (memory leaks):
27012 - Stop leaking memory every time we parse a v3 certificate. Bugfix
27014 - Stop leaking memory every time we load a v3 certificate. Bugfix
27015 on 0.2.0.1-alpha. Fixes bug 536.
27016 - Stop leaking a cached networkstatus on exit. Bugfix on
27018 - Stop leaking voter information every time we free a consensus.
27019 Bugfix on 0.2.0.3-alpha.
27020 - Stop leaking signed data every time we check a voter signature.
27021 Bugfix on 0.2.0.3-alpha.
27022 - Stop leaking a signature every time we fail to parse a consensus or
27023 a vote. Bugfix on 0.2.0.3-alpha.
27024 - Stop leaking v2_download_status_map on shutdown. Bugfix on
27026 - Stop leaking conn->nickname every time we make a connection to a
27027 Tor relay without knowing its expected identity digest (e.g. when
27028 using bridges). Bugfix on 0.2.0.3-alpha.
27030 - Minor bugfixes (portability):
27031 - Run correctly on platforms where rlim_t is larger than unsigned
27032 long, and/or where the real limit for number of open files is
27033 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
27034 particular, these may be needed for OS X 10.5.
27037 Changes in version 0.1.2.18 - 2007-10-28
27038 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
27039 hidden service introduction that were causing huge delays, and a big
27040 bug that was causing some servers to disappear from the network status
27041 lists for a few hours each day.
27043 o Major bugfixes (crashes):
27044 - If a connection is shut down abruptly because of something that
27045 happened inside connection_flushed_some(), do not call
27046 connection_finished_flushing(). Should fix bug 451:
27047 "connection_stop_writing: Assertion conn->write_event failed"
27048 Bugfix on 0.1.2.7-alpha.
27049 - Fix possible segfaults in functions called from
27050 rend_process_relay_cell().
27052 o Major bugfixes (hidden services):
27053 - Hidden services were choosing introduction points uniquely by
27054 hexdigest, but when constructing the hidden service descriptor
27055 they merely wrote the (potentially ambiguous) nickname.
27056 - Clients now use the v2 intro format for hidden service
27057 connections: they specify their chosen rendezvous point by identity
27058 digest rather than by (potentially ambiguous) nickname. These
27059 changes could speed up hidden service connections dramatically.
27061 o Major bugfixes (other):
27062 - Stop publishing a new server descriptor just because we get a
27063 HUP signal. This led (in a roundabout way) to some servers getting
27064 dropped from the networkstatus lists for a few hours each day.
27065 - When looking for a circuit to cannibalize, consider family as well
27066 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27067 circuit cannibalization).
27068 - When a router wasn't listed in a new networkstatus, we were leaving
27069 the flags for that router alone -- meaning it remained Named,
27070 Running, etc -- even though absence from the networkstatus means
27071 that it shouldn't be considered to exist at all anymore. Now we
27072 clear all the flags for routers that fall out of the networkstatus
27073 consensus. Fixes bug 529.
27076 - Don't try to access (or alter) the state file when running
27077 --list-fingerprint or --verify-config or --hash-password. Resolves
27079 - When generating information telling us how to extend to a given
27080 router, do not try to include the nickname if it is
27081 absent. Resolves bug 467.
27082 - Fix a user-triggerable segfault in expand_filename(). (There isn't
27083 a way to trigger this remotely.)
27084 - When sending a status event to the controller telling it that an
27085 OR address is reachable, set the port correctly. (Previously we
27086 were reporting the dir port.)
27087 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27088 command. Bugfix on 0.1.2.17.
27089 - When loading bandwidth history, do not believe any information in
27090 the future. Fixes bug 434.
27091 - When loading entry guard information, do not believe any information
27093 - When we have our clock set far in the future and generate an
27094 onion key, then re-set our clock to be correct, we should not stop
27095 the onion key from getting rotated.
27096 - On some platforms, accept() can return a broken address. Detect
27097 this more quietly, and deal accordingly. Fixes bug 483.
27098 - It's not actually an error to find a non-pending entry in the DNS
27099 cache when canceling a pending resolve. Don't log unless stuff
27100 is fishy. Resolves bug 463.
27101 - Don't reset trusted dir server list when we set a configuration
27102 option. Patch from Robert Hogan.
27103 - Don't try to create the datadir when running --verify-config or
27104 --hash-password. Resolves bug 540.
27107 Changes in version 0.2.0.9-alpha - 2007-10-24
27108 This ninth development snapshot switches clients to the new v3 directory
27109 system; allows servers to be listed in the network status even when they
27110 have the same nickname as a registered server; and fixes many other
27111 bugs including a big one that was causing some servers to disappear
27112 from the network status lists for a few hours each day.
27114 o Major features (directory system):
27115 - Clients now download v3 consensus networkstatus documents instead
27116 of v2 networkstatus documents. Clients and caches now base their
27117 opinions about routers on these consensus documents. Clients only
27118 download router descriptors listed in the consensus.
27119 - Authorities now list servers who have the same nickname as
27120 a different named server, but list them with a new flag,
27121 "Unnamed". Now we can list servers that happen to pick the same
27122 nickname as a server that registered two years ago and then
27123 disappeared. Partially implements proposal 122.
27124 - If the consensus lists a router as "Unnamed", the name is assigned
27125 to a different router: do not identify the router by that name.
27126 Partially implements proposal 122.
27127 - Authorities can now come to a consensus on which method to use to
27128 compute the consensus. This gives us forward compatibility.
27131 - Stop publishing a new server descriptor just because we HUP or
27132 when we find our DirPort to be reachable but won't actually publish
27133 it. New descriptors without any real changes are dropped by the
27134 authorities, and can screw up our "publish every 18 hours" schedule.
27136 - When a router wasn't listed in a new networkstatus, we were leaving
27137 the flags for that router alone -- meaning it remained Named,
27138 Running, etc -- even though absence from the networkstatus means
27139 that it shouldn't be considered to exist at all anymore. Now we
27140 clear all the flags for routers that fall out of the networkstatus
27141 consensus. Fixes bug 529; bugfix on 0.1.2.x.
27142 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
27143 extrainfo documents and then discard them immediately for not
27144 matching the latest router. Bugfix on 0.2.0.1-alpha.
27146 o Minor features (v3 directory protocol):
27147 - Allow tor-gencert to generate a new certificate without replacing
27149 - Allow certificates to include an address.
27150 - When we change our directory-cache settings, reschedule all voting
27151 and download operations.
27152 - Reattempt certificate downloads immediately on failure, as long as
27153 we haven't failed a threshold number of times yet.
27154 - Delay retrying consensus downloads while we're downloading
27155 certificates to verify the one we just got. Also, count getting a
27156 consensus that we already have (or one that isn't valid) as a failure,
27157 and count failing to get the certificates after 20 minutes as a
27159 - Build circuits and download descriptors even if our consensus is a
27160 little expired. (This feature will go away once authorities are
27163 o Minor features (router descriptor cache):
27164 - If we find a cached-routers file that's been sitting around for more
27165 than 28 days unmodified, then most likely it's a leftover from
27166 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
27168 - When we (as a cache) download a descriptor because it was listed
27169 in a consensus, remember when the consensus was supposed to expire,
27170 and don't expire the descriptor until then.
27172 o Minor features (performance):
27173 - Call routerlist_remove_old_routers() much less often. This should
27174 speed startup, especially on directory caches.
27175 - Don't try to launch new descriptor downloads quite so often when we
27176 already have enough directory information to build circuits.
27177 - Base64 decoding was actually showing up on our profile when parsing
27178 the initial descriptor file; switch to an in-process all-at-once
27179 implementation that's about 3.5x times faster than calling out to
27182 o Minor features (compilation):
27183 - Detect non-ASCII platforms (if any still exist) and refuse to
27184 build there: some of our code assumes that 'A' is 65 and so on.
27186 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
27187 - Make the "next period" votes into "current period" votes immediately
27188 after publishing the consensus; avoid a heisenbug that made them
27189 stick around indefinitely.
27190 - When we discard a vote as a duplicate, do not report this as
27192 - Treat missing v3 keys or certificates as an error when running as a
27193 v3 directory authority.
27194 - When we're configured to be a v3 authority, but we're only listed
27195 as a non-v3 authority in our DirServer line for ourself, correct
27197 - If an authority doesn't have a qualified hostname, just put
27198 its address in the vote. This fixes the problem where we referred to
27199 "moria on moria:9031."
27200 - Distinguish between detached signatures for the wrong period, and
27201 detached signatures for a divergent vote.
27202 - Fix a small memory leak when computing a consensus.
27203 - When there's no consensus, we were forming a vote every 30
27204 minutes, but writing the "valid-after" line in our vote based
27205 on our configured V3AuthVotingInterval: so unless the intervals
27206 matched up, we immediately rejected our own vote because it didn't
27207 start at the voting interval that caused us to construct a vote.
27209 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
27210 - Delete unverified-consensus when the real consensus is set.
27211 - Consider retrying a consensus networkstatus fetch immediately
27212 after one fails: don't wait 60 seconds to notice.
27213 - When fetching a consensus as a cache, wait until a newer consensus
27214 should exist before trying to replace the current one.
27215 - Use a more forgiving schedule for retrying failed consensus
27216 downloads than for other types.
27218 o Minor bugfixes (other directory issues):
27219 - Correct the implementation of "download votes by digest." Bugfix on
27221 - Authorities no longer send back "400 you're unreachable please fix
27222 it" errors to Tor servers that aren't online all the time. We're
27223 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
27225 o Minor bugfixes (controller):
27226 - Don't reset trusted dir server list when we set a configuration
27227 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
27228 - Respond to INT and TERM SIGNAL commands before we execute the
27229 signal, in case the signal shuts us down. We had a patch in
27230 0.1.2.1-alpha that tried to do this by queueing the response on
27231 the connection's buffer before shutting down, but that really
27232 isn't the same thing at all. Bug located by Matt Edman.
27234 o Minor bugfixes (misc):
27235 - Correctly check for bad options to the "PublishServerDescriptor"
27236 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
27237 - Stop leaking memory on failing case of base32_decode, and make
27238 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
27239 - Don't try to download extrainfo documents when we're trying to
27240 fetch enough directory info to build a circuit: having enough
27241 info should get priority. Bugfix on 0.2.0.x.
27242 - Don't complain that "your server has not managed to confirm that its
27243 ports are reachable" if we haven't been able to build any circuits
27244 yet. Bug found by spending four hours without a v3 consensus. Bugfix
27246 - Detect the reason for failing to mmap a descriptor file we just
27247 wrote, and give a more useful log message. Fixes bug 533. Bugfix
27250 o Code simplifications and refactoring:
27251 - Remove support for the old bw_accounting file: we've been storing
27252 bandwidth accounting information in the state file since
27253 0.1.2.5-alpha. This may result in bandwidth accounting errors
27254 if you try to upgrade from 0.1.1.x or earlier, or if you try to
27255 downgrade to 0.1.1.x or earlier.
27256 - New convenience code to locate a file within the DataDirectory.
27257 - Move non-authority functionality out of dirvote.c.
27258 - Refactor the arguments for router_pick_{directory_|trusteddir}server
27259 so that they all take the same named flags.
27262 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
27263 Unix users an easy way to script their Tor process (e.g. by
27264 adjusting bandwidth based on the time of the day).
27267 Changes in version 0.2.0.8-alpha - 2007-10-12
27268 This eighth development snapshot fixes a crash bug that's been bothering
27269 us since February 2007, lets bridge authorities store a list of bridge
27270 descriptors they've seen, gets v3 directory voting closer to working,
27271 starts caching v3 directory consensus documents on directory mirrors,
27272 and fixes a variety of smaller issues including some minor memory leaks.
27274 o Major features (router descriptor cache):
27275 - Store routers in a file called cached-descriptors instead of in
27276 cached-routers. Initialize cached-descriptors from cached-routers
27277 if the old format is around. The new format allows us to store
27278 annotations along with descriptors.
27279 - Use annotations to record the time we received each descriptor, its
27280 source, and its purpose.
27281 - Disable the SETROUTERPURPOSE controller command: it is now
27283 - Controllers should now specify cache=no or cache=yes when using
27284 the +POSTDESCRIPTOR command.
27285 - Bridge authorities now write bridge descriptors to disk, meaning
27286 we can export them to other programs and begin distributing them
27289 o Major features (directory authorities):
27290 - When a v3 authority is missing votes or signatures, it now tries
27292 - Directory authorities track weighted fractional uptime as well as
27293 weighted mean-time-between failures. WFU is suitable for deciding
27294 whether a node is "usually up", while MTBF is suitable for deciding
27295 whether a node is "likely to stay up." We need both, because
27296 "usually up" is a good requirement for guards, while "likely to
27297 stay up" is a good requirement for long-lived connections.
27299 o Major features (v3 directory system):
27300 - Caches now download v3 network status documents as needed,
27301 and download the descriptors listed in them.
27302 - All hosts now attempt to download and keep fresh v3 authority
27303 certificates, and re-attempt after failures.
27304 - More internal-consistency checks for vote parsing.
27306 o Major bugfixes (crashes):
27307 - If a connection is shut down abruptly because of something that
27308 happened inside connection_flushed_some(), do not call
27309 connection_finished_flushing(). Should fix bug 451. Bugfix on
27312 o Major bugfixes (performance):
27313 - Fix really bad O(n^2) performance when parsing a long list of
27314 routers: Instead of searching the entire list for an "extra-info "
27315 string which usually wasn't there, once for every routerinfo
27316 we read, just scan lines forward until we find one we like.
27318 - When we add data to a write buffer in response to the data on that
27319 write buffer getting low because of a flush, do not consider the
27320 newly added data as a candidate for immediate flushing, but rather
27321 make it wait until the next round of writing. Otherwise, we flush
27322 and refill recursively, and a single greedy TLS connection can
27323 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
27325 o Minor features (v3 authority system):
27326 - Add more ways for tools to download the votes that lead to the
27328 - Send a 503 when low on bandwidth and a vote, consensus, or
27329 certificate is requested.
27330 - If-modified-since is now implemented properly for all kinds of
27331 certificate requests.
27333 o Minor bugfixes (network statuses):
27334 - Tweak the implementation of proposal 109 slightly: allow at most
27335 two Tor servers on the same IP address, except if it's the location
27336 of a directory authority, in which case allow five. Bugfix on
27339 o Minor bugfixes (controller):
27340 - When sending a status event to the controller telling it that an
27341 OR address is reachable, set the port correctly. (Previously we
27342 were reporting the dir port.) Bugfix on 0.1.2.x.
27344 o Minor bugfixes (v3 directory system):
27345 - Fix logic to look up a cert by its signing key digest. Bugfix on
27347 - Only change the reply to a vote to "OK" if it's not already
27348 set. This gets rid of annoying "400 OK" log messages, which may
27349 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
27350 - When we get a valid consensus, recompute the voting schedule.
27351 - Base the valid-after time of a vote on the consensus voting
27352 schedule, not on our preferred schedule.
27353 - Make the return values and messages from signature uploads and
27354 downloads more sensible.
27355 - Fix a memory leak when serving votes and consensus documents, and
27356 another when serving certificates.
27358 o Minor bugfixes (performance):
27359 - Use a slightly simpler string hashing algorithm (copying Python's
27360 instead of Java's) and optimize our digest hashing algorithm to take
27361 advantage of 64-bit platforms and to remove some possibly-costly
27363 - Fix a minor memory leak whenever we parse guards from our state
27364 file. Bugfix on 0.2.0.7-alpha.
27365 - Fix a minor memory leak whenever we write out a file. Bugfix on
27367 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27368 command. Bugfix on 0.2.0.5-alpha.
27370 o Minor bugfixes (portability):
27371 - On some platforms, accept() can return a broken address. Detect
27372 this more quietly, and deal accordingly. Fixes bug 483.
27373 - Stop calling tor_strlower() on uninitialized memory in some cases.
27374 Bugfix in 0.2.0.7-alpha.
27376 o Minor bugfixes (usability):
27377 - Treat some 403 responses from directory servers as INFO rather than
27378 WARN-severity events.
27379 - It's not actually an error to find a non-pending entry in the DNS
27380 cache when canceling a pending resolve. Don't log unless stuff is
27381 fishy. Resolves bug 463.
27383 o Minor bugfixes (anonymity):
27384 - Never report that we've used more bandwidth than we're willing to
27385 relay: it leaks how much non-relay traffic we're using. Resolves
27387 - When looking for a circuit to cannibalize, consider family as well
27388 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27389 circuit cannibalization).
27391 o Code simplifications and refactoring:
27392 - Make a bunch of functions static. Remove some dead code.
27393 - Pull out about a third of the really big routerlist.c; put it in a
27394 new module, networkstatus.c.
27395 - Merge the extra fields in local_routerstatus_t back into
27396 routerstatus_t: we used to need one routerstatus_t for each
27397 authority's opinion, plus a local_routerstatus_t for the locally
27398 computed consensus opinion. To save space, we put the locally
27399 modified fields into local_routerstatus_t, and only the common
27400 stuff into routerstatus_t. But once v3 directories are in use,
27401 clients and caches will no longer need to hold authority opinions;
27402 thus, the rationale for keeping the types separate is now gone.
27403 - Make the code used to reschedule and reattempt downloads more
27405 - Turn all 'Are we a directory server/mirror?' logic into a call to
27407 - Remove the code to generate the oldest (v1) directory format.
27408 The code has been disabled since 0.2.0.5-alpha.
27411 Changes in version 0.2.0.7-alpha - 2007-09-21
27412 This seventh development snapshot makes bridges work again, makes bridge
27413 authorities work for the first time, fixes two huge performance flaws
27414 in hidden services, and fixes a variety of minor issues.
27416 o New directory authorities:
27417 - Set up moria1 and tor26 as the first v3 directory authorities. See
27418 doc/spec/dir-spec.txt for details on the new directory design.
27420 o Major bugfixes (crashes):
27421 - Fix possible segfaults in functions called from
27422 rend_process_relay_cell(). Bugfix on 0.1.2.x.
27424 o Major bugfixes (bridges):
27425 - Fix a bug that made servers send a "404 Not found" in response to
27426 attempts to fetch their server descriptor. This caused Tor servers
27427 to take many minutes to establish reachability for their DirPort,
27428 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
27429 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
27430 users configure that and specify a bridge with an identity
27431 fingerprint, now they will lookup the bridge descriptor at the
27432 default bridge authority via a one-hop tunnel, but once circuits
27433 are established they will switch to a three-hop tunnel for later
27434 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
27436 o Major bugfixes (hidden services):
27437 - Hidden services were choosing introduction points uniquely by
27438 hexdigest, but when constructing the hidden service descriptor
27439 they merely wrote the (potentially ambiguous) nickname.
27440 - Clients now use the v2 intro format for hidden service
27441 connections: they specify their chosen rendezvous point by identity
27442 digest rather than by (potentially ambiguous) nickname. Both
27443 are bugfixes on 0.1.2.x, and they could speed up hidden service
27444 connections dramatically. Thanks to Karsten Loesing.
27446 o Minor features (security):
27447 - As a client, do not believe any server that tells us that an
27448 address maps to an internal address space.
27449 - Make it possible to enable HashedControlPassword and
27450 CookieAuthentication at the same time.
27452 o Minor features (guard nodes):
27453 - Tag every guard node in our state file with the version that
27454 we believe added it, or with our own version if we add it. This way,
27455 if a user temporarily runs an old version of Tor and then switches
27456 back to a new one, she doesn't automatically lose her guards.
27458 o Minor features (speed):
27459 - When implementing AES counter mode, update only the portions of the
27460 counter buffer that need to change, and don't keep separate
27461 network-order and host-order counters when they are the same (i.e.,
27462 on big-endian hosts.)
27464 o Minor features (controller):
27465 - Accept LF instead of CRLF on controller, since some software has a
27466 hard time generating real Internet newlines.
27467 - Add GETINFO values for the server status events
27468 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
27471 o Removed features:
27472 - Routers no longer include bandwidth-history lines in their
27473 descriptors; this information is already available in extra-info
27474 documents, and including it in router descriptors took up 60%
27475 (!) of compressed router descriptor downloads. Completes
27476 implementation of proposal 104.
27477 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
27478 and TorControl.py, as they use the old v0 controller protocol,
27479 and are obsoleted by TorFlow anyway.
27480 - Drop support for v1 rendezvous descriptors, since we never used
27481 them anyway, and the code has probably rotted by now. Based on
27482 patch from Karsten Loesing.
27483 - On OSX, stop warning the user that kqueue support in libevent is
27484 "experimental", since it seems to have worked fine for ages.
27487 - When generating information telling us how to extend to a given
27488 router, do not try to include the nickname if it is absent. Fixes
27489 bug 467. Bugfix on 0.2.0.3-alpha.
27490 - Fix a user-triggerable (but not remotely-triggerable) segfault
27491 in expand_filename(). Bugfix on 0.1.2.x.
27492 - Fix a memory leak when freeing incomplete requests from DNSPort.
27493 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
27494 - Don't try to access (or alter) the state file when running
27495 --list-fingerprint or --verify-config or --hash-password. (Resolves
27496 bug 499.) Bugfix on 0.1.2.x.
27497 - Servers used to decline to publish their DirPort if their
27498 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
27499 were below a threshold. Now they only look at BandwidthRate and
27500 RelayBandwidthRate. Bugfix on 0.1.2.x.
27501 - Remove an optimization in the AES counter-mode code that assumed
27502 that the counter never exceeded 2^68. When the counter can be set
27503 arbitrarily as an IV (as it is by Karsten's new hidden services
27504 code), this assumption no longer holds. Bugfix on 0.1.2.x.
27505 - Resume listing "AUTHORITY" flag for authorities in network status.
27506 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
27508 o Code simplifications and refactoring:
27509 - Revamp file-writing logic so we don't need to have the entire
27510 contents of a file in memory at once before we write to disk. Tor,
27512 - Turn "descriptor store" into a full-fledged type.
27513 - Move all NT services code into a separate source file.
27514 - Unify all code that computes medians, percentile elements, etc.
27515 - Get rid of a needless malloc when parsing address policies.
27518 Changes in version 0.1.2.17 - 2007-08-30
27519 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
27520 X bundles. Vidalia 0.0.14 makes authentication required for the
27521 ControlPort in the default configuration, which addresses important
27522 security risks. Everybody who uses Vidalia (or another controller)
27525 In addition, this Tor update fixes major load balancing problems with
27526 path selection, which should speed things up a lot once many people
27529 o Major bugfixes (security):
27530 - We removed support for the old (v0) control protocol. It has been
27531 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
27532 become more of a headache than it's worth.
27534 o Major bugfixes (load balancing):
27535 - When choosing nodes for non-guard positions, weight guards
27536 proportionally less, since they already have enough load. Patch
27538 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27539 will allow fast Tor servers to get more attention.
27540 - When we're upgrading from an old Tor version, forget our current
27541 guards and pick new ones according to the new weightings. These
27542 three load balancing patches could raise effective network capacity
27543 by a factor of four. Thanks to Mike Perry for measurements.
27545 o Major bugfixes (stream expiration):
27546 - Expire not-yet-successful application streams in all cases if
27547 they've been around longer than SocksTimeout. Right now there are
27548 some cases where the stream will live forever, demanding a new
27549 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27551 o Minor features (controller):
27552 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27553 is valid before any authentication has been received. It tells
27554 a controller what kind of authentication is expected, and what
27555 protocol is spoken. Implements proposal 119.
27557 o Minor bugfixes (performance):
27558 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27559 greatly speeding up loading cached-routers from disk on startup.
27560 - Disable sentinel-based debugging for buffer code: we squashed all
27561 the bugs that this was supposed to detect a long time ago, and now
27562 its only effect is to change our buffer sizes from nice powers of
27563 two (which platform mallocs tend to like) to values slightly over
27564 powers of two (which make some platform mallocs sad).
27566 o Minor bugfixes (misc):
27567 - If exit bandwidth ever exceeds one third of total bandwidth, then
27568 use the correct formula to weight exit nodes when choosing paths.
27569 Based on patch from Mike Perry.
27570 - Choose perfectly fairly among routers when choosing by bandwidth and
27571 weighting by fraction of bandwidth provided by exits. Previously, we
27572 would choose with only approximate fairness, and correct ourselves
27573 if we ran off the end of the list.
27574 - If we require CookieAuthentication but we fail to write the
27575 cookie file, we would warn but not exit, and end up in a state
27576 where no controller could authenticate. Now we exit.
27577 - If we require CookieAuthentication, stop generating a new cookie
27578 every time we change any piece of our config.
27579 - Refuse to start with certain directory authority keys, and
27580 encourage people using them to stop.
27581 - Terminate multi-line control events properly. Original patch
27583 - Fix a minor memory leak when we fail to find enough suitable
27584 servers to choose a circuit.
27585 - Stop leaking part of the descriptor when we run into a particularly
27586 unparseable piece of it.
27589 Changes in version 0.2.0.6-alpha - 2007-08-26
27590 This sixth development snapshot features a new Vidalia version in the
27591 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27592 the ControlPort in the default configuration, which addresses important
27595 In addition, this snapshot fixes major load balancing problems
27596 with path selection, which should speed things up a lot once many
27597 people have upgraded. The directory authorities also use a new
27598 mean-time-between-failure approach to tracking which servers are stable,
27599 rather than just looking at the most recent uptime.
27601 o New directory authorities:
27602 - Set up Tonga as the default bridge directory authority.
27605 - Directory authorities now track servers by weighted
27606 mean-times-between-failures. When we have 4 or more days of data,
27607 use measured MTBF rather than declared uptime to decide whether
27608 to call a router Stable. Implements proposal 108.
27610 o Major bugfixes (load balancing):
27611 - When choosing nodes for non-guard positions, weight guards
27612 proportionally less, since they already have enough load. Patch
27614 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27615 will allow fast Tor servers to get more attention.
27616 - When we're upgrading from an old Tor version, forget our current
27617 guards and pick new ones according to the new weightings. These
27618 three load balancing patches could raise effective network capacity
27619 by a factor of four. Thanks to Mike Perry for measurements.
27621 o Major bugfixes (descriptor parsing):
27622 - Handle unexpected whitespace better in malformed descriptors. Bug
27623 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27626 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27627 GETINFO for Torstat to use until it can switch to using extrainfos.
27628 - Optionally (if built with -DEXPORTMALLINFO) export the output
27629 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27633 - Do not intermix bridge routers with controller-added
27634 routers. (Bugfix on 0.2.0.x)
27635 - Do not fail with an assert when accept() returns an unexpected
27636 address family. Addresses but does not wholly fix bug 483. (Bugfix
27638 - Let directory authorities startup even when they can't generate
27639 a descriptor immediately, e.g. because they don't know their
27641 - Stop putting the authentication cookie in a file called "0"
27642 in your working directory if you don't specify anything for the
27643 new CookieAuthFile option. Reported by Matt Edman.
27644 - Make it possible to read the PROTOCOLINFO response in a way that
27645 conforms to our control-spec. Reported by Matt Edman.
27646 - Fix a minor memory leak when we fail to find enough suitable
27647 servers to choose a circuit. Bugfix on 0.1.2.x.
27648 - Stop leaking part of the descriptor when we run into a particularly
27649 unparseable piece of it. Bugfix on 0.1.2.x.
27650 - Unmap the extrainfo cache file on exit.
27653 Changes in version 0.2.0.5-alpha - 2007-08-19
27654 This fifth development snapshot fixes compilation on Windows again;
27655 fixes an obnoxious client-side bug that slowed things down and put
27656 extra load on the network; gets us closer to using the v3 directory
27657 voting scheme; makes it easier for Tor controllers to use cookie-based
27658 authentication; and fixes a variety of other bugs.
27660 o Removed features:
27661 - Version 1 directories are no longer generated in full. Instead,
27662 authorities generate and serve "stub" v1 directories that list
27663 no servers. This will stop Tor versions 0.1.0.x and earlier from
27664 working, but (for security reasons) nobody should be running those
27667 o Major bugfixes (compilation, 0.2.0.x):
27668 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27669 - Try to fix MSVC compilation: build correctly on platforms that do
27670 not define s6_addr16 or s6_addr32.
27671 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27674 o Major bugfixes (stream expiration):
27675 - Expire not-yet-successful application streams in all cases if
27676 they've been around longer than SocksTimeout. Right now there are
27677 some cases where the stream will live forever, demanding a new
27678 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27679 reported by lodger.
27681 o Minor features (directory servers):
27682 - When somebody requests a list of statuses or servers, and we have
27683 none of those, return a 404 rather than an empty 200.
27685 o Minor features (directory voting):
27686 - Store v3 consensus status consensuses on disk, and reload them
27689 o Minor features (security):
27690 - Warn about unsafe ControlPort configurations.
27691 - Refuse to start with certain directory authority keys, and
27692 encourage people using them to stop.
27694 o Minor features (controller):
27695 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27696 is valid before any authentication has been received. It tells
27697 a controller what kind of authentication is expected, and what
27698 protocol is spoken. Implements proposal 119.
27699 - New config option CookieAuthFile to choose a new location for the
27700 cookie authentication file, and config option
27701 CookieAuthFileGroupReadable to make it group-readable.
27703 o Minor features (unit testing):
27704 - Add command-line arguments to unit-test executable so that we can
27705 invoke any chosen test from the command line rather than having
27706 to run the whole test suite at once; and so that we can turn on
27707 logging for the unit tests.
27709 o Minor bugfixes (on 0.1.2.x):
27710 - If we require CookieAuthentication but we fail to write the
27711 cookie file, we would warn but not exit, and end up in a state
27712 where no controller could authenticate. Now we exit.
27713 - If we require CookieAuthentication, stop generating a new cookie
27714 every time we change any piece of our config.
27715 - When loading bandwidth history, do not believe any information in
27716 the future. Fixes bug 434.
27717 - When loading entry guard information, do not believe any information
27719 - When we have our clock set far in the future and generate an
27720 onion key, then re-set our clock to be correct, we should not stop
27721 the onion key from getting rotated.
27722 - Clean up torrc sample config file.
27723 - Do not automatically run configure from autogen.sh. This
27724 non-standard behavior tended to annoy people who have built other
27727 o Minor bugfixes (on 0.2.0.x):
27728 - Fix a bug with AutomapHostsOnResolve that would always cause
27729 the second request to fail. Bug reported by Kate. Bugfix on
27731 - Fix a bug in ADDRMAP controller replies that would sometimes
27732 try to print a NULL. Patch from tup.
27733 - Read v3 directory authority keys from the right location.
27734 - Numerous bugfixes to directory voting code.
27737 Changes in version 0.1.2.16 - 2007-08-01
27738 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27739 remote attacker in certain situations to rewrite the user's torrc
27740 configuration file. This can completely compromise anonymity of users
27741 in most configurations, including those running the Vidalia bundles,
27742 TorK, etc. Or worse.
27744 o Major security fixes:
27745 - Close immediately after missing authentication on control port;
27746 do not allow multiple authentication attempts.
27749 Changes in version 0.2.0.4-alpha - 2007-08-01
27750 This fourth development snapshot fixes a critical security vulnerability
27751 for most users, specifically those running Vidalia, TorK, etc. Everybody
27752 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
27754 o Major security fixes:
27755 - Close immediately after missing authentication on control port;
27756 do not allow multiple authentication attempts.
27758 o Major bugfixes (compilation):
27759 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
27762 o Minor features (performance):
27763 - Be even more aggressive about releasing RAM from small
27764 empty buffers. Thanks to our free-list code, this shouldn't be too
27765 performance-intensive.
27766 - Disable sentinel-based debugging for buffer code: we squashed all
27767 the bugs that this was supposed to detect a long time ago, and
27768 now its only effect is to change our buffer sizes from nice
27769 powers of two (which platform mallocs tend to like) to values
27770 slightly over powers of two (which make some platform mallocs sad).
27771 - Log malloc statistics from mallinfo() on platforms where it
27775 Changes in version 0.2.0.3-alpha - 2007-07-29
27776 This third development snapshot introduces new experimental
27777 blocking-resistance features and a preliminary version of the v3
27778 directory voting design, and includes many other smaller features
27782 - The first pieces of our "bridge" design for blocking-resistance
27783 are implemented. People can run bridge directory authorities;
27784 people can run bridges; and people can configure their Tor clients
27785 with a set of bridges to use as the first hop into the Tor network.
27786 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
27788 - Create listener connections before we setuid to the configured
27789 User and Group. Now non-Windows users can choose port values
27790 under 1024, start Tor as root, and have Tor bind those ports
27791 before it changes to another UID. (Windows users could already
27793 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
27794 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
27795 on "vserver" accounts. (Patch from coderman.)
27796 - Be even more aggressive about separating local traffic from relayed
27797 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
27799 o Major features (experimental):
27800 - First cut of code for "v3 dir voting": directory authorities will
27801 vote on a common network status document rather than each publishing
27802 their own opinion. This code needs more testing and more corner-case
27803 handling before it's ready for use.
27806 - Directory authorities now call routers Fast if their bandwidth is
27807 at least 100KB/s, and consider their bandwidth adequate to be a
27808 Guard if it is at least 250KB/s, no matter the medians. This fix
27809 complements proposal 107. [Bugfix on 0.1.2.x]
27810 - Directory authorities now never mark more than 3 servers per IP as
27811 Valid and Running. (Implements proposal 109, by Kevin Bauer and
27813 - Minor change to organizationName and commonName generation
27814 procedures in TLS certificates during Tor handshakes, to invalidate
27815 some earlier censorware approaches. This is not a long-term
27816 solution, but applying it will give us a bit of time to look into
27817 the epidemiology of countermeasures as they spread.
27819 o Major bugfixes (directory):
27820 - Rewrite directory tokenization code to never run off the end of
27821 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
27823 o Minor features (controller):
27824 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
27825 match requests to applications. (Patch from Robert Hogan.)
27826 - Report address and port correctly on connections to DNSPort. (Patch
27827 from Robert Hogan.)
27828 - Add a RESOLVE command to launch hostname lookups. (Original patch
27829 from Robert Hogan.)
27830 - Add GETINFO status/enough-dir-info to let controllers tell whether
27831 Tor has downloaded sufficient directory information. (Patch
27833 - You can now use the ControlSocket option to tell Tor to listen for
27834 controller connections on Unix domain sockets on systems that
27835 support them. (Patch from Peter Palfrader.)
27836 - STREAM NEW events are generated for DNSPort requests and for
27837 tunneled directory connections. (Patch from Robert Hogan.)
27838 - New "GETINFO address-mappings/*" command to get address mappings
27839 with expiry information. "addr-mappings/*" is now deprecated.
27842 o Minor features (misc):
27843 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
27845 - The tor-gencert tool for v3 directory authorities now creates all
27846 files as readable to the file creator only, and write-protects
27847 the authority identity key.
27848 - When dumping memory usage, list bytes used in buffer memory
27850 - When running with dmalloc, dump more stats on hup and on exit.
27851 - Directory authorities now fail quickly and (relatively) harmlessly
27852 if they generate a network status document that is somehow
27855 o Traffic load balancing improvements:
27856 - If exit bandwidth ever exceeds one third of total bandwidth, then
27857 use the correct formula to weight exit nodes when choosing paths.
27858 (Based on patch from Mike Perry.)
27859 - Choose perfectly fairly among routers when choosing by bandwidth and
27860 weighting by fraction of bandwidth provided by exits. Previously, we
27861 would choose with only approximate fairness, and correct ourselves
27862 if we ran off the end of the list. [Bugfix on 0.1.2.x]
27864 o Performance improvements:
27865 - Be more aggressive with freeing buffer RAM or putting it on the
27867 - Use Critical Sections rather than Mutexes for synchronizing threads
27868 on win32; Mutexes are heavier-weight, and designed for synchronizing
27871 o Deprecated and removed features:
27872 - RedirectExits is now deprecated.
27873 - Stop allowing address masks that do not correspond to bit prefixes.
27874 We have warned about these for a really long time; now it's time
27875 to reject them. (Patch from croup.)
27877 o Minor bugfixes (directory):
27878 - Fix another crash bug related to extra-info caching. (Bug found by
27879 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
27880 - Directories no longer return a "304 not modified" when they don't
27881 have the networkstatus the client asked for. Also fix a memory
27882 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
27883 - We had accidentally labelled 0.1.2.x directory servers as not
27884 suitable for begin_dir requests, and had labelled no directory
27885 servers as suitable for uploading extra-info documents. [Bugfix
27888 o Minor bugfixes (dns):
27889 - Fix a crash when DNSPort is set more than once. (Patch from Robert
27890 Hogan.) [Bugfix on 0.2.0.2-alpha]
27891 - Add DNSPort connections to the global connection list, so that we
27892 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
27894 - Fix a dangling reference that could lead to a crash when DNSPort is
27895 changed or closed (Patch from Robert Hogan.) [Bugfix on
27898 o Minor bugfixes (controller):
27899 - Provide DNS expiry times in GMT, not in local time. For backward
27900 compatibility, ADDRMAP events only provide GMT expiry in an extended
27901 field. "GETINFO address-mappings" always does the right thing.
27902 - Use CRLF line endings properly in NS events.
27903 - Terminate multi-line control events properly. (Original patch
27904 from tup.) [Bugfix on 0.1.2.x-alpha]
27905 - Do not include spaces in SOURCE_ADDR fields in STREAM
27906 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
27909 Changes in version 0.1.2.15 - 2007-07-17
27910 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
27911 problems, fixes compilation on BSD, and fixes a variety of other
27912 bugs. Everybody should upgrade.
27914 o Major bugfixes (compilation):
27915 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
27917 o Major bugfixes (crashes):
27918 - Try even harder not to dereference the first character after
27919 an mmap(). Reported by lodger.
27920 - Fix a crash bug in directory authorities when we re-number the
27921 routerlist while inserting a new router.
27922 - When the cached-routers file is an even multiple of the page size,
27923 don't run off the end and crash. (Fixes bug 455; based on idea
27925 - Fix eventdns.c behavior on Solaris: It is critical to include
27926 orconfig.h _before_ sys/types.h, so that we can get the expected
27927 definition of _FILE_OFFSET_BITS.
27929 o Major bugfixes (security):
27930 - Fix a possible buffer overrun when using BSD natd support. Bug
27932 - When sending destroy cells from a circuit's origin, don't include
27933 the reason for tearing down the circuit. The spec says we didn't,
27934 and now we actually don't. Reported by lodger.
27935 - Keep streamids from different exits on a circuit separate. This
27936 bug may have allowed other routers on a given circuit to inject
27937 cells into streams. Reported by lodger; fixes bug 446.
27938 - If there's a never-before-connected-to guard node in our list,
27939 never choose any guards past it. This way we don't expand our
27940 guard list unless we need to.
27942 o Minor bugfixes (guard nodes):
27943 - Weight guard selection by bandwidth, so that low-bandwidth nodes
27944 don't get overused as guards.
27946 o Minor bugfixes (directory):
27947 - Correctly count the number of authorities that recommend each
27948 version. Previously, we were under-counting by 1.
27949 - Fix a potential crash bug when we load many server descriptors at
27950 once and some of them make others of them obsolete. Fixes bug 458.
27952 o Minor bugfixes (hidden services):
27953 - Stop tearing down the whole circuit when the user asks for a
27954 connection to a port that the hidden service didn't configure.
27957 o Minor bugfixes (misc):
27958 - On Windows, we were preventing other processes from reading
27959 cached-routers while Tor was running. Reported by janbar.
27960 - Fix a possible (but very unlikely) bug in picking routers by
27961 bandwidth. Add a log message to confirm that it is in fact
27962 unlikely. Patch from lodger.
27963 - Backport a couple of memory leak fixes.
27964 - Backport miscellaneous cosmetic bugfixes.
27967 Changes in version 0.2.0.2-alpha - 2007-06-02
27968 o Major bugfixes on 0.2.0.1-alpha:
27969 - Fix an assertion failure related to servers without extra-info digests.
27970 Resolves bugs 441 and 442.
27972 o Minor features (directory):
27973 - Support "If-Modified-Since" when answering HTTP requests for
27974 directories, running-routers documents, and network-status documents.
27975 (There's no need to support it for router descriptors, since those
27976 are downloaded by descriptor digest.)
27978 o Minor build issues:
27979 - Clear up some MIPSPro compiler warnings.
27980 - When building from a tarball on a machine that happens to have SVK
27981 installed, report the micro-revision as whatever version existed
27982 in the tarball, not as "x".
27985 Changes in version 0.2.0.1-alpha - 2007-06-01
27986 This early development snapshot provides new features for people running
27987 Tor as both a client and a server (check out the new RelayBandwidth
27988 config options); lets Tor run as a DNS proxy; and generally moves us
27989 forward on a lot of fronts.
27991 o Major features, server usability:
27992 - New config options RelayBandwidthRate and RelayBandwidthBurst:
27993 a separate set of token buckets for relayed traffic. Right now
27994 relayed traffic is defined as answers to directory requests, and
27995 OR connections that don't have any local circuits on them.
27997 o Major features, client usability:
27998 - A client-side DNS proxy feature to replace the need for
27999 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
28000 for DNS requests on port 9999, use the Tor network to resolve them
28001 anonymously, and send the reply back like a regular DNS server.
28002 The code still only implements a subset of DNS.
28003 - Make PreferTunneledDirConns and TunnelDirConns work even when
28004 we have no cached directory info. This means Tor clients can now
28005 do all of their connections protected by TLS.
28007 o Major features, performance and efficiency:
28008 - Directory authorities accept and serve "extra info" documents for
28009 routers. These documents contain fields from router descriptors
28010 that aren't usually needed, and that use a lot of excess
28011 bandwidth. Once these fields are removed from router descriptors,
28012 the bandwidth savings should be about 60%. [Partially implements
28014 - Servers upload extra-info documents to any authority that accepts
28015 them. Authorities (and caches that have been configured to download
28016 extra-info documents) download them as needed. [Partially implements
28018 - Change the way that Tor buffers data that it is waiting to write.
28019 Instead of queueing data cells in an enormous ring buffer for each
28020 client->OR or OR->OR connection, we now queue cells on a separate
28021 queue for each circuit. This lets us use less slack memory, and
28022 will eventually let us be smarter about prioritizing different kinds
28024 - Use memory pools to allocate cells with better speed and memory
28025 efficiency, especially on platforms where malloc() is inefficient.
28026 - Stop reading on edge connections when their corresponding circuit
28027 buffers are full; start again as the circuits empty out.
28029 o Major features, other:
28030 - Add an HSAuthorityRecordStats option that hidden service authorities
28031 can use to track statistics of overall hidden service usage without
28032 logging information that would be very useful to an attacker.
28033 - Start work implementing multi-level keys for directory authorities:
28034 Add a standalone tool to generate key certificates. (Proposal 103.)
28037 - Directory authorities now call routers Stable if they have an
28038 uptime of at least 30 days, even if that's not the median uptime
28039 in the network. Implements proposal 107, suggested by Kevin Bauer
28042 o Minor fixes (resource management):
28043 - Count the number of open sockets separately from the number
28044 of active connection_t objects. This will let us avoid underusing
28045 our allocated connection limit.
28046 - We no longer use socket pairs to link an edge connection to an
28047 anonymous directory connection or a DirPort test connection.
28048 Instead, we track the link internally and transfer the data
28049 in-process. This saves two sockets per "linked" connection (at the
28050 client and at the server), and avoids the nasty Windows socketpair()
28052 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
28053 for every single inactive connection_t. Free items from the
28054 4k/16k-buffer free lists when they haven't been used for a while.
28056 o Minor features (build):
28057 - Make autoconf search for libevent, openssl, and zlib consistently.
28058 - Update deprecated macros in configure.in.
28059 - When warning about missing headers, tell the user to let us
28060 know if the compile succeeds anyway, so we can downgrade the
28062 - Include the current subversion revision as part of the version
28063 string: either fetch it directly if we're in an SVN checkout, do
28064 some magic to guess it if we're in an SVK checkout, or use
28065 the last-detected version if we're building from a .tar.gz.
28066 Use this version consistently in log messages.
28068 o Minor features (logging):
28069 - Always prepend "Bug: " to any log message about a bug.
28070 - Put a platform string (e.g. "Linux i686") in the startup log
28071 message, so when people paste just their logs, we know if it's
28072 OpenBSD or Windows or what.
28073 - When logging memory usage, break down memory used in buffers by
28076 o Minor features (directory system):
28077 - New config option V2AuthoritativeDirectory that all directory
28078 authorities should set. This will let future authorities choose
28079 not to serve V2 directory information.
28080 - Directory authorities allow multiple router descriptors and/or extra
28081 info documents to be uploaded in a single go. This will make
28082 implementing proposal 104 simpler.
28084 o Minor features (controller):
28085 - Add a new config option __DisablePredictedCircuits designed for
28086 use by the controller, when we don't want Tor to build any circuits
28088 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
28089 so we can exit from the middle of the circuit.
28090 - Implement "getinfo status/circuit-established".
28091 - Implement "getinfo status/version/..." so a controller can tell
28092 whether the current version is recommended, and whether any versions
28093 are good, and how many authorities agree. (Patch from shibz.)
28095 o Minor features (hidden services):
28096 - Allow multiple HiddenServicePort directives with the same virtual
28097 port; when they occur, the user is sent round-robin to one
28098 of the target ports chosen at random. Partially fixes bug 393 by
28099 adding limited ad-hoc round-robining.
28101 o Minor features (other):
28103 - Add a new AutomapHostsOnResolve option: when it is enabled, any
28104 resolve request for hosts matching a given pattern causes Tor to
28105 generate an internal virtual address mapping for that host. This
28106 allows DNSPort to work sensibly with hidden service users. By
28107 default, .exit and .onion addresses are remapped; the list of
28108 patterns can be reconfigured with AutomapHostsSuffixes.
28109 - Add an "-F" option to tor-resolve to force a resolve for a .onion
28110 address. Thanks to the AutomapHostsOnResolve option, this is no
28111 longer a completely silly thing to do.
28112 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
28113 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
28114 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
28115 minus 1 byte: the actual maximum declared bandwidth.
28117 o Removed features:
28118 - Removed support for the old binary "version 0" controller protocol.
28119 This has been deprecated since 0.1.1, and warnings have been issued
28120 since 0.1.2. When we encounter a v0 control message, we now send
28121 back an error and close the connection.
28122 - Remove the old "dns worker" server DNS code: it hasn't been default
28123 since 0.1.2.2-alpha, and all the servers seem to be using the new
28126 o Minor bugfixes (portability):
28127 - Even though Windows is equally happy with / and \ as path separators,
28128 try to use \ consistently on Windows and / consistently on Unix: it
28129 makes the log messages nicer.
28130 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
28131 - Read resolv.conf files correctly on platforms where read() returns
28132 partial results on small file reads.
28134 o Minor bugfixes (directory):
28135 - Correctly enforce that elements of directory objects do not appear
28136 more often than they are allowed to appear.
28137 - When we are reporting the DirServer line we just parsed, we were
28138 logging the second stanza of the key fingerprint, not the first.
28140 o Minor bugfixes (logging):
28141 - When we hit an EOF on a log (probably because we're shutting down),
28142 don't try to remove the log from the list: just mark it as
28143 unusable. (Bulletproofs against bug 222.)
28145 o Minor bugfixes (other):
28146 - In the exitlist script, only consider the most recently published
28147 server descriptor for each server. Also, when the user requests
28148 a list of servers that _reject_ connections to a given address,
28149 explicitly exclude the IPs that also have servers that accept
28150 connections to that address. (Resolves bug 405.)
28151 - Stop allowing hibernating servers to be "stable" or "fast".
28152 - On Windows, we were preventing other processes from reading
28153 cached-routers while Tor was running. (Reported by janbar)
28154 - Make the NodeFamilies config option work. (Reported by
28155 lodger -- it has never actually worked, even though we added it
28157 - Check return values from pthread_mutex functions.
28158 - Don't save non-general-purpose router descriptors to the disk cache,
28159 because we have no way of remembering what their purpose was when
28161 - Add even more asserts to hunt down bug 417.
28162 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
28163 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
28164 Add a log message to confirm that it is in fact unlikely.
28166 o Minor bugfixes (controller):
28167 - Make 'getinfo fingerprint' return a 551 error if we're not a
28168 server, so we match what the control spec claims we do. Reported
28170 - Fix a typo in an error message when extendcircuit fails that
28171 caused us to not follow the \r\n-based delimiter protocol. Reported
28174 o Code simplifications and refactoring:
28175 - Stop passing around circuit_t and crypt_path_t pointers that are
28176 implicit in other procedure arguments.
28177 - Drop the old code to choke directory connections when the
28178 corresponding OR connections got full: thanks to the cell queue
28179 feature, OR conns don't get full any more.
28180 - Make dns_resolve() handle attaching connections to circuits
28181 properly, so the caller doesn't have to.
28182 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
28183 - Keep the connection array as a dynamic smartlist_t, rather than as
28184 a fixed-sized array. This is important, as the number of connections
28185 is becoming increasingly decoupled from the number of sockets.
28188 Changes in version 0.1.2.14 - 2007-05-25
28189 Tor 0.1.2.14 changes the addresses of two directory authorities (this
28190 change especially affects those who serve or use hidden services),
28191 and fixes several other crash- and security-related bugs.
28193 o Directory authority changes:
28194 - Two directory authorities (moria1 and moria2) just moved to new
28195 IP addresses. This change will particularly affect those who serve
28196 or use hidden services.
28198 o Major bugfixes (crashes):
28199 - If a directory server runs out of space in the connection table
28200 as it's processing a begin_dir request, it will free the exit stream
28201 but leave it attached to the circuit, leading to unpredictable
28202 behavior. (Reported by seeess, fixes bug 425.)
28203 - Fix a bug in dirserv_remove_invalid() that would cause authorities
28204 to corrupt memory under some really unlikely scenarios.
28205 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
28206 - Avoid segfaults when reading from mmaped descriptor file. (Reported
28209 o Major bugfixes (security):
28210 - When choosing an entry guard for a circuit, avoid using guards
28211 that are in the same family as the chosen exit -- not just guards
28212 that are exactly the chosen exit. (Reported by lodger.)
28214 o Major bugfixes (resource management):
28215 - If a directory authority is down, skip it when deciding where to get
28216 networkstatus objects or descriptors. Otherwise we keep asking
28217 every 10 seconds forever. Fixes bug 384.
28218 - Count it as a failure if we fetch a valid network-status but we
28219 don't want to keep it. Otherwise we'll keep fetching it and keep
28220 not wanting to keep it. Fixes part of bug 422.
28221 - If all of our dirservers have given us bad or no networkstatuses
28222 lately, then stop hammering them once per minute even when we
28223 think they're failed. Fixes another part of bug 422.
28226 - Actually set the purpose correctly for descriptors inserted with
28227 purpose=controller.
28228 - When we have k non-v2 authorities in our DirServer config,
28229 we ignored the last k authorities in the list when updating our
28231 - Correctly back-off from requesting router descriptors that we are
28232 having a hard time downloading.
28233 - Read resolv.conf files correctly on platforms where read() returns
28234 partial results on small file reads.
28235 - Don't rebuild the entire router store every time we get 32K of
28236 routers: rebuild it when the journal gets very large, or when
28237 the gaps in the store get very large.
28240 - When routers publish SVN revisions in their router descriptors,
28241 authorities now include those versions correctly in networkstatus
28243 - Warn when using a version of libevent before 1.3b to run a server on
28244 OSX or BSD: these versions interact badly with userspace threads.
28247 Changes in version 0.1.2.13 - 2007-04-24
28248 This release features some major anonymity fixes, such as safer path
28249 selection; better client performance; faster bootstrapping, better
28250 address detection, and better DNS support for servers; write limiting as
28251 well as read limiting to make servers easier to run; and a huge pile of
28252 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
28254 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
28255 of the Freenode IRC network, remembering his patience and vision for
28256 free speech on the Internet.
28259 - Fix a memory leak when we ask for "all" networkstatuses and we
28260 get one we don't recognize.
28261 - Add more asserts to hunt down bug 417.
28262 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
28265 Changes in version 0.1.2.12-rc - 2007-03-16
28267 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
28268 directory information requested inside Tor connections (i.e. via
28269 begin_dir cells). It only triggered when the same connection was
28270 serving other data at the same time. Reported by seeess.
28273 - When creating a circuit via the controller, send a 'launched'
28274 event when we're done, so we follow the spec better.
28277 Changes in version 0.1.2.11-rc - 2007-03-15
28278 o Minor bugfixes (controller), reported by daejees:
28279 - Correct the control spec to match how the code actually responds
28280 to 'getinfo addr-mappings/*'.
28281 - The control spec described a GUARDS event, but the code
28282 implemented a GUARD event. Standardize on GUARD, but let people
28283 ask for GUARDS too.
28286 Changes in version 0.1.2.10-rc - 2007-03-07
28287 o Major bugfixes (Windows):
28288 - Do not load the NT services library functions (which may not exist)
28289 just to detect if we're a service trying to shut down. Now we run
28290 on Win98 and friends again.
28292 o Minor bugfixes (other):
28293 - Clarify a couple of log messages.
28294 - Fix a misleading socks5 error number.
28297 Changes in version 0.1.2.9-rc - 2007-03-02
28298 o Major bugfixes (Windows):
28299 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
28300 of the usual GCC "%llu". This prevents a bug when saving 64-bit
28301 int configuration values: the high-order 32 bits would get
28302 truncated. In particular, we were being bitten by the default
28303 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
28304 and maybe also bug 397.)
28306 o Minor bugfixes (performance):
28307 - Use OpenSSL's AES implementation on platforms where it's faster.
28308 This could save us as much as 10% CPU usage.
28310 o Minor bugfixes (server):
28311 - Do not rotate onion key immediately after setting it for the first
28314 o Minor bugfixes (directory authorities):
28315 - Stop calling servers that have been hibernating for a long time
28316 "stable". Also, stop letting hibernating or obsolete servers affect
28317 uptime and bandwidth cutoffs.
28318 - Stop listing hibernating servers in the v1 directory.
28320 o Minor bugfixes (hidden services):
28321 - Upload hidden service descriptors slightly less often, to reduce
28322 load on authorities.
28324 o Minor bugfixes (other):
28325 - Fix an assert that could trigger if a controller quickly set then
28326 cleared EntryNodes. Bug found by Udo van den Heuvel.
28327 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
28329 - Fix a potential race condition in the rpm installer. Found by
28331 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
28332 of 2 as indicating that the server is completely bad; it sometimes
28333 means that the server is just bad for the request in question. (may fix
28334 the last of bug 326.)
28335 - Disable encrypted directory connections when we don't have a server
28336 descriptor for the destination. We'll get this working again in
28340 Changes in version 0.1.2.8-beta - 2007-02-26
28341 o Major bugfixes (crashes):
28342 - Stop crashing when the controller asks us to resetconf more than
28343 one config option at once. (Vidalia 0.0.11 does this.)
28344 - Fix a crash that happened on Win98 when we're given command-line
28345 arguments: don't try to load NT service functions from advapi32.dll
28346 except when we need them. (Bug introduced in 0.1.2.7-alpha;
28348 - Fix a longstanding obscure crash bug that could occur when
28349 we run out of DNS worker processes. (Resolves bug 390.)
28351 o Major bugfixes (hidden services):
28352 - Correctly detect whether hidden service descriptor downloads are
28353 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
28355 o Major bugfixes (accounting):
28356 - When we start during an accounting interval before it's time to wake
28357 up, remember to wake up at the correct time. (May fix bug 342.)
28359 o Minor bugfixes (controller):
28360 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
28361 clear the corresponding on_circuit variable, and remember later
28362 that we don't need to send a redundant CLOSED event. Resolves part
28364 - Report events where a resolve succeeded or where we got a socks
28365 protocol error correctly, rather than calling both of them
28367 - Change reported stream target addresses to IP consistently when
28368 we finally get the IP from an exit node.
28369 - Send log messages to the controller even if they happen to be very
28372 o Minor bugfixes (other):
28373 - Display correct results when reporting which versions are
28374 recommended, and how recommended they are. (Resolves bug 383.)
28375 - Improve our estimates for directory bandwidth to be less random:
28376 guess that an unrecognized directory will have the average bandwidth
28377 from all known directories, not that it will have the average
28378 bandwidth from those directories earlier than it on the list.
28379 - If we start a server with ClientOnly 1, then set ClientOnly to 0
28380 and hup, stop triggering an assert based on an empty onion_key.
28381 - On platforms with no working mmap() equivalent, don't warn the
28382 user when cached-routers doesn't exist.
28383 - Warn the user when mmap() [or its equivalent] fails for some reason
28384 other than file-not-found.
28385 - Don't warn the user when cached-routers.new doesn't exist: that's
28386 perfectly fine when starting up for the first time.
28387 - When EntryNodes are configured, rebuild the guard list to contain,
28388 in order: the EntryNodes that were guards before; the rest of the
28389 EntryNodes; the nodes that were guards before.
28390 - Mask out all signals in sub-threads; only the libevent signal
28391 handler should be processing them. This should prevent some crashes
28392 on some machines using pthreads. (Patch from coderman.)
28393 - Fix switched arguments on memset in the implementation of
28394 tor_munmap() for systems with no mmap() call.
28395 - When Tor receives a router descriptor that it asked for, but
28396 no longer wants (because it has received fresh networkstatuses
28397 in the meantime), do not warn the user. Cache the descriptor if
28398 we're a cache; drop it if we aren't.
28399 - Make earlier entry guards _really_ get retried when the network
28401 - On a malformed DNS reply, always give an error to the corresponding
28403 - Build with recent libevents on platforms that do not define the
28404 nonstandard types "u_int8_t" and friends.
28406 o Minor features (controller):
28407 - Warn the user when an application uses the obsolete binary v0
28408 control protocol. We're planning to remove support for it during
28409 the next development series, so it's good to give people some
28411 - Add STREAM_BW events to report per-entry-stream bandwidth
28412 use. (Patch from Robert Hogan.)
28413 - Rate-limit SIGNEWNYM signals in response to controllers that
28414 impolitely generate them for every single stream. (Patch from
28415 mwenge; closes bug 394.)
28416 - Make REMAP stream events have a SOURCE (cache or exit), and
28417 make them generated in every case where we get a successful
28418 connected or resolved cell.
28420 o Minor bugfixes (performance):
28421 - Call router_have_min_dir_info half as often. (This is showing up in
28422 some profiles, but not others.)
28423 - When using GCC, make log_debug never get called at all, and its
28424 arguments never get evaluated, when no debug logs are configured.
28425 (This is showing up in some profiles, but not others.)
28428 - Remove some never-implemented options. Mark PathlenCoinWeight as
28430 - Implement proposal 106: Stop requiring clients to have well-formed
28431 certificates; stop checking nicknames in certificates. (Clients
28432 have certificates so that they can look like Tor servers, but in
28433 the future we might want to allow them to look like regular TLS
28434 clients instead. Nicknames in certificates serve no purpose other
28435 than making our protocol easier to recognize on the wire.)
28436 - Revise messages on handshake failure again to be even more clear about
28437 which are incoming connections and which are outgoing.
28438 - Discard any v1 directory info that's over 1 month old (for
28439 directories) or over 1 week old (for running-routers lists).
28440 - Do not warn when individual nodes in the configuration's EntryNodes,
28441 ExitNodes, etc are down: warn only when all possible nodes
28442 are down. (Fixes bug 348.)
28443 - Always remove expired routers and networkstatus docs before checking
28444 whether we have enough information to build circuits. (Fixes
28446 - Put a lower-bound on MaxAdvertisedBandwidth.
28449 Changes in version 0.1.2.7-alpha - 2007-02-06
28450 o Major bugfixes (rate limiting):
28451 - Servers decline directory requests much more aggressively when
28452 they're low on bandwidth. Otherwise they end up queueing more and
28453 more directory responses, which can't be good for latency.
28454 - But never refuse directory requests from local addresses.
28455 - Fix a memory leak when sending a 503 response for a networkstatus
28457 - Be willing to read or write on local connections (e.g. controller
28458 connections) even when the global rate limiting buckets are empty.
28459 - If our system clock jumps back in time, don't publish a negative
28460 uptime in the descriptor. Also, don't let the global rate limiting
28461 buckets go absurdly negative.
28462 - Flush local controller connection buffers periodically as we're
28463 writing to them, so we avoid queueing 4+ megabytes of data before
28466 o Major bugfixes (NT services):
28467 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
28468 command-line flag so that admins can override the default by saying
28469 "tor --service install --user "SomeUser"". This will not affect
28470 existing installed services. Also, warn the user that the service
28471 will look for its configuration file in the service user's
28472 %appdata% directory. (We can't do the 'hardwire the user's appdata
28473 directory' trick any more, since we may not have read access to that
28476 o Major bugfixes (other):
28477 - Previously, we would cache up to 16 old networkstatus documents
28478 indefinitely, if they came from nontrusted authorities. Now we
28479 discard them if they are more than 10 days old.
28480 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
28482 - Detect and reject malformed DNS responses containing circular
28484 - If exits are rare enough that we're not marking exits as guards,
28485 ignore exit bandwidth when we're deciding the required bandwidth
28487 - When we're handling a directory connection tunneled over Tor,
28488 don't fill up internal memory buffers with all the data we want
28489 to tunnel; instead, only add it if the OR connection that will
28490 eventually receive it has some room for it. (This can lead to
28491 slowdowns in tunneled dir connections; a better solution will have
28492 to wait for 0.2.0.)
28494 o Minor bugfixes (dns):
28495 - Add some defensive programming to eventdns.c in an attempt to catch
28496 possible memory-stomping bugs.
28497 - Detect and reject DNS replies containing IPv4 or IPv6 records with
28498 an incorrect number of bytes. (Previously, we would ignore the
28500 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
28501 in the correct order, and doesn't crash.
28502 - Free memory held in recently-completed DNS lookup attempts on exit.
28503 This was not a memory leak, but may have been hiding memory leaks.
28504 - Handle TTL values correctly on reverse DNS lookups.
28505 - Treat failure to parse resolv.conf as an error.
28507 o Minor bugfixes (other):
28508 - Fix crash with "tor --list-fingerprint" (reported by seeess).
28509 - When computing clock skew from directory HTTP headers, consider what
28510 time it was when we finished asking for the directory, not what
28512 - Expire socks connections if they spend too long waiting for the
28513 handshake to finish. Previously we would let them sit around for
28514 days, if the connecting application didn't close them either.
28515 - And if the socks handshake hasn't started, don't send a
28516 "DNS resolve socks failed" handshake reply; just close it.
28517 - Stop using C functions that OpenBSD's linker doesn't like.
28518 - Don't launch requests for descriptors unless we have networkstatuses
28519 from at least half of the authorities. This delays the first
28520 download slightly under pathological circumstances, but can prevent
28521 us from downloading a bunch of descriptors we don't need.
28522 - Do not log IPs with TLS failures for incoming TLS
28523 connections. (Fixes bug 382.)
28524 - If the user asks to use invalid exit nodes, be willing to use
28526 - Stop using the reserved ac_cv namespace in our configure script.
28527 - Call stat() slightly less often; use fstat() when possible.
28528 - Refactor the way we handle pending circuits when an OR connection
28529 completes or fails, in an attempt to fix a rare crash bug.
28530 - Only rewrite a conn's address based on X-Forwarded-For: headers
28531 if it's a parseable public IP address; and stop adding extra quotes
28532 to the resulting address.
28535 - Weight directory requests by advertised bandwidth. Now we can
28536 let servers enable write limiting but still allow most clients to
28537 succeed at their directory requests. (We still ignore weights when
28538 choosing a directory authority; I hope this is a feature.)
28541 - Create a new file ReleaseNotes which was the old ChangeLog. The
28542 new ChangeLog file now includes the summaries for all development
28544 - Check for addresses with invalid characters at the exit as well
28545 as at the client, and warn less verbosely when they fail. You can
28546 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28547 - Adapt a patch from goodell to let the contrib/exitlist script
28548 take arguments rather than require direct editing.
28549 - Inform the server operator when we decide not to advertise a
28550 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28551 was confusing Zax, so now we're hopefully more helpful.
28552 - Bring us one step closer to being able to establish an encrypted
28553 directory tunnel without knowing a descriptor first. Still not
28554 ready yet. As part of the change, now assume we can use a
28555 create_fast cell if we don't know anything about a router.
28556 - Allow exit nodes to use nameservers running on ports other than 53.
28557 - Servers now cache reverse DNS replies.
28558 - Add an --ignore-missing-torrc command-line option so that we can
28559 get the "use sensible defaults if the configuration file doesn't
28560 exist" behavior even when specifying a torrc location on the command
28563 o Minor features (controller):
28564 - Track reasons for OR connection failure; make these reasons
28565 available via the controller interface. (Patch from Mike Perry.)
28566 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28567 can learn when clients are sending malformed hostnames to Tor.
28568 - Clean up documentation for controller status events.
28569 - Add a REMAP status to stream events to note that a stream's
28570 address has changed because of a cached address or a MapAddress
28574 Changes in version 0.1.2.6-alpha - 2007-01-09
28576 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28577 connection handles more than 4 gigs in either direction, we crash.
28578 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28579 advertised exit node, somebody might try to exit from us when
28580 we're bootstrapping and before we've built our descriptor yet.
28581 Refuse the connection rather than crashing.
28584 - Warn if we (as a server) find that we've resolved an address that we
28585 weren't planning to resolve.
28586 - Warn that using select() on any libevent version before 1.1 will be
28587 unnecessarily slow (even for select()).
28588 - Flush ERR-level controller status events just like we currently
28589 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28590 the controller from learning about current events.
28592 o Minor features (more controller status events):
28593 - Implement EXTERNAL_ADDRESS server status event so controllers can
28594 learn when our address changes.
28595 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28596 can learn when directories reject our descriptor.
28597 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28598 can learn when a client application is speaking a non-socks protocol
28600 - Implement DANGEROUS_SOCKS client status event so controllers
28601 can learn when a client application is leaking DNS addresses.
28602 - Implement BUG general status event so controllers can learn when
28603 Tor is unhappy about its internal invariants.
28604 - Implement CLOCK_SKEW general status event so controllers can learn
28605 when Tor thinks the system clock is set incorrectly.
28606 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28607 server status events so controllers can learn when their descriptors
28608 are accepted by a directory.
28609 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28610 server status events so controllers can learn about Tor's progress in
28611 deciding whether it's reachable from the outside.
28612 - Implement BAD_LIBEVENT general status event so controllers can learn
28613 when we have a version/method combination in libevent that needs to
28615 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28616 and DNS_USELESS server status events so controllers can learn
28617 about changes to DNS server status.
28619 o Minor features (directory):
28620 - Authorities no longer recommend exits as guards if this would shift
28621 too much load to the exit nodes.
28624 Changes in version 0.1.2.5-alpha - 2007-01-06
28626 - Enable write limiting as well as read limiting. Now we sacrifice
28627 capacity if we're pushing out lots of directory traffic, rather
28628 than overrunning the user's intended bandwidth limits.
28629 - Include TLS overhead when counting bandwidth usage; previously, we
28630 would count only the bytes sent over TLS, but not the bytes used
28632 - Support running the Tor service with a torrc not in the same
28633 directory as tor.exe and default to using the torrc located in
28634 the %appdata%\Tor\ of the user who installed the service. Patch
28636 - Servers now check for the case when common DNS requests are going to
28637 wildcarded addresses (i.e. all getting the same answer), and change
28638 their exit policy to reject *:* if it's happening.
28639 - Implement BEGIN_DIR cells, so we can connect to the directory
28640 server via TLS to do encrypted directory requests rather than
28641 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28642 config options if you like.
28644 o Minor features (config and docs):
28645 - Start using the state file to store bandwidth accounting data:
28646 the bw_accounting file is now obsolete. We'll keep generating it
28647 for a while for people who are still using 0.1.2.4-alpha.
28648 - Try to batch changes to the state file so that we do as few
28649 disk writes as possible while still storing important things in
28651 - The state file and the bw_accounting file get saved less often when
28652 the AvoidDiskWrites config option is set.
28653 - Make PIDFile work on Windows (untested).
28654 - Add internal descriptions for a bunch of configuration options:
28655 accessible via controller interface and in comments in saved
28657 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28658 NNTP by default, so this seems like a sensible addition.
28659 - Clients now reject hostnames with invalid characters. This should
28660 avoid some inadvertent info leaks. Add an option
28661 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28662 is running a private network with hosts called @, !, and #.
28663 - Add a maintainer script to tell us which options are missing
28664 documentation: "make check-docs".
28665 - Add a new address-spec.txt document to describe our special-case
28666 addresses: .exit, .onion, and .noconnnect.
28668 o Minor features (DNS):
28669 - Ongoing work on eventdns infrastructure: now it has dns server
28670 and ipv6 support. One day Tor will make use of it.
28671 - Add client-side caching for reverse DNS lookups.
28672 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28673 - When we change nameservers or IP addresses, reset and re-launch
28674 our tests for DNS hijacking.
28676 o Minor features (directory):
28677 - Authorities now specify server versions in networkstatus. This adds
28678 about 2% to the size of compressed networkstatus docs, and allows
28679 clients to tell which servers support BEGIN_DIR and which don't.
28680 The implementation is forward-compatible with a proposed future
28681 protocol version scheme not tied to Tor versions.
28682 - DirServer configuration lines now have an orport= option so
28683 clients can open encrypted tunnels to the authorities without
28684 having downloaded their descriptors yet. Enabled for moria1,
28685 moria2, tor26, and lefkada now in the default configuration.
28686 - Directory servers are more willing to send a 503 "busy" if they
28687 are near their write limit, especially for v1 directory requests.
28688 Now they can use their limited bandwidth for actual Tor traffic.
28689 - Clients track responses with status 503 from dirservers. After a
28690 dirserver has given us a 503, we try not to use it until an hour has
28691 gone by, or until we have no dirservers that haven't given us a 503.
28692 - When we get a 503 from a directory, and we're not a server, we don't
28693 count the failure against the total number of failures allowed
28694 for the thing we're trying to download.
28695 - Report X-Your-Address-Is correctly from tunneled directory
28696 connections; don't report X-Your-Address-Is when it's an internal
28697 address; and never believe reported remote addresses when they're
28699 - Protect against an unlikely DoS attack on directory servers.
28700 - Add a BadDirectory flag to network status docs so that authorities
28701 can (eventually) tell clients about caches they believe to be
28704 o Minor features (controller):
28705 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28706 - Reimplement GETINFO so that info/names stays in sync with the
28708 - Implement "GETINFO fingerprint".
28709 - Implement "SETEVENTS GUARD" so controllers can get updates on
28710 entry guard status as it changes.
28712 o Minor features (clean up obsolete pieces):
28713 - Remove some options that have been deprecated since at least
28714 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28715 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28716 to set log options.
28717 - We no longer look for identity and onion keys in "identity.key" and
28718 "onion.key" -- these were replaced by secret_id_key and
28719 secret_onion_key in 0.0.8pre1.
28720 - We no longer require unrecognized directory entries to be
28723 o Major bugfixes (security):
28724 - Stop sending the HttpProxyAuthenticator string to directory
28725 servers when directory connections are tunnelled through Tor.
28726 - Clients no longer store bandwidth history in the state file.
28727 - Do not log introduction points for hidden services if SafeLogging
28729 - When generating bandwidth history, round down to the nearest
28730 1k. When storing accounting data, round up to the nearest 1k.
28731 - When we're running as a server, remember when we last rotated onion
28732 keys, so that we will rotate keys once they're a week old even if
28733 we never stay up for a week ourselves.
28735 o Major bugfixes (other):
28736 - Fix a longstanding bug in eventdns that prevented the count of
28737 timed-out resolves from ever being reset. This bug caused us to
28738 give up on a nameserver the third time it timed out, and try it
28739 10 seconds later... and to give up on it every time it timed out
28741 - Take out the '5 second' timeout from the connection retry
28742 schedule. Now the first connect attempt will wait a full 10
28743 seconds before switching to a new circuit. Perhaps this will help
28744 a lot. Based on observations from Mike Perry.
28745 - Fix a bug on the Windows implementation of tor_mmap_file() that
28746 would prevent the cached-routers file from ever loading. Reported
28750 - Fix an assert failure when a directory authority sets
28751 AuthDirRejectUnlisted and then receives a descriptor from an
28752 unlisted router. Reported by seeess.
28753 - Avoid a double-free when parsing malformed DirServer lines.
28754 - Fix a bug when a BSD-style PF socket is first used. Patch from
28756 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
28757 to resolve an address at a given exit node even when they ask for
28759 - Servers no longer ever list themselves in their "family" line,
28760 even if configured to do so. This makes it easier to configure
28761 family lists conveniently.
28762 - When running as a server, don't fall back to 127.0.0.1 when no
28763 nameservers are configured in /etc/resolv.conf; instead, make the
28764 user fix resolv.conf or specify nameservers explicitly. (Resolves
28766 - Stop accepting certain malformed ports in configured exit policies.
28767 - Don't re-write the fingerprint file every restart, unless it has
28769 - Stop warning when a single nameserver fails: only warn when _all_ of
28770 our nameservers have failed. Also, when we only have one nameserver,
28771 raise the threshold for deciding that the nameserver is dead.
28772 - Directory authorities now only decide that routers are reachable
28773 if their identity keys are as expected.
28774 - When the user uses bad syntax in the Log config line, stop
28775 suggesting other bad syntax as a replacement.
28776 - Correctly detect ipv6 DNS capability on OpenBSD.
28778 o Minor bugfixes (controller):
28779 - Report the circuit number correctly in STREAM CLOSED events. Bug
28780 reported by Mike Perry.
28781 - Do not report bizarre values for results of accounting GETINFOs
28782 when the last second's write or read exceeds the allotted bandwidth.
28783 - Report "unrecognized key" rather than an empty string when the
28784 controller tries to fetch a networkstatus that doesn't exist.
28787 Changes in version 0.1.1.26 - 2006-12-14
28788 o Security bugfixes:
28789 - Stop sending the HttpProxyAuthenticator string to directory
28790 servers when directory connections are tunnelled through Tor.
28791 - Clients no longer store bandwidth history in the state file.
28792 - Do not log introduction points for hidden services if SafeLogging
28796 - Fix an assert failure when a directory authority sets
28797 AuthDirRejectUnlisted and then receives a descriptor from an
28798 unlisted router (reported by seeess).
28801 Changes in version 0.1.2.4-alpha - 2006-12-03
28803 - Add support for using natd; this allows FreeBSDs earlier than
28804 5.1.2 to have ipfw send connections through Tor without using
28805 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
28808 - Make all connections to addresses of the form ".noconnect"
28809 immediately get closed. This lets application/controller combos
28810 successfully test whether they're talking to the same Tor by
28811 watching for STREAM events.
28812 - Make cross.sh cross-compilation script work even when autogen.sh
28813 hasn't been run. (Patch from Michael Mohr.)
28814 - Statistics dumped by -USR2 now include a breakdown of public key
28815 operations, for profiling.
28818 - Fix a major leak when directory authorities parse their
28819 approved-routers list, a minor memory leak when we fail to pick
28820 an exit node, and a few rare leaks on errors.
28821 - Handle TransPort connections even when the server sends data before
28822 the client sends data. Previously, the connection would just hang
28823 until the client sent data. (Patch from tup based on patch from
28825 - Avoid assert failure when our cached-routers file is empty on
28829 - Don't log spurious warnings when we see a circuit close reason we
28830 don't recognize; it's probably just from a newer version of Tor.
28831 - Have directory authorities allow larger amounts of drift in uptime
28832 without replacing the server descriptor: previously, a server that
28833 restarted every 30 minutes could have 48 "interesting" descriptors
28835 - Start linking to the Tor specification and Tor reference manual
28836 correctly in the Windows installer.
28837 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28838 Tor/Privoxy we also uninstall Vidalia.
28839 - Resume building on Irix64, and fix a lot of warnings from its
28840 MIPSpro C compiler.
28841 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
28842 when we're running as a client.
28845 Changes in version 0.1.1.25 - 2006-11-04
28847 - When a client asks us to resolve (rather than connect to)
28848 an address, and we have a cached answer, give them the cached
28849 answer. Previously, we would give them no answer at all.
28850 - We were building exactly the wrong circuits when we predict
28851 hidden service requirements, meaning Tor would have to build all
28852 its circuits on demand.
28853 - If none of our live entry guards have a high uptime, but we
28854 require a guard with a high uptime, try adding a new guard before
28855 we give up on the requirement. This patch should make long-lived
28856 connections more stable on average.
28857 - When testing reachability of our DirPort, don't launch new
28858 tests when there's already one in progress -- unreachable
28859 servers were stacking up dozens of testing streams.
28861 o Security bugfixes:
28862 - When the user sends a NEWNYM signal, clear the client-side DNS
28863 cache too. Otherwise we continue to act on previous information.
28866 - Avoid a memory corruption bug when creating a hash table for
28868 - Avoid possibility of controller-triggered crash when misusing
28869 certain commands from a v0 controller on platforms that do not
28870 handle printf("%s",NULL) gracefully.
28871 - Avoid infinite loop on unexpected controller input.
28872 - Don't log spurious warnings when we see a circuit close reason we
28873 don't recognize; it's probably just from a newer version of Tor.
28874 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28875 Tor/Privoxy we also uninstall Vidalia.
28878 Changes in version 0.1.2.3-alpha - 2006-10-29
28880 - Prepare for servers to publish descriptors less often: never
28881 discard a descriptor simply for being too old until either it is
28882 recommended by no authorities, or until we get a better one for
28883 the same router. Make caches consider retaining old recommended
28884 routers for even longer.
28885 - If most authorities set a BadExit flag for a server, clients
28886 don't think of it as a general-purpose exit. Clients only consider
28887 authorities that advertise themselves as listing bad exits.
28888 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
28889 headers for content, so that we can work better in the presence of
28890 caching HTTP proxies.
28891 - Allow authorities to list nodes as bad exits by fingerprint or by
28894 o Minor features, controller:
28895 - Add a REASON field to CIRC events; for backward compatibility, this
28896 field is sent only to controllers that have enabled the extended
28897 event format. Also, add additional reason codes to explain why
28898 a given circuit has been destroyed or truncated. (Patches from
28900 - Add a REMOTE_REASON field to extended CIRC events to tell the
28901 controller about why a remote OR told us to close a circuit.
28902 - Stream events also now have REASON and REMOTE_REASON fields,
28903 working much like those for circuit events.
28904 - There's now a GETINFO ns/... field so that controllers can ask Tor
28905 about the current status of a router.
28906 - A new event type "NS" to inform a controller when our opinion of
28907 a router's status has changed.
28908 - Add a GETINFO events/names and GETINFO features/names so controllers
28909 can tell which events and features are supported.
28910 - A new CLEARDNSCACHE signal to allow controllers to clear the
28911 client-side DNS cache without expiring circuits.
28913 o Security bugfixes:
28914 - When the user sends a NEWNYM signal, clear the client-side DNS
28915 cache too. Otherwise we continue to act on previous information.
28918 - Avoid sending junk to controllers or segfaulting when a controller
28919 uses EVENT_NEW_DESC with verbose nicknames.
28920 - Stop triggering asserts if the controller tries to extend hidden
28921 service circuits (reported by mwenge).
28922 - Avoid infinite loop on unexpected controller input.
28923 - When the controller does a "GETINFO network-status", tell it
28924 about even those routers whose descriptors are very old, and use
28925 long nicknames where appropriate.
28926 - Change NT service functions to be loaded on demand. This lets us
28927 build with MinGW without breaking Tor for Windows 98 users.
28928 - Do DirPort reachability tests less often, since a single test
28929 chews through many circuits before giving up.
28930 - In the hidden service example in torrc.sample, stop recommending
28931 esoteric and discouraged hidden service options.
28932 - When stopping an NT service, wait up to 10 sec for it to actually
28933 stop. Patch from Matt Edman; resolves bug 295.
28934 - Fix handling of verbose nicknames with ORCONN controller events:
28935 make them show up exactly when requested, rather than exactly when
28937 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
28938 printing a duplicate "$" in the keys we send (reported by mwenge).
28939 - Correctly set maximum connection limit on Cygwin. (This time
28941 - Try to detect Windows correctly when cross-compiling.
28942 - Detect the size of the routers file correctly even if it is
28943 corrupted (on systems without mmap) or not page-aligned (on systems
28944 with mmap). This bug was harmless.
28945 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
28946 to open a stream fails; now we do in more cases. This should
28947 make clients able to find a good exit faster in some cases, since
28948 unhandleable requests will now get an error rather than timing out.
28949 - Resolve two memory leaks when rebuilding the on-disk router cache
28950 (reported by fookoowa).
28951 - Clean up minor code warnings suggested by the MIPSpro C compiler,
28952 and reported by some Centos users.
28953 - Controller signals now work on non-Unix platforms that don't define
28954 SIGUSR1 and SIGUSR2 the way we expect.
28955 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
28956 values before failing, and always enables eventdns.
28957 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
28958 Try to fix this in configure.in by checking for most functions
28959 before we check for libevent.
28962 Changes in version 0.1.2.2-alpha - 2006-10-07
28964 - Make our async eventdns library on-by-default for Tor servers,
28965 and plan to deprecate the separate dnsworker threads.
28966 - Add server-side support for "reverse" DNS lookups (using PTR
28967 records so clients can determine the canonical hostname for a given
28968 IPv4 address). Only supported by servers using eventdns; servers
28969 now announce in their descriptors whether they support eventdns.
28970 - Specify and implement client-side SOCKS5 interface for reverse DNS
28971 lookups (see doc/socks-extensions.txt).
28972 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
28973 connect to directory servers through Tor. Previously, clients needed
28974 to find Tor exits to make private connections to directory servers.
28975 - Avoid choosing Exit nodes for entry or middle hops when the
28976 total bandwidth available from non-Exit nodes is much higher than
28977 the total bandwidth available from Exit nodes.
28978 - Workaround for name servers (like Earthlink's) that hijack failing
28979 DNS requests and replace the no-such-server answer with a "helpful"
28980 redirect to an advertising-driven search portal. Also work around
28981 DNS hijackers who "helpfully" decline to hijack known-invalid
28982 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
28983 lets you turn it off.
28984 - Send out a burst of long-range padding cells once we've established
28985 that we're reachable. Spread them over 4 circuits, so hopefully
28986 a few will be fast. This exercises our bandwidth and bootstraps
28987 us into the directory more quickly.
28989 o New/improved config options:
28990 - Add new config option "ResolvConf" to let the server operator
28991 choose an alternate resolve.conf file when using eventdns.
28992 - Add an "EnforceDistinctSubnets" option to control our "exclude
28993 servers on the same /16" behavior. It's still on by default; this
28994 is mostly for people who want to operate private test networks with
28995 all the machines on the same subnet.
28996 - If one of our entry guards is on the ExcludeNodes list, or the
28997 directory authorities don't think it's a good guard, treat it as
28998 if it were unlisted: stop using it as a guard, and throw it off
28999 the guards list if it stays that way for a long time.
29000 - Allow directory authorities to be marked separately as authorities
29001 for the v1 directory protocol, the v2 directory protocol, and
29002 as hidden service directories, to make it easier to retire old
29003 authorities. V1 authorities should set "HSAuthoritativeDir 1"
29004 to continue being hidden service authorities too.
29005 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
29007 o Minor features, controller:
29008 - Fix CIRC controller events so that controllers can learn the
29009 identity digests of non-Named servers used in circuit paths.
29010 - Let controllers ask for more useful identifiers for servers. Instead
29011 of learning identity digests for un-Named servers and nicknames
29012 for Named servers, the new identifiers include digest, nickname,
29013 and indication of Named status. Off by default; see control-spec.txt
29014 for more information.
29015 - Add a "getinfo address" controller command so it can display Tor's
29016 best guess to the user.
29017 - New controller event to alert the controller when our server
29018 descriptor has changed.
29019 - Give more meaningful errors on controller authentication failure.
29021 o Minor features, other:
29022 - When asked to resolve a hostname, don't use non-exit servers unless
29023 requested to do so. This allows servers with broken DNS to be
29024 useful to the network.
29025 - Divide eventdns log messages into warn and info messages.
29026 - Reserve the nickname "Unnamed" for routers that can't pick
29027 a hostname: any router can call itself Unnamed; directory
29028 authorities will never allocate Unnamed to any particular router;
29029 clients won't believe that any router is the canonical Unnamed.
29030 - Only include function names in log messages for info/debug messages.
29031 For notice/warn/err, the content of the message should be clear on
29032 its own, and printing the function name only confuses users.
29033 - Avoid some false positives during reachability testing: don't try
29034 to test via a server that's on the same /24 as us.
29035 - If we fail to build a circuit to an intended enclave, and it's
29036 not mandatory that we use that enclave, stop wanting it.
29037 - When eventdns is enabled, allow multithreaded builds on NetBSD and
29038 OpenBSD. (We had previously disabled threads on these platforms
29039 because they didn't have working thread-safe resolver functions.)
29041 o Major bugfixes, anonymity/security:
29042 - If a client asked for a server by name, and there's a named server
29043 in our network-status but we don't have its descriptor yet, we
29044 could return an unnamed server instead.
29045 - Fix NetBSD bug that could allow someone to force uninitialized RAM
29046 to be sent to a server's DNS resolver. This only affects NetBSD
29047 and other platforms that do not bounds-check tolower().
29048 - Reject (most) attempts to use Tor circuits with length one. (If
29049 many people start using Tor as a one-hop proxy, exit nodes become
29050 a more attractive target for compromise.)
29051 - Just because your DirPort is open doesn't mean people should be
29052 able to remotely teach you about hidden service descriptors. Now
29053 only accept rendezvous posts if you've got HSAuthoritativeDir set.
29055 o Major bugfixes, other:
29056 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
29057 - When a client asks the server to resolve (not connect to)
29058 an address, and it has a cached answer, give them the cached answer.
29059 Previously, the server would give them no answer at all.
29060 - Allow really slow clients to not hang up five minutes into their
29061 directory downloads (suggested by Adam J. Richter).
29062 - We were building exactly the wrong circuits when we anticipated
29063 hidden service requirements, meaning Tor would have to build all
29064 its circuits on demand.
29065 - Avoid crashing when we mmap a router cache file of size 0.
29066 - When testing reachability of our DirPort, don't launch new
29067 tests when there's already one in progress -- unreachable
29068 servers were stacking up dozens of testing streams.
29070 o Minor bugfixes, correctness:
29071 - If we're a directory mirror and we ask for "all" network status
29072 documents, we would discard status documents from authorities
29073 we don't recognize.
29074 - Avoid a memory corruption bug when creating a hash table for
29076 - Avoid controller-triggered crash when misusing certain commands
29077 from a v0 controller on platforms that do not handle
29078 printf("%s",NULL) gracefully.
29079 - Don't crash when a controller sends a third argument to an
29080 "extendcircuit" request.
29081 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29082 response; fix error code when "getinfo dir/status/" fails.
29083 - Avoid crash when telling controller stream-status and a stream
29085 - Patch from Adam Langley to fix assert() in eventdns.c.
29086 - Fix a debug log message in eventdns to say "X resolved to Y"
29087 instead of "X resolved to X".
29088 - Make eventdns give strings for DNS errors, not just error numbers.
29089 - Track unreachable entry guards correctly: don't conflate
29090 'unreachable by us right now' with 'listed as down by the directory
29091 authorities'. With the old code, if a guard was unreachable by
29092 us but listed as running, it would clog our guard list forever.
29093 - Behave correctly in case we ever have a network with more than
29094 2GB/s total advertised capacity.
29095 - Make TrackExitHosts case-insensitive, and fix the behavior of
29096 ".suffix" TrackExitHosts items to avoid matching in the middle of
29098 - Finally fix the openssl warnings from newer gccs that believe that
29099 ignoring a return value is okay, but casting a return value and
29100 then ignoring it is a sign of madness.
29101 - Prevent the contrib/exitlist script from printing the same
29102 result more than once.
29103 - Patch from Steve Hildrey: Generate network status correctly on
29104 non-versioning dirservers.
29105 - Don't listen to the X-Your-Address-Is hint if you did the lookup
29106 via Tor; otherwise you'll think you're the exit node's IP address.
29108 o Minor bugfixes, performance:
29109 - Two small performance improvements on parsing descriptors.
29110 - Major performance improvement on inserting descriptors: change
29111 algorithm from O(n^2) to O(n).
29112 - Make the common memory allocation path faster on machines where
29113 malloc(0) returns a pointer.
29114 - Start remembering X-Your-Address-Is directory hints even if you're
29115 a client, so you can become a server more smoothly.
29116 - Avoid duplicate entries on MyFamily line in server descriptor.
29118 o Packaging, features:
29119 - Remove architecture from OS X builds. The official builds are
29120 now universal binaries.
29121 - The Debian package now uses --verify-config when (re)starting,
29122 to distinguish configuration errors from other errors.
29123 - Update RPMs to require libevent 1.1b.
29125 o Packaging, bugfixes:
29126 - Patches so Tor builds with MinGW on Windows.
29127 - Patches so Tor might run on Cygwin again.
29128 - Resume building on non-gcc compilers and ancient gcc. Resume
29129 building with the -O0 compile flag. Resume building cleanly on
29131 - Run correctly on OS X platforms with case-sensitive filesystems.
29132 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
29133 - Add autoconf checks so Tor can build on Solaris x86 again.
29136 - Documented (and renamed) ServerDNSSearchDomains and
29137 ServerDNSResolvConfFile options.
29138 - Be clearer that the *ListenAddress directives can be repeated
29142 Changes in version 0.1.1.24 - 2006-09-29
29144 - Allow really slow clients to not hang up five minutes into their
29145 directory downloads (suggested by Adam J. Richter).
29146 - Fix major performance regression from 0.1.0.x: instead of checking
29147 whether we have enough directory information every time we want to
29148 do something, only check when the directory information has changed.
29149 This should improve client CPU usage by 25-50%.
29150 - Don't crash if, after a server has been running for a while,
29151 it can't resolve its hostname.
29154 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29155 - Don't crash when the controller receives a third argument to an
29156 "extendcircuit" request.
29157 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29158 response; fix error code when "getinfo dir/status/" fails.
29159 - Fix configure.in to not produce broken configure files with
29160 more recent versions of autoconf. Thanks to Clint for his auto*
29162 - Fix security bug on NetBSD that could allow someone to force
29163 uninitialized RAM to be sent to a server's DNS resolver. This
29164 only affects NetBSD and other platforms that do not bounds-check
29166 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
29167 methods: these are known to be buggy.
29168 - If we're a directory mirror and we ask for "all" network status
29169 documents, we would discard status documents from authorities
29170 we don't recognize.
29173 Changes in version 0.1.2.1-alpha - 2006-08-27
29175 - Add "eventdns" async dns library from Adam Langley, tweaked to
29176 build on OSX and Windows. Only enabled if you pass the
29177 --enable-eventdns argument to configure.
29178 - Allow servers with no hostname or IP address to learn their
29179 IP address by asking the directory authorities. This code only
29180 kicks in when you would normally have exited with a "no address"
29181 error. Nothing's authenticated, so use with care.
29182 - Rather than waiting a fixed amount of time between retrying
29183 application connections, we wait only 5 seconds for the first,
29184 10 seconds for the second, and 15 seconds for each retry after
29185 that. Hopefully this will improve the expected user experience.
29186 - Patch from Tup to add support for transparent AP connections:
29187 this basically bundles the functionality of trans-proxy-tor
29188 into the Tor mainline. Now hosts with compliant pf/netfilter
29189 implementations can redirect TCP connections straight to Tor
29190 without diverting through SOCKS. Needs docs.
29191 - Busy directory servers save lots of memory by spooling server
29192 descriptors, v1 directories, and v2 networkstatus docs to buffers
29193 as needed rather than en masse. Also mmap the cached-routers
29194 files, so we don't need to keep the whole thing in memory too.
29195 - Automatically avoid picking more than one node from the same
29196 /16 network when constructing a circuit.
29197 - Revise and clean up the torrc.sample that we ship with; add
29198 a section for BandwidthRate and BandwidthBurst.
29201 - Split circuit_t into origin_circuit_t and or_circuit_t, and
29202 split connection_t into edge, or, dir, control, and base structs.
29203 These will save quite a bit of memory on busy servers, and they'll
29204 also help us track down bugs in the code and bugs in the spec.
29205 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
29206 or later. Log when we are doing this, so we can diagnose it when
29207 it fails. (Also, recommend libevent 1.1b for kqueue and
29208 win32 methods; deprecate libevent 1.0b harder; make libevent
29209 recommendation system saner.)
29210 - Start being able to build universal binaries on OS X (thanks
29212 - Export the default exit policy via the control port, so controllers
29213 don't need to guess what it is / will be later.
29214 - Add a man page entry for ProtocolWarnings.
29215 - Add TestVia config option to the man page.
29216 - Remove even more protocol-related warnings from Tor server logs,
29217 such as bad TLS handshakes and malformed begin cells.
29218 - Stop fetching descriptors if you're not a dir mirror and you
29219 haven't tried to establish any circuits lately. [This currently
29220 causes some dangerous behavior, because when you start up again
29221 you'll use your ancient server descriptors.]
29222 - New DirPort behavior: if you have your dirport set, you download
29223 descriptors aggressively like a directory mirror, whether or not
29224 your ORPort is set.
29225 - Get rid of the router_retry_connections notion. Now routers
29226 no longer try to rebuild long-term connections to directory
29227 authorities, and directory authorities no longer try to rebuild
29228 long-term connections to all servers. We still don't hang up
29229 connections in these two cases though -- we need to look at it
29230 more carefully to avoid flapping, and we likely need to wait til
29231 0.1.1.x is obsolete.
29232 - Drop compatibility with obsolete Tors that permit create cells
29233 to have the wrong circ_id_type.
29234 - Re-enable per-connection rate limiting. Get rid of the "OP
29235 bandwidth" concept. Lay groundwork for "bandwidth classes" --
29236 separate global buckets that apply depending on what sort of conn
29238 - Start publishing one minute or so after we find our ORPort
29239 to be reachable. This will help reduce the number of descriptors
29240 we have for ourselves floating around, since it's quite likely
29241 other things (e.g. DirPort) will change during that minute too.
29242 - Fork the v1 directory protocol into its own spec document,
29243 and mark dir-spec.txt as the currently correct (v2) spec.
29246 - When we find our DirPort to be reachable, publish a new descriptor
29247 so we'll tell the world (reported by pnx).
29248 - Publish a new descriptor after we hup/reload. This is important
29249 if our config has changed such that we'll want to start advertising
29250 our DirPort now, etc.
29251 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29252 - When we have a state file we cannot parse, tell the user and
29253 move it aside. Now we avoid situations where the user starts
29254 Tor in 1904, Tor writes a state file with that timestamp in it,
29255 the user fixes her clock, and Tor refuses to start.
29256 - Fix configure.in to not produce broken configure files with
29257 more recent versions of autoconf. Thanks to Clint for his auto*
29259 - "tor --verify-config" now exits with -1(255) or 0 depending on
29260 whether the config options are bad or good.
29261 - Resolve bug 321 when using dnsworkers: append a period to every
29262 address we resolve at the exit node, so that we do not accidentally
29263 pick up local addresses, and so that failing searches are retried
29264 in the resolver search domains. (This is already solved for
29265 eventdns.) (This breaks Blossom servers for now.)
29266 - If we are using an exit enclave and we can't connect, e.g. because
29267 its webserver is misconfigured to not listen on localhost, then
29268 back off and try connecting from somewhere else before we fail.
29271 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
29272 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
29273 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
29274 when the IP address is mapped through MapAddress to a hostname.
29275 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
29276 useless IPv6 DNS resolves.
29277 - Patch suggested by Karsten Loesing: respond to SIGNAL command
29278 before we execute the signal, in case the signal shuts us down.
29279 - Clean up AllowInvalidNodes man page entry.
29280 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
29281 - Add more asserts to track down an assert error on a windows Tor
29282 server with connection_add being called with socket == -1.
29283 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
29284 - Fix misleading log messages: an entry guard that is "unlisted",
29285 as well as not known to be "down" (because we've never heard
29286 of it), is not therefore "up".
29287 - Remove code to special-case "-cvs" ending, since it has not
29288 actually mattered since 0.0.9.
29289 - Make our socks5 handling more robust to broken socks clients:
29290 throw out everything waiting on the buffer in between socks
29291 handshake phases, since they can't possibly (so the theory
29292 goes) have predicted what we plan to respond to them.
29295 Changes in version 0.1.1.23 - 2006-07-30
29297 - Fast Tor servers, especially exit nodes, were triggering asserts
29298 due to a bug in handling the list of pending DNS resolves. Some
29299 bugs still remain here; we're hunting them.
29300 - Entry guards could crash clients by sending unexpected input.
29301 - More fixes on reachability testing: if you find yourself reachable,
29302 then don't ever make any client requests (so you stop predicting
29303 circuits), then hup or have your clock jump, then later your IP
29304 changes, you won't think circuits are working, so you won't try to
29305 test reachability, so you won't publish.
29308 - Avoid a crash if the controller does a resetconf firewallports
29309 and then a setconf fascistfirewall=1.
29310 - Avoid an integer underflow when the dir authority decides whether
29311 a router is stable: we might wrongly label it stable, and compute
29312 a slightly wrong median stability, when a descriptor is published
29314 - Fix a place where we might trigger an assert if we can't build our
29315 own server descriptor yet.
29318 Changes in version 0.1.1.22 - 2006-07-05
29320 - Fix a big bug that was causing servers to not find themselves
29321 reachable if they changed IP addresses. Since only 0.1.1.22+
29322 servers can do reachability testing correctly, now we automatically
29323 make sure to test via one of these.
29324 - Fix to allow clients and mirrors to learn directory info from
29325 descriptor downloads that get cut off partway through.
29326 - Directory authorities had a bug in deciding if a newly published
29327 descriptor was novel enough to make everybody want a copy -- a few
29328 servers seem to be publishing new descriptors many times a minute.
29330 - Fix a rare bug that was causing some servers to complain about
29331 "closing wedged cpuworkers" and skip some circuit create requests.
29332 - Make the Exit flag in directory status documents actually work.
29335 Changes in version 0.1.1.21 - 2006-06-10
29336 o Crash and assert fixes from 0.1.1.20:
29337 - Fix a rare crash on Tor servers that have enabled hibernation.
29338 - Fix a seg fault on startup for Tor networks that use only one
29339 directory authority.
29340 - Fix an assert from a race condition that occurs on Tor servers
29341 while exiting, where various threads are trying to log that they're
29342 exiting, and delete the logs, at the same time.
29343 - Make our unit tests pass again on certain obscure platforms.
29346 - Add support for building SUSE RPM packages.
29347 - Speed up initial bootstrapping for clients: if we are making our
29348 first ever connection to any entry guard, then don't mark it down
29350 - When only one Tor server in the network is labelled as a guard,
29351 and we've already picked him, we would cycle endlessly picking him
29352 again, being unhappy about it, etc. Now we specifically exclude
29353 current guards when picking a new guard.
29354 - Servers send create cells more reliably after the TLS connection
29355 is established: we were sometimes forgetting to send half of them
29356 when we had more than one pending.
29357 - If we get a create cell that asks us to extend somewhere, but the
29358 Tor server there doesn't match the expected digest, we now send
29359 a destroy cell back, rather than silently doing nothing.
29360 - Make options->RedirectExit work again.
29361 - Make cookie authentication for the controller work again.
29362 - Stop being picky about unusual characters in the arguments to
29363 mapaddress. It's none of our business.
29364 - Add a new config option "TestVia" that lets you specify preferred
29365 middle hops to use for test circuits. Perhaps this will let me
29366 debug the reachability problems better.
29368 o Log / documentation fixes:
29369 - If we're a server and some peer has a broken TLS certificate, don't
29370 log about it unless ProtocolWarnings is set, i.e., we want to hear
29371 about protocol violations by others.
29372 - Fix spelling of VirtualAddrNetwork in man page.
29373 - Add a better explanation at the top of the autogenerated torrc file
29374 about what happened to our old torrc.
29377 Changes in version 0.1.1.20 - 2006-05-23
29379 - Downgrade a log severity where servers complain that they're
29381 - Avoid a compile warning on FreeBSD.
29382 - Remove string size limit on NEWDESC messages; solve bug 291.
29383 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
29384 more thoroughly when we're running on windows.
29387 Changes in version 0.1.1.19-rc - 2006-05-03
29389 - Regenerate our local descriptor if it's dirty and we try to use
29390 it locally (e.g. if it changes during reachability detection).
29391 - If we setconf our ORPort to 0, we continued to listen on the
29392 old ORPort and receive connections.
29393 - Avoid a second warning about machine/limits.h on Debian
29395 - Be willing to add our own routerinfo into the routerlist.
29396 Now authorities will include themselves in their directories
29397 and network-statuses.
29398 - Stop trying to upload rendezvous descriptors to every
29399 directory authority: only try the v1 authorities.
29400 - Servers no longer complain when they think they're not
29401 registered with the directory authorities. There were too many
29403 - Backport dist-rpm changes so rpms can be built without errors.
29406 - Implement an option, VirtualAddrMask, to set which addresses
29407 get handed out in response to mapaddress requests. This works
29408 around a bug in tsocks where 127.0.0.0/8 is never socksified.
29411 Changes in version 0.1.1.18-rc - 2006-04-10
29413 - Work harder to download live network-statuses from all the
29414 directory authorities we know about. Improve the threshold
29415 decision logic so we're more robust to edge cases.
29416 - When fetching rendezvous descriptors, we were willing to ask
29417 v2 authorities too, which would always return 404.
29420 - Stop listing down or invalid nodes in the v1 directory. This will
29421 reduce its bulk by about 1/3, and reduce load on directory
29423 - When deciding whether a router is Fast or Guard-worthy, consider
29424 his advertised BandwidthRate and not just the BandwidthCapacity.
29425 - No longer ship INSTALL and README files -- they are useless now.
29426 - Force rpmbuild to behave and honor target_cpu.
29427 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
29428 - Start to include translated versions of the tor-doc-*.html
29429 files, along with the screenshots. Still needs more work.
29430 - Start sending back 512 and 451 errors if mapaddress fails,
29431 rather than not sending anything back at all.
29432 - When we fail to bind or listen on an incoming or outgoing
29433 socket, we should close it before failing. otherwise we just
29434 leak it. (thanks to weasel for finding.)
29435 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
29436 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
29437 - Make NoPublish (even though deprecated) work again.
29438 - Fix a minor security flaw where a versioning auth dirserver
29439 could list a recommended version many times in a row to make
29440 clients more convinced that it's recommended.
29441 - Fix crash bug if there are two unregistered servers running
29442 with the same nickname, one of them is down, and you ask for
29443 them by nickname in your EntryNodes or ExitNodes. Also, try
29444 to pick the one that's running rather than an arbitrary one.
29445 - Fix an infinite loop we could hit if we go offline for too long.
29446 - Complain when we hit WSAENOBUFS on recv() or write() too.
29447 Perhaps this will help us hunt the bug.
29448 - If you're not a versioning dirserver, don't put the string
29449 "client-versions \nserver-versions \n" in your network-status.
29450 - Lower the minimum required number of file descriptors to 1000,
29451 so we can have some overhead for Valgrind on Linux, where the
29452 default ulimit -n is 1024.
29455 - Add tor.dizum.com as the fifth authoritative directory server.
29456 - Add a new config option FetchUselessDescriptors, off by default,
29457 for when you plan to run "exitlist" on your client and you want
29458 to know about even the non-running descriptors.
29461 Changes in version 0.1.1.17-rc - 2006-03-28
29463 - Clients and servers since 0.1.1.10-alpha have been expiring
29464 connections whenever they are idle for 5 minutes and they *do*
29465 have circuits on them. Oops. With this new version, clients will
29466 discard their previous entry guard choices and avoid choosing
29467 entry guards running these flawed versions.
29468 - Fix memory leak when uncompressing concatenated zlib streams. This
29469 was causing substantial leaks over time on Tor servers.
29470 - The v1 directory was including servers as much as 48 hours old,
29471 because that's how the new routerlist->routers works. Now only
29472 include them if they're 20 hours old or less.
29475 - Resume building on irix64, netbsd 2.0, etc.
29476 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
29478 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
29479 and it is confusing some users.
29480 - Mirrors stop caching the v1 directory so often.
29481 - Make the max number of old descriptors that a cache will hold
29482 rise with the number of directory authorities, so we can scale.
29483 - Change our win32 uname() hack to be more forgiving about what
29484 win32 versions it thinks it's found.
29487 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
29489 - When the controller's *setconf commands fail, collect an error
29490 message in a string and hand it back to the controller.
29491 - Make the v2 dir's "Fast" flag based on relative capacity, just
29492 like "Stable" is based on median uptime. Name everything in the
29493 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
29494 - Log server fingerprint on startup, so new server operators don't
29495 have to go hunting around their filesystem for it.
29496 - Return a robots.txt on our dirport to discourage google indexing.
29497 - Let the controller ask for GETINFO dir/status/foo so it can ask
29498 directly rather than connecting to the dir port. Only works when
29499 dirport is set for now.
29501 o New config options rather than constants in the code:
29502 - SocksTimeout: How long do we let a socks connection wait
29503 unattached before we fail it?
29504 - CircuitBuildTimeout: Cull non-open circuits that were born
29505 at least this many seconds ago.
29506 - CircuitIdleTimeout: Cull open clean circuits that were born
29507 at least this many seconds ago.
29510 Changes in version 0.1.1.16-rc - 2006-03-18
29511 o Bugfixes on 0.1.1.15-rc:
29512 - Fix assert when the controller asks to attachstream a connect-wait
29513 or resolve-wait stream.
29514 - Now do address rewriting when the controller asks us to attach
29515 to a particular circuit too. This will let Blossom specify
29516 "moria2.exit" without having to learn what moria2's IP address is.
29517 - Make the "tor --verify-config" command-line work again, so people
29518 can automatically check if their torrc will parse.
29519 - Authoritative dirservers no longer require an open connection from
29520 a server to consider him "reachable". We need this change because
29521 when we add new auth dirservers, old servers won't know not to
29523 - Let Tor build on Sun CC again.
29524 - Fix an off-by-one buffer size in dirserv.c that magically never
29525 hit our three authorities but broke sjmurdoch's own tor network.
29526 - If we as a directory mirror don't know of any v1 directory
29527 authorities, then don't try to cache any v1 directories.
29528 - Stop warning about unknown servers in our family when they are
29529 given as hex digests.
29530 - Stop complaining as quickly to the server operator that he
29531 hasn't registered his nickname/key binding.
29532 - Various cleanups so we can add new V2 Auth Dirservers.
29533 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
29534 reflect the updated flags in our v2 dir protocol.
29535 - Resume allowing non-printable characters for exit streams (both
29536 for connecting and for resolving). Now we tolerate applications
29537 that don't follow the RFCs. But continue to block malformed names
29540 o Bugfixes on 0.1.0.x:
29541 - Fix assert bug in close_logs(): when we close and delete logs,
29542 remove them all from the global "logfiles" list.
29543 - Fix minor integer overflow in calculating when we expect to use up
29544 our bandwidth allocation before hibernating.
29545 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29546 there are multiple SSLs installed with different versions.
29547 - When we try to be a server and Address is not explicitly set and
29548 our hostname resolves to a private IP address, try to use an
29549 interface address if it has a public address. Now Windows machines
29550 that think of themselves as localhost can work by default.
29553 - Let the controller ask for GETINFO dir/server/foo so it can ask
29554 directly rather than connecting to the dir port.
29555 - Let the controller tell us about certain router descriptors
29556 that it doesn't want Tor to use in circuits. Implement
29557 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29558 - New config option SafeSocks to reject all application connections
29559 using unsafe socks protocols. Defaults to off.
29562 Changes in version 0.1.1.15-rc - 2006-03-11
29563 o Bugfixes and cleanups:
29564 - When we're printing strings from the network, don't try to print
29565 non-printable characters. This protects us against shell escape
29566 sequence exploits, and also against attacks to fool humans into
29567 misreading their logs.
29568 - Fix a bug where Tor would fail to establish any connections if you
29569 left it off for 24 hours and then started it: we were happy with
29570 the obsolete network statuses, but they all referred to router
29571 descriptors that were too old to fetch, so we ended up with no
29572 valid router descriptors.
29573 - Fix a seg fault in the controller's "getinfo orconn-status"
29574 command while listing status on incoming handshaking connections.
29575 Introduce a status name "NEW" for these connections.
29576 - If we get a linelist or linelist_s config option from the torrc
29577 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29578 silently resetting it to its default.
29579 - Don't abandon entry guards until they've been down or gone for
29581 - Cleaner and quieter log messages.
29584 - New controller signal NEWNYM that makes new application requests
29585 use clean circuits.
29586 - Add a new circuit purpose 'controller' to let the controller ask
29587 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29588 controller command to let you specify the purpose if you're
29589 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29590 command to let you change a circuit's purpose after it's been
29592 - Accept "private:*" in routerdesc exit policies; not generated yet
29593 because older Tors do not understand it.
29594 - Add BSD-style contributed startup script "rc.subr" from Peter
29598 Changes in version 0.1.1.14-alpha - 2006-02-20
29599 o Bugfixes on 0.1.1.x:
29600 - Don't die if we ask for a stdout or stderr log (even implicitly)
29601 and we're set to RunAsDaemon -- just warn.
29602 - We still had a few bugs in the OR connection rotation code that
29603 caused directory servers to slowly aggregate connections to other
29604 fast Tor servers. This time for sure!
29605 - Make log entries on Win32 include the name of the function again.
29606 - We were treating a pair of exit policies if they were equal even
29607 if one said accept and the other said reject -- causing us to
29608 not always publish a new descriptor since we thought nothing
29610 - Retry pending server downloads as well as pending networkstatus
29611 downloads when we unexpectedly get a socks request.
29612 - We were ignoring the IS_FAST flag in the directory status,
29613 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29615 - If the controller's SAVECONF command fails (e.g. due to file
29616 permissions), let the controller know that it failed.
29619 - If we're trying to be a Tor server and running Windows 95/98/ME
29620 as a server, explain that we'll likely crash.
29621 - When we're a server, a client asks for an old-style directory,
29622 and our write bucket is empty, don't give it to him. This way
29623 small servers can continue to serve the directory *sometimes*,
29624 without getting overloaded.
29625 - Compress exit policies even more -- look for duplicate lines
29627 - Clients now honor the "guard" flag in the router status when
29628 picking entry guards, rather than looking at is_fast or is_stable.
29629 - Retain unrecognized lines in $DATADIR/state file, so that we can
29630 be forward-compatible.
29631 - Generate 18.0.0.0/8 address policy format in descs when we can;
29632 warn when the mask is not reducible to a bit-prefix.
29633 - Let the user set ControlListenAddress in the torrc. This can be
29634 dangerous, but there are some cases (like a secured LAN) where it
29636 - Split ReachableAddresses into ReachableDirAddresses and
29637 ReachableORAddresses, so we can restrict Dir conns to port 80
29638 and OR conns to port 443.
29639 - Now we can target arch and OS in rpm builds (contributed by
29640 Phobos). Also make the resulting dist-rpm filename match the
29642 - New config options to help controllers: FetchServerDescriptors
29643 and FetchHidServDescriptors for whether to fetch server
29644 info and hidserv info or let the controller do it, and
29645 PublishServerDescriptor and PublishHidServDescriptors.
29646 - Also let the controller set the __AllDirActionsPrivate config
29647 option if you want all directory fetches/publishes to happen via
29648 Tor (it assumes your controller bootstraps your circuits).
29651 Changes in version 0.1.0.17 - 2006-02-17
29652 o Crash bugfixes on 0.1.0.x:
29653 - When servers with a non-zero DirPort came out of hibernation,
29654 sometimes they would trigger an assert.
29656 o Other important bugfixes:
29657 - On platforms that don't have getrlimit (like Windows), we were
29658 artificially constraining ourselves to a max of 1024
29659 connections. Now just assume that we can handle as many as 15000
29660 connections. Hopefully this won't cause other problems.
29662 o Backported features:
29663 - When we're a server, a client asks for an old-style directory,
29664 and our write bucket is empty, don't give it to him. This way
29665 small servers can continue to serve the directory *sometimes*,
29666 without getting overloaded.
29667 - Whenever you get a 503 in response to a directory fetch, try
29668 once more. This will become important once servers start sending
29669 503's whenever they feel busy.
29670 - Fetch a new directory every 120 minutes, not every 40 minutes.
29671 Now that we have hundreds of thousands of users running the old
29672 directory algorithm, it's starting to hurt a lot.
29673 - Bump up the period for forcing a hidden service descriptor upload
29674 from 20 minutes to 1 hour.
29677 Changes in version 0.1.1.13-alpha - 2006-02-09
29678 o Crashes in 0.1.1.x:
29679 - When you tried to setconf ORPort via the controller, Tor would
29680 crash. So people using TorCP to become a server were sad.
29681 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29682 servers. The problem appears to be something do with OpenSSL's
29683 random number generation, or how we call it, or something. Let me
29684 know if the crashes continue.
29685 - Turn crypto hardware acceleration off by default, until we find
29686 somebody smart who can test it for us. (It appears to produce
29687 seg faults in at least some cases.)
29688 - Fix a rare assert error when we've tried all intro points for
29689 a hidden service and we try fetching the service descriptor again:
29690 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29693 - Fix a major load balance bug: we were round-robining in 16 KB
29694 chunks, and servers with bandwidthrate of 20 KB, while downloading
29695 a 600 KB directory, would starve their other connections. Now we
29696 try to be a bit more fair.
29697 - Dir authorities and mirrors were never expiring the newest
29698 descriptor for each server, causing memory and directory bloat.
29699 - Fix memory-bloating and connection-bloating bug on servers: We
29700 were never closing any connection that had ever had a circuit on
29701 it, because we were checking conn->n_circuits == 0, yet we had a
29702 bug that let it go negative.
29703 - Make Tor work using squid as your http proxy again -- squid
29704 returns an error if you ask for a URL that's too long, and it uses
29705 a really generic error message. Plus, many people are behind a
29706 transparent squid so they don't even realize it.
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.
29711 - Add a new config option ExitPolicyRejectPrivate which defaults to
29712 1. This means all exit policies will begin with rejecting private
29713 addresses, unless the server operator explicitly turns it off.
29716 - Clients no longer download descriptors for non-running
29718 - Before we add new directory authorities, we should make it
29719 clear that only v1 authorities should receive/publish hidden
29720 service descriptors.
29723 - As soon as we've fetched some more directory info, immediately
29724 try to download more server descriptors. This way we don't have
29725 a 10 second pause during initial bootstrapping.
29726 - Remove even more loud log messages that the server operator can't
29728 - When we're running an obsolete or un-recommended version, make
29729 the log message more clear about what the problem is and what
29730 versions *are* still recommended.
29731 - Provide a more useful warn message when our onion queue gets full:
29732 the CPU is too slow or the exit policy is too liberal.
29733 - Don't warn when we receive a 503 from a dirserver/cache -- this
29734 will pave the way for them being able to refuse if they're busy.
29735 - When we fail to bind a listener, try to provide a more useful
29736 log message: e.g., "Is Tor already running?"
29737 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29738 Goldberg can prove things about our handshake protocol more
29740 - MaxConn has been obsolete for a while now. Document the ConnLimit
29741 config option, which is a *minimum* number of file descriptors
29742 that must be available else Tor refuses to start.
29743 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29744 if you log to syslog and want something other than LOG_DAEMON.
29745 - Make dirservers generate a separate "guard" flag to mean,
29746 "would make a good entry guard". Make clients parse it and vote
29747 on it. Not used by clients yet.
29748 - Implement --with-libevent-dir option to ./configure. Also, improve
29749 search techniques to find libevent, and use those for openssl too.
29750 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
29751 - Only start testing reachability once we've established a
29752 circuit. This will make startup on dirservers less noisy.
29753 - Don't try to upload hidden service descriptors until we have
29754 established a circuit.
29755 - Fix the controller's "attachstream 0" command to treat conn like
29756 it just connected, doing address remapping, handling .exit and
29757 .onion idioms, and so on. Now we're more uniform in making sure
29758 that the controller hears about new and closing connections.
29761 Changes in version 0.1.1.12-alpha - 2006-01-11
29762 o Bugfixes on 0.1.1.x:
29763 - The fix to close duplicate server connections was closing all
29764 Tor client connections if they didn't establish a circuit
29765 quickly enough. Oops.
29766 - Fix minor memory issue (double-free) that happened on exit.
29768 o Bugfixes on 0.1.0.x:
29769 - Tor didn't warn when it failed to open a log file.
29772 Changes in version 0.1.1.11-alpha - 2006-01-10
29773 o Crashes in 0.1.1.x:
29774 - Include all the assert/crash fixes from 0.1.0.16.
29775 - If you start Tor and then quit very quickly, there were some
29776 races that tried to free things that weren't allocated yet.
29777 - Fix a rare memory stomp if you're running hidden services.
29778 - Fix segfault when specifying DirServer in config without nickname.
29779 - Fix a seg fault when you finish connecting to a server but at
29780 that moment you dump his server descriptor.
29781 - Extendcircuit and Attachstream controller commands would
29782 assert/crash if you don't give them enough arguments.
29783 - Fix an assert error when we're out of space in the connection_list
29784 and we try to post a hidden service descriptor (reported by weasel).
29785 - If you specify a relative torrc path and you set RunAsDaemon in
29786 your torrc, then it chdir()'s to the new directory. If you HUP,
29787 it tries to load the new torrc location, fails, and exits.
29788 The fix: no longer allow a relative path to torrc using -f.
29791 - Implement "entry guards": automatically choose a handful of entry
29792 nodes and stick with them for all circuits. Only pick new guards
29793 when the ones you have are unsuitable, and if the old guards
29794 become suitable again, switch back. This will increase security
29795 dramatically against certain end-point attacks. The EntryNodes
29796 config option now provides some hints about which entry guards you
29797 want to use most; and StrictEntryNodes means to only use those.
29798 - New directory logic: download by descriptor digest, not by
29799 fingerprint. Caches try to download all listed digests from
29800 authorities; clients try to download "best" digests from caches.
29801 This avoids partitioning and isolating attacks better.
29802 - Make the "stable" router flag in network-status be the median of
29803 the uptimes of running valid servers, and make clients pay
29804 attention to the network-status flags. Thus the cutoff adapts
29805 to the stability of the network as a whole, making IRC, IM, etc
29806 connections more reliable.
29809 - Tor servers with dynamic IP addresses were needing to wait 18
29810 hours before they could start doing reachability testing using
29811 the new IP address and ports. This is because they were using
29812 the internal descriptor to learn what to test, yet they were only
29813 rebuilding the descriptor once they decided they were reachable.
29814 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
29815 to download certain server descriptors, throw them away, and then
29816 fetch them again after 30 minutes. Now mirrors throw away these
29817 server descriptors so clients can't get them.
29818 - We were leaving duplicate connections to other ORs open for a week,
29819 rather than closing them once we detect a duplicate. This only
29820 really affected authdirservers, but it affected them a lot.
29821 - Spread the authdirservers' reachability testing over the entire
29822 testing interval, so we don't try to do 500 TLS's at once every
29826 - If the network is down, and we try to connect to a conn because
29827 we have a circuit in mind, and we timeout (30 seconds) because the
29828 network never answers, we were expiring the circuit, but we weren't
29829 obsoleting the connection or telling the entry_guards functions.
29830 - Some Tor servers process billions of cells per day. These statistics
29831 need to be uint64_t's.
29832 - Check for integer overflows in more places, when adding elements
29833 to smartlists. This could possibly prevent a buffer overflow
29834 on malicious huge inputs. I don't see any, but I haven't looked
29836 - ReachableAddresses kept growing new "reject *:*" lines on every
29838 - When you "setconf log" via the controller, it should remove all
29839 logs. We were automatically adding back in a "log notice stdout".
29840 - Newly bootstrapped Tor networks couldn't establish hidden service
29841 circuits until they had nodes with high uptime. Be more tolerant.
29842 - We were marking servers down when they could not answer every piece
29843 of the directory request we sent them. This was far too harsh.
29844 - Fix the torify (tsocks) config file to not use Tor for localhost
29846 - Directory authorities now go to the proper authority when asking for
29847 a networkstatus, even when they want a compressed one.
29848 - Fix a harmless bug that was causing Tor servers to log
29849 "Got an end because of misc error, but we're not an AP. Closing."
29850 - Authorities were treating their own descriptor changes as cosmetic,
29851 meaning the descriptor available in the network-status and the
29852 descriptor that clients downloaded were different.
29853 - The OS X installer was adding a symlink for tor_resolve but
29854 the binary was called tor-resolve (reported by Thomas Hardly).
29855 - Workaround a problem with some http proxies where they refuse GET
29856 requests that specify "Content-Length: 0" (reported by Adrian).
29857 - Fix wrong log message when you add a "HiddenServiceNodes" config
29858 line without any HiddenServiceDir line (reported by Chris Thomas).
29861 - Write the TorVersion into the state file so we have a prayer of
29862 keeping forward and backward compatibility.
29863 - Revive the FascistFirewall config option rather than eliminating it:
29864 now it's a synonym for ReachableAddresses *:80,*:443.
29865 - Clients choose directory servers from the network status lists,
29866 not from their internal list of router descriptors. Now they can
29867 go to caches directly rather than needing to go to authorities
29869 - Directory authorities ignore router descriptors that have only
29870 cosmetic differences: do this for 0.1.0.x servers now too.
29871 - Add a new flag to network-status indicating whether the server
29872 can answer v2 directory requests too.
29873 - Authdirs now stop whining so loudly about bad descriptors that
29874 they fetch from other dirservers. So when there's a log complaint,
29875 it's for sure from a freshly uploaded descriptor.
29876 - Reduce memory requirements in our structs by changing the order
29878 - There used to be two ways to specify your listening ports in a
29879 server descriptor: on the "router" line and with a separate "ports"
29880 line. Remove support for the "ports" line.
29881 - New config option "AuthDirRejectUnlisted" for auth dirservers as
29882 a panic button: if we get flooded with unusable servers we can
29883 revert to only listing servers in the approved-routers file.
29884 - Auth dir servers can now mark a fingerprint as "!reject" or
29885 "!invalid" in the approved-routers file (as its nickname), to
29886 refuse descriptors outright or include them but marked as invalid.
29887 - Servers store bandwidth history across restarts/crashes.
29888 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
29889 get a better idea of why their circuits failed. Not used yet.
29890 - Directory mirrors now cache up to 16 unrecognized network-status
29891 docs. Now we can add new authdirservers and they'll be cached too.
29892 - When picking a random directory, prefer non-authorities if any
29894 - New controller option "getinfo desc/all-recent" to fetch the
29895 latest server descriptor for every router that Tor knows about.
29898 Changes in version 0.1.0.16 - 2006-01-02
29899 o Crash bugfixes on 0.1.0.x:
29900 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29901 corrupting the heap, losing FDs, or crashing when we need to resize
29902 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29903 - It turns out sparc64 platforms crash on unaligned memory access
29904 too -- so detect and avoid this.
29905 - Handle truncated compressed data correctly (by detecting it and
29907 - Fix possible-but-unlikely free(NULL) in control.c.
29908 - When we were closing connections, there was a rare case that
29909 stomped on memory, triggering seg faults and asserts.
29910 - Avoid potential infinite recursion when building a descriptor. (We
29911 don't know that it ever happened, but better to fix it anyway.)
29912 - We were neglecting to unlink marked circuits from soon-to-close OR
29913 connections, which caused some rare scribbling on freed memory.
29914 - Fix a memory stomping race bug when closing the joining point of two
29915 rendezvous circuits.
29916 - Fix an assert in time parsing found by Steven Murdoch.
29918 o Other bugfixes on 0.1.0.x:
29919 - When we're doing reachability testing, provide more useful log
29920 messages so the operator knows what to expect.
29921 - Do not check whether DirPort is reachable when we are suppressing
29922 advertising it because of hibernation.
29923 - When building with -static or on Solaris, we sometimes needed -ldl.
29924 - When we're deciding whether a stream has enough circuits around
29925 that can handle it, count the freshly dirty ones and not the ones
29926 that are so dirty they won't be able to handle it.
29927 - When we're expiring old circuits, we had a logic error that caused
29928 us to close new rendezvous circuits rather than old ones.
29929 - Give a more helpful log message when you try to change ORPort via
29930 the controller: you should upgrade Tor if you want that to work.
29931 - We were failing to parse Tor versions that start with "Tor ".
29932 - Tolerate faulty streams better: when a stream fails for reason
29933 exitpolicy, stop assuming that the router is lying about his exit
29934 policy. When a stream fails for reason misc, allow it to retry just
29935 as if it was resolvefailed. When a stream has failed three times,
29936 reset its failure count so we can try again and get all three tries.
29939 Changes in version 0.1.1.10-alpha - 2005-12-11
29940 o Correctness bugfixes on 0.1.0.x:
29941 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29942 corrupting the heap, losing FDs, or crashing when we need to resize
29943 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29944 - Stop doing the complex voodoo overkill checking for insecure
29945 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
29946 - When we were closing connections, there was a rare case that
29947 stomped on memory, triggering seg faults and asserts.
29948 - We were neglecting to unlink marked circuits from soon-to-close OR
29949 connections, which caused some rare scribbling on freed memory.
29950 - When we're deciding whether a stream has enough circuits around
29951 that can handle it, count the freshly dirty ones and not the ones
29952 that are so dirty they won't be able to handle it.
29953 - Recover better from TCP connections to Tor servers that are
29954 broken but don't tell you (it happens!); and rotate TLS
29955 connections once a week.
29956 - When we're expiring old circuits, we had a logic error that caused
29957 us to close new rendezvous circuits rather than old ones.
29958 - Fix a scary-looking but apparently harmless bug where circuits
29959 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
29960 servers, and never switch to state CIRCUIT_STATE_OPEN.
29961 - When building with -static or on Solaris, we sometimes needed to
29963 - Give a useful message when people run Tor as the wrong user,
29964 rather than telling them to start chowning random directories.
29965 - We were failing to inform the controller about new .onion streams.
29967 o Security bugfixes on 0.1.0.x:
29968 - Refuse server descriptors if the fingerprint line doesn't match
29969 the included identity key. Tor doesn't care, but other apps (and
29970 humans) might actually be trusting the fingerprint line.
29971 - We used to kill the circuit when we receive a relay command we
29972 don't recognize. Now we just drop it.
29973 - Start obeying our firewall options more rigorously:
29974 . If we can't get to a dirserver directly, try going via Tor.
29975 . Don't ever try to connect (as a client) to a place our
29976 firewall options forbid.
29977 . If we specify a proxy and also firewall options, obey the
29978 firewall options even when we're using the proxy: some proxies
29979 can only proxy to certain destinations.
29980 - Fix a bug found by Lasse Overlier: when we were making internal
29981 circuits (intended to be cannibalized later for rendezvous and
29982 introduction circuits), we were picking them so that they had
29983 useful exit nodes. There was no need for this, and it actually
29984 aids some statistical attacks.
29985 - Start treating internal circuits and exit circuits separately.
29986 It's important to keep them separate because internal circuits
29987 have their last hops picked like middle hops, rather than like
29988 exit hops. So exiting on them will break the user's expectations.
29990 o Bugfixes on 0.1.1.x:
29991 - Take out the mis-feature where we tried to detect IP address
29992 flapping for people with DynDNS, and chose not to upload a new
29993 server descriptor sometimes.
29994 - Try to be compatible with OpenSSL 0.9.6 again.
29995 - Log fix: when the controller is logging about .onion addresses,
29996 sometimes it didn't include the ".onion" part of the address.
29997 - Don't try to modify options->DirServers internally -- if the
29998 user didn't specify any, just add the default ones directly to
29999 the trusted dirserver list. This fixes a bug where people running
30000 controllers would use SETCONF on some totally unrelated config
30001 option, and Tor would start yelling at them about changing their
30003 - Let the controller's redirectstream command specify a port, in
30004 case the controller wants to change that too.
30005 - When we requested a pile of server descriptors, we sometimes
30006 accidentally launched a duplicate request for the first one.
30007 - Bugfix for trackhostexits: write down the fingerprint of the
30008 chosen exit, not its nickname, because the chosen exit might not
30010 - When parsing foo.exit, if foo is unknown, and we are leaving
30011 circuits unattached, set the chosen_exit field and leave the
30012 address empty. This matters because controllers got confused
30014 - Directory authorities no longer try to download server
30015 descriptors that they know they will reject.
30017 o Features and updates:
30018 - Replace balanced trees with hash tables: this should make stuff
30019 significantly faster.
30020 - Resume using the AES counter-mode implementation that we ship,
30021 rather than OpenSSL's. Ours is significantly faster.
30022 - Many other CPU and memory improvements.
30023 - Add a new config option FastFirstHopPK (on by default) so clients
30024 do a trivial crypto handshake for their first hop, since TLS has
30025 already taken care of confidentiality and authentication.
30026 - Add a new config option TestSocks so people can see if their
30027 applications are using socks4, socks4a, socks5-with-ip, or
30028 socks5-with-hostname. This way they don't have to keep mucking
30029 with tcpdump and wondering if something got cached somewhere.
30030 - Warn when listening on a public address for socks. I suspect a
30031 lot of people are setting themselves up as open socks proxies,
30032 and they have no idea that jerks on the Internet are using them,
30033 since they simply proxy the traffic into the Tor network.
30034 - Add "private:*" as an alias in configuration for policies. Now
30035 you can simplify your exit policy rather than needing to list
30036 every single internal or nonroutable network space.
30037 - Add a new controller event type that allows controllers to get
30038 all server descriptors that were uploaded to a router in its role
30039 as authoritative dirserver.
30040 - Start shipping socks-extensions.txt, tor-doc-unix.html,
30041 tor-doc-server.html, and stylesheet.css in the tarball.
30042 - Stop shipping tor-doc.html in the tarball.
30045 Changes in version 0.1.1.9-alpha - 2005-11-15
30046 o Usability improvements:
30047 - Start calling it FooListenAddress rather than FooBindAddress,
30048 since few of our users know what it means to bind an address
30050 - Reduce clutter in server logs. We're going to try to make
30051 them actually usable now. New config option ProtocolWarnings that
30052 lets you hear about how _other Tors_ are breaking the protocol. Off
30054 - Divide log messages into logging domains. Once we put some sort
30055 of interface on this, it will let people looking at more verbose
30056 log levels specify the topics they want to hear more about.
30057 - Make directory servers return better http 404 error messages
30058 instead of a generic "Servers unavailable".
30059 - Check for even more Windows version flags when writing the platform
30060 string in server descriptors, and note any we don't recognize.
30061 - Clean up more of the OpenSSL memory when exiting, so we can detect
30062 memory leaks better.
30063 - Make directory authorities be non-versioning, non-naming by
30064 default. Now we can add new directory servers without requiring
30065 their operators to pay close attention.
30066 - When logging via syslog, include the pid whenever we provide
30067 a log entry. Suggested by Todd Fries.
30069 o Performance improvements:
30070 - Directory servers now silently throw away new descriptors that
30071 haven't changed much if the timestamps are similar. We do this to
30072 tolerate older Tor servers that upload a new descriptor every 15
30073 minutes. (It seemed like a good idea at the time.)
30074 - Inline bottleneck smartlist functions; use fast versions by default.
30075 - Add a "Map from digest to void*" abstraction digestmap_t so we
30076 can do less hex encoding/decoding. Use it in router_get_by_digest()
30077 to resolve a performance bottleneck.
30078 - Allow tor_gzip_uncompress to extract as much as possible from
30079 truncated compressed data. Try to extract as many
30080 descriptors as possible from truncated http responses (when
30081 DIR_PURPOSE_FETCH_ROUTERDESC).
30082 - Make circ->onionskin a pointer, not a static array. moria2 was using
30083 125000 circuit_t's after it had been up for a few weeks, which
30084 translates to 20+ megs of wasted space.
30085 - The private half of our EDH handshake keys are now chosen out
30086 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
30088 o Security improvements:
30089 - Start making directory caches retain old routerinfos, so soon
30090 clients can start asking by digest of descriptor rather than by
30091 fingerprint of server.
30092 - Add half our entropy from RAND_poll in OpenSSL. This knows how
30093 to use egd (if present), openbsd weirdness (if present), vms/os2
30094 weirdness (if we ever port there), and more in the future.
30096 o Bugfixes on 0.1.0.x:
30097 - Do round-robin writes of at most 16 kB per write. This might be
30098 more fair on loaded Tor servers, and it might resolve our Windows
30099 crash bug. It might also slow things down.
30100 - Our TLS handshakes were generating a single public/private
30101 keypair for the TLS context, rather than making a new one for
30102 each new connections. Oops. (But we were still rotating them
30103 periodically, so it's not so bad.)
30104 - When we were cannibalizing a circuit with a particular exit
30105 node in mind, we weren't checking to see if that exit node was
30106 already present earlier in the circuit. Oops.
30107 - When a Tor server's IP changes (e.g. from a dyndns address),
30108 upload a new descriptor so clients will learn too.
30109 - Really busy servers were keeping enough circuits open on stable
30110 connections that they were wrapping around the circuit_id
30111 space. (It's only two bytes.) This exposed a bug where we would
30112 feel free to reuse a circuit_id even if it still exists but has
30113 been marked for close. Try to fix this bug. Some bug remains.
30114 - If we would close a stream early (e.g. it asks for a .exit that
30115 we know would refuse it) but the LeaveStreamsUnattached config
30116 option is set by the controller, then don't close it.
30118 o Bugfixes on 0.1.1.8-alpha:
30119 - Fix a big pile of memory leaks, some of them serious.
30120 - Do not try to download a routerdesc if we would immediately reject
30122 - Resume inserting a newline between all router descriptors when
30123 generating (old style) signed directories, since our spec says
30125 - When providing content-type application/octet-stream for
30126 server descriptors using .z, we were leaving out the
30127 content-encoding header. Oops. (Everything tolerated this just
30128 fine, but that doesn't mean we need to be part of the problem.)
30129 - Fix a potential seg fault in getconf and getinfo using version 1
30130 of the controller protocol.
30131 - Avoid crash: do not check whether DirPort is reachable when we
30132 are suppressing it because of hibernation.
30133 - Make --hash-password not crash on exit.
30136 Changes in version 0.1.1.8-alpha - 2005-10-07
30137 o New features (major):
30138 - Clients don't download or use the directory anymore. Now they
30139 download and use network-statuses from the trusted dirservers,
30140 and fetch individual server descriptors as needed from mirrors.
30141 See dir-spec.txt for all the gory details.
30142 - Be more conservative about whether to advertise our DirPort.
30143 The main change is to not advertise if we're running at capacity
30144 and either a) we could hibernate or b) our capacity is low and
30145 we're using a default DirPort.
30146 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
30148 o New features (minor):
30149 - Try to be smart about when to retry network-status and
30150 server-descriptor fetches. Still needs some tuning.
30151 - Stop parsing, storing, or using running-routers output (but
30152 mirrors still cache and serve it).
30153 - Consider a threshold of versioning dirservers (dirservers who have
30154 an opinion about which Tor versions are still recommended) before
30155 deciding whether to warn the user that he's obsolete.
30156 - Dirservers can now reject/invalidate by key and IP, with the
30157 config options "AuthDirInvalid" and "AuthDirReject". This is
30158 useful since currently we automatically list servers as running
30159 and usable even if we know they're jerks.
30160 - Provide dire warnings to any users who set DirServer; move it out
30161 of torrc.sample and into torrc.complete.
30162 - Add MyFamily to torrc.sample in the server section.
30163 - Add nicknames to the DirServer line, so we can refer to them
30164 without requiring all our users to memorize their IP addresses.
30165 - When we get an EOF or a timeout on a directory connection, note
30166 how many bytes of serverdesc we are dropping. This will help
30167 us determine whether it is smart to parse incomplete serverdesc
30169 - Add a new function to "change pseudonyms" -- that is, to stop
30170 using any currently-dirty circuits for new streams, so we don't
30171 link new actions to old actions. Currently it's only called on
30172 HUP (or SIGNAL RELOAD).
30173 - On sighup, if UseHelperNodes changed to 1, use new circuits.
30174 - Start using RAND_bytes rather than RAND_pseudo_bytes from
30175 OpenSSL. Also, reseed our entropy every hour, not just at
30176 startup. And entropy in 512-bit chunks, not 160-bit chunks.
30178 o Fixes on 0.1.1.7-alpha:
30179 - Nobody ever implemented EVENT_ADDRMAP for control protocol
30180 version 0, so don't let version 0 controllers ask for it.
30181 - If you requested something with too many newlines via the
30182 v1 controller protocol, you could crash tor.
30183 - Fix a number of memory leaks, including some pretty serious ones.
30184 - Re-enable DirPort testing again, so Tor servers will be willing
30185 to advertise their DirPort if it's reachable.
30186 - On TLS handshake, only check the other router's nickname against
30187 its expected nickname if is_named is set.
30189 o Fixes forward-ported from 0.1.0.15:
30190 - Don't crash when we don't have any spare file descriptors and we
30191 try to spawn a dns or cpu worker.
30192 - Make the numbers in read-history and write-history into uint64s,
30193 so they don't overflow and publish negatives in the descriptor.
30195 o Fixes on 0.1.0.x:
30196 - For the OS X package's modified privoxy config file, comment
30197 out the "logfile" line so we don't log everything passed
30199 - We were whining about using socks4 or socks5-with-local-lookup
30200 even when it's an IP in the "virtual" range we designed exactly
30202 - We were leaking some memory every time the client changes IPs.
30203 - Never call free() on tor_malloc()d memory. This will help us
30204 use dmalloc to detect memory leaks.
30205 - Check for named servers when looking them up by nickname;
30206 warn when we'recalling a non-named server by its nickname;
30207 don't warn twice about the same name.
30208 - Try to list MyFamily elements by key, not by nickname, and warn
30209 if we've not heard of the server.
30210 - Make windows platform detection (uname equivalent) smarter.
30211 - It turns out sparc64 doesn't like unaligned access either.
30214 Changes in version 0.1.0.15 - 2005-09-23
30215 o Bugfixes on 0.1.0.x:
30216 - Reject ports 465 and 587 (spam targets) in default exit policy.
30217 - Don't crash when we don't have any spare file descriptors and we
30218 try to spawn a dns or cpu worker.
30219 - Get rid of IgnoreVersion undocumented config option, and make us
30220 only warn, never exit, when we're running an obsolete version.
30221 - Don't try to print a null string when your server finds itself to
30222 be unreachable and the Address config option is empty.
30223 - Make the numbers in read-history and write-history into uint64s,
30224 so they don't overflow and publish negatives in the descriptor.
30225 - Fix a minor memory leak in smartlist_string_remove().
30226 - We were only allowing ourselves to upload a server descriptor at
30227 most every 20 minutes, even if it changed earlier than that.
30228 - Clean up log entries that pointed to old URLs.
30231 Changes in version 0.1.1.7-alpha - 2005-09-14
30232 o Fixes on 0.1.1.6-alpha:
30233 - Exit servers were crashing when people asked them to make a
30234 connection to an address not in their exit policy.
30235 - Looking up a non-existent stream for a v1 control connection would
30237 - Fix a seg fault if we ask a dirserver for a descriptor by
30238 fingerprint but he doesn't know about him.
30239 - SETCONF was appending items to linelists, not clearing them.
30240 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
30241 out and refuse the setconf if it would fail.
30242 - Downgrade the dirserver log messages when whining about
30246 - Add Peter Palfrader's check-tor script to tor/contrib/
30247 It lets you easily check whether a given server (referenced by
30248 nickname) is reachable by you.
30249 - Numerous changes to move towards client-side v2 directories. Not
30252 o Fixes on 0.1.0.x:
30253 - If the user gave tor an odd number of command-line arguments,
30254 we were silently ignoring the last one. Now we complain and fail.
30255 [This wins the oldest-bug prize -- this bug has been present since
30256 November 2002, as released in Tor 0.0.0.]
30257 - Do not use unaligned memory access on alpha, mips, or mipsel.
30258 It *works*, but is very slow, so we treat them as if it doesn't.
30259 - Retry directory requests if we fail to get an answer we like
30260 from a given dirserver (we were retrying before, but only if
30261 we fail to connect).
30262 - When writing the RecommendedVersions line, sort them first.
30263 - When the client asked for a rendezvous port that the hidden
30264 service didn't want to provide, we were sending an IP address
30265 back along with the end cell. Fortunately, it was zero. But stop
30267 - Correct "your server is reachable" log entries to indicate that
30268 it was self-testing that told us so.
30271 Changes in version 0.1.1.6-alpha - 2005-09-09
30272 o Fixes on 0.1.1.5-alpha:
30273 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
30274 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
30275 - Fix bug with tor_memmem finding a match at the end of the string.
30276 - Make unit tests run without segfaulting.
30277 - Resolve some solaris x86 compile warnings.
30278 - Handle duplicate lines in approved-routers files without warning.
30279 - Fix bug where as soon as a server refused any requests due to his
30280 exit policy (e.g. when we ask for localhost and he tells us that's
30281 127.0.0.1 and he won't do it), we decided he wasn't obeying his
30282 exit policy using him for any exits.
30283 - Only do openssl hardware accelerator stuff if openssl version is
30286 o New controller features/fixes:
30287 - Add a "RESETCONF" command so you can set config options like
30288 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
30289 a config option in the torrc with no value, then it clears it
30290 entirely (rather than setting it to its default).
30291 - Add a "GETINFO config-file" to tell us where torrc is.
30292 - Avoid sending blank lines when GETINFO replies should be empty.
30293 - Add a QUIT command for the controller (for using it manually).
30294 - Fix a bug in SAVECONF that was adding default dirservers and
30295 other redundant entries to the torrc file.
30297 o Start on the new directory design:
30298 - Generate, publish, cache, serve new network-status format.
30299 - Publish individual descriptors (by fingerprint, by "all", and by
30301 - Publish client and server recommended versions separately.
30302 - Allow tor_gzip_uncompress() to handle multiple concatenated
30303 compressed strings. Serve compressed groups of router
30304 descriptors. The compression logic here could be more
30306 - Distinguish v1 authorities (all currently trusted directories)
30307 from v2 authorities (all trusted directories).
30308 - Change DirServers config line to note which dirs are v1 authorities.
30309 - Add configuration option "V1AuthoritativeDirectory 1" which
30310 moria1, moria2, and tor26 should set.
30311 - Remove option when getting directory cache to see whether they
30312 support running-routers; they all do now. Replace it with one
30313 to see whether caches support v2 stuff.
30316 - Dirservers now do their own external reachability testing of each
30317 Tor server, and only list them as running if they've been found to
30318 be reachable. We also send back warnings to the server's logs if
30319 it uploads a descriptor that we already believe is unreachable.
30320 - Implement exit enclaves: if we know an IP address for the
30321 destination, and there's a running Tor server at that address
30322 which allows exit to the destination, then extend the circuit to
30323 that exit first. This provides end-to-end encryption and end-to-end
30324 authentication. Also, if the user wants a .exit address or enclave,
30325 use 4 hops rather than 3, and cannibalize a general circ for it
30327 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
30328 controller. Also, rotate dns and cpu workers if the controller
30329 changes options that will affect them; and initialize the dns
30330 worker cache tree whether or not we start out as a server.
30331 - Only upload a new server descriptor when options change, 18
30332 hours have passed, uptime is reset, or bandwidth changes a lot.
30333 - Check [X-]Forwarded-For headers in HTTP requests when generating
30334 log messages. This lets people run dirservers (and caches) behind
30335 Apache but still know which IP addresses are causing warnings.
30337 o Config option changes:
30338 - Replace (Fascist)Firewall* config options with a new
30339 ReachableAddresses option that understands address policies.
30340 For example, "ReachableAddresses *:80,*:443"
30341 - Get rid of IgnoreVersion undocumented config option, and make us
30342 only warn, never exit, when we're running an obsolete version.
30343 - Make MonthlyAccountingStart config option truly obsolete now.
30345 o Fixes on 0.1.0.x:
30346 - Reject ports 465 and 587 in the default exit policy, since
30347 people have started using them for spam too.
30348 - It turns out we couldn't bootstrap a network since we added
30349 reachability detection in 0.1.0.1-rc. Good thing the Tor network
30350 has never gone down. Add an AssumeReachable config option to let
30351 servers and dirservers bootstrap. When we're trying to build a
30352 high-uptime or high-bandwidth circuit but there aren't enough
30353 suitable servers, try being less picky rather than simply failing.
30354 - Our logic to decide if the OR we connected to was the right guy
30355 was brittle and maybe open to a mitm for unverified routers.
30356 - We weren't cannibalizing circuits correctly for
30357 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
30358 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
30359 build those from scratch. This should make hidden services faster.
30360 - Predict required circuits better, with an eye toward making hidden
30361 services faster on the service end.
30362 - Retry streams if the exit node sends back a 'misc' failure. This
30363 should result in fewer random failures. Also, after failing
30364 from resolve failed or misc, reset the num failures, so we give
30365 it a fair shake next time we try.
30366 - Clean up the rendezvous warn log msgs, and downgrade some to info.
30367 - Reduce severity on logs about dns worker spawning and culling.
30368 - When we're shutting down and we do something like try to post a
30369 server descriptor or rendezvous descriptor, don't complain that
30370 we seem to be unreachable. Of course we are, we're shutting down.
30371 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
30372 We don't use them yet, but maybe one day our DNS resolver will be
30373 able to discover them.
30374 - Make ContactInfo mandatory for authoritative directory servers.
30375 - Require server descriptors to list IPv4 addresses -- hostnames
30376 are no longer allowed. This also fixes some potential security
30377 problems with people providing hostnames as their address and then
30378 preferentially resolving them to partition users.
30379 - Change log line for unreachability to explicitly suggest /etc/hosts
30380 as the culprit. Also make it clearer what IP address and ports we're
30381 testing for reachability.
30382 - Put quotes around user-supplied strings when logging so users are
30383 more likely to realize if they add bad characters (like quotes)
30385 - Let auth dir servers start without specifying an Address config
30387 - Make unit tests (and other invocations that aren't the real Tor)
30388 run without launching listeners, creating subdirectories, and so on.
30391 Changes in version 0.1.1.5-alpha - 2005-08-08
30392 o Bugfixes included in 0.1.0.14.
30394 o Bugfixes on 0.1.0.x:
30395 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
30396 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
30397 it would silently using ignore the 6668.
30400 Changes in version 0.1.0.14 - 2005-08-08
30401 o Bugfixes on 0.1.0.x:
30402 - Fix the other half of the bug with crypto handshakes
30404 - Fix an assert trigger if you send a 'signal term' via the
30405 controller when it's listening for 'event info' messages.
30408 Changes in version 0.1.1.4-alpha - 2005-08-04
30409 o Bugfixes included in 0.1.0.13.
30412 - Improve tor_gettimeofday() granularity on windows.
30413 - Make clients regenerate their keys when their IP address changes.
30414 - Implement some more GETINFO goodness: expose helper nodes, config
30415 options, getinfo keys.
30418 Changes in version 0.1.0.13 - 2005-08-04
30419 o Bugfixes on 0.1.0.x:
30420 - Fix a critical bug in the security of our crypto handshakes.
30421 - Fix a size_t underflow in smartlist_join_strings2() that made
30422 it do bad things when you hand it an empty smartlist.
30423 - Fix Windows installer to ship Tor license (thanks to Aphex for
30424 pointing out this oversight) and put a link to the doc directory
30426 - Explicitly set no-unaligned-access for sparc: it turns out the
30427 new gcc's let you compile broken code, but that doesn't make it
30431 Changes in version 0.1.1.3-alpha - 2005-07-23
30432 o Bugfixes on 0.1.1.2-alpha:
30433 - Fix a bug in handling the controller's "post descriptor"
30435 - Fix several bugs in handling the controller's "extend circuit"
30437 - Fix a bug in handling the controller's "stream status" event.
30438 - Fix an assert failure if we have a controller listening for
30439 circuit events and we go offline.
30440 - Re-allow hidden service descriptors to publish 0 intro points.
30441 - Fix a crash when generating your hidden service descriptor if
30442 you don't have enough intro points already.
30444 o New features on 0.1.1.2-alpha:
30445 - New controller function "getinfo accounting", to ask how
30446 many bytes we've used in this time period.
30447 - Experimental support for helper nodes: a lot of the risk from
30448 a small static adversary comes because users pick new random
30449 nodes every time they rebuild a circuit. Now users will try to
30450 stick to the same small set of entry nodes if they can. Not
30451 enabled by default yet.
30453 o Bugfixes on 0.1.0.12:
30454 - If you're an auth dir server, always publish your dirport,
30455 even if you haven't yet found yourself to be reachable.
30456 - Fix a size_t underflow in smartlist_join_strings2() that made
30457 it do bad things when you hand it an empty smartlist.
30460 Changes in version 0.1.0.12 - 2005-07-18
30461 o New directory servers:
30462 - tor26 has changed IP address.
30464 o Bugfixes on 0.1.0.x:
30465 - Fix a possible double-free in tor_gzip_uncompress().
30466 - When --disable-threads is set, do not search for or link against
30467 pthreads libraries.
30468 - Don't trigger an assert if an authoritative directory server
30469 claims its dirport is 0.
30470 - Fix bug with removing Tor as an NT service: some people were
30471 getting "The service did not return an error." Thanks to Matt
30475 Changes in version 0.1.1.2-alpha - 2005-07-15
30476 o New directory servers:
30477 - tor26 has changed IP address.
30479 o Bugfixes on 0.1.0.x, crashes/leaks:
30480 - Port the servers-not-obeying-their-exit-policies fix from
30482 - Fix an fd leak in start_daemon().
30483 - On Windows, you can't always reopen a port right after you've
30484 closed it. So change retry_listeners() to only close and re-open
30485 ports that have changed.
30486 - Fix a possible double-free in tor_gzip_uncompress().
30488 o Bugfixes on 0.1.0.x, usability:
30489 - When tor_socketpair() fails in Windows, give a reasonable
30490 Windows-style errno back.
30491 - Let people type "tor --install" as well as "tor -install" when
30493 want to make it an NT service.
30494 - NT service patch from Matt Edman to improve error messages.
30495 - When the controller asks for a config option with an abbreviated
30496 name, give the full name in our response.
30497 - Correct the man page entry on TrackHostExitsExpire.
30498 - Looks like we were never delivering deflated (i.e. compressed)
30499 running-routers lists, even when asked. Oops.
30500 - When --disable-threads is set, do not search for or link against
30501 pthreads libraries.
30503 o Bugfixes on 0.1.1.x:
30504 - Fix a seg fault with autodetecting which controller version is
30508 - New hidden service descriptor format: put a version in it, and
30509 let people specify introduction/rendezvous points that aren't
30510 in "the directory" (which is subjective anyway).
30511 - Allow the DEBUG controller event to work again. Mark certain log
30512 entries as "don't tell this to controllers", so we avoid cycles.
30515 Changes in version 0.1.0.11 - 2005-06-30
30516 o Bugfixes on 0.1.0.x:
30517 - Fix major security bug: servers were disregarding their
30518 exit policies if clients behaved unexpectedly.
30519 - Make OS X init script check for missing argument, so we don't
30520 confuse users who invoke it incorrectly.
30521 - Fix a seg fault in "tor --hash-password foo".
30522 - The MAPADDRESS control command was broken.
30525 Changes in version 0.1.1.1-alpha - 2005-06-29
30527 - Make OS X init script check for missing argument, so we don't
30528 confuse users who invoke it incorrectly.
30529 - Fix a seg fault in "tor --hash-password foo".
30530 - Fix a possible way to DoS dirservers.
30531 - When we complain that your exit policy implicitly allows local or
30532 private address spaces, name them explicitly so operators can
30534 - Make the log message less scary when all the dirservers are
30535 temporarily unreachable.
30536 - We were printing the number of idle dns workers incorrectly when
30540 - Revised controller protocol (version 1) that uses ascii rather
30541 than binary. Add supporting libraries in python and java so you
30542 can use the controller from your applications without caring how
30543 our protocol works.
30544 - Spiffy new support for crypto hardware accelerators. Can somebody
30548 Changes in version 0.0.9.10 - 2005-06-16
30549 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30550 - Refuse relay cells that claim to have a length larger than the
30551 maximum allowed. This prevents a potential attack that could read
30552 arbitrary memory (e.g. keys) from an exit server's process
30556 Changes in version 0.1.0.10 - 2005-06-14
30557 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30558 libevent before 1.1a.
30561 Changes in version 0.1.0.9-rc - 2005-06-09
30563 - Reset buf->highwater every time buf_shrink() is called, not just on
30564 a successful shrink. This was causing significant memory bloat.
30565 - Fix buffer overflow when checking hashed passwords.
30566 - Security fix: if seeding the RNG on Win32 fails, quit.
30567 - Allow seeding the RNG on Win32 even when you're not running as
30569 - Disable threading on Solaris too. Something is wonky with it,
30570 cpuworkers, and reentrant libs.
30571 - Reenable the part of the code that tries to flush as soon as an
30572 OR outbuf has a full TLS record available. Perhaps this will make
30573 OR outbufs not grow as huge except in rare cases, thus saving lots
30574 of CPU time plus memory.
30575 - Reject malformed .onion addresses rather then passing them on as
30576 normal web requests.
30577 - Adapt patch from Adam Langley: fix possible memory leak in
30578 tor_lookup_hostname().
30579 - Initialize libevent later in the startup process, so the logs are
30580 already established by the time we start logging libevent warns.
30581 - Use correct errno on win32 if libevent fails.
30582 - Check and warn about known-bad/slow libevent versions.
30583 - Pay more attention to the ClientOnly config option.
30584 - Have torctl.in/tor.sh.in check for location of su binary (needed
30586 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30587 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30588 HttpProxyAuthenticator
30589 - Stop warning about sigpipes in the logs. We're going to
30590 pretend that getting these occasionally is normal and fine.
30591 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30593 installer screens; and don't put stuff into StartupItems unless
30594 the user asks you to.
30595 - Require servers that use the default dirservers to have public IP
30596 addresses. We have too many servers that are configured with private
30597 IPs and their admins never notice the log entries complaining that
30598 their descriptors are being rejected.
30599 - Add OSX uninstall instructions. An actual uninstall script will
30603 Changes in version 0.1.0.8-rc - 2005-05-23
30605 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30606 panics. Disable kqueue on all OS X Tors.
30607 - Fix RPM: remove duplicate line accidentally added to the rpm
30609 - Disable threads on openbsd too, since its gethostaddr is not
30611 - Tolerate libevent 0.8 since it still works, even though it's
30613 - Enable building on Red Hat 9.0 again.
30614 - Allow the middle hop of the testing circuit to be running any
30615 version, now that most of them have the bugfix to let them connect
30616 to unknown servers. This will allow reachability testing to work
30617 even when 0.0.9.7-0.0.9.9 become obsolete.
30618 - Handle relay cells with rh.length too large. This prevents
30619 a potential attack that could read arbitrary memory (maybe even
30620 keys) from the exit server's process.
30621 - We screwed up the dirport reachability testing when we don't yet
30622 have a cached version of the directory. Hopefully now fixed.
30623 - Clean up router_load_single_router() (used by the controller),
30624 so it doesn't seg fault on error.
30625 - Fix a minor memory leak when somebody establishes an introduction
30626 point at your Tor server.
30627 - If a socks connection ends because read fails, don't warn that
30628 you're not sending a socks reply back.
30631 - Add HttpProxyAuthenticator config option too, that works like
30632 the HttpsProxyAuthenticator config option.
30633 - Encode hashed controller passwords in hex instead of base64,
30634 to make it easier to write controllers.
30637 Changes in version 0.1.0.7-rc - 2005-05-17
30639 - Fix a bug in the OS X package installer that prevented it from
30640 installing on Tiger.
30641 - Fix a script bug in the OS X package installer that made it
30642 complain during installation.
30643 - Find libevent even if it's hiding in /usr/local/ and your
30644 CFLAGS and LDFLAGS don't tell you to look there.
30645 - Be able to link with libevent as a shared library (the default
30646 after 1.0d), even if it's hiding in /usr/local/lib and even
30647 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30648 assuming you're running gcc. Otherwise fail and give a useful
30650 - Fix a bug in the RPM packager: set home directory for _tor to
30651 something more reasonable when first installing.
30652 - Free a minor amount of memory that is still reachable on exit.
30655 Changes in version 0.1.0.6-rc - 2005-05-14
30657 - Implement --disable-threads configure option. Disable threads on
30658 netbsd by default, because it appears to have no reentrant resolver
30660 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30661 release (1.1) detects and disables kqueue if it's broken.
30662 - Append default exit policy before checking for implicit internal
30663 addresses. Now we don't log a bunch of complaints on startup
30664 when using the default exit policy.
30665 - Some people were putting "Address " in their torrc, and they had
30666 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30667 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30668 LOCALSTATEDIR/tor instead.
30669 - Fix fragmented-message bug in TorControl.py.
30670 - Resolve a minor bug which would prevent unreachable dirports
30671 from getting suppressed in the published descriptor.
30672 - When the controller gave us a new descriptor, we weren't resolving
30673 it immediately, so Tor would think its address was 0.0.0.0 until
30674 we fetched a new directory.
30675 - Fix an uppercase/lowercase case error in suppressing a bogus
30676 libevent warning on some Linuxes.
30679 - Begin scrubbing sensitive strings from logs by default. Turn off
30680 the config option SafeLogging if you need to do debugging.
30681 - Switch to a new buffer management algorithm, which tries to avoid
30682 reallocing and copying quite as much. In first tests it looks like
30683 it uses *more* memory on average, but less cpu.
30684 - First cut at support for "create-fast" cells. Clients can use
30685 these when extending to their first hop, since the TLS already
30686 provides forward secrecy and authentication. Not enabled on
30688 - When dirservers refuse a router descriptor, we now log its
30689 contactinfo, platform, and the poster's IP address.
30690 - Call tor_free_all instead of connections_free_all after forking, to
30691 save memory on systems that need to fork.
30692 - Whine at you if you're a server and you don't set your contactinfo.
30693 - Implement --verify-config command-line option to check if your torrc
30694 is valid without actually launching Tor.
30695 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30696 rather than just rejecting it.
30699 Changes in version 0.1.0.5-rc - 2005-04-27
30701 - Stop trying to print a null pointer if an OR conn fails because
30702 we didn't like its cert.
30704 - Switch our internal buffers implementation to use a ring buffer,
30705 to hopefully improve performance for fast servers a lot.
30706 - Add HttpsProxyAuthenticator support (basic auth only), based
30707 on patch from Adam Langley.
30708 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30709 the fast servers that have been joining lately.
30710 - Give hidden service accesses extra time on the first attempt,
30711 since 60 seconds is often only barely enough. This might improve
30713 - Improve performance for dirservers: stop re-parsing the whole
30714 directory every time you regenerate it.
30715 - Add more debugging info to help us find the weird dns freebsd
30716 pthreads bug; cleaner debug messages to help track future issues.
30719 Changes in version 0.0.9.9 - 2005-04-23
30720 o Bugfixes on 0.0.9.x:
30721 - If unofficial Tor clients connect and send weird TLS certs, our
30722 Tor server triggers an assert. This release contains a minimal
30723 backport from the broader fix that we put into 0.1.0.4-rc.
30726 Changes in version 0.1.0.4-rc - 2005-04-23
30728 - If unofficial Tor clients connect and send weird TLS certs, our
30729 Tor server triggers an assert. Stop asserting, and start handling
30730 TLS errors better in other situations too.
30731 - When the controller asks us to tell it about all the debug-level
30732 logs, it turns out we were generating debug-level logs while
30733 telling it about them, which turns into a bad loop. Now keep
30734 track of whether you're sending a debug log to the controller,
30735 and don't log when you are.
30736 - Fix the "postdescriptor" feature of the controller interface: on
30737 non-complete success, only say "done" once.
30739 - Clients are now willing to load balance over up to 2mB, not 1mB,
30740 of advertised bandwidth capacity.
30741 - Add a NoPublish config option, so you can be a server (e.g. for
30742 testing running Tor servers in other Tor networks) without
30743 publishing your descriptor to the primary dirservers.
30746 Changes in version 0.1.0.3-rc - 2005-04-08
30747 o Improvements on 0.1.0.2-rc:
30748 - Client now retries when streams end early for 'hibernating' or
30749 'resource limit' reasons, rather than failing them.
30750 - More automated handling for dirserver operators:
30751 - Automatically approve nodes running 0.1.0.2-rc or later,
30752 now that the the reachability detection stuff is working.
30753 - Now we allow two unverified servers with the same nickname
30754 but different keys. But if a nickname is verified, only that
30755 nickname+key are allowed.
30756 - If you're an authdirserver connecting to an address:port,
30757 and it's not the OR you were expecting, forget about that
30758 descriptor. If he *was* the one you were expecting, then forget
30759 about all other descriptors for that address:port.
30760 - Allow servers to publish descriptors from 12 hours in the future.
30761 Corollary: only whine about clock skew from the dirserver if
30762 he's a trusted dirserver (since now even verified servers could
30763 have quite wrong clocks).
30764 - Adjust maximum skew and age for rendezvous descriptors: let skew
30765 be 48 hours rather than 90 minutes.
30766 - Efficiency improvements:
30767 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
30768 it much faster to look up a circuit for each relay cell.
30769 - Remove most calls to assert_all_pending_dns_resolves_ok(),
30770 since they're eating our cpu on exit nodes.
30771 - Stop wasting time doing a case insensitive comparison for every
30772 dns name every time we do any lookup. Canonicalize the names to
30773 lowercase and be done with it.
30774 - Start sending 'truncated' cells back rather than destroy cells,
30775 if the circuit closes in front of you. This means we won't have
30776 to abandon partially built circuits.
30777 - Only warn once per nickname from add_nickname_list_to_smartlist
30778 per failure, so an entrynode or exitnode choice that's down won't
30780 - Put a note in the torrc about abuse potential with the default
30782 - Revise control spec and implementation to allow all log messages to
30783 be sent to controller with their severities intact (suggested by
30784 Matt Edman). Update TorControl to handle new log event types.
30785 - Provide better explanation messages when controller's POSTDESCRIPTOR
30787 - Stop putting nodename in the Platform string in server descriptors.
30788 It doesn't actually help, and it is confusing/upsetting some people.
30790 o Bugfixes on 0.1.0.2-rc:
30791 - We were printing the host mask wrong in exit policies in server
30792 descriptors. This isn't a critical bug though, since we were still
30793 obeying the exit policy internally.
30794 - Fix Tor when compiled with libevent but without pthreads: move
30795 connection_unregister() from _connection_free() to
30797 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
30798 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
30799 when we look through the connection array, we'll find any of the
30800 cpu/dnsworkers. This is no good.
30802 o Bugfixes on 0.0.9.8:
30803 - Fix possible bug on threading platforms (e.g. win32) which was
30804 leaking a file descriptor whenever a cpuworker or dnsworker died.
30805 - When using preferred entry or exit nodes, ignore whether the
30806 circuit wants uptime or capacity. They asked for the nodes, they
30808 - chdir() to your datadirectory at the *end* of the daemonize process,
30809 not the beginning. This was a problem because the first time you
30810 run tor, if your datadir isn't there, and you have runasdaemon set
30811 to 1, it will try to chdir to it before it tries to create it. Oops.
30812 - Handle changed router status correctly when dirserver reloads
30813 fingerprint file. We used to be dropping all unverified descriptors
30814 right then. The bug was hidden because we would immediately
30815 fetch a directory from another dirserver, which would include the
30816 descriptors we just dropped.
30817 - When we're connecting to an OR and he's got a different nickname/key
30818 than we were expecting, only complain loudly if we're an OP or a
30819 dirserver. Complaining loudly to the OR admins just confuses them.
30820 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
30821 artificially capped at 500kB.
30824 Changes in version 0.0.9.8 - 2005-04-07
30825 o Bugfixes on 0.0.9.x:
30826 - We have a bug that I haven't found yet. Sometimes, very rarely,
30827 cpuworkers get stuck in the 'busy' state, even though the cpuworker
30828 thinks of itself as idle. This meant that no new circuits ever got
30829 established. Here's a workaround to kill any cpuworker that's been
30830 busy for more than 100 seconds.
30833 Changes in version 0.1.0.2-rc - 2005-04-01
30834 o Bugfixes on 0.1.0.1-rc:
30835 - Fixes on reachability detection:
30836 - Don't check for reachability while hibernating.
30837 - If ORPort is reachable but DirPort isn't, still publish the
30838 descriptor, but zero out DirPort until it's found reachable.
30839 - When building testing circs for ORPort testing, use only
30840 high-bandwidth nodes, so fewer circuits fail.
30841 - Complain about unreachable ORPort separately from unreachable
30842 DirPort, so the user knows what's going on.
30843 - Make sure we only conclude ORPort reachability if we didn't
30844 initiate the conn. Otherwise we could falsely conclude that
30845 we're reachable just because we connected to the guy earlier
30846 and he used that same pipe to extend to us.
30847 - Authdirservers shouldn't do ORPort reachability detection,
30848 since they're in clique mode, so it will be rare to find a
30849 server not already connected to them.
30850 - When building testing circuits, always pick middle hops running
30851 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
30852 bug. (This is a kludge; it will go away when 0.0.9.x becomes
30854 - When we decide we're reachable, actually publish our descriptor
30856 - Fix bug in redirectstream in the controller.
30857 - Fix the state descriptor strings so logs don't claim edge streams
30858 are in a different state than they actually are.
30859 - Use recent libevent features when possible (this only really affects
30860 win32 and osx right now, because the new libevent with these
30861 features hasn't been released yet). Add code to suppress spurious
30863 - Prevent possible segfault in connection_close_unattached_ap().
30864 - Fix newlines on torrc in win32.
30865 - Improve error msgs when tor-resolve fails.
30867 o Improvements on 0.0.9.x:
30868 - New experimental script tor/contrib/ExerciseServer.py (needs more
30869 work) that uses the controller interface to build circuits and
30870 fetch pages over them. This will help us bootstrap servers that
30871 have lots of capacity but haven't noticed it yet.
30872 - New experimental script tor/contrib/PathDemo.py (needs more work)
30873 that uses the controller interface to let you choose whole paths
30875 "<hostname>.<path,separated by dots>.<length of path>.path"
30876 - When we've connected to an OR and handshaked but didn't like
30877 the result, we were closing the conn without sending destroy
30878 cells back for pending circuits. Now send those destroys.
30881 Changes in version 0.0.9.7 - 2005-04-01
30882 o Bugfixes on 0.0.9.x:
30883 - Fix another race crash bug (thanks to Glenn Fink for reporting).
30884 - Compare identity to identity, not to nickname, when extending to
30885 a router not already in the directory. This was preventing us from
30886 extending to unknown routers. Oops.
30887 - Make sure to create OS X Tor user in <500 range, so we aren't
30888 creating actual system users.
30889 - Note where connection-that-hasn't-sent-end was marked, and fix
30890 a few really loud instances of this harmless bug (it's fixed more
30894 Changes in version 0.1.0.1-rc - 2005-03-28
30896 - Add reachability testing. Your Tor server will automatically try
30897 to see if its ORPort and DirPort are reachable from the outside,
30898 and it won't upload its descriptor until it decides they are.
30899 - Handle unavailable hidden services better. Handle slow or busy
30900 hidden services better.
30901 - Add support for CONNECTing through https proxies, with "HttpsProxy"
30903 - New exit policy: accept most low-numbered ports, rather than
30904 rejecting most low-numbered ports.
30905 - More Tor controller support (still experimental). See
30906 http://tor.eff.org/doc/control-spec.txt for all the new features,
30907 including signals to emulate unix signals from any platform;
30908 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
30909 closestream; closecircuit; etc.
30910 - Make nt services work and start on startup on win32 (based on
30911 patch by Matt Edman).
30912 - Add a new AddressMap config directive to rewrite incoming socks
30913 addresses. This lets you, for example, declare an implicit
30914 required exit node for certain sites.
30915 - Add a new TrackHostExits config directive to trigger addressmaps
30916 for certain incoming socks addresses -- for sites that break when
30917 your exit keeps changing (based on patch by Mike Perry).
30918 - Redo the client-side dns cache so it's just an addressmap too.
30919 - Notice when our IP changes, and reset stats/uptime/reachability.
30920 - When an application is using socks5, give him the whole variety of
30921 potential socks5 responses (connect refused, host unreachable, etc),
30922 rather than just "success" or "failure".
30923 - A more sane version numbering system. See
30924 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
30925 - New contributed script "exitlist": a simple python script to
30926 parse directories and find Tor nodes that exit to listed
30928 - New contributed script "privoxy-tor-toggle" to toggle whether
30929 Privoxy uses Tor. Seems to be configured for Debian by default.
30930 - Report HTTP reasons to client when getting a response from directory
30931 servers -- so you can actually know what went wrong.
30932 - New config option MaxAdvertisedBandwidth which lets you advertise
30933 a low bandwidthrate (to not attract as many circuits) while still
30934 allowing a higher bandwidthrate in reality.
30936 o Robustness/stability fixes:
30937 - Make Tor use Niels Provos's libevent instead of its current
30938 poll-but-sometimes-select mess. This will let us use faster async
30939 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
30941 - pthread support now too. This was forced because when we forked,
30942 we ended up wasting a lot of duplicate ram over time. Also switch
30943 to foo_r versions of some library calls to allow reentry and
30945 - Better handling for heterogeneous / unreliable nodes:
30946 - Annotate circuits w/ whether they aim to contain high uptime nodes
30947 and/or high capacity nodes. When building circuits, choose
30949 - This means that every single node in an intro rend circuit,
30950 not just the last one, will have a minimum uptime.
30951 - New config option LongLivedPorts to indicate application streams
30952 that will want high uptime circuits.
30953 - Servers reset uptime when a dir fetch entirely fails. This
30954 hopefully reflects stability of the server's network connectivity.
30955 - If somebody starts his tor server in Jan 2004 and then fixes his
30956 clock, don't make his published uptime be a year.
30957 - Reset published uptime when you wake up from hibernation.
30958 - Introduce a notion of 'internal' circs, which are chosen without
30959 regard to the exit policy of the last hop. Intro and rendezvous
30960 circs must be internal circs, to avoid leaking information. Resolve
30961 and connect streams can use internal circs if they want.
30962 - New circuit pooling algorithm: make sure to have enough circs around
30963 to satisfy any predicted ports, and also make sure to have 2 internal
30964 circs around if we've required internal circs lately (and with high
30965 uptime if we've seen that lately too).
30966 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
30967 which describes how often we retry making new circuits if current
30968 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
30969 how long we're willing to make use of an already-dirty circuit.
30970 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
30971 circ as necessary, if there are any completed ones lying around
30972 when we try to launch one.
30973 - Make hidden services try to establish a rendezvous for 30 seconds,
30974 rather than for n (where n=3) attempts to build a circuit.
30975 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
30976 "ShutdownWaitLength".
30977 - Try to be more zealous about calling connection_edge_end when
30978 things go bad with edge conns in connection.c.
30979 - Revise tor-spec to add more/better stream end reasons.
30980 - Revise all calls to connection_edge_end to avoid sending "misc",
30981 and to take errno into account where possible.
30984 - Fix a race condition that can trigger an assert, when we have a
30985 pending create cell and an OR connection fails right then.
30986 - Fix several double-mark-for-close bugs, e.g. where we were finding
30987 a conn for a cell even if that conn is already marked for close.
30988 - Make sequence of log messages when starting on win32 with no config
30989 file more reasonable.
30990 - When choosing an exit node for a new non-internal circ, don't take
30991 into account whether it'll be useful for any pending x.onion
30992 addresses -- it won't.
30993 - Turn addr_policy_compare from a tristate to a quadstate; this should
30994 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
30995 for google.com" problem.
30996 - Make "platform" string in descriptor more accurate for Win32 servers,
30997 so it's not just "unknown platform".
30998 - Fix an edge case in parsing config options (thanks weasel).
30999 If they say "--" on the commandline, it's not an option.
31000 - Reject odd-looking addresses at the client (e.g. addresses that
31001 contain a colon), rather than having the server drop them because
31003 - tor-resolve requests were ignoring .exit if there was a working circuit
31004 they could use instead.
31005 - REUSEADDR on normal platforms means you can rebind to the port
31006 right after somebody else has let it go. But REUSEADDR on win32
31007 means to let you bind to the port _even when somebody else
31008 already has it bound_! So, don't do that on Win32.
31009 - Change version parsing logic: a version is "obsolete" if it is not
31010 recommended and (1) there is a newer recommended version in the
31011 same series, or (2) there are no recommended versions in the same
31012 series, but there are some recommended versions in a newer series.
31013 A version is "new" if it is newer than any recommended version in
31015 - Stop most cases of hanging up on a socks connection without sending
31019 - Require BandwidthRate to be at least 20kB/s for servers.
31020 - When a dirserver causes you to give a warn, mention which dirserver
31022 - New config option DirAllowPrivateAddresses for authdirservers.
31023 Now by default they refuse router descriptors that have non-IP or
31024 private-IP addresses.
31025 - Stop publishing socksport in the directory, since it's not
31026 actually meant to be public. For compatibility, publish a 0 there
31028 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
31029 smart" value, that is low for servers and high for clients.
31030 - If our clock jumps forward by 100 seconds or more, assume something
31031 has gone wrong with our network and abandon all not-yet-used circs.
31032 - Warn when exit policy implicitly allows local addresses.
31033 - If we get an incredibly skewed timestamp from a dirserver mirror
31034 that isn't a verified OR, don't warn -- it's probably him that's
31036 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
31037 cookies to disk and doesn't log each web request to disk. (Thanks
31038 to Brett Carrington for pointing this out.)
31039 - When a client asks us for a dir mirror and we don't have one,
31040 launch an attempt to get a fresh one.
31041 - If we're hibernating and we get a SIGINT, exit immediately.
31042 - Add --with-dmalloc ./configure option, to track memory leaks.
31043 - And try to free all memory on closing, so we can detect what
31045 - Cache local dns resolves correctly even when they're .exit
31047 - Give a better warning when some other server advertises an
31048 ORPort that is actually an apache running ssl.
31049 - Add "opt hibernating 1" to server descriptor to make it clearer
31050 whether the server is hibernating.
31053 Changes in version 0.0.9.6 - 2005-03-24
31054 o Bugfixes on 0.0.9.x (crashes and asserts):
31055 - Add new end stream reasons to maintenance branch. Fix bug where
31056 reason (8) could trigger an assert. Prevent bug from recurring.
31057 - Apparently win32 stat wants paths to not end with a slash.
31058 - Fix assert triggers in assert_cpath_layer_ok(), where we were
31059 blowing away the circuit that conn->cpath_layer points to, then
31060 checking to see if the circ is well-formed. Backport check to make
31061 sure we dont use the cpath on a closed connection.
31062 - Prevent circuit_resume_edge_reading_helper() from trying to package
31063 inbufs for marked-for-close streams.
31064 - Don't crash on hup if your options->address has become unresolvable.
31065 - Some systems (like OS X) sometimes accept() a connection and tell
31066 you the remote host is 0.0.0.0:0. If this happens, due to some
31067 other mis-features, we get confused; so refuse the conn for now.
31069 o Bugfixes on 0.0.9.x (other):
31070 - Fix harmless but scary "Unrecognized content encoding" warn message.
31071 - Add new stream error reason: TORPROTOCOL reason means "you are not
31072 speaking a version of Tor I understand; say bye-bye to your stream."
31073 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
31074 into the future, now that we are more tolerant of skew. This
31075 resolves a bug where a Tor server would refuse to cache a directory
31076 because all the directories it gets are too far in the future;
31077 yet the Tor server never logs any complaints about clock skew.
31078 - Mac packaging magic: make man pages useable, and do not overwrite
31079 existing torrc files.
31080 - Make OS X log happily to /var/log/tor/tor.log
31083 Changes in version 0.0.9.5 - 2005-02-22
31084 o Bugfixes on 0.0.9.x:
31085 - Fix an assert race at exit nodes when resolve requests fail.
31086 - Stop picking unverified dir mirrors--it only leads to misery.
31087 - Patch from Matt Edman to make NT services work better. Service
31088 support is still not compiled into the executable by default.
31089 - Patch from Dmitri Bely so the Tor service runs better under
31090 the win32 SYSTEM account.
31091 - Make tor-resolve actually work (?) on Win32.
31092 - Fix a sign bug when getrlimit claims to have 4+ billion
31093 file descriptors available.
31094 - Stop refusing to start when bandwidthburst == bandwidthrate.
31095 - When create cells have been on the onion queue more than five
31096 seconds, just send back a destroy and take them off the list.
31099 Changes in version 0.0.9.4 - 2005-02-03
31100 o Bugfixes on 0.0.9:
31101 - Fix an assert bug that took down most of our servers: when
31102 a server claims to have 1 GB of bandwidthburst, don't
31104 - Don't crash as badly if we have spawned the max allowed number
31105 of dnsworkers, or we're out of file descriptors.
31106 - Block more file-sharing ports in the default exit policy.
31107 - MaxConn is now automatically set to the hard limit of max
31108 file descriptors we're allowed (ulimit -n), minus a few for
31110 - Give a clearer message when servers need to raise their
31111 ulimit -n when they start running out of file descriptors.
31112 - SGI Compatibility patches from Jan Schaumann.
31113 - Tolerate a corrupt cached directory better.
31114 - When a dirserver hasn't approved your server, list which one.
31115 - Go into soft hibernation after 95% of the bandwidth is used,
31116 not 99%. This is especially important for daily hibernators who
31117 have a small accounting max. Hopefully it will result in fewer
31118 cut connections when the hard hibernation starts.
31119 - Load-balance better when using servers that claim more than
31120 800kB/s of capacity.
31121 - Make NT services work (experimental, only used if compiled in).
31124 Changes in version 0.0.9.3 - 2005-01-21
31125 o Bugfixes on 0.0.9:
31126 - Backport the cpu use fixes from main branch, so busy servers won't
31127 need as much processor time.
31128 - Work better when we go offline and then come back, or when we
31129 run Tor at boot before the network is up. We do this by
31130 optimistically trying to fetch a new directory whenever an
31131 application request comes in and we think we're offline -- the
31132 human is hopefully a good measure of when the network is back.
31133 - Backport some minimal hidserv bugfixes: keep rend circuits open as
31134 long as you keep using them; actually publish hidserv descriptors
31135 shortly after they change, rather than waiting 20-40 minutes.
31136 - Enable Mac startup script by default.
31137 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
31138 - When you update AllowUnverifiedNodes or FirewallPorts via the
31139 controller's setconf feature, we were always appending, never
31141 - When you update HiddenServiceDir via setconf, it was screwing up
31142 the order of reading the lines, making it fail.
31143 - Do not rewrite a cached directory back to the cache; otherwise we
31144 will think it is recent and not fetch a newer one on startup.
31145 - Workaround for webservers that lie about Content-Encoding: Tor
31146 now tries to autodetect compressed directories and compression
31147 itself. This lets us Proxypass dir fetches through apache.
31150 Changes in version 0.0.9.2 - 2005-01-04
31151 o Bugfixes on 0.0.9 (crashes and asserts):
31152 - Fix an assert on startup when the disk is full and you're logging
31154 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
31155 style address, then we'd crash.
31156 - Fix an assert trigger when the running-routers string we get from
31157 a dirserver is broken.
31158 - Make worker threads start and run on win32. Now win32 servers
31160 - Bandaid (not actually fix, but now it doesn't crash) an assert
31161 where the dns worker dies mysteriously and the main Tor process
31162 doesn't remember anything about the address it was resolving.
31164 o Bugfixes on 0.0.9 (Win32):
31165 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
31166 name out of the warning/assert messages.
31167 - Fix a superficial "unhandled error on read" bug on win32.
31168 - The win32 installer no longer requires a click-through for our
31169 license, since our Free Software license grants rights but does not
31171 - Win32: When connecting to a dirserver fails, try another one
31172 immediately. (This was already working for non-win32 Tors.)
31173 - Stop trying to parse $HOME on win32 when hunting for default
31175 - Make tor-resolve.c work on win32 by calling network_init().
31177 o Bugfixes on 0.0.9 (other):
31178 - Make 0.0.9.x build on Solaris again.
31179 - Due to a fencepost error, we were blowing away the \n when reporting
31180 confvalue items in the controller. So asking for multiple config
31181 values at once couldn't work.
31182 - When listing circuits that are pending on an opening OR connection,
31183 if we're an OR we were listing circuits that *end* at us as
31184 being pending on every listener, dns/cpu worker, etc. Stop that.
31185 - Dirservers were failing to create 'running-routers' or 'directory'
31186 strings if we had more than some threshold of routers. Fix them so
31187 they can handle any number of routers.
31188 - Fix a superficial "Duplicate mark for close" bug.
31189 - Stop checking for clock skew for OR connections, even for servers.
31190 - Fix a fencepost error that was chopping off the last letter of any
31191 nickname that is the maximum allowed nickname length.
31192 - Update URLs in log messages so they point to the new website.
31193 - Fix a potential problem in mangling server private keys while
31194 writing to disk (not triggered yet, as far as we know).
31195 - Include the licenses for other free software we include in Tor,
31196 now that we're shipping binary distributions more regularly.
31199 Changes in version 0.0.9.1 - 2004-12-15
31200 o Bugfixes on 0.0.9:
31201 - Make hibernation actually work.
31202 - Make HashedControlPassword config option work.
31203 - When we're reporting event circuit status to a controller,
31204 don't use the stream status code.
31207 Changes in version 0.0.9 - 2004-12-12
31209 - Clean up manpage and torrc.sample file.
31210 - Clean up severities and text of log warnings.
31212 - Make servers trigger an assert when they enter hibernation.
31215 Changes in version 0.0.9rc7 - 2004-12-08
31216 o Bugfixes on 0.0.9rc:
31217 - Fix a stack-trashing crash when an exit node begins hibernating.
31218 - Avoid looking at unallocated memory while considering which
31219 ports we need to build circuits to cover.
31220 - Stop a sigpipe: when an 'end' cell races with eof from the app,
31221 we shouldn't hold-open-until-flush if the eof arrived first.
31222 - Fix a bug with init_cookie_authentication() in the controller.
31223 - When recommending new-format log lines, if the upper bound is
31224 LOG_ERR, leave it implicit.
31226 o Bugfixes on 0.0.8.1:
31227 - Fix a whole slew of memory leaks.
31228 - Fix isspace() and friends so they still make Solaris happy
31229 but also so they don't trigger asserts on win32.
31230 - Fix parse_iso_time on platforms without strptime (eg win32).
31231 - win32: tolerate extra "readable" events better.
31232 - win32: when being multithreaded, leave parent fdarray open.
31233 - Make unit tests work on win32.
31236 Changes in version 0.0.9rc6 - 2004-12-06
31237 o Bugfixes on 0.0.9pre:
31238 - Clean up some more integer underflow opportunities (not exploitable
31240 - While hibernating, hup should not regrow our listeners.
31241 - Send an end to the streams we close when we hibernate, rather
31242 than just chopping them off.
31243 - React to eof immediately on non-open edge connections.
31245 o Bugfixes on 0.0.8.1:
31246 - Calculate timeout for waiting for a connected cell from the time
31247 we sent the begin cell, not from the time the stream started. If
31248 it took a long time to establish the circuit, we would time out
31249 right after sending the begin cell.
31250 - Fix router_compare_addr_to_addr_policy: it was not treating a port
31251 of * as always matching, so we were picking reject *:* nodes as
31252 exit nodes too. Oops.
31255 - New circuit building strategy: keep a list of ports that we've
31256 used in the past 6 hours, and always try to have 2 circuits open
31257 or on the way that will handle each such port. Seed us with port
31258 80 so web users won't complain that Tor is "slow to start up".
31259 - Make kill -USR1 dump more useful stats about circuits.
31260 - When warning about retrying or giving up, print the address, so
31261 the user knows which one it's talking about.
31262 - If you haven't used a clean circuit in an hour, throw it away,
31263 just to be on the safe side. (This means after 6 hours a totally
31264 unused Tor client will have no circuits open.)
31267 Changes in version 0.0.9rc5 - 2004-12-01
31268 o Bugfixes on 0.0.8.1:
31269 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
31270 - Let resolve conns retry/expire also, rather than sticking around
31272 - If we are using select, make sure we stay within FD_SETSIZE.
31274 o Bugfixes on 0.0.9pre:
31275 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
31276 but doesn't seem to be currently; thanks to Ilja van Sprundel for
31278 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
31279 instead. Impose minima and maxima for all *Period options; impose
31280 even tighter maxima for fetching if we are a caching dirserver.
31281 Clip rather than rejecting.
31282 - Fetch cached running-routers from servers that serve it (that is,
31283 authdirservers and servers running 0.0.9rc5-cvs or later.)
31286 - Accept *:706 (silc) in default exit policy.
31287 - Implement new versioning format for post 0.1.
31288 - Support "foo.nickname.exit" addresses, to let Alice request the
31289 address "foo" as viewed by exit node "nickname". Based on a patch
31291 - Make tor --version --version dump the cvs Id of every file.
31294 Changes in version 0.0.9rc4 - 2004-11-28
31295 o Bugfixes on 0.0.8.1:
31296 - Make windows sockets actually non-blocking (oops), and handle
31297 win32 socket errors better.
31299 o Bugfixes on 0.0.9rc1:
31300 - Actually catch the -USR2 signal.
31303 Changes in version 0.0.9rc3 - 2004-11-25
31304 o Bugfixes on 0.0.8.1:
31305 - Flush the log file descriptor after we print "Tor opening log file",
31306 so we don't see those messages days later.
31308 o Bugfixes on 0.0.9rc1:
31309 - Make tor-resolve work again.
31310 - Avoid infinite loop in tor-resolve if tor hangs up on it.
31311 - Fix an assert trigger for clients/servers handling resolves.
31314 Changes in version 0.0.9rc2 - 2004-11-24
31315 o Bugfixes on 0.0.9rc1:
31316 - I broke socks5 support while fixing the eof bug.
31317 - Allow unitless bandwidths and intervals; they default to bytes
31319 - New servers don't start out hibernating; they are active until
31320 they run out of bytes, so they have a better estimate of how
31321 long it takes, and so their operators can know they're working.
31324 Changes in version 0.0.9rc1 - 2004-11-23
31325 o Bugfixes on 0.0.8.1:
31326 - Finally fix a bug that's been plaguing us for a year:
31327 With high load, circuit package window was reaching 0. Whenever
31328 we got a circuit-level sendme, we were reading a lot on each
31329 socket, but only writing out a bit. So we would eventually reach
31330 eof. This would be noticed and acted on even when there were still
31331 bytes sitting in the inbuf.
31332 - When poll() is interrupted, we shouldn't believe the revents values.
31334 o Bugfixes on 0.0.9pre6:
31335 - Fix hibernate bug that caused pre6 to be broken.
31336 - Don't keep rephist info for routers that haven't had activity for
31337 24 hours. (This matters now that clients have keys, since we track
31339 - Never call close_temp_logs while validating log options.
31340 - Fix backslash-escaping on tor.sh.in and torctl.in.
31343 - Implement weekly/monthly/daily accounting: now you specify your
31344 hibernation properties by
31345 AccountingMax N bytes|KB|MB|GB|TB
31346 AccountingStart day|week|month [day] HH:MM
31347 Defaults to "month 1 0:00".
31348 - Let bandwidth and interval config options be specified as 5 bytes,
31349 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
31350 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
31351 get back to normal.)
31352 - If your requested entry or exit node has advertised bandwidth 0,
31354 - Be more greedy about filling up relay cells -- we try reading again
31355 once we've processed the stuff we read, in case enough has arrived
31356 to fill the last cell completely.
31357 - Apply NT service patch from Osamu Fujino. Still needs more work.
31360 Changes in version 0.0.9pre6 - 2004-11-15
31361 o Bugfixes on 0.0.8.1:
31362 - Fix assert failure on malformed socks4a requests.
31363 - Use identity comparison, not nickname comparison, to choose which
31364 half of circuit-ID-space each side gets to use. This is needed
31365 because sometimes we think of a router as a nickname, and sometimes
31366 as a hex ID, and we can't predict what the other side will do.
31367 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
31368 write() call will fail and we handle it there.
31369 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
31370 and smartlist_len, which are two major profiling offenders.
31372 o Bugfixes on 0.0.9pre5:
31373 - Fix a bug in read_all that was corrupting config files on windows.
31374 - When we're raising the max number of open file descriptors to
31375 'unlimited', don't log that we just raised it to '-1'.
31376 - Include event code with events, as required by control-spec.txt.
31377 - Don't give a fingerprint when clients do --list-fingerprint:
31378 it's misleading, because it will never be the same again.
31379 - Stop using strlcpy in tor_strndup, since it was slowing us
31381 - Remove warn on startup about missing cached-directory file.
31382 - Make kill -USR1 work again.
31383 - Hibernate if we start tor during the "wait for wakeup-time" phase
31384 of an accounting interval. Log our hibernation plans better.
31385 - Authoritative dirservers now also cache their directory, so they
31386 have it on start-up.
31389 - Fetch running-routers; cache running-routers; compress
31390 running-routers; serve compressed running-routers.z
31391 - Add NSI installer script contributed by J Doe.
31392 - Commit VC6 and VC7 workspace/project files.
31393 - Commit a tor.spec for making RPM files, with help from jbash.
31394 - Add contrib/torctl.in contributed by Glenn Fink.
31395 - Implement the control-spec's SAVECONF command, to write your
31396 configuration to torrc.
31397 - Get cookie authentication for the controller closer to working.
31398 - Include control-spec.txt in the tarball.
31399 - When set_conf changes our server descriptor, upload a new copy.
31400 But don't upload it too often if there are frequent changes.
31401 - Document authentication config in man page, and document signals
31403 - Clean up confusing parts of man page and torrc.sample.
31404 - Make expand_filename handle ~ and ~username.
31405 - Use autoconf to enable largefile support where necessary. Use
31406 ftello where available, since ftell can fail at 2GB.
31407 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
31408 log more informatively.
31409 - Give a slightly more useful output for "tor -h".
31410 - Refuse application socks connections to port 0.
31411 - Check clock skew for verified servers, but allow unverified
31412 servers and clients to have any clock skew.
31413 - Break DirFetchPostPeriod into:
31414 - DirFetchPeriod for fetching full directory,
31415 - StatusFetchPeriod for fetching running-routers,
31416 - DirPostPeriod for posting server descriptor,
31417 - RendPostPeriod for posting hidden service descriptors.
31418 - Make sure the hidden service descriptors are at a random offset
31419 from each other, to hinder linkability.
31422 Changes in version 0.0.9pre5 - 2004-11-09
31423 o Bugfixes on 0.0.9pre4:
31424 - Fix a seg fault in unit tests (doesn't affect main program).
31425 - Fix an assert bug where a hidden service provider would fail if
31426 the first hop of his rendezvous circuit was down.
31427 - Hidden service operators now correctly handle version 1 style
31428 INTRODUCE1 cells (nobody generates them still, so not a critical
31430 - If do_hup fails, actually notice.
31431 - Handle more errnos from accept() without closing the listener.
31432 Some OpenBSD machines were closing their listeners because
31433 they ran out of file descriptors.
31434 - Send resolve cells to exit routers that are running a new
31435 enough version of the resolve code to work right.
31436 - Better handling of winsock includes on non-MSV win32 compilers.
31437 - Some people had wrapped their tor client/server in a script
31438 that would restart it whenever it died. This did not play well
31439 with our "shut down if your version is obsolete" code. Now people
31440 don't fetch a new directory if their local cached version is
31442 - Make our autogen.sh work on ksh as well as bash.
31445 - Hibernation: New config option "AccountingMaxKB" lets you
31446 set how many KBytes per month you want to allow your server to
31447 consume. Rather than spreading those bytes out evenly over the
31448 month, we instead hibernate for some of the month and pop up
31449 at a deterministic time, work until the bytes are consumed, then
31450 hibernate again. Config option "MonthlyAccountingStart" lets you
31451 specify which day of the month your billing cycle starts on.
31452 - Control interface: a separate program can now talk to your
31453 client/server over a socket, and get/set config options, receive
31454 notifications of circuits and streams starting/finishing/dying,
31455 bandwidth used, etc. The next step is to get some GUIs working.
31456 Let us know if you want to help out. See doc/control-spec.txt .
31457 - Ship a contrib/tor-control.py as an example script to interact
31458 with the control port.
31459 - "tor --hash-password zzyxz" will output a salted password for
31460 use in authenticating to the control interface.
31461 - New log format in config:
31462 "Log minsev[-maxsev] stdout|stderr|syslog" or
31463 "Log minsev[-maxsev] file /var/foo"
31466 - DirPolicy config option, to let people reject incoming addresses
31467 from their dirserver.
31468 - "tor --list-fingerprint" will list your identity key fingerprint
31470 - Add "pass" target for RedirectExit, to make it easier to break
31471 out of a sequence of RedirectExit rules.
31472 - Clients now generate a TLS cert too, in preparation for having
31473 them act more like real nodes.
31474 - Ship src/win32/ in the tarball, so people can use it to build.
31475 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
31477 - New "router-status" line in directory, to better bind each verified
31478 nickname to its identity key.
31479 - Deprecate unofficial config option abbreviations, and abbreviations
31480 not on the command line.
31481 - Add a pure-C tor-resolve implementation.
31482 - Use getrlimit and friends to ensure we can reach MaxConn (currently
31483 1024) file descriptors.
31485 o Code security improvements, inspired by Ilja:
31486 - Replace sprintf with snprintf. (I think they were all safe, but
31488 - Replace strcpy/strncpy with strlcpy in more places.
31489 - Avoid strcat; use snprintf or strlcat instead.
31490 - snprintf wrapper with consistent (though not C99) overflow behavior.
31493 Changes in version 0.0.9pre4 - 2004-10-17
31494 o Bugfixes on 0.0.9pre3:
31495 - If the server doesn't specify an exit policy, use the real default
31496 exit policy, not reject *:*.
31497 - Ignore fascistfirewall when uploading/downloading hidden service
31498 descriptors, since we go through Tor for those; and when using
31499 an HttpProxy, since we assume it can reach them all.
31500 - When looking for an authoritative dirserver, use only the ones
31501 configured at boot. Don't bother looking in the directory.
31502 - The rest of the fix for get_default_conf_file() on older win32.
31503 - Make 'Routerfile' config option obsolete.
31506 - New 'MyFamily nick1,...' config option for a server to
31507 specify other servers that shouldn't be used in the same circuit
31508 with it. Only believed if nick1 also specifies us.
31509 - New 'NodeFamily nick1,nick2,...' config option for a client to
31510 specify nodes that it doesn't want to use in the same circuit.
31511 - New 'Redirectexit pattern address:port' config option for a
31512 server to redirect exit connections, e.g. to a local squid.
31515 Changes in version 0.0.9pre3 - 2004-10-13
31516 o Bugfixes on 0.0.8.1:
31517 - Better torrc example lines for dirbindaddress and orbindaddress.
31518 - Improved bounds checking on parsed ints (e.g. config options and
31519 the ones we find in directories.)
31520 - Better handling of size_t vs int, so we're more robust on 64
31522 - Fix the rest of the bug where a newly started OR would appear
31523 as unverified even after we've added his fingerprint and hupped
31525 - Fix a bug from 0.0.7: when read() failed on a stream, we would
31526 close it without sending back an end. So 'connection refused'
31527 would simply be ignored and the user would get no response.
31529 o Bugfixes on 0.0.9pre2:
31530 - Serving the cached-on-disk directory to people is bad. We now
31531 provide no directory until we've fetched a fresh one.
31532 - Workaround for bug on windows where cached-directories get crlf
31534 - Make get_default_conf_file() work on older windows too.
31535 - If we write a *:* exit policy line in the descriptor, don't write
31536 any more exit policy lines.
31539 - Use only 0.0.9pre1 and later servers for resolve cells.
31540 - Make the dirservers file obsolete.
31541 - Include a dir-signing-key token in directories to tell the
31542 parsing entity which key is being used to sign.
31543 - Remove the built-in bulky default dirservers string.
31544 - New config option "Dirserver %s:%d [fingerprint]", which can be
31545 repeated as many times as needed. If no dirservers specified,
31546 default to moria1,moria2,tor26.
31547 - Make moria2 advertise a dirport of 80, so people behind firewalls
31548 will be able to get a directory.
31549 - Http proxy support
31550 - Dirservers translate requests for http://%s:%d/x to /x
31551 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31552 be routed through this host.
31553 - Clients ask for /tor/x rather than /x for new enough dirservers.
31554 This way we can one day coexist peacefully with apache.
31555 - Clients specify a "Host: %s%d" http header, to be compatible
31556 with more proxies, and so running squid on an exit node can work.
31559 Changes in version 0.0.8.1 - 2004-10-13
31561 - Fix a seg fault that can be triggered remotely for Tor
31562 clients/servers with an open dirport.
31563 - Fix a rare assert trigger, where routerinfos for entries in
31564 our cpath would expire while we're building the path.
31565 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31566 - Fix a rare seg fault for people running hidden services on
31567 intermittent connections.
31568 - Fix a bug in parsing opt keywords with objects.
31569 - Fix a stale pointer assert bug when a stream detaches and
31571 - Fix a string format vulnerability (probably not exploitable)
31572 in reporting stats locally.
31573 - Fix an assert trigger: sometimes launching circuits can fail
31574 immediately, e.g. because too many circuits have failed recently.
31575 - Fix a compile warning on 64 bit platforms.
31578 Changes in version 0.0.9pre2 - 2004-10-03
31580 - Make fetching a cached directory work for 64-bit platforms too.
31581 - Make zlib.h a required header, not an optional header.
31584 Changes in version 0.0.9pre1 - 2004-10-01
31586 - Stop using separate defaults for no-config-file and
31587 empty-config-file. Now you have to explicitly turn off SocksPort,
31588 if you don't want it open.
31589 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31590 - Improve man page to mention more of the 0.0.8 features.
31591 - Fix a rare seg fault for people running hidden services on
31592 intermittent connections.
31593 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31595 - Fix more dns related bugs: send back resolve_failed and end cells
31596 more reliably when the resolve fails, rather than closing the
31597 circuit and then trying to send the cell. Also attach dummy resolve
31598 connections to a circuit *before* calling dns_resolve(), to fix
31599 a bug where cached answers would never be sent in RESOLVED cells.
31600 - When we run out of disk space, or other log writing error, don't
31601 crash. Just stop logging to that log and continue.
31602 - We were starting to daemonize before we opened our logs, so if
31603 there were any problems opening logs, we would complain to stderr,
31604 which wouldn't work, and then mysteriously exit.
31605 - Fix a rare bug where sometimes a verified OR would connect to us
31606 before he'd uploaded his descriptor, which would cause us to
31607 assign conn->nickname as though he's unverified. Now we look through
31608 the fingerprint list to see if he's there.
31609 - Fix a rare assert trigger, where routerinfos for entries in
31610 our cpath would expire while we're building the path.
31613 - Clients can ask dirservers for /dir.z to get a compressed version
31614 of the directory. Only works for servers running 0.0.9, of course.
31615 - Make clients cache directories and use them to seed their router
31616 lists at startup. This means clients have a datadir again.
31617 - Configuration infrastructure support for warning on obsolete
31619 - Respond to content-encoding headers by trying to uncompress as
31621 - Reply with a deflated directory when a client asks for "dir.z".
31622 We could use allow-encodings instead, but allow-encodings isn't
31623 specified in HTTP 1.0.
31624 - Raise the max dns workers from 50 to 100.
31625 - Discourage people from setting their dirfetchpostperiod more often
31626 than once per minute.
31627 - Protect dirservers from overzealous descriptor uploading -- wait
31628 10 seconds after directory gets dirty, before regenerating.
31631 Changes in version 0.0.8 - 2004-08-25
31632 o Port it to SunOS 5.9 / Athena
31635 Changes in version 0.0.8rc2 - 2004-08-20
31636 o Make it compile on cygwin again.
31637 o When picking unverified routers, skip those with low uptime and/or
31638 low bandwidth, depending on what properties you care about.
31641 Changes in version 0.0.8rc1 - 2004-08-18
31642 o Changes from 0.0.7.3:
31644 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31645 don't put it into the client dns cache.
31646 - If a begin failed due to exit policy, but we believe the IP address
31647 should have been allowed, switch that router to exitpolicy reject *:*
31648 until we get our next directory.
31650 - Clients choose nodes proportional to advertised bandwidth.
31651 - Avoid using nodes with low uptime as introduction points.
31652 - Handle servers with dynamic IP addresses: don't replace
31653 options->Address with the resolved one at startup, and
31654 detect our address right before we make a routerinfo each time.
31655 - 'FascistFirewall' option to pick dirservers and ORs on specific
31656 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31657 which ports are open. (Defaults to 80,443)
31658 - Be more aggressive about trying to make circuits when the network
31659 has changed (e.g. when you unsuspend your laptop).
31660 - Check for time skew on http headers; report date in response to
31662 - If the entrynode config line has only one node, don't pick it as
31664 - Add strict{entry|exit}nodes config options. If set to 1, then
31665 we refuse to build circuits that don't include the specified entry
31667 - OutboundBindAddress config option, to bind to a specific
31668 IP address for outgoing connect()s.
31669 - End truncated log entries (e.g. directories) with "[truncated]".
31671 o Patches to 0.0.8preX:
31673 - Patches to compile and run on win32 again (maybe)?
31674 - Fix crash when looking for ~/.torrc with no $HOME set.
31675 - Fix a race bug in the unit tests.
31676 - Handle verified/unverified name collisions better when new
31677 routerinfo's arrive in a directory.
31678 - Sometimes routers were getting entered into the stats before
31679 we'd assigned their identity_digest. Oops.
31680 - Only pick and establish intro points after we've gotten a
31683 - AllowUnverifiedNodes config option to let circuits choose no-name
31684 routers in entry,middle,exit,introduction,rendezvous positions.
31685 Allow middle and rendezvous positions by default.
31686 - Add a man page for tor-resolve.
31689 Changes in version 0.0.7.3 - 2004-08-12
31690 o Stop dnsworkers from triggering an assert failure when you
31691 ask them to resolve the host "".
31694 Changes in version 0.0.8pre3 - 2004-08-09
31695 o Changes from 0.0.7.2:
31696 - Allow multiple ORs with same nickname in routerlist -- now when
31697 people give us one identity key for a nickname, then later
31698 another, we don't constantly complain until the first expires.
31699 - Remember used bandwidth (both in and out), and publish 15-minute
31700 snapshots for the past day into our descriptor.
31701 - You can now fetch $DIRURL/running-routers to get just the
31702 running-routers line, not the whole descriptor list. (But
31703 clients don't use this yet.)
31704 - When people mistakenly use Tor as an http proxy, point them
31705 at the tor-doc.html rather than the INSTALL.
31706 - Remove our mostly unused -- and broken -- hex_encode()
31707 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31708 for pointing out this bug.)
31709 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31710 fewer problems with people using the wrong key.
31711 - Change the default exit policy to reject the default edonkey,
31712 kazaa, gnutella ports.
31713 - Add replace_file() to util.[ch] to handle win32's rename().
31715 o Changes from 0.0.8preX:
31716 - Fix two bugs in saving onion keys to disk when rotating, so
31717 hopefully we'll get fewer people using old onion keys.
31718 - Fix an assert error that was making SocksPolicy not work.
31719 - Be willing to expire routers that have an open dirport -- it's
31720 just the authoritative dirservers we want to not forget.
31721 - Reject tor-resolve requests for .onion addresses early, so we
31722 don't build a whole rendezvous circuit and then fail.
31723 - When you're warning a server that he's unverified, don't cry
31724 wolf unpredictably.
31725 - Fix a race condition: don't try to extend onto a connection
31726 that's still handshaking.
31727 - For servers in clique mode, require the conn to be open before
31728 you'll choose it for your path.
31729 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31730 end relay cell, etc.
31731 - Measure bandwidth capacity over the last 24 hours, not just 12
31732 - Bugfix: authoritative dirservers were making and signing a new
31733 directory for each client, rather than reusing the cached one.
31736 Changes in version 0.0.8pre2 - 2004-08-04
31737 o Changes from 0.0.7.2:
31739 - Check directory signature _before_ you decide whether you're
31740 you're running an obsolete version and should exit.
31741 - Check directory signature _before_ you parse the running-routers
31742 list to decide who's running or verified.
31743 - Bugfixes and features:
31744 - Check return value of fclose while writing to disk, so we don't
31745 end up with broken files when servers run out of disk space.
31746 - Log a warning if the user uses an unsafe socks variant, so people
31747 are more likely to learn about privoxy or socat.
31748 - Dirservers now include RFC1123-style dates in the HTTP headers,
31749 which one day we will use to better detect clock skew.
31751 o Changes from 0.0.8pre1:
31752 - Make it compile without warnings again on win32.
31753 - Log a warning if you're running an unverified server, to let you
31754 know you might want to get it verified.
31755 - Only pick a default nickname if you plan to be a server.
31758 Changes in version 0.0.8pre1 - 2004-07-23
31760 - Made our unit tests compile again on OpenBSD 3.5, and tor
31761 itself compile again on OpenBSD on a sparc64.
31762 - We were neglecting milliseconds when logging on win32, so
31763 everything appeared to happen at the beginning of each second.
31765 o Protocol changes:
31766 - 'Extend' relay cell payloads now include the digest of the
31767 intended next hop's identity key. Now we can verify that we're
31768 extending to the right router, and also extend to routers we
31769 hadn't heard of before.
31772 - Tor nodes can now act as relays (with an advertised ORPort)
31773 without being manually verified by the dirserver operators.
31774 - Uploaded descriptors of unverified routers are now accepted
31775 by the dirservers, and included in the directory.
31776 - Verified routers are listed by nickname in the running-routers
31777 list; unverified routers are listed as "$<fingerprint>".
31778 - We now use hash-of-identity-key in most places rather than
31779 nickname or addr:port, for improved security/flexibility.
31780 - To avoid Sybil attacks, paths still use only verified servers.
31781 But now we have a chance to play around with hybrid approaches.
31782 - Nodes track bandwidth usage to estimate capacity (not used yet).
31783 - ClientOnly option for nodes that never want to become servers.
31784 - Directory caching.
31785 - "AuthoritativeDir 1" option for the official dirservers.
31786 - Now other nodes (clients and servers) will cache the latest
31787 directory they've pulled down.
31788 - They can enable their DirPort to serve it to others.
31789 - Clients will pull down a directory from any node with an open
31790 DirPort, and check the signature/timestamp correctly.
31791 - Authoritative dirservers now fetch directories from other
31792 authdirservers, to stay better synced.
31793 - Running-routers list tells who's down also, along with noting
31794 if they're verified (listed by nickname) or unverified (listed
31796 - Allow dirservers to serve running-router list separately.
31797 This isn't used yet.
31798 - ORs connect-on-demand to other ORs
31799 - If you get an extend cell to an OR you're not connected to,
31800 connect, handshake, and forward the create cell.
31801 - The authoritative dirservers stay connected to everybody,
31802 and everybody stays connected to 0.0.7 servers, but otherwise
31803 clients/servers expire unused connections after 5 minutes.
31804 - When servers get a sigint, they delay 30 seconds (refusing new
31805 connections) then exit. A second sigint causes immediate exit.
31806 - File and name management:
31807 - Look for .torrc if no CONFDIR "torrc" is found.
31808 - If no datadir is defined, then choose, make, and secure ~/.tor
31810 - If torrc not found, exitpolicy reject *:*.
31811 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
31812 - If no nickname is defined, derive default from hostname.
31813 - Rename secret key files, e.g. identity.key -> secret_id_key,
31814 to discourage people from mailing their identity key to tor-ops.
31815 - Refuse to build a circuit before the directory has arrived --
31816 it won't work anyway, since you won't know the right onion keys
31818 - Try other dirservers immediately if the one you try is down. This
31819 should tolerate down dirservers better now.
31820 - Parse tor version numbers so we can do an is-newer-than check
31821 rather than an is-in-the-list check.
31822 - New socks command 'resolve', to let us shim gethostbyname()
31824 - A 'tor_resolve' script to access the socks resolve functionality.
31825 - A new socks-extensions.txt doc file to describe our
31826 interpretation and extensions to the socks protocols.
31827 - Add a ContactInfo option, which gets published in descriptor.
31828 - Publish OR uptime in descriptor (and thus in directory) too.
31829 - Write tor version at the top of each log file
31830 - New docs in the tarball:
31832 - Document that you should proxy your SSL traffic too.
31835 Changes in version 0.0.7.2 - 2004-07-07
31836 o A better fix for the 0.0.0.0 problem, that will hopefully
31837 eliminate the remaining related assertion failures.
31840 Changes in version 0.0.7.1 - 2004-07-04
31841 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
31842 since internally we use 0.0.0.0 to signify "not yet resolved".
31845 Changes in version 0.0.7 - 2004-06-07
31846 o Updated the man page to reflect the new features.
31849 Changes in version 0.0.7rc2 - 2004-06-06
31850 o Changes from 0.0.7rc1:
31851 - Make it build on Win32 again.
31852 o Changes from 0.0.6.2:
31853 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
31857 Changes in version 0.0.7rc1 - 2004-06-02
31859 - On sighup, we were adding another log without removing the first
31860 one. So log messages would get duplicated n times for n sighups.
31861 - Several cases of using a connection after we'd freed it. The
31862 problem was that connections that are pending resolve are in both
31863 the pending_resolve tree, and also the circuit's resolving_streams
31864 list. When you want to remove one, you must remove it from both.
31865 - Fix a double-mark-for-close where an end cell arrived for a
31866 resolving stream, and then the resolve failed.
31867 - Check directory signatures based on name of signer, not on whom
31868 we got the directory from. This will let us cache directories more
31871 - Crank up some of our constants to handle more users.
31874 Changes in version 0.0.7pre1 - 2004-06-02
31875 o Fixes for crashes and other obnoxious bugs:
31876 - Fix an epipe bug: sometimes when directory connections failed
31877 to connect, we would give them a chance to flush before closing
31879 - When we detached from a circuit because of resolvefailed, we
31880 would immediately try the same circuit twice more, and then
31881 give up on the resolve thinking we'd tried three different
31883 - Limit the number of intro circuits we'll attempt to build for a
31884 hidden service per 15-minute period.
31885 - Check recommended-software string *early*, before actually parsing
31886 the directory. Thus we can detect an obsolete version and exit,
31887 even if the new directory format doesn't parse.
31888 o Fixes for security bugs:
31889 - Remember which nodes are dirservers when you startup, and if a
31890 random OR enables his dirport, don't automatically assume he's
31891 a trusted dirserver.
31893 - Directory connections were asking the wrong poll socket to
31894 start writing, and not asking themselves to start writing.
31895 - When we detached from a circuit because we sent a begin but
31896 didn't get a connected, we would use it again the first time;
31897 but after that we would correctly switch to a different one.
31898 - Stop warning when the first onion decrypt attempt fails; they
31899 will sometimes legitimately fail now that we rotate keys.
31900 - Override unaligned-access-ok check when $host_cpu is ia64 or
31901 arm. Apparently they allow it but the kernel whines.
31902 - Dirservers try to reconnect periodically too, in case connections
31904 - Fix some memory leaks in directory servers.
31905 - Allow backslash in Win32 filenames.
31906 - Made Tor build complain-free on FreeBSD, hopefully without
31907 breaking other BSD builds. We'll see.
31909 - Doxygen markup on all functions and global variables.
31910 - Make directory functions update routerlist, not replace it. So
31911 now directory disagreements are not so critical a problem.
31912 - Remove the upper limit on number of descriptors in a dirserver's
31913 directory (not that we were anywhere close).
31914 - Allow multiple logfiles at different severity ranges.
31915 - Allow *BindAddress to specify ":port" rather than setting *Port
31916 separately. Allow multiple instances of each BindAddress config
31917 option, so you can bind to multiple interfaces if you want.
31918 - Allow multiple exit policy lines, which are processed in order.
31919 Now we don't need that huge line with all the commas in it.
31920 - Enable accept/reject policies on SOCKS connections, so you can bind
31921 to 0.0.0.0 but still control who can use your OP.
31924 Changes in version 0.0.6.2 - 2004-05-16
31925 o Our integrity-checking digest was checking only the most recent cell,
31926 not the previous cells like we'd thought.
31927 Thanks to Stefan Mark for finding the flaw!
31930 Changes in version 0.0.6.1 - 2004-05-06
31931 o Fix two bugs in our AES counter-mode implementation (this affected
31932 onion-level stream encryption, but not TLS-level). It turns
31933 out we were doing something much more akin to a 16-character
31934 polyalphabetic cipher. Oops.
31935 Thanks to Stefan Mark for finding the flaw!
31936 o Retire moria3 as a directory server, and add tor26 as a directory
31940 Changes in version 0.0.6 - 2004-05-02
31941 [version bump only]
31944 Changes in version 0.0.6rc4 - 2004-05-01
31945 o Update the built-in dirservers list to use the new directory format
31946 o Fix a rare seg fault: if a node offering a hidden service attempts
31947 to build a circuit to Alice's rendezvous point and fails before it
31948 reaches the last hop, it retries with a different circuit, but
31950 o Handle windows socket errors correctly.
31953 Changes in version 0.0.6rc3 - 2004-04-28
31954 o Don't expire non-general excess circuits (if we had enough
31955 circuits open, we were expiring rendezvous circuits -- even
31956 when they had a stream attached. oops.)
31957 o Fetch randomness from /dev/urandom better (not via fopen/fread)
31958 o Better debugging for tls errors
31959 o Some versions of openssl have an SSL_pending function that erroneously
31960 returns bytes when there is a non-application record pending.
31961 o Set Content-Type on the directory and hidserv descriptor.
31962 o Remove IVs from cipher code, since AES-ctr has none.
31963 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
31964 o We were using an array of length zero in a few places.
31965 o win32's gethostbyname can't resolve an IP to an IP.
31966 o win32's close can't close a socket.
31969 Changes in version 0.0.6rc2 - 2004-04-26
31970 o Fix a bug where we were closing tls connections intermittently.
31971 It turns out openssl keeps its errors around -- so if an error
31972 happens, and you don't ask about it, and then another openssl
31973 operation happens and succeeds, and you ask if there was an error,
31974 it tells you about the first error. Fun fun.
31975 o Fix a bug that's been lurking since 27 may 03 (!)
31976 When passing back a destroy cell, we would use the wrong circ id.
31977 'Mostly harmless', but still worth fixing.
31978 o Since we don't support truncateds much, don't bother sending them;
31979 just close the circ.
31980 o check for <machine/limits.h> so we build on NetBSD again (I hope).
31981 o don't crash if a conn that sent a begin has suddenly lost its circuit
31982 (this was quite rare).
31985 Changes in version 0.0.6rc1 - 2004-04-25
31986 o We now rotate link (tls context) keys and onion keys.
31987 o CREATE cells now include oaep padding, so you can tell
31988 if you decrypted them correctly.
31989 o Add bandwidthburst to server descriptor.
31990 o Directories now say which dirserver signed them.
31991 o Use a tor_assert macro that logs failed assertions too.
31994 Changes in version 0.0.6pre5 - 2004-04-18
31995 o changes from 0.0.6pre4:
31996 - make tor build on broken freebsd 5.2 installs
31997 - fix a failed assert when you try an intro point, get a nack, and try
31998 a second one and it works.
31999 - when alice uses a port that the hidden service doesn't accept,
32000 it now sends back an end cell (denied by exit policy). otherwise
32001 alice would just have to wait to time out.
32002 - fix another rare bug: when we had tried all the intro
32003 points for a hidden service, we fetched the descriptor
32004 again, but we left our introcirc thinking it had already
32005 sent an intro, so it kept waiting for a response...
32006 - bugfix: when you sleep your hidden-service laptop, as soon
32007 as it wakes up it tries to upload a service descriptor, but
32008 socketpair fails for some reason (localhost not up yet?).
32009 now we simply give up on that upload, and we'll try again later.
32010 i'd still like to find the bug though.
32011 - if an intro circ waiting for an ack dies before getting one, then
32013 - we were reusing stale service descriptors and refetching usable
32017 Changes in version 0.0.6pre4 - 2004-04-14
32018 o changes from 0.0.6pre3:
32019 - when bob fails to connect to the rendezvous point, and his
32020 circ didn't fail because of the rendezvous point itself, then
32021 he retries a couple of times
32022 - we expire introduction and rendezvous circs more thoroughly
32023 (sometimes they were hanging around forever)
32024 - we expire unattached rendezvous streams that have been around
32025 too long (they were sticking around forever).
32026 - fix a measly fencepost error that was crashing everybody with
32030 Changes in version 0.0.6pre3 - 2004-04-14
32031 o changes from 0.0.6pre2:
32032 - make hup work again
32033 - fix some memory leaks for dirservers
32034 - allow more skew in rendezvous descriptor timestamps, to help
32035 handle people like blanu who don't know what time it is
32036 - normal circs are 3 hops, but some rend/intro circs are 4, if
32037 the initiator doesn't get to choose the last hop
32038 - send acks for introductions, so alice can know whether to try
32040 - bob publishes intro points more correctly
32041 o changes from 0.0.5:
32042 - fix an assert trigger that's been plaguing us since the days
32043 of 0.0.2prexx (thanks weasel!)
32044 - retry stream correctly when we fail to connect because of
32045 exit-policy-reject (should try another) or can't-resolve-address
32046 (also should try another, because dns on random internet servers
32048 - when we hup a dirserver and we've *removed* a server from the
32049 approved-routers list, now we remove that server from the
32050 in-memory directories too
32053 Changes in version 0.0.6pre2 - 2004-04-08
32054 o We fixed our base32 implementation. Now it works on all architectures.
32057 Changes in version 0.0.6pre1 - 2004-04-08
32059 - Hidden services and rendezvous points are implemented. Go to
32060 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
32061 hidden services. (This only works via a socks4a proxy such as
32062 Privoxy, and currently it's quite slow.)
32065 Changes in version 0.0.5 - 2004-03-30
32066 [version bump only]
32069 Changes in version 0.0.5rc3 - 2004-03-29
32070 o Install torrc as torrc.sample -- we no longer clobber your
32072 o Re-enable recommendedversion checking (we broke it in rc2, oops)
32073 o Add in a 'notice' log level for things the operator should hear
32074 but that aren't warnings
32077 Changes in version 0.0.5rc2 - 2004-03-29
32078 o Hold socks connection open until reply is flushed (if possible)
32079 o Make exit nodes resolve IPs to IPs immediately, rather than asking
32080 the dns farm to do it.
32081 o Fix c99 aliasing warnings in rephist.c
32082 o Don't include server descriptors that are older than 24 hours in the
32084 o Give socks 'reject' replies their whole 15s to attempt to flush,
32085 rather than seeing the 60s timeout and assuming the flush had failed.
32086 o Clean automake droppings from the cvs repository
32089 Changes in version 0.0.5rc1 - 2004-03-28
32090 o Fix mangled-state bug in directory fetching (was causing sigpipes).
32091 o Only build circuits after we've fetched the directory: clients were
32092 using only the directory servers before they'd fetched a directory.
32093 This also means longer startup time; so it goes.
32094 o Fix an assert trigger where an OP would fail to handshake, and we'd
32095 expect it to have a nickname.
32096 o Work around a tsocks bug: do a socks reject when AP connection dies
32097 early, else tsocks goes into an infinite loop.
32100 Changes in version 0.0.4 - 2004-03-26
32101 o When connecting to a dirserver or OR and the network is down,
32105 Changes in version 0.0.3 - 2004-03-26
32106 o Warn and fail if server chose a nickname with illegal characters
32107 o Port to Solaris and Sparc:
32108 - include missing header fcntl.h
32109 - have autoconf find -lsocket -lnsl automatically
32110 - deal with hardware word alignment
32111 - make uname() work (solaris has a different return convention)
32112 - switch from using signal() to sigaction()
32113 o Preliminary work on reputation system:
32114 - Keep statistics on success/fail of connect attempts; they're published
32115 by kill -USR1 currently.
32116 - Add a RunTesting option to try to learn link state by creating test
32117 circuits, even when SocksPort is off.
32118 - Remove unused open circuits when there are too many.
32121 Changes in version 0.0.2 - 2004-03-19
32122 - Include strlcpy and strlcat for safer string ops
32123 - define INADDR_NONE so we compile (but still not run) on solaris
32126 Changes in version 0.0.2pre27 - 2004-03-14
32128 - Allow internal tor networks (we were rejecting internal IPs,
32129 now we allow them if they're set explicitly).
32130 - And fix a few endian issues.
32133 Changes in version 0.0.2pre26 - 2004-03-14
32135 - If a stream times out after 15s without a connected cell, don't
32136 try that circuit again: try a new one.
32137 - Retry streams at most 4 times. Then give up.
32138 - When a dirserver gets a descriptor from an unknown router, it
32139 logs its fingerprint (so the dirserver operator can choose to
32140 accept it even without mail from the server operator).
32141 - Inform unapproved servers when we reject their descriptors.
32142 - Make tor build on Windows again. It works as a client, who knows
32144 - Clearer instructions in the torrc for how to set up a server.
32145 - Be more efficient about reading fd's when our global token bucket
32146 (used for rate limiting) becomes empty.
32148 - Stop asserting that computers always go forward in time. It's
32150 - When we sent a cell (e.g. destroy) and then marked an OR connection
32151 expired, we might close it before finishing a flush if the other
32152 side isn't reading right then.
32153 - Don't allow dirservers to start if they haven't defined
32154 RecommendedVersions
32155 - We were caching transient dns failures. Oops.
32156 - Prevent servers from publishing an internal IP as their address.
32157 - Address a strcat vulnerability in circuit.c
32160 Changes in version 0.0.2pre25 - 2004-03-04
32162 - Put the OR's IP in its router descriptor, not its fqdn. That way
32163 we'll stop being stalled by gethostbyname for nodes with flaky dns,
32166 - If the user typed in an address that didn't resolve, the server
32170 Changes in version 0.0.2pre24 - 2004-03-03
32172 - Fix an assertion failure in dns.c, where we were trying to dequeue
32173 a pending dns resolve even if it wasn't pending
32174 - Fix a spurious socks5 warning about still trying to write after the
32175 connection is finished.
32176 - Hold certain marked_for_close connections open until they're finished
32177 flushing, rather than losing bytes by closing them too early.
32178 - Correctly report the reason for ending a stream
32179 - Remove some duplicate calls to connection_mark_for_close
32180 - Put switch_id and start_daemon earlier in the boot sequence, so it
32181 will actually try to chdir() to options.DataDirectory
32182 - Make 'make test' exit(1) if a test fails; fix some unit tests
32183 - Make tor fail when you use a config option it doesn't know about,
32184 rather than warn and continue.
32185 - Make --version work
32186 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
32189 Changes in version 0.0.2pre23 - 2004-02-29
32191 - Print a statement when the first circ is finished, so the user
32192 knows it's working.
32193 - If a relay cell is unrecognized at the end of the circuit,
32194 send back a destroy. (So attacks to mutate cells are more
32196 - New config option 'excludenodes' to avoid certain nodes for circuits.
32197 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
32198 so you can collect coredumps there.
32200 - Fix a bug in tls flushing where sometimes data got wedged and
32201 didn't flush until more data got sent. Hopefully this bug was
32202 a big factor in the random delays we were seeing.
32203 - Make 'connected' cells include the resolved IP, so the client
32204 dns cache actually gets populated.
32205 - Disallow changing from ORPort=0 to ORPort>0 on hup.
32206 - When we time-out on a stream and detach from the circuit, send an
32207 end cell down it first.
32208 - Only warn about an unknown router (in exitnodes, entrynodes,
32209 excludenodes) after we've fetched a directory.
32212 Changes in version 0.0.2pre22 - 2004-02-26
32214 - Servers publish less revealing uname information in descriptors.
32215 - More memory tracking and assertions, to crash more usefully when
32217 - If the default torrc isn't there, just use some default defaults.
32218 Plus provide an internal dirservers file if they don't have one.
32219 - When the user tries to use Tor as an http proxy, give them an http
32220 501 failure explaining that we're a socks proxy.
32221 - Dump a new router.desc on hup, to help confused people who change
32222 their exit policies and then wonder why router.desc doesn't reflect
32224 - Clean up the generic tor.sh init script that we ship with.
32226 - If the exit stream is pending on the resolve, and a destroy arrives,
32227 then the stream wasn't getting removed from the pending list. I
32228 think this was the one causing recent server crashes.
32229 - Use a more robust poll on OSX 10.3, since their poll is flaky.
32230 - When it couldn't resolve any dirservers, it was useless from then on.
32231 Now it reloads the RouterFile (or default dirservers) if it has no
32233 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
32234 many users don't even *have* a /usr/local/sbin/.
32237 Changes in version 0.0.2pre21 - 2004-02-18
32239 - There's a ChangeLog file that actually reflects the changelog.
32240 - There's a 'torify' wrapper script, with an accompanying
32241 tor-tsocks.conf, that simplifies the process of using tsocks for
32242 tor. It even has a man page.
32243 - The tor binary gets installed to sbin rather than bin now.
32244 - Retry streams where the connected cell hasn't arrived in 15 seconds
32245 - Clean up exit policy handling -- get the default out of the torrc,
32246 so we can update it without forcing each server operator to fix
32248 - Allow imaps and pop3s in default exit policy
32250 - Prevent picking middleman nodes as the last node in the circuit
32253 Changes in version 0.0.2pre20 - 2004-01-30
32255 - We now have a deb package, and it's in debian unstable. Go to
32256 it, apt-getters. :)
32257 - I've split the TotalBandwidth option into BandwidthRate (how many
32258 bytes per second you want to allow, long-term) and
32259 BandwidthBurst (how many bytes you will allow at once before the cap
32260 kicks in). This better token bucket approach lets you, say, set
32261 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
32262 performance while not exceeding your monthly bandwidth quota.
32263 - Push out a tls record's worth of data once you've got it, rather
32264 than waiting until you've read everything waiting to be read. This
32265 may improve performance by pipelining better. We'll see.
32266 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
32267 from failed circuits (if they haven't been connected yet) and attach
32269 - Expire old streams that haven't managed to connect. Some day we'll
32270 have them reattach to new circuits instead.
32273 - Fix several memory leaks that were causing servers to become bloated
32275 - Fix a few very rare assert triggers. A few more remain.
32276 - Setuid to User _before_ complaining about running as root.
32279 Changes in version 0.0.2pre19 - 2004-01-07
32281 - Fix deadlock condition in dns farm. We were telling a child to die by
32282 closing the parent's file descriptor to him. But newer children were
32283 inheriting the open file descriptor from the parent, and since they
32284 weren't closing it, the socket never closed, so the child never read
32285 eof, so he never knew to exit. Similarly, dns workers were holding
32286 open other sockets, leading to all sorts of chaos.
32287 - New cleaner daemon() code for forking and backgrounding.
32288 - If you log to a file, it now prints an entry at the top of the
32289 logfile so you know it's working.
32290 - The onionskin challenge length was 30 bytes longer than necessary.
32291 - Started to patch up the spec so it's not quite so out of date.
32294 Changes in version 0.0.2pre18 - 2004-01-02
32296 - Fix endian issues with the 'integrity' field in the relay header.
32297 - Fix a potential bug where connections in state
32298 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
32301 Changes in version 0.0.2pre17 - 2003-12-30
32303 - Made --debuglogfile (or any second log file, actually) work.
32304 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
32305 adversary could force us into an infinite loop.
32308 - Each onionskin handshake now includes a hash of the computed key,
32309 to prove the server's identity and help perfect forward secrecy.
32310 - Changed cell size from 256 to 512 bytes (working toward compatibility
32312 - Changed cell length to 2 bytes, and moved it to the relay header.
32313 - Implemented end-to-end integrity checking for the payloads of
32315 - Separated streamid from 'recognized' (otherwise circuits will get
32316 messed up when we try to have streams exit from the middle). We
32317 use the integrity-checking to confirm that a cell is addressed to
32319 - Randomize the initial circid and streamid values, so an adversary who
32320 breaks into a node can't learn how many circuits or streams have
32324 Changes in version 0.0.2pre16 - 2003-12-14
32326 - Fixed a bug that made HUP trigger an assert
32327 - Fixed a bug where a circuit that immediately failed wasn't being
32328 counted as a failed circuit in counting retries.
32331 - Now we close the circuit when we get a truncated cell: otherwise we're
32332 open to an anonymity attack where a bad node in the path truncates
32333 the circuit and then we open streams at him.
32334 - Add port ranges to exit policies
32335 - Add a conservative default exit policy
32336 - Warn if you're running tor as root
32337 - on HUP, retry OR connections and close/rebind listeners
32338 - options.EntryNodes: try these nodes first when picking the first node
32339 - options.ExitNodes: if your best choices happen to include any of
32340 your preferred exit nodes, you choose among just those preferred
32342 - options.ExcludedNodes: nodes that are never picked in path building
32345 Changes in version 0.0.2pre15 - 2003-12-03
32346 o Robustness and bugfixes:
32347 - Sometimes clients would cache incorrect DNS resolves, which would
32348 really screw things up.
32349 - An OP that goes offline would slowly leak all its sockets and stop
32351 - A wide variety of bugfixes in exit node selection, exit policy
32352 handling, and processing pending streams when a new circuit is
32354 - Pick nodes for a path only from those the directory says are up
32355 - Choose randomly from all running dirservers, not always the first one
32356 - Increase allowed http header size for directory fetch.
32357 - Stop writing to stderr (if we're daemonized it will be closed).
32358 - Enable -g always, so cores will be more useful to me.
32359 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
32362 - Wrote a man page. It lists commonly used options.
32365 - Change default loglevel to warn.
32366 - Make PidFile default to null rather than littering in your CWD.
32367 - OnionRouter config option is now obsolete. Instead it just checks
32369 - Moved to a single unified torrc file for both clients and servers.
32372 Changes in version 0.0.2pre14 - 2003-11-29
32373 o Robustness and bugfixes:
32374 - Force the admin to make the DataDirectory himself
32375 - to get ownership/permissions right
32376 - so clients no longer make a DataDirectory and then never use it
32377 - fix bug where a client who was offline for 45 minutes would never
32378 pull down a directory again
32379 - fix (or at least hide really well) the dns assert bug that was
32380 causing server crashes
32381 - warnings and improved robustness wrt clockskew for certs
32382 - use the native daemon(3) to daemonize, when available
32383 - exit if bind() fails
32384 - exit if neither socksport nor orport is defined
32385 - include our own tor_timegm (Win32 doesn't have its own)
32386 - bugfix for win32 with lots of connections
32387 - fix minor bias in PRNG
32388 - make dirserver more robust to corrupt cached directory
32391 - Wrote the design document (woo)
32393 o Circuit building and exit policies:
32394 - Circuits no longer try to use nodes that the directory has told them
32396 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
32397 bitcounts (18.0.0.0/8).
32398 - Make AP connections standby for a circuit if no suitable circuit
32399 exists, rather than failing
32400 - Circuits choose exit node based on addr/port, exit policies, and
32401 which AP connections are standing by
32402 - Bump min pathlen from 2 to 3
32403 - Relay end cells have a payload to describe why the stream ended.
32404 - If the stream failed because of exit policy, try again with a new
32406 - Clients have a dns cache to remember resolved addresses.
32407 - Notice more quickly when we have no working circuits
32410 - APPort is now called SocksPort
32411 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
32413 - RecommendedVersions is now a config variable rather than
32414 hardcoded (for dirservers)
32415 - Reloads config on HUP
32416 - Usage info on -h or --help
32417 - If you set User and Group config vars, it'll setu/gid to them.
32420 Changes in version 0.0.2pre13 - 2003-10-19
32421 o General stability:
32422 - SSL_write no longer fails when it returns WANTWRITE and the number
32423 of bytes in the buf has changed by the next SSL_write call.
32424 - Fix segfault fetching directory when network is down
32425 - Fix a variety of minor memory leaks
32426 - Dirservers reload the fingerprints file on HUP, so I don't have
32427 to take down the network when I approve a new router
32428 - Default server config file has explicit Address line to specify fqdn
32431 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
32432 - Make listener connections not ever alloc bufs
32434 o Autoconf improvements:
32435 - don't clobber an external CFLAGS in ./configure
32436 - Make install now works
32437 - create var/lib/tor on make install
32438 - autocreate a tor.sh initscript to help distribs
32439 - autocreate the torrc and sample-server-torrc with correct paths
32441 o Log files and Daemonizing now work:
32442 - If --DebugLogFile is specified, log to it at -l debug
32443 - If --LogFile is specified, use it instead of commandline
32444 - If --RunAsDaemon is set, tor forks and backgrounds on startup