1 Changes in version 0.4.1.1-alpha - 2019-05-22
2 This is the first alpha in the 0.4.1.x series. It introduces
3 lightweight circuit padding to make some onion-service circuits harder
4 to distinguish, includes a new "authenticated SENDME" feature to make
5 certain denial-of-service attacks more difficult, and improves
6 performance in several areas.
8 o Major features (circuit padding):
9 - Onion service clients now add padding cells at the start of their
10 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
11 look more like general purpose Exit traffic. The overhead for this
12 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
13 extra upstream cell and 10 downstream cells for INTRODUCE
14 circuits. This feature is only enabled when also supported by the
15 circuit's middle node. (Clients may specify fixed middle nodes
16 with the MiddleNodes option, and may force-disable this feature
17 with the CircuitPadding torrc.) Closes ticket 28634.
19 o Major features (code organization):
20 - Tor now includes a generic publish-subscribe message-passing
21 subsystem that we can use to organize intermodule dependencies. We
22 hope to use this to reduce dependencies between modules that don't
23 need to be related, and to generally simplify our codebase. Closes
26 o Major features (controller protocol):
27 - Controller commands are now parsed using a generalized parsing
28 subsystem. Previously, each controller command was responsible for
29 parsing its own input, which led to strange inconsistencies.
32 o Major features (flow control):
33 - Implement authenticated SENDMEs as detailed in proposal 289. A
34 SENDME cell now includes the digest of the traffic that it
35 acknowledges, so that once an end point receives the SENDME, it
36 can confirm the other side's knowledge of the previous cells that
37 were sent, and prevent certain types of denial-of-service attacks.
38 This behavior is controlled by two new consensus parameters: see
39 the proposal for more details. Fixes ticket 26288.
41 o Major features (performance):
42 - Our node selection algorithm now excludes nodes in linear time.
43 Previously, the algorithm was quadratic, which could slow down
44 heavily used onion services. Closes ticket 30307.
46 o Major features (performance, RNG):
47 - Tor now constructs a fast secure pseudorandom number generator for
48 each thread, to use when performance is critical. This PRNG is
49 based on AES-CTR, using a buffering construction similar to
50 libottery and the (newer) OpenBSD arc4random() code. It
51 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
52 small outputs. Although we believe it to be cryptographically
53 strong, we are only using it when necessary for performance.
54 Implements tickets 29023 and 29536.
56 o Major bugfixes (onion service v3):
57 - Fix an unreachable bug in which an introduction point could try to
58 send an INTRODUCE_ACK with a status code that Trunnel would refuse
59 to encode, leading the relay to assert(). We've consolidated the
60 ABI values into Trunnel now. Fixes bug 30454; bugfix
62 - Clients can now handle unknown status codes from INTRODUCE_ACK
63 cells. (The NACK behavior will stay the same.) This will allow us
64 to extend status codes in the future without breaking the normal
65 client behavior. Fixes another part of bug 30454; bugfix
68 o Minor features (circuit padding):
69 - We now use a fast PRNG when scheduling circuit padding. Part of
71 - Allow the padding machine designer to pick the edges of their
72 histogram instead of trying to compute them automatically using an
73 exponential formula. Resolves some undefined behavior in the case
74 of small histograms and allows greater flexibility on machine
75 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
76 - Allow circuit padding machines to hold a circuit open until they
77 are done padding it. Closes ticket 28780.
79 o Minor features (compile-time modules):
80 - Add a "--list-modules" command to print a list of which compile-
81 time modules are enabled. Closes ticket 30452.
83 o Minor features (continuous integration):
84 - Remove sudo configuration lines from .travis.yml as they are no
85 longer needed with current Travis build environment. Resolves
87 - In Travis, show stem's tor log after failure. Closes ticket 30234.
89 o Minor features (controller):
90 - Add onion service version 3 support to the HSFETCH command.
91 Previously, only version 2 onion services were supported. Closes
92 ticket 25417. Patch by Neel Chauhan.
94 o Minor features (debugging):
95 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
96 logging of additional information during assert failure. Now we
97 can use format strings to include information for trouble
98 shooting. Resolves ticket 29662.
100 o Minor features (defense in depth):
101 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
102 case a bug causes them to be used later. Closes ticket 30176.
103 Patch from Tobias Stoeckmann.
104 - Tor now uses a cryptographically strong PRNG even for decisions
105 that we do not believe are security-sensitive. Previously, for
106 performance reasons, we had used a trivially predictable linear
107 congruential generator algorithm for certain load-balancing and
108 statistical sampling decisions. Now we use our fast RNG in those
109 cases. Closes ticket 29542.
111 o Minor features (developer tools):
112 - Tor's "practracker" test script now checks for files and functions
113 that seem too long and complicated. Existing overlong functions
114 and files are accepted for now, but should eventually be
115 refactored. Closes ticket 29221.
116 - Add some scripts used for git maintenance to scripts/git. Closes
118 - Call practracker from pre-push and pre-commit git hooks to let
119 developers know if they made any code style violations. Closes
121 - Add a script to check that each header has a well-formed and
122 unique guard macro. Closes ticket 29756.
124 o Minor features (geoip):
125 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
126 Country database. Closes ticket 30522.
128 o Minor features (HTTP tunnel):
129 - Return an informative web page when the HTTPTunnelPort is used as
130 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
132 o Minor features (IPv6, v3 onion services):
133 - Make v3 onion services put IPv6 addresses in service descriptors.
134 Before this change, service descriptors only contained IPv4
135 addresses. Implements 26992.
137 o Minor features (modularity):
138 - The "--disable-module-dirauth" compile-time option now disables
139 even more dirauth-only code. Closes ticket 30345.
141 o Minor features (performance):
142 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
143 1.1.1 and later), since they tend to be faster than tiny-keccak.
146 o Minor features (testing):
147 - Tor's unit test code now contains helper functions to replace the
148 PRNG with a deterministic or reproducible version for testing.
149 Previously, various tests implemented this in various ways.
150 Implements ticket 29732.
151 - We now have a script, cov-test-determinism.sh, to identify places
152 where our unit test coverage has become nondeterministic. Closes
154 - Check that representative subsets of values of `int` and `unsigned
155 int` can be represented by `void *`. Resolves issue 29537.
157 o Minor bugfixes (bridge authority):
158 - Bridge authorities now set bridges as running or non-running when
159 about to dump their status to a file. Previously, they set bridges
160 as running in response to a GETINFO command, but those shouldn't
161 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
162 Patch by Neel Chauhan.
164 o Minor bugfixes (channel padding statistics):
165 - Channel padding write totals and padding-enabled totals are now
166 counted properly in relay extrainfo descriptors. Fixes bug 29231;
167 bugfix on 0.3.1.1-alpha.
169 o Minor bugfixes (circuit padding):
170 - Add a "CircuitPadding" torrc option to disable circuit padding.
171 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
172 - Allow circuit padding machines to specify that they do not
173 contribute much overhead, and provide consensus flags and torrc
174 options to force clients to only use these low overhead machines.
175 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
176 - Provide a consensus parameter to fully disable circuit padding, to
177 be used in emergency network overload situations. Fixes bug 30173;
178 bugfix on 0.4.0.1-alpha.
179 - The circuit padding subsystem will no longer schedule padding if
180 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
181 - Inspect a circuit-level cell queue before sending padding, to
182 avoid sending padding while too much data is already queued. Fixes
183 bug 29204; bugfix on 0.4.0.1-alpha.
184 - Avoid calling monotime_absolute_usec() in circuit padding machines
185 that do not use token removal or circuit RTT estimation. Fixes bug
186 29085; bugfix on 0.4.0.1-alpha.
188 o Minor bugfixes (compilation, unusual configurations):
189 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
190 due to missing declarations of abort(), and prevent other such
191 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
193 o Minor bugfixes (controller protocol):
194 - Teach the controller parser to distinguish an object preceded by
195 an argument list from one without. Previously, it couldn't
196 distinguish an argument list from the first line of a multiline
197 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
199 o Minor bugfixes (directory authority, ipv6):
200 - Directory authorities with IPv6 support now always mark themselves
201 as reachable via IPv6. Fixes bug 24338; bugfix on 0.4.0.2-alpha.
202 Patch by Neel Chauhan.
204 o Minor bugfixes (documentation):
205 - Improve the documentation for using MapAddress with ".exit". Fixes
206 bug 30109; bugfix on 0.1.0.1-rc.
207 - Improve the monotonic time module and function documentation to
208 explain what "monotonic" actually means, and document some results
209 that have surprised people. Fixes bug 29640; bugfix
211 - Use proper formatting when providing an example on quoting options
212 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
214 o Minor bugfixes (logging):
215 - Do not log a warning when running with an OpenSSL version other
216 than the one Tor was compiled with, if the two versions should be
217 compatible. Previously, we would warn whenever the version was
218 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
219 - Warn operators when the MyFamily option is set but ContactInfo is
220 missing, as the latter should be set too. Fixes bug 25110; bugfix
223 o Minor bugfixes (memory leak):
224 - Avoid a minor memory leak that could occur on relays when failing
225 to create a "keys" directory. Fixes bug 30148; bugfix
228 o Minor bugfixes (onion services):
229 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
230 implemenation) when failing to load an onion service client
231 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
232 - When refusing to launch a controller's HSFETCH request because of
233 rate-limiting, respond to the controller with a new response,
234 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
235 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
237 - When relaunching a circuit to a rendezvous service, mark the
238 circuit as needing high-uptime routers as appropriate. Fixes bug
239 17357; bugfix on 0.4.0.2-alpha. Patch by Neel Chauhan.
240 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
241 (IPv6 support for v3 onion services is still incomplete: see
242 ticket 23493 for details.) Fixes bug 23588; bugfix on
243 0.3.2.1-alpha. Patch by Neel Chauhan.
245 o Minor bugfixes (onion services, performance):
246 - When building circuits to onion services, call tor_addr_parse()
247 less often. Previously, we called tor_addr_parse() in
248 circuit_is_acceptable() even if its output wasn't used. This
249 change should improve performance when building circuits. Fixes
250 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
252 o Minor bugfixes (performance):
253 - When checking whether a node is a bridge, use a fast check to make
254 sure that its identity is set. Previously, we used a constant-time
255 check, which is not necessary in this case. Fixes bug 30308;
256 bugfix on 0.3.5.1-alpha.
258 o Minor bugfixes (pluggable transports):
259 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
260 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
262 o Minor bugfixes (probability distributions):
263 - Refactor and improve parts of the probability distribution code
264 that made Coverity complain. Fixes bug 29805; bugfix
267 o Minor bugfixes (python):
268 - Stop assuming that /usr/bin/python3 exists. For scripts that work
269 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
270 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
272 o Minor bugfixes (relay):
273 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
274 is auto, act as if ExitRelay is 1. Previously, we would ignore
275 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
276 0.3.5.1-alpha. Patch by Neel Chauhan.
278 o Minor bugfixes (stats):
279 - When ExtraInfoStatistics is 0, stop including bandwidth usage
280 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
281 bridge statistics by country in extra-info documents. Fixes bug
282 29018; bugfix on 0.2.4.1-alpha.
284 o Minor bugfixes (testing):
285 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
286 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
287 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
288 - Fix some incorrect code in the v3 onion service unit tests. Fixes
289 bug 29243; bugfix on 0.3.2.1-alpha.
290 - In the "routerkeys/*" tests, check the return values of mkdir()
291 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
292 Found by Coverity as CID 1444254.
293 - Split test_utils_general() into several smaller test functions.
294 This makes it easier to perform resource deallocation on assert
295 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
296 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
298 o Minor bugfixes (tor-resolve):
299 - Fix a memory leak in tor-resolve that could happen if Tor gave it
300 a malformed SOCKS response. (Memory leaks in tor-resolve don't
301 actually matter, but it's good to fix them anyway.) Fixes bug
302 30151; bugfix on 0.4.0.1-alpha.
304 o Code simplification and refactoring:
305 - Abstract out the low-level formatting of replies on the control
306 port. Implements ticket 30007.
307 - Add several assertions in an attempt to fix some Coverity
308 warnings. Closes ticket 30149.
309 - Introduce a connection_dir_buf_add() helper function that checks
310 for compress_state of dir_connection_t and automatically writes a
311 string to directory connection with or without compression.
312 Resolves issue 28816.
313 - Make the base32_decode() API return the number of bytes written,
314 for consistency with base64_decode(). Closes ticket 28913.
315 - Move most relay-only periodic events out of mainloop.c into the
316 relay subsystem. Closes ticket 30414.
317 - Refactor and encapsulate parts of the codebase that manipulate
318 crypt_path_t objects. Resolves issue 30236.
319 - Refactor several places in our code that Coverity incorrectly
320 believed might have memory leaks. Closes ticket 30147.
321 - Remove redundant return values in crypto_format, and the
322 associated return value checks elsewhere in the code. Make the
323 implementations in crypto_format consistent, and remove redundant
324 code. Resolves ticket 29660.
325 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
326 it is not a constant-time function. Closes ticket 30309.
327 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
328 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
329 bugfix on 0.3.2.1-alpha.
330 - Simplify v3 onion service link specifier handling code. Fixes bug
331 23576; bugfix on 0.3.2.1-alpha.
332 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
333 code. Resolves ticket 29108.
334 - Split control.c into several submodules, in preparation for
335 distributing its current responsibilities throughout the codebase.
337 - Start to move responsibility for knowing about periodic events to
338 the appropriate subsystems, so that the mainloop doesn't need to
339 know all the periodic events in the rest of the codebase.
340 Implements tickets 30293 and 30294.
343 - Document how to find git commits and tags for bug fixes in
344 CodingStandards.md. Update some file documentation. Closes
348 - Remove the linux-tor-prio.sh script from contrib/operator-tools
349 directory. Resolves issue 29434.
350 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
351 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
354 o Code simplification and refactoring (shell scripts):
355 - Clean up many of our shell scripts to fix shellcheck warnings.
356 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
357 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
358 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
359 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
360 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
361 nagios-check-tor-authority-cert (ticket 29071),
362 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
363 (ticket 29060), test_key_expiration.sh (ticket 30002),
364 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
368 - In "make test-network-all", test IPv6-only v3 single onion
369 services, using the chutney network single-onion-v23-ipv6-md.
373 Changes in version 0.4.0.5 - 2019-05-02
374 This is the first stable release in the 0.4.0.x series. It contains
375 improvements for power management and bootstrap reporting, as well as
376 preliminary backend support for circuit padding to prevent some kinds
377 of traffic analysis. It also continues our work in refactoring Tor for
378 long-term maintainability.
380 Per our support policy, we will support the 0.4.0.x series for nine
381 months, or until three months after the release of a stable 0.4.1.x:
382 whichever is longer. If you need longer-term support, please stick
383 with 0.3.5.x, which will we plan to support until Feb 2022.
385 Below are the changes since 0.4.0.4-rc. For a complete list of changes
386 since 0.3.5.7, see the ReleaseNotes file.
388 o Minor features (continuous integration):
389 - In Travis, tell timelimit to use stem's backtrace signals, and
390 launch python directly from timelimit, so python receives the
391 signals from timelimit, rather than make. Closes ticket 30117.
393 o Minor features (diagnostic):
394 - Add more diagnostic log messages in an attempt to solve the issue
395 of NUL bytes appearing in a microdescriptor cache. Related to
398 o Minor features (testing):
399 - Use the approx_time() function when setting the "Expires" header
400 in directory replies, to make them more testable. Needed for
403 o Minor bugfixes (rust):
404 - Abort on panic in all build profiles, instead of potentially
405 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
407 o Minor bugfixes (shellcheck):
408 - Look for scripts in their correct locations during "make
409 shellcheck". Previously we had looked in the wrong place during
410 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
412 o Minor bugfixes (testing):
413 - Check the time in the "Expires" header using approx_time(). Fixes
414 bug 30001; bugfix on 0.4.0.4-rc.
416 o Minor bugfixes (UI):
417 - Lower log level of unlink() errors during bootstrap. Fixes bug
418 29930; bugfix on 0.4.0.1-alpha.
421 Changes in version 0.4.0.4-rc - 2019-04-11
422 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
423 several bugs from earlier versions, including some that had affected
424 stability, and one that prevented relays from working with NSS.
426 o Major bugfixes (NSS, relay):
427 - When running with NSS, disable TLS 1.2 ciphersuites that use
428 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
429 these ciphersuites don't work -- which caused relays to fail to
430 handshake with one another when these ciphersuites were enabled.
431 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
433 o Minor features (bandwidth authority):
434 - Make bandwidth authorities ignore relays that are reported in the
435 bandwidth file with the flag "vote=0". This change allows us to
436 report unmeasured relays for diagnostic reasons without including
437 their bandwidth in the bandwidth authorities' vote. Closes
439 - When a directory authority is using a bandwidth file to obtain the
440 bandwidth values that will be included in the next vote, serve
441 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
444 o Minor features (circuit padding):
445 - Stop warning about undefined behavior in the probability
446 distribution tests. Float division by zero may technically be
447 undefined behavior in C, but it's well defined in IEEE 754.
448 Partial backport of 29298. Closes ticket 29527; bugfix
451 o Minor features (continuous integration):
452 - On Travis Rust builds, cleanup Rust registry and refrain from
453 caching the "target/" directory to speed up builds. Resolves
456 o Minor features (dormant mode):
457 - Add a DormantCanceledByStartup option to tell Tor that it should
458 treat a startup event as cancelling any previous dormant state.
459 Integrators should use this option with caution: it should only be
460 used if Tor is being started because of something that the user
461 did, and not if Tor is being automatically started in the
462 background. Closes ticket 29357.
464 o Minor features (geoip):
465 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
466 Country database. Closes ticket 29992.
468 o Minor features (NSS, diagnostic):
469 - Try to log an error from NSS (if there is any) and a more useful
470 description of our situation if we are using NSS and a call to
471 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
473 o Minor bugfixes (security):
474 - Fix a potential double free bug when reading huge bandwidth files.
475 The issue is not exploitable in the current Tor network because
476 the vulnerable code is only reached when directory authorities
477 read bandwidth files, but bandwidth files come from a trusted
478 source (usually the authorities themselves). Furthermore, the
479 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
480 which are not used by any of the current authorities. Fixes bug
481 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
483 - Verify in more places that we are not about to create a buffer
484 with more than INT_MAX bytes, to avoid possible OOB access in the
485 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
486 fixed by Tobias Stoeckmann.
488 o Minor bugfix (continuous integration):
489 - Reset coverage state on disk after Travis CI has finished. This
490 should prevent future coverage merge errors from causing the test
491 suite for the "process" subsystem to fail. The process subsystem
492 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
494 - Terminate test-stem if it takes more than 9.5 minutes to run.
495 (Travis terminates the job after 10 minutes of no output.)
496 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
498 o Minor bugfixes (bootstrap reporting):
499 - During bootstrap reporting, correctly distinguish pluggable
500 transports from plain proxies. Fixes bug 28925; bugfix
503 o Minor bugfixes (C correctness):
504 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
505 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
508 o Minor bugfixes (circuitpadding testing):
509 - Minor tweaks to avoid rare test failures related to timers and
510 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
512 o Minor bugfixes (directory authorities):
513 - Actually include the bandwidth-file-digest line in directory
514 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
516 o Minor bugfixes (logging):
517 - On Windows, when errors cause us to reload a consensus from disk,
518 tell the user that we are retrying at log level "notice".
519 Previously we only logged this information at "info", which was
520 confusing because the errors themselves were logged at "warning".
521 Improves previous fix for 28614. Fixes bug 30004; bugfix
524 o Minor bugfixes (pluggable transports):
525 - Restore old behavior when it comes to discovering the path of a
526 given Pluggable Transport executable file. A change in
527 0.4.0.1-alpha had broken this behavior on paths containing a
528 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
530 o Minor bugfixes (testing):
531 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
532 recent test-network.sh to use new chutney features in CI. Fixes
533 bug 29703; bugfix on 0.2.9.1-alpha.
534 - Fix a test failure on Windows caused by an unexpected "BUG"
535 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
538 o Minor bugfixes (TLS protocol):
539 - When classifying a client's selection of TLS ciphers, if the
540 client ciphers are not yet available, do not cache the result.
541 Previously, we had cached the unavailability of the cipher list
542 and never looked again, which in turn led us to assume that the
543 client only supported the ancient V1 link protocol. This, in turn,
544 was causing Stem integration tests to stall in some cases. Fixes
545 bug 30021; bugfix on 0.2.4.8-alpha.
547 o Code simplification and refactoring:
548 - Introduce a connection_dir_buf_add() helper function that detects
549 whether compression is in use, and adds a string accordingly.
550 Resolves issue 28816.
551 - Refactor handle_get_next_bandwidth() to use
552 connection_dir_buf_add(). Implements ticket 29897.
555 - Clarify that Tor performs stream isolation among *Port listeners
556 by default. Resolves issue 29121.
559 Changes in version 0.4.0.3-alpha - 2019-03-22
560 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
561 bugs from earlier versions.
563 o Minor features (address selection):
564 - Treat the subnet 100.64.0.0/10 as public for some purposes;
565 private for others. This subnet is the RFC 6598 (Carrier Grade
566 NAT) IP range, and is deployed by many ISPs as an alternative to
567 RFC 1918 that does not break existing internal networks. Tor now
568 blocks SOCKS and control ports on these addresses and warns users
569 if client ports or ExtORPorts are listening on a RFC 6598 address.
570 Closes ticket 28525. Patch by Neel Chauhan.
572 o Minor features (geoip):
573 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
574 Country database. Closes ticket 29666.
576 o Minor bugfixes (circuitpadding):
577 - Inspect the circuit-level cell queue before sending padding, to
578 avoid sending padding when too much data is queued. Fixes bug
579 29204; bugfix on 0.4.0.1-alpha.
581 o Minor bugfixes (logging):
582 - Correct a misleading error message when IPv4Only or IPv6Only is
583 used but the resolved address can not be interpreted as an address
584 of the specified IP version. Fixes bug 13221; bugfix on
585 0.2.3.9-alpha. Patch from Kris Katterjohn.
586 - Log the correct port number for listening sockets when "auto" is
587 used to let Tor pick the port number. Previously, port 0 was
588 logged instead of the actual port number. Fixes bug 29144; bugfix
589 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
590 - Stop logging a BUG() warning when Tor is waiting for exit
591 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
593 o Minor bugfixes (memory management):
594 - Refactor the shared random state's memory management so that it
595 actually takes ownership of the shared random value pointers.
596 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
598 o Minor bugfixes (memory management, testing):
599 - Stop leaking parts of the shared random state in the shared-random
600 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
602 o Minor bugfixes (pluggable transports):
603 - Fix an assertion failure crash bug when a pluggable transport is
604 terminated during the bootstrap phase. Fixes bug 29562; bugfix
607 o Minor bugfixes (Rust, protover):
608 - Add a missing "Padding" value to the Rust implementation of
609 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
611 o Minor bugfixes (single onion services):
612 - Allow connections to single onion services to remain idle without
613 being disconnected. Previously, relays acting as rendezvous points
614 for single onion services were mistakenly closing idle rendezvous
615 circuits after 60 seconds, thinking that they were unused
616 directory-fetching circuits that had served their purpose. Fixes
617 bug 29665; bugfix on 0.2.1.26.
619 o Minor bugfixes (stats):
620 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
621 relay and bridge extra-info documents. Fixes bug 29017; bugfix
624 o Minor bugfixes (testing):
625 - Downgrade some LOG_ERR messages in the address/* tests to
626 warnings. The LOG_ERR messages were occurring when we had no
627 configured network. We were failing the unit tests, because we
628 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
629 29530; bugfix on 0.3.5.8.
630 - Fix our gcov wrapper script to look for object files at the
631 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
632 - Decrease the false positive rate of stochastic probability
633 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
635 o Minor bugfixes (Windows, CI):
636 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
637 Windows Server 2012 R2 job. The remaining 2 jobs still provide
638 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
639 fast_finish, so failed jobs terminate the build immediately. Fixes
640 bug 29601; bugfix on 0.3.5.4-alpha.
643 Changes in version 0.3.5.8 - 2019-02-21
644 Tor 0.3.5.8 backports serveral fixes from later releases, including fixes
645 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
648 It also includes a fix for a medium-severity security bug affecting Tor
649 0.3.2.1-alpha and later. All Tor instances running an affected release
650 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
652 o Major bugfixes (cell scheduler, KIST, security):
653 - Make KIST consider the outbuf length when computing what it can
654 put in the outbuf. Previously, KIST acted as though the outbuf
655 were empty, which could lead to the outbuf becoming too full. It
656 is possible that an attacker could exploit this bug to cause a Tor
657 client or relay to run out of memory and crash. Fixes bug 29168;
658 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
659 TROVE-2019-001 and CVE-2019-8955.
661 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
662 - Gracefully handle empty username/password fields in SOCKS5
663 username/password auth messsage and allow SOCKS5 handshake to
664 continue. Previously, we had rejected these handshakes, breaking
665 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
667 o Minor features (compilation, backport from 0.4.0.2-alpha):
668 - Compile correctly when OpenSSL is built with engine support
669 disabled, or with deprecated APIs disabled. Closes ticket 29026.
670 Patches from "Mangix".
672 o Minor features (geoip):
673 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
674 Country database. Closes ticket 29478.
676 o Minor features (testing, backport from 0.4.0.2-alpha):
677 - Treat all unexpected ERR and BUG messages as test failures. Closes
680 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
681 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
682 connection waiting for a descriptor that we actually have in the
683 cache. It turns out that this can actually happen, though it is
684 rare. Now, tor will recover and retry the descriptor. Fixes bug
685 28669; bugfix on 0.3.2.4-alpha.
687 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
688 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
689 IPv6 socket was bound using an address family of AF_INET instead
690 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
693 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
694 - Update Cargo.lock file to match the version made by the latest
695 version of Rust, so that "make distcheck" will pass again. Fixes
696 bug 29244; bugfix on 0.3.3.4-alpha.
698 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
699 - Select guards even if the consensus has expired, as long as the
700 consensus is still reasonably live. Fixes bug 24661; bugfix
703 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
704 - Compile correctly on OpenBSD; previously, we were missing some
705 headers required in order to detect it properly. Fixes bug 28938;
706 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
708 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
709 - Describe the contents of the v3 onion service client authorization
710 files correctly: They hold public keys, not private keys. Fixes
711 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
713 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
714 - Rework rep_hist_log_link_protocol_counts() to iterate through all
715 link protocol versions when logging incoming/outgoing connection
716 counts. Tor no longer skips version 5, and we won't have to
717 remember to update this function when new link protocol version is
718 developed. Fixes bug 28920; bugfix on 0.2.6.10.
720 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
721 - Log more information at "warning" level when unable to read a
722 private key; log more information at "info" level when unable to
723 read a public key. We had warnings here before, but they were lost
724 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
726 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
727 - The amount of total available physical memory is now determined
728 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
729 when it is defined and a 64-bit variant is not available. Fixes
730 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
732 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
733 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
734 than one private key for a hidden service. Fixes bug 29040; bugfix
736 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
737 "debug" level. Tor used to log it as a warning, which caused very
738 long log lines to appear for some users. Fixes bug 29135; bugfix
740 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
741 as a warning. Instead, log it as a protocol warning, because there
742 is nothing that relay operators can do to fix it. Fixes bug 29029;
743 bugfix on 0.2.5.7-rc.
745 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
746 - Mark outdated dirservers when Tor only has a reasonably live
747 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
749 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
750 - Detect and suppress "bug" warnings from the util/time test on
751 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
752 - Do not log an error-level message if we fail to find an IPv6
753 network interface from the unit tests. Fixes bug 29160; bugfix
756 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
757 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
758 Some users took this phrasing to mean that the mentioned guard was
759 under their control or responsibility, which it is not. Fixes bug
760 28895; bugfix on Tor 0.3.0.1-alpha.
763 Changes in version 0.3.4.11 - 2019-02-21
764 Tor 0.3.4.11 is the third stable release in its series. It includes
765 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
766 later. All Tor instances running an affected release should upgrade to
767 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
769 o Major bugfixes (cell scheduler, KIST, security):
770 - Make KIST consider the outbuf length when computing what it can
771 put in the outbuf. Previously, KIST acted as though the outbuf
772 were empty, which could lead to the outbuf becoming too full. It
773 is possible that an attacker could exploit this bug to cause a Tor
774 client or relay to run out of memory and crash. Fixes bug 29168;
775 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
776 TROVE-2019-001 and CVE-2019-8955.
778 o Minor features (geoip):
779 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
780 Country database. Closes ticket 29478.
782 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
783 - Update Cargo.lock file to match the version made by the latest
784 version of Rust, so that "make distcheck" will pass again. Fixes
785 bug 29244; bugfix on 0.3.3.4-alpha.
787 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
788 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
789 as a warning. Instead, log it as a protocol warning, because there
790 is nothing that relay operators can do to fix it. Fixes bug 29029;
791 bugfix on 0.2.5.7-rc.
794 Changes in version 0.3.3.12 - 2019-02-21
795 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
796 0.3.2.1-alpha and later. All Tor instances running an affected release
797 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
799 This release marks the end of support for the Tor 0.3.3.x series. We
800 recommend that users switch to either the Tor 0.3.4 series (supported
801 until at least 10 June 2019), or the Tor 0.3.5 series, which will
802 receive long-term support until at least 1 Feb 2022.
804 o Major bugfixes (cell scheduler, KIST, security):
805 - Make KIST consider the outbuf length when computing what it can
806 put in the outbuf. Previously, KIST acted as though the outbuf
807 were empty, which could lead to the outbuf becoming too full. It
808 is possible that an attacker could exploit this bug to cause a Tor
809 client or relay to run out of memory and crash. Fixes bug 29168;
810 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
811 TROVE-2019-001 and CVE-2019-8955.
813 o Minor features (geoip):
814 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
815 Country database. Closes ticket 29478.
817 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
818 - Update Cargo.lock file to match the version made by the latest
819 version of Rust, so that "make distcheck" will pass again. Fixes
820 bug 29244; bugfix on 0.3.3.4-alpha.
822 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
823 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
824 as a warning. Instead, log it as a protocol warning, because there
825 is nothing that relay operators can do to fix it. Fixes bug 29029;
826 bugfix on 0.2.5.7-rc.
829 Changes in version 0.4.0.2-alpha - 2019-02-21
830 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
831 bugs from earlier versions, including several that had broken
832 backward compatibility.
834 It also includes a fix for a medium-severity security bug affecting Tor
835 0.3.2.1-alpha and later. All Tor instances running an affected release
836 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
838 o Major bugfixes (cell scheduler, KIST, security):
839 - Make KIST consider the outbuf length when computing what it can
840 put in the outbuf. Previously, KIST acted as though the outbuf
841 were empty, which could lead to the outbuf becoming too full. It
842 is possible that an attacker could exploit this bug to cause a Tor
843 client or relay to run out of memory and crash. Fixes bug 29168;
844 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
845 TROVE-2019-001 and CVE-2019-8955.
847 o Major bugfixes (networking):
848 - Gracefully handle empty username/password fields in SOCKS5
849 username/password auth messsage and allow SOCKS5 handshake to
850 continue. Previously, we had rejected these handshakes, breaking
851 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
853 o Major bugfixes (windows, startup):
854 - When reading a consensus file from disk, detect whether it was
855 written in text mode, and re-read it in text mode if so. Always
856 write consensus files in binary mode so that we can map them into
857 memory later. Previously, we had written in text mode, which
858 confused us when we tried to map the file on windows. Fixes bug
859 28614; bugfix on 0.4.0.1-alpha.
861 o Minor features (compilation):
862 - Compile correctly when OpenSSL is built with engine support
863 disabled, or with deprecated APIs disabled. Closes ticket 29026.
864 Patches from "Mangix".
866 o Minor features (developer tooling):
867 - Check that bugfix versions in changes files look like Tor versions
868 from the versions spec. Warn when bugfixes claim to be on a future
869 release. Closes ticket 27761.
870 - Provide a git pre-commit hook that disallows commiting if we have
871 any failures in our code and changelog formatting checks. It is
872 now available in scripts/maint/pre-commit.git-hook. Implements
875 o Minor features (directory authority):
876 - When a directory authority is using a bandwidth file to obtain
877 bandwidth values, include the digest of that file in the vote.
880 o Minor features (geoip):
881 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
882 Country database. Closes ticket 29478.
884 o Minor features (testing):
885 - Treat all unexpected ERR and BUG messages as test failures. Closes
888 o Minor bugfixes (build, compatibility, rust):
889 - Update Cargo.lock file to match the version made by the latest
890 version of Rust, so that "make distcheck" will pass again. Fixes
891 bug 29244; bugfix on 0.3.3.4-alpha.
893 o Minor bugfixes (compilation):
894 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
895 29169; bugfix on 0.4.0.1-alpha.
896 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
897 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
899 o Minor bugfixes (documentation):
900 - Describe the contents of the v3 onion service client authorization
901 files correctly: They hold public keys, not private keys. Fixes
902 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
904 o Minor bugfixes (linux seccomp sandbox):
905 - Fix startup crash when experimental sandbox support is enabled.
906 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
908 o Minor bugfixes (logging):
909 - Avoid logging that we are relaxing a circuit timeout when that
910 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
911 - Log more information at "warning" level when unable to read a
912 private key; log more information at "info" level when unable to
913 read a public key. We had warnings here before, but they were lost
914 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
916 o Minor bugfixes (misc):
917 - The amount of total available physical memory is now determined
918 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
919 when it is defined and a 64-bit variant is not available. Fixes
920 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
922 o Minor bugfixes (onion services):
923 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
924 than one private key for a hidden service. Fixes bug 29040; bugfix
926 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
927 "debug" level. Tor used to log it as a warning, which caused very
928 long log lines to appear for some users. Fixes bug 29135; bugfix
930 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
931 as a warning. Instead, log it as a protocol warning, because there
932 is nothing that relay operators can do to fix it. Fixes bug 29029;
933 bugfix on 0.2.5.7-rc.
935 o Minor bugfixes (scheduler):
936 - When re-adding channels to the pending list, check the correct
937 channel's sched_heap_idx. This issue has had no effect in mainline
938 Tor, but could have led to bugs down the road in improved versions
939 of our circuit scheduling code. Fixes bug 29508; bugfix
942 o Minor bugfixes (tests):
943 - Fix intermittent failures on an adaptive padding test. Fixes one
944 case of bug 29122; bugfix on 0.4.0.1-alpha.
945 - Disable an unstable circuit-padding test that was failing
946 intermittently because of an ill-defined small histogram. Such
947 histograms will be allowed again after 29298 is implemented. Fixes
948 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
949 - Detect and suppress "bug" warnings from the util/time test on
950 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
951 - Do not log an error-level message if we fail to find an IPv6
952 network interface from the unit tests. Fixes bug 29160; bugfix
956 - In the manpage entry describing MapAddress torrc setting, use
957 example IP addresses from ranges specified for use in documentation
958 by RFC 5737. Resolves issue 28623.
961 - Remove the old check-tor script. Resolves issue 29072.
964 Changes in version 0.4.0.1-alpha - 2019-01-18
965 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
966 introduces improved features for power and bandwidth conservation,
967 more accurate reporting of bootstrap progress for user interfaces, and
968 an experimental backend for an exciting new adaptive padding feature.
969 There is also the usual assortment of bugfixes and minor features, all
972 o Major features (battery management, client, dormant mode):
973 - When Tor is running as a client, and it is unused for a long time,
974 it can now enter a "dormant" state. When Tor is dormant, it avoids
975 network and CPU activity until it is reawoken either by a user
976 request or by a controller command. For more information, see the
977 configuration options starting with "Dormant". Implements tickets
979 - The client's memory of whether it is "dormant", and how long it
980 has spent idle, persists across invocations. Implements
982 - There is a DormantOnFirstStartup option that integrators can use
983 if they expect that in many cases, Tor will be installed but
986 o Major features (bootstrap reporting):
987 - When reporting bootstrap progress, report the first connection
988 uniformly, regardless of whether it's a connection for building
989 application circuits. This allows finer-grained reporting of early
990 progress than previously possible, with the improvements of ticket
991 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
992 - When reporting bootstrap progress, treat connecting to a proxy or
993 pluggable transport as separate from having successfully used that
994 proxy or pluggable transport to connect to a relay. Closes tickets
997 o Major features (circuit padding):
998 - Implement preliminary support for the circuit padding portion of
999 Proposal 254. The implementation supports Adaptive Padding (aka
1000 WTF-PAD) state machines for use between experimental clients and
1001 relays. Support is also provided for APE-style state machines that
1002 use probability distributions instead of histograms to specify
1003 inter-packet delay. At the moment, Tor does not provide any
1004 padding state machines that are used in normal operation: for now,
1005 this feature exists solely for experimentation. Closes
1008 o Major features (refactoring):
1009 - Tor now uses an explicit list of its own subsystems when
1010 initializing and shutting down. Previously, these systems were
1011 managed implicitly in various places throughout the codebase.
1012 (There may still be some subsystems using the old system.) Closes
1015 o Minor features (bootstrap reporting):
1016 - When reporting bootstrap progress, stop distinguishing between
1017 situations where only internal paths are available and situations
1018 where external paths are available. Previously, Tor would often
1019 erroneously report that it had only internal paths. Closes
1022 o Minor features (continuous integration):
1023 - Log Python version during each Travis CI job. Resolves
1026 o Minor features (controller):
1027 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
1028 Implements ticket 28843.
1030 o Minor features (developer tooling):
1031 - Provide a git hook script to prevent "fixup!" and "squash!"
1032 commits from ending up in the master branch, as scripts/main/pre-
1033 push.git-hook. Closes ticket 27993.
1035 o Minor features (directory authority):
1036 - Directory authorities support a new consensus algorithm, under
1037 which the family lines in microdescriptors are encoded in a
1038 canonical form. This change makes family lines more compressible
1039 in transit, and on the client. Closes ticket 28266; implements
1042 o Minor features (directory authority, relay):
1043 - Authorities now vote on a "StaleDesc" flag to indicate that a
1044 relay's descriptor is so old that the relay should upload again
1045 soon. Relays treat this flag as a signal to upload a new
1046 descriptor. This flag will eventually let us remove the
1047 'published' date from routerstatus entries, and make our consensus
1048 diffs much smaller. Closes ticket 26770; implements proposal 293.
1050 o Minor features (fallback directory mirrors):
1051 - Update the fallback whitelist based on operator opt-ins and opt-
1052 outs. Closes ticket 24805, patch by Phoul.
1054 o Minor features (FreeBSD):
1055 - On FreeBSD-based systems, warn relay operators if the
1056 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
1057 Closes ticket 28518.
1059 o Minor features (HTTP standards compliance):
1060 - Stop sending the header "Content-type: application/octet-stream"
1061 along with transparently compressed documents: this confused
1062 browsers. Closes ticket 28100.
1064 o Minor features (IPv6):
1065 - We add an option ClientAutoIPv6ORPort, to make clients randomly
1066 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
1067 every time a node is loaded from a new consensus or bridge config.
1068 We expect that this option will enable clients to bootstrap more
1069 quickly without having to determine whether they support IPv4,
1070 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
1071 - When using addrs_in_same_network_family(), avoid choosing circuit
1072 paths that pass through the same IPv6 subnet more than once.
1073 Previously, we only checked IPv4 subnets. Closes ticket 24393.
1074 Patch by Neel Chauhan.
1076 o Minor features (log messages):
1077 - Improve log message in v3 onion services that could print out
1078 negative revision counters. Closes ticket 27707. Patch
1081 o Minor features (memory usage):
1082 - Save memory by storing microdescriptor family lists with a more
1083 compact representation. Closes ticket 27359.
1084 - Tor clients now use mmap() to read consensus files from disk, so
1085 that they no longer need keep the full text of a consensus in
1086 memory when parsing it or applying a diff. Closes ticket 27244.
1088 o Minor features (parsing):
1089 - Directory authorities now validate that router descriptors and
1090 ExtraInfo documents are in a valid subset of UTF-8, and reject
1091 them if they are not. Closes ticket 27367.
1093 o Minor features (performance):
1094 - Cache the results of summarize_protocol_flags(), so that we don't
1095 have to parse the same protocol-versions string over and over.
1096 This should save us a huge number of malloc calls on startup, and
1097 may reduce memory fragmentation with some allocators. Closes
1099 - Remove a needless memset() call from get_token_arguments, thereby
1100 speeding up the tokenization of directory objects by about 20%.
1101 Closes ticket 28852.
1102 - Replace parse_short_policy() with a faster implementation, to
1103 improve microdescriptor parsing time. Closes ticket 28853.
1104 - Speed up directory parsing a little by avoiding use of the non-
1105 inlined strcmp_len() function. Closes ticket 28856.
1106 - Speed up microdescriptor parsing by about 30%, to help improve
1107 startup time. Closes ticket 28839.
1109 o Minor features (pluggable transports):
1110 - Add support for emitting STATUS updates to Tor's control port from
1111 a pluggable transport process. Closes ticket 28846.
1112 - Add support for logging to Tor's logging subsystem from a
1113 pluggable transport process. Closes ticket 28180.
1115 o Minor features (process management):
1116 - Add a new process API for handling child processes. This new API
1117 allows Tor to have bi-directional communication with child
1118 processes on both Unix and Windows. Closes ticket 28179.
1119 - Use the subsystem manager to initialize and shut down the process
1120 module. Closes ticket 28847.
1122 o Minor features (relay):
1123 - When listing relay families, list them in canonical form including
1124 the relay's own identity, and try to give a more useful set of
1125 warnings. Part of ticket 28266 and proposal 298.
1127 o Minor features (required protocols):
1128 - Before exiting because of a missing required protocol, Tor will
1129 now check the publication time of the consensus, and not exit
1130 unless the consensus is newer than the Tor program's own release
1131 date. Previously, Tor would not check the consensus publication
1132 time, and so might exit because of a missing protocol that might
1133 no longer be required in a current consensus. Implements proposal
1134 297; closes ticket 27735.
1136 o Minor features (testing):
1137 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
1138 networks. Closes ticket 28840. Patch by Rob Jansen.
1140 o Minor bugfixes (client, clock skew):
1141 - Bootstrap successfully even when Tor's clock is behind the clocks
1142 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
1143 - Select guards even if the consensus has expired, as long as the
1144 consensus is still reasonably live. Fixes bug 24661; bugfix
1147 o Minor bugfixes (compilation):
1148 - Compile correctly on OpenBSD; previously, we were missing some
1149 headers required in order to detect it properly. Fixes bug 28938;
1150 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1152 o Minor bugfixes (directory clients):
1153 - Mark outdated dirservers when Tor only has a reasonably live
1154 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1156 o Minor bugfixes (directory mirrors):
1157 - Even when a directory mirror's clock is behind the clocks on the
1158 authorities, we now allow the mirror to serve "future"
1159 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
1161 o Minor bugfixes (DNS):
1162 - Gracefully handle an empty or absent resolve.conf file by falling
1163 back to using "localhost" as a DNS server (and hoping it works).
1164 Previously, we would just stop running as an exit. Fixes bug
1165 21900; bugfix on 0.2.1.10-alpha.
1167 o Minor bugfixes (guards):
1168 - In count_acceptable_nodes(), the minimum number is now one bridge
1169 or guard node, and two non-guard nodes for a circuit. Previously,
1170 we had added up the sum of all nodes with a descriptor, but that
1171 could cause us to build failing circuits when we had either too
1172 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
1173 0.3.6.1-alpha. Patch by Neel Chauhan.
1175 o Minor bugfixes (IPv6):
1176 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1177 IPv6 socket was bound using an address family of AF_INET instead
1178 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1181 o Minor bugfixes (logging):
1182 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1183 link protocol versions when logging incoming/outgoing connection
1184 counts. Tor no longer skips version 5, and we won't have to
1185 remember to update this function when new link protocol version is
1186 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1188 o Minor bugfixes (networking):
1189 - Introduce additional checks into tor_addr_parse() to reject
1190 certain incorrect inputs that previously were not detected. Fixes
1191 bug 23082; bugfix on 0.2.0.10-alpha.
1193 o Minor bugfixes (onion service v3, client):
1194 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1195 connection waiting for a descriptor that we actually have in the
1196 cache. It turns out that this can actually happen, though it is
1197 rare. Now, tor will recover and retry the descriptor. Fixes bug
1198 28669; bugfix on 0.3.2.4-alpha.
1200 o Minor bugfixes (periodic events):
1201 - Refrain from calling routerlist_remove_old_routers() from
1202 check_descriptor_callback(). Instead, create a new hourly periodic
1203 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1205 o Minor bugfixes (pluggable transports):
1206 - Make sure that data is continously read from standard output and
1207 standard error pipes of a pluggable transport child-process, to
1208 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1209 bugfix on 0.2.3.6-alpha.
1211 o Minor bugfixes (unit tests):
1212 - Instead of relying on hs_free_all() to clean up all onion service
1213 objects in test_build_descriptors(), we now deallocate them one by
1214 one. This lets Coverity know that we are not leaking memory there
1215 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1217 o Minor bugfixes (usability):
1218 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1219 Some users took this phrasing to mean that the mentioned guard was
1220 under their control or responsibility, which it is not. Fixes bug
1221 28895; bugfix on Tor 0.3.0.1-alpha.
1223 o Code simplification and refactoring:
1224 - Reimplement NETINFO cell parsing and generation to rely on
1225 trunnel-generated wire format handling code. Closes ticket 27325.
1226 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1228 - Rework SOCKS wire format handling to rely on trunnel-generated
1229 parsing/generation code. Resolves ticket 27620.
1230 - Split out bootstrap progress reporting from control.c into a
1231 separate file. Part of ticket 27402.
1232 - The .may_include files that we use to describe our directory-by-
1233 directory dependency structure now describe a noncircular
1234 dependency graph over the directories that they cover. Our
1235 checkIncludes.py tool now enforces this noncircularity. Closes
1239 - Mention that you cannot add a new onion service if Tor is already
1240 running with Sandbox enabled. Closes ticket 28560.
1241 - Improve ControlPort documentation. Mention that it accepts
1242 address:port pairs, and can be used multiple times. Closes
1244 - Document the exact output of "tor --version". Closes ticket 28889.
1247 - Stop responding to the 'GETINFO status/version/num-concurring' and
1248 'GETINFO status/version/num-versioning' control port commands, as
1249 those were deprecated back in 0.2.0.30. Also stop listing them in
1250 output of 'GETINFO info/names'. Resolves ticket 28757.
1251 - The scripts used to generate and maintain the list of fallback
1252 directories have been extracted into a new "fallback-scripts"
1253 repository. Closes ticket 27914.
1256 - Run shellcheck for scripts in the in scripts/ directory. Closes
1258 - Add unit tests for tokenize_string() and get_next_token()
1259 functions. Resolves ticket 27625.
1261 o Code simplification and refactoring (onion service v3):
1262 - Consolidate the authorized client descriptor cookie computation
1263 code from client and service into one function. Closes
1266 o Code simplification and refactoring (shell scripts):
1267 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1269 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1270 Resolves ticket 28006.
1271 - Fix issues that shellcheck found in updateRustDependencies.sh.
1272 Resolves ticket 28012.
1273 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1274 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1275 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1276 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1280 Changes in version 0.3.3.11 - 2019-01-07
1281 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1282 numerous fixes, including an important fix for anyone using OpenSSL
1283 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1284 to this version, or to a later series.
1286 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1287 We anticipate that this will be the last release of Tor 0.3.3, unless
1288 some major bug is before then. Some time between now and then, users
1289 should switch to either the Tor 0.3.4 series (supported until at least
1290 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1291 support until at least 1 Feb 2022.
1293 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1294 - Fix our usage of named groups when running as a TLS 1.3 client in
1295 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1296 running as a relay, which caused clients to fail to negotiate TLS
1297 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1300 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1301 - Fix a use-after-free error that could be caused by passing Tor an
1302 impossible set of options that would fail during options_act().
1303 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1305 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1306 - Only run one online rust build in Travis, to reduce network
1307 errors. Skip offline rust builds on Travis for Linux gcc, because
1308 they're redundant. Implements ticket 27252.
1309 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1310 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1311 Linux with default settings, because all the non-default builds
1312 use gcc on Linux. Implements ticket 27252.
1314 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1315 - Use the Travis Homebrew addon to install packages on macOS during
1316 Travis CI. The package list is the same, but the Homebrew addon
1317 does not do a `brew update` by default. Implements ticket 27738.
1319 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1320 - Replace the 150 fallbacks originally introduced in Tor
1321 0.3.3.1-alpha in January 2018 (of which ~115 were still
1322 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1323 removed) generated in December 2018. Closes ticket 24803.
1325 o Minor features (geoip):
1326 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1327 Country database. Closes ticket 29012.
1329 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1330 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1331 key export function from handling long labels. When this bug is
1332 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1333 version of OpenSSL without this bug when it becomes available.
1334 Closes ticket 28973.
1336 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1337 - Update relay descriptor on bandwidth changes only when the uptime
1338 is smaller than 24h, in order to reduce the efficiency of guard
1339 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1341 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1342 - Avoid undefined behavior in an end-of-string check when parsing
1343 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1346 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1347 - Rewrite our assertion macros so that they no longer suppress the
1348 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1350 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1351 - Initialize a variable unconditionally in aes_new_cipher(), since
1352 some compilers cannot tell that we always initialize it before
1353 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1355 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1356 - Log additional info when we get a relay that shares an ed25519 ID
1357 with a different relay, instead making a BUG() warning. Fixes bug
1358 27800; bugfix on 0.3.2.1-alpha.
1360 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1361 - When a user requests a group-readable DataDirectory, give it to
1362 them. Previously, when the DataDirectory and the CacheDirectory
1363 were the same, the default setting (0) for
1364 CacheDirectoryGroupReadable would override the setting for
1365 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1368 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1369 - When the onion service directory can't be created or has the wrong
1370 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1373 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1374 - Close all SOCKS request (for the same .onion) if the newly fetched
1375 descriptor is unusable. Before that, we would close only the first
1376 one leaving the other hanging and let to time out by themselves.
1377 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1379 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1380 - Don't warn so loudly when Tor is unable to decode an onion
1381 descriptor. This can now happen as a normal use case if a client
1382 gets a descriptor with client authorization but the client is not
1383 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1385 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1386 - When deleting an ephemeral onion service (DEL_ONION), do not close
1387 any rendezvous circuits in order to let the existing client
1388 connections finish by themselves or closed by the application. The
1389 HS v2 is doing that already so now we have the same behavior for
1390 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1392 o Minor bugfixes (HTTP tunnel):
1393 - Fix a bug warning when closing an HTTP tunnel connection due to
1394 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1397 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1398 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1399 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1401 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1402 - Ensure circuitmux queues are empty before scheduling or sending
1403 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1405 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1406 - Reject protocol names containing bytes other than alphanumeric
1407 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1410 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1411 - Compute protover votes correctly in the rust version of the
1412 protover code. Previously, the protover rewrite in 24031 allowed
1413 repeated votes from the same voter for the same protocol version
1414 to be counted multiple times in protover_compute_vote(). Fixes bug
1415 27649; bugfix on 0.3.3.5-rc.
1416 - Reject protover names that contain invalid characters. Fixes bug
1417 27687; bugfix on 0.3.3.1-alpha.
1419 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1420 - protover_all_supported() would attempt to allocate up to 16GB on
1421 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1422 bugfix on 0.3.3.5-rc.
1424 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1425 - Fix a potential null dereference in protover_all_supported(). Add
1426 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1427 - Return a string that can be safely freed by C code, not one
1428 created by the rust allocator, in protover_all_supported(). Fixes
1429 bug 27740; bugfix on 0.3.3.1-alpha.
1430 - Fix an API mismatch in the rust implementation of
1431 protover_compute_vote(). This bug could have caused crashes on any
1432 directory authorities running Tor with Rust (which we do not yet
1433 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1435 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1436 - If a unit test running in a subprocess exits abnormally or with a
1437 nonzero status code, treat the test as having failed, even if the
1438 test reported success. Without this fix, memory leaks don't cause
1439 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1440 bugfix on 0.2.2.4-alpha.
1442 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1443 - Treat backtrace test failures as expected on BSD-derived systems
1444 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1445 (FreeBSD failures have been treated as expected since 18204 in
1446 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1448 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1449 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1450 bugfix on 0.3.0.1-alpha.
1453 Changes in version 0.3.4.10 - 2019-01-07
1454 Tor 0.3.4.9 is the second stable release in its series; it backports
1455 numerous fixes, including an important fix for relays, and for anyone
1456 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1459 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1460 2019. Some time between now and then, users should switch to the Tor
1461 0.3.5 series, which will receive long-term support until at least 1
1464 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1465 - Fix our usage of named groups when running as a TLS 1.3 client in
1466 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1467 running as a relay, which caused clients to fail to negotiate TLS
1468 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1471 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1472 - Always reactivate linked connections in the main loop so long as
1473 any linked connection has been active. Previously, connections
1474 serving directory information wouldn't get reactivated after the
1475 first chunk of data was sent (usually 32KB), which would prevent
1476 clients from bootstrapping. Fixes bug 28912; bugfix on
1477 0.3.4.1-alpha. Patch by "cypherpunks3".
1479 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1480 - Always show the configure and test logs, and upload them as build
1481 artifacts, when building for Windows using Appveyor CI.
1484 o Minor features (controller, backport from 0.3.5.1-alpha):
1485 - For purposes of CIRC_BW-based dropped cell detection, track half-
1486 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1487 bias check cells to arrive without counting it as dropped until
1488 either the END arrives, or the windows are empty. Closes
1491 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1492 - Replace the 150 fallbacks originally introduced in Tor
1493 0.3.3.1-alpha in January 2018 (of which ~115 were still
1494 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1495 removed) generated in December 2018. Closes ticket 24803.
1497 o Minor features (geoip):
1498 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1499 Country database. Closes ticket 28395.
1501 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1502 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1503 key export function from handling long labels. When this bug is
1504 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1505 version of OpenSSL without this bug when it becomes available.
1506 Closes ticket 28973.
1508 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1509 - Initialize a variable unconditionally in aes_new_cipher(), since
1510 some compilers cannot tell that we always initialize it before
1511 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1513 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1514 - Avoid a logging a BUG() stacktrace when closing connection held
1515 open because the write side is rate limited but not the read side.
1516 Now, the connection read side is simply shut down until Tor is
1517 able to flush the connection and close it. Fixes bug 27750; bugfix
1520 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1521 - Manually configure the zstd compiler options, when building using
1522 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1523 not come with a pkg-config file. Fixes bug 28454; bugfix
1525 - Stop using an external OpenSSL install, and stop installing MSYS2
1526 packages, when building using mingw on Appveyor Windows CI. Fixes
1527 bug 28399; bugfix on 0.3.4.1-alpha.
1529 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1530 - Explicitly specify the path to the OpenSSL library and do not
1531 download OpenSSL from Pacman, but instead use the library that is
1532 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1534 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1535 - When a user requests a group-readable DataDirectory, give it to
1536 them. Previously, when the DataDirectory and the CacheDirectory
1537 were the same, the default setting (0) for
1538 CacheDirectoryGroupReadable would override the setting for
1539 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1542 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1543 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1544 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1546 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1547 - Don't warn so loudly when Tor is unable to decode an onion
1548 descriptor. This can now happen as a normal use case if a client
1549 gets a descriptor with client authorization but the client is not
1550 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1552 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1553 - When deleting an ephemeral onion service (DEL_ONION), do not close
1554 any rendezvous circuits in order to let the existing client
1555 connections finish by themselves or closed by the application. The
1556 HS v2 is doing that already so now we have the same behavior for
1557 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1559 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1560 - Update relay descriptor on bandwidth changes only when the uptime
1561 is smaller than 24h, in order to reduce the efficiency of guard
1562 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1564 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1565 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1566 bugfix on 0.3.0.1-alpha.
1569 Changes in version 0.3.5.7 - 2019-01-07
1570 Tor 0.3.5.7 is the first stable release in its series; it includes
1571 compilation and portability fixes, and a fix for a severe problem
1572 affecting directory caches.
1574 The Tor 0.3.5 series includes several new features and performance
1575 improvements, including client authorization for v3 onion services,
1576 cleanups to bootstrap reporting, support for improved bandwidth-
1577 measurement tools, experimental support for NSS in place of OpenSSL,
1578 and much more. It also begins a full reorganization of Tor's code
1579 layout, for improved modularity and maintainability in the future.
1580 Finally, there is the usual set of performance improvements and
1581 bugfixes that we try to do in every release series.
1583 There are a couple of changes in the 0.3.5 that may affect
1584 compatibility. First, the default version for newly created onion
1585 services is now v3. Use the HiddenServiceVersion option if you want to
1586 override this. Second, some log messages related to bootstrapping have
1587 changed; if you use stem, you may need to update to the latest version
1588 so it will recognize them.
1590 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1591 will continue to patch major bugs in typical configurations of 0.3.5
1592 until at least 1 Feb 2022. (We do not plan to provide long-term
1593 support for embedding, Rust support, NSS support, running a directory
1594 authority, or unsupported platforms. For these, you will need to stick
1595 with the latest stable release.)
1597 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1598 since 0.3.4.9, see the ReleaseNotes file.
1600 o Major bugfixes (relay, directory):
1601 - Always reactivate linked connections in the main loop so long as
1602 any linked connection has been active. Previously, connections
1603 serving directory information wouldn't get reactivated after the
1604 first chunk of data was sent (usually 32KB), which would prevent
1605 clients from bootstrapping. Fixes bug 28912; bugfix on
1606 0.3.4.1-alpha. Patch by "cypherpunks3".
1608 o Minor features (compilation):
1609 - When possible, place our warning flags in a separate file, to
1610 avoid flooding verbose build logs. Closes ticket 28924.
1612 o Minor features (geoip):
1613 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1614 Country database. Closes ticket 29012.
1616 o Minor features (OpenSSL bug workaround):
1617 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1618 key export function from handling long labels. When this bug is
1619 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1620 version of OpenSSL without this bug when it becomes available.
1621 Closes ticket 28973.
1623 o Minor features (performance):
1624 - Remove about 96% of the work from the function that we run at
1625 startup to test our curve25519_basepoint implementation. Since
1626 this function has yet to find an actual failure, we now only run
1627 it for 8 iterations instead of 200. Based on our profile
1628 information, this change should save around 8% of our startup time
1629 on typical desktops, and may have a similar effect on other
1630 platforms. Closes ticket 28838.
1631 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1632 every startup. Doing this wasted time and cycles, especially on
1633 low-powered devices. Closes ticket 28851.
1635 o Minor bugfixes (compilation):
1636 - Fix compilation for Android by adding a missing header to
1637 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
1639 o Minor bugfixes (correctness):
1640 - Fix an unreached code path where we checked the value of
1641 "hostname" inside send_resolved_hostname_cell(). Previously, we
1642 used it before checking it; now we check it first. Fixes bug
1643 28879; bugfix on 0.1.2.7-alpha.
1645 o Minor bugfixes (testing):
1646 - Make sure that test_rebind.py actually obeys its timeout, even
1647 when it receives a large number of log messages. Fixes bug 28883;
1648 bugfix on 0.3.5.4-alpha.
1649 - Stop running stem's unit tests as part of "make test-stem", but
1650 continue to run stem's unit and online tests during "make test-
1651 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1653 o Minor bugfixes (windows services):
1654 - Make Tor start correctly as an NT service again: previously it was
1655 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
1657 o Code simplification and refactoring:
1658 - When parsing a port configuration, make it more obvious to static
1659 analyzer tools that we always initialize the address. Closes
1663 Changes in version 0.3.5.6-rc - 2018-12-18
1664 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
1665 It is the first release candidate in the 0.3.5.x series; if no further
1666 huge bugs are found, our next release may be the stable 0.3.5.x.
1668 o Minor features (continuous integration, Windows):
1669 - Always show the configure and test logs, and upload them as build
1670 artifacts, when building for Windows using Appveyor CI.
1673 o Minor features (fallback directory list):
1674 - Replace the 150 fallbacks originally introduced in Tor
1675 0.3.3.1-alpha in January 2018 (of which ~115 were still
1676 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1677 removed) generated in December 2018. Closes ticket 24803.
1679 o Minor features (geoip):
1680 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
1681 Country database. Closes ticket 28744.
1683 o Minor bugfixes (compilation):
1684 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
1685 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
1687 o Minor bugfixes (continuous integration, Windows):
1688 - Explicitly specify the path to the OpenSSL library and do not
1689 download OpenSSL from Pacman, but instead use the library that is
1690 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1692 o Minor bugfixes (onion service v3):
1693 - When deleting an ephemeral onion service (DEL_ONION), do not close
1694 any rendezvous circuits in order to let the existing client
1695 connections finish by themselves or closed by the application. The
1696 HS v2 is doing that already so now we have the same behavior for
1697 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1699 o Minor bugfixes (restart-in-process, boostrap):
1700 - Add missing resets of bootstrap tracking state when shutting down
1701 (regression caused by ticket 27169). Fixes bug 28524; bugfix
1704 o Minor bugfixes (testing):
1705 - Use a separate DataDirectory for the test_rebind script.
1706 Previously, this script would run using the default DataDirectory,
1707 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
1708 Patch from Taylor R Campbell.
1709 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1710 bugfix on 0.3.0.1-alpha.
1712 o Minor bugfixes (Windows):
1713 - Correctly identify Windows 8.1, Windows 10, and Windows Server
1714 2008 and later from their NT versions. Fixes bug 28096; bugfix on
1715 0.2.2.34; reported by Keifer Bly.
1716 - On recent Windows versions, the GetVersionEx() function may report
1717 an earlier Windows version than the running OS. To avoid user
1718 confusion, add "[or later]" to Tor's version string on affected
1719 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
1721 - Remove Windows versions that were never supported by the
1722 GetVersionEx() function. Stop duplicating the latest Windows
1723 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
1724 reported by Keifer Bly.
1727 - Increase logging and tag all log entries with timestamps in
1728 test_rebind.py. Provides diagnostics for issue 28229.
1730 o Code simplification and refactoring (shared random, dirauth):
1731 - Change many tor_assert() to use BUG() instead. The idea is to not
1732 crash a dirauth but rather scream loudly with a stacktrace and let
1733 it continue run. The shared random subsystem is very resilient and
1734 if anything wrong happens with it, at worst a non coherent value
1735 will be put in the vote and discarded by the other authorities.
1736 Closes ticket 19566.
1738 o Documentation (onion services):
1739 - Document in the man page that changing ClientOnionAuthDir value or
1740 adding a new file in the directory will not work at runtime upon
1741 sending a HUP if Sandbox 1. Closes ticket 28128.
1742 - Note in the man page that the only real way to fully revoke an
1743 onion service v3 client authorization is by restarting the tor
1744 process. Closes ticket 28275.
1747 Changes in version 0.3.5.5-alpha - 2018-11-16
1748 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
1749 including several that we hope to backport to older release series in
1752 o Major bugfixes (OpenSSL, portability):
1753 - Fix our usage of named groups when running as a TLS 1.3 client in
1754 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1755 running as a relay, which caused clients to fail to negotiate TLS
1756 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1759 o Minor features (geoip):
1760 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1761 Country database. Closes ticket 28395.
1763 o Minor bugfixes (compilation):
1764 - Initialize a variable unconditionally in aes_new_cipher(), since
1765 some compilers cannot tell that we always initialize it before
1766 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1768 o Minor bugfixes (connection, relay):
1769 - Avoid a logging a BUG() stacktrace when closing connection held
1770 open because the write side is rate limited but not the read side.
1771 Now, the connection read side is simply shut down until Tor is
1772 able to flush the connection and close it. Fixes bug 27750; bugfix
1775 o Minor bugfixes (continuous integration, Windows):
1776 - Manually configure the zstd compiler options, when building using
1777 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1778 not come with a pkg-config file. Fixes bug 28454; bugfix
1780 - Stop using an external OpenSSL install, and stop installing MSYS2
1781 packages, when building using mingw on Appveyor Windows CI. Fixes
1782 bug 28399; bugfix on 0.3.4.1-alpha.
1784 o Minor bugfixes (documentation):
1785 - Make Doxygen work again after the code movement in the 0.3.5
1786 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
1788 o Minor bugfixes (Linux seccomp2 sandbox):
1789 - Permit the "shutdown()" system call, which is apparently used by
1790 OpenSSL under some circumstances. Fixes bug 28183; bugfix
1793 o Minor bugfixes (logging):
1794 - Stop talking about the Named flag in log messages. Clients have
1795 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
1798 o Minor bugfixes (memory leaks):
1799 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1800 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1802 o Minor bugfixes (onion services):
1803 - On an intro point for a version 3 onion service, stop closing
1804 introduction circuits on an NACK. This lets the client decide
1805 whether to reuse the circuit or discard it. Previously, we closed
1806 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
1807 0.3.2.1-alpha. Patch by Neel Chaunan.
1808 - When replacing a descriptor in the client cache, make sure to
1809 close all client introduction circuits for the old descriptor, so
1810 we don't end up with unusable leftover circuits. Fixes bug 27471;
1811 bugfix on 0.3.2.1-alpha.
1814 Changes in version 0.3.5.4-alpha - 2018-11-08
1815 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
1816 improves our continuous integration support. It continues our attempts
1817 to stabilize this alpha branch and build it into a foundation for an
1818 acceptable long-term-support release.
1820 o Major bugfixes (compilation, rust):
1821 - Rust tests can now build and run successfully with the
1822 --enable-fragile-hardening option enabled. Doing this currently
1823 requires the rust beta channel; it will be possible with stable
1824 rust once Rust version 1.31 is released. Patch from Alex Crichton.
1825 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
1827 o Major bugfixes (embedding, main loop):
1828 - When DisableNetwork becomes set, actually disable periodic events
1829 that are already enabled. (Previously, we would refrain from
1830 enabling new ones, but we would leave the old ones turned on.)
1831 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
1833 o Minor features (continuous integration):
1834 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
1836 - Add new CI job to Travis configuration to run stem-based
1837 integration tests. Closes ticket 27913.
1839 o Minor features (Windows, continuous integration):
1840 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
1841 Appveyor's CI. Closes ticket 28318.
1843 o Minor bugfixes (C correctness, also in 0.3.4.9):
1844 - Avoid undefined behavior in an end-of-string check when parsing
1845 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1848 o Minor bugfixes (compilation):
1849 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
1850 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1852 o Minor bugfixes (compilation, OpenSolaris):
1853 - Fix compilation on OpenSolaris and its descendants by adding a
1854 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
1857 o Minor bugfixes (configuration):
1858 - Refuse to start with relative file paths and RunAsDaemon set
1859 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
1862 o Minor bugfixes (directory authority, also in 0.3.4.9):
1863 - Log additional info when we get a relay that shares an ed25519 ID
1864 with a different relay, instead of a BUG() warning with a
1865 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
1867 o Minor bugfixes (onion service v3):
1868 - Build the service descriptor's signing key certificate before
1869 uploading, so we always have a fresh one: leaving no chances for
1870 it to expire service side. Fixes bug 27838; bugfix
1873 o Minor bugfixes (onion service v3, client authorization):
1874 - Fix an assert() when adding a client authorization for the first
1875 time and then sending a HUP signal to the service. Before that,
1876 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
1878 o Minor bugfixes (onion services):
1879 - Unless we have explicitly set HiddenServiceVersion, detect the
1880 onion service version and then look for invalid options.
1881 Previously, we did the reverse, but that broke existing configs
1882 which were pointed to a v2 service and had options like
1883 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
1884 0.3.5.1-alpha. Patch by Neel Chauhan.
1886 o Minor bugfixes (portability):
1887 - Make the OPE code (which is used for v3 onion services) run
1888 correctly on big-endian platforms. Fixes bug 28115; bugfix
1891 o Minor bugfixes (protover, rust):
1892 - Reject extra commas in version strings. Fixes bug 27197; bugfix
1895 o Minor bugfixes (relay shutdown, systemd):
1896 - Notify systemd of ShutdownWaitLength so it can be set to longer
1897 than systemd's TimeoutStopSec. In Tor's systemd service file, set
1898 TimeoutSec to 60 seconds to allow Tor some time to shut down.
1899 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
1901 o Minor bugfixes (rust, also in 0.3.4.9):
1902 - Fix a potential null dereference in protover_all_supported(). Add
1903 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1904 - Return a string that can be safely freed by C code, not one
1905 created by the rust allocator, in protover_all_supported(). Fixes
1906 bug 27740; bugfix on 0.3.3.1-alpha.
1908 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
1909 - Fix an API mismatch in the rust implementation of
1910 protover_compute_vote(). This bug could have caused crashes on any
1911 directory authorities running Tor with Rust (which we do not yet
1912 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1914 o Minor bugfixes (testing):
1915 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
1916 27968; bugfix on 0.3.5.1-alpha.
1918 o Minor bugfixes (testing, also in 0.3.4.9):
1919 - Treat backtrace test failures as expected on BSD-derived systems
1920 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1921 (FreeBSD failures have been treated as expected since 18204 in
1922 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1924 o Documentation (onion service manpage):
1925 - Improve HSv3 client authorization by making some options more
1926 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
1929 Changes in version 0.3.4.9 - 2018-11-02
1930 Tor 0.3.4.9 is the second stable release in its series; it backports
1931 numerous fixes, including a fix for a bandwidth management bug that
1932 was causing memory exhaustion on relays. Anyone running an earlier
1933 version of Tor 0.3.4.9 should upgrade.
1935 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
1936 - Fix compilation on ARM (and other less-used CPUs) when compiling
1937 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
1939 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
1940 - Make sure Tor bootstraps and works properly if only the
1941 ControlPort is set. Prior to this fix, Tor would only bootstrap
1942 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
1943 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
1945 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
1946 - When our write bandwidth limit is exhausted, stop writing on the
1947 connection. Previously, we had a typo in the code that would make
1948 us stop reading instead, leading to relay connections being stuck
1949 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
1952 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1953 - Fix a use-after-free error that could be caused by passing Tor an
1954 impossible set of options that would fail during options_act().
1955 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1957 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1958 - Don't do a distcheck with --disable-module-dirauth in Travis.
1959 Implements ticket 27252.
1960 - Only run one online rust build in Travis, to reduce network
1961 errors. Skip offline rust builds on Travis for Linux gcc, because
1962 they're redundant. Implements ticket 27252.
1963 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1964 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1965 Linux with default settings, because all the non-default builds
1966 use gcc on Linux. Implements ticket 27252.
1968 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1969 - Use the Travis Homebrew addon to install packages on macOS during
1970 Travis CI. The package list is the same, but the Homebrew addon
1971 does not do a `brew update` by default. Implements ticket 27738.
1973 o Minor features (geoip):
1974 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
1975 Country database. Closes ticket 27991.
1977 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
1978 - Fix an integer overflow bug in our optimized 32-bit millisecond-
1979 difference algorithm for 32-bit Apple platforms. Previously, it
1980 would overflow when calculating the difference between two times
1981 more than 47 days apart. Fixes part of bug 27139; bugfix
1983 - Improve the precision of our 32-bit millisecond difference
1984 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
1985 bugfix on 0.3.4.1-alpha.
1986 - Relax the tolerance on the mainloop/update_time_jumps test when
1987 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
1990 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
1991 - Avoid undefined behavior in an end-of-string check when parsing
1992 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1995 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
1996 - Only install the necessary mingw packages during our appveyor
1997 builds. This change makes the build a little faster, and prevents
1998 a conflict with a preinstalled mingw openssl that appveyor now
1999 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2001 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2002 - Rewrite our assertion macros so that they no longer suppress the
2003 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2005 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2006 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2007 27464; bugfix on 0.3.4.1-alpha.
2009 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2010 - Log additional info when we get a relay that shares an ed25519 ID
2011 with a different relay, instead making a BUG() warning. Fixes bug
2012 27800; bugfix on 0.3.2.1-alpha.
2014 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2015 - Avoid a double-close when shutting down a stalled directory
2016 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2018 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2019 - Fix a bug warning when closing an HTTP tunnel connection due to an
2020 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2023 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2024 - Ensure circuitmux queues are empty before scheduling or sending
2025 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2027 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2028 - When the onion service directory can't be created or has the wrong
2029 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2032 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2033 - Close all SOCKS request (for the same .onion) if the newly fetched
2034 descriptor is unusable. Before that, we would close only the first
2035 one leaving the other hanging and let to time out by themselves.
2036 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2038 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2039 - When selecting a v3 rendezvous point, don't only look at the
2040 protover, but also check whether the curve25519 onion key is
2041 present. This way we avoid picking a relay that supports the v3
2042 rendezvous but for which we don't have the microdescriptor. Fixes
2043 bug 27797; bugfix on 0.3.2.1-alpha.
2045 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2046 - Reject protocol names containing bytes other than alphanumeric
2047 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2050 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2051 - Compute protover votes correctly in the rust version of the
2052 protover code. Previously, the protover rewrite in 24031 allowed
2053 repeated votes from the same voter for the same protocol version
2054 to be counted multiple times in protover_compute_vote(). Fixes bug
2055 27649; bugfix on 0.3.3.5-rc.
2056 - Reject protover names that contain invalid characters. Fixes bug
2057 27687; bugfix on 0.3.3.1-alpha.
2059 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2060 - protover_all_supported() would attempt to allocate up to 16GB on
2061 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2062 bugfix on 0.3.3.5-rc.
2064 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2065 - Fix an API mismatch in the rust implementation of
2066 protover_compute_vote(). This bug could have caused crashes on any
2067 directory authorities running Tor with Rust (which we do not yet
2068 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2070 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2071 - Fix a potential null dereference in protover_all_supported(). Add
2072 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2073 - Return a string that can be safely freed by C code, not one
2074 created by the rust allocator, in protover_all_supported(). Fixes
2075 bug 27740; bugfix on 0.3.3.1-alpha.
2077 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2078 - If a unit test running in a subprocess exits abnormally or with a
2079 nonzero status code, treat the test as having failed, even if the
2080 test reported success. Without this fix, memory leaks don't cause
2081 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2082 bugfix on 0.2.2.4-alpha.
2084 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2085 - Make the hs_service tests use the same time source when creating
2086 the introduction point and when testing it. Now tests work better
2087 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2090 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2091 - Treat backtrace test failures as expected on BSD-derived systems
2092 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2093 (FreeBSD failures have been treated as expected since 18204 in
2094 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2097 Changes in version 0.3.5.3-alpha - 2018-10-17
2098 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
2099 versions. One important fix for relays addresses a problem with rate-
2100 limiting code from back in 0.3.4.x: If the fix works out, we'll be
2101 backporting it soon. This release is still an alpha, but we hope it's
2102 getting closer and closer to stability.
2104 o Major features (onion services):
2105 - Version 3 onion services can now use the per-service
2106 HiddenServiceExportCircuitID option to differentiate client
2107 circuits. It communicates with the service by using the HAProxy
2108 protocol to assign virtual IP addresses to inbound client
2109 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
2111 o Major bugfixes (compilation):
2112 - Fix compilation on ARM (and other less-used CPUs) when compiling
2113 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2115 o Major bugfixes (initialization, crash):
2116 - Fix an assertion crash that would stop Tor from starting up if it
2117 tried to activate a periodic event too early. Fixes bug 27861;
2118 bugfix on 0.3.5.1-alpha.
2120 o Major bugfixes (mainloop, bootstrap):
2121 - Make sure Tor bootstraps and works properly if only the
2122 ControlPort is set. Prior to this fix, Tor would only bootstrap
2123 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2124 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2126 o Major bugfixes (relay):
2127 - When our write bandwidth limit is exhausted, stop writing on the
2128 connection. Previously, we had a typo in the code that would make
2129 us stop reading instead, leading to relay connections being stuck
2130 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2133 o Minor features (continuous integration):
2134 - Use the Travis Homebrew addon to install packages on macOS during
2135 Travis CI. The package list is the same, but the Homebrew addon
2136 does not do a `brew update` by default. Implements ticket 27738.
2137 - Report what program produced the mysterious core file that we
2138 occasionally see on Travis CI during make distcheck. Closes
2141 o Minor features (geoip):
2142 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2143 Country database. Closes ticket 27991.
2145 o Minor bugfixes (code safety):
2146 - Rewrite our assertion macros so that they no longer suppress the
2147 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2150 o Minor bugfixes (compilation):
2151 - Compile the ed25519-donna code with a correct declaration of
2152 crypto_strongest_rand(). Previously, we built it with one type,
2153 but linked it against another in the unit tests, which caused
2154 compilation failures with LTO enabled. This could have caused
2155 other undefined behavior in the tests. Fixes bug 27728; bugfix
2158 o Minor bugfixes (compilation, netbsd):
2159 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
2162 o Minor bugfixes (continuous integration, appveyor):
2163 - Install only the necessary mingw packages during our appveyor
2164 builds. This change makes the build a little faster, and prevents
2165 a conflict with a preinstalled mingw openssl that appveyor now
2166 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2168 o Minor bugfixes (directory permissions):
2169 - When a user requests a group-readable DataDirectory, give it to
2170 them. Previously, when the DataDirectory and the CacheDirectory
2171 were the same, the default setting (0) for
2172 CacheDirectoryGroupReadable would override the setting for
2173 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2176 o Minor bugfixes (memory leaks):
2177 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2178 bug 27893; bugfix on 0.3.2.1-alpha.
2180 o Minor bugfixes (networking):
2181 - In retry_listeners_ports(), make sure that we're removing a member
2182 of old_conns smartlist at most once. Fixes bug 27808; bugfix
2184 - Refrain from attempting socket rebinding when old and new
2185 listeners are in different address families. Fixes bug 27928;
2186 bugfix on 0.3.5.1-alpha.
2188 o Minor bugfixes (onion service v3):
2189 - Stop dumping a stack trace when trying to connect to an intro
2190 point without having a descriptor for it. Fixes bug 27774; bugfix
2192 - Don't warn so loudly when Tor is unable to decode an onion
2193 descriptor. This can now happen as a normal use case if a client
2194 gets a descriptor with client authorization but the client is not
2195 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
2196 - When selecting a v3 rendezvous point, don't only look at the
2197 protover, but also check whether the curve25519 onion key is
2198 present. This way we avoid picking a relay that supports the v3
2199 rendezvous but for which we don't have the microdescriptor. Fixes
2200 bug 27797; bugfix on 0.3.2.1-alpha.
2202 o Minor bugfixes (protover):
2203 - Reject protocol names containing bytes other than alphanumeric
2204 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2207 o Minor bugfixes (testing):
2208 - Make the hs_service tests use the same time source when creating
2209 the introduction point and when testing it. Now tests work better
2210 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2212 - In test_rebind.py, check if the Python version is in the supported
2213 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
2215 o Code simplification and refactoring:
2216 - Divide more large Tor source files -- especially ones that span
2217 multiple areas of functionality -- into smaller parts, including
2218 onion.c and main.c. Closes ticket 26747.
2219 - Divide the "routerparse.c" module into separate modules for each
2220 group of parsed objects. Closes ticket 27924.
2221 - Move protover_rust.c to the same place protover.c was moved to.
2222 Closes ticket 27814.
2223 - Split directory.c into separate pieces for client, server, and
2224 common functionality. Closes ticket 26744.
2225 - Split the non-statistics-related parts from the rephist.c and
2226 geoip.c modules. Closes ticket 27892.
2227 - Split the router.c file into relay-only and shared components, to
2228 help with future modularization. Closes ticket 27864.
2231 - In the tor-resolve(1) manpage, fix the reference to socks-
2232 extensions.txt by adding a web URL. Resolves ticket 27853.
2233 - Mention that we require Python to be 2.7 or newer for some
2234 integration tests that we ship with Tor. Resolves ticket 27677.
2237 Changes in version 0.3.5.2-alpha - 2018-09-21
2238 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
2239 that made Tor think it had run out of sockets. Anybody running a relay
2240 or an onion service on 0.3.5.1-alpha should upgrade.
2242 o Major bugfixes (relay bandwidth statistics):
2243 - When we close relayed circuits, report the data in the circuit
2244 queues as being written in our relay bandwidth stats. This
2245 mitigates guard discovery and other attacks that close circuits
2246 for the explicit purpose of noticing this discrepancy in
2247 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
2249 o Major bugfixes (socket accounting):
2250 - In our socket accounting code, count a socket as closed even when
2251 it is closed indirectly by the TLS layer. Previously, we would
2252 count these sockets as still in use, and incorrectly believe that
2253 we had run out of sockets. Fixes bug 27795; bugfix
2256 o Minor bugfixes (32-bit OSX and iOS, timing):
2257 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2258 difference algorithm for 32-bit Apple platforms. Previously, it
2259 would overflow when calculating the difference between two times
2260 more than 47 days apart. Fixes part of bug 27139; bugfix
2262 - Improve the precision of our 32-bit millisecond difference
2263 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2264 bugfix on 0.3.4.1-alpha.
2265 - Relax the tolerance on the mainloop/update_time_jumps test when
2266 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2269 o Minor bugfixes (onion service v3):
2270 - Close all SOCKS request (for the same .onion) if the newly fetched
2271 descriptor is unusable. Before that, we would close only the first
2272 one leaving the other hanging and let to time out by themselves.
2273 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2275 o Minor bugfixes (memory leak):
2276 - Fix an unlikely memory leak when trying to read a private key from
2277 a ridiculously large file. Fixes bug 27764; bugfix on
2278 0.3.5.1-alpha. This is CID 1439488.
2280 o Minor bugfixes (NSS):
2281 - Correctly detect failure to open a dummy TCP socket when stealing
2282 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
2285 o Minor bugfixes (rust):
2286 - protover_all_supported() would attempt to allocate up to 16GB on
2287 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2288 bugfix on 0.3.3.5-rc.
2290 o Minor bugfixes (testing):
2291 - Revise the "conditionvar_timeout" test so that it succeeds even on
2292 heavily loaded systems where the test threads are not scheduled
2293 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2295 o Code simplification and refactoring:
2296 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2297 Closes ticket 27799.
2300 Changes in version 0.3.5.1-alpha - 2018-09-18
2301 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
2302 client authorization for modern (v3) onion services, improves
2303 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
2304 support for NSS in place of OpenSSL, and much more.
2306 o Major features (onion services, UI change):
2307 - For a newly created onion service, the default version is now 3.
2308 Tor still supports existing version 2 services, but the operator
2309 now needs to set "HiddenServiceVersion 2" in order to create a new
2310 version 2 service. For existing services, Tor now learns the
2311 version by reading the key file. Closes ticket 27215.
2313 o Major features (relay, UI change):
2314 - Relays no longer run as exits by default. If the "ExitRelay"
2315 option is auto (or unset), and no exit policy is specified with
2316 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
2317 Previously in this case, we allowed exit traffic and logged a
2318 warning message. Closes ticket 21530. Patch by Neel Chauhan.
2319 - Tor now validates that the ContactInfo config option is valid UTF-
2320 8 when parsing torrc. Closes ticket 27428.
2322 o Major features (bootstrap):
2323 - Don't report directory progress until after a connection to a
2324 relay or bridge has succeeded. Previously, we'd report 80%
2325 progress based on cached directory information when we couldn't
2326 even connect to the network. Closes ticket 27169.
2328 o Major features (new code layout):
2329 - Nearly all of Tor's source code has been moved around into more
2330 logical places. The "common" directory is now divided into a set
2331 of libraries in "lib", and files in the "or" directory have been
2332 split into "core" (logic absolutely needed for onion routing),
2333 "feature" (independent modules in Tor), and "app" (to configure
2334 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
2335 more information. Closes ticket 26481.
2337 This refactoring is not complete: although the libraries have been
2338 refactored to be acyclic, the main body of Tor is still too
2339 interconnected. We will attempt to improve this in the future.
2341 o Major features (onion services v3):
2342 - Implement onion service client authorization at the descriptor
2343 level: only authorized clients can decrypt a service's descriptor
2344 to find out how to contact it. A new torrc option was added to
2345 control this client side: ClientOnionAuthDir <path>. On the
2346 service side, if the "authorized_clients/" directory exists in the
2347 onion service directory path, client configurations are read from
2348 the files within. See the manpage for more details. Closes ticket
2349 27547. Patch done by Suphanat Chunhapanya (haxxpop).
2350 - Improve revision counter generation in next-gen onion services.
2351 Onion services can now scale by hosting multiple instances on
2352 different hosts without synchronization between them, which was
2353 previously impossible because descriptors would get rejected by
2354 HSDirs. Addresses ticket 25552.
2356 o Major features (portability, cryptography, experimental, TLS):
2357 - Tor now has the option to compile with the NSS library instead of
2358 OpenSSL. This feature is experimental, and we expect that bugs may
2359 remain. It is mainly intended for environments where Tor's
2360 performance is not CPU-bound, and where NSS is already known to be
2361 installed. To try it out, configure Tor with the --enable-nss
2362 flag. Closes tickets 26631, 26815, and 26816.
2364 If you are experimenting with this option and using an old cached
2365 consensus, Tor may fail to start. To solve this, delete your
2366 "cached-consensus" and "cached-microdesc-consensus" files,
2367 (if present), and restart Tor.
2369 o Major bugfixes (directory authority):
2370 - Actually check that the address we get from DirAuthority
2371 configuration line is valid IPv4. Explicitly disallow DirAuthority
2372 address to be a DNS hostname. Fixes bug 26488; bugfix
2375 o Major bugfixes (restart-in-process):
2376 - Fix a use-after-free error that could be caused by passing Tor an
2377 impossible set of options that would fail during options_act().
2378 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2380 o Minor features (admin tools):
2381 - Add a new --key-expiration option to print the expiration date of
2382 the signing cert in an ed25519_signing_cert file. Resolves
2385 o Minor features (build):
2386 - If you pass the "--enable-pic" option to configure, Tor will try
2387 to tell the compiler to build position-independent code suitable
2388 to link into a dynamic library. (The default remains -fPIE, for
2389 code suitable for a relocatable executable.) Closes ticket 23846.
2391 o Minor features (code correctness, testing):
2392 - Tor's build process now includes a "check-includes" make target to
2393 verify that no module of Tor relies on any headers from a higher-
2394 level module. We hope to use this feature over time to help
2395 refactor our codebase. Closes ticket 26447.
2397 o Minor features (code layout):
2398 - We have a new "lowest-level" error-handling API for use by code
2399 invoked from within the logging module. With this interface, the
2400 logging code is no longer at risk of calling into itself if a
2401 failure occurs while it is trying to log something. Closes
2404 o Minor features (compilation):
2405 - Tor's configure script now supports a --with-malloc= option to
2406 select your malloc implementation. Supported options are
2407 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
2408 default). Addresses part of ticket 20424. Based on a patch from
2411 o Minor features (config):
2412 - The "auto" keyword in torrc is now case-insensitive. Closes
2415 o Minor features (continuous integration):
2416 - Don't do a distcheck with --disable-module-dirauth in Travis.
2417 Implements ticket 27252.
2418 - Install libcap-dev and libseccomp2-dev so these optional
2419 dependencies get tested on Travis CI. Closes ticket 26560.
2420 - Only run one online rust build in Travis, to reduce network
2421 errors. Skip offline rust builds on Travis for Linux gcc, because
2422 they're redundant. Implements ticket 27252.
2423 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2424 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2425 Linux with default settings, because all the non-default builds
2426 use gcc on Linux. Implements ticket 27252.
2428 o Minor features (controller):
2429 - Emit CIRC_BW events as soon as we detect that we processed an
2430 invalid or otherwise dropped cell on a circuit. This allows
2431 vanguards and other controllers to react more quickly to dropped
2432 cells. Closes ticket 27678.
2433 - For purposes of CIRC_BW-based dropped cell detection, track half-
2434 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2435 bias check cells to arrive without counting it as dropped until
2436 either the END arrives, or the windows are empty. Closes
2438 - Implement a 'GETINFO md/all' controller command to enable getting
2439 all known microdescriptors. Closes ticket 8323.
2440 - The GETINFO command now support an "uptime" argument, to return
2441 Tor's uptime in seconds. Closes ticket 25132.
2443 o Minor features (denial-of-service avoidance):
2444 - Make our OOM handler aware of the DNS cache so that it doesn't
2445 fill up the memory. This check is important for our DoS mitigation
2446 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2448 o Minor features (development):
2449 - Tor's makefile now supports running the "clippy" Rust style tool
2450 on our Rust code. Closes ticket 22156.
2452 o Minor features (directory authority):
2453 - There is no longer an artificial upper limit on the length of
2454 bandwidth lines. Closes ticket 26223.
2455 - When a bandwidth file is used to obtain the bandwidth measurements,
2456 include this bandwidth file headers in the votes. Closes
2458 - Improved support for networks with only a single authority or a
2459 single fallback directory. Patch from Gabriel Somlo. Closes
2462 o Minor features (embedding API):
2463 - The Tor controller API now supports a function to launch Tor with
2464 a preconstructed owning controller FD, so that embedding
2465 applications don't need to manage controller ports and
2466 authentication. Closes ticket 24204.
2467 - The Tor controller API now has a function that returns the name
2468 and version of the backend implementing the API. Closes
2471 o Minor features (geoip):
2472 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2473 Country database. Closes ticket 27631.
2475 o Minor features (memory management):
2476 - Get Libevent to use the same memory allocator as Tor, by calling
2477 event_set_mem_functions() during initialization. Resolves
2480 o Minor features (memory usage):
2481 - When not using them, store legacy TAP public onion keys in DER-
2482 encoded format, rather than as expanded public keys. This should
2483 save several megabytes on typical clients. Closes ticket 27246.
2485 o Minor features (OpenSSL):
2486 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2487 than our own. Resolves ticket 19979.
2489 o Minor features (Rust, code quality):
2490 - Improve rust code quality in the rust protover implementation by
2491 making it more idiomatic. Includes changing an internal API to
2492 take &str instead of &String. Closes ticket 26492.
2494 o Minor features (testing):
2495 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2496 chutney. Implements ticket 27211.
2498 o Minor features (tor-resolve):
2499 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2500 Side-effect of the refactoring for ticket 26526.
2502 o Minor features (UI):
2503 - Log each included configuration file or directory as we read it,
2504 to provide more visibility about where Tor is reading from. Patch
2505 from Unto Sten; closes ticket 27186.
2506 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2507 Closes ticket 26703.
2509 o Minor bugfixes (bootstrap):
2510 - Try harder to get descriptors in non-exit test networks, by using
2511 the mid weight for the third hop when there are no exits. Fixes
2512 bug 27237; bugfix on 0.2.6.2-alpha.
2514 o Minor bugfixes (C correctness):
2515 - Avoid casting smartlist index to int implicitly, as it may trigger
2516 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2517 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2518 - Use time_t for all values in
2519 predicted_ports_prediction_time_remaining(). Rework the code that
2520 computes difference between durations/timestamps. Fixes bug 27165;
2521 bugfix on 0.3.1.1-alpha.
2523 o Minor bugfixes (client, memory usage):
2524 - When not running as a directory cache, there is no need to store
2525 the text of the current consensus networkstatus in RAM.
2526 Previously, however, clients would store it anyway, at a cost of
2527 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2530 o Minor bugfixes (client, reachableaddresses):
2531 - Instead of adding a "reject *:*" line to ReachableAddresses when
2532 loading the configuration, add one to the policy after parsing it
2533 in parse_reachable_addresses(). This prevents extra "reject *.*"
2534 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2535 0.1.1.5-alpha. Patch by Neel Chauhan.
2537 o Minor bugfixes (code quality):
2538 - Rename sandbox_getaddrinfo() and other functions to no longer
2539 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2540 bugfix on 0.2.7.1-alpha.
2542 o Minor bugfixes (configuration, Onion Services):
2543 - In rend_service_parse_port_config(), disallow any input to remain
2544 after address-port pair was parsed. This will catch address and
2545 port being whitespace-separated by mistake of the user. Fixes bug
2546 27044; bugfix on 0.2.9.10.
2548 o Minor bugfixes (continuous integration):
2549 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2550 27464; bugfix on 0.3.4.1-alpha.
2552 o Minor bugfixes (controller):
2553 - Consider all routerinfo errors other than "not a server" to be
2554 transient for the purpose of "GETINFO exit-policy/*" controller
2555 request. Print stacktrace in the unlikely case of failing to
2556 recompute routerinfo digest. Fixes bug 27034; bugfix
2559 o Minor bugfixes (directory connection shutdown):
2560 - Avoid a double-close when shutting down a stalled directory
2561 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2563 o Minor bugfixes (HTTP tunnel):
2564 - Fix a bug warning when closing an HTTP tunnel connection due to an
2565 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2568 o Minor bugfixes (ipv6):
2569 - In addrs_in_same_network_family(), we choose the subnet size based
2570 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2571 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2572 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2574 o Minor bugfixes (logging):
2575 - As a precaution, do an early return from log_addr_has_changed() if
2576 Tor is running as client. Also, log a stack trace for debugging as
2577 this function should only be called when Tor runs as server. Fixes
2578 bug 26892; bugfix on 0.1.1.9-alpha.
2579 - Refrain from mentioning bug 21018 in the logs, as it is already
2580 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2582 o Minor bugfixes (logging, documentation):
2583 - When SafeLogging is enabled, scrub IP address in
2584 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2585 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2586 bug 26882; bugfix on 0.2.4.10-alpha.
2588 o Minor bugfixes (netflow padding):
2589 - Ensure circuitmux queues are empty before scheduling or sending
2590 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2592 o Minor bugfixes (onion service v2):
2593 - Log at level "info", not "warning", in the case that we do not
2594 have a consensus when a .onion request comes in. This can happen
2595 normally while bootstrapping. Fixes bug 27040; bugfix
2598 o Minor bugfixes (onion service v3):
2599 - When the onion service directory can't be created or has the wrong
2600 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2603 o Minor bugfixes (OS compatibility):
2604 - Properly handle configuration changes that move a listener to/from
2605 wildcard IP address. If the first attempt to bind a socket fails,
2606 close the old listener and try binding the socket again. Fixes bug
2607 17873; bugfix on 0.0.8pre-1.
2609 o Minor bugfixes (performance)::
2610 - Rework node_is_a_configured_bridge() to no longer call
2611 node_get_all_orports(), which was performing too many memory
2612 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2614 o Minor bugfixes (relay statistics):
2615 - Update relay descriptor on bandwidth changes only when the uptime
2616 is smaller than 24h, in order to reduce the efficiency of guard
2617 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2619 o Minor bugfixes (relays):
2620 - Consider the fact that we'll be making direct connections to our
2621 entry and guard nodes when computing the fraction of nodes that
2622 have their descriptors. Also, if we are using bridges and there is
2623 at least one bridge with a full descriptor, treat the fraction of
2624 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2625 Patch by Neel Chauhan.
2626 - Update the message logged on relays when DirCache is disabled.
2627 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2628 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2630 o Minor bugfixes (rust, protover):
2631 - Compute protover votes correctly in the rust version of the
2632 protover code. Previously, the protover rewrite in 24031 allowed
2633 repeated votes from the same voter for the same protocol version
2634 to be counted multiple times in protover_compute_vote(). Fixes bug
2635 27649; bugfix on 0.3.3.5-rc.
2636 - Reject protover names that contain invalid characters. Fixes bug
2637 27687; bugfix on 0.3.3.1-alpha.
2639 o Minor bugfixes (testing):
2640 - Fix two unit tests to work when HOME environment variable is not
2641 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2642 - If a unit test running in a subprocess exits abnormally or with a
2643 nonzero status code, treat the test as having failed, even if the
2644 test reported success. Without this fix, memory leaks don't cause
2645 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2646 bugfix on 0.2.2.4-alpha.
2647 - When logging a version mismatch in our openssl_version tests,
2648 report the actual offending version strings. Fixes bug 26152;
2649 bugfix on 0.2.9.1-alpha.
2650 - Fix forking tests on Windows when there is a space somewhere in
2651 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2653 o Code simplification and refactoring:
2654 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2655 longer needed. Closes ticket 26502.
2656 - Include paths to header files within Tor are now qualified by
2657 directory within the top-level src directory.
2658 - Many structures have been removed from the centralized "or.h"
2659 header, and moved into their own headers. This will allow us to
2660 reduce the number of places in the code that rely on each
2661 structure's contents and layout. Closes ticket 26383.
2662 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2663 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2664 removed as part of the 26481 refactor. Closes ticket 27467.
2665 - Rework Tor SOCKS server code to use Trunnel and benefit from
2666 autogenerated functions for parsing and generating SOCKS wire
2667 format. New implementation is cleaner, more maintainable and
2668 should be less prone to heartbleed-style vulnerabilities.
2669 Implements a significant fraction of ticket 3569.
2670 - Split sampled_guards_update_from_consensus() and
2671 select_entry_guard_for_circuit() into subfunctions. In
2672 entry_guards_update_primary() unite three smartlist enumerations
2673 into one and move smartlist comparison code out of the function.
2674 Closes ticket 21349.
2675 - Tor now assumes that you have standards-conformant stdint.h and
2676 inttypes.h headers when compiling. Closes ticket 26626.
2677 - Unify our bloom filter logic. Previously we had two copies of this
2678 code: one for routerlist filtering, and one for address set
2679 calculations. Closes ticket 26510.
2680 - Use the simpler strcmpstart() helper in
2681 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2683 - Utility functions that can perform a DNS lookup are now wholly
2684 separated from those that can't, in separate headers and C
2685 modules. Closes ticket 26526.
2688 - Copy paragraph and URL to Tor's code of conduct document from
2689 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2690 - Remove old instructions from INSTALL document. Closes ticket 26588.
2691 - Warn users that they should not include MyFamily line(s) in their
2692 torrc when running Tor bridge. Closes ticket 26908.
2695 - Tor no longer supports building with the dmalloc library. For
2696 debugging memory issues, we suggest using gperftools or msan
2697 instead. Closes ticket 26426.
2698 - Tor no longer attempts to run on Windows environments without the
2699 GetAdaptersAddresses() function. This function has existed since
2700 Windows XP, which is itself already older than we support.
2701 - Remove Tor2web functionality for version 2 onion services. The
2702 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2703 (This feature was never shipped in vanilla Tor and it was only
2704 possible to use this feature by building the support at compile
2705 time. Tor2webMode is not implemented for version 3 onion services.)
2706 Closes ticket 26367.
2709 Changes in version 0.2.9.17 - 2018-09-10
2710 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
2712 o Minor features (compatibility, backport from 0.3.4.8):
2713 - Tell OpenSSL to maintain backward compatibility with previous
2714 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2715 ciphers are disabled by default. Closes ticket 27344.
2717 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2718 - Enable macOS builds in our Travis CI configuration. Closes
2720 - Install libcap-dev and libseccomp2-dev so these optional
2721 dependencies get tested on Travis CI. Closes ticket 26560.
2722 - Run asciidoc during Travis CI. Implements ticket 27087.
2723 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2725 o Minor features (geoip):
2726 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2727 Country database. Closes ticket 27089.
2729 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2730 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2731 tell the compiler not to include the system malloc implementation.
2732 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2734 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2735 - Silence a spurious compiler warning on the GetAdaptersAddresses
2736 function pointer cast. This issue is already fixed by 26481 in
2737 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2738 bugfix on 0.2.3.11-alpha.
2739 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2740 supported, and always fails. Some compilers warn about the
2741 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2744 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2745 - Don't link or search for pthreads when building for Windows, even
2746 if we are using build environment (like mingw) that provides a
2747 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2749 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2750 - Skip a pair of unreliable key generation tests on Windows, until
2751 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2752 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2754 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2755 - Pass the module flags to distcheck configure, and log the flags
2756 before running configure. (Backported to 0.2.9 and later as a
2757 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2759 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2760 - When a Travis build fails, and showing a log fails, keep trying to
2761 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2762 - When we use echo in Travis, don't pass a --flag as the first
2763 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2765 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2766 - When voting for recommended versions, make sure that all of the
2767 versions are well-formed and parsable. Fixes bug 26485; bugfix
2770 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2771 - Fix a bug in out sandboxing rules for the openat() syscall.
2772 Previously, no openat() call would be permitted, which would break
2773 filesystem operations on recent glibc versions. Fixes bug 25440;
2774 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2776 o Minor bugfixes (onion services, backport from 0.3.4.8):
2777 - Silence a spurious compiler warning in
2778 rend_client_send_introduction(). Fixes bug 27463; bugfix
2781 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2782 - Log a protocol warning when single onion services or Tor2web clients
2783 fail to authenticate direct connections to relays.
2784 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2786 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2787 - Disable core dumps in test_bt.sh, to avoid failures in "make
2788 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2790 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2791 - Before running make test-network-all, delete old logs and test
2792 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2795 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2796 - Our "tortls/cert_matches_key" unit test no longer relies on
2797 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2798 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2799 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2801 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2802 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2803 27185; bugfix on 0.2.2.2-alpha.
2806 Changes in version 0.3.2.12 - 2018-09-10
2807 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
2809 o Minor features (compatibility, backport from 0.3.4.8):
2810 - Tell OpenSSL to maintain backward compatibility with previous
2811 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2812 ciphers are disabled by default. Closes ticket 27344.
2814 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2815 - Enable macOS builds in our Travis CI configuration. Closes
2817 - Install libcap-dev and libseccomp2-dev so these optional
2818 dependencies get tested on Travis CI. Closes ticket 26560.
2819 - Run asciidoc during Travis CI. Implements ticket 27087.
2820 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2822 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2823 - Use cargo cache in our Travis CI configuration. Closes
2826 o Minor features (controller, backport from 0.3.4.6-rc):
2827 - The control port now exposes the list of HTTPTunnelPorts and
2828 ExtOrPorts via GETINFO net/listeners/httptunnel and
2829 net/listeners/extor respectively. Closes ticket 26647.
2831 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2832 - Authorities no longer vote to make the subprotocol version
2833 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2834 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2836 o Minor features (geoip):
2837 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2838 Country database. Closes ticket 27089.
2840 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2841 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2842 tell the compiler not to include the system malloc implementation.
2843 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2844 - Don't try to use a pragma to temporarily disable the
2845 -Wunused-const-variable warning if the compiler doesn't support
2846 it. Fixes bug 26785; bugfix on 0.3.2.11.
2848 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2849 - Silence a spurious compiler warning on the GetAdaptersAddresses
2850 function pointer cast. This issue is already fixed by 26481 in
2851 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
2852 bugfix on 0.2.3.11-alpha.
2853 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
2854 supported, and always fails. Some compilers warn about the
2855 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
2858 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
2859 - Don't link or search for pthreads when building for Windows, even
2860 if we are using build environment (like mingw) that provides a
2861 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
2863 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
2864 - Skip a pair of unreliable key generation tests on Windows, until
2865 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
2866 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
2868 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
2869 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
2870 - Pass the module flags to distcheck configure, and log the flags
2871 before running configure. (Backported to 0.2.9 and later as a
2872 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
2874 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
2875 - When a Travis build fails, and showing a log fails, keep trying to
2876 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
2877 - When we use echo in Travis, don't pass a --flag as the first
2878 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
2880 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
2881 - When voting for recommended versions, make sure that all of the
2882 versions are well-formed and parsable. Fixes bug 26485; bugfix
2885 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
2886 - Fix a bug in out sandboxing rules for the openat() syscall.
2887 Previously, no openat() call would be permitted, which would break
2888 filesystem operations on recent glibc versions. Fixes bug 25440;
2889 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
2891 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
2892 - Improve the log message when connection initiators fail to
2893 authenticate direct connections to relays. Fixes bug 26927; bugfix
2896 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
2897 - Fix bug that causes services to not ever rotate their descriptors
2898 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
2901 o Minor bugfixes (onion services, backport from 0.3.4.8):
2902 - Silence a spurious compiler warning in
2903 rend_client_send_introduction(). Fixes bug 27463; bugfix
2906 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
2907 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
2909 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
2910 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
2911 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
2912 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
2914 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
2915 - Log a protocol warning when single onion services or Tor2web clients
2916 fail to authenticate direct connections to relays.
2917 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
2919 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
2920 - Disable core dumps in test_bt.sh, to avoid failures in "make
2921 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
2923 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
2924 - When running make test-network-all, use the mixed+hs-v2 network.
2925 (A previous fix to chutney removed v3 onion services from the
2926 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
2927 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
2928 - Before running make test-network-all, delete old logs and test
2929 result files, to avoid spurious failures. Fixes bug 27295; bugfix
2932 o Minor bugfixes (testing, openssl compatibility):
2933 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
2934 internals. Previously, it relied on unsupported OpenSSL behavior in
2935 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
2936 bugfix on 0.2.5.1-alpha.
2938 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
2939 - Our "tortls/cert_matches_key" unit test no longer relies on
2940 OpenSSL internals. Previously, it relied on unsupported OpenSSL
2941 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
2942 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
2944 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
2945 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
2946 27185; bugfix on 0.2.2.2-alpha.
2949 Changes in version 0.3.3.10 - 2018-09-10
2950 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
2952 o Minor features (bug workaround, backport from 0.3.4.7-rc):
2953 - Compile correctly on systems that provide the C11 stdatomic.h
2954 header, but where C11 atomic functions don't actually compile.
2955 Closes ticket 26779; workaround for Debian issue 903709.
2957 o Minor features (compatibility, backport from 0.3.4.8):
2958 - Tell OpenSSL to maintain backward compatibility with previous
2959 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
2960 ciphers are disabled by default. Closes ticket 27344.
2962 o Minor features (continuous integration, backport from 0.3.4.7-rc):
2963 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
2964 - Enable macOS builds in our Travis CI configuration. Closes
2966 - Install libcap-dev and libseccomp2-dev so these optional
2967 dependencies get tested on Travis CI. Closes ticket 26560.
2968 - Run asciidoc during Travis CI. Implements ticket 27087.
2969 - Use ccache in our Travis CI configuration. Closes ticket 26952.
2971 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
2972 - Use cargo cache in our Travis CI configuration. Closes
2975 o Minor features (controller, backport from 0.3.4.6-rc):
2976 - The control port now exposes the list of HTTPTunnelPorts and
2977 ExtOrPorts via GETINFO net/listeners/httptunnel and
2978 net/listeners/extor respectively. Closes ticket 26647.
2980 o Minor features (directory authorities, backport from 0.3.4.7-rc):
2981 - Authorities no longer vote to make the subprotocol version
2982 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
2983 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
2985 o Minor features (geoip):
2986 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
2987 Country database. Closes ticket 27089.
2989 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
2990 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
2991 tell the compiler not to include the system malloc implementation.
2992 Fixes bug 20424; bugfix on 0.2.0.20-rc.
2993 - Don't try to use a pragma to temporarily disable the
2994 -Wunused-const-variable warning if the compiler doesn't support
2995 it. Fixes bug 26785; bugfix on 0.3.2.11.
2997 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
2998 - Silence a spurious compiler warning on the GetAdaptersAddresses
2999 function pointer cast. This issue is already fixed by 26481 in
3000 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3001 bugfix on 0.2.3.11-alpha.
3002 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3003 supported, and always fails. Some compilers warn about the
3004 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3007 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3008 - Don't link or search for pthreads when building for Windows, even
3009 if we are using build environment (like mingw) that provides a
3010 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3012 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3013 - Skip a pair of unreliable key generation tests on Windows, until
3014 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3015 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3017 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3018 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3019 - Pass the module flags to distcheck configure, and log the flags
3020 before running configure. (Backported to 0.2.9 and later as a
3021 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3023 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3024 - When a Travis build fails, and showing a log fails, keep trying to
3025 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3026 - When we use echo in Travis, don't pass a --flag as the first
3027 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3029 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3030 - When voting for recommended versions, make sure that all of the
3031 versions are well-formed and parsable. Fixes bug 26485; bugfix
3034 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
3035 - Always call tor_free_all() when leaving tor_run_main(). When we
3036 did not, restarting tor in-process would cause an assertion
3037 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3039 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3040 - Fix a bug in our sandboxing rules for the openat() syscall.
3041 Previously, no openat() call would be permitted, which would break
3042 filesystem operations on recent glibc versions. Fixes bug 25440;
3043 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3045 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3046 - Improve the log message when connection initiators fail to
3047 authenticate direct connections to relays. Fixes bug 26927; bugfix
3050 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3051 - Fix bug that causes services to not ever rotate their descriptors
3052 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3055 o Minor bugfixes (onion services, backport from 0.3.4.8):
3056 - Silence a spurious compiler warning in
3057 rend_client_send_introduction(). Fixes bug 27463; bugfix
3060 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
3061 - Work around two different bugs in the OS X 10.10 and later SDKs
3062 that would prevent us from successfully targeting earlier versions
3063 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3065 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
3066 - Fix compilation of the unit tests on GNU/Hurd, which does not
3067 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3070 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3071 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3073 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3074 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3075 - Protover parsing was accepting the presence of whitespace in
3076 version strings, which the C implementation would choke on, e.g.
3077 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3078 - Protover parsing was ignoring a 2nd hyphen and everything after
3079 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3081 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3082 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3083 - cd to ${abs_top_builddir}/src/rust before running cargo in
3084 src/test/test_rust.sh. This makes the working directory consistent
3085 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3087 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3088 - Log a protocol warning when single onion services or Tor2web clients
3089 fail to authenticate direct connections to relays.
3090 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3092 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3093 - Disable core dumps in test_bt.sh, to avoid failures in "make
3094 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3096 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3097 - When running make test-network-all, use the mixed+hs-v2 network.
3098 (A previous fix to chutney removed v3 onion services from the
3099 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3100 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3101 - Before running make test-network-all, delete old logs and test
3102 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3105 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3106 - Our "tortls/cert_matches_key" unit test no longer relies on
3107 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3108 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3109 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3111 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3112 - Stop sending ed25519 link specifiers in v3 onion service introduce
3113 cells and descriptors, when the rendezvous or introduction point
3114 doesn't support ed25519 link authentication. Fixes bug 26627;
3115 bugfix on 0.3.2.4-alpha.
3117 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3118 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3119 27185; bugfix on 0.2.2.2-alpha.
3122 Changes in version 0.3.4.8 - 2018-09-10
3123 Tor 0.3.4.8 is the first stable release in its series; it includes
3124 compilation and portability fixes.
3126 The Tor 0.3.4 series includes improvements for running Tor in
3127 low-power and embedded environments, which should help performance in
3128 general. We've begun work on better modularity, and included preliminary
3129 changes on the directory authority side to accommodate a new bandwidth
3130 measurement system. We've also integrated more continuous-integration
3131 systems into our development process, and made corresponding changes to
3132 Tor's testing infrastructure. Finally, we've continued to refine
3133 our anti-denial-of-service code.
3135 Below are the changes since 0.3.4.7-rc. For a complete list of changes
3136 since 0.3.3.9, see the ReleaseNotes file.
3138 o Minor features (compatibility):
3139 - Tell OpenSSL to maintain backward compatibility with previous
3140 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3141 ciphers are disabled by default. Closes ticket 27344.
3143 o Minor features (continuous integration):
3144 - Log the compiler path and version during Appveyor builds.
3145 Implements ticket 27449.
3146 - Show config.log and test-suite.log after failed Appveyor builds.
3147 Also upload the zipped full logs as a build artifact. Implements
3150 o Minor bugfixes (compilation):
3151 - Silence a spurious compiler warning on the GetAdaptersAddresses
3152 function pointer cast. This issue is already fixed by 26481 in
3153 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3154 bugfix on 0.2.3.11-alpha.
3155 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3156 supported, and always fails. Some compilers warn about the
3157 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3160 o Minor bugfixes (continuous integration):
3161 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
3162 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
3163 Executables compiled for 64-bit Windows with this version of gcc
3164 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
3165 27460; bugfix on 0.3.4.1-alpha.
3166 - When a Travis build fails, and showing a log fails, keep trying to
3167 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3168 - When we use echo in Travis, don't pass a --flag as the first
3169 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3171 o Minor bugfixes (onion services):
3172 - Silence a spurious compiler warning in
3173 rend_client_send_introduction(). Fixes bug 27463; bugfix
3176 o Minor bugfixes (testing, chutney):
3177 - When running make test-network-all, use the mixed+hs-v2 network.
3178 (A previous fix to chutney removed v3 onion services from the
3179 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3180 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3181 - Before running make test-network-all, delete old logs and test
3182 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3185 Changes in version 0.3.4.7-rc - 2018-08-24
3186 Tor 0.3.4.7-rc fixes several small compilation, portability, and
3187 correctness issues in previous versions of Tor. This version is a
3188 release candidate: if no serious bugs are found, we expect that the
3189 stable 0.3.4 release will be (almost) the same as this release.
3191 o Minor features (bug workaround):
3192 - Compile correctly on systems that provide the C11 stdatomic.h
3193 header, but where C11 atomic functions don't actually compile.
3194 Closes ticket 26779; workaround for Debian issue 903709.
3196 o Minor features (continuous integration):
3197 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3198 - Enable macOS builds in our Travis CI configuration. Closes
3200 - Install libcap-dev and libseccomp2-dev so these optional
3201 dependencies get tested on Travis CI. Closes ticket 26560.
3202 - Only post Appveyor IRC notifications when the build fails.
3203 Implements ticket 27275.
3204 - Run asciidoc during Travis CI. Implements ticket 27087.
3205 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3207 o Minor features (continuous integration, rust):
3208 - Use cargo cache in our Travis CI configuration. Closes
3211 o Minor features (directory authorities):
3212 - Authorities no longer vote to make the subprotocol version
3213 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3214 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3216 o Minor features (geoip):
3217 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3218 Country database. Closes ticket 27089.
3220 o Minor bugfixes (compilation, windows):
3221 - Don't link or search for pthreads when building for Windows, even
3222 if we are using build environment (like mingw) that provides a
3223 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3225 o Minor bugfixes (continuous integration):
3226 - Improve Appveyor CI IRC logging. Generate correct branches and
3227 URLs for pull requests and tags. Use unambiguous short commits.
3228 Fixes bug 26979; bugfix on master.
3229 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3230 - Pass the module flags to distcheck configure, and log the flags
3231 before running configure. (Backported to 0.2.9 and later as a
3232 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3234 o Minor bugfixes (in-process restart):
3235 - Always call tor_free_all() when leaving tor_run_main(). When we
3236 did not, restarting tor in-process would cause an assertion
3237 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3239 o Minor bugfixes (linux seccomp2 sandbox):
3240 - Fix a bug in out sandboxing rules for the openat() syscall.
3241 Previously, no openat() call would be permitted, which would break
3242 filesystem operations on recent glibc versions. Fixes bug 25440;
3243 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3245 o Minor bugfixes (onion services):
3246 - Fix bug that causes services to not ever rotate their descriptors
3247 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3250 o Minor bugfixes (portability):
3251 - Fix compilation of the unit tests on GNU/Hurd, which does not
3252 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3255 o Minor bugfixes (rust):
3256 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3258 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3259 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3260 - Protover parsing was accepting the presence of whitespace in
3261 version strings, which the C implementation would choke on, e.g.
3262 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3263 - Protover parsing was ignoring a 2nd hyphen and everything after
3264 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3266 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3267 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3268 - cd to ${abs_top_builddir}/src/rust before running cargo in
3269 src/test/test_rust.sh. This makes the working directory consistent
3270 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3272 o Minor bugfixes (testing, bootstrap):
3273 - When calculating bootstrap progress, check exit policies and the
3274 exit flag. Previously, Tor would only check the exit flag, which
3275 caused race conditions in small and fast networks like chutney.
3276 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3278 o Minor bugfixes (testing, openssl compatibility):
3279 - Our "tortls/cert_matches_key" unit test no longer relies on
3280 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3281 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3282 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3284 o Minor bugfixes (Windows, compilation):
3285 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3286 27185; bugfix on 0.2.2.2-alpha.
3289 Changes in version 0.3.4.6-rc - 2018-08-06
3290 Tor 0.3.4.6-rc fixes several small compilation, portability, and
3291 correctness issues in previous versions of Tor. This version is a
3292 release candidate: if no serious bugs are found, we expect that the
3293 stable 0.3.4 release will be (almost) the same as this release.
3295 o Major bugfixes (event scheduler):
3296 - When we enable a periodic event, schedule it in the event loop
3297 rather than running it immediately. Previously, we would re-run
3298 periodic events immediately in the middle of (for example)
3299 changing our options, with unpredictable effects. Fixes bug 27003;
3300 bugfix on 0.3.4.1-alpha.
3302 o Minor features (compilation):
3303 - When building Tor, prefer to use Python 3 over Python 2, and more
3304 recent (contemplated) versions over older ones. Closes
3306 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3307 tell the compiler not to include the system malloc implementation.
3308 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3309 - Don't try to use a pragma to temporarily disable the
3310 -Wunused-const-variable warning if the compiler doesn't support
3311 it. Fixes bug 26785; bugfix on 0.3.2.11.
3313 o Minor bugfixes (continuous integration):
3314 - Skip a pair of unreliable key generation tests on Windows, until
3315 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3316 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3318 o Minor features (controller):
3319 - The control port now exposes the list of HTTPTunnelPorts and
3320 ExtOrPorts via GETINFO net/listeners/httptunnel and
3321 net/listeners/extor respectively. Closes ticket 26647.
3323 o Minor bugfixes (directory authority):
3324 - When voting for recommended versions, make sure that all of the
3325 versions are well-formed and parsable. Fixes bug 26485; bugfix
3328 o Minor features (geoip):
3329 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3330 Country database. Closes ticket 26674.
3332 o Minor features (Rust, portability):
3333 - Rust cross-compilation is now supported. Closes ticket 25895.
3335 o Minor bugfixes (compilation):
3336 - Update build system so that tor builds again with --disable-unittests
3337 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
3338 - Fix a compilation warning on some versions of GCC when building
3339 code that calls routerinfo_get_my_routerinfo() twice, assuming
3340 that the second call will succeed if the first one did. Fixes bug
3341 26269; bugfix on 0.2.8.2-alpha.
3343 o Minor bugfixes (controller):
3344 - Report the port correctly when a port is configured to bind to
3345 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3346 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3347 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3348 on 0.3.3.1-alpha. Patch by "akwizgran".
3350 o Minor bugfixes (correctness, flow control):
3351 - Upon receiving a stream-level SENDME cell, verify that our window
3352 has not grown too large. Fixes bug 26214; bugfix on svn
3355 o Minor bugfixes (memory, correctness):
3356 - Fix a number of small memory leaks identified by coverity. Fixes
3357 bug 26467; bugfix on numerous Tor versions.
3359 o Minor bugfixes (logging):
3360 - Improve the log message when connection initiators fail to
3361 authenticate direct connections to relays. Fixes bug 26927; bugfix
3364 o Minor bugfixes (portability):
3365 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
3366 26994; bugfix on 0.3.4.1-alpha.
3367 - Work around two different bugs in the OS X 10.10 and later SDKs
3368 that would prevent us from successfully targeting earlier versions
3369 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3371 o Minor bugfixes (single onion services, Tor2web):
3372 - Log a protocol warning when single onion services or Tor2web
3373 clients fail to authenticate direct connections to relays. Fixes
3374 bug 26924; bugfix on 0.2.9.1-alpha.
3376 o Minor bugfixes (testing):
3377 - Disable core dumps in test_bt.sh, to avoid failures in "make
3378 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3380 o Minor bugfixes (testing, compatibility):
3381 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
3382 only to pass strings (rather than "bytes" objects) to the Python
3383 subprocess module. Python 3 on Windows seems to require this.
3384 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
3385 0.3.1.1-alpha (for hs_ntor_ref.py).
3387 o Minor bugfixes (v3 onion services):
3388 - Stop sending ed25519 link specifiers in v3 onion service introduce
3389 cells and descriptors, when the rendezvous or introduction point
3390 doesn't support ed25519 link authentication. Fixes bug 26627;
3391 bugfix on 0.3.2.4-alpha.
3394 Changes in version 0.3.4.5-rc - 2018-07-13
3395 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
3396 bridge relays should upgrade.
3398 o Directory authority changes:
3399 - The "Bifroest" bridge authority has been retired; the new bridge
3400 authority is "Serge", and it is operated by George from the
3401 TorBSD project. Closes ticket 26771.
3404 Changes in version 0.3.3.9 - 2018-07-13
3405 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3406 bridge relays should upgrade.
3408 o Directory authority changes:
3409 - The "Bifroest" bridge authority has been retired; the new bridge
3410 authority is "Serge", and it is operated by George from the
3411 TorBSD project. Closes ticket 26771.
3414 Changes in version 0.3.2.11 - 2018-07-13
3415 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3416 bridge relays should upgrade. We also take this opportunity to backport
3419 o Directory authority changes:
3420 - The "Bifroest" bridge authority has been retired; the new bridge
3421 authority is "Serge", and it is operated by George from the
3422 TorBSD project. Closes ticket 26771.
3424 o Directory authority changes (backport from 0.3.3.7):
3425 - Add an IPv6 address for the "dannenberg" directory authority.
3426 Closes ticket 26343.
3428 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3429 - When directory authorities read a zero-byte bandwidth file, they
3430 would previously log a warning with the contents of an
3431 uninitialised buffer. They now log a warning about the empty file
3432 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3434 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3435 - Correctly detect when onion services get disabled after HUP. Fixes
3436 bug 25761; bugfix on 0.3.2.1.
3438 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3439 - Explicitly permit the poll() system call when the Linux
3440 seccomp2-based sandbox is enabled: apparently, some versions of
3441 libc use poll() when calling getpwnam(). Closes ticket 25313.
3443 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3444 - Update the Travis CI configuration to use the stable Rust channel,
3445 now that we have decided to require that. Closes ticket 25714.
3447 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3448 - Our .travis.yml configuration now includes support for testing the
3449 results of "make distcheck". (It's not uncommon for "make check"
3450 to pass but "make distcheck" to fail.) Closes ticket 25814.
3451 - Our Travis CI configuration now integrates with the Coveralls
3452 coverage analysis tool. Closes ticket 25818.
3454 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3455 - Add several checks to detect whether Tor relays are uploading
3456 their descriptors without specifying why they regenerated them.
3457 Diagnostic for ticket 25686.
3459 o Minor features (compilation, backport from 0.3.4.4-rc):
3460 - When building Tor, prefer to use Python 3 over Python 2, and more
3461 recent (contemplated) versions over older ones. Closes
3464 o Minor features (geoip):
3465 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3466 Country database. Closes ticket 26674.
3468 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3469 - Upon receiving a malformed connected cell, stop processing the
3470 cell immediately. Previously we would mark the connection for
3471 close, but continue processing the cell as if the connection were
3472 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3474 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3475 - Allow the nanosleep() system call, which glibc uses to implement
3476 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3478 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3479 - When running the hs_ntor_ref.py test, make sure only to pass
3480 strings (rather than "bytes" objects) to the Python subprocess
3481 module. Python 3 on Windows seems to require this. Fixes bug
3482 26535; bugfix on 0.3.1.1-alpha.
3483 - When running the ntor_ref.py test, make sure only to pass strings
3484 (rather than "bytes" objects) to the Python subprocess module.
3485 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3488 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3489 - Work around a change in OpenSSL 1.1.1 where return values that
3490 would previously indicate "no password" now indicate an empty
3491 password. Without this workaround, Tor instances running with
3492 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3493 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3495 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3496 - Document that the PerConnBW{Rate,Burst} options will fall back to
3497 their corresponding consensus parameters only if those parameters
3498 are set. Previously we had claimed that these values would always
3499 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3501 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3502 - Fix a compilation warning on some versions of GCC when building
3503 code that calls routerinfo_get_my_routerinfo() twice, assuming
3504 that the second call will succeed if the first one did. Fixes bug
3505 26269; bugfix on 0.2.8.2-alpha.
3507 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3508 - Don't consider Tor running as a client if the ControlPort is open,
3509 but no actual client ports are open. Fixes bug 26062; bugfix
3512 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3513 - Prevent a possible out-of-bounds smartlist read in
3514 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3516 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3517 - Fix a very unlikely (impossible, we believe) null pointer
3518 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3519 Coverity; this is CID 1430932.
3521 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3522 - Fix a memory leak when a v3 onion service is configured and gets a
3523 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3524 - When parsing the descriptor signature, look for the token plus an
3525 extra white-space at the end. This is more correct but also will
3526 allow us to support new fields that might start with "signature".
3527 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3529 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3530 - Relays now correctly block attempts to re-extend to the previous
3531 relay by Ed25519 identity. Previously they would warn in this
3532 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3535 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3536 - Avoid a crash when running with DirPort set but ORPort turned off.
3537 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3539 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3540 - Silence unused-const-variable warnings in zstd.h with some GCC
3541 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3543 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3544 - Avoid intermittent test failures due to a test that had relied on
3545 onion service introduction point creation finishing within 5
3546 seconds of real clock time. Fixes bug 25450; bugfix
3549 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3550 - Fix a C99 compliance issue in our configuration script that caused
3551 compilation issues when compiling Tor with certain versions of
3552 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3554 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3555 - Fix a number of small memory leaks identified by coverity. Fixes
3556 bug 26467; bugfix on numerous Tor versions.
3558 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3559 - Move the list of default directory authorities to its own file.
3560 Closes ticket 24854. Patch by "beastr0".
3563 Changes in version 0.2.9.16 - 2018-07-13
3564 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3565 bridge relays should upgrade. We also take this opportunity to backport
3568 o Directory authority changes:
3569 - The "Bifroest" bridge authority has been retired; the new bridge
3570 authority is "Serge", and it is operated by George from the
3571 TorBSD project. Closes ticket 26771.
3573 o Directory authority changes (backport from 0.3.3.7):
3574 - Add an IPv6 address for the "dannenberg" directory authority.
3575 Closes ticket 26343.
3577 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3578 - When directory authorities read a zero-byte bandwidth file, they
3579 would previously log a warning with the contents of an
3580 uninitialised buffer. They now log a warning about the empty file
3581 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3583 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3584 - Explicitly permit the poll() system call when the Linux
3585 seccomp2-based sandbox is enabled: apparently, some versions of
3586 libc use poll() when calling getpwnam(). Closes ticket 25313.
3588 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3589 - Our .travis.yml configuration now includes support for testing the
3590 results of "make distcheck". (It's not uncommon for "make check"
3591 to pass but "make distcheck" to fail.) Closes ticket 25814.
3592 - Our Travis CI configuration now integrates with the Coveralls
3593 coverage analysis tool. Closes ticket 25818.
3595 o Minor features (compilation, backport from 0.3.4.4-rc):
3596 - When building Tor, prefer to use Python 3 over Python 2, and more
3597 recent (contemplated) versions over older ones. Closes
3600 o Minor features (geoip):
3601 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3602 Country database. Closes ticket 26674.
3604 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3605 - Upon receiving a malformed connected cell, stop processing the
3606 cell immediately. Previously we would mark the connection for
3607 close, but continue processing the cell as if the connection were
3608 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3610 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3611 - Allow the nanosleep() system call, which glibc uses to implement
3612 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3614 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3615 - When running the ntor_ref.py test, make sure only to pass strings
3616 (rather than "bytes" objects) to the Python subprocess module.
3617 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3620 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3621 - Work around a change in OpenSSL 1.1.1 where return values that
3622 would previously indicate "no password" now indicate an empty
3623 password. Without this workaround, Tor instances running with
3624 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3625 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3627 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3628 - Fix a compilation warning on some versions of GCC when building
3629 code that calls routerinfo_get_my_routerinfo() twice, assuming
3630 that the second call will succeed if the first one did. Fixes bug
3631 26269; bugfix on 0.2.8.2-alpha.
3633 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3634 - Don't consider Tor running as a client if the ControlPort is open,
3635 but no actual client ports are open. Fixes bug 26062; bugfix
3638 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3639 - Prevent a possible out-of-bounds smartlist read in
3640 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3642 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3643 - Fix a very unlikely (impossible, we believe) null pointer
3644 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3645 Coverity; this is CID 1430932.
3647 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3648 - Fix a number of small memory leaks identified by coverity. Fixes
3649 bug 26467; bugfix on numerous Tor versions.
3651 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3652 - Move the list of default directory authorities to its own file.
3653 Closes ticket 24854. Patch by "beastr0".
3656 Changes in version 0.3.4.4-rc - 2018-07-09
3657 Tor 0.3.4.4-rc fixes several small compilation, portability, and
3658 correctness issues in previous versions of Tor. This version is a
3659 release candidate: if no serious bugs are found, we expect that the
3660 stable 0.3.4 release will be (almost) the same as this release.
3662 o Minor features (compilation):
3663 - When building Tor, prefer to use Python 3 over Python 2, and more
3664 recent (contemplated) versions over older ones. Closes
3667 o Minor features (geoip):
3668 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3669 Country database. Closes ticket 26674.
3671 o Minor features (Rust, portability):
3672 - Rust cross-compilation is now supported. Closes ticket 25895.
3674 o Minor bugfixes (compilation):
3675 - Fix a compilation warning on some versions of GCC when building
3676 code that calls routerinfo_get_my_routerinfo() twice, assuming
3677 that the second call will succeed if the first one did. Fixes bug
3678 26269; bugfix on 0.2.8.2-alpha.
3680 o Minor bugfixes (control port):
3681 - Report the port correctly when a port is configured to bind to
3682 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3683 - Handle the HSADDRESS= argument to the HSPOST command properly.
3684 (Previously, this argument was misparsed and thus ignored.) Fixes
3685 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3687 o Minor bugfixes (correctness, flow control):
3688 - Upon receiving a stream-level SENDME cell, verify that our window
3689 has not grown too large. Fixes bug 26214; bugfix on svn
3692 o Minor bugfixes (memory, correctness):
3693 - Fix a number of small memory leaks identified by coverity. Fixes
3694 bug 26467; bugfix on numerous Tor versions.
3696 o Minor bugfixes (testing, compatibility):
3697 - When running the hs_ntor_ref.py test, make sure only to pass
3698 strings (rather than "bytes" objects) to the Python subprocess
3699 module. Python 3 on Windows seems to require this. Fixes bug
3700 26535; bugfix on 0.3.1.1-alpha.
3701 - When running the ntor_ref.py test, make sure only to pass strings
3702 (rather than "bytes" objects) to the Python subprocess module.
3703 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3707 Changes in version 0.3.3.8 - 2018-07-09
3708 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
3709 fixes for a memory leak affecting directory authorities.
3711 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
3712 - Stop leaking memory on directory authorities when planning to
3713 vote. This bug was crashing authorities by exhausting their
3714 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3716 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
3717 - Make sure that failing tests in Rust will actually cause the build
3718 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3721 o Minor features (compilation, backport from 0.3.4.4-rc):
3722 - When building Tor, prefer to use Python 3 over Python 2, and more
3723 recent (contemplated) versions over older ones. Closes
3726 o Minor features (geoip):
3727 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3728 Country database. Closes ticket 26674.
3730 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3731 - Add several checks to detect whether Tor relays are uploading
3732 their descriptors without specifying why they regenerated them.
3733 Diagnostic for ticket 25686.
3735 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
3736 - Don't count path selection failures as circuit build failures.
3737 This change should eliminate cases where Tor blames its guard or
3738 the network for situations like insufficient microdescriptors
3739 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
3742 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3743 - Fix a compilation warning on some versions of GCC when building
3744 code that calls routerinfo_get_my_routerinfo() twice, assuming
3745 that the second call will succeed if the first one did. Fixes bug
3746 26269; bugfix on 0.2.8.2-alpha.
3748 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
3749 - Handle the HSADDRESS= argument to the HSPOST command properly.
3750 (Previously, this argument was misparsed and thus ignored.) Fixes
3751 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3753 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3754 - Fix a number of small memory leaks identified by coverity. Fixes
3755 bug 26467; bugfix on numerous Tor versions.
3757 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3758 - Relays now correctly block attempts to re-extend to the previous
3759 relay by Ed25519 identity. Previously they would warn in this
3760 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3763 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
3764 - When shutting down, Tor now clears all the flags in the control.c
3765 module. This should prevent a bug where authentication cookies are
3766 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
3768 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3769 - When running the hs_ntor_ref.py test, make sure only to pass
3770 strings (rather than "bytes" objects) to the Python subprocess
3771 module. Python 3 on Windows seems to require this. Fixes bug
3772 26535; bugfix on 0.3.1.1-alpha.
3773 - When running the ntor_ref.py test, make sure only to pass strings
3774 (rather than "bytes" objects) to the Python subprocess module.
3775 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3779 Changes in version 0.3.4.3-alpha - 2018-06-26
3780 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
3781 one that was causing stability issues on directory authorities.
3783 o Major bugfixes (directory authority):
3784 - Stop leaking memory on directory authorities when planning to
3785 vote. This bug was crashing authorities by exhausting their
3786 memory. Fixes bug 26435; bugfix on 0.3.3.6.
3788 o Major bugfixes (rust, testing):
3789 - Make sure that failing tests in Rust will actually cause the build
3790 to fail: previously, they were ignored. Fixes bug 26258; bugfix
3793 o Minor feature (directory authorities):
3794 - Stop warning about incomplete bw lines before the first complete
3795 bw line has been found, so that additional header lines can be
3796 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
3798 o Minor features (relay, diagnostic):
3799 - Add several checks to detect whether Tor relays are uploading
3800 their descriptors without specifying why they regenerated them.
3801 Diagnostic for ticket 25686.
3803 o Minor features (unit tests):
3804 - Test complete bandwidth measurements files, and test that
3805 incomplete bandwidth lines only give warnings when the end of the
3806 header has not been detected. Fixes bug 25947; bugfix
3809 o Minor bugfixes (compilation):
3810 - Refrain from compiling unit testing related object files when
3811 --disable-unittests is set to configure script. Fixes bug 24891;
3812 bugfix on 0.2.5.1-alpha.
3813 - When linking the libtor_testing.a library, only include the
3814 dirauth object files once. Previously, they were getting added
3815 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
3816 - The --enable-fatal-warnings flag now affects Rust code as well.
3817 Closes ticket 26245.
3819 o Minor bugfixes (onion services):
3820 - Recompute some consensus information after detecting a clock jump,
3821 or after transitioning from a non-live consensus to a live
3822 consensus. We do this to avoid having an outdated state, and
3823 miscalculating the index for next-generation onion services. Fixes
3824 bug 24977; bugfix on 0.3.2.1-alpha.
3826 o Minor bugfixes (relay):
3827 - Relays now correctly block attempts to re-extend to the previous
3828 relay by Ed25519 identity. Previously they would warn in this
3829 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3832 o Minor bugfixes (testing):
3833 - Fix compilation of the doctests in the Rust crypto crate. Fixes
3834 bug 26415; bugfix on 0.3.4.1-alpha.
3835 - Instead of trying to read the geoip configuration files from
3836 within the unit tests, instead create our own ersatz files with
3837 just enough geoip data in the format we expect. Trying to read
3838 from the source directory created problems on Windows with mingw,
3839 where the build system's paths are not the same as the platform's
3840 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
3841 - Refrain from trying to get an item from an empty smartlist in
3842 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
3843 to catch improper smartlist usage. Furthermore, enable
3844 DEBUG_SMARTLIST globally when build is configured with fragile
3845 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
3848 Changes in version 0.3.3.7 - 2018-06-12
3849 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
3850 fixes for bugs affecting compatibility and stability.
3852 o Directory authority changes:
3853 - Add an IPv6 address for the "dannenberg" directory authority.
3854 Closes ticket 26343.
3856 o Minor features (geoip):
3857 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3858 Country database. Closes ticket 26351.
3860 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3861 - Work around a change in OpenSSL 1.1.1 where return values that
3862 would previously indicate "no password" now indicate an empty
3863 password. Without this workaround, Tor instances running with
3864 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3865 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3867 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3868 - Silence unused-const-variable warnings in zstd.h with some GCC
3869 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3871 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
3872 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3873 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3874 miscounting the total number of circuits for these field values.)
3875 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3877 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3878 - Prevent a possible out-of-bounds smartlist read in
3879 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3881 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
3882 - Only select relays when they have the descriptors we prefer to use
3883 for them. This change fixes a bug where we could select a relay
3884 because it had _some_ descriptor, but reject it later with a
3885 nonfatal assertion error because it didn't have the exact one we
3886 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
3889 Changes in version 0.3.4.2-alpha - 2018-06-12
3890 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
3891 release, and forward-ports an authority-only security fix from 0.3.3.6.
3893 o Directory authority changes:
3894 - Add an IPv6 address for the "dannenberg" directory authority.
3895 Closes ticket 26343.
3897 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
3898 - Fix a bug that could have allowed an attacker to force a directory
3899 authority to use up all its RAM by passing it a maliciously
3900 crafted protocol versions string. Fixes bug 25517; bugfix on
3901 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3903 o Minor features (continuous integration):
3904 - Add the necessary configuration files for continuous integration
3905 testing on Windows, via the Appveyor platform. Closes ticket
3906 25549. Patches from Marcin Cieślak and Isis Lovecruft.
3908 o Minor features (geoip):
3909 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
3910 Country database. Closes ticket 26351.
3912 o Minor bugfixes (compatibility, openssl):
3913 - Work around a change in OpenSSL 1.1.1 where return values that
3914 would previously indicate "no password" now indicate an empty
3915 password. Without this workaround, Tor instances running with
3916 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3917 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3919 o Minor bugfixes (compilation):
3920 - Silence unused-const-variable warnings in zstd.h with some GCC
3921 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3922 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
3923 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
3924 - Avoid a compiler warning when casting the return value of
3925 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
3926 26283; bugfix on 0.2.4.10-alpha.
3928 o Minor bugfixes (control port):
3929 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
3930 CIRC_BW events. Previously, such cells were counted entirely in
3931 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
3934 o Minor bugfixes (controller):
3935 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
3936 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
3937 miscounting the total number of circuits for these field values.)
3938 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
3940 o Minor bugfixes (hardening):
3941 - Prevent a possible out-of-bounds smartlist read in
3942 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3944 o Minor bugfixes (onion services):
3945 - Fix a bug that blocked the creation of ephemeral v3 onion
3946 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
3948 o Minor bugfixes (test coverage tools):
3949 - Update our "cov-diff" script to handle output from the latest
3950 version of gcov, and to remove extraneous timestamp information
3951 from its output. Fixes bugs 26101 and 26102; bugfix
3955 Changes in version 0.3.3.6 - 2018-05-22
3956 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
3957 backports several important fixes from the 0.3.4.1-alpha.
3959 The Tor 0.3.3 series includes controller support and other
3960 improvements for v3 onion services, official support for embedding Tor
3961 within other applications, and our first non-trivial module written in
3962 the Rust programming language. (Rust is still not enabled by default
3963 when building Tor.) And as usual, there are numerous other smaller
3964 bugfixes, features, and improvements.
3966 Below are the changes since 0.3.3.5-rc. For a list of all changes
3967 since 0.3.2.10, see the ReleaseNotes file.
3969 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
3970 - When directory authorities read a zero-byte bandwidth file, they
3971 would previously log a warning with the contents of an
3972 uninitialised buffer. They now log a warning about the empty file
3973 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3975 o Major bugfixes (security, directory authority, denial-of-service):
3976 - Fix a bug that could have allowed an attacker to force a directory
3977 authority to use up all its RAM by passing it a maliciously
3978 crafted protocol versions string. Fixes bug 25517; bugfix on
3979 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
3981 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
3982 - Avoid a rare assertion failure in the circuit build timeout code
3983 if we fail to allow any circuits to actually complete. Fixes bug
3984 25733; bugfix on 0.2.2.2-alpha.
3986 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3987 - Avoid a crash when testing router reachability on a router that
3988 could have an ed25519 ID, but which does not. Fixes bug 25415;
3989 bugfix on 0.3.3.2-alpha.
3991 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3992 - Correctly detect when onion services get disabled after HUP. Fixes
3993 bug 25761; bugfix on 0.3.2.1.
3995 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
3996 - Impose a limit on circuit cell queue size. The limit can be
3997 controlled by a consensus parameter. Fixes bug 25226; bugfix
4000 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4001 - Avoid some compilation warnings with recent versions of LibreSSL.
4002 Closes ticket 26006.
4004 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4005 - Our .travis.yml configuration now includes support for testing the
4006 results of "make distcheck". (It's not uncommon for "make check"
4007 to pass but "make distcheck" to fail.) Closes ticket 25814.
4008 - Our Travis CI configuration now integrates with the Coveralls
4009 coverage analysis tool. Closes ticket 25818.
4011 o Minor features (geoip):
4012 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4013 database. Closes ticket 26104.
4015 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4016 - Don't consider Tor running as a client if the ControlPort is open,
4017 but no actual client ports are open. Fixes bug 26062; bugfix
4020 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4021 - Upon receiving a malformed connected cell, stop processing the
4022 cell immediately. Previously we would mark the connection for
4023 close, but continue processing the cell as if the connection were
4024 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4026 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4027 - Stop saying in the manual that clients cache ipv4 dns answers from
4028 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4029 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4030 we forgot to say so in the man page. Fixes bug 26052; bugfix
4033 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4034 - Allow the nanosleep() system call, which glibc uses to implement
4035 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4037 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4038 - Fix a memory leak when a v3 onion service is configured and gets a
4039 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4040 - When parsing the descriptor signature, look for the token plus an
4041 extra white-space at the end. This is more correct but also will
4042 allow us to support new fields that might start with "signature".
4043 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4045 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4046 - Avoid a crash when running with DirPort set but ORPort turned off.
4047 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4049 o Documentation (backport from 0.3.4.1-alpha):
4050 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4051 ticket 25857. Patch from "CTassisF".
4054 Changes in version 0.3.4.1-alpha - 2018-05-17
4055 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
4056 includes refactoring to begin reducing Tor's binary size and idle CPU
4057 usage on mobile, along with prep work for new bandwidth scanners,
4058 improvements to the experimental "vanguards" feature, and numerous
4059 other small features and bugfixes.
4061 o New system requirements:
4062 - Tor no longer tries to support old operating systems without
4063 mmap() or some local equivalent. Apparently, compilation on such
4064 systems has been broken for some time, without anybody noticing or
4065 complaining. Closes ticket 25398.
4067 o Major feature (directory authority, modularization):
4068 - The directory authority subsystem has been modularized. The code
4069 is now located in src/or/dirauth/, and is compiled in by default.
4070 To disable the module, the configure option
4071 --disable-module-dirauth has been added. This module may be
4072 disabled by default in some future release. Closes ticket 25610.
4074 o Major features (main loop, CPU usage):
4075 - When Tor is disabled (via DisableNetwork or via hibernation), it
4076 no longer needs to run any per-second events. This change should
4077 make it easier for mobile applications to disable Tor while the
4078 device is sleeping, or Tor is not running. Closes ticket 26063.
4079 - Tor no longer enables all of its periodic events by default.
4080 Previously, Tor would enable all possible main loop events,
4081 regardless of whether it needed them. Furthermore, many of these
4082 events are now disabled with Tor is hibernating or DisableNetwork
4083 is set. This is a big step towards reducing client CPU usage by
4084 reducing the amount of wake-ups the daemon does. Closes ticket
4086 - The bandwidth-limitation logic has been refactored so that
4087 bandwidth calculations are performed on-demand, rather than every
4088 TokenBucketRefillInterval milliseconds. This change should improve
4089 the granularity of our bandwidth calculations, and limit the
4090 number of times that the Tor process needs to wake up when it is
4091 idle. Closes ticket 25373.
4092 - Move responsibility for many operations from a once-per-second
4093 callback to a callback that is only scheduled as needed. Moving
4094 this functionality has allowed us to disable the callback when
4095 Tor's network is disabled. Once enough items are removed from our
4096 once-per-second callback, we can eliminate it entirely to conserve
4097 CPU when idle. The functionality removed includes: closing
4098 connections, circuits, and channels (ticket 25932); consensus
4099 voting (25937); flushing log callbacks (25951); honoring delayed
4100 SIGNEWNYM requests (25949); rescanning the consensus cache
4101 (25931); saving the state file to disk (25948); warning relay
4102 operators about unreachable ports (25952); and keeping track of
4103 Tor's uptime (26009).
4105 o Major bugfixes (directory authorities, security):
4106 - When directory authorities read a zero-byte bandwidth file, they
4107 would previously log a warning with the contents of an
4108 uninitialised buffer. They now log a warning about the empty file
4109 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4111 o Major bugfixes (crash):
4112 - Avoid a rare assertion failure in the circuit build timeout code
4113 if we fail to allow any circuits to actually complete. Fixes bug
4114 25733; bugfix on 0.2.2.2-alpha.
4116 o Major bugfixes (directory authority):
4117 - Avoid a crash when testing router reachability on a router that
4118 could have an ed25519 ID, but which does not. Fixes bug 25415;
4119 bugfix on 0.3.3.2-alpha.
4121 o Major bugfixes (onion service):
4122 - Correctly detect when onion services get disabled after HUP. Fixes
4123 bug 25761; bugfix on 0.3.2.1.
4125 o Major bugfixes (protover, voting):
4126 - Revise Rust implementation of protover to use a more memory-
4127 efficient voting algorithm and corresponding data structures, thus
4128 avoiding a potential (but small impact) DoS attack where specially
4129 crafted protocol strings would expand to several potential
4130 megabytes in memory. In the process, several portions of code were
4131 revised to be methods on new, custom types, rather than functions
4132 taking interchangeable types, thus increasing type safety of the
4133 module. Custom error types and handling were added as well, in
4134 order to facilitate better error dismissal/handling in outside
4135 crates and avoid mistakenly passing an internal error string to C
4136 over the FFI boundary. Many tests were added, and some previous
4137 differences between the C and Rust implementations have been
4138 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4140 o Major bugfixes (relay, denial of service):
4141 - Impose a limit on circuit cell queue size. The limit can be
4142 controlled by a consensus parameter. Fixes bug 25226; bugfix
4145 o Minor features (accounting):
4146 - When Tor becomes dormant, it now uses a scheduled event to wake up
4147 at the right time. Previously, we would use the per-second timer
4148 to check whether to wake up, but we no longer have any per-second
4149 timers enabled when the network is disabled. Closes ticket 26064.
4151 o Minor features (code quality):
4152 - Add optional spell-checking for the Tor codebase, using the
4153 "misspell" program. To use this feature, run "make check-typos".
4154 Closes ticket 25024.
4156 o Minor features (compatibility):
4157 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
4158 the no-deprecated option, and builds correctly with them. Closes
4159 tickets 19429, 19981, and 25353.
4160 - Avoid some compilation warnings with recent versions of LibreSSL.
4161 Closes ticket 26006.
4163 o Minor features (compression, zstd):
4164 - When running with zstd, Tor now considers using advanced functions
4165 that the zstd maintainers have labeled as potentially unstable. To
4166 prevent breakage, Tor will only use this functionality when the
4167 runtime version of the zstd library matches the version with which
4168 Tor was compiled. Closes ticket 25162.
4170 o Minor features (configuration):
4171 - The "DownloadSchedule" options have been renamed to end with
4172 "DownloadInitialDelay". The old names are still allowed, but will
4173 produce a warning. Comma-separated lists are still permitted for
4174 these options, but all values after the first are ignored (as they
4175 have been since 0.2.9). Closes ticket 23354.
4177 o Minor features (continuous integration):
4178 - Our .travis.yml configuration now includes support for testing the
4179 results of "make distcheck". (It's not uncommon for "make check"
4180 to pass but "make distcheck" to fail.) Closes ticket 25814.
4181 - Our Travis CI configuration now integrates with the Coveralls
4182 coverage analysis tool. Closes ticket 25818.
4184 o Minor features (control port):
4185 - Introduce GETINFO "current-time/{local,utc}" to return the local
4186 and UTC times respectively in ISO format. This helps a controller
4187 like Tor Browser detect a time-related error. Closes ticket 25511.
4188 Patch by Neel Chauhan.
4189 - Introduce new fields to the CIRC_BW event. There are two new
4190 fields in each of the read and written directions. The DELIVERED
4191 fields report the total valid data on the circuit, as measured by
4192 the payload sizes of verified and error-checked relay command
4193 cells. The OVERHEAD fields report the total unused bytes in each
4194 of these cells. Closes ticket 25903.
4196 o Minor features (directory authority):
4197 - Directory authorities now open their key-pinning files as O_SYNC,
4198 to limit their chances of accidentally writing partial lines.
4199 Closes ticket 23909.
4201 o Minor features (directory authority, forward compatibility):
4202 - Make the lines of the measured bandwidth file able to contain
4203 their entries in any order. Previously, the node_id entry needed
4204 to come first. Closes ticket 26004.
4206 o Minor features (entry guards):
4207 - Introduce a new torrc option NumPrimaryGuards for controlling the
4208 number of primary guards. Closes ticket 25843.
4210 o Minor features (geoip):
4211 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4212 database. Closes ticket 26104.
4214 o Minor features (performance):
4215 - Avoid a needless call to malloc() when processing an incoming
4216 relay cell. Closes ticket 24914.
4217 - Make our timing-wheel code run a tiny bit faster on 32-bit
4218 platforms, by preferring 32-bit math to 64-bit. Closes
4220 - Avoid a needless malloc()/free() pair every time we handle an ntor
4221 handshake. Closes ticket 25150.
4223 o Minor features (testing):
4224 - Add a unit test for voting_schedule_get_start_of_next_interval().
4225 Closes ticket 26014, and helps make unit test coverage
4227 - A new unittests module specifically for testing the functions in
4228 the (new-ish) bridges.c module has been created with new
4229 unittests, raising the code coverage percentages. Closes 25425.
4230 - We now have improved testing for addressmap_get_virtual_address()
4231 function. This should improve our test coverage, and make our test
4232 coverage more deterministic. Closes ticket 25993.
4234 o Minor features (timekeeping, circuit scheduling):
4235 - When keeping track of how busy each circuit have been recently on
4236 a given connection, use coarse-grained monotonic timers rather
4237 than gettimeofday(). This change should marginally increase
4238 accuracy and performance. Implements part of ticket 25927.
4240 o Minor bugfixes (bandwidth management):
4241 - Consider ourselves "low on write bandwidth" if we have exhausted
4242 our write bandwidth some time in the last second. This was the
4243 documented behavior before, but the actual behavior was to change
4244 this value every TokenBucketRefillInterval. Fixes bug 25828;
4245 bugfix on 0.2.3.5-alpha.
4247 o Minor bugfixes (C correctness):
4248 - Add a missing lock acquisition in the shutdown code of the control
4249 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
4250 Coverity; this is CID 1433643.
4252 o Minor bugfixes (circuit path selection):
4253 - Don't count path selection failures as circuit build failures.
4254 This change should eliminate cases where Tor blames its guard or
4255 the network for situations like insufficient microdescriptors
4256 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4259 o Minor bugfixes (client):
4260 - Don't consider Tor running as a client if the ControlPort is open,
4261 but no actual client ports are open. Fixes bug 26062; bugfix
4264 o Minor bugfixes (code style):
4265 - Fixed multiple includes of transports.h in src/or/connection.c
4266 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
4267 - Remove the unused variable n_possible from the function
4268 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
4270 o Minor bugfixes (control interface):
4271 - Respond with more human-readable error messages to GETINFO exit-
4272 policy/* requests. Also, let controller know if an error is
4273 transient (response code 551) or not (response code 552). Fixes
4274 bug 25852; bugfix on 0.2.8.1-alpha.
4276 o Minor bugfixes (controller):
4277 - Make CIRC_BW event reflect the total of all data sent on a
4278 circuit, including padding and dropped cells. Also fix a mis-
4279 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
4280 bugfix on 0.2.5.2-alpha.
4282 o Minor bugfixes (correctness, client):
4283 - Upon receiving a malformed connected cell, stop processing the cell
4284 immediately. Previously we would mark the connection for close, but
4285 continue processing the cell as if the connection were open. Fixes bug
4286 26072; bugfix on 0.2.4.7-alpha.
4288 o Minor bugfixes (directory client):
4289 - When unverified-consensus is verified, rename it to cached-
4290 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
4291 - Fixed launching a certificate fetch always during the scheduled
4292 periodic consensus fetch by fetching only in those cases when
4293 consensus are waiting for certs. Fixes bug 24740; bugfix
4296 o Minor bugfixes (documentation):
4297 - Stop saying in the manual that clients cache ipv4 dns answers from
4298 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4299 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4300 we forgot to say so in the man page. Fixes bug 26052; bugfix
4303 o Minor bugfixes (error reporting):
4304 - Improve tolerance for directory authorities with skewed clocks.
4305 Previously, an authority with a clock more than 60 seconds ahead
4306 could cause a client with a correct clock to warn that the
4307 client's clock was behind. Now the clocks of a majority of
4308 directory authorities have to be ahead of the client before this
4309 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
4311 o Minor bugfixes (Linux seccomp2 sandbox):
4312 - Allow the nanosleep() system call, which glibc uses to implement
4313 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4315 o Minor bugfixes (onion service):
4316 - Fix a memory leak when a v3 onion service is configured and gets a
4317 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4318 - When parsing the descriptor signature, look for the token plus an
4319 extra white-space at the end. This is more correct but also will
4320 allow us to support new fields that might start with "signature".
4321 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4323 o Minor bugfixes (path selection):
4324 - Only select relays when they have the descriptors we prefer to use
4325 for them. This change fixes a bug where we could select a relay
4326 because it had _some_ descriptor, but reject it later with a
4327 nonfatal assertion error because it didn't have the exact one we
4328 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4330 o Minor bugfixes (portability):
4331 - Do not align mmap length, as it is not required by POSIX, and the
4332 getpagesize function is deprecated. Fixes bug 25399; bugfix
4335 o Minor bugfixes (portability, FreeBSD):
4336 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
4337 does not stringify on FreeBSD, so we switch to tor_asprintf().
4338 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
4340 o Minor bugfixes (relay statistics):
4341 - When a relay is collecting internal statistics about how many
4342 create cell requests it has seen of each type, accurately count
4343 the requests from relays that temporarily fall out of the
4344 consensus. (To be extra conservative, we were already ignoring
4345 requests from clients in our counts, and we continue ignoring them
4346 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
4348 o Minor bugfixes (relay, crash):
4349 - Avoid a crash when running with DirPort set but ORPort turned off.
4350 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4352 o Minor bugfixes (restart-in-process):
4353 - When shutting down, Tor now clears all the flags in the control.c
4354 module. This should prevent a bug where authentication cookies are
4355 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4357 o Minor bugfixes (testing):
4358 - When testing workqueue event-cancellation, make sure that we
4359 actually cancel an event, and that cancel each event with equal
4360 probability. (It was previously possible, though extremely
4361 unlikely, for our event-canceling test not to cancel any events.)
4362 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
4363 - Repeat part of the test in test_client_pick_intro() a number of
4364 times, to give it consistent coverage. Fixes bug 25996; bugfix
4366 - Remove randomness from the hs_common/responsible_hsdirs test, so
4367 that it always takes the same path through the function it tests.
4368 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
4369 - Change the behavior of the "channel/outbound" test so that it
4370 never causes a 10-second rollover for the EWMA circuitmux code.
4371 Previously, this behavior would happen randomly, and result in
4372 fluctuating test coverage. Fixes bug 25994; bugfix
4374 - Use X509_new() to allocate certificates that will be freed later
4375 with X509_free(). Previously, some parts of the unit tests had
4376 used tor_malloc_zero(), which is incorrect, and which caused test
4377 failures on Windows when they were built with extra hardening.
4378 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
4380 - While running the circuit_timeout test, fix the PRNG to a
4381 deterministic AES stream, so that the test coverage from this test
4382 will itself be deterministic. Fixes bug 25995; bugfix
4385 o Minor bugfixes (vanguards):
4386 - Allow the last hop in a vanguard circuit to be the same as our
4387 first, to prevent the adversary from influencing guard node choice
4388 by choice of last hop. Also prevent the creation of A - B - A
4389 paths, or A - A paths, which are forbidden by relays. Fixes bug
4390 25870; bugfix on 0.3.3.1-alpha.
4392 o Code simplification and refactoring:
4393 - Remove duplicate code in parse_{c,s}method_line and bootstrap
4394 their functionalities into a single function. Fixes bug 6236;
4395 bugfix on 0.2.3.6-alpha.
4396 - We remove the PortForwsrding and PortForwardingHelper options,
4397 related functions, and the port_forwarding tests. These options
4398 were used by the now-deprecated Vidalia to help ordinary users
4399 become Tor relays or bridges. Closes ticket 25409. Patch by
4401 - In order to make the OR and dir checking function in router.c less
4402 confusing we renamed some functions and
4403 consider_testing_reachability() has been split into
4404 router_should_check_reachability() and
4405 router_do_reachability_checks(). Also we improved the documentation
4406 in some functions. Closes ticket 18918.
4407 - Initial work to isolate Libevent usage to a handful of modules in
4408 our codebase, to simplify our call structure, and so that we can
4409 more easily change event loops in the future if needed. Closes
4411 - Introduce a function to call getsockname() and return tor_addr_t,
4412 to save a little complexity throughout the codebase. Closes
4414 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
4415 as hsdir_index is always present. Also, we move hsdir_index_t into
4416 or.h. Closes ticket 23094. Patch by Neel Chauhan.
4417 - Merge functions used for describing nodes and suppress the
4418 functions that do not allocate memory for the output buffer
4419 string. NODE_DESC_BUF_LEN constant and format_node_description()
4420 function cannot be used externally from router.c module anymore.
4421 Closes ticket 25432. Patch by valentecaio.
4422 - Our main loop has been simplified so that all important operations
4423 happen inside events. Previously, some operations had to happen
4424 outside the event loop, to prevent infinite sequences of event
4425 activations. Closes ticket 25374.
4426 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4427 it in register_intro_circ() and service_intro_point_new(). This
4428 prevents the digest from being re-calculated each time. Closes
4429 ticket 23107. Patch by Neel Chauhan.
4430 - Refactor token-bucket implementations to use a common backend.
4431 Closes ticket 25766.
4432 - Remove extern declaration of stats_n_seconds_working variable from
4433 main, protecting its accesses with get_uptime() and reset_uptime()
4434 functions. Closes ticket 25081, patch by “valentecaio”.
4435 - Remove our previous logic for "cached gettimeofday()" -- our
4436 coarse monotonic timers are fast enough for this purpose, and far
4437 less error-prone. Implements part of ticket 25927.
4438 - Remove the return value for fascist_firewall_choose_address_base(),
4439 and sister functions such as fascist_firewall_choose_address_node()
4440 and fascist_firewall_choose_address_rs(). Also, while we're here,
4441 initialize the ap argument as leaving it uninitialized can pose a
4442 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4443 - Rename two fields of connection_t struct. timestamp_lastwritten is
4444 renamed to timestamp_last_write_allowed and timestamp_lastread is
4445 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4447 - Since Tor requires C99, remove our old workaround code for libc
4448 implementations where free(NULL) doesn't work. Closes ticket 24484.
4449 - Use our standard rate-limiting code to deal with excessive
4450 libevent failures, rather than the hand-rolled logic we had
4451 before. Closes ticket 26016.
4452 - We remove the return value of node_get_prim_orport() and
4453 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4454 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4455 check for a null address. Closes ticket 23873. Patch by
4457 - We switch to should_record_bridge_info() in
4458 geoip_note_client_seen() and options_need_geoip_info() instead of
4459 accessing the configuration values directly. Fixes bug 25290;
4460 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4462 o Deprecated features:
4463 - As we are not recommending 0.2.5 anymore, we require relays that
4464 once had an ed25519 key associated with their RSA key to always
4465 have that key, instead of allowing them to drop back to a version
4466 that didn't support ed25519. This means they need to use a new RSA
4467 key if they want to downgrade to an older version of tor without
4468 ed25519. Closes ticket 20522.
4471 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4472 ticket 25857. Patch from "CTassisF".
4475 - Directory authorities will no longer support voting according to
4476 any consensus method before consensus method 25. This keeps
4477 authorities compatible with all authorities running 0.2.9.8 and
4478 later, and does not break any clients or relays. Implements ticket
4479 24378 and proposal 290.
4480 - The PortForwarding and PortForwardingHelper features have been
4481 removed. The reasoning is, given that implementations of NAT
4482 traversal protocols within common consumer grade routers are
4483 frequently buggy, and that the target audience for a NAT punching
4484 feature is a perhaps less-technically-inclined relay operator,
4485 when the helper fails to setup traversal the problems are usually
4486 deep, ugly, and very router specific, making them horrendously
4487 impossible for technical support to reliable assist with, and thus
4488 resulting in frustration all around. Unfortunately, relay
4489 operators who would like to run relays behind NATs will need to
4490 become more familiar with the port forwarding configurations on
4491 their local router. Closes 25409.
4492 - The TestingEnableTbEmptyEvent option has been removed. It was used
4493 in testing simulations to measure how often connection buckets
4494 were emptied, in order to improve our scheduling, but it has not
4495 been actively used in years. Closes ticket 25760.
4496 - The old "round-robin" circuit multiplexer (circuitmux)
4497 implementation has been removed, along with a fairly large set of
4498 code that existed to support it. It has not been the default
4499 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4500 but it still required an unreasonable amount of memory and CPU.
4501 Closes ticket 25268.
4504 Changes in version 0.3.3.5-rc - 2018-04-15
4505 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4506 including some that could affect reliability or correctness.
4508 This is the first release candidate in the 0.3.3 series. If we find no
4509 new bugs or regression here, then the first stable 0.3.3 release will
4510 be nearly identical to this one.
4512 o Major bugfixes (security, protover, voting):
4513 - Revise Rust implementation of protover to use a more memory-
4514 efficient voting algorithm and corresponding data structures, thus
4515 avoiding a potential memory-based DoS attack where specially
4516 crafted protocol strings would expand to fill available memory.
4517 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4519 o Major bugfixes (performance, load balancing):
4520 - Directory authorities no longer vote in favor of the Guard flag
4521 for relays without directory support. Starting in Tor
4522 0.3.0.1-alpha, clients have been avoiding using such relays in the
4523 Guard position, leading to increasingly broken load balancing for
4524 the 5%-or-so of Guards that don't advertise directory support.
4525 Fixes bug 22310; bugfix on 0.3.0.6.
4527 o Minor feature (continuous integration):
4528 - Update the Travis CI configuration to use the stable Rust channel,
4529 now that we have decided to require that. Closes ticket 25714.
4531 o Minor features (config options):
4532 - Change the way the default value for MaxMemInQueues is calculated.
4533 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4534 more. Otherwise we use the former value of 75%. Closes
4537 o Minor features (geoip):
4538 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4539 Country database. Closes ticket 25718.
4541 o Minor bugfixes (client):
4542 - When using a listed relay as a bridge, and also using
4543 microdescriptors, and considering that relay as a non-bridge in a
4544 circuit, treat its microdescriptor as a valid source of
4545 information about that relay. This change should prevent a non-
4546 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4548 o Minor bugfixes (controller):
4549 - Restore the correct operation of the RESOLVE command, which had
4550 been broken since we added the ability to enable/disable DNS on
4551 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4553 o Minor bugfixes (distribution, compilation, rust):
4554 - Build correctly when the rust dependencies submodule is loaded,
4555 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4556 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4557 - Actually include all of our Rust source in our source
4558 distributions. (Previously, a few of the files were accidentally
4559 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4561 o Minor bugfixes (documentation):
4562 - Document that the PerConnBW{Rate,Burst} options will fall back to
4563 their corresponding consensus parameters only if those parameters
4564 are set. Previously we had claimed that these values would always
4565 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4566 - Revert a misformatting issue in the ExitPolicy documentation.
4567 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4569 o Minor bugfixes (exit relay DNS retries):
4570 - Re-attempt timed-out DNS queries 3 times before failure, since our
4571 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4572 slightly more timeouts per resolver when an exit has multiple
4573 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4575 o Minor bugfixes (onion services):
4576 - Re-instate counting the client HSDir fetch circuits against the
4577 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4579 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4580 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4581 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4583 o Code simplification and refactoring:
4584 - Move the list of default directory authorities to its own file.
4585 Closes ticket 24854. Patch by "beastr0".
4587 o Documentation (manpage, denial of service):
4588 - Provide more detail about the denial-of-service options, by
4589 listing each mitigation and explaining how they relate. Closes
4593 Changes in version 0.3.3.4-alpha - 2018-03-29
4594 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4595 the alpha testing of earlier releases in its series. We are
4596 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4598 o New system requirements:
4599 - When built with Rust, Tor now depends on version 0.2.39 of the
4600 libc crate. Closes tickets 25310 and 25664.
4602 o Major bugfixes (relay, connection):
4603 - If we have failed to connect to a relay and received a connection
4604 refused, timeout, or similar error (at the TCP level), do not try
4605 that same address/port again for 60 seconds after the failure has
4606 occurred. Fixes bug 24767; bugfix on 0.0.6.
4608 o Minor features (geoip):
4609 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4610 Country database. Closes ticket 25469.
4612 o Minor features (log messages):
4613 - Improve log message in the out-of-memory handler to include
4614 information about memory usage from the different compression
4615 backends. Closes ticket 25372.
4617 o Minor features (sandbox):
4618 - Explicitly permit the poll() system call when the Linux
4619 seccomp2-based sandbox is enabled: apparently, some versions of
4620 libc use poll() when calling getpwnam(). Closes ticket 25313.
4622 o Minor bugfixes (C correctness):
4623 - Fix a very unlikely (impossible, we believe) null pointer
4624 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4625 Coverity; this is CID 1430932.
4627 o Minor bugfixes (channel, client):
4628 - Better identify client connection when reporting to the geoip
4629 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4631 o Minor bugfixes (compilation):
4632 - Fix a C99 compliance issue in our configuration script that caused
4633 compilation issues when compiling Tor with certain versions of
4634 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4636 o Minor bugfixes (controller, reliability):
4637 - Avoid a (nonfatal) assertion failure when extending a one-hop
4638 circuit from the controller to become a multihop circuit. Fixes
4639 bug 24903; bugfix on 0.2.5.2-alpha.
4641 o Major bugfixes (networking):
4642 - Tor will no longer reject IPv6 address strings from Tor Browser
4643 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4644 25036, bugfix on Tor 0.3.1.2.
4646 o Minor bugfixes (networking):
4647 - string_is_valid_hostname() will not consider IP strings to be
4648 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4650 o Minor bugfixes (onion service v3):
4651 - Avoid an assertion failure when the next onion service
4652 descriptor rotation type is out of sync with the consensus's
4653 valid-after time. Instead, log a warning message with extra
4654 information, so we can better hunt down the cause of this
4655 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
4657 o Minor bugfixes (testing):
4658 - Avoid intermittent test failures due to a test that had relied on
4659 onion service introduction point creation finishing within 5
4660 seconds of real clock time. Fixes bug 25450; bugfix
4662 - Rust crates are now automatically detected and tested. Previously,
4663 some crates were not tested by `make test-rust` due to a static
4664 string in the `src/test/test_rust.sh` script specifying which
4665 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
4667 o Minor bugfixes (testing, benchmarks):
4668 - Fix a crash when running benchmark tests on win32 systems. The
4669 crash was due to a mutex that wasn't initialized before logging
4670 and options were initialized. Fixes bug 25479; bugfix
4673 o Minor bugfixes (warnings, ipv6):
4674 - Avoid a bug warning that could occur when trying to connect to a
4675 relay over IPv6. This warning would occur on a Tor instance that
4676 downloads router descriptors, but prefers to use microdescriptors.
4677 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
4679 o Code simplification and refactoring:
4680 - Remove the old (deterministic) directory retry logic entirely:
4681 We've used exponential backoff exclusively for some time. Closes
4685 - Improved the documentation of AccountingStart parameter. Closes
4687 - Update the documentation for "Log" to include the current list of
4688 logging domains. Closes ticket 25378.
4691 Changes in version 0.3.1.10 - 2018-03-03
4692 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4695 It includes an important security fix for a remote crash attack
4696 against directory authorities, tracked as TROVE-2018-001.
4698 This release also backports our new system for improved resistance to
4699 denial-of-service attacks against relays.
4701 This release also fixes several minor bugs and annoyances from
4704 All directory authorities should upgrade to one of the versions
4705 released today. Relays running 0.3.1.x may wish to update to one of
4706 the versions released today, for the DoS mitigations.
4708 Please note: according to our release calendar, Tor 0.3.1 will no
4709 longer be supported after 1 July 2018. If you will be running Tor
4710 after that date, you should make sure to plan to upgrade to the latest
4711 stable version, or downgrade to 0.2.9 (which will receive long-term
4714 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4715 - Fix a protocol-list handling bug that could be used to remotely crash
4716 directory authorities with a null-pointer exception. Fixes bug 25074;
4717 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4720 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
4721 - Give relays some defenses against the recent network overload. We
4722 start with three defenses (default parameters in parentheses).
4723 First: if a single client address makes too many concurrent
4724 connections (>100), hang up on further connections. Second: if a
4725 single client address makes circuits too quickly (more than 3 per
4726 second, with an allowed burst of 90) while also having too many
4727 connections open (3), refuse new create cells for the next while
4728 (1-2 hours). Third: if a client asks to establish a rendezvous
4729 point to you directly, ignore the request. These defenses can be
4730 manually controlled by new torrc options, but relays will also
4731 take guidance from consensus parameters, so there's no need to
4732 configure anything manually. Implements ticket 24902.
4734 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4735 - Update the sandbox rules so that they should now work correctly
4736 with Glibc 2.26. Closes ticket 24315.
4738 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
4739 - Fix an "off by 2" error in counting rendezvous failures on the
4740 onion service side. While we thought we would stop the rendezvous
4741 attempt after one failed circuit, we were actually making three
4742 circuit attempts before giving up. Now switch to a default of 2,
4743 and allow the consensus parameter "hs_service_max_rdv_failures" to
4744 override. Fixes bug 24895; bugfix on 0.0.6.
4746 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
4747 - Add Link protocol version 5 to the supported protocols list. Fixes
4748 bug 25070; bugfix on 0.3.1.1-alpha.
4750 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
4751 - Fix a set of false positives where relays would consider
4752 connections to other relays as being client-only connections (and
4753 thus e.g. deserving different link padding schemes) if those
4754 relays fell out of the consensus briefly. Now we look only at the
4755 initial handshake and whether the connection authenticated as a
4756 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
4758 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
4759 - Make our OOM handler aware of the geoip client history cache so it
4760 doesn't fill up the memory. This check is important for IPv6 and
4761 our DoS mitigation subsystem. Closes ticket 25122.
4763 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
4764 - Change relay bandwidth reporting stats interval from 4 hours to 24
4765 hours in order to reduce the efficiency of guard discovery
4766 attacks. Fixes ticket 23856.
4768 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
4769 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4770 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4771 since they neither disabled TLS 1.3 nor enabled any of the
4772 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4773 Closes ticket 24978.
4775 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
4776 - The fallback directory list has been re-generated based on the
4777 current status of the network. Tor uses fallback directories to
4778 bootstrap when it doesn't yet have up-to-date directory
4779 information. Closes ticket 24801.
4780 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4781 prefer to bootstrap from fallback directory mirrors. This is a
4782 follow-up to 24679, which removed weights from the default
4783 fallbacks. Implements ticket 24681.
4785 o Minor features (geoip):
4786 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
4789 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
4790 - Use the actual observed address of an incoming relay connection,
4791 not the canonical address of the relay from its descriptor, when
4792 making decisions about how to handle the incoming connection.
4793 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
4795 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
4796 - Directory authorities, when refusing a descriptor from a rejected
4797 relay, now explicitly tell the relay (in its logs) to set a valid
4798 ContactInfo address and contact the bad-relays@ mailing list.
4799 Fixes bug 25170; bugfix on 0.2.9.1.
4801 o Minor bugfixes (address selection, backport from 0.3.2.9):
4802 - When the fascist_firewall_choose_address_ functions don't find a
4803 reachable address, set the returned address to the null address
4804 and port. This is a precautionary measure, because some callers do
4805 not check the return value. Fixes bug 24736; bugfix
4808 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
4809 - Fetch descriptors aggressively whenever we lack enough to build
4810 circuits, regardless of how many descriptors we are missing.
4811 Previously, we would delay launching the fetch when we had fewer
4812 than 15 missing descriptors, even if some of those descriptors
4813 were blocking circuits from building. Fixes bug 23985; bugfix on
4814 0.1.1.11-alpha. The effects of this bug became worse in
4815 0.3.0.3-alpha, when we began treating missing descriptors from our
4816 primary guards as a reason to delay circuits.
4817 - Don't try fetching microdescriptors from relays that have failed
4818 to deliver them in the past. Fixes bug 23817; bugfix
4821 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
4822 - Fix a signed/unsigned comparison warning introduced by our fix to
4823 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
4825 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
4826 - Avoid a crash when attempting to use the seccomp2 sandbox together
4827 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
4830 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
4831 - Fix a possible crash on malformed consensus. If a consensus had
4832 contained an unparseable protocol line, it could have made clients
4833 and relays crash with a null-pointer exception. To exploit this
4834 issue, however, an attacker would need to be able to subvert the
4835 directory authority system. Fixes bug 25251; bugfix on
4836 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
4838 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
4839 - Recover better from empty or corrupt files in the consensus cache
4840 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
4841 - When a consensus diff calculation is only partially successful,
4842 only record the successful parts as having succeeded. Partial
4843 success can happen if (for example) one compression method fails
4844 but the others succeed. Previously we misrecorded all the
4845 calculations as having succeeded, which would later cause a
4846 nonfatal assertion failure. Fixes bug 24086; bugfix
4849 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
4850 - Tor now updates its guard state when it reads a consensus
4851 regardless of whether it's missing descriptors. That makes tor use
4852 its primary guards to fetch descriptors in some edge cases where
4853 it would previously have used fallback directories. Fixes bug
4854 23862; bugfix on 0.3.0.1-alpha.
4856 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
4857 - Don't treat inability to store a cached consensus object as a bug:
4858 it can happen normally when we are out of disk space. Fixes bug
4859 24859; bugfix on 0.3.1.1-alpha.
4861 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
4862 - When queuing DESTROY cells on a channel, only queue the circuit-id
4863 and reason fields: not the entire 514-byte cell. This fix should
4864 help mitigate any bugs or attacks that fill up these queues, and
4865 free more RAM for other uses. Fixes bug 24666; bugfix
4868 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
4869 - When closing a connection via close_connection_immediately(), we
4870 mark it as "not blocked on bandwidth", to prevent later calls from
4871 trying to unblock it, and give it permission to read. This fixes a
4872 backtrace warning that can happen on relays under various
4873 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
4875 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
4876 - When selecting relays by bandwidth, avoid a rounding error that
4877 could sometimes cause load to be imbalanced incorrectly.
4878 Previously, we would always round upwards; now, we round towards
4879 the nearest integer. This had the biggest effect when a relay's
4880 weight adjustments should have given it weight 0, but it got
4881 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
4882 - When calculating the fraction of nodes that have descriptors, and
4883 all nodes in the network have zero bandwidths, count the number of
4884 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
4885 - Actually log the total bandwidth in compute_weighted_bandwidths().
4886 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
4888 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
4889 - Improve the performance of our consensus-diff application code
4890 when Tor is built with the --enable-fragile-hardening option set.
4891 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
4893 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
4894 - Don't exit the Tor process if setrlimit() fails to change the file
4895 limit (which can happen sometimes on some versions of OSX). Fixes
4896 bug 21074; bugfix on 0.0.9pre5.
4898 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
4899 - Fix a bug in the bit-counting parts of our timing-wheel code on
4900 MSVC. (Note that MSVC is still not a supported build platform, due
4901 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
4904 o Minor bugfixes (relay, partial backport):
4905 - Make the internal channel_is_client() function look at what sort
4906 of connection handshake the other side used, rather than whether
4907 the other side ever sent a create_fast cell to us. Backports part
4908 of the fixes from bugs 22805 and 24898.
4910 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
4911 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
4913 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
4914 bugfix on 0.2.9.4-alpha.
4916 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
4917 - Update the "rust dependencies" submodule to be a project-level
4918 repository, rather than a user repository. Closes ticket 25323.
4921 Changes in version 0.2.9.15 - 2018-03-03
4922 Tor 0.2.9.15 backports important security and stability bugfixes from
4925 It includes an important security fix for a remote crash attack
4926 against directory authorities, tracked as TROVE-2018-001.
4928 This release also backports our new system for improved resistance to
4929 denial-of-service attacks against relays.
4931 This release also fixes several minor bugs and annoyances from
4934 All directory authorities should upgrade to one of the versions
4935 released today. Relays running 0.2.9.x may wish to update to one of
4936 the versions released today, for the DoS mitigations.
4938 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
4939 - Fix a protocol-list handling bug that could be used to remotely crash
4940 directory authorities with a null-pointer exception. Fixes bug 25074;
4941 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
4944 o Major features (denial-of-service mitigation):
4945 - Give relays some defenses against the recent network overload. We
4946 start with three defenses (default parameters in parentheses).
4947 First: if a single client address makes too many concurrent
4948 connections (>100), hang up on further connections. Second: if a
4949 single client address makes circuits too quickly (more than 3 per
4950 second, with an allowed burst of 90) while also having too many
4951 connections open (3), refuse new create cells for the next while
4952 (1-2 hours). Third: if a client asks to establish a rendezvous
4953 point to you directly, ignore the request. These defenses can be
4954 manually controlled by new torrc options, but relays will also
4955 take guidance from consensus parameters, so there's no need to
4956 configure anything manually. Implements ticket 24902.
4958 o Major bugfixes (bootstrapping):
4959 - Fetch descriptors aggressively whenever we lack enough to build
4960 circuits, regardless of how many descriptors we are missing.
4961 Previously, we would delay launching the fetch when we had fewer
4962 than 15 missing descriptors, even if some of those descriptors
4963 were blocking circuits from building. Fixes bug 23985; bugfix on
4964 0.1.1.11-alpha. The effects of this bug became worse in
4965 0.3.0.3-alpha, when we began treating missing descriptors from our
4966 primary guards as a reason to delay circuits.
4968 o Major bugfixes (onion services, retry behavior):
4969 - Fix an "off by 2" error in counting rendezvous failures on the
4970 onion service side. While we thought we would stop the rendezvous
4971 attempt after one failed circuit, we were actually making three
4972 circuit attempts before giving up. Now switch to a default of 2,
4973 and allow the consensus parameter "hs_service_max_rdv_failures" to
4974 override. Fixes bug 24895; bugfix on 0.0.6.
4976 o Minor feature (relay statistics):
4977 - Change relay bandwidth reporting stats interval from 4 hours to 24
4978 hours in order to reduce the efficiency of guard discovery
4979 attacks. Fixes ticket 23856.
4981 o Minor features (compatibility, OpenSSL):
4982 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
4983 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
4984 since they neither disabled TLS 1.3 nor enabled any of the
4985 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
4986 Closes ticket 24978.
4988 o Minor features (denial-of-service avoidance):
4989 - Make our OOM handler aware of the geoip client history cache so it
4990 doesn't fill up the memory. This check is important for IPv6 and
4991 our DoS mitigation subsystem. Closes ticket 25122.
4993 o Minor features (fallback directory mirrors):
4994 - The fallback directory list has been re-generated based on the
4995 current status of the network. Tor uses fallback directories to
4996 bootstrap when it doesn't yet have up-to-date directory
4997 information. Closes ticket 24801.
4998 - Make the default DirAuthorityFallbackRate 0.1, so that clients
4999 prefer to bootstrap from fallback directory mirrors. This is a
5000 follow-up to 24679, which removed weights from the default
5001 fallbacks. Implements ticket 24681.
5003 o Minor features (geoip):
5004 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5007 o Minor features (linux seccomp2 sandbox):
5008 - Update the sandbox rules so that they should now work correctly
5009 with Glibc 2.26. Closes ticket 24315.
5011 o Minor bugfix (channel connection):
5012 - Use the actual observed address of an incoming relay connection,
5013 not the canonical address of the relay from its descriptor, when
5014 making decisions about how to handle the incoming connection.
5015 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5017 o Minor bugfix (directory authority):
5018 - Directory authorities, when refusing a descriptor from a rejected
5019 relay, now explicitly tell the relay (in its logs) to set a valid
5020 ContactInfo address and contact the bad-relays@ mailing list.
5021 Fixes bug 25170; bugfix on 0.2.9.1.
5023 o Minor bugfixes (address selection):
5024 - When the fascist_firewall_choose_address_ functions don't find a
5025 reachable address, set the returned address to the null address
5026 and port. This is a precautionary measure, because some callers do
5027 not check the return value. Fixes bug 24736; bugfix
5030 o Minor bugfixes (compilation):
5031 - Fix a signed/unsigned comparison warning introduced by our fix to
5032 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5034 o Minor bugfixes (control port, linux seccomp2 sandbox):
5035 - Avoid a crash when attempting to use the seccomp2 sandbox together
5036 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5039 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5040 - Fix a possible crash on malformed consensus. If a consensus had
5041 contained an unparseable protocol line, it could have made clients
5042 and relays crash with a null-pointer exception. To exploit this
5043 issue, however, an attacker would need to be able to subvert the
5044 directory authority system. Fixes bug 25251; bugfix on
5045 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5047 o Minor bugfixes (memory usage):
5048 - When queuing DESTROY cells on a channel, only queue the circuit-id
5049 and reason fields: not the entire 514-byte cell. This fix should
5050 help mitigate any bugs or attacks that fill up these queues, and
5051 free more RAM for other uses. Fixes bug 24666; bugfix
5054 o Minor bugfixes (network layer):
5055 - When closing a connection via close_connection_immediately(), we
5056 mark it as "not blocked on bandwidth", to prevent later calls from
5057 trying to unblock it, and give it permission to read. This fixes a
5058 backtrace warning that can happen on relays under various
5059 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5061 o Minor bugfixes (OSX):
5062 - Don't exit the Tor process if setrlimit() fails to change the file
5063 limit (which can happen sometimes on some versions of OSX). Fixes
5064 bug 21074; bugfix on 0.0.9pre5.
5066 o Minor bugfixes (path selection):
5067 - When selecting relays by bandwidth, avoid a rounding error that
5068 could sometimes cause load to be imbalanced incorrectly.
5069 Previously, we would always round upwards; now, we round towards
5070 the nearest integer. This had the biggest effect when a relay's
5071 weight adjustments should have given it weight 0, but it got
5072 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5073 - When calculating the fraction of nodes that have descriptors, and
5074 all nodes in the network have zero bandwidths, count the number of
5075 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5076 - Actually log the total bandwidth in compute_weighted_bandwidths().
5077 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5079 o Minor bugfixes (portability, msvc):
5080 - Fix a bug in the bit-counting parts of our timing-wheel code on
5081 MSVC. (Note that MSVC is still not a supported build platform, due
5082 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5085 o Minor bugfixes (relay):
5086 - Make the internal channel_is_client() function look at what sort
5087 of connection handshake the other side used, rather than whether
5088 the other side ever sent a create_fast cell to us. Backports part
5089 of the fixes from bugs 22805 and 24898.
5091 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5092 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5094 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5095 bugfix on 0.2.9.4-alpha.
5098 Changes in version 0.3.2.10 - 2018-03-03
5099 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
5100 backports a number of bugfixes, including important fixes for security
5103 It includes an important security fix for a remote crash attack
5104 against directory authorities, tracked as TROVE-2018-001.
5106 Additionally, it backports a fix for a bug whose severity we have
5107 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
5108 triggered in order to crash relays with a use-after-free pattern. As
5109 such, we are now tracking that bug as TROVE-2018-002 and
5110 CVE-2018-0491, and backporting it to earlier releases. This bug
5111 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
5114 This release also backports our new system for improved resistance to
5115 denial-of-service attacks against relays.
5117 This release also fixes several minor bugs and annoyances from
5120 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5121 today, for the fix to TROVE-2018-002. Directory authorities should
5122 also upgrade. (Relays on earlier versions might want to update too for
5123 the DoS mitigations.)
5125 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5126 - Fix a protocol-list handling bug that could be used to remotely crash
5127 directory authorities with a null-pointer exception. Fixes bug 25074;
5128 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5131 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5132 - Avoid adding the same channel twice in the KIST scheduler pending
5133 list, which could lead to remote denial-of-service use-after-free
5134 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5136 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5137 - Give relays some defenses against the recent network overload. We
5138 start with three defenses (default parameters in parentheses).
5139 First: if a single client address makes too many concurrent
5140 connections (>100), hang up on further connections. Second: if a
5141 single client address makes circuits too quickly (more than 3 per
5142 second, with an allowed burst of 90) while also having too many
5143 connections open (3), refuse new create cells for the next while
5144 (1-2 hours). Third: if a client asks to establish a rendezvous
5145 point to you directly, ignore the request. These defenses can be
5146 manually controlled by new torrc options, but relays will also
5147 take guidance from consensus parameters, so there's no need to
5148 configure anything manually. Implements ticket 24902.
5150 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5151 - Fix an "off by 2" error in counting rendezvous failures on the
5152 onion service side. While we thought we would stop the rendezvous
5153 attempt after one failed circuit, we were actually making three
5154 circuit attempts before giving up. Now switch to a default of 2,
5155 and allow the consensus parameter "hs_service_max_rdv_failures" to
5156 override. Fixes bug 24895; bugfix on 0.0.6.
5157 - New-style (v3) onion services now obey the "max rendezvous circuit
5158 attempts" logic. Previously they would make as many rendezvous
5159 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5160 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5162 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5163 - Add Link protocol version 5 to the supported protocols list. Fixes
5164 bug 25070; bugfix on 0.3.1.1-alpha.
5166 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5167 - Fix a set of false positives where relays would consider
5168 connections to other relays as being client-only connections (and
5169 thus e.g. deserving different link padding schemes) if those
5170 relays fell out of the consensus briefly. Now we look only at the
5171 initial handshake and whether the connection authenticated as a
5172 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5174 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5175 - The scheduler subsystem was failing to promptly notice changes in
5176 consensus parameters, making it harder to switch schedulers
5177 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5179 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5180 - Make our OOM handler aware of the geoip client history cache so it
5181 doesn't fill up the memory. This check is important for IPv6 and
5182 our DoS mitigation subsystem. Closes ticket 25122.
5184 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5185 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5186 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5187 since they neither disabled TLS 1.3 nor enabled any of the
5188 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5189 Closes ticket 24978.
5191 o Minor features (geoip):
5192 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5195 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5196 - When logging a failure to create an onion service's descriptor,
5197 also log what the problem with the descriptor was. Diagnostic
5200 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5201 - Use the actual observed address of an incoming relay connection,
5202 not the canonical address of the relay from its descriptor, when
5203 making decisions about how to handle the incoming connection.
5204 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5206 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5207 - Fix a possible crash on malformed consensus. If a consensus had
5208 contained an unparseable protocol line, it could have made clients
5209 and relays crash with a null-pointer exception. To exploit this
5210 issue, however, an attacker would need to be able to subvert the
5211 directory authority system. Fixes bug 25251; bugfix on
5212 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5214 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5215 - Directory authorities, when refusing a descriptor from a rejected
5216 relay, now explicitly tell the relay (in its logs) to set a valid
5217 ContactInfo address and contact the bad-relays@ mailing list.
5218 Fixes bug 25170; bugfix on 0.2.9.1.
5220 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5221 - When building with Rust on OSX, link against libresolv, to work
5222 around the issue at https://github.com/rust-lang/rust/issues/46797.
5223 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5225 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5226 - Remove a BUG() statement when a client fetches an onion descriptor
5227 that has a lower revision counter than the one in its cache. This
5228 can happen in normal circumstances due to HSDir desync. Fixes bug
5229 24976; bugfix on 0.3.2.1-alpha.
5231 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5232 - Don't treat inability to store a cached consensus object as a bug:
5233 it can happen normally when we are out of disk space. Fixes bug
5234 24859; bugfix on 0.3.1.1-alpha.
5236 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5237 - Improve the performance of our consensus-diff application code
5238 when Tor is built with the --enable-fragile-hardening option set.
5239 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5241 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5242 - Don't exit the Tor process if setrlimit() fails to change the file
5243 limit (which can happen sometimes on some versions of OSX). Fixes
5244 bug 21074; bugfix on 0.0.9pre5.
5246 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5247 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5249 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5250 bugfix on 0.2.9.4-alpha.
5252 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5253 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5254 25005; bugfix on 0.3.2.7-rc.
5256 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5257 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5258 version, when deciding whether a consensus entry can support the
5259 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5260 bugfix on 0.3.2.1-alpha.
5262 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5263 - Update the "rust dependencies" submodule to be a project-level
5264 repository, rather than a user repository. Closes ticket 25323.
5266 o Documentation (backport from 0.3.3.1-alpha)
5267 - Document that operators who run more than one relay or bridge are
5268 expected to set MyFamily and ContactInfo correctly. Closes
5272 Changes in version 0.3.3.3-alpha - 2018-03-03
5273 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
5274 It includes an important security fix for a remote crash attack
5275 against directory authorities tracked as TROVE-2018-001.
5277 Additionally, with this release, we are upgrading the severity of a
5278 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
5279 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
5280 a use-after-free pattern. As such, we are now tracking that bug as
5281 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
5282 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
5284 This release also fixes several minor bugs and annoyances from
5287 Relays running 0.3.2.x should upgrade to one of the versions released
5288 today, for the fix to TROVE-2018-002. Directory authorities should
5289 also upgrade. (Relays on earlier versions might want to update too for
5290 the DoS mitigations.)
5292 o Major bugfixes (denial-of-service, directory authority):
5293 - Fix a protocol-list handling bug that could be used to remotely crash
5294 directory authorities with a null-pointer exception. Fixes bug 25074;
5295 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5298 o Minor features (compatibility, OpenSSL):
5299 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5300 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5301 since they neither disabled TLS 1.3 nor enabled any of the
5302 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5303 Closes ticket 24978.
5305 o Minor features (logging):
5306 - Clarify the log messages produced when getrandom() or a related
5307 entropy-generation mechanism gives an error. Closes ticket 25120.
5309 o Minor features (testing):
5310 - Add a "make test-rust" target to run the rust tests only. Closes
5313 o Minor bugfixes (denial-of-service):
5314 - Fix a possible crash on malformed consensus. If a consensus had
5315 contained an unparseable protocol line, it could have made clients
5316 and relays crash with a null-pointer exception. To exploit this
5317 issue, however, an attacker would need to be able to subvert the
5318 directory authority system. Fixes bug 25251; bugfix on
5319 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5321 o Minor bugfixes (DoS mitigation):
5322 - Add extra safety checks when refilling the circuit creation bucket
5323 to ensure we never set a value above the allowed maximum burst.
5324 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
5325 - When a new consensus arrives, don't update our DoS-mitigation
5326 parameters if we aren't a public relay. Fixes bug 25223; bugfix
5329 o Minor bugfixes (man page, SocksPort):
5330 - Remove dead code from the old "SocksSocket" option, and rename
5331 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
5332 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
5334 o Minor bugfixes (performance):
5335 - Reduce the number of circuits that will be opened at once during
5336 the circuit build timeout phase. This is done by increasing the
5337 idle timeout to 3 minutes, and lowering the maximum number of
5338 concurrent learning circuits to 10. Fixes bug 24769; bugfix
5341 o Minor bugfixes (spec conformance):
5342 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5344 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5345 bugfix on 0.2.9.4-alpha.
5347 o Minor bugfixes (spec conformance, rust):
5348 - Resolve a denial-of-service issue caused by an infinite loop in
5349 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
5350 Also tracked as TROVE-2018-003.
5352 o Code simplification and refactoring:
5353 - Update the "rust dependencies" submodule to be a project-level
5354 repository, rather than a user repository. Closes ticket 25323.
5357 Changes in version 0.3.3.2-alpha - 2018-02-10
5358 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
5359 introduces a mechanism to handle the high loads that many relay
5360 operators have been reporting recently. It also fixes several bugs in
5361 older releases. If this new code proves reliable, we plan to backport
5362 it to older supported release series.
5364 o Major features (denial-of-service mitigation):
5365 - Give relays some defenses against the recent network overload. We
5366 start with three defenses (default parameters in parentheses).
5367 First: if a single client address makes too many concurrent
5368 connections (>100), hang up on further connections. Second: if a
5369 single client address makes circuits too quickly (more than 3 per
5370 second, with an allowed burst of 90) while also having too many
5371 connections open (3), refuse new create cells for the next while
5372 (1-2 hours). Third: if a client asks to establish a rendezvous
5373 point to you directly, ignore the request. These defenses can be
5374 manually controlled by new torrc options, but relays will also
5375 take guidance from consensus parameters, so there's no need to
5376 configure anything manually. Implements ticket 24902.
5378 o Major bugfixes (netflow padding):
5379 - Stop adding unneeded channel padding right after we finish
5380 flushing to a connection that has been trying to flush for many
5381 seconds. Instead, treat all partial or complete flushes as
5382 activity on the channel, which will defer the time until we need
5383 to add padding. This fix should resolve confusing and scary log
5384 messages like "Channel padding timeout scheduled 221453ms in the
5385 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5387 o Major bugfixes (protocol versions):
5388 - Add Link protocol version 5 to the supported protocols list. Fixes
5389 bug 25070; bugfix on 0.3.1.1-alpha.
5391 o Major bugfixes (scheduler, consensus):
5392 - The scheduler subsystem was failing to promptly notice changes in
5393 consensus parameters, making it harder to switch schedulers
5394 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5396 o Minor features (denial-of-service avoidance):
5397 - Make our OOM handler aware of the geoip client history cache so it
5398 doesn't fill up the memory. This check is important for IPv6 and
5399 our DoS mitigation subsystem. Closes ticket 25122.
5401 o Minor features (directory authority):
5402 - When directory authorities are unable to add signatures to a
5403 pending consensus, log the reason why. Closes ticket 24849.
5405 o Minor features (geoip):
5406 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5409 o Minor features (logging, diagnostic):
5410 - When logging a failure to create an onion service's descriptor,
5411 also log what the problem with the descriptor was. Diagnostic for
5414 o Minor bugfix (channel connection):
5415 - Use the actual observed address of an incoming relay connection,
5416 not the canonical address of the relay from its descriptor, when
5417 making decisions about how to handle the incoming connection.
5418 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5420 o Minor bugfix (directory authority):
5421 - Directory authorities, when refusing a descriptor from a rejected
5422 relay, now explicitly tell the relay (in its logs) to set a valid
5423 ContactInfo address and contact the bad-relays@ mailing list.
5424 Fixes bug 25170; bugfix on 0.2.9.1.
5426 o Minor bugfixes (all versions of Tor):
5427 - Use the "misspell" tool to detect and fix typos throughout the
5428 source code. Fixes bug 23650; bugfix on various versions of Tor.
5429 Patch from Deepesh Pathak.
5431 o Minor bugfixes (circuit, cannibalization):
5432 - Don't cannibalize preemptively-built circuits if we no longer
5433 recognize their first hop. This situation can happen if our Guard
5434 relay went off the consensus after the circuit was created. Fixes
5435 bug 24469; bugfix on 0.0.6.
5437 o Minor bugfixes (correctness):
5438 - Remove a nonworking, unnecessary check to see whether a circuit
5439 hop's identity digest was set when the circuit failed. Fixes bug
5440 24927; bugfix on 0.2.4.4-alpha.
5442 o Minor bugfixes (logging):
5443 - Don't treat inability to store a cached consensus object as a bug:
5444 it can happen normally when we are out of disk space. Fixes bug
5445 24859; bugfix on 0.3.1.1-alpha.
5446 - Fix a (mostly harmless) race condition when invoking
5447 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5448 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5450 o Minor bugfixes (onion services):
5451 - Remove a BUG() statement when a client fetches an onion descriptor
5452 that has a lower revision counter than the one in its cache. This
5453 can happen in normal circumstances due to HSDir desync. Fixes bug
5454 24976; bugfix on 0.3.2.1-alpha.
5455 - If we are configured to offer a single onion service, don't log
5456 long-term established one hop rendezvous points in the heartbeat.
5457 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5459 o Minor bugfixes (performance):
5460 - Avoid calling protocol_list_supports_protocol() from inside tight
5461 loops when running with cached routerinfo_t objects. Instead,
5462 summarize the relevant protocols as flags in the routerinfo_t, as
5463 we do for routerstatus_t objects. This change simplifies our code
5464 a little, and saves a large amount of short-term memory allocation
5465 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5467 o Minor bugfixes (Rust FFI):
5468 - Fix a minor memory leak which would happen whenever the C code
5469 would call the Rust implementation of
5470 protover_get_supported_protocols(). This was due to the C version
5471 returning a static string, whereas the Rust version newly allocated
5472 a CString to pass across the FFI boundary. Consequently, the C
5473 code was not expecting to need to free() what it was given. Fixes
5474 bug 25127; bugfix on 0.3.2.1-alpha.
5476 o Minor bugfixes (scheduler, KIST):
5477 - Avoid adding the same channel twice in the KIST scheduler pending
5478 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5481 o Minor bugfixes (unit test, monotonic time):
5482 - Increase a constant (1msec to 10msec) in the monotonic time test
5483 that makes sure the nsec/usec/msec times read are synchronized.
5484 This change was needed to accommodate slow systems like armel or
5485 when the clock_gettime() is not a VDSO on the running kernel.
5486 Fixes bug 25113; bugfix on 0.2.9.1.
5488 o Minor bugfixes (v3 onion services):
5489 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5490 version, when deciding whether a consensus entry can support the
5491 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5492 bugfix on 0.3.2.1-alpha.
5494 o Code simplification and refactoring:
5495 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5497 - Remove a series of counters used to track circuit extend attempts
5498 and connection status but that in reality we aren't using for
5499 anything other than stats logged by a SIGUSR1 signal. Closes
5502 o Documentation (man page):
5503 - The HiddenServiceVersion torrc option accepts only one number:
5504 either version 2 or 3. Closes ticket 25026; bugfix
5508 Changes in version 0.3.3.1-alpha - 2018-01-25
5509 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5510 several new features to Tor, including several improvements to
5511 bootstrapping, and support for an experimental "vanguards" feature to
5512 resist guard discovery attacks. This series also includes better
5513 support for applications that need to embed Tor or manage v3
5516 o Major features (embedding):
5517 - There is now a documented stable API for programs that need to
5518 embed Tor. See tor_api.h for full documentation and known bugs.
5519 Closes ticket 23684.
5520 - Tor now has support for restarting in the same process.
5521 Controllers that run Tor using the "tor_api.h" interface can now
5522 restart Tor after Tor has exited. This support is incomplete,
5523 however: we fixed crash bugs that prevented it from working at
5524 all, but many bugs probably remain, including a possibility of
5525 security issues. Implements ticket 24581.
5527 o Major features (IPv6, directory documents):
5528 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5529 consensus. This information makes it easier for IPv6 clients to
5530 bootstrap and choose reachable entry guards. Implements ticket 23826.
5531 - Add consensus method 28, which removes IPv6 ORPorts from
5532 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5533 are redundant in microdescs. This change will be used by Tor clients
5534 on 0.2.8.x and later. (That is to say, with all Tor clients that
5535 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5536 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5537 set by different numbers of authorities. Fixes 23870
5540 o Major features (onion service v3, control port):
5541 - The control port now supports commands and events for v3 onion
5542 services. It is now possible to create ephemeral v3 services using
5543 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5544 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5545 DEL_ONION) have been extended to support v3 onion services. Closes
5546 ticket 20699; implements proposal 284.
5548 o Major features (onion services):
5549 - Provide torrc options to pin the second and third hops of onion
5550 service circuits to a list of nodes. The option HSLayer2Guards
5551 pins the second hop, and the option HSLayer3Guards pins the third
5552 hop. These options are for use in conjunction with experiments
5553 with "vanguards" for preventing guard enumeration attacks. Closes
5556 o Major features (rust, portability, experimental):
5557 - Tor now ships with an optional implementation of one of its
5558 smaller modules (protover.c) in the Rust programming language. To
5559 try it out, install a Rust build environment, and configure Tor
5560 with "--enable-rust --enable-cargo-online-mode". This should not
5561 cause any user-visible changes, but should help us gain more
5562 experience with Rust, and plan future Rust integration work.
5563 Implementation by Chelsea Komlo. Closes ticket 22840.
5565 o Minor features (storage, configuration):
5566 - Users can store cached directory documents somewhere other than
5567 the DataDirectory by using the CacheDirectory option. Similarly,
5568 the storage location for relay's keys can be overridden with the
5569 KeyDirectory option. Closes ticket 22703.
5571 o Major features (v3 onion services, ipv6):
5572 - When v3 onion service clients send introduce cells, they now
5573 include the IPv6 address of the rendezvous point, if it has one.
5574 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5575 in future Tor versions, IPv6-only v3 single onion services will be
5576 able to use IPv6 addresses to connect directly to the rendezvous
5577 point. Closes ticket 23577. Patch by Neel Chauhan.
5579 o Major bugfixes (onion services, retry behavior):
5580 - Fix an "off by 2" error in counting rendezvous failures on the
5581 onion service side. While we thought we would stop the rendezvous
5582 attempt after one failed circuit, we were actually making three
5583 circuit attempts before giving up. Now switch to a default of 2,
5584 and allow the consensus parameter "hs_service_max_rdv_failures" to
5585 override. Fixes bug 24895; bugfix on 0.0.6.
5586 - New-style (v3) onion services now obey the "max rendezvous circuit
5587 attempts" logic. Previously they would make as many rendezvous
5588 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5589 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5591 o Major bugfixes (relays):
5592 - Fix a set of false positives where relays would consider
5593 connections to other relays as being client-only connections (and
5594 thus e.g. deserving different link padding schemes) if those
5595 relays fell out of the consensus briefly. Now we look only at the
5596 initial handshake and whether the connection authenticated as a
5597 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5599 o Minor feature (IPv6):
5600 - Make IPv6-only clients wait for microdescs for relays, even if we
5601 were previously using descriptors (or were using them as a bridge)
5602 and have a cached descriptor for them. Implements ticket 23827.
5603 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5604 them, rather than waiting to download microdescriptors.
5605 Implements ticket 23827.
5607 o Minor features (cleanup):
5608 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5609 when it stops. Closes ticket 23271.
5611 o Minor features (defensive programming):
5612 - Most of the functions in Tor that free objects have been replaced
5613 with macros that free the objects and set the corresponding
5614 pointers to NULL. This change should help prevent a large class of
5615 dangling pointer bugs. Closes ticket 24337.
5616 - Where possible, the tor_free() macro now only evaluates its input
5617 once. Part of ticket 24337.
5618 - Check that microdesc ed25519 ids are non-zero in
5619 node_get_ed25519_id() before returning them. Implements ticket
5620 24001, patch by "aruna1234".
5622 o Minor features (embedding):
5623 - Tor can now start with a preauthenticated control connection
5624 created by the process that launched it. This feature is meant for
5625 use by programs that want to launch and manage a Tor process
5626 without allowing other programs to manage it as well. For more
5627 information, see the __OwningControllerFD option documented in
5628 control-spec.txt. Closes ticket 23900.
5629 - On most errors that would cause Tor to exit, it now tries to
5630 return from the tor_main() function, rather than calling the
5631 system exit() function. Most users won't notice a difference here,
5632 but it should be significant for programs that run Tor inside
5633 a separate thread: they should now be able to survive Tor's exit
5634 conditions rather than having Tor shut down the entire process.
5635 Closes ticket 23848.
5636 - Applications that want to embed Tor can now tell Tor not to
5637 register any of its own POSIX signal handlers, using the
5638 __DisableSignalHandlers option. Closes ticket 24588.
5640 o Minor features (fallback directory list):
5641 - Avoid selecting fallbacks that change their IP addresses too
5642 often. Select more fallbacks by ignoring the Guard flag, and
5643 allowing lower cutoffs for the Running and V2Dir flags. Also allow
5644 a lower bandwidth, and a higher number of fallbacks per operator
5645 (5% of the list). Implements ticket 24785.
5646 - Update the fallback whitelist and blacklist based on opt-ins and
5647 relay changes. Closes tickets 22321, 24678, 22527, 24135,
5650 o Minor features (fallback directory mirror configuration):
5651 - Add a nickname to each fallback in a C comment. This makes it
5652 easier for operators to find their relays, and allows stem to use
5653 nicknames to identify fallbacks. Implements ticket 24600.
5654 - Add a type and version header to the fallback directory mirror
5655 file. Also add a delimiter to the end of each fallback entry. This
5656 helps external parsers like stem and Relay Search. Implements
5658 - Add an extrainfo cache flag for each fallback in a C comment. This
5659 allows stem to use fallbacks to fetch extra-info documents, rather
5660 than using authorities. Implements ticket 22759.
5661 - Add the generateFallbackDirLine.py script for automatically
5662 generating fallback directory mirror lines from relay fingerprints.
5663 No more typos! Add the lookupFallbackDirContact.py script for
5664 automatically looking up operator contact info from relay
5665 fingerprints. Implements ticket 24706, patch by teor and atagar.
5666 - Reject any fallback directory mirror that serves an expired
5667 consensus. Implements ticket 20942, patch by "minik".
5668 - Remove commas and equals signs from external string inputs to the
5669 fallback list. This avoids format confusion attacks. Implements
5671 - Remove the "weight=10" line from fallback directory mirror
5672 entries. Ticket 24681 will maintain the current fallback weights
5673 by changing Tor's default fallback weight to 10. Implements
5675 - Stop logging excessive information about fallback netblocks.
5676 Implements ticket 24791.
5678 o Minor features (forward-compatibility):
5679 - If a relay supports some link authentication protocol that we do
5680 not recognize, then include that relay's ed25519 key when telling
5681 other relays to extend to it. Previously, we treated future
5682 versions as if they were too old to support ed25519 link
5683 authentication. Closes ticket 20895.
5685 o Minor features (heartbeat):
5686 - Add onion service information to our heartbeat logs, displaying
5687 stats about the activity of configured onion services. Closes
5690 o Minor features (instrumentation, development):
5691 - Add the MainloopStats option to allow developers to get
5692 instrumentation information from the main event loop via the
5693 heartbeat messages. We hope to use this to improve Tor's behavior
5694 when it's trying to sleep. Closes ticket 24605.
5696 o Minor features (log messages):
5697 - Improve a warning message that happens when we fail to re-parse an
5698 old router because of an expired certificate. Closes ticket 20020.
5699 - Make the log more quantitative when we hit MaxMemInQueues
5700 threshold exposing some values. Closes ticket 24501.
5702 o Minor features (logging, android):
5703 - Added support for the Android logging subsystem. Closes
5706 o Minor features (performance):
5707 - Support predictive circuit building for onion service circuits
5708 with multiple layers of guards. Closes ticket 23101.
5709 - Use stdatomic.h where available, rather than mutexes, to implement
5710 atomic_counter_t. Closes ticket 23953.
5712 o Minor features (performance, 32-bit):
5713 - Improve performance on 32-bit systems by avoiding 64-bit division
5714 when calculating the timestamp in milliseconds for channel padding
5715 computations. Implements ticket 24613.
5716 - Improve performance on 32-bit systems by avoiding 64-bit division
5717 when timestamping cells and buffer chunks for OOM calculations.
5718 Implements ticket 24374.
5720 o Minor features (performance, OSX, iOS):
5721 - Use the mach_approximate_time() function (when available) to
5722 implement coarse monotonic time. Having a coarse time function
5723 should avoid a large number of system calls, and improve
5724 performance slightly, especially under load. Closes ticket 24427.
5726 o Minor features (performance, windows):
5727 - Improve performance on Windows Vista and Windows 7 by adjusting
5728 TCP send window size according to the recommendation from
5729 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
5732 o Major features (relay):
5733 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
5734 operator to use a more reasonable ("reduced") exit policy, rather
5735 than the default one. If you want to run an exit node without
5736 thinking too hard about which ports to allow, this one is for you.
5737 Closes ticket 13605. Patch from Neel Chauhan.
5739 o Minor features (testing, debugging, embedding):
5740 - For development purposes, Tor now has a mode in which it runs for
5741 a few seconds, then stops, and starts again without exiting the
5742 process. This mode is meant to help us debug various issues with
5743 ticket 23847. To use this feature, compile with
5744 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
5745 environment variable. This is expected to crash a lot, and is
5746 really meant for developers only. It will likely be removed in a
5747 future release. Implements ticket 24583.
5749 o Minor bugfix (network IPv6 test):
5750 - Tor's test scripts now check if "ping -6 ::1" works when the user
5751 runs "make test-network-all". Fixes bug 24677; bugfix on
5752 0.2.9.3-alpha. Patch by "ffmancera".
5754 o Minor bugfixes (build, rust):
5755 - Fix output of autoconf checks to display success messages for Rust
5756 dependencies and a suitable rustc compiler version. Fixes bug
5757 24612; bugfix on 0.3.1.3-alpha.
5758 - When building with Rust on OSX, link against libresolv, to work
5759 around the issue at https://github.com/rust-lang/rust/issues/46797.
5760 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5761 - Don't pass the --quiet option to cargo: it seems to suppress some
5762 errors, which is not what we want to do when building. Fixes bug
5763 24518; bugfix on 0.3.1.7.
5764 - Build correctly when building from outside Tor's source tree with
5765 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
5768 o Minor bugfixes (directory authorities, IPv6):
5769 - When creating a routerstatus (vote) from a routerinfo (descriptor),
5770 set the IPv6 address to the unspecified IPv6 address, and
5771 explicitly initialize the port to zero. Fixes bug 24488; bugfix
5774 o Minor bugfixes (fallback directory mirrors):
5775 - Make updateFallbackDirs.py search harder for python. (Some OSs
5776 don't put it in /usr/bin.) Fixes bug 24708; bugfix
5779 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
5780 - When hibernating, close connections normally and allow them to
5781 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
5783 - Do not attempt to launch self-reachability tests when entering
5784 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5785 - Resolve several bugs related to descriptor fetching on bridge
5786 clients with bandwidth accounting enabled. (This combination is
5787 not recommended!) Fixes a case of bug 12062; bugfix
5789 - When hibernating, do not attempt to launch DNS checks. Fixes a
5790 case of bug 12062; bugfix on 0.1.2.2-alpha.
5791 - When hibernating, do not try to upload or download descriptors.
5792 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
5794 o Minor bugfixes (IPv6, bridges):
5795 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
5796 bugfix on 0.2.8.2-alpha.
5797 - Tor now sets IPv6 address in the routerstatus as well as in the
5798 router descriptors when updating addresses for a bridge. Closes
5799 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
5801 o Minor bugfixes (linux seccomp2 sandbox):
5802 - When running with the sandbox enabled, reload configuration files
5803 correctly even when %include was used. Previously we would crash.
5804 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
5806 o Minor bugfixes (memory leaks):
5807 - Avoid possible at-exit memory leaks related to use of Libevent's
5808 event_base_once() function. (This function tends to leak memory if
5809 the event_base is closed before the event fires.) Fixes bug 24584;
5810 bugfix on 0.2.8.1-alpha.
5811 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
5814 o Minor bugfixes (OSX):
5815 - Don't exit the Tor process if setrlimit() fails to change the file
5816 limit (which can happen sometimes on some versions of OSX). Fixes
5817 bug 21074; bugfix on 0.0.9pre5.
5819 o Minor bugfixes (performance, fragile-hardening):
5820 - Improve the performance of our consensus-diff application code
5821 when Tor is built with the --enable-fragile-hardening option set.
5822 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5824 o Minor bugfixes (performance, timeouts):
5825 - Consider circuits for timeout as soon as they complete a hop. This
5826 is more accurate than applying the timeout in
5827 circuit_expire_building() because that function is only called
5828 once per second, which is now too slow for typical timeouts on the
5829 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
5830 - Use onion service circuits (and other circuits longer than 3 hops)
5831 to calculate a circuit build timeout. Previously, Tor only
5832 calculated its build timeout based on circuits that planned to be
5833 exactly 3 hops long. With this change, we include measurements
5834 from all circuits at the point where they complete their third
5835 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
5837 o Minor bugfixes (testing):
5838 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
5839 bugfix on 0.2.3.1-alpha.
5840 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5841 25005; bugfix on 0.3.2.7-rc.
5843 o Code simplification and refactoring:
5844 - Remove /usr/athena from search path in configure.ac. Closes
5846 - Remove duplicate code in node_has_curve25519_onion_key() and
5847 node_get_curve25519_onion_key(), and add a check for a zero
5848 microdesc curve25519 onion key. Closes ticket 23966, patch by
5849 "aruna1234" and teor.
5850 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
5851 memory allocations with large numbers of OR connections (e.g.
5852 relays). Closes ticket 24119.
5853 - Separate the function that deletes ephemeral files when Tor
5855 - Small changes to Tor's buf_t API to make it suitable for use as a
5856 general-purpose safe string constructor. Closes ticket 22342.
5857 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
5858 avoid source code identifier confusion. Closes ticket 24467.
5859 - The tor_git_revision[] constant no longer needs to be redeclared
5860 by everything that links against the rest of Tor. Done as part of
5861 ticket 23845, to simplify our external API.
5862 - We make extend_info_from_node() use node_get_curve25519_onion_key()
5863 introduced in ticket 23577 to access the curve25519 public keys
5864 rather than accessing it directly. Closes ticket 23760. Patch by
5866 - Add a function to log channels' scheduler state changes to aid
5867 debugging efforts. Closes ticket 24531.
5870 - Add documentation on how to build tor with Rust dependencies
5871 without having to be online. Closes ticket 22907; bugfix
5873 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
5874 traffic. Closes ticket 24318.
5875 - Document that OutboundBindAddress doesn't apply to DNS requests.
5876 Closes ticket 22145. Patch from Aruna Maurya.
5877 - Document that operators who run more than one relay or bridge are
5878 expected to set MyFamily and ContactInfo correctly. Closes
5881 o Code simplification and refactoring (channels):
5882 - Remove the incoming and outgoing channel queues. These were never
5883 used, but still took up a step in our fast path.
5884 - The majority of the channel unit tests have been rewritten and the
5885 code coverage has now been raised to 83.6% for channel.c. Closes
5887 - Remove other dead code from the channel subsystem: All together,
5888 this cleanup has removed more than 1500 lines of code overall and
5889 adding very little except for unit test.
5891 o Code simplification and refactoring (circuit rendezvous):
5892 - Split the client-side rendezvous circuit lookup into two
5893 functions: one that returns only established circuits and another
5894 that returns all kinds of circuits. Closes ticket 23459.
5896 o Code simplification and refactoring (controller):
5897 - Make most of the variables in networkstatus_getinfo_by_purpose()
5898 const. Implements ticket 24489.
5901 Changes in version 0.3.2.9 - 2018-01-09
5902 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
5904 The 0.3.2 series includes our long-anticipated new onion service
5905 design, with numerous security features. (For more information, see
5906 our blog post at https://blog.torproject.org/fall-harvest.) We also
5907 have a new circuit scheduler algorithm for improved performance on
5908 relays everywhere (see https://blog.torproject.org/kist-and-tell),
5909 along with many smaller features and bugfixes.
5911 Per our stable release policy, we plan to support each stable release
5912 series for at least the next nine months, or for three months after
5913 the first stable release of the next series: whichever is longer. If
5914 you need a release with long-term support, we recommend that you stay
5915 with the 0.2.9 series.
5917 Below is a list of the changes since 0.3.2.8-rc. For a list of all
5918 changes since 0.3.1, see the ReleaseNotes file.
5920 o Minor features (fallback directory mirrors):
5921 - The fallback directory list has been re-generated based on the
5922 current status of the network. Tor uses fallback directories to
5923 bootstrap when it doesn't yet have up-to-date directory
5924 information. Closes ticket 24801.
5925 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5926 prefer to bootstrap from fallback directory mirrors. This is a
5927 follow-up to 24679, which removed weights from the default
5928 fallbacks. Implements ticket 24681.
5930 o Minor features (geoip):
5931 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
5934 o Minor bugfixes (address selection):
5935 - When the fascist_firewall_choose_address_ functions don't find a
5936 reachable address, set the returned address to the null address
5937 and port. This is a precautionary measure, because some callers do
5938 not check the return value. Fixes bug 24736; bugfix
5941 o Minor bugfixes (compilation):
5942 - Resolve a few shadowed-variable warnings in the onion service
5943 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
5945 o Minor bugfixes (portability, msvc):
5946 - Fix a bug in the bit-counting parts of our timing-wheel code on
5947 MSVC. (Note that MSVC is still not a supported build platform, due
5948 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5952 Changes in version 0.3.2.8-rc - 2017-12-21
5953 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
5954 schedulers that had led servers under heavy load to overload their
5955 outgoing connections. All relay operators running earlier 0.3.2.x
5956 versions should upgrade. This version also includes a mitigation for
5957 over-full DESTROY queues leading to out-of-memory conditions: if it
5958 works, we will soon backport it to earlier release series.
5960 This is the second release candidate in the 0.3.2 series. If we find
5961 no new bugs or regression here, then the first stable 0.3.2 release
5962 will be nearly identical to this.
5964 o Major bugfixes (KIST, scheduler):
5965 - The KIST scheduler did not correctly account for data already
5966 enqueued in each connection's send socket buffer, particularly in
5967 cases when the TCP/IP congestion window was reduced between
5968 scheduler calls. This situation lead to excessive per-connection
5969 buffering in the kernel, and a potential memory DoS. Fixes bug
5970 24665; bugfix on 0.3.2.1-alpha.
5972 o Minor features (geoip):
5973 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
5976 o Minor bugfixes (hidden service v3):
5977 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
5978 the probability of reaching a service for a client missing
5979 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
5981 o Minor bugfixes (memory usage):
5982 - When queuing DESTROY cells on a channel, only queue the circuit-id
5983 and reason fields: not the entire 514-byte cell. This fix should
5984 help mitigate any bugs or attacks that fill up these queues, and
5985 free more RAM for other uses. Fixes bug 24666; bugfix
5988 o Minor bugfixes (scheduler, KIST):
5989 - Use a sane write limit for KISTLite when writing onto a connection
5990 buffer instead of using INT_MAX and shoving as much as it can.
5991 Because the OOM handler cleans up circuit queues, we are better
5992 off at keeping them in that queue instead of the connection's
5993 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
5996 Changes in version 0.3.2.7-rc - 2017-12-14
5997 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
5998 including some that could affect reliability or correctness.
6000 This is the first release candidate in the 0.3.2 series. If we find no
6001 new bugs or regression here, then the first stable 0.3.2. release will
6002 be nearly identical to this.
6004 o Major bugfixes (circuit prediction):
6005 - Fix circuit prediction logic so that a client doesn't treat a port
6006 as being "handled" by a circuit if that circuit already has
6007 isolation settings on it. This change should make Tor clients more
6008 responsive by improving their chances of having a pre-created
6009 circuit ready for use when a request arrives. Fixes bug 18859;
6010 bugfix on 0.2.3.3-alpha.
6012 o Minor features (logging):
6013 - Provide better warnings when the getrandom() syscall fails. Closes
6016 o Minor features (portability):
6017 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
6018 (It doesn't yet work with the sandbox enabled.) Closes
6021 o Minor bugfixes (bridge clients, bootstrap):
6022 - Retry directory downloads when we get our first bridge descriptor
6023 during bootstrap or while reconnecting to the network. Keep
6024 retrying every time we get a bridge descriptor, until we have a
6025 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
6026 - Stop delaying bridge descriptor fetches when we have cached bridge
6027 descriptors. Instead, only delay bridge descriptor fetches when we
6028 have at least one reachable bridge. Fixes part of bug 24367;
6029 bugfix on 0.2.0.3-alpha.
6030 - Stop delaying directory fetches when we have cached bridge
6031 descriptors. Instead, only delay bridge descriptor fetches when
6032 all our bridges are definitely unreachable. Fixes part of bug
6033 24367; bugfix on 0.2.0.3-alpha.
6035 o Minor bugfixes (compilation):
6036 - Fix a signed/unsigned comparison warning introduced by our fix to
6037 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6039 o Minor bugfixes (correctness):
6040 - Fix several places in our codebase where a C compiler would be
6041 likely to eliminate a check, based on assuming that undefined
6042 behavior had not happened elsewhere in the code. These cases are
6043 usually a sign of redundant checking or dubious arithmetic. Found
6044 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
6045 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
6048 o Minor bugfixes (onion service v3):
6049 - Fix a race where an onion service would launch a new intro circuit
6050 after closing an old one, but fail to register it before freeing
6051 the previously closed circuit. This bug was making the service
6052 unable to find the established intro circuit and thus not upload
6053 its descriptor, thus making a service unavailable for up to 24
6054 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
6056 o Minor bugfixes (scheduler, KIST):
6057 - Properly set the scheduler state of an unopened channel in the
6058 KIST scheduler main loop. This prevents a harmless but annoying
6059 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
6060 - Avoid a possible integer overflow when computing the available
6061 space on the TCP buffer of a channel. This had no security
6062 implications; but could make KIST allow too many cells on a
6063 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
6064 - Downgrade to "info" a harmless warning about the monotonic time
6065 moving backwards: This can happen on platform not supporting
6066 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6069 Changes in version 0.3.2.6-alpha - 2017-12-01
6070 This version of Tor is the latest in the 0.3.2 alpha series. It
6071 includes fixes for several important security issues. All Tor users
6072 should upgrade to this release, or to one of the other releases coming
6075 o Major bugfixes (security):
6076 - Fix a denial of service bug where an attacker could use a
6077 malformed directory object to cause a Tor instance to pause while
6078 OpenSSL would try to read a passphrase from the terminal. (Tor
6079 instances run without a terminal, which is the case for most Tor
6080 packages, are not impacted.) Fixes bug 24246; bugfix on every
6081 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6082 Found by OSS-Fuzz as testcase 6360145429790720.
6083 - Fix a denial of service issue where an attacker could crash a
6084 directory authority using a malformed router descriptor. Fixes bug
6085 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6087 - When checking for replays in the INTRODUCE1 cell data for a
6088 (legacy) onion service, correctly detect replays in the RSA-
6089 encrypted part of the cell. We were previously checking for
6090 replays on the entire cell, but those can be circumvented due to
6091 the malleability of Tor's legacy hybrid encryption. This fix helps
6092 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6093 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6096 o Major bugfixes (security, onion service v2):
6097 - Fix a use-after-free error that could crash v2 Tor onion services
6098 when they failed to open circuits while expiring introduction
6099 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6100 also tracked as TROVE-2017-013 and CVE-2017-8823.
6102 o Major bugfixes (security, relay):
6103 - When running as a relay, make sure that we never build a path
6104 through ourselves, even in the case where we have somehow lost the
6105 version of our descriptor appearing in the consensus. Fixes part
6106 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6107 as TROVE-2017-012 and CVE-2017-8822.
6108 - When running as a relay, make sure that we never choose ourselves
6109 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6110 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6112 o Minor feature (relay statistics):
6113 - Change relay bandwidth reporting stats interval from 4 hours to 24
6114 hours in order to reduce the efficiency of guard discovery
6115 attacks. Fixes ticket 23856.
6117 o Minor features (directory authority):
6118 - Add an IPv6 address for the "bastet" directory authority. Closes
6121 o Minor bugfixes (client):
6122 - By default, do not enable storage of client-side DNS values. These
6123 values were unused by default previously, but they should not have
6124 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
6127 Changes in version 0.3.1.9 - 2017-12-01:
6128 Tor 0.3.1.9 backports important security and stability fixes from the
6129 0.3.2 development series. All Tor users should upgrade to this
6130 release, or to another of the releases coming out today.
6132 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6133 - Fix a denial of service bug where an attacker could use a
6134 malformed directory object to cause a Tor instance to pause while
6135 OpenSSL would try to read a passphrase from the terminal. (Tor
6136 instances run without a terminal, which is the case for most Tor
6137 packages, are not impacted.) Fixes bug 24246; bugfix on every
6138 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6139 Found by OSS-Fuzz as testcase 6360145429790720.
6140 - Fix a denial of service issue where an attacker could crash a
6141 directory authority using a malformed router descriptor. Fixes bug
6142 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6144 - When checking for replays in the INTRODUCE1 cell data for a
6145 (legacy) onion service, correctly detect replays in the RSA-
6146 encrypted part of the cell. We were previously checking for
6147 replays on the entire cell, but those can be circumvented due to
6148 the malleability of Tor's legacy hybrid encryption. This fix helps
6149 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6150 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6153 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6154 - Fix a use-after-free error that could crash v2 Tor onion services
6155 when they failed to open circuits while expiring introduction
6156 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6157 also tracked as TROVE-2017-013 and CVE-2017-8823.
6159 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6160 - When running as a relay, make sure that we never build a path
6161 through ourselves, even in the case where we have somehow lost the
6162 version of our descriptor appearing in the consensus. Fixes part
6163 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6164 as TROVE-2017-012 and CVE-2017-8822.
6165 - When running as a relay, make sure that we never choose ourselves
6166 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6167 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6169 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6170 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6171 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6172 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6173 identifying and finding a workaround to this bug and to Moritz,
6174 Arthur Edelstein, and Roger for helping to track it down and
6177 o Minor features (bridge):
6178 - Bridges now include notice in their descriptors that they are
6179 bridges, and notice of their distribution status, based on their
6180 publication settings. Implements ticket 18329. For more fine-
6181 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6184 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6185 - Add an IPv6 address for the "bastet" directory authority. Closes
6188 o Minor features (geoip):
6189 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6192 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6193 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6194 relays, to prevent spurious address resolutions and descriptor
6195 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6196 bugfix on in 0.2.8.1-alpha.
6198 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6199 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6200 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6202 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6203 - When a circuit is marked for close, do not attempt to package any
6204 cells for channels on that circuit. Previously, we would detect
6205 this condition lower in the call stack, when we noticed that the
6206 circuit had no attached channel, and log an annoying message.
6207 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6209 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
6210 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6211 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6214 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6215 - Avoid a crash when transitioning from client mode to bridge mode.
6216 Previously, we would launch the worker threads whenever our
6217 "public server" mode changed, but not when our "server" mode
6218 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6221 Changes in version 0.3.0.13 - 2017-12-01
6222 Tor 0.3.0.13 backports important security and stability bugfixes from
6223 later Tor releases. All Tor users should upgrade to this release, or
6224 to another of the releases coming out today.
6226 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6227 2018. If you need a release with long-term support, please stick with
6228 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6230 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6231 - Fix a denial of service bug where an attacker could use a
6232 malformed directory object to cause a Tor instance to pause while
6233 OpenSSL would try to read a passphrase from the terminal. (Tor
6234 instances run without a terminal, which is the case for most Tor
6235 packages, are not impacted.) Fixes bug 24246; bugfix on every
6236 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6237 Found by OSS-Fuzz as testcase 6360145429790720.
6238 - Fix a denial of service issue where an attacker could crash a
6239 directory authority using a malformed router descriptor. Fixes bug
6240 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6242 - When checking for replays in the INTRODUCE1 cell data for a
6243 (legacy) onion service, correctly detect replays in the RSA-
6244 encrypted part of the cell. We were previously checking for
6245 replays on the entire cell, but those can be circumvented due to
6246 the malleability of Tor's legacy hybrid encryption. This fix helps
6247 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6248 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6251 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6252 - Fix a use-after-free error that could crash v2 Tor onion services
6253 when they failed to open circuits while expiring introduction
6254 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6255 also tracked as TROVE-2017-013 and CVE-2017-8823.
6257 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6258 - When running as a relay, make sure that we never build a path
6259 through ourselves, even in the case where we have somehow lost the
6260 version of our descriptor appearing in the consensus. Fixes part
6261 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6262 as TROVE-2017-012 and CVE-2017-8822.
6263 - When running as a relay, make sure that we never choose ourselves
6264 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6265 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6267 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6268 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6269 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6270 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6271 identifying and finding a workaround to this bug and to Moritz,
6272 Arthur Edelstein, and Roger for helping to track it down and
6275 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6276 - Enable a couple of pieces of Windows hardening: one
6277 (HeapEnableTerminationOnCorruption) that has been on-by-default
6278 since Windows 8, and unavailable before Windows 7; and one
6279 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6280 affect us, but shouldn't do any harm. Closes ticket 21953.
6282 o Minor features (bridge, backport from 0.3.1.9):
6283 - Bridges now include notice in their descriptors that they are
6284 bridges, and notice of their distribution status, based on their
6285 publication settings. Implements ticket 18329. For more fine-
6286 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6289 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6290 - Add an IPv6 address for the "bastet" directory authority. Closes
6293 o Minor features (geoip):
6294 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6297 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6298 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6299 relays, to prevent spurious address resolutions and descriptor
6300 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6301 bugfix on in 0.2.8.1-alpha.
6303 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6304 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6305 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6307 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6308 - When a circuit is marked for close, do not attempt to package any
6309 cells for channels on that circuit. Previously, we would detect
6310 this condition lower in the call stack, when we noticed that the
6311 circuit had no attached channel, and log an annoying message.
6312 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6314 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6315 - Avoid a crash when transitioning from client mode to bridge mode.
6316 Previously, we would launch the worker threads whenever our
6317 "public server" mode changed, but not when our "server" mode
6318 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6320 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6321 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6322 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6325 Changes in version 0.2.9.14 - 2017-12-01
6326 Tor 0.3.0.13 backports important security and stability bugfixes from
6327 later Tor releases. All Tor users should upgrade to this release, or
6328 to another of the releases coming out today.
6330 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6331 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6332 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6333 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6334 identifying and finding a workaround to this bug and to Moritz,
6335 Arthur Edelstein, and Roger for helping to track it down and
6338 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6339 - Fix a denial of service bug where an attacker could use a
6340 malformed directory object to cause a Tor instance to pause while
6341 OpenSSL would try to read a passphrase from the terminal. (Tor
6342 instances run without a terminal, which is the case for most Tor
6343 packages, are not impacted.) Fixes bug 24246; bugfix on every
6344 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6345 Found by OSS-Fuzz as testcase 6360145429790720.
6346 - Fix a denial of service issue where an attacker could crash a
6347 directory authority using a malformed router descriptor. Fixes bug
6348 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6350 - When checking for replays in the INTRODUCE1 cell data for a
6351 (legacy) onion service, correctly detect replays in the RSA-
6352 encrypted part of the cell. We were previously checking for
6353 replays on the entire cell, but those can be circumvented due to
6354 the malleability of Tor's legacy hybrid encryption. This fix helps
6355 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6356 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6359 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6360 - Fix a use-after-free error that could crash v2 Tor onion services
6361 when they failed to open circuits while expiring introduction
6362 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6363 also tracked as TROVE-2017-013 and CVE-2017-8823.
6365 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6366 - When running as a relay, make sure that we never build a path
6367 through ourselves, even in the case where we have somehow lost the
6368 version of our descriptor appearing in the consensus. Fixes part
6369 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6370 as TROVE-2017-012 and CVE-2017-8822.
6372 o Minor features (bridge, backport from 0.3.1.9):
6373 - Bridges now include notice in their descriptors that they are
6374 bridges, and notice of their distribution status, based on their
6375 publication settings. Implements ticket 18329. For more fine-
6376 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6379 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6380 - Add an IPv6 address for the "bastet" directory authority. Closes
6383 o Minor features (geoip):
6384 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6387 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6388 - Enable a couple of pieces of Windows hardening: one
6389 (HeapEnableTerminationOnCorruption) that has been on-by-default
6390 since Windows 8, and unavailable before Windows 7; and one
6391 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6392 affect us, but shouldn't do any harm. Closes ticket 21953.
6394 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6395 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6396 relays, to prevent spurious address resolutions and descriptor
6397 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6398 bugfix on in 0.2.8.1-alpha.
6400 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6401 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6402 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6404 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6405 - When a circuit is marked for close, do not attempt to package any
6406 cells for channels on that circuit. Previously, we would detect
6407 this condition lower in the call stack, when we noticed that the
6408 circuit had no attached channel, and log an annoying message.
6409 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6411 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6412 - Avoid a crash when transitioning from client mode to bridge mode.
6413 Previously, we would launch the worker threads whenever our
6414 "public server" mode changed, but not when our "server" mode
6415 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6417 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6418 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6419 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6422 Changes in version 0.2.8.17 - 2017-12-01
6423 Tor 0.2.8.17 backports important security and stability bugfixes from
6424 later Tor releases. All Tor users should upgrade to this release, or
6425 to another of the releases coming out today.
6427 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6428 2018. If you need a release with long-term support, please upgrade with
6429 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6431 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6432 - Fix a denial of service bug where an attacker could use a
6433 malformed directory object to cause a Tor instance to pause while
6434 OpenSSL would try to read a passphrase from the terminal. (Tor
6435 instances run without a terminal, which is the case for most Tor
6436 packages, are not impacted.) Fixes bug 24246; bugfix on every
6437 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6438 Found by OSS-Fuzz as testcase 6360145429790720.
6439 - When checking for replays in the INTRODUCE1 cell data for a
6440 (legacy) onion service, correctly detect replays in the RSA-
6441 encrypted part of the cell. We were previously checking for
6442 replays on the entire cell, but those can be circumvented due to
6443 the malleability of Tor's legacy hybrid encryption. This fix helps
6444 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6445 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6448 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6449 - Fix a use-after-free error that could crash v2 Tor onion services
6450 when they failed to open circuits while expiring introduction
6451 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6452 also tracked as TROVE-2017-013 and CVE-2017-8823.
6454 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6455 - When running as a relay, make sure that we never build a path through
6456 ourselves, even in the case where we have somehow lost the version of
6457 our descriptor appearing in the consensus. Fixes part of bug 21534;
6458 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6461 o Minor features (bridge, backport from 0.3.1.9):
6462 - Bridges now include notice in their descriptors that they are
6463 bridges, and notice of their distribution status, based on their
6464 publication settings. Implements ticket 18329. For more fine-
6465 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6468 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6469 - Add an IPv6 address for the "bastet" directory authority. Closes
6472 o Minor features (geoip):
6473 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6476 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6477 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6478 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6481 Changes in version 0.2.5.16 - 2017-12-01
6482 Tor 0.2.5.13 backports important security and stability bugfixes from
6483 later Tor releases. All Tor users should upgrade to this release, or
6484 to another of the releases coming out today.
6486 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6487 2018. If you need a release with long-term support, please upgrade to
6488 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6490 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6491 - Fix a denial of service bug where an attacker could use a
6492 malformed directory object to cause a Tor instance to pause while
6493 OpenSSL would try to read a passphrase from the terminal. (Tor
6494 instances run without a terminal, which is the case for most Tor
6495 packages, are not impacted.) Fixes bug 24246; bugfix on every
6496 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6497 Found by OSS-Fuzz as testcase 6360145429790720.
6498 - When checking for replays in the INTRODUCE1 cell data for a
6499 (legacy) onion service, correctly detect replays in the RSA-
6500 encrypted part of the cell. We were previously checking for
6501 replays on the entire cell, but those can be circumvented due to
6502 the malleability of Tor's legacy hybrid encryption. This fix helps
6503 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6504 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6507 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6508 - When running as a relay, make sure that we never build a path
6509 through ourselves, even in the case where we have somehow lost the
6510 version of our descriptor appearing in the consensus. Fixes part
6511 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6512 as TROVE-2017-012 and CVE-2017-8822.
6514 o Minor features (bridge, backport from 0.3.1.9):
6515 - Bridges now include notice in their descriptors that they are
6516 bridges, and notice of their distribution status, based on their
6517 publication settings. Implements ticket 18329. For more fine-
6518 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6521 o Minor features (geoip):
6522 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6526 Changes in version 0.3.2.5-alpha - 2017-11-22
6527 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6528 fixes several stability and reliability bugs, including a fix for
6529 intermittent bootstrapping failures that some people have been seeing
6530 since the 0.3.0.x series.
6532 Please test this alpha out -- many of these fixes will soon be
6533 backported to stable Tor versions if no additional bugs are found
6536 o Major bugfixes (bootstrapping):
6537 - Fetch descriptors aggressively whenever we lack enough to build
6538 circuits, regardless of how many descriptors we are missing.
6539 Previously, we would delay launching the fetch when we had fewer
6540 than 15 missing descriptors, even if some of those descriptors
6541 were blocking circuits from building. Fixes bug 23985; bugfix on
6542 0.1.1.11-alpha. The effects of this bug became worse in
6543 0.3.0.3-alpha, when we began treating missing descriptors from our
6544 primary guards as a reason to delay circuits.
6545 - Don't try fetching microdescriptors from relays that have failed
6546 to deliver them in the past. Fixes bug 23817; bugfix
6549 o Minor features (directory authority):
6550 - Make the "Exit" flag assignment only depend on whether the exit
6551 policy allows connections to ports 80 and 443. Previously relays
6552 would get the Exit flag if they allowed connections to one of
6553 these ports and also port 6667. Resolves ticket 23637.
6555 o Minor features (geoip):
6556 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6559 o Minor features (linux seccomp2 sandbox):
6560 - Update the sandbox rules so that they should now work correctly
6561 with Glibc 2.26. Closes ticket 24315.
6563 o Minor features (logging):
6564 - Downgrade a pair of log messages that could occur when an exit's
6565 resolver gave us an unusual (but not forbidden) response. Closes
6567 - Improve the message we log when re-enabling circuit build timeouts
6568 after having received a consensus. Closes ticket 20963.
6570 o Minor bugfixes (compilation):
6571 - Fix a memory leak warning in one of the libevent-related
6572 configuration tests that could occur when manually specifying
6573 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6574 Found and patched by Alex Xu.
6575 - When detecting OpenSSL on Windows from our configure script, make
6576 sure to try linking with the ws2_32 library. Fixes bug 23783;
6577 bugfix on 0.3.2.2-alpha.
6579 o Minor bugfixes (control port, linux seccomp2 sandbox):
6580 - Avoid a crash when attempting to use the seccomp2 sandbox together
6581 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6584 o Minor bugfixes (control port, onion services):
6585 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6586 HS_DESC event when a service is not able to upload a descriptor.
6587 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6589 o Minor bugfixes (directory cache):
6590 - Recover better from empty or corrupt files in the consensus cache
6591 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6592 - When a consensus diff calculation is only partially successful,
6593 only record the successful parts as having succeeded. Partial
6594 success can happen if (for example) one compression method fails
6595 but the others succeed. Previously we misrecorded all the
6596 calculations as having succeeded, which would later cause a
6597 nonfatal assertion failure. Fixes bug 24086; bugfix
6600 o Minor bugfixes (logging):
6601 - Only log once if we notice that KIST support is gone. Fixes bug
6602 24158; bugfix on 0.3.2.1-alpha.
6603 - Suppress a log notice when relay descriptors arrive. We already
6604 have a bootstrap progress for this so no need to log notice
6605 everytime tor receives relay descriptors. Microdescriptors behave
6606 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6608 o Minor bugfixes (network layer):
6609 - When closing a connection via close_connection_immediately(), we
6610 mark it as "not blocked on bandwidth", to prevent later calls from
6611 trying to unblock it, and give it permission to read. This fixes a
6612 backtrace warning that can happen on relays under various
6613 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6615 o Minor bugfixes (onion services):
6616 - The introduction circuit was being timed out too quickly while
6617 waiting for the rendezvous circuit to complete. Keep the intro
6618 circuit around longer instead of timing out and reopening new ones
6619 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6620 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6621 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6623 - Silence a warning about failed v3 onion descriptor uploads that
6624 can happen naturally under certain edge cases. Fixes part of bug
6625 23662; bugfix on 0.3.2.1-alpha.
6627 o Minor bugfixes (tests):
6628 - Fix a memory leak in one of the bridge-distribution test cases.
6629 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
6630 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
6631 to correctly handle cases where a caller gives it an RSA key of
6632 under 160 bits. (This is not actually a bug in Tor itself, but
6633 rather in our fuzzing code.) Fixes bug 24247; bugfix on
6634 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
6637 - Add notes in man page regarding OS support for the various
6638 scheduler types. Attempt to use less jargon in the scheduler
6639 section. Closes ticket 24254.
6642 Changes in version 0.3.2.4-alpha - 2017-11-08
6643 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
6644 It fixes several stability and reliability bugs, especially including
6645 a major reliability issue that has been plaguing fast exit relays in
6648 o Major bugfixes (exit relays, DNS):
6649 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6650 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6651 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6652 identifying and finding a workaround to this bug and to Moritz,
6653 Arthur Edelstein, and Roger for helping to track it down and
6656 o Major bugfixes (scheduler, channel):
6657 - Stop processing scheduled channels if they closed while flushing
6658 cells. This can happen if the write on the connection fails
6659 leading to the channel being closed while in the scheduler loop.
6660 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
6662 o Minor features (logging, scheduler):
6663 - Introduce a SCHED_BUG() function to log extra information about
6664 the scheduler state if we ever catch a bug in the scheduler.
6665 Closes ticket 23753.
6667 o Minor features (removed deprecations):
6668 - The ClientDNSRejectInternalAddresses flag can once again be set in
6669 non-testing Tor networks, so long as they do not use the default
6670 directory authorities. This change also removes the deprecation of
6671 this flag from 0.2.9.2-alpha. Closes ticket 21031.
6673 o Minor features (testing):
6674 - Our fuzzing tests now test the encrypted portions of v3 onion
6675 service descriptors. Implements more of 21509.
6677 o Minor bugfixes (directory client):
6678 - On failure to download directory information, delay retry attempts
6679 by a random amount based on the "decorrelated jitter" algorithm.
6680 Our previous delay algorithm tended to produce extra-long delays
6681 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
6683 o Minor bugfixes (IPv6, v3 single onion services):
6684 - Remove buggy code for IPv6-only v3 single onion services, and
6685 reject attempts to configure them. This release supports IPv4,
6686 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
6687 stack v3 single onion services. Fixes bug 23820; bugfix
6690 o Minor bugfixes (logging, relay):
6691 - Give only a protocol warning when the ed25519 key is not
6692 consistent between the descriptor and microdescriptor of a relay.
6693 This can happen, for instance, if the relay has been flagged
6694 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
6696 o Minor bugfixes (manpage, onion service):
6697 - Document that the HiddenServiceNumIntroductionPoints option is
6698 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
6699 bugfix on 0.3.2.1-alpha.
6701 o Minor bugfixes (memory leaks):
6702 - Fix a minor memory leak at exit in the KIST scheduler. This bug
6703 should have no user-visible impact. Fixes bug 23774; bugfix
6705 - Fix a memory leak when decrypting a badly formatted v3 onion
6706 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
6707 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
6709 o Minor bugfixes (onion services):
6710 - Cache some needed onion service client information instead of
6711 constantly computing it over and over again. Fixes bug 23623;
6712 bugfix on 0.3.2.1-alpha.
6713 - Properly retry HSv3 descriptor fetches when missing required
6714 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
6716 o Minor bugfixes (path selection):
6717 - When selecting relays by bandwidth, avoid a rounding error that
6718 could sometimes cause load to be imbalanced incorrectly.
6719 Previously, we would always round upwards; now, we round towards
6720 the nearest integer. This had the biggest effect when a relay's
6721 weight adjustments should have given it weight 0, but it got
6722 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
6723 - When calculating the fraction of nodes that have descriptors, and
6724 all nodes in the network have zero bandwidths, count the number of
6725 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
6726 - Actually log the total bandwidth in compute_weighted_bandwidths().
6727 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
6729 o Minor bugfixes (relay, crash):
6730 - Avoid a crash when transitioning from client mode to bridge mode.
6731 Previously, we would launch the worker threads whenever our
6732 "public server" mode changed, but not when our "server" mode
6733 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6735 o Minor bugfixes (testing):
6736 - Fix a spurious fuzzing-only use of an uninitialized value. Found
6737 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
6738 - Test that IPv6-only clients can use microdescriptors when running
6739 "make test-network-all". Requires chutney master 61c28b9 or later.
6740 Closes ticket 24109.
6743 Changes in version 0.3.2.3-alpha - 2017-10-27
6744 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
6745 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
6746 directory authority, Bastet.
6748 o Directory authority changes:
6749 - Add "Bastet" as a ninth directory authority to the default list.
6750 Closes ticket 23910.
6751 - The directory authority "Longclaw" has changed its IP address.
6752 Closes ticket 23592.
6754 o Minor features (bridge):
6755 - Bridge relays can now set the BridgeDistribution config option to
6756 add a "bridge-distribution-request" line to their bridge
6757 descriptor, which tells BridgeDB how they'd like their bridge
6758 address to be given out. (Note that as of Oct 2017, BridgeDB does
6759 not yet implement this feature.) As a side benefit, this feature
6760 provides a way to distinguish bridge descriptors from non-bridge
6761 descriptors. Implements tickets 18329.
6763 o Minor features (client, entry guards):
6764 - Improve log messages when missing descriptors for primary guards.
6765 Resolves ticket 23670.
6767 o Minor features (geoip):
6768 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6771 o Minor bugfixes (bridge):
6772 - Overwrite the bridge address earlier in the process of retrieving
6773 its descriptor, to make sure we reach it on the configured
6774 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
6776 o Minor bugfixes (documentation):
6777 - Document better how to read gcov, and what our gcov postprocessing
6778 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
6780 o Minor bugfixes (entry guards):
6781 - Tor now updates its guard state when it reads a consensus
6782 regardless of whether it's missing descriptors. That makes tor use
6783 its primary guards to fetch descriptors in some edge cases where
6784 it would previously have used fallback directories. Fixes bug
6785 23862; bugfix on 0.3.0.1-alpha.
6787 o Minor bugfixes (hidden service client):
6788 - When handling multiple SOCKS request for the same .onion address,
6789 only fetch the service descriptor once.
6790 - When a descriptor fetch fails with a non-recoverable error, close
6791 all pending SOCKS requests for that .onion. Fixes bug 23653;
6792 bugfix on 0.3.2.1-alpha.
6794 o Minor bugfixes (hidden service):
6795 - Always regenerate missing hidden service public key files. Prior
6796 to this, if the public key was deleted from disk, it wouldn't get
6797 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
6799 - Make sure that we have a usable ed25519 key when the intro point
6800 relay supports ed25519 link authentication. Fixes bug 24002;
6801 bugfix on 0.3.2.1-alpha.
6803 o Minor bugfixes (hidden service, v2):
6804 - When reloading configured hidden services, copy all information
6805 from the old service object. Previously, some data was omitted,
6806 causing delays in descriptor upload, and other bugs. Fixes bug
6807 23790; bugfix on 0.2.1.9-alpha.
6809 o Minor bugfixes (memory safety, defensive programming):
6810 - Clear the target address when node_get_prim_orport() returns
6811 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6813 o Minor bugfixes (relay):
6814 - Avoid a BUG warning when receiving a dubious CREATE cell while an
6815 option transition is in progress. Fixes bug 23952; bugfix
6818 o Minor bugfixes (testing):
6819 - Adjust the GitLab CI configuration to more closely match that of
6820 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
6821 - Prevent scripts/test/coverage from attempting to move gcov output
6822 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
6823 - When running unit tests as root, skip a test that would fail
6824 because it expects a permissions error. This affects some
6825 continuous integration setups. Fixes bug 23758; bugfix
6827 - Stop unconditionally mirroring the tor repository in GitLab CI.
6828 This prevented developers from enabling GitLab CI on master. Fixes
6829 bug 23755; bugfix on 0.3.2.2-alpha.
6830 - Fix the hidden service v3 descriptor decoding fuzzing to use the
6831 latest decoding API correctly. Fixes bug 21509; bugfix
6834 o Minor bugfixes (warnings):
6835 - When we get an HTTP request on a SOCKS port, tell the user about
6836 the new HTTPTunnelPort option. Previously, we would give a "Tor is
6837 not an HTTP Proxy" message, which stopped being true when
6838 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
6842 Changes in version 0.2.5.15 - 2017-10-25
6843 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
6844 series. It also adds a new directory authority, Bastet.
6846 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6847 2018. If you need a release with long-term support, please upgrade to
6848 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6850 o Directory authority changes:
6851 - Add "Bastet" as a ninth directory authority to the default list.
6852 Closes ticket 23910.
6853 - The directory authority "Longclaw" has changed its IP address.
6854 Closes ticket 23592.
6856 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
6857 - Avoid an assertion failure bug affecting our implementation of
6858 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
6859 handling of "0xx" differs from what we had expected. Fixes bug
6860 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
6862 o Minor features (geoip):
6863 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6866 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
6867 - Fix a memset() off the end of an array when packing cells. This
6868 bug should be harmless in practice, since the corrupted bytes are
6869 still in the same structure, and are always padding bytes,
6870 ignored, or immediately overwritten, depending on compiler
6871 behavior. Nevertheless, because the memset()'s purpose is to make
6872 sure that any other cell-handling bugs can't expose bytes to the
6873 network, we need to fix it. Fixes bug 22737; bugfix on
6874 0.2.4.11-alpha. Fixes CID 1401591.
6876 o Build features (backport from 0.3.1.5-alpha):
6877 - Tor's repository now includes a Travis Continuous Integration (CI)
6878 configuration file (.travis.yml). This is meant to help new
6879 developers and contributors who fork Tor to a Github repository be
6880 better able to test their changes, and understand what we expect
6881 to pass. To use this new build feature, you must fork Tor to your
6882 Github account, then go into the "Integrations" menu in the
6883 repository settings for your fork and enable Travis, then push
6884 your changes. Closes ticket 22636.
6887 Changes in version 0.2.8.16 - 2017-10-25
6888 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
6889 series, including a bugfix for a crash issue that had affected relays
6890 under memory pressure. It also adds a new directory authority, Bastet.
6892 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6893 2018. If you need a release with long-term support, please stick with
6894 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6896 o Directory authority changes:
6897 - Add "Bastet" as a ninth directory authority to the default list.
6898 Closes ticket 23910.
6899 - The directory authority "Longclaw" has changed its IP address.
6900 Closes ticket 23592.
6902 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6903 - Fix a timing-based assertion failure that could occur when the
6904 circuit out-of-memory handler freed a connection's output buffer.
6905 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6907 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6908 - Remove longclaw's IPv6 address, as it will soon change. Authority
6909 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6910 3/8 directory authorities with IPv6 addresses, but there are also
6911 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6913 o Minor features (geoip):
6914 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6918 Changes in version 0.2.9.13 - 2017-10-25
6919 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
6920 series, including a bugfix for a crash issue that had affected relays
6921 under memory pressure. It also adds a new directory authority, Bastet.
6923 o Directory authority changes:
6924 - Add "Bastet" as a ninth directory authority to the default list.
6925 Closes ticket 23910.
6926 - The directory authority "Longclaw" has changed its IP address.
6927 Closes ticket 23592.
6929 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6930 - Fix a timing-based assertion failure that could occur when the
6931 circuit out-of-memory handler freed a connection's output buffer.
6932 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6934 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6935 - Remove longclaw's IPv6 address, as it will soon change. Authority
6936 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6937 3/8 directory authorities with IPv6 addresses, but there are also
6938 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6940 o Minor features (geoip):
6941 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6944 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6945 - When a directory authority rejects a descriptor or extrainfo with
6946 a given digest, mark that digest as undownloadable, so that we do
6947 not attempt to download it again over and over. We previously
6948 tried to avoid downloading such descriptors by other means, but we
6949 didn't notice if we accidentally downloaded one anyway. This
6950 behavior became problematic in 0.2.7.2-alpha, when authorities
6951 began pinning Ed25519 keys. Fixes bug 22349; bugfix
6954 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
6955 - Clear the address when node_get_prim_orport() returns early.
6956 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
6958 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
6959 - When running as a Windows service, set the ID of the main thread
6960 correctly. Failure to do so made us fail to send log messages to
6961 the controller in 0.2.1.16-rc, slowed down controller event
6962 delivery in 0.2.7.3-rc and later, and crash with an assertion
6963 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
6964 Patch and diagnosis from "Vort".
6967 Changes in version 0.3.0.12 - 2017-10-25
6968 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
6969 series, including a bugfix for a crash issue that had affected relays
6970 under memory pressure. It also adds a new directory authority, Bastet.
6972 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6973 2018. If you need a release with long-term support, please stick with
6974 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6976 o Directory authority changes:
6977 - Add "Bastet" as a ninth directory authority to the default list.
6978 Closes ticket 23910.
6979 - The directory authority "Longclaw" has changed its IP address.
6980 Closes ticket 23592.
6982 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
6983 - Fix a timing-based assertion failure that could occur when the
6984 circuit out-of-memory handler freed a connection's output buffer.
6985 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
6987 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
6988 - Remove longclaw's IPv6 address, as it will soon change. Authority
6989 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
6990 3/8 directory authorities with IPv6 addresses, but there are also
6991 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
6993 o Minor features (geoip):
6994 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
6997 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
6998 - When a directory authority rejects a descriptor or extrainfo with
6999 a given digest, mark that digest as undownloadable, so that we do
7000 not attempt to download it again over and over. We previously
7001 tried to avoid downloading such descriptors by other means, but we
7002 didn't notice if we accidentally downloaded one anyway. This
7003 behavior became problematic in 0.2.7.2-alpha, when authorities
7004 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7007 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7008 - Avoid a possible double close of a circuit by the intro point on
7009 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7010 bugfix on 0.3.0.1-alpha.
7012 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7013 - Clear the address when node_get_prim_orport() returns early.
7014 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7016 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7017 - When running as a Windows service, set the ID of the main thread
7018 correctly. Failure to do so made us fail to send log messages to
7019 the controller in 0.2.1.16-rc, slowed down controller event
7020 delivery in 0.2.7.3-rc and later, and crash with an assertion
7021 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7022 Patch and diagnosis from "Vort".
7025 Changes in version 0.3.1.8 - 2017-10-25
7026 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7027 It includes several bugfixes, including a bugfix for a crash issue
7028 that had affected relays under memory pressure. It also adds
7029 a new directory authority, Bastet.
7031 o Directory authority changes:
7032 - Add "Bastet" as a ninth directory authority to the default list.
7033 Closes ticket 23910.
7034 - The directory authority "Longclaw" has changed its IP address.
7035 Closes ticket 23592.
7037 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7038 - Fix a timing-based assertion failure that could occur when the
7039 circuit out-of-memory handler freed a connection's output buffer.
7040 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7042 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7043 - Remove longclaw's IPv6 address, as it will soon change. Authority
7044 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7045 3/8 directory authorities with IPv6 addresses, but there are also
7046 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7048 o Minor features (geoip):
7049 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7052 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
7053 - Fix a compilation warning when building with zstd support on
7054 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7055 and fixed by Andreas Stieger.
7057 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
7058 - Handle a pathological case when decompressing Zstandard data when
7059 the output buffer size is zero. Fixes bug 23551; bugfix
7062 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
7063 - Remove the length limit on HTTP status lines that authorities can
7064 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
7066 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7067 - Avoid a possible double close of a circuit by the intro point on
7068 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7069 bugfix on 0.3.0.1-alpha.
7071 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7072 - Clear the address when node_get_prim_orport() returns early.
7073 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7075 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
7076 - Fix additional channelpadding unit test failures by using mocked
7077 time instead of actual time for all tests. Fixes bug 23608; bugfix
7081 Changes in version 0.3.2.2-alpha - 2017-09-29
7082 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
7083 release fixes several minor bugs in the new scheduler and next-
7084 generation onion services; both features were newly added in the 0.3.2
7085 series. Other fixes in this alpha include several fixes for non-fatal
7086 tracebacks which would appear in logs.
7088 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
7089 alpha does not contain any substantial new features. Minor features
7090 include better testing and logging.
7092 The following comprises the complete list of changes included
7095 o Major bugfixes (relay, crash, assertion failure):
7096 - Fix a timing-based assertion failure that could occur when the
7097 circuit out-of-memory handler freed a connection's output buffer.
7098 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7100 o Major bugfixes (scheduler):
7101 - If a channel is put into the scheduler's pending list, then it
7102 starts closing, and then if the scheduler runs before it finishes
7103 closing, the scheduler will get stuck trying to flush its cells
7104 while the lower layers refuse to cooperate. Fix that race
7105 condition by giving the scheduler an escape method. Fixes bug
7106 23676; bugfix on 0.3.2.1-alpha.
7108 o Minor features (build, compilation):
7109 - The "check-changes" feature is now part of the "make check" tests;
7110 we'll use it to try to prevent misformed changes files from
7111 accumulating. Closes ticket 23564.
7112 - Tor builds should now fail if there are any mismatches between the
7113 C type representing a configuration variable and the C type the
7114 data-driven parser uses to store a value there. Previously, we
7115 needed to check these by hand, which sometimes led to mistakes.
7116 Closes ticket 23643.
7118 o Minor features (directory authorities):
7119 - Remove longclaw's IPv6 address, as it will soon change. Authority
7120 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7121 3/8 directory authorities with IPv6 addresses, but there are also
7122 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7124 o Minor features (hidden service, circuit, logging):
7125 - Improve logging of many callsite in the circuit subsystem to print
7126 the circuit identifier(s).
7127 - Log when we cleanup an intro point from a service so we know when
7128 and for what reason it happened. Closes ticket 23604.
7130 o Minor features (logging):
7131 - Log more circuit information whenever we are about to try to
7132 package a relay cell on a circuit with a nonexistent n_chan.
7133 Attempt to diagnose ticket 8185.
7134 - Improve info-level log identification of particular circuits, to
7135 help with debugging. Closes ticket 23645.
7137 o Minor features (relay):
7138 - When choosing which circuits can be expired as unused, consider
7139 circuits from clients even if those clients used regular CREATE
7140 cells to make them; and do not consider circuits from relays even
7141 if they were made with CREATE_FAST. Part of ticket 22805.
7143 o Minor features (robustness):
7144 - Change several fatal assertions when flushing buffers into non-
7145 fatal assertions, to prevent any recurrence of 23690.
7147 o Minor features (spec conformance, bridge, diagnostic):
7148 - When handling the USERADDR command on an ExtOrPort, warn when the
7149 transports provides a USERADDR with no port. In a future version,
7150 USERADDR commands of this format may be rejected. Detects problems
7151 related to ticket 23080.
7153 o Minor features (testing):
7154 - Add a unit test to make sure that our own generated platform
7155 string will be accepted by directory authorities. Closes
7158 o Minor bugfixes (bootstrapping):
7159 - When warning about state file clock skew, report the correct
7160 direction for the detected skew. Fixes bug 23606; bugfix
7162 - Avoid an assertion failure when logging a state file clock skew
7163 very early in bootstrapping. Fixes bug 23607; bugfix
7166 o Minor bugfixes (build, compilation):
7167 - Fix a compilation warning when building with zstd support on
7168 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7169 and fixed by Andreas Stieger.
7170 - When searching for OpenSSL, don't accept any OpenSSL library that
7171 lacks TLSv1_1_method(): Tor doesn't build with those versions.
7172 Additionally, look in /usr/local/opt/openssl, if it's present.
7173 These changes together repair the default build on OSX systems
7174 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
7176 o Minor bugfixes (compression):
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 (documentation):
7182 - Fix manpage to not refer to the obsolete (and misspelled)
7183 UseEntryGuardsAsDirectoryGuards parameter in the description of
7184 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
7186 o Minor bugfixes (hidden service v3):
7187 - Don't log an assertion failure when we can't find the right
7188 information to extend to an introduction point. In rare cases,
7189 this could happen, causing a warning, even though tor would
7190 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
7191 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
7192 much bigger so the rendezvous point can't distinguish which hidden
7193 service protocol is being used. Fixes bug 23420; bugfix
7196 o Minor bugfixes (hidden service, relay):
7197 - Avoid a possible double close of a circuit by the intro point on
7198 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7199 bugfix on 0.3.0.1-alpha.
7201 o Minor bugfixes (logging, relay shutdown, annoyance):
7202 - When a circuit is marked for close, do not attempt to package any
7203 cells for channels on that circuit. Previously, we would detect
7204 this condition lower in the call stack, when we noticed that the
7205 circuit had no attached channel, and log an annoying message.
7206 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
7208 o Minor bugfixes (scheduler):
7209 - When switching schedulers due to a consensus change, we didn't
7210 give the new scheduler a chance to react to the consensus. Fix
7211 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
7212 - Make the KISTSchedRunInterval option a non negative value. With
7213 this, the way to disable KIST through the consensus is to set it
7214 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
7215 - Only notice log the selected scheduler when we switch scheduler
7216 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
7217 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
7218 by a different tv_usec data type. Fixes bug 23575; bugfix
7220 - Make a hard exit if tor is unable to pick a scheduler which can
7221 happen if the user specifies a scheduler type that is not
7222 supported and not other types in Schedulers. Fixes bug 23581;
7223 bugfix on 0.3.2.1-alpha.
7224 - Properly initialize the scheduler last run time counter so it is
7225 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
7227 o Minor bugfixes (testing):
7228 - Capture and detect several "Result does not fit" warnings in unit
7229 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
7231 - Fix additional channelpadding unit test failures by using mocked
7232 time instead of actual time for all tests. Fixes bug 23608; bugfix
7234 - The removal of some old scheduler options caused some tests to
7235 fail on BSD systems. Assume current behavior is correct and make
7236 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
7238 o Code simplification and refactoring:
7239 - Remove various ways of testing circuits and connections for
7240 "clientness"; instead, favor channel_is_client(). Part of
7243 o Deprecated features:
7244 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
7245 now deprecated; they do not apply to relays, and they have had no
7246 effect on clients since 0.2.8.x. Closes ticket 19704.
7249 - HiddenServiceVersion man page entry wasn't mentioning the now
7250 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
7251 - Clarify that the Address option is entirely about setting an
7252 advertised IPv4 address. Closes ticket 18891.
7253 - Clarify the manpage's use of the term "address" to clarify what
7254 kind of address is intended. Closes ticket 21405.
7255 - Document that onion service subdomains are allowed, and ignored.
7256 Closes ticket 18736.
7259 Changes in version 0.3.2.1-alpha - 2017-09-18
7260 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
7261 includes support for our next-generation ("v3") onion service
7262 protocol, and adds a new circuit scheduler for more responsive
7263 forwarding decisions from relays. There are also numerous other small
7264 features and bugfixes here.
7266 Below are the changes since Tor 0.3.1.7.
7268 o Major feature (scheduler, channel):
7269 - Tor now uses new schedulers to decide which circuits should
7270 deliver cells first, in order to improve congestion at relays. The
7271 first type is called "KIST" ("Kernel Informed Socket Transport"),
7272 and is only available on Linux-like systems: it uses feedback from
7273 the kernel to prevent the kernel's TCP buffers from growing too
7274 full. The second new scheduler type is called "KISTLite": it
7275 behaves the same as KIST, but runs on systems without kernel
7276 support for inspecting TCP implementation details. The old
7277 scheduler is still available, under the name "Vanilla". To change
7278 the default scheduler preference order, use the new "Schedulers"
7279 option. (The default preference order is "KIST,KISTLite,Vanilla".)
7281 Matt Traudt implemented KIST, based on research by Rob Jansen,
7282 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
7283 more information, see the design paper at
7284 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
7285 followup implementation paper at https://arxiv.org/abs/1709.01044.
7286 Closes ticket 12541.
7288 o Major features (next-generation onion services):
7289 - Tor now supports the next-generation onion services protocol for
7290 clients and services! As part of this release, the core of
7291 proposal 224 has been implemented and is available for
7292 experimentation and testing by our users. This newer version of
7293 onion services ("v3") features many improvements over the legacy
7296 a) Better crypto (replaced SHA1/DH/RSA1024
7297 with SHA3/ed25519/curve25519)
7299 b) Improved directory protocol, leaking much less information to
7302 c) Improved directory protocol, with smaller surface for
7305 d) Better onion address security against impersonation.
7307 e) More extensible introduction/rendezvous protocol.
7309 f) A cleaner and more modular codebase.
7311 You can identify a next-generation onion address by its length:
7312 they are 56 characters long, as in
7313 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
7315 In the future, we will release more options and features for v3
7316 onion services, but we first need a testing period, so that the
7317 current codebase matures and becomes more robust. Planned features
7318 include: offline keys, advanced client authorization, improved
7319 guard algorithms, and statistics. For full details, see
7322 Legacy ("v2") onion services will still work for the foreseeable
7323 future, and will remain the default until this new codebase gets
7324 tested and hardened. Service operators who want to experiment with
7325 the new system can use the 'HiddenServiceVersion 3' torrc
7326 directive along with the regular onion service configuration
7327 options. We will publish a blog post about this new feature
7330 o Major bugfixes (usability, control port):
7331 - Report trusted clock skew indications as bootstrap errors, so
7332 controllers can more easily alert users when their clocks are
7333 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
7335 o Minor features (bug detection):
7336 - Log a warning message with a stack trace for any attempt to call
7337 get_options() during option validation. This pattern has caused
7338 subtle bugs in the past. Closes ticket 22281.
7340 o Minor features (client):
7341 - You can now use Tor as a tunneled HTTP proxy: use the new
7342 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
7343 requests. Closes ticket 22407.
7344 - Add an extra check to make sure that we always use the newer guard
7345 selection code for picking our guards. Closes ticket 22779.
7346 - When downloading (micro)descriptors, don't split the list into
7347 multiple requests unless we want at least 32 descriptors.
7348 Previously, we split at 4, not 32, which led to significant
7349 overhead in HTTP request size and degradation in compression
7350 performance. Closes ticket 23220.
7352 o Minor features (command line):
7353 - Add a new commandline option, --key-expiration, which prints when
7354 the current signing key is going to expire. Implements ticket
7355 17639; patch by Isis Lovecruft.
7357 o Minor features (control port):
7358 - If an application tries to use the control port as an HTTP proxy,
7359 respond with a meaningful "This is the Tor control port" message,
7360 and log the event. Closes ticket 1667. Patch from Ravi
7362 - Provide better error message for GETINFO desc/(id|name) when not
7363 fetching router descriptors. Closes ticket 5847. Patch by
7365 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
7366 whether Tor will try to download router descriptors and
7367 microdescriptors respectively. Closes ticket 22684.
7368 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
7369 so controllers can tell whether the geoip databases are loaded.
7370 Closes ticket 23237.
7371 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
7372 events. Closes ticket 19254. Patch by "DonnchaC".
7374 o Minor features (development support):
7375 - Developers can now generate a call-graph for Tor using the
7376 "calltool" python program, which post-processes object dumps. It
7377 should work okay on many Linux and OSX platforms, and might work
7378 elsewhere too. To run it, install calltool from
7379 https://gitweb.torproject.org/user/nickm/calltool.git and run
7380 "make callgraph". Closes ticket 19307.
7382 o Minor features (ed25519):
7383 - Add validation function to checks for torsion components in
7384 ed25519 public keys, used by prop224 client-side code. Closes
7385 ticket 22006. Math help by Ian Goldberg.
7387 o Minor features (exit relay, DNS):
7388 - Improve the clarity and safety of the log message from evdns when
7389 receiving an apparently spoofed DNS reply. Closes ticket 3056.
7391 o Minor features (integration, hardening):
7392 - Add a new NoExec option to prevent Tor from running other
7393 programs. When this option is set to 1, Tor will never try to run
7394 another program, regardless of the settings of
7395 PortForwardingHelper, ClientTransportPlugin, or
7396 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
7397 without restarting Tor. Closes ticket 22976.
7399 o Minor features (logging):
7400 - Improve the warning message for specifying a relay by nickname.
7401 The previous message implied that nickname registration was still
7402 part of the Tor network design, which it isn't. Closes
7404 - If the sandbox filter fails to load, suggest to the user that
7405 their kernel might not support seccomp2. Closes ticket 23090.
7407 o Minor features (portability):
7408 - Check at configure time whether uint8_t is the same type as
7409 unsigned char. Lots of existing code already makes this
7410 assumption, and there could be strict aliasing issues if the
7411 assumption is violated. Closes ticket 22410.
7413 o Minor features (relay, configuration):
7414 - Reject attempts to use relative file paths when RunAsDaemon is
7415 set. Previously, Tor would accept these, but the directory-
7416 changing step of RunAsDaemon would give strange and/or confusing
7417 results. Closes ticket 22731.
7419 o Minor features (startup, safety):
7420 - When configured to write a PID file, Tor now exits if it is unable
7421 to do so. Previously, it would warn and continue. Closes
7424 o Minor features (static analysis):
7425 - The BUG() macro has been changed slightly so that Coverity no
7426 longer complains about dead code if the bug is impossible. Closes
7429 o Minor features (testing):
7430 - The default chutney network tests now include tests for the v3
7431 hidden service design. Make sure you have the latest version of
7432 chutney if you want to run these. Closes ticket 22437.
7433 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7434 service descriptor. Closes ticket 15554.
7436 o Minor bugfixes (certificate handling):
7437 - Fix a time handling bug in Tor certificates set to expire after
7438 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7439 Coverity as CID 1415728.
7441 o Minor bugfixes (client, usability):
7442 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7443 SOCKS4a requests that contain IP address strings, even when
7444 SafeSocks in enabled, as this prevents user from connecting to
7445 known IP addresses without relying on DNS for resolving. SafeSocks
7446 still rejects SOCKS connections that connect to IP addresses when
7447 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7448 bugfix on Tor 0.2.6.2-alpha.
7450 o Minor bugfixes (code correctness):
7451 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7452 Previously we used ntohs(), which happens to behave the same on
7453 all the platforms we support, but which isn't really correct.
7454 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7455 - For defense-in-depth, make the controller's write_escaped_data()
7456 function robust to extremely long inputs. Fixes bug 19281; bugfix
7457 on 0.1.1.1-alpha. Reported by Guido Vranken.
7459 o Minor bugfixes (compilation):
7460 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7461 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7463 o Minor bugfixes (consensus expiry):
7464 - Check for adequate directory information correctly. Previously, Tor
7465 would reconsider whether it had sufficient directory information
7466 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7468 o Minor bugfixes (directory protocol):
7469 - Directory servers now include a "Date:" http header for response
7470 codes other than 200. Clients starting with a skewed clock and a
7471 recent consensus were getting "304 Not modified" responses from
7472 directory authorities, so without the Date header, the client
7473 would never hear about a wrong clock. Fixes bug 23499; bugfix
7475 - Make clients wait for 6 seconds before trying to download a
7476 consensus from an authority. Fixes bug 17750; bugfix
7479 o Minor bugfixes (DoS-resistance):
7480 - If future code asks if there are any running bridges, without
7481 checking if bridges are enabled, log a BUG warning rather than
7482 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7484 o Minor bugfixes (format strictness):
7485 - Restrict several data formats to decimal. Previously, the
7486 BuildTimeHistogram entries in the state file, the "bw=" entries in
7487 the bandwidth authority file, and the process IDs passed to the
7488 __OwningControllerProcess option could all be specified in hex or
7489 octal as well as in decimal. This was not an intentional feature.
7490 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7493 o Minor bugfixes (heartbeat):
7494 - If we fail to write a heartbeat message, schedule a retry for the
7495 minimum heartbeat interval number of seconds in the future. Fixes
7496 bug 19476; bugfix on 0.2.3.1-alpha.
7498 o Minor bugfixes (linux seccomp2 sandbox, logging):
7499 - Fix some messages on unexpected errors from the seccomp2 library.
7500 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7502 o Minor bugfixes (logging):
7503 - Remove duplicate log messages regarding opening non-local
7504 SocksPorts upon parsing config and opening listeners at startup.
7505 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7506 - Use a more comprehensible log message when telling the user
7507 they've excluded every running exit node. Fixes bug 7890; bugfix
7509 - When logging the number of descriptors we intend to download per
7510 directory request, do not log a number higher than then the number
7511 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7513 - When warning about a directory owned by the wrong user, log the
7514 actual name of the user owning the directory. Previously, we'd log
7515 the name of the process owner twice. Fixes bug 23487; bugfix
7517 - The tor specification says hop counts are 1-based, so fix two log
7518 messages that mistakenly logged 0-based hop counts. Fixes bug
7519 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7520 Credit to Xiaofan Li for reporting this issue.
7522 o Minor bugfixes (portability):
7523 - Stop using the PATH_MAX variable, which is not defined on GNU
7524 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7526 o Minor bugfixes (relay):
7527 - When uploading our descriptor for the first time after startup,
7528 report the reason for uploading as "Tor just started" rather than
7529 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7530 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7531 relays, to prevent spurious address resolutions and descriptor
7532 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7533 bugfix on in 0.2.8.1-alpha.
7535 o Minor bugfixes (tests):
7536 - Fix a broken unit test for the OutboundAddress option: the parsing
7537 function was never returning an error on failure. Fixes bug 23366;
7538 bugfix on 0.3.0.3-alpha.
7539 - Fix a signed-integer overflow in the unit tests for
7540 dir/download_status_random_backoff, which was untriggered until we
7541 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7543 o Minor bugfixes (usability, control port):
7544 - Stop making an unnecessary routerlist check in NETINFO clock skew
7545 detection; this was preventing clients from reporting NETINFO clock
7546 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7548 o Code simplification and refactoring:
7549 - Extract the code for handling newly-open channels into a separate
7550 function from the general code to handle channel state
7551 transitions. This change simplifies our callgraph, reducing the
7552 size of the largest strongly connected component by roughly a
7553 factor of two. Closes ticket 22608.
7554 - Remove dead code for largely unused statistics on the number of
7555 times we've attempted various public key operations. Fixes bug
7556 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7557 - Remove several now-obsolete functions for asking about old
7558 variants directory authority status. Closes ticket 22311; patch
7560 - Remove some of the code that once supported "Named" and "Unnamed"
7561 routers. Authorities no longer vote for these flags. Closes
7563 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7564 and old hidden services, to indicate that they aren't suitable for
7565 new protocols or formats. Closes ticket 23026.
7566 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7567 22521. Patch from Neel Chauhan.
7568 - Split the enormous circuit_send_next_onion_skin() function into
7569 multiple subfunctions. Closes ticket 22804.
7570 - Split the portions of the buffer.c module that handle particular
7571 protocols into separate modules. Part of ticket 23149.
7572 - Use our test macros more consistently, to produce more useful
7573 error messages when our unit tests fail. Add coccinelle patches to
7574 allow us to re-check for test macro uses. Closes ticket 22497.
7576 o Deprecated features:
7577 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7578 only applies to direct unencrypted HTTP connections to your
7579 directory server, which your Tor probably isn't using. Closes
7583 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7584 kernels. Closes ticket 22677.
7585 - Document all values of PublishServerDescriptor in the manpage.
7586 Closes ticket 15645.
7587 - Improve the documentation for the directory port part of the
7588 DirAuthority line. Closes ticket 20152.
7589 - Restore documentation for the authorities' "approved-routers"
7590 file. Closes ticket 21148.
7593 - The AllowDotExit option has been removed as unsafe. It has been
7594 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7595 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7596 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7597 Closes ticket 21031.
7598 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7599 nobody was using it any longer. Closes ticket 22377.
7602 Changes in version 0.2.8.15 - 2017-09-18
7603 Tor 0.2.8.15 backports a collection of bugfixes from later
7606 Most significantly, it includes a fix for TROVE-2017-008, a
7607 security bug that affects hidden services running with the
7608 SafeLogging option disabled. For more information, see
7609 https://trac.torproject.org/projects/tor/ticket/23490
7611 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7612 2018. We suggest that you upgrade to the latest stable release if
7613 possible. If you can't, we recommend that you upgrade at least to
7614 0.2.9, which will be supported until 2020.
7616 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7617 - Avoid an assertion failure bug affecting our implementation of
7618 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7619 handling of "0xx" differs from what we had expected. Fixes bug
7620 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7623 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7626 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7627 - Backport a fix for an "unused variable" warning that appeared
7628 in some versions of mingw. Fixes bug 22838; bugfix on
7631 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7632 - Fix a memset() off the end of an array when packing cells. This
7633 bug should be harmless in practice, since the corrupted bytes are
7634 still in the same structure, and are always padding bytes,
7635 ignored, or immediately overwritten, depending on compiler
7636 behavior. Nevertheless, because the memset()'s purpose is to make
7637 sure that any other cell-handling bugs can't expose bytes to the
7638 network, we need to fix it. Fixes bug 22737; bugfix on
7639 0.2.4.11-alpha. Fixes CID 1401591.
7641 o Build features (backport from 0.3.1.5-alpha):
7642 - Tor's repository now includes a Travis Continuous Integration (CI)
7643 configuration file (.travis.yml). This is meant to help new
7644 developers and contributors who fork Tor to a Github repository be
7645 better able to test their changes, and understand what we expect
7646 to pass. To use this new build feature, you must fork Tor to your
7647 Github account, then go into the "Integrations" menu in the
7648 repository settings for your fork and enable Travis, then push
7649 your changes. Closes ticket 22636.
7652 Changes in version 0.2.9.12 - 2017-09-18
7653 Tor 0.2.9.12 backports a collection of bugfixes from later
7656 Most significantly, it includes a fix for TROVE-2017-008, a
7657 security bug that affects hidden services running with the
7658 SafeLogging option disabled. For more information, see
7659 https://trac.torproject.org/projects/tor/ticket/23490
7661 o Major features (security, backport from 0.3.0.2-alpha):
7662 - Change the algorithm used to decide DNS TTLs on client and server
7663 side, to better resist DNS-based correlation attacks like the
7664 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7665 Feamster. Now relays only return one of two possible DNS TTL
7666 values, and clients are willing to believe DNS TTL values up to 3
7667 hours long. Closes ticket 19769.
7669 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
7670 - Fix a rare crash when sending a begin cell on a circuit whose
7671 linked directory connection had already been closed. Fixes bug
7672 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7674 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
7675 - Fix a bug that prevented exit nodes from caching DNS records for
7676 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7678 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7679 - Fix a typo that had prevented TPROXY-based transparent proxying
7680 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7681 Patch from "d4fq0fQAgoJ".
7683 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7684 - Avoid an assertion failure bug affecting our implementation of
7685 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7686 handling of "0xx" differs from what we had expected. Fixes bug
7687 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7689 o Minor features (code style, backport from 0.3.1.3-alpha):
7690 - Add "Falls through" comments to our codebase, in order to silence
7691 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7692 Stieger. Closes ticket 22446.
7694 o Minor features (geoip):
7695 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7698 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
7699 - Roll over monthly accounting at the configured hour and minute,
7700 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7701 Found by Andrey Karpov with PVS-Studio.
7703 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
7704 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7705 bugfix on 0.2.8.1-alpha.
7706 - Fix warnings when building with libscrypt and openssl scrypt support
7707 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
7708 - When building with certain versions the mingw C header files, avoid
7709 float-conversion warnings when calling the C functions isfinite(),
7710 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
7712 o Minor bugfixes (compilation, backport from 0.3.1.7):
7713 - Avoid compiler warnings in the unit tests for running tor_sscanf()
7714 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7716 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7717 - Backport a fix for an "unused variable" warning that appeared
7718 in some versions of mingw. Fixes bug 22838; bugfix on
7721 o Minor bugfixes (controller, backport from 0.3.1.7):
7722 - Do not crash when receiving a HSPOST command with an empty body.
7723 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7724 - Do not crash when receiving a POSTDESCRIPTOR command with an
7725 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7727 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
7728 - Avoid Coverity build warnings related to our BUG() macro. By
7729 default, Coverity treats BUG() as the Linux kernel does: an
7730 instant abort(). We need to override that so our BUG() macro
7731 doesn't prevent Coverity from analyzing functions that use it.
7732 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
7734 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7735 - Fix a memset() off the end of an array when packing cells. This
7736 bug should be harmless in practice, since the corrupted bytes are
7737 still in the same structure, and are always padding bytes,
7738 ignored, or immediately overwritten, depending on compiler
7739 behavior. Nevertheless, because the memset()'s purpose is to make
7740 sure that any other cell-handling bugs can't expose bytes to the
7741 network, we need to fix it. Fixes bug 22737; bugfix on
7742 0.2.4.11-alpha. Fixes CID 1401591.
7744 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7745 - When setting the maximum number of connections allowed by the OS,
7746 always allow some extra file descriptors for other files. Fixes
7747 bug 22797; bugfix on 0.2.0.10-alpha.
7749 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
7750 - Avoid a sandbox failure when trying to re-bind to a socket and
7751 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
7753 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
7754 - Permit the fchmod system call, to avoid crashing on startup when
7755 starting with the seccomp2 sandbox and an unexpected set of
7756 permissions on the data directory or its contents. Fixes bug
7757 22516; bugfix on 0.2.5.4-alpha.
7759 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
7760 - Avoid a double-marked-circuit warning that could happen when we
7761 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
7764 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
7765 - Reject version numbers with non-numeric prefixes (such as +, -, or
7766 whitespace). Disallowing whitespace prevents differential version
7767 parsing between POSIX-based and Windows platforms. Fixes bug 21507
7768 and part of 21508; bugfix on 0.0.8pre1.
7770 o Build features (backport from 0.3.1.5-alpha):
7771 - Tor's repository now includes a Travis Continuous Integration (CI)
7772 configuration file (.travis.yml). This is meant to help new
7773 developers and contributors who fork Tor to a Github repository be
7774 better able to test their changes, and understand what we expect
7775 to pass. To use this new build feature, you must fork Tor to your
7776 Github account, then go into the "Integrations" menu in the
7777 repository settings for your fork and enable Travis, then push
7778 your changes. Closes ticket 22636.
7781 Changes in version 0.3.0.11 - 2017-09-18
7782 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
7785 Most significantly, it includes a fix for TROVE-2017-008, a
7786 security bug that affects hidden services running with the
7787 SafeLogging option disabled. For more information, see
7788 https://trac.torproject.org/projects/tor/ticket/23490
7790 o Minor features (code style, backport from 0.3.1.7):
7791 - Add "Falls through" comments to our codebase, in order to silence
7792 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7793 Stieger. Closes ticket 22446.
7796 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7799 o Minor bugfixes (compilation, backport from 0.3.1.7):
7800 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7801 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7803 o Minor bugfixes (controller, backport from 0.3.1.7):
7804 - Do not crash when receiving a HSPOST command with an empty body.
7805 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7806 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7807 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7809 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
7810 - When setting the maximum number of connections allowed by the OS,
7811 always allow some extra file descriptors for other files. Fixes
7812 bug 22797; bugfix on 0.2.0.10-alpha.
7814 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
7815 - Remove a forgotten debugging message when an introduction point
7816 successfully establishes a hidden service prop224 circuit with
7818 - Change three other log_warn() for an introduction point to
7819 protocol warnings, because they can be failure from the network
7820 and are not relevant to the operator. Fixes bug 23078; bugfix on
7821 0.3.0.1-alpha and 0.3.0.2-alpha.
7824 Changes in version 0.3.1.7 - 2017-09-18
7825 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
7827 With the 0.3.1 series, Tor now serves and downloads directory
7828 information in more compact formats, to save on bandwidth overhead. It
7829 also contains a new padding system to resist netflow-based traffic
7830 analysis, and experimental support for building parts of Tor in Rust
7831 (though no parts of Tor are in Rust yet). There are also numerous
7832 small features, bugfixes on earlier release series, and groundwork for
7833 the hidden services revamp of 0.3.2.
7835 This release also includes a fix for TROVE-2017-008, a security bug
7836 that affects hidden services running with the SafeLogging option
7837 disabled. For more information, see
7838 https://trac.torproject.org/projects/tor/ticket/23490
7840 Per our stable release policy, we plan to support each stable release
7841 series for at least the next nine months, or for three months after
7842 the first stable release of the next series: whichever is longer. If
7843 you need a release with long-term support, we recommend that you stay
7844 with the 0.2.9 series.
7846 Below is a list of the changes since 0.3.1.6-rc. For a list of all
7847 changes since 0.3.0, see the ReleaseNotes file.
7849 o Major bugfixes (security, hidden services, loggging):
7850 - Fix a bug where we could log uninitialized stack when a certain
7851 hidden service error occurred while SafeLogging was disabled.
7852 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
7853 TROVE-2017-008 and CVE-2017-0380.
7855 o Minor features (defensive programming):
7856 - Create a pair of consensus parameters, nf_pad_tor2web and
7857 nf_pad_single_onion, to disable netflow padding in the consensus
7858 for non-anonymous connections in case the overhead is high. Closes
7861 o Minor features (diagnostic):
7862 - Add a stack trace to the bug warnings that can be logged when
7863 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
7864 attempt for bug 23105.
7866 o Minor features (geoip):
7867 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7870 o Minor bugfixes (compilation):
7871 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
7872 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
7874 o Minor bugfixes (controller):
7875 - Do not crash when receiving a HSPOST command with an empty body.
7876 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
7877 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
7878 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
7880 o Minor bugfixes (relay):
7881 - Inform the geoip and rephist modules about all requests, even on
7882 relays that are only fetching microdescriptors. Fixes a bug
7883 related to 21585; bugfix on 0.3.0.1-alpha.
7885 o Minor bugfixes (unit tests):
7886 - Fix a channelpadding unit test failure on slow systems by using
7887 mocked time instead of actual time. Fixes bug 23077; bugfix
7891 Changes in version 0.3.1.6-rc - 2017-09-05
7892 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
7893 release series, including a bug that produced weird behavior on
7894 Windows directory caches.
7896 This is the first release candidate in the Tor 0.3.1 series. If we
7897 find no new bugs or regressions here, the first stable 0.3.1 release
7898 will be nearly identical to it.
7900 o Major bugfixes (windows, directory cache):
7901 - On Windows, do not try to delete cached consensus documents and
7902 diffs before they are unmapped from memory--Windows won't allow
7903 that. Instead, allow the consensus cache directory to grow larger,
7904 to hold files that might need to stay around longer. Fixes bug
7905 22752; bugfix on 0.3.1.1-alpha.
7907 o Minor features (directory authority):
7908 - Improve the message that authorities report to relays that present
7909 RSA/Ed25519 keypairs that conflict with previously pinned keys.
7910 Closes ticket 22348.
7912 o Minor features (geoip):
7913 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
7916 o Minor features (testing):
7917 - Add more tests for compression backend initialization. Closes
7920 o Minor bugfixes (directory cache):
7921 - Fix a memory leak when recovering space in the consensus cache.
7922 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
7924 o Minor bugfixes (hidden service):
7925 - Increase the number of circuits that a service is allowed to
7926 open over a specific period of time. The value was lower than it
7927 should be (8 vs 12) in the normal case of 3 introduction points.
7928 Fixes bug 22159; bugfix on 0.3.0.5-rc.
7929 - Fix a BUG warning during HSv3 descriptor decoding that could be
7930 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
7931 on 0.3.0.1-alpha. Bug found by "haxxpop".
7932 - Rate-limit the log messages if we exceed the maximum number of
7933 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
7935 o Minor bugfixes (logging, relay):
7936 - Remove a forgotten debugging message when an introduction point
7937 successfully establishes a hidden service prop224 circuit with
7939 - Change three other log_warn() for an introduction point to
7940 protocol warnings, because they can be failure from the network
7941 and are not relevant to the operator. Fixes bug 23078; bugfix on
7942 0.3.0.1-alpha and 0.3.0.2-alpha.
7944 o Minor bugfixes (relay):
7945 - When a relay is not running as a directory cache, it will no
7946 longer generate compressed consensuses and consensus diff
7947 information. Previously, this was a waste of disk and CPU. Fixes
7948 bug 23275; bugfix on 0.3.1.1-alpha.
7950 o Minor bugfixes (robustness, error handling):
7951 - Improve our handling of the cases where OpenSSL encounters a
7952 memory error while encoding keys and certificates. We haven't
7953 observed these errors in the wild, but if they do happen, we now
7954 detect and respond better. Fixes bug 19418; bugfix on all versions
7955 of Tor. Reported by Guido Vranken.
7957 o Minor bugfixes (stability):
7958 - Avoid crashing on a double-free when unable to load or process an
7959 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
7960 with the clang static analyzer.
7962 o Minor bugfixes (testing):
7963 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
7964 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
7965 - Port the hs_ntor handshake test to work correctly with recent
7966 versions of the pysha3 module. Fixes bug 23071; bugfix
7969 o Minor bugfixes (Windows service):
7970 - When running as a Windows service, set the ID of the main thread
7971 correctly. Failure to do so made us fail to send log messages to
7972 the controller in 0.2.1.16-rc, slowed down controller event
7973 delivery in 0.2.7.3-rc and later, and crash with an assertion
7974 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7975 Patch and diagnosis from "Vort".
7978 Changes in version 0.3.0.10 - 2017-08-02
7979 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
7980 from the current Tor alpha series. OpenBSD users and TPROXY users
7981 should upgrade; others are probably okay sticking with 0.3.0.9.
7983 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
7984 - Tor's repository now includes a Travis Continuous Integration (CI)
7985 configuration file (.travis.yml). This is meant to help new
7986 developers and contributors who fork Tor to a Github repository be
7987 better able to test their changes, and understand what we expect
7988 to pass. To use this new build feature, you must fork Tor to your
7989 Github account, then go into the "Integrations" menu in the
7990 repository settings for your fork and enable Travis, then push
7991 your changes. Closes ticket 22636.
7993 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7994 - Fix a typo that had prevented TPROXY-based transparent proxying
7995 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7996 Patch from "d4fq0fQAgoJ".
7998 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7999 - Avoid an assertion failure bug affecting our implementation of
8000 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8001 handling of "0xbar" differs from what we had expected. Fixes bug
8002 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8004 o Minor features (backport from 0.3.1.5-alpha):
8005 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8008 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
8009 - Roll over monthly accounting at the configured hour and minute,
8010 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8011 Found by Andrey Karpov with PVS-Studio.
8013 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
8014 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8015 bugfix on 0.2.8.1-alpha.
8016 - Fix warnings when building with libscrypt and openssl scrypt
8017 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8018 - When building with certain versions of the mingw C header files,
8019 avoid float-conversion warnings when calling the C functions
8020 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8023 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8024 - Backport a fix for an "unused variable" warning that appeared
8025 in some versions of mingw. Fixes bug 22838; bugfix on
8028 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8029 - Avoid Coverity build warnings related to our BUG() macro. By
8030 default, Coverity treats BUG() as the Linux kernel does: an
8031 instant abort(). We need to override that so our BUG() macro
8032 doesn't prevent Coverity from analyzing functions that use it.
8033 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8035 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
8036 - When rejecting a router descriptor for running an obsolete version
8037 of Tor without ntor support, warn about the obsolete tor version,
8038 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8040 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8041 - Avoid a sandbox failure when trying to re-bind to a socket and
8042 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8044 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
8045 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8046 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8049 Changes in version 0.3.1.5-alpha - 2017-08-01
8050 Tor 0.3.1.5-alpha improves the performance of consensus diff
8051 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
8052 several other bugs. If no serious bugs are found in this version, the
8053 next version will be a release candidate.
8055 This release also marks the end of support for the Tor 0.2.4.x,
8056 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
8057 further bug or security fixes. Anyone still running or distributing
8058 one of those versions should upgrade.
8060 o Major features (build system, continuous integration):
8061 - Tor's repository now includes a Travis Continuous Integration (CI)
8062 configuration file (.travis.yml). This is meant to help new
8063 developers and contributors who fork Tor to a Github repository be
8064 better able to test their changes, and understand what we expect
8065 to pass. To use this new build feature, you must fork Tor to your
8066 Github account, then go into the "Integrations" menu in the
8067 repository settings for your fork and enable Travis, then push
8068 your changes. Closes ticket 22636.
8070 o Major bugfixes (openbsd, denial-of-service):
8071 - Avoid an assertion failure bug affecting our implementation of
8072 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8073 handling of "0xbar" differs from what we had expected. Fixes bug
8074 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8076 o Major bugfixes (relay, performance):
8077 - Perform circuit handshake operations at a higher priority than we
8078 use for consensus diff creation and compression. This should
8079 prevent circuits from starving when a relay or bridge receives a
8080 new consensus, especially on lower-powered machines. Fixes bug
8081 22883; bugfix on 0.3.1.1-alpha.
8083 o Minor features (bridge authority):
8084 - Add "fingerprint" lines to the networkstatus-bridges file produced
8085 by bridge authorities. Closes ticket 22207.
8087 o Minor features (directory cache, consensus diff):
8088 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
8089 operators with low-resource environments to adjust the number of
8090 consensuses they'll store and generate diffs from. Most cache
8091 operators should leave it unchanged. Helps to work around
8094 o Minor features (geoip):
8095 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8098 o Minor features (relay, performance):
8099 - Always start relays with at least two worker threads, to prevent
8100 priority inversion on slow tasks. Part of the fix for bug 22883.
8101 - Allow background work to be queued with different priorities, so
8102 that a big pile of slow low-priority jobs will not starve out
8103 higher priority jobs. This lays the groundwork for a fix for
8106 o Minor bugfixes (build system, rust):
8107 - Fix a problem where Rust toolchains were not being found when
8108 building without --enable-cargo-online-mode, due to setting the
8109 $HOME environment variable instead of $CARGO_HOME. Fixes bug
8110 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
8112 o Minor bugfixes (compatibility, zstd):
8113 - Write zstd epilogues correctly when the epilogue requires
8114 reallocation of the output buffer, even with zstd 1.3.0.
8115 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
8116 22927; bugfix on 0.3.1.1-alpha.
8118 o Minor bugfixes (compilation warnings):
8119 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
8120 22915; bugfix on 0.2.8.1-alpha.
8121 - Fix warnings when building with libscrypt and openssl scrypt
8122 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8123 - Compile correctly when both openssl 1.1.0 and libscrypt are
8124 detected. Previously this would cause an error. Fixes bug 22892;
8125 bugfix on 0.3.1.1-alpha.
8126 - When building with certain versions of the mingw C header files,
8127 avoid float-conversion warnings when calling the C functions
8128 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8131 o Minor bugfixes (coverity build support):
8132 - Avoid Coverity build warnings related to our BUG() macro. By
8133 default, Coverity treats BUG() as the Linux kernel does: an
8134 instant abort(). We need to override that so our BUG() macro
8135 doesn't prevent Coverity from analyzing functions that use it.
8136 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8138 o Minor bugfixes (directory authority):
8139 - When a directory authority rejects a descriptor or extrainfo with
8140 a given digest, mark that digest as undownloadable, so that we do
8141 not attempt to download it again over and over. We previously
8142 tried to avoid downloading such descriptors by other means, but we
8143 didn't notice if we accidentally downloaded one anyway. This
8144 behavior became problematic in 0.2.7.2-alpha, when authorities
8145 began pinning Ed25519 keys. Fixes bug 22349; bugfix
8148 o Minor bugfixes (error reporting, windows):
8149 - When formatting Windows error messages, use the English format to
8150 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
8153 o Minor bugfixes (file limits, osx):
8154 - When setting the maximum number of connections allowed by the OS,
8155 always allow some extra file descriptors for other files. Fixes
8156 bug 22797; bugfix on 0.2.0.10-alpha.
8158 o Minor bugfixes (linux seccomp2 sandbox):
8159 - Avoid a sandbox failure when trying to re-bind to a socket and
8160 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8162 o Minor bugfixes (memory leaks):
8163 - Fix a small memory leak when validating a configuration that uses
8164 two or more AF_UNIX sockets for the same port type. Fixes bug
8165 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
8167 o Minor bugfixes (unit tests):
8168 - test_consdiff_base64cmp would fail on OS X because while OS X
8169 follows the standard of (less than zero/zero/greater than zero),
8170 it doesn't follow the convention of (-1/0/+1). Make the test
8171 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
8172 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8173 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8176 Changes in version 0.3.1.4-alpha - 2017-06-29
8177 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
8178 to use a guard that was in the same network family as a chosen exit
8179 relay. This is a security regression; all clients running earlier
8180 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8183 This release also fixes several other bugs introduced in 0.3.0.x
8184 and 0.3.1.x, including others that can affect bandwidth usage
8188 - To build with zstd and lzma support, Tor now requires the
8189 pkg-config tool at build time. (This requirement was new in
8190 0.3.1.1-alpha, but was not noted at the time. Noting it here to
8191 close ticket 22623.)
8193 o Major bugfixes (path selection, security):
8194 - When choosing which guard to use for a circuit, avoid the exit's
8195 family along with the exit itself. Previously, the new guard
8196 selection logic avoided the exit, but did not consider its family.
8197 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8198 006 and CVE-2017-0377.
8200 o Major bugfixes (compression, zstd):
8201 - Correctly detect a full buffer when decompressing a large zstd-
8202 compressed input. Previously, we would sometimes treat a full
8203 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
8205 o Major bugfixes (directory protocol):
8206 - Ensure that we send "304 Not modified" as HTTP status code when a
8207 client is attempting to fetch a consensus or consensus diff, and
8208 the best one we can send them is one they already have. Fixes bug
8209 22702; bugfix on 0.3.1.1-alpha.
8211 o Major bugfixes (entry guards):
8212 - When starting with an old consensus, do not add new entry guards
8213 unless the consensus is "reasonably live" (under 1 day old). Fixes
8214 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8216 o Minor features (bug mitigation, diagnostics, logging):
8217 - Avoid an assertion failure, and log a better error message, when
8218 unable to remove a file from the consensus cache on Windows.
8219 Attempts to mitigate and diagnose bug 22752.
8221 o Minor features (geoip):
8222 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8225 o Minor bugfixes (compression):
8226 - When compressing or decompressing a buffer, check for a failure to
8227 create a compression object. Fixes bug 22626; bugfix
8229 - When decompressing a buffer, check for extra data after the end of
8230 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
8231 - When decompressing an object received over an anonymous directory
8232 connection, if we have already decompressed it using an acceptable
8233 compression method, do not reject it for looking like an
8234 unacceptable compression method. Fixes part of bug 22670; bugfix
8236 - When serving directory votes compressed with zlib, do not claim to
8237 have compressed them with zstd. Fixes bug 22669; bugfix
8239 - When spooling compressed data to an output buffer, don't try to
8240 spool more data when there is no more data to spool and we are not
8241 trying to flush the input. Previously, we would sometimes launch
8242 compression requests with nothing to do, which interferes with our
8243 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
8245 o Minor bugfixes (defensive programming):
8246 - Detect and break out of infinite loops in our compression code. We
8247 don't think that any such loops exist now, but it's best to be
8248 safe. Closes ticket 22672.
8249 - Fix a memset() off the end of an array when packing cells. This
8250 bug should be harmless in practice, since the corrupted bytes are
8251 still in the same structure, and are always padding bytes,
8252 ignored, or immediately overwritten, depending on compiler
8253 behavior. Nevertheless, because the memset()'s purpose is to make
8254 sure that any other cell-handling bugs can't expose bytes to the
8255 network, we need to fix it. Fixes bug 22737; bugfix on
8256 0.2.4.11-alpha. Fixes CID 1401591.
8258 o Minor bugfixes (linux seccomp2 sandbox):
8259 - Permit the fchmod system call, to avoid crashing on startup when
8260 starting with the seccomp2 sandbox and an unexpected set of
8261 permissions on the data directory or its contents. Fixes bug
8262 22516; bugfix on 0.2.5.4-alpha.
8263 - Fix a crash in the LZMA module, when the sandbox was enabled, and
8264 liblzma would allocate more than 16 MB of memory. We solve this by
8265 bumping the mprotect() limit in the sandbox module from 16 MB to
8266 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
8268 o Minor bugfixes (logging):
8269 - When decompressing, do not warn if we fail to decompress using a
8270 compression method that we merely guessed. Fixes part of bug
8271 22670; bugfix on 0.1.1.14-alpha.
8272 - When decompressing, treat mismatch between content-encoding and
8273 actual compression type as a protocol warning. Fixes part of bug
8274 22670; bugfix on 0.1.1.9-alpha.
8275 - Downgrade "assigned_to_cpuworker failed" message to info-level
8276 severity. In every case that can reach it, either a better warning
8277 has already been logged, or no warning is warranted. Fixes bug
8278 22356; bugfix on 0.2.6.3-alpha.
8279 - Demote a warn that was caused by libevent delays to info if
8280 netflow padding is less than 4.5 seconds late, or to notice
8281 if it is more (4.5 seconds is the amount of time that a netflow
8282 record might be emitted after, if we chose the maximum timeout).
8283 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8285 o Minor bugfixes (process behavior):
8286 - When exiting because of an error, always exit with a nonzero exit
8287 status. Previously, we would fail to report an error in our exit
8288 status in cases related to __OwningControllerProcess failure,
8289 lockfile contention, and Ed25519 key initialization. Fixes bug
8290 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
8291 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
8295 - Add a manpage description for the key-pinning-journal file. Closes
8297 - Correctly note that bandwidth accounting values are stored in the
8298 state file, and the bw_accounting file is now obsolete. Closes
8300 - Document more of the files in the Tor data directory, including
8301 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
8302 approved-routers, sr-random, and diff-cache. Found while fixing
8306 Changes in version 0.3.0.9 - 2017-06-29
8307 Tor 0.3.0.9 fixes a path selection bug that would allow a client
8308 to use a guard that was in the same network family as a chosen exit
8309 relay. This is a security regression; all clients running earlier
8310 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
8313 This release also backports several other bugfixes from the 0.3.1.x
8316 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
8317 - When choosing which guard to use for a circuit, avoid the exit's
8318 family along with the exit itself. Previously, the new guard
8319 selection logic avoided the exit, but did not consider its family.
8320 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8321 006 and CVE-2017-0377.
8323 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
8324 - Don't block bootstrapping when a primary bridge is offline and we
8325 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8326 21969; bugfix on 0.3.0.3-alpha.
8328 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
8329 - When starting with an old consensus, do not add new entry guards
8330 unless the consensus is "reasonably live" (under 1 day old). Fixes
8331 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8333 o Minor features (geoip):
8334 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8337 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8338 - Reject version numbers with non-numeric prefixes (such as +, -, or
8339 whitespace). Disallowing whitespace prevents differential version
8340 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8341 and part of 21508; bugfix on 0.0.8pre1.
8343 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8344 - Permit the fchmod system call, to avoid crashing on startup when
8345 starting with the seccomp2 sandbox and an unexpected set of
8346 permissions on the data directory or its contents. Fixes bug
8347 22516; bugfix on 0.2.5.4-alpha.
8349 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
8350 - Fix a memset() off the end of an array when packing cells. This
8351 bug should be harmless in practice, since the corrupted bytes are
8352 still in the same structure, and are always padding bytes,
8353 ignored, or immediately overwritten, depending on compiler
8354 behavior. Nevertheless, because the memset()'s purpose is to make
8355 sure that any other cell-handling bugs can't expose bytes to the
8356 network, we need to fix it. Fixes bug 22737; bugfix on
8357 0.2.4.11-alpha. Fixes CID 1401591.
8360 Changes in version 0.3.1.3-alpha - 2017-06-08
8361 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
8362 remotely crash a hidden service with an assertion failure. Anyone
8363 running a hidden service should upgrade to this version, or to some
8364 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8366 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
8367 that sometimes made relays unreliable, as well as several other
8368 bugfixes described below.
8370 o Major bugfixes (hidden service, relay, security):
8371 - Fix a remotely triggerable assertion failure when a hidden service
8372 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8373 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8374 - Fix a remotely triggerable assertion failure caused by receiving a
8375 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8376 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8379 o Major bugfixes (relay, link handshake):
8380 - When performing the v3 link handshake on a TLS connection, report
8381 that we have the x509 certificate that we actually used on that
8382 connection, even if we have changed certificates since that
8383 connection was first opened. Previously, we would claim to have
8384 used our most recent x509 link certificate, which would sometimes
8385 make the link handshake fail. Fixes one case of bug 22460; bugfix
8388 o Major bugfixes (relays, key management):
8389 - Regenerate link and authentication certificates whenever the key
8390 that signs them changes; also, regenerate link certificates
8391 whenever the signed key changes. Previously, these processes were
8392 only weakly coupled, and we relays could (for minutes to hours)
8393 wind up with an inconsistent set of keys and certificates, which
8394 other relays would not accept. Fixes two cases of bug 22460;
8395 bugfix on 0.3.0.1-alpha.
8396 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8397 send the certificate that matches the x509 certificate that we
8398 used on the TLS connection. Previously, there was a race condition
8399 if the TLS context rotated after we began the TLS handshake but
8400 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8403 o Major bugfixes (torrc, crash):
8404 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
8405 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
8407 o Minor features (code style):
8408 - Add "Falls through" comments to our codebase, in order to silence
8409 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8410 Stieger. Closes ticket 22446.
8412 o Minor features (diagnostic):
8413 - Add logging messages to try to diagnose a rare bug that seems to
8414 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
8415 think this is happening because of incorrect system clocks, but
8416 we'd like to know for certain. Diagnostic for bug 22466.
8418 o Minor bugfixes (correctness):
8419 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8420 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8422 o Minor bugfixes (directory protocol):
8423 - Check for libzstd >= 1.1, because older versions lack the
8424 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8426 o Minor bugfixes (link handshake):
8427 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8428 months, and regenerate it when it is within one month of expiring.
8429 Previously, we had generated this certificate at startup with a
8430 ten-year lifetime, but that could lead to weird behavior when Tor
8431 was started with a grossly inaccurate clock. Mitigates bug 22466;
8432 mitigation on 0.3.0.1-alpha.
8434 o Minor bugfixes (storage directories):
8435 - Always check for underflows in the cached storage directory usage.
8436 If the usage does underflow, re-calculate it. Also, avoid a
8437 separate underflow when the usage is not known. Fixes bug 22424;
8438 bugfix on 0.3.1.1-alpha.
8440 o Minor bugfixes (unit tests):
8441 - The unit tests now pass on systems where localhost is misconfigured
8442 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8446 - Clarify the manpage for the (deprecated) torify script. Closes
8449 Changes in version 0.3.0.8 - 2017-06-08
8450 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8451 remotely crash a hidden service with an assertion failure. Anyone
8452 running a hidden service should upgrade to this version, or to some
8453 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8455 Tor 0.3.0.8 also includes fixes for several key management bugs
8456 that sometimes made relays unreliable, as well as several other
8457 bugfixes described below.
8459 o Major bugfixes (hidden service, relay, security, backport
8460 from 0.3.1.3-alpha):
8461 - Fix a remotely triggerable assertion failure when a hidden service
8462 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8463 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8464 - Fix a remotely triggerable assertion failure caused by receiving a
8465 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8466 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8469 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8470 - When performing the v3 link handshake on a TLS connection, report
8471 that we have the x509 certificate that we actually used on that
8472 connection, even if we have changed certificates since that
8473 connection was first opened. Previously, we would claim to have
8474 used our most recent x509 link certificate, which would sometimes
8475 make the link handshake fail. Fixes one case of bug 22460; bugfix
8478 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8479 - Regenerate link and authentication certificates whenever the key
8480 that signs them changes; also, regenerate link certificates
8481 whenever the signed key changes. Previously, these processes were
8482 only weakly coupled, and we relays could (for minutes to hours)
8483 wind up with an inconsistent set of keys and certificates, which
8484 other relays would not accept. Fixes two cases of bug 22460;
8485 bugfix on 0.3.0.1-alpha.
8486 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8487 send the certificate that matches the x509 certificate that we
8488 used on the TLS connection. Previously, there was a race condition
8489 if the TLS context rotated after we began the TLS handshake but
8490 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8493 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8494 - Stop rejecting v3 hidden service descriptors because their size
8495 did not match an old padding rule. Fixes bug 22447; bugfix on
8498 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8499 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8500 December 2016 (of which ~126 were still functional) with a list of
8501 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8502 2017. Resolves ticket 21564.
8504 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8505 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8506 bug 22252; bugfix on 0.2.9.3-alpha.
8508 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8509 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8510 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8512 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8513 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8514 months, and regenerate it when it is within one month of expiring.
8515 Previously, we had generated this certificate at startup with a
8516 ten-year lifetime, but that could lead to weird behavior when Tor
8517 was started with a grossly inaccurate clock. Mitigates bug 22466;
8518 mitigation on 0.3.0.1-alpha.
8520 o Minor bugfixes (memory leak, directory authority, backport from
8522 - When directory authorities reject a router descriptor due to
8523 keypinning, free the router descriptor rather than leaking the
8524 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8527 Changes in version 0.2.9.11 - 2017-06-08
8528 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8529 remotely crash a hidden service with an assertion failure. Anyone
8530 running a hidden service should upgrade to this version, or to some
8531 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8532 are not affected by TROVE-2017-004.)
8534 Tor 0.2.9.11 also backports fixes for several key management bugs
8535 that sometimes made relays unreliable, as well as several other
8536 bugfixes described below.
8538 o Major bugfixes (hidden service, relay, security, backport
8539 from 0.3.1.3-alpha):
8540 - Fix a remotely triggerable assertion failure caused by receiving a
8541 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8542 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8545 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8546 - When performing the v3 link handshake on a TLS connection, report
8547 that we have the x509 certificate that we actually used on that
8548 connection, even if we have changed certificates since that
8549 connection was first opened. Previously, we would claim to have
8550 used our most recent x509 link certificate, which would sometimes
8551 make the link handshake fail. Fixes one case of bug 22460; bugfix
8554 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8555 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8556 December 2016 (of which ~126 were still functional) with a list of
8557 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8558 2017. Resolves ticket 21564.
8560 o Minor features (future-proofing, backport from 0.3.0.7):
8561 - Tor no longer refuses to download microdescriptors or descriptors if
8562 they are listed as "published in the future". This change will
8563 eventually allow us to stop listing meaningful "published" dates
8564 in microdescriptor consensuses, and thereby allow us to reduce the
8565 resources required to download consensus diffs by over 50%.
8566 Implements part of ticket 21642; implements part of proposal 275.
8568 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8569 - Directory authorities now reject relays running versions
8570 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8571 suffer from bug 20499 and don't keep their consensus cache
8572 up-to-date. Resolves ticket 20509.
8574 o Minor features (geoip):
8575 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8578 o Minor bugfixes (control port, backport from 0.3.0.6):
8579 - The GETINFO extra-info/digest/<digest> command was broken because
8580 of a wrong base16 decode return value check, introduced when
8581 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8583 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8584 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8585 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8587 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8588 - The getpid() system call is now permitted under the Linux seccomp2
8589 sandbox, to avoid crashing with versions of OpenSSL (and other
8590 libraries) that attempt to learn the process's PID by using the
8591 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8594 o Minor bugfixes (memory leak, directory authority, backport
8595 from 0.3.1.2-alpha):
8596 - When directory authorities reject a router descriptor due to
8597 keypinning, free the router descriptor rather than leaking the
8598 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8600 Changes in version 0.2.8.14 - 2017-06-08
8601 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8602 remotely crash a hidden service with an assertion failure. Anyone
8603 running a hidden service should upgrade to this version, or to some
8604 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8605 are not affected by TROVE-2017-004.)
8607 o Major bugfixes (hidden service, relay, security):
8608 - Fix a remotely triggerable assertion failure caused by receiving a
8609 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8610 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8613 o Minor features (geoip):
8614 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
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 (correctness):
8624 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8625 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8627 Changes in version 0.2.7.8 - 2017-06-08
8628 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8629 remotely crash a hidden service with an assertion failure. Anyone
8630 running a hidden service should upgrade to this version, or to some
8631 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8632 are not affected by TROVE-2017-004.)
8634 o Major bugfixes (hidden service, relay, security):
8635 - Fix a remotely triggerable assertion failure caused by receiving a
8636 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8637 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8640 o Minor features (geoip):
8641 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8644 o Minor bugfixes (correctness):
8645 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8646 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8649 Changes in version 0.2.6.12 - 2017-06-08
8650 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
8651 remotely crash a hidden service with an assertion failure. Anyone
8652 running a hidden service should upgrade to this version, or to some
8653 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8654 are not affected by TROVE-2017-004.)
8656 o Major bugfixes (hidden service, relay, security):
8657 - Fix a remotely triggerable assertion failure caused by receiving a
8658 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8659 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8662 o Minor features (geoip):
8663 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8666 o Minor bugfixes (correctness):
8667 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8668 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8670 Changes in version 0.2.5.14 - 2017-06-08
8671 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
8672 remotely crash a hidden service with an assertion failure. Anyone
8673 running a hidden service should upgrade to this version, or to some
8674 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8675 are not affected by TROVE-2017-004.)
8677 o Major bugfixes (hidden service, relay, security):
8678 - Fix a remotely triggerable assertion failure caused by receiving a
8679 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8680 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8683 o Minor features (geoip):
8684 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8687 o Minor bugfixes (correctness):
8688 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8689 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8691 Changes in version 0.2.4.29 - 2017-06-08
8692 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
8693 remotely crash a hidden service with an assertion failure. Anyone
8694 running a hidden service should upgrade to this version, or to some
8695 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8696 are not affected by TROVE-2017-004.)
8698 o Major bugfixes (hidden service, relay, security):
8699 - Fix a remotely triggerable assertion failure caused by receiving a
8700 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8701 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8704 o Minor features (geoip):
8705 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8708 o Minor bugfixes (correctness):
8709 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8710 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8713 Changes in version 0.3.1.2-alpha - 2017-05-26
8714 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
8715 fixes a few bugs found while testing 0.3.1.1-alpha, including a
8716 memory corruption bug that affected relay stability.
8718 o Major bugfixes (crash, relay):
8719 - Fix a memory-corruption bug in relays that set MyFamily.
8720 Previously, they would double-free MyFamily elements when making
8721 the next descriptor or when changing their configuration. Fixes
8722 bug 22368; bugfix on 0.3.1.1-alpha.
8724 o Minor bugfixes (logging):
8725 - Log a better message when a directory authority replies to an
8726 upload with an unexpected status code. Fixes bug 11121; bugfix
8729 o Minor bugfixes (memory leak, directory authority):
8730 - When directory authorities reject a router descriptor due to
8731 keypinning, free the router descriptor rather than leaking the
8732 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8735 Changes in version 0.3.1.1-alpha - 2017-05-22
8736 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
8737 reduces the bandwidth usage for Tor's directory protocol, adds some
8738 basic padding to resist netflow-based traffic analysis and to serve as
8739 the basis of other padding in the future, and adds rust support to the
8742 It also contains numerous other small features and improvements to
8743 security, correctness, and performance.
8745 Below are the changes since 0.3.0.7.
8747 o Major features (directory protocol):
8748 - Tor relays and authorities can now serve clients an abbreviated
8749 version of the consensus document, containing only the changes
8750 since an older consensus document that the client holds. Clients
8751 now request these documents when available. When both client and
8752 server use this new protocol, they will use far less bandwidth (up
8753 to 94% less) to keep the client's consensus up-to-date. Implements
8754 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
8755 - Tor can now compress directory traffic with lzma or with zstd
8756 compression algorithms, which can deliver better bandwidth
8757 performance. Because lzma is computationally expensive, it's only
8758 used for documents that can be compressed once and served many
8759 times. Support for these algorithms requires that tor is built
8760 with the libzstd and/or liblzma libraries available. Implements
8761 proposal 278; closes ticket 21662.
8762 - Relays now perform the more expensive compression operations, and
8763 consensus diff generation, in worker threads. This separation
8764 avoids delaying the main thread when a new consensus arrives.
8766 o Major features (experimental):
8767 - Tor can now build modules written in Rust. To turn this on, pass
8768 the "--enable-rust" flag to the configure script. It's not time to
8769 get excited yet: currently, there is no actual Rust functionality
8770 beyond some simple glue code, and a notice at startup to tell you
8771 that Rust is running. Still, we hope that programmers and
8772 packagers will try building Tor with Rust support, so that we can
8773 find issues and solve portability problems. Closes ticket 22106.
8775 o Major features (traffic analysis resistance):
8776 - Connections between clients and relays now send a padding cell in
8777 each direction every 1.5 to 9.5 seconds (tunable via consensus
8778 parameters). This padding will not resist specialized
8779 eavesdroppers, but it should be enough to make many ISPs' routine
8780 network flow logging less useful in traffic analysis against
8783 Padding is negotiated using Tor's link protocol, so both relays
8784 and clients must upgrade for this to take effect. Clients may
8785 still send padding despite the relay's version by setting
8786 ConnectionPadding 1 in torrc, and may disable padding by setting
8787 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
8788 users with the torrc option ReducedConnectionPadding. Implements
8789 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
8790 - Relays will publish 24 hour totals of padding and non-padding cell
8791 counts to their extra-info descriptors, unless PaddingStatistics 0
8792 is set in torrc. These 24 hour totals are also rounded to
8795 o Major bugfixes (connection usage):
8796 - We use NETINFO cells to try to determine if both relays involved
8797 in a connection will agree on the canonical status of that
8798 connection. We prefer the connections where this is the case for
8799 extend cells, and try to close connections where relays disagree
8800 on their canonical status early. Also, we now prefer the oldest
8801 valid connection for extend cells. These two changes should reduce
8802 the number of long-term connections that are kept open between
8803 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
8804 - Relays now log hourly statistics (look for
8805 "channel_check_for_duplicates" lines) on the total number of
8806 connections to other relays. If the number of connections per
8807 relay is unexpectedly large, this log message is at notice level.
8808 Otherwise it is at info.
8810 o Major bugfixes (entry guards):
8811 - Don't block bootstrapping when a primary bridge is offline and we
8812 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8813 21969; bugfix on 0.3.0.3-alpha.
8815 o Major bugfixes (linux TPROXY support):
8816 - Fix a typo that had prevented TPROXY-based transparent proxying
8817 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8818 Patch from "d4fq0fQAgoJ".
8820 o Minor features (security, windows):
8821 - Enable a couple of pieces of Windows hardening: one
8822 (HeapEnableTerminationOnCorruption) that has been on-by-default
8823 since Windows 8, and unavailable before Windows 7; and one
8824 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
8825 affect us, but shouldn't do any harm. Closes ticket 21953.
8827 o Minor features (config options):
8828 - Allow "%include" directives in torrc configuration files. These
8829 directives import the settings from other files, or from all the
8830 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
8831 - Make SAVECONF return an error when overwriting a torrc that has
8832 includes. Using SAVECONF with the FORCE option will allow it to
8833 overwrite torrc even if includes are used. Related to ticket 1922.
8834 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
8835 will work without the FORCE option. Related to ticket 1922.
8837 o Minor features (controller):
8838 - Warn the first time that a controller requests data in the long-
8839 deprecated 'GETINFO network-status' format. Closes ticket 21703.
8841 o Minor features (defaults):
8842 - The default value for UseCreateFast is now 0: clients which
8843 haven't yet received a consensus document will now use a proper
8844 ntor handshake to talk to their directory servers whenever they
8845 can. Closes ticket 21407.
8846 - Onion key rotation and expiry intervals are now defined as a
8847 network consensus parameter, per proposal 274. The default
8848 lifetime of an onion key is increased from 7 to 28 days. Old onion
8849 keys will expire after 7 days by default. This change will make
8850 consensus diffs much smaller, and save significant bandwidth.
8851 Closes ticket 21641.
8853 o Minor features (fallback directory list):
8854 - Update the fallback directory mirror whitelist and blacklist based
8855 on operator emails. Closes task 21121.
8856 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8857 December 2016 (of which ~126 were still functional) with a list of
8858 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8859 2017. Resolves ticket 21564.
8861 o Minor features (hidden services, logging):
8862 - Log a message when a hidden service descriptor has fewer
8863 introduction points than specified in
8864 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
8865 - Log a message when a hidden service reaches its introduction point
8866 circuit limit, and when that limit is reset. Follow up to ticket
8867 21594; closes ticket 21622.
8868 - Warn user if multiple entries in EntryNodes and at least one
8869 HiddenService are used together. Pinning EntryNodes along with a
8870 hidden service can be possibly harmful; for instance see ticket
8871 14917 or 21155. Closes ticket 21155.
8873 o Minor features (linux seccomp2 sandbox):
8874 - We now have a document storage backend compatible with the Linux
8875 seccomp2 sandbox. This backend is used for consensus documents and
8876 diffs between them; in the long term, we'd like to use it for
8877 unparseable directory material too. Closes ticket 21645
8878 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
8879 from 1MB to 16MB. This was necessary with the glibc allocator in
8880 order to allow worker threads to allocate more memory -- which in
8881 turn is necessary because of our new use of worker threads for
8882 compression. Closes ticket 22096.
8884 o Minor features (logging):
8885 - Log files are no longer created world-readable by default.
8886 (Previously, most distributors would store the logs in a non-
8887 world-readable location to prevent inappropriate access. This
8888 change is an extra precaution.) Closes ticket 21729; patch
8891 o Minor features (performance):
8892 - Our Keccak (SHA-3) implementation now accesses memory more
8893 efficiently, especially on little-endian systems. Closes
8895 - Add an O(1) implementation of channel_find_by_global_id(), to
8896 speed some controller functions.
8898 o Minor features (relay, configuration):
8899 - The MyFamily option may now be repeated as many times as desired,
8900 for relays that want to configure large families. Closes ticket
8901 4998; patch by Daniel Pinto.
8903 o Minor features (safety):
8904 - Add an explicit check to extrainfo_parse_entry_from_string() for
8905 NULL inputs. We don't believe this can actually happen, but it may
8906 help silence a warning from the Clang analyzer. Closes
8909 o Minor features (testing):
8910 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
8911 When Tor is compiled with this option, we disable a number of
8912 redundant memory-safety failsafes that are intended to stop bugs
8913 from becoming security issues. This makes it easier to hunt for
8914 bugs that would be security issues without the failsafes turned
8915 on. Closes ticket 21439.
8916 - Add a general event-tracing instrumentation support to Tor. This
8917 subsystem will enable developers and researchers to add fine-
8918 grained instrumentation to their Tor instances, for use when
8919 examining Tor network performance issues. There are no trace
8920 events yet, and event-tracing is off by default unless enabled at
8921 compile time. Implements ticket 13802.
8922 - Improve our version parsing tests: add tests for typical version
8923 components, add tests for invalid versions, including numeric
8924 range and non-numeric prefixes. Unit tests 21278, 21450, and
8925 21507. Partially implements 21470.
8927 o Minor bugfixes (bandwidth accounting):
8928 - Roll over monthly accounting at the configured hour and minute,
8929 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8930 Found by Andrey Karpov with PVS-Studio.
8932 o Minor bugfixes (code correctness):
8933 - Accurately identify client connections by their lack of peer
8934 authentication. This means that we bail out earlier if asked to
8935 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
8938 o Minor bugfixes (configuration):
8939 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8940 bug 22252; bugfix on 0.2.9.3-alpha.
8942 o Minor bugfixes (connection lifespan):
8943 - Allow more control over how long TLS connections are kept open:
8944 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
8945 single option called CircuitsAvailableTimeout. Also, allow the
8946 consensus to control the default values for both this preference
8947 and the lifespan of relay-to-relay connections. Fixes bug 17592;
8948 bugfix on 0.2.5.5-alpha.
8949 - Increase the initial circuit build timeout testing frequency, to
8950 help ensure that ReducedConnectionPadding clients finish learning
8951 a timeout before their orconn would expire. The initial testing
8952 rate was set back in the days of TAP and before the Tor Browser
8953 updater, when we had to be much more careful about new clients
8954 making lots of circuits. With this change, a circuit build timeout
8955 is learned in about 15-20 minutes, instead of 100-120 minutes.
8957 o Minor bugfixes (controller):
8958 - GETINFO onions/current and onions/detached no longer respond with
8959 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
8960 - Trigger HS descriptor events on the control port when the client
8961 fails to pick a hidden service directory for a hidden service.
8962 This can happen if all the hidden service directories are in
8963 ExcludeNodes, or they have all been queried within the last 15
8964 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
8966 o Minor bugfixes (directory authority):
8967 - When rejecting a router descriptor for running an obsolete version
8968 of Tor without ntor support, warn about the obsolete tor version,
8969 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8970 - Prevent the shared randomness subsystem from asserting when
8971 initialized by a bridge authority with an incomplete configuration
8972 file. Fixes bug 21586; bugfix on 0.2.9.8.
8974 o Minor bugfixes (exit-side DNS):
8975 - Fix an untriggerable assertion that checked the output of a
8976 libevent DNS error, so that the assertion actually behaves as
8977 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
8978 Karpov using PVS-Studio.
8980 o Minor bugfixes (fallback directories):
8981 - Make the usage example in updateFallbackDirs.py actually work, and
8982 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
8983 - Decrease the guard flag average required to be a fallback. This
8984 allows us to keep relays that have their guard flag removed when
8985 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8986 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
8987 bugfix on 0.2.8.1-alpha.
8988 - Make sure fallback directory mirrors have the same address, port,
8989 and relay identity key for at least 30 days before they are
8990 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
8992 o Minor bugfixes (hidden services):
8993 - Stop printing a cryptic warning when a hidden service gets a
8994 request to connect to a virtual port that it hasn't configured.
8995 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
8996 - Simplify hidden service descriptor creation by using an existing
8997 flag to check if an introduction point is established. Fixes bug
8998 21599; bugfix on 0.2.7.2-alpha.
9000 o Minor bugfixes (memory leak):
9001 - Fix a small memory leak at exit from the backtrace handler code.
9002 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
9004 o Minor bugfixes (protocol, logging):
9005 - Downgrade a log statement about unexpected relay cells from "bug"
9006 to "protocol warning", because there is at least one use case
9007 where it can be triggered by a buggy tor implementation. Fixes bug
9008 21293; bugfix on 0.1.1.14-alpha.
9010 o Minor bugfixes (testing):
9011 - Use unbuffered I/O for utility functions around the
9012 process_handle_t type. This fixes unit test failures reported on
9013 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
9014 - Make display of captured unit test log messages consistent. Fixes
9015 bug 21510; bugfix on 0.2.9.3-alpha.
9016 - Make test-network.sh always call chutney's test-network.sh.
9017 Previously, this only worked on systems which had bash installed,
9018 due to some bash-specific code in the script. Fixes bug 19699;
9019 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
9021 o Minor bugfixes (voting consistency):
9022 - Reject version numbers with non-numeric prefixes (such as +, -, or
9023 whitespace). Disallowing whitespace prevents differential version
9024 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9025 and part of 21508; bugfix on 0.0.8pre1.
9027 o Minor bugfixes (windows, relay):
9028 - Resolve "Failure from drain_fd: No error" warnings on Windows
9029 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
9031 o Code simplification and refactoring:
9032 - Break up the 630-line function connection_dir_client_reached_eof()
9033 into a dozen smaller functions. This change should help
9034 maintainability and readability of the client directory code.
9035 - Isolate our use of the openssl headers so that they are only
9036 included from our crypto wrapper modules, and from tests that
9037 examine those modules' internals. Closes ticket 21841.
9038 - Simplify our API to launch directory requests, making it more
9039 extensible and less error-prone. Now it's easier to add extra
9040 headers to directory requests. Closes ticket 21646.
9041 - Our base64 decoding functions no longer overestimate the output
9042 space that they need when parsing unpadded inputs. Closes
9044 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
9045 Resolves ticket 22213.
9046 - The logic that directory caches use to spool request to clients,
9047 serving them one part at a time so as not to allocate too much
9048 memory, has been refactored for consistency. Previously there was
9049 a separate spooling implementation per type of spoolable data. Now
9050 there is one common spooling implementation, with extensible data
9051 types. Closes ticket 21651.
9052 - Tor's compression module now supports multiple backends. Part of
9053 the implementation for proposal 278; closes ticket 21663.
9056 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
9057 Closes ticket 21873.
9058 - Correct documentation about the default DataDirectory value.
9059 Closes ticket 21151.
9060 - Document the default behavior of NumEntryGuards and
9061 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
9063 - Document key=value pluggable transport arguments for Bridge lines
9064 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
9065 - Note that bandwidth-limiting options don't affect TCP headers or
9066 DNS. Closes ticket 17170.
9068 o Removed features (configuration options, all in ticket 22060):
9069 - These configuration options are now marked Obsolete, and no longer
9070 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
9071 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
9072 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
9073 in 0.2.9.2-alpha and have now been removed. The previous default
9074 behavior is now always chosen; the previous (less secure) non-
9075 default behavior is now unavailable.
9076 - CloseHSClientCircuitsImmediatelyOnTimeout and
9077 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
9078 0.2.9.2-alpha and now have been removed. HS circuits never close
9079 on circuit build timeout; they have a longer timeout period.
9080 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
9081 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
9082 (and others) to configure listen-only and advertise-only addresses.
9084 o Removed features (tools):
9085 - We've removed the tor-checkkey tool from src/tools. Long ago, we
9086 used it to help people detect RSA keys that were generated by
9087 versions of Debian affected by CVE-2008-0166. But those keys have
9088 been out of circulation for ages, and this tool is no longer
9089 required. Closes ticket 21842.
9092 Changes in version 0.3.0.7 - 2017-05-15
9093 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
9094 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
9095 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
9096 clients are not affected.
9098 o Major bugfixes (hidden service directory, security):
9099 - Fix an assertion failure in the hidden service directory code, which
9100 could be used by an attacker to remotely cause a Tor relay process to
9101 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
9102 should upgrade. This security issue is tracked as TROVE-2017-002.
9103 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
9106 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9109 o Minor features (future-proofing):
9110 - Tor no longer refuses to download microdescriptors or descriptors
9111 if they are listed as "published in the future". This change will
9112 eventually allow us to stop listing meaningful "published" dates
9113 in microdescriptor consensuses, and thereby allow us to reduce the
9114 resources required to download consensus diffs by over 50%.
9115 Implements part of ticket 21642; implements part of proposal 275.
9117 o Minor bugfixes (Linux seccomp2 sandbox):
9118 - The getpid() system call is now permitted under the Linux seccomp2
9119 sandbox, to avoid crashing with versions of OpenSSL (and other
9120 libraries) that attempt to learn the process's PID by using the
9121 syscall rather than the VDSO code. Fixes bug 21943; bugfix
9125 Changes in version 0.3.0.6 - 2017-04-26
9126 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
9128 With the 0.3.0 series, clients and relays now use Ed25519 keys to
9129 authenticate their link connections to relays, rather than the old
9130 RSA1024 keys that they used before. (Circuit crypto has been
9131 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
9132 the guard selection and replacement algorithm to behave more robustly
9133 in the presence of unreliable networks, and to resist guard-
9136 This series also includes numerous other small features and bugfixes,
9137 along with more groundwork for the upcoming hidden-services revamp.
9139 Per our stable release policy, we plan to support the Tor 0.3.0
9140 release series for at least the next nine months, or for three months
9141 after the first stable release of the 0.3.1 series: whichever is
9142 longer. If you need a release with long-term support, we recommend
9143 that you stay with the 0.2.9 series.
9145 Below are the changes since 0.3.0.5-rc. For a list of all changes
9146 since 0.2.9, see the ReleaseNotes file.
9148 o Minor features (geoip):
9149 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
9152 o Minor bugfixes (control port):
9153 - The GETINFO extra-info/digest/<digest> command was broken because
9154 of a wrong base16 decode return value check, introduced when
9155 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
9157 o Minor bugfixes (crash prevention):
9158 - Fix a (currently untriggerable, but potentially dangerous) crash
9159 bug when base32-encoding inputs whose sizes are not a multiple of
9160 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
9163 Changes in version 0.3.0.5-rc - 2017-04-05
9164 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
9165 0.3.0 release series.
9167 This is the second release candidate in the Tor 0.3.0 series, and has
9168 much fewer changes than the first. If we find no new bugs or
9169 regressions here, the first stable 0.3.0 release will be nearly
9172 o Major bugfixes (crash, directory connections):
9173 - Fix a rare crash when sending a begin cell on a circuit whose
9174 linked directory connection had already been closed. Fixes bug
9175 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9177 o Major bugfixes (guard selection):
9178 - Fix a guard selection bug where Tor would refuse to bootstrap in
9179 some cases if the user swapped a bridge for another bridge in
9180 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
9181 Reported by "torvlnt33r".
9183 o Minor features (geoip):
9184 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
9187 o Minor bugfix (compilation):
9188 - Fix a warning when compiling hs_service.c. Previously, it had no
9189 exported symbols when compiled for libor.a, resulting in a
9190 compilation warning from clang. Fixes bug 21825; bugfix
9193 o Minor bugfixes (hidden services):
9194 - Make hidden services check for failed intro point connections,
9195 even when they have exceeded their intro point creation limit.
9196 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
9197 - Make hidden services with 8 to 10 introduction points check for
9198 failed circuits immediately after startup. Previously, they would
9199 wait for 5 minutes before performing their first checks. Fixes bug
9200 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
9202 o Minor bugfixes (memory leaks):
9203 - Fix a memory leak when using GETCONF on a port option. Fixes bug
9204 21682; bugfix on 0.3.0.3-alpha.
9206 o Minor bugfixes (relay):
9207 - Avoid a double-marked-circuit warning that could happen when we
9208 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9211 o Minor bugfixes (tests):
9212 - Run the entry_guard_parse_from_state_full() test with the time set
9213 to a specific date. (The guard state that this test was parsing
9214 contained guards that had expired since the test was first
9215 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
9218 - Update the description of the directory server options in the
9219 manual page, to clarify that a relay no longer needs to set
9220 DirPort in order to be a directory cache. Closes ticket 21720.
9224 Changes in version 0.2.8.13 - 2017-03-03
9225 Tor 0.2.8.13 backports a security fix from later Tor
9226 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9227 this release, if for some reason they cannot upgrade to a later
9228 release series, and if they build Tor with the --enable-expensive-hardening
9231 Note that support for Tor 0.2.8.x is ending next year: we will not issue
9232 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
9233 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9235 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9236 - Fix an integer underflow bug when comparing malformed Tor
9237 versions. This bug could crash Tor when built with
9238 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9239 0.2.9.8, which were built with -ftrapv by default. In other cases
9240 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9241 on 0.0.8pre1. Found by OSS-Fuzz.
9243 o Minor features (geoip):
9244 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9248 Changes in version 0.2.7.7 - 2017-03-03
9249 Tor 0.2.7.7 backports a number of security fixes from later Tor
9250 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
9251 this release, if for some reason they cannot upgrade to a later
9254 Note that support for Tor 0.2.7.x is ending this year: we will not issue
9255 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
9256 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9258 o Directory authority changes (backport from 0.2.8.5-rc):
9259 - Urras is no longer a directory authority. Closes ticket 19271.
9261 o Directory authority changes (backport from 0.2.9.2-alpha):
9262 - The "Tonga" bridge authority has been retired; the new bridge
9263 authority is "Bifroest". Closes tickets 19728 and 19690.
9265 o Directory authority key updates (backport from 0.2.8.1-alpha):
9266 - Update the V3 identity key for the dannenberg directory authority:
9267 it was changed on 18 November 2015. Closes task 17906. Patch
9270 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9271 - Fix a bug in parsing that could cause clients to read a single
9272 byte past the end of an allocated region. This bug could be used
9273 to cause hardened clients (built with --enable-expensive-hardening)
9274 to crash if they tried to visit a hostile hidden service. Non-
9275 hardened clients are only affected depending on the details of
9276 their platform's memory allocator. Fixes bug 21018; bugfix on
9277 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9278 2016-12-002 and as CVE-2016-1254.
9280 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9281 - Stop a crash that could occur when a client running with DNSPort
9282 received a query with multiple address types, and the first
9283 address type was not supported. Found and fixed by Scott Dial.
9284 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9285 - Prevent a class of security bugs caused by treating the contents
9286 of a buffer chunk as if they were a NUL-terminated string. At
9287 least one such bug seems to be present in all currently used
9288 versions of Tor, and would allow an attacker to remotely crash
9289 most Tor instances, especially those compiled with extra compiler
9290 hardening. With this defense in place, such bugs can't crash Tor,
9291 though we should still fix them as they occur. Closes ticket
9292 20384 (TROVE-2016-10-001).
9294 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9295 - Avoid a difficult-to-trigger heap corruption attack when extending
9296 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9297 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9298 Reported by Guido Vranken.
9300 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9301 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9302 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9304 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9305 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9306 pointer to the previous (uninitialized) key value. The impact here
9307 should be limited to a difficult-to-trigger crash, if OpenSSL is
9308 running an engine that makes key generation failures possible, or
9309 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9310 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9313 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9314 - Fix an integer underflow bug when comparing malformed Tor
9315 versions. This bug could crash Tor when built with
9316 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9317 0.2.9.8, which were built with -ftrapv by default. In other cases
9318 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9319 on 0.0.8pre1. Found by OSS-Fuzz.
9321 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9322 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9323 zero size. Check size argument to memwipe() for underflow. Fixes
9324 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9327 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9328 - Make Tor survive errors involving connections without a
9329 corresponding event object. Previously we'd fail with an
9330 assertion; now we produce a log message. Related to bug 16248.
9332 o Minor features (geoip):
9333 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9337 Changes in version 0.2.6.11 - 2017-03-03
9338 Tor 0.2.6.11 backports a number of security fixes from later Tor
9339 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
9340 this release, if for some reason they cannot upgrade to a later
9343 Note that support for Tor 0.2.6.x is ending this year: we will not issue
9344 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
9345 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9347 o Directory authority changes (backport from 0.2.8.5-rc):
9348 - Urras is no longer a directory authority. Closes ticket 19271.
9350 o Directory authority changes (backport from 0.2.9.2-alpha):
9351 - The "Tonga" bridge authority has been retired; the new bridge
9352 authority is "Bifroest". Closes tickets 19728 and 19690.
9354 o Directory authority key updates (backport from 0.2.8.1-alpha):
9355 - Update the V3 identity key for the dannenberg directory authority:
9356 it was changed on 18 November 2015. Closes task 17906. Patch
9359 o Major features (security fixes, backport from 0.2.9.4-alpha):
9360 - Prevent a class of security bugs caused by treating the contents
9361 of a buffer chunk as if they were a NUL-terminated string. At
9362 least one such bug seems to be present in all currently used
9363 versions of Tor, and would allow an attacker to remotely crash
9364 most Tor instances, especially those compiled with extra compiler
9365 hardening. With this defense in place, such bugs can't crash Tor,
9366 though we should still fix them as they occur. Closes ticket
9367 20384 (TROVE-2016-10-001).
9369 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9370 - Fix a bug in parsing that could cause clients to read a single
9371 byte past the end of an allocated region. This bug could be used
9372 to cause hardened clients (built with --enable-expensive-hardening)
9373 to crash if they tried to visit a hostile hidden service. Non-
9374 hardened clients are only affected depending on the details of
9375 their platform's memory allocator. Fixes bug 21018; bugfix on
9376 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9377 2016-12-002 and as CVE-2016-1254.
9379 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9380 - Stop a crash that could occur when a client running with DNSPort
9381 received a query with multiple address types, and the first
9382 address type was not supported. Found and fixed by Scott Dial.
9383 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9385 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9386 - Fix an error that could cause us to read 4 bytes before the
9387 beginning of an openssl string. This bug could be used to cause
9388 Tor to crash on systems with unusual malloc implementations, or
9389 systems with unusual hardening installed. Fixes bug 17404; bugfix
9392 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9393 - Avoid a difficult-to-trigger heap corruption attack when extending
9394 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9395 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9396 Reported by Guido Vranken.
9398 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9399 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9400 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9402 o Major bugfixes (guard selection, backport from 0.2.7.6):
9403 - Actually look at the Guard flag when selecting a new directory
9404 guard. When we implemented the directory guard design, we
9405 accidentally started treating all relays as if they have the Guard
9406 flag during guard selection, leading to weaker anonymity and worse
9407 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9410 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9411 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9412 pointer to the previous (uninitialized) key value. The impact here
9413 should be limited to a difficult-to-trigger crash, if OpenSSL is
9414 running an engine that makes key generation failures possible, or
9415 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9416 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9419 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9420 - Fix an integer underflow bug when comparing malformed Tor
9421 versions. This bug could crash Tor when built with
9422 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9423 0.2.9.8, which were built with -ftrapv by default. In other cases
9424 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9425 on 0.0.8pre1. Found by OSS-Fuzz.
9427 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9428 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9429 zero size. Check size argument to memwipe() for underflow. Fixes
9430 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9433 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9434 - Make Tor survive errors involving connections without a
9435 corresponding event object. Previously we'd fail with an
9436 assertion; now we produce a log message. Related to bug 16248.
9438 o Minor features (geoip):
9439 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9442 o Minor bugfixes (compilation, backport from 0.2.7.6):
9443 - Fix a compilation warning with Clang 3.6: Do not check the
9444 presence of an address which can never be NULL. Fixes bug 17781.
9447 Changes in version 0.2.5.13 - 2017-03-03
9448 Tor 0.2.5.13 backports a number of security fixes from later Tor
9449 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9450 this release, if for some reason they cannot upgrade to a later
9453 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9454 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9455 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9457 o Directory authority changes (backport from 0.2.8.5-rc):
9458 - Urras is no longer a directory authority. Closes ticket 19271.
9460 o Directory authority changes (backport from 0.2.9.2-alpha):
9461 - The "Tonga" bridge authority has been retired; the new bridge
9462 authority is "Bifroest". Closes tickets 19728 and 19690.
9464 o Directory authority key updates (backport from 0.2.8.1-alpha):
9465 - Update the V3 identity key for the dannenberg directory authority:
9466 it was changed on 18 November 2015. Closes task 17906. Patch
9469 o Major features (security fixes, backport from 0.2.9.4-alpha):
9470 - Prevent a class of security bugs caused by treating the contents
9471 of a buffer chunk as if they were a NUL-terminated string. At
9472 least one such bug seems to be present in all currently used
9473 versions of Tor, and would allow an attacker to remotely crash
9474 most Tor instances, especially those compiled with extra compiler
9475 hardening. With this defense in place, such bugs can't crash Tor,
9476 though we should still fix them as they occur. Closes ticket
9477 20384 (TROVE-2016-10-001).
9479 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9480 - Fix a bug in parsing that could cause clients to read a single
9481 byte past the end of an allocated region. This bug could be used
9482 to cause hardened clients (built with --enable-expensive-hardening)
9483 to crash if they tried to visit a hostile hidden service. Non-
9484 hardened clients are only affected depending on the details of
9485 their platform's memory allocator. Fixes bug 21018; bugfix on
9486 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9487 2016-12-002 and as CVE-2016-1254.
9489 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9490 - Stop a crash that could occur when a client running with DNSPort
9491 received a query with multiple address types, and the first
9492 address type was not supported. Found and fixed by Scott Dial.
9493 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9495 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9496 - Fix an error that could cause us to read 4 bytes before the
9497 beginning of an openssl string. This bug could be used to cause
9498 Tor to crash on systems with unusual malloc implementations, or
9499 systems with unusual hardening installed. Fixes bug 17404; bugfix
9502 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9503 - Avoid a difficult-to-trigger heap corruption attack when extending
9504 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9505 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9506 Reported by Guido Vranken.
9508 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9509 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9510 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9512 o Major bugfixes (guard selection, backport from 0.2.7.6):
9513 - Actually look at the Guard flag when selecting a new directory
9514 guard. When we implemented the directory guard design, we
9515 accidentally started treating all relays as if they have the Guard
9516 flag during guard selection, leading to weaker anonymity and worse
9517 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9520 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9521 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9522 pointer to the previous (uninitialized) key value. The impact here
9523 should be limited to a difficult-to-trigger crash, if OpenSSL is
9524 running an engine that makes key generation failures possible, or
9525 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9526 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9529 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9530 - Fix an integer underflow bug when comparing malformed Tor
9531 versions. This bug could crash Tor when built with
9532 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9533 0.2.9.8, which were built with -ftrapv by default. In other cases
9534 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9535 on 0.0.8pre1. Found by OSS-Fuzz.
9537 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9538 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9539 zero size. Check size argument to memwipe() for underflow. Fixes
9540 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9543 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9544 - Make Tor survive errors involving connections without a
9545 corresponding event object. Previously we'd fail with an
9546 assertion; now we produce a log message. Related to bug 16248.
9548 o Minor features (geoip):
9549 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9552 o Minor bugfixes (compilation, backport from 0.2.7.6):
9553 - Fix a compilation warning with Clang 3.6: Do not check the
9554 presence of an address which can never be NULL. Fixes bug 17781.
9556 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9557 - Check for failures from crypto_early_init, and refuse to continue.
9558 A previous typo meant that we could keep going with an
9559 uninitialized crypto library, and would have OpenSSL initialize
9560 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9561 when implementing ticket 4900. Patch by "teor".
9563 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9564 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9565 a client authorized hidden service. Fixes bug 15823; bugfix
9569 Changes in version 0.2.4.28 - 2017-03-03
9570 Tor 0.2.4.28 backports a number of security fixes from later Tor
9571 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9572 this release, if for some reason they cannot upgrade to a later
9575 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9576 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9577 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9579 o Directory authority changes (backport from 0.2.8.5-rc):
9580 - Urras is no longer a directory authority. Closes ticket 19271.
9582 o Directory authority changes (backport from 0.2.9.2-alpha):
9583 - The "Tonga" bridge authority has been retired; the new bridge
9584 authority is "Bifroest". Closes tickets 19728 and 19690.
9586 o Directory authority key updates (backport from 0.2.8.1-alpha):
9587 - Update the V3 identity key for the dannenberg directory authority:
9588 it was changed on 18 November 2015. Closes task 17906. Patch
9591 o Major features (security fixes, backport from 0.2.9.4-alpha):
9592 - Prevent a class of security bugs caused by treating the contents
9593 of a buffer chunk as if they were a NUL-terminated string. At
9594 least one such bug seems to be present in all currently used
9595 versions of Tor, and would allow an attacker to remotely crash
9596 most Tor instances, especially those compiled with extra compiler
9597 hardening. With this defense in place, such bugs can't crash Tor,
9598 though we should still fix them as they occur. Closes ticket
9599 20384 (TROVE-2016-10-001).
9601 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9602 - Fix a bug in parsing that could cause clients to read a single
9603 byte past the end of an allocated region. This bug could be used
9604 to cause hardened clients (built with --enable-expensive-hardening)
9605 to crash if they tried to visit a hostile hidden service. Non-
9606 hardened clients are only affected depending on the details of
9607 their platform's memory allocator. Fixes bug 21018; bugfix on
9608 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9609 2016-12-002 and as CVE-2016-1254.
9611 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9612 - Fix an error that could cause us to read 4 bytes before the
9613 beginning of an openssl string. This bug could be used to cause
9614 Tor to crash on systems with unusual malloc implementations, or
9615 systems with unusual hardening installed. Fixes bug 17404; bugfix
9618 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9619 - Avoid a difficult-to-trigger heap corruption attack when extending
9620 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9621 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9622 Reported by Guido Vranken.
9624 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9625 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9626 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9628 o Major bugfixes (guard selection, backport from 0.2.7.6):
9629 - Actually look at the Guard flag when selecting a new directory
9630 guard. When we implemented the directory guard design, we
9631 accidentally started treating all relays as if they have the Guard
9632 flag during guard selection, leading to weaker anonymity and worse
9633 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9636 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9637 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9638 pointer to the previous (uninitialized) key value. The impact here
9639 should be limited to a difficult-to-trigger crash, if OpenSSL is
9640 running an engine that makes key generation failures possible, or
9641 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9642 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9645 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9646 - Fix an integer underflow bug when comparing malformed Tor
9647 versions. This bug could crash Tor when built with
9648 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9649 0.2.9.8, which were built with -ftrapv by default. In other cases
9650 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9651 on 0.0.8pre1. Found by OSS-Fuzz.
9653 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9654 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9655 zero size. Check size argument to memwipe() for underflow. Fixes
9656 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9659 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9660 - Make Tor survive errors involving connections without a
9661 corresponding event object. Previously we'd fail with an
9662 assertion; now we produce a log message. Related to bug 16248.
9664 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
9665 - Make it harder for attackers to overload hidden services with
9666 introductions, by blocking multiple introduction requests on the
9667 same circuit. Resolves ticket 15515.
9669 o Minor features (geoip):
9670 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9673 o Minor bugfixes (compilation, backport from 0.2.7.6):
9674 - Fix a compilation warning with Clang 3.6: Do not check the
9675 presence of an address which can never be NULL. Fixes bug 17781.
9677 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9678 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9679 a client authorized hidden service. Fixes bug 15823; bugfix
9683 Changes in version 0.3.0.4-rc - 2017-03-01
9684 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
9685 0.3.0 release series, and introduces a few reliability features to
9686 keep them from coming back.
9688 This is the first release candidate in the Tor 0.3.0 series. If we
9689 find no new bugs or regressions here, the first stable 0.3.0 release
9690 will be nearly identical to it.
9692 o Major bugfixes (bridges):
9693 - When the same bridge is configured multiple times with the same
9694 identity, but at different address:port combinations, treat those
9695 bridge instances as separate guards. This fix restores the ability
9696 of clients to configure the same bridge with multiple pluggable
9697 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
9699 o Major bugfixes (hidden service directory v3):
9700 - Stop crashing on a failed v3 hidden service descriptor lookup
9701 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
9703 o Major bugfixes (parsing):
9704 - When parsing a malformed content-length field from an HTTP
9705 message, do not read off the end of the buffer. This bug was a
9706 potential remote denial-of-service attack against Tor clients and
9707 relays. A workaround was released in October 2016, to prevent this
9708 bug from crashing Tor. This is a fix for the underlying issue,
9709 which should no longer matter (if you applied the earlier patch).
9710 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
9711 using AFL (http://lcamtuf.coredump.cx/afl/).
9712 - Fix an integer underflow bug when comparing malformed Tor
9713 versions. This bug could crash Tor when built with
9714 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9715 0.2.9.8, which were built with -ftrapv by default. In other cases
9716 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9717 on 0.0.8pre1. Found by OSS-Fuzz.
9719 o Minor feature (protocol versioning):
9720 - Add new protocol version for proposal 224. HSIntro now advertises
9721 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
9723 o Minor features (directory authorities):
9724 - Directory authorities now reject descriptors that claim to be
9725 malformed versions of Tor. Helps prevent exploitation of
9727 - Reject version numbers with components that exceed INT32_MAX.
9728 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9729 Fixes bug 21450; bugfix on 0.0.8pre1.
9730 - Directory authorities now reject relays running versions
9731 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
9732 suffer from bug 20499 and don't keep their consensus cache
9733 up-to-date. Resolves ticket 20509.
9735 o Minor features (geoip):
9736 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9739 o Minor features (reliability, crash):
9740 - Try better to detect problems in buffers where they might grow (or
9741 think they have grown) over 2 GB in size. Diagnostic for
9744 o Minor features (testing):
9745 - During 'make test-network-all', if tor logs any warnings, ask
9746 chutney to output them. Requires a recent version of chutney with
9747 the 21572 patch. Implements 21570.
9749 o Minor bugfixes (certificate expiration time):
9750 - Avoid using link certificates that don't become valid till some
9751 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
9753 o Minor bugfixes (code correctness):
9754 - Repair a couple of (unreachable or harmless) cases of the risky
9755 comparison-by-subtraction pattern that caused bug 21278.
9756 - Remove a redundant check for the UseEntryGuards option from the
9757 options_transition_affects_guards() function. Fixes bug 21492;
9758 bugfix on 0.3.0.1-alpha.
9760 o Minor bugfixes (directory mirrors):
9761 - Allow relays to use directory mirrors without a DirPort: these
9762 relays need to be contacted over their ORPorts using a begindir
9763 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
9764 - Clarify the message logged when a remote relay is unexpectedly
9765 missing an ORPort or DirPort: users were confusing this with a
9766 local port. Fixes another case of bug 20711; bugfix
9769 o Minor bugfixes (guards):
9770 - Don't warn about a missing guard state on timeout-measurement
9771 circuits: they aren't supposed to be using guards. Fixes an
9772 instance of bug 21007; bugfix on 0.3.0.1-alpha.
9773 - Silence a BUG() warning when attempting to use a guard whose
9774 descriptor we don't know, and make this scenario less likely to
9775 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
9777 o Minor bugfixes (hidden service):
9778 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
9779 cells. Previously, we were using sizeof() on a pointer, instead of
9780 the real destination buffer. Fortunately, that value was only used
9781 to double-check that there was enough room--which was already
9782 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
9784 o Minor bugfixes (testing):
9785 - Fix Raspbian build issues related to missing socket errno in
9786 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
9788 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
9789 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
9790 - Use bash in src/test/test-network.sh. This ensures we reliably
9791 call chutney's newer tools/test-network.sh when available. Fixes
9792 bug 21562; bugfix on 0.2.9.1-alpha.
9795 - Small fixes to the fuzzing documentation. Closes ticket 21472.
9798 Changes in version 0.2.9.10 - 2017-03-01
9799 Tor 0.2.9.10 backports a security fix from later Tor release. It also
9800 includes fixes for some major issues affecting directory authorities,
9801 LibreSSL compatibility, and IPv6 correctness.
9803 The Tor 0.2.9.x release series is now marked as a long-term-support
9804 series. We intend to backport security fixes to 0.2.9.x until at
9805 least January of 2020.
9807 o Major bugfixes (directory authority, 0.3.0.3-alpha):
9808 - During voting, when marking a relay as a probable sybil, do not
9809 clear its BadExit flag: sybils can still be bad in other ways
9810 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9813 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
9814 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9815 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9816 exit policy rejects that port on more than an IPv6 /16 of
9817 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9818 which rejected a relay's own IPv6 address by default. Fixes bug
9819 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9821 o Major bugfixes (parsing, also in 0.3.0.4-rc):
9822 - Fix an integer underflow bug when comparing malformed Tor
9823 versions. This bug could crash Tor when built with
9824 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9825 0.2.9.8, which were built with -ftrapv by default. In other cases
9826 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9827 on 0.0.8pre1. Found by OSS-Fuzz.
9829 o Minor features (directory authorities, also in 0.3.0.4-rc):
9830 - Directory authorities now reject descriptors that claim to be
9831 malformed versions of Tor. Helps prevent exploitation of
9833 - Reject version numbers with components that exceed INT32_MAX.
9834 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
9835 Fixes bug 21450; bugfix on 0.0.8pre1.
9837 o Minor features (geoip):
9838 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9841 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
9842 - Autoconf now checks to determine if OpenSSL structures are opaque,
9843 instead of explicitly checking for OpenSSL version numbers. Part
9845 - Support building with recent LibreSSL code that uses opaque
9846 structures. Closes ticket 21359.
9848 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
9849 - Repair a couple of (unreachable or harmless) cases of the risky
9850 comparison-by-subtraction pattern that caused bug 21278.
9852 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
9853 - The tor-resolve command line tool now rejects hostnames over 255
9854 characters in length. Previously, it would silently truncate them,
9855 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9856 Patch by "junglefowl".
9859 Changes in version 0.3.0.3-alpha - 2017-02-03
9860 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
9861 0.3.0.x development series, including some that could cause
9862 authorities to behave badly. There is also a fix for a longstanding
9863 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
9864 includes some smaller features and bugfixes.
9866 The Tor 0.3.0.x release series is now in patch-freeze: no additional
9867 features will be considered for inclusion in 0.3.0.x. We suspect that
9868 some bugs will probably remain, however, and we encourage people to
9871 o Major bugfixes (directory authority):
9872 - During voting, when marking a relay as a probable sybil, do not
9873 clear its BadExit flag: sybils can still be bad in other ways
9874 too. (We still clear the other flags.) Fixes bug 21108; bugfix
9876 - When deciding whether we have just found a router to be reachable,
9877 do not penalize it for not having performed an Ed25519 link
9878 handshake if it does not claim to support an Ed25519 handshake.
9879 Previously, we would treat such relays as non-running. Fixes bug
9880 21107; bugfix on 0.3.0.1-alpha.
9882 o Major bugfixes (entry guards):
9883 - Stop trying to build circuits through entry guards for which we
9884 have no descriptor. Also, stop crashing in the case that we *do*
9885 accidentally try to build a circuit in such a state. Fixes bug
9886 21242; bugfix on 0.3.0.1-alpha.
9888 o Major bugfixes (IPv6 Exits):
9889 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
9890 any IPv6 addresses. Instead, only reject a port over IPv6 if the
9891 exit policy rejects that port on more than an IPv6 /16 of
9892 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
9893 which rejected a relay's own IPv6 address by default. Fixes bug
9894 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
9896 o Minor feature (client):
9897 - Enable IPv6 traffic on the SocksPort by default. To disable this,
9898 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
9900 o Minor feature (fallback scripts):
9901 - Add a check_existing mode to updateFallbackDirs.py, which checks
9902 if fallbacks in the hard-coded list are working. Closes ticket
9903 20174. Patch by haxxpop.
9905 o Minor features (ciphersuite selection):
9906 - Clients now advertise a list of ciphersuites closer to the ones
9907 preferred by Firefox. Closes part of ticket 15426.
9908 - Allow relays to accept a wider range of ciphersuites, including
9909 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
9911 o Minor features (controller, configuration):
9912 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
9913 and so on, now comes with a __*Port variant that will not be saved
9914 to the torrc file by the controller's SAVECONF command. This
9915 change allows TorBrowser to set up a single-use domain socket for
9916 each time it launches Tor. Closes ticket 20956.
9917 - The GETCONF command can now query options that may only be
9918 meaningful in context-sensitive lists. This allows the controller
9919 to query the mixed SocksPort/__SocksPort style options introduced
9920 in feature 20956. Implements ticket 21300.
9922 o Minor features (portability, compilation):
9923 - Autoconf now checks to determine if OpenSSL structures are opaque,
9924 instead of explicitly checking for OpenSSL version numbers. Part
9926 - Support building with recent LibreSSL code that uses opaque
9927 structures. Closes ticket 21359.
9929 o Minor features (relay):
9930 - We now allow separation of exit and relay traffic to different
9931 source IP addresses, using the OutboundBindAddressExit and
9932 OutboundBindAddressOR options respectively. Closes ticket 17975.
9933 Written by Michael Sonntag.
9935 o Minor bugfix (logging):
9936 - Don't recommend the use of Tor2web in non-anonymous mode.
9937 Recommending Tor2web is a bad idea because the client loses all
9938 anonymity. Tor2web should only be used in specific cases by users
9939 who *know* and understand the issues. Fixes bug 21294; bugfix
9942 o Minor bugfixes (client):
9943 - Always recover from failures in extend_info_from_node(), in an
9944 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
9945 bugfix on 0.2.3.1-alpha.
9947 o Minor bugfixes (client, entry guards):
9948 - Fix a bug warning (with backtrace) when we fail a channel that
9949 circuits to fallback directories on it. Fixes bug 21128; bugfix
9951 - Fix a spurious bug warning (with backtrace) when removing an
9952 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
9953 - Fix a bug of the new guard algorithm where tor could stall for up
9954 to 10 minutes before retrying a guard after a long period of no
9955 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
9956 - Do not try to build circuits until we have descriptors for our
9957 primary entry guards. Related to fix for bug 21242.
9959 o Minor bugfixes (configure, autoconf):
9960 - Rename the configure option --enable-expensive-hardening to
9961 --enable-fragile-hardening. Expensive hardening makes the tor
9962 daemon abort when some kinds of issues are detected. Thus, it
9963 makes tor more at risk of remote crashes but safer against RCE or
9964 heartbleed bug category. We now try to explain this issue in a
9965 message from the configure script. Fixes bug 21290; bugfix
9968 o Minor bugfixes (controller):
9969 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
9970 20824; bugfix on 0.3.0.1-alpha.
9972 o Minor bugfixes (hidden service):
9973 - Clean up the code for expiring intro points with no associated
9974 circuits. It was causing, rarely, a service with some expiring
9975 introduction points to not open enough additional introduction
9976 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
9977 - Stop setting the torrc option HiddenServiceStatistics to "0" just
9978 because we're not a bridge or relay. Instead, we preserve whatever
9979 value the user set (or didn't set). Fixes bug 21150; bugfix
9981 - Resolve two possible underflows which could lead to creating and
9982 closing a lot of introduction point circuits in a non-stop loop.
9983 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
9985 o Minor bugfixes (portability):
9986 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
9987 It is supported by OpenBSD itself, and also by most OpenBSD
9988 variants (such as Bitrig). Fixes bug 20980; bugfix
9990 - When mapping a file of length greater than SIZE_MAX, do not
9991 silently truncate its contents. This issue could occur on 32 bit
9992 systems with large file support and files which are larger than 4
9993 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
9995 o Minor bugfixes (tor-resolve):
9996 - The tor-resolve command line tool now rejects hostnames over 255
9997 characters in length. Previously, it would silently truncate them,
9998 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
9999 Patch by "junglefowl".
10001 o Minor bugfixes (Windows services):
10002 - Be sure to initialize the monotonic time subsystem before using
10003 it, even when running as an NT service. Fixes bug 21356; bugfix
10007 Changes in version 0.3.0.2-alpha - 2017-01-23
10008 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
10009 cause relays and clients to crash, even if they were not built with
10010 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10011 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10012 version should upgrade.
10014 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
10015 time-to-live values, makes directory authorities enforce the 1-to-1
10016 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
10017 client-side onion service reachability bug, does better at selecting
10018 the set of fallback directories, and more.
10020 o Major bugfixes (security, also in 0.2.9.9):
10021 - Downgrade the "-ftrapv" option from "always on" to "only on when
10022 --enable-expensive-hardening is provided." This hardening option, like
10023 others, can turn survivable bugs into crashes--and having it on by
10024 default made a (relatively harmless) integer overflow bug into a
10025 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
10028 o Major features (security):
10029 - Change the algorithm used to decide DNS TTLs on client and server
10030 side, to better resist DNS-based correlation attacks like the
10031 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10032 Feamster. Now relays only return one of two possible DNS TTL
10033 values, and clients are willing to believe DNS TTL values up to 3
10034 hours long. Closes ticket 19769.
10036 o Major features (directory authority, security):
10037 - The default for AuthDirPinKeys is now 1: directory authorities
10038 will reject relays where the RSA identity key matches a previously
10039 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10041 o Major bugfixes (client, guard, crash):
10042 - In circuit_get_global_origin_list(), return the actual list of
10043 origin circuits. The previous version of this code returned the
10044 list of all the circuits, and could have caused strange bugs,
10045 including possible crashes. Fixes bug 21118; bugfix
10048 o Major bugfixes (client, onion service, also in 0.2.9.9):
10049 - Fix a client-side onion service reachability bug, where multiple
10050 socks requests to an onion service (or a single slow request)
10051 could cause us to mistakenly mark some of the service's
10052 introduction points as failed, and we cache that failure so
10053 eventually we run out and can't reach the service. Also resolves a
10054 mysterious "Remote server sent bogus reason code 65021" log
10055 warning. The bug was introduced in ticket 17218, where we tried to
10056 remember the circuit end reason as a uint16_t, which mangled
10057 negative values. Partially fixes bug 21056 and fixes bug 20307;
10058 bugfix on 0.2.8.1-alpha.
10060 o Major bugfixes (DNS):
10061 - Fix a bug that prevented exit nodes from caching DNS records for
10062 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10064 o Minor features (controller):
10065 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10066 shared-random values to the controller. Closes ticket 19925.
10068 o Minor features (entry guards):
10069 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10070 break regression tests.
10071 - Require UseEntryGuards when UseBridges is set, in order to make
10072 sure bridges aren't bypassed. Resolves ticket 20502.
10074 o Minor features (fallback directories):
10075 - Select 200 fallback directories for each release. Closes
10077 - Allow 3 fallback relays per operator, which is safe now that we
10078 are choosing 200 fallback relays. Closes ticket 20912.
10079 - Exclude relays affected by bug 20499 from the fallback list.
10080 Exclude relays from the fallback list if they are running versions
10081 known to be affected by bug 20499, or if in our tests they deliver
10082 a stale consensus (i.e. one that expired more than 24 hours ago).
10083 Closes ticket 20539.
10084 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10086 - Require fallback directories to have the same address and port for
10087 7 days (now that we have enough relays with this stability).
10088 Relays whose OnionOO stability timer is reset on restart by bug
10089 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10090 this issue. Closes ticket 20880; maintains short-term fix
10092 - Require fallbacks to have flags for 90% of the time (weighted
10093 decaying average), rather than 95%. This allows at least 73% of
10094 clients to bootstrap in the first 5 seconds without contacting an
10095 authority. Part of ticket 18828.
10096 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10097 weight for each candidate fallback. Closes ticket 20878.
10098 - Make it easier to change the output sort order of fallbacks.
10099 Closes ticket 20822.
10100 - Display the relay fingerprint when downloading consensuses from
10101 fallbacks. Closes ticket 20908.
10103 o Minor features (geoip, also in 0.2.9.9):
10104 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10107 o Minor features (next-gen onion service directories):
10108 - Remove the "EnableOnionServicesV3" consensus parameter that we
10109 introduced in 0.3.0.1-alpha: relays are now always willing to act
10110 as v3 onion service directories. Resolves ticket 19899.
10112 o Minor features (linting):
10113 - Enhance the changes file linter to warn on Tor versions that are
10114 prefixed with "tor-". Closes ticket 21096.
10116 o Minor features (logging):
10117 - In several places, describe unset ed25519 keys as "<unset>",
10118 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10120 o Minor bugfix (control protocol):
10121 - The reply to a "GETINFO config/names" request via the control
10122 protocol now spells the type "Dependent" correctly. This is a
10123 breaking change in the control protocol. (The field seems to be
10124 ignored by the most common known controllers.) Fixes bug 18146;
10125 bugfix on 0.1.1.4-alpha.
10127 o Minor bugfixes (bug resilience):
10128 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
10129 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
10130 Hans Jerry Illikainen.
10132 o Minor bugfixes (build):
10133 - Replace obsolete Autoconf macros with their modern equivalent and
10134 prevent similar issues in the future. Fixes bug 20990; bugfix
10137 o Minor bugfixes (client, guards):
10138 - Fix bug where Tor would think that there are circuits waiting for
10139 better guards even though those circuits have been freed. Fixes
10140 bug 21142; bugfix on 0.3.0.1-alpha.
10142 o Minor bugfixes (config):
10143 - Don't assert on startup when trying to get the options list and
10144 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
10145 options so of course they aren't ready yet. Fixes bug 21062;
10146 bugfix on 0.2.9.3-alpha.
10148 o Minor bugfixes (controller):
10149 - Make the GETINFO interface for inquiring about entry guards
10150 support the new guards backend. Fixes bug 20823; bugfix
10153 o Minor bugfixes (dead code):
10154 - Remove a redundant check for PidFile changes at runtime in
10155 options_transition_allowed(): this check is already performed
10156 regardless of whether the sandbox is active. Fixes bug 21123;
10157 bugfix on 0.2.5.4-alpha.
10159 o Minor bugfixes (documentation):
10160 - Update the tor manual page to document every option that can not
10161 be changed while tor is running. Fixes bug 21122.
10163 o Minor bugfixes (fallback directories):
10164 - Stop failing when a relay has no uptime data in
10165 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
10166 - Avoid checking fallback candidates' DirPorts if they are down in
10167 OnionOO. When a relay operator has multiple relays, this
10168 prioritizes relays that are up over relays that are down. Fixes
10169 bug 20926; bugfix on 0.2.8.3-alpha.
10170 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
10171 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
10173 o Minor bugfixes (guards, bootstrapping):
10174 - When connecting to a directory guard during bootstrap, do not mark
10175 the guard as successful until we receive a good-looking directory
10176 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
10178 o Minor bugfixes (onion services):
10179 - Fix the config reload pruning of old vs new services so it
10180 actually works when both ephemeral and non-ephemeral services are
10181 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
10182 - Allow the number of introduction points to be as low as 0, rather
10183 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
10185 o Minor bugfixes (IPv6):
10186 - Make IPv6-using clients try harder to find an IPv6 directory
10187 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
10188 - When IPv6 addresses have not been downloaded yet (microdesc
10189 consensus documents don't list relay IPv6 addresses), use hard-
10190 coded addresses for authorities, fallbacks, and configured
10191 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
10192 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
10194 o Minor bugfixes (memory leaks):
10195 - Fix a memory leak when configuring hidden services. Fixes bug
10196 20987; bugfix on 0.3.0.1-alpha.
10198 o Minor bugfixes (portability, also in 0.2.9.9):
10199 - Avoid crashing when Tor is built using headers that contain
10200 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10201 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10203 - Fix Libevent detection on platforms without Libevent 1 headers
10204 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10206 o Minor bugfixes (relay):
10207 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
10208 initializing the keys would reset the DataDirectory to 0700
10209 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
10210 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
10212 o Minor bugfixes (testing):
10213 - Remove undefined behavior from the backtrace generator by removing
10214 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
10216 o Minor bugfixes (unit tests):
10217 - Allow the unit tests to pass even when DNS lookups of bogus
10218 addresses do not fail as expected. Fixes bug 20862 and 20863;
10219 bugfix on unit tests introduced in 0.2.8.1-alpha
10220 through 0.2.9.4-alpha.
10222 o Code simplification and refactoring:
10223 - Refactor code to manipulate global_origin_circuit_list into
10224 separate functions. Closes ticket 20921.
10226 o Documentation (formatting):
10227 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
10228 blocks were incorrectly appearing. Closes ticket 20885.
10230 o Documentation (man page):
10231 - Clarify many options in tor.1 and add some min/max values for
10232 HiddenService options. Closes ticket 21058.
10235 Changes in version 0.2.9.9 - 2017-01-23
10236 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
10237 cause relays and clients to crash, even if they were not built with
10238 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10239 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10240 version should upgrade.
10242 This release also resolves a client-side onion service reachability
10243 bug, and resolves a pair of small portability issues.
10245 o Major bugfixes (security):
10246 - Downgrade the "-ftrapv" option from "always on" to "only on when
10247 --enable-expensive-hardening is provided." This hardening option,
10248 like others, can turn survivable bugs into crashes -- and having
10249 it on by default made a (relatively harmless) integer overflow bug
10250 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10251 bugfix on 0.2.9.1-alpha.
10253 o Major bugfixes (client, onion service):
10254 - Fix a client-side onion service reachability bug, where multiple
10255 socks requests to an onion service (or a single slow request)
10256 could cause us to mistakenly mark some of the service's
10257 introduction points as failed, and we cache that failure so
10258 eventually we run out and can't reach the service. Also resolves a
10259 mysterious "Remote server sent bogus reason code 65021" log
10260 warning. The bug was introduced in ticket 17218, where we tried to
10261 remember the circuit end reason as a uint16_t, which mangled
10262 negative values. Partially fixes bug 21056 and fixes bug 20307;
10263 bugfix on 0.2.8.1-alpha.
10265 o Minor features (geoip):
10266 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10269 o Minor bugfixes (portability):
10270 - Avoid crashing when Tor is built using headers that contain
10271 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10272 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10274 - Fix Libevent detection on platforms without Libevent 1 headers
10275 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10278 Changes in version 0.3.0.1-alpha - 2016-12-19
10279 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
10280 series. It strengthens Tor's link and circuit handshakes by
10281 identifying relays by their Ed25519 keys, improves the algorithm that
10282 clients use to choose and maintain their list of guards, and includes
10283 additional backend support for the next-generation hidden service
10284 design. It also contains numerous other small features and
10285 improvements to security, correctness, and performance.
10287 Below are the changes since 0.2.9.8.
10289 o Major features (guard selection algorithm):
10290 - Tor's guard selection algorithm has been redesigned from the
10291 ground up, to better support unreliable networks and restrictive
10292 sets of entry nodes, and to better resist guard-capture attacks by
10293 hostile local networks. Implements proposal 271; closes
10296 o Major features (next-generation hidden services):
10297 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10298 prop224 aka "Next Generation Hidden Services". Service and clients
10299 don't use this functionality yet. Closes ticket 19043. Based on
10300 initial code by Alec Heifetz.
10301 - Relays now support the HSDir version 3 protocol, so that they can
10302 can store and serve v3 descriptors. This is part of the next-
10303 generation onion service work detailed in proposal 224. Closes
10306 o Major features (protocol, ed25519 identity keys):
10307 - Relays now use Ed25519 to prove their Ed25519 identities and to
10308 one another, and to clients. This algorithm is faster and more
10309 secure than the RSA-based handshake we've been doing until now.
10310 Implements the second big part of proposal 220; Closes
10312 - Clients now support including Ed25519 identity keys in the EXTEND2
10313 cells they generate. By default, this is controlled by a consensus
10314 parameter, currently disabled. You can turn this feature on for
10315 testing by setting ExtendByEd25519ID in your configuration. This
10316 might make your traffic appear different than the traffic
10317 generated by other users, however. Implements part of ticket
10318 15056; part of proposal 220.
10319 - Relays now understand requests to extend to other relays by their
10320 Ed25519 identity keys. When an Ed25519 identity key is included in
10321 an EXTEND2 cell, the relay will only extend the circuit if the
10322 other relay can prove ownership of that identity. Implements part
10323 of ticket 15056; part of proposal 220.
10325 o Major bugfixes (scheduler):
10326 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10327 caused the channel scheduler to behave more or less randomly,
10328 rather than preferring channels with higher-priority circuits.
10329 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10331 o Minor features (controller):
10332 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10333 rather than "unrecognized." Closes ticket 20389; patch from
10336 o Minor features (diagnostic, directory client):
10337 - Warn when we find an unexpected inconsistency in directory
10338 download status objects. Prevents some negative consequences of
10341 o Minor features (directory authority):
10342 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10343 default) to control whether authorities should try to probe relays
10344 by their Ed25519 link keys. This option will go away in a few
10345 releases--unless we encounter major trouble in our ed25519 link
10346 protocol rollout, in which case it will serve as a safety option.
10348 o Minor features (directory cache):
10349 - Relays and bridges will now refuse to serve the consensus they
10350 have if they know it is too old for a client to use. Closes
10353 o Minor features (ed25519 link handshake):
10354 - Advertise support for the ed25519 link handshake using the
10355 subprotocol-versions mechanism, so that clients can tell which
10356 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10358 o Minor features (fingerprinting resistance, authentication):
10359 - Extend the length of RSA keys used for TLS link authentication to
10360 2048 bits. (These weren't used for forward secrecy; for forward
10361 secrecy, we used P256.) Closes ticket 13752.
10363 o Minor features (infrastructure):
10364 - Implement smartlist_add_strdup() function. Replaces the use of
10365 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10367 o Minor bugfixes (client):
10368 - When clients that use bridges start up with a cached consensus on
10369 disk, they were ignoring it and downloading a new one. Now they
10370 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
10372 o Minor bugfixes (configuration):
10373 - Accept non-space whitespace characters after the severity level in
10374 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
10375 - Support "TByte" and "TBytes" units in options given in bytes.
10376 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
10377 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
10379 o Minor bugfixes (consensus weight):
10380 - Add new consensus method that initializes bw weights to 1 instead
10381 of 0. This prevents a zero weight from making it all the way to
10382 the end (happens in small testing networks) and causing an error.
10383 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
10385 o Minor bugfixes (descriptors):
10386 - Correctly recognise downloaded full descriptors as valid, even
10387 when using microdescriptors as circuits. This affects clients with
10388 FetchUselessDescriptors set, and may affect directory authorities.
10389 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
10391 o Minor bugfixes (directory system):
10392 - Download all consensus flavors, descriptors, and authority
10393 certificates when FetchUselessDescriptors is set, regardless of
10394 whether tor is a directory cache or not. Fixes bug 20667; bugfix
10395 on all recent tor versions.
10396 - Bridges and relays now use microdescriptors (like clients do)
10397 rather than old-style router descriptors. Now bridges will blend
10398 in with clients in terms of the circuits they build. Fixes bug
10399 6769; bugfix on 0.2.3.2-alpha.
10401 o Minor bugfixes (ed25519 certificates):
10402 - Correctly interpret ed25519 certificates that would expire some
10403 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
10405 o Minor bugfixes (hidden services):
10406 - Stop ignoring misconfigured hidden services. Instead, refuse to
10407 start tor until the misconfigurations have been corrected. Fixes
10408 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
10411 o Minor bugfixes (memory leak at exit):
10412 - Fix a small harmless memory leak at exit of the previously unused
10413 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
10416 o Minor bugfixes (util):
10417 - When finishing writing a file to disk, if we were about to replace
10418 the file with the temporary file created before and we fail to
10419 replace it, remove the temporary file so it doesn't stay on disk.
10420 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10422 o Minor bugfixes (Windows):
10423 - Check for getpagesize before using it to mmap files. This fixes
10424 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10425 0.1.2.1-alpha. Reported by "ice".
10427 o Code simplification and refactoring:
10428 - Abolish all global guard context in entrynodes.c; replace with new
10429 guard_selection_t structure as preparation for proposal 271.
10430 Closes ticket 19858.
10431 - Introduce rend_service_is_ephemeral() that tells if given onion
10432 service is ephemeral. Replace unclear NULL-checkings for service
10433 directory with this function. Closes ticket 20526.
10434 - Extract magic numbers in circuituse.c into defined variables.
10435 - Refactor circuit_is_available_for_use to remove unnecessary check.
10436 - Refactor circuit_predict_and_launch_new for readability and
10437 testability. Closes ticket 18873.
10438 - Refactor large if statement in purpose_needs_anonymity to use
10439 switch statement instead. Closes part of ticket 20077.
10440 - Refactor the hashing API to return negative values for errors, as
10441 is done as throughout the codebase. Closes ticket 20717.
10442 - Remove data structures that were used to index or_connection
10443 objects by their RSA identity digests. These structures are fully
10444 redundant with the similar structures used in the
10445 channel abstraction.
10446 - Remove duplicate code in the channel_write_*cell() functions.
10447 Closes ticket 13827; patch from Pingl.
10448 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10449 use only purpose_needs_anonymity. Closes part of ticket 20077.
10450 - The code to generate and parse EXTEND and EXTEND2 cells has been
10451 replaced with code automatically generated by the
10455 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10456 20622; bugfix on 0.2.5.1-alpha.
10457 - Change '1' to 'weight_scale' in consensus bw weights calculation
10458 comments, as that is reality. Closes ticket 20273. Patch
10460 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10461 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10463 - Stop the man page from incorrectly stating that HiddenServiceDir
10464 must already exist. Fixes 20486.
10465 - Clarify that when ClientRejectInternalAddresses is enabled (which
10466 is the default), multicast DNS hostnames for machines on the local
10467 network (of the form *.local) are also rejected. Closes
10470 o Removed features:
10471 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10472 limit for relays running on a single IP applies to authority IP
10473 addresses as well as to non-authority IP addresses. Closes
10475 - The UseDirectoryGuards torrc option no longer exists: all users
10476 that use entry guards will also use directory guards. Related to
10477 proposal 271; implements part of ticket 20831.
10480 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10481 from "overcaffeinated".
10482 - Perform the coding style checks when running the tests and fail
10483 when coding style violations are found. Closes ticket 5500.
10484 - Add tests for networkstatus_compute_bw_weights_v10.
10485 - Add unit tests circuit_predict_and_launch_new.
10486 - Extract dummy_origin_circuit_new so it can be used by other
10490 Changes in version 0.2.8.12 - 2016-12-19
10491 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10492 below) where Tor clients could crash when attempting to visit a
10493 hostile hidden service. Clients are recommended to upgrade as packages
10494 become available for their systems.
10496 It also includes an updated list of fallback directories, backported
10499 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10500 backported to 0.2.8 in the future.
10502 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10503 - Fix a bug in parsing that could cause clients to read a single
10504 byte past the end of an allocated region. This bug could be used
10505 to cause hardened clients (built with --enable-expensive-hardening)
10506 to crash if they tried to visit a hostile hidden service. Non-
10507 hardened clients are only affected depending on the details of
10508 their platform's memory allocator. Fixes bug 21018; bugfix on
10509 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10510 2016-12-002 and as CVE-2016-1254.
10512 o Minor features (fallback directory list, backported from 0.2.9.8):
10513 - Replace the 81 remaining fallbacks of the 100 originally
10514 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10515 fallbacks (123 new, 54 existing, 27 removed) generated in December
10516 2016. Resolves ticket 20170.
10518 o Minor features (geoip, backported from 0.2.9.7-rc):
10519 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10523 Changes in version 0.2.9.8 - 2016-12-19
10524 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10526 The Tor 0.2.9 series makes mandatory a number of security features
10527 that were formerly optional. It includes support for a new shared-
10528 randomness protocol that will form the basis for next generation
10529 hidden services, includes a single-hop hidden service mode for
10530 optimizing .onion services that don't actually want to be hidden,
10531 tries harder not to overload the directory authorities with excessive
10532 downloads, and supports a better protocol versioning scheme for
10533 improved compatibility with other implementations of the Tor protocol.
10535 And of course, there are numerous other bugfixes and improvements.
10537 This release also includes a fix for a medium-severity issue (bug
10538 21018 below) where Tor clients could crash when attempting to visit a
10539 hostile hidden service. Clients are recommended to upgrade as packages
10540 become available for their systems.
10542 Below are the changes since 0.2.9.7-rc. For a list of all changes
10543 since 0.2.8, see the ReleaseNotes file.
10545 o Major bugfixes (parsing, security):
10546 - Fix a bug in parsing that could cause clients to read a single
10547 byte past the end of an allocated region. This bug could be used
10548 to cause hardened clients (built with --enable-expensive-hardening)
10549 to crash if they tried to visit a hostile hidden service. Non-
10550 hardened clients are only affected depending on the details of
10551 their platform's memory allocator. Fixes bug 21018; bugfix on
10552 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10553 2016-12-002 and as CVE-2016-1254.
10555 o Minor features (fallback directory list):
10556 - Replace the 81 remaining fallbacks of the 100 originally
10557 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10558 fallbacks (123 new, 54 existing, 27 removed) generated in December
10559 2016. Resolves ticket 20170.
10562 Changes in version 0.2.9.7-rc - 2016-12-12
10563 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10564 including a few that had prevented tests from passing on
10567 o Minor features (geoip):
10568 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10571 o Minor bugfix (build):
10572 - The current Git revision when building from a local repository is
10573 now detected correctly when using git worktrees. Fixes bug 20492;
10574 bugfix on 0.2.3.9-alpha.
10576 o Minor bugfixes (directory authority):
10577 - When computing old Tor protocol line version in protover, we were
10578 looking at 0.2.7.5 twice instead of a specific case for
10579 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10581 o Minor bugfixes (download scheduling):
10582 - Resolve a "bug" warning when considering a download schedule whose
10583 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10585 o Minor bugfixes (logging):
10586 - Downgrade a harmless log message about the
10587 pending_entry_connections list from "warn" to "info". Mitigates
10590 o Minor bugfixes (memory leak):
10591 - Fix a small memory leak when receiving AF_UNIX connections on a
10592 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10593 - When moving a signed descriptor object from a source to an
10594 existing destination, free the allocated memory inside that
10595 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10597 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10598 - Fix a memory leak and use-after-free error when removing entries
10599 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10600 0.2.5.5-alpha. Patch from "cypherpunks".
10602 o Minor bugfixes (portability):
10603 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10604 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10606 o Minor bugfixes (unit tests):
10607 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10608 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10609 - Fix tolerances in unit tests for monotonic time comparisons
10610 between nanoseconds and microseconds. Previously, we accepted a 10
10611 us difference only, which is not realistic on every platform's
10612 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10613 - Remove a double-free in the single onion service unit test. Stop
10614 ignoring a return value. Make future changes less error-prone.
10615 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10618 Changes in version 0.2.8.11 - 2016-12-08
10619 Tor 0.2.8.11 backports fixes for additional portability issues that
10620 could prevent Tor from building correctly on OSX Sierra, or with
10621 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10624 o Minor bugfixes (portability):
10625 - Avoid compilation errors when building on OSX Sierra. Sierra began
10626 to support the getentropy() and clock_gettime() APIs, but created
10627 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10628 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
10629 monotonic time interfaces. Fixes bug 20865. Bugfix
10632 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10633 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10634 architectures. Closes ticket 20588.
10637 Changes in version 0.2.8.10 - 2016-12-02
10638 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
10639 unusable after they left standby mode. It also backports fixes for
10640 a few portability issues and a small but problematic memory leak.
10642 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
10643 - When Tor leaves standby because of a new application request, open
10644 circuits as needed to serve that request. Previously, we would
10645 potentially wait a very long time. Fixes part of bug 19969; bugfix
10648 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
10649 - Clients now respond to new application stream requests immediately
10650 when they arrive, rather than waiting up to one second before
10651 starting to handle them. Fixes part of bug 19969; bugfix
10654 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
10655 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10656 successfully targeting earlier versions of OSX. Resolves
10659 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10660 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10661 20551; bugfix on 0.2.1.1-alpha.
10663 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
10664 - Work around a memory leak in OpenSSL 1.1 when encoding public
10665 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10667 o Minor features (geoip):
10668 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10671 Changes in version 0.2.9.6-rc - 2016-12-02
10672 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
10673 version. We hope that it will be ready to become stable soon, and we
10674 encourage everyone to test this release. If no showstopper bugs are
10675 found here, the next 0.2.9 release will be stable.
10677 o Major bugfixes (relay, resolver, logging):
10678 - For relays that don't know their own address, avoid attempting a
10679 local hostname resolve for each descriptor we download. This
10680 will cut down on the number of "Success: chose address 'x.x.x.x'"
10681 log lines, and also avoid confusing clock jumps if the resolver
10682 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
10684 o Minor bugfixes (client, fascistfirewall):
10685 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
10686 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
10688 o Minor bugfixes (hidden services):
10689 - Stop ignoring the anonymity status of saved keys for hidden
10690 services and single onion services when first starting tor.
10691 Instead, refuse to start tor if any hidden service key has been
10692 used in a different hidden service anonymity mode. Fixes bug
10693 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
10695 o Minor bugfixes (portability):
10696 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10697 successfully targeting earlier versions of OSX. Resolves
10699 - Run correctly when built on Windows build environments that
10700 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
10702 o Minor bugfixes (single onion services, Tor2web):
10703 - Stop complaining about long-term one-hop circuits deliberately
10704 created by single onion services and Tor2web. These log messages
10705 are intended to diagnose issue 8387, which relates to circuits
10706 hanging around forever for no reason. Fixes bug 20613; bugfix on
10707 0.2.9.1-alpha. Reported by "pastly".
10709 o Minor bugfixes (unit tests):
10710 - Stop spurious failures in the local interface address discovery
10711 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
10715 - Correct the minimum bandwidth value in torrc.sample, and queue a
10716 corresponding change for torrc.minimal. Closes ticket 20085.
10719 Changes in version 0.2.9.5-alpha - 2016-11-08
10720 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
10721 version. We believe one or two probably remain, and we encourage
10722 everyone to test this release.
10724 o Major bugfixes (client performance):
10725 - Clients now respond to new application stream requests immediately
10726 when they arrive, rather than waiting up to one second before
10727 starting to handle them. Fixes part of bug 19969; bugfix
10730 o Major bugfixes (client reliability):
10731 - When Tor leaves standby because of a new application request, open
10732 circuits as needed to serve that request. Previously, we would
10733 potentially wait a very long time. Fixes part of bug 19969; bugfix
10736 o Major bugfixes (download scheduling):
10737 - When using an exponential backoff schedule, do not give up on
10738 downloading just because we have failed a bunch of times. Since
10739 each delay is longer than the last, retrying indefinitely won't
10740 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
10741 - If a consensus expires while we are waiting for certificates to
10742 download, stop waiting for certificates.
10743 - If we stop waiting for certificates less than a minute after we
10744 started downloading them, do not consider the certificate download
10745 failure a separate failure. Fixes bug 20533; bugfix
10747 - Remove the maximum delay on exponential-backoff scheduling. Since
10748 we now allow an infinite number of failures (see ticket 20536), we
10749 must now allow the time to grow longer on each failure. Fixes part
10750 of bug 20534; bugfix on 0.2.9.1-alpha.
10751 - Make our initial download delays closer to those from 0.2.8. Fixes
10752 another part of bug 20534; bugfix on 0.2.9.1-alpha.
10753 - When determining when to download a directory object, handle times
10754 after 2038 if the operating system supports them. (Someday this
10755 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
10756 - When using exponential backoff in test networks, use a lower
10757 exponent, so the delays do not vary as much. This helps test
10758 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
10760 o Minor features (geoip):
10761 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10764 o Minor bugfixes (client directory scheduling):
10765 - Treat "relay too busy to answer request" as a failed request and a
10766 reason to back off on our retry frequency. This is safe now that
10767 exponential backoffs retry indefinitely, and avoids a bug where we
10768 would reset our download schedule erroneously. Fixes bug 20593;
10769 bugfix on 0.2.9.1-alpha.
10771 o Minor bugfixes (client, logging):
10772 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
10773 assume all nodes support EXTEND2. Use ntor whenever a key is
10774 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
10775 - On DNSPort, stop logging a BUG warning on a failed hostname
10776 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
10778 o Minor bugfixes (hidden services):
10779 - When configuring hidden services, check every hidden service
10780 directory's permissions. Previously, we only checked the last
10781 hidden service. Fixes bug 20529; bugfix the work to fix 13942
10784 o Minor bugfixes (portability):
10785 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10786 architectures. Closes ticket 20588.
10787 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
10788 removed the ECDH ciphers which caused the tests to fail on
10789 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
10790 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10791 20551; bugfix on 0.2.1.1-alpha.
10793 o Minor bugfixes (relay bootstrap):
10794 - Ensure relays don't make multiple connections during bootstrap.
10795 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
10797 o Minor bugfixes (relay):
10798 - Work around a memory leak in OpenSSL 1.1 when encoding public
10799 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10800 - Avoid a small memory leak when informing worker threads about
10801 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
10802 - Do not try to parallelize workers more than 16x without the user
10803 explicitly configuring us to do so, even if we do detect more than
10804 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10806 o Minor bugfixes (single onion services):
10807 - Start correctly when creating a single onion service in a
10808 directory that did not previously exist. Fixes bug 20484; bugfix
10811 o Minor bugfixes (testing):
10812 - Avoid a unit test failure on systems with over 16 detectable CPU
10813 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
10816 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
10817 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
10818 - Module-level documentation for several more modules. Closes
10819 tickets 19287 and 19290.
10822 Changes in version 0.2.8.9 - 2016-10-17
10823 Tor 0.2.8.9 backports a fix for a security hole in previous versions
10824 of Tor that would allow a remote attacker to crash a Tor client,
10825 hidden service, relay, or authority. All Tor users should upgrade to
10826 this version, or to 0.2.9.4-alpha. Patches will be released for older
10829 o Major features (security fixes, also in 0.2.9.4-alpha):
10830 - Prevent a class of security bugs caused by treating the contents
10831 of a buffer chunk as if they were a NUL-terminated string. At
10832 least one such bug seems to be present in all currently used
10833 versions of Tor, and would allow an attacker to remotely crash
10834 most Tor instances, especially those compiled with extra compiler
10835 hardening. With this defense in place, such bugs can't crash Tor,
10836 though we should still fix them as they occur. Closes ticket
10837 20384 (TROVE-2016-10-001).
10839 o Minor features (geoip):
10840 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10844 Changes in version 0.2.9.4-alpha - 2016-10-17
10845 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
10846 that would allow a remote attacker to crash a Tor client, hidden
10847 service, relay, or authority. All Tor users should upgrade to this
10848 version, or to 0.2.8.9. Patches will be released for older versions
10851 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
10852 previous versions of Tor, including the implementation of a feature to
10853 future- proof the Tor ecosystem against protocol changes, some bug
10854 fixes necessary for Tor Browser to use unix domain sockets correctly,
10855 and several portability improvements. We anticipate that this will be
10856 the last alpha in the Tor 0.2.9 series, and that the next release will
10857 be a release candidate.
10859 o Major features (security fixes):
10860 - Prevent a class of security bugs caused by treating the contents
10861 of a buffer chunk as if they were a NUL-terminated string. At
10862 least one such bug seems to be present in all currently used
10863 versions of Tor, and would allow an attacker to remotely crash
10864 most Tor instances, especially those compiled with extra compiler
10865 hardening. With this defense in place, such bugs can't crash Tor,
10866 though we should still fix them as they occur. Closes ticket
10867 20384 (TROVE-2016-10-001).
10869 o Major features (subprotocol versions):
10870 - Tor directory authorities now vote on a set of recommended
10871 subprotocol versions, and on a set of required subprotocol
10872 versions. Clients and relays that lack support for a _required_
10873 subprotocol version will not start; those that lack support for a
10874 _recommended_ subprotocol version will warn the user to upgrade.
10875 Closes ticket 19958; implements part of proposal 264.
10876 - Tor now uses "subprotocol versions" to indicate compatibility.
10877 Previously, versions of Tor looked at the declared Tor version of
10878 a relay to tell whether they could use a given feature. Now, they
10879 should be able to rely on its declared subprotocol versions. This
10880 change allows compatible implementations of the Tor protocol(s) to
10881 exist without pretending to be 100% bug-compatible with particular
10882 releases of Tor itself. Closes ticket 19958; implements part of
10885 o Minor feature (fallback directories):
10886 - Remove broken fallbacks from the hard-coded fallback directory
10887 list. Closes ticket 20190; patch by teor.
10889 o Minor features (client, directory):
10890 - Since authorities now omit all routers that lack the Running and
10891 Valid flags, we assume that any relay listed in the consensus must
10892 have those flags. Closes ticket 20001; implements part of
10895 o Minor features (compilation, portability):
10896 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
10899 o Minor features (development tools, etags):
10900 - Teach the "make tags" Makefile target how to correctly find
10901 "MOCK_IMPL" function definitions. Patch from nherring; closes
10904 o Minor features (geoip):
10905 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
10908 o Minor features (unix domain sockets):
10909 - When configuring a unix domain socket for a SocksPort,
10910 ControlPort, or Hidden service, you can now wrap the address in
10911 quotes, using C-style escapes inside the quotes. This allows unix
10912 domain socket paths to contain spaces.
10914 o Minor features (virtual addresses):
10915 - Increase the maximum number of bits for the IPv6 virtual network
10916 prefix from 16 to 104. In this way, the condition for address
10917 allocation is less restrictive. Closes ticket 20151; feature
10920 o Minor bugfixes (address discovery):
10921 - Stop reordering IP addresses returned by the OS. This makes it
10922 more likely that Tor will guess the same relay IP address every
10923 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
10924 Reported by René Mayrhofer, patch by "cypherpunks".
10926 o Minor bugfixes (client, unix domain sockets):
10927 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
10928 the client address is meaningless. Fixes bug 20261; bugfix
10931 o Minor bugfixes (compilation, OpenBSD):
10932 - Detect Libevent2 functions correctly on systems that provide
10933 libevent2, but where libevent1 is linked with -levent. Fixes bug
10934 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
10936 o Minor bugfixes (configuration):
10937 - When parsing quoted configuration values from the torrc file,
10938 handle windows line endings correctly. Fixes bug 19167; bugfix on
10939 0.2.0.16-alpha. Patch from "Pingl".
10941 o Minor bugfixes (getpass):
10942 - Defensively fix a non-triggerable heap corruption at do_getpass()
10943 to protect ourselves from mistakes in the future. Fixes bug
10944 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
10947 o Minor bugfixes (hidden service):
10948 - Allow hidden services to run on IPv6 addresses even when the
10949 IPv6Exit option is not set. Fixes bug 18357; bugfix
10953 - Add module-level internal documentation for 36 C files that
10954 previously didn't have a high-level overview. Closes ticket #20385.
10956 o Required libraries:
10957 - When building with OpenSSL, Tor now requires version 1.0.1 or
10958 later. OpenSSL 1.0.0 and earlier are no longer supported by the
10959 OpenSSL team, and should not be used. Closes ticket 20303.
10962 Changes in version 0.2.9.3-alpha - 2016-09-23
10963 Tor 0.2.9.3-alpha adds improved support for entities that want to make
10964 high-performance services available through the Tor .onion mechanism
10965 without themselves receiving anonymity as they host those services. It
10966 also tries harder to ensure that all steps on a circuit are using the
10967 strongest crypto possible, strengthens some TLS properties, and
10968 resolves several bugs -- including a pair of crash bugs from the 0.2.8
10969 series. Anybody running an earlier version of 0.2.9.x should upgrade.
10971 o Major bugfixes (crash, also in 0.2.8.8):
10972 - Fix a complicated crash bug that could affect Tor clients
10973 configured to use bridges when replacing a networkstatus consensus
10974 in which one of their bridges was mentioned. OpenBSD users saw
10975 more crashes here, but all platforms were potentially affected.
10976 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
10978 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
10979 - Fix a timing-dependent assertion failure that could occur when we
10980 tried to flush from a circuit after having freed its cells because
10981 of an out-of-memory condition. Fixes bug 20203; bugfix on
10982 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
10985 o Major features (circuit building, security):
10986 - Authorities, relays and clients now require ntor keys in all
10987 descriptors, for all hops (except for rare hidden service protocol
10988 cases), for all circuits, and for all other roles. Part of
10990 - Tor authorities, relays, and clients only use ntor, except for
10991 rare cases in the hidden service protocol. Part of ticket 19163.
10993 o Major features (single-hop "hidden" services):
10994 - Add experimental HiddenServiceSingleHopMode and
10995 HiddenServiceNonAnonymousMode options. When both are set to 1,
10996 every hidden service on a Tor instance becomes a non-anonymous
10997 Single Onion Service. Single Onions make one-hop (direct)
10998 connections to their introduction and renzedvous points. One-hop
10999 circuits make Single Onion servers easily locatable, but clients
11000 remain location-anonymous. This is compatible with the existing
11001 hidden service implementation, and works on the current tor
11002 network without any changes to older relays or clients. Implements
11003 proposal 260, completes ticket 17178. Patch by teor and asn.
11005 o Major features (resource management):
11006 - Tor can now notice it is about to run out of sockets, and
11007 preemptively close connections of lower priority. (This feature is
11008 off by default for now, since the current prioritizing method is
11009 yet not mature enough. You can enable it by setting
11010 "DisableOOSCheck 0", but watch out: it might close some sockets
11011 you would rather have it keep.) Closes ticket 18640.
11013 o Major bugfixes (circuit building):
11014 - Hidden service client-to-intro-point and service-to-rendezvous-
11015 point circuits use the TAP key supplied by the protocol, to avoid
11016 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
11018 o Major bugfixes (compilation, OpenBSD):
11019 - Fix a Libevent-detection bug in our autoconf script that would
11020 prevent Tor from linking successfully on OpenBSD. Patch from
11021 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
11023 o Major bugfixes (hidden services):
11024 - Clients now require hidden services to include the TAP keys for
11025 their intro points in the hidden service descriptor. This prevents
11026 an inadvertent upgrade to ntor, which a malicious hidden service
11027 could use to distinguish clients by consensus version. Fixes bug
11028 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
11030 o Minor features (security, TLS):
11031 - Servers no longer support clients that without AES ciphersuites.
11032 (3DES is no longer considered an acceptable cipher.) We believe
11033 that no such Tor clients currently exist, since Tor has required
11034 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
11036 o Minor feature (fallback directories):
11037 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11038 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11039 2016. Closes ticket 20190; patch by teor.
11041 o Minor features (geoip, also in 0.2.8.8):
11042 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11045 o Minor feature (port flags):
11046 - Add new flags to the *Port options to finer control over which
11047 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
11048 and the synthetic flag OnionTrafficOnly, which is equivalent to
11049 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
11050 18693; patch by "teor".
11052 o Minor features (directory authority):
11053 - After voting, if the authorities decide that a relay is not
11054 "Valid", they no longer include it in the consensus at all. Closes
11055 ticket 20002; implements part of proposal 272.
11057 o Minor features (testing):
11058 - Disable memory protections on OpenBSD when performing our unit
11059 tests for memwipe(). The test deliberately invokes undefined
11060 behavior, and the OpenBSD protections interfere with this. Patch
11061 from "rubiate". Closes ticket 20066.
11063 o Minor features (testing, ipv6):
11064 - Add the single-onion and single-onion-ipv6 chutney targets to
11065 "make test-network-all". This requires a recent chutney version
11066 with the single onion network flavours (git c72a652 or later).
11067 Closes ticket 20072; patch by teor.
11068 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
11069 tests. Remove bridges+hs, as it's somewhat redundant. This
11070 requires a recent chutney version that supports IPv6 clients,
11071 relays, and authorities. Closes ticket 20069; patch by teor.
11073 o Minor features (Tor2web):
11074 - Make Tor2web clients respect ReachableAddresses. This feature was
11075 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
11076 0.2.8.7. Implements feature 20034. Patch by teor.
11078 o Minor features (unit tests):
11079 - We've done significant work to make the unit tests run faster.
11080 - Our link-handshake unit tests now check that when invalid
11081 handshakes fail, they fail with the error messages we expected.
11082 - Our unit testing code that captures log messages no longer
11083 prevents them from being written out if the user asked for them
11084 (by passing --debug or --info or or --notice --warn to the "test"
11085 binary). This change prevents us from missing unexpected log
11086 messages simply because we were looking for others. Related to
11088 - The unit tests now log all warning messages with the "BUG" flag.
11089 Previously, they only logged errors by default. This change will
11090 help us make our testing code more correct, and make sure that we
11091 only hit this code when we mean to. In the meantime, however,
11092 there will be more warnings in the unit test logs than before.
11093 This is preparatory work for ticket 19999.
11094 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
11095 assertion as a test failure.
11097 o Minor bug fixes (circuits):
11098 - Use the CircuitBuildTimeout option whenever
11099 LearnCircuitBuildTimeout is disabled. Previously, we would respect
11100 the option when a user disabled it, but not when it was disabled
11101 because some other option was set. Fixes bug 20073; bugfix on
11102 0.2.4.12-alpha. Patch by teor.
11104 o Minor bugfixes (allocation):
11105 - Change how we allocate memory for large chunks on buffers, to
11106 avoid a (currently impossible) integer overflow, and to waste less
11107 space when allocating unusually large chunks. Fixes bug 20081;
11108 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
11109 - Always include orconfig.h before including any other C headers.
11110 Sometimes, it includes macros that affect the behavior of the
11111 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
11112 first version to use AC_USE_SYSTEM_EXTENSIONS).
11113 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
11114 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
11115 Patch from Gisle Vanem.
11116 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
11117 They apparently require a set of annotations that we aren't
11118 currently using, and they create false positives in our pthreads
11119 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
11121 o Minor bugfixes (directory authority):
11122 - Die with a more useful error when the operator forgets to place
11123 the authority_signing_key file into the keys directory. This
11124 avoids an uninformative assert & traceback about having an invalid
11125 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
11126 - When allowing private addresses, mark Exits that only exit to
11127 private locations as such. Fixes bug 20064; bugfix
11130 o Minor bugfixes (documentation):
11131 - Document the default PathsNeededToBuildCircuits value that's used
11132 by clients when the directory authorities don't set
11133 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
11134 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
11135 - Fix manual for the User option: it takes a username, not a UID.
11136 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
11139 o Minor bugfixes (hidden services):
11140 - Stop logging intro point details to the client log on certain
11141 error conditions. Fixed as part of bug 20012; bugfix on
11142 0.2.4.8-alpha. Patch by teor.
11144 o Minor bugfixes (IPv6, testing):
11145 - Check for IPv6 correctly on Linux when running test networks.
11146 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
11148 o Minor bugfixes (Linux seccomp2 sandbox):
11149 - Add permission to run the sched_yield() and sigaltstack() system
11150 calls, in order to support versions of Tor compiled with asan or
11151 ubsan code that use these calls. Now "sandbox 1" and
11152 "--enable-expensive-hardening" should be compatible on more
11153 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
11155 o Minor bugfixes (logging):
11156 - When logging a message from the BUG() macro, be explicit about
11157 what we were asserting. Previously we were confusing what we were
11158 asserting with what the bug was. Fixes bug 20093; bugfix
11160 - When we are unable to remove the bw_accounting file, do not warn
11161 if the reason we couldn't remove it was that it didn't exist.
11162 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
11164 o Minor bugfixes (option parsing):
11165 - Count unix sockets when counting client listeners (SOCKS, Trans,
11166 NATD, and DNS). This has no user-visible behaviour changes: these
11167 options are set once, and never read. Required for correct
11168 behaviour in ticket 17178. Fixes bug 19677; bugfix on
11169 0.2.6.3-alpha. Patch by teor.
11171 o Minor bugfixes (options):
11172 - Check the consistency of UseEntryGuards and EntryNodes more
11173 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
11175 - Stop changing the configured value of UseEntryGuards on
11176 authorities and Tor2web clients. Fixes bug 20074; bugfix on
11177 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
11180 o Minor bugfixes (Tor2web):
11181 - Prevent Tor2web clients running hidden services, these services
11182 are not anonymous due to the one-hop client paths. Fixes bug
11183 19678. Patch by teor.
11185 o Minor bugfixes (unit tests):
11186 - Fix a shared-random unit test that was failing on big endian
11187 architectures due to internal representation of a integer copied
11188 to a buffer. The test is changed to take a full 32 bytes of data
11189 and use the output of a python script that make the COMMIT and
11190 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
11192 - The tor_tls_server_info_callback unit test no longer crashes when
11193 debug-level logging is turned on. Fixes bug 20041; bugfix
11197 Changes in version 0.2.8.8 - 2016-09-23
11198 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
11199 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
11200 who select public relays as their bridges.
11202 o Major bugfixes (crash):
11203 - Fix a complicated crash bug that could affect Tor clients
11204 configured to use bridges when replacing a networkstatus consensus
11205 in which one of their bridges was mentioned. OpenBSD users saw
11206 more crashes here, but all platforms were potentially affected.
11207 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11209 o Major bugfixes (relay, OOM handler):
11210 - Fix a timing-dependent assertion failure that could occur when we
11211 tried to flush from a circuit after having freed its cells because
11212 of an out-of-memory condition. Fixes bug 20203; bugfix on
11213 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11216 o Minor feature (fallback directories):
11217 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11218 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11219 2016. Closes ticket 20190; patch by teor.
11221 o Minor features (geoip):
11222 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11226 Changes in version 0.2.9.2-alpha - 2016-08-24
11227 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
11228 several new features and bugfixes. It also includes an important
11229 authority update and an important bugfix from 0.2.8.7. Everyone who
11230 sets the ReachableAddresses option, and all bridges, are strongly
11231 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
11233 o Directory authority changes (also in 0.2.8.7):
11234 - The "Tonga" bridge authority has been retired; the new bridge
11235 authority is "Bifroest". Closes tickets 19728 and 19690.
11237 o Major bugfixes (client, security, also in 0.2.8.7):
11238 - Only use the ReachableAddresses option to restrict the first hop
11239 in a path. In earlier versions of 0.2.8.x, it would apply to
11240 every hop in the path, with a possible degradation in anonymity
11241 for anyone using an uncommon ReachableAddress setting. Fixes bug
11242 19973; bugfix on 0.2.8.2-alpha.
11244 o Major features (user interface):
11245 - Tor now supports the ability to declare options deprecated, so
11246 that we can recommend that people stop using them. Previously,
11247 this was done in an ad-hoc way. Closes ticket 19820.
11249 o Major bugfixes (directory downloads):
11250 - Avoid resetting download status for consensuses hourly, since we
11251 already have another, smarter retry mechanism. Fixes bug 8625;
11252 bugfix on 0.2.0.9-alpha.
11254 o Minor features (config):
11255 - Warn users when descriptor and port addresses are inconsistent.
11256 Mitigates bug 13953; patch by teor.
11258 o Minor features (geoip):
11259 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11262 o Minor features (user interface):
11263 - There is a new --list-deprecated-options command-line option to
11264 list all of the deprecated options. Implemented as part of
11267 o Minor bugfixes (code style):
11268 - Fix an integer signedness conversion issue in the case conversion
11269 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
11271 o Minor bugfixes (compilation):
11272 - Build correctly on versions of libevent2 without support for
11273 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
11275 - Fix a compilation warning on GCC versions before 4.6. Our
11276 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
11277 when it is also required as an argument to the compiler pragma.
11278 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
11280 o Minor bugfixes (compilation, also in 0.2.8.7):
11281 - Remove an inappropriate "inline" in tortls.c that was causing
11282 warnings on older versions of GCC. Fixes bug 19903; bugfix
11285 o Minor bugfixes (fallback directories, also in 0.2.8.7):
11286 - Avoid logging a NULL string pointer when loading fallback
11287 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11288 and 0.2.8.1-alpha. Report and patch by "rubiate".
11290 o Minor bugfixes (logging):
11291 - Log a more accurate message when we fail to dump a microdescriptor.
11292 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
11294 o Minor bugfixes (memory leak):
11295 - Fix a series of slow memory leaks related to parsing torrc files
11296 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
11298 o Deprecated features:
11299 - A number of DNS-cache-related sub-options for client ports are now
11300 deprecated for security reasons, and may be removed in a future
11301 version of Tor. (We believe that client-side DNS caching is a bad
11302 idea for anonymity, and you should not turn it on.) The options
11303 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11304 UseIPv4Cache, and UseIPv6Cache.
11305 - A number of options are deprecated for security reasons, and may
11306 be removed in a future version of Tor. The options are:
11307 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11308 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11309 CloseHSClientCircuitsImmediatelyOnTimeout,
11310 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11311 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11312 UseNTorHandshake, and WarnUnsafeSocks.
11313 - The *ListenAddress options are now deprecated as unnecessary: the
11314 corresponding *Port options should be used instead. These options
11315 may someday be removed. The affected options are:
11316 ControlListenAddress, DNSListenAddress, DirListenAddress,
11317 NATDListenAddress, ORListenAddress, SocksListenAddress,
11318 and TransListenAddress.
11321 - Correct the IPv6 syntax in our documentation for the
11322 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
11325 - We no longer include the (dead, deprecated) bufferevent code in
11326 Tor. Closes ticket 19450. Based on a patch from U+039b.
11329 Changes in version 0.2.8.7 - 2016-08-24
11330 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
11331 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
11332 who sets the ReachableAddresses option, and all bridges, are strongly
11333 encouraged to upgrade.
11335 o Directory authority changes:
11336 - The "Tonga" bridge authority has been retired; the new bridge
11337 authority is "Bifroest". Closes tickets 19728 and 19690.
11339 o Major bugfixes (client, security):
11340 - Only use the ReachableAddresses option to restrict the first hop
11341 in a path. In earlier versions of 0.2.8.x, it would apply to
11342 every hop in the path, with a possible degradation in anonymity
11343 for anyone using an uncommon ReachableAddress setting. Fixes bug
11344 19973; bugfix on 0.2.8.2-alpha.
11346 o Minor features (geoip):
11347 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11350 o Minor bugfixes (compilation):
11351 - Remove an inappropriate "inline" in tortls.c that was causing
11352 warnings on older versions of GCC. Fixes bug 19903; bugfix
11355 o Minor bugfixes (fallback directories):
11356 - Avoid logging a NULL string pointer when loading fallback
11357 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11358 and 0.2.8.1-alpha. Report and patch by "rubiate".
11361 Changes in version 0.2.9.1-alpha - 2016-08-08
11362 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
11363 series. It improves our support for hardened builds and compiler
11364 warnings, deploys some critical infrastructure for improvements to
11365 hidden services, includes a new timing backend that we hope to use for
11366 better support for traffic padding, makes it easier for programmers to
11367 log unexpected events, and contains other small improvements to
11368 security, correctness, and performance.
11370 Below are the changes since 0.2.8.6.
11372 o New system requirements:
11373 - Tor now requires Libevent version 2.0.10-stable or later. Older
11374 versions of Libevent have less efficient backends for several
11375 platforms, and lack the DNS code that we use for our server-side
11376 DNS support. This implements ticket 19554.
11377 - Tor now requires zlib version 1.2 or later, for security,
11378 efficiency, and (eventually) gzip support. (Back when we started,
11379 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11380 released in 2003. We recommend the latest version.)
11382 o Major features (build, hardening):
11383 - Tor now builds with -ftrapv by default on compilers that support
11384 it. This option detects signed integer overflow (which C forbids),
11385 and turns it into a hard-failure. We do not apply this option to
11386 code that needs to run in constant time to avoid side-channels;
11387 instead, we use -fwrapv in that code. Closes ticket 17983.
11388 - When --enable-expensive-hardening is selected, stop applying the
11389 clang/gcc sanitizers to code that needs to run in constant time.
11390 Although we are aware of no introduced side-channels, we are not
11391 able to prove that there are none. Related to ticket 17983.
11393 o Major features (compilation):
11394 - Our big list of extra GCC warnings is now enabled by default when
11395 building with GCC (or with anything like Clang that claims to be
11396 GCC-compatible). To make all warnings into fatal compilation
11397 errors, pass --enable-fatal-warnings to configure. Closes
11399 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11400 turn on C and POSIX extensions. (Previously, we attempted to do
11401 this on an ad hoc basis.) Closes ticket 19139.
11403 o Major features (directory authorities, hidden services):
11404 - Directory authorities can now perform the shared randomness
11405 protocol specified by proposal 250. Using this protocol, directory
11406 authorities generate a global fresh random value every day. In the
11407 future, this value will be used by hidden services to select
11408 HSDirs. This release implements the directory authority feature;
11409 the hidden service side will be implemented in the future as part
11410 of proposal 224. Resolves ticket 16943; implements proposal 250.
11412 o Major features (downloading, random exponential backoff):
11413 - When we fail to download an object from a directory service, wait
11414 for an (exponentially increasing) randomized amount of time before
11415 retrying, rather than a fixed interval as we did before. This
11416 prevents a group of Tor instances from becoming too synchronized,
11417 or a single Tor instance from becoming too predictable, in its
11418 download schedule. Closes ticket 15942.
11420 o Major bugfixes (exit policies):
11421 - Avoid disclosing exit outbound bind addresses, configured port
11422 bind addresses, and local interface addresses in relay descriptors
11423 by default under ExitPolicyRejectPrivate. Instead, only reject
11424 these (otherwise unlisted) addresses if
11425 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11426 0.2.7.2-alpha. Patch by teor.
11428 o Major bugfixes (hidden service client):
11429 - Allow Tor clients with appropriate controllers to work with
11430 FetchHidServDescriptors set to 0. Previously, this option also
11431 disabled descriptor cache lookup, thus breaking hidden services
11432 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11434 o Minor features (build, hardening):
11435 - Detect and work around a libclang_rt problem that would prevent
11436 clang from finding __mulodi4() on some 32-bit platforms, and thus
11437 keep -ftrapv from linking on those systems. Closes ticket 19079.
11438 - When building on a system without runtime support for the runtime
11439 hardening options, try to log a useful warning at configuration
11440 time, rather than an incomprehensible warning at link time. If
11441 expensive hardening was requested, this warning becomes an error.
11442 Closes ticket 18895.
11444 o Minor features (code safety):
11445 - In our integer-parsing functions, ensure that maxiumum value we
11446 give is no smaller than the minimum value. Closes ticket 19063;
11449 o Minor features (controller):
11450 - Implement new GETINFO queries for all downloads that use
11451 download_status_t to schedule retries. This allows controllers to
11452 examine the schedule for pending downloads. Closes ticket 19323.
11453 - Allow controllers to configure basic client authorization on
11454 hidden services when they create them with the ADD_ONION control
11455 command. Implements ticket 15588. Patch by "special".
11456 - Fire a STATUS_SERVER controller event whenever the hibernation
11457 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11459 o Minor features (directory authority):
11460 - Directory authorities now only give the Guard flag to a relay if
11461 they are also giving it the Stable flag. This change allows us to
11462 simplify path selection for clients. It should have minimal effect
11463 in practice, since >99% of Guards already have the Stable flag.
11464 Implements ticket 18624.
11465 - Directory authorities now write their v3-status-votes file out to
11466 disk earlier in the consensus process, so we have a record of the
11467 votes even if we abort the consensus process. Resolves
11470 o Minor features (hidden service):
11471 - Stop being so strict about the payload length of "rendezvous1"
11472 cells. We used to be locked in to the "TAP" handshake length, and
11473 now we can handle better handshakes like "ntor". Resolves
11476 o Minor features (infrastructure, time):
11477 - Tor now uses the operating system's monotonic timers (where
11478 available) for internal fine-grained timing. Previously we would
11479 look at the system clock, and then attempt to compensate for the
11480 clock running backwards. Closes ticket 18908.
11481 - Tor now includes an improved timer backend, so that we can
11482 efficiently support tens or hundreds of thousands of concurrent
11483 timers, as will be needed for some of our planned anti-traffic-
11484 analysis work. This code is based on William Ahern's "timeout.c"
11485 project, which implements a "tickless hierarchical timing wheel".
11486 Closes ticket 18365.
11488 o Minor features (logging):
11489 - Provide a more useful warning message when configured with an
11490 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11491 - When dumping unparseable router descriptors, optionally store them
11492 in separate files, named by digest, up to a configurable size
11493 limit. You can change the size limit by setting the
11494 MaxUnparseableDescSizeToLog option, and disable this feature by
11495 setting that option to 0. Closes ticket 18322.
11496 - Add a set of macros to check nonfatal assertions, for internal
11497 use. Migrating more of our checks to these should help us avoid
11498 needless crash bugs. Closes ticket 18613.
11500 o Minor features (performance):
11501 - Changer the "optimistic data" extension from "off by default" to
11502 "on by default". The default was ordinarily overridden by a
11503 consensus option, but when clients were bootstrapping for the
11504 first time, they would not have a consensus to get the option
11505 from. Changing this default When fetching a consensus for the
11506 first time, use optimistic data. This saves a round-trip during
11507 startup. Closes ticket 18815.
11509 o Minor features (relay, usability):
11510 - When the directory authorities refuse a bad relay's descriptor,
11511 encourage the relay operator to contact us. Many relay operators
11512 won't notice this line in their logs, but it's a win if even a few
11513 learn why we don't like what their relay was doing. Resolves
11516 o Minor features (testing):
11517 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11518 part of bug 18934; bugfix on 0.2.5.2-alpha.
11519 - Move the test-network.sh script to chutney, and modify tor's test-
11520 network.sh to call the (newer) chutney version when available.
11521 Resolves ticket 19116. Patch by teor.
11522 - Use the lcov convention for marking lines as unreachable, so that
11523 we don't count them when we're generating test coverage data.
11524 Update our coverage tools to understand this convention. Closes
11527 o Minor bugfixes (bootstrap):
11528 - Remember the directory we fetched the consensus or previous
11529 certificates from, and use it to fetch future authority
11530 certificates. This change improves bootstrapping performance.
11531 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11533 o Minor bugfixes (build):
11534 - The test-stem and test-network makefile targets now depend only on
11535 the tor binary that they are testing. Previously, they depended on
11536 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11537 patch from "cypherpunks".
11539 o Minor bugfixes (circuits):
11540 - Make sure extend_info_from_router() is only called on servers.
11541 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11543 o Minor bugfixes (compilation):
11544 - When building with Clang, use a full set of GCC warnings.
11545 (Previously, we included only a subset, because of the way we
11546 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11548 o Minor bugfixes (directory authority):
11549 - Authorities now sort the "package" lines in their votes, for ease
11550 of debugging. (They are already sorted in consensus documents.)
11551 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11552 - When parsing a detached signature, make sure we use the length of
11553 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11554 order to avoid comparing bytes out-of-bounds with a smaller digest
11555 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11557 o Minor bugfixes (documentation):
11558 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11559 19504; bugfix on 0.2.7.3-rc.
11560 - Fix the description of the --passphrase-fd option in the
11561 tor-gencert manpage. The option is used to pass the number of a
11562 file descriptor to read the passphrase from, not to read the file
11563 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11565 o Minor bugfixes (ephemeral hidden service):
11566 - When deleting an ephemeral hidden service, close its intro points
11567 even if they are not completely open. Fixes bug 18604; bugfix
11570 o Minor bugfixes (guard selection):
11571 - Use a single entry guard even if the NumEntryGuards consensus
11572 parameter is not provided. Fixes bug 17688; bugfix
11574 - Don't mark guards as unreachable if connection_connect() fails.
11575 That function fails for local reasons, so it shouldn't reveal
11576 anything about the status of the guard. Fixes bug 14334; bugfix
11579 o Minor bugfixes (hidden service client):
11580 - Increase the minimum number of internal circuits we preemptively
11581 build from 2 to 3, so a circuit is available when a client
11582 connects to another onion service. Fixes bug 13239; bugfix
11585 o Minor bugfixes (logging):
11586 - When logging a directory ownership mismatch, log the owning
11587 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11589 o Minor bugfixes (memory leaks):
11590 - Fix a small, uncommon memory leak that could occur when reading a
11591 truncated ed25519 key file. Fixes bug 18956; bugfix
11594 o Minor bugfixes (testing):
11595 - Allow clients to retry HSDirs much faster in test networks. Fixes
11596 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11597 - Disable ASAN's detection of segmentation faults while running
11598 test_bt.sh, so that we can make sure that our own backtrace
11599 generation code works. Fixes another aspect of bug 18934; bugfix
11600 on 0.2.5.2-alpha. Patch from "cypherpunks".
11601 - Fix the test-network-all target on out-of-tree builds by using the
11602 correct path to the test driver script. Fixes bug 19421; bugfix
11605 o Minor bugfixes (time):
11606 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11607 bugfix on all released tor versions.
11608 - When computing the difference between two times in milliseconds,
11609 we now round to the nearest millisecond correctly. Previously, we
11610 could sometimes round in the wrong direction. Fixes bug 19428;
11611 bugfix on 0.2.2.2-alpha.
11613 o Minor bugfixes (user interface):
11614 - Display a more accurate number of suppressed messages in the log
11615 rate-limiter. Previously, there was a potential integer overflow
11616 in the counter. Now, if the number of messages hits a maximum, the
11617 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11619 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11620 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11622 o Code simplification and refactoring:
11623 - Remove redundant declarations of the MIN macro. Closes
11625 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11626 Closes ticket 18462; patch from "icanhasaccount".
11627 - Split the 600-line directory_handle_command_get function into
11628 separate functions for different URL types. Closes ticket 16698.
11631 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
11632 ticket 19153. Patch from "U+039b".
11634 o Removed features:
11635 - Remove support for "GET /tor/bytes.txt" DirPort request, and
11636 "GETINFO dir-usage" controller request, which were only available
11637 via a compile-time option in Tor anyway. Feature was added in
11638 0.2.2.1-alpha. Resolves ticket 19035.
11639 - There is no longer a compile-time option to disable support for
11640 TransPort. (If you don't want TransPort; just don't use it.) Patch
11641 from "U+039b". Closes ticket 19449.
11644 - Run more workqueue tests as part of "make check". These had
11645 previously been implemented, but you needed to know special
11646 command-line options to enable them.
11647 - We now have unit tests for our code to reject zlib "compression
11648 bombs". (Fortunately, the code works fine.)
11651 Changes in version 0.2.8.6 - 2016-08-02
11653 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
11655 The Tor 0.2.8 series improves client bootstrapping performance,
11656 completes the authority-side implementation of improved identity
11657 keys for relays, and includes numerous bugfixes and performance
11658 improvements throughout the program. This release continues to
11659 improve the coverage of Tor's test suite. For a full list of
11660 changes since Tor 0.2.7, see the ReleaseNotes file.
11662 Changes since 0.2.8.5-rc:
11664 o Minor features (geoip):
11665 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
11668 o Minor bugfixes (compilation):
11669 - Fix a compilation warning in the unit tests on systems where char
11670 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
11672 o Minor bugfixes (fallback directories):
11673 - Remove 1 fallback that was on the hardcoded list, then opted-out,
11674 leaving 89 of the 100 fallbacks originally introduced in Tor
11675 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
11677 o Minor bugfixes (Linux seccomp2 sandbox):
11678 - Allow more syscalls when running with "Sandbox 1" enabled:
11679 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
11680 some systems, these are required for Tor to start. Fixes bug
11681 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
11682 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
11683 so that get_interface_address6_via_udp_socket_hack() can work.
11684 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
11687 Changes in version 0.2.8.5-rc - 2016-07-07
11688 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
11689 series. If we find no new bugs or regressions here, the first stable
11690 0.2.8 release will be identical to it. It has a few small bugfixes
11691 against previous versions.
11693 o Directory authority changes:
11694 - Urras is no longer a directory authority. Closes ticket 19271.
11696 o Major bugfixes (heartbeat):
11697 - Fix a regression that would crash Tor when the periodic
11698 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
11699 0.2.8.1-alpha. Reported by "kubaku".
11701 o Minor features (build):
11702 - Tor now again builds with the recent OpenSSL 1.1 development
11703 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
11704 - When building manual pages, set the timezone to "UTC", so that the
11705 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
11706 Patch from intrigeri.
11708 o Minor bugfixes (fallback directory selection):
11709 - Avoid errors during fallback selection if there are no eligible
11710 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
11713 o Minor bugfixes (IPv6, microdescriptors):
11714 - Don't check node addresses when we only have a routerstatus. This
11715 allows IPv6-only clients to bootstrap by fetching microdescriptors
11716 from fallback directory mirrors. (The microdescriptor consensus
11717 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
11720 o Minor bugfixes (logging):
11721 - Reduce pointlessly verbose log messages when directory servers
11722 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
11723 0.2.8.1-alpha. Patch by teor.
11724 - When a fallback directory changes its fingerprint from the hard-
11725 coded fingerprint, log a less severe, more explanatory log
11726 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
11728 o Minor bugfixes (Linux seccomp2 sandboxing):
11729 - Allow statistics to be written to disk when "Sandbox 1" is
11730 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
11731 0.2.6.1-alpha respectively.
11733 o Minor bugfixes (user interface):
11734 - Remove a warning message "Service [scrubbed] not found after
11735 descriptor upload". This message appears when one uses HSPOST
11736 control command to upload a service descriptor. Since there is
11737 only a descriptor and no service, showing this message is
11738 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
11740 o Fallback directory list:
11741 - Add a comment to the generated fallback directory list that
11742 explains how to comment out unsuitable fallbacks in a way that's
11743 compatible with the stem fallback parser.
11744 - Update fallback whitelist and blacklist based on relay operator
11745 emails. Blacklist unsuitable (non-working, over-volatile)
11746 fallbacks. Resolves ticket 19071. Patch by teor.
11747 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
11748 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
11749 ticket 19071; patch by teor.
11752 Changes in version 0.2.8.4-rc - 2016-06-15
11753 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
11754 If we find no new bugs or regressions here, the first stable 0.2.8
11755 release will be identical to it. It has a few small bugfixes against
11758 o Major bugfixes (user interface):
11759 - Correctly give a warning in the cases where a relay is specified
11760 by nickname, and one such relay is found, but it is not officially
11761 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
11763 o Minor features (build):
11764 - Tor now builds once again with the recent OpenSSL 1.1 development
11765 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
11767 o Minor features (geoip):
11768 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
11771 o Minor bugfixes (compilation):
11772 - Cause the unit tests to compile correctly on mingw64 versions that
11773 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
11775 o Minor bugfixes (downloading):
11776 - Predict more correctly whether we'll be downloading over HTTP when
11777 we determine the maximum length of a URL. This should avoid a
11778 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
11782 Changes in version 0.2.8.3-alpha - 2016-05-26
11783 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
11784 the course of the 0.2.8 development cycle. It improves the behavior of
11785 directory clients, fixes several crash bugs, fixes a gap in compiler
11786 hardening, and allows the full integration test suite to run on
11789 o Major bugfixes (security, client, DNS proxy):
11790 - Stop a crash that could occur when a client running with DNSPort
11791 received a query with multiple address types, and the first
11792 address type was not supported. Found and fixed by Scott Dial.
11793 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
11795 o Major bugfixes (security, compilation):
11796 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
11797 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
11798 cause a compiler warning, thereby making other checks fail, and
11799 needlessly disabling compiler-hardening support. Fixes one case of
11800 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
11802 o Major bugfixes (security, directory authorities):
11803 - Fix a crash and out-of-bounds write during authority voting, when
11804 the list of relays includes duplicate ed25519 identity keys. Fixes
11805 bug 19032; bugfix on 0.2.8.2-alpha.
11807 o Major bugfixes (client, bootstrapping):
11808 - Check if bootstrap consensus downloads are still needed when the
11809 linked connection attaches. This prevents tor making unnecessary
11810 begindir-style connections, which are the only directory
11811 connections tor clients make since the fix for 18483 was merged.
11812 - Fix some edge cases where consensus download connections may not
11813 have been closed, even though they were not needed. Related to fix
11815 - Make relays retry consensus downloads the correct number of times,
11816 rather than the more aggressive client retry count. Fixes part of
11818 - Stop downloading consensuses when we have a consensus, even if we
11819 don't have all the certificates for it yet. Fixes bug 18809;
11820 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
11822 o Major bugfixes (directory mirrors):
11823 - Decide whether to advertise begindir support in the the same way
11824 we decide whether to advertise our DirPort. Allowing these
11825 decisions to become out-of-sync led to surprising behavior like
11826 advertising begindir support when hibernation made us not
11827 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
11830 o Major bugfixes (IPv6 bridges, client):
11831 - Actually use IPv6 addresses when selecting directory addresses for
11832 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
11835 o Major bugfixes (key management):
11836 - If OpenSSL fails to generate an RSA key, do not retain a dangling
11837 pointer to the previous (uninitialized) key value. The impact here
11838 should be limited to a difficult-to-trigger crash, if OpenSSL is
11839 running an engine that makes key generation failures possible, or
11840 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
11841 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
11844 o Major bugfixes (testing):
11845 - Fix a bug that would block 'make test-network-all' on systems where
11846 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
11847 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
11848 bugfix on 0.2.8.1-alpha.
11850 o Minor features (clients):
11851 - Make clients, onion services, and bridge relays always use an
11852 encrypted begindir connection for directory requests. Resolves
11853 ticket 18483. Patch by "teor".
11855 o Minor features (fallback directory mirrors):
11856 - Give each fallback the same weight for client selection; restrict
11857 fallbacks to one per operator; report fallback directory detail
11858 changes when rebuilding list; add new fallback directory mirrors
11859 to the whitelist; and many other minor simplifications and fixes.
11860 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
11861 0.2.8.1-alpha; patch by "teor".
11862 - Replace the 21 fallbacks generated in January 2016 and included in
11863 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
11864 2016. Closes task 17158; patch by "teor".
11866 o Minor features (geoip):
11867 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
11870 o Minor bugfixes (assert, portability):
11871 - Fix an assertion failure in memarea.c on systems where "long" is
11872 shorter than the size of a pointer. Fixes bug 18716; bugfix
11875 o Minor bugfixes (bootstrap):
11876 - Consistently use the consensus download schedule for authority
11877 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
11879 o Minor bugfixes (build):
11880 - Remove a pair of redundant AM_CONDITIONAL declarations from
11881 configure.ac. Fixes one final case of bug 17744; bugfix
11883 - Resolve warnings when building on systems that are concerned with
11884 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
11886 - When libscrypt.h is found, but no libscrypt library can be linked,
11887 treat libscrypt as absent. Fixes bug 19161; bugfix
11890 o Minor bugfixes (client):
11891 - Turn all TestingClientBootstrap* into non-testing torrc options.
11892 This changes simply renames them by removing "Testing" in front of
11893 them and they do not require TestingTorNetwork to be enabled
11894 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
11895 - Make directory node selection more reliable, mainly for IPv6-only
11896 clients and clients with few reachable addresses. Fixes bug 18929;
11897 bugfix on 0.2.8.1-alpha. Patch by "teor".
11899 o Minor bugfixes (controller, microdescriptors):
11900 - Make GETINFO dir/status-vote/current/consensus conform to the
11901 control specification by returning "551 Could not open cached
11902 consensus..." when not caching consensuses. Fixes bug 18920;
11903 bugfix on 0.2.2.6-alpha.
11905 o Minor bugfixes (crypto, portability):
11906 - The SHA3 and SHAKE routines now produce the correct output on Big
11907 Endian systems. No code calls either algorithm yet, so this is
11908 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
11909 - Tor now builds again with the recent OpenSSL 1.1 development
11910 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
11913 o Minor bugfixes (directories):
11914 - When fetching extrainfo documents, compare their SHA256 digests
11915 and Ed25519 signing key certificates with the routerinfo that led
11916 us to fetch them, rather than with the most recent routerinfo.
11917 Otherwise we generate many spurious warnings about mismatches.
11918 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
11920 o Minor bugfixes (logging):
11921 - When we can't generate a signing key because OfflineMasterKey is
11922 set, do not imply that we should have been able to load it. Fixes
11923 bug 18133; bugfix on 0.2.7.2-alpha.
11924 - Stop periodic_event_dispatch() from blasting twelve lines per
11925 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
11926 - When rejecting a misformed INTRODUCE2 cell, only log at
11927 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
11929 o Minor bugfixes (pluggable transports):
11930 - Avoid reporting a spurious error when we decide that we don't need
11931 to terminate a pluggable transport because it has already exited.
11932 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
11934 o Minor bugfixes (pointer arithmetic):
11935 - Fix a bug in memarea_alloc() that could have resulted in remote
11936 heap write access, if Tor had ever passed an unchecked size to
11937 memarea_alloc(). Fortunately, all the sizes we pass to
11938 memarea_alloc() are pre-checked to be less than 128 kilobytes.
11939 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
11942 o Minor bugfixes (relays):
11943 - Consider more config options when relays decide whether to
11944 regenerate their descriptor. Fixes more of bug 12538; bugfix
11946 - Resolve some edge cases where we might launch an ORPort
11947 reachability check even when DisableNetwork is set. Noticed while
11948 fixing bug 18616; bugfix on 0.2.3.9-alpha.
11950 o Minor bugfixes (statistics):
11951 - We now include consensus downloads via IPv6 in our directory-
11952 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
11954 o Minor bugfixes (testing):
11955 - Allow directories in small networks to bootstrap by skipping
11956 DirPort checks when the consensus has no exits. Fixes bug 19003;
11957 bugfix on 0.2.8.1-alpha. Patch by teor.
11958 - Fix a small memory leak that would occur when the
11959 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
11960 bugfix on 0.2.5.2-alpha.
11962 o Minor bugfixes (time handling):
11963 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
11964 field. Otherwise, our unit tests crash on Windows. Fixes bug
11965 18977; bugfix on 0.2.2.25-alpha.
11968 - Document the contents of the 'datadir/keys' subdirectory in the
11969 manual page. Closes ticket 17621.
11970 - Stop recommending use of nicknames to identify relays in our
11971 MapAddress documentation. Closes ticket 18312.
11974 Changes in version 0.2.8.2-alpha - 2016-03-28
11975 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
11976 bugs in earlier versions of Tor, including some that prevented
11977 authorities using Tor 0.2.7.x from running correctly. IPv6 and
11978 directory support should also be much improved.
11980 o New system requirements:
11981 - Tor no longer supports versions of OpenSSL with a broken
11982 implementation of counter mode. (This bug was present in OpenSSL
11983 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
11984 longer runs with, these versions.
11985 - Tor no longer attempts to support platforms where the "time_t"
11986 type is unsigned. (To the best of our knowledge, only OpenVMS does
11987 this, and Tor has never actually built on OpenVMS.) Closes
11989 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
11990 later (released in 2008 and 2009 respectively). If you are
11991 building Tor from the git repository instead of from the source
11992 distribution, and your tools are older than this, you will need to
11993 upgrade. Closes ticket 17732.
11995 o Major bugfixes (security, pointers):
11996 - Avoid a difficult-to-trigger heap corruption attack when extending
11997 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
11998 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
11999 Reported by Guido Vranken.
12001 o Major bugfixes (bridges, pluggable transports):
12002 - Modify the check for OR connections to private addresses. Allow
12003 bridges on private addresses, including pluggable transports that
12004 ignore the (potentially private) address in the bridge line. Fixes
12005 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
12007 o Major bugfixes (compilation):
12008 - Repair hardened builds under the clang compiler. Previously, our
12009 use of _FORTIFY_SOURCE would conflict with clang's address
12010 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12012 o Major bugfixes (crash on shutdown):
12013 - Correctly handle detaching circuits from muxes when shutting down.
12014 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
12015 - Fix an assert-on-exit bug related to counting memory usage in
12016 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
12018 o Major bugfixes (crash on startup):
12019 - Fix a segfault during startup: If a Unix domain socket was
12020 configured as listener (such as a ControlSocket or a SocksPort
12021 "unix:" socket), and tor was started as root but not configured to
12022 switch to another user, tor would segfault while trying to string
12023 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
12026 o Major bugfixes (dns proxy mode, crash):
12027 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12028 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12030 o Major bugfixes (relays, bridge clients):
12031 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
12032 bridge clients use the address configured in the bridge line.
12033 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
12036 o Major bugfixes (voting):
12037 - Actually enable support for authorities to match routers by their
12038 Ed25519 identities. Previously, the code had been written, but
12039 some debugging code that had accidentally been left in the
12040 codebase made it stay turned off. Fixes bug 17702; bugfix
12042 - When collating votes by Ed25519 identities, authorities now
12043 include a "NoEdConsensus" flag if the ed25519 value (or lack
12044 thereof) for a server does not reflect the majority consensus.
12045 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12046 - When generating a vote with keypinning disabled, never include two
12047 entries for the same ed25519 identity. This bug was causing
12048 authorities to generate votes that they could not parse when a
12049 router violated key pinning by changing its RSA identity but
12050 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12051 18318. Bugfix on 0.2.7.2-alpha.
12053 o Minor features (security, win32):
12054 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
12055 attack. Fixes bug 18123; bugfix on all tor versions. Patch
12058 o Minor features (bug-resistance):
12059 - Make Tor survive errors involving connections without a
12060 corresponding event object. Previously we'd fail with an
12061 assertion; now we produce a log message. Related to bug 16248.
12063 o Minor features (build):
12064 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12065 as having possible IPFW support. Closes ticket 18448. Patch from
12066 Steven Chamberlain.
12068 o Minor features (code hardening):
12069 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12070 level code, to harden against accidental failures to NUL-
12071 terminate. Part of ticket 17852. Patch from jsturgix. Found
12074 o Minor features (crypto):
12075 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12076 p is a safe prime, and g is a suitable generator. Closes
12079 o Minor features (geoip):
12080 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
12083 o Minor features (hidden service directory):
12084 - Streamline relay-side hsdir handling: when relays consider whether
12085 to accept an uploaded hidden service descriptor, they no longer
12086 check whether they are one of the relays in the network that is
12087 "supposed" to handle that descriptor. Implements ticket 18332.
12089 o Minor features (IPv6):
12090 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12091 to 1, tor prefers IPv6 directory addresses.
12092 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12093 avoids using IPv4 for client OR and directory connections.
12094 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12095 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12096 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12098 o Minor features (linux seccomp2 sandbox):
12099 - Reject attempts to change our Address with "Sandbox 1" enabled.
12100 Changing Address with Sandbox turned on would never actually work,
12101 but previously it would fail in strange and confusing ways. Found
12102 while fixing 18548.
12104 o Minor features (robustness):
12105 - Exit immediately with an error message if the code attempts to use
12106 Libevent without having initialized it. This should resolve some
12107 frequently-made mistakes in our unit tests. Closes ticket 18241.
12109 o Minor features (unix domain sockets):
12110 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
12111 Unix domain sockets without checking the permissions on the parent
12112 directory. (Tor checks permissions by default because some
12113 operating systems only check permissions on the parent directory.
12114 However, some operating systems do look at permissions on the
12115 socket, and tor's default check is unneeded.) Closes ticket 18458.
12118 o Minor bugfixes (exit policies, security):
12119 - Refresh an exit relay's exit policy when interface addresses
12120 change. Previously, tor only refreshed the exit policy when the
12121 configured external address changed. Fixes bug 18208; bugfix on
12122 0.2.7.3-rc. Patch by teor.
12124 o Minor bugfixes (security, hidden services):
12125 - Prevent hidden services connecting to client-supplied rendezvous
12126 addresses that are reserved as internal or multicast. Fixes bug
12127 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
12129 o Minor bugfixes (build):
12130 - Do not link the unit tests against both the testing and non-
12131 testing versions of the static libraries. Fixes bug 18490; bugfix
12133 - Avoid spurious failures from configure files related to calling
12134 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
12135 0.2.0.1-alpha. Patch from "cypherpunks".
12136 - Silence spurious clang-scan warnings in the ed25519_donna code by
12137 explicitly initializing some objects. Fixes bug 18384; bugfix on
12138 0.2.7.2-alpha. Patch by teor.
12140 o Minor bugfixes (client, bootstrap):
12141 - Count receipt of new microdescriptors as progress towards
12142 bootstrapping. Previously, with EntryNodes set, Tor might not
12143 successfully repopulate the guard set on bootstrapping. Fixes bug
12144 16825; bugfix on 0.2.3.1-alpha.
12146 o Minor bugfixes (code correctness):
12147 - Update to the latest version of Trunnel, which tries harder to
12148 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
12149 by clang address sanitizer. Fixes bug 18373; bugfix
12152 o Minor bugfixes (configuration):
12153 - Fix a tiny memory leak when parsing a port configuration ending in
12154 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
12156 o Minor bugfixes (containers):
12157 - If we somehow attempt to construct a heap with more than
12158 1073741822 elements, avoid an integer overflow when maintaining
12159 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
12161 o Minor bugfixes (correctness):
12162 - Fix a bad memory handling bug that would occur if we had queued a
12163 cell on a channel's incoming queue. Fortunately, we can't actually
12164 queue a cell like that as our code is constructed today, but it's
12165 best to avoid this kind of error, even if there isn't any code
12166 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
12168 o Minor bugfixes (directory):
12169 - When generating a URL for a directory server on an IPv6 address,
12170 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
12171 on 0.2.3.9-alpha. Patch from Malek.
12173 o Minor bugfixes (fallback directory mirrors):
12174 - When requesting extrainfo descriptors from a trusted directory
12175 server, check whether it is an authority or a fallback directory
12176 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
12177 0.2.4.7-alpha. Reported by atagar, patch by teor.
12179 o Minor bugfixes (hidden service, client):
12180 - Handle the case where the user makes several fast consecutive
12181 requests to the same .onion address. Previously, the first six
12182 requests would each trigger a descriptor fetch, each picking a
12183 directory (there are 6 overall) and the seventh one would fail
12184 because no directories were left, thereby triggering a close on
12185 all current directory connections asking for the hidden service.
12186 The solution here is to not close the connections if we have
12187 pending directory fetches. Fixes bug 15937; bugfix
12190 o Minor bugfixes (hidden service, control port):
12191 - Add the onion address to the HS_DESC event for the UPLOADED action
12192 both on success or failure. It was previously hardcoded with
12193 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
12195 o Minor bugfixes (hidden service, directory):
12196 - Bridges now refuse "rendezvous2" (hidden service descriptor)
12197 publish attempts. Suggested by ticket 18332.
12199 o Minor bugfixes (linux seccomp2 sandbox):
12200 - Allow the setrlimit syscall, and the prlimit and prlimit64
12201 syscalls, which some libc implementations use under the hood.
12202 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
12203 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
12204 enabled and no DNS resolvers configured. This should help TAILS
12205 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
12206 - Fix the sandbox's interoperability with unix domain sockets under
12207 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
12209 o Minor bugfixes (logging):
12210 - When logging information about an unparsable networkstatus vote or
12211 consensus, do not say "vote" when we mean consensus. Fixes bug
12212 18368; bugfix on 0.2.0.8-alpha.
12213 - Scrub service name in "unrecognized service ID" log messages.
12214 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
12215 - Downgrade logs and backtraces about IP versions to info-level.
12216 Only log backtraces once each time tor runs. Assists in diagnosing
12217 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
12218 Christian, patch by teor.
12220 o Minor bugfixes (memory safety):
12221 - Avoid freeing an uninitialized pointer when opening a socket fails
12222 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
12223 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
12225 - Correctly duplicate addresses in get_interface_address6_list().
12226 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
12227 patch by "cypherpunks".
12228 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
12230 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
12231 18672; bugfix on 0.2.5.1-alpha.
12233 o Minor bugfixes (private directory):
12234 - Prevent a race condition when creating private directories. Fixes
12235 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
12236 Patch from jsturgix. Found with Flawfinder.
12238 o Minor bugfixes (test networks, IPv6):
12239 - Allow internal IPv6 addresses in descriptors in test networks.
12240 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
12243 o Minor bugfixes (testing):
12244 - We no longer disable assertions in the unit tests when coverage is
12245 enabled. Instead, we require you to say --disable-asserts-in-tests
12246 to the configure script if you need assertions disabled in the
12247 unit tests (for example, if you want to perform branch coverage).
12248 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
12250 o Minor bugfixes (time parsing):
12251 - Avoid overflow in tor_timegm when parsing dates in and after 2038
12252 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
12253 0.0.2pre14. Patch by teor.
12255 o Minor bugfixes (tor-gencert):
12256 - Correctly handle the case where an authority operator enters a
12257 passphrase but sends an EOF before sending a newline. Fixes bug
12258 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
12260 o Code simplification and refactoring:
12261 - Quote all the string interpolations in configure.ac -- even those
12262 which we are pretty sure can't contain spaces. Closes ticket
12263 17744. Patch from zerosion.
12264 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
12265 inplace, so there's no need to have a separate implementation for
12266 the non-inplace code. Closes ticket 18258. Patch from Malek.
12267 - Simplify return types for some crypto functions that can't
12268 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
12271 - Change build messages to refer to "Fedora" instead of "Fedora
12272 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
12273 Patches from "icanhasaccount" and "cypherpunks".
12275 o Removed features:
12276 - We no longer maintain an internal freelist in memarea.c.
12277 Allocators should be good enough to make this code unnecessary,
12278 and it's doubtful that it ever had any performance benefit.
12281 - Fix several warnings from clang's address sanitizer produced in
12283 - Treat backtrace test failures as expected on FreeBSD until we
12284 solve bug 17808. Closes ticket 18204.
12287 Changes in version 0.2.8.1-alpha - 2016-02-04
12288 Tor 0.2.8.1-alpha is the first alpha release in its series. It
12289 includes numerous small features and bugfixes against previous Tor
12290 versions, and numerous small infrastructure improvements. The most
12291 notable features are a set of improvements to the directory subsystem.
12293 o Major features (security, Linux):
12294 - When Tor starts as root on Linux and is told to switch user ID, it
12295 can now retain the capability to bind to low ports. By default,
12296 Tor will do this only when it's switching user ID and some low
12297 ports have been configured. You can change this behavior with the
12298 new option KeepBindCapabilities. Closes ticket 8195.
12300 o Major features (directory system):
12301 - When bootstrapping multiple consensus downloads at a time, use the
12302 first one that starts downloading, and close the rest. This
12303 reduces failures when authorities or fallback directories are slow
12304 or down. Together with the code for feature 15775, this feature
12305 should reduces failures due to fallback churn. Implements ticket
12306 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
12307 "mikeperry" and "teor".
12308 - Include a trial list of 21 default fallback directories, generated
12309 in January 2016, based on an opt-in survey of suitable relays.
12310 Doing this should make clients bootstrap more quickly and reliably,
12311 and reduce the load on the directory authorities. Closes ticket
12312 15775. Patch by "teor".
12313 Candidates identified using an OnionOO script by "weasel", "teor",
12314 "gsathya", and "karsten".
12315 - Previously only relays that explicitly opened a directory port
12316 (DirPort) accepted directory requests from clients. Now all
12317 relays, with and without a DirPort, accept and serve tunneled
12318 directory requests that they receive through their ORPort. You can
12319 disable this behavior using the new DirCache option. Closes
12322 o Major key updates:
12323 - Update the V3 identity key for the dannenberg directory authority:
12324 it was changed on 18 November 2015. Closes task 17906. Patch
12327 o Minor features (security, clock):
12328 - Warn when the system clock appears to move back in time (when the
12329 state file was last written in the future). Tor doesn't know that
12330 consensuses have expired if the clock is in the past. Patch by
12331 "teor". Implements ticket 17188.
12333 o Minor features (security, exit policies):
12334 - ExitPolicyRejectPrivate now rejects more private addresses by
12335 default. Specifically, it now rejects the relay's outbound bind
12336 addresses (if configured), and the relay's configured port
12337 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12338 0.2.0.11-alpha. Patch by "teor".
12340 o Minor features (security, memory erasure):
12341 - Set the unused entries in a smartlist to NULL. This helped catch
12342 a (harmless) bug, and shouldn't affect performance too much.
12343 Implements ticket 17026.
12344 - Use SecureMemoryWipe() function to securely clean memory on
12345 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12346 Implements feature 17986.
12347 - Use explicit_bzero or memset_s when present. Previously, we'd use
12348 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
12349 from <logan@hackers.mu> and <selven@hackers.mu>.
12350 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12351 zero size. Check size argument to memwipe() for underflow. Fixes
12352 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12355 o Minor features (security, RNG):
12356 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
12357 positively are not allowed to fail. Previously we depended on
12358 internal details of OpenSSL's behavior. Closes ticket 17686.
12359 - Never use the system entropy output directly for anything besides
12360 seeding the PRNG. When we want to generate important keys, instead
12361 of using system entropy directly, we now hash it with the PRNG
12362 stream. This may help resist certain attacks based on broken OS
12363 entropy implementations. Closes part of ticket 17694.
12364 - Use modern system calls (like getentropy() or getrandom()) to
12365 generate strong entropy on platforms that have them. Closes
12368 o Minor features (accounting):
12369 - Added two modes to the AccountingRule option: One for limiting
12370 only the number of bytes sent ("AccountingRule out"), and one for
12371 limiting only the number of bytes received ("AccountingRule in").
12372 Closes ticket 15989; patch from "unixninja92".
12374 o Minor features (build):
12375 - Since our build process now uses "make distcheck", we no longer
12376 force "make dist" to depend on "make check". Closes ticket 17893;
12377 patch from "cypherpunks."
12378 - Tor now builds successfully with the recent OpenSSL 1.1
12379 development branch, and with the latest LibreSSL. Closes tickets
12380 17549, 17921, and 17984.
12382 o Minor features (controller):
12383 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12384 tickets 16774 and 17817. Patch by George Tankersley.
12385 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12386 service descriptor from a service's local hidden service
12387 descriptor cache. Closes ticket 14846.
12388 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12389 controllers can examine the the reject rules added by
12390 ExitPolicyRejectPrivate. This makes it easier for stem to display
12393 o Minor features (crypto):
12394 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12396 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12397 - When allocating a digest state object, allocate no more space than
12398 we actually need. Previously, we would allocate as much space as
12399 the state for the largest algorithm would need. This change saves
12400 up to 672 bytes per circuit. Closes ticket 17796.
12401 - Improve performance when hashing non-multiple of 8 sized buffers,
12402 based on Andrew Moon's public domain SipHash-2-4 implementation.
12403 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12405 o Minor features (directory downloads):
12406 - Wait for busy authorities and fallback directories to become non-
12407 busy when bootstrapping. (A similar change was made in 6c443e987d
12408 for directory caches chosen from the consensus.) Closes ticket
12409 17864; patch by "teor".
12410 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12411 directory mirrors. The default is 1; set it to 0 to disable
12412 fallbacks. Implements ticket 17576. Patch by "teor".
12414 o Minor features (geoip):
12415 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
12418 o Minor features (IPv6):
12419 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12420 FallbackDir torrc options, to specify an IPv6 address for an
12421 authority or fallback directory. Add hard-coded ipv6 addresses for
12422 directory authorities that have them. Closes ticket 17327; patch
12423 from Nick Mathewson and "teor".
12424 - Add address policy assume_action support for IPv6 addresses.
12425 - Limit IPv6 mask bits to 128.
12426 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12427 almost always a bug. Closes ticket 17863; patch by "teor".
12428 - Allow users to configure directory authorities and fallback
12429 directory servers with IPv6 addresses and ORPorts. Resolves
12431 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12432 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12433 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12434 17638; bugfix on 0.0.2pre8. Patch by "teor".
12436 o Minor features (logging):
12437 - When logging to syslog, allow a tag to be added to the syslog
12438 identity (the string prepended to every log message). The tag can
12439 be configured with SyslogIdentityTag and defaults to none. Setting
12440 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12443 o Minor features (portability):
12444 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12445 patch from <logan@hackers.mu>.
12447 o Minor features (relay, address discovery):
12448 - Add a family argument to get_interface_addresses_raw() and
12449 subfunctions to make network interface address interogation more
12450 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12451 types of interfaces from the operating system. Resolves
12453 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12454 fails to enumerate interface addresses using the platform-specific
12455 API, have it rely on the UDP socket fallback technique to try and
12456 find out what IP addresses (both IPv4 and IPv6) our machine has.
12457 Resolves ticket 17951.
12459 o Minor features (replay cache):
12460 - The replay cache now uses SHA256 instead of SHA1. Implements
12461 feature 8961. Patch by "teor", issue reported by "rransom".
12463 o Minor features (unix file permissions):
12464 - Defer creation of Unix sockets until after setuid. This avoids
12465 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12466 CapabilityBoundingSet, or chown and fowner when using SELinux.
12467 Implements part of ticket 17562. Patch from Jamie Nguyen.
12468 - If any directory created by Tor is marked as group readable, the
12469 filesystem group is allowed to be either the default GID or the
12470 root user. Allowing root to read the DataDirectory prevents the
12471 need for CAP_READ_SEARCH when using systemd's
12472 CapabilityBoundingSet, or dac_read_search when using SELinux.
12473 Implements part of ticket 17562. Patch from Jamie Nguyen.
12474 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12475 1, the DataDirectory will be made readable by the default GID.
12476 Implements part of ticket 17562. Patch from Jamie Nguyen.
12478 o Minor bugfixes (accounting):
12479 - The max bandwidth when using 'AccountRule sum' is now correctly
12480 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12481 from "unixninja92".
12483 o Minor bugfixes (code correctness):
12484 - When closing an entry connection, generate a warning if we should
12485 have sent an end cell for it but we haven't. Fixes bug 17876;
12486 bugfix on 0.2.3.2-alpha.
12487 - Assert that allocated memory held by the reputation code is freed
12488 according to its internal counters. Fixes bug 17753; bugfix
12490 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12493 o Minor bugfixes (compilation):
12494 - Mark all object files that include micro-revision.i as depending
12495 on it, so as to make parallel builds more reliable. Fixes bug
12496 17826; bugfix on 0.2.5.1-alpha.
12497 - Don't try to use the pthread_condattr_setclock() function unless
12498 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12499 17819; bugfix on 0.2.6.3-alpha.
12500 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12502 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12503 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12504 - Fix search for libevent libraries on OpenBSD (and other systems
12505 that install libevent 1 and libevent 2 in parallel). Fixes bug
12506 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12507 - Isolate environment variables meant for tests from the rest of the
12508 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12509 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12511 - Remove config.log only from make distclean, not from make clean.
12512 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12514 o Minor bugfixes (crypto):
12515 - Check the return value of HMAC() and assert on failure. Fixes bug
12516 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12518 o Minor bugfixes (fallback directories):
12519 - Mark fallbacks as "too busy" when they return a 503 response,
12520 rather than just marking authorities. Fixes bug 17572; bugfix on
12521 0.2.4.7-alpha. Patch by "teor".
12523 o Minor bugfixes (IPv6):
12524 - Update the limits in max_dl_per_request for IPv6 address length.
12525 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12527 o Minor bugfixes (linux seccomp2 sandbox):
12528 - Fix a crash when using offline master ed25519 keys with the Linux
12529 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12531 o Minor bugfixes (logging):
12532 - In log messages that include a function name, use __FUNCTION__
12533 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12534 with clang __PRETTY_FUNCTION__ has extra information we don't
12535 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12537 - Remove needless quotes from a log message about unparseable
12538 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12540 o Minor bugfixes (portability):
12541 - Remove an #endif from configure.ac so that we correctly detect the
12542 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12545 o Minor bugfixes (relays):
12546 - Check that both the ORPort and DirPort (if present) are reachable
12547 before publishing a relay descriptor. Otherwise, relays publish a
12548 descriptor with DirPort 0 when the DirPort reachability test takes
12549 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12550 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12552 o Minor bugfixes (relays, hidden services):
12553 - Refuse connection requests to private OR addresses unless
12554 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12555 then refuse to send any cells to a private address. Fixes bugs
12556 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12558 o Minor bugfixes (safe logging):
12559 - When logging a malformed hostname received through socks4, scrub
12560 it if SafeLogging says we should. Fixes bug 17419; bugfix
12563 o Minor bugfixes (statistics code):
12564 - Consistently check for overflow in round_*_to_next_multiple_of
12565 functions, and add unit tests with additional and maximal values.
12566 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12567 - Handle edge cases in the laplace functions: avoid division by
12568 zero, avoid taking the log of zero, and silence clang type
12569 conversion warnings using round and trunc. Add unit tests for edge
12570 cases with maximal values. Fixes part of bug 13192; bugfix
12573 o Minor bugfixes (testing):
12574 - The test for log_heartbeat was incorrectly failing in timezones
12575 with non-integer offsets. Instead of comparing the end of the time
12576 string against a constant, compare it to the output of
12577 format_local_iso_time when given the correct input. Fixes bug
12578 18039; bugfix on 0.2.5.4-alpha.
12579 - Make unit tests pass on IPv6-only systems, and systems without
12580 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12581 bugfix on 0.2.7.3-rc. Patch by "teor".
12582 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12584 - Check the full results of SHA256 and SHA512 digests in the unit
12585 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12587 o Code simplification and refactoring:
12588 - Move logging of redundant policy entries in
12589 policies_parse_exit_policy_internal into its own function. Closes
12590 ticket 17608; patch from "juce".
12591 - Extract the more complicated parts of circuit_mark_for_close()
12592 into a new function that we run periodically before circuits are
12593 freed. This change removes more than half of the functions
12594 currently in the "blob". Closes ticket 17218.
12595 - Clean up a little duplicated code in
12596 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12598 - Decouple the list of streams waiting to be attached to circuits
12599 from the overall connection list. This change makes it possible to
12600 attach streams quickly while simplifying Tor's callgraph and
12601 avoiding O(N) scans of the entire connection list. Closes
12603 - When a direct directory request fails immediately on launch,
12604 instead of relaunching that request from inside the code that
12605 launches it, instead mark the connection for teardown. This change
12606 simplifies Tor's callback and prevents the directory-request
12607 launching code from invoking itself recursively. Closes
12609 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12610 use them. Closes ticket 17926.
12613 - Add a description of the correct use of the '--keygen' command-
12614 line option. Closes ticket 17583; based on text by 's7r'.
12615 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12616 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12617 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12618 - Mention torspec URL in the manpage and point the reader to it
12619 whenever we mention a document that belongs in torspce. Fixes
12622 o Removed features:
12623 - Remove client-side support for connecting to Tor relays running
12624 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12625 the v3 TLS handshake protocol, and are no longer allowed on the
12626 Tor network. Implements the client side of ticket 11150. Based on
12627 patches by Tom van der Woerdt.
12630 - Add unit tests to check for common RNG failure modes, such as
12631 returning all zeroes, identical values, or incrementing values
12632 (OpenSSL's rand_predictable feature). Patch by "teor".
12633 - Log more information when the backtrace tests fail. Closes ticket
12634 17892. Patch from "cypherpunks."
12635 - Always test both ed25519 backends, so that we can be sure that our
12636 batch-open replacement code works. Part of ticket 16794.
12637 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
12638 portion of ticket 16831.
12639 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
12640 util_format.c, directory.c, and options_validate.c. Closes tickets
12641 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
12643 - Unit tests for directory_handle_command_get. Closes ticket 17004.
12644 Patch from Reinaldo de Souza Jr.
12647 Changes in version 0.2.7.6 - 2015-12-10
12648 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
12649 well as a minor bug in hidden service reliability.
12651 o Major bugfixes (guard selection):
12652 - Actually look at the Guard flag when selecting a new directory
12653 guard. When we implemented the directory guard design, we
12654 accidentally started treating all relays as if they have the Guard
12655 flag during guard selection, leading to weaker anonymity and worse
12656 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12659 o Minor features (geoip):
12660 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
12663 o Minor bugfixes (compilation):
12664 - When checking for net/pfvar.h, include netinet/in.h if possible.
12665 This fixes transparent proxy detection on OpenBSD. Fixes bug
12666 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
12667 - Fix a compilation warning with Clang 3.6: Do not check the
12668 presence of an address which can never be NULL. Fixes bug 17781.
12670 o Minor bugfixes (correctness):
12671 - When displaying an IPv6 exit policy, include the mask bits
12672 correctly even when the number is greater than 31. Fixes bug
12673 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
12674 - The wrong list was used when looking up expired intro points in a
12675 rend service object, causing what we think could be reachability
12676 issues for hidden services, and triggering a BUG log. Fixes bug
12677 16702; bugfix on 0.2.7.2-alpha.
12678 - Fix undefined behavior in the tor_cert_checksig function. Fixes
12679 bug 17722; bugfix on 0.2.7.2-alpha.
12682 Changes in version 0.2.7.5 - 2015-11-20
12683 The Tor 0.2.7 release series is dedicated to the memory of Tor user
12684 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
12685 tirelessly to advocate human rights regardless of national borders,
12686 and oppose the encroachments of mass surveillance. He opposed national
12687 exceptionalism, he brought clarity to legal and policy debates, he
12688 understood and predicted the impact of mass surveillance on the world,
12689 and he laid the groundwork for resisting it. While serving on the Tor
12690 Project's board of directors, he brought us his uncompromising focus
12691 on technical excellence in the service of humankind. Caspar was an
12692 inimitable force for good and a wonderful friend. He was kind,
12693 humorous, generous, gallant, and believed we should protect one
12694 another without exception. We honor him here for his ideals, his
12695 efforts, and his accomplishments. Please honor his memory with works
12696 that would make him proud.
12698 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
12700 The 0.2.7 series adds a more secure identity key type for relays,
12701 improves cryptography performance, resolves several longstanding
12702 hidden-service performance issues, improves controller support for
12703 hidden services, and includes small bugfixes and performance
12704 improvements throughout the program. This release series also includes
12705 more tests than before, and significant simplifications to which parts
12706 of Tor invoke which others.
12708 (This release contains no code changes since 0.2.7.4-rc.)
12711 Changes in version 0.2.7.4-rc - 2015-10-21
12712 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
12713 fixes some important memory leaks, and a scary-looking (but mostly
12714 harmless in practice) invalid-read bug. It also has a few small
12715 bugfixes, notably fixes for compilation and portability on different
12716 platforms. If no further significant bounds are found, the next
12717 release will the the official stable release.
12719 o Major bugfixes (security, correctness):
12720 - Fix an error that could cause us to read 4 bytes before the
12721 beginning of an openssl string. This bug could be used to cause
12722 Tor to crash on systems with unusual malloc implementations, or
12723 systems with unusual hardening installed. Fixes bug 17404; bugfix
12726 o Major bugfixes (correctness):
12727 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
12728 bug 17401; bugfix on 0.2.7.3-rc.
12730 o Major bugfixes (memory leaks):
12731 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
12732 17398; bugfix on 0.2.6.1-alpha.
12733 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
12734 17402; bugfix on 0.2.7.3-rc.
12735 - Fix a memory leak when reading an expired signing key from disk.
12736 Fixes bug 17403; bugfix on 0.2.7.2-rc.
12738 o Minor features (geoIP):
12739 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
12742 o Minor bugfixes (compilation):
12743 - Repair compilation with the most recent (unreleased, alpha)
12744 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
12745 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
12746 17251; bugfix on 0.2.7.2-alpha.
12747 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12748 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12750 o Minor bugfixes (portability):
12751 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
12752 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
12755 o Minor bugfixes (sandbox):
12756 - Add the "hidserv-stats" filename to our sandbox filter for the
12757 HiddenServiceStatistics option to work properly. Fixes bug 17354;
12758 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
12760 o Minor bugfixes (testing):
12761 - Add unit tests for get_interface_address* failure cases. Fixes bug
12762 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
12763 - Fix breakage when running 'make check' with BSD make. Fixes bug
12764 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
12765 - Make the get_ifaddrs_* unit tests more tolerant of different
12766 network configurations. (Don't assume every test box has an IPv4
12767 address, and don't assume every test box has a non-localhost
12768 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
12769 - Skip backtrace tests when backtrace support is not compiled in.
12770 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
12774 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
12775 - Note that HiddenServicePorts can take a unix domain socket. Closes
12779 Changes in version 0.2.7.3-rc - 2015-09-25
12780 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
12781 contains numerous usability fixes for Ed25519 keys, safeguards against
12782 several misconfiguration problems, significant simplifications to
12783 Tor's callgraph, and numerous bugfixes and small features.
12785 This is the most tested release of Tor to date. The unit tests cover
12786 39.40% of the code, and the integration tests (accessible with "make
12787 test-full-online", requiring stem and chutney and a network
12788 connection) raise the coverage to 64.49%.
12790 o Major features (security, hidden services):
12791 - Hidden services, if using the EntryNodes option, are required to
12792 use more than one EntryNode, in order to avoid a guard discovery
12793 attack. (This would only affect people who had configured hidden
12794 services and manually specified the EntryNodes option with a
12795 single entry-node. The impact was that it would be easy to
12796 remotely identify the guard node used by such a hidden service.
12797 See ticket for more information.) Fixes ticket 14917.
12799 o Major features (Ed25519 keys, keypinning):
12800 - The key-pinning option on directory authorities is now advisory-
12801 only by default. In a future version, or when the AuthDirPinKeys
12802 option is set, pins are enforced again. Disabling key-pinning
12803 seemed like a good idea so that we can survive the fallout of any
12804 usability problems associated with Ed25519 keys. Closes
12807 o Major features (Ed25519 performance):
12808 - Improve the speed of Ed25519 operations and Curve25519 keypair
12809 generation when built targeting 32 bit x86 platforms with SSE2
12810 available. Implements ticket 16535.
12811 - Improve the runtime speed of Ed25519 signature verification by
12812 using Ed25519-donna's batch verification support. Implements
12815 o Major features (performance testing):
12816 - The test-network.sh script now supports performance testing.
12817 Requires corresponding chutney performance testing changes. Patch
12818 by "teor". Closes ticket 14175.
12820 o Major features (relay, Ed25519):
12821 - Significant usability improvements for Ed25519 key management. Log
12822 messages are better, and the code can recover from far more
12823 failure conditions. Thanks to "s7r" for reporting and diagnosing
12825 - Add a new OfflineMasterKey option to tell Tor never to try loading
12826 or generating a secret Ed25519 identity key. You can use this in
12827 combination with tor --keygen to manage offline and/or encrypted
12828 Ed25519 keys. Implements ticket 16944.
12829 - Add a --newpass option to allow changing or removing the
12830 passphrase of an encrypted key with tor --keygen. Implements part
12832 - On receiving a HUP signal, check to see whether the Ed25519
12833 signing key has changed, and reload it if so. Closes ticket 16790.
12835 o Major bugfixes (relay, Ed25519):
12836 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
12837 0.2.7.2-alpha. Reported by "s7r".
12838 - Improve handling of expired signing keys with offline master keys.
12839 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
12841 o Minor features (client-side privacy):
12842 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
12843 lifespan when IsolateSOCKSAuth and streams with SOCKS
12844 authentication are attached to the circuit. This allows
12845 applications like TorBrowser to manage circuit lifetime on their
12846 own. Implements feature 15482.
12847 - When logging malformed hostnames from SOCKS5 requests, respect
12848 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
12850 o Minor features (compilation):
12851 - Give a warning as early as possible when trying to build with an
12852 unsupported OpenSSL version. Closes ticket 16901.
12853 - Fail during configure if we're trying to build against an OpenSSL
12854 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
12855 which started requiring ECC.
12857 o Minor features (geoip):
12858 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
12861 o Minor features (hidden services):
12862 - Relays need to have the Fast flag to get the HSDir flag. As this
12863 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
12864 drop. This change should make some attacks against the hidden
12865 service directory system harder. Fixes ticket 15963.
12866 - Turn on hidden service statistics collection by setting the torrc
12867 option HiddenServiceStatistics to "1" by default. (This keeps
12868 track only of the fraction of traffic used by hidden services, and
12869 the total number of hidden services in existence.) Closes
12871 - Client now uses an introduction point failure cache to know when
12872 to fetch or keep a descriptor in their cache. Previously, failures
12873 were recorded implicitly, but not explicitly remembered. Closes
12876 o Minor features (testing, authorities, documentation):
12877 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
12878 explicitly manage consensus flags in testing networks. Patch by
12879 "robgjansen", modified by "teor". Implements part of ticket 14882.
12881 o Minor bugfixes (security, exit policies):
12882 - ExitPolicyRejectPrivate now also rejects the relay's published
12883 IPv6 address (if any), and any publicly routable IPv4 or IPv6
12884 addresses on any local interfaces. ticket 17027. Patch by "teor".
12885 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
12887 o Minor bug fixes (torrc exit policies):
12888 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
12889 produce IPv6 wildcard addresses. Previously they would produce
12890 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
12891 of bug 16069; bugfix on 0.2.4.7-alpha.
12892 - When parsing torrc ExitPolicies, we now warn for a number of cases
12893 where the user's intent is likely to differ from Tor's actual
12894 behavior. These include: using an IPv4 address with an accept6 or
12895 reject6 line; using "private" on an accept6 or reject6 line; and
12896 including any ExitPolicy lines after accept *:* or reject *:*.
12897 Related to ticket 16069.
12898 - When parsing torrc ExitPolicies, we now issue an info-level
12899 message when expanding an "accept/reject *" line to include both
12900 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
12901 - In each instance above, usage advice is provided to avoid the
12902 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
12903 16069; bugfix on 0.2.4.7-alpha.
12905 o Minor bugfixes (authority):
12906 - Don't assign "HSDir" to a router if it isn't Valid and Running.
12907 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
12908 - Downgrade log messages about Ed25519 key issues if they are in old
12909 cached router descriptors. Fixes part of bug 16286; bugfix
12911 - When we find an Ed25519 key issue in a cached descriptor, stop
12912 saying the descriptor was just "uploaded". Fixes another part of
12913 bug 16286; bugfix on 0.2.7.2-alpha.
12915 o Minor bugfixes (control port):
12916 - Repair a warning and a spurious result when getting the maximum
12917 number of file descriptors from the controller. Fixes bug 16697;
12918 bugfix on 0.2.7.2-alpha.
12920 o Minor bugfixes (correctness):
12921 - When calling channel_free_list(), avoid calling smartlist_remove()
12922 while inside a FOREACH loop. This partially reverts commit
12923 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
12924 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
12926 o Minor bugfixes (documentation):
12927 - Advise users on how to configure separate IPv4 and IPv6 exit
12928 policies in the manpage and sample torrcs. Related to ticket 16069.
12929 - Fix the usage message of tor-resolve(1) so that it no longer lists
12930 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
12931 - Fix an error in the manual page and comments for
12932 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
12933 required "ORPort connectivity". While this is true, it is in no
12934 way unique to the HSDir flag. Of all the flags, only HSDirs need a
12935 DirPort configured in order for the authorities to assign that
12936 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
12939 o Minor bugfixes (Ed25519):
12940 - Fix a memory leak when reading router descriptors with expired
12941 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
12943 o Minor bugfixes (linux seccomp2 sandbox):
12944 - Allow bridge authorities to run correctly under the seccomp2
12945 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
12946 - Allow routers with ed25519 keys to run correctly under the
12947 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
12949 o Minor bugfixes (open file limit):
12950 - Fix set_max_file_descriptors() to set by default the max open file
12951 limit to the current limit when setrlimit() fails. Fixes bug
12952 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
12954 o Minor bugfixes (portability):
12955 - Try harder to normalize the exit status of the Tor process to the
12956 standard-provided range. Fixes bug 16975; bugfix on every version
12958 - Check correctly for Windows socket errors in the workqueue
12959 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
12960 - Fix the behavior of crypto_rand_time_range() when told to consider
12961 times before 1970. (These times were possible when running in a
12962 simulated network environment where time()'s output starts at
12963 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
12964 - Restore correct operation of TLS client-cipher detection on
12965 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
12967 o Minor bugfixes (relay):
12968 - Ensure that worker threads actually exit when a fatal error or
12969 shutdown is indicated. This fix doesn't currently affect the
12970 behavior of Tor, because Tor workers never indicates fatal error
12971 or shutdown except in the unit tests. Fixes bug 16868; bugfix
12973 - Unblock threads before releasing the work queue mutex to ensure
12974 predictable scheduling behavior. Fixes bug 16644; bugfix
12977 o Code simplification and refactoring:
12978 - Change the function that's called when we need to retry all
12979 downloads so that it only reschedules the downloads to happen
12980 immediately, rather than launching them all at once itself. This
12981 further simplifies Tor's callgraph.
12982 - Move some format-parsing functions out of crypto.c and
12983 crypto_curve25519.c into crypto_format.c and/or util_format.c.
12984 - Move the client-only parts of init_keys() into a separate
12985 function. Closes ticket 16763.
12986 - Simplify the microdesc_free() implementation so that it no longer
12987 appears (to code analysis tools) to potentially invoke a huge
12988 suite of other microdesc functions.
12989 - Simply the control graph further by deferring the inner body of
12990 directory_all_unreachable() into a callback. Closes ticket 16762.
12991 - Treat the loss of an owning controller as equivalent to a SIGTERM
12992 signal. This removes a tiny amount of duplicated code, and
12993 simplifies our callgraph. Closes ticket 16788.
12994 - When generating an event to send to the controller, we no longer
12995 put the event over the network immediately. Instead, we queue
12996 these events, and use a Libevent callback to deliver them. This
12997 change simplifies Tor's callgraph by reducing the number of
12998 functions from which all other Tor functions are reachable. Closes
13000 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13001 that try to scan or compile every file on Unix won't decide that
13003 - Remove the unused "nulterminate" argument from buf_pullup().
13006 - Recommend a 40 GB example AccountingMax in torrc.sample rather
13007 than a 4 GB max. Closes ticket 16742.
13008 - Include the TUNING document in our source tarball. It is referred
13009 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13013 - The internal pure-C tor-fw-helper tool is now removed from the Tor
13014 distribution, in favor of the pure-Go clone available from
13015 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
13016 used by the C tor-fw-helper are not, in our opinion, very
13017 confidence- inspiring in their secure-programming techniques.
13018 Closes ticket 13338.
13019 - Remove the code that would try to aggressively flush controller
13020 connections while writing to them. This code was introduced in
13021 0.1.2.7-alpha, in order to keep output buffers from exceeding
13022 their limits. But there is no longer a maximum output buffer size,
13023 and flushing data in this way caused some undesirable recursions
13024 in our call graph. Closes ticket 16480.
13027 - Make "bridges+hs" the default test network. This tests almost all
13028 tor functionality during make test-network, while allowing tests
13029 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
13030 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
13031 (chutney). Patches by "teor".
13032 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
13033 by-side in the same parent directory. Closes ticket 16903. Patch
13035 - Use environment variables rather than autoconf substitutions to
13036 send variables from the build system to the test scripts. This
13037 change should be easier to maintain, and cause 'make distcheck' to
13038 work better than before. Fixes bug 17148.
13039 - Add a new set of callgraph analysis scripts that use clang to
13040 produce a list of which Tor functions are reachable from which
13041 other Tor functions. We're planning to use these to help simplify
13042 our code structure by identifying illogical dependencies.
13043 - Add new 'test-full' and 'test-full-online' targets to run all
13044 tests, including integration tests with stem and chutney.
13045 - Make the test-workqueue test work on Windows by initializing the
13046 network before we begin.
13047 - New make target (make test-network-all) to run multiple applicable
13048 chutney test cases. Patch from Teor; closes 16953.
13049 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
13050 functions in dns.c. Implements a portion of ticket 16831.
13051 - When building Tor with testing coverage enabled, run Chutney tests
13052 (if any) using the 'tor-cov' coverage binary.
13053 - When running test-network or test-stem, check for the absence of
13054 stem/chutney before doing any build operations.
13057 Changes in version 0.2.7.2-alpha - 2015-07-27
13058 This, the second alpha in the Tor 0.2.7 series, has a number of new
13059 features, including a way to manually pick the number of introduction
13060 points for hidden services, and the much stronger Ed25519 signing key
13061 algorithm for regular Tor relays (including support for encrypted
13062 offline identity keys in the new algorithm).
13064 Support for Ed25519 on relays is currently limited to signing router
13065 descriptors; later alphas in this series will extend Ed25519 key
13066 support to more parts of the Tor protocol.
13068 o Major features (Ed25519 identity keys, Proposal 220):
13069 - All relays now maintain a stronger identity key, using the Ed25519
13070 elliptic curve signature format. This master key is designed so
13071 that it can be kept offline. Relays also generate an online
13072 signing key, and a set of other Ed25519 keys and certificates.
13073 These are all automatically regenerated and rotated as needed.
13074 Implements part of ticket 12498.
13075 - Directory authorities now vote on Ed25519 identity keys along with
13076 RSA1024 keys. Implements part of ticket 12498.
13077 - Directory authorities track which Ed25519 identity keys have been
13078 used with which RSA1024 identity keys, and do not allow them to
13079 vary freely. Implements part of ticket 12498.
13080 - Microdescriptors now include Ed25519 identity keys. Implements
13081 part of ticket 12498.
13082 - Add support for offline encrypted Ed25519 master keys. To use this
13083 feature on your tor relay, run "tor --keygen" to make a new master
13084 key (or to make a new signing key if you already have a master
13085 key). Closes ticket 13642.
13087 o Major features (Hidden services):
13088 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13089 specify a fixed number of introduction points. Its maximum value
13090 is 10 and default is 3. Using this option can increase a hidden
13091 service's reliability under load, at the cost of making it more
13092 visible that the hidden service is facing extra load. Closes
13094 - Remove the adaptive algorithm for choosing the number of
13095 introduction points, which used to change the number of
13096 introduction points (poorly) depending on the number of
13097 connections the HS sees. Closes ticket 4862.
13099 o Major features (onion key cross-certification):
13100 - Relay descriptors now include signatures of their own identity
13101 keys, made using the TAP and ntor onion keys. These signatures
13102 allow relays to prove ownership of their own onion keys. Because
13103 of this change, microdescriptors will no longer need to include
13104 RSA identity keys. Implements proposal 228; closes ticket 12499.
13106 o Major features (performance):
13107 - Improve the runtime speed of Ed25519 operations by using the
13108 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13109 Implements ticket 16467.
13110 - Improve the runtime speed of the ntor handshake by using an
13111 optimized curve25519 basepoint scalarmult implementation from the
13112 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13113 ideas by Adam Langley. Implements ticket 9663.
13115 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13116 - Properly separate out each SOCKSPort when applying stream
13117 isolation. The error occurred because each port's session group
13118 was being overwritten by a default value when the listener
13119 connection was initialized. Fixes bug 16247; bugfix on
13120 0.2.6.3-alpha. Patch by "jojelino".
13122 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13123 - Stop refusing to store updated hidden service descriptors on a
13124 client. This reverts commit 9407040c59218 (which indeed fixed bug
13125 14219, but introduced a major hidden service reachability
13126 regression detailed in bug 16381). This is a temporary fix since
13127 we can live with the minor issue in bug 14219 (it just results in
13128 some load on the network) but the regression of 16381 is too much
13129 of a setback. First-round fix for bug 16381; bugfix
13132 o Major bugfixes (hidden services):
13133 - When cannibalizing a circuit for an introduction point, always
13134 extend to the chosen exit node (creating a 4 hop circuit).
13135 Previously Tor would use the current circuit exit node, which
13136 changed the original choice of introduction point, and could cause
13137 the hidden service to skip excluded introduction points or
13138 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13141 o Major bugfixes (open file limit):
13142 - The open file limit wasn't checked before calling
13143 tor_accept_socket_nonblocking(), which would make Tor exceed the
13144 limit. Now, before opening a new socket, Tor validates the open
13145 file limit just before, and if the max has been reached, return an
13146 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13148 o Major bugfixes (stability, also in 0.2.6.10):
13149 - Stop crashing with an assertion failure when parsing certain kinds
13150 of malformed or truncated microdescriptors. Fixes bug 16400;
13151 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13152 by "cypherpunks_backup".
13153 - Stop random client-side assertion failures that could occur when
13154 connecting to a busy hidden service, or connecting to a hidden
13155 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13158 o Minor features (directory authorities, security, also in 0.2.6.9):
13159 - The HSDir flag given by authorities now requires the Stable flag.
13160 For the current network, this results in going from 2887 to 2806
13161 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13162 attack by raising the effort for a relay to become Stable to
13163 require at the very least 7 days, while maintaining the 96 hours
13164 uptime requirement for HSDir. Implements ticket 8243.
13166 o Minor features (client):
13167 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13168 character '_' to appear, in order to cope with domains observed in
13169 the wild that are serving non-RFC compliant records. Resolves
13171 - Relax the validation done to hostnames in SOCKS5 requests, and
13172 allow a single trailing '.' to cope with clients that pass FQDNs
13173 using that syntax to explicitly indicate that the domain name is
13174 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13175 - Add GroupWritable and WorldWritable options to unix-socket based
13176 SocksPort and ControlPort options. These options apply to a single
13177 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13180 o Minor features (control protocol):
13181 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13182 the control protocol. Resolves ticket 15358.
13184 o Minor features (directory authorities):
13185 - Directory authorities no longer vote against the "Fast", "Stable",
13186 and "HSDir" flags just because they were going to vote against
13187 "Running": if the consensus turns out to be that the router was
13188 running, then the authority's vote should count. Patch from Peter
13189 Retzlaff; closes issue 8712.
13191 o Minor features (geoip, also in 0.2.6.10):
13192 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13193 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13195 o Minor features (hidden services):
13196 - Add the new options "HiddenServiceMaxStreams" and
13197 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13198 limit the maximum number of simultaneous streams per circuit, and
13199 optionally tear down the circuit when the limit is exceeded. Part
13202 o Minor features (portability):
13203 - Use C99 variadic macros when the compiler is not GCC. This avoids
13204 failing compilations on MSVC, and fixes a log-file-based race
13205 condition in our old workarounds. Original patch from Gisle Vanem.
13207 o Minor bugfixes (compilation, also in 0.2.6.9):
13208 - Build with --enable-systemd correctly when libsystemd is
13209 installed, but systemd is not. Fixes bug 16164; bugfix on
13210 0.2.6.3-alpha. Patch from Peter Palfrader.
13212 o Minor bugfixes (controller):
13213 - Add the descriptor ID in each HS_DESC control event. It was
13214 missing, but specified in control-spec.txt. Fixes bug 15881;
13215 bugfix on 0.2.5.2-alpha.
13217 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13218 - Check for failures from crypto_early_init, and refuse to continue.
13219 A previous typo meant that we could keep going with an
13220 uninitialized crypto library, and would have OpenSSL initialize
13221 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13222 when implementing ticket 4900. Patch by "teor".
13224 o Minor bugfixes (hidden services):
13225 - Fix a crash when reloading configuration while at least one
13226 configured and one ephemeral hidden service exists. Fixes bug
13227 16060; bugfix on 0.2.7.1-alpha.
13228 - Avoid crashing with a double-free bug when we create an ephemeral
13229 hidden service but adding it fails for some reason. Fixes bug
13230 16228; bugfix on 0.2.7.1-alpha.
13232 o Minor bugfixes (Linux seccomp2 sandbox):
13233 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13234 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13236 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13237 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13238 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13239 on 0.2.6.3-alpha. Patch from "teor".
13241 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13242 - Fix sandboxing to work when running as a relay, by allowing the
13243 renaming of secret_id_key, and allowing the eventfd2 and futex
13244 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13246 - Allow systemd connections to work with the Linux seccomp2 sandbox
13247 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13250 o Minor bugfixes (relay):
13251 - Fix a rarely-encountered memory leak when failing to initialize
13252 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13253 from "cypherpunks".
13255 o Minor bugfixes (systemd):
13256 - Fix an accidental formatting error that broke the systemd
13257 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
13258 - Tor's systemd unit file no longer contains extraneous spaces.
13259 These spaces would sometimes confuse tools like deb-systemd-
13260 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13262 o Minor bugfixes (tests):
13263 - Use the configured Python executable when running test-stem-full.
13264 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
13266 o Minor bugfixes (tests, also in 0.2.6.9):
13267 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13268 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13270 o Minor bugfixes (threads, comments):
13271 - Always initialize return value in compute_desc_id in rendcommon.c
13272 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13273 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
13274 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13275 - Remove undefined directive-in-macro in test_util_writepid clang
13276 3.7 complains that using a preprocessor directive inside a macro
13277 invocation in test_util_writepid in test_util.c is undefined.
13278 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13280 o Code simplification and refactoring:
13281 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13282 to ensure they remain consistent and visible everywhere.
13283 - Remove some vestigial workarounds for the MSVC6 compiler. We
13284 haven't supported that in ages.
13285 - The link authentication code has been refactored for better
13286 testability and reliability. It now uses code generated with the
13287 "trunnel" binary encoding generator, to reduce the risk of bugs
13288 due to programmer error. Done as part of ticket 12498.
13291 - Include a specific and (hopefully) accurate documentation of the
13292 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13293 of interest to people writing programs to parse or generate torrc
13294 files. This document is not a commitment to long-term
13295 compatibility; some aspects of the current format are a bit
13296 ridiculous. Closes ticket 2325.
13298 o Removed features:
13299 - Tor no longer supports copies of OpenSSL that are missing support
13300 for Elliptic Curve Cryptography. (We began using ECC when
13301 available in 0.2.4.8-alpha, for more safe and efficient key
13302 negotiation.) In particular, support for at least one of P256 or
13303 P224 is now required, with manual configuration needed if only
13304 P224 is available. Resolves ticket 16140.
13305 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13306 on an operating system that has not upgraded to OpenSSL 1.0 or
13307 later, and you compile Tor from source, you will need to install a
13308 more recent OpenSSL to link Tor against.) These versions of
13309 OpenSSL are still supported by the OpenSSL, but the numerous
13310 cryptographic improvements in later OpenSSL releases makes them a
13311 clear choice. Resolves ticket 16034.
13312 - Remove the HidServDirectoryV2 option. Now all relays offer to
13313 store hidden service descriptors. Related to 16543.
13314 - Remove the VoteOnHidServDirectoriesV2 option, since all
13315 authorities have long set it to 1. Closes ticket 16543.
13318 - Document use of coverity, clang static analyzer, and clang dynamic
13319 undefined behavior and address sanitizers in doc/HACKING. Include
13320 detailed usage instructions in the blacklist. Patch by "teor".
13321 Closes ticket 15817.
13322 - The link authentication protocol code now has extensive tests.
13323 - The relay descriptor signature testing code now has
13325 - The test_workqueue program now runs faster, and is enabled by
13326 default as a part of "make check".
13327 - Now that OpenSSL has its own scrypt implementation, add an unit
13328 test that checks for interoperability between libscrypt_scrypt()
13329 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
13330 and rely on EVP_PBE_scrypt() whenever possible. Resolves
13334 Changes in version 0.2.6.10 - 2015-07-12
13335 Tor version 0.2.6.10 fixes some significant stability and hidden
13336 service client bugs, bulletproofs the cryptography init process, and
13337 fixes a bug when using the sandbox code with some older versions of
13338 Linux. Everyone running an older version, especially an older version
13339 of 0.2.6, should upgrade.
13341 o Major bugfixes (hidden service clients, stability):
13342 - Stop refusing to store updated hidden service descriptors on a
13343 client. This reverts commit 9407040c59218 (which indeed fixed bug
13344 14219, but introduced a major hidden service reachability
13345 regression detailed in bug 16381). This is a temporary fix since
13346 we can live with the minor issue in bug 14219 (it just results in
13347 some load on the network) but the regression of 16381 is too much
13348 of a setback. First-round fix for bug 16381; bugfix
13351 o Major bugfixes (stability):
13352 - Stop crashing with an assertion failure when parsing certain kinds
13353 of malformed or truncated microdescriptors. Fixes bug 16400;
13354 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13355 by "cypherpunks_backup".
13356 - Stop random client-side assertion failures that could occur when
13357 connecting to a busy hidden service, or connecting to a hidden
13358 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13361 o Minor features (geoip):
13362 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13363 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13365 o Minor bugfixes (crypto error-handling):
13366 - Check for failures from crypto_early_init, and refuse to continue.
13367 A previous typo meant that we could keep going with an
13368 uninitialized crypto library, and would have OpenSSL initialize
13369 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13370 when implementing ticket 4900. Patch by "teor".
13372 o Minor bugfixes (Linux seccomp2 sandbox):
13373 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13374 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13375 on 0.2.6.3-alpha. Patch from "teor".
13378 Changes in version 0.2.6.9 - 2015-06-11
13379 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
13380 requirements for receiving an HSDir flag, and addresses some other small
13381 bugs in the systemd and sandbox code. Clients using circuit isolation
13382 should upgrade; all directory authorities should upgrade.
13384 o Major bugfixes (client-side privacy):
13385 - Properly separate out each SOCKSPort when applying stream
13386 isolation. The error occurred because each port's session group was
13387 being overwritten by a default value when the listener connection
13388 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
13391 o Minor feature (directory authorities, security):
13392 - The HSDir flag given by authorities now requires the Stable flag.
13393 For the current network, this results in going from 2887 to 2806
13394 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13395 attack by raising the effort for a relay to become Stable which
13396 takes at the very least 7 days to do so and by keeping the 96
13397 hours uptime requirement for HSDir. Implements ticket 8243.
13399 o Minor bugfixes (compilation):
13400 - Build with --enable-systemd correctly when libsystemd is
13401 installed, but systemd is not. Fixes bug 16164; bugfix on
13402 0.2.6.3-alpha. Patch from Peter Palfrader.
13404 o Minor bugfixes (Linux seccomp2 sandbox):
13405 - Fix sandboxing to work when running as a relaymby renaming of
13406 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
13407 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
13408 - Allow systemd connections to work with the Linux seccomp2 sandbox
13409 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13412 o Minor bugfixes (tests):
13413 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13414 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13417 Changes in version 0.2.6.8 - 2015-05-21
13418 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
13419 fixes an authority-side bug in assigning the HSDir flag. All directory
13420 authorities should upgrade.
13422 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13423 - Revert commit that made directory authorities assign the HSDir
13424 flag to relays without a DirPort; this was bad because such relays
13425 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13428 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13429 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13430 a client authorized hidden service. Fixes bug 15823; bugfix
13433 o Minor features (geoip):
13434 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13435 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13439 Changes in version 0.2.7.1-alpha - 2015-05-12
13440 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13441 includes numerous small features and bugfixes against previous Tor
13442 versions, and numerous small infrastructure improvements. The most
13443 notable features are several new ways for controllers to interact with
13444 the hidden services subsystem.
13446 o New system requirements:
13447 - Tor no longer includes workarounds to support Libevent versions
13448 before 1.3e. Libevent 2.0 or later is recommended. Closes
13451 o Major features (controller):
13452 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13453 and management of hidden services via the controller. Closes
13455 - New "GETINFO onions/current" and "GETINFO onions/detached"
13456 commands to get information about hidden services created via the
13457 controller. Part of ticket 6411.
13458 - New HSFETCH command to launch a request for a hidden service
13459 descriptor. Closes ticket 14847.
13460 - New HSPOST command to upload a hidden service descriptor. Closes
13461 ticket 3523. Patch by "DonnchaC".
13463 o Major bugfixes (hidden services):
13464 - Revert commit that made directory authorities assign the HSDir
13465 flag to relays without a DirPort; this was bad because such relays
13466 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13469 o Minor features (clock-jump tolerance):
13470 - Recover better when our clock jumps back many hours, like might
13471 happen for Tails or Whonix users who start with a very wrong
13472 hardware clock, use Tor to discover a more accurate time, and then
13473 fix their clock. Resolves part of ticket 8766.
13475 o Minor features (command-line interface):
13476 - Make --hash-password imply --hush to prevent unnecessary noise.
13477 Closes ticket 15542. Patch from "cypherpunks".
13478 - Print a warning whenever we find a relative file path being used
13479 as torrc option. Resolves issue 14018.
13481 o Minor features (controller):
13482 - Add DirAuthority lines for default directory authorities to the
13483 output of the "GETINFO config/defaults" command if not already
13484 present. Implements ticket 14840.
13485 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13486 retrieve items from the client's hidden service descriptor cache.
13487 Closes ticket 14845.
13488 - Implement a new controller command "GETINFO status/fresh-relay-
13489 descs" to fetch a descriptor/extrainfo pair that was generated on
13490 demand just for the controller's use. Implements ticket 14784.
13492 o Minor features (DoS-resistance):
13493 - Make it harder for attackers to overload hidden services with
13494 introductions, by blocking multiple introduction requests on the
13495 same circuit. Resolves ticket 15515.
13497 o Minor features (geoip):
13498 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13499 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13502 o Minor features (HS popularity countermeasure):
13503 - To avoid leaking HS popularity, don't cycle the introduction point
13504 when we've handled a fixed number of INTRODUCE2 cells but instead
13505 cycle it when a random number of introductions is reached, thus
13506 making it more difficult for an attacker to find out the amount of
13507 clients that have used the introduction point for a specific HS.
13508 Closes ticket 15745.
13510 o Minor features (logging):
13511 - Include the Tor version in all LD_BUG log messages, since people
13512 tend to cut and paste those into the bugtracker. Implements
13515 o Minor features (pluggable transports):
13516 - When launching managed pluggable transports on Linux systems,
13517 attempt to have the kernel deliver a SIGTERM on tor exit if the
13518 pluggable transport process is still running. Resolves
13520 - When launching managed pluggable transports, setup a valid open
13521 stdin in the child process that can be used to detect if tor has
13522 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13523 can be used by implementations to detect this new behavior.
13524 Resolves ticket 15435.
13526 o Minor features (testing):
13527 - Add a test to verify that the compiler does not eliminate our
13528 memwipe() implementation. Closes ticket 15377.
13529 - Add make rule `check-changes` to verify the format of changes
13530 files. Closes ticket 15180.
13531 - Add unit tests for control_event_is_interesting(). Add a compile-
13532 time check that the number of events doesn't exceed the capacity
13533 of control_event_t.event_mask. Closes ticket 15431, checks for
13534 bugs similar to 13085. Patch by "teor".
13535 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13536 - Integrate the ntor, backtrace, and zero-length keys tests into the
13537 automake test suite. Closes ticket 15344.
13538 - Remove assertions during builds to determine Tor's test coverage.
13539 We don't want to trigger these even in assertions, so including
13540 them artificially makes our branch coverage look worse than it is.
13541 This patch provides the new test-stem-full and coverage-html-full
13542 configure options. Implements ticket 15400.
13544 o Minor bugfixes (build):
13545 - Improve out-of-tree builds by making non-standard rules work and
13546 clean up additional files and directories. Fixes bug 15053; bugfix
13549 o Minor bugfixes (command-line interface):
13550 - When "--quiet" is provided along with "--validate-config", do not
13551 write anything to stdout on success. Fixes bug 14994; bugfix
13553 - When complaining about bad arguments to "--dump-config", use
13554 stderr, not stdout.
13556 o Minor bugfixes (configuration, unit tests):
13557 - Only add the default fallback directories when the DirAuthorities,
13558 AlternateDirAuthority, and FallbackDir directory config options
13559 are set to their defaults. The default fallback directory list is
13560 currently empty, this fix will only change tor's behavior when it
13561 has default fallback directories. Includes unit tests for
13562 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13563 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13565 o Minor bugfixes (correctness):
13566 - For correctness, avoid modifying a constant string in
13567 handle_control_postdescriptor. Fixes bug 15546; bugfix
13569 - Remove side-effects from tor_assert() calls. This was harmless,
13570 because we never disable assertions, but it is bad style and
13571 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13574 o Minor bugfixes (hidden service):
13575 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13576 a client authorized hidden service. Fixes bug 15823; bugfix
13578 - Remove an extraneous newline character from the end of hidden
13579 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13581 o Minor bugfixes (interface):
13582 - Print usage information for --dump-config when it is used without
13583 an argument. Also, fix the error message to use different wording
13584 and add newline at the end. Fixes bug 15541; bugfix
13587 o Minor bugfixes (logs):
13588 - When building Tor under Clang, do not include an extra set of
13589 parentheses in log messages that include function names. Fixes bug
13590 15269; bugfix on every released version of Tor when compiled with
13591 recent enough Clang.
13593 o Minor bugfixes (network):
13594 - When attempting to use fallback technique for network interface
13595 lookup, disregard loopback and multicast addresses since they are
13596 unsuitable for public communications.
13598 o Minor bugfixes (statistics):
13599 - Disregard the ConnDirectionStatistics torrc options when Tor is
13600 not a relay since in that mode of operation no sensible data is
13601 being collected and because Tor might run into measurement hiccups
13602 when running as a client for some time, then becoming a relay.
13603 Fixes bug 15604; bugfix on 0.2.2.35.
13605 o Minor bugfixes (test networks):
13606 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13607 determine if local/private addresses imply reachability. The
13608 previous fix used TestingTorNetwork, which implies
13609 ExtendAllowPrivateAddresses, but this excluded rare configurations
13610 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13611 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13612 issue discovered by CJ Ess.
13614 o Minor bugfixes (testing):
13615 - Check for matching value in server response in ntor_ref.py. Fixes
13616 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13618 - Set the severity correctly when testing
13619 get_interface_addresses_ifaddrs() and
13620 get_interface_addresses_win32(), so that the tests fail gracefully
13621 instead of triggering an assertion. Fixes bug 15759; bugfix on
13622 0.2.6.3-alpha. Reported by Nicolas Derive.
13624 o Code simplification and refactoring:
13625 - Move the hacky fallback code out of get_interface_address6() into
13626 separate function and get it covered with unit-tests. Resolves
13628 - Refactor hidden service client-side cache lookup to intelligently
13629 report its various failure cases, and disentangle failure cases
13630 involving a lack of introduction points. Closes ticket 14391.
13631 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13632 control over the output. Part of ticket 15652.
13635 - Improve the descriptions of statistics-related torrc options in
13636 the manpage to describe rationale and possible uses cases. Fixes
13638 - Improve the layout and formatting of ./configure --help messages.
13639 Closes ticket 15024. Patch from "cypherpunks".
13640 - Standardize on the term "server descriptor" in the manual page.
13641 Previously, we had used "router descriptor", "server descriptor",
13642 and "relay descriptor" interchangeably. Part of ticket 14987.
13645 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
13646 and always use the internal Base64 decoder. The internal decoder
13647 has been part of tor since 0.2.0.10-alpha, and no one should
13648 be using the OpenSSL one. Part of ticket 15652.
13649 - Remove the 'tor_strclear()' function; use memwipe() instead.
13650 Closes ticket 14922.
13652 o Removed features:
13653 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
13654 fingerprinting we now recommend pluggable transports; for forward-
13655 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
13656 - Remove the undocumented "--digests" command-line option. It
13657 complicated our build process, caused subtle build issues on
13658 multiple platforms, and is now redundant since we started
13659 including git version identifiers. Closes ticket 14742.
13660 - Tor no longer contains checks for ancient directory cache versions
13661 that didn't know about microdescriptors.
13662 - Tor no longer contains workarounds for stat files generated by
13663 super-old versions of Tor that didn't choose guards sensibly.
13666 Changes in version 0.2.4.27 - 2015-04-06
13667 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
13668 could be used by an attacker to crash hidden services, or crash clients
13669 visiting hidden services. Hidden services should upgrade as soon as
13670 possible; clients should upgrade whenever packages become available.
13672 This release also backports a simple improvement to make hidden
13673 services a bit less vulnerable to denial-of-service attacks.
13675 o Major bugfixes (security, hidden service):
13676 - Fix an issue that would allow a malicious client to trigger an
13677 assertion failure and halt a hidden service. Fixes bug 15600;
13678 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13679 - Fix a bug that could cause a client to crash with an assertion
13680 failure when parsing a malformed hidden service descriptor. Fixes
13681 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13683 o Minor features (DoS-resistance, hidden service):
13684 - Introduction points no longer allow multiple INTRODUCE1 cells to
13685 arrive on the same circuit. This should make it more expensive for
13686 attackers to overwhelm hidden services with introductions.
13687 Resolves ticket 15515.
13690 Changes in version 0.2.5.12 - 2015-04-06
13691 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
13692 could be used by an attacker to crash hidden services, or crash clients
13693 visiting hidden services. Hidden services should upgrade as soon as
13694 possible; clients should upgrade whenever packages become available.
13696 This release also backports a simple improvement to make hidden
13697 services a bit less vulnerable to denial-of-service attacks.
13699 o Major bugfixes (security, hidden service):
13700 - Fix an issue that would allow a malicious client to trigger an
13701 assertion failure and halt a hidden service. Fixes bug 15600;
13702 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13703 - Fix a bug that could cause a client to crash with an assertion
13704 failure when parsing a malformed hidden service descriptor. Fixes
13705 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13707 o Minor features (DoS-resistance, hidden service):
13708 - Introduction points no longer allow multiple INTRODUCE1 cells to
13709 arrive on the same circuit. This should make it more expensive for
13710 attackers to overwhelm hidden services with introductions.
13711 Resolves ticket 15515.
13714 Changes in version 0.2.6.7 - 2015-04-06
13715 Tor 0.2.6.7 fixes two security issues that could be used by an
13716 attacker to crash hidden services, or crash clients visiting hidden
13717 services. Hidden services should upgrade as soon as possible; clients
13718 should upgrade whenever packages become available.
13720 This release also contains two simple improvements to make hidden
13721 services a bit less vulnerable to denial-of-service attacks.
13723 o Major bugfixes (security, hidden service):
13724 - Fix an issue that would allow a malicious client to trigger an
13725 assertion failure and halt a hidden service. Fixes bug 15600;
13726 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13727 - Fix a bug that could cause a client to crash with an assertion
13728 failure when parsing a malformed hidden service descriptor. Fixes
13729 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13731 o Minor features (DoS-resistance, hidden service):
13732 - Introduction points no longer allow multiple INTRODUCE1 cells to
13733 arrive on the same circuit. This should make it more expensive for
13734 attackers to overwhelm hidden services with introductions.
13735 Resolves ticket 15515.
13736 - Decrease the amount of reattempts that a hidden service performs
13737 when its rendezvous circuits fail. This reduces the computational
13738 cost for running a hidden service under heavy load. Resolves
13742 Changes in version 0.2.6.6 - 2015-03-24
13743 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
13745 It adds numerous safety, security, correctness, and performance
13746 improvements. Client programs can be configured to use more kinds of
13747 sockets, AutomapHosts works better, the multithreading backend is
13748 improved, cell transmission is refactored, test coverage is much
13749 higher, more denial-of-service attacks are handled, guard selection is
13750 improved to handle long-term guards better, pluggable transports
13751 should work a bit better, and some annoying hidden service performance
13752 bugs should be addressed.
13754 o Minor bugfixes (portability):
13755 - Use the correct datatype in the SipHash-2-4 function to prevent
13756 compilers from assuming any sort of alignment. Fixes bug 15436;
13757 bugfix on 0.2.5.3-alpha.
13759 Changes in version 0.2.6.5-rc - 2015-03-18
13760 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
13761 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
13763 o Major bugfixes (client):
13764 - Avoid crashing when making certain configuration option changes on
13765 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
13768 o Major bugfixes (pluggable transports):
13769 - Initialize the extended OR Port authentication cookie before
13770 launching pluggable transports. This prevents a race condition
13771 that occurred when server-side pluggable transports would cache the
13772 authentication cookie before it has been (re)generated. Fixes bug
13773 15240; bugfix on 0.2.5.1-alpha.
13775 o Major bugfixes (portability):
13776 - Do not crash on startup when running on Solaris. Fixes a bug
13777 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
13780 o Minor features (heartbeat):
13781 - On relays, report how many connections we negotiated using each
13782 version of the Tor link protocols. This information will let us
13783 know if removing support for very old versions of the Tor
13784 protocols is harming the network. Closes ticket 15212.
13786 o Code simplification and refactoring:
13787 - Refactor main loop to extract the 'loop' part. This makes it
13788 easier to run Tor under Shadow. Closes ticket 15176.
13791 Changes in version 0.2.5.11 - 2015-03-17
13792 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
13794 It backports several bugfixes from the 0.2.6 branch, including a
13795 couple of medium-level security fixes for relays and exit nodes.
13796 It also updates the list of directory authorities.
13798 o Directory authority changes:
13799 - Remove turtles as a directory authority.
13800 - Add longclaw as a new (v3) directory authority. This implements
13801 ticket 13296. This keeps the directory authority count at 9.
13802 - The directory authority Faravahar has a new IP address. This
13803 closes ticket 14487.
13805 o Major bugfixes (crash, OSX, security):
13806 - Fix a remote denial-of-service opportunity caused by a bug in
13807 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13810 o Major bugfixes (relay, stability, possible security):
13811 - Fix a bug that could lead to a relay crashing with an assertion
13812 failure if a buffer of exactly the wrong layout was passed to
13813 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13814 0.2.0.10-alpha. Patch from 'cypherpunks'.
13815 - Do not assert if the 'data' pointer on a buffer is advanced to the
13816 very end of the buffer; log a BUG message instead. Only assert if
13817 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13819 o Major bugfixes (exit node stability):
13820 - Fix an assertion failure that could occur under high DNS load.
13821 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13822 diagnosed and fixed by "cypherpunks".
13824 o Major bugfixes (Linux seccomp2 sandbox):
13825 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13826 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13827 0.2.5.1-alpha. Patch from "sanic".
13829 o Minor features (controller):
13830 - New "GETINFO bw-event-cache" to get information about recent
13831 bandwidth events. Closes ticket 14128. Useful for controllers to
13832 get recent bandwidth history after the fix for ticket 13988.
13834 o Minor features (geoip):
13835 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13836 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13839 o Minor bugfixes (client, automapping):
13840 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
13841 no value follows the option. Fixes bug 14142; bugfix on
13842 0.2.4.7-alpha. Patch by "teor".
13843 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
13844 14195; bugfix on 0.1.0.1-rc.
13846 o Minor bugfixes (compilation):
13847 - Build without warnings with the stock OpenSSL srtp.h header, which
13848 has a duplicate declaration of SSL_get_selected_srtp_profile().
13849 Fixes bug 14220; this is OpenSSL's bug, not ours.
13851 o Minor bugfixes (directory authority):
13852 - Allow directory authorities to fetch more data from one another if
13853 they find themselves missing lots of votes. Previously, they had
13854 been bumping against the 10 MB queued data limit. Fixes bug 14261;
13855 bugfix on 0.1.2.5-alpha.
13856 - Enlarge the buffer to read bwauth generated files to avoid an
13857 issue when parsing the file in dirserv_read_measured_bandwidths().
13858 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
13860 o Minor bugfixes (statistics):
13861 - Increase period over which bandwidth observations are aggregated
13862 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
13864 o Minor bugfixes (preventative security, C safety):
13865 - When reading a hexadecimal, base-32, or base-64 encoded value from
13866 a string, always overwrite the whole output buffer. This prevents
13867 some bugs where we would look at (but fortunately, not reveal)
13868 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
13872 Changes in version 0.2.4.26 - 2015-03-17
13873 Tor 0.2.4.26 includes an updated list of directory authorities. It
13874 also backports a couple of stability and security bugfixes from 0.2.5
13877 o Directory authority changes:
13878 - Remove turtles as a directory authority.
13879 - Add longclaw as a new (v3) directory authority. This implements
13880 ticket 13296. This keeps the directory authority count at 9.
13881 - The directory authority Faravahar has a new IP address. This
13882 closes ticket 14487.
13884 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
13885 - Fix an assertion failure that could occur under high DNS load.
13886 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
13887 diagnosed and fixed by "cypherpunks".
13889 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
13890 - Fix a bug that could lead to a relay crashing with an assertion
13891 failure if a buffer of exactly the wrong layout was passed to
13892 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13893 0.2.0.10-alpha. Patch from 'cypherpunks'.
13894 - Do not assert if the 'data' pointer on a buffer is advanced to the
13895 very end of the buffer; log a BUG message instead. Only assert if
13896 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13898 o Minor features (geoip):
13899 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13900 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13903 Changes in version 0.2.6.4-rc - 2015-03-09
13904 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
13905 attacker might be able to use in order to crash certain Tor
13906 directories. It also resolves some minor issues left over from, or
13907 introduced in, Tor 0.2.6.3-alpha or earlier.
13909 o Major bugfixes (crash, OSX, security):
13910 - Fix a remote denial-of-service opportunity caused by a bug in
13911 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
13914 o Major bugfixes (relay, stability, possible security):
13915 - Fix a bug that could lead to a relay crashing with an assertion
13916 failure if a buffer of exactly the wrong layout is passed to
13917 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
13918 0.2.0.10-alpha. Patch from "cypherpunks".
13919 - Do not assert if the 'data' pointer on a buffer is advanced to the
13920 very end of the buffer; log a BUG message instead. Only assert if
13921 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
13923 o Major bugfixes (FreeBSD IPFW transparent proxy):
13924 - Fix address detection with FreeBSD transparent proxies, when
13925 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
13928 o Major bugfixes (Linux seccomp2 sandbox):
13929 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
13930 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
13932 - Allow AF_UNIX hidden services to be used with the seccomp2
13933 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
13934 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
13935 crash during attempts to call wait4. Fixes bug 15088; bugfix on
13936 0.2.5.1-alpha. Patch from "sanic".
13938 o Minor features (controller):
13939 - Messages about problems in the bootstrap process now include
13940 information about the server we were trying to connect to when we
13941 noticed the problem. Closes ticket 15006.
13943 o Minor features (geoip):
13944 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
13945 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
13948 o Minor features (logs):
13949 - Quiet some log messages in the heartbeat and at startup. Closes
13952 o Minor bugfixes (certificate handling):
13953 - If an authority operator accidentally makes a signing certificate
13954 with a future publication time, do not discard its real signing
13955 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
13956 - Remove any old authority certificates that have been superseded
13957 for at least two days. Previously, we would keep superseded
13958 certificates until they expired, if they were published close in
13959 time to the certificate that superseded them. Fixes bug 11454;
13960 bugfix on 0.2.1.8-alpha.
13962 o Minor bugfixes (compilation):
13963 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
13965 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
13968 o Minor bugfixes (testing):
13969 - Fix endianness issues in unit test for resolve_my_address() to
13970 have it pass on big endian systems. Fixes bug 14980; bugfix on
13972 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
13973 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
13974 - When running the new 'make test-stem' target, use the configured
13975 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
13976 from "cypherpunks".
13977 - When running the zero-length-keys tests, do not use the default
13978 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
13981 o Directory authority IP change:
13982 - The directory authority Faravahar has a new IP address. This
13983 closes ticket 14487.
13986 - Remove some lingering dead code that once supported mempools.
13987 Mempools were disabled by default in 0.2.5, and removed entirely
13988 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
13992 Changes in version 0.2.6.3-alpha - 2015-02-19
13993 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
13994 the 0.2.6.x series. It introduces support for more kinds of sockets,
13995 makes it harder to accidentally run an exit, improves our
13996 multithreading backend, incorporates several fixes for the
13997 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
13999 If no major regressions or security holes are found in this version,
14000 the next version will be a release candidate.
14002 o Deprecated versions:
14003 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14004 advertise themselves on the network. Closes ticket 13555.
14006 o Major features (security, unix domain sockets):
14007 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14008 applications can reach Tor without having to create AF_INET or
14009 AF_INET6 sockets, meaning they can completely disable their
14010 ability to make non-Tor network connections. To create a socket of
14011 this type, use "SocksPort unix:/path/to/socket". Implements
14013 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14014 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14015 Implements ticket 11485.
14017 o Major features (changed defaults):
14018 - Prevent relay operators from unintentionally running exits: When a
14019 relay is configured as an exit node, we now warn the user unless
14020 the "ExitRelay" option is set to 1. We warn even more loudly if
14021 the relay is configured with the default exit policy, since this
14022 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14023 stops Tor from running as an exit relay. Closes ticket 10067.
14025 o Major features (directory system):
14026 - When downloading server- or microdescriptors from a directory
14027 server, we no longer launch multiple simultaneous requests to the
14028 same server. This reduces load on the directory servers,
14029 especially when directory guards are in use. Closes ticket 9969.
14030 - When downloading server- or microdescriptors over a tunneled
14031 connection, do not limit the length of our requests to what the
14032 Squid proxy is willing to handle. Part of ticket 9969.
14033 - Authorities can now vote on the correct digests and latest
14034 versions for different software packages. This allows packages
14035 that include Tor to use the Tor authority system as a way to get
14036 notified of updates and their correct digests. Implements proposal
14037 227. Closes ticket 10395.
14039 o Major features (guards):
14040 - Introduce the Guardfraction feature to improves load balancing on
14041 guard nodes. Specifically, it aims to reduce the traffic gap that
14042 guard nodes experience when they first get the Guard flag. This is
14043 a required step if we want to increase the guard lifetime to 9
14044 months or greater. Closes ticket 9321.
14046 o Major features (performance):
14047 - Make the CPU worker implementation more efficient by avoiding the
14048 kernel and lengthening pipelines. The original implementation used
14049 sockets to transfer data from the main thread to the workers, and
14050 didn't allow any thread to be assigned more than a single piece of
14051 work at once. The new implementation avoids communications
14052 overhead by making requests in shared memory, avoiding kernel IO
14053 where possible, and keeping more requests in flight at once.
14054 Implements ticket 9682.
14056 o Major features (relay):
14057 - Raise the minimum acceptable configured bandwidth rate for bridges
14058 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14059 20 KiB/sec.) Closes ticket 13822.
14061 o Major bugfixes (exit node stability):
14062 - Fix an assertion failure that could occur under high DNS load.
14063 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14064 diagnosed and fixed by "cypherpunks".
14066 o Major bugfixes (mixed relay-client operation):
14067 - When running as a relay and client at the same time (not
14068 recommended), if we decide not to use a new guard because we want
14069 to retry older guards, only close the locally-originating circuits
14070 passing through that guard. Previously we would close all the
14071 circuits through that guard. Fixes bug 9819; bugfix on
14072 0.2.1.1-alpha. Reported by "skruffy".
14074 o Minor features (build):
14075 - New --disable-system-torrc compile-time option to prevent Tor from
14076 looking for the system-wide torrc or torrc-defaults files.
14077 Resolves ticket 13037.
14079 o Minor features (controller):
14080 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14081 events so controllers can observe circuit isolation inputs. Closes
14083 - ControlPort now supports the unix:/path/to/socket syntax as an
14084 alternative to the ControlSocket option, for consistency with
14085 SocksPort and HiddenServicePort. Closes ticket 14451.
14086 - New "GETINFO bw-event-cache" to get information about recent
14087 bandwidth events. Closes ticket 14128. Useful for controllers to
14088 get recent bandwidth history after the fix for ticket 13988.
14090 o Minor features (Denial of service resistance):
14091 - Count the total number of bytes used storing hidden service
14092 descriptors against the value of MaxMemInQueues. If we're low on
14093 memory, and more than 20% of our memory is used holding hidden
14094 service descriptors, free them until no more than 10% of our
14095 memory holds hidden service descriptors. Free the least recently
14096 fetched descriptors first. Resolves ticket 13806.
14097 - When we have recently been under memory pressure (over 3/4 of
14098 MaxMemInQueues is allocated), then allocate smaller zlib objects
14099 for small requests. Closes ticket 11791.
14101 o Minor features (geoip):
14102 - Update geoip and geoip6 files to the January 7 2015 Maxmind
14103 GeoLite2 Country database.
14105 o Minor features (guard nodes):
14106 - Reduce the time delay before saving guard status to disk from 10
14107 minutes to 30 seconds (or from one hour to 10 minutes if
14108 AvoidDiskWrites is set). Closes ticket 12485.
14110 o Minor features (hidden service):
14111 - Make Sybil attacks against hidden services harder by changing the
14112 minimum time required to get the HSDir flag from 25 hours up to 96
14113 hours. Addresses ticket 14149.
14114 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14115 services to disable the anti-scanning feature introduced in
14116 0.2.6.2-alpha. With this option not set, a connection to an
14117 unlisted port closes the circuit. With this option set, only a
14118 RELAY_DONE cell is sent. Closes ticket 14084.
14120 o Minor features (interface):
14121 - Implement "-f -" command-line option to read torrc configuration
14122 from standard input, if you don't want to store the torrc file in
14123 the file system. Implements feature 13865.
14125 o Minor features (logging):
14126 - Add a count of unique clients to the bridge heartbeat message.
14127 Resolves ticket 6852.
14128 - Suppress "router info incompatible with extra info" message when
14129 reading extrainfo documents from cache. (This message got loud
14130 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14132 - Elevate hidden service authorized-client message from DEBUG to
14133 INFO. Closes ticket 14015.
14135 o Minor features (stability):
14136 - Add assertions in our hash-table iteration code to check for
14137 corrupted values that could cause infinite loops. Closes
14140 o Minor features (systemd):
14141 - Various improvements and modernizations in systemd hardening
14142 support. Closes ticket 13805. Patch from Craig Andrews.
14144 o Minor features (testing networks):
14145 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14146 and the default on a testing network to 2 minutes. Drop the
14147 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14148 keep the default on a testing network at 30 seconds. This reduces
14149 HS bootstrap time to around 25 seconds. Also, change the default
14150 time in test-network.sh to match. Closes ticket 13401. Patch
14152 - Create TestingDirAuthVoteHSDir to correspond to
14153 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14154 HSDir flag for the listed relays regardless of uptime or ORPort
14155 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14156 Partial implementation for ticket 14067. Patch by "teor".
14158 o Minor features (tor2web mode):
14159 - Introduce the config option Tor2webRendezvousPoints, which allows
14160 clients in Tor2webMode to select a specific Rendezvous Point to be
14161 used in HS circuits. This might allow better performance for
14162 Tor2Web nodes. Implements ticket 12844.
14164 o Minor bugfixes (client DNS):
14165 - Report the correct cached DNS expiration times on SOCKS port or in
14166 DNS replies. Previously, we would report everything as "never
14167 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14168 - Avoid a small memory leak when we find a cached answer for a
14169 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14170 side DNS caching is off by default, and is not recommended.) Fixes
14171 bug 14259; bugfix on 0.2.0.1-alpha.
14173 o Minor bugfixes (client, automapping):
14174 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14175 no value follows the option. Fixes bug 14142; bugfix on
14176 0.2.4.7-alpha. Patch by "teor".
14177 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14178 14195; bugfix on 0.1.0.1-rc.
14179 - Prevent changes to other options from removing the wildcard value
14180 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14182 - Allow MapAddress and AutomapHostsOnResolve to work together when
14183 an address is mapped into another address type (like .onion) that
14184 must be automapped at resolve time. Fixes bug 7555; bugfix
14187 o Minor bugfixes (client, bridges):
14188 - When we are using bridges and we had a network connectivity
14189 problem, only retry connecting to our currently configured
14190 bridges, not all bridges we know about and remember using. Fixes
14191 bug 14216; bugfix on 0.2.2.17-alpha.
14193 o Minor bugfixes (client, IPv6):
14194 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14195 flag is not set; and not because the NoIPv4Traffic flag was set.
14196 Previously we'd looked at the NoIPv4Traffic flag for both types of
14197 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14199 o Minor bugfixes (compilation):
14200 - The address of an array in the middle of a structure will always
14201 be non-NULL. clang recognises this and complains. Disable the
14202 tautologous and redundant check to silence this warning. Fixes bug
14203 14001; bugfix on 0.2.1.2-alpha.
14204 - Avoid warnings when building with systemd 209 or later. Fixes bug
14205 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
14206 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14207 Addresses ticket 14188.
14208 - Build without warnings with the stock OpenSSL srtp.h header, which
14209 has a duplicate declaration of SSL_get_selected_srtp_profile().
14210 Fixes bug 14220; this is OpenSSL's bug, not ours.
14211 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14212 is not enabled at compile time. Previously, this code was included
14213 in a disabled state. See discussion on ticket 12844.
14214 - Remove the --disable-threads configure option again. It was
14215 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
14216 14819; bugfix on 0.2.6.2-alpha.
14218 o Minor bugfixes (controller):
14219 - Report "down" in response to the "GETINFO entry-guards" command
14220 when relays are down with an unreachable_since value. Previously,
14221 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14222 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14223 14116; bugfix on 0.2.2.9-alpha.
14224 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
14225 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
14227 o Minor bugfixes (directory authority):
14228 - Allow directory authorities to fetch more data from one another if
14229 they find themselves missing lots of votes. Previously, they had
14230 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14231 bugfix on 0.1.2.5-alpha.
14232 - Do not attempt to download extrainfo documents which we will be
14233 unable to validate with a matching server descriptor. Fixes bug
14234 13762; bugfix on 0.2.0.1-alpha.
14235 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14236 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14237 - Enlarge the buffer to read bwauth generated files to avoid an
14238 issue when parsing the file in dirserv_read_measured_bandwidths().
14239 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14241 o Minor bugfixes (file handling):
14242 - Stop failing when key files are zero-length. Instead, generate new
14243 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14244 on all versions of Tor. Patch by "teor".
14245 - Stop generating a fresh .old RSA onion key file when the .old file
14246 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14247 - Avoid overwriting .old key files with empty key files.
14248 - Skip loading zero-length extrainfo store, router store, stats,
14249 state, and key files.
14250 - Avoid crashing when trying to reload a torrc specified as a
14251 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14254 o Minor bugfixes (hidden services):
14255 - Close the introduction circuit when we have no more usable intro
14256 points, instead of waiting for it to time out. This also ensures
14257 that no follow-up HS descriptor fetch is triggered when the
14258 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14259 - When fetching a hidden service descriptor for a down service that
14260 was recently up, do not keep refetching until we try the same
14261 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14262 - Successfully launch Tor with a nonexistent hidden service
14263 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
14264 14106; bugfix on 0.2.6.2-alpha.
14266 o Minor bugfixes (logging):
14267 - Avoid crashing when there are more log domains than entries in
14268 domain_list. Bugfix on 0.2.3.1-alpha.
14269 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
14271 - Don't log messages to stdout twice when starting up. Fixes bug
14272 13993; bugfix on 0.2.6.1-alpha.
14274 o Minor bugfixes (parsing):
14275 - Stop accepting milliseconds (or other junk) at the end of
14276 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14277 - Support two-number and three-number version numbers correctly, in
14278 case we change the Tor versioning system in the future. Fixes bug
14279 13661; bugfix on 0.0.8pre1.
14281 o Minor bugfixes (path counting):
14282 - When deciding whether the consensus lists any exit nodes, count
14283 the number listed in the consensus, not the number we have
14284 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
14285 - When deciding whether we have any exit nodes, only examine
14286 ExitNodes when the ExitNodes option is actually set. Fixes part of
14287 bug 14918; bugfix on 0.2.6.2-alpha.
14288 - Get rid of redundant and possibly scary warnings that we are
14289 missing directory information while we bootstrap. Fixes part of
14290 bug 14918; bugfix on 0.2.6.2-alpha.
14292 o Minor bugfixes (portability):
14293 - Fix the ioctl()-based network interface lookup code so that it
14294 will work on systems that have variable-length struct ifreq, for
14296 - Fix scheduler compilation on targets where char is unsigned. Fixes
14297 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
14299 o Minor bugfixes (sandbox):
14300 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14301 Previously, glibc would try to write them to /dev/tty, and the
14302 sandbox would trap the call and make Tor exit prematurely. Fixes
14303 bug 14759; bugfix on 0.2.5.1-alpha.
14305 o Minor bugfixes (shutdown):
14306 - When shutting down, always call event_del() on lingering read or
14307 write events before freeing them. Otherwise, we risk double-frees
14308 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
14311 o Minor bugfixes (small memory leaks):
14312 - Avoid leaking memory when using IPv6 virtual address mappings.
14313 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
14316 o Minor bugfixes (statistics):
14317 - Increase period over which bandwidth observations are aggregated
14318 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14320 o Minor bugfixes (systemd support):
14321 - Fix detection and operation of systemd watchdog. Fixes part of bug
14322 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
14323 - Run correctly under systemd with the RunAsDaemon option set. Fixes
14324 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
14325 - Inform the systemd supervisor about more changes in the Tor
14326 process status. Implements part of ticket 14141. Patch from
14328 - Cause the "--disable-systemd" option to actually disable systemd
14329 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
14332 o Minor bugfixes (TLS):
14333 - Check more thoroughly throughout the TLS code for possible
14334 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
14336 o Minor bugfixes (transparent proxy):
14337 - Use getsockname, not getsockopt, to retrieve the address for a
14338 TPROXY-redirected connection. Fixes bug 13796; bugfix
14341 o Code simplification and refactoring:
14342 - Move fields related to isolating and configuring client ports into
14343 a shared structure. Previously, they were duplicated across
14344 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
14345 to copy them correctly had been the cause of at least one bug in
14346 the past. Closes ticket 8546.
14347 - Refactor the get_interface_addresses_raw() doom-function into
14348 multiple smaller and simpler subfunctions. Cover the resulting
14349 subfunctions with unit-tests. Fixes a significant portion of
14351 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
14352 only for version <= 0.2.2.24 which is now deprecated. Closes
14354 - Remove a test for a long-defunct broken version-one
14358 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
14359 for writing the OpenBSD-specific tips. Resolves ticket 13702.
14360 - Make the tor-resolve documentation match its help string and its
14361 options. Resolves part of ticket 14325.
14362 - Log a more useful error message from tor-resolve when failing to
14363 look up a hidden service address. Resolves part of ticket 14325.
14365 o Downgraded warnings:
14366 - Don't warn when we've attempted to contact a relay using the wrong
14367 ntor onion key. Closes ticket 9635.
14369 o Removed features:
14370 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
14371 longer silently accepted as an alias for "ExitNodes".
14372 - The --enable-mempool and --enable-buf-freelists options, which
14373 were originally created to work around bad malloc implementations,
14374 no longer exist. They were off-by-default in 0.2.5. Closes
14378 - Make the checkdir/perms test complete successfully even if the
14379 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
14380 - Test that tor does not fail when key files are zero-length. Check
14381 that tor generates new keys, and overwrites the empty key files.
14382 - Test that tor generates new keys when keys are missing
14383 (existing behavior).
14384 - Test that tor does not overwrite key files that already contain
14385 data (existing behavior). Tests bug 13111. Patch by "teor".
14386 - New "make test-stem" target to run stem integration tests.
14387 Requires that the "STEM_SOURCE_DIR" environment variable be set.
14388 Closes ticket 14107.
14389 - Make the test_cmdline_args.py script work correctly on Windows.
14390 Patch from Gisle Vanem.
14391 - Move the slower unit tests into a new "./src/test/test-slow"
14392 binary that can be run independently of the other tests. Closes
14394 - Avoid undefined behavior when sampling huge values from the
14395 Laplace distribution. This made unittests fail on Raspberry Pi.
14396 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
14399 Changes in version 0.2.6.2-alpha - 2014-12-31
14400 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
14401 It introduces a major new backend for deciding when to send cells on
14402 channels, which should lead down the road to big performance
14403 increases. It contains security and statistics features for better
14404 work on hidden services, and numerous bugfixes.
14406 This release contains many new unit tests, along with major
14407 performance improvements for running testing networks using Chutney.
14408 Thanks to a series of patches contributed by "teor", testing networks
14409 should now bootstrap in seconds, rather than minutes.
14411 o Major features (relay, infrastructure):
14412 - Complete revision of the code that relays use to decide which cell
14413 to send next. Formerly, we selected the best circuit to write on
14414 each channel, but we didn't select among channels in any
14415 sophisticated way. Now, we choose the best circuits globally from
14416 among those whose channels are ready to deliver traffic.
14418 This patch implements a new inter-cmux comparison API, a global
14419 high/low watermark mechanism and a global scheduler loop for
14420 transmission prioritization across all channels as well as among
14421 circuits on one channel. This schedule is currently tuned to
14422 (tolerantly) avoid making changes in network performance, but it
14423 should form the basis for major circuit performance increases in
14424 the future. Code by Andrea; tuning by Rob Jansen; implements
14427 o Major features (hidden services):
14428 - Make HS port scanning more difficult by immediately closing the
14429 circuit when a user attempts to connect to a nonexistent port.
14430 Closes ticket 13667.
14431 - Add a HiddenServiceStatistics option that allows Tor relays to
14432 gather and publish statistics about the overall size and volume of
14433 hidden service usage. Specifically, when this option is turned on,
14434 an HSDir will publish an approximate number of hidden services
14435 that have published descriptors to it the past 24 hours. Also, if
14436 a relay has acted as a hidden service rendezvous point, it will
14437 publish the approximate amount of rendezvous cells it has relayed
14438 the past 24 hours. The statistics themselves are obfuscated so
14439 that the exact values cannot be derived. For more details see
14440 proposal 238, "Better hidden service stats from Tor relays". This
14441 feature is currently disabled by default. Implements feature 13192.
14443 o Major bugfixes (client, automap):
14444 - Repair automapping with IPv6 addresses. This automapping should
14445 have worked previously, but one piece of debugging code that we
14446 inserted to detect a regression actually caused the regression to
14447 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14448 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14451 o Major bugfixes (hidden services):
14452 - When closing an introduction circuit that was opened in parallel
14453 with others, don't mark the introduction point as unreachable.
14454 Previously, the first successful connection to an introduction
14455 point would make the other introduction points get marked as
14456 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14458 o Directory authority changes:
14459 - Remove turtles as a directory authority.
14460 - Add longclaw as a new (v3) directory authority. This implements
14461 ticket 13296. This keeps the directory authority count at 9.
14463 o Major removed features:
14464 - Tor clients no longer support connecting to hidden services
14465 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14466 option has been removed. (There shouldn't be any hidden services
14467 running these versions on the network.) Closes ticket 7803.
14469 o Minor features (client):
14470 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14471 is enabled, reject requests with IP addresses as hostnames.
14472 Resolves ticket 13315.
14474 o Minor features (controller):
14475 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14476 write an unscheduled heartbeat message to the log. Implements
14479 o Minor features (geoip):
14480 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14483 o Minor features (hidden services):
14484 - When re-enabling the network, don't try to build introduction
14485 circuits until we have successfully built a circuit. This makes
14486 hidden services come up faster when the network is re-enabled.
14487 Patch from "akwizgran". Closes ticket 13447.
14488 - When we fail to retrieve a hidden service descriptor, send the
14489 controller an "HS_DESC FAILED" controller event. Implements
14491 - New HiddenServiceDirGroupReadable option to cause hidden service
14492 directories and hostname files to be created group-readable. Patch
14493 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14495 o Minor features (systemd):
14496 - Where supported, when running with systemd, report successful
14497 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14498 - When running with systemd, support systemd watchdog messages. Part
14499 of ticket 11016. Patch by Michael Scherer.
14501 o Minor features (transparent proxy):
14502 - Update the transparent proxy option checks to allow for both ipfw
14503 and pf on OS X. Closes ticket 14002.
14504 - Use the correct option when using IPv6 with transparent proxy
14505 support on Linux. Resolves 13808. Patch by Francisco Blas
14508 o Minor bugfixes (preventative security, C safety):
14509 - When reading a hexadecimal, base-32, or base-64 encoded value from
14510 a string, always overwrite the whole output buffer. This prevents
14511 some bugs where we would look at (but fortunately, not reveal)
14512 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14514 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14515 just the part that's used. This makes it harder for data leak bugs
14516 to occur in the event of other programming failures. Resolves
14519 o Minor bugfixes (client, microdescriptors):
14520 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14521 computing which microdescriptors to download. This keeps us from
14522 erroneous download behavior if two microdescriptor digests ever
14523 have the same first 160 bits. Fixes part of bug 13399; bugfix
14525 - Reset a router's status if its microdescriptor digest changes,
14526 even if the first 160 bits remain the same. Fixes part of bug
14527 13399; bugfix on 0.2.3.1-alpha.
14529 o Minor bugfixes (compilation):
14530 - Silence clang warnings under --enable-expensive-hardening,
14531 including implicit truncation of 64 bit values to 32 bit, const
14532 char assignment to self, tautological compare, and additional
14533 parentheses around equality tests. Fixes bug 13577; bugfix
14535 - Fix a clang warning about checking whether an address in the
14536 middle of a structure is NULL. Fixes bug 14001; bugfix
14539 o Minor bugfixes (hidden services):
14540 - Correctly send a controller event when we find that a rendezvous
14541 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14542 - Pre-check directory permissions for new hidden-services to avoid
14543 at least one case of "Bug: Acting on config options left us in a
14544 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14545 - When adding a new hidden service (for example, via SETCONF), Tor
14546 no longer congratulates the user for running a relay. Fixes bug
14547 13941; bugfix on 0.2.6.1-alpha.
14548 - When fetching hidden service descriptors, we now check not only
14549 for whether we got the hidden service we had in mind, but also
14550 whether we got the particular descriptors we wanted. This prevents
14551 a class of inefficient but annoying DoS attacks by hidden service
14552 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14555 o Minor bugfixes (Linux seccomp2 sandbox):
14556 - Make transparent proxy support work along with the seccomp2
14557 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14558 by Francisco Blas Izquierdo Riera.
14559 - Fix a memory leak in tor-resolve when running with the sandbox
14560 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14562 o Minor bugfixes (logging):
14563 - Downgrade warnings about RSA signature failures to info log level.
14564 Emit a warning when an extra info document is found incompatible
14565 with a corresponding router descriptor. Fixes bug 9812; bugfix
14567 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14568 correctly. Fixes bug 13701; bugfix on 0.0.6.
14570 o Minor bugfixes (misc):
14571 - Stop allowing invalid address patterns like "*/24" that contain
14572 both a wildcard address and a bit prefix length. This affects all
14573 our address-range parsing code. Fixes bug 7484; bugfix
14576 o Minor bugfixes (testing networks, fast startup):
14577 - Allow Tor to build circuits using a consensus with no exits. If
14578 the consensus has no exits (typical of a bootstrapping test
14579 network), allow Tor to build circuits once enough descriptors have
14580 been downloaded. This assists in bootstrapping a testing Tor
14581 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14583 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14584 header to directory servers. This allows us to obtain consensuses
14585 promptly when the consensus interval is very short. This assists
14586 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14587 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14588 - Stop assuming that private addresses are local when checking
14589 reachability in a TestingTorNetwork. Instead, when testing, assume
14590 all OR connections are remote. (This is necessary due to many test
14591 scenarios running all relays on localhost.) This assists in
14592 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14593 0.1.0.1-rc. Patch by "teor".
14594 - Avoid building exit circuits from a consensus with no exits. Now
14595 thanks to our fix for 13718, we accept a no-exit network as not
14596 wholly lost, but we need to remember not to try to build exit
14597 circuits on it. Closes ticket 13814; patch by "teor".
14598 - Stop requiring exits to have non-zero bandwithcapacity in a
14599 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14600 ignore exit bandwidthcapacity. This assists in bootstrapping a
14601 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14602 on 0.2.0.3-alpha. Patch by "teor".
14603 - Add "internal" to some bootstrap statuses when no exits are
14604 available. If the consensus does not contain Exits, Tor will only
14605 build internal circuits. In this case, relevant statuses will
14606 contain the word "internal" as indicated in the Tor control-
14607 spec.txt. When bootstrap completes, Tor will be ready to build
14608 internal circuits. If a future consensus contains Exits, exit
14609 circuits may become available. Fixes part of bug 13718; bugfix on
14610 0.2.4.10-alpha. Patch by "teor".
14611 - Decrease minimum consensus interval to 10 seconds when
14612 TestingTorNetwork is set, or 5 seconds for the first consensus.
14613 Fix assumptions throughout the code that assume larger intervals.
14614 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14616 - Avoid excluding guards from path building in minimal test
14617 networks, when we're in a test network and excluding guards would
14618 exclude all relays. This typically occurs in incredibly small tor
14619 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14620 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14622 o Code simplification and refactoring:
14623 - Stop using can_complete_circuits as a global variable; access it
14624 with a function instead.
14625 - Avoid using operators directly as macro arguments: this lets us
14626 apply coccinelle transformations to our codebase more directly.
14627 Closes ticket 13172.
14628 - Combine the functions used to parse ClientTransportPlugin and
14629 ServerTransportPlugin into a single function. Closes ticket 6456.
14630 - Add inline functions and convenience macros for inspecting channel
14631 state. Refactor the code to use convenience macros instead of
14632 checking channel state directly. Fixes issue 7356.
14633 - Document all members of was_router_added_t and rename
14634 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
14635 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
14636 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
14637 constant instead of hardcoded value. Fixes issue 13840.
14638 - Refactor our generic strmap and digestmap types into a single
14639 implementation, so that we can add a new digest256map
14643 - Document the bridge-authority-only 'networkstatus-bridges' file.
14644 Closes ticket 13713; patch from "tom".
14645 - Fix typo in PredictedPortsRelevanceTime option description in
14646 manpage. Resolves issue 13707.
14647 - Stop suggesting that users specify relays by nickname: it isn't a
14648 good idea. Also, properly cross-reference how to specify relays in
14649 all parts of manual documenting options that take a list of
14650 relays. Closes ticket 13381.
14651 - Clarify the HiddenServiceDir option description in manpage to make
14652 it clear that relative paths are taken with respect to the current
14653 working directory. Also clarify that this behavior is not
14654 guaranteed to remain indefinitely. Fixes issue 13913.
14657 - New tests for many parts of channel, relay, and circuitmux
14658 functionality. Code by Andrea; part of 9262.
14659 - New tests for parse_transport_line(). Part of ticket 6456.
14660 - In the unit tests, use chgrp() to change the group of the unit
14661 test temporary directory to the current user, so that the sticky
14662 bit doesn't interfere with tests that check directory groups.
14664 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
14668 Changes in version 0.2.6.1-alpha - 2014-10-30
14669 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
14670 includes numerous code cleanups and new tests, and fixes a large
14671 number of annoying bugs. Out-of-memory conditions are handled better
14672 than in 0.2.5, pluggable transports have improved proxy support, and
14673 clients now use optimistic data for contacting hidden services. Also,
14674 we are now more robust to changes in what we consider a parseable
14675 directory object, so that tightening restrictions does not have a risk
14676 of introducing infinite download loops.
14678 This is the first alpha release in a new series, so expect there to be
14679 bugs. Users who would rather test out a more stable branch should stay
14680 with 0.2.5.x for now.
14682 o New compiler and system requirements:
14683 - Tor 0.2.6.x requires that your compiler support more of the C99
14684 language standard than before. The 'configure' script now detects
14685 whether your compiler supports C99 mid-block declarations and
14686 designated initializers. If it does not, Tor will not compile.
14688 We may revisit this requirement if it turns out that a significant
14689 number of people need to build Tor with compilers that don't
14690 bother implementing a 15-year-old standard. Closes ticket 13233.
14691 - Tor no longer supports systems without threading support. When we
14692 began working on Tor, there were several systems that didn't have
14693 threads, or where the thread support wasn't able to run the
14694 threads of a single process on multiple CPUs. That no longer
14695 holds: every system where Tor needs to run well now has threading
14696 support. Resolves ticket 12439.
14698 o Removed platform support:
14699 - We no longer include special code to build on Windows CE; as far
14700 as we know, nobody has used Tor on Windows CE in a very long time.
14701 Closes ticket 11446.
14703 o Major features (bridges):
14704 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14705 transports if they are configured via the "TOR_PT_PROXY"
14706 environment variable. Implements proposal 232. Resolves
14709 o Major features (client performance, hidden services):
14710 - Allow clients to use optimistic data when connecting to a hidden
14711 service, which should remove a round-trip from hidden service
14712 initialization. See proposal 181 for details. Implements
14715 o Major features (directory system):
14716 - Upon receiving an unparseable directory object, if its digest
14717 matches what we expected, then don't try to download it again.
14718 Previously, when we got a descriptor we didn't like, we would keep
14719 trying to download it over and over. Closes ticket 11243.
14721 o Major features (sample torrc):
14722 - Add a new, infrequently-changed "torrc.minimal". This file is
14723 similar to torrc.sample, but it will change as infrequently as
14724 possible, for the benefit of users whose systems prompt them for
14725 intervention whenever a default configuration file is changed.
14726 Making this change allows us to update torrc.sample to be a more
14727 generally useful "sample torrc".
14729 o Major bugfixes (directory authorities):
14730 - Do not assign the HSDir flag to relays if they are not Valid, or
14731 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
14733 o Major bugfixes (directory bandwidth performance):
14734 - Don't flush the zlib buffer aggressively when compressing
14735 directory information for clients. This should save about 7% of
14736 the bandwidth currently used for compressed descriptors and
14737 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
14739 o Minor features (security, memory wiping):
14740 - Ensure we securely wipe keys from memory after
14741 crypto_digest_get_digest and init_curve25519_keypair_from_file
14742 have finished using them. Resolves ticket 13477.
14744 o Minor features (security, out-of-memory handling):
14745 - When handling an out-of-memory condition, allocate less memory for
14746 temporary data structures. Fixes issue 10115.
14747 - When handling an out-of-memory condition, consider more types of
14748 buffers, including those on directory connections, and zlib
14749 buffers. Resolves ticket 11792.
14752 - When identity keypair is generated for first time, log a
14753 congratulatory message that links to the new relay lifecycle
14754 document. Implements feature 10427.
14756 o Minor features (client):
14757 - Clients are now willing to send optimistic data (before they
14758 receive a 'connected' cell) to relays of any version. (Relays
14759 without support for optimistic data are no longer supported on the
14760 Tor network.) Resolves ticket 13153.
14762 o Minor features (directory authorities):
14763 - Don't list relays with a bandwidth estimate of 0 in the consensus.
14764 Implements a feature proposed during discussion of bug 13000.
14765 - In tor-gencert, report an error if the user provides the same
14766 argument more than once.
14767 - If a directory authority can't find a best consensus method in the
14768 votes that it holds, it now falls back to its favorite consensus
14769 method. Previously, it fell back to method 1. Neither of these is
14770 likely to get enough signatures, but "fall back to favorite"
14771 doesn't require us to maintain support an obsolete consensus
14772 method. Implements part of proposal 215.
14774 o Minor features (logging):
14775 - On Unix-like systems, you can now use named pipes as the target of
14776 the Log option, and other options that try to append to files.
14777 Closes ticket 12061. Patch from "carlo von lynX".
14778 - When opening a log file at startup, send it every log message that
14779 we generated between startup and opening it. Previously, log
14780 messages that were generated before opening the log file were only
14781 logged to stdout. Closes ticket 6938.
14782 - Add a TruncateLogFile option to overwrite logs instead of
14783 appending to them. Closes ticket 5583.
14785 o Minor features (portability, Solaris):
14786 - Threads are no longer disabled by default on Solaris; we believe
14787 that the versions of Solaris with broken threading support are all
14788 obsolete by now. Resolves ticket 9495.
14790 o Minor features (relay):
14791 - Re-check our address after we detect a changed IP address from
14792 getsockname(). This ensures that the controller command "GETINFO
14793 address" will report the correct value. Resolves ticket 11582.
14795 - A new AccountingRule option lets Relays set whether they'd like
14796 AccountingMax to be applied separately to inbound and outbound
14797 traffic, or applied to the sum of inbound and outbound traffic.
14798 Resolves ticket 961. Patch by "chobe".
14800 o Minor features (testing networks):
14801 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
14802 the "Exit" flag regardless of their uptime, bandwidth, or exit
14803 policy. TestingTorNetwork must be set for this option to have any
14804 effect. Previously, authorities would take up to 35 minutes to
14805 give nodes the Exit flag in a test network. Partially implements
14808 o Minor features (validation):
14809 - Check all date/time values passed to tor_timegm and
14810 parse_rfc1123_time for validity, taking leap years into account.
14811 Improves HTTP header validation. Implemented with bug 13476.
14812 - In correct_tm(), limit the range of values returned by system
14813 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
14814 This means we don't have to deal with negative or too large dates,
14815 even if a clock is wrong. Otherwise we might fail to read a file
14816 written by us which includes such a date. Fixes bug 13476.
14818 o Minor bugfixes (bridge clients):
14819 - When configured to use a bridge without an identity digest (not
14820 recommended), avoid launching an extra channel to it when
14821 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
14823 o Minor bugfixes (bridges):
14824 - When DisableNetwork is set, do not launch pluggable transport
14825 plugins, and if any are running, terminate them. Fixes bug 13213;
14826 bugfix on 0.2.3.6-alpha.
14828 o Minor bugfixes (C correctness):
14829 - Fix several instances of possible integer overflow/underflow/NaN.
14830 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
14832 - In circuit_build_times_calculate_timeout() in circuitstats.c,
14833 avoid dividing by zero in the pareto calculations. This traps
14834 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
14836 - Fix an integer overflow in format_time_interval(). Fixes bug
14837 13393; bugfix on 0.2.0.10-alpha.
14838 - Set the correct day of year value when the system's localtime(_r)
14839 or gmtime(_r) functions fail to set struct tm. Not externally
14840 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
14841 - Avoid unlikely signed integer overflow in tor_timegm on systems
14842 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
14844 o Minor bugfixes (client):
14845 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
14846 BadExit flag are not considered worthy candidates. Fixes bug
14847 13066; bugfix on 0.1.2.3-alpha.
14848 - Use the consensus schedule for downloading consensuses, and not
14849 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
14850 - Handle unsupported or malformed SOCKS5 requests properly by
14851 responding with the appropriate error message before closing the
14852 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
14854 o Minor bugfixes (client, torrc):
14855 - Stop modifying the value of our DirReqStatistics torrc option just
14856 because we're not a bridge or relay. This bug was causing Tor
14857 Browser users to write "DirReqStatistics 0" in their torrc files
14858 as if they had chosen to change the config. Fixes bug 4244; bugfix
14860 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
14861 that our options have changed every time we SIGHUP. Fixes bug
14862 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
14864 o Minor bugfixes (controller):
14865 - Return an error when the second or later arguments of the
14866 "setevents" controller command are invalid events. Previously we
14867 would return success while silently skipping invalid events. Fixes
14868 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
14870 o Minor bugfixes (directory system):
14871 - Always believe that v3 directory authorities serve extra-info
14872 documents, whether they advertise "caches-extra-info" or not.
14873 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14874 - When running as a v3 directory authority, advertise that you serve
14875 extra-info documents so that clients who want them can find them
14876 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
14877 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
14878 Previously, directories offering BRIDGE_DIRINFO and some other
14879 flag (i.e. microdescriptors or extrainfo) would be ignored when
14880 looking for bridges. Partially fixes bug 13163; bugfix
14883 o Minor bugfixes (networking):
14884 - Check for orconns and use connection_or_close_for_error() rather
14885 than connection_mark_for_close() directly in the getsockopt()
14886 failure case of connection_handle_write_impl(). Fixes bug 11302;
14887 bugfix on 0.2.4.4-alpha.
14889 o Minor bugfixes (relay):
14890 - When generating our family list, remove spaces from around the
14891 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
14892 - If our previous bandwidth estimate was 0 bytes, allow publishing a
14893 new relay descriptor immediately. Fixes bug 13000; bugfix
14896 o Minor bugfixes (testing networks):
14897 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
14898 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
14899 - Stop using the default authorities in networks which provide both
14900 AlternateDirAuthority and AlternateBridgeAuthority. Partially
14901 fixes bug 13163; bugfix on 0.2.0.13-alpha.
14903 o Minor bugfixes (testing):
14904 - Stop spawn test failures due to a race condition between the
14905 SIGCHLD handler updating the process status, and the test reading
14906 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
14908 o Minor bugfixes (testing, Windows):
14909 - Avoid passing an extra backslash when creating a temporary
14910 directory for running the unit tests on Windows. Fixes bug 12392;
14911 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
14913 o Minor bugfixes (windows):
14914 - Remove code to special-case handling of NTE_BAD_KEYSET when
14915 acquiring windows CryptoAPI context. This error can't actually
14916 occur for the parameters we're providing. Fixes bug 10816; bugfix
14919 o Minor bugfixes (zlib):
14920 - Avoid truncating a zlib stream when trying to finalize it with an
14921 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
14924 - Allow our configure script to build correctly with autoconf 2.62
14925 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
14926 - Improve the error message from ./configure to make it clear that
14927 when asciidoc has not been found, the user will have to either add
14928 --disable-asciidoc argument or install asciidoc. Resolves
14931 o Code simplification and refactoring:
14932 - Change the entry_is_live() function to take named bitfield
14933 elements instead of an unnamed list of booleans. Closes
14935 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
14936 Resolves ticket 12205.
14937 - Use calloc and reallocarray functions instead of multiply-
14938 then-malloc. This makes it less likely for us to fall victim to an
14939 integer overflow attack when allocating. Resolves ticket 12855.
14940 - Use the standard macro name SIZE_MAX, instead of our
14942 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
14943 functions which take them as arguments. Replace 0 with NO_DIRINFO
14944 in a function call for clarity. Seeks to prevent future issues
14946 - Avoid 4 null pointer errors under clang static analysis by using
14947 tor_assert() to prove that the pointers aren't null. Fixes
14949 - Rework the API of policies_parse_exit_policy() to use a bitmask to
14950 represent parsing options, instead of a confusing mess of
14951 booleans. Resolves ticket 8197.
14952 - Introduce a helper function to parse ExitPolicy in
14953 or_options_t structure.
14956 - Add a doc/TUNING document with tips for handling large numbers of
14957 TCP connections when running busy Tor relay. Update the warning
14958 message to point to this file when running out of sockets
14959 operating system is allowing to use simultaneously. Resolves
14962 o Removed features:
14963 - We no longer remind the user about configuration options that have
14964 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
14965 - Remove our old, non-weighted bandwidth-based node selection code.
14966 Previously, we used it as a fallback when we couldn't perform
14967 weighted bandwidth-based node selection. But that would only
14968 happen in the cases where we had no consensus, or when we had a
14969 consensus generated by buggy or ancient directory authorities. In
14970 either case, it's better to use the more modern, better maintained
14971 algorithm, with reasonable defaults for the weights. Closes
14973 - Remove the --disable-curve25519 configure option. Relays and
14974 clients now are required to support curve25519 and the
14976 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
14977 used to be deprecated synonyms for "StrictNodes", are now marked
14978 obsolete. Resolves ticket 12226.
14979 - Clients don't understand the BadDirectory flag in the consensus
14980 anymore, and ignore it.
14983 - Refactor the function that chooses guard nodes so that it can more
14984 easily be tested; write some tests for it.
14985 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
14986 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
14987 - Create unit tests for format_time_interval(). With bug 13393.
14988 - Add unit tests for tor_timegm signed overflow, tor_timegm and
14989 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
14990 tests (visible) fixes in bug 13476.
14991 - Add a "coverage-html" make target to generate HTML-visualized
14992 coverage results when building with --enable-coverage. (Requires
14993 lcov.) Patch from Kevin Murray.
14994 - Enable the backtrace handler (where supported) when running the
14996 - Revise all unit tests that used the legacy test_* macros to
14997 instead use the recommended tt_* macros. This patch was generated
14998 with coccinelle, to avoid manual errors. Closes ticket 13119.
15000 o Distribution (systemd):
15001 - systemd unit file: only allow tor to write to /var/lib/tor and
15002 /var/log/tor. The rest of the filesystem is accessible for reading
15003 only. Patch by intrigeri; resolves ticket 12751.
15004 - systemd unit file: ensure that the process and all its children
15005 can never gain new privileges. Patch by intrigeri; resolves
15007 - systemd unit file: set up /var/run/tor as writable for the Tor
15008 service. Patch by intrigeri; resolves ticket 13196.
15010 o Removed features (directory authorities):
15011 - Remove code that prevented authorities from listing Tor relays
15012 affected by CVE-2011-2769 as guards. These relays are already
15013 rejected altogether due to the minimum version requirement of
15014 0.2.3.16-alpha. Closes ticket 13152.
15015 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15016 the fingerprints file (approved-routers) has been deprecated.
15017 - Directory authorities do not support being Naming dirauths anymore.
15018 The "NamingAuthoritativeDir" config option is now obsolete.
15019 - Directory authorities do not support giving out the BadDirectory
15021 - Directory authorities no longer advertise or support consensus
15022 methods 1 through 12 inclusive. These consensus methods were
15023 obsolete and/or insecure: maintaining the ability to support them
15024 served no good purpose. Implements part of proposal 215; closes
15027 o Testing (test-network.sh):
15028 - Stop using "echo -n", as some shells' built-in echo doesn't
15029 support "-n". Instead, use "/bin/echo -n". Partially fixes
15031 - Stop an apparent test-network hang when used with make -j2. Fixes
15033 - Add a --delay option to test-network.sh, which configures the
15034 delay before the chutney network tests for data transmission.
15035 Partially implements ticket 13161.
15038 Changes in version 0.2.5.10 - 2014-10-24
15039 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15041 It adds several new security features, including improved
15042 denial-of-service resistance for relays, new compiler hardening
15043 options, and a system-call sandbox for hardened installations on Linux
15044 (requires seccomp2). The controller protocol has several new features,
15045 resolving IPv6 addresses should work better than before, and relays
15046 should be a little more CPU-efficient. We've added support for more
15047 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15048 system and testing infrastructure to allow unit testing of more parts
15049 of the Tor codebase. Finally, we've addressed several nagging pluggable
15050 transport usability issues, and included numerous other small bugfixes
15051 and features mentioned below.
15053 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15054 have accumulated many known flaws; everyone should upgrade.
15056 o Deprecated versions:
15057 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15058 attention for some while.
15061 Changes in version 0.2.5.9-rc - 2014-10-20
15062 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
15063 series. It disables SSL3 in response to the recent "POODLE" attack
15064 (even though POODLE does not affect Tor). It also works around a crash
15065 bug caused by some operating systems' response to the "POODLE" attack
15066 (which does affect Tor). It also contains a few miscellaneous fixes.
15068 o Major security fixes:
15069 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15070 today support TLS 1.0 or later, so we can safely turn off support
15071 for this old (and insecure) protocol. Fixes bug 13426.
15073 o Major bugfixes (openssl bug workaround):
15074 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15075 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15076 13471. This is a workaround for an OpenSSL bug.
15079 - Disable the sandbox name resolver cache when running tor-resolve:
15080 tor-resolve doesn't use the sandbox code, and turning it on was
15081 breaking attempts to do tor-resolve on a non-default server on
15082 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
15084 o Compilation fixes:
15085 - Build and run correctly on systems like OpenBSD-current that have
15086 patched OpenSSL to remove get_cipher_by_char and/or its
15087 implementations. Fixes issue 13325.
15089 o Downgraded warnings:
15090 - Downgrade the severity of the 'unexpected sendme cell from client'
15091 from 'warn' to 'protocol warning'. Closes ticket 8093.
15094 Changes in version 0.2.4.25 - 2014-10-20
15095 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
15096 (even though POODLE does not affect Tor). It also works around a crash
15097 bug caused by some operating systems' response to the "POODLE" attack
15098 (which does affect Tor).
15100 o Major security fixes (also in 0.2.5.9-rc):
15101 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15102 today support TLS 1.0 or later, so we can safely turn off support
15103 for this old (and insecure) protocol. Fixes bug 13426.
15105 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
15106 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15107 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15108 13471. This is a workaround for an OpenSSL bug.
15111 Changes in version 0.2.5.8-rc - 2014-09-22
15112 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
15113 series. It fixes a bug that affects consistency and speed when
15114 connecting to hidden services, and it updates the location of one of
15115 the directory authorities.
15118 - Clients now send the correct address for their chosen rendezvous
15119 point when trying to access a hidden service. They used to send
15120 the wrong address, which would still work some of the time because
15121 they also sent the identity digest of the rendezvous point, and if
15122 the hidden service happened to try connecting to the rendezvous
15123 point from a relay that already had a connection open to it,
15124 the relay would reuse that connection. Now connections to hidden
15125 services should be more robust and faster. Also, this bug meant
15126 that clients were leaking to the hidden service whether they were
15127 on a little-endian (common) or big-endian (rare) system, which for
15128 some users might have reduced their anonymity. Fixes bug 13151;
15129 bugfix on 0.2.1.5-alpha.
15131 o Directory authority changes:
15132 - Change IP address for gabelmoo (v3 directory authority).
15135 Changes in version 0.2.4.24 - 2014-09-22
15136 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
15137 connecting to hidden services, and it updates the location of one of
15138 the directory authorities.
15141 - Clients now send the correct address for their chosen rendezvous
15142 point when trying to access a hidden service. They used to send
15143 the wrong address, which would still work some of the time because
15144 they also sent the identity digest of the rendezvous point, and if
15145 the hidden service happened to try connecting to the rendezvous
15146 point from a relay that already had a connection open to it,
15147 the relay would reuse that connection. Now connections to hidden
15148 services should be more robust and faster. Also, this bug meant
15149 that clients were leaking to the hidden service whether they were
15150 on a little-endian (common) or big-endian (rare) system, which for
15151 some users might have reduced their anonymity. Fixes bug 13151;
15152 bugfix on 0.2.1.5-alpha.
15154 o Directory authority changes:
15155 - Change IP address for gabelmoo (v3 directory authority).
15157 o Minor features (geoip):
15158 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15162 Changes in version 0.2.5.7-rc - 2014-09-11
15163 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
15164 release series, and some long-standing bugs related to ORPort reachability
15165 testing and failure to send CREATE cells. It is the first release
15166 candidate for the Tor 0.2.5.x series.
15168 o Major bugfixes (client, startup):
15169 - Start making circuits as soon as DisabledNetwork is turned off.
15170 When Tor started with DisabledNetwork set, it would correctly
15171 conclude that it shouldn't build circuits, but it would mistakenly
15172 cache this conclusion, and continue believing it even when
15173 DisableNetwork is set to 0. Fixes the bug introduced by the fix
15174 for bug 11200; bugfix on 0.2.5.4-alpha.
15175 - Resume expanding abbreviations for command-line options. The fix
15176 for bug 4647 accidentally removed our hack from bug 586 that
15177 rewrote HashedControlPassword to __HashedControlSessionPassword
15178 when it appears on the commandline (which allowed the user to set
15179 her own HashedControlPassword in the torrc file while the
15180 controller generates a fresh session password for each run). Fixes
15181 bug 12948; bugfix on 0.2.5.1-alpha.
15182 - Warn about attempts to run hidden services and relays in the same
15183 process: that's probably not a good idea. Closes ticket 12908.
15185 o Major bugfixes (relay):
15186 - Avoid queuing or sending destroy cells for circuit ID zero when we
15187 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15188 Found and fixed by "cypherpunks".
15189 - Fix ORPort reachability detection on relays running behind a
15190 proxy, by correctly updating the "local" mark on the controlling
15191 channel when changing the address of an or_connection_t after the
15192 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15194 o Minor features (bridge):
15195 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15196 cookie file for the ExtORPort g+r by default.
15198 o Minor features (geoip):
15199 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15202 o Minor bugfixes (logging):
15203 - Reduce the log severity of the "Pluggable transport proxy does not
15204 provide any needed transports and will not be launched." message,
15205 since Tor Browser includes several ClientTransportPlugin lines in
15206 its torrc-defaults file, leading every Tor Browser user who looks
15207 at her logs to see these notices and wonder if they're dangerous.
15208 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
15209 - Downgrade "Unexpected onionskin length after decryption" warning
15210 to a protocol-warn, since there's nothing relay operators can do
15211 about a client that sends them a malformed create cell. Resolves
15212 bug 12996; bugfix on 0.0.6rc1.
15213 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15214 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15215 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15216 their names correctly. Fixes part of bug 12700; bugfix
15218 - When logging information about a relay cell whose command we don't
15219 recognize, log its command as an integer. Fixes part of bug 12700;
15220 bugfix on 0.2.1.10-alpha.
15221 - Escape all strings from the directory connection before logging
15222 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
15224 o Minor bugfixes (controller):
15225 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
15226 bug 12864; bugfix on 0.2.5.1-alpha.
15227 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
15228 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
15231 o Minor bugfixes (compilation):
15232 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
15233 bugfix on 0.2.5.5-alpha.
15234 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
15235 0.2.5.1-alpha. Patch from "NewEraCracker".
15236 - In routerlist_assert_ok(), don't take the address of a
15237 routerinfo's cache_info member unless that routerinfo is non-NULL.
15238 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15239 - Fix a large number of false positive warnings from the clang
15240 analyzer static analysis tool. This should make real warnings
15241 easier for clang analyzer to find. Patch from "teor". Closes
15244 o Distribution (systemd):
15245 - Verify configuration file via ExecStartPre in the systemd unit
15246 file. Patch from intrigeri; resolves ticket 12730.
15247 - Explicitly disable RunAsDaemon in the systemd unit file. Our
15248 current systemd unit uses "Type = simple", so systemd does not
15249 expect tor to fork. If the user has "RunAsDaemon 1" in their
15250 torrc, then things won't work as expected. This is e.g. the case
15251 on Debian (and derivatives), since there we pass "--defaults-torrc
15252 /usr/share/tor/tor-service-defaults-torrc" (that contains
15253 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
15257 - Adjust the URLs in the README to refer to the new locations of
15258 several documents on the website. Fixes bug 12830. Patch from
15260 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
15264 Changes in version 0.2.5.6-alpha - 2014-07-28
15265 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
15266 risk from guard rotation, and fixes a variety of other issues to get
15267 us closer to a release candidate.
15269 o Major features (also in 0.2.4.23):
15270 - Make the number of entry guards configurable via a new
15271 NumEntryGuards consensus parameter, and the number of directory
15272 guards configurable via a new NumDirectoryGuards consensus
15273 parameter. Implements ticket 12688.
15275 o Major bugfixes (also in 0.2.4.23):
15276 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15277 implementation that caused incorrect results on 32-bit
15278 implementations when certain malformed inputs were used along with
15279 a small class of private ntor keys. This bug does not currently
15280 appear to allow an attacker to learn private keys or impersonate a
15281 Tor server, but it could provide a means to distinguish 32-bit Tor
15282 implementations from 64-bit Tor implementations. Fixes bug 12694;
15283 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15287 - Perform circuit cleanup operations even when circuit
15288 construction operations are disabled (because the network is
15289 disabled, or because there isn't enough directory information).
15290 Previously, when we were not building predictive circuits, we
15291 were not closing expired circuits either. Fixes bug 8387; bugfix on
15292 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15293 became more strict about when we have "enough directory information
15294 to build circuits".
15297 - Authorities now assign the Guard flag to the fastest 25% of the
15298 network (it used to be the fastest 50%). Also raise the consensus
15299 weight that guarantees the Guard flag from 250 to 2000. For the
15300 current network, this results in about 1100 guards, down from 2500.
15301 This step paves the way for moving the number of entry guards
15302 down to 1 (proposal 236) while still providing reasonable expected
15303 performance for most users. Implements ticket 12690.
15304 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15306 - Slightly enhance the diagnostic message for bug 12184.
15308 o Minor bugfixes (also in 0.2.4.23):
15309 - Warn and drop the circuit if we receive an inbound 'relay early'
15310 cell. Those used to be normal to receive on hidden service circuits
15311 due to bug 1038, but the buggy Tor versions are long gone from
15312 the network so we can afford to resume watching for them. Resolves
15313 the rest of bug 1038; bugfix on 0.2.1.19.
15314 - Correct a confusing error message when trying to extend a circuit
15315 via the control protocol but we don't know a descriptor or
15316 microdescriptor for one of the specified relays. Fixes bug 12718;
15317 bugfix on 0.2.3.1-alpha.
15320 - Fix compilation when building with bufferevents enabled. (This
15321 configuration is still not expected to work, however.)
15322 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
15323 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
15325 - Compile correctly with builds and forks of OpenSSL (such as
15326 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15327 0.2.1.1-alpha. Patch from "dhill".
15330 Changes in version 0.2.4.23 - 2014-07-28
15331 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
15332 guard rotation, and also backports several important fixes from the
15333 Tor 0.2.5 alpha release series.
15336 - Clients now look at the "usecreatefast" consensus parameter to
15337 decide whether to use CREATE_FAST or CREATE cells for the first hop
15338 of their circuit. This approach can improve security on connections
15339 where Tor's circuit handshake is stronger than the available TLS
15340 connection security levels, but the tradeoff is more computational
15341 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15342 - Make the number of entry guards configurable via a new
15343 NumEntryGuards consensus parameter, and the number of directory
15344 guards configurable via a new NumDirectoryGuards consensus
15345 parameter. Implements ticket 12688.
15348 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15349 implementation that caused incorrect results on 32-bit
15350 implementations when certain malformed inputs were used along with
15351 a small class of private ntor keys. This bug does not currently
15352 appear to allow an attacker to learn private keys or impersonate a
15353 Tor server, but it could provide a means to distinguish 32-bit Tor
15354 implementations from 64-bit Tor implementations. Fixes bug 12694;
15355 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15359 - Warn and drop the circuit if we receive an inbound 'relay early'
15360 cell. Those used to be normal to receive on hidden service circuits
15361 due to bug 1038, but the buggy Tor versions are long gone from
15362 the network so we can afford to resume watching for them. Resolves
15363 the rest of bug 1038; bugfix on 0.2.1.19.
15364 - Correct a confusing error message when trying to extend a circuit
15365 via the control protocol but we don't know a descriptor or
15366 microdescriptor for one of the specified relays. Fixes bug 12718;
15367 bugfix on 0.2.3.1-alpha.
15368 - Avoid an illegal read from stack when initializing the TLS
15369 module using a version of OpenSSL without all of the ciphers
15370 used by the v2 link handshake. Fixes bug 12227; bugfix on
15371 0.2.4.8-alpha. Found by "starlight".
15374 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15378 Changes in version 0.2.5.5-alpha - 2014-06-18
15379 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
15380 0.2.5.x release series, including a couple of DoS issues, some
15381 performance regressions, a large number of bugs affecting the Linux
15382 seccomp2 sandbox code, and various other bugfixes. It also adds
15383 diagnostic bugfixes for a few tricky issues that we're trying to
15386 o Major features (security, traffic analysis resistance):
15387 - Several major improvements to the algorithm used to decide when to
15388 close TLS connections. Previous versions of Tor closed connections
15389 at a fixed interval after the last time a non-padding cell was
15390 sent over the connection, regardless of the target of the
15391 connection. Now, we randomize the intervals by adding up to 50% of
15392 their base value, we measure the length of time since connection
15393 last had at least one circuit, and we allow connections to known
15394 ORs to remain open a little longer (15 minutes instead of 3
15395 minutes minimum). These changes should improve Tor's resistance
15396 against some kinds of traffic analysis, and lower some overhead
15397 from needlessly closed connections. Fixes ticket 6799.
15398 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
15400 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
15401 - Fix a memory leak that could occur if a microdescriptor parse
15402 fails during the tokenizing step. This bug could enable a memory
15403 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15406 o Major bugfixes (security, directory authorities):
15407 - Directory authorities now include a digest of each relay's
15408 identity key as a part of its microdescriptor.
15410 This is a workaround for bug 11743 (reported by "cypherpunks"),
15411 where Tor clients do not support receiving multiple
15412 microdescriptors with the same SHA256 digest in the same
15413 consensus. When clients receive a consensus like this, they only
15414 use one of the relays. Without this fix, a hostile relay could
15415 selectively disable some client use of target relays by
15416 constructing a router descriptor with a different identity and the
15417 same microdescriptor parameters and getting the authorities to
15418 list it in a microdescriptor consensus. This fix prevents an
15419 attacker from causing a microdescriptor collision, because the
15420 router's identity is not forgeable.
15422 o Major bugfixes (relay):
15423 - Use a direct dirport connection when uploading non-anonymous
15424 descriptors to the directory authorities. Previously, relays would
15425 incorrectly use tunnel connections under a fairly wide variety of
15426 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15427 - When a circuit accidentally has the same circuit ID for its
15428 forward and reverse direction, correctly detect the direction of
15429 cells using that circuit. Previously, this bug made roughly one
15430 circuit in a million non-functional. Fixes bug 12195; this is a
15431 bugfix on every version of Tor.
15433 o Major bugfixes (client, pluggable transports):
15434 - When managing pluggable transports, use OS notification facilities
15435 to learn if they have crashed, and don't attempt to kill any
15436 process that has already exited. Fixes bug 8746; bugfix
15439 o Minor features (diagnostic):
15440 - When logging a warning because of bug 7164, additionally check the
15441 hash table for consistency (as proposed on ticket 11737). This may
15442 help diagnose bug 7164.
15443 - When we log a heartbeat, log how many one-hop circuits we have
15444 that are at least 30 minutes old, and log status information about
15445 a few of them. This is an attempt to track down bug 8387.
15446 - When encountering an unexpected CR while writing text to a file on
15447 Windows, log the name of the file. Should help diagnosing
15449 - Give more specific warnings when a client notices that an onion
15450 handshake has failed. Fixes ticket 9635.
15451 - Add significant new logging code to attempt to diagnose bug 12184,
15452 where relays seem to run out of available circuit IDs.
15453 - Improve the diagnostic log message for bug 8387 even further to
15454 try to improve our odds of figuring out why one-hop directory
15455 circuits sometimes do not get closed.
15457 o Minor features (security, memory management):
15458 - Memory allocation tricks (mempools and buffer freelists) are now
15459 disabled by default. You can turn them back on with
15460 --enable-mempools and --enable-buf-freelists respectively. We're
15461 disabling these features because malloc performance is good enough
15462 on most platforms, and a similar feature in OpenSSL exacerbated
15463 exploitation of the Heartbleed attack. Resolves ticket 11476.
15465 o Minor features (security):
15466 - Apply the secure SipHash-2-4 function to the hash table mapping
15467 circuit IDs and channels to circuits. We missed this one when we
15468 were converting all the other hash functions to use SipHash back
15469 in 0.2.5.3-alpha. Resolves ticket 11750.
15471 o Minor features (build):
15472 - The configure script has a --disable-seccomp option to turn off
15473 support for libseccomp on systems that have it, in case it (or
15474 Tor's use of it) is broken. Resolves ticket 11628.
15476 o Minor features (other):
15477 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15480 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15481 - When running a hidden service, do not allow TunneledDirConns 0;
15482 this will keep the hidden service from running, and also
15483 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15484 bugfix on 0.2.1.1-alpha.
15486 o Minor bugfixes (performance):
15487 - Avoid a bug where every successful connection made us recompute
15488 the flag telling us whether we have sufficient information to
15489 build circuits. Previously, we would forget our cached value
15490 whenever we successfully opened a channel (or marked a router as
15491 running or not running for any other reason), regardless of
15492 whether we had previously believed the router to be running. This
15493 forced us to run an expensive update operation far too often.
15494 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15495 - Avoid using tor_memeq() for checking relay cell integrity. This
15496 removes a possible performance bottleneck. Fixes part of bug
15497 12169; bugfix on 0.2.1.31.
15499 o Minor bugfixes (compilation):
15500 - Fix compilation of test_status.c when building with MVSC. Bugfix
15501 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15502 - Resolve GCC complaints on OpenBSD about discarding constness in
15503 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15504 on 0.1.1.23. Patch from Dana Koch.
15505 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15506 treatment of long and time_t as comparable types. Fixes part of
15507 bug 11633. Patch from Dana Koch.
15508 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15509 11623; bugfix on 0.2.5.3-alpha.
15510 - When deciding whether to build the 64-bit curve25519
15511 implementation, detect platforms where we can compile 128-bit
15512 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15513 0.2.4.8-alpha. Patch from "conradev".
15514 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15515 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15516 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15519 o Minor bugfixes (Directory server):
15520 - When sending a compressed set of descriptors or microdescriptors,
15521 make sure to finalize the zlib stream. Previously, we would write
15522 all the compressed data, but if the last descriptor we wanted to
15523 send was missing or too old, we would not mark the stream as
15524 finished. This caused problems for decompression tools. Fixes bug
15525 11648; bugfix on 0.1.1.23.
15527 o Minor bugfixes (Linux seccomp sandbox):
15528 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15529 11622; bugfix on 0.2.5.1-alpha.
15530 - Avoid crashing when re-opening listener ports with the seccomp
15531 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15532 - Avoid crashing with the seccomp sandbox enabled along with
15533 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15534 - When we receive a SIGHUP with the sandbox enabled, correctly
15535 support rotating our log files. Fixes bug 12032; bugfix
15537 - Avoid crash when running with sandboxing enabled and
15538 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15540 - Fix a "BUG" warning when trying to write bridge-stats files with
15541 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15543 - Prevent the sandbox from crashing on startup when run with the
15544 --enable-expensive-hardening configuration option. Fixes bug
15545 11477; bugfix on 0.2.5.4-alpha.
15546 - When running with DirPortFrontPage and sandboxing both enabled,
15547 reload the DirPortFrontPage correctly when restarting. Fixes bug
15548 12028; bugfix on 0.2.5.1-alpha.
15549 - Don't try to enable the sandbox when using the Tor binary to check
15550 its configuration, hash a passphrase, or so on. Doing so was
15551 crashing on startup for some users. Fixes bug 11609; bugfix
15553 - Avoid warnings when running with sandboxing and node statistics
15554 enabled at the same time. Fixes part of 12064; bugfix on
15555 0.2.5.1-alpha. Patch from Michael Wolf.
15556 - Avoid warnings when running with sandboxing enabled at the same
15557 time as cookie authentication, hidden services, or directory
15558 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15559 - Do not allow options that require calls to exec to be enabled
15560 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15561 bug 12043; bugfix on 0.2.5.1-alpha.
15562 - Handle failures in getpwnam()/getpwuid() when running with the
15563 User option set and the Linux syscall sandbox enabled. Fixes bug
15564 11946; bugfix on 0.2.5.1-alpha.
15565 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15566 to avoid calling getaddrinfo() after installing the sandbox
15567 filters. Previously, it preloaded a cache with the IPv4 address
15568 for our hostname, and nothing else. Now, it loads the cache with
15569 every address that it used to initialize the Tor process. Fixes
15570 bug 11970; bugfix on 0.2.5.1-alpha.
15572 o Minor bugfixes (pluggable transports):
15573 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15574 default location of the authentication token for the extended OR
15575 Port as used by sever-side pluggable transports. We had
15576 implemented this option before, but the code to make it settable
15577 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15578 - Avoid another 60-second delay when starting Tor in a pluggable-
15579 transport-using configuration when we already have cached
15580 descriptors for our bridges. Fixes bug 11965; bugfix
15583 o Minor bugfixes (client):
15584 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15585 when starting a client with bridges configured and DisableNetwork
15586 set. (Tor launcher starts Tor with DisableNetwork set the first
15587 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15589 o Minor bugfixes (testing):
15590 - The Python parts of the test scripts now work on Python 3 as well
15591 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15592 no longer have the tests break. Fixes bug 11608; bugfix
15594 - When looking for versions of python that we could run the tests
15595 with, check for "python2.7" and "python3.3"; previously we were
15596 only looking for "python", "python2", and "python3". Patch from
15597 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15598 - Fix all valgrind warnings produced by the unit tests. There were
15599 over a thousand memory leak warnings previously, mostly produced
15600 by forgetting to free things in the unit test code. Fixes bug
15601 11618, bugfixes on many versions of Tor.
15603 o Minor bugfixes (tor-fw-helper):
15604 - Give a correct log message when tor-fw-helper fails to launch.
15605 (Previously, we would say something like "tor-fw-helper sent us a
15606 string we could not parse".) Fixes bug 9781; bugfix
15609 o Minor bugfixes (relay, threading):
15610 - Check return code on spawn_func() in cpuworker code, so that we
15611 don't think we've spawned a nonworking cpuworker and write junk to
15612 it forever. Fix related to bug 4345; bugfix on all released Tor
15613 versions. Found by "skruffy".
15614 - Use a pthread_attr to make sure that spawn_func() cannot return an
15615 error while at the same time launching a thread. Fix related to
15616 bug 4345; bugfix on all released Tor versions. Reported
15619 o Minor bugfixes (relay, oom prevention):
15620 - Correctly detect the total available system memory. We tried to do
15621 this in 0.2.5.4-alpha, but the code was set up to always return an
15622 error value, even on success. Fixes bug 11805; bugfix
15625 o Minor bugfixes (relay, other):
15626 - We now drop CREATE cells for already-existent circuit IDs and for
15627 zero-valued circuit IDs, regardless of other factors that might
15628 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
15630 - Avoid an illegal read from stack when initializing the TLS module
15631 using a version of OpenSSL without all of the ciphers used by the
15632 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
15634 - When rejecting DATA cells for stream_id zero, still count them
15635 against the circuit's deliver window so that we don't fail to send
15636 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
15638 o Minor bugfixes (logging):
15639 - Fix a misformatted log message about delayed directory fetches.
15640 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
15641 - Squelch a spurious LD_BUG message "No origin circuit for
15642 successful SOCKS stream" in certain hidden service failure cases;
15646 - Include a tor.service file in contrib/dist for use with systemd.
15647 Some distributions will be able to use this file unmodified;
15648 others will need to tweak it, or write their own. Patch from Jamie
15649 Nguyen; resolves ticket 8368.
15652 - Clean up several option names in the manpage to match their real
15653 names, add the missing documentation for a couple of testing and
15654 directory authority options, remove the documentation for a
15655 V2-directory fetching option that no longer exists. Resolves
15657 - Correct the documentation so that it lists the correct directory
15658 for the stats files. (They are in a subdirectory called "stats",
15660 - In the manpage, move more authority-only options into the
15661 directory authority section so that operators of regular directory
15662 caches don't get confused.
15665 - The contrib directory has been sorted and tidied. Before, it was
15666 an unsorted dumping ground for useful and not-so-useful things.
15667 Now, it is divided based on functionality, and the items which
15668 seemed to be nonfunctional or useless have been removed. Resolves
15669 ticket 8966; based on patches from "rl1987".
15672 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
15673 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
15674 - The TunnelDirConns and PreferTunnelledDirConns options no longer
15675 exist; tunneled directory connections have been available since
15676 0.1.2.5-alpha, and turning them off is not a good idea. This is a
15677 brute-force fix for 10849, where "TunnelDirConns 0" would break
15681 Changes in version 0.2.4.22 - 2014-05-16
15682 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
15683 alpha release series. These include blocking all authority signing
15684 keys that may have been affected by the OpenSSL "heartbleed" bug,
15685 choosing a far more secure set of TLS ciphersuites by default, closing
15686 a couple of memory leaks that could be used to run a target relay out
15687 of RAM, and several others.
15689 o Major features (security, backport from 0.2.5.4-alpha):
15690 - Block authority signing keys that were used on authorities
15691 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15692 don't have any evidence that these keys _were_ compromised; we're
15693 doing this to be prudent.) Resolves ticket 11464.
15695 o Major bugfixes (security, OOM):
15696 - Fix a memory leak that could occur if a microdescriptor parse
15697 fails during the tokenizing step. This bug could enable a memory
15698 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15701 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
15702 - The relay ciphersuite list is now generated automatically based on
15703 uniform criteria, and includes all OpenSSL ciphersuites with
15704 acceptable strength and forward secrecy. Previously, we had left
15705 some perfectly fine ciphersuites unsupported due to omission or
15706 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15707 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15708 - Relays now trust themselves to have a better view than clients of
15709 which TLS ciphersuites are better than others. (Thanks to bug
15710 11513, the relay list is now well-considered, whereas the client
15711 list has been chosen mainly for anti-fingerprinting purposes.)
15712 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15713 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15714 AES128. Resolves ticket 11528.
15715 - Clients now try to advertise the same list of ciphersuites as
15716 Firefox 28. This change enables selection of (fast) GCM
15717 ciphersuites, disables some strange old ciphers, and stops
15718 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15719 Resolves ticket 11438.
15721 o Minor bugfixes (configuration, security):
15722 - When running a hidden service, do not allow TunneledDirConns 0:
15723 trying to set that option together with a hidden service would
15724 otherwise prevent the hidden service from running, and also make
15725 it publish its descriptors directly over HTTP. Fixes bug 10849;
15726 bugfix on 0.2.1.1-alpha.
15728 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
15729 - Avoid sending a garbage value to the controller when a circuit is
15730 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15732 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
15733 - Stop leaking memory when we successfully resolve a PTR record.
15734 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15736 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
15737 - Avoid 60-second delays in the bootstrapping process when Tor is
15738 launching for a second time while using bridges. Fixes bug 9229;
15739 bugfix on 0.2.0.3-alpha.
15741 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
15742 - Give the correct URL in the warning message when trying to run a
15743 relay on an ancient version of Windows. Fixes bug 9393.
15745 o Minor bugfixes (compilation):
15746 - Fix a compilation error when compiling with --disable-curve25519.
15747 Fixes bug 9700; bugfix on 0.2.4.17-rc.
15750 - Downgrade the warning severity for the the "md was still
15751 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
15752 for trying to diagnose this bug, and the current warning in
15753 earlier versions of tor achieves nothing useful. Addresses warning
15756 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
15757 - When we run out of usable circuit IDs on a channel, log only one
15758 warning for the whole channel, and describe how many circuits
15759 there were on the channel. Fixes part of ticket 11553.
15761 o Minor features (security, backport from 0.2.5.4-alpha):
15762 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
15763 leave the default at 8GBytes), to better support Raspberry Pi
15764 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
15766 o Documentation (backport from 0.2.5.4-alpha):
15767 - Correctly document that we search for a system torrc file before
15768 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
15772 Changes in version 0.2.5.4-alpha - 2014-04-25
15773 Tor 0.2.5.4-alpha includes several security and performance
15774 improvements for clients and relays, including blacklisting authority
15775 signing keys that were used while susceptible to the OpenSSL
15776 "heartbleed" bug, fixing two expensive functions on busy relays,
15777 improved TLS ciphersuite preference lists, support for run-time
15778 hardening on compilers that support AddressSanitizer, and more work on
15779 the Linux sandbox code.
15781 There are also several usability fixes for clients (especially clients
15782 that use bridges), two new TransPort protocols supported (one on
15783 OpenBSD, one on FreeBSD), and various other bugfixes.
15785 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
15786 have accumulated many known flaws; everyone should upgrade.
15788 o Major features (security):
15789 - If you don't specify MaxMemInQueues yourself, Tor now tries to
15790 pick a good value based on your total system memory. Previously,
15791 the default was always 8 GB. You can still override the default by
15792 setting MaxMemInQueues yourself. Resolves ticket 11396.
15793 - Block authority signing keys that were used on authorities
15794 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15795 don't have any evidence that these keys _were_ compromised; we're
15796 doing this to be prudent.) Resolves ticket 11464.
15798 o Major features (relay performance):
15799 - Speed up server-side lookups of rendezvous and introduction point
15800 circuits by using hashtables instead of linear searches. These
15801 functions previously accounted between 3 and 7% of CPU usage on
15802 some busy relays. Resolves ticket 9841.
15803 - Avoid wasting CPU when extending a circuit over a channel that is
15804 nearly out of circuit IDs. Previously, we would do a linear scan
15805 over possible circuit IDs before finding one or deciding that we
15806 had exhausted our possibilities. Now, we try at most 64 random
15807 circuit IDs before deciding that we probably won't succeed. Fixes
15808 a possible root cause of ticket 11553.
15810 o Major features (seccomp2 sandbox, Linux only):
15811 - The seccomp2 sandbox can now run a test network for multiple hours
15812 without crashing. The sandbox is still experimental, and more bugs
15813 will probably turn up. To try it, enable "Sandbox 1" on a Linux
15814 host. Resolves ticket 11351.
15815 - Strengthen sandbox code: the sandbox can now test the arguments
15816 for rename(), and blocks _sysctl() entirely. Resolves another part
15818 - When the sandbox blocks a system call, it now tries to log a stack
15819 trace before exiting. Resolves ticket 11465.
15821 o Major bugfixes (TLS cipher selection):
15822 - The relay ciphersuite list is now generated automatically based on
15823 uniform criteria, and includes all OpenSSL ciphersuites with
15824 acceptable strength and forward secrecy. Previously, we had left
15825 some perfectly fine ciphersuites unsupported due to omission or
15826 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15827 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
15828 - Relays now trust themselves to have a better view than clients of
15829 which TLS ciphersuites are better than others. (Thanks to bug
15830 11513, the relay list is now well-considered, whereas the client
15831 list has been chosen mainly for anti-fingerprinting purposes.)
15832 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
15833 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
15834 AES128. Resolves ticket 11528.
15835 - Clients now try to advertise the same list of ciphersuites as
15836 Firefox 28. This change enables selection of (fast) GCM
15837 ciphersuites, disables some strange old ciphers, and stops
15838 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
15839 Resolves ticket 11438.
15841 o Major bugfixes (bridge client):
15842 - Avoid 60-second delays in the bootstrapping process when Tor is
15843 launching for a second time while using bridges. Fixes bug 9229;
15844 bugfix on 0.2.0.3-alpha.
15846 o Minor features (transparent proxy, *BSD):
15847 - Support FreeBSD's ipfw firewall interface for TransPort ports on
15848 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
15849 10267; patch from "yurivict".
15850 - Support OpenBSD's divert-to rules with the pf firewall for
15851 transparent proxy ports. To enable it, set "TransProxyType
15852 pf-divert". This allows Tor to run a TransPort transparent proxy
15853 port on OpenBSD 4.4 or later without root privileges. See the
15854 pf.conf(5) manual page for information on configuring pf to use
15855 divert-to rules. Closes ticket 10896; patch from Dana Koch.
15857 o Minor features (security):
15858 - New --enable-expensive-hardening option to enable security
15859 hardening options that consume nontrivial amounts of CPU and
15860 memory. Right now, this includes AddressSanitizer and UbSan, which
15861 are supported in newer versions of GCC and Clang. Closes ticket
15864 o Minor features (log verbosity):
15865 - Demote the message that we give when a flushing connection times
15866 out for too long from NOTICE to INFO. It was usually meaningless.
15867 Resolves ticket 5286.
15868 - Don't log so many notice-level bootstrapping messages at startup
15869 about downloading descriptors. Previously, we'd log a notice
15870 whenever we learned about more routers. Now, we only log a notice
15871 at every 5% of progress. Fixes bug 9963.
15872 - Warn less verbosely when receiving a malformed
15873 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
15874 - When we run out of usable circuit IDs on a channel, log only one
15875 warning for the whole channel, and describe how many circuits
15876 there were on the channel. Fixes part of ticket 11553.
15878 o Minor features (relay):
15879 - If a circuit timed out for at least 3 minutes, check if we have a
15880 new external IP address, and publish a new descriptor with the new
15881 IP address if it changed. Resolves ticket 2454.
15883 o Minor features (controller):
15884 - Make the entire exit policy available from the control port via
15885 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
15887 - Because of the fix for ticket 11396, the real limit for memory
15888 usage may no longer match the configured MaxMemInQueues value. The
15889 real limit is now exposed via GETINFO limits/max-mem-in-queues.
15891 o Minor features (bridge client):
15892 - Report a more useful failure message when we can't connect to a
15893 bridge because we don't have the right pluggable transport
15894 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
15896 o Minor features (diagnostic):
15897 - Add more log messages to diagnose bug 7164, which causes
15898 intermittent "microdesc_free() called but md was still referenced"
15899 warnings. We now include more information, to figure out why we
15900 might be cleaning a microdescriptor for being too old if it's
15901 still referenced by a live node_t object.
15903 o Minor bugfixes (client, DNSPort):
15904 - When using DNSPort, try to respond to AAAA requests with AAAA
15905 answers. Previously, we hadn't looked at the request type when
15906 deciding which answer type to prefer. Fixes bug 10468; bugfix on
15908 - When receiving a DNS query for an unsupported record type, reply
15909 with no answer rather than with a NOTIMPL error. This behavior
15910 isn't correct either, but it will break fewer client programs, we
15911 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
15914 o Minor bugfixes (exit relay):
15915 - Stop leaking memory when we successfully resolve a PTR record.
15916 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
15918 o Minor bugfixes (bridge client):
15919 - Stop accepting bridge lines containing hostnames. Doing so would
15920 cause clients to perform DNS requests on the hostnames, which was
15921 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
15922 - Avoid a 60-second delay in the bootstrapping process when a Tor
15923 client with pluggable transports re-reads its configuration at
15924 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
15926 o Minor bugfixes (client, logging during bootstrap):
15927 - Warn only once if we start logging in an unsafe way. Previously,
15928 we complain as many times as we had problems. Fixes bug 9870;
15929 bugfix on 0.2.5.1-alpha.
15930 - Only report the first fatal bootstrap error on a given OR
15931 connection. This stops us from telling the controller bogus error
15932 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
15933 - Be more helpful when trying to run sandboxed on Linux without
15934 libseccomp. Instead of saying "Sandbox is not implemented on this
15935 platform", we now explain that we need to be built with
15936 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
15937 - Avoid generating spurious warnings when starting with
15938 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
15941 o Minor bugfixes (closing OR connections):
15942 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
15943 check if it's an or_connection_t and correctly call
15944 connection_or_close_for_error() rather than
15945 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
15947 - When closing all connections on setting DisableNetwork to 1, use
15948 connection_or_close_normally() rather than closing OR connections
15949 out from under the channel layer. Fixes bug 11306; bugfix on
15952 o Minor bugfixes (controller):
15953 - Avoid sending a garbage value to the controller when a circuit is
15954 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
15956 o Minor bugfixes (tor-fw-helper):
15957 - Allow tor-fw-helper to build again by adding src/ext to its
15958 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
15960 o Minor bugfixes (bridges):
15961 - Avoid potential crashes or bad behavior when launching a
15962 server-side managed proxy with ORPort or ExtORPort temporarily
15963 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
15965 o Minor bugfixes (platform-specific):
15966 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
15967 bug 11426; bugfix on 0.2.5.3-alpha.
15968 - When dumping a malformed directory object to disk, save it in
15969 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
15971 - Don't report failures from make_socket_reuseable() on incoming
15972 sockets on OSX: this can happen when incoming connections close
15973 early. Fixes bug 10081.
15975 o Minor bugfixes (trivial memory leaks):
15976 - Fix a small memory leak when signing a directory object. Fixes bug
15977 11275; bugfix on 0.2.4.13-alpha.
15978 - Free placeholder entries in our circuit table at exit; fixes a
15979 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
15980 - Don't re-initialize a second set of OpenSSL mutexes when starting
15981 up. Previously, we'd make one set of mutexes, and then immediately
15982 replace them with another. Fixes bug 11726; bugfix on
15984 - Resolve some memory leaks found by coverity in the unit tests, on
15985 exit in tor-gencert, and on a failure to compute digests for our
15986 own keys when generating a v3 networkstatus vote. These leaks
15987 should never have affected anyone in practice.
15989 o Minor bugfixes (hidden service):
15990 - Only retry attempts to connect to a chosen rendezvous point 8
15991 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
15993 o Minor bugfixes (misc code correctness):
15994 - Fix various instances of undefined behavior in channeltls.c,
15995 tor_memmem(), and eventdns.c that would cause us to construct
15996 pointers to memory outside an allocated object. (These invalid
15997 pointers were not accessed, but C does not even allow them to
15998 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
15999 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16000 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16001 fix some miscellaneous errors in our tests and codebase. Fixes bug
16002 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16003 - Always check return values for unlink, munmap, UnmapViewOfFile;
16004 check strftime return values more often. In some cases all we can
16005 do is report a warning, but this may help prevent deeper bugs from
16006 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16008 - Fix numerous warnings from the clang "scan-build" static analyzer.
16009 Some of these are programming style issues; some of them are false
16010 positives that indicated awkward code; some are undefined behavior
16011 cases related to constructing (but not using) invalid pointers;
16012 some are assumptions about API behavior; some are (harmlessly)
16013 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16014 correct; and one or two are genuine bugs that weren't reachable
16015 from the rest of the program. Fixes bug 8793; bugfixes on many,
16019 - Build the torify.1 manpage again. Previously, we were only trying
16020 to build it when also building tor-fw-helper. That's why we didn't
16021 notice that we'd broken the ability to build it. Fixes bug 11321;
16022 bugfix on 0.2.5.1-alpha.
16023 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16024 11061; bugfix on 0.2.4.7-alpha.
16025 - Correctly document that we search for a system torrc file before
16026 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16028 - Resolve warnings from Doxygen.
16030 o Code simplifications and refactoring:
16031 - Remove is_internal_IP() function. Resolves ticket 4645.
16032 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16033 Closes issue 9107; patch from "marek".
16034 - Change our use of the ENUM_BF macro to avoid declarations that
16037 o Deprecated versions:
16038 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
16039 attention for some while. Directory authorities no longer accept
16040 descriptors from relays running any version of Tor prior to Tor
16041 0.2.3.16-alpha. Resolves ticket 11149.
16044 - New macros in test.h to simplify writing mock-functions for unit
16045 tests. Part of ticket 11507. Patch from Dana Koch.
16046 - Complete tests for the status.c module. Resolves ticket 11507.
16047 Patch from Dana Koch.
16050 - Remove all code for the long unused v1 directory protocol.
16051 Resolves ticket 11070.
16054 Changes in version 0.2.5.3-alpha - 2014-03-22
16055 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
16056 two new anti-DoS features for Tor relays, resolves a bug that kept
16057 SOCKS5 support for IPv6 from working, fixes several annoying usability
16058 issues for bridge users, and removes more old code for unused
16061 The Tor 0.2.5.x release series is now in patch-freeze: no feature
16062 patches not already written will be considered for inclusion in 0.2.5.x.
16064 o Major features (relay security, DoS-resistance):
16065 - When deciding whether we have run out of memory and we need to
16066 close circuits, also consider memory allocated in buffers for
16067 streams attached to each circuit.
16069 This change, which extends an anti-DoS feature introduced in
16070 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16071 better resist more memory-based DoS attacks than before. Since the
16072 MaxMemInCellQueues option now applies to all queues, it is renamed
16073 to MaxMemInQueues. This feature fixes bug 10169.
16074 - Avoid hash-flooding denial-of-service attacks by using the secure
16075 SipHash-2-4 hash function for our hashtables. Without this
16076 feature, an attacker could degrade performance of a targeted
16077 client or server by flooding their data structures with a large
16078 number of entries to be stored at the same hash table position,
16079 thereby slowing down the Tor instance. With this feature, hash
16080 table positions are derived from a randomized cryptographic key,
16081 and an attacker cannot predict which entries will collide. Closes
16083 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
16084 the default at 8GBytes), to better support Raspberry Pi users. Fixes
16085 bug 9686; bugfix on 0.2.4.14-alpha.
16087 o Minor features (bridges, pluggable transports):
16088 - Bridges now write the SHA1 digest of their identity key
16089 fingerprint (that is, a hash of a hash of their public key) to
16090 notice-level logs, and to a new hashed-fingerprint file. This
16091 information will help bridge operators look up their bridge in
16092 Globe and similar tools. Resolves ticket 10884.
16093 - Improve the message that Tor displays when running as a bridge
16094 using pluggable transports without an Extended ORPort listener.
16095 Also, log the message in the log file too. Resolves ticket 11043.
16097 o Minor features (other):
16098 - Add a new option, PredictedPortsRelevanceTime, to control how long
16099 after having received a request to connect to a given port Tor
16100 will try to keep circuits ready in anticipation of future requests
16101 for that port. Patch from "unixninja92"; implements ticket 9176.
16102 - Generate a warning if any ports are listed in the SocksPolicy,
16103 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16104 AuthDirBadExit options. (These options only support address
16105 ranges.) Fixes part of ticket 11108.
16106 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
16109 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
16110 - Build without warnings under clang 3.4. (We have some macros that
16111 define static functions only some of which will get used later in
16112 the module. Starting with clang 3.4, these give a warning unless the
16113 unused attribute is set on them.) Resolves ticket 10904.
16114 - Fix build warnings about missing "a2x" comment when building the
16115 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16116 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16118 o Minor bugfixes (client):
16119 - Improve the log message when we can't connect to a hidden service
16120 because all of the hidden service directory nodes hosting its
16121 descriptor are excluded. Improves on our fix for bug 10722, which
16122 was a bugfix on 0.2.0.10-alpha.
16123 - Raise a control port warning when we fail to connect to all of
16124 our bridges. Previously, we didn't inform the controller, and
16125 the bootstrap process would stall. Fixes bug 11069; bugfix on
16127 - Exit immediately when a process-owning controller exits.
16128 Previously, tor relays would wait for a little while after their
16129 controller exited, as if they had gotten an INT signal -- but this
16130 was problematic, since there was no feedback for the user. To do a
16131 clean shutdown, controllers should send an INT signal and give Tor
16132 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16133 - Stop attempting to connect to bridges before our pluggable
16134 transports are configured (harmless but resulted in some erroneous
16135 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16136 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16137 generating incorrect SOCKS5 responses, and confusing client
16138 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16140 o Minor bugfixes (relays and bridges):
16141 - Avoid crashing on a malformed resolv.conf file when running a
16142 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16143 - Non-exit relays no longer launch mock DNS requests to check for
16144 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16145 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16146 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16147 - Bridges now report complete directory request statistics. Related
16148 to bug 5824; bugfix on 0.2.2.1-alpha.
16149 - Bridges now never collect statistics that were designed for
16150 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16151 - Stop giving annoying warning messages when we decide not to launch
16152 a pluggable transport proxy that we don't need (because there are
16153 no bridges configured to use it). Resolves ticket 5018; bugfix
16155 - Give the correct URL in the warning message when trying to run a
16156 relay on an ancient version of Windows. Fixes bug 9393.
16158 o Minor bugfixes (backtrace support):
16159 - Support automatic backtraces on more platforms by using the
16160 "-fasynchronous-unwind-tables" compiler option. This option is
16161 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
16162 is on by default and table generation is not. This doesn't yet
16163 add Windows support; only Linux, OSX, and some BSDs are affected.
16164 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
16165 - Avoid strange behavior if two threads hit failed assertions at the
16166 same time and both try to log backtraces at once. (Previously, if
16167 this had happened, both threads would have stored their intermediate
16168 results in the same buffer, and generated junk outputs.) Reported by
16169 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
16170 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
16171 0.2.5.2-alpha; patch from Nick Hopper.
16173 o Minor bugfixes (unit tests):
16174 - Fix a small bug in the unit tests that might have made the tests
16175 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
16176 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
16179 - Remove all remaining code related to version-0 hidden service
16180 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16181 the rest of bug 10841.
16184 - Document in the manpage that "KBytes" may also be written as
16185 "kilobytes" or "KB", that "Kbits" may also be written as
16186 "kilobits", and so forth. Closes ticket 9222.
16187 - Document that the ClientOnly config option overrides ORPort.
16188 Our old explanation made ClientOnly sound as though it did
16189 nothing at all. Resolves bug 9059.
16190 - Explain that SocksPolicy, DirPolicy, and similar options don't
16191 take port arguments. Fixes the other part of ticket 11108.
16192 - Fix a comment about the rend_server_descriptor_t.protocols field
16193 to more accurately describe its range. Also, make that field
16194 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16195 bugfix on 0.2.1.5-alpha.
16196 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16197 the maximum client name length is 16, not 19. Fixes bug 11118;
16198 bugfix on 0.2.1.6-alpha.
16200 o Code simplifications and refactoring:
16201 - Get rid of router->address, since in all cases it was just the
16202 string representation of router->addr. Resolves ticket 5528.
16204 o Test infrastructure:
16205 - Update to the latest version of tinytest.
16206 - Improve the tinytest implementation of string operation tests so
16207 that comparisons with NULL strings no longer crash the tests; they
16208 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16211 Changes in version 0.2.4.21 - 2014-02-28
16212 Tor 0.2.4.21 further improves security against potential adversaries who
16213 find breaking 1024-bit crypto doable, and backports several stability
16214 and robustness patches from the 0.2.5 branch.
16216 o Major features (client security):
16217 - When we choose a path for a 3-hop circuit, make sure it contains
16218 at least one relay that supports the NTor circuit extension
16219 handshake. Otherwise, there is a chance that we're building
16220 a circuit that's worth attacking by an adversary who finds
16221 breaking 1024-bit crypto doable, and that chance changes the game
16222 theory. Implements ticket 9777.
16225 - Do not treat streams that fail with reason
16226 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16227 since it could also indicate an ENETUNREACH connection error. Fixes
16228 part of bug 10777; bugfix on 0.2.4.8-alpha.
16230 o Code simplification and refactoring:
16231 - Remove data structures which were introduced to implement the
16232 CellStatistics option: they are now redundant with the new timestamp
16233 field in the regular packed_cell_t data structure, which we did
16234 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16237 - Always clear OpenSSL bignums before freeing them -- even bignums
16238 that don't contain secrets. Resolves ticket 10793. Patch by
16240 - Build without warnings under clang 3.4. (We have some macros that
16241 define static functions only some of which will get used later in
16242 the module. Starting with clang 3.4, these give a warning unless the
16243 unused attribute is set on them.) Resolves ticket 10904.
16244 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16245 GeoLite2 Country database.
16248 - Set the listen() backlog limit to the largest actually supported
16249 on the system, not to the value in a header file. Fixes bug 9716;
16250 bugfix on every released Tor.
16251 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16252 exit node as a NOROUTE error, not an INTERNAL error, since they
16253 can apparently happen when trying to connect to the wrong sort
16254 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16255 - Fix build warnings about missing "a2x" comment when building the
16256 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16257 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16258 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16259 not entirely remove it from the connection lists. Fixes bug 9602;
16260 bugfix on 0.2.4.4-alpha.
16261 - Fix a segmentation fault in our benchmark code when running with
16262 Fedora's OpenSSL package, or any other OpenSSL that provides
16263 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16264 - Turn "circuit handshake stats since last time" log messages into a
16265 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16267 o Documentation fixes:
16268 - Document that all but one DirPort entry must have the NoAdvertise
16269 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16272 Changes in version 0.2.5.2-alpha - 2014-02-13
16273 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
16274 like the "poor random number generation" fix and the "building too many
16275 circuits" fix. It also further improves security against potential
16276 adversaries who find breaking 1024-bit crypto doable, and launches
16277 pluggable transports on demand (which gets us closer to integrating
16278 pluggable transport support by default -- not to be confused with Tor
16279 bundles enabling pluggable transports and bridges by default).
16281 o Major features (client security):
16282 - When we choose a path for a 3-hop circuit, make sure it contains
16283 at least one relay that supports the NTor circuit extension
16284 handshake. Otherwise, there is a chance that we're building
16285 a circuit that's worth attacking by an adversary who finds
16286 breaking 1024-bit crypto doable, and that chance changes the game
16287 theory. Implements ticket 9777.
16288 - Clients now look at the "usecreatefast" consensus parameter to
16289 decide whether to use CREATE_FAST or CREATE cells for the first hop
16290 of their circuit. This approach can improve security on connections
16291 where Tor's circuit handshake is stronger than the available TLS
16292 connection security levels, but the tradeoff is more computational
16293 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16295 o Major features (bridges):
16296 - Don't launch pluggable transport proxies if we don't have any
16297 bridges configured that would use them. Now we can list many
16298 pluggable transports, and Tor will dynamically start one when it
16299 hears a bridge address that needs it. Resolves ticket 5018.
16300 - The bridge directory authority now assigns status flags (Stable,
16301 Guard, etc) to bridges based on thresholds calculated over all
16302 Running bridges. Now bridgedb can finally make use of its features
16303 to e.g. include at least one Stable bridge in its answers. Fixes
16306 o Major features (other):
16307 - Extend ORCONN controller event to include an "ID" parameter,
16308 and add four new controller event types CONN_BW, CIRC_BW,
16309 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16310 The new events are emitted in private Tor networks only, with the
16311 goal of being able to better track performance and load during
16312 full-network simulations. Implements proposal 218 and ticket 7359.
16313 - On some platforms (currently: recent OSX versions, glibc-based
16314 platforms that support the ELF format, and a few other
16315 Unix-like operating systems), Tor can now dump stack traces
16316 when a crash occurs or an assertion fails. By default, traces
16317 are dumped to stderr (if possible) and to any logs that are
16318 reporting errors. Implements ticket 9299.
16321 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16322 not entirely remove it from the connection lists. Fixes bug 9602;
16323 bugfix on 0.2.4.4-alpha.
16324 - Do not treat streams that fail with reason
16325 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16326 since it could also indicate an ENETUNREACH connection error. Fixes
16327 part of bug 10777; bugfix on 0.2.4.8-alpha.
16329 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16330 - Do not allow OpenSSL engines to replace the PRNG, even when
16331 HardwareAccel is set. The only default builtin PRNG engine uses
16332 the Intel RDRAND instruction to replace the entire PRNG, and
16333 ignores all attempts to seed it with more entropy. That's
16334 cryptographically stupid: the right response to a new alleged
16335 entropy source is never to discard all previously used entropy
16336 sources. Fixes bug 10402; works around behavior introduced in
16337 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16339 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16340 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16341 - Avoid launching spurious extra circuits when a stream is pending.
16342 This fixes a bug where any circuit that _wasn't_ unusable for new
16343 streams would be treated as if it were, causing extra circuits to
16344 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16346 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16347 - No longer stop reading or writing on cpuworker connections when
16348 our rate limiting buckets go empty. Now we should handle circuit
16349 handshake requests more promptly. Resolves bug 9731.
16350 - Stop trying to bootstrap all our directory information from
16351 only our first guard. Discovered while fixing bug 9946; bugfix
16354 o Minor features (bridges, pluggable transports):
16355 - Add threshold cutoffs to the networkstatus document created by
16356 the Bridge Authority. Fixes bug 1117.
16357 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16358 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16359 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16360 Vidalia set this option for us.) Implements ticket 10297.
16362 o Minor features (security):
16363 - Always clear OpenSSL bignums before freeing them -- even bignums
16364 that don't contain secrets. Resolves ticket 10793. Patch by
16367 o Minor features (config options and command line):
16368 - Add an --allow-missing-torrc commandline option that tells Tor to
16369 run even if the configuration file specified by -f is not available.
16370 Implements ticket 10060.
16371 - Add support for the TPROXY transparent proxying facility on Linux.
16372 See documentation for the new TransProxyType option for more
16373 details. Implementation by "thomo". Closes ticket 10582.
16375 o Minor features (controller):
16376 - Add a new "HS_DESC" controller event that reports activities
16377 related to hidden service descriptors. Resolves ticket 8510.
16378 - New "DROPGUARDS" controller command to forget all current entry
16379 guards. Not recommended for ordinary use, since replacing guards
16380 too frequently makes several attacks easier. Resolves ticket 9934;
16383 o Minor features (build):
16384 - Assume that a user using ./configure --host wants to cross-compile,
16385 and give an error if we cannot find a properly named
16386 tool-chain. Add a --disable-tool-name-check option to proceed
16387 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16388 - If we run ./configure and the compiler recognizes -fstack-protector
16389 but the linker rejects it, warn the user about a potentially missing
16390 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16392 o Minor features (testing):
16393 - If Python is installed, "make check" now runs extra tests beyond
16394 the unit test scripts.
16395 - When bootstrapping a test network, sometimes very few relays get
16396 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16397 specify a set of relays which should be voted Guard regardless of
16398 their uptime or bandwidth. Addresses ticket 9206.
16400 o Minor features (log messages):
16401 - When ServerTransportPlugin is set on a bridge, Tor can write more
16402 useful statistics about bridge use in its extrainfo descriptors,
16403 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16404 log message to inform the user in this case. Resolves ticket 9651.
16405 - When receiving a new controller connection, log the origin address.
16406 Resolves ticket 9698; patch from "sigpipe".
16407 - When logging OpenSSL engine status at startup, log the status of
16408 more engines. Fixes ticket 10043; patch from Joshua Datko.
16409 - Turn "circuit handshake stats since last time" log messages into a
16410 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16412 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16413 - Improve the circuit queue out-of-memory handler. Previously, when
16414 we ran low on memory, we'd close whichever circuits had the most
16415 queued cells. Now, we close those that have the *oldest* queued
16416 cells, on the theory that those are most responsible for us
16417 running low on memory. Based on analysis from a forthcoming paper
16418 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16419 - Generate bootstrapping status update events correctly when fetching
16420 microdescriptors. Fixes bug 9927.
16421 - Update to the October 2 2013 Maxmind GeoLite Country database.
16423 o Minor bugfixes (clients):
16424 - When closing a channel that has already been open, do not close
16425 pending circuits that were waiting to connect to the same relay.
16426 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16429 o Minor bugfixes (relays):
16430 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16431 exit node as a NOROUTE error, not an INTERNAL error, since they
16432 can apparently happen when trying to connect to the wrong sort
16433 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16435 o Minor bugfixes (bridges):
16436 - Fix a bug where the first connection works to a bridge that uses a
16437 pluggable transport with client-side parameters, but we don't send
16438 the client-side parameters on subsequent connections. (We don't
16439 use any pluggable transports with client-side parameters yet,
16440 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16441 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16443 o Minor bugfixes (node selection):
16444 - If ExcludeNodes is set, consider non-excluded hidden service
16445 directory servers before excluded ones. Do not consider excluded
16446 hidden service directory servers at all if StrictNodes is
16447 set. (Previously, we would sometimes decide to connect to those
16448 servers, and then realize before we initiated a connection that
16449 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16450 Reported by "mr-4".
16451 - If we set the ExitNodes option but it doesn't include any nodes
16452 that have the Exit flag, we would choose not to bootstrap. Now we
16453 bootstrap so long as ExitNodes includes nodes which can exit to
16454 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16456 o Minor bugfixes (controller and command-line):
16457 - If changing a config option via "setconf" fails in a recoverable
16458 way, we used to nonetheless write our new control ports to the
16459 file described by the "ControlPortWriteToFile" option. Now we only
16460 write out that file if we successfully switch to the new config
16461 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16462 - When a command-line option such as --version or --help that
16463 ordinarily implies --hush appears on the command line along with
16464 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16465 only if it appeared later on the command line. Fixes bug 9578;
16466 bugfix on 0.2.5.1-alpha.
16468 o Minor bugfixes (code correctness):
16469 - Previously we used two temporary files when writing descriptors to
16470 disk; now we only use one. Fixes bug 1376.
16471 - Remove an erroneous (but impossible and thus harmless) pointer
16472 comparison that would have allowed compilers to skip a bounds
16473 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16474 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16475 - Fix an always-true assertion in pluggable transports code so it
16476 actually checks what it was trying to check. Fixes bug 10046;
16477 bugfix on 0.2.3.9-alpha. Found by "dcb".
16479 o Minor bugfixes (protocol correctness):
16480 - When receiving a VERSIONS cell with an odd number of bytes, close
16481 the connection immediately since the cell is malformed. Fixes bug
16482 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16485 o Minor bugfixes (build):
16486 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16487 turned off (that is, without support for v2 link handshakes). Fixes
16488 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16489 - Fix compilation warnings and startup issues when running with
16490 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16492 - Fix compilation on Solaris 9, which didn't like us having an
16493 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16495 o Minor bugfixes (testing):
16496 - Fix a segmentation fault in our benchmark code when running with
16497 Fedora's OpenSSL package, or any other OpenSSL that provides
16498 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16500 o Minor bugfixes (log messages):
16501 - Fix a bug where clients using bridges would report themselves
16502 as 50% bootstrapped even without a live consensus document.
16503 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16504 - Suppress a warning where, if there's only one directory authority
16505 in the network, we would complain that votes and signatures cannot
16506 be uploaded to other directory authorities. Fixes bug 10842;
16507 bugfix on 0.2.2.26-beta.
16508 - Report bootstrapping progress correctly when we're downloading
16509 microdescriptors. We had updated our "do we have enough microdescs
16510 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16511 (see bug 5956), but we left the bootstrap status event logic at
16512 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16513 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16515 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16516 - Avoid a crash bug when starting with a corrupted microdescriptor
16517 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16518 - If we fail to dump a previously cached microdescriptor to disk, avoid
16519 freeing duplicate data later on. Fixes bug 10423; bugfix on
16520 0.2.4.13-alpha. Spotted by "bobnomnom".
16522 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16523 - Correctly log long IPv6 exit policies, instead of truncating them
16524 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16525 - Our default TLS ecdhe groups were backwards: we meant to be using
16526 P224 for relays (for performance win) and P256 for bridges (since
16527 it is more common in the wild). Instead we had it backwards. After
16528 reconsideration, we decided that the default should be P256 on all
16529 hosts, since its security is probably better, and since P224 is
16530 reportedly used quite little in the wild. Found by "skruffy" on
16531 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16532 - Free directory authority certificate download statuses on exit
16533 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16535 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16536 - If the guard we choose first doesn't answer, we would try the
16537 second guard, but once we connected to the second guard we would
16538 abandon it and retry the first one, slowing down bootstrapping.
16539 The fix is to treat all our initially chosen guards as acceptable
16540 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16541 - Fix an assertion failure that would occur when disabling the
16542 ORPort setting on a running Tor process while accounting was
16543 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16544 - When examining the list of network interfaces to find our address,
16545 do not consider non-running or disabled network interfaces. Fixes
16546 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16547 - Avoid an off-by-one error when checking buffer boundaries when
16548 formatting the exit status of a pluggable transport helper.
16549 This is probably not an exploitable bug, but better safe than
16550 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16553 o Removed code and features:
16554 - Clients now reject any directory authority certificates lacking
16555 a dir-key-crosscert element. These have been included since
16556 0.2.1.9-alpha, so there's no real reason for them to be optional
16557 any longer. Completes proposal 157. Resolves ticket 10162.
16558 - Remove all code that existed to support the v2 directory system,
16559 since there are no longer any v2 directory authorities. Resolves
16561 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16562 options, which were used for designating authorities as "Hidden
16563 service authorities". There has been no use of hidden service
16564 authorities since 0.2.2.1-alpha, when we stopped uploading or
16565 downloading v0 hidden service descriptors. Fixes bug 10881; also
16566 part of a fix for bug 10841.
16568 o Code simplification and refactoring:
16569 - Remove some old fallback code designed to keep Tor clients working
16570 in a network with only two working relays. Elsewhere in the code we
16571 have long since stopped supporting such networks, so there wasn't
16572 much point in keeping it around. Addresses ticket 9926.
16573 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16574 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16575 - Remove data structures which were introduced to implement the
16576 CellStatistics option: they are now redundant with the addition
16577 of a timestamp to the regular packed_cell_t data structure, which
16578 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16581 o Documentation (man page) fixes:
16582 - Update manpage to describe some of the files you can expect to
16583 find in Tor's DataDirectory. Addresses ticket 9839.
16584 - Document that all but one DirPort entry must have the NoAdvertise
16585 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16587 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16588 - Clarify the usage and risks of setting the ContactInfo torrc line
16589 for your relay or bridge. Resolves ticket 9854.
16590 - Add anchors to the manpage so we can link to the html version of
16591 the documentation for specific options. Resolves ticket 9866.
16592 - Replace remaining references to DirServer in man page and
16593 log entries. Resolves ticket 10124.
16596 - Make the "tor-gencert" tool used by directory authority operators
16597 create 2048-bit signing keys by default (rather than 1024-bit, since
16598 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16601 Changes in version 0.2.4.20 - 2013-12-22
16602 Tor 0.2.4.20 fixes potentially poor random number generation for users
16603 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16604 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16605 and 4) have no state file in their DataDirectory (as would happen on
16606 first start). Users who generated relay or hidden service identity
16607 keys in such a situation should discard them and generate new ones.
16609 This release also fixes a logic error that caused Tor clients to build
16610 many more preemptive circuits than they actually need.
16613 - Do not allow OpenSSL engines to replace the PRNG, even when
16614 HardwareAccel is set. The only default builtin PRNG engine uses
16615 the Intel RDRAND instruction to replace the entire PRNG, and
16616 ignores all attempts to seed it with more entropy. That's
16617 cryptographically stupid: the right response to a new alleged
16618 entropy source is never to discard all previously used entropy
16619 sources. Fixes bug 10402; works around behavior introduced in
16620 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16622 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16623 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16624 - Avoid launching spurious extra circuits when a stream is pending.
16625 This fixes a bug where any circuit that _wasn't_ unusable for new
16626 streams would be treated as if it were, causing extra circuits to
16627 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16630 - Avoid a crash bug when starting with a corrupted microdescriptor
16631 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16632 - If we fail to dump a previously cached microdescriptor to disk, avoid
16633 freeing duplicate data later on. Fixes bug 10423; bugfix on
16634 0.2.4.13-alpha. Spotted by "bobnomnom".
16637 Changes in version 0.2.4.19 - 2013-12-11
16638 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16639 (1986-2013). Aaron worked on diverse projects including helping to guide
16640 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16641 transparency to the U.S government's PACER documents, and contributing
16642 design and development for Tor and Tor2Web. Aaron was one of the latest
16643 martyrs in our collective fight for civil liberties and human rights,
16644 and his death is all the more painful because he was one of us.
16646 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16647 a new circuit handshake and link encryption that use ECC to provide
16648 better security and efficiency; makes relays better manage circuit
16649 creation requests; uses "directory guards" to reduce client enumeration
16650 risks; makes bridges collect and report statistics about the pluggable
16651 transports they support; cleans up and improves our geoip database;
16652 gets much closer to IPv6 support for clients, bridges, and relays; makes
16653 directory authorities use measured bandwidths rather than advertised
16654 ones when computing flags and thresholds; disables client-side DNS
16655 caching to reduce tracking risks; and fixes a big bug in bridge
16656 reachability testing. This release introduces two new design
16657 abstractions in the code: a new "channel" abstraction between circuits
16658 and or_connections to allow for implementing alternate relay-to-relay
16659 transports, and a new "circuitmux" abstraction storing the queue of
16660 circuits for a channel. The release also includes many stability,
16661 security, and privacy fixes.
16664 Changes in version 0.2.4.18-rc - 2013-11-16
16665 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
16666 series. It takes a variety of fixes from the 0.2.5.x branch to improve
16667 stability, performance, and better handling of edge cases.
16670 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16671 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16672 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16673 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16674 them to solve bug 6033.)
16677 - No longer stop reading or writing on cpuworker connections when
16678 our rate limiting buckets go empty. Now we should handle circuit
16679 handshake requests more promptly. Resolves bug 9731.
16680 - If we are unable to save a microdescriptor to the journal, do not
16681 drop it from memory and then reattempt downloading it. Fixes bug
16682 9645; bugfix on 0.2.2.6-alpha.
16683 - Stop trying to bootstrap all our directory information from
16684 only our first guard. Discovered while fixing bug 9946; bugfix
16686 - The new channel code sometimes lost track of in-progress circuits,
16687 causing long-running clients to stop building new circuits. The
16688 fix is to always call circuit_n_chan_done(chan, 0) from
16689 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16691 o Minor bugfixes (on 0.2.4.x):
16692 - Correctly log long IPv6 exit policies, instead of truncating them
16693 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16694 - Our default TLS ecdhe groups were backwards: we meant to be using
16695 P224 for relays (for performance win) and P256 for bridges (since
16696 it is more common in the wild). Instead we had it backwards. After
16697 reconsideration, we decided that the default should be P256 on all
16698 hosts, since its security is probably better, and since P224 is
16699 reportedly used quite little in the wild. Found by "skruffy" on
16700 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16701 - Free directory authority certificate download statuses on exit
16702 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16704 o Minor bugfixes (on 0.2.3.x and earlier):
16705 - If the guard we choose first doesn't answer, we would try the
16706 second guard, but once we connected to the second guard we would
16707 abandon it and retry the first one, slowing down bootstrapping.
16708 The fix is to treat all our initially chosen guards as acceptable
16709 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16710 - Fix an assertion failure that would occur when disabling the
16711 ORPort setting on a running Tor process while accounting was
16712 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16713 - When examining the list of network interfaces to find our address,
16714 do not consider non-running or disabled network interfaces. Fixes
16715 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16716 - Avoid an off-by-one error when checking buffer boundaries when
16717 formatting the exit status of a pluggable transport helper.
16718 This is probably not an exploitable bug, but better safe than
16719 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16722 o Minor features (protecting client timestamps):
16723 - Clients no longer send timestamps in their NETINFO cells. These were
16724 not used for anything, and they provided one small way for clients
16725 to be distinguished from each other as they moved from network to
16726 network or behind NAT. Implements part of proposal 222.
16727 - Clients now round timestamps in INTRODUCE cells down to the nearest
16728 10 minutes. If a new Support022HiddenServices option is set to 0, or
16729 if it's set to "auto" and the feature is disabled in the consensus,
16730 the timestamp is sent as 0 instead. Implements part of proposal 222.
16731 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16732 a big deal from a security point of view, but it achieves no actual
16733 good purpose, and isn't needed. Implements part of proposal 222.
16734 - Reduce down accuracy of timestamps in hidden service descriptors.
16735 Implements part of proposal 222.
16737 o Minor features (other):
16738 - Improve the circuit queue out-of-memory handler. Previously, when
16739 we ran low on memory, we'd close whichever circuits had the most
16740 queued cells. Now, we close those that have the *oldest* queued
16741 cells, on the theory that those are most responsible for us
16742 running low on memory. Based on analysis from a forthcoming paper
16743 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16744 - Generate bootstrapping status update events correctly when fetching
16745 microdescriptors. Fixes bug 9927.
16746 - Update to the October 2 2013 Maxmind GeoLite Country database.
16748 o Documentation fixes:
16749 - Clarify the usage and risks of setting the ContactInfo torrc line
16750 for your relay or bridge. Resolves ticket 9854.
16751 - Add anchors to the manpage so we can link to the html version of
16752 the documentation for specific options. Resolves ticket 9866.
16753 - Replace remaining references to DirServer in man page and
16754 log entries. Resolves ticket 10124.
16757 Changes in version 0.2.5.1-alpha - 2013-10-02
16758 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
16759 on Linux, allows bridges that offer pluggable transports to report usage
16760 statistics, fixes many issues to make testing easier, and provides
16761 a pile of minor features and bugfixes that have been waiting for a
16762 release of the new branch.
16764 This is the first alpha release in a new series, so expect there to
16765 be bugs. Users who would rather test out a more stable branch should
16766 stay with 0.2.4.x for now.
16768 o Major features (security):
16769 - Use the seccomp2 syscall filtering facility on Linux to limit
16770 which system calls Tor can invoke. This is an experimental,
16771 Linux-only feature to provide defense-in-depth against unknown
16772 attacks. To try turning it on, set "Sandbox 1" in your torrc
16773 file. Please be ready to report bugs. We hope to add support
16774 for better sandboxing in the future, including more fine-grained
16775 filters, better division of responsibility, and support for more
16776 platforms. This work has been done by Cristian-Matei Toader for
16777 Google Summer of Code.
16778 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16779 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16780 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16781 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16782 them to solve bug 6033.)
16784 o Major features (other):
16785 - Add support for passing arguments to managed pluggable transport
16786 proxies. Implements ticket 3594.
16787 - Bridges now track GeoIP information and the number of their users
16788 even when pluggable transports are in use, and report usage
16789 statistics in their extra-info descriptors. Resolves tickets 4773
16791 - Make testing Tor networks bootstrap better: lower directory fetch
16792 retry schedules and maximum interval without directory requests,
16793 and raise maximum download tries. Implements ticket 6752.
16794 - Add make target 'test-network' to run tests on a Chutney network.
16795 Implements ticket 8530.
16796 - The ntor handshake is now on-by-default, no matter what the
16797 directory authorities recommend. Implements ticket 8561.
16800 - Instead of writing destroy cells directly to outgoing connection
16801 buffers, queue them and intersperse them with other outgoing cells.
16802 This can prevent a set of resource starvation conditions where too
16803 many pending destroy cells prevent data cells from actually getting
16804 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
16805 bugfix on 0.2.0.1-alpha.
16806 - If we are unable to save a microdescriptor to the journal, do not
16807 drop it from memory and then reattempt downloading it. Fixes bug
16808 9645; bugfix on 0.2.2.6-alpha.
16809 - The new channel code sometimes lost track of in-progress circuits,
16810 causing long-running clients to stop building new circuits. The
16811 fix is to always call circuit_n_chan_done(chan, 0) from
16812 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16815 - Tor now builds each source file in two modes: a mode that avoids
16816 exposing identifiers needlessly, and another mode that exposes
16817 more identifiers for testing. This lets the compiler do better at
16818 optimizing the production code, while enabling us to take more
16819 radical measures to let the unit tests test things.
16820 - The production builds no longer include functions used only in
16821 the unit tests; all functions exposed from a module only for
16822 unit-testing are now static in production builds.
16823 - Add an --enable-coverage configuration option to make the unit
16824 tests (and a new src/or/tor-cov target) to build with gcov test
16828 - We now have rudimentary function mocking support that our unit
16829 tests can use to test functions in isolation. Function mocking
16830 lets the tests temporarily replace a function's dependencies with
16831 stub functions, so that the tests can check the function without
16832 invoking the other functions it calls.
16833 - Add more unit tests for the <circid,channel>->circuit map, and
16834 the destroy-cell-tracking code to fix bug 7912.
16835 - Unit tests for failing cases of the TAP onion handshake.
16836 - More unit tests for address-manipulation functions.
16838 o Minor features (protecting client timestamps):
16839 - Clients no longer send timestamps in their NETINFO cells. These were
16840 not used for anything, and they provided one small way for clients
16841 to be distinguished from each other as they moved from network to
16842 network or behind NAT. Implements part of proposal 222.
16843 - Clients now round timestamps in INTRODUCE cells down to the nearest
16844 10 minutes. If a new Support022HiddenServices option is set to 0, or
16845 if it's set to "auto" and the feature is disabled in the consensus,
16846 the timestamp is sent as 0 instead. Implements part of proposal 222.
16847 - Stop sending timestamps in AUTHENTICATE cells. This is not such
16848 a big deal from a security point of view, but it achieves no actual
16849 good purpose, and isn't needed. Implements part of proposal 222.
16850 - Reduce down accuracy of timestamps in hidden service descriptors.
16851 Implements part of proposal 222.
16853 o Minor features (config options):
16854 - Config (torrc) lines now handle fingerprints which are missing
16855 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
16856 - Support a --dump-config option to print some or all of the
16857 configured options. Mainly useful for debugging the command-line
16858 option parsing code. Helps resolve ticket 4647.
16859 - Raise awareness of safer logging: notify user of potentially
16860 unsafe config options, like logging more verbosely than severity
16861 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
16862 - Add a new configuration option TestingV3AuthVotingStartOffset
16863 that bootstraps a network faster by changing the timing for
16864 consensus votes. Addresses ticket 8532.
16865 - Add a new torrc option "ServerTransportOptions" that allows
16866 bridge operators to pass configuration parameters to their
16867 pluggable transports. Resolves ticket 8929.
16868 - The config (torrc) file now accepts bandwidth and space limits in
16869 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
16870 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
16873 o Minor features (build):
16874 - Add support for `--library-versions` flag. Implements ticket 6384.
16875 - Return the "unexpected sendme" warnings to a warn severity, but make
16876 them rate limited, to help diagnose ticket 8093.
16877 - Detect a missing asciidoc, and warn the user about it, during
16878 configure rather than at build time. Fixes issue 6506. Patch from
16881 o Minor features (other):
16882 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
16883 sockets in a single system call. Implements ticket 5129.
16884 - Log current accounting state (bytes sent and received + remaining
16885 time for the current accounting period) in the relay's heartbeat
16886 message. Implements ticket 5526; patch from Peter Retzlaff.
16887 - Implement the TRANSPORT_LAUNCHED control port event that
16888 notifies controllers about new launched pluggable
16889 transports. Resolves ticket 5609.
16890 - If we're using the pure-C 32-bit curve25519_donna implementation
16891 of curve25519, build it with the -fomit-frame-pointer option to
16892 make it go faster on register-starved hosts. This improves our
16893 handshake performance by about 6% on i386 hosts without nacl.
16894 Closes ticket 8109.
16895 - Update to the September 4 2013 Maxmind GeoLite Country database.
16898 - Set the listen() backlog limit to the largest actually supported
16899 on the system, not to the value in a header file. Fixes bug 9716;
16900 bugfix on every released Tor.
16901 - No longer accept malformed http headers when parsing urls from
16902 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
16903 bugfix on 0.0.6pre1.
16904 - In munge_extrainfo_into_routerinfo(), check the return value of
16905 memchr(). This would have been a serious issue if we ever passed
16906 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
16908 - On the chance that somebody manages to build Tor on a
16909 platform where time_t is unsigned, correct the way that
16910 microdesc_add_to_cache() handles negative time arguments.
16911 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
16912 - Reject relative control socket paths and emit a warning. Previously,
16913 single-component control socket paths would be rejected, but Tor
16914 would not log why it could not validate the config. Fixes bug 9258;
16915 bugfix on 0.2.3.16-alpha.
16917 o Minor bugfixes (command line):
16918 - Use a single command-line parser for parsing torrc options on the
16919 command line and for finding special command-line options to avoid
16920 inconsistent behavior for torrc option arguments that have the same
16921 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
16923 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
16924 9573; bugfix on 0.0.9pre5.
16926 o Minor fixes (build, auxiliary programs):
16927 - Stop preprocessing the "torify" script with autoconf, since
16928 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
16930 - The tor-fw-helper program now follows the standard convention and
16931 exits with status code "0" on success. Fixes bug 9030; bugfix on
16932 0.2.3.1-alpha. Patch by Arlo Breault.
16933 - Corrected ./configure advice for what openssl dev package you should
16934 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
16936 o Minor code improvements:
16937 - Remove constants and tests for PKCS1 padding; it's insecure and
16938 shouldn't be used for anything new. Fixes bug 8792; patch
16940 - Remove instances of strcpy() from the unit tests. They weren't
16941 hurting anything, since they were only in the unit tests, but it's
16942 embarrassing to have strcpy() in the code at all, and some analysis
16943 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
16944 0.2.3.8-alpha. Patch from Arlo Breault.
16946 o Removed features:
16947 - Remove migration code from when we renamed the "cached-routers"
16948 file to "cached-descriptors" back in 0.2.0.8-alpha. This
16949 incidentally resolves ticket 6502 by cleaning up the related code
16950 a bit. Patch from Akshay Hebbar.
16952 o Code simplification and refactoring:
16953 - Extract the common duplicated code for creating a subdirectory
16954 of the data directory and writing to a file in it. Fixes ticket
16955 4282; patch from Peter Retzlaff.
16956 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
16957 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
16958 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
16959 - Add a set of accessor functions for the circuit timeout data
16960 structure. Fixes ticket 6153; patch from "piet".
16961 - Clean up exit paths from connection_listener_new(). Closes ticket
16962 8789. Patch from Arlo Breault.
16963 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
16964 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
16965 - Use a doubly-linked list to implement the global circuit list.
16966 Resolves ticket 9108. Patch from Marek Majkowski.
16967 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
16970 Changes in version 0.2.4.17-rc - 2013-09-05
16971 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
16972 series. It adds an emergency step to help us tolerate the massive
16973 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
16974 circuit-level handshakes now effectively jump the queue compared to
16975 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
16976 big bug hindering bridge reachability tests.
16979 - Relays now process the new "NTor" circuit-level handshake requests
16980 with higher priority than the old "TAP" circuit-level handshake
16981 requests. We still process some TAP requests to not totally starve
16982 0.2.3 clients when NTor becomes popular. A new consensus parameter
16983 "NumNTorsPerTAP" lets us tune the balance later if we need to.
16984 Implements ticket 9574.
16987 - If the circuit build timeout logic is disabled (via the consensus,
16988 or because we are an authority), then don't build testing circuits.
16989 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
16990 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
16991 previously they did not, which prevented them from receiving
16992 successful connections from relays for self-test or bandwidth
16993 testing. Also, when a relay is extending a circuit to a bridge,
16994 it needs to send a NETINFO cell, even when the bridge hasn't sent
16995 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
16996 - If the time to download the next old-style networkstatus is in
16997 the future, do not decline to consider whether to download the
16998 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17002 - Avoid double-closing the listener socket in our socketpair()
17003 replacement (used on Windows) in the case where the addresses on
17004 our opened sockets don't match what we expected. Fixes bug 9400;
17005 bugfix on 0.0.2pre7. Found by Coverity.
17007 o Minor fixes (config options):
17008 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17009 ridiculously high value, by imposing a (ridiculously high) 30-day
17010 maximum on MaxCircuitDirtiness.
17011 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17012 message is logged at notice, not at info.
17013 - Warn and fail if a server is configured not to advertise any
17014 ORPorts at all. (We need *something* to put in our descriptor,
17015 or we just won't work.)
17018 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17019 and how many we complete, and log it every hour to help relay
17020 operators follow trends in network load. Addresses ticket 9658.
17021 - Update to the August 7 2013 Maxmind GeoLite Country database.
17024 Changes in version 0.2.4.16-rc - 2013-08-10
17025 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
17026 series. It fixes several crash bugs in the 0.2.4 branch.
17029 - Fix a bug in the voting algorithm that could yield incorrect results
17030 when a non-naming authority declared too many flags. Fixes bug 9200;
17031 bugfix on 0.2.0.3-alpha.
17032 - Fix an uninitialized read that could in some cases lead to a remote
17033 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
17034 Anybody running a hidden service on the experimental 0.2.4.x
17035 branch should upgrade. (This is, so far as we know, unrelated to
17037 - Avoid an assertion failure when processing DNS replies without the
17038 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
17039 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
17040 0.2.4.15-rc. Found by stem integration tests.
17043 - Fix an invalid memory read that occurred when a pluggable
17044 transport proxy failed its configuration protocol.
17045 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
17046 - When evaluating whether to use a connection that we haven't
17047 decided is canonical using a recent link protocol version,
17048 decide that it's canonical only if it used address _does_
17049 match the desired address. Fixes bug 9309; bugfix on
17050 0.2.4.4-alpha. Reported by skruffy.
17051 - Make the default behavior of NumDirectoryGuards be to track
17052 NumEntryGuards. Now a user who changes only NumEntryGuards will get
17053 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
17054 - Fix a spurious compilation warning with some older versions of
17055 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
17058 - Update to the July 3 2013 Maxmind GeoLite Country database.
17061 Changes in version 0.2.4.15-rc - 2013-07-01
17062 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
17063 series. It fixes a few smaller bugs, but generally appears stable.
17064 Please test it and let us know whether it is!
17067 - When receiving a new configuration file via the control port's
17068 LOADCONF command, do not treat the defaults file as absent.
17069 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17072 - Issue a warning when running with the bufferevents backend enabled.
17073 It's still not stable, and people should know that they're likely
17074 to hit unexpected problems. Closes ticket 9147.
17077 Changes in version 0.2.4.14-alpha - 2013-06-18
17078 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
17079 present in 0.2.4.13-alpha.
17082 - When we have too much memory queued in circuits (according to a new
17083 MaxMemInCellQueues option), close the circuits consuming the most
17084 memory. This prevents us from running out of memory as a relay if
17085 circuits fill up faster than they can be drained. Fixes bug 9063;
17086 bugfix on the 54th commit of Tor. This bug is a further fix beyond
17087 bug 6252, whose fix was merged into 0.2.3.21-rc.
17089 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
17090 where we tried to solve this issue simply by imposing an upper limit
17091 on the number of queued cells for a single circuit. That approach
17092 proved to be problematic, since there are ways to provoke clients to
17093 send a number of cells in excess of any such reasonable limit. Fixes
17094 bug 9072; bugfix on 0.2.4.13-alpha.
17096 - Limit hidden service descriptors to at most ten introduction
17097 points, to slow one kind of guard enumeration. Fixes bug 9002;
17098 bugfix on 0.1.1.11-alpha.
17101 Changes in version 0.2.4.13-alpha - 2013-06-14
17102 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
17103 vulnerabilities, makes socks5 username/password circuit isolation
17104 actually actually work (this time for sure!), and cleans up a bunch
17105 of other issues in preparation for a release candidate.
17107 o Major bugfixes (robustness):
17108 - Close any circuit that has too many cells queued on it. Fixes
17109 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
17110 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
17111 - Prevent the get_freelists() function from running off the end of
17112 the list of freelists if it somehow gets an unrecognized
17113 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17115 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17116 when an exit connection with optimistic data succeeds immediately
17117 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17119 - Fix a directory authority crash bug when building a consensus
17120 using an older consensus as its basis. Fixes bug 8833. Bugfix
17124 - Avoid a memory leak where we would leak a consensus body when we
17125 find that a consensus which we couldn't previously verify due to
17126 missing certificates is now verifiable. Fixes bug 8719; bugfix
17128 - We used to always request authority certificates by identity digest,
17129 meaning we'd get the newest one even when we wanted one with a
17130 different signing key. Then we would complain about being given
17131 a certificate we already had, and never get the one we really
17132 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17133 resource to request the one we want. Fixes bug 5595; bugfix on
17135 - Follow the socks5 protocol when offering username/password
17136 authentication. The fix for bug 8117 exposed this bug, and it
17137 turns out real-world applications like Pidgin do care. Bugfix on
17138 0.2.3.2-alpha; fixes bug 8879.
17139 - Prevent failures on Windows Vista and later when rebuilding the
17140 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
17141 bugfix on 0.2.4.12-alpha.
17144 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17145 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17146 - If for some reason we fail to write a microdescriptor while
17147 rebuilding the cache, do not let the annotations from that
17148 microdescriptor linger in the cache file, and do not let the
17149 microdescriptor stay recorded as present in its old location.
17150 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17151 - Fix a memory leak that would occur whenever a configuration
17152 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17153 - Paste the description for PathBias parameters from the man
17154 page into or.h, so the code documents them too. Fixes bug 7982;
17155 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
17156 - Relays now treat a changed IPv6 ORPort as sufficient reason to
17157 publish an updated descriptor. Fixes bug 6026; bugfix on
17159 - When launching a resolve request on behalf of an AF_UNIX control
17160 socket, omit the address field of the new entry connection, used in
17161 subsequent controller events, rather than letting tor_dup_addr()
17162 set it to "<unknown address type>". Fixes bug 8639; bugfix on
17165 o Minor bugfixes (log messages):
17166 - Fix a scaling issue in the path bias accounting code that
17167 resulted in "Bug:" log messages from either
17168 pathbias_scale_close_rates() or pathbias_count_build_success().
17169 This represents a bugfix on a previous bugfix: the original fix
17170 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
17172 - Give a less useless error message when the user asks for an IPv4
17173 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
17177 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
17178 to tolerate bug 8093 for now.
17179 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17180 in directory authority votes to describe whether they have enough
17181 measured bandwidths to ignore advertised (relay descriptor)
17182 bandwidth claims. Resolves ticket 8711.
17183 - Update to the June 5 2013 Maxmind GeoLite Country database.
17185 o Removed documentation:
17186 - Remove some of the older contents of doc/ as obsolete; move others
17187 to torspec.git. Fixes bug 8965.
17189 o Code simplification and refactoring:
17190 - Avoid using character buffers when constructing most directory
17191 objects: this approach was unwieldy and error-prone. Instead,
17192 build smartlists of strings, and concatenate them when done.
17195 Changes in version 0.2.4.12-alpha - 2013-04-18
17196 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
17197 process for lengthening the guard rotation period, makes directory
17198 authority opinions in the consensus a bit less gameable, makes socks5
17199 username/password circuit isolation actually work, and fixes a wide
17200 variety of other issues.
17203 - Raise the default time that a client keeps an entry guard from
17204 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17205 2012 paper. (We would make it even longer, but we need better client
17206 load balancing first.) Also, make the guard lifetime controllable
17207 via a new GuardLifetime torrc option and a GuardLifetime consensus
17208 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17209 - Directory authorities now prefer using measured bandwidths to
17210 advertised ones when computing flags and thresholds. Resolves
17212 - Directory authorities that have more than a threshold number
17213 of relays with measured bandwidths now treat relays with unmeasured
17214 bandwidths as having bandwidth 0. Resolves ticket 8435.
17216 o Major bugfixes (assert / resource use):
17217 - Avoid a bug where our response to TLS renegotiation under certain
17218 network conditions could lead to a busy-loop, with 100% CPU
17219 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17220 - Avoid an assertion when we discover that we'd like to write a cell
17221 onto a closing connection: just discard the cell. Fixes another
17222 case of bug 7350; bugfix on 0.2.4.4-alpha.
17224 o Major bugfixes (client-side privacy):
17225 - When we mark a circuit as unusable for new circuits, have it
17226 continue to be unusable for new circuits even if MaxCircuitDirtiness
17227 is increased too much at the wrong time, or the system clock jumps
17228 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17229 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17230 which have resolved to internal addresses") is set, apply that
17231 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17232 - When an exit relay rejects a stream with reason "exit policy", but
17233 we only know an exit policy summary (e.g. from the microdesc
17234 consensus) for it, do not mark the relay as useless for all exiting.
17235 Instead, mark just the circuit as unsuitable for that particular
17236 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17237 - Allow applications to get proper stream isolation with
17238 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17239 username/password authentication also offer "no authentication". Tor
17240 had previously preferred "no authentication", so the applications
17241 never actually sent Tor their auth details. Now Tor selects
17242 username/password authentication if it's offered. You can disable
17243 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17244 bug 8117; bugfix on 0.2.3.3-alpha.
17246 o Major bugfixes (other):
17247 - When unable to find any working directory nodes to use as a
17248 directory guard, give up rather than adding the same non-working
17249 nodes to the directory guard list over and over. Fixes bug 8231;
17250 bugfix on 0.2.4.8-alpha.
17253 - Reject as invalid most directory objects containing a NUL.
17254 Belt-and-suspender fix for bug 8037.
17255 - In our testsuite, create temporary directories with a bit more
17256 entropy in their name to make name collisions less likely. Fixes
17258 - Add CACHED keyword to ADDRMAP events in the control protocol
17259 to indicate whether a DNS result will be cached or not. Resolves
17261 - Update to the April 3 2013 Maxmind GeoLite Country database.
17263 o Minor features (build):
17264 - Detect and reject attempts to build Tor with threading support
17265 when OpenSSL has been compiled without threading support.
17267 - Clarify that when autoconf is checking for nacl, it is checking
17268 specifically for nacl with a fast curve25519 implementation.
17270 - Warn if building on a platform with an unsigned time_t: there
17271 are too many places where Tor currently assumes that time_t can
17272 hold negative values. We'd like to fix them all, but probably
17275 o Minor bugfixes (build):
17276 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17277 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17278 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17279 - Add the old src/or/micro-revision.i filename to CLEANFILES.
17280 On the off chance that somebody has one, it will go away as soon
17281 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
17282 - Build Tor correctly on 32-bit platforms where the compiler can build
17283 but not run code using the "uint128_t" construction. Fixes bug 8587;
17284 bugfix on 0.2.4.8-alpha.
17285 - Fix compilation warning with some versions of clang that would
17286 prefer the -Wswitch-enum compiler flag to warn about switch
17287 statements with missing enum values, even if those switch
17288 statements have a "default:" statement. Fixes bug 8598; bugfix
17291 o Minor bugfixes (protocol):
17292 - Fix the handling of a TRUNCATE cell when it arrives while the
17293 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17294 - Fix a misframing issue when reading the version numbers in a
17295 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17296 'version 1, version 2, and version 0x100', when it should have
17297 only included versions 1 and 2. Fixes bug 8059; bugfix on
17298 0.2.0.10-alpha. Reported pseudonymously.
17299 - Make the format and order of STREAM events for DNS lookups
17300 consistent among the various ways to launch DNS lookups. Fixes
17301 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17302 - Correct our check for which versions of Tor support the EXTEND2
17303 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
17304 later, when support was really added in version 0.2.4.8-alpha.
17305 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
17307 o Minor bugfixes (other):
17308 - Correctly store microdescriptors and extrainfo descriptors with
17309 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
17310 Bug reported by "cypherpunks".
17311 - Increase the width of the field used to remember a connection's
17312 link protocol version to two bytes. Harmless for now, since the
17313 only currently recognized versions are one byte long. Reported
17314 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17315 - If the state file's path bias counts are invalid (presumably from a
17316 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17317 additional checks and log messages to the scaling of Path Bias
17318 counts, in case there still are remaining issues with scaling.
17319 Should help resolve bug 8235.
17320 - Eliminate several instances where we use "Nickname=ID" to refer to
17321 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17322 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17323 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
17325 o Minor bugfixes (syscalls):
17326 - Always check the return values of functions fcntl() and
17327 setsockopt(). We don't believe these are ever actually failing in
17328 practice, but better safe than sorry. Also, checking these return
17329 values should please analysis tools like Coverity. Patch from
17330 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17331 - Use direct writes rather than stdio when building microdescriptor
17332 caches, in an attempt to mitigate bug 8031, or at least make it
17335 o Minor bugfixes (config):
17336 - When rejecting a configuration because we were unable to parse a
17337 quoted string, log an actual error message. Fixes bug 7950; bugfix
17339 - Behave correctly when the user disables LearnCircuitBuildTimeout
17340 but doesn't tell us what they would like the timeout to be. Fixes
17341 bug 6304; bugfix on 0.2.2.14-alpha.
17342 - When autodetecting the number of CPUs, use the number of available
17343 CPUs in preference to the number of configured CPUs. Inform the
17344 user if this reduces the number of available CPUs. Fixes bug 8002;
17345 bugfix on 0.2.3.1-alpha.
17346 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17347 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17348 bug 8180; bugfix on 0.2.3.11-alpha.
17349 - Allow TestingTorNetworks to override the 4096-byte minimum for
17350 the Fast threshold. Otherwise they can't bootstrap until they've
17351 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
17352 - Fix some logic errors when the user manually overrides the
17353 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
17356 o Minor bugfixes (log messages to help diagnose bugs):
17357 - If we fail to free a microdescriptor because of bug 7164, log
17358 the filename and line number from which we tried to free it.
17359 - Add another diagnostic to the heartbeat message: track and log
17360 overhead that TLS is adding to the data we write. If this is
17361 high, we are sending too little data to SSL_write at a time.
17362 Diagnostic for bug 7707.
17363 - Add more detail to a log message about relaxed timeouts, to help
17365 - Warn more aggressively when flushing microdescriptors to a
17366 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17367 or at least make it more diagnosable.
17368 - Improve debugging output to help track down bug 8185 ("Bug:
17369 outgoing relay cell has n_chan==NULL. Dropping.")
17370 - Log the purpose of a path-bias testing circuit correctly.
17371 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
17373 o Minor bugfixes (0.2.4.x log messages that were too noisy):
17374 - Don't attempt to relax the timeout of already opened 1-hop circuits.
17375 They might never timeout. This should eliminate some/all cases of
17376 the relaxed timeout log message.
17377 - Use circuit creation time for network liveness evaluation. This
17378 should eliminate warning log messages about liveness caused
17379 by changes in timeout evaluation. Fixes bug 6572; bugfix on
17381 - Reduce a path bias length check from notice to info. The message
17382 is triggered when creating controller circuits. Fixes bug 8196;
17383 bugfix on 0.2.4.8-alpha.
17384 - Fix a path state issue that triggered a notice during relay startup.
17385 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
17386 - Reduce occurrences of warns about circuit purpose in
17387 connection_ap_expire_building(). Fixes bug 8477; bugfix on
17390 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
17391 - If we encounter a write failure on a SOCKS connection before we
17392 finish our SOCKS handshake, don't warn that we closed the
17393 connection before we could send a SOCKS reply. Fixes bug 8427;
17394 bugfix on 0.1.0.1-rc.
17395 - Correctly recognize that [::1] is a loopback address. Fixes
17396 bug 8377; bugfix on 0.2.1.3-alpha.
17397 - Fix a directory authority warn caused when we have a large amount
17398 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17399 - Don't log inappropriate heartbeat messages when hibernating: a
17400 hibernating node is _expected_ to drop out of the consensus,
17401 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17402 bugfix on 0.2.3.1-alpha.
17403 - Don't complain about bootstrapping problems while hibernating.
17404 These complaints reflect a general code problem, but not one
17405 with any problematic effects (no connections are actually
17406 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17408 o Documentation fixes:
17409 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17410 names match. Fixes bug 7768.
17411 - Make the torify manpage no longer refer to tsocks; torify hasn't
17412 supported tsocks since 0.2.3.14-alpha.
17413 - Make the tor manpage no longer reference tsocks.
17414 - Fix the GeoIPExcludeUnknown documentation to refer to
17415 ExcludeExitNodes rather than the currently nonexistent
17416 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17419 - The tor-tsocks.conf is no longer distributed or installed. We
17420 recommend that tsocks users use torsocks instead. Resolves
17424 Changes in version 0.2.4.11-alpha - 2013-03-11
17425 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17426 more robust, makes hidden service authentication work again, and
17427 resolves a DPI fingerprint for Tor's SSL transport.
17429 o Major features (directory authorities):
17430 - Directory authorities now support a new consensus method (17)
17431 where they cap the published bandwidth of servers for which
17432 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17433 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17434 serve any v2 directory information. Now we can test disabling the
17435 old deprecated v2 directory format, and see whether doing so has
17436 any effect on network load. Begins to fix bug 6783.
17437 - Directory authorities now include inside each vote a statement of
17438 the performance thresholds they used when assigning flags.
17439 Implements ticket 8151.
17441 o Major bugfixes (directory authorities):
17442 - Stop marking every relay as having been down for one hour every
17443 time we restart a directory authority. These artificial downtimes
17444 were messing with our Stable and Guard flag calculations. Fixes
17445 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17447 o Major bugfixes (hidden services):
17448 - Allow hidden service authentication to succeed again. When we
17449 refactored the hidden service introduction code back
17450 in 0.2.4.1-alpha, we didn't update the code that checks
17451 whether authentication information is present, causing all
17452 authentication checks to return "false". Fix for bug 8207; bugfix
17453 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17455 o Minor features (relays, bridges):
17456 - Make bridge relays check once a minute for whether their IP
17457 address has changed, rather than only every 15 minutes. Resolves
17458 bugs 1913 and 1992.
17459 - Refactor resolve_my_address() so it returns the method by which we
17460 decided our public IP address (explicitly configured, resolved from
17461 explicit hostname, guessed from interfaces, learned by gethostname).
17462 Now we can provide more helpful log messages when a relay guesses
17463 its IP address incorrectly (e.g. due to unexpected lines in
17464 /etc/hosts). Resolves ticket 2267.
17465 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17466 microdescriptor-related dir requests, and only fall back to normal
17467 descriptors if none of their bridges can handle microdescriptors
17468 (as opposed to the fix in ticket 4013, which caused them to fall
17469 back to normal descriptors if *any* of their bridges preferred
17470 them). Resolves ticket 4994.
17471 - Randomize the lifetime of our SSL link certificate, so censors can't
17472 use the static value for filtering Tor flows. Resolves ticket 8443;
17473 related to ticket 4014 which was included in 0.2.2.33.
17474 - Support a new version of the link protocol that allows 4-byte circuit
17475 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17476 a possible resource exhaustion issue. Closes ticket 7351; implements
17479 o Minor features (portability):
17480 - Tweak the curve25519-donna*.c implementations to tolerate systems
17481 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17482 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17483 the signs of types during autoconf. This is better than our old
17484 approach, which didn't work when cross-compiling.
17485 - Detect the sign of enum values, rather than assuming that MSC is the
17486 only compiler where enum types are all signed. Fixes bug 7727;
17487 bugfix on 0.2.4.10-alpha.
17489 o Minor features (other):
17490 - Say "KBytes" rather than "KB" in the man page (for various values
17491 of K), to further reduce confusion about whether Tor counts in
17492 units of memory or fractions of units of memory. Resolves ticket 7054.
17493 - Clear the high bit on curve25519 public keys before passing them to
17494 our backend, in case we ever wind up using a backend that doesn't do
17495 so itself. If we used such a backend, and *didn't* clear the high bit,
17496 we could wind up in a situation where users with such backends would
17497 be distinguishable from users without. Fixes bug 8121; bugfix on
17499 - Update to the March 6 2013 Maxmind GeoLite Country database.
17501 o Minor bugfixes (clients):
17502 - When we receive a RELAY_END cell with the reason DONE, or with no
17503 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17504 status as "connection refused". Previously we reported these cases
17505 as success but then immediately closed the connection. Fixes bug
17506 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17507 - Downgrade an assertion in connection_ap_expire_beginning to an
17508 LD_BUG message. The fix for bug 8024 should prevent this message
17509 from displaying, but just in case, a warn that we can diagnose
17510 is better than more assert crashes. Fixes bug 8065; bugfix on
17512 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17513 Also make the rate limiting flags for the path use bias log messages
17514 independent from the original path bias flags. Fixes bug 8161;
17515 bugfix on 0.2.4.10-alpha.
17517 o Minor bugfixes (relays):
17518 - Stop trying to resolve our hostname so often (e.g. every time we
17519 think about doing a directory fetch). Now we reuse the cached
17520 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17521 and 2410 (bugfix on 0.1.2.2-alpha).
17522 - Stop sending a stray "(null)" in some cases for the server status
17523 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17525 - When choosing which stream on a formerly stalled circuit to wake
17526 first, make better use of the platform's weak RNG. Previously,
17527 we had been using the % ("modulo") operator to try to generate a
17528 1/N chance of picking each stream, but this behaves badly with
17529 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17531 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17532 Irix's random() only return 15 bits; Solaris's random() returns more
17533 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17534 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17536 o Minor bugfixes (directory authorities):
17537 - Directory authorities now use less space when formatting identical
17538 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17541 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17542 - Avoid leaking memory if we fail to compute a consensus signature
17543 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17544 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17546 - Fix a memory leak during safe-cookie controller authentication.
17547 Bugfix on 0.2.3.13-alpha.
17548 - Avoid memory leak of IPv6 policy content if we fail to format it into
17549 a router descriptor. Bugfix on 0.2.4.7-alpha.
17551 o Minor bugfixes (other code correctness issues):
17552 - Avoid a crash if we fail to generate an extrainfo descriptor.
17553 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17554 this is CID 718634.
17555 - When detecting the largest possible file descriptor (in order to
17556 close all file descriptors when launching a new program), actually
17557 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17558 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17560 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17561 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17562 Bugfix on 0.2.4.10-alpha.
17563 - Fix an impossible-to-trigger integer overflow when estimating how
17564 long our onionskin queue would take. (This overflow would require us
17565 to accept 4 million onionskins before processing 100 of them.) Fixes
17566 bug 8210; bugfix on 0.2.4.10-alpha.
17568 o Code simplification and refactoring:
17569 - Add a wrapper function for the common "log a message with a
17573 Changes in version 0.2.4.10-alpha - 2013-02-04
17574 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17575 certain attacks that flood the network with relays; changes the queue
17576 for circuit create requests from a sized-based limit to a time-based
17577 limit; resumes building with MSVC on Windows; and fixes a wide variety
17580 o Major bugfixes (directory authority):
17581 - When computing directory thresholds, ignore any rejected-as-sybil
17582 nodes during the computation so that they can't influence Fast,
17583 Guard, etc. (We should have done this for proposal 109.) Fixes
17585 - When marking a node as a likely sybil, reset its uptime metrics
17586 to zero, so that it cannot time towards getting marked as Guard,
17587 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17591 - When a TLS write is partially successful but incomplete, remember
17592 that the flushed part has been flushed, and notice that bytes were
17593 actually written. Reported and fixed pseudonymously. Fixes bug
17594 7708; bugfix on Tor 0.1.0.5-rc.
17595 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17596 ID: these could be used to create unexpected streams and circuits
17597 which would count as "present" to some parts of Tor but "absent"
17598 to others, leading to zombie circuits and streams or to a bandwidth
17599 denial-of-service. Fixes bug 7889; bugfix on every released version
17600 of Tor. Reported by "oftc_must_be_destroyed".
17601 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17602 This change seems the only good way to permanently prevent conflicts
17603 with queue.h on various operating systems. Fixes bug 8107; bugfix
17606 o Major features (relay):
17607 - Instead of limiting the number of queued onionskins (aka circuit
17608 create requests) to a fixed, hard-to-configure number, we limit
17609 the size of the queue based on how many we expect to be able to
17610 process in a given amount of time. We estimate the time it will
17611 take to process an onionskin based on average processing time
17612 of previous onionskins. Closes ticket 7291. You'll never have to
17613 configure MaxOnionsPending again.
17615 o Major features (portability):
17616 - Resume building correctly with MSVC and Makefile.nmake. This patch
17617 resolves numerous bugs and fixes reported by ultramage, including
17618 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17619 - Make the ntor and curve25519 code build correctly with MSVC.
17620 Fix on 0.2.4.8-alpha.
17623 - When directory authorities are computing thresholds for flags,
17624 never let the threshold for the Fast flag fall below 4096
17625 bytes. Also, do not consider nodes with extremely low bandwidths
17626 when deciding thresholds for various directory flags. This change
17627 should raise our threshold for Fast relays, possibly in turn
17628 improving overall network performance; see ticket 1854. Resolves
17630 - The Tor client now ignores sub-domain components of a .onion
17631 address. This change makes HTTP "virtual" hosting
17632 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17633 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17634 hosted on the same hidden service. Implements proposal 204.
17635 - We compute the overhead from passing onionskins back and forth to
17636 cpuworkers, and report it when dumping statistics in response to
17637 SIGUSR1. Supports ticket 7291.
17639 o Minor features (path selection):
17640 - When deciding whether we have enough descriptors to build circuits,
17641 instead of looking at raw relay counts, look at which fraction
17642 of (bandwidth-weighted) paths we're able to build. This approach
17643 keeps clients from building circuits if their paths are likely to
17644 stand out statistically. The default fraction of paths needed is
17645 taken from the consensus directory; you can override it with the
17646 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17647 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17648 and we have GeoIP information, also exclude all nodes with unknown
17649 countries "??" and "A1". This behavior is controlled by the
17650 new GeoIPExcludeUnknown option: you can make such nodes always
17651 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17652 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17653 gets you the default behavior. Implements feature 7706.
17654 - Path Use Bias: Perform separate accounting for successful circuit
17655 use. Keep separate statistics on stream attempt rates versus stream
17656 success rates for each guard. Provide configurable thresholds to
17657 determine when to emit log messages or disable use of guards that
17658 fail too many stream attempts. Resolves ticket 7802.
17660 o Minor features (log messages):
17661 - When learning a fingerprint for a bridge, log its corresponding
17662 transport type. Implements ticket 7896.
17663 - Improve the log message when "Bug/attack: unexpected sendme cell
17664 from client" occurs, to help us track bug 8093.
17667 - Remove a couple of extraneous semicolons that were upsetting the
17668 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17669 bugfix on 0.2.2.1-alpha.
17670 - Remove a source of rounding error during path bias count scaling;
17671 don't count cannibalized circuits as used for path bias until we
17672 actually try to use them; and fix a circuit_package_relay_cell()
17673 warning message about n_chan==NULL. Fixes bug 7802.
17674 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
17675 actually link against nacl when we're configured to use it. Fixes
17676 bug 7972; bugfix on 0.2.4.8-alpha.
17677 - Compile correctly with the --disable-curve25519 option. Fixes
17678 bug 8153; bugfix on 0.2.4.8-alpha.
17680 o Build improvements:
17681 - Do not report status verbosely from autogen.sh unless the -v flag
17682 is specified. Fixes issue 4664. Patch from Onizuka.
17683 - Replace all calls to snprintf() outside of src/ext with
17684 tor_snprintf(). Also remove the #define to replace snprintf with
17685 _snprintf on Windows; they have different semantics, and all of
17686 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17687 - Try to detect if we are ever building on a platform where
17688 memset(...,0,...) does not set the value of a double to 0.0. Such
17689 platforms are permitted by the C standard, though in practice
17690 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17691 currently support them, but it's better to detect them and fail
17692 than to perform erroneously.
17694 o Removed features:
17695 - Stop exporting estimates of v2 and v3 directory traffic shares
17696 in extrainfo documents. They were unneeded and sometimes inaccurate.
17697 Also stop exporting any v2 directory request statistics. Resolves
17699 - Drop support for detecting and warning about versions of Libevent
17700 before 1.3e. Nothing reasonable ships with them any longer;
17701 warning the user about them shouldn't be needed. Resolves ticket
17704 o Code simplifications and refactoring:
17705 - Rename "isin" functions to "contains", for grammar. Resolves
17707 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
17708 with the natural logarithm function from the system libm. Resolves
17712 Changes in version 0.2.4.9-alpha - 2013-01-15
17713 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
17714 work more robustly.
17717 - Fix backward compatibility logic when receiving an embedded ntor
17718 handshake tunneled in a CREATE cell. This clears up the "Bug:
17719 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
17723 Changes in version 0.2.4.8-alpha - 2013-01-14
17724 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
17725 risks, adds a new stronger and faster circuit handshake, and offers
17726 stronger and faster link encryption when both sides support it.
17729 - Preliminary support for directory guards (proposal 207): when
17730 possible, clients now use their entry guards for non-anonymous
17731 directory requests. This can help prevent client enumeration. Note
17732 that this behavior only works when we have a usable consensus
17733 directory, and when options about what to download are more or less
17734 standard. In the future we should re-bootstrap from our guards,
17735 rather than re-bootstrapping from the preconfigured list of
17736 directory sources that ships with Tor. Resolves ticket 6526.
17737 - Tor relays and clients now support a better CREATE/EXTEND cell
17738 format, allowing the sender to specify multiple address, identity,
17739 and handshake types. Implements Robert Ransom's proposal 200;
17740 closes ticket 7199.
17742 o Major features (new circuit handshake):
17743 - Tor now supports a new circuit extension handshake designed by Ian
17744 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
17745 circuit extension handshake, later called "TAP", was a bit slow
17746 (especially on the relay side), had a fragile security proof, and
17747 used weaker keys than we'd now prefer. The new circuit handshake
17748 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
17749 function, making it significantly more secure than the older
17750 handshake, and significantly faster. Tor can use one of two built-in
17751 pure-C curve25519-donna implementations by Adam Langley, or it
17752 can link against the "nacl" library for a tuned version if present.
17754 The built-in version is very fast for 64-bit systems when building
17755 with GCC. The built-in 32-bit version is still faster than the
17756 old TAP protocol, but using libnacl is better on most such hosts.
17758 Clients don't currently use this protocol by default, since
17759 comparatively few clients support it so far. To try it, set
17760 UseNTorHandshake to 1.
17762 Implements proposal 216; closes ticket 7202.
17764 o Major features (better link encryption):
17765 - Relays can now enable the ECDHE TLS ciphersuites when available
17766 and appropriate. These ciphersuites let us negotiate forward-secure
17767 TLS secret keys more safely and more efficiently than with our
17768 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
17769 public relays prefer the (faster) P224 group, and bridges prefer
17770 the (more common) P256 group; you can override this with the
17773 Enabling these ciphers was a little tricky, since for a long time,
17774 clients had been claiming to support them without actually doing
17775 so, in order to foil fingerprinting. But with the client-side
17776 implementation of proposal 198 in 0.2.3.17-beta, clients can now
17777 match the ciphers from recent Firefox versions *and* list the
17778 ciphers they actually mean, so relays can believe such clients
17779 when they advertise ECDHE support in their TLS ClientHello messages.
17781 This feature requires clients running 0.2.3.17-beta or later,
17782 and requires both sides to be running OpenSSL 1.0.0 or later
17783 with ECC support. OpenSSL 1.0.1, with the compile-time option
17784 "enable-ec_nistp_64_gcc_128", is highly recommended.
17786 Implements the relay side of proposal 198; closes ticket 7200.
17789 - Avoid crashing when, as a relay without IPv6-exit support, a
17790 client insists on getting an IPv6 address or nothing. Fixes bug
17791 7814; bugfix on 0.2.4.7-alpha.
17794 - Improve circuit build timeout handling for hidden services.
17795 In particular: adjust build timeouts more accurately depending
17796 upon the number of hop-RTTs that a particular circuit type
17797 undergoes. Additionally, launch intro circuits in parallel
17798 if they timeout, and take the first one to reply as valid.
17799 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
17800 separate error codes; or at least, don't break for that reason.
17801 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
17802 - Update to the January 2 2013 Maxmind GeoLite Country database.
17804 o Minor features (testing):
17805 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
17806 (P-256) Diffie-Hellman handshakes to src/or/bench.
17807 - Add benchmark functions to test onion handshake performance.
17809 o Minor features (path bias detection):
17810 - Alter the Path Bias log messages to be more descriptive in terms
17811 of reporting timeouts and other statistics.
17812 - Create three levels of Path Bias log messages, as opposed to just
17813 two. These are configurable via consensus as well as via the torrc
17814 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
17815 The default values are 0.70, 0.50, and 0.30 respectively.
17816 - Separate the log message levels from the decision to drop guards,
17817 which also is available via torrc option PathBiasDropGuards.
17818 PathBiasDropGuards still defaults to 0 (off).
17819 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
17820 in combination with PathBiasExtremeRate.
17821 - Increase the default values for PathBiasScaleThreshold and
17822 PathBiasCircThreshold from (200, 20) to (300, 150).
17823 - Add in circuit usage accounting to path bias. If we try to use a
17824 built circuit but fail for any reason, it counts as path bias.
17825 Certain classes of circuits where the adversary gets to pick your
17826 destination node are exempt from this accounting. Usage accounting
17827 can be specifically disabled via consensus parameter or torrc.
17828 - Convert all internal path bias state to double-precision floating
17829 point, to avoid roundoff error and other issues.
17830 - Only record path bias information for circuits that have completed
17831 *two* hops. Assuming end-to-end tagging is the attack vector, this
17832 makes us more resilient to ambient circuit failure without any
17833 detection capability loss.
17835 o Minor bugfixes (log messages):
17836 - Rate-limit the "No circuits are opened. Relaxed timeout for a
17837 circuit with channel state open..." message to once per hour to
17838 keep it from filling the notice logs. Mitigates bug 7799 but does
17839 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
17840 - Avoid spurious warnings when configuring multiple client ports of
17841 which only some are nonlocal. Previously, we had claimed that some
17842 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
17845 o Code simplifications and refactoring:
17846 - Get rid of a couple of harmless clang warnings, where we compared
17847 enums to ints. These warnings are newly introduced in clang 3.2.
17848 - Split the onion.c file into separate modules for the onion queue
17849 and the different handshakes it supports.
17850 - Remove the marshalling/unmarshalling code for sending requests to
17851 cpuworkers over a socket, and instead just send structs. The
17852 recipient will always be the same Tor binary as the sender, so
17853 any encoding is overkill.
17856 Changes in version 0.2.4.7-alpha - 2012-12-24
17857 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
17858 directory mirrors for more robust bootstrapping; fixes more issues where
17859 clients with changing network conditions refuse to make any circuits;
17860 adds initial support for exiting to IPv6 addresses; resumes being able
17861 to update our GeoIP database, and includes the geoip6 file this time;
17862 turns off the client-side DNS cache by default due to privacy risks;
17863 and fixes a variety of other issues.
17865 o Major features (client resilience):
17866 - Add a new "FallbackDir" torrc option to use when we can't use
17867 a directory mirror from the consensus (either because we lack a
17868 consensus, or because they're all down). Currently, all authorities
17869 are fallbacks by default, and there are no other default fallbacks,
17870 but that will change. This option will allow us to give clients a
17871 longer list of servers to try to get a consensus from when first
17872 connecting to the Tor network, and thereby reduce load on the
17873 directory authorities. Implements proposal 206, "Preconfigured
17874 directory sources for bootstrapping". We also removed the old
17875 "FallbackNetworkstatus" option, since we never got it working well
17876 enough to use it. Closes bug 572.
17877 - If we have no circuits open, use a relaxed timeout (the
17878 95-percentile cutoff) until a circuit succeeds. This heuristic
17879 should allow Tor to succeed at building circuits even when the
17880 network connection drastically changes. Should help with bug 3443.
17882 o Major features (IPv6):
17883 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
17884 connectivity, then set the IPv6Exit flag to 1. Also make sure your
17885 exit policy reads as you would like: the address * applies to all
17886 address families, whereas *4 is IPv4 address only, and *6 is IPv6
17887 addresses only. On the client side, you'll need to wait until the
17888 authorities have upgraded, wait for enough exits to support IPv6,
17889 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
17890 ticket 5547, implements proposal 117 as revised in proposal 208.
17892 We DO NOT recommend that clients with actual anonymity needs start
17893 using IPv6 over Tor yet, since not enough exits support it yet.
17895 o Major features (geoip database):
17896 - Maxmind began labelling Tor relays as being in country "A1",
17897 which breaks by-country node selection inside Tor. Now we use a
17898 script to replace "A1" ("Anonymous Proxy") entries in our geoip
17899 file with real country codes. This script fixes about 90% of "A1"
17900 entries automatically and uses manual country code assignments to
17901 fix the remaining 10%. See src/config/README.geoip for details.
17902 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
17903 Country database, as modified above.
17905 o Major bugfixes (client-side DNS):
17906 - Turn off the client-side DNS cache by default. Updating and using
17907 the DNS cache is now configurable on a per-client-port
17908 level. SOCKSPort, DNSPort, etc lines may now contain
17909 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
17910 cache these types of DNS answers when we receive them from an
17911 exit node in response to an application request on this port, and
17912 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
17913 cached DNS answers of these types, we shouldn't use them. It's
17914 potentially risky to use cached DNS answers at the client, since
17915 doing so can indicate to one exit what answers we've gotten
17916 for DNS lookups in the past. With IPv6, this becomes especially
17917 problematic. Using cached DNS answers for requests on the same
17918 circuit would present less linkability risk, since all traffic
17919 on a circuit is already linkable, but it would also provide
17920 little performance benefit: the exit node caches DNS replies
17921 too. Implements a simplified version of Proposal 205. Implements
17924 o Major bugfixes (other):
17925 - Alter circuit build timeout measurement to start at the point
17926 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
17927 initialization). This should make our timeout measurements more
17928 uniform. Previously, we were sometimes including ORconn setup time
17929 in our circuit build time measurements. Should resolve bug 3443.
17930 - Fix an assertion that could trigger in hibernate_go_dormant() when
17931 closing an or_connection_t: call channel_mark_for_close() rather
17932 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
17934 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
17935 7655; bugfix on 0.2.4.6-alpha.
17938 - Add a new torrc option "ServerTransportListenAddr" to let bridge
17939 operators select the address where their pluggable transports will
17940 listen for connections. Resolves ticket 7013.
17941 - Allow an optional $ before the node identity digest in the
17942 controller command GETINFO ns/id/<identity>, for consistency with
17943 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
17944 - Log packaged cell fullness as part of the heartbeat message.
17945 Diagnosis to try to determine the extent of bug 7743.
17947 o Minor features (IPv6):
17948 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
17949 prefer to hand out virtual IPv6 addresses, since there are more of
17950 them and we can't run out. To override this behavior and make IPv4
17951 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
17952 or DNSPort you're using for resolving. Implements ticket 7571.
17953 - AutomapHostsOnResolve responses are now randomized, to avoid
17954 annoying situations where Tor is restarted and applications
17955 connect to the wrong addresses.
17956 - Never try more than 1000 times to pick a new virtual address when
17957 AutomapHostsOnResolve is set. That's good enough so long as we
17958 aren't close to handing out our entire virtual address space;
17959 if you're getting there, it's best to switch to IPv6 virtual
17963 - The ADDRMAP command can no longer generate an ill-formed error
17964 code on a failed MAPADDRESS. It now says "internal" rather than
17965 an English sentence fragment with spaces in the middle. Bugfix on
17966 Tor 0.2.0.19-alpha.
17967 - Fix log messages and comments to avoid saying "GMT" when we mean
17968 "UTC". Fixes bug 6113.
17969 - Compile on win64 using mingw64. Fixes bug 7260; patches from
17971 - Fix a crash when debugging unit tests on Windows: deallocate a
17972 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
17973 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
17976 - The DirServer option is now DirAuthority, for consistency with
17977 current naming patterns. You can still use the old DirServer form.
17979 o Code simplification and refactoring:
17980 - Move the client-side address-map/virtual-address/DNS-cache code
17981 out of connection_edge.c into a new addressmap.c module.
17982 - Remove unused code for parsing v1 directories and "running routers"
17983 documents. Fixes bug 6887.
17986 Changes in version 0.2.3.25 - 2012-11-19
17987 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
17988 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
17989 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
17990 programmer, and friend. Unstinting in his dedication to the cause of
17991 freedom, he inspired and helped many of us as we began our work on
17992 anonymity, and inspires us still. Please honor his memory by writing
17993 software to protect people's freedoms, and by helping others to do so.
17995 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
17996 significantly reduced directory overhead (via microdescriptors),
17997 enormous crypto performance improvements for fast relays on new
17998 enough hardware, a new v3 TLS handshake protocol that can better
17999 resist fingerprinting, support for protocol obfuscation plugins (aka
18000 pluggable transports), better scalability for hidden services, IPv6
18001 support for bridges, performance improvements like allowing clients
18002 to skip the first round-trip on the circuit ("optimistic data") and
18003 refilling token buckets more often, a new "stream isolation" design
18004 to isolate different applications on different circuits, and many
18005 stability, security, and privacy fixes.
18008 - Tor tries to wipe potentially sensitive data after using it, so
18009 that if some subsequent security failure exposes Tor's memory,
18010 the damage will be limited. But we had a bug where the compiler
18011 was eliminating these wipe operations when it decided that the
18012 memory was no longer visible to a (correctly running) program,
18013 hence defeating our attempt at defense in depth. We fix that
18014 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18015 is unlikely to optimize away. Future versions of Tor may use
18016 a less ridiculously heavy approach for this. Fixes bug 7352.
18017 Reported in an article by Andrey Karpov.
18020 - Fix a harmless bug when opting against publishing a relay descriptor
18021 because DisableNetwork is set. Fixes bug 7464; bugfix on
18025 Changes in version 0.2.4.6-alpha - 2012-11-13
18026 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
18027 makes our defense-in-depth memory wiping more reliable, and begins to
18028 count IPv6 addresses in bridge statistics,
18031 - Fix an assertion failure that could occur when closing a connection
18032 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
18034 - Tor tries to wipe potentially sensitive data after using it, so
18035 that if some subsequent security failure exposes Tor's memory,
18036 the damage will be limited. But we had a bug where the compiler
18037 was eliminating these wipe operations when it decided that the
18038 memory was no longer visible to a (correctly running) program,
18039 hence defeating our attempt at defense in depth. We fix that
18040 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18041 is unlikely to optimize away. Future versions of Tor may use
18042 a less ridiculously heavy approach for this. Fixes bug 7352.
18043 Reported in an article by Andrey Karpov.
18046 - Add GeoIP database for IPv6 addresses. The new config option
18048 - Bridge statistics now count bridge clients connecting over IPv6:
18049 bridge statistics files now list "bridge-ip-versions" and
18050 extra-info documents list "geoip6-db-digest". The control protocol
18051 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18052 implementation by "shkoo", addressing ticket 5055.
18055 - Warn when we are binding low ports when hibernation is enabled;
18056 previously we had warned when we were _advertising_ low ports with
18057 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18058 - Fix a harmless bug when opting against publishing a relay descriptor
18059 because DisableNetwork is set. Fixes bug 7464; bugfix on
18061 - Add warning message when a managed proxy dies during configuration.
18062 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
18063 - Fix a linking error when building tor-fw-helper without miniupnp.
18064 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
18065 - Check for closing an or_connection_t without going through correct
18066 channel functions; emit a warning and then call
18067 connection_or_close_for_error() so we don't assert as in bugs 7212
18069 - Compile correctly on compilers without C99 designated initializer
18070 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
18071 - Avoid a possible assert that can occur when channel_send_destroy() is
18072 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
18073 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
18074 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
18075 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
18076 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
18078 o Code simplification and refactoring:
18079 - Start using OpenBSD's implementation of queue.h, so that we don't
18080 need to hand-roll our own pointer and list structures whenever we
18081 need them. (We can't rely on a sys/queue.h, since some operating
18082 systems don't have them, and the ones that do have them don't all
18083 present the same extensions.)
18086 Changes in version 0.2.4.5-alpha - 2012-10-25
18087 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
18088 two important security vulnerabilities that could lead to remotely
18089 triggerable relay crashes, fix a major bug that was preventing clients
18090 from choosing suitable exit nodes, and refactor some of our code.
18092 o Major bugfixes (security, also in 0.2.3.24-rc):
18093 - Fix a group of remotely triggerable assertion failures related to
18094 incorrect link protocol negotiation. Found, diagnosed, and fixed
18095 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18097 - Fix a denial of service attack by which any directory authority
18098 could crash all the others, or by which a single v2 directory
18099 authority could crash everybody downloading v2 directory
18100 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18102 o Major bugfixes (also in 0.2.3.24-rc):
18103 - When parsing exit policy summaries from microdescriptors, we had
18104 previously been ignoring the last character in each one, so that
18105 "accept 80,443,8080" would be treated by clients as indicating
18106 a node that allows access to ports 80, 443, and 808. That would
18107 lead to clients attempting connections that could never work,
18108 and ignoring exit nodes that would support their connections. Now
18109 clients parse these exit policy summaries correctly. Fixes bug 7192;
18110 bugfix on 0.2.3.1-alpha.
18112 o Minor bugfixes (also in 0.2.3.24-rc):
18113 - Clients now consider the ClientRejectInternalAddresses config option
18114 when using a microdescriptor consensus stanza to decide whether
18115 an exit relay would allow exiting to an internal address. Fixes
18116 bug 7190; bugfix on 0.2.3.1-alpha.
18119 - Only disable TLS session ticket support when running as a TLS
18120 server. Now clients will blend better with regular Firefox
18121 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18123 o Code simplification and refactoring:
18124 - Start using OpenBSD's implementation of queue.h (originally by
18126 - Move the entry node code from circuitbuild.c to its own file.
18127 - Move the circuit build timeout tracking code from circuitbuild.c
18131 Changes in version 0.2.3.24-rc - 2012-10-25
18132 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
18133 could lead to remotely triggerable relay crashes, and fixes
18134 a major bug that was preventing clients from choosing suitable exit
18137 o Major bugfixes (security):
18138 - Fix a group of remotely triggerable assertion failures related to
18139 incorrect link protocol negotiation. Found, diagnosed, and fixed
18140 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18142 - Fix a denial of service attack by which any directory authority
18143 could crash all the others, or by which a single v2 directory
18144 authority could crash everybody downloading v2 directory
18145 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18148 - When parsing exit policy summaries from microdescriptors, we had
18149 previously been ignoring the last character in each one, so that
18150 "accept 80,443,8080" would be treated by clients as indicating
18151 a node that allows access to ports 80, 443, and 808. That would
18152 lead to clients attempting connections that could never work,
18153 and ignoring exit nodes that would support their connections. Now
18154 clients parse these exit policy summaries correctly. Fixes bug 7192;
18155 bugfix on 0.2.3.1-alpha.
18158 - Clients now consider the ClientRejectInternalAddresses config option
18159 when using a microdescriptor consensus stanza to decide whether
18160 an exit relay would allow exiting to an internal address. Fixes
18161 bug 7190; bugfix on 0.2.3.1-alpha.
18164 Changes in version 0.2.4.4-alpha - 2012-10-20
18165 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
18166 vulnerability introduced by a change in OpenSSL, fixes a remotely
18167 triggerable assert, and adds new channel_t and circuitmux_t abstractions
18168 that will make it easier to test new connection transport and cell
18169 scheduling algorithms.
18171 o New directory authorities (also in 0.2.3.23-rc):
18172 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18173 authority. Closes ticket 5749.
18175 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
18176 - Disable TLS session tickets. OpenSSL's implementation was giving
18177 our TLS session keys the lifetime of our TLS context objects, when
18178 perfect forward secrecy would want us to discard anything that
18179 could decrypt a link connection as soon as the link connection
18180 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18181 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18182 - Discard extraneous renegotiation attempts once the V3 link
18183 protocol has been initiated. Failure to do so left us open to
18184 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18185 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18187 o Internal abstraction features:
18188 - Introduce new channel_t abstraction between circuits and
18189 or_connection_t to allow for implementing alternate OR-to-OR
18190 transports. A channel_t is an abstract object which can either be a
18191 cell-bearing channel, which is responsible for authenticating and
18192 handshaking with the remote OR and transmitting cells to and from
18193 it, or a listening channel, which spawns new cell-bearing channels
18194 at the request of remote ORs. Implements part of ticket 6465.
18195 - Also new is the channel_tls_t subclass of channel_t, adapting it
18196 to the existing or_connection_t code. The V2/V3 protocol handshaking
18197 code which formerly resided in command.c has been moved below the
18198 channel_t abstraction layer and may be found in channeltls.c now.
18199 Implements the rest of ticket 6465.
18200 - Introduce new circuitmux_t storing the queue of circuits for
18201 a channel; this encapsulates and abstracts the queue logic and
18202 circuit selection policy, and allows the latter to be overridden
18203 easily by switching out a policy object. The existing EWMA behavior
18204 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18206 o Required libraries:
18207 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18208 strongly recommended.
18211 - Warn users who run hidden services on a Tor client with
18212 UseEntryGuards disabled that their hidden services will be
18213 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18214 attack which motivated Tor to support entry guards in the first
18215 place). Resolves ticket 6889.
18216 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18217 dhill. Resolves ticket 6982.
18218 - Option OutboundBindAddress can be specified multiple times and
18219 accepts IPv6 addresses. Resolves ticket 6876.
18221 o Minor bugfixes (also in 0.2.3.23-rc):
18222 - Don't serve or accept v2 hidden service descriptors over a
18223 relay's DirPort. It's never correct to do so, and disabling it
18224 might make it more annoying to exploit any bugs that turn up in the
18225 descriptor-parsing code. Fixes bug 7149.
18226 - Fix two cases in src/or/transports.c where we were calling
18227 fmt_addr() twice in a parameter list. Bug found by David
18228 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18229 - Fix memory leaks whenever we logged any message about the "path
18230 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18231 - When relays refuse a "create" cell because their queue of pending
18232 create cells is too big (typically because their cpu can't keep up
18233 with the arrival rate), send back reason "resource limit" rather
18234 than reason "internal", so network measurement scripts can get a
18235 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
18238 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18239 - Free some more still-in-use memory at exit, to make hunting for
18240 memory leaks easier. Resolves bug 7029.
18241 - When a Tor client gets a "truncated" relay cell, the first byte of
18242 its payload specifies why the circuit was truncated. We were
18243 ignoring this 'reason' byte when tearing down the circuit, resulting
18244 in the controller not being told why the circuit closed. Now we
18245 pass the reason from the truncated cell to the controller. Bugfix
18246 on 0.1.2.3-alpha; fixes bug 7039.
18247 - Downgrade "Failed to hand off onionskin" messages to "debug"
18248 severity, since they're typically redundant with the "Your computer
18249 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18250 - Make clients running with IPv6 bridges connect over IPv6 again,
18251 even without setting new config options ClientUseIPv6 and
18252 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
18253 - Use square brackets around IPv6 addresses in numerous places
18254 that needed them, including log messages, HTTPS CONNECT proxy
18255 requests, TransportProxy statefile entries, and pluggable transport
18256 extra-info lines. Fixes bug 7011; patch by David Fifield.
18258 o Code refactoring and cleanup:
18259 - Source files taken from other packages now reside in src/ext;
18260 previously they were scattered around the rest of Tor.
18261 - Avoid use of reserved identifiers in our C code. The C standard
18262 doesn't like us declaring anything that starts with an
18263 underscore, so let's knock it off before we get in trouble. Fix
18264 for bug 1031; bugfix on the first Tor commit.
18267 Changes in version 0.2.3.23-rc - 2012-10-20
18268 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
18269 vulnerability introduced by a change in OpenSSL, and fixes a variety
18270 of smaller bugs in preparation for the release.
18272 o New directory authorities:
18273 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18274 authority. Closes ticket 5749.
18276 o Major bugfixes (security/privacy):
18277 - Disable TLS session tickets. OpenSSL's implementation was giving
18278 our TLS session keys the lifetime of our TLS context objects, when
18279 perfect forward secrecy would want us to discard anything that
18280 could decrypt a link connection as soon as the link connection
18281 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18282 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18283 - Discard extraneous renegotiation attempts once the V3 link
18284 protocol has been initiated. Failure to do so left us open to
18285 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18286 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18289 - Fix a possible crash bug when checking for deactivated circuits
18290 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18291 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18293 o Minor bugfixes (on 0.2.3.x):
18294 - Fix two cases in src/or/transports.c where we were calling
18295 fmt_addr() twice in a parameter list. Bug found by David
18296 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18297 - Convert an assert in the pathbias code to a log message. The assert
18298 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18299 bugfix on 0.2.3.17-beta.
18300 - Fix memory leaks whenever we logged any message about the "path
18301 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18303 o Minor bugfixes (on 0.2.2.x and earlier):
18304 - Don't serve or accept v2 hidden service descriptors over a relay's
18305 DirPort. It's never correct to do so, and disabling it might
18306 make it more annoying to exploit any bugs that turn up in the
18307 descriptor-parsing code. Fixes bug 7149.
18308 - When relays refuse a "create" cell because their queue of pending
18309 create cells is too big (typically because their cpu can't keep up
18310 with the arrival rate), send back reason "resource limit" rather
18311 than reason "internal", so network measurement scripts can get a
18312 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18313 - Correct file sizes when reading binary files on Cygwin, to avoid
18314 a bug where Tor would fail to read its state file. Fixes bug 6844;
18315 bugfix on 0.1.2.7-alpha.
18316 - Avoid undefined behavior when parsing the list of supported
18317 rendezvous/introduction protocols in a hidden service descriptor.
18318 Previously, Tor would have confused (as-yet-unused) protocol version
18319 numbers greater than 32 with lower ones on many platforms. Fixes
18320 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18322 o Documentation fixes:
18323 - Clarify that hidden services are TCP only. Fixes bug 6024.
18326 Changes in version 0.2.4.3-alpha - 2012-09-22
18327 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
18328 assertion, resumes letting relays test reachability of their DirPort,
18329 and cleans up a bunch of smaller bugs.
18332 - Fix an assertion failure in tor_timegm() that could be triggered
18333 by a badly formatted directory object. Bug found by fuzzing with
18334 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18337 - Fix a possible crash bug when checking for deactivated circuits
18338 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18339 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18340 - Allow routers to detect that their own DirPorts are running. When
18341 we removed support for versions_supports_begindir, we also
18342 accidentally removed the mechanism we used to self-test our
18343 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
18344 bugfix on 0.2.4.2-alpha.
18346 o Security features:
18347 - Switch to a completely time-invariant approach for picking nodes
18348 weighted by bandwidth. Our old approach would run through the
18349 part of the loop after it had made its choice slightly slower
18350 than it ran through the part of the loop before it had made its
18351 choice. Addresses ticket 6538.
18352 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18353 by tor2web clients allows hidden services to identify tor2web
18354 clients through their repeated selection of the same rendezvous
18355 and introduction point circuit endpoints (their guards). Resolves
18359 - Enable Tor to read configuration, state, and key information from
18360 a FIFO. Previously Tor would only read from files with a positive
18361 stat.st_size. Code from meejah; fixes bug 6044.
18364 - Correct file sizes when reading binary files on Cygwin, to avoid
18365 a bug where Tor would fail to read its state file. Fixes bug 6844;
18366 bugfix on 0.1.2.7-alpha.
18367 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18368 bugfix on 0.2.0.3-alpha.
18369 - When complaining about a client port on a public address, log
18370 which address we're complaining about. Fixes bug 4020; bugfix on
18371 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18372 - Convert an assert in the pathbias code to a log message. The assert
18373 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18374 bugfix on 0.2.3.17-beta.
18375 - Our new buildsystem was overzealous about rebuilding manpages: it
18376 would rebuild them all whenever any one of them changed. Now our
18377 dependency checking should be correct. Fixes bug 6843; bugfix on
18379 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
18380 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
18381 - Correct log printout about which address family is preferred
18382 when connecting to a bridge with both an IPv4 and IPv6 OR port.
18383 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
18385 o Minor bugfixes (code cleanliness):
18386 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18387 with large values. This situation was untriggered, but nevertheless
18388 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18389 - Reject consensus votes with more than 64 known-flags. We aren't even
18390 close to that limit yet, and our code doesn't handle it correctly.
18391 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18392 - Avoid undefined behavior when parsing the list of supported
18393 rendezvous/introduction protocols in a hidden service descriptor.
18394 Previously, Tor would have confused (as-yet-unused) protocol version
18395 numbers greater than 32 with lower ones on many platforms. Fixes
18396 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18397 - Fix handling of rendezvous client authorization types over 8.
18398 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18399 - Fix building with older versions of GCC (2.95, for one) that don't
18400 like preprocessor directives inside macro arguments. Found by
18401 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
18402 - Switch weighted node selection rule from using a list of doubles
18403 to using a list of int64_t. This change should make the process
18404 slightly easier to debug and maintain. Needed to finish ticket 6538.
18406 o Code simplification and refactoring:
18407 - Move the generic "config" code into a new file, and have "config.c"
18408 hold only torrc- and state-related code. Resolves ticket 6823.
18409 - Move the core of our "choose a weighted element at random" logic
18410 into its own function, and give it unit tests. Now the logic is
18411 testable, and a little less fragile too.
18412 - Removed the testing_since field of node_t, which hasn't been used
18413 for anything since 0.2.0.9-alpha.
18415 o Documentation fixes:
18416 - Clarify that hidden services are TCP only. Fixes bug 6024.
18417 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18421 Changes in version 0.2.3.22-rc - 2012-09-11
18422 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18426 - Fix an assertion failure in tor_timegm() that could be triggered
18427 by a badly formatted directory object. Bug found by fuzzing with
18428 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18431 - Avoid segfault when starting up having run with an extremely old
18432 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18436 Changes in version 0.2.2.39 - 2012-09-11
18437 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18441 - Fix an assertion failure in tor_timegm() that could be triggered
18442 by a badly formatted directory object. Bug found by fuzzing with
18443 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18444 - Do not crash when comparing an address with port value 0 to an
18445 address policy. This bug could have been used to cause a remote
18446 assertion failure by or against directory authorities, or to
18447 allow some applications to crash clients. Fixes bug 6690; bugfix
18451 Changes in version 0.2.4.2-alpha - 2012-09-10
18452 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18453 raises the default rate limiting even more, and makes the bootstrapping
18454 log messages less noisy.
18457 - Automatically forward the TCP ports of pluggable transport
18458 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18462 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18463 to 1GB/1GB. The previous defaults were intended to be "basically
18464 infinite", but it turns out they're now limiting our 100mbit+
18465 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18466 last time we raised it).
18469 - Detect when we're running with a version of OpenSSL other than the
18470 one we compiled with. This has occasionally given people hard-to-
18472 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18473 versions and capabilities when everything is going right. Resolves
18474 part of ticket 6736.
18475 - Directory authorities no long accept descriptors for any version of
18476 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18477 These versions are insecure, unsupported, or both. Implements
18481 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18482 to start with a triple-underscore so the controller won't touch it.
18483 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18484 - Avoid segfault when starting up having run with an extremely old
18485 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18487 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18488 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18489 - Don't follow the NULL pointer if microdescriptor generation fails.
18490 (This does not appear to be triggerable, but it's best to be safe.)
18491 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18492 - Fix mis-declared dependencies on src/common/crypto.c and
18493 src/or/tor_main.c that could break out-of-tree builds under some
18494 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18495 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18496 6778; bugfix on 0.2.4.1-alpha.
18497 - Fix a harmless (in this case) build warning for implicitly
18498 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18500 o Removed features:
18501 - Now that all versions before 0.2.2.x are disallowed, we no longer
18502 need to work around their missing features. Thus we can remove a
18503 bunch of compatibility code.
18505 o Code refactoring:
18506 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18507 TCP ports to forward. In the past it only accepted two ports:
18508 the ORPort and the DirPort.
18511 Changes in version 0.2.4.1-alpha - 2012-09-05
18512 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18513 bridgedb; lets relays use IPv6 addresses and directory authorities
18514 advertise them; and switches to a cleaner build interface.
18516 This is the first alpha release in a new series, so expect there to
18517 be bugs. Users who would rather test out a more stable branch should
18518 stay with 0.2.3.x for now.
18520 o Major features (bridges):
18521 - Bridges now report the pluggable transports they support to the
18522 bridge authority, so it can pass the supported transports on to
18523 bridgedb and/or eventually do reachability testing. Implements
18526 o Major features (IPv6):
18527 - Bridge authorities now accept IPv6 bridge addresses and include
18528 them in network status documents. Implements ticket 5534.
18529 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18530 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18531 to happen. Implements ticket 5535.
18532 - All kind of relays, not just bridges, can now advertise an IPv6
18533 OR port. Implements ticket 6362.
18534 - Directory authorities vote on IPv6 OR ports using the new consensus
18535 method 14. Implements ticket 6363.
18537 o Major features (build):
18538 - Switch to a nonrecursive Makefile structure. Now instead of each
18539 Makefile.am invoking other Makefile.am's, there is a master
18540 Makefile.am that includes the others. This change makes our build
18541 process slightly more maintainable, and improves parallelism for
18542 building with make -j. Original patch by Stewart Smith; various
18543 fixes by Jim Meyering.
18544 - Where available, we now use automake's "silent" make rules by
18545 default, so that warnings are easier to spot. You can get the old
18546 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18548 o Minor features (code security and spec conformance):
18549 - Clear keys and key-derived material left on the stack in
18550 rendservice.c and rendclient.c. Check return value of
18551 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18552 These fixes should make us more forward-secure against cold-boot
18553 attacks and the like. Fixes bug 2385.
18554 - Reject EXTEND cells sent to nonexistent streams. According to the
18555 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18556 we were only checking for stream IDs that were currently in use.
18557 Found while hunting for more instances of bug 6271. Bugfix on
18558 0.0.2pre8, which introduced incremental circuit construction.
18560 o Minor features (streamlining);
18561 - No longer include the "opt" prefix when generating routerinfos
18562 or v2 directories: it has been needless since Tor 0.1.2. Closes
18564 - Remove some now-needless code that tried to aggressively flush
18565 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18566 cell queue logic has saved us from the failure mode that this code
18567 was supposed to prevent. Removing this code will limit the number
18568 of baroque control flow paths through Tor's network logic. Reported
18569 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18571 o Minor features (controller):
18572 - Add a "GETINFO signal/names" control port command. Implements
18574 - Provide default values for all options via "GETINFO config/defaults".
18575 Implements ticket 4971.
18577 o Minor features (IPv6):
18578 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18579 authorities should set if they have IPv6 connectivity and want to
18580 do reachability tests for IPv6 relays. Implements feature 5974.
18581 - A relay with an IPv6 OR port now sends that address in NETINFO
18582 cells (in addition to its other address). Implements ticket 6364.
18584 o Minor features (log messages):
18585 - Omit the first heartbeat log message, because it never has anything
18586 useful to say, and it clutters up the bootstrapping messages.
18587 Resolves ticket 6758.
18588 - Don't log about reloading the microdescriptor cache at startup. Our
18589 bootstrap warnings are supposed to tell the user when there's a
18590 problem, and our bootstrap notices say when there isn't. Resolves
18591 ticket 6759; bugfix on 0.2.2.6-alpha.
18592 - Don't log "I learned some more directory information" when we're
18593 reading cached directory information. Reserve it for when new
18594 directory information arrives in response to a fetch. Resolves
18596 - Prevent rounding error in path bias counts when scaling
18597 them down, and use the correct scale factor default. Also demote
18598 some path bias related log messages down a level and make others
18599 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18600 - We no longer warn so much when generating manpages from their
18603 o Code simplifications and refactoring:
18604 - Enhance our internal sscanf replacement so that we can eliminate
18605 the last remaining uses of the system sscanf. (Though those uses
18606 of sscanf were safe, sscanf itself is generally error prone, so
18607 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18609 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18610 - Move last_reachable and testing_since from routerinfo_t to node_t.
18611 Implements ticket 5529.
18612 - Add replaycache_t structure, functions and unit tests, then refactor
18613 rend_service_introduce() to be more clear to read, improve, debug,
18614 and test. Resolves bug 6177.
18615 - Finally remove support for malloc_good_size and malloc_usable_size.
18616 We had hoped that these functions would let us eke a little more
18617 memory out of our malloc implementation. Unfortunately, the only
18618 implementations that provided these functions are also ones that
18619 are already efficient about not overallocation: they never got us
18620 more than 7 or so bytes per allocation. Removing them saves us a
18621 little code complexity and a nontrivial amount of build complexity.
18623 o New requirements:
18624 - Tor maintainers now require Automake version 1.9 or later to build
18625 Tor from the Git repository. (Automake is not required when building
18626 from a source distribution.)
18629 Changes in version 0.2.3.21-rc - 2012-09-05
18630 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
18631 series. It fixes a trio of potential security bugs, fixes a bug where
18632 we were leaving some of the fast relays out of the microdescriptor
18633 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
18634 and cleans up other smaller issues.
18636 o Major bugfixes (security):
18637 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18638 could use this trick to make their circuits receive cells faster
18639 than our flow control would have allowed, or to gum up the network,
18640 or possibly to do targeted memory denial-of-service attacks on
18641 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18642 from July 2002, before the release of Tor 0.0.0. We had committed
18643 this patch previously, but we had to revert it because of bug 6271.
18644 Now that 6271 is fixed, this patch appears to work.
18645 - Reject any attempt to extend to an internal address. Without
18646 this fix, a router could be used to probe addresses on an internal
18647 network to see whether they were accepting connections. Fixes bug
18648 6710; bugfix on 0.0.8pre1.
18649 - Do not crash when comparing an address with port value 0 to an
18650 address policy. This bug could have been used to cause a remote
18651 assertion failure by or against directory authorities, or to
18652 allow some applications to crash clients. Fixes bug 6690; bugfix
18656 - Remove the upper bound on microdescriptor length. We were hitting
18657 the limit for routers with complex exit policies or family
18658 declarations, causing clients to not use them. Fixes the first
18659 piece of bug 6404; fix on 0.2.2.6-alpha.
18660 - Detect "ORPort 0" as meaning, uniformly, that we're not running
18661 as a relay. Previously, some of our code would treat the presence
18662 of any ORPort line as meaning that we should act like a relay,
18663 even though our new listener code would correctly not open any
18664 ORPorts for ORPort 0. Similar bugs in other Port options are also
18665 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
18668 - Avoid a pair of double-free and use-after-mark bugs that can
18669 occur with certain timings in canceled and re-received DNS
18670 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18671 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18672 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18673 - Allow one-hop directory fetching circuits the full "circuit build
18674 timeout" period, rather than just half of it, before failing them
18675 and marking the relay down. This fix should help reduce cases where
18676 clients declare relays (or worse, bridges) unreachable because
18677 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18678 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18680 - Authorities no longer include any router in their microdescriptor
18681 consensuses for which they couldn't generate or agree on a
18682 microdescriptor. Fixes the second piece of bug 6404; fix on
18684 - Detect and reject attempts to specify both "FooPort" and
18685 "FooPort 0" in the same configuration domain. (It's still okay
18686 to have a FooPort in your configuration file, and use "FooPort 0"
18687 on the command line to disable it.) Fixes the second half of bug
18688 6507; bugfix on 0.2.3.3-alpha.
18689 - Make wildcarded addresses (that is, ones beginning with "*.") work
18690 when provided via the controller's MapAddress command. Previously,
18691 they were accepted, but we never actually noticed that they were
18692 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
18693 - Avoid crashing on a malformed state file where EntryGuardPathBias
18694 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
18695 - Add a (probably redundant) memory clear between iterations of
18696 the router status voting loop, to prevent future coding errors
18697 where data might leak between iterations of the loop. Resolves
18700 o Minor bugfixes (log messages):
18701 - Downgrade "set buildtimeout to low value" messages to "info"
18702 severity; they were never an actual problem, there was never
18703 anything reasonable to do about them, and they tended to spam logs
18704 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18705 - Downgrade path-bias warning messages to "info". We'll try to get
18706 them working better in 0.2.4. Add internal circuit construction
18707 state to protect against the noisy warn message "Unexpectedly high
18708 circuit_successes". Also add some additional rate-limited notice
18709 messages to help determine the root cause of the warn. Fixes bug
18710 6475. Bugfix against 0.2.3.17-beta.
18711 - Move log message when unable to find a microdesc in a routerstatus
18712 entry to parse time. Previously we'd spam this warning every time
18713 we tried to figure out which microdescriptors to download. Fixes
18714 the third piece of bug 6404; fix on 0.2.3.18-rc.
18717 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
18718 change when the authority is deciding whether to accept a newly
18719 uploaded descriptor. Implements ticket 6423.
18720 - Add missing documentation for consensus and microdesc files.
18721 Resolves ticket 6732.
18724 Changes in version 0.2.2.38 - 2012-08-12
18725 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
18726 attack that could in theory leak path information.
18729 - Avoid an uninitialized memory read when reading a vote or consensus
18730 document that has an unrecognized flavor name. This read could
18731 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18732 - Try to leak less information about what relays a client is
18733 choosing to a side-channel attacker. Previously, a Tor client would
18734 stop iterating through the list of available relays as soon as it
18735 had chosen one, thus finishing a little earlier when it picked
18736 a router earlier in the list. If an attacker can recover this
18737 timing information (nontrivial but not proven to be impossible),
18738 they could learn some coarse-grained information about which relays
18739 a client was picking (middle nodes in particular are likelier to
18740 be affected than exits). The timing attack might be mitigated by
18741 other factors (see bug 6537 for some discussion), but it's best
18742 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18745 Changes in version 0.2.3.20-rc - 2012-08-05
18746 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
18747 series. It fixes a pair of code security bugs and a potential anonymity
18748 issue, updates our RPM spec files, and cleans up other smaller issues.
18751 - Avoid read-from-freed-memory and double-free bugs that could occur
18752 when a DNS request fails while launching it. Fixes bug 6480;
18753 bugfix on 0.2.0.1-alpha.
18754 - Avoid an uninitialized memory read when reading a vote or consensus
18755 document that has an unrecognized flavor name. This read could
18756 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
18757 - Try to leak less information about what relays a client is
18758 choosing to a side-channel attacker. Previously, a Tor client would
18759 stop iterating through the list of available relays as soon as it
18760 had chosen one, thus finishing a little earlier when it picked
18761 a router earlier in the list. If an attacker can recover this
18762 timing information (nontrivial but not proven to be impossible),
18763 they could learn some coarse-grained information about which relays
18764 a client was picking (middle nodes in particular are likelier to
18765 be affected than exits). The timing attack might be mitigated by
18766 other factors (see bug 6537 for some discussion), but it's best
18767 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
18770 - Try to make the warning when giving an obsolete SOCKSListenAddress
18771 a little more useful.
18772 - Terminate active server managed proxies if Tor stops being a
18773 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
18774 - Provide a better error message about possible OSX Asciidoc failure
18775 reasons. Fixes bug 6436.
18776 - Warn when Tor is configured to use accounting in a way that can
18777 link a hidden service to some other hidden service or public
18778 address. Resolves ticket 6490.
18781 - Check return value of fputs() when writing authority certificate
18782 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
18783 - Ignore ServerTransportPlugin lines when Tor is not configured as
18784 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
18785 - When disabling guards for having too high a proportion of failed
18786 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
18790 - Update our default RPM spec files to work with mock and rpmbuild
18791 on RHEL/Fedora. They have an updated set of dependencies and
18792 conflicts, a fix for an ancient typo when creating the "_tor"
18793 user, and better instructions. Thanks to Ondrej Mikle for the
18794 patch series. Fixes bug 6043.
18797 - Make it possible to set the TestingTorNetwork configuration
18798 option using AlternateDirAuthority and AlternateBridgeAuthority
18799 as an alternative to setting DirServer. Addresses ticket 6377.
18802 - Clarify the documentation for the Alternate*Authority options.
18804 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
18806 o Code simplification and refactoring:
18807 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
18808 10 lines. Also, don't nest them. Doing so in the past has
18809 led to hard-to-debug code. The new style is to use the
18810 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
18813 Changes in version 0.2.3.19-rc - 2012-07-06
18814 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
18815 series. It fixes the compile on Windows, reverts to a GeoIP database
18816 that isn't as broken, and fixes a flow control bug that has been around
18817 since the beginning of Tor.
18820 - Fix a bug handling SENDME cells on nonexistent streams that could
18821 result in bizarre window values. Report and patch contributed
18822 pseudonymously. Fixes part of bug 6271. This bug was introduced
18823 before the first Tor release, in svn commit r152.
18824 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
18825 June 2012 database, Maxmind marked many Tor relays as country "A1",
18826 which will cause risky behavior for clients that set EntryNodes
18827 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
18828 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
18829 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
18832 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
18833 bugfix on 0.2.1.10-alpha.
18836 Changes in version 0.2.3.18-rc - 2012-06-28
18837 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
18838 series. It fixes a few smaller bugs, but generally appears stable.
18839 Please test it and let us know whether it is!
18842 - Allow wildcarded mapaddress targets to be specified on the
18843 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
18844 - Make our linker option detection code more robust against linkers
18845 such as on FreeBSD 8, where a bad combination of options completes
18846 successfully but makes an unrunnable binary. Fixes bug 6173;
18847 bugfix on 0.2.3.17-beta.
18849 o Minor bugfixes (on 0.2.2.x and earlier):
18850 - Avoid a false positive in the util/threads unit test by increasing
18851 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
18852 - Replace "Sending publish request" log messages with "Launching
18853 upload", so that they no longer confusingly imply that we're
18854 sending something to a directory we might not even be connected
18855 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
18856 - Make sure to set *socket_error in all error cases in
18857 connection_connect(), so it can't produce a warning about
18858 errno being zero from errno_to_orconn_end_reason(). Bugfix on
18859 0.2.1.1-alpha; resolves ticket 6028.
18860 - Downgrade "Got a certificate, but we already have it" log messages
18861 from warning to info, except when we're a dirauth. Fixes bug 5238;
18862 bugfix on 0.2.1.7-alpha.
18863 - When checking for requested signatures on the latest consensus
18864 before serving it to a client, make sure to check the right
18865 consensus flavor. Bugfix on 0.2.2.6-alpha.
18866 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
18867 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
18869 o Minor bugfixes (on 0.2.3.x):
18870 - Make format_helper_exit_status() avoid unnecessary space padding
18871 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
18873 - Downgrade a message about cleaning the microdescriptor cache to
18874 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
18875 - Log a BUG message at severity INFO if we have a networkstatus with
18876 a missing entry for some microdescriptor. Continues on a patch
18878 - Improve the log message when a managed proxy fails to launch. Fixes
18879 bug 5099; bugfix on 0.2.3.6-alpha.
18880 - Don't do DNS lookups when parsing corrupted managed proxy protocol
18881 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
18882 - When formatting wildcarded address mappings for the controller,
18883 be sure to include "*." as appropriate. Partially fixes bug 6244;
18884 bugfix on 0.2.3.9-alpha.
18885 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
18886 Bugfix on 0.2.3.13-alpha.
18887 - Stop logging messages about running with circuit timeout learning
18888 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
18889 - Disable a spurious warning about reading on a marked and flushing
18890 connection. We shouldn't be doing that, but apparently we
18891 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
18892 - Fix a bug that stopped AllowDotExit from working on addresses
18893 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
18896 o Code simplification, refactoring, unit tests:
18897 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
18898 Libevent's notion of cached time when possible.
18899 - Remove duplicate code for invoking getrlimit() from control.c.
18900 - Add a unit test for the environment_variable_names_equal function.
18903 - Document the --defaults-torrc option, and the new (in 0.2.3)
18904 semantics for overriding, extending, and clearing lists of
18905 options. Closes bug 4748.
18908 Changes in version 0.2.3.17-beta - 2012-06-15
18909 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
18910 gets our TLS handshake back on track for being able to blend in with
18911 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
18912 with Vidalia, and otherwise continues to get us closer to a release
18916 - Enable gcc and ld hardening by default. Resolves ticket 5210.
18917 - Update TLS cipher list to match Firefox 8 and later. Resolves
18919 - Implement the client side of proposal 198: remove support for
18920 clients falsely claiming to support standard ciphersuites that
18921 they can actually provide. As of modern OpenSSL versions, it's not
18922 necessary to fake any standard ciphersuite, and doing so prevents
18923 us from using better ciphersuites in the future, since servers
18924 can't know whether an advertised ciphersuite is really supported or
18925 not. Some hosts -- notably, ones with very old versions of OpenSSL
18926 or where OpenSSL has been built with ECC disabled -- will stand
18927 out because of this change; TBB users should not be affected.
18930 - Change the default value for DynamicDHGroups (introduced in
18931 0.2.3.9-alpha) to 0. This feature can make Tor relays less
18932 identifiable by their use of the mod_ssl DH group, but at
18933 the cost of some usability (#4721) and bridge tracing (#6087)
18934 regressions. Resolves ticket 5598.
18935 - Send a CRLF at the end of each STATUS_* control protocol event. This
18936 bug tickled a bug in Vidalia which would make it freeze. Fixes
18937 bug 6094; bugfix on 0.2.3.16-alpha.
18940 - Disable writing on marked-for-close connections when they are
18941 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
18942 bug 5263; bugfix on 0.0.2pre13, where we first added a special
18943 case for flushing marked connections.
18944 - Detect SSL handshake even when the initial attempt to write the
18945 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
18946 - Change the AllowDotExit rules so they should actually work.
18947 We now enforce AllowDotExit only immediately after receiving an
18948 address via SOCKS or DNSPort: other sources are free to provide
18949 .exit addresses after the resolution occurs. Fixes bug 3940;
18950 bugfix on 0.2.2.1-alpha.
18951 - Fix a (harmless) integer overflow in cell statistics reported by
18952 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
18953 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
18954 right places and never depends on the consensus parameters or
18955 computes adaptive timeouts when it is disabled. Fixes bug 5049;
18956 bugfix on 0.2.2.14-alpha.
18957 - When building Tor on Windows with -DUNICODE (not default), ensure
18958 that error messages, filenames, and DNS server names are always
18959 NUL-terminated when we convert them to a single-byte encoding.
18960 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
18961 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
18962 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
18963 - Fix an edge case where TestingTorNetwork is set but the authorities
18964 and relays all have an uptime of zero, where the private Tor network
18965 could briefly lack support for hidden services. Fixes bug 3886;
18966 bugfix on 0.2.2.18-alpha.
18967 - Correct the manpage's descriptions for the default values of
18968 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
18970 - Fix the documentation for the --hush and --quiet command line
18971 options, which changed their behavior back in 0.2.3.3-alpha.
18972 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
18976 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
18977 more information to it, so that we can track it down in case it
18978 returns again. Mitigates bug 5235.
18979 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
18980 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
18981 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
18982 - Warn the user when HTTPProxy, but no other proxy type, is
18983 configured. This can cause surprising behavior: it doesn't send
18984 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
18985 directory traffic only. Resolves ticket 4663.
18986 - Issue a notice if a guard completes less than 40% of your circuits.
18987 Threshold is configurable by torrc option PathBiasNoticeRate and
18988 consensus parameter pb_noticepct. There is additional, off-by-
18989 default code to disable guards which fail too many circuits.
18990 Addresses ticket 5458.
18991 - Update to the June 6 2012 Maxmind GeoLite Country database.
18993 o Code simplifications and refactoring:
18994 - Remove validate_pluggable_transports_config(): its warning
18995 message is now handled by connection_or_connect().
18998 Changes in version 0.2.2.37 - 2012-06-06
18999 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19000 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19004 - Work around a bug in OpenSSL that broke renegotiation with TLS
19005 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19006 the v2 Tor connection protocol when both sides were using OpenSSL
19007 1.0.1 would fail. Resolves ticket 6033.
19008 - When waiting for a client to renegotiate, don't allow it to add
19009 any bytes to the input buffer. This fixes a potential DoS issue.
19010 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19011 - Fix an edge case where if we fetch or publish a hidden service
19012 descriptor, we might build a 4-hop circuit and then use that circuit
19013 for exiting afterwards -- even if the new last hop doesn't obey our
19014 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19017 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19018 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19021 - Tell GCC and Clang to check for any errors in format strings passed
19022 to the tor_v*(print|scan)f functions.
19025 Changes in version 0.2.3.16-alpha - 2012-06-05
19026 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
19027 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19028 currently). It also fixes a variety of smaller bugs and other cleanups
19029 that get us closer to a release candidate.
19031 o Major bugfixes (general):
19032 - Work around a bug in OpenSSL that broke renegotiation with TLS
19033 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19034 the v2 Tor connection protocol when both sides were using OpenSSL
19035 1.0.1 would fail. Resolves ticket 6033.
19036 - When waiting for a client to renegotiate, don't allow it to add
19037 any bytes to the input buffer. This fixes a potential DoS issue.
19038 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19039 - Pass correct OR address to managed proxies (like obfsproxy),
19040 even when ORListenAddress is used. Fixes bug 4865; bugfix on
19042 - The advertised platform of a router now includes only its operating
19043 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
19044 service pack level (for Windows) or its CPU architecture (for Unix).
19045 We also no longer include the "git-XYZ" tag in the version. Resolves
19048 o Major bugfixes (clients):
19049 - If we are unable to find any exit that supports our predicted ports,
19050 stop calling them predicted, so that we don't loop and build
19051 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19052 which introduced predicted ports.
19053 - Fix an edge case where if we fetch or publish a hidden service
19054 descriptor, we might build a 4-hop circuit and then use that circuit
19055 for exiting afterwards -- even if the new last hop doesn't obey our
19056 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19057 - Check at each new consensus whether our entry guards were picked
19058 long enough ago that we should rotate them. Previously, we only
19059 did this check at startup, which could lead to us holding a guard
19060 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19061 - When fetching a bridge descriptor from a bridge authority,
19062 always do so anonymously, whether we have been able to open
19063 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19064 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19065 but we'll need to wait for bug 6010 before it's actually usable.
19067 o Major bugfixes (directory authorities):
19068 - When computing weight parameters, behave more robustly in the
19069 presence of a bad bwweightscale value. Previously, the authorities
19070 would crash if they agreed on a sufficiently broken weight_scale
19071 value: now, they use a reasonable default and carry on. Partial
19072 fix for 5786; bugfix on 0.2.2.17-alpha.
19073 - Check more thoroughly to prevent a rogue authority from
19074 double-voting on any consensus directory parameter. Previously,
19075 authorities would crash in this case if the total number of
19076 votes for any parameter exceeded the number of active voters,
19077 but would let it pass otherwise. Partial fix for bug 5786; bugfix
19081 - Rate-limit log messages when asked to connect anonymously to
19082 a private address. When these hit, they tended to hit fast and
19083 often. Also, don't bother trying to connect to addresses that we
19084 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19085 reply makes us think we have been lied to, even when the address the
19086 client tried to connect to was "localhost." Resolves ticket 2822.
19087 - Allow packagers to insert an extra string in server descriptor
19088 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
19089 Resolves the rest of ticket 2988.
19090 - Raise the threshold of server descriptors needed (75%) and exit
19091 server descriptors needed (50%) before we will declare ourselves
19092 bootstrapped. This will make clients start building circuits a
19093 little later, but makes the initially constructed circuits less
19094 skewed and less in conflict with further directory fetches. Fixes
19096 - Close any connection that sends unrecognized junk before the
19097 handshake. Solves an issue noted in bug 4369.
19098 - Improve log messages about managed transports. Resolves ticket 5070.
19099 - Tag a bridge's descriptor as "never to be sent unencrypted".
19100 This shouldn't matter, since bridges don't open non-anonymous
19101 connections to the bridge authority and don't allow unencrypted
19102 directory connections from clients, but we might as well make
19103 sure. Closes bug 5139.
19104 - Expose our view of whether we have gone dormant to the controller,
19105 via a new "GETINFO dormant" value. Torbutton and other controllers
19106 can use this to avoid doing periodic requests through Tor while
19107 it's dormant (bug 4718). Fixes bug 5954.
19108 - Tell GCC and Clang to check for any errors in format strings passed
19109 to the tor_v*(print|scan)f functions.
19110 - Update to the May 1 2012 Maxmind GeoLite Country database.
19112 o Minor bugfixes (already included in 0.2.2.36):
19113 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19114 Fixes bug 5346; bugfix on 0.0.8pre3.
19115 - Correct parsing of certain date types in parse_http_time().
19116 Without this patch, If-Modified-Since would behave
19117 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19118 Esteban Manchado Velázques.
19119 - Make our number-parsing functions always treat too-large values
19120 as an error, even when those values exceed the width of the
19121 underlying type. Previously, if the caller provided these
19122 functions with minima or maxima set to the extreme values of the
19123 underlying integer type, these functions would return those
19124 values on overflow rather than treating overflow as an error.
19125 Fixes part of bug 5786; bugfix on 0.0.9.
19126 - If we hit the error case where routerlist_insert() replaces an
19127 existing (old) server descriptor, make sure to remove that
19128 server descriptor from the old_routers list. Fix related to bug
19129 1776. Bugfix on 0.2.2.18-alpha.
19130 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19131 circuits. Fixes issue 5259.
19133 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
19134 - Prevent a null-pointer dereference when receiving a data cell
19135 for a nonexistent stream when the circuit in question has an
19136 empty deliver window. We don't believe this is triggerable,
19137 since we don't currently allow deliver windows to become empty,
19138 but the logic is tricky enough that it's better to make the code
19139 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19140 - Fix a memory leak when trying to launch a DNS request when the
19141 network is disabled or the nameservers are unconfigurable. Fixes
19142 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
19143 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
19144 - Don't hold a Windows file handle open for every file mapping;
19145 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19147 - Avoid O(n^2) performance characteristics when parsing a large
19148 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19149 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19150 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19152 - Make our replacement implementation of strtok_r() compatible with
19153 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19154 bugfix on 0.2.2.1-alpha.
19155 - Fix a NULL-pointer dereference on a badly formed
19156 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
19157 bugfix on 0.2.2.9-alpha.
19158 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19159 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19160 - Defensively refactor rend_mid_rendezvous() so that protocol
19161 violations and length checks happen in the beginning. Fixes
19163 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19164 that IPv6 stuff will compile on MSVC, and compilation issues
19165 will be easier to track down. Fixes bug 5861.
19167 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
19168 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19169 resource exhaustion, so that clients can adjust their load to
19170 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19171 started using END_STREAM_REASON_RESOURCELIMIT.
19172 - Don't check for whether the address we're using for outbound
19173 connections has changed until after the outbound connection has
19174 completed. On Windows, getsockname() doesn't succeed until the
19175 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19176 - If the configuration tries to set MyFamily on a bridge, refuse to
19177 do so, and warn about the security implications. Fixes bug 4657;
19178 bugfix on 0.2.0.3-alpha.
19179 - If the client fails to set a reasonable set of ciphersuites
19180 during its v2 handshake renegotiation, allow the renegotiation to
19181 continue nevertheless (i.e. send all the required certificates).
19182 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19183 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19184 option is set to 0 (which Vidalia version 0.2.16 now does when
19185 a SAVECONF attempt fails), perform other actions that SIGHUP
19186 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19188 - If we fail to write a microdescriptor to the disk cache, do not
19189 continue replacing the old microdescriptor file. Fixes bug 2954;
19190 bugfix on 0.2.2.6-alpha.
19191 - Exit nodes don't need to fetch certificates for authorities that
19192 they don't recognize; only directory authorities, bridges,
19193 and caches need to do that. Fixes part of bug 2297; bugfix on
19195 - Correctly handle checking the permissions on the parent
19196 directory of a control socket in the root directory. Bug found
19197 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19199 - When told to add a bridge with the same digest as a preexisting
19200 bridge but a different addr:port, change the addr:port as
19201 requested. Previously we would not notice the change. Fixes half
19202 of bug 5603; fix on 0.2.2.26-beta.
19203 - End AUTHCHALLENGE error messages (in the control protocol) with
19204 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
19206 o Minor bugfixes (on 0.2.3.x):
19207 - Turn an assertion (that the number of handshakes received as a
19208 server is not < 1) into a warning. Fixes bug 4873; bugfix on
19210 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
19211 we had reversed them when the answer was cached.) Fixes bug
19212 5723; bugfix on 0.2.3.1-alpha.
19213 - Work correctly on Linux systems with accept4 support advertised in
19214 their headers, but without accept4 support in the kernel. Fix
19215 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
19216 - When told to add a bridge with the same addr:port as a preexisting
19217 bridge but a different transport, change the transport as
19218 requested. Previously we would not notice the change. Fixes half
19219 of bug 5603; fix on 0.2.3.2-alpha.
19220 - Avoid a "double-reply" warning when replying to a SOCKS request
19221 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
19222 bugfix on 0.2.3.4-alpha.
19223 - Fix a bug where a bridge authority crashes if it has seen no
19224 directory requests when it's time to write statistics to disk.
19225 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
19227 - Don't try to open non-control listeners when DisableNetwork is set.
19228 Previously, we'd open all listeners, then immediately close them.
19229 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
19230 - Don't abort the managed proxy protocol if the managed proxy
19231 sends us an unrecognized line; ignore it instead. Fixes bug
19232 5910; bugfix on 0.2.3.9-alpha.
19233 - Fix a compile warning in crypto.c when compiling with clang 3.1.
19234 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
19235 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
19236 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
19237 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
19238 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
19239 - Resolve numerous small warnings and build issues with MSVC. Resolves
19242 o Documentation fixes:
19243 - Improve the manual's documentation for the NT Service command-line
19244 options. Addresses ticket 3964.
19245 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19246 - Document the changes to the ORPort and DirPort options, and the
19247 fact that {OR/Dir}ListenAddress is now unnecessary (and
19248 therefore deprecated). Resolves ticket 5597.
19251 - Remove the torrc.bridge file: we don't use it for anything, and
19252 it had become badly desynchronized from torrc.sample. Resolves
19256 Changes in version 0.2.2.36 - 2012-05-24
19257 Tor 0.2.2.36 updates the addresses for two of the eight directory
19258 authorities, fixes some potential anonymity and security issues,
19259 and fixes several crash bugs.
19261 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19262 known flaws, and nobody should be using them. You should upgrade. If
19263 you're using a Linux or BSD and its packages are obsolete, stop using
19264 those packages and upgrade anyway.
19266 o Directory authority changes:
19267 - Change IP address for maatuska (v3 directory authority).
19268 - Change IP address for ides (v3 directory authority), and rename
19272 - When building or running with any version of OpenSSL earlier
19273 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19274 versions have a bug (CVE-2011-4576) in which their block cipher
19275 padding includes uninitialized data, potentially leaking sensitive
19276 information to any peer with whom they make a SSLv3 connection. Tor
19277 does not use SSL v3 by default, but a hostile client or server
19278 could force an SSLv3 connection in order to gain information that
19279 they shouldn't have been able to get. The best solution here is to
19280 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19281 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19282 to make sure that the bug can't happen.
19283 - Never use a bridge or a controller-supplied node as an exit, even
19284 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19285 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19286 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19287 - Only build circuits if we have a sufficient threshold of the total
19288 descriptors that are marked in the consensus with the "Exit"
19289 flag. This mitigates an attack proposed by wanoskarnet, in which
19290 all of a client's bridges collude to restrict the exit nodes that
19291 the client knows about. Fixes bug 5343.
19292 - Provide controllers with a safer way to implement the cookie
19293 authentication mechanism. With the old method, if another locally
19294 running program could convince a controller that it was the Tor
19295 process, then that program could trick the controller into telling
19296 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19297 authentication method uses a challenge-response approach to prevent
19298 this attack. Fixes bug 5185; implements proposal 193.
19301 - Avoid logging uninitialized data when unable to decode a hidden
19302 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19303 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19304 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19306 - Fix builds when the path to sed, openssl, or sha1sum contains
19307 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19309 - Correct our replacements for the timeradd() and timersub() functions
19310 on platforms that lack them (for example, Windows). The timersub()
19311 function is used when expiring circuits, while timeradd() is
19312 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19313 bugfix on 0.2.2.24-alpha.
19314 - Fix the SOCKET_OK test that we use to tell when socket
19315 creation fails so that it works on Win64. Fixes part of bug 4533;
19316 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19319 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19320 Fixes bug 5346; bugfix on 0.0.8pre3.
19321 - Make our number-parsing functions always treat too-large values
19322 as an error, even when those values exceed the width of the
19323 underlying type. Previously, if the caller provided these
19324 functions with minima or maxima set to the extreme values of the
19325 underlying integer type, these functions would return those
19326 values on overflow rather than treating overflow as an error.
19327 Fixes part of bug 5786; bugfix on 0.0.9.
19328 - Older Linux kernels erroneously respond to strange nmap behavior
19329 by having accept() return successfully with a zero-length
19330 socket. When this happens, just close the connection. Previously,
19331 we would try harder to learn the remote address: but there was
19332 no such remote address to learn, and our method for trying to
19333 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19334 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19335 - Correct parsing of certain date types in parse_http_time().
19336 Without this patch, If-Modified-Since would behave
19337 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19338 Esteban Manchado Velázques.
19339 - Change the BridgePassword feature (part of the "bridge community"
19340 design, which is not yet implemented) to use a time-independent
19341 comparison. The old behavior might have allowed an adversary
19342 to use timing to guess the BridgePassword value. Fixes bug 5543;
19343 bugfix on 0.2.0.14-alpha.
19344 - Detect and reject certain misformed escape sequences in
19345 configuration values. Previously, these values would cause us
19346 to crash if received in a torrc file or over an authenticated
19347 control port. Bug found by Esteban Manchado Velázquez, and
19348 independently by Robert Connolly from Matta Consulting who further
19349 noted that it allows a post-authentication heap overflow. Patch
19350 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19351 bugfix on 0.2.0.16-alpha.
19352 - Fix a compile warning when using the --enable-openbsd-malloc
19353 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19354 - During configure, detect when we're building with clang version
19355 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19356 CFLAGS. clang doesn't support them yet.
19357 - When sending an HTTP/1.1 proxy request, include a Host header.
19358 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19359 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19360 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19361 - If we hit the error case where routerlist_insert() replaces an
19362 existing (old) server descriptor, make sure to remove that
19363 server descriptor from the old_routers list. Fix related to bug
19364 1776. Bugfix on 0.2.2.18-alpha.
19366 o Minor bugfixes (documentation and log messages):
19367 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19368 Fixes bug 4856; bugfix on Tor 0.0.6.
19369 - Update "ClientOnly" man page entry to explain that there isn't
19370 really any point to messing with it. Resolves ticket 5005.
19371 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19372 directory authority option (introduced in Tor 0.2.2.34).
19373 - Downgrade the "We're missing a certificate" message from notice
19374 to info: people kept mistaking it for a real problem, whereas it
19375 is seldom the problem even when we are failing to bootstrap. Fixes
19376 bug 5067; bugfix on 0.2.0.10-alpha.
19377 - Correctly spell "connect" in a log message on failure to create a
19378 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19379 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19380 circuits. Fixes issue 5259.
19383 - Directory authorities now reject versions of Tor older than
19384 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19385 inclusive. These versions accounted for only a small fraction of
19386 the Tor network, and have numerous known security issues. Resolves
19388 - Update to the May 1 2012 Maxmind GeoLite Country database.
19391 - When sending or relaying a RELAY_EARLY cell, we used to convert
19392 it to a RELAY cell if the connection was using the v1 link
19393 protocol. This was a workaround for older versions of Tor, which
19394 didn't handle RELAY_EARLY cells properly. Now that all supported
19395 versions can handle RELAY_EARLY cells, and now that we're enforcing
19396 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19397 remove this workaround. Addresses bug 4786.
19400 Changes in version 0.2.3.15-alpha - 2012-04-30
19401 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
19402 the development branch build on Windows again.
19404 o Minor bugfixes (on 0.2.2.x and earlier):
19405 - Make sure that there are no unhandled pending TLS errors before
19406 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19407 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19408 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19409 - Fix an assert that directory authorities could trigger on sighup
19410 during some configuration state transitions. We now don't treat
19411 it as a fatal error when the new descriptor we just generated in
19412 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19413 - After we pick a directory mirror, we would refuse to use it if
19414 it's in our ExcludeExitNodes list, resulting in mysterious failures
19415 to bootstrap for people who just wanted to avoid exiting from
19416 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19417 - When building with --enable-static-tor on OpenBSD, do not
19418 erroneously attempt to link -lrt. Fixes bug 5103.
19420 o Minor bugfixes (on 0.2.3.x):
19421 - When Tor is built with kernel headers from a recent (last few
19422 years) Linux kernel, do not fail to run on older (pre-2.6.28
19423 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19424 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19425 and 0.2.3.12-alpha.
19426 - Fix compilation with miniupnpc version 1.6; patch from
19427 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19428 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19429 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19430 - Fix compilation on platforms without unistd.h, or where environ
19431 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19434 - Directory authorities are now a little more lenient at accepting
19435 older router descriptors, or newer router descriptors that don't
19436 make big changes. This should help ameliorate past and future
19437 issues where routers think they have uploaded valid descriptors,
19438 but the authorities don't think so. Fix for ticket 2479.
19439 - Make the code that clients use to detect an address change be
19440 IPv6-aware, so that it won't fill clients' logs with error
19441 messages when trying to get the IPv4 address of an IPv6
19442 connection. Implements ticket 5537.
19444 o Removed features:
19445 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19446 authorities needed to use it for a while to keep the network working
19447 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19448 that was six months ago. As of now, it should no longer be needed
19452 Changes in version 0.2.3.14-alpha - 2012-04-23
19453 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19454 candidate. It also dramatically speeds up AES: fast relays should
19455 consider switching to the newer OpenSSL library.
19457 o Directory authority changes:
19458 - Change IP address for ides (v3 directory authority), and rename
19462 - Avoid logging uninitialized data when unable to decode a hidden
19463 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19464 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19465 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19467 - If authorities are unable to get a v2 consensus document from other
19468 directory authorities, they no longer fall back to fetching
19469 them from regular directory caches. Fixes bug 5635; bugfix on
19470 0.2.2.26-beta, where routers stopped downloading v2 consensus
19471 documents entirely.
19472 - When we start a Tor client with a normal consensus already cached,
19473 be willing to download a microdescriptor consensus. Fixes bug 4011;
19474 fix on 0.2.3.1-alpha.
19476 o Major features (performance):
19477 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19478 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19479 vectorized AES implementations as appropriate. These can be much,
19480 much faster than other AES implementations.
19482 o Minor bugfixes (0.2.2.x and earlier):
19483 - Don't launch more than 10 service-side introduction-point circuits
19484 for a hidden service in five minutes. Previously, we would consider
19485 launching more introduction-point circuits if at least one second
19486 had passed without any introduction-point circuits failing. Fixes
19487 bug 4607; bugfix on 0.0.7pre1.
19488 - Change the BridgePassword feature (part of the "bridge community"
19489 design, which is not yet implemented) to use a time-independent
19490 comparison. The old behavior might have allowed an adversary
19491 to use timing to guess the BridgePassword value. Fixes bug 5543;
19492 bugfix on 0.2.0.14-alpha.
19493 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19494 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19495 - When sending an HTTP/1.1 proxy request, include a Host header.
19496 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19497 - Don't log that we have "decided to publish new relay descriptor"
19498 unless we are actually publishing a descriptor. Fixes bug 3942;
19499 bugfix on 0.2.2.28-beta.
19501 o Minor bugfixes (0.2.3.x):
19502 - Fix a bug where a bridge authority crashes (on a failed assert)
19503 if it has seen no directory requests when it's time to write
19504 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19505 - Fix bug stomping on ORPort option NoListen and ignoring option
19506 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19507 - In the testsuite, provide a large enough buffer in the tor_sscanf
19508 unit test. Otherwise we'd overrun that buffer and crash during
19509 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19511 - Make sure we create the keys directory if it doesn't exist and we're
19512 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19513 5572; bugfix on 0.2.3.13-alpha.
19514 - Fix a small memory leak when trying to decode incorrect base16
19515 authenticator during SAFECOOKIE authentication. Found by
19516 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19519 - Add more information to a log statement that might help track down
19520 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19521 non-IP address" messages (or any Bug messages, for that matter!),
19522 please let us know about it.
19523 - Relays now understand an IPv6 address when they get one from a
19524 directory server. Resolves ticket 4875.
19525 - Resolve IPv6 addresses in bridge and entry statistics to country
19526 code "??" which means we at least count them. Resolves ticket 5053;
19527 improves on 0.2.3.9-alpha.
19528 - Update to the April 3 2012 Maxmind GeoLite Country database.
19529 - Begin a doc/state-contents.txt file to explain the contents of
19530 the Tor state file. Fixes bug 2987.
19532 o Default torrc changes:
19533 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19534 port on 9050 by default anyway, so this should not change anything
19536 - Stop mentioning the deprecated *ListenAddress options in
19537 torrc.sample. Fixes bug 5438.
19538 - Document unit of bandwidth related options in sample torrc.
19541 o Removed features:
19542 - The "torify" script no longer supports the "tsocks" socksifier
19543 tool, since tsocks doesn't support DNS and UDP right for Tor.
19544 Everyone should be using torsocks instead. Fixes bugs 3530 and
19545 5180. Based on a patch by "ugh".
19547 o Code refactoring:
19548 - Change the symmetric cipher interface so that creating and
19549 initializing a stream cipher are no longer separate functions.
19550 - Remove all internal support for unpadded RSA. We never used it, and
19551 it would be a bad idea to start.
19554 Changes in version 0.2.3.13-alpha - 2012-03-26
19555 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19556 in managed pluggable transports, as well as providing other cleanups
19557 that get us closer to a release candidate.
19559 o Directory authority changes:
19560 - Change IP address for maatuska (v3 directory authority).
19563 - Provide controllers with a safer way to implement the cookie
19564 authentication mechanism. With the old method, if another locally
19565 running program could convince a controller that it was the Tor
19566 process, then that program could trick the controller into telling
19567 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19568 authentication method uses a challenge-response approach to prevent
19569 this attack. Fixes bug 5185, implements proposal 193.
19570 - Never use a bridge or a controller-supplied node as an exit, even
19571 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19572 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19573 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19574 - Only build circuits if we have a sufficient threshold of the total
19575 descriptors that are marked in the consensus with the "Exit"
19576 flag. This mitigates an attack proposed by wanoskarnet, in which
19577 all of a client's bridges collude to restrict the exit nodes that
19578 the client knows about. Fixes bug 5343.
19580 o Major bugfixes (on Tor 0.2.3.x):
19581 - Avoid an assert when managed proxies like obfsproxy are configured,
19582 and we receive HUP signals or setconf attempts too rapidly. This
19583 situation happens most commonly when Vidalia tries to attach to
19584 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19585 bugfix on 0.2.3.6-alpha.
19586 - Fix a relay-side pluggable transports bug where managed proxies were
19587 unreachable from the Internet, because Tor asked them to bind on
19588 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19589 - Stop discarding command-line arguments when TestingTorNetwork
19590 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19591 0.2.3.9-alpha, where task 4552 added support for two layers of
19593 - Resume allowing the unit tests to run in gdb. This was accidentally
19594 made impossible when the DisableDebuggerAttachment option was
19595 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19596 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19597 0.2.3.11-alpha. Reported by Anthony G. Basile.
19599 o Minor bugfixes (on 0.2.2.x and earlier):
19600 - Ensure we don't cannibalize circuits that are longer than three hops
19601 already, so we don't end up making circuits with 5 or more
19602 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19603 0.1.0.1-rc which introduced cannibalization.
19604 - Detect and reject certain misformed escape sequences in
19605 configuration values. Previously, these values would cause us
19606 to crash if received in a torrc file or over an authenticated
19607 control port. Bug found by Esteban Manchado Velázquez, and
19608 independently by Robert Connolly from Matta Consulting who further
19609 noted that it allows a post-authentication heap overflow. Patch
19610 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19611 bugfix on 0.2.0.16-alpha.
19612 - Fix a compile warning when using the --enable-openbsd-malloc
19613 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19614 - Directory caches no longer refuse to clean out descriptors because
19615 of missing v2 networkstatus documents, unless they're configured
19616 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19617 0.2.2.26-beta. Patch by Daniel Bryg.
19618 - Update to the latest version of the tinytest unit testing framework.
19619 This includes a couple of bugfixes that can be relevant for
19620 running forked unit tests on Windows, and removes all reserved
19623 o Minor bugfixes (on 0.2.3.x):
19624 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19625 4296; bugfix on 0.2.3.1-alpha.
19626 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19627 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19628 on 0.2.3.6-alpha. Patch by "frosty".
19629 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
19630 option, so that the IP stack doesn't decide to use it for IPv4
19631 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
19632 - Ensure that variables set in Tor's environment cannot override
19633 environment variables that Tor passes to a managed
19634 pluggable-transport proxy. Previously, Tor would pass every
19635 variable in its environment to managed proxies along with the new
19636 ones, in such a way that on many operating systems, the inherited
19637 environment variables would override those which Tor tried to
19638 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
19639 bugfix on 0.2.3.9-alpha for Windows.
19642 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19643 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19644 - Update to the March 6 2012 Maxmind GeoLite Country database.
19647 Changes in version 0.2.3.12-alpha - 2012-02-13
19648 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
19649 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
19650 when Tor is configured to use a pluggable transport like obfsproxy.
19653 - Fix builds when the path to sed, openssl, or sha1sum contains
19654 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19656 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19657 connections. This change should allow busy exit relays to stop
19658 running out of available sockets as quickly. Fixes bug 4950;
19659 bugfix on 0.2.2.26-beta.
19660 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
19661 would ask the bridge for microdescriptors, which are only supported
19662 in 0.2.3.x, and then fail to bootstrap when it didn't get the
19663 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
19664 - Properly set up obfsproxy's environment when in managed mode. The
19665 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
19666 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
19667 5076 and 5082; bugfix on 0.2.3.6-alpha.
19670 - Use the dead_strip option when building Tor on OS X. This reduces
19671 binary size by almost 19% when linking openssl and libevent
19672 statically, which we do for Tor Browser Bundle.
19673 - Fix broken URLs in the sample torrc file, and tell readers about
19674 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19675 PublishServerDescriptor options. Addresses bug 4652.
19676 - Update to the February 7 2012 Maxmind GeoLite Country database.
19679 - Downgrade the "We're missing a certificate" message from notice
19680 to info: people kept mistaking it for a real problem, whereas it
19681 is seldom the problem even when we are failing to bootstrap. Fixes
19682 bug 5067; bugfix on 0.2.0.10-alpha.
19683 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
19684 managed pluggable transport server proxy's environment.
19685 Previously, we would put it there, even though Tor doesn't
19686 implement an 'extended server port' yet, and even though Tor
19687 almost certainly isn't listening at that address. For now, we set
19688 it to an empty string to avoid crashing older obfsproxies. Bugfix
19690 - Log the heartbeat message every HeartbeatPeriod seconds, not every
19691 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
19692 0.2.3.1-alpha. Bug reported by Scott Bennett.
19693 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
19694 bugfix on 0.2.3.11-alpha.
19695 - Update "ClientOnly" man page entry to explain that there isn't
19696 really any point to messing with it. Resolves ticket 5005.
19697 - Use the correct CVE number for CVE-2011-4576 in our comments and
19698 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
19701 o Code simplifications and refactoring:
19702 - Use the _WIN32 macro throughout our code to detect Windows.
19703 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19707 Changes in version 0.2.3.11-alpha - 2012-01-22
19708 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
19709 the last step of the plan to limit maximum circuit length, includes
19710 a wide variety of hidden service performance and correctness fixes,
19711 works around an OpenSSL security flaw if your distro is too stubborn
19712 to upgrade, and fixes a bunch of smaller issues.
19715 - Now that Tor 0.2.0.x is completely deprecated, enable the final
19716 part of "Proposal 110: Avoiding infinite length circuits" by
19717 refusing all circuit-extend requests that do not use a relay_early
19718 cell. This change helps Tor resist a class of denial-of-service
19719 attacks by limiting the maximum circuit length.
19720 - Adjust the number of introduction points that a hidden service
19721 will try to maintain based on how long its introduction points
19722 remain in use and how many introductions they handle. Fixes
19724 - Try to use system facilities for enumerating local interface
19725 addresses, before falling back to our old approach (which was
19726 binding a UDP socket, and calling getsockname() on it). That
19727 approach was scaring OS X users whose draconian firewall
19728 software warned about binding to UDP sockets, regardless of
19729 whether packets were sent. Now we try to use getifaddrs(),
19730 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
19731 system supports. Resolves ticket 1827.
19733 o Major security workaround:
19734 - When building or running with any version of OpenSSL earlier
19735 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19736 versions have a bug (CVE-2011-4576) in which their block cipher
19737 padding includes uninitialized data, potentially leaking sensitive
19738 information to any peer with whom they make a SSLv3 connection. Tor
19739 does not use SSL v3 by default, but a hostile client or server
19740 could force an SSLv3 connection in order to gain information that
19741 they shouldn't have been able to get. The best solution here is to
19742 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19743 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19744 to make sure that the bug can't happen.
19747 - Fix the SOCKET_OK test that we use to tell when socket
19748 creation fails so that it works on Win64. Fixes part of bug 4533;
19749 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19750 - Correct our replacements for the timeradd() and timersub() functions
19751 on platforms that lack them (for example, Windows). The timersub()
19752 function is used when expiring circuits, while timeradd() is
19753 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19754 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
19755 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
19756 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
19757 bug at runtime, not compile time, because some distributions hack
19758 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
19759 on 0.2.3.9-alpha. Found by Pascal.
19761 o Minor features (controller):
19762 - Use absolute path names when reporting the torrc filename in the
19763 control protocol, so a controller can more easily find the torrc
19764 file. Resolves bug 1101.
19765 - Extend the control protocol to report flags that control a circuit's
19766 path selection in CIRC events and in replies to 'GETINFO
19767 circuit-status'. Implements part of ticket 2411.
19768 - Extend the control protocol to report the hidden service address
19769 and current state of a hidden-service-related circuit in CIRC
19770 events and in replies to 'GETINFO circuit-status'. Implements part
19772 - When reporting the path to the cookie file to the controller,
19773 give an absolute path. Resolves ticket 4881.
19774 - Allow controllers to request an event notification whenever a
19775 circuit is cannibalized or its purpose is changed. Implements
19776 part of ticket 3457.
19777 - Include the creation time of a circuit in CIRC and CIRC2
19778 control-port events and the list produced by the 'GETINFO
19779 circuit-status' control-port command.
19781 o Minor features (directory authorities):
19782 - Directory authorities now reject versions of Tor older than
19783 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19784 inclusive. These versions accounted for only a small fraction of
19785 the Tor network, and have numerous known security issues. Resolves
19787 - Authority operators can now vote for all relays in a given
19788 set of countries to be BadDir/BadExit/Invalid/Rejected.
19789 - Provide two consensus parameters (FastFlagMinThreshold and
19790 FastFlagMaxThreshold) to control the range of allowable bandwidths
19791 for the Fast directory flag. These allow authorities to run
19792 experiments on appropriate requirements for being a "Fast" node.
19793 The AuthDirFastGuarantee config value still applies. Implements
19795 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19796 directory authority option (introduced in Tor 0.2.2.34).
19798 o Minor features (other):
19799 - Don't disable the DirPort when we cannot exceed our AccountingMax
19800 limit during this interval because the effective bandwidthrate is
19801 low enough. This is useful in a situation where AccountMax is only
19802 used as an additional safeguard or to provide statistics.
19803 - Prepend an informative header to generated dynamic_dh_params files.
19804 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
19805 EntryNodes will have no effect. Resolves issue 2571.
19806 - Log more useful messages when we fail to disable debugger
19808 - Log which authority we're missing votes from when we go to fetch
19809 them from the other auths.
19810 - Log (at debug level) whenever a circuit's purpose is changed.
19811 - Add missing documentation for the MaxClientCircuitsPending,
19812 UseMicrodescriptors, UserspaceIOCPBuffers, and
19813 _UseFilteringSSLBufferevents options, all introduced during
19814 the 0.2.3.x series.
19815 - Update to the January 3 2012 Maxmind GeoLite Country database.
19817 o Minor bugfixes (hidden services):
19818 - Don't close hidden service client circuits which have almost
19819 finished connecting to their destination when they reach
19820 the normal circuit-build timeout. Previously, we would close
19821 introduction circuits which are waiting for an acknowledgement
19822 from the introduction point, and rendezvous circuits which have
19823 been specified in an INTRODUCE1 cell sent to a hidden service,
19824 after the normal CBT. Now, we mark them as 'timed out', and launch
19825 another rendezvous attempt in parallel. This behavior change can
19826 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
19827 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
19828 - Don't close hidden-service-side rendezvous circuits when they
19829 reach the normal circuit-build timeout. This behavior change can
19830 be disabled using the new
19831 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
19832 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
19833 - Make sure we never mark the wrong rendezvous circuit as having
19834 had its introduction cell acknowledged by the introduction-point
19835 relay. Previously, when we received an INTRODUCE_ACK cell on a
19836 client-side hidden-service introduction circuit, we might have
19837 marked a rendezvous circuit other than the one we specified in
19838 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
19839 a warning message and interfered with the hidden service
19840 connection-establishment process. Fixes bug 4759; bugfix on
19841 0.2.3.3-alpha, when we added the stream-isolation feature which
19842 might cause Tor to open multiple rendezvous circuits for the same
19844 - Don't trigger an assertion failure when we mark a new client-side
19845 hidden-service introduction circuit for close during the process
19846 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
19849 o Minor bugfixes (log messages):
19850 - Correctly spell "connect" in a log message on failure to create a
19851 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
19853 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19854 Fixes bug 4856; bugfix on Tor 0.0.6.
19855 - Fix the log message describing how we work around discovering
19856 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
19857 4837; bugfix on 0.2.2.9-alpha.
19858 - When logging about a disallowed .exit name, do not also call it
19859 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
19861 o Minor bugfixes (build fixes):
19862 - During configure, detect when we're building with clang version
19863 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19864 CFLAGS. clang doesn't support them yet.
19865 - During configure, search for library containing cos function as
19866 libm lives in libcore on some platforms (BeOS/Haiku). Linking
19867 against libm was hard-coded before. Fixes the first part of bug
19868 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
19870 - Detect attempts to build Tor on (as yet hypothetical) versions
19871 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
19872 fix for bug 4533. Bugfix on 0.2.2.28-beta.
19873 - Preprocessor directives should not be put inside the arguments
19874 of a macro. This would break compilation with GCC releases prior
19875 to version 3.3. We would never recommend such an old GCC version,
19876 but it is apparently required for binary compatibility on some
19877 platforms (namely, certain builds of Haiku). Fixes the other part
19878 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
19881 o Minor bugfixes (other):
19882 - Older Linux kernels erroneously respond to strange nmap behavior
19883 by having accept() return successfully with a zero-length
19884 socket. When this happens, just close the connection. Previously,
19885 we would try harder to learn the remote address: but there was
19886 no such remote address to learn, and our method for trying to
19887 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19888 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19889 - Fix null-pointer access that could occur if TLS allocation failed.
19890 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
19891 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
19892 accidentally been reverted.
19893 - Fix our implementation of crypto_random_hostname() so it can't
19894 overflow on ridiculously large inputs. (No Tor version has ever
19895 provided this kind of bad inputs, but let's be correct in depth.)
19896 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
19897 - Find more places in the code that should have been testing for
19898 invalid sockets using the SOCKET_OK macro. Required for a fix
19899 for bug 4533. Bugfix on 0.2.2.28-beta.
19900 - Fix an assertion failure when, while running with bufferevents, a
19901 connection finishes connecting after it is marked for close, but
19902 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
19903 - test_util_spawn_background_ok() hardcoded the expected value
19904 for ENOENT to 2. This isn't portable as error numbers are
19905 platform specific, and particularly the hurd has ENOENT at
19906 0x40000002. Construct expected string at runtime, using the correct
19907 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
19908 - Reject attempts to disable DisableDebuggerAttachment while Tor is
19909 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
19910 - Use an appropriate-width type for sockets in tor-fw-helper on
19911 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
19914 - When sending or relaying a RELAY_EARLY cell, we used to convert
19915 it to a RELAY cell if the connection was using the v1 link
19916 protocol. This was a workaround for older versions of Tor, which
19917 didn't handle RELAY_EARLY cells properly. Now that all supported
19918 versions can handle RELAY_EARLY cells, and now that we're enforcing
19919 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19920 remove this workaround. Addresses bug 4786.
19922 o Code simplifications and refactoring:
19923 - Use OpenSSL's built-in SSL_state_string_long() instead of our
19924 own homebrewed ssl_state_to_string() replacement. Patch from
19925 Emile Snyder. Fixes bug 4653.
19926 - Use macros to indicate OpenSSL versions, so we don't need to worry
19927 about accidental hexadecimal bit shifts.
19928 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
19930 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
19931 - Use the smartlist_add_asprintf() alias more consistently.
19932 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
19933 invalid value, rather than just -1.
19934 - Rename a handful of old identifiers, mostly related to crypto
19935 structures and crypto functions. By convention, our "create an
19936 object" functions are called "type_new()", our "free an object"
19937 functions are called "type_free()", and our types indicate that
19938 they are types only with a final "_t". But a handful of older
19939 types and functions broke these rules, with function names like
19940 "type_create" or "subsystem_op_type", or with type names like
19944 Changes in version 0.2.3.10-alpha - 2011-12-16
19945 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
19946 Tor's buffers code. Absolutely everybody should upgrade.
19948 The bug relied on an incorrect calculation when making data continuous
19949 in one of our IO buffers, if the first chunk of the buffer was
19950 misaligned by just the wrong amount. The miscalculation would allow an
19951 attacker to overflow a piece of heap-allocated memory. To mount this
19952 attack, the attacker would need to either open a SOCKS connection to
19953 Tor's SocksPort (usually restricted to localhost), or target a Tor
19954 instance configured to make its connections through a SOCKS proxy
19955 (which Tor does not do by default).
19957 Good security practice requires that all heap-overflow bugs should be
19958 presumed to be exploitable until proven otherwise, so we are treating
19959 this as a potential code execution attack. Please upgrade immediately!
19960 This bug does not affect bufferevents-based builds of Tor. Special
19961 thanks to "Vektor" for reporting this issue to us!
19963 This release also contains a few minor bugfixes for issues discovered
19967 - Fix a heap overflow bug that could occur when trying to pull
19968 data into the first chunk of a buffer, when that chunk had
19969 already had some data drained from it. Fixes CVE-2011-2778;
19970 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
19973 - If we can't attach streams to a rendezvous circuit when we
19974 finish connecting to a hidden service, clear the rendezvous
19975 circuit's stream-isolation state and try to attach streams
19976 again. Previously, we cleared rendezvous circuits' isolation
19977 state either too early (if they were freshly built) or not at all
19978 (if they had been built earlier and were cannibalized). Bugfix on
19979 0.2.3.3-alpha; fixes bug 4655.
19980 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
19981 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
19982 - Fix an assertion failure when a relay with accounting enabled
19983 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
19986 - Update to the December 6 2011 Maxmind GeoLite Country database.
19989 Changes in version 0.2.2.35 - 2011-12-16
19990 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
19991 buffers code. Absolutely everybody should upgrade.
19993 The bug relied on an incorrect calculation when making data continuous
19994 in one of our IO buffers, if the first chunk of the buffer was
19995 misaligned by just the wrong amount. The miscalculation would allow an
19996 attacker to overflow a piece of heap-allocated memory. To mount this
19997 attack, the attacker would need to either open a SOCKS connection to
19998 Tor's SocksPort (usually restricted to localhost), or target a Tor
19999 instance configured to make its connections through a SOCKS proxy
20000 (which Tor does not do by default).
20002 Good security practice requires that all heap-overflow bugs should be
20003 presumed to be exploitable until proven otherwise, so we are treating
20004 this as a potential code execution attack. Please upgrade immediately!
20005 This bug does not affect bufferevents-based builds of Tor. Special
20006 thanks to "Vektor" for reporting this issue to us!
20008 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20009 crash bugs for unusual configurations, and a long-term bug that
20010 would prevent Tor from starting on Windows machines with draconian
20013 With this release, we remind everyone that 0.2.0.x has reached its
20014 formal end-of-life. Those Tor versions have many known flaws, and
20015 nobody should be using them. You should upgrade -- ideally to the
20016 0.2.2.x series. If you're using a Linux or BSD and its packages are
20017 obsolete, stop using those packages and upgrade anyway.
20019 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20020 longer receive support after some time in early 2012.
20023 - Fix a heap overflow bug that could occur when trying to pull
20024 data into the first chunk of a buffer, when that chunk had
20025 already had some data drained from it. Fixes CVE-2011-2778;
20026 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20027 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20028 that it doesn't attempt to allocate a socketpair. This could cause
20029 some problems on Windows systems with overzealous firewalls. Fix for
20030 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20032 - If we mark an OR connection for close based on a cell we process,
20033 don't process any further cells on it. We already avoid further
20034 reads on marked-for-close connections, but now we also discard the
20035 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20036 which was the first version where we might mark a connection for
20037 close based on processing a cell on it.
20038 - Correctly sanity-check that we don't underflow on a memory
20039 allocation (and then assert) for hidden service introduction
20040 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20041 bugfix on 0.2.1.5-alpha.
20042 - Fix a memory leak when we check whether a hidden service
20043 descriptor has any usable introduction points left. Fixes bug
20044 4424. Bugfix on 0.2.2.25-alpha.
20045 - Don't crash when we're running as a relay and don't have a GeoIP
20046 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20047 we've had in the 0.2.3.x branch already.
20048 - When running as a client, do not print a misleading (and plain
20049 wrong) log message that we're collecting "directory request"
20050 statistics: clients don't collect statistics. Also don't create a
20051 useless (because empty) stats file in the stats/ directory. Fixes
20052 bug 4353; bugfix on 0.2.2.34.
20055 - Detect failure to initialize Libevent. This fix provides better
20056 detection for future instances of bug 4457.
20057 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20058 function. This was eating up hideously large amounts of time on some
20059 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20060 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20061 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20063 - Don't warn about unused log_mutex in log.c when building with
20064 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20065 0.1.0.6-rc which introduced --disable-threads.
20066 - When configuring, starting, or stopping an NT service, stop
20067 immediately after the service configuration attempt has succeeded
20068 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20069 - When sending a NETINFO cell, include the original address
20070 received for the other side, not its canonical address. Found
20071 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20072 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20073 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20074 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20075 occurred when a client tried to fetch a descriptor for a bridge
20076 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20077 - Backport fixes for a pair of compilation warnings on Windows.
20078 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20079 - If we had ever tried to call tor_addr_to_str on an address of
20080 unknown type, we would have done a strdup on an uninitialized
20081 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20082 Reported by "troll_un".
20083 - Correctly detect and handle transient lookup failures from
20084 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20085 Reported by "troll_un".
20086 - Fix null-pointer access that could occur if TLS allocation failed.
20087 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20088 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20089 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20092 - Add two new config options for directory authorities:
20093 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20094 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20095 that is always sufficient to satisfy the bandwidth requirement for
20096 the Guard flag. Now it will be easier for researchers to simulate
20097 Tor networks with different values. Resolves ticket 4484.
20098 - When Tor ignores a hidden service specified in its configuration,
20099 include the hidden service's directory in the warning message.
20100 Previously, we would only tell the user that some hidden service
20101 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20102 - Update to the December 6 2011 Maxmind GeoLite Country database.
20104 o Packaging changes:
20105 - Make it easier to automate expert package builds on Windows,
20106 by removing an absolute path from makensis.exe command.
20109 Changes in version 0.2.1.32 - 2011-12-16
20110 Tor 0.2.1.32 backports important security and privacy fixes for
20111 oldstable. This release is intended only for package maintainers and
20112 others who cannot use the 0.2.2 stable series. All others should be
20113 using Tor 0.2.2.x or newer.
20115 The Tor 0.2.1.x series will reach formal end-of-life some time in
20116 early 2012; we will stop releasing patches for it then.
20118 o Major bugfixes (also included in 0.2.2.x):
20119 - Correctly sanity-check that we don't underflow on a memory
20120 allocation (and then assert) for hidden service introduction
20121 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20122 bugfix on 0.2.1.5-alpha.
20123 - Fix a heap overflow bug that could occur when trying to pull
20124 data into the first chunk of a buffer, when that chunk had
20125 already had some data drained from it. Fixes CVE-2011-2778;
20126 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20129 - Update to the December 6 2011 Maxmind GeoLite Country database.
20132 Changes in version 0.2.3.9-alpha - 2011-12-08
20133 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
20134 a "DisableNetwork" security feature that bundles can use to avoid
20135 touching the network until bridges are configured, moves forward on
20136 the pluggable transport design, fixes a flaw in the hidden service
20137 design that unnecessarily prevented clients with wrong clocks from
20138 reaching hidden services, and fixes a wide variety of other issues.
20141 - Clients can now connect to private bridges over IPv6. Bridges
20142 still need at least one IPv4 address in order to connect to
20143 other relays. Note that we don't yet handle the case where the
20144 user has two bridge lines for the same bridge (one IPv4, one
20145 IPv6). Implements parts of proposal 186.
20146 - New "DisableNetwork" config option to prevent Tor from launching any
20147 connections or accepting any connections except on a control port.
20148 Bundles and controllers can set this option before letting Tor talk
20149 to the rest of the network, for example to prevent any connections
20150 to a non-bridge address. Packages like Orbot can also use this
20151 option to instruct Tor to save power when the network is off.
20152 - Clients and bridges can now be configured to use a separate
20153 "transport" proxy. This approach makes the censorship arms race
20154 easier by allowing bridges to use protocol obfuscation plugins. It
20155 implements the "managed proxy" part of proposal 180 (ticket 3472).
20156 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20157 implementation. It makes AES_CTR about 7% faster than our old one
20158 (which was about 10% faster than the one OpenSSL used to provide).
20159 Resolves ticket 4526.
20160 - Add a "tor2web mode" for clients that want to connect to hidden
20161 services non-anonymously (and possibly more quickly). As a safety
20162 measure to try to keep users from turning this on without knowing
20163 what they are doing, tor2web mode must be explicitly enabled at
20164 compile time, and a copy of Tor compiled to run in tor2web mode
20165 cannot be used as a normal Tor client. Implements feature 2553.
20166 - Add experimental support for running on Windows with IOCP and no
20167 kernel-space socket buffers. This feature is controlled by a new
20168 "UserspaceIOCPBuffers" config option (off by default), which has
20169 no effect unless Tor has been built with support for bufferevents,
20170 is running on Windows, and has enabled IOCP. This may, in the long
20171 run, help solve or mitigate bug 98.
20172 - Use a more secure consensus parameter voting algorithm. Now at
20173 least three directory authorities or a majority of them must
20174 vote on a given parameter before it will be included in the
20175 consensus. Implements proposal 178.
20178 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20179 They used to check that the timestamp was within 30 minutes
20180 of their system clock, so they could cap the size of their
20181 replay-detection cache, but that approach unnecessarily refused
20182 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20183 the v3 intro-point protocol (the first one which sent a timestamp
20184 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20185 - Only use the EVP interface when AES acceleration is enabled,
20186 to avoid a 5-7% performance regression. Resolves issue 4525;
20187 bugfix on 0.2.3.8-alpha.
20189 o Privacy/anonymity features (bridge detection):
20190 - Make bridge SSL certificates a bit more stealthy by using random
20191 serial numbers, in the same fashion as OpenSSL when generating
20192 self-signed certificates. Implements ticket 4584.
20193 - Introduce a new config option "DynamicDHGroups", enabled by
20194 default, which provides each bridge with a unique prime DH modulus
20195 to be used during SSL handshakes. This option attempts to help
20196 against censors who might use the Apache DH modulus as a static
20197 identifier for bridges. Addresses ticket 4548.
20199 o Minor features (new/different config options):
20200 - New configuration option "DisableDebuggerAttachment" (on by default)
20201 to prevent basic debugging attachment attempts by other processes.
20202 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20203 - Allow MapAddress directives to specify matches against super-domains,
20204 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20205 Implements issue 933.
20206 - Slightly change behavior of "list" options (that is, config
20207 options that can appear more than once) when they appear both in
20208 torrc and on the command line. Previously, the command-line options
20209 would be appended to the ones from torrc. Now, the command-line
20210 options override the torrc options entirely. This new behavior
20211 allows the user to override list options (like exit policies and
20212 ports to listen on) from the command line, rather than simply
20213 appending to the list.
20214 - You can get the old (appending) command-line behavior for "list"
20215 options by prefixing the option name with a "+".
20216 - You can remove all the values for a "list" option from the command
20217 line without adding any new ones by prefixing the option name
20219 - Add experimental support for a "defaults" torrc file to be parsed
20220 before the regular torrc. Torrc options override the defaults file's
20221 options in the same way that the command line overrides the torrc.
20222 The SAVECONF controller command saves only those options which
20223 differ between the current configuration and the defaults file. HUP
20224 reloads both files. (Note: This is an experimental feature; its
20225 behavior will probably be refined in future 0.2.3.x-alpha versions
20226 to better meet packagers' needs.) Implements task 4552.
20229 - Try to make the introductory warning message that Tor prints on
20230 startup more useful for actually finding help and information.
20231 Resolves ticket 2474.
20232 - Running "make version" now displays the version of Tor that
20233 we're about to build. Idea from katmagic; resolves issue 4400.
20234 - Expire old or over-used hidden service introduction points.
20235 Required by fix for bug 3460.
20236 - Move the replay-detection cache for the RSA-encrypted parts of
20237 INTRODUCE2 cells to the introduction point data structures.
20238 Previously, we would use one replay-detection cache per hidden
20239 service. Required by fix for bug 3460.
20240 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20241 public key replay-detection cache from 60 minutes to 5 minutes. This
20242 replay-detection cache is now used only to detect multiple
20243 INTRODUCE2 cells specifying the same rendezvous point, so we can
20244 avoid launching multiple simultaneous attempts to connect to it.
20246 o Minor bugfixes (on Tor 0.2.2.x and earlier):
20247 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20248 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20250 - Fix a minor formatting issue in one of tor-gencert's error messages.
20252 - Prevent a false positive from the check-spaces script, by disabling
20253 the "whitespace between function name and (" check for functions
20255 - Fix a log message suggesting that people contact a non-existent
20256 email address. Fixes bug 3448.
20257 - Fix null-pointer access that could occur if TLS allocation failed.
20258 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20259 - Report a real bootstrap problem to the controller on router
20260 identity mismatch. Previously we just said "foo", which probably
20261 made a lot of sense at the time. Fixes bug 4169; bugfix on
20263 - If we had ever tried to call tor_addr_to_str() on an address of
20264 unknown type, we would have done a strdup() on an uninitialized
20265 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20266 Reported by "troll_un".
20267 - Correctly detect and handle transient lookup failures from
20268 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20269 Reported by "troll_un".
20270 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20271 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20272 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20273 bug 4532; found by "troll_un".
20275 o Minor bugfixes (on Tor 0.2.3.x):
20276 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
20278 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
20279 circuit for use as a hidden service client's rendezvous point.
20280 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
20281 with help from wanoskarnet.
20282 - Restore behavior of overriding SocksPort, ORPort, and similar
20283 options from the command line. Bugfix on 0.2.3.3-alpha.
20286 - Properly handle the case where the build-tree is not the same
20287 as the source tree when generating src/common/common_sha1.i,
20288 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20289 bugfix on 0.2.0.1-alpha.
20291 o Code simplifications, cleanups, and refactorings:
20292 - Remove the pure attribute from all functions that used it
20293 previously. In many cases we assigned it incorrectly, because the
20294 functions might assert or call impure functions, and we don't have
20295 evidence that keeping the pure attribute is worthwhile. Implements
20296 changes suggested in ticket 4421.
20297 - Remove some dead code spotted by coverity. Fixes cid 432.
20298 Bugfix on 0.2.3.1-alpha, closes bug 4637.
20301 Changes in version 0.2.3.8-alpha - 2011-11-22
20302 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
20303 socketpair-related bug that has been bothering Windows users. It adds
20304 support to serve microdescriptors to controllers, so Vidalia's network
20305 map can resume listing relays (once Vidalia implements its side),
20306 and adds better support for hardware AES acceleration. Finally, it
20307 starts the process of adjusting the bandwidth cutoff for getting the
20308 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
20309 that tiny relays harm performance more than they help network capacity.
20312 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20313 that it doesn't attempt to allocate a socketpair. This could cause
20314 some problems on Windows systems with overzealous firewalls. Fix for
20315 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20317 - Correctly sanity-check that we don't underflow on a memory
20318 allocation (and then assert) for hidden service introduction
20319 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20320 bugfix on 0.2.1.5-alpha.
20321 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20322 flag. In the past few years the average relay speed has picked
20323 up, and while the "top 7/8 of the network get the Fast flag" and
20324 "all relays with 20KB or more of capacity get the Fast flag" rules
20325 used to have the same result, now the top 7/8 of the network has
20326 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20327 - Fix a rare assertion failure when checking whether a v0 hidden
20328 service descriptor has any usable introduction points left, and
20329 we don't have enough information to build a circuit to the first
20330 intro point named in the descriptor. The HS client code in
20331 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
20332 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
20333 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
20334 - Make bridge authorities not crash when they are asked for their own
20335 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
20336 - When running as a client, do not print a misleading (and plain
20337 wrong) log message that we're collecting "directory request"
20338 statistics: clients don't collect statistics. Also don't create a
20339 useless (because empty) stats file in the stats/ directory. Fixes
20340 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
20343 - Allow Tor controllers like Vidalia to obtain the microdescriptor
20344 for a relay by identity digest or nickname. Previously,
20345 microdescriptors were only available by their own digests, so a
20346 controller would have to ask for and parse the whole microdescriptor
20347 consensus in order to look up a single relay's microdesc. Fixes
20348 bug 3832; bugfix on 0.2.3.1-alpha.
20349 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20350 operations can use hardware acceleration (if present). Resolves
20353 o Minor bugfixes (on 0.2.2.x and earlier):
20354 - Detect failure to initialize Libevent. This fix provides better
20355 detection for future instances of bug 4457.
20356 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20357 function. This was eating up hideously large amounts of time on some
20358 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20359 - Don't warn about unused log_mutex in log.c when building with
20360 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20361 0.1.0.6-rc which introduced --disable-threads.
20362 - Allow manual 'authenticate' commands to the controller interface
20363 from netcat (nc) as well as telnet. We were rejecting them because
20364 they didn't come with the expected whitespace at the end of the
20365 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20366 - Fix some (not actually triggerable) buffer size checks in usage of
20367 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20369 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20370 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20371 - When configuring, starting, or stopping an NT service, stop
20372 immediately after the service configuration attempt has succeeded
20373 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20374 - When sending a NETINFO cell, include the original address
20375 received for the other side, not its canonical address. Found
20376 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20377 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20378 can pick them up when the tests aren't disabled. Bugfix on
20379 0.2.2.4-alpha which introduced tinytest.
20380 - Fix a memory leak when we check whether a hidden service
20381 descriptor has any usable introduction points left. Fixes bug
20382 4424. Bugfix on 0.2.2.25-alpha.
20383 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20384 occurred when a client tried to fetch a descriptor for a bridge
20385 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20387 o Minor bugfixes (on 0.2.3.x):
20388 - Make util unit tests build correctly with MSVC. Bugfix on
20389 0.2.3.3-alpha. Patch by Gisle Vanem.
20390 - Successfully detect AUTH_CHALLENGE cells with no recognized
20391 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
20392 Found by frosty_un.
20393 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
20394 it should still send a NETINFO cell to allow the connection to
20395 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
20397 - Log less loudly when we get an invalid authentication certificate
20398 from a source other than a directory authority: it's not unusual
20399 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
20401 - Tolerate servers with more clock skew in their authentication
20402 certificates than previously. Fixes bug 4371; bugfix on
20404 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
20405 on 0.2.3.4-alpha and 0.2.3.6-alpha.
20408 - Add two new config options for directory authorities:
20409 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20410 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20411 that is always sufficient to satisfy the bandwidth requirement for
20412 the Guard flag. Now it will be easier for researchers to simulate
20413 Tor networks with different values. Resolves ticket 4484.
20414 - When Tor ignores a hidden service specified in its configuration,
20415 include the hidden service's directory in the warning message.
20416 Previously, we would only tell the user that some hidden service
20417 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20418 - When we fail to initialize Libevent, retry with IOCP disabled so we
20419 don't need to turn on multi-threading support in Libevent, which in
20420 turn requires a working socketpair(). This is a workaround for bug
20421 4457, which affects Libevent versions from 2.0.1-alpha through
20423 - Detect when we try to build on a platform that doesn't define
20424 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20425 - Update to the November 1 2011 Maxmind GeoLite Country database.
20427 o Packaging changes:
20428 - Make it easier to automate expert package builds on Windows,
20429 by removing an absolute path from makensis.exe command.
20431 o Code simplifications and refactoring:
20432 - Remove some redundant #include directives throughout the code.
20433 Patch from Andrea Gelmini.
20434 - Unconditionally use OpenSSL's AES implementation instead of our
20435 old built-in one. OpenSSL's AES has been better for a while, and
20436 relatively few servers should still be on any version of OpenSSL
20437 that doesn't have good optimized assembly AES.
20438 - Use the name "CERTS" consistently to refer to the new cell type;
20439 we were calling it CERT in some places and CERTS in others.
20442 - Numerous new unit tests for functions in util.c and address.c by
20444 - The long-disabled benchmark tests are now split into their own
20445 ./src/test/bench binary.
20446 - The benchmark tests can now use more accurate timers than
20447 gettimeofday() when such timers are available.
20450 Changes in version 0.2.3.7-alpha - 2011-10-30
20451 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20452 the new v3 handshake. It also resolves yet another bridge address
20456 - If we mark an OR connection for close based on a cell we process,
20457 don't process any further cells on it. We already avoid further
20458 reads on marked-for-close connections, but now we also discard the
20459 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20460 which was the first version where we might mark a connection for
20461 close based on processing a cell on it.
20462 - Fix a double-free bug that would occur when we received an invalid
20463 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20464 bugfix on 0.2.3.6-alpha.
20465 - Bridges no longer include their address in NETINFO cells on outgoing
20466 OR connections, to allow them to blend in better with clients.
20467 Removes another avenue for enumerating bridges. Reported by
20468 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20469 cells were introduced.
20472 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20473 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20476 Changes in version 0.2.3.6-alpha - 2011-10-26
20477 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20478 anonymity vulnerability where an attacker can deanonymize Tor
20479 users. Everybody should upgrade.
20481 This release also features support for a new v3 connection handshake
20482 protocol, and fixes to make hidden service connections more robust.
20485 - Implement a new handshake protocol (v3) for authenticating Tors to
20486 each other over TLS. It should be more resistant to fingerprinting
20487 than previous protocols, and should require less TLS hacking for
20488 future Tor implementations. Implements proposal 176.
20489 - Allow variable-length padding cells to disguise the length of
20490 Tor's TLS records. Implements part of proposal 184.
20492 o Privacy/anonymity fixes (clients):
20493 - Clients and bridges no longer send TLS certificate chains on
20494 outgoing OR connections. Previously, each client or bridge would
20495 use the same cert chain for all outgoing OR connections until
20496 its IP address changes, which allowed any relay that the client
20497 or bridge contacted to determine which entry guards it is using.
20498 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20499 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20500 no longer considers that connection as suitable for satisfying a
20501 circuit EXTEND request. Now relays can protect clients from the
20502 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20503 - Directory authorities no longer assign the Guard flag to relays
20504 that haven't upgraded to the above "refuse EXTEND requests
20505 to client connections" fix. Now directory authorities can
20506 protect clients from the CVE-2011-2768 issue even if neither
20507 the clients nor the relays have upgraded yet. There's a new
20508 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20509 to let us transition smoothly, else tomorrow there would be no
20512 o Major bugfixes (hidden services):
20513 - Improve hidden service robustness: when an attempt to connect to
20514 a hidden service ends, be willing to refetch its hidden service
20515 descriptors from each of the HSDir relays responsible for them
20516 immediately. Previously, we would not consider refetching the
20517 service's descriptors from each HSDir for 15 minutes after the last
20518 fetch, which was inconvenient if the hidden service was not running
20519 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20520 - When one of a hidden service's introduction points appears to be
20521 unreachable, stop trying it. Previously, we would keep trying
20522 to build circuits to the introduction point until we lost the
20523 descriptor, usually because the user gave up and restarted Tor.
20524 Partly fixes bug 3825.
20525 - Don't launch a useless circuit after failing to use one of a
20526 hidden service's introduction points. Previously, we would
20527 launch a new introduction circuit, but not set the hidden service
20528 which that circuit was intended to connect to, so it would never
20529 actually be used. A different piece of code would then create a
20530 new introduction circuit correctly. Bug reported by katmagic and
20531 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20533 o Major bugfixes (other):
20534 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20535 that they initiated. Relays could distinguish incoming bridge
20536 connections from client connections, creating another avenue for
20537 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20538 Found by "frosty_un".
20539 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20540 tor gets started. This prevents a wrong average bandwidth
20541 estimate, which would cause relays to always start a new accounting
20542 interval at the earliest possible moment. Fixes bug 2003; bugfix
20543 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20544 immensely in tracking this bug down.
20545 - Fix a crash bug when changing node restrictions while a DNS lookup
20546 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20549 o Minor bugfixes (on 0.2.2.x and earlier):
20550 - When a hidden service turns an extra service-side introduction
20551 circuit into a general-purpose circuit, free the rend_data and
20552 intro_key fields first, so we won't leak memory if the circuit
20553 is cannibalized for use as another service-side introduction
20554 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20555 - Rephrase the log message emitted if the TestSocks check is
20556 successful. Patch from Fabian Keil; fixes bug 4094.
20557 - Bridges now skip DNS self-tests, to act a little more stealthily.
20558 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20559 bridges. Patch by "warms0x".
20560 - Remove a confusing dollar sign from the example fingerprint in the
20561 man page, and also make the example fingerprint a valid one. Fixes
20562 bug 4309; bugfix on 0.2.1.3-alpha.
20563 - Fix internal bug-checking logic that was supposed to catch
20564 failures in digest generation so that it will fail more robustly
20565 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20566 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20567 - Report any failure in init_keys() calls launched because our
20568 IP address has changed. Spotted by Coverity Scan. Bugfix on
20569 0.1.1.4-alpha; fixes CID 484.
20571 o Minor bugfixes (on 0.2.3.x):
20572 - Fix a bug in configure.in that kept it from building a configure
20573 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20574 bugfix on 0.2.3.1-alpha.
20575 - Don't warn users that they are exposing a client port to the
20576 Internet if they have specified an RFC1918 address. Previously,
20577 we would warn if the user had specified any non-loopback
20578 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20579 - Fix memory leaks in the failing cases of the new SocksPort and
20580 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20581 fixes coverity CIDs 485, 486, and 487.
20584 - When a hidden service's introduction point times out, consider
20585 trying it again during the next attempt to connect to the
20586 HS. Previously, we would not try it again unless a newly fetched
20587 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20588 - The next version of Windows will be called Windows 8, and it has
20589 a major version of 6, minor version of 2. Correctly identify that
20590 version instead of calling it "Very recent version". Resolves
20591 ticket 4153; reported by funkstar.
20592 - The Bridge Authority now writes statistics on how many bridge
20593 descriptors it gave out in total, and how many unique descriptors
20594 it gave out. It also lists how often the most and least commonly
20595 fetched descriptors were given out, as well as the median and
20596 25th/75th percentile. Implements tickets 4200 and 4294.
20597 - Update to the October 4 2011 Maxmind GeoLite Country database.
20599 o Code simplifications and refactoring:
20600 - Remove some old code to remember statistics about which descriptors
20601 we've served as a directory mirror. The feature wasn't used and
20602 is outdated now that microdescriptors are around.
20603 - Rename Tor functions that turn strings into addresses, so that
20604 "parse" indicates that no hostname resolution occurs, and
20605 "lookup" indicates that hostname resolution may occur. This
20606 should help prevent mistakes in the future. Fixes bug 3512.
20609 Changes in version 0.2.2.34 - 2011-10-26
20610 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20611 can deanonymize Tor users. Everybody should upgrade.
20613 The attack relies on four components: 1) Clients reuse their TLS cert
20614 when talking to different relays, so relays can recognize a user by
20615 the identity key in her cert. 2) An attacker who knows the client's
20616 identity key can probe each guard relay to see if that identity key
20617 is connected to that guard relay right now. 3) A variety of active
20618 attacks in the literature (starting from "Low-Cost Traffic Analysis
20619 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20620 discover the guard relays that a Tor user visiting the website is using.
20621 4) Clients typically pick three guards at random, so the set of guards
20622 for a given user could well be a unique fingerprint for her. This
20623 release fixes components #1 and #2, which is enough to block the attack;
20624 the other two remain as open research problems. Special thanks to
20625 "frosty_un" for reporting the issue to us!
20627 Clients should upgrade so they are no longer recognizable by the TLS
20628 certs they present. Relays should upgrade so they no longer allow a
20629 remote attacker to probe them to test whether unpatched clients are
20630 currently connected to them.
20632 This release also fixes several vulnerabilities that allow an attacker
20633 to enumerate bridge relays. Some bridge enumeration attacks still
20634 remain; see for example proposal 188.
20636 o Privacy/anonymity fixes (clients):
20637 - Clients and bridges no longer send TLS certificate chains on
20638 outgoing OR connections. Previously, each client or bridge would
20639 use the same cert chain for all outgoing OR connections until
20640 its IP address changes, which allowed any relay that the client
20641 or bridge contacted to determine which entry guards it is using.
20642 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20643 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20644 no longer considers that connection as suitable for satisfying a
20645 circuit EXTEND request. Now relays can protect clients from the
20646 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20647 - Directory authorities no longer assign the Guard flag to relays
20648 that haven't upgraded to the above "refuse EXTEND requests
20649 to client connections" fix. Now directory authorities can
20650 protect clients from the CVE-2011-2768 issue even if neither
20651 the clients nor the relays have upgraded yet. There's a new
20652 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20653 to let us transition smoothly, else tomorrow there would be no
20656 o Privacy/anonymity fixes (bridge enumeration):
20657 - Bridge relays now do their directory fetches inside Tor TLS
20658 connections, like all the other clients do, rather than connecting
20659 directly to the DirPort like public relays do. Removes another
20660 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20661 - Bridges relays now build circuits for themselves in a more similar
20662 way to how clients build them. Removes another avenue for
20663 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20664 when bridges were introduced.
20665 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20666 that they initiated. Relays could distinguish incoming bridge
20667 connections from client connections, creating another avenue for
20668 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20669 Found by "frosty_un".
20672 - Fix a crash bug when changing node restrictions while a DNS lookup
20673 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20675 - Don't launch a useless circuit after failing to use one of a
20676 hidden service's introduction points. Previously, we would
20677 launch a new introduction circuit, but not set the hidden service
20678 which that circuit was intended to connect to, so it would never
20679 actually be used. A different piece of code would then create a
20680 new introduction circuit correctly. Bug reported by katmagic and
20681 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20684 - Change an integer overflow check in the OpenBSD_Malloc code so
20685 that GCC is less likely to eliminate it as impossible. Patch
20686 from Mansour Moufid. Fixes bug 4059.
20687 - When a hidden service turns an extra service-side introduction
20688 circuit into a general-purpose circuit, free the rend_data and
20689 intro_key fields first, so we won't leak memory if the circuit
20690 is cannibalized for use as another service-side introduction
20691 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20692 - Bridges now skip DNS self-tests, to act a little more stealthily.
20693 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20694 bridges. Patch by "warms0x".
20695 - Fix internal bug-checking logic that was supposed to catch
20696 failures in digest generation so that it will fail more robustly
20697 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20698 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20699 - Report any failure in init_keys() calls launched because our
20700 IP address has changed. Spotted by Coverity Scan. Bugfix on
20701 0.1.1.4-alpha; fixes CID 484.
20703 o Minor bugfixes (log messages and documentation):
20704 - Remove a confusing dollar sign from the example fingerprint in the
20705 man page, and also make the example fingerprint a valid one. Fixes
20706 bug 4309; bugfix on 0.2.1.3-alpha.
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 - Downgrade log messages about circuit timeout calibration from
20712 "notice" to "info": they don't require or suggest any human
20713 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20714 bugfix on 0.2.2.14-alpha.
20717 - Turn on directory request statistics by default and include them in
20718 extra-info descriptors. Don't break if we have no GeoIP database.
20719 Backported from 0.2.3.1-alpha; implements ticket 3951.
20720 - Update to the October 4 2011 Maxmind GeoLite Country database.
20723 Changes in version 0.2.1.31 - 2011-10-26
20724 Tor 0.2.1.31 backports important security and privacy fixes for
20725 oldstable. This release is intended only for package maintainers and
20726 others who cannot use the 0.2.2 stable series. All others should be
20727 using Tor 0.2.2.x or newer.
20729 o Security fixes (also included in 0.2.2.x):
20730 - Replace all potentially sensitive memory comparison operations
20731 with versions whose runtime does not depend on the data being
20732 compared. This will help resist a class of attacks where an
20733 adversary can use variations in timing information to learn
20734 sensitive data. Fix for one case of bug 3122. (Safe memcmp
20735 implementation by Robert Ransom based partially on code by DJB.)
20736 - Fix an assert in parsing router descriptors containing IPv6
20737 addresses. This one took down the directory authorities when
20738 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
20740 o Privacy/anonymity fixes (also included in 0.2.2.x):
20741 - Clients and bridges no longer send TLS certificate chains on
20742 outgoing OR connections. Previously, each client or bridge would
20743 use the same cert chain for all outgoing OR connections until
20744 its IP address changes, which allowed any relay that the client
20745 or bridge contacted to determine which entry guards it is using.
20746 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20747 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20748 no longer considers that connection as suitable for satisfying a
20749 circuit EXTEND request. Now relays can protect clients from the
20750 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20751 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20752 that they initiated. Relays could distinguish incoming bridge
20753 connections from client connections, creating another avenue for
20754 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20755 Found by "frosty_un".
20756 - When receiving a hidden service descriptor, check that it is for
20757 the hidden service we wanted. Previously, Tor would store any
20758 hidden service descriptors that a directory gave it, whether it
20759 wanted them or not. This wouldn't have let an attacker impersonate
20760 a hidden service, but it did let directories pre-seed a client
20761 with descriptors that it didn't want. Bugfix on 0.0.6.
20762 - Avoid linkability based on cached hidden service descriptors: forget
20763 all hidden service descriptors cached as a client when processing a
20764 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
20765 - Make the bridge directory authority refuse to answer directory
20766 requests for "all" descriptors. It used to include bridge
20767 descriptors in its answer, which was a major information leak.
20768 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
20769 - Don't attach new streams to old rendezvous circuits after SIGNAL
20770 NEWNYM. Previously, we would keep using an existing rendezvous
20771 circuit if it remained open (i.e. if it were kept open by a
20772 long-lived stream, or if a new stream were attached to it before
20773 Tor could notice that it was old and no longer in use). Bugfix on
20774 0.1.1.15-rc; fixes bug 3375.
20776 o Minor bugfixes (also included in 0.2.2.x):
20777 - When we restart our relay, we might get a successful connection
20778 from the outside before we've started our reachability tests,
20779 triggering a warning: "ORPort found reachable, but I have no
20780 routerinfo yet. Failing to inform controller of success." This
20781 bug was harmless unless Tor is running under a controller
20782 like Vidalia, in which case the controller would never get a
20783 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
20785 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
20786 enabled. Fixes bug 1526.
20787 - Remove undocumented option "-F" from tor-resolve: it hasn't done
20788 anything since 0.2.1.16-rc.
20789 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
20790 None of the cases where we did this before were wrong, but by making
20791 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
20792 - Fix a rare crash bug that could occur when a client was configured
20793 with a large number of bridges. Fixes bug 2629; bugfix on
20794 0.2.1.2-alpha. Bugfix by trac user "shitlei".
20795 - Correct the warning displayed when a rendezvous descriptor exceeds
20796 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
20798 - Fix an uncommon assertion failure when running with DNSPort under
20799 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
20800 - When warning about missing zlib development packages during compile,
20801 give the correct package names. Bugfix on 0.2.0.1-alpha.
20802 - Require that introduction point keys and onion keys have public
20803 exponent 65537. Bugfix on 0.2.0.10-alpha.
20804 - Do not crash when our configuration file becomes unreadable, for
20805 example due to a permissions change, between when we start up
20806 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
20808 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
20810 - Always NUL-terminate the sun_path field of a sockaddr_un before
20811 passing it to the kernel. (Not a security issue: kernels are
20812 smart enough to reject bad sockaddr_uns.) Found by Coverity;
20813 CID #428. Bugfix on Tor 0.2.0.3-alpha.
20814 - Don't stack-allocate the list of supplementary GIDs when we're
20815 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
20816 could take up to 256K, which is way too much stack. Found by
20817 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
20819 o Minor bugfixes (only in 0.2.1.x):
20820 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
20821 rely on them. Bugfix on 0.2.1.30.
20822 - Use git revisions instead of svn revisions when generating our
20823 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
20825 o Minor features (also included in 0.2.2.x):
20826 - Adjust the expiration time on our SSL session certificates to
20827 better match SSL certs seen in the wild. Resolves ticket 4014.
20828 - Allow nameservers with IPv6 address. Resolves bug 2574.
20829 - Update to the October 4 2011 Maxmind GeoLite Country database.
20832 Changes in version 0.2.3.5-alpha - 2011-09-28
20833 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
20834 bridge relays; fixes an assertion error that many users started hitting
20835 today; and adds the ability to refill token buckets more often than
20836 once per second, allowing significant performance improvements.
20839 - Bridge relays now do their directory fetches inside Tor TLS
20840 connections, like all the other clients do, rather than connecting
20841 directly to the DirPort like public relays do. Removes another
20842 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20843 - Bridges relays now build circuits for themselves in a more similar
20844 way to how clients build them. Removes another avenue for
20845 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20846 when bridges were introduced.
20849 - Fix an "Assertion md->held_by_node == 1 failed" error that could
20850 occur when the same microdescriptor was referenced by two node_t
20851 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
20853 o Major features (networking):
20854 - Add a new TokenBucketRefillInterval option to refill token buckets
20855 more frequently than once per second. This should improve network
20856 performance, alleviate queueing problems, and make traffic less
20857 bursty. Implements proposal 183; closes ticket 3630. Design by
20858 Florian Tschorsch and Björn Scheuermann; implementation by
20862 - Change an integer overflow check in the OpenBSD_Malloc code so
20863 that GCC is less likely to eliminate it as impossible. Patch
20864 from Mansour Moufid. Fixes bug 4059.
20866 o Minor bugfixes (usability):
20867 - Downgrade log messages about circuit timeout calibration from
20868 "notice" to "info": they don't require or suggest any human
20869 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
20870 bugfix on 0.2.2.14-alpha.
20872 o Minor features (diagnostics):
20873 - When the system call to create a listener socket fails, log the
20874 error message explaining why. This may help diagnose bug 4027.
20877 Changes in version 0.2.3.4-alpha - 2011-09-13
20878 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
20879 tweak to Tor's TLS handshake that makes relays and bridges that run
20880 this new version reachable from Iran again. It also fixes a few new
20881 bugs in 0.2.3.x, and teaches relays to recognize when they're not
20882 listed in the network consensus and republish.
20884 o Major bugfixes (also part of 0.2.2.33):
20885 - Avoid an assertion failure when reloading a configuration with
20886 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20887 3923; bugfix on 0.2.2.25-alpha.
20889 o Minor features (security, also part of 0.2.2.33):
20890 - Check for replays of the public-key encrypted portion of an
20891 INTRODUCE1 cell, in addition to the current check for replays of
20892 the g^x value. This prevents a possible class of active attacks
20893 by an attacker who controls both an introduction point and a
20894 rendezvous point, and who uses the malleability of AES-CTR to
20895 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20896 that these attacks are infeasible (requiring the attacker to send
20897 on the order of zettabytes of altered cells in a short interval),
20898 but we'd rather block them off in case there are any classes of
20899 this attack that we missed. Reported by Willem Pinckaers.
20901 o Minor features (also part of 0.2.2.33):
20902 - Adjust the expiration time on our SSL session certificates to
20903 better match SSL certs seen in the wild. Resolves ticket 4014.
20904 - Change the default required uptime for a relay to be accepted as
20905 a HSDir (hidden service directory) from 24 hours to 25 hours.
20906 Improves on 0.2.0.10-alpha; resolves ticket 2649.
20907 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
20908 authorities to abstain from voting on assignment of the HSDir
20909 consensus flag. Related to bug 2649.
20910 - Update to the September 6 2011 Maxmind GeoLite Country database.
20912 o Minor bugfixes (also part of 0.2.2.33):
20913 - Demote the 'replay detected' log message emitted when a hidden
20914 service receives the same Diffie-Hellman public key in two different
20915 INTRODUCE2 cells to info level. A normal Tor client can cause that
20916 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
20917 fixes part of bug 2442.
20918 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
20919 level. There is nothing that a hidden service's operator can do
20920 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
20922 - Clarify a log message specifying the characters permitted in
20923 HiddenServiceAuthorizeClient client names. Previously, the log
20924 message said that "[A-Za-z0-9+-_]" were permitted; that could have
20925 given the impression that every ASCII character between "+" and "_"
20926 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
20928 o Build fixes (also part of 0.2.2.33):
20929 - Clean up some code issues that prevented Tor from building on older
20930 BSDs. Fixes bug 3894; reported by "grarpamp".
20931 - Search for a platform-specific version of "ar" when cross-compiling.
20932 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
20935 - Fix a bug where the SocksPort option (for example) would get
20936 ignored and replaced by the default if a SocksListenAddress
20937 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
20941 - Relays now try regenerating and uploading their descriptor more
20942 frequently if they are not listed in the consensus, or if the
20943 version of their descriptor listed in the consensus is too
20944 old. This fix should prevent situations where a server declines
20945 to re-publish itself because it has done so too recently, even
20946 though the authorities decided not to list its recent-enough
20947 descriptor. Fix for bug 3327.
20950 - Relays now include a reason for regenerating their descriptors
20951 in an HTTP header when uploading to the authorities. This will
20952 make it easier to debug descriptor-upload issues in the future.
20953 - When starting as root and then changing our UID via the User
20954 control option, and we have a ControlSocket configured, make sure
20955 that the ControlSocket is owned by the same account that Tor will
20956 run under. Implements ticket 3421; fix by Jérémy Bobbio.
20959 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
20960 utility function used in the control-port code). This shouldn't
20961 ever happen unless Tor is completely out of memory, but if it did
20962 happen and Tor somehow recovered from it, Tor could have sent a log
20963 message to a control port in the middle of a reply to a controller
20964 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
20965 - Make 'FetchUselessDescriptors' cause all descriptor types and
20966 all consensus types (including microdescriptors) to get fetched.
20967 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
20969 o Code refactoring:
20970 - Make a new "entry connection" struct as an internal subtype of "edge
20971 connection", to simplify the code and make exit connections smaller.
20974 Changes in version 0.2.2.33 - 2011-09-13
20975 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
20976 TLS handshake that makes relays and bridges that run this new version
20977 reachable from Iran again.
20980 - Avoid an assertion failure when reloading a configuration with
20981 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
20982 3923; bugfix on 0.2.2.25-alpha.
20984 o Minor features (security):
20985 - Check for replays of the public-key encrypted portion of an
20986 INTRODUCE1 cell, in addition to the current check for replays of
20987 the g^x value. This prevents a possible class of active attacks
20988 by an attacker who controls both an introduction point and a
20989 rendezvous point, and who uses the malleability of AES-CTR to
20990 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
20991 that these attacks are infeasible (requiring the attacker to send
20992 on the order of zettabytes of altered cells in a short interval),
20993 but we'd rather block them off in case there are any classes of
20994 this attack that we missed. Reported by Willem Pinckaers.
20997 - Adjust the expiration time on our SSL session certificates to
20998 better match SSL certs seen in the wild. Resolves ticket 4014.
20999 - Change the default required uptime for a relay to be accepted as
21000 a HSDir (hidden service directory) from 24 hours to 25 hours.
21001 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21002 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21003 authorities to abstain from voting on assignment of the HSDir
21004 consensus flag. Related to bug 2649.
21005 - Update to the September 6 2011 Maxmind GeoLite Country database.
21007 o Minor bugfixes (documentation and log messages):
21008 - Correct the man page to explain that HashedControlPassword and
21009 CookieAuthentication can both be set, in which case either method
21010 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21011 when we decided to allow these config options to both be set. Issue
21012 raised by bug 3898.
21013 - Demote the 'replay detected' log message emitted when a hidden
21014 service receives the same Diffie-Hellman public key in two different
21015 INTRODUCE2 cells to info level. A normal Tor client can cause that
21016 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21017 fixes part of bug 2442.
21018 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21019 level. There is nothing that a hidden service's operator can do
21020 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21022 - Clarify a log message specifying the characters permitted in
21023 HiddenServiceAuthorizeClient client names. Previously, the log
21024 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21025 given the impression that every ASCII character between "+" and "_"
21026 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21029 - Provide a substitute implementation of lround() for MSVC, which
21030 apparently lacks it. Patch from Gisle Vanem.
21031 - Clean up some code issues that prevented Tor from building on older
21032 BSDs. Fixes bug 3894; reported by "grarpamp".
21033 - Search for a platform-specific version of "ar" when cross-compiling.
21034 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21037 Changes in version 0.2.3.3-alpha - 2011-09-01
21038 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
21039 security, and provides client-side support for the microdescriptor
21040 and optimistic data features introduced earlier in the 0.2.3.x
21041 series. It also includes numerous critical bugfixes in the (optional)
21042 bufferevent-based networking backend.
21044 o Major features (stream isolation):
21045 - You can now configure Tor so that streams from different
21046 applications are isolated on different circuits, to prevent an
21047 attacker who sees your streams as they leave an exit node from
21048 linking your sessions to one another. To do this, choose some way
21049 to distinguish the applications: have them connect to different
21050 SocksPorts, or have one of them use SOCKS4 while the other uses
21051 SOCKS5, or have them pass different authentication strings to the
21052 SOCKS proxy. Then, use the new SocksPort syntax to configure the
21053 degree of isolation you need. This implements Proposal 171.
21054 - There's a new syntax for specifying multiple client ports (such as
21055 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
21056 multiple *Port entries with full addr:port syntax on each.
21057 The old *ListenAddress format is still supported, but you can't
21058 mix it with the new *Port syntax.
21060 o Major features (other):
21061 - Enable microdescriptor fetching by default for clients. This allows
21062 clients to download a much smaller amount of directory information.
21063 To disable it (and go back to the old-style consensus and
21064 descriptors), set "UseMicrodescriptors 0" in your torrc file.
21065 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
21066 "PortForwarding" config option), now supports Windows.
21067 - When using an exit relay running 0.2.3.x, clients can now
21068 "optimistically" send data before the exit relay reports that
21069 the stream has opened. This saves a round trip when starting
21070 connections where the client speaks first (such as web browsing).
21071 This behavior is controlled by a consensus parameter (currently
21072 disabled). To turn it on or off manually, use the "OptimisticData"
21073 torrc option. Implements proposal 181; code by Ian Goldberg.
21075 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
21076 - When using IOCP on Windows, we need to enable Libevent windows
21078 - The IOCP backend now works even when the user has not specified
21079 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
21080 Fixes part of bug 3752.
21081 - Correctly record the bytes we've read and written when using
21082 bufferevents, so that we can include them in our bandwidth history
21083 and advertised bandwidth. Fixes bug 3803.
21084 - Apply rate-limiting only at the bottom of a chain of filtering
21085 bufferevents. This prevents us from filling up internal read
21086 buffers and violating rate-limits when filtering bufferevents
21087 are enabled. Fixes part of bug 3804.
21088 - Add high-watermarks to the output buffers for filtered
21089 bufferevents. This prevents us from filling up internal write
21090 buffers and wasting CPU cycles when filtering bufferevents are
21091 enabled. Fixes part of bug 3804.
21092 - Correctly notice when data has been written from a bufferevent
21093 without flushing it completely. Fixes bug 3805.
21094 - Fix a bug where server-side tunneled bufferevent-based directory
21095 streams would get closed prematurely. Fixes bug 3814.
21096 - Fix a use-after-free error with per-connection rate-limiting
21097 buckets. Fixes bug 3888.
21099 o Major bugfixes (also part of 0.2.2.31-rc):
21100 - If we're configured to write our ControlPorts to disk, only write
21101 them after switching UID and creating the data directory. This way,
21102 we don't fail when starting up with a nonexistent DataDirectory
21103 and a ControlPortWriteToFile setting based on that directory. Fixes
21104 bug 3747; bugfix on Tor 0.2.2.26-beta.
21107 - Added a new CONF_CHANGED event so that controllers can be notified
21108 of any configuration changes made by other controllers, or by the
21109 user. Implements ticket 1692.
21110 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
21111 leak when using bufferevents, and lets Libevent worry about how to
21112 best copy data out of a buffer.
21113 - Replace files in stats/ rather than appending to them. Now that we
21114 include statistics in extra-info descriptors, it makes no sense to
21115 keep old statistics forever. Implements ticket 2930.
21117 o Minor features (build compatibility):
21118 - Limited, experimental support for building with nmake and MSVC.
21119 - Provide a substitute implementation of lround() for MSVC, which
21120 apparently lacks it. Patch from Gisle Vanem.
21122 o Minor features (also part of 0.2.2.31-rc):
21123 - Update to the August 2 2011 Maxmind GeoLite Country database.
21125 o Minor bugfixes (on 0.2.3.x-alpha):
21126 - Fix a spurious warning when parsing SOCKS requests with
21127 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
21128 - Get rid of a harmless warning that could happen on relays running
21129 with bufferevents. The warning was caused by someone doing an http
21130 request to a relay's orport. Also don't warn for a few related
21131 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
21133 o Minor bugfixes (on 2.2.x and earlier):
21134 - Correct the man page to explain that HashedControlPassword and
21135 CookieAuthentication can both be set, in which case either method
21136 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21137 when we decided to allow these config options to both be set. Issue
21138 raised by bug 3898.
21139 - The "--quiet" and "--hush" options now apply not only to Tor's
21140 behavior before logs are configured, but also to Tor's behavior in
21141 the absence of configured logs. Fixes bug 3550; bugfix on
21144 o Minor bugfixes (also part of 0.2.2.31-rc):
21145 - Write several files in text mode, on OSes that distinguish text
21146 mode from binary mode (namely, Windows). These files are:
21147 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21148 that collect those statistics; 'client_keys' and 'hostname' for
21149 hidden services that use authentication; and (in the tor-gencert
21150 utility) newly generated identity and signing keys. Previously,
21151 we wouldn't specify text mode or binary mode, leading to an
21152 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21153 the DirRecordUsageByCountry option which would have triggered
21154 the assertion failure was added), although this assertion failure
21155 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21156 - Selectively disable deprecation warnings on OS X because Lion
21157 started deprecating the shipped copy of openssl. Fixes bug 3643.
21158 - Remove an extra pair of quotation marks around the error
21159 message in control-port STATUS_GENERAL BUG events. Bugfix on
21160 0.1.2.6-alpha; fixes bug 3732.
21161 - When unable to format an address as a string, report its value
21162 as "???" rather than reusing the last formatted address. Bugfix
21165 o Code simplifications and refactoring:
21166 - Rewrite the listener-selection logic so that parsing which ports
21167 we want to listen on is now separate from binding to the ports
21171 - Building Tor with bufferevent support now requires Libevent
21172 2.0.13-stable or later. Previous versions of Libevent had bugs in
21173 SSL-related bufferevents and related issues that would make Tor
21174 work badly with bufferevents. Requiring 2.0.13-stable also allows
21175 Tor with bufferevents to take advantage of Libevent APIs
21176 introduced after 2.0.8-rc.
21179 Changes in version 0.2.2.32 - 2011-08-27
21180 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21181 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21182 a founder of the PETS community, a leader in our field, a mentor,
21183 and a friend. He left us with these words: "I had the possibility
21184 to contribute to this world that is not as it should be. I hope I
21185 could help in some areas to make the world a better place, and that
21186 I could also encourage other people to be engaged in improving the
21187 world. Please, stay engaged. This world needs you, your love, your
21188 initiative -- now I cannot be part of that anymore."
21190 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21191 ready. More than two years in the making, this release features improved
21192 client performance and hidden service reliability, better compatibility
21193 for Android, correct behavior for bridges that listen on more than
21194 one address, more extensible and flexible directory object handling,
21195 better reporting of network statistics, improved code security, and
21196 many many other features and bugfixes.
21199 Changes in version 0.2.2.31-rc - 2011-08-17
21200 Tor 0.2.2.31-rc is the second and hopefully final release candidate
21201 for the Tor 0.2.2.x series.
21204 - Remove an extra pair of quotation marks around the error
21205 message in control-port STATUS_GENERAL BUG events. Bugfix on
21206 0.1.2.6-alpha; fixes bug 3732.
21207 - If we're configured to write our ControlPorts to disk, only write
21208 them after switching UID and creating the data directory. This way,
21209 we don't fail when starting up with a nonexistent DataDirectory
21210 and a ControlPortWriteToFile setting based on that directory. Fixes
21211 bug 3747; bugfix on Tor 0.2.2.26-beta.
21214 - Update to the August 2 2011 Maxmind GeoLite Country database.
21217 - Allow GETINFO fingerprint to return a fingerprint even when
21218 we have not yet built a router descriptor. Fixes bug 3577;
21219 bugfix on 0.2.0.1-alpha.
21220 - Write several files in text mode, on OSes that distinguish text
21221 mode from binary mode (namely, Windows). These files are:
21222 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21223 that collect those statistics; 'client_keys' and 'hostname' for
21224 hidden services that use authentication; and (in the tor-gencert
21225 utility) newly generated identity and signing keys. Previously,
21226 we wouldn't specify text mode or binary mode, leading to an
21227 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21228 the DirRecordUsageByCountry option which would have triggered
21229 the assertion failure was added), although this assertion failure
21230 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21231 - Selectively disable deprecation warnings on OS X because Lion
21232 started deprecating the shipped copy of openssl. Fixes bug 3643.
21233 - When unable to format an address as a string, report its value
21234 as "???" rather than reusing the last formatted address. Bugfix
21238 Changes in version 0.2.3.2-alpha - 2011-07-18
21239 Tor 0.2.3.2-alpha introduces two new experimental features:
21240 microdescriptors and pluggable transports. It also continues cleaning
21241 up a variety of recently introduced features.
21244 - Clients can now use microdescriptors instead of regular descriptors
21245 to build circuits. Microdescriptors are authority-generated
21246 summaries of regular descriptors' contents, designed to change
21247 very rarely (see proposal 158 for details). This feature is
21248 designed to save bandwidth, especially for clients on slow internet
21249 connections. It's off by default for now, since nearly no caches
21250 support it, but it will be on-by-default for clients in a future
21251 version. You can use the UseMicrodescriptors option to turn it on.
21252 - Tor clients using bridges can now be configured to use a separate
21253 'transport' proxy for each bridge. This approach helps to resist
21254 censorship by allowing bridges to use protocol obfuscation
21255 plugins. It implements part of proposal 180. Implements ticket 2841.
21256 - While we're trying to bootstrap, record how many TLS connections
21257 fail in each state, and report which states saw the most failures
21258 in response to any bootstrap failures. This feature may speed up
21259 diagnosis of censorship events. Implements ticket 3116.
21261 o Major bugfixes (on 0.2.3.1-alpha):
21262 - When configuring a large set of nodes in EntryNodes (as with
21263 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
21264 random subset to be guards, and choose them in random
21265 order. Fixes bug 2798.
21266 - Tor could crash when remembering a consensus in a non-used consensus
21267 flavor without having a current consensus set. Fixes bug 3361.
21268 - Comparing an unknown address to a microdescriptor's shortened exit
21269 policy would always give a "rejected" result. Fixes bug 3599.
21270 - Using microdescriptors as a client no longer prevents Tor from
21271 uploading and downloading hidden service descriptors. Fixes
21275 - Allow nameservers with IPv6 address. Resolves bug 2574.
21276 - Accept attempts to include a password authenticator in the
21277 handshake, as supported by SOCKS5. This handles SOCKS clients that
21278 don't know how to omit a password when authenticating. Resolves
21280 - When configuring a large set of nodes in EntryNodes, and there are
21281 enough of them listed as Guard so that we don't need to consider
21282 the non-guard entries, prefer the ones listed with the Guard flag.
21283 - Check for and recover from inconsistency in the microdescriptor
21284 cache. This will make it harder for us to accidentally free a
21285 microdescriptor without removing it from the appropriate data
21286 structures. Fixes issue 3135; issue noted by "wanoskarnet".
21287 - Log SSL state transitions at log level DEBUG, log domain
21288 HANDSHAKE. This can be useful for debugging censorship events.
21289 Implements ticket 3264.
21290 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
21291 implements ticket 3439.
21293 o Minor bugfixes (on 0.2.3.1-alpha):
21294 - Do not free all general-purpose regular descriptors just
21295 because microdescriptor use is enabled. Fixes bug 3113.
21296 - Correctly link libevent_openssl when --enable-static-libevent
21297 is passed to configure. Fixes bug 3118.
21298 - Bridges should not complain during their heartbeat log messages that
21299 they are unlisted in the consensus: that's more or less the point
21300 of being a bridge. Fixes bug 3183.
21301 - Report a SIGNAL event to controllers when acting on a delayed
21302 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
21303 event to the controller if we acted on a SIGNAL NEWNYM command
21304 immediately, and otherwise not report a SIGNAL event for the
21305 command at all. Fixes bug 3349.
21306 - Fix a crash when handling the SIGNAL controller command or
21307 reporting ERR-level status events with bufferevents enabled. Found
21308 by Robert Ransom. Fixes bug 3367.
21309 - Always ship the tor-fw-helper manpage in our release tarballs.
21310 Fixes bug 3389. Reported by Stephen Walker.
21311 - Fix a class of double-mark-for-close bugs when bufferevents
21312 are enabled. Fixes bug 3403.
21313 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
21314 - Add SIGNAL to the list returned by the 'GETINFO events/names'
21315 control-port command. Fixes part of bug 3465.
21316 - Prevent using negative indices during unit test runs when read_all()
21317 fails. Spotted by coverity.
21318 - Fix a rare memory leak when checking the nodelist without it being
21319 present. Found by coverity.
21320 - Only try to download a microdescriptor-flavored consensus from
21321 a directory cache that provides them.
21323 o Minor bugfixes (on 0.2.2.x and earlier):
21324 - Assert that hidden-service-related operations are not performed
21325 using single-hop circuits. Previously, Tor would assert that
21326 client-side streams are not attached to single-hop circuits,
21327 but not that other sensitive operations on the client and service
21328 side are not performed using single-hop circuits. Fixes bug 3332;
21330 - Don't publish a new relay descriptor when we reload our onion key,
21331 unless the onion key has actually changed. Fixes bug 3263 and
21332 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
21333 - Allow GETINFO fingerprint to return a fingerprint even when
21334 we have not yet built a router descriptor. Fixes bug 3577;
21335 bugfix on 0.2.0.1-alpha.
21336 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
21337 on 0.2.2.4-alpha; fixes bug 3427.
21339 o Code simplification and refactoring:
21340 - Use tor_sscanf() in place of scanf() in more places through the
21341 code. This makes us a little more locale-independent, and
21342 should help shut up code-analysis tools that can't tell
21343 a safe sscanf string from a dangerous one.
21344 - Use tt_assert(), not tor_assert(), for checking for test failures.
21345 This makes the unit tests more able to go on in the event that
21347 - Split connection_about_to_close() into separate functions for each
21351 - On Windows, we now define the _WIN32_WINNT macros only if they
21352 are not already defined. This lets the person building Tor decide,
21353 if they want, to require a later version of Windows.
21356 Changes in version 0.2.2.30-rc - 2011-07-07
21357 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
21358 series. It fixes a few smaller bugs, but generally appears stable.
21359 Please test it and let us know whether it is!
21362 - Send a SUCCEEDED stream event to the controller when a reverse
21363 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21364 discovered by katmagic.
21365 - Always NUL-terminate the sun_path field of a sockaddr_un before
21366 passing it to the kernel. (Not a security issue: kernels are
21367 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21368 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21369 - Don't stack-allocate the list of supplementary GIDs when we're
21370 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21371 could take up to 256K, which is way too much stack. Found by
21372 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21373 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
21374 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
21375 fixes part of bug 3465.
21376 - Fix a memory leak when receiving a descriptor for a hidden
21377 service we didn't ask for. Found by Coverity; CID #30. Bugfix
21381 - Update to the July 1 2011 Maxmind GeoLite Country database.
21384 Changes in version 0.2.2.29-beta - 2011-06-20
21385 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
21386 have bridge lines in their torrc but don't want to use them; gets
21387 us closer to having the control socket feature working on Debian;
21388 and fixes a variety of smaller bugs.
21391 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
21392 When we changed the default behavior to "use bridges if any
21393 are listed in the torrc", we surprised users who had bridges
21394 in their torrc files but who didn't actually want to use them.
21395 Partial resolution for bug 3354.
21398 - Don't attach new streams to old rendezvous circuits after SIGNAL
21399 NEWNYM. Previously, we would keep using an existing rendezvous
21400 circuit if it remained open (i.e. if it were kept open by a
21401 long-lived stream, or if a new stream were attached to it before
21402 Tor could notice that it was old and no longer in use). Bugfix on
21403 0.1.1.15-rc; fixes bug 3375.
21406 - Fix a bug when using ControlSocketsGroupWritable with User. The
21407 directory's group would be checked against the current group, not
21408 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
21409 bugfix on 0.2.2.26-beta.
21410 - Make connection_printf_to_buf()'s behavior sane. Its callers
21411 expect it to emit a CRLF iff the format string ends with CRLF;
21412 it actually emitted a CRLF iff (a) the format string ended with
21413 CRLF or (b) the resulting string was over 1023 characters long or
21414 (c) the format string did not end with CRLF *and* the resulting
21415 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21416 fixes part of bug 3407.
21417 - Make send_control_event_impl()'s behavior sane. Its callers
21418 expect it to always emit a CRLF at the end of the string; it
21419 might have emitted extra control characters as well. Bugfix on
21420 0.1.1.9-alpha; fixes another part of bug 3407.
21421 - Make crypto_rand_int() check the value of its input correctly.
21422 Previously, it accepted values up to UINT_MAX, but could return a
21423 negative number if given a value above INT_MAX+1. Found by George
21424 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21425 - Avoid a segfault when reading a malformed circuit build state
21426 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21428 - When asked about a DNS record type we don't support via a
21429 client DNSPort, reply with NOTIMPL rather than an empty
21430 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21431 - Fix a rare memory leak during stats writing. Found by coverity.
21434 - Update to the June 1 2011 Maxmind GeoLite Country database.
21436 o Code simplifications and refactoring:
21437 - Remove some dead code as indicated by coverity.
21438 - Remove a few dead assignments during router parsing. Found by
21440 - Add some forgotten return value checks during unit tests. Found
21442 - Don't use 1-bit wide signed bit fields. Found by coverity.
21445 Changes in version 0.2.2.28-beta - 2011-06-04
21446 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21447 fixed a big bug in whether relays stay in the consensus consistently,
21448 we moved closer to handling bridges and hidden services correctly,
21449 and we started the process of better handling the dreaded "my Vidalia
21450 died, and now my Tor demands a password when I try to reconnect to it"
21454 - Don't decide to make a new descriptor when receiving a HUP signal.
21455 This bug has caused a lot of 0.2.2.x relays to disappear from the
21456 consensus periodically. Fixes the most common case of triggering
21457 bug 1810; bugfix on 0.2.2.7-alpha.
21458 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21459 - Don't try to build descriptors if "ORPort auto" is set and we
21460 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21462 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21463 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21464 - Apply circuit timeouts to opened hidden-service-related circuits
21465 based on the correct start time. Previously, we would apply the
21466 circuit build timeout based on time since the circuit's creation;
21467 it was supposed to be applied based on time since the circuit
21468 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21469 - Use the same circuit timeout for client-side introduction
21470 circuits as for other four-hop circuits, rather than the timeout
21471 for single-hop directory-fetch circuits; the shorter timeout may
21472 have been appropriate with the static circuit build timeout in
21473 0.2.1.x and earlier, but caused many hidden service access attempts
21474 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21475 on 0.2.2.2-alpha; fixes another part of bug 1297.
21476 - In ticket 2511 we fixed a case where you could use an unconfigured
21477 bridge if you had configured it as a bridge the last time you ran
21478 Tor. Now fix another edge case: if you had configured it as a bridge
21479 but then switched to a different bridge via the controller, you
21480 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21484 - Add an __OwningControllerProcess configuration option and a
21485 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21486 that when it exits, Tor will shut down. Implements feature 3049.
21487 - If "UseBridges 1" is set and no bridges are configured, Tor will
21488 now refuse to build any circuits until some bridges are set.
21489 If "UseBridges auto" is set, Tor will use bridges if they are
21490 configured and we are not running as a server, but otherwise will
21491 make circuits as usual. The new default is "auto". Patch by anonym,
21492 so the Tails LiveCD can stop automatically revealing you as a Tor
21496 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21497 - Remove a trailing asterisk from "exit-policy/default" in the
21498 output of the control port command "GETINFO info/names". Bugfix
21500 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21502 - Warn when the user configures two HiddenServiceDir lines that point
21503 to the same directory. Bugfix on 0.0.6 (the version introducing
21504 HiddenServiceDir); fixes bug 3289.
21505 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21506 part of bug 2748; bugfix on 0.2.0.10-alpha.
21507 - Log malformed requests for rendezvous descriptors as protocol
21508 warnings, not warnings. Also, use a more informative log message
21509 in case someone sees it at log level warning without prior
21510 info-level messages. Fixes the other part of bug 2748; bugfix
21512 - Clear the table recording the time of the last request for each
21513 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21514 Previously, we would clear our HS descriptor cache on SIGNAL
21515 NEWNYM, but if we had previously retrieved a descriptor (or tried
21516 to) from every directory responsible for it, we would refuse to
21517 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21519 - Fix a log message that said "bits" while displaying a value in
21520 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21522 - When checking for 1024-bit keys, check for 1024 bits, not 128
21523 bytes. This allows Tor to correctly discard keys of length 1017
21524 through 1023. Bugfix on 0.0.9pre5.
21527 - Relays now log the reason for publishing a new relay descriptor,
21528 so we have a better chance of hunting down instances of bug 1810.
21529 Resolves ticket 3252.
21530 - Revise most log messages that refer to nodes by nickname to
21531 instead use the "$key=nickname at address" format. This should be
21532 more useful, especially since nicknames are less and less likely
21533 to be unique. Resolves ticket 3045.
21534 - Log (at info level) when purging pieces of hidden-service-client
21535 state because of SIGNAL NEWNYM.
21538 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21539 anything since 0.2.1.16-rc.
21542 Changes in version 0.2.2.27-beta - 2011-05-18
21543 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21544 release, and also adds a few more general bugfixes.
21547 - Fix a crash bug when changing bridges in a running Tor process.
21548 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21549 - When the controller configures a new bridge, don't wait 10 to 60
21550 seconds before trying to fetch its descriptor. Bugfix on
21551 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21554 - Require that onion keys have exponent 65537 in microdescriptors too.
21555 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21556 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21557 Changed the limit to 512 characters by removing base64 newlines.
21558 Fixes bug 2752. Fix by Michael Yakubovich.
21559 - When a client starts or stops using bridges, never use a circuit
21560 that was built before the configuration change. This behavior could
21561 put at risk a user who uses bridges to ensure that her traffic
21562 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21566 Changes in version 0.2.2.26-beta - 2011-05-17
21567 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21568 also introduces a new "socksport auto" approach that should make it
21569 easier to run multiple Tors on the same system, and does a lot of
21570 cleanup to get us closer to a release candidate.
21572 o Security/privacy fixes:
21573 - Replace all potentially sensitive memory comparison operations
21574 with versions whose runtime does not depend on the data being
21575 compared. This will help resist a class of attacks where an
21576 adversary can use variations in timing information to learn
21577 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21578 implementation by Robert Ransom based partially on code by DJB.)
21579 - When receiving a hidden service descriptor, check that it is for
21580 the hidden service we wanted. Previously, Tor would store any
21581 hidden service descriptors that a directory gave it, whether it
21582 wanted them or not. This wouldn't have let an attacker impersonate
21583 a hidden service, but it did let directories pre-seed a client
21584 with descriptors that it didn't want. Bugfix on 0.0.6.
21585 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21586 DNS cache entries, and virtual address mappings: that's what
21587 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21590 - The options SocksPort, ControlPort, and so on now all accept a
21591 value "auto" that opens a socket on an OS-selected port. A
21592 new ControlPortWriteToFile option tells Tor to write its
21593 actual control port or ports to a chosen file. If the option
21594 ControlPortFileGroupReadable is set, the file is created as
21595 group-readable. Now users can run two Tor clients on the same
21596 system without needing to manually mess with parameters. Resolves
21597 part of ticket 3076.
21598 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21599 help busy exit nodes avoid running out of useable ports just
21600 because all the ports have been used in the near past. Resolves
21604 - New "GETINFO net/listeners/(type)" controller command to return
21605 a list of addresses and ports that are bound for listeners for a
21606 given connection type. This is useful when the user has configured
21607 "SocksPort auto" and the controller needs to know which port got
21608 chosen. Resolves another part of ticket 3076.
21609 - Add a new ControlSocketsGroupWritable configuration option: when
21610 it is turned on, ControlSockets are group-writeable by the default
21611 group of the current user. Patch by Jérémy Bobbio; implements
21613 - Tor now refuses to create a ControlSocket in a directory that is
21614 world-readable (or group-readable if ControlSocketsGroupWritable
21615 is 0). This is necessary because some operating systems do not
21616 enforce permissions on an AF_UNIX sockets. Permissions on the
21617 directory holding the socket, however, seems to work everywhere.
21618 - Rate-limit a warning about failures to download v2 networkstatus
21619 documents. Resolves part of bug 1352.
21620 - Backport code from 0.2.3.x that allows directory authorities to
21621 clean their microdescriptor caches. Needed to resolve bug 2230.
21622 - When an HTTPS proxy reports "403 Forbidden", we now explain
21623 what it means rather than calling it an unexpected status code.
21624 Closes bug 2503. Patch from Michael Yakubovich.
21625 - Update to the May 1 2011 Maxmind GeoLite Country database.
21628 - Authorities now clean their microdesc cache periodically and when
21629 reading from disk initially, not only when adding new descriptors.
21630 This prevents a bug where we could lose microdescriptors. Bugfix
21631 on 0.2.2.6-alpha. Fixes bug 2230.
21632 - Do not crash when our configuration file becomes unreadable, for
21633 example due to a permissions change, between when we start up
21634 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21636 - Avoid a bug that would keep us from replacing a microdescriptor
21637 cache on Windows. (We would try to replace the file while still
21638 holding it open. That's fine on Unix, but Windows doesn't let us
21639 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
21640 - Add missing explanations for the authority-related torrc options
21641 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
21642 man page. Resolves issue 2379.
21643 - As an authority, do not upload our own vote or signature set to
21644 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
21645 it would get flagged as a duplicate. Resolves bug 3026.
21646 - Accept hidden service descriptors if we think we might be a hidden
21647 service directory, regardless of what our consensus says. This
21648 helps robustness, since clients and hidden services can sometimes
21649 have a more up-to-date view of the network consensus than we do,
21650 and if they think that the directory authorities list us a HSDir,
21651 we might actually be one. Related to bug 2732; bugfix on
21653 - When a controller changes TrackHostExits, remove mappings for
21654 hosts that should no longer have their exits tracked. Bugfix on
21656 - When a controller changes VirtualAddrNetwork, remove any mappings
21657 for hosts that were automapped to the old network. Bugfix on
21659 - When a controller changes one of the AutomapHosts* options, remove
21660 any mappings for hosts that should no longer be automapped. Bugfix
21662 - Do not reset the bridge descriptor download status every time we
21663 re-parse our configuration or get a configuration change. Fixes
21664 bug 3019; bugfix on 0.2.0.3-alpha.
21666 o Minor bugfixes (code cleanup):
21667 - When loading the microdesc journal, remember its current size.
21668 In 0.2.2, this helps prevent the microdesc journal from growing
21669 without limit on authorities (who are the only ones to use it in
21670 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21671 Fix posted by "cypherpunks."
21672 - The microdesc journal is supposed to get rebuilt only if it is
21673 at least _half_ the length of the store, not _twice_ the length
21674 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21675 - Fix a potential null-pointer dereference while computing a
21676 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21678 - Avoid a possible null-pointer dereference when rebuilding the mdesc
21679 cache without actually having any descriptors to cache. Bugfix on
21680 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
21681 - If we fail to compute the identity digest of a v3 legacy keypair,
21682 warn, and don't use a buffer-full of junk instead. Bugfix on
21683 0.2.1.1-alpha; fixes bug 3106.
21684 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21685 where if the function had ever in the future been used to check
21686 for the presence of a too-large number, it would have given an
21687 incorrect result. (Fortunately, we only used it for 16-bit
21688 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21689 - Require that introduction point keys and onion handshake keys
21690 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21693 o Removed features:
21694 - Caches no longer download and serve v2 networkstatus documents
21695 unless FetchV2Networkstatus flag is set: these documents haven't
21696 haven't been used by clients or relays since 0.2.0.x. Resolves
21700 Changes in version 0.2.3.1-alpha - 2011-05-05
21701 Tor 0.2.3.1-alpha adds some new experimental features, including support
21702 for an improved network IO backend, IOCP networking on Windows,
21703 microdescriptor caching, "fast-start" support for streams, and automatic
21704 home router configuration. There are also numerous internal improvements
21705 to try to make the code easier for developers to work with.
21707 This is the first alpha release in a new series, so expect there to be
21708 bugs. Users who would rather test out a more stable branch should
21709 stay with 0.2.2.x for now.
21712 - Tor can now optionally build with the "bufferevents" buffered IO
21713 backend provided by Libevent 2. To use this feature, make sure you
21714 have the latest possible version of Libevent, and pass the
21715 --enable-bufferevents flag to configure when building Tor from
21716 source. This feature will make our networking code more flexible,
21717 let us stack layers on each other, and let us use more efficient
21718 zero-copy transports where available.
21719 - As an experimental feature, Tor can use IOCP for networking on Windows.
21720 Once this code is tuned and optimized, it promises much better
21721 performance than the select-based backend we've used in the past. To
21722 try this feature, you must build Tor with Libevent 2, configure Tor
21723 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
21724 your torrc. There are known bugs here: only try this if you can help
21725 debug it as it breaks.
21726 - The EntryNodes option can now include country codes like {de} or IP
21727 addresses or network masks. Previously we had disallowed these options
21728 because we didn't have an efficient way to keep the list up to
21729 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
21730 - Exit nodes now accept and queue data on not-yet-connected streams.
21731 Previously, the client wasn't allowed to send data until the stream was
21732 connected, which slowed down all connections. This change will enable
21733 clients to perform a "fast-start" on streams and send data without
21734 having to wait for a confirmation that the stream has opened. (Patch
21735 from Ian Goldberg; implements the server side of Proposal 174.)
21736 - Tor now has initial support for automatic port mapping on the many
21737 home routers that support NAT-PMP or UPnP. (Not yet supported on
21738 Windows). To build the support code, you'll need to have libnatpnp
21739 library and/or the libminiupnpc library, and you'll need to enable the
21740 feature specifically by passing "--enable-upnp" and/or
21741 "--enable-natpnp" to configure. To turn it on, use the new
21742 PortForwarding option.
21743 - Caches now download, cache, and serve multiple "flavors" of the
21744 consensus, including a flavor that describes microdescriptors.
21745 - Caches now download, cache, and serve microdescriptors -- small
21746 summaries of router descriptors that are authenticated by all of the
21747 directory authorities. Once enough caches are running this code,
21748 clients will be able to save significant amounts of directory bandwidth
21749 by downloading microdescriptors instead of router descriptors.
21752 - Make logging resolution configurable with a new LogTimeGranularity
21753 option, and change the default from 1 millisecond to 1 second.
21754 Implements enhancement 1668.
21755 - We log which torrc file we're using on startup. Implements ticket
21757 - Ordinarily, Tor does not count traffic from private addresses (like
21758 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
21759 There is now a new option, CountPrivateBandwidth, to disable this
21760 behavior. Patch from Daniel Cagara.
21761 - New --enable-static-tor configure option for building Tor as
21762 statically as possible. Idea, general hackery and thoughts from
21763 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
21765 - If you set the NumCPUs option to 0, Tor will now try to detect how
21766 many CPUs you have. This is the new default behavior.
21767 - Turn on directory request statistics by default and include them in
21768 extra-info descriptors. Don't break if we have no GeoIP database.
21769 - Relays that set "ConnDirectionStatistics 1" write statistics on the
21770 bidirectional use of connections to disk every 24 hours.
21771 - Add a GeoIP file digest to the extra-info descriptor. Implements
21773 - The NodeFamily option -- which let you declare that you want to
21774 consider nodes to be part of a family whether they list themselves
21775 that way or not -- now allows IP address ranges and country codes.
21776 - Add a new 'Heartbeat' log message type to periodically log a message
21777 describing Tor's status at level Notice. This feature is meant for
21778 operators who log at notice, and want to make sure that their Tor
21779 server is still working. Implementation by George Kadianakis.
21781 o Minor bugfixes (on 0.2.2.25-alpha):
21782 - When loading the microdesc journal, remember its current size.
21783 In 0.2.2, this helps prevent the microdesc journal from growing
21784 without limit on authorities (who are the only ones to use it in
21785 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21786 Fix posted by "cypherpunks."
21787 - The microdesc journal is supposed to get rebuilt only if it is
21788 at least _half_ the length of the store, not _twice_ the length
21789 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21790 - If as an authority we fail to compute the identity digest of a v3
21791 legacy keypair, warn, and don't use a buffer-full of junk instead.
21792 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
21793 - Authorities now clean their microdesc cache periodically and when
21794 reading from disk initially, not only when adding new descriptors.
21795 This prevents a bug where we could lose microdescriptors. Bugfix
21798 o Minor features (controller):
21799 - Add a new SIGNAL event to the controller interface so that
21800 controllers can be notified when Tor handles a signal. Resolves
21801 issue 1955. Patch by John Brooks.
21802 - Add a new GETINFO option to get total bytes read and written. Patch
21803 from pipe, revised by atagar. Resolves ticket 2345.
21804 - Implement some GETINFO controller fields to provide information about
21805 the Tor process's pid, euid, username, and resource limits.
21808 - Our build system requires automake 1.6 or later to create the
21809 Makefile.in files. Previously, you could have used 1.4.
21810 This only affects developers and people building Tor from git;
21811 people who build Tor from the source distribution without changing
21812 the Makefile.am files should be fine.
21813 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
21814 so on. This is more robust against some of the failure modes
21815 associated with running the autotools pieces on their own.
21817 o Minor packaging issues:
21818 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
21819 already created. Patch from Andreas Stieger. Fixes bug 2573.
21821 o Code simplifications and refactoring:
21822 - A major revision to our internal node-selecting and listing logic.
21823 Tor already had at least two major ways to look at the question of
21824 "which Tor servers do we know about": a list of router descriptors,
21825 and a list of entries in the current consensus. With
21826 microdescriptors, we're adding a third. Having so many systems
21827 without an abstraction layer over them was hurting the codebase.
21828 Now, we have a new "node_t" abstraction that presents a consistent
21829 interface to a client's view of a Tor node, and holds (nearly) all
21830 of the mutable state formerly in routerinfo_t and routerstatus_t.
21831 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
21832 no longer link against Libevent: they never used it, but
21833 our library structure used to force them to link it.
21835 o Removed features:
21836 - Remove some old code to work around even older versions of Tor that
21837 used forked processes to handle DNS requests. Such versions of Tor
21838 are no longer in use as servers.
21840 o Documentation fixes:
21841 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
21842 - Add missing documentation for the authority-related torrc options
21843 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
21847 Changes in version 0.2.2.25-alpha - 2011-04-29
21848 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
21849 robust, routers no longer overreport their bandwidth, Win7 should crash
21850 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
21851 now prevents hidden service-related activity from being linkable. It
21852 provides more information to Vidalia so you can see if your bridge is
21853 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
21854 StrictNodes configuration options to make them more reliable, more
21855 understandable, and more regularly applied. If you use those options,
21856 please see the revised documentation for them in the manual page.
21859 - Relays were publishing grossly inflated bandwidth values because
21860 they were writing their state files wrong--now they write the
21861 correct value. Also, resume reading bandwidth history from the
21862 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
21863 - Improve hidden service robustness: When we find that we have
21864 extended a hidden service's introduction circuit to a relay not
21865 listed as an introduction point in the HS descriptor we currently
21866 have, retry with an introduction point from the current
21867 descriptor. Previously we would just give up. Fixes bugs 1024 and
21868 1930; bugfix on 0.2.0.10-alpha.
21869 - Clients now stop trying to use an exit node associated with a given
21870 destination by TrackHostExits if they fail to reach that exit node.
21871 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
21872 - Fix crash bug on platforms where gmtime and localtime can return
21873 NULL. Windows 7 users were running into this one. Fixes part of bug
21874 2077. Bugfix on all versions of Tor. Found by boboper.
21876 o Security and stability fixes:
21877 - Don't double-free a parsable, but invalid, microdescriptor, even if
21878 it is followed in the blob we're parsing by an unparsable
21879 microdescriptor. Fixes an issue reported in a comment on bug 2954.
21880 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
21881 - If the Nickname configuration option isn't given, Tor would pick a
21882 nickname based on the local hostname as the nickname for a relay.
21883 Because nicknames are not very important in today's Tor and the
21884 "Unnamed" nickname has been implemented, this is now problematic
21885 behavior: It leaks information about the hostname without being
21886 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
21887 introduced the Unnamed nickname. Reported by tagnaq.
21888 - Fix an uncommon assertion failure when running with DNSPort under
21889 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21890 - Avoid linkability based on cached hidden service descriptors: forget
21891 all hidden service descriptors cached as a client when processing a
21892 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21895 - Export GeoIP information on bridge usage to controllers even if we
21896 have not yet been running for 24 hours. Now Vidalia bridge operators
21897 can get more accurate and immediate feedback about their
21898 contributions to the network.
21900 o Major features and bugfixes (node selection):
21901 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
21902 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
21903 options. Previously, we had been ambiguous in describing what
21904 counted as an "exit" node, and what operations exactly "StrictNodes
21905 0" would permit. This created confusion when people saw nodes built
21906 through unexpected circuits, and made it hard to tell real bugs from
21907 surprises. Now the intended behavior is:
21908 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
21909 a node that delivers user traffic outside the Tor network.
21910 . "Entry", in the context of EntryNodes, means a node used as the
21911 first hop of a multihop circuit. It doesn't include direct
21912 connections to directory servers.
21913 . "ExcludeNodes" applies to all nodes.
21914 . "StrictNodes" changes the behavior of ExcludeNodes only. When
21915 StrictNodes is set, Tor should avoid all nodes listed in
21916 ExcludeNodes, even when it will make user requests fail. When
21917 StrictNodes is *not* set, then Tor should follow ExcludeNodes
21918 whenever it can, except when it must use an excluded node to
21919 perform self-tests, connect to a hidden service, provide a
21920 hidden service, fulfill a .exit request, upload directory
21921 information, or fetch directory information.
21922 Collectively, the changes to implement the behavior fix bug 1090.
21923 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
21924 a node is listed in both, it's treated as excluded.
21925 - ExcludeNodes now applies to directory nodes -- as a preference if
21926 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
21927 Don't exclude all the directory authorities and set StrictNodes to 1
21928 unless you really want your Tor to break.
21929 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
21930 - ExcludeExitNodes now overrides .exit requests.
21931 - We don't use bridges listed in ExcludeNodes.
21932 - When StrictNodes is 1:
21933 . We now apply ExcludeNodes to hidden service introduction points
21934 and to rendezvous points selected by hidden service users. This
21935 can make your hidden service less reliable: use it with caution!
21936 . If we have used ExcludeNodes on ourself, do not try relay
21937 reachability self-tests.
21938 . If we have excluded all the directory authorities, we will not
21939 even try to upload our descriptor if we're a relay.
21940 . Do not honor .exit requests to an excluded node.
21941 - Remove a misfeature that caused us to ignore the Fast/Stable flags
21942 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
21943 - When the set of permitted nodes changes, we now remove any mappings
21944 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
21946 - We never cannibalize a circuit that had excluded nodes on it, even
21947 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
21948 - Revert a change where we would be laxer about attaching streams to
21949 circuits than when building the circuits. This was meant to prevent
21950 a set of bugs where streams were never attachable, but our improved
21951 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
21952 - Keep track of how many times we launch a new circuit to handle a
21953 given stream. Too many launches could indicate an inconsistency
21954 between our "launch a circuit to handle this stream" logic and our
21955 "attach this stream to one of the available circuits" logic.
21956 - Improve log messages related to excluded nodes.
21959 - Fix a spurious warning when moving from a short month to a long
21960 month on relays with month-based BandwidthAccounting. Bugfix on
21961 0.2.2.17-alpha; fixes bug 3020.
21962 - When a client finds that an origin circuit has run out of 16-bit
21963 stream IDs, we now mark it as unusable for new streams. Previously,
21964 we would try to close the entire circuit. Bugfix on 0.0.6.
21965 - Add a forgotten cast that caused a compile warning on OS X 10.6.
21966 Bugfix on 0.2.2.24-alpha.
21967 - Be more careful about reporting the correct error from a failed
21968 connect() system call. Under some circumstances, it was possible to
21969 look at an incorrect value for errno when sending the end reason.
21970 Bugfix on 0.1.0.1-rc.
21971 - Correctly handle an "impossible" overflow cases in connection byte
21972 counting, where we write or read more than 4GB on an edge connection
21973 in a single second. Bugfix on 0.1.2.8-beta.
21974 - Correct the warning displayed when a rendezvous descriptor exceeds
21975 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21977 - Clients and hidden services now use HSDir-flagged relays for hidden
21978 service descriptor downloads and uploads even if the relays have no
21979 DirPort set and the client has disabled TunnelDirConns. This will
21980 eventually allow us to give the HSDir flag to relays with no
21981 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
21982 - Downgrade "no current certificates known for authority" message from
21983 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
21984 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
21985 2917. Bugfix on 0.1.1.1-alpha.
21986 - Only limit the lengths of single HS descriptors, even when multiple
21987 HS descriptors are published to an HSDir relay in a single POST
21988 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
21989 - Write the current time into the LastWritten line in our state file,
21990 rather than the time from the previous write attempt. Also, stop
21991 trying to use a time of -1 in our log statements. Fixes bug 3039;
21992 bugfix on 0.2.2.14-alpha.
21993 - Be more consistent in our treatment of file system paths. "~" should
21994 get expanded to the user's home directory in the Log config option.
21995 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
21996 feature for the -f and --DataDirectory options.
21999 - Make sure every relay writes a state file at least every 12 hours.
22000 Previously, a relay could go for weeks without writing its state
22001 file, and on a crash could lose its bandwidth history, capacity
22002 estimates, client country statistics, and so on. Addresses bug 3012.
22003 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22004 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22005 clients are already deprecated because of security bugs.
22006 - Don't allow v0 hidden service authorities to act as clients.
22007 Required by fix for bug 3000.
22008 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22009 by fix for bug 3000.
22010 - Ensure that no empty [dirreq-](read|write)-history lines are added
22011 to an extrainfo document. Implements ticket 2497.
22013 o Code simplification and refactoring:
22014 - Remove workaround code to handle directory responses from servers
22015 that had bug 539 (they would send HTTP status 503 responses _and_
22016 send a body too). Since only server versions before
22017 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22018 keep the workaround in place.
22019 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22020 handling calculations where we have a known amount of clock skew and
22021 an allowed amount of unknown skew. But we only used it in three
22022 places, and we never adjusted the known/unknown skew values. This is
22023 still something we might want to do someday, but if we do, we'll
22024 want to do it differently.
22025 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22026 None of the cases where we did this before were wrong, but by making
22027 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22028 - Use GetTempDir to find the proper temporary directory location on
22029 Windows when generating temporary files for the unit tests. Patch by
22033 Changes in version 0.2.2.24-alpha - 2011-04-08
22034 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
22035 prevented Tor clients from effectively using "multihomed" bridges,
22036 that is, bridges that listen on multiple ports or IP addresses so users
22037 can continue to use some of their addresses even if others get blocked.
22040 - Fix a bug where bridge users who configure the non-canonical
22041 address of a bridge automatically switch to its canonical
22042 address. If a bridge listens at more than one address, it should be
22043 able to advertise those addresses independently and any non-blocked
22044 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
22046 - If you configured Tor to use bridge A, and then quit and
22047 configured Tor to use bridge B instead, it would happily continue
22048 to use bridge A if it's still reachable. While this behavior is
22049 a feature if your goal is connectivity, in some scenarios it's a
22050 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22051 - Directory authorities now use data collected from their own
22052 uptime observations when choosing whether to assign the HSDir flag
22053 to relays, instead of trusting the uptime value the relay reports in
22054 its descriptor. This change helps prevent an attack where a small
22055 set of nodes with frequently-changing identity keys can blackhole
22056 a hidden service. (Only authorities need upgrade; others will be
22057 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22060 - When we restart our relay, we might get a successful connection
22061 from the outside before we've started our reachability tests,
22062 triggering a warning: "ORPort found reachable, but I have no
22063 routerinfo yet. Failing to inform controller of success." This
22064 bug was harmless unless Tor is running under a controller
22065 like Vidalia, in which case the controller would never get a
22066 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22068 - Make directory authorities more accurate at recording when
22069 relays that have failed several reachability tests became
22070 unreachable, so we can provide more accuracy at assigning Stable,
22071 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22072 - Fix an issue that prevented static linking of libevent on
22073 some platforms (notably Linux). Fixes bug 2698; bugfix on
22074 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
22075 the --with-static-libevent configure option).
22076 - We now ask the other side of a stream (the client or the exit)
22077 for more data on that stream when the amount of queued data on
22078 that stream dips low enough. Previously, we wouldn't ask the
22079 other side for more data until either it sent us more data (which
22080 it wasn't supposed to do if it had exhausted its window!) or we
22081 had completely flushed all our queued data. This flow control fix
22082 should improve throughput. Fixes bug 2756; bugfix on the earliest
22083 released versions of Tor (svn commit r152).
22084 - Avoid a double-mark-for-free warning when failing to attach a
22085 transparent proxy connection. (We thought we had fixed this in
22086 0.2.2.23-alpha, but it turns out our fix was checking the wrong
22087 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
22088 bug) and 0.2.2.23-alpha (the incorrect fix).
22089 - When warning about missing zlib development packages during compile,
22090 give the correct package names. Bugfix on 0.2.0.1-alpha.
22093 - Directory authorities now log the source of a rejected POSTed v3
22094 networkstatus vote.
22095 - Make compilation with clang possible when using
22096 --enable-gcc-warnings by removing two warning options that clang
22097 hasn't implemented yet and by fixing a few warnings. Implements
22099 - When expiring circuits, use microsecond timers rather than
22100 one-second timers. This can avoid an unpleasant situation where a
22101 circuit is launched near the end of one second and expired right
22102 near the beginning of the next, and prevent fluctuations in circuit
22104 - Use computed circuit-build timeouts to decide when to launch
22105 parallel introduction circuits for hidden services. (Previously,
22106 we would retry after 15 seconds.)
22107 - Update to the April 1 2011 Maxmind GeoLite Country database.
22110 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22111 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22113 o Documentation changes:
22114 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22115 - Resolve all doxygen warnings except those for missing documentation.
22117 - Add doxygen documentation for more functions, fields, and types.
22120 Changes in version 0.2.2.23-alpha - 2011-03-08
22121 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
22122 they restart they don't lose their bandwidth capacity estimate. This
22123 release also fixes a diverse set of user-facing bugs, ranging from
22124 relays overrunning their rate limiting to clients falsely warning about
22125 clock skew to bridge descriptor leaks by our bridge directory authority.
22128 - Stop sending a CLOCK_SKEW controller status event whenever
22129 we fetch directory information from a relay that has a wrong clock.
22130 Instead, only inform the controller when it's a trusted authority
22131 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22132 the rest of bug 1074.
22133 - Fix an assert in parsing router descriptors containing IPv6
22134 addresses. This one took down the directory authorities when
22135 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22136 - Make the bridge directory authority refuse to answer directory
22137 requests for "all" descriptors. It used to include bridge
22138 descriptors in its answer, which was a major information leak.
22139 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22140 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22141 Tor would ignore their RelayBandwidthBurst setting,
22142 potentially using more bandwidth than expected. Bugfix on
22143 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22144 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22145 hidserv" in her torrc. The 'hidserv' argument never controlled
22146 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22149 - Relays now save observed peak bandwidth throughput rates to their
22150 state file (along with total usage, which was already saved)
22151 so that they can determine their correct estimated bandwidth on
22152 restart. Resolves bug 1863, where Tor relays would reset their
22153 estimated bandwidth to 0 after restarting.
22154 - Directory authorities now take changes in router IP address and
22155 ORPort into account when determining router stability. Previously,
22156 if a router changed its IP or ORPort, the authorities would not
22157 treat it as having any downtime for the purposes of stability
22158 calculation, whereas clients would experience downtime since the
22159 change could take a while to propagate to them. Resolves issue 1035.
22160 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22161 Prevention (DEP) by default on Windows to make it harder for
22162 attackers to exploit vulnerabilities. Patch from John Brooks.
22164 o Minor bugfixes (on 0.2.1.x and earlier):
22165 - Fix a rare crash bug that could occur when a client was configured
22166 with a large number of bridges. Fixes bug 2629; bugfix on
22167 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22168 - Avoid a double mark-for-free warning when failing to attach a
22169 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22171 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22172 found by "cypherpunks". This bug was introduced before the first
22173 Tor release, in svn commit r110.
22174 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
22175 don't mention them in the manpage. Fixes bug 2450; issue
22176 spotted by keb and G-Lo.
22177 - Fix a bug in bandwidth history state parsing that could have been
22178 triggered if a future version of Tor ever changed the timing
22179 granularity at which bandwidth history is measured. Bugfix on
22180 Tor 0.1.1.11-alpha.
22181 - When a relay decides that its DNS is too broken for it to serve
22182 as an exit server, it advertised itself as a non-exit, but
22183 continued to act as an exit. This could create accidental
22184 partitioning opportunities for users. Instead, if a relay is
22185 going to advertise reject *:* as its exit policy, it should
22186 really act with exit policy "reject *:*". Fixes bug 2366.
22187 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22188 - In the special case where you configure a public exit relay as your
22189 bridge, Tor would be willing to use that exit relay as the last
22190 hop in your circuit as well. Now we fail that circuit instead.
22191 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22192 - Fix a bug with our locking implementation on Windows that couldn't
22193 correctly detect when a file was already locked. Fixes bug 2504,
22194 bugfix on 0.2.1.6-alpha.
22195 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22196 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22198 - Set target port in get_interface_address6() correctly. Bugfix
22199 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22200 - Directory authorities are now more robust to hops back in time
22201 when calculating router stability. Previously, if a run of uptime
22202 or downtime appeared to be negative, the calculation could give
22203 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22205 - Fix an assert that got triggered when using the TestingTorNetwork
22206 configuration option and then issuing a GETINFO config-text control
22207 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22209 o Minor bugfixes (on 0.2.2.x):
22210 - Clients should not weight BadExit nodes as Exits in their node
22211 selection. Similarly, directory authorities should not count BadExit
22212 bandwidth as Exit bandwidth when computing bandwidth-weights.
22213 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
22214 - Correctly clear our dir_read/dir_write history when there is an
22215 error parsing any bw history value from the state file. Bugfix on
22216 Tor 0.2.2.15-alpha.
22217 - Resolve a bug in verifying signatures of directory objects
22218 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
22219 Fixes bug 2409. Found by "piebeer".
22220 - Bridge authorities no longer crash on SIGHUP when they try to
22221 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
22225 - Log less aggressively about circuit timeout changes, and improve
22226 some other circuit timeout messages. Resolves bug 2004.
22227 - Log a little more clearly about the times at which we're no longer
22228 accepting new connections. Resolves bug 2181.
22229 - Reject attempts at the client side to open connections to private
22230 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22231 a randomly chosen exit node. Attempts to do so are always
22232 ill-defined, generally prevented by exit policies, and usually
22233 in error. This will also help to detect loops in transparent
22234 proxy configurations. You can disable this feature by setting
22235 "ClientRejectInternalAddresses 0" in your torrc.
22236 - Always treat failure to allocate an RSA key as an unrecoverable
22238 - Update to the March 1 2011 Maxmind GeoLite Country database.
22240 o Minor features (log subsystem):
22241 - Add documentation for configuring logging at different severities in
22242 different log domains. We've had this feature since 0.2.1.1-alpha,
22243 but for some reason it never made it into the manpage. Fixes
22245 - Make it simpler to specify "All log domains except for A and B".
22246 Previously you needed to say "[*,~A,~B]". Now you can just say
22248 - Add a "LogMessageDomains 1" option to include the domains of log
22249 messages along with the messages. Without this, there's no way
22250 to use log domains without reading the source or doing a lot
22253 o Packaging changes:
22254 - Stop shipping the Tor specs files and development proposal documents
22255 in the tarball. They are now in a separate git repository at
22256 git://git.torproject.org/torspec.git
22259 Changes in version 0.2.1.30 - 2011-02-23
22260 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22261 change is a slight tweak to Tor's TLS handshake that makes relays
22262 and bridges that run this new version reachable from Iran again.
22263 We don't expect this tweak will win the arms race long-term, but it
22264 buys us time until we roll out a better solution.
22267 - Stop sending a CLOCK_SKEW controller status event whenever
22268 we fetch directory information from a relay that has a wrong clock.
22269 Instead, only inform the controller when it's a trusted authority
22270 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22271 the rest of bug 1074.
22272 - Fix a bounds-checking error that could allow an attacker to
22273 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22274 Found by "piebeer".
22275 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22276 Tor would ignore their RelayBandwidthBurst setting,
22277 potentially using more bandwidth than expected. Bugfix on
22278 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22279 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22280 hidserv" in her torrc. The 'hidserv' argument never controlled
22281 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22284 - Adjust our TLS Diffie-Hellman parameters to match those used by
22286 - Update to the February 1 2011 Maxmind GeoLite Country database.
22289 - Check for and reject overly long directory certificates and
22290 directory tokens before they have a chance to hit any assertions.
22291 Bugfix on 0.2.1.28. Found by "doorss".
22292 - Bring the logic that gathers routerinfos and assesses the
22293 acceptability of circuits into line. This prevents a Tor OP from
22294 getting locked in a cycle of choosing its local OR as an exit for a
22295 path (due to a .exit request) and then rejecting the circuit because
22296 its OR is not listed yet. It also prevents Tor clients from using an
22297 OR running in the same instance as an exit (due to a .exit request)
22298 if the OR does not meet the same requirements expected of an OR
22299 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22301 o Packaging changes:
22302 - Stop shipping the Tor specs files and development proposal documents
22303 in the tarball. They are now in a separate git repository at
22304 git://git.torproject.org/torspec.git
22305 - Do not include Git version tags as though they are SVN tags when
22306 generating a tarball from inside a repository that has switched
22307 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22310 Changes in version 0.2.2.22-alpha - 2011-01-25
22311 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
22312 main other change is a slight tweak to Tor's TLS handshake that makes
22313 relays and bridges that run this new version reachable from Iran again.
22314 We don't expect this tweak will win the arms race long-term, but it
22315 will buy us a bit more time until we roll out a better solution.
22318 - Fix a bounds-checking error that could allow an attacker to
22319 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22320 Found by "piebeer".
22321 - Don't assert when changing from bridge to relay or vice versa
22322 via the controller. The assert happened because we didn't properly
22323 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
22324 bug 2433. Reported by bastik.
22327 - Adjust our TLS Diffie-Hellman parameters to match those used by
22329 - Provide a log message stating which geoip file we're parsing
22330 instead of just stating that we're parsing the geoip file.
22331 Implements ticket 2432.
22334 - Check for and reject overly long directory certificates and
22335 directory tokens before they have a chance to hit any assertions.
22336 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
22339 Changes in version 0.2.2.21-alpha - 2011-01-15
22340 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
22341 continues our recent code security audit work. The main fix resolves
22342 a remote heap overflow vulnerability that can allow remote code
22343 execution (CVE-2011-0427). Other fixes address a variety of assert
22344 and crash bugs, most of which we think are hard to exploit remotely.
22346 o Major bugfixes (security), also included in 0.2.1.29:
22347 - Fix a heap overflow bug where an adversary could cause heap
22348 corruption. This bug probably allows remote code execution
22349 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22351 - Prevent a denial-of-service attack by disallowing any
22352 zlib-compressed data whose compression factor is implausibly
22353 high. Fixes part of bug 2324; reported by "doorss".
22354 - Zero out a few more keys in memory before freeing them. Fixes
22355 bug 2384 and part of bug 2385. These key instances found by
22356 "cypherpunks", based on Andrew Case's report about being able
22357 to find sensitive data in Tor's memory space if you have enough
22358 permissions. Bugfix on 0.0.2pre9.
22360 o Major bugfixes (crashes), also included in 0.2.1.29:
22361 - Prevent calls to Libevent from inside Libevent log handlers.
22362 This had potential to cause a nasty set of crashes, especially
22363 if running Libevent with debug logging enabled, and running
22364 Tor with a controller watching for low-severity log messages.
22365 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22366 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22367 underflow errors there too. Fixes the other part of bug 2324.
22368 - Fix a bug where we would assert if we ever had a
22369 cached-descriptors.new file (or another file read directly into
22370 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22371 on 0.2.1.25. Found by doorss.
22372 - Fix some potential asserts and parsing issues with grossly
22373 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22376 o Minor bugfixes (other), also included in 0.2.1.29:
22377 - Fix a bug with handling misformed replies to reverse DNS lookup
22378 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22379 bug reported by doorss.
22380 - Fix compilation on mingw when a pthreads compatibility library
22381 has been installed. (We don't want to use it, so we shouldn't
22382 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22383 - Fix a bug where we would declare that we had run out of virtual
22384 addresses when the address space was only half-exhausted. Bugfix
22386 - Correctly handle the case where AutomapHostsOnResolve is set but
22387 no virtual addresses are available. Fixes bug 2328; bugfix on
22388 0.1.2.1-alpha. Bug found by doorss.
22389 - Correctly handle wrapping around when we run out of virtual
22390 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22392 o Minor features, also included in 0.2.1.29:
22393 - Update to the January 1 2011 Maxmind GeoLite Country database.
22394 - Introduce output size checks on all of our decryption functions.
22396 o Build changes, also included in 0.2.1.29:
22397 - Tor does not build packages correctly with Automake 1.6 and earlier;
22398 added a check to Makefile.am to make sure that we're building with
22399 Automake 1.7 or later.
22400 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22401 because we built it with a too-old version of automake. Thus that
22402 release broke ./configure --enable-openbsd-malloc, which is popular
22403 among really fast exit relays on Linux.
22405 o Major bugfixes, new in 0.2.2.21-alpha:
22406 - Prevent crash/heap corruption when the cbtnummodes consensus
22407 parameter is set to 0 or large values. Fixes bug 2317; bugfix
22410 o Major features, new in 0.2.2.21-alpha:
22411 - Introduce minimum/maximum values that clients will believe
22412 from the consensus. Now we'll have a better chance to avoid crashes
22413 or worse when a consensus param has a weird value.
22415 o Minor features, new in 0.2.2.21-alpha:
22416 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22417 used on bridges, and it makes bridge scanning somewhat easier.
22418 - If writing the state file to disk fails, wait up to an hour before
22419 retrying again, rather than trying again each second. Fixes bug
22420 2346; bugfix on Tor 0.1.1.3-alpha.
22421 - Make Libevent log messages get delivered to controllers later,
22422 and not from inside the Libevent log handler. This prevents unsafe
22423 reentrant Libevent calls while still letting the log messages
22425 - Detect platforms that brokenly use a signed size_t, and refuse to
22426 build there. Found and analyzed by doorss and rransom.
22427 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22430 o Minor bugfixes, new in 0.2.2.21-alpha:
22431 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22432 than waiting forever for them to finish. Fixes bug 2330; bugfix
22433 on 0.2.0.16-alpha. Found by doorss.
22434 - Add assertions to check for overflow in arguments to
22435 base32_encode() and base32_decode(); fix a signed-unsigned
22436 comparison there too. These bugs are not actually reachable in Tor,
22437 but it's good to prevent future errors too. Found by doorss.
22438 - Correctly detect failures to create DNS requests when using Libevent
22439 versions before v2. (Before Libevent 2, we used our own evdns
22440 implementation. Its return values for Libevent's evdns_resolve_*()
22441 functions are not consistent with those from Libevent.) Fixes bug
22442 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22444 o Documentation, new in 0.2.2.21-alpha:
22445 - Document the default socks host and port (127.0.0.1:9050) for
22449 Changes in version 0.2.1.29 - 2011-01-15
22450 Tor 0.2.1.29 continues our recent code security audit work. The main
22451 fix resolves a remote heap overflow vulnerability that can allow remote
22452 code execution. Other fixes address a variety of assert and crash bugs,
22453 most of which we think are hard to exploit remotely.
22455 o Major bugfixes (security):
22456 - Fix a heap overflow bug where an adversary could cause heap
22457 corruption. This bug probably allows remote code execution
22458 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22460 - Prevent a denial-of-service attack by disallowing any
22461 zlib-compressed data whose compression factor is implausibly
22462 high. Fixes part of bug 2324; reported by "doorss".
22463 - Zero out a few more keys in memory before freeing them. Fixes
22464 bug 2384 and part of bug 2385. These key instances found by
22465 "cypherpunks", based on Andrew Case's report about being able
22466 to find sensitive data in Tor's memory space if you have enough
22467 permissions. Bugfix on 0.0.2pre9.
22469 o Major bugfixes (crashes):
22470 - Prevent calls to Libevent from inside Libevent log handlers.
22471 This had potential to cause a nasty set of crashes, especially
22472 if running Libevent with debug logging enabled, and running
22473 Tor with a controller watching for low-severity log messages.
22474 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22475 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22476 underflow errors there too. Fixes the other part of bug 2324.
22477 - Fix a bug where we would assert if we ever had a
22478 cached-descriptors.new file (or another file read directly into
22479 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22480 on 0.2.1.25. Found by doorss.
22481 - Fix some potential asserts and parsing issues with grossly
22482 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22485 o Minor bugfixes (other):
22486 - Fix a bug with handling misformed replies to reverse DNS lookup
22487 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22488 bug reported by doorss.
22489 - Fix compilation on mingw when a pthreads compatibility library
22490 has been installed. (We don't want to use it, so we shouldn't
22491 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22492 - Fix a bug where we would declare that we had run out of virtual
22493 addresses when the address space was only half-exhausted. Bugfix
22495 - Correctly handle the case where AutomapHostsOnResolve is set but
22496 no virtual addresses are available. Fixes bug 2328; bugfix on
22497 0.1.2.1-alpha. Bug found by doorss.
22498 - Correctly handle wrapping around to when we run out of virtual
22499 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22500 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22501 because we built it with a too-old version of automake. Thus that
22502 release broke ./configure --enable-openbsd-malloc, which is popular
22503 among really fast exit relays on Linux.
22506 - Update to the January 1 2011 Maxmind GeoLite Country database.
22507 - Introduce output size checks on all of our decryption functions.
22510 - Tor does not build packages correctly with Automake 1.6 and earlier;
22511 added a check to Makefile.am to make sure that we're building with
22512 Automake 1.7 or later.
22515 Changes in version 0.2.2.20-alpha - 2010-12-17
22516 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22517 exploitable bugs. We also fix a variety of other significant bugs,
22518 change the IP address for one of our directory authorities, and update
22519 the minimum version that Tor relays must run to join the network.
22522 - Fix a remotely exploitable bug that could be used to crash instances
22523 of Tor remotely by overflowing on the heap. Remote-code execution
22524 hasn't been confirmed, but can't be ruled out. Everyone should
22525 upgrade. Bugfix on the 0.1.1 series and later.
22526 - Fix a bug that could break accounting on 64-bit systems with large
22527 time_t values, making them hibernate for impossibly long intervals.
22528 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22529 - Fix a logic error in directory_fetches_from_authorities() that
22530 would cause all _non_-exits refusing single-hop-like circuits
22531 to fetch from authorities, when we wanted to have _exits_ fetch
22532 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22534 - Fix a stream fairness bug that would cause newer streams on a given
22535 circuit to get preference when reading bytes from the origin or
22536 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22537 introduced before the first Tor release, in svn revision r152.
22539 o Directory authority changes:
22540 - Change IP address and ports for gabelmoo (v3 directory authority).
22543 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22544 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22545 - Fix an off-by-one error in calculating some controller command
22546 argument lengths. Fortunately, this mistake is harmless since
22547 the controller code does redundant NUL termination too. Found by
22548 boboper. Bugfix on 0.1.1.1-alpha.
22549 - Do not dereference NULL if a bridge fails to build its
22550 extra-info descriptor. Found by an anonymous commenter on
22551 Trac. Bugfix on 0.2.2.19-alpha.
22554 - Update to the December 1 2010 Maxmind GeoLite Country database.
22555 - Directory authorities now reject relays running any versions of
22556 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22557 known bugs that keep RELAY_EARLY cells from working on rendezvous
22558 circuits. Followup to fix for bug 2081.
22559 - Directory authorities now reject relays running any version of Tor
22560 older than 0.2.0.26-rc. That version is the earliest that fetches
22561 current directory information correctly. Fixes bug 2156.
22562 - Report only the top 10 ports in exit-port stats in order not to
22563 exceed the maximum extra-info descriptor length of 50 KB. Implements
22567 Changes in version 0.2.1.28 - 2010-12-17
22568 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22569 exploitable bugs. We also took this opportunity to change the IP address
22570 for one of our directory authorities, and to update the geoip database
22574 - Fix a remotely exploitable bug that could be used to crash instances
22575 of Tor remotely by overflowing on the heap. Remote-code execution
22576 hasn't been confirmed, but can't be ruled out. Everyone should
22577 upgrade. Bugfix on the 0.1.1 series and later.
22579 o Directory authority changes:
22580 - Change IP address and ports for gabelmoo (v3 directory authority).
22583 - Update to the December 1 2010 Maxmind GeoLite Country database.
22586 Changes in version 0.2.1.27 - 2010-11-23
22587 Yet another OpenSSL security patch broke its compatibility with Tor:
22588 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22589 also took this opportunity to fix several crash bugs, integrate a new
22590 directory authority, and update the bundled GeoIP database.
22593 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22594 No longer set the tlsext_host_name extension on server SSL objects;
22595 but continue to set it on client SSL objects. Our goal in setting
22596 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22597 bugfix on 0.2.1.1-alpha.
22598 - Do not log messages to the controller while shrinking buffer
22599 freelists. Doing so would sometimes make the controller connection
22600 try to allocate a buffer chunk, which would mess up the internals
22601 of the freelist and cause an assertion failure. Fixes bug 1125;
22602 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22603 - Learn our external IP address when we're a relay or bridge, even if
22604 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22605 where we introduced bridge relays that don't need to publish to
22606 be useful. Fixes bug 2050.
22607 - Do even more to reject (and not just ignore) annotations on
22608 router descriptors received anywhere but from the cache. Previously
22609 we would ignore such annotations at first, but cache them to disk
22610 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22611 - When you're using bridges and your network goes away and your
22612 bridges get marked as down, recover when you attempt a new socks
22613 connection (if the network is back), rather than waiting up to an
22614 hour to try fetching new descriptors for your bridges. Bugfix on
22615 0.2.0.3-alpha; fixes bug 1981.
22618 - Move to the November 2010 Maxmind GeoLite country db (rather
22619 than the June 2009 ip-to-country GeoIP db) for our statistics that
22620 count how many users relays are seeing from each country. Now we'll
22621 have more accurate data, especially for many African countries.
22623 o New directory authorities:
22624 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22628 - Fix an assertion failure that could occur in directory caches or
22629 bridge users when using a very short voting interval on a testing
22630 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22632 - Enforce multiplicity rules when parsing annotations. Bugfix on
22633 0.2.0.8-alpha. Found by piebeer.
22634 - Allow handshaking OR connections to take a full KeepalivePeriod
22635 seconds to handshake. Previously, we would close them after
22636 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22637 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22639 - When building with --enable-gcc-warnings on OpenBSD, disable
22640 warnings in system headers. This makes --enable-gcc-warnings
22641 pass on OpenBSD 4.8.
22644 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22645 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22646 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22647 Servers can start sending this code when enough clients recognize
22648 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22649 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22650 Patch from mingw-san.
22653 - Remove the old debian/ directory from the main Tor distribution.
22654 The official Tor-for-debian git repository lives at the URL
22655 https://git.torproject.org/debian/tor.git
22656 - Stop shipping the old doc/website/ directory in the tarball. We
22657 changed the website format in late 2010, and what we shipped in
22658 0.2.1.26 really wasn't that useful anyway.
22661 Changes in version 0.2.2.19-alpha - 2010-11-22
22662 Yet another OpenSSL security patch broke its compatibility with Tor:
22663 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
22666 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22667 No longer set the tlsext_host_name extension on server SSL objects;
22668 but continue to set it on client SSL objects. Our goal in setting
22669 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22670 bugfix on 0.2.1.1-alpha.
22673 - Try harder not to exceed the maximum length of 50 KB when writing
22674 statistics to extra-info descriptors. This bug was triggered by very
22675 fast relays reporting exit-port, entry, and dirreq statistics.
22676 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
22677 - Publish a router descriptor even if generating an extra-info
22678 descriptor fails. Previously we would not publish a router
22679 descriptor without an extra-info descriptor; this can cause fast
22680 exit relays collecting exit-port statistics to drop from the
22681 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22684 Changes in version 0.2.2.18-alpha - 2010-11-16
22685 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
22686 us lately, makes unpublished bridge relays able to detect their IP
22687 address, and fixes a wide variety of other bugs to get us much closer
22688 to a stable release.
22691 - Do even more to reject (and not just ignore) annotations on
22692 router descriptors received anywhere but from the cache. Previously
22693 we would ignore such annotations at first, but cache them to disk
22694 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22695 - Do not log messages to the controller while shrinking buffer
22696 freelists. Doing so would sometimes make the controller connection
22697 try to allocate a buffer chunk, which would mess up the internals
22698 of the freelist and cause an assertion failure. Fixes bug 1125;
22699 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22700 - Learn our external IP address when we're a relay or bridge, even if
22701 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22702 where we introduced bridge relays that don't need to publish to
22703 be useful. Fixes bug 2050.
22704 - Maintain separate TLS contexts and certificates for incoming and
22705 outgoing connections in bridge relays. Previously we would use the
22706 same TLS contexts and certs for incoming and outgoing connections.
22707 Bugfix on 0.2.0.3-alpha; addresses bug 988.
22708 - Maintain separate identity keys for incoming and outgoing TLS
22709 contexts in bridge relays. Previously we would use the same
22710 identity keys for incoming and outgoing TLS contexts. Bugfix on
22711 0.2.0.3-alpha; addresses the other half of bug 988.
22712 - Avoid an assertion failure when we as an authority receive a
22713 duplicate upload of a router descriptor that we already have,
22714 but which we previously considered an obsolete descriptor.
22715 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
22716 - Avoid a crash bug triggered by looking at a dangling pointer while
22717 setting the network status consensus. Found by Robert Ransom.
22718 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
22719 - Fix a logic error where servers that _didn't_ act as exits would
22720 try to keep their server lists more aggressively up to date than
22721 exits, when it was supposed to be the other way around. Bugfix
22724 o Minor bugfixes (on Tor 0.2.1.x and earlier):
22725 - When we're trying to guess whether we know our IP address as
22726 a relay, we would log various ways that we failed to guess
22727 our address, but never log that we ended up guessing it
22728 successfully. Now add a log line to help confused and anxious
22729 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
22730 - Bring the logic that gathers routerinfos and assesses the
22731 acceptability of circuits into line. This prevents a Tor OP from
22732 getting locked in a cycle of choosing its local OR as an exit for a
22733 path (due to a .exit request) and then rejecting the circuit because
22734 its OR is not listed yet. It also prevents Tor clients from using an
22735 OR running in the same instance as an exit (due to a .exit request)
22736 if the OR does not meet the same requirements expected of an OR
22737 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22738 - Correctly describe errors that occur when generating a TLS object.
22739 Previously we would attribute them to a failure while generating a
22740 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
22742 - Enforce multiplicity rules when parsing annotations. Bugfix on
22743 0.2.0.8-alpha. Found by piebeer.
22744 - Fix warnings that newer versions of autoconf produced during
22745 ./autogen.sh. These warnings appear to be harmless in our case,
22746 but they were extremely verbose. Fixes bug 2020.
22748 o Minor bugfixes (on Tor 0.2.2.x):
22749 - Enable protection of small arrays whenever we build with gcc
22750 hardening features, not only when also building with warnings
22751 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
22754 - Make hidden services work better in private Tor networks by not
22755 requiring any uptime to join the hidden service descriptor
22756 DHT. Implements ticket 2088.
22757 - Rate-limit the "your application is giving Tor only an IP address"
22758 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
22759 - When AllowSingleHopExits is set, print a warning to explain to the
22760 relay operator why most clients are avoiding her relay.
22761 - Update to the November 1 2010 Maxmind GeoLite Country database.
22763 o Code simplifications and refactoring:
22764 - When we fixed bug 1038 we had to put in a restriction not to send
22765 RELAY_EARLY cells on rend circuits. This was necessary as long
22766 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
22767 active. Now remove this obsolete check. Resolves bug 2081.
22768 - Some options used different conventions for uppercasing of acronyms
22769 when comparing manpage and source. Fix those in favor of the
22770 manpage, as it makes sense to capitalize acronyms.
22771 - Remove the torrc.complete file. It hasn't been kept up to date
22772 and users will have better luck checking out the manpage.
22773 - Remove the obsolete "NoPublish" option; it has been flagged
22774 as obsolete and has produced a warning since 0.1.1.18-rc.
22775 - Remove everything related to building the expert bundle for OS X.
22776 It has confused many users, doesn't work right on OS X 10.6,
22777 and is hard to get rid of once installed. Resolves bug 1274.
22780 Changes in version 0.2.2.17-alpha - 2010-09-30
22781 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
22782 to use one-hop circuits (which can put the exit relays at higher risk,
22783 plus unbalance the network); fixes a big bug in bandwidth accounting
22784 for relays that want to limit their monthly bandwidth use; fixes a
22785 big pile of bugs in how clients tolerate temporary network failure;
22786 and makes our adaptive circuit build timeout feature (which improves
22787 client performance if your network is fast while not breaking things
22788 if your network is slow) better handle bad networks.
22791 - Exit relays now try harder to block exit attempts from unknown
22792 relays, to make it harder for people to use them as one-hop proxies
22793 a la tortunnel. Controlled by the refuseunknownexits consensus
22794 parameter (currently enabled), or you can override it on your
22795 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
22797 o Major bugfixes (0.2.1.x and earlier):
22798 - Fix a bug in bandwidth accounting that could make us use twice
22799 the intended bandwidth when our interval start changes due to
22800 daylight saving time. Now we tolerate skew in stored vs computed
22801 interval starts: if the start of the period changes by no more than
22802 50% of the period's duration, we remember bytes that we transferred
22803 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
22804 - Always search the Windows system directory for system DLLs, and
22805 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
22806 - When you're using bridges and your network goes away and your
22807 bridges get marked as down, recover when you attempt a new socks
22808 connection (if the network is back), rather than waiting up to an
22809 hour to try fetching new descriptors for your bridges. Bugfix on
22810 0.2.0.3-alpha; fixes bug 1981.
22812 o Major bugfixes (on 0.2.2.x):
22813 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
22815 - Fix a segfault that could happen when operating a bridge relay with
22816 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
22817 - The consensus bandwidth-weights (used by clients to choose fast
22818 relays) entered an unexpected edge case in September where
22819 Exits were much scarcer than Guards, resulting in bad weight
22820 recommendations. Now we compute them using new constraints that
22821 should succeed in all cases. Also alter directory authorities to
22822 not include the bandwidth-weights line if they fail to produce
22823 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
22824 - When weighting bridges during path selection, we used to trust
22825 the bandwidths they provided in their descriptor, only capping them
22826 at 10MB/s. This turned out to be problematic for two reasons:
22827 Bridges could claim to handle a lot more traffic then they
22828 actually would, thus making more clients pick them and have a
22829 pretty effective DoS attack. The other issue is that new bridges
22830 that might not have a good estimate for their bw capacity yet
22831 would not get used at all unless no other bridges are available
22832 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
22834 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
22835 - Ignore cannibalized circuits when recording circuit build times.
22836 This should provide for a minor performance improvement for hidden
22837 service users using 0.2.2.14-alpha, and should remove two spurious
22838 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
22839 - Simplify the logic that causes us to decide if the network is
22840 unavailable for purposes of recording circuit build times. If we
22841 receive no cells whatsoever for the entire duration of a circuit's
22842 full measured lifetime, the network is probably down. Also ignore
22843 one-hop directory fetching circuit timeouts when calculating our
22844 circuit build times. These changes should hopefully reduce the
22845 cases where we see ridiculous circuit build timeouts for people
22846 with spotty wireless connections. Fixes part of bug 1772; bugfix
22848 - Prevent the circuit build timeout from becoming larger than
22849 the maximum build time we have ever seen. Also, prevent the time
22850 period for measurement circuits from becoming larger than twice that
22851 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
22854 - When we run out of directory information such that we can't build
22855 circuits, but then get enough that we can build circuits, log when
22856 we actually construct a circuit, so the user has a better chance of
22857 knowing what's going on. Fixes bug 1362.
22858 - Be more generous with how much bandwidth we'd use up (with
22859 accounting enabled) before entering "soft hibernation". Previously,
22860 we'd refuse new connections and circuits once we'd used up 95% of
22861 our allotment. Now, we use up 95% of our allotment, AND make sure
22862 that we have no more than 500MB (or 3 hours of expected traffic,
22863 whichever is lower) remaining before we enter soft hibernation.
22864 - If we've configured EntryNodes and our network goes away and/or all
22865 our entrynodes get marked down, optimistically retry them all when
22866 a new socks application request appears. Fixes bug 1882.
22867 - Add some more defensive programming for architectures that can't
22868 handle unaligned integer accesses. We don't know of any actual bugs
22869 right now, but that's the best time to fix them. Fixes bug 1943.
22870 - Support line continuations in the torrc config file. If a line
22871 ends with a single backslash character, the newline is ignored, and
22872 the configuration value is treated as continuing on the next line.
22875 o Minor bugfixes (on 0.2.1.x and earlier):
22876 - For bandwidth accounting, calculate our expected bandwidth rate
22877 based on the time during which we were active and not in
22878 soft-hibernation during the last interval. Previously, we were
22879 also considering the time spent in soft-hibernation. If this
22880 was a long time, we would wind up underestimating our bandwidth
22881 by a lot, and skewing our wakeup time towards the start of the
22882 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
22884 o Minor bugfixes (on 0.2.2.x):
22885 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
22886 which were disabled by the circuit build timeout changes in
22887 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
22888 - Make sure we don't warn about missing bandwidth weights when
22889 choosing bridges or other relays not in the consensus. Bugfix on
22890 0.2.2.10-alpha; fixes bug 1805.
22891 - In our logs, do not double-report signatures from unrecognized
22892 authorities both as "from unknown authority" and "not
22893 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
22896 Changes in version 0.2.2.16-alpha - 2010-09-17
22897 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
22898 evident at exit relays), and also continues to resolve all the little
22899 bugs that have been filling up trac lately.
22901 o Major bugfixes (stream-level fairness):
22902 - When receiving a circuit-level SENDME for a blocked circuit, try
22903 to package cells fairly from all the streams that had previously
22904 been blocked on that circuit. Previously, we had started with the
22905 oldest stream, and allowed each stream to potentially exhaust
22906 the circuit's package window. This gave older streams on any
22907 given circuit priority over newer ones. Fixes bug 1937. Detected
22908 originally by Camilo Viecco. This bug was introduced before the
22909 first Tor release, in svn commit r152: it is the new winner of
22910 the longest-lived bug prize.
22911 - When the exit relay got a circuit-level sendme cell, it started
22912 reading on the exit streams, even if had 500 cells queued in the
22913 circuit queue already, so the circuit queue just grew and grew in
22914 some cases. We fix this by not re-enabling reading on receipt of a
22915 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
22916 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
22918 - Newly created streams were allowed to read cells onto circuits,
22919 even if the circuit's cell queue was blocked and waiting to drain.
22920 This created potential unfairness, as older streams would be
22921 blocked, but newer streams would gladly fill the queue completely.
22922 We add code to detect this situation and prevent any stream from
22923 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
22927 - Update to the September 1 2010 Maxmind GeoLite Country database.
22928 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
22929 not. This would lead to a cookie that is still not group readable.
22930 Closes bug 1843. Suggested by katmagic.
22931 - When logging a rate-limited warning, we now mention how many messages
22932 got suppressed since the last warning.
22933 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
22934 do individual connection-level rate limiting of clients. The torrc
22935 config options with the same names trump the consensus params, if
22936 both are present. Replaces the old "bwconnrate" and "bwconnburst"
22937 consensus params which were broken from 0.2.2.7-alpha through
22938 0.2.2.14-alpha. Closes bug 1947.
22939 - When a router changes IP address or port, authorities now launch
22940 a new reachability test for it. Implements ticket 1899.
22941 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
22942 2 no signature, 4 required" messages about consensus signatures
22943 easier to read, and make sure they get logged at the same severity
22944 as the messages explaining which keys are which. Fixes bug 1290.
22945 - Don't warn when we have a consensus that we can't verify because
22946 of missing certificates, unless those certificates are ones
22947 that we have been trying and failing to download. Fixes bug 1145.
22948 - If you configure your bridge with a known identity fingerprint,
22949 and the bridge authority is unreachable (as it is in at least
22950 one country now), fall back to directly requesting the descriptor
22951 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
22953 - When building with --enable-gcc-warnings on OpenBSD, disable
22954 warnings in system headers. This makes --enable-gcc-warnings
22955 pass on OpenBSD 4.8.
22957 o Minor bugfixes (on 0.2.1.x and earlier):
22958 - Authorities will now attempt to download consensuses if their
22959 own efforts to make a live consensus have failed. This change
22960 means authorities that restart will fetch a valid consensus, and
22961 it means authorities that didn't agree with the current consensus
22962 will still fetch and serve it if it has enough signatures. Bugfix
22963 on 0.2.0.9-alpha; fixes bug 1300.
22964 - Ensure DNS requests launched by "RESOLVE" commands from the
22965 controller respect the __LeaveStreamsUnattached setconf options. The
22966 same goes for requests launched via DNSPort or transparent
22967 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
22968 - Allow handshaking OR connections to take a full KeepalivePeriod
22969 seconds to handshake. Previously, we would close them after
22970 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22971 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22973 - Rate-limit "Failed to hand off onionskin" warnings.
22974 - Never relay a cell for a circuit we have already destroyed.
22975 Between marking a circuit as closeable and finally closing it,
22976 it may have been possible for a few queued cells to get relayed,
22977 even though they would have been immediately dropped by the next
22978 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
22979 - Never queue a cell for a circuit that's already been marked
22981 - Never vote for a server as "Running" if we have a descriptor for
22982 it claiming to be hibernating, and that descriptor was published
22983 more recently than our last contact with the server. Bugfix on
22984 0.2.0.3-alpha; fixes bug 911.
22985 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
22988 o Minor bugfixes (on 0.2.2.x):
22989 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
22990 down if a directory fetch fails and you've configured either
22991 bridges or EntryNodes. The intent was to mark the relay as down
22992 _unless_ you're using bridges or EntryNodes, since if you are
22993 then you could quickly run out of entry points.
22994 - Fix the Windows directory-listing code. A bug introduced in
22995 0.2.2.14-alpha could make Windows directory servers forget to load
22996 some of their cached v2 networkstatus files.
22997 - Really allow clients to use relays as bridges. Fixes bug 1776;
22998 bugfix on 0.2.2.15-alpha.
22999 - Demote a warn to info that happens when the CellStatistics option
23000 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
23001 Reported by Moritz Bartl.
23002 - On Windows, build correctly either with or without Unicode support.
23003 This is necessary so that Tor can support fringe platforms like
23004 Windows 98 (which has no Unicode), or Windows CE (which has no
23005 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
23008 - Add a unit test for cross-platform directory-listing code.
23011 Changes in version 0.2.2.15-alpha - 2010-08-18
23012 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
23013 fixes a variety of other bugs that were preventing performance
23014 experiments from moving forward, fixes several bothersome memory leaks,
23015 and generally closes a lot of smaller bugs that have been filling up
23019 - Stop assigning the HSDir flag to relays that disable their
23020 DirPort (and thus will refuse to answer directory requests). This
23021 fix should dramatically improve the reachability of hidden services:
23022 hidden services and hidden service clients pick six HSDir relays
23023 to store and retrieve the hidden service descriptor, and currently
23024 about half of the HSDir relays will refuse to work. Bugfix on
23025 0.2.0.10-alpha; fixes part of bug 1693.
23026 - The PerConnBWRate and Burst config options, along with the
23027 bwconnrate and bwconnburst consensus params, initialized each conn's
23028 token bucket values only when the connection is established. Now we
23029 update them if the config options change, and update them every time
23030 we get a new consensus. Otherwise we can encounter an ugly edge
23031 case where we initialize an OR conn to client-level bandwidth,
23032 but then later the relay joins the consensus and we leave it
23033 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
23034 - Fix a regression that caused Tor to rebind its ports if it receives
23035 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
23038 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23039 should give us approximately 40-50% more Guard-flagged nodes,
23040 improving the anonymity the Tor network can provide and also
23041 decreasing the dropoff in throughput that relays experience when
23042 they first get the Guard flag.
23043 - Allow enabling or disabling the *Statistics config options while
23047 - Update to the August 1 2010 Maxmind GeoLite Country database.
23048 - Have the controller interface give a more useful message than
23049 "Internal Error" in response to failed GETINFO requests.
23050 - Warn when the same option is provided more than once in a torrc
23051 file, on the command line, or in a single SETCONF statement, and
23052 the option is one that only accepts a single line. Closes bug 1384.
23053 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23054 Patch from mingw-san.
23055 - Add support for the country code "{??}" in torrc options like
23056 ExcludeNodes, to indicate all routers of unknown country. Closes
23058 - Relays report the number of bytes spent on answering directory
23059 requests in extra-info descriptors similar to {read,write}-history.
23060 Implements enhancement 1790.
23062 o Minor bugfixes (on 0.2.1.x and earlier):
23063 - Complain if PublishServerDescriptor is given multiple arguments that
23064 include 0 or 1. This configuration will be rejected in the future.
23065 Bugfix on 0.2.0.1-alpha; closes bug 1107.
23066 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
23067 Bugfix on 0.2.0.13-alpha; closes bug 928.
23068 - Change "Application request when we're believed to be offline."
23069 notice to "Application request when we haven't used client
23070 functionality lately.", to clarify that it's not an error. Bugfix
23071 on 0.0.9.3; fixes bug 1222.
23072 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
23073 would return "551 Internal error" rather than "552 Unrecognized key
23074 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
23075 - Users can't configure a regular relay to be their bridge. It didn't
23076 work because when Tor fetched the bridge descriptor, it found
23077 that it already had it, and didn't realize that the purpose of the
23078 descriptor had changed. Now we replace routers with a purpose other
23079 than bridge with bridge descriptors when fetching them. Bugfix on
23080 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
23081 refetch the descriptor with router purpose 'general', disabling
23083 - Fix a rare bug in rend_fn unit tests: we would fail a test when
23084 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
23085 on 0.2.0.10-alpha; fixes bug 1808.
23086 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23087 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23088 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23089 Servers can start sending this code when enough clients recognize
23090 it. Also update the spec to reflect this new reason. Bugfix on
23091 0.1.0.1-rc; fixes part of bug 1793.
23092 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
23093 when we switch from being a public relay to a bridge. Otherwise
23094 there will still be clients that see the relay in their consensus,
23095 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
23097 - Instead of giving an assertion failure on an internal mismatch
23098 on estimated freelist size, just log a BUG warning and try later.
23099 Mitigates but does not fix bug 1125.
23100 - Fix an assertion failure that could occur in caches or bridge users
23101 when using a very short voting interval on a testing network.
23102 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
23104 o Minor bugfixes (on 0.2.2.x):
23105 - Alter directory authorities to always consider Exit-flagged nodes
23106 as potential Guard nodes in their votes. The actual decision to
23107 use Exits as Guards is done in the consensus bandwidth weights.
23108 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
23109 - When the controller is reporting the purpose of circuits that
23110 didn't finish building before the circuit build timeout, it was
23111 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
23112 - Our libevent version parsing code couldn't handle versions like
23113 1.4.14b-stable and incorrectly warned the user about using an
23114 old and broken version of libevent. Treat 1.4.14b-stable like
23115 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
23117 - Don't use substitution references like $(VAR:MOD) when
23118 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
23119 '$(:x)' to 'x' rather than the empty string. This bites us in
23120 doc/ when configured with --disable-asciidoc. Bugfix on
23121 0.2.2.9-alpha; fixes bug 1773.
23122 - Remove a spurious hidden service server-side log notice about
23123 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
23125 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
23127 - Correctly report written bytes on linked connections. Found while
23128 implementing 1790. Bugfix on 0.2.2.4-alpha.
23129 - Fix three memory leaks: one in circuit_build_times_parse_state(),
23130 one in dirvote_add_signatures_to_pending_consensus(), and one every
23131 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
23132 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
23134 o Code simplifications and refactoring:
23135 - Take a first step towards making or.h smaller by splitting out
23136 function definitions for all source files in src/or/. Leave
23137 structures and defines in or.h for now.
23138 - Remove a bunch of unused function declarations as well as a block of
23139 #if 0'd code from the unit tests. Closes bug 1824.
23140 - New unit tests for exit-port history statistics; refactored exit
23141 statistics code to be more easily tested.
23142 - Remove the old debian/ directory from the main Tor distribution.
23143 The official Tor-for-debian git repository lives at the URL
23144 https://git.torproject.org/debian/tor.git
23147 Changes in version 0.2.2.14-alpha - 2010-07-12
23148 Tor 0.2.2.14-alpha greatly improves client-side handling of
23149 circuit build timeouts, which are used to estimate speed and improve
23150 performance. We also move to a much better GeoIP database, port Tor to
23151 Windows CE, introduce new compile flags that improve code security,
23152 add an eighth v3 directory authority, and address a lot of more
23156 - Tor directory authorities no longer crash when started with a
23157 cached-microdesc-consensus file in their data directory. Bugfix
23158 on 0.2.2.6-alpha; fixes bug 1532.
23159 - Treat an unset $HOME like an empty $HOME rather than triggering an
23160 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
23161 - Ignore negative and large circuit build timeout values that can
23162 happen during a suspend or hibernate. These values caused various
23163 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
23164 - Alter calculation of Pareto distribution parameter 'Xm' for
23165 Circuit Build Timeout learning to use the weighted average of the
23166 top N=3 modes (because we have three entry guards). Considering
23167 multiple modes should improve the timeout calculation in some cases,
23168 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
23170 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
23171 right censored distribution model. This approach improves over the
23172 synthetic timeout generation approach that was producing insanely
23173 high timeout values. Now we calculate build timeouts using truncated
23174 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
23175 - Do not close circuits that are under construction when they reach
23176 the circuit build timeout. Instead, leave them building (but do not
23177 use them) for up until the time corresponding to the 95th percentile
23178 on the Pareto CDF or 60 seconds, whichever is greater. This is done
23179 to provide better data for the new Pareto model. This percentile
23180 can be controlled by the consensus.
23183 - Move to the June 2010 Maxmind GeoLite country db (rather than the
23184 June 2009 ip-to-country GeoIP db) for our statistics that count
23185 how many users relays are seeing from each country. Now we have
23186 more accurate data for many African countries.
23187 - Port Tor to build and run correctly on Windows CE systems, using
23188 the wcecompat library. Contributed by Valerio Lupi.
23189 - New "--enable-gcc-hardening" ./configure flag (off by default)
23190 to turn on gcc compile time hardening options. It ensures
23191 that signed ints have defined behavior (-fwrapv), enables
23192 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
23193 with canaries (-fstack-protector-all), turns on ASLR protection if
23194 supported by the kernel (-fPIE, -pie), and adds additional security
23195 related warnings. Verified to work on Mac OS X and Debian Lenny.
23196 - New "--enable-linker-hardening" ./configure flag (off by default)
23197 to turn on ELF specific hardening features (relro, now). This does
23198 not work with Mac OS X or any other non-ELF binary format.
23200 o New directory authorities:
23201 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23205 - New config option "WarnUnsafeSocks 0" disables the warning that
23206 occurs whenever Tor receives a socks handshake using a version of
23207 the socks protocol that can only provide an IP address (rather
23208 than a hostname). Setups that do DNS locally over Tor are fine,
23209 and we shouldn't spam the logs in that case.
23210 - Convert the HACKING file to asciidoc, and add a few new sections
23211 to it, explaining how we use Git, how we make changelogs, and
23212 what should go in a patch.
23213 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
23214 event, to give information on the current rate of circuit timeouts
23215 over our stored history.
23216 - Add ability to disable circuit build time learning via consensus
23217 parameter and via a LearnCircuitBuildTimeout config option. Also
23218 automatically disable circuit build time calculation if we are
23219 either a AuthoritativeDirectory, or if we fail to write our state
23220 file. Fixes bug 1296.
23221 - More gracefully handle corrupt state files, removing asserts
23222 in favor of saving a backup and resetting state.
23223 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
23227 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23229 - When a2x fails, mention that the user could disable manpages instead
23230 of trying to fix their asciidoc installation.
23231 - Where available, use Libevent 2.0's periodic timers so that our
23232 once-per-second cleanup code gets called even more closely to
23233 once per second than it would otherwise. Fixes bug 943.
23234 - If you run a bridge that listens on multiple IP addresses, and
23235 some user configures a bridge address that uses a different IP
23236 address than your bridge writes in its router descriptor, and the
23237 user doesn't specify an identity key, their Tor would discard the
23238 descriptor because "it isn't one of our configured bridges", and
23239 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
23240 Bugfix on 0.2.0.3-alpha.
23241 - If OpenSSL fails to make a duplicate of a private or public key, log
23242 an error message and try to exit cleanly. May help with debugging
23243 if bug 1209 ever remanifests.
23244 - Save a couple bytes in memory allocation every time we escape
23245 certain characters in a string. Patch from Florian Zumbiehl.
23246 - Make it explicit that we don't cannibalize one-hop circuits. This
23247 happens in the wild, but doesn't turn out to be a problem because
23248 we fortunately don't use those circuits. Many thanks to outofwords
23249 for the initial analysis and to swissknife who confirmed that
23250 two-hop circuits are actually created.
23251 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
23252 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
23253 - Eliminate a case where a circuit build time warning was displayed
23254 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
23257 Changes in version 0.2.1.26 - 2010-05-02
23258 Tor 0.2.1.26 addresses the recent connection and memory overload
23259 problems we've been seeing on relays, especially relays with their
23260 DirPort open. If your relay has been crashing, or you turned it off
23261 because it used too many resources, give this release a try.
23263 This release also fixes yet another instance of broken OpenSSL libraries
23264 that was causing some relays to drop out of the consensus.
23267 - Teach relays to defend themselves from connection overload. Relays
23268 now close idle circuits early if it looks like they were intended
23269 for directory fetches. Relays are also more aggressive about closing
23270 TLS connections that have no circuits on them. Such circuits are
23271 unlikely to be re-used, and tens of thousands of them were piling
23272 up at the fast relays, causing the relays to run out of sockets
23273 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23274 their directory fetches over TLS).
23275 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23276 that claim to be earlier than 0.9.8m, but which have in reality
23277 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23278 behavior. Possible fix for some cases of bug 1346.
23279 - Directory mirrors were fetching relay descriptors only from v2
23280 directory authorities, rather than v3 authorities like they should.
23281 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23282 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23285 - Finally get rid of the deprecated and now harmful notion of "clique
23286 mode", where directory authorities maintain TLS connections to
23290 - In the util/threads test, no longer free the test_mutex before all
23291 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23292 - The master thread could starve the worker threads quite badly on
23293 certain systems, causing them to run only partially in the allowed
23294 window. This resulted in test failures. Now the master thread sleeps
23295 occasionally for a few microseconds while the two worker-threads
23296 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23299 Changes in version 0.2.2.13-alpha - 2010-04-24
23300 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
23301 problems we've been seeing on relays, especially relays with their
23302 DirPort open. If your relay has been crashing, or you turned it off
23303 because it used too many resources, give this release a try.
23306 - Teach relays to defend themselves from connection overload. Relays
23307 now close idle circuits early if it looks like they were intended
23308 for directory fetches. Relays are also more aggressive about closing
23309 TLS connections that have no circuits on them. Such circuits are
23310 unlikely to be re-used, and tens of thousands of them were piling
23311 up at the fast relays, causing the relays to run out of sockets
23312 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23313 their directory fetches over TLS).
23316 - Finally get rid of the deprecated and now harmful notion of "clique
23317 mode", where directory authorities maintain TLS connections to
23319 - Directory authorities now do an immediate reachability check as soon
23320 as they hear about a new relay. This change should slightly reduce
23321 the time between setting up a relay and getting listed as running
23322 in the consensus. It should also improve the time between setting
23323 up a bridge and seeing use by bridge users.
23324 - Directory authorities no longer launch a TLS connection to every
23325 relay as they startup. Now that we have 2k+ descriptors cached,
23326 the resulting network hiccup is becoming a burden. Besides,
23327 authorities already avoid voting about Running for the first half
23328 hour of their uptime.
23331 Changes in version 0.2.2.12-alpha - 2010-04-20
23332 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
23333 handle and vote on descriptors. It was causing relays to drop out of
23337 - Many relays have been falling out of the consensus lately because
23338 not enough authorities know about their descriptor for them to get
23339 a majority of votes. When we deprecated the v2 directory protocol,
23340 we got rid of the only way that v3 authorities can hear from each
23341 other about other descriptors. Now authorities examine every v3
23342 vote for new descriptors, and fetch them from that authority. Bugfix
23344 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
23345 and a warning in or.h related to bandwidth_weight_rule_t that
23346 prevented clean compile on OS X. Fixes bug 1363; bugfix on
23348 - Fix a segfault on relays when DirReqStatistics is enabled
23349 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
23353 - Demote a confusing TLS warning that relay operators might get when
23354 someone tries to talk to their OrPort. It is neither the operator's
23355 fault nor can they do anything about it. Fixes bug 1364; bugfix
23359 Changes in version 0.2.2.11-alpha - 2010-04-15
23360 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
23361 libraries that was causing some relays to drop out of the consensus.
23364 - Directory mirrors were fetching relay descriptors only from v2
23365 directory authorities, rather than v3 authorities like they should.
23366 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23367 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23368 - Fix a parsing error that made every possible value of
23369 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
23370 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
23371 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
23372 about the option without breaking older ones.
23373 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23374 that claim to be earlier than 0.9.8m, but which have in reality
23375 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23376 behavior. Possible fix for some cases of bug 1346.
23379 - Experiment with a more aggressive approach to preventing clients
23380 from making one-hop exit streams. Exit relays who want to try it
23381 out can set "RefuseUnknownExits 1" in their torrc, and then look
23382 for "Attempt by %s to open a stream" log messages. Let us know
23384 - Add support for statically linking zlib by specifying
23385 --enable-static-zlib, to go with our support for statically linking
23386 openssl and libevent. Resolves bug 1358.
23389 - Fix a segfault that happens whenever a Tor client that is using
23390 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
23392 - When we cleaned up the contrib/tor-exit-notice.html file, we left
23393 out the first line. Fixes bug 1295.
23394 - When building the manpage from a tarball, we required asciidoc, but
23395 the asciidoc -> roff/html conversion was already done for the
23396 tarball. Make 'make' complain only when we need asciidoc (either
23397 because we're compiling directly from git, or because we altered
23398 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
23399 - When none of the directory authorities vote on any params, Tor
23400 segfaulted when trying to make the consensus from the votes. We
23401 didn't trigger the bug in practice, because authorities do include
23402 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
23405 - In the util/threads test, no longer free the test_mutex before all
23406 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23407 - The master thread could starve the worker threads quite badly on
23408 certain systems, causing them to run only partially in the allowed
23409 window. This resulted in test failures. Now the master thread sleeps
23410 occasionally for a few microseconds while the two worker-threads
23411 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23414 Changes in version 0.2.2.10-alpha - 2010-03-07
23415 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
23416 could prevent relays from guessing their IP address correctly. It also
23417 starts the groundwork for another client-side performance boost, since
23418 currently we're not making efficient use of relays that have both the
23419 Guard flag and the Exit flag.
23422 - Fix a regression from our patch for bug 1244 that caused relays
23423 to guess their IP address incorrectly if they didn't set Address
23424 in their torrc and/or their address fails to resolve. Bugfix on
23425 0.2.2.9-alpha; fixes bug 1269.
23427 o Major features (performance):
23428 - Directory authorities now compute consensus weightings that instruct
23429 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23430 and no flag. Clients that use these weightings will distribute
23431 network load more evenly across these different relay types. The
23432 weightings are in the consensus so we can change them globally in
23433 the future. Extra thanks to "outofwords" for finding some nasty
23434 security bugs in the first implementation of this feature.
23436 o Minor features (performance):
23437 - Always perform router selections using weighted relay bandwidth,
23438 even if we don't need a high capacity circuit at the time. Non-fast
23439 circuits now only differ from fast ones in that they can use relays
23440 not marked with the Fast flag. This "feature" could turn out to
23441 be a horrible bug; we should investigate more before it goes into
23445 - Allow disabling building of the manpages. Skipping the manpage
23446 speeds up the build considerably.
23448 o Minor bugfixes (on 0.2.2.x):
23449 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23450 Bugfix on 0.2.2.9-alpha.
23451 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23452 config option. Bugfix on 0.2.2.7-alpha.
23453 - Ship the asciidoc-helper file in the tarball, so that people can
23454 build from source if they want to, and touching the .1.txt files
23455 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23457 o Minor bugfixes (on 0.2.1.x or earlier):
23458 - Fix a dereference-then-NULL-check sequence when publishing
23459 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23461 - Fix another dereference-then-NULL-check sequence. Bugfix on
23462 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23463 - Make sure we treat potentially not NUL-terminated strings correctly.
23464 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23466 o Code simplifications and refactoring:
23467 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23468 compliant. Based on a patch from Christian Kujau.
23469 - Don't use sed in asciidoc-helper anymore.
23470 - Make the build process fail if asciidoc cannot be found and
23471 building with asciidoc isn't disabled.
23474 Changes in version 0.2.2.9-alpha - 2010-02-22
23475 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23476 location of a directory authority, and cleans up a bunch of small bugs.
23478 o Directory authority changes:
23479 - Change IP address for dannenberg (v3 directory authority), and
23480 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23481 service directory authority) from the list.
23484 - Make Tor work again on the latest OS X: when deciding whether to
23485 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23486 version at run-time, not compile time. We need to do this because
23487 Apple doesn't update its dev-tools headers when it updates its
23488 libraries in a security patch.
23489 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23490 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23491 a memory leak when requesting a hidden service descriptor we've
23492 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23494 - Authorities could be tricked into giving out the Exit flag to relays
23495 that didn't allow exiting to any ports. This bug could screw
23496 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23497 1238. Bug discovered by Martin Kowalczyk.
23498 - When freeing a session key, zero it out completely. We only zeroed
23499 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23500 patched by ekir. Fixes bug 1254.
23503 - Fix static compilation by listing the openssl libraries in the right
23504 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23505 - Resume handling .exit hostnames in a special way: originally we
23506 stripped the .exit part and used the requested exit relay. In
23507 0.2.2.1-alpha we stopped treating them in any special way, meaning
23508 if you use a .exit address then Tor will pass it on to the exit
23509 relay. Now we reject the .exit stream outright, since that behavior
23510 might be more expected by the user. Found and diagnosed by Scott
23511 Bennett and Downie on or-talk.
23512 - Don't spam the controller with events when we have no file
23513 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23514 for log messages was already solved from bug 748.)
23515 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23517 - Make the DNSPort option work with libevent 2.x. Don't alter the
23518 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23519 - Emit a GUARD DROPPED controller event for a case we missed.
23520 - Make more fields in the controller protocol case-insensitive, since
23521 control-spec.txt said they were.
23522 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23523 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23524 - Fix a spec conformance issue: the network-status-version token
23525 must be the first token in a v3 consensus or vote. Discovered by
23526 parakeep. Bugfix on 0.2.0.3-alpha.
23528 o Code simplifications and refactoring:
23529 - Generate our manpage and HTML documentation using Asciidoc. This
23530 change should make it easier to maintain the documentation, and
23531 produce nicer HTML.
23532 - Remove the --enable-iphone option. According to reports from Marco
23533 Bonetti, Tor builds fine without any special tweaking on recent
23534 iPhone SDK versions.
23535 - Removed some unnecessary files from the source distribution. The
23536 AUTHORS file has now been merged into the people page on the
23537 website. The roadmaps and design doc can now be found in the
23538 projects directory in svn.
23539 - Enabled various circuit build timeout constants to be controlled
23540 by consensus parameters. Also set better defaults for these
23541 parameters based on experimentation on broadband and simulated
23542 high latency links.
23545 - The 'EXTENDCIRCUIT' control port command can now be used with
23546 a circ id of 0 and no path. This feature will cause Tor to build
23547 a new 'fast' general purpose circuit using its own path selection
23549 - Added a BUILDTIMEOUT_SET controller event to describe changes
23550 to the circuit build timeout.
23551 - Future-proof the controller protocol a bit by ignoring keyword
23552 arguments we do not recognize.
23553 - Expand homedirs passed to tor-checkkey. This should silence a
23554 coverity complaint about passing a user-supplied string into
23555 open() without checking it.
23558 Changes in version 0.2.1.25 - 2010-03-16
23559 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23560 prevent relays from guessing their IP address correctly. It also fixes
23561 several minor potential security bugs.
23564 - Fix a regression from our patch for bug 1244 that caused relays
23565 to guess their IP address incorrectly if they didn't set Address
23566 in their torrc and/or their address fails to resolve. Bugfix on
23567 0.2.1.23; fixes bug 1269.
23568 - When freeing a session key, zero it out completely. We only zeroed
23569 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23570 patched by ekir. Fixes bug 1254.
23573 - Fix a dereference-then-NULL-check sequence when publishing
23574 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23576 - Fix another dereference-then-NULL-check sequence. Bugfix on
23577 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23578 - Make sure we treat potentially not NUL-terminated strings correctly.
23579 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23583 Changes in version 0.2.1.24 - 2010-02-21
23584 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23588 - Work correctly out-of-the-box with even more vendor-patched versions
23589 of OpenSSL. In particular, make it so Debian and OS X don't need
23590 customized patches to run/build.
23593 Changes in version 0.2.1.23 - 2010-02-13
23594 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23595 again on the latest OS X, and updates the location of a directory
23598 o Major bugfixes (performance):
23599 - We were selecting our guards uniformly at random, and then weighting
23600 which of our guards we'd use uniformly at random. This imbalance
23601 meant that Tor clients were severely limited on throughput (and
23602 probably latency too) by the first hop in their circuit. Now we
23603 select guards weighted by currently advertised bandwidth. We also
23604 automatically discard guards picked using the old algorithm. Fixes
23605 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23608 - Make Tor work again on the latest OS X: when deciding whether to
23609 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23610 version at run-time, not compile time. We need to do this because
23611 Apple doesn't update its dev-tools headers when it updates its
23612 libraries in a security patch.
23613 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23614 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23615 a memory leak when requesting a hidden service descriptor we've
23616 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23619 o Directory authority changes:
23620 - Change IP address for dannenberg (v3 directory authority), and
23621 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23622 service directory authority) from the list.
23625 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23626 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23629 - Avoid a mad rush at the beginning of each month when each client
23630 rotates half of its guards. Instead we spread the rotation out
23631 throughout the month, but we still avoid leaving a precise timestamp
23632 in the state file about when we first picked the guard. Improves
23633 over the behavior introduced in 0.1.2.17.
23636 Changes in version 0.2.2.8-alpha - 2010-01-26
23637 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
23638 causing bridge relays to disappear. If you're running a bridge,
23642 - Fix a memory corruption bug on bridges that occurred during the
23643 inclusion of stats data in extra-info descriptors. Also fix the
23644 interface for geoip_get_bridge_stats* to prevent similar bugs in
23645 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
23646 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
23649 - Ignore OutboundBindAddress when connecting to localhost.
23650 Connections to localhost need to come _from_ localhost, or else
23651 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
23655 Changes in version 0.2.2.7-alpha - 2010-01-19
23656 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
23657 as laying the groundwork for further relay-side performance fixes. It
23658 also starts cleaning up client behavior with respect to the EntryNodes,
23659 ExitNodes, and StrictNodes config options.
23661 This release also rotates two directory authority keys, due to a
23662 security breach of some of the Torproject servers.
23664 o Directory authority changes:
23665 - Rotate keys (both v3 identity and relay identity) for moria1
23668 o Major features (performance):
23669 - We were selecting our guards uniformly at random, and then weighting
23670 which of our guards we'd use uniformly at random. This imbalance
23671 meant that Tor clients were severely limited on throughput (and
23672 probably latency too) by the first hop in their circuit. Now we
23673 select guards weighted by currently advertised bandwidth. We also
23674 automatically discard guards picked using the old algorithm. Fixes
23675 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23676 - When choosing which cells to relay first, relays can now favor
23677 circuits that have been quiet recently, to provide lower latency
23678 for low-volume circuits. By default, relays enable or disable this
23679 feature based on a setting in the consensus. You can override
23680 this default by using the new "CircuitPriorityHalflife" config
23681 option. Design and code by Ian Goldberg, Can Tang, and Chris
23683 - Add separate per-conn write limiting to go with the per-conn read
23684 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
23685 but never per-conn write limits.
23686 - New consensus params "bwconnrate" and "bwconnburst" to let us
23687 rate-limit client connections as they enter the network. It's
23688 controlled in the consensus so we can turn it on and off for
23689 experiments. It's starting out off. Based on proposal 163.
23691 o Major features (relay selection options):
23692 - Switch to a StrictNodes config option, rather than the previous
23693 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
23694 "StrictExcludeNodes" option.
23695 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
23696 change during a config reload, mark and discard all our origin
23697 circuits. This fix should address edge cases where we change the
23698 config options and but then choose a circuit that we created before
23700 - If EntryNodes or ExitNodes are set, be more willing to use an
23701 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
23703 - Make EntryNodes config option much more aggressive even when
23704 StrictNodes is not set. Before it would prepend your requested
23705 entrynodes to your list of guard nodes, but feel free to use others
23706 after that. Now it chooses only from your EntryNodes if any of
23707 those are available, and only falls back to others if a) they're
23708 all down and b) StrictNodes is not set.
23709 - Now we refresh your entry guards from EntryNodes at each consensus
23710 fetch -- rather than just at startup and then they slowly rot as
23711 the network changes.
23714 - Stop bridge directory authorities from answering dbg-stability.txt
23715 directory queries, which would let people fetch a list of all
23716 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23719 - Log a notice when we get a new control connection. Now it's easier
23720 for security-conscious users to recognize when a local application
23721 is knocking on their controller door. Suggested by bug 1196.
23722 - New config option "CircuitStreamTimeout" to override our internal
23723 timeout schedule for how many seconds until we detach a stream from
23724 a circuit and try a new circuit. If your network is particularly
23725 slow, you might want to set this to a number like 60.
23726 - New controller command "getinfo config-text". It returns the
23727 contents that Tor would write if you send it a SAVECONF command,
23728 so the controller can write the file to disk itself.
23729 - New options for SafeLogging to allow scrubbing only log messages
23730 generated while acting as a relay.
23731 - Ship the bridges spec file in the tarball too.
23732 - Avoid a mad rush at the beginning of each month when each client
23733 rotates half of its guards. Instead we spread the rotation out
23734 throughout the month, but we still avoid leaving a precise timestamp
23735 in the state file about when we first picked the guard. Improves
23736 over the behavior introduced in 0.1.2.17.
23738 o Minor bugfixes (compiling):
23739 - Fix compilation on OS X 10.3, which has a stub mlockall() but
23740 hides it. Bugfix on 0.2.2.6-alpha.
23741 - Fix compilation on Solaris by removing support for the
23742 DisableAllSwap config option. Solaris doesn't have an rlimit for
23743 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
23746 o Minor bugfixes (crashes):
23747 - Do not segfault when writing buffer stats when we haven't observed
23748 a single circuit to report about. Found by Fabian Lanze. Bugfix on
23750 - If we're in the pathological case where there's no exit bandwidth
23751 but there is non-exit bandwidth, or no guard bandwidth but there
23752 is non-guard bandwidth, don't crash during path selection. Bugfix
23754 - Fix an impossible-to-actually-trigger buffer overflow in relay
23755 descriptor generation. Bugfix on 0.1.0.15.
23757 o Minor bugfixes (privacy):
23758 - Fix an instance where a Tor directory mirror might accidentally
23759 log the IP address of a misbehaving Tor client. Bugfix on
23761 - Don't list Windows capabilities in relay descriptors. We never made
23762 use of them, and maybe it's a bad idea to publish them. Bugfix
23765 o Minor bugfixes (other):
23766 - Resolve an edge case in path weighting that could make us misweight
23767 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
23768 - Fix statistics on client numbers by country as seen by bridges that
23769 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
23770 intervals instead of variable 12-to-48-hour intervals.
23771 - After we free an internal connection structure, overwrite it
23772 with a different memory value than we use for overwriting a freed
23773 internal circuit structure. Should help with debugging. Suggested
23775 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
23778 o Removed features:
23779 - Remove the HSAuthorityRecordStats option that version 0 hidden
23780 service authorities could have used to track statistics of overall
23781 hidden service usage.
23784 Changes in version 0.2.1.22 - 2010-01-19
23785 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
23786 authorities -- it would tell you its whole history of bridge descriptors
23787 if you make the right directory request. This stable update also
23788 rotates two of the seven v3 directory authority keys and locations.
23790 o Directory authority changes:
23791 - Rotate keys (both v3 identity and relay identity) for moria1
23795 - Stop bridge directory authorities from answering dbg-stability.txt
23796 directory queries, which would let people fetch a list of all
23797 bridge identities they track. Bugfix on 0.2.1.6-alpha.
23800 Changes in version 0.2.1.21 - 2009-12-21
23801 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
23802 library. If you use Tor on Linux / Unix and you're getting SSL
23803 renegotiation errors, upgrading should help. We also recommend an
23804 upgrade if you're an exit relay.
23807 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23808 handshake from working unless we explicitly tell OpenSSL that we
23809 are using SSL renegotiation safely. We are, of course, but OpenSSL
23810 0.9.8l won't work unless we say we are.
23811 - Avoid crashing if the client is trying to upload many bytes and the
23812 circuit gets torn down at the same time, or if the flip side
23813 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
23816 - Do not refuse to learn about authority certs and v2 networkstatus
23817 documents that are older than the latest consensus. This bug might
23818 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23819 Spotted and fixed by xmux.
23820 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
23821 trigger platform-specific option misparsing case found by Coverity
23823 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
23824 trigger assert. Fixes bug 1173.
23827 Changes in version 0.2.2.6-alpha - 2009-11-19
23828 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
23829 support for the new lower-footprint "microdescriptor" directory design,
23830 future-proofing our consensus format against new hash functions or
23831 other changes, and an Android port. It also makes Tor compatible with
23832 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
23835 - Directory authorities can now create, vote on, and serve multiple
23836 parallel formats of directory data as part of their voting process.
23837 Partially implements Proposal 162: "Publish the consensus in
23839 - Directory authorities can now agree on and publish small summaries
23840 of router information that clients can use in place of regular
23841 server descriptors. This transition will eventually allow clients
23842 to use far less bandwidth for downloading information about the
23843 network. Begins the implementation of Proposal 158: "Clients
23844 download consensus + microdescriptors".
23845 - The directory voting system is now extensible to use multiple hash
23846 algorithms for signatures and resource selection. Newer formats
23847 are signed with SHA256, with a possibility for moving to a better
23848 hash algorithm in the future.
23849 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
23850 current and future memory pages via mlockall(). On supported
23851 platforms (modern Linux and probably BSD but not Windows or OS X),
23852 this should effectively disable any and all attempts to page out
23853 memory. This option requires that you start your Tor as root --
23854 if you use DisableAllSwap, please consider using the User option
23855 to properly reduce the privileges of your Tor.
23856 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
23857 to help Tor build correctly for Android phones.
23860 - Work around a security feature in OpenSSL 0.9.8l that prevents our
23861 handshake from working unless we explicitly tell OpenSSL that we
23862 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
23863 won't work unless we say we are.
23866 - Fix a crash bug when trying to initialize the evdns module in
23867 Libevent 2. Bugfix on 0.2.1.16-rc.
23868 - Stop logging at severity 'warn' when some other Tor client tries
23869 to establish a circuit with us using weak DH keys. It's a protocol
23870 violation, but that doesn't mean ordinary users need to hear about
23871 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
23872 - Do not refuse to learn about authority certs and v2 networkstatus
23873 documents that are older than the latest consensus. This bug might
23874 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
23875 Spotted and fixed by xmux.
23876 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
23877 - If all authorities restart at once right before a consensus vote,
23878 nobody will vote about "Running", and clients will get a consensus
23879 with no usable relays. Instead, authorities refuse to build a
23880 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
23881 - If your relay can't keep up with the number of incoming create
23882 cells, it would log one warning per failure into your logs. Limit
23883 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
23884 - Bridges now use "reject *:*" as their default exit policy. Bugfix
23885 on 0.2.0.3-alpha; fixes bug 1113.
23886 - Fix a memory leak on directory authorities during voting that was
23887 introduced in 0.2.2.1-alpha. Found via valgrind.
23890 Changes in version 0.2.1.20 - 2009-10-15
23891 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
23892 services at once, prepares for more performance improvements, and
23893 fixes a bunch of smaller bugs.
23895 The Windows and OS X bundles also include a more recent Vidalia,
23896 and switch from Privoxy to Polipo.
23898 The OS X installers are now drag and drop. It's best to un-install
23899 Tor/Vidalia and then install this new bundle, rather than upgrade. If
23900 you want to upgrade, you'll need to update the paths for Tor and Polipo
23901 in the Vidalia Settings window.
23904 - Send circuit or stream sendme cells when our window has decreased
23905 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
23906 by Karsten when testing the "reduce circuit window" performance
23907 patch. Bugfix on the 54th commit on Tor -- from July 2002,
23908 before the release of Tor 0.0.0. This is the new winner of the
23910 - Fix a remotely triggerable memory leak when a consensus document
23911 contains more than one signature from the same voter. Bugfix on
23913 - Avoid segfault in rare cases when finishing an introduction circuit
23914 as a client and finding out that we don't have an introduction key
23915 for it. Fixes bug 1073. Reported by Aaron Swartz.
23918 - Tor now reads the "circwindow" parameter out of the consensus,
23919 and uses that value for its circuit package window rather than the
23920 default of 1000 cells. Begins the implementation of proposal 168.
23922 o New directory authorities:
23923 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
23925 - Move moria1 and tonga to alternate IP addresses.
23928 - Fix a signed/unsigned compile warning in 0.2.1.19.
23929 - Fix possible segmentation fault on directory authorities. Bugfix on
23931 - Fix an extremely rare infinite recursion bug that could occur if
23932 we tried to log a message after shutting down the log subsystem.
23933 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
23934 - Fix an obscure bug where hidden services on 64-bit big-endian
23935 systems might mis-read the timestamp in v3 introduce cells, and
23936 refuse to connect back to the client. Discovered by "rotor".
23937 Bugfix on 0.2.1.6-alpha.
23938 - We were triggering a CLOCK_SKEW controller status event whenever
23939 we connect via the v2 connection protocol to any relay that has
23940 a wrong clock. Instead, we should only inform the controller when
23941 it's a trusted authority that claims our clock is wrong. Bugfix
23942 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
23943 - We were telling the controller about CHECKING_REACHABILITY and
23944 REACHABILITY_FAILED status events whenever we launch a testing
23945 circuit or notice that one has failed. Instead, only tell the
23946 controller when we want to inform the user of overall success or
23947 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
23949 - Don't warn when we're using a circuit that ends with a node
23950 excluded in ExcludeExitNodes, but the circuit is not used to access
23951 the outside world. This should help fix bug 1090. Bugfix on
23953 - Work around a small memory leak in some versions of OpenSSL that
23954 stopped the memory used by the hostname TLS extension from being
23958 - Add a "getinfo status/accepted-server-descriptor" controller
23959 command, which is the recommended way for controllers to learn
23960 whether our server descriptor has been successfully received by at
23961 least on directory authority. Un-recommend good-server-descriptor
23962 getinfo and status events until we have a better design for them.
23965 Changes in version 0.2.2.5-alpha - 2009-10-11
23966 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
23969 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
23971 o Directory authorities:
23972 - Temporarily (just for this release) move dizum to an alternate
23976 Changes in version 0.2.2.4-alpha - 2009-10-10
23977 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
23978 introduces a new unit test framework, shifts directry authority
23979 addresses around to reduce the impact from recent blocking events,
23980 and fixes a few smaller bugs.
23983 - Fix several more asserts in the circuit_build_times code, for
23984 example one that causes Tor to fail to start once we have
23985 accumulated 5000 build times in the state file. Bugfixes on
23986 0.2.2.2-alpha; fixes bug 1108.
23988 o New directory authorities:
23989 - Move moria1 and Tonga to alternate IP addresses.
23992 - Log SSL state transitions at debug level during handshake, and
23993 include SSL states in error messages. This may help debug future
23994 SSL handshake issues.
23995 - Add a new "Handshake" log domain for activities that happen
23996 during the TLS handshake.
23997 - Revert to the "June 3 2009" ip-to-country file. The September one
23998 seems to have removed most US IP addresses.
23999 - Directory authorities now reject Tor relays with versions less than
24000 0.1.2.14. This step cuts out four relays from the current network,
24001 none of which are very big.
24004 - Fix a couple of smaller issues with gathering statistics. Bugfixes
24006 - Fix two memory leaks in the error case of
24007 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
24008 - Don't count one-hop circuits when we're estimating how long it
24009 takes circuits to build on average. Otherwise we'll set our circuit
24010 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
24011 - Directory authorities no longer change their opinion of, or vote on,
24012 whether a router is Running, unless they have themselves been
24013 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
24016 o Code simplifications and refactoring:
24017 - Revise our unit tests to use the "tinytest" framework, so we
24018 can run tests in their own processes, have smarter setup/teardown
24019 code, and so on. The unit test code has moved to its own
24020 subdirectory, and has been split into multiple modules.
24023 Changes in version 0.2.2.3-alpha - 2009-09-23
24024 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
24027 - Fix an overzealous assert in our new circuit build timeout code.
24028 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
24031 - If the networkstatus consensus tells us that we should use a
24032 negative circuit package window, ignore it. Otherwise we'll
24033 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
24036 Changes in version 0.2.2.2-alpha - 2009-09-21
24037 Tor 0.2.2.2-alpha introduces our latest performance improvement for
24038 clients: Tor tracks the average time it takes to build a circuit, and
24039 avoids using circuits that take too long to build. For fast connections,
24040 this feature can cut your expected latency in half. For slow or flaky
24041 connections, it could ruin your Tor experience. Let us know if it does!
24044 - Tor now tracks how long it takes to build client-side circuits
24045 over time, and adapts its timeout to local network performance.
24046 Since a circuit that takes a long time to build will also provide
24047 bad performance, we get significant latency improvements by
24048 discarding the slowest 20% of circuits. Specifically, Tor creates
24049 circuits more aggressively than usual until it has enough data
24050 points for a good timeout estimate. Implements proposal 151.
24051 We are especially looking for reports (good and bad) from users with
24052 both EDGE and broadband connections that can move from broadband
24053 to EDGE and find out if the build-time data in the .tor/state gets
24054 reset without loss of Tor usability. You should also see a notice
24055 log message telling you that Tor has reset its timeout.
24056 - Directory authorities can now vote on arbitrary integer values as
24057 part of the consensus process. This is designed to help set
24058 network-wide parameters. Implements proposal 167.
24059 - Tor now reads the "circwindow" parameter out of the consensus,
24060 and uses that value for its circuit package window rather than the
24061 default of 1000 cells. Begins the implementation of proposal 168.
24064 - Fix a remotely triggerable memory leak when a consensus document
24065 contains more than one signature from the same voter. Bugfix on
24069 - Fix an extremely rare infinite recursion bug that could occur if
24070 we tried to log a message after shutting down the log subsystem.
24071 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24072 - Fix parsing for memory or time units given without a space between
24073 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
24074 - A networkstatus vote must contain exactly one signature. Spec
24075 conformance issue. Bugfix on 0.2.0.3-alpha.
24076 - Fix an obscure bug where hidden services on 64-bit big-endian
24077 systems might mis-read the timestamp in v3 introduce cells, and
24078 refuse to connect back to the client. Discovered by "rotor".
24079 Bugfix on 0.2.1.6-alpha.
24080 - We were triggering a CLOCK_SKEW controller status event whenever
24081 we connect via the v2 connection protocol to any relay that has
24082 a wrong clock. Instead, we should only inform the controller when
24083 it's a trusted authority that claims our clock is wrong. Bugfix
24084 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24085 - We were telling the controller about CHECKING_REACHABILITY and
24086 REACHABILITY_FAILED status events whenever we launch a testing
24087 circuit or notice that one has failed. Instead, only tell the
24088 controller when we want to inform the user of overall success or
24089 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24091 - Don't warn when we're using a circuit that ends with a node
24092 excluded in ExcludeExitNodes, but the circuit is not used to access
24093 the outside world. This should help fix bug 1090, but more problems
24094 remain. Bugfix on 0.2.1.6-alpha.
24095 - Work around a small memory leak in some versions of OpenSSL that
24096 stopped the memory used by the hostname TLS extension from being
24098 - Make our 'torify' script more portable; if we have only one of
24099 'torsocks' or 'tsocks' installed, don't complain to the user;
24100 and explain our warning about tsocks better.
24103 - Add a "getinfo status/accepted-server-descriptor" controller
24104 command, which is the recommended way for controllers to learn
24105 whether our server descriptor has been successfully received by at
24106 least on directory authority. Un-recommend good-server-descriptor
24107 getinfo and status events until we have a better design for them.
24108 - Update to the "September 4 2009" ip-to-country file.
24111 Changes in version 0.2.2.1-alpha - 2009-08-26
24112 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
24113 Tor clients to bootstrap on networks where only port 80 is reachable,
24114 makes it more straightforward to support hardware crypto accelerators,
24115 and starts the groundwork for gathering stats safely at relays.
24118 - Start the process of disabling ".exit" address notation, since it
24119 can be used for a variety of esoteric application-level attacks
24120 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
24123 o New directory authorities:
24124 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24128 - New AccelName and AccelDir options add support for dynamic OpenSSL
24129 hardware crypto acceleration engines.
24130 - Tor now supports tunneling all of its outgoing connections over
24131 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
24132 configuration options. Code by Christopher Davis.
24135 - Send circuit or stream sendme cells when our window has decreased
24136 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24137 by Karsten when testing the "reduce circuit window" performance
24138 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24139 before the release of Tor 0.0.0. This is the new winner of the
24142 o New options for gathering stats safely:
24143 - Directory mirrors that set "DirReqStatistics 1" write statistics
24144 about directory requests to disk every 24 hours. As compared to the
24145 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
24146 1) stats are written to disk exactly every 24 hours; 2) estimated
24147 shares of v2 and v3 requests are determined as mean values, not at
24148 the end of a measurement period; 3) unresolved requests are listed
24149 with country code '??'; 4) directories also measure download times.
24150 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
24151 number of exit streams and transferred bytes per port to disk every
24153 - Relays that set "CellStatistics 1" write statistics on how long
24154 cells spend in their circuit queues to disk every 24 hours.
24155 - Entry nodes that set "EntryStatistics 1" write statistics on the
24156 rough number and origins of connecting clients to disk every 24
24158 - Relays that write any of the above statistics to disk and set
24159 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
24160 their extra-info documents.
24163 - New --digests command-line switch to output the digests of the
24164 source files Tor was built with.
24165 - The "torify" script now uses torsocks where available.
24166 - The memarea code now uses a sentinel value at the end of each area
24167 to make sure nothing writes beyond the end of an area. This might
24168 help debug some conceivable causes of bug 930.
24169 - Time and memory units in the configuration file can now be set to
24170 fractional units. For example, "2.5 GB" is now a valid value for
24172 - Certain Tor clients (such as those behind check.torproject.org) may
24173 want to fetch the consensus in an extra early manner. To enable this
24174 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
24175 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
24176 as only certain clients who must have this information sooner should
24178 - Instead of adding the svn revision to the Tor version string, report
24179 the git commit (when we're building from a git checkout).
24182 - If any of the v3 certs we download are unparseable, we should
24183 actually notice the failure so we don't retry indefinitely. Bugfix
24184 on 0.2.0.x; reported by "rotator".
24185 - If the cached cert file is unparseable, warn but don't exit.
24186 - Fix possible segmentation fault on directory authorities. Bugfix on
24188 - When Tor fails to parse a descriptor of any kind, dump it to disk.
24189 Might help diagnosing bug 1051.
24191 o Deprecated and removed features:
24192 - The controller no longer accepts the old obsolete "addr-mappings/"
24193 or "unregistered-servers-" GETINFO values.
24194 - Hidden services no longer publish version 0 descriptors, and clients
24195 do not request or use version 0 descriptors. However, the old hidden
24196 service authorities still accept and serve version 0 descriptors
24197 when contacted by older hidden services/clients.
24198 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
24199 always on; using them is necessary for correct forward-compatible
24201 - Remove support for .noconnect style addresses. Nobody was using
24202 them, and they provided another avenue for detecting Tor users
24203 via application-level web tricks.
24205 o Packaging changes:
24206 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
24207 installer bundles. See
24208 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
24209 for details of what's new in Vidalia 0.2.3.
24210 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
24211 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
24212 configuration file, rather than the old Privoxy.
24213 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
24214 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
24215 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
24216 better compatibility with OS X 10.6, aka Snow Leopard.
24217 - OS X Vidalia Bundle: The multi-package installer is now replaced
24218 by a simple drag and drop to the /Applications folder. This change
24219 occurred with the upgrade to Vidalia 0.2.3.
24222 Changes in version 0.2.1.19 - 2009-07-28
24223 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
24224 services on Tor 0.2.1.3-alpha through 0.2.1.18.
24227 - Make accessing hidden services on 0.2.1.x work right again.
24228 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
24229 part of patch provided by "optimist".
24232 - When a relay/bridge is writing out its identity key fingerprint to
24233 the "fingerprint" file and to its logs, write it without spaces. Now
24234 it will look like the fingerprints in our bridges documentation,
24235 and confuse fewer users.
24238 - Relays no longer publish a new server descriptor if they change
24239 their MaxAdvertisedBandwidth config option but it doesn't end up
24240 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
24241 fixes bug 1026. Patch from Sebastian.
24242 - Avoid leaking memory every time we get a create cell but we have
24243 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
24244 fixes bug 1034. Reported by BarkerJr.
24247 Changes in version 0.2.1.18 - 2009-07-24
24248 Tor 0.2.1.18 lays the foundations for performance improvements,
24249 adds status events to help users diagnose bootstrap problems, adds
24250 optional authentication/authorization for hidden services, fixes a
24251 variety of potential anonymity problems, and includes a huge pile of
24252 other features and bug fixes.
24255 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
24258 Changes in version 0.2.1.17-rc - 2009-07-07
24259 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
24260 candidate for the 0.2.1.x series. It lays the groundwork for further
24261 client performance improvements, and also fixes a big bug with directory
24262 authorities that were causing them to assign Guard and Stable flags
24265 The Windows bundles also finally include the geoip database that we
24266 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
24267 should actually install Torbutton rather than giving you a cryptic
24268 failure message (oops).
24271 - Clients now use the bandwidth values in the consensus, rather than
24272 the bandwidth values in each relay descriptor. This approach opens
24273 the door to more accurate bandwidth estimates once the directory
24274 authorities start doing active measurements. Implements more of
24278 - When Tor clients restart after 1-5 days, they discard all their
24279 cached descriptors as too old, but they still use the cached
24280 consensus document. This approach is good for robustness, but
24281 bad for performance: since they don't know any bandwidths, they
24282 end up choosing at random rather than weighting their choice by
24283 speed. Fixed by the above feature of putting bandwidths in the
24284 consensus. Bugfix on 0.2.0.x.
24285 - Directory authorities were neglecting to mark relays down in their
24286 internal histories if the relays fall off the routerlist without
24287 ever being found unreachable. So there were relays in the histories
24288 that haven't been seen for eight months, and are listed as being
24289 up for eight months. This wreaked havoc on the "median wfu"
24290 and "median mtbf" calculations, in turn making Guard and Stable
24291 flags very wrong, hurting network performance. Fixes bugs 696 and
24292 969. Bugfix on 0.2.0.6-alpha.
24295 - Serve the DirPortFrontPage page even when we have been approaching
24296 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
24297 - The control port would close the connection before flushing long
24298 replies, such as the network consensus, if a QUIT command was issued
24299 before the reply had completed. Now, the control port flushes all
24300 pending replies before closing the connection. Also fixed a spurious
24301 warning when a QUIT command is issued after a malformed or rejected
24302 AUTHENTICATE command, but before the connection was closed. Patch
24303 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
24304 - When we can't find an intro key for a v2 hidden service descriptor,
24305 fall back to the v0 hidden service descriptor and log a bug message.
24306 Workaround for bug 1024.
24307 - Fix a log message that did not respect the SafeLogging option.
24311 - If we're a relay and we change our IP address, be more verbose
24312 about the reason that made us change. Should help track down
24313 further bugs for relays on dynamic IP addresses.
24316 Changes in version 0.2.0.35 - 2009-06-24
24318 - Avoid crashing in the presence of certain malformed descriptors.
24319 Found by lark, and by automated fuzzing.
24320 - Fix an edge case where a malicious exit relay could convince a
24321 controller that the client's DNS question resolves to an internal IP
24322 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24325 - Finally fix the bug where dynamic-IP relays disappear when their
24326 IP address changes: directory mirrors were mistakenly telling
24327 them their old address if they asked via begin_dir, so they
24328 never got an accurate answer about their new address, so they
24329 just vanished after a day. For belt-and-suspenders, relays that
24330 don't set Address in their config now avoid using begin_dir for
24331 all direct connections. Should fix bugs 827, 883, and 900.
24332 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24333 that would occur on some exit nodes when DNS failures and timeouts
24334 occurred in certain patterns. Fix for bug 957.
24337 - When starting with a cache over a few days old, do not leak
24338 memory for the obsolete router descriptors in it. Bugfix on
24339 0.2.0.33; fixes bug 672.
24340 - Hidden service clients didn't use a cached service descriptor that
24341 was older than 15 minutes, but wouldn't fetch a new one either,
24342 because there was already one in the cache. Now, fetch a v2
24343 descriptor unless the same descriptor was added to the cache within
24344 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24347 Changes in version 0.2.1.16-rc - 2009-06-20
24348 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
24349 a bunch of minor bugs.
24352 - Fix an edge case where a malicious exit relay could convince a
24353 controller that the client's DNS question resolves to an internal IP
24354 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24356 o Major performance improvements (on 0.2.0.x):
24357 - Disable and refactor some debugging checks that forced a linear scan
24358 over the whole server-side DNS cache. These accounted for over 50%
24359 of CPU time on a relatively busy exit node's gprof profile. Found
24361 - Disable some debugging checks that appeared in exit node profile
24365 - Update to the "June 3 2009" ip-to-country file.
24366 - Do not have tor-resolve automatically refuse all .onion addresses;
24367 if AutomapHostsOnResolve is set in your torrc, this will work fine.
24369 o Minor bugfixes (on 0.2.0.x):
24370 - Log correct error messages for DNS-related network errors on
24372 - Fix a race condition that could cause crashes or memory corruption
24373 when running as a server with a controller listening for log
24375 - Avoid crashing when we have a policy specified in a DirPolicy or
24376 SocksPolicy or ReachableAddresses option with ports set on it,
24377 and we re-load the policy. May fix bug 996.
24378 - Hidden service clients didn't use a cached service descriptor that
24379 was older than 15 minutes, but wouldn't fetch a new one either,
24380 because there was already one in the cache. Now, fetch a v2
24381 descriptor unless the same descriptor was added to the cache within
24382 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24384 o Minor bugfixes (on 0.2.1.x):
24385 - Don't warn users about low port and hibernation mix when they
24386 provide a *ListenAddress directive to fix that. Bugfix on
24388 - When switching back and forth between bridge mode, do not start
24389 gathering GeoIP data until two hours have passed.
24390 - Do not complain that the user has requested an excluded node as
24391 an exit when the node is not really an exit. This could happen
24392 because the circuit was for testing, or an introduction point.
24396 Changes in version 0.2.1.15-rc - 2009-05-25
24397 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
24398 series. It fixes a major bug on fast exit relays, as well as a variety
24399 of more minor bugs.
24401 o Major bugfixes (on 0.2.0.x):
24402 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24403 that would occur on some exit nodes when DNS failures and timeouts
24404 occurred in certain patterns. Fix for bug 957.
24406 o Minor bugfixes (on 0.2.0.x):
24407 - Actually return -1 in the error case for read_bandwidth_usage().
24408 Harmless bug, since we currently don't care about the return value
24409 anywhere. Bugfix on 0.2.0.9-alpha.
24410 - Provide a more useful log message if bug 977 (related to buffer
24411 freelists) ever reappears, and do not crash right away.
24412 - Fix an assertion failure on 64-bit platforms when we allocated
24413 memory right up to the end of a memarea, then realigned the memory
24414 one step beyond the end. Fixes a possible cause of bug 930.
24415 - Protect the count of open sockets with a mutex, so we can't
24416 corrupt it when two threads are closing or opening sockets at once.
24417 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
24418 - Don't allow a bridge to publish its router descriptor to a
24419 non-bridge directory authority. Fixes part of bug 932.
24420 - When we change to or from being a bridge, reset our counts of
24421 client usage by country. Fixes bug 932.
24422 - Fix a bug that made stream bandwidth get misreported to the
24424 - Stop using malloc_usable_size() to use more area than we had
24425 actually allocated: it was safe, but made valgrind really unhappy.
24426 - Fix a memory leak when v3 directory authorities load their keys
24427 and cert from disk. Bugfix on 0.2.0.1-alpha.
24429 o Minor bugfixes (on 0.2.1.x):
24430 - Fix use of freed memory when deciding to mark a non-addable
24431 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24434 Changes in version 0.2.1.14-rc - 2009-04-12
24435 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24436 series. It begins fixing some major performance problems, and also
24437 finally addresses the bug that was causing relays on dynamic IP
24438 addresses to fall out of the directory.
24441 - Clients replace entry guards that were chosen more than a few months
24442 ago. This change should significantly improve client performance,
24443 especially once more people upgrade, since relays that have been
24444 a guard for a long time are currently overloaded.
24446 o Major bugfixes (on 0.2.0):
24447 - Finally fix the bug where dynamic-IP relays disappear when their
24448 IP address changes: directory mirrors were mistakenly telling
24449 them their old address if they asked via begin_dir, so they
24450 never got an accurate answer about their new address, so they
24451 just vanished after a day. For belt-and-suspenders, relays that
24452 don't set Address in their config now avoid using begin_dir for
24453 all direct connections. Should fix bugs 827, 883, and 900.
24454 - Relays were falling out of the networkstatus consensus for
24455 part of a day if they changed their local config but the
24456 authorities discarded their new descriptor as "not sufficiently
24457 different". Now directory authorities accept a descriptor as changed
24458 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24459 patch by Sebastian.
24460 - Avoid crashing in the presence of certain malformed descriptors.
24461 Found by lark, and by automated fuzzing.
24464 - When generating circuit events with verbose nicknames for
24465 controllers, try harder to look up nicknames for routers on a
24466 circuit. (Previously, we would look in the router descriptors we had
24467 for nicknames, but not in the consensus.) Partial fix for bug 941.
24468 - If the bridge config line doesn't specify a port, assume 443.
24469 This makes bridge lines a bit smaller and easier for users to
24471 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24472 bytes (aka 20KB/s), to match our documentation. Also update
24473 directory authorities so they always assign the Fast flag to relays
24474 with 20KB/s of capacity. Now people running relays won't suddenly
24475 find themselves not seeing any use, if the network gets faster
24477 - Update to the "April 3 2009" ip-to-country file.
24480 - Avoid trying to print raw memory to the logs when we decide to
24481 give up on downloading a given relay descriptor. Bugfix on
24483 - In tor-resolve, when the Tor client to use is specified by
24484 <hostname>:<port>, actually use the specified port rather than
24485 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24486 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24487 - When starting with a cache over a few days old, do not leak
24488 memory for the obsolete router descriptors in it. Bugfix on
24490 - Avoid double-free on list of successfully uploaded hidden
24491 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24492 - Change memarea_strndup() implementation to work even when
24493 duplicating a string at the end of a page. This bug was
24494 harmless for now, but could have meant crashes later. Fix by
24495 lark. Bugfix on 0.2.1.1-alpha.
24496 - Limit uploaded directory documents to be 16M rather than 500K.
24497 The directory authorities were refusing v3 consensus votes from
24498 other authorities, since the votes are now 504K. Fixes bug 959;
24499 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24500 - Directory authorities should never send a 503 "busy" response to
24501 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24505 Changes in version 0.2.1.13-alpha - 2009-03-09
24506 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24507 cleanups. We're finally getting close to a release candidate.
24510 - Correctly update the list of which countries we exclude as
24511 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24512 lark. Bugfix on 0.2.1.6-alpha.
24514 o Minor bugfixes (on 0.2.0.x and earlier):
24515 - Automatically detect MacOSX versions earlier than 10.4.0, and
24516 disable kqueue from inside Tor when running with these versions.
24517 We previously did this from the startup script, but that was no
24518 help to people who didn't use the startup script. Resolves bug 863.
24519 - When we had picked an exit node for a connection, but marked it as
24520 "optional", and it turned out we had no onion key for the exit,
24521 stop wanting that exit and try again. This situation may not
24522 be possible now, but will probably become feasible with proposal
24523 158. Spotted by rovv. Fixes another case of bug 752.
24524 - Clients no longer cache certificates for authorities they do not
24525 recognize. Bugfix on 0.2.0.9-alpha.
24526 - When we can't transmit a DNS request due to a network error, retry
24527 it after a while, and eventually transmit a failing response to
24528 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24529 - If the controller claimed responsibility for a stream, but that
24530 stream never finished making its connection, it would live
24531 forever in circuit_wait state. Now we close it after SocksTimeout
24532 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24533 - Drop begin cells to a hidden service if they come from the middle
24534 of a circuit. Patch from lark.
24535 - When we erroneously receive two EXTEND cells for the same circuit
24536 ID on the same connection, drop the second. Patch from lark.
24537 - Fix a crash that occurs on exit nodes when a nameserver request
24538 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24539 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24541 - Do not assume that a stack-allocated character array will be
24542 64-bit aligned on platforms that demand that uint64_t access is
24543 aligned. Possible fix for bug 604.
24544 - Parse dates and IPv4 addresses in a locale- and libc-independent
24545 manner, to avoid platform-dependent behavior on malformed input.
24546 - Build correctly when configured to build outside the main source
24547 path. Patch from Michael Gold.
24548 - We were already rejecting relay begin cells with destination port
24549 of 0. Now also reject extend cells with destination port or address
24550 of 0. Suggested by lark.
24552 o Minor bugfixes (on 0.2.1.x):
24553 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24554 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24555 - If we're an exit node, scrub the IP address to which we are exiting
24556 in the logs. Bugfix on 0.2.1.8-alpha.
24559 - On Linux, use the prctl call to re-enable core dumps when the user
24561 - New controller event NEWCONSENSUS that lists the networkstatus
24562 lines for every recommended relay. Now controllers like Torflow
24563 can keep up-to-date on which relays they should be using.
24564 - Update to the "February 26 2009" ip-to-country file.
24567 Changes in version 0.2.0.34 - 2009-02-08
24568 Tor 0.2.0.34 features several more security-related fixes. You should
24569 upgrade, especially if you run an exit relay (remote crash) or a
24570 directory authority (remote infinite loop), or you're on an older
24571 (pre-XP) or not-recently-patched Windows (remote exploit).
24573 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24574 have many known flaws, and nobody should be using them. You should
24575 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24576 stop using those packages and upgrade anyway.
24579 - Fix an infinite-loop bug on handling corrupt votes under certain
24580 circumstances. Bugfix on 0.2.0.8-alpha.
24581 - Fix a temporary DoS vulnerability that could be performed by
24582 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24583 - Avoid a potential crash on exit nodes when processing malformed
24584 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24585 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24586 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24589 - Fix compilation on systems where time_t is a 64-bit integer.
24590 Patch from Matthias Drochner.
24591 - Don't consider expiring already-closed client connections. Fixes
24592 bug 893. Bugfix on 0.0.2pre20.
24595 Changes in version 0.2.1.12-alpha - 2009-02-08
24596 Tor 0.2.1.12-alpha features several more security-related fixes. You
24597 should upgrade, especially if you run an exit relay (remote crash) or
24598 a directory authority (remote infinite loop), or you're on an older
24599 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24600 includes a big pile of minor bugfixes and cleanups.
24603 - Fix an infinite-loop bug on handling corrupt votes under certain
24604 circumstances. Bugfix on 0.2.0.8-alpha.
24605 - Fix a temporary DoS vulnerability that could be performed by
24606 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24607 - Avoid a potential crash on exit nodes when processing malformed
24608 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24611 - Let controllers actually ask for the "clients_seen" event for
24612 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24613 reported by Matt Edman.
24614 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24616 - Fix a bug in address parsing that was preventing bridges or hidden
24617 service targets from being at IPv6 addresses.
24618 - Solve a bug that kept hardware crypto acceleration from getting
24619 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24621 - Remove a bash-ism from configure.in to build properly on non-Linux
24622 platforms. Bugfix on 0.2.1.1-alpha.
24623 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24624 headers. Bugfix on 0.2.0.10-alpha.
24625 - Don't consider expiring already-closed client connections. Fixes
24626 bug 893. Bugfix on 0.0.2pre20.
24627 - Fix another interesting corner-case of bug 891 spotted by rovv:
24628 Previously, if two hosts had different amounts of clock drift, and
24629 one of them created a new connection with just the wrong timing,
24630 the other might decide to deprecate the new connection erroneously.
24631 Bugfix on 0.1.1.13-alpha.
24632 - Resolve a very rare crash bug that could occur when the user forced
24633 a nameserver reconfiguration during the middle of a nameserver
24634 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
24635 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
24636 Bugfix on 0.2.1.7-alpha.
24637 - If we're using bridges and our network goes away, be more willing
24638 to forgive our bridges and try again when we get an application
24639 request. Bugfix on 0.2.0.x.
24642 - Support platforms where time_t is 64 bits long. (Congratulations,
24643 NetBSD!) Patch from Matthias Drochner.
24644 - Add a 'getinfo status/clients-seen' controller command, in case
24645 controllers want to hear clients_seen events but connect late.
24648 - Disable GCC's strict alias optimization by default, to avoid the
24649 likelihood of its introducing subtle bugs whenever our code violates
24650 the letter of C99's alias rules.
24653 Changes in version 0.2.0.33 - 2009-01-21
24654 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24655 useful to users. It also finally fixes a bug where a relay or client
24656 that's been off for many days would take a long time to bootstrap.
24658 This update also fixes an important security-related bug reported by
24659 Ilja van Sprundel. You should upgrade. (We'll send out more details
24660 about the bug once people have had some time to upgrade.)
24663 - Fix a heap-corruption bug that may be remotely triggerable on
24664 some platforms. Reported by Ilja van Sprundel.
24667 - When a stream at an exit relay is in state "resolving" or
24668 "connecting" and it receives an "end" relay cell, the exit relay
24669 would silently ignore the end cell and not close the stream. If
24670 the client never closes the circuit, then the exit relay never
24671 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24672 reported by "wood".
24673 - When sending CREATED cells back for a given circuit, use a 64-bit
24674 connection ID to find the right connection, rather than an addr:port
24675 combination. Now that we can have multiple OR connections between
24676 the same ORs, it is no longer possible to use addr:port to uniquely
24677 identify a connection.
24678 - Bridge relays that had DirPort set to 0 would stop fetching
24679 descriptors shortly after startup, and then briefly resume
24680 after a new bandwidth test and/or after publishing a new bridge
24681 descriptor. Bridge users that try to bootstrap from them would
24682 get a recent networkstatus but would get descriptors from up to
24683 18 hours earlier, meaning most of the descriptors were obsolete
24684 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24685 - Prevent bridge relays from serving their 'extrainfo' document
24686 to anybody who asks, now that extrainfo docs include potentially
24687 sensitive aggregated client geoip summaries. Bugfix on
24689 - If the cached networkstatus consensus is more than five days old,
24690 discard it rather than trying to use it. In theory it could be
24691 useful because it lists alternate directory mirrors, but in practice
24692 it just means we spend many minutes trying directory mirrors that
24693 are long gone from the network. Also discard router descriptors as
24694 we load them if they are more than five days old, since the onion
24695 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24698 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24699 could make gcc generate non-functional binary search code. Bugfix
24701 - Build correctly on platforms without socklen_t.
24702 - Compile without warnings on solaris.
24703 - Avoid potential crash on internal error during signature collection.
24704 Fixes bug 864. Patch from rovv.
24705 - Correct handling of possible malformed authority signing key
24706 certificates with internal signature types. Fixes bug 880.
24707 Bugfix on 0.2.0.3-alpha.
24708 - Fix a hard-to-trigger resource leak when logging credential status.
24710 - When we can't initialize DNS because the network is down, do not
24711 automatically stop Tor from starting. Instead, we retry failed
24712 dns_init() every 10 minutes, and change the exit policy to reject
24713 *:* until one succeeds. Fixes bug 691.
24714 - Use 64 bits instead of 32 bits for connection identifiers used with
24715 the controller protocol, to greatly reduce risk of identifier reuse.
24716 - When we're choosing an exit node for a circuit, and we have
24717 no pending streams, choose a good general exit rather than one that
24718 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
24719 - Fix another case of assuming, when a specific exit is requested,
24720 that we know more than the user about what hosts it allows.
24721 Fixes one case of bug 752. Patch from rovv.
24722 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24723 seconds. Warn the user if lower values are given in the
24724 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24725 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24726 user if lower values are given in the configuration. Bugfix on
24727 0.1.1.17-rc. Patch by Sebastian.
24728 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
24729 the cache because we already had a v0 descriptor with the same ID.
24730 Bugfix on 0.2.0.18-alpha.
24731 - Fix a race condition when freeing keys shared between main thread
24732 and CPU workers that could result in a memory leak. Bugfix on
24733 0.1.0.1-rc. Fixes bug 889.
24734 - Send a valid END cell back when a client tries to connect to a
24735 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
24736 840. Patch from rovv.
24737 - Check which hops rendezvous stream cells are associated with to
24738 prevent possible guess-the-streamid injection attacks from
24739 intermediate hops. Fixes another case of bug 446. Based on patch
24741 - If a broken client asks a non-exit router to connect somewhere,
24742 do not even do the DNS lookup before rejecting the connection.
24743 Fixes another case of bug 619. Patch from rovv.
24744 - When a relay gets a create cell it can't decrypt (e.g. because it's
24745 using the wrong onion key), we were dropping it and letting the
24746 client time out. Now actually answer with a destroy cell. Fixes
24747 bug 904. Bugfix on 0.0.2pre8.
24749 o Minor bugfixes (hidden services):
24750 - Do not throw away existing introduction points on SIGHUP. Bugfix on
24751 0.0.6pre1. Patch by Karsten. Fixes bug 874.
24754 - Report the case where all signatures in a detached set are rejected
24755 differently than the case where there is an error handling the
24757 - When we realize that another process has modified our cached
24758 descriptors, print out a more useful error message rather than
24759 triggering an assertion. Fixes bug 885. Patch from Karsten.
24760 - Implement the 0x20 hack to better resist DNS poisoning: set the
24761 case on outgoing DNS requests randomly, and reject responses that do
24762 not match the case correctly. This logic can be disabled with the
24763 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
24764 of servers that do not reliably preserve case in replies. See
24765 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
24767 - Check DNS replies for more matching fields to better resist DNS
24769 - Never use OpenSSL compression: it wastes RAM and CPU trying to
24770 compress cells, which are basically all encrypted, compressed, or
24774 Changes in version 0.2.1.11-alpha - 2009-01-20
24775 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
24776 week it will take a long time to bootstrap again" bug. It also fixes
24777 an important security-related bug reported by Ilja van Sprundel. You
24778 should upgrade. (We'll send out more details about the bug once people
24779 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 - Discard router descriptors as we load them if they are more than
24787 five days old. Otherwise if Tor is off for a long time and then
24788 starts with cached descriptors, it will try to use the onion
24789 keys in those obsolete descriptors when building circuits. Bugfix
24790 on 0.2.0.x. Fixes bug 887.
24793 - Try to make sure that the version of Libevent we're running with
24794 is binary-compatible with the one we built with. May address bug
24796 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
24797 for bug 905. Bugfix on 0.2.1.7-alpha.
24798 - Add a new --enable-local-appdata configuration switch to change
24799 the default location of the datadir on win32 from APPDATA to
24800 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
24801 entirely. Patch from coderman.
24804 - Make outbound DNS packets respect the OutboundBindAddress setting.
24805 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
24806 - When our circuit fails at the first hop (e.g. we get a destroy
24807 cell back), avoid using that OR connection anymore, and also
24808 tell all the one-hop directory requests waiting for it that they
24809 should fail. Bugfix on 0.2.1.3-alpha.
24810 - In the torify(1) manpage, mention that tsocks will leak your
24814 Changes in version 0.2.1.10-alpha - 2009-01-06
24815 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
24816 would make the bridge relay not so useful if it had DirPort set to 0,
24817 and one that could let an attacker learn a little bit of information
24818 about the bridge's users), and a bug that would cause your Tor relay
24819 to ignore a circuit create request it can't decrypt (rather than reply
24820 with an error). It also fixes a wide variety of other bugs.
24823 - If the cached networkstatus consensus is more than five days old,
24824 discard it rather than trying to use it. In theory it could
24825 be useful because it lists alternate directory mirrors, but in
24826 practice it just means we spend many minutes trying directory
24827 mirrors that are long gone from the network. Helps bug 887 a bit;
24829 - Bridge relays that had DirPort set to 0 would stop fetching
24830 descriptors shortly after startup, and then briefly resume
24831 after a new bandwidth test and/or after publishing a new bridge
24832 descriptor. Bridge users that try to bootstrap from them would
24833 get a recent networkstatus but would get descriptors from up to
24834 18 hours earlier, meaning most of the descriptors were obsolete
24835 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24836 - Prevent bridge relays from serving their 'extrainfo' document
24837 to anybody who asks, now that extrainfo docs include potentially
24838 sensitive aggregated client geoip summaries. Bugfix on
24842 - New controller event "clients_seen" to report a geoip-based summary
24843 of which countries we've seen clients from recently. Now controllers
24844 like Vidalia can show bridge operators that they're actually making
24846 - Build correctly against versions of OpenSSL 0.9.8 or later built
24847 without support for deprecated functions.
24848 - Update to the "December 19 2008" ip-to-country file.
24850 o Minor bugfixes (on 0.2.0.x):
24851 - Authorities now vote for the Stable flag for any router whose
24852 weighted MTBF is at least 5 days, regardless of the mean MTBF.
24853 - Do not remove routers as too old if we do not have any consensus
24854 document. Bugfix on 0.2.0.7-alpha.
24855 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24856 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24857 - When an exit relay resolves a stream address to a local IP address,
24858 do not just keep retrying that same exit relay over and
24859 over. Instead, just close the stream. Addresses bug 872. Bugfix
24860 on 0.2.0.32. Patch from rovv.
24861 - If a hidden service sends us an END cell, do not consider
24862 retrying the connection; just close it. Patch from rovv.
24863 - When we made bridge authorities stop serving bridge descriptors over
24864 unencrypted links, we also broke DirPort reachability testing for
24865 bridges. So bridges with a non-zero DirPort were printing spurious
24866 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
24867 - When a relay gets a create cell it can't decrypt (e.g. because it's
24868 using the wrong onion key), we were dropping it and letting the
24869 client time out. Now actually answer with a destroy cell. Fixes
24870 bug 904. Bugfix on 0.0.2pre8.
24871 - Squeeze 2-5% out of client performance (according to oprofile) by
24872 improving the implementation of some policy-manipulation functions.
24874 o Minor bugfixes (on 0.2.1.x):
24875 - Make get_interface_address() function work properly again; stop
24876 guessing the wrong parts of our address as our address.
24877 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
24878 send on that circuit. Otherwise we might violate the proposal-110
24879 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
24881 - When we're sending non-EXTEND cells to the first hop in a circuit,
24882 for example to use an encrypted directory connection, we don't need
24883 to use RELAY_EARLY cells: the first hop knows what kind of cell
24884 it is, and nobody else can even see the cell type. Conserving
24885 RELAY_EARLY cells makes it easier to cannibalize circuits like
24887 - Stop logging nameserver addresses in reverse order.
24888 - If we are retrying a directory download slowly over and over, do
24889 not automatically give up after the 254th failure. Bugfix on
24891 - Resume reporting accurate "stream end" reasons to the local control
24892 port. They were lost in the changes for Proposal 148. Bugfix on
24895 o Deprecated and removed features:
24896 - The old "tor --version --version" command, which would print out
24897 the subversion "Id" of most of the source files, is now removed. It
24898 turned out to be less useful than we'd expected, and harder to
24901 o Code simplifications and refactoring:
24902 - Change our header file guard macros to be less likely to conflict
24903 with system headers. Adam Langley noticed that we were conflicting
24904 with log.h on Android.
24905 - Tool-assisted documentation cleanup. Nearly every function or
24906 static variable in Tor should have its own documentation now.
24909 Changes in version 0.2.1.9-alpha - 2008-12-25
24910 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
24912 o New directory authorities:
24913 - gabelmoo (the authority run by Karsten Loesing) now has a new
24917 - Never use a connection with a mismatched address to extend a
24918 circuit, unless that connection is canonical. A canonical
24919 connection is one whose address is authenticated by the router's
24920 identity key, either in a NETINFO cell or in a router descriptor.
24921 - Avoid a possible memory corruption bug when receiving hidden service
24922 descriptors. Bugfix on 0.2.1.6-alpha.
24925 - Fix a logic error that would automatically reject all but the first
24926 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
24927 part of bug 813/868. Bug spotted by coderman.
24928 - When a stream at an exit relay is in state "resolving" or
24929 "connecting" and it receives an "end" relay cell, the exit relay
24930 would silently ignore the end cell and not close the stream. If
24931 the client never closes the circuit, then the exit relay never
24932 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
24933 reported by "wood".
24934 - When we can't initialize DNS because the network is down, do not
24935 automatically stop Tor from starting. Instead, retry failed
24936 dns_init() every 10 minutes, and change the exit policy to reject
24937 *:* until one succeeds. Fixes bug 691.
24940 - Give a better error message when an overzealous init script says
24941 "sudo -u username tor --user username". Makes Bug 882 easier for
24943 - When a directory authority gives us a new guess for our IP address,
24944 log which authority we used. Hopefully this will help us debug
24945 the recent complaints about bad IP address guesses.
24946 - Detect svn revision properly when we're using git-svn.
24947 - Try not to open more than one descriptor-downloading connection
24948 to an authority at once. This should reduce load on directory
24949 authorities. Fixes bug 366.
24950 - Add cross-certification to newly generated certificates, so that
24951 a signing key is enough information to look up a certificate.
24952 Partial implementation of proposal 157.
24953 - Start serving certificates by <identity digest, signing key digest>
24954 pairs. Partial implementation of proposal 157.
24955 - Clients now never report any stream end reason except 'MISC'.
24956 Implements proposal 148.
24957 - On platforms with a maximum syslog string length, truncate syslog
24958 messages to that length ourselves, rather than relying on the
24959 system to do it for us.
24960 - Optimize out calls to time(NULL) that occur for every IO operation,
24961 or for every cell. On systems where time() is a slow syscall,
24962 this fix will be slightly helpful.
24963 - Exit servers can now answer resolve requests for ip6.arpa addresses.
24964 - When we download a descriptor that we then immediately (as
24965 a directory authority) reject, do not retry downloading it right
24966 away. Should save some bandwidth on authorities. Fix for bug
24967 888. Patch by Sebastian Hahn.
24968 - When a download gets us zero good descriptors, do not notify
24969 Tor that new directory information has arrived.
24970 - Avoid some nasty corner cases in the logic for marking connections
24971 as too old or obsolete or noncanonical for circuits. Partial
24974 o Minor features (controller):
24975 - New CONSENSUS_ARRIVED event to note when a new consensus has
24976 been fetched and validated.
24977 - When we realize that another process has modified our cached
24978 descriptors file, print out a more useful error message rather
24979 than triggering an assertion. Fixes bug 885. Patch from Karsten.
24980 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
24981 controllers to prevent SIGHUP from reloading the
24982 configuration. Fixes bug 856.
24985 - Resume using the correct "REASON=" stream when telling the
24986 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
24987 - When a canonical connection appears later in our internal list
24988 than a noncanonical one for a given OR ID, always use the
24989 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
24991 - Clip the MaxCircuitDirtiness config option to a minimum of 10
24992 seconds. Warn the user if lower values are given in the
24993 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
24994 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
24995 user if lower values are given in the configuration. Bugfix on
24996 0.1.1.17-rc. Patch by Sebastian.
24997 - Fix a race condition when freeing keys shared between main thread
24998 and CPU workers that could result in a memory leak. Bugfix on
24999 0.1.0.1-rc. Fixes bug 889.
25001 o Minor bugfixes (hidden services):
25002 - Do not throw away existing introduction points on SIGHUP (bugfix on
25003 0.0.6pre1); also, do not stall hidden services because we're
25004 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
25005 by John Brooks. Patch by Karsten. Fixes bug 874.
25006 - Fix a memory leak when we decline to add a v2 rendezvous
25007 descriptor to the cache because we already had a v0 descriptor
25008 with the same ID. Bugfix on 0.2.0.18-alpha.
25010 o Deprecated and removed features:
25011 - RedirectExits has been removed. It was deprecated since
25013 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
25014 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
25015 - Cell pools are now always enabled; --disable-cell-pools is ignored.
25017 o Code simplifications and refactoring:
25018 - Rename the confusing or_is_obsolete field to the more appropriate
25019 is_bad_for_new_circs, and move it to or_connection_t where it
25021 - Move edge-only flags from connection_t to edge_connection_t: not
25022 only is this better coding, but on machines of plausible alignment,
25023 it should save 4-8 bytes per connection_t. "Every little bit helps."
25024 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
25025 for consistency; keep old option working for backward compatibility.
25026 - Simplify the code for finding connections to use for a circuit.
25029 Changes in version 0.2.1.8-alpha - 2008-12-08
25030 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
25031 builds better on unusual platforms like Solaris and old OS X, and
25032 fixes a variety of other issues.
25035 - New DirPortFrontPage option that takes an html file and publishes
25036 it as "/" on the DirPort. Now relay operators can provide a
25037 disclaimer without needing to set up a separate webserver. There's
25038 a sample disclaimer in contrib/tor-exit-notice.html.
25041 - When the client is choosing entry guards, now it selects at most
25042 one guard from a given relay family. Otherwise we could end up with
25043 all of our entry points into the network run by the same operator.
25044 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
25047 - Fix a DOS opportunity during the voting signature collection process
25048 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25049 - Fix a possible segfault when establishing an exit connection. Bugfix
25053 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
25055 - Made Tor a little less aggressive about deleting expired
25056 certificates. Partial fix for bug 854.
25057 - Stop doing unaligned memory access that generated bus errors on
25058 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
25059 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
25060 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
25061 - Make USR2 log-level switch take effect immediately. Bugfix on
25063 - If one win32 nameserver fails to get added, continue adding the
25064 rest, and don't automatically fail.
25065 - Use fcntl() for locking when flock() is not available. Should fix
25066 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
25067 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25068 could make gcc generate non-functional binary search code. Bugfix
25070 - Build correctly on platforms without socklen_t.
25071 - Avoid potential crash on internal error during signature collection.
25072 Fixes bug 864. Patch from rovv.
25073 - Do not use C's stdio library for writing to log files. This will
25074 improve logging performance by a minute amount, and will stop
25075 leaking fds when our disk is full. Fixes bug 861.
25076 - Stop erroneous use of O_APPEND in cases where we did not in fact
25077 want to re-seek to the end of a file before every last write().
25078 - Correct handling of possible malformed authority signing key
25079 certificates with internal signature types. Fixes bug 880. Bugfix
25081 - Fix a hard-to-trigger resource leak when logging credential status.
25085 - Directory mirrors no longer fetch the v1 directory or
25086 running-routers files. They are obsolete, and nobody asks for them
25087 anymore. This is the first step to making v1 authorities obsolete.
25089 o Minor features (controller):
25090 - Return circuit purposes in response to GETINFO circuit-status. Fixes
25094 Changes in version 0.2.0.32 - 2008-11-20
25095 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
25096 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25097 a smaller security flaw that might allow an attacker to access local
25098 services, further improves hidden service performance, and fixes a
25099 variety of other issues.
25102 - The "User" and "Group" config options did not clear the
25103 supplementary group entries for the Tor process. The "User" option
25104 is now more robust, and we now set the groups to the specified
25105 user's primary group. The "Group" option is now ignored. For more
25106 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25107 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25108 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
25109 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25110 consistently obeyed: if an exit relay refuses a stream because its
25111 exit policy doesn't allow it, we would remember what IP address
25112 the relay said the destination address resolves to, even if it's
25113 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25116 - Fix a DOS opportunity during the voting signature collection process
25117 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25119 o Major bugfixes (hidden services):
25120 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25121 we were failing the whole hidden service request when the v0
25122 descriptor fetch fails, even if the v2 fetch is still pending and
25123 might succeed. Similarly, if the last v2 fetch fails, we were
25124 failing the whole hidden service request even if a v0 fetch is
25125 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25126 - When extending a circuit to a hidden service directory to upload a
25127 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25128 requests failed, because the router descriptor has not been
25129 downloaded yet. In these cases, do not attempt to upload the
25130 rendezvous descriptor, but wait until the router descriptor is
25131 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
25132 descriptor from a hidden service directory for which the router
25133 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
25137 - Fix several infrequent memory leaks spotted by Coverity.
25138 - When testing for libevent functions, set the LDFLAGS variable
25139 correctly. Found by Riastradh.
25140 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25141 bootstrapping with tunneled directory connections. Bugfix on
25142 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25143 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25144 and we know that server B rejects most-but-not all connections to
25145 port 80, we would previously reject the connection. Now, we assume
25146 the user knows what they were asking for. Fixes bug 752. Bugfix
25147 on 0.0.9rc5. Diagnosed by BarkerJr.
25148 - If we overrun our per-second write limits a little, count this as
25149 having used up our write allocation for the second, and choke
25150 outgoing directory writes. Previously, we had only counted this when
25151 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
25152 Bugfix on 0.2.0.x (??).
25153 - Remove the old v2 directory authority 'lefkada' from the default
25154 list. It has been gone for many months.
25155 - Stop doing unaligned memory access that generated bus errors on
25156 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
25157 - Make USR2 log-level switch take effect immediately. Bugfix on
25160 o Minor bugfixes (controller):
25161 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
25162 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
25165 Changes in version 0.2.1.7-alpha - 2008-11-08
25166 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
25167 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25168 a smaller security flaw that might allow an attacker to access local
25169 services, adds better defense against DNS poisoning attacks on exit
25170 relays, further improves hidden service performance, and fixes a
25171 variety of other issues.
25174 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25175 consistently obeyed: if an exit relay refuses a stream because its
25176 exit policy doesn't allow it, we would remember what IP address
25177 the relay said the destination address resolves to, even if it's
25178 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25179 - The "User" and "Group" config options did not clear the
25180 supplementary group entries for the Tor process. The "User" option
25181 is now more robust, and we now set the groups to the specified
25182 user's primary group. The "Group" option is now ignored. For more
25183 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25184 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25185 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
25186 - Do not use or believe expired v3 authority certificates. Patch
25187 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
25190 - Now NodeFamily and MyFamily config options allow spaces in
25191 identity fingerprints, so it's easier to paste them in.
25192 Suggested by Lucky Green.
25193 - Implement the 0x20 hack to better resist DNS poisoning: set the
25194 case on outgoing DNS requests randomly, and reject responses that do
25195 not match the case correctly. This logic can be disabled with the
25196 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
25197 of servers that do not reliably preserve case in replies. See
25198 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25200 - Preserve case in replies to DNSPort requests in order to support
25201 the 0x20 hack for resisting DNS poisoning attacks.
25203 o Hidden service performance improvements:
25204 - When the client launches an introduction circuit, retry with a
25205 new circuit after 30 seconds rather than 60 seconds.
25206 - Launch a second client-side introduction circuit in parallel
25207 after a delay of 15 seconds (based on work by Christian Wilms).
25208 - Hidden services start out building five intro circuits rather
25209 than three, and when the first three finish they publish a service
25210 descriptor using those. Now we publish our service descriptor much
25211 faster after restart.
25214 - Minor fix in the warning messages when you're having problems
25215 bootstrapping; also, be more forgiving of bootstrap problems when
25216 we're still making incremental progress on a given bootstrap phase.
25217 - When we're choosing an exit node for a circuit, and we have
25218 no pending streams, choose a good general exit rather than one that
25219 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25220 - Send a valid END cell back when a client tries to connect to a
25221 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25222 840. Patch from rovv.
25223 - If a broken client asks a non-exit router to connect somewhere,
25224 do not even do the DNS lookup before rejecting the connection.
25225 Fixes another case of bug 619. Patch from rovv.
25226 - Fix another case of assuming, when a specific exit is requested,
25227 that we know more than the user about what hosts it allows.
25228 Fixes another case of bug 752. Patch from rovv.
25229 - Check which hops rendezvous stream cells are associated with to
25230 prevent possible guess-the-streamid injection attacks from
25231 intermediate hops. Fixes another case of bug 446. Based on patch
25233 - Avoid using a negative right-shift when comparing 32-bit
25234 addresses. Possible fix for bug 845 and bug 811.
25235 - Make the assert_circuit_ok() function work correctly on circuits that
25236 have already been marked for close.
25237 - Fix read-off-the-end-of-string error in unit tests when decoding
25238 introduction points.
25239 - Fix uninitialized size field for memory area allocation: may improve
25240 memory performance during directory parsing.
25241 - Treat duplicate certificate fetches as failures, so that we do
25242 not try to re-fetch an expired certificate over and over and over.
25243 - Do not say we're fetching a certificate when we'll in fact skip it
25244 because of a pending download.
25247 Changes in version 0.2.1.6-alpha - 2008-09-30
25248 Tor 0.2.1.6-alpha further improves performance and robustness of
25249 hidden services, starts work on supporting per-country relay selection,
25250 and fixes a variety of smaller issues.
25253 - Implement proposal 121: make it possible to build hidden services
25254 that only certain clients are allowed to connect to. This is
25255 enforced at several points, so that unauthorized clients are unable
25256 to send INTRODUCE cells to the service, or even (depending on the
25257 type of authentication) to learn introduction points. This feature
25258 raises the bar for certain kinds of active attacks against hidden
25259 services. Code by Karsten Loesing.
25260 - Relays now store and serve v2 hidden service descriptors by default,
25261 i.e., the new default value for HidServDirectoryV2 is 1. This is
25262 the last step in proposal 114, which aims to make hidden service
25263 lookups more reliable.
25264 - Start work to allow node restrictions to include country codes. The
25265 syntax to exclude nodes in a country with country code XX is
25266 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
25267 refinement to decide what config options should take priority if
25268 you ask to both use a particular node and exclude it.
25269 - Allow ExitNodes list to include IP ranges and country codes, just
25270 like the Exclude*Nodes lists. Patch from Robert Hogan.
25273 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
25274 Tor to fail to start if you had it configured to use a bridge
25275 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
25276 - When extending a circuit to a hidden service directory to upload a
25277 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25278 requests failed, because the router descriptor had not been
25279 downloaded yet. In these cases, we now wait until the router
25280 descriptor is downloaded, and then retry. Likewise, clients
25281 now skip over a hidden service directory if they don't yet have
25282 its router descriptor, rather than futilely requesting it and
25283 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
25285 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25286 we were failing the whole hidden service request when the v0
25287 descriptor fetch fails, even if the v2 fetch is still pending and
25288 might succeed. Similarly, if the last v2 fetch fails, we were
25289 failing the whole hidden service request even if a v0 fetch is
25290 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25291 - DNS replies need to have names matching their requests, but
25292 these names should be in the questions section, not necessarily
25293 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
25296 - Update to the "September 1 2008" ip-to-country file.
25297 - Allow ports 465 and 587 in the default exit policy again. We had
25298 rejected them in 0.1.0.15, because back in 2005 they were commonly
25299 misconfigured and ended up as spam targets. We hear they are better
25300 locked down these days.
25301 - Use a lockfile to make sure that two Tor processes are not
25302 simultaneously running with the same datadir.
25303 - Serve the latest v3 networkstatus consensus via the control
25304 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
25305 - Better logging about stability/reliability calculations on directory
25307 - Drop the requirement to have an open dir port for storing and
25308 serving v2 hidden service descriptors.
25309 - Directory authorities now serve a /tor/dbg-stability.txt URL to
25310 help debug WFU and MTBF calculations.
25311 - Implement most of Proposal 152: allow specialized servers to permit
25312 single-hop circuits, and clients to use those servers to build
25313 single-hop circuits when using a specialized controller. Patch
25314 from Josh Albrecht. Resolves feature request 768.
25315 - Add a -p option to tor-resolve for specifying the SOCKS port: some
25316 people find host:port too confusing.
25317 - Make TrackHostExit mappings expire a while after their last use, not
25318 after their creation. Patch from Robert Hogan.
25319 - Provide circuit purposes along with circuit events to the controller.
25322 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
25324 - Fixed some memory leaks -- some quite frequent, some almost
25325 impossible to trigger -- based on results from Coverity.
25326 - When testing for libevent functions, set the LDFLAGS variable
25327 correctly. Found by Riastradh.
25328 - Fix an assertion bug in parsing policy-related options; possible fix
25330 - Catch and report a few more bootstrapping failure cases when Tor
25331 fails to establish a TCP connection. Cleanup on 0.2.1.x.
25332 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25333 bootstrapping with tunneled directory connections. Bugfix on
25334 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25335 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25336 and we know that server B rejects most-but-not all connections to
25337 port 80, we would previously reject the connection. Now, we assume
25338 the user knows what they were asking for. Fixes bug 752. Bugfix
25339 on 0.0.9rc5. Diagnosed by BarkerJr.
25340 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
25341 service directories if they have no advertised dir port. Bugfix
25343 - If we overrun our per-second write limits a little, count this as
25344 having used up our write allocation for the second, and choke
25345 outgoing directory writes. Previously, we had only counted this when
25346 we had met our limits precisely. Fixes bug 824. Patch by rovv.
25347 Bugfix on 0.2.0.x (??).
25348 - Avoid a "0 divided by 0" calculation when calculating router uptime
25349 at directory authorities. Bugfix on 0.2.0.8-alpha.
25350 - Make DNS resolved controller events into "CLOSED", not
25351 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
25353 - Fix a bug where an unreachable relay would establish enough
25354 reachability testing circuits to do a bandwidth test -- if
25355 we already have a connection to the middle hop of the testing
25356 circuit, then it could establish the last hop by using the existing
25357 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
25358 circuits no longer use entry guards in 0.2.1.3-alpha.
25359 - If we have correct permissions on $datadir, we complain to stdout
25360 and fail to start. But dangerous permissions on
25361 $datadir/cached-status/ would cause us to open a log and complain
25362 there. Now complain to stdout and fail to start in both cases. Fixes
25363 bug 820, reported by seeess.
25364 - Remove the old v2 directory authority 'lefkada' from the default
25365 list. It has been gone for many months.
25367 o Code simplifications and refactoring:
25368 - Revise the connection_new functions so that a more typesafe variant
25369 exists. This will work better with Coverity, and let us find any
25370 actual mistakes we're making here.
25371 - Refactor unit testing logic so that dmalloc can be used sensibly
25372 with unit tests to check for memory leaks.
25373 - Move all hidden-service related fields from connection and circuit
25374 structure to substructures: this way they won't eat so much memory.
25377 Changes in version 0.2.0.31 - 2008-09-03
25378 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
25379 a big bug we're seeing where in rare cases traffic from one Tor stream
25380 gets mixed into another stream, and fixes a variety of smaller issues.
25383 - Make sure that two circuits can never exist on the same connection
25384 with the same circuit ID, even if one is marked for close. This
25385 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
25386 - Relays now reject risky extend cells: if the extend cell includes
25387 a digest of all zeroes, or asks to extend back to the relay that
25388 sent the extend cell, tear down the circuit. Ideas suggested
25390 - If not enough of our entry guards are available so we add a new
25391 one, we might use the new one even if it overlapped with the
25392 current circuit's exit relay (or its family). Anonymity bugfix
25393 pointed out by rovv.
25396 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25397 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25398 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25399 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25400 - Pick size of default geoip filename string correctly on windows.
25401 Fixes bug 806. Bugfix on 0.2.0.30.
25402 - Make the autoconf script accept the obsolete --with-ssl-dir
25403 option as an alias for the actually-working --with-openssl-dir
25404 option. Fix the help documentation to recommend --with-openssl-dir.
25405 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25406 - When using the TransPort option on OpenBSD, and using the User
25407 option to change UID and drop privileges, make sure to open
25408 /dev/pf before dropping privileges. Fixes bug 782. Patch from
25409 Christopher Davis. Bugfix on 0.1.2.1-alpha.
25410 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25411 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25412 on the client side when connecting to a hidden service. Bugfix
25413 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25414 - When closing an application-side connection because its circuit is
25415 getting torn down, generate the stream event correctly. Bugfix on
25416 0.1.2.x. Anonymous patch.
25419 Changes in version 0.2.1.5-alpha - 2008-08-31
25420 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25421 in a lot of the infrastructure for adding authorization to hidden
25422 services, lays the groundwork for having clients read their load
25423 balancing information out of the networkstatus consensus rather than
25424 the individual router descriptors, addresses two potential anonymity
25425 issues, and fixes a variety of smaller issues.
25428 - Convert many internal address representations to optionally hold
25430 - Generate and accept IPv6 addresses in many protocol elements.
25431 - Make resolver code handle nameservers located at ipv6 addresses.
25432 - Begin implementation of proposal 121 ("Client authorization for
25433 hidden services"): configure hidden services with client
25434 authorization, publish descriptors for them, and configure
25435 authorization data for hidden services at clients. The next
25436 step is to actually access hidden services that perform client
25438 - More progress toward proposal 141: Network status consensus
25439 documents and votes now contain bandwidth information for each
25440 router and a summary of that router's exit policy. Eventually this
25441 will be used by clients so that they do not have to download every
25442 known descriptor before building circuits.
25444 o Major bugfixes (on 0.2.0.x and before):
25445 - When sending CREATED cells back for a given circuit, use a 64-bit
25446 connection ID to find the right connection, rather than an addr:port
25447 combination. Now that we can have multiple OR connections between
25448 the same ORs, it is no longer possible to use addr:port to uniquely
25449 identify a connection.
25450 - Relays now reject risky extend cells: if the extend cell includes
25451 a digest of all zeroes, or asks to extend back to the relay that
25452 sent the extend cell, tear down the circuit. Ideas suggested
25454 - If not enough of our entry guards are available so we add a new
25455 one, we might use the new one even if it overlapped with the
25456 current circuit's exit relay (or its family). Anonymity bugfix
25457 pointed out by rovv.
25460 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25461 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25462 - When using the TransPort option on OpenBSD, and using the User
25463 option to change UID and drop privileges, make sure to open /dev/pf
25464 before dropping privileges. Fixes bug 782. Patch from Christopher
25465 Davis. Bugfix on 0.1.2.1-alpha.
25466 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25467 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25468 - Add a missing safe_str() call for a debug log message.
25469 - Use 64 bits instead of 32 bits for connection identifiers used with
25470 the controller protocol, to greatly reduce risk of identifier reuse.
25471 - Make the autoconf script accept the obsolete --with-ssl-dir
25472 option as an alias for the actually-working --with-openssl-dir
25473 option. Fix the help documentation to recommend --with-openssl-dir.
25474 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25477 - Rate-limit too-many-sockets messages: when they happen, they happen
25478 a lot. Resolves bug 748.
25479 - Resist DNS poisoning a little better by making sure that names in
25480 answer sections match.
25481 - Print the SOCKS5 error message string as well as the error code
25482 when a tor-resolve request fails. Patch from Jacob.
25485 Changes in version 0.2.1.4-alpha - 2008-08-04
25486 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25489 - The address part of exit policies was not correctly written
25490 to router descriptors. This generated router descriptors that failed
25491 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25493 - Tor triggered a false assert when extending a circuit to a relay
25494 but we already have a connection open to that relay. Noticed by
25495 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25498 - Fix a hidden service logging bug: in some edge cases, the router
25499 descriptor of a previously picked introduction point becomes
25500 obsolete and we need to give up on it rather than continually
25501 complaining that it has become obsolete. Observed by xiando. Bugfix
25504 o Removed features:
25505 - Take out the TestVia config option, since it was a workaround for
25506 a bug that was fixed in Tor 0.1.1.21.
25509 Changes in version 0.2.1.3-alpha - 2008-08-03
25510 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25511 infinite-length circuit attacks (see proposal 110); fixes a bug that
25512 might cause exit relays to corrupt streams they send back; allows
25513 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25514 ExcludeExitNodes config options; and fixes a big pile of bugs.
25516 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25517 - Send a bootstrap problem "warn" event on the first problem if the
25518 reason is NO_ROUTE (that is, our network is down).
25521 - Implement most of proposal 110: The first K cells to be sent
25522 along a circuit are marked as special "early" cells; only K "early"
25523 cells will be allowed. Once this code is universal, we can block
25524 certain kinds of DOS attack by requiring that EXTEND commands must
25525 be sent using an "early" cell.
25528 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25529 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25530 on the client side when connecting to a hidden service. Bugfix
25531 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25532 - Ensure that two circuits can never exist on the same connection
25533 with the same circuit ID, even if one is marked for close. This
25534 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25537 - When relays do their initial bandwidth measurement, don't limit
25538 to just our entry guards for the test circuits. Otherwise we tend
25539 to have multiple test circuits going through a single entry guard,
25540 which makes our bandwidth test less accurate. Fixes part of bug 654;
25541 patch contributed by Josh Albrecht.
25542 - Add an ExcludeExitNodes option so users can list a set of nodes
25543 that should be be excluded from the exit node position, but
25544 allowed elsewhere. Implements proposal 151.
25545 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25546 ExcludeNodes and ExcludeExitNodes lists.
25547 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25548 be more efficient. Formerly it was quadratic in the number of
25549 servers; now it should be linear. Fixes bug 509.
25550 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25551 and n_conn_id_digest fields into a separate structure that's
25552 only needed when the circuit has not yet attached to an n_conn.
25555 - Change the contrib/tor.logrotate script so it makes the new
25556 logs as "_tor:_tor" rather than the default, which is generally
25557 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25558 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25559 warnings (occasionally), but it can also cause the compiler to
25560 eliminate error-checking code. Suggested by Peter Gutmann.
25561 - When a hidden service is giving up on an introduction point candidate
25562 that was not included in the last published rendezvous descriptor,
25563 don't reschedule publication of the next descriptor. Fixes bug 763.
25565 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25566 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25567 and nobody claims to be using them. Fixes bug 754. Bugfix on
25568 0.1.0.1-rc. Patch from Christian Wilms.
25569 - Fix a small alignment and memory-wasting bug on buffer chunks.
25572 o Minor bugfixes (controller):
25573 - When closing an application-side connection because its circuit
25574 is getting torn down, generate the stream event correctly.
25575 Bugfix on 0.1.2.x. Anonymous patch.
25577 o Removed features:
25578 - Remove all backward-compatibility code to support relays running
25579 versions of Tor so old that they no longer work at all on the
25583 Changes in version 0.2.0.30 - 2008-07-15
25585 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25586 warnings (occasionally), but it can also cause the compiler to
25587 eliminate error-checking code. Suggested by Peter Gutmann.
25590 Changes in version 0.2.0.29-rc - 2008-07-08
25591 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25592 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25595 - If you have more than one bridge but don't know their keys,
25596 you would only launch a request for the descriptor of the first one
25597 on your list. (Tor considered launching requests for the others, but
25598 found that it already had a connection on the way for $0000...0000
25599 so it didn't open another.) Bugfix on 0.2.0.x.
25600 - If you have more than one bridge but don't know their keys, and the
25601 connection to one of the bridges failed, you would cancel all
25602 pending bridge connections. (After all, they all have the same
25603 digest.) Bugfix on 0.2.0.x.
25604 - When a hidden service was trying to establish an introduction point,
25605 and Tor had built circuits preemptively for such purposes, we
25606 were ignoring all the preemptive circuits and launching a new one
25607 instead. Bugfix on 0.2.0.14-alpha.
25608 - When a hidden service was trying to establish an introduction point,
25609 and Tor *did* manage to reuse one of the preemptively built
25610 circuits, it didn't correctly remember which one it used,
25611 so it asked for another one soon after, until there were no
25612 more preemptive circuits, at which point it launched one from
25613 scratch. Bugfix on 0.0.9.x.
25614 - Make directory servers include the X-Your-Address-Is: http header in
25615 their responses even for begin_dir conns. Now clients who only
25616 ever use begin_dir connections still have a way to learn their IP
25617 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25620 - Fix a macro/CPP interaction that was confusing some compilers:
25621 some GCCs don't like #if/#endif pairs inside macro arguments.
25623 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25624 Fixes bug 704; fix from Steven Murdoch.
25625 - When opening /dev/null in finish_daemonize(), do not pass the
25626 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25627 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25628 - Correctly detect transparent proxy support on Linux hosts that
25629 require in.h to be included before netfilter_ipv4.h. Patch
25631 - Disallow session resumption attempts during the renegotiation
25632 stage of the v2 handshake protocol. Clients should never be trying
25633 session resumption at this point, but apparently some did, in
25634 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
25635 found by Geoff Goodell.
25638 Changes in version 0.2.1.2-alpha - 2008-06-20
25639 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
25640 make it easier to set up your own private Tor network; fixes several
25641 big bugs with using more than one bridge relay; fixes a big bug with
25642 offering hidden services quickly after Tor starts; and uses a better
25643 API for reporting potential bootstrapping problems to the controller.
25646 - New TestingTorNetwork config option to allow adjustment of
25647 previously constant values that, while reasonable, could slow
25648 bootstrapping. Implements proposal 135. Patch from Karsten.
25651 - If you have more than one bridge but don't know their digests,
25652 you would only learn a request for the descriptor of the first one
25653 on your list. (Tor considered launching requests for the others, but
25654 found that it already had a connection on the way for $0000...0000
25655 so it didn't open another.) Bugfix on 0.2.0.x.
25656 - If you have more than one bridge but don't know their digests,
25657 and the connection to one of the bridges failed, you would cancel
25658 all pending bridge connections. (After all, they all have the
25659 same digest.) Bugfix on 0.2.0.x.
25660 - When establishing a hidden service, introduction points that
25661 originate from cannibalized circuits are completely ignored and not
25662 included in rendezvous service descriptors. This might be another
25663 reason for delay in making a hidden service available. Bugfix
25664 from long ago (0.0.9.x?)
25667 - Allow OpenSSL to use dynamic locks if it wants.
25668 - When building a consensus, do not include routers that are down.
25669 This will cut down 30% to 40% on consensus size. Implements
25671 - In directory authorities' approved-routers files, allow
25672 fingerprints with or without space.
25673 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
25674 controller can query our current bootstrap state in case it attaches
25675 partway through and wants to catch up.
25676 - Send an initial "Starting" bootstrap status event, so we have a
25677 state to start out in.
25680 - Asking for a conditional consensus at .../consensus/<fingerprints>
25681 would crash a dirserver if it did not already have a
25682 consensus. Bugfix on 0.2.1.1-alpha.
25683 - Clean up some macro/CPP interactions: some GCC versions don't like
25684 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
25687 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
25688 - Directory authorities shouldn't complain about bootstrapping
25689 problems just because they do a lot of reachability testing and
25690 some of the connection attempts fail.
25691 - Start sending "count" and "recommendation" key/value pairs in
25692 bootstrap problem status events, so the controller can hear about
25693 problems even before Tor decides they're worth reporting for sure.
25694 - If you're using bridges, generate "bootstrap problem" warnings
25695 as soon as you run out of working bridges, rather than waiting
25696 for ten failures -- which will never happen if you have less than
25698 - If we close our OR connection because there's been a circuit
25699 pending on it for too long, we were telling our bootstrap status
25700 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
25703 Changes in version 0.2.1.1-alpha - 2008-06-13
25704 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
25705 were making the Tor process bloat especially on Linux; makes our TLS
25706 handshake blend in better; sends "bootstrap phase" status events to
25707 the controller, so it can keep the user informed of progress (and
25708 problems) fetching directory information and establishing circuits;
25709 and adds a variety of smaller features.
25712 - More work on making our TLS handshake blend in: modify the list
25713 of ciphers advertised by OpenSSL in client mode to even more
25714 closely resemble a common web browser. We cheat a little so that
25715 we can advertise ciphers that the locally installed OpenSSL doesn't
25717 - Start sending "bootstrap phase" status events to the controller,
25718 so it can keep the user informed of progress fetching directory
25719 information and establishing circuits. Also inform the controller
25720 if we think we're stuck at a particular bootstrap phase. Implements
25722 - Resume using OpenSSL's RAND_poll() for better (and more portable)
25723 cross-platform entropy collection again. We used to use it, then
25724 stopped using it because of a bug that could crash systems that
25725 called RAND_poll when they had a lot of fds open. It looks like the
25726 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
25727 at startup, and to call RAND_poll() when we reseed later only if
25728 we have a non-buggy OpenSSL version.
25731 - When we choose to abandon a new entry guard because we think our
25732 older ones might be better, close any circuits pending on that
25733 new entry guard connection. This fix should make us recover much
25734 faster when our network is down and then comes back. Bugfix on
25735 0.1.2.8-beta; found by lodger.
25737 o Memory fixes and improvements:
25738 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
25739 to avoid unused RAM in buffer chunks and memory pools.
25740 - Speed up parsing and cut down on memory fragmentation by using
25741 stack-style allocations for parsing directory objects. Previously,
25742 this accounted for over 40% of allocations from within Tor's code
25743 on a typical directory cache.
25744 - Use a Bloom filter rather than a digest-based set to track which
25745 descriptors we need to keep around when we're cleaning out old
25746 router descriptors. This speeds up the computation significantly,
25747 and may reduce fragmentation.
25748 - Reduce the default smartlist size from 32 to 16; it turns out that
25749 most smartlists hold around 8-12 elements tops.
25750 - Make dumpstats() log the fullness and size of openssl-internal
25752 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
25753 patch to their OpenSSL, turn it on to save memory on servers. This
25754 patch will (with any luck) get included in a mainline distribution
25756 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25757 compress cells, which are basically all encrypted, compressed,
25761 - Stop reloading the router list from disk for no reason when we
25762 run out of reachable directory mirrors. Once upon a time reloading
25763 it would set the 'is_running' flag back to 1 for them. It hasn't
25764 done that for a long time.
25765 - In very rare situations new hidden service descriptors were
25766 published earlier than 30 seconds after the last change to the
25767 service. (We currently think that a hidden service descriptor
25768 that's been stable for 30 seconds is worth publishing.)
25771 - Allow separate log levels to be configured for different logging
25772 domains. For example, this allows one to log all notices, warnings,
25773 or errors, plus all memory management messages of level debug or
25774 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
25775 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
25776 and stop using a warning that had become unfixably verbose under
25778 - New --hush command-line option similar to --quiet. While --quiet
25779 disables all logging to the console on startup, --hush limits the
25780 output to messages of warning and error severity.
25781 - Servers support a new URL scheme for consensus downloads that
25782 allows the client to specify which authorities are trusted.
25783 The server then only sends the consensus if the client will trust
25784 it. Otherwise a 404 error is sent back. Clients use this
25785 new scheme when the server supports it (meaning it's running
25786 0.2.1.1-alpha or later). Implements proposal 134.
25787 - New configure/torrc options (--enable-geoip-stats,
25788 DirRecordUsageByCountry) to record how many IPs we've served
25789 directory info to in each country code, how many status documents
25790 total we've sent to each country code, and what share of the total
25791 directory requests we should expect to see.
25792 - Use the TLS1 hostname extension to more closely resemble browser
25794 - Lots of new unit tests.
25795 - Add a macro to implement the common pattern of iterating through
25796 two parallel lists in lockstep.
25799 Changes in version 0.2.0.28-rc - 2008-06-13
25800 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
25801 performance bug, and fixes a bunch of smaller bugs.
25804 - Fix a bug where, when we were choosing the 'end stream reason' to
25805 put in our relay end cell that we send to the exit relay, Tor
25806 clients on Windows were sometimes sending the wrong 'reason'. The
25807 anonymity problem is that exit relays may be able to guess whether
25808 the client is running Windows, thus helping partition the anonymity
25809 set. Down the road we should stop sending reasons to exit relays,
25810 or otherwise prevent future versions of this bug.
25813 - While setting up a hidden service, some valid introduction circuits
25814 were overlooked and abandoned. This might be the reason for
25815 the long delay in making a hidden service available. Bugfix on
25819 - Update to the "June 9 2008" ip-to-country file.
25820 - Run 'make test' as part of 'make dist', so we stop releasing so
25821 many development snapshots that fail their unit tests.
25824 - When we're checking if we have enough dir info for each relay
25825 to begin establishing circuits, make sure that we actually have
25826 the descriptor listed in the consensus, not just any descriptor.
25828 - Bridge relays no longer print "xx=0" in their extrainfo document
25829 for every single country code in the geoip db. Bugfix on
25831 - Only warn when we fail to load the geoip file if we were planning to
25832 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
25833 - If we change our MaxAdvertisedBandwidth and then reload torrc,
25834 Tor won't realize it should publish a new relay descriptor. Fixes
25835 bug 688, reported by mfr. Bugfix on 0.1.2.x.
25836 - When we haven't had any application requests lately, don't bother
25837 logging that we have expired a bunch of descriptors. Bugfix
25839 - Make relay cells written on a connection count as non-padding when
25840 tracking how long a connection has been in use. Bugfix on
25841 0.2.0.1-alpha. Spotted by lodger.
25842 - Fix unit tests in 0.2.0.27-rc.
25843 - Fix compile on Windows.
25846 Changes in version 0.2.0.27-rc - 2008-06-03
25847 Tor 0.2.0.27-rc adds a few features we left out of the earlier
25848 release candidates. In particular, we now include an IP-to-country
25849 GeoIP database, so controllers can easily look up what country a
25850 given relay is in, and so bridge relays can give us some sanitized
25851 summaries about which countries are making use of bridges. (See proposal
25852 126-geoip-fetching.txt for details.)
25855 - Include an IP-to-country GeoIP file in the tarball, so bridge
25856 relays can report sanitized summaries of the usage they're seeing.
25859 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
25860 Robert Hogan. Fixes the first part of bug 681.
25861 - Make bridge authorities never serve extrainfo docs.
25862 - Add support to detect Libevent versions in the 1.4.x series
25864 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
25865 - Include a new contrib/tor-exit-notice.html file that exit relay
25866 operators can put on their website to help reduce abuse queries.
25869 - When tunneling an encrypted directory connection, and its first
25870 circuit fails, do not leave it unattached and ask the controller
25871 to deal. Fixes the second part of bug 681.
25872 - Make bridge authorities correctly expire old extrainfo documents
25876 Changes in version 0.2.0.26-rc - 2008-05-13
25877 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
25878 in Debian's OpenSSL packages. All users running any 0.2.0.x version
25879 should upgrade, whether they're running Debian or not.
25881 o Major security fixes:
25882 - Use new V3 directory authority keys on the tor26, gabelmoo, and
25883 moria1 V3 directory authorities. The old keys were generated with
25884 a vulnerable version of Debian's OpenSSL package, and must be
25885 considered compromised. Other authorities' keys were not generated
25886 with an affected version of OpenSSL.
25889 - List authority signatures as "unrecognized" based on DirServer
25890 lines, not on cert cache. Bugfix on 0.2.0.x.
25893 - Add a new V3AuthUseLegacyKey option to make it easier for
25894 authorities to change their identity keys if they have to.
25897 Changes in version 0.2.0.25-rc - 2008-04-23
25898 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
25901 - Remember to initialize threading before initializing logging.
25902 Otherwise, many BSD-family implementations will crash hard on
25903 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
25906 - Authorities correctly free policies on bad servers on
25907 exit. Fixes bug 672. Bugfix on 0.2.0.x.
25910 Changes in version 0.2.0.24-rc - 2008-04-22
25911 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
25912 v3 directory authority, makes relays with dynamic IP addresses and no
25913 DirPort notice more quickly when their IP address changes, fixes a few
25914 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
25916 o New directory authorities:
25917 - Take lefkada out of the list of v3 directory authorities, since
25918 it has been down for months.
25919 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
25923 - Detect address changes more quickly on non-directory mirror
25924 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
25926 o Minor features (security):
25927 - Reject requests for reverse-dns lookup of names that are in
25928 a private address space. Patch from lodger.
25929 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
25932 o Minor bugfixes (crashes):
25933 - Avoid a rare assert that can trigger when Tor doesn't have much
25934 directory information yet and it tries to fetch a v2 hidden
25935 service descriptor. Fixes bug 651, reported by nwf.
25936 - Initialize log mutex before initializing dmalloc. Otherwise,
25937 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
25938 - Use recursive pthread mutexes in order to avoid deadlock when
25939 logging debug-level messages to a controller. Bug spotted by nwf,
25940 bugfix on 0.2.0.16-alpha.
25942 o Minor bugfixes (resource management):
25943 - Keep address policies from leaking memory: start their refcount
25944 at 1, not 2. Bugfix on 0.2.0.16-alpha.
25945 - Free authority certificates on exit, so they don't look like memory
25946 leaks. Bugfix on 0.2.0.19-alpha.
25947 - Free static hashtables for policy maps and for TLS connections on
25948 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
25949 - Avoid allocating extra space when computing consensuses on 64-bit
25950 platforms. Bug spotted by aakova.
25952 o Minor bugfixes (misc):
25953 - Do not read the configuration file when we've only been told to
25954 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
25955 based on patch from Sebastian Hahn.
25956 - Exit relays that are used as a client can now reach themselves
25957 using the .exit notation, rather than just launching an infinite
25958 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
25959 - When attempting to open a logfile fails, tell us why.
25960 - Fix a dumb bug that was preventing us from knowing that we should
25961 preemptively build circuits to handle expected directory requests.
25962 Fixes bug 660. Bugfix on 0.1.2.x.
25963 - Warn less verbosely about clock skew from netinfo cells from
25964 untrusted sources. Fixes bug 663.
25965 - Make controller stream events for DNS requests more consistent,
25966 by adding "new stream" events for DNS requests, and removing
25967 spurious "stream closed" events" for cached reverse resolves.
25968 Patch from mwenge. Fixes bug 646.
25969 - Correctly notify one-hop connections when a circuit build has
25970 failed. Possible fix for bug 669. Found by lodger.
25973 Changes in version 0.2.0.23-rc - 2008-03-24
25974 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
25975 makes bootstrapping faster if the first directory mirror you contact
25976 is down. The bundles also include the new Vidalia 0.1.2 release.
25979 - When a tunneled directory request is made to a directory server
25980 that's down, notice after 30 seconds rather than 120 seconds. Also,
25981 fail any begindir streams that are pending on it, so they can
25982 retry elsewhere. This was causing multi-minute delays on bootstrap.
25985 Changes in version 0.2.0.22-rc - 2008-03-18
25986 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
25987 enables encrypted directory connections by default for non-relays, fixes
25988 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
25989 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
25992 - Enable encrypted directory connections by default for non-relays,
25993 so censor tools that block Tor directory connections based on their
25994 plaintext patterns will no longer work. This means Tor works in
25995 certain censored countries by default again.
25998 - Make sure servers always request certificates from clients during
25999 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
26000 - Do not enter a CPU-eating loop when a connection is closed in
26001 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
26002 diagnosed by lodger; bugfix on 0.2.0.20-rc.
26003 - Fix assertion failure that could occur when a blocked circuit
26004 became unblocked, and it had pending client DNS requests. Bugfix
26005 on 0.2.0.1-alpha. Fixes bug 632.
26007 o Minor bugfixes (on 0.1.2.x):
26008 - Generate "STATUS_SERVER" events rather than misspelled
26009 "STATUS_SEVER" events. Caught by mwenge.
26010 - When counting the number of bytes written on a TLS connection,
26011 look at the BIO actually used for writing to the network, not
26012 at the BIO used (sometimes) to buffer data for the network.
26013 Looking at different BIOs could result in write counts on the
26014 order of ULONG_MAX. Fixes bug 614.
26015 - On Windows, correctly detect errors when listing the contents of
26016 a directory. Fix from lodger.
26018 o Minor bugfixes (on 0.2.0.x):
26019 - Downgrade "sslv3 alert handshake failure" message to INFO.
26020 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
26021 left BandwidthRate and BandwidthBurst at the default, we would be
26022 silently limited by those defaults. Now raise them to match the
26023 RelayBandwidth* values.
26024 - Fix the SVK version detection logic to work correctly on a branch.
26025 - Make --enable-openbsd-malloc work correctly on Linux with alpha
26026 CPUs. Fixes bug 625.
26027 - Logging functions now check that the passed severity is sane.
26028 - Use proper log levels in the testsuite call of
26029 get_interface_address6().
26030 - When using a nonstandard malloc, do not use the platform values for
26031 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
26032 - Make the openbsd malloc code use 8k pages on alpha CPUs and
26034 - Detect mismatched page sizes when using --enable-openbsd-malloc.
26035 - Avoid double-marked-for-close warning when certain kinds of invalid
26036 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
26037 for bug 617. Bugfix on 0.2.0.1-alpha.
26038 - Make sure that the "NULL-means-reject *:*" convention is followed by
26039 all the policy manipulation functions, avoiding some possible crash
26040 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
26041 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
26042 actually works, and doesn't warn about every single reverse lookup.
26043 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
26046 - Only log guard node status when guard node status has changed.
26047 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
26048 make "INFO" 75% less verbose.
26051 Changes in version 0.2.0.21-rc - 2008-03-02
26052 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
26053 makes Tor work well with Vidalia again, fixes a rare assert bug,
26054 and fixes a pair of more minor bugs. The bundles also include Vidalia
26055 0.1.0 and Torbutton 1.1.16.
26058 - The control port should declare that it requires password auth
26059 when HashedControlSessionPassword is set too. Patch from Matt Edman;
26060 bugfix on 0.2.0.20-rc. Fixes bug 615.
26061 - Downgrade assert in connection_buckets_decrement() to a log message.
26062 This may help us solve bug 614, and in any case will make its
26063 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
26064 - We were sometimes miscounting the number of bytes read from the
26065 network, causing our rate limiting to not be followed exactly.
26066 Bugfix on 0.2.0.16-alpha. Reported by lodger.
26069 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
26070 OpenSSL versions should have been working fine. Diagnosis and patch
26071 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
26072 Bugfix on 0.2.0.20-rc.
26075 Changes in version 0.2.0.20-rc - 2008-02-24
26076 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
26077 makes more progress towards normalizing Tor's TLS handshake, makes
26078 hidden services work better again, helps relays bootstrap if they don't
26079 know their IP address, adds optional support for linking in openbsd's
26080 allocator or tcmalloc, allows really fast relays to scale past 15000
26081 sockets, and fixes a bunch of minor bugs reported by Veracode.
26084 - Enable the revised TLS handshake based on the one designed by
26085 Steven Murdoch in proposal 124, as revised in proposal 130. It
26086 includes version negotiation for OR connections as described in
26087 proposal 105. The new handshake is meant to be harder for censors
26088 to fingerprint, and it adds the ability to detect certain kinds of
26089 man-in-the-middle traffic analysis attacks. The version negotiation
26090 feature will allow us to improve Tor's link protocol more safely
26092 - Choose which bridge to use proportional to its advertised bandwidth,
26093 rather than uniformly at random. This should speed up Tor for
26094 bridge users. Also do this for people who set StrictEntryNodes.
26095 - When a TrackHostExits-chosen exit fails too many times in a row,
26096 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
26099 - Resolved problems with (re-)fetching hidden service descriptors.
26100 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
26101 and 0.2.0.19-alpha.
26102 - If we only ever used Tor for hidden service lookups or posts, we
26103 would stop building circuits and start refusing connections after
26104 24 hours, since we falsely believed that Tor was dormant. Reported
26105 by nwf; bugfix on 0.1.2.x.
26106 - Servers that don't know their own IP address should go to the
26107 authorities for their first directory fetch, even if their DirPort
26108 is off or if they don't know they're reachable yet. This will help
26109 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
26110 - When counting the number of open sockets, count not only the number
26111 of sockets we have received from the socket() call, but also
26112 the number we've gotten from accept() and socketpair(). This bug
26113 made us fail to count all sockets that we were using for incoming
26114 connections. Bugfix on 0.2.0.x.
26115 - Fix code used to find strings within buffers, when those strings
26116 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
26117 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
26118 - Add a new __HashedControlSessionPassword option for controllers
26119 to use for one-off session password hashes that shouldn't get
26120 saved to disk by SAVECONF --- Vidalia users were accumulating a
26121 pile of HashedControlPassword lines in their torrc files, one for
26122 each time they had restarted Tor and then clicked Save. Make Tor
26123 automatically convert "HashedControlPassword" to this new option but
26124 only when it's given on the command line. Partial fix for bug 586.
26126 o Minor features (performance):
26127 - Tune parameters for cell pool allocation to minimize amount of
26129 - Add OpenBSD malloc code from phk as an optional malloc
26130 replacement on Linux: some glibc libraries do very poorly
26131 with Tor's memory allocation patterns. Pass
26132 --enable-openbsd-malloc to get the replacement malloc code.
26133 - Add a --with-tcmalloc option to the configure script to link
26134 against tcmalloc (if present). Does not yet search for
26135 non-system include paths.
26136 - Stop imposing an arbitrary maximum on the number of file descriptors
26137 used for busy servers. Bug reported by Olaf Selke; patch from
26140 o Minor features (other):
26141 - When SafeLogging is disabled, log addresses along with all TLS
26143 - When building with --enable-gcc-warnings, check for whether Apple's
26144 warning "-Wshorten-64-to-32" is available.
26145 - Add a --passphrase-fd argument to the tor-gencert command for
26148 o Minor bugfixes (memory leaks and code problems):
26149 - We were leaking a file descriptor if Tor started with a zero-length
26150 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
26151 - Detect size overflow in zlib code. Reported by Justin Ferguson and
26153 - We were comparing the raw BridgePassword entry with a base64'ed
26154 version of it, when handling a "/tor/networkstatus-bridges"
26155 directory request. Now compare correctly. Noticed by Veracode.
26156 - Recover from bad tracked-since value in MTBF-history file.
26157 Should fix bug 537.
26158 - Alter the code that tries to recover from unhandled write
26159 errors, to not try to flush onto a socket that's given us
26160 unhandled errors. Bugfix on 0.1.2.x.
26161 - Make Unix controlsockets work correctly on OpenBSD. Patch from
26162 tup. Bugfix on 0.2.0.3-alpha.
26164 o Minor bugfixes (other):
26165 - If we have an extra-info document for our server, always make
26166 it available on the control port, even if we haven't gotten
26167 a copy of it from an authority yet. Patch from mwenge.
26168 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
26169 - Directory mirrors no longer include a guess at the client's IP
26170 address if the connection appears to be coming from the same /24
26171 network; it was producing too many wrong guesses.
26172 - Make the new hidden service code respect the SafeLogging setting.
26173 Bugfix on 0.2.0.x. Patch from Karsten.
26174 - When starting as an authority, do not overwrite all certificates
26175 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
26176 - If we're trying to flush the last bytes on a connection (for
26177 example, when answering a directory request), reset the
26178 time-to-give-up timeout every time we manage to write something
26179 on the socket. Bugfix on 0.1.2.x.
26180 - Change the behavior of "getinfo status/good-server-descriptor"
26181 so it doesn't return failure when any authority disappears.
26182 - Even though the man page said that "TrackHostExits ." should
26183 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
26184 - Report TLS "zero return" case as a "clean close" and "IO error"
26185 as a "close". Stop calling closes "unexpected closes": existing
26186 Tors don't use SSL_close(), so having a connection close without
26187 the TLS shutdown handshake is hardly unexpected.
26188 - Send NAMESERVER_STATUS messages for a single failed nameserver
26191 o Code simplifications and refactoring:
26192 - Remove the tor_strpartition function: its logic was confused,
26193 and it was only used for one thing that could be implemented far
26197 Changes in version 0.2.0.19-alpha - 2008-02-09
26198 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
26199 handshake, makes path selection for relays more secure and IP address
26200 guessing more robust, and generally fixes a lot of bugs in preparation
26201 for calling the 0.2.0 branch stable.
26204 - Do not include recognizeable strings in the commonname part of
26205 Tor's x509 certificates.
26208 - If we're a relay, avoid picking ourselves as an introduction point,
26209 a rendezvous point, or as the final hop for internal circuits. Bug
26210 reported by taranis and lodger. Bugfix on 0.1.2.x.
26211 - Patch from "Andrew S. Lists" to catch when we contact a directory
26212 mirror at IP address X and he says we look like we're coming from
26213 IP address X. Bugfix on 0.1.2.x.
26215 o Minor features (security):
26216 - Be more paranoid about overwriting sensitive memory on free(),
26217 as a defensive programming tactic to ensure forward secrecy.
26219 o Minor features (directory authority):
26220 - Actually validate the options passed to AuthDirReject,
26221 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
26222 - Reject router descriptors with out-of-range bandwidthcapacity or
26223 bandwidthburst values.
26225 o Minor features (controller):
26226 - Reject controller commands over 1MB in length. This keeps rogue
26227 processes from running us out of memory.
26229 o Minor features (misc):
26230 - Give more descriptive well-formedness errors for out-of-range
26231 hidden service descriptor/protocol versions.
26232 - Make memory debugging information describe more about history
26233 of cell allocation, so we can help reduce our memory use.
26235 o Deprecated features (controller):
26236 - The status/version/num-versioning and status/version/num-concurring
26237 GETINFO options are no longer useful in the v3 directory protocol:
26238 treat them as deprecated, and warn when they're used.
26241 - When our consensus networkstatus has been expired for a while, stop
26242 being willing to build circuits using it. Fixes bug 401. Bugfix
26244 - Directory caches now fetch certificates from all authorities
26245 listed in a networkstatus consensus, even when they do not
26246 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
26247 - When connecting to a bridge without specifying its key, insert
26248 the connection into the identity-to-connection map as soon as
26249 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
26250 - Detect versions of OS X where malloc_good_size() is present in the
26251 library but never actually declared. Resolves bug 587. Bugfix
26253 - Stop incorrectly truncating zlib responses to directory authority
26254 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
26255 - Stop recommending that every server operator send mail to tor-ops.
26256 Resolves bug 597. Bugfix on 0.1.2.x.
26257 - Don't trigger an assert if we start a directory authority with a
26258 private IP address (like 127.0.0.1).
26259 - Avoid possible failures when generating a directory with routers
26260 with over-long versions strings, or too many flags set. Bugfix
26262 - If an attempt to launch a DNS resolve request over the control
26263 port fails because we have overrun the limit on the number of
26264 connections, tell the controller that the request has failed.
26265 - Avoid using too little bandwidth when our clock skips a few
26266 seconds. Bugfix on 0.1.2.x.
26267 - Fix shell error when warning about missing packages in configure
26268 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
26269 - Do not become confused when receiving a spurious VERSIONS-like
26270 cell from a confused v1 client. Bugfix on 0.2.0.x.
26271 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
26272 introduction points for a hidden service have failed. Patch from
26273 Karsten Loesing. Bugfix on 0.2.0.x.
26275 o Code simplifications and refactoring:
26276 - Remove some needless generality from cpuworker code, for improved
26278 - Stop overloading the circuit_t.onionskin field for both "onionskin
26279 from a CREATE cell that we are waiting for a cpuworker to be
26280 assigned" and "onionskin from an EXTEND cell that we are going to
26281 send to an OR as soon as we are connected". Might help with bug 600.
26282 - Add an in-place version of aes_crypt() so that we can avoid doing a
26283 needless memcpy() call on each cell payload.
26286 Changes in version 0.2.0.18-alpha - 2008-01-25
26287 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
26288 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
26289 that can warn or reject connections to ports generally associated with
26290 vulnerable-plaintext protocols.
26292 o New directory authorities:
26293 - Set up dannenberg (run by CCC) as the sixth v3 directory
26297 - Fix a major memory leak when attempting to use the v2 TLS
26298 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
26299 - We accidentally enabled the under-development v2 TLS handshake
26300 code, which was causing log entries like "TLS error while
26301 renegotiating handshake". Disable it again. Resolves bug 590.
26302 - We were computing the wrong Content-Length: header for directory
26303 responses that need to be compressed on the fly, causing clients
26304 asking for those items to always fail. Bugfix on 0.2.0.x; partially
26308 - Avoid going directly to the directory authorities even if you're a
26309 relay, if you haven't found yourself reachable yet or if you've
26310 decided not to advertise your dirport yet. Addresses bug 556.
26311 - If we've gone 12 hours since our last bandwidth check, and we
26312 estimate we have less than 50KB bandwidth capacity but we could
26313 handle more, do another bandwidth test.
26314 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
26315 Tor can warn and/or refuse connections to ports commonly used with
26316 vulnerable-plaintext protocols. Currently we warn on ports 23,
26317 109, 110, and 143, but we don't reject any.
26320 - When we setconf ClientOnly to 1, close any current OR and Dir
26321 listeners. Reported by mwenge.
26322 - When we get a consensus that's been signed by more people than
26323 we expect, don't log about it; it's not a big deal. Reported
26327 - Don't answer "/tor/networkstatus-bridges" directory requests if
26328 the request isn't encrypted.
26329 - Make "ClientOnly 1" config option disable directory ports too.
26330 - Patches from Karsten Loesing to make v2 hidden services more
26331 robust: work even when there aren't enough HSDir relays available;
26332 retry when a v2 rend desc fetch fails; but don't retry if we
26333 already have a usable v0 rend desc.
26336 Changes in version 0.2.0.17-alpha - 2008-01-17
26337 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
26340 - Make the tor-gencert man page get included correctly in the tarball.
26343 Changes in version 0.2.0.16-alpha - 2008-01-17
26344 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
26345 Loesing, and generally cleans up a lot of features and minor bugs.
26347 o New directory authorities:
26348 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
26351 o Major performance improvements:
26352 - Switch our old ring buffer implementation for one more like that
26353 used by free Unix kernels. The wasted space in a buffer with 1mb
26354 of data will now be more like 8k than 1mb. The new implementation
26355 also avoids realloc();realloc(); patterns that can contribute to
26356 memory fragmentation.
26359 - Configuration files now accept C-style strings as values. This
26360 helps encode characters not allowed in the current configuration
26361 file format, such as newline or #. Addresses bug 557.
26362 - Although we fixed bug 539 (where servers would send HTTP status 503
26363 responses _and_ send a body too), there are still servers out
26364 there that haven't upgraded. Therefore, make clients parse such
26365 bodies when they receive them.
26366 - When we're not serving v2 directory information, there is no reason
26367 to actually keep any around. Remove the obsolete files and directory
26368 on startup if they are very old and we aren't going to serve them.
26370 o Minor performance improvements:
26371 - Reference-count and share copies of address policy entries; only 5%
26372 of them were actually distinct.
26373 - Never walk through the list of logs if we know that no log is
26374 interested in a given message.
26377 - When an authority has not signed a consensus, do not try to
26378 download a nonexistent "certificate with key 00000000". Bugfix
26379 on 0.2.0.x. Fixes bug 569.
26380 - Fix a rare assert error when we're closing one of our threads:
26381 use a mutex to protect the list of logs, so we never write to the
26382 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
26383 bug 575, which is kind of the revenge of bug 222.
26384 - Patch from Karsten Loesing to complain less at both the client
26385 and the relay when a relay used to have the HSDir flag but doesn't
26386 anymore, and we try to upload a hidden service descriptor.
26387 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
26389 - Do not try to download missing certificates until we have tried
26390 to check our fallback consensus. Fixes bug 583.
26391 - Make bridges round reported GeoIP stats info up to the nearest
26392 estimate, not down. Now we can distinguish between "0 people from
26393 this country" and "1 person from this country".
26394 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
26395 - Avoid possible segfault if key generation fails in
26396 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
26397 - Avoid segfault in the case where a badly behaved v2 versioning
26398 directory sends a signed networkstatus with missing client-versions.
26400 - Avoid segfaults on certain complex invocations of
26401 router_get_by_hexdigest(). Bugfix on 0.1.2.
26402 - Correct bad index on array access in parse_http_time(). Bugfix
26404 - Fix possible bug in vote generation when server versions are present
26405 but client versions are not.
26406 - Fix rare bug on REDIRECTSTREAM control command when called with no
26407 port set: it could erroneously report an error when none had
26409 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
26410 compressing large objects and find ourselves with more than 4k
26411 left over. Bugfix on 0.2.0.
26412 - Fix a small memory leak when setting up a hidden service.
26413 - Fix a few memory leaks that could in theory happen under bizarre
26415 - Fix an assert if we post a general-purpose descriptor via the
26416 control port but that descriptor isn't mentioned in our current
26417 network consensus. Bug reported by Jon McLachlan; bugfix on
26420 o Minor features (controller):
26421 - Get NS events working again. Patch from tup.
26422 - The GETCONF command now escapes and quotes configuration values
26423 that don't otherwise fit into the torrc file.
26424 - The SETCONF command now handles quoted values correctly.
26426 o Minor features (directory authorities):
26427 - New configuration options to override default maximum number of
26428 servers allowed on a single IP address. This is important for
26429 running a test network on a single host.
26430 - Actually implement the -s option to tor-gencert.
26431 - Add a manual page for tor-gencert.
26433 o Minor features (bridges):
26434 - Bridge authorities no longer serve bridge descriptors over
26435 unencrypted connections.
26437 o Minor features (other):
26438 - Add hidden services and DNSPorts to the list of things that make
26439 Tor accept that it has running ports. Change starting Tor with no
26440 ports from a fatal error to a warning; we might change it back if
26441 this turns out to confuse anybody. Fixes bug 579.
26444 Changes in version 0.1.2.19 - 2008-01-17
26445 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26446 exit policy a little bit more conservative so it's safer to run an
26447 exit relay on a home system, and fixes a variety of smaller issues.
26450 - Exit policies now reject connections that are addressed to a
26451 relay's public (external) IP address too, unless
26452 ExitPolicyRejectPrivate is turned off. We do this because too
26453 many relays are running nearby to services that trust them based
26454 on network address.
26457 - When the clock jumps forward a lot, do not allow the bandwidth
26458 buckets to become negative. Fixes bug 544.
26459 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26460 on every successful resolve. Reported by Mike Perry.
26461 - Purge old entries from the "rephist" database and the hidden
26462 service descriptor database even when DirPort is zero.
26463 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26464 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26465 crashing or mis-answering these requests.
26466 - When we decide to send a 503 response to a request for servers, do
26467 not then also send the server descriptors: this defeats the whole
26468 purpose. Fixes bug 539.
26471 - Changing the ExitPolicyRejectPrivate setting should cause us to
26472 rebuild our server descriptor.
26473 - Fix handling of hex nicknames when answering controller requests for
26474 networkstatus by name, or when deciding whether to warn about
26475 unknown routers in a config option. (Patch from mwenge.)
26476 - Fix a couple of hard-to-trigger autoconf problems that could result
26477 in really weird results on platforms whose sys/types.h files define
26478 nonstandard integer types.
26479 - Don't try to create the datadir when running --verify-config or
26480 --hash-password. Resolves bug 540.
26481 - If we were having problems getting a particular descriptor from the
26482 directory caches, and then we learned about a new descriptor for
26483 that router, we weren't resetting our failure count. Reported
26485 - Although we fixed bug 539 (where servers would send HTTP status 503
26486 responses _and_ send a body too), there are still servers out there
26487 that haven't upgraded. Therefore, make clients parse such bodies
26488 when they receive them.
26489 - Run correctly on systems where rlim_t is larger than unsigned long.
26490 This includes some 64-bit systems.
26491 - Run correctly on platforms (like some versions of OS X 10.5) where
26492 the real limit for number of open files is OPEN_FILES, not rlim_max
26493 from getrlimit(RLIMIT_NOFILES).
26494 - Avoid a spurious free on base64 failure.
26495 - Avoid segfaults on certain complex invocations of
26496 router_get_by_hexdigest().
26497 - Fix rare bug on REDIRECTSTREAM control command when called with no
26498 port set: it could erroneously report an error when none had
26502 Changes in version 0.2.0.15-alpha - 2007-12-25
26503 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26504 features added in 0.2.0.13-alpha.
26507 - Fix several remotely triggerable asserts based on DirPort requests
26508 for a v2 or v3 networkstatus object before we were prepared. This
26509 was particularly bad for 0.2.0.13 and later bridge relays, who
26510 would never have a v2 networkstatus and would thus always crash
26511 when used. Bugfixes on 0.2.0.x.
26512 - Estimate the v3 networkstatus size more accurately, rather than
26513 estimating it at zero bytes and giving it artificially high priority
26514 compared to other directory requests. Bugfix on 0.2.0.x.
26517 - Fix configure.in logic for cross-compilation.
26518 - When we load a bridge descriptor from the cache, and it was
26519 previously unreachable, mark it as retriable so we won't just
26520 ignore it. Also, try fetching a new copy immediately. Bugfixes
26522 - The bridge GeoIP stats were counting other relays, for example
26523 self-reachability and authority-reachability tests.
26526 - Support compilation to target iPhone; patch from cjacker huang.
26527 To build for iPhone, pass the --enable-iphone option to configure.
26530 Changes in version 0.2.0.14-alpha - 2007-12-23
26532 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26533 without a datadirectory from a previous Tor install. Reported
26535 - Fix a crash when we fetch a descriptor that turns out to be
26536 unexpected (it used to be in our networkstatus when we started
26537 fetching it, but it isn't in our current networkstatus), and we
26538 aren't using bridges. Bugfix on 0.2.0.x.
26539 - Fix a crash when accessing hidden services: it would work the first
26540 time you use a given introduction point for your service, but
26541 on subsequent requests we'd be using garbage memory. Fixed by
26542 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26543 - Fix a crash when we load a bridge descriptor from disk but we don't
26544 currently have a Bridge line for it in our torrc. Bugfix on
26548 - If bridge authorities set BridgePassword, they will serve a
26549 snapshot of known bridge routerstatuses from their DirPort to
26550 anybody who knows that password. Unset by default.
26553 - Make the unit tests build again.
26554 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26555 - Make PublishServerDescriptor default to 1, so the default doesn't
26556 have to change as we invent new directory protocol versions.
26557 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26558 be included unless sys/time.h is already included. Fixes
26559 bug 553. Bugfix on 0.2.0.x.
26560 - If we receive a general-purpose descriptor and then receive an
26561 identical bridge-purpose descriptor soon after, don't discard
26562 the next one as a duplicate.
26565 - If BridgeRelay is set to 1, then the default for
26566 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26567 - If the user sets RelayBandwidthRate but doesn't set
26568 RelayBandwidthBurst, then make them equal rather than erroring out.
26571 Changes in version 0.2.0.13-alpha - 2007-12-21
26572 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26573 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26576 o New directory authorities:
26577 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26581 - Only update guard status (usable / not usable) once we have
26582 enough directory information. This was causing us to always pick
26583 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26584 causing us to discard all our guards on startup if we hadn't been
26585 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26586 - Purge old entries from the "rephist" database and the hidden
26587 service descriptor databases even when DirPort is zero. Bugfix
26589 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26590 after opening a circuit -- even a relayed circuit. Bugfix on
26592 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26593 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26594 crashing or mis-answering these types of requests.
26595 - Relays were publishing their server descriptor to v1 and v2
26596 directory authorities, but they didn't try publishing to v3-only
26597 authorities. Fix this; and also stop publishing to v1 authorities.
26599 - When we were reading router descriptors from cache, we were ignoring
26600 the annotations -- so for example we were reading in bridge-purpose
26601 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26602 - When we decided to send a 503 response to a request for servers, we
26603 were then also sending the server descriptors: this defeats the
26604 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26607 - Bridge relays now behave like clients with respect to time
26608 intervals for downloading new consensus documents -- otherwise they
26609 stand out. Bridge users now wait until the end of the interval,
26610 so their bridge relay will be sure to have a new consensus document.
26611 - Three new config options (AlternateDirAuthority,
26612 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26613 user selectively replace the default directory authorities by type,
26614 rather than the all-or-nothing replacement that DirServer offers.
26615 - Tor can now be configured to read a GeoIP file from disk in one
26616 of two formats. This can be used by controllers to map IP addresses
26617 to countries. Eventually, it may support exit-by-country.
26618 - When possible, bridge relays remember which countries users
26619 are coming from, and report aggregate information in their
26620 extra-info documents, so that the bridge authorities can learn
26621 where Tor is blocked.
26622 - Bridge directory authorities now do reachability testing on the
26623 bridges they know. They provide router status summaries to the
26624 controller via "getinfo ns/purpose/bridge", and also dump summaries
26625 to a file periodically.
26626 - Stop fetching directory info so aggressively if your DirPort is
26627 on but your ORPort is off; stop fetching v2 dir info entirely.
26628 You can override these choices with the new FetchDirInfoEarly
26632 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
26633 consensus documents when there are too many relays at a single
26634 IP address. Now clear it in v2 network status documents too, and
26635 also clear it in routerinfo_t when the relay is no longer listed
26636 in the relevant networkstatus document.
26637 - Don't crash if we get an unexpected value for the
26638 PublishServerDescriptor config option. Reported by Matt Edman;
26639 bugfix on 0.2.0.9-alpha.
26640 - Our new v2 hidden service descriptor format allows descriptors
26641 that have no introduction points. But Tor crashed when we tried
26642 to build a descriptor with no intro points (and it would have
26643 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
26644 by Karsten Loesing.
26645 - Fix building with dmalloc 5.5.2 with glibc.
26646 - Reject uploaded descriptors and extrainfo documents if they're
26647 huge. Otherwise we'll cache them all over the network and it'll
26648 clog everything up. Reported by Aljosha Judmayer.
26649 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
26650 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
26651 - When the DANGEROUS_VERSION controller status event told us we're
26652 running an obsolete version, it used the string "OLD" to describe
26653 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
26654 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
26655 - If we can't expand our list of entry guards (e.g. because we're
26656 using bridges or we have StrictEntryNodes set), don't mark relays
26657 down when they fail a directory request. Otherwise we're too quick
26658 to mark all our entry points down. Bugfix on 0.1.2.x.
26659 - Fix handling of hex nicknames when answering controller requests for
26660 networkstatus by name, or when deciding whether to warn about unknown
26661 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
26662 - Fix a couple of hard-to-trigger autoconf problems that could result
26663 in really weird results on platforms whose sys/types.h files define
26664 nonstandard integer types. Bugfix on 0.1.2.x.
26665 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
26666 - Don't crash on name lookup when we have no current consensus. Fixes
26667 bug 538; bugfix on 0.2.0.x.
26668 - Only Tors that want to mirror the v2 directory info should
26669 create the "cached-status" directory in their datadir. (All Tors
26670 used to create it.) Bugfix on 0.2.0.9-alpha.
26671 - Directory authorities should only automatically download Extra Info
26672 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
26675 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
26676 consumers. (We already do this on HUP.)
26677 - Authorities and caches fetch the v2 networkstatus documents
26678 less often, now that v3 is encouraged.
26679 - Add a new config option BridgeRelay that specifies you want to
26680 be a bridge relay. Right now the only difference is that it makes
26681 you answer begin_dir requests, and it makes you cache dir info,
26682 even if your DirPort isn't on.
26683 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
26684 ask about source, timestamp of arrival, purpose, etc. We need
26685 something like this to help Vidalia not do GeoIP lookups on bridge
26687 - Allow multiple HashedControlPassword config lines, to support
26688 multiple controller passwords.
26689 - Authorities now decide whether they're authoritative for a given
26690 router based on the router's purpose.
26691 - New config options AuthDirBadDir and AuthDirListBadDirs for
26692 authorities to mark certain relays as "bad directories" in the
26693 networkstatus documents. Also supports the "!baddir" directive in
26694 the approved-routers file.
26697 Changes in version 0.2.0.12-alpha - 2007-11-16
26698 This twelfth development snapshot fixes some more build problems as
26699 well as a few minor bugs.
26702 - Make it build on OpenBSD again. Patch from tup.
26703 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
26704 package-building for Red Hat, OS X, etc.
26706 o Minor bugfixes (on 0.1.2.x):
26707 - Changing the ExitPolicyRejectPrivate setting should cause us to
26708 rebuild our server descriptor.
26710 o Minor bugfixes (on 0.2.0.x):
26711 - When we're lacking a consensus, don't try to perform rendezvous
26712 operations. Reported by Karsten Loesing.
26713 - Fix a small memory leak whenever we decide against using a
26714 newly picked entry guard. Reported by Mike Perry.
26715 - When authorities detected more than two relays running on the same
26716 IP address, they were clearing all the status flags but forgetting
26717 to clear the "hsdir" flag. So clients were being told that a
26718 given relay was the right choice for a v2 hsdir lookup, yet they
26719 never had its descriptor because it was marked as 'not running'
26721 - If we're trying to fetch a bridge descriptor and there's no way
26722 the bridge authority could help us (for example, we don't know
26723 a digest, or there is no bridge authority), don't be so eager to
26724 fall back to asking the bridge authority.
26725 - If we're using bridges or have strictentrynodes set, and our
26726 chosen exit is in the same family as all our bridges/entry guards,
26727 then be flexible about families.
26730 - When we negotiate a v2 link-layer connection (not yet implemented),
26731 accept RELAY_EARLY cells and turn them into RELAY cells if we've
26732 negotiated a v1 connection for their next step. Initial code for
26736 Changes in version 0.2.0.11-alpha - 2007-11-12
26737 This eleventh development snapshot fixes some build problems with
26738 the previous snapshot. It also includes a more secure-by-default exit
26739 policy for relays, fixes an enormous memory leak for exit relays, and
26740 fixes another bug where servers were falling out of the directory list.
26743 - Exit policies now reject connections that are addressed to a
26744 relay's public (external) IP address too, unless
26745 ExitPolicyRejectPrivate is turned off. We do this because too
26746 many relays are running nearby to services that trust them based
26747 on network address. Bugfix on 0.1.2.x.
26750 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26751 on every successful resolve. Reported by Mike Perry; bugfix
26753 - On authorities, never downgrade to old router descriptors simply
26754 because they're listed in the consensus. This created a catch-22
26755 where we wouldn't list a new descriptor because there was an
26756 old one in the consensus, and we couldn't get the new one in the
26757 consensus because we wouldn't list it. Possible fix for bug 548.
26758 Also, this might cause bug 543 to appear on authorities; if so,
26759 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
26761 o Packaging fixes on 0.2.0.10-alpha:
26762 - We were including instructions about what to do with the
26763 src/config/fallback-consensus file, but we weren't actually
26764 including it in the tarball. Disable all of that for now.
26767 - Allow people to say PreferTunnelledDirConns rather than
26768 PreferTunneledDirConns, for those alternate-spellers out there.
26771 - Don't reevaluate all the information from our consensus document
26772 just because we've downloaded a v2 networkstatus that we intend
26773 to cache. Fixes bug 545; bugfix on 0.2.0.x.
26776 Changes in version 0.2.0.10-alpha - 2007-11-10
26777 This tenth development snapshot adds a third v3 directory authority
26778 run by Mike Perry, adds most of Karsten Loesing's new hidden service
26779 descriptor format, fixes a bad crash bug and new bridge bugs introduced
26780 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
26781 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
26782 addresses many more minor issues.
26784 o New directory authorities:
26785 - Set up ides (run by Mike Perry) as the third v3 directory authority.
26788 - Allow tunnelled directory connections to ask for an encrypted
26789 "begin_dir" connection or an anonymized "uses a full Tor circuit"
26790 connection independently. Now we can make anonymized begin_dir
26791 connections for (e.g.) more secure hidden service posting and
26793 - More progress on proposal 114: code from Karsten Loesing to
26794 implement new hidden service descriptor format.
26795 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
26796 accommodate the growing number of servers that use the default
26797 and are reaching it.
26798 - Directory authorities use a new formula for selecting which nodes
26799 to advertise as Guards: they must be in the top 7/8 in terms of
26800 how long we have known about them, and above the median of those
26801 nodes in terms of weighted fractional uptime.
26802 - Make "not enough dir info yet" warnings describe *why* Tor feels
26803 it doesn't have enough directory info yet.
26806 - Stop servers from crashing if they set a Family option (or
26807 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
26809 - Make bridge users work again -- the move to v3 directories in
26810 0.2.0.9-alpha had introduced a number of bugs that made bridges
26811 no longer work for clients.
26812 - When the clock jumps forward a lot, do not allow the bandwidth
26813 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
26815 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
26816 - When the consensus lists a router descriptor that we previously were
26817 mirroring, but that we considered non-canonical, reload the
26818 descriptor as canonical. This fixes bug 543 where Tor servers
26819 would start complaining after a few days that they don't have
26820 enough directory information to build a circuit.
26821 - Consider replacing the current consensus when certificates arrive
26822 that make the pending consensus valid. Previously, we were only
26823 considering replacement when the new certs _didn't_ help.
26824 - Fix an assert error on startup if we didn't already have the
26825 consensus and certs cached in our datadirectory: we were caching
26826 the consensus in consensus_waiting_for_certs but then free'ing it
26828 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
26829 Request) if we need more v3 certs but we've already got pending
26830 requests for all of them.
26831 - Correctly back off from failing certificate downloads. Fixes
26833 - Authorities don't vote on the Running flag if they have been running
26834 for less than 30 minutes themselves. Fixes bug 547, where a newly
26835 started authority would vote that everyone was down.
26837 o New requirements:
26838 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
26839 it, it had no AES, and it hasn't seen any security patches since
26843 - Clients now hold circuitless TLS connections open for 1.5 times
26844 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
26845 rebuild a new circuit over them within that timeframe. Previously,
26846 they held them open only for KeepalivePeriod (5 minutes).
26847 - Use "If-Modified-Since" to avoid retrieving consensus
26848 networkstatuses that we already have.
26849 - When we have no consensus, check FallbackNetworkstatusFile (defaults
26850 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
26851 we start knowing some directory caches.
26852 - When we receive a consensus from the future, warn about skew.
26853 - Improve skew reporting: try to give the user a better log message
26854 about how skewed they are, and how much this matters.
26855 - When we have a certificate for an authority, believe that
26856 certificate's claims about the authority's IP address.
26857 - New --quiet command-line option to suppress the default console log.
26858 Good in combination with --hash-password.
26859 - Authorities send back an X-Descriptor-Not-New header in response to
26860 an accepted-but-discarded descriptor upload. Partially implements
26862 - Make the log message for "tls error. breaking." more useful.
26863 - Better log messages about certificate downloads, to attempt to
26864 track down the second incarnation of bug 546.
26866 o Minor features (bridges):
26867 - If bridge users set UpdateBridgesFromAuthority, but the digest
26868 they ask for is a 404 from the bridge authority, they now fall
26869 back to trying the bridge directly.
26870 - Bridges now use begin_dir to publish their server descriptor to
26871 the bridge authority, even when they haven't set TunnelDirConns.
26873 o Minor features (controller):
26874 - When reporting clock skew, and we know that the clock is _at least
26875 as skewed_ as some value, but we don't know the actual value,
26876 report the value as a "minimum skew."
26879 - Update linux-tor-prio.sh script to allow QoS based on the uid of
26880 the Tor process. Patch from Marco Bonetti with tweaks from Mike
26884 - Refuse to start if both ORPort and UseBridges are set. Bugfix
26885 on 0.2.0.x, suggested by Matt Edman.
26886 - Don't stop fetching descriptors when FetchUselessDescriptors is
26887 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
26888 reported by tup and ioerror.
26889 - Better log message on vote from unknown authority.
26890 - Don't log "Launching 0 request for 0 router" message.
26892 o Minor bugfixes (memory leaks):
26893 - Stop leaking memory every time we parse a v3 certificate. Bugfix
26895 - Stop leaking memory every time we load a v3 certificate. Bugfix
26896 on 0.2.0.1-alpha. Fixes bug 536.
26897 - Stop leaking a cached networkstatus on exit. Bugfix on
26899 - Stop leaking voter information every time we free a consensus.
26900 Bugfix on 0.2.0.3-alpha.
26901 - Stop leaking signed data every time we check a voter signature.
26902 Bugfix on 0.2.0.3-alpha.
26903 - Stop leaking a signature every time we fail to parse a consensus or
26904 a vote. Bugfix on 0.2.0.3-alpha.
26905 - Stop leaking v2_download_status_map on shutdown. Bugfix on
26907 - Stop leaking conn->nickname every time we make a connection to a
26908 Tor relay without knowing its expected identity digest (e.g. when
26909 using bridges). Bugfix on 0.2.0.3-alpha.
26911 - Minor bugfixes (portability):
26912 - Run correctly on platforms where rlim_t is larger than unsigned
26913 long, and/or where the real limit for number of open files is
26914 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
26915 particular, these may be needed for OS X 10.5.
26918 Changes in version 0.1.2.18 - 2007-10-28
26919 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
26920 hidden service introduction that were causing huge delays, and a big
26921 bug that was causing some servers to disappear from the network status
26922 lists for a few hours each day.
26924 o Major bugfixes (crashes):
26925 - If a connection is shut down abruptly because of something that
26926 happened inside connection_flushed_some(), do not call
26927 connection_finished_flushing(). Should fix bug 451:
26928 "connection_stop_writing: Assertion conn->write_event failed"
26929 Bugfix on 0.1.2.7-alpha.
26930 - Fix possible segfaults in functions called from
26931 rend_process_relay_cell().
26933 o Major bugfixes (hidden services):
26934 - Hidden services were choosing introduction points uniquely by
26935 hexdigest, but when constructing the hidden service descriptor
26936 they merely wrote the (potentially ambiguous) nickname.
26937 - Clients now use the v2 intro format for hidden service
26938 connections: they specify their chosen rendezvous point by identity
26939 digest rather than by (potentially ambiguous) nickname. These
26940 changes could speed up hidden service connections dramatically.
26942 o Major bugfixes (other):
26943 - Stop publishing a new server descriptor just because we get a
26944 HUP signal. This led (in a roundabout way) to some servers getting
26945 dropped from the networkstatus lists for a few hours each day.
26946 - When looking for a circuit to cannibalize, consider family as well
26947 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
26948 circuit cannibalization).
26949 - When a router wasn't listed in a new networkstatus, we were leaving
26950 the flags for that router alone -- meaning it remained Named,
26951 Running, etc -- even though absence from the networkstatus means
26952 that it shouldn't be considered to exist at all anymore. Now we
26953 clear all the flags for routers that fall out of the networkstatus
26954 consensus. Fixes bug 529.
26957 - Don't try to access (or alter) the state file when running
26958 --list-fingerprint or --verify-config or --hash-password. Resolves
26960 - When generating information telling us how to extend to a given
26961 router, do not try to include the nickname if it is
26962 absent. Resolves bug 467.
26963 - Fix a user-triggerable segfault in expand_filename(). (There isn't
26964 a way to trigger this remotely.)
26965 - When sending a status event to the controller telling it that an
26966 OR address is reachable, set the port correctly. (Previously we
26967 were reporting the dir port.)
26968 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
26969 command. Bugfix on 0.1.2.17.
26970 - When loading bandwidth history, do not believe any information in
26971 the future. Fixes bug 434.
26972 - When loading entry guard information, do not believe any information
26974 - When we have our clock set far in the future and generate an
26975 onion key, then re-set our clock to be correct, we should not stop
26976 the onion key from getting rotated.
26977 - On some platforms, accept() can return a broken address. Detect
26978 this more quietly, and deal accordingly. Fixes bug 483.
26979 - It's not actually an error to find a non-pending entry in the DNS
26980 cache when canceling a pending resolve. Don't log unless stuff
26981 is fishy. Resolves bug 463.
26982 - Don't reset trusted dir server list when we set a configuration
26983 option. Patch from Robert Hogan.
26984 - Don't try to create the datadir when running --verify-config or
26985 --hash-password. Resolves bug 540.
26988 Changes in version 0.2.0.9-alpha - 2007-10-24
26989 This ninth development snapshot switches clients to the new v3 directory
26990 system; allows servers to be listed in the network status even when they
26991 have the same nickname as a registered server; and fixes many other
26992 bugs including a big one that was causing some servers to disappear
26993 from the network status lists for a few hours each day.
26995 o Major features (directory system):
26996 - Clients now download v3 consensus networkstatus documents instead
26997 of v2 networkstatus documents. Clients and caches now base their
26998 opinions about routers on these consensus documents. Clients only
26999 download router descriptors listed in the consensus.
27000 - Authorities now list servers who have the same nickname as
27001 a different named server, but list them with a new flag,
27002 "Unnamed". Now we can list servers that happen to pick the same
27003 nickname as a server that registered two years ago and then
27004 disappeared. Partially implements proposal 122.
27005 - If the consensus lists a router as "Unnamed", the name is assigned
27006 to a different router: do not identify the router by that name.
27007 Partially implements proposal 122.
27008 - Authorities can now come to a consensus on which method to use to
27009 compute the consensus. This gives us forward compatibility.
27012 - Stop publishing a new server descriptor just because we HUP or
27013 when we find our DirPort to be reachable but won't actually publish
27014 it. New descriptors without any real changes are dropped by the
27015 authorities, and can screw up our "publish every 18 hours" schedule.
27017 - When a router wasn't listed in a new networkstatus, we were leaving
27018 the flags for that router alone -- meaning it remained Named,
27019 Running, etc -- even though absence from the networkstatus means
27020 that it shouldn't be considered to exist at all anymore. Now we
27021 clear all the flags for routers that fall out of the networkstatus
27022 consensus. Fixes bug 529; bugfix on 0.1.2.x.
27023 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
27024 extrainfo documents and then discard them immediately for not
27025 matching the latest router. Bugfix on 0.2.0.1-alpha.
27027 o Minor features (v3 directory protocol):
27028 - Allow tor-gencert to generate a new certificate without replacing
27030 - Allow certificates to include an address.
27031 - When we change our directory-cache settings, reschedule all voting
27032 and download operations.
27033 - Reattempt certificate downloads immediately on failure, as long as
27034 we haven't failed a threshold number of times yet.
27035 - Delay retrying consensus downloads while we're downloading
27036 certificates to verify the one we just got. Also, count getting a
27037 consensus that we already have (or one that isn't valid) as a failure,
27038 and count failing to get the certificates after 20 minutes as a
27040 - Build circuits and download descriptors even if our consensus is a
27041 little expired. (This feature will go away once authorities are
27044 o Minor features (router descriptor cache):
27045 - If we find a cached-routers file that's been sitting around for more
27046 than 28 days unmodified, then most likely it's a leftover from
27047 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
27049 - When we (as a cache) download a descriptor because it was listed
27050 in a consensus, remember when the consensus was supposed to expire,
27051 and don't expire the descriptor until then.
27053 o Minor features (performance):
27054 - Call routerlist_remove_old_routers() much less often. This should
27055 speed startup, especially on directory caches.
27056 - Don't try to launch new descriptor downloads quite so often when we
27057 already have enough directory information to build circuits.
27058 - Base64 decoding was actually showing up on our profile when parsing
27059 the initial descriptor file; switch to an in-process all-at-once
27060 implementation that's about 3.5x times faster than calling out to
27063 o Minor features (compilation):
27064 - Detect non-ASCII platforms (if any still exist) and refuse to
27065 build there: some of our code assumes that 'A' is 65 and so on.
27067 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
27068 - Make the "next period" votes into "current period" votes immediately
27069 after publishing the consensus; avoid a heisenbug that made them
27070 stick around indefinitely.
27071 - When we discard a vote as a duplicate, do not report this as
27073 - Treat missing v3 keys or certificates as an error when running as a
27074 v3 directory authority.
27075 - When we're configured to be a v3 authority, but we're only listed
27076 as a non-v3 authority in our DirServer line for ourself, correct
27078 - If an authority doesn't have a qualified hostname, just put
27079 its address in the vote. This fixes the problem where we referred to
27080 "moria on moria:9031."
27081 - Distinguish between detached signatures for the wrong period, and
27082 detached signatures for a divergent vote.
27083 - Fix a small memory leak when computing a consensus.
27084 - When there's no consensus, we were forming a vote every 30
27085 minutes, but writing the "valid-after" line in our vote based
27086 on our configured V3AuthVotingInterval: so unless the intervals
27087 matched up, we immediately rejected our own vote because it didn't
27088 start at the voting interval that caused us to construct a vote.
27090 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
27091 - Delete unverified-consensus when the real consensus is set.
27092 - Consider retrying a consensus networkstatus fetch immediately
27093 after one fails: don't wait 60 seconds to notice.
27094 - When fetching a consensus as a cache, wait until a newer consensus
27095 should exist before trying to replace the current one.
27096 - Use a more forgiving schedule for retrying failed consensus
27097 downloads than for other types.
27099 o Minor bugfixes (other directory issues):
27100 - Correct the implementation of "download votes by digest." Bugfix on
27102 - Authorities no longer send back "400 you're unreachable please fix
27103 it" errors to Tor servers that aren't online all the time. We're
27104 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
27106 o Minor bugfixes (controller):
27107 - Don't reset trusted dir server list when we set a configuration
27108 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
27109 - Respond to INT and TERM SIGNAL commands before we execute the
27110 signal, in case the signal shuts us down. We had a patch in
27111 0.1.2.1-alpha that tried to do this by queueing the response on
27112 the connection's buffer before shutting down, but that really
27113 isn't the same thing at all. Bug located by Matt Edman.
27115 o Minor bugfixes (misc):
27116 - Correctly check for bad options to the "PublishServerDescriptor"
27117 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
27118 - Stop leaking memory on failing case of base32_decode, and make
27119 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
27120 - Don't try to download extrainfo documents when we're trying to
27121 fetch enough directory info to build a circuit: having enough
27122 info should get priority. Bugfix on 0.2.0.x.
27123 - Don't complain that "your server has not managed to confirm that its
27124 ports are reachable" if we haven't been able to build any circuits
27125 yet. Bug found by spending four hours without a v3 consensus. Bugfix
27127 - Detect the reason for failing to mmap a descriptor file we just
27128 wrote, and give a more useful log message. Fixes bug 533. Bugfix
27131 o Code simplifications and refactoring:
27132 - Remove support for the old bw_accounting file: we've been storing
27133 bandwidth accounting information in the state file since
27134 0.1.2.5-alpha. This may result in bandwidth accounting errors
27135 if you try to upgrade from 0.1.1.x or earlier, or if you try to
27136 downgrade to 0.1.1.x or earlier.
27137 - New convenience code to locate a file within the DataDirectory.
27138 - Move non-authority functionality out of dirvote.c.
27139 - Refactor the arguments for router_pick_{directory_|trusteddir}server
27140 so that they all take the same named flags.
27143 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
27144 Unix users an easy way to script their Tor process (e.g. by
27145 adjusting bandwidth based on the time of the day).
27148 Changes in version 0.2.0.8-alpha - 2007-10-12
27149 This eighth development snapshot fixes a crash bug that's been bothering
27150 us since February 2007, lets bridge authorities store a list of bridge
27151 descriptors they've seen, gets v3 directory voting closer to working,
27152 starts caching v3 directory consensus documents on directory mirrors,
27153 and fixes a variety of smaller issues including some minor memory leaks.
27155 o Major features (router descriptor cache):
27156 - Store routers in a file called cached-descriptors instead of in
27157 cached-routers. Initialize cached-descriptors from cached-routers
27158 if the old format is around. The new format allows us to store
27159 annotations along with descriptors.
27160 - Use annotations to record the time we received each descriptor, its
27161 source, and its purpose.
27162 - Disable the SETROUTERPURPOSE controller command: it is now
27164 - Controllers should now specify cache=no or cache=yes when using
27165 the +POSTDESCRIPTOR command.
27166 - Bridge authorities now write bridge descriptors to disk, meaning
27167 we can export them to other programs and begin distributing them
27170 o Major features (directory authorities):
27171 - When a v3 authority is missing votes or signatures, it now tries
27173 - Directory authorities track weighted fractional uptime as well as
27174 weighted mean-time-between failures. WFU is suitable for deciding
27175 whether a node is "usually up", while MTBF is suitable for deciding
27176 whether a node is "likely to stay up." We need both, because
27177 "usually up" is a good requirement for guards, while "likely to
27178 stay up" is a good requirement for long-lived connections.
27180 o Major features (v3 directory system):
27181 - Caches now download v3 network status documents as needed,
27182 and download the descriptors listed in them.
27183 - All hosts now attempt to download and keep fresh v3 authority
27184 certificates, and re-attempt after failures.
27185 - More internal-consistency checks for vote parsing.
27187 o Major bugfixes (crashes):
27188 - If a connection is shut down abruptly because of something that
27189 happened inside connection_flushed_some(), do not call
27190 connection_finished_flushing(). Should fix bug 451. Bugfix on
27193 o Major bugfixes (performance):
27194 - Fix really bad O(n^2) performance when parsing a long list of
27195 routers: Instead of searching the entire list for an "extra-info "
27196 string which usually wasn't there, once for every routerinfo
27197 we read, just scan lines forward until we find one we like.
27199 - When we add data to a write buffer in response to the data on that
27200 write buffer getting low because of a flush, do not consider the
27201 newly added data as a candidate for immediate flushing, but rather
27202 make it wait until the next round of writing. Otherwise, we flush
27203 and refill recursively, and a single greedy TLS connection can
27204 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
27206 o Minor features (v3 authority system):
27207 - Add more ways for tools to download the votes that lead to the
27209 - Send a 503 when low on bandwidth and a vote, consensus, or
27210 certificate is requested.
27211 - If-modified-since is now implemented properly for all kinds of
27212 certificate requests.
27214 o Minor bugfixes (network statuses):
27215 - Tweak the implementation of proposal 109 slightly: allow at most
27216 two Tor servers on the same IP address, except if it's the location
27217 of a directory authority, in which case allow five. Bugfix on
27220 o Minor bugfixes (controller):
27221 - When sending a status event to the controller telling it that an
27222 OR address is reachable, set the port correctly. (Previously we
27223 were reporting the dir port.) Bugfix on 0.1.2.x.
27225 o Minor bugfixes (v3 directory system):
27226 - Fix logic to look up a cert by its signing key digest. Bugfix on
27228 - Only change the reply to a vote to "OK" if it's not already
27229 set. This gets rid of annoying "400 OK" log messages, which may
27230 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
27231 - When we get a valid consensus, recompute the voting schedule.
27232 - Base the valid-after time of a vote on the consensus voting
27233 schedule, not on our preferred schedule.
27234 - Make the return values and messages from signature uploads and
27235 downloads more sensible.
27236 - Fix a memory leak when serving votes and consensus documents, and
27237 another when serving certificates.
27239 o Minor bugfixes (performance):
27240 - Use a slightly simpler string hashing algorithm (copying Python's
27241 instead of Java's) and optimize our digest hashing algorithm to take
27242 advantage of 64-bit platforms and to remove some possibly-costly
27244 - Fix a minor memory leak whenever we parse guards from our state
27245 file. Bugfix on 0.2.0.7-alpha.
27246 - Fix a minor memory leak whenever we write out a file. Bugfix on
27248 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27249 command. Bugfix on 0.2.0.5-alpha.
27251 o Minor bugfixes (portability):
27252 - On some platforms, accept() can return a broken address. Detect
27253 this more quietly, and deal accordingly. Fixes bug 483.
27254 - Stop calling tor_strlower() on uninitialized memory in some cases.
27255 Bugfix in 0.2.0.7-alpha.
27257 o Minor bugfixes (usability):
27258 - Treat some 403 responses from directory servers as INFO rather than
27259 WARN-severity events.
27260 - It's not actually an error to find a non-pending entry in the DNS
27261 cache when canceling a pending resolve. Don't log unless stuff is
27262 fishy. Resolves bug 463.
27264 o Minor bugfixes (anonymity):
27265 - Never report that we've used more bandwidth than we're willing to
27266 relay: it leaks how much non-relay traffic we're using. Resolves
27268 - When looking for a circuit to cannibalize, consider family as well
27269 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27270 circuit cannibalization).
27272 o Code simplifications and refactoring:
27273 - Make a bunch of functions static. Remove some dead code.
27274 - Pull out about a third of the really big routerlist.c; put it in a
27275 new module, networkstatus.c.
27276 - Merge the extra fields in local_routerstatus_t back into
27277 routerstatus_t: we used to need one routerstatus_t for each
27278 authority's opinion, plus a local_routerstatus_t for the locally
27279 computed consensus opinion. To save space, we put the locally
27280 modified fields into local_routerstatus_t, and only the common
27281 stuff into routerstatus_t. But once v3 directories are in use,
27282 clients and caches will no longer need to hold authority opinions;
27283 thus, the rationale for keeping the types separate is now gone.
27284 - Make the code used to reschedule and reattempt downloads more
27286 - Turn all 'Are we a directory server/mirror?' logic into a call to
27288 - Remove the code to generate the oldest (v1) directory format.
27289 The code has been disabled since 0.2.0.5-alpha.
27292 Changes in version 0.2.0.7-alpha - 2007-09-21
27293 This seventh development snapshot makes bridges work again, makes bridge
27294 authorities work for the first time, fixes two huge performance flaws
27295 in hidden services, and fixes a variety of minor issues.
27297 o New directory authorities:
27298 - Set up moria1 and tor26 as the first v3 directory authorities. See
27299 doc/spec/dir-spec.txt for details on the new directory design.
27301 o Major bugfixes (crashes):
27302 - Fix possible segfaults in functions called from
27303 rend_process_relay_cell(). Bugfix on 0.1.2.x.
27305 o Major bugfixes (bridges):
27306 - Fix a bug that made servers send a "404 Not found" in response to
27307 attempts to fetch their server descriptor. This caused Tor servers
27308 to take many minutes to establish reachability for their DirPort,
27309 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
27310 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
27311 users configure that and specify a bridge with an identity
27312 fingerprint, now they will lookup the bridge descriptor at the
27313 default bridge authority via a one-hop tunnel, but once circuits
27314 are established they will switch to a three-hop tunnel for later
27315 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
27317 o Major bugfixes (hidden services):
27318 - Hidden services were choosing introduction points uniquely by
27319 hexdigest, but when constructing the hidden service descriptor
27320 they merely wrote the (potentially ambiguous) nickname.
27321 - Clients now use the v2 intro format for hidden service
27322 connections: they specify their chosen rendezvous point by identity
27323 digest rather than by (potentially ambiguous) nickname. Both
27324 are bugfixes on 0.1.2.x, and they could speed up hidden service
27325 connections dramatically. Thanks to Karsten Loesing.
27327 o Minor features (security):
27328 - As a client, do not believe any server that tells us that an
27329 address maps to an internal address space.
27330 - Make it possible to enable HashedControlPassword and
27331 CookieAuthentication at the same time.
27333 o Minor features (guard nodes):
27334 - Tag every guard node in our state file with the version that
27335 we believe added it, or with our own version if we add it. This way,
27336 if a user temporarily runs an old version of Tor and then switches
27337 back to a new one, she doesn't automatically lose her guards.
27339 o Minor features (speed):
27340 - When implementing AES counter mode, update only the portions of the
27341 counter buffer that need to change, and don't keep separate
27342 network-order and host-order counters when they are the same (i.e.,
27343 on big-endian hosts.)
27345 o Minor features (controller):
27346 - Accept LF instead of CRLF on controller, since some software has a
27347 hard time generating real Internet newlines.
27348 - Add GETINFO values for the server status events
27349 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
27352 o Removed features:
27353 - Routers no longer include bandwidth-history lines in their
27354 descriptors; this information is already available in extra-info
27355 documents, and including it in router descriptors took up 60%
27356 (!) of compressed router descriptor downloads. Completes
27357 implementation of proposal 104.
27358 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
27359 and TorControl.py, as they use the old v0 controller protocol,
27360 and are obsoleted by TorFlow anyway.
27361 - Drop support for v1 rendezvous descriptors, since we never used
27362 them anyway, and the code has probably rotted by now. Based on
27363 patch from Karsten Loesing.
27364 - On OSX, stop warning the user that kqueue support in libevent is
27365 "experimental", since it seems to have worked fine for ages.
27368 - When generating information telling us how to extend to a given
27369 router, do not try to include the nickname if it is absent. Fixes
27370 bug 467. Bugfix on 0.2.0.3-alpha.
27371 - Fix a user-triggerable (but not remotely-triggerable) segfault
27372 in expand_filename(). Bugfix on 0.1.2.x.
27373 - Fix a memory leak when freeing incomplete requests from DNSPort.
27374 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
27375 - Don't try to access (or alter) the state file when running
27376 --list-fingerprint or --verify-config or --hash-password. (Resolves
27377 bug 499.) Bugfix on 0.1.2.x.
27378 - Servers used to decline to publish their DirPort if their
27379 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
27380 were below a threshold. Now they only look at BandwidthRate and
27381 RelayBandwidthRate. Bugfix on 0.1.2.x.
27382 - Remove an optimization in the AES counter-mode code that assumed
27383 that the counter never exceeded 2^68. When the counter can be set
27384 arbitrarily as an IV (as it is by Karsten's new hidden services
27385 code), this assumption no longer holds. Bugfix on 0.1.2.x.
27386 - Resume listing "AUTHORITY" flag for authorities in network status.
27387 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
27389 o Code simplifications and refactoring:
27390 - Revamp file-writing logic so we don't need to have the entire
27391 contents of a file in memory at once before we write to disk. Tor,
27393 - Turn "descriptor store" into a full-fledged type.
27394 - Move all NT services code into a separate source file.
27395 - Unify all code that computes medians, percentile elements, etc.
27396 - Get rid of a needless malloc when parsing address policies.
27399 Changes in version 0.1.2.17 - 2007-08-30
27400 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
27401 X bundles. Vidalia 0.0.14 makes authentication required for the
27402 ControlPort in the default configuration, which addresses important
27403 security risks. Everybody who uses Vidalia (or another controller)
27406 In addition, this Tor update fixes major load balancing problems with
27407 path selection, which should speed things up a lot once many people
27410 o Major bugfixes (security):
27411 - We removed support for the old (v0) control protocol. It has been
27412 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
27413 become more of a headache than it's worth.
27415 o Major bugfixes (load balancing):
27416 - When choosing nodes for non-guard positions, weight guards
27417 proportionally less, since they already have enough load. Patch
27419 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27420 will allow fast Tor servers to get more attention.
27421 - When we're upgrading from an old Tor version, forget our current
27422 guards and pick new ones according to the new weightings. These
27423 three load balancing patches could raise effective network capacity
27424 by a factor of four. Thanks to Mike Perry for measurements.
27426 o Major bugfixes (stream expiration):
27427 - Expire not-yet-successful application streams in all cases if
27428 they've been around longer than SocksTimeout. Right now there are
27429 some cases where the stream will live forever, demanding a new
27430 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27432 o Minor features (controller):
27433 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27434 is valid before any authentication has been received. It tells
27435 a controller what kind of authentication is expected, and what
27436 protocol is spoken. Implements proposal 119.
27438 o Minor bugfixes (performance):
27439 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27440 greatly speeding up loading cached-routers from disk on startup.
27441 - Disable sentinel-based debugging for buffer code: we squashed all
27442 the bugs that this was supposed to detect a long time ago, and now
27443 its only effect is to change our buffer sizes from nice powers of
27444 two (which platform mallocs tend to like) to values slightly over
27445 powers of two (which make some platform mallocs sad).
27447 o Minor bugfixes (misc):
27448 - If exit bandwidth ever exceeds one third of total bandwidth, then
27449 use the correct formula to weight exit nodes when choosing paths.
27450 Based on patch from Mike Perry.
27451 - Choose perfectly fairly among routers when choosing by bandwidth and
27452 weighting by fraction of bandwidth provided by exits. Previously, we
27453 would choose with only approximate fairness, and correct ourselves
27454 if we ran off the end of the list.
27455 - If we require CookieAuthentication but we fail to write the
27456 cookie file, we would warn but not exit, and end up in a state
27457 where no controller could authenticate. Now we exit.
27458 - If we require CookieAuthentication, stop generating a new cookie
27459 every time we change any piece of our config.
27460 - Refuse to start with certain directory authority keys, and
27461 encourage people using them to stop.
27462 - Terminate multi-line control events properly. Original patch
27464 - Fix a minor memory leak when we fail to find enough suitable
27465 servers to choose a circuit.
27466 - Stop leaking part of the descriptor when we run into a particularly
27467 unparseable piece of it.
27470 Changes in version 0.2.0.6-alpha - 2007-08-26
27471 This sixth development snapshot features a new Vidalia version in the
27472 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27473 the ControlPort in the default configuration, which addresses important
27476 In addition, this snapshot fixes major load balancing problems
27477 with path selection, which should speed things up a lot once many
27478 people have upgraded. The directory authorities also use a new
27479 mean-time-between-failure approach to tracking which servers are stable,
27480 rather than just looking at the most recent uptime.
27482 o New directory authorities:
27483 - Set up Tonga as the default bridge directory authority.
27486 - Directory authorities now track servers by weighted
27487 mean-times-between-failures. When we have 4 or more days of data,
27488 use measured MTBF rather than declared uptime to decide whether
27489 to call a router Stable. Implements proposal 108.
27491 o Major bugfixes (load balancing):
27492 - When choosing nodes for non-guard positions, weight guards
27493 proportionally less, since they already have enough load. Patch
27495 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27496 will allow fast Tor servers to get more attention.
27497 - When we're upgrading from an old Tor version, forget our current
27498 guards and pick new ones according to the new weightings. These
27499 three load balancing patches could raise effective network capacity
27500 by a factor of four. Thanks to Mike Perry for measurements.
27502 o Major bugfixes (descriptor parsing):
27503 - Handle unexpected whitespace better in malformed descriptors. Bug
27504 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27507 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27508 GETINFO for Torstat to use until it can switch to using extrainfos.
27509 - Optionally (if built with -DEXPORTMALLINFO) export the output
27510 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27514 - Do not intermix bridge routers with controller-added
27515 routers. (Bugfix on 0.2.0.x)
27516 - Do not fail with an assert when accept() returns an unexpected
27517 address family. Addresses but does not wholly fix bug 483. (Bugfix
27519 - Let directory authorities startup even when they can't generate
27520 a descriptor immediately, e.g. because they don't know their
27522 - Stop putting the authentication cookie in a file called "0"
27523 in your working directory if you don't specify anything for the
27524 new CookieAuthFile option. Reported by Matt Edman.
27525 - Make it possible to read the PROTOCOLINFO response in a way that
27526 conforms to our control-spec. Reported by Matt Edman.
27527 - Fix a minor memory leak when we fail to find enough suitable
27528 servers to choose a circuit. Bugfix on 0.1.2.x.
27529 - Stop leaking part of the descriptor when we run into a particularly
27530 unparseable piece of it. Bugfix on 0.1.2.x.
27531 - Unmap the extrainfo cache file on exit.
27534 Changes in version 0.2.0.5-alpha - 2007-08-19
27535 This fifth development snapshot fixes compilation on Windows again;
27536 fixes an obnoxious client-side bug that slowed things down and put
27537 extra load on the network; gets us closer to using the v3 directory
27538 voting scheme; makes it easier for Tor controllers to use cookie-based
27539 authentication; and fixes a variety of other bugs.
27541 o Removed features:
27542 - Version 1 directories are no longer generated in full. Instead,
27543 authorities generate and serve "stub" v1 directories that list
27544 no servers. This will stop Tor versions 0.1.0.x and earlier from
27545 working, but (for security reasons) nobody should be running those
27548 o Major bugfixes (compilation, 0.2.0.x):
27549 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27550 - Try to fix MSVC compilation: build correctly on platforms that do
27551 not define s6_addr16 or s6_addr32.
27552 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27555 o Major bugfixes (stream expiration):
27556 - Expire not-yet-successful application streams in all cases if
27557 they've been around longer than SocksTimeout. Right now there are
27558 some cases where the stream will live forever, demanding a new
27559 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27560 reported by lodger.
27562 o Minor features (directory servers):
27563 - When somebody requests a list of statuses or servers, and we have
27564 none of those, return a 404 rather than an empty 200.
27566 o Minor features (directory voting):
27567 - Store v3 consensus status consensuses on disk, and reload them
27570 o Minor features (security):
27571 - Warn about unsafe ControlPort configurations.
27572 - Refuse to start with certain directory authority keys, and
27573 encourage people using them to stop.
27575 o Minor features (controller):
27576 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27577 is valid before any authentication has been received. It tells
27578 a controller what kind of authentication is expected, and what
27579 protocol is spoken. Implements proposal 119.
27580 - New config option CookieAuthFile to choose a new location for the
27581 cookie authentication file, and config option
27582 CookieAuthFileGroupReadable to make it group-readable.
27584 o Minor features (unit testing):
27585 - Add command-line arguments to unit-test executable so that we can
27586 invoke any chosen test from the command line rather than having
27587 to run the whole test suite at once; and so that we can turn on
27588 logging for the unit tests.
27590 o Minor bugfixes (on 0.1.2.x):
27591 - If we require CookieAuthentication but we fail to write the
27592 cookie file, we would warn but not exit, and end up in a state
27593 where no controller could authenticate. Now we exit.
27594 - If we require CookieAuthentication, stop generating a new cookie
27595 every time we change any piece of our config.
27596 - When loading bandwidth history, do not believe any information in
27597 the future. Fixes bug 434.
27598 - When loading entry guard information, do not believe any information
27600 - When we have our clock set far in the future and generate an
27601 onion key, then re-set our clock to be correct, we should not stop
27602 the onion key from getting rotated.
27603 - Clean up torrc sample config file.
27604 - Do not automatically run configure from autogen.sh. This
27605 non-standard behavior tended to annoy people who have built other
27608 o Minor bugfixes (on 0.2.0.x):
27609 - Fix a bug with AutomapHostsOnResolve that would always cause
27610 the second request to fail. Bug reported by Kate. Bugfix on
27612 - Fix a bug in ADDRMAP controller replies that would sometimes
27613 try to print a NULL. Patch from tup.
27614 - Read v3 directory authority keys from the right location.
27615 - Numerous bugfixes to directory voting code.
27618 Changes in version 0.1.2.16 - 2007-08-01
27619 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27620 remote attacker in certain situations to rewrite the user's torrc
27621 configuration file. This can completely compromise anonymity of users
27622 in most configurations, including those running the Vidalia bundles,
27623 TorK, etc. Or worse.
27625 o Major security fixes:
27626 - Close immediately after missing authentication on control port;
27627 do not allow multiple authentication attempts.
27630 Changes in version 0.2.0.4-alpha - 2007-08-01
27631 This fourth development snapshot fixes a critical security vulnerability
27632 for most users, specifically those running Vidalia, TorK, etc. Everybody
27633 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
27635 o Major security fixes:
27636 - Close immediately after missing authentication on control port;
27637 do not allow multiple authentication attempts.
27639 o Major bugfixes (compilation):
27640 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
27643 o Minor features (performance):
27644 - Be even more aggressive about releasing RAM from small
27645 empty buffers. Thanks to our free-list code, this shouldn't be too
27646 performance-intensive.
27647 - Disable sentinel-based debugging for buffer code: we squashed all
27648 the bugs that this was supposed to detect a long time ago, and
27649 now its only effect is to change our buffer sizes from nice
27650 powers of two (which platform mallocs tend to like) to values
27651 slightly over powers of two (which make some platform mallocs sad).
27652 - Log malloc statistics from mallinfo() on platforms where it
27656 Changes in version 0.2.0.3-alpha - 2007-07-29
27657 This third development snapshot introduces new experimental
27658 blocking-resistance features and a preliminary version of the v3
27659 directory voting design, and includes many other smaller features
27663 - The first pieces of our "bridge" design for blocking-resistance
27664 are implemented. People can run bridge directory authorities;
27665 people can run bridges; and people can configure their Tor clients
27666 with a set of bridges to use as the first hop into the Tor network.
27667 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
27669 - Create listener connections before we setuid to the configured
27670 User and Group. Now non-Windows users can choose port values
27671 under 1024, start Tor as root, and have Tor bind those ports
27672 before it changes to another UID. (Windows users could already
27674 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
27675 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
27676 on "vserver" accounts. (Patch from coderman.)
27677 - Be even more aggressive about separating local traffic from relayed
27678 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
27680 o Major features (experimental):
27681 - First cut of code for "v3 dir voting": directory authorities will
27682 vote on a common network status document rather than each publishing
27683 their own opinion. This code needs more testing and more corner-case
27684 handling before it's ready for use.
27687 - Directory authorities now call routers Fast if their bandwidth is
27688 at least 100KB/s, and consider their bandwidth adequate to be a
27689 Guard if it is at least 250KB/s, no matter the medians. This fix
27690 complements proposal 107. [Bugfix on 0.1.2.x]
27691 - Directory authorities now never mark more than 3 servers per IP as
27692 Valid and Running. (Implements proposal 109, by Kevin Bauer and
27694 - Minor change to organizationName and commonName generation
27695 procedures in TLS certificates during Tor handshakes, to invalidate
27696 some earlier censorware approaches. This is not a long-term
27697 solution, but applying it will give us a bit of time to look into
27698 the epidemiology of countermeasures as they spread.
27700 o Major bugfixes (directory):
27701 - Rewrite directory tokenization code to never run off the end of
27702 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
27704 o Minor features (controller):
27705 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
27706 match requests to applications. (Patch from Robert Hogan.)
27707 - Report address and port correctly on connections to DNSPort. (Patch
27708 from Robert Hogan.)
27709 - Add a RESOLVE command to launch hostname lookups. (Original patch
27710 from Robert Hogan.)
27711 - Add GETINFO status/enough-dir-info to let controllers tell whether
27712 Tor has downloaded sufficient directory information. (Patch
27714 - You can now use the ControlSocket option to tell Tor to listen for
27715 controller connections on Unix domain sockets on systems that
27716 support them. (Patch from Peter Palfrader.)
27717 - STREAM NEW events are generated for DNSPort requests and for
27718 tunneled directory connections. (Patch from Robert Hogan.)
27719 - New "GETINFO address-mappings/*" command to get address mappings
27720 with expiry information. "addr-mappings/*" is now deprecated.
27723 o Minor features (misc):
27724 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
27726 - The tor-gencert tool for v3 directory authorities now creates all
27727 files as readable to the file creator only, and write-protects
27728 the authority identity key.
27729 - When dumping memory usage, list bytes used in buffer memory
27731 - When running with dmalloc, dump more stats on hup and on exit.
27732 - Directory authorities now fail quickly and (relatively) harmlessly
27733 if they generate a network status document that is somehow
27736 o Traffic load balancing improvements:
27737 - If exit bandwidth ever exceeds one third of total bandwidth, then
27738 use the correct formula to weight exit nodes when choosing paths.
27739 (Based on patch from Mike Perry.)
27740 - Choose perfectly fairly among routers when choosing by bandwidth and
27741 weighting by fraction of bandwidth provided by exits. Previously, we
27742 would choose with only approximate fairness, and correct ourselves
27743 if we ran off the end of the list. [Bugfix on 0.1.2.x]
27745 o Performance improvements:
27746 - Be more aggressive with freeing buffer RAM or putting it on the
27748 - Use Critical Sections rather than Mutexes for synchronizing threads
27749 on win32; Mutexes are heavier-weight, and designed for synchronizing
27752 o Deprecated and removed features:
27753 - RedirectExits is now deprecated.
27754 - Stop allowing address masks that do not correspond to bit prefixes.
27755 We have warned about these for a really long time; now it's time
27756 to reject them. (Patch from croup.)
27758 o Minor bugfixes (directory):
27759 - Fix another crash bug related to extra-info caching. (Bug found by
27760 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
27761 - Directories no longer return a "304 not modified" when they don't
27762 have the networkstatus the client asked for. Also fix a memory
27763 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
27764 - We had accidentally labelled 0.1.2.x directory servers as not
27765 suitable for begin_dir requests, and had labelled no directory
27766 servers as suitable for uploading extra-info documents. [Bugfix
27769 o Minor bugfixes (dns):
27770 - Fix a crash when DNSPort is set more than once. (Patch from Robert
27771 Hogan.) [Bugfix on 0.2.0.2-alpha]
27772 - Add DNSPort connections to the global connection list, so that we
27773 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
27775 - Fix a dangling reference that could lead to a crash when DNSPort is
27776 changed or closed (Patch from Robert Hogan.) [Bugfix on
27779 o Minor bugfixes (controller):
27780 - Provide DNS expiry times in GMT, not in local time. For backward
27781 compatibility, ADDRMAP events only provide GMT expiry in an extended
27782 field. "GETINFO address-mappings" always does the right thing.
27783 - Use CRLF line endings properly in NS events.
27784 - Terminate multi-line control events properly. (Original patch
27785 from tup.) [Bugfix on 0.1.2.x-alpha]
27786 - Do not include spaces in SOURCE_ADDR fields in STREAM
27787 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
27790 Changes in version 0.1.2.15 - 2007-07-17
27791 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
27792 problems, fixes compilation on BSD, and fixes a variety of other
27793 bugs. Everybody should upgrade.
27795 o Major bugfixes (compilation):
27796 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
27798 o Major bugfixes (crashes):
27799 - Try even harder not to dereference the first character after
27800 an mmap(). Reported by lodger.
27801 - Fix a crash bug in directory authorities when we re-number the
27802 routerlist while inserting a new router.
27803 - When the cached-routers file is an even multiple of the page size,
27804 don't run off the end and crash. (Fixes bug 455; based on idea
27806 - Fix eventdns.c behavior on Solaris: It is critical to include
27807 orconfig.h _before_ sys/types.h, so that we can get the expected
27808 definition of _FILE_OFFSET_BITS.
27810 o Major bugfixes (security):
27811 - Fix a possible buffer overrun when using BSD natd support. Bug
27813 - When sending destroy cells from a circuit's origin, don't include
27814 the reason for tearing down the circuit. The spec says we didn't,
27815 and now we actually don't. Reported by lodger.
27816 - Keep streamids from different exits on a circuit separate. This
27817 bug may have allowed other routers on a given circuit to inject
27818 cells into streams. Reported by lodger; fixes bug 446.
27819 - If there's a never-before-connected-to guard node in our list,
27820 never choose any guards past it. This way we don't expand our
27821 guard list unless we need to.
27823 o Minor bugfixes (guard nodes):
27824 - Weight guard selection by bandwidth, so that low-bandwidth nodes
27825 don't get overused as guards.
27827 o Minor bugfixes (directory):
27828 - Correctly count the number of authorities that recommend each
27829 version. Previously, we were under-counting by 1.
27830 - Fix a potential crash bug when we load many server descriptors at
27831 once and some of them make others of them obsolete. Fixes bug 458.
27833 o Minor bugfixes (hidden services):
27834 - Stop tearing down the whole circuit when the user asks for a
27835 connection to a port that the hidden service didn't configure.
27838 o Minor bugfixes (misc):
27839 - On Windows, we were preventing other processes from reading
27840 cached-routers while Tor was running. Reported by janbar.
27841 - Fix a possible (but very unlikely) bug in picking routers by
27842 bandwidth. Add a log message to confirm that it is in fact
27843 unlikely. Patch from lodger.
27844 - Backport a couple of memory leak fixes.
27845 - Backport miscellaneous cosmetic bugfixes.
27848 Changes in version 0.2.0.2-alpha - 2007-06-02
27849 o Major bugfixes on 0.2.0.1-alpha:
27850 - Fix an assertion failure related to servers without extra-info digests.
27851 Resolves bugs 441 and 442.
27853 o Minor features (directory):
27854 - Support "If-Modified-Since" when answering HTTP requests for
27855 directories, running-routers documents, and network-status documents.
27856 (There's no need to support it for router descriptors, since those
27857 are downloaded by descriptor digest.)
27859 o Minor build issues:
27860 - Clear up some MIPSPro compiler warnings.
27861 - When building from a tarball on a machine that happens to have SVK
27862 installed, report the micro-revision as whatever version existed
27863 in the tarball, not as "x".
27866 Changes in version 0.2.0.1-alpha - 2007-06-01
27867 This early development snapshot provides new features for people running
27868 Tor as both a client and a server (check out the new RelayBandwidth
27869 config options); lets Tor run as a DNS proxy; and generally moves us
27870 forward on a lot of fronts.
27872 o Major features, server usability:
27873 - New config options RelayBandwidthRate and RelayBandwidthBurst:
27874 a separate set of token buckets for relayed traffic. Right now
27875 relayed traffic is defined as answers to directory requests, and
27876 OR connections that don't have any local circuits on them.
27878 o Major features, client usability:
27879 - A client-side DNS proxy feature to replace the need for
27880 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
27881 for DNS requests on port 9999, use the Tor network to resolve them
27882 anonymously, and send the reply back like a regular DNS server.
27883 The code still only implements a subset of DNS.
27884 - Make PreferTunneledDirConns and TunnelDirConns work even when
27885 we have no cached directory info. This means Tor clients can now
27886 do all of their connections protected by TLS.
27888 o Major features, performance and efficiency:
27889 - Directory authorities accept and serve "extra info" documents for
27890 routers. These documents contain fields from router descriptors
27891 that aren't usually needed, and that use a lot of excess
27892 bandwidth. Once these fields are removed from router descriptors,
27893 the bandwidth savings should be about 60%. [Partially implements
27895 - Servers upload extra-info documents to any authority that accepts
27896 them. Authorities (and caches that have been configured to download
27897 extra-info documents) download them as needed. [Partially implements
27899 - Change the way that Tor buffers data that it is waiting to write.
27900 Instead of queueing data cells in an enormous ring buffer for each
27901 client->OR or OR->OR connection, we now queue cells on a separate
27902 queue for each circuit. This lets us use less slack memory, and
27903 will eventually let us be smarter about prioritizing different kinds
27905 - Use memory pools to allocate cells with better speed and memory
27906 efficiency, especially on platforms where malloc() is inefficient.
27907 - Stop reading on edge connections when their corresponding circuit
27908 buffers are full; start again as the circuits empty out.
27910 o Major features, other:
27911 - Add an HSAuthorityRecordStats option that hidden service authorities
27912 can use to track statistics of overall hidden service usage without
27913 logging information that would be very useful to an attacker.
27914 - Start work implementing multi-level keys for directory authorities:
27915 Add a standalone tool to generate key certificates. (Proposal 103.)
27918 - Directory authorities now call routers Stable if they have an
27919 uptime of at least 30 days, even if that's not the median uptime
27920 in the network. Implements proposal 107, suggested by Kevin Bauer
27923 o Minor fixes (resource management):
27924 - Count the number of open sockets separately from the number
27925 of active connection_t objects. This will let us avoid underusing
27926 our allocated connection limit.
27927 - We no longer use socket pairs to link an edge connection to an
27928 anonymous directory connection or a DirPort test connection.
27929 Instead, we track the link internally and transfer the data
27930 in-process. This saves two sockets per "linked" connection (at the
27931 client and at the server), and avoids the nasty Windows socketpair()
27933 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
27934 for every single inactive connection_t. Free items from the
27935 4k/16k-buffer free lists when they haven't been used for a while.
27937 o Minor features (build):
27938 - Make autoconf search for libevent, openssl, and zlib consistently.
27939 - Update deprecated macros in configure.in.
27940 - When warning about missing headers, tell the user to let us
27941 know if the compile succeeds anyway, so we can downgrade the
27943 - Include the current subversion revision as part of the version
27944 string: either fetch it directly if we're in an SVN checkout, do
27945 some magic to guess it if we're in an SVK checkout, or use
27946 the last-detected version if we're building from a .tar.gz.
27947 Use this version consistently in log messages.
27949 o Minor features (logging):
27950 - Always prepend "Bug: " to any log message about a bug.
27951 - Put a platform string (e.g. "Linux i686") in the startup log
27952 message, so when people paste just their logs, we know if it's
27953 OpenBSD or Windows or what.
27954 - When logging memory usage, break down memory used in buffers by
27957 o Minor features (directory system):
27958 - New config option V2AuthoritativeDirectory that all directory
27959 authorities should set. This will let future authorities choose
27960 not to serve V2 directory information.
27961 - Directory authorities allow multiple router descriptors and/or extra
27962 info documents to be uploaded in a single go. This will make
27963 implementing proposal 104 simpler.
27965 o Minor features (controller):
27966 - Add a new config option __DisablePredictedCircuits designed for
27967 use by the controller, when we don't want Tor to build any circuits
27969 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
27970 so we can exit from the middle of the circuit.
27971 - Implement "getinfo status/circuit-established".
27972 - Implement "getinfo status/version/..." so a controller can tell
27973 whether the current version is recommended, and whether any versions
27974 are good, and how many authorities agree. (Patch from shibz.)
27976 o Minor features (hidden services):
27977 - Allow multiple HiddenServicePort directives with the same virtual
27978 port; when they occur, the user is sent round-robin to one
27979 of the target ports chosen at random. Partially fixes bug 393 by
27980 adding limited ad-hoc round-robining.
27982 o Minor features (other):
27984 - Add a new AutomapHostsOnResolve option: when it is enabled, any
27985 resolve request for hosts matching a given pattern causes Tor to
27986 generate an internal virtual address mapping for that host. This
27987 allows DNSPort to work sensibly with hidden service users. By
27988 default, .exit and .onion addresses are remapped; the list of
27989 patterns can be reconfigured with AutomapHostsSuffixes.
27990 - Add an "-F" option to tor-resolve to force a resolve for a .onion
27991 address. Thanks to the AutomapHostsOnResolve option, this is no
27992 longer a completely silly thing to do.
27993 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
27994 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
27995 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
27996 minus 1 byte: the actual maximum declared bandwidth.
27998 o Removed features:
27999 - Removed support for the old binary "version 0" controller protocol.
28000 This has been deprecated since 0.1.1, and warnings have been issued
28001 since 0.1.2. When we encounter a v0 control message, we now send
28002 back an error and close the connection.
28003 - Remove the old "dns worker" server DNS code: it hasn't been default
28004 since 0.1.2.2-alpha, and all the servers seem to be using the new
28007 o Minor bugfixes (portability):
28008 - Even though Windows is equally happy with / and \ as path separators,
28009 try to use \ consistently on Windows and / consistently on Unix: it
28010 makes the log messages nicer.
28011 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
28012 - Read resolv.conf files correctly on platforms where read() returns
28013 partial results on small file reads.
28015 o Minor bugfixes (directory):
28016 - Correctly enforce that elements of directory objects do not appear
28017 more often than they are allowed to appear.
28018 - When we are reporting the DirServer line we just parsed, we were
28019 logging the second stanza of the key fingerprint, not the first.
28021 o Minor bugfixes (logging):
28022 - When we hit an EOF on a log (probably because we're shutting down),
28023 don't try to remove the log from the list: just mark it as
28024 unusable. (Bulletproofs against bug 222.)
28026 o Minor bugfixes (other):
28027 - In the exitlist script, only consider the most recently published
28028 server descriptor for each server. Also, when the user requests
28029 a list of servers that _reject_ connections to a given address,
28030 explicitly exclude the IPs that also have servers that accept
28031 connections to that address. (Resolves bug 405.)
28032 - Stop allowing hibernating servers to be "stable" or "fast".
28033 - On Windows, we were preventing other processes from reading
28034 cached-routers while Tor was running. (Reported by janbar)
28035 - Make the NodeFamilies config option work. (Reported by
28036 lodger -- it has never actually worked, even though we added it
28038 - Check return values from pthread_mutex functions.
28039 - Don't save non-general-purpose router descriptors to the disk cache,
28040 because we have no way of remembering what their purpose was when
28042 - Add even more asserts to hunt down bug 417.
28043 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
28044 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
28045 Add a log message to confirm that it is in fact unlikely.
28047 o Minor bugfixes (controller):
28048 - Make 'getinfo fingerprint' return a 551 error if we're not a
28049 server, so we match what the control spec claims we do. Reported
28051 - Fix a typo in an error message when extendcircuit fails that
28052 caused us to not follow the \r\n-based delimiter protocol. Reported
28055 o Code simplifications and refactoring:
28056 - Stop passing around circuit_t and crypt_path_t pointers that are
28057 implicit in other procedure arguments.
28058 - Drop the old code to choke directory connections when the
28059 corresponding OR connections got full: thanks to the cell queue
28060 feature, OR conns don't get full any more.
28061 - Make dns_resolve() handle attaching connections to circuits
28062 properly, so the caller doesn't have to.
28063 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
28064 - Keep the connection array as a dynamic smartlist_t, rather than as
28065 a fixed-sized array. This is important, as the number of connections
28066 is becoming increasingly decoupled from the number of sockets.
28069 Changes in version 0.1.2.14 - 2007-05-25
28070 Tor 0.1.2.14 changes the addresses of two directory authorities (this
28071 change especially affects those who serve or use hidden services),
28072 and fixes several other crash- and security-related bugs.
28074 o Directory authority changes:
28075 - Two directory authorities (moria1 and moria2) just moved to new
28076 IP addresses. This change will particularly affect those who serve
28077 or use hidden services.
28079 o Major bugfixes (crashes):
28080 - If a directory server runs out of space in the connection table
28081 as it's processing a begin_dir request, it will free the exit stream
28082 but leave it attached to the circuit, leading to unpredictable
28083 behavior. (Reported by seeess, fixes bug 425.)
28084 - Fix a bug in dirserv_remove_invalid() that would cause authorities
28085 to corrupt memory under some really unlikely scenarios.
28086 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
28087 - Avoid segfaults when reading from mmaped descriptor file. (Reported
28090 o Major bugfixes (security):
28091 - When choosing an entry guard for a circuit, avoid using guards
28092 that are in the same family as the chosen exit -- not just guards
28093 that are exactly the chosen exit. (Reported by lodger.)
28095 o Major bugfixes (resource management):
28096 - If a directory authority is down, skip it when deciding where to get
28097 networkstatus objects or descriptors. Otherwise we keep asking
28098 every 10 seconds forever. Fixes bug 384.
28099 - Count it as a failure if we fetch a valid network-status but we
28100 don't want to keep it. Otherwise we'll keep fetching it and keep
28101 not wanting to keep it. Fixes part of bug 422.
28102 - If all of our dirservers have given us bad or no networkstatuses
28103 lately, then stop hammering them once per minute even when we
28104 think they're failed. Fixes another part of bug 422.
28107 - Actually set the purpose correctly for descriptors inserted with
28108 purpose=controller.
28109 - When we have k non-v2 authorities in our DirServer config,
28110 we ignored the last k authorities in the list when updating our
28112 - Correctly back-off from requesting router descriptors that we are
28113 having a hard time downloading.
28114 - Read resolv.conf files correctly on platforms where read() returns
28115 partial results on small file reads.
28116 - Don't rebuild the entire router store every time we get 32K of
28117 routers: rebuild it when the journal gets very large, or when
28118 the gaps in the store get very large.
28121 - When routers publish SVN revisions in their router descriptors,
28122 authorities now include those versions correctly in networkstatus
28124 - Warn when using a version of libevent before 1.3b to run a server on
28125 OSX or BSD: these versions interact badly with userspace threads.
28128 Changes in version 0.1.2.13 - 2007-04-24
28129 This release features some major anonymity fixes, such as safer path
28130 selection; better client performance; faster bootstrapping, better
28131 address detection, and better DNS support for servers; write limiting as
28132 well as read limiting to make servers easier to run; and a huge pile of
28133 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
28135 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
28136 of the Freenode IRC network, remembering his patience and vision for
28137 free speech on the Internet.
28140 - Fix a memory leak when we ask for "all" networkstatuses and we
28141 get one we don't recognize.
28142 - Add more asserts to hunt down bug 417.
28143 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
28146 Changes in version 0.1.2.12-rc - 2007-03-16
28148 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
28149 directory information requested inside Tor connections (i.e. via
28150 begin_dir cells). It only triggered when the same connection was
28151 serving other data at the same time. Reported by seeess.
28154 - When creating a circuit via the controller, send a 'launched'
28155 event when we're done, so we follow the spec better.
28158 Changes in version 0.1.2.11-rc - 2007-03-15
28159 o Minor bugfixes (controller), reported by daejees:
28160 - Correct the control spec to match how the code actually responds
28161 to 'getinfo addr-mappings/*'.
28162 - The control spec described a GUARDS event, but the code
28163 implemented a GUARD event. Standardize on GUARD, but let people
28164 ask for GUARDS too.
28167 Changes in version 0.1.2.10-rc - 2007-03-07
28168 o Major bugfixes (Windows):
28169 - Do not load the NT services library functions (which may not exist)
28170 just to detect if we're a service trying to shut down. Now we run
28171 on Win98 and friends again.
28173 o Minor bugfixes (other):
28174 - Clarify a couple of log messages.
28175 - Fix a misleading socks5 error number.
28178 Changes in version 0.1.2.9-rc - 2007-03-02
28179 o Major bugfixes (Windows):
28180 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
28181 of the usual GCC "%llu". This prevents a bug when saving 64-bit
28182 int configuration values: the high-order 32 bits would get
28183 truncated. In particular, we were being bitten by the default
28184 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
28185 and maybe also bug 397.)
28187 o Minor bugfixes (performance):
28188 - Use OpenSSL's AES implementation on platforms where it's faster.
28189 This could save us as much as 10% CPU usage.
28191 o Minor bugfixes (server):
28192 - Do not rotate onion key immediately after setting it for the first
28195 o Minor bugfixes (directory authorities):
28196 - Stop calling servers that have been hibernating for a long time
28197 "stable". Also, stop letting hibernating or obsolete servers affect
28198 uptime and bandwidth cutoffs.
28199 - Stop listing hibernating servers in the v1 directory.
28201 o Minor bugfixes (hidden services):
28202 - Upload hidden service descriptors slightly less often, to reduce
28203 load on authorities.
28205 o Minor bugfixes (other):
28206 - Fix an assert that could trigger if a controller quickly set then
28207 cleared EntryNodes. Bug found by Udo van den Heuvel.
28208 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
28210 - Fix a potential race condition in the rpm installer. Found by
28212 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
28213 of 2 as indicating that the server is completely bad; it sometimes
28214 means that the server is just bad for the request in question. (may fix
28215 the last of bug 326.)
28216 - Disable encrypted directory connections when we don't have a server
28217 descriptor for the destination. We'll get this working again in
28221 Changes in version 0.1.2.8-beta - 2007-02-26
28222 o Major bugfixes (crashes):
28223 - Stop crashing when the controller asks us to resetconf more than
28224 one config option at once. (Vidalia 0.0.11 does this.)
28225 - Fix a crash that happened on Win98 when we're given command-line
28226 arguments: don't try to load NT service functions from advapi32.dll
28227 except when we need them. (Bug introduced in 0.1.2.7-alpha;
28229 - Fix a longstanding obscure crash bug that could occur when
28230 we run out of DNS worker processes. (Resolves bug 390.)
28232 o Major bugfixes (hidden services):
28233 - Correctly detect whether hidden service descriptor downloads are
28234 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
28236 o Major bugfixes (accounting):
28237 - When we start during an accounting interval before it's time to wake
28238 up, remember to wake up at the correct time. (May fix bug 342.)
28240 o Minor bugfixes (controller):
28241 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
28242 clear the corresponding on_circuit variable, and remember later
28243 that we don't need to send a redundant CLOSED event. Resolves part
28245 - Report events where a resolve succeeded or where we got a socks
28246 protocol error correctly, rather than calling both of them
28248 - Change reported stream target addresses to IP consistently when
28249 we finally get the IP from an exit node.
28250 - Send log messages to the controller even if they happen to be very
28253 o Minor bugfixes (other):
28254 - Display correct results when reporting which versions are
28255 recommended, and how recommended they are. (Resolves bug 383.)
28256 - Improve our estimates for directory bandwidth to be less random:
28257 guess that an unrecognized directory will have the average bandwidth
28258 from all known directories, not that it will have the average
28259 bandwidth from those directories earlier than it on the list.
28260 - If we start a server with ClientOnly 1, then set ClientOnly to 0
28261 and hup, stop triggering an assert based on an empty onion_key.
28262 - On platforms with no working mmap() equivalent, don't warn the
28263 user when cached-routers doesn't exist.
28264 - Warn the user when mmap() [or its equivalent] fails for some reason
28265 other than file-not-found.
28266 - Don't warn the user when cached-routers.new doesn't exist: that's
28267 perfectly fine when starting up for the first time.
28268 - When EntryNodes are configured, rebuild the guard list to contain,
28269 in order: the EntryNodes that were guards before; the rest of the
28270 EntryNodes; the nodes that were guards before.
28271 - Mask out all signals in sub-threads; only the libevent signal
28272 handler should be processing them. This should prevent some crashes
28273 on some machines using pthreads. (Patch from coderman.)
28274 - Fix switched arguments on memset in the implementation of
28275 tor_munmap() for systems with no mmap() call.
28276 - When Tor receives a router descriptor that it asked for, but
28277 no longer wants (because it has received fresh networkstatuses
28278 in the meantime), do not warn the user. Cache the descriptor if
28279 we're a cache; drop it if we aren't.
28280 - Make earlier entry guards _really_ get retried when the network
28282 - On a malformed DNS reply, always give an error to the corresponding
28284 - Build with recent libevents on platforms that do not define the
28285 nonstandard types "u_int8_t" and friends.
28287 o Minor features (controller):
28288 - Warn the user when an application uses the obsolete binary v0
28289 control protocol. We're planning to remove support for it during
28290 the next development series, so it's good to give people some
28292 - Add STREAM_BW events to report per-entry-stream bandwidth
28293 use. (Patch from Robert Hogan.)
28294 - Rate-limit SIGNEWNYM signals in response to controllers that
28295 impolitely generate them for every single stream. (Patch from
28296 mwenge; closes bug 394.)
28297 - Make REMAP stream events have a SOURCE (cache or exit), and
28298 make them generated in every case where we get a successful
28299 connected or resolved cell.
28301 o Minor bugfixes (performance):
28302 - Call router_have_min_dir_info half as often. (This is showing up in
28303 some profiles, but not others.)
28304 - When using GCC, make log_debug never get called at all, and its
28305 arguments never get evaluated, when no debug logs are configured.
28306 (This is showing up in some profiles, but not others.)
28309 - Remove some never-implemented options. Mark PathlenCoinWeight as
28311 - Implement proposal 106: Stop requiring clients to have well-formed
28312 certificates; stop checking nicknames in certificates. (Clients
28313 have certificates so that they can look like Tor servers, but in
28314 the future we might want to allow them to look like regular TLS
28315 clients instead. Nicknames in certificates serve no purpose other
28316 than making our protocol easier to recognize on the wire.)
28317 - Revise messages on handshake failure again to be even more clear about
28318 which are incoming connections and which are outgoing.
28319 - Discard any v1 directory info that's over 1 month old (for
28320 directories) or over 1 week old (for running-routers lists).
28321 - Do not warn when individual nodes in the configuration's EntryNodes,
28322 ExitNodes, etc are down: warn only when all possible nodes
28323 are down. (Fixes bug 348.)
28324 - Always remove expired routers and networkstatus docs before checking
28325 whether we have enough information to build circuits. (Fixes
28327 - Put a lower-bound on MaxAdvertisedBandwidth.
28330 Changes in version 0.1.2.7-alpha - 2007-02-06
28331 o Major bugfixes (rate limiting):
28332 - Servers decline directory requests much more aggressively when
28333 they're low on bandwidth. Otherwise they end up queueing more and
28334 more directory responses, which can't be good for latency.
28335 - But never refuse directory requests from local addresses.
28336 - Fix a memory leak when sending a 503 response for a networkstatus
28338 - Be willing to read or write on local connections (e.g. controller
28339 connections) even when the global rate limiting buckets are empty.
28340 - If our system clock jumps back in time, don't publish a negative
28341 uptime in the descriptor. Also, don't let the global rate limiting
28342 buckets go absurdly negative.
28343 - Flush local controller connection buffers periodically as we're
28344 writing to them, so we avoid queueing 4+ megabytes of data before
28347 o Major bugfixes (NT services):
28348 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
28349 command-line flag so that admins can override the default by saying
28350 "tor --service install --user "SomeUser"". This will not affect
28351 existing installed services. Also, warn the user that the service
28352 will look for its configuration file in the service user's
28353 %appdata% directory. (We can't do the 'hardwire the user's appdata
28354 directory' trick any more, since we may not have read access to that
28357 o Major bugfixes (other):
28358 - Previously, we would cache up to 16 old networkstatus documents
28359 indefinitely, if they came from nontrusted authorities. Now we
28360 discard them if they are more than 10 days old.
28361 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
28363 - Detect and reject malformed DNS responses containing circular
28365 - If exits are rare enough that we're not marking exits as guards,
28366 ignore exit bandwidth when we're deciding the required bandwidth
28368 - When we're handling a directory connection tunneled over Tor,
28369 don't fill up internal memory buffers with all the data we want
28370 to tunnel; instead, only add it if the OR connection that will
28371 eventually receive it has some room for it. (This can lead to
28372 slowdowns in tunneled dir connections; a better solution will have
28373 to wait for 0.2.0.)
28375 o Minor bugfixes (dns):
28376 - Add some defensive programming to eventdns.c in an attempt to catch
28377 possible memory-stomping bugs.
28378 - Detect and reject DNS replies containing IPv4 or IPv6 records with
28379 an incorrect number of bytes. (Previously, we would ignore the
28381 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
28382 in the correct order, and doesn't crash.
28383 - Free memory held in recently-completed DNS lookup attempts on exit.
28384 This was not a memory leak, but may have been hiding memory leaks.
28385 - Handle TTL values correctly on reverse DNS lookups.
28386 - Treat failure to parse resolv.conf as an error.
28388 o Minor bugfixes (other):
28389 - Fix crash with "tor --list-fingerprint" (reported by seeess).
28390 - When computing clock skew from directory HTTP headers, consider what
28391 time it was when we finished asking for the directory, not what
28393 - Expire socks connections if they spend too long waiting for the
28394 handshake to finish. Previously we would let them sit around for
28395 days, if the connecting application didn't close them either.
28396 - And if the socks handshake hasn't started, don't send a
28397 "DNS resolve socks failed" handshake reply; just close it.
28398 - Stop using C functions that OpenBSD's linker doesn't like.
28399 - Don't launch requests for descriptors unless we have networkstatuses
28400 from at least half of the authorities. This delays the first
28401 download slightly under pathological circumstances, but can prevent
28402 us from downloading a bunch of descriptors we don't need.
28403 - Do not log IPs with TLS failures for incoming TLS
28404 connections. (Fixes bug 382.)
28405 - If the user asks to use invalid exit nodes, be willing to use
28407 - Stop using the reserved ac_cv namespace in our configure script.
28408 - Call stat() slightly less often; use fstat() when possible.
28409 - Refactor the way we handle pending circuits when an OR connection
28410 completes or fails, in an attempt to fix a rare crash bug.
28411 - Only rewrite a conn's address based on X-Forwarded-For: headers
28412 if it's a parseable public IP address; and stop adding extra quotes
28413 to the resulting address.
28416 - Weight directory requests by advertised bandwidth. Now we can
28417 let servers enable write limiting but still allow most clients to
28418 succeed at their directory requests. (We still ignore weights when
28419 choosing a directory authority; I hope this is a feature.)
28422 - Create a new file ReleaseNotes which was the old ChangeLog. The
28423 new ChangeLog file now includes the summaries for all development
28425 - Check for addresses with invalid characters at the exit as well
28426 as at the client, and warn less verbosely when they fail. You can
28427 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28428 - Adapt a patch from goodell to let the contrib/exitlist script
28429 take arguments rather than require direct editing.
28430 - Inform the server operator when we decide not to advertise a
28431 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28432 was confusing Zax, so now we're hopefully more helpful.
28433 - Bring us one step closer to being able to establish an encrypted
28434 directory tunnel without knowing a descriptor first. Still not
28435 ready yet. As part of the change, now assume we can use a
28436 create_fast cell if we don't know anything about a router.
28437 - Allow exit nodes to use nameservers running on ports other than 53.
28438 - Servers now cache reverse DNS replies.
28439 - Add an --ignore-missing-torrc command-line option so that we can
28440 get the "use sensible defaults if the configuration file doesn't
28441 exist" behavior even when specifying a torrc location on the command
28444 o Minor features (controller):
28445 - Track reasons for OR connection failure; make these reasons
28446 available via the controller interface. (Patch from Mike Perry.)
28447 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28448 can learn when clients are sending malformed hostnames to Tor.
28449 - Clean up documentation for controller status events.
28450 - Add a REMAP status to stream events to note that a stream's
28451 address has changed because of a cached address or a MapAddress
28455 Changes in version 0.1.2.6-alpha - 2007-01-09
28457 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28458 connection handles more than 4 gigs in either direction, we crash.
28459 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28460 advertised exit node, somebody might try to exit from us when
28461 we're bootstrapping and before we've built our descriptor yet.
28462 Refuse the connection rather than crashing.
28465 - Warn if we (as a server) find that we've resolved an address that we
28466 weren't planning to resolve.
28467 - Warn that using select() on any libevent version before 1.1 will be
28468 unnecessarily slow (even for select()).
28469 - Flush ERR-level controller status events just like we currently
28470 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28471 the controller from learning about current events.
28473 o Minor features (more controller status events):
28474 - Implement EXTERNAL_ADDRESS server status event so controllers can
28475 learn when our address changes.
28476 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28477 can learn when directories reject our descriptor.
28478 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28479 can learn when a client application is speaking a non-socks protocol
28481 - Implement DANGEROUS_SOCKS client status event so controllers
28482 can learn when a client application is leaking DNS addresses.
28483 - Implement BUG general status event so controllers can learn when
28484 Tor is unhappy about its internal invariants.
28485 - Implement CLOCK_SKEW general status event so controllers can learn
28486 when Tor thinks the system clock is set incorrectly.
28487 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28488 server status events so controllers can learn when their descriptors
28489 are accepted by a directory.
28490 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28491 server status events so controllers can learn about Tor's progress in
28492 deciding whether it's reachable from the outside.
28493 - Implement BAD_LIBEVENT general status event so controllers can learn
28494 when we have a version/method combination in libevent that needs to
28496 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28497 and DNS_USELESS server status events so controllers can learn
28498 about changes to DNS server status.
28500 o Minor features (directory):
28501 - Authorities no longer recommend exits as guards if this would shift
28502 too much load to the exit nodes.
28505 Changes in version 0.1.2.5-alpha - 2007-01-06
28507 - Enable write limiting as well as read limiting. Now we sacrifice
28508 capacity if we're pushing out lots of directory traffic, rather
28509 than overrunning the user's intended bandwidth limits.
28510 - Include TLS overhead when counting bandwidth usage; previously, we
28511 would count only the bytes sent over TLS, but not the bytes used
28513 - Support running the Tor service with a torrc not in the same
28514 directory as tor.exe and default to using the torrc located in
28515 the %appdata%\Tor\ of the user who installed the service. Patch
28517 - Servers now check for the case when common DNS requests are going to
28518 wildcarded addresses (i.e. all getting the same answer), and change
28519 their exit policy to reject *:* if it's happening.
28520 - Implement BEGIN_DIR cells, so we can connect to the directory
28521 server via TLS to do encrypted directory requests rather than
28522 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28523 config options if you like.
28525 o Minor features (config and docs):
28526 - Start using the state file to store bandwidth accounting data:
28527 the bw_accounting file is now obsolete. We'll keep generating it
28528 for a while for people who are still using 0.1.2.4-alpha.
28529 - Try to batch changes to the state file so that we do as few
28530 disk writes as possible while still storing important things in
28532 - The state file and the bw_accounting file get saved less often when
28533 the AvoidDiskWrites config option is set.
28534 - Make PIDFile work on Windows (untested).
28535 - Add internal descriptions for a bunch of configuration options:
28536 accessible via controller interface and in comments in saved
28538 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28539 NNTP by default, so this seems like a sensible addition.
28540 - Clients now reject hostnames with invalid characters. This should
28541 avoid some inadvertent info leaks. Add an option
28542 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28543 is running a private network with hosts called @, !, and #.
28544 - Add a maintainer script to tell us which options are missing
28545 documentation: "make check-docs".
28546 - Add a new address-spec.txt document to describe our special-case
28547 addresses: .exit, .onion, and .noconnnect.
28549 o Minor features (DNS):
28550 - Ongoing work on eventdns infrastructure: now it has dns server
28551 and ipv6 support. One day Tor will make use of it.
28552 - Add client-side caching for reverse DNS lookups.
28553 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28554 - When we change nameservers or IP addresses, reset and re-launch
28555 our tests for DNS hijacking.
28557 o Minor features (directory):
28558 - Authorities now specify server versions in networkstatus. This adds
28559 about 2% to the size of compressed networkstatus docs, and allows
28560 clients to tell which servers support BEGIN_DIR and which don't.
28561 The implementation is forward-compatible with a proposed future
28562 protocol version scheme not tied to Tor versions.
28563 - DirServer configuration lines now have an orport= option so
28564 clients can open encrypted tunnels to the authorities without
28565 having downloaded their descriptors yet. Enabled for moria1,
28566 moria2, tor26, and lefkada now in the default configuration.
28567 - Directory servers are more willing to send a 503 "busy" if they
28568 are near their write limit, especially for v1 directory requests.
28569 Now they can use their limited bandwidth for actual Tor traffic.
28570 - Clients track responses with status 503 from dirservers. After a
28571 dirserver has given us a 503, we try not to use it until an hour has
28572 gone by, or until we have no dirservers that haven't given us a 503.
28573 - When we get a 503 from a directory, and we're not a server, we don't
28574 count the failure against the total number of failures allowed
28575 for the thing we're trying to download.
28576 - Report X-Your-Address-Is correctly from tunneled directory
28577 connections; don't report X-Your-Address-Is when it's an internal
28578 address; and never believe reported remote addresses when they're
28580 - Protect against an unlikely DoS attack on directory servers.
28581 - Add a BadDirectory flag to network status docs so that authorities
28582 can (eventually) tell clients about caches they believe to be
28585 o Minor features (controller):
28586 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28587 - Reimplement GETINFO so that info/names stays in sync with the
28589 - Implement "GETINFO fingerprint".
28590 - Implement "SETEVENTS GUARD" so controllers can get updates on
28591 entry guard status as it changes.
28593 o Minor features (clean up obsolete pieces):
28594 - Remove some options that have been deprecated since at least
28595 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28596 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28597 to set log options.
28598 - We no longer look for identity and onion keys in "identity.key" and
28599 "onion.key" -- these were replaced by secret_id_key and
28600 secret_onion_key in 0.0.8pre1.
28601 - We no longer require unrecognized directory entries to be
28604 o Major bugfixes (security):
28605 - Stop sending the HttpProxyAuthenticator string to directory
28606 servers when directory connections are tunnelled through Tor.
28607 - Clients no longer store bandwidth history in the state file.
28608 - Do not log introduction points for hidden services if SafeLogging
28610 - When generating bandwidth history, round down to the nearest
28611 1k. When storing accounting data, round up to the nearest 1k.
28612 - When we're running as a server, remember when we last rotated onion
28613 keys, so that we will rotate keys once they're a week old even if
28614 we never stay up for a week ourselves.
28616 o Major bugfixes (other):
28617 - Fix a longstanding bug in eventdns that prevented the count of
28618 timed-out resolves from ever being reset. This bug caused us to
28619 give up on a nameserver the third time it timed out, and try it
28620 10 seconds later... and to give up on it every time it timed out
28622 - Take out the '5 second' timeout from the connection retry
28623 schedule. Now the first connect attempt will wait a full 10
28624 seconds before switching to a new circuit. Perhaps this will help
28625 a lot. Based on observations from Mike Perry.
28626 - Fix a bug on the Windows implementation of tor_mmap_file() that
28627 would prevent the cached-routers file from ever loading. Reported
28631 - Fix an assert failure when a directory authority sets
28632 AuthDirRejectUnlisted and then receives a descriptor from an
28633 unlisted router. Reported by seeess.
28634 - Avoid a double-free when parsing malformed DirServer lines.
28635 - Fix a bug when a BSD-style PF socket is first used. Patch from
28637 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
28638 to resolve an address at a given exit node even when they ask for
28640 - Servers no longer ever list themselves in their "family" line,
28641 even if configured to do so. This makes it easier to configure
28642 family lists conveniently.
28643 - When running as a server, don't fall back to 127.0.0.1 when no
28644 nameservers are configured in /etc/resolv.conf; instead, make the
28645 user fix resolv.conf or specify nameservers explicitly. (Resolves
28647 - Stop accepting certain malformed ports in configured exit policies.
28648 - Don't re-write the fingerprint file every restart, unless it has
28650 - Stop warning when a single nameserver fails: only warn when _all_ of
28651 our nameservers have failed. Also, when we only have one nameserver,
28652 raise the threshold for deciding that the nameserver is dead.
28653 - Directory authorities now only decide that routers are reachable
28654 if their identity keys are as expected.
28655 - When the user uses bad syntax in the Log config line, stop
28656 suggesting other bad syntax as a replacement.
28657 - Correctly detect ipv6 DNS capability on OpenBSD.
28659 o Minor bugfixes (controller):
28660 - Report the circuit number correctly in STREAM CLOSED events. Bug
28661 reported by Mike Perry.
28662 - Do not report bizarre values for results of accounting GETINFOs
28663 when the last second's write or read exceeds the allotted bandwidth.
28664 - Report "unrecognized key" rather than an empty string when the
28665 controller tries to fetch a networkstatus that doesn't exist.
28668 Changes in version 0.1.1.26 - 2006-12-14
28669 o Security bugfixes:
28670 - Stop sending the HttpProxyAuthenticator string to directory
28671 servers when directory connections are tunnelled through Tor.
28672 - Clients no longer store bandwidth history in the state file.
28673 - Do not log introduction points for hidden services if SafeLogging
28677 - Fix an assert failure when a directory authority sets
28678 AuthDirRejectUnlisted and then receives a descriptor from an
28679 unlisted router (reported by seeess).
28682 Changes in version 0.1.2.4-alpha - 2006-12-03
28684 - Add support for using natd; this allows FreeBSDs earlier than
28685 5.1.2 to have ipfw send connections through Tor without using
28686 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
28689 - Make all connections to addresses of the form ".noconnect"
28690 immediately get closed. This lets application/controller combos
28691 successfully test whether they're talking to the same Tor by
28692 watching for STREAM events.
28693 - Make cross.sh cross-compilation script work even when autogen.sh
28694 hasn't been run. (Patch from Michael Mohr.)
28695 - Statistics dumped by -USR2 now include a breakdown of public key
28696 operations, for profiling.
28699 - Fix a major leak when directory authorities parse their
28700 approved-routers list, a minor memory leak when we fail to pick
28701 an exit node, and a few rare leaks on errors.
28702 - Handle TransPort connections even when the server sends data before
28703 the client sends data. Previously, the connection would just hang
28704 until the client sent data. (Patch from tup based on patch from
28706 - Avoid assert failure when our cached-routers file is empty on
28710 - Don't log spurious warnings when we see a circuit close reason we
28711 don't recognize; it's probably just from a newer version of Tor.
28712 - Have directory authorities allow larger amounts of drift in uptime
28713 without replacing the server descriptor: previously, a server that
28714 restarted every 30 minutes could have 48 "interesting" descriptors
28716 - Start linking to the Tor specification and Tor reference manual
28717 correctly in the Windows installer.
28718 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28719 Tor/Privoxy we also uninstall Vidalia.
28720 - Resume building on Irix64, and fix a lot of warnings from its
28721 MIPSpro C compiler.
28722 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
28723 when we're running as a client.
28726 Changes in version 0.1.1.25 - 2006-11-04
28728 - When a client asks us to resolve (rather than connect to)
28729 an address, and we have a cached answer, give them the cached
28730 answer. Previously, we would give them no answer at all.
28731 - We were building exactly the wrong circuits when we predict
28732 hidden service requirements, meaning Tor would have to build all
28733 its circuits on demand.
28734 - If none of our live entry guards have a high uptime, but we
28735 require a guard with a high uptime, try adding a new guard before
28736 we give up on the requirement. This patch should make long-lived
28737 connections more stable on average.
28738 - When testing reachability of our DirPort, don't launch new
28739 tests when there's already one in progress -- unreachable
28740 servers were stacking up dozens of testing streams.
28742 o Security bugfixes:
28743 - When the user sends a NEWNYM signal, clear the client-side DNS
28744 cache too. Otherwise we continue to act on previous information.
28747 - Avoid a memory corruption bug when creating a hash table for
28749 - Avoid possibility of controller-triggered crash when misusing
28750 certain commands from a v0 controller on platforms that do not
28751 handle printf("%s",NULL) gracefully.
28752 - Avoid infinite loop on unexpected controller input.
28753 - Don't log spurious warnings when we see a circuit close reason we
28754 don't recognize; it's probably just from a newer version of Tor.
28755 - Add Vidalia to the OS X uninstaller script, so when we uninstall
28756 Tor/Privoxy we also uninstall Vidalia.
28759 Changes in version 0.1.2.3-alpha - 2006-10-29
28761 - Prepare for servers to publish descriptors less often: never
28762 discard a descriptor simply for being too old until either it is
28763 recommended by no authorities, or until we get a better one for
28764 the same router. Make caches consider retaining old recommended
28765 routers for even longer.
28766 - If most authorities set a BadExit flag for a server, clients
28767 don't think of it as a general-purpose exit. Clients only consider
28768 authorities that advertise themselves as listing bad exits.
28769 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
28770 headers for content, so that we can work better in the presence of
28771 caching HTTP proxies.
28772 - Allow authorities to list nodes as bad exits by fingerprint or by
28775 o Minor features, controller:
28776 - Add a REASON field to CIRC events; for backward compatibility, this
28777 field is sent only to controllers that have enabled the extended
28778 event format. Also, add additional reason codes to explain why
28779 a given circuit has been destroyed or truncated. (Patches from
28781 - Add a REMOTE_REASON field to extended CIRC events to tell the
28782 controller about why a remote OR told us to close a circuit.
28783 - Stream events also now have REASON and REMOTE_REASON fields,
28784 working much like those for circuit events.
28785 - There's now a GETINFO ns/... field so that controllers can ask Tor
28786 about the current status of a router.
28787 - A new event type "NS" to inform a controller when our opinion of
28788 a router's status has changed.
28789 - Add a GETINFO events/names and GETINFO features/names so controllers
28790 can tell which events and features are supported.
28791 - A new CLEARDNSCACHE signal to allow controllers to clear the
28792 client-side DNS cache without expiring circuits.
28794 o Security bugfixes:
28795 - When the user sends a NEWNYM signal, clear the client-side DNS
28796 cache too. Otherwise we continue to act on previous information.
28799 - Avoid sending junk to controllers or segfaulting when a controller
28800 uses EVENT_NEW_DESC with verbose nicknames.
28801 - Stop triggering asserts if the controller tries to extend hidden
28802 service circuits (reported by mwenge).
28803 - Avoid infinite loop on unexpected controller input.
28804 - When the controller does a "GETINFO network-status", tell it
28805 about even those routers whose descriptors are very old, and use
28806 long nicknames where appropriate.
28807 - Change NT service functions to be loaded on demand. This lets us
28808 build with MinGW without breaking Tor for Windows 98 users.
28809 - Do DirPort reachability tests less often, since a single test
28810 chews through many circuits before giving up.
28811 - In the hidden service example in torrc.sample, stop recommending
28812 esoteric and discouraged hidden service options.
28813 - When stopping an NT service, wait up to 10 sec for it to actually
28814 stop. Patch from Matt Edman; resolves bug 295.
28815 - Fix handling of verbose nicknames with ORCONN controller events:
28816 make them show up exactly when requested, rather than exactly when
28818 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
28819 printing a duplicate "$" in the keys we send (reported by mwenge).
28820 - Correctly set maximum connection limit on Cygwin. (This time
28822 - Try to detect Windows correctly when cross-compiling.
28823 - Detect the size of the routers file correctly even if it is
28824 corrupted (on systems without mmap) or not page-aligned (on systems
28825 with mmap). This bug was harmless.
28826 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
28827 to open a stream fails; now we do in more cases. This should
28828 make clients able to find a good exit faster in some cases, since
28829 unhandleable requests will now get an error rather than timing out.
28830 - Resolve two memory leaks when rebuilding the on-disk router cache
28831 (reported by fookoowa).
28832 - Clean up minor code warnings suggested by the MIPSpro C compiler,
28833 and reported by some Centos users.
28834 - Controller signals now work on non-Unix platforms that don't define
28835 SIGUSR1 and SIGUSR2 the way we expect.
28836 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
28837 values before failing, and always enables eventdns.
28838 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
28839 Try to fix this in configure.in by checking for most functions
28840 before we check for libevent.
28843 Changes in version 0.1.2.2-alpha - 2006-10-07
28845 - Make our async eventdns library on-by-default for Tor servers,
28846 and plan to deprecate the separate dnsworker threads.
28847 - Add server-side support for "reverse" DNS lookups (using PTR
28848 records so clients can determine the canonical hostname for a given
28849 IPv4 address). Only supported by servers using eventdns; servers
28850 now announce in their descriptors whether they support eventdns.
28851 - Specify and implement client-side SOCKS5 interface for reverse DNS
28852 lookups (see doc/socks-extensions.txt).
28853 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
28854 connect to directory servers through Tor. Previously, clients needed
28855 to find Tor exits to make private connections to directory servers.
28856 - Avoid choosing Exit nodes for entry or middle hops when the
28857 total bandwidth available from non-Exit nodes is much higher than
28858 the total bandwidth available from Exit nodes.
28859 - Workaround for name servers (like Earthlink's) that hijack failing
28860 DNS requests and replace the no-such-server answer with a "helpful"
28861 redirect to an advertising-driven search portal. Also work around
28862 DNS hijackers who "helpfully" decline to hijack known-invalid
28863 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
28864 lets you turn it off.
28865 - Send out a burst of long-range padding cells once we've established
28866 that we're reachable. Spread them over 4 circuits, so hopefully
28867 a few will be fast. This exercises our bandwidth and bootstraps
28868 us into the directory more quickly.
28870 o New/improved config options:
28871 - Add new config option "ResolvConf" to let the server operator
28872 choose an alternate resolve.conf file when using eventdns.
28873 - Add an "EnforceDistinctSubnets" option to control our "exclude
28874 servers on the same /16" behavior. It's still on by default; this
28875 is mostly for people who want to operate private test networks with
28876 all the machines on the same subnet.
28877 - If one of our entry guards is on the ExcludeNodes list, or the
28878 directory authorities don't think it's a good guard, treat it as
28879 if it were unlisted: stop using it as a guard, and throw it off
28880 the guards list if it stays that way for a long time.
28881 - Allow directory authorities to be marked separately as authorities
28882 for the v1 directory protocol, the v2 directory protocol, and
28883 as hidden service directories, to make it easier to retire old
28884 authorities. V1 authorities should set "HSAuthoritativeDir 1"
28885 to continue being hidden service authorities too.
28886 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
28888 o Minor features, controller:
28889 - Fix CIRC controller events so that controllers can learn the
28890 identity digests of non-Named servers used in circuit paths.
28891 - Let controllers ask for more useful identifiers for servers. Instead
28892 of learning identity digests for un-Named servers and nicknames
28893 for Named servers, the new identifiers include digest, nickname,
28894 and indication of Named status. Off by default; see control-spec.txt
28895 for more information.
28896 - Add a "getinfo address" controller command so it can display Tor's
28897 best guess to the user.
28898 - New controller event to alert the controller when our server
28899 descriptor has changed.
28900 - Give more meaningful errors on controller authentication failure.
28902 o Minor features, other:
28903 - When asked to resolve a hostname, don't use non-exit servers unless
28904 requested to do so. This allows servers with broken DNS to be
28905 useful to the network.
28906 - Divide eventdns log messages into warn and info messages.
28907 - Reserve the nickname "Unnamed" for routers that can't pick
28908 a hostname: any router can call itself Unnamed; directory
28909 authorities will never allocate Unnamed to any particular router;
28910 clients won't believe that any router is the canonical Unnamed.
28911 - Only include function names in log messages for info/debug messages.
28912 For notice/warn/err, the content of the message should be clear on
28913 its own, and printing the function name only confuses users.
28914 - Avoid some false positives during reachability testing: don't try
28915 to test via a server that's on the same /24 as us.
28916 - If we fail to build a circuit to an intended enclave, and it's
28917 not mandatory that we use that enclave, stop wanting it.
28918 - When eventdns is enabled, allow multithreaded builds on NetBSD and
28919 OpenBSD. (We had previously disabled threads on these platforms
28920 because they didn't have working thread-safe resolver functions.)
28922 o Major bugfixes, anonymity/security:
28923 - If a client asked for a server by name, and there's a named server
28924 in our network-status but we don't have its descriptor yet, we
28925 could return an unnamed server instead.
28926 - Fix NetBSD bug that could allow someone to force uninitialized RAM
28927 to be sent to a server's DNS resolver. This only affects NetBSD
28928 and other platforms that do not bounds-check tolower().
28929 - Reject (most) attempts to use Tor circuits with length one. (If
28930 many people start using Tor as a one-hop proxy, exit nodes become
28931 a more attractive target for compromise.)
28932 - Just because your DirPort is open doesn't mean people should be
28933 able to remotely teach you about hidden service descriptors. Now
28934 only accept rendezvous posts if you've got HSAuthoritativeDir set.
28936 o Major bugfixes, other:
28937 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
28938 - When a client asks the server to resolve (not connect to)
28939 an address, and it has a cached answer, give them the cached answer.
28940 Previously, the server would give them no answer at all.
28941 - Allow really slow clients to not hang up five minutes into their
28942 directory downloads (suggested by Adam J. Richter).
28943 - We were building exactly the wrong circuits when we anticipated
28944 hidden service requirements, meaning Tor would have to build all
28945 its circuits on demand.
28946 - Avoid crashing when we mmap a router cache file of size 0.
28947 - When testing reachability of our DirPort, don't launch new
28948 tests when there's already one in progress -- unreachable
28949 servers were stacking up dozens of testing streams.
28951 o Minor bugfixes, correctness:
28952 - If we're a directory mirror and we ask for "all" network status
28953 documents, we would discard status documents from authorities
28954 we don't recognize.
28955 - Avoid a memory corruption bug when creating a hash table for
28957 - Avoid controller-triggered crash when misusing certain commands
28958 from a v0 controller on platforms that do not handle
28959 printf("%s",NULL) gracefully.
28960 - Don't crash when a controller sends a third argument to an
28961 "extendcircuit" request.
28962 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
28963 response; fix error code when "getinfo dir/status/" fails.
28964 - Avoid crash when telling controller stream-status and a stream
28966 - Patch from Adam Langley to fix assert() in eventdns.c.
28967 - Fix a debug log message in eventdns to say "X resolved to Y"
28968 instead of "X resolved to X".
28969 - Make eventdns give strings for DNS errors, not just error numbers.
28970 - Track unreachable entry guards correctly: don't conflate
28971 'unreachable by us right now' with 'listed as down by the directory
28972 authorities'. With the old code, if a guard was unreachable by
28973 us but listed as running, it would clog our guard list forever.
28974 - Behave correctly in case we ever have a network with more than
28975 2GB/s total advertised capacity.
28976 - Make TrackExitHosts case-insensitive, and fix the behavior of
28977 ".suffix" TrackExitHosts items to avoid matching in the middle of
28979 - Finally fix the openssl warnings from newer gccs that believe that
28980 ignoring a return value is okay, but casting a return value and
28981 then ignoring it is a sign of madness.
28982 - Prevent the contrib/exitlist script from printing the same
28983 result more than once.
28984 - Patch from Steve Hildrey: Generate network status correctly on
28985 non-versioning dirservers.
28986 - Don't listen to the X-Your-Address-Is hint if you did the lookup
28987 via Tor; otherwise you'll think you're the exit node's IP address.
28989 o Minor bugfixes, performance:
28990 - Two small performance improvements on parsing descriptors.
28991 - Major performance improvement on inserting descriptors: change
28992 algorithm from O(n^2) to O(n).
28993 - Make the common memory allocation path faster on machines where
28994 malloc(0) returns a pointer.
28995 - Start remembering X-Your-Address-Is directory hints even if you're
28996 a client, so you can become a server more smoothly.
28997 - Avoid duplicate entries on MyFamily line in server descriptor.
28999 o Packaging, features:
29000 - Remove architecture from OS X builds. The official builds are
29001 now universal binaries.
29002 - The Debian package now uses --verify-config when (re)starting,
29003 to distinguish configuration errors from other errors.
29004 - Update RPMs to require libevent 1.1b.
29006 o Packaging, bugfixes:
29007 - Patches so Tor builds with MinGW on Windows.
29008 - Patches so Tor might run on Cygwin again.
29009 - Resume building on non-gcc compilers and ancient gcc. Resume
29010 building with the -O0 compile flag. Resume building cleanly on
29012 - Run correctly on OS X platforms with case-sensitive filesystems.
29013 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
29014 - Add autoconf checks so Tor can build on Solaris x86 again.
29017 - Documented (and renamed) ServerDNSSearchDomains and
29018 ServerDNSResolvConfFile options.
29019 - Be clearer that the *ListenAddress directives can be repeated
29023 Changes in version 0.1.1.24 - 2006-09-29
29025 - Allow really slow clients to not hang up five minutes into their
29026 directory downloads (suggested by Adam J. Richter).
29027 - Fix major performance regression from 0.1.0.x: instead of checking
29028 whether we have enough directory information every time we want to
29029 do something, only check when the directory information has changed.
29030 This should improve client CPU usage by 25-50%.
29031 - Don't crash if, after a server has been running for a while,
29032 it can't resolve its hostname.
29035 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29036 - Don't crash when the controller receives a third argument to an
29037 "extendcircuit" request.
29038 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29039 response; fix error code when "getinfo dir/status/" fails.
29040 - Fix configure.in to not produce broken configure files with
29041 more recent versions of autoconf. Thanks to Clint for his auto*
29043 - Fix security bug on NetBSD that could allow someone to force
29044 uninitialized RAM to be sent to a server's DNS resolver. This
29045 only affects NetBSD and other platforms that do not bounds-check
29047 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
29048 methods: these are known to be buggy.
29049 - If we're a directory mirror and we ask for "all" network status
29050 documents, we would discard status documents from authorities
29051 we don't recognize.
29054 Changes in version 0.1.2.1-alpha - 2006-08-27
29056 - Add "eventdns" async dns library from Adam Langley, tweaked to
29057 build on OSX and Windows. Only enabled if you pass the
29058 --enable-eventdns argument to configure.
29059 - Allow servers with no hostname or IP address to learn their
29060 IP address by asking the directory authorities. This code only
29061 kicks in when you would normally have exited with a "no address"
29062 error. Nothing's authenticated, so use with care.
29063 - Rather than waiting a fixed amount of time between retrying
29064 application connections, we wait only 5 seconds for the first,
29065 10 seconds for the second, and 15 seconds for each retry after
29066 that. Hopefully this will improve the expected user experience.
29067 - Patch from Tup to add support for transparent AP connections:
29068 this basically bundles the functionality of trans-proxy-tor
29069 into the Tor mainline. Now hosts with compliant pf/netfilter
29070 implementations can redirect TCP connections straight to Tor
29071 without diverting through SOCKS. Needs docs.
29072 - Busy directory servers save lots of memory by spooling server
29073 descriptors, v1 directories, and v2 networkstatus docs to buffers
29074 as needed rather than en masse. Also mmap the cached-routers
29075 files, so we don't need to keep the whole thing in memory too.
29076 - Automatically avoid picking more than one node from the same
29077 /16 network when constructing a circuit.
29078 - Revise and clean up the torrc.sample that we ship with; add
29079 a section for BandwidthRate and BandwidthBurst.
29082 - Split circuit_t into origin_circuit_t and or_circuit_t, and
29083 split connection_t into edge, or, dir, control, and base structs.
29084 These will save quite a bit of memory on busy servers, and they'll
29085 also help us track down bugs in the code and bugs in the spec.
29086 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
29087 or later. Log when we are doing this, so we can diagnose it when
29088 it fails. (Also, recommend libevent 1.1b for kqueue and
29089 win32 methods; deprecate libevent 1.0b harder; make libevent
29090 recommendation system saner.)
29091 - Start being able to build universal binaries on OS X (thanks
29093 - Export the default exit policy via the control port, so controllers
29094 don't need to guess what it is / will be later.
29095 - Add a man page entry for ProtocolWarnings.
29096 - Add TestVia config option to the man page.
29097 - Remove even more protocol-related warnings from Tor server logs,
29098 such as bad TLS handshakes and malformed begin cells.
29099 - Stop fetching descriptors if you're not a dir mirror and you
29100 haven't tried to establish any circuits lately. [This currently
29101 causes some dangerous behavior, because when you start up again
29102 you'll use your ancient server descriptors.]
29103 - New DirPort behavior: if you have your dirport set, you download
29104 descriptors aggressively like a directory mirror, whether or not
29105 your ORPort is set.
29106 - Get rid of the router_retry_connections notion. Now routers
29107 no longer try to rebuild long-term connections to directory
29108 authorities, and directory authorities no longer try to rebuild
29109 long-term connections to all servers. We still don't hang up
29110 connections in these two cases though -- we need to look at it
29111 more carefully to avoid flapping, and we likely need to wait til
29112 0.1.1.x is obsolete.
29113 - Drop compatibility with obsolete Tors that permit create cells
29114 to have the wrong circ_id_type.
29115 - Re-enable per-connection rate limiting. Get rid of the "OP
29116 bandwidth" concept. Lay groundwork for "bandwidth classes" --
29117 separate global buckets that apply depending on what sort of conn
29119 - Start publishing one minute or so after we find our ORPort
29120 to be reachable. This will help reduce the number of descriptors
29121 we have for ourselves floating around, since it's quite likely
29122 other things (e.g. DirPort) will change during that minute too.
29123 - Fork the v1 directory protocol into its own spec document,
29124 and mark dir-spec.txt as the currently correct (v2) spec.
29127 - When we find our DirPort to be reachable, publish a new descriptor
29128 so we'll tell the world (reported by pnx).
29129 - Publish a new descriptor after we hup/reload. This is important
29130 if our config has changed such that we'll want to start advertising
29131 our DirPort now, etc.
29132 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29133 - When we have a state file we cannot parse, tell the user and
29134 move it aside. Now we avoid situations where the user starts
29135 Tor in 1904, Tor writes a state file with that timestamp in it,
29136 the user fixes her clock, and Tor refuses to start.
29137 - Fix configure.in to not produce broken configure files with
29138 more recent versions of autoconf. Thanks to Clint for his auto*
29140 - "tor --verify-config" now exits with -1(255) or 0 depending on
29141 whether the config options are bad or good.
29142 - Resolve bug 321 when using dnsworkers: append a period to every
29143 address we resolve at the exit node, so that we do not accidentally
29144 pick up local addresses, and so that failing searches are retried
29145 in the resolver search domains. (This is already solved for
29146 eventdns.) (This breaks Blossom servers for now.)
29147 - If we are using an exit enclave and we can't connect, e.g. because
29148 its webserver is misconfigured to not listen on localhost, then
29149 back off and try connecting from somewhere else before we fail.
29152 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
29153 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
29154 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
29155 when the IP address is mapped through MapAddress to a hostname.
29156 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
29157 useless IPv6 DNS resolves.
29158 - Patch suggested by Karsten Loesing: respond to SIGNAL command
29159 before we execute the signal, in case the signal shuts us down.
29160 - Clean up AllowInvalidNodes man page entry.
29161 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
29162 - Add more asserts to track down an assert error on a windows Tor
29163 server with connection_add being called with socket == -1.
29164 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
29165 - Fix misleading log messages: an entry guard that is "unlisted",
29166 as well as not known to be "down" (because we've never heard
29167 of it), is not therefore "up".
29168 - Remove code to special-case "-cvs" ending, since it has not
29169 actually mattered since 0.0.9.
29170 - Make our socks5 handling more robust to broken socks clients:
29171 throw out everything waiting on the buffer in between socks
29172 handshake phases, since they can't possibly (so the theory
29173 goes) have predicted what we plan to respond to them.
29176 Changes in version 0.1.1.23 - 2006-07-30
29178 - Fast Tor servers, especially exit nodes, were triggering asserts
29179 due to a bug in handling the list of pending DNS resolves. Some
29180 bugs still remain here; we're hunting them.
29181 - Entry guards could crash clients by sending unexpected input.
29182 - More fixes on reachability testing: if you find yourself reachable,
29183 then don't ever make any client requests (so you stop predicting
29184 circuits), then hup or have your clock jump, then later your IP
29185 changes, you won't think circuits are working, so you won't try to
29186 test reachability, so you won't publish.
29189 - Avoid a crash if the controller does a resetconf firewallports
29190 and then a setconf fascistfirewall=1.
29191 - Avoid an integer underflow when the dir authority decides whether
29192 a router is stable: we might wrongly label it stable, and compute
29193 a slightly wrong median stability, when a descriptor is published
29195 - Fix a place where we might trigger an assert if we can't build our
29196 own server descriptor yet.
29199 Changes in version 0.1.1.22 - 2006-07-05
29201 - Fix a big bug that was causing servers to not find themselves
29202 reachable if they changed IP addresses. Since only 0.1.1.22+
29203 servers can do reachability testing correctly, now we automatically
29204 make sure to test via one of these.
29205 - Fix to allow clients and mirrors to learn directory info from
29206 descriptor downloads that get cut off partway through.
29207 - Directory authorities had a bug in deciding if a newly published
29208 descriptor was novel enough to make everybody want a copy -- a few
29209 servers seem to be publishing new descriptors many times a minute.
29211 - Fix a rare bug that was causing some servers to complain about
29212 "closing wedged cpuworkers" and skip some circuit create requests.
29213 - Make the Exit flag in directory status documents actually work.
29216 Changes in version 0.1.1.21 - 2006-06-10
29217 o Crash and assert fixes from 0.1.1.20:
29218 - Fix a rare crash on Tor servers that have enabled hibernation.
29219 - Fix a seg fault on startup for Tor networks that use only one
29220 directory authority.
29221 - Fix an assert from a race condition that occurs on Tor servers
29222 while exiting, where various threads are trying to log that they're
29223 exiting, and delete the logs, at the same time.
29224 - Make our unit tests pass again on certain obscure platforms.
29227 - Add support for building SUSE RPM packages.
29228 - Speed up initial bootstrapping for clients: if we are making our
29229 first ever connection to any entry guard, then don't mark it down
29231 - When only one Tor server in the network is labelled as a guard,
29232 and we've already picked him, we would cycle endlessly picking him
29233 again, being unhappy about it, etc. Now we specifically exclude
29234 current guards when picking a new guard.
29235 - Servers send create cells more reliably after the TLS connection
29236 is established: we were sometimes forgetting to send half of them
29237 when we had more than one pending.
29238 - If we get a create cell that asks us to extend somewhere, but the
29239 Tor server there doesn't match the expected digest, we now send
29240 a destroy cell back, rather than silently doing nothing.
29241 - Make options->RedirectExit work again.
29242 - Make cookie authentication for the controller work again.
29243 - Stop being picky about unusual characters in the arguments to
29244 mapaddress. It's none of our business.
29245 - Add a new config option "TestVia" that lets you specify preferred
29246 middle hops to use for test circuits. Perhaps this will let me
29247 debug the reachability problems better.
29249 o Log / documentation fixes:
29250 - If we're a server and some peer has a broken TLS certificate, don't
29251 log about it unless ProtocolWarnings is set, i.e., we want to hear
29252 about protocol violations by others.
29253 - Fix spelling of VirtualAddrNetwork in man page.
29254 - Add a better explanation at the top of the autogenerated torrc file
29255 about what happened to our old torrc.
29258 Changes in version 0.1.1.20 - 2006-05-23
29260 - Downgrade a log severity where servers complain that they're
29262 - Avoid a compile warning on FreeBSD.
29263 - Remove string size limit on NEWDESC messages; solve bug 291.
29264 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
29265 more thoroughly when we're running on windows.
29268 Changes in version 0.1.1.19-rc - 2006-05-03
29270 - Regenerate our local descriptor if it's dirty and we try to use
29271 it locally (e.g. if it changes during reachability detection).
29272 - If we setconf our ORPort to 0, we continued to listen on the
29273 old ORPort and receive connections.
29274 - Avoid a second warning about machine/limits.h on Debian
29276 - Be willing to add our own routerinfo into the routerlist.
29277 Now authorities will include themselves in their directories
29278 and network-statuses.
29279 - Stop trying to upload rendezvous descriptors to every
29280 directory authority: only try the v1 authorities.
29281 - Servers no longer complain when they think they're not
29282 registered with the directory authorities. There were too many
29284 - Backport dist-rpm changes so rpms can be built without errors.
29287 - Implement an option, VirtualAddrMask, to set which addresses
29288 get handed out in response to mapaddress requests. This works
29289 around a bug in tsocks where 127.0.0.0/8 is never socksified.
29292 Changes in version 0.1.1.18-rc - 2006-04-10
29294 - Work harder to download live network-statuses from all the
29295 directory authorities we know about. Improve the threshold
29296 decision logic so we're more robust to edge cases.
29297 - When fetching rendezvous descriptors, we were willing to ask
29298 v2 authorities too, which would always return 404.
29301 - Stop listing down or invalid nodes in the v1 directory. This will
29302 reduce its bulk by about 1/3, and reduce load on directory
29304 - When deciding whether a router is Fast or Guard-worthy, consider
29305 his advertised BandwidthRate and not just the BandwidthCapacity.
29306 - No longer ship INSTALL and README files -- they are useless now.
29307 - Force rpmbuild to behave and honor target_cpu.
29308 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
29309 - Start to include translated versions of the tor-doc-*.html
29310 files, along with the screenshots. Still needs more work.
29311 - Start sending back 512 and 451 errors if mapaddress fails,
29312 rather than not sending anything back at all.
29313 - When we fail to bind or listen on an incoming or outgoing
29314 socket, we should close it before failing. otherwise we just
29315 leak it. (thanks to weasel for finding.)
29316 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
29317 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
29318 - Make NoPublish (even though deprecated) work again.
29319 - Fix a minor security flaw where a versioning auth dirserver
29320 could list a recommended version many times in a row to make
29321 clients more convinced that it's recommended.
29322 - Fix crash bug if there are two unregistered servers running
29323 with the same nickname, one of them is down, and you ask for
29324 them by nickname in your EntryNodes or ExitNodes. Also, try
29325 to pick the one that's running rather than an arbitrary one.
29326 - Fix an infinite loop we could hit if we go offline for too long.
29327 - Complain when we hit WSAENOBUFS on recv() or write() too.
29328 Perhaps this will help us hunt the bug.
29329 - If you're not a versioning dirserver, don't put the string
29330 "client-versions \nserver-versions \n" in your network-status.
29331 - Lower the minimum required number of file descriptors to 1000,
29332 so we can have some overhead for Valgrind on Linux, where the
29333 default ulimit -n is 1024.
29336 - Add tor.dizum.com as the fifth authoritative directory server.
29337 - Add a new config option FetchUselessDescriptors, off by default,
29338 for when you plan to run "exitlist" on your client and you want
29339 to know about even the non-running descriptors.
29342 Changes in version 0.1.1.17-rc - 2006-03-28
29344 - Clients and servers since 0.1.1.10-alpha have been expiring
29345 connections whenever they are idle for 5 minutes and they *do*
29346 have circuits on them. Oops. With this new version, clients will
29347 discard their previous entry guard choices and avoid choosing
29348 entry guards running these flawed versions.
29349 - Fix memory leak when uncompressing concatenated zlib streams. This
29350 was causing substantial leaks over time on Tor servers.
29351 - The v1 directory was including servers as much as 48 hours old,
29352 because that's how the new routerlist->routers works. Now only
29353 include them if they're 20 hours old or less.
29356 - Resume building on irix64, netbsd 2.0, etc.
29357 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
29359 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
29360 and it is confusing some users.
29361 - Mirrors stop caching the v1 directory so often.
29362 - Make the max number of old descriptors that a cache will hold
29363 rise with the number of directory authorities, so we can scale.
29364 - Change our win32 uname() hack to be more forgiving about what
29365 win32 versions it thinks it's found.
29368 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
29370 - When the controller's *setconf commands fail, collect an error
29371 message in a string and hand it back to the controller.
29372 - Make the v2 dir's "Fast" flag based on relative capacity, just
29373 like "Stable" is based on median uptime. Name everything in the
29374 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
29375 - Log server fingerprint on startup, so new server operators don't
29376 have to go hunting around their filesystem for it.
29377 - Return a robots.txt on our dirport to discourage google indexing.
29378 - Let the controller ask for GETINFO dir/status/foo so it can ask
29379 directly rather than connecting to the dir port. Only works when
29380 dirport is set for now.
29382 o New config options rather than constants in the code:
29383 - SocksTimeout: How long do we let a socks connection wait
29384 unattached before we fail it?
29385 - CircuitBuildTimeout: Cull non-open circuits that were born
29386 at least this many seconds ago.
29387 - CircuitIdleTimeout: Cull open clean circuits that were born
29388 at least this many seconds ago.
29391 Changes in version 0.1.1.16-rc - 2006-03-18
29392 o Bugfixes on 0.1.1.15-rc:
29393 - Fix assert when the controller asks to attachstream a connect-wait
29394 or resolve-wait stream.
29395 - Now do address rewriting when the controller asks us to attach
29396 to a particular circuit too. This will let Blossom specify
29397 "moria2.exit" without having to learn what moria2's IP address is.
29398 - Make the "tor --verify-config" command-line work again, so people
29399 can automatically check if their torrc will parse.
29400 - Authoritative dirservers no longer require an open connection from
29401 a server to consider him "reachable". We need this change because
29402 when we add new auth dirservers, old servers won't know not to
29404 - Let Tor build on Sun CC again.
29405 - Fix an off-by-one buffer size in dirserv.c that magically never
29406 hit our three authorities but broke sjmurdoch's own tor network.
29407 - If we as a directory mirror don't know of any v1 directory
29408 authorities, then don't try to cache any v1 directories.
29409 - Stop warning about unknown servers in our family when they are
29410 given as hex digests.
29411 - Stop complaining as quickly to the server operator that he
29412 hasn't registered his nickname/key binding.
29413 - Various cleanups so we can add new V2 Auth Dirservers.
29414 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
29415 reflect the updated flags in our v2 dir protocol.
29416 - Resume allowing non-printable characters for exit streams (both
29417 for connecting and for resolving). Now we tolerate applications
29418 that don't follow the RFCs. But continue to block malformed names
29421 o Bugfixes on 0.1.0.x:
29422 - Fix assert bug in close_logs(): when we close and delete logs,
29423 remove them all from the global "logfiles" list.
29424 - Fix minor integer overflow in calculating when we expect to use up
29425 our bandwidth allocation before hibernating.
29426 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29427 there are multiple SSLs installed with different versions.
29428 - When we try to be a server and Address is not explicitly set and
29429 our hostname resolves to a private IP address, try to use an
29430 interface address if it has a public address. Now Windows machines
29431 that think of themselves as localhost can work by default.
29434 - Let the controller ask for GETINFO dir/server/foo so it can ask
29435 directly rather than connecting to the dir port.
29436 - Let the controller tell us about certain router descriptors
29437 that it doesn't want Tor to use in circuits. Implement
29438 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29439 - New config option SafeSocks to reject all application connections
29440 using unsafe socks protocols. Defaults to off.
29443 Changes in version 0.1.1.15-rc - 2006-03-11
29444 o Bugfixes and cleanups:
29445 - When we're printing strings from the network, don't try to print
29446 non-printable characters. This protects us against shell escape
29447 sequence exploits, and also against attacks to fool humans into
29448 misreading their logs.
29449 - Fix a bug where Tor would fail to establish any connections if you
29450 left it off for 24 hours and then started it: we were happy with
29451 the obsolete network statuses, but they all referred to router
29452 descriptors that were too old to fetch, so we ended up with no
29453 valid router descriptors.
29454 - Fix a seg fault in the controller's "getinfo orconn-status"
29455 command while listing status on incoming handshaking connections.
29456 Introduce a status name "NEW" for these connections.
29457 - If we get a linelist or linelist_s config option from the torrc
29458 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29459 silently resetting it to its default.
29460 - Don't abandon entry guards until they've been down or gone for
29462 - Cleaner and quieter log messages.
29465 - New controller signal NEWNYM that makes new application requests
29466 use clean circuits.
29467 - Add a new circuit purpose 'controller' to let the controller ask
29468 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29469 controller command to let you specify the purpose if you're
29470 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29471 command to let you change a circuit's purpose after it's been
29473 - Accept "private:*" in routerdesc exit policies; not generated yet
29474 because older Tors do not understand it.
29475 - Add BSD-style contributed startup script "rc.subr" from Peter
29479 Changes in version 0.1.1.14-alpha - 2006-02-20
29480 o Bugfixes on 0.1.1.x:
29481 - Don't die if we ask for a stdout or stderr log (even implicitly)
29482 and we're set to RunAsDaemon -- just warn.
29483 - We still had a few bugs in the OR connection rotation code that
29484 caused directory servers to slowly aggregate connections to other
29485 fast Tor servers. This time for sure!
29486 - Make log entries on Win32 include the name of the function again.
29487 - We were treating a pair of exit policies if they were equal even
29488 if one said accept and the other said reject -- causing us to
29489 not always publish a new descriptor since we thought nothing
29491 - Retry pending server downloads as well as pending networkstatus
29492 downloads when we unexpectedly get a socks request.
29493 - We were ignoring the IS_FAST flag in the directory status,
29494 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29496 - If the controller's SAVECONF command fails (e.g. due to file
29497 permissions), let the controller know that it failed.
29500 - If we're trying to be a Tor server and running Windows 95/98/ME
29501 as a server, explain that we'll likely crash.
29502 - When we're a server, a client asks for an old-style directory,
29503 and our write bucket is empty, don't give it to him. This way
29504 small servers can continue to serve the directory *sometimes*,
29505 without getting overloaded.
29506 - Compress exit policies even more -- look for duplicate lines
29508 - Clients now honor the "guard" flag in the router status when
29509 picking entry guards, rather than looking at is_fast or is_stable.
29510 - Retain unrecognized lines in $DATADIR/state file, so that we can
29511 be forward-compatible.
29512 - Generate 18.0.0.0/8 address policy format in descs when we can;
29513 warn when the mask is not reducible to a bit-prefix.
29514 - Let the user set ControlListenAddress in the torrc. This can be
29515 dangerous, but there are some cases (like a secured LAN) where it
29517 - Split ReachableAddresses into ReachableDirAddresses and
29518 ReachableORAddresses, so we can restrict Dir conns to port 80
29519 and OR conns to port 443.
29520 - Now we can target arch and OS in rpm builds (contributed by
29521 Phobos). Also make the resulting dist-rpm filename match the
29523 - New config options to help controllers: FetchServerDescriptors
29524 and FetchHidServDescriptors for whether to fetch server
29525 info and hidserv info or let the controller do it, and
29526 PublishServerDescriptor and PublishHidServDescriptors.
29527 - Also let the controller set the __AllDirActionsPrivate config
29528 option if you want all directory fetches/publishes to happen via
29529 Tor (it assumes your controller bootstraps your circuits).
29532 Changes in version 0.1.0.17 - 2006-02-17
29533 o Crash bugfixes on 0.1.0.x:
29534 - When servers with a non-zero DirPort came out of hibernation,
29535 sometimes they would trigger an assert.
29537 o Other important bugfixes:
29538 - On platforms that don't have getrlimit (like Windows), we were
29539 artificially constraining ourselves to a max of 1024
29540 connections. Now just assume that we can handle as many as 15000
29541 connections. Hopefully this won't cause other problems.
29543 o Backported features:
29544 - When we're a server, a client asks for an old-style directory,
29545 and our write bucket is empty, don't give it to him. This way
29546 small servers can continue to serve the directory *sometimes*,
29547 without getting overloaded.
29548 - Whenever you get a 503 in response to a directory fetch, try
29549 once more. This will become important once servers start sending
29550 503's whenever they feel busy.
29551 - Fetch a new directory every 120 minutes, not every 40 minutes.
29552 Now that we have hundreds of thousands of users running the old
29553 directory algorithm, it's starting to hurt a lot.
29554 - Bump up the period for forcing a hidden service descriptor upload
29555 from 20 minutes to 1 hour.
29558 Changes in version 0.1.1.13-alpha - 2006-02-09
29559 o Crashes in 0.1.1.x:
29560 - When you tried to setconf ORPort via the controller, Tor would
29561 crash. So people using TorCP to become a server were sad.
29562 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29563 servers. The problem appears to be something do with OpenSSL's
29564 random number generation, or how we call it, or something. Let me
29565 know if the crashes continue.
29566 - Turn crypto hardware acceleration off by default, until we find
29567 somebody smart who can test it for us. (It appears to produce
29568 seg faults in at least some cases.)
29569 - Fix a rare assert error when we've tried all intro points for
29570 a hidden service and we try fetching the service descriptor again:
29571 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29574 - Fix a major load balance bug: we were round-robining in 16 KB
29575 chunks, and servers with bandwidthrate of 20 KB, while downloading
29576 a 600 KB directory, would starve their other connections. Now we
29577 try to be a bit more fair.
29578 - Dir authorities and mirrors were never expiring the newest
29579 descriptor for each server, causing memory and directory bloat.
29580 - Fix memory-bloating and connection-bloating bug on servers: We
29581 were never closing any connection that had ever had a circuit on
29582 it, because we were checking conn->n_circuits == 0, yet we had a
29583 bug that let it go negative.
29584 - Make Tor work using squid as your http proxy again -- squid
29585 returns an error if you ask for a URL that's too long, and it uses
29586 a really generic error message. Plus, many people are behind a
29587 transparent squid so they don't even realize it.
29588 - On platforms that don't have getrlimit (like Windows), we were
29589 artificially constraining ourselves to a max of 1024
29590 connections. Now just assume that we can handle as many as 15000
29591 connections. Hopefully this won't cause other problems.
29592 - Add a new config option ExitPolicyRejectPrivate which defaults to
29593 1. This means all exit policies will begin with rejecting private
29594 addresses, unless the server operator explicitly turns it off.
29597 - Clients no longer download descriptors for non-running
29599 - Before we add new directory authorities, we should make it
29600 clear that only v1 authorities should receive/publish hidden
29601 service descriptors.
29604 - As soon as we've fetched some more directory info, immediately
29605 try to download more server descriptors. This way we don't have
29606 a 10 second pause during initial bootstrapping.
29607 - Remove even more loud log messages that the server operator can't
29609 - When we're running an obsolete or un-recommended version, make
29610 the log message more clear about what the problem is and what
29611 versions *are* still recommended.
29612 - Provide a more useful warn message when our onion queue gets full:
29613 the CPU is too slow or the exit policy is too liberal.
29614 - Don't warn when we receive a 503 from a dirserver/cache -- this
29615 will pave the way for them being able to refuse if they're busy.
29616 - When we fail to bind a listener, try to provide a more useful
29617 log message: e.g., "Is Tor already running?"
29618 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29619 Goldberg can prove things about our handshake protocol more
29621 - MaxConn has been obsolete for a while now. Document the ConnLimit
29622 config option, which is a *minimum* number of file descriptors
29623 that must be available else Tor refuses to start.
29624 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29625 if you log to syslog and want something other than LOG_DAEMON.
29626 - Make dirservers generate a separate "guard" flag to mean,
29627 "would make a good entry guard". Make clients parse it and vote
29628 on it. Not used by clients yet.
29629 - Implement --with-libevent-dir option to ./configure. Also, improve
29630 search techniques to find libevent, and use those for openssl too.
29631 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
29632 - Only start testing reachability once we've established a
29633 circuit. This will make startup on dirservers less noisy.
29634 - Don't try to upload hidden service descriptors until we have
29635 established a circuit.
29636 - Fix the controller's "attachstream 0" command to treat conn like
29637 it just connected, doing address remapping, handling .exit and
29638 .onion idioms, and so on. Now we're more uniform in making sure
29639 that the controller hears about new and closing connections.
29642 Changes in version 0.1.1.12-alpha - 2006-01-11
29643 o Bugfixes on 0.1.1.x:
29644 - The fix to close duplicate server connections was closing all
29645 Tor client connections if they didn't establish a circuit
29646 quickly enough. Oops.
29647 - Fix minor memory issue (double-free) that happened on exit.
29649 o Bugfixes on 0.1.0.x:
29650 - Tor didn't warn when it failed to open a log file.
29653 Changes in version 0.1.1.11-alpha - 2006-01-10
29654 o Crashes in 0.1.1.x:
29655 - Include all the assert/crash fixes from 0.1.0.16.
29656 - If you start Tor and then quit very quickly, there were some
29657 races that tried to free things that weren't allocated yet.
29658 - Fix a rare memory stomp if you're running hidden services.
29659 - Fix segfault when specifying DirServer in config without nickname.
29660 - Fix a seg fault when you finish connecting to a server but at
29661 that moment you dump his server descriptor.
29662 - Extendcircuit and Attachstream controller commands would
29663 assert/crash if you don't give them enough arguments.
29664 - Fix an assert error when we're out of space in the connection_list
29665 and we try to post a hidden service descriptor (reported by weasel).
29666 - If you specify a relative torrc path and you set RunAsDaemon in
29667 your torrc, then it chdir()'s to the new directory. If you HUP,
29668 it tries to load the new torrc location, fails, and exits.
29669 The fix: no longer allow a relative path to torrc using -f.
29672 - Implement "entry guards": automatically choose a handful of entry
29673 nodes and stick with them for all circuits. Only pick new guards
29674 when the ones you have are unsuitable, and if the old guards
29675 become suitable again, switch back. This will increase security
29676 dramatically against certain end-point attacks. The EntryNodes
29677 config option now provides some hints about which entry guards you
29678 want to use most; and StrictEntryNodes means to only use those.
29679 - New directory logic: download by descriptor digest, not by
29680 fingerprint. Caches try to download all listed digests from
29681 authorities; clients try to download "best" digests from caches.
29682 This avoids partitioning and isolating attacks better.
29683 - Make the "stable" router flag in network-status be the median of
29684 the uptimes of running valid servers, and make clients pay
29685 attention to the network-status flags. Thus the cutoff adapts
29686 to the stability of the network as a whole, making IRC, IM, etc
29687 connections more reliable.
29690 - Tor servers with dynamic IP addresses were needing to wait 18
29691 hours before they could start doing reachability testing using
29692 the new IP address and ports. This is because they were using
29693 the internal descriptor to learn what to test, yet they were only
29694 rebuilding the descriptor once they decided they were reachable.
29695 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
29696 to download certain server descriptors, throw them away, and then
29697 fetch them again after 30 minutes. Now mirrors throw away these
29698 server descriptors so clients can't get them.
29699 - We were leaving duplicate connections to other ORs open for a week,
29700 rather than closing them once we detect a duplicate. This only
29701 really affected authdirservers, but it affected them a lot.
29702 - Spread the authdirservers' reachability testing over the entire
29703 testing interval, so we don't try to do 500 TLS's at once every
29707 - If the network is down, and we try to connect to a conn because
29708 we have a circuit in mind, and we timeout (30 seconds) because the
29709 network never answers, we were expiring the circuit, but we weren't
29710 obsoleting the connection or telling the entry_guards functions.
29711 - Some Tor servers process billions of cells per day. These statistics
29712 need to be uint64_t's.
29713 - Check for integer overflows in more places, when adding elements
29714 to smartlists. This could possibly prevent a buffer overflow
29715 on malicious huge inputs. I don't see any, but I haven't looked
29717 - ReachableAddresses kept growing new "reject *:*" lines on every
29719 - When you "setconf log" via the controller, it should remove all
29720 logs. We were automatically adding back in a "log notice stdout".
29721 - Newly bootstrapped Tor networks couldn't establish hidden service
29722 circuits until they had nodes with high uptime. Be more tolerant.
29723 - We were marking servers down when they could not answer every piece
29724 of the directory request we sent them. This was far too harsh.
29725 - Fix the torify (tsocks) config file to not use Tor for localhost
29727 - Directory authorities now go to the proper authority when asking for
29728 a networkstatus, even when they want a compressed one.
29729 - Fix a harmless bug that was causing Tor servers to log
29730 "Got an end because of misc error, but we're not an AP. Closing."
29731 - Authorities were treating their own descriptor changes as cosmetic,
29732 meaning the descriptor available in the network-status and the
29733 descriptor that clients downloaded were different.
29734 - The OS X installer was adding a symlink for tor_resolve but
29735 the binary was called tor-resolve (reported by Thomas Hardly).
29736 - Workaround a problem with some http proxies where they refuse GET
29737 requests that specify "Content-Length: 0" (reported by Adrian).
29738 - Fix wrong log message when you add a "HiddenServiceNodes" config
29739 line without any HiddenServiceDir line (reported by Chris Thomas).
29742 - Write the TorVersion into the state file so we have a prayer of
29743 keeping forward and backward compatibility.
29744 - Revive the FascistFirewall config option rather than eliminating it:
29745 now it's a synonym for ReachableAddresses *:80,*:443.
29746 - Clients choose directory servers from the network status lists,
29747 not from their internal list of router descriptors. Now they can
29748 go to caches directly rather than needing to go to authorities
29750 - Directory authorities ignore router descriptors that have only
29751 cosmetic differences: do this for 0.1.0.x servers now too.
29752 - Add a new flag to network-status indicating whether the server
29753 can answer v2 directory requests too.
29754 - Authdirs now stop whining so loudly about bad descriptors that
29755 they fetch from other dirservers. So when there's a log complaint,
29756 it's for sure from a freshly uploaded descriptor.
29757 - Reduce memory requirements in our structs by changing the order
29759 - There used to be two ways to specify your listening ports in a
29760 server descriptor: on the "router" line and with a separate "ports"
29761 line. Remove support for the "ports" line.
29762 - New config option "AuthDirRejectUnlisted" for auth dirservers as
29763 a panic button: if we get flooded with unusable servers we can
29764 revert to only listing servers in the approved-routers file.
29765 - Auth dir servers can now mark a fingerprint as "!reject" or
29766 "!invalid" in the approved-routers file (as its nickname), to
29767 refuse descriptors outright or include them but marked as invalid.
29768 - Servers store bandwidth history across restarts/crashes.
29769 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
29770 get a better idea of why their circuits failed. Not used yet.
29771 - Directory mirrors now cache up to 16 unrecognized network-status
29772 docs. Now we can add new authdirservers and they'll be cached too.
29773 - When picking a random directory, prefer non-authorities if any
29775 - New controller option "getinfo desc/all-recent" to fetch the
29776 latest server descriptor for every router that Tor knows about.
29779 Changes in version 0.1.0.16 - 2006-01-02
29780 o Crash bugfixes on 0.1.0.x:
29781 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29782 corrupting the heap, losing FDs, or crashing when we need to resize
29783 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29784 - It turns out sparc64 platforms crash on unaligned memory access
29785 too -- so detect and avoid this.
29786 - Handle truncated compressed data correctly (by detecting it and
29788 - Fix possible-but-unlikely free(NULL) in control.c.
29789 - When we were closing connections, there was a rare case that
29790 stomped on memory, triggering seg faults and asserts.
29791 - Avoid potential infinite recursion when building a descriptor. (We
29792 don't know that it ever happened, but better to fix it anyway.)
29793 - We were neglecting to unlink marked circuits from soon-to-close OR
29794 connections, which caused some rare scribbling on freed memory.
29795 - Fix a memory stomping race bug when closing the joining point of two
29796 rendezvous circuits.
29797 - Fix an assert in time parsing found by Steven Murdoch.
29799 o Other bugfixes on 0.1.0.x:
29800 - When we're doing reachability testing, provide more useful log
29801 messages so the operator knows what to expect.
29802 - Do not check whether DirPort is reachable when we are suppressing
29803 advertising it because of hibernation.
29804 - When building with -static or on Solaris, we sometimes needed -ldl.
29805 - When we're deciding whether a stream has enough circuits around
29806 that can handle it, count the freshly dirty ones and not the ones
29807 that are so dirty they won't be able to handle it.
29808 - When we're expiring old circuits, we had a logic error that caused
29809 us to close new rendezvous circuits rather than old ones.
29810 - Give a more helpful log message when you try to change ORPort via
29811 the controller: you should upgrade Tor if you want that to work.
29812 - We were failing to parse Tor versions that start with "Tor ".
29813 - Tolerate faulty streams better: when a stream fails for reason
29814 exitpolicy, stop assuming that the router is lying about his exit
29815 policy. When a stream fails for reason misc, allow it to retry just
29816 as if it was resolvefailed. When a stream has failed three times,
29817 reset its failure count so we can try again and get all three tries.
29820 Changes in version 0.1.1.10-alpha - 2005-12-11
29821 o Correctness bugfixes on 0.1.0.x:
29822 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
29823 corrupting the heap, losing FDs, or crashing when we need to resize
29824 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
29825 - Stop doing the complex voodoo overkill checking for insecure
29826 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
29827 - When we were closing connections, there was a rare case that
29828 stomped on memory, triggering seg faults and asserts.
29829 - We were neglecting to unlink marked circuits from soon-to-close OR
29830 connections, which caused some rare scribbling on freed memory.
29831 - When we're deciding whether a stream has enough circuits around
29832 that can handle it, count the freshly dirty ones and not the ones
29833 that are so dirty they won't be able to handle it.
29834 - Recover better from TCP connections to Tor servers that are
29835 broken but don't tell you (it happens!); and rotate TLS
29836 connections once a week.
29837 - When we're expiring old circuits, we had a logic error that caused
29838 us to close new rendezvous circuits rather than old ones.
29839 - Fix a scary-looking but apparently harmless bug where circuits
29840 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
29841 servers, and never switch to state CIRCUIT_STATE_OPEN.
29842 - When building with -static or on Solaris, we sometimes needed to
29844 - Give a useful message when people run Tor as the wrong user,
29845 rather than telling them to start chowning random directories.
29846 - We were failing to inform the controller about new .onion streams.
29848 o Security bugfixes on 0.1.0.x:
29849 - Refuse server descriptors if the fingerprint line doesn't match
29850 the included identity key. Tor doesn't care, but other apps (and
29851 humans) might actually be trusting the fingerprint line.
29852 - We used to kill the circuit when we receive a relay command we
29853 don't recognize. Now we just drop it.
29854 - Start obeying our firewall options more rigorously:
29855 . If we can't get to a dirserver directly, try going via Tor.
29856 . Don't ever try to connect (as a client) to a place our
29857 firewall options forbid.
29858 . If we specify a proxy and also firewall options, obey the
29859 firewall options even when we're using the proxy: some proxies
29860 can only proxy to certain destinations.
29861 - Fix a bug found by Lasse Overlier: when we were making internal
29862 circuits (intended to be cannibalized later for rendezvous and
29863 introduction circuits), we were picking them so that they had
29864 useful exit nodes. There was no need for this, and it actually
29865 aids some statistical attacks.
29866 - Start treating internal circuits and exit circuits separately.
29867 It's important to keep them separate because internal circuits
29868 have their last hops picked like middle hops, rather than like
29869 exit hops. So exiting on them will break the user's expectations.
29871 o Bugfixes on 0.1.1.x:
29872 - Take out the mis-feature where we tried to detect IP address
29873 flapping for people with DynDNS, and chose not to upload a new
29874 server descriptor sometimes.
29875 - Try to be compatible with OpenSSL 0.9.6 again.
29876 - Log fix: when the controller is logging about .onion addresses,
29877 sometimes it didn't include the ".onion" part of the address.
29878 - Don't try to modify options->DirServers internally -- if the
29879 user didn't specify any, just add the default ones directly to
29880 the trusted dirserver list. This fixes a bug where people running
29881 controllers would use SETCONF on some totally unrelated config
29882 option, and Tor would start yelling at them about changing their
29884 - Let the controller's redirectstream command specify a port, in
29885 case the controller wants to change that too.
29886 - When we requested a pile of server descriptors, we sometimes
29887 accidentally launched a duplicate request for the first one.
29888 - Bugfix for trackhostexits: write down the fingerprint of the
29889 chosen exit, not its nickname, because the chosen exit might not
29891 - When parsing foo.exit, if foo is unknown, and we are leaving
29892 circuits unattached, set the chosen_exit field and leave the
29893 address empty. This matters because controllers got confused
29895 - Directory authorities no longer try to download server
29896 descriptors that they know they will reject.
29898 o Features and updates:
29899 - Replace balanced trees with hash tables: this should make stuff
29900 significantly faster.
29901 - Resume using the AES counter-mode implementation that we ship,
29902 rather than OpenSSL's. Ours is significantly faster.
29903 - Many other CPU and memory improvements.
29904 - Add a new config option FastFirstHopPK (on by default) so clients
29905 do a trivial crypto handshake for their first hop, since TLS has
29906 already taken care of confidentiality and authentication.
29907 - Add a new config option TestSocks so people can see if their
29908 applications are using socks4, socks4a, socks5-with-ip, or
29909 socks5-with-hostname. This way they don't have to keep mucking
29910 with tcpdump and wondering if something got cached somewhere.
29911 - Warn when listening on a public address for socks. I suspect a
29912 lot of people are setting themselves up as open socks proxies,
29913 and they have no idea that jerks on the Internet are using them,
29914 since they simply proxy the traffic into the Tor network.
29915 - Add "private:*" as an alias in configuration for policies. Now
29916 you can simplify your exit policy rather than needing to list
29917 every single internal or nonroutable network space.
29918 - Add a new controller event type that allows controllers to get
29919 all server descriptors that were uploaded to a router in its role
29920 as authoritative dirserver.
29921 - Start shipping socks-extensions.txt, tor-doc-unix.html,
29922 tor-doc-server.html, and stylesheet.css in the tarball.
29923 - Stop shipping tor-doc.html in the tarball.
29926 Changes in version 0.1.1.9-alpha - 2005-11-15
29927 o Usability improvements:
29928 - Start calling it FooListenAddress rather than FooBindAddress,
29929 since few of our users know what it means to bind an address
29931 - Reduce clutter in server logs. We're going to try to make
29932 them actually usable now. New config option ProtocolWarnings that
29933 lets you hear about how _other Tors_ are breaking the protocol. Off
29935 - Divide log messages into logging domains. Once we put some sort
29936 of interface on this, it will let people looking at more verbose
29937 log levels specify the topics they want to hear more about.
29938 - Make directory servers return better http 404 error messages
29939 instead of a generic "Servers unavailable".
29940 - Check for even more Windows version flags when writing the platform
29941 string in server descriptors, and note any we don't recognize.
29942 - Clean up more of the OpenSSL memory when exiting, so we can detect
29943 memory leaks better.
29944 - Make directory authorities be non-versioning, non-naming by
29945 default. Now we can add new directory servers without requiring
29946 their operators to pay close attention.
29947 - When logging via syslog, include the pid whenever we provide
29948 a log entry. Suggested by Todd Fries.
29950 o Performance improvements:
29951 - Directory servers now silently throw away new descriptors that
29952 haven't changed much if the timestamps are similar. We do this to
29953 tolerate older Tor servers that upload a new descriptor every 15
29954 minutes. (It seemed like a good idea at the time.)
29955 - Inline bottleneck smartlist functions; use fast versions by default.
29956 - Add a "Map from digest to void*" abstraction digestmap_t so we
29957 can do less hex encoding/decoding. Use it in router_get_by_digest()
29958 to resolve a performance bottleneck.
29959 - Allow tor_gzip_uncompress to extract as much as possible from
29960 truncated compressed data. Try to extract as many
29961 descriptors as possible from truncated http responses (when
29962 DIR_PURPOSE_FETCH_ROUTERDESC).
29963 - Make circ->onionskin a pointer, not a static array. moria2 was using
29964 125000 circuit_t's after it had been up for a few weeks, which
29965 translates to 20+ megs of wasted space.
29966 - The private half of our EDH handshake keys are now chosen out
29967 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
29969 o Security improvements:
29970 - Start making directory caches retain old routerinfos, so soon
29971 clients can start asking by digest of descriptor rather than by
29972 fingerprint of server.
29973 - Add half our entropy from RAND_poll in OpenSSL. This knows how
29974 to use egd (if present), openbsd weirdness (if present), vms/os2
29975 weirdness (if we ever port there), and more in the future.
29977 o Bugfixes on 0.1.0.x:
29978 - Do round-robin writes of at most 16 kB per write. This might be
29979 more fair on loaded Tor servers, and it might resolve our Windows
29980 crash bug. It might also slow things down.
29981 - Our TLS handshakes were generating a single public/private
29982 keypair for the TLS context, rather than making a new one for
29983 each new connections. Oops. (But we were still rotating them
29984 periodically, so it's not so bad.)
29985 - When we were cannibalizing a circuit with a particular exit
29986 node in mind, we weren't checking to see if that exit node was
29987 already present earlier in the circuit. Oops.
29988 - When a Tor server's IP changes (e.g. from a dyndns address),
29989 upload a new descriptor so clients will learn too.
29990 - Really busy servers were keeping enough circuits open on stable
29991 connections that they were wrapping around the circuit_id
29992 space. (It's only two bytes.) This exposed a bug where we would
29993 feel free to reuse a circuit_id even if it still exists but has
29994 been marked for close. Try to fix this bug. Some bug remains.
29995 - If we would close a stream early (e.g. it asks for a .exit that
29996 we know would refuse it) but the LeaveStreamsUnattached config
29997 option is set by the controller, then don't close it.
29999 o Bugfixes on 0.1.1.8-alpha:
30000 - Fix a big pile of memory leaks, some of them serious.
30001 - Do not try to download a routerdesc if we would immediately reject
30003 - Resume inserting a newline between all router descriptors when
30004 generating (old style) signed directories, since our spec says
30006 - When providing content-type application/octet-stream for
30007 server descriptors using .z, we were leaving out the
30008 content-encoding header. Oops. (Everything tolerated this just
30009 fine, but that doesn't mean we need to be part of the problem.)
30010 - Fix a potential seg fault in getconf and getinfo using version 1
30011 of the controller protocol.
30012 - Avoid crash: do not check whether DirPort is reachable when we
30013 are suppressing it because of hibernation.
30014 - Make --hash-password not crash on exit.
30017 Changes in version 0.1.1.8-alpha - 2005-10-07
30018 o New features (major):
30019 - Clients don't download or use the directory anymore. Now they
30020 download and use network-statuses from the trusted dirservers,
30021 and fetch individual server descriptors as needed from mirrors.
30022 See dir-spec.txt for all the gory details.
30023 - Be more conservative about whether to advertise our DirPort.
30024 The main change is to not advertise if we're running at capacity
30025 and either a) we could hibernate or b) our capacity is low and
30026 we're using a default DirPort.
30027 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
30029 o New features (minor):
30030 - Try to be smart about when to retry network-status and
30031 server-descriptor fetches. Still needs some tuning.
30032 - Stop parsing, storing, or using running-routers output (but
30033 mirrors still cache and serve it).
30034 - Consider a threshold of versioning dirservers (dirservers who have
30035 an opinion about which Tor versions are still recommended) before
30036 deciding whether to warn the user that he's obsolete.
30037 - Dirservers can now reject/invalidate by key and IP, with the
30038 config options "AuthDirInvalid" and "AuthDirReject". This is
30039 useful since currently we automatically list servers as running
30040 and usable even if we know they're jerks.
30041 - Provide dire warnings to any users who set DirServer; move it out
30042 of torrc.sample and into torrc.complete.
30043 - Add MyFamily to torrc.sample in the server section.
30044 - Add nicknames to the DirServer line, so we can refer to them
30045 without requiring all our users to memorize their IP addresses.
30046 - When we get an EOF or a timeout on a directory connection, note
30047 how many bytes of serverdesc we are dropping. This will help
30048 us determine whether it is smart to parse incomplete serverdesc
30050 - Add a new function to "change pseudonyms" -- that is, to stop
30051 using any currently-dirty circuits for new streams, so we don't
30052 link new actions to old actions. Currently it's only called on
30053 HUP (or SIGNAL RELOAD).
30054 - On sighup, if UseHelperNodes changed to 1, use new circuits.
30055 - Start using RAND_bytes rather than RAND_pseudo_bytes from
30056 OpenSSL. Also, reseed our entropy every hour, not just at
30057 startup. And entropy in 512-bit chunks, not 160-bit chunks.
30059 o Fixes on 0.1.1.7-alpha:
30060 - Nobody ever implemented EVENT_ADDRMAP for control protocol
30061 version 0, so don't let version 0 controllers ask for it.
30062 - If you requested something with too many newlines via the
30063 v1 controller protocol, you could crash tor.
30064 - Fix a number of memory leaks, including some pretty serious ones.
30065 - Re-enable DirPort testing again, so Tor servers will be willing
30066 to advertise their DirPort if it's reachable.
30067 - On TLS handshake, only check the other router's nickname against
30068 its expected nickname if is_named is set.
30070 o Fixes forward-ported from 0.1.0.15:
30071 - Don't crash when we don't have any spare file descriptors and we
30072 try to spawn a dns or cpu worker.
30073 - Make the numbers in read-history and write-history into uint64s,
30074 so they don't overflow and publish negatives in the descriptor.
30076 o Fixes on 0.1.0.x:
30077 - For the OS X package's modified privoxy config file, comment
30078 out the "logfile" line so we don't log everything passed
30080 - We were whining about using socks4 or socks5-with-local-lookup
30081 even when it's an IP in the "virtual" range we designed exactly
30083 - We were leaking some memory every time the client changes IPs.
30084 - Never call free() on tor_malloc()d memory. This will help us
30085 use dmalloc to detect memory leaks.
30086 - Check for named servers when looking them up by nickname;
30087 warn when we'recalling a non-named server by its nickname;
30088 don't warn twice about the same name.
30089 - Try to list MyFamily elements by key, not by nickname, and warn
30090 if we've not heard of the server.
30091 - Make windows platform detection (uname equivalent) smarter.
30092 - It turns out sparc64 doesn't like unaligned access either.
30095 Changes in version 0.1.0.15 - 2005-09-23
30096 o Bugfixes on 0.1.0.x:
30097 - Reject ports 465 and 587 (spam targets) in default exit policy.
30098 - Don't crash when we don't have any spare file descriptors and we
30099 try to spawn a dns or cpu worker.
30100 - Get rid of IgnoreVersion undocumented config option, and make us
30101 only warn, never exit, when we're running an obsolete version.
30102 - Don't try to print a null string when your server finds itself to
30103 be unreachable and the Address config option is empty.
30104 - Make the numbers in read-history and write-history into uint64s,
30105 so they don't overflow and publish negatives in the descriptor.
30106 - Fix a minor memory leak in smartlist_string_remove().
30107 - We were only allowing ourselves to upload a server descriptor at
30108 most every 20 minutes, even if it changed earlier than that.
30109 - Clean up log entries that pointed to old URLs.
30112 Changes in version 0.1.1.7-alpha - 2005-09-14
30113 o Fixes on 0.1.1.6-alpha:
30114 - Exit servers were crashing when people asked them to make a
30115 connection to an address not in their exit policy.
30116 - Looking up a non-existent stream for a v1 control connection would
30118 - Fix a seg fault if we ask a dirserver for a descriptor by
30119 fingerprint but he doesn't know about him.
30120 - SETCONF was appending items to linelists, not clearing them.
30121 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
30122 out and refuse the setconf if it would fail.
30123 - Downgrade the dirserver log messages when whining about
30127 - Add Peter Palfrader's check-tor script to tor/contrib/
30128 It lets you easily check whether a given server (referenced by
30129 nickname) is reachable by you.
30130 - Numerous changes to move towards client-side v2 directories. Not
30133 o Fixes on 0.1.0.x:
30134 - If the user gave tor an odd number of command-line arguments,
30135 we were silently ignoring the last one. Now we complain and fail.
30136 [This wins the oldest-bug prize -- this bug has been present since
30137 November 2002, as released in Tor 0.0.0.]
30138 - Do not use unaligned memory access on alpha, mips, or mipsel.
30139 It *works*, but is very slow, so we treat them as if it doesn't.
30140 - Retry directory requests if we fail to get an answer we like
30141 from a given dirserver (we were retrying before, but only if
30142 we fail to connect).
30143 - When writing the RecommendedVersions line, sort them first.
30144 - When the client asked for a rendezvous port that the hidden
30145 service didn't want to provide, we were sending an IP address
30146 back along with the end cell. Fortunately, it was zero. But stop
30148 - Correct "your server is reachable" log entries to indicate that
30149 it was self-testing that told us so.
30152 Changes in version 0.1.1.6-alpha - 2005-09-09
30153 o Fixes on 0.1.1.5-alpha:
30154 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
30155 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
30156 - Fix bug with tor_memmem finding a match at the end of the string.
30157 - Make unit tests run without segfaulting.
30158 - Resolve some solaris x86 compile warnings.
30159 - Handle duplicate lines in approved-routers files without warning.
30160 - Fix bug where as soon as a server refused any requests due to his
30161 exit policy (e.g. when we ask for localhost and he tells us that's
30162 127.0.0.1 and he won't do it), we decided he wasn't obeying his
30163 exit policy using him for any exits.
30164 - Only do openssl hardware accelerator stuff if openssl version is
30167 o New controller features/fixes:
30168 - Add a "RESETCONF" command so you can set config options like
30169 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
30170 a config option in the torrc with no value, then it clears it
30171 entirely (rather than setting it to its default).
30172 - Add a "GETINFO config-file" to tell us where torrc is.
30173 - Avoid sending blank lines when GETINFO replies should be empty.
30174 - Add a QUIT command for the controller (for using it manually).
30175 - Fix a bug in SAVECONF that was adding default dirservers and
30176 other redundant entries to the torrc file.
30178 o Start on the new directory design:
30179 - Generate, publish, cache, serve new network-status format.
30180 - Publish individual descriptors (by fingerprint, by "all", and by
30182 - Publish client and server recommended versions separately.
30183 - Allow tor_gzip_uncompress() to handle multiple concatenated
30184 compressed strings. Serve compressed groups of router
30185 descriptors. The compression logic here could be more
30187 - Distinguish v1 authorities (all currently trusted directories)
30188 from v2 authorities (all trusted directories).
30189 - Change DirServers config line to note which dirs are v1 authorities.
30190 - Add configuration option "V1AuthoritativeDirectory 1" which
30191 moria1, moria2, and tor26 should set.
30192 - Remove option when getting directory cache to see whether they
30193 support running-routers; they all do now. Replace it with one
30194 to see whether caches support v2 stuff.
30197 - Dirservers now do their own external reachability testing of each
30198 Tor server, and only list them as running if they've been found to
30199 be reachable. We also send back warnings to the server's logs if
30200 it uploads a descriptor that we already believe is unreachable.
30201 - Implement exit enclaves: if we know an IP address for the
30202 destination, and there's a running Tor server at that address
30203 which allows exit to the destination, then extend the circuit to
30204 that exit first. This provides end-to-end encryption and end-to-end
30205 authentication. Also, if the user wants a .exit address or enclave,
30206 use 4 hops rather than 3, and cannibalize a general circ for it
30208 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
30209 controller. Also, rotate dns and cpu workers if the controller
30210 changes options that will affect them; and initialize the dns
30211 worker cache tree whether or not we start out as a server.
30212 - Only upload a new server descriptor when options change, 18
30213 hours have passed, uptime is reset, or bandwidth changes a lot.
30214 - Check [X-]Forwarded-For headers in HTTP requests when generating
30215 log messages. This lets people run dirservers (and caches) behind
30216 Apache but still know which IP addresses are causing warnings.
30218 o Config option changes:
30219 - Replace (Fascist)Firewall* config options with a new
30220 ReachableAddresses option that understands address policies.
30221 For example, "ReachableAddresses *:80,*:443"
30222 - Get rid of IgnoreVersion undocumented config option, and make us
30223 only warn, never exit, when we're running an obsolete version.
30224 - Make MonthlyAccountingStart config option truly obsolete now.
30226 o Fixes on 0.1.0.x:
30227 - Reject ports 465 and 587 in the default exit policy, since
30228 people have started using them for spam too.
30229 - It turns out we couldn't bootstrap a network since we added
30230 reachability detection in 0.1.0.1-rc. Good thing the Tor network
30231 has never gone down. Add an AssumeReachable config option to let
30232 servers and dirservers bootstrap. When we're trying to build a
30233 high-uptime or high-bandwidth circuit but there aren't enough
30234 suitable servers, try being less picky rather than simply failing.
30235 - Our logic to decide if the OR we connected to was the right guy
30236 was brittle and maybe open to a mitm for unverified routers.
30237 - We weren't cannibalizing circuits correctly for
30238 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
30239 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
30240 build those from scratch. This should make hidden services faster.
30241 - Predict required circuits better, with an eye toward making hidden
30242 services faster on the service end.
30243 - Retry streams if the exit node sends back a 'misc' failure. This
30244 should result in fewer random failures. Also, after failing
30245 from resolve failed or misc, reset the num failures, so we give
30246 it a fair shake next time we try.
30247 - Clean up the rendezvous warn log msgs, and downgrade some to info.
30248 - Reduce severity on logs about dns worker spawning and culling.
30249 - When we're shutting down and we do something like try to post a
30250 server descriptor or rendezvous descriptor, don't complain that
30251 we seem to be unreachable. Of course we are, we're shutting down.
30252 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
30253 We don't use them yet, but maybe one day our DNS resolver will be
30254 able to discover them.
30255 - Make ContactInfo mandatory for authoritative directory servers.
30256 - Require server descriptors to list IPv4 addresses -- hostnames
30257 are no longer allowed. This also fixes some potential security
30258 problems with people providing hostnames as their address and then
30259 preferentially resolving them to partition users.
30260 - Change log line for unreachability to explicitly suggest /etc/hosts
30261 as the culprit. Also make it clearer what IP address and ports we're
30262 testing for reachability.
30263 - Put quotes around user-supplied strings when logging so users are
30264 more likely to realize if they add bad characters (like quotes)
30266 - Let auth dir servers start without specifying an Address config
30268 - Make unit tests (and other invocations that aren't the real Tor)
30269 run without launching listeners, creating subdirectories, and so on.
30272 Changes in version 0.1.1.5-alpha - 2005-08-08
30273 o Bugfixes included in 0.1.0.14.
30275 o Bugfixes on 0.1.0.x:
30276 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
30277 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
30278 it would silently using ignore the 6668.
30281 Changes in version 0.1.0.14 - 2005-08-08
30282 o Bugfixes on 0.1.0.x:
30283 - Fix the other half of the bug with crypto handshakes
30285 - Fix an assert trigger if you send a 'signal term' via the
30286 controller when it's listening for 'event info' messages.
30289 Changes in version 0.1.1.4-alpha - 2005-08-04
30290 o Bugfixes included in 0.1.0.13.
30293 - Improve tor_gettimeofday() granularity on windows.
30294 - Make clients regenerate their keys when their IP address changes.
30295 - Implement some more GETINFO goodness: expose helper nodes, config
30296 options, getinfo keys.
30299 Changes in version 0.1.0.13 - 2005-08-04
30300 o Bugfixes on 0.1.0.x:
30301 - Fix a critical bug in the security of our crypto handshakes.
30302 - Fix a size_t underflow in smartlist_join_strings2() that made
30303 it do bad things when you hand it an empty smartlist.
30304 - Fix Windows installer to ship Tor license (thanks to Aphex for
30305 pointing out this oversight) and put a link to the doc directory
30307 - Explicitly set no-unaligned-access for sparc: it turns out the
30308 new gcc's let you compile broken code, but that doesn't make it
30312 Changes in version 0.1.1.3-alpha - 2005-07-23
30313 o Bugfixes on 0.1.1.2-alpha:
30314 - Fix a bug in handling the controller's "post descriptor"
30316 - Fix several bugs in handling the controller's "extend circuit"
30318 - Fix a bug in handling the controller's "stream status" event.
30319 - Fix an assert failure if we have a controller listening for
30320 circuit events and we go offline.
30321 - Re-allow hidden service descriptors to publish 0 intro points.
30322 - Fix a crash when generating your hidden service descriptor if
30323 you don't have enough intro points already.
30325 o New features on 0.1.1.2-alpha:
30326 - New controller function "getinfo accounting", to ask how
30327 many bytes we've used in this time period.
30328 - Experimental support for helper nodes: a lot of the risk from
30329 a small static adversary comes because users pick new random
30330 nodes every time they rebuild a circuit. Now users will try to
30331 stick to the same small set of entry nodes if they can. Not
30332 enabled by default yet.
30334 o Bugfixes on 0.1.0.12:
30335 - If you're an auth dir server, always publish your dirport,
30336 even if you haven't yet found yourself to be reachable.
30337 - Fix a size_t underflow in smartlist_join_strings2() that made
30338 it do bad things when you hand it an empty smartlist.
30341 Changes in version 0.1.0.12 - 2005-07-18
30342 o New directory servers:
30343 - tor26 has changed IP address.
30345 o Bugfixes on 0.1.0.x:
30346 - Fix a possible double-free in tor_gzip_uncompress().
30347 - When --disable-threads is set, do not search for or link against
30348 pthreads libraries.
30349 - Don't trigger an assert if an authoritative directory server
30350 claims its dirport is 0.
30351 - Fix bug with removing Tor as an NT service: some people were
30352 getting "The service did not return an error." Thanks to Matt
30356 Changes in version 0.1.1.2-alpha - 2005-07-15
30357 o New directory servers:
30358 - tor26 has changed IP address.
30360 o Bugfixes on 0.1.0.x, crashes/leaks:
30361 - Port the servers-not-obeying-their-exit-policies fix from
30363 - Fix an fd leak in start_daemon().
30364 - On Windows, you can't always reopen a port right after you've
30365 closed it. So change retry_listeners() to only close and re-open
30366 ports that have changed.
30367 - Fix a possible double-free in tor_gzip_uncompress().
30369 o Bugfixes on 0.1.0.x, usability:
30370 - When tor_socketpair() fails in Windows, give a reasonable
30371 Windows-style errno back.
30372 - Let people type "tor --install" as well as "tor -install" when
30374 want to make it an NT service.
30375 - NT service patch from Matt Edman to improve error messages.
30376 - When the controller asks for a config option with an abbreviated
30377 name, give the full name in our response.
30378 - Correct the man page entry on TrackHostExitsExpire.
30379 - Looks like we were never delivering deflated (i.e. compressed)
30380 running-routers lists, even when asked. Oops.
30381 - When --disable-threads is set, do not search for or link against
30382 pthreads libraries.
30384 o Bugfixes on 0.1.1.x:
30385 - Fix a seg fault with autodetecting which controller version is
30389 - New hidden service descriptor format: put a version in it, and
30390 let people specify introduction/rendezvous points that aren't
30391 in "the directory" (which is subjective anyway).
30392 - Allow the DEBUG controller event to work again. Mark certain log
30393 entries as "don't tell this to controllers", so we avoid cycles.
30396 Changes in version 0.1.0.11 - 2005-06-30
30397 o Bugfixes on 0.1.0.x:
30398 - Fix major security bug: servers were disregarding their
30399 exit policies if clients behaved unexpectedly.
30400 - Make OS X init script check for missing argument, so we don't
30401 confuse users who invoke it incorrectly.
30402 - Fix a seg fault in "tor --hash-password foo".
30403 - The MAPADDRESS control command was broken.
30406 Changes in version 0.1.1.1-alpha - 2005-06-29
30408 - Make OS X init script check for missing argument, so we don't
30409 confuse users who invoke it incorrectly.
30410 - Fix a seg fault in "tor --hash-password foo".
30411 - Fix a possible way to DoS dirservers.
30412 - When we complain that your exit policy implicitly allows local or
30413 private address spaces, name them explicitly so operators can
30415 - Make the log message less scary when all the dirservers are
30416 temporarily unreachable.
30417 - We were printing the number of idle dns workers incorrectly when
30421 - Revised controller protocol (version 1) that uses ascii rather
30422 than binary. Add supporting libraries in python and java so you
30423 can use the controller from your applications without caring how
30424 our protocol works.
30425 - Spiffy new support for crypto hardware accelerators. Can somebody
30429 Changes in version 0.0.9.10 - 2005-06-16
30430 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30431 - Refuse relay cells that claim to have a length larger than the
30432 maximum allowed. This prevents a potential attack that could read
30433 arbitrary memory (e.g. keys) from an exit server's process
30437 Changes in version 0.1.0.10 - 2005-06-14
30438 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30439 libevent before 1.1a.
30442 Changes in version 0.1.0.9-rc - 2005-06-09
30444 - Reset buf->highwater every time buf_shrink() is called, not just on
30445 a successful shrink. This was causing significant memory bloat.
30446 - Fix buffer overflow when checking hashed passwords.
30447 - Security fix: if seeding the RNG on Win32 fails, quit.
30448 - Allow seeding the RNG on Win32 even when you're not running as
30450 - Disable threading on Solaris too. Something is wonky with it,
30451 cpuworkers, and reentrant libs.
30452 - Reenable the part of the code that tries to flush as soon as an
30453 OR outbuf has a full TLS record available. Perhaps this will make
30454 OR outbufs not grow as huge except in rare cases, thus saving lots
30455 of CPU time plus memory.
30456 - Reject malformed .onion addresses rather then passing them on as
30457 normal web requests.
30458 - Adapt patch from Adam Langley: fix possible memory leak in
30459 tor_lookup_hostname().
30460 - Initialize libevent later in the startup process, so the logs are
30461 already established by the time we start logging libevent warns.
30462 - Use correct errno on win32 if libevent fails.
30463 - Check and warn about known-bad/slow libevent versions.
30464 - Pay more attention to the ClientOnly config option.
30465 - Have torctl.in/tor.sh.in check for location of su binary (needed
30467 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30468 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30469 HttpProxyAuthenticator
30470 - Stop warning about sigpipes in the logs. We're going to
30471 pretend that getting these occasionally is normal and fine.
30472 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30474 installer screens; and don't put stuff into StartupItems unless
30475 the user asks you to.
30476 - Require servers that use the default dirservers to have public IP
30477 addresses. We have too many servers that are configured with private
30478 IPs and their admins never notice the log entries complaining that
30479 their descriptors are being rejected.
30480 - Add OSX uninstall instructions. An actual uninstall script will
30484 Changes in version 0.1.0.8-rc - 2005-05-23
30486 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30487 panics. Disable kqueue on all OS X Tors.
30488 - Fix RPM: remove duplicate line accidentally added to the rpm
30490 - Disable threads on openbsd too, since its gethostaddr is not
30492 - Tolerate libevent 0.8 since it still works, even though it's
30494 - Enable building on Red Hat 9.0 again.
30495 - Allow the middle hop of the testing circuit to be running any
30496 version, now that most of them have the bugfix to let them connect
30497 to unknown servers. This will allow reachability testing to work
30498 even when 0.0.9.7-0.0.9.9 become obsolete.
30499 - Handle relay cells with rh.length too large. This prevents
30500 a potential attack that could read arbitrary memory (maybe even
30501 keys) from the exit server's process.
30502 - We screwed up the dirport reachability testing when we don't yet
30503 have a cached version of the directory. Hopefully now fixed.
30504 - Clean up router_load_single_router() (used by the controller),
30505 so it doesn't seg fault on error.
30506 - Fix a minor memory leak when somebody establishes an introduction
30507 point at your Tor server.
30508 - If a socks connection ends because read fails, don't warn that
30509 you're not sending a socks reply back.
30512 - Add HttpProxyAuthenticator config option too, that works like
30513 the HttpsProxyAuthenticator config option.
30514 - Encode hashed controller passwords in hex instead of base64,
30515 to make it easier to write controllers.
30518 Changes in version 0.1.0.7-rc - 2005-05-17
30520 - Fix a bug in the OS X package installer that prevented it from
30521 installing on Tiger.
30522 - Fix a script bug in the OS X package installer that made it
30523 complain during installation.
30524 - Find libevent even if it's hiding in /usr/local/ and your
30525 CFLAGS and LDFLAGS don't tell you to look there.
30526 - Be able to link with libevent as a shared library (the default
30527 after 1.0d), even if it's hiding in /usr/local/lib and even
30528 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30529 assuming you're running gcc. Otherwise fail and give a useful
30531 - Fix a bug in the RPM packager: set home directory for _tor to
30532 something more reasonable when first installing.
30533 - Free a minor amount of memory that is still reachable on exit.
30536 Changes in version 0.1.0.6-rc - 2005-05-14
30538 - Implement --disable-threads configure option. Disable threads on
30539 netbsd by default, because it appears to have no reentrant resolver
30541 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30542 release (1.1) detects and disables kqueue if it's broken.
30543 - Append default exit policy before checking for implicit internal
30544 addresses. Now we don't log a bunch of complaints on startup
30545 when using the default exit policy.
30546 - Some people were putting "Address " in their torrc, and they had
30547 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30548 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30549 LOCALSTATEDIR/tor instead.
30550 - Fix fragmented-message bug in TorControl.py.
30551 - Resolve a minor bug which would prevent unreachable dirports
30552 from getting suppressed in the published descriptor.
30553 - When the controller gave us a new descriptor, we weren't resolving
30554 it immediately, so Tor would think its address was 0.0.0.0 until
30555 we fetched a new directory.
30556 - Fix an uppercase/lowercase case error in suppressing a bogus
30557 libevent warning on some Linuxes.
30560 - Begin scrubbing sensitive strings from logs by default. Turn off
30561 the config option SafeLogging if you need to do debugging.
30562 - Switch to a new buffer management algorithm, which tries to avoid
30563 reallocing and copying quite as much. In first tests it looks like
30564 it uses *more* memory on average, but less cpu.
30565 - First cut at support for "create-fast" cells. Clients can use
30566 these when extending to their first hop, since the TLS already
30567 provides forward secrecy and authentication. Not enabled on
30569 - When dirservers refuse a router descriptor, we now log its
30570 contactinfo, platform, and the poster's IP address.
30571 - Call tor_free_all instead of connections_free_all after forking, to
30572 save memory on systems that need to fork.
30573 - Whine at you if you're a server and you don't set your contactinfo.
30574 - Implement --verify-config command-line option to check if your torrc
30575 is valid without actually launching Tor.
30576 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30577 rather than just rejecting it.
30580 Changes in version 0.1.0.5-rc - 2005-04-27
30582 - Stop trying to print a null pointer if an OR conn fails because
30583 we didn't like its cert.
30585 - Switch our internal buffers implementation to use a ring buffer,
30586 to hopefully improve performance for fast servers a lot.
30587 - Add HttpsProxyAuthenticator support (basic auth only), based
30588 on patch from Adam Langley.
30589 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30590 the fast servers that have been joining lately.
30591 - Give hidden service accesses extra time on the first attempt,
30592 since 60 seconds is often only barely enough. This might improve
30594 - Improve performance for dirservers: stop re-parsing the whole
30595 directory every time you regenerate it.
30596 - Add more debugging info to help us find the weird dns freebsd
30597 pthreads bug; cleaner debug messages to help track future issues.
30600 Changes in version 0.0.9.9 - 2005-04-23
30601 o Bugfixes on 0.0.9.x:
30602 - If unofficial Tor clients connect and send weird TLS certs, our
30603 Tor server triggers an assert. This release contains a minimal
30604 backport from the broader fix that we put into 0.1.0.4-rc.
30607 Changes in version 0.1.0.4-rc - 2005-04-23
30609 - If unofficial Tor clients connect and send weird TLS certs, our
30610 Tor server triggers an assert. Stop asserting, and start handling
30611 TLS errors better in other situations too.
30612 - When the controller asks us to tell it about all the debug-level
30613 logs, it turns out we were generating debug-level logs while
30614 telling it about them, which turns into a bad loop. Now keep
30615 track of whether you're sending a debug log to the controller,
30616 and don't log when you are.
30617 - Fix the "postdescriptor" feature of the controller interface: on
30618 non-complete success, only say "done" once.
30620 - Clients are now willing to load balance over up to 2mB, not 1mB,
30621 of advertised bandwidth capacity.
30622 - Add a NoPublish config option, so you can be a server (e.g. for
30623 testing running Tor servers in other Tor networks) without
30624 publishing your descriptor to the primary dirservers.
30627 Changes in version 0.1.0.3-rc - 2005-04-08
30628 o Improvements on 0.1.0.2-rc:
30629 - Client now retries when streams end early for 'hibernating' or
30630 'resource limit' reasons, rather than failing them.
30631 - More automated handling for dirserver operators:
30632 - Automatically approve nodes running 0.1.0.2-rc or later,
30633 now that the the reachability detection stuff is working.
30634 - Now we allow two unverified servers with the same nickname
30635 but different keys. But if a nickname is verified, only that
30636 nickname+key are allowed.
30637 - If you're an authdirserver connecting to an address:port,
30638 and it's not the OR you were expecting, forget about that
30639 descriptor. If he *was* the one you were expecting, then forget
30640 about all other descriptors for that address:port.
30641 - Allow servers to publish descriptors from 12 hours in the future.
30642 Corollary: only whine about clock skew from the dirserver if
30643 he's a trusted dirserver (since now even verified servers could
30644 have quite wrong clocks).
30645 - Adjust maximum skew and age for rendezvous descriptors: let skew
30646 be 48 hours rather than 90 minutes.
30647 - Efficiency improvements:
30648 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
30649 it much faster to look up a circuit for each relay cell.
30650 - Remove most calls to assert_all_pending_dns_resolves_ok(),
30651 since they're eating our cpu on exit nodes.
30652 - Stop wasting time doing a case insensitive comparison for every
30653 dns name every time we do any lookup. Canonicalize the names to
30654 lowercase and be done with it.
30655 - Start sending 'truncated' cells back rather than destroy cells,
30656 if the circuit closes in front of you. This means we won't have
30657 to abandon partially built circuits.
30658 - Only warn once per nickname from add_nickname_list_to_smartlist
30659 per failure, so an entrynode or exitnode choice that's down won't
30661 - Put a note in the torrc about abuse potential with the default
30663 - Revise control spec and implementation to allow all log messages to
30664 be sent to controller with their severities intact (suggested by
30665 Matt Edman). Update TorControl to handle new log event types.
30666 - Provide better explanation messages when controller's POSTDESCRIPTOR
30668 - Stop putting nodename in the Platform string in server descriptors.
30669 It doesn't actually help, and it is confusing/upsetting some people.
30671 o Bugfixes on 0.1.0.2-rc:
30672 - We were printing the host mask wrong in exit policies in server
30673 descriptors. This isn't a critical bug though, since we were still
30674 obeying the exit policy internally.
30675 - Fix Tor when compiled with libevent but without pthreads: move
30676 connection_unregister() from _connection_free() to
30678 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
30679 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
30680 when we look through the connection array, we'll find any of the
30681 cpu/dnsworkers. This is no good.
30683 o Bugfixes on 0.0.9.8:
30684 - Fix possible bug on threading platforms (e.g. win32) which was
30685 leaking a file descriptor whenever a cpuworker or dnsworker died.
30686 - When using preferred entry or exit nodes, ignore whether the
30687 circuit wants uptime or capacity. They asked for the nodes, they
30689 - chdir() to your datadirectory at the *end* of the daemonize process,
30690 not the beginning. This was a problem because the first time you
30691 run tor, if your datadir isn't there, and you have runasdaemon set
30692 to 1, it will try to chdir to it before it tries to create it. Oops.
30693 - Handle changed router status correctly when dirserver reloads
30694 fingerprint file. We used to be dropping all unverified descriptors
30695 right then. The bug was hidden because we would immediately
30696 fetch a directory from another dirserver, which would include the
30697 descriptors we just dropped.
30698 - When we're connecting to an OR and he's got a different nickname/key
30699 than we were expecting, only complain loudly if we're an OP or a
30700 dirserver. Complaining loudly to the OR admins just confuses them.
30701 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
30702 artificially capped at 500kB.
30705 Changes in version 0.0.9.8 - 2005-04-07
30706 o Bugfixes on 0.0.9.x:
30707 - We have a bug that I haven't found yet. Sometimes, very rarely,
30708 cpuworkers get stuck in the 'busy' state, even though the cpuworker
30709 thinks of itself as idle. This meant that no new circuits ever got
30710 established. Here's a workaround to kill any cpuworker that's been
30711 busy for more than 100 seconds.
30714 Changes in version 0.1.0.2-rc - 2005-04-01
30715 o Bugfixes on 0.1.0.1-rc:
30716 - Fixes on reachability detection:
30717 - Don't check for reachability while hibernating.
30718 - If ORPort is reachable but DirPort isn't, still publish the
30719 descriptor, but zero out DirPort until it's found reachable.
30720 - When building testing circs for ORPort testing, use only
30721 high-bandwidth nodes, so fewer circuits fail.
30722 - Complain about unreachable ORPort separately from unreachable
30723 DirPort, so the user knows what's going on.
30724 - Make sure we only conclude ORPort reachability if we didn't
30725 initiate the conn. Otherwise we could falsely conclude that
30726 we're reachable just because we connected to the guy earlier
30727 and he used that same pipe to extend to us.
30728 - Authdirservers shouldn't do ORPort reachability detection,
30729 since they're in clique mode, so it will be rare to find a
30730 server not already connected to them.
30731 - When building testing circuits, always pick middle hops running
30732 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
30733 bug. (This is a kludge; it will go away when 0.0.9.x becomes
30735 - When we decide we're reachable, actually publish our descriptor
30737 - Fix bug in redirectstream in the controller.
30738 - Fix the state descriptor strings so logs don't claim edge streams
30739 are in a different state than they actually are.
30740 - Use recent libevent features when possible (this only really affects
30741 win32 and osx right now, because the new libevent with these
30742 features hasn't been released yet). Add code to suppress spurious
30744 - Prevent possible segfault in connection_close_unattached_ap().
30745 - Fix newlines on torrc in win32.
30746 - Improve error msgs when tor-resolve fails.
30748 o Improvements on 0.0.9.x:
30749 - New experimental script tor/contrib/ExerciseServer.py (needs more
30750 work) that uses the controller interface to build circuits and
30751 fetch pages over them. This will help us bootstrap servers that
30752 have lots of capacity but haven't noticed it yet.
30753 - New experimental script tor/contrib/PathDemo.py (needs more work)
30754 that uses the controller interface to let you choose whole paths
30756 "<hostname>.<path,separated by dots>.<length of path>.path"
30757 - When we've connected to an OR and handshaked but didn't like
30758 the result, we were closing the conn without sending destroy
30759 cells back for pending circuits. Now send those destroys.
30762 Changes in version 0.0.9.7 - 2005-04-01
30763 o Bugfixes on 0.0.9.x:
30764 - Fix another race crash bug (thanks to Glenn Fink for reporting).
30765 - Compare identity to identity, not to nickname, when extending to
30766 a router not already in the directory. This was preventing us from
30767 extending to unknown routers. Oops.
30768 - Make sure to create OS X Tor user in <500 range, so we aren't
30769 creating actual system users.
30770 - Note where connection-that-hasn't-sent-end was marked, and fix
30771 a few really loud instances of this harmless bug (it's fixed more
30775 Changes in version 0.1.0.1-rc - 2005-03-28
30777 - Add reachability testing. Your Tor server will automatically try
30778 to see if its ORPort and DirPort are reachable from the outside,
30779 and it won't upload its descriptor until it decides they are.
30780 - Handle unavailable hidden services better. Handle slow or busy
30781 hidden services better.
30782 - Add support for CONNECTing through https proxies, with "HttpsProxy"
30784 - New exit policy: accept most low-numbered ports, rather than
30785 rejecting most low-numbered ports.
30786 - More Tor controller support (still experimental). See
30787 http://tor.eff.org/doc/control-spec.txt for all the new features,
30788 including signals to emulate unix signals from any platform;
30789 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
30790 closestream; closecircuit; etc.
30791 - Make nt services work and start on startup on win32 (based on
30792 patch by Matt Edman).
30793 - Add a new AddressMap config directive to rewrite incoming socks
30794 addresses. This lets you, for example, declare an implicit
30795 required exit node for certain sites.
30796 - Add a new TrackHostExits config directive to trigger addressmaps
30797 for certain incoming socks addresses -- for sites that break when
30798 your exit keeps changing (based on patch by Mike Perry).
30799 - Redo the client-side dns cache so it's just an addressmap too.
30800 - Notice when our IP changes, and reset stats/uptime/reachability.
30801 - When an application is using socks5, give him the whole variety of
30802 potential socks5 responses (connect refused, host unreachable, etc),
30803 rather than just "success" or "failure".
30804 - A more sane version numbering system. See
30805 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
30806 - New contributed script "exitlist": a simple python script to
30807 parse directories and find Tor nodes that exit to listed
30809 - New contributed script "privoxy-tor-toggle" to toggle whether
30810 Privoxy uses Tor. Seems to be configured for Debian by default.
30811 - Report HTTP reasons to client when getting a response from directory
30812 servers -- so you can actually know what went wrong.
30813 - New config option MaxAdvertisedBandwidth which lets you advertise
30814 a low bandwidthrate (to not attract as many circuits) while still
30815 allowing a higher bandwidthrate in reality.
30817 o Robustness/stability fixes:
30818 - Make Tor use Niels Provos's libevent instead of its current
30819 poll-but-sometimes-select mess. This will let us use faster async
30820 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
30822 - pthread support now too. This was forced because when we forked,
30823 we ended up wasting a lot of duplicate ram over time. Also switch
30824 to foo_r versions of some library calls to allow reentry and
30826 - Better handling for heterogeneous / unreliable nodes:
30827 - Annotate circuits w/ whether they aim to contain high uptime nodes
30828 and/or high capacity nodes. When building circuits, choose
30830 - This means that every single node in an intro rend circuit,
30831 not just the last one, will have a minimum uptime.
30832 - New config option LongLivedPorts to indicate application streams
30833 that will want high uptime circuits.
30834 - Servers reset uptime when a dir fetch entirely fails. This
30835 hopefully reflects stability of the server's network connectivity.
30836 - If somebody starts his tor server in Jan 2004 and then fixes his
30837 clock, don't make his published uptime be a year.
30838 - Reset published uptime when you wake up from hibernation.
30839 - Introduce a notion of 'internal' circs, which are chosen without
30840 regard to the exit policy of the last hop. Intro and rendezvous
30841 circs must be internal circs, to avoid leaking information. Resolve
30842 and connect streams can use internal circs if they want.
30843 - New circuit pooling algorithm: make sure to have enough circs around
30844 to satisfy any predicted ports, and also make sure to have 2 internal
30845 circs around if we've required internal circs lately (and with high
30846 uptime if we've seen that lately too).
30847 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
30848 which describes how often we retry making new circuits if current
30849 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
30850 how long we're willing to make use of an already-dirty circuit.
30851 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
30852 circ as necessary, if there are any completed ones lying around
30853 when we try to launch one.
30854 - Make hidden services try to establish a rendezvous for 30 seconds,
30855 rather than for n (where n=3) attempts to build a circuit.
30856 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
30857 "ShutdownWaitLength".
30858 - Try to be more zealous about calling connection_edge_end when
30859 things go bad with edge conns in connection.c.
30860 - Revise tor-spec to add more/better stream end reasons.
30861 - Revise all calls to connection_edge_end to avoid sending "misc",
30862 and to take errno into account where possible.
30865 - Fix a race condition that can trigger an assert, when we have a
30866 pending create cell and an OR connection fails right then.
30867 - Fix several double-mark-for-close bugs, e.g. where we were finding
30868 a conn for a cell even if that conn is already marked for close.
30869 - Make sequence of log messages when starting on win32 with no config
30870 file more reasonable.
30871 - When choosing an exit node for a new non-internal circ, don't take
30872 into account whether it'll be useful for any pending x.onion
30873 addresses -- it won't.
30874 - Turn addr_policy_compare from a tristate to a quadstate; this should
30875 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
30876 for google.com" problem.
30877 - Make "platform" string in descriptor more accurate for Win32 servers,
30878 so it's not just "unknown platform".
30879 - Fix an edge case in parsing config options (thanks weasel).
30880 If they say "--" on the commandline, it's not an option.
30881 - Reject odd-looking addresses at the client (e.g. addresses that
30882 contain a colon), rather than having the server drop them because
30884 - tor-resolve requests were ignoring .exit if there was a working circuit
30885 they could use instead.
30886 - REUSEADDR on normal platforms means you can rebind to the port
30887 right after somebody else has let it go. But REUSEADDR on win32
30888 means to let you bind to the port _even when somebody else
30889 already has it bound_! So, don't do that on Win32.
30890 - Change version parsing logic: a version is "obsolete" if it is not
30891 recommended and (1) there is a newer recommended version in the
30892 same series, or (2) there are no recommended versions in the same
30893 series, but there are some recommended versions in a newer series.
30894 A version is "new" if it is newer than any recommended version in
30896 - Stop most cases of hanging up on a socks connection without sending
30900 - Require BandwidthRate to be at least 20kB/s for servers.
30901 - When a dirserver causes you to give a warn, mention which dirserver
30903 - New config option DirAllowPrivateAddresses for authdirservers.
30904 Now by default they refuse router descriptors that have non-IP or
30905 private-IP addresses.
30906 - Stop publishing socksport in the directory, since it's not
30907 actually meant to be public. For compatibility, publish a 0 there
30909 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
30910 smart" value, that is low for servers and high for clients.
30911 - If our clock jumps forward by 100 seconds or more, assume something
30912 has gone wrong with our network and abandon all not-yet-used circs.
30913 - Warn when exit policy implicitly allows local addresses.
30914 - If we get an incredibly skewed timestamp from a dirserver mirror
30915 that isn't a verified OR, don't warn -- it's probably him that's
30917 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
30918 cookies to disk and doesn't log each web request to disk. (Thanks
30919 to Brett Carrington for pointing this out.)
30920 - When a client asks us for a dir mirror and we don't have one,
30921 launch an attempt to get a fresh one.
30922 - If we're hibernating and we get a SIGINT, exit immediately.
30923 - Add --with-dmalloc ./configure option, to track memory leaks.
30924 - And try to free all memory on closing, so we can detect what
30926 - Cache local dns resolves correctly even when they're .exit
30928 - Give a better warning when some other server advertises an
30929 ORPort that is actually an apache running ssl.
30930 - Add "opt hibernating 1" to server descriptor to make it clearer
30931 whether the server is hibernating.
30934 Changes in version 0.0.9.6 - 2005-03-24
30935 o Bugfixes on 0.0.9.x (crashes and asserts):
30936 - Add new end stream reasons to maintenance branch. Fix bug where
30937 reason (8) could trigger an assert. Prevent bug from recurring.
30938 - Apparently win32 stat wants paths to not end with a slash.
30939 - Fix assert triggers in assert_cpath_layer_ok(), where we were
30940 blowing away the circuit that conn->cpath_layer points to, then
30941 checking to see if the circ is well-formed. Backport check to make
30942 sure we dont use the cpath on a closed connection.
30943 - Prevent circuit_resume_edge_reading_helper() from trying to package
30944 inbufs for marked-for-close streams.
30945 - Don't crash on hup if your options->address has become unresolvable.
30946 - Some systems (like OS X) sometimes accept() a connection and tell
30947 you the remote host is 0.0.0.0:0. If this happens, due to some
30948 other mis-features, we get confused; so refuse the conn for now.
30950 o Bugfixes on 0.0.9.x (other):
30951 - Fix harmless but scary "Unrecognized content encoding" warn message.
30952 - Add new stream error reason: TORPROTOCOL reason means "you are not
30953 speaking a version of Tor I understand; say bye-bye to your stream."
30954 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
30955 into the future, now that we are more tolerant of skew. This
30956 resolves a bug where a Tor server would refuse to cache a directory
30957 because all the directories it gets are too far in the future;
30958 yet the Tor server never logs any complaints about clock skew.
30959 - Mac packaging magic: make man pages useable, and do not overwrite
30960 existing torrc files.
30961 - Make OS X log happily to /var/log/tor/tor.log
30964 Changes in version 0.0.9.5 - 2005-02-22
30965 o Bugfixes on 0.0.9.x:
30966 - Fix an assert race at exit nodes when resolve requests fail.
30967 - Stop picking unverified dir mirrors--it only leads to misery.
30968 - Patch from Matt Edman to make NT services work better. Service
30969 support is still not compiled into the executable by default.
30970 - Patch from Dmitri Bely so the Tor service runs better under
30971 the win32 SYSTEM account.
30972 - Make tor-resolve actually work (?) on Win32.
30973 - Fix a sign bug when getrlimit claims to have 4+ billion
30974 file descriptors available.
30975 - Stop refusing to start when bandwidthburst == bandwidthrate.
30976 - When create cells have been on the onion queue more than five
30977 seconds, just send back a destroy and take them off the list.
30980 Changes in version 0.0.9.4 - 2005-02-03
30981 o Bugfixes on 0.0.9:
30982 - Fix an assert bug that took down most of our servers: when
30983 a server claims to have 1 GB of bandwidthburst, don't
30985 - Don't crash as badly if we have spawned the max allowed number
30986 of dnsworkers, or we're out of file descriptors.
30987 - Block more file-sharing ports in the default exit policy.
30988 - MaxConn is now automatically set to the hard limit of max
30989 file descriptors we're allowed (ulimit -n), minus a few for
30991 - Give a clearer message when servers need to raise their
30992 ulimit -n when they start running out of file descriptors.
30993 - SGI Compatibility patches from Jan Schaumann.
30994 - Tolerate a corrupt cached directory better.
30995 - When a dirserver hasn't approved your server, list which one.
30996 - Go into soft hibernation after 95% of the bandwidth is used,
30997 not 99%. This is especially important for daily hibernators who
30998 have a small accounting max. Hopefully it will result in fewer
30999 cut connections when the hard hibernation starts.
31000 - Load-balance better when using servers that claim more than
31001 800kB/s of capacity.
31002 - Make NT services work (experimental, only used if compiled in).
31005 Changes in version 0.0.9.3 - 2005-01-21
31006 o Bugfixes on 0.0.9:
31007 - Backport the cpu use fixes from main branch, so busy servers won't
31008 need as much processor time.
31009 - Work better when we go offline and then come back, or when we
31010 run Tor at boot before the network is up. We do this by
31011 optimistically trying to fetch a new directory whenever an
31012 application request comes in and we think we're offline -- the
31013 human is hopefully a good measure of when the network is back.
31014 - Backport some minimal hidserv bugfixes: keep rend circuits open as
31015 long as you keep using them; actually publish hidserv descriptors
31016 shortly after they change, rather than waiting 20-40 minutes.
31017 - Enable Mac startup script by default.
31018 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
31019 - When you update AllowUnverifiedNodes or FirewallPorts via the
31020 controller's setconf feature, we were always appending, never
31022 - When you update HiddenServiceDir via setconf, it was screwing up
31023 the order of reading the lines, making it fail.
31024 - Do not rewrite a cached directory back to the cache; otherwise we
31025 will think it is recent and not fetch a newer one on startup.
31026 - Workaround for webservers that lie about Content-Encoding: Tor
31027 now tries to autodetect compressed directories and compression
31028 itself. This lets us Proxypass dir fetches through apache.
31031 Changes in version 0.0.9.2 - 2005-01-04
31032 o Bugfixes on 0.0.9 (crashes and asserts):
31033 - Fix an assert on startup when the disk is full and you're logging
31035 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
31036 style address, then we'd crash.
31037 - Fix an assert trigger when the running-routers string we get from
31038 a dirserver is broken.
31039 - Make worker threads start and run on win32. Now win32 servers
31041 - Bandaid (not actually fix, but now it doesn't crash) an assert
31042 where the dns worker dies mysteriously and the main Tor process
31043 doesn't remember anything about the address it was resolving.
31045 o Bugfixes on 0.0.9 (Win32):
31046 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
31047 name out of the warning/assert messages.
31048 - Fix a superficial "unhandled error on read" bug on win32.
31049 - The win32 installer no longer requires a click-through for our
31050 license, since our Free Software license grants rights but does not
31052 - Win32: When connecting to a dirserver fails, try another one
31053 immediately. (This was already working for non-win32 Tors.)
31054 - Stop trying to parse $HOME on win32 when hunting for default
31056 - Make tor-resolve.c work on win32 by calling network_init().
31058 o Bugfixes on 0.0.9 (other):
31059 - Make 0.0.9.x build on Solaris again.
31060 - Due to a fencepost error, we were blowing away the \n when reporting
31061 confvalue items in the controller. So asking for multiple config
31062 values at once couldn't work.
31063 - When listing circuits that are pending on an opening OR connection,
31064 if we're an OR we were listing circuits that *end* at us as
31065 being pending on every listener, dns/cpu worker, etc. Stop that.
31066 - Dirservers were failing to create 'running-routers' or 'directory'
31067 strings if we had more than some threshold of routers. Fix them so
31068 they can handle any number of routers.
31069 - Fix a superficial "Duplicate mark for close" bug.
31070 - Stop checking for clock skew for OR connections, even for servers.
31071 - Fix a fencepost error that was chopping off the last letter of any
31072 nickname that is the maximum allowed nickname length.
31073 - Update URLs in log messages so they point to the new website.
31074 - Fix a potential problem in mangling server private keys while
31075 writing to disk (not triggered yet, as far as we know).
31076 - Include the licenses for other free software we include in Tor,
31077 now that we're shipping binary distributions more regularly.
31080 Changes in version 0.0.9.1 - 2004-12-15
31081 o Bugfixes on 0.0.9:
31082 - Make hibernation actually work.
31083 - Make HashedControlPassword config option work.
31084 - When we're reporting event circuit status to a controller,
31085 don't use the stream status code.
31088 Changes in version 0.0.9 - 2004-12-12
31090 - Clean up manpage and torrc.sample file.
31091 - Clean up severities and text of log warnings.
31093 - Make servers trigger an assert when they enter hibernation.
31096 Changes in version 0.0.9rc7 - 2004-12-08
31097 o Bugfixes on 0.0.9rc:
31098 - Fix a stack-trashing crash when an exit node begins hibernating.
31099 - Avoid looking at unallocated memory while considering which
31100 ports we need to build circuits to cover.
31101 - Stop a sigpipe: when an 'end' cell races with eof from the app,
31102 we shouldn't hold-open-until-flush if the eof arrived first.
31103 - Fix a bug with init_cookie_authentication() in the controller.
31104 - When recommending new-format log lines, if the upper bound is
31105 LOG_ERR, leave it implicit.
31107 o Bugfixes on 0.0.8.1:
31108 - Fix a whole slew of memory leaks.
31109 - Fix isspace() and friends so they still make Solaris happy
31110 but also so they don't trigger asserts on win32.
31111 - Fix parse_iso_time on platforms without strptime (eg win32).
31112 - win32: tolerate extra "readable" events better.
31113 - win32: when being multithreaded, leave parent fdarray open.
31114 - Make unit tests work on win32.
31117 Changes in version 0.0.9rc6 - 2004-12-06
31118 o Bugfixes on 0.0.9pre:
31119 - Clean up some more integer underflow opportunities (not exploitable
31121 - While hibernating, hup should not regrow our listeners.
31122 - Send an end to the streams we close when we hibernate, rather
31123 than just chopping them off.
31124 - React to eof immediately on non-open edge connections.
31126 o Bugfixes on 0.0.8.1:
31127 - Calculate timeout for waiting for a connected cell from the time
31128 we sent the begin cell, not from the time the stream started. If
31129 it took a long time to establish the circuit, we would time out
31130 right after sending the begin cell.
31131 - Fix router_compare_addr_to_addr_policy: it was not treating a port
31132 of * as always matching, so we were picking reject *:* nodes as
31133 exit nodes too. Oops.
31136 - New circuit building strategy: keep a list of ports that we've
31137 used in the past 6 hours, and always try to have 2 circuits open
31138 or on the way that will handle each such port. Seed us with port
31139 80 so web users won't complain that Tor is "slow to start up".
31140 - Make kill -USR1 dump more useful stats about circuits.
31141 - When warning about retrying or giving up, print the address, so
31142 the user knows which one it's talking about.
31143 - If you haven't used a clean circuit in an hour, throw it away,
31144 just to be on the safe side. (This means after 6 hours a totally
31145 unused Tor client will have no circuits open.)
31148 Changes in version 0.0.9rc5 - 2004-12-01
31149 o Bugfixes on 0.0.8.1:
31150 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
31151 - Let resolve conns retry/expire also, rather than sticking around
31153 - If we are using select, make sure we stay within FD_SETSIZE.
31155 o Bugfixes on 0.0.9pre:
31156 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
31157 but doesn't seem to be currently; thanks to Ilja van Sprundel for
31159 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
31160 instead. Impose minima and maxima for all *Period options; impose
31161 even tighter maxima for fetching if we are a caching dirserver.
31162 Clip rather than rejecting.
31163 - Fetch cached running-routers from servers that serve it (that is,
31164 authdirservers and servers running 0.0.9rc5-cvs or later.)
31167 - Accept *:706 (silc) in default exit policy.
31168 - Implement new versioning format for post 0.1.
31169 - Support "foo.nickname.exit" addresses, to let Alice request the
31170 address "foo" as viewed by exit node "nickname". Based on a patch
31172 - Make tor --version --version dump the cvs Id of every file.
31175 Changes in version 0.0.9rc4 - 2004-11-28
31176 o Bugfixes on 0.0.8.1:
31177 - Make windows sockets actually non-blocking (oops), and handle
31178 win32 socket errors better.
31180 o Bugfixes on 0.0.9rc1:
31181 - Actually catch the -USR2 signal.
31184 Changes in version 0.0.9rc3 - 2004-11-25
31185 o Bugfixes on 0.0.8.1:
31186 - Flush the log file descriptor after we print "Tor opening log file",
31187 so we don't see those messages days later.
31189 o Bugfixes on 0.0.9rc1:
31190 - Make tor-resolve work again.
31191 - Avoid infinite loop in tor-resolve if tor hangs up on it.
31192 - Fix an assert trigger for clients/servers handling resolves.
31195 Changes in version 0.0.9rc2 - 2004-11-24
31196 o Bugfixes on 0.0.9rc1:
31197 - I broke socks5 support while fixing the eof bug.
31198 - Allow unitless bandwidths and intervals; they default to bytes
31200 - New servers don't start out hibernating; they are active until
31201 they run out of bytes, so they have a better estimate of how
31202 long it takes, and so their operators can know they're working.
31205 Changes in version 0.0.9rc1 - 2004-11-23
31206 o Bugfixes on 0.0.8.1:
31207 - Finally fix a bug that's been plaguing us for a year:
31208 With high load, circuit package window was reaching 0. Whenever
31209 we got a circuit-level sendme, we were reading a lot on each
31210 socket, but only writing out a bit. So we would eventually reach
31211 eof. This would be noticed and acted on even when there were still
31212 bytes sitting in the inbuf.
31213 - When poll() is interrupted, we shouldn't believe the revents values.
31215 o Bugfixes on 0.0.9pre6:
31216 - Fix hibernate bug that caused pre6 to be broken.
31217 - Don't keep rephist info for routers that haven't had activity for
31218 24 hours. (This matters now that clients have keys, since we track
31220 - Never call close_temp_logs while validating log options.
31221 - Fix backslash-escaping on tor.sh.in and torctl.in.
31224 - Implement weekly/monthly/daily accounting: now you specify your
31225 hibernation properties by
31226 AccountingMax N bytes|KB|MB|GB|TB
31227 AccountingStart day|week|month [day] HH:MM
31228 Defaults to "month 1 0:00".
31229 - Let bandwidth and interval config options be specified as 5 bytes,
31230 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
31231 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
31232 get back to normal.)
31233 - If your requested entry or exit node has advertised bandwidth 0,
31235 - Be more greedy about filling up relay cells -- we try reading again
31236 once we've processed the stuff we read, in case enough has arrived
31237 to fill the last cell completely.
31238 - Apply NT service patch from Osamu Fujino. Still needs more work.
31241 Changes in version 0.0.9pre6 - 2004-11-15
31242 o Bugfixes on 0.0.8.1:
31243 - Fix assert failure on malformed socks4a requests.
31244 - Use identity comparison, not nickname comparison, to choose which
31245 half of circuit-ID-space each side gets to use. This is needed
31246 because sometimes we think of a router as a nickname, and sometimes
31247 as a hex ID, and we can't predict what the other side will do.
31248 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
31249 write() call will fail and we handle it there.
31250 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
31251 and smartlist_len, which are two major profiling offenders.
31253 o Bugfixes on 0.0.9pre5:
31254 - Fix a bug in read_all that was corrupting config files on windows.
31255 - When we're raising the max number of open file descriptors to
31256 'unlimited', don't log that we just raised it to '-1'.
31257 - Include event code with events, as required by control-spec.txt.
31258 - Don't give a fingerprint when clients do --list-fingerprint:
31259 it's misleading, because it will never be the same again.
31260 - Stop using strlcpy in tor_strndup, since it was slowing us
31262 - Remove warn on startup about missing cached-directory file.
31263 - Make kill -USR1 work again.
31264 - Hibernate if we start tor during the "wait for wakeup-time" phase
31265 of an accounting interval. Log our hibernation plans better.
31266 - Authoritative dirservers now also cache their directory, so they
31267 have it on start-up.
31270 - Fetch running-routers; cache running-routers; compress
31271 running-routers; serve compressed running-routers.z
31272 - Add NSI installer script contributed by J Doe.
31273 - Commit VC6 and VC7 workspace/project files.
31274 - Commit a tor.spec for making RPM files, with help from jbash.
31275 - Add contrib/torctl.in contributed by Glenn Fink.
31276 - Implement the control-spec's SAVECONF command, to write your
31277 configuration to torrc.
31278 - Get cookie authentication for the controller closer to working.
31279 - Include control-spec.txt in the tarball.
31280 - When set_conf changes our server descriptor, upload a new copy.
31281 But don't upload it too often if there are frequent changes.
31282 - Document authentication config in man page, and document signals
31284 - Clean up confusing parts of man page and torrc.sample.
31285 - Make expand_filename handle ~ and ~username.
31286 - Use autoconf to enable largefile support where necessary. Use
31287 ftello where available, since ftell can fail at 2GB.
31288 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
31289 log more informatively.
31290 - Give a slightly more useful output for "tor -h".
31291 - Refuse application socks connections to port 0.
31292 - Check clock skew for verified servers, but allow unverified
31293 servers and clients to have any clock skew.
31294 - Break DirFetchPostPeriod into:
31295 - DirFetchPeriod for fetching full directory,
31296 - StatusFetchPeriod for fetching running-routers,
31297 - DirPostPeriod for posting server descriptor,
31298 - RendPostPeriod for posting hidden service descriptors.
31299 - Make sure the hidden service descriptors are at a random offset
31300 from each other, to hinder linkability.
31303 Changes in version 0.0.9pre5 - 2004-11-09
31304 o Bugfixes on 0.0.9pre4:
31305 - Fix a seg fault in unit tests (doesn't affect main program).
31306 - Fix an assert bug where a hidden service provider would fail if
31307 the first hop of his rendezvous circuit was down.
31308 - Hidden service operators now correctly handle version 1 style
31309 INTRODUCE1 cells (nobody generates them still, so not a critical
31311 - If do_hup fails, actually notice.
31312 - Handle more errnos from accept() without closing the listener.
31313 Some OpenBSD machines were closing their listeners because
31314 they ran out of file descriptors.
31315 - Send resolve cells to exit routers that are running a new
31316 enough version of the resolve code to work right.
31317 - Better handling of winsock includes on non-MSV win32 compilers.
31318 - Some people had wrapped their tor client/server in a script
31319 that would restart it whenever it died. This did not play well
31320 with our "shut down if your version is obsolete" code. Now people
31321 don't fetch a new directory if their local cached version is
31323 - Make our autogen.sh work on ksh as well as bash.
31326 - Hibernation: New config option "AccountingMaxKB" lets you
31327 set how many KBytes per month you want to allow your server to
31328 consume. Rather than spreading those bytes out evenly over the
31329 month, we instead hibernate for some of the month and pop up
31330 at a deterministic time, work until the bytes are consumed, then
31331 hibernate again. Config option "MonthlyAccountingStart" lets you
31332 specify which day of the month your billing cycle starts on.
31333 - Control interface: a separate program can now talk to your
31334 client/server over a socket, and get/set config options, receive
31335 notifications of circuits and streams starting/finishing/dying,
31336 bandwidth used, etc. The next step is to get some GUIs working.
31337 Let us know if you want to help out. See doc/control-spec.txt .
31338 - Ship a contrib/tor-control.py as an example script to interact
31339 with the control port.
31340 - "tor --hash-password zzyxz" will output a salted password for
31341 use in authenticating to the control interface.
31342 - New log format in config:
31343 "Log minsev[-maxsev] stdout|stderr|syslog" or
31344 "Log minsev[-maxsev] file /var/foo"
31347 - DirPolicy config option, to let people reject incoming addresses
31348 from their dirserver.
31349 - "tor --list-fingerprint" will list your identity key fingerprint
31351 - Add "pass" target for RedirectExit, to make it easier to break
31352 out of a sequence of RedirectExit rules.
31353 - Clients now generate a TLS cert too, in preparation for having
31354 them act more like real nodes.
31355 - Ship src/win32/ in the tarball, so people can use it to build.
31356 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
31358 - New "router-status" line in directory, to better bind each verified
31359 nickname to its identity key.
31360 - Deprecate unofficial config option abbreviations, and abbreviations
31361 not on the command line.
31362 - Add a pure-C tor-resolve implementation.
31363 - Use getrlimit and friends to ensure we can reach MaxConn (currently
31364 1024) file descriptors.
31366 o Code security improvements, inspired by Ilja:
31367 - Replace sprintf with snprintf. (I think they were all safe, but
31369 - Replace strcpy/strncpy with strlcpy in more places.
31370 - Avoid strcat; use snprintf or strlcat instead.
31371 - snprintf wrapper with consistent (though not C99) overflow behavior.
31374 Changes in version 0.0.9pre4 - 2004-10-17
31375 o Bugfixes on 0.0.9pre3:
31376 - If the server doesn't specify an exit policy, use the real default
31377 exit policy, not reject *:*.
31378 - Ignore fascistfirewall when uploading/downloading hidden service
31379 descriptors, since we go through Tor for those; and when using
31380 an HttpProxy, since we assume it can reach them all.
31381 - When looking for an authoritative dirserver, use only the ones
31382 configured at boot. Don't bother looking in the directory.
31383 - The rest of the fix for get_default_conf_file() on older win32.
31384 - Make 'Routerfile' config option obsolete.
31387 - New 'MyFamily nick1,...' config option for a server to
31388 specify other servers that shouldn't be used in the same circuit
31389 with it. Only believed if nick1 also specifies us.
31390 - New 'NodeFamily nick1,nick2,...' config option for a client to
31391 specify nodes that it doesn't want to use in the same circuit.
31392 - New 'Redirectexit pattern address:port' config option for a
31393 server to redirect exit connections, e.g. to a local squid.
31396 Changes in version 0.0.9pre3 - 2004-10-13
31397 o Bugfixes on 0.0.8.1:
31398 - Better torrc example lines for dirbindaddress and orbindaddress.
31399 - Improved bounds checking on parsed ints (e.g. config options and
31400 the ones we find in directories.)
31401 - Better handling of size_t vs int, so we're more robust on 64
31403 - Fix the rest of the bug where a newly started OR would appear
31404 as unverified even after we've added his fingerprint and hupped
31406 - Fix a bug from 0.0.7: when read() failed on a stream, we would
31407 close it without sending back an end. So 'connection refused'
31408 would simply be ignored and the user would get no response.
31410 o Bugfixes on 0.0.9pre2:
31411 - Serving the cached-on-disk directory to people is bad. We now
31412 provide no directory until we've fetched a fresh one.
31413 - Workaround for bug on windows where cached-directories get crlf
31415 - Make get_default_conf_file() work on older windows too.
31416 - If we write a *:* exit policy line in the descriptor, don't write
31417 any more exit policy lines.
31420 - Use only 0.0.9pre1 and later servers for resolve cells.
31421 - Make the dirservers file obsolete.
31422 - Include a dir-signing-key token in directories to tell the
31423 parsing entity which key is being used to sign.
31424 - Remove the built-in bulky default dirservers string.
31425 - New config option "Dirserver %s:%d [fingerprint]", which can be
31426 repeated as many times as needed. If no dirservers specified,
31427 default to moria1,moria2,tor26.
31428 - Make moria2 advertise a dirport of 80, so people behind firewalls
31429 will be able to get a directory.
31430 - Http proxy support
31431 - Dirservers translate requests for http://%s:%d/x to /x
31432 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31433 be routed through this host.
31434 - Clients ask for /tor/x rather than /x for new enough dirservers.
31435 This way we can one day coexist peacefully with apache.
31436 - Clients specify a "Host: %s%d" http header, to be compatible
31437 with more proxies, and so running squid on an exit node can work.
31440 Changes in version 0.0.8.1 - 2004-10-13
31442 - Fix a seg fault that can be triggered remotely for Tor
31443 clients/servers with an open dirport.
31444 - Fix a rare assert trigger, where routerinfos for entries in
31445 our cpath would expire while we're building the path.
31446 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31447 - Fix a rare seg fault for people running hidden services on
31448 intermittent connections.
31449 - Fix a bug in parsing opt keywords with objects.
31450 - Fix a stale pointer assert bug when a stream detaches and
31452 - Fix a string format vulnerability (probably not exploitable)
31453 in reporting stats locally.
31454 - Fix an assert trigger: sometimes launching circuits can fail
31455 immediately, e.g. because too many circuits have failed recently.
31456 - Fix a compile warning on 64 bit platforms.
31459 Changes in version 0.0.9pre2 - 2004-10-03
31461 - Make fetching a cached directory work for 64-bit platforms too.
31462 - Make zlib.h a required header, not an optional header.
31465 Changes in version 0.0.9pre1 - 2004-10-01
31467 - Stop using separate defaults for no-config-file and
31468 empty-config-file. Now you have to explicitly turn off SocksPort,
31469 if you don't want it open.
31470 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31471 - Improve man page to mention more of the 0.0.8 features.
31472 - Fix a rare seg fault for people running hidden services on
31473 intermittent connections.
31474 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31476 - Fix more dns related bugs: send back resolve_failed and end cells
31477 more reliably when the resolve fails, rather than closing the
31478 circuit and then trying to send the cell. Also attach dummy resolve
31479 connections to a circuit *before* calling dns_resolve(), to fix
31480 a bug where cached answers would never be sent in RESOLVED cells.
31481 - When we run out of disk space, or other log writing error, don't
31482 crash. Just stop logging to that log and continue.
31483 - We were starting to daemonize before we opened our logs, so if
31484 there were any problems opening logs, we would complain to stderr,
31485 which wouldn't work, and then mysteriously exit.
31486 - Fix a rare bug where sometimes a verified OR would connect to us
31487 before he'd uploaded his descriptor, which would cause us to
31488 assign conn->nickname as though he's unverified. Now we look through
31489 the fingerprint list to see if he's there.
31490 - Fix a rare assert trigger, where routerinfos for entries in
31491 our cpath would expire while we're building the path.
31494 - Clients can ask dirservers for /dir.z to get a compressed version
31495 of the directory. Only works for servers running 0.0.9, of course.
31496 - Make clients cache directories and use them to seed their router
31497 lists at startup. This means clients have a datadir again.
31498 - Configuration infrastructure support for warning on obsolete
31500 - Respond to content-encoding headers by trying to uncompress as
31502 - Reply with a deflated directory when a client asks for "dir.z".
31503 We could use allow-encodings instead, but allow-encodings isn't
31504 specified in HTTP 1.0.
31505 - Raise the max dns workers from 50 to 100.
31506 - Discourage people from setting their dirfetchpostperiod more often
31507 than once per minute.
31508 - Protect dirservers from overzealous descriptor uploading -- wait
31509 10 seconds after directory gets dirty, before regenerating.
31512 Changes in version 0.0.8 - 2004-08-25
31513 o Port it to SunOS 5.9 / Athena
31516 Changes in version 0.0.8rc2 - 2004-08-20
31517 o Make it compile on cygwin again.
31518 o When picking unverified routers, skip those with low uptime and/or
31519 low bandwidth, depending on what properties you care about.
31522 Changes in version 0.0.8rc1 - 2004-08-18
31523 o Changes from 0.0.7.3:
31525 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31526 don't put it into the client dns cache.
31527 - If a begin failed due to exit policy, but we believe the IP address
31528 should have been allowed, switch that router to exitpolicy reject *:*
31529 until we get our next directory.
31531 - Clients choose nodes proportional to advertised bandwidth.
31532 - Avoid using nodes with low uptime as introduction points.
31533 - Handle servers with dynamic IP addresses: don't replace
31534 options->Address with the resolved one at startup, and
31535 detect our address right before we make a routerinfo each time.
31536 - 'FascistFirewall' option to pick dirservers and ORs on specific
31537 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31538 which ports are open. (Defaults to 80,443)
31539 - Be more aggressive about trying to make circuits when the network
31540 has changed (e.g. when you unsuspend your laptop).
31541 - Check for time skew on http headers; report date in response to
31543 - If the entrynode config line has only one node, don't pick it as
31545 - Add strict{entry|exit}nodes config options. If set to 1, then
31546 we refuse to build circuits that don't include the specified entry
31548 - OutboundBindAddress config option, to bind to a specific
31549 IP address for outgoing connect()s.
31550 - End truncated log entries (e.g. directories) with "[truncated]".
31552 o Patches to 0.0.8preX:
31554 - Patches to compile and run on win32 again (maybe)?
31555 - Fix crash when looking for ~/.torrc with no $HOME set.
31556 - Fix a race bug in the unit tests.
31557 - Handle verified/unverified name collisions better when new
31558 routerinfo's arrive in a directory.
31559 - Sometimes routers were getting entered into the stats before
31560 we'd assigned their identity_digest. Oops.
31561 - Only pick and establish intro points after we've gotten a
31564 - AllowUnverifiedNodes config option to let circuits choose no-name
31565 routers in entry,middle,exit,introduction,rendezvous positions.
31566 Allow middle and rendezvous positions by default.
31567 - Add a man page for tor-resolve.
31570 Changes in version 0.0.7.3 - 2004-08-12
31571 o Stop dnsworkers from triggering an assert failure when you
31572 ask them to resolve the host "".
31575 Changes in version 0.0.8pre3 - 2004-08-09
31576 o Changes from 0.0.7.2:
31577 - Allow multiple ORs with same nickname in routerlist -- now when
31578 people give us one identity key for a nickname, then later
31579 another, we don't constantly complain until the first expires.
31580 - Remember used bandwidth (both in and out), and publish 15-minute
31581 snapshots for the past day into our descriptor.
31582 - You can now fetch $DIRURL/running-routers to get just the
31583 running-routers line, not the whole descriptor list. (But
31584 clients don't use this yet.)
31585 - When people mistakenly use Tor as an http proxy, point them
31586 at the tor-doc.html rather than the INSTALL.
31587 - Remove our mostly unused -- and broken -- hex_encode()
31588 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31589 for pointing out this bug.)
31590 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31591 fewer problems with people using the wrong key.
31592 - Change the default exit policy to reject the default edonkey,
31593 kazaa, gnutella ports.
31594 - Add replace_file() to util.[ch] to handle win32's rename().
31596 o Changes from 0.0.8preX:
31597 - Fix two bugs in saving onion keys to disk when rotating, so
31598 hopefully we'll get fewer people using old onion keys.
31599 - Fix an assert error that was making SocksPolicy not work.
31600 - Be willing to expire routers that have an open dirport -- it's
31601 just the authoritative dirservers we want to not forget.
31602 - Reject tor-resolve requests for .onion addresses early, so we
31603 don't build a whole rendezvous circuit and then fail.
31604 - When you're warning a server that he's unverified, don't cry
31605 wolf unpredictably.
31606 - Fix a race condition: don't try to extend onto a connection
31607 that's still handshaking.
31608 - For servers in clique mode, require the conn to be open before
31609 you'll choose it for your path.
31610 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31611 end relay cell, etc.
31612 - Measure bandwidth capacity over the last 24 hours, not just 12
31613 - Bugfix: authoritative dirservers were making and signing a new
31614 directory for each client, rather than reusing the cached one.
31617 Changes in version 0.0.8pre2 - 2004-08-04
31618 o Changes from 0.0.7.2:
31620 - Check directory signature _before_ you decide whether you're
31621 you're running an obsolete version and should exit.
31622 - Check directory signature _before_ you parse the running-routers
31623 list to decide who's running or verified.
31624 - Bugfixes and features:
31625 - Check return value of fclose while writing to disk, so we don't
31626 end up with broken files when servers run out of disk space.
31627 - Log a warning if the user uses an unsafe socks variant, so people
31628 are more likely to learn about privoxy or socat.
31629 - Dirservers now include RFC1123-style dates in the HTTP headers,
31630 which one day we will use to better detect clock skew.
31632 o Changes from 0.0.8pre1:
31633 - Make it compile without warnings again on win32.
31634 - Log a warning if you're running an unverified server, to let you
31635 know you might want to get it verified.
31636 - Only pick a default nickname if you plan to be a server.
31639 Changes in version 0.0.8pre1 - 2004-07-23
31641 - Made our unit tests compile again on OpenBSD 3.5, and tor
31642 itself compile again on OpenBSD on a sparc64.
31643 - We were neglecting milliseconds when logging on win32, so
31644 everything appeared to happen at the beginning of each second.
31646 o Protocol changes:
31647 - 'Extend' relay cell payloads now include the digest of the
31648 intended next hop's identity key. Now we can verify that we're
31649 extending to the right router, and also extend to routers we
31650 hadn't heard of before.
31653 - Tor nodes can now act as relays (with an advertised ORPort)
31654 without being manually verified by the dirserver operators.
31655 - Uploaded descriptors of unverified routers are now accepted
31656 by the dirservers, and included in the directory.
31657 - Verified routers are listed by nickname in the running-routers
31658 list; unverified routers are listed as "$<fingerprint>".
31659 - We now use hash-of-identity-key in most places rather than
31660 nickname or addr:port, for improved security/flexibility.
31661 - To avoid Sybil attacks, paths still use only verified servers.
31662 But now we have a chance to play around with hybrid approaches.
31663 - Nodes track bandwidth usage to estimate capacity (not used yet).
31664 - ClientOnly option for nodes that never want to become servers.
31665 - Directory caching.
31666 - "AuthoritativeDir 1" option for the official dirservers.
31667 - Now other nodes (clients and servers) will cache the latest
31668 directory they've pulled down.
31669 - They can enable their DirPort to serve it to others.
31670 - Clients will pull down a directory from any node with an open
31671 DirPort, and check the signature/timestamp correctly.
31672 - Authoritative dirservers now fetch directories from other
31673 authdirservers, to stay better synced.
31674 - Running-routers list tells who's down also, along with noting
31675 if they're verified (listed by nickname) or unverified (listed
31677 - Allow dirservers to serve running-router list separately.
31678 This isn't used yet.
31679 - ORs connect-on-demand to other ORs
31680 - If you get an extend cell to an OR you're not connected to,
31681 connect, handshake, and forward the create cell.
31682 - The authoritative dirservers stay connected to everybody,
31683 and everybody stays connected to 0.0.7 servers, but otherwise
31684 clients/servers expire unused connections after 5 minutes.
31685 - When servers get a sigint, they delay 30 seconds (refusing new
31686 connections) then exit. A second sigint causes immediate exit.
31687 - File and name management:
31688 - Look for .torrc if no CONFDIR "torrc" is found.
31689 - If no datadir is defined, then choose, make, and secure ~/.tor
31691 - If torrc not found, exitpolicy reject *:*.
31692 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
31693 - If no nickname is defined, derive default from hostname.
31694 - Rename secret key files, e.g. identity.key -> secret_id_key,
31695 to discourage people from mailing their identity key to tor-ops.
31696 - Refuse to build a circuit before the directory has arrived --
31697 it won't work anyway, since you won't know the right onion keys
31699 - Try other dirservers immediately if the one you try is down. This
31700 should tolerate down dirservers better now.
31701 - Parse tor version numbers so we can do an is-newer-than check
31702 rather than an is-in-the-list check.
31703 - New socks command 'resolve', to let us shim gethostbyname()
31705 - A 'tor_resolve' script to access the socks resolve functionality.
31706 - A new socks-extensions.txt doc file to describe our
31707 interpretation and extensions to the socks protocols.
31708 - Add a ContactInfo option, which gets published in descriptor.
31709 - Publish OR uptime in descriptor (and thus in directory) too.
31710 - Write tor version at the top of each log file
31711 - New docs in the tarball:
31713 - Document that you should proxy your SSL traffic too.
31716 Changes in version 0.0.7.2 - 2004-07-07
31717 o A better fix for the 0.0.0.0 problem, that will hopefully
31718 eliminate the remaining related assertion failures.
31721 Changes in version 0.0.7.1 - 2004-07-04
31722 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
31723 since internally we use 0.0.0.0 to signify "not yet resolved".
31726 Changes in version 0.0.7 - 2004-06-07
31727 o Updated the man page to reflect the new features.
31730 Changes in version 0.0.7rc2 - 2004-06-06
31731 o Changes from 0.0.7rc1:
31732 - Make it build on Win32 again.
31733 o Changes from 0.0.6.2:
31734 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
31738 Changes in version 0.0.7rc1 - 2004-06-02
31740 - On sighup, we were adding another log without removing the first
31741 one. So log messages would get duplicated n times for n sighups.
31742 - Several cases of using a connection after we'd freed it. The
31743 problem was that connections that are pending resolve are in both
31744 the pending_resolve tree, and also the circuit's resolving_streams
31745 list. When you want to remove one, you must remove it from both.
31746 - Fix a double-mark-for-close where an end cell arrived for a
31747 resolving stream, and then the resolve failed.
31748 - Check directory signatures based on name of signer, not on whom
31749 we got the directory from. This will let us cache directories more
31752 - Crank up some of our constants to handle more users.
31755 Changes in version 0.0.7pre1 - 2004-06-02
31756 o Fixes for crashes and other obnoxious bugs:
31757 - Fix an epipe bug: sometimes when directory connections failed
31758 to connect, we would give them a chance to flush before closing
31760 - When we detached from a circuit because of resolvefailed, we
31761 would immediately try the same circuit twice more, and then
31762 give up on the resolve thinking we'd tried three different
31764 - Limit the number of intro circuits we'll attempt to build for a
31765 hidden service per 15-minute period.
31766 - Check recommended-software string *early*, before actually parsing
31767 the directory. Thus we can detect an obsolete version and exit,
31768 even if the new directory format doesn't parse.
31769 o Fixes for security bugs:
31770 - Remember which nodes are dirservers when you startup, and if a
31771 random OR enables his dirport, don't automatically assume he's
31772 a trusted dirserver.
31774 - Directory connections were asking the wrong poll socket to
31775 start writing, and not asking themselves to start writing.
31776 - When we detached from a circuit because we sent a begin but
31777 didn't get a connected, we would use it again the first time;
31778 but after that we would correctly switch to a different one.
31779 - Stop warning when the first onion decrypt attempt fails; they
31780 will sometimes legitimately fail now that we rotate keys.
31781 - Override unaligned-access-ok check when $host_cpu is ia64 or
31782 arm. Apparently they allow it but the kernel whines.
31783 - Dirservers try to reconnect periodically too, in case connections
31785 - Fix some memory leaks in directory servers.
31786 - Allow backslash in Win32 filenames.
31787 - Made Tor build complain-free on FreeBSD, hopefully without
31788 breaking other BSD builds. We'll see.
31790 - Doxygen markup on all functions and global variables.
31791 - Make directory functions update routerlist, not replace it. So
31792 now directory disagreements are not so critical a problem.
31793 - Remove the upper limit on number of descriptors in a dirserver's
31794 directory (not that we were anywhere close).
31795 - Allow multiple logfiles at different severity ranges.
31796 - Allow *BindAddress to specify ":port" rather than setting *Port
31797 separately. Allow multiple instances of each BindAddress config
31798 option, so you can bind to multiple interfaces if you want.
31799 - Allow multiple exit policy lines, which are processed in order.
31800 Now we don't need that huge line with all the commas in it.
31801 - Enable accept/reject policies on SOCKS connections, so you can bind
31802 to 0.0.0.0 but still control who can use your OP.
31805 Changes in version 0.0.6.2 - 2004-05-16
31806 o Our integrity-checking digest was checking only the most recent cell,
31807 not the previous cells like we'd thought.
31808 Thanks to Stefan Mark for finding the flaw!
31811 Changes in version 0.0.6.1 - 2004-05-06
31812 o Fix two bugs in our AES counter-mode implementation (this affected
31813 onion-level stream encryption, but not TLS-level). It turns
31814 out we were doing something much more akin to a 16-character
31815 polyalphabetic cipher. Oops.
31816 Thanks to Stefan Mark for finding the flaw!
31817 o Retire moria3 as a directory server, and add tor26 as a directory
31821 Changes in version 0.0.6 - 2004-05-02
31822 [version bump only]
31825 Changes in version 0.0.6rc4 - 2004-05-01
31826 o Update the built-in dirservers list to use the new directory format
31827 o Fix a rare seg fault: if a node offering a hidden service attempts
31828 to build a circuit to Alice's rendezvous point and fails before it
31829 reaches the last hop, it retries with a different circuit, but
31831 o Handle windows socket errors correctly.
31834 Changes in version 0.0.6rc3 - 2004-04-28
31835 o Don't expire non-general excess circuits (if we had enough
31836 circuits open, we were expiring rendezvous circuits -- even
31837 when they had a stream attached. oops.)
31838 o Fetch randomness from /dev/urandom better (not via fopen/fread)
31839 o Better debugging for tls errors
31840 o Some versions of openssl have an SSL_pending function that erroneously
31841 returns bytes when there is a non-application record pending.
31842 o Set Content-Type on the directory and hidserv descriptor.
31843 o Remove IVs from cipher code, since AES-ctr has none.
31844 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
31845 o We were using an array of length zero in a few places.
31846 o win32's gethostbyname can't resolve an IP to an IP.
31847 o win32's close can't close a socket.
31850 Changes in version 0.0.6rc2 - 2004-04-26
31851 o Fix a bug where we were closing tls connections intermittently.
31852 It turns out openssl keeps its errors around -- so if an error
31853 happens, and you don't ask about it, and then another openssl
31854 operation happens and succeeds, and you ask if there was an error,
31855 it tells you about the first error. Fun fun.
31856 o Fix a bug that's been lurking since 27 may 03 (!)
31857 When passing back a destroy cell, we would use the wrong circ id.
31858 'Mostly harmless', but still worth fixing.
31859 o Since we don't support truncateds much, don't bother sending them;
31860 just close the circ.
31861 o check for <machine/limits.h> so we build on NetBSD again (I hope).
31862 o don't crash if a conn that sent a begin has suddenly lost its circuit
31863 (this was quite rare).
31866 Changes in version 0.0.6rc1 - 2004-04-25
31867 o We now rotate link (tls context) keys and onion keys.
31868 o CREATE cells now include oaep padding, so you can tell
31869 if you decrypted them correctly.
31870 o Add bandwidthburst to server descriptor.
31871 o Directories now say which dirserver signed them.
31872 o Use a tor_assert macro that logs failed assertions too.
31875 Changes in version 0.0.6pre5 - 2004-04-18
31876 o changes from 0.0.6pre4:
31877 - make tor build on broken freebsd 5.2 installs
31878 - fix a failed assert when you try an intro point, get a nack, and try
31879 a second one and it works.
31880 - when alice uses a port that the hidden service doesn't accept,
31881 it now sends back an end cell (denied by exit policy). otherwise
31882 alice would just have to wait to time out.
31883 - fix another rare bug: when we had tried all the intro
31884 points for a hidden service, we fetched the descriptor
31885 again, but we left our introcirc thinking it had already
31886 sent an intro, so it kept waiting for a response...
31887 - bugfix: when you sleep your hidden-service laptop, as soon
31888 as it wakes up it tries to upload a service descriptor, but
31889 socketpair fails for some reason (localhost not up yet?).
31890 now we simply give up on that upload, and we'll try again later.
31891 i'd still like to find the bug though.
31892 - if an intro circ waiting for an ack dies before getting one, then
31894 - we were reusing stale service descriptors and refetching usable
31898 Changes in version 0.0.6pre4 - 2004-04-14
31899 o changes from 0.0.6pre3:
31900 - when bob fails to connect to the rendezvous point, and his
31901 circ didn't fail because of the rendezvous point itself, then
31902 he retries a couple of times
31903 - we expire introduction and rendezvous circs more thoroughly
31904 (sometimes they were hanging around forever)
31905 - we expire unattached rendezvous streams that have been around
31906 too long (they were sticking around forever).
31907 - fix a measly fencepost error that was crashing everybody with
31911 Changes in version 0.0.6pre3 - 2004-04-14
31912 o changes from 0.0.6pre2:
31913 - make hup work again
31914 - fix some memory leaks for dirservers
31915 - allow more skew in rendezvous descriptor timestamps, to help
31916 handle people like blanu who don't know what time it is
31917 - normal circs are 3 hops, but some rend/intro circs are 4, if
31918 the initiator doesn't get to choose the last hop
31919 - send acks for introductions, so alice can know whether to try
31921 - bob publishes intro points more correctly
31922 o changes from 0.0.5:
31923 - fix an assert trigger that's been plaguing us since the days
31924 of 0.0.2prexx (thanks weasel!)
31925 - retry stream correctly when we fail to connect because of
31926 exit-policy-reject (should try another) or can't-resolve-address
31927 (also should try another, because dns on random internet servers
31929 - when we hup a dirserver and we've *removed* a server from the
31930 approved-routers list, now we remove that server from the
31931 in-memory directories too
31934 Changes in version 0.0.6pre2 - 2004-04-08
31935 o We fixed our base32 implementation. Now it works on all architectures.
31938 Changes in version 0.0.6pre1 - 2004-04-08
31940 - Hidden services and rendezvous points are implemented. Go to
31941 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
31942 hidden services. (This only works via a socks4a proxy such as
31943 Privoxy, and currently it's quite slow.)
31946 Changes in version 0.0.5 - 2004-03-30
31947 [version bump only]
31950 Changes in version 0.0.5rc3 - 2004-03-29
31951 o Install torrc as torrc.sample -- we no longer clobber your
31953 o Re-enable recommendedversion checking (we broke it in rc2, oops)
31954 o Add in a 'notice' log level for things the operator should hear
31955 but that aren't warnings
31958 Changes in version 0.0.5rc2 - 2004-03-29
31959 o Hold socks connection open until reply is flushed (if possible)
31960 o Make exit nodes resolve IPs to IPs immediately, rather than asking
31961 the dns farm to do it.
31962 o Fix c99 aliasing warnings in rephist.c
31963 o Don't include server descriptors that are older than 24 hours in the
31965 o Give socks 'reject' replies their whole 15s to attempt to flush,
31966 rather than seeing the 60s timeout and assuming the flush had failed.
31967 o Clean automake droppings from the cvs repository
31970 Changes in version 0.0.5rc1 - 2004-03-28
31971 o Fix mangled-state bug in directory fetching (was causing sigpipes).
31972 o Only build circuits after we've fetched the directory: clients were
31973 using only the directory servers before they'd fetched a directory.
31974 This also means longer startup time; so it goes.
31975 o Fix an assert trigger where an OP would fail to handshake, and we'd
31976 expect it to have a nickname.
31977 o Work around a tsocks bug: do a socks reject when AP connection dies
31978 early, else tsocks goes into an infinite loop.
31981 Changes in version 0.0.4 - 2004-03-26
31982 o When connecting to a dirserver or OR and the network is down,
31986 Changes in version 0.0.3 - 2004-03-26
31987 o Warn and fail if server chose a nickname with illegal characters
31988 o Port to Solaris and Sparc:
31989 - include missing header fcntl.h
31990 - have autoconf find -lsocket -lnsl automatically
31991 - deal with hardware word alignment
31992 - make uname() work (solaris has a different return convention)
31993 - switch from using signal() to sigaction()
31994 o Preliminary work on reputation system:
31995 - Keep statistics on success/fail of connect attempts; they're published
31996 by kill -USR1 currently.
31997 - Add a RunTesting option to try to learn link state by creating test
31998 circuits, even when SocksPort is off.
31999 - Remove unused open circuits when there are too many.
32002 Changes in version 0.0.2 - 2004-03-19
32003 - Include strlcpy and strlcat for safer string ops
32004 - define INADDR_NONE so we compile (but still not run) on solaris
32007 Changes in version 0.0.2pre27 - 2004-03-14
32009 - Allow internal tor networks (we were rejecting internal IPs,
32010 now we allow them if they're set explicitly).
32011 - And fix a few endian issues.
32014 Changes in version 0.0.2pre26 - 2004-03-14
32016 - If a stream times out after 15s without a connected cell, don't
32017 try that circuit again: try a new one.
32018 - Retry streams at most 4 times. Then give up.
32019 - When a dirserver gets a descriptor from an unknown router, it
32020 logs its fingerprint (so the dirserver operator can choose to
32021 accept it even without mail from the server operator).
32022 - Inform unapproved servers when we reject their descriptors.
32023 - Make tor build on Windows again. It works as a client, who knows
32025 - Clearer instructions in the torrc for how to set up a server.
32026 - Be more efficient about reading fd's when our global token bucket
32027 (used for rate limiting) becomes empty.
32029 - Stop asserting that computers always go forward in time. It's
32031 - When we sent a cell (e.g. destroy) and then marked an OR connection
32032 expired, we might close it before finishing a flush if the other
32033 side isn't reading right then.
32034 - Don't allow dirservers to start if they haven't defined
32035 RecommendedVersions
32036 - We were caching transient dns failures. Oops.
32037 - Prevent servers from publishing an internal IP as their address.
32038 - Address a strcat vulnerability in circuit.c
32041 Changes in version 0.0.2pre25 - 2004-03-04
32043 - Put the OR's IP in its router descriptor, not its fqdn. That way
32044 we'll stop being stalled by gethostbyname for nodes with flaky dns,
32047 - If the user typed in an address that didn't resolve, the server
32051 Changes in version 0.0.2pre24 - 2004-03-03
32053 - Fix an assertion failure in dns.c, where we were trying to dequeue
32054 a pending dns resolve even if it wasn't pending
32055 - Fix a spurious socks5 warning about still trying to write after the
32056 connection is finished.
32057 - Hold certain marked_for_close connections open until they're finished
32058 flushing, rather than losing bytes by closing them too early.
32059 - Correctly report the reason for ending a stream
32060 - Remove some duplicate calls to connection_mark_for_close
32061 - Put switch_id and start_daemon earlier in the boot sequence, so it
32062 will actually try to chdir() to options.DataDirectory
32063 - Make 'make test' exit(1) if a test fails; fix some unit tests
32064 - Make tor fail when you use a config option it doesn't know about,
32065 rather than warn and continue.
32066 - Make --version work
32067 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
32070 Changes in version 0.0.2pre23 - 2004-02-29
32072 - Print a statement when the first circ is finished, so the user
32073 knows it's working.
32074 - If a relay cell is unrecognized at the end of the circuit,
32075 send back a destroy. (So attacks to mutate cells are more
32077 - New config option 'excludenodes' to avoid certain nodes for circuits.
32078 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
32079 so you can collect coredumps there.
32081 - Fix a bug in tls flushing where sometimes data got wedged and
32082 didn't flush until more data got sent. Hopefully this bug was
32083 a big factor in the random delays we were seeing.
32084 - Make 'connected' cells include the resolved IP, so the client
32085 dns cache actually gets populated.
32086 - Disallow changing from ORPort=0 to ORPort>0 on hup.
32087 - When we time-out on a stream and detach from the circuit, send an
32088 end cell down it first.
32089 - Only warn about an unknown router (in exitnodes, entrynodes,
32090 excludenodes) after we've fetched a directory.
32093 Changes in version 0.0.2pre22 - 2004-02-26
32095 - Servers publish less revealing uname information in descriptors.
32096 - More memory tracking and assertions, to crash more usefully when
32098 - If the default torrc isn't there, just use some default defaults.
32099 Plus provide an internal dirservers file if they don't have one.
32100 - When the user tries to use Tor as an http proxy, give them an http
32101 501 failure explaining that we're a socks proxy.
32102 - Dump a new router.desc on hup, to help confused people who change
32103 their exit policies and then wonder why router.desc doesn't reflect
32105 - Clean up the generic tor.sh init script that we ship with.
32107 - If the exit stream is pending on the resolve, and a destroy arrives,
32108 then the stream wasn't getting removed from the pending list. I
32109 think this was the one causing recent server crashes.
32110 - Use a more robust poll on OSX 10.3, since their poll is flaky.
32111 - When it couldn't resolve any dirservers, it was useless from then on.
32112 Now it reloads the RouterFile (or default dirservers) if it has no
32114 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
32115 many users don't even *have* a /usr/local/sbin/.
32118 Changes in version 0.0.2pre21 - 2004-02-18
32120 - There's a ChangeLog file that actually reflects the changelog.
32121 - There's a 'torify' wrapper script, with an accompanying
32122 tor-tsocks.conf, that simplifies the process of using tsocks for
32123 tor. It even has a man page.
32124 - The tor binary gets installed to sbin rather than bin now.
32125 - Retry streams where the connected cell hasn't arrived in 15 seconds
32126 - Clean up exit policy handling -- get the default out of the torrc,
32127 so we can update it without forcing each server operator to fix
32129 - Allow imaps and pop3s in default exit policy
32131 - Prevent picking middleman nodes as the last node in the circuit
32134 Changes in version 0.0.2pre20 - 2004-01-30
32136 - We now have a deb package, and it's in debian unstable. Go to
32137 it, apt-getters. :)
32138 - I've split the TotalBandwidth option into BandwidthRate (how many
32139 bytes per second you want to allow, long-term) and
32140 BandwidthBurst (how many bytes you will allow at once before the cap
32141 kicks in). This better token bucket approach lets you, say, set
32142 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
32143 performance while not exceeding your monthly bandwidth quota.
32144 - Push out a tls record's worth of data once you've got it, rather
32145 than waiting until you've read everything waiting to be read. This
32146 may improve performance by pipelining better. We'll see.
32147 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
32148 from failed circuits (if they haven't been connected yet) and attach
32150 - Expire old streams that haven't managed to connect. Some day we'll
32151 have them reattach to new circuits instead.
32154 - Fix several memory leaks that were causing servers to become bloated
32156 - Fix a few very rare assert triggers. A few more remain.
32157 - Setuid to User _before_ complaining about running as root.
32160 Changes in version 0.0.2pre19 - 2004-01-07
32162 - Fix deadlock condition in dns farm. We were telling a child to die by
32163 closing the parent's file descriptor to him. But newer children were
32164 inheriting the open file descriptor from the parent, and since they
32165 weren't closing it, the socket never closed, so the child never read
32166 eof, so he never knew to exit. Similarly, dns workers were holding
32167 open other sockets, leading to all sorts of chaos.
32168 - New cleaner daemon() code for forking and backgrounding.
32169 - If you log to a file, it now prints an entry at the top of the
32170 logfile so you know it's working.
32171 - The onionskin challenge length was 30 bytes longer than necessary.
32172 - Started to patch up the spec so it's not quite so out of date.
32175 Changes in version 0.0.2pre18 - 2004-01-02
32177 - Fix endian issues with the 'integrity' field in the relay header.
32178 - Fix a potential bug where connections in state
32179 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
32182 Changes in version 0.0.2pre17 - 2003-12-30
32184 - Made --debuglogfile (or any second log file, actually) work.
32185 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
32186 adversary could force us into an infinite loop.
32189 - Each onionskin handshake now includes a hash of the computed key,
32190 to prove the server's identity and help perfect forward secrecy.
32191 - Changed cell size from 256 to 512 bytes (working toward compatibility
32193 - Changed cell length to 2 bytes, and moved it to the relay header.
32194 - Implemented end-to-end integrity checking for the payloads of
32196 - Separated streamid from 'recognized' (otherwise circuits will get
32197 messed up when we try to have streams exit from the middle). We
32198 use the integrity-checking to confirm that a cell is addressed to
32200 - Randomize the initial circid and streamid values, so an adversary who
32201 breaks into a node can't learn how many circuits or streams have
32205 Changes in version 0.0.2pre16 - 2003-12-14
32207 - Fixed a bug that made HUP trigger an assert
32208 - Fixed a bug where a circuit that immediately failed wasn't being
32209 counted as a failed circuit in counting retries.
32212 - Now we close the circuit when we get a truncated cell: otherwise we're
32213 open to an anonymity attack where a bad node in the path truncates
32214 the circuit and then we open streams at him.
32215 - Add port ranges to exit policies
32216 - Add a conservative default exit policy
32217 - Warn if you're running tor as root
32218 - on HUP, retry OR connections and close/rebind listeners
32219 - options.EntryNodes: try these nodes first when picking the first node
32220 - options.ExitNodes: if your best choices happen to include any of
32221 your preferred exit nodes, you choose among just those preferred
32223 - options.ExcludedNodes: nodes that are never picked in path building
32226 Changes in version 0.0.2pre15 - 2003-12-03
32227 o Robustness and bugfixes:
32228 - Sometimes clients would cache incorrect DNS resolves, which would
32229 really screw things up.
32230 - An OP that goes offline would slowly leak all its sockets and stop
32232 - A wide variety of bugfixes in exit node selection, exit policy
32233 handling, and processing pending streams when a new circuit is
32235 - Pick nodes for a path only from those the directory says are up
32236 - Choose randomly from all running dirservers, not always the first one
32237 - Increase allowed http header size for directory fetch.
32238 - Stop writing to stderr (if we're daemonized it will be closed).
32239 - Enable -g always, so cores will be more useful to me.
32240 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
32243 - Wrote a man page. It lists commonly used options.
32246 - Change default loglevel to warn.
32247 - Make PidFile default to null rather than littering in your CWD.
32248 - OnionRouter config option is now obsolete. Instead it just checks
32250 - Moved to a single unified torrc file for both clients and servers.
32253 Changes in version 0.0.2pre14 - 2003-11-29
32254 o Robustness and bugfixes:
32255 - Force the admin to make the DataDirectory himself
32256 - to get ownership/permissions right
32257 - so clients no longer make a DataDirectory and then never use it
32258 - fix bug where a client who was offline for 45 minutes would never
32259 pull down a directory again
32260 - fix (or at least hide really well) the dns assert bug that was
32261 causing server crashes
32262 - warnings and improved robustness wrt clockskew for certs
32263 - use the native daemon(3) to daemonize, when available
32264 - exit if bind() fails
32265 - exit if neither socksport nor orport is defined
32266 - include our own tor_timegm (Win32 doesn't have its own)
32267 - bugfix for win32 with lots of connections
32268 - fix minor bias in PRNG
32269 - make dirserver more robust to corrupt cached directory
32272 - Wrote the design document (woo)
32274 o Circuit building and exit policies:
32275 - Circuits no longer try to use nodes that the directory has told them
32277 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
32278 bitcounts (18.0.0.0/8).
32279 - Make AP connections standby for a circuit if no suitable circuit
32280 exists, rather than failing
32281 - Circuits choose exit node based on addr/port, exit policies, and
32282 which AP connections are standing by
32283 - Bump min pathlen from 2 to 3
32284 - Relay end cells have a payload to describe why the stream ended.
32285 - If the stream failed because of exit policy, try again with a new
32287 - Clients have a dns cache to remember resolved addresses.
32288 - Notice more quickly when we have no working circuits
32291 - APPort is now called SocksPort
32292 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
32294 - RecommendedVersions is now a config variable rather than
32295 hardcoded (for dirservers)
32296 - Reloads config on HUP
32297 - Usage info on -h or --help
32298 - If you set User and Group config vars, it'll setu/gid to them.
32301 Changes in version 0.0.2pre13 - 2003-10-19
32302 o General stability:
32303 - SSL_write no longer fails when it returns WANTWRITE and the number
32304 of bytes in the buf has changed by the next SSL_write call.
32305 - Fix segfault fetching directory when network is down
32306 - Fix a variety of minor memory leaks
32307 - Dirservers reload the fingerprints file on HUP, so I don't have
32308 to take down the network when I approve a new router
32309 - Default server config file has explicit Address line to specify fqdn
32312 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
32313 - Make listener connections not ever alloc bufs
32315 o Autoconf improvements:
32316 - don't clobber an external CFLAGS in ./configure
32317 - Make install now works
32318 - create var/lib/tor on make install
32319 - autocreate a tor.sh initscript to help distribs
32320 - autocreate the torrc and sample-server-torrc with correct paths
32322 o Log files and Daemonizing now work:
32323 - If --DebugLogFile is specified, log to it at -l debug
32324 - If --LogFile is specified, use it instead of commandline
32325 - If --RunAsDaemon is set, tor forks and backgrounds on startup