1 Changes in version 0.4.1.5 - 2019-08-20
2 This is the first stable release in the 0.4.1.x series. This series
3 adds experimental circuit-level padding, authenticated SENDME cells to
4 defend against certain attacks, and several performance improvements
5 to save on CPU consumption. It fixes bugs in bootstrapping and v3
6 onion services. It also includes numerous smaller features and
7 bugfixes on earlier versions.
9 Per our support policy, we will support the 0.4.1.x series for nine
10 months, or until three months after the release of a stable 0.4.2.x:
11 whichever is longer. If you need longer-term support, please stick
12 with 0.3.5.x, which will we plan to support until Feb 2022.
14 Below are the changes since 0.4.1.4-rc. For a complete list of changes
15 since 0.4.0.5, see the ReleaseNotes file.
17 o Directory authority changes:
18 - The directory authority "dizum" has a new IP address. Closes
21 o Minor features (circuit padding logging):
22 - Demote noisy client-side warn logs about circuit padding to
23 protocol warnings. Add additional log messages and circuit ID
24 fields to help with bug 30992 and any other future issues.
26 o Minor bugfixes (circuit padding negotiation):
27 - Bump the circuit padding protocol version to explicitly signify
28 that the HS setup machine support is finalized in 0.4.1.x-stable.
29 This also means that 0.4.1.x-alpha clients will not negotiate
30 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
31 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
32 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
34 o Minor bugfixes (circuit padding):
35 - Ignore non-padding cells on padding circuits. This addresses
36 various warning messages from subsystems that were not expecting
37 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
39 o Minor bugfixes (clock skew detection):
40 - Don't believe clock skew results from NETINFO cells that appear to
41 arrive before we sent the VERSIONS cells they are responding to.
42 Previously, we would accept them up to 3 minutes "in the past".
43 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
45 o Minor bugfixes (compatibility, standards compliance):
46 - Fix a bug that would invoke undefined behavior on certain
47 operating systems when trying to asprintf() a string exactly
48 INT_MAX bytes long. We don't believe this is exploitable, but it's
49 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
50 Found and fixed by Tobias Stoeckmann.
52 o Minor bugfixes (compilation warning):
53 - Fix a compilation warning on Windows about casting a function
54 pointer for GetTickCount64(). Fixes bug 31374; bugfix
57 o Minor bugfixes (compilation):
58 - Avoid using labs() on time_t, which can cause compilation warnings
59 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
61 o Minor bugfixes (distribution):
62 - Do not ship any temporary files found in the
63 scripts/maint/practracker directory. Fixes bug 31311; bugfix
66 o Testing (continuous integration):
67 - In Travis, make stem log a controller trace to the console, and
68 tail stem's tor log after failure. Closes ticket 30591.
69 - In Travis, only run the stem tests that use a tor binary. Closes
73 Changes in version 0.4.1.4-rc - 2019-07-25
74 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
75 updates to a new list of fallback directories. If no new bugs are
76 found, the next release in the 0.4.1.x serious should be stable.
78 o Major bugfixes (circuit build, guard):
79 - When considering upgrading circuits from "waiting for guard" to
80 "open", always ignore circuits that are marked for close. Otherwise,
81 we can end up in the situation where a subsystem is notified that
82 a closing circuit has just opened, leading to undesirable
83 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
85 o Minor features (continuous integration):
86 - Our Travis configuration now uses Chutney to run some network
87 integration tests automatically. Closes ticket 29280.
89 o Minor features (fallback directory list):
90 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
91 in December 2018 (of which ~122 were still functional), with a
92 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
93 in June 2019. Closes ticket 28795.
95 o Minor bugfixes (circuit padding):
96 - On relays, properly check that a padding machine is absent before
97 logging a warning about it being absent. Fixes bug 30649; bugfix
99 - Add two NULL checks in unreachable places to silence Coverity (CID
100 144729 and 1447291) and better future-proof ourselves. Fixes bug
101 31024; bugfix on 0.4.1.1-alpha.
103 o Minor bugfixes (crash on exit):
104 - Avoid a set of possible code paths that could try to use freed
105 memory in routerlist_free() while Tor was exiting. Fixes bug
106 31003; bugfix on 0.1.2.2-alpha.
108 o Minor bugfixes (logging):
109 - Fix a conflict between the flag used for messaging-domain log
110 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
113 o Minor bugfixes (memory leaks):
114 - Fix a trivial memory leak when parsing an invalid value from a
115 download schedule in the configuration. Fixes bug 30894; bugfix
118 o Code simplification and refactoring:
119 - Remove some dead code from circpad_machine_remove_token() to fix
120 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
124 Changes in version 0.4.1.3-alpha - 2019-06-25
125 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
126 alpha, most of them from earlier release series.
128 o Major bugfixes (Onion service reachability):
129 - Properly clean up the introduction point map when circuits change
130 purpose from onion service circuits to pathbias, measurement, or
131 other circuit types. This should fix some service-side instances
132 of introduction point failure. Fixes bug 29034; bugfix
135 o Minor features (geoip):
136 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
137 Country database. Closes ticket 30852.
139 o Minor features (logging):
140 - Give a more useful assertion failure message if we think we have
141 minherit() but we fail to make a region non-inheritable. Give a
142 compile-time warning if our support for minherit() is incomplete.
145 o Minor bugfixes (circuit isolation):
146 - Fix a logic error that prevented the SessionGroup sub-option from
147 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
149 o Minor bugfixes (continuous integration):
150 - Allow the test-stem job to fail in Travis, because it sometimes
151 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
152 - Skip test_rebind on macOS in Travis, because it is unreliable on
153 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
154 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
155 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
157 o Minor bugfixes (directory authorities):
158 - Stop crashing after parsing an unknown descriptor purpose
159 annotation. We think this bug can only be triggered by modifying a
160 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
162 o Minor bugfixes (pluggable transports):
163 - When running as a bridge with pluggable transports, always publish
164 pluggable transport information in our extrainfo descriptor, even
165 if ExtraInfoStatistics is 0. This information is needed by
166 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
169 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
173 Changes in version 0.4.1.2-alpha - 2019-06-06
174 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
175 previous alpha, and some much older. It also contains minor testing
176 improvements, and an improvement to the security of our authenticated
177 SENDME implementation.
179 o Major bugfixes (bridges):
180 - Consider our directory information to have changed when our list
181 of bridges changes. Previously, Tor would not re-compute the
182 status of its directory information when bridges changed, and
183 therefore would not realize that it was no longer able to build
184 circuits. Fixes part of bug 29875.
185 - Do not count previously configured working bridges towards our
186 total of working bridges. Previously, when Tor's list of bridges
187 changed, it would think that the old bridges were still usable,
188 and delay fetching router descriptors for the new ones. Fixes part
189 of bug 29875; bugfix on 0.3.0.1-alpha.
191 o Major bugfixes (flow control, SENDME):
192 - Decrement the stream-level package window after packaging a cell.
193 Previously, it was done inside a log_debug() call, meaning that if
194 debug logs were not enabled, the decrement would never happen, and
195 thus the window would be out of sync with the other end point.
196 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
198 o Major bugfixes (onion service reachability):
199 - Properly clean up the introduction point map and associated state
200 when circuits change purpose from onion service circuits to
201 pathbias, measurement, or other circuit types. This may fix some
202 instances of introduction point failure. Fixes bug 29034; bugfix
205 o Minor features (authenticated SENDME):
206 - Ensure that there is enough randomness on every circuit to prevent
207 an attacker from successfully predicting the hashes they will need
208 to include in authenticated SENDME cells. At a random interval, if
209 we have not sent randomness already, we now leave some extra space
210 at the end of a cell that we can fill with random bytes. Closes
213 o Minor features (continuous integration):
214 - When running coverage builds on Travis, we now set
215 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
218 o Minor features (maintenance):
219 - Add a new "make autostyle" target that developers can use to apply
220 all automatic Tor style and consistency conversions to the
221 codebase. Closes ticket 30539.
223 o Minor features (testing):
224 - The circuitpadding tests now use a reproducible RNG implementation,
225 so that if a test fails, we can learn why. Part of ticket 28878.
226 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
227 to set the RNG seed for tests that use a reproducible RNG. Part of
229 - When running tests in coverage mode, take additional care to make
230 our coverage deterministic, so that we can accurately track
231 changes in code coverage. Closes ticket 30519.
233 o Minor bugfixes (configuration, proxies):
234 - Fix a bug that prevented us from supporting SOCKS5 proxies that
235 want authentication along with configured (but unused!)
236 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
238 o Minor bugfixes (controller):
239 - POSTDESCRIPTOR requests should work again. Previously, they were
240 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
242 - Repair the HSFETCH command so that it works again. Previously, it
243 expected a body when it shouldn't have. Fixes bug 30646; bugfix
246 o Minor bugfixes (developer tooling):
247 - Fix pre-push hook to allow fixup and squash commits when pushing
248 to non-upstream git remote. Fixes bug 30286; bugfix
251 o Minor bugfixes (directory authority):
252 - Move the "bandwidth-file-headers" line in directory authority
253 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
256 o Minor bugfixes (NetBSD):
257 - Fix usage of minherit() on NetBSD and other platforms that define
258 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
259 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
261 o Minor bugfixes (out-of-memory handler):
262 - When purging the DNS cache because of an out-of-memory condition,
263 try purging just the older entries at first. Previously, we would
264 always purge the whole thing. Fixes bug 29617; bugfix
267 o Minor bugfixes (portability):
268 - Avoid crashing in our tor_vasprintf() implementation on systems
269 that define neither vasprintf() nor _vscprintf(). (This bug has
270 been here long enough that we question whether people are running
271 Tor on such systems, but we're applying the fix out of caution.)
272 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
275 o Minor bugfixes (shutdown, libevent, memory safety):
276 - Avoid use-after-free bugs when shutting down, by making sure that
277 we shut down libevent only after shutting down all of its users.
278 We believe these are harmless in practice, since they only occur
279 on the shutdown path, and do not involve any attacker-controlled
280 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
282 o Minor bugfixes (static analysis):
283 - Fix several spurious Coverity warnings about the unit tests, to
284 lower our chances of missing real warnings in the future. Fixes
285 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
288 - Specify torrc paths (with empty files) when launching tor in
289 integration tests; refrain from reading user and system torrcs.
290 Resolves issue 29702.
293 Changes in version 0.4.1.1-alpha - 2019-05-22
294 This is the first alpha in the 0.4.1.x series. It introduces
295 lightweight circuit padding to make some onion-service circuits harder
296 to distinguish, includes a new "authenticated SENDME" feature to make
297 certain denial-of-service attacks more difficult, and improves
298 performance in several areas.
300 o Major features (circuit padding):
301 - Onion service clients now add padding cells at the start of their
302 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
303 look more like general purpose Exit traffic. The overhead for this
304 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
305 extra upstream cell and 10 downstream cells for INTRODUCE
306 circuits. This feature is only enabled when also supported by the
307 circuit's middle node. (Clients may specify fixed middle nodes
308 with the MiddleNodes option, and may force-disable this feature
309 with the CircuitPadding torrc.) Closes ticket 28634.
311 o Major features (code organization):
312 - Tor now includes a generic publish-subscribe message-passing
313 subsystem that we can use to organize intermodule dependencies. We
314 hope to use this to reduce dependencies between modules that don't
315 need to be related, and to generally simplify our codebase. Closes
318 o Major features (controller protocol):
319 - Controller commands are now parsed using a generalized parsing
320 subsystem. Previously, each controller command was responsible for
321 parsing its own input, which led to strange inconsistencies.
324 o Major features (flow control):
325 - Implement authenticated SENDMEs as detailed in proposal 289. A
326 SENDME cell now includes the digest of the traffic that it
327 acknowledges, so that once an end point receives the SENDME, it
328 can confirm the other side's knowledge of the previous cells that
329 were sent, and prevent certain types of denial-of-service attacks.
330 This behavior is controlled by two new consensus parameters: see
331 the proposal for more details. Fixes ticket 26288.
333 o Major features (performance):
334 - Our node selection algorithm now excludes nodes in linear time.
335 Previously, the algorithm was quadratic, which could slow down
336 heavily used onion services. Closes ticket 30307.
338 o Major features (performance, RNG):
339 - Tor now constructs a fast secure pseudorandom number generator for
340 each thread, to use when performance is critical. This PRNG is
341 based on AES-CTR, using a buffering construction similar to
342 libottery and the (newer) OpenBSD arc4random() code. It
343 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
344 small outputs. Although we believe it to be cryptographically
345 strong, we are only using it when necessary for performance.
346 Implements tickets 29023 and 29536.
348 o Major bugfixes (onion service v3):
349 - Fix an unreachable bug in which an introduction point could try to
350 send an INTRODUCE_ACK with a status code that Trunnel would refuse
351 to encode, leading the relay to assert(). We've consolidated the
352 ABI values into Trunnel now. Fixes bug 30454; bugfix
354 - Clients can now handle unknown status codes from INTRODUCE_ACK
355 cells. (The NACK behavior will stay the same.) This will allow us
356 to extend status codes in the future without breaking the normal
357 client behavior. Fixes another part of bug 30454; bugfix
360 o Minor features (circuit padding):
361 - We now use a fast PRNG when scheduling circuit padding. Part of
363 - Allow the padding machine designer to pick the edges of their
364 histogram instead of trying to compute them automatically using an
365 exponential formula. Resolves some undefined behavior in the case
366 of small histograms and allows greater flexibility on machine
367 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
368 - Allow circuit padding machines to hold a circuit open until they
369 are done padding it. Closes ticket 28780.
371 o Minor features (compile-time modules):
372 - Add a "--list-modules" command to print a list of which compile-
373 time modules are enabled. Closes ticket 30452.
375 o Minor features (continuous integration):
376 - Remove sudo configuration lines from .travis.yml as they are no
377 longer needed with current Travis build environment. Resolves
379 - In Travis, show stem's tor log after failure. Closes ticket 30234.
381 o Minor features (controller):
382 - Add onion service version 3 support to the HSFETCH command.
383 Previously, only version 2 onion services were supported. Closes
384 ticket 25417. Patch by Neel Chauhan.
386 o Minor features (debugging):
387 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
388 logging of additional information during assert failure. Now we
389 can use format strings to include information for trouble
390 shooting. Resolves ticket 29662.
392 o Minor features (defense in depth):
393 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
394 case a bug causes them to be used later. Closes ticket 30176.
395 Patch from Tobias Stoeckmann.
396 - Tor now uses a cryptographically strong PRNG even for decisions
397 that we do not believe are security-sensitive. Previously, for
398 performance reasons, we had used a trivially predictable linear
399 congruential generator algorithm for certain load-balancing and
400 statistical sampling decisions. Now we use our fast RNG in those
401 cases. Closes ticket 29542.
403 o Minor features (developer tools):
404 - Tor's "practracker" test script now checks for files and functions
405 that seem too long and complicated. Existing overlong functions
406 and files are accepted for now, but should eventually be
407 refactored. Closes ticket 29221.
408 - Add some scripts used for git maintenance to scripts/git. Closes
410 - Call practracker from pre-push and pre-commit git hooks to let
411 developers know if they made any code style violations. Closes
413 - Add a script to check that each header has a well-formed and
414 unique guard macro. Closes ticket 29756.
416 o Minor features (geoip):
417 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
418 Country database. Closes ticket 30522.
420 o Minor features (HTTP tunnel):
421 - Return an informative web page when the HTTPTunnelPort is used as
422 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
424 o Minor features (IPv6, v3 onion services):
425 - Make v3 onion services put IPv6 addresses in service descriptors.
426 Before this change, service descriptors only contained IPv4
427 addresses. Implements 26992.
429 o Minor features (modularity):
430 - The "--disable-module-dirauth" compile-time option now disables
431 even more dirauth-only code. Closes ticket 30345.
433 o Minor features (performance):
434 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
435 1.1.1 and later), since they tend to be faster than tiny-keccak.
438 o Minor features (testing):
439 - Tor's unit test code now contains helper functions to replace the
440 PRNG with a deterministic or reproducible version for testing.
441 Previously, various tests implemented this in various ways.
442 Implements ticket 29732.
443 - We now have a script, cov-test-determinism.sh, to identify places
444 where our unit test coverage has become nondeterministic. Closes
446 - Check that representative subsets of values of `int` and `unsigned
447 int` can be represented by `void *`. Resolves issue 29537.
449 o Minor bugfixes (bridge authority):
450 - Bridge authorities now set bridges as running or non-running when
451 about to dump their status to a file. Previously, they set bridges
452 as running in response to a GETINFO command, but those shouldn't
453 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
454 Patch by Neel Chauhan.
456 o Minor bugfixes (channel padding statistics):
457 - Channel padding write totals and padding-enabled totals are now
458 counted properly in relay extrainfo descriptors. Fixes bug 29231;
459 bugfix on 0.3.1.1-alpha.
461 o Minor bugfixes (circuit padding):
462 - Add a "CircuitPadding" torrc option to disable circuit padding.
463 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
464 - Allow circuit padding machines to specify that they do not
465 contribute much overhead, and provide consensus flags and torrc
466 options to force clients to only use these low overhead machines.
467 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
468 - Provide a consensus parameter to fully disable circuit padding, to
469 be used in emergency network overload situations. Fixes bug 30173;
470 bugfix on 0.4.0.1-alpha.
471 - The circuit padding subsystem will no longer schedule padding if
472 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
473 - Inspect a circuit-level cell queue before sending padding, to
474 avoid sending padding while too much data is already queued. Fixes
475 bug 29204; bugfix on 0.4.0.1-alpha.
476 - Avoid calling monotime_absolute_usec() in circuit padding machines
477 that do not use token removal or circuit RTT estimation. Fixes bug
478 29085; bugfix on 0.4.0.1-alpha.
480 o Minor bugfixes (compilation, unusual configurations):
481 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
482 due to missing declarations of abort(), and prevent other such
483 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
485 o Minor bugfixes (controller protocol):
486 - Teach the controller parser to distinguish an object preceded by
487 an argument list from one without. Previously, it couldn't
488 distinguish an argument list from the first line of a multiline
489 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
491 o Minor bugfixes (directory authority, ipv6):
492 - Directory authorities with IPv6 support now always mark themselves
493 as reachable via IPv6. Fixes bug 24338; bugfix on 0.4.0.2-alpha.
494 Patch by Neel Chauhan.
496 o Minor bugfixes (documentation):
497 - Improve the documentation for using MapAddress with ".exit". Fixes
498 bug 30109; bugfix on 0.1.0.1-rc.
499 - Improve the monotonic time module and function documentation to
500 explain what "monotonic" actually means, and document some results
501 that have surprised people. Fixes bug 29640; bugfix
503 - Use proper formatting when providing an example on quoting options
504 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
506 o Minor bugfixes (logging):
507 - Do not log a warning when running with an OpenSSL version other
508 than the one Tor was compiled with, if the two versions should be
509 compatible. Previously, we would warn whenever the version was
510 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
511 - Warn operators when the MyFamily option is set but ContactInfo is
512 missing, as the latter should be set too. Fixes bug 25110; bugfix
515 o Minor bugfixes (memory leak):
516 - Avoid a minor memory leak that could occur on relays when failing
517 to create a "keys" directory. Fixes bug 30148; bugfix
520 o Minor bugfixes (onion services):
521 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
522 implemenation) when failing to load an onion service client
523 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
524 - When refusing to launch a controller's HSFETCH request because of
525 rate-limiting, respond to the controller with a new response,
526 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
527 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
529 - When relaunching a circuit to a rendezvous service, mark the
530 circuit as needing high-uptime routers as appropriate. Fixes bug
531 17357; bugfix on 0.4.0.2-alpha. Patch by Neel Chauhan.
532 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
533 (IPv6 support for v3 onion services is still incomplete: see
534 ticket 23493 for details.) Fixes bug 23588; bugfix on
535 0.3.2.1-alpha. Patch by Neel Chauhan.
537 o Minor bugfixes (onion services, performance):
538 - When building circuits to onion services, call tor_addr_parse()
539 less often. Previously, we called tor_addr_parse() in
540 circuit_is_acceptable() even if its output wasn't used. This
541 change should improve performance when building circuits. Fixes
542 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
544 o Minor bugfixes (performance):
545 - When checking whether a node is a bridge, use a fast check to make
546 sure that its identity is set. Previously, we used a constant-time
547 check, which is not necessary in this case. Fixes bug 30308;
548 bugfix on 0.3.5.1-alpha.
550 o Minor bugfixes (pluggable transports):
551 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
552 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
554 o Minor bugfixes (probability distributions):
555 - Refactor and improve parts of the probability distribution code
556 that made Coverity complain. Fixes bug 29805; bugfix
559 o Minor bugfixes (python):
560 - Stop assuming that /usr/bin/python3 exists. For scripts that work
561 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
562 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
564 o Minor bugfixes (relay):
565 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
566 is auto, act as if ExitRelay is 1. Previously, we would ignore
567 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
568 0.3.5.1-alpha. Patch by Neel Chauhan.
570 o Minor bugfixes (stats):
571 - When ExtraInfoStatistics is 0, stop including bandwidth usage
572 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
573 bridge statistics by country in extra-info documents. Fixes bug
574 29018; bugfix on 0.2.4.1-alpha.
576 o Minor bugfixes (testing):
577 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
578 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
579 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
580 - Fix some incorrect code in the v3 onion service unit tests. Fixes
581 bug 29243; bugfix on 0.3.2.1-alpha.
582 - In the "routerkeys/*" tests, check the return values of mkdir()
583 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
584 Found by Coverity as CID 1444254.
585 - Split test_utils_general() into several smaller test functions.
586 This makes it easier to perform resource deallocation on assert
587 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
588 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
590 o Minor bugfixes (tor-resolve):
591 - Fix a memory leak in tor-resolve that could happen if Tor gave it
592 a malformed SOCKS response. (Memory leaks in tor-resolve don't
593 actually matter, but it's good to fix them anyway.) Fixes bug
594 30151; bugfix on 0.4.0.1-alpha.
596 o Code simplification and refactoring:
597 - Abstract out the low-level formatting of replies on the control
598 port. Implements ticket 30007.
599 - Add several assertions in an attempt to fix some Coverity
600 warnings. Closes ticket 30149.
601 - Introduce a connection_dir_buf_add() helper function that checks
602 for compress_state of dir_connection_t and automatically writes a
603 string to directory connection with or without compression.
604 Resolves issue 28816.
605 - Make the base32_decode() API return the number of bytes written,
606 for consistency with base64_decode(). Closes ticket 28913.
607 - Move most relay-only periodic events out of mainloop.c into the
608 relay subsystem. Closes ticket 30414.
609 - Refactor and encapsulate parts of the codebase that manipulate
610 crypt_path_t objects. Resolves issue 30236.
611 - Refactor several places in our code that Coverity incorrectly
612 believed might have memory leaks. Closes ticket 30147.
613 - Remove redundant return values in crypto_format, and the
614 associated return value checks elsewhere in the code. Make the
615 implementations in crypto_format consistent, and remove redundant
616 code. Resolves ticket 29660.
617 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
618 it is not a constant-time function. Closes ticket 30309.
619 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
620 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
621 bugfix on 0.3.2.1-alpha.
622 - Simplify v3 onion service link specifier handling code. Fixes bug
623 23576; bugfix on 0.3.2.1-alpha.
624 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
625 code. Resolves ticket 29108.
626 - Split control.c into several submodules, in preparation for
627 distributing its current responsibilities throughout the codebase.
629 - Start to move responsibility for knowing about periodic events to
630 the appropriate subsystems, so that the mainloop doesn't need to
631 know all the periodic events in the rest of the codebase.
632 Implements tickets 30293 and 30294.
635 - Document how to find git commits and tags for bug fixes in
636 CodingStandards.md. Update some file documentation. Closes
640 - Remove the linux-tor-prio.sh script from contrib/operator-tools
641 directory. Resolves issue 29434.
642 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
643 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
646 o Code simplification and refactoring (shell scripts):
647 - Clean up many of our shell scripts to fix shellcheck warnings.
648 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
649 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
650 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
651 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
652 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
653 nagios-check-tor-authority-cert (ticket 29071),
654 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
655 (ticket 29060), test_key_expiration.sh (ticket 30002),
656 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
660 - In "make test-network-all", test IPv6-only v3 single onion
661 services, using the chutney network single-onion-v23-ipv6-md.
665 Changes in version 0.4.0.5 - 2019-05-02
666 This is the first stable release in the 0.4.0.x series. It contains
667 improvements for power management and bootstrap reporting, as well as
668 preliminary backend support for circuit padding to prevent some kinds
669 of traffic analysis. It also continues our work in refactoring Tor for
670 long-term maintainability.
672 Per our support policy, we will support the 0.4.0.x series for nine
673 months, or until three months after the release of a stable 0.4.1.x:
674 whichever is longer. If you need longer-term support, please stick
675 with 0.3.5.x, which will we plan to support until Feb 2022.
677 Below are the changes since 0.4.0.4-rc. For a complete list of changes
678 since 0.3.5.7, see the ReleaseNotes file.
680 o Minor features (continuous integration):
681 - In Travis, tell timelimit to use stem's backtrace signals, and
682 launch python directly from timelimit, so python receives the
683 signals from timelimit, rather than make. Closes ticket 30117.
685 o Minor features (diagnostic):
686 - Add more diagnostic log messages in an attempt to solve the issue
687 of NUL bytes appearing in a microdescriptor cache. Related to
690 o Minor features (testing):
691 - Use the approx_time() function when setting the "Expires" header
692 in directory replies, to make them more testable. Needed for
695 o Minor bugfixes (rust):
696 - Abort on panic in all build profiles, instead of potentially
697 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
699 o Minor bugfixes (shellcheck):
700 - Look for scripts in their correct locations during "make
701 shellcheck". Previously we had looked in the wrong place during
702 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
704 o Minor bugfixes (testing):
705 - Check the time in the "Expires" header using approx_time(). Fixes
706 bug 30001; bugfix on 0.4.0.4-rc.
708 o Minor bugfixes (UI):
709 - Lower log level of unlink() errors during bootstrap. Fixes bug
710 29930; bugfix on 0.4.0.1-alpha.
713 Changes in version 0.4.0.4-rc - 2019-04-11
714 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
715 several bugs from earlier versions, including some that had affected
716 stability, and one that prevented relays from working with NSS.
718 o Major bugfixes (NSS, relay):
719 - When running with NSS, disable TLS 1.2 ciphersuites that use
720 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
721 these ciphersuites don't work -- which caused relays to fail to
722 handshake with one another when these ciphersuites were enabled.
723 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
725 o Minor features (bandwidth authority):
726 - Make bandwidth authorities ignore relays that are reported in the
727 bandwidth file with the flag "vote=0". This change allows us to
728 report unmeasured relays for diagnostic reasons without including
729 their bandwidth in the bandwidth authorities' vote. Closes
731 - When a directory authority is using a bandwidth file to obtain the
732 bandwidth values that will be included in the next vote, serve
733 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
736 o Minor features (circuit padding):
737 - Stop warning about undefined behavior in the probability
738 distribution tests. Float division by zero may technically be
739 undefined behavior in C, but it's well defined in IEEE 754.
740 Partial backport of 29298. Closes ticket 29527; bugfix
743 o Minor features (continuous integration):
744 - On Travis Rust builds, cleanup Rust registry and refrain from
745 caching the "target/" directory to speed up builds. Resolves
748 o Minor features (dormant mode):
749 - Add a DormantCanceledByStartup option to tell Tor that it should
750 treat a startup event as cancelling any previous dormant state.
751 Integrators should use this option with caution: it should only be
752 used if Tor is being started because of something that the user
753 did, and not if Tor is being automatically started in the
754 background. Closes ticket 29357.
756 o Minor features (geoip):
757 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
758 Country database. Closes ticket 29992.
760 o Minor features (NSS, diagnostic):
761 - Try to log an error from NSS (if there is any) and a more useful
762 description of our situation if we are using NSS and a call to
763 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
765 o Minor bugfixes (security):
766 - Fix a potential double free bug when reading huge bandwidth files.
767 The issue is not exploitable in the current Tor network because
768 the vulnerable code is only reached when directory authorities
769 read bandwidth files, but bandwidth files come from a trusted
770 source (usually the authorities themselves). Furthermore, the
771 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
772 which are not used by any of the current authorities. Fixes bug
773 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
775 - Verify in more places that we are not about to create a buffer
776 with more than INT_MAX bytes, to avoid possible OOB access in the
777 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
778 fixed by Tobias Stoeckmann.
780 o Minor bugfix (continuous integration):
781 - Reset coverage state on disk after Travis CI has finished. This
782 should prevent future coverage merge errors from causing the test
783 suite for the "process" subsystem to fail. The process subsystem
784 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
786 - Terminate test-stem if it takes more than 9.5 minutes to run.
787 (Travis terminates the job after 10 minutes of no output.)
788 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
790 o Minor bugfixes (bootstrap reporting):
791 - During bootstrap reporting, correctly distinguish pluggable
792 transports from plain proxies. Fixes bug 28925; bugfix
795 o Minor bugfixes (C correctness):
796 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
797 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
800 o Minor bugfixes (circuitpadding testing):
801 - Minor tweaks to avoid rare test failures related to timers and
802 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
804 o Minor bugfixes (directory authorities):
805 - Actually include the bandwidth-file-digest line in directory
806 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
808 o Minor bugfixes (logging):
809 - On Windows, when errors cause us to reload a consensus from disk,
810 tell the user that we are retrying at log level "notice".
811 Previously we only logged this information at "info", which was
812 confusing because the errors themselves were logged at "warning".
813 Improves previous fix for 28614. Fixes bug 30004; bugfix
816 o Minor bugfixes (pluggable transports):
817 - Restore old behavior when it comes to discovering the path of a
818 given Pluggable Transport executable file. A change in
819 0.4.0.1-alpha had broken this behavior on paths containing a
820 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
822 o Minor bugfixes (testing):
823 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
824 recent test-network.sh to use new chutney features in CI. Fixes
825 bug 29703; bugfix on 0.2.9.1-alpha.
826 - Fix a test failure on Windows caused by an unexpected "BUG"
827 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
830 o Minor bugfixes (TLS protocol):
831 - When classifying a client's selection of TLS ciphers, if the
832 client ciphers are not yet available, do not cache the result.
833 Previously, we had cached the unavailability of the cipher list
834 and never looked again, which in turn led us to assume that the
835 client only supported the ancient V1 link protocol. This, in turn,
836 was causing Stem integration tests to stall in some cases. Fixes
837 bug 30021; bugfix on 0.2.4.8-alpha.
839 o Code simplification and refactoring:
840 - Introduce a connection_dir_buf_add() helper function that detects
841 whether compression is in use, and adds a string accordingly.
842 Resolves issue 28816.
843 - Refactor handle_get_next_bandwidth() to use
844 connection_dir_buf_add(). Implements ticket 29897.
847 - Clarify that Tor performs stream isolation among *Port listeners
848 by default. Resolves issue 29121.
851 Changes in version 0.4.0.3-alpha - 2019-03-22
852 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
853 bugs from earlier versions.
855 o Minor features (address selection):
856 - Treat the subnet 100.64.0.0/10 as public for some purposes;
857 private for others. This subnet is the RFC 6598 (Carrier Grade
858 NAT) IP range, and is deployed by many ISPs as an alternative to
859 RFC 1918 that does not break existing internal networks. Tor now
860 blocks SOCKS and control ports on these addresses and warns users
861 if client ports or ExtORPorts are listening on a RFC 6598 address.
862 Closes ticket 28525. Patch by Neel Chauhan.
864 o Minor features (geoip):
865 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
866 Country database. Closes ticket 29666.
868 o Minor bugfixes (circuitpadding):
869 - Inspect the circuit-level cell queue before sending padding, to
870 avoid sending padding when too much data is queued. Fixes bug
871 29204; bugfix on 0.4.0.1-alpha.
873 o Minor bugfixes (logging):
874 - Correct a misleading error message when IPv4Only or IPv6Only is
875 used but the resolved address can not be interpreted as an address
876 of the specified IP version. Fixes bug 13221; bugfix on
877 0.2.3.9-alpha. Patch from Kris Katterjohn.
878 - Log the correct port number for listening sockets when "auto" is
879 used to let Tor pick the port number. Previously, port 0 was
880 logged instead of the actual port number. Fixes bug 29144; bugfix
881 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
882 - Stop logging a BUG() warning when Tor is waiting for exit
883 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
885 o Minor bugfixes (memory management):
886 - Refactor the shared random state's memory management so that it
887 actually takes ownership of the shared random value pointers.
888 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
890 o Minor bugfixes (memory management, testing):
891 - Stop leaking parts of the shared random state in the shared-random
892 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
894 o Minor bugfixes (pluggable transports):
895 - Fix an assertion failure crash bug when a pluggable transport is
896 terminated during the bootstrap phase. Fixes bug 29562; bugfix
899 o Minor bugfixes (Rust, protover):
900 - Add a missing "Padding" value to the Rust implementation of
901 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
903 o Minor bugfixes (single onion services):
904 - Allow connections to single onion services to remain idle without
905 being disconnected. Previously, relays acting as rendezvous points
906 for single onion services were mistakenly closing idle rendezvous
907 circuits after 60 seconds, thinking that they were unused
908 directory-fetching circuits that had served their purpose. Fixes
909 bug 29665; bugfix on 0.2.1.26.
911 o Minor bugfixes (stats):
912 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
913 relay and bridge extra-info documents. Fixes bug 29017; bugfix
916 o Minor bugfixes (testing):
917 - Downgrade some LOG_ERR messages in the address/* tests to
918 warnings. The LOG_ERR messages were occurring when we had no
919 configured network. We were failing the unit tests, because we
920 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
921 29530; bugfix on 0.3.5.8.
922 - Fix our gcov wrapper script to look for object files at the
923 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
924 - Decrease the false positive rate of stochastic probability
925 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
927 o Minor bugfixes (Windows, CI):
928 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
929 Windows Server 2012 R2 job. The remaining 2 jobs still provide
930 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
931 fast_finish, so failed jobs terminate the build immediately. Fixes
932 bug 29601; bugfix on 0.3.5.4-alpha.
935 Changes in version 0.3.5.8 - 2019-02-21
936 Tor 0.3.5.8 backports several fixes from later releases, including fixes
937 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
940 It also includes a fix for a medium-severity security bug affecting Tor
941 0.3.2.1-alpha and later. All Tor instances running an affected release
942 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
944 o Major bugfixes (cell scheduler, KIST, security):
945 - Make KIST consider the outbuf length when computing what it can
946 put in the outbuf. Previously, KIST acted as though the outbuf
947 were empty, which could lead to the outbuf becoming too full. It
948 is possible that an attacker could exploit this bug to cause a Tor
949 client or relay to run out of memory and crash. Fixes bug 29168;
950 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
951 TROVE-2019-001 and CVE-2019-8955.
953 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
954 - Gracefully handle empty username/password fields in SOCKS5
955 username/password auth message and allow SOCKS5 handshake to
956 continue. Previously, we had rejected these handshakes, breaking
957 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
959 o Minor features (compilation, backport from 0.4.0.2-alpha):
960 - Compile correctly when OpenSSL is built with engine support
961 disabled, or with deprecated APIs disabled. Closes ticket 29026.
962 Patches from "Mangix".
964 o Minor features (geoip):
965 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
966 Country database. Closes ticket 29478.
968 o Minor features (testing, backport from 0.4.0.2-alpha):
969 - Treat all unexpected ERR and BUG messages as test failures. Closes
972 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
973 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
974 connection waiting for a descriptor that we actually have in the
975 cache. It turns out that this can actually happen, though it is
976 rare. Now, tor will recover and retry the descriptor. Fixes bug
977 28669; bugfix on 0.3.2.4-alpha.
979 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
980 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
981 IPv6 socket was bound using an address family of AF_INET instead
982 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
985 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
986 - Update Cargo.lock file to match the version made by the latest
987 version of Rust, so that "make distcheck" will pass again. Fixes
988 bug 29244; bugfix on 0.3.3.4-alpha.
990 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
991 - Select guards even if the consensus has expired, as long as the
992 consensus is still reasonably live. Fixes bug 24661; bugfix
995 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
996 - Compile correctly on OpenBSD; previously, we were missing some
997 headers required in order to detect it properly. Fixes bug 28938;
998 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1000 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
1001 - Describe the contents of the v3 onion service client authorization
1002 files correctly: They hold public keys, not private keys. Fixes
1003 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1005 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
1006 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1007 link protocol versions when logging incoming/outgoing connection
1008 counts. Tor no longer skips version 5, and we won't have to
1009 remember to update this function when new link protocol version is
1010 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1012 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1013 - Log more information at "warning" level when unable to read a
1014 private key; log more information at "info" level when unable to
1015 read a public key. We had warnings here before, but they were lost
1016 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1018 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
1019 - The amount of total available physical memory is now determined
1020 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1021 when it is defined and a 64-bit variant is not available. Fixes
1022 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1024 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1025 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1026 than one private key for a hidden service. Fixes bug 29040; bugfix
1028 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1029 "debug" level. Tor used to log it as a warning, which caused very
1030 long log lines to appear for some users. Fixes bug 29135; bugfix
1032 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1033 as a warning. Instead, log it as a protocol warning, because there
1034 is nothing that relay operators can do to fix it. Fixes bug 29029;
1035 bugfix on 0.2.5.7-rc.
1037 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
1038 - Mark outdated dirservers when Tor only has a reasonably live
1039 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1041 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
1042 - Detect and suppress "bug" warnings from the util/time test on
1043 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1044 - Do not log an error-level message if we fail to find an IPv6
1045 network interface from the unit tests. Fixes bug 29160; bugfix
1048 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
1049 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1050 Some users took this phrasing to mean that the mentioned guard was
1051 under their control or responsibility, which it is not. Fixes bug
1052 28895; bugfix on Tor 0.3.0.1-alpha.
1055 Changes in version 0.3.4.11 - 2019-02-21
1056 Tor 0.3.4.11 is the third stable release in its series. It includes
1057 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
1058 later. All Tor instances running an affected release should upgrade to
1059 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1061 o Major bugfixes (cell scheduler, KIST, security):
1062 - Make KIST consider the outbuf length when computing what it can
1063 put in the outbuf. Previously, KIST acted as though the outbuf
1064 were empty, which could lead to the outbuf becoming too full. It
1065 is possible that an attacker could exploit this bug to cause a Tor
1066 client or relay to run out of memory and crash. Fixes bug 29168;
1067 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1068 TROVE-2019-001 and CVE-2019-8955.
1070 o Minor features (geoip):
1071 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1072 Country database. Closes ticket 29478.
1074 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1075 - Update Cargo.lock file to match the version made by the latest
1076 version of Rust, so that "make distcheck" will pass again. Fixes
1077 bug 29244; bugfix on 0.3.3.4-alpha.
1079 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1080 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1081 as a warning. Instead, log it as a protocol warning, because there
1082 is nothing that relay operators can do to fix it. Fixes bug 29029;
1083 bugfix on 0.2.5.7-rc.
1086 Changes in version 0.3.3.12 - 2019-02-21
1087 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
1088 0.3.2.1-alpha and later. All Tor instances running an affected release
1089 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1091 This release marks the end of support for the Tor 0.3.3.x series. We
1092 recommend that users switch to either the Tor 0.3.4 series (supported
1093 until at least 10 June 2019), or the Tor 0.3.5 series, which will
1094 receive long-term support until at least 1 Feb 2022.
1096 o Major bugfixes (cell scheduler, KIST, security):
1097 - Make KIST consider the outbuf length when computing what it can
1098 put in the outbuf. Previously, KIST acted as though the outbuf
1099 were empty, which could lead to the outbuf becoming too full. It
1100 is possible that an attacker could exploit this bug to cause a Tor
1101 client or relay to run out of memory and crash. Fixes bug 29168;
1102 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1103 TROVE-2019-001 and CVE-2019-8955.
1105 o Minor features (geoip):
1106 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1107 Country database. Closes ticket 29478.
1109 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1110 - Update Cargo.lock file to match the version made by the latest
1111 version of Rust, so that "make distcheck" will pass again. Fixes
1112 bug 29244; bugfix on 0.3.3.4-alpha.
1114 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1115 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1116 as a warning. Instead, log it as a protocol warning, because there
1117 is nothing that relay operators can do to fix it. Fixes bug 29029;
1118 bugfix on 0.2.5.7-rc.
1121 Changes in version 0.4.0.2-alpha - 2019-02-21
1122 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
1123 bugs from earlier versions, including several that had broken
1124 backward compatibility.
1126 It also includes a fix for a medium-severity security bug affecting Tor
1127 0.3.2.1-alpha and later. All Tor instances running an affected release
1128 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1130 o Major bugfixes (cell scheduler, KIST, security):
1131 - Make KIST consider the outbuf length when computing what it can
1132 put in the outbuf. Previously, KIST acted as though the outbuf
1133 were empty, which could lead to the outbuf becoming too full. It
1134 is possible that an attacker could exploit this bug to cause a Tor
1135 client or relay to run out of memory and crash. Fixes bug 29168;
1136 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1137 TROVE-2019-001 and CVE-2019-8955.
1139 o Major bugfixes (networking):
1140 - Gracefully handle empty username/password fields in SOCKS5
1141 username/password auth messsage and allow SOCKS5 handshake to
1142 continue. Previously, we had rejected these handshakes, breaking
1143 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
1145 o Major bugfixes (windows, startup):
1146 - When reading a consensus file from disk, detect whether it was
1147 written in text mode, and re-read it in text mode if so. Always
1148 write consensus files in binary mode so that we can map them into
1149 memory later. Previously, we had written in text mode, which
1150 confused us when we tried to map the file on windows. Fixes bug
1151 28614; bugfix on 0.4.0.1-alpha.
1153 o Minor features (compilation):
1154 - Compile correctly when OpenSSL is built with engine support
1155 disabled, or with deprecated APIs disabled. Closes ticket 29026.
1156 Patches from "Mangix".
1158 o Minor features (developer tooling):
1159 - Check that bugfix versions in changes files look like Tor versions
1160 from the versions spec. Warn when bugfixes claim to be on a future
1161 release. Closes ticket 27761.
1162 - Provide a git pre-commit hook that disallows committing if we have
1163 any failures in our code and changelog formatting checks. It is
1164 now available in scripts/maint/pre-commit.git-hook. Implements
1167 o Minor features (directory authority):
1168 - When a directory authority is using a bandwidth file to obtain
1169 bandwidth values, include the digest of that file in the vote.
1170 Closes ticket 26698.
1172 o Minor features (geoip):
1173 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1174 Country database. Closes ticket 29478.
1176 o Minor features (testing):
1177 - Treat all unexpected ERR and BUG messages as test failures. Closes
1180 o Minor bugfixes (build, compatibility, rust):
1181 - Update Cargo.lock file to match the version made by the latest
1182 version of Rust, so that "make distcheck" will pass again. Fixes
1183 bug 29244; bugfix on 0.3.3.4-alpha.
1185 o Minor bugfixes (compilation):
1186 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
1187 29169; bugfix on 0.4.0.1-alpha.
1188 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1189 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1191 o Minor bugfixes (documentation):
1192 - Describe the contents of the v3 onion service client authorization
1193 files correctly: They hold public keys, not private keys. Fixes
1194 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1196 o Minor bugfixes (linux seccomp sandbox):
1197 - Fix startup crash when experimental sandbox support is enabled.
1198 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
1200 o Minor bugfixes (logging):
1201 - Avoid logging that we are relaxing a circuit timeout when that
1202 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1203 - Log more information at "warning" level when unable to read a
1204 private key; log more information at "info" level when unable to
1205 read a public key. We had warnings here before, but they were lost
1206 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1208 o Minor bugfixes (misc):
1209 - The amount of total available physical memory is now determined
1210 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1211 when it is defined and a 64-bit variant is not available. Fixes
1212 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1214 o Minor bugfixes (onion services):
1215 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1216 than one private key for a hidden service. Fixes bug 29040; bugfix
1218 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1219 "debug" level. Tor used to log it as a warning, which caused very
1220 long log lines to appear for some users. Fixes bug 29135; bugfix
1222 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1223 as a warning. Instead, log it as a protocol warning, because there
1224 is nothing that relay operators can do to fix it. Fixes bug 29029;
1225 bugfix on 0.2.5.7-rc.
1227 o Minor bugfixes (scheduler):
1228 - When re-adding channels to the pending list, check the correct
1229 channel's sched_heap_idx. This issue has had no effect in mainline
1230 Tor, but could have led to bugs down the road in improved versions
1231 of our circuit scheduling code. Fixes bug 29508; bugfix
1234 o Minor bugfixes (tests):
1235 - Fix intermittent failures on an adaptive padding test. Fixes one
1236 case of bug 29122; bugfix on 0.4.0.1-alpha.
1237 - Disable an unstable circuit-padding test that was failing
1238 intermittently because of an ill-defined small histogram. Such
1239 histograms will be allowed again after 29298 is implemented. Fixes
1240 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
1241 - Detect and suppress "bug" warnings from the util/time test on
1242 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1243 - Do not log an error-level message if we fail to find an IPv6
1244 network interface from the unit tests. Fixes bug 29160; bugfix
1248 - In the manpage entry describing MapAddress torrc setting, use
1249 example IP addresses from ranges specified for use in documentation
1250 by RFC 5737. Resolves issue 28623.
1253 - Remove the old check-tor script. Resolves issue 29072.
1256 Changes in version 0.4.0.1-alpha - 2019-01-18
1257 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
1258 introduces improved features for power and bandwidth conservation,
1259 more accurate reporting of bootstrap progress for user interfaces, and
1260 an experimental backend for an exciting new adaptive padding feature.
1261 There is also the usual assortment of bugfixes and minor features, all
1264 o Major features (battery management, client, dormant mode):
1265 - When Tor is running as a client, and it is unused for a long time,
1266 it can now enter a "dormant" state. When Tor is dormant, it avoids
1267 network and CPU activity until it is reawoken either by a user
1268 request or by a controller command. For more information, see the
1269 configuration options starting with "Dormant". Implements tickets
1271 - The client's memory of whether it is "dormant", and how long it
1272 has spent idle, persists across invocations. Implements
1274 - There is a DormantOnFirstStartup option that integrators can use
1275 if they expect that in many cases, Tor will be installed but
1278 o Major features (bootstrap reporting):
1279 - When reporting bootstrap progress, report the first connection
1280 uniformly, regardless of whether it's a connection for building
1281 application circuits. This allows finer-grained reporting of early
1282 progress than previously possible, with the improvements of ticket
1283 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
1284 - When reporting bootstrap progress, treat connecting to a proxy or
1285 pluggable transport as separate from having successfully used that
1286 proxy or pluggable transport to connect to a relay. Closes tickets
1289 o Major features (circuit padding):
1290 - Implement preliminary support for the circuit padding portion of
1291 Proposal 254. The implementation supports Adaptive Padding (aka
1292 WTF-PAD) state machines for use between experimental clients and
1293 relays. Support is also provided for APE-style state machines that
1294 use probability distributions instead of histograms to specify
1295 inter-packet delay. At the moment, Tor does not provide any
1296 padding state machines that are used in normal operation: for now,
1297 this feature exists solely for experimentation. Closes
1300 o Major features (refactoring):
1301 - Tor now uses an explicit list of its own subsystems when
1302 initializing and shutting down. Previously, these systems were
1303 managed implicitly in various places throughout the codebase.
1304 (There may still be some subsystems using the old system.) Closes
1307 o Minor features (bootstrap reporting):
1308 - When reporting bootstrap progress, stop distinguishing between
1309 situations where only internal paths are available and situations
1310 where external paths are available. Previously, Tor would often
1311 erroneously report that it had only internal paths. Closes
1314 o Minor features (continuous integration):
1315 - Log Python version during each Travis CI job. Resolves
1318 o Minor features (controller):
1319 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
1320 Implements ticket 28843.
1322 o Minor features (developer tooling):
1323 - Provide a git hook script to prevent "fixup!" and "squash!"
1324 commits from ending up in the master branch, as scripts/main/pre-
1325 push.git-hook. Closes ticket 27993.
1327 o Minor features (directory authority):
1328 - Directory authorities support a new consensus algorithm, under
1329 which the family lines in microdescriptors are encoded in a
1330 canonical form. This change makes family lines more compressible
1331 in transit, and on the client. Closes ticket 28266; implements
1334 o Minor features (directory authority, relay):
1335 - Authorities now vote on a "StaleDesc" flag to indicate that a
1336 relay's descriptor is so old that the relay should upload again
1337 soon. Relays treat this flag as a signal to upload a new
1338 descriptor. This flag will eventually let us remove the
1339 'published' date from routerstatus entries, and make our consensus
1340 diffs much smaller. Closes ticket 26770; implements proposal 293.
1342 o Minor features (fallback directory mirrors):
1343 - Update the fallback whitelist based on operator opt-ins and opt-
1344 outs. Closes ticket 24805, patch by Phoul.
1346 o Minor features (FreeBSD):
1347 - On FreeBSD-based systems, warn relay operators if the
1348 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
1349 Closes ticket 28518.
1351 o Minor features (HTTP standards compliance):
1352 - Stop sending the header "Content-type: application/octet-stream"
1353 along with transparently compressed documents: this confused
1354 browsers. Closes ticket 28100.
1356 o Minor features (IPv6):
1357 - We add an option ClientAutoIPv6ORPort, to make clients randomly
1358 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
1359 every time a node is loaded from a new consensus or bridge config.
1360 We expect that this option will enable clients to bootstrap more
1361 quickly without having to determine whether they support IPv4,
1362 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
1363 - When using addrs_in_same_network_family(), avoid choosing circuit
1364 paths that pass through the same IPv6 subnet more than once.
1365 Previously, we only checked IPv4 subnets. Closes ticket 24393.
1366 Patch by Neel Chauhan.
1368 o Minor features (log messages):
1369 - Improve log message in v3 onion services that could print out
1370 negative revision counters. Closes ticket 27707. Patch
1373 o Minor features (memory usage):
1374 - Save memory by storing microdescriptor family lists with a more
1375 compact representation. Closes ticket 27359.
1376 - Tor clients now use mmap() to read consensus files from disk, so
1377 that they no longer need keep the full text of a consensus in
1378 memory when parsing it or applying a diff. Closes ticket 27244.
1380 o Minor features (parsing):
1381 - Directory authorities now validate that router descriptors and
1382 ExtraInfo documents are in a valid subset of UTF-8, and reject
1383 them if they are not. Closes ticket 27367.
1385 o Minor features (performance):
1386 - Cache the results of summarize_protocol_flags(), so that we don't
1387 have to parse the same protocol-versions string over and over.
1388 This should save us a huge number of malloc calls on startup, and
1389 may reduce memory fragmentation with some allocators. Closes
1391 - Remove a needless memset() call from get_token_arguments, thereby
1392 speeding up the tokenization of directory objects by about 20%.
1393 Closes ticket 28852.
1394 - Replace parse_short_policy() with a faster implementation, to
1395 improve microdescriptor parsing time. Closes ticket 28853.
1396 - Speed up directory parsing a little by avoiding use of the non-
1397 inlined strcmp_len() function. Closes ticket 28856.
1398 - Speed up microdescriptor parsing by about 30%, to help improve
1399 startup time. Closes ticket 28839.
1401 o Minor features (pluggable transports):
1402 - Add support for emitting STATUS updates to Tor's control port from
1403 a pluggable transport process. Closes ticket 28846.
1404 - Add support for logging to Tor's logging subsystem from a
1405 pluggable transport process. Closes ticket 28180.
1407 o Minor features (process management):
1408 - Add a new process API for handling child processes. This new API
1409 allows Tor to have bi-directional communication with child
1410 processes on both Unix and Windows. Closes ticket 28179.
1411 - Use the subsystem manager to initialize and shut down the process
1412 module. Closes ticket 28847.
1414 o Minor features (relay):
1415 - When listing relay families, list them in canonical form including
1416 the relay's own identity, and try to give a more useful set of
1417 warnings. Part of ticket 28266 and proposal 298.
1419 o Minor features (required protocols):
1420 - Before exiting because of a missing required protocol, Tor will
1421 now check the publication time of the consensus, and not exit
1422 unless the consensus is newer than the Tor program's own release
1423 date. Previously, Tor would not check the consensus publication
1424 time, and so might exit because of a missing protocol that might
1425 no longer be required in a current consensus. Implements proposal
1426 297; closes ticket 27735.
1428 o Minor features (testing):
1429 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
1430 networks. Closes ticket 28840. Patch by Rob Jansen.
1432 o Minor bugfixes (client, clock skew):
1433 - Bootstrap successfully even when Tor's clock is behind the clocks
1434 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
1435 - Select guards even if the consensus has expired, as long as the
1436 consensus is still reasonably live. Fixes bug 24661; bugfix
1439 o Minor bugfixes (compilation):
1440 - Compile correctly on OpenBSD; previously, we were missing some
1441 headers required in order to detect it properly. Fixes bug 28938;
1442 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1444 o Minor bugfixes (directory clients):
1445 - Mark outdated dirservers when Tor only has a reasonably live
1446 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1448 o Minor bugfixes (directory mirrors):
1449 - Even when a directory mirror's clock is behind the clocks on the
1450 authorities, we now allow the mirror to serve "future"
1451 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
1453 o Minor bugfixes (DNS):
1454 - Gracefully handle an empty or absent resolve.conf file by falling
1455 back to using "localhost" as a DNS server (and hoping it works).
1456 Previously, we would just stop running as an exit. Fixes bug
1457 21900; bugfix on 0.2.1.10-alpha.
1459 o Minor bugfixes (guards):
1460 - In count_acceptable_nodes(), the minimum number is now one bridge
1461 or guard node, and two non-guard nodes for a circuit. Previously,
1462 we had added up the sum of all nodes with a descriptor, but that
1463 could cause us to build failing circuits when we had either too
1464 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
1465 0.3.6.1-alpha. Patch by Neel Chauhan.
1467 o Minor bugfixes (IPv6):
1468 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1469 IPv6 socket was bound using an address family of AF_INET instead
1470 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1473 o Minor bugfixes (logging):
1474 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1475 link protocol versions when logging incoming/outgoing connection
1476 counts. Tor no longer skips version 5, and we won't have to
1477 remember to update this function when new link protocol version is
1478 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1480 o Minor bugfixes (networking):
1481 - Introduce additional checks into tor_addr_parse() to reject
1482 certain incorrect inputs that previously were not detected. Fixes
1483 bug 23082; bugfix on 0.2.0.10-alpha.
1485 o Minor bugfixes (onion service v3, client):
1486 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1487 connection waiting for a descriptor that we actually have in the
1488 cache. It turns out that this can actually happen, though it is
1489 rare. Now, tor will recover and retry the descriptor. Fixes bug
1490 28669; bugfix on 0.3.2.4-alpha.
1492 o Minor bugfixes (periodic events):
1493 - Refrain from calling routerlist_remove_old_routers() from
1494 check_descriptor_callback(). Instead, create a new hourly periodic
1495 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1497 o Minor bugfixes (pluggable transports):
1498 - Make sure that data is continously read from standard output and
1499 standard error pipes of a pluggable transport child-process, to
1500 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1501 bugfix on 0.2.3.6-alpha.
1503 o Minor bugfixes (unit tests):
1504 - Instead of relying on hs_free_all() to clean up all onion service
1505 objects in test_build_descriptors(), we now deallocate them one by
1506 one. This lets Coverity know that we are not leaking memory there
1507 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1509 o Minor bugfixes (usability):
1510 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1511 Some users took this phrasing to mean that the mentioned guard was
1512 under their control or responsibility, which it is not. Fixes bug
1513 28895; bugfix on Tor 0.3.0.1-alpha.
1515 o Code simplification and refactoring:
1516 - Reimplement NETINFO cell parsing and generation to rely on
1517 trunnel-generated wire format handling code. Closes ticket 27325.
1518 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1520 - Rework SOCKS wire format handling to rely on trunnel-generated
1521 parsing/generation code. Resolves ticket 27620.
1522 - Split out bootstrap progress reporting from control.c into a
1523 separate file. Part of ticket 27402.
1524 - The .may_include files that we use to describe our directory-by-
1525 directory dependency structure now describe a noncircular
1526 dependency graph over the directories that they cover. Our
1527 checkIncludes.py tool now enforces this noncircularity. Closes
1531 - Mention that you cannot add a new onion service if Tor is already
1532 running with Sandbox enabled. Closes ticket 28560.
1533 - Improve ControlPort documentation. Mention that it accepts
1534 address:port pairs, and can be used multiple times. Closes
1536 - Document the exact output of "tor --version". Closes ticket 28889.
1539 - Stop responding to the 'GETINFO status/version/num-concurring' and
1540 'GETINFO status/version/num-versioning' control port commands, as
1541 those were deprecated back in 0.2.0.30. Also stop listing them in
1542 output of 'GETINFO info/names'. Resolves ticket 28757.
1543 - The scripts used to generate and maintain the list of fallback
1544 directories have been extracted into a new "fallback-scripts"
1545 repository. Closes ticket 27914.
1548 - Run shellcheck for scripts in the in scripts/ directory. Closes
1550 - Add unit tests for tokenize_string() and get_next_token()
1551 functions. Resolves ticket 27625.
1553 o Code simplification and refactoring (onion service v3):
1554 - Consolidate the authorized client descriptor cookie computation
1555 code from client and service into one function. Closes
1558 o Code simplification and refactoring (shell scripts):
1559 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1561 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1562 Resolves ticket 28006.
1563 - Fix issues that shellcheck found in updateRustDependencies.sh.
1564 Resolves ticket 28012.
1565 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1566 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1567 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1568 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1572 Changes in version 0.3.3.11 - 2019-01-07
1573 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1574 numerous fixes, including an important fix for anyone using OpenSSL
1575 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1576 to this version, or to a later series.
1578 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1579 We anticipate that this will be the last release of Tor 0.3.3, unless
1580 some major bug is before then. Some time between now and then, users
1581 should switch to either the Tor 0.3.4 series (supported until at least
1582 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1583 support until at least 1 Feb 2022.
1585 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1586 - Fix our usage of named groups when running as a TLS 1.3 client in
1587 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1588 running as a relay, which caused clients to fail to negotiate TLS
1589 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1592 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1593 - Fix a use-after-free error that could be caused by passing Tor an
1594 impossible set of options that would fail during options_act().
1595 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1597 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1598 - Only run one online rust build in Travis, to reduce network
1599 errors. Skip offline rust builds on Travis for Linux gcc, because
1600 they're redundant. Implements ticket 27252.
1601 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1602 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1603 Linux with default settings, because all the non-default builds
1604 use gcc on Linux. Implements ticket 27252.
1606 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1607 - Use the Travis Homebrew addon to install packages on macOS during
1608 Travis CI. The package list is the same, but the Homebrew addon
1609 does not do a `brew update` by default. Implements ticket 27738.
1611 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1612 - Replace the 150 fallbacks originally introduced in Tor
1613 0.3.3.1-alpha in January 2018 (of which ~115 were still
1614 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1615 removed) generated in December 2018. Closes ticket 24803.
1617 o Minor features (geoip):
1618 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1619 Country database. Closes ticket 29012.
1621 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1622 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1623 key export function from handling long labels. When this bug is
1624 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1625 version of OpenSSL without this bug when it becomes available.
1626 Closes ticket 28973.
1628 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1629 - Update relay descriptor on bandwidth changes only when the uptime
1630 is smaller than 24h, in order to reduce the efficiency of guard
1631 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1633 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1634 - Avoid undefined behavior in an end-of-string check when parsing
1635 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1638 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1639 - Rewrite our assertion macros so that they no longer suppress the
1640 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1642 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1643 - Initialize a variable unconditionally in aes_new_cipher(), since
1644 some compilers cannot tell that we always initialize it before
1645 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1647 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1648 - Log additional info when we get a relay that shares an ed25519 ID
1649 with a different relay, instead making a BUG() warning. Fixes bug
1650 27800; bugfix on 0.3.2.1-alpha.
1652 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1653 - When a user requests a group-readable DataDirectory, give it to
1654 them. Previously, when the DataDirectory and the CacheDirectory
1655 were the same, the default setting (0) for
1656 CacheDirectoryGroupReadable would override the setting for
1657 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1660 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1661 - When the onion service directory can't be created or has the wrong
1662 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1665 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1666 - Close all SOCKS request (for the same .onion) if the newly fetched
1667 descriptor is unusable. Before that, we would close only the first
1668 one leaving the other hanging and let to time out by themselves.
1669 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1671 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1672 - Don't warn so loudly when Tor is unable to decode an onion
1673 descriptor. This can now happen as a normal use case if a client
1674 gets a descriptor with client authorization but the client is not
1675 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1677 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1678 - When deleting an ephemeral onion service (DEL_ONION), do not close
1679 any rendezvous circuits in order to let the existing client
1680 connections finish by themselves or closed by the application. The
1681 HS v2 is doing that already so now we have the same behavior for
1682 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1684 o Minor bugfixes (HTTP tunnel):
1685 - Fix a bug warning when closing an HTTP tunnel connection due to
1686 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1689 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1690 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1691 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1693 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1694 - Ensure circuitmux queues are empty before scheduling or sending
1695 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1697 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1698 - Reject protocol names containing bytes other than alphanumeric
1699 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1702 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1703 - Compute protover votes correctly in the rust version of the
1704 protover code. Previously, the protover rewrite in 24031 allowed
1705 repeated votes from the same voter for the same protocol version
1706 to be counted multiple times in protover_compute_vote(). Fixes bug
1707 27649; bugfix on 0.3.3.5-rc.
1708 - Reject protover names that contain invalid characters. Fixes bug
1709 27687; bugfix on 0.3.3.1-alpha.
1711 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1712 - protover_all_supported() would attempt to allocate up to 16GB on
1713 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1714 bugfix on 0.3.3.5-rc.
1716 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1717 - Fix a potential null dereference in protover_all_supported(). Add
1718 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1719 - Return a string that can be safely freed by C code, not one
1720 created by the rust allocator, in protover_all_supported(). Fixes
1721 bug 27740; bugfix on 0.3.3.1-alpha.
1722 - Fix an API mismatch in the rust implementation of
1723 protover_compute_vote(). This bug could have caused crashes on any
1724 directory authorities running Tor with Rust (which we do not yet
1725 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1727 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1728 - If a unit test running in a subprocess exits abnormally or with a
1729 nonzero status code, treat the test as having failed, even if the
1730 test reported success. Without this fix, memory leaks don't cause
1731 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1732 bugfix on 0.2.2.4-alpha.
1734 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1735 - Treat backtrace test failures as expected on BSD-derived systems
1736 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1737 (FreeBSD failures have been treated as expected since 18204 in
1738 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1740 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1741 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1742 bugfix on 0.3.0.1-alpha.
1745 Changes in version 0.3.4.10 - 2019-01-07
1746 Tor 0.3.4.9 is the second stable release in its series; it backports
1747 numerous fixes, including an important fix for relays, and for anyone
1748 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1751 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1752 2019. Some time between now and then, users should switch to the Tor
1753 0.3.5 series, which will receive long-term support until at least 1
1756 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1757 - Fix our usage of named groups when running as a TLS 1.3 client in
1758 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1759 running as a relay, which caused clients to fail to negotiate TLS
1760 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1763 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1764 - Always reactivate linked connections in the main loop so long as
1765 any linked connection has been active. Previously, connections
1766 serving directory information wouldn't get reactivated after the
1767 first chunk of data was sent (usually 32KB), which would prevent
1768 clients from bootstrapping. Fixes bug 28912; bugfix on
1769 0.3.4.1-alpha. Patch by "cypherpunks3".
1771 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1772 - Always show the configure and test logs, and upload them as build
1773 artifacts, when building for Windows using Appveyor CI.
1776 o Minor features (controller, backport from 0.3.5.1-alpha):
1777 - For purposes of CIRC_BW-based dropped cell detection, track half-
1778 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1779 bias check cells to arrive without counting it as dropped until
1780 either the END arrives, or the windows are empty. Closes
1783 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1784 - Replace the 150 fallbacks originally introduced in Tor
1785 0.3.3.1-alpha in January 2018 (of which ~115 were still
1786 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1787 removed) generated in December 2018. Closes ticket 24803.
1789 o Minor features (geoip):
1790 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1791 Country database. Closes ticket 28395.
1793 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1794 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1795 key export function from handling long labels. When this bug is
1796 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1797 version of OpenSSL without this bug when it becomes available.
1798 Closes ticket 28973.
1800 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1801 - Initialize a variable unconditionally in aes_new_cipher(), since
1802 some compilers cannot tell that we always initialize it before
1803 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1805 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1806 - Avoid a logging a BUG() stacktrace when closing connection held
1807 open because the write side is rate limited but not the read side.
1808 Now, the connection read side is simply shut down until Tor is
1809 able to flush the connection and close it. Fixes bug 27750; bugfix
1812 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1813 - Manually configure the zstd compiler options, when building using
1814 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1815 not come with a pkg-config file. Fixes bug 28454; bugfix
1817 - Stop using an external OpenSSL install, and stop installing MSYS2
1818 packages, when building using mingw on Appveyor Windows CI. Fixes
1819 bug 28399; bugfix on 0.3.4.1-alpha.
1821 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1822 - Explicitly specify the path to the OpenSSL library and do not
1823 download OpenSSL from Pacman, but instead use the library that is
1824 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1826 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1827 - When a user requests a group-readable DataDirectory, give it to
1828 them. Previously, when the DataDirectory and the CacheDirectory
1829 were the same, the default setting (0) for
1830 CacheDirectoryGroupReadable would override the setting for
1831 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1834 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1835 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1836 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1838 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1839 - Don't warn so loudly when Tor is unable to decode an onion
1840 descriptor. This can now happen as a normal use case if a client
1841 gets a descriptor with client authorization but the client is not
1842 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1844 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1845 - When deleting an ephemeral onion service (DEL_ONION), do not close
1846 any rendezvous circuits in order to let the existing client
1847 connections finish by themselves or closed by the application. The
1848 HS v2 is doing that already so now we have the same behavior for
1849 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1851 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1852 - Update relay descriptor on bandwidth changes only when the uptime
1853 is smaller than 24h, in order to reduce the efficiency of guard
1854 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1856 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1857 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1858 bugfix on 0.3.0.1-alpha.
1861 Changes in version 0.3.5.7 - 2019-01-07
1862 Tor 0.3.5.7 is the first stable release in its series; it includes
1863 compilation and portability fixes, and a fix for a severe problem
1864 affecting directory caches.
1866 The Tor 0.3.5 series includes several new features and performance
1867 improvements, including client authorization for v3 onion services,
1868 cleanups to bootstrap reporting, support for improved bandwidth-
1869 measurement tools, experimental support for NSS in place of OpenSSL,
1870 and much more. It also begins a full reorganization of Tor's code
1871 layout, for improved modularity and maintainability in the future.
1872 Finally, there is the usual set of performance improvements and
1873 bugfixes that we try to do in every release series.
1875 There are a couple of changes in the 0.3.5 that may affect
1876 compatibility. First, the default version for newly created onion
1877 services is now v3. Use the HiddenServiceVersion option if you want to
1878 override this. Second, some log messages related to bootstrapping have
1879 changed; if you use stem, you may need to update to the latest version
1880 so it will recognize them.
1882 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1883 will continue to patch major bugs in typical configurations of 0.3.5
1884 until at least 1 Feb 2022. (We do not plan to provide long-term
1885 support for embedding, Rust support, NSS support, running a directory
1886 authority, or unsupported platforms. For these, you will need to stick
1887 with the latest stable release.)
1889 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1890 since 0.3.4.9, see the ReleaseNotes file.
1892 o Major bugfixes (relay, directory):
1893 - Always reactivate linked connections in the main loop so long as
1894 any linked connection has been active. Previously, connections
1895 serving directory information wouldn't get reactivated after the
1896 first chunk of data was sent (usually 32KB), which would prevent
1897 clients from bootstrapping. Fixes bug 28912; bugfix on
1898 0.3.4.1-alpha. Patch by "cypherpunks3".
1900 o Minor features (compilation):
1901 - When possible, place our warning flags in a separate file, to
1902 avoid flooding verbose build logs. Closes ticket 28924.
1904 o Minor features (geoip):
1905 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1906 Country database. Closes ticket 29012.
1908 o Minor features (OpenSSL bug workaround):
1909 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1910 key export function from handling long labels. When this bug is
1911 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1912 version of OpenSSL without this bug when it becomes available.
1913 Closes ticket 28973.
1915 o Minor features (performance):
1916 - Remove about 96% of the work from the function that we run at
1917 startup to test our curve25519_basepoint implementation. Since
1918 this function has yet to find an actual failure, we now only run
1919 it for 8 iterations instead of 200. Based on our profile
1920 information, this change should save around 8% of our startup time
1921 on typical desktops, and may have a similar effect on other
1922 platforms. Closes ticket 28838.
1923 - Stop re-validating our hardcoded Diffie-Hellman parameters on
1924 every startup. Doing this wasted time and cycles, especially on
1925 low-powered devices. Closes ticket 28851.
1927 o Minor bugfixes (compilation):
1928 - Fix compilation for Android by adding a missing header to
1929 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
1931 o Minor bugfixes (correctness):
1932 - Fix an unreached code path where we checked the value of
1933 "hostname" inside send_resolved_hostname_cell(). Previously, we
1934 used it before checking it; now we check it first. Fixes bug
1935 28879; bugfix on 0.1.2.7-alpha.
1937 o Minor bugfixes (testing):
1938 - Make sure that test_rebind.py actually obeys its timeout, even
1939 when it receives a large number of log messages. Fixes bug 28883;
1940 bugfix on 0.3.5.4-alpha.
1941 - Stop running stem's unit tests as part of "make test-stem", but
1942 continue to run stem's unit and online tests during "make test-
1943 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
1945 o Minor bugfixes (windows services):
1946 - Make Tor start correctly as an NT service again: previously it was
1947 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
1949 o Code simplification and refactoring:
1950 - When parsing a port configuration, make it more obvious to static
1951 analyzer tools that we always initialize the address. Closes
1955 Changes in version 0.3.5.6-rc - 2018-12-18
1956 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
1957 It is the first release candidate in the 0.3.5.x series; if no further
1958 huge bugs are found, our next release may be the stable 0.3.5.x.
1960 o Minor features (continuous integration, Windows):
1961 - Always show the configure and test logs, and upload them as build
1962 artifacts, when building for Windows using Appveyor CI.
1965 o Minor features (fallback directory list):
1966 - Replace the 150 fallbacks originally introduced in Tor
1967 0.3.3.1-alpha in January 2018 (of which ~115 were still
1968 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1969 removed) generated in December 2018. Closes ticket 24803.
1971 o Minor features (geoip):
1972 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
1973 Country database. Closes ticket 28744.
1975 o Minor bugfixes (compilation):
1976 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
1977 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
1979 o Minor bugfixes (continuous integration, Windows):
1980 - Explicitly specify the path to the OpenSSL library and do not
1981 download OpenSSL from Pacman, but instead use the library that is
1982 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1984 o Minor bugfixes (onion service v3):
1985 - When deleting an ephemeral onion service (DEL_ONION), do not close
1986 any rendezvous circuits in order to let the existing client
1987 connections finish by themselves or closed by the application. The
1988 HS v2 is doing that already so now we have the same behavior for
1989 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1991 o Minor bugfixes (restart-in-process, boostrap):
1992 - Add missing resets of bootstrap tracking state when shutting down
1993 (regression caused by ticket 27169). Fixes bug 28524; bugfix
1996 o Minor bugfixes (testing):
1997 - Use a separate DataDirectory for the test_rebind script.
1998 Previously, this script would run using the default DataDirectory,
1999 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
2000 Patch from Taylor R Campbell.
2001 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
2002 bugfix on 0.3.0.1-alpha.
2004 o Minor bugfixes (Windows):
2005 - Correctly identify Windows 8.1, Windows 10, and Windows Server
2006 2008 and later from their NT versions. Fixes bug 28096; bugfix on
2007 0.2.2.34; reported by Keifer Bly.
2008 - On recent Windows versions, the GetVersionEx() function may report
2009 an earlier Windows version than the running OS. To avoid user
2010 confusion, add "[or later]" to Tor's version string on affected
2011 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
2013 - Remove Windows versions that were never supported by the
2014 GetVersionEx() function. Stop duplicating the latest Windows
2015 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
2016 reported by Keifer Bly.
2019 - Increase logging and tag all log entries with timestamps in
2020 test_rebind.py. Provides diagnostics for issue 28229.
2022 o Code simplification and refactoring (shared random, dirauth):
2023 - Change many tor_assert() to use BUG() instead. The idea is to not
2024 crash a dirauth but rather scream loudly with a stacktrace and let
2025 it continue run. The shared random subsystem is very resilient and
2026 if anything wrong happens with it, at worst a non coherent value
2027 will be put in the vote and discarded by the other authorities.
2028 Closes ticket 19566.
2030 o Documentation (onion services):
2031 - Document in the man page that changing ClientOnionAuthDir value or
2032 adding a new file in the directory will not work at runtime upon
2033 sending a HUP if Sandbox 1. Closes ticket 28128.
2034 - Note in the man page that the only real way to fully revoke an
2035 onion service v3 client authorization is by restarting the tor
2036 process. Closes ticket 28275.
2039 Changes in version 0.3.5.5-alpha - 2018-11-16
2040 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
2041 including several that we hope to backport to older release series in
2044 o Major bugfixes (OpenSSL, portability):
2045 - Fix our usage of named groups when running as a TLS 1.3 client in
2046 OpenSSL 1.1.1. Previously, we only initialized EC groups when
2047 running as a relay, which caused clients to fail to negotiate TLS
2048 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
2051 o Minor features (geoip):
2052 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
2053 Country database. Closes ticket 28395.
2055 o Minor bugfixes (compilation):
2056 - Initialize a variable unconditionally in aes_new_cipher(), since
2057 some compilers cannot tell that we always initialize it before
2058 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
2060 o Minor bugfixes (connection, relay):
2061 - Avoid a logging a BUG() stacktrace when closing connection held
2062 open because the write side is rate limited but not the read side.
2063 Now, the connection read side is simply shut down until Tor is
2064 able to flush the connection and close it. Fixes bug 27750; bugfix
2067 o Minor bugfixes (continuous integration, Windows):
2068 - Manually configure the zstd compiler options, when building using
2069 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
2070 not come with a pkg-config file. Fixes bug 28454; bugfix
2072 - Stop using an external OpenSSL install, and stop installing MSYS2
2073 packages, when building using mingw on Appveyor Windows CI. Fixes
2074 bug 28399; bugfix on 0.3.4.1-alpha.
2076 o Minor bugfixes (documentation):
2077 - Make Doxygen work again after the code movement in the 0.3.5
2078 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
2080 o Minor bugfixes (Linux seccomp2 sandbox):
2081 - Permit the "shutdown()" system call, which is apparently used by
2082 OpenSSL under some circumstances. Fixes bug 28183; bugfix
2085 o Minor bugfixes (logging):
2086 - Stop talking about the Named flag in log messages. Clients have
2087 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
2090 o Minor bugfixes (memory leaks):
2091 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
2092 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
2094 o Minor bugfixes (onion services):
2095 - On an intro point for a version 3 onion service, stop closing
2096 introduction circuits on an NACK. This lets the client decide
2097 whether to reuse the circuit or discard it. Previously, we closed
2098 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
2099 0.3.2.1-alpha. Patch by Neel Chaunan.
2100 - When replacing a descriptor in the client cache, make sure to
2101 close all client introduction circuits for the old descriptor, so
2102 we don't end up with unusable leftover circuits. Fixes bug 27471;
2103 bugfix on 0.3.2.1-alpha.
2106 Changes in version 0.3.5.4-alpha - 2018-11-08
2107 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
2108 improves our continuous integration support. It continues our attempts
2109 to stabilize this alpha branch and build it into a foundation for an
2110 acceptable long-term-support release.
2112 o Major bugfixes (compilation, rust):
2113 - Rust tests can now build and run successfully with the
2114 --enable-fragile-hardening option enabled. Doing this currently
2115 requires the rust beta channel; it will be possible with stable
2116 rust once Rust version 1.31 is released. Patch from Alex Crichton.
2117 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
2119 o Major bugfixes (embedding, main loop):
2120 - When DisableNetwork becomes set, actually disable periodic events
2121 that are already enabled. (Previously, we would refrain from
2122 enabling new ones, but we would leave the old ones turned on.)
2123 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
2125 o Minor features (continuous integration):
2126 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
2128 - Add new CI job to Travis configuration to run stem-based
2129 integration tests. Closes ticket 27913.
2131 o Minor features (Windows, continuous integration):
2132 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
2133 Appveyor's CI. Closes ticket 28318.
2135 o Minor bugfixes (C correctness, also in 0.3.4.9):
2136 - Avoid undefined behavior in an end-of-string check when parsing
2137 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2140 o Minor bugfixes (compilation):
2141 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
2142 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2144 o Minor bugfixes (compilation, OpenSolaris):
2145 - Fix compilation on OpenSolaris and its descendants by adding a
2146 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
2149 o Minor bugfixes (configuration):
2150 - Refuse to start with relative file paths and RunAsDaemon set
2151 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
2154 o Minor bugfixes (directory authority, also in 0.3.4.9):
2155 - Log additional info when we get a relay that shares an ed25519 ID
2156 with a different relay, instead of a BUG() warning with a
2157 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
2159 o Minor bugfixes (onion service v3):
2160 - Build the service descriptor's signing key certificate before
2161 uploading, so we always have a fresh one: leaving no chances for
2162 it to expire service side. Fixes bug 27838; bugfix
2165 o Minor bugfixes (onion service v3, client authorization):
2166 - Fix an assert() when adding a client authorization for the first
2167 time and then sending a HUP signal to the service. Before that,
2168 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
2170 o Minor bugfixes (onion services):
2171 - Unless we have explicitly set HiddenServiceVersion, detect the
2172 onion service version and then look for invalid options.
2173 Previously, we did the reverse, but that broke existing configs
2174 which were pointed to a v2 service and had options like
2175 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
2176 0.3.5.1-alpha. Patch by Neel Chauhan.
2178 o Minor bugfixes (portability):
2179 - Make the OPE code (which is used for v3 onion services) run
2180 correctly on big-endian platforms. Fixes bug 28115; bugfix
2183 o Minor bugfixes (protover, rust):
2184 - Reject extra commas in version strings. Fixes bug 27197; bugfix
2187 o Minor bugfixes (relay shutdown, systemd):
2188 - Notify systemd of ShutdownWaitLength so it can be set to longer
2189 than systemd's TimeoutStopSec. In Tor's systemd service file, set
2190 TimeoutSec to 60 seconds to allow Tor some time to shut down.
2191 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
2193 o Minor bugfixes (rust, also in 0.3.4.9):
2194 - Fix a potential null dereference in protover_all_supported(). Add
2195 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2196 - Return a string that can be safely freed by C code, not one
2197 created by the rust allocator, in protover_all_supported(). Fixes
2198 bug 27740; bugfix on 0.3.3.1-alpha.
2200 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
2201 - Fix an API mismatch in the rust implementation of
2202 protover_compute_vote(). This bug could have caused crashes on any
2203 directory authorities running Tor with Rust (which we do not yet
2204 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2206 o Minor bugfixes (testing):
2207 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
2208 27968; bugfix on 0.3.5.1-alpha.
2210 o Minor bugfixes (testing, also in 0.3.4.9):
2211 - Treat backtrace test failures as expected on BSD-derived systems
2212 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2213 (FreeBSD failures have been treated as expected since 18204 in
2214 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2216 o Documentation (onion service manpage):
2217 - Improve HSv3 client authorization by making some options more
2218 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
2221 Changes in version 0.3.4.9 - 2018-11-02
2222 Tor 0.3.4.9 is the second stable release in its series; it backports
2223 numerous fixes, including a fix for a bandwidth management bug that
2224 was causing memory exhaustion on relays. Anyone running an earlier
2225 version of Tor 0.3.4.9 should upgrade.
2227 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
2228 - Fix compilation on ARM (and other less-used CPUs) when compiling
2229 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2231 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
2232 - Make sure Tor bootstraps and works properly if only the
2233 ControlPort is set. Prior to this fix, Tor would only bootstrap
2234 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2235 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2237 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
2238 - When our write bandwidth limit is exhausted, stop writing on the
2239 connection. Previously, we had a typo in the code that would make
2240 us stop reading instead, leading to relay connections being stuck
2241 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2244 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
2245 - Fix a use-after-free error that could be caused by passing Tor an
2246 impossible set of options that would fail during options_act().
2247 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2249 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
2250 - Don't do a distcheck with --disable-module-dirauth in Travis.
2251 Implements ticket 27252.
2252 - Only run one online rust build in Travis, to reduce network
2253 errors. Skip offline rust builds on Travis for Linux gcc, because
2254 they're redundant. Implements ticket 27252.
2255 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2256 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2257 Linux with default settings, because all the non-default builds
2258 use gcc on Linux. Implements ticket 27252.
2260 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
2261 - Use the Travis Homebrew addon to install packages on macOS during
2262 Travis CI. The package list is the same, but the Homebrew addon
2263 does not do a `brew update` by default. Implements ticket 27738.
2265 o Minor features (geoip):
2266 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2267 Country database. Closes ticket 27991.
2269 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
2270 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2271 difference algorithm for 32-bit Apple platforms. Previously, it
2272 would overflow when calculating the difference between two times
2273 more than 47 days apart. Fixes part of bug 27139; bugfix
2275 - Improve the precision of our 32-bit millisecond difference
2276 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2277 bugfix on 0.3.4.1-alpha.
2278 - Relax the tolerance on the mainloop/update_time_jumps test when
2279 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2282 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
2283 - Avoid undefined behavior in an end-of-string check when parsing
2284 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2287 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
2288 - Only install the necessary mingw packages during our appveyor
2289 builds. This change makes the build a little faster, and prevents
2290 a conflict with a preinstalled mingw openssl that appveyor now
2291 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2293 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2294 - Rewrite our assertion macros so that they no longer suppress the
2295 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2297 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2298 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2299 27464; bugfix on 0.3.4.1-alpha.
2301 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2302 - Log additional info when we get a relay that shares an ed25519 ID
2303 with a different relay, instead making a BUG() warning. Fixes bug
2304 27800; bugfix on 0.3.2.1-alpha.
2306 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2307 - Avoid a double-close when shutting down a stalled directory
2308 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2310 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2311 - Fix a bug warning when closing an HTTP tunnel connection due to an
2312 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2315 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2316 - Ensure circuitmux queues are empty before scheduling or sending
2317 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2319 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2320 - When the onion service directory can't be created or has the wrong
2321 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2324 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2325 - Close all SOCKS request (for the same .onion) if the newly fetched
2326 descriptor is unusable. Before that, we would close only the first
2327 one leaving the other hanging and let to time out by themselves.
2328 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2330 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2331 - When selecting a v3 rendezvous point, don't only look at the
2332 protover, but also check whether the curve25519 onion key is
2333 present. This way we avoid picking a relay that supports the v3
2334 rendezvous but for which we don't have the microdescriptor. Fixes
2335 bug 27797; bugfix on 0.3.2.1-alpha.
2337 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2338 - Reject protocol names containing bytes other than alphanumeric
2339 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2342 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2343 - Compute protover votes correctly in the rust version of the
2344 protover code. Previously, the protover rewrite in 24031 allowed
2345 repeated votes from the same voter for the same protocol version
2346 to be counted multiple times in protover_compute_vote(). Fixes bug
2347 27649; bugfix on 0.3.3.5-rc.
2348 - Reject protover names that contain invalid characters. Fixes bug
2349 27687; bugfix on 0.3.3.1-alpha.
2351 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2352 - protover_all_supported() would attempt to allocate up to 16GB on
2353 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2354 bugfix on 0.3.3.5-rc.
2356 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2357 - Fix an API mismatch in the rust implementation of
2358 protover_compute_vote(). This bug could have caused crashes on any
2359 directory authorities running Tor with Rust (which we do not yet
2360 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2362 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2363 - Fix a potential null dereference in protover_all_supported(). Add
2364 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2365 - Return a string that can be safely freed by C code, not one
2366 created by the rust allocator, in protover_all_supported(). Fixes
2367 bug 27740; bugfix on 0.3.3.1-alpha.
2369 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2370 - If a unit test running in a subprocess exits abnormally or with a
2371 nonzero status code, treat the test as having failed, even if the
2372 test reported success. Without this fix, memory leaks don't cause
2373 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2374 bugfix on 0.2.2.4-alpha.
2376 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2377 - Make the hs_service tests use the same time source when creating
2378 the introduction point and when testing it. Now tests work better
2379 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2382 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2383 - Treat backtrace test failures as expected on BSD-derived systems
2384 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2385 (FreeBSD failures have been treated as expected since 18204 in
2386 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2389 Changes in version 0.3.5.3-alpha - 2018-10-17
2390 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
2391 versions. One important fix for relays addresses a problem with rate-
2392 limiting code from back in 0.3.4.x: If the fix works out, we'll be
2393 backporting it soon. This release is still an alpha, but we hope it's
2394 getting closer and closer to stability.
2396 o Major features (onion services):
2397 - Version 3 onion services can now use the per-service
2398 HiddenServiceExportCircuitID option to differentiate client
2399 circuits. It communicates with the service by using the HAProxy
2400 protocol to assign virtual IP addresses to inbound client
2401 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
2403 o Major bugfixes (compilation):
2404 - Fix compilation on ARM (and other less-used CPUs) when compiling
2405 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2407 o Major bugfixes (initialization, crash):
2408 - Fix an assertion crash that would stop Tor from starting up if it
2409 tried to activate a periodic event too early. Fixes bug 27861;
2410 bugfix on 0.3.5.1-alpha.
2412 o Major bugfixes (mainloop, bootstrap):
2413 - Make sure Tor bootstraps and works properly if only the
2414 ControlPort is set. Prior to this fix, Tor would only bootstrap
2415 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2416 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2418 o Major bugfixes (relay):
2419 - When our write bandwidth limit is exhausted, stop writing on the
2420 connection. Previously, we had a typo in the code that would make
2421 us stop reading instead, leading to relay connections being stuck
2422 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2425 o Minor features (continuous integration):
2426 - Use the Travis Homebrew addon to install packages on macOS during
2427 Travis CI. The package list is the same, but the Homebrew addon
2428 does not do a `brew update` by default. Implements ticket 27738.
2429 - Report what program produced the mysterious core file that we
2430 occasionally see on Travis CI during make distcheck. Closes
2433 o Minor features (geoip):
2434 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2435 Country database. Closes ticket 27991.
2437 o Minor bugfixes (code safety):
2438 - Rewrite our assertion macros so that they no longer suppress the
2439 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2442 o Minor bugfixes (compilation):
2443 - Compile the ed25519-donna code with a correct declaration of
2444 crypto_strongest_rand(). Previously, we built it with one type,
2445 but linked it against another in the unit tests, which caused
2446 compilation failures with LTO enabled. This could have caused
2447 other undefined behavior in the tests. Fixes bug 27728; bugfix
2450 o Minor bugfixes (compilation, netbsd):
2451 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
2454 o Minor bugfixes (continuous integration, appveyor):
2455 - Install only the necessary mingw packages during our appveyor
2456 builds. This change makes the build a little faster, and prevents
2457 a conflict with a preinstalled mingw openssl that appveyor now
2458 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2460 o Minor bugfixes (directory permissions):
2461 - When a user requests a group-readable DataDirectory, give it to
2462 them. Previously, when the DataDirectory and the CacheDirectory
2463 were the same, the default setting (0) for
2464 CacheDirectoryGroupReadable would override the setting for
2465 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2468 o Minor bugfixes (memory leaks):
2469 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2470 bug 27893; bugfix on 0.3.2.1-alpha.
2472 o Minor bugfixes (networking):
2473 - In retry_listeners_ports(), make sure that we're removing a member
2474 of old_conns smartlist at most once. Fixes bug 27808; bugfix
2476 - Refrain from attempting socket rebinding when old and new
2477 listeners are in different address families. Fixes bug 27928;
2478 bugfix on 0.3.5.1-alpha.
2480 o Minor bugfixes (onion service v3):
2481 - Stop dumping a stack trace when trying to connect to an intro
2482 point without having a descriptor for it. Fixes bug 27774; bugfix
2484 - Don't warn so loudly when Tor is unable to decode an onion
2485 descriptor. This can now happen as a normal use case if a client
2486 gets a descriptor with client authorization but the client is not
2487 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
2488 - When selecting a v3 rendezvous point, don't only look at the
2489 protover, but also check whether the curve25519 onion key is
2490 present. This way we avoid picking a relay that supports the v3
2491 rendezvous but for which we don't have the microdescriptor. Fixes
2492 bug 27797; bugfix on 0.3.2.1-alpha.
2494 o Minor bugfixes (protover):
2495 - Reject protocol names containing bytes other than alphanumeric
2496 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2499 o Minor bugfixes (testing):
2500 - Make the hs_service tests use the same time source when creating
2501 the introduction point and when testing it. Now tests work better
2502 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2504 - In test_rebind.py, check if the Python version is in the supported
2505 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
2507 o Code simplification and refactoring:
2508 - Divide more large Tor source files -- especially ones that span
2509 multiple areas of functionality -- into smaller parts, including
2510 onion.c and main.c. Closes ticket 26747.
2511 - Divide the "routerparse.c" module into separate modules for each
2512 group of parsed objects. Closes ticket 27924.
2513 - Move protover_rust.c to the same place protover.c was moved to.
2514 Closes ticket 27814.
2515 - Split directory.c into separate pieces for client, server, and
2516 common functionality. Closes ticket 26744.
2517 - Split the non-statistics-related parts from the rephist.c and
2518 geoip.c modules. Closes ticket 27892.
2519 - Split the router.c file into relay-only and shared components, to
2520 help with future modularization. Closes ticket 27864.
2523 - In the tor-resolve(1) manpage, fix the reference to socks-
2524 extensions.txt by adding a web URL. Resolves ticket 27853.
2525 - Mention that we require Python to be 2.7 or newer for some
2526 integration tests that we ship with Tor. Resolves ticket 27677.
2529 Changes in version 0.3.5.2-alpha - 2018-09-21
2530 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
2531 that made Tor think it had run out of sockets. Anybody running a relay
2532 or an onion service on 0.3.5.1-alpha should upgrade.
2534 o Major bugfixes (relay bandwidth statistics):
2535 - When we close relayed circuits, report the data in the circuit
2536 queues as being written in our relay bandwidth stats. This
2537 mitigates guard discovery and other attacks that close circuits
2538 for the explicit purpose of noticing this discrepancy in
2539 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
2541 o Major bugfixes (socket accounting):
2542 - In our socket accounting code, count a socket as closed even when
2543 it is closed indirectly by the TLS layer. Previously, we would
2544 count these sockets as still in use, and incorrectly believe that
2545 we had run out of sockets. Fixes bug 27795; bugfix
2548 o Minor bugfixes (32-bit OSX and iOS, timing):
2549 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2550 difference algorithm for 32-bit Apple platforms. Previously, it
2551 would overflow when calculating the difference between two times
2552 more than 47 days apart. Fixes part of bug 27139; bugfix
2554 - Improve the precision of our 32-bit millisecond difference
2555 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2556 bugfix on 0.3.4.1-alpha.
2557 - Relax the tolerance on the mainloop/update_time_jumps test when
2558 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2561 o Minor bugfixes (onion service v3):
2562 - Close all SOCKS request (for the same .onion) if the newly fetched
2563 descriptor is unusable. Before that, we would close only the first
2564 one leaving the other hanging and let to time out by themselves.
2565 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2567 o Minor bugfixes (memory leak):
2568 - Fix an unlikely memory leak when trying to read a private key from
2569 a ridiculously large file. Fixes bug 27764; bugfix on
2570 0.3.5.1-alpha. This is CID 1439488.
2572 o Minor bugfixes (NSS):
2573 - Correctly detect failure to open a dummy TCP socket when stealing
2574 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
2577 o Minor bugfixes (rust):
2578 - protover_all_supported() would attempt to allocate up to 16GB on
2579 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2580 bugfix on 0.3.3.5-rc.
2582 o Minor bugfixes (testing):
2583 - Revise the "conditionvar_timeout" test so that it succeeds even on
2584 heavily loaded systems where the test threads are not scheduled
2585 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2587 o Code simplification and refactoring:
2588 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2589 Closes ticket 27799.
2592 Changes in version 0.3.5.1-alpha - 2018-09-18
2593 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
2594 client authorization for modern (v3) onion services, improves
2595 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
2596 support for NSS in place of OpenSSL, and much more.
2598 o Major features (onion services, UI change):
2599 - For a newly created onion service, the default version is now 3.
2600 Tor still supports existing version 2 services, but the operator
2601 now needs to set "HiddenServiceVersion 2" in order to create a new
2602 version 2 service. For existing services, Tor now learns the
2603 version by reading the key file. Closes ticket 27215.
2605 o Major features (relay, UI change):
2606 - Relays no longer run as exits by default. If the "ExitRelay"
2607 option is auto (or unset), and no exit policy is specified with
2608 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
2609 Previously in this case, we allowed exit traffic and logged a
2610 warning message. Closes ticket 21530. Patch by Neel Chauhan.
2611 - Tor now validates that the ContactInfo config option is valid UTF-
2612 8 when parsing torrc. Closes ticket 27428.
2614 o Major features (bootstrap):
2615 - Don't report directory progress until after a connection to a
2616 relay or bridge has succeeded. Previously, we'd report 80%
2617 progress based on cached directory information when we couldn't
2618 even connect to the network. Closes ticket 27169.
2620 o Major features (new code layout):
2621 - Nearly all of Tor's source code has been moved around into more
2622 logical places. The "common" directory is now divided into a set
2623 of libraries in "lib", and files in the "or" directory have been
2624 split into "core" (logic absolutely needed for onion routing),
2625 "feature" (independent modules in Tor), and "app" (to configure
2626 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
2627 more information. Closes ticket 26481.
2629 This refactoring is not complete: although the libraries have been
2630 refactored to be acyclic, the main body of Tor is still too
2631 interconnected. We will attempt to improve this in the future.
2633 o Major features (onion services v3):
2634 - Implement onion service client authorization at the descriptor
2635 level: only authorized clients can decrypt a service's descriptor
2636 to find out how to contact it. A new torrc option was added to
2637 control this client side: ClientOnionAuthDir <path>. On the
2638 service side, if the "authorized_clients/" directory exists in the
2639 onion service directory path, client configurations are read from
2640 the files within. See the manpage for more details. Closes ticket
2641 27547. Patch done by Suphanat Chunhapanya (haxxpop).
2642 - Improve revision counter generation in next-gen onion services.
2643 Onion services can now scale by hosting multiple instances on
2644 different hosts without synchronization between them, which was
2645 previously impossible because descriptors would get rejected by
2646 HSDirs. Addresses ticket 25552.
2648 o Major features (portability, cryptography, experimental, TLS):
2649 - Tor now has the option to compile with the NSS library instead of
2650 OpenSSL. This feature is experimental, and we expect that bugs may
2651 remain. It is mainly intended for environments where Tor's
2652 performance is not CPU-bound, and where NSS is already known to be
2653 installed. To try it out, configure Tor with the --enable-nss
2654 flag. Closes tickets 26631, 26815, and 26816.
2656 If you are experimenting with this option and using an old cached
2657 consensus, Tor may fail to start. To solve this, delete your
2658 "cached-consensus" and "cached-microdesc-consensus" files,
2659 (if present), and restart Tor.
2661 o Major bugfixes (directory authority):
2662 - Actually check that the address we get from DirAuthority
2663 configuration line is valid IPv4. Explicitly disallow DirAuthority
2664 address to be a DNS hostname. Fixes bug 26488; bugfix
2667 o Major bugfixes (restart-in-process):
2668 - Fix a use-after-free error that could be caused by passing Tor an
2669 impossible set of options that would fail during options_act().
2670 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2672 o Minor features (admin tools):
2673 - Add a new --key-expiration option to print the expiration date of
2674 the signing cert in an ed25519_signing_cert file. Resolves
2677 o Minor features (build):
2678 - If you pass the "--enable-pic" option to configure, Tor will try
2679 to tell the compiler to build position-independent code suitable
2680 to link into a dynamic library. (The default remains -fPIE, for
2681 code suitable for a relocatable executable.) Closes ticket 23846.
2683 o Minor features (code correctness, testing):
2684 - Tor's build process now includes a "check-includes" make target to
2685 verify that no module of Tor relies on any headers from a higher-
2686 level module. We hope to use this feature over time to help
2687 refactor our codebase. Closes ticket 26447.
2689 o Minor features (code layout):
2690 - We have a new "lowest-level" error-handling API for use by code
2691 invoked from within the logging module. With this interface, the
2692 logging code is no longer at risk of calling into itself if a
2693 failure occurs while it is trying to log something. Closes
2696 o Minor features (compilation):
2697 - Tor's configure script now supports a --with-malloc= option to
2698 select your malloc implementation. Supported options are
2699 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
2700 default). Addresses part of ticket 20424. Based on a patch from
2703 o Minor features (config):
2704 - The "auto" keyword in torrc is now case-insensitive. Closes
2707 o Minor features (continuous integration):
2708 - Don't do a distcheck with --disable-module-dirauth in Travis.
2709 Implements ticket 27252.
2710 - Install libcap-dev and libseccomp2-dev so these optional
2711 dependencies get tested on Travis CI. Closes ticket 26560.
2712 - Only run one online rust build in Travis, to reduce network
2713 errors. Skip offline rust builds on Travis for Linux gcc, because
2714 they're redundant. Implements ticket 27252.
2715 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2716 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2717 Linux with default settings, because all the non-default builds
2718 use gcc on Linux. Implements ticket 27252.
2720 o Minor features (controller):
2721 - Emit CIRC_BW events as soon as we detect that we processed an
2722 invalid or otherwise dropped cell on a circuit. This allows
2723 vanguards and other controllers to react more quickly to dropped
2724 cells. Closes ticket 27678.
2725 - For purposes of CIRC_BW-based dropped cell detection, track half-
2726 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2727 bias check cells to arrive without counting it as dropped until
2728 either the END arrives, or the windows are empty. Closes
2730 - Implement a 'GETINFO md/all' controller command to enable getting
2731 all known microdescriptors. Closes ticket 8323.
2732 - The GETINFO command now support an "uptime" argument, to return
2733 Tor's uptime in seconds. Closes ticket 25132.
2735 o Minor features (denial-of-service avoidance):
2736 - Make our OOM handler aware of the DNS cache so that it doesn't
2737 fill up the memory. This check is important for our DoS mitigation
2738 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2740 o Minor features (development):
2741 - Tor's makefile now supports running the "clippy" Rust style tool
2742 on our Rust code. Closes ticket 22156.
2744 o Minor features (directory authority):
2745 - There is no longer an artificial upper limit on the length of
2746 bandwidth lines. Closes ticket 26223.
2747 - When a bandwidth file is used to obtain the bandwidth measurements,
2748 include this bandwidth file headers in the votes. Closes
2750 - Improved support for networks with only a single authority or a
2751 single fallback directory. Patch from Gabriel Somlo. Closes
2754 o Minor features (embedding API):
2755 - The Tor controller API now supports a function to launch Tor with
2756 a preconstructed owning controller FD, so that embedding
2757 applications don't need to manage controller ports and
2758 authentication. Closes ticket 24204.
2759 - The Tor controller API now has a function that returns the name
2760 and version of the backend implementing the API. Closes
2763 o Minor features (geoip):
2764 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2765 Country database. Closes ticket 27631.
2767 o Minor features (memory management):
2768 - Get Libevent to use the same memory allocator as Tor, by calling
2769 event_set_mem_functions() during initialization. Resolves
2772 o Minor features (memory usage):
2773 - When not using them, store legacy TAP public onion keys in DER-
2774 encoded format, rather than as expanded public keys. This should
2775 save several megabytes on typical clients. Closes ticket 27246.
2777 o Minor features (OpenSSL):
2778 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2779 than our own. Resolves ticket 19979.
2781 o Minor features (Rust, code quality):
2782 - Improve rust code quality in the rust protover implementation by
2783 making it more idiomatic. Includes changing an internal API to
2784 take &str instead of &String. Closes ticket 26492.
2786 o Minor features (testing):
2787 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2788 chutney. Implements ticket 27211.
2790 o Minor features (tor-resolve):
2791 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2792 Side-effect of the refactoring for ticket 26526.
2794 o Minor features (UI):
2795 - Log each included configuration file or directory as we read it,
2796 to provide more visibility about where Tor is reading from. Patch
2797 from Unto Sten; closes ticket 27186.
2798 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2799 Closes ticket 26703.
2801 o Minor bugfixes (bootstrap):
2802 - Try harder to get descriptors in non-exit test networks, by using
2803 the mid weight for the third hop when there are no exits. Fixes
2804 bug 27237; bugfix on 0.2.6.2-alpha.
2806 o Minor bugfixes (C correctness):
2807 - Avoid casting smartlist index to int implicitly, as it may trigger
2808 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2809 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2810 - Use time_t for all values in
2811 predicted_ports_prediction_time_remaining(). Rework the code that
2812 computes difference between durations/timestamps. Fixes bug 27165;
2813 bugfix on 0.3.1.1-alpha.
2815 o Minor bugfixes (client, memory usage):
2816 - When not running as a directory cache, there is no need to store
2817 the text of the current consensus networkstatus in RAM.
2818 Previously, however, clients would store it anyway, at a cost of
2819 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2822 o Minor bugfixes (client, reachableaddresses):
2823 - Instead of adding a "reject *:*" line to ReachableAddresses when
2824 loading the configuration, add one to the policy after parsing it
2825 in parse_reachable_addresses(). This prevents extra "reject *.*"
2826 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2827 0.1.1.5-alpha. Patch by Neel Chauhan.
2829 o Minor bugfixes (code quality):
2830 - Rename sandbox_getaddrinfo() and other functions to no longer
2831 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2832 bugfix on 0.2.7.1-alpha.
2834 o Minor bugfixes (configuration, Onion Services):
2835 - In rend_service_parse_port_config(), disallow any input to remain
2836 after address-port pair was parsed. This will catch address and
2837 port being whitespace-separated by mistake of the user. Fixes bug
2838 27044; bugfix on 0.2.9.10.
2840 o Minor bugfixes (continuous integration):
2841 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2842 27464; bugfix on 0.3.4.1-alpha.
2844 o Minor bugfixes (controller):
2845 - Consider all routerinfo errors other than "not a server" to be
2846 transient for the purpose of "GETINFO exit-policy/*" controller
2847 request. Print stacktrace in the unlikely case of failing to
2848 recompute routerinfo digest. Fixes bug 27034; bugfix
2851 o Minor bugfixes (directory connection shutdown):
2852 - Avoid a double-close when shutting down a stalled directory
2853 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2855 o Minor bugfixes (HTTP tunnel):
2856 - Fix a bug warning when closing an HTTP tunnel connection due to an
2857 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2860 o Minor bugfixes (ipv6):
2861 - In addrs_in_same_network_family(), we choose the subnet size based
2862 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2863 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2864 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2866 o Minor bugfixes (logging):
2867 - As a precaution, do an early return from log_addr_has_changed() if
2868 Tor is running as client. Also, log a stack trace for debugging as
2869 this function should only be called when Tor runs as server. Fixes
2870 bug 26892; bugfix on 0.1.1.9-alpha.
2871 - Refrain from mentioning bug 21018 in the logs, as it is already
2872 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2874 o Minor bugfixes (logging, documentation):
2875 - When SafeLogging is enabled, scrub IP address in
2876 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2877 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2878 bug 26882; bugfix on 0.2.4.10-alpha.
2880 o Minor bugfixes (netflow padding):
2881 - Ensure circuitmux queues are empty before scheduling or sending
2882 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2884 o Minor bugfixes (onion service v2):
2885 - Log at level "info", not "warning", in the case that we do not
2886 have a consensus when a .onion request comes in. This can happen
2887 normally while bootstrapping. Fixes bug 27040; bugfix
2890 o Minor bugfixes (onion service v3):
2891 - When the onion service directory can't be created or has the wrong
2892 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2895 o Minor bugfixes (OS compatibility):
2896 - Properly handle configuration changes that move a listener to/from
2897 wildcard IP address. If the first attempt to bind a socket fails,
2898 close the old listener and try binding the socket again. Fixes bug
2899 17873; bugfix on 0.0.8pre-1.
2901 o Minor bugfixes (performance)::
2902 - Rework node_is_a_configured_bridge() to no longer call
2903 node_get_all_orports(), which was performing too many memory
2904 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2906 o Minor bugfixes (relay statistics):
2907 - Update relay descriptor on bandwidth changes only when the uptime
2908 is smaller than 24h, in order to reduce the efficiency of guard
2909 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2911 o Minor bugfixes (relays):
2912 - Consider the fact that we'll be making direct connections to our
2913 entry and guard nodes when computing the fraction of nodes that
2914 have their descriptors. Also, if we are using bridges and there is
2915 at least one bridge with a full descriptor, treat the fraction of
2916 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2917 Patch by Neel Chauhan.
2918 - Update the message logged on relays when DirCache is disabled.
2919 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2920 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
2922 o Minor bugfixes (rust, protover):
2923 - Compute protover votes correctly in the rust version of the
2924 protover code. Previously, the protover rewrite in 24031 allowed
2925 repeated votes from the same voter for the same protocol version
2926 to be counted multiple times in protover_compute_vote(). Fixes bug
2927 27649; bugfix on 0.3.3.5-rc.
2928 - Reject protover names that contain invalid characters. Fixes bug
2929 27687; bugfix on 0.3.3.1-alpha.
2931 o Minor bugfixes (testing):
2932 - Fix two unit tests to work when HOME environment variable is not
2933 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
2934 - If a unit test running in a subprocess exits abnormally or with a
2935 nonzero status code, treat the test as having failed, even if the
2936 test reported success. Without this fix, memory leaks don't cause
2937 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2938 bugfix on 0.2.2.4-alpha.
2939 - When logging a version mismatch in our openssl_version tests,
2940 report the actual offending version strings. Fixes bug 26152;
2941 bugfix on 0.2.9.1-alpha.
2942 - Fix forking tests on Windows when there is a space somewhere in
2943 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
2945 o Code simplification and refactoring:
2946 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
2947 longer needed. Closes ticket 26502.
2948 - Include paths to header files within Tor are now qualified by
2949 directory within the top-level src directory.
2950 - Many structures have been removed from the centralized "or.h"
2951 header, and moved into their own headers. This will allow us to
2952 reduce the number of places in the code that rely on each
2953 structure's contents and layout. Closes ticket 26383.
2954 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
2955 - Remove GetAdaptersAddresses_fn_t. The code that used it was
2956 removed as part of the 26481 refactor. Closes ticket 27467.
2957 - Rework Tor SOCKS server code to use Trunnel and benefit from
2958 autogenerated functions for parsing and generating SOCKS wire
2959 format. New implementation is cleaner, more maintainable and
2960 should be less prone to heartbleed-style vulnerabilities.
2961 Implements a significant fraction of ticket 3569.
2962 - Split sampled_guards_update_from_consensus() and
2963 select_entry_guard_for_circuit() into subfunctions. In
2964 entry_guards_update_primary() unite three smartlist enumerations
2965 into one and move smartlist comparison code out of the function.
2966 Closes ticket 21349.
2967 - Tor now assumes that you have standards-conformant stdint.h and
2968 inttypes.h headers when compiling. Closes ticket 26626.
2969 - Unify our bloom filter logic. Previously we had two copies of this
2970 code: one for routerlist filtering, and one for address set
2971 calculations. Closes ticket 26510.
2972 - Use the simpler strcmpstart() helper in
2973 rend_parse_v2_service_descriptor instead of strncmp(). Closes
2975 - Utility functions that can perform a DNS lookup are now wholly
2976 separated from those that can't, in separate headers and C
2977 modules. Closes ticket 26526.
2980 - Copy paragraph and URL to Tor's code of conduct document from
2981 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
2982 - Remove old instructions from INSTALL document. Closes ticket 26588.
2983 - Warn users that they should not include MyFamily line(s) in their
2984 torrc when running Tor bridge. Closes ticket 26908.
2987 - Tor no longer supports building with the dmalloc library. For
2988 debugging memory issues, we suggest using gperftools or msan
2989 instead. Closes ticket 26426.
2990 - Tor no longer attempts to run on Windows environments without the
2991 GetAdaptersAddresses() function. This function has existed since
2992 Windows XP, which is itself already older than we support.
2993 - Remove Tor2web functionality for version 2 onion services. The
2994 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
2995 (This feature was never shipped in vanilla Tor and it was only
2996 possible to use this feature by building the support at compile
2997 time. Tor2webMode is not implemented for version 3 onion services.)
2998 Closes ticket 26367.
3001 Changes in version 0.2.9.17 - 2018-09-10
3002 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
3004 o Minor features (compatibility, backport from 0.3.4.8):
3005 - Tell OpenSSL to maintain backward compatibility with previous
3006 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3007 ciphers are disabled by default. Closes ticket 27344.
3009 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3010 - Enable macOS builds in our Travis CI configuration. Closes
3012 - Install libcap-dev and libseccomp2-dev so these optional
3013 dependencies get tested on Travis CI. Closes ticket 26560.
3014 - Run asciidoc during Travis CI. Implements ticket 27087.
3015 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3017 o Minor features (geoip):
3018 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3019 Country database. Closes ticket 27089.
3021 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3022 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3023 tell the compiler not to include the system malloc implementation.
3024 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3026 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3027 - Silence a spurious compiler warning on the GetAdaptersAddresses
3028 function pointer cast. This issue is already fixed by 26481 in
3029 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3030 bugfix on 0.2.3.11-alpha.
3031 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3032 supported, and always fails. Some compilers warn about the
3033 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3036 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3037 - Don't link or search for pthreads when building for Windows, even
3038 if we are using build environment (like mingw) that provides a
3039 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3041 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3042 - Skip a pair of unreliable key generation tests on Windows, until
3043 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3044 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3046 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3047 - Pass the module flags to distcheck configure, and log the flags
3048 before running configure. (Backported to 0.2.9 and later as a
3049 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3051 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3052 - When a Travis build fails, and showing a log fails, keep trying to
3053 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3054 - When we use echo in Travis, don't pass a --flag as the first
3055 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3057 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3058 - When voting for recommended versions, make sure that all of the
3059 versions are well-formed and parsable. Fixes bug 26485; bugfix
3062 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3063 - Fix a bug in out sandboxing rules for the openat() syscall.
3064 Previously, no openat() call would be permitted, which would break
3065 filesystem operations on recent glibc versions. Fixes bug 25440;
3066 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3068 o Minor bugfixes (onion services, backport from 0.3.4.8):
3069 - Silence a spurious compiler warning in
3070 rend_client_send_introduction(). Fixes bug 27463; bugfix
3073 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3074 - Log a protocol warning when single onion services or Tor2web clients
3075 fail to authenticate direct connections to relays.
3076 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3078 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3079 - Disable core dumps in test_bt.sh, to avoid failures in "make
3080 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3082 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3083 - Before running make test-network-all, delete old logs and test
3084 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3087 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3088 - Our "tortls/cert_matches_key" unit test no longer relies on
3089 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3090 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3091 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3093 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3094 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3095 27185; bugfix on 0.2.2.2-alpha.
3098 Changes in version 0.3.2.12 - 2018-09-10
3099 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
3101 o Minor features (compatibility, backport from 0.3.4.8):
3102 - Tell OpenSSL to maintain backward compatibility with previous
3103 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3104 ciphers are disabled by default. Closes ticket 27344.
3106 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3107 - Enable macOS builds in our Travis CI configuration. Closes
3109 - Install libcap-dev and libseccomp2-dev so these optional
3110 dependencies get tested on Travis CI. Closes ticket 26560.
3111 - Run asciidoc during Travis CI. Implements ticket 27087.
3112 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3114 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3115 - Use cargo cache in our Travis CI configuration. Closes
3118 o Minor features (controller, backport from 0.3.4.6-rc):
3119 - The control port now exposes the list of HTTPTunnelPorts and
3120 ExtOrPorts via GETINFO net/listeners/httptunnel and
3121 net/listeners/extor respectively. Closes ticket 26647.
3123 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3124 - Authorities no longer vote to make the subprotocol version
3125 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3126 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3128 o Minor features (geoip):
3129 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3130 Country database. Closes ticket 27089.
3132 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3133 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3134 tell the compiler not to include the system malloc implementation.
3135 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3136 - Don't try to use a pragma to temporarily disable the
3137 -Wunused-const-variable warning if the compiler doesn't support
3138 it. Fixes bug 26785; bugfix on 0.3.2.11.
3140 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3141 - Silence a spurious compiler warning on the GetAdaptersAddresses
3142 function pointer cast. This issue is already fixed by 26481 in
3143 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3144 bugfix on 0.2.3.11-alpha.
3145 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3146 supported, and always fails. Some compilers warn about the
3147 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3150 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3151 - Don't link or search for pthreads when building for Windows, even
3152 if we are using build environment (like mingw) that provides a
3153 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3155 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3156 - Skip a pair of unreliable key generation tests on Windows, until
3157 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3158 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3160 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3161 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3162 - Pass the module flags to distcheck configure, and log the flags
3163 before running configure. (Backported to 0.2.9 and later as a
3164 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3166 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3167 - When a Travis build fails, and showing a log fails, keep trying to
3168 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3169 - When we use echo in Travis, don't pass a --flag as the first
3170 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3172 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3173 - When voting for recommended versions, make sure that all of the
3174 versions are well-formed and parsable. Fixes bug 26485; bugfix
3177 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3178 - Fix a bug in out sandboxing rules for the openat() syscall.
3179 Previously, no openat() call would be permitted, which would break
3180 filesystem operations on recent glibc versions. Fixes bug 25440;
3181 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3183 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3184 - Improve the log message when connection initiators fail to
3185 authenticate direct connections to relays. Fixes bug 26927; bugfix
3188 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3189 - Fix bug that causes services to not ever rotate their descriptors
3190 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3193 o Minor bugfixes (onion services, backport from 0.3.4.8):
3194 - Silence a spurious compiler warning in
3195 rend_client_send_introduction(). Fixes bug 27463; bugfix
3198 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3199 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3201 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3202 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3203 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3204 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3206 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3207 - Log a protocol warning when single onion services or Tor2web clients
3208 fail to authenticate direct connections to relays.
3209 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3211 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3212 - Disable core dumps in test_bt.sh, to avoid failures in "make
3213 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3215 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3216 - When running make test-network-all, use the mixed+hs-v2 network.
3217 (A previous fix to chutney removed v3 onion services from the
3218 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3219 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3220 - Before running make test-network-all, delete old logs and test
3221 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3224 o Minor bugfixes (testing, openssl compatibility):
3225 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
3226 internals. Previously, it relied on unsupported OpenSSL behavior in
3227 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
3228 bugfix on 0.2.5.1-alpha.
3230 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3231 - Our "tortls/cert_matches_key" unit test no longer relies on
3232 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3233 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3234 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3236 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3237 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3238 27185; bugfix on 0.2.2.2-alpha.
3241 Changes in version 0.3.3.10 - 2018-09-10
3242 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
3244 o Minor features (bug workaround, backport from 0.3.4.7-rc):
3245 - Compile correctly on systems that provide the C11 stdatomic.h
3246 header, but where C11 atomic functions don't actually compile.
3247 Closes ticket 26779; workaround for Debian issue 903709.
3249 o Minor features (compatibility, backport from 0.3.4.8):
3250 - Tell OpenSSL to maintain backward compatibility with previous
3251 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3252 ciphers are disabled by default. Closes ticket 27344.
3254 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3255 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3256 - Enable macOS builds in our Travis CI configuration. Closes
3258 - Install libcap-dev and libseccomp2-dev so these optional
3259 dependencies get tested on Travis CI. Closes ticket 26560.
3260 - Run asciidoc during Travis CI. Implements ticket 27087.
3261 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3263 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3264 - Use cargo cache in our Travis CI configuration. Closes
3267 o Minor features (controller, backport from 0.3.4.6-rc):
3268 - The control port now exposes the list of HTTPTunnelPorts and
3269 ExtOrPorts via GETINFO net/listeners/httptunnel and
3270 net/listeners/extor respectively. Closes ticket 26647.
3272 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3273 - Authorities no longer vote to make the subprotocol version
3274 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3275 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3277 o Minor features (geoip):
3278 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3279 Country database. Closes ticket 27089.
3281 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3282 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3283 tell the compiler not to include the system malloc implementation.
3284 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3285 - Don't try to use a pragma to temporarily disable the
3286 -Wunused-const-variable warning if the compiler doesn't support
3287 it. Fixes bug 26785; bugfix on 0.3.2.11.
3289 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3290 - Silence a spurious compiler warning on the GetAdaptersAddresses
3291 function pointer cast. This issue is already fixed by 26481 in
3292 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3293 bugfix on 0.2.3.11-alpha.
3294 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3295 supported, and always fails. Some compilers warn about the
3296 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3299 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3300 - Don't link or search for pthreads when building for Windows, even
3301 if we are using build environment (like mingw) that provides a
3302 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3304 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3305 - Skip a pair of unreliable key generation tests on Windows, until
3306 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3307 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3309 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3310 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3311 - Pass the module flags to distcheck configure, and log the flags
3312 before running configure. (Backported to 0.2.9 and later as a
3313 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3315 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3316 - When a Travis build fails, and showing a log fails, keep trying to
3317 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3318 - When we use echo in Travis, don't pass a --flag as the first
3319 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3321 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3322 - When voting for recommended versions, make sure that all of the
3323 versions are well-formed and parsable. Fixes bug 26485; bugfix
3326 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
3327 - Always call tor_free_all() when leaving tor_run_main(). When we
3328 did not, restarting tor in-process would cause an assertion
3329 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3331 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3332 - Fix a bug in our sandboxing rules for the openat() syscall.
3333 Previously, no openat() call would be permitted, which would break
3334 filesystem operations on recent glibc versions. Fixes bug 25440;
3335 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3337 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3338 - Improve the log message when connection initiators fail to
3339 authenticate direct connections to relays. Fixes bug 26927; bugfix
3342 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3343 - Fix bug that causes services to not ever rotate their descriptors
3344 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3347 o Minor bugfixes (onion services, backport from 0.3.4.8):
3348 - Silence a spurious compiler warning in
3349 rend_client_send_introduction(). Fixes bug 27463; bugfix
3352 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
3353 - Work around two different bugs in the OS X 10.10 and later SDKs
3354 that would prevent us from successfully targeting earlier versions
3355 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3357 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
3358 - Fix compilation of the unit tests on GNU/Hurd, which does not
3359 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3362 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3363 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3365 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3366 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3367 - Protover parsing was accepting the presence of whitespace in
3368 version strings, which the C implementation would choke on, e.g.
3369 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3370 - Protover parsing was ignoring a 2nd hyphen and everything after
3371 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3373 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3374 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3375 - cd to ${abs_top_builddir}/src/rust before running cargo in
3376 src/test/test_rust.sh. This makes the working directory consistent
3377 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3379 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3380 - Log a protocol warning when single onion services or Tor2web clients
3381 fail to authenticate direct connections to relays.
3382 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3384 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3385 - Disable core dumps in test_bt.sh, to avoid failures in "make
3386 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3388 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3389 - When running make test-network-all, use the mixed+hs-v2 network.
3390 (A previous fix to chutney removed v3 onion services from the
3391 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3392 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3393 - Before running make test-network-all, delete old logs and test
3394 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3397 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3398 - Our "tortls/cert_matches_key" unit test no longer relies on
3399 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3400 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3401 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3403 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3404 - Stop sending ed25519 link specifiers in v3 onion service introduce
3405 cells and descriptors, when the rendezvous or introduction point
3406 doesn't support ed25519 link authentication. Fixes bug 26627;
3407 bugfix on 0.3.2.4-alpha.
3409 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3410 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3411 27185; bugfix on 0.2.2.2-alpha.
3414 Changes in version 0.3.4.8 - 2018-09-10
3415 Tor 0.3.4.8 is the first stable release in its series; it includes
3416 compilation and portability fixes.
3418 The Tor 0.3.4 series includes improvements for running Tor in
3419 low-power and embedded environments, which should help performance in
3420 general. We've begun work on better modularity, and included preliminary
3421 changes on the directory authority side to accommodate a new bandwidth
3422 measurement system. We've also integrated more continuous-integration
3423 systems into our development process, and made corresponding changes to
3424 Tor's testing infrastructure. Finally, we've continued to refine
3425 our anti-denial-of-service code.
3427 Below are the changes since 0.3.4.7-rc. For a complete list of changes
3428 since 0.3.3.9, see the ReleaseNotes file.
3430 o Minor features (compatibility):
3431 - Tell OpenSSL to maintain backward compatibility with previous
3432 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3433 ciphers are disabled by default. Closes ticket 27344.
3435 o Minor features (continuous integration):
3436 - Log the compiler path and version during Appveyor builds.
3437 Implements ticket 27449.
3438 - Show config.log and test-suite.log after failed Appveyor builds.
3439 Also upload the zipped full logs as a build artifact. Implements
3442 o Minor bugfixes (compilation):
3443 - Silence a spurious compiler warning on the GetAdaptersAddresses
3444 function pointer cast. This issue is already fixed by 26481 in
3445 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3446 bugfix on 0.2.3.11-alpha.
3447 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3448 supported, and always fails. Some compilers warn about the
3449 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3452 o Minor bugfixes (continuous integration):
3453 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
3454 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
3455 Executables compiled for 64-bit Windows with this version of gcc
3456 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
3457 27460; bugfix on 0.3.4.1-alpha.
3458 - When a Travis build fails, and showing a log fails, keep trying to
3459 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3460 - When we use echo in Travis, don't pass a --flag as the first
3461 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3463 o Minor bugfixes (onion services):
3464 - Silence a spurious compiler warning in
3465 rend_client_send_introduction(). Fixes bug 27463; bugfix
3468 o Minor bugfixes (testing, chutney):
3469 - When running make test-network-all, use the mixed+hs-v2 network.
3470 (A previous fix to chutney removed v3 onion services from the
3471 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3472 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3473 - Before running make test-network-all, delete old logs and test
3474 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3477 Changes in version 0.3.4.7-rc - 2018-08-24
3478 Tor 0.3.4.7-rc fixes several small compilation, portability, and
3479 correctness issues in previous versions of Tor. This version is a
3480 release candidate: if no serious bugs are found, we expect that the
3481 stable 0.3.4 release will be (almost) the same as this release.
3483 o Minor features (bug workaround):
3484 - Compile correctly on systems that provide the C11 stdatomic.h
3485 header, but where C11 atomic functions don't actually compile.
3486 Closes ticket 26779; workaround for Debian issue 903709.
3488 o Minor features (continuous integration):
3489 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3490 - Enable macOS builds in our Travis CI configuration. Closes
3492 - Install libcap-dev and libseccomp2-dev so these optional
3493 dependencies get tested on Travis CI. Closes ticket 26560.
3494 - Only post Appveyor IRC notifications when the build fails.
3495 Implements ticket 27275.
3496 - Run asciidoc during Travis CI. Implements ticket 27087.
3497 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3499 o Minor features (continuous integration, rust):
3500 - Use cargo cache in our Travis CI configuration. Closes
3503 o Minor features (directory authorities):
3504 - Authorities no longer vote to make the subprotocol version
3505 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3506 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3508 o Minor features (geoip):
3509 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3510 Country database. Closes ticket 27089.
3512 o Minor bugfixes (compilation, windows):
3513 - Don't link or search for pthreads when building for Windows, even
3514 if we are using build environment (like mingw) that provides a
3515 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3517 o Minor bugfixes (continuous integration):
3518 - Improve Appveyor CI IRC logging. Generate correct branches and
3519 URLs for pull requests and tags. Use unambiguous short commits.
3520 Fixes bug 26979; bugfix on master.
3521 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3522 - Pass the module flags to distcheck configure, and log the flags
3523 before running configure. (Backported to 0.2.9 and later as a
3524 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3526 o Minor bugfixes (in-process restart):
3527 - Always call tor_free_all() when leaving tor_run_main(). When we
3528 did not, restarting tor in-process would cause an assertion
3529 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3531 o Minor bugfixes (linux seccomp2 sandbox):
3532 - Fix a bug in out sandboxing rules for the openat() syscall.
3533 Previously, no openat() call would be permitted, which would break
3534 filesystem operations on recent glibc versions. Fixes bug 25440;
3535 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3537 o Minor bugfixes (onion services):
3538 - Fix bug that causes services to not ever rotate their descriptors
3539 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3542 o Minor bugfixes (portability):
3543 - Fix compilation of the unit tests on GNU/Hurd, which does not
3544 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3547 o Minor bugfixes (rust):
3548 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3550 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3551 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3552 - Protover parsing was accepting the presence of whitespace in
3553 version strings, which the C implementation would choke on, e.g.
3554 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3555 - Protover parsing was ignoring a 2nd hyphen and everything after
3556 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3558 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3559 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3560 - cd to ${abs_top_builddir}/src/rust before running cargo in
3561 src/test/test_rust.sh. This makes the working directory consistent
3562 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3564 o Minor bugfixes (testing, bootstrap):
3565 - When calculating bootstrap progress, check exit policies and the
3566 exit flag. Previously, Tor would only check the exit flag, which
3567 caused race conditions in small and fast networks like chutney.
3568 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3570 o Minor bugfixes (testing, openssl compatibility):
3571 - Our "tortls/cert_matches_key" unit test no longer relies on
3572 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3573 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3574 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3576 o Minor bugfixes (Windows, compilation):
3577 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3578 27185; bugfix on 0.2.2.2-alpha.
3581 Changes in version 0.3.4.6-rc - 2018-08-06
3582 Tor 0.3.4.6-rc fixes several small compilation, portability, and
3583 correctness issues in previous versions of Tor. This version is a
3584 release candidate: if no serious bugs are found, we expect that the
3585 stable 0.3.4 release will be (almost) the same as this release.
3587 o Major bugfixes (event scheduler):
3588 - When we enable a periodic event, schedule it in the event loop
3589 rather than running it immediately. Previously, we would re-run
3590 periodic events immediately in the middle of (for example)
3591 changing our options, with unpredictable effects. Fixes bug 27003;
3592 bugfix on 0.3.4.1-alpha.
3594 o Minor features (compilation):
3595 - When building Tor, prefer to use Python 3 over Python 2, and more
3596 recent (contemplated) versions over older ones. Closes
3598 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3599 tell the compiler not to include the system malloc implementation.
3600 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3601 - Don't try to use a pragma to temporarily disable the
3602 -Wunused-const-variable warning if the compiler doesn't support
3603 it. Fixes bug 26785; bugfix on 0.3.2.11.
3605 o Minor bugfixes (continuous integration):
3606 - Skip a pair of unreliable key generation tests on Windows, until
3607 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3608 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3610 o Minor features (controller):
3611 - The control port now exposes the list of HTTPTunnelPorts and
3612 ExtOrPorts via GETINFO net/listeners/httptunnel and
3613 net/listeners/extor respectively. Closes ticket 26647.
3615 o Minor bugfixes (directory authority):
3616 - When voting for recommended versions, make sure that all of the
3617 versions are well-formed and parsable. Fixes bug 26485; bugfix
3620 o Minor features (geoip):
3621 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3622 Country database. Closes ticket 26674.
3624 o Minor features (Rust, portability):
3625 - Rust cross-compilation is now supported. Closes ticket 25895.
3627 o Minor bugfixes (compilation):
3628 - Update build system so that tor builds again with --disable-unittests
3629 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
3630 - Fix a compilation warning on some versions of GCC when building
3631 code that calls routerinfo_get_my_routerinfo() twice, assuming
3632 that the second call will succeed if the first one did. Fixes bug
3633 26269; bugfix on 0.2.8.2-alpha.
3635 o Minor bugfixes (controller):
3636 - Report the port correctly when a port is configured to bind to
3637 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3638 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3639 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3640 on 0.3.3.1-alpha. Patch by "akwizgran".
3642 o Minor bugfixes (correctness, flow control):
3643 - Upon receiving a stream-level SENDME cell, verify that our window
3644 has not grown too large. Fixes bug 26214; bugfix on svn
3647 o Minor bugfixes (memory, correctness):
3648 - Fix a number of small memory leaks identified by coverity. Fixes
3649 bug 26467; bugfix on numerous Tor versions.
3651 o Minor bugfixes (logging):
3652 - Improve the log message when connection initiators fail to
3653 authenticate direct connections to relays. Fixes bug 26927; bugfix
3656 o Minor bugfixes (portability):
3657 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
3658 26994; bugfix on 0.3.4.1-alpha.
3659 - Work around two different bugs in the OS X 10.10 and later SDKs
3660 that would prevent us from successfully targeting earlier versions
3661 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3663 o Minor bugfixes (single onion services, Tor2web):
3664 - Log a protocol warning when single onion services or Tor2web
3665 clients fail to authenticate direct connections to relays. Fixes
3666 bug 26924; bugfix on 0.2.9.1-alpha.
3668 o Minor bugfixes (testing):
3669 - Disable core dumps in test_bt.sh, to avoid failures in "make
3670 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3672 o Minor bugfixes (testing, compatibility):
3673 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
3674 only to pass strings (rather than "bytes" objects) to the Python
3675 subprocess module. Python 3 on Windows seems to require this.
3676 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
3677 0.3.1.1-alpha (for hs_ntor_ref.py).
3679 o Minor bugfixes (v3 onion services):
3680 - Stop sending ed25519 link specifiers in v3 onion service introduce
3681 cells and descriptors, when the rendezvous or introduction point
3682 doesn't support ed25519 link authentication. Fixes bug 26627;
3683 bugfix on 0.3.2.4-alpha.
3686 Changes in version 0.3.4.5-rc - 2018-07-13
3687 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
3688 bridge relays should upgrade.
3690 o Directory authority changes:
3691 - The "Bifroest" bridge authority has been retired; the new bridge
3692 authority is "Serge", and it is operated by George from the
3693 TorBSD project. Closes ticket 26771.
3696 Changes in version 0.3.3.9 - 2018-07-13
3697 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3698 bridge relays should upgrade.
3700 o Directory authority changes:
3701 - The "Bifroest" bridge authority has been retired; the new bridge
3702 authority is "Serge", and it is operated by George from the
3703 TorBSD project. Closes ticket 26771.
3706 Changes in version 0.3.2.11 - 2018-07-13
3707 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3708 bridge relays should upgrade. We also take this opportunity to backport
3711 o Directory authority changes:
3712 - The "Bifroest" bridge authority has been retired; the new bridge
3713 authority is "Serge", and it is operated by George from the
3714 TorBSD project. Closes ticket 26771.
3716 o Directory authority changes (backport from 0.3.3.7):
3717 - Add an IPv6 address for the "dannenberg" directory authority.
3718 Closes ticket 26343.
3720 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3721 - When directory authorities read a zero-byte bandwidth file, they
3722 would previously log a warning with the contents of an
3723 uninitialised buffer. They now log a warning about the empty file
3724 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3726 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3727 - Correctly detect when onion services get disabled after HUP. Fixes
3728 bug 25761; bugfix on 0.3.2.1.
3730 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3731 - Explicitly permit the poll() system call when the Linux
3732 seccomp2-based sandbox is enabled: apparently, some versions of
3733 libc use poll() when calling getpwnam(). Closes ticket 25313.
3735 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3736 - Update the Travis CI configuration to use the stable Rust channel,
3737 now that we have decided to require that. Closes ticket 25714.
3739 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3740 - Our .travis.yml configuration now includes support for testing the
3741 results of "make distcheck". (It's not uncommon for "make check"
3742 to pass but "make distcheck" to fail.) Closes ticket 25814.
3743 - Our Travis CI configuration now integrates with the Coveralls
3744 coverage analysis tool. Closes ticket 25818.
3746 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3747 - Add several checks to detect whether Tor relays are uploading
3748 their descriptors without specifying why they regenerated them.
3749 Diagnostic for ticket 25686.
3751 o Minor features (compilation, backport from 0.3.4.4-rc):
3752 - When building Tor, prefer to use Python 3 over Python 2, and more
3753 recent (contemplated) versions over older ones. Closes
3756 o Minor features (geoip):
3757 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3758 Country database. Closes ticket 26674.
3760 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3761 - Upon receiving a malformed connected cell, stop processing the
3762 cell immediately. Previously we would mark the connection for
3763 close, but continue processing the cell as if the connection were
3764 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3766 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3767 - Allow the nanosleep() system call, which glibc uses to implement
3768 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3770 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3771 - When running the hs_ntor_ref.py test, make sure only to pass
3772 strings (rather than "bytes" objects) to the Python subprocess
3773 module. Python 3 on Windows seems to require this. Fixes bug
3774 26535; bugfix on 0.3.1.1-alpha.
3775 - When running the ntor_ref.py test, make sure only to pass strings
3776 (rather than "bytes" objects) to the Python subprocess module.
3777 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3780 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3781 - Work around a change in OpenSSL 1.1.1 where return values that
3782 would previously indicate "no password" now indicate an empty
3783 password. Without this workaround, Tor instances running with
3784 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3785 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3787 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3788 - Document that the PerConnBW{Rate,Burst} options will fall back to
3789 their corresponding consensus parameters only if those parameters
3790 are set. Previously we had claimed that these values would always
3791 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3793 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3794 - Fix a compilation warning on some versions of GCC when building
3795 code that calls routerinfo_get_my_routerinfo() twice, assuming
3796 that the second call will succeed if the first one did. Fixes bug
3797 26269; bugfix on 0.2.8.2-alpha.
3799 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3800 - Don't consider Tor running as a client if the ControlPort is open,
3801 but no actual client ports are open. Fixes bug 26062; bugfix
3804 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3805 - Prevent a possible out-of-bounds smartlist read in
3806 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3808 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3809 - Fix a very unlikely (impossible, we believe) null pointer
3810 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3811 Coverity; this is CID 1430932.
3813 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3814 - Fix a memory leak when a v3 onion service is configured and gets a
3815 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3816 - When parsing the descriptor signature, look for the token plus an
3817 extra white-space at the end. This is more correct but also will
3818 allow us to support new fields that might start with "signature".
3819 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3821 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3822 - Relays now correctly block attempts to re-extend to the previous
3823 relay by Ed25519 identity. Previously they would warn in this
3824 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3827 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3828 - Avoid a crash when running with DirPort set but ORPort turned off.
3829 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3831 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3832 - Silence unused-const-variable warnings in zstd.h with some GCC
3833 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3835 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3836 - Avoid intermittent test failures due to a test that had relied on
3837 onion service introduction point creation finishing within 5
3838 seconds of real clock time. Fixes bug 25450; bugfix
3841 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3842 - Fix a C99 compliance issue in our configuration script that caused
3843 compilation issues when compiling Tor with certain versions of
3844 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3846 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3847 - Fix a number of small memory leaks identified by coverity. Fixes
3848 bug 26467; bugfix on numerous Tor versions.
3850 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3851 - Move the list of default directory authorities to its own file.
3852 Closes ticket 24854. Patch by "beastr0".
3855 Changes in version 0.2.9.16 - 2018-07-13
3856 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3857 bridge relays should upgrade. We also take this opportunity to backport
3860 o Directory authority changes:
3861 - The "Bifroest" bridge authority has been retired; the new bridge
3862 authority is "Serge", and it is operated by George from the
3863 TorBSD project. Closes ticket 26771.
3865 o Directory authority changes (backport from 0.3.3.7):
3866 - Add an IPv6 address for the "dannenberg" directory authority.
3867 Closes ticket 26343.
3869 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3870 - When directory authorities read a zero-byte bandwidth file, they
3871 would previously log a warning with the contents of an
3872 uninitialised buffer. They now log a warning about the empty file
3873 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3875 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3876 - Explicitly permit the poll() system call when the Linux
3877 seccomp2-based sandbox is enabled: apparently, some versions of
3878 libc use poll() when calling getpwnam(). Closes ticket 25313.
3880 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3881 - Our .travis.yml configuration now includes support for testing the
3882 results of "make distcheck". (It's not uncommon for "make check"
3883 to pass but "make distcheck" to fail.) Closes ticket 25814.
3884 - Our Travis CI configuration now integrates with the Coveralls
3885 coverage analysis tool. Closes ticket 25818.
3887 o Minor features (compilation, backport from 0.3.4.4-rc):
3888 - When building Tor, prefer to use Python 3 over Python 2, and more
3889 recent (contemplated) versions over older ones. Closes
3892 o Minor features (geoip):
3893 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3894 Country database. Closes ticket 26674.
3896 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3897 - Upon receiving a malformed connected cell, stop processing the
3898 cell immediately. Previously we would mark the connection for
3899 close, but continue processing the cell as if the connection were
3900 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3902 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3903 - Allow the nanosleep() system call, which glibc uses to implement
3904 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3906 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3907 - When running the ntor_ref.py test, make sure only to pass strings
3908 (rather than "bytes" objects) to the Python subprocess module.
3909 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3912 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3913 - Work around a change in OpenSSL 1.1.1 where return values that
3914 would previously indicate "no password" now indicate an empty
3915 password. Without this workaround, Tor instances running with
3916 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3917 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3919 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3920 - Fix a compilation warning on some versions of GCC when building
3921 code that calls routerinfo_get_my_routerinfo() twice, assuming
3922 that the second call will succeed if the first one did. Fixes bug
3923 26269; bugfix on 0.2.8.2-alpha.
3925 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3926 - Don't consider Tor running as a client if the ControlPort is open,
3927 but no actual client ports are open. Fixes bug 26062; bugfix
3930 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3931 - Prevent a possible out-of-bounds smartlist read in
3932 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3934 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3935 - Fix a very unlikely (impossible, we believe) null pointer
3936 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3937 Coverity; this is CID 1430932.
3939 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3940 - Fix a number of small memory leaks identified by coverity. Fixes
3941 bug 26467; bugfix on numerous Tor versions.
3943 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3944 - Move the list of default directory authorities to its own file.
3945 Closes ticket 24854. Patch by "beastr0".
3948 Changes in version 0.3.4.4-rc - 2018-07-09
3949 Tor 0.3.4.4-rc fixes several small compilation, portability, and
3950 correctness issues in previous versions of Tor. This version is a
3951 release candidate: if no serious bugs are found, we expect that the
3952 stable 0.3.4 release will be (almost) the same as this release.
3954 o Minor features (compilation):
3955 - When building Tor, prefer to use Python 3 over Python 2, and more
3956 recent (contemplated) versions over older ones. Closes
3959 o Minor features (geoip):
3960 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3961 Country database. Closes ticket 26674.
3963 o Minor features (Rust, portability):
3964 - Rust cross-compilation is now supported. Closes ticket 25895.
3966 o Minor bugfixes (compilation):
3967 - Fix a compilation warning on some versions of GCC when building
3968 code that calls routerinfo_get_my_routerinfo() twice, assuming
3969 that the second call will succeed if the first one did. Fixes bug
3970 26269; bugfix on 0.2.8.2-alpha.
3972 o Minor bugfixes (control port):
3973 - Report the port correctly when a port is configured to bind to
3974 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3975 - Handle the HSADDRESS= argument to the HSPOST command properly.
3976 (Previously, this argument was misparsed and thus ignored.) Fixes
3977 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
3979 o Minor bugfixes (correctness, flow control):
3980 - Upon receiving a stream-level SENDME cell, verify that our window
3981 has not grown too large. Fixes bug 26214; bugfix on svn
3984 o Minor bugfixes (memory, correctness):
3985 - Fix a number of small memory leaks identified by coverity. Fixes
3986 bug 26467; bugfix on numerous Tor versions.
3988 o Minor bugfixes (testing, compatibility):
3989 - When running the hs_ntor_ref.py test, make sure only to pass
3990 strings (rather than "bytes" objects) to the Python subprocess
3991 module. Python 3 on Windows seems to require this. Fixes bug
3992 26535; bugfix on 0.3.1.1-alpha.
3993 - When running the ntor_ref.py test, make sure only to pass strings
3994 (rather than "bytes" objects) to the Python subprocess module.
3995 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3999 Changes in version 0.3.3.8 - 2018-07-09
4000 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
4001 fixes for a memory leak affecting directory authorities.
4003 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
4004 - Stop leaking memory on directory authorities when planning to
4005 vote. This bug was crashing authorities by exhausting their
4006 memory. Fixes bug 26435; bugfix on 0.3.3.6.
4008 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
4009 - Make sure that failing tests in Rust will actually cause the build
4010 to fail: previously, they were ignored. Fixes bug 26258; bugfix
4013 o Minor features (compilation, backport from 0.3.4.4-rc):
4014 - When building Tor, prefer to use Python 3 over Python 2, and more
4015 recent (contemplated) versions over older ones. Closes
4018 o Minor features (geoip):
4019 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
4020 Country database. Closes ticket 26674.
4022 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
4023 - Add several checks to detect whether Tor relays are uploading
4024 their descriptors without specifying why they regenerated them.
4025 Diagnostic for ticket 25686.
4027 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
4028 - Don't count path selection failures as circuit build failures.
4029 This change should eliminate cases where Tor blames its guard or
4030 the network for situations like insufficient microdescriptors
4031 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4034 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
4035 - Fix a compilation warning on some versions of GCC when building
4036 code that calls routerinfo_get_my_routerinfo() twice, assuming
4037 that the second call will succeed if the first one did. Fixes bug
4038 26269; bugfix on 0.2.8.2-alpha.
4040 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
4041 - Handle the HSADDRESS= argument to the HSPOST command properly.
4042 (Previously, this argument was misparsed and thus ignored.) Fixes
4043 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
4045 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
4046 - Fix a number of small memory leaks identified by coverity. Fixes
4047 bug 26467; bugfix on numerous Tor versions.
4049 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
4050 - Relays now correctly block attempts to re-extend to the previous
4051 relay by Ed25519 identity. Previously they would warn in this
4052 case, but not actually reject the attempt. Fixes bug 26158; bugfix
4055 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
4056 - When shutting down, Tor now clears all the flags in the control.c
4057 module. This should prevent a bug where authentication cookies are
4058 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4060 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
4061 - When running the hs_ntor_ref.py test, make sure only to pass
4062 strings (rather than "bytes" objects) to the Python subprocess
4063 module. Python 3 on Windows seems to require this. Fixes bug
4064 26535; bugfix on 0.3.1.1-alpha.
4065 - When running the ntor_ref.py test, make sure only to pass strings
4066 (rather than "bytes" objects) to the Python subprocess module.
4067 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
4071 Changes in version 0.3.4.3-alpha - 2018-06-26
4072 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
4073 one that was causing stability issues on directory authorities.
4075 o Major bugfixes (directory authority):
4076 - Stop leaking memory on directory authorities when planning to
4077 vote. This bug was crashing authorities by exhausting their
4078 memory. Fixes bug 26435; bugfix on 0.3.3.6.
4080 o Major bugfixes (rust, testing):
4081 - Make sure that failing tests in Rust will actually cause the build
4082 to fail: previously, they were ignored. Fixes bug 26258; bugfix
4085 o Minor feature (directory authorities):
4086 - Stop warning about incomplete bw lines before the first complete
4087 bw line has been found, so that additional header lines can be
4088 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
4090 o Minor features (relay, diagnostic):
4091 - Add several checks to detect whether Tor relays are uploading
4092 their descriptors without specifying why they regenerated them.
4093 Diagnostic for ticket 25686.
4095 o Minor features (unit tests):
4096 - Test complete bandwidth measurements files, and test that
4097 incomplete bandwidth lines only give warnings when the end of the
4098 header has not been detected. Fixes bug 25947; bugfix
4101 o Minor bugfixes (compilation):
4102 - Refrain from compiling unit testing related object files when
4103 --disable-unittests is set to configure script. Fixes bug 24891;
4104 bugfix on 0.2.5.1-alpha.
4105 - When linking the libtor_testing.a library, only include the
4106 dirauth object files once. Previously, they were getting added
4107 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
4108 - The --enable-fatal-warnings flag now affects Rust code as well.
4109 Closes ticket 26245.
4111 o Minor bugfixes (onion services):
4112 - Recompute some consensus information after detecting a clock jump,
4113 or after transitioning from a non-live consensus to a live
4114 consensus. We do this to avoid having an outdated state, and
4115 miscalculating the index for next-generation onion services. Fixes
4116 bug 24977; bugfix on 0.3.2.1-alpha.
4118 o Minor bugfixes (relay):
4119 - Relays now correctly block attempts to re-extend to the previous
4120 relay by Ed25519 identity. Previously they would warn in this
4121 case, but not actually reject the attempt. Fixes bug 26158; bugfix
4124 o Minor bugfixes (testing):
4125 - Fix compilation of the doctests in the Rust crypto crate. Fixes
4126 bug 26415; bugfix on 0.3.4.1-alpha.
4127 - Instead of trying to read the geoip configuration files from
4128 within the unit tests, instead create our own ersatz files with
4129 just enough geoip data in the format we expect. Trying to read
4130 from the source directory created problems on Windows with mingw,
4131 where the build system's paths are not the same as the platform's
4132 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
4133 - Refrain from trying to get an item from an empty smartlist in
4134 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
4135 to catch improper smartlist usage. Furthermore, enable
4136 DEBUG_SMARTLIST globally when build is configured with fragile
4137 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
4140 Changes in version 0.3.3.7 - 2018-06-12
4141 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
4142 fixes for bugs affecting compatibility and stability.
4144 o Directory authority changes:
4145 - Add an IPv6 address for the "dannenberg" directory authority.
4146 Closes ticket 26343.
4148 o Minor features (geoip):
4149 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4150 Country database. Closes ticket 26351.
4152 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
4153 - Work around a change in OpenSSL 1.1.1 where return values that
4154 would previously indicate "no password" now indicate an empty
4155 password. Without this workaround, Tor instances running with
4156 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4157 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4159 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
4160 - Silence unused-const-variable warnings in zstd.h with some GCC
4161 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4163 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
4164 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4165 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4166 miscounting the total number of circuits for these field values.)
4167 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4169 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
4170 - Prevent a possible out-of-bounds smartlist read in
4171 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4173 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
4174 - Only select relays when they have the descriptors we prefer to use
4175 for them. This change fixes a bug where we could select a relay
4176 because it had _some_ descriptor, but reject it later with a
4177 nonfatal assertion error because it didn't have the exact one we
4178 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4181 Changes in version 0.3.4.2-alpha - 2018-06-12
4182 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
4183 release, and forward-ports an authority-only security fix from 0.3.3.6.
4185 o Directory authority changes:
4186 - Add an IPv6 address for the "dannenberg" directory authority.
4187 Closes ticket 26343.
4189 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
4190 - Fix a bug that could have allowed an attacker to force a directory
4191 authority to use up all its RAM by passing it a maliciously
4192 crafted protocol versions string. Fixes bug 25517; bugfix on
4193 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4195 o Minor features (continuous integration):
4196 - Add the necessary configuration files for continuous integration
4197 testing on Windows, via the Appveyor platform. Closes ticket
4198 25549. Patches from Marcin Cieślak and Isis Lovecruft.
4200 o Minor features (geoip):
4201 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4202 Country database. Closes ticket 26351.
4204 o Minor bugfixes (compatibility, openssl):
4205 - Work around a change in OpenSSL 1.1.1 where return values that
4206 would previously indicate "no password" now indicate an empty
4207 password. Without this workaround, Tor instances running with
4208 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4209 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4211 o Minor bugfixes (compilation):
4212 - Silence unused-const-variable warnings in zstd.h with some GCC
4213 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4214 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
4215 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
4216 - Avoid a compiler warning when casting the return value of
4217 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
4218 26283; bugfix on 0.2.4.10-alpha.
4220 o Minor bugfixes (control port):
4221 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
4222 CIRC_BW events. Previously, such cells were counted entirely in
4223 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
4226 o Minor bugfixes (controller):
4227 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4228 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4229 miscounting the total number of circuits for these field values.)
4230 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4232 o Minor bugfixes (hardening):
4233 - Prevent a possible out-of-bounds smartlist read in
4234 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4236 o Minor bugfixes (onion services):
4237 - Fix a bug that blocked the creation of ephemeral v3 onion
4238 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
4240 o Minor bugfixes (test coverage tools):
4241 - Update our "cov-diff" script to handle output from the latest
4242 version of gcov, and to remove extraneous timestamp information
4243 from its output. Fixes bugs 26101 and 26102; bugfix
4247 Changes in version 0.3.3.6 - 2018-05-22
4248 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
4249 backports several important fixes from the 0.3.4.1-alpha.
4251 The Tor 0.3.3 series includes controller support and other
4252 improvements for v3 onion services, official support for embedding Tor
4253 within other applications, and our first non-trivial module written in
4254 the Rust programming language. (Rust is still not enabled by default
4255 when building Tor.) And as usual, there are numerous other smaller
4256 bugfixes, features, and improvements.
4258 Below are the changes since 0.3.3.5-rc. For a list of all changes
4259 since 0.3.2.10, see the ReleaseNotes file.
4261 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
4262 - When directory authorities read a zero-byte bandwidth file, they
4263 would previously log a warning with the contents of an
4264 uninitialised buffer. They now log a warning about the empty file
4265 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4267 o Major bugfixes (security, directory authority, denial-of-service):
4268 - Fix a bug that could have allowed an attacker to force a directory
4269 authority to use up all its RAM by passing it a maliciously
4270 crafted protocol versions string. Fixes bug 25517; bugfix on
4271 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4273 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
4274 - Avoid a rare assertion failure in the circuit build timeout code
4275 if we fail to allow any circuits to actually complete. Fixes bug
4276 25733; bugfix on 0.2.2.2-alpha.
4278 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
4279 - Avoid a crash when testing router reachability on a router that
4280 could have an ed25519 ID, but which does not. Fixes bug 25415;
4281 bugfix on 0.3.3.2-alpha.
4283 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
4284 - Correctly detect when onion services get disabled after HUP. Fixes
4285 bug 25761; bugfix on 0.3.2.1.
4287 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
4288 - Impose a limit on circuit cell queue size. The limit can be
4289 controlled by a consensus parameter. Fixes bug 25226; bugfix
4292 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4293 - Avoid some compilation warnings with recent versions of LibreSSL.
4294 Closes ticket 26006.
4296 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4297 - Our .travis.yml configuration now includes support for testing the
4298 results of "make distcheck". (It's not uncommon for "make check"
4299 to pass but "make distcheck" to fail.) Closes ticket 25814.
4300 - Our Travis CI configuration now integrates with the Coveralls
4301 coverage analysis tool. Closes ticket 25818.
4303 o Minor features (geoip):
4304 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4305 database. Closes ticket 26104.
4307 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4308 - Don't consider Tor running as a client if the ControlPort is open,
4309 but no actual client ports are open. Fixes bug 26062; bugfix
4312 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4313 - Upon receiving a malformed connected cell, stop processing the
4314 cell immediately. Previously we would mark the connection for
4315 close, but continue processing the cell as if the connection were
4316 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4318 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4319 - Stop saying in the manual that clients cache ipv4 dns answers from
4320 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4321 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4322 we forgot to say so in the man page. Fixes bug 26052; bugfix
4325 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4326 - Allow the nanosleep() system call, which glibc uses to implement
4327 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4329 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4330 - Fix a memory leak when a v3 onion service is configured and gets a
4331 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4332 - When parsing the descriptor signature, look for the token plus an
4333 extra white-space at the end. This is more correct but also will
4334 allow us to support new fields that might start with "signature".
4335 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4337 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4338 - Avoid a crash when running with DirPort set but ORPort turned off.
4339 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4341 o Documentation (backport from 0.3.4.1-alpha):
4342 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4343 ticket 25857. Patch from "CTassisF".
4346 Changes in version 0.3.4.1-alpha - 2018-05-17
4347 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
4348 includes refactoring to begin reducing Tor's binary size and idle CPU
4349 usage on mobile, along with prep work for new bandwidth scanners,
4350 improvements to the experimental "vanguards" feature, and numerous
4351 other small features and bugfixes.
4353 o New system requirements:
4354 - Tor no longer tries to support old operating systems without
4355 mmap() or some local equivalent. Apparently, compilation on such
4356 systems has been broken for some time, without anybody noticing or
4357 complaining. Closes ticket 25398.
4359 o Major feature (directory authority, modularization):
4360 - The directory authority subsystem has been modularized. The code
4361 is now located in src/or/dirauth/, and is compiled in by default.
4362 To disable the module, the configure option
4363 --disable-module-dirauth has been added. This module may be
4364 disabled by default in some future release. Closes ticket 25610.
4366 o Major features (main loop, CPU usage):
4367 - When Tor is disabled (via DisableNetwork or via hibernation), it
4368 no longer needs to run any per-second events. This change should
4369 make it easier for mobile applications to disable Tor while the
4370 device is sleeping, or Tor is not running. Closes ticket 26063.
4371 - Tor no longer enables all of its periodic events by default.
4372 Previously, Tor would enable all possible main loop events,
4373 regardless of whether it needed them. Furthermore, many of these
4374 events are now disabled with Tor is hibernating or DisableNetwork
4375 is set. This is a big step towards reducing client CPU usage by
4376 reducing the amount of wake-ups the daemon does. Closes ticket
4378 - The bandwidth-limitation logic has been refactored so that
4379 bandwidth calculations are performed on-demand, rather than every
4380 TokenBucketRefillInterval milliseconds. This change should improve
4381 the granularity of our bandwidth calculations, and limit the
4382 number of times that the Tor process needs to wake up when it is
4383 idle. Closes ticket 25373.
4384 - Move responsibility for many operations from a once-per-second
4385 callback to a callback that is only scheduled as needed. Moving
4386 this functionality has allowed us to disable the callback when
4387 Tor's network is disabled. Once enough items are removed from our
4388 once-per-second callback, we can eliminate it entirely to conserve
4389 CPU when idle. The functionality removed includes: closing
4390 connections, circuits, and channels (ticket 25932); consensus
4391 voting (25937); flushing log callbacks (25951); honoring delayed
4392 SIGNEWNYM requests (25949); rescanning the consensus cache
4393 (25931); saving the state file to disk (25948); warning relay
4394 operators about unreachable ports (25952); and keeping track of
4395 Tor's uptime (26009).
4397 o Major bugfixes (directory authorities, security):
4398 - When directory authorities read a zero-byte bandwidth file, they
4399 would previously log a warning with the contents of an
4400 uninitialised buffer. They now log a warning about the empty file
4401 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4403 o Major bugfixes (crash):
4404 - Avoid a rare assertion failure in the circuit build timeout code
4405 if we fail to allow any circuits to actually complete. Fixes bug
4406 25733; bugfix on 0.2.2.2-alpha.
4408 o Major bugfixes (directory authority):
4409 - Avoid a crash when testing router reachability on a router that
4410 could have an ed25519 ID, but which does not. Fixes bug 25415;
4411 bugfix on 0.3.3.2-alpha.
4413 o Major bugfixes (onion service):
4414 - Correctly detect when onion services get disabled after HUP. Fixes
4415 bug 25761; bugfix on 0.3.2.1.
4417 o Major bugfixes (protover, voting):
4418 - Revise Rust implementation of protover to use a more memory-
4419 efficient voting algorithm and corresponding data structures, thus
4420 avoiding a potential (but small impact) DoS attack where specially
4421 crafted protocol strings would expand to several potential
4422 megabytes in memory. In the process, several portions of code were
4423 revised to be methods on new, custom types, rather than functions
4424 taking interchangeable types, thus increasing type safety of the
4425 module. Custom error types and handling were added as well, in
4426 order to facilitate better error dismissal/handling in outside
4427 crates and avoid mistakenly passing an internal error string to C
4428 over the FFI boundary. Many tests were added, and some previous
4429 differences between the C and Rust implementations have been
4430 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4432 o Major bugfixes (relay, denial of service):
4433 - Impose a limit on circuit cell queue size. The limit can be
4434 controlled by a consensus parameter. Fixes bug 25226; bugfix
4437 o Minor features (accounting):
4438 - When Tor becomes dormant, it now uses a scheduled event to wake up
4439 at the right time. Previously, we would use the per-second timer
4440 to check whether to wake up, but we no longer have any per-second
4441 timers enabled when the network is disabled. Closes ticket 26064.
4443 o Minor features (code quality):
4444 - Add optional spell-checking for the Tor codebase, using the
4445 "misspell" program. To use this feature, run "make check-typos".
4446 Closes ticket 25024.
4448 o Minor features (compatibility):
4449 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
4450 the no-deprecated option, and builds correctly with them. Closes
4451 tickets 19429, 19981, and 25353.
4452 - Avoid some compilation warnings with recent versions of LibreSSL.
4453 Closes ticket 26006.
4455 o Minor features (compression, zstd):
4456 - When running with zstd, Tor now considers using advanced functions
4457 that the zstd maintainers have labeled as potentially unstable. To
4458 prevent breakage, Tor will only use this functionality when the
4459 runtime version of the zstd library matches the version with which
4460 Tor was compiled. Closes ticket 25162.
4462 o Minor features (configuration):
4463 - The "DownloadSchedule" options have been renamed to end with
4464 "DownloadInitialDelay". The old names are still allowed, but will
4465 produce a warning. Comma-separated lists are still permitted for
4466 these options, but all values after the first are ignored (as they
4467 have been since 0.2.9). Closes ticket 23354.
4469 o Minor features (continuous integration):
4470 - Our .travis.yml configuration now includes support for testing the
4471 results of "make distcheck". (It's not uncommon for "make check"
4472 to pass but "make distcheck" to fail.) Closes ticket 25814.
4473 - Our Travis CI configuration now integrates with the Coveralls
4474 coverage analysis tool. Closes ticket 25818.
4476 o Minor features (control port):
4477 - Introduce GETINFO "current-time/{local,utc}" to return the local
4478 and UTC times respectively in ISO format. This helps a controller
4479 like Tor Browser detect a time-related error. Closes ticket 25511.
4480 Patch by Neel Chauhan.
4481 - Introduce new fields to the CIRC_BW event. There are two new
4482 fields in each of the read and written directions. The DELIVERED
4483 fields report the total valid data on the circuit, as measured by
4484 the payload sizes of verified and error-checked relay command
4485 cells. The OVERHEAD fields report the total unused bytes in each
4486 of these cells. Closes ticket 25903.
4488 o Minor features (directory authority):
4489 - Directory authorities now open their key-pinning files as O_SYNC,
4490 to limit their chances of accidentally writing partial lines.
4491 Closes ticket 23909.
4493 o Minor features (directory authority, forward compatibility):
4494 - Make the lines of the measured bandwidth file able to contain
4495 their entries in any order. Previously, the node_id entry needed
4496 to come first. Closes ticket 26004.
4498 o Minor features (entry guards):
4499 - Introduce a new torrc option NumPrimaryGuards for controlling the
4500 number of primary guards. Closes ticket 25843.
4502 o Minor features (geoip):
4503 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4504 database. Closes ticket 26104.
4506 o Minor features (performance):
4507 - Avoid a needless call to malloc() when processing an incoming
4508 relay cell. Closes ticket 24914.
4509 - Make our timing-wheel code run a tiny bit faster on 32-bit
4510 platforms, by preferring 32-bit math to 64-bit. Closes
4512 - Avoid a needless malloc()/free() pair every time we handle an ntor
4513 handshake. Closes ticket 25150.
4515 o Minor features (testing):
4516 - Add a unit test for voting_schedule_get_start_of_next_interval().
4517 Closes ticket 26014, and helps make unit test coverage
4519 - A new unittests module specifically for testing the functions in
4520 the (new-ish) bridges.c module has been created with new
4521 unittests, raising the code coverage percentages. Closes 25425.
4522 - We now have improved testing for addressmap_get_virtual_address()
4523 function. This should improve our test coverage, and make our test
4524 coverage more deterministic. Closes ticket 25993.
4526 o Minor features (timekeeping, circuit scheduling):
4527 - When keeping track of how busy each circuit have been recently on
4528 a given connection, use coarse-grained monotonic timers rather
4529 than gettimeofday(). This change should marginally increase
4530 accuracy and performance. Implements part of ticket 25927.
4532 o Minor bugfixes (bandwidth management):
4533 - Consider ourselves "low on write bandwidth" if we have exhausted
4534 our write bandwidth some time in the last second. This was the
4535 documented behavior before, but the actual behavior was to change
4536 this value every TokenBucketRefillInterval. Fixes bug 25828;
4537 bugfix on 0.2.3.5-alpha.
4539 o Minor bugfixes (C correctness):
4540 - Add a missing lock acquisition in the shutdown code of the control
4541 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
4542 Coverity; this is CID 1433643.
4544 o Minor bugfixes (circuit path selection):
4545 - Don't count path selection failures as circuit build failures.
4546 This change should eliminate cases where Tor blames its guard or
4547 the network for situations like insufficient microdescriptors
4548 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4551 o Minor bugfixes (client):
4552 - Don't consider Tor running as a client if the ControlPort is open,
4553 but no actual client ports are open. Fixes bug 26062; bugfix
4556 o Minor bugfixes (code style):
4557 - Fixed multiple includes of transports.h in src/or/connection.c
4558 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
4559 - Remove the unused variable n_possible from the function
4560 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
4562 o Minor bugfixes (control interface):
4563 - Respond with more human-readable error messages to GETINFO exit-
4564 policy/* requests. Also, let controller know if an error is
4565 transient (response code 551) or not (response code 552). Fixes
4566 bug 25852; bugfix on 0.2.8.1-alpha.
4568 o Minor bugfixes (controller):
4569 - Make CIRC_BW event reflect the total of all data sent on a
4570 circuit, including padding and dropped cells. Also fix a mis-
4571 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
4572 bugfix on 0.2.5.2-alpha.
4574 o Minor bugfixes (correctness, client):
4575 - Upon receiving a malformed connected cell, stop processing the cell
4576 immediately. Previously we would mark the connection for close, but
4577 continue processing the cell as if the connection were open. Fixes bug
4578 26072; bugfix on 0.2.4.7-alpha.
4580 o Minor bugfixes (directory client):
4581 - When unverified-consensus is verified, rename it to cached-
4582 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
4583 - Fixed launching a certificate fetch always during the scheduled
4584 periodic consensus fetch by fetching only in those cases when
4585 consensus are waiting for certs. Fixes bug 24740; bugfix
4588 o Minor bugfixes (documentation):
4589 - Stop saying in the manual that clients cache ipv4 dns answers from
4590 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4591 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4592 we forgot to say so in the man page. Fixes bug 26052; bugfix
4595 o Minor bugfixes (error reporting):
4596 - Improve tolerance for directory authorities with skewed clocks.
4597 Previously, an authority with a clock more than 60 seconds ahead
4598 could cause a client with a correct clock to warn that the
4599 client's clock was behind. Now the clocks of a majority of
4600 directory authorities have to be ahead of the client before this
4601 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
4603 o Minor bugfixes (Linux seccomp2 sandbox):
4604 - Allow the nanosleep() system call, which glibc uses to implement
4605 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4607 o Minor bugfixes (onion service):
4608 - Fix a memory leak when a v3 onion service is configured and gets a
4609 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4610 - When parsing the descriptor signature, look for the token plus an
4611 extra white-space at the end. This is more correct but also will
4612 allow us to support new fields that might start with "signature".
4613 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4615 o Minor bugfixes (path selection):
4616 - Only select relays when they have the descriptors we prefer to use
4617 for them. This change fixes a bug where we could select a relay
4618 because it had _some_ descriptor, but reject it later with a
4619 nonfatal assertion error because it didn't have the exact one we
4620 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4622 o Minor bugfixes (portability):
4623 - Do not align mmap length, as it is not required by POSIX, and the
4624 getpagesize function is deprecated. Fixes bug 25399; bugfix
4627 o Minor bugfixes (portability, FreeBSD):
4628 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
4629 does not stringify on FreeBSD, so we switch to tor_asprintf().
4630 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
4632 o Minor bugfixes (relay statistics):
4633 - When a relay is collecting internal statistics about how many
4634 create cell requests it has seen of each type, accurately count
4635 the requests from relays that temporarily fall out of the
4636 consensus. (To be extra conservative, we were already ignoring
4637 requests from clients in our counts, and we continue ignoring them
4638 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
4640 o Minor bugfixes (relay, crash):
4641 - Avoid a crash when running with DirPort set but ORPort turned off.
4642 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4644 o Minor bugfixes (restart-in-process):
4645 - When shutting down, Tor now clears all the flags in the control.c
4646 module. This should prevent a bug where authentication cookies are
4647 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4649 o Minor bugfixes (testing):
4650 - When testing workqueue event-cancellation, make sure that we
4651 actually cancel an event, and that cancel each event with equal
4652 probability. (It was previously possible, though extremely
4653 unlikely, for our event-canceling test not to cancel any events.)
4654 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
4655 - Repeat part of the test in test_client_pick_intro() a number of
4656 times, to give it consistent coverage. Fixes bug 25996; bugfix
4658 - Remove randomness from the hs_common/responsible_hsdirs test, so
4659 that it always takes the same path through the function it tests.
4660 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
4661 - Change the behavior of the "channel/outbound" test so that it
4662 never causes a 10-second rollover for the EWMA circuitmux code.
4663 Previously, this behavior would happen randomly, and result in
4664 fluctuating test coverage. Fixes bug 25994; bugfix
4666 - Use X509_new() to allocate certificates that will be freed later
4667 with X509_free(). Previously, some parts of the unit tests had
4668 used tor_malloc_zero(), which is incorrect, and which caused test
4669 failures on Windows when they were built with extra hardening.
4670 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
4672 - While running the circuit_timeout test, fix the PRNG to a
4673 deterministic AES stream, so that the test coverage from this test
4674 will itself be deterministic. Fixes bug 25995; bugfix
4677 o Minor bugfixes (vanguards):
4678 - Allow the last hop in a vanguard circuit to be the same as our
4679 first, to prevent the adversary from influencing guard node choice
4680 by choice of last hop. Also prevent the creation of A - B - A
4681 paths, or A - A paths, which are forbidden by relays. Fixes bug
4682 25870; bugfix on 0.3.3.1-alpha.
4684 o Code simplification and refactoring:
4685 - Remove duplicate code in parse_{c,s}method_line and bootstrap
4686 their functionalities into a single function. Fixes bug 6236;
4687 bugfix on 0.2.3.6-alpha.
4688 - We remove the PortForwsrding and PortForwardingHelper options,
4689 related functions, and the port_forwarding tests. These options
4690 were used by the now-deprecated Vidalia to help ordinary users
4691 become Tor relays or bridges. Closes ticket 25409. Patch by
4693 - In order to make the OR and dir checking function in router.c less
4694 confusing we renamed some functions and
4695 consider_testing_reachability() has been split into
4696 router_should_check_reachability() and
4697 router_do_reachability_checks(). Also we improved the documentation
4698 in some functions. Closes ticket 18918.
4699 - Initial work to isolate Libevent usage to a handful of modules in
4700 our codebase, to simplify our call structure, and so that we can
4701 more easily change event loops in the future if needed. Closes
4703 - Introduce a function to call getsockname() and return tor_addr_t,
4704 to save a little complexity throughout the codebase. Closes
4706 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
4707 as hsdir_index is always present. Also, we move hsdir_index_t into
4708 or.h. Closes ticket 23094. Patch by Neel Chauhan.
4709 - Merge functions used for describing nodes and suppress the
4710 functions that do not allocate memory for the output buffer
4711 string. NODE_DESC_BUF_LEN constant and format_node_description()
4712 function cannot be used externally from router.c module anymore.
4713 Closes ticket 25432. Patch by valentecaio.
4714 - Our main loop has been simplified so that all important operations
4715 happen inside events. Previously, some operations had to happen
4716 outside the event loop, to prevent infinite sequences of event
4717 activations. Closes ticket 25374.
4718 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4719 it in register_intro_circ() and service_intro_point_new(). This
4720 prevents the digest from being re-calculated each time. Closes
4721 ticket 23107. Patch by Neel Chauhan.
4722 - Refactor token-bucket implementations to use a common backend.
4723 Closes ticket 25766.
4724 - Remove extern declaration of stats_n_seconds_working variable from
4725 main, protecting its accesses with get_uptime() and reset_uptime()
4726 functions. Closes ticket 25081, patch by “valentecaio”.
4727 - Remove our previous logic for "cached gettimeofday()" -- our
4728 coarse monotonic timers are fast enough for this purpose, and far
4729 less error-prone. Implements part of ticket 25927.
4730 - Remove the return value for fascist_firewall_choose_address_base(),
4731 and sister functions such as fascist_firewall_choose_address_node()
4732 and fascist_firewall_choose_address_rs(). Also, while we're here,
4733 initialize the ap argument as leaving it uninitialized can pose a
4734 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4735 - Rename two fields of connection_t struct. timestamp_lastwritten is
4736 renamed to timestamp_last_write_allowed and timestamp_lastread is
4737 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4739 - Since Tor requires C99, remove our old workaround code for libc
4740 implementations where free(NULL) doesn't work. Closes ticket 24484.
4741 - Use our standard rate-limiting code to deal with excessive
4742 libevent failures, rather than the hand-rolled logic we had
4743 before. Closes ticket 26016.
4744 - We remove the return value of node_get_prim_orport() and
4745 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4746 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4747 check for a null address. Closes ticket 23873. Patch by
4749 - We switch to should_record_bridge_info() in
4750 geoip_note_client_seen() and options_need_geoip_info() instead of
4751 accessing the configuration values directly. Fixes bug 25290;
4752 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4754 o Deprecated features:
4755 - As we are not recommending 0.2.5 anymore, we require relays that
4756 once had an ed25519 key associated with their RSA key to always
4757 have that key, instead of allowing them to drop back to a version
4758 that didn't support ed25519. This means they need to use a new RSA
4759 key if they want to downgrade to an older version of tor without
4760 ed25519. Closes ticket 20522.
4763 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4764 ticket 25857. Patch from "CTassisF".
4767 - Directory authorities will no longer support voting according to
4768 any consensus method before consensus method 25. This keeps
4769 authorities compatible with all authorities running 0.2.9.8 and
4770 later, and does not break any clients or relays. Implements ticket
4771 24378 and proposal 290.
4772 - The PortForwarding and PortForwardingHelper features have been
4773 removed. The reasoning is, given that implementations of NAT
4774 traversal protocols within common consumer grade routers are
4775 frequently buggy, and that the target audience for a NAT punching
4776 feature is a perhaps less-technically-inclined relay operator,
4777 when the helper fails to setup traversal the problems are usually
4778 deep, ugly, and very router specific, making them horrendously
4779 impossible for technical support to reliable assist with, and thus
4780 resulting in frustration all around. Unfortunately, relay
4781 operators who would like to run relays behind NATs will need to
4782 become more familiar with the port forwarding configurations on
4783 their local router. Closes 25409.
4784 - The TestingEnableTbEmptyEvent option has been removed. It was used
4785 in testing simulations to measure how often connection buckets
4786 were emptied, in order to improve our scheduling, but it has not
4787 been actively used in years. Closes ticket 25760.
4788 - The old "round-robin" circuit multiplexer (circuitmux)
4789 implementation has been removed, along with a fairly large set of
4790 code that existed to support it. It has not been the default
4791 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4792 but it still required an unreasonable amount of memory and CPU.
4793 Closes ticket 25268.
4796 Changes in version 0.3.3.5-rc - 2018-04-15
4797 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4798 including some that could affect reliability or correctness.
4800 This is the first release candidate in the 0.3.3 series. If we find no
4801 new bugs or regression here, then the first stable 0.3.3 release will
4802 be nearly identical to this one.
4804 o Major bugfixes (security, protover, voting):
4805 - Revise Rust implementation of protover to use a more memory-
4806 efficient voting algorithm and corresponding data structures, thus
4807 avoiding a potential memory-based DoS attack where specially
4808 crafted protocol strings would expand to fill available memory.
4809 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4811 o Major bugfixes (performance, load balancing):
4812 - Directory authorities no longer vote in favor of the Guard flag
4813 for relays without directory support. Starting in Tor
4814 0.3.0.1-alpha, clients have been avoiding using such relays in the
4815 Guard position, leading to increasingly broken load balancing for
4816 the 5%-or-so of Guards that don't advertise directory support.
4817 Fixes bug 22310; bugfix on 0.3.0.6.
4819 o Minor feature (continuous integration):
4820 - Update the Travis CI configuration to use the stable Rust channel,
4821 now that we have decided to require that. Closes ticket 25714.
4823 o Minor features (config options):
4824 - Change the way the default value for MaxMemInQueues is calculated.
4825 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4826 more. Otherwise we use the former value of 75%. Closes
4829 o Minor features (geoip):
4830 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4831 Country database. Closes ticket 25718.
4833 o Minor bugfixes (client):
4834 - When using a listed relay as a bridge, and also using
4835 microdescriptors, and considering that relay as a non-bridge in a
4836 circuit, treat its microdescriptor as a valid source of
4837 information about that relay. This change should prevent a non-
4838 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4840 o Minor bugfixes (controller):
4841 - Restore the correct operation of the RESOLVE command, which had
4842 been broken since we added the ability to enable/disable DNS on
4843 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4845 o Minor bugfixes (distribution, compilation, rust):
4846 - Build correctly when the rust dependencies submodule is loaded,
4847 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4848 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4849 - Actually include all of our Rust source in our source
4850 distributions. (Previously, a few of the files were accidentally
4851 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4853 o Minor bugfixes (documentation):
4854 - Document that the PerConnBW{Rate,Burst} options will fall back to
4855 their corresponding consensus parameters only if those parameters
4856 are set. Previously we had claimed that these values would always
4857 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4858 - Revert a misformatting issue in the ExitPolicy documentation.
4859 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4861 o Minor bugfixes (exit relay DNS retries):
4862 - Re-attempt timed-out DNS queries 3 times before failure, since our
4863 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4864 slightly more timeouts per resolver when an exit has multiple
4865 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4867 o Minor bugfixes (onion services):
4868 - Re-instate counting the client HSDir fetch circuits against the
4869 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4871 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4872 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4873 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4875 o Code simplification and refactoring:
4876 - Move the list of default directory authorities to its own file.
4877 Closes ticket 24854. Patch by "beastr0".
4879 o Documentation (manpage, denial of service):
4880 - Provide more detail about the denial-of-service options, by
4881 listing each mitigation and explaining how they relate. Closes
4885 Changes in version 0.3.3.4-alpha - 2018-03-29
4886 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4887 the alpha testing of earlier releases in its series. We are
4888 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4890 o New system requirements:
4891 - When built with Rust, Tor now depends on version 0.2.39 of the
4892 libc crate. Closes tickets 25310 and 25664.
4894 o Major bugfixes (relay, connection):
4895 - If we have failed to connect to a relay and received a connection
4896 refused, timeout, or similar error (at the TCP level), do not try
4897 that same address/port again for 60 seconds after the failure has
4898 occurred. Fixes bug 24767; bugfix on 0.0.6.
4900 o Minor features (geoip):
4901 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4902 Country database. Closes ticket 25469.
4904 o Minor features (log messages):
4905 - Improve log message in the out-of-memory handler to include
4906 information about memory usage from the different compression
4907 backends. Closes ticket 25372.
4909 o Minor features (sandbox):
4910 - Explicitly permit the poll() system call when the Linux
4911 seccomp2-based sandbox is enabled: apparently, some versions of
4912 libc use poll() when calling getpwnam(). Closes ticket 25313.
4914 o Minor bugfixes (C correctness):
4915 - Fix a very unlikely (impossible, we believe) null pointer
4916 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4917 Coverity; this is CID 1430932.
4919 o Minor bugfixes (channel, client):
4920 - Better identify client connection when reporting to the geoip
4921 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
4923 o Minor bugfixes (compilation):
4924 - Fix a C99 compliance issue in our configuration script that caused
4925 compilation issues when compiling Tor with certain versions of
4926 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
4928 o Minor bugfixes (controller, reliability):
4929 - Avoid a (nonfatal) assertion failure when extending a one-hop
4930 circuit from the controller to become a multihop circuit. Fixes
4931 bug 24903; bugfix on 0.2.5.2-alpha.
4933 o Major bugfixes (networking):
4934 - Tor will no longer reject IPv6 address strings from Tor Browser
4935 when they are passed as hostnames in SOCKS5 requests. Fixes bug
4936 25036, bugfix on Tor 0.3.1.2.
4938 o Minor bugfixes (networking):
4939 - string_is_valid_hostname() will not consider IP strings to be
4940 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
4942 o Minor bugfixes (onion service v3):
4943 - Avoid an assertion failure when the next onion service
4944 descriptor rotation type is out of sync with the consensus's
4945 valid-after time. Instead, log a warning message with extra
4946 information, so we can better hunt down the cause of this
4947 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
4949 o Minor bugfixes (testing):
4950 - Avoid intermittent test failures due to a test that had relied on
4951 onion service introduction point creation finishing within 5
4952 seconds of real clock time. Fixes bug 25450; bugfix
4954 - Rust crates are now automatically detected and tested. Previously,
4955 some crates were not tested by `make test-rust` due to a static
4956 string in the `src/test/test_rust.sh` script specifying which
4957 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
4959 o Minor bugfixes (testing, benchmarks):
4960 - Fix a crash when running benchmark tests on win32 systems. The
4961 crash was due to a mutex that wasn't initialized before logging
4962 and options were initialized. Fixes bug 25479; bugfix
4965 o Minor bugfixes (warnings, ipv6):
4966 - Avoid a bug warning that could occur when trying to connect to a
4967 relay over IPv6. This warning would occur on a Tor instance that
4968 downloads router descriptors, but prefers to use microdescriptors.
4969 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
4971 o Code simplification and refactoring:
4972 - Remove the old (deterministic) directory retry logic entirely:
4973 We've used exponential backoff exclusively for some time. Closes
4977 - Improved the documentation of AccountingStart parameter. Closes
4979 - Update the documentation for "Log" to include the current list of
4980 logging domains. Closes ticket 25378.
4983 Changes in version 0.3.1.10 - 2018-03-03
4984 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
4987 It includes an important security fix for a remote crash attack
4988 against directory authorities, tracked as TROVE-2018-001.
4990 This release also backports our new system for improved resistance to
4991 denial-of-service attacks against relays.
4993 This release also fixes several minor bugs and annoyances from
4996 All directory authorities should upgrade to one of the versions
4997 released today. Relays running 0.3.1.x may wish to update to one of
4998 the versions released today, for the DoS mitigations.
5000 Please note: according to our release calendar, Tor 0.3.1 will no
5001 longer be supported after 1 July 2018. If you will be running Tor
5002 after that date, you should make sure to plan to upgrade to the latest
5003 stable version, or downgrade to 0.2.9 (which will receive long-term
5006 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5007 - Fix a protocol-list handling bug that could be used to remotely crash
5008 directory authorities with a null-pointer exception. Fixes bug 25074;
5009 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5012 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5013 - Give relays some defenses against the recent network overload. We
5014 start with three defenses (default parameters in parentheses).
5015 First: if a single client address makes too many concurrent
5016 connections (>100), hang up on further connections. Second: if a
5017 single client address makes circuits too quickly (more than 3 per
5018 second, with an allowed burst of 90) while also having too many
5019 connections open (3), refuse new create cells for the next while
5020 (1-2 hours). Third: if a client asks to establish a rendezvous
5021 point to you directly, ignore the request. These defenses can be
5022 manually controlled by new torrc options, but relays will also
5023 take guidance from consensus parameters, so there's no need to
5024 configure anything manually. Implements ticket 24902.
5026 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
5027 - Update the sandbox rules so that they should now work correctly
5028 with Glibc 2.26. Closes ticket 24315.
5030 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5031 - Fix an "off by 2" error in counting rendezvous failures on the
5032 onion service side. While we thought we would stop the rendezvous
5033 attempt after one failed circuit, we were actually making three
5034 circuit attempts before giving up. Now switch to a default of 2,
5035 and allow the consensus parameter "hs_service_max_rdv_failures" to
5036 override. Fixes bug 24895; bugfix on 0.0.6.
5038 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5039 - Add Link protocol version 5 to the supported protocols list. Fixes
5040 bug 25070; bugfix on 0.3.1.1-alpha.
5042 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5043 - Fix a set of false positives where relays would consider
5044 connections to other relays as being client-only connections (and
5045 thus e.g. deserving different link padding schemes) if those
5046 relays fell out of the consensus briefly. Now we look only at the
5047 initial handshake and whether the connection authenticated as a
5048 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5050 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5051 - Make our OOM handler aware of the geoip client history cache so it
5052 doesn't fill up the memory. This check is important for IPv6 and
5053 our DoS mitigation subsystem. Closes ticket 25122.
5055 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
5056 - Change relay bandwidth reporting stats interval from 4 hours to 24
5057 hours in order to reduce the efficiency of guard discovery
5058 attacks. Fixes ticket 23856.
5060 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5061 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5062 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5063 since they neither disabled TLS 1.3 nor enabled any of the
5064 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5065 Closes ticket 24978.
5067 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
5068 - The fallback directory list has been re-generated based on the
5069 current status of the network. Tor uses fallback directories to
5070 bootstrap when it doesn't yet have up-to-date directory
5071 information. Closes ticket 24801.
5072 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5073 prefer to bootstrap from fallback directory mirrors. This is a
5074 follow-up to 24679, which removed weights from the default
5075 fallbacks. Implements ticket 24681.
5077 o Minor features (geoip):
5078 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5081 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5082 - Use the actual observed address of an incoming relay connection,
5083 not the canonical address of the relay from its descriptor, when
5084 making decisions about how to handle the incoming connection.
5085 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5087 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5088 - Directory authorities, when refusing a descriptor from a rejected
5089 relay, now explicitly tell the relay (in its logs) to set a valid
5090 ContactInfo address and contact the bad-relays@ mailing list.
5091 Fixes bug 25170; bugfix on 0.2.9.1.
5093 o Minor bugfixes (address selection, backport from 0.3.2.9):
5094 - When the fascist_firewall_choose_address_ functions don't find a
5095 reachable address, set the returned address to the null address
5096 and port. This is a precautionary measure, because some callers do
5097 not check the return value. Fixes bug 24736; bugfix
5100 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
5101 - Fetch descriptors aggressively whenever we lack enough to build
5102 circuits, regardless of how many descriptors we are missing.
5103 Previously, we would delay launching the fetch when we had fewer
5104 than 15 missing descriptors, even if some of those descriptors
5105 were blocking circuits from building. Fixes bug 23985; bugfix on
5106 0.1.1.11-alpha. The effects of this bug became worse in
5107 0.3.0.3-alpha, when we began treating missing descriptors from our
5108 primary guards as a reason to delay circuits.
5109 - Don't try fetching microdescriptors from relays that have failed
5110 to deliver them in the past. Fixes bug 23817; bugfix
5113 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
5114 - Fix a signed/unsigned comparison warning introduced by our fix to
5115 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5117 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
5118 - Avoid a crash when attempting to use the seccomp2 sandbox together
5119 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5122 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5123 - Fix a possible crash on malformed consensus. If a consensus had
5124 contained an unparseable protocol line, it could have made clients
5125 and relays crash with a null-pointer exception. To exploit this
5126 issue, however, an attacker would need to be able to subvert the
5127 directory authority system. Fixes bug 25251; bugfix on
5128 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5130 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
5131 - Recover better from empty or corrupt files in the consensus cache
5132 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5133 - When a consensus diff calculation is only partially successful,
5134 only record the successful parts as having succeeded. Partial
5135 success can happen if (for example) one compression method fails
5136 but the others succeed. Previously we misrecorded all the
5137 calculations as having succeeded, which would later cause a
5138 nonfatal assertion failure. Fixes bug 24086; bugfix
5141 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
5142 - Tor now updates its guard state when it reads a consensus
5143 regardless of whether it's missing descriptors. That makes tor use
5144 its primary guards to fetch descriptors in some edge cases where
5145 it would previously have used fallback directories. Fixes bug
5146 23862; bugfix on 0.3.0.1-alpha.
5148 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5149 - Don't treat inability to store a cached consensus object as a bug:
5150 it can happen normally when we are out of disk space. Fixes bug
5151 24859; bugfix on 0.3.1.1-alpha.
5153 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
5154 - When queuing DESTROY cells on a channel, only queue the circuit-id
5155 and reason fields: not the entire 514-byte cell. This fix should
5156 help mitigate any bugs or attacks that fill up these queues, and
5157 free more RAM for other uses. Fixes bug 24666; bugfix
5160 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
5161 - When closing a connection via close_connection_immediately(), we
5162 mark it as "not blocked on bandwidth", to prevent later calls from
5163 trying to unblock it, and give it permission to read. This fixes a
5164 backtrace warning that can happen on relays under various
5165 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5167 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
5168 - When selecting relays by bandwidth, avoid a rounding error that
5169 could sometimes cause load to be imbalanced incorrectly.
5170 Previously, we would always round upwards; now, we round towards
5171 the nearest integer. This had the biggest effect when a relay's
5172 weight adjustments should have given it weight 0, but it got
5173 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5174 - When calculating the fraction of nodes that have descriptors, and
5175 all nodes in the network have zero bandwidths, count the number of
5176 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5177 - Actually log the total bandwidth in compute_weighted_bandwidths().
5178 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5180 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5181 - Improve the performance of our consensus-diff application code
5182 when Tor is built with the --enable-fragile-hardening option set.
5183 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5185 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5186 - Don't exit the Tor process if setrlimit() fails to change the file
5187 limit (which can happen sometimes on some versions of OSX). Fixes
5188 bug 21074; bugfix on 0.0.9pre5.
5190 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
5191 - Fix a bug in the bit-counting parts of our timing-wheel code on
5192 MSVC. (Note that MSVC is still not a supported build platform, due
5193 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
5196 o Minor bugfixes (relay, partial backport):
5197 - Make the internal channel_is_client() function look at what sort
5198 of connection handshake the other side used, rather than whether
5199 the other side ever sent a create_fast cell to us. Backports part
5200 of the fixes from bugs 22805 and 24898.
5202 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5203 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5205 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5206 bugfix on 0.2.9.4-alpha.
5208 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5209 - Update the "rust dependencies" submodule to be a project-level
5210 repository, rather than a user repository. Closes ticket 25323.
5213 Changes in version 0.2.9.15 - 2018-03-03
5214 Tor 0.2.9.15 backports important security and stability bugfixes from
5217 It includes an important security fix for a remote crash attack
5218 against directory authorities, tracked as TROVE-2018-001.
5220 This release also backports our new system for improved resistance to
5221 denial-of-service attacks against relays.
5223 This release also fixes several minor bugs and annoyances from
5226 All directory authorities should upgrade to one of the versions
5227 released today. Relays running 0.2.9.x may wish to update to one of
5228 the versions released today, for the DoS mitigations.
5230 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5231 - Fix a protocol-list handling bug that could be used to remotely crash
5232 directory authorities with a null-pointer exception. Fixes bug 25074;
5233 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5236 o Major features (denial-of-service mitigation):
5237 - Give relays some defenses against the recent network overload. We
5238 start with three defenses (default parameters in parentheses).
5239 First: if a single client address makes too many concurrent
5240 connections (>100), hang up on further connections. Second: if a
5241 single client address makes circuits too quickly (more than 3 per
5242 second, with an allowed burst of 90) while also having too many
5243 connections open (3), refuse new create cells for the next while
5244 (1-2 hours). Third: if a client asks to establish a rendezvous
5245 point to you directly, ignore the request. These defenses can be
5246 manually controlled by new torrc options, but relays will also
5247 take guidance from consensus parameters, so there's no need to
5248 configure anything manually. Implements ticket 24902.
5250 o Major bugfixes (bootstrapping):
5251 - Fetch descriptors aggressively whenever we lack enough to build
5252 circuits, regardless of how many descriptors we are missing.
5253 Previously, we would delay launching the fetch when we had fewer
5254 than 15 missing descriptors, even if some of those descriptors
5255 were blocking circuits from building. Fixes bug 23985; bugfix on
5256 0.1.1.11-alpha. The effects of this bug became worse in
5257 0.3.0.3-alpha, when we began treating missing descriptors from our
5258 primary guards as a reason to delay circuits.
5260 o Major bugfixes (onion services, retry behavior):
5261 - Fix an "off by 2" error in counting rendezvous failures on the
5262 onion service side. While we thought we would stop the rendezvous
5263 attempt after one failed circuit, we were actually making three
5264 circuit attempts before giving up. Now switch to a default of 2,
5265 and allow the consensus parameter "hs_service_max_rdv_failures" to
5266 override. Fixes bug 24895; bugfix on 0.0.6.
5268 o Minor feature (relay statistics):
5269 - Change relay bandwidth reporting stats interval from 4 hours to 24
5270 hours in order to reduce the efficiency of guard discovery
5271 attacks. Fixes ticket 23856.
5273 o Minor features (compatibility, OpenSSL):
5274 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5275 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5276 since they neither disabled TLS 1.3 nor enabled any of the
5277 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5278 Closes ticket 24978.
5280 o Minor features (denial-of-service avoidance):
5281 - Make our OOM handler aware of the geoip client history cache so it
5282 doesn't fill up the memory. This check is important for IPv6 and
5283 our DoS mitigation subsystem. Closes ticket 25122.
5285 o Minor features (fallback directory mirrors):
5286 - The fallback directory list has been re-generated based on the
5287 current status of the network. Tor uses fallback directories to
5288 bootstrap when it doesn't yet have up-to-date directory
5289 information. Closes ticket 24801.
5290 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5291 prefer to bootstrap from fallback directory mirrors. This is a
5292 follow-up to 24679, which removed weights from the default
5293 fallbacks. Implements ticket 24681.
5295 o Minor features (geoip):
5296 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5299 o Minor features (linux seccomp2 sandbox):
5300 - Update the sandbox rules so that they should now work correctly
5301 with Glibc 2.26. Closes ticket 24315.
5303 o Minor bugfix (channel connection):
5304 - Use the actual observed address of an incoming relay connection,
5305 not the canonical address of the relay from its descriptor, when
5306 making decisions about how to handle the incoming connection.
5307 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5309 o Minor bugfix (directory authority):
5310 - Directory authorities, when refusing a descriptor from a rejected
5311 relay, now explicitly tell the relay (in its logs) to set a valid
5312 ContactInfo address and contact the bad-relays@ mailing list.
5313 Fixes bug 25170; bugfix on 0.2.9.1.
5315 o Minor bugfixes (address selection):
5316 - When the fascist_firewall_choose_address_ functions don't find a
5317 reachable address, set the returned address to the null address
5318 and port. This is a precautionary measure, because some callers do
5319 not check the return value. Fixes bug 24736; bugfix
5322 o Minor bugfixes (compilation):
5323 - Fix a signed/unsigned comparison warning introduced by our fix to
5324 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5326 o Minor bugfixes (control port, linux seccomp2 sandbox):
5327 - Avoid a crash when attempting to use the seccomp2 sandbox together
5328 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5331 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5332 - Fix a possible crash on malformed consensus. If a consensus had
5333 contained an unparseable protocol line, it could have made clients
5334 and relays crash with a null-pointer exception. To exploit this
5335 issue, however, an attacker would need to be able to subvert the
5336 directory authority system. Fixes bug 25251; bugfix on
5337 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5339 o Minor bugfixes (memory usage):
5340 - When queuing DESTROY cells on a channel, only queue the circuit-id
5341 and reason fields: not the entire 514-byte cell. This fix should
5342 help mitigate any bugs or attacks that fill up these queues, and
5343 free more RAM for other uses. Fixes bug 24666; bugfix
5346 o Minor bugfixes (network layer):
5347 - When closing a connection via close_connection_immediately(), we
5348 mark it as "not blocked on bandwidth", to prevent later calls from
5349 trying to unblock it, and give it permission to read. This fixes a
5350 backtrace warning that can happen on relays under various
5351 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5353 o Minor bugfixes (OSX):
5354 - Don't exit the Tor process if setrlimit() fails to change the file
5355 limit (which can happen sometimes on some versions of OSX). Fixes
5356 bug 21074; bugfix on 0.0.9pre5.
5358 o Minor bugfixes (path selection):
5359 - When selecting relays by bandwidth, avoid a rounding error that
5360 could sometimes cause load to be imbalanced incorrectly.
5361 Previously, we would always round upwards; now, we round towards
5362 the nearest integer. This had the biggest effect when a relay's
5363 weight adjustments should have given it weight 0, but it got
5364 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5365 - When calculating the fraction of nodes that have descriptors, and
5366 all nodes in the network have zero bandwidths, count the number of
5367 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5368 - Actually log the total bandwidth in compute_weighted_bandwidths().
5369 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5371 o Minor bugfixes (portability, msvc):
5372 - Fix a bug in the bit-counting parts of our timing-wheel code on
5373 MSVC. (Note that MSVC is still not a supported build platform, due
5374 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5377 o Minor bugfixes (relay):
5378 - Make the internal channel_is_client() function look at what sort
5379 of connection handshake the other side used, rather than whether
5380 the other side ever sent a create_fast cell to us. Backports part
5381 of the fixes from bugs 22805 and 24898.
5383 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5384 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5386 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5387 bugfix on 0.2.9.4-alpha.
5390 Changes in version 0.3.2.10 - 2018-03-03
5391 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
5392 backports a number of bugfixes, including important fixes for security
5395 It includes an important security fix for a remote crash attack
5396 against directory authorities, tracked as TROVE-2018-001.
5398 Additionally, it backports a fix for a bug whose severity we have
5399 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
5400 triggered in order to crash relays with a use-after-free pattern. As
5401 such, we are now tracking that bug as TROVE-2018-002 and
5402 CVE-2018-0491, and backporting it to earlier releases. This bug
5403 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
5406 This release also backports our new system for improved resistance to
5407 denial-of-service attacks against relays.
5409 This release also fixes several minor bugs and annoyances from
5412 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5413 today, for the fix to TROVE-2018-002. Directory authorities should
5414 also upgrade. (Relays on earlier versions might want to update too for
5415 the DoS mitigations.)
5417 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5418 - Fix a protocol-list handling bug that could be used to remotely crash
5419 directory authorities with a null-pointer exception. Fixes bug 25074;
5420 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5423 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5424 - Avoid adding the same channel twice in the KIST scheduler pending
5425 list, which could lead to remote denial-of-service use-after-free
5426 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5428 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5429 - Give relays some defenses against the recent network overload. We
5430 start with three defenses (default parameters in parentheses).
5431 First: if a single client address makes too many concurrent
5432 connections (>100), hang up on further connections. Second: if a
5433 single client address makes circuits too quickly (more than 3 per
5434 second, with an allowed burst of 90) while also having too many
5435 connections open (3), refuse new create cells for the next while
5436 (1-2 hours). Third: if a client asks to establish a rendezvous
5437 point to you directly, ignore the request. These defenses can be
5438 manually controlled by new torrc options, but relays will also
5439 take guidance from consensus parameters, so there's no need to
5440 configure anything manually. Implements ticket 24902.
5442 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5443 - Fix an "off by 2" error in counting rendezvous failures on the
5444 onion service side. While we thought we would stop the rendezvous
5445 attempt after one failed circuit, we were actually making three
5446 circuit attempts before giving up. Now switch to a default of 2,
5447 and allow the consensus parameter "hs_service_max_rdv_failures" to
5448 override. Fixes bug 24895; bugfix on 0.0.6.
5449 - New-style (v3) onion services now obey the "max rendezvous circuit
5450 attempts" logic. Previously they would make as many rendezvous
5451 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5452 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5454 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5455 - Add Link protocol version 5 to the supported protocols list. Fixes
5456 bug 25070; bugfix on 0.3.1.1-alpha.
5458 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5459 - Fix a set of false positives where relays would consider
5460 connections to other relays as being client-only connections (and
5461 thus e.g. deserving different link padding schemes) if those
5462 relays fell out of the consensus briefly. Now we look only at the
5463 initial handshake and whether the connection authenticated as a
5464 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5466 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5467 - The scheduler subsystem was failing to promptly notice changes in
5468 consensus parameters, making it harder to switch schedulers
5469 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5471 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5472 - Make our OOM handler aware of the geoip client history cache so it
5473 doesn't fill up the memory. This check is important for IPv6 and
5474 our DoS mitigation subsystem. Closes ticket 25122.
5476 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5477 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5478 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5479 since they neither disabled TLS 1.3 nor enabled any of the
5480 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5481 Closes ticket 24978.
5483 o Minor features (geoip):
5484 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5487 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5488 - When logging a failure to create an onion service's descriptor,
5489 also log what the problem with the descriptor was. Diagnostic
5492 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5493 - Use the actual observed address of an incoming relay connection,
5494 not the canonical address of the relay from its descriptor, when
5495 making decisions about how to handle the incoming connection.
5496 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5498 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5499 - Fix a possible crash on malformed consensus. If a consensus had
5500 contained an unparseable protocol line, it could have made clients
5501 and relays crash with a null-pointer exception. To exploit this
5502 issue, however, an attacker would need to be able to subvert the
5503 directory authority system. Fixes bug 25251; bugfix on
5504 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5506 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5507 - Directory authorities, when refusing a descriptor from a rejected
5508 relay, now explicitly tell the relay (in its logs) to set a valid
5509 ContactInfo address and contact the bad-relays@ mailing list.
5510 Fixes bug 25170; bugfix on 0.2.9.1.
5512 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5513 - When building with Rust on OSX, link against libresolv, to work
5514 around the issue at https://github.com/rust-lang/rust/issues/46797.
5515 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5517 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5518 - Remove a BUG() statement when a client fetches an onion descriptor
5519 that has a lower revision counter than the one in its cache. This
5520 can happen in normal circumstances due to HSDir desync. Fixes bug
5521 24976; bugfix on 0.3.2.1-alpha.
5523 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5524 - Don't treat inability to store a cached consensus object as a bug:
5525 it can happen normally when we are out of disk space. Fixes bug
5526 24859; bugfix on 0.3.1.1-alpha.
5528 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5529 - Improve the performance of our consensus-diff application code
5530 when Tor is built with the --enable-fragile-hardening option set.
5531 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5533 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5534 - Don't exit the Tor process if setrlimit() fails to change the file
5535 limit (which can happen sometimes on some versions of OSX). Fixes
5536 bug 21074; bugfix on 0.0.9pre5.
5538 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5539 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5541 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5542 bugfix on 0.2.9.4-alpha.
5544 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5545 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5546 25005; bugfix on 0.3.2.7-rc.
5548 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5549 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5550 version, when deciding whether a consensus entry can support the
5551 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5552 bugfix on 0.3.2.1-alpha.
5554 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5555 - Update the "rust dependencies" submodule to be a project-level
5556 repository, rather than a user repository. Closes ticket 25323.
5558 o Documentation (backport from 0.3.3.1-alpha)
5559 - Document that operators who run more than one relay or bridge are
5560 expected to set MyFamily and ContactInfo correctly. Closes
5564 Changes in version 0.3.3.3-alpha - 2018-03-03
5565 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
5566 It includes an important security fix for a remote crash attack
5567 against directory authorities tracked as TROVE-2018-001.
5569 Additionally, with this release, we are upgrading the severity of a
5570 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
5571 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
5572 a use-after-free pattern. As such, we are now tracking that bug as
5573 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
5574 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
5576 This release also fixes several minor bugs and annoyances from
5579 Relays running 0.3.2.x should upgrade to one of the versions released
5580 today, for the fix to TROVE-2018-002. Directory authorities should
5581 also upgrade. (Relays on earlier versions might want to update too for
5582 the DoS mitigations.)
5584 o Major bugfixes (denial-of-service, directory authority):
5585 - Fix a protocol-list handling bug that could be used to remotely crash
5586 directory authorities with a null-pointer exception. Fixes bug 25074;
5587 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5590 o Minor features (compatibility, OpenSSL):
5591 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5592 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5593 since they neither disabled TLS 1.3 nor enabled any of the
5594 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5595 Closes ticket 24978.
5597 o Minor features (logging):
5598 - Clarify the log messages produced when getrandom() or a related
5599 entropy-generation mechanism gives an error. Closes ticket 25120.
5601 o Minor features (testing):
5602 - Add a "make test-rust" target to run the rust tests only. Closes
5605 o Minor bugfixes (denial-of-service):
5606 - Fix a possible crash on malformed consensus. If a consensus had
5607 contained an unparseable protocol line, it could have made clients
5608 and relays crash with a null-pointer exception. To exploit this
5609 issue, however, an attacker would need to be able to subvert the
5610 directory authority system. Fixes bug 25251; bugfix on
5611 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5613 o Minor bugfixes (DoS mitigation):
5614 - Add extra safety checks when refilling the circuit creation bucket
5615 to ensure we never set a value above the allowed maximum burst.
5616 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
5617 - When a new consensus arrives, don't update our DoS-mitigation
5618 parameters if we aren't a public relay. Fixes bug 25223; bugfix
5621 o Minor bugfixes (man page, SocksPort):
5622 - Remove dead code from the old "SocksSocket" option, and rename
5623 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
5624 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
5626 o Minor bugfixes (performance):
5627 - Reduce the number of circuits that will be opened at once during
5628 the circuit build timeout phase. This is done by increasing the
5629 idle timeout to 3 minutes, and lowering the maximum number of
5630 concurrent learning circuits to 10. Fixes bug 24769; bugfix
5633 o Minor bugfixes (spec conformance):
5634 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5636 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5637 bugfix on 0.2.9.4-alpha.
5639 o Minor bugfixes (spec conformance, rust):
5640 - Resolve a denial-of-service issue caused by an infinite loop in
5641 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
5642 Also tracked as TROVE-2018-003.
5644 o Code simplification and refactoring:
5645 - Update the "rust dependencies" submodule to be a project-level
5646 repository, rather than a user repository. Closes ticket 25323.
5649 Changes in version 0.3.3.2-alpha - 2018-02-10
5650 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
5651 introduces a mechanism to handle the high loads that many relay
5652 operators have been reporting recently. It also fixes several bugs in
5653 older releases. If this new code proves reliable, we plan to backport
5654 it to older supported release series.
5656 o Major features (denial-of-service mitigation):
5657 - Give relays some defenses against the recent network overload. We
5658 start with three defenses (default parameters in parentheses).
5659 First: if a single client address makes too many concurrent
5660 connections (>100), hang up on further connections. Second: if a
5661 single client address makes circuits too quickly (more than 3 per
5662 second, with an allowed burst of 90) while also having too many
5663 connections open (3), refuse new create cells for the next while
5664 (1-2 hours). Third: if a client asks to establish a rendezvous
5665 point to you directly, ignore the request. These defenses can be
5666 manually controlled by new torrc options, but relays will also
5667 take guidance from consensus parameters, so there's no need to
5668 configure anything manually. Implements ticket 24902.
5670 o Major bugfixes (netflow padding):
5671 - Stop adding unneeded channel padding right after we finish
5672 flushing to a connection that has been trying to flush for many
5673 seconds. Instead, treat all partial or complete flushes as
5674 activity on the channel, which will defer the time until we need
5675 to add padding. This fix should resolve confusing and scary log
5676 messages like "Channel padding timeout scheduled 221453ms in the
5677 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5679 o Major bugfixes (protocol versions):
5680 - Add Link protocol version 5 to the supported protocols list. Fixes
5681 bug 25070; bugfix on 0.3.1.1-alpha.
5683 o Major bugfixes (scheduler, consensus):
5684 - The scheduler subsystem was failing to promptly notice changes in
5685 consensus parameters, making it harder to switch schedulers
5686 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5688 o Minor features (denial-of-service avoidance):
5689 - Make our OOM handler aware of the geoip client history cache so it
5690 doesn't fill up the memory. This check is important for IPv6 and
5691 our DoS mitigation subsystem. Closes ticket 25122.
5693 o Minor features (directory authority):
5694 - When directory authorities are unable to add signatures to a
5695 pending consensus, log the reason why. Closes ticket 24849.
5697 o Minor features (geoip):
5698 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5701 o Minor features (logging, diagnostic):
5702 - When logging a failure to create an onion service's descriptor,
5703 also log what the problem with the descriptor was. Diagnostic for
5706 o Minor bugfix (channel connection):
5707 - Use the actual observed address of an incoming relay connection,
5708 not the canonical address of the relay from its descriptor, when
5709 making decisions about how to handle the incoming connection.
5710 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5712 o Minor bugfix (directory authority):
5713 - Directory authorities, when refusing a descriptor from a rejected
5714 relay, now explicitly tell the relay (in its logs) to set a valid
5715 ContactInfo address and contact the bad-relays@ mailing list.
5716 Fixes bug 25170; bugfix on 0.2.9.1.
5718 o Minor bugfixes (all versions of Tor):
5719 - Use the "misspell" tool to detect and fix typos throughout the
5720 source code. Fixes bug 23650; bugfix on various versions of Tor.
5721 Patch from Deepesh Pathak.
5723 o Minor bugfixes (circuit, cannibalization):
5724 - Don't cannibalize preemptively-built circuits if we no longer
5725 recognize their first hop. This situation can happen if our Guard
5726 relay went off the consensus after the circuit was created. Fixes
5727 bug 24469; bugfix on 0.0.6.
5729 o Minor bugfixes (correctness):
5730 - Remove a nonworking, unnecessary check to see whether a circuit
5731 hop's identity digest was set when the circuit failed. Fixes bug
5732 24927; bugfix on 0.2.4.4-alpha.
5734 o Minor bugfixes (logging):
5735 - Don't treat inability to store a cached consensus object as a bug:
5736 it can happen normally when we are out of disk space. Fixes bug
5737 24859; bugfix on 0.3.1.1-alpha.
5738 - Fix a (mostly harmless) race condition when invoking
5739 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5740 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5742 o Minor bugfixes (onion services):
5743 - Remove a BUG() statement when a client fetches an onion descriptor
5744 that has a lower revision counter than the one in its cache. This
5745 can happen in normal circumstances due to HSDir desync. Fixes bug
5746 24976; bugfix on 0.3.2.1-alpha.
5747 - If we are configured to offer a single onion service, don't log
5748 long-term established one hop rendezvous points in the heartbeat.
5749 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5751 o Minor bugfixes (performance):
5752 - Avoid calling protocol_list_supports_protocol() from inside tight
5753 loops when running with cached routerinfo_t objects. Instead,
5754 summarize the relevant protocols as flags in the routerinfo_t, as
5755 we do for routerstatus_t objects. This change simplifies our code
5756 a little, and saves a large amount of short-term memory allocation
5757 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5759 o Minor bugfixes (Rust FFI):
5760 - Fix a minor memory leak which would happen whenever the C code
5761 would call the Rust implementation of
5762 protover_get_supported_protocols(). This was due to the C version
5763 returning a static string, whereas the Rust version newly allocated
5764 a CString to pass across the FFI boundary. Consequently, the C
5765 code was not expecting to need to free() what it was given. Fixes
5766 bug 25127; bugfix on 0.3.2.1-alpha.
5768 o Minor bugfixes (scheduler, KIST):
5769 - Avoid adding the same channel twice in the KIST scheduler pending
5770 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5773 o Minor bugfixes (unit test, monotonic time):
5774 - Increase a constant (1msec to 10msec) in the monotonic time test
5775 that makes sure the nsec/usec/msec times read are synchronized.
5776 This change was needed to accommodate slow systems like armel or
5777 when the clock_gettime() is not a VDSO on the running kernel.
5778 Fixes bug 25113; bugfix on 0.2.9.1.
5780 o Minor bugfixes (v3 onion services):
5781 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5782 version, when deciding whether a consensus entry can support the
5783 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5784 bugfix on 0.3.2.1-alpha.
5786 o Code simplification and refactoring:
5787 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5789 - Remove a series of counters used to track circuit extend attempts
5790 and connection status but that in reality we aren't using for
5791 anything other than stats logged by a SIGUSR1 signal. Closes
5794 o Documentation (man page):
5795 - The HiddenServiceVersion torrc option accepts only one number:
5796 either version 2 or 3. Closes ticket 25026; bugfix
5800 Changes in version 0.3.3.1-alpha - 2018-01-25
5801 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5802 several new features to Tor, including several improvements to
5803 bootstrapping, and support for an experimental "vanguards" feature to
5804 resist guard discovery attacks. This series also includes better
5805 support for applications that need to embed Tor or manage v3
5808 o Major features (embedding):
5809 - There is now a documented stable API for programs that need to
5810 embed Tor. See tor_api.h for full documentation and known bugs.
5811 Closes ticket 23684.
5812 - Tor now has support for restarting in the same process.
5813 Controllers that run Tor using the "tor_api.h" interface can now
5814 restart Tor after Tor has exited. This support is incomplete,
5815 however: we fixed crash bugs that prevented it from working at
5816 all, but many bugs probably remain, including a possibility of
5817 security issues. Implements ticket 24581.
5819 o Major features (IPv6, directory documents):
5820 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5821 consensus. This information makes it easier for IPv6 clients to
5822 bootstrap and choose reachable entry guards. Implements ticket 23826.
5823 - Add consensus method 28, which removes IPv6 ORPorts from
5824 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5825 are redundant in microdescs. This change will be used by Tor clients
5826 on 0.2.8.x and later. (That is to say, with all Tor clients that
5827 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5828 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5829 set by different numbers of authorities. Fixes 23870
5832 o Major features (onion service v3, control port):
5833 - The control port now supports commands and events for v3 onion
5834 services. It is now possible to create ephemeral v3 services using
5835 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5836 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5837 DEL_ONION) have been extended to support v3 onion services. Closes
5838 ticket 20699; implements proposal 284.
5840 o Major features (onion services):
5841 - Provide torrc options to pin the second and third hops of onion
5842 service circuits to a list of nodes. The option HSLayer2Guards
5843 pins the second hop, and the option HSLayer3Guards pins the third
5844 hop. These options are for use in conjunction with experiments
5845 with "vanguards" for preventing guard enumeration attacks. Closes
5848 o Major features (rust, portability, experimental):
5849 - Tor now ships with an optional implementation of one of its
5850 smaller modules (protover.c) in the Rust programming language. To
5851 try it out, install a Rust build environment, and configure Tor
5852 with "--enable-rust --enable-cargo-online-mode". This should not
5853 cause any user-visible changes, but should help us gain more
5854 experience with Rust, and plan future Rust integration work.
5855 Implementation by Chelsea Komlo. Closes ticket 22840.
5857 o Minor features (storage, configuration):
5858 - Users can store cached directory documents somewhere other than
5859 the DataDirectory by using the CacheDirectory option. Similarly,
5860 the storage location for relay's keys can be overridden with the
5861 KeyDirectory option. Closes ticket 22703.
5863 o Major features (v3 onion services, ipv6):
5864 - When v3 onion service clients send introduce cells, they now
5865 include the IPv6 address of the rendezvous point, if it has one.
5866 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5867 in future Tor versions, IPv6-only v3 single onion services will be
5868 able to use IPv6 addresses to connect directly to the rendezvous
5869 point. Closes ticket 23577. Patch by Neel Chauhan.
5871 o Major bugfixes (onion services, retry behavior):
5872 - Fix an "off by 2" error in counting rendezvous failures on the
5873 onion service side. While we thought we would stop the rendezvous
5874 attempt after one failed circuit, we were actually making three
5875 circuit attempts before giving up. Now switch to a default of 2,
5876 and allow the consensus parameter "hs_service_max_rdv_failures" to
5877 override. Fixes bug 24895; bugfix on 0.0.6.
5878 - New-style (v3) onion services now obey the "max rendezvous circuit
5879 attempts" logic. Previously they would make as many rendezvous
5880 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5881 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5883 o Major bugfixes (relays):
5884 - Fix a set of false positives where relays would consider
5885 connections to other relays as being client-only connections (and
5886 thus e.g. deserving different link padding schemes) if those
5887 relays fell out of the consensus briefly. Now we look only at the
5888 initial handshake and whether the connection authenticated as a
5889 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5891 o Minor feature (IPv6):
5892 - Make IPv6-only clients wait for microdescs for relays, even if we
5893 were previously using descriptors (or were using them as a bridge)
5894 and have a cached descriptor for them. Implements ticket 23827.
5895 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5896 them, rather than waiting to download microdescriptors.
5897 Implements ticket 23827.
5899 o Minor features (cleanup):
5900 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5901 when it stops. Closes ticket 23271.
5903 o Minor features (defensive programming):
5904 - Most of the functions in Tor that free objects have been replaced
5905 with macros that free the objects and set the corresponding
5906 pointers to NULL. This change should help prevent a large class of
5907 dangling pointer bugs. Closes ticket 24337.
5908 - Where possible, the tor_free() macro now only evaluates its input
5909 once. Part of ticket 24337.
5910 - Check that microdesc ed25519 ids are non-zero in
5911 node_get_ed25519_id() before returning them. Implements ticket
5912 24001, patch by "aruna1234".
5914 o Minor features (embedding):
5915 - Tor can now start with a preauthenticated control connection
5916 created by the process that launched it. This feature is meant for
5917 use by programs that want to launch and manage a Tor process
5918 without allowing other programs to manage it as well. For more
5919 information, see the __OwningControllerFD option documented in
5920 control-spec.txt. Closes ticket 23900.
5921 - On most errors that would cause Tor to exit, it now tries to
5922 return from the tor_main() function, rather than calling the
5923 system exit() function. Most users won't notice a difference here,
5924 but it should be significant for programs that run Tor inside
5925 a separate thread: they should now be able to survive Tor's exit
5926 conditions rather than having Tor shut down the entire process.
5927 Closes ticket 23848.
5928 - Applications that want to embed Tor can now tell Tor not to
5929 register any of its own POSIX signal handlers, using the
5930 __DisableSignalHandlers option. Closes ticket 24588.
5932 o Minor features (fallback directory list):
5933 - Avoid selecting fallbacks that change their IP addresses too
5934 often. Select more fallbacks by ignoring the Guard flag, and
5935 allowing lower cutoffs for the Running and V2Dir flags. Also allow
5936 a lower bandwidth, and a higher number of fallbacks per operator
5937 (5% of the list). Implements ticket 24785.
5938 - Update the fallback whitelist and blacklist based on opt-ins and
5939 relay changes. Closes tickets 22321, 24678, 22527, 24135,
5942 o Minor features (fallback directory mirror configuration):
5943 - Add a nickname to each fallback in a C comment. This makes it
5944 easier for operators to find their relays, and allows stem to use
5945 nicknames to identify fallbacks. Implements ticket 24600.
5946 - Add a type and version header to the fallback directory mirror
5947 file. Also add a delimiter to the end of each fallback entry. This
5948 helps external parsers like stem and Relay Search. Implements
5950 - Add an extrainfo cache flag for each fallback in a C comment. This
5951 allows stem to use fallbacks to fetch extra-info documents, rather
5952 than using authorities. Implements ticket 22759.
5953 - Add the generateFallbackDirLine.py script for automatically
5954 generating fallback directory mirror lines from relay fingerprints.
5955 No more typos! Add the lookupFallbackDirContact.py script for
5956 automatically looking up operator contact info from relay
5957 fingerprints. Implements ticket 24706, patch by teor and atagar.
5958 - Reject any fallback directory mirror that serves an expired
5959 consensus. Implements ticket 20942, patch by "minik".
5960 - Remove commas and equals signs from external string inputs to the
5961 fallback list. This avoids format confusion attacks. Implements
5963 - Remove the "weight=10" line from fallback directory mirror
5964 entries. Ticket 24681 will maintain the current fallback weights
5965 by changing Tor's default fallback weight to 10. Implements
5967 - Stop logging excessive information about fallback netblocks.
5968 Implements ticket 24791.
5970 o Minor features (forward-compatibility):
5971 - If a relay supports some link authentication protocol that we do
5972 not recognize, then include that relay's ed25519 key when telling
5973 other relays to extend to it. Previously, we treated future
5974 versions as if they were too old to support ed25519 link
5975 authentication. Closes ticket 20895.
5977 o Minor features (heartbeat):
5978 - Add onion service information to our heartbeat logs, displaying
5979 stats about the activity of configured onion services. Closes
5982 o Minor features (instrumentation, development):
5983 - Add the MainloopStats option to allow developers to get
5984 instrumentation information from the main event loop via the
5985 heartbeat messages. We hope to use this to improve Tor's behavior
5986 when it's trying to sleep. Closes ticket 24605.
5988 o Minor features (log messages):
5989 - Improve a warning message that happens when we fail to re-parse an
5990 old router because of an expired certificate. Closes ticket 20020.
5991 - Make the log more quantitative when we hit MaxMemInQueues
5992 threshold exposing some values. Closes ticket 24501.
5994 o Minor features (logging, android):
5995 - Added support for the Android logging subsystem. Closes
5998 o Minor features (performance):
5999 - Support predictive circuit building for onion service circuits
6000 with multiple layers of guards. Closes ticket 23101.
6001 - Use stdatomic.h where available, rather than mutexes, to implement
6002 atomic_counter_t. Closes ticket 23953.
6004 o Minor features (performance, 32-bit):
6005 - Improve performance on 32-bit systems by avoiding 64-bit division
6006 when calculating the timestamp in milliseconds for channel padding
6007 computations. Implements ticket 24613.
6008 - Improve performance on 32-bit systems by avoiding 64-bit division
6009 when timestamping cells and buffer chunks for OOM calculations.
6010 Implements ticket 24374.
6012 o Minor features (performance, OSX, iOS):
6013 - Use the mach_approximate_time() function (when available) to
6014 implement coarse monotonic time. Having a coarse time function
6015 should avoid a large number of system calls, and improve
6016 performance slightly, especially under load. Closes ticket 24427.
6018 o Minor features (performance, windows):
6019 - Improve performance on Windows Vista and Windows 7 by adjusting
6020 TCP send window size according to the recommendation from
6021 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
6024 o Major features (relay):
6025 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
6026 operator to use a more reasonable ("reduced") exit policy, rather
6027 than the default one. If you want to run an exit node without
6028 thinking too hard about which ports to allow, this one is for you.
6029 Closes ticket 13605. Patch from Neel Chauhan.
6031 o Minor features (testing, debugging, embedding):
6032 - For development purposes, Tor now has a mode in which it runs for
6033 a few seconds, then stops, and starts again without exiting the
6034 process. This mode is meant to help us debug various issues with
6035 ticket 23847. To use this feature, compile with
6036 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
6037 environment variable. This is expected to crash a lot, and is
6038 really meant for developers only. It will likely be removed in a
6039 future release. Implements ticket 24583.
6041 o Minor bugfix (network IPv6 test):
6042 - Tor's test scripts now check if "ping -6 ::1" works when the user
6043 runs "make test-network-all". Fixes bug 24677; bugfix on
6044 0.2.9.3-alpha. Patch by "ffmancera".
6046 o Minor bugfixes (build, rust):
6047 - Fix output of autoconf checks to display success messages for Rust
6048 dependencies and a suitable rustc compiler version. Fixes bug
6049 24612; bugfix on 0.3.1.3-alpha.
6050 - When building with Rust on OSX, link against libresolv, to work
6051 around the issue at https://github.com/rust-lang/rust/issues/46797.
6052 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
6053 - Don't pass the --quiet option to cargo: it seems to suppress some
6054 errors, which is not what we want to do when building. Fixes bug
6055 24518; bugfix on 0.3.1.7.
6056 - Build correctly when building from outside Tor's source tree with
6057 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
6060 o Minor bugfixes (directory authorities, IPv6):
6061 - When creating a routerstatus (vote) from a routerinfo (descriptor),
6062 set the IPv6 address to the unspecified IPv6 address, and
6063 explicitly initialize the port to zero. Fixes bug 24488; bugfix
6066 o Minor bugfixes (fallback directory mirrors):
6067 - Make updateFallbackDirs.py search harder for python. (Some OSs
6068 don't put it in /usr/bin.) Fixes bug 24708; bugfix
6071 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
6072 - When hibernating, close connections normally and allow them to
6073 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
6075 - Do not attempt to launch self-reachability tests when entering
6076 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
6077 - Resolve several bugs related to descriptor fetching on bridge
6078 clients with bandwidth accounting enabled. (This combination is
6079 not recommended!) Fixes a case of bug 12062; bugfix
6081 - When hibernating, do not attempt to launch DNS checks. Fixes a
6082 case of bug 12062; bugfix on 0.1.2.2-alpha.
6083 - When hibernating, do not try to upload or download descriptors.
6084 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
6086 o Minor bugfixes (IPv6, bridges):
6087 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
6088 bugfix on 0.2.8.2-alpha.
6089 - Tor now sets IPv6 address in the routerstatus as well as in the
6090 router descriptors when updating addresses for a bridge. Closes
6091 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
6093 o Minor bugfixes (linux seccomp2 sandbox):
6094 - When running with the sandbox enabled, reload configuration files
6095 correctly even when %include was used. Previously we would crash.
6096 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
6098 o Minor bugfixes (memory leaks):
6099 - Avoid possible at-exit memory leaks related to use of Libevent's
6100 event_base_once() function. (This function tends to leak memory if
6101 the event_base is closed before the event fires.) Fixes bug 24584;
6102 bugfix on 0.2.8.1-alpha.
6103 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
6106 o Minor bugfixes (OSX):
6107 - Don't exit the Tor process if setrlimit() fails to change the file
6108 limit (which can happen sometimes on some versions of OSX). Fixes
6109 bug 21074; bugfix on 0.0.9pre5.
6111 o Minor bugfixes (performance, fragile-hardening):
6112 - Improve the performance of our consensus-diff application code
6113 when Tor is built with the --enable-fragile-hardening option set.
6114 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
6116 o Minor bugfixes (performance, timeouts):
6117 - Consider circuits for timeout as soon as they complete a hop. This
6118 is more accurate than applying the timeout in
6119 circuit_expire_building() because that function is only called
6120 once per second, which is now too slow for typical timeouts on the
6121 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
6122 - Use onion service circuits (and other circuits longer than 3 hops)
6123 to calculate a circuit build timeout. Previously, Tor only
6124 calculated its build timeout based on circuits that planned to be
6125 exactly 3 hops long. With this change, we include measurements
6126 from all circuits at the point where they complete their third
6127 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
6129 o Minor bugfixes (testing):
6130 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
6131 bugfix on 0.2.3.1-alpha.
6132 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
6133 25005; bugfix on 0.3.2.7-rc.
6135 o Code simplification and refactoring:
6136 - Remove /usr/athena from search path in configure.ac. Closes
6138 - Remove duplicate code in node_has_curve25519_onion_key() and
6139 node_get_curve25519_onion_key(), and add a check for a zero
6140 microdesc curve25519 onion key. Closes ticket 23966, patch by
6141 "aruna1234" and teor.
6142 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
6143 memory allocations with large numbers of OR connections (e.g.
6144 relays). Closes ticket 24119.
6145 - Separate the function that deletes ephemeral files when Tor
6147 - Small changes to Tor's buf_t API to make it suitable for use as a
6148 general-purpose safe string constructor. Closes ticket 22342.
6149 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
6150 avoid source code identifier confusion. Closes ticket 24467.
6151 - The tor_git_revision[] constant no longer needs to be redeclared
6152 by everything that links against the rest of Tor. Done as part of
6153 ticket 23845, to simplify our external API.
6154 - We make extend_info_from_node() use node_get_curve25519_onion_key()
6155 introduced in ticket 23577 to access the curve25519 public keys
6156 rather than accessing it directly. Closes ticket 23760. Patch by
6158 - Add a function to log channels' scheduler state changes to aid
6159 debugging efforts. Closes ticket 24531.
6162 - Add documentation on how to build tor with Rust dependencies
6163 without having to be online. Closes ticket 22907; bugfix
6165 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
6166 traffic. Closes ticket 24318.
6167 - Document that OutboundBindAddress doesn't apply to DNS requests.
6168 Closes ticket 22145. Patch from Aruna Maurya.
6169 - Document that operators who run more than one relay or bridge are
6170 expected to set MyFamily and ContactInfo correctly. Closes
6173 o Code simplification and refactoring (channels):
6174 - Remove the incoming and outgoing channel queues. These were never
6175 used, but still took up a step in our fast path.
6176 - The majority of the channel unit tests have been rewritten and the
6177 code coverage has now been raised to 83.6% for channel.c. Closes
6179 - Remove other dead code from the channel subsystem: All together,
6180 this cleanup has removed more than 1500 lines of code overall and
6181 adding very little except for unit test.
6183 o Code simplification and refactoring (circuit rendezvous):
6184 - Split the client-side rendezvous circuit lookup into two
6185 functions: one that returns only established circuits and another
6186 that returns all kinds of circuits. Closes ticket 23459.
6188 o Code simplification and refactoring (controller):
6189 - Make most of the variables in networkstatus_getinfo_by_purpose()
6190 const. Implements ticket 24489.
6193 Changes in version 0.3.2.9 - 2018-01-09
6194 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
6196 The 0.3.2 series includes our long-anticipated new onion service
6197 design, with numerous security features. (For more information, see
6198 our blog post at https://blog.torproject.org/fall-harvest.) We also
6199 have a new circuit scheduler algorithm for improved performance on
6200 relays everywhere (see https://blog.torproject.org/kist-and-tell),
6201 along with many smaller features and bugfixes.
6203 Per our stable release policy, we plan to support each stable release
6204 series for at least the next nine months, or for three months after
6205 the first stable release of the next series: whichever is longer. If
6206 you need a release with long-term support, we recommend that you stay
6207 with the 0.2.9 series.
6209 Below is a list of the changes since 0.3.2.8-rc. For a list of all
6210 changes since 0.3.1, see the ReleaseNotes file.
6212 o Minor features (fallback directory mirrors):
6213 - The fallback directory list has been re-generated based on the
6214 current status of the network. Tor uses fallback directories to
6215 bootstrap when it doesn't yet have up-to-date directory
6216 information. Closes ticket 24801.
6217 - Make the default DirAuthorityFallbackRate 0.1, so that clients
6218 prefer to bootstrap from fallback directory mirrors. This is a
6219 follow-up to 24679, which removed weights from the default
6220 fallbacks. Implements ticket 24681.
6222 o Minor features (geoip):
6223 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
6226 o Minor bugfixes (address selection):
6227 - When the fascist_firewall_choose_address_ functions don't find a
6228 reachable address, set the returned address to the null address
6229 and port. This is a precautionary measure, because some callers do
6230 not check the return value. Fixes bug 24736; bugfix
6233 o Minor bugfixes (compilation):
6234 - Resolve a few shadowed-variable warnings in the onion service
6235 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
6237 o Minor bugfixes (portability, msvc):
6238 - Fix a bug in the bit-counting parts of our timing-wheel code on
6239 MSVC. (Note that MSVC is still not a supported build platform, due
6240 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
6244 Changes in version 0.3.2.8-rc - 2017-12-21
6245 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
6246 schedulers that had led servers under heavy load to overload their
6247 outgoing connections. All relay operators running earlier 0.3.2.x
6248 versions should upgrade. This version also includes a mitigation for
6249 over-full DESTROY queues leading to out-of-memory conditions: if it
6250 works, we will soon backport it to earlier release series.
6252 This is the second release candidate in the 0.3.2 series. If we find
6253 no new bugs or regression here, then the first stable 0.3.2 release
6254 will be nearly identical to this.
6256 o Major bugfixes (KIST, scheduler):
6257 - The KIST scheduler did not correctly account for data already
6258 enqueued in each connection's send socket buffer, particularly in
6259 cases when the TCP/IP congestion window was reduced between
6260 scheduler calls. This situation lead to excessive per-connection
6261 buffering in the kernel, and a potential memory DoS. Fixes bug
6262 24665; bugfix on 0.3.2.1-alpha.
6264 o Minor features (geoip):
6265 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
6268 o Minor bugfixes (hidden service v3):
6269 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
6270 the probability of reaching a service for a client missing
6271 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
6273 o Minor bugfixes (memory usage):
6274 - When queuing DESTROY cells on a channel, only queue the circuit-id
6275 and reason fields: not the entire 514-byte cell. This fix should
6276 help mitigate any bugs or attacks that fill up these queues, and
6277 free more RAM for other uses. Fixes bug 24666; bugfix
6280 o Minor bugfixes (scheduler, KIST):
6281 - Use a sane write limit for KISTLite when writing onto a connection
6282 buffer instead of using INT_MAX and shoving as much as it can.
6283 Because the OOM handler cleans up circuit queues, we are better
6284 off at keeping them in that queue instead of the connection's
6285 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
6288 Changes in version 0.3.2.7-rc - 2017-12-14
6289 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
6290 including some that could affect reliability or correctness.
6292 This is the first release candidate in the 0.3.2 series. If we find no
6293 new bugs or regression here, then the first stable 0.3.2. release will
6294 be nearly identical to this.
6296 o Major bugfixes (circuit prediction):
6297 - Fix circuit prediction logic so that a client doesn't treat a port
6298 as being "handled" by a circuit if that circuit already has
6299 isolation settings on it. This change should make Tor clients more
6300 responsive by improving their chances of having a pre-created
6301 circuit ready for use when a request arrives. Fixes bug 18859;
6302 bugfix on 0.2.3.3-alpha.
6304 o Minor features (logging):
6305 - Provide better warnings when the getrandom() syscall fails. Closes
6308 o Minor features (portability):
6309 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
6310 (It doesn't yet work with the sandbox enabled.) Closes
6313 o Minor bugfixes (bridge clients, bootstrap):
6314 - Retry directory downloads when we get our first bridge descriptor
6315 during bootstrap or while reconnecting to the network. Keep
6316 retrying every time we get a bridge descriptor, until we have a
6317 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
6318 - Stop delaying bridge descriptor fetches when we have cached bridge
6319 descriptors. Instead, only delay bridge descriptor fetches when we
6320 have at least one reachable bridge. Fixes part of bug 24367;
6321 bugfix on 0.2.0.3-alpha.
6322 - Stop delaying directory fetches when we have cached bridge
6323 descriptors. Instead, only delay bridge descriptor fetches when
6324 all our bridges are definitely unreachable. Fixes part of bug
6325 24367; bugfix on 0.2.0.3-alpha.
6327 o Minor bugfixes (compilation):
6328 - Fix a signed/unsigned comparison warning introduced by our fix to
6329 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6331 o Minor bugfixes (correctness):
6332 - Fix several places in our codebase where a C compiler would be
6333 likely to eliminate a check, based on assuming that undefined
6334 behavior had not happened elsewhere in the code. These cases are
6335 usually a sign of redundant checking or dubious arithmetic. Found
6336 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
6337 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
6340 o Minor bugfixes (onion service v3):
6341 - Fix a race where an onion service would launch a new intro circuit
6342 after closing an old one, but fail to register it before freeing
6343 the previously closed circuit. This bug was making the service
6344 unable to find the established intro circuit and thus not upload
6345 its descriptor, thus making a service unavailable for up to 24
6346 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
6348 o Minor bugfixes (scheduler, KIST):
6349 - Properly set the scheduler state of an unopened channel in the
6350 KIST scheduler main loop. This prevents a harmless but annoying
6351 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
6352 - Avoid a possible integer overflow when computing the available
6353 space on the TCP buffer of a channel. This had no security
6354 implications; but could make KIST allow too many cells on a
6355 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
6356 - Downgrade to "info" a harmless warning about the monotonic time
6357 moving backwards: This can happen on platform not supporting
6358 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6361 Changes in version 0.3.2.6-alpha - 2017-12-01
6362 This version of Tor is the latest in the 0.3.2 alpha series. It
6363 includes fixes for several important security issues. All Tor users
6364 should upgrade to this release, or to one of the other releases coming
6367 o Major bugfixes (security):
6368 - Fix a denial of service bug where an attacker could use a
6369 malformed directory object to cause a Tor instance to pause while
6370 OpenSSL would try to read a passphrase from the terminal. (Tor
6371 instances run without a terminal, which is the case for most Tor
6372 packages, are not impacted.) Fixes bug 24246; bugfix on every
6373 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6374 Found by OSS-Fuzz as testcase 6360145429790720.
6375 - Fix a denial of service issue where an attacker could crash a
6376 directory authority using a malformed router descriptor. Fixes bug
6377 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6379 - When checking for replays in the INTRODUCE1 cell data for a
6380 (legacy) onion service, correctly detect replays in the RSA-
6381 encrypted part of the cell. We were previously checking for
6382 replays on the entire cell, but those can be circumvented due to
6383 the malleability of Tor's legacy hybrid encryption. This fix helps
6384 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6385 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6388 o Major bugfixes (security, onion service v2):
6389 - Fix a use-after-free error that could crash v2 Tor onion services
6390 when they failed to open circuits while expiring introduction
6391 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6392 also tracked as TROVE-2017-013 and CVE-2017-8823.
6394 o Major bugfixes (security, relay):
6395 - When running as a relay, make sure that we never build a path
6396 through ourselves, even in the case where we have somehow lost the
6397 version of our descriptor appearing in the consensus. Fixes part
6398 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6399 as TROVE-2017-012 and CVE-2017-8822.
6400 - When running as a relay, make sure that we never choose ourselves
6401 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6402 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6404 o Minor feature (relay statistics):
6405 - Change relay bandwidth reporting stats interval from 4 hours to 24
6406 hours in order to reduce the efficiency of guard discovery
6407 attacks. Fixes ticket 23856.
6409 o Minor features (directory authority):
6410 - Add an IPv6 address for the "bastet" directory authority. Closes
6413 o Minor bugfixes (client):
6414 - By default, do not enable storage of client-side DNS values. These
6415 values were unused by default previously, but they should not have
6416 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
6419 Changes in version 0.3.1.9 - 2017-12-01:
6420 Tor 0.3.1.9 backports important security and stability fixes from the
6421 0.3.2 development series. All Tor users should upgrade to this
6422 release, or to another of the releases coming out today.
6424 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6425 - Fix a denial of service bug where an attacker could use a
6426 malformed directory object to cause a Tor instance to pause while
6427 OpenSSL would try to read a passphrase from the terminal. (Tor
6428 instances run without a terminal, which is the case for most Tor
6429 packages, are not impacted.) Fixes bug 24246; bugfix on every
6430 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6431 Found by OSS-Fuzz as testcase 6360145429790720.
6432 - Fix a denial of service issue where an attacker could crash a
6433 directory authority using a malformed router descriptor. Fixes bug
6434 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6436 - When checking for replays in the INTRODUCE1 cell data for a
6437 (legacy) onion service, correctly detect replays in the RSA-
6438 encrypted part of the cell. We were previously checking for
6439 replays on the entire cell, but those can be circumvented due to
6440 the malleability of Tor's legacy hybrid encryption. This fix helps
6441 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6442 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6445 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6446 - Fix a use-after-free error that could crash v2 Tor onion services
6447 when they failed to open circuits while expiring introduction
6448 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6449 also tracked as TROVE-2017-013 and CVE-2017-8823.
6451 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6452 - When running as a relay, make sure that we never build a path
6453 through ourselves, even in the case where we have somehow lost the
6454 version of our descriptor appearing in the consensus. Fixes part
6455 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6456 as TROVE-2017-012 and CVE-2017-8822.
6457 - When running as a relay, make sure that we never choose ourselves
6458 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6459 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6461 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6462 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6463 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6464 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6465 identifying and finding a workaround to this bug and to Moritz,
6466 Arthur Edelstein, and Roger for helping to track it down and
6469 o Minor features (bridge):
6470 - Bridges now include notice in their descriptors that they are
6471 bridges, and notice of their distribution status, based on their
6472 publication settings. Implements ticket 18329. For more fine-
6473 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6476 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6477 - Add an IPv6 address for the "bastet" directory authority. Closes
6480 o Minor features (geoip):
6481 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6484 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6485 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6486 relays, to prevent spurious address resolutions and descriptor
6487 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6488 bugfix on in 0.2.8.1-alpha.
6490 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6491 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6492 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6494 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6495 - When a circuit is marked for close, do not attempt to package any
6496 cells for channels on that circuit. Previously, we would detect
6497 this condition lower in the call stack, when we noticed that the
6498 circuit had no attached channel, and log an annoying message.
6499 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6501 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
6502 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6503 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6506 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6507 - Avoid a crash when transitioning from client mode to bridge mode.
6508 Previously, we would launch the worker threads whenever our
6509 "public server" mode changed, but not when our "server" mode
6510 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6513 Changes in version 0.3.0.13 - 2017-12-01
6514 Tor 0.3.0.13 backports important security and stability bugfixes from
6515 later Tor releases. All Tor users should upgrade to this release, or
6516 to another of the releases coming out today.
6518 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6519 2018. If you need a release with long-term support, please stick with
6520 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6522 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6523 - Fix a denial of service bug where an attacker could use a
6524 malformed directory object to cause a Tor instance to pause while
6525 OpenSSL would try to read a passphrase from the terminal. (Tor
6526 instances run without a terminal, which is the case for most Tor
6527 packages, are not impacted.) Fixes bug 24246; bugfix on every
6528 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6529 Found by OSS-Fuzz as testcase 6360145429790720.
6530 - Fix a denial of service issue where an attacker could crash a
6531 directory authority using a malformed router descriptor. Fixes bug
6532 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6534 - When checking for replays in the INTRODUCE1 cell data for a
6535 (legacy) onion service, correctly detect replays in the RSA-
6536 encrypted part of the cell. We were previously checking for
6537 replays on the entire cell, but those can be circumvented due to
6538 the malleability of Tor's legacy hybrid encryption. This fix helps
6539 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6540 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6543 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6544 - Fix a use-after-free error that could crash v2 Tor onion services
6545 when they failed to open circuits while expiring introduction
6546 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6547 also tracked as TROVE-2017-013 and CVE-2017-8823.
6549 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6550 - When running as a relay, make sure that we never build a path
6551 through ourselves, even in the case where we have somehow lost the
6552 version of our descriptor appearing in the consensus. Fixes part
6553 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6554 as TROVE-2017-012 and CVE-2017-8822.
6555 - When running as a relay, make sure that we never choose ourselves
6556 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6557 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6559 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6560 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6561 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6562 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6563 identifying and finding a workaround to this bug and to Moritz,
6564 Arthur Edelstein, and Roger for helping to track it down and
6567 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6568 - Enable a couple of pieces of Windows hardening: one
6569 (HeapEnableTerminationOnCorruption) that has been on-by-default
6570 since Windows 8, and unavailable before Windows 7; and one
6571 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6572 affect us, but shouldn't do any harm. Closes ticket 21953.
6574 o Minor features (bridge, backport from 0.3.1.9):
6575 - Bridges now include notice in their descriptors that they are
6576 bridges, and notice of their distribution status, based on their
6577 publication settings. Implements ticket 18329. For more fine-
6578 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6581 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6582 - Add an IPv6 address for the "bastet" directory authority. Closes
6585 o Minor features (geoip):
6586 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6589 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6590 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6591 relays, to prevent spurious address resolutions and descriptor
6592 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6593 bugfix on in 0.2.8.1-alpha.
6595 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6596 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6597 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6599 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6600 - When a circuit is marked for close, do not attempt to package any
6601 cells for channels on that circuit. Previously, we would detect
6602 this condition lower in the call stack, when we noticed that the
6603 circuit had no attached channel, and log an annoying message.
6604 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6606 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6607 - Avoid a crash when transitioning from client mode to bridge mode.
6608 Previously, we would launch the worker threads whenever our
6609 "public server" mode changed, but not when our "server" mode
6610 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6612 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6613 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6614 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6617 Changes in version 0.2.9.14 - 2017-12-01
6618 Tor 0.3.0.13 backports important security and stability bugfixes from
6619 later Tor releases. All Tor users should upgrade to this release, or
6620 to another of the releases coming out today.
6622 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6623 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6624 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6625 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6626 identifying and finding a workaround to this bug and to Moritz,
6627 Arthur Edelstein, and Roger for helping to track it down and
6630 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6631 - Fix a denial of service bug where an attacker could use a
6632 malformed directory object to cause a Tor instance to pause while
6633 OpenSSL would try to read a passphrase from the terminal. (Tor
6634 instances run without a terminal, which is the case for most Tor
6635 packages, are not impacted.) Fixes bug 24246; bugfix on every
6636 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6637 Found by OSS-Fuzz as testcase 6360145429790720.
6638 - Fix a denial of service issue where an attacker could crash a
6639 directory authority using a malformed router descriptor. Fixes bug
6640 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6642 - When checking for replays in the INTRODUCE1 cell data for a
6643 (legacy) onion service, correctly detect replays in the RSA-
6644 encrypted part of the cell. We were previously checking for
6645 replays on the entire cell, but those can be circumvented due to
6646 the malleability of Tor's legacy hybrid encryption. This fix helps
6647 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6648 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6651 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6652 - Fix a use-after-free error that could crash v2 Tor onion services
6653 when they failed to open circuits while expiring introduction
6654 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6655 also tracked as TROVE-2017-013 and CVE-2017-8823.
6657 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6658 - When running as a relay, make sure that we never build a path
6659 through ourselves, even in the case where we have somehow lost the
6660 version of our descriptor appearing in the consensus. Fixes part
6661 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6662 as TROVE-2017-012 and CVE-2017-8822.
6664 o Minor features (bridge, backport from 0.3.1.9):
6665 - Bridges now include notice in their descriptors that they are
6666 bridges, and notice of their distribution status, based on their
6667 publication settings. Implements ticket 18329. For more fine-
6668 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6671 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6672 - Add an IPv6 address for the "bastet" directory authority. Closes
6675 o Minor features (geoip):
6676 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6679 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6680 - Enable a couple of pieces of Windows hardening: one
6681 (HeapEnableTerminationOnCorruption) that has been on-by-default
6682 since Windows 8, and unavailable before Windows 7; and one
6683 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6684 affect us, but shouldn't do any harm. Closes ticket 21953.
6686 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6687 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6688 relays, to prevent spurious address resolutions and descriptor
6689 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6690 bugfix on in 0.2.8.1-alpha.
6692 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6693 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6694 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6696 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6697 - When a circuit is marked for close, do not attempt to package any
6698 cells for channels on that circuit. Previously, we would detect
6699 this condition lower in the call stack, when we noticed that the
6700 circuit had no attached channel, and log an annoying message.
6701 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6703 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6704 - Avoid a crash when transitioning from client mode to bridge mode.
6705 Previously, we would launch the worker threads whenever our
6706 "public server" mode changed, but not when our "server" mode
6707 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6709 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6710 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6711 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6714 Changes in version 0.2.8.17 - 2017-12-01
6715 Tor 0.2.8.17 backports important security and stability bugfixes from
6716 later Tor releases. All Tor users should upgrade to this release, or
6717 to another of the releases coming out today.
6719 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6720 2018. If you need a release with long-term support, please upgrade with
6721 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6723 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6724 - Fix a denial of service bug where an attacker could use a
6725 malformed directory object to cause a Tor instance to pause while
6726 OpenSSL would try to read a passphrase from the terminal. (Tor
6727 instances run without a terminal, which is the case for most Tor
6728 packages, are not impacted.) Fixes bug 24246; bugfix on every
6729 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6730 Found by OSS-Fuzz as testcase 6360145429790720.
6731 - When checking for replays in the INTRODUCE1 cell data for a
6732 (legacy) onion service, correctly detect replays in the RSA-
6733 encrypted part of the cell. We were previously checking for
6734 replays on the entire cell, but those can be circumvented due to
6735 the malleability of Tor's legacy hybrid encryption. This fix helps
6736 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6737 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6740 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6741 - Fix a use-after-free error that could crash v2 Tor onion services
6742 when they failed to open circuits while expiring introduction
6743 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6744 also tracked as TROVE-2017-013 and CVE-2017-8823.
6746 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6747 - When running as a relay, make sure that we never build a path through
6748 ourselves, even in the case where we have somehow lost the version of
6749 our descriptor appearing in the consensus. Fixes part of bug 21534;
6750 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6753 o Minor features (bridge, backport from 0.3.1.9):
6754 - Bridges now include notice in their descriptors that they are
6755 bridges, and notice of their distribution status, based on their
6756 publication settings. Implements ticket 18329. For more fine-
6757 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6760 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6761 - Add an IPv6 address for the "bastet" directory authority. Closes
6764 o Minor features (geoip):
6765 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6768 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6769 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6770 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6773 Changes in version 0.2.5.16 - 2017-12-01
6774 Tor 0.2.5.13 backports important security and stability bugfixes from
6775 later Tor releases. All Tor users should upgrade to this release, or
6776 to another of the releases coming out today.
6778 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6779 2018. If you need a release with long-term support, please upgrade to
6780 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6782 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6783 - Fix a denial of service bug where an attacker could use a
6784 malformed directory object to cause a Tor instance to pause while
6785 OpenSSL would try to read a passphrase from the terminal. (Tor
6786 instances run without a terminal, which is the case for most Tor
6787 packages, are not impacted.) Fixes bug 24246; bugfix on every
6788 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6789 Found by OSS-Fuzz as testcase 6360145429790720.
6790 - When checking for replays in the INTRODUCE1 cell data for a
6791 (legacy) onion service, correctly detect replays in the RSA-
6792 encrypted part of the cell. We were previously checking for
6793 replays on the entire cell, but those can be circumvented due to
6794 the malleability of Tor's legacy hybrid encryption. This fix helps
6795 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6796 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6799 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6800 - When running as a relay, make sure that we never build a path
6801 through ourselves, even in the case where we have somehow lost the
6802 version of our descriptor appearing in the consensus. Fixes part
6803 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6804 as TROVE-2017-012 and CVE-2017-8822.
6806 o Minor features (bridge, backport from 0.3.1.9):
6807 - Bridges now include notice in their descriptors that they are
6808 bridges, and notice of their distribution status, based on their
6809 publication settings. Implements ticket 18329. For more fine-
6810 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6813 o Minor features (geoip):
6814 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6818 Changes in version 0.3.2.5-alpha - 2017-11-22
6819 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6820 fixes several stability and reliability bugs, including a fix for
6821 intermittent bootstrapping failures that some people have been seeing
6822 since the 0.3.0.x series.
6824 Please test this alpha out -- many of these fixes will soon be
6825 backported to stable Tor versions if no additional bugs are found
6828 o Major bugfixes (bootstrapping):
6829 - Fetch descriptors aggressively whenever we lack enough to build
6830 circuits, regardless of how many descriptors we are missing.
6831 Previously, we would delay launching the fetch when we had fewer
6832 than 15 missing descriptors, even if some of those descriptors
6833 were blocking circuits from building. Fixes bug 23985; bugfix on
6834 0.1.1.11-alpha. The effects of this bug became worse in
6835 0.3.0.3-alpha, when we began treating missing descriptors from our
6836 primary guards as a reason to delay circuits.
6837 - Don't try fetching microdescriptors from relays that have failed
6838 to deliver them in the past. Fixes bug 23817; bugfix
6841 o Minor features (directory authority):
6842 - Make the "Exit" flag assignment only depend on whether the exit
6843 policy allows connections to ports 80 and 443. Previously relays
6844 would get the Exit flag if they allowed connections to one of
6845 these ports and also port 6667. Resolves ticket 23637.
6847 o Minor features (geoip):
6848 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6851 o Minor features (linux seccomp2 sandbox):
6852 - Update the sandbox rules so that they should now work correctly
6853 with Glibc 2.26. Closes ticket 24315.
6855 o Minor features (logging):
6856 - Downgrade a pair of log messages that could occur when an exit's
6857 resolver gave us an unusual (but not forbidden) response. Closes
6859 - Improve the message we log when re-enabling circuit build timeouts
6860 after having received a consensus. Closes ticket 20963.
6862 o Minor bugfixes (compilation):
6863 - Fix a memory leak warning in one of the libevent-related
6864 configuration tests that could occur when manually specifying
6865 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6866 Found and patched by Alex Xu.
6867 - When detecting OpenSSL on Windows from our configure script, make
6868 sure to try linking with the ws2_32 library. Fixes bug 23783;
6869 bugfix on 0.3.2.2-alpha.
6871 o Minor bugfixes (control port, linux seccomp2 sandbox):
6872 - Avoid a crash when attempting to use the seccomp2 sandbox together
6873 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6876 o Minor bugfixes (control port, onion services):
6877 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6878 HS_DESC event when a service is not able to upload a descriptor.
6879 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6881 o Minor bugfixes (directory cache):
6882 - Recover better from empty or corrupt files in the consensus cache
6883 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6884 - When a consensus diff calculation is only partially successful,
6885 only record the successful parts as having succeeded. Partial
6886 success can happen if (for example) one compression method fails
6887 but the others succeed. Previously we misrecorded all the
6888 calculations as having succeeded, which would later cause a
6889 nonfatal assertion failure. Fixes bug 24086; bugfix
6892 o Minor bugfixes (logging):
6893 - Only log once if we notice that KIST support is gone. Fixes bug
6894 24158; bugfix on 0.3.2.1-alpha.
6895 - Suppress a log notice when relay descriptors arrive. We already
6896 have a bootstrap progress for this so no need to log notice
6897 everytime tor receives relay descriptors. Microdescriptors behave
6898 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6900 o Minor bugfixes (network layer):
6901 - When closing a connection via close_connection_immediately(), we
6902 mark it as "not blocked on bandwidth", to prevent later calls from
6903 trying to unblock it, and give it permission to read. This fixes a
6904 backtrace warning that can happen on relays under various
6905 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6907 o Minor bugfixes (onion services):
6908 - The introduction circuit was being timed out too quickly while
6909 waiting for the rendezvous circuit to complete. Keep the intro
6910 circuit around longer instead of timing out and reopening new ones
6911 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6912 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6913 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6915 - Silence a warning about failed v3 onion descriptor uploads that
6916 can happen naturally under certain edge cases. Fixes part of bug
6917 23662; bugfix on 0.3.2.1-alpha.
6919 o Minor bugfixes (tests):
6920 - Fix a memory leak in one of the bridge-distribution test cases.
6921 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
6922 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
6923 to correctly handle cases where a caller gives it an RSA key of
6924 under 160 bits. (This is not actually a bug in Tor itself, but
6925 rather in our fuzzing code.) Fixes bug 24247; bugfix on
6926 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
6929 - Add notes in man page regarding OS support for the various
6930 scheduler types. Attempt to use less jargon in the scheduler
6931 section. Closes ticket 24254.
6934 Changes in version 0.3.2.4-alpha - 2017-11-08
6935 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
6936 It fixes several stability and reliability bugs, especially including
6937 a major reliability issue that has been plaguing fast exit relays in
6940 o Major bugfixes (exit relays, DNS):
6941 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6942 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6943 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6944 identifying and finding a workaround to this bug and to Moritz,
6945 Arthur Edelstein, and Roger for helping to track it down and
6948 o Major bugfixes (scheduler, channel):
6949 - Stop processing scheduled channels if they closed while flushing
6950 cells. This can happen if the write on the connection fails
6951 leading to the channel being closed while in the scheduler loop.
6952 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
6954 o Minor features (logging, scheduler):
6955 - Introduce a SCHED_BUG() function to log extra information about
6956 the scheduler state if we ever catch a bug in the scheduler.
6957 Closes ticket 23753.
6959 o Minor features (removed deprecations):
6960 - The ClientDNSRejectInternalAddresses flag can once again be set in
6961 non-testing Tor networks, so long as they do not use the default
6962 directory authorities. This change also removes the deprecation of
6963 this flag from 0.2.9.2-alpha. Closes ticket 21031.
6965 o Minor features (testing):
6966 - Our fuzzing tests now test the encrypted portions of v3 onion
6967 service descriptors. Implements more of 21509.
6969 o Minor bugfixes (directory client):
6970 - On failure to download directory information, delay retry attempts
6971 by a random amount based on the "decorrelated jitter" algorithm.
6972 Our previous delay algorithm tended to produce extra-long delays
6973 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
6975 o Minor bugfixes (IPv6, v3 single onion services):
6976 - Remove buggy code for IPv6-only v3 single onion services, and
6977 reject attempts to configure them. This release supports IPv4,
6978 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
6979 stack v3 single onion services. Fixes bug 23820; bugfix
6982 o Minor bugfixes (logging, relay):
6983 - Give only a protocol warning when the ed25519 key is not
6984 consistent between the descriptor and microdescriptor of a relay.
6985 This can happen, for instance, if the relay has been flagged
6986 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
6988 o Minor bugfixes (manpage, onion service):
6989 - Document that the HiddenServiceNumIntroductionPoints option is
6990 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
6991 bugfix on 0.3.2.1-alpha.
6993 o Minor bugfixes (memory leaks):
6994 - Fix a minor memory leak at exit in the KIST scheduler. This bug
6995 should have no user-visible impact. Fixes bug 23774; bugfix
6997 - Fix a memory leak when decrypting a badly formatted v3 onion
6998 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
6999 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
7001 o Minor bugfixes (onion services):
7002 - Cache some needed onion service client information instead of
7003 constantly computing it over and over again. Fixes bug 23623;
7004 bugfix on 0.3.2.1-alpha.
7005 - Properly retry HSv3 descriptor fetches when missing required
7006 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
7008 o Minor bugfixes (path selection):
7009 - When selecting relays by bandwidth, avoid a rounding error that
7010 could sometimes cause load to be imbalanced incorrectly.
7011 Previously, we would always round upwards; now, we round towards
7012 the nearest integer. This had the biggest effect when a relay's
7013 weight adjustments should have given it weight 0, but it got
7014 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7015 - When calculating the fraction of nodes that have descriptors, and
7016 all nodes in the network have zero bandwidths, count the number of
7017 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7018 - Actually log the total bandwidth in compute_weighted_bandwidths().
7019 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7021 o Minor bugfixes (relay, crash):
7022 - Avoid a crash when transitioning from client mode to bridge mode.
7023 Previously, we would launch the worker threads whenever our
7024 "public server" mode changed, but not when our "server" mode
7025 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
7027 o Minor bugfixes (testing):
7028 - Fix a spurious fuzzing-only use of an uninitialized value. Found
7029 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
7030 - Test that IPv6-only clients can use microdescriptors when running
7031 "make test-network-all". Requires chutney master 61c28b9 or later.
7032 Closes ticket 24109.
7035 Changes in version 0.3.2.3-alpha - 2017-10-27
7036 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
7037 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
7038 directory authority, Bastet.
7040 o Directory authority changes:
7041 - Add "Bastet" as a ninth directory authority to the default list.
7042 Closes ticket 23910.
7043 - The directory authority "Longclaw" has changed its IP address.
7044 Closes ticket 23592.
7046 o Minor features (bridge):
7047 - Bridge relays can now set the BridgeDistribution config option to
7048 add a "bridge-distribution-request" line to their bridge
7049 descriptor, which tells BridgeDB how they'd like their bridge
7050 address to be given out. (Note that as of Oct 2017, BridgeDB does
7051 not yet implement this feature.) As a side benefit, this feature
7052 provides a way to distinguish bridge descriptors from non-bridge
7053 descriptors. Implements tickets 18329.
7055 o Minor features (client, entry guards):
7056 - Improve log messages when missing descriptors for primary guards.
7057 Resolves ticket 23670.
7059 o Minor features (geoip):
7060 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7063 o Minor bugfixes (bridge):
7064 - Overwrite the bridge address earlier in the process of retrieving
7065 its descriptor, to make sure we reach it on the configured
7066 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
7068 o Minor bugfixes (documentation):
7069 - Document better how to read gcov, and what our gcov postprocessing
7070 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
7072 o Minor bugfixes (entry guards):
7073 - Tor now updates its guard state when it reads a consensus
7074 regardless of whether it's missing descriptors. That makes tor use
7075 its primary guards to fetch descriptors in some edge cases where
7076 it would previously have used fallback directories. Fixes bug
7077 23862; bugfix on 0.3.0.1-alpha.
7079 o Minor bugfixes (hidden service client):
7080 - When handling multiple SOCKS request for the same .onion address,
7081 only fetch the service descriptor once.
7082 - When a descriptor fetch fails with a non-recoverable error, close
7083 all pending SOCKS requests for that .onion. Fixes bug 23653;
7084 bugfix on 0.3.2.1-alpha.
7086 o Minor bugfixes (hidden service):
7087 - Always regenerate missing hidden service public key files. Prior
7088 to this, if the public key was deleted from disk, it wouldn't get
7089 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
7091 - Make sure that we have a usable ed25519 key when the intro point
7092 relay supports ed25519 link authentication. Fixes bug 24002;
7093 bugfix on 0.3.2.1-alpha.
7095 o Minor bugfixes (hidden service, v2):
7096 - When reloading configured hidden services, copy all information
7097 from the old service object. Previously, some data was omitted,
7098 causing delays in descriptor upload, and other bugs. Fixes bug
7099 23790; bugfix on 0.2.1.9-alpha.
7101 o Minor bugfixes (memory safety, defensive programming):
7102 - Clear the target address when node_get_prim_orport() returns
7103 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7105 o Minor bugfixes (relay):
7106 - Avoid a BUG warning when receiving a dubious CREATE cell while an
7107 option transition is in progress. Fixes bug 23952; bugfix
7110 o Minor bugfixes (testing):
7111 - Adjust the GitLab CI configuration to more closely match that of
7112 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
7113 - Prevent scripts/test/coverage from attempting to move gcov output
7114 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
7115 - When running unit tests as root, skip a test that would fail
7116 because it expects a permissions error. This affects some
7117 continuous integration setups. Fixes bug 23758; bugfix
7119 - Stop unconditionally mirroring the tor repository in GitLab CI.
7120 This prevented developers from enabling GitLab CI on master. Fixes
7121 bug 23755; bugfix on 0.3.2.2-alpha.
7122 - Fix the hidden service v3 descriptor decoding fuzzing to use the
7123 latest decoding API correctly. Fixes bug 21509; bugfix
7126 o Minor bugfixes (warnings):
7127 - When we get an HTTP request on a SOCKS port, tell the user about
7128 the new HTTPTunnelPort option. Previously, we would give a "Tor is
7129 not an HTTP Proxy" message, which stopped being true when
7130 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
7134 Changes in version 0.2.5.15 - 2017-10-25
7135 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
7136 series. It also adds a new directory authority, Bastet.
7138 Note: the Tor 0.2.5 series will no longer be supported after 1 May
7139 2018. If you need a release with long-term support, please upgrade to
7140 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7142 o Directory authority changes:
7143 - Add "Bastet" as a ninth directory authority to the default list.
7144 Closes ticket 23910.
7145 - The directory authority "Longclaw" has changed its IP address.
7146 Closes ticket 23592.
7148 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7149 - Avoid an assertion failure bug affecting our implementation of
7150 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7151 handling of "0xx" differs from what we had expected. Fixes bug
7152 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7154 o Minor features (geoip):
7155 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7158 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7159 - Fix a memset() off the end of an array when packing cells. This
7160 bug should be harmless in practice, since the corrupted bytes are
7161 still in the same structure, and are always padding bytes,
7162 ignored, or immediately overwritten, depending on compiler
7163 behavior. Nevertheless, because the memset()'s purpose is to make
7164 sure that any other cell-handling bugs can't expose bytes to the
7165 network, we need to fix it. Fixes bug 22737; bugfix on
7166 0.2.4.11-alpha. Fixes CID 1401591.
7168 o Build features (backport from 0.3.1.5-alpha):
7169 - Tor's repository now includes a Travis Continuous Integration (CI)
7170 configuration file (.travis.yml). This is meant to help new
7171 developers and contributors who fork Tor to a Github repository be
7172 better able to test their changes, and understand what we expect
7173 to pass. To use this new build feature, you must fork Tor to your
7174 Github account, then go into the "Integrations" menu in the
7175 repository settings for your fork and enable Travis, then push
7176 your changes. Closes ticket 22636.
7179 Changes in version 0.2.8.16 - 2017-10-25
7180 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
7181 series, including a bugfix for a crash issue that had affected relays
7182 under memory pressure. It also adds a new directory authority, Bastet.
7184 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
7185 2018. If you need a release with long-term support, please stick with
7186 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7188 o Directory authority changes:
7189 - Add "Bastet" as a ninth directory authority to the default list.
7190 Closes ticket 23910.
7191 - The directory authority "Longclaw" has changed its IP address.
7192 Closes ticket 23592.
7194 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7195 - Fix a timing-based assertion failure that could occur when the
7196 circuit out-of-memory handler freed a connection's output buffer.
7197 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7199 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7200 - Remove longclaw's IPv6 address, as it will soon change. Authority
7201 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7202 3/8 directory authorities with IPv6 addresses, but there are also
7203 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7205 o Minor features (geoip):
7206 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7210 Changes in version 0.2.9.13 - 2017-10-25
7211 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
7212 series, including a bugfix for a crash issue that had affected relays
7213 under memory pressure. It also adds a new directory authority, Bastet.
7215 o Directory authority changes:
7216 - Add "Bastet" as a ninth directory authority to the default list.
7217 Closes ticket 23910.
7218 - The directory authority "Longclaw" has changed its IP address.
7219 Closes ticket 23592.
7221 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7222 - Fix a timing-based assertion failure that could occur when the
7223 circuit out-of-memory handler freed a connection's output buffer.
7224 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7226 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7227 - Remove longclaw's IPv6 address, as it will soon change. Authority
7228 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7229 3/8 directory authorities with IPv6 addresses, but there are also
7230 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7232 o Minor features (geoip):
7233 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7236 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7237 - When a directory authority rejects a descriptor or extrainfo with
7238 a given digest, mark that digest as undownloadable, so that we do
7239 not attempt to download it again over and over. We previously
7240 tried to avoid downloading such descriptors by other means, but we
7241 didn't notice if we accidentally downloaded one anyway. This
7242 behavior became problematic in 0.2.7.2-alpha, when authorities
7243 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7246 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7247 - Clear the address when node_get_prim_orport() returns early.
7248 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7250 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7251 - When running as a Windows service, set the ID of the main thread
7252 correctly. Failure to do so made us fail to send log messages to
7253 the controller in 0.2.1.16-rc, slowed down controller event
7254 delivery in 0.2.7.3-rc and later, and crash with an assertion
7255 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7256 Patch and diagnosis from "Vort".
7259 Changes in version 0.3.0.12 - 2017-10-25
7260 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
7261 series, including a bugfix for a crash issue that had affected relays
7262 under memory pressure. It also adds a new directory authority, Bastet.
7264 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
7265 2018. If you need a release with long-term support, please stick with
7266 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7268 o Directory authority changes:
7269 - Add "Bastet" as a ninth directory authority to the default list.
7270 Closes ticket 23910.
7271 - The directory authority "Longclaw" has changed its IP address.
7272 Closes ticket 23592.
7274 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7275 - Fix a timing-based assertion failure that could occur when the
7276 circuit out-of-memory handler freed a connection's output buffer.
7277 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7279 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7280 - Remove longclaw's IPv6 address, as it will soon change. Authority
7281 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7282 3/8 directory authorities with IPv6 addresses, but there are also
7283 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7285 o Minor features (geoip):
7286 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7289 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7290 - When a directory authority rejects a descriptor or extrainfo with
7291 a given digest, mark that digest as undownloadable, so that we do
7292 not attempt to download it again over and over. We previously
7293 tried to avoid downloading such descriptors by other means, but we
7294 didn't notice if we accidentally downloaded one anyway. This
7295 behavior became problematic in 0.2.7.2-alpha, when authorities
7296 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7299 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7300 - Avoid a possible double close of a circuit by the intro point on
7301 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7302 bugfix on 0.3.0.1-alpha.
7304 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7305 - Clear the address when node_get_prim_orport() returns early.
7306 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7308 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7309 - When running as a Windows service, set the ID of the main thread
7310 correctly. Failure to do so made us fail to send log messages to
7311 the controller in 0.2.1.16-rc, slowed down controller event
7312 delivery in 0.2.7.3-rc and later, and crash with an assertion
7313 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7314 Patch and diagnosis from "Vort".
7317 Changes in version 0.3.1.8 - 2017-10-25
7318 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7319 It includes several bugfixes, including a bugfix for a crash issue
7320 that had affected relays under memory pressure. It also adds
7321 a new directory authority, Bastet.
7323 o Directory authority changes:
7324 - Add "Bastet" as a ninth directory authority to the default list.
7325 Closes ticket 23910.
7326 - The directory authority "Longclaw" has changed its IP address.
7327 Closes ticket 23592.
7329 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7330 - Fix a timing-based assertion failure that could occur when the
7331 circuit out-of-memory handler freed a connection's output buffer.
7332 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7334 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7335 - Remove longclaw's IPv6 address, as it will soon change. Authority
7336 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7337 3/8 directory authorities with IPv6 addresses, but there are also
7338 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7340 o Minor features (geoip):
7341 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7344 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
7345 - Fix a compilation warning when building with zstd support on
7346 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7347 and fixed by Andreas Stieger.
7349 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
7350 - Handle a pathological case when decompressing Zstandard data when
7351 the output buffer size is zero. Fixes bug 23551; bugfix
7354 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
7355 - Remove the length limit on HTTP status lines that authorities can
7356 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
7358 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7359 - Avoid a possible double close of a circuit by the intro point on
7360 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7361 bugfix on 0.3.0.1-alpha.
7363 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7364 - Clear the address when node_get_prim_orport() returns early.
7365 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7367 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
7368 - Fix additional channelpadding unit test failures by using mocked
7369 time instead of actual time for all tests. Fixes bug 23608; bugfix
7373 Changes in version 0.3.2.2-alpha - 2017-09-29
7374 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
7375 release fixes several minor bugs in the new scheduler and next-
7376 generation onion services; both features were newly added in the 0.3.2
7377 series. Other fixes in this alpha include several fixes for non-fatal
7378 tracebacks which would appear in logs.
7380 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
7381 alpha does not contain any substantial new features. Minor features
7382 include better testing and logging.
7384 The following comprises the complete list of changes included
7387 o Major bugfixes (relay, crash, assertion failure):
7388 - Fix a timing-based assertion failure that could occur when the
7389 circuit out-of-memory handler freed a connection's output buffer.
7390 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7392 o Major bugfixes (scheduler):
7393 - If a channel is put into the scheduler's pending list, then it
7394 starts closing, and then if the scheduler runs before it finishes
7395 closing, the scheduler will get stuck trying to flush its cells
7396 while the lower layers refuse to cooperate. Fix that race
7397 condition by giving the scheduler an escape method. Fixes bug
7398 23676; bugfix on 0.3.2.1-alpha.
7400 o Minor features (build, compilation):
7401 - The "check-changes" feature is now part of the "make check" tests;
7402 we'll use it to try to prevent misformed changes files from
7403 accumulating. Closes ticket 23564.
7404 - Tor builds should now fail if there are any mismatches between the
7405 C type representing a configuration variable and the C type the
7406 data-driven parser uses to store a value there. Previously, we
7407 needed to check these by hand, which sometimes led to mistakes.
7408 Closes ticket 23643.
7410 o Minor features (directory authorities):
7411 - Remove longclaw's IPv6 address, as it will soon change. Authority
7412 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7413 3/8 directory authorities with IPv6 addresses, but there are also
7414 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7416 o Minor features (hidden service, circuit, logging):
7417 - Improve logging of many callsite in the circuit subsystem to print
7418 the circuit identifier(s).
7419 - Log when we cleanup an intro point from a service so we know when
7420 and for what reason it happened. Closes ticket 23604.
7422 o Minor features (logging):
7423 - Log more circuit information whenever we are about to try to
7424 package a relay cell on a circuit with a nonexistent n_chan.
7425 Attempt to diagnose ticket 8185.
7426 - Improve info-level log identification of particular circuits, to
7427 help with debugging. Closes ticket 23645.
7429 o Minor features (relay):
7430 - When choosing which circuits can be expired as unused, consider
7431 circuits from clients even if those clients used regular CREATE
7432 cells to make them; and do not consider circuits from relays even
7433 if they were made with CREATE_FAST. Part of ticket 22805.
7435 o Minor features (robustness):
7436 - Change several fatal assertions when flushing buffers into non-
7437 fatal assertions, to prevent any recurrence of 23690.
7439 o Minor features (spec conformance, bridge, diagnostic):
7440 - When handling the USERADDR command on an ExtOrPort, warn when the
7441 transports provides a USERADDR with no port. In a future version,
7442 USERADDR commands of this format may be rejected. Detects problems
7443 related to ticket 23080.
7445 o Minor features (testing):
7446 - Add a unit test to make sure that our own generated platform
7447 string will be accepted by directory authorities. Closes
7450 o Minor bugfixes (bootstrapping):
7451 - When warning about state file clock skew, report the correct
7452 direction for the detected skew. Fixes bug 23606; bugfix
7454 - Avoid an assertion failure when logging a state file clock skew
7455 very early in bootstrapping. Fixes bug 23607; bugfix
7458 o Minor bugfixes (build, compilation):
7459 - Fix a compilation warning when building with zstd support on
7460 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7461 and fixed by Andreas Stieger.
7462 - When searching for OpenSSL, don't accept any OpenSSL library that
7463 lacks TLSv1_1_method(): Tor doesn't build with those versions.
7464 Additionally, look in /usr/local/opt/openssl, if it's present.
7465 These changes together repair the default build on OSX systems
7466 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
7468 o Minor bugfixes (compression):
7469 - Handle a pathological case when decompressing Zstandard data when
7470 the output buffer size is zero. Fixes bug 23551; bugfix
7473 o Minor bugfixes (documentation):
7474 - Fix manpage to not refer to the obsolete (and misspelled)
7475 UseEntryGuardsAsDirectoryGuards parameter in the description of
7476 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
7478 o Minor bugfixes (hidden service v3):
7479 - Don't log an assertion failure when we can't find the right
7480 information to extend to an introduction point. In rare cases,
7481 this could happen, causing a warning, even though tor would
7482 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
7483 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
7484 much bigger so the rendezvous point can't distinguish which hidden
7485 service protocol is being used. Fixes bug 23420; bugfix
7488 o Minor bugfixes (hidden service, relay):
7489 - Avoid a possible double close of a circuit by the intro point on
7490 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7491 bugfix on 0.3.0.1-alpha.
7493 o Minor bugfixes (logging, relay shutdown, annoyance):
7494 - When a circuit is marked for close, do not attempt to package any
7495 cells for channels on that circuit. Previously, we would detect
7496 this condition lower in the call stack, when we noticed that the
7497 circuit had no attached channel, and log an annoying message.
7498 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
7500 o Minor bugfixes (scheduler):
7501 - When switching schedulers due to a consensus change, we didn't
7502 give the new scheduler a chance to react to the consensus. Fix
7503 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
7504 - Make the KISTSchedRunInterval option a non negative value. With
7505 this, the way to disable KIST through the consensus is to set it
7506 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
7507 - Only notice log the selected scheduler when we switch scheduler
7508 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
7509 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
7510 by a different tv_usec data type. Fixes bug 23575; bugfix
7512 - Make a hard exit if tor is unable to pick a scheduler which can
7513 happen if the user specifies a scheduler type that is not
7514 supported and not other types in Schedulers. Fixes bug 23581;
7515 bugfix on 0.3.2.1-alpha.
7516 - Properly initialize the scheduler last run time counter so it is
7517 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
7519 o Minor bugfixes (testing):
7520 - Capture and detect several "Result does not fit" warnings in unit
7521 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
7523 - Fix additional channelpadding unit test failures by using mocked
7524 time instead of actual time for all tests. Fixes bug 23608; bugfix
7526 - The removal of some old scheduler options caused some tests to
7527 fail on BSD systems. Assume current behavior is correct and make
7528 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
7530 o Code simplification and refactoring:
7531 - Remove various ways of testing circuits and connections for
7532 "clientness"; instead, favor channel_is_client(). Part of
7535 o Deprecated features:
7536 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
7537 now deprecated; they do not apply to relays, and they have had no
7538 effect on clients since 0.2.8.x. Closes ticket 19704.
7541 - HiddenServiceVersion man page entry wasn't mentioning the now
7542 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
7543 - Clarify that the Address option is entirely about setting an
7544 advertised IPv4 address. Closes ticket 18891.
7545 - Clarify the manpage's use of the term "address" to clarify what
7546 kind of address is intended. Closes ticket 21405.
7547 - Document that onion service subdomains are allowed, and ignored.
7548 Closes ticket 18736.
7551 Changes in version 0.3.2.1-alpha - 2017-09-18
7552 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
7553 includes support for our next-generation ("v3") onion service
7554 protocol, and adds a new circuit scheduler for more responsive
7555 forwarding decisions from relays. There are also numerous other small
7556 features and bugfixes here.
7558 Below are the changes since Tor 0.3.1.7.
7560 o Major feature (scheduler, channel):
7561 - Tor now uses new schedulers to decide which circuits should
7562 deliver cells first, in order to improve congestion at relays. The
7563 first type is called "KIST" ("Kernel Informed Socket Transport"),
7564 and is only available on Linux-like systems: it uses feedback from
7565 the kernel to prevent the kernel's TCP buffers from growing too
7566 full. The second new scheduler type is called "KISTLite": it
7567 behaves the same as KIST, but runs on systems without kernel
7568 support for inspecting TCP implementation details. The old
7569 scheduler is still available, under the name "Vanilla". To change
7570 the default scheduler preference order, use the new "Schedulers"
7571 option. (The default preference order is "KIST,KISTLite,Vanilla".)
7573 Matt Traudt implemented KIST, based on research by Rob Jansen,
7574 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
7575 more information, see the design paper at
7576 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
7577 followup implementation paper at https://arxiv.org/abs/1709.01044.
7578 Closes ticket 12541.
7580 o Major features (next-generation onion services):
7581 - Tor now supports the next-generation onion services protocol for
7582 clients and services! As part of this release, the core of
7583 proposal 224 has been implemented and is available for
7584 experimentation and testing by our users. This newer version of
7585 onion services ("v3") features many improvements over the legacy
7588 a) Better crypto (replaced SHA1/DH/RSA1024
7589 with SHA3/ed25519/curve25519)
7591 b) Improved directory protocol, leaking much less information to
7594 c) Improved directory protocol, with smaller surface for
7597 d) Better onion address security against impersonation.
7599 e) More extensible introduction/rendezvous protocol.
7601 f) A cleaner and more modular codebase.
7603 You can identify a next-generation onion address by its length:
7604 they are 56 characters long, as in
7605 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
7607 In the future, we will release more options and features for v3
7608 onion services, but we first need a testing period, so that the
7609 current codebase matures and becomes more robust. Planned features
7610 include: offline keys, advanced client authorization, improved
7611 guard algorithms, and statistics. For full details, see
7614 Legacy ("v2") onion services will still work for the foreseeable
7615 future, and will remain the default until this new codebase gets
7616 tested and hardened. Service operators who want to experiment with
7617 the new system can use the 'HiddenServiceVersion 3' torrc
7618 directive along with the regular onion service configuration
7619 options. We will publish a blog post about this new feature
7622 o Major bugfixes (usability, control port):
7623 - Report trusted clock skew indications as bootstrap errors, so
7624 controllers can more easily alert users when their clocks are
7625 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
7627 o Minor features (bug detection):
7628 - Log a warning message with a stack trace for any attempt to call
7629 get_options() during option validation. This pattern has caused
7630 subtle bugs in the past. Closes ticket 22281.
7632 o Minor features (client):
7633 - You can now use Tor as a tunneled HTTP proxy: use the new
7634 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
7635 requests. Closes ticket 22407.
7636 - Add an extra check to make sure that we always use the newer guard
7637 selection code for picking our guards. Closes ticket 22779.
7638 - When downloading (micro)descriptors, don't split the list into
7639 multiple requests unless we want at least 32 descriptors.
7640 Previously, we split at 4, not 32, which led to significant
7641 overhead in HTTP request size and degradation in compression
7642 performance. Closes ticket 23220.
7644 o Minor features (command line):
7645 - Add a new commandline option, --key-expiration, which prints when
7646 the current signing key is going to expire. Implements ticket
7647 17639; patch by Isis Lovecruft.
7649 o Minor features (control port):
7650 - If an application tries to use the control port as an HTTP proxy,
7651 respond with a meaningful "This is the Tor control port" message,
7652 and log the event. Closes ticket 1667. Patch from Ravi
7654 - Provide better error message for GETINFO desc/(id|name) when not
7655 fetching router descriptors. Closes ticket 5847. Patch by
7657 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
7658 whether Tor will try to download router descriptors and
7659 microdescriptors respectively. Closes ticket 22684.
7660 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
7661 so controllers can tell whether the geoip databases are loaded.
7662 Closes ticket 23237.
7663 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
7664 events. Closes ticket 19254. Patch by "DonnchaC".
7666 o Minor features (development support):
7667 - Developers can now generate a call-graph for Tor using the
7668 "calltool" python program, which post-processes object dumps. It
7669 should work okay on many Linux and OSX platforms, and might work
7670 elsewhere too. To run it, install calltool from
7671 https://gitweb.torproject.org/user/nickm/calltool.git and run
7672 "make callgraph". Closes ticket 19307.
7674 o Minor features (ed25519):
7675 - Add validation function to checks for torsion components in
7676 ed25519 public keys, used by prop224 client-side code. Closes
7677 ticket 22006. Math help by Ian Goldberg.
7679 o Minor features (exit relay, DNS):
7680 - Improve the clarity and safety of the log message from evdns when
7681 receiving an apparently spoofed DNS reply. Closes ticket 3056.
7683 o Minor features (integration, hardening):
7684 - Add a new NoExec option to prevent Tor from running other
7685 programs. When this option is set to 1, Tor will never try to run
7686 another program, regardless of the settings of
7687 PortForwardingHelper, ClientTransportPlugin, or
7688 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
7689 without restarting Tor. Closes ticket 22976.
7691 o Minor features (logging):
7692 - Improve the warning message for specifying a relay by nickname.
7693 The previous message implied that nickname registration was still
7694 part of the Tor network design, which it isn't. Closes
7696 - If the sandbox filter fails to load, suggest to the user that
7697 their kernel might not support seccomp2. Closes ticket 23090.
7699 o Minor features (portability):
7700 - Check at configure time whether uint8_t is the same type as
7701 unsigned char. Lots of existing code already makes this
7702 assumption, and there could be strict aliasing issues if the
7703 assumption is violated. Closes ticket 22410.
7705 o Minor features (relay, configuration):
7706 - Reject attempts to use relative file paths when RunAsDaemon is
7707 set. Previously, Tor would accept these, but the directory-
7708 changing step of RunAsDaemon would give strange and/or confusing
7709 results. Closes ticket 22731.
7711 o Minor features (startup, safety):
7712 - When configured to write a PID file, Tor now exits if it is unable
7713 to do so. Previously, it would warn and continue. Closes
7716 o Minor features (static analysis):
7717 - The BUG() macro has been changed slightly so that Coverity no
7718 longer complains about dead code if the bug is impossible. Closes
7721 o Minor features (testing):
7722 - The default chutney network tests now include tests for the v3
7723 hidden service design. Make sure you have the latest version of
7724 chutney if you want to run these. Closes ticket 22437.
7725 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7726 service descriptor. Closes ticket 15554.
7728 o Minor bugfixes (certificate handling):
7729 - Fix a time handling bug in Tor certificates set to expire after
7730 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7731 Coverity as CID 1415728.
7733 o Minor bugfixes (client, usability):
7734 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7735 SOCKS4a requests that contain IP address strings, even when
7736 SafeSocks in enabled, as this prevents user from connecting to
7737 known IP addresses without relying on DNS for resolving. SafeSocks
7738 still rejects SOCKS connections that connect to IP addresses when
7739 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7740 bugfix on Tor 0.2.6.2-alpha.
7742 o Minor bugfixes (code correctness):
7743 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7744 Previously we used ntohs(), which happens to behave the same on
7745 all the platforms we support, but which isn't really correct.
7746 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7747 - For defense-in-depth, make the controller's write_escaped_data()
7748 function robust to extremely long inputs. Fixes bug 19281; bugfix
7749 on 0.1.1.1-alpha. Reported by Guido Vranken.
7751 o Minor bugfixes (compilation):
7752 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7753 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7755 o Minor bugfixes (consensus expiry):
7756 - Check for adequate directory information correctly. Previously, Tor
7757 would reconsider whether it had sufficient directory information
7758 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7760 o Minor bugfixes (directory protocol):
7761 - Directory servers now include a "Date:" http header for response
7762 codes other than 200. Clients starting with a skewed clock and a
7763 recent consensus were getting "304 Not modified" responses from
7764 directory authorities, so without the Date header, the client
7765 would never hear about a wrong clock. Fixes bug 23499; bugfix
7767 - Make clients wait for 6 seconds before trying to download a
7768 consensus from an authority. Fixes bug 17750; bugfix
7771 o Minor bugfixes (DoS-resistance):
7772 - If future code asks if there are any running bridges, without
7773 checking if bridges are enabled, log a BUG warning rather than
7774 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7776 o Minor bugfixes (format strictness):
7777 - Restrict several data formats to decimal. Previously, the
7778 BuildTimeHistogram entries in the state file, the "bw=" entries in
7779 the bandwidth authority file, and the process IDs passed to the
7780 __OwningControllerProcess option could all be specified in hex or
7781 octal as well as in decimal. This was not an intentional feature.
7782 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7785 o Minor bugfixes (heartbeat):
7786 - If we fail to write a heartbeat message, schedule a retry for the
7787 minimum heartbeat interval number of seconds in the future. Fixes
7788 bug 19476; bugfix on 0.2.3.1-alpha.
7790 o Minor bugfixes (linux seccomp2 sandbox, logging):
7791 - Fix some messages on unexpected errors from the seccomp2 library.
7792 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7794 o Minor bugfixes (logging):
7795 - Remove duplicate log messages regarding opening non-local
7796 SocksPorts upon parsing config and opening listeners at startup.
7797 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7798 - Use a more comprehensible log message when telling the user
7799 they've excluded every running exit node. Fixes bug 7890; bugfix
7801 - When logging the number of descriptors we intend to download per
7802 directory request, do not log a number higher than then the number
7803 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7805 - When warning about a directory owned by the wrong user, log the
7806 actual name of the user owning the directory. Previously, we'd log
7807 the name of the process owner twice. Fixes bug 23487; bugfix
7809 - The tor specification says hop counts are 1-based, so fix two log
7810 messages that mistakenly logged 0-based hop counts. Fixes bug
7811 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7812 Credit to Xiaofan Li for reporting this issue.
7814 o Minor bugfixes (portability):
7815 - Stop using the PATH_MAX variable, which is not defined on GNU
7816 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7818 o Minor bugfixes (relay):
7819 - When uploading our descriptor for the first time after startup,
7820 report the reason for uploading as "Tor just started" rather than
7821 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7822 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7823 relays, to prevent spurious address resolutions and descriptor
7824 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7825 bugfix on in 0.2.8.1-alpha.
7827 o Minor bugfixes (tests):
7828 - Fix a broken unit test for the OutboundAddress option: the parsing
7829 function was never returning an error on failure. Fixes bug 23366;
7830 bugfix on 0.3.0.3-alpha.
7831 - Fix a signed-integer overflow in the unit tests for
7832 dir/download_status_random_backoff, which was untriggered until we
7833 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7835 o Minor bugfixes (usability, control port):
7836 - Stop making an unnecessary routerlist check in NETINFO clock skew
7837 detection; this was preventing clients from reporting NETINFO clock
7838 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7840 o Code simplification and refactoring:
7841 - Extract the code for handling newly-open channels into a separate
7842 function from the general code to handle channel state
7843 transitions. This change simplifies our callgraph, reducing the
7844 size of the largest strongly connected component by roughly a
7845 factor of two. Closes ticket 22608.
7846 - Remove dead code for largely unused statistics on the number of
7847 times we've attempted various public key operations. Fixes bug
7848 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7849 - Remove several now-obsolete functions for asking about old
7850 variants directory authority status. Closes ticket 22311; patch
7852 - Remove some of the code that once supported "Named" and "Unnamed"
7853 routers. Authorities no longer vote for these flags. Closes
7855 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7856 and old hidden services, to indicate that they aren't suitable for
7857 new protocols or formats. Closes ticket 23026.
7858 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7859 22521. Patch from Neel Chauhan.
7860 - Split the enormous circuit_send_next_onion_skin() function into
7861 multiple subfunctions. Closes ticket 22804.
7862 - Split the portions of the buffer.c module that handle particular
7863 protocols into separate modules. Part of ticket 23149.
7864 - Use our test macros more consistently, to produce more useful
7865 error messages when our unit tests fail. Add coccinelle patches to
7866 allow us to re-check for test macro uses. Closes ticket 22497.
7868 o Deprecated features:
7869 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7870 only applies to direct unencrypted HTTP connections to your
7871 directory server, which your Tor probably isn't using. Closes
7875 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7876 kernels. Closes ticket 22677.
7877 - Document all values of PublishServerDescriptor in the manpage.
7878 Closes ticket 15645.
7879 - Improve the documentation for the directory port part of the
7880 DirAuthority line. Closes ticket 20152.
7881 - Restore documentation for the authorities' "approved-routers"
7882 file. Closes ticket 21148.
7885 - The AllowDotExit option has been removed as unsafe. It has been
7886 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7887 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7888 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7889 Closes ticket 21031.
7890 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7891 nobody was using it any longer. Closes ticket 22377.
7894 Changes in version 0.2.8.15 - 2017-09-18
7895 Tor 0.2.8.15 backports a collection of bugfixes from later
7898 Most significantly, it includes a fix for TROVE-2017-008, a
7899 security bug that affects hidden services running with the
7900 SafeLogging option disabled. For more information, see
7901 https://trac.torproject.org/projects/tor/ticket/23490
7903 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7904 2018. We suggest that you upgrade to the latest stable release if
7905 possible. If you can't, we recommend that you upgrade at least to
7906 0.2.9, which will be supported until 2020.
7908 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7909 - Avoid an assertion failure bug affecting our implementation of
7910 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7911 handling of "0xx" differs from what we had expected. Fixes bug
7912 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7915 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7918 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7919 - Backport a fix for an "unused variable" warning that appeared
7920 in some versions of mingw. Fixes bug 22838; bugfix on
7923 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7924 - Fix a memset() off the end of an array when packing cells. This
7925 bug should be harmless in practice, since the corrupted bytes are
7926 still in the same structure, and are always padding bytes,
7927 ignored, or immediately overwritten, depending on compiler
7928 behavior. Nevertheless, because the memset()'s purpose is to make
7929 sure that any other cell-handling bugs can't expose bytes to the
7930 network, we need to fix it. Fixes bug 22737; bugfix on
7931 0.2.4.11-alpha. Fixes CID 1401591.
7933 o Build features (backport from 0.3.1.5-alpha):
7934 - Tor's repository now includes a Travis Continuous Integration (CI)
7935 configuration file (.travis.yml). This is meant to help new
7936 developers and contributors who fork Tor to a Github repository be
7937 better able to test their changes, and understand what we expect
7938 to pass. To use this new build feature, you must fork Tor to your
7939 Github account, then go into the "Integrations" menu in the
7940 repository settings for your fork and enable Travis, then push
7941 your changes. Closes ticket 22636.
7944 Changes in version 0.2.9.12 - 2017-09-18
7945 Tor 0.2.9.12 backports a collection of bugfixes from later
7948 Most significantly, it includes a fix for TROVE-2017-008, a
7949 security bug that affects hidden services running with the
7950 SafeLogging option disabled. For more information, see
7951 https://trac.torproject.org/projects/tor/ticket/23490
7953 o Major features (security, backport from 0.3.0.2-alpha):
7954 - Change the algorithm used to decide DNS TTLs on client and server
7955 side, to better resist DNS-based correlation attacks like the
7956 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
7957 Feamster. Now relays only return one of two possible DNS TTL
7958 values, and clients are willing to believe DNS TTL values up to 3
7959 hours long. Closes ticket 19769.
7961 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
7962 - Fix a rare crash when sending a begin cell on a circuit whose
7963 linked directory connection had already been closed. Fixes bug
7964 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
7966 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
7967 - Fix a bug that prevented exit nodes from caching DNS records for
7968 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
7970 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
7971 - Fix a typo that had prevented TPROXY-based transparent proxying
7972 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
7973 Patch from "d4fq0fQAgoJ".
7975 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7976 - Avoid an assertion failure bug affecting our implementation of
7977 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7978 handling of "0xx" differs from what we had expected. Fixes bug
7979 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7981 o Minor features (code style, backport from 0.3.1.3-alpha):
7982 - Add "Falls through" comments to our codebase, in order to silence
7983 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
7984 Stieger. Closes ticket 22446.
7986 o Minor features (geoip):
7987 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7990 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
7991 - Roll over monthly accounting at the configured hour and minute,
7992 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
7993 Found by Andrey Karpov with PVS-Studio.
7995 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
7996 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
7997 bugfix on 0.2.8.1-alpha.
7998 - Fix warnings when building with libscrypt and openssl scrypt support
7999 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8000 - When building with certain versions the mingw C header files, avoid
8001 float-conversion warnings when calling the C functions isfinite(),
8002 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
8004 o Minor bugfixes (compilation, backport from 0.3.1.7):
8005 - Avoid compiler warnings in the unit tests for running tor_sscanf()
8006 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8008 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8009 - Backport a fix for an "unused variable" warning that appeared
8010 in some versions of mingw. Fixes bug 22838; bugfix on
8013 o Minor bugfixes (controller, backport from 0.3.1.7):
8014 - Do not crash when receiving a HSPOST command with an empty body.
8015 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8016 - Do not crash when receiving a POSTDESCRIPTOR command with an
8017 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8019 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8020 - Avoid Coverity build warnings related to our BUG() macro. By
8021 default, Coverity treats BUG() as the Linux kernel does: an
8022 instant abort(). We need to override that so our BUG() macro
8023 doesn't prevent Coverity from analyzing functions that use it.
8024 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8026 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
8027 - Fix a memset() off the end of an array when packing cells. This
8028 bug should be harmless in practice, since the corrupted bytes are
8029 still in the same structure, and are always padding bytes,
8030 ignored, or immediately overwritten, depending on compiler
8031 behavior. Nevertheless, because the memset()'s purpose is to make
8032 sure that any other cell-handling bugs can't expose bytes to the
8033 network, we need to fix it. Fixes bug 22737; bugfix on
8034 0.2.4.11-alpha. Fixes CID 1401591.
8036 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
8037 - When setting the maximum number of connections allowed by the OS,
8038 always allow some extra file descriptors for other files. Fixes
8039 bug 22797; bugfix on 0.2.0.10-alpha.
8041 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8042 - Avoid a sandbox failure when trying to re-bind to a socket and
8043 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8045 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8046 - Permit the fchmod system call, to avoid crashing on startup when
8047 starting with the seccomp2 sandbox and an unexpected set of
8048 permissions on the data directory or its contents. Fixes bug
8049 22516; bugfix on 0.2.5.4-alpha.
8051 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
8052 - Avoid a double-marked-circuit warning that could happen when we
8053 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8056 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8057 - Reject version numbers with non-numeric prefixes (such as +, -, or
8058 whitespace). Disallowing whitespace prevents differential version
8059 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8060 and part of 21508; bugfix on 0.0.8pre1.
8062 o Build features (backport from 0.3.1.5-alpha):
8063 - Tor's repository now includes a Travis Continuous Integration (CI)
8064 configuration file (.travis.yml). This is meant to help new
8065 developers and contributors who fork Tor to a Github repository be
8066 better able to test their changes, and understand what we expect
8067 to pass. To use this new build feature, you must fork Tor to your
8068 Github account, then go into the "Integrations" menu in the
8069 repository settings for your fork and enable Travis, then push
8070 your changes. Closes ticket 22636.
8073 Changes in version 0.3.0.11 - 2017-09-18
8074 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
8077 Most significantly, it includes a fix for TROVE-2017-008, a
8078 security bug that affects hidden services running with the
8079 SafeLogging option disabled. For more information, see
8080 https://trac.torproject.org/projects/tor/ticket/23490
8082 o Minor features (code style, backport from 0.3.1.7):
8083 - Add "Falls through" comments to our codebase, in order to silence
8084 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8085 Stieger. Closes ticket 22446.
8088 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8091 o Minor bugfixes (compilation, backport from 0.3.1.7):
8092 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
8093 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8095 o Minor bugfixes (controller, backport from 0.3.1.7):
8096 - Do not crash when receiving a HSPOST command with an empty body.
8097 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8098 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
8099 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8101 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
8102 - When setting the maximum number of connections allowed by the OS,
8103 always allow some extra file descriptors for other files. Fixes
8104 bug 22797; bugfix on 0.2.0.10-alpha.
8106 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
8107 - Remove a forgotten debugging message when an introduction point
8108 successfully establishes a hidden service prop224 circuit with
8110 - Change three other log_warn() for an introduction point to
8111 protocol warnings, because they can be failure from the network
8112 and are not relevant to the operator. Fixes bug 23078; bugfix on
8113 0.3.0.1-alpha and 0.3.0.2-alpha.
8116 Changes in version 0.3.1.7 - 2017-09-18
8117 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
8119 With the 0.3.1 series, Tor now serves and downloads directory
8120 information in more compact formats, to save on bandwidth overhead. It
8121 also contains a new padding system to resist netflow-based traffic
8122 analysis, and experimental support for building parts of Tor in Rust
8123 (though no parts of Tor are in Rust yet). There are also numerous
8124 small features, bugfixes on earlier release series, and groundwork for
8125 the hidden services revamp of 0.3.2.
8127 This release also includes a fix for TROVE-2017-008, a security bug
8128 that affects hidden services running with the SafeLogging option
8129 disabled. For more information, see
8130 https://trac.torproject.org/projects/tor/ticket/23490
8132 Per our stable release policy, we plan to support each stable release
8133 series for at least the next nine months, or for three months after
8134 the first stable release of the next series: whichever is longer. If
8135 you need a release with long-term support, we recommend that you stay
8136 with the 0.2.9 series.
8138 Below is a list of the changes since 0.3.1.6-rc. For a list of all
8139 changes since 0.3.0, see the ReleaseNotes file.
8141 o Major bugfixes (security, hidden services, loggging):
8142 - Fix a bug where we could log uninitialized stack when a certain
8143 hidden service error occurred while SafeLogging was disabled.
8144 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
8145 TROVE-2017-008 and CVE-2017-0380.
8147 o Minor features (defensive programming):
8148 - Create a pair of consensus parameters, nf_pad_tor2web and
8149 nf_pad_single_onion, to disable netflow padding in the consensus
8150 for non-anonymous connections in case the overhead is high. Closes
8153 o Minor features (diagnostic):
8154 - Add a stack trace to the bug warnings that can be logged when
8155 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
8156 attempt for bug 23105.
8158 o Minor features (geoip):
8159 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8162 o Minor bugfixes (compilation):
8163 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
8164 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8166 o Minor bugfixes (controller):
8167 - Do not crash when receiving a HSPOST command with an empty body.
8168 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8169 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
8170 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8172 o Minor bugfixes (relay):
8173 - Inform the geoip and rephist modules about all requests, even on
8174 relays that are only fetching microdescriptors. Fixes a bug
8175 related to 21585; bugfix on 0.3.0.1-alpha.
8177 o Minor bugfixes (unit tests):
8178 - Fix a channelpadding unit test failure on slow systems by using
8179 mocked time instead of actual time. Fixes bug 23077; bugfix
8183 Changes in version 0.3.1.6-rc - 2017-09-05
8184 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
8185 release series, including a bug that produced weird behavior on
8186 Windows directory caches.
8188 This is the first release candidate in the Tor 0.3.1 series. If we
8189 find no new bugs or regressions here, the first stable 0.3.1 release
8190 will be nearly identical to it.
8192 o Major bugfixes (windows, directory cache):
8193 - On Windows, do not try to delete cached consensus documents and
8194 diffs before they are unmapped from memory--Windows won't allow
8195 that. Instead, allow the consensus cache directory to grow larger,
8196 to hold files that might need to stay around longer. Fixes bug
8197 22752; bugfix on 0.3.1.1-alpha.
8199 o Minor features (directory authority):
8200 - Improve the message that authorities report to relays that present
8201 RSA/Ed25519 keypairs that conflict with previously pinned keys.
8202 Closes ticket 22348.
8204 o Minor features (geoip):
8205 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
8208 o Minor features (testing):
8209 - Add more tests for compression backend initialization. Closes
8212 o Minor bugfixes (directory cache):
8213 - Fix a memory leak when recovering space in the consensus cache.
8214 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
8216 o Minor bugfixes (hidden service):
8217 - Increase the number of circuits that a service is allowed to
8218 open over a specific period of time. The value was lower than it
8219 should be (8 vs 12) in the normal case of 3 introduction points.
8220 Fixes bug 22159; bugfix on 0.3.0.5-rc.
8221 - Fix a BUG warning during HSv3 descriptor decoding that could be
8222 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
8223 on 0.3.0.1-alpha. Bug found by "haxxpop".
8224 - Rate-limit the log messages if we exceed the maximum number of
8225 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
8227 o Minor bugfixes (logging, relay):
8228 - Remove a forgotten debugging message when an introduction point
8229 successfully establishes a hidden service prop224 circuit with
8231 - Change three other log_warn() for an introduction point to
8232 protocol warnings, because they can be failure from the network
8233 and are not relevant to the operator. Fixes bug 23078; bugfix on
8234 0.3.0.1-alpha and 0.3.0.2-alpha.
8236 o Minor bugfixes (relay):
8237 - When a relay is not running as a directory cache, it will no
8238 longer generate compressed consensuses and consensus diff
8239 information. Previously, this was a waste of disk and CPU. Fixes
8240 bug 23275; bugfix on 0.3.1.1-alpha.
8242 o Minor bugfixes (robustness, error handling):
8243 - Improve our handling of the cases where OpenSSL encounters a
8244 memory error while encoding keys and certificates. We haven't
8245 observed these errors in the wild, but if they do happen, we now
8246 detect and respond better. Fixes bug 19418; bugfix on all versions
8247 of Tor. Reported by Guido Vranken.
8249 o Minor bugfixes (stability):
8250 - Avoid crashing on a double-free when unable to load or process an
8251 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
8252 with the clang static analyzer.
8254 o Minor bugfixes (testing):
8255 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8256 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8257 - Port the hs_ntor handshake test to work correctly with recent
8258 versions of the pysha3 module. Fixes bug 23071; bugfix
8261 o Minor bugfixes (Windows service):
8262 - When running as a Windows service, set the ID of the main thread
8263 correctly. Failure to do so made us fail to send log messages to
8264 the controller in 0.2.1.16-rc, slowed down controller event
8265 delivery in 0.2.7.3-rc and later, and crash with an assertion
8266 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
8267 Patch and diagnosis from "Vort".
8270 Changes in version 0.3.0.10 - 2017-08-02
8271 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
8272 from the current Tor alpha series. OpenBSD users and TPROXY users
8273 should upgrade; others are probably okay sticking with 0.3.0.9.
8275 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
8276 - Tor's repository now includes a Travis Continuous Integration (CI)
8277 configuration file (.travis.yml). This is meant to help new
8278 developers and contributors who fork Tor to a Github repository be
8279 better able to test their changes, and understand what we expect
8280 to pass. To use this new build feature, you must fork Tor to your
8281 Github account, then go into the "Integrations" menu in the
8282 repository settings for your fork and enable Travis, then push
8283 your changes. Closes ticket 22636.
8285 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
8286 - Fix a typo that had prevented TPROXY-based transparent proxying
8287 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8288 Patch from "d4fq0fQAgoJ".
8290 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8291 - Avoid an assertion failure bug affecting our implementation of
8292 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8293 handling of "0xbar" differs from what we had expected. Fixes bug
8294 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8296 o Minor features (backport from 0.3.1.5-alpha):
8297 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8300 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
8301 - Roll over monthly accounting at the configured hour and minute,
8302 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8303 Found by Andrey Karpov with PVS-Studio.
8305 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
8306 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8307 bugfix on 0.2.8.1-alpha.
8308 - Fix warnings when building with libscrypt and openssl scrypt
8309 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8310 - When building with certain versions of the mingw C header files,
8311 avoid float-conversion warnings when calling the C functions
8312 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8315 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8316 - Backport a fix for an "unused variable" warning that appeared
8317 in some versions of mingw. Fixes bug 22838; bugfix on
8320 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8321 - Avoid Coverity build warnings related to our BUG() macro. By
8322 default, Coverity treats BUG() as the Linux kernel does: an
8323 instant abort(). We need to override that so our BUG() macro
8324 doesn't prevent Coverity from analyzing functions that use it.
8325 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8327 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
8328 - When rejecting a router descriptor for running an obsolete version
8329 of Tor without ntor support, warn about the obsolete tor version,
8330 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8332 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8333 - Avoid a sandbox failure when trying to re-bind to a socket and
8334 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8336 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
8337 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8338 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8341 Changes in version 0.3.1.5-alpha - 2017-08-01
8342 Tor 0.3.1.5-alpha improves the performance of consensus diff
8343 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
8344 several other bugs. If no serious bugs are found in this version, the
8345 next version will be a release candidate.
8347 This release also marks the end of support for the Tor 0.2.4.x,
8348 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
8349 further bug or security fixes. Anyone still running or distributing
8350 one of those versions should upgrade.
8352 o Major features (build system, continuous integration):
8353 - Tor's repository now includes a Travis Continuous Integration (CI)
8354 configuration file (.travis.yml). This is meant to help new
8355 developers and contributors who fork Tor to a Github repository be
8356 better able to test their changes, and understand what we expect
8357 to pass. To use this new build feature, you must fork Tor to your
8358 Github account, then go into the "Integrations" menu in the
8359 repository settings for your fork and enable Travis, then push
8360 your changes. Closes ticket 22636.
8362 o Major bugfixes (openbsd, denial-of-service):
8363 - Avoid an assertion failure bug affecting our implementation of
8364 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8365 handling of "0xbar" differs from what we had expected. Fixes bug
8366 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8368 o Major bugfixes (relay, performance):
8369 - Perform circuit handshake operations at a higher priority than we
8370 use for consensus diff creation and compression. This should
8371 prevent circuits from starving when a relay or bridge receives a
8372 new consensus, especially on lower-powered machines. Fixes bug
8373 22883; bugfix on 0.3.1.1-alpha.
8375 o Minor features (bridge authority):
8376 - Add "fingerprint" lines to the networkstatus-bridges file produced
8377 by bridge authorities. Closes ticket 22207.
8379 o Minor features (directory cache, consensus diff):
8380 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
8381 operators with low-resource environments to adjust the number of
8382 consensuses they'll store and generate diffs from. Most cache
8383 operators should leave it unchanged. Helps to work around
8386 o Minor features (geoip):
8387 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8390 o Minor features (relay, performance):
8391 - Always start relays with at least two worker threads, to prevent
8392 priority inversion on slow tasks. Part of the fix for bug 22883.
8393 - Allow background work to be queued with different priorities, so
8394 that a big pile of slow low-priority jobs will not starve out
8395 higher priority jobs. This lays the groundwork for a fix for
8398 o Minor bugfixes (build system, rust):
8399 - Fix a problem where Rust toolchains were not being found when
8400 building without --enable-cargo-online-mode, due to setting the
8401 $HOME environment variable instead of $CARGO_HOME. Fixes bug
8402 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
8404 o Minor bugfixes (compatibility, zstd):
8405 - Write zstd epilogues correctly when the epilogue requires
8406 reallocation of the output buffer, even with zstd 1.3.0.
8407 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
8408 22927; bugfix on 0.3.1.1-alpha.
8410 o Minor bugfixes (compilation warnings):
8411 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
8412 22915; bugfix on 0.2.8.1-alpha.
8413 - Fix warnings when building with libscrypt and openssl scrypt
8414 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8415 - Compile correctly when both openssl 1.1.0 and libscrypt are
8416 detected. Previously this would cause an error. Fixes bug 22892;
8417 bugfix on 0.3.1.1-alpha.
8418 - When building with certain versions of the mingw C header files,
8419 avoid float-conversion warnings when calling the C functions
8420 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8423 o Minor bugfixes (coverity build support):
8424 - Avoid Coverity build warnings related to our BUG() macro. By
8425 default, Coverity treats BUG() as the Linux kernel does: an
8426 instant abort(). We need to override that so our BUG() macro
8427 doesn't prevent Coverity from analyzing functions that use it.
8428 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8430 o Minor bugfixes (directory authority):
8431 - When a directory authority rejects a descriptor or extrainfo with
8432 a given digest, mark that digest as undownloadable, so that we do
8433 not attempt to download it again over and over. We previously
8434 tried to avoid downloading such descriptors by other means, but we
8435 didn't notice if we accidentally downloaded one anyway. This
8436 behavior became problematic in 0.2.7.2-alpha, when authorities
8437 began pinning Ed25519 keys. Fixes bug 22349; bugfix
8440 o Minor bugfixes (error reporting, windows):
8441 - When formatting Windows error messages, use the English format to
8442 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
8445 o Minor bugfixes (file limits, osx):
8446 - When setting the maximum number of connections allowed by the OS,
8447 always allow some extra file descriptors for other files. Fixes
8448 bug 22797; bugfix on 0.2.0.10-alpha.
8450 o Minor bugfixes (linux seccomp2 sandbox):
8451 - Avoid a sandbox failure when trying to re-bind to a socket and
8452 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8454 o Minor bugfixes (memory leaks):
8455 - Fix a small memory leak when validating a configuration that uses
8456 two or more AF_UNIX sockets for the same port type. Fixes bug
8457 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
8459 o Minor bugfixes (unit tests):
8460 - test_consdiff_base64cmp would fail on OS X because while OS X
8461 follows the standard of (less than zero/zero/greater than zero),
8462 it doesn't follow the convention of (-1/0/+1). Make the test
8463 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
8464 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8465 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8468 Changes in version 0.3.1.4-alpha - 2017-06-29
8469 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
8470 to use a guard that was in the same network family as a chosen exit
8471 relay. This is a security regression; all clients running earlier
8472 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8475 This release also fixes several other bugs introduced in 0.3.0.x
8476 and 0.3.1.x, including others that can affect bandwidth usage
8480 - To build with zstd and lzma support, Tor now requires the
8481 pkg-config tool at build time. (This requirement was new in
8482 0.3.1.1-alpha, but was not noted at the time. Noting it here to
8483 close ticket 22623.)
8485 o Major bugfixes (path selection, security):
8486 - When choosing which guard to use for a circuit, avoid the exit's
8487 family along with the exit itself. Previously, the new guard
8488 selection logic avoided the exit, but did not consider its family.
8489 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8490 006 and CVE-2017-0377.
8492 o Major bugfixes (compression, zstd):
8493 - Correctly detect a full buffer when decompressing a large zstd-
8494 compressed input. Previously, we would sometimes treat a full
8495 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
8497 o Major bugfixes (directory protocol):
8498 - Ensure that we send "304 Not modified" as HTTP status code when a
8499 client is attempting to fetch a consensus or consensus diff, and
8500 the best one we can send them is one they already have. Fixes bug
8501 22702; bugfix on 0.3.1.1-alpha.
8503 o Major bugfixes (entry guards):
8504 - When starting with an old consensus, do not add new entry guards
8505 unless the consensus is "reasonably live" (under 1 day old). Fixes
8506 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8508 o Minor features (bug mitigation, diagnostics, logging):
8509 - Avoid an assertion failure, and log a better error message, when
8510 unable to remove a file from the consensus cache on Windows.
8511 Attempts to mitigate and diagnose bug 22752.
8513 o Minor features (geoip):
8514 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8517 o Minor bugfixes (compression):
8518 - When compressing or decompressing a buffer, check for a failure to
8519 create a compression object. Fixes bug 22626; bugfix
8521 - When decompressing a buffer, check for extra data after the end of
8522 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
8523 - When decompressing an object received over an anonymous directory
8524 connection, if we have already decompressed it using an acceptable
8525 compression method, do not reject it for looking like an
8526 unacceptable compression method. Fixes part of bug 22670; bugfix
8528 - When serving directory votes compressed with zlib, do not claim to
8529 have compressed them with zstd. Fixes bug 22669; bugfix
8531 - When spooling compressed data to an output buffer, don't try to
8532 spool more data when there is no more data to spool and we are not
8533 trying to flush the input. Previously, we would sometimes launch
8534 compression requests with nothing to do, which interferes with our
8535 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
8537 o Minor bugfixes (defensive programming):
8538 - Detect and break out of infinite loops in our compression code. We
8539 don't think that any such loops exist now, but it's best to be
8540 safe. Closes ticket 22672.
8541 - Fix a memset() off the end of an array when packing cells. This
8542 bug should be harmless in practice, since the corrupted bytes are
8543 still in the same structure, and are always padding bytes,
8544 ignored, or immediately overwritten, depending on compiler
8545 behavior. Nevertheless, because the memset()'s purpose is to make
8546 sure that any other cell-handling bugs can't expose bytes to the
8547 network, we need to fix it. Fixes bug 22737; bugfix on
8548 0.2.4.11-alpha. Fixes CID 1401591.
8550 o Minor bugfixes (linux seccomp2 sandbox):
8551 - Permit the fchmod system call, to avoid crashing on startup when
8552 starting with the seccomp2 sandbox and an unexpected set of
8553 permissions on the data directory or its contents. Fixes bug
8554 22516; bugfix on 0.2.5.4-alpha.
8555 - Fix a crash in the LZMA module, when the sandbox was enabled, and
8556 liblzma would allocate more than 16 MB of memory. We solve this by
8557 bumping the mprotect() limit in the sandbox module from 16 MB to
8558 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
8560 o Minor bugfixes (logging):
8561 - When decompressing, do not warn if we fail to decompress using a
8562 compression method that we merely guessed. Fixes part of bug
8563 22670; bugfix on 0.1.1.14-alpha.
8564 - When decompressing, treat mismatch between content-encoding and
8565 actual compression type as a protocol warning. Fixes part of bug
8566 22670; bugfix on 0.1.1.9-alpha.
8567 - Downgrade "assigned_to_cpuworker failed" message to info-level
8568 severity. In every case that can reach it, either a better warning
8569 has already been logged, or no warning is warranted. Fixes bug
8570 22356; bugfix on 0.2.6.3-alpha.
8571 - Demote a warn that was caused by libevent delays to info if
8572 netflow padding is less than 4.5 seconds late, or to notice
8573 if it is more (4.5 seconds is the amount of time that a netflow
8574 record might be emitted after, if we chose the maximum timeout).
8575 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8577 o Minor bugfixes (process behavior):
8578 - When exiting because of an error, always exit with a nonzero exit
8579 status. Previously, we would fail to report an error in our exit
8580 status in cases related to __OwningControllerProcess failure,
8581 lockfile contention, and Ed25519 key initialization. Fixes bug
8582 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
8583 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
8587 - Add a manpage description for the key-pinning-journal file. Closes
8589 - Correctly note that bandwidth accounting values are stored in the
8590 state file, and the bw_accounting file is now obsolete. Closes
8592 - Document more of the files in the Tor data directory, including
8593 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
8594 approved-routers, sr-random, and diff-cache. Found while fixing
8598 Changes in version 0.3.0.9 - 2017-06-29
8599 Tor 0.3.0.9 fixes a path selection bug that would allow a client
8600 to use a guard that was in the same network family as a chosen exit
8601 relay. This is a security regression; all clients running earlier
8602 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
8605 This release also backports several other bugfixes from the 0.3.1.x
8608 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
8609 - When choosing which guard to use for a circuit, avoid the exit's
8610 family along with the exit itself. Previously, the new guard
8611 selection logic avoided the exit, but did not consider its family.
8612 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8613 006 and CVE-2017-0377.
8615 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
8616 - Don't block bootstrapping when a primary bridge is offline and we
8617 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8618 21969; bugfix on 0.3.0.3-alpha.
8620 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
8621 - When starting with an old consensus, do not add new entry guards
8622 unless the consensus is "reasonably live" (under 1 day old). Fixes
8623 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8625 o Minor features (geoip):
8626 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8629 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8630 - Reject version numbers with non-numeric prefixes (such as +, -, or
8631 whitespace). Disallowing whitespace prevents differential version
8632 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8633 and part of 21508; bugfix on 0.0.8pre1.
8635 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8636 - Permit the fchmod system call, to avoid crashing on startup when
8637 starting with the seccomp2 sandbox and an unexpected set of
8638 permissions on the data directory or its contents. Fixes bug
8639 22516; bugfix on 0.2.5.4-alpha.
8641 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
8642 - Fix a memset() off the end of an array when packing cells. This
8643 bug should be harmless in practice, since the corrupted bytes are
8644 still in the same structure, and are always padding bytes,
8645 ignored, or immediately overwritten, depending on compiler
8646 behavior. Nevertheless, because the memset()'s purpose is to make
8647 sure that any other cell-handling bugs can't expose bytes to the
8648 network, we need to fix it. Fixes bug 22737; bugfix on
8649 0.2.4.11-alpha. Fixes CID 1401591.
8652 Changes in version 0.3.1.3-alpha - 2017-06-08
8653 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
8654 remotely crash a hidden service with an assertion failure. Anyone
8655 running a hidden service should upgrade to this version, or to some
8656 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8658 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
8659 that sometimes made relays unreliable, as well as several other
8660 bugfixes described below.
8662 o Major bugfixes (hidden service, relay, security):
8663 - Fix a remotely triggerable assertion failure when a hidden service
8664 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8665 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8666 - Fix a remotely triggerable assertion failure caused by receiving a
8667 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8668 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8671 o Major bugfixes (relay, link handshake):
8672 - When performing the v3 link handshake on a TLS connection, report
8673 that we have the x509 certificate that we actually used on that
8674 connection, even if we have changed certificates since that
8675 connection was first opened. Previously, we would claim to have
8676 used our most recent x509 link certificate, which would sometimes
8677 make the link handshake fail. Fixes one case of bug 22460; bugfix
8680 o Major bugfixes (relays, key management):
8681 - Regenerate link and authentication certificates whenever the key
8682 that signs them changes; also, regenerate link certificates
8683 whenever the signed key changes. Previously, these processes were
8684 only weakly coupled, and we relays could (for minutes to hours)
8685 wind up with an inconsistent set of keys and certificates, which
8686 other relays would not accept. Fixes two cases of bug 22460;
8687 bugfix on 0.3.0.1-alpha.
8688 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8689 send the certificate that matches the x509 certificate that we
8690 used on the TLS connection. Previously, there was a race condition
8691 if the TLS context rotated after we began the TLS handshake but
8692 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8695 o Major bugfixes (torrc, crash):
8696 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
8697 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
8699 o Minor features (code style):
8700 - Add "Falls through" comments to our codebase, in order to silence
8701 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8702 Stieger. Closes ticket 22446.
8704 o Minor features (diagnostic):
8705 - Add logging messages to try to diagnose a rare bug that seems to
8706 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
8707 think this is happening because of incorrect system clocks, but
8708 we'd like to know for certain. Diagnostic for bug 22466.
8710 o Minor bugfixes (correctness):
8711 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8712 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8714 o Minor bugfixes (directory protocol):
8715 - Check for libzstd >= 1.1, because older versions lack the
8716 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8718 o Minor bugfixes (link handshake):
8719 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8720 months, and regenerate it when it is within one month of expiring.
8721 Previously, we had generated this certificate at startup with a
8722 ten-year lifetime, but that could lead to weird behavior when Tor
8723 was started with a grossly inaccurate clock. Mitigates bug 22466;
8724 mitigation on 0.3.0.1-alpha.
8726 o Minor bugfixes (storage directories):
8727 - Always check for underflows in the cached storage directory usage.
8728 If the usage does underflow, re-calculate it. Also, avoid a
8729 separate underflow when the usage is not known. Fixes bug 22424;
8730 bugfix on 0.3.1.1-alpha.
8732 o Minor bugfixes (unit tests):
8733 - The unit tests now pass on systems where localhost is misconfigured
8734 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8738 - Clarify the manpage for the (deprecated) torify script. Closes
8741 Changes in version 0.3.0.8 - 2017-06-08
8742 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8743 remotely crash a hidden service with an assertion failure. Anyone
8744 running a hidden service should upgrade to this version, or to some
8745 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8747 Tor 0.3.0.8 also includes fixes for several key management bugs
8748 that sometimes made relays unreliable, as well as several other
8749 bugfixes described below.
8751 o Major bugfixes (hidden service, relay, security, backport
8752 from 0.3.1.3-alpha):
8753 - Fix a remotely triggerable assertion failure when a hidden service
8754 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8755 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8756 - Fix a remotely triggerable assertion failure caused by receiving a
8757 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8758 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8761 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8762 - When performing the v3 link handshake on a TLS connection, report
8763 that we have the x509 certificate that we actually used on that
8764 connection, even if we have changed certificates since that
8765 connection was first opened. Previously, we would claim to have
8766 used our most recent x509 link certificate, which would sometimes
8767 make the link handshake fail. Fixes one case of bug 22460; bugfix
8770 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8771 - Regenerate link and authentication certificates whenever the key
8772 that signs them changes; also, regenerate link certificates
8773 whenever the signed key changes. Previously, these processes were
8774 only weakly coupled, and we relays could (for minutes to hours)
8775 wind up with an inconsistent set of keys and certificates, which
8776 other relays would not accept. Fixes two cases of bug 22460;
8777 bugfix on 0.3.0.1-alpha.
8778 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8779 send the certificate that matches the x509 certificate that we
8780 used on the TLS connection. Previously, there was a race condition
8781 if the TLS context rotated after we began the TLS handshake but
8782 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8785 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8786 - Stop rejecting v3 hidden service descriptors because their size
8787 did not match an old padding rule. Fixes bug 22447; bugfix on
8790 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8791 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8792 December 2016 (of which ~126 were still functional) with a list of
8793 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8794 2017. Resolves ticket 21564.
8796 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8797 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8798 bug 22252; bugfix on 0.2.9.3-alpha.
8800 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8801 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8802 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8804 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8805 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8806 months, and regenerate it when it is within one month of expiring.
8807 Previously, we had generated this certificate at startup with a
8808 ten-year lifetime, but that could lead to weird behavior when Tor
8809 was started with a grossly inaccurate clock. Mitigates bug 22466;
8810 mitigation on 0.3.0.1-alpha.
8812 o Minor bugfixes (memory leak, directory authority, backport from
8814 - When directory authorities reject a router descriptor due to
8815 keypinning, free the router descriptor rather than leaking the
8816 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8819 Changes in version 0.2.9.11 - 2017-06-08
8820 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8821 remotely crash a hidden service with an assertion failure. Anyone
8822 running a hidden service should upgrade to this version, or to some
8823 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8824 are not affected by TROVE-2017-004.)
8826 Tor 0.2.9.11 also backports fixes for several key management bugs
8827 that sometimes made relays unreliable, as well as several other
8828 bugfixes described below.
8830 o Major bugfixes (hidden service, relay, security, backport
8831 from 0.3.1.3-alpha):
8832 - Fix a remotely triggerable assertion failure caused by receiving a
8833 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8834 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8837 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8838 - When performing the v3 link handshake on a TLS connection, report
8839 that we have the x509 certificate that we actually used on that
8840 connection, even if we have changed certificates since that
8841 connection was first opened. Previously, we would claim to have
8842 used our most recent x509 link certificate, which would sometimes
8843 make the link handshake fail. Fixes one case of bug 22460; bugfix
8846 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8847 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8848 December 2016 (of which ~126 were still functional) with a list of
8849 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8850 2017. Resolves ticket 21564.
8852 o Minor features (future-proofing, backport from 0.3.0.7):
8853 - Tor no longer refuses to download microdescriptors or descriptors if
8854 they are listed as "published in the future". This change will
8855 eventually allow us to stop listing meaningful "published" dates
8856 in microdescriptor consensuses, and thereby allow us to reduce the
8857 resources required to download consensus diffs by over 50%.
8858 Implements part of ticket 21642; implements part of proposal 275.
8860 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8861 - Directory authorities now reject relays running versions
8862 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8863 suffer from bug 20499 and don't keep their consensus cache
8864 up-to-date. Resolves ticket 20509.
8866 o Minor features (geoip):
8867 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8870 o Minor bugfixes (control port, backport from 0.3.0.6):
8871 - The GETINFO extra-info/digest/<digest> command was broken because
8872 of a wrong base16 decode return value check, introduced when
8873 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8875 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8876 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8877 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8879 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8880 - The getpid() system call is now permitted under the Linux seccomp2
8881 sandbox, to avoid crashing with versions of OpenSSL (and other
8882 libraries) that attempt to learn the process's PID by using the
8883 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8886 o Minor bugfixes (memory leak, directory authority, backport
8887 from 0.3.1.2-alpha):
8888 - When directory authorities reject a router descriptor due to
8889 keypinning, free the router descriptor rather than leaking the
8890 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8892 Changes in version 0.2.8.14 - 2017-06-08
8893 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8894 remotely crash a hidden service with an assertion failure. Anyone
8895 running a hidden service should upgrade to this version, or to some
8896 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8897 are not affected by TROVE-2017-004.)
8899 o Major bugfixes (hidden service, relay, security):
8900 - Fix a remotely triggerable assertion failure caused by receiving a
8901 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8902 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8905 o Minor features (geoip):
8906 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8909 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8910 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8911 December 2016 (of which ~126 were still functional) with a list of
8912 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8913 2017. Resolves ticket 21564.
8915 o Minor bugfixes (correctness):
8916 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8917 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8919 Changes in version 0.2.7.8 - 2017-06-08
8920 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8921 remotely crash a hidden service with an assertion failure. Anyone
8922 running a hidden service should upgrade to this version, or to some
8923 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8924 are not affected by TROVE-2017-004.)
8926 o Major bugfixes (hidden service, relay, security):
8927 - Fix a remotely triggerable assertion failure caused by receiving a
8928 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8929 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8932 o Minor features (geoip):
8933 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8936 o Minor bugfixes (correctness):
8937 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8938 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8941 Changes in version 0.2.6.12 - 2017-06-08
8942 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
8943 remotely crash a hidden service with an assertion failure. Anyone
8944 running a hidden service should upgrade to this version, or to some
8945 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8946 are not affected by TROVE-2017-004.)
8948 o Major bugfixes (hidden service, relay, security):
8949 - Fix a remotely triggerable assertion failure caused by receiving a
8950 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8951 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8954 o Minor features (geoip):
8955 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8958 o Minor bugfixes (correctness):
8959 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8960 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8962 Changes in version 0.2.5.14 - 2017-06-08
8963 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
8964 remotely crash a hidden service with an assertion failure. Anyone
8965 running a hidden service should upgrade to this version, or to some
8966 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8967 are not affected by TROVE-2017-004.)
8969 o Major bugfixes (hidden service, relay, security):
8970 - Fix a remotely triggerable assertion failure caused by receiving a
8971 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8972 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8975 o Minor features (geoip):
8976 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8979 o Minor bugfixes (correctness):
8980 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8981 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8983 Changes in version 0.2.4.29 - 2017-06-08
8984 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
8985 remotely crash a hidden service with an assertion failure. Anyone
8986 running a hidden service should upgrade to this version, or to some
8987 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8988 are not affected by TROVE-2017-004.)
8990 o Major bugfixes (hidden service, relay, security):
8991 - Fix a remotely triggerable assertion failure caused by receiving a
8992 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8993 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8996 o Minor features (geoip):
8997 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9000 o Minor bugfixes (correctness):
9001 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
9002 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
9005 Changes in version 0.3.1.2-alpha - 2017-05-26
9006 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
9007 fixes a few bugs found while testing 0.3.1.1-alpha, including a
9008 memory corruption bug that affected relay stability.
9010 o Major bugfixes (crash, relay):
9011 - Fix a memory-corruption bug in relays that set MyFamily.
9012 Previously, they would double-free MyFamily elements when making
9013 the next descriptor or when changing their configuration. Fixes
9014 bug 22368; bugfix on 0.3.1.1-alpha.
9016 o Minor bugfixes (logging):
9017 - Log a better message when a directory authority replies to an
9018 upload with an unexpected status code. Fixes bug 11121; bugfix
9021 o Minor bugfixes (memory leak, directory authority):
9022 - When directory authorities reject a router descriptor due to
9023 keypinning, free the router descriptor rather than leaking the
9024 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
9027 Changes in version 0.3.1.1-alpha - 2017-05-22
9028 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
9029 reduces the bandwidth usage for Tor's directory protocol, adds some
9030 basic padding to resist netflow-based traffic analysis and to serve as
9031 the basis of other padding in the future, and adds rust support to the
9034 It also contains numerous other small features and improvements to
9035 security, correctness, and performance.
9037 Below are the changes since 0.3.0.7.
9039 o Major features (directory protocol):
9040 - Tor relays and authorities can now serve clients an abbreviated
9041 version of the consensus document, containing only the changes
9042 since an older consensus document that the client holds. Clients
9043 now request these documents when available. When both client and
9044 server use this new protocol, they will use far less bandwidth (up
9045 to 94% less) to keep the client's consensus up-to-date. Implements
9046 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
9047 - Tor can now compress directory traffic with lzma or with zstd
9048 compression algorithms, which can deliver better bandwidth
9049 performance. Because lzma is computationally expensive, it's only
9050 used for documents that can be compressed once and served many
9051 times. Support for these algorithms requires that tor is built
9052 with the libzstd and/or liblzma libraries available. Implements
9053 proposal 278; closes ticket 21662.
9054 - Relays now perform the more expensive compression operations, and
9055 consensus diff generation, in worker threads. This separation
9056 avoids delaying the main thread when a new consensus arrives.
9058 o Major features (experimental):
9059 - Tor can now build modules written in Rust. To turn this on, pass
9060 the "--enable-rust" flag to the configure script. It's not time to
9061 get excited yet: currently, there is no actual Rust functionality
9062 beyond some simple glue code, and a notice at startup to tell you
9063 that Rust is running. Still, we hope that programmers and
9064 packagers will try building Tor with Rust support, so that we can
9065 find issues and solve portability problems. Closes ticket 22106.
9067 o Major features (traffic analysis resistance):
9068 - Connections between clients and relays now send a padding cell in
9069 each direction every 1.5 to 9.5 seconds (tunable via consensus
9070 parameters). This padding will not resist specialized
9071 eavesdroppers, but it should be enough to make many ISPs' routine
9072 network flow logging less useful in traffic analysis against
9075 Padding is negotiated using Tor's link protocol, so both relays
9076 and clients must upgrade for this to take effect. Clients may
9077 still send padding despite the relay's version by setting
9078 ConnectionPadding 1 in torrc, and may disable padding by setting
9079 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
9080 users with the torrc option ReducedConnectionPadding. Implements
9081 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
9082 - Relays will publish 24 hour totals of padding and non-padding cell
9083 counts to their extra-info descriptors, unless PaddingStatistics 0
9084 is set in torrc. These 24 hour totals are also rounded to
9087 o Major bugfixes (connection usage):
9088 - We use NETINFO cells to try to determine if both relays involved
9089 in a connection will agree on the canonical status of that
9090 connection. We prefer the connections where this is the case for
9091 extend cells, and try to close connections where relays disagree
9092 on their canonical status early. Also, we now prefer the oldest
9093 valid connection for extend cells. These two changes should reduce
9094 the number of long-term connections that are kept open between
9095 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
9096 - Relays now log hourly statistics (look for
9097 "channel_check_for_duplicates" lines) on the total number of
9098 connections to other relays. If the number of connections per
9099 relay is unexpectedly large, this log message is at notice level.
9100 Otherwise it is at info.
9102 o Major bugfixes (entry guards):
9103 - Don't block bootstrapping when a primary bridge is offline and we
9104 can't get its descriptor. Fixes bug 22325; fixes one case of bug
9105 21969; bugfix on 0.3.0.3-alpha.
9107 o Major bugfixes (linux TPROXY support):
9108 - Fix a typo that had prevented TPROXY-based transparent proxying
9109 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9110 Patch from "d4fq0fQAgoJ".
9112 o Minor features (security, windows):
9113 - Enable a couple of pieces of Windows hardening: one
9114 (HeapEnableTerminationOnCorruption) that has been on-by-default
9115 since Windows 8, and unavailable before Windows 7; and one
9116 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9117 affect us, but shouldn't do any harm. Closes ticket 21953.
9119 o Minor features (config options):
9120 - Allow "%include" directives in torrc configuration files. These
9121 directives import the settings from other files, or from all the
9122 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
9123 - Make SAVECONF return an error when overwriting a torrc that has
9124 includes. Using SAVECONF with the FORCE option will allow it to
9125 overwrite torrc even if includes are used. Related to ticket 1922.
9126 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
9127 will work without the FORCE option. Related to ticket 1922.
9129 o Minor features (controller):
9130 - Warn the first time that a controller requests data in the long-
9131 deprecated 'GETINFO network-status' format. Closes ticket 21703.
9133 o Minor features (defaults):
9134 - The default value for UseCreateFast is now 0: clients which
9135 haven't yet received a consensus document will now use a proper
9136 ntor handshake to talk to their directory servers whenever they
9137 can. Closes ticket 21407.
9138 - Onion key rotation and expiry intervals are now defined as a
9139 network consensus parameter, per proposal 274. The default
9140 lifetime of an onion key is increased from 7 to 28 days. Old onion
9141 keys will expire after 7 days by default. This change will make
9142 consensus diffs much smaller, and save significant bandwidth.
9143 Closes ticket 21641.
9145 o Minor features (fallback directory list):
9146 - Update the fallback directory mirror whitelist and blacklist based
9147 on operator emails. Closes task 21121.
9148 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
9149 December 2016 (of which ~126 were still functional) with a list of
9150 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
9151 2017. Resolves ticket 21564.
9153 o Minor features (hidden services, logging):
9154 - Log a message when a hidden service descriptor has fewer
9155 introduction points than specified in
9156 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
9157 - Log a message when a hidden service reaches its introduction point
9158 circuit limit, and when that limit is reset. Follow up to ticket
9159 21594; closes ticket 21622.
9160 - Warn user if multiple entries in EntryNodes and at least one
9161 HiddenService are used together. Pinning EntryNodes along with a
9162 hidden service can be possibly harmful; for instance see ticket
9163 14917 or 21155. Closes ticket 21155.
9165 o Minor features (linux seccomp2 sandbox):
9166 - We now have a document storage backend compatible with the Linux
9167 seccomp2 sandbox. This backend is used for consensus documents and
9168 diffs between them; in the long term, we'd like to use it for
9169 unparseable directory material too. Closes ticket 21645
9170 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
9171 from 1MB to 16MB. This was necessary with the glibc allocator in
9172 order to allow worker threads to allocate more memory -- which in
9173 turn is necessary because of our new use of worker threads for
9174 compression. Closes ticket 22096.
9176 o Minor features (logging):
9177 - Log files are no longer created world-readable by default.
9178 (Previously, most distributors would store the logs in a non-
9179 world-readable location to prevent inappropriate access. This
9180 change is an extra precaution.) Closes ticket 21729; patch
9183 o Minor features (performance):
9184 - Our Keccak (SHA-3) implementation now accesses memory more
9185 efficiently, especially on little-endian systems. Closes
9187 - Add an O(1) implementation of channel_find_by_global_id(), to
9188 speed some controller functions.
9190 o Minor features (relay, configuration):
9191 - The MyFamily option may now be repeated as many times as desired,
9192 for relays that want to configure large families. Closes ticket
9193 4998; patch by Daniel Pinto.
9195 o Minor features (safety):
9196 - Add an explicit check to extrainfo_parse_entry_from_string() for
9197 NULL inputs. We don't believe this can actually happen, but it may
9198 help silence a warning from the Clang analyzer. Closes
9201 o Minor features (testing):
9202 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
9203 When Tor is compiled with this option, we disable a number of
9204 redundant memory-safety failsafes that are intended to stop bugs
9205 from becoming security issues. This makes it easier to hunt for
9206 bugs that would be security issues without the failsafes turned
9207 on. Closes ticket 21439.
9208 - Add a general event-tracing instrumentation support to Tor. This
9209 subsystem will enable developers and researchers to add fine-
9210 grained instrumentation to their Tor instances, for use when
9211 examining Tor network performance issues. There are no trace
9212 events yet, and event-tracing is off by default unless enabled at
9213 compile time. Implements ticket 13802.
9214 - Improve our version parsing tests: add tests for typical version
9215 components, add tests for invalid versions, including numeric
9216 range and non-numeric prefixes. Unit tests 21278, 21450, and
9217 21507. Partially implements 21470.
9219 o Minor bugfixes (bandwidth accounting):
9220 - Roll over monthly accounting at the configured hour and minute,
9221 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9222 Found by Andrey Karpov with PVS-Studio.
9224 o Minor bugfixes (code correctness):
9225 - Accurately identify client connections by their lack of peer
9226 authentication. This means that we bail out earlier if asked to
9227 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
9230 o Minor bugfixes (configuration):
9231 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
9232 bug 22252; bugfix on 0.2.9.3-alpha.
9234 o Minor bugfixes (connection lifespan):
9235 - Allow more control over how long TLS connections are kept open:
9236 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
9237 single option called CircuitsAvailableTimeout. Also, allow the
9238 consensus to control the default values for both this preference
9239 and the lifespan of relay-to-relay connections. Fixes bug 17592;
9240 bugfix on 0.2.5.5-alpha.
9241 - Increase the initial circuit build timeout testing frequency, to
9242 help ensure that ReducedConnectionPadding clients finish learning
9243 a timeout before their orconn would expire. The initial testing
9244 rate was set back in the days of TAP and before the Tor Browser
9245 updater, when we had to be much more careful about new clients
9246 making lots of circuits. With this change, a circuit build timeout
9247 is learned in about 15-20 minutes, instead of 100-120 minutes.
9249 o Minor bugfixes (controller):
9250 - GETINFO onions/current and onions/detached no longer respond with
9251 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
9252 - Trigger HS descriptor events on the control port when the client
9253 fails to pick a hidden service directory for a hidden service.
9254 This can happen if all the hidden service directories are in
9255 ExcludeNodes, or they have all been queried within the last 15
9256 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
9258 o Minor bugfixes (directory authority):
9259 - When rejecting a router descriptor for running an obsolete version
9260 of Tor without ntor support, warn about the obsolete tor version,
9261 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
9262 - Prevent the shared randomness subsystem from asserting when
9263 initialized by a bridge authority with an incomplete configuration
9264 file. Fixes bug 21586; bugfix on 0.2.9.8.
9266 o Minor bugfixes (exit-side DNS):
9267 - Fix an untriggerable assertion that checked the output of a
9268 libevent DNS error, so that the assertion actually behaves as
9269 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
9270 Karpov using PVS-Studio.
9272 o Minor bugfixes (fallback directories):
9273 - Make the usage example in updateFallbackDirs.py actually work, and
9274 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
9275 - Decrease the guard flag average required to be a fallback. This
9276 allows us to keep relays that have their guard flag removed when
9277 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9278 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
9279 bugfix on 0.2.8.1-alpha.
9280 - Make sure fallback directory mirrors have the same address, port,
9281 and relay identity key for at least 30 days before they are
9282 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9284 o Minor bugfixes (hidden services):
9285 - Stop printing a cryptic warning when a hidden service gets a
9286 request to connect to a virtual port that it hasn't configured.
9287 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
9288 - Simplify hidden service descriptor creation by using an existing
9289 flag to check if an introduction point is established. Fixes bug
9290 21599; bugfix on 0.2.7.2-alpha.
9292 o Minor bugfixes (memory leak):
9293 - Fix a small memory leak at exit from the backtrace handler code.
9294 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
9296 o Minor bugfixes (protocol, logging):
9297 - Downgrade a log statement about unexpected relay cells from "bug"
9298 to "protocol warning", because there is at least one use case
9299 where it can be triggered by a buggy tor implementation. Fixes bug
9300 21293; bugfix on 0.1.1.14-alpha.
9302 o Minor bugfixes (testing):
9303 - Use unbuffered I/O for utility functions around the
9304 process_handle_t type. This fixes unit test failures reported on
9305 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
9306 - Make display of captured unit test log messages consistent. Fixes
9307 bug 21510; bugfix on 0.2.9.3-alpha.
9308 - Make test-network.sh always call chutney's test-network.sh.
9309 Previously, this only worked on systems which had bash installed,
9310 due to some bash-specific code in the script. Fixes bug 19699;
9311 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
9313 o Minor bugfixes (voting consistency):
9314 - Reject version numbers with non-numeric prefixes (such as +, -, or
9315 whitespace). Disallowing whitespace prevents differential version
9316 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9317 and part of 21508; bugfix on 0.0.8pre1.
9319 o Minor bugfixes (windows, relay):
9320 - Resolve "Failure from drain_fd: No error" warnings on Windows
9321 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
9323 o Code simplification and refactoring:
9324 - Break up the 630-line function connection_dir_client_reached_eof()
9325 into a dozen smaller functions. This change should help
9326 maintainability and readability of the client directory code.
9327 - Isolate our use of the openssl headers so that they are only
9328 included from our crypto wrapper modules, and from tests that
9329 examine those modules' internals. Closes ticket 21841.
9330 - Simplify our API to launch directory requests, making it more
9331 extensible and less error-prone. Now it's easier to add extra
9332 headers to directory requests. Closes ticket 21646.
9333 - Our base64 decoding functions no longer overestimate the output
9334 space that they need when parsing unpadded inputs. Closes
9336 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
9337 Resolves ticket 22213.
9338 - The logic that directory caches use to spool request to clients,
9339 serving them one part at a time so as not to allocate too much
9340 memory, has been refactored for consistency. Previously there was
9341 a separate spooling implementation per type of spoolable data. Now
9342 there is one common spooling implementation, with extensible data
9343 types. Closes ticket 21651.
9344 - Tor's compression module now supports multiple backends. Part of
9345 the implementation for proposal 278; closes ticket 21663.
9348 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
9349 Closes ticket 21873.
9350 - Correct documentation about the default DataDirectory value.
9351 Closes ticket 21151.
9352 - Document the default behavior of NumEntryGuards and
9353 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
9355 - Document key=value pluggable transport arguments for Bridge lines
9356 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
9357 - Note that bandwidth-limiting options don't affect TCP headers or
9358 DNS. Closes ticket 17170.
9360 o Removed features (configuration options, all in ticket 22060):
9361 - These configuration options are now marked Obsolete, and no longer
9362 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
9363 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
9364 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
9365 in 0.2.9.2-alpha and have now been removed. The previous default
9366 behavior is now always chosen; the previous (less secure) non-
9367 default behavior is now unavailable.
9368 - CloseHSClientCircuitsImmediatelyOnTimeout and
9369 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
9370 0.2.9.2-alpha and now have been removed. HS circuits never close
9371 on circuit build timeout; they have a longer timeout period.
9372 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
9373 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
9374 (and others) to configure listen-only and advertise-only addresses.
9376 o Removed features (tools):
9377 - We've removed the tor-checkkey tool from src/tools. Long ago, we
9378 used it to help people detect RSA keys that were generated by
9379 versions of Debian affected by CVE-2008-0166. But those keys have
9380 been out of circulation for ages, and this tool is no longer
9381 required. Closes ticket 21842.
9384 Changes in version 0.3.0.7 - 2017-05-15
9385 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
9386 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
9387 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
9388 clients are not affected.
9390 o Major bugfixes (hidden service directory, security):
9391 - Fix an assertion failure in the hidden service directory code, which
9392 could be used by an attacker to remotely cause a Tor relay process to
9393 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
9394 should upgrade. This security issue is tracked as TROVE-2017-002.
9395 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
9398 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9401 o Minor features (future-proofing):
9402 - Tor no longer refuses to download microdescriptors or descriptors
9403 if they are listed as "published in the future". This change will
9404 eventually allow us to stop listing meaningful "published" dates
9405 in microdescriptor consensuses, and thereby allow us to reduce the
9406 resources required to download consensus diffs by over 50%.
9407 Implements part of ticket 21642; implements part of proposal 275.
9409 o Minor bugfixes (Linux seccomp2 sandbox):
9410 - The getpid() system call is now permitted under the Linux seccomp2
9411 sandbox, to avoid crashing with versions of OpenSSL (and other
9412 libraries) that attempt to learn the process's PID by using the
9413 syscall rather than the VDSO code. Fixes bug 21943; bugfix
9417 Changes in version 0.3.0.6 - 2017-04-26
9418 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
9420 With the 0.3.0 series, clients and relays now use Ed25519 keys to
9421 authenticate their link connections to relays, rather than the old
9422 RSA1024 keys that they used before. (Circuit crypto has been
9423 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
9424 the guard selection and replacement algorithm to behave more robustly
9425 in the presence of unreliable networks, and to resist guard-
9428 This series also includes numerous other small features and bugfixes,
9429 along with more groundwork for the upcoming hidden-services revamp.
9431 Per our stable release policy, we plan to support the Tor 0.3.0
9432 release series for at least the next nine months, or for three months
9433 after the first stable release of the 0.3.1 series: whichever is
9434 longer. If you need a release with long-term support, we recommend
9435 that you stay with the 0.2.9 series.
9437 Below are the changes since 0.3.0.5-rc. For a list of all changes
9438 since 0.2.9, see the ReleaseNotes file.
9440 o Minor features (geoip):
9441 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
9444 o Minor bugfixes (control port):
9445 - The GETINFO extra-info/digest/<digest> command was broken because
9446 of a wrong base16 decode return value check, introduced when
9447 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
9449 o Minor bugfixes (crash prevention):
9450 - Fix a (currently untriggerable, but potentially dangerous) crash
9451 bug when base32-encoding inputs whose sizes are not a multiple of
9452 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
9455 Changes in version 0.3.0.5-rc - 2017-04-05
9456 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
9457 0.3.0 release series.
9459 This is the second release candidate in the Tor 0.3.0 series, and has
9460 much fewer changes than the first. If we find no new bugs or
9461 regressions here, the first stable 0.3.0 release will be nearly
9464 o Major bugfixes (crash, directory connections):
9465 - Fix a rare crash when sending a begin cell on a circuit whose
9466 linked directory connection had already been closed. Fixes bug
9467 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9469 o Major bugfixes (guard selection):
9470 - Fix a guard selection bug where Tor would refuse to bootstrap in
9471 some cases if the user swapped a bridge for another bridge in
9472 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
9473 Reported by "torvlnt33r".
9475 o Minor features (geoip):
9476 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
9479 o Minor bugfix (compilation):
9480 - Fix a warning when compiling hs_service.c. Previously, it had no
9481 exported symbols when compiled for libor.a, resulting in a
9482 compilation warning from clang. Fixes bug 21825; bugfix
9485 o Minor bugfixes (hidden services):
9486 - Make hidden services check for failed intro point connections,
9487 even when they have exceeded their intro point creation limit.
9488 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
9489 - Make hidden services with 8 to 10 introduction points check for
9490 failed circuits immediately after startup. Previously, they would
9491 wait for 5 minutes before performing their first checks. Fixes bug
9492 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
9494 o Minor bugfixes (memory leaks):
9495 - Fix a memory leak when using GETCONF on a port option. Fixes bug
9496 21682; bugfix on 0.3.0.3-alpha.
9498 o Minor bugfixes (relay):
9499 - Avoid a double-marked-circuit warning that could happen when we
9500 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9503 o Minor bugfixes (tests):
9504 - Run the entry_guard_parse_from_state_full() test with the time set
9505 to a specific date. (The guard state that this test was parsing
9506 contained guards that had expired since the test was first
9507 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
9510 - Update the description of the directory server options in the
9511 manual page, to clarify that a relay no longer needs to set
9512 DirPort in order to be a directory cache. Closes ticket 21720.
9516 Changes in version 0.2.8.13 - 2017-03-03
9517 Tor 0.2.8.13 backports a security fix from later Tor
9518 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9519 this release, if for some reason they cannot upgrade to a later
9520 release series, and if they build Tor with the --enable-expensive-hardening
9523 Note that support for Tor 0.2.8.x is ending next year: we will not issue
9524 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
9525 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9527 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9528 - Fix an integer underflow bug when comparing malformed Tor
9529 versions. This bug could crash Tor when built with
9530 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9531 0.2.9.8, which were built with -ftrapv by default. In other cases
9532 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9533 on 0.0.8pre1. Found by OSS-Fuzz.
9535 o Minor features (geoip):
9536 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9540 Changes in version 0.2.7.7 - 2017-03-03
9541 Tor 0.2.7.7 backports a number of security fixes from later Tor
9542 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
9543 this release, if for some reason they cannot upgrade to a later
9546 Note that support for Tor 0.2.7.x is ending this year: we will not issue
9547 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
9548 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9550 o Directory authority changes (backport from 0.2.8.5-rc):
9551 - Urras is no longer a directory authority. Closes ticket 19271.
9553 o Directory authority changes (backport from 0.2.9.2-alpha):
9554 - The "Tonga" bridge authority has been retired; the new bridge
9555 authority is "Bifroest". Closes tickets 19728 and 19690.
9557 o Directory authority key updates (backport from 0.2.8.1-alpha):
9558 - Update the V3 identity key for the dannenberg directory authority:
9559 it was changed on 18 November 2015. Closes task 17906. Patch
9562 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9563 - Fix a bug in parsing that could cause clients to read a single
9564 byte past the end of an allocated region. This bug could be used
9565 to cause hardened clients (built with --enable-expensive-hardening)
9566 to crash if they tried to visit a hostile hidden service. Non-
9567 hardened clients are only affected depending on the details of
9568 their platform's memory allocator. Fixes bug 21018; bugfix on
9569 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9570 2016-12-002 and as CVE-2016-1254.
9572 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9573 - Stop a crash that could occur when a client running with DNSPort
9574 received a query with multiple address types, and the first
9575 address type was not supported. Found and fixed by Scott Dial.
9576 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9577 - Prevent a class of security bugs caused by treating the contents
9578 of a buffer chunk as if they were a NUL-terminated string. At
9579 least one such bug seems to be present in all currently used
9580 versions of Tor, and would allow an attacker to remotely crash
9581 most Tor instances, especially those compiled with extra compiler
9582 hardening. With this defense in place, such bugs can't crash Tor,
9583 though we should still fix them as they occur. Closes ticket
9584 20384 (TROVE-2016-10-001).
9586 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9587 - Avoid a difficult-to-trigger heap corruption attack when extending
9588 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9589 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9590 Reported by Guido Vranken.
9592 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9593 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9594 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9596 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9597 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9598 pointer to the previous (uninitialized) key value. The impact here
9599 should be limited to a difficult-to-trigger crash, if OpenSSL is
9600 running an engine that makes key generation failures possible, or
9601 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9602 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9605 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9606 - Fix an integer underflow bug when comparing malformed Tor
9607 versions. This bug could crash Tor when built with
9608 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9609 0.2.9.8, which were built with -ftrapv by default. In other cases
9610 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9611 on 0.0.8pre1. Found by OSS-Fuzz.
9613 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9614 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9615 zero size. Check size argument to memwipe() for underflow. Fixes
9616 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9619 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9620 - Make Tor survive errors involving connections without a
9621 corresponding event object. Previously we'd fail with an
9622 assertion; now we produce a log message. Related to bug 16248.
9624 o Minor features (geoip):
9625 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9629 Changes in version 0.2.6.11 - 2017-03-03
9630 Tor 0.2.6.11 backports a number of security fixes from later Tor
9631 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
9632 this release, if for some reason they cannot upgrade to a later
9635 Note that support for Tor 0.2.6.x is ending this year: we will not issue
9636 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
9637 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9639 o Directory authority changes (backport from 0.2.8.5-rc):
9640 - Urras is no longer a directory authority. Closes ticket 19271.
9642 o Directory authority changes (backport from 0.2.9.2-alpha):
9643 - The "Tonga" bridge authority has been retired; the new bridge
9644 authority is "Bifroest". Closes tickets 19728 and 19690.
9646 o Directory authority key updates (backport from 0.2.8.1-alpha):
9647 - Update the V3 identity key for the dannenberg directory authority:
9648 it was changed on 18 November 2015. Closes task 17906. Patch
9651 o Major features (security fixes, backport from 0.2.9.4-alpha):
9652 - Prevent a class of security bugs caused by treating the contents
9653 of a buffer chunk as if they were a NUL-terminated string. At
9654 least one such bug seems to be present in all currently used
9655 versions of Tor, and would allow an attacker to remotely crash
9656 most Tor instances, especially those compiled with extra compiler
9657 hardening. With this defense in place, such bugs can't crash Tor,
9658 though we should still fix them as they occur. Closes ticket
9659 20384 (TROVE-2016-10-001).
9661 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9662 - Fix a bug in parsing that could cause clients to read a single
9663 byte past the end of an allocated region. This bug could be used
9664 to cause hardened clients (built with --enable-expensive-hardening)
9665 to crash if they tried to visit a hostile hidden service. Non-
9666 hardened clients are only affected depending on the details of
9667 their platform's memory allocator. Fixes bug 21018; bugfix on
9668 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9669 2016-12-002 and as CVE-2016-1254.
9671 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9672 - Stop a crash that could occur when a client running with DNSPort
9673 received a query with multiple address types, and the first
9674 address type was not supported. Found and fixed by Scott Dial.
9675 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9677 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9678 - Fix an error that could cause us to read 4 bytes before the
9679 beginning of an openssl string. This bug could be used to cause
9680 Tor to crash on systems with unusual malloc implementations, or
9681 systems with unusual hardening installed. Fixes bug 17404; bugfix
9684 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9685 - Avoid a difficult-to-trigger heap corruption attack when extending
9686 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9687 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9688 Reported by Guido Vranken.
9690 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9691 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9692 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9694 o Major bugfixes (guard selection, backport from 0.2.7.6):
9695 - Actually look at the Guard flag when selecting a new directory
9696 guard. When we implemented the directory guard design, we
9697 accidentally started treating all relays as if they have the Guard
9698 flag during guard selection, leading to weaker anonymity and worse
9699 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9702 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9703 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9704 pointer to the previous (uninitialized) key value. The impact here
9705 should be limited to a difficult-to-trigger crash, if OpenSSL is
9706 running an engine that makes key generation failures possible, or
9707 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9708 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9711 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
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 features (security, memory erasure, backport from 0.2.8.1-alpha):
9720 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9721 zero size. Check size argument to memwipe() for underflow. Fixes
9722 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9725 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9726 - Make Tor survive errors involving connections without a
9727 corresponding event object. Previously we'd fail with an
9728 assertion; now we produce a log message. Related to bug 16248.
9730 o Minor features (geoip):
9731 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9734 o Minor bugfixes (compilation, backport from 0.2.7.6):
9735 - Fix a compilation warning with Clang 3.6: Do not check the
9736 presence of an address which can never be NULL. Fixes bug 17781.
9739 Changes in version 0.2.5.13 - 2017-03-03
9740 Tor 0.2.5.13 backports a number of security fixes from later Tor
9741 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9742 this release, if for some reason they cannot upgrade to a later
9745 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9746 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9747 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9749 o Directory authority changes (backport from 0.2.8.5-rc):
9750 - Urras is no longer a directory authority. Closes ticket 19271.
9752 o Directory authority changes (backport from 0.2.9.2-alpha):
9753 - The "Tonga" bridge authority has been retired; the new bridge
9754 authority is "Bifroest". Closes tickets 19728 and 19690.
9756 o Directory authority key updates (backport from 0.2.8.1-alpha):
9757 - Update the V3 identity key for the dannenberg directory authority:
9758 it was changed on 18 November 2015. Closes task 17906. Patch
9761 o Major features (security fixes, backport from 0.2.9.4-alpha):
9762 - Prevent a class of security bugs caused by treating the contents
9763 of a buffer chunk as if they were a NUL-terminated string. At
9764 least one such bug seems to be present in all currently used
9765 versions of Tor, and would allow an attacker to remotely crash
9766 most Tor instances, especially those compiled with extra compiler
9767 hardening. With this defense in place, such bugs can't crash Tor,
9768 though we should still fix them as they occur. Closes ticket
9769 20384 (TROVE-2016-10-001).
9771 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9772 - Fix a bug in parsing that could cause clients to read a single
9773 byte past the end of an allocated region. This bug could be used
9774 to cause hardened clients (built with --enable-expensive-hardening)
9775 to crash if they tried to visit a hostile hidden service. Non-
9776 hardened clients are only affected depending on the details of
9777 their platform's memory allocator. Fixes bug 21018; bugfix on
9778 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9779 2016-12-002 and as CVE-2016-1254.
9781 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9782 - Stop a crash that could occur when a client running with DNSPort
9783 received a query with multiple address types, and the first
9784 address type was not supported. Found and fixed by Scott Dial.
9785 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9787 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9788 - Fix an error that could cause us to read 4 bytes before the
9789 beginning of an openssl string. This bug could be used to cause
9790 Tor to crash on systems with unusual malloc implementations, or
9791 systems with unusual hardening installed. Fixes bug 17404; bugfix
9794 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9795 - Avoid a difficult-to-trigger heap corruption attack when extending
9796 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9797 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9798 Reported by Guido Vranken.
9800 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9801 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9802 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9804 o Major bugfixes (guard selection, backport from 0.2.7.6):
9805 - Actually look at the Guard flag when selecting a new directory
9806 guard. When we implemented the directory guard design, we
9807 accidentally started treating all relays as if they have the Guard
9808 flag during guard selection, leading to weaker anonymity and worse
9809 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9812 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9813 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9814 pointer to the previous (uninitialized) key value. The impact here
9815 should be limited to a difficult-to-trigger crash, if OpenSSL is
9816 running an engine that makes key generation failures possible, or
9817 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9818 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9821 o Major bugfixes (parsing, backported from 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 (security, memory erasure, backport from 0.2.8.1-alpha):
9830 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9831 zero size. Check size argument to memwipe() for underflow. Fixes
9832 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9835 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9836 - Make Tor survive errors involving connections without a
9837 corresponding event object. Previously we'd fail with an
9838 assertion; now we produce a log message. Related to bug 16248.
9840 o Minor features (geoip):
9841 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9844 o Minor bugfixes (compilation, backport from 0.2.7.6):
9845 - Fix a compilation warning with Clang 3.6: Do not check the
9846 presence of an address which can never be NULL. Fixes bug 17781.
9848 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9849 - Check for failures from crypto_early_init, and refuse to continue.
9850 A previous typo meant that we could keep going with an
9851 uninitialized crypto library, and would have OpenSSL initialize
9852 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9853 when implementing ticket 4900. Patch by "teor".
9855 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9856 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9857 a client authorized hidden service. Fixes bug 15823; bugfix
9861 Changes in version 0.2.4.28 - 2017-03-03
9862 Tor 0.2.4.28 backports a number of security fixes from later Tor
9863 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9864 this release, if for some reason they cannot upgrade to a later
9867 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9868 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9869 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9871 o Directory authority changes (backport from 0.2.8.5-rc):
9872 - Urras is no longer a directory authority. Closes ticket 19271.
9874 o Directory authority changes (backport from 0.2.9.2-alpha):
9875 - The "Tonga" bridge authority has been retired; the new bridge
9876 authority is "Bifroest". Closes tickets 19728 and 19690.
9878 o Directory authority key updates (backport from 0.2.8.1-alpha):
9879 - Update the V3 identity key for the dannenberg directory authority:
9880 it was changed on 18 November 2015. Closes task 17906. Patch
9883 o Major features (security fixes, backport from 0.2.9.4-alpha):
9884 - Prevent a class of security bugs caused by treating the contents
9885 of a buffer chunk as if they were a NUL-terminated string. At
9886 least one such bug seems to be present in all currently used
9887 versions of Tor, and would allow an attacker to remotely crash
9888 most Tor instances, especially those compiled with extra compiler
9889 hardening. With this defense in place, such bugs can't crash Tor,
9890 though we should still fix them as they occur. Closes ticket
9891 20384 (TROVE-2016-10-001).
9893 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9894 - Fix a bug in parsing that could cause clients to read a single
9895 byte past the end of an allocated region. This bug could be used
9896 to cause hardened clients (built with --enable-expensive-hardening)
9897 to crash if they tried to visit a hostile hidden service. Non-
9898 hardened clients are only affected depending on the details of
9899 their platform's memory allocator. Fixes bug 21018; bugfix on
9900 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9901 2016-12-002 and as CVE-2016-1254.
9903 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9904 - Fix an error that could cause us to read 4 bytes before the
9905 beginning of an openssl string. This bug could be used to cause
9906 Tor to crash on systems with unusual malloc implementations, or
9907 systems with unusual hardening installed. Fixes bug 17404; bugfix
9910 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9911 - Avoid a difficult-to-trigger heap corruption attack when extending
9912 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9913 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9914 Reported by Guido Vranken.
9916 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9917 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9918 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9920 o Major bugfixes (guard selection, backport from 0.2.7.6):
9921 - Actually look at the Guard flag when selecting a new directory
9922 guard. When we implemented the directory guard design, we
9923 accidentally started treating all relays as if they have the Guard
9924 flag during guard selection, leading to weaker anonymity and worse
9925 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9928 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9929 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9930 pointer to the previous (uninitialized) key value. The impact here
9931 should be limited to a difficult-to-trigger crash, if OpenSSL is
9932 running an engine that makes key generation failures possible, or
9933 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9934 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9937 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9938 - Fix an integer underflow bug when comparing malformed Tor
9939 versions. This bug could crash Tor when built with
9940 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9941 0.2.9.8, which were built with -ftrapv by default. In other cases
9942 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9943 on 0.0.8pre1. Found by OSS-Fuzz.
9945 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9946 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9947 zero size. Check size argument to memwipe() for underflow. Fixes
9948 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9951 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9952 - Make Tor survive errors involving connections without a
9953 corresponding event object. Previously we'd fail with an
9954 assertion; now we produce a log message. Related to bug 16248.
9956 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
9957 - Make it harder for attackers to overload hidden services with
9958 introductions, by blocking multiple introduction requests on the
9959 same circuit. Resolves ticket 15515.
9961 o Minor features (geoip):
9962 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9965 o Minor bugfixes (compilation, backport from 0.2.7.6):
9966 - Fix a compilation warning with Clang 3.6: Do not check the
9967 presence of an address which can never be NULL. Fixes bug 17781.
9969 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9970 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9971 a client authorized hidden service. Fixes bug 15823; bugfix
9975 Changes in version 0.3.0.4-rc - 2017-03-01
9976 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
9977 0.3.0 release series, and introduces a few reliability features to
9978 keep them from coming back.
9980 This is the first release candidate in the Tor 0.3.0 series. If we
9981 find no new bugs or regressions here, the first stable 0.3.0 release
9982 will be nearly identical to it.
9984 o Major bugfixes (bridges):
9985 - When the same bridge is configured multiple times with the same
9986 identity, but at different address:port combinations, treat those
9987 bridge instances as separate guards. This fix restores the ability
9988 of clients to configure the same bridge with multiple pluggable
9989 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
9991 o Major bugfixes (hidden service directory v3):
9992 - Stop crashing on a failed v3 hidden service descriptor lookup
9993 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
9995 o Major bugfixes (parsing):
9996 - When parsing a malformed content-length field from an HTTP
9997 message, do not read off the end of the buffer. This bug was a
9998 potential remote denial-of-service attack against Tor clients and
9999 relays. A workaround was released in October 2016, to prevent this
10000 bug from crashing Tor. This is a fix for the underlying issue,
10001 which should no longer matter (if you applied the earlier patch).
10002 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
10003 using AFL (http://lcamtuf.coredump.cx/afl/).
10004 - Fix an integer underflow bug when comparing malformed Tor
10005 versions. This bug could crash Tor when built with
10006 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10007 0.2.9.8, which were built with -ftrapv by default. In other cases
10008 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10009 on 0.0.8pre1. Found by OSS-Fuzz.
10011 o Minor feature (protocol versioning):
10012 - Add new protocol version for proposal 224. HSIntro now advertises
10013 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
10015 o Minor features (directory authorities):
10016 - Directory authorities now reject descriptors that claim to be
10017 malformed versions of Tor. Helps prevent exploitation of
10019 - Reject version numbers with components that exceed INT32_MAX.
10020 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10021 Fixes bug 21450; bugfix on 0.0.8pre1.
10022 - Directory authorities now reject relays running versions
10023 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
10024 suffer from bug 20499 and don't keep their consensus cache
10025 up-to-date. Resolves ticket 20509.
10027 o Minor features (geoip):
10028 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10031 o Minor features (reliability, crash):
10032 - Try better to detect problems in buffers where they might grow (or
10033 think they have grown) over 2 GB in size. Diagnostic for
10036 o Minor features (testing):
10037 - During 'make test-network-all', if tor logs any warnings, ask
10038 chutney to output them. Requires a recent version of chutney with
10039 the 21572 patch. Implements 21570.
10041 o Minor bugfixes (certificate expiration time):
10042 - Avoid using link certificates that don't become valid till some
10043 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
10045 o Minor bugfixes (code correctness):
10046 - Repair a couple of (unreachable or harmless) cases of the risky
10047 comparison-by-subtraction pattern that caused bug 21278.
10048 - Remove a redundant check for the UseEntryGuards option from the
10049 options_transition_affects_guards() function. Fixes bug 21492;
10050 bugfix on 0.3.0.1-alpha.
10052 o Minor bugfixes (directory mirrors):
10053 - Allow relays to use directory mirrors without a DirPort: these
10054 relays need to be contacted over their ORPorts using a begindir
10055 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
10056 - Clarify the message logged when a remote relay is unexpectedly
10057 missing an ORPort or DirPort: users were confusing this with a
10058 local port. Fixes another case of bug 20711; bugfix
10061 o Minor bugfixes (guards):
10062 - Don't warn about a missing guard state on timeout-measurement
10063 circuits: they aren't supposed to be using guards. Fixes an
10064 instance of bug 21007; bugfix on 0.3.0.1-alpha.
10065 - Silence a BUG() warning when attempting to use a guard whose
10066 descriptor we don't know, and make this scenario less likely to
10067 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
10069 o Minor bugfixes (hidden service):
10070 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
10071 cells. Previously, we were using sizeof() on a pointer, instead of
10072 the real destination buffer. Fortunately, that value was only used
10073 to double-check that there was enough room--which was already
10074 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
10076 o Minor bugfixes (testing):
10077 - Fix Raspbian build issues related to missing socket errno in
10078 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
10080 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
10081 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
10082 - Use bash in src/test/test-network.sh. This ensures we reliably
10083 call chutney's newer tools/test-network.sh when available. Fixes
10084 bug 21562; bugfix on 0.2.9.1-alpha.
10087 - Small fixes to the fuzzing documentation. Closes ticket 21472.
10090 Changes in version 0.2.9.10 - 2017-03-01
10091 Tor 0.2.9.10 backports a security fix from later Tor release. It also
10092 includes fixes for some major issues affecting directory authorities,
10093 LibreSSL compatibility, and IPv6 correctness.
10095 The Tor 0.2.9.x release series is now marked as a long-term-support
10096 series. We intend to backport security fixes to 0.2.9.x until at
10097 least January of 2020.
10099 o Major bugfixes (directory authority, 0.3.0.3-alpha):
10100 - During voting, when marking a relay as a probable sybil, do not
10101 clear its BadExit flag: sybils can still be bad in other ways
10102 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10105 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
10106 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10107 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10108 exit policy rejects that port on more than an IPv6 /16 of
10109 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10110 which rejected a relay's own IPv6 address by default. Fixes bug
10111 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10113 o Major bugfixes (parsing, also in 0.3.0.4-rc):
10114 - Fix an integer underflow bug when comparing malformed Tor
10115 versions. This bug could crash Tor when built with
10116 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10117 0.2.9.8, which were built with -ftrapv by default. In other cases
10118 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10119 on 0.0.8pre1. Found by OSS-Fuzz.
10121 o Minor features (directory authorities, also in 0.3.0.4-rc):
10122 - Directory authorities now reject descriptors that claim to be
10123 malformed versions of Tor. Helps prevent exploitation of
10125 - Reject version numbers with components that exceed INT32_MAX.
10126 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10127 Fixes bug 21450; bugfix on 0.0.8pre1.
10129 o Minor features (geoip):
10130 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10133 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
10134 - Autoconf now checks to determine if OpenSSL structures are opaque,
10135 instead of explicitly checking for OpenSSL version numbers. Part
10137 - Support building with recent LibreSSL code that uses opaque
10138 structures. Closes ticket 21359.
10140 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
10141 - Repair a couple of (unreachable or harmless) cases of the risky
10142 comparison-by-subtraction pattern that caused bug 21278.
10144 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
10145 - The tor-resolve command line tool now rejects hostnames over 255
10146 characters in length. Previously, it would silently truncate them,
10147 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10148 Patch by "junglefowl".
10151 Changes in version 0.3.0.3-alpha - 2017-02-03
10152 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
10153 0.3.0.x development series, including some that could cause
10154 authorities to behave badly. There is also a fix for a longstanding
10155 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
10156 includes some smaller features and bugfixes.
10158 The Tor 0.3.0.x release series is now in patch-freeze: no additional
10159 features will be considered for inclusion in 0.3.0.x. We suspect that
10160 some bugs will probably remain, however, and we encourage people to
10163 o Major bugfixes (directory authority):
10164 - During voting, when marking a relay as a probable sybil, do not
10165 clear its BadExit flag: sybils can still be bad in other ways
10166 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10168 - When deciding whether we have just found a router to be reachable,
10169 do not penalize it for not having performed an Ed25519 link
10170 handshake if it does not claim to support an Ed25519 handshake.
10171 Previously, we would treat such relays as non-running. Fixes bug
10172 21107; bugfix on 0.3.0.1-alpha.
10174 o Major bugfixes (entry guards):
10175 - Stop trying to build circuits through entry guards for which we
10176 have no descriptor. Also, stop crashing in the case that we *do*
10177 accidentally try to build a circuit in such a state. Fixes bug
10178 21242; bugfix on 0.3.0.1-alpha.
10180 o Major bugfixes (IPv6 Exits):
10181 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10182 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10183 exit policy rejects that port on more than an IPv6 /16 of
10184 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10185 which rejected a relay's own IPv6 address by default. Fixes bug
10186 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10188 o Minor feature (client):
10189 - Enable IPv6 traffic on the SocksPort by default. To disable this,
10190 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
10192 o Minor feature (fallback scripts):
10193 - Add a check_existing mode to updateFallbackDirs.py, which checks
10194 if fallbacks in the hard-coded list are working. Closes ticket
10195 20174. Patch by haxxpop.
10197 o Minor features (ciphersuite selection):
10198 - Clients now advertise a list of ciphersuites closer to the ones
10199 preferred by Firefox. Closes part of ticket 15426.
10200 - Allow relays to accept a wider range of ciphersuites, including
10201 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
10203 o Minor features (controller, configuration):
10204 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
10205 and so on, now comes with a __*Port variant that will not be saved
10206 to the torrc file by the controller's SAVECONF command. This
10207 change allows TorBrowser to set up a single-use domain socket for
10208 each time it launches Tor. Closes ticket 20956.
10209 - The GETCONF command can now query options that may only be
10210 meaningful in context-sensitive lists. This allows the controller
10211 to query the mixed SocksPort/__SocksPort style options introduced
10212 in feature 20956. Implements ticket 21300.
10214 o Minor features (portability, compilation):
10215 - Autoconf now checks to determine if OpenSSL structures are opaque,
10216 instead of explicitly checking for OpenSSL version numbers. Part
10218 - Support building with recent LibreSSL code that uses opaque
10219 structures. Closes ticket 21359.
10221 o Minor features (relay):
10222 - We now allow separation of exit and relay traffic to different
10223 source IP addresses, using the OutboundBindAddressExit and
10224 OutboundBindAddressOR options respectively. Closes ticket 17975.
10225 Written by Michael Sonntag.
10227 o Minor bugfix (logging):
10228 - Don't recommend the use of Tor2web in non-anonymous mode.
10229 Recommending Tor2web is a bad idea because the client loses all
10230 anonymity. Tor2web should only be used in specific cases by users
10231 who *know* and understand the issues. Fixes bug 21294; bugfix
10234 o Minor bugfixes (client):
10235 - Always recover from failures in extend_info_from_node(), in an
10236 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
10237 bugfix on 0.2.3.1-alpha.
10239 o Minor bugfixes (client, entry guards):
10240 - Fix a bug warning (with backtrace) when we fail a channel that
10241 circuits to fallback directories on it. Fixes bug 21128; bugfix
10243 - Fix a spurious bug warning (with backtrace) when removing an
10244 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
10245 - Fix a bug of the new guard algorithm where tor could stall for up
10246 to 10 minutes before retrying a guard after a long period of no
10247 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
10248 - Do not try to build circuits until we have descriptors for our
10249 primary entry guards. Related to fix for bug 21242.
10251 o Minor bugfixes (configure, autoconf):
10252 - Rename the configure option --enable-expensive-hardening to
10253 --enable-fragile-hardening. Expensive hardening makes the tor
10254 daemon abort when some kinds of issues are detected. Thus, it
10255 makes tor more at risk of remote crashes but safer against RCE or
10256 heartbleed bug category. We now try to explain this issue in a
10257 message from the configure script. Fixes bug 21290; bugfix
10260 o Minor bugfixes (controller):
10261 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
10262 20824; bugfix on 0.3.0.1-alpha.
10264 o Minor bugfixes (hidden service):
10265 - Clean up the code for expiring intro points with no associated
10266 circuits. It was causing, rarely, a service with some expiring
10267 introduction points to not open enough additional introduction
10268 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
10269 - Stop setting the torrc option HiddenServiceStatistics to "0" just
10270 because we're not a bridge or relay. Instead, we preserve whatever
10271 value the user set (or didn't set). Fixes bug 21150; bugfix
10273 - Resolve two possible underflows which could lead to creating and
10274 closing a lot of introduction point circuits in a non-stop loop.
10275 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
10277 o Minor bugfixes (portability):
10278 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
10279 It is supported by OpenBSD itself, and also by most OpenBSD
10280 variants (such as Bitrig). Fixes bug 20980; bugfix
10282 - When mapping a file of length greater than SIZE_MAX, do not
10283 silently truncate its contents. This issue could occur on 32 bit
10284 systems with large file support and files which are larger than 4
10285 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
10287 o Minor bugfixes (tor-resolve):
10288 - The tor-resolve command line tool now rejects hostnames over 255
10289 characters in length. Previously, it would silently truncate them,
10290 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10291 Patch by "junglefowl".
10293 o Minor bugfixes (Windows services):
10294 - Be sure to initialize the monotonic time subsystem before using
10295 it, even when running as an NT service. Fixes bug 21356; bugfix
10299 Changes in version 0.3.0.2-alpha - 2017-01-23
10300 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
10301 cause relays and clients to crash, even if they were not built with
10302 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10303 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10304 version should upgrade.
10306 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
10307 time-to-live values, makes directory authorities enforce the 1-to-1
10308 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
10309 client-side onion service reachability bug, does better at selecting
10310 the set of fallback directories, and more.
10312 o Major bugfixes (security, also in 0.2.9.9):
10313 - Downgrade the "-ftrapv" option from "always on" to "only on when
10314 --enable-expensive-hardening is provided." This hardening option, like
10315 others, can turn survivable bugs into crashes--and having it on by
10316 default made a (relatively harmless) integer overflow bug into a
10317 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
10320 o Major features (security):
10321 - Change the algorithm used to decide DNS TTLs on client and server
10322 side, to better resist DNS-based correlation attacks like the
10323 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10324 Feamster. Now relays only return one of two possible DNS TTL
10325 values, and clients are willing to believe DNS TTL values up to 3
10326 hours long. Closes ticket 19769.
10328 o Major features (directory authority, security):
10329 - The default for AuthDirPinKeys is now 1: directory authorities
10330 will reject relays where the RSA identity key matches a previously
10331 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10333 o Major bugfixes (client, guard, crash):
10334 - In circuit_get_global_origin_list(), return the actual list of
10335 origin circuits. The previous version of this code returned the
10336 list of all the circuits, and could have caused strange bugs,
10337 including possible crashes. Fixes bug 21118; bugfix
10340 o Major bugfixes (client, onion service, also in 0.2.9.9):
10341 - Fix a client-side onion service reachability bug, where multiple
10342 socks requests to an onion service (or a single slow request)
10343 could cause us to mistakenly mark some of the service's
10344 introduction points as failed, and we cache that failure so
10345 eventually we run out and can't reach the service. Also resolves a
10346 mysterious "Remote server sent bogus reason code 65021" log
10347 warning. The bug was introduced in ticket 17218, where we tried to
10348 remember the circuit end reason as a uint16_t, which mangled
10349 negative values. Partially fixes bug 21056 and fixes bug 20307;
10350 bugfix on 0.2.8.1-alpha.
10352 o Major bugfixes (DNS):
10353 - Fix a bug that prevented exit nodes from caching DNS records for
10354 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10356 o Minor features (controller):
10357 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10358 shared-random values to the controller. Closes ticket 19925.
10360 o Minor features (entry guards):
10361 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10362 break regression tests.
10363 - Require UseEntryGuards when UseBridges is set, in order to make
10364 sure bridges aren't bypassed. Resolves ticket 20502.
10366 o Minor features (fallback directories):
10367 - Select 200 fallback directories for each release. Closes
10369 - Allow 3 fallback relays per operator, which is safe now that we
10370 are choosing 200 fallback relays. Closes ticket 20912.
10371 - Exclude relays affected by bug 20499 from the fallback list.
10372 Exclude relays from the fallback list if they are running versions
10373 known to be affected by bug 20499, or if in our tests they deliver
10374 a stale consensus (i.e. one that expired more than 24 hours ago).
10375 Closes ticket 20539.
10376 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10378 - Require fallback directories to have the same address and port for
10379 7 days (now that we have enough relays with this stability).
10380 Relays whose OnionOO stability timer is reset on restart by bug
10381 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10382 this issue. Closes ticket 20880; maintains short-term fix
10384 - Require fallbacks to have flags for 90% of the time (weighted
10385 decaying average), rather than 95%. This allows at least 73% of
10386 clients to bootstrap in the first 5 seconds without contacting an
10387 authority. Part of ticket 18828.
10388 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10389 weight for each candidate fallback. Closes ticket 20878.
10390 - Make it easier to change the output sort order of fallbacks.
10391 Closes ticket 20822.
10392 - Display the relay fingerprint when downloading consensuses from
10393 fallbacks. Closes ticket 20908.
10395 o Minor features (geoip, also in 0.2.9.9):
10396 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10399 o Minor features (next-gen onion service directories):
10400 - Remove the "EnableOnionServicesV3" consensus parameter that we
10401 introduced in 0.3.0.1-alpha: relays are now always willing to act
10402 as v3 onion service directories. Resolves ticket 19899.
10404 o Minor features (linting):
10405 - Enhance the changes file linter to warn on Tor versions that are
10406 prefixed with "tor-". Closes ticket 21096.
10408 o Minor features (logging):
10409 - In several places, describe unset ed25519 keys as "<unset>",
10410 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10412 o Minor bugfix (control protocol):
10413 - The reply to a "GETINFO config/names" request via the control
10414 protocol now spells the type "Dependent" correctly. This is a
10415 breaking change in the control protocol. (The field seems to be
10416 ignored by the most common known controllers.) Fixes bug 18146;
10417 bugfix on 0.1.1.4-alpha.
10419 o Minor bugfixes (bug resilience):
10420 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
10421 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
10422 Hans Jerry Illikainen.
10424 o Minor bugfixes (build):
10425 - Replace obsolete Autoconf macros with their modern equivalent and
10426 prevent similar issues in the future. Fixes bug 20990; bugfix
10429 o Minor bugfixes (client, guards):
10430 - Fix bug where Tor would think that there are circuits waiting for
10431 better guards even though those circuits have been freed. Fixes
10432 bug 21142; bugfix on 0.3.0.1-alpha.
10434 o Minor bugfixes (config):
10435 - Don't assert on startup when trying to get the options list and
10436 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
10437 options so of course they aren't ready yet. Fixes bug 21062;
10438 bugfix on 0.2.9.3-alpha.
10440 o Minor bugfixes (controller):
10441 - Make the GETINFO interface for inquiring about entry guards
10442 support the new guards backend. Fixes bug 20823; bugfix
10445 o Minor bugfixes (dead code):
10446 - Remove a redundant check for PidFile changes at runtime in
10447 options_transition_allowed(): this check is already performed
10448 regardless of whether the sandbox is active. Fixes bug 21123;
10449 bugfix on 0.2.5.4-alpha.
10451 o Minor bugfixes (documentation):
10452 - Update the tor manual page to document every option that can not
10453 be changed while tor is running. Fixes bug 21122.
10455 o Minor bugfixes (fallback directories):
10456 - Stop failing when a relay has no uptime data in
10457 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
10458 - Avoid checking fallback candidates' DirPorts if they are down in
10459 OnionOO. When a relay operator has multiple relays, this
10460 prioritizes relays that are up over relays that are down. Fixes
10461 bug 20926; bugfix on 0.2.8.3-alpha.
10462 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
10463 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
10465 o Minor bugfixes (guards, bootstrapping):
10466 - When connecting to a directory guard during bootstrap, do not mark
10467 the guard as successful until we receive a good-looking directory
10468 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
10470 o Minor bugfixes (onion services):
10471 - Fix the config reload pruning of old vs new services so it
10472 actually works when both ephemeral and non-ephemeral services are
10473 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
10474 - Allow the number of introduction points to be as low as 0, rather
10475 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
10477 o Minor bugfixes (IPv6):
10478 - Make IPv6-using clients try harder to find an IPv6 directory
10479 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
10480 - When IPv6 addresses have not been downloaded yet (microdesc
10481 consensus documents don't list relay IPv6 addresses), use hard-
10482 coded addresses for authorities, fallbacks, and configured
10483 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
10484 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
10486 o Minor bugfixes (memory leaks):
10487 - Fix a memory leak when configuring hidden services. Fixes bug
10488 20987; bugfix on 0.3.0.1-alpha.
10490 o Minor bugfixes (portability, also in 0.2.9.9):
10491 - Avoid crashing when Tor is built using headers that contain
10492 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10493 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10495 - Fix Libevent detection on platforms without Libevent 1 headers
10496 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10498 o Minor bugfixes (relay):
10499 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
10500 initializing the keys would reset the DataDirectory to 0700
10501 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
10502 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
10504 o Minor bugfixes (testing):
10505 - Remove undefined behavior from the backtrace generator by removing
10506 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
10508 o Minor bugfixes (unit tests):
10509 - Allow the unit tests to pass even when DNS lookups of bogus
10510 addresses do not fail as expected. Fixes bug 20862 and 20863;
10511 bugfix on unit tests introduced in 0.2.8.1-alpha
10512 through 0.2.9.4-alpha.
10514 o Code simplification and refactoring:
10515 - Refactor code to manipulate global_origin_circuit_list into
10516 separate functions. Closes ticket 20921.
10518 o Documentation (formatting):
10519 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
10520 blocks were incorrectly appearing. Closes ticket 20885.
10522 o Documentation (man page):
10523 - Clarify many options in tor.1 and add some min/max values for
10524 HiddenService options. Closes ticket 21058.
10527 Changes in version 0.2.9.9 - 2017-01-23
10528 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
10529 cause relays and clients to crash, even if they were not built with
10530 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10531 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10532 version should upgrade.
10534 This release also resolves a client-side onion service reachability
10535 bug, and resolves a pair of small portability issues.
10537 o Major bugfixes (security):
10538 - Downgrade the "-ftrapv" option from "always on" to "only on when
10539 --enable-expensive-hardening is provided." This hardening option,
10540 like others, can turn survivable bugs into crashes -- and having
10541 it on by default made a (relatively harmless) integer overflow bug
10542 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10543 bugfix on 0.2.9.1-alpha.
10545 o Major bugfixes (client, onion service):
10546 - Fix a client-side onion service reachability bug, where multiple
10547 socks requests to an onion service (or a single slow request)
10548 could cause us to mistakenly mark some of the service's
10549 introduction points as failed, and we cache that failure so
10550 eventually we run out and can't reach the service. Also resolves a
10551 mysterious "Remote server sent bogus reason code 65021" log
10552 warning. The bug was introduced in ticket 17218, where we tried to
10553 remember the circuit end reason as a uint16_t, which mangled
10554 negative values. Partially fixes bug 21056 and fixes bug 20307;
10555 bugfix on 0.2.8.1-alpha.
10557 o Minor features (geoip):
10558 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10561 o Minor bugfixes (portability):
10562 - Avoid crashing when Tor is built using headers that contain
10563 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10564 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10566 - Fix Libevent detection on platforms without Libevent 1 headers
10567 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10570 Changes in version 0.3.0.1-alpha - 2016-12-19
10571 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
10572 series. It strengthens Tor's link and circuit handshakes by
10573 identifying relays by their Ed25519 keys, improves the algorithm that
10574 clients use to choose and maintain their list of guards, and includes
10575 additional backend support for the next-generation hidden service
10576 design. It also contains numerous other small features and
10577 improvements to security, correctness, and performance.
10579 Below are the changes since 0.2.9.8.
10581 o Major features (guard selection algorithm):
10582 - Tor's guard selection algorithm has been redesigned from the
10583 ground up, to better support unreliable networks and restrictive
10584 sets of entry nodes, and to better resist guard-capture attacks by
10585 hostile local networks. Implements proposal 271; closes
10588 o Major features (next-generation hidden services):
10589 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10590 prop224 aka "Next Generation Hidden Services". Service and clients
10591 don't use this functionality yet. Closes ticket 19043. Based on
10592 initial code by Alec Heifetz.
10593 - Relays now support the HSDir version 3 protocol, so that they can
10594 can store and serve v3 descriptors. This is part of the next-
10595 generation onion service work detailed in proposal 224. Closes
10598 o Major features (protocol, ed25519 identity keys):
10599 - Relays now use Ed25519 to prove their Ed25519 identities and to
10600 one another, and to clients. This algorithm is faster and more
10601 secure than the RSA-based handshake we've been doing until now.
10602 Implements the second big part of proposal 220; Closes
10604 - Clients now support including Ed25519 identity keys in the EXTEND2
10605 cells they generate. By default, this is controlled by a consensus
10606 parameter, currently disabled. You can turn this feature on for
10607 testing by setting ExtendByEd25519ID in your configuration. This
10608 might make your traffic appear different than the traffic
10609 generated by other users, however. Implements part of ticket
10610 15056; part of proposal 220.
10611 - Relays now understand requests to extend to other relays by their
10612 Ed25519 identity keys. When an Ed25519 identity key is included in
10613 an EXTEND2 cell, the relay will only extend the circuit if the
10614 other relay can prove ownership of that identity. Implements part
10615 of ticket 15056; part of proposal 220.
10617 o Major bugfixes (scheduler):
10618 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10619 caused the channel scheduler to behave more or less randomly,
10620 rather than preferring channels with higher-priority circuits.
10621 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10623 o Minor features (controller):
10624 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10625 rather than "unrecognized." Closes ticket 20389; patch from
10628 o Minor features (diagnostic, directory client):
10629 - Warn when we find an unexpected inconsistency in directory
10630 download status objects. Prevents some negative consequences of
10633 o Minor features (directory authority):
10634 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10635 default) to control whether authorities should try to probe relays
10636 by their Ed25519 link keys. This option will go away in a few
10637 releases--unless we encounter major trouble in our ed25519 link
10638 protocol rollout, in which case it will serve as a safety option.
10640 o Minor features (directory cache):
10641 - Relays and bridges will now refuse to serve the consensus they
10642 have if they know it is too old for a client to use. Closes
10645 o Minor features (ed25519 link handshake):
10646 - Advertise support for the ed25519 link handshake using the
10647 subprotocol-versions mechanism, so that clients can tell which
10648 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10650 o Minor features (fingerprinting resistance, authentication):
10651 - Extend the length of RSA keys used for TLS link authentication to
10652 2048 bits. (These weren't used for forward secrecy; for forward
10653 secrecy, we used P256.) Closes ticket 13752.
10655 o Minor features (infrastructure):
10656 - Implement smartlist_add_strdup() function. Replaces the use of
10657 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10659 o Minor bugfixes (client):
10660 - When clients that use bridges start up with a cached consensus on
10661 disk, they were ignoring it and downloading a new one. Now they
10662 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
10664 o Minor bugfixes (configuration):
10665 - Accept non-space whitespace characters after the severity level in
10666 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
10667 - Support "TByte" and "TBytes" units in options given in bytes.
10668 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
10669 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
10671 o Minor bugfixes (consensus weight):
10672 - Add new consensus method that initializes bw weights to 1 instead
10673 of 0. This prevents a zero weight from making it all the way to
10674 the end (happens in small testing networks) and causing an error.
10675 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
10677 o Minor bugfixes (descriptors):
10678 - Correctly recognise downloaded full descriptors as valid, even
10679 when using microdescriptors as circuits. This affects clients with
10680 FetchUselessDescriptors set, and may affect directory authorities.
10681 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
10683 o Minor bugfixes (directory system):
10684 - Download all consensus flavors, descriptors, and authority
10685 certificates when FetchUselessDescriptors is set, regardless of
10686 whether tor is a directory cache or not. Fixes bug 20667; bugfix
10687 on all recent tor versions.
10688 - Bridges and relays now use microdescriptors (like clients do)
10689 rather than old-style router descriptors. Now bridges will blend
10690 in with clients in terms of the circuits they build. Fixes bug
10691 6769; bugfix on 0.2.3.2-alpha.
10693 o Minor bugfixes (ed25519 certificates):
10694 - Correctly interpret ed25519 certificates that would expire some
10695 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
10697 o Minor bugfixes (hidden services):
10698 - Stop ignoring misconfigured hidden services. Instead, refuse to
10699 start tor until the misconfigurations have been corrected. Fixes
10700 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
10703 o Minor bugfixes (memory leak at exit):
10704 - Fix a small harmless memory leak at exit of the previously unused
10705 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
10708 o Minor bugfixes (util):
10709 - When finishing writing a file to disk, if we were about to replace
10710 the file with the temporary file created before and we fail to
10711 replace it, remove the temporary file so it doesn't stay on disk.
10712 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10714 o Minor bugfixes (Windows):
10715 - Check for getpagesize before using it to mmap files. This fixes
10716 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10717 0.1.2.1-alpha. Reported by "ice".
10719 o Code simplification and refactoring:
10720 - Abolish all global guard context in entrynodes.c; replace with new
10721 guard_selection_t structure as preparation for proposal 271.
10722 Closes ticket 19858.
10723 - Introduce rend_service_is_ephemeral() that tells if given onion
10724 service is ephemeral. Replace unclear NULL-checkings for service
10725 directory with this function. Closes ticket 20526.
10726 - Extract magic numbers in circuituse.c into defined variables.
10727 - Refactor circuit_is_available_for_use to remove unnecessary check.
10728 - Refactor circuit_predict_and_launch_new for readability and
10729 testability. Closes ticket 18873.
10730 - Refactor large if statement in purpose_needs_anonymity to use
10731 switch statement instead. Closes part of ticket 20077.
10732 - Refactor the hashing API to return negative values for errors, as
10733 is done as throughout the codebase. Closes ticket 20717.
10734 - Remove data structures that were used to index or_connection
10735 objects by their RSA identity digests. These structures are fully
10736 redundant with the similar structures used in the
10737 channel abstraction.
10738 - Remove duplicate code in the channel_write_*cell() functions.
10739 Closes ticket 13827; patch from Pingl.
10740 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10741 use only purpose_needs_anonymity. Closes part of ticket 20077.
10742 - The code to generate and parse EXTEND and EXTEND2 cells has been
10743 replaced with code automatically generated by the
10747 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10748 20622; bugfix on 0.2.5.1-alpha.
10749 - Change '1' to 'weight_scale' in consensus bw weights calculation
10750 comments, as that is reality. Closes ticket 20273. Patch
10752 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10753 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10755 - Stop the man page from incorrectly stating that HiddenServiceDir
10756 must already exist. Fixes 20486.
10757 - Clarify that when ClientRejectInternalAddresses is enabled (which
10758 is the default), multicast DNS hostnames for machines on the local
10759 network (of the form *.local) are also rejected. Closes
10762 o Removed features:
10763 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10764 limit for relays running on a single IP applies to authority IP
10765 addresses as well as to non-authority IP addresses. Closes
10767 - The UseDirectoryGuards torrc option no longer exists: all users
10768 that use entry guards will also use directory guards. Related to
10769 proposal 271; implements part of ticket 20831.
10772 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10773 from "overcaffeinated".
10774 - Perform the coding style checks when running the tests and fail
10775 when coding style violations are found. Closes ticket 5500.
10776 - Add tests for networkstatus_compute_bw_weights_v10.
10777 - Add unit tests circuit_predict_and_launch_new.
10778 - Extract dummy_origin_circuit_new so it can be used by other
10782 Changes in version 0.2.8.12 - 2016-12-19
10783 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10784 below) where Tor clients could crash when attempting to visit a
10785 hostile hidden service. Clients are recommended to upgrade as packages
10786 become available for their systems.
10788 It also includes an updated list of fallback directories, backported
10791 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10792 backported to 0.2.8 in the future.
10794 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10795 - Fix a bug in parsing that could cause clients to read a single
10796 byte past the end of an allocated region. This bug could be used
10797 to cause hardened clients (built with --enable-expensive-hardening)
10798 to crash if they tried to visit a hostile hidden service. Non-
10799 hardened clients are only affected depending on the details of
10800 their platform's memory allocator. Fixes bug 21018; bugfix on
10801 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10802 2016-12-002 and as CVE-2016-1254.
10804 o Minor features (fallback directory list, backported from 0.2.9.8):
10805 - Replace the 81 remaining fallbacks of the 100 originally
10806 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10807 fallbacks (123 new, 54 existing, 27 removed) generated in December
10808 2016. Resolves ticket 20170.
10810 o Minor features (geoip, backported from 0.2.9.7-rc):
10811 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10815 Changes in version 0.2.9.8 - 2016-12-19
10816 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10818 The Tor 0.2.9 series makes mandatory a number of security features
10819 that were formerly optional. It includes support for a new shared-
10820 randomness protocol that will form the basis for next generation
10821 hidden services, includes a single-hop hidden service mode for
10822 optimizing .onion services that don't actually want to be hidden,
10823 tries harder not to overload the directory authorities with excessive
10824 downloads, and supports a better protocol versioning scheme for
10825 improved compatibility with other implementations of the Tor protocol.
10827 And of course, there are numerous other bugfixes and improvements.
10829 This release also includes a fix for a medium-severity issue (bug
10830 21018 below) where Tor clients could crash when attempting to visit a
10831 hostile hidden service. Clients are recommended to upgrade as packages
10832 become available for their systems.
10834 Below are the changes since 0.2.9.7-rc. For a list of all changes
10835 since 0.2.8, see the ReleaseNotes file.
10837 o Major bugfixes (parsing, security):
10838 - Fix a bug in parsing that could cause clients to read a single
10839 byte past the end of an allocated region. This bug could be used
10840 to cause hardened clients (built with --enable-expensive-hardening)
10841 to crash if they tried to visit a hostile hidden service. Non-
10842 hardened clients are only affected depending on the details of
10843 their platform's memory allocator. Fixes bug 21018; bugfix on
10844 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10845 2016-12-002 and as CVE-2016-1254.
10847 o Minor features (fallback directory list):
10848 - Replace the 81 remaining fallbacks of the 100 originally
10849 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10850 fallbacks (123 new, 54 existing, 27 removed) generated in December
10851 2016. Resolves ticket 20170.
10854 Changes in version 0.2.9.7-rc - 2016-12-12
10855 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10856 including a few that had prevented tests from passing on
10859 o Minor features (geoip):
10860 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10863 o Minor bugfix (build):
10864 - The current Git revision when building from a local repository is
10865 now detected correctly when using git worktrees. Fixes bug 20492;
10866 bugfix on 0.2.3.9-alpha.
10868 o Minor bugfixes (directory authority):
10869 - When computing old Tor protocol line version in protover, we were
10870 looking at 0.2.7.5 twice instead of a specific case for
10871 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10873 o Minor bugfixes (download scheduling):
10874 - Resolve a "bug" warning when considering a download schedule whose
10875 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10877 o Minor bugfixes (logging):
10878 - Downgrade a harmless log message about the
10879 pending_entry_connections list from "warn" to "info". Mitigates
10882 o Minor bugfixes (memory leak):
10883 - Fix a small memory leak when receiving AF_UNIX connections on a
10884 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10885 - When moving a signed descriptor object from a source to an
10886 existing destination, free the allocated memory inside that
10887 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10889 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10890 - Fix a memory leak and use-after-free error when removing entries
10891 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10892 0.2.5.5-alpha. Patch from "cypherpunks".
10894 o Minor bugfixes (portability):
10895 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10896 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10898 o Minor bugfixes (unit tests):
10899 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10900 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10901 - Fix tolerances in unit tests for monotonic time comparisons
10902 between nanoseconds and microseconds. Previously, we accepted a 10
10903 us difference only, which is not realistic on every platform's
10904 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10905 - Remove a double-free in the single onion service unit test. Stop
10906 ignoring a return value. Make future changes less error-prone.
10907 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10910 Changes in version 0.2.8.11 - 2016-12-08
10911 Tor 0.2.8.11 backports fixes for additional portability issues that
10912 could prevent Tor from building correctly on OSX Sierra, or with
10913 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10916 o Minor bugfixes (portability):
10917 - Avoid compilation errors when building on OSX Sierra. Sierra began
10918 to support the getentropy() and clock_gettime() APIs, but created
10919 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10920 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
10921 monotonic time interfaces. Fixes bug 20865. Bugfix
10924 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10925 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
10926 architectures. Closes ticket 20588.
10929 Changes in version 0.2.8.10 - 2016-12-02
10930 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
10931 unusable after they left standby mode. It also backports fixes for
10932 a few portability issues and a small but problematic memory leak.
10934 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
10935 - When Tor leaves standby because of a new application request, open
10936 circuits as needed to serve that request. Previously, we would
10937 potentially wait a very long time. Fixes part of bug 19969; bugfix
10940 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
10941 - Clients now respond to new application stream requests immediately
10942 when they arrive, rather than waiting up to one second before
10943 starting to handle them. Fixes part of bug 19969; bugfix
10946 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
10947 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10948 successfully targeting earlier versions of OSX. Resolves
10951 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
10952 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
10953 20551; bugfix on 0.2.1.1-alpha.
10955 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
10956 - Work around a memory leak in OpenSSL 1.1 when encoding public
10957 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
10959 o Minor features (geoip):
10960 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
10963 Changes in version 0.2.9.6-rc - 2016-12-02
10964 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
10965 version. We hope that it will be ready to become stable soon, and we
10966 encourage everyone to test this release. If no showstopper bugs are
10967 found here, the next 0.2.9 release will be stable.
10969 o Major bugfixes (relay, resolver, logging):
10970 - For relays that don't know their own address, avoid attempting a
10971 local hostname resolve for each descriptor we download. This
10972 will cut down on the number of "Success: chose address 'x.x.x.x'"
10973 log lines, and also avoid confusing clock jumps if the resolver
10974 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
10976 o Minor bugfixes (client, fascistfirewall):
10977 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
10978 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
10980 o Minor bugfixes (hidden services):
10981 - Stop ignoring the anonymity status of saved keys for hidden
10982 services and single onion services when first starting tor.
10983 Instead, refuse to start tor if any hidden service key has been
10984 used in a different hidden service anonymity mode. Fixes bug
10985 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
10987 o Minor bugfixes (portability):
10988 - Work around a bug in the OSX 10.12 SDK that would prevent us from
10989 successfully targeting earlier versions of OSX. Resolves
10991 - Run correctly when built on Windows build environments that
10992 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
10994 o Minor bugfixes (single onion services, Tor2web):
10995 - Stop complaining about long-term one-hop circuits deliberately
10996 created by single onion services and Tor2web. These log messages
10997 are intended to diagnose issue 8387, which relates to circuits
10998 hanging around forever for no reason. Fixes bug 20613; bugfix on
10999 0.2.9.1-alpha. Reported by "pastly".
11001 o Minor bugfixes (unit tests):
11002 - Stop spurious failures in the local interface address discovery
11003 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
11007 - Correct the minimum bandwidth value in torrc.sample, and queue a
11008 corresponding change for torrc.minimal. Closes ticket 20085.
11011 Changes in version 0.2.9.5-alpha - 2016-11-08
11012 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
11013 version. We believe one or two probably remain, and we encourage
11014 everyone to test this release.
11016 o Major bugfixes (client performance):
11017 - Clients now respond to new application stream requests immediately
11018 when they arrive, rather than waiting up to one second before
11019 starting to handle them. Fixes part of bug 19969; bugfix
11022 o Major bugfixes (client reliability):
11023 - When Tor leaves standby because of a new application request, open
11024 circuits as needed to serve that request. Previously, we would
11025 potentially wait a very long time. Fixes part of bug 19969; bugfix
11028 o Major bugfixes (download scheduling):
11029 - When using an exponential backoff schedule, do not give up on
11030 downloading just because we have failed a bunch of times. Since
11031 each delay is longer than the last, retrying indefinitely won't
11032 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
11033 - If a consensus expires while we are waiting for certificates to
11034 download, stop waiting for certificates.
11035 - If we stop waiting for certificates less than a minute after we
11036 started downloading them, do not consider the certificate download
11037 failure a separate failure. Fixes bug 20533; bugfix
11039 - Remove the maximum delay on exponential-backoff scheduling. Since
11040 we now allow an infinite number of failures (see ticket 20536), we
11041 must now allow the time to grow longer on each failure. Fixes part
11042 of bug 20534; bugfix on 0.2.9.1-alpha.
11043 - Make our initial download delays closer to those from 0.2.8. Fixes
11044 another part of bug 20534; bugfix on 0.2.9.1-alpha.
11045 - When determining when to download a directory object, handle times
11046 after 2038 if the operating system supports them. (Someday this
11047 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
11048 - When using exponential backoff in test networks, use a lower
11049 exponent, so the delays do not vary as much. This helps test
11050 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
11052 o Minor features (geoip):
11053 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
11056 o Minor bugfixes (client directory scheduling):
11057 - Treat "relay too busy to answer request" as a failed request and a
11058 reason to back off on our retry frequency. This is safe now that
11059 exponential backoffs retry indefinitely, and avoids a bug where we
11060 would reset our download schedule erroneously. Fixes bug 20593;
11061 bugfix on 0.2.9.1-alpha.
11063 o Minor bugfixes (client, logging):
11064 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
11065 assume all nodes support EXTEND2. Use ntor whenever a key is
11066 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
11067 - On DNSPort, stop logging a BUG warning on a failed hostname
11068 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
11070 o Minor bugfixes (hidden services):
11071 - When configuring hidden services, check every hidden service
11072 directory's permissions. Previously, we only checked the last
11073 hidden service. Fixes bug 20529; bugfix the work to fix 13942
11076 o Minor bugfixes (portability):
11077 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
11078 architectures. Closes ticket 20588.
11079 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
11080 removed the ECDH ciphers which caused the tests to fail on
11081 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
11082 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
11083 20551; bugfix on 0.2.1.1-alpha.
11085 o Minor bugfixes (relay bootstrap):
11086 - Ensure relays don't make multiple connections during bootstrap.
11087 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
11089 o Minor bugfixes (relay):
11090 - Work around a memory leak in OpenSSL 1.1 when encoding public
11091 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
11092 - Avoid a small memory leak when informing worker threads about
11093 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
11094 - Do not try to parallelize workers more than 16x without the user
11095 explicitly configuring us to do so, even if we do detect more than
11096 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
11098 o Minor bugfixes (single onion services):
11099 - Start correctly when creating a single onion service in a
11100 directory that did not previously exist. Fixes bug 20484; bugfix
11103 o Minor bugfixes (testing):
11104 - Avoid a unit test failure on systems with over 16 detectable CPU
11105 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
11108 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
11109 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
11110 - Module-level documentation for several more modules. Closes
11111 tickets 19287 and 19290.
11114 Changes in version 0.2.8.9 - 2016-10-17
11115 Tor 0.2.8.9 backports a fix for a security hole in previous versions
11116 of Tor that would allow a remote attacker to crash a Tor client,
11117 hidden service, relay, or authority. All Tor users should upgrade to
11118 this version, or to 0.2.9.4-alpha. Patches will be released for older
11121 o Major features (security fixes, also in 0.2.9.4-alpha):
11122 - Prevent a class of security bugs caused by treating the contents
11123 of a buffer chunk as if they were a NUL-terminated string. At
11124 least one such bug seems to be present in all currently used
11125 versions of Tor, and would allow an attacker to remotely crash
11126 most Tor instances, especially those compiled with extra compiler
11127 hardening. With this defense in place, such bugs can't crash Tor,
11128 though we should still fix them as they occur. Closes ticket
11129 20384 (TROVE-2016-10-001).
11131 o Minor features (geoip):
11132 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11136 Changes in version 0.2.9.4-alpha - 2016-10-17
11137 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
11138 that would allow a remote attacker to crash a Tor client, hidden
11139 service, relay, or authority. All Tor users should upgrade to this
11140 version, or to 0.2.8.9. Patches will be released for older versions
11143 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
11144 previous versions of Tor, including the implementation of a feature to
11145 future- proof the Tor ecosystem against protocol changes, some bug
11146 fixes necessary for Tor Browser to use unix domain sockets correctly,
11147 and several portability improvements. We anticipate that this will be
11148 the last alpha in the Tor 0.2.9 series, and that the next release will
11149 be a release candidate.
11151 o Major features (security fixes):
11152 - Prevent a class of security bugs caused by treating the contents
11153 of a buffer chunk as if they were a NUL-terminated string. At
11154 least one such bug seems to be present in all currently used
11155 versions of Tor, and would allow an attacker to remotely crash
11156 most Tor instances, especially those compiled with extra compiler
11157 hardening. With this defense in place, such bugs can't crash Tor,
11158 though we should still fix them as they occur. Closes ticket
11159 20384 (TROVE-2016-10-001).
11161 o Major features (subprotocol versions):
11162 - Tor directory authorities now vote on a set of recommended
11163 subprotocol versions, and on a set of required subprotocol
11164 versions. Clients and relays that lack support for a _required_
11165 subprotocol version will not start; those that lack support for a
11166 _recommended_ subprotocol version will warn the user to upgrade.
11167 Closes ticket 19958; implements part of proposal 264.
11168 - Tor now uses "subprotocol versions" to indicate compatibility.
11169 Previously, versions of Tor looked at the declared Tor version of
11170 a relay to tell whether they could use a given feature. Now, they
11171 should be able to rely on its declared subprotocol versions. This
11172 change allows compatible implementations of the Tor protocol(s) to
11173 exist without pretending to be 100% bug-compatible with particular
11174 releases of Tor itself. Closes ticket 19958; implements part of
11177 o Minor feature (fallback directories):
11178 - Remove broken fallbacks from the hard-coded fallback directory
11179 list. Closes ticket 20190; patch by teor.
11181 o Minor features (client, directory):
11182 - Since authorities now omit all routers that lack the Running and
11183 Valid flags, we assume that any relay listed in the consensus must
11184 have those flags. Closes ticket 20001; implements part of
11187 o Minor features (compilation, portability):
11188 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
11191 o Minor features (development tools, etags):
11192 - Teach the "make tags" Makefile target how to correctly find
11193 "MOCK_IMPL" function definitions. Patch from nherring; closes
11196 o Minor features (geoip):
11197 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11200 o Minor features (unix domain sockets):
11201 - When configuring a unix domain socket for a SocksPort,
11202 ControlPort, or Hidden service, you can now wrap the address in
11203 quotes, using C-style escapes inside the quotes. This allows unix
11204 domain socket paths to contain spaces.
11206 o Minor features (virtual addresses):
11207 - Increase the maximum number of bits for the IPv6 virtual network
11208 prefix from 16 to 104. In this way, the condition for address
11209 allocation is less restrictive. Closes ticket 20151; feature
11212 o Minor bugfixes (address discovery):
11213 - Stop reordering IP addresses returned by the OS. This makes it
11214 more likely that Tor will guess the same relay IP address every
11215 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
11216 Reported by René Mayrhofer, patch by "cypherpunks".
11218 o Minor bugfixes (client, unix domain sockets):
11219 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
11220 the client address is meaningless. Fixes bug 20261; bugfix
11223 o Minor bugfixes (compilation, OpenBSD):
11224 - Detect Libevent2 functions correctly on systems that provide
11225 libevent2, but where libevent1 is linked with -levent. Fixes bug
11226 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
11228 o Minor bugfixes (configuration):
11229 - When parsing quoted configuration values from the torrc file,
11230 handle windows line endings correctly. Fixes bug 19167; bugfix on
11231 0.2.0.16-alpha. Patch from "Pingl".
11233 o Minor bugfixes (getpass):
11234 - Defensively fix a non-triggerable heap corruption at do_getpass()
11235 to protect ourselves from mistakes in the future. Fixes bug
11236 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
11239 o Minor bugfixes (hidden service):
11240 - Allow hidden services to run on IPv6 addresses even when the
11241 IPv6Exit option is not set. Fixes bug 18357; bugfix
11245 - Add module-level internal documentation for 36 C files that
11246 previously didn't have a high-level overview. Closes ticket #20385.
11248 o Required libraries:
11249 - When building with OpenSSL, Tor now requires version 1.0.1 or
11250 later. OpenSSL 1.0.0 and earlier are no longer supported by the
11251 OpenSSL team, and should not be used. Closes ticket 20303.
11254 Changes in version 0.2.9.3-alpha - 2016-09-23
11255 Tor 0.2.9.3-alpha adds improved support for entities that want to make
11256 high-performance services available through the Tor .onion mechanism
11257 without themselves receiving anonymity as they host those services. It
11258 also tries harder to ensure that all steps on a circuit are using the
11259 strongest crypto possible, strengthens some TLS properties, and
11260 resolves several bugs -- including a pair of crash bugs from the 0.2.8
11261 series. Anybody running an earlier version of 0.2.9.x should upgrade.
11263 o Major bugfixes (crash, also in 0.2.8.8):
11264 - Fix a complicated crash bug that could affect Tor clients
11265 configured to use bridges when replacing a networkstatus consensus
11266 in which one of their bridges was mentioned. OpenBSD users saw
11267 more crashes here, but all platforms were potentially affected.
11268 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11270 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
11271 - Fix a timing-dependent assertion failure that could occur when we
11272 tried to flush from a circuit after having freed its cells because
11273 of an out-of-memory condition. Fixes bug 20203; bugfix on
11274 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11277 o Major features (circuit building, security):
11278 - Authorities, relays and clients now require ntor keys in all
11279 descriptors, for all hops (except for rare hidden service protocol
11280 cases), for all circuits, and for all other roles. Part of
11282 - Tor authorities, relays, and clients only use ntor, except for
11283 rare cases in the hidden service protocol. Part of ticket 19163.
11285 o Major features (single-hop "hidden" services):
11286 - Add experimental HiddenServiceSingleHopMode and
11287 HiddenServiceNonAnonymousMode options. When both are set to 1,
11288 every hidden service on a Tor instance becomes a non-anonymous
11289 Single Onion Service. Single Onions make one-hop (direct)
11290 connections to their introduction and renzedvous points. One-hop
11291 circuits make Single Onion servers easily locatable, but clients
11292 remain location-anonymous. This is compatible with the existing
11293 hidden service implementation, and works on the current tor
11294 network without any changes to older relays or clients. Implements
11295 proposal 260, completes ticket 17178. Patch by teor and asn.
11297 o Major features (resource management):
11298 - Tor can now notice it is about to run out of sockets, and
11299 preemptively close connections of lower priority. (This feature is
11300 off by default for now, since the current prioritizing method is
11301 yet not mature enough. You can enable it by setting
11302 "DisableOOSCheck 0", but watch out: it might close some sockets
11303 you would rather have it keep.) Closes ticket 18640.
11305 o Major bugfixes (circuit building):
11306 - Hidden service client-to-intro-point and service-to-rendezvous-
11307 point circuits use the TAP key supplied by the protocol, to avoid
11308 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
11310 o Major bugfixes (compilation, OpenBSD):
11311 - Fix a Libevent-detection bug in our autoconf script that would
11312 prevent Tor from linking successfully on OpenBSD. Patch from
11313 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
11315 o Major bugfixes (hidden services):
11316 - Clients now require hidden services to include the TAP keys for
11317 their intro points in the hidden service descriptor. This prevents
11318 an inadvertent upgrade to ntor, which a malicious hidden service
11319 could use to distinguish clients by consensus version. Fixes bug
11320 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
11322 o Minor features (security, TLS):
11323 - Servers no longer support clients that without AES ciphersuites.
11324 (3DES is no longer considered an acceptable cipher.) We believe
11325 that no such Tor clients currently exist, since Tor has required
11326 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
11328 o Minor feature (fallback directories):
11329 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11330 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11331 2016. Closes ticket 20190; patch by teor.
11333 o Minor features (geoip, also in 0.2.8.8):
11334 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11337 o Minor feature (port flags):
11338 - Add new flags to the *Port options to finer control over which
11339 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
11340 and the synthetic flag OnionTrafficOnly, which is equivalent to
11341 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
11342 18693; patch by "teor".
11344 o Minor features (directory authority):
11345 - After voting, if the authorities decide that a relay is not
11346 "Valid", they no longer include it in the consensus at all. Closes
11347 ticket 20002; implements part of proposal 272.
11349 o Minor features (testing):
11350 - Disable memory protections on OpenBSD when performing our unit
11351 tests for memwipe(). The test deliberately invokes undefined
11352 behavior, and the OpenBSD protections interfere with this. Patch
11353 from "rubiate". Closes ticket 20066.
11355 o Minor features (testing, ipv6):
11356 - Add the single-onion and single-onion-ipv6 chutney targets to
11357 "make test-network-all". This requires a recent chutney version
11358 with the single onion network flavours (git c72a652 or later).
11359 Closes ticket 20072; patch by teor.
11360 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
11361 tests. Remove bridges+hs, as it's somewhat redundant. This
11362 requires a recent chutney version that supports IPv6 clients,
11363 relays, and authorities. Closes ticket 20069; patch by teor.
11365 o Minor features (Tor2web):
11366 - Make Tor2web clients respect ReachableAddresses. This feature was
11367 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
11368 0.2.8.7. Implements feature 20034. Patch by teor.
11370 o Minor features (unit tests):
11371 - We've done significant work to make the unit tests run faster.
11372 - Our link-handshake unit tests now check that when invalid
11373 handshakes fail, they fail with the error messages we expected.
11374 - Our unit testing code that captures log messages no longer
11375 prevents them from being written out if the user asked for them
11376 (by passing --debug or --info or or --notice --warn to the "test"
11377 binary). This change prevents us from missing unexpected log
11378 messages simply because we were looking for others. Related to
11380 - The unit tests now log all warning messages with the "BUG" flag.
11381 Previously, they only logged errors by default. This change will
11382 help us make our testing code more correct, and make sure that we
11383 only hit this code when we mean to. In the meantime, however,
11384 there will be more warnings in the unit test logs than before.
11385 This is preparatory work for ticket 19999.
11386 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
11387 assertion as a test failure.
11389 o Minor bug fixes (circuits):
11390 - Use the CircuitBuildTimeout option whenever
11391 LearnCircuitBuildTimeout is disabled. Previously, we would respect
11392 the option when a user disabled it, but not when it was disabled
11393 because some other option was set. Fixes bug 20073; bugfix on
11394 0.2.4.12-alpha. Patch by teor.
11396 o Minor bugfixes (allocation):
11397 - Change how we allocate memory for large chunks on buffers, to
11398 avoid a (currently impossible) integer overflow, and to waste less
11399 space when allocating unusually large chunks. Fixes bug 20081;
11400 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
11401 - Always include orconfig.h before including any other C headers.
11402 Sometimes, it includes macros that affect the behavior of the
11403 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
11404 first version to use AC_USE_SYSTEM_EXTENSIONS).
11405 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
11406 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
11407 Patch from Gisle Vanem.
11408 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
11409 They apparently require a set of annotations that we aren't
11410 currently using, and they create false positives in our pthreads
11411 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
11413 o Minor bugfixes (directory authority):
11414 - Die with a more useful error when the operator forgets to place
11415 the authority_signing_key file into the keys directory. This
11416 avoids an uninformative assert & traceback about having an invalid
11417 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
11418 - When allowing private addresses, mark Exits that only exit to
11419 private locations as such. Fixes bug 20064; bugfix
11422 o Minor bugfixes (documentation):
11423 - Document the default PathsNeededToBuildCircuits value that's used
11424 by clients when the directory authorities don't set
11425 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
11426 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
11427 - Fix manual for the User option: it takes a username, not a UID.
11428 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
11431 o Minor bugfixes (hidden services):
11432 - Stop logging intro point details to the client log on certain
11433 error conditions. Fixed as part of bug 20012; bugfix on
11434 0.2.4.8-alpha. Patch by teor.
11436 o Minor bugfixes (IPv6, testing):
11437 - Check for IPv6 correctly on Linux when running test networks.
11438 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
11440 o Minor bugfixes (Linux seccomp2 sandbox):
11441 - Add permission to run the sched_yield() and sigaltstack() system
11442 calls, in order to support versions of Tor compiled with asan or
11443 ubsan code that use these calls. Now "sandbox 1" and
11444 "--enable-expensive-hardening" should be compatible on more
11445 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
11447 o Minor bugfixes (logging):
11448 - When logging a message from the BUG() macro, be explicit about
11449 what we were asserting. Previously we were confusing what we were
11450 asserting with what the bug was. Fixes bug 20093; bugfix
11452 - When we are unable to remove the bw_accounting file, do not warn
11453 if the reason we couldn't remove it was that it didn't exist.
11454 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
11456 o Minor bugfixes (option parsing):
11457 - Count unix sockets when counting client listeners (SOCKS, Trans,
11458 NATD, and DNS). This has no user-visible behaviour changes: these
11459 options are set once, and never read. Required for correct
11460 behaviour in ticket 17178. Fixes bug 19677; bugfix on
11461 0.2.6.3-alpha. Patch by teor.
11463 o Minor bugfixes (options):
11464 - Check the consistency of UseEntryGuards and EntryNodes more
11465 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
11467 - Stop changing the configured value of UseEntryGuards on
11468 authorities and Tor2web clients. Fixes bug 20074; bugfix on
11469 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
11472 o Minor bugfixes (Tor2web):
11473 - Prevent Tor2web clients running hidden services, these services
11474 are not anonymous due to the one-hop client paths. Fixes bug
11475 19678. Patch by teor.
11477 o Minor bugfixes (unit tests):
11478 - Fix a shared-random unit test that was failing on big endian
11479 architectures due to internal representation of a integer copied
11480 to a buffer. The test is changed to take a full 32 bytes of data
11481 and use the output of a python script that make the COMMIT and
11482 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
11484 - The tor_tls_server_info_callback unit test no longer crashes when
11485 debug-level logging is turned on. Fixes bug 20041; bugfix
11489 Changes in version 0.2.8.8 - 2016-09-23
11490 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
11491 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
11492 who select public relays as their bridges.
11494 o Major bugfixes (crash):
11495 - Fix a complicated crash bug that could affect Tor clients
11496 configured to use bridges when replacing a networkstatus consensus
11497 in which one of their bridges was mentioned. OpenBSD users saw
11498 more crashes here, but all platforms were potentially affected.
11499 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11501 o Major bugfixes (relay, OOM handler):
11502 - Fix a timing-dependent assertion failure that could occur when we
11503 tried to flush from a circuit after having freed its cells because
11504 of an out-of-memory condition. Fixes bug 20203; bugfix on
11505 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11508 o Minor feature (fallback directories):
11509 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11510 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11511 2016. Closes ticket 20190; patch by teor.
11513 o Minor features (geoip):
11514 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11518 Changes in version 0.2.9.2-alpha - 2016-08-24
11519 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
11520 several new features and bugfixes. It also includes an important
11521 authority update and an important bugfix from 0.2.8.7. Everyone who
11522 sets the ReachableAddresses option, and all bridges, are strongly
11523 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
11525 o Directory authority changes (also in 0.2.8.7):
11526 - The "Tonga" bridge authority has been retired; the new bridge
11527 authority is "Bifroest". Closes tickets 19728 and 19690.
11529 o Major bugfixes (client, security, also in 0.2.8.7):
11530 - Only use the ReachableAddresses option to restrict the first hop
11531 in a path. In earlier versions of 0.2.8.x, it would apply to
11532 every hop in the path, with a possible degradation in anonymity
11533 for anyone using an uncommon ReachableAddress setting. Fixes bug
11534 19973; bugfix on 0.2.8.2-alpha.
11536 o Major features (user interface):
11537 - Tor now supports the ability to declare options deprecated, so
11538 that we can recommend that people stop using them. Previously,
11539 this was done in an ad-hoc way. Closes ticket 19820.
11541 o Major bugfixes (directory downloads):
11542 - Avoid resetting download status for consensuses hourly, since we
11543 already have another, smarter retry mechanism. Fixes bug 8625;
11544 bugfix on 0.2.0.9-alpha.
11546 o Minor features (config):
11547 - Warn users when descriptor and port addresses are inconsistent.
11548 Mitigates bug 13953; patch by teor.
11550 o Minor features (geoip):
11551 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11554 o Minor features (user interface):
11555 - There is a new --list-deprecated-options command-line option to
11556 list all of the deprecated options. Implemented as part of
11559 o Minor bugfixes (code style):
11560 - Fix an integer signedness conversion issue in the case conversion
11561 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
11563 o Minor bugfixes (compilation):
11564 - Build correctly on versions of libevent2 without support for
11565 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
11567 - Fix a compilation warning on GCC versions before 4.6. Our
11568 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
11569 when it is also required as an argument to the compiler pragma.
11570 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
11572 o Minor bugfixes (compilation, also in 0.2.8.7):
11573 - Remove an inappropriate "inline" in tortls.c that was causing
11574 warnings on older versions of GCC. Fixes bug 19903; bugfix
11577 o Minor bugfixes (fallback directories, also in 0.2.8.7):
11578 - Avoid logging a NULL string pointer when loading fallback
11579 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11580 and 0.2.8.1-alpha. Report and patch by "rubiate".
11582 o Minor bugfixes (logging):
11583 - Log a more accurate message when we fail to dump a microdescriptor.
11584 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
11586 o Minor bugfixes (memory leak):
11587 - Fix a series of slow memory leaks related to parsing torrc files
11588 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
11590 o Deprecated features:
11591 - A number of DNS-cache-related sub-options for client ports are now
11592 deprecated for security reasons, and may be removed in a future
11593 version of Tor. (We believe that client-side DNS caching is a bad
11594 idea for anonymity, and you should not turn it on.) The options
11595 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11596 UseIPv4Cache, and UseIPv6Cache.
11597 - A number of options are deprecated for security reasons, and may
11598 be removed in a future version of Tor. The options are:
11599 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11600 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11601 CloseHSClientCircuitsImmediatelyOnTimeout,
11602 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11603 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11604 UseNTorHandshake, and WarnUnsafeSocks.
11605 - The *ListenAddress options are now deprecated as unnecessary: the
11606 corresponding *Port options should be used instead. These options
11607 may someday be removed. The affected options are:
11608 ControlListenAddress, DNSListenAddress, DirListenAddress,
11609 NATDListenAddress, ORListenAddress, SocksListenAddress,
11610 and TransListenAddress.
11613 - Correct the IPv6 syntax in our documentation for the
11614 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
11617 - We no longer include the (dead, deprecated) bufferevent code in
11618 Tor. Closes ticket 19450. Based on a patch from U+039b.
11621 Changes in version 0.2.8.7 - 2016-08-24
11622 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
11623 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
11624 who sets the ReachableAddresses option, and all bridges, are strongly
11625 encouraged to upgrade.
11627 o Directory authority changes:
11628 - The "Tonga" bridge authority has been retired; the new bridge
11629 authority is "Bifroest". Closes tickets 19728 and 19690.
11631 o Major bugfixes (client, security):
11632 - Only use the ReachableAddresses option to restrict the first hop
11633 in a path. In earlier versions of 0.2.8.x, it would apply to
11634 every hop in the path, with a possible degradation in anonymity
11635 for anyone using an uncommon ReachableAddress setting. Fixes bug
11636 19973; bugfix on 0.2.8.2-alpha.
11638 o Minor features (geoip):
11639 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11642 o Minor bugfixes (compilation):
11643 - Remove an inappropriate "inline" in tortls.c that was causing
11644 warnings on older versions of GCC. Fixes bug 19903; bugfix
11647 o Minor bugfixes (fallback directories):
11648 - Avoid logging a NULL string pointer when loading fallback
11649 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11650 and 0.2.8.1-alpha. Report and patch by "rubiate".
11653 Changes in version 0.2.9.1-alpha - 2016-08-08
11654 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
11655 series. It improves our support for hardened builds and compiler
11656 warnings, deploys some critical infrastructure for improvements to
11657 hidden services, includes a new timing backend that we hope to use for
11658 better support for traffic padding, makes it easier for programmers to
11659 log unexpected events, and contains other small improvements to
11660 security, correctness, and performance.
11662 Below are the changes since 0.2.8.6.
11664 o New system requirements:
11665 - Tor now requires Libevent version 2.0.10-stable or later. Older
11666 versions of Libevent have less efficient backends for several
11667 platforms, and lack the DNS code that we use for our server-side
11668 DNS support. This implements ticket 19554.
11669 - Tor now requires zlib version 1.2 or later, for security,
11670 efficiency, and (eventually) gzip support. (Back when we started,
11671 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11672 released in 2003. We recommend the latest version.)
11674 o Major features (build, hardening):
11675 - Tor now builds with -ftrapv by default on compilers that support
11676 it. This option detects signed integer overflow (which C forbids),
11677 and turns it into a hard-failure. We do not apply this option to
11678 code that needs to run in constant time to avoid side-channels;
11679 instead, we use -fwrapv in that code. Closes ticket 17983.
11680 - When --enable-expensive-hardening is selected, stop applying the
11681 clang/gcc sanitizers to code that needs to run in constant time.
11682 Although we are aware of no introduced side-channels, we are not
11683 able to prove that there are none. Related to ticket 17983.
11685 o Major features (compilation):
11686 - Our big list of extra GCC warnings is now enabled by default when
11687 building with GCC (or with anything like Clang that claims to be
11688 GCC-compatible). To make all warnings into fatal compilation
11689 errors, pass --enable-fatal-warnings to configure. Closes
11691 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11692 turn on C and POSIX extensions. (Previously, we attempted to do
11693 this on an ad hoc basis.) Closes ticket 19139.
11695 o Major features (directory authorities, hidden services):
11696 - Directory authorities can now perform the shared randomness
11697 protocol specified by proposal 250. Using this protocol, directory
11698 authorities generate a global fresh random value every day. In the
11699 future, this value will be used by hidden services to select
11700 HSDirs. This release implements the directory authority feature;
11701 the hidden service side will be implemented in the future as part
11702 of proposal 224. Resolves ticket 16943; implements proposal 250.
11704 o Major features (downloading, random exponential backoff):
11705 - When we fail to download an object from a directory service, wait
11706 for an (exponentially increasing) randomized amount of time before
11707 retrying, rather than a fixed interval as we did before. This
11708 prevents a group of Tor instances from becoming too synchronized,
11709 or a single Tor instance from becoming too predictable, in its
11710 download schedule. Closes ticket 15942.
11712 o Major bugfixes (exit policies):
11713 - Avoid disclosing exit outbound bind addresses, configured port
11714 bind addresses, and local interface addresses in relay descriptors
11715 by default under ExitPolicyRejectPrivate. Instead, only reject
11716 these (otherwise unlisted) addresses if
11717 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11718 0.2.7.2-alpha. Patch by teor.
11720 o Major bugfixes (hidden service client):
11721 - Allow Tor clients with appropriate controllers to work with
11722 FetchHidServDescriptors set to 0. Previously, this option also
11723 disabled descriptor cache lookup, thus breaking hidden services
11724 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11726 o Minor features (build, hardening):
11727 - Detect and work around a libclang_rt problem that would prevent
11728 clang from finding __mulodi4() on some 32-bit platforms, and thus
11729 keep -ftrapv from linking on those systems. Closes ticket 19079.
11730 - When building on a system without runtime support for the runtime
11731 hardening options, try to log a useful warning at configuration
11732 time, rather than an incomprehensible warning at link time. If
11733 expensive hardening was requested, this warning becomes an error.
11734 Closes ticket 18895.
11736 o Minor features (code safety):
11737 - In our integer-parsing functions, ensure that maxiumum value we
11738 give is no smaller than the minimum value. Closes ticket 19063;
11741 o Minor features (controller):
11742 - Implement new GETINFO queries for all downloads that use
11743 download_status_t to schedule retries. This allows controllers to
11744 examine the schedule for pending downloads. Closes ticket 19323.
11745 - Allow controllers to configure basic client authorization on
11746 hidden services when they create them with the ADD_ONION control
11747 command. Implements ticket 15588. Patch by "special".
11748 - Fire a STATUS_SERVER controller event whenever the hibernation
11749 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11751 o Minor features (directory authority):
11752 - Directory authorities now only give the Guard flag to a relay if
11753 they are also giving it the Stable flag. This change allows us to
11754 simplify path selection for clients. It should have minimal effect
11755 in practice, since >99% of Guards already have the Stable flag.
11756 Implements ticket 18624.
11757 - Directory authorities now write their v3-status-votes file out to
11758 disk earlier in the consensus process, so we have a record of the
11759 votes even if we abort the consensus process. Resolves
11762 o Minor features (hidden service):
11763 - Stop being so strict about the payload length of "rendezvous1"
11764 cells. We used to be locked in to the "TAP" handshake length, and
11765 now we can handle better handshakes like "ntor". Resolves
11768 o Minor features (infrastructure, time):
11769 - Tor now uses the operating system's monotonic timers (where
11770 available) for internal fine-grained timing. Previously we would
11771 look at the system clock, and then attempt to compensate for the
11772 clock running backwards. Closes ticket 18908.
11773 - Tor now includes an improved timer backend, so that we can
11774 efficiently support tens or hundreds of thousands of concurrent
11775 timers, as will be needed for some of our planned anti-traffic-
11776 analysis work. This code is based on William Ahern's "timeout.c"
11777 project, which implements a "tickless hierarchical timing wheel".
11778 Closes ticket 18365.
11780 o Minor features (logging):
11781 - Provide a more useful warning message when configured with an
11782 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11783 - When dumping unparseable router descriptors, optionally store them
11784 in separate files, named by digest, up to a configurable size
11785 limit. You can change the size limit by setting the
11786 MaxUnparseableDescSizeToLog option, and disable this feature by
11787 setting that option to 0. Closes ticket 18322.
11788 - Add a set of macros to check nonfatal assertions, for internal
11789 use. Migrating more of our checks to these should help us avoid
11790 needless crash bugs. Closes ticket 18613.
11792 o Minor features (performance):
11793 - Changer the "optimistic data" extension from "off by default" to
11794 "on by default". The default was ordinarily overridden by a
11795 consensus option, but when clients were bootstrapping for the
11796 first time, they would not have a consensus to get the option
11797 from. Changing this default When fetching a consensus for the
11798 first time, use optimistic data. This saves a round-trip during
11799 startup. Closes ticket 18815.
11801 o Minor features (relay, usability):
11802 - When the directory authorities refuse a bad relay's descriptor,
11803 encourage the relay operator to contact us. Many relay operators
11804 won't notice this line in their logs, but it's a win if even a few
11805 learn why we don't like what their relay was doing. Resolves
11808 o Minor features (testing):
11809 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11810 part of bug 18934; bugfix on 0.2.5.2-alpha.
11811 - Move the test-network.sh script to chutney, and modify tor's test-
11812 network.sh to call the (newer) chutney version when available.
11813 Resolves ticket 19116. Patch by teor.
11814 - Use the lcov convention for marking lines as unreachable, so that
11815 we don't count them when we're generating test coverage data.
11816 Update our coverage tools to understand this convention. Closes
11819 o Minor bugfixes (bootstrap):
11820 - Remember the directory we fetched the consensus or previous
11821 certificates from, and use it to fetch future authority
11822 certificates. This change improves bootstrapping performance.
11823 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11825 o Minor bugfixes (build):
11826 - The test-stem and test-network makefile targets now depend only on
11827 the tor binary that they are testing. Previously, they depended on
11828 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11829 patch from "cypherpunks".
11831 o Minor bugfixes (circuits):
11832 - Make sure extend_info_from_router() is only called on servers.
11833 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11835 o Minor bugfixes (compilation):
11836 - When building with Clang, use a full set of GCC warnings.
11837 (Previously, we included only a subset, because of the way we
11838 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11840 o Minor bugfixes (directory authority):
11841 - Authorities now sort the "package" lines in their votes, for ease
11842 of debugging. (They are already sorted in consensus documents.)
11843 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11844 - When parsing a detached signature, make sure we use the length of
11845 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11846 order to avoid comparing bytes out-of-bounds with a smaller digest
11847 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11849 o Minor bugfixes (documentation):
11850 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11851 19504; bugfix on 0.2.7.3-rc.
11852 - Fix the description of the --passphrase-fd option in the
11853 tor-gencert manpage. The option is used to pass the number of a
11854 file descriptor to read the passphrase from, not to read the file
11855 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11857 o Minor bugfixes (ephemeral hidden service):
11858 - When deleting an ephemeral hidden service, close its intro points
11859 even if they are not completely open. Fixes bug 18604; bugfix
11862 o Minor bugfixes (guard selection):
11863 - Use a single entry guard even if the NumEntryGuards consensus
11864 parameter is not provided. Fixes bug 17688; bugfix
11866 - Don't mark guards as unreachable if connection_connect() fails.
11867 That function fails for local reasons, so it shouldn't reveal
11868 anything about the status of the guard. Fixes bug 14334; bugfix
11871 o Minor bugfixes (hidden service client):
11872 - Increase the minimum number of internal circuits we preemptively
11873 build from 2 to 3, so a circuit is available when a client
11874 connects to another onion service. Fixes bug 13239; bugfix
11877 o Minor bugfixes (logging):
11878 - When logging a directory ownership mismatch, log the owning
11879 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11881 o Minor bugfixes (memory leaks):
11882 - Fix a small, uncommon memory leak that could occur when reading a
11883 truncated ed25519 key file. Fixes bug 18956; bugfix
11886 o Minor bugfixes (testing):
11887 - Allow clients to retry HSDirs much faster in test networks. Fixes
11888 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11889 - Disable ASAN's detection of segmentation faults while running
11890 test_bt.sh, so that we can make sure that our own backtrace
11891 generation code works. Fixes another aspect of bug 18934; bugfix
11892 on 0.2.5.2-alpha. Patch from "cypherpunks".
11893 - Fix the test-network-all target on out-of-tree builds by using the
11894 correct path to the test driver script. Fixes bug 19421; bugfix
11897 o Minor bugfixes (time):
11898 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11899 bugfix on all released tor versions.
11900 - When computing the difference between two times in milliseconds,
11901 we now round to the nearest millisecond correctly. Previously, we
11902 could sometimes round in the wrong direction. Fixes bug 19428;
11903 bugfix on 0.2.2.2-alpha.
11905 o Minor bugfixes (user interface):
11906 - Display a more accurate number of suppressed messages in the log
11907 rate-limiter. Previously, there was a potential integer overflow
11908 in the counter. Now, if the number of messages hits a maximum, the
11909 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11911 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11912 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11914 o Code simplification and refactoring:
11915 - Remove redundant declarations of the MIN macro. Closes
11917 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11918 Closes ticket 18462; patch from "icanhasaccount".
11919 - Split the 600-line directory_handle_command_get function into
11920 separate functions for different URL types. Closes ticket 16698.
11923 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
11924 ticket 19153. Patch from "U+039b".
11926 o Removed features:
11927 - Remove support for "GET /tor/bytes.txt" DirPort request, and
11928 "GETINFO dir-usage" controller request, which were only available
11929 via a compile-time option in Tor anyway. Feature was added in
11930 0.2.2.1-alpha. Resolves ticket 19035.
11931 - There is no longer a compile-time option to disable support for
11932 TransPort. (If you don't want TransPort; just don't use it.) Patch
11933 from "U+039b". Closes ticket 19449.
11936 - Run more workqueue tests as part of "make check". These had
11937 previously been implemented, but you needed to know special
11938 command-line options to enable them.
11939 - We now have unit tests for our code to reject zlib "compression
11940 bombs". (Fortunately, the code works fine.)
11943 Changes in version 0.2.8.6 - 2016-08-02
11945 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
11947 The Tor 0.2.8 series improves client bootstrapping performance,
11948 completes the authority-side implementation of improved identity
11949 keys for relays, and includes numerous bugfixes and performance
11950 improvements throughout the program. This release continues to
11951 improve the coverage of Tor's test suite. For a full list of
11952 changes since Tor 0.2.7, see the ReleaseNotes file.
11954 Changes since 0.2.8.5-rc:
11956 o Minor features (geoip):
11957 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
11960 o Minor bugfixes (compilation):
11961 - Fix a compilation warning in the unit tests on systems where char
11962 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
11964 o Minor bugfixes (fallback directories):
11965 - Remove 1 fallback that was on the hardcoded list, then opted-out,
11966 leaving 89 of the 100 fallbacks originally introduced in Tor
11967 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
11969 o Minor bugfixes (Linux seccomp2 sandbox):
11970 - Allow more syscalls when running with "Sandbox 1" enabled:
11971 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
11972 some systems, these are required for Tor to start. Fixes bug
11973 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
11974 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
11975 so that get_interface_address6_via_udp_socket_hack() can work.
11976 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
11979 Changes in version 0.2.8.5-rc - 2016-07-07
11980 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
11981 series. If we find no new bugs or regressions here, the first stable
11982 0.2.8 release will be identical to it. It has a few small bugfixes
11983 against previous versions.
11985 o Directory authority changes:
11986 - Urras is no longer a directory authority. Closes ticket 19271.
11988 o Major bugfixes (heartbeat):
11989 - Fix a regression that would crash Tor when the periodic
11990 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
11991 0.2.8.1-alpha. Reported by "kubaku".
11993 o Minor features (build):
11994 - Tor now again builds with the recent OpenSSL 1.1 development
11995 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
11996 - When building manual pages, set the timezone to "UTC", so that the
11997 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
11998 Patch from intrigeri.
12000 o Minor bugfixes (fallback directory selection):
12001 - Avoid errors during fallback selection if there are no eligible
12002 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
12005 o Minor bugfixes (IPv6, microdescriptors):
12006 - Don't check node addresses when we only have a routerstatus. This
12007 allows IPv6-only clients to bootstrap by fetching microdescriptors
12008 from fallback directory mirrors. (The microdescriptor consensus
12009 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
12012 o Minor bugfixes (logging):
12013 - Reduce pointlessly verbose log messages when directory servers
12014 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
12015 0.2.8.1-alpha. Patch by teor.
12016 - When a fallback directory changes its fingerprint from the hard-
12017 coded fingerprint, log a less severe, more explanatory log
12018 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
12020 o Minor bugfixes (Linux seccomp2 sandboxing):
12021 - Allow statistics to be written to disk when "Sandbox 1" is
12022 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
12023 0.2.6.1-alpha respectively.
12025 o Minor bugfixes (user interface):
12026 - Remove a warning message "Service [scrubbed] not found after
12027 descriptor upload". This message appears when one uses HSPOST
12028 control command to upload a service descriptor. Since there is
12029 only a descriptor and no service, showing this message is
12030 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
12032 o Fallback directory list:
12033 - Add a comment to the generated fallback directory list that
12034 explains how to comment out unsuitable fallbacks in a way that's
12035 compatible with the stem fallback parser.
12036 - Update fallback whitelist and blacklist based on relay operator
12037 emails. Blacklist unsuitable (non-working, over-volatile)
12038 fallbacks. Resolves ticket 19071. Patch by teor.
12039 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
12040 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
12041 ticket 19071; patch by teor.
12044 Changes in version 0.2.8.4-rc - 2016-06-15
12045 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
12046 If we find no new bugs or regressions here, the first stable 0.2.8
12047 release will be identical to it. It has a few small bugfixes against
12050 o Major bugfixes (user interface):
12051 - Correctly give a warning in the cases where a relay is specified
12052 by nickname, and one such relay is found, but it is not officially
12053 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
12055 o Minor features (build):
12056 - Tor now builds once again with the recent OpenSSL 1.1 development
12057 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
12059 o Minor features (geoip):
12060 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
12063 o Minor bugfixes (compilation):
12064 - Cause the unit tests to compile correctly on mingw64 versions that
12065 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
12067 o Minor bugfixes (downloading):
12068 - Predict more correctly whether we'll be downloading over HTTP when
12069 we determine the maximum length of a URL. This should avoid a
12070 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
12074 Changes in version 0.2.8.3-alpha - 2016-05-26
12075 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
12076 the course of the 0.2.8 development cycle. It improves the behavior of
12077 directory clients, fixes several crash bugs, fixes a gap in compiler
12078 hardening, and allows the full integration test suite to run on
12081 o Major bugfixes (security, client, DNS proxy):
12082 - Stop a crash that could occur when a client running with DNSPort
12083 received a query with multiple address types, and the first
12084 address type was not supported. Found and fixed by Scott Dial.
12085 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12087 o Major bugfixes (security, compilation):
12088 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
12089 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
12090 cause a compiler warning, thereby making other checks fail, and
12091 needlessly disabling compiler-hardening support. Fixes one case of
12092 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
12094 o Major bugfixes (security, directory authorities):
12095 - Fix a crash and out-of-bounds write during authority voting, when
12096 the list of relays includes duplicate ed25519 identity keys. Fixes
12097 bug 19032; bugfix on 0.2.8.2-alpha.
12099 o Major bugfixes (client, bootstrapping):
12100 - Check if bootstrap consensus downloads are still needed when the
12101 linked connection attaches. This prevents tor making unnecessary
12102 begindir-style connections, which are the only directory
12103 connections tor clients make since the fix for 18483 was merged.
12104 - Fix some edge cases where consensus download connections may not
12105 have been closed, even though they were not needed. Related to fix
12107 - Make relays retry consensus downloads the correct number of times,
12108 rather than the more aggressive client retry count. Fixes part of
12110 - Stop downloading consensuses when we have a consensus, even if we
12111 don't have all the certificates for it yet. Fixes bug 18809;
12112 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
12114 o Major bugfixes (directory mirrors):
12115 - Decide whether to advertise begindir support in the the same way
12116 we decide whether to advertise our DirPort. Allowing these
12117 decisions to become out-of-sync led to surprising behavior like
12118 advertising begindir support when hibernation made us not
12119 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
12122 o Major bugfixes (IPv6 bridges, client):
12123 - Actually use IPv6 addresses when selecting directory addresses for
12124 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
12127 o Major bugfixes (key management):
12128 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12129 pointer to the previous (uninitialized) key value. The impact here
12130 should be limited to a difficult-to-trigger crash, if OpenSSL is
12131 running an engine that makes key generation failures possible, or
12132 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12133 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12136 o Major bugfixes (testing):
12137 - Fix a bug that would block 'make test-network-all' on systems where
12138 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
12139 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
12140 bugfix on 0.2.8.1-alpha.
12142 o Minor features (clients):
12143 - Make clients, onion services, and bridge relays always use an
12144 encrypted begindir connection for directory requests. Resolves
12145 ticket 18483. Patch by "teor".
12147 o Minor features (fallback directory mirrors):
12148 - Give each fallback the same weight for client selection; restrict
12149 fallbacks to one per operator; report fallback directory detail
12150 changes when rebuilding list; add new fallback directory mirrors
12151 to the whitelist; and many other minor simplifications and fixes.
12152 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
12153 0.2.8.1-alpha; patch by "teor".
12154 - Replace the 21 fallbacks generated in January 2016 and included in
12155 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
12156 2016. Closes task 17158; patch by "teor".
12158 o Minor features (geoip):
12159 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
12162 o Minor bugfixes (assert, portability):
12163 - Fix an assertion failure in memarea.c on systems where "long" is
12164 shorter than the size of a pointer. Fixes bug 18716; bugfix
12167 o Minor bugfixes (bootstrap):
12168 - Consistently use the consensus download schedule for authority
12169 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
12171 o Minor bugfixes (build):
12172 - Remove a pair of redundant AM_CONDITIONAL declarations from
12173 configure.ac. Fixes one final case of bug 17744; bugfix
12175 - Resolve warnings when building on systems that are concerned with
12176 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
12178 - When libscrypt.h is found, but no libscrypt library can be linked,
12179 treat libscrypt as absent. Fixes bug 19161; bugfix
12182 o Minor bugfixes (client):
12183 - Turn all TestingClientBootstrap* into non-testing torrc options.
12184 This changes simply renames them by removing "Testing" in front of
12185 them and they do not require TestingTorNetwork to be enabled
12186 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
12187 - Make directory node selection more reliable, mainly for IPv6-only
12188 clients and clients with few reachable addresses. Fixes bug 18929;
12189 bugfix on 0.2.8.1-alpha. Patch by "teor".
12191 o Minor bugfixes (controller, microdescriptors):
12192 - Make GETINFO dir/status-vote/current/consensus conform to the
12193 control specification by returning "551 Could not open cached
12194 consensus..." when not caching consensuses. Fixes bug 18920;
12195 bugfix on 0.2.2.6-alpha.
12197 o Minor bugfixes (crypto, portability):
12198 - The SHA3 and SHAKE routines now produce the correct output on Big
12199 Endian systems. No code calls either algorithm yet, so this is
12200 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
12201 - Tor now builds again with the recent OpenSSL 1.1 development
12202 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
12205 o Minor bugfixes (directories):
12206 - When fetching extrainfo documents, compare their SHA256 digests
12207 and Ed25519 signing key certificates with the routerinfo that led
12208 us to fetch them, rather than with the most recent routerinfo.
12209 Otherwise we generate many spurious warnings about mismatches.
12210 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
12212 o Minor bugfixes (logging):
12213 - When we can't generate a signing key because OfflineMasterKey is
12214 set, do not imply that we should have been able to load it. Fixes
12215 bug 18133; bugfix on 0.2.7.2-alpha.
12216 - Stop periodic_event_dispatch() from blasting twelve lines per
12217 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
12218 - When rejecting a misformed INTRODUCE2 cell, only log at
12219 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
12221 o Minor bugfixes (pluggable transports):
12222 - Avoid reporting a spurious error when we decide that we don't need
12223 to terminate a pluggable transport because it has already exited.
12224 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
12226 o Minor bugfixes (pointer arithmetic):
12227 - Fix a bug in memarea_alloc() that could have resulted in remote
12228 heap write access, if Tor had ever passed an unchecked size to
12229 memarea_alloc(). Fortunately, all the sizes we pass to
12230 memarea_alloc() are pre-checked to be less than 128 kilobytes.
12231 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
12234 o Minor bugfixes (relays):
12235 - Consider more config options when relays decide whether to
12236 regenerate their descriptor. Fixes more of bug 12538; bugfix
12238 - Resolve some edge cases where we might launch an ORPort
12239 reachability check even when DisableNetwork is set. Noticed while
12240 fixing bug 18616; bugfix on 0.2.3.9-alpha.
12242 o Minor bugfixes (statistics):
12243 - We now include consensus downloads via IPv6 in our directory-
12244 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
12246 o Minor bugfixes (testing):
12247 - Allow directories in small networks to bootstrap by skipping
12248 DirPort checks when the consensus has no exits. Fixes bug 19003;
12249 bugfix on 0.2.8.1-alpha. Patch by teor.
12250 - Fix a small memory leak that would occur when the
12251 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
12252 bugfix on 0.2.5.2-alpha.
12254 o Minor bugfixes (time handling):
12255 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
12256 field. Otherwise, our unit tests crash on Windows. Fixes bug
12257 18977; bugfix on 0.2.2.25-alpha.
12260 - Document the contents of the 'datadir/keys' subdirectory in the
12261 manual page. Closes ticket 17621.
12262 - Stop recommending use of nicknames to identify relays in our
12263 MapAddress documentation. Closes ticket 18312.
12266 Changes in version 0.2.8.2-alpha - 2016-03-28
12267 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
12268 bugs in earlier versions of Tor, including some that prevented
12269 authorities using Tor 0.2.7.x from running correctly. IPv6 and
12270 directory support should also be much improved.
12272 o New system requirements:
12273 - Tor no longer supports versions of OpenSSL with a broken
12274 implementation of counter mode. (This bug was present in OpenSSL
12275 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
12276 longer runs with, these versions.
12277 - Tor no longer attempts to support platforms where the "time_t"
12278 type is unsigned. (To the best of our knowledge, only OpenVMS does
12279 this, and Tor has never actually built on OpenVMS.) Closes
12281 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
12282 later (released in 2008 and 2009 respectively). If you are
12283 building Tor from the git repository instead of from the source
12284 distribution, and your tools are older than this, you will need to
12285 upgrade. Closes ticket 17732.
12287 o Major bugfixes (security, pointers):
12288 - Avoid a difficult-to-trigger heap corruption attack when extending
12289 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12290 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12291 Reported by Guido Vranken.
12293 o Major bugfixes (bridges, pluggable transports):
12294 - Modify the check for OR connections to private addresses. Allow
12295 bridges on private addresses, including pluggable transports that
12296 ignore the (potentially private) address in the bridge line. Fixes
12297 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
12299 o Major bugfixes (compilation):
12300 - Repair hardened builds under the clang compiler. Previously, our
12301 use of _FORTIFY_SOURCE would conflict with clang's address
12302 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12304 o Major bugfixes (crash on shutdown):
12305 - Correctly handle detaching circuits from muxes when shutting down.
12306 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
12307 - Fix an assert-on-exit bug related to counting memory usage in
12308 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
12310 o Major bugfixes (crash on startup):
12311 - Fix a segfault during startup: If a Unix domain socket was
12312 configured as listener (such as a ControlSocket or a SocksPort
12313 "unix:" socket), and tor was started as root but not configured to
12314 switch to another user, tor would segfault while trying to string
12315 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
12318 o Major bugfixes (dns proxy mode, crash):
12319 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12320 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12322 o Major bugfixes (relays, bridge clients):
12323 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
12324 bridge clients use the address configured in the bridge line.
12325 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
12328 o Major bugfixes (voting):
12329 - Actually enable support for authorities to match routers by their
12330 Ed25519 identities. Previously, the code had been written, but
12331 some debugging code that had accidentally been left in the
12332 codebase made it stay turned off. Fixes bug 17702; bugfix
12334 - When collating votes by Ed25519 identities, authorities now
12335 include a "NoEdConsensus" flag if the ed25519 value (or lack
12336 thereof) for a server does not reflect the majority consensus.
12337 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12338 - When generating a vote with keypinning disabled, never include two
12339 entries for the same ed25519 identity. This bug was causing
12340 authorities to generate votes that they could not parse when a
12341 router violated key pinning by changing its RSA identity but
12342 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12343 18318. Bugfix on 0.2.7.2-alpha.
12345 o Minor features (security, win32):
12346 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
12347 attack. Fixes bug 18123; bugfix on all tor versions. Patch
12350 o Minor features (bug-resistance):
12351 - Make Tor survive errors involving connections without a
12352 corresponding event object. Previously we'd fail with an
12353 assertion; now we produce a log message. Related to bug 16248.
12355 o Minor features (build):
12356 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12357 as having possible IPFW support. Closes ticket 18448. Patch from
12358 Steven Chamberlain.
12360 o Minor features (code hardening):
12361 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12362 level code, to harden against accidental failures to NUL-
12363 terminate. Part of ticket 17852. Patch from jsturgix. Found
12366 o Minor features (crypto):
12367 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12368 p is a safe prime, and g is a suitable generator. Closes
12371 o Minor features (geoip):
12372 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
12375 o Minor features (hidden service directory):
12376 - Streamline relay-side hsdir handling: when relays consider whether
12377 to accept an uploaded hidden service descriptor, they no longer
12378 check whether they are one of the relays in the network that is
12379 "supposed" to handle that descriptor. Implements ticket 18332.
12381 o Minor features (IPv6):
12382 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12383 to 1, tor prefers IPv6 directory addresses.
12384 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12385 avoids using IPv4 for client OR and directory connections.
12386 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12387 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12388 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12390 o Minor features (linux seccomp2 sandbox):
12391 - Reject attempts to change our Address with "Sandbox 1" enabled.
12392 Changing Address with Sandbox turned on would never actually work,
12393 but previously it would fail in strange and confusing ways. Found
12394 while fixing 18548.
12396 o Minor features (robustness):
12397 - Exit immediately with an error message if the code attempts to use
12398 Libevent without having initialized it. This should resolve some
12399 frequently-made mistakes in our unit tests. Closes ticket 18241.
12401 o Minor features (unix domain sockets):
12402 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
12403 Unix domain sockets without checking the permissions on the parent
12404 directory. (Tor checks permissions by default because some
12405 operating systems only check permissions on the parent directory.
12406 However, some operating systems do look at permissions on the
12407 socket, and tor's default check is unneeded.) Closes ticket 18458.
12410 o Minor bugfixes (exit policies, security):
12411 - Refresh an exit relay's exit policy when interface addresses
12412 change. Previously, tor only refreshed the exit policy when the
12413 configured external address changed. Fixes bug 18208; bugfix on
12414 0.2.7.3-rc. Patch by teor.
12416 o Minor bugfixes (security, hidden services):
12417 - Prevent hidden services connecting to client-supplied rendezvous
12418 addresses that are reserved as internal or multicast. Fixes bug
12419 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
12421 o Minor bugfixes (build):
12422 - Do not link the unit tests against both the testing and non-
12423 testing versions of the static libraries. Fixes bug 18490; bugfix
12425 - Avoid spurious failures from configure files related to calling
12426 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
12427 0.2.0.1-alpha. Patch from "cypherpunks".
12428 - Silence spurious clang-scan warnings in the ed25519_donna code by
12429 explicitly initializing some objects. Fixes bug 18384; bugfix on
12430 0.2.7.2-alpha. Patch by teor.
12432 o Minor bugfixes (client, bootstrap):
12433 - Count receipt of new microdescriptors as progress towards
12434 bootstrapping. Previously, with EntryNodes set, Tor might not
12435 successfully repopulate the guard set on bootstrapping. Fixes bug
12436 16825; bugfix on 0.2.3.1-alpha.
12438 o Minor bugfixes (code correctness):
12439 - Update to the latest version of Trunnel, which tries harder to
12440 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
12441 by clang address sanitizer. Fixes bug 18373; bugfix
12444 o Minor bugfixes (configuration):
12445 - Fix a tiny memory leak when parsing a port configuration ending in
12446 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
12448 o Minor bugfixes (containers):
12449 - If we somehow attempt to construct a heap with more than
12450 1073741822 elements, avoid an integer overflow when maintaining
12451 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
12453 o Minor bugfixes (correctness):
12454 - Fix a bad memory handling bug that would occur if we had queued a
12455 cell on a channel's incoming queue. Fortunately, we can't actually
12456 queue a cell like that as our code is constructed today, but it's
12457 best to avoid this kind of error, even if there isn't any code
12458 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
12460 o Minor bugfixes (directory):
12461 - When generating a URL for a directory server on an IPv6 address,
12462 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
12463 on 0.2.3.9-alpha. Patch from Malek.
12465 o Minor bugfixes (fallback directory mirrors):
12466 - When requesting extrainfo descriptors from a trusted directory
12467 server, check whether it is an authority or a fallback directory
12468 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
12469 0.2.4.7-alpha. Reported by atagar, patch by teor.
12471 o Minor bugfixes (hidden service, client):
12472 - Handle the case where the user makes several fast consecutive
12473 requests to the same .onion address. Previously, the first six
12474 requests would each trigger a descriptor fetch, each picking a
12475 directory (there are 6 overall) and the seventh one would fail
12476 because no directories were left, thereby triggering a close on
12477 all current directory connections asking for the hidden service.
12478 The solution here is to not close the connections if we have
12479 pending directory fetches. Fixes bug 15937; bugfix
12482 o Minor bugfixes (hidden service, control port):
12483 - Add the onion address to the HS_DESC event for the UPLOADED action
12484 both on success or failure. It was previously hardcoded with
12485 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
12487 o Minor bugfixes (hidden service, directory):
12488 - Bridges now refuse "rendezvous2" (hidden service descriptor)
12489 publish attempts. Suggested by ticket 18332.
12491 o Minor bugfixes (linux seccomp2 sandbox):
12492 - Allow the setrlimit syscall, and the prlimit and prlimit64
12493 syscalls, which some libc implementations use under the hood.
12494 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
12495 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
12496 enabled and no DNS resolvers configured. This should help TAILS
12497 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
12498 - Fix the sandbox's interoperability with unix domain sockets under
12499 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
12501 o Minor bugfixes (logging):
12502 - When logging information about an unparsable networkstatus vote or
12503 consensus, do not say "vote" when we mean consensus. Fixes bug
12504 18368; bugfix on 0.2.0.8-alpha.
12505 - Scrub service name in "unrecognized service ID" log messages.
12506 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
12507 - Downgrade logs and backtraces about IP versions to info-level.
12508 Only log backtraces once each time tor runs. Assists in diagnosing
12509 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
12510 Christian, patch by teor.
12512 o Minor bugfixes (memory safety):
12513 - Avoid freeing an uninitialized pointer when opening a socket fails
12514 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
12515 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
12517 - Correctly duplicate addresses in get_interface_address6_list().
12518 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
12519 patch by "cypherpunks".
12520 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
12522 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
12523 18672; bugfix on 0.2.5.1-alpha.
12525 o Minor bugfixes (private directory):
12526 - Prevent a race condition when creating private directories. Fixes
12527 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
12528 Patch from jsturgix. Found with Flawfinder.
12530 o Minor bugfixes (test networks, IPv6):
12531 - Allow internal IPv6 addresses in descriptors in test networks.
12532 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
12535 o Minor bugfixes (testing):
12536 - We no longer disable assertions in the unit tests when coverage is
12537 enabled. Instead, we require you to say --disable-asserts-in-tests
12538 to the configure script if you need assertions disabled in the
12539 unit tests (for example, if you want to perform branch coverage).
12540 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
12542 o Minor bugfixes (time parsing):
12543 - Avoid overflow in tor_timegm when parsing dates in and after 2038
12544 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
12545 0.0.2pre14. Patch by teor.
12547 o Minor bugfixes (tor-gencert):
12548 - Correctly handle the case where an authority operator enters a
12549 passphrase but sends an EOF before sending a newline. Fixes bug
12550 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
12552 o Code simplification and refactoring:
12553 - Quote all the string interpolations in configure.ac -- even those
12554 which we are pretty sure can't contain spaces. Closes ticket
12555 17744. Patch from zerosion.
12556 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
12557 inplace, so there's no need to have a separate implementation for
12558 the non-inplace code. Closes ticket 18258. Patch from Malek.
12559 - Simplify return types for some crypto functions that can't
12560 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
12563 - Change build messages to refer to "Fedora" instead of "Fedora
12564 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
12565 Patches from "icanhasaccount" and "cypherpunks".
12567 o Removed features:
12568 - We no longer maintain an internal freelist in memarea.c.
12569 Allocators should be good enough to make this code unnecessary,
12570 and it's doubtful that it ever had any performance benefit.
12573 - Fix several warnings from clang's address sanitizer produced in
12575 - Treat backtrace test failures as expected on FreeBSD until we
12576 solve bug 17808. Closes ticket 18204.
12579 Changes in version 0.2.8.1-alpha - 2016-02-04
12580 Tor 0.2.8.1-alpha is the first alpha release in its series. It
12581 includes numerous small features and bugfixes against previous Tor
12582 versions, and numerous small infrastructure improvements. The most
12583 notable features are a set of improvements to the directory subsystem.
12585 o Major features (security, Linux):
12586 - When Tor starts as root on Linux and is told to switch user ID, it
12587 can now retain the capability to bind to low ports. By default,
12588 Tor will do this only when it's switching user ID and some low
12589 ports have been configured. You can change this behavior with the
12590 new option KeepBindCapabilities. Closes ticket 8195.
12592 o Major features (directory system):
12593 - When bootstrapping multiple consensus downloads at a time, use the
12594 first one that starts downloading, and close the rest. This
12595 reduces failures when authorities or fallback directories are slow
12596 or down. Together with the code for feature 15775, this feature
12597 should reduces failures due to fallback churn. Implements ticket
12598 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
12599 "mikeperry" and "teor".
12600 - Include a trial list of 21 default fallback directories, generated
12601 in January 2016, based on an opt-in survey of suitable relays.
12602 Doing this should make clients bootstrap more quickly and reliably,
12603 and reduce the load on the directory authorities. Closes ticket
12604 15775. Patch by "teor".
12605 Candidates identified using an OnionOO script by "weasel", "teor",
12606 "gsathya", and "karsten".
12607 - Previously only relays that explicitly opened a directory port
12608 (DirPort) accepted directory requests from clients. Now all
12609 relays, with and without a DirPort, accept and serve tunneled
12610 directory requests that they receive through their ORPort. You can
12611 disable this behavior using the new DirCache option. Closes
12614 o Major key updates:
12615 - Update the V3 identity key for the dannenberg directory authority:
12616 it was changed on 18 November 2015. Closes task 17906. Patch
12619 o Minor features (security, clock):
12620 - Warn when the system clock appears to move back in time (when the
12621 state file was last written in the future). Tor doesn't know that
12622 consensuses have expired if the clock is in the past. Patch by
12623 "teor". Implements ticket 17188.
12625 o Minor features (security, exit policies):
12626 - ExitPolicyRejectPrivate now rejects more private addresses by
12627 default. Specifically, it now rejects the relay's outbound bind
12628 addresses (if configured), and the relay's configured port
12629 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12630 0.2.0.11-alpha. Patch by "teor".
12632 o Minor features (security, memory erasure):
12633 - Set the unused entries in a smartlist to NULL. This helped catch
12634 a (harmless) bug, and shouldn't affect performance too much.
12635 Implements ticket 17026.
12636 - Use SecureMemoryWipe() function to securely clean memory on
12637 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12638 Implements feature 17986.
12639 - Use explicit_bzero or memset_s when present. Previously, we'd use
12640 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
12641 from <logan@hackers.mu> and <selven@hackers.mu>.
12642 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12643 zero size. Check size argument to memwipe() for underflow. Fixes
12644 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12647 o Minor features (security, RNG):
12648 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
12649 positively are not allowed to fail. Previously we depended on
12650 internal details of OpenSSL's behavior. Closes ticket 17686.
12651 - Never use the system entropy output directly for anything besides
12652 seeding the PRNG. When we want to generate important keys, instead
12653 of using system entropy directly, we now hash it with the PRNG
12654 stream. This may help resist certain attacks based on broken OS
12655 entropy implementations. Closes part of ticket 17694.
12656 - Use modern system calls (like getentropy() or getrandom()) to
12657 generate strong entropy on platforms that have them. Closes
12660 o Minor features (accounting):
12661 - Added two modes to the AccountingRule option: One for limiting
12662 only the number of bytes sent ("AccountingRule out"), and one for
12663 limiting only the number of bytes received ("AccountingRule in").
12664 Closes ticket 15989; patch from "unixninja92".
12666 o Minor features (build):
12667 - Since our build process now uses "make distcheck", we no longer
12668 force "make dist" to depend on "make check". Closes ticket 17893;
12669 patch from "cypherpunks."
12670 - Tor now builds successfully with the recent OpenSSL 1.1
12671 development branch, and with the latest LibreSSL. Closes tickets
12672 17549, 17921, and 17984.
12674 o Minor features (controller):
12675 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12676 tickets 16774 and 17817. Patch by George Tankersley.
12677 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12678 service descriptor from a service's local hidden service
12679 descriptor cache. Closes ticket 14846.
12680 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12681 controllers can examine the the reject rules added by
12682 ExitPolicyRejectPrivate. This makes it easier for stem to display
12685 o Minor features (crypto):
12686 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12688 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12689 - When allocating a digest state object, allocate no more space than
12690 we actually need. Previously, we would allocate as much space as
12691 the state for the largest algorithm would need. This change saves
12692 up to 672 bytes per circuit. Closes ticket 17796.
12693 - Improve performance when hashing non-multiple of 8 sized buffers,
12694 based on Andrew Moon's public domain SipHash-2-4 implementation.
12695 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12697 o Minor features (directory downloads):
12698 - Wait for busy authorities and fallback directories to become non-
12699 busy when bootstrapping. (A similar change was made in 6c443e987d
12700 for directory caches chosen from the consensus.) Closes ticket
12701 17864; patch by "teor".
12702 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12703 directory mirrors. The default is 1; set it to 0 to disable
12704 fallbacks. Implements ticket 17576. Patch by "teor".
12706 o Minor features (geoip):
12707 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
12710 o Minor features (IPv6):
12711 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12712 FallbackDir torrc options, to specify an IPv6 address for an
12713 authority or fallback directory. Add hard-coded ipv6 addresses for
12714 directory authorities that have them. Closes ticket 17327; patch
12715 from Nick Mathewson and "teor".
12716 - Add address policy assume_action support for IPv6 addresses.
12717 - Limit IPv6 mask bits to 128.
12718 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12719 almost always a bug. Closes ticket 17863; patch by "teor".
12720 - Allow users to configure directory authorities and fallback
12721 directory servers with IPv6 addresses and ORPorts. Resolves
12723 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12724 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12725 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12726 17638; bugfix on 0.0.2pre8. Patch by "teor".
12728 o Minor features (logging):
12729 - When logging to syslog, allow a tag to be added to the syslog
12730 identity (the string prepended to every log message). The tag can
12731 be configured with SyslogIdentityTag and defaults to none. Setting
12732 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12735 o Minor features (portability):
12736 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12737 patch from <logan@hackers.mu>.
12739 o Minor features (relay, address discovery):
12740 - Add a family argument to get_interface_addresses_raw() and
12741 subfunctions to make network interface address interogation more
12742 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12743 types of interfaces from the operating system. Resolves
12745 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12746 fails to enumerate interface addresses using the platform-specific
12747 API, have it rely on the UDP socket fallback technique to try and
12748 find out what IP addresses (both IPv4 and IPv6) our machine has.
12749 Resolves ticket 17951.
12751 o Minor features (replay cache):
12752 - The replay cache now uses SHA256 instead of SHA1. Implements
12753 feature 8961. Patch by "teor", issue reported by "rransom".
12755 o Minor features (unix file permissions):
12756 - Defer creation of Unix sockets until after setuid. This avoids
12757 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12758 CapabilityBoundingSet, or chown and fowner when using SELinux.
12759 Implements part of ticket 17562. Patch from Jamie Nguyen.
12760 - If any directory created by Tor is marked as group readable, the
12761 filesystem group is allowed to be either the default GID or the
12762 root user. Allowing root to read the DataDirectory prevents the
12763 need for CAP_READ_SEARCH when using systemd's
12764 CapabilityBoundingSet, or dac_read_search when using SELinux.
12765 Implements part of ticket 17562. Patch from Jamie Nguyen.
12766 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12767 1, the DataDirectory will be made readable by the default GID.
12768 Implements part of ticket 17562. Patch from Jamie Nguyen.
12770 o Minor bugfixes (accounting):
12771 - The max bandwidth when using 'AccountRule sum' is now correctly
12772 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12773 from "unixninja92".
12775 o Minor bugfixes (code correctness):
12776 - When closing an entry connection, generate a warning if we should
12777 have sent an end cell for it but we haven't. Fixes bug 17876;
12778 bugfix on 0.2.3.2-alpha.
12779 - Assert that allocated memory held by the reputation code is freed
12780 according to its internal counters. Fixes bug 17753; bugfix
12782 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12785 o Minor bugfixes (compilation):
12786 - Mark all object files that include micro-revision.i as depending
12787 on it, so as to make parallel builds more reliable. Fixes bug
12788 17826; bugfix on 0.2.5.1-alpha.
12789 - Don't try to use the pthread_condattr_setclock() function unless
12790 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12791 17819; bugfix on 0.2.6.3-alpha.
12792 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12794 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12795 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12796 - Fix search for libevent libraries on OpenBSD (and other systems
12797 that install libevent 1 and libevent 2 in parallel). Fixes bug
12798 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12799 - Isolate environment variables meant for tests from the rest of the
12800 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12801 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12803 - Remove config.log only from make distclean, not from make clean.
12804 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12806 o Minor bugfixes (crypto):
12807 - Check the return value of HMAC() and assert on failure. Fixes bug
12808 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12810 o Minor bugfixes (fallback directories):
12811 - Mark fallbacks as "too busy" when they return a 503 response,
12812 rather than just marking authorities. Fixes bug 17572; bugfix on
12813 0.2.4.7-alpha. Patch by "teor".
12815 o Minor bugfixes (IPv6):
12816 - Update the limits in max_dl_per_request for IPv6 address length.
12817 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12819 o Minor bugfixes (linux seccomp2 sandbox):
12820 - Fix a crash when using offline master ed25519 keys with the Linux
12821 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12823 o Minor bugfixes (logging):
12824 - In log messages that include a function name, use __FUNCTION__
12825 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12826 with clang __PRETTY_FUNCTION__ has extra information we don't
12827 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12829 - Remove needless quotes from a log message about unparseable
12830 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12832 o Minor bugfixes (portability):
12833 - Remove an #endif from configure.ac so that we correctly detect the
12834 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12837 o Minor bugfixes (relays):
12838 - Check that both the ORPort and DirPort (if present) are reachable
12839 before publishing a relay descriptor. Otherwise, relays publish a
12840 descriptor with DirPort 0 when the DirPort reachability test takes
12841 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12842 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12844 o Minor bugfixes (relays, hidden services):
12845 - Refuse connection requests to private OR addresses unless
12846 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12847 then refuse to send any cells to a private address. Fixes bugs
12848 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12850 o Minor bugfixes (safe logging):
12851 - When logging a malformed hostname received through socks4, scrub
12852 it if SafeLogging says we should. Fixes bug 17419; bugfix
12855 o Minor bugfixes (statistics code):
12856 - Consistently check for overflow in round_*_to_next_multiple_of
12857 functions, and add unit tests with additional and maximal values.
12858 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12859 - Handle edge cases in the laplace functions: avoid division by
12860 zero, avoid taking the log of zero, and silence clang type
12861 conversion warnings using round and trunc. Add unit tests for edge
12862 cases with maximal values. Fixes part of bug 13192; bugfix
12865 o Minor bugfixes (testing):
12866 - The test for log_heartbeat was incorrectly failing in timezones
12867 with non-integer offsets. Instead of comparing the end of the time
12868 string against a constant, compare it to the output of
12869 format_local_iso_time when given the correct input. Fixes bug
12870 18039; bugfix on 0.2.5.4-alpha.
12871 - Make unit tests pass on IPv6-only systems, and systems without
12872 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12873 bugfix on 0.2.7.3-rc. Patch by "teor".
12874 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12876 - Check the full results of SHA256 and SHA512 digests in the unit
12877 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12879 o Code simplification and refactoring:
12880 - Move logging of redundant policy entries in
12881 policies_parse_exit_policy_internal into its own function. Closes
12882 ticket 17608; patch from "juce".
12883 - Extract the more complicated parts of circuit_mark_for_close()
12884 into a new function that we run periodically before circuits are
12885 freed. This change removes more than half of the functions
12886 currently in the "blob". Closes ticket 17218.
12887 - Clean up a little duplicated code in
12888 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12890 - Decouple the list of streams waiting to be attached to circuits
12891 from the overall connection list. This change makes it possible to
12892 attach streams quickly while simplifying Tor's callgraph and
12893 avoiding O(N) scans of the entire connection list. Closes
12895 - When a direct directory request fails immediately on launch,
12896 instead of relaunching that request from inside the code that
12897 launches it, instead mark the connection for teardown. This change
12898 simplifies Tor's callback and prevents the directory-request
12899 launching code from invoking itself recursively. Closes
12901 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12902 use them. Closes ticket 17926.
12905 - Add a description of the correct use of the '--keygen' command-
12906 line option. Closes ticket 17583; based on text by 's7r'.
12907 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12908 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12909 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12910 - Mention torspec URL in the manpage and point the reader to it
12911 whenever we mention a document that belongs in torspce. Fixes
12914 o Removed features:
12915 - Remove client-side support for connecting to Tor relays running
12916 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12917 the v3 TLS handshake protocol, and are no longer allowed on the
12918 Tor network. Implements the client side of ticket 11150. Based on
12919 patches by Tom van der Woerdt.
12922 - Add unit tests to check for common RNG failure modes, such as
12923 returning all zeroes, identical values, or incrementing values
12924 (OpenSSL's rand_predictable feature). Patch by "teor".
12925 - Log more information when the backtrace tests fail. Closes ticket
12926 17892. Patch from "cypherpunks."
12927 - Always test both ed25519 backends, so that we can be sure that our
12928 batch-open replacement code works. Part of ticket 16794.
12929 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
12930 portion of ticket 16831.
12931 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
12932 util_format.c, directory.c, and options_validate.c. Closes tickets
12933 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
12935 - Unit tests for directory_handle_command_get. Closes ticket 17004.
12936 Patch from Reinaldo de Souza Jr.
12939 Changes in version 0.2.7.6 - 2015-12-10
12940 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
12941 well as a minor bug in hidden service reliability.
12943 o Major bugfixes (guard selection):
12944 - Actually look at the Guard flag when selecting a new directory
12945 guard. When we implemented the directory guard design, we
12946 accidentally started treating all relays as if they have the Guard
12947 flag during guard selection, leading to weaker anonymity and worse
12948 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
12951 o Minor features (geoip):
12952 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
12955 o Minor bugfixes (compilation):
12956 - When checking for net/pfvar.h, include netinet/in.h if possible.
12957 This fixes transparent proxy detection on OpenBSD. Fixes bug
12958 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
12959 - Fix a compilation warning with Clang 3.6: Do not check the
12960 presence of an address which can never be NULL. Fixes bug 17781.
12962 o Minor bugfixes (correctness):
12963 - When displaying an IPv6 exit policy, include the mask bits
12964 correctly even when the number is greater than 31. Fixes bug
12965 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
12966 - The wrong list was used when looking up expired intro points in a
12967 rend service object, causing what we think could be reachability
12968 issues for hidden services, and triggering a BUG log. Fixes bug
12969 16702; bugfix on 0.2.7.2-alpha.
12970 - Fix undefined behavior in the tor_cert_checksig function. Fixes
12971 bug 17722; bugfix on 0.2.7.2-alpha.
12974 Changes in version 0.2.7.5 - 2015-11-20
12975 The Tor 0.2.7 release series is dedicated to the memory of Tor user
12976 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
12977 tirelessly to advocate human rights regardless of national borders,
12978 and oppose the encroachments of mass surveillance. He opposed national
12979 exceptionalism, he brought clarity to legal and policy debates, he
12980 understood and predicted the impact of mass surveillance on the world,
12981 and he laid the groundwork for resisting it. While serving on the Tor
12982 Project's board of directors, he brought us his uncompromising focus
12983 on technical excellence in the service of humankind. Caspar was an
12984 inimitable force for good and a wonderful friend. He was kind,
12985 humorous, generous, gallant, and believed we should protect one
12986 another without exception. We honor him here for his ideals, his
12987 efforts, and his accomplishments. Please honor his memory with works
12988 that would make him proud.
12990 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
12992 The 0.2.7 series adds a more secure identity key type for relays,
12993 improves cryptography performance, resolves several longstanding
12994 hidden-service performance issues, improves controller support for
12995 hidden services, and includes small bugfixes and performance
12996 improvements throughout the program. This release series also includes
12997 more tests than before, and significant simplifications to which parts
12998 of Tor invoke which others.
13000 (This release contains no code changes since 0.2.7.4-rc.)
13003 Changes in version 0.2.7.4-rc - 2015-10-21
13004 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
13005 fixes some important memory leaks, and a scary-looking (but mostly
13006 harmless in practice) invalid-read bug. It also has a few small
13007 bugfixes, notably fixes for compilation and portability on different
13008 platforms. If no further significant bounds are found, the next
13009 release will the the official stable release.
13011 o Major bugfixes (security, correctness):
13012 - Fix an error that could cause us to read 4 bytes before the
13013 beginning of an openssl string. This bug could be used to cause
13014 Tor to crash on systems with unusual malloc implementations, or
13015 systems with unusual hardening installed. Fixes bug 17404; bugfix
13018 o Major bugfixes (correctness):
13019 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
13020 bug 17401; bugfix on 0.2.7.3-rc.
13022 o Major bugfixes (memory leaks):
13023 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
13024 17398; bugfix on 0.2.6.1-alpha.
13025 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
13026 17402; bugfix on 0.2.7.3-rc.
13027 - Fix a memory leak when reading an expired signing key from disk.
13028 Fixes bug 17403; bugfix on 0.2.7.2-rc.
13030 o Minor features (geoIP):
13031 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
13034 o Minor bugfixes (compilation):
13035 - Repair compilation with the most recent (unreleased, alpha)
13036 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
13037 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
13038 17251; bugfix on 0.2.7.2-alpha.
13039 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
13040 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
13042 o Minor bugfixes (portability):
13043 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
13044 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
13047 o Minor bugfixes (sandbox):
13048 - Add the "hidserv-stats" filename to our sandbox filter for the
13049 HiddenServiceStatistics option to work properly. Fixes bug 17354;
13050 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
13052 o Minor bugfixes (testing):
13053 - Add unit tests for get_interface_address* failure cases. Fixes bug
13054 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
13055 - Fix breakage when running 'make check' with BSD make. Fixes bug
13056 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
13057 - Make the get_ifaddrs_* unit tests more tolerant of different
13058 network configurations. (Don't assume every test box has an IPv4
13059 address, and don't assume every test box has a non-localhost
13060 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
13061 - Skip backtrace tests when backtrace support is not compiled in.
13062 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
13066 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
13067 - Note that HiddenServicePorts can take a unix domain socket. Closes
13071 Changes in version 0.2.7.3-rc - 2015-09-25
13072 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
13073 contains numerous usability fixes for Ed25519 keys, safeguards against
13074 several misconfiguration problems, significant simplifications to
13075 Tor's callgraph, and numerous bugfixes and small features.
13077 This is the most tested release of Tor to date. The unit tests cover
13078 39.40% of the code, and the integration tests (accessible with "make
13079 test-full-online", requiring stem and chutney and a network
13080 connection) raise the coverage to 64.49%.
13082 o Major features (security, hidden services):
13083 - Hidden services, if using the EntryNodes option, are required to
13084 use more than one EntryNode, in order to avoid a guard discovery
13085 attack. (This would only affect people who had configured hidden
13086 services and manually specified the EntryNodes option with a
13087 single entry-node. The impact was that it would be easy to
13088 remotely identify the guard node used by such a hidden service.
13089 See ticket for more information.) Fixes ticket 14917.
13091 o Major features (Ed25519 keys, keypinning):
13092 - The key-pinning option on directory authorities is now advisory-
13093 only by default. In a future version, or when the AuthDirPinKeys
13094 option is set, pins are enforced again. Disabling key-pinning
13095 seemed like a good idea so that we can survive the fallout of any
13096 usability problems associated with Ed25519 keys. Closes
13099 o Major features (Ed25519 performance):
13100 - Improve the speed of Ed25519 operations and Curve25519 keypair
13101 generation when built targeting 32 bit x86 platforms with SSE2
13102 available. Implements ticket 16535.
13103 - Improve the runtime speed of Ed25519 signature verification by
13104 using Ed25519-donna's batch verification support. Implements
13107 o Major features (performance testing):
13108 - The test-network.sh script now supports performance testing.
13109 Requires corresponding chutney performance testing changes. Patch
13110 by "teor". Closes ticket 14175.
13112 o Major features (relay, Ed25519):
13113 - Significant usability improvements for Ed25519 key management. Log
13114 messages are better, and the code can recover from far more
13115 failure conditions. Thanks to "s7r" for reporting and diagnosing
13117 - Add a new OfflineMasterKey option to tell Tor never to try loading
13118 or generating a secret Ed25519 identity key. You can use this in
13119 combination with tor --keygen to manage offline and/or encrypted
13120 Ed25519 keys. Implements ticket 16944.
13121 - Add a --newpass option to allow changing or removing the
13122 passphrase of an encrypted key with tor --keygen. Implements part
13124 - On receiving a HUP signal, check to see whether the Ed25519
13125 signing key has changed, and reload it if so. Closes ticket 16790.
13127 o Major bugfixes (relay, Ed25519):
13128 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
13129 0.2.7.2-alpha. Reported by "s7r".
13130 - Improve handling of expired signing keys with offline master keys.
13131 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
13133 o Minor features (client-side privacy):
13134 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
13135 lifespan when IsolateSOCKSAuth and streams with SOCKS
13136 authentication are attached to the circuit. This allows
13137 applications like TorBrowser to manage circuit lifetime on their
13138 own. Implements feature 15482.
13139 - When logging malformed hostnames from SOCKS5 requests, respect
13140 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
13142 o Minor features (compilation):
13143 - Give a warning as early as possible when trying to build with an
13144 unsupported OpenSSL version. Closes ticket 16901.
13145 - Fail during configure if we're trying to build against an OpenSSL
13146 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
13147 which started requiring ECC.
13149 o Minor features (geoip):
13150 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
13153 o Minor features (hidden services):
13154 - Relays need to have the Fast flag to get the HSDir flag. As this
13155 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
13156 drop. This change should make some attacks against the hidden
13157 service directory system harder. Fixes ticket 15963.
13158 - Turn on hidden service statistics collection by setting the torrc
13159 option HiddenServiceStatistics to "1" by default. (This keeps
13160 track only of the fraction of traffic used by hidden services, and
13161 the total number of hidden services in existence.) Closes
13163 - Client now uses an introduction point failure cache to know when
13164 to fetch or keep a descriptor in their cache. Previously, failures
13165 were recorded implicitly, but not explicitly remembered. Closes
13168 o Minor features (testing, authorities, documentation):
13169 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
13170 explicitly manage consensus flags in testing networks. Patch by
13171 "robgjansen", modified by "teor". Implements part of ticket 14882.
13173 o Minor bugfixes (security, exit policies):
13174 - ExitPolicyRejectPrivate now also rejects the relay's published
13175 IPv6 address (if any), and any publicly routable IPv4 or IPv6
13176 addresses on any local interfaces. ticket 17027. Patch by "teor".
13177 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
13179 o Minor bug fixes (torrc exit policies):
13180 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
13181 produce IPv6 wildcard addresses. Previously they would produce
13182 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
13183 of bug 16069; bugfix on 0.2.4.7-alpha.
13184 - When parsing torrc ExitPolicies, we now warn for a number of cases
13185 where the user's intent is likely to differ from Tor's actual
13186 behavior. These include: using an IPv4 address with an accept6 or
13187 reject6 line; using "private" on an accept6 or reject6 line; and
13188 including any ExitPolicy lines after accept *:* or reject *:*.
13189 Related to ticket 16069.
13190 - When parsing torrc ExitPolicies, we now issue an info-level
13191 message when expanding an "accept/reject *" line to include both
13192 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
13193 - In each instance above, usage advice is provided to avoid the
13194 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
13195 16069; bugfix on 0.2.4.7-alpha.
13197 o Minor bugfixes (authority):
13198 - Don't assign "HSDir" to a router if it isn't Valid and Running.
13199 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
13200 - Downgrade log messages about Ed25519 key issues if they are in old
13201 cached router descriptors. Fixes part of bug 16286; bugfix
13203 - When we find an Ed25519 key issue in a cached descriptor, stop
13204 saying the descriptor was just "uploaded". Fixes another part of
13205 bug 16286; bugfix on 0.2.7.2-alpha.
13207 o Minor bugfixes (control port):
13208 - Repair a warning and a spurious result when getting the maximum
13209 number of file descriptors from the controller. Fixes bug 16697;
13210 bugfix on 0.2.7.2-alpha.
13212 o Minor bugfixes (correctness):
13213 - When calling channel_free_list(), avoid calling smartlist_remove()
13214 while inside a FOREACH loop. This partially reverts commit
13215 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
13216 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
13218 o Minor bugfixes (documentation):
13219 - Advise users on how to configure separate IPv4 and IPv6 exit
13220 policies in the manpage and sample torrcs. Related to ticket 16069.
13221 - Fix the usage message of tor-resolve(1) so that it no longer lists
13222 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
13223 - Fix an error in the manual page and comments for
13224 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
13225 required "ORPort connectivity". While this is true, it is in no
13226 way unique to the HSDir flag. Of all the flags, only HSDirs need a
13227 DirPort configured in order for the authorities to assign that
13228 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
13231 o Minor bugfixes (Ed25519):
13232 - Fix a memory leak when reading router descriptors with expired
13233 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
13235 o Minor bugfixes (linux seccomp2 sandbox):
13236 - Allow bridge authorities to run correctly under the seccomp2
13237 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
13238 - Allow routers with ed25519 keys to run correctly under the
13239 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
13241 o Minor bugfixes (open file limit):
13242 - Fix set_max_file_descriptors() to set by default the max open file
13243 limit to the current limit when setrlimit() fails. Fixes bug
13244 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
13246 o Minor bugfixes (portability):
13247 - Try harder to normalize the exit status of the Tor process to the
13248 standard-provided range. Fixes bug 16975; bugfix on every version
13250 - Check correctly for Windows socket errors in the workqueue
13251 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
13252 - Fix the behavior of crypto_rand_time_range() when told to consider
13253 times before 1970. (These times were possible when running in a
13254 simulated network environment where time()'s output starts at
13255 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
13256 - Restore correct operation of TLS client-cipher detection on
13257 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
13259 o Minor bugfixes (relay):
13260 - Ensure that worker threads actually exit when a fatal error or
13261 shutdown is indicated. This fix doesn't currently affect the
13262 behavior of Tor, because Tor workers never indicates fatal error
13263 or shutdown except in the unit tests. Fixes bug 16868; bugfix
13265 - Unblock threads before releasing the work queue mutex to ensure
13266 predictable scheduling behavior. Fixes bug 16644; bugfix
13269 o Code simplification and refactoring:
13270 - Change the function that's called when we need to retry all
13271 downloads so that it only reschedules the downloads to happen
13272 immediately, rather than launching them all at once itself. This
13273 further simplifies Tor's callgraph.
13274 - Move some format-parsing functions out of crypto.c and
13275 crypto_curve25519.c into crypto_format.c and/or util_format.c.
13276 - Move the client-only parts of init_keys() into a separate
13277 function. Closes ticket 16763.
13278 - Simplify the microdesc_free() implementation so that it no longer
13279 appears (to code analysis tools) to potentially invoke a huge
13280 suite of other microdesc functions.
13281 - Simply the control graph further by deferring the inner body of
13282 directory_all_unreachable() into a callback. Closes ticket 16762.
13283 - Treat the loss of an owning controller as equivalent to a SIGTERM
13284 signal. This removes a tiny amount of duplicated code, and
13285 simplifies our callgraph. Closes ticket 16788.
13286 - When generating an event to send to the controller, we no longer
13287 put the event over the network immediately. Instead, we queue
13288 these events, and use a Libevent callback to deliver them. This
13289 change simplifies Tor's callgraph by reducing the number of
13290 functions from which all other Tor functions are reachable. Closes
13292 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13293 that try to scan or compile every file on Unix won't decide that
13295 - Remove the unused "nulterminate" argument from buf_pullup().
13298 - Recommend a 40 GB example AccountingMax in torrc.sample rather
13299 than a 4 GB max. Closes ticket 16742.
13300 - Include the TUNING document in our source tarball. It is referred
13301 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13305 - The internal pure-C tor-fw-helper tool is now removed from the Tor
13306 distribution, in favor of the pure-Go clone available from
13307 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
13308 used by the C tor-fw-helper are not, in our opinion, very
13309 confidence- inspiring in their secure-programming techniques.
13310 Closes ticket 13338.
13311 - Remove the code that would try to aggressively flush controller
13312 connections while writing to them. This code was introduced in
13313 0.1.2.7-alpha, in order to keep output buffers from exceeding
13314 their limits. But there is no longer a maximum output buffer size,
13315 and flushing data in this way caused some undesirable recursions
13316 in our call graph. Closes ticket 16480.
13319 - Make "bridges+hs" the default test network. This tests almost all
13320 tor functionality during make test-network, while allowing tests
13321 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
13322 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
13323 (chutney). Patches by "teor".
13324 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
13325 by-side in the same parent directory. Closes ticket 16903. Patch
13327 - Use environment variables rather than autoconf substitutions to
13328 send variables from the build system to the test scripts. This
13329 change should be easier to maintain, and cause 'make distcheck' to
13330 work better than before. Fixes bug 17148.
13331 - Add a new set of callgraph analysis scripts that use clang to
13332 produce a list of which Tor functions are reachable from which
13333 other Tor functions. We're planning to use these to help simplify
13334 our code structure by identifying illogical dependencies.
13335 - Add new 'test-full' and 'test-full-online' targets to run all
13336 tests, including integration tests with stem and chutney.
13337 - Make the test-workqueue test work on Windows by initializing the
13338 network before we begin.
13339 - New make target (make test-network-all) to run multiple applicable
13340 chutney test cases. Patch from Teor; closes 16953.
13341 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
13342 functions in dns.c. Implements a portion of ticket 16831.
13343 - When building Tor with testing coverage enabled, run Chutney tests
13344 (if any) using the 'tor-cov' coverage binary.
13345 - When running test-network or test-stem, check for the absence of
13346 stem/chutney before doing any build operations.
13349 Changes in version 0.2.7.2-alpha - 2015-07-27
13350 This, the second alpha in the Tor 0.2.7 series, has a number of new
13351 features, including a way to manually pick the number of introduction
13352 points for hidden services, and the much stronger Ed25519 signing key
13353 algorithm for regular Tor relays (including support for encrypted
13354 offline identity keys in the new algorithm).
13356 Support for Ed25519 on relays is currently limited to signing router
13357 descriptors; later alphas in this series will extend Ed25519 key
13358 support to more parts of the Tor protocol.
13360 o Major features (Ed25519 identity keys, Proposal 220):
13361 - All relays now maintain a stronger identity key, using the Ed25519
13362 elliptic curve signature format. This master key is designed so
13363 that it can be kept offline. Relays also generate an online
13364 signing key, and a set of other Ed25519 keys and certificates.
13365 These are all automatically regenerated and rotated as needed.
13366 Implements part of ticket 12498.
13367 - Directory authorities now vote on Ed25519 identity keys along with
13368 RSA1024 keys. Implements part of ticket 12498.
13369 - Directory authorities track which Ed25519 identity keys have been
13370 used with which RSA1024 identity keys, and do not allow them to
13371 vary freely. Implements part of ticket 12498.
13372 - Microdescriptors now include Ed25519 identity keys. Implements
13373 part of ticket 12498.
13374 - Add support for offline encrypted Ed25519 master keys. To use this
13375 feature on your tor relay, run "tor --keygen" to make a new master
13376 key (or to make a new signing key if you already have a master
13377 key). Closes ticket 13642.
13379 o Major features (Hidden services):
13380 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13381 specify a fixed number of introduction points. Its maximum value
13382 is 10 and default is 3. Using this option can increase a hidden
13383 service's reliability under load, at the cost of making it more
13384 visible that the hidden service is facing extra load. Closes
13386 - Remove the adaptive algorithm for choosing the number of
13387 introduction points, which used to change the number of
13388 introduction points (poorly) depending on the number of
13389 connections the HS sees. Closes ticket 4862.
13391 o Major features (onion key cross-certification):
13392 - Relay descriptors now include signatures of their own identity
13393 keys, made using the TAP and ntor onion keys. These signatures
13394 allow relays to prove ownership of their own onion keys. Because
13395 of this change, microdescriptors will no longer need to include
13396 RSA identity keys. Implements proposal 228; closes ticket 12499.
13398 o Major features (performance):
13399 - Improve the runtime speed of Ed25519 operations by using the
13400 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13401 Implements ticket 16467.
13402 - Improve the runtime speed of the ntor handshake by using an
13403 optimized curve25519 basepoint scalarmult implementation from the
13404 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13405 ideas by Adam Langley. Implements ticket 9663.
13407 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13408 - Properly separate out each SOCKSPort when applying stream
13409 isolation. The error occurred because each port's session group
13410 was being overwritten by a default value when the listener
13411 connection was initialized. Fixes bug 16247; bugfix on
13412 0.2.6.3-alpha. Patch by "jojelino".
13414 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13415 - Stop refusing to store updated hidden service descriptors on a
13416 client. This reverts commit 9407040c59218 (which indeed fixed bug
13417 14219, but introduced a major hidden service reachability
13418 regression detailed in bug 16381). This is a temporary fix since
13419 we can live with the minor issue in bug 14219 (it just results in
13420 some load on the network) but the regression of 16381 is too much
13421 of a setback. First-round fix for bug 16381; bugfix
13424 o Major bugfixes (hidden services):
13425 - When cannibalizing a circuit for an introduction point, always
13426 extend to the chosen exit node (creating a 4 hop circuit).
13427 Previously Tor would use the current circuit exit node, which
13428 changed the original choice of introduction point, and could cause
13429 the hidden service to skip excluded introduction points or
13430 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13433 o Major bugfixes (open file limit):
13434 - The open file limit wasn't checked before calling
13435 tor_accept_socket_nonblocking(), which would make Tor exceed the
13436 limit. Now, before opening a new socket, Tor validates the open
13437 file limit just before, and if the max has been reached, return an
13438 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13440 o Major bugfixes (stability, also in 0.2.6.10):
13441 - Stop crashing with an assertion failure when parsing certain kinds
13442 of malformed or truncated microdescriptors. Fixes bug 16400;
13443 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13444 by "cypherpunks_backup".
13445 - Stop random client-side assertion failures that could occur when
13446 connecting to a busy hidden service, or connecting to a hidden
13447 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13450 o Minor features (directory authorities, security, also in 0.2.6.9):
13451 - The HSDir flag given by authorities now requires the Stable flag.
13452 For the current network, this results in going from 2887 to 2806
13453 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13454 attack by raising the effort for a relay to become Stable to
13455 require at the very least 7 days, while maintaining the 96 hours
13456 uptime requirement for HSDir. Implements ticket 8243.
13458 o Minor features (client):
13459 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13460 character '_' to appear, in order to cope with domains observed in
13461 the wild that are serving non-RFC compliant records. Resolves
13463 - Relax the validation done to hostnames in SOCKS5 requests, and
13464 allow a single trailing '.' to cope with clients that pass FQDNs
13465 using that syntax to explicitly indicate that the domain name is
13466 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13467 - Add GroupWritable and WorldWritable options to unix-socket based
13468 SocksPort and ControlPort options. These options apply to a single
13469 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13472 o Minor features (control protocol):
13473 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13474 the control protocol. Resolves ticket 15358.
13476 o Minor features (directory authorities):
13477 - Directory authorities no longer vote against the "Fast", "Stable",
13478 and "HSDir" flags just because they were going to vote against
13479 "Running": if the consensus turns out to be that the router was
13480 running, then the authority's vote should count. Patch from Peter
13481 Retzlaff; closes issue 8712.
13483 o Minor features (geoip, also in 0.2.6.10):
13484 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13485 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13487 o Minor features (hidden services):
13488 - Add the new options "HiddenServiceMaxStreams" and
13489 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13490 limit the maximum number of simultaneous streams per circuit, and
13491 optionally tear down the circuit when the limit is exceeded. Part
13494 o Minor features (portability):
13495 - Use C99 variadic macros when the compiler is not GCC. This avoids
13496 failing compilations on MSVC, and fixes a log-file-based race
13497 condition in our old workarounds. Original patch from Gisle Vanem.
13499 o Minor bugfixes (compilation, also in 0.2.6.9):
13500 - Build with --enable-systemd correctly when libsystemd is
13501 installed, but systemd is not. Fixes bug 16164; bugfix on
13502 0.2.6.3-alpha. Patch from Peter Palfrader.
13504 o Minor bugfixes (controller):
13505 - Add the descriptor ID in each HS_DESC control event. It was
13506 missing, but specified in control-spec.txt. Fixes bug 15881;
13507 bugfix on 0.2.5.2-alpha.
13509 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13510 - Check for failures from crypto_early_init, and refuse to continue.
13511 A previous typo meant that we could keep going with an
13512 uninitialized crypto library, and would have OpenSSL initialize
13513 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13514 when implementing ticket 4900. Patch by "teor".
13516 o Minor bugfixes (hidden services):
13517 - Fix a crash when reloading configuration while at least one
13518 configured and one ephemeral hidden service exists. Fixes bug
13519 16060; bugfix on 0.2.7.1-alpha.
13520 - Avoid crashing with a double-free bug when we create an ephemeral
13521 hidden service but adding it fails for some reason. Fixes bug
13522 16228; bugfix on 0.2.7.1-alpha.
13524 o Minor bugfixes (Linux seccomp2 sandbox):
13525 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13526 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13528 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13529 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13530 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13531 on 0.2.6.3-alpha. Patch from "teor".
13533 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13534 - Fix sandboxing to work when running as a relay, by allowing the
13535 renaming of secret_id_key, and allowing the eventfd2 and futex
13536 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13538 - Allow systemd connections to work with the Linux seccomp2 sandbox
13539 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13542 o Minor bugfixes (relay):
13543 - Fix a rarely-encountered memory leak when failing to initialize
13544 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13545 from "cypherpunks".
13547 o Minor bugfixes (systemd):
13548 - Fix an accidental formatting error that broke the systemd
13549 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
13550 - Tor's systemd unit file no longer contains extraneous spaces.
13551 These spaces would sometimes confuse tools like deb-systemd-
13552 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13554 o Minor bugfixes (tests):
13555 - Use the configured Python executable when running test-stem-full.
13556 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
13558 o Minor bugfixes (tests, also in 0.2.6.9):
13559 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13560 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13562 o Minor bugfixes (threads, comments):
13563 - Always initialize return value in compute_desc_id in rendcommon.c
13564 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13565 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
13566 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13567 - Remove undefined directive-in-macro in test_util_writepid clang
13568 3.7 complains that using a preprocessor directive inside a macro
13569 invocation in test_util_writepid in test_util.c is undefined.
13570 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13572 o Code simplification and refactoring:
13573 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13574 to ensure they remain consistent and visible everywhere.
13575 - Remove some vestigial workarounds for the MSVC6 compiler. We
13576 haven't supported that in ages.
13577 - The link authentication code has been refactored for better
13578 testability and reliability. It now uses code generated with the
13579 "trunnel" binary encoding generator, to reduce the risk of bugs
13580 due to programmer error. Done as part of ticket 12498.
13583 - Include a specific and (hopefully) accurate documentation of the
13584 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13585 of interest to people writing programs to parse or generate torrc
13586 files. This document is not a commitment to long-term
13587 compatibility; some aspects of the current format are a bit
13588 ridiculous. Closes ticket 2325.
13590 o Removed features:
13591 - Tor no longer supports copies of OpenSSL that are missing support
13592 for Elliptic Curve Cryptography. (We began using ECC when
13593 available in 0.2.4.8-alpha, for more safe and efficient key
13594 negotiation.) In particular, support for at least one of P256 or
13595 P224 is now required, with manual configuration needed if only
13596 P224 is available. Resolves ticket 16140.
13597 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13598 on an operating system that has not upgraded to OpenSSL 1.0 or
13599 later, and you compile Tor from source, you will need to install a
13600 more recent OpenSSL to link Tor against.) These versions of
13601 OpenSSL are still supported by the OpenSSL, but the numerous
13602 cryptographic improvements in later OpenSSL releases makes them a
13603 clear choice. Resolves ticket 16034.
13604 - Remove the HidServDirectoryV2 option. Now all relays offer to
13605 store hidden service descriptors. Related to 16543.
13606 - Remove the VoteOnHidServDirectoriesV2 option, since all
13607 authorities have long set it to 1. Closes ticket 16543.
13610 - Document use of coverity, clang static analyzer, and clang dynamic
13611 undefined behavior and address sanitizers in doc/HACKING. Include
13612 detailed usage instructions in the blacklist. Patch by "teor".
13613 Closes ticket 15817.
13614 - The link authentication protocol code now has extensive tests.
13615 - The relay descriptor signature testing code now has
13617 - The test_workqueue program now runs faster, and is enabled by
13618 default as a part of "make check".
13619 - Now that OpenSSL has its own scrypt implementation, add an unit
13620 test that checks for interoperability between libscrypt_scrypt()
13621 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
13622 and rely on EVP_PBE_scrypt() whenever possible. Resolves
13626 Changes in version 0.2.6.10 - 2015-07-12
13627 Tor version 0.2.6.10 fixes some significant stability and hidden
13628 service client bugs, bulletproofs the cryptography init process, and
13629 fixes a bug when using the sandbox code with some older versions of
13630 Linux. Everyone running an older version, especially an older version
13631 of 0.2.6, should upgrade.
13633 o Major bugfixes (hidden service clients, stability):
13634 - Stop refusing to store updated hidden service descriptors on a
13635 client. This reverts commit 9407040c59218 (which indeed fixed bug
13636 14219, but introduced a major hidden service reachability
13637 regression detailed in bug 16381). This is a temporary fix since
13638 we can live with the minor issue in bug 14219 (it just results in
13639 some load on the network) but the regression of 16381 is too much
13640 of a setback. First-round fix for bug 16381; bugfix
13643 o Major bugfixes (stability):
13644 - Stop crashing with an assertion failure when parsing certain kinds
13645 of malformed or truncated microdescriptors. Fixes bug 16400;
13646 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13647 by "cypherpunks_backup".
13648 - Stop random client-side assertion failures that could occur when
13649 connecting to a busy hidden service, or connecting to a hidden
13650 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13653 o Minor features (geoip):
13654 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13655 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13657 o Minor bugfixes (crypto error-handling):
13658 - Check for failures from crypto_early_init, and refuse to continue.
13659 A previous typo meant that we could keep going with an
13660 uninitialized crypto library, and would have OpenSSL initialize
13661 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13662 when implementing ticket 4900. Patch by "teor".
13664 o Minor bugfixes (Linux seccomp2 sandbox):
13665 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13666 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13667 on 0.2.6.3-alpha. Patch from "teor".
13670 Changes in version 0.2.6.9 - 2015-06-11
13671 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
13672 requirements for receiving an HSDir flag, and addresses some other small
13673 bugs in the systemd and sandbox code. Clients using circuit isolation
13674 should upgrade; all directory authorities should upgrade.
13676 o Major bugfixes (client-side privacy):
13677 - Properly separate out each SOCKSPort when applying stream
13678 isolation. The error occurred because each port's session group was
13679 being overwritten by a default value when the listener connection
13680 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
13683 o Minor feature (directory authorities, security):
13684 - The HSDir flag given by authorities now requires the Stable flag.
13685 For the current network, this results in going from 2887 to 2806
13686 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13687 attack by raising the effort for a relay to become Stable which
13688 takes at the very least 7 days to do so and by keeping the 96
13689 hours uptime requirement for HSDir. Implements ticket 8243.
13691 o Minor bugfixes (compilation):
13692 - Build with --enable-systemd correctly when libsystemd is
13693 installed, but systemd is not. Fixes bug 16164; bugfix on
13694 0.2.6.3-alpha. Patch from Peter Palfrader.
13696 o Minor bugfixes (Linux seccomp2 sandbox):
13697 - Fix sandboxing to work when running as a relaymby renaming of
13698 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
13699 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
13700 - Allow systemd connections to work with the Linux seccomp2 sandbox
13701 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13704 o Minor bugfixes (tests):
13705 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13706 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13709 Changes in version 0.2.6.8 - 2015-05-21
13710 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
13711 fixes an authority-side bug in assigning the HSDir flag. All directory
13712 authorities should upgrade.
13714 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13715 - Revert commit that made directory authorities assign the HSDir
13716 flag to relays without a DirPort; this was bad because such relays
13717 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13720 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13721 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13722 a client authorized hidden service. Fixes bug 15823; bugfix
13725 o Minor features (geoip):
13726 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13727 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13731 Changes in version 0.2.7.1-alpha - 2015-05-12
13732 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13733 includes numerous small features and bugfixes against previous Tor
13734 versions, and numerous small infrastructure improvements. The most
13735 notable features are several new ways for controllers to interact with
13736 the hidden services subsystem.
13738 o New system requirements:
13739 - Tor no longer includes workarounds to support Libevent versions
13740 before 1.3e. Libevent 2.0 or later is recommended. Closes
13743 o Major features (controller):
13744 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13745 and management of hidden services via the controller. Closes
13747 - New "GETINFO onions/current" and "GETINFO onions/detached"
13748 commands to get information about hidden services created via the
13749 controller. Part of ticket 6411.
13750 - New HSFETCH command to launch a request for a hidden service
13751 descriptor. Closes ticket 14847.
13752 - New HSPOST command to upload a hidden service descriptor. Closes
13753 ticket 3523. Patch by "DonnchaC".
13755 o Major bugfixes (hidden services):
13756 - Revert commit that made directory authorities assign the HSDir
13757 flag to relays without a DirPort; this was bad because such relays
13758 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13761 o Minor features (clock-jump tolerance):
13762 - Recover better when our clock jumps back many hours, like might
13763 happen for Tails or Whonix users who start with a very wrong
13764 hardware clock, use Tor to discover a more accurate time, and then
13765 fix their clock. Resolves part of ticket 8766.
13767 o Minor features (command-line interface):
13768 - Make --hash-password imply --hush to prevent unnecessary noise.
13769 Closes ticket 15542. Patch from "cypherpunks".
13770 - Print a warning whenever we find a relative file path being used
13771 as torrc option. Resolves issue 14018.
13773 o Minor features (controller):
13774 - Add DirAuthority lines for default directory authorities to the
13775 output of the "GETINFO config/defaults" command if not already
13776 present. Implements ticket 14840.
13777 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13778 retrieve items from the client's hidden service descriptor cache.
13779 Closes ticket 14845.
13780 - Implement a new controller command "GETINFO status/fresh-relay-
13781 descs" to fetch a descriptor/extrainfo pair that was generated on
13782 demand just for the controller's use. Implements ticket 14784.
13784 o Minor features (DoS-resistance):
13785 - Make it harder for attackers to overload hidden services with
13786 introductions, by blocking multiple introduction requests on the
13787 same circuit. Resolves ticket 15515.
13789 o Minor features (geoip):
13790 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13791 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13794 o Minor features (HS popularity countermeasure):
13795 - To avoid leaking HS popularity, don't cycle the introduction point
13796 when we've handled a fixed number of INTRODUCE2 cells but instead
13797 cycle it when a random number of introductions is reached, thus
13798 making it more difficult for an attacker to find out the amount of
13799 clients that have used the introduction point for a specific HS.
13800 Closes ticket 15745.
13802 o Minor features (logging):
13803 - Include the Tor version in all LD_BUG log messages, since people
13804 tend to cut and paste those into the bugtracker. Implements
13807 o Minor features (pluggable transports):
13808 - When launching managed pluggable transports on Linux systems,
13809 attempt to have the kernel deliver a SIGTERM on tor exit if the
13810 pluggable transport process is still running. Resolves
13812 - When launching managed pluggable transports, setup a valid open
13813 stdin in the child process that can be used to detect if tor has
13814 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13815 can be used by implementations to detect this new behavior.
13816 Resolves ticket 15435.
13818 o Minor features (testing):
13819 - Add a test to verify that the compiler does not eliminate our
13820 memwipe() implementation. Closes ticket 15377.
13821 - Add make rule `check-changes` to verify the format of changes
13822 files. Closes ticket 15180.
13823 - Add unit tests for control_event_is_interesting(). Add a compile-
13824 time check that the number of events doesn't exceed the capacity
13825 of control_event_t.event_mask. Closes ticket 15431, checks for
13826 bugs similar to 13085. Patch by "teor".
13827 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13828 - Integrate the ntor, backtrace, and zero-length keys tests into the
13829 automake test suite. Closes ticket 15344.
13830 - Remove assertions during builds to determine Tor's test coverage.
13831 We don't want to trigger these even in assertions, so including
13832 them artificially makes our branch coverage look worse than it is.
13833 This patch provides the new test-stem-full and coverage-html-full
13834 configure options. Implements ticket 15400.
13836 o Minor bugfixes (build):
13837 - Improve out-of-tree builds by making non-standard rules work and
13838 clean up additional files and directories. Fixes bug 15053; bugfix
13841 o Minor bugfixes (command-line interface):
13842 - When "--quiet" is provided along with "--validate-config", do not
13843 write anything to stdout on success. Fixes bug 14994; bugfix
13845 - When complaining about bad arguments to "--dump-config", use
13846 stderr, not stdout.
13848 o Minor bugfixes (configuration, unit tests):
13849 - Only add the default fallback directories when the DirAuthorities,
13850 AlternateDirAuthority, and FallbackDir directory config options
13851 are set to their defaults. The default fallback directory list is
13852 currently empty, this fix will only change tor's behavior when it
13853 has default fallback directories. Includes unit tests for
13854 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13855 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13857 o Minor bugfixes (correctness):
13858 - For correctness, avoid modifying a constant string in
13859 handle_control_postdescriptor. Fixes bug 15546; bugfix
13861 - Remove side-effects from tor_assert() calls. This was harmless,
13862 because we never disable assertions, but it is bad style and
13863 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13866 o Minor bugfixes (hidden service):
13867 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13868 a client authorized hidden service. Fixes bug 15823; bugfix
13870 - Remove an extraneous newline character from the end of hidden
13871 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13873 o Minor bugfixes (interface):
13874 - Print usage information for --dump-config when it is used without
13875 an argument. Also, fix the error message to use different wording
13876 and add newline at the end. Fixes bug 15541; bugfix
13879 o Minor bugfixes (logs):
13880 - When building Tor under Clang, do not include an extra set of
13881 parentheses in log messages that include function names. Fixes bug
13882 15269; bugfix on every released version of Tor when compiled with
13883 recent enough Clang.
13885 o Minor bugfixes (network):
13886 - When attempting to use fallback technique for network interface
13887 lookup, disregard loopback and multicast addresses since they are
13888 unsuitable for public communications.
13890 o Minor bugfixes (statistics):
13891 - Disregard the ConnDirectionStatistics torrc options when Tor is
13892 not a relay since in that mode of operation no sensible data is
13893 being collected and because Tor might run into measurement hiccups
13894 when running as a client for some time, then becoming a relay.
13895 Fixes bug 15604; bugfix on 0.2.2.35.
13897 o Minor bugfixes (test networks):
13898 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13899 determine if local/private addresses imply reachability. The
13900 previous fix used TestingTorNetwork, which implies
13901 ExtendAllowPrivateAddresses, but this excluded rare configurations
13902 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13903 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13904 issue discovered by CJ Ess.
13906 o Minor bugfixes (testing):
13907 - Check for matching value in server response in ntor_ref.py. Fixes
13908 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13910 - Set the severity correctly when testing
13911 get_interface_addresses_ifaddrs() and
13912 get_interface_addresses_win32(), so that the tests fail gracefully
13913 instead of triggering an assertion. Fixes bug 15759; bugfix on
13914 0.2.6.3-alpha. Reported by Nicolas Derive.
13916 o Code simplification and refactoring:
13917 - Move the hacky fallback code out of get_interface_address6() into
13918 separate function and get it covered with unit-tests. Resolves
13920 - Refactor hidden service client-side cache lookup to intelligently
13921 report its various failure cases, and disentangle failure cases
13922 involving a lack of introduction points. Closes ticket 14391.
13923 - Use our own Base64 encoder instead of OpenSSL's, to allow more
13924 control over the output. Part of ticket 15652.
13927 - Improve the descriptions of statistics-related torrc options in
13928 the manpage to describe rationale and possible uses cases. Fixes
13930 - Improve the layout and formatting of ./configure --help messages.
13931 Closes ticket 15024. Patch from "cypherpunks".
13932 - Standardize on the term "server descriptor" in the manual page.
13933 Previously, we had used "router descriptor", "server descriptor",
13934 and "relay descriptor" interchangeably. Part of ticket 14987.
13937 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
13938 and always use the internal Base64 decoder. The internal decoder
13939 has been part of tor since 0.2.0.10-alpha, and no one should
13940 be using the OpenSSL one. Part of ticket 15652.
13941 - Remove the 'tor_strclear()' function; use memwipe() instead.
13942 Closes ticket 14922.
13944 o Removed features:
13945 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
13946 fingerprinting we now recommend pluggable transports; for forward-
13947 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
13948 - Remove the undocumented "--digests" command-line option. It
13949 complicated our build process, caused subtle build issues on
13950 multiple platforms, and is now redundant since we started
13951 including git version identifiers. Closes ticket 14742.
13952 - Tor no longer contains checks for ancient directory cache versions
13953 that didn't know about microdescriptors.
13954 - Tor no longer contains workarounds for stat files generated by
13955 super-old versions of Tor that didn't choose guards sensibly.
13958 Changes in version 0.2.4.27 - 2015-04-06
13959 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
13960 could be used by an attacker to crash hidden services, or crash clients
13961 visiting hidden services. Hidden services should upgrade as soon as
13962 possible; clients should upgrade whenever packages become available.
13964 This release also backports a simple improvement to make hidden
13965 services a bit less vulnerable to denial-of-service attacks.
13967 o Major bugfixes (security, hidden service):
13968 - Fix an issue that would allow a malicious client to trigger an
13969 assertion failure and halt a hidden service. Fixes bug 15600;
13970 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13971 - Fix a bug that could cause a client to crash with an assertion
13972 failure when parsing a malformed hidden service descriptor. Fixes
13973 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13975 o Minor features (DoS-resistance, hidden service):
13976 - Introduction points no longer allow multiple INTRODUCE1 cells to
13977 arrive on the same circuit. This should make it more expensive for
13978 attackers to overwhelm hidden services with introductions.
13979 Resolves ticket 15515.
13982 Changes in version 0.2.5.12 - 2015-04-06
13983 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
13984 could be used by an attacker to crash hidden services, or crash clients
13985 visiting hidden services. Hidden services should upgrade as soon as
13986 possible; clients should upgrade whenever packages become available.
13988 This release also backports a simple improvement to make hidden
13989 services a bit less vulnerable to denial-of-service attacks.
13991 o Major bugfixes (security, hidden service):
13992 - Fix an issue that would allow a malicious client to trigger an
13993 assertion failure and halt a hidden service. Fixes bug 15600;
13994 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
13995 - Fix a bug that could cause a client to crash with an assertion
13996 failure when parsing a malformed hidden service descriptor. Fixes
13997 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
13999 o Minor features (DoS-resistance, hidden service):
14000 - Introduction points no longer allow multiple INTRODUCE1 cells to
14001 arrive on the same circuit. This should make it more expensive for
14002 attackers to overwhelm hidden services with introductions.
14003 Resolves ticket 15515.
14006 Changes in version 0.2.6.7 - 2015-04-06
14007 Tor 0.2.6.7 fixes two security issues that could be used by an
14008 attacker to crash hidden services, or crash clients visiting hidden
14009 services. Hidden services should upgrade as soon as possible; clients
14010 should upgrade whenever packages become available.
14012 This release also contains two simple improvements to make hidden
14013 services a bit less vulnerable to denial-of-service attacks.
14015 o Major bugfixes (security, hidden service):
14016 - Fix an issue that would allow a malicious client to trigger an
14017 assertion failure and halt a hidden service. Fixes bug 15600;
14018 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14019 - Fix a bug that could cause a client to crash with an assertion
14020 failure when parsing a malformed hidden service descriptor. Fixes
14021 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14023 o Minor features (DoS-resistance, hidden service):
14024 - Introduction points no longer allow multiple INTRODUCE1 cells to
14025 arrive on the same circuit. This should make it more expensive for
14026 attackers to overwhelm hidden services with introductions.
14027 Resolves ticket 15515.
14028 - Decrease the amount of reattempts that a hidden service performs
14029 when its rendezvous circuits fail. This reduces the computational
14030 cost for running a hidden service under heavy load. Resolves
14034 Changes in version 0.2.6.6 - 2015-03-24
14035 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
14037 It adds numerous safety, security, correctness, and performance
14038 improvements. Client programs can be configured to use more kinds of
14039 sockets, AutomapHosts works better, the multithreading backend is
14040 improved, cell transmission is refactored, test coverage is much
14041 higher, more denial-of-service attacks are handled, guard selection is
14042 improved to handle long-term guards better, pluggable transports
14043 should work a bit better, and some annoying hidden service performance
14044 bugs should be addressed.
14046 o Minor bugfixes (portability):
14047 - Use the correct datatype in the SipHash-2-4 function to prevent
14048 compilers from assuming any sort of alignment. Fixes bug 15436;
14049 bugfix on 0.2.5.3-alpha.
14051 Changes in version 0.2.6.5-rc - 2015-03-18
14052 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
14053 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
14055 o Major bugfixes (client):
14056 - Avoid crashing when making certain configuration option changes on
14057 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
14060 o Major bugfixes (pluggable transports):
14061 - Initialize the extended OR Port authentication cookie before
14062 launching pluggable transports. This prevents a race condition
14063 that occurred when server-side pluggable transports would cache the
14064 authentication cookie before it has been (re)generated. Fixes bug
14065 15240; bugfix on 0.2.5.1-alpha.
14067 o Major bugfixes (portability):
14068 - Do not crash on startup when running on Solaris. Fixes a bug
14069 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
14072 o Minor features (heartbeat):
14073 - On relays, report how many connections we negotiated using each
14074 version of the Tor link protocols. This information will let us
14075 know if removing support for very old versions of the Tor
14076 protocols is harming the network. Closes ticket 15212.
14078 o Code simplification and refactoring:
14079 - Refactor main loop to extract the 'loop' part. This makes it
14080 easier to run Tor under Shadow. Closes ticket 15176.
14083 Changes in version 0.2.5.11 - 2015-03-17
14084 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
14086 It backports several bugfixes from the 0.2.6 branch, including a
14087 couple of medium-level security fixes for relays and exit nodes.
14088 It also updates the list of directory authorities.
14090 o Directory authority changes:
14091 - Remove turtles as a directory authority.
14092 - Add longclaw as a new (v3) directory authority. This implements
14093 ticket 13296. This keeps the directory authority count at 9.
14094 - The directory authority Faravahar has a new IP address. This
14095 closes ticket 14487.
14097 o Major bugfixes (crash, OSX, security):
14098 - Fix a remote denial-of-service opportunity caused by a bug in
14099 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14102 o Major bugfixes (relay, stability, possible security):
14103 - Fix a bug that could lead to a relay crashing with an assertion
14104 failure if a buffer of exactly the wrong layout was passed to
14105 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14106 0.2.0.10-alpha. Patch from 'cypherpunks'.
14107 - Do not assert if the 'data' pointer on a buffer is advanced to the
14108 very end of the buffer; log a BUG message instead. Only assert if
14109 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14111 o Major bugfixes (exit node stability):
14112 - Fix an assertion failure that could occur under high DNS load.
14113 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14114 diagnosed and fixed by "cypherpunks".
14116 o Major bugfixes (Linux seccomp2 sandbox):
14117 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14118 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14119 0.2.5.1-alpha. Patch from "sanic".
14121 o Minor features (controller):
14122 - New "GETINFO bw-event-cache" to get information about recent
14123 bandwidth events. Closes ticket 14128. Useful for controllers to
14124 get recent bandwidth history after the fix for ticket 13988.
14126 o Minor features (geoip):
14127 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14128 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14131 o Minor bugfixes (client, automapping):
14132 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14133 no value follows the option. Fixes bug 14142; bugfix on
14134 0.2.4.7-alpha. Patch by "teor".
14135 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14136 14195; bugfix on 0.1.0.1-rc.
14138 o Minor bugfixes (compilation):
14139 - Build without warnings with the stock OpenSSL srtp.h header, which
14140 has a duplicate declaration of SSL_get_selected_srtp_profile().
14141 Fixes bug 14220; this is OpenSSL's bug, not ours.
14143 o Minor bugfixes (directory authority):
14144 - Allow directory authorities to fetch more data from one another if
14145 they find themselves missing lots of votes. Previously, they had
14146 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14147 bugfix on 0.1.2.5-alpha.
14148 - Enlarge the buffer to read bwauth generated files to avoid an
14149 issue when parsing the file in dirserv_read_measured_bandwidths().
14150 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14152 o Minor bugfixes (statistics):
14153 - Increase period over which bandwidth observations are aggregated
14154 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14156 o Minor bugfixes (preventative security, C safety):
14157 - When reading a hexadecimal, base-32, or base-64 encoded value from
14158 a string, always overwrite the whole output buffer. This prevents
14159 some bugs where we would look at (but fortunately, not reveal)
14160 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14164 Changes in version 0.2.4.26 - 2015-03-17
14165 Tor 0.2.4.26 includes an updated list of directory authorities. It
14166 also backports a couple of stability and security bugfixes from 0.2.5
14169 o Directory authority changes:
14170 - Remove turtles as a directory authority.
14171 - Add longclaw as a new (v3) directory authority. This implements
14172 ticket 13296. This keeps the directory authority count at 9.
14173 - The directory authority Faravahar has a new IP address. This
14174 closes ticket 14487.
14176 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
14177 - Fix an assertion failure that could occur under high DNS load.
14178 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14179 diagnosed and fixed by "cypherpunks".
14181 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
14182 - Fix a bug that could lead to a relay crashing with an assertion
14183 failure if a buffer of exactly the wrong layout was passed to
14184 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14185 0.2.0.10-alpha. Patch from 'cypherpunks'.
14186 - Do not assert if the 'data' pointer on a buffer is advanced to the
14187 very end of the buffer; log a BUG message instead. Only assert if
14188 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14190 o Minor features (geoip):
14191 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14192 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14195 Changes in version 0.2.6.4-rc - 2015-03-09
14196 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
14197 attacker might be able to use in order to crash certain Tor
14198 directories. It also resolves some minor issues left over from, or
14199 introduced in, Tor 0.2.6.3-alpha or earlier.
14201 o Major bugfixes (crash, OSX, security):
14202 - Fix a remote denial-of-service opportunity caused by a bug in
14203 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14206 o Major bugfixes (relay, stability, possible security):
14207 - Fix a bug that could lead to a relay crashing with an assertion
14208 failure if a buffer of exactly the wrong layout is passed to
14209 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14210 0.2.0.10-alpha. Patch from "cypherpunks".
14211 - Do not assert if the 'data' pointer on a buffer is advanced to the
14212 very end of the buffer; log a BUG message instead. Only assert if
14213 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14215 o Major bugfixes (FreeBSD IPFW transparent proxy):
14216 - Fix address detection with FreeBSD transparent proxies, when
14217 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14220 o Major bugfixes (Linux seccomp2 sandbox):
14221 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
14222 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
14224 - Allow AF_UNIX hidden services to be used with the seccomp2
14225 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
14226 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14227 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14228 0.2.5.1-alpha. Patch from "sanic".
14230 o Minor features (controller):
14231 - Messages about problems in the bootstrap process now include
14232 information about the server we were trying to connect to when we
14233 noticed the problem. Closes ticket 15006.
14235 o Minor features (geoip):
14236 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14237 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14240 o Minor features (logs):
14241 - Quiet some log messages in the heartbeat and at startup. Closes
14244 o Minor bugfixes (certificate handling):
14245 - If an authority operator accidentally makes a signing certificate
14246 with a future publication time, do not discard its real signing
14247 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
14248 - Remove any old authority certificates that have been superseded
14249 for at least two days. Previously, we would keep superseded
14250 certificates until they expired, if they were published close in
14251 time to the certificate that superseded them. Fixes bug 11454;
14252 bugfix on 0.2.1.8-alpha.
14254 o Minor bugfixes (compilation):
14255 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
14257 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
14260 o Minor bugfixes (testing):
14261 - Fix endianness issues in unit test for resolve_my_address() to
14262 have it pass on big endian systems. Fixes bug 14980; bugfix on
14264 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
14265 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
14266 - When running the new 'make test-stem' target, use the configured
14267 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
14268 from "cypherpunks".
14269 - When running the zero-length-keys tests, do not use the default
14270 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
14273 o Directory authority IP change:
14274 - The directory authority Faravahar has a new IP address. This
14275 closes ticket 14487.
14278 - Remove some lingering dead code that once supported mempools.
14279 Mempools were disabled by default in 0.2.5, and removed entirely
14280 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
14284 Changes in version 0.2.6.3-alpha - 2015-02-19
14285 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
14286 the 0.2.6.x series. It introduces support for more kinds of sockets,
14287 makes it harder to accidentally run an exit, improves our
14288 multithreading backend, incorporates several fixes for the
14289 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
14291 If no major regressions or security holes are found in this version,
14292 the next version will be a release candidate.
14294 o Deprecated versions:
14295 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14296 advertise themselves on the network. Closes ticket 13555.
14298 o Major features (security, unix domain sockets):
14299 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14300 applications can reach Tor without having to create AF_INET or
14301 AF_INET6 sockets, meaning they can completely disable their
14302 ability to make non-Tor network connections. To create a socket of
14303 this type, use "SocksPort unix:/path/to/socket". Implements
14305 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14306 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14307 Implements ticket 11485.
14309 o Major features (changed defaults):
14310 - Prevent relay operators from unintentionally running exits: When a
14311 relay is configured as an exit node, we now warn the user unless
14312 the "ExitRelay" option is set to 1. We warn even more loudly if
14313 the relay is configured with the default exit policy, since this
14314 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14315 stops Tor from running as an exit relay. Closes ticket 10067.
14317 o Major features (directory system):
14318 - When downloading server- or microdescriptors from a directory
14319 server, we no longer launch multiple simultaneous requests to the
14320 same server. This reduces load on the directory servers,
14321 especially when directory guards are in use. Closes ticket 9969.
14322 - When downloading server- or microdescriptors over a tunneled
14323 connection, do not limit the length of our requests to what the
14324 Squid proxy is willing to handle. Part of ticket 9969.
14325 - Authorities can now vote on the correct digests and latest
14326 versions for different software packages. This allows packages
14327 that include Tor to use the Tor authority system as a way to get
14328 notified of updates and their correct digests. Implements proposal
14329 227. Closes ticket 10395.
14331 o Major features (guards):
14332 - Introduce the Guardfraction feature to improves load balancing on
14333 guard nodes. Specifically, it aims to reduce the traffic gap that
14334 guard nodes experience when they first get the Guard flag. This is
14335 a required step if we want to increase the guard lifetime to 9
14336 months or greater. Closes ticket 9321.
14338 o Major features (performance):
14339 - Make the CPU worker implementation more efficient by avoiding the
14340 kernel and lengthening pipelines. The original implementation used
14341 sockets to transfer data from the main thread to the workers, and
14342 didn't allow any thread to be assigned more than a single piece of
14343 work at once. The new implementation avoids communications
14344 overhead by making requests in shared memory, avoiding kernel IO
14345 where possible, and keeping more requests in flight at once.
14346 Implements ticket 9682.
14348 o Major features (relay):
14349 - Raise the minimum acceptable configured bandwidth rate for bridges
14350 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14351 20 KiB/sec.) Closes ticket 13822.
14353 o Major bugfixes (exit node stability):
14354 - Fix an assertion failure that could occur under high DNS load.
14355 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14356 diagnosed and fixed by "cypherpunks".
14358 o Major bugfixes (mixed relay-client operation):
14359 - When running as a relay and client at the same time (not
14360 recommended), if we decide not to use a new guard because we want
14361 to retry older guards, only close the locally-originating circuits
14362 passing through that guard. Previously we would close all the
14363 circuits through that guard. Fixes bug 9819; bugfix on
14364 0.2.1.1-alpha. Reported by "skruffy".
14366 o Minor features (build):
14367 - New --disable-system-torrc compile-time option to prevent Tor from
14368 looking for the system-wide torrc or torrc-defaults files.
14369 Resolves ticket 13037.
14371 o Minor features (controller):
14372 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14373 events so controllers can observe circuit isolation inputs. Closes
14375 - ControlPort now supports the unix:/path/to/socket syntax as an
14376 alternative to the ControlSocket option, for consistency with
14377 SocksPort and HiddenServicePort. Closes ticket 14451.
14378 - New "GETINFO bw-event-cache" to get information about recent
14379 bandwidth events. Closes ticket 14128. Useful for controllers to
14380 get recent bandwidth history after the fix for ticket 13988.
14382 o Minor features (Denial of service resistance):
14383 - Count the total number of bytes used storing hidden service
14384 descriptors against the value of MaxMemInQueues. If we're low on
14385 memory, and more than 20% of our memory is used holding hidden
14386 service descriptors, free them until no more than 10% of our
14387 memory holds hidden service descriptors. Free the least recently
14388 fetched descriptors first. Resolves ticket 13806.
14389 - When we have recently been under memory pressure (over 3/4 of
14390 MaxMemInQueues is allocated), then allocate smaller zlib objects
14391 for small requests. Closes ticket 11791.
14393 o Minor features (geoip):
14394 - Update geoip and geoip6 files to the January 7 2015 Maxmind
14395 GeoLite2 Country database.
14397 o Minor features (guard nodes):
14398 - Reduce the time delay before saving guard status to disk from 10
14399 minutes to 30 seconds (or from one hour to 10 minutes if
14400 AvoidDiskWrites is set). Closes ticket 12485.
14402 o Minor features (hidden service):
14403 - Make Sybil attacks against hidden services harder by changing the
14404 minimum time required to get the HSDir flag from 25 hours up to 96
14405 hours. Addresses ticket 14149.
14406 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14407 services to disable the anti-scanning feature introduced in
14408 0.2.6.2-alpha. With this option not set, a connection to an
14409 unlisted port closes the circuit. With this option set, only a
14410 RELAY_DONE cell is sent. Closes ticket 14084.
14412 o Minor features (interface):
14413 - Implement "-f -" command-line option to read torrc configuration
14414 from standard input, if you don't want to store the torrc file in
14415 the file system. Implements feature 13865.
14417 o Minor features (logging):
14418 - Add a count of unique clients to the bridge heartbeat message.
14419 Resolves ticket 6852.
14420 - Suppress "router info incompatible with extra info" message when
14421 reading extrainfo documents from cache. (This message got loud
14422 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14424 - Elevate hidden service authorized-client message from DEBUG to
14425 INFO. Closes ticket 14015.
14427 o Minor features (stability):
14428 - Add assertions in our hash-table iteration code to check for
14429 corrupted values that could cause infinite loops. Closes
14432 o Minor features (systemd):
14433 - Various improvements and modernizations in systemd hardening
14434 support. Closes ticket 13805. Patch from Craig Andrews.
14436 o Minor features (testing networks):
14437 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14438 and the default on a testing network to 2 minutes. Drop the
14439 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14440 keep the default on a testing network at 30 seconds. This reduces
14441 HS bootstrap time to around 25 seconds. Also, change the default
14442 time in test-network.sh to match. Closes ticket 13401. Patch
14444 - Create TestingDirAuthVoteHSDir to correspond to
14445 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14446 HSDir flag for the listed relays regardless of uptime or ORPort
14447 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14448 Partial implementation for ticket 14067. Patch by "teor".
14450 o Minor features (tor2web mode):
14451 - Introduce the config option Tor2webRendezvousPoints, which allows
14452 clients in Tor2webMode to select a specific Rendezvous Point to be
14453 used in HS circuits. This might allow better performance for
14454 Tor2Web nodes. Implements ticket 12844.
14456 o Minor bugfixes (client DNS):
14457 - Report the correct cached DNS expiration times on SOCKS port or in
14458 DNS replies. Previously, we would report everything as "never
14459 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14460 - Avoid a small memory leak when we find a cached answer for a
14461 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14462 side DNS caching is off by default, and is not recommended.) Fixes
14463 bug 14259; bugfix on 0.2.0.1-alpha.
14465 o Minor bugfixes (client, automapping):
14466 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14467 no value follows the option. Fixes bug 14142; bugfix on
14468 0.2.4.7-alpha. Patch by "teor".
14469 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14470 14195; bugfix on 0.1.0.1-rc.
14471 - Prevent changes to other options from removing the wildcard value
14472 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14474 - Allow MapAddress and AutomapHostsOnResolve to work together when
14475 an address is mapped into another address type (like .onion) that
14476 must be automapped at resolve time. Fixes bug 7555; bugfix
14479 o Minor bugfixes (client, bridges):
14480 - When we are using bridges and we had a network connectivity
14481 problem, only retry connecting to our currently configured
14482 bridges, not all bridges we know about and remember using. Fixes
14483 bug 14216; bugfix on 0.2.2.17-alpha.
14485 o Minor bugfixes (client, IPv6):
14486 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14487 flag is not set; and not because the NoIPv4Traffic flag was set.
14488 Previously we'd looked at the NoIPv4Traffic flag for both types of
14489 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14491 o Minor bugfixes (compilation):
14492 - The address of an array in the middle of a structure will always
14493 be non-NULL. clang recognises this and complains. Disable the
14494 tautologous and redundant check to silence this warning. Fixes bug
14495 14001; bugfix on 0.2.1.2-alpha.
14496 - Avoid warnings when building with systemd 209 or later. Fixes bug
14497 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
14498 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14499 Addresses ticket 14188.
14500 - Build without warnings with the stock OpenSSL srtp.h header, which
14501 has a duplicate declaration of SSL_get_selected_srtp_profile().
14502 Fixes bug 14220; this is OpenSSL's bug, not ours.
14503 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14504 is not enabled at compile time. Previously, this code was included
14505 in a disabled state. See discussion on ticket 12844.
14506 - Remove the --disable-threads configure option again. It was
14507 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
14508 14819; bugfix on 0.2.6.2-alpha.
14510 o Minor bugfixes (controller):
14511 - Report "down" in response to the "GETINFO entry-guards" command
14512 when relays are down with an unreachable_since value. Previously,
14513 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14514 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14515 14116; bugfix on 0.2.2.9-alpha.
14516 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
14517 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
14519 o Minor bugfixes (directory authority):
14520 - Allow directory authorities to fetch more data from one another if
14521 they find themselves missing lots of votes. Previously, they had
14522 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14523 bugfix on 0.1.2.5-alpha.
14524 - Do not attempt to download extrainfo documents which we will be
14525 unable to validate with a matching server descriptor. Fixes bug
14526 13762; bugfix on 0.2.0.1-alpha.
14527 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14528 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14529 - Enlarge the buffer to read bwauth generated files to avoid an
14530 issue when parsing the file in dirserv_read_measured_bandwidths().
14531 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14533 o Minor bugfixes (file handling):
14534 - Stop failing when key files are zero-length. Instead, generate new
14535 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14536 on all versions of Tor. Patch by "teor".
14537 - Stop generating a fresh .old RSA onion key file when the .old file
14538 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14539 - Avoid overwriting .old key files with empty key files.
14540 - Skip loading zero-length extrainfo store, router store, stats,
14541 state, and key files.
14542 - Avoid crashing when trying to reload a torrc specified as a
14543 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14546 o Minor bugfixes (hidden services):
14547 - Close the introduction circuit when we have no more usable intro
14548 points, instead of waiting for it to time out. This also ensures
14549 that no follow-up HS descriptor fetch is triggered when the
14550 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14551 - When fetching a hidden service descriptor for a down service that
14552 was recently up, do not keep refetching until we try the same
14553 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14554 - Successfully launch Tor with a nonexistent hidden service
14555 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
14556 14106; bugfix on 0.2.6.2-alpha.
14558 o Minor bugfixes (logging):
14559 - Avoid crashing when there are more log domains than entries in
14560 domain_list. Bugfix on 0.2.3.1-alpha.
14561 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
14563 - Don't log messages to stdout twice when starting up. Fixes bug
14564 13993; bugfix on 0.2.6.1-alpha.
14566 o Minor bugfixes (parsing):
14567 - Stop accepting milliseconds (or other junk) at the end of
14568 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14569 - Support two-number and three-number version numbers correctly, in
14570 case we change the Tor versioning system in the future. Fixes bug
14571 13661; bugfix on 0.0.8pre1.
14573 o Minor bugfixes (path counting):
14574 - When deciding whether the consensus lists any exit nodes, count
14575 the number listed in the consensus, not the number we have
14576 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
14577 - When deciding whether we have any exit nodes, only examine
14578 ExitNodes when the ExitNodes option is actually set. Fixes part of
14579 bug 14918; bugfix on 0.2.6.2-alpha.
14580 - Get rid of redundant and possibly scary warnings that we are
14581 missing directory information while we bootstrap. Fixes part of
14582 bug 14918; bugfix on 0.2.6.2-alpha.
14584 o Minor bugfixes (portability):
14585 - Fix the ioctl()-based network interface lookup code so that it
14586 will work on systems that have variable-length struct ifreq, for
14588 - Fix scheduler compilation on targets where char is unsigned. Fixes
14589 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
14591 o Minor bugfixes (sandbox):
14592 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14593 Previously, glibc would try to write them to /dev/tty, and the
14594 sandbox would trap the call and make Tor exit prematurely. Fixes
14595 bug 14759; bugfix on 0.2.5.1-alpha.
14597 o Minor bugfixes (shutdown):
14598 - When shutting down, always call event_del() on lingering read or
14599 write events before freeing them. Otherwise, we risk double-frees
14600 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
14603 o Minor bugfixes (small memory leaks):
14604 - Avoid leaking memory when using IPv6 virtual address mappings.
14605 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
14608 o Minor bugfixes (statistics):
14609 - Increase period over which bandwidth observations are aggregated
14610 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14612 o Minor bugfixes (systemd support):
14613 - Fix detection and operation of systemd watchdog. Fixes part of bug
14614 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
14615 - Run correctly under systemd with the RunAsDaemon option set. Fixes
14616 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
14617 - Inform the systemd supervisor about more changes in the Tor
14618 process status. Implements part of ticket 14141. Patch from
14620 - Cause the "--disable-systemd" option to actually disable systemd
14621 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
14624 o Minor bugfixes (TLS):
14625 - Check more thoroughly throughout the TLS code for possible
14626 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
14628 o Minor bugfixes (transparent proxy):
14629 - Use getsockname, not getsockopt, to retrieve the address for a
14630 TPROXY-redirected connection. Fixes bug 13796; bugfix
14633 o Code simplification and refactoring:
14634 - Move fields related to isolating and configuring client ports into
14635 a shared structure. Previously, they were duplicated across
14636 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
14637 to copy them correctly had been the cause of at least one bug in
14638 the past. Closes ticket 8546.
14639 - Refactor the get_interface_addresses_raw() doom-function into
14640 multiple smaller and simpler subfunctions. Cover the resulting
14641 subfunctions with unit-tests. Fixes a significant portion of
14643 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
14644 only for version <= 0.2.2.24 which is now deprecated. Closes
14646 - Remove a test for a long-defunct broken version-one
14650 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
14651 for writing the OpenBSD-specific tips. Resolves ticket 13702.
14652 - Make the tor-resolve documentation match its help string and its
14653 options. Resolves part of ticket 14325.
14654 - Log a more useful error message from tor-resolve when failing to
14655 look up a hidden service address. Resolves part of ticket 14325.
14657 o Downgraded warnings:
14658 - Don't warn when we've attempted to contact a relay using the wrong
14659 ntor onion key. Closes ticket 9635.
14661 o Removed features:
14662 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
14663 longer silently accepted as an alias for "ExitNodes".
14664 - The --enable-mempool and --enable-buf-freelists options, which
14665 were originally created to work around bad malloc implementations,
14666 no longer exist. They were off-by-default in 0.2.5. Closes
14670 - Make the checkdir/perms test complete successfully even if the
14671 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
14672 - Test that tor does not fail when key files are zero-length. Check
14673 that tor generates new keys, and overwrites the empty key files.
14674 - Test that tor generates new keys when keys are missing
14675 (existing behavior).
14676 - Test that tor does not overwrite key files that already contain
14677 data (existing behavior). Tests bug 13111. Patch by "teor".
14678 - New "make test-stem" target to run stem integration tests.
14679 Requires that the "STEM_SOURCE_DIR" environment variable be set.
14680 Closes ticket 14107.
14681 - Make the test_cmdline_args.py script work correctly on Windows.
14682 Patch from Gisle Vanem.
14683 - Move the slower unit tests into a new "./src/test/test-slow"
14684 binary that can be run independently of the other tests. Closes
14686 - Avoid undefined behavior when sampling huge values from the
14687 Laplace distribution. This made unittests fail on Raspberry Pi.
14688 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
14691 Changes in version 0.2.6.2-alpha - 2014-12-31
14692 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
14693 It introduces a major new backend for deciding when to send cells on
14694 channels, which should lead down the road to big performance
14695 increases. It contains security and statistics features for better
14696 work on hidden services, and numerous bugfixes.
14698 This release contains many new unit tests, along with major
14699 performance improvements for running testing networks using Chutney.
14700 Thanks to a series of patches contributed by "teor", testing networks
14701 should now bootstrap in seconds, rather than minutes.
14703 o Major features (relay, infrastructure):
14704 - Complete revision of the code that relays use to decide which cell
14705 to send next. Formerly, we selected the best circuit to write on
14706 each channel, but we didn't select among channels in any
14707 sophisticated way. Now, we choose the best circuits globally from
14708 among those whose channels are ready to deliver traffic.
14710 This patch implements a new inter-cmux comparison API, a global
14711 high/low watermark mechanism and a global scheduler loop for
14712 transmission prioritization across all channels as well as among
14713 circuits on one channel. This schedule is currently tuned to
14714 (tolerantly) avoid making changes in network performance, but it
14715 should form the basis for major circuit performance increases in
14716 the future. Code by Andrea; tuning by Rob Jansen; implements
14719 o Major features (hidden services):
14720 - Make HS port scanning more difficult by immediately closing the
14721 circuit when a user attempts to connect to a nonexistent port.
14722 Closes ticket 13667.
14723 - Add a HiddenServiceStatistics option that allows Tor relays to
14724 gather and publish statistics about the overall size and volume of
14725 hidden service usage. Specifically, when this option is turned on,
14726 an HSDir will publish an approximate number of hidden services
14727 that have published descriptors to it the past 24 hours. Also, if
14728 a relay has acted as a hidden service rendezvous point, it will
14729 publish the approximate amount of rendezvous cells it has relayed
14730 the past 24 hours. The statistics themselves are obfuscated so
14731 that the exact values cannot be derived. For more details see
14732 proposal 238, "Better hidden service stats from Tor relays". This
14733 feature is currently disabled by default. Implements feature 13192.
14735 o Major bugfixes (client, automap):
14736 - Repair automapping with IPv6 addresses. This automapping should
14737 have worked previously, but one piece of debugging code that we
14738 inserted to detect a regression actually caused the regression to
14739 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14740 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14743 o Major bugfixes (hidden services):
14744 - When closing an introduction circuit that was opened in parallel
14745 with others, don't mark the introduction point as unreachable.
14746 Previously, the first successful connection to an introduction
14747 point would make the other introduction points get marked as
14748 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14750 o Directory authority changes:
14751 - Remove turtles as a directory authority.
14752 - Add longclaw as a new (v3) directory authority. This implements
14753 ticket 13296. This keeps the directory authority count at 9.
14755 o Major removed features:
14756 - Tor clients no longer support connecting to hidden services
14757 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14758 option has been removed. (There shouldn't be any hidden services
14759 running these versions on the network.) Closes ticket 7803.
14761 o Minor features (client):
14762 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14763 is enabled, reject requests with IP addresses as hostnames.
14764 Resolves ticket 13315.
14766 o Minor features (controller):
14767 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14768 write an unscheduled heartbeat message to the log. Implements
14771 o Minor features (geoip):
14772 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14775 o Minor features (hidden services):
14776 - When re-enabling the network, don't try to build introduction
14777 circuits until we have successfully built a circuit. This makes
14778 hidden services come up faster when the network is re-enabled.
14779 Patch from "akwizgran". Closes ticket 13447.
14780 - When we fail to retrieve a hidden service descriptor, send the
14781 controller an "HS_DESC FAILED" controller event. Implements
14783 - New HiddenServiceDirGroupReadable option to cause hidden service
14784 directories and hostname files to be created group-readable. Patch
14785 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14787 o Minor features (systemd):
14788 - Where supported, when running with systemd, report successful
14789 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14790 - When running with systemd, support systemd watchdog messages. Part
14791 of ticket 11016. Patch by Michael Scherer.
14793 o Minor features (transparent proxy):
14794 - Update the transparent proxy option checks to allow for both ipfw
14795 and pf on OS X. Closes ticket 14002.
14796 - Use the correct option when using IPv6 with transparent proxy
14797 support on Linux. Resolves 13808. Patch by Francisco Blas
14800 o Minor bugfixes (preventative security, C safety):
14801 - When reading a hexadecimal, base-32, or base-64 encoded value from
14802 a string, always overwrite the whole output buffer. This prevents
14803 some bugs where we would look at (but fortunately, not reveal)
14804 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14806 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14807 just the part that's used. This makes it harder for data leak bugs
14808 to occur in the event of other programming failures. Resolves
14811 o Minor bugfixes (client, microdescriptors):
14812 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14813 computing which microdescriptors to download. This keeps us from
14814 erroneous download behavior if two microdescriptor digests ever
14815 have the same first 160 bits. Fixes part of bug 13399; bugfix
14817 - Reset a router's status if its microdescriptor digest changes,
14818 even if the first 160 bits remain the same. Fixes part of bug
14819 13399; bugfix on 0.2.3.1-alpha.
14821 o Minor bugfixes (compilation):
14822 - Silence clang warnings under --enable-expensive-hardening,
14823 including implicit truncation of 64 bit values to 32 bit, const
14824 char assignment to self, tautological compare, and additional
14825 parentheses around equality tests. Fixes bug 13577; bugfix
14827 - Fix a clang warning about checking whether an address in the
14828 middle of a structure is NULL. Fixes bug 14001; bugfix
14831 o Minor bugfixes (hidden services):
14832 - Correctly send a controller event when we find that a rendezvous
14833 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14834 - Pre-check directory permissions for new hidden-services to avoid
14835 at least one case of "Bug: Acting on config options left us in a
14836 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14837 - When adding a new hidden service (for example, via SETCONF), Tor
14838 no longer congratulates the user for running a relay. Fixes bug
14839 13941; bugfix on 0.2.6.1-alpha.
14840 - When fetching hidden service descriptors, we now check not only
14841 for whether we got the hidden service we had in mind, but also
14842 whether we got the particular descriptors we wanted. This prevents
14843 a class of inefficient but annoying DoS attacks by hidden service
14844 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14847 o Minor bugfixes (Linux seccomp2 sandbox):
14848 - Make transparent proxy support work along with the seccomp2
14849 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14850 by Francisco Blas Izquierdo Riera.
14851 - Fix a memory leak in tor-resolve when running with the sandbox
14852 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14854 o Minor bugfixes (logging):
14855 - Downgrade warnings about RSA signature failures to info log level.
14856 Emit a warning when an extra info document is found incompatible
14857 with a corresponding router descriptor. Fixes bug 9812; bugfix
14859 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14860 correctly. Fixes bug 13701; bugfix on 0.0.6.
14862 o Minor bugfixes (misc):
14863 - Stop allowing invalid address patterns like "*/24" that contain
14864 both a wildcard address and a bit prefix length. This affects all
14865 our address-range parsing code. Fixes bug 7484; bugfix
14868 o Minor bugfixes (testing networks, fast startup):
14869 - Allow Tor to build circuits using a consensus with no exits. If
14870 the consensus has no exits (typical of a bootstrapping test
14871 network), allow Tor to build circuits once enough descriptors have
14872 been downloaded. This assists in bootstrapping a testing Tor
14873 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14875 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14876 header to directory servers. This allows us to obtain consensuses
14877 promptly when the consensus interval is very short. This assists
14878 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14879 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14880 - Stop assuming that private addresses are local when checking
14881 reachability in a TestingTorNetwork. Instead, when testing, assume
14882 all OR connections are remote. (This is necessary due to many test
14883 scenarios running all relays on localhost.) This assists in
14884 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14885 0.1.0.1-rc. Patch by "teor".
14886 - Avoid building exit circuits from a consensus with no exits. Now
14887 thanks to our fix for 13718, we accept a no-exit network as not
14888 wholly lost, but we need to remember not to try to build exit
14889 circuits on it. Closes ticket 13814; patch by "teor".
14890 - Stop requiring exits to have non-zero bandwithcapacity in a
14891 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14892 ignore exit bandwidthcapacity. This assists in bootstrapping a
14893 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14894 on 0.2.0.3-alpha. Patch by "teor".
14895 - Add "internal" to some bootstrap statuses when no exits are
14896 available. If the consensus does not contain Exits, Tor will only
14897 build internal circuits. In this case, relevant statuses will
14898 contain the word "internal" as indicated in the Tor control-
14899 spec.txt. When bootstrap completes, Tor will be ready to build
14900 internal circuits. If a future consensus contains Exits, exit
14901 circuits may become available. Fixes part of bug 13718; bugfix on
14902 0.2.4.10-alpha. Patch by "teor".
14903 - Decrease minimum consensus interval to 10 seconds when
14904 TestingTorNetwork is set, or 5 seconds for the first consensus.
14905 Fix assumptions throughout the code that assume larger intervals.
14906 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14908 - Avoid excluding guards from path building in minimal test
14909 networks, when we're in a test network and excluding guards would
14910 exclude all relays. This typically occurs in incredibly small tor
14911 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14912 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14914 o Code simplification and refactoring:
14915 - Stop using can_complete_circuits as a global variable; access it
14916 with a function instead.
14917 - Avoid using operators directly as macro arguments: this lets us
14918 apply coccinelle transformations to our codebase more directly.
14919 Closes ticket 13172.
14920 - Combine the functions used to parse ClientTransportPlugin and
14921 ServerTransportPlugin into a single function. Closes ticket 6456.
14922 - Add inline functions and convenience macros for inspecting channel
14923 state. Refactor the code to use convenience macros instead of
14924 checking channel state directly. Fixes issue 7356.
14925 - Document all members of was_router_added_t and rename
14926 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
14927 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
14928 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
14929 constant instead of hardcoded value. Fixes issue 13840.
14930 - Refactor our generic strmap and digestmap types into a single
14931 implementation, so that we can add a new digest256map
14935 - Document the bridge-authority-only 'networkstatus-bridges' file.
14936 Closes ticket 13713; patch from "tom".
14937 - Fix typo in PredictedPortsRelevanceTime option description in
14938 manpage. Resolves issue 13707.
14939 - Stop suggesting that users specify relays by nickname: it isn't a
14940 good idea. Also, properly cross-reference how to specify relays in
14941 all parts of manual documenting options that take a list of
14942 relays. Closes ticket 13381.
14943 - Clarify the HiddenServiceDir option description in manpage to make
14944 it clear that relative paths are taken with respect to the current
14945 working directory. Also clarify that this behavior is not
14946 guaranteed to remain indefinitely. Fixes issue 13913.
14949 - New tests for many parts of channel, relay, and circuitmux
14950 functionality. Code by Andrea; part of 9262.
14951 - New tests for parse_transport_line(). Part of ticket 6456.
14952 - In the unit tests, use chgrp() to change the group of the unit
14953 test temporary directory to the current user, so that the sticky
14954 bit doesn't interfere with tests that check directory groups.
14956 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
14960 Changes in version 0.2.6.1-alpha - 2014-10-30
14961 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
14962 includes numerous code cleanups and new tests, and fixes a large
14963 number of annoying bugs. Out-of-memory conditions are handled better
14964 than in 0.2.5, pluggable transports have improved proxy support, and
14965 clients now use optimistic data for contacting hidden services. Also,
14966 we are now more robust to changes in what we consider a parseable
14967 directory object, so that tightening restrictions does not have a risk
14968 of introducing infinite download loops.
14970 This is the first alpha release in a new series, so expect there to be
14971 bugs. Users who would rather test out a more stable branch should stay
14972 with 0.2.5.x for now.
14974 o New compiler and system requirements:
14975 - Tor 0.2.6.x requires that your compiler support more of the C99
14976 language standard than before. The 'configure' script now detects
14977 whether your compiler supports C99 mid-block declarations and
14978 designated initializers. If it does not, Tor will not compile.
14980 We may revisit this requirement if it turns out that a significant
14981 number of people need to build Tor with compilers that don't
14982 bother implementing a 15-year-old standard. Closes ticket 13233.
14983 - Tor no longer supports systems without threading support. When we
14984 began working on Tor, there were several systems that didn't have
14985 threads, or where the thread support wasn't able to run the
14986 threads of a single process on multiple CPUs. That no longer
14987 holds: every system where Tor needs to run well now has threading
14988 support. Resolves ticket 12439.
14990 o Removed platform support:
14991 - We no longer include special code to build on Windows CE; as far
14992 as we know, nobody has used Tor on Windows CE in a very long time.
14993 Closes ticket 11446.
14995 o Major features (bridges):
14996 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
14997 transports if they are configured via the "TOR_PT_PROXY"
14998 environment variable. Implements proposal 232. Resolves
15001 o Major features (client performance, hidden services):
15002 - Allow clients to use optimistic data when connecting to a hidden
15003 service, which should remove a round-trip from hidden service
15004 initialization. See proposal 181 for details. Implements
15007 o Major features (directory system):
15008 - Upon receiving an unparseable directory object, if its digest
15009 matches what we expected, then don't try to download it again.
15010 Previously, when we got a descriptor we didn't like, we would keep
15011 trying to download it over and over. Closes ticket 11243.
15013 o Major features (sample torrc):
15014 - Add a new, infrequently-changed "torrc.minimal". This file is
15015 similar to torrc.sample, but it will change as infrequently as
15016 possible, for the benefit of users whose systems prompt them for
15017 intervention whenever a default configuration file is changed.
15018 Making this change allows us to update torrc.sample to be a more
15019 generally useful "sample torrc".
15021 o Major bugfixes (directory authorities):
15022 - Do not assign the HSDir flag to relays if they are not Valid, or
15023 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
15025 o Major bugfixes (directory bandwidth performance):
15026 - Don't flush the zlib buffer aggressively when compressing
15027 directory information for clients. This should save about 7% of
15028 the bandwidth currently used for compressed descriptors and
15029 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
15031 o Minor features (security, memory wiping):
15032 - Ensure we securely wipe keys from memory after
15033 crypto_digest_get_digest and init_curve25519_keypair_from_file
15034 have finished using them. Resolves ticket 13477.
15036 o Minor features (security, out-of-memory handling):
15037 - When handling an out-of-memory condition, allocate less memory for
15038 temporary data structures. Fixes issue 10115.
15039 - When handling an out-of-memory condition, consider more types of
15040 buffers, including those on directory connections, and zlib
15041 buffers. Resolves ticket 11792.
15044 - When identity keypair is generated for first time, log a
15045 congratulatory message that links to the new relay lifecycle
15046 document. Implements feature 10427.
15048 o Minor features (client):
15049 - Clients are now willing to send optimistic data (before they
15050 receive a 'connected' cell) to relays of any version. (Relays
15051 without support for optimistic data are no longer supported on the
15052 Tor network.) Resolves ticket 13153.
15054 o Minor features (directory authorities):
15055 - Don't list relays with a bandwidth estimate of 0 in the consensus.
15056 Implements a feature proposed during discussion of bug 13000.
15057 - In tor-gencert, report an error if the user provides the same
15058 argument more than once.
15059 - If a directory authority can't find a best consensus method in the
15060 votes that it holds, it now falls back to its favorite consensus
15061 method. Previously, it fell back to method 1. Neither of these is
15062 likely to get enough signatures, but "fall back to favorite"
15063 doesn't require us to maintain support an obsolete consensus
15064 method. Implements part of proposal 215.
15066 o Minor features (logging):
15067 - On Unix-like systems, you can now use named pipes as the target of
15068 the Log option, and other options that try to append to files.
15069 Closes ticket 12061. Patch from "carlo von lynX".
15070 - When opening a log file at startup, send it every log message that
15071 we generated between startup and opening it. Previously, log
15072 messages that were generated before opening the log file were only
15073 logged to stdout. Closes ticket 6938.
15074 - Add a TruncateLogFile option to overwrite logs instead of
15075 appending to them. Closes ticket 5583.
15077 o Minor features (portability, Solaris):
15078 - Threads are no longer disabled by default on Solaris; we believe
15079 that the versions of Solaris with broken threading support are all
15080 obsolete by now. Resolves ticket 9495.
15082 o Minor features (relay):
15083 - Re-check our address after we detect a changed IP address from
15084 getsockname(). This ensures that the controller command "GETINFO
15085 address" will report the correct value. Resolves ticket 11582.
15087 - A new AccountingRule option lets Relays set whether they'd like
15088 AccountingMax to be applied separately to inbound and outbound
15089 traffic, or applied to the sum of inbound and outbound traffic.
15090 Resolves ticket 961. Patch by "chobe".
15092 o Minor features (testing networks):
15093 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
15094 the "Exit" flag regardless of their uptime, bandwidth, or exit
15095 policy. TestingTorNetwork must be set for this option to have any
15096 effect. Previously, authorities would take up to 35 minutes to
15097 give nodes the Exit flag in a test network. Partially implements
15100 o Minor features (validation):
15101 - Check all date/time values passed to tor_timegm and
15102 parse_rfc1123_time for validity, taking leap years into account.
15103 Improves HTTP header validation. Implemented with bug 13476.
15104 - In correct_tm(), limit the range of values returned by system
15105 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
15106 This means we don't have to deal with negative or too large dates,
15107 even if a clock is wrong. Otherwise we might fail to read a file
15108 written by us which includes such a date. Fixes bug 13476.
15110 o Minor bugfixes (bridge clients):
15111 - When configured to use a bridge without an identity digest (not
15112 recommended), avoid launching an extra channel to it when
15113 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
15115 o Minor bugfixes (bridges):
15116 - When DisableNetwork is set, do not launch pluggable transport
15117 plugins, and if any are running, terminate them. Fixes bug 13213;
15118 bugfix on 0.2.3.6-alpha.
15120 o Minor bugfixes (C correctness):
15121 - Fix several instances of possible integer overflow/underflow/NaN.
15122 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
15124 - In circuit_build_times_calculate_timeout() in circuitstats.c,
15125 avoid dividing by zero in the pareto calculations. This traps
15126 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
15128 - Fix an integer overflow in format_time_interval(). Fixes bug
15129 13393; bugfix on 0.2.0.10-alpha.
15130 - Set the correct day of year value when the system's localtime(_r)
15131 or gmtime(_r) functions fail to set struct tm. Not externally
15132 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
15133 - Avoid unlikely signed integer overflow in tor_timegm on systems
15134 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
15136 o Minor bugfixes (client):
15137 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
15138 BadExit flag are not considered worthy candidates. Fixes bug
15139 13066; bugfix on 0.1.2.3-alpha.
15140 - Use the consensus schedule for downloading consensuses, and not
15141 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
15142 - Handle unsupported or malformed SOCKS5 requests properly by
15143 responding with the appropriate error message before closing the
15144 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
15146 o Minor bugfixes (client, torrc):
15147 - Stop modifying the value of our DirReqStatistics torrc option just
15148 because we're not a bridge or relay. This bug was causing Tor
15149 Browser users to write "DirReqStatistics 0" in their torrc files
15150 as if they had chosen to change the config. Fixes bug 4244; bugfix
15152 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
15153 that our options have changed every time we SIGHUP. Fixes bug
15154 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
15156 o Minor bugfixes (controller):
15157 - Return an error when the second or later arguments of the
15158 "setevents" controller command are invalid events. Previously we
15159 would return success while silently skipping invalid events. Fixes
15160 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
15162 o Minor bugfixes (directory system):
15163 - Always believe that v3 directory authorities serve extra-info
15164 documents, whether they advertise "caches-extra-info" or not.
15165 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15166 - When running as a v3 directory authority, advertise that you serve
15167 extra-info documents so that clients who want them can find them
15168 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15169 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
15170 Previously, directories offering BRIDGE_DIRINFO and some other
15171 flag (i.e. microdescriptors or extrainfo) would be ignored when
15172 looking for bridges. Partially fixes bug 13163; bugfix
15175 o Minor bugfixes (networking):
15176 - Check for orconns and use connection_or_close_for_error() rather
15177 than connection_mark_for_close() directly in the getsockopt()
15178 failure case of connection_handle_write_impl(). Fixes bug 11302;
15179 bugfix on 0.2.4.4-alpha.
15181 o Minor bugfixes (relay):
15182 - When generating our family list, remove spaces from around the
15183 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
15184 - If our previous bandwidth estimate was 0 bytes, allow publishing a
15185 new relay descriptor immediately. Fixes bug 13000; bugfix
15188 o Minor bugfixes (testing networks):
15189 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15190 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15191 - Stop using the default authorities in networks which provide both
15192 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15193 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15195 o Minor bugfixes (testing):
15196 - Stop spawn test failures due to a race condition between the
15197 SIGCHLD handler updating the process status, and the test reading
15198 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15200 o Minor bugfixes (testing, Windows):
15201 - Avoid passing an extra backslash when creating a temporary
15202 directory for running the unit tests on Windows. Fixes bug 12392;
15203 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15205 o Minor bugfixes (windows):
15206 - Remove code to special-case handling of NTE_BAD_KEYSET when
15207 acquiring windows CryptoAPI context. This error can't actually
15208 occur for the parameters we're providing. Fixes bug 10816; bugfix
15211 o Minor bugfixes (zlib):
15212 - Avoid truncating a zlib stream when trying to finalize it with an
15213 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15216 - Allow our configure script to build correctly with autoconf 2.62
15217 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
15218 - Improve the error message from ./configure to make it clear that
15219 when asciidoc has not been found, the user will have to either add
15220 --disable-asciidoc argument or install asciidoc. Resolves
15223 o Code simplification and refactoring:
15224 - Change the entry_is_live() function to take named bitfield
15225 elements instead of an unnamed list of booleans. Closes
15227 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15228 Resolves ticket 12205.
15229 - Use calloc and reallocarray functions instead of multiply-
15230 then-malloc. This makes it less likely for us to fall victim to an
15231 integer overflow attack when allocating. Resolves ticket 12855.
15232 - Use the standard macro name SIZE_MAX, instead of our
15234 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15235 functions which take them as arguments. Replace 0 with NO_DIRINFO
15236 in a function call for clarity. Seeks to prevent future issues
15238 - Avoid 4 null pointer errors under clang static analysis by using
15239 tor_assert() to prove that the pointers aren't null. Fixes
15241 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15242 represent parsing options, instead of a confusing mess of
15243 booleans. Resolves ticket 8197.
15244 - Introduce a helper function to parse ExitPolicy in
15245 or_options_t structure.
15248 - Add a doc/TUNING document with tips for handling large numbers of
15249 TCP connections when running busy Tor relay. Update the warning
15250 message to point to this file when running out of sockets
15251 operating system is allowing to use simultaneously. Resolves
15254 o Removed features:
15255 - We no longer remind the user about configuration options that have
15256 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15257 - Remove our old, non-weighted bandwidth-based node selection code.
15258 Previously, we used it as a fallback when we couldn't perform
15259 weighted bandwidth-based node selection. But that would only
15260 happen in the cases where we had no consensus, or when we had a
15261 consensus generated by buggy or ancient directory authorities. In
15262 either case, it's better to use the more modern, better maintained
15263 algorithm, with reasonable defaults for the weights. Closes
15265 - Remove the --disable-curve25519 configure option. Relays and
15266 clients now are required to support curve25519 and the
15268 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15269 used to be deprecated synonyms for "StrictNodes", are now marked
15270 obsolete. Resolves ticket 12226.
15271 - Clients don't understand the BadDirectory flag in the consensus
15272 anymore, and ignore it.
15275 - Refactor the function that chooses guard nodes so that it can more
15276 easily be tested; write some tests for it.
15277 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15278 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15279 - Create unit tests for format_time_interval(). With bug 13393.
15280 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15281 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15282 tests (visible) fixes in bug 13476.
15283 - Add a "coverage-html" make target to generate HTML-visualized
15284 coverage results when building with --enable-coverage. (Requires
15285 lcov.) Patch from Kevin Murray.
15286 - Enable the backtrace handler (where supported) when running the
15288 - Revise all unit tests that used the legacy test_* macros to
15289 instead use the recommended tt_* macros. This patch was generated
15290 with coccinelle, to avoid manual errors. Closes ticket 13119.
15292 o Distribution (systemd):
15293 - systemd unit file: only allow tor to write to /var/lib/tor and
15294 /var/log/tor. The rest of the filesystem is accessible for reading
15295 only. Patch by intrigeri; resolves ticket 12751.
15296 - systemd unit file: ensure that the process and all its children
15297 can never gain new privileges. Patch by intrigeri; resolves
15299 - systemd unit file: set up /var/run/tor as writable for the Tor
15300 service. Patch by intrigeri; resolves ticket 13196.
15302 o Removed features (directory authorities):
15303 - Remove code that prevented authorities from listing Tor relays
15304 affected by CVE-2011-2769 as guards. These relays are already
15305 rejected altogether due to the minimum version requirement of
15306 0.2.3.16-alpha. Closes ticket 13152.
15307 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15308 the fingerprints file (approved-routers) has been deprecated.
15309 - Directory authorities do not support being Naming dirauths anymore.
15310 The "NamingAuthoritativeDir" config option is now obsolete.
15311 - Directory authorities do not support giving out the BadDirectory
15313 - Directory authorities no longer advertise or support consensus
15314 methods 1 through 12 inclusive. These consensus methods were
15315 obsolete and/or insecure: maintaining the ability to support them
15316 served no good purpose. Implements part of proposal 215; closes
15319 o Testing (test-network.sh):
15320 - Stop using "echo -n", as some shells' built-in echo doesn't
15321 support "-n". Instead, use "/bin/echo -n". Partially fixes
15323 - Stop an apparent test-network hang when used with make -j2. Fixes
15325 - Add a --delay option to test-network.sh, which configures the
15326 delay before the chutney network tests for data transmission.
15327 Partially implements ticket 13161.
15330 Changes in version 0.2.5.10 - 2014-10-24
15331 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15333 It adds several new security features, including improved
15334 denial-of-service resistance for relays, new compiler hardening
15335 options, and a system-call sandbox for hardened installations on Linux
15336 (requires seccomp2). The controller protocol has several new features,
15337 resolving IPv6 addresses should work better than before, and relays
15338 should be a little more CPU-efficient. We've added support for more
15339 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15340 system and testing infrastructure to allow unit testing of more parts
15341 of the Tor codebase. Finally, we've addressed several nagging pluggable
15342 transport usability issues, and included numerous other small bugfixes
15343 and features mentioned below.
15345 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15346 have accumulated many known flaws; everyone should upgrade.
15348 o Deprecated versions:
15349 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15350 attention for some while.
15353 Changes in version 0.2.5.9-rc - 2014-10-20
15354 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
15355 series. It disables SSL3 in response to the recent "POODLE" attack
15356 (even though POODLE does not affect Tor). It also works around a crash
15357 bug caused by some operating systems' response to the "POODLE" attack
15358 (which does affect Tor). It also contains a few miscellaneous fixes.
15360 o Major security fixes:
15361 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15362 today support TLS 1.0 or later, so we can safely turn off support
15363 for this old (and insecure) protocol. Fixes bug 13426.
15365 o Major bugfixes (openssl bug workaround):
15366 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15367 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15368 13471. This is a workaround for an OpenSSL bug.
15371 - Disable the sandbox name resolver cache when running tor-resolve:
15372 tor-resolve doesn't use the sandbox code, and turning it on was
15373 breaking attempts to do tor-resolve on a non-default server on
15374 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
15376 o Compilation fixes:
15377 - Build and run correctly on systems like OpenBSD-current that have
15378 patched OpenSSL to remove get_cipher_by_char and/or its
15379 implementations. Fixes issue 13325.
15381 o Downgraded warnings:
15382 - Downgrade the severity of the 'unexpected sendme cell from client'
15383 from 'warn' to 'protocol warning'. Closes ticket 8093.
15386 Changes in version 0.2.4.25 - 2014-10-20
15387 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
15388 (even though POODLE does not affect Tor). It also works around a crash
15389 bug caused by some operating systems' response to the "POODLE" attack
15390 (which does affect Tor).
15392 o Major security fixes (also in 0.2.5.9-rc):
15393 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15394 today support TLS 1.0 or later, so we can safely turn off support
15395 for this old (and insecure) protocol. Fixes bug 13426.
15397 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
15398 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15399 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15400 13471. This is a workaround for an OpenSSL bug.
15403 Changes in version 0.2.5.8-rc - 2014-09-22
15404 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
15405 series. It fixes a bug that affects consistency and speed when
15406 connecting to hidden services, and it updates the location of one of
15407 the directory authorities.
15410 - Clients now send the correct address for their chosen rendezvous
15411 point when trying to access a hidden service. They used to send
15412 the wrong address, which would still work some of the time because
15413 they also sent the identity digest of the rendezvous point, and if
15414 the hidden service happened to try connecting to the rendezvous
15415 point from a relay that already had a connection open to it,
15416 the relay would reuse that connection. Now connections to hidden
15417 services should be more robust and faster. Also, this bug meant
15418 that clients were leaking to the hidden service whether they were
15419 on a little-endian (common) or big-endian (rare) system, which for
15420 some users might have reduced their anonymity. Fixes bug 13151;
15421 bugfix on 0.2.1.5-alpha.
15423 o Directory authority changes:
15424 - Change IP address for gabelmoo (v3 directory authority).
15427 Changes in version 0.2.4.24 - 2014-09-22
15428 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
15429 connecting to hidden services, and it updates the location of one of
15430 the directory authorities.
15433 - Clients now send the correct address for their chosen rendezvous
15434 point when trying to access a hidden service. They used to send
15435 the wrong address, which would still work some of the time because
15436 they also sent the identity digest of the rendezvous point, and if
15437 the hidden service happened to try connecting to the rendezvous
15438 point from a relay that already had a connection open to it,
15439 the relay would reuse that connection. Now connections to hidden
15440 services should be more robust and faster. Also, this bug meant
15441 that clients were leaking to the hidden service whether they were
15442 on a little-endian (common) or big-endian (rare) system, which for
15443 some users might have reduced their anonymity. Fixes bug 13151;
15444 bugfix on 0.2.1.5-alpha.
15446 o Directory authority changes:
15447 - Change IP address for gabelmoo (v3 directory authority).
15449 o Minor features (geoip):
15450 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15454 Changes in version 0.2.5.7-rc - 2014-09-11
15455 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
15456 release series, and some long-standing bugs related to ORPort reachability
15457 testing and failure to send CREATE cells. It is the first release
15458 candidate for the Tor 0.2.5.x series.
15460 o Major bugfixes (client, startup):
15461 - Start making circuits as soon as DisabledNetwork is turned off.
15462 When Tor started with DisabledNetwork set, it would correctly
15463 conclude that it shouldn't build circuits, but it would mistakenly
15464 cache this conclusion, and continue believing it even when
15465 DisableNetwork is set to 0. Fixes the bug introduced by the fix
15466 for bug 11200; bugfix on 0.2.5.4-alpha.
15467 - Resume expanding abbreviations for command-line options. The fix
15468 for bug 4647 accidentally removed our hack from bug 586 that
15469 rewrote HashedControlPassword to __HashedControlSessionPassword
15470 when it appears on the commandline (which allowed the user to set
15471 her own HashedControlPassword in the torrc file while the
15472 controller generates a fresh session password for each run). Fixes
15473 bug 12948; bugfix on 0.2.5.1-alpha.
15474 - Warn about attempts to run hidden services and relays in the same
15475 process: that's probably not a good idea. Closes ticket 12908.
15477 o Major bugfixes (relay):
15478 - Avoid queuing or sending destroy cells for circuit ID zero when we
15479 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15480 Found and fixed by "cypherpunks".
15481 - Fix ORPort reachability detection on relays running behind a
15482 proxy, by correctly updating the "local" mark on the controlling
15483 channel when changing the address of an or_connection_t after the
15484 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15486 o Minor features (bridge):
15487 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15488 cookie file for the ExtORPort g+r by default.
15490 o Minor features (geoip):
15491 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15494 o Minor bugfixes (logging):
15495 - Reduce the log severity of the "Pluggable transport proxy does not
15496 provide any needed transports and will not be launched." message,
15497 since Tor Browser includes several ClientTransportPlugin lines in
15498 its torrc-defaults file, leading every Tor Browser user who looks
15499 at her logs to see these notices and wonder if they're dangerous.
15500 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
15501 - Downgrade "Unexpected onionskin length after decryption" warning
15502 to a protocol-warn, since there's nothing relay operators can do
15503 about a client that sends them a malformed create cell. Resolves
15504 bug 12996; bugfix on 0.0.6rc1.
15505 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15506 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15507 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15508 their names correctly. Fixes part of bug 12700; bugfix
15510 - When logging information about a relay cell whose command we don't
15511 recognize, log its command as an integer. Fixes part of bug 12700;
15512 bugfix on 0.2.1.10-alpha.
15513 - Escape all strings from the directory connection before logging
15514 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
15516 o Minor bugfixes (controller):
15517 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
15518 bug 12864; bugfix on 0.2.5.1-alpha.
15519 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
15520 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
15523 o Minor bugfixes (compilation):
15524 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
15525 bugfix on 0.2.5.5-alpha.
15526 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
15527 0.2.5.1-alpha. Patch from "NewEraCracker".
15528 - In routerlist_assert_ok(), don't take the address of a
15529 routerinfo's cache_info member unless that routerinfo is non-NULL.
15530 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15531 - Fix a large number of false positive warnings from the clang
15532 analyzer static analysis tool. This should make real warnings
15533 easier for clang analyzer to find. Patch from "teor". Closes
15536 o Distribution (systemd):
15537 - Verify configuration file via ExecStartPre in the systemd unit
15538 file. Patch from intrigeri; resolves ticket 12730.
15539 - Explicitly disable RunAsDaemon in the systemd unit file. Our
15540 current systemd unit uses "Type = simple", so systemd does not
15541 expect tor to fork. If the user has "RunAsDaemon 1" in their
15542 torrc, then things won't work as expected. This is e.g. the case
15543 on Debian (and derivatives), since there we pass "--defaults-torrc
15544 /usr/share/tor/tor-service-defaults-torrc" (that contains
15545 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
15549 - Adjust the URLs in the README to refer to the new locations of
15550 several documents on the website. Fixes bug 12830. Patch from
15552 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
15556 Changes in version 0.2.5.6-alpha - 2014-07-28
15557 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
15558 risk from guard rotation, and fixes a variety of other issues to get
15559 us closer to a release candidate.
15561 o Major features (also in 0.2.4.23):
15562 - Make the number of entry guards configurable via a new
15563 NumEntryGuards consensus parameter, and the number of directory
15564 guards configurable via a new NumDirectoryGuards consensus
15565 parameter. Implements ticket 12688.
15567 o Major bugfixes (also in 0.2.4.23):
15568 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15569 implementation that caused incorrect results on 32-bit
15570 implementations when certain malformed inputs were used along with
15571 a small class of private ntor keys. This bug does not currently
15572 appear to allow an attacker to learn private keys or impersonate a
15573 Tor server, but it could provide a means to distinguish 32-bit Tor
15574 implementations from 64-bit Tor implementations. Fixes bug 12694;
15575 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15579 - Perform circuit cleanup operations even when circuit
15580 construction operations are disabled (because the network is
15581 disabled, or because there isn't enough directory information).
15582 Previously, when we were not building predictive circuits, we
15583 were not closing expired circuits either. Fixes bug 8387; bugfix on
15584 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15585 became more strict about when we have "enough directory information
15586 to build circuits".
15589 - Authorities now assign the Guard flag to the fastest 25% of the
15590 network (it used to be the fastest 50%). Also raise the consensus
15591 weight that guarantees the Guard flag from 250 to 2000. For the
15592 current network, this results in about 1100 guards, down from 2500.
15593 This step paves the way for moving the number of entry guards
15594 down to 1 (proposal 236) while still providing reasonable expected
15595 performance for most users. Implements ticket 12690.
15596 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15598 - Slightly enhance the diagnostic message for bug 12184.
15600 o Minor bugfixes (also in 0.2.4.23):
15601 - Warn and drop the circuit if we receive an inbound 'relay early'
15602 cell. Those used to be normal to receive on hidden service circuits
15603 due to bug 1038, but the buggy Tor versions are long gone from
15604 the network so we can afford to resume watching for them. Resolves
15605 the rest of bug 1038; bugfix on 0.2.1.19.
15606 - Correct a confusing error message when trying to extend a circuit
15607 via the control protocol but we don't know a descriptor or
15608 microdescriptor for one of the specified relays. Fixes bug 12718;
15609 bugfix on 0.2.3.1-alpha.
15612 - Fix compilation when building with bufferevents enabled. (This
15613 configuration is still not expected to work, however.)
15614 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
15615 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
15617 - Compile correctly with builds and forks of OpenSSL (such as
15618 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15619 0.2.1.1-alpha. Patch from "dhill".
15622 Changes in version 0.2.4.23 - 2014-07-28
15623 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
15624 guard rotation, and also backports several important fixes from the
15625 Tor 0.2.5 alpha release series.
15628 - Clients now look at the "usecreatefast" consensus parameter to
15629 decide whether to use CREATE_FAST or CREATE cells for the first hop
15630 of their circuit. This approach can improve security on connections
15631 where Tor's circuit handshake is stronger than the available TLS
15632 connection security levels, but the tradeoff is more computational
15633 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15634 - Make the number of entry guards configurable via a new
15635 NumEntryGuards consensus parameter, and the number of directory
15636 guards configurable via a new NumDirectoryGuards consensus
15637 parameter. Implements ticket 12688.
15640 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15641 implementation that caused incorrect results on 32-bit
15642 implementations when certain malformed inputs were used along with
15643 a small class of private ntor keys. This bug does not currently
15644 appear to allow an attacker to learn private keys or impersonate a
15645 Tor server, but it could provide a means to distinguish 32-bit Tor
15646 implementations from 64-bit Tor implementations. Fixes bug 12694;
15647 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15651 - Warn and drop the circuit if we receive an inbound 'relay early'
15652 cell. Those used to be normal to receive on hidden service circuits
15653 due to bug 1038, but the buggy Tor versions are long gone from
15654 the network so we can afford to resume watching for them. Resolves
15655 the rest of bug 1038; bugfix on 0.2.1.19.
15656 - Correct a confusing error message when trying to extend a circuit
15657 via the control protocol but we don't know a descriptor or
15658 microdescriptor for one of the specified relays. Fixes bug 12718;
15659 bugfix on 0.2.3.1-alpha.
15660 - Avoid an illegal read from stack when initializing the TLS
15661 module using a version of OpenSSL without all of the ciphers
15662 used by the v2 link handshake. Fixes bug 12227; bugfix on
15663 0.2.4.8-alpha. Found by "starlight".
15666 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15670 Changes in version 0.2.5.5-alpha - 2014-06-18
15671 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
15672 0.2.5.x release series, including a couple of DoS issues, some
15673 performance regressions, a large number of bugs affecting the Linux
15674 seccomp2 sandbox code, and various other bugfixes. It also adds
15675 diagnostic bugfixes for a few tricky issues that we're trying to
15678 o Major features (security, traffic analysis resistance):
15679 - Several major improvements to the algorithm used to decide when to
15680 close TLS connections. Previous versions of Tor closed connections
15681 at a fixed interval after the last time a non-padding cell was
15682 sent over the connection, regardless of the target of the
15683 connection. Now, we randomize the intervals by adding up to 50% of
15684 their base value, we measure the length of time since connection
15685 last had at least one circuit, and we allow connections to known
15686 ORs to remain open a little longer (15 minutes instead of 3
15687 minutes minimum). These changes should improve Tor's resistance
15688 against some kinds of traffic analysis, and lower some overhead
15689 from needlessly closed connections. Fixes ticket 6799.
15690 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
15692 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
15693 - Fix a memory leak that could occur if a microdescriptor parse
15694 fails during the tokenizing step. This bug could enable a memory
15695 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15698 o Major bugfixes (security, directory authorities):
15699 - Directory authorities now include a digest of each relay's
15700 identity key as a part of its microdescriptor.
15702 This is a workaround for bug 11743 (reported by "cypherpunks"),
15703 where Tor clients do not support receiving multiple
15704 microdescriptors with the same SHA256 digest in the same
15705 consensus. When clients receive a consensus like this, they only
15706 use one of the relays. Without this fix, a hostile relay could
15707 selectively disable some client use of target relays by
15708 constructing a router descriptor with a different identity and the
15709 same microdescriptor parameters and getting the authorities to
15710 list it in a microdescriptor consensus. This fix prevents an
15711 attacker from causing a microdescriptor collision, because the
15712 router's identity is not forgeable.
15714 o Major bugfixes (relay):
15715 - Use a direct dirport connection when uploading non-anonymous
15716 descriptors to the directory authorities. Previously, relays would
15717 incorrectly use tunnel connections under a fairly wide variety of
15718 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15719 - When a circuit accidentally has the same circuit ID for its
15720 forward and reverse direction, correctly detect the direction of
15721 cells using that circuit. Previously, this bug made roughly one
15722 circuit in a million non-functional. Fixes bug 12195; this is a
15723 bugfix on every version of Tor.
15725 o Major bugfixes (client, pluggable transports):
15726 - When managing pluggable transports, use OS notification facilities
15727 to learn if they have crashed, and don't attempt to kill any
15728 process that has already exited. Fixes bug 8746; bugfix
15731 o Minor features (diagnostic):
15732 - When logging a warning because of bug 7164, additionally check the
15733 hash table for consistency (as proposed on ticket 11737). This may
15734 help diagnose bug 7164.
15735 - When we log a heartbeat, log how many one-hop circuits we have
15736 that are at least 30 minutes old, and log status information about
15737 a few of them. This is an attempt to track down bug 8387.
15738 - When encountering an unexpected CR while writing text to a file on
15739 Windows, log the name of the file. Should help diagnosing
15741 - Give more specific warnings when a client notices that an onion
15742 handshake has failed. Fixes ticket 9635.
15743 - Add significant new logging code to attempt to diagnose bug 12184,
15744 where relays seem to run out of available circuit IDs.
15745 - Improve the diagnostic log message for bug 8387 even further to
15746 try to improve our odds of figuring out why one-hop directory
15747 circuits sometimes do not get closed.
15749 o Minor features (security, memory management):
15750 - Memory allocation tricks (mempools and buffer freelists) are now
15751 disabled by default. You can turn them back on with
15752 --enable-mempools and --enable-buf-freelists respectively. We're
15753 disabling these features because malloc performance is good enough
15754 on most platforms, and a similar feature in OpenSSL exacerbated
15755 exploitation of the Heartbleed attack. Resolves ticket 11476.
15757 o Minor features (security):
15758 - Apply the secure SipHash-2-4 function to the hash table mapping
15759 circuit IDs and channels to circuits. We missed this one when we
15760 were converting all the other hash functions to use SipHash back
15761 in 0.2.5.3-alpha. Resolves ticket 11750.
15763 o Minor features (build):
15764 - The configure script has a --disable-seccomp option to turn off
15765 support for libseccomp on systems that have it, in case it (or
15766 Tor's use of it) is broken. Resolves ticket 11628.
15768 o Minor features (other):
15769 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15772 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15773 - When running a hidden service, do not allow TunneledDirConns 0;
15774 this will keep the hidden service from running, and also
15775 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15776 bugfix on 0.2.1.1-alpha.
15778 o Minor bugfixes (performance):
15779 - Avoid a bug where every successful connection made us recompute
15780 the flag telling us whether we have sufficient information to
15781 build circuits. Previously, we would forget our cached value
15782 whenever we successfully opened a channel (or marked a router as
15783 running or not running for any other reason), regardless of
15784 whether we had previously believed the router to be running. This
15785 forced us to run an expensive update operation far too often.
15786 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15787 - Avoid using tor_memeq() for checking relay cell integrity. This
15788 removes a possible performance bottleneck. Fixes part of bug
15789 12169; bugfix on 0.2.1.31.
15791 o Minor bugfixes (compilation):
15792 - Fix compilation of test_status.c when building with MVSC. Bugfix
15793 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15794 - Resolve GCC complaints on OpenBSD about discarding constness in
15795 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15796 on 0.1.1.23. Patch from Dana Koch.
15797 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15798 treatment of long and time_t as comparable types. Fixes part of
15799 bug 11633. Patch from Dana Koch.
15800 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15801 11623; bugfix on 0.2.5.3-alpha.
15802 - When deciding whether to build the 64-bit curve25519
15803 implementation, detect platforms where we can compile 128-bit
15804 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15805 0.2.4.8-alpha. Patch from "conradev".
15806 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15807 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15808 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15811 o Minor bugfixes (Directory server):
15812 - When sending a compressed set of descriptors or microdescriptors,
15813 make sure to finalize the zlib stream. Previously, we would write
15814 all the compressed data, but if the last descriptor we wanted to
15815 send was missing or too old, we would not mark the stream as
15816 finished. This caused problems for decompression tools. Fixes bug
15817 11648; bugfix on 0.1.1.23.
15819 o Minor bugfixes (Linux seccomp sandbox):
15820 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15821 11622; bugfix on 0.2.5.1-alpha.
15822 - Avoid crashing when re-opening listener ports with the seccomp
15823 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15824 - Avoid crashing with the seccomp sandbox enabled along with
15825 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15826 - When we receive a SIGHUP with the sandbox enabled, correctly
15827 support rotating our log files. Fixes bug 12032; bugfix
15829 - Avoid crash when running with sandboxing enabled and
15830 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15832 - Fix a "BUG" warning when trying to write bridge-stats files with
15833 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15835 - Prevent the sandbox from crashing on startup when run with the
15836 --enable-expensive-hardening configuration option. Fixes bug
15837 11477; bugfix on 0.2.5.4-alpha.
15838 - When running with DirPortFrontPage and sandboxing both enabled,
15839 reload the DirPortFrontPage correctly when restarting. Fixes bug
15840 12028; bugfix on 0.2.5.1-alpha.
15841 - Don't try to enable the sandbox when using the Tor binary to check
15842 its configuration, hash a passphrase, or so on. Doing so was
15843 crashing on startup for some users. Fixes bug 11609; bugfix
15845 - Avoid warnings when running with sandboxing and node statistics
15846 enabled at the same time. Fixes part of 12064; bugfix on
15847 0.2.5.1-alpha. Patch from Michael Wolf.
15848 - Avoid warnings when running with sandboxing enabled at the same
15849 time as cookie authentication, hidden services, or directory
15850 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15851 - Do not allow options that require calls to exec to be enabled
15852 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15853 bug 12043; bugfix on 0.2.5.1-alpha.
15854 - Handle failures in getpwnam()/getpwuid() when running with the
15855 User option set and the Linux syscall sandbox enabled. Fixes bug
15856 11946; bugfix on 0.2.5.1-alpha.
15857 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15858 to avoid calling getaddrinfo() after installing the sandbox
15859 filters. Previously, it preloaded a cache with the IPv4 address
15860 for our hostname, and nothing else. Now, it loads the cache with
15861 every address that it used to initialize the Tor process. Fixes
15862 bug 11970; bugfix on 0.2.5.1-alpha.
15864 o Minor bugfixes (pluggable transports):
15865 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15866 default location of the authentication token for the extended OR
15867 Port as used by sever-side pluggable transports. We had
15868 implemented this option before, but the code to make it settable
15869 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15870 - Avoid another 60-second delay when starting Tor in a pluggable-
15871 transport-using configuration when we already have cached
15872 descriptors for our bridges. Fixes bug 11965; bugfix
15875 o Minor bugfixes (client):
15876 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15877 when starting a client with bridges configured and DisableNetwork
15878 set. (Tor launcher starts Tor with DisableNetwork set the first
15879 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15881 o Minor bugfixes (testing):
15882 - The Python parts of the test scripts now work on Python 3 as well
15883 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15884 no longer have the tests break. Fixes bug 11608; bugfix
15886 - When looking for versions of python that we could run the tests
15887 with, check for "python2.7" and "python3.3"; previously we were
15888 only looking for "python", "python2", and "python3". Patch from
15889 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15890 - Fix all valgrind warnings produced by the unit tests. There were
15891 over a thousand memory leak warnings previously, mostly produced
15892 by forgetting to free things in the unit test code. Fixes bug
15893 11618, bugfixes on many versions of Tor.
15895 o Minor bugfixes (tor-fw-helper):
15896 - Give a correct log message when tor-fw-helper fails to launch.
15897 (Previously, we would say something like "tor-fw-helper sent us a
15898 string we could not parse".) Fixes bug 9781; bugfix
15901 o Minor bugfixes (relay, threading):
15902 - Check return code on spawn_func() in cpuworker code, so that we
15903 don't think we've spawned a nonworking cpuworker and write junk to
15904 it forever. Fix related to bug 4345; bugfix on all released Tor
15905 versions. Found by "skruffy".
15906 - Use a pthread_attr to make sure that spawn_func() cannot return an
15907 error while at the same time launching a thread. Fix related to
15908 bug 4345; bugfix on all released Tor versions. Reported
15911 o Minor bugfixes (relay, oom prevention):
15912 - Correctly detect the total available system memory. We tried to do
15913 this in 0.2.5.4-alpha, but the code was set up to always return an
15914 error value, even on success. Fixes bug 11805; bugfix
15917 o Minor bugfixes (relay, other):
15918 - We now drop CREATE cells for already-existent circuit IDs and for
15919 zero-valued circuit IDs, regardless of other factors that might
15920 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
15922 - Avoid an illegal read from stack when initializing the TLS module
15923 using a version of OpenSSL without all of the ciphers used by the
15924 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
15926 - When rejecting DATA cells for stream_id zero, still count them
15927 against the circuit's deliver window so that we don't fail to send
15928 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
15930 o Minor bugfixes (logging):
15931 - Fix a misformatted log message about delayed directory fetches.
15932 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
15933 - Squelch a spurious LD_BUG message "No origin circuit for
15934 successful SOCKS stream" in certain hidden service failure cases;
15938 - Include a tor.service file in contrib/dist for use with systemd.
15939 Some distributions will be able to use this file unmodified;
15940 others will need to tweak it, or write their own. Patch from Jamie
15941 Nguyen; resolves ticket 8368.
15944 - Clean up several option names in the manpage to match their real
15945 names, add the missing documentation for a couple of testing and
15946 directory authority options, remove the documentation for a
15947 V2-directory fetching option that no longer exists. Resolves
15949 - Correct the documentation so that it lists the correct directory
15950 for the stats files. (They are in a subdirectory called "stats",
15952 - In the manpage, move more authority-only options into the
15953 directory authority section so that operators of regular directory
15954 caches don't get confused.
15957 - The contrib directory has been sorted and tidied. Before, it was
15958 an unsorted dumping ground for useful and not-so-useful things.
15959 Now, it is divided based on functionality, and the items which
15960 seemed to be nonfunctional or useless have been removed. Resolves
15961 ticket 8966; based on patches from "rl1987".
15964 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
15965 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
15966 - The TunnelDirConns and PreferTunnelledDirConns options no longer
15967 exist; tunneled directory connections have been available since
15968 0.1.2.5-alpha, and turning them off is not a good idea. This is a
15969 brute-force fix for 10849, where "TunnelDirConns 0" would break
15973 Changes in version 0.2.4.22 - 2014-05-16
15974 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
15975 alpha release series. These include blocking all authority signing
15976 keys that may have been affected by the OpenSSL "heartbleed" bug,
15977 choosing a far more secure set of TLS ciphersuites by default, closing
15978 a couple of memory leaks that could be used to run a target relay out
15979 of RAM, and several others.
15981 o Major features (security, backport from 0.2.5.4-alpha):
15982 - Block authority signing keys that were used on authorities
15983 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
15984 don't have any evidence that these keys _were_ compromised; we're
15985 doing this to be prudent.) Resolves ticket 11464.
15987 o Major bugfixes (security, OOM):
15988 - Fix a memory leak that could occur if a microdescriptor parse
15989 fails during the tokenizing step. This bug could enable a memory
15990 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15993 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
15994 - The relay ciphersuite list is now generated automatically based on
15995 uniform criteria, and includes all OpenSSL ciphersuites with
15996 acceptable strength and forward secrecy. Previously, we had left
15997 some perfectly fine ciphersuites unsupported due to omission or
15998 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
15999 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16000 - Relays now trust themselves to have a better view than clients of
16001 which TLS ciphersuites are better than others. (Thanks to bug
16002 11513, the relay list is now well-considered, whereas the client
16003 list has been chosen mainly for anti-fingerprinting purposes.)
16004 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16005 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16006 AES128. Resolves ticket 11528.
16007 - Clients now try to advertise the same list of ciphersuites as
16008 Firefox 28. This change enables selection of (fast) GCM
16009 ciphersuites, disables some strange old ciphers, and stops
16010 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16011 Resolves ticket 11438.
16013 o Minor bugfixes (configuration, security):
16014 - When running a hidden service, do not allow TunneledDirConns 0:
16015 trying to set that option together with a hidden service would
16016 otherwise prevent the hidden service from running, and also make
16017 it publish its descriptors directly over HTTP. Fixes bug 10849;
16018 bugfix on 0.2.1.1-alpha.
16020 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
16021 - Avoid sending a garbage value to the controller when a circuit is
16022 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16024 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
16025 - Stop leaking memory when we successfully resolve a PTR record.
16026 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16028 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
16029 - Avoid 60-second delays in the bootstrapping process when Tor is
16030 launching for a second time while using bridges. Fixes bug 9229;
16031 bugfix on 0.2.0.3-alpha.
16033 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
16034 - Give the correct URL in the warning message when trying to run a
16035 relay on an ancient version of Windows. Fixes bug 9393.
16037 o Minor bugfixes (compilation):
16038 - Fix a compilation error when compiling with --disable-curve25519.
16039 Fixes bug 9700; bugfix on 0.2.4.17-rc.
16042 - Downgrade the warning severity for the the "md was still
16043 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
16044 for trying to diagnose this bug, and the current warning in
16045 earlier versions of tor achieves nothing useful. Addresses warning
16048 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
16049 - When we run out of usable circuit IDs on a channel, log only one
16050 warning for the whole channel, and describe how many circuits
16051 there were on the channel. Fixes part of ticket 11553.
16053 o Minor features (security, backport from 0.2.5.4-alpha):
16054 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
16055 leave the default at 8GBytes), to better support Raspberry Pi
16056 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
16058 o Documentation (backport from 0.2.5.4-alpha):
16059 - Correctly document that we search for a system torrc file before
16060 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16064 Changes in version 0.2.5.4-alpha - 2014-04-25
16065 Tor 0.2.5.4-alpha includes several security and performance
16066 improvements for clients and relays, including blacklisting authority
16067 signing keys that were used while susceptible to the OpenSSL
16068 "heartbleed" bug, fixing two expensive functions on busy relays,
16069 improved TLS ciphersuite preference lists, support for run-time
16070 hardening on compilers that support AddressSanitizer, and more work on
16071 the Linux sandbox code.
16073 There are also several usability fixes for clients (especially clients
16074 that use bridges), two new TransPort protocols supported (one on
16075 OpenBSD, one on FreeBSD), and various other bugfixes.
16077 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
16078 have accumulated many known flaws; everyone should upgrade.
16080 o Major features (security):
16081 - If you don't specify MaxMemInQueues yourself, Tor now tries to
16082 pick a good value based on your total system memory. Previously,
16083 the default was always 8 GB. You can still override the default by
16084 setting MaxMemInQueues yourself. Resolves ticket 11396.
16085 - Block authority signing keys that were used on authorities
16086 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
16087 don't have any evidence that these keys _were_ compromised; we're
16088 doing this to be prudent.) Resolves ticket 11464.
16090 o Major features (relay performance):
16091 - Speed up server-side lookups of rendezvous and introduction point
16092 circuits by using hashtables instead of linear searches. These
16093 functions previously accounted between 3 and 7% of CPU usage on
16094 some busy relays. Resolves ticket 9841.
16095 - Avoid wasting CPU when extending a circuit over a channel that is
16096 nearly out of circuit IDs. Previously, we would do a linear scan
16097 over possible circuit IDs before finding one or deciding that we
16098 had exhausted our possibilities. Now, we try at most 64 random
16099 circuit IDs before deciding that we probably won't succeed. Fixes
16100 a possible root cause of ticket 11553.
16102 o Major features (seccomp2 sandbox, Linux only):
16103 - The seccomp2 sandbox can now run a test network for multiple hours
16104 without crashing. The sandbox is still experimental, and more bugs
16105 will probably turn up. To try it, enable "Sandbox 1" on a Linux
16106 host. Resolves ticket 11351.
16107 - Strengthen sandbox code: the sandbox can now test the arguments
16108 for rename(), and blocks _sysctl() entirely. Resolves another part
16110 - When the sandbox blocks a system call, it now tries to log a stack
16111 trace before exiting. Resolves ticket 11465.
16113 o Major bugfixes (TLS cipher selection):
16114 - The relay ciphersuite list is now generated automatically based on
16115 uniform criteria, and includes all OpenSSL ciphersuites with
16116 acceptable strength and forward secrecy. Previously, we had left
16117 some perfectly fine ciphersuites unsupported due to omission or
16118 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
16119 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16120 - Relays now trust themselves to have a better view than clients of
16121 which TLS ciphersuites are better than others. (Thanks to bug
16122 11513, the relay list is now well-considered, whereas the client
16123 list has been chosen mainly for anti-fingerprinting purposes.)
16124 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16125 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16126 AES128. Resolves ticket 11528.
16127 - Clients now try to advertise the same list of ciphersuites as
16128 Firefox 28. This change enables selection of (fast) GCM
16129 ciphersuites, disables some strange old ciphers, and stops
16130 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16131 Resolves ticket 11438.
16133 o Major bugfixes (bridge client):
16134 - Avoid 60-second delays in the bootstrapping process when Tor is
16135 launching for a second time while using bridges. Fixes bug 9229;
16136 bugfix on 0.2.0.3-alpha.
16138 o Minor features (transparent proxy, *BSD):
16139 - Support FreeBSD's ipfw firewall interface for TransPort ports on
16140 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
16141 10267; patch from "yurivict".
16142 - Support OpenBSD's divert-to rules with the pf firewall for
16143 transparent proxy ports. To enable it, set "TransProxyType
16144 pf-divert". This allows Tor to run a TransPort transparent proxy
16145 port on OpenBSD 4.4 or later without root privileges. See the
16146 pf.conf(5) manual page for information on configuring pf to use
16147 divert-to rules. Closes ticket 10896; patch from Dana Koch.
16149 o Minor features (security):
16150 - New --enable-expensive-hardening option to enable security
16151 hardening options that consume nontrivial amounts of CPU and
16152 memory. Right now, this includes AddressSanitizer and UbSan, which
16153 are supported in newer versions of GCC and Clang. Closes ticket
16156 o Minor features (log verbosity):
16157 - Demote the message that we give when a flushing connection times
16158 out for too long from NOTICE to INFO. It was usually meaningless.
16159 Resolves ticket 5286.
16160 - Don't log so many notice-level bootstrapping messages at startup
16161 about downloading descriptors. Previously, we'd log a notice
16162 whenever we learned about more routers. Now, we only log a notice
16163 at every 5% of progress. Fixes bug 9963.
16164 - Warn less verbosely when receiving a malformed
16165 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
16166 - When we run out of usable circuit IDs on a channel, log only one
16167 warning for the whole channel, and describe how many circuits
16168 there were on the channel. Fixes part of ticket 11553.
16170 o Minor features (relay):
16171 - If a circuit timed out for at least 3 minutes, check if we have a
16172 new external IP address, and publish a new descriptor with the new
16173 IP address if it changed. Resolves ticket 2454.
16175 o Minor features (controller):
16176 - Make the entire exit policy available from the control port via
16177 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16179 - Because of the fix for ticket 11396, the real limit for memory
16180 usage may no longer match the configured MaxMemInQueues value. The
16181 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16183 o Minor features (bridge client):
16184 - Report a more useful failure message when we can't connect to a
16185 bridge because we don't have the right pluggable transport
16186 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16188 o Minor features (diagnostic):
16189 - Add more log messages to diagnose bug 7164, which causes
16190 intermittent "microdesc_free() called but md was still referenced"
16191 warnings. We now include more information, to figure out why we
16192 might be cleaning a microdescriptor for being too old if it's
16193 still referenced by a live node_t object.
16195 o Minor bugfixes (client, DNSPort):
16196 - When using DNSPort, try to respond to AAAA requests with AAAA
16197 answers. Previously, we hadn't looked at the request type when
16198 deciding which answer type to prefer. Fixes bug 10468; bugfix on
16200 - When receiving a DNS query for an unsupported record type, reply
16201 with no answer rather than with a NOTIMPL error. This behavior
16202 isn't correct either, but it will break fewer client programs, we
16203 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
16206 o Minor bugfixes (exit relay):
16207 - Stop leaking memory when we successfully resolve a PTR record.
16208 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16210 o Minor bugfixes (bridge client):
16211 - Stop accepting bridge lines containing hostnames. Doing so would
16212 cause clients to perform DNS requests on the hostnames, which was
16213 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
16214 - Avoid a 60-second delay in the bootstrapping process when a Tor
16215 client with pluggable transports re-reads its configuration at
16216 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
16218 o Minor bugfixes (client, logging during bootstrap):
16219 - Warn only once if we start logging in an unsafe way. Previously,
16220 we complain as many times as we had problems. Fixes bug 9870;
16221 bugfix on 0.2.5.1-alpha.
16222 - Only report the first fatal bootstrap error on a given OR
16223 connection. This stops us from telling the controller bogus error
16224 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
16225 - Be more helpful when trying to run sandboxed on Linux without
16226 libseccomp. Instead of saying "Sandbox is not implemented on this
16227 platform", we now explain that we need to be built with
16228 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
16229 - Avoid generating spurious warnings when starting with
16230 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
16233 o Minor bugfixes (closing OR connections):
16234 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
16235 check if it's an or_connection_t and correctly call
16236 connection_or_close_for_error() rather than
16237 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
16239 - When closing all connections on setting DisableNetwork to 1, use
16240 connection_or_close_normally() rather than closing OR connections
16241 out from under the channel layer. Fixes bug 11306; bugfix on
16244 o Minor bugfixes (controller):
16245 - Avoid sending a garbage value to the controller when a circuit is
16246 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16248 o Minor bugfixes (tor-fw-helper):
16249 - Allow tor-fw-helper to build again by adding src/ext to its
16250 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
16252 o Minor bugfixes (bridges):
16253 - Avoid potential crashes or bad behavior when launching a
16254 server-side managed proxy with ORPort or ExtORPort temporarily
16255 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
16257 o Minor bugfixes (platform-specific):
16258 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
16259 bug 11426; bugfix on 0.2.5.3-alpha.
16260 - When dumping a malformed directory object to disk, save it in
16261 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16263 - Don't report failures from make_socket_reuseable() on incoming
16264 sockets on OSX: this can happen when incoming connections close
16265 early. Fixes bug 10081.
16267 o Minor bugfixes (trivial memory leaks):
16268 - Fix a small memory leak when signing a directory object. Fixes bug
16269 11275; bugfix on 0.2.4.13-alpha.
16270 - Free placeholder entries in our circuit table at exit; fixes a
16271 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
16272 - Don't re-initialize a second set of OpenSSL mutexes when starting
16273 up. Previously, we'd make one set of mutexes, and then immediately
16274 replace them with another. Fixes bug 11726; bugfix on
16276 - Resolve some memory leaks found by coverity in the unit tests, on
16277 exit in tor-gencert, and on a failure to compute digests for our
16278 own keys when generating a v3 networkstatus vote. These leaks
16279 should never have affected anyone in practice.
16281 o Minor bugfixes (hidden service):
16282 - Only retry attempts to connect to a chosen rendezvous point 8
16283 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
16285 o Minor bugfixes (misc code correctness):
16286 - Fix various instances of undefined behavior in channeltls.c,
16287 tor_memmem(), and eventdns.c that would cause us to construct
16288 pointers to memory outside an allocated object. (These invalid
16289 pointers were not accessed, but C does not even allow them to
16290 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16291 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16292 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16293 fix some miscellaneous errors in our tests and codebase. Fixes bug
16294 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16295 - Always check return values for unlink, munmap, UnmapViewOfFile;
16296 check strftime return values more often. In some cases all we can
16297 do is report a warning, but this may help prevent deeper bugs from
16298 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16300 - Fix numerous warnings from the clang "scan-build" static analyzer.
16301 Some of these are programming style issues; some of them are false
16302 positives that indicated awkward code; some are undefined behavior
16303 cases related to constructing (but not using) invalid pointers;
16304 some are assumptions about API behavior; some are (harmlessly)
16305 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16306 correct; and one or two are genuine bugs that weren't reachable
16307 from the rest of the program. Fixes bug 8793; bugfixes on many,
16311 - Build the torify.1 manpage again. Previously, we were only trying
16312 to build it when also building tor-fw-helper. That's why we didn't
16313 notice that we'd broken the ability to build it. Fixes bug 11321;
16314 bugfix on 0.2.5.1-alpha.
16315 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16316 11061; bugfix on 0.2.4.7-alpha.
16317 - Correctly document that we search for a system torrc file before
16318 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16320 - Resolve warnings from Doxygen.
16322 o Code simplifications and refactoring:
16323 - Remove is_internal_IP() function. Resolves ticket 4645.
16324 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16325 Closes issue 9107; patch from "marek".
16326 - Change our use of the ENUM_BF macro to avoid declarations that
16329 o Deprecated versions:
16330 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
16331 attention for some while. Directory authorities no longer accept
16332 descriptors from relays running any version of Tor prior to Tor
16333 0.2.3.16-alpha. Resolves ticket 11149.
16336 - New macros in test.h to simplify writing mock-functions for unit
16337 tests. Part of ticket 11507. Patch from Dana Koch.
16338 - Complete tests for the status.c module. Resolves ticket 11507.
16339 Patch from Dana Koch.
16342 - Remove all code for the long unused v1 directory protocol.
16343 Resolves ticket 11070.
16346 Changes in version 0.2.5.3-alpha - 2014-03-22
16347 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
16348 two new anti-DoS features for Tor relays, resolves a bug that kept
16349 SOCKS5 support for IPv6 from working, fixes several annoying usability
16350 issues for bridge users, and removes more old code for unused
16353 The Tor 0.2.5.x release series is now in patch-freeze: no feature
16354 patches not already written will be considered for inclusion in 0.2.5.x.
16356 o Major features (relay security, DoS-resistance):
16357 - When deciding whether we have run out of memory and we need to
16358 close circuits, also consider memory allocated in buffers for
16359 streams attached to each circuit.
16361 This change, which extends an anti-DoS feature introduced in
16362 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16363 better resist more memory-based DoS attacks than before. Since the
16364 MaxMemInCellQueues option now applies to all queues, it is renamed
16365 to MaxMemInQueues. This feature fixes bug 10169.
16366 - Avoid hash-flooding denial-of-service attacks by using the secure
16367 SipHash-2-4 hash function for our hashtables. Without this
16368 feature, an attacker could degrade performance of a targeted
16369 client or server by flooding their data structures with a large
16370 number of entries to be stored at the same hash table position,
16371 thereby slowing down the Tor instance. With this feature, hash
16372 table positions are derived from a randomized cryptographic key,
16373 and an attacker cannot predict which entries will collide. Closes
16375 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
16376 the default at 8GBytes), to better support Raspberry Pi users. Fixes
16377 bug 9686; bugfix on 0.2.4.14-alpha.
16379 o Minor features (bridges, pluggable transports):
16380 - Bridges now write the SHA1 digest of their identity key
16381 fingerprint (that is, a hash of a hash of their public key) to
16382 notice-level logs, and to a new hashed-fingerprint file. This
16383 information will help bridge operators look up their bridge in
16384 Globe and similar tools. Resolves ticket 10884.
16385 - Improve the message that Tor displays when running as a bridge
16386 using pluggable transports without an Extended ORPort listener.
16387 Also, log the message in the log file too. Resolves ticket 11043.
16389 o Minor features (other):
16390 - Add a new option, PredictedPortsRelevanceTime, to control how long
16391 after having received a request to connect to a given port Tor
16392 will try to keep circuits ready in anticipation of future requests
16393 for that port. Patch from "unixninja92"; implements ticket 9176.
16394 - Generate a warning if any ports are listed in the SocksPolicy,
16395 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16396 AuthDirBadExit options. (These options only support address
16397 ranges.) Fixes part of ticket 11108.
16398 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
16401 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
16402 - Build without warnings under clang 3.4. (We have some macros that
16403 define static functions only some of which will get used later in
16404 the module. Starting with clang 3.4, these give a warning unless the
16405 unused attribute is set on them.) Resolves ticket 10904.
16406 - Fix build warnings about missing "a2x" comment when building the
16407 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16408 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16410 o Minor bugfixes (client):
16411 - Improve the log message when we can't connect to a hidden service
16412 because all of the hidden service directory nodes hosting its
16413 descriptor are excluded. Improves on our fix for bug 10722, which
16414 was a bugfix on 0.2.0.10-alpha.
16415 - Raise a control port warning when we fail to connect to all of
16416 our bridges. Previously, we didn't inform the controller, and
16417 the bootstrap process would stall. Fixes bug 11069; bugfix on
16419 - Exit immediately when a process-owning controller exits.
16420 Previously, tor relays would wait for a little while after their
16421 controller exited, as if they had gotten an INT signal -- but this
16422 was problematic, since there was no feedback for the user. To do a
16423 clean shutdown, controllers should send an INT signal and give Tor
16424 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16425 - Stop attempting to connect to bridges before our pluggable
16426 transports are configured (harmless but resulted in some erroneous
16427 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16428 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16429 generating incorrect SOCKS5 responses, and confusing client
16430 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16432 o Minor bugfixes (relays and bridges):
16433 - Avoid crashing on a malformed resolv.conf file when running a
16434 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16435 - Non-exit relays no longer launch mock DNS requests to check for
16436 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16437 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16438 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16439 - Bridges now report complete directory request statistics. Related
16440 to bug 5824; bugfix on 0.2.2.1-alpha.
16441 - Bridges now never collect statistics that were designed for
16442 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16443 - Stop giving annoying warning messages when we decide not to launch
16444 a pluggable transport proxy that we don't need (because there are
16445 no bridges configured to use it). Resolves ticket 5018; bugfix
16447 - Give the correct URL in the warning message when trying to run a
16448 relay on an ancient version of Windows. Fixes bug 9393.
16450 o Minor bugfixes (backtrace support):
16451 - Support automatic backtraces on more platforms by using the
16452 "-fasynchronous-unwind-tables" compiler option. This option is
16453 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
16454 is on by default and table generation is not. This doesn't yet
16455 add Windows support; only Linux, OSX, and some BSDs are affected.
16456 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
16457 - Avoid strange behavior if two threads hit failed assertions at the
16458 same time and both try to log backtraces at once. (Previously, if
16459 this had happened, both threads would have stored their intermediate
16460 results in the same buffer, and generated junk outputs.) Reported by
16461 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
16462 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
16463 0.2.5.2-alpha; patch from Nick Hopper.
16465 o Minor bugfixes (unit tests):
16466 - Fix a small bug in the unit tests that might have made the tests
16467 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
16468 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
16471 - Remove all remaining code related to version-0 hidden service
16472 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16473 the rest of bug 10841.
16476 - Document in the manpage that "KBytes" may also be written as
16477 "kilobytes" or "KB", that "Kbits" may also be written as
16478 "kilobits", and so forth. Closes ticket 9222.
16479 - Document that the ClientOnly config option overrides ORPort.
16480 Our old explanation made ClientOnly sound as though it did
16481 nothing at all. Resolves bug 9059.
16482 - Explain that SocksPolicy, DirPolicy, and similar options don't
16483 take port arguments. Fixes the other part of ticket 11108.
16484 - Fix a comment about the rend_server_descriptor_t.protocols field
16485 to more accurately describe its range. Also, make that field
16486 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16487 bugfix on 0.2.1.5-alpha.
16488 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16489 the maximum client name length is 16, not 19. Fixes bug 11118;
16490 bugfix on 0.2.1.6-alpha.
16492 o Code simplifications and refactoring:
16493 - Get rid of router->address, since in all cases it was just the
16494 string representation of router->addr. Resolves ticket 5528.
16496 o Test infrastructure:
16497 - Update to the latest version of tinytest.
16498 - Improve the tinytest implementation of string operation tests so
16499 that comparisons with NULL strings no longer crash the tests; they
16500 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16503 Changes in version 0.2.4.21 - 2014-02-28
16504 Tor 0.2.4.21 further improves security against potential adversaries who
16505 find breaking 1024-bit crypto doable, and backports several stability
16506 and robustness patches from the 0.2.5 branch.
16508 o Major features (client security):
16509 - When we choose a path for a 3-hop circuit, make sure it contains
16510 at least one relay that supports the NTor circuit extension
16511 handshake. Otherwise, there is a chance that we're building
16512 a circuit that's worth attacking by an adversary who finds
16513 breaking 1024-bit crypto doable, and that chance changes the game
16514 theory. Implements ticket 9777.
16517 - Do not treat streams that fail with reason
16518 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16519 since it could also indicate an ENETUNREACH connection error. Fixes
16520 part of bug 10777; bugfix on 0.2.4.8-alpha.
16522 o Code simplification and refactoring:
16523 - Remove data structures which were introduced to implement the
16524 CellStatistics option: they are now redundant with the new timestamp
16525 field in the regular packed_cell_t data structure, which we did
16526 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16529 - Always clear OpenSSL bignums before freeing them -- even bignums
16530 that don't contain secrets. Resolves ticket 10793. Patch by
16532 - Build without warnings under clang 3.4. (We have some macros that
16533 define static functions only some of which will get used later in
16534 the module. Starting with clang 3.4, these give a warning unless the
16535 unused attribute is set on them.) Resolves ticket 10904.
16536 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16537 GeoLite2 Country database.
16540 - Set the listen() backlog limit to the largest actually supported
16541 on the system, not to the value in a header file. Fixes bug 9716;
16542 bugfix on every released Tor.
16543 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16544 exit node as a NOROUTE error, not an INTERNAL error, since they
16545 can apparently happen when trying to connect to the wrong sort
16546 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16547 - Fix build warnings about missing "a2x" comment when building the
16548 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16549 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16550 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16551 not entirely remove it from the connection lists. Fixes bug 9602;
16552 bugfix on 0.2.4.4-alpha.
16553 - Fix a segmentation fault in our benchmark code when running with
16554 Fedora's OpenSSL package, or any other OpenSSL that provides
16555 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16556 - Turn "circuit handshake stats since last time" log messages into a
16557 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16559 o Documentation fixes:
16560 - Document that all but one DirPort entry must have the NoAdvertise
16561 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16564 Changes in version 0.2.5.2-alpha - 2014-02-13
16565 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
16566 like the "poor random number generation" fix and the "building too many
16567 circuits" fix. It also further improves security against potential
16568 adversaries who find breaking 1024-bit crypto doable, and launches
16569 pluggable transports on demand (which gets us closer to integrating
16570 pluggable transport support by default -- not to be confused with Tor
16571 bundles enabling pluggable transports and bridges by default).
16573 o Major features (client security):
16574 - When we choose a path for a 3-hop circuit, make sure it contains
16575 at least one relay that supports the NTor circuit extension
16576 handshake. Otherwise, there is a chance that we're building
16577 a circuit that's worth attacking by an adversary who finds
16578 breaking 1024-bit crypto doable, and that chance changes the game
16579 theory. Implements ticket 9777.
16580 - Clients now look at the "usecreatefast" consensus parameter to
16581 decide whether to use CREATE_FAST or CREATE cells for the first hop
16582 of their circuit. This approach can improve security on connections
16583 where Tor's circuit handshake is stronger than the available TLS
16584 connection security levels, but the tradeoff is more computational
16585 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16587 o Major features (bridges):
16588 - Don't launch pluggable transport proxies if we don't have any
16589 bridges configured that would use them. Now we can list many
16590 pluggable transports, and Tor will dynamically start one when it
16591 hears a bridge address that needs it. Resolves ticket 5018.
16592 - The bridge directory authority now assigns status flags (Stable,
16593 Guard, etc) to bridges based on thresholds calculated over all
16594 Running bridges. Now bridgedb can finally make use of its features
16595 to e.g. include at least one Stable bridge in its answers. Fixes
16598 o Major features (other):
16599 - Extend ORCONN controller event to include an "ID" parameter,
16600 and add four new controller event types CONN_BW, CIRC_BW,
16601 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16602 The new events are emitted in private Tor networks only, with the
16603 goal of being able to better track performance and load during
16604 full-network simulations. Implements proposal 218 and ticket 7359.
16605 - On some platforms (currently: recent OSX versions, glibc-based
16606 platforms that support the ELF format, and a few other
16607 Unix-like operating systems), Tor can now dump stack traces
16608 when a crash occurs or an assertion fails. By default, traces
16609 are dumped to stderr (if possible) and to any logs that are
16610 reporting errors. Implements ticket 9299.
16613 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16614 not entirely remove it from the connection lists. Fixes bug 9602;
16615 bugfix on 0.2.4.4-alpha.
16616 - Do not treat streams that fail with reason
16617 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16618 since it could also indicate an ENETUNREACH connection error. Fixes
16619 part of bug 10777; bugfix on 0.2.4.8-alpha.
16621 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16622 - Do not allow OpenSSL engines to replace the PRNG, even when
16623 HardwareAccel is set. The only default builtin PRNG engine uses
16624 the Intel RDRAND instruction to replace the entire PRNG, and
16625 ignores all attempts to seed it with more entropy. That's
16626 cryptographically stupid: the right response to a new alleged
16627 entropy source is never to discard all previously used entropy
16628 sources. Fixes bug 10402; works around behavior introduced in
16629 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16631 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16632 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16633 - Avoid launching spurious extra circuits when a stream is pending.
16634 This fixes a bug where any circuit that _wasn't_ unusable for new
16635 streams would be treated as if it were, causing extra circuits to
16636 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16638 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16639 - No longer stop reading or writing on cpuworker connections when
16640 our rate limiting buckets go empty. Now we should handle circuit
16641 handshake requests more promptly. Resolves bug 9731.
16642 - Stop trying to bootstrap all our directory information from
16643 only our first guard. Discovered while fixing bug 9946; bugfix
16646 o Minor features (bridges, pluggable transports):
16647 - Add threshold cutoffs to the networkstatus document created by
16648 the Bridge Authority. Fixes bug 1117.
16649 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16650 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16651 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16652 Vidalia set this option for us.) Implements ticket 10297.
16654 o Minor features (security):
16655 - Always clear OpenSSL bignums before freeing them -- even bignums
16656 that don't contain secrets. Resolves ticket 10793. Patch by
16659 o Minor features (config options and command line):
16660 - Add an --allow-missing-torrc commandline option that tells Tor to
16661 run even if the configuration file specified by -f is not available.
16662 Implements ticket 10060.
16663 - Add support for the TPROXY transparent proxying facility on Linux.
16664 See documentation for the new TransProxyType option for more
16665 details. Implementation by "thomo". Closes ticket 10582.
16667 o Minor features (controller):
16668 - Add a new "HS_DESC" controller event that reports activities
16669 related to hidden service descriptors. Resolves ticket 8510.
16670 - New "DROPGUARDS" controller command to forget all current entry
16671 guards. Not recommended for ordinary use, since replacing guards
16672 too frequently makes several attacks easier. Resolves ticket 9934;
16675 o Minor features (build):
16676 - Assume that a user using ./configure --host wants to cross-compile,
16677 and give an error if we cannot find a properly named
16678 tool-chain. Add a --disable-tool-name-check option to proceed
16679 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16680 - If we run ./configure and the compiler recognizes -fstack-protector
16681 but the linker rejects it, warn the user about a potentially missing
16682 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16684 o Minor features (testing):
16685 - If Python is installed, "make check" now runs extra tests beyond
16686 the unit test scripts.
16687 - When bootstrapping a test network, sometimes very few relays get
16688 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16689 specify a set of relays which should be voted Guard regardless of
16690 their uptime or bandwidth. Addresses ticket 9206.
16692 o Minor features (log messages):
16693 - When ServerTransportPlugin is set on a bridge, Tor can write more
16694 useful statistics about bridge use in its extrainfo descriptors,
16695 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16696 log message to inform the user in this case. Resolves ticket 9651.
16697 - When receiving a new controller connection, log the origin address.
16698 Resolves ticket 9698; patch from "sigpipe".
16699 - When logging OpenSSL engine status at startup, log the status of
16700 more engines. Fixes ticket 10043; patch from Joshua Datko.
16701 - Turn "circuit handshake stats since last time" log messages into a
16702 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16704 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16705 - Improve the circuit queue out-of-memory handler. Previously, when
16706 we ran low on memory, we'd close whichever circuits had the most
16707 queued cells. Now, we close those that have the *oldest* queued
16708 cells, on the theory that those are most responsible for us
16709 running low on memory. Based on analysis from a forthcoming paper
16710 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16711 - Generate bootstrapping status update events correctly when fetching
16712 microdescriptors. Fixes bug 9927.
16713 - Update to the October 2 2013 Maxmind GeoLite Country database.
16715 o Minor bugfixes (clients):
16716 - When closing a channel that has already been open, do not close
16717 pending circuits that were waiting to connect to the same relay.
16718 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16721 o Minor bugfixes (relays):
16722 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16723 exit node as a NOROUTE error, not an INTERNAL error, since they
16724 can apparently happen when trying to connect to the wrong sort
16725 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16727 o Minor bugfixes (bridges):
16728 - Fix a bug where the first connection works to a bridge that uses a
16729 pluggable transport with client-side parameters, but we don't send
16730 the client-side parameters on subsequent connections. (We don't
16731 use any pluggable transports with client-side parameters yet,
16732 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16733 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16735 o Minor bugfixes (node selection):
16736 - If ExcludeNodes is set, consider non-excluded hidden service
16737 directory servers before excluded ones. Do not consider excluded
16738 hidden service directory servers at all if StrictNodes is
16739 set. (Previously, we would sometimes decide to connect to those
16740 servers, and then realize before we initiated a connection that
16741 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16742 Reported by "mr-4".
16743 - If we set the ExitNodes option but it doesn't include any nodes
16744 that have the Exit flag, we would choose not to bootstrap. Now we
16745 bootstrap so long as ExitNodes includes nodes which can exit to
16746 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16748 o Minor bugfixes (controller and command-line):
16749 - If changing a config option via "setconf" fails in a recoverable
16750 way, we used to nonetheless write our new control ports to the
16751 file described by the "ControlPortWriteToFile" option. Now we only
16752 write out that file if we successfully switch to the new config
16753 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16754 - When a command-line option such as --version or --help that
16755 ordinarily implies --hush appears on the command line along with
16756 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16757 only if it appeared later on the command line. Fixes bug 9578;
16758 bugfix on 0.2.5.1-alpha.
16760 o Minor bugfixes (code correctness):
16761 - Previously we used two temporary files when writing descriptors to
16762 disk; now we only use one. Fixes bug 1376.
16763 - Remove an erroneous (but impossible and thus harmless) pointer
16764 comparison that would have allowed compilers to skip a bounds
16765 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16766 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16767 - Fix an always-true assertion in pluggable transports code so it
16768 actually checks what it was trying to check. Fixes bug 10046;
16769 bugfix on 0.2.3.9-alpha. Found by "dcb".
16771 o Minor bugfixes (protocol correctness):
16772 - When receiving a VERSIONS cell with an odd number of bytes, close
16773 the connection immediately since the cell is malformed. Fixes bug
16774 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16777 o Minor bugfixes (build):
16778 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16779 turned off (that is, without support for v2 link handshakes). Fixes
16780 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16781 - Fix compilation warnings and startup issues when running with
16782 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16784 - Fix compilation on Solaris 9, which didn't like us having an
16785 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16787 o Minor bugfixes (testing):
16788 - Fix a segmentation fault in our benchmark code when running with
16789 Fedora's OpenSSL package, or any other OpenSSL that provides
16790 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16792 o Minor bugfixes (log messages):
16793 - Fix a bug where clients using bridges would report themselves
16794 as 50% bootstrapped even without a live consensus document.
16795 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16796 - Suppress a warning where, if there's only one directory authority
16797 in the network, we would complain that votes and signatures cannot
16798 be uploaded to other directory authorities. Fixes bug 10842;
16799 bugfix on 0.2.2.26-beta.
16800 - Report bootstrapping progress correctly when we're downloading
16801 microdescriptors. We had updated our "do we have enough microdescs
16802 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16803 (see bug 5956), but we left the bootstrap status event logic at
16804 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16805 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16807 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16808 - Avoid a crash bug when starting with a corrupted microdescriptor
16809 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16810 - If we fail to dump a previously cached microdescriptor to disk, avoid
16811 freeing duplicate data later on. Fixes bug 10423; bugfix on
16812 0.2.4.13-alpha. Spotted by "bobnomnom".
16814 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16815 - Correctly log long IPv6 exit policies, instead of truncating them
16816 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16817 - Our default TLS ecdhe groups were backwards: we meant to be using
16818 P224 for relays (for performance win) and P256 for bridges (since
16819 it is more common in the wild). Instead we had it backwards. After
16820 reconsideration, we decided that the default should be P256 on all
16821 hosts, since its security is probably better, and since P224 is
16822 reportedly used quite little in the wild. Found by "skruffy" on
16823 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16824 - Free directory authority certificate download statuses on exit
16825 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16827 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16828 - If the guard we choose first doesn't answer, we would try the
16829 second guard, but once we connected to the second guard we would
16830 abandon it and retry the first one, slowing down bootstrapping.
16831 The fix is to treat all our initially chosen guards as acceptable
16832 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16833 - Fix an assertion failure that would occur when disabling the
16834 ORPort setting on a running Tor process while accounting was
16835 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16836 - When examining the list of network interfaces to find our address,
16837 do not consider non-running or disabled network interfaces. Fixes
16838 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16839 - Avoid an off-by-one error when checking buffer boundaries when
16840 formatting the exit status of a pluggable transport helper.
16841 This is probably not an exploitable bug, but better safe than
16842 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16845 o Removed code and features:
16846 - Clients now reject any directory authority certificates lacking
16847 a dir-key-crosscert element. These have been included since
16848 0.2.1.9-alpha, so there's no real reason for them to be optional
16849 any longer. Completes proposal 157. Resolves ticket 10162.
16850 - Remove all code that existed to support the v2 directory system,
16851 since there are no longer any v2 directory authorities. Resolves
16853 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16854 options, which were used for designating authorities as "Hidden
16855 service authorities". There has been no use of hidden service
16856 authorities since 0.2.2.1-alpha, when we stopped uploading or
16857 downloading v0 hidden service descriptors. Fixes bug 10881; also
16858 part of a fix for bug 10841.
16860 o Code simplification and refactoring:
16861 - Remove some old fallback code designed to keep Tor clients working
16862 in a network with only two working relays. Elsewhere in the code we
16863 have long since stopped supporting such networks, so there wasn't
16864 much point in keeping it around. Addresses ticket 9926.
16865 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16866 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16867 - Remove data structures which were introduced to implement the
16868 CellStatistics option: they are now redundant with the addition
16869 of a timestamp to the regular packed_cell_t data structure, which
16870 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16873 o Documentation (man page) fixes:
16874 - Update manpage to describe some of the files you can expect to
16875 find in Tor's DataDirectory. Addresses ticket 9839.
16876 - Document that all but one DirPort entry must have the NoAdvertise
16877 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16879 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16880 - Clarify the usage and risks of setting the ContactInfo torrc line
16881 for your relay or bridge. Resolves ticket 9854.
16882 - Add anchors to the manpage so we can link to the html version of
16883 the documentation for specific options. Resolves ticket 9866.
16884 - Replace remaining references to DirServer in man page and
16885 log entries. Resolves ticket 10124.
16888 - Make the "tor-gencert" tool used by directory authority operators
16889 create 2048-bit signing keys by default (rather than 1024-bit, since
16890 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16893 Changes in version 0.2.4.20 - 2013-12-22
16894 Tor 0.2.4.20 fixes potentially poor random number generation for users
16895 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16896 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16897 and 4) have no state file in their DataDirectory (as would happen on
16898 first start). Users who generated relay or hidden service identity
16899 keys in such a situation should discard them and generate new ones.
16901 This release also fixes a logic error that caused Tor clients to build
16902 many more preemptive circuits than they actually need.
16905 - Do not allow OpenSSL engines to replace the PRNG, even when
16906 HardwareAccel is set. The only default builtin PRNG engine uses
16907 the Intel RDRAND instruction to replace the entire PRNG, and
16908 ignores all attempts to seed it with more entropy. That's
16909 cryptographically stupid: the right response to a new alleged
16910 entropy source is never to discard all previously used entropy
16911 sources. Fixes bug 10402; works around behavior introduced in
16912 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16914 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16915 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16916 - Avoid launching spurious extra circuits when a stream is pending.
16917 This fixes a bug where any circuit that _wasn't_ unusable for new
16918 streams would be treated as if it were, causing extra circuits to
16919 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16922 - Avoid a crash bug when starting with a corrupted microdescriptor
16923 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16924 - If we fail to dump a previously cached microdescriptor to disk, avoid
16925 freeing duplicate data later on. Fixes bug 10423; bugfix on
16926 0.2.4.13-alpha. Spotted by "bobnomnom".
16929 Changes in version 0.2.4.19 - 2013-12-11
16930 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
16931 (1986-2013). Aaron worked on diverse projects including helping to guide
16932 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
16933 transparency to the U.S government's PACER documents, and contributing
16934 design and development for Tor and Tor2Web. Aaron was one of the latest
16935 martyrs in our collective fight for civil liberties and human rights,
16936 and his death is all the more painful because he was one of us.
16938 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
16939 a new circuit handshake and link encryption that use ECC to provide
16940 better security and efficiency; makes relays better manage circuit
16941 creation requests; uses "directory guards" to reduce client enumeration
16942 risks; makes bridges collect and report statistics about the pluggable
16943 transports they support; cleans up and improves our geoip database;
16944 gets much closer to IPv6 support for clients, bridges, and relays; makes
16945 directory authorities use measured bandwidths rather than advertised
16946 ones when computing flags and thresholds; disables client-side DNS
16947 caching to reduce tracking risks; and fixes a big bug in bridge
16948 reachability testing. This release introduces two new design
16949 abstractions in the code: a new "channel" abstraction between circuits
16950 and or_connections to allow for implementing alternate relay-to-relay
16951 transports, and a new "circuitmux" abstraction storing the queue of
16952 circuits for a channel. The release also includes many stability,
16953 security, and privacy fixes.
16956 Changes in version 0.2.4.18-rc - 2013-11-16
16957 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
16958 series. It takes a variety of fixes from the 0.2.5.x branch to improve
16959 stability, performance, and better handling of edge cases.
16962 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
16963 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
16964 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
16965 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
16966 them to solve bug 6033.)
16969 - No longer stop reading or writing on cpuworker connections when
16970 our rate limiting buckets go empty. Now we should handle circuit
16971 handshake requests more promptly. Resolves bug 9731.
16972 - If we are unable to save a microdescriptor to the journal, do not
16973 drop it from memory and then reattempt downloading it. Fixes bug
16974 9645; bugfix on 0.2.2.6-alpha.
16975 - Stop trying to bootstrap all our directory information from
16976 only our first guard. Discovered while fixing bug 9946; bugfix
16978 - The new channel code sometimes lost track of in-progress circuits,
16979 causing long-running clients to stop building new circuits. The
16980 fix is to always call circuit_n_chan_done(chan, 0) from
16981 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
16983 o Minor bugfixes (on 0.2.4.x):
16984 - Correctly log long IPv6 exit policies, instead of truncating them
16985 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16986 - Our default TLS ecdhe groups were backwards: we meant to be using
16987 P224 for relays (for performance win) and P256 for bridges (since
16988 it is more common in the wild). Instead we had it backwards. After
16989 reconsideration, we decided that the default should be P256 on all
16990 hosts, since its security is probably better, and since P224 is
16991 reportedly used quite little in the wild. Found by "skruffy" on
16992 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16993 - Free directory authority certificate download statuses on exit
16994 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16996 o Minor bugfixes (on 0.2.3.x and earlier):
16997 - If the guard we choose first doesn't answer, we would try the
16998 second guard, but once we connected to the second guard we would
16999 abandon it and retry the first one, slowing down bootstrapping.
17000 The fix is to treat all our initially chosen guards as acceptable
17001 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
17002 - Fix an assertion failure that would occur when disabling the
17003 ORPort setting on a running Tor process while accounting was
17004 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
17005 - When examining the list of network interfaces to find our address,
17006 do not consider non-running or disabled network interfaces. Fixes
17007 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
17008 - Avoid an off-by-one error when checking buffer boundaries when
17009 formatting the exit status of a pluggable transport helper.
17010 This is probably not an exploitable bug, but better safe than
17011 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
17014 o Minor features (protecting client timestamps):
17015 - Clients no longer send timestamps in their NETINFO cells. These were
17016 not used for anything, and they provided one small way for clients
17017 to be distinguished from each other as they moved from network to
17018 network or behind NAT. Implements part of proposal 222.
17019 - Clients now round timestamps in INTRODUCE cells down to the nearest
17020 10 minutes. If a new Support022HiddenServices option is set to 0, or
17021 if it's set to "auto" and the feature is disabled in the consensus,
17022 the timestamp is sent as 0 instead. Implements part of proposal 222.
17023 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17024 a big deal from a security point of view, but it achieves no actual
17025 good purpose, and isn't needed. Implements part of proposal 222.
17026 - Reduce down accuracy of timestamps in hidden service descriptors.
17027 Implements part of proposal 222.
17029 o Minor features (other):
17030 - Improve the circuit queue out-of-memory handler. Previously, when
17031 we ran low on memory, we'd close whichever circuits had the most
17032 queued cells. Now, we close those that have the *oldest* queued
17033 cells, on the theory that those are most responsible for us
17034 running low on memory. Based on analysis from a forthcoming paper
17035 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
17036 - Generate bootstrapping status update events correctly when fetching
17037 microdescriptors. Fixes bug 9927.
17038 - Update to the October 2 2013 Maxmind GeoLite Country database.
17040 o Documentation fixes:
17041 - Clarify the usage and risks of setting the ContactInfo torrc line
17042 for your relay or bridge. Resolves ticket 9854.
17043 - Add anchors to the manpage so we can link to the html version of
17044 the documentation for specific options. Resolves ticket 9866.
17045 - Replace remaining references to DirServer in man page and
17046 log entries. Resolves ticket 10124.
17049 Changes in version 0.2.5.1-alpha - 2013-10-02
17050 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
17051 on Linux, allows bridges that offer pluggable transports to report usage
17052 statistics, fixes many issues to make testing easier, and provides
17053 a pile of minor features and bugfixes that have been waiting for a
17054 release of the new branch.
17056 This is the first alpha release in a new series, so expect there to
17057 be bugs. Users who would rather test out a more stable branch should
17058 stay with 0.2.4.x for now.
17060 o Major features (security):
17061 - Use the seccomp2 syscall filtering facility on Linux to limit
17062 which system calls Tor can invoke. This is an experimental,
17063 Linux-only feature to provide defense-in-depth against unknown
17064 attacks. To try turning it on, set "Sandbox 1" in your torrc
17065 file. Please be ready to report bugs. We hope to add support
17066 for better sandboxing in the future, including more fine-grained
17067 filters, better division of responsibility, and support for more
17068 platforms. This work has been done by Cristian-Matei Toader for
17069 Google Summer of Code.
17070 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
17071 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
17072 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
17073 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
17074 them to solve bug 6033.)
17076 o Major features (other):
17077 - Add support for passing arguments to managed pluggable transport
17078 proxies. Implements ticket 3594.
17079 - Bridges now track GeoIP information and the number of their users
17080 even when pluggable transports are in use, and report usage
17081 statistics in their extra-info descriptors. Resolves tickets 4773
17083 - Make testing Tor networks bootstrap better: lower directory fetch
17084 retry schedules and maximum interval without directory requests,
17085 and raise maximum download tries. Implements ticket 6752.
17086 - Add make target 'test-network' to run tests on a Chutney network.
17087 Implements ticket 8530.
17088 - The ntor handshake is now on-by-default, no matter what the
17089 directory authorities recommend. Implements ticket 8561.
17092 - Instead of writing destroy cells directly to outgoing connection
17093 buffers, queue them and intersperse them with other outgoing cells.
17094 This can prevent a set of resource starvation conditions where too
17095 many pending destroy cells prevent data cells from actually getting
17096 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
17097 bugfix on 0.2.0.1-alpha.
17098 - If we are unable to save a microdescriptor to the journal, do not
17099 drop it from memory and then reattempt downloading it. Fixes bug
17100 9645; bugfix on 0.2.2.6-alpha.
17101 - The new channel code sometimes lost track of in-progress circuits,
17102 causing long-running clients to stop building new circuits. The
17103 fix is to always call circuit_n_chan_done(chan, 0) from
17104 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
17107 - Tor now builds each source file in two modes: a mode that avoids
17108 exposing identifiers needlessly, and another mode that exposes
17109 more identifiers for testing. This lets the compiler do better at
17110 optimizing the production code, while enabling us to take more
17111 radical measures to let the unit tests test things.
17112 - The production builds no longer include functions used only in
17113 the unit tests; all functions exposed from a module only for
17114 unit-testing are now static in production builds.
17115 - Add an --enable-coverage configuration option to make the unit
17116 tests (and a new src/or/tor-cov target) to build with gcov test
17120 - We now have rudimentary function mocking support that our unit
17121 tests can use to test functions in isolation. Function mocking
17122 lets the tests temporarily replace a function's dependencies with
17123 stub functions, so that the tests can check the function without
17124 invoking the other functions it calls.
17125 - Add more unit tests for the <circid,channel>->circuit map, and
17126 the destroy-cell-tracking code to fix bug 7912.
17127 - Unit tests for failing cases of the TAP onion handshake.
17128 - More unit tests for address-manipulation functions.
17130 o Minor features (protecting client timestamps):
17131 - Clients no longer send timestamps in their NETINFO cells. These were
17132 not used for anything, and they provided one small way for clients
17133 to be distinguished from each other as they moved from network to
17134 network or behind NAT. Implements part of proposal 222.
17135 - Clients now round timestamps in INTRODUCE cells down to the nearest
17136 10 minutes. If a new Support022HiddenServices option is set to 0, or
17137 if it's set to "auto" and the feature is disabled in the consensus,
17138 the timestamp is sent as 0 instead. Implements part of proposal 222.
17139 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17140 a big deal from a security point of view, but it achieves no actual
17141 good purpose, and isn't needed. Implements part of proposal 222.
17142 - Reduce down accuracy of timestamps in hidden service descriptors.
17143 Implements part of proposal 222.
17145 o Minor features (config options):
17146 - Config (torrc) lines now handle fingerprints which are missing
17147 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
17148 - Support a --dump-config option to print some or all of the
17149 configured options. Mainly useful for debugging the command-line
17150 option parsing code. Helps resolve ticket 4647.
17151 - Raise awareness of safer logging: notify user of potentially
17152 unsafe config options, like logging more verbosely than severity
17153 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
17154 - Add a new configuration option TestingV3AuthVotingStartOffset
17155 that bootstraps a network faster by changing the timing for
17156 consensus votes. Addresses ticket 8532.
17157 - Add a new torrc option "ServerTransportOptions" that allows
17158 bridge operators to pass configuration parameters to their
17159 pluggable transports. Resolves ticket 8929.
17160 - The config (torrc) file now accepts bandwidth and space limits in
17161 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
17162 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
17165 o Minor features (build):
17166 - Add support for `--library-versions` flag. Implements ticket 6384.
17167 - Return the "unexpected sendme" warnings to a warn severity, but make
17168 them rate limited, to help diagnose ticket 8093.
17169 - Detect a missing asciidoc, and warn the user about it, during
17170 configure rather than at build time. Fixes issue 6506. Patch from
17173 o Minor features (other):
17174 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17175 sockets in a single system call. Implements ticket 5129.
17176 - Log current accounting state (bytes sent and received + remaining
17177 time for the current accounting period) in the relay's heartbeat
17178 message. Implements ticket 5526; patch from Peter Retzlaff.
17179 - Implement the TRANSPORT_LAUNCHED control port event that
17180 notifies controllers about new launched pluggable
17181 transports. Resolves ticket 5609.
17182 - If we're using the pure-C 32-bit curve25519_donna implementation
17183 of curve25519, build it with the -fomit-frame-pointer option to
17184 make it go faster on register-starved hosts. This improves our
17185 handshake performance by about 6% on i386 hosts without nacl.
17186 Closes ticket 8109.
17187 - Update to the September 4 2013 Maxmind GeoLite Country database.
17190 - Set the listen() backlog limit to the largest actually supported
17191 on the system, not to the value in a header file. Fixes bug 9716;
17192 bugfix on every released Tor.
17193 - No longer accept malformed http headers when parsing urls from
17194 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17195 bugfix on 0.0.6pre1.
17196 - In munge_extrainfo_into_routerinfo(), check the return value of
17197 memchr(). This would have been a serious issue if we ever passed
17198 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17200 - On the chance that somebody manages to build Tor on a
17201 platform where time_t is unsigned, correct the way that
17202 microdesc_add_to_cache() handles negative time arguments.
17203 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17204 - Reject relative control socket paths and emit a warning. Previously,
17205 single-component control socket paths would be rejected, but Tor
17206 would not log why it could not validate the config. Fixes bug 9258;
17207 bugfix on 0.2.3.16-alpha.
17209 o Minor bugfixes (command line):
17210 - Use a single command-line parser for parsing torrc options on the
17211 command line and for finding special command-line options to avoid
17212 inconsistent behavior for torrc option arguments that have the same
17213 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17215 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17216 9573; bugfix on 0.0.9pre5.
17218 o Minor fixes (build, auxiliary programs):
17219 - Stop preprocessing the "torify" script with autoconf, since
17220 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17222 - The tor-fw-helper program now follows the standard convention and
17223 exits with status code "0" on success. Fixes bug 9030; bugfix on
17224 0.2.3.1-alpha. Patch by Arlo Breault.
17225 - Corrected ./configure advice for what openssl dev package you should
17226 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17228 o Minor code improvements:
17229 - Remove constants and tests for PKCS1 padding; it's insecure and
17230 shouldn't be used for anything new. Fixes bug 8792; patch
17232 - Remove instances of strcpy() from the unit tests. They weren't
17233 hurting anything, since they were only in the unit tests, but it's
17234 embarrassing to have strcpy() in the code at all, and some analysis
17235 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17236 0.2.3.8-alpha. Patch from Arlo Breault.
17238 o Removed features:
17239 - Remove migration code from when we renamed the "cached-routers"
17240 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17241 incidentally resolves ticket 6502 by cleaning up the related code
17242 a bit. Patch from Akshay Hebbar.
17244 o Code simplification and refactoring:
17245 - Extract the common duplicated code for creating a subdirectory
17246 of the data directory and writing to a file in it. Fixes ticket
17247 4282; patch from Peter Retzlaff.
17248 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17249 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17250 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17251 - Add a set of accessor functions for the circuit timeout data
17252 structure. Fixes ticket 6153; patch from "piet".
17253 - Clean up exit paths from connection_listener_new(). Closes ticket
17254 8789. Patch from Arlo Breault.
17255 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17256 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17257 - Use a doubly-linked list to implement the global circuit list.
17258 Resolves ticket 9108. Patch from Marek Majkowski.
17259 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17262 Changes in version 0.2.4.17-rc - 2013-09-05
17263 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
17264 series. It adds an emergency step to help us tolerate the massive
17265 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
17266 circuit-level handshakes now effectively jump the queue compared to
17267 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
17268 big bug hindering bridge reachability tests.
17271 - Relays now process the new "NTor" circuit-level handshake requests
17272 with higher priority than the old "TAP" circuit-level handshake
17273 requests. We still process some TAP requests to not totally starve
17274 0.2.3 clients when NTor becomes popular. A new consensus parameter
17275 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17276 Implements ticket 9574.
17279 - If the circuit build timeout logic is disabled (via the consensus,
17280 or because we are an authority), then don't build testing circuits.
17281 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
17282 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
17283 previously they did not, which prevented them from receiving
17284 successful connections from relays for self-test or bandwidth
17285 testing. Also, when a relay is extending a circuit to a bridge,
17286 it needs to send a NETINFO cell, even when the bridge hasn't sent
17287 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
17288 - If the time to download the next old-style networkstatus is in
17289 the future, do not decline to consider whether to download the
17290 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17294 - Avoid double-closing the listener socket in our socketpair()
17295 replacement (used on Windows) in the case where the addresses on
17296 our opened sockets don't match what we expected. Fixes bug 9400;
17297 bugfix on 0.0.2pre7. Found by Coverity.
17299 o Minor fixes (config options):
17300 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17301 ridiculously high value, by imposing a (ridiculously high) 30-day
17302 maximum on MaxCircuitDirtiness.
17303 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17304 message is logged at notice, not at info.
17305 - Warn and fail if a server is configured not to advertise any
17306 ORPorts at all. (We need *something* to put in our descriptor,
17307 or we just won't work.)
17310 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17311 and how many we complete, and log it every hour to help relay
17312 operators follow trends in network load. Addresses ticket 9658.
17313 - Update to the August 7 2013 Maxmind GeoLite Country database.
17316 Changes in version 0.2.4.16-rc - 2013-08-10
17317 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
17318 series. It fixes several crash bugs in the 0.2.4 branch.
17321 - Fix a bug in the voting algorithm that could yield incorrect results
17322 when a non-naming authority declared too many flags. Fixes bug 9200;
17323 bugfix on 0.2.0.3-alpha.
17324 - Fix an uninitialized read that could in some cases lead to a remote
17325 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
17326 Anybody running a hidden service on the experimental 0.2.4.x
17327 branch should upgrade. (This is, so far as we know, unrelated to
17329 - Avoid an assertion failure when processing DNS replies without the
17330 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
17331 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
17332 0.2.4.15-rc. Found by stem integration tests.
17335 - Fix an invalid memory read that occurred when a pluggable
17336 transport proxy failed its configuration protocol.
17337 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
17338 - When evaluating whether to use a connection that we haven't
17339 decided is canonical using a recent link protocol version,
17340 decide that it's canonical only if it used address _does_
17341 match the desired address. Fixes bug 9309; bugfix on
17342 0.2.4.4-alpha. Reported by skruffy.
17343 - Make the default behavior of NumDirectoryGuards be to track
17344 NumEntryGuards. Now a user who changes only NumEntryGuards will get
17345 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
17346 - Fix a spurious compilation warning with some older versions of
17347 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
17350 - Update to the July 3 2013 Maxmind GeoLite Country database.
17353 Changes in version 0.2.4.15-rc - 2013-07-01
17354 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
17355 series. It fixes a few smaller bugs, but generally appears stable.
17356 Please test it and let us know whether it is!
17359 - When receiving a new configuration file via the control port's
17360 LOADCONF command, do not treat the defaults file as absent.
17361 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17364 - Issue a warning when running with the bufferevents backend enabled.
17365 It's still not stable, and people should know that they're likely
17366 to hit unexpected problems. Closes ticket 9147.
17369 Changes in version 0.2.4.14-alpha - 2013-06-18
17370 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
17371 present in 0.2.4.13-alpha.
17374 - When we have too much memory queued in circuits (according to a new
17375 MaxMemInCellQueues option), close the circuits consuming the most
17376 memory. This prevents us from running out of memory as a relay if
17377 circuits fill up faster than they can be drained. Fixes bug 9063;
17378 bugfix on the 54th commit of Tor. This bug is a further fix beyond
17379 bug 6252, whose fix was merged into 0.2.3.21-rc.
17381 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
17382 where we tried to solve this issue simply by imposing an upper limit
17383 on the number of queued cells for a single circuit. That approach
17384 proved to be problematic, since there are ways to provoke clients to
17385 send a number of cells in excess of any such reasonable limit. Fixes
17386 bug 9072; bugfix on 0.2.4.13-alpha.
17388 - Limit hidden service descriptors to at most ten introduction
17389 points, to slow one kind of guard enumeration. Fixes bug 9002;
17390 bugfix on 0.1.1.11-alpha.
17393 Changes in version 0.2.4.13-alpha - 2013-06-14
17394 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
17395 vulnerabilities, makes socks5 username/password circuit isolation
17396 actually actually work (this time for sure!), and cleans up a bunch
17397 of other issues in preparation for a release candidate.
17399 o Major bugfixes (robustness):
17400 - Close any circuit that has too many cells queued on it. Fixes
17401 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
17402 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
17403 - Prevent the get_freelists() function from running off the end of
17404 the list of freelists if it somehow gets an unrecognized
17405 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17407 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17408 when an exit connection with optimistic data succeeds immediately
17409 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17411 - Fix a directory authority crash bug when building a consensus
17412 using an older consensus as its basis. Fixes bug 8833. Bugfix
17416 - Avoid a memory leak where we would leak a consensus body when we
17417 find that a consensus which we couldn't previously verify due to
17418 missing certificates is now verifiable. Fixes bug 8719; bugfix
17420 - We used to always request authority certificates by identity digest,
17421 meaning we'd get the newest one even when we wanted one with a
17422 different signing key. Then we would complain about being given
17423 a certificate we already had, and never get the one we really
17424 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17425 resource to request the one we want. Fixes bug 5595; bugfix on
17427 - Follow the socks5 protocol when offering username/password
17428 authentication. The fix for bug 8117 exposed this bug, and it
17429 turns out real-world applications like Pidgin do care. Bugfix on
17430 0.2.3.2-alpha; fixes bug 8879.
17431 - Prevent failures on Windows Vista and later when rebuilding the
17432 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
17433 bugfix on 0.2.4.12-alpha.
17436 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17437 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17438 - If for some reason we fail to write a microdescriptor while
17439 rebuilding the cache, do not let the annotations from that
17440 microdescriptor linger in the cache file, and do not let the
17441 microdescriptor stay recorded as present in its old location.
17442 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17443 - Fix a memory leak that would occur whenever a configuration
17444 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17445 - Paste the description for PathBias parameters from the man
17446 page into or.h, so the code documents them too. Fixes bug 7982;
17447 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
17448 - Relays now treat a changed IPv6 ORPort as sufficient reason to
17449 publish an updated descriptor. Fixes bug 6026; bugfix on
17451 - When launching a resolve request on behalf of an AF_UNIX control
17452 socket, omit the address field of the new entry connection, used in
17453 subsequent controller events, rather than letting tor_dup_addr()
17454 set it to "<unknown address type>". Fixes bug 8639; bugfix on
17457 o Minor bugfixes (log messages):
17458 - Fix a scaling issue in the path bias accounting code that
17459 resulted in "Bug:" log messages from either
17460 pathbias_scale_close_rates() or pathbias_count_build_success().
17461 This represents a bugfix on a previous bugfix: the original fix
17462 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
17464 - Give a less useless error message when the user asks for an IPv4
17465 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
17469 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
17470 to tolerate bug 8093 for now.
17471 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17472 in directory authority votes to describe whether they have enough
17473 measured bandwidths to ignore advertised (relay descriptor)
17474 bandwidth claims. Resolves ticket 8711.
17475 - Update to the June 5 2013 Maxmind GeoLite Country database.
17477 o Removed documentation:
17478 - Remove some of the older contents of doc/ as obsolete; move others
17479 to torspec.git. Fixes bug 8965.
17481 o Code simplification and refactoring:
17482 - Avoid using character buffers when constructing most directory
17483 objects: this approach was unwieldy and error-prone. Instead,
17484 build smartlists of strings, and concatenate them when done.
17487 Changes in version 0.2.4.12-alpha - 2013-04-18
17488 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
17489 process for lengthening the guard rotation period, makes directory
17490 authority opinions in the consensus a bit less gameable, makes socks5
17491 username/password circuit isolation actually work, and fixes a wide
17492 variety of other issues.
17495 - Raise the default time that a client keeps an entry guard from
17496 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17497 2012 paper. (We would make it even longer, but we need better client
17498 load balancing first.) Also, make the guard lifetime controllable
17499 via a new GuardLifetime torrc option and a GuardLifetime consensus
17500 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17501 - Directory authorities now prefer using measured bandwidths to
17502 advertised ones when computing flags and thresholds. Resolves
17504 - Directory authorities that have more than a threshold number
17505 of relays with measured bandwidths now treat relays with unmeasured
17506 bandwidths as having bandwidth 0. Resolves ticket 8435.
17508 o Major bugfixes (assert / resource use):
17509 - Avoid a bug where our response to TLS renegotiation under certain
17510 network conditions could lead to a busy-loop, with 100% CPU
17511 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17512 - Avoid an assertion when we discover that we'd like to write a cell
17513 onto a closing connection: just discard the cell. Fixes another
17514 case of bug 7350; bugfix on 0.2.4.4-alpha.
17516 o Major bugfixes (client-side privacy):
17517 - When we mark a circuit as unusable for new circuits, have it
17518 continue to be unusable for new circuits even if MaxCircuitDirtiness
17519 is increased too much at the wrong time, or the system clock jumps
17520 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17521 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17522 which have resolved to internal addresses") is set, apply that
17523 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17524 - When an exit relay rejects a stream with reason "exit policy", but
17525 we only know an exit policy summary (e.g. from the microdesc
17526 consensus) for it, do not mark the relay as useless for all exiting.
17527 Instead, mark just the circuit as unsuitable for that particular
17528 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17529 - Allow applications to get proper stream isolation with
17530 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17531 username/password authentication also offer "no authentication". Tor
17532 had previously preferred "no authentication", so the applications
17533 never actually sent Tor their auth details. Now Tor selects
17534 username/password authentication if it's offered. You can disable
17535 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17536 bug 8117; bugfix on 0.2.3.3-alpha.
17538 o Major bugfixes (other):
17539 - When unable to find any working directory nodes to use as a
17540 directory guard, give up rather than adding the same non-working
17541 nodes to the directory guard list over and over. Fixes bug 8231;
17542 bugfix on 0.2.4.8-alpha.
17545 - Reject as invalid most directory objects containing a NUL.
17546 Belt-and-suspender fix for bug 8037.
17547 - In our testsuite, create temporary directories with a bit more
17548 entropy in their name to make name collisions less likely. Fixes
17550 - Add CACHED keyword to ADDRMAP events in the control protocol
17551 to indicate whether a DNS result will be cached or not. Resolves
17553 - Update to the April 3 2013 Maxmind GeoLite Country database.
17555 o Minor features (build):
17556 - Detect and reject attempts to build Tor with threading support
17557 when OpenSSL has been compiled without threading support.
17559 - Clarify that when autoconf is checking for nacl, it is checking
17560 specifically for nacl with a fast curve25519 implementation.
17562 - Warn if building on a platform with an unsigned time_t: there
17563 are too many places where Tor currently assumes that time_t can
17564 hold negative values. We'd like to fix them all, but probably
17567 o Minor bugfixes (build):
17568 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17569 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17570 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17571 - Add the old src/or/micro-revision.i filename to CLEANFILES.
17572 On the off chance that somebody has one, it will go away as soon
17573 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
17574 - Build Tor correctly on 32-bit platforms where the compiler can build
17575 but not run code using the "uint128_t" construction. Fixes bug 8587;
17576 bugfix on 0.2.4.8-alpha.
17577 - Fix compilation warning with some versions of clang that would
17578 prefer the -Wswitch-enum compiler flag to warn about switch
17579 statements with missing enum values, even if those switch
17580 statements have a "default:" statement. Fixes bug 8598; bugfix
17583 o Minor bugfixes (protocol):
17584 - Fix the handling of a TRUNCATE cell when it arrives while the
17585 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17586 - Fix a misframing issue when reading the version numbers in a
17587 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17588 'version 1, version 2, and version 0x100', when it should have
17589 only included versions 1 and 2. Fixes bug 8059; bugfix on
17590 0.2.0.10-alpha. Reported pseudonymously.
17591 - Make the format and order of STREAM events for DNS lookups
17592 consistent among the various ways to launch DNS lookups. Fixes
17593 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17594 - Correct our check for which versions of Tor support the EXTEND2
17595 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
17596 later, when support was really added in version 0.2.4.8-alpha.
17597 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
17599 o Minor bugfixes (other):
17600 - Correctly store microdescriptors and extrainfo descriptors with
17601 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
17602 Bug reported by "cypherpunks".
17603 - Increase the width of the field used to remember a connection's
17604 link protocol version to two bytes. Harmless for now, since the
17605 only currently recognized versions are one byte long. Reported
17606 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17607 - If the state file's path bias counts are invalid (presumably from a
17608 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17609 additional checks and log messages to the scaling of Path Bias
17610 counts, in case there still are remaining issues with scaling.
17611 Should help resolve bug 8235.
17612 - Eliminate several instances where we use "Nickname=ID" to refer to
17613 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17614 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17615 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
17617 o Minor bugfixes (syscalls):
17618 - Always check the return values of functions fcntl() and
17619 setsockopt(). We don't believe these are ever actually failing in
17620 practice, but better safe than sorry. Also, checking these return
17621 values should please analysis tools like Coverity. Patch from
17622 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17623 - Use direct writes rather than stdio when building microdescriptor
17624 caches, in an attempt to mitigate bug 8031, or at least make it
17627 o Minor bugfixes (config):
17628 - When rejecting a configuration because we were unable to parse a
17629 quoted string, log an actual error message. Fixes bug 7950; bugfix
17631 - Behave correctly when the user disables LearnCircuitBuildTimeout
17632 but doesn't tell us what they would like the timeout to be. Fixes
17633 bug 6304; bugfix on 0.2.2.14-alpha.
17634 - When autodetecting the number of CPUs, use the number of available
17635 CPUs in preference to the number of configured CPUs. Inform the
17636 user if this reduces the number of available CPUs. Fixes bug 8002;
17637 bugfix on 0.2.3.1-alpha.
17638 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17639 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17640 bug 8180; bugfix on 0.2.3.11-alpha.
17641 - Allow TestingTorNetworks to override the 4096-byte minimum for
17642 the Fast threshold. Otherwise they can't bootstrap until they've
17643 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
17644 - Fix some logic errors when the user manually overrides the
17645 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
17648 o Minor bugfixes (log messages to help diagnose bugs):
17649 - If we fail to free a microdescriptor because of bug 7164, log
17650 the filename and line number from which we tried to free it.
17651 - Add another diagnostic to the heartbeat message: track and log
17652 overhead that TLS is adding to the data we write. If this is
17653 high, we are sending too little data to SSL_write at a time.
17654 Diagnostic for bug 7707.
17655 - Add more detail to a log message about relaxed timeouts, to help
17657 - Warn more aggressively when flushing microdescriptors to a
17658 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17659 or at least make it more diagnosable.
17660 - Improve debugging output to help track down bug 8185 ("Bug:
17661 outgoing relay cell has n_chan==NULL. Dropping.")
17662 - Log the purpose of a path-bias testing circuit correctly.
17663 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
17665 o Minor bugfixes (0.2.4.x log messages that were too noisy):
17666 - Don't attempt to relax the timeout of already opened 1-hop circuits.
17667 They might never timeout. This should eliminate some/all cases of
17668 the relaxed timeout log message.
17669 - Use circuit creation time for network liveness evaluation. This
17670 should eliminate warning log messages about liveness caused
17671 by changes in timeout evaluation. Fixes bug 6572; bugfix on
17673 - Reduce a path bias length check from notice to info. The message
17674 is triggered when creating controller circuits. Fixes bug 8196;
17675 bugfix on 0.2.4.8-alpha.
17676 - Fix a path state issue that triggered a notice during relay startup.
17677 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
17678 - Reduce occurrences of warns about circuit purpose in
17679 connection_ap_expire_building(). Fixes bug 8477; bugfix on
17682 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
17683 - If we encounter a write failure on a SOCKS connection before we
17684 finish our SOCKS handshake, don't warn that we closed the
17685 connection before we could send a SOCKS reply. Fixes bug 8427;
17686 bugfix on 0.1.0.1-rc.
17687 - Correctly recognize that [::1] is a loopback address. Fixes
17688 bug 8377; bugfix on 0.2.1.3-alpha.
17689 - Fix a directory authority warn caused when we have a large amount
17690 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17691 - Don't log inappropriate heartbeat messages when hibernating: a
17692 hibernating node is _expected_ to drop out of the consensus,
17693 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17694 bugfix on 0.2.3.1-alpha.
17695 - Don't complain about bootstrapping problems while hibernating.
17696 These complaints reflect a general code problem, but not one
17697 with any problematic effects (no connections are actually
17698 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17700 o Documentation fixes:
17701 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17702 names match. Fixes bug 7768.
17703 - Make the torify manpage no longer refer to tsocks; torify hasn't
17704 supported tsocks since 0.2.3.14-alpha.
17705 - Make the tor manpage no longer reference tsocks.
17706 - Fix the GeoIPExcludeUnknown documentation to refer to
17707 ExcludeExitNodes rather than the currently nonexistent
17708 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17711 - The tor-tsocks.conf is no longer distributed or installed. We
17712 recommend that tsocks users use torsocks instead. Resolves
17716 Changes in version 0.2.4.11-alpha - 2013-03-11
17717 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17718 more robust, makes hidden service authentication work again, and
17719 resolves a DPI fingerprint for Tor's SSL transport.
17721 o Major features (directory authorities):
17722 - Directory authorities now support a new consensus method (17)
17723 where they cap the published bandwidth of servers for which
17724 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17725 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17726 serve any v2 directory information. Now we can test disabling the
17727 old deprecated v2 directory format, and see whether doing so has
17728 any effect on network load. Begins to fix bug 6783.
17729 - Directory authorities now include inside each vote a statement of
17730 the performance thresholds they used when assigning flags.
17731 Implements ticket 8151.
17733 o Major bugfixes (directory authorities):
17734 - Stop marking every relay as having been down for one hour every
17735 time we restart a directory authority. These artificial downtimes
17736 were messing with our Stable and Guard flag calculations. Fixes
17737 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17739 o Major bugfixes (hidden services):
17740 - Allow hidden service authentication to succeed again. When we
17741 refactored the hidden service introduction code back
17742 in 0.2.4.1-alpha, we didn't update the code that checks
17743 whether authentication information is present, causing all
17744 authentication checks to return "false". Fix for bug 8207; bugfix
17745 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17747 o Minor features (relays, bridges):
17748 - Make bridge relays check once a minute for whether their IP
17749 address has changed, rather than only every 15 minutes. Resolves
17750 bugs 1913 and 1992.
17751 - Refactor resolve_my_address() so it returns the method by which we
17752 decided our public IP address (explicitly configured, resolved from
17753 explicit hostname, guessed from interfaces, learned by gethostname).
17754 Now we can provide more helpful log messages when a relay guesses
17755 its IP address incorrectly (e.g. due to unexpected lines in
17756 /etc/hosts). Resolves ticket 2267.
17757 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17758 microdescriptor-related dir requests, and only fall back to normal
17759 descriptors if none of their bridges can handle microdescriptors
17760 (as opposed to the fix in ticket 4013, which caused them to fall
17761 back to normal descriptors if *any* of their bridges preferred
17762 them). Resolves ticket 4994.
17763 - Randomize the lifetime of our SSL link certificate, so censors can't
17764 use the static value for filtering Tor flows. Resolves ticket 8443;
17765 related to ticket 4014 which was included in 0.2.2.33.
17766 - Support a new version of the link protocol that allows 4-byte circuit
17767 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17768 a possible resource exhaustion issue. Closes ticket 7351; implements
17771 o Minor features (portability):
17772 - Tweak the curve25519-donna*.c implementations to tolerate systems
17773 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17774 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17775 the signs of types during autoconf. This is better than our old
17776 approach, which didn't work when cross-compiling.
17777 - Detect the sign of enum values, rather than assuming that MSC is the
17778 only compiler where enum types are all signed. Fixes bug 7727;
17779 bugfix on 0.2.4.10-alpha.
17781 o Minor features (other):
17782 - Say "KBytes" rather than "KB" in the man page (for various values
17783 of K), to further reduce confusion about whether Tor counts in
17784 units of memory or fractions of units of memory. Resolves ticket 7054.
17785 - Clear the high bit on curve25519 public keys before passing them to
17786 our backend, in case we ever wind up using a backend that doesn't do
17787 so itself. If we used such a backend, and *didn't* clear the high bit,
17788 we could wind up in a situation where users with such backends would
17789 be distinguishable from users without. Fixes bug 8121; bugfix on
17791 - Update to the March 6 2013 Maxmind GeoLite Country database.
17793 o Minor bugfixes (clients):
17794 - When we receive a RELAY_END cell with the reason DONE, or with no
17795 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17796 status as "connection refused". Previously we reported these cases
17797 as success but then immediately closed the connection. Fixes bug
17798 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17799 - Downgrade an assertion in connection_ap_expire_beginning to an
17800 LD_BUG message. The fix for bug 8024 should prevent this message
17801 from displaying, but just in case, a warn that we can diagnose
17802 is better than more assert crashes. Fixes bug 8065; bugfix on
17804 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17805 Also make the rate limiting flags for the path use bias log messages
17806 independent from the original path bias flags. Fixes bug 8161;
17807 bugfix on 0.2.4.10-alpha.
17809 o Minor bugfixes (relays):
17810 - Stop trying to resolve our hostname so often (e.g. every time we
17811 think about doing a directory fetch). Now we reuse the cached
17812 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17813 and 2410 (bugfix on 0.1.2.2-alpha).
17814 - Stop sending a stray "(null)" in some cases for the server status
17815 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17817 - When choosing which stream on a formerly stalled circuit to wake
17818 first, make better use of the platform's weak RNG. Previously,
17819 we had been using the % ("modulo") operator to try to generate a
17820 1/N chance of picking each stream, but this behaves badly with
17821 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17823 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17824 Irix's random() only return 15 bits; Solaris's random() returns more
17825 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17826 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17828 o Minor bugfixes (directory authorities):
17829 - Directory authorities now use less space when formatting identical
17830 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17833 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17834 - Avoid leaking memory if we fail to compute a consensus signature
17835 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17836 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17838 - Fix a memory leak during safe-cookie controller authentication.
17839 Bugfix on 0.2.3.13-alpha.
17840 - Avoid memory leak of IPv6 policy content if we fail to format it into
17841 a router descriptor. Bugfix on 0.2.4.7-alpha.
17843 o Minor bugfixes (other code correctness issues):
17844 - Avoid a crash if we fail to generate an extrainfo descriptor.
17845 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17846 this is CID 718634.
17847 - When detecting the largest possible file descriptor (in order to
17848 close all file descriptors when launching a new program), actually
17849 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17850 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17852 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17853 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17854 Bugfix on 0.2.4.10-alpha.
17855 - Fix an impossible-to-trigger integer overflow when estimating how
17856 long our onionskin queue would take. (This overflow would require us
17857 to accept 4 million onionskins before processing 100 of them.) Fixes
17858 bug 8210; bugfix on 0.2.4.10-alpha.
17860 o Code simplification and refactoring:
17861 - Add a wrapper function for the common "log a message with a
17865 Changes in version 0.2.4.10-alpha - 2013-02-04
17866 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17867 certain attacks that flood the network with relays; changes the queue
17868 for circuit create requests from a sized-based limit to a time-based
17869 limit; resumes building with MSVC on Windows; and fixes a wide variety
17872 o Major bugfixes (directory authority):
17873 - When computing directory thresholds, ignore any rejected-as-sybil
17874 nodes during the computation so that they can't influence Fast,
17875 Guard, etc. (We should have done this for proposal 109.) Fixes
17877 - When marking a node as a likely sybil, reset its uptime metrics
17878 to zero, so that it cannot time towards getting marked as Guard,
17879 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17883 - When a TLS write is partially successful but incomplete, remember
17884 that the flushed part has been flushed, and notice that bytes were
17885 actually written. Reported and fixed pseudonymously. Fixes bug
17886 7708; bugfix on Tor 0.1.0.5-rc.
17887 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17888 ID: these could be used to create unexpected streams and circuits
17889 which would count as "present" to some parts of Tor but "absent"
17890 to others, leading to zombie circuits and streams or to a bandwidth
17891 denial-of-service. Fixes bug 7889; bugfix on every released version
17892 of Tor. Reported by "oftc_must_be_destroyed".
17893 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17894 This change seems the only good way to permanently prevent conflicts
17895 with queue.h on various operating systems. Fixes bug 8107; bugfix
17898 o Major features (relay):
17899 - Instead of limiting the number of queued onionskins (aka circuit
17900 create requests) to a fixed, hard-to-configure number, we limit
17901 the size of the queue based on how many we expect to be able to
17902 process in a given amount of time. We estimate the time it will
17903 take to process an onionskin based on average processing time
17904 of previous onionskins. Closes ticket 7291. You'll never have to
17905 configure MaxOnionsPending again.
17907 o Major features (portability):
17908 - Resume building correctly with MSVC and Makefile.nmake. This patch
17909 resolves numerous bugs and fixes reported by ultramage, including
17910 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17911 - Make the ntor and curve25519 code build correctly with MSVC.
17912 Fix on 0.2.4.8-alpha.
17915 - When directory authorities are computing thresholds for flags,
17916 never let the threshold for the Fast flag fall below 4096
17917 bytes. Also, do not consider nodes with extremely low bandwidths
17918 when deciding thresholds for various directory flags. This change
17919 should raise our threshold for Fast relays, possibly in turn
17920 improving overall network performance; see ticket 1854. Resolves
17922 - The Tor client now ignores sub-domain components of a .onion
17923 address. This change makes HTTP "virtual" hosting
17924 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
17925 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
17926 hosted on the same hidden service. Implements proposal 204.
17927 - We compute the overhead from passing onionskins back and forth to
17928 cpuworkers, and report it when dumping statistics in response to
17929 SIGUSR1. Supports ticket 7291.
17931 o Minor features (path selection):
17932 - When deciding whether we have enough descriptors to build circuits,
17933 instead of looking at raw relay counts, look at which fraction
17934 of (bandwidth-weighted) paths we're able to build. This approach
17935 keeps clients from building circuits if their paths are likely to
17936 stand out statistically. The default fraction of paths needed is
17937 taken from the consensus directory; you can override it with the
17938 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
17939 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
17940 and we have GeoIP information, also exclude all nodes with unknown
17941 countries "??" and "A1". This behavior is controlled by the
17942 new GeoIPExcludeUnknown option: you can make such nodes always
17943 excluded with "GeoIPExcludeUnknown 1", and disable the feature
17944 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
17945 gets you the default behavior. Implements feature 7706.
17946 - Path Use Bias: Perform separate accounting for successful circuit
17947 use. Keep separate statistics on stream attempt rates versus stream
17948 success rates for each guard. Provide configurable thresholds to
17949 determine when to emit log messages or disable use of guards that
17950 fail too many stream attempts. Resolves ticket 7802.
17952 o Minor features (log messages):
17953 - When learning a fingerprint for a bridge, log its corresponding
17954 transport type. Implements ticket 7896.
17955 - Improve the log message when "Bug/attack: unexpected sendme cell
17956 from client" occurs, to help us track bug 8093.
17959 - Remove a couple of extraneous semicolons that were upsetting the
17960 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
17961 bugfix on 0.2.2.1-alpha.
17962 - Remove a source of rounding error during path bias count scaling;
17963 don't count cannibalized circuits as used for path bias until we
17964 actually try to use them; and fix a circuit_package_relay_cell()
17965 warning message about n_chan==NULL. Fixes bug 7802.
17966 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
17967 actually link against nacl when we're configured to use it. Fixes
17968 bug 7972; bugfix on 0.2.4.8-alpha.
17969 - Compile correctly with the --disable-curve25519 option. Fixes
17970 bug 8153; bugfix on 0.2.4.8-alpha.
17972 o Build improvements:
17973 - Do not report status verbosely from autogen.sh unless the -v flag
17974 is specified. Fixes issue 4664. Patch from Onizuka.
17975 - Replace all calls to snprintf() outside of src/ext with
17976 tor_snprintf(). Also remove the #define to replace snprintf with
17977 _snprintf on Windows; they have different semantics, and all of
17978 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
17979 - Try to detect if we are ever building on a platform where
17980 memset(...,0,...) does not set the value of a double to 0.0. Such
17981 platforms are permitted by the C standard, though in practice
17982 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
17983 currently support them, but it's better to detect them and fail
17984 than to perform erroneously.
17986 o Removed features:
17987 - Stop exporting estimates of v2 and v3 directory traffic shares
17988 in extrainfo documents. They were unneeded and sometimes inaccurate.
17989 Also stop exporting any v2 directory request statistics. Resolves
17991 - Drop support for detecting and warning about versions of Libevent
17992 before 1.3e. Nothing reasonable ships with them any longer;
17993 warning the user about them shouldn't be needed. Resolves ticket
17996 o Code simplifications and refactoring:
17997 - Rename "isin" functions to "contains", for grammar. Resolves
17999 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
18000 with the natural logarithm function from the system libm. Resolves
18004 Changes in version 0.2.4.9-alpha - 2013-01-15
18005 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
18006 work more robustly.
18009 - Fix backward compatibility logic when receiving an embedded ntor
18010 handshake tunneled in a CREATE cell. This clears up the "Bug:
18011 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
18015 Changes in version 0.2.4.8-alpha - 2013-01-14
18016 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
18017 risks, adds a new stronger and faster circuit handshake, and offers
18018 stronger and faster link encryption when both sides support it.
18021 - Preliminary support for directory guards (proposal 207): when
18022 possible, clients now use their entry guards for non-anonymous
18023 directory requests. This can help prevent client enumeration. Note
18024 that this behavior only works when we have a usable consensus
18025 directory, and when options about what to download are more or less
18026 standard. In the future we should re-bootstrap from our guards,
18027 rather than re-bootstrapping from the preconfigured list of
18028 directory sources that ships with Tor. Resolves ticket 6526.
18029 - Tor relays and clients now support a better CREATE/EXTEND cell
18030 format, allowing the sender to specify multiple address, identity,
18031 and handshake types. Implements Robert Ransom's proposal 200;
18032 closes ticket 7199.
18034 o Major features (new circuit handshake):
18035 - Tor now supports a new circuit extension handshake designed by Ian
18036 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
18037 circuit extension handshake, later called "TAP", was a bit slow
18038 (especially on the relay side), had a fragile security proof, and
18039 used weaker keys than we'd now prefer. The new circuit handshake
18040 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
18041 function, making it significantly more secure than the older
18042 handshake, and significantly faster. Tor can use one of two built-in
18043 pure-C curve25519-donna implementations by Adam Langley, or it
18044 can link against the "nacl" library for a tuned version if present.
18046 The built-in version is very fast for 64-bit systems when building
18047 with GCC. The built-in 32-bit version is still faster than the
18048 old TAP protocol, but using libnacl is better on most such hosts.
18050 Clients don't currently use this protocol by default, since
18051 comparatively few clients support it so far. To try it, set
18052 UseNTorHandshake to 1.
18054 Implements proposal 216; closes ticket 7202.
18056 o Major features (better link encryption):
18057 - Relays can now enable the ECDHE TLS ciphersuites when available
18058 and appropriate. These ciphersuites let us negotiate forward-secure
18059 TLS secret keys more safely and more efficiently than with our
18060 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
18061 public relays prefer the (faster) P224 group, and bridges prefer
18062 the (more common) P256 group; you can override this with the
18065 Enabling these ciphers was a little tricky, since for a long time,
18066 clients had been claiming to support them without actually doing
18067 so, in order to foil fingerprinting. But with the client-side
18068 implementation of proposal 198 in 0.2.3.17-beta, clients can now
18069 match the ciphers from recent Firefox versions *and* list the
18070 ciphers they actually mean, so relays can believe such clients
18071 when they advertise ECDHE support in their TLS ClientHello messages.
18073 This feature requires clients running 0.2.3.17-beta or later,
18074 and requires both sides to be running OpenSSL 1.0.0 or later
18075 with ECC support. OpenSSL 1.0.1, with the compile-time option
18076 "enable-ec_nistp_64_gcc_128", is highly recommended.
18078 Implements the relay side of proposal 198; closes ticket 7200.
18081 - Avoid crashing when, as a relay without IPv6-exit support, a
18082 client insists on getting an IPv6 address or nothing. Fixes bug
18083 7814; bugfix on 0.2.4.7-alpha.
18086 - Improve circuit build timeout handling for hidden services.
18087 In particular: adjust build timeouts more accurately depending
18088 upon the number of hop-RTTs that a particular circuit type
18089 undergoes. Additionally, launch intro circuits in parallel
18090 if they timeout, and take the first one to reply as valid.
18091 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
18092 separate error codes; or at least, don't break for that reason.
18093 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
18094 - Update to the January 2 2013 Maxmind GeoLite Country database.
18096 o Minor features (testing):
18097 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
18098 (P-256) Diffie-Hellman handshakes to src/or/bench.
18099 - Add benchmark functions to test onion handshake performance.
18101 o Minor features (path bias detection):
18102 - Alter the Path Bias log messages to be more descriptive in terms
18103 of reporting timeouts and other statistics.
18104 - Create three levels of Path Bias log messages, as opposed to just
18105 two. These are configurable via consensus as well as via the torrc
18106 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
18107 The default values are 0.70, 0.50, and 0.30 respectively.
18108 - Separate the log message levels from the decision to drop guards,
18109 which also is available via torrc option PathBiasDropGuards.
18110 PathBiasDropGuards still defaults to 0 (off).
18111 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
18112 in combination with PathBiasExtremeRate.
18113 - Increase the default values for PathBiasScaleThreshold and
18114 PathBiasCircThreshold from (200, 20) to (300, 150).
18115 - Add in circuit usage accounting to path bias. If we try to use a
18116 built circuit but fail for any reason, it counts as path bias.
18117 Certain classes of circuits where the adversary gets to pick your
18118 destination node are exempt from this accounting. Usage accounting
18119 can be specifically disabled via consensus parameter or torrc.
18120 - Convert all internal path bias state to double-precision floating
18121 point, to avoid roundoff error and other issues.
18122 - Only record path bias information for circuits that have completed
18123 *two* hops. Assuming end-to-end tagging is the attack vector, this
18124 makes us more resilient to ambient circuit failure without any
18125 detection capability loss.
18127 o Minor bugfixes (log messages):
18128 - Rate-limit the "No circuits are opened. Relaxed timeout for a
18129 circuit with channel state open..." message to once per hour to
18130 keep it from filling the notice logs. Mitigates bug 7799 but does
18131 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
18132 - Avoid spurious warnings when configuring multiple client ports of
18133 which only some are nonlocal. Previously, we had claimed that some
18134 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
18137 o Code simplifications and refactoring:
18138 - Get rid of a couple of harmless clang warnings, where we compared
18139 enums to ints. These warnings are newly introduced in clang 3.2.
18140 - Split the onion.c file into separate modules for the onion queue
18141 and the different handshakes it supports.
18142 - Remove the marshalling/unmarshalling code for sending requests to
18143 cpuworkers over a socket, and instead just send structs. The
18144 recipient will always be the same Tor binary as the sender, so
18145 any encoding is overkill.
18148 Changes in version 0.2.4.7-alpha - 2012-12-24
18149 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
18150 directory mirrors for more robust bootstrapping; fixes more issues where
18151 clients with changing network conditions refuse to make any circuits;
18152 adds initial support for exiting to IPv6 addresses; resumes being able
18153 to update our GeoIP database, and includes the geoip6 file this time;
18154 turns off the client-side DNS cache by default due to privacy risks;
18155 and fixes a variety of other issues.
18157 o Major features (client resilience):
18158 - Add a new "FallbackDir" torrc option to use when we can't use
18159 a directory mirror from the consensus (either because we lack a
18160 consensus, or because they're all down). Currently, all authorities
18161 are fallbacks by default, and there are no other default fallbacks,
18162 but that will change. This option will allow us to give clients a
18163 longer list of servers to try to get a consensus from when first
18164 connecting to the Tor network, and thereby reduce load on the
18165 directory authorities. Implements proposal 206, "Preconfigured
18166 directory sources for bootstrapping". We also removed the old
18167 "FallbackNetworkstatus" option, since we never got it working well
18168 enough to use it. Closes bug 572.
18169 - If we have no circuits open, use a relaxed timeout (the
18170 95-percentile cutoff) until a circuit succeeds. This heuristic
18171 should allow Tor to succeed at building circuits even when the
18172 network connection drastically changes. Should help with bug 3443.
18174 o Major features (IPv6):
18175 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18176 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18177 exit policy reads as you would like: the address * applies to all
18178 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18179 addresses only. On the client side, you'll need to wait until the
18180 authorities have upgraded, wait for enough exits to support IPv6,
18181 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
18182 ticket 5547, implements proposal 117 as revised in proposal 208.
18184 We DO NOT recommend that clients with actual anonymity needs start
18185 using IPv6 over Tor yet, since not enough exits support it yet.
18187 o Major features (geoip database):
18188 - Maxmind began labelling Tor relays as being in country "A1",
18189 which breaks by-country node selection inside Tor. Now we use a
18190 script to replace "A1" ("Anonymous Proxy") entries in our geoip
18191 file with real country codes. This script fixes about 90% of "A1"
18192 entries automatically and uses manual country code assignments to
18193 fix the remaining 10%. See src/config/README.geoip for details.
18194 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
18195 Country database, as modified above.
18197 o Major bugfixes (client-side DNS):
18198 - Turn off the client-side DNS cache by default. Updating and using
18199 the DNS cache is now configurable on a per-client-port
18200 level. SOCKSPort, DNSPort, etc lines may now contain
18201 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18202 cache these types of DNS answers when we receive them from an
18203 exit node in response to an application request on this port, and
18204 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18205 cached DNS answers of these types, we shouldn't use them. It's
18206 potentially risky to use cached DNS answers at the client, since
18207 doing so can indicate to one exit what answers we've gotten
18208 for DNS lookups in the past. With IPv6, this becomes especially
18209 problematic. Using cached DNS answers for requests on the same
18210 circuit would present less linkability risk, since all traffic
18211 on a circuit is already linkable, but it would also provide
18212 little performance benefit: the exit node caches DNS replies
18213 too. Implements a simplified version of Proposal 205. Implements
18216 o Major bugfixes (other):
18217 - Alter circuit build timeout measurement to start at the point
18218 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18219 initialization). This should make our timeout measurements more
18220 uniform. Previously, we were sometimes including ORconn setup time
18221 in our circuit build time measurements. Should resolve bug 3443.
18222 - Fix an assertion that could trigger in hibernate_go_dormant() when
18223 closing an or_connection_t: call channel_mark_for_close() rather
18224 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
18226 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
18227 7655; bugfix on 0.2.4.6-alpha.
18230 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18231 operators select the address where their pluggable transports will
18232 listen for connections. Resolves ticket 7013.
18233 - Allow an optional $ before the node identity digest in the
18234 controller command GETINFO ns/id/<identity>, for consistency with
18235 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18236 - Log packaged cell fullness as part of the heartbeat message.
18237 Diagnosis to try to determine the extent of bug 7743.
18239 o Minor features (IPv6):
18240 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18241 prefer to hand out virtual IPv6 addresses, since there are more of
18242 them and we can't run out. To override this behavior and make IPv4
18243 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18244 or DNSPort you're using for resolving. Implements ticket 7571.
18245 - AutomapHostsOnResolve responses are now randomized, to avoid
18246 annoying situations where Tor is restarted and applications
18247 connect to the wrong addresses.
18248 - Never try more than 1000 times to pick a new virtual address when
18249 AutomapHostsOnResolve is set. That's good enough so long as we
18250 aren't close to handing out our entire virtual address space;
18251 if you're getting there, it's best to switch to IPv6 virtual
18255 - The ADDRMAP command can no longer generate an ill-formed error
18256 code on a failed MAPADDRESS. It now says "internal" rather than
18257 an English sentence fragment with spaces in the middle. Bugfix on
18258 Tor 0.2.0.19-alpha.
18259 - Fix log messages and comments to avoid saying "GMT" when we mean
18260 "UTC". Fixes bug 6113.
18261 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18263 - Fix a crash when debugging unit tests on Windows: deallocate a
18264 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
18265 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
18268 - The DirServer option is now DirAuthority, for consistency with
18269 current naming patterns. You can still use the old DirServer form.
18271 o Code simplification and refactoring:
18272 - Move the client-side address-map/virtual-address/DNS-cache code
18273 out of connection_edge.c into a new addressmap.c module.
18274 - Remove unused code for parsing v1 directories and "running routers"
18275 documents. Fixes bug 6887.
18278 Changes in version 0.2.3.25 - 2012-11-19
18279 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18280 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18281 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18282 programmer, and friend. Unstinting in his dedication to the cause of
18283 freedom, he inspired and helped many of us as we began our work on
18284 anonymity, and inspires us still. Please honor his memory by writing
18285 software to protect people's freedoms, and by helping others to do so.
18287 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18288 significantly reduced directory overhead (via microdescriptors),
18289 enormous crypto performance improvements for fast relays on new
18290 enough hardware, a new v3 TLS handshake protocol that can better
18291 resist fingerprinting, support for protocol obfuscation plugins (aka
18292 pluggable transports), better scalability for hidden services, IPv6
18293 support for bridges, performance improvements like allowing clients
18294 to skip the first round-trip on the circuit ("optimistic data") and
18295 refilling token buckets more often, a new "stream isolation" design
18296 to isolate different applications on different circuits, and many
18297 stability, security, and privacy fixes.
18300 - Tor tries to wipe potentially sensitive data after using it, so
18301 that if some subsequent security failure exposes Tor's memory,
18302 the damage will be limited. But we had a bug where the compiler
18303 was eliminating these wipe operations when it decided that the
18304 memory was no longer visible to a (correctly running) program,
18305 hence defeating our attempt at defense in depth. We fix that
18306 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18307 is unlikely to optimize away. Future versions of Tor may use
18308 a less ridiculously heavy approach for this. Fixes bug 7352.
18309 Reported in an article by Andrey Karpov.
18312 - Fix a harmless bug when opting against publishing a relay descriptor
18313 because DisableNetwork is set. Fixes bug 7464; bugfix on
18317 Changes in version 0.2.4.6-alpha - 2012-11-13
18318 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
18319 makes our defense-in-depth memory wiping more reliable, and begins to
18320 count IPv6 addresses in bridge statistics,
18323 - Fix an assertion failure that could occur when closing a connection
18324 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
18326 - Tor tries to wipe potentially sensitive data after using it, so
18327 that if some subsequent security failure exposes Tor's memory,
18328 the damage will be limited. But we had a bug where the compiler
18329 was eliminating these wipe operations when it decided that the
18330 memory was no longer visible to a (correctly running) program,
18331 hence defeating our attempt at defense in depth. We fix that
18332 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18333 is unlikely to optimize away. Future versions of Tor may use
18334 a less ridiculously heavy approach for this. Fixes bug 7352.
18335 Reported in an article by Andrey Karpov.
18338 - Add GeoIP database for IPv6 addresses. The new config option
18340 - Bridge statistics now count bridge clients connecting over IPv6:
18341 bridge statistics files now list "bridge-ip-versions" and
18342 extra-info documents list "geoip6-db-digest". The control protocol
18343 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18344 implementation by "shkoo", addressing ticket 5055.
18347 - Warn when we are binding low ports when hibernation is enabled;
18348 previously we had warned when we were _advertising_ low ports with
18349 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18350 - Fix a harmless bug when opting against publishing a relay descriptor
18351 because DisableNetwork is set. Fixes bug 7464; bugfix on
18353 - Add warning message when a managed proxy dies during configuration.
18354 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
18355 - Fix a linking error when building tor-fw-helper without miniupnp.
18356 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
18357 - Check for closing an or_connection_t without going through correct
18358 channel functions; emit a warning and then call
18359 connection_or_close_for_error() so we don't assert as in bugs 7212
18361 - Compile correctly on compilers without C99 designated initializer
18362 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
18363 - Avoid a possible assert that can occur when channel_send_destroy() is
18364 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
18365 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
18366 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
18367 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
18368 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
18370 o Code simplification and refactoring:
18371 - Start using OpenBSD's implementation of queue.h, so that we don't
18372 need to hand-roll our own pointer and list structures whenever we
18373 need them. (We can't rely on a sys/queue.h, since some operating
18374 systems don't have them, and the ones that do have them don't all
18375 present the same extensions.)
18378 Changes in version 0.2.4.5-alpha - 2012-10-25
18379 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
18380 two important security vulnerabilities that could lead to remotely
18381 triggerable relay crashes, fix a major bug that was preventing clients
18382 from choosing suitable exit nodes, and refactor some of our code.
18384 o Major bugfixes (security, also in 0.2.3.24-rc):
18385 - Fix a group of remotely triggerable assertion failures related to
18386 incorrect link protocol negotiation. Found, diagnosed, and fixed
18387 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18389 - Fix a denial of service attack by which any directory authority
18390 could crash all the others, or by which a single v2 directory
18391 authority could crash everybody downloading v2 directory
18392 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18394 o Major bugfixes (also in 0.2.3.24-rc):
18395 - When parsing exit policy summaries from microdescriptors, we had
18396 previously been ignoring the last character in each one, so that
18397 "accept 80,443,8080" would be treated by clients as indicating
18398 a node that allows access to ports 80, 443, and 808. That would
18399 lead to clients attempting connections that could never work,
18400 and ignoring exit nodes that would support their connections. Now
18401 clients parse these exit policy summaries correctly. Fixes bug 7192;
18402 bugfix on 0.2.3.1-alpha.
18404 o Minor bugfixes (also in 0.2.3.24-rc):
18405 - Clients now consider the ClientRejectInternalAddresses config option
18406 when using a microdescriptor consensus stanza to decide whether
18407 an exit relay would allow exiting to an internal address. Fixes
18408 bug 7190; bugfix on 0.2.3.1-alpha.
18411 - Only disable TLS session ticket support when running as a TLS
18412 server. Now clients will blend better with regular Firefox
18413 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18415 o Code simplification and refactoring:
18416 - Start using OpenBSD's implementation of queue.h (originally by
18418 - Move the entry node code from circuitbuild.c to its own file.
18419 - Move the circuit build timeout tracking code from circuitbuild.c
18423 Changes in version 0.2.3.24-rc - 2012-10-25
18424 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
18425 could lead to remotely triggerable relay crashes, and fixes
18426 a major bug that was preventing clients from choosing suitable exit
18429 o Major bugfixes (security):
18430 - Fix a group of remotely triggerable assertion failures related to
18431 incorrect link protocol negotiation. Found, diagnosed, and fixed
18432 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18434 - Fix a denial of service attack by which any directory authority
18435 could crash all the others, or by which a single v2 directory
18436 authority could crash everybody downloading v2 directory
18437 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18440 - When parsing exit policy summaries from microdescriptors, we had
18441 previously been ignoring the last character in each one, so that
18442 "accept 80,443,8080" would be treated by clients as indicating
18443 a node that allows access to ports 80, 443, and 808. That would
18444 lead to clients attempting connections that could never work,
18445 and ignoring exit nodes that would support their connections. Now
18446 clients parse these exit policy summaries correctly. Fixes bug 7192;
18447 bugfix on 0.2.3.1-alpha.
18450 - Clients now consider the ClientRejectInternalAddresses config option
18451 when using a microdescriptor consensus stanza to decide whether
18452 an exit relay would allow exiting to an internal address. Fixes
18453 bug 7190; bugfix on 0.2.3.1-alpha.
18456 Changes in version 0.2.4.4-alpha - 2012-10-20
18457 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
18458 vulnerability introduced by a change in OpenSSL, fixes a remotely
18459 triggerable assert, and adds new channel_t and circuitmux_t abstractions
18460 that will make it easier to test new connection transport and cell
18461 scheduling algorithms.
18463 o New directory authorities (also in 0.2.3.23-rc):
18464 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18465 authority. Closes ticket 5749.
18467 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
18468 - Disable TLS session tickets. OpenSSL's implementation was giving
18469 our TLS session keys the lifetime of our TLS context objects, when
18470 perfect forward secrecy would want us to discard anything that
18471 could decrypt a link connection as soon as the link connection
18472 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18473 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18474 - Discard extraneous renegotiation attempts once the V3 link
18475 protocol has been initiated. Failure to do so left us open to
18476 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18477 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18479 o Internal abstraction features:
18480 - Introduce new channel_t abstraction between circuits and
18481 or_connection_t to allow for implementing alternate OR-to-OR
18482 transports. A channel_t is an abstract object which can either be a
18483 cell-bearing channel, which is responsible for authenticating and
18484 handshaking with the remote OR and transmitting cells to and from
18485 it, or a listening channel, which spawns new cell-bearing channels
18486 at the request of remote ORs. Implements part of ticket 6465.
18487 - Also new is the channel_tls_t subclass of channel_t, adapting it
18488 to the existing or_connection_t code. The V2/V3 protocol handshaking
18489 code which formerly resided in command.c has been moved below the
18490 channel_t abstraction layer and may be found in channeltls.c now.
18491 Implements the rest of ticket 6465.
18492 - Introduce new circuitmux_t storing the queue of circuits for
18493 a channel; this encapsulates and abstracts the queue logic and
18494 circuit selection policy, and allows the latter to be overridden
18495 easily by switching out a policy object. The existing EWMA behavior
18496 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18498 o Required libraries:
18499 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18500 strongly recommended.
18503 - Warn users who run hidden services on a Tor client with
18504 UseEntryGuards disabled that their hidden services will be
18505 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18506 attack which motivated Tor to support entry guards in the first
18507 place). Resolves ticket 6889.
18508 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18509 dhill. Resolves ticket 6982.
18510 - Option OutboundBindAddress can be specified multiple times and
18511 accepts IPv6 addresses. Resolves ticket 6876.
18513 o Minor bugfixes (also in 0.2.3.23-rc):
18514 - Don't serve or accept v2 hidden service descriptors over a
18515 relay's DirPort. It's never correct to do so, and disabling it
18516 might make it more annoying to exploit any bugs that turn up in the
18517 descriptor-parsing code. Fixes bug 7149.
18518 - Fix two cases in src/or/transports.c where we were calling
18519 fmt_addr() twice in a parameter list. Bug found by David
18520 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18521 - Fix memory leaks whenever we logged any message about the "path
18522 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18523 - When relays refuse a "create" cell because their queue of pending
18524 create cells is too big (typically because their cpu can't keep up
18525 with the arrival rate), send back reason "resource limit" rather
18526 than reason "internal", so network measurement scripts can get a
18527 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
18530 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18531 - Free some more still-in-use memory at exit, to make hunting for
18532 memory leaks easier. Resolves bug 7029.
18533 - When a Tor client gets a "truncated" relay cell, the first byte of
18534 its payload specifies why the circuit was truncated. We were
18535 ignoring this 'reason' byte when tearing down the circuit, resulting
18536 in the controller not being told why the circuit closed. Now we
18537 pass the reason from the truncated cell to the controller. Bugfix
18538 on 0.1.2.3-alpha; fixes bug 7039.
18539 - Downgrade "Failed to hand off onionskin" messages to "debug"
18540 severity, since they're typically redundant with the "Your computer
18541 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18542 - Make clients running with IPv6 bridges connect over IPv6 again,
18543 even without setting new config options ClientUseIPv6 and
18544 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
18545 - Use square brackets around IPv6 addresses in numerous places
18546 that needed them, including log messages, HTTPS CONNECT proxy
18547 requests, TransportProxy statefile entries, and pluggable transport
18548 extra-info lines. Fixes bug 7011; patch by David Fifield.
18550 o Code refactoring and cleanup:
18551 - Source files taken from other packages now reside in src/ext;
18552 previously they were scattered around the rest of Tor.
18553 - Avoid use of reserved identifiers in our C code. The C standard
18554 doesn't like us declaring anything that starts with an
18555 underscore, so let's knock it off before we get in trouble. Fix
18556 for bug 1031; bugfix on the first Tor commit.
18559 Changes in version 0.2.3.23-rc - 2012-10-20
18560 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
18561 vulnerability introduced by a change in OpenSSL, and fixes a variety
18562 of smaller bugs in preparation for the release.
18564 o New directory authorities:
18565 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18566 authority. Closes ticket 5749.
18568 o Major bugfixes (security/privacy):
18569 - Disable TLS session tickets. OpenSSL's implementation was giving
18570 our TLS session keys the lifetime of our TLS context objects, when
18571 perfect forward secrecy would want us to discard anything that
18572 could decrypt a link connection as soon as the link connection
18573 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18574 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18575 - Discard extraneous renegotiation attempts once the V3 link
18576 protocol has been initiated. Failure to do so left us open to
18577 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18578 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18581 - Fix a possible crash bug when checking for deactivated circuits
18582 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18583 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18585 o Minor bugfixes (on 0.2.3.x):
18586 - Fix two cases in src/or/transports.c where we were calling
18587 fmt_addr() twice in a parameter list. Bug found by David
18588 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18589 - Convert an assert in the pathbias code to a log message. The assert
18590 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18591 bugfix on 0.2.3.17-beta.
18592 - Fix memory leaks whenever we logged any message about the "path
18593 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18595 o Minor bugfixes (on 0.2.2.x and earlier):
18596 - Don't serve or accept v2 hidden service descriptors over a relay's
18597 DirPort. It's never correct to do so, and disabling it might
18598 make it more annoying to exploit any bugs that turn up in the
18599 descriptor-parsing code. Fixes bug 7149.
18600 - When relays refuse a "create" cell because their queue of pending
18601 create cells is too big (typically because their cpu can't keep up
18602 with the arrival rate), send back reason "resource limit" rather
18603 than reason "internal", so network measurement scripts can get a
18604 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18605 - Correct file sizes when reading binary files on Cygwin, to avoid
18606 a bug where Tor would fail to read its state file. Fixes bug 6844;
18607 bugfix on 0.1.2.7-alpha.
18608 - Avoid undefined behavior when parsing the list of supported
18609 rendezvous/introduction protocols in a hidden service descriptor.
18610 Previously, Tor would have confused (as-yet-unused) protocol version
18611 numbers greater than 32 with lower ones on many platforms. Fixes
18612 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18614 o Documentation fixes:
18615 - Clarify that hidden services are TCP only. Fixes bug 6024.
18618 Changes in version 0.2.4.3-alpha - 2012-09-22
18619 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
18620 assertion, resumes letting relays test reachability of their DirPort,
18621 and cleans up a bunch of smaller bugs.
18624 - Fix an assertion failure in tor_timegm() that could be triggered
18625 by a badly formatted directory object. Bug found by fuzzing with
18626 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18629 - Fix a possible crash bug when checking for deactivated circuits
18630 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18631 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18632 - Allow routers to detect that their own DirPorts are running. When
18633 we removed support for versions_supports_begindir, we also
18634 accidentally removed the mechanism we used to self-test our
18635 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
18636 bugfix on 0.2.4.2-alpha.
18638 o Security features:
18639 - Switch to a completely time-invariant approach for picking nodes
18640 weighted by bandwidth. Our old approach would run through the
18641 part of the loop after it had made its choice slightly slower
18642 than it ran through the part of the loop before it had made its
18643 choice. Addresses ticket 6538.
18644 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18645 by tor2web clients allows hidden services to identify tor2web
18646 clients through their repeated selection of the same rendezvous
18647 and introduction point circuit endpoints (their guards). Resolves
18651 - Enable Tor to read configuration, state, and key information from
18652 a FIFO. Previously Tor would only read from files with a positive
18653 stat.st_size. Code from meejah; fixes bug 6044.
18656 - Correct file sizes when reading binary files on Cygwin, to avoid
18657 a bug where Tor would fail to read its state file. Fixes bug 6844;
18658 bugfix on 0.1.2.7-alpha.
18659 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18660 bugfix on 0.2.0.3-alpha.
18661 - When complaining about a client port on a public address, log
18662 which address we're complaining about. Fixes bug 4020; bugfix on
18663 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18664 - Convert an assert in the pathbias code to a log message. The assert
18665 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18666 bugfix on 0.2.3.17-beta.
18667 - Our new buildsystem was overzealous about rebuilding manpages: it
18668 would rebuild them all whenever any one of them changed. Now our
18669 dependency checking should be correct. Fixes bug 6843; bugfix on
18671 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
18672 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
18673 - Correct log printout about which address family is preferred
18674 when connecting to a bridge with both an IPv4 and IPv6 OR port.
18675 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
18677 o Minor bugfixes (code cleanliness):
18678 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18679 with large values. This situation was untriggered, but nevertheless
18680 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18681 - Reject consensus votes with more than 64 known-flags. We aren't even
18682 close to that limit yet, and our code doesn't handle it correctly.
18683 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18684 - Avoid undefined behavior when parsing the list of supported
18685 rendezvous/introduction protocols in a hidden service descriptor.
18686 Previously, Tor would have confused (as-yet-unused) protocol version
18687 numbers greater than 32 with lower ones on many platforms. Fixes
18688 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18689 - Fix handling of rendezvous client authorization types over 8.
18690 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18691 - Fix building with older versions of GCC (2.95, for one) that don't
18692 like preprocessor directives inside macro arguments. Found by
18693 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
18694 - Switch weighted node selection rule from using a list of doubles
18695 to using a list of int64_t. This change should make the process
18696 slightly easier to debug and maintain. Needed to finish ticket 6538.
18698 o Code simplification and refactoring:
18699 - Move the generic "config" code into a new file, and have "config.c"
18700 hold only torrc- and state-related code. Resolves ticket 6823.
18701 - Move the core of our "choose a weighted element at random" logic
18702 into its own function, and give it unit tests. Now the logic is
18703 testable, and a little less fragile too.
18704 - Removed the testing_since field of node_t, which hasn't been used
18705 for anything since 0.2.0.9-alpha.
18707 o Documentation fixes:
18708 - Clarify that hidden services are TCP only. Fixes bug 6024.
18709 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18713 Changes in version 0.2.3.22-rc - 2012-09-11
18714 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18718 - Fix an assertion failure in tor_timegm() that could be triggered
18719 by a badly formatted directory object. Bug found by fuzzing with
18720 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18723 - Avoid segfault when starting up having run with an extremely old
18724 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18728 Changes in version 0.2.2.39 - 2012-09-11
18729 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18733 - Fix an assertion failure in tor_timegm() that could be triggered
18734 by a badly formatted directory object. Bug found by fuzzing with
18735 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18736 - Do not crash when comparing an address with port value 0 to an
18737 address policy. This bug could have been used to cause a remote
18738 assertion failure by or against directory authorities, or to
18739 allow some applications to crash clients. Fixes bug 6690; bugfix
18743 Changes in version 0.2.4.2-alpha - 2012-09-10
18744 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18745 raises the default rate limiting even more, and makes the bootstrapping
18746 log messages less noisy.
18749 - Automatically forward the TCP ports of pluggable transport
18750 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18754 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18755 to 1GB/1GB. The previous defaults were intended to be "basically
18756 infinite", but it turns out they're now limiting our 100mbit+
18757 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18758 last time we raised it).
18761 - Detect when we're running with a version of OpenSSL other than the
18762 one we compiled with. This has occasionally given people hard-to-
18764 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18765 versions and capabilities when everything is going right. Resolves
18766 part of ticket 6736.
18767 - Directory authorities no long accept descriptors for any version of
18768 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18769 These versions are insecure, unsupported, or both. Implements
18773 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18774 to start with a triple-underscore so the controller won't touch it.
18775 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18776 - Avoid segfault when starting up having run with an extremely old
18777 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18779 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18780 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18781 - Don't follow the NULL pointer if microdescriptor generation fails.
18782 (This does not appear to be triggerable, but it's best to be safe.)
18783 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18784 - Fix mis-declared dependencies on src/common/crypto.c and
18785 src/or/tor_main.c that could break out-of-tree builds under some
18786 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18787 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18788 6778; bugfix on 0.2.4.1-alpha.
18789 - Fix a harmless (in this case) build warning for implicitly
18790 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18792 o Removed features:
18793 - Now that all versions before 0.2.2.x are disallowed, we no longer
18794 need to work around their missing features. Thus we can remove a
18795 bunch of compatibility code.
18797 o Code refactoring:
18798 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18799 TCP ports to forward. In the past it only accepted two ports:
18800 the ORPort and the DirPort.
18803 Changes in version 0.2.4.1-alpha - 2012-09-05
18804 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18805 bridgedb; lets relays use IPv6 addresses and directory authorities
18806 advertise them; and switches to a cleaner build interface.
18808 This is the first alpha release in a new series, so expect there to
18809 be bugs. Users who would rather test out a more stable branch should
18810 stay with 0.2.3.x for now.
18812 o Major features (bridges):
18813 - Bridges now report the pluggable transports they support to the
18814 bridge authority, so it can pass the supported transports on to
18815 bridgedb and/or eventually do reachability testing. Implements
18818 o Major features (IPv6):
18819 - Bridge authorities now accept IPv6 bridge addresses and include
18820 them in network status documents. Implements ticket 5534.
18821 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18822 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18823 to happen. Implements ticket 5535.
18824 - All kind of relays, not just bridges, can now advertise an IPv6
18825 OR port. Implements ticket 6362.
18826 - Directory authorities vote on IPv6 OR ports using the new consensus
18827 method 14. Implements ticket 6363.
18829 o Major features (build):
18830 - Switch to a nonrecursive Makefile structure. Now instead of each
18831 Makefile.am invoking other Makefile.am's, there is a master
18832 Makefile.am that includes the others. This change makes our build
18833 process slightly more maintainable, and improves parallelism for
18834 building with make -j. Original patch by Stewart Smith; various
18835 fixes by Jim Meyering.
18836 - Where available, we now use automake's "silent" make rules by
18837 default, so that warnings are easier to spot. You can get the old
18838 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18840 o Minor features (code security and spec conformance):
18841 - Clear keys and key-derived material left on the stack in
18842 rendservice.c and rendclient.c. Check return value of
18843 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18844 These fixes should make us more forward-secure against cold-boot
18845 attacks and the like. Fixes bug 2385.
18846 - Reject EXTEND cells sent to nonexistent streams. According to the
18847 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18848 we were only checking for stream IDs that were currently in use.
18849 Found while hunting for more instances of bug 6271. Bugfix on
18850 0.0.2pre8, which introduced incremental circuit construction.
18852 o Minor features (streamlining);
18853 - No longer include the "opt" prefix when generating routerinfos
18854 or v2 directories: it has been needless since Tor 0.1.2. Closes
18856 - Remove some now-needless code that tried to aggressively flush
18857 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18858 cell queue logic has saved us from the failure mode that this code
18859 was supposed to prevent. Removing this code will limit the number
18860 of baroque control flow paths through Tor's network logic. Reported
18861 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18863 o Minor features (controller):
18864 - Add a "GETINFO signal/names" control port command. Implements
18866 - Provide default values for all options via "GETINFO config/defaults".
18867 Implements ticket 4971.
18869 o Minor features (IPv6):
18870 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18871 authorities should set if they have IPv6 connectivity and want to
18872 do reachability tests for IPv6 relays. Implements feature 5974.
18873 - A relay with an IPv6 OR port now sends that address in NETINFO
18874 cells (in addition to its other address). Implements ticket 6364.
18876 o Minor features (log messages):
18877 - Omit the first heartbeat log message, because it never has anything
18878 useful to say, and it clutters up the bootstrapping messages.
18879 Resolves ticket 6758.
18880 - Don't log about reloading the microdescriptor cache at startup. Our
18881 bootstrap warnings are supposed to tell the user when there's a
18882 problem, and our bootstrap notices say when there isn't. Resolves
18883 ticket 6759; bugfix on 0.2.2.6-alpha.
18884 - Don't log "I learned some more directory information" when we're
18885 reading cached directory information. Reserve it for when new
18886 directory information arrives in response to a fetch. Resolves
18888 - Prevent rounding error in path bias counts when scaling
18889 them down, and use the correct scale factor default. Also demote
18890 some path bias related log messages down a level and make others
18891 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18892 - We no longer warn so much when generating manpages from their
18895 o Code simplifications and refactoring:
18896 - Enhance our internal sscanf replacement so that we can eliminate
18897 the last remaining uses of the system sscanf. (Though those uses
18898 of sscanf were safe, sscanf itself is generally error prone, so
18899 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18901 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18902 - Move last_reachable and testing_since from routerinfo_t to node_t.
18903 Implements ticket 5529.
18904 - Add replaycache_t structure, functions and unit tests, then refactor
18905 rend_service_introduce() to be more clear to read, improve, debug,
18906 and test. Resolves bug 6177.
18907 - Finally remove support for malloc_good_size and malloc_usable_size.
18908 We had hoped that these functions would let us eke a little more
18909 memory out of our malloc implementation. Unfortunately, the only
18910 implementations that provided these functions are also ones that
18911 are already efficient about not overallocation: they never got us
18912 more than 7 or so bytes per allocation. Removing them saves us a
18913 little code complexity and a nontrivial amount of build complexity.
18915 o New requirements:
18916 - Tor maintainers now require Automake version 1.9 or later to build
18917 Tor from the Git repository. (Automake is not required when building
18918 from a source distribution.)
18921 Changes in version 0.2.3.21-rc - 2012-09-05
18922 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
18923 series. It fixes a trio of potential security bugs, fixes a bug where
18924 we were leaving some of the fast relays out of the microdescriptor
18925 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
18926 and cleans up other smaller issues.
18928 o Major bugfixes (security):
18929 - Tear down the circuit if we get an unexpected SENDME cell. Clients
18930 could use this trick to make their circuits receive cells faster
18931 than our flow control would have allowed, or to gum up the network,
18932 or possibly to do targeted memory denial-of-service attacks on
18933 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
18934 from July 2002, before the release of Tor 0.0.0. We had committed
18935 this patch previously, but we had to revert it because of bug 6271.
18936 Now that 6271 is fixed, this patch appears to work.
18937 - Reject any attempt to extend to an internal address. Without
18938 this fix, a router could be used to probe addresses on an internal
18939 network to see whether they were accepting connections. Fixes bug
18940 6710; bugfix on 0.0.8pre1.
18941 - Do not crash when comparing an address with port value 0 to an
18942 address policy. This bug could have been used to cause a remote
18943 assertion failure by or against directory authorities, or to
18944 allow some applications to crash clients. Fixes bug 6690; bugfix
18948 - Remove the upper bound on microdescriptor length. We were hitting
18949 the limit for routers with complex exit policies or family
18950 declarations, causing clients to not use them. Fixes the first
18951 piece of bug 6404; fix on 0.2.2.6-alpha.
18952 - Detect "ORPort 0" as meaning, uniformly, that we're not running
18953 as a relay. Previously, some of our code would treat the presence
18954 of any ORPort line as meaning that we should act like a relay,
18955 even though our new listener code would correctly not open any
18956 ORPorts for ORPort 0. Similar bugs in other Port options are also
18957 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
18960 - Avoid a pair of double-free and use-after-mark bugs that can
18961 occur with certain timings in canceled and re-received DNS
18962 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
18963 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
18964 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
18965 - Allow one-hop directory fetching circuits the full "circuit build
18966 timeout" period, rather than just half of it, before failing them
18967 and marking the relay down. This fix should help reduce cases where
18968 clients declare relays (or worse, bridges) unreachable because
18969 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
18970 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
18972 - Authorities no longer include any router in their microdescriptor
18973 consensuses for which they couldn't generate or agree on a
18974 microdescriptor. Fixes the second piece of bug 6404; fix on
18976 - Detect and reject attempts to specify both "FooPort" and
18977 "FooPort 0" in the same configuration domain. (It's still okay
18978 to have a FooPort in your configuration file, and use "FooPort 0"
18979 on the command line to disable it.) Fixes the second half of bug
18980 6507; bugfix on 0.2.3.3-alpha.
18981 - Make wildcarded addresses (that is, ones beginning with "*.") work
18982 when provided via the controller's MapAddress command. Previously,
18983 they were accepted, but we never actually noticed that they were
18984 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
18985 - Avoid crashing on a malformed state file where EntryGuardPathBias
18986 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
18987 - Add a (probably redundant) memory clear between iterations of
18988 the router status voting loop, to prevent future coding errors
18989 where data might leak between iterations of the loop. Resolves
18992 o Minor bugfixes (log messages):
18993 - Downgrade "set buildtimeout to low value" messages to "info"
18994 severity; they were never an actual problem, there was never
18995 anything reasonable to do about them, and they tended to spam logs
18996 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
18997 - Downgrade path-bias warning messages to "info". We'll try to get
18998 them working better in 0.2.4. Add internal circuit construction
18999 state to protect against the noisy warn message "Unexpectedly high
19000 circuit_successes". Also add some additional rate-limited notice
19001 messages to help determine the root cause of the warn. Fixes bug
19002 6475. Bugfix against 0.2.3.17-beta.
19003 - Move log message when unable to find a microdesc in a routerstatus
19004 entry to parse time. Previously we'd spam this warning every time
19005 we tried to figure out which microdescriptors to download. Fixes
19006 the third piece of bug 6404; fix on 0.2.3.18-rc.
19009 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
19010 change when the authority is deciding whether to accept a newly
19011 uploaded descriptor. Implements ticket 6423.
19012 - Add missing documentation for consensus and microdesc files.
19013 Resolves ticket 6732.
19016 Changes in version 0.2.2.38 - 2012-08-12
19017 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
19018 attack that could in theory leak path information.
19021 - Avoid an uninitialized memory read when reading a vote or consensus
19022 document that has an unrecognized flavor name. This read could
19023 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19024 - Try to leak less information about what relays a client is
19025 choosing to a side-channel attacker. Previously, a Tor client would
19026 stop iterating through the list of available relays as soon as it
19027 had chosen one, thus finishing a little earlier when it picked
19028 a router earlier in the list. If an attacker can recover this
19029 timing information (nontrivial but not proven to be impossible),
19030 they could learn some coarse-grained information about which relays
19031 a client was picking (middle nodes in particular are likelier to
19032 be affected than exits). The timing attack might be mitigated by
19033 other factors (see bug 6537 for some discussion), but it's best
19034 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
19037 Changes in version 0.2.3.20-rc - 2012-08-05
19038 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
19039 series. It fixes a pair of code security bugs and a potential anonymity
19040 issue, updates our RPM spec files, and cleans up other smaller issues.
19043 - Avoid read-from-freed-memory and double-free bugs that could occur
19044 when a DNS request fails while launching it. Fixes bug 6480;
19045 bugfix on 0.2.0.1-alpha.
19046 - Avoid an uninitialized memory read when reading a vote or consensus
19047 document that has an unrecognized flavor name. This read could
19048 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19049 - Try to leak less information about what relays a client is
19050 choosing to a side-channel attacker. Previously, a Tor client would
19051 stop iterating through the list of available relays as soon as it
19052 had chosen one, thus finishing a little earlier when it picked
19053 a router earlier in the list. If an attacker can recover this
19054 timing information (nontrivial but not proven to be impossible),
19055 they could learn some coarse-grained information about which relays
19056 a client was picking (middle nodes in particular are likelier to
19057 be affected than exits). The timing attack might be mitigated by
19058 other factors (see bug 6537 for some discussion), but it's best
19059 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
19062 - Try to make the warning when giving an obsolete SOCKSListenAddress
19063 a little more useful.
19064 - Terminate active server managed proxies if Tor stops being a
19065 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
19066 - Provide a better error message about possible OSX Asciidoc failure
19067 reasons. Fixes bug 6436.
19068 - Warn when Tor is configured to use accounting in a way that can
19069 link a hidden service to some other hidden service or public
19070 address. Resolves ticket 6490.
19073 - Check return value of fputs() when writing authority certificate
19074 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
19075 - Ignore ServerTransportPlugin lines when Tor is not configured as
19076 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
19077 - When disabling guards for having too high a proportion of failed
19078 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
19082 - Update our default RPM spec files to work with mock and rpmbuild
19083 on RHEL/Fedora. They have an updated set of dependencies and
19084 conflicts, a fix for an ancient typo when creating the "_tor"
19085 user, and better instructions. Thanks to Ondrej Mikle for the
19086 patch series. Fixes bug 6043.
19089 - Make it possible to set the TestingTorNetwork configuration
19090 option using AlternateDirAuthority and AlternateBridgeAuthority
19091 as an alternative to setting DirServer. Addresses ticket 6377.
19094 - Clarify the documentation for the Alternate*Authority options.
19096 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
19098 o Code simplification and refactoring:
19099 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
19100 10 lines. Also, don't nest them. Doing so in the past has
19101 led to hard-to-debug code. The new style is to use the
19102 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
19105 Changes in version 0.2.3.19-rc - 2012-07-06
19106 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
19107 series. It fixes the compile on Windows, reverts to a GeoIP database
19108 that isn't as broken, and fixes a flow control bug that has been around
19109 since the beginning of Tor.
19112 - Fix a bug handling SENDME cells on nonexistent streams that could
19113 result in bizarre window values. Report and patch contributed
19114 pseudonymously. Fixes part of bug 6271. This bug was introduced
19115 before the first Tor release, in svn commit r152.
19116 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
19117 June 2012 database, Maxmind marked many Tor relays as country "A1",
19118 which will cause risky behavior for clients that set EntryNodes
19119 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
19120 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
19121 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
19124 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
19125 bugfix on 0.2.1.10-alpha.
19128 Changes in version 0.2.3.18-rc - 2012-06-28
19129 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
19130 series. It fixes a few smaller bugs, but generally appears stable.
19131 Please test it and let us know whether it is!
19134 - Allow wildcarded mapaddress targets to be specified on the
19135 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
19136 - Make our linker option detection code more robust against linkers
19137 such as on FreeBSD 8, where a bad combination of options completes
19138 successfully but makes an unrunnable binary. Fixes bug 6173;
19139 bugfix on 0.2.3.17-beta.
19141 o Minor bugfixes (on 0.2.2.x and earlier):
19142 - Avoid a false positive in the util/threads unit test by increasing
19143 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
19144 - Replace "Sending publish request" log messages with "Launching
19145 upload", so that they no longer confusingly imply that we're
19146 sending something to a directory we might not even be connected
19147 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
19148 - Make sure to set *socket_error in all error cases in
19149 connection_connect(), so it can't produce a warning about
19150 errno being zero from errno_to_orconn_end_reason(). Bugfix on
19151 0.2.1.1-alpha; resolves ticket 6028.
19152 - Downgrade "Got a certificate, but we already have it" log messages
19153 from warning to info, except when we're a dirauth. Fixes bug 5238;
19154 bugfix on 0.2.1.7-alpha.
19155 - When checking for requested signatures on the latest consensus
19156 before serving it to a client, make sure to check the right
19157 consensus flavor. Bugfix on 0.2.2.6-alpha.
19158 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
19159 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
19161 o Minor bugfixes (on 0.2.3.x):
19162 - Make format_helper_exit_status() avoid unnecessary space padding
19163 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
19165 - Downgrade a message about cleaning the microdescriptor cache to
19166 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
19167 - Log a BUG message at severity INFO if we have a networkstatus with
19168 a missing entry for some microdescriptor. Continues on a patch
19170 - Improve the log message when a managed proxy fails to launch. Fixes
19171 bug 5099; bugfix on 0.2.3.6-alpha.
19172 - Don't do DNS lookups when parsing corrupted managed proxy protocol
19173 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
19174 - When formatting wildcarded address mappings for the controller,
19175 be sure to include "*." as appropriate. Partially fixes bug 6244;
19176 bugfix on 0.2.3.9-alpha.
19177 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
19178 Bugfix on 0.2.3.13-alpha.
19179 - Stop logging messages about running with circuit timeout learning
19180 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
19181 - Disable a spurious warning about reading on a marked and flushing
19182 connection. We shouldn't be doing that, but apparently we
19183 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
19184 - Fix a bug that stopped AllowDotExit from working on addresses
19185 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
19188 o Code simplification, refactoring, unit tests:
19189 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
19190 Libevent's notion of cached time when possible.
19191 - Remove duplicate code for invoking getrlimit() from control.c.
19192 - Add a unit test for the environment_variable_names_equal function.
19195 - Document the --defaults-torrc option, and the new (in 0.2.3)
19196 semantics for overriding, extending, and clearing lists of
19197 options. Closes bug 4748.
19200 Changes in version 0.2.3.17-beta - 2012-06-15
19201 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
19202 gets our TLS handshake back on track for being able to blend in with
19203 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
19204 with Vidalia, and otherwise continues to get us closer to a release
19208 - Enable gcc and ld hardening by default. Resolves ticket 5210.
19209 - Update TLS cipher list to match Firefox 8 and later. Resolves
19211 - Implement the client side of proposal 198: remove support for
19212 clients falsely claiming to support standard ciphersuites that
19213 they can actually provide. As of modern OpenSSL versions, it's not
19214 necessary to fake any standard ciphersuite, and doing so prevents
19215 us from using better ciphersuites in the future, since servers
19216 can't know whether an advertised ciphersuite is really supported or
19217 not. Some hosts -- notably, ones with very old versions of OpenSSL
19218 or where OpenSSL has been built with ECC disabled -- will stand
19219 out because of this change; TBB users should not be affected.
19222 - Change the default value for DynamicDHGroups (introduced in
19223 0.2.3.9-alpha) to 0. This feature can make Tor relays less
19224 identifiable by their use of the mod_ssl DH group, but at
19225 the cost of some usability (#4721) and bridge tracing (#6087)
19226 regressions. Resolves ticket 5598.
19227 - Send a CRLF at the end of each STATUS_* control protocol event. This
19228 bug tickled a bug in Vidalia which would make it freeze. Fixes
19229 bug 6094; bugfix on 0.2.3.16-alpha.
19232 - Disable writing on marked-for-close connections when they are
19233 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
19234 bug 5263; bugfix on 0.0.2pre13, where we first added a special
19235 case for flushing marked connections.
19236 - Detect SSL handshake even when the initial attempt to write the
19237 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
19238 - Change the AllowDotExit rules so they should actually work.
19239 We now enforce AllowDotExit only immediately after receiving an
19240 address via SOCKS or DNSPort: other sources are free to provide
19241 .exit addresses after the resolution occurs. Fixes bug 3940;
19242 bugfix on 0.2.2.1-alpha.
19243 - Fix a (harmless) integer overflow in cell statistics reported by
19244 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19245 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
19246 right places and never depends on the consensus parameters or
19247 computes adaptive timeouts when it is disabled. Fixes bug 5049;
19248 bugfix on 0.2.2.14-alpha.
19249 - When building Tor on Windows with -DUNICODE (not default), ensure
19250 that error messages, filenames, and DNS server names are always
19251 NUL-terminated when we convert them to a single-byte encoding.
19252 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19253 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
19254 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
19255 - Fix an edge case where TestingTorNetwork is set but the authorities
19256 and relays all have an uptime of zero, where the private Tor network
19257 could briefly lack support for hidden services. Fixes bug 3886;
19258 bugfix on 0.2.2.18-alpha.
19259 - Correct the manpage's descriptions for the default values of
19260 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
19262 - Fix the documentation for the --hush and --quiet command line
19263 options, which changed their behavior back in 0.2.3.3-alpha.
19264 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
19268 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
19269 more information to it, so that we can track it down in case it
19270 returns again. Mitigates bug 5235.
19271 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
19272 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
19273 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
19274 - Warn the user when HTTPProxy, but no other proxy type, is
19275 configured. This can cause surprising behavior: it doesn't send
19276 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19277 directory traffic only. Resolves ticket 4663.
19278 - Issue a notice if a guard completes less than 40% of your circuits.
19279 Threshold is configurable by torrc option PathBiasNoticeRate and
19280 consensus parameter pb_noticepct. There is additional, off-by-
19281 default code to disable guards which fail too many circuits.
19282 Addresses ticket 5458.
19283 - Update to the June 6 2012 Maxmind GeoLite Country database.
19285 o Code simplifications and refactoring:
19286 - Remove validate_pluggable_transports_config(): its warning
19287 message is now handled by connection_or_connect().
19290 Changes in version 0.2.2.37 - 2012-06-06
19291 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19292 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19296 - Work around a bug in OpenSSL that broke renegotiation with TLS
19297 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19298 the v2 Tor connection protocol when both sides were using OpenSSL
19299 1.0.1 would fail. Resolves ticket 6033.
19300 - When waiting for a client to renegotiate, don't allow it to add
19301 any bytes to the input buffer. This fixes a potential DoS issue.
19302 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19303 - Fix an edge case where if we fetch or publish a hidden service
19304 descriptor, we might build a 4-hop circuit and then use that circuit
19305 for exiting afterwards -- even if the new last hop doesn't obey our
19306 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19309 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19310 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19313 - Tell GCC and Clang to check for any errors in format strings passed
19314 to the tor_v*(print|scan)f functions.
19317 Changes in version 0.2.3.16-alpha - 2012-06-05
19318 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
19319 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19320 currently). It also fixes a variety of smaller bugs and other cleanups
19321 that get us closer to a release candidate.
19323 o Major bugfixes (general):
19324 - Work around a bug in OpenSSL that broke renegotiation with TLS
19325 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19326 the v2 Tor connection protocol when both sides were using OpenSSL
19327 1.0.1 would fail. Resolves ticket 6033.
19328 - When waiting for a client to renegotiate, don't allow it to add
19329 any bytes to the input buffer. This fixes a potential DoS issue.
19330 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19331 - Pass correct OR address to managed proxies (like obfsproxy),
19332 even when ORListenAddress is used. Fixes bug 4865; bugfix on
19334 - The advertised platform of a router now includes only its operating
19335 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
19336 service pack level (for Windows) or its CPU architecture (for Unix).
19337 We also no longer include the "git-XYZ" tag in the version. Resolves
19340 o Major bugfixes (clients):
19341 - If we are unable to find any exit that supports our predicted ports,
19342 stop calling them predicted, so that we don't loop and build
19343 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19344 which introduced predicted ports.
19345 - Fix an edge case where if we fetch or publish a hidden service
19346 descriptor, we might build a 4-hop circuit and then use that circuit
19347 for exiting afterwards -- even if the new last hop doesn't obey our
19348 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19349 - Check at each new consensus whether our entry guards were picked
19350 long enough ago that we should rotate them. Previously, we only
19351 did this check at startup, which could lead to us holding a guard
19352 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19353 - When fetching a bridge descriptor from a bridge authority,
19354 always do so anonymously, whether we have been able to open
19355 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19356 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19357 but we'll need to wait for bug 6010 before it's actually usable.
19359 o Major bugfixes (directory authorities):
19360 - When computing weight parameters, behave more robustly in the
19361 presence of a bad bwweightscale value. Previously, the authorities
19362 would crash if they agreed on a sufficiently broken weight_scale
19363 value: now, they use a reasonable default and carry on. Partial
19364 fix for 5786; bugfix on 0.2.2.17-alpha.
19365 - Check more thoroughly to prevent a rogue authority from
19366 double-voting on any consensus directory parameter. Previously,
19367 authorities would crash in this case if the total number of
19368 votes for any parameter exceeded the number of active voters,
19369 but would let it pass otherwise. Partial fix for bug 5786; bugfix
19373 - Rate-limit log messages when asked to connect anonymously to
19374 a private address. When these hit, they tended to hit fast and
19375 often. Also, don't bother trying to connect to addresses that we
19376 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19377 reply makes us think we have been lied to, even when the address the
19378 client tried to connect to was "localhost." Resolves ticket 2822.
19379 - Allow packagers to insert an extra string in server descriptor
19380 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
19381 Resolves the rest of ticket 2988.
19382 - Raise the threshold of server descriptors needed (75%) and exit
19383 server descriptors needed (50%) before we will declare ourselves
19384 bootstrapped. This will make clients start building circuits a
19385 little later, but makes the initially constructed circuits less
19386 skewed and less in conflict with further directory fetches. Fixes
19388 - Close any connection that sends unrecognized junk before the
19389 handshake. Solves an issue noted in bug 4369.
19390 - Improve log messages about managed transports. Resolves ticket 5070.
19391 - Tag a bridge's descriptor as "never to be sent unencrypted".
19392 This shouldn't matter, since bridges don't open non-anonymous
19393 connections to the bridge authority and don't allow unencrypted
19394 directory connections from clients, but we might as well make
19395 sure. Closes bug 5139.
19396 - Expose our view of whether we have gone dormant to the controller,
19397 via a new "GETINFO dormant" value. Torbutton and other controllers
19398 can use this to avoid doing periodic requests through Tor while
19399 it's dormant (bug 4718). Fixes bug 5954.
19400 - Tell GCC and Clang to check for any errors in format strings passed
19401 to the tor_v*(print|scan)f functions.
19402 - Update to the May 1 2012 Maxmind GeoLite Country database.
19404 o Minor bugfixes (already included in 0.2.2.36):
19405 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19406 Fixes bug 5346; bugfix on 0.0.8pre3.
19407 - Correct parsing of certain date types in parse_http_time().
19408 Without this patch, If-Modified-Since would behave
19409 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19410 Esteban Manchado Velázques.
19411 - Make our number-parsing functions always treat too-large values
19412 as an error, even when those values exceed the width of the
19413 underlying type. Previously, if the caller provided these
19414 functions with minima or maxima set to the extreme values of the
19415 underlying integer type, these functions would return those
19416 values on overflow rather than treating overflow as an error.
19417 Fixes part of bug 5786; bugfix on 0.0.9.
19418 - If we hit the error case where routerlist_insert() replaces an
19419 existing (old) server descriptor, make sure to remove that
19420 server descriptor from the old_routers list. Fix related to bug
19421 1776. Bugfix on 0.2.2.18-alpha.
19422 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19423 circuits. Fixes issue 5259.
19425 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
19426 - Prevent a null-pointer dereference when receiving a data cell
19427 for a nonexistent stream when the circuit in question has an
19428 empty deliver window. We don't believe this is triggerable,
19429 since we don't currently allow deliver windows to become empty,
19430 but the logic is tricky enough that it's better to make the code
19431 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19432 - Fix a memory leak when trying to launch a DNS request when the
19433 network is disabled or the nameservers are unconfigurable. Fixes
19434 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
19435 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
19436 - Don't hold a Windows file handle open for every file mapping;
19437 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19439 - Avoid O(n^2) performance characteristics when parsing a large
19440 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19441 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19442 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19444 - Make our replacement implementation of strtok_r() compatible with
19445 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19446 bugfix on 0.2.2.1-alpha.
19447 - Fix a NULL-pointer dereference on a badly formed
19448 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
19449 bugfix on 0.2.2.9-alpha.
19450 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19451 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19452 - Defensively refactor rend_mid_rendezvous() so that protocol
19453 violations and length checks happen in the beginning. Fixes
19455 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19456 that IPv6 stuff will compile on MSVC, and compilation issues
19457 will be easier to track down. Fixes bug 5861.
19459 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
19460 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19461 resource exhaustion, so that clients can adjust their load to
19462 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19463 started using END_STREAM_REASON_RESOURCELIMIT.
19464 - Don't check for whether the address we're using for outbound
19465 connections has changed until after the outbound connection has
19466 completed. On Windows, getsockname() doesn't succeed until the
19467 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19468 - If the configuration tries to set MyFamily on a bridge, refuse to
19469 do so, and warn about the security implications. Fixes bug 4657;
19470 bugfix on 0.2.0.3-alpha.
19471 - If the client fails to set a reasonable set of ciphersuites
19472 during its v2 handshake renegotiation, allow the renegotiation to
19473 continue nevertheless (i.e. send all the required certificates).
19474 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19475 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19476 option is set to 0 (which Vidalia version 0.2.16 now does when
19477 a SAVECONF attempt fails), perform other actions that SIGHUP
19478 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19480 - If we fail to write a microdescriptor to the disk cache, do not
19481 continue replacing the old microdescriptor file. Fixes bug 2954;
19482 bugfix on 0.2.2.6-alpha.
19483 - Exit nodes don't need to fetch certificates for authorities that
19484 they don't recognize; only directory authorities, bridges,
19485 and caches need to do that. Fixes part of bug 2297; bugfix on
19487 - Correctly handle checking the permissions on the parent
19488 directory of a control socket in the root directory. Bug found
19489 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19491 - When told to add a bridge with the same digest as a preexisting
19492 bridge but a different addr:port, change the addr:port as
19493 requested. Previously we would not notice the change. Fixes half
19494 of bug 5603; fix on 0.2.2.26-beta.
19495 - End AUTHCHALLENGE error messages (in the control protocol) with
19496 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
19498 o Minor bugfixes (on 0.2.3.x):
19499 - Turn an assertion (that the number of handshakes received as a
19500 server is not < 1) into a warning. Fixes bug 4873; bugfix on
19502 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
19503 we had reversed them when the answer was cached.) Fixes bug
19504 5723; bugfix on 0.2.3.1-alpha.
19505 - Work correctly on Linux systems with accept4 support advertised in
19506 their headers, but without accept4 support in the kernel. Fix
19507 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
19508 - When told to add a bridge with the same addr:port as a preexisting
19509 bridge but a different transport, change the transport as
19510 requested. Previously we would not notice the change. Fixes half
19511 of bug 5603; fix on 0.2.3.2-alpha.
19512 - Avoid a "double-reply" warning when replying to a SOCKS request
19513 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
19514 bugfix on 0.2.3.4-alpha.
19515 - Fix a bug where a bridge authority crashes if it has seen no
19516 directory requests when it's time to write statistics to disk.
19517 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
19519 - Don't try to open non-control listeners when DisableNetwork is set.
19520 Previously, we'd open all listeners, then immediately close them.
19521 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
19522 - Don't abort the managed proxy protocol if the managed proxy
19523 sends us an unrecognized line; ignore it instead. Fixes bug
19524 5910; bugfix on 0.2.3.9-alpha.
19525 - Fix a compile warning in crypto.c when compiling with clang 3.1.
19526 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
19527 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
19528 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
19529 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
19530 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
19531 - Resolve numerous small warnings and build issues with MSVC. Resolves
19534 o Documentation fixes:
19535 - Improve the manual's documentation for the NT Service command-line
19536 options. Addresses ticket 3964.
19537 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19538 - Document the changes to the ORPort and DirPort options, and the
19539 fact that {OR/Dir}ListenAddress is now unnecessary (and
19540 therefore deprecated). Resolves ticket 5597.
19543 - Remove the torrc.bridge file: we don't use it for anything, and
19544 it had become badly desynchronized from torrc.sample. Resolves
19548 Changes in version 0.2.2.36 - 2012-05-24
19549 Tor 0.2.2.36 updates the addresses for two of the eight directory
19550 authorities, fixes some potential anonymity and security issues,
19551 and fixes several crash bugs.
19553 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19554 known flaws, and nobody should be using them. You should upgrade. If
19555 you're using a Linux or BSD and its packages are obsolete, stop using
19556 those packages and upgrade anyway.
19558 o Directory authority changes:
19559 - Change IP address for maatuska (v3 directory authority).
19560 - Change IP address for ides (v3 directory authority), and rename
19564 - When building or running with any version of OpenSSL earlier
19565 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19566 versions have a bug (CVE-2011-4576) in which their block cipher
19567 padding includes uninitialized data, potentially leaking sensitive
19568 information to any peer with whom they make a SSLv3 connection. Tor
19569 does not use SSL v3 by default, but a hostile client or server
19570 could force an SSLv3 connection in order to gain information that
19571 they shouldn't have been able to get. The best solution here is to
19572 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19573 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19574 to make sure that the bug can't happen.
19575 - Never use a bridge or a controller-supplied node as an exit, even
19576 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19577 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19578 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19579 - Only build circuits if we have a sufficient threshold of the total
19580 descriptors that are marked in the consensus with the "Exit"
19581 flag. This mitigates an attack proposed by wanoskarnet, in which
19582 all of a client's bridges collude to restrict the exit nodes that
19583 the client knows about. Fixes bug 5343.
19584 - Provide controllers with a safer way to implement the cookie
19585 authentication mechanism. With the old method, if another locally
19586 running program could convince a controller that it was the Tor
19587 process, then that program could trick the controller into telling
19588 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19589 authentication method uses a challenge-response approach to prevent
19590 this attack. Fixes bug 5185; implements proposal 193.
19593 - Avoid logging uninitialized data when unable to decode a hidden
19594 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19595 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19596 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19598 - Fix builds when the path to sed, openssl, or sha1sum contains
19599 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19601 - Correct our replacements for the timeradd() and timersub() functions
19602 on platforms that lack them (for example, Windows). The timersub()
19603 function is used when expiring circuits, while timeradd() is
19604 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19605 bugfix on 0.2.2.24-alpha.
19606 - Fix the SOCKET_OK test that we use to tell when socket
19607 creation fails so that it works on Win64. Fixes part of bug 4533;
19608 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19611 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19612 Fixes bug 5346; bugfix on 0.0.8pre3.
19613 - Make our number-parsing functions always treat too-large values
19614 as an error, even when those values exceed the width of the
19615 underlying type. Previously, if the caller provided these
19616 functions with minima or maxima set to the extreme values of the
19617 underlying integer type, these functions would return those
19618 values on overflow rather than treating overflow as an error.
19619 Fixes part of bug 5786; bugfix on 0.0.9.
19620 - Older Linux kernels erroneously respond to strange nmap behavior
19621 by having accept() return successfully with a zero-length
19622 socket. When this happens, just close the connection. Previously,
19623 we would try harder to learn the remote address: but there was
19624 no such remote address to learn, and our method for trying to
19625 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19626 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19627 - Correct parsing of certain date types in parse_http_time().
19628 Without this patch, If-Modified-Since would behave
19629 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19630 Esteban Manchado Velázques.
19631 - Change the BridgePassword feature (part of the "bridge community"
19632 design, which is not yet implemented) to use a time-independent
19633 comparison. The old behavior might have allowed an adversary
19634 to use timing to guess the BridgePassword value. Fixes bug 5543;
19635 bugfix on 0.2.0.14-alpha.
19636 - Detect and reject certain misformed escape sequences in
19637 configuration values. Previously, these values would cause us
19638 to crash if received in a torrc file or over an authenticated
19639 control port. Bug found by Esteban Manchado Velázquez, and
19640 independently by Robert Connolly from Matta Consulting who further
19641 noted that it allows a post-authentication heap overflow. Patch
19642 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19643 bugfix on 0.2.0.16-alpha.
19644 - Fix a compile warning when using the --enable-openbsd-malloc
19645 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19646 - During configure, detect when we're building with clang version
19647 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19648 CFLAGS. clang doesn't support them yet.
19649 - When sending an HTTP/1.1 proxy request, include a Host header.
19650 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19651 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19652 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19653 - If we hit the error case where routerlist_insert() replaces an
19654 existing (old) server descriptor, make sure to remove that
19655 server descriptor from the old_routers list. Fix related to bug
19656 1776. Bugfix on 0.2.2.18-alpha.
19658 o Minor bugfixes (documentation and log messages):
19659 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19660 Fixes bug 4856; bugfix on Tor 0.0.6.
19661 - Update "ClientOnly" man page entry to explain that there isn't
19662 really any point to messing with it. Resolves ticket 5005.
19663 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19664 directory authority option (introduced in Tor 0.2.2.34).
19665 - Downgrade the "We're missing a certificate" message from notice
19666 to info: people kept mistaking it for a real problem, whereas it
19667 is seldom the problem even when we are failing to bootstrap. Fixes
19668 bug 5067; bugfix on 0.2.0.10-alpha.
19669 - Correctly spell "connect" in a log message on failure to create a
19670 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19671 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19672 circuits. Fixes issue 5259.
19675 - Directory authorities now reject versions of Tor older than
19676 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19677 inclusive. These versions accounted for only a small fraction of
19678 the Tor network, and have numerous known security issues. Resolves
19680 - Update to the May 1 2012 Maxmind GeoLite Country database.
19683 - When sending or relaying a RELAY_EARLY cell, we used to convert
19684 it to a RELAY cell if the connection was using the v1 link
19685 protocol. This was a workaround for older versions of Tor, which
19686 didn't handle RELAY_EARLY cells properly. Now that all supported
19687 versions can handle RELAY_EARLY cells, and now that we're enforcing
19688 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19689 remove this workaround. Addresses bug 4786.
19692 Changes in version 0.2.3.15-alpha - 2012-04-30
19693 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
19694 the development branch build on Windows again.
19696 o Minor bugfixes (on 0.2.2.x and earlier):
19697 - Make sure that there are no unhandled pending TLS errors before
19698 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19699 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19700 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19701 - Fix an assert that directory authorities could trigger on sighup
19702 during some configuration state transitions. We now don't treat
19703 it as a fatal error when the new descriptor we just generated in
19704 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19705 - After we pick a directory mirror, we would refuse to use it if
19706 it's in our ExcludeExitNodes list, resulting in mysterious failures
19707 to bootstrap for people who just wanted to avoid exiting from
19708 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19709 - When building with --enable-static-tor on OpenBSD, do not
19710 erroneously attempt to link -lrt. Fixes bug 5103.
19712 o Minor bugfixes (on 0.2.3.x):
19713 - When Tor is built with kernel headers from a recent (last few
19714 years) Linux kernel, do not fail to run on older (pre-2.6.28
19715 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19716 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19717 and 0.2.3.12-alpha.
19718 - Fix compilation with miniupnpc version 1.6; patch from
19719 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19720 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19721 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19722 - Fix compilation on platforms without unistd.h, or where environ
19723 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19726 - Directory authorities are now a little more lenient at accepting
19727 older router descriptors, or newer router descriptors that don't
19728 make big changes. This should help ameliorate past and future
19729 issues where routers think they have uploaded valid descriptors,
19730 but the authorities don't think so. Fix for ticket 2479.
19731 - Make the code that clients use to detect an address change be
19732 IPv6-aware, so that it won't fill clients' logs with error
19733 messages when trying to get the IPv4 address of an IPv6
19734 connection. Implements ticket 5537.
19736 o Removed features:
19737 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19738 authorities needed to use it for a while to keep the network working
19739 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19740 that was six months ago. As of now, it should no longer be needed
19744 Changes in version 0.2.3.14-alpha - 2012-04-23
19745 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19746 candidate. It also dramatically speeds up AES: fast relays should
19747 consider switching to the newer OpenSSL library.
19749 o Directory authority changes:
19750 - Change IP address for ides (v3 directory authority), and rename
19754 - Avoid logging uninitialized data when unable to decode a hidden
19755 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19756 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19757 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19759 - If authorities are unable to get a v2 consensus document from other
19760 directory authorities, they no longer fall back to fetching
19761 them from regular directory caches. Fixes bug 5635; bugfix on
19762 0.2.2.26-beta, where routers stopped downloading v2 consensus
19763 documents entirely.
19764 - When we start a Tor client with a normal consensus already cached,
19765 be willing to download a microdescriptor consensus. Fixes bug 4011;
19766 fix on 0.2.3.1-alpha.
19768 o Major features (performance):
19769 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19770 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19771 vectorized AES implementations as appropriate. These can be much,
19772 much faster than other AES implementations.
19774 o Minor bugfixes (0.2.2.x and earlier):
19775 - Don't launch more than 10 service-side introduction-point circuits
19776 for a hidden service in five minutes. Previously, we would consider
19777 launching more introduction-point circuits if at least one second
19778 had passed without any introduction-point circuits failing. Fixes
19779 bug 4607; bugfix on 0.0.7pre1.
19780 - Change the BridgePassword feature (part of the "bridge community"
19781 design, which is not yet implemented) to use a time-independent
19782 comparison. The old behavior might have allowed an adversary
19783 to use timing to guess the BridgePassword value. Fixes bug 5543;
19784 bugfix on 0.2.0.14-alpha.
19785 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19786 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19787 - When sending an HTTP/1.1 proxy request, include a Host header.
19788 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19789 - Don't log that we have "decided to publish new relay descriptor"
19790 unless we are actually publishing a descriptor. Fixes bug 3942;
19791 bugfix on 0.2.2.28-beta.
19793 o Minor bugfixes (0.2.3.x):
19794 - Fix a bug where a bridge authority crashes (on a failed assert)
19795 if it has seen no directory requests when it's time to write
19796 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19797 - Fix bug stomping on ORPort option NoListen and ignoring option
19798 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19799 - In the testsuite, provide a large enough buffer in the tor_sscanf
19800 unit test. Otherwise we'd overrun that buffer and crash during
19801 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19803 - Make sure we create the keys directory if it doesn't exist and we're
19804 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19805 5572; bugfix on 0.2.3.13-alpha.
19806 - Fix a small memory leak when trying to decode incorrect base16
19807 authenticator during SAFECOOKIE authentication. Found by
19808 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19811 - Add more information to a log statement that might help track down
19812 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19813 non-IP address" messages (or any Bug messages, for that matter!),
19814 please let us know about it.
19815 - Relays now understand an IPv6 address when they get one from a
19816 directory server. Resolves ticket 4875.
19817 - Resolve IPv6 addresses in bridge and entry statistics to country
19818 code "??" which means we at least count them. Resolves ticket 5053;
19819 improves on 0.2.3.9-alpha.
19820 - Update to the April 3 2012 Maxmind GeoLite Country database.
19821 - Begin a doc/state-contents.txt file to explain the contents of
19822 the Tor state file. Fixes bug 2987.
19824 o Default torrc changes:
19825 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19826 port on 9050 by default anyway, so this should not change anything
19828 - Stop mentioning the deprecated *ListenAddress options in
19829 torrc.sample. Fixes bug 5438.
19830 - Document unit of bandwidth related options in sample torrc.
19833 o Removed features:
19834 - The "torify" script no longer supports the "tsocks" socksifier
19835 tool, since tsocks doesn't support DNS and UDP right for Tor.
19836 Everyone should be using torsocks instead. Fixes bugs 3530 and
19837 5180. Based on a patch by "ugh".
19839 o Code refactoring:
19840 - Change the symmetric cipher interface so that creating and
19841 initializing a stream cipher are no longer separate functions.
19842 - Remove all internal support for unpadded RSA. We never used it, and
19843 it would be a bad idea to start.
19846 Changes in version 0.2.3.13-alpha - 2012-03-26
19847 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19848 in managed pluggable transports, as well as providing other cleanups
19849 that get us closer to a release candidate.
19851 o Directory authority changes:
19852 - Change IP address for maatuska (v3 directory authority).
19855 - Provide controllers with a safer way to implement the cookie
19856 authentication mechanism. With the old method, if another locally
19857 running program could convince a controller that it was the Tor
19858 process, then that program could trick the controller into telling
19859 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19860 authentication method uses a challenge-response approach to prevent
19861 this attack. Fixes bug 5185, implements proposal 193.
19862 - Never use a bridge or a controller-supplied node as an exit, even
19863 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19864 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19865 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19866 - Only build circuits if we have a sufficient threshold of the total
19867 descriptors that are marked in the consensus with the "Exit"
19868 flag. This mitigates an attack proposed by wanoskarnet, in which
19869 all of a client's bridges collude to restrict the exit nodes that
19870 the client knows about. Fixes bug 5343.
19872 o Major bugfixes (on Tor 0.2.3.x):
19873 - Avoid an assert when managed proxies like obfsproxy are configured,
19874 and we receive HUP signals or setconf attempts too rapidly. This
19875 situation happens most commonly when Vidalia tries to attach to
19876 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19877 bugfix on 0.2.3.6-alpha.
19878 - Fix a relay-side pluggable transports bug where managed proxies were
19879 unreachable from the Internet, because Tor asked them to bind on
19880 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19881 - Stop discarding command-line arguments when TestingTorNetwork
19882 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19883 0.2.3.9-alpha, where task 4552 added support for two layers of
19885 - Resume allowing the unit tests to run in gdb. This was accidentally
19886 made impossible when the DisableDebuggerAttachment option was
19887 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19888 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19889 0.2.3.11-alpha. Reported by Anthony G. Basile.
19891 o Minor bugfixes (on 0.2.2.x and earlier):
19892 - Ensure we don't cannibalize circuits that are longer than three hops
19893 already, so we don't end up making circuits with 5 or more
19894 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19895 0.1.0.1-rc which introduced cannibalization.
19896 - Detect and reject certain misformed escape sequences in
19897 configuration values. Previously, these values would cause us
19898 to crash if received in a torrc file or over an authenticated
19899 control port. Bug found by Esteban Manchado Velázquez, and
19900 independently by Robert Connolly from Matta Consulting who further
19901 noted that it allows a post-authentication heap overflow. Patch
19902 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19903 bugfix on 0.2.0.16-alpha.
19904 - Fix a compile warning when using the --enable-openbsd-malloc
19905 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19906 - Directory caches no longer refuse to clean out descriptors because
19907 of missing v2 networkstatus documents, unless they're configured
19908 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19909 0.2.2.26-beta. Patch by Daniel Bryg.
19910 - Update to the latest version of the tinytest unit testing framework.
19911 This includes a couple of bugfixes that can be relevant for
19912 running forked unit tests on Windows, and removes all reserved
19915 o Minor bugfixes (on 0.2.3.x):
19916 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19917 4296; bugfix on 0.2.3.1-alpha.
19918 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19919 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19920 on 0.2.3.6-alpha. Patch by "frosty".
19921 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
19922 option, so that the IP stack doesn't decide to use it for IPv4
19923 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
19924 - Ensure that variables set in Tor's environment cannot override
19925 environment variables that Tor passes to a managed
19926 pluggable-transport proxy. Previously, Tor would pass every
19927 variable in its environment to managed proxies along with the new
19928 ones, in such a way that on many operating systems, the inherited
19929 environment variables would override those which Tor tried to
19930 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
19931 bugfix on 0.2.3.9-alpha for Windows.
19934 - A wide variety of new unit tests by Esteban Manchado Velázquez.
19935 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
19936 - Update to the March 6 2012 Maxmind GeoLite Country database.
19939 Changes in version 0.2.3.12-alpha - 2012-02-13
19940 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
19941 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
19942 when Tor is configured to use a pluggable transport like obfsproxy.
19945 - Fix builds when the path to sed, openssl, or sha1sum contains
19946 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19948 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
19949 connections. This change should allow busy exit relays to stop
19950 running out of available sockets as quickly. Fixes bug 4950;
19951 bugfix on 0.2.2.26-beta.
19952 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
19953 would ask the bridge for microdescriptors, which are only supported
19954 in 0.2.3.x, and then fail to bootstrap when it didn't get the
19955 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
19956 - Properly set up obfsproxy's environment when in managed mode. The
19957 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
19958 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
19959 5076 and 5082; bugfix on 0.2.3.6-alpha.
19962 - Use the dead_strip option when building Tor on OS X. This reduces
19963 binary size by almost 19% when linking openssl and libevent
19964 statically, which we do for Tor Browser Bundle.
19965 - Fix broken URLs in the sample torrc file, and tell readers about
19966 the OutboundBindAddress, ExitPolicyRejectPrivate, and
19967 PublishServerDescriptor options. Addresses bug 4652.
19968 - Update to the February 7 2012 Maxmind GeoLite Country database.
19971 - Downgrade the "We're missing a certificate" message from notice
19972 to info: people kept mistaking it for a real problem, whereas it
19973 is seldom the problem even when we are failing to bootstrap. Fixes
19974 bug 5067; bugfix on 0.2.0.10-alpha.
19975 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
19976 managed pluggable transport server proxy's environment.
19977 Previously, we would put it there, even though Tor doesn't
19978 implement an 'extended server port' yet, and even though Tor
19979 almost certainly isn't listening at that address. For now, we set
19980 it to an empty string to avoid crashing older obfsproxies. Bugfix
19982 - Log the heartbeat message every HeartbeatPeriod seconds, not every
19983 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
19984 0.2.3.1-alpha. Bug reported by Scott Bennett.
19985 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
19986 bugfix on 0.2.3.11-alpha.
19987 - Update "ClientOnly" man page entry to explain that there isn't
19988 really any point to messing with it. Resolves ticket 5005.
19989 - Use the correct CVE number for CVE-2011-4576 in our comments and
19990 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
19993 o Code simplifications and refactoring:
19994 - Use the _WIN32 macro throughout our code to detect Windows.
19995 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
19999 Changes in version 0.2.3.11-alpha - 2012-01-22
20000 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
20001 the last step of the plan to limit maximum circuit length, includes
20002 a wide variety of hidden service performance and correctness fixes,
20003 works around an OpenSSL security flaw if your distro is too stubborn
20004 to upgrade, and fixes a bunch of smaller issues.
20007 - Now that Tor 0.2.0.x is completely deprecated, enable the final
20008 part of "Proposal 110: Avoiding infinite length circuits" by
20009 refusing all circuit-extend requests that do not use a relay_early
20010 cell. This change helps Tor resist a class of denial-of-service
20011 attacks by limiting the maximum circuit length.
20012 - Adjust the number of introduction points that a hidden service
20013 will try to maintain based on how long its introduction points
20014 remain in use and how many introductions they handle. Fixes
20016 - Try to use system facilities for enumerating local interface
20017 addresses, before falling back to our old approach (which was
20018 binding a UDP socket, and calling getsockname() on it). That
20019 approach was scaring OS X users whose draconian firewall
20020 software warned about binding to UDP sockets, regardless of
20021 whether packets were sent. Now we try to use getifaddrs(),
20022 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
20023 system supports. Resolves ticket 1827.
20025 o Major security workaround:
20026 - When building or running with any version of OpenSSL earlier
20027 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
20028 versions have a bug (CVE-2011-4576) in which their block cipher
20029 padding includes uninitialized data, potentially leaking sensitive
20030 information to any peer with whom they make a SSLv3 connection. Tor
20031 does not use SSL v3 by default, but a hostile client or server
20032 could force an SSLv3 connection in order to gain information that
20033 they shouldn't have been able to get. The best solution here is to
20034 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
20035 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
20036 to make sure that the bug can't happen.
20039 - Fix the SOCKET_OK test that we use to tell when socket
20040 creation fails so that it works on Win64. Fixes part of bug 4533;
20041 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
20042 - Correct our replacements for the timeradd() and timersub() functions
20043 on platforms that lack them (for example, Windows). The timersub()
20044 function is used when expiring circuits, while timeradd() is
20045 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
20046 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
20047 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
20048 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
20049 bug at runtime, not compile time, because some distributions hack
20050 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
20051 on 0.2.3.9-alpha. Found by Pascal.
20053 o Minor features (controller):
20054 - Use absolute path names when reporting the torrc filename in the
20055 control protocol, so a controller can more easily find the torrc
20056 file. Resolves bug 1101.
20057 - Extend the control protocol to report flags that control a circuit's
20058 path selection in CIRC events and in replies to 'GETINFO
20059 circuit-status'. Implements part of ticket 2411.
20060 - Extend the control protocol to report the hidden service address
20061 and current state of a hidden-service-related circuit in CIRC
20062 events and in replies to 'GETINFO circuit-status'. Implements part
20064 - When reporting the path to the cookie file to the controller,
20065 give an absolute path. Resolves ticket 4881.
20066 - Allow controllers to request an event notification whenever a
20067 circuit is cannibalized or its purpose is changed. Implements
20068 part of ticket 3457.
20069 - Include the creation time of a circuit in CIRC and CIRC2
20070 control-port events and the list produced by the 'GETINFO
20071 circuit-status' control-port command.
20073 o Minor features (directory authorities):
20074 - Directory authorities now reject versions of Tor older than
20075 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
20076 inclusive. These versions accounted for only a small fraction of
20077 the Tor network, and have numerous known security issues. Resolves
20079 - Authority operators can now vote for all relays in a given
20080 set of countries to be BadDir/BadExit/Invalid/Rejected.
20081 - Provide two consensus parameters (FastFlagMinThreshold and
20082 FastFlagMaxThreshold) to control the range of allowable bandwidths
20083 for the Fast directory flag. These allow authorities to run
20084 experiments on appropriate requirements for being a "Fast" node.
20085 The AuthDirFastGuarantee config value still applies. Implements
20087 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
20088 directory authority option (introduced in Tor 0.2.2.34).
20090 o Minor features (other):
20091 - Don't disable the DirPort when we cannot exceed our AccountingMax
20092 limit during this interval because the effective bandwidthrate is
20093 low enough. This is useful in a situation where AccountMax is only
20094 used as an additional safeguard or to provide statistics.
20095 - Prepend an informative header to generated dynamic_dh_params files.
20096 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
20097 EntryNodes will have no effect. Resolves issue 2571.
20098 - Log more useful messages when we fail to disable debugger
20100 - Log which authority we're missing votes from when we go to fetch
20101 them from the other auths.
20102 - Log (at debug level) whenever a circuit's purpose is changed.
20103 - Add missing documentation for the MaxClientCircuitsPending,
20104 UseMicrodescriptors, UserspaceIOCPBuffers, and
20105 _UseFilteringSSLBufferevents options, all introduced during
20106 the 0.2.3.x series.
20107 - Update to the January 3 2012 Maxmind GeoLite Country database.
20109 o Minor bugfixes (hidden services):
20110 - Don't close hidden service client circuits which have almost
20111 finished connecting to their destination when they reach
20112 the normal circuit-build timeout. Previously, we would close
20113 introduction circuits which are waiting for an acknowledgement
20114 from the introduction point, and rendezvous circuits which have
20115 been specified in an INTRODUCE1 cell sent to a hidden service,
20116 after the normal CBT. Now, we mark them as 'timed out', and launch
20117 another rendezvous attempt in parallel. This behavior change can
20118 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
20119 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
20120 - Don't close hidden-service-side rendezvous circuits when they
20121 reach the normal circuit-build timeout. This behavior change can
20122 be disabled using the new
20123 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
20124 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
20125 - Make sure we never mark the wrong rendezvous circuit as having
20126 had its introduction cell acknowledged by the introduction-point
20127 relay. Previously, when we received an INTRODUCE_ACK cell on a
20128 client-side hidden-service introduction circuit, we might have
20129 marked a rendezvous circuit other than the one we specified in
20130 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
20131 a warning message and interfered with the hidden service
20132 connection-establishment process. Fixes bug 4759; bugfix on
20133 0.2.3.3-alpha, when we added the stream-isolation feature which
20134 might cause Tor to open multiple rendezvous circuits for the same
20136 - Don't trigger an assertion failure when we mark a new client-side
20137 hidden-service introduction circuit for close during the process
20138 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
20141 o Minor bugfixes (log messages):
20142 - Correctly spell "connect" in a log message on failure to create a
20143 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
20145 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
20146 Fixes bug 4856; bugfix on Tor 0.0.6.
20147 - Fix the log message describing how we work around discovering
20148 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
20149 4837; bugfix on 0.2.2.9-alpha.
20150 - When logging about a disallowed .exit name, do not also call it
20151 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
20153 o Minor bugfixes (build fixes):
20154 - During configure, detect when we're building with clang version
20155 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
20156 CFLAGS. clang doesn't support them yet.
20157 - During configure, search for library containing cos function as
20158 libm lives in libcore on some platforms (BeOS/Haiku). Linking
20159 against libm was hard-coded before. Fixes the first part of bug
20160 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
20162 - Detect attempts to build Tor on (as yet hypothetical) versions
20163 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
20164 fix for bug 4533. Bugfix on 0.2.2.28-beta.
20165 - Preprocessor directives should not be put inside the arguments
20166 of a macro. This would break compilation with GCC releases prior
20167 to version 3.3. We would never recommend such an old GCC version,
20168 but it is apparently required for binary compatibility on some
20169 platforms (namely, certain builds of Haiku). Fixes the other part
20170 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
20173 o Minor bugfixes (other):
20174 - Older Linux kernels erroneously respond to strange nmap behavior
20175 by having accept() return successfully with a zero-length
20176 socket. When this happens, just close the connection. Previously,
20177 we would try harder to learn the remote address: but there was
20178 no such remote address to learn, and our method for trying to
20179 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20180 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20181 - Fix null-pointer access that could occur if TLS allocation failed.
20182 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
20183 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
20184 accidentally been reverted.
20185 - Fix our implementation of crypto_random_hostname() so it can't
20186 overflow on ridiculously large inputs. (No Tor version has ever
20187 provided this kind of bad inputs, but let's be correct in depth.)
20188 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
20189 - Find more places in the code that should have been testing for
20190 invalid sockets using the SOCKET_OK macro. Required for a fix
20191 for bug 4533. Bugfix on 0.2.2.28-beta.
20192 - Fix an assertion failure when, while running with bufferevents, a
20193 connection finishes connecting after it is marked for close, but
20194 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
20195 - test_util_spawn_background_ok() hardcoded the expected value
20196 for ENOENT to 2. This isn't portable as error numbers are
20197 platform specific, and particularly the hurd has ENOENT at
20198 0x40000002. Construct expected string at runtime, using the correct
20199 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
20200 - Reject attempts to disable DisableDebuggerAttachment while Tor is
20201 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
20202 - Use an appropriate-width type for sockets in tor-fw-helper on
20203 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
20206 - When sending or relaying a RELAY_EARLY cell, we used to convert
20207 it to a RELAY cell if the connection was using the v1 link
20208 protocol. This was a workaround for older versions of Tor, which
20209 didn't handle RELAY_EARLY cells properly. Now that all supported
20210 versions can handle RELAY_EARLY cells, and now that we're enforcing
20211 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20212 remove this workaround. Addresses bug 4786.
20214 o Code simplifications and refactoring:
20215 - Use OpenSSL's built-in SSL_state_string_long() instead of our
20216 own homebrewed ssl_state_to_string() replacement. Patch from
20217 Emile Snyder. Fixes bug 4653.
20218 - Use macros to indicate OpenSSL versions, so we don't need to worry
20219 about accidental hexadecimal bit shifts.
20220 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
20222 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
20223 - Use the smartlist_add_asprintf() alias more consistently.
20224 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
20225 invalid value, rather than just -1.
20226 - Rename a handful of old identifiers, mostly related to crypto
20227 structures and crypto functions. By convention, our "create an
20228 object" functions are called "type_new()", our "free an object"
20229 functions are called "type_free()", and our types indicate that
20230 they are types only with a final "_t". But a handful of older
20231 types and functions broke these rules, with function names like
20232 "type_create" or "subsystem_op_type", or with type names like
20236 Changes in version 0.2.3.10-alpha - 2011-12-16
20237 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
20238 Tor's buffers code. Absolutely everybody should upgrade.
20240 The bug relied on an incorrect calculation when making data continuous
20241 in one of our IO buffers, if the first chunk of the buffer was
20242 misaligned by just the wrong amount. The miscalculation would allow an
20243 attacker to overflow a piece of heap-allocated memory. To mount this
20244 attack, the attacker would need to either open a SOCKS connection to
20245 Tor's SocksPort (usually restricted to localhost), or target a Tor
20246 instance configured to make its connections through a SOCKS proxy
20247 (which Tor does not do by default).
20249 Good security practice requires that all heap-overflow bugs should be
20250 presumed to be exploitable until proven otherwise, so we are treating
20251 this as a potential code execution attack. Please upgrade immediately!
20252 This bug does not affect bufferevents-based builds of Tor. Special
20253 thanks to "Vektor" for reporting this issue to us!
20255 This release also contains a few minor bugfixes for issues discovered
20259 - Fix a heap overflow bug that could occur when trying to pull
20260 data into the first chunk of a buffer, when that chunk had
20261 already had some data drained from it. Fixes CVE-2011-2778;
20262 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20265 - If we can't attach streams to a rendezvous circuit when we
20266 finish connecting to a hidden service, clear the rendezvous
20267 circuit's stream-isolation state and try to attach streams
20268 again. Previously, we cleared rendezvous circuits' isolation
20269 state either too early (if they were freshly built) or not at all
20270 (if they had been built earlier and were cannibalized). Bugfix on
20271 0.2.3.3-alpha; fixes bug 4655.
20272 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
20273 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
20274 - Fix an assertion failure when a relay with accounting enabled
20275 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
20278 - Update to the December 6 2011 Maxmind GeoLite Country database.
20281 Changes in version 0.2.2.35 - 2011-12-16
20282 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20283 buffers code. Absolutely everybody should upgrade.
20285 The bug relied on an incorrect calculation when making data continuous
20286 in one of our IO buffers, if the first chunk of the buffer was
20287 misaligned by just the wrong amount. The miscalculation would allow an
20288 attacker to overflow a piece of heap-allocated memory. To mount this
20289 attack, the attacker would need to either open a SOCKS connection to
20290 Tor's SocksPort (usually restricted to localhost), or target a Tor
20291 instance configured to make its connections through a SOCKS proxy
20292 (which Tor does not do by default).
20294 Good security practice requires that all heap-overflow bugs should be
20295 presumed to be exploitable until proven otherwise, so we are treating
20296 this as a potential code execution attack. Please upgrade immediately!
20297 This bug does not affect bufferevents-based builds of Tor. Special
20298 thanks to "Vektor" for reporting this issue to us!
20300 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20301 crash bugs for unusual configurations, and a long-term bug that
20302 would prevent Tor from starting on Windows machines with draconian
20305 With this release, we remind everyone that 0.2.0.x has reached its
20306 formal end-of-life. Those Tor versions have many known flaws, and
20307 nobody should be using them. You should upgrade -- ideally to the
20308 0.2.2.x series. If you're using a Linux or BSD and its packages are
20309 obsolete, stop using those packages and upgrade anyway.
20311 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20312 longer receive support after some time in early 2012.
20315 - Fix a heap overflow bug that could occur when trying to pull
20316 data into the first chunk of a buffer, when that chunk had
20317 already had some data drained from it. Fixes CVE-2011-2778;
20318 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20319 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20320 that it doesn't attempt to allocate a socketpair. This could cause
20321 some problems on Windows systems with overzealous firewalls. Fix for
20322 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20324 - If we mark an OR connection for close based on a cell we process,
20325 don't process any further cells on it. We already avoid further
20326 reads on marked-for-close connections, but now we also discard the
20327 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20328 which was the first version where we might mark a connection for
20329 close based on processing a cell on it.
20330 - Correctly sanity-check that we don't underflow on a memory
20331 allocation (and then assert) for hidden service introduction
20332 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20333 bugfix on 0.2.1.5-alpha.
20334 - Fix a memory leak when we check whether a hidden service
20335 descriptor has any usable introduction points left. Fixes bug
20336 4424. Bugfix on 0.2.2.25-alpha.
20337 - Don't crash when we're running as a relay and don't have a GeoIP
20338 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20339 we've had in the 0.2.3.x branch already.
20340 - When running as a client, do not print a misleading (and plain
20341 wrong) log message that we're collecting "directory request"
20342 statistics: clients don't collect statistics. Also don't create a
20343 useless (because empty) stats file in the stats/ directory. Fixes
20344 bug 4353; bugfix on 0.2.2.34.
20347 - Detect failure to initialize Libevent. This fix provides better
20348 detection for future instances of bug 4457.
20349 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20350 function. This was eating up hideously large amounts of time on some
20351 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20352 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20353 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20355 - Don't warn about unused log_mutex in log.c when building with
20356 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20357 0.1.0.6-rc which introduced --disable-threads.
20358 - When configuring, starting, or stopping an NT service, stop
20359 immediately after the service configuration attempt has succeeded
20360 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20361 - When sending a NETINFO cell, include the original address
20362 received for the other side, not its canonical address. Found
20363 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20364 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20365 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20366 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20367 occurred when a client tried to fetch a descriptor for a bridge
20368 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20369 - Backport fixes for a pair of compilation warnings on Windows.
20370 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20371 - If we had ever tried to call tor_addr_to_str on an address of
20372 unknown type, we would have done a strdup on an uninitialized
20373 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20374 Reported by "troll_un".
20375 - Correctly detect and handle transient lookup failures from
20376 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20377 Reported by "troll_un".
20378 - Fix null-pointer access that could occur if TLS allocation failed.
20379 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20380 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20381 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20384 - Add two new config options for directory authorities:
20385 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20386 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20387 that is always sufficient to satisfy the bandwidth requirement for
20388 the Guard flag. Now it will be easier for researchers to simulate
20389 Tor networks with different values. Resolves ticket 4484.
20390 - When Tor ignores a hidden service specified in its configuration,
20391 include the hidden service's directory in the warning message.
20392 Previously, we would only tell the user that some hidden service
20393 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20394 - Update to the December 6 2011 Maxmind GeoLite Country database.
20396 o Packaging changes:
20397 - Make it easier to automate expert package builds on Windows,
20398 by removing an absolute path from makensis.exe command.
20401 Changes in version 0.2.1.32 - 2011-12-16
20402 Tor 0.2.1.32 backports important security and privacy fixes for
20403 oldstable. This release is intended only for package maintainers and
20404 others who cannot use the 0.2.2 stable series. All others should be
20405 using Tor 0.2.2.x or newer.
20407 The Tor 0.2.1.x series will reach formal end-of-life some time in
20408 early 2012; we will stop releasing patches for it then.
20410 o Major bugfixes (also included in 0.2.2.x):
20411 - Correctly sanity-check that we don't underflow on a memory
20412 allocation (and then assert) for hidden service introduction
20413 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20414 bugfix on 0.2.1.5-alpha.
20415 - Fix a heap overflow bug that could occur when trying to pull
20416 data into the first chunk of a buffer, when that chunk had
20417 already had some data drained from it. Fixes CVE-2011-2778;
20418 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20421 - Update to the December 6 2011 Maxmind GeoLite Country database.
20424 Changes in version 0.2.3.9-alpha - 2011-12-08
20425 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
20426 a "DisableNetwork" security feature that bundles can use to avoid
20427 touching the network until bridges are configured, moves forward on
20428 the pluggable transport design, fixes a flaw in the hidden service
20429 design that unnecessarily prevented clients with wrong clocks from
20430 reaching hidden services, and fixes a wide variety of other issues.
20433 - Clients can now connect to private bridges over IPv6. Bridges
20434 still need at least one IPv4 address in order to connect to
20435 other relays. Note that we don't yet handle the case where the
20436 user has two bridge lines for the same bridge (one IPv4, one
20437 IPv6). Implements parts of proposal 186.
20438 - New "DisableNetwork" config option to prevent Tor from launching any
20439 connections or accepting any connections except on a control port.
20440 Bundles and controllers can set this option before letting Tor talk
20441 to the rest of the network, for example to prevent any connections
20442 to a non-bridge address. Packages like Orbot can also use this
20443 option to instruct Tor to save power when the network is off.
20444 - Clients and bridges can now be configured to use a separate
20445 "transport" proxy. This approach makes the censorship arms race
20446 easier by allowing bridges to use protocol obfuscation plugins. It
20447 implements the "managed proxy" part of proposal 180 (ticket 3472).
20448 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20449 implementation. It makes AES_CTR about 7% faster than our old one
20450 (which was about 10% faster than the one OpenSSL used to provide).
20451 Resolves ticket 4526.
20452 - Add a "tor2web mode" for clients that want to connect to hidden
20453 services non-anonymously (and possibly more quickly). As a safety
20454 measure to try to keep users from turning this on without knowing
20455 what they are doing, tor2web mode must be explicitly enabled at
20456 compile time, and a copy of Tor compiled to run in tor2web mode
20457 cannot be used as a normal Tor client. Implements feature 2553.
20458 - Add experimental support for running on Windows with IOCP and no
20459 kernel-space socket buffers. This feature is controlled by a new
20460 "UserspaceIOCPBuffers" config option (off by default), which has
20461 no effect unless Tor has been built with support for bufferevents,
20462 is running on Windows, and has enabled IOCP. This may, in the long
20463 run, help solve or mitigate bug 98.
20464 - Use a more secure consensus parameter voting algorithm. Now at
20465 least three directory authorities or a majority of them must
20466 vote on a given parameter before it will be included in the
20467 consensus. Implements proposal 178.
20470 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20471 They used to check that the timestamp was within 30 minutes
20472 of their system clock, so they could cap the size of their
20473 replay-detection cache, but that approach unnecessarily refused
20474 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20475 the v3 intro-point protocol (the first one which sent a timestamp
20476 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20477 - Only use the EVP interface when AES acceleration is enabled,
20478 to avoid a 5-7% performance regression. Resolves issue 4525;
20479 bugfix on 0.2.3.8-alpha.
20481 o Privacy/anonymity features (bridge detection):
20482 - Make bridge SSL certificates a bit more stealthy by using random
20483 serial numbers, in the same fashion as OpenSSL when generating
20484 self-signed certificates. Implements ticket 4584.
20485 - Introduce a new config option "DynamicDHGroups", enabled by
20486 default, which provides each bridge with a unique prime DH modulus
20487 to be used during SSL handshakes. This option attempts to help
20488 against censors who might use the Apache DH modulus as a static
20489 identifier for bridges. Addresses ticket 4548.
20491 o Minor features (new/different config options):
20492 - New configuration option "DisableDebuggerAttachment" (on by default)
20493 to prevent basic debugging attachment attempts by other processes.
20494 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20495 - Allow MapAddress directives to specify matches against super-domains,
20496 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20497 Implements issue 933.
20498 - Slightly change behavior of "list" options (that is, config
20499 options that can appear more than once) when they appear both in
20500 torrc and on the command line. Previously, the command-line options
20501 would be appended to the ones from torrc. Now, the command-line
20502 options override the torrc options entirely. This new behavior
20503 allows the user to override list options (like exit policies and
20504 ports to listen on) from the command line, rather than simply
20505 appending to the list.
20506 - You can get the old (appending) command-line behavior for "list"
20507 options by prefixing the option name with a "+".
20508 - You can remove all the values for a "list" option from the command
20509 line without adding any new ones by prefixing the option name
20511 - Add experimental support for a "defaults" torrc file to be parsed
20512 before the regular torrc. Torrc options override the defaults file's
20513 options in the same way that the command line overrides the torrc.
20514 The SAVECONF controller command saves only those options which
20515 differ between the current configuration and the defaults file. HUP
20516 reloads both files. (Note: This is an experimental feature; its
20517 behavior will probably be refined in future 0.2.3.x-alpha versions
20518 to better meet packagers' needs.) Implements task 4552.
20521 - Try to make the introductory warning message that Tor prints on
20522 startup more useful for actually finding help and information.
20523 Resolves ticket 2474.
20524 - Running "make version" now displays the version of Tor that
20525 we're about to build. Idea from katmagic; resolves issue 4400.
20526 - Expire old or over-used hidden service introduction points.
20527 Required by fix for bug 3460.
20528 - Move the replay-detection cache for the RSA-encrypted parts of
20529 INTRODUCE2 cells to the introduction point data structures.
20530 Previously, we would use one replay-detection cache per hidden
20531 service. Required by fix for bug 3460.
20532 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20533 public key replay-detection cache from 60 minutes to 5 minutes. This
20534 replay-detection cache is now used only to detect multiple
20535 INTRODUCE2 cells specifying the same rendezvous point, so we can
20536 avoid launching multiple simultaneous attempts to connect to it.
20538 o Minor bugfixes (on Tor 0.2.2.x and earlier):
20539 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20540 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20542 - Fix a minor formatting issue in one of tor-gencert's error messages.
20544 - Prevent a false positive from the check-spaces script, by disabling
20545 the "whitespace between function name and (" check for functions
20547 - Fix a log message suggesting that people contact a non-existent
20548 email address. Fixes bug 3448.
20549 - Fix null-pointer access that could occur if TLS allocation failed.
20550 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20551 - Report a real bootstrap problem to the controller on router
20552 identity mismatch. Previously we just said "foo", which probably
20553 made a lot of sense at the time. Fixes bug 4169; bugfix on
20555 - If we had ever tried to call tor_addr_to_str() on an address of
20556 unknown type, we would have done a strdup() on an uninitialized
20557 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20558 Reported by "troll_un".
20559 - Correctly detect and handle transient lookup failures from
20560 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20561 Reported by "troll_un".
20562 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20563 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20564 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20565 bug 4532; found by "troll_un".
20567 o Minor bugfixes (on Tor 0.2.3.x):
20568 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
20570 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
20571 circuit for use as a hidden service client's rendezvous point.
20572 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
20573 with help from wanoskarnet.
20574 - Restore behavior of overriding SocksPort, ORPort, and similar
20575 options from the command line. Bugfix on 0.2.3.3-alpha.
20578 - Properly handle the case where the build-tree is not the same
20579 as the source tree when generating src/common/common_sha1.i,
20580 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20581 bugfix on 0.2.0.1-alpha.
20583 o Code simplifications, cleanups, and refactorings:
20584 - Remove the pure attribute from all functions that used it
20585 previously. In many cases we assigned it incorrectly, because the
20586 functions might assert or call impure functions, and we don't have
20587 evidence that keeping the pure attribute is worthwhile. Implements
20588 changes suggested in ticket 4421.
20589 - Remove some dead code spotted by coverity. Fixes cid 432.
20590 Bugfix on 0.2.3.1-alpha, closes bug 4637.
20593 Changes in version 0.2.3.8-alpha - 2011-11-22
20594 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
20595 socketpair-related bug that has been bothering Windows users. It adds
20596 support to serve microdescriptors to controllers, so Vidalia's network
20597 map can resume listing relays (once Vidalia implements its side),
20598 and adds better support for hardware AES acceleration. Finally, it
20599 starts the process of adjusting the bandwidth cutoff for getting the
20600 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
20601 that tiny relays harm performance more than they help network capacity.
20604 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20605 that it doesn't attempt to allocate a socketpair. This could cause
20606 some problems on Windows systems with overzealous firewalls. Fix for
20607 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20609 - Correctly sanity-check that we don't underflow on a memory
20610 allocation (and then assert) for hidden service introduction
20611 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20612 bugfix on 0.2.1.5-alpha.
20613 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20614 flag. In the past few years the average relay speed has picked
20615 up, and while the "top 7/8 of the network get the Fast flag" and
20616 "all relays with 20KB or more of capacity get the Fast flag" rules
20617 used to have the same result, now the top 7/8 of the network has
20618 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20619 - Fix a rare assertion failure when checking whether a v0 hidden
20620 service descriptor has any usable introduction points left, and
20621 we don't have enough information to build a circuit to the first
20622 intro point named in the descriptor. The HS client code in
20623 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
20624 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
20625 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
20626 - Make bridge authorities not crash when they are asked for their own
20627 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
20628 - When running as a client, do not print a misleading (and plain
20629 wrong) log message that we're collecting "directory request"
20630 statistics: clients don't collect statistics. Also don't create a
20631 useless (because empty) stats file in the stats/ directory. Fixes
20632 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
20635 - Allow Tor controllers like Vidalia to obtain the microdescriptor
20636 for a relay by identity digest or nickname. Previously,
20637 microdescriptors were only available by their own digests, so a
20638 controller would have to ask for and parse the whole microdescriptor
20639 consensus in order to look up a single relay's microdesc. Fixes
20640 bug 3832; bugfix on 0.2.3.1-alpha.
20641 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20642 operations can use hardware acceleration (if present). Resolves
20645 o Minor bugfixes (on 0.2.2.x and earlier):
20646 - Detect failure to initialize Libevent. This fix provides better
20647 detection for future instances of bug 4457.
20648 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20649 function. This was eating up hideously large amounts of time on some
20650 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20651 - Don't warn about unused log_mutex in log.c when building with
20652 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20653 0.1.0.6-rc which introduced --disable-threads.
20654 - Allow manual 'authenticate' commands to the controller interface
20655 from netcat (nc) as well as telnet. We were rejecting them because
20656 they didn't come with the expected whitespace at the end of the
20657 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20658 - Fix some (not actually triggerable) buffer size checks in usage of
20659 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20661 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20662 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20663 - When configuring, starting, or stopping an NT service, stop
20664 immediately after the service configuration attempt has succeeded
20665 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20666 - When sending a NETINFO cell, include the original address
20667 received for the other side, not its canonical address. Found
20668 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20669 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20670 can pick them up when the tests aren't disabled. Bugfix on
20671 0.2.2.4-alpha which introduced tinytest.
20672 - Fix a memory leak when we check whether a hidden service
20673 descriptor has any usable introduction points left. Fixes bug
20674 4424. Bugfix on 0.2.2.25-alpha.
20675 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20676 occurred when a client tried to fetch a descriptor for a bridge
20677 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20679 o Minor bugfixes (on 0.2.3.x):
20680 - Make util unit tests build correctly with MSVC. Bugfix on
20681 0.2.3.3-alpha. Patch by Gisle Vanem.
20682 - Successfully detect AUTH_CHALLENGE cells with no recognized
20683 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
20684 Found by frosty_un.
20685 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
20686 it should still send a NETINFO cell to allow the connection to
20687 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
20689 - Log less loudly when we get an invalid authentication certificate
20690 from a source other than a directory authority: it's not unusual
20691 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
20693 - Tolerate servers with more clock skew in their authentication
20694 certificates than previously. Fixes bug 4371; bugfix on
20696 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
20697 on 0.2.3.4-alpha and 0.2.3.6-alpha.
20700 - Add two new config options for directory authorities:
20701 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20702 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20703 that is always sufficient to satisfy the bandwidth requirement for
20704 the Guard flag. Now it will be easier for researchers to simulate
20705 Tor networks with different values. Resolves ticket 4484.
20706 - When Tor ignores a hidden service specified in its configuration,
20707 include the hidden service's directory in the warning message.
20708 Previously, we would only tell the user that some hidden service
20709 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20710 - When we fail to initialize Libevent, retry with IOCP disabled so we
20711 don't need to turn on multi-threading support in Libevent, which in
20712 turn requires a working socketpair(). This is a workaround for bug
20713 4457, which affects Libevent versions from 2.0.1-alpha through
20715 - Detect when we try to build on a platform that doesn't define
20716 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20717 - Update to the November 1 2011 Maxmind GeoLite Country database.
20719 o Packaging changes:
20720 - Make it easier to automate expert package builds on Windows,
20721 by removing an absolute path from makensis.exe command.
20723 o Code simplifications and refactoring:
20724 - Remove some redundant #include directives throughout the code.
20725 Patch from Andrea Gelmini.
20726 - Unconditionally use OpenSSL's AES implementation instead of our
20727 old built-in one. OpenSSL's AES has been better for a while, and
20728 relatively few servers should still be on any version of OpenSSL
20729 that doesn't have good optimized assembly AES.
20730 - Use the name "CERTS" consistently to refer to the new cell type;
20731 we were calling it CERT in some places and CERTS in others.
20734 - Numerous new unit tests for functions in util.c and address.c by
20736 - The long-disabled benchmark tests are now split into their own
20737 ./src/test/bench binary.
20738 - The benchmark tests can now use more accurate timers than
20739 gettimeofday() when such timers are available.
20742 Changes in version 0.2.3.7-alpha - 2011-10-30
20743 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20744 the new v3 handshake. It also resolves yet another bridge address
20748 - If we mark an OR connection for close based on a cell we process,
20749 don't process any further cells on it. We already avoid further
20750 reads on marked-for-close connections, but now we also discard the
20751 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20752 which was the first version where we might mark a connection for
20753 close based on processing a cell on it.
20754 - Fix a double-free bug that would occur when we received an invalid
20755 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20756 bugfix on 0.2.3.6-alpha.
20757 - Bridges no longer include their address in NETINFO cells on outgoing
20758 OR connections, to allow them to blend in better with clients.
20759 Removes another avenue for enumerating bridges. Reported by
20760 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20761 cells were introduced.
20764 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20765 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20768 Changes in version 0.2.3.6-alpha - 2011-10-26
20769 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20770 anonymity vulnerability where an attacker can deanonymize Tor
20771 users. Everybody should upgrade.
20773 This release also features support for a new v3 connection handshake
20774 protocol, and fixes to make hidden service connections more robust.
20777 - Implement a new handshake protocol (v3) for authenticating Tors to
20778 each other over TLS. It should be more resistant to fingerprinting
20779 than previous protocols, and should require less TLS hacking for
20780 future Tor implementations. Implements proposal 176.
20781 - Allow variable-length padding cells to disguise the length of
20782 Tor's TLS records. Implements part of proposal 184.
20784 o Privacy/anonymity fixes (clients):
20785 - Clients and bridges no longer send TLS certificate chains on
20786 outgoing OR connections. Previously, each client or bridge would
20787 use the same cert chain for all outgoing OR connections until
20788 its IP address changes, which allowed any relay that the client
20789 or bridge contacted to determine which entry guards it is using.
20790 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20791 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20792 no longer considers that connection as suitable for satisfying a
20793 circuit EXTEND request. Now relays can protect clients from the
20794 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20795 - Directory authorities no longer assign the Guard flag to relays
20796 that haven't upgraded to the above "refuse EXTEND requests
20797 to client connections" fix. Now directory authorities can
20798 protect clients from the CVE-2011-2768 issue even if neither
20799 the clients nor the relays have upgraded yet. There's a new
20800 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20801 to let us transition smoothly, else tomorrow there would be no
20804 o Major bugfixes (hidden services):
20805 - Improve hidden service robustness: when an attempt to connect to
20806 a hidden service ends, be willing to refetch its hidden service
20807 descriptors from each of the HSDir relays responsible for them
20808 immediately. Previously, we would not consider refetching the
20809 service's descriptors from each HSDir for 15 minutes after the last
20810 fetch, which was inconvenient if the hidden service was not running
20811 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20812 - When one of a hidden service's introduction points appears to be
20813 unreachable, stop trying it. Previously, we would keep trying
20814 to build circuits to the introduction point until we lost the
20815 descriptor, usually because the user gave up and restarted Tor.
20816 Partly fixes bug 3825.
20817 - Don't launch a useless circuit after failing to use one of a
20818 hidden service's introduction points. Previously, we would
20819 launch a new introduction circuit, but not set the hidden service
20820 which that circuit was intended to connect to, so it would never
20821 actually be used. A different piece of code would then create a
20822 new introduction circuit correctly. Bug reported by katmagic and
20823 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20825 o Major bugfixes (other):
20826 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20827 that they initiated. Relays could distinguish incoming bridge
20828 connections from client connections, creating another avenue for
20829 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20830 Found by "frosty_un".
20831 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20832 tor gets started. This prevents a wrong average bandwidth
20833 estimate, which would cause relays to always start a new accounting
20834 interval at the earliest possible moment. Fixes bug 2003; bugfix
20835 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20836 immensely in tracking this bug down.
20837 - Fix a crash bug when changing node restrictions while a DNS lookup
20838 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20841 o Minor bugfixes (on 0.2.2.x and earlier):
20842 - When a hidden service turns an extra service-side introduction
20843 circuit into a general-purpose circuit, free the rend_data and
20844 intro_key fields first, so we won't leak memory if the circuit
20845 is cannibalized for use as another service-side introduction
20846 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20847 - Rephrase the log message emitted if the TestSocks check is
20848 successful. Patch from Fabian Keil; fixes bug 4094.
20849 - Bridges now skip DNS self-tests, to act a little more stealthily.
20850 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20851 bridges. Patch by "warms0x".
20852 - Remove a confusing dollar sign from the example fingerprint in the
20853 man page, and also make the example fingerprint a valid one. Fixes
20854 bug 4309; bugfix on 0.2.1.3-alpha.
20855 - Fix internal bug-checking logic that was supposed to catch
20856 failures in digest generation so that it will fail more robustly
20857 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20858 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20859 - Report any failure in init_keys() calls launched because our
20860 IP address has changed. Spotted by Coverity Scan. Bugfix on
20861 0.1.1.4-alpha; fixes CID 484.
20863 o Minor bugfixes (on 0.2.3.x):
20864 - Fix a bug in configure.in that kept it from building a configure
20865 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20866 bugfix on 0.2.3.1-alpha.
20867 - Don't warn users that they are exposing a client port to the
20868 Internet if they have specified an RFC1918 address. Previously,
20869 we would warn if the user had specified any non-loopback
20870 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20871 - Fix memory leaks in the failing cases of the new SocksPort and
20872 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20873 fixes coverity CIDs 485, 486, and 487.
20876 - When a hidden service's introduction point times out, consider
20877 trying it again during the next attempt to connect to the
20878 HS. Previously, we would not try it again unless a newly fetched
20879 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20880 - The next version of Windows will be called Windows 8, and it has
20881 a major version of 6, minor version of 2. Correctly identify that
20882 version instead of calling it "Very recent version". Resolves
20883 ticket 4153; reported by funkstar.
20884 - The Bridge Authority now writes statistics on how many bridge
20885 descriptors it gave out in total, and how many unique descriptors
20886 it gave out. It also lists how often the most and least commonly
20887 fetched descriptors were given out, as well as the median and
20888 25th/75th percentile. Implements tickets 4200 and 4294.
20889 - Update to the October 4 2011 Maxmind GeoLite Country database.
20891 o Code simplifications and refactoring:
20892 - Remove some old code to remember statistics about which descriptors
20893 we've served as a directory mirror. The feature wasn't used and
20894 is outdated now that microdescriptors are around.
20895 - Rename Tor functions that turn strings into addresses, so that
20896 "parse" indicates that no hostname resolution occurs, and
20897 "lookup" indicates that hostname resolution may occur. This
20898 should help prevent mistakes in the future. Fixes bug 3512.
20901 Changes in version 0.2.2.34 - 2011-10-26
20902 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20903 can deanonymize Tor users. Everybody should upgrade.
20905 The attack relies on four components: 1) Clients reuse their TLS cert
20906 when talking to different relays, so relays can recognize a user by
20907 the identity key in her cert. 2) An attacker who knows the client's
20908 identity key can probe each guard relay to see if that identity key
20909 is connected to that guard relay right now. 3) A variety of active
20910 attacks in the literature (starting from "Low-Cost Traffic Analysis
20911 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20912 discover the guard relays that a Tor user visiting the website is using.
20913 4) Clients typically pick three guards at random, so the set of guards
20914 for a given user could well be a unique fingerprint for her. This
20915 release fixes components #1 and #2, which is enough to block the attack;
20916 the other two remain as open research problems. Special thanks to
20917 "frosty_un" for reporting the issue to us!
20919 Clients should upgrade so they are no longer recognizable by the TLS
20920 certs they present. Relays should upgrade so they no longer allow a
20921 remote attacker to probe them to test whether unpatched clients are
20922 currently connected to them.
20924 This release also fixes several vulnerabilities that allow an attacker
20925 to enumerate bridge relays. Some bridge enumeration attacks still
20926 remain; see for example proposal 188.
20928 o Privacy/anonymity fixes (clients):
20929 - Clients and bridges no longer send TLS certificate chains on
20930 outgoing OR connections. Previously, each client or bridge would
20931 use the same cert chain for all outgoing OR connections until
20932 its IP address changes, which allowed any relay that the client
20933 or bridge contacted to determine which entry guards it is using.
20934 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20935 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20936 no longer considers that connection as suitable for satisfying a
20937 circuit EXTEND request. Now relays can protect clients from the
20938 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20939 - Directory authorities no longer assign the Guard flag to relays
20940 that haven't upgraded to the above "refuse EXTEND requests
20941 to client connections" fix. Now directory authorities can
20942 protect clients from the CVE-2011-2768 issue even if neither
20943 the clients nor the relays have upgraded yet. There's a new
20944 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20945 to let us transition smoothly, else tomorrow there would be no
20948 o Privacy/anonymity fixes (bridge enumeration):
20949 - Bridge relays now do their directory fetches inside Tor TLS
20950 connections, like all the other clients do, rather than connecting
20951 directly to the DirPort like public relays do. Removes another
20952 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
20953 - Bridges relays now build circuits for themselves in a more similar
20954 way to how clients build them. Removes another avenue for
20955 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
20956 when bridges were introduced.
20957 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20958 that they initiated. Relays could distinguish incoming bridge
20959 connections from client connections, creating another avenue for
20960 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20961 Found by "frosty_un".
20964 - Fix a crash bug when changing node restrictions while a DNS lookup
20965 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20967 - Don't launch a useless circuit after failing to use one of a
20968 hidden service's introduction points. Previously, we would
20969 launch a new introduction circuit, but not set the hidden service
20970 which that circuit was intended to connect to, so it would never
20971 actually be used. A different piece of code would then create a
20972 new introduction circuit correctly. Bug reported by katmagic and
20973 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20976 - Change an integer overflow check in the OpenBSD_Malloc code so
20977 that GCC is less likely to eliminate it as impossible. Patch
20978 from Mansour Moufid. Fixes bug 4059.
20979 - When a hidden service turns an extra service-side introduction
20980 circuit into a general-purpose circuit, free the rend_data and
20981 intro_key fields first, so we won't leak memory if the circuit
20982 is cannibalized for use as another service-side introduction
20983 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20984 - Bridges now skip DNS self-tests, to act a little more stealthily.
20985 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20986 bridges. Patch by "warms0x".
20987 - Fix internal bug-checking logic that was supposed to catch
20988 failures in digest generation so that it will fail more robustly
20989 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20990 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20991 - Report any failure in init_keys() calls launched because our
20992 IP address has changed. Spotted by Coverity Scan. Bugfix on
20993 0.1.1.4-alpha; fixes CID 484.
20995 o Minor bugfixes (log messages and documentation):
20996 - Remove a confusing dollar sign from the example fingerprint in the
20997 man page, and also make the example fingerprint a valid one. Fixes
20998 bug 4309; bugfix on 0.2.1.3-alpha.
20999 - The next version of Windows will be called Windows 8, and it has
21000 a major version of 6, minor version of 2. Correctly identify that
21001 version instead of calling it "Very recent version". Resolves
21002 ticket 4153; reported by funkstar.
21003 - Downgrade log messages about circuit timeout calibration from
21004 "notice" to "info": they don't require or suggest any human
21005 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21006 bugfix on 0.2.2.14-alpha.
21009 - Turn on directory request statistics by default and include them in
21010 extra-info descriptors. Don't break if we have no GeoIP database.
21011 Backported from 0.2.3.1-alpha; implements ticket 3951.
21012 - Update to the October 4 2011 Maxmind GeoLite Country database.
21015 Changes in version 0.2.1.31 - 2011-10-26
21016 Tor 0.2.1.31 backports important security and privacy fixes for
21017 oldstable. This release is intended only for package maintainers and
21018 others who cannot use the 0.2.2 stable series. All others should be
21019 using Tor 0.2.2.x or newer.
21021 o Security fixes (also included in 0.2.2.x):
21022 - Replace all potentially sensitive memory comparison operations
21023 with versions whose runtime does not depend on the data being
21024 compared. This will help resist a class of attacks where an
21025 adversary can use variations in timing information to learn
21026 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21027 implementation by Robert Ransom based partially on code by DJB.)
21028 - Fix an assert in parsing router descriptors containing IPv6
21029 addresses. This one took down the directory authorities when
21030 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21032 o Privacy/anonymity fixes (also included in 0.2.2.x):
21033 - Clients and bridges no longer send TLS certificate chains on
21034 outgoing OR connections. Previously, each client or bridge would
21035 use the same cert chain for all outgoing OR connections until
21036 its IP address changes, which allowed any relay that the client
21037 or bridge contacted to determine which entry guards it is using.
21038 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
21039 - If a relay receives a CREATE_FAST cell on a TLS connection, it
21040 no longer considers that connection as suitable for satisfying a
21041 circuit EXTEND request. Now relays can protect clients from the
21042 CVE-2011-2768 issue even if the clients haven't upgraded yet.
21043 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
21044 that they initiated. Relays could distinguish incoming bridge
21045 connections from client connections, creating another avenue for
21046 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
21047 Found by "frosty_un".
21048 - When receiving a hidden service descriptor, check that it is for
21049 the hidden service we wanted. Previously, Tor would store any
21050 hidden service descriptors that a directory gave it, whether it
21051 wanted them or not. This wouldn't have let an attacker impersonate
21052 a hidden service, but it did let directories pre-seed a client
21053 with descriptors that it didn't want. Bugfix on 0.0.6.
21054 - Avoid linkability based on cached hidden service descriptors: forget
21055 all hidden service descriptors cached as a client when processing a
21056 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21057 - Make the bridge directory authority refuse to answer directory
21058 requests for "all" descriptors. It used to include bridge
21059 descriptors in its answer, which was a major information leak.
21060 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21061 - Don't attach new streams to old rendezvous circuits after SIGNAL
21062 NEWNYM. Previously, we would keep using an existing rendezvous
21063 circuit if it remained open (i.e. if it were kept open by a
21064 long-lived stream, or if a new stream were attached to it before
21065 Tor could notice that it was old and no longer in use). Bugfix on
21066 0.1.1.15-rc; fixes bug 3375.
21068 o Minor bugfixes (also included in 0.2.2.x):
21069 - When we restart our relay, we might get a successful connection
21070 from the outside before we've started our reachability tests,
21071 triggering a warning: "ORPort found reachable, but I have no
21072 routerinfo yet. Failing to inform controller of success." This
21073 bug was harmless unless Tor is running under a controller
21074 like Vidalia, in which case the controller would never get a
21075 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21077 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
21078 enabled. Fixes bug 1526.
21079 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21080 anything since 0.2.1.16-rc.
21081 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21082 None of the cases where we did this before were wrong, but by making
21083 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21084 - Fix a rare crash bug that could occur when a client was configured
21085 with a large number of bridges. Fixes bug 2629; bugfix on
21086 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21087 - Correct the warning displayed when a rendezvous descriptor exceeds
21088 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21090 - Fix an uncommon assertion failure when running with DNSPort under
21091 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21092 - When warning about missing zlib development packages during compile,
21093 give the correct package names. Bugfix on 0.2.0.1-alpha.
21094 - Require that introduction point keys and onion keys have public
21095 exponent 65537. Bugfix on 0.2.0.10-alpha.
21096 - Do not crash when our configuration file becomes unreadable, for
21097 example due to a permissions change, between when we start up
21098 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21100 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21102 - Always NUL-terminate the sun_path field of a sockaddr_un before
21103 passing it to the kernel. (Not a security issue: kernels are
21104 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21105 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21106 - Don't stack-allocate the list of supplementary GIDs when we're
21107 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21108 could take up to 256K, which is way too much stack. Found by
21109 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21111 o Minor bugfixes (only in 0.2.1.x):
21112 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
21113 rely on them. Bugfix on 0.2.1.30.
21114 - Use git revisions instead of svn revisions when generating our
21115 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21117 o Minor features (also included in 0.2.2.x):
21118 - Adjust the expiration time on our SSL session certificates to
21119 better match SSL certs seen in the wild. Resolves ticket 4014.
21120 - Allow nameservers with IPv6 address. Resolves bug 2574.
21121 - Update to the October 4 2011 Maxmind GeoLite Country database.
21124 Changes in version 0.2.3.5-alpha - 2011-09-28
21125 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
21126 bridge relays; fixes an assertion error that many users started hitting
21127 today; and adds the ability to refill token buckets more often than
21128 once per second, allowing significant performance improvements.
21131 - Bridge relays now do their directory fetches inside Tor TLS
21132 connections, like all the other clients do, rather than connecting
21133 directly to the DirPort like public relays do. Removes another
21134 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
21135 - Bridges relays now build circuits for themselves in a more similar
21136 way to how clients build them. Removes another avenue for
21137 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
21138 when bridges were introduced.
21141 - Fix an "Assertion md->held_by_node == 1 failed" error that could
21142 occur when the same microdescriptor was referenced by two node_t
21143 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
21145 o Major features (networking):
21146 - Add a new TokenBucketRefillInterval option to refill token buckets
21147 more frequently than once per second. This should improve network
21148 performance, alleviate queueing problems, and make traffic less
21149 bursty. Implements proposal 183; closes ticket 3630. Design by
21150 Florian Tschorsch and Björn Scheuermann; implementation by
21154 - Change an integer overflow check in the OpenBSD_Malloc code so
21155 that GCC is less likely to eliminate it as impossible. Patch
21156 from Mansour Moufid. Fixes bug 4059.
21158 o Minor bugfixes (usability):
21159 - Downgrade log messages about circuit timeout calibration from
21160 "notice" to "info": they don't require or suggest any human
21161 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21162 bugfix on 0.2.2.14-alpha.
21164 o Minor features (diagnostics):
21165 - When the system call to create a listener socket fails, log the
21166 error message explaining why. This may help diagnose bug 4027.
21169 Changes in version 0.2.3.4-alpha - 2011-09-13
21170 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
21171 tweak to Tor's TLS handshake that makes relays and bridges that run
21172 this new version reachable from Iran again. It also fixes a few new
21173 bugs in 0.2.3.x, and teaches relays to recognize when they're not
21174 listed in the network consensus and republish.
21176 o Major bugfixes (also part of 0.2.2.33):
21177 - Avoid an assertion failure when reloading a configuration with
21178 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21179 3923; bugfix on 0.2.2.25-alpha.
21181 o Minor features (security, also part of 0.2.2.33):
21182 - Check for replays of the public-key encrypted portion of an
21183 INTRODUCE1 cell, in addition to the current check for replays of
21184 the g^x value. This prevents a possible class of active attacks
21185 by an attacker who controls both an introduction point and a
21186 rendezvous point, and who uses the malleability of AES-CTR to
21187 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21188 that these attacks are infeasible (requiring the attacker to send
21189 on the order of zettabytes of altered cells in a short interval),
21190 but we'd rather block them off in case there are any classes of
21191 this attack that we missed. Reported by Willem Pinckaers.
21193 o Minor features (also part of 0.2.2.33):
21194 - Adjust the expiration time on our SSL session certificates to
21195 better match SSL certs seen in the wild. Resolves ticket 4014.
21196 - Change the default required uptime for a relay to be accepted as
21197 a HSDir (hidden service directory) from 24 hours to 25 hours.
21198 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21199 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21200 authorities to abstain from voting on assignment of the HSDir
21201 consensus flag. Related to bug 2649.
21202 - Update to the September 6 2011 Maxmind GeoLite Country database.
21204 o Minor bugfixes (also part of 0.2.2.33):
21205 - Demote the 'replay detected' log message emitted when a hidden
21206 service receives the same Diffie-Hellman public key in two different
21207 INTRODUCE2 cells to info level. A normal Tor client can cause that
21208 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21209 fixes part of bug 2442.
21210 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21211 level. There is nothing that a hidden service's operator can do
21212 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21214 - Clarify a log message specifying the characters permitted in
21215 HiddenServiceAuthorizeClient client names. Previously, the log
21216 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21217 given the impression that every ASCII character between "+" and "_"
21218 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21220 o Build fixes (also part of 0.2.2.33):
21221 - Clean up some code issues that prevented Tor from building on older
21222 BSDs. Fixes bug 3894; reported by "grarpamp".
21223 - Search for a platform-specific version of "ar" when cross-compiling.
21224 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21227 - Fix a bug where the SocksPort option (for example) would get
21228 ignored and replaced by the default if a SocksListenAddress
21229 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
21233 - Relays now try regenerating and uploading their descriptor more
21234 frequently if they are not listed in the consensus, or if the
21235 version of their descriptor listed in the consensus is too
21236 old. This fix should prevent situations where a server declines
21237 to re-publish itself because it has done so too recently, even
21238 though the authorities decided not to list its recent-enough
21239 descriptor. Fix for bug 3327.
21242 - Relays now include a reason for regenerating their descriptors
21243 in an HTTP header when uploading to the authorities. This will
21244 make it easier to debug descriptor-upload issues in the future.
21245 - When starting as root and then changing our UID via the User
21246 control option, and we have a ControlSocket configured, make sure
21247 that the ControlSocket is owned by the same account that Tor will
21248 run under. Implements ticket 3421; fix by Jérémy Bobbio.
21251 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
21252 utility function used in the control-port code). This shouldn't
21253 ever happen unless Tor is completely out of memory, but if it did
21254 happen and Tor somehow recovered from it, Tor could have sent a log
21255 message to a control port in the middle of a reply to a controller
21256 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
21257 - Make 'FetchUselessDescriptors' cause all descriptor types and
21258 all consensus types (including microdescriptors) to get fetched.
21259 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
21261 o Code refactoring:
21262 - Make a new "entry connection" struct as an internal subtype of "edge
21263 connection", to simplify the code and make exit connections smaller.
21266 Changes in version 0.2.2.33 - 2011-09-13
21267 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21268 TLS handshake that makes relays and bridges that run this new version
21269 reachable from Iran again.
21272 - Avoid an assertion failure when reloading a configuration with
21273 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21274 3923; bugfix on 0.2.2.25-alpha.
21276 o Minor features (security):
21277 - Check for replays of the public-key encrypted portion of an
21278 INTRODUCE1 cell, in addition to the current check for replays of
21279 the g^x value. This prevents a possible class of active attacks
21280 by an attacker who controls both an introduction point and a
21281 rendezvous point, and who uses the malleability of AES-CTR to
21282 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21283 that these attacks are infeasible (requiring the attacker to send
21284 on the order of zettabytes of altered cells in a short interval),
21285 but we'd rather block them off in case there are any classes of
21286 this attack that we missed. Reported by Willem Pinckaers.
21289 - Adjust the expiration time on our SSL session certificates to
21290 better match SSL certs seen in the wild. Resolves ticket 4014.
21291 - Change the default required uptime for a relay to be accepted as
21292 a HSDir (hidden service directory) from 24 hours to 25 hours.
21293 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21294 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21295 authorities to abstain from voting on assignment of the HSDir
21296 consensus flag. Related to bug 2649.
21297 - Update to the September 6 2011 Maxmind GeoLite Country database.
21299 o Minor bugfixes (documentation and log messages):
21300 - Correct the man page to explain that HashedControlPassword and
21301 CookieAuthentication can both be set, in which case either method
21302 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21303 when we decided to allow these config options to both be set. Issue
21304 raised by bug 3898.
21305 - Demote the 'replay detected' log message emitted when a hidden
21306 service receives the same Diffie-Hellman public key in two different
21307 INTRODUCE2 cells to info level. A normal Tor client can cause that
21308 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21309 fixes part of bug 2442.
21310 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21311 level. There is nothing that a hidden service's operator can do
21312 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21314 - Clarify a log message specifying the characters permitted in
21315 HiddenServiceAuthorizeClient client names. Previously, the log
21316 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21317 given the impression that every ASCII character between "+" and "_"
21318 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21321 - Provide a substitute implementation of lround() for MSVC, which
21322 apparently lacks it. Patch from Gisle Vanem.
21323 - Clean up some code issues that prevented Tor from building on older
21324 BSDs. Fixes bug 3894; reported by "grarpamp".
21325 - Search for a platform-specific version of "ar" when cross-compiling.
21326 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21329 Changes in version 0.2.3.3-alpha - 2011-09-01
21330 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
21331 security, and provides client-side support for the microdescriptor
21332 and optimistic data features introduced earlier in the 0.2.3.x
21333 series. It also includes numerous critical bugfixes in the (optional)
21334 bufferevent-based networking backend.
21336 o Major features (stream isolation):
21337 - You can now configure Tor so that streams from different
21338 applications are isolated on different circuits, to prevent an
21339 attacker who sees your streams as they leave an exit node from
21340 linking your sessions to one another. To do this, choose some way
21341 to distinguish the applications: have them connect to different
21342 SocksPorts, or have one of them use SOCKS4 while the other uses
21343 SOCKS5, or have them pass different authentication strings to the
21344 SOCKS proxy. Then, use the new SocksPort syntax to configure the
21345 degree of isolation you need. This implements Proposal 171.
21346 - There's a new syntax for specifying multiple client ports (such as
21347 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
21348 multiple *Port entries with full addr:port syntax on each.
21349 The old *ListenAddress format is still supported, but you can't
21350 mix it with the new *Port syntax.
21352 o Major features (other):
21353 - Enable microdescriptor fetching by default for clients. This allows
21354 clients to download a much smaller amount of directory information.
21355 To disable it (and go back to the old-style consensus and
21356 descriptors), set "UseMicrodescriptors 0" in your torrc file.
21357 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
21358 "PortForwarding" config option), now supports Windows.
21359 - When using an exit relay running 0.2.3.x, clients can now
21360 "optimistically" send data before the exit relay reports that
21361 the stream has opened. This saves a round trip when starting
21362 connections where the client speaks first (such as web browsing).
21363 This behavior is controlled by a consensus parameter (currently
21364 disabled). To turn it on or off manually, use the "OptimisticData"
21365 torrc option. Implements proposal 181; code by Ian Goldberg.
21367 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
21368 - When using IOCP on Windows, we need to enable Libevent windows
21370 - The IOCP backend now works even when the user has not specified
21371 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
21372 Fixes part of bug 3752.
21373 - Correctly record the bytes we've read and written when using
21374 bufferevents, so that we can include them in our bandwidth history
21375 and advertised bandwidth. Fixes bug 3803.
21376 - Apply rate-limiting only at the bottom of a chain of filtering
21377 bufferevents. This prevents us from filling up internal read
21378 buffers and violating rate-limits when filtering bufferevents
21379 are enabled. Fixes part of bug 3804.
21380 - Add high-watermarks to the output buffers for filtered
21381 bufferevents. This prevents us from filling up internal write
21382 buffers and wasting CPU cycles when filtering bufferevents are
21383 enabled. Fixes part of bug 3804.
21384 - Correctly notice when data has been written from a bufferevent
21385 without flushing it completely. Fixes bug 3805.
21386 - Fix a bug where server-side tunneled bufferevent-based directory
21387 streams would get closed prematurely. Fixes bug 3814.
21388 - Fix a use-after-free error with per-connection rate-limiting
21389 buckets. Fixes bug 3888.
21391 o Major bugfixes (also part of 0.2.2.31-rc):
21392 - If we're configured to write our ControlPorts to disk, only write
21393 them after switching UID and creating the data directory. This way,
21394 we don't fail when starting up with a nonexistent DataDirectory
21395 and a ControlPortWriteToFile setting based on that directory. Fixes
21396 bug 3747; bugfix on Tor 0.2.2.26-beta.
21399 - Added a new CONF_CHANGED event so that controllers can be notified
21400 of any configuration changes made by other controllers, or by the
21401 user. Implements ticket 1692.
21402 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
21403 leak when using bufferevents, and lets Libevent worry about how to
21404 best copy data out of a buffer.
21405 - Replace files in stats/ rather than appending to them. Now that we
21406 include statistics in extra-info descriptors, it makes no sense to
21407 keep old statistics forever. Implements ticket 2930.
21409 o Minor features (build compatibility):
21410 - Limited, experimental support for building with nmake and MSVC.
21411 - Provide a substitute implementation of lround() for MSVC, which
21412 apparently lacks it. Patch from Gisle Vanem.
21414 o Minor features (also part of 0.2.2.31-rc):
21415 - Update to the August 2 2011 Maxmind GeoLite Country database.
21417 o Minor bugfixes (on 0.2.3.x-alpha):
21418 - Fix a spurious warning when parsing SOCKS requests with
21419 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
21420 - Get rid of a harmless warning that could happen on relays running
21421 with bufferevents. The warning was caused by someone doing an http
21422 request to a relay's orport. Also don't warn for a few related
21423 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
21425 o Minor bugfixes (on 2.2.x and earlier):
21426 - Correct the man page to explain that HashedControlPassword and
21427 CookieAuthentication can both be set, in which case either method
21428 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21429 when we decided to allow these config options to both be set. Issue
21430 raised by bug 3898.
21431 - The "--quiet" and "--hush" options now apply not only to Tor's
21432 behavior before logs are configured, but also to Tor's behavior in
21433 the absence of configured logs. Fixes bug 3550; bugfix on
21436 o Minor bugfixes (also part of 0.2.2.31-rc):
21437 - Write several files in text mode, on OSes that distinguish text
21438 mode from binary mode (namely, Windows). These files are:
21439 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21440 that collect those statistics; 'client_keys' and 'hostname' for
21441 hidden services that use authentication; and (in the tor-gencert
21442 utility) newly generated identity and signing keys. Previously,
21443 we wouldn't specify text mode or binary mode, leading to an
21444 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21445 the DirRecordUsageByCountry option which would have triggered
21446 the assertion failure was added), although this assertion failure
21447 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21448 - Selectively disable deprecation warnings on OS X because Lion
21449 started deprecating the shipped copy of openssl. Fixes bug 3643.
21450 - Remove an extra pair of quotation marks around the error
21451 message in control-port STATUS_GENERAL BUG events. Bugfix on
21452 0.1.2.6-alpha; fixes bug 3732.
21453 - When unable to format an address as a string, report its value
21454 as "???" rather than reusing the last formatted address. Bugfix
21457 o Code simplifications and refactoring:
21458 - Rewrite the listener-selection logic so that parsing which ports
21459 we want to listen on is now separate from binding to the ports
21463 - Building Tor with bufferevent support now requires Libevent
21464 2.0.13-stable or later. Previous versions of Libevent had bugs in
21465 SSL-related bufferevents and related issues that would make Tor
21466 work badly with bufferevents. Requiring 2.0.13-stable also allows
21467 Tor with bufferevents to take advantage of Libevent APIs
21468 introduced after 2.0.8-rc.
21471 Changes in version 0.2.2.32 - 2011-08-27
21472 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21473 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21474 a founder of the PETS community, a leader in our field, a mentor,
21475 and a friend. He left us with these words: "I had the possibility
21476 to contribute to this world that is not as it should be. I hope I
21477 could help in some areas to make the world a better place, and that
21478 I could also encourage other people to be engaged in improving the
21479 world. Please, stay engaged. This world needs you, your love, your
21480 initiative -- now I cannot be part of that anymore."
21482 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21483 ready. More than two years in the making, this release features improved
21484 client performance and hidden service reliability, better compatibility
21485 for Android, correct behavior for bridges that listen on more than
21486 one address, more extensible and flexible directory object handling,
21487 better reporting of network statistics, improved code security, and
21488 many many other features and bugfixes.
21491 Changes in version 0.2.2.31-rc - 2011-08-17
21492 Tor 0.2.2.31-rc is the second and hopefully final release candidate
21493 for the Tor 0.2.2.x series.
21496 - Remove an extra pair of quotation marks around the error
21497 message in control-port STATUS_GENERAL BUG events. Bugfix on
21498 0.1.2.6-alpha; fixes bug 3732.
21499 - If we're configured to write our ControlPorts to disk, only write
21500 them after switching UID and creating the data directory. This way,
21501 we don't fail when starting up with a nonexistent DataDirectory
21502 and a ControlPortWriteToFile setting based on that directory. Fixes
21503 bug 3747; bugfix on Tor 0.2.2.26-beta.
21506 - Update to the August 2 2011 Maxmind GeoLite Country database.
21509 - Allow GETINFO fingerprint to return a fingerprint even when
21510 we have not yet built a router descriptor. Fixes bug 3577;
21511 bugfix on 0.2.0.1-alpha.
21512 - Write several files in text mode, on OSes that distinguish text
21513 mode from binary mode (namely, Windows). These files are:
21514 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21515 that collect those statistics; 'client_keys' and 'hostname' for
21516 hidden services that use authentication; and (in the tor-gencert
21517 utility) newly generated identity and signing keys. Previously,
21518 we wouldn't specify text mode or binary mode, leading to an
21519 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21520 the DirRecordUsageByCountry option which would have triggered
21521 the assertion failure was added), although this assertion failure
21522 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21523 - Selectively disable deprecation warnings on OS X because Lion
21524 started deprecating the shipped copy of openssl. Fixes bug 3643.
21525 - When unable to format an address as a string, report its value
21526 as "???" rather than reusing the last formatted address. Bugfix
21530 Changes in version 0.2.3.2-alpha - 2011-07-18
21531 Tor 0.2.3.2-alpha introduces two new experimental features:
21532 microdescriptors and pluggable transports. It also continues cleaning
21533 up a variety of recently introduced features.
21536 - Clients can now use microdescriptors instead of regular descriptors
21537 to build circuits. Microdescriptors are authority-generated
21538 summaries of regular descriptors' contents, designed to change
21539 very rarely (see proposal 158 for details). This feature is
21540 designed to save bandwidth, especially for clients on slow internet
21541 connections. It's off by default for now, since nearly no caches
21542 support it, but it will be on-by-default for clients in a future
21543 version. You can use the UseMicrodescriptors option to turn it on.
21544 - Tor clients using bridges can now be configured to use a separate
21545 'transport' proxy for each bridge. This approach helps to resist
21546 censorship by allowing bridges to use protocol obfuscation
21547 plugins. It implements part of proposal 180. Implements ticket 2841.
21548 - While we're trying to bootstrap, record how many TLS connections
21549 fail in each state, and report which states saw the most failures
21550 in response to any bootstrap failures. This feature may speed up
21551 diagnosis of censorship events. Implements ticket 3116.
21553 o Major bugfixes (on 0.2.3.1-alpha):
21554 - When configuring a large set of nodes in EntryNodes (as with
21555 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
21556 random subset to be guards, and choose them in random
21557 order. Fixes bug 2798.
21558 - Tor could crash when remembering a consensus in a non-used consensus
21559 flavor without having a current consensus set. Fixes bug 3361.
21560 - Comparing an unknown address to a microdescriptor's shortened exit
21561 policy would always give a "rejected" result. Fixes bug 3599.
21562 - Using microdescriptors as a client no longer prevents Tor from
21563 uploading and downloading hidden service descriptors. Fixes
21567 - Allow nameservers with IPv6 address. Resolves bug 2574.
21568 - Accept attempts to include a password authenticator in the
21569 handshake, as supported by SOCKS5. This handles SOCKS clients that
21570 don't know how to omit a password when authenticating. Resolves
21572 - When configuring a large set of nodes in EntryNodes, and there are
21573 enough of them listed as Guard so that we don't need to consider
21574 the non-guard entries, prefer the ones listed with the Guard flag.
21575 - Check for and recover from inconsistency in the microdescriptor
21576 cache. This will make it harder for us to accidentally free a
21577 microdescriptor without removing it from the appropriate data
21578 structures. Fixes issue 3135; issue noted by "wanoskarnet".
21579 - Log SSL state transitions at log level DEBUG, log domain
21580 HANDSHAKE. This can be useful for debugging censorship events.
21581 Implements ticket 3264.
21582 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
21583 implements ticket 3439.
21585 o Minor bugfixes (on 0.2.3.1-alpha):
21586 - Do not free all general-purpose regular descriptors just
21587 because microdescriptor use is enabled. Fixes bug 3113.
21588 - Correctly link libevent_openssl when --enable-static-libevent
21589 is passed to configure. Fixes bug 3118.
21590 - Bridges should not complain during their heartbeat log messages that
21591 they are unlisted in the consensus: that's more or less the point
21592 of being a bridge. Fixes bug 3183.
21593 - Report a SIGNAL event to controllers when acting on a delayed
21594 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
21595 event to the controller if we acted on a SIGNAL NEWNYM command
21596 immediately, and otherwise not report a SIGNAL event for the
21597 command at all. Fixes bug 3349.
21598 - Fix a crash when handling the SIGNAL controller command or
21599 reporting ERR-level status events with bufferevents enabled. Found
21600 by Robert Ransom. Fixes bug 3367.
21601 - Always ship the tor-fw-helper manpage in our release tarballs.
21602 Fixes bug 3389. Reported by Stephen Walker.
21603 - Fix a class of double-mark-for-close bugs when bufferevents
21604 are enabled. Fixes bug 3403.
21605 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
21606 - Add SIGNAL to the list returned by the 'GETINFO events/names'
21607 control-port command. Fixes part of bug 3465.
21608 - Prevent using negative indices during unit test runs when read_all()
21609 fails. Spotted by coverity.
21610 - Fix a rare memory leak when checking the nodelist without it being
21611 present. Found by coverity.
21612 - Only try to download a microdescriptor-flavored consensus from
21613 a directory cache that provides them.
21615 o Minor bugfixes (on 0.2.2.x and earlier):
21616 - Assert that hidden-service-related operations are not performed
21617 using single-hop circuits. Previously, Tor would assert that
21618 client-side streams are not attached to single-hop circuits,
21619 but not that other sensitive operations on the client and service
21620 side are not performed using single-hop circuits. Fixes bug 3332;
21622 - Don't publish a new relay descriptor when we reload our onion key,
21623 unless the onion key has actually changed. Fixes bug 3263 and
21624 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
21625 - Allow GETINFO fingerprint to return a fingerprint even when
21626 we have not yet built a router descriptor. Fixes bug 3577;
21627 bugfix on 0.2.0.1-alpha.
21628 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
21629 on 0.2.2.4-alpha; fixes bug 3427.
21631 o Code simplification and refactoring:
21632 - Use tor_sscanf() in place of scanf() in more places through the
21633 code. This makes us a little more locale-independent, and
21634 should help shut up code-analysis tools that can't tell
21635 a safe sscanf string from a dangerous one.
21636 - Use tt_assert(), not tor_assert(), for checking for test failures.
21637 This makes the unit tests more able to go on in the event that
21639 - Split connection_about_to_close() into separate functions for each
21643 - On Windows, we now define the _WIN32_WINNT macros only if they
21644 are not already defined. This lets the person building Tor decide,
21645 if they want, to require a later version of Windows.
21648 Changes in version 0.2.2.30-rc - 2011-07-07
21649 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
21650 series. It fixes a few smaller bugs, but generally appears stable.
21651 Please test it and let us know whether it is!
21654 - Send a SUCCEEDED stream event to the controller when a reverse
21655 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21656 discovered by katmagic.
21657 - Always NUL-terminate the sun_path field of a sockaddr_un before
21658 passing it to the kernel. (Not a security issue: kernels are
21659 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21660 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21661 - Don't stack-allocate the list of supplementary GIDs when we're
21662 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21663 could take up to 256K, which is way too much stack. Found by
21664 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21665 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
21666 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
21667 fixes part of bug 3465.
21668 - Fix a memory leak when receiving a descriptor for a hidden
21669 service we didn't ask for. Found by Coverity; CID #30. Bugfix
21673 - Update to the July 1 2011 Maxmind GeoLite Country database.
21676 Changes in version 0.2.2.29-beta - 2011-06-20
21677 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
21678 have bridge lines in their torrc but don't want to use them; gets
21679 us closer to having the control socket feature working on Debian;
21680 and fixes a variety of smaller bugs.
21683 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
21684 When we changed the default behavior to "use bridges if any
21685 are listed in the torrc", we surprised users who had bridges
21686 in their torrc files but who didn't actually want to use them.
21687 Partial resolution for bug 3354.
21690 - Don't attach new streams to old rendezvous circuits after SIGNAL
21691 NEWNYM. Previously, we would keep using an existing rendezvous
21692 circuit if it remained open (i.e. if it were kept open by a
21693 long-lived stream, or if a new stream were attached to it before
21694 Tor could notice that it was old and no longer in use). Bugfix on
21695 0.1.1.15-rc; fixes bug 3375.
21698 - Fix a bug when using ControlSocketsGroupWritable with User. The
21699 directory's group would be checked against the current group, not
21700 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
21701 bugfix on 0.2.2.26-beta.
21702 - Make connection_printf_to_buf()'s behavior sane. Its callers
21703 expect it to emit a CRLF iff the format string ends with CRLF;
21704 it actually emitted a CRLF iff (a) the format string ended with
21705 CRLF or (b) the resulting string was over 1023 characters long or
21706 (c) the format string did not end with CRLF *and* the resulting
21707 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21708 fixes part of bug 3407.
21709 - Make send_control_event_impl()'s behavior sane. Its callers
21710 expect it to always emit a CRLF at the end of the string; it
21711 might have emitted extra control characters as well. Bugfix on
21712 0.1.1.9-alpha; fixes another part of bug 3407.
21713 - Make crypto_rand_int() check the value of its input correctly.
21714 Previously, it accepted values up to UINT_MAX, but could return a
21715 negative number if given a value above INT_MAX+1. Found by George
21716 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21717 - Avoid a segfault when reading a malformed circuit build state
21718 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21720 - When asked about a DNS record type we don't support via a
21721 client DNSPort, reply with NOTIMPL rather than an empty
21722 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21723 - Fix a rare memory leak during stats writing. Found by coverity.
21726 - Update to the June 1 2011 Maxmind GeoLite Country database.
21728 o Code simplifications and refactoring:
21729 - Remove some dead code as indicated by coverity.
21730 - Remove a few dead assignments during router parsing. Found by
21732 - Add some forgotten return value checks during unit tests. Found
21734 - Don't use 1-bit wide signed bit fields. Found by coverity.
21737 Changes in version 0.2.2.28-beta - 2011-06-04
21738 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21739 fixed a big bug in whether relays stay in the consensus consistently,
21740 we moved closer to handling bridges and hidden services correctly,
21741 and we started the process of better handling the dreaded "my Vidalia
21742 died, and now my Tor demands a password when I try to reconnect to it"
21746 - Don't decide to make a new descriptor when receiving a HUP signal.
21747 This bug has caused a lot of 0.2.2.x relays to disappear from the
21748 consensus periodically. Fixes the most common case of triggering
21749 bug 1810; bugfix on 0.2.2.7-alpha.
21750 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21751 - Don't try to build descriptors if "ORPort auto" is set and we
21752 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21754 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21755 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21756 - Apply circuit timeouts to opened hidden-service-related circuits
21757 based on the correct start time. Previously, we would apply the
21758 circuit build timeout based on time since the circuit's creation;
21759 it was supposed to be applied based on time since the circuit
21760 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21761 - Use the same circuit timeout for client-side introduction
21762 circuits as for other four-hop circuits, rather than the timeout
21763 for single-hop directory-fetch circuits; the shorter timeout may
21764 have been appropriate with the static circuit build timeout in
21765 0.2.1.x and earlier, but caused many hidden service access attempts
21766 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21767 on 0.2.2.2-alpha; fixes another part of bug 1297.
21768 - In ticket 2511 we fixed a case where you could use an unconfigured
21769 bridge if you had configured it as a bridge the last time you ran
21770 Tor. Now fix another edge case: if you had configured it as a bridge
21771 but then switched to a different bridge via the controller, you
21772 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21776 - Add an __OwningControllerProcess configuration option and a
21777 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21778 that when it exits, Tor will shut down. Implements feature 3049.
21779 - If "UseBridges 1" is set and no bridges are configured, Tor will
21780 now refuse to build any circuits until some bridges are set.
21781 If "UseBridges auto" is set, Tor will use bridges if they are
21782 configured and we are not running as a server, but otherwise will
21783 make circuits as usual. The new default is "auto". Patch by anonym,
21784 so the Tails LiveCD can stop automatically revealing you as a Tor
21788 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21789 - Remove a trailing asterisk from "exit-policy/default" in the
21790 output of the control port command "GETINFO info/names". Bugfix
21792 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21794 - Warn when the user configures two HiddenServiceDir lines that point
21795 to the same directory. Bugfix on 0.0.6 (the version introducing
21796 HiddenServiceDir); fixes bug 3289.
21797 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21798 part of bug 2748; bugfix on 0.2.0.10-alpha.
21799 - Log malformed requests for rendezvous descriptors as protocol
21800 warnings, not warnings. Also, use a more informative log message
21801 in case someone sees it at log level warning without prior
21802 info-level messages. Fixes the other part of bug 2748; bugfix
21804 - Clear the table recording the time of the last request for each
21805 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21806 Previously, we would clear our HS descriptor cache on SIGNAL
21807 NEWNYM, but if we had previously retrieved a descriptor (or tried
21808 to) from every directory responsible for it, we would refuse to
21809 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21811 - Fix a log message that said "bits" while displaying a value in
21812 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21814 - When checking for 1024-bit keys, check for 1024 bits, not 128
21815 bytes. This allows Tor to correctly discard keys of length 1017
21816 through 1023. Bugfix on 0.0.9pre5.
21819 - Relays now log the reason for publishing a new relay descriptor,
21820 so we have a better chance of hunting down instances of bug 1810.
21821 Resolves ticket 3252.
21822 - Revise most log messages that refer to nodes by nickname to
21823 instead use the "$key=nickname at address" format. This should be
21824 more useful, especially since nicknames are less and less likely
21825 to be unique. Resolves ticket 3045.
21826 - Log (at info level) when purging pieces of hidden-service-client
21827 state because of SIGNAL NEWNYM.
21830 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21831 anything since 0.2.1.16-rc.
21834 Changes in version 0.2.2.27-beta - 2011-05-18
21835 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21836 release, and also adds a few more general bugfixes.
21839 - Fix a crash bug when changing bridges in a running Tor process.
21840 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21841 - When the controller configures a new bridge, don't wait 10 to 60
21842 seconds before trying to fetch its descriptor. Bugfix on
21843 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21846 - Require that onion keys have exponent 65537 in microdescriptors too.
21847 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21848 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21849 Changed the limit to 512 characters by removing base64 newlines.
21850 Fixes bug 2752. Fix by Michael Yakubovich.
21851 - When a client starts or stops using bridges, never use a circuit
21852 that was built before the configuration change. This behavior could
21853 put at risk a user who uses bridges to ensure that her traffic
21854 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21858 Changes in version 0.2.2.26-beta - 2011-05-17
21859 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21860 also introduces a new "socksport auto" approach that should make it
21861 easier to run multiple Tors on the same system, and does a lot of
21862 cleanup to get us closer to a release candidate.
21864 o Security/privacy fixes:
21865 - Replace all potentially sensitive memory comparison operations
21866 with versions whose runtime does not depend on the data being
21867 compared. This will help resist a class of attacks where an
21868 adversary can use variations in timing information to learn
21869 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21870 implementation by Robert Ransom based partially on code by DJB.)
21871 - When receiving a hidden service descriptor, check that it is for
21872 the hidden service we wanted. Previously, Tor would store any
21873 hidden service descriptors that a directory gave it, whether it
21874 wanted them or not. This wouldn't have let an attacker impersonate
21875 a hidden service, but it did let directories pre-seed a client
21876 with descriptors that it didn't want. Bugfix on 0.0.6.
21877 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21878 DNS cache entries, and virtual address mappings: that's what
21879 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21882 - The options SocksPort, ControlPort, and so on now all accept a
21883 value "auto" that opens a socket on an OS-selected port. A
21884 new ControlPortWriteToFile option tells Tor to write its
21885 actual control port or ports to a chosen file. If the option
21886 ControlPortFileGroupReadable is set, the file is created as
21887 group-readable. Now users can run two Tor clients on the same
21888 system without needing to manually mess with parameters. Resolves
21889 part of ticket 3076.
21890 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21891 help busy exit nodes avoid running out of useable ports just
21892 because all the ports have been used in the near past. Resolves
21896 - New "GETINFO net/listeners/(type)" controller command to return
21897 a list of addresses and ports that are bound for listeners for a
21898 given connection type. This is useful when the user has configured
21899 "SocksPort auto" and the controller needs to know which port got
21900 chosen. Resolves another part of ticket 3076.
21901 - Add a new ControlSocketsGroupWritable configuration option: when
21902 it is turned on, ControlSockets are group-writeable by the default
21903 group of the current user. Patch by Jérémy Bobbio; implements
21905 - Tor now refuses to create a ControlSocket in a directory that is
21906 world-readable (or group-readable if ControlSocketsGroupWritable
21907 is 0). This is necessary because some operating systems do not
21908 enforce permissions on an AF_UNIX sockets. Permissions on the
21909 directory holding the socket, however, seems to work everywhere.
21910 - Rate-limit a warning about failures to download v2 networkstatus
21911 documents. Resolves part of bug 1352.
21912 - Backport code from 0.2.3.x that allows directory authorities to
21913 clean their microdescriptor caches. Needed to resolve bug 2230.
21914 - When an HTTPS proxy reports "403 Forbidden", we now explain
21915 what it means rather than calling it an unexpected status code.
21916 Closes bug 2503. Patch from Michael Yakubovich.
21917 - Update to the May 1 2011 Maxmind GeoLite Country database.
21920 - Authorities now clean their microdesc cache periodically and when
21921 reading from disk initially, not only when adding new descriptors.
21922 This prevents a bug where we could lose microdescriptors. Bugfix
21923 on 0.2.2.6-alpha. Fixes bug 2230.
21924 - Do not crash when our configuration file becomes unreadable, for
21925 example due to a permissions change, between when we start up
21926 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21928 - Avoid a bug that would keep us from replacing a microdescriptor
21929 cache on Windows. (We would try to replace the file while still
21930 holding it open. That's fine on Unix, but Windows doesn't let us
21931 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
21932 - Add missing explanations for the authority-related torrc options
21933 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
21934 man page. Resolves issue 2379.
21935 - As an authority, do not upload our own vote or signature set to
21936 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
21937 it would get flagged as a duplicate. Resolves bug 3026.
21938 - Accept hidden service descriptors if we think we might be a hidden
21939 service directory, regardless of what our consensus says. This
21940 helps robustness, since clients and hidden services can sometimes
21941 have a more up-to-date view of the network consensus than we do,
21942 and if they think that the directory authorities list us a HSDir,
21943 we might actually be one. Related to bug 2732; bugfix on
21945 - When a controller changes TrackHostExits, remove mappings for
21946 hosts that should no longer have their exits tracked. Bugfix on
21948 - When a controller changes VirtualAddrNetwork, remove any mappings
21949 for hosts that were automapped to the old network. Bugfix on
21951 - When a controller changes one of the AutomapHosts* options, remove
21952 any mappings for hosts that should no longer be automapped. Bugfix
21954 - Do not reset the bridge descriptor download status every time we
21955 re-parse our configuration or get a configuration change. Fixes
21956 bug 3019; bugfix on 0.2.0.3-alpha.
21958 o Minor bugfixes (code cleanup):
21959 - When loading the microdesc journal, remember its current size.
21960 In 0.2.2, this helps prevent the microdesc journal from growing
21961 without limit on authorities (who are the only ones to use it in
21962 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
21963 Fix posted by "cypherpunks."
21964 - The microdesc journal is supposed to get rebuilt only if it is
21965 at least _half_ the length of the store, not _twice_ the length
21966 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
21967 - Fix a potential null-pointer dereference while computing a
21968 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
21970 - Avoid a possible null-pointer dereference when rebuilding the mdesc
21971 cache without actually having any descriptors to cache. Bugfix on
21972 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
21973 - If we fail to compute the identity digest of a v3 legacy keypair,
21974 warn, and don't use a buffer-full of junk instead. Bugfix on
21975 0.2.1.1-alpha; fixes bug 3106.
21976 - Resolve an untriggerable issue in smartlist_string_num_isin(),
21977 where if the function had ever in the future been used to check
21978 for the presence of a too-large number, it would have given an
21979 incorrect result. (Fortunately, we only used it for 16-bit
21980 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
21981 - Require that introduction point keys and onion handshake keys
21982 have a public exponent of 65537. Starts to fix bug 3207; bugfix
21985 o Removed features:
21986 - Caches no longer download and serve v2 networkstatus documents
21987 unless FetchV2Networkstatus flag is set: these documents haven't
21988 haven't been used by clients or relays since 0.2.0.x. Resolves
21992 Changes in version 0.2.3.1-alpha - 2011-05-05
21993 Tor 0.2.3.1-alpha adds some new experimental features, including support
21994 for an improved network IO backend, IOCP networking on Windows,
21995 microdescriptor caching, "fast-start" support for streams, and automatic
21996 home router configuration. There are also numerous internal improvements
21997 to try to make the code easier for developers to work with.
21999 This is the first alpha release in a new series, so expect there to be
22000 bugs. Users who would rather test out a more stable branch should
22001 stay with 0.2.2.x for now.
22004 - Tor can now optionally build with the "bufferevents" buffered IO
22005 backend provided by Libevent 2. To use this feature, make sure you
22006 have the latest possible version of Libevent, and pass the
22007 --enable-bufferevents flag to configure when building Tor from
22008 source. This feature will make our networking code more flexible,
22009 let us stack layers on each other, and let us use more efficient
22010 zero-copy transports where available.
22011 - As an experimental feature, Tor can use IOCP for networking on Windows.
22012 Once this code is tuned and optimized, it promises much better
22013 performance than the select-based backend we've used in the past. To
22014 try this feature, you must build Tor with Libevent 2, configure Tor
22015 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
22016 your torrc. There are known bugs here: only try this if you can help
22017 debug it as it breaks.
22018 - The EntryNodes option can now include country codes like {de} or IP
22019 addresses or network masks. Previously we had disallowed these options
22020 because we didn't have an efficient way to keep the list up to
22021 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
22022 - Exit nodes now accept and queue data on not-yet-connected streams.
22023 Previously, the client wasn't allowed to send data until the stream was
22024 connected, which slowed down all connections. This change will enable
22025 clients to perform a "fast-start" on streams and send data without
22026 having to wait for a confirmation that the stream has opened. (Patch
22027 from Ian Goldberg; implements the server side of Proposal 174.)
22028 - Tor now has initial support for automatic port mapping on the many
22029 home routers that support NAT-PMP or UPnP. (Not yet supported on
22030 Windows). To build the support code, you'll need to have libnatpnp
22031 library and/or the libminiupnpc library, and you'll need to enable the
22032 feature specifically by passing "--enable-upnp" and/or
22033 "--enable-natpnp" to configure. To turn it on, use the new
22034 PortForwarding option.
22035 - Caches now download, cache, and serve multiple "flavors" of the
22036 consensus, including a flavor that describes microdescriptors.
22037 - Caches now download, cache, and serve microdescriptors -- small
22038 summaries of router descriptors that are authenticated by all of the
22039 directory authorities. Once enough caches are running this code,
22040 clients will be able to save significant amounts of directory bandwidth
22041 by downloading microdescriptors instead of router descriptors.
22044 - Make logging resolution configurable with a new LogTimeGranularity
22045 option, and change the default from 1 millisecond to 1 second.
22046 Implements enhancement 1668.
22047 - We log which torrc file we're using on startup. Implements ticket
22049 - Ordinarily, Tor does not count traffic from private addresses (like
22050 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
22051 There is now a new option, CountPrivateBandwidth, to disable this
22052 behavior. Patch from Daniel Cagara.
22053 - New --enable-static-tor configure option for building Tor as
22054 statically as possible. Idea, general hackery and thoughts from
22055 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
22057 - If you set the NumCPUs option to 0, Tor will now try to detect how
22058 many CPUs you have. This is the new default behavior.
22059 - Turn on directory request statistics by default and include them in
22060 extra-info descriptors. Don't break if we have no GeoIP database.
22061 - Relays that set "ConnDirectionStatistics 1" write statistics on the
22062 bidirectional use of connections to disk every 24 hours.
22063 - Add a GeoIP file digest to the extra-info descriptor. Implements
22065 - The NodeFamily option -- which let you declare that you want to
22066 consider nodes to be part of a family whether they list themselves
22067 that way or not -- now allows IP address ranges and country codes.
22068 - Add a new 'Heartbeat' log message type to periodically log a message
22069 describing Tor's status at level Notice. This feature is meant for
22070 operators who log at notice, and want to make sure that their Tor
22071 server is still working. Implementation by George Kadianakis.
22073 o Minor bugfixes (on 0.2.2.25-alpha):
22074 - When loading the microdesc journal, remember its current size.
22075 In 0.2.2, this helps prevent the microdesc journal from growing
22076 without limit on authorities (who are the only ones to use it in
22077 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
22078 Fix posted by "cypherpunks."
22079 - The microdesc journal is supposed to get rebuilt only if it is
22080 at least _half_ the length of the store, not _twice_ the length
22081 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
22082 - If as an authority we fail to compute the identity digest of a v3
22083 legacy keypair, warn, and don't use a buffer-full of junk instead.
22084 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
22085 - Authorities now clean their microdesc cache periodically and when
22086 reading from disk initially, not only when adding new descriptors.
22087 This prevents a bug where we could lose microdescriptors. Bugfix
22090 o Minor features (controller):
22091 - Add a new SIGNAL event to the controller interface so that
22092 controllers can be notified when Tor handles a signal. Resolves
22093 issue 1955. Patch by John Brooks.
22094 - Add a new GETINFO option to get total bytes read and written. Patch
22095 from pipe, revised by atagar. Resolves ticket 2345.
22096 - Implement some GETINFO controller fields to provide information about
22097 the Tor process's pid, euid, username, and resource limits.
22100 - Our build system requires automake 1.6 or later to create the
22101 Makefile.in files. Previously, you could have used 1.4.
22102 This only affects developers and people building Tor from git;
22103 people who build Tor from the source distribution without changing
22104 the Makefile.am files should be fine.
22105 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
22106 so on. This is more robust against some of the failure modes
22107 associated with running the autotools pieces on their own.
22109 o Minor packaging issues:
22110 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
22111 already created. Patch from Andreas Stieger. Fixes bug 2573.
22113 o Code simplifications and refactoring:
22114 - A major revision to our internal node-selecting and listing logic.
22115 Tor already had at least two major ways to look at the question of
22116 "which Tor servers do we know about": a list of router descriptors,
22117 and a list of entries in the current consensus. With
22118 microdescriptors, we're adding a third. Having so many systems
22119 without an abstraction layer over them was hurting the codebase.
22120 Now, we have a new "node_t" abstraction that presents a consistent
22121 interface to a client's view of a Tor node, and holds (nearly) all
22122 of the mutable state formerly in routerinfo_t and routerstatus_t.
22123 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
22124 no longer link against Libevent: they never used it, but
22125 our library structure used to force them to link it.
22127 o Removed features:
22128 - Remove some old code to work around even older versions of Tor that
22129 used forked processes to handle DNS requests. Such versions of Tor
22130 are no longer in use as servers.
22132 o Documentation fixes:
22133 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
22134 - Add missing documentation for the authority-related torrc options
22135 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
22139 Changes in version 0.2.2.25-alpha - 2011-04-29
22140 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
22141 robust, routers no longer overreport their bandwidth, Win7 should crash
22142 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
22143 now prevents hidden service-related activity from being linkable. It
22144 provides more information to Vidalia so you can see if your bridge is
22145 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
22146 StrictNodes configuration options to make them more reliable, more
22147 understandable, and more regularly applied. If you use those options,
22148 please see the revised documentation for them in the manual page.
22151 - Relays were publishing grossly inflated bandwidth values because
22152 they were writing their state files wrong--now they write the
22153 correct value. Also, resume reading bandwidth history from the
22154 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
22155 - Improve hidden service robustness: When we find that we have
22156 extended a hidden service's introduction circuit to a relay not
22157 listed as an introduction point in the HS descriptor we currently
22158 have, retry with an introduction point from the current
22159 descriptor. Previously we would just give up. Fixes bugs 1024 and
22160 1930; bugfix on 0.2.0.10-alpha.
22161 - Clients now stop trying to use an exit node associated with a given
22162 destination by TrackHostExits if they fail to reach that exit node.
22163 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
22164 - Fix crash bug on platforms where gmtime and localtime can return
22165 NULL. Windows 7 users were running into this one. Fixes part of bug
22166 2077. Bugfix on all versions of Tor. Found by boboper.
22168 o Security and stability fixes:
22169 - Don't double-free a parsable, but invalid, microdescriptor, even if
22170 it is followed in the blob we're parsing by an unparsable
22171 microdescriptor. Fixes an issue reported in a comment on bug 2954.
22172 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
22173 - If the Nickname configuration option isn't given, Tor would pick a
22174 nickname based on the local hostname as the nickname for a relay.
22175 Because nicknames are not very important in today's Tor and the
22176 "Unnamed" nickname has been implemented, this is now problematic
22177 behavior: It leaks information about the hostname without being
22178 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
22179 introduced the Unnamed nickname. Reported by tagnaq.
22180 - Fix an uncommon assertion failure when running with DNSPort under
22181 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22182 - Avoid linkability based on cached hidden service descriptors: forget
22183 all hidden service descriptors cached as a client when processing a
22184 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22187 - Export GeoIP information on bridge usage to controllers even if we
22188 have not yet been running for 24 hours. Now Vidalia bridge operators
22189 can get more accurate and immediate feedback about their
22190 contributions to the network.
22192 o Major features and bugfixes (node selection):
22193 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
22194 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
22195 options. Previously, we had been ambiguous in describing what
22196 counted as an "exit" node, and what operations exactly "StrictNodes
22197 0" would permit. This created confusion when people saw nodes built
22198 through unexpected circuits, and made it hard to tell real bugs from
22199 surprises. Now the intended behavior is:
22200 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
22201 a node that delivers user traffic outside the Tor network.
22202 . "Entry", in the context of EntryNodes, means a node used as the
22203 first hop of a multihop circuit. It doesn't include direct
22204 connections to directory servers.
22205 . "ExcludeNodes" applies to all nodes.
22206 . "StrictNodes" changes the behavior of ExcludeNodes only. When
22207 StrictNodes is set, Tor should avoid all nodes listed in
22208 ExcludeNodes, even when it will make user requests fail. When
22209 StrictNodes is *not* set, then Tor should follow ExcludeNodes
22210 whenever it can, except when it must use an excluded node to
22211 perform self-tests, connect to a hidden service, provide a
22212 hidden service, fulfill a .exit request, upload directory
22213 information, or fetch directory information.
22214 Collectively, the changes to implement the behavior fix bug 1090.
22215 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
22216 a node is listed in both, it's treated as excluded.
22217 - ExcludeNodes now applies to directory nodes -- as a preference if
22218 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
22219 Don't exclude all the directory authorities and set StrictNodes to 1
22220 unless you really want your Tor to break.
22221 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
22222 - ExcludeExitNodes now overrides .exit requests.
22223 - We don't use bridges listed in ExcludeNodes.
22224 - When StrictNodes is 1:
22225 . We now apply ExcludeNodes to hidden service introduction points
22226 and to rendezvous points selected by hidden service users. This
22227 can make your hidden service less reliable: use it with caution!
22228 . If we have used ExcludeNodes on ourself, do not try relay
22229 reachability self-tests.
22230 . If we have excluded all the directory authorities, we will not
22231 even try to upload our descriptor if we're a relay.
22232 . Do not honor .exit requests to an excluded node.
22233 - Remove a misfeature that caused us to ignore the Fast/Stable flags
22234 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
22235 - When the set of permitted nodes changes, we now remove any mappings
22236 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
22238 - We never cannibalize a circuit that had excluded nodes on it, even
22239 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
22240 - Revert a change where we would be laxer about attaching streams to
22241 circuits than when building the circuits. This was meant to prevent
22242 a set of bugs where streams were never attachable, but our improved
22243 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
22244 - Keep track of how many times we launch a new circuit to handle a
22245 given stream. Too many launches could indicate an inconsistency
22246 between our "launch a circuit to handle this stream" logic and our
22247 "attach this stream to one of the available circuits" logic.
22248 - Improve log messages related to excluded nodes.
22251 - Fix a spurious warning when moving from a short month to a long
22252 month on relays with month-based BandwidthAccounting. Bugfix on
22253 0.2.2.17-alpha; fixes bug 3020.
22254 - When a client finds that an origin circuit has run out of 16-bit
22255 stream IDs, we now mark it as unusable for new streams. Previously,
22256 we would try to close the entire circuit. Bugfix on 0.0.6.
22257 - Add a forgotten cast that caused a compile warning on OS X 10.6.
22258 Bugfix on 0.2.2.24-alpha.
22259 - Be more careful about reporting the correct error from a failed
22260 connect() system call. Under some circumstances, it was possible to
22261 look at an incorrect value for errno when sending the end reason.
22262 Bugfix on 0.1.0.1-rc.
22263 - Correctly handle an "impossible" overflow cases in connection byte
22264 counting, where we write or read more than 4GB on an edge connection
22265 in a single second. Bugfix on 0.1.2.8-beta.
22266 - Correct the warning displayed when a rendezvous descriptor exceeds
22267 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22269 - Clients and hidden services now use HSDir-flagged relays for hidden
22270 service descriptor downloads and uploads even if the relays have no
22271 DirPort set and the client has disabled TunnelDirConns. This will
22272 eventually allow us to give the HSDir flag to relays with no
22273 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
22274 - Downgrade "no current certificates known for authority" message from
22275 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22276 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
22277 2917. Bugfix on 0.1.1.1-alpha.
22278 - Only limit the lengths of single HS descriptors, even when multiple
22279 HS descriptors are published to an HSDir relay in a single POST
22280 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
22281 - Write the current time into the LastWritten line in our state file,
22282 rather than the time from the previous write attempt. Also, stop
22283 trying to use a time of -1 in our log statements. Fixes bug 3039;
22284 bugfix on 0.2.2.14-alpha.
22285 - Be more consistent in our treatment of file system paths. "~" should
22286 get expanded to the user's home directory in the Log config option.
22287 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
22288 feature for the -f and --DataDirectory options.
22291 - Make sure every relay writes a state file at least every 12 hours.
22292 Previously, a relay could go for weeks without writing its state
22293 file, and on a crash could lose its bandwidth history, capacity
22294 estimates, client country statistics, and so on. Addresses bug 3012.
22295 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22296 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22297 clients are already deprecated because of security bugs.
22298 - Don't allow v0 hidden service authorities to act as clients.
22299 Required by fix for bug 3000.
22300 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22301 by fix for bug 3000.
22302 - Ensure that no empty [dirreq-](read|write)-history lines are added
22303 to an extrainfo document. Implements ticket 2497.
22305 o Code simplification and refactoring:
22306 - Remove workaround code to handle directory responses from servers
22307 that had bug 539 (they would send HTTP status 503 responses _and_
22308 send a body too). Since only server versions before
22309 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22310 keep the workaround in place.
22311 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22312 handling calculations where we have a known amount of clock skew and
22313 an allowed amount of unknown skew. But we only used it in three
22314 places, and we never adjusted the known/unknown skew values. This is
22315 still something we might want to do someday, but if we do, we'll
22316 want to do it differently.
22317 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22318 None of the cases where we did this before were wrong, but by making
22319 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22320 - Use GetTempDir to find the proper temporary directory location on
22321 Windows when generating temporary files for the unit tests. Patch by
22325 Changes in version 0.2.2.24-alpha - 2011-04-08
22326 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
22327 prevented Tor clients from effectively using "multihomed" bridges,
22328 that is, bridges that listen on multiple ports or IP addresses so users
22329 can continue to use some of their addresses even if others get blocked.
22332 - Fix a bug where bridge users who configure the non-canonical
22333 address of a bridge automatically switch to its canonical
22334 address. If a bridge listens at more than one address, it should be
22335 able to advertise those addresses independently and any non-blocked
22336 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
22338 - If you configured Tor to use bridge A, and then quit and
22339 configured Tor to use bridge B instead, it would happily continue
22340 to use bridge A if it's still reachable. While this behavior is
22341 a feature if your goal is connectivity, in some scenarios it's a
22342 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22343 - Directory authorities now use data collected from their own
22344 uptime observations when choosing whether to assign the HSDir flag
22345 to relays, instead of trusting the uptime value the relay reports in
22346 its descriptor. This change helps prevent an attack where a small
22347 set of nodes with frequently-changing identity keys can blackhole
22348 a hidden service. (Only authorities need upgrade; others will be
22349 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22352 - When we restart our relay, we might get a successful connection
22353 from the outside before we've started our reachability tests,
22354 triggering a warning: "ORPort found reachable, but I have no
22355 routerinfo yet. Failing to inform controller of success." This
22356 bug was harmless unless Tor is running under a controller
22357 like Vidalia, in which case the controller would never get a
22358 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22360 - Make directory authorities more accurate at recording when
22361 relays that have failed several reachability tests became
22362 unreachable, so we can provide more accuracy at assigning Stable,
22363 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22364 - Fix an issue that prevented static linking of libevent on
22365 some platforms (notably Linux). Fixes bug 2698; bugfix on
22366 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
22367 the --with-static-libevent configure option).
22368 - We now ask the other side of a stream (the client or the exit)
22369 for more data on that stream when the amount of queued data on
22370 that stream dips low enough. Previously, we wouldn't ask the
22371 other side for more data until either it sent us more data (which
22372 it wasn't supposed to do if it had exhausted its window!) or we
22373 had completely flushed all our queued data. This flow control fix
22374 should improve throughput. Fixes bug 2756; bugfix on the earliest
22375 released versions of Tor (svn commit r152).
22376 - Avoid a double-mark-for-free warning when failing to attach a
22377 transparent proxy connection. (We thought we had fixed this in
22378 0.2.2.23-alpha, but it turns out our fix was checking the wrong
22379 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
22380 bug) and 0.2.2.23-alpha (the incorrect fix).
22381 - When warning about missing zlib development packages during compile,
22382 give the correct package names. Bugfix on 0.2.0.1-alpha.
22385 - Directory authorities now log the source of a rejected POSTed v3
22386 networkstatus vote.
22387 - Make compilation with clang possible when using
22388 --enable-gcc-warnings by removing two warning options that clang
22389 hasn't implemented yet and by fixing a few warnings. Implements
22391 - When expiring circuits, use microsecond timers rather than
22392 one-second timers. This can avoid an unpleasant situation where a
22393 circuit is launched near the end of one second and expired right
22394 near the beginning of the next, and prevent fluctuations in circuit
22396 - Use computed circuit-build timeouts to decide when to launch
22397 parallel introduction circuits for hidden services. (Previously,
22398 we would retry after 15 seconds.)
22399 - Update to the April 1 2011 Maxmind GeoLite Country database.
22402 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22403 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22405 o Documentation changes:
22406 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22407 - Resolve all doxygen warnings except those for missing documentation.
22409 - Add doxygen documentation for more functions, fields, and types.
22412 Changes in version 0.2.2.23-alpha - 2011-03-08
22413 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
22414 they restart they don't lose their bandwidth capacity estimate. This
22415 release also fixes a diverse set of user-facing bugs, ranging from
22416 relays overrunning their rate limiting to clients falsely warning about
22417 clock skew to bridge descriptor leaks by our bridge directory authority.
22420 - Stop sending a CLOCK_SKEW controller status event whenever
22421 we fetch directory information from a relay that has a wrong clock.
22422 Instead, only inform the controller when it's a trusted authority
22423 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22424 the rest of bug 1074.
22425 - Fix an assert in parsing router descriptors containing IPv6
22426 addresses. This one took down the directory authorities when
22427 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22428 - Make the bridge directory authority refuse to answer directory
22429 requests for "all" descriptors. It used to include bridge
22430 descriptors in its answer, which was a major information leak.
22431 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22432 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22433 Tor would ignore their RelayBandwidthBurst setting,
22434 potentially using more bandwidth than expected. Bugfix on
22435 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22436 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22437 hidserv" in her torrc. The 'hidserv' argument never controlled
22438 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22441 - Relays now save observed peak bandwidth throughput rates to their
22442 state file (along with total usage, which was already saved)
22443 so that they can determine their correct estimated bandwidth on
22444 restart. Resolves bug 1863, where Tor relays would reset their
22445 estimated bandwidth to 0 after restarting.
22446 - Directory authorities now take changes in router IP address and
22447 ORPort into account when determining router stability. Previously,
22448 if a router changed its IP or ORPort, the authorities would not
22449 treat it as having any downtime for the purposes of stability
22450 calculation, whereas clients would experience downtime since the
22451 change could take a while to propagate to them. Resolves issue 1035.
22452 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22453 Prevention (DEP) by default on Windows to make it harder for
22454 attackers to exploit vulnerabilities. Patch from John Brooks.
22456 o Minor bugfixes (on 0.2.1.x and earlier):
22457 - Fix a rare crash bug that could occur when a client was configured
22458 with a large number of bridges. Fixes bug 2629; bugfix on
22459 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22460 - Avoid a double mark-for-free warning when failing to attach a
22461 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22463 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22464 found by "cypherpunks". This bug was introduced before the first
22465 Tor release, in svn commit r110.
22466 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
22467 don't mention them in the manpage. Fixes bug 2450; issue
22468 spotted by keb and G-Lo.
22469 - Fix a bug in bandwidth history state parsing that could have been
22470 triggered if a future version of Tor ever changed the timing
22471 granularity at which bandwidth history is measured. Bugfix on
22472 Tor 0.1.1.11-alpha.
22473 - When a relay decides that its DNS is too broken for it to serve
22474 as an exit server, it advertised itself as a non-exit, but
22475 continued to act as an exit. This could create accidental
22476 partitioning opportunities for users. Instead, if a relay is
22477 going to advertise reject *:* as its exit policy, it should
22478 really act with exit policy "reject *:*". Fixes bug 2366.
22479 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22480 - In the special case where you configure a public exit relay as your
22481 bridge, Tor would be willing to use that exit relay as the last
22482 hop in your circuit as well. Now we fail that circuit instead.
22483 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22484 - Fix a bug with our locking implementation on Windows that couldn't
22485 correctly detect when a file was already locked. Fixes bug 2504,
22486 bugfix on 0.2.1.6-alpha.
22487 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22488 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22490 - Set target port in get_interface_address6() correctly. Bugfix
22491 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22492 - Directory authorities are now more robust to hops back in time
22493 when calculating router stability. Previously, if a run of uptime
22494 or downtime appeared to be negative, the calculation could give
22495 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22497 - Fix an assert that got triggered when using the TestingTorNetwork
22498 configuration option and then issuing a GETINFO config-text control
22499 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22501 o Minor bugfixes (on 0.2.2.x):
22502 - Clients should not weight BadExit nodes as Exits in their node
22503 selection. Similarly, directory authorities should not count BadExit
22504 bandwidth as Exit bandwidth when computing bandwidth-weights.
22505 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
22506 - Correctly clear our dir_read/dir_write history when there is an
22507 error parsing any bw history value from the state file. Bugfix on
22508 Tor 0.2.2.15-alpha.
22509 - Resolve a bug in verifying signatures of directory objects
22510 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
22511 Fixes bug 2409. Found by "piebeer".
22512 - Bridge authorities no longer crash on SIGHUP when they try to
22513 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
22517 - Log less aggressively about circuit timeout changes, and improve
22518 some other circuit timeout messages. Resolves bug 2004.
22519 - Log a little more clearly about the times at which we're no longer
22520 accepting new connections. Resolves bug 2181.
22521 - Reject attempts at the client side to open connections to private
22522 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22523 a randomly chosen exit node. Attempts to do so are always
22524 ill-defined, generally prevented by exit policies, and usually
22525 in error. This will also help to detect loops in transparent
22526 proxy configurations. You can disable this feature by setting
22527 "ClientRejectInternalAddresses 0" in your torrc.
22528 - Always treat failure to allocate an RSA key as an unrecoverable
22530 - Update to the March 1 2011 Maxmind GeoLite Country database.
22532 o Minor features (log subsystem):
22533 - Add documentation for configuring logging at different severities in
22534 different log domains. We've had this feature since 0.2.1.1-alpha,
22535 but for some reason it never made it into the manpage. Fixes
22537 - Make it simpler to specify "All log domains except for A and B".
22538 Previously you needed to say "[*,~A,~B]". Now you can just say
22540 - Add a "LogMessageDomains 1" option to include the domains of log
22541 messages along with the messages. Without this, there's no way
22542 to use log domains without reading the source or doing a lot
22545 o Packaging changes:
22546 - Stop shipping the Tor specs files and development proposal documents
22547 in the tarball. They are now in a separate git repository at
22548 git://git.torproject.org/torspec.git
22551 Changes in version 0.2.1.30 - 2011-02-23
22552 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22553 change is a slight tweak to Tor's TLS handshake that makes relays
22554 and bridges that run this new version reachable from Iran again.
22555 We don't expect this tweak will win the arms race long-term, but it
22556 buys us time until we roll out a better solution.
22559 - Stop sending a CLOCK_SKEW controller status event whenever
22560 we fetch directory information from a relay that has a wrong clock.
22561 Instead, only inform the controller when it's a trusted authority
22562 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22563 the rest of bug 1074.
22564 - Fix a bounds-checking error that could allow an attacker to
22565 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22566 Found by "piebeer".
22567 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22568 Tor would ignore their RelayBandwidthBurst setting,
22569 potentially using more bandwidth than expected. Bugfix on
22570 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22571 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22572 hidserv" in her torrc. The 'hidserv' argument never controlled
22573 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22576 - Adjust our TLS Diffie-Hellman parameters to match those used by
22578 - Update to the February 1 2011 Maxmind GeoLite Country database.
22581 - Check for and reject overly long directory certificates and
22582 directory tokens before they have a chance to hit any assertions.
22583 Bugfix on 0.2.1.28. Found by "doorss".
22584 - Bring the logic that gathers routerinfos and assesses the
22585 acceptability of circuits into line. This prevents a Tor OP from
22586 getting locked in a cycle of choosing its local OR as an exit for a
22587 path (due to a .exit request) and then rejecting the circuit because
22588 its OR is not listed yet. It also prevents Tor clients from using an
22589 OR running in the same instance as an exit (due to a .exit request)
22590 if the OR does not meet the same requirements expected of an OR
22591 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22593 o Packaging changes:
22594 - Stop shipping the Tor specs files and development proposal documents
22595 in the tarball. They are now in a separate git repository at
22596 git://git.torproject.org/torspec.git
22597 - Do not include Git version tags as though they are SVN tags when
22598 generating a tarball from inside a repository that has switched
22599 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22602 Changes in version 0.2.2.22-alpha - 2011-01-25
22603 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
22604 main other change is a slight tweak to Tor's TLS handshake that makes
22605 relays and bridges that run this new version reachable from Iran again.
22606 We don't expect this tweak will win the arms race long-term, but it
22607 will buy us a bit more time until we roll out a better solution.
22610 - Fix a bounds-checking error that could allow an attacker to
22611 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22612 Found by "piebeer".
22613 - Don't assert when changing from bridge to relay or vice versa
22614 via the controller. The assert happened because we didn't properly
22615 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
22616 bug 2433. Reported by bastik.
22619 - Adjust our TLS Diffie-Hellman parameters to match those used by
22621 - Provide a log message stating which geoip file we're parsing
22622 instead of just stating that we're parsing the geoip file.
22623 Implements ticket 2432.
22626 - Check for and reject overly long directory certificates and
22627 directory tokens before they have a chance to hit any assertions.
22628 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
22631 Changes in version 0.2.2.21-alpha - 2011-01-15
22632 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
22633 continues our recent code security audit work. The main fix resolves
22634 a remote heap overflow vulnerability that can allow remote code
22635 execution (CVE-2011-0427). Other fixes address a variety of assert
22636 and crash bugs, most of which we think are hard to exploit remotely.
22638 o Major bugfixes (security), also included in 0.2.1.29:
22639 - Fix a heap overflow bug where an adversary could cause heap
22640 corruption. This bug probably allows remote code execution
22641 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22643 - Prevent a denial-of-service attack by disallowing any
22644 zlib-compressed data whose compression factor is implausibly
22645 high. Fixes part of bug 2324; reported by "doorss".
22646 - Zero out a few more keys in memory before freeing them. Fixes
22647 bug 2384 and part of bug 2385. These key instances found by
22648 "cypherpunks", based on Andrew Case's report about being able
22649 to find sensitive data in Tor's memory space if you have enough
22650 permissions. Bugfix on 0.0.2pre9.
22652 o Major bugfixes (crashes), also included in 0.2.1.29:
22653 - Prevent calls to Libevent from inside Libevent log handlers.
22654 This had potential to cause a nasty set of crashes, especially
22655 if running Libevent with debug logging enabled, and running
22656 Tor with a controller watching for low-severity log messages.
22657 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22658 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22659 underflow errors there too. Fixes the other part of bug 2324.
22660 - Fix a bug where we would assert if we ever had a
22661 cached-descriptors.new file (or another file read directly into
22662 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22663 on 0.2.1.25. Found by doorss.
22664 - Fix some potential asserts and parsing issues with grossly
22665 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22668 o Minor bugfixes (other), also included in 0.2.1.29:
22669 - Fix a bug with handling misformed replies to reverse DNS lookup
22670 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22671 bug reported by doorss.
22672 - Fix compilation on mingw when a pthreads compatibility library
22673 has been installed. (We don't want to use it, so we shouldn't
22674 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22675 - Fix a bug where we would declare that we had run out of virtual
22676 addresses when the address space was only half-exhausted. Bugfix
22678 - Correctly handle the case where AutomapHostsOnResolve is set but
22679 no virtual addresses are available. Fixes bug 2328; bugfix on
22680 0.1.2.1-alpha. Bug found by doorss.
22681 - Correctly handle wrapping around when we run out of virtual
22682 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22684 o Minor features, also included in 0.2.1.29:
22685 - Update to the January 1 2011 Maxmind GeoLite Country database.
22686 - Introduce output size checks on all of our decryption functions.
22688 o Build changes, also included in 0.2.1.29:
22689 - Tor does not build packages correctly with Automake 1.6 and earlier;
22690 added a check to Makefile.am to make sure that we're building with
22691 Automake 1.7 or later.
22692 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22693 because we built it with a too-old version of automake. Thus that
22694 release broke ./configure --enable-openbsd-malloc, which is popular
22695 among really fast exit relays on Linux.
22697 o Major bugfixes, new in 0.2.2.21-alpha:
22698 - Prevent crash/heap corruption when the cbtnummodes consensus
22699 parameter is set to 0 or large values. Fixes bug 2317; bugfix
22702 o Major features, new in 0.2.2.21-alpha:
22703 - Introduce minimum/maximum values that clients will believe
22704 from the consensus. Now we'll have a better chance to avoid crashes
22705 or worse when a consensus param has a weird value.
22707 o Minor features, new in 0.2.2.21-alpha:
22708 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22709 used on bridges, and it makes bridge scanning somewhat easier.
22710 - If writing the state file to disk fails, wait up to an hour before
22711 retrying again, rather than trying again each second. Fixes bug
22712 2346; bugfix on Tor 0.1.1.3-alpha.
22713 - Make Libevent log messages get delivered to controllers later,
22714 and not from inside the Libevent log handler. This prevents unsafe
22715 reentrant Libevent calls while still letting the log messages
22717 - Detect platforms that brokenly use a signed size_t, and refuse to
22718 build there. Found and analyzed by doorss and rransom.
22719 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22722 o Minor bugfixes, new in 0.2.2.21-alpha:
22723 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22724 than waiting forever for them to finish. Fixes bug 2330; bugfix
22725 on 0.2.0.16-alpha. Found by doorss.
22726 - Add assertions to check for overflow in arguments to
22727 base32_encode() and base32_decode(); fix a signed-unsigned
22728 comparison there too. These bugs are not actually reachable in Tor,
22729 but it's good to prevent future errors too. Found by doorss.
22730 - Correctly detect failures to create DNS requests when using Libevent
22731 versions before v2. (Before Libevent 2, we used our own evdns
22732 implementation. Its return values for Libevent's evdns_resolve_*()
22733 functions are not consistent with those from Libevent.) Fixes bug
22734 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22736 o Documentation, new in 0.2.2.21-alpha:
22737 - Document the default socks host and port (127.0.0.1:9050) for
22741 Changes in version 0.2.1.29 - 2011-01-15
22742 Tor 0.2.1.29 continues our recent code security audit work. The main
22743 fix resolves a remote heap overflow vulnerability that can allow remote
22744 code execution. Other fixes address a variety of assert and crash bugs,
22745 most of which we think are hard to exploit remotely.
22747 o Major bugfixes (security):
22748 - Fix a heap overflow bug where an adversary could cause heap
22749 corruption. This bug probably allows remote code execution
22750 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22752 - Prevent a denial-of-service attack by disallowing any
22753 zlib-compressed data whose compression factor is implausibly
22754 high. Fixes part of bug 2324; reported by "doorss".
22755 - Zero out a few more keys in memory before freeing them. Fixes
22756 bug 2384 and part of bug 2385. These key instances found by
22757 "cypherpunks", based on Andrew Case's report about being able
22758 to find sensitive data in Tor's memory space if you have enough
22759 permissions. Bugfix on 0.0.2pre9.
22761 o Major bugfixes (crashes):
22762 - Prevent calls to Libevent from inside Libevent log handlers.
22763 This had potential to cause a nasty set of crashes, especially
22764 if running Libevent with debug logging enabled, and running
22765 Tor with a controller watching for low-severity log messages.
22766 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22767 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22768 underflow errors there too. Fixes the other part of bug 2324.
22769 - Fix a bug where we would assert if we ever had a
22770 cached-descriptors.new file (or another file read directly into
22771 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22772 on 0.2.1.25. Found by doorss.
22773 - Fix some potential asserts and parsing issues with grossly
22774 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22777 o Minor bugfixes (other):
22778 - Fix a bug with handling misformed replies to reverse DNS lookup
22779 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22780 bug reported by doorss.
22781 - Fix compilation on mingw when a pthreads compatibility library
22782 has been installed. (We don't want to use it, so we shouldn't
22783 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22784 - Fix a bug where we would declare that we had run out of virtual
22785 addresses when the address space was only half-exhausted. Bugfix
22787 - Correctly handle the case where AutomapHostsOnResolve is set but
22788 no virtual addresses are available. Fixes bug 2328; bugfix on
22789 0.1.2.1-alpha. Bug found by doorss.
22790 - Correctly handle wrapping around to when we run out of virtual
22791 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22792 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22793 because we built it with a too-old version of automake. Thus that
22794 release broke ./configure --enable-openbsd-malloc, which is popular
22795 among really fast exit relays on Linux.
22798 - Update to the January 1 2011 Maxmind GeoLite Country database.
22799 - Introduce output size checks on all of our decryption functions.
22802 - Tor does not build packages correctly with Automake 1.6 and earlier;
22803 added a check to Makefile.am to make sure that we're building with
22804 Automake 1.7 or later.
22807 Changes in version 0.2.2.20-alpha - 2010-12-17
22808 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22809 exploitable bugs. We also fix a variety of other significant bugs,
22810 change the IP address for one of our directory authorities, and update
22811 the minimum version that Tor relays must run to join the network.
22814 - Fix a remotely exploitable bug that could be used to crash instances
22815 of Tor remotely by overflowing on the heap. Remote-code execution
22816 hasn't been confirmed, but can't be ruled out. Everyone should
22817 upgrade. Bugfix on the 0.1.1 series and later.
22818 - Fix a bug that could break accounting on 64-bit systems with large
22819 time_t values, making them hibernate for impossibly long intervals.
22820 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22821 - Fix a logic error in directory_fetches_from_authorities() that
22822 would cause all _non_-exits refusing single-hop-like circuits
22823 to fetch from authorities, when we wanted to have _exits_ fetch
22824 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22826 - Fix a stream fairness bug that would cause newer streams on a given
22827 circuit to get preference when reading bytes from the origin or
22828 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22829 introduced before the first Tor release, in svn revision r152.
22831 o Directory authority changes:
22832 - Change IP address and ports for gabelmoo (v3 directory authority).
22835 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22836 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22837 - Fix an off-by-one error in calculating some controller command
22838 argument lengths. Fortunately, this mistake is harmless since
22839 the controller code does redundant NUL termination too. Found by
22840 boboper. Bugfix on 0.1.1.1-alpha.
22841 - Do not dereference NULL if a bridge fails to build its
22842 extra-info descriptor. Found by an anonymous commenter on
22843 Trac. Bugfix on 0.2.2.19-alpha.
22846 - Update to the December 1 2010 Maxmind GeoLite Country database.
22847 - Directory authorities now reject relays running any versions of
22848 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22849 known bugs that keep RELAY_EARLY cells from working on rendezvous
22850 circuits. Followup to fix for bug 2081.
22851 - Directory authorities now reject relays running any version of Tor
22852 older than 0.2.0.26-rc. That version is the earliest that fetches
22853 current directory information correctly. Fixes bug 2156.
22854 - Report only the top 10 ports in exit-port stats in order not to
22855 exceed the maximum extra-info descriptor length of 50 KB. Implements
22859 Changes in version 0.2.1.28 - 2010-12-17
22860 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22861 exploitable bugs. We also took this opportunity to change the IP address
22862 for one of our directory authorities, and to update the geoip database
22866 - Fix a remotely exploitable bug that could be used to crash instances
22867 of Tor remotely by overflowing on the heap. Remote-code execution
22868 hasn't been confirmed, but can't be ruled out. Everyone should
22869 upgrade. Bugfix on the 0.1.1 series and later.
22871 o Directory authority changes:
22872 - Change IP address and ports for gabelmoo (v3 directory authority).
22875 - Update to the December 1 2010 Maxmind GeoLite Country database.
22878 Changes in version 0.2.1.27 - 2010-11-23
22879 Yet another OpenSSL security patch broke its compatibility with Tor:
22880 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22881 also took this opportunity to fix several crash bugs, integrate a new
22882 directory authority, and update the bundled GeoIP database.
22885 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22886 No longer set the tlsext_host_name extension on server SSL objects;
22887 but continue to set it on client SSL objects. Our goal in setting
22888 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22889 bugfix on 0.2.1.1-alpha.
22890 - Do not log messages to the controller while shrinking buffer
22891 freelists. Doing so would sometimes make the controller connection
22892 try to allocate a buffer chunk, which would mess up the internals
22893 of the freelist and cause an assertion failure. Fixes bug 1125;
22894 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22895 - Learn our external IP address when we're a relay or bridge, even if
22896 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22897 where we introduced bridge relays that don't need to publish to
22898 be useful. Fixes bug 2050.
22899 - Do even more to reject (and not just ignore) annotations on
22900 router descriptors received anywhere but from the cache. Previously
22901 we would ignore such annotations at first, but cache them to disk
22902 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22903 - When you're using bridges and your network goes away and your
22904 bridges get marked as down, recover when you attempt a new socks
22905 connection (if the network is back), rather than waiting up to an
22906 hour to try fetching new descriptors for your bridges. Bugfix on
22907 0.2.0.3-alpha; fixes bug 1981.
22910 - Move to the November 2010 Maxmind GeoLite country db (rather
22911 than the June 2009 ip-to-country GeoIP db) for our statistics that
22912 count how many users relays are seeing from each country. Now we'll
22913 have more accurate data, especially for many African countries.
22915 o New directory authorities:
22916 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22920 - Fix an assertion failure that could occur in directory caches or
22921 bridge users when using a very short voting interval on a testing
22922 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
22924 - Enforce multiplicity rules when parsing annotations. Bugfix on
22925 0.2.0.8-alpha. Found by piebeer.
22926 - Allow handshaking OR connections to take a full KeepalivePeriod
22927 seconds to handshake. Previously, we would close them after
22928 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
22929 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
22931 - When building with --enable-gcc-warnings on OpenBSD, disable
22932 warnings in system headers. This makes --enable-gcc-warnings
22933 pass on OpenBSD 4.8.
22936 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
22937 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
22938 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
22939 Servers can start sending this code when enough clients recognize
22940 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
22941 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
22942 Patch from mingw-san.
22945 - Remove the old debian/ directory from the main Tor distribution.
22946 The official Tor-for-debian git repository lives at the URL
22947 https://git.torproject.org/debian/tor.git
22948 - Stop shipping the old doc/website/ directory in the tarball. We
22949 changed the website format in late 2010, and what we shipped in
22950 0.2.1.26 really wasn't that useful anyway.
22953 Changes in version 0.2.2.19-alpha - 2010-11-22
22954 Yet another OpenSSL security patch broke its compatibility with Tor:
22955 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
22958 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22959 No longer set the tlsext_host_name extension on server SSL objects;
22960 but continue to set it on client SSL objects. Our goal in setting
22961 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22962 bugfix on 0.2.1.1-alpha.
22965 - Try harder not to exceed the maximum length of 50 KB when writing
22966 statistics to extra-info descriptors. This bug was triggered by very
22967 fast relays reporting exit-port, entry, and dirreq statistics.
22968 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
22969 - Publish a router descriptor even if generating an extra-info
22970 descriptor fails. Previously we would not publish a router
22971 descriptor without an extra-info descriptor; this can cause fast
22972 exit relays collecting exit-port statistics to drop from the
22973 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
22976 Changes in version 0.2.2.18-alpha - 2010-11-16
22977 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
22978 us lately, makes unpublished bridge relays able to detect their IP
22979 address, and fixes a wide variety of other bugs to get us much closer
22980 to a stable release.
22983 - Do even more to reject (and not just ignore) annotations on
22984 router descriptors received anywhere but from the cache. Previously
22985 we would ignore such annotations at first, but cache them to disk
22986 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22987 - Do not log messages to the controller while shrinking buffer
22988 freelists. Doing so would sometimes make the controller connection
22989 try to allocate a buffer chunk, which would mess up the internals
22990 of the freelist and cause an assertion failure. Fixes bug 1125;
22991 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22992 - Learn our external IP address when we're a relay or bridge, even if
22993 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22994 where we introduced bridge relays that don't need to publish to
22995 be useful. Fixes bug 2050.
22996 - Maintain separate TLS contexts and certificates for incoming and
22997 outgoing connections in bridge relays. Previously we would use the
22998 same TLS contexts and certs for incoming and outgoing connections.
22999 Bugfix on 0.2.0.3-alpha; addresses bug 988.
23000 - Maintain separate identity keys for incoming and outgoing TLS
23001 contexts in bridge relays. Previously we would use the same
23002 identity keys for incoming and outgoing TLS contexts. Bugfix on
23003 0.2.0.3-alpha; addresses the other half of bug 988.
23004 - Avoid an assertion failure when we as an authority receive a
23005 duplicate upload of a router descriptor that we already have,
23006 but which we previously considered an obsolete descriptor.
23007 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
23008 - Avoid a crash bug triggered by looking at a dangling pointer while
23009 setting the network status consensus. Found by Robert Ransom.
23010 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
23011 - Fix a logic error where servers that _didn't_ act as exits would
23012 try to keep their server lists more aggressively up to date than
23013 exits, when it was supposed to be the other way around. Bugfix
23016 o Minor bugfixes (on Tor 0.2.1.x and earlier):
23017 - When we're trying to guess whether we know our IP address as
23018 a relay, we would log various ways that we failed to guess
23019 our address, but never log that we ended up guessing it
23020 successfully. Now add a log line to help confused and anxious
23021 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
23022 - Bring the logic that gathers routerinfos and assesses the
23023 acceptability of circuits into line. This prevents a Tor OP from
23024 getting locked in a cycle of choosing its local OR as an exit for a
23025 path (due to a .exit request) and then rejecting the circuit because
23026 its OR is not listed yet. It also prevents Tor clients from using an
23027 OR running in the same instance as an exit (due to a .exit request)
23028 if the OR does not meet the same requirements expected of an OR
23029 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
23030 - Correctly describe errors that occur when generating a TLS object.
23031 Previously we would attribute them to a failure while generating a
23032 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
23034 - Enforce multiplicity rules when parsing annotations. Bugfix on
23035 0.2.0.8-alpha. Found by piebeer.
23036 - Fix warnings that newer versions of autoconf produced during
23037 ./autogen.sh. These warnings appear to be harmless in our case,
23038 but they were extremely verbose. Fixes bug 2020.
23040 o Minor bugfixes (on Tor 0.2.2.x):
23041 - Enable protection of small arrays whenever we build with gcc
23042 hardening features, not only when also building with warnings
23043 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
23046 - Make hidden services work better in private Tor networks by not
23047 requiring any uptime to join the hidden service descriptor
23048 DHT. Implements ticket 2088.
23049 - Rate-limit the "your application is giving Tor only an IP address"
23050 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
23051 - When AllowSingleHopExits is set, print a warning to explain to the
23052 relay operator why most clients are avoiding her relay.
23053 - Update to the November 1 2010 Maxmind GeoLite Country database.
23055 o Code simplifications and refactoring:
23056 - When we fixed bug 1038 we had to put in a restriction not to send
23057 RELAY_EARLY cells on rend circuits. This was necessary as long
23058 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
23059 active. Now remove this obsolete check. Resolves bug 2081.
23060 - Some options used different conventions for uppercasing of acronyms
23061 when comparing manpage and source. Fix those in favor of the
23062 manpage, as it makes sense to capitalize acronyms.
23063 - Remove the torrc.complete file. It hasn't been kept up to date
23064 and users will have better luck checking out the manpage.
23065 - Remove the obsolete "NoPublish" option; it has been flagged
23066 as obsolete and has produced a warning since 0.1.1.18-rc.
23067 - Remove everything related to building the expert bundle for OS X.
23068 It has confused many users, doesn't work right on OS X 10.6,
23069 and is hard to get rid of once installed. Resolves bug 1274.
23072 Changes in version 0.2.2.17-alpha - 2010-09-30
23073 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
23074 to use one-hop circuits (which can put the exit relays at higher risk,
23075 plus unbalance the network); fixes a big bug in bandwidth accounting
23076 for relays that want to limit their monthly bandwidth use; fixes a
23077 big pile of bugs in how clients tolerate temporary network failure;
23078 and makes our adaptive circuit build timeout feature (which improves
23079 client performance if your network is fast while not breaking things
23080 if your network is slow) better handle bad networks.
23083 - Exit relays now try harder to block exit attempts from unknown
23084 relays, to make it harder for people to use them as one-hop proxies
23085 a la tortunnel. Controlled by the refuseunknownexits consensus
23086 parameter (currently enabled), or you can override it on your
23087 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
23089 o Major bugfixes (0.2.1.x and earlier):
23090 - Fix a bug in bandwidth accounting that could make us use twice
23091 the intended bandwidth when our interval start changes due to
23092 daylight saving time. Now we tolerate skew in stored vs computed
23093 interval starts: if the start of the period changes by no more than
23094 50% of the period's duration, we remember bytes that we transferred
23095 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
23096 - Always search the Windows system directory for system DLLs, and
23097 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
23098 - When you're using bridges and your network goes away and your
23099 bridges get marked as down, recover when you attempt a new socks
23100 connection (if the network is back), rather than waiting up to an
23101 hour to try fetching new descriptors for your bridges. Bugfix on
23102 0.2.0.3-alpha; fixes bug 1981.
23104 o Major bugfixes (on 0.2.2.x):
23105 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
23107 - Fix a segfault that could happen when operating a bridge relay with
23108 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
23109 - The consensus bandwidth-weights (used by clients to choose fast
23110 relays) entered an unexpected edge case in September where
23111 Exits were much scarcer than Guards, resulting in bad weight
23112 recommendations. Now we compute them using new constraints that
23113 should succeed in all cases. Also alter directory authorities to
23114 not include the bandwidth-weights line if they fail to produce
23115 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
23116 - When weighting bridges during path selection, we used to trust
23117 the bandwidths they provided in their descriptor, only capping them
23118 at 10MB/s. This turned out to be problematic for two reasons:
23119 Bridges could claim to handle a lot more traffic then they
23120 actually would, thus making more clients pick them and have a
23121 pretty effective DoS attack. The other issue is that new bridges
23122 that might not have a good estimate for their bw capacity yet
23123 would not get used at all unless no other bridges are available
23124 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
23126 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
23127 - Ignore cannibalized circuits when recording circuit build times.
23128 This should provide for a minor performance improvement for hidden
23129 service users using 0.2.2.14-alpha, and should remove two spurious
23130 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
23131 - Simplify the logic that causes us to decide if the network is
23132 unavailable for purposes of recording circuit build times. If we
23133 receive no cells whatsoever for the entire duration of a circuit's
23134 full measured lifetime, the network is probably down. Also ignore
23135 one-hop directory fetching circuit timeouts when calculating our
23136 circuit build times. These changes should hopefully reduce the
23137 cases where we see ridiculous circuit build timeouts for people
23138 with spotty wireless connections. Fixes part of bug 1772; bugfix
23140 - Prevent the circuit build timeout from becoming larger than
23141 the maximum build time we have ever seen. Also, prevent the time
23142 period for measurement circuits from becoming larger than twice that
23143 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
23146 - When we run out of directory information such that we can't build
23147 circuits, but then get enough that we can build circuits, log when
23148 we actually construct a circuit, so the user has a better chance of
23149 knowing what's going on. Fixes bug 1362.
23150 - Be more generous with how much bandwidth we'd use up (with
23151 accounting enabled) before entering "soft hibernation". Previously,
23152 we'd refuse new connections and circuits once we'd used up 95% of
23153 our allotment. Now, we use up 95% of our allotment, AND make sure
23154 that we have no more than 500MB (or 3 hours of expected traffic,
23155 whichever is lower) remaining before we enter soft hibernation.
23156 - If we've configured EntryNodes and our network goes away and/or all
23157 our entrynodes get marked down, optimistically retry them all when
23158 a new socks application request appears. Fixes bug 1882.
23159 - Add some more defensive programming for architectures that can't
23160 handle unaligned integer accesses. We don't know of any actual bugs
23161 right now, but that's the best time to fix them. Fixes bug 1943.
23162 - Support line continuations in the torrc config file. If a line
23163 ends with a single backslash character, the newline is ignored, and
23164 the configuration value is treated as continuing on the next line.
23167 o Minor bugfixes (on 0.2.1.x and earlier):
23168 - For bandwidth accounting, calculate our expected bandwidth rate
23169 based on the time during which we were active and not in
23170 soft-hibernation during the last interval. Previously, we were
23171 also considering the time spent in soft-hibernation. If this
23172 was a long time, we would wind up underestimating our bandwidth
23173 by a lot, and skewing our wakeup time towards the start of the
23174 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
23176 o Minor bugfixes (on 0.2.2.x):
23177 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
23178 which were disabled by the circuit build timeout changes in
23179 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
23180 - Make sure we don't warn about missing bandwidth weights when
23181 choosing bridges or other relays not in the consensus. Bugfix on
23182 0.2.2.10-alpha; fixes bug 1805.
23183 - In our logs, do not double-report signatures from unrecognized
23184 authorities both as "from unknown authority" and "not
23185 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
23188 Changes in version 0.2.2.16-alpha - 2010-09-17
23189 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
23190 evident at exit relays), and also continues to resolve all the little
23191 bugs that have been filling up trac lately.
23193 o Major bugfixes (stream-level fairness):
23194 - When receiving a circuit-level SENDME for a blocked circuit, try
23195 to package cells fairly from all the streams that had previously
23196 been blocked on that circuit. Previously, we had started with the
23197 oldest stream, and allowed each stream to potentially exhaust
23198 the circuit's package window. This gave older streams on any
23199 given circuit priority over newer ones. Fixes bug 1937. Detected
23200 originally by Camilo Viecco. This bug was introduced before the
23201 first Tor release, in svn commit r152: it is the new winner of
23202 the longest-lived bug prize.
23203 - When the exit relay got a circuit-level sendme cell, it started
23204 reading on the exit streams, even if had 500 cells queued in the
23205 circuit queue already, so the circuit queue just grew and grew in
23206 some cases. We fix this by not re-enabling reading on receipt of a
23207 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
23208 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
23210 - Newly created streams were allowed to read cells onto circuits,
23211 even if the circuit's cell queue was blocked and waiting to drain.
23212 This created potential unfairness, as older streams would be
23213 blocked, but newer streams would gladly fill the queue completely.
23214 We add code to detect this situation and prevent any stream from
23215 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
23219 - Update to the September 1 2010 Maxmind GeoLite Country database.
23220 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
23221 not. This would lead to a cookie that is still not group readable.
23222 Closes bug 1843. Suggested by katmagic.
23223 - When logging a rate-limited warning, we now mention how many messages
23224 got suppressed since the last warning.
23225 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
23226 do individual connection-level rate limiting of clients. The torrc
23227 config options with the same names trump the consensus params, if
23228 both are present. Replaces the old "bwconnrate" and "bwconnburst"
23229 consensus params which were broken from 0.2.2.7-alpha through
23230 0.2.2.14-alpha. Closes bug 1947.
23231 - When a router changes IP address or port, authorities now launch
23232 a new reachability test for it. Implements ticket 1899.
23233 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
23234 2 no signature, 4 required" messages about consensus signatures
23235 easier to read, and make sure they get logged at the same severity
23236 as the messages explaining which keys are which. Fixes bug 1290.
23237 - Don't warn when we have a consensus that we can't verify because
23238 of missing certificates, unless those certificates are ones
23239 that we have been trying and failing to download. Fixes bug 1145.
23240 - If you configure your bridge with a known identity fingerprint,
23241 and the bridge authority is unreachable (as it is in at least
23242 one country now), fall back to directly requesting the descriptor
23243 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
23245 - When building with --enable-gcc-warnings on OpenBSD, disable
23246 warnings in system headers. This makes --enable-gcc-warnings
23247 pass on OpenBSD 4.8.
23249 o Minor bugfixes (on 0.2.1.x and earlier):
23250 - Authorities will now attempt to download consensuses if their
23251 own efforts to make a live consensus have failed. This change
23252 means authorities that restart will fetch a valid consensus, and
23253 it means authorities that didn't agree with the current consensus
23254 will still fetch and serve it if it has enough signatures. Bugfix
23255 on 0.2.0.9-alpha; fixes bug 1300.
23256 - Ensure DNS requests launched by "RESOLVE" commands from the
23257 controller respect the __LeaveStreamsUnattached setconf options. The
23258 same goes for requests launched via DNSPort or transparent
23259 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
23260 - Allow handshaking OR connections to take a full KeepalivePeriod
23261 seconds to handshake. Previously, we would close them after
23262 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23263 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23265 - Rate-limit "Failed to hand off onionskin" warnings.
23266 - Never relay a cell for a circuit we have already destroyed.
23267 Between marking a circuit as closeable and finally closing it,
23268 it may have been possible for a few queued cells to get relayed,
23269 even though they would have been immediately dropped by the next
23270 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
23271 - Never queue a cell for a circuit that's already been marked
23273 - Never vote for a server as "Running" if we have a descriptor for
23274 it claiming to be hibernating, and that descriptor was published
23275 more recently than our last contact with the server. Bugfix on
23276 0.2.0.3-alpha; fixes bug 911.
23277 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
23280 o Minor bugfixes (on 0.2.2.x):
23281 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
23282 down if a directory fetch fails and you've configured either
23283 bridges or EntryNodes. The intent was to mark the relay as down
23284 _unless_ you're using bridges or EntryNodes, since if you are
23285 then you could quickly run out of entry points.
23286 - Fix the Windows directory-listing code. A bug introduced in
23287 0.2.2.14-alpha could make Windows directory servers forget to load
23288 some of their cached v2 networkstatus files.
23289 - Really allow clients to use relays as bridges. Fixes bug 1776;
23290 bugfix on 0.2.2.15-alpha.
23291 - Demote a warn to info that happens when the CellStatistics option
23292 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
23293 Reported by Moritz Bartl.
23294 - On Windows, build correctly either with or without Unicode support.
23295 This is necessary so that Tor can support fringe platforms like
23296 Windows 98 (which has no Unicode), or Windows CE (which has no
23297 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
23300 - Add a unit test for cross-platform directory-listing code.
23303 Changes in version 0.2.2.15-alpha - 2010-08-18
23304 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
23305 fixes a variety of other bugs that were preventing performance
23306 experiments from moving forward, fixes several bothersome memory leaks,
23307 and generally closes a lot of smaller bugs that have been filling up
23311 - Stop assigning the HSDir flag to relays that disable their
23312 DirPort (and thus will refuse to answer directory requests). This
23313 fix should dramatically improve the reachability of hidden services:
23314 hidden services and hidden service clients pick six HSDir relays
23315 to store and retrieve the hidden service descriptor, and currently
23316 about half of the HSDir relays will refuse to work. Bugfix on
23317 0.2.0.10-alpha; fixes part of bug 1693.
23318 - The PerConnBWRate and Burst config options, along with the
23319 bwconnrate and bwconnburst consensus params, initialized each conn's
23320 token bucket values only when the connection is established. Now we
23321 update them if the config options change, and update them every time
23322 we get a new consensus. Otherwise we can encounter an ugly edge
23323 case where we initialize an OR conn to client-level bandwidth,
23324 but then later the relay joins the consensus and we leave it
23325 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
23326 - Fix a regression that caused Tor to rebind its ports if it receives
23327 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
23330 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23331 should give us approximately 40-50% more Guard-flagged nodes,
23332 improving the anonymity the Tor network can provide and also
23333 decreasing the dropoff in throughput that relays experience when
23334 they first get the Guard flag.
23335 - Allow enabling or disabling the *Statistics config options while
23339 - Update to the August 1 2010 Maxmind GeoLite Country database.
23340 - Have the controller interface give a more useful message than
23341 "Internal Error" in response to failed GETINFO requests.
23342 - Warn when the same option is provided more than once in a torrc
23343 file, on the command line, or in a single SETCONF statement, and
23344 the option is one that only accepts a single line. Closes bug 1384.
23345 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23346 Patch from mingw-san.
23347 - Add support for the country code "{??}" in torrc options like
23348 ExcludeNodes, to indicate all routers of unknown country. Closes
23350 - Relays report the number of bytes spent on answering directory
23351 requests in extra-info descriptors similar to {read,write}-history.
23352 Implements enhancement 1790.
23354 o Minor bugfixes (on 0.2.1.x and earlier):
23355 - Complain if PublishServerDescriptor is given multiple arguments that
23356 include 0 or 1. This configuration will be rejected in the future.
23357 Bugfix on 0.2.0.1-alpha; closes bug 1107.
23358 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
23359 Bugfix on 0.2.0.13-alpha; closes bug 928.
23360 - Change "Application request when we're believed to be offline."
23361 notice to "Application request when we haven't used client
23362 functionality lately.", to clarify that it's not an error. Bugfix
23363 on 0.0.9.3; fixes bug 1222.
23364 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
23365 would return "551 Internal error" rather than "552 Unrecognized key
23366 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
23367 - Users can't configure a regular relay to be their bridge. It didn't
23368 work because when Tor fetched the bridge descriptor, it found
23369 that it already had it, and didn't realize that the purpose of the
23370 descriptor had changed. Now we replace routers with a purpose other
23371 than bridge with bridge descriptors when fetching them. Bugfix on
23372 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
23373 refetch the descriptor with router purpose 'general', disabling
23375 - Fix a rare bug in rend_fn unit tests: we would fail a test when
23376 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
23377 on 0.2.0.10-alpha; fixes bug 1808.
23378 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23379 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23380 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23381 Servers can start sending this code when enough clients recognize
23382 it. Also update the spec to reflect this new reason. Bugfix on
23383 0.1.0.1-rc; fixes part of bug 1793.
23384 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
23385 when we switch from being a public relay to a bridge. Otherwise
23386 there will still be clients that see the relay in their consensus,
23387 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
23389 - Instead of giving an assertion failure on an internal mismatch
23390 on estimated freelist size, just log a BUG warning and try later.
23391 Mitigates but does not fix bug 1125.
23392 - Fix an assertion failure that could occur in caches or bridge users
23393 when using a very short voting interval on a testing network.
23394 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
23396 o Minor bugfixes (on 0.2.2.x):
23397 - Alter directory authorities to always consider Exit-flagged nodes
23398 as potential Guard nodes in their votes. The actual decision to
23399 use Exits as Guards is done in the consensus bandwidth weights.
23400 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
23401 - When the controller is reporting the purpose of circuits that
23402 didn't finish building before the circuit build timeout, it was
23403 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
23404 - Our libevent version parsing code couldn't handle versions like
23405 1.4.14b-stable and incorrectly warned the user about using an
23406 old and broken version of libevent. Treat 1.4.14b-stable like
23407 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
23409 - Don't use substitution references like $(VAR:MOD) when
23410 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
23411 '$(:x)' to 'x' rather than the empty string. This bites us in
23412 doc/ when configured with --disable-asciidoc. Bugfix on
23413 0.2.2.9-alpha; fixes bug 1773.
23414 - Remove a spurious hidden service server-side log notice about
23415 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
23417 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
23419 - Correctly report written bytes on linked connections. Found while
23420 implementing 1790. Bugfix on 0.2.2.4-alpha.
23421 - Fix three memory leaks: one in circuit_build_times_parse_state(),
23422 one in dirvote_add_signatures_to_pending_consensus(), and one every
23423 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
23424 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
23426 o Code simplifications and refactoring:
23427 - Take a first step towards making or.h smaller by splitting out
23428 function definitions for all source files in src/or/. Leave
23429 structures and defines in or.h for now.
23430 - Remove a bunch of unused function declarations as well as a block of
23431 #if 0'd code from the unit tests. Closes bug 1824.
23432 - New unit tests for exit-port history statistics; refactored exit
23433 statistics code to be more easily tested.
23434 - Remove the old debian/ directory from the main Tor distribution.
23435 The official Tor-for-debian git repository lives at the URL
23436 https://git.torproject.org/debian/tor.git
23439 Changes in version 0.2.2.14-alpha - 2010-07-12
23440 Tor 0.2.2.14-alpha greatly improves client-side handling of
23441 circuit build timeouts, which are used to estimate speed and improve
23442 performance. We also move to a much better GeoIP database, port Tor to
23443 Windows CE, introduce new compile flags that improve code security,
23444 add an eighth v3 directory authority, and address a lot of more
23448 - Tor directory authorities no longer crash when started with a
23449 cached-microdesc-consensus file in their data directory. Bugfix
23450 on 0.2.2.6-alpha; fixes bug 1532.
23451 - Treat an unset $HOME like an empty $HOME rather than triggering an
23452 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
23453 - Ignore negative and large circuit build timeout values that can
23454 happen during a suspend or hibernate. These values caused various
23455 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
23456 - Alter calculation of Pareto distribution parameter 'Xm' for
23457 Circuit Build Timeout learning to use the weighted average of the
23458 top N=3 modes (because we have three entry guards). Considering
23459 multiple modes should improve the timeout calculation in some cases,
23460 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
23462 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
23463 right censored distribution model. This approach improves over the
23464 synthetic timeout generation approach that was producing insanely
23465 high timeout values. Now we calculate build timeouts using truncated
23466 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
23467 - Do not close circuits that are under construction when they reach
23468 the circuit build timeout. Instead, leave them building (but do not
23469 use them) for up until the time corresponding to the 95th percentile
23470 on the Pareto CDF or 60 seconds, whichever is greater. This is done
23471 to provide better data for the new Pareto model. This percentile
23472 can be controlled by the consensus.
23475 - Move to the June 2010 Maxmind GeoLite country db (rather than the
23476 June 2009 ip-to-country GeoIP db) for our statistics that count
23477 how many users relays are seeing from each country. Now we have
23478 more accurate data for many African countries.
23479 - Port Tor to build and run correctly on Windows CE systems, using
23480 the wcecompat library. Contributed by Valerio Lupi.
23481 - New "--enable-gcc-hardening" ./configure flag (off by default)
23482 to turn on gcc compile time hardening options. It ensures
23483 that signed ints have defined behavior (-fwrapv), enables
23484 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
23485 with canaries (-fstack-protector-all), turns on ASLR protection if
23486 supported by the kernel (-fPIE, -pie), and adds additional security
23487 related warnings. Verified to work on Mac OS X and Debian Lenny.
23488 - New "--enable-linker-hardening" ./configure flag (off by default)
23489 to turn on ELF specific hardening features (relro, now). This does
23490 not work with Mac OS X or any other non-ELF binary format.
23492 o New directory authorities:
23493 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23497 - New config option "WarnUnsafeSocks 0" disables the warning that
23498 occurs whenever Tor receives a socks handshake using a version of
23499 the socks protocol that can only provide an IP address (rather
23500 than a hostname). Setups that do DNS locally over Tor are fine,
23501 and we shouldn't spam the logs in that case.
23502 - Convert the HACKING file to asciidoc, and add a few new sections
23503 to it, explaining how we use Git, how we make changelogs, and
23504 what should go in a patch.
23505 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
23506 event, to give information on the current rate of circuit timeouts
23507 over our stored history.
23508 - Add ability to disable circuit build time learning via consensus
23509 parameter and via a LearnCircuitBuildTimeout config option. Also
23510 automatically disable circuit build time calculation if we are
23511 either a AuthoritativeDirectory, or if we fail to write our state
23512 file. Fixes bug 1296.
23513 - More gracefully handle corrupt state files, removing asserts
23514 in favor of saving a backup and resetting state.
23515 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
23519 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23521 - When a2x fails, mention that the user could disable manpages instead
23522 of trying to fix their asciidoc installation.
23523 - Where available, use Libevent 2.0's periodic timers so that our
23524 once-per-second cleanup code gets called even more closely to
23525 once per second than it would otherwise. Fixes bug 943.
23526 - If you run a bridge that listens on multiple IP addresses, and
23527 some user configures a bridge address that uses a different IP
23528 address than your bridge writes in its router descriptor, and the
23529 user doesn't specify an identity key, their Tor would discard the
23530 descriptor because "it isn't one of our configured bridges", and
23531 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
23532 Bugfix on 0.2.0.3-alpha.
23533 - If OpenSSL fails to make a duplicate of a private or public key, log
23534 an error message and try to exit cleanly. May help with debugging
23535 if bug 1209 ever remanifests.
23536 - Save a couple bytes in memory allocation every time we escape
23537 certain characters in a string. Patch from Florian Zumbiehl.
23538 - Make it explicit that we don't cannibalize one-hop circuits. This
23539 happens in the wild, but doesn't turn out to be a problem because
23540 we fortunately don't use those circuits. Many thanks to outofwords
23541 for the initial analysis and to swissknife who confirmed that
23542 two-hop circuits are actually created.
23543 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
23544 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
23545 - Eliminate a case where a circuit build time warning was displayed
23546 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
23549 Changes in version 0.2.1.26 - 2010-05-02
23550 Tor 0.2.1.26 addresses the recent connection and memory overload
23551 problems we've been seeing on relays, especially relays with their
23552 DirPort open. If your relay has been crashing, or you turned it off
23553 because it used too many resources, give this release a try.
23555 This release also fixes yet another instance of broken OpenSSL libraries
23556 that was causing some relays to drop out of the consensus.
23559 - Teach relays to defend themselves from connection overload. Relays
23560 now close idle circuits early if it looks like they were intended
23561 for directory fetches. Relays are also more aggressive about closing
23562 TLS connections that have no circuits on them. Such circuits are
23563 unlikely to be re-used, and tens of thousands of them were piling
23564 up at the fast relays, causing the relays to run out of sockets
23565 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23566 their directory fetches over TLS).
23567 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23568 that claim to be earlier than 0.9.8m, but which have in reality
23569 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23570 behavior. Possible fix for some cases of bug 1346.
23571 - Directory mirrors were fetching relay descriptors only from v2
23572 directory authorities, rather than v3 authorities like they should.
23573 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23574 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23577 - Finally get rid of the deprecated and now harmful notion of "clique
23578 mode", where directory authorities maintain TLS connections to
23582 - In the util/threads test, no longer free the test_mutex before all
23583 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23584 - The master thread could starve the worker threads quite badly on
23585 certain systems, causing them to run only partially in the allowed
23586 window. This resulted in test failures. Now the master thread sleeps
23587 occasionally for a few microseconds while the two worker-threads
23588 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23591 Changes in version 0.2.2.13-alpha - 2010-04-24
23592 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
23593 problems we've been seeing on relays, especially relays with their
23594 DirPort open. If your relay has been crashing, or you turned it off
23595 because it used too many resources, give this release a try.
23598 - Teach relays to defend themselves from connection overload. Relays
23599 now close idle circuits early if it looks like they were intended
23600 for directory fetches. Relays are also more aggressive about closing
23601 TLS connections that have no circuits on them. Such circuits are
23602 unlikely to be re-used, and tens of thousands of them were piling
23603 up at the fast relays, causing the relays to run out of sockets
23604 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23605 their directory fetches over TLS).
23608 - Finally get rid of the deprecated and now harmful notion of "clique
23609 mode", where directory authorities maintain TLS connections to
23611 - Directory authorities now do an immediate reachability check as soon
23612 as they hear about a new relay. This change should slightly reduce
23613 the time between setting up a relay and getting listed as running
23614 in the consensus. It should also improve the time between setting
23615 up a bridge and seeing use by bridge users.
23616 - Directory authorities no longer launch a TLS connection to every
23617 relay as they startup. Now that we have 2k+ descriptors cached,
23618 the resulting network hiccup is becoming a burden. Besides,
23619 authorities already avoid voting about Running for the first half
23620 hour of their uptime.
23623 Changes in version 0.2.2.12-alpha - 2010-04-20
23624 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
23625 handle and vote on descriptors. It was causing relays to drop out of
23629 - Many relays have been falling out of the consensus lately because
23630 not enough authorities know about their descriptor for them to get
23631 a majority of votes. When we deprecated the v2 directory protocol,
23632 we got rid of the only way that v3 authorities can hear from each
23633 other about other descriptors. Now authorities examine every v3
23634 vote for new descriptors, and fetch them from that authority. Bugfix
23636 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
23637 and a warning in or.h related to bandwidth_weight_rule_t that
23638 prevented clean compile on OS X. Fixes bug 1363; bugfix on
23640 - Fix a segfault on relays when DirReqStatistics is enabled
23641 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
23645 - Demote a confusing TLS warning that relay operators might get when
23646 someone tries to talk to their OrPort. It is neither the operator's
23647 fault nor can they do anything about it. Fixes bug 1364; bugfix
23651 Changes in version 0.2.2.11-alpha - 2010-04-15
23652 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
23653 libraries that was causing some relays to drop out of the consensus.
23656 - Directory mirrors were fetching relay descriptors only from v2
23657 directory authorities, rather than v3 authorities like they should.
23658 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23659 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23660 - Fix a parsing error that made every possible value of
23661 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
23662 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
23663 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
23664 about the option without breaking older ones.
23665 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23666 that claim to be earlier than 0.9.8m, but which have in reality
23667 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23668 behavior. Possible fix for some cases of bug 1346.
23671 - Experiment with a more aggressive approach to preventing clients
23672 from making one-hop exit streams. Exit relays who want to try it
23673 out can set "RefuseUnknownExits 1" in their torrc, and then look
23674 for "Attempt by %s to open a stream" log messages. Let us know
23676 - Add support for statically linking zlib by specifying
23677 --enable-static-zlib, to go with our support for statically linking
23678 openssl and libevent. Resolves bug 1358.
23681 - Fix a segfault that happens whenever a Tor client that is using
23682 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
23684 - When we cleaned up the contrib/tor-exit-notice.html file, we left
23685 out the first line. Fixes bug 1295.
23686 - When building the manpage from a tarball, we required asciidoc, but
23687 the asciidoc -> roff/html conversion was already done for the
23688 tarball. Make 'make' complain only when we need asciidoc (either
23689 because we're compiling directly from git, or because we altered
23690 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
23691 - When none of the directory authorities vote on any params, Tor
23692 segfaulted when trying to make the consensus from the votes. We
23693 didn't trigger the bug in practice, because authorities do include
23694 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
23697 - In the util/threads test, no longer free the test_mutex before all
23698 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23699 - The master thread could starve the worker threads quite badly on
23700 certain systems, causing them to run only partially in the allowed
23701 window. This resulted in test failures. Now the master thread sleeps
23702 occasionally for a few microseconds while the two worker-threads
23703 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23706 Changes in version 0.2.2.10-alpha - 2010-03-07
23707 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
23708 could prevent relays from guessing their IP address correctly. It also
23709 starts the groundwork for another client-side performance boost, since
23710 currently we're not making efficient use of relays that have both the
23711 Guard flag and the Exit flag.
23714 - Fix a regression from our patch for bug 1244 that caused relays
23715 to guess their IP address incorrectly if they didn't set Address
23716 in their torrc and/or their address fails to resolve. Bugfix on
23717 0.2.2.9-alpha; fixes bug 1269.
23719 o Major features (performance):
23720 - Directory authorities now compute consensus weightings that instruct
23721 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23722 and no flag. Clients that use these weightings will distribute
23723 network load more evenly across these different relay types. The
23724 weightings are in the consensus so we can change them globally in
23725 the future. Extra thanks to "outofwords" for finding some nasty
23726 security bugs in the first implementation of this feature.
23728 o Minor features (performance):
23729 - Always perform router selections using weighted relay bandwidth,
23730 even if we don't need a high capacity circuit at the time. Non-fast
23731 circuits now only differ from fast ones in that they can use relays
23732 not marked with the Fast flag. This "feature" could turn out to
23733 be a horrible bug; we should investigate more before it goes into
23737 - Allow disabling building of the manpages. Skipping the manpage
23738 speeds up the build considerably.
23740 o Minor bugfixes (on 0.2.2.x):
23741 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23742 Bugfix on 0.2.2.9-alpha.
23743 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23744 config option. Bugfix on 0.2.2.7-alpha.
23745 - Ship the asciidoc-helper file in the tarball, so that people can
23746 build from source if they want to, and touching the .1.txt files
23747 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23749 o Minor bugfixes (on 0.2.1.x or earlier):
23750 - Fix a dereference-then-NULL-check sequence when publishing
23751 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23753 - Fix another dereference-then-NULL-check sequence. Bugfix on
23754 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23755 - Make sure we treat potentially not NUL-terminated strings correctly.
23756 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23758 o Code simplifications and refactoring:
23759 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23760 compliant. Based on a patch from Christian Kujau.
23761 - Don't use sed in asciidoc-helper anymore.
23762 - Make the build process fail if asciidoc cannot be found and
23763 building with asciidoc isn't disabled.
23766 Changes in version 0.2.2.9-alpha - 2010-02-22
23767 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23768 location of a directory authority, and cleans up a bunch of small bugs.
23770 o Directory authority changes:
23771 - Change IP address for dannenberg (v3 directory authority), and
23772 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23773 service directory authority) from the list.
23776 - Make Tor work again on the latest OS X: when deciding whether to
23777 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23778 version at run-time, not compile time. We need to do this because
23779 Apple doesn't update its dev-tools headers when it updates its
23780 libraries in a security patch.
23781 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23782 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23783 a memory leak when requesting a hidden service descriptor we've
23784 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23786 - Authorities could be tricked into giving out the Exit flag to relays
23787 that didn't allow exiting to any ports. This bug could screw
23788 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23789 1238. Bug discovered by Martin Kowalczyk.
23790 - When freeing a session key, zero it out completely. We only zeroed
23791 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23792 patched by ekir. Fixes bug 1254.
23795 - Fix static compilation by listing the openssl libraries in the right
23796 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23797 - Resume handling .exit hostnames in a special way: originally we
23798 stripped the .exit part and used the requested exit relay. In
23799 0.2.2.1-alpha we stopped treating them in any special way, meaning
23800 if you use a .exit address then Tor will pass it on to the exit
23801 relay. Now we reject the .exit stream outright, since that behavior
23802 might be more expected by the user. Found and diagnosed by Scott
23803 Bennett and Downie on or-talk.
23804 - Don't spam the controller with events when we have no file
23805 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23806 for log messages was already solved from bug 748.)
23807 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23809 - Make the DNSPort option work with libevent 2.x. Don't alter the
23810 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23811 - Emit a GUARD DROPPED controller event for a case we missed.
23812 - Make more fields in the controller protocol case-insensitive, since
23813 control-spec.txt said they were.
23814 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23815 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23816 - Fix a spec conformance issue: the network-status-version token
23817 must be the first token in a v3 consensus or vote. Discovered by
23818 parakeep. Bugfix on 0.2.0.3-alpha.
23820 o Code simplifications and refactoring:
23821 - Generate our manpage and HTML documentation using Asciidoc. This
23822 change should make it easier to maintain the documentation, and
23823 produce nicer HTML.
23824 - Remove the --enable-iphone option. According to reports from Marco
23825 Bonetti, Tor builds fine without any special tweaking on recent
23826 iPhone SDK versions.
23827 - Removed some unnecessary files from the source distribution. The
23828 AUTHORS file has now been merged into the people page on the
23829 website. The roadmaps and design doc can now be found in the
23830 projects directory in svn.
23831 - Enabled various circuit build timeout constants to be controlled
23832 by consensus parameters. Also set better defaults for these
23833 parameters based on experimentation on broadband and simulated
23834 high latency links.
23837 - The 'EXTENDCIRCUIT' control port command can now be used with
23838 a circ id of 0 and no path. This feature will cause Tor to build
23839 a new 'fast' general purpose circuit using its own path selection
23841 - Added a BUILDTIMEOUT_SET controller event to describe changes
23842 to the circuit build timeout.
23843 - Future-proof the controller protocol a bit by ignoring keyword
23844 arguments we do not recognize.
23845 - Expand homedirs passed to tor-checkkey. This should silence a
23846 coverity complaint about passing a user-supplied string into
23847 open() without checking it.
23850 Changes in version 0.2.1.25 - 2010-03-16
23851 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23852 prevent relays from guessing their IP address correctly. It also fixes
23853 several minor potential security bugs.
23856 - Fix a regression from our patch for bug 1244 that caused relays
23857 to guess their IP address incorrectly if they didn't set Address
23858 in their torrc and/or their address fails to resolve. Bugfix on
23859 0.2.1.23; fixes bug 1269.
23860 - When freeing a session key, zero it out completely. We only zeroed
23861 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23862 patched by ekir. Fixes bug 1254.
23865 - Fix a dereference-then-NULL-check sequence when publishing
23866 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23868 - Fix another dereference-then-NULL-check sequence. Bugfix on
23869 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23870 - Make sure we treat potentially not NUL-terminated strings correctly.
23871 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23875 Changes in version 0.2.1.24 - 2010-02-21
23876 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23880 - Work correctly out-of-the-box with even more vendor-patched versions
23881 of OpenSSL. In particular, make it so Debian and OS X don't need
23882 customized patches to run/build.
23885 Changes in version 0.2.1.23 - 2010-02-13
23886 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23887 again on the latest OS X, and updates the location of a directory
23890 o Major bugfixes (performance):
23891 - We were selecting our guards uniformly at random, and then weighting
23892 which of our guards we'd use uniformly at random. This imbalance
23893 meant that Tor clients were severely limited on throughput (and
23894 probably latency too) by the first hop in their circuit. Now we
23895 select guards weighted by currently advertised bandwidth. We also
23896 automatically discard guards picked using the old algorithm. Fixes
23897 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23900 - Make Tor work again on the latest OS X: when deciding whether to
23901 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23902 version at run-time, not compile time. We need to do this because
23903 Apple doesn't update its dev-tools headers when it updates its
23904 libraries in a security patch.
23905 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23906 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23907 a memory leak when requesting a hidden service descriptor we've
23908 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23911 o Directory authority changes:
23912 - Change IP address for dannenberg (v3 directory authority), and
23913 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23914 service directory authority) from the list.
23917 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23918 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23921 - Avoid a mad rush at the beginning of each month when each client
23922 rotates half of its guards. Instead we spread the rotation out
23923 throughout the month, but we still avoid leaving a precise timestamp
23924 in the state file about when we first picked the guard. Improves
23925 over the behavior introduced in 0.1.2.17.
23928 Changes in version 0.2.2.8-alpha - 2010-01-26
23929 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
23930 causing bridge relays to disappear. If you're running a bridge,
23934 - Fix a memory corruption bug on bridges that occurred during the
23935 inclusion of stats data in extra-info descriptors. Also fix the
23936 interface for geoip_get_bridge_stats* to prevent similar bugs in
23937 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
23938 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
23941 - Ignore OutboundBindAddress when connecting to localhost.
23942 Connections to localhost need to come _from_ localhost, or else
23943 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
23947 Changes in version 0.2.2.7-alpha - 2010-01-19
23948 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
23949 as laying the groundwork for further relay-side performance fixes. It
23950 also starts cleaning up client behavior with respect to the EntryNodes,
23951 ExitNodes, and StrictNodes config options.
23953 This release also rotates two directory authority keys, due to a
23954 security breach of some of the Torproject servers.
23956 o Directory authority changes:
23957 - Rotate keys (both v3 identity and relay identity) for moria1
23960 o Major features (performance):
23961 - We were selecting our guards uniformly at random, and then weighting
23962 which of our guards we'd use uniformly at random. This imbalance
23963 meant that Tor clients were severely limited on throughput (and
23964 probably latency too) by the first hop in their circuit. Now we
23965 select guards weighted by currently advertised bandwidth. We also
23966 automatically discard guards picked using the old algorithm. Fixes
23967 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23968 - When choosing which cells to relay first, relays can now favor
23969 circuits that have been quiet recently, to provide lower latency
23970 for low-volume circuits. By default, relays enable or disable this
23971 feature based on a setting in the consensus. You can override
23972 this default by using the new "CircuitPriorityHalflife" config
23973 option. Design and code by Ian Goldberg, Can Tang, and Chris
23975 - Add separate per-conn write limiting to go with the per-conn read
23976 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
23977 but never per-conn write limits.
23978 - New consensus params "bwconnrate" and "bwconnburst" to let us
23979 rate-limit client connections as they enter the network. It's
23980 controlled in the consensus so we can turn it on and off for
23981 experiments. It's starting out off. Based on proposal 163.
23983 o Major features (relay selection options):
23984 - Switch to a StrictNodes config option, rather than the previous
23985 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
23986 "StrictExcludeNodes" option.
23987 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
23988 change during a config reload, mark and discard all our origin
23989 circuits. This fix should address edge cases where we change the
23990 config options and but then choose a circuit that we created before
23992 - If EntryNodes or ExitNodes are set, be more willing to use an
23993 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
23995 - Make EntryNodes config option much more aggressive even when
23996 StrictNodes is not set. Before it would prepend your requested
23997 entrynodes to your list of guard nodes, but feel free to use others
23998 after that. Now it chooses only from your EntryNodes if any of
23999 those are available, and only falls back to others if a) they're
24000 all down and b) StrictNodes is not set.
24001 - Now we refresh your entry guards from EntryNodes at each consensus
24002 fetch -- rather than just at startup and then they slowly rot as
24003 the network changes.
24006 - Stop bridge directory authorities from answering dbg-stability.txt
24007 directory queries, which would let people fetch a list of all
24008 bridge identities they track. Bugfix on 0.2.1.6-alpha.
24011 - Log a notice when we get a new control connection. Now it's easier
24012 for security-conscious users to recognize when a local application
24013 is knocking on their controller door. Suggested by bug 1196.
24014 - New config option "CircuitStreamTimeout" to override our internal
24015 timeout schedule for how many seconds until we detach a stream from
24016 a circuit and try a new circuit. If your network is particularly
24017 slow, you might want to set this to a number like 60.
24018 - New controller command "getinfo config-text". It returns the
24019 contents that Tor would write if you send it a SAVECONF command,
24020 so the controller can write the file to disk itself.
24021 - New options for SafeLogging to allow scrubbing only log messages
24022 generated while acting as a relay.
24023 - Ship the bridges spec file in the tarball too.
24024 - Avoid a mad rush at the beginning of each month when each client
24025 rotates half of its guards. Instead we spread the rotation out
24026 throughout the month, but we still avoid leaving a precise timestamp
24027 in the state file about when we first picked the guard. Improves
24028 over the behavior introduced in 0.1.2.17.
24030 o Minor bugfixes (compiling):
24031 - Fix compilation on OS X 10.3, which has a stub mlockall() but
24032 hides it. Bugfix on 0.2.2.6-alpha.
24033 - Fix compilation on Solaris by removing support for the
24034 DisableAllSwap config option. Solaris doesn't have an rlimit for
24035 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
24038 o Minor bugfixes (crashes):
24039 - Do not segfault when writing buffer stats when we haven't observed
24040 a single circuit to report about. Found by Fabian Lanze. Bugfix on
24042 - If we're in the pathological case where there's no exit bandwidth
24043 but there is non-exit bandwidth, or no guard bandwidth but there
24044 is non-guard bandwidth, don't crash during path selection. Bugfix
24046 - Fix an impossible-to-actually-trigger buffer overflow in relay
24047 descriptor generation. Bugfix on 0.1.0.15.
24049 o Minor bugfixes (privacy):
24050 - Fix an instance where a Tor directory mirror might accidentally
24051 log the IP address of a misbehaving Tor client. Bugfix on
24053 - Don't list Windows capabilities in relay descriptors. We never made
24054 use of them, and maybe it's a bad idea to publish them. Bugfix
24057 o Minor bugfixes (other):
24058 - Resolve an edge case in path weighting that could make us misweight
24059 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
24060 - Fix statistics on client numbers by country as seen by bridges that
24061 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
24062 intervals instead of variable 12-to-48-hour intervals.
24063 - After we free an internal connection structure, overwrite it
24064 with a different memory value than we use for overwriting a freed
24065 internal circuit structure. Should help with debugging. Suggested
24067 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
24070 o Removed features:
24071 - Remove the HSAuthorityRecordStats option that version 0 hidden
24072 service authorities could have used to track statistics of overall
24073 hidden service usage.
24076 Changes in version 0.2.1.22 - 2010-01-19
24077 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
24078 authorities -- it would tell you its whole history of bridge descriptors
24079 if you make the right directory request. This stable update also
24080 rotates two of the seven v3 directory authority keys and locations.
24082 o Directory authority changes:
24083 - Rotate keys (both v3 identity and relay identity) for moria1
24087 - Stop bridge directory authorities from answering dbg-stability.txt
24088 directory queries, which would let people fetch a list of all
24089 bridge identities they track. Bugfix on 0.2.1.6-alpha.
24092 Changes in version 0.2.1.21 - 2009-12-21
24093 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
24094 library. If you use Tor on Linux / Unix and you're getting SSL
24095 renegotiation errors, upgrading should help. We also recommend an
24096 upgrade if you're an exit relay.
24099 - Work around a security feature in OpenSSL 0.9.8l that prevents our
24100 handshake from working unless we explicitly tell OpenSSL that we
24101 are using SSL renegotiation safely. We are, of course, but OpenSSL
24102 0.9.8l won't work unless we say we are.
24103 - Avoid crashing if the client is trying to upload many bytes and the
24104 circuit gets torn down at the same time, or if the flip side
24105 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
24108 - Do not refuse to learn about authority certs and v2 networkstatus
24109 documents that are older than the latest consensus. This bug might
24110 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
24111 Spotted and fixed by xmux.
24112 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
24113 trigger platform-specific option misparsing case found by Coverity
24115 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
24116 trigger assert. Fixes bug 1173.
24119 Changes in version 0.2.2.6-alpha - 2009-11-19
24120 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
24121 support for the new lower-footprint "microdescriptor" directory design,
24122 future-proofing our consensus format against new hash functions or
24123 other changes, and an Android port. It also makes Tor compatible with
24124 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
24127 - Directory authorities can now create, vote on, and serve multiple
24128 parallel formats of directory data as part of their voting process.
24129 Partially implements Proposal 162: "Publish the consensus in
24131 - Directory authorities can now agree on and publish small summaries
24132 of router information that clients can use in place of regular
24133 server descriptors. This transition will eventually allow clients
24134 to use far less bandwidth for downloading information about the
24135 network. Begins the implementation of Proposal 158: "Clients
24136 download consensus + microdescriptors".
24137 - The directory voting system is now extensible to use multiple hash
24138 algorithms for signatures and resource selection. Newer formats
24139 are signed with SHA256, with a possibility for moving to a better
24140 hash algorithm in the future.
24141 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
24142 current and future memory pages via mlockall(). On supported
24143 platforms (modern Linux and probably BSD but not Windows or OS X),
24144 this should effectively disable any and all attempts to page out
24145 memory. This option requires that you start your Tor as root --
24146 if you use DisableAllSwap, please consider using the User option
24147 to properly reduce the privileges of your Tor.
24148 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
24149 to help Tor build correctly for Android phones.
24152 - Work around a security feature in OpenSSL 0.9.8l that prevents our
24153 handshake from working unless we explicitly tell OpenSSL that we
24154 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
24155 won't work unless we say we are.
24158 - Fix a crash bug when trying to initialize the evdns module in
24159 Libevent 2. Bugfix on 0.2.1.16-rc.
24160 - Stop logging at severity 'warn' when some other Tor client tries
24161 to establish a circuit with us using weak DH keys. It's a protocol
24162 violation, but that doesn't mean ordinary users need to hear about
24163 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
24164 - Do not refuse to learn about authority certs and v2 networkstatus
24165 documents that are older than the latest consensus. This bug might
24166 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
24167 Spotted and fixed by xmux.
24168 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
24169 - If all authorities restart at once right before a consensus vote,
24170 nobody will vote about "Running", and clients will get a consensus
24171 with no usable relays. Instead, authorities refuse to build a
24172 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
24173 - If your relay can't keep up with the number of incoming create
24174 cells, it would log one warning per failure into your logs. Limit
24175 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
24176 - Bridges now use "reject *:*" as their default exit policy. Bugfix
24177 on 0.2.0.3-alpha; fixes bug 1113.
24178 - Fix a memory leak on directory authorities during voting that was
24179 introduced in 0.2.2.1-alpha. Found via valgrind.
24182 Changes in version 0.2.1.20 - 2009-10-15
24183 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
24184 services at once, prepares for more performance improvements, and
24185 fixes a bunch of smaller bugs.
24187 The Windows and OS X bundles also include a more recent Vidalia,
24188 and switch from Privoxy to Polipo.
24190 The OS X installers are now drag and drop. It's best to un-install
24191 Tor/Vidalia and then install this new bundle, rather than upgrade. If
24192 you want to upgrade, you'll need to update the paths for Tor and Polipo
24193 in the Vidalia Settings window.
24196 - Send circuit or stream sendme cells when our window has decreased
24197 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24198 by Karsten when testing the "reduce circuit window" performance
24199 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24200 before the release of Tor 0.0.0. This is the new winner of the
24202 - Fix a remotely triggerable memory leak when a consensus document
24203 contains more than one signature from the same voter. Bugfix on
24205 - Avoid segfault in rare cases when finishing an introduction circuit
24206 as a client and finding out that we don't have an introduction key
24207 for it. Fixes bug 1073. Reported by Aaron Swartz.
24210 - Tor now reads the "circwindow" parameter out of the consensus,
24211 and uses that value for its circuit package window rather than the
24212 default of 1000 cells. Begins the implementation of proposal 168.
24214 o New directory authorities:
24215 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24217 - Move moria1 and tonga to alternate IP addresses.
24220 - Fix a signed/unsigned compile warning in 0.2.1.19.
24221 - Fix possible segmentation fault on directory authorities. Bugfix on
24223 - Fix an extremely rare infinite recursion bug that could occur if
24224 we tried to log a message after shutting down the log subsystem.
24225 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24226 - Fix an obscure bug where hidden services on 64-bit big-endian
24227 systems might mis-read the timestamp in v3 introduce cells, and
24228 refuse to connect back to the client. Discovered by "rotor".
24229 Bugfix on 0.2.1.6-alpha.
24230 - We were triggering a CLOCK_SKEW controller status event whenever
24231 we connect via the v2 connection protocol to any relay that has
24232 a wrong clock. Instead, we should only inform the controller when
24233 it's a trusted authority that claims our clock is wrong. Bugfix
24234 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24235 - We were telling the controller about CHECKING_REACHABILITY and
24236 REACHABILITY_FAILED status events whenever we launch a testing
24237 circuit or notice that one has failed. Instead, only tell the
24238 controller when we want to inform the user of overall success or
24239 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24241 - Don't warn when we're using a circuit that ends with a node
24242 excluded in ExcludeExitNodes, but the circuit is not used to access
24243 the outside world. This should help fix bug 1090. Bugfix on
24245 - Work around a small memory leak in some versions of OpenSSL that
24246 stopped the memory used by the hostname TLS extension from being
24250 - Add a "getinfo status/accepted-server-descriptor" controller
24251 command, which is the recommended way for controllers to learn
24252 whether our server descriptor has been successfully received by at
24253 least on directory authority. Un-recommend good-server-descriptor
24254 getinfo and status events until we have a better design for them.
24257 Changes in version 0.2.2.5-alpha - 2009-10-11
24258 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
24261 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
24263 o Directory authorities:
24264 - Temporarily (just for this release) move dizum to an alternate
24268 Changes in version 0.2.2.4-alpha - 2009-10-10
24269 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
24270 introduces a new unit test framework, shifts directry authority
24271 addresses around to reduce the impact from recent blocking events,
24272 and fixes a few smaller bugs.
24275 - Fix several more asserts in the circuit_build_times code, for
24276 example one that causes Tor to fail to start once we have
24277 accumulated 5000 build times in the state file. Bugfixes on
24278 0.2.2.2-alpha; fixes bug 1108.
24280 o New directory authorities:
24281 - Move moria1 and Tonga to alternate IP addresses.
24284 - Log SSL state transitions at debug level during handshake, and
24285 include SSL states in error messages. This may help debug future
24286 SSL handshake issues.
24287 - Add a new "Handshake" log domain for activities that happen
24288 during the TLS handshake.
24289 - Revert to the "June 3 2009" ip-to-country file. The September one
24290 seems to have removed most US IP addresses.
24291 - Directory authorities now reject Tor relays with versions less than
24292 0.1.2.14. This step cuts out four relays from the current network,
24293 none of which are very big.
24296 - Fix a couple of smaller issues with gathering statistics. Bugfixes
24298 - Fix two memory leaks in the error case of
24299 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
24300 - Don't count one-hop circuits when we're estimating how long it
24301 takes circuits to build on average. Otherwise we'll set our circuit
24302 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
24303 - Directory authorities no longer change their opinion of, or vote on,
24304 whether a router is Running, unless they have themselves been
24305 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
24308 o Code simplifications and refactoring:
24309 - Revise our unit tests to use the "tinytest" framework, so we
24310 can run tests in their own processes, have smarter setup/teardown
24311 code, and so on. The unit test code has moved to its own
24312 subdirectory, and has been split into multiple modules.
24315 Changes in version 0.2.2.3-alpha - 2009-09-23
24316 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
24319 - Fix an overzealous assert in our new circuit build timeout code.
24320 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
24323 - If the networkstatus consensus tells us that we should use a
24324 negative circuit package window, ignore it. Otherwise we'll
24325 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
24328 Changes in version 0.2.2.2-alpha - 2009-09-21
24329 Tor 0.2.2.2-alpha introduces our latest performance improvement for
24330 clients: Tor tracks the average time it takes to build a circuit, and
24331 avoids using circuits that take too long to build. For fast connections,
24332 this feature can cut your expected latency in half. For slow or flaky
24333 connections, it could ruin your Tor experience. Let us know if it does!
24336 - Tor now tracks how long it takes to build client-side circuits
24337 over time, and adapts its timeout to local network performance.
24338 Since a circuit that takes a long time to build will also provide
24339 bad performance, we get significant latency improvements by
24340 discarding the slowest 20% of circuits. Specifically, Tor creates
24341 circuits more aggressively than usual until it has enough data
24342 points for a good timeout estimate. Implements proposal 151.
24343 We are especially looking for reports (good and bad) from users with
24344 both EDGE and broadband connections that can move from broadband
24345 to EDGE and find out if the build-time data in the .tor/state gets
24346 reset without loss of Tor usability. You should also see a notice
24347 log message telling you that Tor has reset its timeout.
24348 - Directory authorities can now vote on arbitrary integer values as
24349 part of the consensus process. This is designed to help set
24350 network-wide parameters. Implements proposal 167.
24351 - Tor now reads the "circwindow" parameter out of the consensus,
24352 and uses that value for its circuit package window rather than the
24353 default of 1000 cells. Begins the implementation of proposal 168.
24356 - Fix a remotely triggerable memory leak when a consensus document
24357 contains more than one signature from the same voter. Bugfix on
24361 - Fix an extremely rare infinite recursion bug that could occur if
24362 we tried to log a message after shutting down the log subsystem.
24363 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24364 - Fix parsing for memory or time units given without a space between
24365 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
24366 - A networkstatus vote must contain exactly one signature. Spec
24367 conformance issue. Bugfix on 0.2.0.3-alpha.
24368 - Fix an obscure bug where hidden services on 64-bit big-endian
24369 systems might mis-read the timestamp in v3 introduce cells, and
24370 refuse to connect back to the client. Discovered by "rotor".
24371 Bugfix on 0.2.1.6-alpha.
24372 - We were triggering a CLOCK_SKEW controller status event whenever
24373 we connect via the v2 connection protocol to any relay that has
24374 a wrong clock. Instead, we should only inform the controller when
24375 it's a trusted authority that claims our clock is wrong. Bugfix
24376 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24377 - We were telling the controller about CHECKING_REACHABILITY and
24378 REACHABILITY_FAILED status events whenever we launch a testing
24379 circuit or notice that one has failed. Instead, only tell the
24380 controller when we want to inform the user of overall success or
24381 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24383 - Don't warn when we're using a circuit that ends with a node
24384 excluded in ExcludeExitNodes, but the circuit is not used to access
24385 the outside world. This should help fix bug 1090, but more problems
24386 remain. Bugfix on 0.2.1.6-alpha.
24387 - Work around a small memory leak in some versions of OpenSSL that
24388 stopped the memory used by the hostname TLS extension from being
24390 - Make our 'torify' script more portable; if we have only one of
24391 'torsocks' or 'tsocks' installed, don't complain to the user;
24392 and explain our warning about tsocks better.
24395 - Add a "getinfo status/accepted-server-descriptor" controller
24396 command, which is the recommended way for controllers to learn
24397 whether our server descriptor has been successfully received by at
24398 least on directory authority. Un-recommend good-server-descriptor
24399 getinfo and status events until we have a better design for them.
24400 - Update to the "September 4 2009" ip-to-country file.
24403 Changes in version 0.2.2.1-alpha - 2009-08-26
24404 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
24405 Tor clients to bootstrap on networks where only port 80 is reachable,
24406 makes it more straightforward to support hardware crypto accelerators,
24407 and starts the groundwork for gathering stats safely at relays.
24410 - Start the process of disabling ".exit" address notation, since it
24411 can be used for a variety of esoteric application-level attacks
24412 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
24415 o New directory authorities:
24416 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24420 - New AccelName and AccelDir options add support for dynamic OpenSSL
24421 hardware crypto acceleration engines.
24422 - Tor now supports tunneling all of its outgoing connections over
24423 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
24424 configuration options. Code by Christopher Davis.
24427 - Send circuit or stream sendme cells when our window has decreased
24428 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24429 by Karsten when testing the "reduce circuit window" performance
24430 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24431 before the release of Tor 0.0.0. This is the new winner of the
24434 o New options for gathering stats safely:
24435 - Directory mirrors that set "DirReqStatistics 1" write statistics
24436 about directory requests to disk every 24 hours. As compared to the
24437 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
24438 1) stats are written to disk exactly every 24 hours; 2) estimated
24439 shares of v2 and v3 requests are determined as mean values, not at
24440 the end of a measurement period; 3) unresolved requests are listed
24441 with country code '??'; 4) directories also measure download times.
24442 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
24443 number of exit streams and transferred bytes per port to disk every
24445 - Relays that set "CellStatistics 1" write statistics on how long
24446 cells spend in their circuit queues to disk every 24 hours.
24447 - Entry nodes that set "EntryStatistics 1" write statistics on the
24448 rough number and origins of connecting clients to disk every 24
24450 - Relays that write any of the above statistics to disk and set
24451 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
24452 their extra-info documents.
24455 - New --digests command-line switch to output the digests of the
24456 source files Tor was built with.
24457 - The "torify" script now uses torsocks where available.
24458 - The memarea code now uses a sentinel value at the end of each area
24459 to make sure nothing writes beyond the end of an area. This might
24460 help debug some conceivable causes of bug 930.
24461 - Time and memory units in the configuration file can now be set to
24462 fractional units. For example, "2.5 GB" is now a valid value for
24464 - Certain Tor clients (such as those behind check.torproject.org) may
24465 want to fetch the consensus in an extra early manner. To enable this
24466 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
24467 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
24468 as only certain clients who must have this information sooner should
24470 - Instead of adding the svn revision to the Tor version string, report
24471 the git commit (when we're building from a git checkout).
24474 - If any of the v3 certs we download are unparseable, we should
24475 actually notice the failure so we don't retry indefinitely. Bugfix
24476 on 0.2.0.x; reported by "rotator".
24477 - If the cached cert file is unparseable, warn but don't exit.
24478 - Fix possible segmentation fault on directory authorities. Bugfix on
24480 - When Tor fails to parse a descriptor of any kind, dump it to disk.
24481 Might help diagnosing bug 1051.
24483 o Deprecated and removed features:
24484 - The controller no longer accepts the old obsolete "addr-mappings/"
24485 or "unregistered-servers-" GETINFO values.
24486 - Hidden services no longer publish version 0 descriptors, and clients
24487 do not request or use version 0 descriptors. However, the old hidden
24488 service authorities still accept and serve version 0 descriptors
24489 when contacted by older hidden services/clients.
24490 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
24491 always on; using them is necessary for correct forward-compatible
24493 - Remove support for .noconnect style addresses. Nobody was using
24494 them, and they provided another avenue for detecting Tor users
24495 via application-level web tricks.
24497 o Packaging changes:
24498 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
24499 installer bundles. See
24500 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
24501 for details of what's new in Vidalia 0.2.3.
24502 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
24503 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
24504 configuration file, rather than the old Privoxy.
24505 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
24506 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
24507 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
24508 better compatibility with OS X 10.6, aka Snow Leopard.
24509 - OS X Vidalia Bundle: The multi-package installer is now replaced
24510 by a simple drag and drop to the /Applications folder. This change
24511 occurred with the upgrade to Vidalia 0.2.3.
24514 Changes in version 0.2.1.19 - 2009-07-28
24515 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
24516 services on Tor 0.2.1.3-alpha through 0.2.1.18.
24519 - Make accessing hidden services on 0.2.1.x work right again.
24520 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
24521 part of patch provided by "optimist".
24524 - When a relay/bridge is writing out its identity key fingerprint to
24525 the "fingerprint" file and to its logs, write it without spaces. Now
24526 it will look like the fingerprints in our bridges documentation,
24527 and confuse fewer users.
24530 - Relays no longer publish a new server descriptor if they change
24531 their MaxAdvertisedBandwidth config option but it doesn't end up
24532 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
24533 fixes bug 1026. Patch from Sebastian.
24534 - Avoid leaking memory every time we get a create cell but we have
24535 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
24536 fixes bug 1034. Reported by BarkerJr.
24539 Changes in version 0.2.1.18 - 2009-07-24
24540 Tor 0.2.1.18 lays the foundations for performance improvements,
24541 adds status events to help users diagnose bootstrap problems, adds
24542 optional authentication/authorization for hidden services, fixes a
24543 variety of potential anonymity problems, and includes a huge pile of
24544 other features and bug fixes.
24547 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
24550 Changes in version 0.2.1.17-rc - 2009-07-07
24551 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
24552 candidate for the 0.2.1.x series. It lays the groundwork for further
24553 client performance improvements, and also fixes a big bug with directory
24554 authorities that were causing them to assign Guard and Stable flags
24557 The Windows bundles also finally include the geoip database that we
24558 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
24559 should actually install Torbutton rather than giving you a cryptic
24560 failure message (oops).
24563 - Clients now use the bandwidth values in the consensus, rather than
24564 the bandwidth values in each relay descriptor. This approach opens
24565 the door to more accurate bandwidth estimates once the directory
24566 authorities start doing active measurements. Implements more of
24570 - When Tor clients restart after 1-5 days, they discard all their
24571 cached descriptors as too old, but they still use the cached
24572 consensus document. This approach is good for robustness, but
24573 bad for performance: since they don't know any bandwidths, they
24574 end up choosing at random rather than weighting their choice by
24575 speed. Fixed by the above feature of putting bandwidths in the
24576 consensus. Bugfix on 0.2.0.x.
24577 - Directory authorities were neglecting to mark relays down in their
24578 internal histories if the relays fall off the routerlist without
24579 ever being found unreachable. So there were relays in the histories
24580 that haven't been seen for eight months, and are listed as being
24581 up for eight months. This wreaked havoc on the "median wfu"
24582 and "median mtbf" calculations, in turn making Guard and Stable
24583 flags very wrong, hurting network performance. Fixes bugs 696 and
24584 969. Bugfix on 0.2.0.6-alpha.
24587 - Serve the DirPortFrontPage page even when we have been approaching
24588 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
24589 - The control port would close the connection before flushing long
24590 replies, such as the network consensus, if a QUIT command was issued
24591 before the reply had completed. Now, the control port flushes all
24592 pending replies before closing the connection. Also fixed a spurious
24593 warning when a QUIT command is issued after a malformed or rejected
24594 AUTHENTICATE command, but before the connection was closed. Patch
24595 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
24596 - When we can't find an intro key for a v2 hidden service descriptor,
24597 fall back to the v0 hidden service descriptor and log a bug message.
24598 Workaround for bug 1024.
24599 - Fix a log message that did not respect the SafeLogging option.
24603 - If we're a relay and we change our IP address, be more verbose
24604 about the reason that made us change. Should help track down
24605 further bugs for relays on dynamic IP addresses.
24608 Changes in version 0.2.0.35 - 2009-06-24
24610 - Avoid crashing in the presence of certain malformed descriptors.
24611 Found by lark, and by automated fuzzing.
24612 - Fix an edge case where a malicious exit relay could convince a
24613 controller that the client's DNS question resolves to an internal IP
24614 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24617 - Finally fix the bug where dynamic-IP relays disappear when their
24618 IP address changes: directory mirrors were mistakenly telling
24619 them their old address if they asked via begin_dir, so they
24620 never got an accurate answer about their new address, so they
24621 just vanished after a day. For belt-and-suspenders, relays that
24622 don't set Address in their config now avoid using begin_dir for
24623 all direct connections. Should fix bugs 827, 883, and 900.
24624 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24625 that would occur on some exit nodes when DNS failures and timeouts
24626 occurred in certain patterns. Fix for bug 957.
24629 - When starting with a cache over a few days old, do not leak
24630 memory for the obsolete router descriptors in it. Bugfix on
24631 0.2.0.33; fixes bug 672.
24632 - Hidden service clients didn't use a cached service descriptor that
24633 was older than 15 minutes, but wouldn't fetch a new one either,
24634 because there was already one in the cache. Now, fetch a v2
24635 descriptor unless the same descriptor was added to the cache within
24636 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24639 Changes in version 0.2.1.16-rc - 2009-06-20
24640 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
24641 a bunch of minor bugs.
24644 - Fix an edge case where a malicious exit relay could convince a
24645 controller that the client's DNS question resolves to an internal IP
24646 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24648 o Major performance improvements (on 0.2.0.x):
24649 - Disable and refactor some debugging checks that forced a linear scan
24650 over the whole server-side DNS cache. These accounted for over 50%
24651 of CPU time on a relatively busy exit node's gprof profile. Found
24653 - Disable some debugging checks that appeared in exit node profile
24657 - Update to the "June 3 2009" ip-to-country file.
24658 - Do not have tor-resolve automatically refuse all .onion addresses;
24659 if AutomapHostsOnResolve is set in your torrc, this will work fine.
24661 o Minor bugfixes (on 0.2.0.x):
24662 - Log correct error messages for DNS-related network errors on
24664 - Fix a race condition that could cause crashes or memory corruption
24665 when running as a server with a controller listening for log
24667 - Avoid crashing when we have a policy specified in a DirPolicy or
24668 SocksPolicy or ReachableAddresses option with ports set on it,
24669 and we re-load the policy. May fix bug 996.
24670 - Hidden service clients didn't use a cached service descriptor that
24671 was older than 15 minutes, but wouldn't fetch a new one either,
24672 because there was already one in the cache. Now, fetch a v2
24673 descriptor unless the same descriptor was added to the cache within
24674 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24676 o Minor bugfixes (on 0.2.1.x):
24677 - Don't warn users about low port and hibernation mix when they
24678 provide a *ListenAddress directive to fix that. Bugfix on
24680 - When switching back and forth between bridge mode, do not start
24681 gathering GeoIP data until two hours have passed.
24682 - Do not complain that the user has requested an excluded node as
24683 an exit when the node is not really an exit. This could happen
24684 because the circuit was for testing, or an introduction point.
24688 Changes in version 0.2.1.15-rc - 2009-05-25
24689 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
24690 series. It fixes a major bug on fast exit relays, as well as a variety
24691 of more minor bugs.
24693 o Major bugfixes (on 0.2.0.x):
24694 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24695 that would occur on some exit nodes when DNS failures and timeouts
24696 occurred in certain patterns. Fix for bug 957.
24698 o Minor bugfixes (on 0.2.0.x):
24699 - Actually return -1 in the error case for read_bandwidth_usage().
24700 Harmless bug, since we currently don't care about the return value
24701 anywhere. Bugfix on 0.2.0.9-alpha.
24702 - Provide a more useful log message if bug 977 (related to buffer
24703 freelists) ever reappears, and do not crash right away.
24704 - Fix an assertion failure on 64-bit platforms when we allocated
24705 memory right up to the end of a memarea, then realigned the memory
24706 one step beyond the end. Fixes a possible cause of bug 930.
24707 - Protect the count of open sockets with a mutex, so we can't
24708 corrupt it when two threads are closing or opening sockets at once.
24709 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
24710 - Don't allow a bridge to publish its router descriptor to a
24711 non-bridge directory authority. Fixes part of bug 932.
24712 - When we change to or from being a bridge, reset our counts of
24713 client usage by country. Fixes bug 932.
24714 - Fix a bug that made stream bandwidth get misreported to the
24716 - Stop using malloc_usable_size() to use more area than we had
24717 actually allocated: it was safe, but made valgrind really unhappy.
24718 - Fix a memory leak when v3 directory authorities load their keys
24719 and cert from disk. Bugfix on 0.2.0.1-alpha.
24721 o Minor bugfixes (on 0.2.1.x):
24722 - Fix use of freed memory when deciding to mark a non-addable
24723 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24726 Changes in version 0.2.1.14-rc - 2009-04-12
24727 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24728 series. It begins fixing some major performance problems, and also
24729 finally addresses the bug that was causing relays on dynamic IP
24730 addresses to fall out of the directory.
24733 - Clients replace entry guards that were chosen more than a few months
24734 ago. This change should significantly improve client performance,
24735 especially once more people upgrade, since relays that have been
24736 a guard for a long time are currently overloaded.
24738 o Major bugfixes (on 0.2.0):
24739 - Finally fix the bug where dynamic-IP relays disappear when their
24740 IP address changes: directory mirrors were mistakenly telling
24741 them their old address if they asked via begin_dir, so they
24742 never got an accurate answer about their new address, so they
24743 just vanished after a day. For belt-and-suspenders, relays that
24744 don't set Address in their config now avoid using begin_dir for
24745 all direct connections. Should fix bugs 827, 883, and 900.
24746 - Relays were falling out of the networkstatus consensus for
24747 part of a day if they changed their local config but the
24748 authorities discarded their new descriptor as "not sufficiently
24749 different". Now directory authorities accept a descriptor as changed
24750 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24751 patch by Sebastian.
24752 - Avoid crashing in the presence of certain malformed descriptors.
24753 Found by lark, and by automated fuzzing.
24756 - When generating circuit events with verbose nicknames for
24757 controllers, try harder to look up nicknames for routers on a
24758 circuit. (Previously, we would look in the router descriptors we had
24759 for nicknames, but not in the consensus.) Partial fix for bug 941.
24760 - If the bridge config line doesn't specify a port, assume 443.
24761 This makes bridge lines a bit smaller and easier for users to
24763 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24764 bytes (aka 20KB/s), to match our documentation. Also update
24765 directory authorities so they always assign the Fast flag to relays
24766 with 20KB/s of capacity. Now people running relays won't suddenly
24767 find themselves not seeing any use, if the network gets faster
24769 - Update to the "April 3 2009" ip-to-country file.
24772 - Avoid trying to print raw memory to the logs when we decide to
24773 give up on downloading a given relay descriptor. Bugfix on
24775 - In tor-resolve, when the Tor client to use is specified by
24776 <hostname>:<port>, actually use the specified port rather than
24777 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24778 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24779 - When starting with a cache over a few days old, do not leak
24780 memory for the obsolete router descriptors in it. Bugfix on
24782 - Avoid double-free on list of successfully uploaded hidden
24783 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24784 - Change memarea_strndup() implementation to work even when
24785 duplicating a string at the end of a page. This bug was
24786 harmless for now, but could have meant crashes later. Fix by
24787 lark. Bugfix on 0.2.1.1-alpha.
24788 - Limit uploaded directory documents to be 16M rather than 500K.
24789 The directory authorities were refusing v3 consensus votes from
24790 other authorities, since the votes are now 504K. Fixes bug 959;
24791 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24792 - Directory authorities should never send a 503 "busy" response to
24793 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24797 Changes in version 0.2.1.13-alpha - 2009-03-09
24798 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24799 cleanups. We're finally getting close to a release candidate.
24802 - Correctly update the list of which countries we exclude as
24803 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24804 lark. Bugfix on 0.2.1.6-alpha.
24806 o Minor bugfixes (on 0.2.0.x and earlier):
24807 - Automatically detect MacOSX versions earlier than 10.4.0, and
24808 disable kqueue from inside Tor when running with these versions.
24809 We previously did this from the startup script, but that was no
24810 help to people who didn't use the startup script. Resolves bug 863.
24811 - When we had picked an exit node for a connection, but marked it as
24812 "optional", and it turned out we had no onion key for the exit,
24813 stop wanting that exit and try again. This situation may not
24814 be possible now, but will probably become feasible with proposal
24815 158. Spotted by rovv. Fixes another case of bug 752.
24816 - Clients no longer cache certificates for authorities they do not
24817 recognize. Bugfix on 0.2.0.9-alpha.
24818 - When we can't transmit a DNS request due to a network error, retry
24819 it after a while, and eventually transmit a failing response to
24820 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24821 - If the controller claimed responsibility for a stream, but that
24822 stream never finished making its connection, it would live
24823 forever in circuit_wait state. Now we close it after SocksTimeout
24824 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24825 - Drop begin cells to a hidden service if they come from the middle
24826 of a circuit. Patch from lark.
24827 - When we erroneously receive two EXTEND cells for the same circuit
24828 ID on the same connection, drop the second. Patch from lark.
24829 - Fix a crash that occurs on exit nodes when a nameserver request
24830 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24831 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24833 - Do not assume that a stack-allocated character array will be
24834 64-bit aligned on platforms that demand that uint64_t access is
24835 aligned. Possible fix for bug 604.
24836 - Parse dates and IPv4 addresses in a locale- and libc-independent
24837 manner, to avoid platform-dependent behavior on malformed input.
24838 - Build correctly when configured to build outside the main source
24839 path. Patch from Michael Gold.
24840 - We were already rejecting relay begin cells with destination port
24841 of 0. Now also reject extend cells with destination port or address
24842 of 0. Suggested by lark.
24844 o Minor bugfixes (on 0.2.1.x):
24845 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24846 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24847 - If we're an exit node, scrub the IP address to which we are exiting
24848 in the logs. Bugfix on 0.2.1.8-alpha.
24851 - On Linux, use the prctl call to re-enable core dumps when the user
24853 - New controller event NEWCONSENSUS that lists the networkstatus
24854 lines for every recommended relay. Now controllers like Torflow
24855 can keep up-to-date on which relays they should be using.
24856 - Update to the "February 26 2009" ip-to-country file.
24859 Changes in version 0.2.0.34 - 2009-02-08
24860 Tor 0.2.0.34 features several more security-related fixes. You should
24861 upgrade, especially if you run an exit relay (remote crash) or a
24862 directory authority (remote infinite loop), or you're on an older
24863 (pre-XP) or not-recently-patched Windows (remote exploit).
24865 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24866 have many known flaws, and nobody should be using them. You should
24867 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24868 stop using those packages and upgrade anyway.
24871 - Fix an infinite-loop bug on handling corrupt votes under certain
24872 circumstances. Bugfix on 0.2.0.8-alpha.
24873 - Fix a temporary DoS vulnerability that could be performed by
24874 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24875 - Avoid a potential crash on exit nodes when processing malformed
24876 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24877 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24878 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24881 - Fix compilation on systems where time_t is a 64-bit integer.
24882 Patch from Matthias Drochner.
24883 - Don't consider expiring already-closed client connections. Fixes
24884 bug 893. Bugfix on 0.0.2pre20.
24887 Changes in version 0.2.1.12-alpha - 2009-02-08
24888 Tor 0.2.1.12-alpha features several more security-related fixes. You
24889 should upgrade, especially if you run an exit relay (remote crash) or
24890 a directory authority (remote infinite loop), or you're on an older
24891 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24892 includes a big pile of minor bugfixes and cleanups.
24895 - Fix an infinite-loop bug on handling corrupt votes under certain
24896 circumstances. Bugfix on 0.2.0.8-alpha.
24897 - Fix a temporary DoS vulnerability that could be performed by
24898 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24899 - Avoid a potential crash on exit nodes when processing malformed
24900 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24903 - Let controllers actually ask for the "clients_seen" event for
24904 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24905 reported by Matt Edman.
24906 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24908 - Fix a bug in address parsing that was preventing bridges or hidden
24909 service targets from being at IPv6 addresses.
24910 - Solve a bug that kept hardware crypto acceleration from getting
24911 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24913 - Remove a bash-ism from configure.in to build properly on non-Linux
24914 platforms. Bugfix on 0.2.1.1-alpha.
24915 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24916 headers. Bugfix on 0.2.0.10-alpha.
24917 - Don't consider expiring already-closed client connections. Fixes
24918 bug 893. Bugfix on 0.0.2pre20.
24919 - Fix another interesting corner-case of bug 891 spotted by rovv:
24920 Previously, if two hosts had different amounts of clock drift, and
24921 one of them created a new connection with just the wrong timing,
24922 the other might decide to deprecate the new connection erroneously.
24923 Bugfix on 0.1.1.13-alpha.
24924 - Resolve a very rare crash bug that could occur when the user forced
24925 a nameserver reconfiguration during the middle of a nameserver
24926 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
24927 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
24928 Bugfix on 0.2.1.7-alpha.
24929 - If we're using bridges and our network goes away, be more willing
24930 to forgive our bridges and try again when we get an application
24931 request. Bugfix on 0.2.0.x.
24934 - Support platforms where time_t is 64 bits long. (Congratulations,
24935 NetBSD!) Patch from Matthias Drochner.
24936 - Add a 'getinfo status/clients-seen' controller command, in case
24937 controllers want to hear clients_seen events but connect late.
24940 - Disable GCC's strict alias optimization by default, to avoid the
24941 likelihood of its introducing subtle bugs whenever our code violates
24942 the letter of C99's alias rules.
24945 Changes in version 0.2.0.33 - 2009-01-21
24946 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
24947 useful to users. It also finally fixes a bug where a relay or client
24948 that's been off for many days would take a long time to bootstrap.
24950 This update also fixes an important security-related bug reported by
24951 Ilja van Sprundel. You should upgrade. (We'll send out more details
24952 about the bug once people have had some time to upgrade.)
24955 - Fix a heap-corruption bug that may be remotely triggerable on
24956 some platforms. Reported by Ilja van Sprundel.
24959 - When a stream at an exit relay is in state "resolving" or
24960 "connecting" and it receives an "end" relay cell, the exit relay
24961 would silently ignore the end cell and not close the stream. If
24962 the client never closes the circuit, then the exit relay never
24963 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
24964 reported by "wood".
24965 - When sending CREATED cells back for a given circuit, use a 64-bit
24966 connection ID to find the right connection, rather than an addr:port
24967 combination. Now that we can have multiple OR connections between
24968 the same ORs, it is no longer possible to use addr:port to uniquely
24969 identify a connection.
24970 - Bridge relays that had DirPort set to 0 would stop fetching
24971 descriptors shortly after startup, and then briefly resume
24972 after a new bandwidth test and/or after publishing a new bridge
24973 descriptor. Bridge users that try to bootstrap from them would
24974 get a recent networkstatus but would get descriptors from up to
24975 18 hours earlier, meaning most of the descriptors were obsolete
24976 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
24977 - Prevent bridge relays from serving their 'extrainfo' document
24978 to anybody who asks, now that extrainfo docs include potentially
24979 sensitive aggregated client geoip summaries. Bugfix on
24981 - If the cached networkstatus consensus is more than five days old,
24982 discard it rather than trying to use it. In theory it could be
24983 useful because it lists alternate directory mirrors, but in practice
24984 it just means we spend many minutes trying directory mirrors that
24985 are long gone from the network. Also discard router descriptors as
24986 we load them if they are more than five days old, since the onion
24987 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
24990 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
24991 could make gcc generate non-functional binary search code. Bugfix
24993 - Build correctly on platforms without socklen_t.
24994 - Compile without warnings on solaris.
24995 - Avoid potential crash on internal error during signature collection.
24996 Fixes bug 864. Patch from rovv.
24997 - Correct handling of possible malformed authority signing key
24998 certificates with internal signature types. Fixes bug 880.
24999 Bugfix on 0.2.0.3-alpha.
25000 - Fix a hard-to-trigger resource leak when logging credential status.
25002 - When we can't initialize DNS because the network is down, do not
25003 automatically stop Tor from starting. Instead, we retry failed
25004 dns_init() every 10 minutes, and change the exit policy to reject
25005 *:* until one succeeds. Fixes bug 691.
25006 - Use 64 bits instead of 32 bits for connection identifiers used with
25007 the controller protocol, to greatly reduce risk of identifier reuse.
25008 - When we're choosing an exit node for a circuit, and we have
25009 no pending streams, choose a good general exit rather than one that
25010 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25011 - Fix another case of assuming, when a specific exit is requested,
25012 that we know more than the user about what hosts it allows.
25013 Fixes one case of bug 752. Patch from rovv.
25014 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25015 seconds. Warn the user if lower values are given in the
25016 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25017 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25018 user if lower values are given in the configuration. Bugfix on
25019 0.1.1.17-rc. Patch by Sebastian.
25020 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
25021 the cache because we already had a v0 descriptor with the same ID.
25022 Bugfix on 0.2.0.18-alpha.
25023 - Fix a race condition when freeing keys shared between main thread
25024 and CPU workers that could result in a memory leak. Bugfix on
25025 0.1.0.1-rc. Fixes bug 889.
25026 - Send a valid END cell back when a client tries to connect to a
25027 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25028 840. Patch from rovv.
25029 - Check which hops rendezvous stream cells are associated with to
25030 prevent possible guess-the-streamid injection attacks from
25031 intermediate hops. Fixes another case of bug 446. Based on patch
25033 - If a broken client asks a non-exit router to connect somewhere,
25034 do not even do the DNS lookup before rejecting the connection.
25035 Fixes another case of bug 619. Patch from rovv.
25036 - When a relay gets a create cell it can't decrypt (e.g. because it's
25037 using the wrong onion key), we were dropping it and letting the
25038 client time out. Now actually answer with a destroy cell. Fixes
25039 bug 904. Bugfix on 0.0.2pre8.
25041 o Minor bugfixes (hidden services):
25042 - Do not throw away existing introduction points on SIGHUP. Bugfix on
25043 0.0.6pre1. Patch by Karsten. Fixes bug 874.
25046 - Report the case where all signatures in a detached set are rejected
25047 differently than the case where there is an error handling the
25049 - When we realize that another process has modified our cached
25050 descriptors, print out a more useful error message rather than
25051 triggering an assertion. Fixes bug 885. Patch from Karsten.
25052 - Implement the 0x20 hack to better resist DNS poisoning: set the
25053 case on outgoing DNS requests randomly, and reject responses that do
25054 not match the case correctly. This logic can be disabled with the
25055 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
25056 of servers that do not reliably preserve case in replies. See
25057 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25059 - Check DNS replies for more matching fields to better resist DNS
25061 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25062 compress cells, which are basically all encrypted, compressed, or
25066 Changes in version 0.2.1.11-alpha - 2009-01-20
25067 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
25068 week it will take a long time to bootstrap again" bug. It also fixes
25069 an important security-related bug reported by Ilja van Sprundel. You
25070 should upgrade. (We'll send out more details about the bug once people
25071 have had some time to upgrade.)
25074 - Fix a heap-corruption bug that may be remotely triggerable on
25075 some platforms. Reported by Ilja van Sprundel.
25078 - Discard router descriptors as we load them if they are more than
25079 five days old. Otherwise if Tor is off for a long time and then
25080 starts with cached descriptors, it will try to use the onion
25081 keys in those obsolete descriptors when building circuits. Bugfix
25082 on 0.2.0.x. Fixes bug 887.
25085 - Try to make sure that the version of Libevent we're running with
25086 is binary-compatible with the one we built with. May address bug
25088 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
25089 for bug 905. Bugfix on 0.2.1.7-alpha.
25090 - Add a new --enable-local-appdata configuration switch to change
25091 the default location of the datadir on win32 from APPDATA to
25092 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
25093 entirely. Patch from coderman.
25096 - Make outbound DNS packets respect the OutboundBindAddress setting.
25097 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
25098 - When our circuit fails at the first hop (e.g. we get a destroy
25099 cell back), avoid using that OR connection anymore, and also
25100 tell all the one-hop directory requests waiting for it that they
25101 should fail. Bugfix on 0.2.1.3-alpha.
25102 - In the torify(1) manpage, mention that tsocks will leak your
25106 Changes in version 0.2.1.10-alpha - 2009-01-06
25107 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
25108 would make the bridge relay not so useful if it had DirPort set to 0,
25109 and one that could let an attacker learn a little bit of information
25110 about the bridge's users), and a bug that would cause your Tor relay
25111 to ignore a circuit create request it can't decrypt (rather than reply
25112 with an error). It also fixes a wide variety of other bugs.
25115 - If the cached networkstatus consensus is more than five days old,
25116 discard it rather than trying to use it. In theory it could
25117 be useful because it lists alternate directory mirrors, but in
25118 practice it just means we spend many minutes trying directory
25119 mirrors that are long gone from the network. Helps bug 887 a bit;
25121 - Bridge relays that had DirPort set to 0 would stop fetching
25122 descriptors shortly after startup, and then briefly resume
25123 after a new bandwidth test and/or after publishing a new bridge
25124 descriptor. Bridge users that try to bootstrap from them would
25125 get a recent networkstatus but would get descriptors from up to
25126 18 hours earlier, meaning most of the descriptors were obsolete
25127 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
25128 - Prevent bridge relays from serving their 'extrainfo' document
25129 to anybody who asks, now that extrainfo docs include potentially
25130 sensitive aggregated client geoip summaries. Bugfix on
25134 - New controller event "clients_seen" to report a geoip-based summary
25135 of which countries we've seen clients from recently. Now controllers
25136 like Vidalia can show bridge operators that they're actually making
25138 - Build correctly against versions of OpenSSL 0.9.8 or later built
25139 without support for deprecated functions.
25140 - Update to the "December 19 2008" ip-to-country file.
25142 o Minor bugfixes (on 0.2.0.x):
25143 - Authorities now vote for the Stable flag for any router whose
25144 weighted MTBF is at least 5 days, regardless of the mean MTBF.
25145 - Do not remove routers as too old if we do not have any consensus
25146 document. Bugfix on 0.2.0.7-alpha.
25147 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
25148 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
25149 - When an exit relay resolves a stream address to a local IP address,
25150 do not just keep retrying that same exit relay over and
25151 over. Instead, just close the stream. Addresses bug 872. Bugfix
25152 on 0.2.0.32. Patch from rovv.
25153 - If a hidden service sends us an END cell, do not consider
25154 retrying the connection; just close it. Patch from rovv.
25155 - When we made bridge authorities stop serving bridge descriptors over
25156 unencrypted links, we also broke DirPort reachability testing for
25157 bridges. So bridges with a non-zero DirPort were printing spurious
25158 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
25159 - When a relay gets a create cell it can't decrypt (e.g. because it's
25160 using the wrong onion key), we were dropping it and letting the
25161 client time out. Now actually answer with a destroy cell. Fixes
25162 bug 904. Bugfix on 0.0.2pre8.
25163 - Squeeze 2-5% out of client performance (according to oprofile) by
25164 improving the implementation of some policy-manipulation functions.
25166 o Minor bugfixes (on 0.2.1.x):
25167 - Make get_interface_address() function work properly again; stop
25168 guessing the wrong parts of our address as our address.
25169 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
25170 send on that circuit. Otherwise we might violate the proposal-110
25171 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
25173 - When we're sending non-EXTEND cells to the first hop in a circuit,
25174 for example to use an encrypted directory connection, we don't need
25175 to use RELAY_EARLY cells: the first hop knows what kind of cell
25176 it is, and nobody else can even see the cell type. Conserving
25177 RELAY_EARLY cells makes it easier to cannibalize circuits like
25179 - Stop logging nameserver addresses in reverse order.
25180 - If we are retrying a directory download slowly over and over, do
25181 not automatically give up after the 254th failure. Bugfix on
25183 - Resume reporting accurate "stream end" reasons to the local control
25184 port. They were lost in the changes for Proposal 148. Bugfix on
25187 o Deprecated and removed features:
25188 - The old "tor --version --version" command, which would print out
25189 the subversion "Id" of most of the source files, is now removed. It
25190 turned out to be less useful than we'd expected, and harder to
25193 o Code simplifications and refactoring:
25194 - Change our header file guard macros to be less likely to conflict
25195 with system headers. Adam Langley noticed that we were conflicting
25196 with log.h on Android.
25197 - Tool-assisted documentation cleanup. Nearly every function or
25198 static variable in Tor should have its own documentation now.
25201 Changes in version 0.2.1.9-alpha - 2008-12-25
25202 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
25204 o New directory authorities:
25205 - gabelmoo (the authority run by Karsten Loesing) now has a new
25209 - Never use a connection with a mismatched address to extend a
25210 circuit, unless that connection is canonical. A canonical
25211 connection is one whose address is authenticated by the router's
25212 identity key, either in a NETINFO cell or in a router descriptor.
25213 - Avoid a possible memory corruption bug when receiving hidden service
25214 descriptors. Bugfix on 0.2.1.6-alpha.
25217 - Fix a logic error that would automatically reject all but the first
25218 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
25219 part of bug 813/868. Bug spotted by coderman.
25220 - When a stream at an exit relay is in state "resolving" or
25221 "connecting" and it receives an "end" relay cell, the exit relay
25222 would silently ignore the end cell and not close the stream. If
25223 the client never closes the circuit, then the exit relay never
25224 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
25225 reported by "wood".
25226 - When we can't initialize DNS because the network is down, do not
25227 automatically stop Tor from starting. Instead, retry failed
25228 dns_init() every 10 minutes, and change the exit policy to reject
25229 *:* until one succeeds. Fixes bug 691.
25232 - Give a better error message when an overzealous init script says
25233 "sudo -u username tor --user username". Makes Bug 882 easier for
25235 - When a directory authority gives us a new guess for our IP address,
25236 log which authority we used. Hopefully this will help us debug
25237 the recent complaints about bad IP address guesses.
25238 - Detect svn revision properly when we're using git-svn.
25239 - Try not to open more than one descriptor-downloading connection
25240 to an authority at once. This should reduce load on directory
25241 authorities. Fixes bug 366.
25242 - Add cross-certification to newly generated certificates, so that
25243 a signing key is enough information to look up a certificate.
25244 Partial implementation of proposal 157.
25245 - Start serving certificates by <identity digest, signing key digest>
25246 pairs. Partial implementation of proposal 157.
25247 - Clients now never report any stream end reason except 'MISC'.
25248 Implements proposal 148.
25249 - On platforms with a maximum syslog string length, truncate syslog
25250 messages to that length ourselves, rather than relying on the
25251 system to do it for us.
25252 - Optimize out calls to time(NULL) that occur for every IO operation,
25253 or for every cell. On systems where time() is a slow syscall,
25254 this fix will be slightly helpful.
25255 - Exit servers can now answer resolve requests for ip6.arpa addresses.
25256 - When we download a descriptor that we then immediately (as
25257 a directory authority) reject, do not retry downloading it right
25258 away. Should save some bandwidth on authorities. Fix for bug
25259 888. Patch by Sebastian Hahn.
25260 - When a download gets us zero good descriptors, do not notify
25261 Tor that new directory information has arrived.
25262 - Avoid some nasty corner cases in the logic for marking connections
25263 as too old or obsolete or noncanonical for circuits. Partial
25266 o Minor features (controller):
25267 - New CONSENSUS_ARRIVED event to note when a new consensus has
25268 been fetched and validated.
25269 - When we realize that another process has modified our cached
25270 descriptors file, print out a more useful error message rather
25271 than triggering an assertion. Fixes bug 885. Patch from Karsten.
25272 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
25273 controllers to prevent SIGHUP from reloading the
25274 configuration. Fixes bug 856.
25277 - Resume using the correct "REASON=" stream when telling the
25278 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
25279 - When a canonical connection appears later in our internal list
25280 than a noncanonical one for a given OR ID, always use the
25281 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
25283 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25284 seconds. Warn the user if lower values are given in the
25285 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25286 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25287 user if lower values are given in the configuration. Bugfix on
25288 0.1.1.17-rc. Patch by Sebastian.
25289 - Fix a race condition when freeing keys shared between main thread
25290 and CPU workers that could result in a memory leak. Bugfix on
25291 0.1.0.1-rc. Fixes bug 889.
25293 o Minor bugfixes (hidden services):
25294 - Do not throw away existing introduction points on SIGHUP (bugfix on
25295 0.0.6pre1); also, do not stall hidden services because we're
25296 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
25297 by John Brooks. Patch by Karsten. Fixes bug 874.
25298 - Fix a memory leak when we decline to add a v2 rendezvous
25299 descriptor to the cache because we already had a v0 descriptor
25300 with the same ID. Bugfix on 0.2.0.18-alpha.
25302 o Deprecated and removed features:
25303 - RedirectExits has been removed. It was deprecated since
25305 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
25306 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
25307 - Cell pools are now always enabled; --disable-cell-pools is ignored.
25309 o Code simplifications and refactoring:
25310 - Rename the confusing or_is_obsolete field to the more appropriate
25311 is_bad_for_new_circs, and move it to or_connection_t where it
25313 - Move edge-only flags from connection_t to edge_connection_t: not
25314 only is this better coding, but on machines of plausible alignment,
25315 it should save 4-8 bytes per connection_t. "Every little bit helps."
25316 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
25317 for consistency; keep old option working for backward compatibility.
25318 - Simplify the code for finding connections to use for a circuit.
25321 Changes in version 0.2.1.8-alpha - 2008-12-08
25322 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
25323 builds better on unusual platforms like Solaris and old OS X, and
25324 fixes a variety of other issues.
25327 - New DirPortFrontPage option that takes an html file and publishes
25328 it as "/" on the DirPort. Now relay operators can provide a
25329 disclaimer without needing to set up a separate webserver. There's
25330 a sample disclaimer in contrib/tor-exit-notice.html.
25333 - When the client is choosing entry guards, now it selects at most
25334 one guard from a given relay family. Otherwise we could end up with
25335 all of our entry points into the network run by the same operator.
25336 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
25339 - Fix a DOS opportunity during the voting signature collection process
25340 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25341 - Fix a possible segfault when establishing an exit connection. Bugfix
25345 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
25347 - Made Tor a little less aggressive about deleting expired
25348 certificates. Partial fix for bug 854.
25349 - Stop doing unaligned memory access that generated bus errors on
25350 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
25351 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
25352 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
25353 - Make USR2 log-level switch take effect immediately. Bugfix on
25355 - If one win32 nameserver fails to get added, continue adding the
25356 rest, and don't automatically fail.
25357 - Use fcntl() for locking when flock() is not available. Should fix
25358 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
25359 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25360 could make gcc generate non-functional binary search code. Bugfix
25362 - Build correctly on platforms without socklen_t.
25363 - Avoid potential crash on internal error during signature collection.
25364 Fixes bug 864. Patch from rovv.
25365 - Do not use C's stdio library for writing to log files. This will
25366 improve logging performance by a minute amount, and will stop
25367 leaking fds when our disk is full. Fixes bug 861.
25368 - Stop erroneous use of O_APPEND in cases where we did not in fact
25369 want to re-seek to the end of a file before every last write().
25370 - Correct handling of possible malformed authority signing key
25371 certificates with internal signature types. Fixes bug 880. Bugfix
25373 - Fix a hard-to-trigger resource leak when logging credential status.
25377 - Directory mirrors no longer fetch the v1 directory or
25378 running-routers files. They are obsolete, and nobody asks for them
25379 anymore. This is the first step to making v1 authorities obsolete.
25381 o Minor features (controller):
25382 - Return circuit purposes in response to GETINFO circuit-status. Fixes
25386 Changes in version 0.2.0.32 - 2008-11-20
25387 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
25388 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25389 a smaller security flaw that might allow an attacker to access local
25390 services, further improves hidden service performance, and fixes a
25391 variety of other issues.
25394 - The "User" and "Group" config options did not clear the
25395 supplementary group entries for the Tor process. The "User" option
25396 is now more robust, and we now set the groups to the specified
25397 user's primary group. The "Group" option is now ignored. For more
25398 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25399 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25400 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
25401 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25402 consistently obeyed: if an exit relay refuses a stream because its
25403 exit policy doesn't allow it, we would remember what IP address
25404 the relay said the destination address resolves to, even if it's
25405 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25408 - Fix a DOS opportunity during the voting signature collection process
25409 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25411 o Major bugfixes (hidden services):
25412 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25413 we were failing the whole hidden service request when the v0
25414 descriptor fetch fails, even if the v2 fetch is still pending and
25415 might succeed. Similarly, if the last v2 fetch fails, we were
25416 failing the whole hidden service request even if a v0 fetch is
25417 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25418 - When extending a circuit to a hidden service directory to upload a
25419 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25420 requests failed, because the router descriptor has not been
25421 downloaded yet. In these cases, do not attempt to upload the
25422 rendezvous descriptor, but wait until the router descriptor is
25423 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
25424 descriptor from a hidden service directory for which the router
25425 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
25429 - Fix several infrequent memory leaks spotted by Coverity.
25430 - When testing for libevent functions, set the LDFLAGS variable
25431 correctly. Found by Riastradh.
25432 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25433 bootstrapping with tunneled directory connections. Bugfix on
25434 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25435 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25436 and we know that server B rejects most-but-not all connections to
25437 port 80, we would previously reject the connection. Now, we assume
25438 the user knows what they were asking for. Fixes bug 752. Bugfix
25439 on 0.0.9rc5. Diagnosed by BarkerJr.
25440 - If we overrun our per-second write limits a little, count this as
25441 having used up our write allocation for the second, and choke
25442 outgoing directory writes. Previously, we had only counted this when
25443 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
25444 Bugfix on 0.2.0.x (??).
25445 - Remove the old v2 directory authority 'lefkada' from the default
25446 list. It has been gone for many months.
25447 - Stop doing unaligned memory access that generated bus errors on
25448 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
25449 - Make USR2 log-level switch take effect immediately. Bugfix on
25452 o Minor bugfixes (controller):
25453 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
25454 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
25457 Changes in version 0.2.1.7-alpha - 2008-11-08
25458 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
25459 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25460 a smaller security flaw that might allow an attacker to access local
25461 services, adds better defense against DNS poisoning attacks on exit
25462 relays, further improves hidden service performance, and fixes a
25463 variety of other issues.
25466 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25467 consistently obeyed: if an exit relay refuses a stream because its
25468 exit policy doesn't allow it, we would remember what IP address
25469 the relay said the destination address resolves to, even if it's
25470 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25471 - The "User" and "Group" config options did not clear the
25472 supplementary group entries for the Tor process. The "User" option
25473 is now more robust, and we now set the groups to the specified
25474 user's primary group. The "Group" option is now ignored. For more
25475 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25476 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25477 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
25478 - Do not use or believe expired v3 authority certificates. Patch
25479 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
25482 - Now NodeFamily and MyFamily config options allow spaces in
25483 identity fingerprints, so it's easier to paste them in.
25484 Suggested by Lucky Green.
25485 - Implement the 0x20 hack to better resist DNS poisoning: set the
25486 case on outgoing DNS requests randomly, and reject responses that do
25487 not match the case correctly. This logic can be disabled with the
25488 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
25489 of servers that do not reliably preserve case in replies. See
25490 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25492 - Preserve case in replies to DNSPort requests in order to support
25493 the 0x20 hack for resisting DNS poisoning attacks.
25495 o Hidden service performance improvements:
25496 - When the client launches an introduction circuit, retry with a
25497 new circuit after 30 seconds rather than 60 seconds.
25498 - Launch a second client-side introduction circuit in parallel
25499 after a delay of 15 seconds (based on work by Christian Wilms).
25500 - Hidden services start out building five intro circuits rather
25501 than three, and when the first three finish they publish a service
25502 descriptor using those. Now we publish our service descriptor much
25503 faster after restart.
25506 - Minor fix in the warning messages when you're having problems
25507 bootstrapping; also, be more forgiving of bootstrap problems when
25508 we're still making incremental progress on a given bootstrap phase.
25509 - When we're choosing an exit node for a circuit, and we have
25510 no pending streams, choose a good general exit rather than one that
25511 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25512 - Send a valid END cell back when a client tries to connect to a
25513 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25514 840. Patch from rovv.
25515 - If a broken client asks a non-exit router to connect somewhere,
25516 do not even do the DNS lookup before rejecting the connection.
25517 Fixes another case of bug 619. Patch from rovv.
25518 - Fix another case of assuming, when a specific exit is requested,
25519 that we know more than the user about what hosts it allows.
25520 Fixes another case of bug 752. Patch from rovv.
25521 - Check which hops rendezvous stream cells are associated with to
25522 prevent possible guess-the-streamid injection attacks from
25523 intermediate hops. Fixes another case of bug 446. Based on patch
25525 - Avoid using a negative right-shift when comparing 32-bit
25526 addresses. Possible fix for bug 845 and bug 811.
25527 - Make the assert_circuit_ok() function work correctly on circuits that
25528 have already been marked for close.
25529 - Fix read-off-the-end-of-string error in unit tests when decoding
25530 introduction points.
25531 - Fix uninitialized size field for memory area allocation: may improve
25532 memory performance during directory parsing.
25533 - Treat duplicate certificate fetches as failures, so that we do
25534 not try to re-fetch an expired certificate over and over and over.
25535 - Do not say we're fetching a certificate when we'll in fact skip it
25536 because of a pending download.
25539 Changes in version 0.2.1.6-alpha - 2008-09-30
25540 Tor 0.2.1.6-alpha further improves performance and robustness of
25541 hidden services, starts work on supporting per-country relay selection,
25542 and fixes a variety of smaller issues.
25545 - Implement proposal 121: make it possible to build hidden services
25546 that only certain clients are allowed to connect to. This is
25547 enforced at several points, so that unauthorized clients are unable
25548 to send INTRODUCE cells to the service, or even (depending on the
25549 type of authentication) to learn introduction points. This feature
25550 raises the bar for certain kinds of active attacks against hidden
25551 services. Code by Karsten Loesing.
25552 - Relays now store and serve v2 hidden service descriptors by default,
25553 i.e., the new default value for HidServDirectoryV2 is 1. This is
25554 the last step in proposal 114, which aims to make hidden service
25555 lookups more reliable.
25556 - Start work to allow node restrictions to include country codes. The
25557 syntax to exclude nodes in a country with country code XX is
25558 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
25559 refinement to decide what config options should take priority if
25560 you ask to both use a particular node and exclude it.
25561 - Allow ExitNodes list to include IP ranges and country codes, just
25562 like the Exclude*Nodes lists. Patch from Robert Hogan.
25565 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
25566 Tor to fail to start if you had it configured to use a bridge
25567 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
25568 - When extending a circuit to a hidden service directory to upload a
25569 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25570 requests failed, because the router descriptor had not been
25571 downloaded yet. In these cases, we now wait until the router
25572 descriptor is downloaded, and then retry. Likewise, clients
25573 now skip over a hidden service directory if they don't yet have
25574 its router descriptor, rather than futilely requesting it and
25575 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
25577 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25578 we were failing the whole hidden service request when the v0
25579 descriptor fetch fails, even if the v2 fetch is still pending and
25580 might succeed. Similarly, if the last v2 fetch fails, we were
25581 failing the whole hidden service request even if a v0 fetch is
25582 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25583 - DNS replies need to have names matching their requests, but
25584 these names should be in the questions section, not necessarily
25585 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
25588 - Update to the "September 1 2008" ip-to-country file.
25589 - Allow ports 465 and 587 in the default exit policy again. We had
25590 rejected them in 0.1.0.15, because back in 2005 they were commonly
25591 misconfigured and ended up as spam targets. We hear they are better
25592 locked down these days.
25593 - Use a lockfile to make sure that two Tor processes are not
25594 simultaneously running with the same datadir.
25595 - Serve the latest v3 networkstatus consensus via the control
25596 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
25597 - Better logging about stability/reliability calculations on directory
25599 - Drop the requirement to have an open dir port for storing and
25600 serving v2 hidden service descriptors.
25601 - Directory authorities now serve a /tor/dbg-stability.txt URL to
25602 help debug WFU and MTBF calculations.
25603 - Implement most of Proposal 152: allow specialized servers to permit
25604 single-hop circuits, and clients to use those servers to build
25605 single-hop circuits when using a specialized controller. Patch
25606 from Josh Albrecht. Resolves feature request 768.
25607 - Add a -p option to tor-resolve for specifying the SOCKS port: some
25608 people find host:port too confusing.
25609 - Make TrackHostExit mappings expire a while after their last use, not
25610 after their creation. Patch from Robert Hogan.
25611 - Provide circuit purposes along with circuit events to the controller.
25614 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
25616 - Fixed some memory leaks -- some quite frequent, some almost
25617 impossible to trigger -- based on results from Coverity.
25618 - When testing for libevent functions, set the LDFLAGS variable
25619 correctly. Found by Riastradh.
25620 - Fix an assertion bug in parsing policy-related options; possible fix
25622 - Catch and report a few more bootstrapping failure cases when Tor
25623 fails to establish a TCP connection. Cleanup on 0.2.1.x.
25624 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25625 bootstrapping with tunneled directory connections. Bugfix on
25626 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25627 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25628 and we know that server B rejects most-but-not all connections to
25629 port 80, we would previously reject the connection. Now, we assume
25630 the user knows what they were asking for. Fixes bug 752. Bugfix
25631 on 0.0.9rc5. Diagnosed by BarkerJr.
25632 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
25633 service directories if they have no advertised dir port. Bugfix
25635 - If we overrun our per-second write limits a little, count this as
25636 having used up our write allocation for the second, and choke
25637 outgoing directory writes. Previously, we had only counted this when
25638 we had met our limits precisely. Fixes bug 824. Patch by rovv.
25639 Bugfix on 0.2.0.x (??).
25640 - Avoid a "0 divided by 0" calculation when calculating router uptime
25641 at directory authorities. Bugfix on 0.2.0.8-alpha.
25642 - Make DNS resolved controller events into "CLOSED", not
25643 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
25645 - Fix a bug where an unreachable relay would establish enough
25646 reachability testing circuits to do a bandwidth test -- if
25647 we already have a connection to the middle hop of the testing
25648 circuit, then it could establish the last hop by using the existing
25649 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
25650 circuits no longer use entry guards in 0.2.1.3-alpha.
25651 - If we have correct permissions on $datadir, we complain to stdout
25652 and fail to start. But dangerous permissions on
25653 $datadir/cached-status/ would cause us to open a log and complain
25654 there. Now complain to stdout and fail to start in both cases. Fixes
25655 bug 820, reported by seeess.
25656 - Remove the old v2 directory authority 'lefkada' from the default
25657 list. It has been gone for many months.
25659 o Code simplifications and refactoring:
25660 - Revise the connection_new functions so that a more typesafe variant
25661 exists. This will work better with Coverity, and let us find any
25662 actual mistakes we're making here.
25663 - Refactor unit testing logic so that dmalloc can be used sensibly
25664 with unit tests to check for memory leaks.
25665 - Move all hidden-service related fields from connection and circuit
25666 structure to substructures: this way they won't eat so much memory.
25669 Changes in version 0.2.0.31 - 2008-09-03
25670 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
25671 a big bug we're seeing where in rare cases traffic from one Tor stream
25672 gets mixed into another stream, and fixes a variety of smaller issues.
25675 - Make sure that two circuits can never exist on the same connection
25676 with the same circuit ID, even if one is marked for close. This
25677 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
25678 - Relays now reject risky extend cells: if the extend cell includes
25679 a digest of all zeroes, or asks to extend back to the relay that
25680 sent the extend cell, tear down the circuit. Ideas suggested
25682 - If not enough of our entry guards are available so we add a new
25683 one, we might use the new one even if it overlapped with the
25684 current circuit's exit relay (or its family). Anonymity bugfix
25685 pointed out by rovv.
25688 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25689 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25690 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25691 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25692 - Pick size of default geoip filename string correctly on windows.
25693 Fixes bug 806. Bugfix on 0.2.0.30.
25694 - Make the autoconf script accept the obsolete --with-ssl-dir
25695 option as an alias for the actually-working --with-openssl-dir
25696 option. Fix the help documentation to recommend --with-openssl-dir.
25697 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25698 - When using the TransPort option on OpenBSD, and using the User
25699 option to change UID and drop privileges, make sure to open
25700 /dev/pf before dropping privileges. Fixes bug 782. Patch from
25701 Christopher Davis. Bugfix on 0.1.2.1-alpha.
25702 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25703 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25704 on the client side when connecting to a hidden service. Bugfix
25705 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25706 - When closing an application-side connection because its circuit is
25707 getting torn down, generate the stream event correctly. Bugfix on
25708 0.1.2.x. Anonymous patch.
25711 Changes in version 0.2.1.5-alpha - 2008-08-31
25712 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25713 in a lot of the infrastructure for adding authorization to hidden
25714 services, lays the groundwork for having clients read their load
25715 balancing information out of the networkstatus consensus rather than
25716 the individual router descriptors, addresses two potential anonymity
25717 issues, and fixes a variety of smaller issues.
25720 - Convert many internal address representations to optionally hold
25722 - Generate and accept IPv6 addresses in many protocol elements.
25723 - Make resolver code handle nameservers located at ipv6 addresses.
25724 - Begin implementation of proposal 121 ("Client authorization for
25725 hidden services"): configure hidden services with client
25726 authorization, publish descriptors for them, and configure
25727 authorization data for hidden services at clients. The next
25728 step is to actually access hidden services that perform client
25730 - More progress toward proposal 141: Network status consensus
25731 documents and votes now contain bandwidth information for each
25732 router and a summary of that router's exit policy. Eventually this
25733 will be used by clients so that they do not have to download every
25734 known descriptor before building circuits.
25736 o Major bugfixes (on 0.2.0.x and before):
25737 - When sending CREATED cells back for a given circuit, use a 64-bit
25738 connection ID to find the right connection, rather than an addr:port
25739 combination. Now that we can have multiple OR connections between
25740 the same ORs, it is no longer possible to use addr:port to uniquely
25741 identify a connection.
25742 - Relays now reject risky extend cells: if the extend cell includes
25743 a digest of all zeroes, or asks to extend back to the relay that
25744 sent the extend cell, tear down the circuit. Ideas suggested
25746 - If not enough of our entry guards are available so we add a new
25747 one, we might use the new one even if it overlapped with the
25748 current circuit's exit relay (or its family). Anonymity bugfix
25749 pointed out by rovv.
25752 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25753 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25754 - When using the TransPort option on OpenBSD, and using the User
25755 option to change UID and drop privileges, make sure to open /dev/pf
25756 before dropping privileges. Fixes bug 782. Patch from Christopher
25757 Davis. Bugfix on 0.1.2.1-alpha.
25758 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25759 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25760 - Add a missing safe_str() call for a debug log message.
25761 - Use 64 bits instead of 32 bits for connection identifiers used with
25762 the controller protocol, to greatly reduce risk of identifier reuse.
25763 - Make the autoconf script accept the obsolete --with-ssl-dir
25764 option as an alias for the actually-working --with-openssl-dir
25765 option. Fix the help documentation to recommend --with-openssl-dir.
25766 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25769 - Rate-limit too-many-sockets messages: when they happen, they happen
25770 a lot. Resolves bug 748.
25771 - Resist DNS poisoning a little better by making sure that names in
25772 answer sections match.
25773 - Print the SOCKS5 error message string as well as the error code
25774 when a tor-resolve request fails. Patch from Jacob.
25777 Changes in version 0.2.1.4-alpha - 2008-08-04
25778 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25781 - The address part of exit policies was not correctly written
25782 to router descriptors. This generated router descriptors that failed
25783 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25785 - Tor triggered a false assert when extending a circuit to a relay
25786 but we already have a connection open to that relay. Noticed by
25787 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25790 - Fix a hidden service logging bug: in some edge cases, the router
25791 descriptor of a previously picked introduction point becomes
25792 obsolete and we need to give up on it rather than continually
25793 complaining that it has become obsolete. Observed by xiando. Bugfix
25796 o Removed features:
25797 - Take out the TestVia config option, since it was a workaround for
25798 a bug that was fixed in Tor 0.1.1.21.
25801 Changes in version 0.2.1.3-alpha - 2008-08-03
25802 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25803 infinite-length circuit attacks (see proposal 110); fixes a bug that
25804 might cause exit relays to corrupt streams they send back; allows
25805 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25806 ExcludeExitNodes config options; and fixes a big pile of bugs.
25808 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25809 - Send a bootstrap problem "warn" event on the first problem if the
25810 reason is NO_ROUTE (that is, our network is down).
25813 - Implement most of proposal 110: The first K cells to be sent
25814 along a circuit are marked as special "early" cells; only K "early"
25815 cells will be allowed. Once this code is universal, we can block
25816 certain kinds of DOS attack by requiring that EXTEND commands must
25817 be sent using an "early" cell.
25820 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25821 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25822 on the client side when connecting to a hidden service. Bugfix
25823 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25824 - Ensure that two circuits can never exist on the same connection
25825 with the same circuit ID, even if one is marked for close. This
25826 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25829 - When relays do their initial bandwidth measurement, don't limit
25830 to just our entry guards for the test circuits. Otherwise we tend
25831 to have multiple test circuits going through a single entry guard,
25832 which makes our bandwidth test less accurate. Fixes part of bug 654;
25833 patch contributed by Josh Albrecht.
25834 - Add an ExcludeExitNodes option so users can list a set of nodes
25835 that should be be excluded from the exit node position, but
25836 allowed elsewhere. Implements proposal 151.
25837 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25838 ExcludeNodes and ExcludeExitNodes lists.
25839 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25840 be more efficient. Formerly it was quadratic in the number of
25841 servers; now it should be linear. Fixes bug 509.
25842 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25843 and n_conn_id_digest fields into a separate structure that's
25844 only needed when the circuit has not yet attached to an n_conn.
25847 - Change the contrib/tor.logrotate script so it makes the new
25848 logs as "_tor:_tor" rather than the default, which is generally
25849 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25850 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25851 warnings (occasionally), but it can also cause the compiler to
25852 eliminate error-checking code. Suggested by Peter Gutmann.
25853 - When a hidden service is giving up on an introduction point candidate
25854 that was not included in the last published rendezvous descriptor,
25855 don't reschedule publication of the next descriptor. Fixes bug 763.
25857 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25858 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25859 and nobody claims to be using them. Fixes bug 754. Bugfix on
25860 0.1.0.1-rc. Patch from Christian Wilms.
25861 - Fix a small alignment and memory-wasting bug on buffer chunks.
25864 o Minor bugfixes (controller):
25865 - When closing an application-side connection because its circuit
25866 is getting torn down, generate the stream event correctly.
25867 Bugfix on 0.1.2.x. Anonymous patch.
25869 o Removed features:
25870 - Remove all backward-compatibility code to support relays running
25871 versions of Tor so old that they no longer work at all on the
25875 Changes in version 0.2.0.30 - 2008-07-15
25877 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25878 warnings (occasionally), but it can also cause the compiler to
25879 eliminate error-checking code. Suggested by Peter Gutmann.
25882 Changes in version 0.2.0.29-rc - 2008-07-08
25883 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25884 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25887 - If you have more than one bridge but don't know their keys,
25888 you would only launch a request for the descriptor of the first one
25889 on your list. (Tor considered launching requests for the others, but
25890 found that it already had a connection on the way for $0000...0000
25891 so it didn't open another.) Bugfix on 0.2.0.x.
25892 - If you have more than one bridge but don't know their keys, and the
25893 connection to one of the bridges failed, you would cancel all
25894 pending bridge connections. (After all, they all have the same
25895 digest.) Bugfix on 0.2.0.x.
25896 - When a hidden service was trying to establish an introduction point,
25897 and Tor had built circuits preemptively for such purposes, we
25898 were ignoring all the preemptive circuits and launching a new one
25899 instead. Bugfix on 0.2.0.14-alpha.
25900 - When a hidden service was trying to establish an introduction point,
25901 and Tor *did* manage to reuse one of the preemptively built
25902 circuits, it didn't correctly remember which one it used,
25903 so it asked for another one soon after, until there were no
25904 more preemptive circuits, at which point it launched one from
25905 scratch. Bugfix on 0.0.9.x.
25906 - Make directory servers include the X-Your-Address-Is: http header in
25907 their responses even for begin_dir conns. Now clients who only
25908 ever use begin_dir connections still have a way to learn their IP
25909 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25912 - Fix a macro/CPP interaction that was confusing some compilers:
25913 some GCCs don't like #if/#endif pairs inside macro arguments.
25915 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25916 Fixes bug 704; fix from Steven Murdoch.
25917 - When opening /dev/null in finish_daemonize(), do not pass the
25918 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25919 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25920 - Correctly detect transparent proxy support on Linux hosts that
25921 require in.h to be included before netfilter_ipv4.h. Patch
25923 - Disallow session resumption attempts during the renegotiation
25924 stage of the v2 handshake protocol. Clients should never be trying
25925 session resumption at this point, but apparently some did, in
25926 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
25927 found by Geoff Goodell.
25930 Changes in version 0.2.1.2-alpha - 2008-06-20
25931 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
25932 make it easier to set up your own private Tor network; fixes several
25933 big bugs with using more than one bridge relay; fixes a big bug with
25934 offering hidden services quickly after Tor starts; and uses a better
25935 API for reporting potential bootstrapping problems to the controller.
25938 - New TestingTorNetwork config option to allow adjustment of
25939 previously constant values that, while reasonable, could slow
25940 bootstrapping. Implements proposal 135. Patch from Karsten.
25943 - If you have more than one bridge but don't know their digests,
25944 you would only learn a request for the descriptor of the first one
25945 on your list. (Tor considered launching requests for the others, but
25946 found that it already had a connection on the way for $0000...0000
25947 so it didn't open another.) Bugfix on 0.2.0.x.
25948 - If you have more than one bridge but don't know their digests,
25949 and the connection to one of the bridges failed, you would cancel
25950 all pending bridge connections. (After all, they all have the
25951 same digest.) Bugfix on 0.2.0.x.
25952 - When establishing a hidden service, introduction points that
25953 originate from cannibalized circuits are completely ignored and not
25954 included in rendezvous service descriptors. This might be another
25955 reason for delay in making a hidden service available. Bugfix
25956 from long ago (0.0.9.x?)
25959 - Allow OpenSSL to use dynamic locks if it wants.
25960 - When building a consensus, do not include routers that are down.
25961 This will cut down 30% to 40% on consensus size. Implements
25963 - In directory authorities' approved-routers files, allow
25964 fingerprints with or without space.
25965 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
25966 controller can query our current bootstrap state in case it attaches
25967 partway through and wants to catch up.
25968 - Send an initial "Starting" bootstrap status event, so we have a
25969 state to start out in.
25972 - Asking for a conditional consensus at .../consensus/<fingerprints>
25973 would crash a dirserver if it did not already have a
25974 consensus. Bugfix on 0.2.1.1-alpha.
25975 - Clean up some macro/CPP interactions: some GCC versions don't like
25976 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
25979 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
25980 - Directory authorities shouldn't complain about bootstrapping
25981 problems just because they do a lot of reachability testing and
25982 some of the connection attempts fail.
25983 - Start sending "count" and "recommendation" key/value pairs in
25984 bootstrap problem status events, so the controller can hear about
25985 problems even before Tor decides they're worth reporting for sure.
25986 - If you're using bridges, generate "bootstrap problem" warnings
25987 as soon as you run out of working bridges, rather than waiting
25988 for ten failures -- which will never happen if you have less than
25990 - If we close our OR connection because there's been a circuit
25991 pending on it for too long, we were telling our bootstrap status
25992 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
25995 Changes in version 0.2.1.1-alpha - 2008-06-13
25996 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
25997 were making the Tor process bloat especially on Linux; makes our TLS
25998 handshake blend in better; sends "bootstrap phase" status events to
25999 the controller, so it can keep the user informed of progress (and
26000 problems) fetching directory information and establishing circuits;
26001 and adds a variety of smaller features.
26004 - More work on making our TLS handshake blend in: modify the list
26005 of ciphers advertised by OpenSSL in client mode to even more
26006 closely resemble a common web browser. We cheat a little so that
26007 we can advertise ciphers that the locally installed OpenSSL doesn't
26009 - Start sending "bootstrap phase" status events to the controller,
26010 so it can keep the user informed of progress fetching directory
26011 information and establishing circuits. Also inform the controller
26012 if we think we're stuck at a particular bootstrap phase. Implements
26014 - Resume using OpenSSL's RAND_poll() for better (and more portable)
26015 cross-platform entropy collection again. We used to use it, then
26016 stopped using it because of a bug that could crash systems that
26017 called RAND_poll when they had a lot of fds open. It looks like the
26018 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
26019 at startup, and to call RAND_poll() when we reseed later only if
26020 we have a non-buggy OpenSSL version.
26023 - When we choose to abandon a new entry guard because we think our
26024 older ones might be better, close any circuits pending on that
26025 new entry guard connection. This fix should make us recover much
26026 faster when our network is down and then comes back. Bugfix on
26027 0.1.2.8-beta; found by lodger.
26029 o Memory fixes and improvements:
26030 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
26031 to avoid unused RAM in buffer chunks and memory pools.
26032 - Speed up parsing and cut down on memory fragmentation by using
26033 stack-style allocations for parsing directory objects. Previously,
26034 this accounted for over 40% of allocations from within Tor's code
26035 on a typical directory cache.
26036 - Use a Bloom filter rather than a digest-based set to track which
26037 descriptors we need to keep around when we're cleaning out old
26038 router descriptors. This speeds up the computation significantly,
26039 and may reduce fragmentation.
26040 - Reduce the default smartlist size from 32 to 16; it turns out that
26041 most smartlists hold around 8-12 elements tops.
26042 - Make dumpstats() log the fullness and size of openssl-internal
26044 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
26045 patch to their OpenSSL, turn it on to save memory on servers. This
26046 patch will (with any luck) get included in a mainline distribution
26048 - Never use OpenSSL compression: it wastes RAM and CPU trying to
26049 compress cells, which are basically all encrypted, compressed,
26053 - Stop reloading the router list from disk for no reason when we
26054 run out of reachable directory mirrors. Once upon a time reloading
26055 it would set the 'is_running' flag back to 1 for them. It hasn't
26056 done that for a long time.
26057 - In very rare situations new hidden service descriptors were
26058 published earlier than 30 seconds after the last change to the
26059 service. (We currently think that a hidden service descriptor
26060 that's been stable for 30 seconds is worth publishing.)
26063 - Allow separate log levels to be configured for different logging
26064 domains. For example, this allows one to log all notices, warnings,
26065 or errors, plus all memory management messages of level debug or
26066 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
26067 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
26068 and stop using a warning that had become unfixably verbose under
26070 - New --hush command-line option similar to --quiet. While --quiet
26071 disables all logging to the console on startup, --hush limits the
26072 output to messages of warning and error severity.
26073 - Servers support a new URL scheme for consensus downloads that
26074 allows the client to specify which authorities are trusted.
26075 The server then only sends the consensus if the client will trust
26076 it. Otherwise a 404 error is sent back. Clients use this
26077 new scheme when the server supports it (meaning it's running
26078 0.2.1.1-alpha or later). Implements proposal 134.
26079 - New configure/torrc options (--enable-geoip-stats,
26080 DirRecordUsageByCountry) to record how many IPs we've served
26081 directory info to in each country code, how many status documents
26082 total we've sent to each country code, and what share of the total
26083 directory requests we should expect to see.
26084 - Use the TLS1 hostname extension to more closely resemble browser
26086 - Lots of new unit tests.
26087 - Add a macro to implement the common pattern of iterating through
26088 two parallel lists in lockstep.
26091 Changes in version 0.2.0.28-rc - 2008-06-13
26092 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
26093 performance bug, and fixes a bunch of smaller bugs.
26096 - Fix a bug where, when we were choosing the 'end stream reason' to
26097 put in our relay end cell that we send to the exit relay, Tor
26098 clients on Windows were sometimes sending the wrong 'reason'. The
26099 anonymity problem is that exit relays may be able to guess whether
26100 the client is running Windows, thus helping partition the anonymity
26101 set. Down the road we should stop sending reasons to exit relays,
26102 or otherwise prevent future versions of this bug.
26105 - While setting up a hidden service, some valid introduction circuits
26106 were overlooked and abandoned. This might be the reason for
26107 the long delay in making a hidden service available. Bugfix on
26111 - Update to the "June 9 2008" ip-to-country file.
26112 - Run 'make test' as part of 'make dist', so we stop releasing so
26113 many development snapshots that fail their unit tests.
26116 - When we're checking if we have enough dir info for each relay
26117 to begin establishing circuits, make sure that we actually have
26118 the descriptor listed in the consensus, not just any descriptor.
26120 - Bridge relays no longer print "xx=0" in their extrainfo document
26121 for every single country code in the geoip db. Bugfix on
26123 - Only warn when we fail to load the geoip file if we were planning to
26124 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
26125 - If we change our MaxAdvertisedBandwidth and then reload torrc,
26126 Tor won't realize it should publish a new relay descriptor. Fixes
26127 bug 688, reported by mfr. Bugfix on 0.1.2.x.
26128 - When we haven't had any application requests lately, don't bother
26129 logging that we have expired a bunch of descriptors. Bugfix
26131 - Make relay cells written on a connection count as non-padding when
26132 tracking how long a connection has been in use. Bugfix on
26133 0.2.0.1-alpha. Spotted by lodger.
26134 - Fix unit tests in 0.2.0.27-rc.
26135 - Fix compile on Windows.
26138 Changes in version 0.2.0.27-rc - 2008-06-03
26139 Tor 0.2.0.27-rc adds a few features we left out of the earlier
26140 release candidates. In particular, we now include an IP-to-country
26141 GeoIP database, so controllers can easily look up what country a
26142 given relay is in, and so bridge relays can give us some sanitized
26143 summaries about which countries are making use of bridges. (See proposal
26144 126-geoip-fetching.txt for details.)
26147 - Include an IP-to-country GeoIP file in the tarball, so bridge
26148 relays can report sanitized summaries of the usage they're seeing.
26151 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
26152 Robert Hogan. Fixes the first part of bug 681.
26153 - Make bridge authorities never serve extrainfo docs.
26154 - Add support to detect Libevent versions in the 1.4.x series
26156 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
26157 - Include a new contrib/tor-exit-notice.html file that exit relay
26158 operators can put on their website to help reduce abuse queries.
26161 - When tunneling an encrypted directory connection, and its first
26162 circuit fails, do not leave it unattached and ask the controller
26163 to deal. Fixes the second part of bug 681.
26164 - Make bridge authorities correctly expire old extrainfo documents
26168 Changes in version 0.2.0.26-rc - 2008-05-13
26169 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
26170 in Debian's OpenSSL packages. All users running any 0.2.0.x version
26171 should upgrade, whether they're running Debian or not.
26173 o Major security fixes:
26174 - Use new V3 directory authority keys on the tor26, gabelmoo, and
26175 moria1 V3 directory authorities. The old keys were generated with
26176 a vulnerable version of Debian's OpenSSL package, and must be
26177 considered compromised. Other authorities' keys were not generated
26178 with an affected version of OpenSSL.
26181 - List authority signatures as "unrecognized" based on DirServer
26182 lines, not on cert cache. Bugfix on 0.2.0.x.
26185 - Add a new V3AuthUseLegacyKey option to make it easier for
26186 authorities to change their identity keys if they have to.
26189 Changes in version 0.2.0.25-rc - 2008-04-23
26190 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
26193 - Remember to initialize threading before initializing logging.
26194 Otherwise, many BSD-family implementations will crash hard on
26195 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
26198 - Authorities correctly free policies on bad servers on
26199 exit. Fixes bug 672. Bugfix on 0.2.0.x.
26202 Changes in version 0.2.0.24-rc - 2008-04-22
26203 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
26204 v3 directory authority, makes relays with dynamic IP addresses and no
26205 DirPort notice more quickly when their IP address changes, fixes a few
26206 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
26208 o New directory authorities:
26209 - Take lefkada out of the list of v3 directory authorities, since
26210 it has been down for months.
26211 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
26215 - Detect address changes more quickly on non-directory mirror
26216 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
26218 o Minor features (security):
26219 - Reject requests for reverse-dns lookup of names that are in
26220 a private address space. Patch from lodger.
26221 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
26224 o Minor bugfixes (crashes):
26225 - Avoid a rare assert that can trigger when Tor doesn't have much
26226 directory information yet and it tries to fetch a v2 hidden
26227 service descriptor. Fixes bug 651, reported by nwf.
26228 - Initialize log mutex before initializing dmalloc. Otherwise,
26229 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
26230 - Use recursive pthread mutexes in order to avoid deadlock when
26231 logging debug-level messages to a controller. Bug spotted by nwf,
26232 bugfix on 0.2.0.16-alpha.
26234 o Minor bugfixes (resource management):
26235 - Keep address policies from leaking memory: start their refcount
26236 at 1, not 2. Bugfix on 0.2.0.16-alpha.
26237 - Free authority certificates on exit, so they don't look like memory
26238 leaks. Bugfix on 0.2.0.19-alpha.
26239 - Free static hashtables for policy maps and for TLS connections on
26240 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
26241 - Avoid allocating extra space when computing consensuses on 64-bit
26242 platforms. Bug spotted by aakova.
26244 o Minor bugfixes (misc):
26245 - Do not read the configuration file when we've only been told to
26246 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
26247 based on patch from Sebastian Hahn.
26248 - Exit relays that are used as a client can now reach themselves
26249 using the .exit notation, rather than just launching an infinite
26250 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
26251 - When attempting to open a logfile fails, tell us why.
26252 - Fix a dumb bug that was preventing us from knowing that we should
26253 preemptively build circuits to handle expected directory requests.
26254 Fixes bug 660. Bugfix on 0.1.2.x.
26255 - Warn less verbosely about clock skew from netinfo cells from
26256 untrusted sources. Fixes bug 663.
26257 - Make controller stream events for DNS requests more consistent,
26258 by adding "new stream" events for DNS requests, and removing
26259 spurious "stream closed" events" for cached reverse resolves.
26260 Patch from mwenge. Fixes bug 646.
26261 - Correctly notify one-hop connections when a circuit build has
26262 failed. Possible fix for bug 669. Found by lodger.
26265 Changes in version 0.2.0.23-rc - 2008-03-24
26266 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
26267 makes bootstrapping faster if the first directory mirror you contact
26268 is down. The bundles also include the new Vidalia 0.1.2 release.
26271 - When a tunneled directory request is made to a directory server
26272 that's down, notice after 30 seconds rather than 120 seconds. Also,
26273 fail any begindir streams that are pending on it, so they can
26274 retry elsewhere. This was causing multi-minute delays on bootstrap.
26277 Changes in version 0.2.0.22-rc - 2008-03-18
26278 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
26279 enables encrypted directory connections by default for non-relays, fixes
26280 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
26281 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
26284 - Enable encrypted directory connections by default for non-relays,
26285 so censor tools that block Tor directory connections based on their
26286 plaintext patterns will no longer work. This means Tor works in
26287 certain censored countries by default again.
26290 - Make sure servers always request certificates from clients during
26291 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
26292 - Do not enter a CPU-eating loop when a connection is closed in
26293 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
26294 diagnosed by lodger; bugfix on 0.2.0.20-rc.
26295 - Fix assertion failure that could occur when a blocked circuit
26296 became unblocked, and it had pending client DNS requests. Bugfix
26297 on 0.2.0.1-alpha. Fixes bug 632.
26299 o Minor bugfixes (on 0.1.2.x):
26300 - Generate "STATUS_SERVER" events rather than misspelled
26301 "STATUS_SEVER" events. Caught by mwenge.
26302 - When counting the number of bytes written on a TLS connection,
26303 look at the BIO actually used for writing to the network, not
26304 at the BIO used (sometimes) to buffer data for the network.
26305 Looking at different BIOs could result in write counts on the
26306 order of ULONG_MAX. Fixes bug 614.
26307 - On Windows, correctly detect errors when listing the contents of
26308 a directory. Fix from lodger.
26310 o Minor bugfixes (on 0.2.0.x):
26311 - Downgrade "sslv3 alert handshake failure" message to INFO.
26312 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
26313 left BandwidthRate and BandwidthBurst at the default, we would be
26314 silently limited by those defaults. Now raise them to match the
26315 RelayBandwidth* values.
26316 - Fix the SVK version detection logic to work correctly on a branch.
26317 - Make --enable-openbsd-malloc work correctly on Linux with alpha
26318 CPUs. Fixes bug 625.
26319 - Logging functions now check that the passed severity is sane.
26320 - Use proper log levels in the testsuite call of
26321 get_interface_address6().
26322 - When using a nonstandard malloc, do not use the platform values for
26323 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
26324 - Make the openbsd malloc code use 8k pages on alpha CPUs and
26326 - Detect mismatched page sizes when using --enable-openbsd-malloc.
26327 - Avoid double-marked-for-close warning when certain kinds of invalid
26328 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
26329 for bug 617. Bugfix on 0.2.0.1-alpha.
26330 - Make sure that the "NULL-means-reject *:*" convention is followed by
26331 all the policy manipulation functions, avoiding some possible crash
26332 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
26333 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
26334 actually works, and doesn't warn about every single reverse lookup.
26335 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
26338 - Only log guard node status when guard node status has changed.
26339 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
26340 make "INFO" 75% less verbose.
26343 Changes in version 0.2.0.21-rc - 2008-03-02
26344 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
26345 makes Tor work well with Vidalia again, fixes a rare assert bug,
26346 and fixes a pair of more minor bugs. The bundles also include Vidalia
26347 0.1.0 and Torbutton 1.1.16.
26350 - The control port should declare that it requires password auth
26351 when HashedControlSessionPassword is set too. Patch from Matt Edman;
26352 bugfix on 0.2.0.20-rc. Fixes bug 615.
26353 - Downgrade assert in connection_buckets_decrement() to a log message.
26354 This may help us solve bug 614, and in any case will make its
26355 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
26356 - We were sometimes miscounting the number of bytes read from the
26357 network, causing our rate limiting to not be followed exactly.
26358 Bugfix on 0.2.0.16-alpha. Reported by lodger.
26361 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
26362 OpenSSL versions should have been working fine. Diagnosis and patch
26363 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
26364 Bugfix on 0.2.0.20-rc.
26367 Changes in version 0.2.0.20-rc - 2008-02-24
26368 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
26369 makes more progress towards normalizing Tor's TLS handshake, makes
26370 hidden services work better again, helps relays bootstrap if they don't
26371 know their IP address, adds optional support for linking in openbsd's
26372 allocator or tcmalloc, allows really fast relays to scale past 15000
26373 sockets, and fixes a bunch of minor bugs reported by Veracode.
26376 - Enable the revised TLS handshake based on the one designed by
26377 Steven Murdoch in proposal 124, as revised in proposal 130. It
26378 includes version negotiation for OR connections as described in
26379 proposal 105. The new handshake is meant to be harder for censors
26380 to fingerprint, and it adds the ability to detect certain kinds of
26381 man-in-the-middle traffic analysis attacks. The version negotiation
26382 feature will allow us to improve Tor's link protocol more safely
26384 - Choose which bridge to use proportional to its advertised bandwidth,
26385 rather than uniformly at random. This should speed up Tor for
26386 bridge users. Also do this for people who set StrictEntryNodes.
26387 - When a TrackHostExits-chosen exit fails too many times in a row,
26388 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
26391 - Resolved problems with (re-)fetching hidden service descriptors.
26392 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
26393 and 0.2.0.19-alpha.
26394 - If we only ever used Tor for hidden service lookups or posts, we
26395 would stop building circuits and start refusing connections after
26396 24 hours, since we falsely believed that Tor was dormant. Reported
26397 by nwf; bugfix on 0.1.2.x.
26398 - Servers that don't know their own IP address should go to the
26399 authorities for their first directory fetch, even if their DirPort
26400 is off or if they don't know they're reachable yet. This will help
26401 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
26402 - When counting the number of open sockets, count not only the number
26403 of sockets we have received from the socket() call, but also
26404 the number we've gotten from accept() and socketpair(). This bug
26405 made us fail to count all sockets that we were using for incoming
26406 connections. Bugfix on 0.2.0.x.
26407 - Fix code used to find strings within buffers, when those strings
26408 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
26409 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
26410 - Add a new __HashedControlSessionPassword option for controllers
26411 to use for one-off session password hashes that shouldn't get
26412 saved to disk by SAVECONF --- Vidalia users were accumulating a
26413 pile of HashedControlPassword lines in their torrc files, one for
26414 each time they had restarted Tor and then clicked Save. Make Tor
26415 automatically convert "HashedControlPassword" to this new option but
26416 only when it's given on the command line. Partial fix for bug 586.
26418 o Minor features (performance):
26419 - Tune parameters for cell pool allocation to minimize amount of
26421 - Add OpenBSD malloc code from phk as an optional malloc
26422 replacement on Linux: some glibc libraries do very poorly
26423 with Tor's memory allocation patterns. Pass
26424 --enable-openbsd-malloc to get the replacement malloc code.
26425 - Add a --with-tcmalloc option to the configure script to link
26426 against tcmalloc (if present). Does not yet search for
26427 non-system include paths.
26428 - Stop imposing an arbitrary maximum on the number of file descriptors
26429 used for busy servers. Bug reported by Olaf Selke; patch from
26432 o Minor features (other):
26433 - When SafeLogging is disabled, log addresses along with all TLS
26435 - When building with --enable-gcc-warnings, check for whether Apple's
26436 warning "-Wshorten-64-to-32" is available.
26437 - Add a --passphrase-fd argument to the tor-gencert command for
26440 o Minor bugfixes (memory leaks and code problems):
26441 - We were leaking a file descriptor if Tor started with a zero-length
26442 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
26443 - Detect size overflow in zlib code. Reported by Justin Ferguson and
26445 - We were comparing the raw BridgePassword entry with a base64'ed
26446 version of it, when handling a "/tor/networkstatus-bridges"
26447 directory request. Now compare correctly. Noticed by Veracode.
26448 - Recover from bad tracked-since value in MTBF-history file.
26449 Should fix bug 537.
26450 - Alter the code that tries to recover from unhandled write
26451 errors, to not try to flush onto a socket that's given us
26452 unhandled errors. Bugfix on 0.1.2.x.
26453 - Make Unix controlsockets work correctly on OpenBSD. Patch from
26454 tup. Bugfix on 0.2.0.3-alpha.
26456 o Minor bugfixes (other):
26457 - If we have an extra-info document for our server, always make
26458 it available on the control port, even if we haven't gotten
26459 a copy of it from an authority yet. Patch from mwenge.
26460 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
26461 - Directory mirrors no longer include a guess at the client's IP
26462 address if the connection appears to be coming from the same /24
26463 network; it was producing too many wrong guesses.
26464 - Make the new hidden service code respect the SafeLogging setting.
26465 Bugfix on 0.2.0.x. Patch from Karsten.
26466 - When starting as an authority, do not overwrite all certificates
26467 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
26468 - If we're trying to flush the last bytes on a connection (for
26469 example, when answering a directory request), reset the
26470 time-to-give-up timeout every time we manage to write something
26471 on the socket. Bugfix on 0.1.2.x.
26472 - Change the behavior of "getinfo status/good-server-descriptor"
26473 so it doesn't return failure when any authority disappears.
26474 - Even though the man page said that "TrackHostExits ." should
26475 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
26476 - Report TLS "zero return" case as a "clean close" and "IO error"
26477 as a "close". Stop calling closes "unexpected closes": existing
26478 Tors don't use SSL_close(), so having a connection close without
26479 the TLS shutdown handshake is hardly unexpected.
26480 - Send NAMESERVER_STATUS messages for a single failed nameserver
26483 o Code simplifications and refactoring:
26484 - Remove the tor_strpartition function: its logic was confused,
26485 and it was only used for one thing that could be implemented far
26489 Changes in version 0.2.0.19-alpha - 2008-02-09
26490 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
26491 handshake, makes path selection for relays more secure and IP address
26492 guessing more robust, and generally fixes a lot of bugs in preparation
26493 for calling the 0.2.0 branch stable.
26496 - Do not include recognizeable strings in the commonname part of
26497 Tor's x509 certificates.
26500 - If we're a relay, avoid picking ourselves as an introduction point,
26501 a rendezvous point, or as the final hop for internal circuits. Bug
26502 reported by taranis and lodger. Bugfix on 0.1.2.x.
26503 - Patch from "Andrew S. Lists" to catch when we contact a directory
26504 mirror at IP address X and he says we look like we're coming from
26505 IP address X. Bugfix on 0.1.2.x.
26507 o Minor features (security):
26508 - Be more paranoid about overwriting sensitive memory on free(),
26509 as a defensive programming tactic to ensure forward secrecy.
26511 o Minor features (directory authority):
26512 - Actually validate the options passed to AuthDirReject,
26513 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
26514 - Reject router descriptors with out-of-range bandwidthcapacity or
26515 bandwidthburst values.
26517 o Minor features (controller):
26518 - Reject controller commands over 1MB in length. This keeps rogue
26519 processes from running us out of memory.
26521 o Minor features (misc):
26522 - Give more descriptive well-formedness errors for out-of-range
26523 hidden service descriptor/protocol versions.
26524 - Make memory debugging information describe more about history
26525 of cell allocation, so we can help reduce our memory use.
26527 o Deprecated features (controller):
26528 - The status/version/num-versioning and status/version/num-concurring
26529 GETINFO options are no longer useful in the v3 directory protocol:
26530 treat them as deprecated, and warn when they're used.
26533 - When our consensus networkstatus has been expired for a while, stop
26534 being willing to build circuits using it. Fixes bug 401. Bugfix
26536 - Directory caches now fetch certificates from all authorities
26537 listed in a networkstatus consensus, even when they do not
26538 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
26539 - When connecting to a bridge without specifying its key, insert
26540 the connection into the identity-to-connection map as soon as
26541 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
26542 - Detect versions of OS X where malloc_good_size() is present in the
26543 library but never actually declared. Resolves bug 587. Bugfix
26545 - Stop incorrectly truncating zlib responses to directory authority
26546 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
26547 - Stop recommending that every server operator send mail to tor-ops.
26548 Resolves bug 597. Bugfix on 0.1.2.x.
26549 - Don't trigger an assert if we start a directory authority with a
26550 private IP address (like 127.0.0.1).
26551 - Avoid possible failures when generating a directory with routers
26552 with over-long versions strings, or too many flags set. Bugfix
26554 - If an attempt to launch a DNS resolve request over the control
26555 port fails because we have overrun the limit on the number of
26556 connections, tell the controller that the request has failed.
26557 - Avoid using too little bandwidth when our clock skips a few
26558 seconds. Bugfix on 0.1.2.x.
26559 - Fix shell error when warning about missing packages in configure
26560 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
26561 - Do not become confused when receiving a spurious VERSIONS-like
26562 cell from a confused v1 client. Bugfix on 0.2.0.x.
26563 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
26564 introduction points for a hidden service have failed. Patch from
26565 Karsten Loesing. Bugfix on 0.2.0.x.
26567 o Code simplifications and refactoring:
26568 - Remove some needless generality from cpuworker code, for improved
26570 - Stop overloading the circuit_t.onionskin field for both "onionskin
26571 from a CREATE cell that we are waiting for a cpuworker to be
26572 assigned" and "onionskin from an EXTEND cell that we are going to
26573 send to an OR as soon as we are connected". Might help with bug 600.
26574 - Add an in-place version of aes_crypt() so that we can avoid doing a
26575 needless memcpy() call on each cell payload.
26578 Changes in version 0.2.0.18-alpha - 2008-01-25
26579 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
26580 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
26581 that can warn or reject connections to ports generally associated with
26582 vulnerable-plaintext protocols.
26584 o New directory authorities:
26585 - Set up dannenberg (run by CCC) as the sixth v3 directory
26589 - Fix a major memory leak when attempting to use the v2 TLS
26590 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
26591 - We accidentally enabled the under-development v2 TLS handshake
26592 code, which was causing log entries like "TLS error while
26593 renegotiating handshake". Disable it again. Resolves bug 590.
26594 - We were computing the wrong Content-Length: header for directory
26595 responses that need to be compressed on the fly, causing clients
26596 asking for those items to always fail. Bugfix on 0.2.0.x; partially
26600 - Avoid going directly to the directory authorities even if you're a
26601 relay, if you haven't found yourself reachable yet or if you've
26602 decided not to advertise your dirport yet. Addresses bug 556.
26603 - If we've gone 12 hours since our last bandwidth check, and we
26604 estimate we have less than 50KB bandwidth capacity but we could
26605 handle more, do another bandwidth test.
26606 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
26607 Tor can warn and/or refuse connections to ports commonly used with
26608 vulnerable-plaintext protocols. Currently we warn on ports 23,
26609 109, 110, and 143, but we don't reject any.
26612 - When we setconf ClientOnly to 1, close any current OR and Dir
26613 listeners. Reported by mwenge.
26614 - When we get a consensus that's been signed by more people than
26615 we expect, don't log about it; it's not a big deal. Reported
26619 - Don't answer "/tor/networkstatus-bridges" directory requests if
26620 the request isn't encrypted.
26621 - Make "ClientOnly 1" config option disable directory ports too.
26622 - Patches from Karsten Loesing to make v2 hidden services more
26623 robust: work even when there aren't enough HSDir relays available;
26624 retry when a v2 rend desc fetch fails; but don't retry if we
26625 already have a usable v0 rend desc.
26628 Changes in version 0.2.0.17-alpha - 2008-01-17
26629 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
26632 - Make the tor-gencert man page get included correctly in the tarball.
26635 Changes in version 0.2.0.16-alpha - 2008-01-17
26636 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
26637 Loesing, and generally cleans up a lot of features and minor bugs.
26639 o New directory authorities:
26640 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
26643 o Major performance improvements:
26644 - Switch our old ring buffer implementation for one more like that
26645 used by free Unix kernels. The wasted space in a buffer with 1mb
26646 of data will now be more like 8k than 1mb. The new implementation
26647 also avoids realloc();realloc(); patterns that can contribute to
26648 memory fragmentation.
26651 - Configuration files now accept C-style strings as values. This
26652 helps encode characters not allowed in the current configuration
26653 file format, such as newline or #. Addresses bug 557.
26654 - Although we fixed bug 539 (where servers would send HTTP status 503
26655 responses _and_ send a body too), there are still servers out
26656 there that haven't upgraded. Therefore, make clients parse such
26657 bodies when they receive them.
26658 - When we're not serving v2 directory information, there is no reason
26659 to actually keep any around. Remove the obsolete files and directory
26660 on startup if they are very old and we aren't going to serve them.
26662 o Minor performance improvements:
26663 - Reference-count and share copies of address policy entries; only 5%
26664 of them were actually distinct.
26665 - Never walk through the list of logs if we know that no log is
26666 interested in a given message.
26669 - When an authority has not signed a consensus, do not try to
26670 download a nonexistent "certificate with key 00000000". Bugfix
26671 on 0.2.0.x. Fixes bug 569.
26672 - Fix a rare assert error when we're closing one of our threads:
26673 use a mutex to protect the list of logs, so we never write to the
26674 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
26675 bug 575, which is kind of the revenge of bug 222.
26676 - Patch from Karsten Loesing to complain less at both the client
26677 and the relay when a relay used to have the HSDir flag but doesn't
26678 anymore, and we try to upload a hidden service descriptor.
26679 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
26681 - Do not try to download missing certificates until we have tried
26682 to check our fallback consensus. Fixes bug 583.
26683 - Make bridges round reported GeoIP stats info up to the nearest
26684 estimate, not down. Now we can distinguish between "0 people from
26685 this country" and "1 person from this country".
26686 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
26687 - Avoid possible segfault if key generation fails in
26688 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
26689 - Avoid segfault in the case where a badly behaved v2 versioning
26690 directory sends a signed networkstatus with missing client-versions.
26692 - Avoid segfaults on certain complex invocations of
26693 router_get_by_hexdigest(). Bugfix on 0.1.2.
26694 - Correct bad index on array access in parse_http_time(). Bugfix
26696 - Fix possible bug in vote generation when server versions are present
26697 but client versions are not.
26698 - Fix rare bug on REDIRECTSTREAM control command when called with no
26699 port set: it could erroneously report an error when none had
26701 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
26702 compressing large objects and find ourselves with more than 4k
26703 left over. Bugfix on 0.2.0.
26704 - Fix a small memory leak when setting up a hidden service.
26705 - Fix a few memory leaks that could in theory happen under bizarre
26707 - Fix an assert if we post a general-purpose descriptor via the
26708 control port but that descriptor isn't mentioned in our current
26709 network consensus. Bug reported by Jon McLachlan; bugfix on
26712 o Minor features (controller):
26713 - Get NS events working again. Patch from tup.
26714 - The GETCONF command now escapes and quotes configuration values
26715 that don't otherwise fit into the torrc file.
26716 - The SETCONF command now handles quoted values correctly.
26718 o Minor features (directory authorities):
26719 - New configuration options to override default maximum number of
26720 servers allowed on a single IP address. This is important for
26721 running a test network on a single host.
26722 - Actually implement the -s option to tor-gencert.
26723 - Add a manual page for tor-gencert.
26725 o Minor features (bridges):
26726 - Bridge authorities no longer serve bridge descriptors over
26727 unencrypted connections.
26729 o Minor features (other):
26730 - Add hidden services and DNSPorts to the list of things that make
26731 Tor accept that it has running ports. Change starting Tor with no
26732 ports from a fatal error to a warning; we might change it back if
26733 this turns out to confuse anybody. Fixes bug 579.
26736 Changes in version 0.1.2.19 - 2008-01-17
26737 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26738 exit policy a little bit more conservative so it's safer to run an
26739 exit relay on a home system, and fixes a variety of smaller issues.
26742 - Exit policies now reject connections that are addressed to a
26743 relay's public (external) IP address too, unless
26744 ExitPolicyRejectPrivate is turned off. We do this because too
26745 many relays are running nearby to services that trust them based
26746 on network address.
26749 - When the clock jumps forward a lot, do not allow the bandwidth
26750 buckets to become negative. Fixes bug 544.
26751 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26752 on every successful resolve. Reported by Mike Perry.
26753 - Purge old entries from the "rephist" database and the hidden
26754 service descriptor database even when DirPort is zero.
26755 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26756 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26757 crashing or mis-answering these requests.
26758 - When we decide to send a 503 response to a request for servers, do
26759 not then also send the server descriptors: this defeats the whole
26760 purpose. Fixes bug 539.
26763 - Changing the ExitPolicyRejectPrivate setting should cause us to
26764 rebuild our server descriptor.
26765 - Fix handling of hex nicknames when answering controller requests for
26766 networkstatus by name, or when deciding whether to warn about
26767 unknown routers in a config option. (Patch from mwenge.)
26768 - Fix a couple of hard-to-trigger autoconf problems that could result
26769 in really weird results on platforms whose sys/types.h files define
26770 nonstandard integer types.
26771 - Don't try to create the datadir when running --verify-config or
26772 --hash-password. Resolves bug 540.
26773 - If we were having problems getting a particular descriptor from the
26774 directory caches, and then we learned about a new descriptor for
26775 that router, we weren't resetting our failure count. Reported
26777 - Although we fixed bug 539 (where servers would send HTTP status 503
26778 responses _and_ send a body too), there are still servers out there
26779 that haven't upgraded. Therefore, make clients parse such bodies
26780 when they receive them.
26781 - Run correctly on systems where rlim_t is larger than unsigned long.
26782 This includes some 64-bit systems.
26783 - Run correctly on platforms (like some versions of OS X 10.5) where
26784 the real limit for number of open files is OPEN_FILES, not rlim_max
26785 from getrlimit(RLIMIT_NOFILES).
26786 - Avoid a spurious free on base64 failure.
26787 - Avoid segfaults on certain complex invocations of
26788 router_get_by_hexdigest().
26789 - Fix rare bug on REDIRECTSTREAM control command when called with no
26790 port set: it could erroneously report an error when none had
26794 Changes in version 0.2.0.15-alpha - 2007-12-25
26795 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26796 features added in 0.2.0.13-alpha.
26799 - Fix several remotely triggerable asserts based on DirPort requests
26800 for a v2 or v3 networkstatus object before we were prepared. This
26801 was particularly bad for 0.2.0.13 and later bridge relays, who
26802 would never have a v2 networkstatus and would thus always crash
26803 when used. Bugfixes on 0.2.0.x.
26804 - Estimate the v3 networkstatus size more accurately, rather than
26805 estimating it at zero bytes and giving it artificially high priority
26806 compared to other directory requests. Bugfix on 0.2.0.x.
26809 - Fix configure.in logic for cross-compilation.
26810 - When we load a bridge descriptor from the cache, and it was
26811 previously unreachable, mark it as retriable so we won't just
26812 ignore it. Also, try fetching a new copy immediately. Bugfixes
26814 - The bridge GeoIP stats were counting other relays, for example
26815 self-reachability and authority-reachability tests.
26818 - Support compilation to target iPhone; patch from cjacker huang.
26819 To build for iPhone, pass the --enable-iphone option to configure.
26822 Changes in version 0.2.0.14-alpha - 2007-12-23
26824 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26825 without a datadirectory from a previous Tor install. Reported
26827 - Fix a crash when we fetch a descriptor that turns out to be
26828 unexpected (it used to be in our networkstatus when we started
26829 fetching it, but it isn't in our current networkstatus), and we
26830 aren't using bridges. Bugfix on 0.2.0.x.
26831 - Fix a crash when accessing hidden services: it would work the first
26832 time you use a given introduction point for your service, but
26833 on subsequent requests we'd be using garbage memory. Fixed by
26834 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26835 - Fix a crash when we load a bridge descriptor from disk but we don't
26836 currently have a Bridge line for it in our torrc. Bugfix on
26840 - If bridge authorities set BridgePassword, they will serve a
26841 snapshot of known bridge routerstatuses from their DirPort to
26842 anybody who knows that password. Unset by default.
26845 - Make the unit tests build again.
26846 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26847 - Make PublishServerDescriptor default to 1, so the default doesn't
26848 have to change as we invent new directory protocol versions.
26849 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26850 be included unless sys/time.h is already included. Fixes
26851 bug 553. Bugfix on 0.2.0.x.
26852 - If we receive a general-purpose descriptor and then receive an
26853 identical bridge-purpose descriptor soon after, don't discard
26854 the next one as a duplicate.
26857 - If BridgeRelay is set to 1, then the default for
26858 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26859 - If the user sets RelayBandwidthRate but doesn't set
26860 RelayBandwidthBurst, then make them equal rather than erroring out.
26863 Changes in version 0.2.0.13-alpha - 2007-12-21
26864 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26865 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26868 o New directory authorities:
26869 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26873 - Only update guard status (usable / not usable) once we have
26874 enough directory information. This was causing us to always pick
26875 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26876 causing us to discard all our guards on startup if we hadn't been
26877 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26878 - Purge old entries from the "rephist" database and the hidden
26879 service descriptor databases even when DirPort is zero. Bugfix
26881 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26882 after opening a circuit -- even a relayed circuit. Bugfix on
26884 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26885 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26886 crashing or mis-answering these types of requests.
26887 - Relays were publishing their server descriptor to v1 and v2
26888 directory authorities, but they didn't try publishing to v3-only
26889 authorities. Fix this; and also stop publishing to v1 authorities.
26891 - When we were reading router descriptors from cache, we were ignoring
26892 the annotations -- so for example we were reading in bridge-purpose
26893 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26894 - When we decided to send a 503 response to a request for servers, we
26895 were then also sending the server descriptors: this defeats the
26896 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26899 - Bridge relays now behave like clients with respect to time
26900 intervals for downloading new consensus documents -- otherwise they
26901 stand out. Bridge users now wait until the end of the interval,
26902 so their bridge relay will be sure to have a new consensus document.
26903 - Three new config options (AlternateDirAuthority,
26904 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26905 user selectively replace the default directory authorities by type,
26906 rather than the all-or-nothing replacement that DirServer offers.
26907 - Tor can now be configured to read a GeoIP file from disk in one
26908 of two formats. This can be used by controllers to map IP addresses
26909 to countries. Eventually, it may support exit-by-country.
26910 - When possible, bridge relays remember which countries users
26911 are coming from, and report aggregate information in their
26912 extra-info documents, so that the bridge authorities can learn
26913 where Tor is blocked.
26914 - Bridge directory authorities now do reachability testing on the
26915 bridges they know. They provide router status summaries to the
26916 controller via "getinfo ns/purpose/bridge", and also dump summaries
26917 to a file periodically.
26918 - Stop fetching directory info so aggressively if your DirPort is
26919 on but your ORPort is off; stop fetching v2 dir info entirely.
26920 You can override these choices with the new FetchDirInfoEarly
26924 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
26925 consensus documents when there are too many relays at a single
26926 IP address. Now clear it in v2 network status documents too, and
26927 also clear it in routerinfo_t when the relay is no longer listed
26928 in the relevant networkstatus document.
26929 - Don't crash if we get an unexpected value for the
26930 PublishServerDescriptor config option. Reported by Matt Edman;
26931 bugfix on 0.2.0.9-alpha.
26932 - Our new v2 hidden service descriptor format allows descriptors
26933 that have no introduction points. But Tor crashed when we tried
26934 to build a descriptor with no intro points (and it would have
26935 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
26936 by Karsten Loesing.
26937 - Fix building with dmalloc 5.5.2 with glibc.
26938 - Reject uploaded descriptors and extrainfo documents if they're
26939 huge. Otherwise we'll cache them all over the network and it'll
26940 clog everything up. Reported by Aljosha Judmayer.
26941 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
26942 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
26943 - When the DANGEROUS_VERSION controller status event told us we're
26944 running an obsolete version, it used the string "OLD" to describe
26945 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
26946 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
26947 - If we can't expand our list of entry guards (e.g. because we're
26948 using bridges or we have StrictEntryNodes set), don't mark relays
26949 down when they fail a directory request. Otherwise we're too quick
26950 to mark all our entry points down. Bugfix on 0.1.2.x.
26951 - Fix handling of hex nicknames when answering controller requests for
26952 networkstatus by name, or when deciding whether to warn about unknown
26953 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
26954 - Fix a couple of hard-to-trigger autoconf problems that could result
26955 in really weird results on platforms whose sys/types.h files define
26956 nonstandard integer types. Bugfix on 0.1.2.x.
26957 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
26958 - Don't crash on name lookup when we have no current consensus. Fixes
26959 bug 538; bugfix on 0.2.0.x.
26960 - Only Tors that want to mirror the v2 directory info should
26961 create the "cached-status" directory in their datadir. (All Tors
26962 used to create it.) Bugfix on 0.2.0.9-alpha.
26963 - Directory authorities should only automatically download Extra Info
26964 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
26967 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
26968 consumers. (We already do this on HUP.)
26969 - Authorities and caches fetch the v2 networkstatus documents
26970 less often, now that v3 is encouraged.
26971 - Add a new config option BridgeRelay that specifies you want to
26972 be a bridge relay. Right now the only difference is that it makes
26973 you answer begin_dir requests, and it makes you cache dir info,
26974 even if your DirPort isn't on.
26975 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
26976 ask about source, timestamp of arrival, purpose, etc. We need
26977 something like this to help Vidalia not do GeoIP lookups on bridge
26979 - Allow multiple HashedControlPassword config lines, to support
26980 multiple controller passwords.
26981 - Authorities now decide whether they're authoritative for a given
26982 router based on the router's purpose.
26983 - New config options AuthDirBadDir and AuthDirListBadDirs for
26984 authorities to mark certain relays as "bad directories" in the
26985 networkstatus documents. Also supports the "!baddir" directive in
26986 the approved-routers file.
26989 Changes in version 0.2.0.12-alpha - 2007-11-16
26990 This twelfth development snapshot fixes some more build problems as
26991 well as a few minor bugs.
26994 - Make it build on OpenBSD again. Patch from tup.
26995 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
26996 package-building for Red Hat, OS X, etc.
26998 o Minor bugfixes (on 0.1.2.x):
26999 - Changing the ExitPolicyRejectPrivate setting should cause us to
27000 rebuild our server descriptor.
27002 o Minor bugfixes (on 0.2.0.x):
27003 - When we're lacking a consensus, don't try to perform rendezvous
27004 operations. Reported by Karsten Loesing.
27005 - Fix a small memory leak whenever we decide against using a
27006 newly picked entry guard. Reported by Mike Perry.
27007 - When authorities detected more than two relays running on the same
27008 IP address, they were clearing all the status flags but forgetting
27009 to clear the "hsdir" flag. So clients were being told that a
27010 given relay was the right choice for a v2 hsdir lookup, yet they
27011 never had its descriptor because it was marked as 'not running'
27013 - If we're trying to fetch a bridge descriptor and there's no way
27014 the bridge authority could help us (for example, we don't know
27015 a digest, or there is no bridge authority), don't be so eager to
27016 fall back to asking the bridge authority.
27017 - If we're using bridges or have strictentrynodes set, and our
27018 chosen exit is in the same family as all our bridges/entry guards,
27019 then be flexible about families.
27022 - When we negotiate a v2 link-layer connection (not yet implemented),
27023 accept RELAY_EARLY cells and turn them into RELAY cells if we've
27024 negotiated a v1 connection for their next step. Initial code for
27028 Changes in version 0.2.0.11-alpha - 2007-11-12
27029 This eleventh development snapshot fixes some build problems with
27030 the previous snapshot. It also includes a more secure-by-default exit
27031 policy for relays, fixes an enormous memory leak for exit relays, and
27032 fixes another bug where servers were falling out of the directory list.
27035 - Exit policies now reject connections that are addressed to a
27036 relay's public (external) IP address too, unless
27037 ExitPolicyRejectPrivate is turned off. We do this because too
27038 many relays are running nearby to services that trust them based
27039 on network address. Bugfix on 0.1.2.x.
27042 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
27043 on every successful resolve. Reported by Mike Perry; bugfix
27045 - On authorities, never downgrade to old router descriptors simply
27046 because they're listed in the consensus. This created a catch-22
27047 where we wouldn't list a new descriptor because there was an
27048 old one in the consensus, and we couldn't get the new one in the
27049 consensus because we wouldn't list it. Possible fix for bug 548.
27050 Also, this might cause bug 543 to appear on authorities; if so,
27051 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
27053 o Packaging fixes on 0.2.0.10-alpha:
27054 - We were including instructions about what to do with the
27055 src/config/fallback-consensus file, but we weren't actually
27056 including it in the tarball. Disable all of that for now.
27059 - Allow people to say PreferTunnelledDirConns rather than
27060 PreferTunneledDirConns, for those alternate-spellers out there.
27063 - Don't reevaluate all the information from our consensus document
27064 just because we've downloaded a v2 networkstatus that we intend
27065 to cache. Fixes bug 545; bugfix on 0.2.0.x.
27068 Changes in version 0.2.0.10-alpha - 2007-11-10
27069 This tenth development snapshot adds a third v3 directory authority
27070 run by Mike Perry, adds most of Karsten Loesing's new hidden service
27071 descriptor format, fixes a bad crash bug and new bridge bugs introduced
27072 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
27073 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
27074 addresses many more minor issues.
27076 o New directory authorities:
27077 - Set up ides (run by Mike Perry) as the third v3 directory authority.
27080 - Allow tunnelled directory connections to ask for an encrypted
27081 "begin_dir" connection or an anonymized "uses a full Tor circuit"
27082 connection independently. Now we can make anonymized begin_dir
27083 connections for (e.g.) more secure hidden service posting and
27085 - More progress on proposal 114: code from Karsten Loesing to
27086 implement new hidden service descriptor format.
27087 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
27088 accommodate the growing number of servers that use the default
27089 and are reaching it.
27090 - Directory authorities use a new formula for selecting which nodes
27091 to advertise as Guards: they must be in the top 7/8 in terms of
27092 how long we have known about them, and above the median of those
27093 nodes in terms of weighted fractional uptime.
27094 - Make "not enough dir info yet" warnings describe *why* Tor feels
27095 it doesn't have enough directory info yet.
27098 - Stop servers from crashing if they set a Family option (or
27099 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
27101 - Make bridge users work again -- the move to v3 directories in
27102 0.2.0.9-alpha had introduced a number of bugs that made bridges
27103 no longer work for clients.
27104 - When the clock jumps forward a lot, do not allow the bandwidth
27105 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
27107 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
27108 - When the consensus lists a router descriptor that we previously were
27109 mirroring, but that we considered non-canonical, reload the
27110 descriptor as canonical. This fixes bug 543 where Tor servers
27111 would start complaining after a few days that they don't have
27112 enough directory information to build a circuit.
27113 - Consider replacing the current consensus when certificates arrive
27114 that make the pending consensus valid. Previously, we were only
27115 considering replacement when the new certs _didn't_ help.
27116 - Fix an assert error on startup if we didn't already have the
27117 consensus and certs cached in our datadirectory: we were caching
27118 the consensus in consensus_waiting_for_certs but then free'ing it
27120 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
27121 Request) if we need more v3 certs but we've already got pending
27122 requests for all of them.
27123 - Correctly back off from failing certificate downloads. Fixes
27125 - Authorities don't vote on the Running flag if they have been running
27126 for less than 30 minutes themselves. Fixes bug 547, where a newly
27127 started authority would vote that everyone was down.
27129 o New requirements:
27130 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
27131 it, it had no AES, and it hasn't seen any security patches since
27135 - Clients now hold circuitless TLS connections open for 1.5 times
27136 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
27137 rebuild a new circuit over them within that timeframe. Previously,
27138 they held them open only for KeepalivePeriod (5 minutes).
27139 - Use "If-Modified-Since" to avoid retrieving consensus
27140 networkstatuses that we already have.
27141 - When we have no consensus, check FallbackNetworkstatusFile (defaults
27142 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
27143 we start knowing some directory caches.
27144 - When we receive a consensus from the future, warn about skew.
27145 - Improve skew reporting: try to give the user a better log message
27146 about how skewed they are, and how much this matters.
27147 - When we have a certificate for an authority, believe that
27148 certificate's claims about the authority's IP address.
27149 - New --quiet command-line option to suppress the default console log.
27150 Good in combination with --hash-password.
27151 - Authorities send back an X-Descriptor-Not-New header in response to
27152 an accepted-but-discarded descriptor upload. Partially implements
27154 - Make the log message for "tls error. breaking." more useful.
27155 - Better log messages about certificate downloads, to attempt to
27156 track down the second incarnation of bug 546.
27158 o Minor features (bridges):
27159 - If bridge users set UpdateBridgesFromAuthority, but the digest
27160 they ask for is a 404 from the bridge authority, they now fall
27161 back to trying the bridge directly.
27162 - Bridges now use begin_dir to publish their server descriptor to
27163 the bridge authority, even when they haven't set TunnelDirConns.
27165 o Minor features (controller):
27166 - When reporting clock skew, and we know that the clock is _at least
27167 as skewed_ as some value, but we don't know the actual value,
27168 report the value as a "minimum skew."
27171 - Update linux-tor-prio.sh script to allow QoS based on the uid of
27172 the Tor process. Patch from Marco Bonetti with tweaks from Mike
27176 - Refuse to start if both ORPort and UseBridges are set. Bugfix
27177 on 0.2.0.x, suggested by Matt Edman.
27178 - Don't stop fetching descriptors when FetchUselessDescriptors is
27179 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
27180 reported by tup and ioerror.
27181 - Better log message on vote from unknown authority.
27182 - Don't log "Launching 0 request for 0 router" message.
27184 o Minor bugfixes (memory leaks):
27185 - Stop leaking memory every time we parse a v3 certificate. Bugfix
27187 - Stop leaking memory every time we load a v3 certificate. Bugfix
27188 on 0.2.0.1-alpha. Fixes bug 536.
27189 - Stop leaking a cached networkstatus on exit. Bugfix on
27191 - Stop leaking voter information every time we free a consensus.
27192 Bugfix on 0.2.0.3-alpha.
27193 - Stop leaking signed data every time we check a voter signature.
27194 Bugfix on 0.2.0.3-alpha.
27195 - Stop leaking a signature every time we fail to parse a consensus or
27196 a vote. Bugfix on 0.2.0.3-alpha.
27197 - Stop leaking v2_download_status_map on shutdown. Bugfix on
27199 - Stop leaking conn->nickname every time we make a connection to a
27200 Tor relay without knowing its expected identity digest (e.g. when
27201 using bridges). Bugfix on 0.2.0.3-alpha.
27203 - Minor bugfixes (portability):
27204 - Run correctly on platforms where rlim_t is larger than unsigned
27205 long, and/or where the real limit for number of open files is
27206 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
27207 particular, these may be needed for OS X 10.5.
27210 Changes in version 0.1.2.18 - 2007-10-28
27211 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
27212 hidden service introduction that were causing huge delays, and a big
27213 bug that was causing some servers to disappear from the network status
27214 lists for a few hours each day.
27216 o Major bugfixes (crashes):
27217 - If a connection is shut down abruptly because of something that
27218 happened inside connection_flushed_some(), do not call
27219 connection_finished_flushing(). Should fix bug 451:
27220 "connection_stop_writing: Assertion conn->write_event failed"
27221 Bugfix on 0.1.2.7-alpha.
27222 - Fix possible segfaults in functions called from
27223 rend_process_relay_cell().
27225 o Major bugfixes (hidden services):
27226 - Hidden services were choosing introduction points uniquely by
27227 hexdigest, but when constructing the hidden service descriptor
27228 they merely wrote the (potentially ambiguous) nickname.
27229 - Clients now use the v2 intro format for hidden service
27230 connections: they specify their chosen rendezvous point by identity
27231 digest rather than by (potentially ambiguous) nickname. These
27232 changes could speed up hidden service connections dramatically.
27234 o Major bugfixes (other):
27235 - Stop publishing a new server descriptor just because we get a
27236 HUP signal. This led (in a roundabout way) to some servers getting
27237 dropped from the networkstatus lists for a few hours each day.
27238 - When looking for a circuit to cannibalize, consider family as well
27239 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27240 circuit cannibalization).
27241 - When a router wasn't listed in a new networkstatus, we were leaving
27242 the flags for that router alone -- meaning it remained Named,
27243 Running, etc -- even though absence from the networkstatus means
27244 that it shouldn't be considered to exist at all anymore. Now we
27245 clear all the flags for routers that fall out of the networkstatus
27246 consensus. Fixes bug 529.
27249 - Don't try to access (or alter) the state file when running
27250 --list-fingerprint or --verify-config or --hash-password. Resolves
27252 - When generating information telling us how to extend to a given
27253 router, do not try to include the nickname if it is
27254 absent. Resolves bug 467.
27255 - Fix a user-triggerable segfault in expand_filename(). (There isn't
27256 a way to trigger this remotely.)
27257 - When sending a status event to the controller telling it that an
27258 OR address is reachable, set the port correctly. (Previously we
27259 were reporting the dir port.)
27260 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27261 command. Bugfix on 0.1.2.17.
27262 - When loading bandwidth history, do not believe any information in
27263 the future. Fixes bug 434.
27264 - When loading entry guard information, do not believe any information
27266 - When we have our clock set far in the future and generate an
27267 onion key, then re-set our clock to be correct, we should not stop
27268 the onion key from getting rotated.
27269 - On some platforms, accept() can return a broken address. Detect
27270 this more quietly, and deal accordingly. Fixes bug 483.
27271 - It's not actually an error to find a non-pending entry in the DNS
27272 cache when canceling a pending resolve. Don't log unless stuff
27273 is fishy. Resolves bug 463.
27274 - Don't reset trusted dir server list when we set a configuration
27275 option. Patch from Robert Hogan.
27276 - Don't try to create the datadir when running --verify-config or
27277 --hash-password. Resolves bug 540.
27280 Changes in version 0.2.0.9-alpha - 2007-10-24
27281 This ninth development snapshot switches clients to the new v3 directory
27282 system; allows servers to be listed in the network status even when they
27283 have the same nickname as a registered server; and fixes many other
27284 bugs including a big one that was causing some servers to disappear
27285 from the network status lists for a few hours each day.
27287 o Major features (directory system):
27288 - Clients now download v3 consensus networkstatus documents instead
27289 of v2 networkstatus documents. Clients and caches now base their
27290 opinions about routers on these consensus documents. Clients only
27291 download router descriptors listed in the consensus.
27292 - Authorities now list servers who have the same nickname as
27293 a different named server, but list them with a new flag,
27294 "Unnamed". Now we can list servers that happen to pick the same
27295 nickname as a server that registered two years ago and then
27296 disappeared. Partially implements proposal 122.
27297 - If the consensus lists a router as "Unnamed", the name is assigned
27298 to a different router: do not identify the router by that name.
27299 Partially implements proposal 122.
27300 - Authorities can now come to a consensus on which method to use to
27301 compute the consensus. This gives us forward compatibility.
27304 - Stop publishing a new server descriptor just because we HUP or
27305 when we find our DirPort to be reachable but won't actually publish
27306 it. New descriptors without any real changes are dropped by the
27307 authorities, and can screw up our "publish every 18 hours" schedule.
27309 - When a router wasn't listed in a new networkstatus, we were leaving
27310 the flags for that router alone -- meaning it remained Named,
27311 Running, etc -- even though absence from the networkstatus means
27312 that it shouldn't be considered to exist at all anymore. Now we
27313 clear all the flags for routers that fall out of the networkstatus
27314 consensus. Fixes bug 529; bugfix on 0.1.2.x.
27315 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
27316 extrainfo documents and then discard them immediately for not
27317 matching the latest router. Bugfix on 0.2.0.1-alpha.
27319 o Minor features (v3 directory protocol):
27320 - Allow tor-gencert to generate a new certificate without replacing
27322 - Allow certificates to include an address.
27323 - When we change our directory-cache settings, reschedule all voting
27324 and download operations.
27325 - Reattempt certificate downloads immediately on failure, as long as
27326 we haven't failed a threshold number of times yet.
27327 - Delay retrying consensus downloads while we're downloading
27328 certificates to verify the one we just got. Also, count getting a
27329 consensus that we already have (or one that isn't valid) as a failure,
27330 and count failing to get the certificates after 20 minutes as a
27332 - Build circuits and download descriptors even if our consensus is a
27333 little expired. (This feature will go away once authorities are
27336 o Minor features (router descriptor cache):
27337 - If we find a cached-routers file that's been sitting around for more
27338 than 28 days unmodified, then most likely it's a leftover from
27339 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
27341 - When we (as a cache) download a descriptor because it was listed
27342 in a consensus, remember when the consensus was supposed to expire,
27343 and don't expire the descriptor until then.
27345 o Minor features (performance):
27346 - Call routerlist_remove_old_routers() much less often. This should
27347 speed startup, especially on directory caches.
27348 - Don't try to launch new descriptor downloads quite so often when we
27349 already have enough directory information to build circuits.
27350 - Base64 decoding was actually showing up on our profile when parsing
27351 the initial descriptor file; switch to an in-process all-at-once
27352 implementation that's about 3.5x times faster than calling out to
27355 o Minor features (compilation):
27356 - Detect non-ASCII platforms (if any still exist) and refuse to
27357 build there: some of our code assumes that 'A' is 65 and so on.
27359 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
27360 - Make the "next period" votes into "current period" votes immediately
27361 after publishing the consensus; avoid a heisenbug that made them
27362 stick around indefinitely.
27363 - When we discard a vote as a duplicate, do not report this as
27365 - Treat missing v3 keys or certificates as an error when running as a
27366 v3 directory authority.
27367 - When we're configured to be a v3 authority, but we're only listed
27368 as a non-v3 authority in our DirServer line for ourself, correct
27370 - If an authority doesn't have a qualified hostname, just put
27371 its address in the vote. This fixes the problem where we referred to
27372 "moria on moria:9031."
27373 - Distinguish between detached signatures for the wrong period, and
27374 detached signatures for a divergent vote.
27375 - Fix a small memory leak when computing a consensus.
27376 - When there's no consensus, we were forming a vote every 30
27377 minutes, but writing the "valid-after" line in our vote based
27378 on our configured V3AuthVotingInterval: so unless the intervals
27379 matched up, we immediately rejected our own vote because it didn't
27380 start at the voting interval that caused us to construct a vote.
27382 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
27383 - Delete unverified-consensus when the real consensus is set.
27384 - Consider retrying a consensus networkstatus fetch immediately
27385 after one fails: don't wait 60 seconds to notice.
27386 - When fetching a consensus as a cache, wait until a newer consensus
27387 should exist before trying to replace the current one.
27388 - Use a more forgiving schedule for retrying failed consensus
27389 downloads than for other types.
27391 o Minor bugfixes (other directory issues):
27392 - Correct the implementation of "download votes by digest." Bugfix on
27394 - Authorities no longer send back "400 you're unreachable please fix
27395 it" errors to Tor servers that aren't online all the time. We're
27396 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
27398 o Minor bugfixes (controller):
27399 - Don't reset trusted dir server list when we set a configuration
27400 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
27401 - Respond to INT and TERM SIGNAL commands before we execute the
27402 signal, in case the signal shuts us down. We had a patch in
27403 0.1.2.1-alpha that tried to do this by queueing the response on
27404 the connection's buffer before shutting down, but that really
27405 isn't the same thing at all. Bug located by Matt Edman.
27407 o Minor bugfixes (misc):
27408 - Correctly check for bad options to the "PublishServerDescriptor"
27409 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
27410 - Stop leaking memory on failing case of base32_decode, and make
27411 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
27412 - Don't try to download extrainfo documents when we're trying to
27413 fetch enough directory info to build a circuit: having enough
27414 info should get priority. Bugfix on 0.2.0.x.
27415 - Don't complain that "your server has not managed to confirm that its
27416 ports are reachable" if we haven't been able to build any circuits
27417 yet. Bug found by spending four hours without a v3 consensus. Bugfix
27419 - Detect the reason for failing to mmap a descriptor file we just
27420 wrote, and give a more useful log message. Fixes bug 533. Bugfix
27423 o Code simplifications and refactoring:
27424 - Remove support for the old bw_accounting file: we've been storing
27425 bandwidth accounting information in the state file since
27426 0.1.2.5-alpha. This may result in bandwidth accounting errors
27427 if you try to upgrade from 0.1.1.x or earlier, or if you try to
27428 downgrade to 0.1.1.x or earlier.
27429 - New convenience code to locate a file within the DataDirectory.
27430 - Move non-authority functionality out of dirvote.c.
27431 - Refactor the arguments for router_pick_{directory_|trusteddir}server
27432 so that they all take the same named flags.
27435 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
27436 Unix users an easy way to script their Tor process (e.g. by
27437 adjusting bandwidth based on the time of the day).
27440 Changes in version 0.2.0.8-alpha - 2007-10-12
27441 This eighth development snapshot fixes a crash bug that's been bothering
27442 us since February 2007, lets bridge authorities store a list of bridge
27443 descriptors they've seen, gets v3 directory voting closer to working,
27444 starts caching v3 directory consensus documents on directory mirrors,
27445 and fixes a variety of smaller issues including some minor memory leaks.
27447 o Major features (router descriptor cache):
27448 - Store routers in a file called cached-descriptors instead of in
27449 cached-routers. Initialize cached-descriptors from cached-routers
27450 if the old format is around. The new format allows us to store
27451 annotations along with descriptors.
27452 - Use annotations to record the time we received each descriptor, its
27453 source, and its purpose.
27454 - Disable the SETROUTERPURPOSE controller command: it is now
27456 - Controllers should now specify cache=no or cache=yes when using
27457 the +POSTDESCRIPTOR command.
27458 - Bridge authorities now write bridge descriptors to disk, meaning
27459 we can export them to other programs and begin distributing them
27462 o Major features (directory authorities):
27463 - When a v3 authority is missing votes or signatures, it now tries
27465 - Directory authorities track weighted fractional uptime as well as
27466 weighted mean-time-between failures. WFU is suitable for deciding
27467 whether a node is "usually up", while MTBF is suitable for deciding
27468 whether a node is "likely to stay up." We need both, because
27469 "usually up" is a good requirement for guards, while "likely to
27470 stay up" is a good requirement for long-lived connections.
27472 o Major features (v3 directory system):
27473 - Caches now download v3 network status documents as needed,
27474 and download the descriptors listed in them.
27475 - All hosts now attempt to download and keep fresh v3 authority
27476 certificates, and re-attempt after failures.
27477 - More internal-consistency checks for vote parsing.
27479 o Major bugfixes (crashes):
27480 - If a connection is shut down abruptly because of something that
27481 happened inside connection_flushed_some(), do not call
27482 connection_finished_flushing(). Should fix bug 451. Bugfix on
27485 o Major bugfixes (performance):
27486 - Fix really bad O(n^2) performance when parsing a long list of
27487 routers: Instead of searching the entire list for an "extra-info "
27488 string which usually wasn't there, once for every routerinfo
27489 we read, just scan lines forward until we find one we like.
27491 - When we add data to a write buffer in response to the data on that
27492 write buffer getting low because of a flush, do not consider the
27493 newly added data as a candidate for immediate flushing, but rather
27494 make it wait until the next round of writing. Otherwise, we flush
27495 and refill recursively, and a single greedy TLS connection can
27496 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
27498 o Minor features (v3 authority system):
27499 - Add more ways for tools to download the votes that lead to the
27501 - Send a 503 when low on bandwidth and a vote, consensus, or
27502 certificate is requested.
27503 - If-modified-since is now implemented properly for all kinds of
27504 certificate requests.
27506 o Minor bugfixes (network statuses):
27507 - Tweak the implementation of proposal 109 slightly: allow at most
27508 two Tor servers on the same IP address, except if it's the location
27509 of a directory authority, in which case allow five. Bugfix on
27512 o Minor bugfixes (controller):
27513 - When sending a status event to the controller telling it that an
27514 OR address is reachable, set the port correctly. (Previously we
27515 were reporting the dir port.) Bugfix on 0.1.2.x.
27517 o Minor bugfixes (v3 directory system):
27518 - Fix logic to look up a cert by its signing key digest. Bugfix on
27520 - Only change the reply to a vote to "OK" if it's not already
27521 set. This gets rid of annoying "400 OK" log messages, which may
27522 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
27523 - When we get a valid consensus, recompute the voting schedule.
27524 - Base the valid-after time of a vote on the consensus voting
27525 schedule, not on our preferred schedule.
27526 - Make the return values and messages from signature uploads and
27527 downloads more sensible.
27528 - Fix a memory leak when serving votes and consensus documents, and
27529 another when serving certificates.
27531 o Minor bugfixes (performance):
27532 - Use a slightly simpler string hashing algorithm (copying Python's
27533 instead of Java's) and optimize our digest hashing algorithm to take
27534 advantage of 64-bit platforms and to remove some possibly-costly
27536 - Fix a minor memory leak whenever we parse guards from our state
27537 file. Bugfix on 0.2.0.7-alpha.
27538 - Fix a minor memory leak whenever we write out a file. Bugfix on
27540 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27541 command. Bugfix on 0.2.0.5-alpha.
27543 o Minor bugfixes (portability):
27544 - On some platforms, accept() can return a broken address. Detect
27545 this more quietly, and deal accordingly. Fixes bug 483.
27546 - Stop calling tor_strlower() on uninitialized memory in some cases.
27547 Bugfix in 0.2.0.7-alpha.
27549 o Minor bugfixes (usability):
27550 - Treat some 403 responses from directory servers as INFO rather than
27551 WARN-severity events.
27552 - It's not actually an error to find a non-pending entry in the DNS
27553 cache when canceling a pending resolve. Don't log unless stuff is
27554 fishy. Resolves bug 463.
27556 o Minor bugfixes (anonymity):
27557 - Never report that we've used more bandwidth than we're willing to
27558 relay: it leaks how much non-relay traffic we're using. Resolves
27560 - When looking for a circuit to cannibalize, consider family as well
27561 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27562 circuit cannibalization).
27564 o Code simplifications and refactoring:
27565 - Make a bunch of functions static. Remove some dead code.
27566 - Pull out about a third of the really big routerlist.c; put it in a
27567 new module, networkstatus.c.
27568 - Merge the extra fields in local_routerstatus_t back into
27569 routerstatus_t: we used to need one routerstatus_t for each
27570 authority's opinion, plus a local_routerstatus_t for the locally
27571 computed consensus opinion. To save space, we put the locally
27572 modified fields into local_routerstatus_t, and only the common
27573 stuff into routerstatus_t. But once v3 directories are in use,
27574 clients and caches will no longer need to hold authority opinions;
27575 thus, the rationale for keeping the types separate is now gone.
27576 - Make the code used to reschedule and reattempt downloads more
27578 - Turn all 'Are we a directory server/mirror?' logic into a call to
27580 - Remove the code to generate the oldest (v1) directory format.
27581 The code has been disabled since 0.2.0.5-alpha.
27584 Changes in version 0.2.0.7-alpha - 2007-09-21
27585 This seventh development snapshot makes bridges work again, makes bridge
27586 authorities work for the first time, fixes two huge performance flaws
27587 in hidden services, and fixes a variety of minor issues.
27589 o New directory authorities:
27590 - Set up moria1 and tor26 as the first v3 directory authorities. See
27591 doc/spec/dir-spec.txt for details on the new directory design.
27593 o Major bugfixes (crashes):
27594 - Fix possible segfaults in functions called from
27595 rend_process_relay_cell(). Bugfix on 0.1.2.x.
27597 o Major bugfixes (bridges):
27598 - Fix a bug that made servers send a "404 Not found" in response to
27599 attempts to fetch their server descriptor. This caused Tor servers
27600 to take many minutes to establish reachability for their DirPort,
27601 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
27602 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
27603 users configure that and specify a bridge with an identity
27604 fingerprint, now they will lookup the bridge descriptor at the
27605 default bridge authority via a one-hop tunnel, but once circuits
27606 are established they will switch to a three-hop tunnel for later
27607 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
27609 o Major bugfixes (hidden services):
27610 - Hidden services were choosing introduction points uniquely by
27611 hexdigest, but when constructing the hidden service descriptor
27612 they merely wrote the (potentially ambiguous) nickname.
27613 - Clients now use the v2 intro format for hidden service
27614 connections: they specify their chosen rendezvous point by identity
27615 digest rather than by (potentially ambiguous) nickname. Both
27616 are bugfixes on 0.1.2.x, and they could speed up hidden service
27617 connections dramatically. Thanks to Karsten Loesing.
27619 o Minor features (security):
27620 - As a client, do not believe any server that tells us that an
27621 address maps to an internal address space.
27622 - Make it possible to enable HashedControlPassword and
27623 CookieAuthentication at the same time.
27625 o Minor features (guard nodes):
27626 - Tag every guard node in our state file with the version that
27627 we believe added it, or with our own version if we add it. This way,
27628 if a user temporarily runs an old version of Tor and then switches
27629 back to a new one, she doesn't automatically lose her guards.
27631 o Minor features (speed):
27632 - When implementing AES counter mode, update only the portions of the
27633 counter buffer that need to change, and don't keep separate
27634 network-order and host-order counters when they are the same (i.e.,
27635 on big-endian hosts.)
27637 o Minor features (controller):
27638 - Accept LF instead of CRLF on controller, since some software has a
27639 hard time generating real Internet newlines.
27640 - Add GETINFO values for the server status events
27641 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
27644 o Removed features:
27645 - Routers no longer include bandwidth-history lines in their
27646 descriptors; this information is already available in extra-info
27647 documents, and including it in router descriptors took up 60%
27648 (!) of compressed router descriptor downloads. Completes
27649 implementation of proposal 104.
27650 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
27651 and TorControl.py, as they use the old v0 controller protocol,
27652 and are obsoleted by TorFlow anyway.
27653 - Drop support for v1 rendezvous descriptors, since we never used
27654 them anyway, and the code has probably rotted by now. Based on
27655 patch from Karsten Loesing.
27656 - On OSX, stop warning the user that kqueue support in libevent is
27657 "experimental", since it seems to have worked fine for ages.
27660 - When generating information telling us how to extend to a given
27661 router, do not try to include the nickname if it is absent. Fixes
27662 bug 467. Bugfix on 0.2.0.3-alpha.
27663 - Fix a user-triggerable (but not remotely-triggerable) segfault
27664 in expand_filename(). Bugfix on 0.1.2.x.
27665 - Fix a memory leak when freeing incomplete requests from DNSPort.
27666 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
27667 - Don't try to access (or alter) the state file when running
27668 --list-fingerprint or --verify-config or --hash-password. (Resolves
27669 bug 499.) Bugfix on 0.1.2.x.
27670 - Servers used to decline to publish their DirPort if their
27671 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
27672 were below a threshold. Now they only look at BandwidthRate and
27673 RelayBandwidthRate. Bugfix on 0.1.2.x.
27674 - Remove an optimization in the AES counter-mode code that assumed
27675 that the counter never exceeded 2^68. When the counter can be set
27676 arbitrarily as an IV (as it is by Karsten's new hidden services
27677 code), this assumption no longer holds. Bugfix on 0.1.2.x.
27678 - Resume listing "AUTHORITY" flag for authorities in network status.
27679 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
27681 o Code simplifications and refactoring:
27682 - Revamp file-writing logic so we don't need to have the entire
27683 contents of a file in memory at once before we write to disk. Tor,
27685 - Turn "descriptor store" into a full-fledged type.
27686 - Move all NT services code into a separate source file.
27687 - Unify all code that computes medians, percentile elements, etc.
27688 - Get rid of a needless malloc when parsing address policies.
27691 Changes in version 0.1.2.17 - 2007-08-30
27692 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
27693 X bundles. Vidalia 0.0.14 makes authentication required for the
27694 ControlPort in the default configuration, which addresses important
27695 security risks. Everybody who uses Vidalia (or another controller)
27698 In addition, this Tor update fixes major load balancing problems with
27699 path selection, which should speed things up a lot once many people
27702 o Major bugfixes (security):
27703 - We removed support for the old (v0) control protocol. It has been
27704 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
27705 become more of a headache than it's worth.
27707 o Major bugfixes (load balancing):
27708 - When choosing nodes for non-guard positions, weight guards
27709 proportionally less, since they already have enough load. Patch
27711 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27712 will allow fast Tor servers to get more attention.
27713 - When we're upgrading from an old Tor version, forget our current
27714 guards and pick new ones according to the new weightings. These
27715 three load balancing patches could raise effective network capacity
27716 by a factor of four. Thanks to Mike Perry for measurements.
27718 o Major bugfixes (stream expiration):
27719 - Expire not-yet-successful application streams in all cases if
27720 they've been around longer than SocksTimeout. Right now there are
27721 some cases where the stream will live forever, demanding a new
27722 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27724 o Minor features (controller):
27725 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27726 is valid before any authentication has been received. It tells
27727 a controller what kind of authentication is expected, and what
27728 protocol is spoken. Implements proposal 119.
27730 o Minor bugfixes (performance):
27731 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27732 greatly speeding up loading cached-routers from disk on startup.
27733 - Disable sentinel-based debugging for buffer code: we squashed all
27734 the bugs that this was supposed to detect a long time ago, and now
27735 its only effect is to change our buffer sizes from nice powers of
27736 two (which platform mallocs tend to like) to values slightly over
27737 powers of two (which make some platform mallocs sad).
27739 o Minor bugfixes (misc):
27740 - If exit bandwidth ever exceeds one third of total bandwidth, then
27741 use the correct formula to weight exit nodes when choosing paths.
27742 Based on patch from Mike Perry.
27743 - Choose perfectly fairly among routers when choosing by bandwidth and
27744 weighting by fraction of bandwidth provided by exits. Previously, we
27745 would choose with only approximate fairness, and correct ourselves
27746 if we ran off the end of the list.
27747 - If we require CookieAuthentication but we fail to write the
27748 cookie file, we would warn but not exit, and end up in a state
27749 where no controller could authenticate. Now we exit.
27750 - If we require CookieAuthentication, stop generating a new cookie
27751 every time we change any piece of our config.
27752 - Refuse to start with certain directory authority keys, and
27753 encourage people using them to stop.
27754 - Terminate multi-line control events properly. Original patch
27756 - Fix a minor memory leak when we fail to find enough suitable
27757 servers to choose a circuit.
27758 - Stop leaking part of the descriptor when we run into a particularly
27759 unparseable piece of it.
27762 Changes in version 0.2.0.6-alpha - 2007-08-26
27763 This sixth development snapshot features a new Vidalia version in the
27764 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27765 the ControlPort in the default configuration, which addresses important
27768 In addition, this snapshot fixes major load balancing problems
27769 with path selection, which should speed things up a lot once many
27770 people have upgraded. The directory authorities also use a new
27771 mean-time-between-failure approach to tracking which servers are stable,
27772 rather than just looking at the most recent uptime.
27774 o New directory authorities:
27775 - Set up Tonga as the default bridge directory authority.
27778 - Directory authorities now track servers by weighted
27779 mean-times-between-failures. When we have 4 or more days of data,
27780 use measured MTBF rather than declared uptime to decide whether
27781 to call a router Stable. Implements proposal 108.
27783 o Major bugfixes (load balancing):
27784 - When choosing nodes for non-guard positions, weight guards
27785 proportionally less, since they already have enough load. Patch
27787 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27788 will allow fast Tor servers to get more attention.
27789 - When we're upgrading from an old Tor version, forget our current
27790 guards and pick new ones according to the new weightings. These
27791 three load balancing patches could raise effective network capacity
27792 by a factor of four. Thanks to Mike Perry for measurements.
27794 o Major bugfixes (descriptor parsing):
27795 - Handle unexpected whitespace better in malformed descriptors. Bug
27796 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27799 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27800 GETINFO for Torstat to use until it can switch to using extrainfos.
27801 - Optionally (if built with -DEXPORTMALLINFO) export the output
27802 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27806 - Do not intermix bridge routers with controller-added
27807 routers. (Bugfix on 0.2.0.x)
27808 - Do not fail with an assert when accept() returns an unexpected
27809 address family. Addresses but does not wholly fix bug 483. (Bugfix
27811 - Let directory authorities startup even when they can't generate
27812 a descriptor immediately, e.g. because they don't know their
27814 - Stop putting the authentication cookie in a file called "0"
27815 in your working directory if you don't specify anything for the
27816 new CookieAuthFile option. Reported by Matt Edman.
27817 - Make it possible to read the PROTOCOLINFO response in a way that
27818 conforms to our control-spec. Reported by Matt Edman.
27819 - Fix a minor memory leak when we fail to find enough suitable
27820 servers to choose a circuit. Bugfix on 0.1.2.x.
27821 - Stop leaking part of the descriptor when we run into a particularly
27822 unparseable piece of it. Bugfix on 0.1.2.x.
27823 - Unmap the extrainfo cache file on exit.
27826 Changes in version 0.2.0.5-alpha - 2007-08-19
27827 This fifth development snapshot fixes compilation on Windows again;
27828 fixes an obnoxious client-side bug that slowed things down and put
27829 extra load on the network; gets us closer to using the v3 directory
27830 voting scheme; makes it easier for Tor controllers to use cookie-based
27831 authentication; and fixes a variety of other bugs.
27833 o Removed features:
27834 - Version 1 directories are no longer generated in full. Instead,
27835 authorities generate and serve "stub" v1 directories that list
27836 no servers. This will stop Tor versions 0.1.0.x and earlier from
27837 working, but (for security reasons) nobody should be running those
27840 o Major bugfixes (compilation, 0.2.0.x):
27841 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27842 - Try to fix MSVC compilation: build correctly on platforms that do
27843 not define s6_addr16 or s6_addr32.
27844 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27847 o Major bugfixes (stream expiration):
27848 - Expire not-yet-successful application streams in all cases if
27849 they've been around longer than SocksTimeout. Right now there are
27850 some cases where the stream will live forever, demanding a new
27851 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27852 reported by lodger.
27854 o Minor features (directory servers):
27855 - When somebody requests a list of statuses or servers, and we have
27856 none of those, return a 404 rather than an empty 200.
27858 o Minor features (directory voting):
27859 - Store v3 consensus status consensuses on disk, and reload them
27862 o Minor features (security):
27863 - Warn about unsafe ControlPort configurations.
27864 - Refuse to start with certain directory authority keys, and
27865 encourage people using them to stop.
27867 o Minor features (controller):
27868 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27869 is valid before any authentication has been received. It tells
27870 a controller what kind of authentication is expected, and what
27871 protocol is spoken. Implements proposal 119.
27872 - New config option CookieAuthFile to choose a new location for the
27873 cookie authentication file, and config option
27874 CookieAuthFileGroupReadable to make it group-readable.
27876 o Minor features (unit testing):
27877 - Add command-line arguments to unit-test executable so that we can
27878 invoke any chosen test from the command line rather than having
27879 to run the whole test suite at once; and so that we can turn on
27880 logging for the unit tests.
27882 o Minor bugfixes (on 0.1.2.x):
27883 - If we require CookieAuthentication but we fail to write the
27884 cookie file, we would warn but not exit, and end up in a state
27885 where no controller could authenticate. Now we exit.
27886 - If we require CookieAuthentication, stop generating a new cookie
27887 every time we change any piece of our config.
27888 - When loading bandwidth history, do not believe any information in
27889 the future. Fixes bug 434.
27890 - When loading entry guard information, do not believe any information
27892 - When we have our clock set far in the future and generate an
27893 onion key, then re-set our clock to be correct, we should not stop
27894 the onion key from getting rotated.
27895 - Clean up torrc sample config file.
27896 - Do not automatically run configure from autogen.sh. This
27897 non-standard behavior tended to annoy people who have built other
27900 o Minor bugfixes (on 0.2.0.x):
27901 - Fix a bug with AutomapHostsOnResolve that would always cause
27902 the second request to fail. Bug reported by Kate. Bugfix on
27904 - Fix a bug in ADDRMAP controller replies that would sometimes
27905 try to print a NULL. Patch from tup.
27906 - Read v3 directory authority keys from the right location.
27907 - Numerous bugfixes to directory voting code.
27910 Changes in version 0.1.2.16 - 2007-08-01
27911 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27912 remote attacker in certain situations to rewrite the user's torrc
27913 configuration file. This can completely compromise anonymity of users
27914 in most configurations, including those running the Vidalia bundles,
27915 TorK, etc. Or worse.
27917 o Major security fixes:
27918 - Close immediately after missing authentication on control port;
27919 do not allow multiple authentication attempts.
27922 Changes in version 0.2.0.4-alpha - 2007-08-01
27923 This fourth development snapshot fixes a critical security vulnerability
27924 for most users, specifically those running Vidalia, TorK, etc. Everybody
27925 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
27927 o Major security fixes:
27928 - Close immediately after missing authentication on control port;
27929 do not allow multiple authentication attempts.
27931 o Major bugfixes (compilation):
27932 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
27935 o Minor features (performance):
27936 - Be even more aggressive about releasing RAM from small
27937 empty buffers. Thanks to our free-list code, this shouldn't be too
27938 performance-intensive.
27939 - Disable sentinel-based debugging for buffer code: we squashed all
27940 the bugs that this was supposed to detect a long time ago, and
27941 now its only effect is to change our buffer sizes from nice
27942 powers of two (which platform mallocs tend to like) to values
27943 slightly over powers of two (which make some platform mallocs sad).
27944 - Log malloc statistics from mallinfo() on platforms where it
27948 Changes in version 0.2.0.3-alpha - 2007-07-29
27949 This third development snapshot introduces new experimental
27950 blocking-resistance features and a preliminary version of the v3
27951 directory voting design, and includes many other smaller features
27955 - The first pieces of our "bridge" design for blocking-resistance
27956 are implemented. People can run bridge directory authorities;
27957 people can run bridges; and people can configure their Tor clients
27958 with a set of bridges to use as the first hop into the Tor network.
27959 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
27961 - Create listener connections before we setuid to the configured
27962 User and Group. Now non-Windows users can choose port values
27963 under 1024, start Tor as root, and have Tor bind those ports
27964 before it changes to another UID. (Windows users could already
27966 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
27967 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
27968 on "vserver" accounts. (Patch from coderman.)
27969 - Be even more aggressive about separating local traffic from relayed
27970 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
27972 o Major features (experimental):
27973 - First cut of code for "v3 dir voting": directory authorities will
27974 vote on a common network status document rather than each publishing
27975 their own opinion. This code needs more testing and more corner-case
27976 handling before it's ready for use.
27979 - Directory authorities now call routers Fast if their bandwidth is
27980 at least 100KB/s, and consider their bandwidth adequate to be a
27981 Guard if it is at least 250KB/s, no matter the medians. This fix
27982 complements proposal 107. [Bugfix on 0.1.2.x]
27983 - Directory authorities now never mark more than 3 servers per IP as
27984 Valid and Running. (Implements proposal 109, by Kevin Bauer and
27986 - Minor change to organizationName and commonName generation
27987 procedures in TLS certificates during Tor handshakes, to invalidate
27988 some earlier censorware approaches. This is not a long-term
27989 solution, but applying it will give us a bit of time to look into
27990 the epidemiology of countermeasures as they spread.
27992 o Major bugfixes (directory):
27993 - Rewrite directory tokenization code to never run off the end of
27994 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
27996 o Minor features (controller):
27997 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
27998 match requests to applications. (Patch from Robert Hogan.)
27999 - Report address and port correctly on connections to DNSPort. (Patch
28000 from Robert Hogan.)
28001 - Add a RESOLVE command to launch hostname lookups. (Original patch
28002 from Robert Hogan.)
28003 - Add GETINFO status/enough-dir-info to let controllers tell whether
28004 Tor has downloaded sufficient directory information. (Patch
28006 - You can now use the ControlSocket option to tell Tor to listen for
28007 controller connections on Unix domain sockets on systems that
28008 support them. (Patch from Peter Palfrader.)
28009 - STREAM NEW events are generated for DNSPort requests and for
28010 tunneled directory connections. (Patch from Robert Hogan.)
28011 - New "GETINFO address-mappings/*" command to get address mappings
28012 with expiry information. "addr-mappings/*" is now deprecated.
28015 o Minor features (misc):
28016 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
28018 - The tor-gencert tool for v3 directory authorities now creates all
28019 files as readable to the file creator only, and write-protects
28020 the authority identity key.
28021 - When dumping memory usage, list bytes used in buffer memory
28023 - When running with dmalloc, dump more stats on hup and on exit.
28024 - Directory authorities now fail quickly and (relatively) harmlessly
28025 if they generate a network status document that is somehow
28028 o Traffic load balancing improvements:
28029 - If exit bandwidth ever exceeds one third of total bandwidth, then
28030 use the correct formula to weight exit nodes when choosing paths.
28031 (Based on patch from Mike Perry.)
28032 - Choose perfectly fairly among routers when choosing by bandwidth and
28033 weighting by fraction of bandwidth provided by exits. Previously, we
28034 would choose with only approximate fairness, and correct ourselves
28035 if we ran off the end of the list. [Bugfix on 0.1.2.x]
28037 o Performance improvements:
28038 - Be more aggressive with freeing buffer RAM or putting it on the
28040 - Use Critical Sections rather than Mutexes for synchronizing threads
28041 on win32; Mutexes are heavier-weight, and designed for synchronizing
28044 o Deprecated and removed features:
28045 - RedirectExits is now deprecated.
28046 - Stop allowing address masks that do not correspond to bit prefixes.
28047 We have warned about these for a really long time; now it's time
28048 to reject them. (Patch from croup.)
28050 o Minor bugfixes (directory):
28051 - Fix another crash bug related to extra-info caching. (Bug found by
28052 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
28053 - Directories no longer return a "304 not modified" when they don't
28054 have the networkstatus the client asked for. Also fix a memory
28055 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
28056 - We had accidentally labelled 0.1.2.x directory servers as not
28057 suitable for begin_dir requests, and had labelled no directory
28058 servers as suitable for uploading extra-info documents. [Bugfix
28061 o Minor bugfixes (dns):
28062 - Fix a crash when DNSPort is set more than once. (Patch from Robert
28063 Hogan.) [Bugfix on 0.2.0.2-alpha]
28064 - Add DNSPort connections to the global connection list, so that we
28065 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
28067 - Fix a dangling reference that could lead to a crash when DNSPort is
28068 changed or closed (Patch from Robert Hogan.) [Bugfix on
28071 o Minor bugfixes (controller):
28072 - Provide DNS expiry times in GMT, not in local time. For backward
28073 compatibility, ADDRMAP events only provide GMT expiry in an extended
28074 field. "GETINFO address-mappings" always does the right thing.
28075 - Use CRLF line endings properly in NS events.
28076 - Terminate multi-line control events properly. (Original patch
28077 from tup.) [Bugfix on 0.1.2.x-alpha]
28078 - Do not include spaces in SOURCE_ADDR fields in STREAM
28079 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
28082 Changes in version 0.1.2.15 - 2007-07-17
28083 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
28084 problems, fixes compilation on BSD, and fixes a variety of other
28085 bugs. Everybody should upgrade.
28087 o Major bugfixes (compilation):
28088 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
28090 o Major bugfixes (crashes):
28091 - Try even harder not to dereference the first character after
28092 an mmap(). Reported by lodger.
28093 - Fix a crash bug in directory authorities when we re-number the
28094 routerlist while inserting a new router.
28095 - When the cached-routers file is an even multiple of the page size,
28096 don't run off the end and crash. (Fixes bug 455; based on idea
28098 - Fix eventdns.c behavior on Solaris: It is critical to include
28099 orconfig.h _before_ sys/types.h, so that we can get the expected
28100 definition of _FILE_OFFSET_BITS.
28102 o Major bugfixes (security):
28103 - Fix a possible buffer overrun when using BSD natd support. Bug
28105 - When sending destroy cells from a circuit's origin, don't include
28106 the reason for tearing down the circuit. The spec says we didn't,
28107 and now we actually don't. Reported by lodger.
28108 - Keep streamids from different exits on a circuit separate. This
28109 bug may have allowed other routers on a given circuit to inject
28110 cells into streams. Reported by lodger; fixes bug 446.
28111 - If there's a never-before-connected-to guard node in our list,
28112 never choose any guards past it. This way we don't expand our
28113 guard list unless we need to.
28115 o Minor bugfixes (guard nodes):
28116 - Weight guard selection by bandwidth, so that low-bandwidth nodes
28117 don't get overused as guards.
28119 o Minor bugfixes (directory):
28120 - Correctly count the number of authorities that recommend each
28121 version. Previously, we were under-counting by 1.
28122 - Fix a potential crash bug when we load many server descriptors at
28123 once and some of them make others of them obsolete. Fixes bug 458.
28125 o Minor bugfixes (hidden services):
28126 - Stop tearing down the whole circuit when the user asks for a
28127 connection to a port that the hidden service didn't configure.
28130 o Minor bugfixes (misc):
28131 - On Windows, we were preventing other processes from reading
28132 cached-routers while Tor was running. Reported by janbar.
28133 - Fix a possible (but very unlikely) bug in picking routers by
28134 bandwidth. Add a log message to confirm that it is in fact
28135 unlikely. Patch from lodger.
28136 - Backport a couple of memory leak fixes.
28137 - Backport miscellaneous cosmetic bugfixes.
28140 Changes in version 0.2.0.2-alpha - 2007-06-02
28141 o Major bugfixes on 0.2.0.1-alpha:
28142 - Fix an assertion failure related to servers without extra-info digests.
28143 Resolves bugs 441 and 442.
28145 o Minor features (directory):
28146 - Support "If-Modified-Since" when answering HTTP requests for
28147 directories, running-routers documents, and network-status documents.
28148 (There's no need to support it for router descriptors, since those
28149 are downloaded by descriptor digest.)
28151 o Minor build issues:
28152 - Clear up some MIPSPro compiler warnings.
28153 - When building from a tarball on a machine that happens to have SVK
28154 installed, report the micro-revision as whatever version existed
28155 in the tarball, not as "x".
28158 Changes in version 0.2.0.1-alpha - 2007-06-01
28159 This early development snapshot provides new features for people running
28160 Tor as both a client and a server (check out the new RelayBandwidth
28161 config options); lets Tor run as a DNS proxy; and generally moves us
28162 forward on a lot of fronts.
28164 o Major features, server usability:
28165 - New config options RelayBandwidthRate and RelayBandwidthBurst:
28166 a separate set of token buckets for relayed traffic. Right now
28167 relayed traffic is defined as answers to directory requests, and
28168 OR connections that don't have any local circuits on them.
28170 o Major features, client usability:
28171 - A client-side DNS proxy feature to replace the need for
28172 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
28173 for DNS requests on port 9999, use the Tor network to resolve them
28174 anonymously, and send the reply back like a regular DNS server.
28175 The code still only implements a subset of DNS.
28176 - Make PreferTunneledDirConns and TunnelDirConns work even when
28177 we have no cached directory info. This means Tor clients can now
28178 do all of their connections protected by TLS.
28180 o Major features, performance and efficiency:
28181 - Directory authorities accept and serve "extra info" documents for
28182 routers. These documents contain fields from router descriptors
28183 that aren't usually needed, and that use a lot of excess
28184 bandwidth. Once these fields are removed from router descriptors,
28185 the bandwidth savings should be about 60%. [Partially implements
28187 - Servers upload extra-info documents to any authority that accepts
28188 them. Authorities (and caches that have been configured to download
28189 extra-info documents) download them as needed. [Partially implements
28191 - Change the way that Tor buffers data that it is waiting to write.
28192 Instead of queueing data cells in an enormous ring buffer for each
28193 client->OR or OR->OR connection, we now queue cells on a separate
28194 queue for each circuit. This lets us use less slack memory, and
28195 will eventually let us be smarter about prioritizing different kinds
28197 - Use memory pools to allocate cells with better speed and memory
28198 efficiency, especially on platforms where malloc() is inefficient.
28199 - Stop reading on edge connections when their corresponding circuit
28200 buffers are full; start again as the circuits empty out.
28202 o Major features, other:
28203 - Add an HSAuthorityRecordStats option that hidden service authorities
28204 can use to track statistics of overall hidden service usage without
28205 logging information that would be very useful to an attacker.
28206 - Start work implementing multi-level keys for directory authorities:
28207 Add a standalone tool to generate key certificates. (Proposal 103.)
28210 - Directory authorities now call routers Stable if they have an
28211 uptime of at least 30 days, even if that's not the median uptime
28212 in the network. Implements proposal 107, suggested by Kevin Bauer
28215 o Minor fixes (resource management):
28216 - Count the number of open sockets separately from the number
28217 of active connection_t objects. This will let us avoid underusing
28218 our allocated connection limit.
28219 - We no longer use socket pairs to link an edge connection to an
28220 anonymous directory connection or a DirPort test connection.
28221 Instead, we track the link internally and transfer the data
28222 in-process. This saves two sockets per "linked" connection (at the
28223 client and at the server), and avoids the nasty Windows socketpair()
28225 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
28226 for every single inactive connection_t. Free items from the
28227 4k/16k-buffer free lists when they haven't been used for a while.
28229 o Minor features (build):
28230 - Make autoconf search for libevent, openssl, and zlib consistently.
28231 - Update deprecated macros in configure.in.
28232 - When warning about missing headers, tell the user to let us
28233 know if the compile succeeds anyway, so we can downgrade the
28235 - Include the current subversion revision as part of the version
28236 string: either fetch it directly if we're in an SVN checkout, do
28237 some magic to guess it if we're in an SVK checkout, or use
28238 the last-detected version if we're building from a .tar.gz.
28239 Use this version consistently in log messages.
28241 o Minor features (logging):
28242 - Always prepend "Bug: " to any log message about a bug.
28243 - Put a platform string (e.g. "Linux i686") in the startup log
28244 message, so when people paste just their logs, we know if it's
28245 OpenBSD or Windows or what.
28246 - When logging memory usage, break down memory used in buffers by
28249 o Minor features (directory system):
28250 - New config option V2AuthoritativeDirectory that all directory
28251 authorities should set. This will let future authorities choose
28252 not to serve V2 directory information.
28253 - Directory authorities allow multiple router descriptors and/or extra
28254 info documents to be uploaded in a single go. This will make
28255 implementing proposal 104 simpler.
28257 o Minor features (controller):
28258 - Add a new config option __DisablePredictedCircuits designed for
28259 use by the controller, when we don't want Tor to build any circuits
28261 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
28262 so we can exit from the middle of the circuit.
28263 - Implement "getinfo status/circuit-established".
28264 - Implement "getinfo status/version/..." so a controller can tell
28265 whether the current version is recommended, and whether any versions
28266 are good, and how many authorities agree. (Patch from shibz.)
28268 o Minor features (hidden services):
28269 - Allow multiple HiddenServicePort directives with the same virtual
28270 port; when they occur, the user is sent round-robin to one
28271 of the target ports chosen at random. Partially fixes bug 393 by
28272 adding limited ad-hoc round-robining.
28274 o Minor features (other):
28276 - Add a new AutomapHostsOnResolve option: when it is enabled, any
28277 resolve request for hosts matching a given pattern causes Tor to
28278 generate an internal virtual address mapping for that host. This
28279 allows DNSPort to work sensibly with hidden service users. By
28280 default, .exit and .onion addresses are remapped; the list of
28281 patterns can be reconfigured with AutomapHostsSuffixes.
28282 - Add an "-F" option to tor-resolve to force a resolve for a .onion
28283 address. Thanks to the AutomapHostsOnResolve option, this is no
28284 longer a completely silly thing to do.
28285 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
28286 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
28287 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
28288 minus 1 byte: the actual maximum declared bandwidth.
28290 o Removed features:
28291 - Removed support for the old binary "version 0" controller protocol.
28292 This has been deprecated since 0.1.1, and warnings have been issued
28293 since 0.1.2. When we encounter a v0 control message, we now send
28294 back an error and close the connection.
28295 - Remove the old "dns worker" server DNS code: it hasn't been default
28296 since 0.1.2.2-alpha, and all the servers seem to be using the new
28299 o Minor bugfixes (portability):
28300 - Even though Windows is equally happy with / and \ as path separators,
28301 try to use \ consistently on Windows and / consistently on Unix: it
28302 makes the log messages nicer.
28303 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
28304 - Read resolv.conf files correctly on platforms where read() returns
28305 partial results on small file reads.
28307 o Minor bugfixes (directory):
28308 - Correctly enforce that elements of directory objects do not appear
28309 more often than they are allowed to appear.
28310 - When we are reporting the DirServer line we just parsed, we were
28311 logging the second stanza of the key fingerprint, not the first.
28313 o Minor bugfixes (logging):
28314 - When we hit an EOF on a log (probably because we're shutting down),
28315 don't try to remove the log from the list: just mark it as
28316 unusable. (Bulletproofs against bug 222.)
28318 o Minor bugfixes (other):
28319 - In the exitlist script, only consider the most recently published
28320 server descriptor for each server. Also, when the user requests
28321 a list of servers that _reject_ connections to a given address,
28322 explicitly exclude the IPs that also have servers that accept
28323 connections to that address. (Resolves bug 405.)
28324 - Stop allowing hibernating servers to be "stable" or "fast".
28325 - On Windows, we were preventing other processes from reading
28326 cached-routers while Tor was running. (Reported by janbar)
28327 - Make the NodeFamilies config option work. (Reported by
28328 lodger -- it has never actually worked, even though we added it
28330 - Check return values from pthread_mutex functions.
28331 - Don't save non-general-purpose router descriptors to the disk cache,
28332 because we have no way of remembering what their purpose was when
28334 - Add even more asserts to hunt down bug 417.
28335 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
28336 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
28337 Add a log message to confirm that it is in fact unlikely.
28339 o Minor bugfixes (controller):
28340 - Make 'getinfo fingerprint' return a 551 error if we're not a
28341 server, so we match what the control spec claims we do. Reported
28343 - Fix a typo in an error message when extendcircuit fails that
28344 caused us to not follow the \r\n-based delimiter protocol. Reported
28347 o Code simplifications and refactoring:
28348 - Stop passing around circuit_t and crypt_path_t pointers that are
28349 implicit in other procedure arguments.
28350 - Drop the old code to choke directory connections when the
28351 corresponding OR connections got full: thanks to the cell queue
28352 feature, OR conns don't get full any more.
28353 - Make dns_resolve() handle attaching connections to circuits
28354 properly, so the caller doesn't have to.
28355 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
28356 - Keep the connection array as a dynamic smartlist_t, rather than as
28357 a fixed-sized array. This is important, as the number of connections
28358 is becoming increasingly decoupled from the number of sockets.
28361 Changes in version 0.1.2.14 - 2007-05-25
28362 Tor 0.1.2.14 changes the addresses of two directory authorities (this
28363 change especially affects those who serve or use hidden services),
28364 and fixes several other crash- and security-related bugs.
28366 o Directory authority changes:
28367 - Two directory authorities (moria1 and moria2) just moved to new
28368 IP addresses. This change will particularly affect those who serve
28369 or use hidden services.
28371 o Major bugfixes (crashes):
28372 - If a directory server runs out of space in the connection table
28373 as it's processing a begin_dir request, it will free the exit stream
28374 but leave it attached to the circuit, leading to unpredictable
28375 behavior. (Reported by seeess, fixes bug 425.)
28376 - Fix a bug in dirserv_remove_invalid() that would cause authorities
28377 to corrupt memory under some really unlikely scenarios.
28378 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
28379 - Avoid segfaults when reading from mmaped descriptor file. (Reported
28382 o Major bugfixes (security):
28383 - When choosing an entry guard for a circuit, avoid using guards
28384 that are in the same family as the chosen exit -- not just guards
28385 that are exactly the chosen exit. (Reported by lodger.)
28387 o Major bugfixes (resource management):
28388 - If a directory authority is down, skip it when deciding where to get
28389 networkstatus objects or descriptors. Otherwise we keep asking
28390 every 10 seconds forever. Fixes bug 384.
28391 - Count it as a failure if we fetch a valid network-status but we
28392 don't want to keep it. Otherwise we'll keep fetching it and keep
28393 not wanting to keep it. Fixes part of bug 422.
28394 - If all of our dirservers have given us bad or no networkstatuses
28395 lately, then stop hammering them once per minute even when we
28396 think they're failed. Fixes another part of bug 422.
28399 - Actually set the purpose correctly for descriptors inserted with
28400 purpose=controller.
28401 - When we have k non-v2 authorities in our DirServer config,
28402 we ignored the last k authorities in the list when updating our
28404 - Correctly back-off from requesting router descriptors that we are
28405 having a hard time downloading.
28406 - Read resolv.conf files correctly on platforms where read() returns
28407 partial results on small file reads.
28408 - Don't rebuild the entire router store every time we get 32K of
28409 routers: rebuild it when the journal gets very large, or when
28410 the gaps in the store get very large.
28413 - When routers publish SVN revisions in their router descriptors,
28414 authorities now include those versions correctly in networkstatus
28416 - Warn when using a version of libevent before 1.3b to run a server on
28417 OSX or BSD: these versions interact badly with userspace threads.
28420 Changes in version 0.1.2.13 - 2007-04-24
28421 This release features some major anonymity fixes, such as safer path
28422 selection; better client performance; faster bootstrapping, better
28423 address detection, and better DNS support for servers; write limiting as
28424 well as read limiting to make servers easier to run; and a huge pile of
28425 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
28427 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
28428 of the Freenode IRC network, remembering his patience and vision for
28429 free speech on the Internet.
28432 - Fix a memory leak when we ask for "all" networkstatuses and we
28433 get one we don't recognize.
28434 - Add more asserts to hunt down bug 417.
28435 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
28438 Changes in version 0.1.2.12-rc - 2007-03-16
28440 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
28441 directory information requested inside Tor connections (i.e. via
28442 begin_dir cells). It only triggered when the same connection was
28443 serving other data at the same time. Reported by seeess.
28446 - When creating a circuit via the controller, send a 'launched'
28447 event when we're done, so we follow the spec better.
28450 Changes in version 0.1.2.11-rc - 2007-03-15
28451 o Minor bugfixes (controller), reported by daejees:
28452 - Correct the control spec to match how the code actually responds
28453 to 'getinfo addr-mappings/*'.
28454 - The control spec described a GUARDS event, but the code
28455 implemented a GUARD event. Standardize on GUARD, but let people
28456 ask for GUARDS too.
28459 Changes in version 0.1.2.10-rc - 2007-03-07
28460 o Major bugfixes (Windows):
28461 - Do not load the NT services library functions (which may not exist)
28462 just to detect if we're a service trying to shut down. Now we run
28463 on Win98 and friends again.
28465 o Minor bugfixes (other):
28466 - Clarify a couple of log messages.
28467 - Fix a misleading socks5 error number.
28470 Changes in version 0.1.2.9-rc - 2007-03-02
28471 o Major bugfixes (Windows):
28472 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
28473 of the usual GCC "%llu". This prevents a bug when saving 64-bit
28474 int configuration values: the high-order 32 bits would get
28475 truncated. In particular, we were being bitten by the default
28476 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
28477 and maybe also bug 397.)
28479 o Minor bugfixes (performance):
28480 - Use OpenSSL's AES implementation on platforms where it's faster.
28481 This could save us as much as 10% CPU usage.
28483 o Minor bugfixes (server):
28484 - Do not rotate onion key immediately after setting it for the first
28487 o Minor bugfixes (directory authorities):
28488 - Stop calling servers that have been hibernating for a long time
28489 "stable". Also, stop letting hibernating or obsolete servers affect
28490 uptime and bandwidth cutoffs.
28491 - Stop listing hibernating servers in the v1 directory.
28493 o Minor bugfixes (hidden services):
28494 - Upload hidden service descriptors slightly less often, to reduce
28495 load on authorities.
28497 o Minor bugfixes (other):
28498 - Fix an assert that could trigger if a controller quickly set then
28499 cleared EntryNodes. Bug found by Udo van den Heuvel.
28500 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
28502 - Fix a potential race condition in the rpm installer. Found by
28504 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
28505 of 2 as indicating that the server is completely bad; it sometimes
28506 means that the server is just bad for the request in question. (may fix
28507 the last of bug 326.)
28508 - Disable encrypted directory connections when we don't have a server
28509 descriptor for the destination. We'll get this working again in
28513 Changes in version 0.1.2.8-beta - 2007-02-26
28514 o Major bugfixes (crashes):
28515 - Stop crashing when the controller asks us to resetconf more than
28516 one config option at once. (Vidalia 0.0.11 does this.)
28517 - Fix a crash that happened on Win98 when we're given command-line
28518 arguments: don't try to load NT service functions from advapi32.dll
28519 except when we need them. (Bug introduced in 0.1.2.7-alpha;
28521 - Fix a longstanding obscure crash bug that could occur when
28522 we run out of DNS worker processes. (Resolves bug 390.)
28524 o Major bugfixes (hidden services):
28525 - Correctly detect whether hidden service descriptor downloads are
28526 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
28528 o Major bugfixes (accounting):
28529 - When we start during an accounting interval before it's time to wake
28530 up, remember to wake up at the correct time. (May fix bug 342.)
28532 o Minor bugfixes (controller):
28533 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
28534 clear the corresponding on_circuit variable, and remember later
28535 that we don't need to send a redundant CLOSED event. Resolves part
28537 - Report events where a resolve succeeded or where we got a socks
28538 protocol error correctly, rather than calling both of them
28540 - Change reported stream target addresses to IP consistently when
28541 we finally get the IP from an exit node.
28542 - Send log messages to the controller even if they happen to be very
28545 o Minor bugfixes (other):
28546 - Display correct results when reporting which versions are
28547 recommended, and how recommended they are. (Resolves bug 383.)
28548 - Improve our estimates for directory bandwidth to be less random:
28549 guess that an unrecognized directory will have the average bandwidth
28550 from all known directories, not that it will have the average
28551 bandwidth from those directories earlier than it on the list.
28552 - If we start a server with ClientOnly 1, then set ClientOnly to 0
28553 and hup, stop triggering an assert based on an empty onion_key.
28554 - On platforms with no working mmap() equivalent, don't warn the
28555 user when cached-routers doesn't exist.
28556 - Warn the user when mmap() [or its equivalent] fails for some reason
28557 other than file-not-found.
28558 - Don't warn the user when cached-routers.new doesn't exist: that's
28559 perfectly fine when starting up for the first time.
28560 - When EntryNodes are configured, rebuild the guard list to contain,
28561 in order: the EntryNodes that were guards before; the rest of the
28562 EntryNodes; the nodes that were guards before.
28563 - Mask out all signals in sub-threads; only the libevent signal
28564 handler should be processing them. This should prevent some crashes
28565 on some machines using pthreads. (Patch from coderman.)
28566 - Fix switched arguments on memset in the implementation of
28567 tor_munmap() for systems with no mmap() call.
28568 - When Tor receives a router descriptor that it asked for, but
28569 no longer wants (because it has received fresh networkstatuses
28570 in the meantime), do not warn the user. Cache the descriptor if
28571 we're a cache; drop it if we aren't.
28572 - Make earlier entry guards _really_ get retried when the network
28574 - On a malformed DNS reply, always give an error to the corresponding
28576 - Build with recent libevents on platforms that do not define the
28577 nonstandard types "u_int8_t" and friends.
28579 o Minor features (controller):
28580 - Warn the user when an application uses the obsolete binary v0
28581 control protocol. We're planning to remove support for it during
28582 the next development series, so it's good to give people some
28584 - Add STREAM_BW events to report per-entry-stream bandwidth
28585 use. (Patch from Robert Hogan.)
28586 - Rate-limit SIGNEWNYM signals in response to controllers that
28587 impolitely generate them for every single stream. (Patch from
28588 mwenge; closes bug 394.)
28589 - Make REMAP stream events have a SOURCE (cache or exit), and
28590 make them generated in every case where we get a successful
28591 connected or resolved cell.
28593 o Minor bugfixes (performance):
28594 - Call router_have_min_dir_info half as often. (This is showing up in
28595 some profiles, but not others.)
28596 - When using GCC, make log_debug never get called at all, and its
28597 arguments never get evaluated, when no debug logs are configured.
28598 (This is showing up in some profiles, but not others.)
28601 - Remove some never-implemented options. Mark PathlenCoinWeight as
28603 - Implement proposal 106: Stop requiring clients to have well-formed
28604 certificates; stop checking nicknames in certificates. (Clients
28605 have certificates so that they can look like Tor servers, but in
28606 the future we might want to allow them to look like regular TLS
28607 clients instead. Nicknames in certificates serve no purpose other
28608 than making our protocol easier to recognize on the wire.)
28609 - Revise messages on handshake failure again to be even more clear about
28610 which are incoming connections and which are outgoing.
28611 - Discard any v1 directory info that's over 1 month old (for
28612 directories) or over 1 week old (for running-routers lists).
28613 - Do not warn when individual nodes in the configuration's EntryNodes,
28614 ExitNodes, etc are down: warn only when all possible nodes
28615 are down. (Fixes bug 348.)
28616 - Always remove expired routers and networkstatus docs before checking
28617 whether we have enough information to build circuits. (Fixes
28619 - Put a lower-bound on MaxAdvertisedBandwidth.
28622 Changes in version 0.1.2.7-alpha - 2007-02-06
28623 o Major bugfixes (rate limiting):
28624 - Servers decline directory requests much more aggressively when
28625 they're low on bandwidth. Otherwise they end up queueing more and
28626 more directory responses, which can't be good for latency.
28627 - But never refuse directory requests from local addresses.
28628 - Fix a memory leak when sending a 503 response for a networkstatus
28630 - Be willing to read or write on local connections (e.g. controller
28631 connections) even when the global rate limiting buckets are empty.
28632 - If our system clock jumps back in time, don't publish a negative
28633 uptime in the descriptor. Also, don't let the global rate limiting
28634 buckets go absurdly negative.
28635 - Flush local controller connection buffers periodically as we're
28636 writing to them, so we avoid queueing 4+ megabytes of data before
28639 o Major bugfixes (NT services):
28640 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
28641 command-line flag so that admins can override the default by saying
28642 "tor --service install --user "SomeUser"". This will not affect
28643 existing installed services. Also, warn the user that the service
28644 will look for its configuration file in the service user's
28645 %appdata% directory. (We can't do the 'hardwire the user's appdata
28646 directory' trick any more, since we may not have read access to that
28649 o Major bugfixes (other):
28650 - Previously, we would cache up to 16 old networkstatus documents
28651 indefinitely, if they came from nontrusted authorities. Now we
28652 discard them if they are more than 10 days old.
28653 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
28655 - Detect and reject malformed DNS responses containing circular
28657 - If exits are rare enough that we're not marking exits as guards,
28658 ignore exit bandwidth when we're deciding the required bandwidth
28660 - When we're handling a directory connection tunneled over Tor,
28661 don't fill up internal memory buffers with all the data we want
28662 to tunnel; instead, only add it if the OR connection that will
28663 eventually receive it has some room for it. (This can lead to
28664 slowdowns in tunneled dir connections; a better solution will have
28665 to wait for 0.2.0.)
28667 o Minor bugfixes (dns):
28668 - Add some defensive programming to eventdns.c in an attempt to catch
28669 possible memory-stomping bugs.
28670 - Detect and reject DNS replies containing IPv4 or IPv6 records with
28671 an incorrect number of bytes. (Previously, we would ignore the
28673 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
28674 in the correct order, and doesn't crash.
28675 - Free memory held in recently-completed DNS lookup attempts on exit.
28676 This was not a memory leak, but may have been hiding memory leaks.
28677 - Handle TTL values correctly on reverse DNS lookups.
28678 - Treat failure to parse resolv.conf as an error.
28680 o Minor bugfixes (other):
28681 - Fix crash with "tor --list-fingerprint" (reported by seeess).
28682 - When computing clock skew from directory HTTP headers, consider what
28683 time it was when we finished asking for the directory, not what
28685 - Expire socks connections if they spend too long waiting for the
28686 handshake to finish. Previously we would let them sit around for
28687 days, if the connecting application didn't close them either.
28688 - And if the socks handshake hasn't started, don't send a
28689 "DNS resolve socks failed" handshake reply; just close it.
28690 - Stop using C functions that OpenBSD's linker doesn't like.
28691 - Don't launch requests for descriptors unless we have networkstatuses
28692 from at least half of the authorities. This delays the first
28693 download slightly under pathological circumstances, but can prevent
28694 us from downloading a bunch of descriptors we don't need.
28695 - Do not log IPs with TLS failures for incoming TLS
28696 connections. (Fixes bug 382.)
28697 - If the user asks to use invalid exit nodes, be willing to use
28699 - Stop using the reserved ac_cv namespace in our configure script.
28700 - Call stat() slightly less often; use fstat() when possible.
28701 - Refactor the way we handle pending circuits when an OR connection
28702 completes or fails, in an attempt to fix a rare crash bug.
28703 - Only rewrite a conn's address based on X-Forwarded-For: headers
28704 if it's a parseable public IP address; and stop adding extra quotes
28705 to the resulting address.
28708 - Weight directory requests by advertised bandwidth. Now we can
28709 let servers enable write limiting but still allow most clients to
28710 succeed at their directory requests. (We still ignore weights when
28711 choosing a directory authority; I hope this is a feature.)
28714 - Create a new file ReleaseNotes which was the old ChangeLog. The
28715 new ChangeLog file now includes the summaries for all development
28717 - Check for addresses with invalid characters at the exit as well
28718 as at the client, and warn less verbosely when they fail. You can
28719 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28720 - Adapt a patch from goodell to let the contrib/exitlist script
28721 take arguments rather than require direct editing.
28722 - Inform the server operator when we decide not to advertise a
28723 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28724 was confusing Zax, so now we're hopefully more helpful.
28725 - Bring us one step closer to being able to establish an encrypted
28726 directory tunnel without knowing a descriptor first. Still not
28727 ready yet. As part of the change, now assume we can use a
28728 create_fast cell if we don't know anything about a router.
28729 - Allow exit nodes to use nameservers running on ports other than 53.
28730 - Servers now cache reverse DNS replies.
28731 - Add an --ignore-missing-torrc command-line option so that we can
28732 get the "use sensible defaults if the configuration file doesn't
28733 exist" behavior even when specifying a torrc location on the command
28736 o Minor features (controller):
28737 - Track reasons for OR connection failure; make these reasons
28738 available via the controller interface. (Patch from Mike Perry.)
28739 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28740 can learn when clients are sending malformed hostnames to Tor.
28741 - Clean up documentation for controller status events.
28742 - Add a REMAP status to stream events to note that a stream's
28743 address has changed because of a cached address or a MapAddress
28747 Changes in version 0.1.2.6-alpha - 2007-01-09
28749 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28750 connection handles more than 4 gigs in either direction, we crash.
28751 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28752 advertised exit node, somebody might try to exit from us when
28753 we're bootstrapping and before we've built our descriptor yet.
28754 Refuse the connection rather than crashing.
28757 - Warn if we (as a server) find that we've resolved an address that we
28758 weren't planning to resolve.
28759 - Warn that using select() on any libevent version before 1.1 will be
28760 unnecessarily slow (even for select()).
28761 - Flush ERR-level controller status events just like we currently
28762 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28763 the controller from learning about current events.
28765 o Minor features (more controller status events):
28766 - Implement EXTERNAL_ADDRESS server status event so controllers can
28767 learn when our address changes.
28768 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28769 can learn when directories reject our descriptor.
28770 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28771 can learn when a client application is speaking a non-socks protocol
28773 - Implement DANGEROUS_SOCKS client status event so controllers
28774 can learn when a client application is leaking DNS addresses.
28775 - Implement BUG general status event so controllers can learn when
28776 Tor is unhappy about its internal invariants.
28777 - Implement CLOCK_SKEW general status event so controllers can learn
28778 when Tor thinks the system clock is set incorrectly.
28779 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28780 server status events so controllers can learn when their descriptors
28781 are accepted by a directory.
28782 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28783 server status events so controllers can learn about Tor's progress in
28784 deciding whether it's reachable from the outside.
28785 - Implement BAD_LIBEVENT general status event so controllers can learn
28786 when we have a version/method combination in libevent that needs to
28788 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28789 and DNS_USELESS server status events so controllers can learn
28790 about changes to DNS server status.
28792 o Minor features (directory):
28793 - Authorities no longer recommend exits as guards if this would shift
28794 too much load to the exit nodes.
28797 Changes in version 0.1.2.5-alpha - 2007-01-06
28799 - Enable write limiting as well as read limiting. Now we sacrifice
28800 capacity if we're pushing out lots of directory traffic, rather
28801 than overrunning the user's intended bandwidth limits.
28802 - Include TLS overhead when counting bandwidth usage; previously, we
28803 would count only the bytes sent over TLS, but not the bytes used
28805 - Support running the Tor service with a torrc not in the same
28806 directory as tor.exe and default to using the torrc located in
28807 the %appdata%\Tor\ of the user who installed the service. Patch
28809 - Servers now check for the case when common DNS requests are going to
28810 wildcarded addresses (i.e. all getting the same answer), and change
28811 their exit policy to reject *:* if it's happening.
28812 - Implement BEGIN_DIR cells, so we can connect to the directory
28813 server via TLS to do encrypted directory requests rather than
28814 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28815 config options if you like.
28817 o Minor features (config and docs):
28818 - Start using the state file to store bandwidth accounting data:
28819 the bw_accounting file is now obsolete. We'll keep generating it
28820 for a while for people who are still using 0.1.2.4-alpha.
28821 - Try to batch changes to the state file so that we do as few
28822 disk writes as possible while still storing important things in
28824 - The state file and the bw_accounting file get saved less often when
28825 the AvoidDiskWrites config option is set.
28826 - Make PIDFile work on Windows (untested).
28827 - Add internal descriptions for a bunch of configuration options:
28828 accessible via controller interface and in comments in saved
28830 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28831 NNTP by default, so this seems like a sensible addition.
28832 - Clients now reject hostnames with invalid characters. This should
28833 avoid some inadvertent info leaks. Add an option
28834 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28835 is running a private network with hosts called @, !, and #.
28836 - Add a maintainer script to tell us which options are missing
28837 documentation: "make check-docs".
28838 - Add a new address-spec.txt document to describe our special-case
28839 addresses: .exit, .onion, and .noconnnect.
28841 o Minor features (DNS):
28842 - Ongoing work on eventdns infrastructure: now it has dns server
28843 and ipv6 support. One day Tor will make use of it.
28844 - Add client-side caching for reverse DNS lookups.
28845 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28846 - When we change nameservers or IP addresses, reset and re-launch
28847 our tests for DNS hijacking.
28849 o Minor features (directory):
28850 - Authorities now specify server versions in networkstatus. This adds
28851 about 2% to the size of compressed networkstatus docs, and allows
28852 clients to tell which servers support BEGIN_DIR and which don't.
28853 The implementation is forward-compatible with a proposed future
28854 protocol version scheme not tied to Tor versions.
28855 - DirServer configuration lines now have an orport= option so
28856 clients can open encrypted tunnels to the authorities without
28857 having downloaded their descriptors yet. Enabled for moria1,
28858 moria2, tor26, and lefkada now in the default configuration.
28859 - Directory servers are more willing to send a 503 "busy" if they
28860 are near their write limit, especially for v1 directory requests.
28861 Now they can use their limited bandwidth for actual Tor traffic.
28862 - Clients track responses with status 503 from dirservers. After a
28863 dirserver has given us a 503, we try not to use it until an hour has
28864 gone by, or until we have no dirservers that haven't given us a 503.
28865 - When we get a 503 from a directory, and we're not a server, we don't
28866 count the failure against the total number of failures allowed
28867 for the thing we're trying to download.
28868 - Report X-Your-Address-Is correctly from tunneled directory
28869 connections; don't report X-Your-Address-Is when it's an internal
28870 address; and never believe reported remote addresses when they're
28872 - Protect against an unlikely DoS attack on directory servers.
28873 - Add a BadDirectory flag to network status docs so that authorities
28874 can (eventually) tell clients about caches they believe to be
28877 o Minor features (controller):
28878 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28879 - Reimplement GETINFO so that info/names stays in sync with the
28881 - Implement "GETINFO fingerprint".
28882 - Implement "SETEVENTS GUARD" so controllers can get updates on
28883 entry guard status as it changes.
28885 o Minor features (clean up obsolete pieces):
28886 - Remove some options that have been deprecated since at least
28887 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28888 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28889 to set log options.
28890 - We no longer look for identity and onion keys in "identity.key" and
28891 "onion.key" -- these were replaced by secret_id_key and
28892 secret_onion_key in 0.0.8pre1.
28893 - We no longer require unrecognized directory entries to be
28896 o Major bugfixes (security):
28897 - Stop sending the HttpProxyAuthenticator string to directory
28898 servers when directory connections are tunnelled through Tor.
28899 - Clients no longer store bandwidth history in the state file.
28900 - Do not log introduction points for hidden services if SafeLogging
28902 - When generating bandwidth history, round down to the nearest
28903 1k. When storing accounting data, round up to the nearest 1k.
28904 - When we're running as a server, remember when we last rotated onion
28905 keys, so that we will rotate keys once they're a week old even if
28906 we never stay up for a week ourselves.
28908 o Major bugfixes (other):
28909 - Fix a longstanding bug in eventdns that prevented the count of
28910 timed-out resolves from ever being reset. This bug caused us to
28911 give up on a nameserver the third time it timed out, and try it
28912 10 seconds later... and to give up on it every time it timed out
28914 - Take out the '5 second' timeout from the connection retry
28915 schedule. Now the first connect attempt will wait a full 10
28916 seconds before switching to a new circuit. Perhaps this will help
28917 a lot. Based on observations from Mike Perry.
28918 - Fix a bug on the Windows implementation of tor_mmap_file() that
28919 would prevent the cached-routers file from ever loading. Reported
28923 - Fix an assert failure when a directory authority sets
28924 AuthDirRejectUnlisted and then receives a descriptor from an
28925 unlisted router. Reported by seeess.
28926 - Avoid a double-free when parsing malformed DirServer lines.
28927 - Fix a bug when a BSD-style PF socket is first used. Patch from
28929 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
28930 to resolve an address at a given exit node even when they ask for
28932 - Servers no longer ever list themselves in their "family" line,
28933 even if configured to do so. This makes it easier to configure
28934 family lists conveniently.
28935 - When running as a server, don't fall back to 127.0.0.1 when no
28936 nameservers are configured in /etc/resolv.conf; instead, make the
28937 user fix resolv.conf or specify nameservers explicitly. (Resolves
28939 - Stop accepting certain malformed ports in configured exit policies.
28940 - Don't re-write the fingerprint file every restart, unless it has
28942 - Stop warning when a single nameserver fails: only warn when _all_ of
28943 our nameservers have failed. Also, when we only have one nameserver,
28944 raise the threshold for deciding that the nameserver is dead.
28945 - Directory authorities now only decide that routers are reachable
28946 if their identity keys are as expected.
28947 - When the user uses bad syntax in the Log config line, stop
28948 suggesting other bad syntax as a replacement.
28949 - Correctly detect ipv6 DNS capability on OpenBSD.
28951 o Minor bugfixes (controller):
28952 - Report the circuit number correctly in STREAM CLOSED events. Bug
28953 reported by Mike Perry.
28954 - Do not report bizarre values for results of accounting GETINFOs
28955 when the last second's write or read exceeds the allotted bandwidth.
28956 - Report "unrecognized key" rather than an empty string when the
28957 controller tries to fetch a networkstatus that doesn't exist.
28960 Changes in version 0.1.1.26 - 2006-12-14
28961 o Security bugfixes:
28962 - Stop sending the HttpProxyAuthenticator string to directory
28963 servers when directory connections are tunnelled through Tor.
28964 - Clients no longer store bandwidth history in the state file.
28965 - Do not log introduction points for hidden services if SafeLogging
28969 - Fix an assert failure when a directory authority sets
28970 AuthDirRejectUnlisted and then receives a descriptor from an
28971 unlisted router (reported by seeess).
28974 Changes in version 0.1.2.4-alpha - 2006-12-03
28976 - Add support for using natd; this allows FreeBSDs earlier than
28977 5.1.2 to have ipfw send connections through Tor without using
28978 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
28981 - Make all connections to addresses of the form ".noconnect"
28982 immediately get closed. This lets application/controller combos
28983 successfully test whether they're talking to the same Tor by
28984 watching for STREAM events.
28985 - Make cross.sh cross-compilation script work even when autogen.sh
28986 hasn't been run. (Patch from Michael Mohr.)
28987 - Statistics dumped by -USR2 now include a breakdown of public key
28988 operations, for profiling.
28991 - Fix a major leak when directory authorities parse their
28992 approved-routers list, a minor memory leak when we fail to pick
28993 an exit node, and a few rare leaks on errors.
28994 - Handle TransPort connections even when the server sends data before
28995 the client sends data. Previously, the connection would just hang
28996 until the client sent data. (Patch from tup based on patch from
28998 - Avoid assert failure when our cached-routers file is empty on
29002 - Don't log spurious warnings when we see a circuit close reason we
29003 don't recognize; it's probably just from a newer version of Tor.
29004 - Have directory authorities allow larger amounts of drift in uptime
29005 without replacing the server descriptor: previously, a server that
29006 restarted every 30 minutes could have 48 "interesting" descriptors
29008 - Start linking to the Tor specification and Tor reference manual
29009 correctly in the Windows installer.
29010 - Add Vidalia to the OS X uninstaller script, so when we uninstall
29011 Tor/Privoxy we also uninstall Vidalia.
29012 - Resume building on Irix64, and fix a lot of warnings from its
29013 MIPSpro C compiler.
29014 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
29015 when we're running as a client.
29018 Changes in version 0.1.1.25 - 2006-11-04
29020 - When a client asks us to resolve (rather than connect to)
29021 an address, and we have a cached answer, give them the cached
29022 answer. Previously, we would give them no answer at all.
29023 - We were building exactly the wrong circuits when we predict
29024 hidden service requirements, meaning Tor would have to build all
29025 its circuits on demand.
29026 - If none of our live entry guards have a high uptime, but we
29027 require a guard with a high uptime, try adding a new guard before
29028 we give up on the requirement. This patch should make long-lived
29029 connections more stable on average.
29030 - When testing reachability of our DirPort, don't launch new
29031 tests when there's already one in progress -- unreachable
29032 servers were stacking up dozens of testing streams.
29034 o Security bugfixes:
29035 - When the user sends a NEWNYM signal, clear the client-side DNS
29036 cache too. Otherwise we continue to act on previous information.
29039 - Avoid a memory corruption bug when creating a hash table for
29041 - Avoid possibility of controller-triggered crash when misusing
29042 certain commands from a v0 controller on platforms that do not
29043 handle printf("%s",NULL) gracefully.
29044 - Avoid infinite loop on unexpected controller input.
29045 - Don't log spurious warnings when we see a circuit close reason we
29046 don't recognize; it's probably just from a newer version of Tor.
29047 - Add Vidalia to the OS X uninstaller script, so when we uninstall
29048 Tor/Privoxy we also uninstall Vidalia.
29051 Changes in version 0.1.2.3-alpha - 2006-10-29
29053 - Prepare for servers to publish descriptors less often: never
29054 discard a descriptor simply for being too old until either it is
29055 recommended by no authorities, or until we get a better one for
29056 the same router. Make caches consider retaining old recommended
29057 routers for even longer.
29058 - If most authorities set a BadExit flag for a server, clients
29059 don't think of it as a general-purpose exit. Clients only consider
29060 authorities that advertise themselves as listing bad exits.
29061 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
29062 headers for content, so that we can work better in the presence of
29063 caching HTTP proxies.
29064 - Allow authorities to list nodes as bad exits by fingerprint or by
29067 o Minor features, controller:
29068 - Add a REASON field to CIRC events; for backward compatibility, this
29069 field is sent only to controllers that have enabled the extended
29070 event format. Also, add additional reason codes to explain why
29071 a given circuit has been destroyed or truncated. (Patches from
29073 - Add a REMOTE_REASON field to extended CIRC events to tell the
29074 controller about why a remote OR told us to close a circuit.
29075 - Stream events also now have REASON and REMOTE_REASON fields,
29076 working much like those for circuit events.
29077 - There's now a GETINFO ns/... field so that controllers can ask Tor
29078 about the current status of a router.
29079 - A new event type "NS" to inform a controller when our opinion of
29080 a router's status has changed.
29081 - Add a GETINFO events/names and GETINFO features/names so controllers
29082 can tell which events and features are supported.
29083 - A new CLEARDNSCACHE signal to allow controllers to clear the
29084 client-side DNS cache without expiring circuits.
29086 o Security bugfixes:
29087 - When the user sends a NEWNYM signal, clear the client-side DNS
29088 cache too. Otherwise we continue to act on previous information.
29091 - Avoid sending junk to controllers or segfaulting when a controller
29092 uses EVENT_NEW_DESC with verbose nicknames.
29093 - Stop triggering asserts if the controller tries to extend hidden
29094 service circuits (reported by mwenge).
29095 - Avoid infinite loop on unexpected controller input.
29096 - When the controller does a "GETINFO network-status", tell it
29097 about even those routers whose descriptors are very old, and use
29098 long nicknames where appropriate.
29099 - Change NT service functions to be loaded on demand. This lets us
29100 build with MinGW without breaking Tor for Windows 98 users.
29101 - Do DirPort reachability tests less often, since a single test
29102 chews through many circuits before giving up.
29103 - In the hidden service example in torrc.sample, stop recommending
29104 esoteric and discouraged hidden service options.
29105 - When stopping an NT service, wait up to 10 sec for it to actually
29106 stop. Patch from Matt Edman; resolves bug 295.
29107 - Fix handling of verbose nicknames with ORCONN controller events:
29108 make them show up exactly when requested, rather than exactly when
29110 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
29111 printing a duplicate "$" in the keys we send (reported by mwenge).
29112 - Correctly set maximum connection limit on Cygwin. (This time
29114 - Try to detect Windows correctly when cross-compiling.
29115 - Detect the size of the routers file correctly even if it is
29116 corrupted (on systems without mmap) or not page-aligned (on systems
29117 with mmap). This bug was harmless.
29118 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
29119 to open a stream fails; now we do in more cases. This should
29120 make clients able to find a good exit faster in some cases, since
29121 unhandleable requests will now get an error rather than timing out.
29122 - Resolve two memory leaks when rebuilding the on-disk router cache
29123 (reported by fookoowa).
29124 - Clean up minor code warnings suggested by the MIPSpro C compiler,
29125 and reported by some Centos users.
29126 - Controller signals now work on non-Unix platforms that don't define
29127 SIGUSR1 and SIGUSR2 the way we expect.
29128 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
29129 values before failing, and always enables eventdns.
29130 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
29131 Try to fix this in configure.in by checking for most functions
29132 before we check for libevent.
29135 Changes in version 0.1.2.2-alpha - 2006-10-07
29137 - Make our async eventdns library on-by-default for Tor servers,
29138 and plan to deprecate the separate dnsworker threads.
29139 - Add server-side support for "reverse" DNS lookups (using PTR
29140 records so clients can determine the canonical hostname for a given
29141 IPv4 address). Only supported by servers using eventdns; servers
29142 now announce in their descriptors whether they support eventdns.
29143 - Specify and implement client-side SOCKS5 interface for reverse DNS
29144 lookups (see doc/socks-extensions.txt).
29145 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
29146 connect to directory servers through Tor. Previously, clients needed
29147 to find Tor exits to make private connections to directory servers.
29148 - Avoid choosing Exit nodes for entry or middle hops when the
29149 total bandwidth available from non-Exit nodes is much higher than
29150 the total bandwidth available from Exit nodes.
29151 - Workaround for name servers (like Earthlink's) that hijack failing
29152 DNS requests and replace the no-such-server answer with a "helpful"
29153 redirect to an advertising-driven search portal. Also work around
29154 DNS hijackers who "helpfully" decline to hijack known-invalid
29155 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
29156 lets you turn it off.
29157 - Send out a burst of long-range padding cells once we've established
29158 that we're reachable. Spread them over 4 circuits, so hopefully
29159 a few will be fast. This exercises our bandwidth and bootstraps
29160 us into the directory more quickly.
29162 o New/improved config options:
29163 - Add new config option "ResolvConf" to let the server operator
29164 choose an alternate resolve.conf file when using eventdns.
29165 - Add an "EnforceDistinctSubnets" option to control our "exclude
29166 servers on the same /16" behavior. It's still on by default; this
29167 is mostly for people who want to operate private test networks with
29168 all the machines on the same subnet.
29169 - If one of our entry guards is on the ExcludeNodes list, or the
29170 directory authorities don't think it's a good guard, treat it as
29171 if it were unlisted: stop using it as a guard, and throw it off
29172 the guards list if it stays that way for a long time.
29173 - Allow directory authorities to be marked separately as authorities
29174 for the v1 directory protocol, the v2 directory protocol, and
29175 as hidden service directories, to make it easier to retire old
29176 authorities. V1 authorities should set "HSAuthoritativeDir 1"
29177 to continue being hidden service authorities too.
29178 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
29180 o Minor features, controller:
29181 - Fix CIRC controller events so that controllers can learn the
29182 identity digests of non-Named servers used in circuit paths.
29183 - Let controllers ask for more useful identifiers for servers. Instead
29184 of learning identity digests for un-Named servers and nicknames
29185 for Named servers, the new identifiers include digest, nickname,
29186 and indication of Named status. Off by default; see control-spec.txt
29187 for more information.
29188 - Add a "getinfo address" controller command so it can display Tor's
29189 best guess to the user.
29190 - New controller event to alert the controller when our server
29191 descriptor has changed.
29192 - Give more meaningful errors on controller authentication failure.
29194 o Minor features, other:
29195 - When asked to resolve a hostname, don't use non-exit servers unless
29196 requested to do so. This allows servers with broken DNS to be
29197 useful to the network.
29198 - Divide eventdns log messages into warn and info messages.
29199 - Reserve the nickname "Unnamed" for routers that can't pick
29200 a hostname: any router can call itself Unnamed; directory
29201 authorities will never allocate Unnamed to any particular router;
29202 clients won't believe that any router is the canonical Unnamed.
29203 - Only include function names in log messages for info/debug messages.
29204 For notice/warn/err, the content of the message should be clear on
29205 its own, and printing the function name only confuses users.
29206 - Avoid some false positives during reachability testing: don't try
29207 to test via a server that's on the same /24 as us.
29208 - If we fail to build a circuit to an intended enclave, and it's
29209 not mandatory that we use that enclave, stop wanting it.
29210 - When eventdns is enabled, allow multithreaded builds on NetBSD and
29211 OpenBSD. (We had previously disabled threads on these platforms
29212 because they didn't have working thread-safe resolver functions.)
29214 o Major bugfixes, anonymity/security:
29215 - If a client asked for a server by name, and there's a named server
29216 in our network-status but we don't have its descriptor yet, we
29217 could return an unnamed server instead.
29218 - Fix NetBSD bug that could allow someone to force uninitialized RAM
29219 to be sent to a server's DNS resolver. This only affects NetBSD
29220 and other platforms that do not bounds-check tolower().
29221 - Reject (most) attempts to use Tor circuits with length one. (If
29222 many people start using Tor as a one-hop proxy, exit nodes become
29223 a more attractive target for compromise.)
29224 - Just because your DirPort is open doesn't mean people should be
29225 able to remotely teach you about hidden service descriptors. Now
29226 only accept rendezvous posts if you've got HSAuthoritativeDir set.
29228 o Major bugfixes, other:
29229 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
29230 - When a client asks the server to resolve (not connect to)
29231 an address, and it has a cached answer, give them the cached answer.
29232 Previously, the server would give them no answer at all.
29233 - Allow really slow clients to not hang up five minutes into their
29234 directory downloads (suggested by Adam J. Richter).
29235 - We were building exactly the wrong circuits when we anticipated
29236 hidden service requirements, meaning Tor would have to build all
29237 its circuits on demand.
29238 - Avoid crashing when we mmap a router cache file of size 0.
29239 - When testing reachability of our DirPort, don't launch new
29240 tests when there's already one in progress -- unreachable
29241 servers were stacking up dozens of testing streams.
29243 o Minor bugfixes, correctness:
29244 - If we're a directory mirror and we ask for "all" network status
29245 documents, we would discard status documents from authorities
29246 we don't recognize.
29247 - Avoid a memory corruption bug when creating a hash table for
29249 - Avoid controller-triggered crash when misusing certain commands
29250 from a v0 controller on platforms that do not handle
29251 printf("%s",NULL) gracefully.
29252 - Don't crash when a controller sends a third argument to an
29253 "extendcircuit" request.
29254 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29255 response; fix error code when "getinfo dir/status/" fails.
29256 - Avoid crash when telling controller stream-status and a stream
29258 - Patch from Adam Langley to fix assert() in eventdns.c.
29259 - Fix a debug log message in eventdns to say "X resolved to Y"
29260 instead of "X resolved to X".
29261 - Make eventdns give strings for DNS errors, not just error numbers.
29262 - Track unreachable entry guards correctly: don't conflate
29263 'unreachable by us right now' with 'listed as down by the directory
29264 authorities'. With the old code, if a guard was unreachable by
29265 us but listed as running, it would clog our guard list forever.
29266 - Behave correctly in case we ever have a network with more than
29267 2GB/s total advertised capacity.
29268 - Make TrackExitHosts case-insensitive, and fix the behavior of
29269 ".suffix" TrackExitHosts items to avoid matching in the middle of
29271 - Finally fix the openssl warnings from newer gccs that believe that
29272 ignoring a return value is okay, but casting a return value and
29273 then ignoring it is a sign of madness.
29274 - Prevent the contrib/exitlist script from printing the same
29275 result more than once.
29276 - Patch from Steve Hildrey: Generate network status correctly on
29277 non-versioning dirservers.
29278 - Don't listen to the X-Your-Address-Is hint if you did the lookup
29279 via Tor; otherwise you'll think you're the exit node's IP address.
29281 o Minor bugfixes, performance:
29282 - Two small performance improvements on parsing descriptors.
29283 - Major performance improvement on inserting descriptors: change
29284 algorithm from O(n^2) to O(n).
29285 - Make the common memory allocation path faster on machines where
29286 malloc(0) returns a pointer.
29287 - Start remembering X-Your-Address-Is directory hints even if you're
29288 a client, so you can become a server more smoothly.
29289 - Avoid duplicate entries on MyFamily line in server descriptor.
29291 o Packaging, features:
29292 - Remove architecture from OS X builds. The official builds are
29293 now universal binaries.
29294 - The Debian package now uses --verify-config when (re)starting,
29295 to distinguish configuration errors from other errors.
29296 - Update RPMs to require libevent 1.1b.
29298 o Packaging, bugfixes:
29299 - Patches so Tor builds with MinGW on Windows.
29300 - Patches so Tor might run on Cygwin again.
29301 - Resume building on non-gcc compilers and ancient gcc. Resume
29302 building with the -O0 compile flag. Resume building cleanly on
29304 - Run correctly on OS X platforms with case-sensitive filesystems.
29305 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
29306 - Add autoconf checks so Tor can build on Solaris x86 again.
29309 - Documented (and renamed) ServerDNSSearchDomains and
29310 ServerDNSResolvConfFile options.
29311 - Be clearer that the *ListenAddress directives can be repeated
29315 Changes in version 0.1.1.24 - 2006-09-29
29317 - Allow really slow clients to not hang up five minutes into their
29318 directory downloads (suggested by Adam J. Richter).
29319 - Fix major performance regression from 0.1.0.x: instead of checking
29320 whether we have enough directory information every time we want to
29321 do something, only check when the directory information has changed.
29322 This should improve client CPU usage by 25-50%.
29323 - Don't crash if, after a server has been running for a while,
29324 it can't resolve its hostname.
29327 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29328 - Don't crash when the controller receives a third argument to an
29329 "extendcircuit" request.
29330 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29331 response; fix error code when "getinfo dir/status/" fails.
29332 - Fix configure.in to not produce broken configure files with
29333 more recent versions of autoconf. Thanks to Clint for his auto*
29335 - Fix security bug on NetBSD that could allow someone to force
29336 uninitialized RAM to be sent to a server's DNS resolver. This
29337 only affects NetBSD and other platforms that do not bounds-check
29339 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
29340 methods: these are known to be buggy.
29341 - If we're a directory mirror and we ask for "all" network status
29342 documents, we would discard status documents from authorities
29343 we don't recognize.
29346 Changes in version 0.1.2.1-alpha - 2006-08-27
29348 - Add "eventdns" async dns library from Adam Langley, tweaked to
29349 build on OSX and Windows. Only enabled if you pass the
29350 --enable-eventdns argument to configure.
29351 - Allow servers with no hostname or IP address to learn their
29352 IP address by asking the directory authorities. This code only
29353 kicks in when you would normally have exited with a "no address"
29354 error. Nothing's authenticated, so use with care.
29355 - Rather than waiting a fixed amount of time between retrying
29356 application connections, we wait only 5 seconds for the first,
29357 10 seconds for the second, and 15 seconds for each retry after
29358 that. Hopefully this will improve the expected user experience.
29359 - Patch from Tup to add support for transparent AP connections:
29360 this basically bundles the functionality of trans-proxy-tor
29361 into the Tor mainline. Now hosts with compliant pf/netfilter
29362 implementations can redirect TCP connections straight to Tor
29363 without diverting through SOCKS. Needs docs.
29364 - Busy directory servers save lots of memory by spooling server
29365 descriptors, v1 directories, and v2 networkstatus docs to buffers
29366 as needed rather than en masse. Also mmap the cached-routers
29367 files, so we don't need to keep the whole thing in memory too.
29368 - Automatically avoid picking more than one node from the same
29369 /16 network when constructing a circuit.
29370 - Revise and clean up the torrc.sample that we ship with; add
29371 a section for BandwidthRate and BandwidthBurst.
29374 - Split circuit_t into origin_circuit_t and or_circuit_t, and
29375 split connection_t into edge, or, dir, control, and base structs.
29376 These will save quite a bit of memory on busy servers, and they'll
29377 also help us track down bugs in the code and bugs in the spec.
29378 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
29379 or later. Log when we are doing this, so we can diagnose it when
29380 it fails. (Also, recommend libevent 1.1b for kqueue and
29381 win32 methods; deprecate libevent 1.0b harder; make libevent
29382 recommendation system saner.)
29383 - Start being able to build universal binaries on OS X (thanks
29385 - Export the default exit policy via the control port, so controllers
29386 don't need to guess what it is / will be later.
29387 - Add a man page entry for ProtocolWarnings.
29388 - Add TestVia config option to the man page.
29389 - Remove even more protocol-related warnings from Tor server logs,
29390 such as bad TLS handshakes and malformed begin cells.
29391 - Stop fetching descriptors if you're not a dir mirror and you
29392 haven't tried to establish any circuits lately. [This currently
29393 causes some dangerous behavior, because when you start up again
29394 you'll use your ancient server descriptors.]
29395 - New DirPort behavior: if you have your dirport set, you download
29396 descriptors aggressively like a directory mirror, whether or not
29397 your ORPort is set.
29398 - Get rid of the router_retry_connections notion. Now routers
29399 no longer try to rebuild long-term connections to directory
29400 authorities, and directory authorities no longer try to rebuild
29401 long-term connections to all servers. We still don't hang up
29402 connections in these two cases though -- we need to look at it
29403 more carefully to avoid flapping, and we likely need to wait til
29404 0.1.1.x is obsolete.
29405 - Drop compatibility with obsolete Tors that permit create cells
29406 to have the wrong circ_id_type.
29407 - Re-enable per-connection rate limiting. Get rid of the "OP
29408 bandwidth" concept. Lay groundwork for "bandwidth classes" --
29409 separate global buckets that apply depending on what sort of conn
29411 - Start publishing one minute or so after we find our ORPort
29412 to be reachable. This will help reduce the number of descriptors
29413 we have for ourselves floating around, since it's quite likely
29414 other things (e.g. DirPort) will change during that minute too.
29415 - Fork the v1 directory protocol into its own spec document,
29416 and mark dir-spec.txt as the currently correct (v2) spec.
29419 - When we find our DirPort to be reachable, publish a new descriptor
29420 so we'll tell the world (reported by pnx).
29421 - Publish a new descriptor after we hup/reload. This is important
29422 if our config has changed such that we'll want to start advertising
29423 our DirPort now, etc.
29424 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29425 - When we have a state file we cannot parse, tell the user and
29426 move it aside. Now we avoid situations where the user starts
29427 Tor in 1904, Tor writes a state file with that timestamp in it,
29428 the user fixes her clock, and Tor refuses to start.
29429 - Fix configure.in to not produce broken configure files with
29430 more recent versions of autoconf. Thanks to Clint for his auto*
29432 - "tor --verify-config" now exits with -1(255) or 0 depending on
29433 whether the config options are bad or good.
29434 - Resolve bug 321 when using dnsworkers: append a period to every
29435 address we resolve at the exit node, so that we do not accidentally
29436 pick up local addresses, and so that failing searches are retried
29437 in the resolver search domains. (This is already solved for
29438 eventdns.) (This breaks Blossom servers for now.)
29439 - If we are using an exit enclave and we can't connect, e.g. because
29440 its webserver is misconfigured to not listen on localhost, then
29441 back off and try connecting from somewhere else before we fail.
29444 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
29445 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
29446 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
29447 when the IP address is mapped through MapAddress to a hostname.
29448 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
29449 useless IPv6 DNS resolves.
29450 - Patch suggested by Karsten Loesing: respond to SIGNAL command
29451 before we execute the signal, in case the signal shuts us down.
29452 - Clean up AllowInvalidNodes man page entry.
29453 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
29454 - Add more asserts to track down an assert error on a windows Tor
29455 server with connection_add being called with socket == -1.
29456 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
29457 - Fix misleading log messages: an entry guard that is "unlisted",
29458 as well as not known to be "down" (because we've never heard
29459 of it), is not therefore "up".
29460 - Remove code to special-case "-cvs" ending, since it has not
29461 actually mattered since 0.0.9.
29462 - Make our socks5 handling more robust to broken socks clients:
29463 throw out everything waiting on the buffer in between socks
29464 handshake phases, since they can't possibly (so the theory
29465 goes) have predicted what we plan to respond to them.
29468 Changes in version 0.1.1.23 - 2006-07-30
29470 - Fast Tor servers, especially exit nodes, were triggering asserts
29471 due to a bug in handling the list of pending DNS resolves. Some
29472 bugs still remain here; we're hunting them.
29473 - Entry guards could crash clients by sending unexpected input.
29474 - More fixes on reachability testing: if you find yourself reachable,
29475 then don't ever make any client requests (so you stop predicting
29476 circuits), then hup or have your clock jump, then later your IP
29477 changes, you won't think circuits are working, so you won't try to
29478 test reachability, so you won't publish.
29481 - Avoid a crash if the controller does a resetconf firewallports
29482 and then a setconf fascistfirewall=1.
29483 - Avoid an integer underflow when the dir authority decides whether
29484 a router is stable: we might wrongly label it stable, and compute
29485 a slightly wrong median stability, when a descriptor is published
29487 - Fix a place where we might trigger an assert if we can't build our
29488 own server descriptor yet.
29491 Changes in version 0.1.1.22 - 2006-07-05
29493 - Fix a big bug that was causing servers to not find themselves
29494 reachable if they changed IP addresses. Since only 0.1.1.22+
29495 servers can do reachability testing correctly, now we automatically
29496 make sure to test via one of these.
29497 - Fix to allow clients and mirrors to learn directory info from
29498 descriptor downloads that get cut off partway through.
29499 - Directory authorities had a bug in deciding if a newly published
29500 descriptor was novel enough to make everybody want a copy -- a few
29501 servers seem to be publishing new descriptors many times a minute.
29503 - Fix a rare bug that was causing some servers to complain about
29504 "closing wedged cpuworkers" and skip some circuit create requests.
29505 - Make the Exit flag in directory status documents actually work.
29508 Changes in version 0.1.1.21 - 2006-06-10
29509 o Crash and assert fixes from 0.1.1.20:
29510 - Fix a rare crash on Tor servers that have enabled hibernation.
29511 - Fix a seg fault on startup for Tor networks that use only one
29512 directory authority.
29513 - Fix an assert from a race condition that occurs on Tor servers
29514 while exiting, where various threads are trying to log that they're
29515 exiting, and delete the logs, at the same time.
29516 - Make our unit tests pass again on certain obscure platforms.
29519 - Add support for building SUSE RPM packages.
29520 - Speed up initial bootstrapping for clients: if we are making our
29521 first ever connection to any entry guard, then don't mark it down
29523 - When only one Tor server in the network is labelled as a guard,
29524 and we've already picked him, we would cycle endlessly picking him
29525 again, being unhappy about it, etc. Now we specifically exclude
29526 current guards when picking a new guard.
29527 - Servers send create cells more reliably after the TLS connection
29528 is established: we were sometimes forgetting to send half of them
29529 when we had more than one pending.
29530 - If we get a create cell that asks us to extend somewhere, but the
29531 Tor server there doesn't match the expected digest, we now send
29532 a destroy cell back, rather than silently doing nothing.
29533 - Make options->RedirectExit work again.
29534 - Make cookie authentication for the controller work again.
29535 - Stop being picky about unusual characters in the arguments to
29536 mapaddress. It's none of our business.
29537 - Add a new config option "TestVia" that lets you specify preferred
29538 middle hops to use for test circuits. Perhaps this will let me
29539 debug the reachability problems better.
29541 o Log / documentation fixes:
29542 - If we're a server and some peer has a broken TLS certificate, don't
29543 log about it unless ProtocolWarnings is set, i.e., we want to hear
29544 about protocol violations by others.
29545 - Fix spelling of VirtualAddrNetwork in man page.
29546 - Add a better explanation at the top of the autogenerated torrc file
29547 about what happened to our old torrc.
29550 Changes in version 0.1.1.20 - 2006-05-23
29552 - Downgrade a log severity where servers complain that they're
29554 - Avoid a compile warning on FreeBSD.
29555 - Remove string size limit on NEWDESC messages; solve bug 291.
29556 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
29557 more thoroughly when we're running on windows.
29560 Changes in version 0.1.1.19-rc - 2006-05-03
29562 - Regenerate our local descriptor if it's dirty and we try to use
29563 it locally (e.g. if it changes during reachability detection).
29564 - If we setconf our ORPort to 0, we continued to listen on the
29565 old ORPort and receive connections.
29566 - Avoid a second warning about machine/limits.h on Debian
29568 - Be willing to add our own routerinfo into the routerlist.
29569 Now authorities will include themselves in their directories
29570 and network-statuses.
29571 - Stop trying to upload rendezvous descriptors to every
29572 directory authority: only try the v1 authorities.
29573 - Servers no longer complain when they think they're not
29574 registered with the directory authorities. There were too many
29576 - Backport dist-rpm changes so rpms can be built without errors.
29579 - Implement an option, VirtualAddrMask, to set which addresses
29580 get handed out in response to mapaddress requests. This works
29581 around a bug in tsocks where 127.0.0.0/8 is never socksified.
29584 Changes in version 0.1.1.18-rc - 2006-04-10
29586 - Work harder to download live network-statuses from all the
29587 directory authorities we know about. Improve the threshold
29588 decision logic so we're more robust to edge cases.
29589 - When fetching rendezvous descriptors, we were willing to ask
29590 v2 authorities too, which would always return 404.
29593 - Stop listing down or invalid nodes in the v1 directory. This will
29594 reduce its bulk by about 1/3, and reduce load on directory
29596 - When deciding whether a router is Fast or Guard-worthy, consider
29597 his advertised BandwidthRate and not just the BandwidthCapacity.
29598 - No longer ship INSTALL and README files -- they are useless now.
29599 - Force rpmbuild to behave and honor target_cpu.
29600 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
29601 - Start to include translated versions of the tor-doc-*.html
29602 files, along with the screenshots. Still needs more work.
29603 - Start sending back 512 and 451 errors if mapaddress fails,
29604 rather than not sending anything back at all.
29605 - When we fail to bind or listen on an incoming or outgoing
29606 socket, we should close it before failing. otherwise we just
29607 leak it. (thanks to weasel for finding.)
29608 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
29609 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
29610 - Make NoPublish (even though deprecated) work again.
29611 - Fix a minor security flaw where a versioning auth dirserver
29612 could list a recommended version many times in a row to make
29613 clients more convinced that it's recommended.
29614 - Fix crash bug if there are two unregistered servers running
29615 with the same nickname, one of them is down, and you ask for
29616 them by nickname in your EntryNodes or ExitNodes. Also, try
29617 to pick the one that's running rather than an arbitrary one.
29618 - Fix an infinite loop we could hit if we go offline for too long.
29619 - Complain when we hit WSAENOBUFS on recv() or write() too.
29620 Perhaps this will help us hunt the bug.
29621 - If you're not a versioning dirserver, don't put the string
29622 "client-versions \nserver-versions \n" in your network-status.
29623 - Lower the minimum required number of file descriptors to 1000,
29624 so we can have some overhead for Valgrind on Linux, where the
29625 default ulimit -n is 1024.
29628 - Add tor.dizum.com as the fifth authoritative directory server.
29629 - Add a new config option FetchUselessDescriptors, off by default,
29630 for when you plan to run "exitlist" on your client and you want
29631 to know about even the non-running descriptors.
29634 Changes in version 0.1.1.17-rc - 2006-03-28
29636 - Clients and servers since 0.1.1.10-alpha have been expiring
29637 connections whenever they are idle for 5 minutes and they *do*
29638 have circuits on them. Oops. With this new version, clients will
29639 discard their previous entry guard choices and avoid choosing
29640 entry guards running these flawed versions.
29641 - Fix memory leak when uncompressing concatenated zlib streams. This
29642 was causing substantial leaks over time on Tor servers.
29643 - The v1 directory was including servers as much as 48 hours old,
29644 because that's how the new routerlist->routers works. Now only
29645 include them if they're 20 hours old or less.
29648 - Resume building on irix64, netbsd 2.0, etc.
29649 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
29651 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
29652 and it is confusing some users.
29653 - Mirrors stop caching the v1 directory so often.
29654 - Make the max number of old descriptors that a cache will hold
29655 rise with the number of directory authorities, so we can scale.
29656 - Change our win32 uname() hack to be more forgiving about what
29657 win32 versions it thinks it's found.
29660 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
29662 - When the controller's *setconf commands fail, collect an error
29663 message in a string and hand it back to the controller.
29664 - Make the v2 dir's "Fast" flag based on relative capacity, just
29665 like "Stable" is based on median uptime. Name everything in the
29666 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
29667 - Log server fingerprint on startup, so new server operators don't
29668 have to go hunting around their filesystem for it.
29669 - Return a robots.txt on our dirport to discourage google indexing.
29670 - Let the controller ask for GETINFO dir/status/foo so it can ask
29671 directly rather than connecting to the dir port. Only works when
29672 dirport is set for now.
29674 o New config options rather than constants in the code:
29675 - SocksTimeout: How long do we let a socks connection wait
29676 unattached before we fail it?
29677 - CircuitBuildTimeout: Cull non-open circuits that were born
29678 at least this many seconds ago.
29679 - CircuitIdleTimeout: Cull open clean circuits that were born
29680 at least this many seconds ago.
29683 Changes in version 0.1.1.16-rc - 2006-03-18
29684 o Bugfixes on 0.1.1.15-rc:
29685 - Fix assert when the controller asks to attachstream a connect-wait
29686 or resolve-wait stream.
29687 - Now do address rewriting when the controller asks us to attach
29688 to a particular circuit too. This will let Blossom specify
29689 "moria2.exit" without having to learn what moria2's IP address is.
29690 - Make the "tor --verify-config" command-line work again, so people
29691 can automatically check if their torrc will parse.
29692 - Authoritative dirservers no longer require an open connection from
29693 a server to consider him "reachable". We need this change because
29694 when we add new auth dirservers, old servers won't know not to
29696 - Let Tor build on Sun CC again.
29697 - Fix an off-by-one buffer size in dirserv.c that magically never
29698 hit our three authorities but broke sjmurdoch's own tor network.
29699 - If we as a directory mirror don't know of any v1 directory
29700 authorities, then don't try to cache any v1 directories.
29701 - Stop warning about unknown servers in our family when they are
29702 given as hex digests.
29703 - Stop complaining as quickly to the server operator that he
29704 hasn't registered his nickname/key binding.
29705 - Various cleanups so we can add new V2 Auth Dirservers.
29706 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
29707 reflect the updated flags in our v2 dir protocol.
29708 - Resume allowing non-printable characters for exit streams (both
29709 for connecting and for resolving). Now we tolerate applications
29710 that don't follow the RFCs. But continue to block malformed names
29713 o Bugfixes on 0.1.0.x:
29714 - Fix assert bug in close_logs(): when we close and delete logs,
29715 remove them all from the global "logfiles" list.
29716 - Fix minor integer overflow in calculating when we expect to use up
29717 our bandwidth allocation before hibernating.
29718 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29719 there are multiple SSLs installed with different versions.
29720 - When we try to be a server and Address is not explicitly set and
29721 our hostname resolves to a private IP address, try to use an
29722 interface address if it has a public address. Now Windows machines
29723 that think of themselves as localhost can work by default.
29726 - Let the controller ask for GETINFO dir/server/foo so it can ask
29727 directly rather than connecting to the dir port.
29728 - Let the controller tell us about certain router descriptors
29729 that it doesn't want Tor to use in circuits. Implement
29730 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29731 - New config option SafeSocks to reject all application connections
29732 using unsafe socks protocols. Defaults to off.
29735 Changes in version 0.1.1.15-rc - 2006-03-11
29736 o Bugfixes and cleanups:
29737 - When we're printing strings from the network, don't try to print
29738 non-printable characters. This protects us against shell escape
29739 sequence exploits, and also against attacks to fool humans into
29740 misreading their logs.
29741 - Fix a bug where Tor would fail to establish any connections if you
29742 left it off for 24 hours and then started it: we were happy with
29743 the obsolete network statuses, but they all referred to router
29744 descriptors that were too old to fetch, so we ended up with no
29745 valid router descriptors.
29746 - Fix a seg fault in the controller's "getinfo orconn-status"
29747 command while listing status on incoming handshaking connections.
29748 Introduce a status name "NEW" for these connections.
29749 - If we get a linelist or linelist_s config option from the torrc
29750 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29751 silently resetting it to its default.
29752 - Don't abandon entry guards until they've been down or gone for
29754 - Cleaner and quieter log messages.
29757 - New controller signal NEWNYM that makes new application requests
29758 use clean circuits.
29759 - Add a new circuit purpose 'controller' to let the controller ask
29760 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29761 controller command to let you specify the purpose if you're
29762 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29763 command to let you change a circuit's purpose after it's been
29765 - Accept "private:*" in routerdesc exit policies; not generated yet
29766 because older Tors do not understand it.
29767 - Add BSD-style contributed startup script "rc.subr" from Peter
29771 Changes in version 0.1.1.14-alpha - 2006-02-20
29772 o Bugfixes on 0.1.1.x:
29773 - Don't die if we ask for a stdout or stderr log (even implicitly)
29774 and we're set to RunAsDaemon -- just warn.
29775 - We still had a few bugs in the OR connection rotation code that
29776 caused directory servers to slowly aggregate connections to other
29777 fast Tor servers. This time for sure!
29778 - Make log entries on Win32 include the name of the function again.
29779 - We were treating a pair of exit policies if they were equal even
29780 if one said accept and the other said reject -- causing us to
29781 not always publish a new descriptor since we thought nothing
29783 - Retry pending server downloads as well as pending networkstatus
29784 downloads when we unexpectedly get a socks request.
29785 - We were ignoring the IS_FAST flag in the directory status,
29786 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29788 - If the controller's SAVECONF command fails (e.g. due to file
29789 permissions), let the controller know that it failed.
29792 - If we're trying to be a Tor server and running Windows 95/98/ME
29793 as a server, explain that we'll likely crash.
29794 - When we're a server, a client asks for an old-style directory,
29795 and our write bucket is empty, don't give it to him. This way
29796 small servers can continue to serve the directory *sometimes*,
29797 without getting overloaded.
29798 - Compress exit policies even more -- look for duplicate lines
29800 - Clients now honor the "guard" flag in the router status when
29801 picking entry guards, rather than looking at is_fast or is_stable.
29802 - Retain unrecognized lines in $DATADIR/state file, so that we can
29803 be forward-compatible.
29804 - Generate 18.0.0.0/8 address policy format in descs when we can;
29805 warn when the mask is not reducible to a bit-prefix.
29806 - Let the user set ControlListenAddress in the torrc. This can be
29807 dangerous, but there are some cases (like a secured LAN) where it
29809 - Split ReachableAddresses into ReachableDirAddresses and
29810 ReachableORAddresses, so we can restrict Dir conns to port 80
29811 and OR conns to port 443.
29812 - Now we can target arch and OS in rpm builds (contributed by
29813 Phobos). Also make the resulting dist-rpm filename match the
29815 - New config options to help controllers: FetchServerDescriptors
29816 and FetchHidServDescriptors for whether to fetch server
29817 info and hidserv info or let the controller do it, and
29818 PublishServerDescriptor and PublishHidServDescriptors.
29819 - Also let the controller set the __AllDirActionsPrivate config
29820 option if you want all directory fetches/publishes to happen via
29821 Tor (it assumes your controller bootstraps your circuits).
29824 Changes in version 0.1.0.17 - 2006-02-17
29825 o Crash bugfixes on 0.1.0.x:
29826 - When servers with a non-zero DirPort came out of hibernation,
29827 sometimes they would trigger an assert.
29829 o Other important bugfixes:
29830 - On platforms that don't have getrlimit (like Windows), we were
29831 artificially constraining ourselves to a max of 1024
29832 connections. Now just assume that we can handle as many as 15000
29833 connections. Hopefully this won't cause other problems.
29835 o Backported features:
29836 - When we're a server, a client asks for an old-style directory,
29837 and our write bucket is empty, don't give it to him. This way
29838 small servers can continue to serve the directory *sometimes*,
29839 without getting overloaded.
29840 - Whenever you get a 503 in response to a directory fetch, try
29841 once more. This will become important once servers start sending
29842 503's whenever they feel busy.
29843 - Fetch a new directory every 120 minutes, not every 40 minutes.
29844 Now that we have hundreds of thousands of users running the old
29845 directory algorithm, it's starting to hurt a lot.
29846 - Bump up the period for forcing a hidden service descriptor upload
29847 from 20 minutes to 1 hour.
29850 Changes in version 0.1.1.13-alpha - 2006-02-09
29851 o Crashes in 0.1.1.x:
29852 - When you tried to setconf ORPort via the controller, Tor would
29853 crash. So people using TorCP to become a server were sad.
29854 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29855 servers. The problem appears to be something do with OpenSSL's
29856 random number generation, or how we call it, or something. Let me
29857 know if the crashes continue.
29858 - Turn crypto hardware acceleration off by default, until we find
29859 somebody smart who can test it for us. (It appears to produce
29860 seg faults in at least some cases.)
29861 - Fix a rare assert error when we've tried all intro points for
29862 a hidden service and we try fetching the service descriptor again:
29863 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29866 - Fix a major load balance bug: we were round-robining in 16 KB
29867 chunks, and servers with bandwidthrate of 20 KB, while downloading
29868 a 600 KB directory, would starve their other connections. Now we
29869 try to be a bit more fair.
29870 - Dir authorities and mirrors were never expiring the newest
29871 descriptor for each server, causing memory and directory bloat.
29872 - Fix memory-bloating and connection-bloating bug on servers: We
29873 were never closing any connection that had ever had a circuit on
29874 it, because we were checking conn->n_circuits == 0, yet we had a
29875 bug that let it go negative.
29876 - Make Tor work using squid as your http proxy again -- squid
29877 returns an error if you ask for a URL that's too long, and it uses
29878 a really generic error message. Plus, many people are behind a
29879 transparent squid so they don't even realize it.
29880 - On platforms that don't have getrlimit (like Windows), we were
29881 artificially constraining ourselves to a max of 1024
29882 connections. Now just assume that we can handle as many as 15000
29883 connections. Hopefully this won't cause other problems.
29884 - Add a new config option ExitPolicyRejectPrivate which defaults to
29885 1. This means all exit policies will begin with rejecting private
29886 addresses, unless the server operator explicitly turns it off.
29889 - Clients no longer download descriptors for non-running
29891 - Before we add new directory authorities, we should make it
29892 clear that only v1 authorities should receive/publish hidden
29893 service descriptors.
29896 - As soon as we've fetched some more directory info, immediately
29897 try to download more server descriptors. This way we don't have
29898 a 10 second pause during initial bootstrapping.
29899 - Remove even more loud log messages that the server operator can't
29901 - When we're running an obsolete or un-recommended version, make
29902 the log message more clear about what the problem is and what
29903 versions *are* still recommended.
29904 - Provide a more useful warn message when our onion queue gets full:
29905 the CPU is too slow or the exit policy is too liberal.
29906 - Don't warn when we receive a 503 from a dirserver/cache -- this
29907 will pave the way for them being able to refuse if they're busy.
29908 - When we fail to bind a listener, try to provide a more useful
29909 log message: e.g., "Is Tor already running?"
29910 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29911 Goldberg can prove things about our handshake protocol more
29913 - MaxConn has been obsolete for a while now. Document the ConnLimit
29914 config option, which is a *minimum* number of file descriptors
29915 that must be available else Tor refuses to start.
29916 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29917 if you log to syslog and want something other than LOG_DAEMON.
29918 - Make dirservers generate a separate "guard" flag to mean,
29919 "would make a good entry guard". Make clients parse it and vote
29920 on it. Not used by clients yet.
29921 - Implement --with-libevent-dir option to ./configure. Also, improve
29922 search techniques to find libevent, and use those for openssl too.
29923 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
29924 - Only start testing reachability once we've established a
29925 circuit. This will make startup on dirservers less noisy.
29926 - Don't try to upload hidden service descriptors until we have
29927 established a circuit.
29928 - Fix the controller's "attachstream 0" command to treat conn like
29929 it just connected, doing address remapping, handling .exit and
29930 .onion idioms, and so on. Now we're more uniform in making sure
29931 that the controller hears about new and closing connections.
29934 Changes in version 0.1.1.12-alpha - 2006-01-11
29935 o Bugfixes on 0.1.1.x:
29936 - The fix to close duplicate server connections was closing all
29937 Tor client connections if they didn't establish a circuit
29938 quickly enough. Oops.
29939 - Fix minor memory issue (double-free) that happened on exit.
29941 o Bugfixes on 0.1.0.x:
29942 - Tor didn't warn when it failed to open a log file.
29945 Changes in version 0.1.1.11-alpha - 2006-01-10
29946 o Crashes in 0.1.1.x:
29947 - Include all the assert/crash fixes from 0.1.0.16.
29948 - If you start Tor and then quit very quickly, there were some
29949 races that tried to free things that weren't allocated yet.
29950 - Fix a rare memory stomp if you're running hidden services.
29951 - Fix segfault when specifying DirServer in config without nickname.
29952 - Fix a seg fault when you finish connecting to a server but at
29953 that moment you dump his server descriptor.
29954 - Extendcircuit and Attachstream controller commands would
29955 assert/crash if you don't give them enough arguments.
29956 - Fix an assert error when we're out of space in the connection_list
29957 and we try to post a hidden service descriptor (reported by weasel).
29958 - If you specify a relative torrc path and you set RunAsDaemon in
29959 your torrc, then it chdir()'s to the new directory. If you HUP,
29960 it tries to load the new torrc location, fails, and exits.
29961 The fix: no longer allow a relative path to torrc using -f.
29964 - Implement "entry guards": automatically choose a handful of entry
29965 nodes and stick with them for all circuits. Only pick new guards
29966 when the ones you have are unsuitable, and if the old guards
29967 become suitable again, switch back. This will increase security
29968 dramatically against certain end-point attacks. The EntryNodes
29969 config option now provides some hints about which entry guards you
29970 want to use most; and StrictEntryNodes means to only use those.
29971 - New directory logic: download by descriptor digest, not by
29972 fingerprint. Caches try to download all listed digests from
29973 authorities; clients try to download "best" digests from caches.
29974 This avoids partitioning and isolating attacks better.
29975 - Make the "stable" router flag in network-status be the median of
29976 the uptimes of running valid servers, and make clients pay
29977 attention to the network-status flags. Thus the cutoff adapts
29978 to the stability of the network as a whole, making IRC, IM, etc
29979 connections more reliable.
29982 - Tor servers with dynamic IP addresses were needing to wait 18
29983 hours before they could start doing reachability testing using
29984 the new IP address and ports. This is because they were using
29985 the internal descriptor to learn what to test, yet they were only
29986 rebuilding the descriptor once they decided they were reachable.
29987 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
29988 to download certain server descriptors, throw them away, and then
29989 fetch them again after 30 minutes. Now mirrors throw away these
29990 server descriptors so clients can't get them.
29991 - We were leaving duplicate connections to other ORs open for a week,
29992 rather than closing them once we detect a duplicate. This only
29993 really affected authdirservers, but it affected them a lot.
29994 - Spread the authdirservers' reachability testing over the entire
29995 testing interval, so we don't try to do 500 TLS's at once every
29999 - If the network is down, and we try to connect to a conn because
30000 we have a circuit in mind, and we timeout (30 seconds) because the
30001 network never answers, we were expiring the circuit, but we weren't
30002 obsoleting the connection or telling the entry_guards functions.
30003 - Some Tor servers process billions of cells per day. These statistics
30004 need to be uint64_t's.
30005 - Check for integer overflows in more places, when adding elements
30006 to smartlists. This could possibly prevent a buffer overflow
30007 on malicious huge inputs. I don't see any, but I haven't looked
30009 - ReachableAddresses kept growing new "reject *:*" lines on every
30011 - When you "setconf log" via the controller, it should remove all
30012 logs. We were automatically adding back in a "log notice stdout".
30013 - Newly bootstrapped Tor networks couldn't establish hidden service
30014 circuits until they had nodes with high uptime. Be more tolerant.
30015 - We were marking servers down when they could not answer every piece
30016 of the directory request we sent them. This was far too harsh.
30017 - Fix the torify (tsocks) config file to not use Tor for localhost
30019 - Directory authorities now go to the proper authority when asking for
30020 a networkstatus, even when they want a compressed one.
30021 - Fix a harmless bug that was causing Tor servers to log
30022 "Got an end because of misc error, but we're not an AP. Closing."
30023 - Authorities were treating their own descriptor changes as cosmetic,
30024 meaning the descriptor available in the network-status and the
30025 descriptor that clients downloaded were different.
30026 - The OS X installer was adding a symlink for tor_resolve but
30027 the binary was called tor-resolve (reported by Thomas Hardly).
30028 - Workaround a problem with some http proxies where they refuse GET
30029 requests that specify "Content-Length: 0" (reported by Adrian).
30030 - Fix wrong log message when you add a "HiddenServiceNodes" config
30031 line without any HiddenServiceDir line (reported by Chris Thomas).
30034 - Write the TorVersion into the state file so we have a prayer of
30035 keeping forward and backward compatibility.
30036 - Revive the FascistFirewall config option rather than eliminating it:
30037 now it's a synonym for ReachableAddresses *:80,*:443.
30038 - Clients choose directory servers from the network status lists,
30039 not from their internal list of router descriptors. Now they can
30040 go to caches directly rather than needing to go to authorities
30042 - Directory authorities ignore router descriptors that have only
30043 cosmetic differences: do this for 0.1.0.x servers now too.
30044 - Add a new flag to network-status indicating whether the server
30045 can answer v2 directory requests too.
30046 - Authdirs now stop whining so loudly about bad descriptors that
30047 they fetch from other dirservers. So when there's a log complaint,
30048 it's for sure from a freshly uploaded descriptor.
30049 - Reduce memory requirements in our structs by changing the order
30051 - There used to be two ways to specify your listening ports in a
30052 server descriptor: on the "router" line and with a separate "ports"
30053 line. Remove support for the "ports" line.
30054 - New config option "AuthDirRejectUnlisted" for auth dirservers as
30055 a panic button: if we get flooded with unusable servers we can
30056 revert to only listing servers in the approved-routers file.
30057 - Auth dir servers can now mark a fingerprint as "!reject" or
30058 "!invalid" in the approved-routers file (as its nickname), to
30059 refuse descriptors outright or include them but marked as invalid.
30060 - Servers store bandwidth history across restarts/crashes.
30061 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
30062 get a better idea of why their circuits failed. Not used yet.
30063 - Directory mirrors now cache up to 16 unrecognized network-status
30064 docs. Now we can add new authdirservers and they'll be cached too.
30065 - When picking a random directory, prefer non-authorities if any
30067 - New controller option "getinfo desc/all-recent" to fetch the
30068 latest server descriptor for every router that Tor knows about.
30071 Changes in version 0.1.0.16 - 2006-01-02
30072 o Crash bugfixes on 0.1.0.x:
30073 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
30074 corrupting the heap, losing FDs, or crashing when we need to resize
30075 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
30076 - It turns out sparc64 platforms crash on unaligned memory access
30077 too -- so detect and avoid this.
30078 - Handle truncated compressed data correctly (by detecting it and
30080 - Fix possible-but-unlikely free(NULL) in control.c.
30081 - When we were closing connections, there was a rare case that
30082 stomped on memory, triggering seg faults and asserts.
30083 - Avoid potential infinite recursion when building a descriptor. (We
30084 don't know that it ever happened, but better to fix it anyway.)
30085 - We were neglecting to unlink marked circuits from soon-to-close OR
30086 connections, which caused some rare scribbling on freed memory.
30087 - Fix a memory stomping race bug when closing the joining point of two
30088 rendezvous circuits.
30089 - Fix an assert in time parsing found by Steven Murdoch.
30091 o Other bugfixes on 0.1.0.x:
30092 - When we're doing reachability testing, provide more useful log
30093 messages so the operator knows what to expect.
30094 - Do not check whether DirPort is reachable when we are suppressing
30095 advertising it because of hibernation.
30096 - When building with -static or on Solaris, we sometimes needed -ldl.
30097 - When we're deciding whether a stream has enough circuits around
30098 that can handle it, count the freshly dirty ones and not the ones
30099 that are so dirty they won't be able to handle it.
30100 - When we're expiring old circuits, we had a logic error that caused
30101 us to close new rendezvous circuits rather than old ones.
30102 - Give a more helpful log message when you try to change ORPort via
30103 the controller: you should upgrade Tor if you want that to work.
30104 - We were failing to parse Tor versions that start with "Tor ".
30105 - Tolerate faulty streams better: when a stream fails for reason
30106 exitpolicy, stop assuming that the router is lying about his exit
30107 policy. When a stream fails for reason misc, allow it to retry just
30108 as if it was resolvefailed. When a stream has failed three times,
30109 reset its failure count so we can try again and get all three tries.
30112 Changes in version 0.1.1.10-alpha - 2005-12-11
30113 o Correctness bugfixes on 0.1.0.x:
30114 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
30115 corrupting the heap, losing FDs, or crashing when we need to resize
30116 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
30117 - Stop doing the complex voodoo overkill checking for insecure
30118 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
30119 - When we were closing connections, there was a rare case that
30120 stomped on memory, triggering seg faults and asserts.
30121 - We were neglecting to unlink marked circuits from soon-to-close OR
30122 connections, which caused some rare scribbling on freed memory.
30123 - When we're deciding whether a stream has enough circuits around
30124 that can handle it, count the freshly dirty ones and not the ones
30125 that are so dirty they won't be able to handle it.
30126 - Recover better from TCP connections to Tor servers that are
30127 broken but don't tell you (it happens!); and rotate TLS
30128 connections once a week.
30129 - When we're expiring old circuits, we had a logic error that caused
30130 us to close new rendezvous circuits rather than old ones.
30131 - Fix a scary-looking but apparently harmless bug where circuits
30132 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
30133 servers, and never switch to state CIRCUIT_STATE_OPEN.
30134 - When building with -static or on Solaris, we sometimes needed to
30136 - Give a useful message when people run Tor as the wrong user,
30137 rather than telling them to start chowning random directories.
30138 - We were failing to inform the controller about new .onion streams.
30140 o Security bugfixes on 0.1.0.x:
30141 - Refuse server descriptors if the fingerprint line doesn't match
30142 the included identity key. Tor doesn't care, but other apps (and
30143 humans) might actually be trusting the fingerprint line.
30144 - We used to kill the circuit when we receive a relay command we
30145 don't recognize. Now we just drop it.
30146 - Start obeying our firewall options more rigorously:
30147 . If we can't get to a dirserver directly, try going via Tor.
30148 . Don't ever try to connect (as a client) to a place our
30149 firewall options forbid.
30150 . If we specify a proxy and also firewall options, obey the
30151 firewall options even when we're using the proxy: some proxies
30152 can only proxy to certain destinations.
30153 - Fix a bug found by Lasse Overlier: when we were making internal
30154 circuits (intended to be cannibalized later for rendezvous and
30155 introduction circuits), we were picking them so that they had
30156 useful exit nodes. There was no need for this, and it actually
30157 aids some statistical attacks.
30158 - Start treating internal circuits and exit circuits separately.
30159 It's important to keep them separate because internal circuits
30160 have their last hops picked like middle hops, rather than like
30161 exit hops. So exiting on them will break the user's expectations.
30163 o Bugfixes on 0.1.1.x:
30164 - Take out the mis-feature where we tried to detect IP address
30165 flapping for people with DynDNS, and chose not to upload a new
30166 server descriptor sometimes.
30167 - Try to be compatible with OpenSSL 0.9.6 again.
30168 - Log fix: when the controller is logging about .onion addresses,
30169 sometimes it didn't include the ".onion" part of the address.
30170 - Don't try to modify options->DirServers internally -- if the
30171 user didn't specify any, just add the default ones directly to
30172 the trusted dirserver list. This fixes a bug where people running
30173 controllers would use SETCONF on some totally unrelated config
30174 option, and Tor would start yelling at them about changing their
30176 - Let the controller's redirectstream command specify a port, in
30177 case the controller wants to change that too.
30178 - When we requested a pile of server descriptors, we sometimes
30179 accidentally launched a duplicate request for the first one.
30180 - Bugfix for trackhostexits: write down the fingerprint of the
30181 chosen exit, not its nickname, because the chosen exit might not
30183 - When parsing foo.exit, if foo is unknown, and we are leaving
30184 circuits unattached, set the chosen_exit field and leave the
30185 address empty. This matters because controllers got confused
30187 - Directory authorities no longer try to download server
30188 descriptors that they know they will reject.
30190 o Features and updates:
30191 - Replace balanced trees with hash tables: this should make stuff
30192 significantly faster.
30193 - Resume using the AES counter-mode implementation that we ship,
30194 rather than OpenSSL's. Ours is significantly faster.
30195 - Many other CPU and memory improvements.
30196 - Add a new config option FastFirstHopPK (on by default) so clients
30197 do a trivial crypto handshake for their first hop, since TLS has
30198 already taken care of confidentiality and authentication.
30199 - Add a new config option TestSocks so people can see if their
30200 applications are using socks4, socks4a, socks5-with-ip, or
30201 socks5-with-hostname. This way they don't have to keep mucking
30202 with tcpdump and wondering if something got cached somewhere.
30203 - Warn when listening on a public address for socks. I suspect a
30204 lot of people are setting themselves up as open socks proxies,
30205 and they have no idea that jerks on the Internet are using them,
30206 since they simply proxy the traffic into the Tor network.
30207 - Add "private:*" as an alias in configuration for policies. Now
30208 you can simplify your exit policy rather than needing to list
30209 every single internal or nonroutable network space.
30210 - Add a new controller event type that allows controllers to get
30211 all server descriptors that were uploaded to a router in its role
30212 as authoritative dirserver.
30213 - Start shipping socks-extensions.txt, tor-doc-unix.html,
30214 tor-doc-server.html, and stylesheet.css in the tarball.
30215 - Stop shipping tor-doc.html in the tarball.
30218 Changes in version 0.1.1.9-alpha - 2005-11-15
30219 o Usability improvements:
30220 - Start calling it FooListenAddress rather than FooBindAddress,
30221 since few of our users know what it means to bind an address
30223 - Reduce clutter in server logs. We're going to try to make
30224 them actually usable now. New config option ProtocolWarnings that
30225 lets you hear about how _other Tors_ are breaking the protocol. Off
30227 - Divide log messages into logging domains. Once we put some sort
30228 of interface on this, it will let people looking at more verbose
30229 log levels specify the topics they want to hear more about.
30230 - Make directory servers return better http 404 error messages
30231 instead of a generic "Servers unavailable".
30232 - Check for even more Windows version flags when writing the platform
30233 string in server descriptors, and note any we don't recognize.
30234 - Clean up more of the OpenSSL memory when exiting, so we can detect
30235 memory leaks better.
30236 - Make directory authorities be non-versioning, non-naming by
30237 default. Now we can add new directory servers without requiring
30238 their operators to pay close attention.
30239 - When logging via syslog, include the pid whenever we provide
30240 a log entry. Suggested by Todd Fries.
30242 o Performance improvements:
30243 - Directory servers now silently throw away new descriptors that
30244 haven't changed much if the timestamps are similar. We do this to
30245 tolerate older Tor servers that upload a new descriptor every 15
30246 minutes. (It seemed like a good idea at the time.)
30247 - Inline bottleneck smartlist functions; use fast versions by default.
30248 - Add a "Map from digest to void*" abstraction digestmap_t so we
30249 can do less hex encoding/decoding. Use it in router_get_by_digest()
30250 to resolve a performance bottleneck.
30251 - Allow tor_gzip_uncompress to extract as much as possible from
30252 truncated compressed data. Try to extract as many
30253 descriptors as possible from truncated http responses (when
30254 DIR_PURPOSE_FETCH_ROUTERDESC).
30255 - Make circ->onionskin a pointer, not a static array. moria2 was using
30256 125000 circuit_t's after it had been up for a few weeks, which
30257 translates to 20+ megs of wasted space.
30258 - The private half of our EDH handshake keys are now chosen out
30259 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
30261 o Security improvements:
30262 - Start making directory caches retain old routerinfos, so soon
30263 clients can start asking by digest of descriptor rather than by
30264 fingerprint of server.
30265 - Add half our entropy from RAND_poll in OpenSSL. This knows how
30266 to use egd (if present), openbsd weirdness (if present), vms/os2
30267 weirdness (if we ever port there), and more in the future.
30269 o Bugfixes on 0.1.0.x:
30270 - Do round-robin writes of at most 16 kB per write. This might be
30271 more fair on loaded Tor servers, and it might resolve our Windows
30272 crash bug. It might also slow things down.
30273 - Our TLS handshakes were generating a single public/private
30274 keypair for the TLS context, rather than making a new one for
30275 each new connections. Oops. (But we were still rotating them
30276 periodically, so it's not so bad.)
30277 - When we were cannibalizing a circuit with a particular exit
30278 node in mind, we weren't checking to see if that exit node was
30279 already present earlier in the circuit. Oops.
30280 - When a Tor server's IP changes (e.g. from a dyndns address),
30281 upload a new descriptor so clients will learn too.
30282 - Really busy servers were keeping enough circuits open on stable
30283 connections that they were wrapping around the circuit_id
30284 space. (It's only two bytes.) This exposed a bug where we would
30285 feel free to reuse a circuit_id even if it still exists but has
30286 been marked for close. Try to fix this bug. Some bug remains.
30287 - If we would close a stream early (e.g. it asks for a .exit that
30288 we know would refuse it) but the LeaveStreamsUnattached config
30289 option is set by the controller, then don't close it.
30291 o Bugfixes on 0.1.1.8-alpha:
30292 - Fix a big pile of memory leaks, some of them serious.
30293 - Do not try to download a routerdesc if we would immediately reject
30295 - Resume inserting a newline between all router descriptors when
30296 generating (old style) signed directories, since our spec says
30298 - When providing content-type application/octet-stream for
30299 server descriptors using .z, we were leaving out the
30300 content-encoding header. Oops. (Everything tolerated this just
30301 fine, but that doesn't mean we need to be part of the problem.)
30302 - Fix a potential seg fault in getconf and getinfo using version 1
30303 of the controller protocol.
30304 - Avoid crash: do not check whether DirPort is reachable when we
30305 are suppressing it because of hibernation.
30306 - Make --hash-password not crash on exit.
30309 Changes in version 0.1.1.8-alpha - 2005-10-07
30310 o New features (major):
30311 - Clients don't download or use the directory anymore. Now they
30312 download and use network-statuses from the trusted dirservers,
30313 and fetch individual server descriptors as needed from mirrors.
30314 See dir-spec.txt for all the gory details.
30315 - Be more conservative about whether to advertise our DirPort.
30316 The main change is to not advertise if we're running at capacity
30317 and either a) we could hibernate or b) our capacity is low and
30318 we're using a default DirPort.
30319 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
30321 o New features (minor):
30322 - Try to be smart about when to retry network-status and
30323 server-descriptor fetches. Still needs some tuning.
30324 - Stop parsing, storing, or using running-routers output (but
30325 mirrors still cache and serve it).
30326 - Consider a threshold of versioning dirservers (dirservers who have
30327 an opinion about which Tor versions are still recommended) before
30328 deciding whether to warn the user that he's obsolete.
30329 - Dirservers can now reject/invalidate by key and IP, with the
30330 config options "AuthDirInvalid" and "AuthDirReject". This is
30331 useful since currently we automatically list servers as running
30332 and usable even if we know they're jerks.
30333 - Provide dire warnings to any users who set DirServer; move it out
30334 of torrc.sample and into torrc.complete.
30335 - Add MyFamily to torrc.sample in the server section.
30336 - Add nicknames to the DirServer line, so we can refer to them
30337 without requiring all our users to memorize their IP addresses.
30338 - When we get an EOF or a timeout on a directory connection, note
30339 how many bytes of serverdesc we are dropping. This will help
30340 us determine whether it is smart to parse incomplete serverdesc
30342 - Add a new function to "change pseudonyms" -- that is, to stop
30343 using any currently-dirty circuits for new streams, so we don't
30344 link new actions to old actions. Currently it's only called on
30345 HUP (or SIGNAL RELOAD).
30346 - On sighup, if UseHelperNodes changed to 1, use new circuits.
30347 - Start using RAND_bytes rather than RAND_pseudo_bytes from
30348 OpenSSL. Also, reseed our entropy every hour, not just at
30349 startup. And entropy in 512-bit chunks, not 160-bit chunks.
30351 o Fixes on 0.1.1.7-alpha:
30352 - Nobody ever implemented EVENT_ADDRMAP for control protocol
30353 version 0, so don't let version 0 controllers ask for it.
30354 - If you requested something with too many newlines via the
30355 v1 controller protocol, you could crash tor.
30356 - Fix a number of memory leaks, including some pretty serious ones.
30357 - Re-enable DirPort testing again, so Tor servers will be willing
30358 to advertise their DirPort if it's reachable.
30359 - On TLS handshake, only check the other router's nickname against
30360 its expected nickname if is_named is set.
30362 o Fixes forward-ported from 0.1.0.15:
30363 - Don't crash when we don't have any spare file descriptors and we
30364 try to spawn a dns or cpu worker.
30365 - Make the numbers in read-history and write-history into uint64s,
30366 so they don't overflow and publish negatives in the descriptor.
30368 o Fixes on 0.1.0.x:
30369 - For the OS X package's modified privoxy config file, comment
30370 out the "logfile" line so we don't log everything passed
30372 - We were whining about using socks4 or socks5-with-local-lookup
30373 even when it's an IP in the "virtual" range we designed exactly
30375 - We were leaking some memory every time the client changes IPs.
30376 - Never call free() on tor_malloc()d memory. This will help us
30377 use dmalloc to detect memory leaks.
30378 - Check for named servers when looking them up by nickname;
30379 warn when we'recalling a non-named server by its nickname;
30380 don't warn twice about the same name.
30381 - Try to list MyFamily elements by key, not by nickname, and warn
30382 if we've not heard of the server.
30383 - Make windows platform detection (uname equivalent) smarter.
30384 - It turns out sparc64 doesn't like unaligned access either.
30387 Changes in version 0.1.0.15 - 2005-09-23
30388 o Bugfixes on 0.1.0.x:
30389 - Reject ports 465 and 587 (spam targets) in default exit policy.
30390 - Don't crash when we don't have any spare file descriptors and we
30391 try to spawn a dns or cpu worker.
30392 - Get rid of IgnoreVersion undocumented config option, and make us
30393 only warn, never exit, when we're running an obsolete version.
30394 - Don't try to print a null string when your server finds itself to
30395 be unreachable and the Address config option is empty.
30396 - Make the numbers in read-history and write-history into uint64s,
30397 so they don't overflow and publish negatives in the descriptor.
30398 - Fix a minor memory leak in smartlist_string_remove().
30399 - We were only allowing ourselves to upload a server descriptor at
30400 most every 20 minutes, even if it changed earlier than that.
30401 - Clean up log entries that pointed to old URLs.
30404 Changes in version 0.1.1.7-alpha - 2005-09-14
30405 o Fixes on 0.1.1.6-alpha:
30406 - Exit servers were crashing when people asked them to make a
30407 connection to an address not in their exit policy.
30408 - Looking up a non-existent stream for a v1 control connection would
30410 - Fix a seg fault if we ask a dirserver for a descriptor by
30411 fingerprint but he doesn't know about him.
30412 - SETCONF was appending items to linelists, not clearing them.
30413 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
30414 out and refuse the setconf if it would fail.
30415 - Downgrade the dirserver log messages when whining about
30419 - Add Peter Palfrader's check-tor script to tor/contrib/
30420 It lets you easily check whether a given server (referenced by
30421 nickname) is reachable by you.
30422 - Numerous changes to move towards client-side v2 directories. Not
30425 o Fixes on 0.1.0.x:
30426 - If the user gave tor an odd number of command-line arguments,
30427 we were silently ignoring the last one. Now we complain and fail.
30428 [This wins the oldest-bug prize -- this bug has been present since
30429 November 2002, as released in Tor 0.0.0.]
30430 - Do not use unaligned memory access on alpha, mips, or mipsel.
30431 It *works*, but is very slow, so we treat them as if it doesn't.
30432 - Retry directory requests if we fail to get an answer we like
30433 from a given dirserver (we were retrying before, but only if
30434 we fail to connect).
30435 - When writing the RecommendedVersions line, sort them first.
30436 - When the client asked for a rendezvous port that the hidden
30437 service didn't want to provide, we were sending an IP address
30438 back along with the end cell. Fortunately, it was zero. But stop
30440 - Correct "your server is reachable" log entries to indicate that
30441 it was self-testing that told us so.
30444 Changes in version 0.1.1.6-alpha - 2005-09-09
30445 o Fixes on 0.1.1.5-alpha:
30446 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
30447 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
30448 - Fix bug with tor_memmem finding a match at the end of the string.
30449 - Make unit tests run without segfaulting.
30450 - Resolve some solaris x86 compile warnings.
30451 - Handle duplicate lines in approved-routers files without warning.
30452 - Fix bug where as soon as a server refused any requests due to his
30453 exit policy (e.g. when we ask for localhost and he tells us that's
30454 127.0.0.1 and he won't do it), we decided he wasn't obeying his
30455 exit policy using him for any exits.
30456 - Only do openssl hardware accelerator stuff if openssl version is
30459 o New controller features/fixes:
30460 - Add a "RESETCONF" command so you can set config options like
30461 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
30462 a config option in the torrc with no value, then it clears it
30463 entirely (rather than setting it to its default).
30464 - Add a "GETINFO config-file" to tell us where torrc is.
30465 - Avoid sending blank lines when GETINFO replies should be empty.
30466 - Add a QUIT command for the controller (for using it manually).
30467 - Fix a bug in SAVECONF that was adding default dirservers and
30468 other redundant entries to the torrc file.
30470 o Start on the new directory design:
30471 - Generate, publish, cache, serve new network-status format.
30472 - Publish individual descriptors (by fingerprint, by "all", and by
30474 - Publish client and server recommended versions separately.
30475 - Allow tor_gzip_uncompress() to handle multiple concatenated
30476 compressed strings. Serve compressed groups of router
30477 descriptors. The compression logic here could be more
30479 - Distinguish v1 authorities (all currently trusted directories)
30480 from v2 authorities (all trusted directories).
30481 - Change DirServers config line to note which dirs are v1 authorities.
30482 - Add configuration option "V1AuthoritativeDirectory 1" which
30483 moria1, moria2, and tor26 should set.
30484 - Remove option when getting directory cache to see whether they
30485 support running-routers; they all do now. Replace it with one
30486 to see whether caches support v2 stuff.
30489 - Dirservers now do their own external reachability testing of each
30490 Tor server, and only list them as running if they've been found to
30491 be reachable. We also send back warnings to the server's logs if
30492 it uploads a descriptor that we already believe is unreachable.
30493 - Implement exit enclaves: if we know an IP address for the
30494 destination, and there's a running Tor server at that address
30495 which allows exit to the destination, then extend the circuit to
30496 that exit first. This provides end-to-end encryption and end-to-end
30497 authentication. Also, if the user wants a .exit address or enclave,
30498 use 4 hops rather than 3, and cannibalize a general circ for it
30500 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
30501 controller. Also, rotate dns and cpu workers if the controller
30502 changes options that will affect them; and initialize the dns
30503 worker cache tree whether or not we start out as a server.
30504 - Only upload a new server descriptor when options change, 18
30505 hours have passed, uptime is reset, or bandwidth changes a lot.
30506 - Check [X-]Forwarded-For headers in HTTP requests when generating
30507 log messages. This lets people run dirservers (and caches) behind
30508 Apache but still know which IP addresses are causing warnings.
30510 o Config option changes:
30511 - Replace (Fascist)Firewall* config options with a new
30512 ReachableAddresses option that understands address policies.
30513 For example, "ReachableAddresses *:80,*:443"
30514 - Get rid of IgnoreVersion undocumented config option, and make us
30515 only warn, never exit, when we're running an obsolete version.
30516 - Make MonthlyAccountingStart config option truly obsolete now.
30518 o Fixes on 0.1.0.x:
30519 - Reject ports 465 and 587 in the default exit policy, since
30520 people have started using them for spam too.
30521 - It turns out we couldn't bootstrap a network since we added
30522 reachability detection in 0.1.0.1-rc. Good thing the Tor network
30523 has never gone down. Add an AssumeReachable config option to let
30524 servers and dirservers bootstrap. When we're trying to build a
30525 high-uptime or high-bandwidth circuit but there aren't enough
30526 suitable servers, try being less picky rather than simply failing.
30527 - Our logic to decide if the OR we connected to was the right guy
30528 was brittle and maybe open to a mitm for unverified routers.
30529 - We weren't cannibalizing circuits correctly for
30530 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
30531 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
30532 build those from scratch. This should make hidden services faster.
30533 - Predict required circuits better, with an eye toward making hidden
30534 services faster on the service end.
30535 - Retry streams if the exit node sends back a 'misc' failure. This
30536 should result in fewer random failures. Also, after failing
30537 from resolve failed or misc, reset the num failures, so we give
30538 it a fair shake next time we try.
30539 - Clean up the rendezvous warn log msgs, and downgrade some to info.
30540 - Reduce severity on logs about dns worker spawning and culling.
30541 - When we're shutting down and we do something like try to post a
30542 server descriptor or rendezvous descriptor, don't complain that
30543 we seem to be unreachable. Of course we are, we're shutting down.
30544 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
30545 We don't use them yet, but maybe one day our DNS resolver will be
30546 able to discover them.
30547 - Make ContactInfo mandatory for authoritative directory servers.
30548 - Require server descriptors to list IPv4 addresses -- hostnames
30549 are no longer allowed. This also fixes some potential security
30550 problems with people providing hostnames as their address and then
30551 preferentially resolving them to partition users.
30552 - Change log line for unreachability to explicitly suggest /etc/hosts
30553 as the culprit. Also make it clearer what IP address and ports we're
30554 testing for reachability.
30555 - Put quotes around user-supplied strings when logging so users are
30556 more likely to realize if they add bad characters (like quotes)
30558 - Let auth dir servers start without specifying an Address config
30560 - Make unit tests (and other invocations that aren't the real Tor)
30561 run without launching listeners, creating subdirectories, and so on.
30564 Changes in version 0.1.1.5-alpha - 2005-08-08
30565 o Bugfixes included in 0.1.0.14.
30567 o Bugfixes on 0.1.0.x:
30568 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
30569 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
30570 it would silently using ignore the 6668.
30573 Changes in version 0.1.0.14 - 2005-08-08
30574 o Bugfixes on 0.1.0.x:
30575 - Fix the other half of the bug with crypto handshakes
30577 - Fix an assert trigger if you send a 'signal term' via the
30578 controller when it's listening for 'event info' messages.
30581 Changes in version 0.1.1.4-alpha - 2005-08-04
30582 o Bugfixes included in 0.1.0.13.
30585 - Improve tor_gettimeofday() granularity on windows.
30586 - Make clients regenerate their keys when their IP address changes.
30587 - Implement some more GETINFO goodness: expose helper nodes, config
30588 options, getinfo keys.
30591 Changes in version 0.1.0.13 - 2005-08-04
30592 o Bugfixes on 0.1.0.x:
30593 - Fix a critical bug in the security of our crypto handshakes.
30594 - Fix a size_t underflow in smartlist_join_strings2() that made
30595 it do bad things when you hand it an empty smartlist.
30596 - Fix Windows installer to ship Tor license (thanks to Aphex for
30597 pointing out this oversight) and put a link to the doc directory
30599 - Explicitly set no-unaligned-access for sparc: it turns out the
30600 new gcc's let you compile broken code, but that doesn't make it
30604 Changes in version 0.1.1.3-alpha - 2005-07-23
30605 o Bugfixes on 0.1.1.2-alpha:
30606 - Fix a bug in handling the controller's "post descriptor"
30608 - Fix several bugs in handling the controller's "extend circuit"
30610 - Fix a bug in handling the controller's "stream status" event.
30611 - Fix an assert failure if we have a controller listening for
30612 circuit events and we go offline.
30613 - Re-allow hidden service descriptors to publish 0 intro points.
30614 - Fix a crash when generating your hidden service descriptor if
30615 you don't have enough intro points already.
30617 o New features on 0.1.1.2-alpha:
30618 - New controller function "getinfo accounting", to ask how
30619 many bytes we've used in this time period.
30620 - Experimental support for helper nodes: a lot of the risk from
30621 a small static adversary comes because users pick new random
30622 nodes every time they rebuild a circuit. Now users will try to
30623 stick to the same small set of entry nodes if they can. Not
30624 enabled by default yet.
30626 o Bugfixes on 0.1.0.12:
30627 - If you're an auth dir server, always publish your dirport,
30628 even if you haven't yet found yourself to be reachable.
30629 - Fix a size_t underflow in smartlist_join_strings2() that made
30630 it do bad things when you hand it an empty smartlist.
30633 Changes in version 0.1.0.12 - 2005-07-18
30634 o New directory servers:
30635 - tor26 has changed IP address.
30637 o Bugfixes on 0.1.0.x:
30638 - Fix a possible double-free in tor_gzip_uncompress().
30639 - When --disable-threads is set, do not search for or link against
30640 pthreads libraries.
30641 - Don't trigger an assert if an authoritative directory server
30642 claims its dirport is 0.
30643 - Fix bug with removing Tor as an NT service: some people were
30644 getting "The service did not return an error." Thanks to Matt
30648 Changes in version 0.1.1.2-alpha - 2005-07-15
30649 o New directory servers:
30650 - tor26 has changed IP address.
30652 o Bugfixes on 0.1.0.x, crashes/leaks:
30653 - Port the servers-not-obeying-their-exit-policies fix from
30655 - Fix an fd leak in start_daemon().
30656 - On Windows, you can't always reopen a port right after you've
30657 closed it. So change retry_listeners() to only close and re-open
30658 ports that have changed.
30659 - Fix a possible double-free in tor_gzip_uncompress().
30661 o Bugfixes on 0.1.0.x, usability:
30662 - When tor_socketpair() fails in Windows, give a reasonable
30663 Windows-style errno back.
30664 - Let people type "tor --install" as well as "tor -install" when
30666 want to make it an NT service.
30667 - NT service patch from Matt Edman to improve error messages.
30668 - When the controller asks for a config option with an abbreviated
30669 name, give the full name in our response.
30670 - Correct the man page entry on TrackHostExitsExpire.
30671 - Looks like we were never delivering deflated (i.e. compressed)
30672 running-routers lists, even when asked. Oops.
30673 - When --disable-threads is set, do not search for or link against
30674 pthreads libraries.
30676 o Bugfixes on 0.1.1.x:
30677 - Fix a seg fault with autodetecting which controller version is
30681 - New hidden service descriptor format: put a version in it, and
30682 let people specify introduction/rendezvous points that aren't
30683 in "the directory" (which is subjective anyway).
30684 - Allow the DEBUG controller event to work again. Mark certain log
30685 entries as "don't tell this to controllers", so we avoid cycles.
30688 Changes in version 0.1.0.11 - 2005-06-30
30689 o Bugfixes on 0.1.0.x:
30690 - Fix major security bug: servers were disregarding their
30691 exit policies if clients behaved unexpectedly.
30692 - Make OS X init script check for missing argument, so we don't
30693 confuse users who invoke it incorrectly.
30694 - Fix a seg fault in "tor --hash-password foo".
30695 - The MAPADDRESS control command was broken.
30698 Changes in version 0.1.1.1-alpha - 2005-06-29
30700 - Make OS X init script check for missing argument, so we don't
30701 confuse users who invoke it incorrectly.
30702 - Fix a seg fault in "tor --hash-password foo".
30703 - Fix a possible way to DoS dirservers.
30704 - When we complain that your exit policy implicitly allows local or
30705 private address spaces, name them explicitly so operators can
30707 - Make the log message less scary when all the dirservers are
30708 temporarily unreachable.
30709 - We were printing the number of idle dns workers incorrectly when
30713 - Revised controller protocol (version 1) that uses ascii rather
30714 than binary. Add supporting libraries in python and java so you
30715 can use the controller from your applications without caring how
30716 our protocol works.
30717 - Spiffy new support for crypto hardware accelerators. Can somebody
30721 Changes in version 0.0.9.10 - 2005-06-16
30722 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30723 - Refuse relay cells that claim to have a length larger than the
30724 maximum allowed. This prevents a potential attack that could read
30725 arbitrary memory (e.g. keys) from an exit server's process
30729 Changes in version 0.1.0.10 - 2005-06-14
30730 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30731 libevent before 1.1a.
30734 Changes in version 0.1.0.9-rc - 2005-06-09
30736 - Reset buf->highwater every time buf_shrink() is called, not just on
30737 a successful shrink. This was causing significant memory bloat.
30738 - Fix buffer overflow when checking hashed passwords.
30739 - Security fix: if seeding the RNG on Win32 fails, quit.
30740 - Allow seeding the RNG on Win32 even when you're not running as
30742 - Disable threading on Solaris too. Something is wonky with it,
30743 cpuworkers, and reentrant libs.
30744 - Reenable the part of the code that tries to flush as soon as an
30745 OR outbuf has a full TLS record available. Perhaps this will make
30746 OR outbufs not grow as huge except in rare cases, thus saving lots
30747 of CPU time plus memory.
30748 - Reject malformed .onion addresses rather then passing them on as
30749 normal web requests.
30750 - Adapt patch from Adam Langley: fix possible memory leak in
30751 tor_lookup_hostname().
30752 - Initialize libevent later in the startup process, so the logs are
30753 already established by the time we start logging libevent warns.
30754 - Use correct errno on win32 if libevent fails.
30755 - Check and warn about known-bad/slow libevent versions.
30756 - Pay more attention to the ClientOnly config option.
30757 - Have torctl.in/tor.sh.in check for location of su binary (needed
30759 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30760 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30761 HttpProxyAuthenticator
30762 - Stop warning about sigpipes in the logs. We're going to
30763 pretend that getting these occasionally is normal and fine.
30764 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30766 installer screens; and don't put stuff into StartupItems unless
30767 the user asks you to.
30768 - Require servers that use the default dirservers to have public IP
30769 addresses. We have too many servers that are configured with private
30770 IPs and their admins never notice the log entries complaining that
30771 their descriptors are being rejected.
30772 - Add OSX uninstall instructions. An actual uninstall script will
30776 Changes in version 0.1.0.8-rc - 2005-05-23
30778 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30779 panics. Disable kqueue on all OS X Tors.
30780 - Fix RPM: remove duplicate line accidentally added to the rpm
30782 - Disable threads on openbsd too, since its gethostaddr is not
30784 - Tolerate libevent 0.8 since it still works, even though it's
30786 - Enable building on Red Hat 9.0 again.
30787 - Allow the middle hop of the testing circuit to be running any
30788 version, now that most of them have the bugfix to let them connect
30789 to unknown servers. This will allow reachability testing to work
30790 even when 0.0.9.7-0.0.9.9 become obsolete.
30791 - Handle relay cells with rh.length too large. This prevents
30792 a potential attack that could read arbitrary memory (maybe even
30793 keys) from the exit server's process.
30794 - We screwed up the dirport reachability testing when we don't yet
30795 have a cached version of the directory. Hopefully now fixed.
30796 - Clean up router_load_single_router() (used by the controller),
30797 so it doesn't seg fault on error.
30798 - Fix a minor memory leak when somebody establishes an introduction
30799 point at your Tor server.
30800 - If a socks connection ends because read fails, don't warn that
30801 you're not sending a socks reply back.
30804 - Add HttpProxyAuthenticator config option too, that works like
30805 the HttpsProxyAuthenticator config option.
30806 - Encode hashed controller passwords in hex instead of base64,
30807 to make it easier to write controllers.
30810 Changes in version 0.1.0.7-rc - 2005-05-17
30812 - Fix a bug in the OS X package installer that prevented it from
30813 installing on Tiger.
30814 - Fix a script bug in the OS X package installer that made it
30815 complain during installation.
30816 - Find libevent even if it's hiding in /usr/local/ and your
30817 CFLAGS and LDFLAGS don't tell you to look there.
30818 - Be able to link with libevent as a shared library (the default
30819 after 1.0d), even if it's hiding in /usr/local/lib and even
30820 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30821 assuming you're running gcc. Otherwise fail and give a useful
30823 - Fix a bug in the RPM packager: set home directory for _tor to
30824 something more reasonable when first installing.
30825 - Free a minor amount of memory that is still reachable on exit.
30828 Changes in version 0.1.0.6-rc - 2005-05-14
30830 - Implement --disable-threads configure option. Disable threads on
30831 netbsd by default, because it appears to have no reentrant resolver
30833 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30834 release (1.1) detects and disables kqueue if it's broken.
30835 - Append default exit policy before checking for implicit internal
30836 addresses. Now we don't log a bunch of complaints on startup
30837 when using the default exit policy.
30838 - Some people were putting "Address " in their torrc, and they had
30839 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30840 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30841 LOCALSTATEDIR/tor instead.
30842 - Fix fragmented-message bug in TorControl.py.
30843 - Resolve a minor bug which would prevent unreachable dirports
30844 from getting suppressed in the published descriptor.
30845 - When the controller gave us a new descriptor, we weren't resolving
30846 it immediately, so Tor would think its address was 0.0.0.0 until
30847 we fetched a new directory.
30848 - Fix an uppercase/lowercase case error in suppressing a bogus
30849 libevent warning on some Linuxes.
30852 - Begin scrubbing sensitive strings from logs by default. Turn off
30853 the config option SafeLogging if you need to do debugging.
30854 - Switch to a new buffer management algorithm, which tries to avoid
30855 reallocing and copying quite as much. In first tests it looks like
30856 it uses *more* memory on average, but less cpu.
30857 - First cut at support for "create-fast" cells. Clients can use
30858 these when extending to their first hop, since the TLS already
30859 provides forward secrecy and authentication. Not enabled on
30861 - When dirservers refuse a router descriptor, we now log its
30862 contactinfo, platform, and the poster's IP address.
30863 - Call tor_free_all instead of connections_free_all after forking, to
30864 save memory on systems that need to fork.
30865 - Whine at you if you're a server and you don't set your contactinfo.
30866 - Implement --verify-config command-line option to check if your torrc
30867 is valid without actually launching Tor.
30868 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30869 rather than just rejecting it.
30872 Changes in version 0.1.0.5-rc - 2005-04-27
30874 - Stop trying to print a null pointer if an OR conn fails because
30875 we didn't like its cert.
30877 - Switch our internal buffers implementation to use a ring buffer,
30878 to hopefully improve performance for fast servers a lot.
30879 - Add HttpsProxyAuthenticator support (basic auth only), based
30880 on patch from Adam Langley.
30881 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30882 the fast servers that have been joining lately.
30883 - Give hidden service accesses extra time on the first attempt,
30884 since 60 seconds is often only barely enough. This might improve
30886 - Improve performance for dirservers: stop re-parsing the whole
30887 directory every time you regenerate it.
30888 - Add more debugging info to help us find the weird dns freebsd
30889 pthreads bug; cleaner debug messages to help track future issues.
30892 Changes in version 0.0.9.9 - 2005-04-23
30893 o Bugfixes on 0.0.9.x:
30894 - If unofficial Tor clients connect and send weird TLS certs, our
30895 Tor server triggers an assert. This release contains a minimal
30896 backport from the broader fix that we put into 0.1.0.4-rc.
30899 Changes in version 0.1.0.4-rc - 2005-04-23
30901 - If unofficial Tor clients connect and send weird TLS certs, our
30902 Tor server triggers an assert. Stop asserting, and start handling
30903 TLS errors better in other situations too.
30904 - When the controller asks us to tell it about all the debug-level
30905 logs, it turns out we were generating debug-level logs while
30906 telling it about them, which turns into a bad loop. Now keep
30907 track of whether you're sending a debug log to the controller,
30908 and don't log when you are.
30909 - Fix the "postdescriptor" feature of the controller interface: on
30910 non-complete success, only say "done" once.
30912 - Clients are now willing to load balance over up to 2mB, not 1mB,
30913 of advertised bandwidth capacity.
30914 - Add a NoPublish config option, so you can be a server (e.g. for
30915 testing running Tor servers in other Tor networks) without
30916 publishing your descriptor to the primary dirservers.
30919 Changes in version 0.1.0.3-rc - 2005-04-08
30920 o Improvements on 0.1.0.2-rc:
30921 - Client now retries when streams end early for 'hibernating' or
30922 'resource limit' reasons, rather than failing them.
30923 - More automated handling for dirserver operators:
30924 - Automatically approve nodes running 0.1.0.2-rc or later,
30925 now that the the reachability detection stuff is working.
30926 - Now we allow two unverified servers with the same nickname
30927 but different keys. But if a nickname is verified, only that
30928 nickname+key are allowed.
30929 - If you're an authdirserver connecting to an address:port,
30930 and it's not the OR you were expecting, forget about that
30931 descriptor. If he *was* the one you were expecting, then forget
30932 about all other descriptors for that address:port.
30933 - Allow servers to publish descriptors from 12 hours in the future.
30934 Corollary: only whine about clock skew from the dirserver if
30935 he's a trusted dirserver (since now even verified servers could
30936 have quite wrong clocks).
30937 - Adjust maximum skew and age for rendezvous descriptors: let skew
30938 be 48 hours rather than 90 minutes.
30939 - Efficiency improvements:
30940 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
30941 it much faster to look up a circuit for each relay cell.
30942 - Remove most calls to assert_all_pending_dns_resolves_ok(),
30943 since they're eating our cpu on exit nodes.
30944 - Stop wasting time doing a case insensitive comparison for every
30945 dns name every time we do any lookup. Canonicalize the names to
30946 lowercase and be done with it.
30947 - Start sending 'truncated' cells back rather than destroy cells,
30948 if the circuit closes in front of you. This means we won't have
30949 to abandon partially built circuits.
30950 - Only warn once per nickname from add_nickname_list_to_smartlist
30951 per failure, so an entrynode or exitnode choice that's down won't
30953 - Put a note in the torrc about abuse potential with the default
30955 - Revise control spec and implementation to allow all log messages to
30956 be sent to controller with their severities intact (suggested by
30957 Matt Edman). Update TorControl to handle new log event types.
30958 - Provide better explanation messages when controller's POSTDESCRIPTOR
30960 - Stop putting nodename in the Platform string in server descriptors.
30961 It doesn't actually help, and it is confusing/upsetting some people.
30963 o Bugfixes on 0.1.0.2-rc:
30964 - We were printing the host mask wrong in exit policies in server
30965 descriptors. This isn't a critical bug though, since we were still
30966 obeying the exit policy internally.
30967 - Fix Tor when compiled with libevent but without pthreads: move
30968 connection_unregister() from _connection_free() to
30970 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
30971 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
30972 when we look through the connection array, we'll find any of the
30973 cpu/dnsworkers. This is no good.
30975 o Bugfixes on 0.0.9.8:
30976 - Fix possible bug on threading platforms (e.g. win32) which was
30977 leaking a file descriptor whenever a cpuworker or dnsworker died.
30978 - When using preferred entry or exit nodes, ignore whether the
30979 circuit wants uptime or capacity. They asked for the nodes, they
30981 - chdir() to your datadirectory at the *end* of the daemonize process,
30982 not the beginning. This was a problem because the first time you
30983 run tor, if your datadir isn't there, and you have runasdaemon set
30984 to 1, it will try to chdir to it before it tries to create it. Oops.
30985 - Handle changed router status correctly when dirserver reloads
30986 fingerprint file. We used to be dropping all unverified descriptors
30987 right then. The bug was hidden because we would immediately
30988 fetch a directory from another dirserver, which would include the
30989 descriptors we just dropped.
30990 - When we're connecting to an OR and he's got a different nickname/key
30991 than we were expecting, only complain loudly if we're an OP or a
30992 dirserver. Complaining loudly to the OR admins just confuses them.
30993 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
30994 artificially capped at 500kB.
30997 Changes in version 0.0.9.8 - 2005-04-07
30998 o Bugfixes on 0.0.9.x:
30999 - We have a bug that I haven't found yet. Sometimes, very rarely,
31000 cpuworkers get stuck in the 'busy' state, even though the cpuworker
31001 thinks of itself as idle. This meant that no new circuits ever got
31002 established. Here's a workaround to kill any cpuworker that's been
31003 busy for more than 100 seconds.
31006 Changes in version 0.1.0.2-rc - 2005-04-01
31007 o Bugfixes on 0.1.0.1-rc:
31008 - Fixes on reachability detection:
31009 - Don't check for reachability while hibernating.
31010 - If ORPort is reachable but DirPort isn't, still publish the
31011 descriptor, but zero out DirPort until it's found reachable.
31012 - When building testing circs for ORPort testing, use only
31013 high-bandwidth nodes, so fewer circuits fail.
31014 - Complain about unreachable ORPort separately from unreachable
31015 DirPort, so the user knows what's going on.
31016 - Make sure we only conclude ORPort reachability if we didn't
31017 initiate the conn. Otherwise we could falsely conclude that
31018 we're reachable just because we connected to the guy earlier
31019 and he used that same pipe to extend to us.
31020 - Authdirservers shouldn't do ORPort reachability detection,
31021 since they're in clique mode, so it will be rare to find a
31022 server not already connected to them.
31023 - When building testing circuits, always pick middle hops running
31024 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
31025 bug. (This is a kludge; it will go away when 0.0.9.x becomes
31027 - When we decide we're reachable, actually publish our descriptor
31029 - Fix bug in redirectstream in the controller.
31030 - Fix the state descriptor strings so logs don't claim edge streams
31031 are in a different state than they actually are.
31032 - Use recent libevent features when possible (this only really affects
31033 win32 and osx right now, because the new libevent with these
31034 features hasn't been released yet). Add code to suppress spurious
31036 - Prevent possible segfault in connection_close_unattached_ap().
31037 - Fix newlines on torrc in win32.
31038 - Improve error msgs when tor-resolve fails.
31040 o Improvements on 0.0.9.x:
31041 - New experimental script tor/contrib/ExerciseServer.py (needs more
31042 work) that uses the controller interface to build circuits and
31043 fetch pages over them. This will help us bootstrap servers that
31044 have lots of capacity but haven't noticed it yet.
31045 - New experimental script tor/contrib/PathDemo.py (needs more work)
31046 that uses the controller interface to let you choose whole paths
31048 "<hostname>.<path,separated by dots>.<length of path>.path"
31049 - When we've connected to an OR and handshaked but didn't like
31050 the result, we were closing the conn without sending destroy
31051 cells back for pending circuits. Now send those destroys.
31054 Changes in version 0.0.9.7 - 2005-04-01
31055 o Bugfixes on 0.0.9.x:
31056 - Fix another race crash bug (thanks to Glenn Fink for reporting).
31057 - Compare identity to identity, not to nickname, when extending to
31058 a router not already in the directory. This was preventing us from
31059 extending to unknown routers. Oops.
31060 - Make sure to create OS X Tor user in <500 range, so we aren't
31061 creating actual system users.
31062 - Note where connection-that-hasn't-sent-end was marked, and fix
31063 a few really loud instances of this harmless bug (it's fixed more
31067 Changes in version 0.1.0.1-rc - 2005-03-28
31069 - Add reachability testing. Your Tor server will automatically try
31070 to see if its ORPort and DirPort are reachable from the outside,
31071 and it won't upload its descriptor until it decides they are.
31072 - Handle unavailable hidden services better. Handle slow or busy
31073 hidden services better.
31074 - Add support for CONNECTing through https proxies, with "HttpsProxy"
31076 - New exit policy: accept most low-numbered ports, rather than
31077 rejecting most low-numbered ports.
31078 - More Tor controller support (still experimental). See
31079 http://tor.eff.org/doc/control-spec.txt for all the new features,
31080 including signals to emulate unix signals from any platform;
31081 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
31082 closestream; closecircuit; etc.
31083 - Make nt services work and start on startup on win32 (based on
31084 patch by Matt Edman).
31085 - Add a new AddressMap config directive to rewrite incoming socks
31086 addresses. This lets you, for example, declare an implicit
31087 required exit node for certain sites.
31088 - Add a new TrackHostExits config directive to trigger addressmaps
31089 for certain incoming socks addresses -- for sites that break when
31090 your exit keeps changing (based on patch by Mike Perry).
31091 - Redo the client-side dns cache so it's just an addressmap too.
31092 - Notice when our IP changes, and reset stats/uptime/reachability.
31093 - When an application is using socks5, give him the whole variety of
31094 potential socks5 responses (connect refused, host unreachable, etc),
31095 rather than just "success" or "failure".
31096 - A more sane version numbering system. See
31097 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
31098 - New contributed script "exitlist": a simple python script to
31099 parse directories and find Tor nodes that exit to listed
31101 - New contributed script "privoxy-tor-toggle" to toggle whether
31102 Privoxy uses Tor. Seems to be configured for Debian by default.
31103 - Report HTTP reasons to client when getting a response from directory
31104 servers -- so you can actually know what went wrong.
31105 - New config option MaxAdvertisedBandwidth which lets you advertise
31106 a low bandwidthrate (to not attract as many circuits) while still
31107 allowing a higher bandwidthrate in reality.
31109 o Robustness/stability fixes:
31110 - Make Tor use Niels Provos's libevent instead of its current
31111 poll-but-sometimes-select mess. This will let us use faster async
31112 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
31114 - pthread support now too. This was forced because when we forked,
31115 we ended up wasting a lot of duplicate ram over time. Also switch
31116 to foo_r versions of some library calls to allow reentry and
31118 - Better handling for heterogeneous / unreliable nodes:
31119 - Annotate circuits w/ whether they aim to contain high uptime nodes
31120 and/or high capacity nodes. When building circuits, choose
31122 - This means that every single node in an intro rend circuit,
31123 not just the last one, will have a minimum uptime.
31124 - New config option LongLivedPorts to indicate application streams
31125 that will want high uptime circuits.
31126 - Servers reset uptime when a dir fetch entirely fails. This
31127 hopefully reflects stability of the server's network connectivity.
31128 - If somebody starts his tor server in Jan 2004 and then fixes his
31129 clock, don't make his published uptime be a year.
31130 - Reset published uptime when you wake up from hibernation.
31131 - Introduce a notion of 'internal' circs, which are chosen without
31132 regard to the exit policy of the last hop. Intro and rendezvous
31133 circs must be internal circs, to avoid leaking information. Resolve
31134 and connect streams can use internal circs if they want.
31135 - New circuit pooling algorithm: make sure to have enough circs around
31136 to satisfy any predicted ports, and also make sure to have 2 internal
31137 circs around if we've required internal circs lately (and with high
31138 uptime if we've seen that lately too).
31139 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
31140 which describes how often we retry making new circuits if current
31141 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
31142 how long we're willing to make use of an already-dirty circuit.
31143 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
31144 circ as necessary, if there are any completed ones lying around
31145 when we try to launch one.
31146 - Make hidden services try to establish a rendezvous for 30 seconds,
31147 rather than for n (where n=3) attempts to build a circuit.
31148 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
31149 "ShutdownWaitLength".
31150 - Try to be more zealous about calling connection_edge_end when
31151 things go bad with edge conns in connection.c.
31152 - Revise tor-spec to add more/better stream end reasons.
31153 - Revise all calls to connection_edge_end to avoid sending "misc",
31154 and to take errno into account where possible.
31157 - Fix a race condition that can trigger an assert, when we have a
31158 pending create cell and an OR connection fails right then.
31159 - Fix several double-mark-for-close bugs, e.g. where we were finding
31160 a conn for a cell even if that conn is already marked for close.
31161 - Make sequence of log messages when starting on win32 with no config
31162 file more reasonable.
31163 - When choosing an exit node for a new non-internal circ, don't take
31164 into account whether it'll be useful for any pending x.onion
31165 addresses -- it won't.
31166 - Turn addr_policy_compare from a tristate to a quadstate; this should
31167 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
31168 for google.com" problem.
31169 - Make "platform" string in descriptor more accurate for Win32 servers,
31170 so it's not just "unknown platform".
31171 - Fix an edge case in parsing config options (thanks weasel).
31172 If they say "--" on the commandline, it's not an option.
31173 - Reject odd-looking addresses at the client (e.g. addresses that
31174 contain a colon), rather than having the server drop them because
31176 - tor-resolve requests were ignoring .exit if there was a working circuit
31177 they could use instead.
31178 - REUSEADDR on normal platforms means you can rebind to the port
31179 right after somebody else has let it go. But REUSEADDR on win32
31180 means to let you bind to the port _even when somebody else
31181 already has it bound_! So, don't do that on Win32.
31182 - Change version parsing logic: a version is "obsolete" if it is not
31183 recommended and (1) there is a newer recommended version in the
31184 same series, or (2) there are no recommended versions in the same
31185 series, but there are some recommended versions in a newer series.
31186 A version is "new" if it is newer than any recommended version in
31188 - Stop most cases of hanging up on a socks connection without sending
31192 - Require BandwidthRate to be at least 20kB/s for servers.
31193 - When a dirserver causes you to give a warn, mention which dirserver
31195 - New config option DirAllowPrivateAddresses for authdirservers.
31196 Now by default they refuse router descriptors that have non-IP or
31197 private-IP addresses.
31198 - Stop publishing socksport in the directory, since it's not
31199 actually meant to be public. For compatibility, publish a 0 there
31201 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
31202 smart" value, that is low for servers and high for clients.
31203 - If our clock jumps forward by 100 seconds or more, assume something
31204 has gone wrong with our network and abandon all not-yet-used circs.
31205 - Warn when exit policy implicitly allows local addresses.
31206 - If we get an incredibly skewed timestamp from a dirserver mirror
31207 that isn't a verified OR, don't warn -- it's probably him that's
31209 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
31210 cookies to disk and doesn't log each web request to disk. (Thanks
31211 to Brett Carrington for pointing this out.)
31212 - When a client asks us for a dir mirror and we don't have one,
31213 launch an attempt to get a fresh one.
31214 - If we're hibernating and we get a SIGINT, exit immediately.
31215 - Add --with-dmalloc ./configure option, to track memory leaks.
31216 - And try to free all memory on closing, so we can detect what
31218 - Cache local dns resolves correctly even when they're .exit
31220 - Give a better warning when some other server advertises an
31221 ORPort that is actually an apache running ssl.
31222 - Add "opt hibernating 1" to server descriptor to make it clearer
31223 whether the server is hibernating.
31226 Changes in version 0.0.9.6 - 2005-03-24
31227 o Bugfixes on 0.0.9.x (crashes and asserts):
31228 - Add new end stream reasons to maintenance branch. Fix bug where
31229 reason (8) could trigger an assert. Prevent bug from recurring.
31230 - Apparently win32 stat wants paths to not end with a slash.
31231 - Fix assert triggers in assert_cpath_layer_ok(), where we were
31232 blowing away the circuit that conn->cpath_layer points to, then
31233 checking to see if the circ is well-formed. Backport check to make
31234 sure we dont use the cpath on a closed connection.
31235 - Prevent circuit_resume_edge_reading_helper() from trying to package
31236 inbufs for marked-for-close streams.
31237 - Don't crash on hup if your options->address has become unresolvable.
31238 - Some systems (like OS X) sometimes accept() a connection and tell
31239 you the remote host is 0.0.0.0:0. If this happens, due to some
31240 other mis-features, we get confused; so refuse the conn for now.
31242 o Bugfixes on 0.0.9.x (other):
31243 - Fix harmless but scary "Unrecognized content encoding" warn message.
31244 - Add new stream error reason: TORPROTOCOL reason means "you are not
31245 speaking a version of Tor I understand; say bye-bye to your stream."
31246 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
31247 into the future, now that we are more tolerant of skew. This
31248 resolves a bug where a Tor server would refuse to cache a directory
31249 because all the directories it gets are too far in the future;
31250 yet the Tor server never logs any complaints about clock skew.
31251 - Mac packaging magic: make man pages useable, and do not overwrite
31252 existing torrc files.
31253 - Make OS X log happily to /var/log/tor/tor.log
31256 Changes in version 0.0.9.5 - 2005-02-22
31257 o Bugfixes on 0.0.9.x:
31258 - Fix an assert race at exit nodes when resolve requests fail.
31259 - Stop picking unverified dir mirrors--it only leads to misery.
31260 - Patch from Matt Edman to make NT services work better. Service
31261 support is still not compiled into the executable by default.
31262 - Patch from Dmitri Bely so the Tor service runs better under
31263 the win32 SYSTEM account.
31264 - Make tor-resolve actually work (?) on Win32.
31265 - Fix a sign bug when getrlimit claims to have 4+ billion
31266 file descriptors available.
31267 - Stop refusing to start when bandwidthburst == bandwidthrate.
31268 - When create cells have been on the onion queue more than five
31269 seconds, just send back a destroy and take them off the list.
31272 Changes in version 0.0.9.4 - 2005-02-03
31273 o Bugfixes on 0.0.9:
31274 - Fix an assert bug that took down most of our servers: when
31275 a server claims to have 1 GB of bandwidthburst, don't
31277 - Don't crash as badly if we have spawned the max allowed number
31278 of dnsworkers, or we're out of file descriptors.
31279 - Block more file-sharing ports in the default exit policy.
31280 - MaxConn is now automatically set to the hard limit of max
31281 file descriptors we're allowed (ulimit -n), minus a few for
31283 - Give a clearer message when servers need to raise their
31284 ulimit -n when they start running out of file descriptors.
31285 - SGI Compatibility patches from Jan Schaumann.
31286 - Tolerate a corrupt cached directory better.
31287 - When a dirserver hasn't approved your server, list which one.
31288 - Go into soft hibernation after 95% of the bandwidth is used,
31289 not 99%. This is especially important for daily hibernators who
31290 have a small accounting max. Hopefully it will result in fewer
31291 cut connections when the hard hibernation starts.
31292 - Load-balance better when using servers that claim more than
31293 800kB/s of capacity.
31294 - Make NT services work (experimental, only used if compiled in).
31297 Changes in version 0.0.9.3 - 2005-01-21
31298 o Bugfixes on 0.0.9:
31299 - Backport the cpu use fixes from main branch, so busy servers won't
31300 need as much processor time.
31301 - Work better when we go offline and then come back, or when we
31302 run Tor at boot before the network is up. We do this by
31303 optimistically trying to fetch a new directory whenever an
31304 application request comes in and we think we're offline -- the
31305 human is hopefully a good measure of when the network is back.
31306 - Backport some minimal hidserv bugfixes: keep rend circuits open as
31307 long as you keep using them; actually publish hidserv descriptors
31308 shortly after they change, rather than waiting 20-40 minutes.
31309 - Enable Mac startup script by default.
31310 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
31311 - When you update AllowUnverifiedNodes or FirewallPorts via the
31312 controller's setconf feature, we were always appending, never
31314 - When you update HiddenServiceDir via setconf, it was screwing up
31315 the order of reading the lines, making it fail.
31316 - Do not rewrite a cached directory back to the cache; otherwise we
31317 will think it is recent and not fetch a newer one on startup.
31318 - Workaround for webservers that lie about Content-Encoding: Tor
31319 now tries to autodetect compressed directories and compression
31320 itself. This lets us Proxypass dir fetches through apache.
31323 Changes in version 0.0.9.2 - 2005-01-04
31324 o Bugfixes on 0.0.9 (crashes and asserts):
31325 - Fix an assert on startup when the disk is full and you're logging
31327 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
31328 style address, then we'd crash.
31329 - Fix an assert trigger when the running-routers string we get from
31330 a dirserver is broken.
31331 - Make worker threads start and run on win32. Now win32 servers
31333 - Bandaid (not actually fix, but now it doesn't crash) an assert
31334 where the dns worker dies mysteriously and the main Tor process
31335 doesn't remember anything about the address it was resolving.
31337 o Bugfixes on 0.0.9 (Win32):
31338 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
31339 name out of the warning/assert messages.
31340 - Fix a superficial "unhandled error on read" bug on win32.
31341 - The win32 installer no longer requires a click-through for our
31342 license, since our Free Software license grants rights but does not
31344 - Win32: When connecting to a dirserver fails, try another one
31345 immediately. (This was already working for non-win32 Tors.)
31346 - Stop trying to parse $HOME on win32 when hunting for default
31348 - Make tor-resolve.c work on win32 by calling network_init().
31350 o Bugfixes on 0.0.9 (other):
31351 - Make 0.0.9.x build on Solaris again.
31352 - Due to a fencepost error, we were blowing away the \n when reporting
31353 confvalue items in the controller. So asking for multiple config
31354 values at once couldn't work.
31355 - When listing circuits that are pending on an opening OR connection,
31356 if we're an OR we were listing circuits that *end* at us as
31357 being pending on every listener, dns/cpu worker, etc. Stop that.
31358 - Dirservers were failing to create 'running-routers' or 'directory'
31359 strings if we had more than some threshold of routers. Fix them so
31360 they can handle any number of routers.
31361 - Fix a superficial "Duplicate mark for close" bug.
31362 - Stop checking for clock skew for OR connections, even for servers.
31363 - Fix a fencepost error that was chopping off the last letter of any
31364 nickname that is the maximum allowed nickname length.
31365 - Update URLs in log messages so they point to the new website.
31366 - Fix a potential problem in mangling server private keys while
31367 writing to disk (not triggered yet, as far as we know).
31368 - Include the licenses for other free software we include in Tor,
31369 now that we're shipping binary distributions more regularly.
31372 Changes in version 0.0.9.1 - 2004-12-15
31373 o Bugfixes on 0.0.9:
31374 - Make hibernation actually work.
31375 - Make HashedControlPassword config option work.
31376 - When we're reporting event circuit status to a controller,
31377 don't use the stream status code.
31380 Changes in version 0.0.9 - 2004-12-12
31382 - Clean up manpage and torrc.sample file.
31383 - Clean up severities and text of log warnings.
31385 - Make servers trigger an assert when they enter hibernation.
31388 Changes in version 0.0.9rc7 - 2004-12-08
31389 o Bugfixes on 0.0.9rc:
31390 - Fix a stack-trashing crash when an exit node begins hibernating.
31391 - Avoid looking at unallocated memory while considering which
31392 ports we need to build circuits to cover.
31393 - Stop a sigpipe: when an 'end' cell races with eof from the app,
31394 we shouldn't hold-open-until-flush if the eof arrived first.
31395 - Fix a bug with init_cookie_authentication() in the controller.
31396 - When recommending new-format log lines, if the upper bound is
31397 LOG_ERR, leave it implicit.
31399 o Bugfixes on 0.0.8.1:
31400 - Fix a whole slew of memory leaks.
31401 - Fix isspace() and friends so they still make Solaris happy
31402 but also so they don't trigger asserts on win32.
31403 - Fix parse_iso_time on platforms without strptime (eg win32).
31404 - win32: tolerate extra "readable" events better.
31405 - win32: when being multithreaded, leave parent fdarray open.
31406 - Make unit tests work on win32.
31409 Changes in version 0.0.9rc6 - 2004-12-06
31410 o Bugfixes on 0.0.9pre:
31411 - Clean up some more integer underflow opportunities (not exploitable
31413 - While hibernating, hup should not regrow our listeners.
31414 - Send an end to the streams we close when we hibernate, rather
31415 than just chopping them off.
31416 - React to eof immediately on non-open edge connections.
31418 o Bugfixes on 0.0.8.1:
31419 - Calculate timeout for waiting for a connected cell from the time
31420 we sent the begin cell, not from the time the stream started. If
31421 it took a long time to establish the circuit, we would time out
31422 right after sending the begin cell.
31423 - Fix router_compare_addr_to_addr_policy: it was not treating a port
31424 of * as always matching, so we were picking reject *:* nodes as
31425 exit nodes too. Oops.
31428 - New circuit building strategy: keep a list of ports that we've
31429 used in the past 6 hours, and always try to have 2 circuits open
31430 or on the way that will handle each such port. Seed us with port
31431 80 so web users won't complain that Tor is "slow to start up".
31432 - Make kill -USR1 dump more useful stats about circuits.
31433 - When warning about retrying or giving up, print the address, so
31434 the user knows which one it's talking about.
31435 - If you haven't used a clean circuit in an hour, throw it away,
31436 just to be on the safe side. (This means after 6 hours a totally
31437 unused Tor client will have no circuits open.)
31440 Changes in version 0.0.9rc5 - 2004-12-01
31441 o Bugfixes on 0.0.8.1:
31442 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
31443 - Let resolve conns retry/expire also, rather than sticking around
31445 - If we are using select, make sure we stay within FD_SETSIZE.
31447 o Bugfixes on 0.0.9pre:
31448 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
31449 but doesn't seem to be currently; thanks to Ilja van Sprundel for
31451 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
31452 instead. Impose minima and maxima for all *Period options; impose
31453 even tighter maxima for fetching if we are a caching dirserver.
31454 Clip rather than rejecting.
31455 - Fetch cached running-routers from servers that serve it (that is,
31456 authdirservers and servers running 0.0.9rc5-cvs or later.)
31459 - Accept *:706 (silc) in default exit policy.
31460 - Implement new versioning format for post 0.1.
31461 - Support "foo.nickname.exit" addresses, to let Alice request the
31462 address "foo" as viewed by exit node "nickname". Based on a patch
31464 - Make tor --version --version dump the cvs Id of every file.
31467 Changes in version 0.0.9rc4 - 2004-11-28
31468 o Bugfixes on 0.0.8.1:
31469 - Make windows sockets actually non-blocking (oops), and handle
31470 win32 socket errors better.
31472 o Bugfixes on 0.0.9rc1:
31473 - Actually catch the -USR2 signal.
31476 Changes in version 0.0.9rc3 - 2004-11-25
31477 o Bugfixes on 0.0.8.1:
31478 - Flush the log file descriptor after we print "Tor opening log file",
31479 so we don't see those messages days later.
31481 o Bugfixes on 0.0.9rc1:
31482 - Make tor-resolve work again.
31483 - Avoid infinite loop in tor-resolve if tor hangs up on it.
31484 - Fix an assert trigger for clients/servers handling resolves.
31487 Changes in version 0.0.9rc2 - 2004-11-24
31488 o Bugfixes on 0.0.9rc1:
31489 - I broke socks5 support while fixing the eof bug.
31490 - Allow unitless bandwidths and intervals; they default to bytes
31492 - New servers don't start out hibernating; they are active until
31493 they run out of bytes, so they have a better estimate of how
31494 long it takes, and so their operators can know they're working.
31497 Changes in version 0.0.9rc1 - 2004-11-23
31498 o Bugfixes on 0.0.8.1:
31499 - Finally fix a bug that's been plaguing us for a year:
31500 With high load, circuit package window was reaching 0. Whenever
31501 we got a circuit-level sendme, we were reading a lot on each
31502 socket, but only writing out a bit. So we would eventually reach
31503 eof. This would be noticed and acted on even when there were still
31504 bytes sitting in the inbuf.
31505 - When poll() is interrupted, we shouldn't believe the revents values.
31507 o Bugfixes on 0.0.9pre6:
31508 - Fix hibernate bug that caused pre6 to be broken.
31509 - Don't keep rephist info for routers that haven't had activity for
31510 24 hours. (This matters now that clients have keys, since we track
31512 - Never call close_temp_logs while validating log options.
31513 - Fix backslash-escaping on tor.sh.in and torctl.in.
31516 - Implement weekly/monthly/daily accounting: now you specify your
31517 hibernation properties by
31518 AccountingMax N bytes|KB|MB|GB|TB
31519 AccountingStart day|week|month [day] HH:MM
31520 Defaults to "month 1 0:00".
31521 - Let bandwidth and interval config options be specified as 5 bytes,
31522 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
31523 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
31524 get back to normal.)
31525 - If your requested entry or exit node has advertised bandwidth 0,
31527 - Be more greedy about filling up relay cells -- we try reading again
31528 once we've processed the stuff we read, in case enough has arrived
31529 to fill the last cell completely.
31530 - Apply NT service patch from Osamu Fujino. Still needs more work.
31533 Changes in version 0.0.9pre6 - 2004-11-15
31534 o Bugfixes on 0.0.8.1:
31535 - Fix assert failure on malformed socks4a requests.
31536 - Use identity comparison, not nickname comparison, to choose which
31537 half of circuit-ID-space each side gets to use. This is needed
31538 because sometimes we think of a router as a nickname, and sometimes
31539 as a hex ID, and we can't predict what the other side will do.
31540 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
31541 write() call will fail and we handle it there.
31542 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
31543 and smartlist_len, which are two major profiling offenders.
31545 o Bugfixes on 0.0.9pre5:
31546 - Fix a bug in read_all that was corrupting config files on windows.
31547 - When we're raising the max number of open file descriptors to
31548 'unlimited', don't log that we just raised it to '-1'.
31549 - Include event code with events, as required by control-spec.txt.
31550 - Don't give a fingerprint when clients do --list-fingerprint:
31551 it's misleading, because it will never be the same again.
31552 - Stop using strlcpy in tor_strndup, since it was slowing us
31554 - Remove warn on startup about missing cached-directory file.
31555 - Make kill -USR1 work again.
31556 - Hibernate if we start tor during the "wait for wakeup-time" phase
31557 of an accounting interval. Log our hibernation plans better.
31558 - Authoritative dirservers now also cache their directory, so they
31559 have it on start-up.
31562 - Fetch running-routers; cache running-routers; compress
31563 running-routers; serve compressed running-routers.z
31564 - Add NSI installer script contributed by J Doe.
31565 - Commit VC6 and VC7 workspace/project files.
31566 - Commit a tor.spec for making RPM files, with help from jbash.
31567 - Add contrib/torctl.in contributed by Glenn Fink.
31568 - Implement the control-spec's SAVECONF command, to write your
31569 configuration to torrc.
31570 - Get cookie authentication for the controller closer to working.
31571 - Include control-spec.txt in the tarball.
31572 - When set_conf changes our server descriptor, upload a new copy.
31573 But don't upload it too often if there are frequent changes.
31574 - Document authentication config in man page, and document signals
31576 - Clean up confusing parts of man page and torrc.sample.
31577 - Make expand_filename handle ~ and ~username.
31578 - Use autoconf to enable largefile support where necessary. Use
31579 ftello where available, since ftell can fail at 2GB.
31580 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
31581 log more informatively.
31582 - Give a slightly more useful output for "tor -h".
31583 - Refuse application socks connections to port 0.
31584 - Check clock skew for verified servers, but allow unverified
31585 servers and clients to have any clock skew.
31586 - Break DirFetchPostPeriod into:
31587 - DirFetchPeriod for fetching full directory,
31588 - StatusFetchPeriod for fetching running-routers,
31589 - DirPostPeriod for posting server descriptor,
31590 - RendPostPeriod for posting hidden service descriptors.
31591 - Make sure the hidden service descriptors are at a random offset
31592 from each other, to hinder linkability.
31595 Changes in version 0.0.9pre5 - 2004-11-09
31596 o Bugfixes on 0.0.9pre4:
31597 - Fix a seg fault in unit tests (doesn't affect main program).
31598 - Fix an assert bug where a hidden service provider would fail if
31599 the first hop of his rendezvous circuit was down.
31600 - Hidden service operators now correctly handle version 1 style
31601 INTRODUCE1 cells (nobody generates them still, so not a critical
31603 - If do_hup fails, actually notice.
31604 - Handle more errnos from accept() without closing the listener.
31605 Some OpenBSD machines were closing their listeners because
31606 they ran out of file descriptors.
31607 - Send resolve cells to exit routers that are running a new
31608 enough version of the resolve code to work right.
31609 - Better handling of winsock includes on non-MSV win32 compilers.
31610 - Some people had wrapped their tor client/server in a script
31611 that would restart it whenever it died. This did not play well
31612 with our "shut down if your version is obsolete" code. Now people
31613 don't fetch a new directory if their local cached version is
31615 - Make our autogen.sh work on ksh as well as bash.
31618 - Hibernation: New config option "AccountingMaxKB" lets you
31619 set how many KBytes per month you want to allow your server to
31620 consume. Rather than spreading those bytes out evenly over the
31621 month, we instead hibernate for some of the month and pop up
31622 at a deterministic time, work until the bytes are consumed, then
31623 hibernate again. Config option "MonthlyAccountingStart" lets you
31624 specify which day of the month your billing cycle starts on.
31625 - Control interface: a separate program can now talk to your
31626 client/server over a socket, and get/set config options, receive
31627 notifications of circuits and streams starting/finishing/dying,
31628 bandwidth used, etc. The next step is to get some GUIs working.
31629 Let us know if you want to help out. See doc/control-spec.txt .
31630 - Ship a contrib/tor-control.py as an example script to interact
31631 with the control port.
31632 - "tor --hash-password zzyxz" will output a salted password for
31633 use in authenticating to the control interface.
31634 - New log format in config:
31635 "Log minsev[-maxsev] stdout|stderr|syslog" or
31636 "Log minsev[-maxsev] file /var/foo"
31639 - DirPolicy config option, to let people reject incoming addresses
31640 from their dirserver.
31641 - "tor --list-fingerprint" will list your identity key fingerprint
31643 - Add "pass" target for RedirectExit, to make it easier to break
31644 out of a sequence of RedirectExit rules.
31645 - Clients now generate a TLS cert too, in preparation for having
31646 them act more like real nodes.
31647 - Ship src/win32/ in the tarball, so people can use it to build.
31648 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
31650 - New "router-status" line in directory, to better bind each verified
31651 nickname to its identity key.
31652 - Deprecate unofficial config option abbreviations, and abbreviations
31653 not on the command line.
31654 - Add a pure-C tor-resolve implementation.
31655 - Use getrlimit and friends to ensure we can reach MaxConn (currently
31656 1024) file descriptors.
31658 o Code security improvements, inspired by Ilja:
31659 - Replace sprintf with snprintf. (I think they were all safe, but
31661 - Replace strcpy/strncpy with strlcpy in more places.
31662 - Avoid strcat; use snprintf or strlcat instead.
31663 - snprintf wrapper with consistent (though not C99) overflow behavior.
31666 Changes in version 0.0.9pre4 - 2004-10-17
31667 o Bugfixes on 0.0.9pre3:
31668 - If the server doesn't specify an exit policy, use the real default
31669 exit policy, not reject *:*.
31670 - Ignore fascistfirewall when uploading/downloading hidden service
31671 descriptors, since we go through Tor for those; and when using
31672 an HttpProxy, since we assume it can reach them all.
31673 - When looking for an authoritative dirserver, use only the ones
31674 configured at boot. Don't bother looking in the directory.
31675 - The rest of the fix for get_default_conf_file() on older win32.
31676 - Make 'Routerfile' config option obsolete.
31679 - New 'MyFamily nick1,...' config option for a server to
31680 specify other servers that shouldn't be used in the same circuit
31681 with it. Only believed if nick1 also specifies us.
31682 - New 'NodeFamily nick1,nick2,...' config option for a client to
31683 specify nodes that it doesn't want to use in the same circuit.
31684 - New 'Redirectexit pattern address:port' config option for a
31685 server to redirect exit connections, e.g. to a local squid.
31688 Changes in version 0.0.9pre3 - 2004-10-13
31689 o Bugfixes on 0.0.8.1:
31690 - Better torrc example lines for dirbindaddress and orbindaddress.
31691 - Improved bounds checking on parsed ints (e.g. config options and
31692 the ones we find in directories.)
31693 - Better handling of size_t vs int, so we're more robust on 64
31695 - Fix the rest of the bug where a newly started OR would appear
31696 as unverified even after we've added his fingerprint and hupped
31698 - Fix a bug from 0.0.7: when read() failed on a stream, we would
31699 close it without sending back an end. So 'connection refused'
31700 would simply be ignored and the user would get no response.
31702 o Bugfixes on 0.0.9pre2:
31703 - Serving the cached-on-disk directory to people is bad. We now
31704 provide no directory until we've fetched a fresh one.
31705 - Workaround for bug on windows where cached-directories get crlf
31707 - Make get_default_conf_file() work on older windows too.
31708 - If we write a *:* exit policy line in the descriptor, don't write
31709 any more exit policy lines.
31712 - Use only 0.0.9pre1 and later servers for resolve cells.
31713 - Make the dirservers file obsolete.
31714 - Include a dir-signing-key token in directories to tell the
31715 parsing entity which key is being used to sign.
31716 - Remove the built-in bulky default dirservers string.
31717 - New config option "Dirserver %s:%d [fingerprint]", which can be
31718 repeated as many times as needed. If no dirservers specified,
31719 default to moria1,moria2,tor26.
31720 - Make moria2 advertise a dirport of 80, so people behind firewalls
31721 will be able to get a directory.
31722 - Http proxy support
31723 - Dirservers translate requests for http://%s:%d/x to /x
31724 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31725 be routed through this host.
31726 - Clients ask for /tor/x rather than /x for new enough dirservers.
31727 This way we can one day coexist peacefully with apache.
31728 - Clients specify a "Host: %s%d" http header, to be compatible
31729 with more proxies, and so running squid on an exit node can work.
31732 Changes in version 0.0.8.1 - 2004-10-13
31734 - Fix a seg fault that can be triggered remotely for Tor
31735 clients/servers with an open dirport.
31736 - Fix a rare assert trigger, where routerinfos for entries in
31737 our cpath would expire while we're building the path.
31738 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31739 - Fix a rare seg fault for people running hidden services on
31740 intermittent connections.
31741 - Fix a bug in parsing opt keywords with objects.
31742 - Fix a stale pointer assert bug when a stream detaches and
31744 - Fix a string format vulnerability (probably not exploitable)
31745 in reporting stats locally.
31746 - Fix an assert trigger: sometimes launching circuits can fail
31747 immediately, e.g. because too many circuits have failed recently.
31748 - Fix a compile warning on 64 bit platforms.
31751 Changes in version 0.0.9pre2 - 2004-10-03
31753 - Make fetching a cached directory work for 64-bit platforms too.
31754 - Make zlib.h a required header, not an optional header.
31757 Changes in version 0.0.9pre1 - 2004-10-01
31759 - Stop using separate defaults for no-config-file and
31760 empty-config-file. Now you have to explicitly turn off SocksPort,
31761 if you don't want it open.
31762 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31763 - Improve man page to mention more of the 0.0.8 features.
31764 - Fix a rare seg fault for people running hidden services on
31765 intermittent connections.
31766 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31768 - Fix more dns related bugs: send back resolve_failed and end cells
31769 more reliably when the resolve fails, rather than closing the
31770 circuit and then trying to send the cell. Also attach dummy resolve
31771 connections to a circuit *before* calling dns_resolve(), to fix
31772 a bug where cached answers would never be sent in RESOLVED cells.
31773 - When we run out of disk space, or other log writing error, don't
31774 crash. Just stop logging to that log and continue.
31775 - We were starting to daemonize before we opened our logs, so if
31776 there were any problems opening logs, we would complain to stderr,
31777 which wouldn't work, and then mysteriously exit.
31778 - Fix a rare bug where sometimes a verified OR would connect to us
31779 before he'd uploaded his descriptor, which would cause us to
31780 assign conn->nickname as though he's unverified. Now we look through
31781 the fingerprint list to see if he's there.
31782 - Fix a rare assert trigger, where routerinfos for entries in
31783 our cpath would expire while we're building the path.
31786 - Clients can ask dirservers for /dir.z to get a compressed version
31787 of the directory. Only works for servers running 0.0.9, of course.
31788 - Make clients cache directories and use them to seed their router
31789 lists at startup. This means clients have a datadir again.
31790 - Configuration infrastructure support for warning on obsolete
31792 - Respond to content-encoding headers by trying to uncompress as
31794 - Reply with a deflated directory when a client asks for "dir.z".
31795 We could use allow-encodings instead, but allow-encodings isn't
31796 specified in HTTP 1.0.
31797 - Raise the max dns workers from 50 to 100.
31798 - Discourage people from setting their dirfetchpostperiod more often
31799 than once per minute.
31800 - Protect dirservers from overzealous descriptor uploading -- wait
31801 10 seconds after directory gets dirty, before regenerating.
31804 Changes in version 0.0.8 - 2004-08-25
31805 o Port it to SunOS 5.9 / Athena
31808 Changes in version 0.0.8rc2 - 2004-08-20
31809 o Make it compile on cygwin again.
31810 o When picking unverified routers, skip those with low uptime and/or
31811 low bandwidth, depending on what properties you care about.
31814 Changes in version 0.0.8rc1 - 2004-08-18
31815 o Changes from 0.0.7.3:
31817 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31818 don't put it into the client dns cache.
31819 - If a begin failed due to exit policy, but we believe the IP address
31820 should have been allowed, switch that router to exitpolicy reject *:*
31821 until we get our next directory.
31823 - Clients choose nodes proportional to advertised bandwidth.
31824 - Avoid using nodes with low uptime as introduction points.
31825 - Handle servers with dynamic IP addresses: don't replace
31826 options->Address with the resolved one at startup, and
31827 detect our address right before we make a routerinfo each time.
31828 - 'FascistFirewall' option to pick dirservers and ORs on specific
31829 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31830 which ports are open. (Defaults to 80,443)
31831 - Be more aggressive about trying to make circuits when the network
31832 has changed (e.g. when you unsuspend your laptop).
31833 - Check for time skew on http headers; report date in response to
31835 - If the entrynode config line has only one node, don't pick it as
31837 - Add strict{entry|exit}nodes config options. If set to 1, then
31838 we refuse to build circuits that don't include the specified entry
31840 - OutboundBindAddress config option, to bind to a specific
31841 IP address for outgoing connect()s.
31842 - End truncated log entries (e.g. directories) with "[truncated]".
31844 o Patches to 0.0.8preX:
31846 - Patches to compile and run on win32 again (maybe)?
31847 - Fix crash when looking for ~/.torrc with no $HOME set.
31848 - Fix a race bug in the unit tests.
31849 - Handle verified/unverified name collisions better when new
31850 routerinfo's arrive in a directory.
31851 - Sometimes routers were getting entered into the stats before
31852 we'd assigned their identity_digest. Oops.
31853 - Only pick and establish intro points after we've gotten a
31856 - AllowUnverifiedNodes config option to let circuits choose no-name
31857 routers in entry,middle,exit,introduction,rendezvous positions.
31858 Allow middle and rendezvous positions by default.
31859 - Add a man page for tor-resolve.
31862 Changes in version 0.0.7.3 - 2004-08-12
31863 o Stop dnsworkers from triggering an assert failure when you
31864 ask them to resolve the host "".
31867 Changes in version 0.0.8pre3 - 2004-08-09
31868 o Changes from 0.0.7.2:
31869 - Allow multiple ORs with same nickname in routerlist -- now when
31870 people give us one identity key for a nickname, then later
31871 another, we don't constantly complain until the first expires.
31872 - Remember used bandwidth (both in and out), and publish 15-minute
31873 snapshots for the past day into our descriptor.
31874 - You can now fetch $DIRURL/running-routers to get just the
31875 running-routers line, not the whole descriptor list. (But
31876 clients don't use this yet.)
31877 - When people mistakenly use Tor as an http proxy, point them
31878 at the tor-doc.html rather than the INSTALL.
31879 - Remove our mostly unused -- and broken -- hex_encode()
31880 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31881 for pointing out this bug.)
31882 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31883 fewer problems with people using the wrong key.
31884 - Change the default exit policy to reject the default edonkey,
31885 kazaa, gnutella ports.
31886 - Add replace_file() to util.[ch] to handle win32's rename().
31888 o Changes from 0.0.8preX:
31889 - Fix two bugs in saving onion keys to disk when rotating, so
31890 hopefully we'll get fewer people using old onion keys.
31891 - Fix an assert error that was making SocksPolicy not work.
31892 - Be willing to expire routers that have an open dirport -- it's
31893 just the authoritative dirservers we want to not forget.
31894 - Reject tor-resolve requests for .onion addresses early, so we
31895 don't build a whole rendezvous circuit and then fail.
31896 - When you're warning a server that he's unverified, don't cry
31897 wolf unpredictably.
31898 - Fix a race condition: don't try to extend onto a connection
31899 that's still handshaking.
31900 - For servers in clique mode, require the conn to be open before
31901 you'll choose it for your path.
31902 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31903 end relay cell, etc.
31904 - Measure bandwidth capacity over the last 24 hours, not just 12
31905 - Bugfix: authoritative dirservers were making and signing a new
31906 directory for each client, rather than reusing the cached one.
31909 Changes in version 0.0.8pre2 - 2004-08-04
31910 o Changes from 0.0.7.2:
31912 - Check directory signature _before_ you decide whether you're
31913 you're running an obsolete version and should exit.
31914 - Check directory signature _before_ you parse the running-routers
31915 list to decide who's running or verified.
31916 - Bugfixes and features:
31917 - Check return value of fclose while writing to disk, so we don't
31918 end up with broken files when servers run out of disk space.
31919 - Log a warning if the user uses an unsafe socks variant, so people
31920 are more likely to learn about privoxy or socat.
31921 - Dirservers now include RFC1123-style dates in the HTTP headers,
31922 which one day we will use to better detect clock skew.
31924 o Changes from 0.0.8pre1:
31925 - Make it compile without warnings again on win32.
31926 - Log a warning if you're running an unverified server, to let you
31927 know you might want to get it verified.
31928 - Only pick a default nickname if you plan to be a server.
31931 Changes in version 0.0.8pre1 - 2004-07-23
31933 - Made our unit tests compile again on OpenBSD 3.5, and tor
31934 itself compile again on OpenBSD on a sparc64.
31935 - We were neglecting milliseconds when logging on win32, so
31936 everything appeared to happen at the beginning of each second.
31938 o Protocol changes:
31939 - 'Extend' relay cell payloads now include the digest of the
31940 intended next hop's identity key. Now we can verify that we're
31941 extending to the right router, and also extend to routers we
31942 hadn't heard of before.
31945 - Tor nodes can now act as relays (with an advertised ORPort)
31946 without being manually verified by the dirserver operators.
31947 - Uploaded descriptors of unverified routers are now accepted
31948 by the dirservers, and included in the directory.
31949 - Verified routers are listed by nickname in the running-routers
31950 list; unverified routers are listed as "$<fingerprint>".
31951 - We now use hash-of-identity-key in most places rather than
31952 nickname or addr:port, for improved security/flexibility.
31953 - To avoid Sybil attacks, paths still use only verified servers.
31954 But now we have a chance to play around with hybrid approaches.
31955 - Nodes track bandwidth usage to estimate capacity (not used yet).
31956 - ClientOnly option for nodes that never want to become servers.
31957 - Directory caching.
31958 - "AuthoritativeDir 1" option for the official dirservers.
31959 - Now other nodes (clients and servers) will cache the latest
31960 directory they've pulled down.
31961 - They can enable their DirPort to serve it to others.
31962 - Clients will pull down a directory from any node with an open
31963 DirPort, and check the signature/timestamp correctly.
31964 - Authoritative dirservers now fetch directories from other
31965 authdirservers, to stay better synced.
31966 - Running-routers list tells who's down also, along with noting
31967 if they're verified (listed by nickname) or unverified (listed
31969 - Allow dirservers to serve running-router list separately.
31970 This isn't used yet.
31971 - ORs connect-on-demand to other ORs
31972 - If you get an extend cell to an OR you're not connected to,
31973 connect, handshake, and forward the create cell.
31974 - The authoritative dirservers stay connected to everybody,
31975 and everybody stays connected to 0.0.7 servers, but otherwise
31976 clients/servers expire unused connections after 5 minutes.
31977 - When servers get a sigint, they delay 30 seconds (refusing new
31978 connections) then exit. A second sigint causes immediate exit.
31979 - File and name management:
31980 - Look for .torrc if no CONFDIR "torrc" is found.
31981 - If no datadir is defined, then choose, make, and secure ~/.tor
31983 - If torrc not found, exitpolicy reject *:*.
31984 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
31985 - If no nickname is defined, derive default from hostname.
31986 - Rename secret key files, e.g. identity.key -> secret_id_key,
31987 to discourage people from mailing their identity key to tor-ops.
31988 - Refuse to build a circuit before the directory has arrived --
31989 it won't work anyway, since you won't know the right onion keys
31991 - Try other dirservers immediately if the one you try is down. This
31992 should tolerate down dirservers better now.
31993 - Parse tor version numbers so we can do an is-newer-than check
31994 rather than an is-in-the-list check.
31995 - New socks command 'resolve', to let us shim gethostbyname()
31997 - A 'tor_resolve' script to access the socks resolve functionality.
31998 - A new socks-extensions.txt doc file to describe our
31999 interpretation and extensions to the socks protocols.
32000 - Add a ContactInfo option, which gets published in descriptor.
32001 - Publish OR uptime in descriptor (and thus in directory) too.
32002 - Write tor version at the top of each log file
32003 - New docs in the tarball:
32005 - Document that you should proxy your SSL traffic too.
32008 Changes in version 0.0.7.2 - 2004-07-07
32009 o A better fix for the 0.0.0.0 problem, that will hopefully
32010 eliminate the remaining related assertion failures.
32013 Changes in version 0.0.7.1 - 2004-07-04
32014 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
32015 since internally we use 0.0.0.0 to signify "not yet resolved".
32018 Changes in version 0.0.7 - 2004-06-07
32019 o Updated the man page to reflect the new features.
32022 Changes in version 0.0.7rc2 - 2004-06-06
32023 o Changes from 0.0.7rc1:
32024 - Make it build on Win32 again.
32025 o Changes from 0.0.6.2:
32026 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
32030 Changes in version 0.0.7rc1 - 2004-06-02
32032 - On sighup, we were adding another log without removing the first
32033 one. So log messages would get duplicated n times for n sighups.
32034 - Several cases of using a connection after we'd freed it. The
32035 problem was that connections that are pending resolve are in both
32036 the pending_resolve tree, and also the circuit's resolving_streams
32037 list. When you want to remove one, you must remove it from both.
32038 - Fix a double-mark-for-close where an end cell arrived for a
32039 resolving stream, and then the resolve failed.
32040 - Check directory signatures based on name of signer, not on whom
32041 we got the directory from. This will let us cache directories more
32044 - Crank up some of our constants to handle more users.
32047 Changes in version 0.0.7pre1 - 2004-06-02
32048 o Fixes for crashes and other obnoxious bugs:
32049 - Fix an epipe bug: sometimes when directory connections failed
32050 to connect, we would give them a chance to flush before closing
32052 - When we detached from a circuit because of resolvefailed, we
32053 would immediately try the same circuit twice more, and then
32054 give up on the resolve thinking we'd tried three different
32056 - Limit the number of intro circuits we'll attempt to build for a
32057 hidden service per 15-minute period.
32058 - Check recommended-software string *early*, before actually parsing
32059 the directory. Thus we can detect an obsolete version and exit,
32060 even if the new directory format doesn't parse.
32061 o Fixes for security bugs:
32062 - Remember which nodes are dirservers when you startup, and if a
32063 random OR enables his dirport, don't automatically assume he's
32064 a trusted dirserver.
32066 - Directory connections were asking the wrong poll socket to
32067 start writing, and not asking themselves to start writing.
32068 - When we detached from a circuit because we sent a begin but
32069 didn't get a connected, we would use it again the first time;
32070 but after that we would correctly switch to a different one.
32071 - Stop warning when the first onion decrypt attempt fails; they
32072 will sometimes legitimately fail now that we rotate keys.
32073 - Override unaligned-access-ok check when $host_cpu is ia64 or
32074 arm. Apparently they allow it but the kernel whines.
32075 - Dirservers try to reconnect periodically too, in case connections
32077 - Fix some memory leaks in directory servers.
32078 - Allow backslash in Win32 filenames.
32079 - Made Tor build complain-free on FreeBSD, hopefully without
32080 breaking other BSD builds. We'll see.
32082 - Doxygen markup on all functions and global variables.
32083 - Make directory functions update routerlist, not replace it. So
32084 now directory disagreements are not so critical a problem.
32085 - Remove the upper limit on number of descriptors in a dirserver's
32086 directory (not that we were anywhere close).
32087 - Allow multiple logfiles at different severity ranges.
32088 - Allow *BindAddress to specify ":port" rather than setting *Port
32089 separately. Allow multiple instances of each BindAddress config
32090 option, so you can bind to multiple interfaces if you want.
32091 - Allow multiple exit policy lines, which are processed in order.
32092 Now we don't need that huge line with all the commas in it.
32093 - Enable accept/reject policies on SOCKS connections, so you can bind
32094 to 0.0.0.0 but still control who can use your OP.
32097 Changes in version 0.0.6.2 - 2004-05-16
32098 o Our integrity-checking digest was checking only the most recent cell,
32099 not the previous cells like we'd thought.
32100 Thanks to Stefan Mark for finding the flaw!
32103 Changes in version 0.0.6.1 - 2004-05-06
32104 o Fix two bugs in our AES counter-mode implementation (this affected
32105 onion-level stream encryption, but not TLS-level). It turns
32106 out we were doing something much more akin to a 16-character
32107 polyalphabetic cipher. Oops.
32108 Thanks to Stefan Mark for finding the flaw!
32109 o Retire moria3 as a directory server, and add tor26 as a directory
32113 Changes in version 0.0.6 - 2004-05-02
32114 [version bump only]
32117 Changes in version 0.0.6rc4 - 2004-05-01
32118 o Update the built-in dirservers list to use the new directory format
32119 o Fix a rare seg fault: if a node offering a hidden service attempts
32120 to build a circuit to Alice's rendezvous point and fails before it
32121 reaches the last hop, it retries with a different circuit, but
32123 o Handle windows socket errors correctly.
32126 Changes in version 0.0.6rc3 - 2004-04-28
32127 o Don't expire non-general excess circuits (if we had enough
32128 circuits open, we were expiring rendezvous circuits -- even
32129 when they had a stream attached. oops.)
32130 o Fetch randomness from /dev/urandom better (not via fopen/fread)
32131 o Better debugging for tls errors
32132 o Some versions of openssl have an SSL_pending function that erroneously
32133 returns bytes when there is a non-application record pending.
32134 o Set Content-Type on the directory and hidserv descriptor.
32135 o Remove IVs from cipher code, since AES-ctr has none.
32136 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
32137 o We were using an array of length zero in a few places.
32138 o win32's gethostbyname can't resolve an IP to an IP.
32139 o win32's close can't close a socket.
32142 Changes in version 0.0.6rc2 - 2004-04-26
32143 o Fix a bug where we were closing tls connections intermittently.
32144 It turns out openssl keeps its errors around -- so if an error
32145 happens, and you don't ask about it, and then another openssl
32146 operation happens and succeeds, and you ask if there was an error,
32147 it tells you about the first error. Fun fun.
32148 o Fix a bug that's been lurking since 27 may 03 (!)
32149 When passing back a destroy cell, we would use the wrong circ id.
32150 'Mostly harmless', but still worth fixing.
32151 o Since we don't support truncateds much, don't bother sending them;
32152 just close the circ.
32153 o check for <machine/limits.h> so we build on NetBSD again (I hope).
32154 o don't crash if a conn that sent a begin has suddenly lost its circuit
32155 (this was quite rare).
32158 Changes in version 0.0.6rc1 - 2004-04-25
32159 o We now rotate link (tls context) keys and onion keys.
32160 o CREATE cells now include oaep padding, so you can tell
32161 if you decrypted them correctly.
32162 o Add bandwidthburst to server descriptor.
32163 o Directories now say which dirserver signed them.
32164 o Use a tor_assert macro that logs failed assertions too.
32167 Changes in version 0.0.6pre5 - 2004-04-18
32168 o changes from 0.0.6pre4:
32169 - make tor build on broken freebsd 5.2 installs
32170 - fix a failed assert when you try an intro point, get a nack, and try
32171 a second one and it works.
32172 - when alice uses a port that the hidden service doesn't accept,
32173 it now sends back an end cell (denied by exit policy). otherwise
32174 alice would just have to wait to time out.
32175 - fix another rare bug: when we had tried all the intro
32176 points for a hidden service, we fetched the descriptor
32177 again, but we left our introcirc thinking it had already
32178 sent an intro, so it kept waiting for a response...
32179 - bugfix: when you sleep your hidden-service laptop, as soon
32180 as it wakes up it tries to upload a service descriptor, but
32181 socketpair fails for some reason (localhost not up yet?).
32182 now we simply give up on that upload, and we'll try again later.
32183 i'd still like to find the bug though.
32184 - if an intro circ waiting for an ack dies before getting one, then
32186 - we were reusing stale service descriptors and refetching usable
32190 Changes in version 0.0.6pre4 - 2004-04-14
32191 o changes from 0.0.6pre3:
32192 - when bob fails to connect to the rendezvous point, and his
32193 circ didn't fail because of the rendezvous point itself, then
32194 he retries a couple of times
32195 - we expire introduction and rendezvous circs more thoroughly
32196 (sometimes they were hanging around forever)
32197 - we expire unattached rendezvous streams that have been around
32198 too long (they were sticking around forever).
32199 - fix a measly fencepost error that was crashing everybody with
32203 Changes in version 0.0.6pre3 - 2004-04-14
32204 o changes from 0.0.6pre2:
32205 - make hup work again
32206 - fix some memory leaks for dirservers
32207 - allow more skew in rendezvous descriptor timestamps, to help
32208 handle people like blanu who don't know what time it is
32209 - normal circs are 3 hops, but some rend/intro circs are 4, if
32210 the initiator doesn't get to choose the last hop
32211 - send acks for introductions, so alice can know whether to try
32213 - bob publishes intro points more correctly
32214 o changes from 0.0.5:
32215 - fix an assert trigger that's been plaguing us since the days
32216 of 0.0.2prexx (thanks weasel!)
32217 - retry stream correctly when we fail to connect because of
32218 exit-policy-reject (should try another) or can't-resolve-address
32219 (also should try another, because dns on random internet servers
32221 - when we hup a dirserver and we've *removed* a server from the
32222 approved-routers list, now we remove that server from the
32223 in-memory directories too
32226 Changes in version 0.0.6pre2 - 2004-04-08
32227 o We fixed our base32 implementation. Now it works on all architectures.
32230 Changes in version 0.0.6pre1 - 2004-04-08
32232 - Hidden services and rendezvous points are implemented. Go to
32233 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
32234 hidden services. (This only works via a socks4a proxy such as
32235 Privoxy, and currently it's quite slow.)
32238 Changes in version 0.0.5 - 2004-03-30
32239 [version bump only]
32242 Changes in version 0.0.5rc3 - 2004-03-29
32243 o Install torrc as torrc.sample -- we no longer clobber your
32245 o Re-enable recommendedversion checking (we broke it in rc2, oops)
32246 o Add in a 'notice' log level for things the operator should hear
32247 but that aren't warnings
32250 Changes in version 0.0.5rc2 - 2004-03-29
32251 o Hold socks connection open until reply is flushed (if possible)
32252 o Make exit nodes resolve IPs to IPs immediately, rather than asking
32253 the dns farm to do it.
32254 o Fix c99 aliasing warnings in rephist.c
32255 o Don't include server descriptors that are older than 24 hours in the
32257 o Give socks 'reject' replies their whole 15s to attempt to flush,
32258 rather than seeing the 60s timeout and assuming the flush had failed.
32259 o Clean automake droppings from the cvs repository
32262 Changes in version 0.0.5rc1 - 2004-03-28
32263 o Fix mangled-state bug in directory fetching (was causing sigpipes).
32264 o Only build circuits after we've fetched the directory: clients were
32265 using only the directory servers before they'd fetched a directory.
32266 This also means longer startup time; so it goes.
32267 o Fix an assert trigger where an OP would fail to handshake, and we'd
32268 expect it to have a nickname.
32269 o Work around a tsocks bug: do a socks reject when AP connection dies
32270 early, else tsocks goes into an infinite loop.
32273 Changes in version 0.0.4 - 2004-03-26
32274 o When connecting to a dirserver or OR and the network is down,
32278 Changes in version 0.0.3 - 2004-03-26
32279 o Warn and fail if server chose a nickname with illegal characters
32280 o Port to Solaris and Sparc:
32281 - include missing header fcntl.h
32282 - have autoconf find -lsocket -lnsl automatically
32283 - deal with hardware word alignment
32284 - make uname() work (solaris has a different return convention)
32285 - switch from using signal() to sigaction()
32286 o Preliminary work on reputation system:
32287 - Keep statistics on success/fail of connect attempts; they're published
32288 by kill -USR1 currently.
32289 - Add a RunTesting option to try to learn link state by creating test
32290 circuits, even when SocksPort is off.
32291 - Remove unused open circuits when there are too many.
32294 Changes in version 0.0.2 - 2004-03-19
32295 - Include strlcpy and strlcat for safer string ops
32296 - define INADDR_NONE so we compile (but still not run) on solaris
32299 Changes in version 0.0.2pre27 - 2004-03-14
32301 - Allow internal tor networks (we were rejecting internal IPs,
32302 now we allow them if they're set explicitly).
32303 - And fix a few endian issues.
32306 Changes in version 0.0.2pre26 - 2004-03-14
32308 - If a stream times out after 15s without a connected cell, don't
32309 try that circuit again: try a new one.
32310 - Retry streams at most 4 times. Then give up.
32311 - When a dirserver gets a descriptor from an unknown router, it
32312 logs its fingerprint (so the dirserver operator can choose to
32313 accept it even without mail from the server operator).
32314 - Inform unapproved servers when we reject their descriptors.
32315 - Make tor build on Windows again. It works as a client, who knows
32317 - Clearer instructions in the torrc for how to set up a server.
32318 - Be more efficient about reading fd's when our global token bucket
32319 (used for rate limiting) becomes empty.
32321 - Stop asserting that computers always go forward in time. It's
32323 - When we sent a cell (e.g. destroy) and then marked an OR connection
32324 expired, we might close it before finishing a flush if the other
32325 side isn't reading right then.
32326 - Don't allow dirservers to start if they haven't defined
32327 RecommendedVersions
32328 - We were caching transient dns failures. Oops.
32329 - Prevent servers from publishing an internal IP as their address.
32330 - Address a strcat vulnerability in circuit.c
32333 Changes in version 0.0.2pre25 - 2004-03-04
32335 - Put the OR's IP in its router descriptor, not its fqdn. That way
32336 we'll stop being stalled by gethostbyname for nodes with flaky dns,
32339 - If the user typed in an address that didn't resolve, the server
32343 Changes in version 0.0.2pre24 - 2004-03-03
32345 - Fix an assertion failure in dns.c, where we were trying to dequeue
32346 a pending dns resolve even if it wasn't pending
32347 - Fix a spurious socks5 warning about still trying to write after the
32348 connection is finished.
32349 - Hold certain marked_for_close connections open until they're finished
32350 flushing, rather than losing bytes by closing them too early.
32351 - Correctly report the reason for ending a stream
32352 - Remove some duplicate calls to connection_mark_for_close
32353 - Put switch_id and start_daemon earlier in the boot sequence, so it
32354 will actually try to chdir() to options.DataDirectory
32355 - Make 'make test' exit(1) if a test fails; fix some unit tests
32356 - Make tor fail when you use a config option it doesn't know about,
32357 rather than warn and continue.
32358 - Make --version work
32359 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
32362 Changes in version 0.0.2pre23 - 2004-02-29
32364 - Print a statement when the first circ is finished, so the user
32365 knows it's working.
32366 - If a relay cell is unrecognized at the end of the circuit,
32367 send back a destroy. (So attacks to mutate cells are more
32369 - New config option 'excludenodes' to avoid certain nodes for circuits.
32370 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
32371 so you can collect coredumps there.
32373 - Fix a bug in tls flushing where sometimes data got wedged and
32374 didn't flush until more data got sent. Hopefully this bug was
32375 a big factor in the random delays we were seeing.
32376 - Make 'connected' cells include the resolved IP, so the client
32377 dns cache actually gets populated.
32378 - Disallow changing from ORPort=0 to ORPort>0 on hup.
32379 - When we time-out on a stream and detach from the circuit, send an
32380 end cell down it first.
32381 - Only warn about an unknown router (in exitnodes, entrynodes,
32382 excludenodes) after we've fetched a directory.
32385 Changes in version 0.0.2pre22 - 2004-02-26
32387 - Servers publish less revealing uname information in descriptors.
32388 - More memory tracking and assertions, to crash more usefully when
32390 - If the default torrc isn't there, just use some default defaults.
32391 Plus provide an internal dirservers file if they don't have one.
32392 - When the user tries to use Tor as an http proxy, give them an http
32393 501 failure explaining that we're a socks proxy.
32394 - Dump a new router.desc on hup, to help confused people who change
32395 their exit policies and then wonder why router.desc doesn't reflect
32397 - Clean up the generic tor.sh init script that we ship with.
32399 - If the exit stream is pending on the resolve, and a destroy arrives,
32400 then the stream wasn't getting removed from the pending list. I
32401 think this was the one causing recent server crashes.
32402 - Use a more robust poll on OSX 10.3, since their poll is flaky.
32403 - When it couldn't resolve any dirservers, it was useless from then on.
32404 Now it reloads the RouterFile (or default dirservers) if it has no
32406 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
32407 many users don't even *have* a /usr/local/sbin/.
32410 Changes in version 0.0.2pre21 - 2004-02-18
32412 - There's a ChangeLog file that actually reflects the changelog.
32413 - There's a 'torify' wrapper script, with an accompanying
32414 tor-tsocks.conf, that simplifies the process of using tsocks for
32415 tor. It even has a man page.
32416 - The tor binary gets installed to sbin rather than bin now.
32417 - Retry streams where the connected cell hasn't arrived in 15 seconds
32418 - Clean up exit policy handling -- get the default out of the torrc,
32419 so we can update it without forcing each server operator to fix
32421 - Allow imaps and pop3s in default exit policy
32423 - Prevent picking middleman nodes as the last node in the circuit
32426 Changes in version 0.0.2pre20 - 2004-01-30
32428 - We now have a deb package, and it's in debian unstable. Go to
32429 it, apt-getters. :)
32430 - I've split the TotalBandwidth option into BandwidthRate (how many
32431 bytes per second you want to allow, long-term) and
32432 BandwidthBurst (how many bytes you will allow at once before the cap
32433 kicks in). This better token bucket approach lets you, say, set
32434 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
32435 performance while not exceeding your monthly bandwidth quota.
32436 - Push out a tls record's worth of data once you've got it, rather
32437 than waiting until you've read everything waiting to be read. This
32438 may improve performance by pipelining better. We'll see.
32439 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
32440 from failed circuits (if they haven't been connected yet) and attach
32442 - Expire old streams that haven't managed to connect. Some day we'll
32443 have them reattach to new circuits instead.
32446 - Fix several memory leaks that were causing servers to become bloated
32448 - Fix a few very rare assert triggers. A few more remain.
32449 - Setuid to User _before_ complaining about running as root.
32452 Changes in version 0.0.2pre19 - 2004-01-07
32454 - Fix deadlock condition in dns farm. We were telling a child to die by
32455 closing the parent's file descriptor to him. But newer children were
32456 inheriting the open file descriptor from the parent, and since they
32457 weren't closing it, the socket never closed, so the child never read
32458 eof, so he never knew to exit. Similarly, dns workers were holding
32459 open other sockets, leading to all sorts of chaos.
32460 - New cleaner daemon() code for forking and backgrounding.
32461 - If you log to a file, it now prints an entry at the top of the
32462 logfile so you know it's working.
32463 - The onionskin challenge length was 30 bytes longer than necessary.
32464 - Started to patch up the spec so it's not quite so out of date.
32467 Changes in version 0.0.2pre18 - 2004-01-02
32469 - Fix endian issues with the 'integrity' field in the relay header.
32470 - Fix a potential bug where connections in state
32471 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
32474 Changes in version 0.0.2pre17 - 2003-12-30
32476 - Made --debuglogfile (or any second log file, actually) work.
32477 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
32478 adversary could force us into an infinite loop.
32481 - Each onionskin handshake now includes a hash of the computed key,
32482 to prove the server's identity and help perfect forward secrecy.
32483 - Changed cell size from 256 to 512 bytes (working toward compatibility
32485 - Changed cell length to 2 bytes, and moved it to the relay header.
32486 - Implemented end-to-end integrity checking for the payloads of
32488 - Separated streamid from 'recognized' (otherwise circuits will get
32489 messed up when we try to have streams exit from the middle). We
32490 use the integrity-checking to confirm that a cell is addressed to
32492 - Randomize the initial circid and streamid values, so an adversary who
32493 breaks into a node can't learn how many circuits or streams have
32497 Changes in version 0.0.2pre16 - 2003-12-14
32499 - Fixed a bug that made HUP trigger an assert
32500 - Fixed a bug where a circuit that immediately failed wasn't being
32501 counted as a failed circuit in counting retries.
32504 - Now we close the circuit when we get a truncated cell: otherwise we're
32505 open to an anonymity attack where a bad node in the path truncates
32506 the circuit and then we open streams at him.
32507 - Add port ranges to exit policies
32508 - Add a conservative default exit policy
32509 - Warn if you're running tor as root
32510 - on HUP, retry OR connections and close/rebind listeners
32511 - options.EntryNodes: try these nodes first when picking the first node
32512 - options.ExitNodes: if your best choices happen to include any of
32513 your preferred exit nodes, you choose among just those preferred
32515 - options.ExcludedNodes: nodes that are never picked in path building
32518 Changes in version 0.0.2pre15 - 2003-12-03
32519 o Robustness and bugfixes:
32520 - Sometimes clients would cache incorrect DNS resolves, which would
32521 really screw things up.
32522 - An OP that goes offline would slowly leak all its sockets and stop
32524 - A wide variety of bugfixes in exit node selection, exit policy
32525 handling, and processing pending streams when a new circuit is
32527 - Pick nodes for a path only from those the directory says are up
32528 - Choose randomly from all running dirservers, not always the first one
32529 - Increase allowed http header size for directory fetch.
32530 - Stop writing to stderr (if we're daemonized it will be closed).
32531 - Enable -g always, so cores will be more useful to me.
32532 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
32535 - Wrote a man page. It lists commonly used options.
32538 - Change default loglevel to warn.
32539 - Make PidFile default to null rather than littering in your CWD.
32540 - OnionRouter config option is now obsolete. Instead it just checks
32542 - Moved to a single unified torrc file for both clients and servers.
32545 Changes in version 0.0.2pre14 - 2003-11-29
32546 o Robustness and bugfixes:
32547 - Force the admin to make the DataDirectory himself
32548 - to get ownership/permissions right
32549 - so clients no longer make a DataDirectory and then never use it
32550 - fix bug where a client who was offline for 45 minutes would never
32551 pull down a directory again
32552 - fix (or at least hide really well) the dns assert bug that was
32553 causing server crashes
32554 - warnings and improved robustness wrt clockskew for certs
32555 - use the native daemon(3) to daemonize, when available
32556 - exit if bind() fails
32557 - exit if neither socksport nor orport is defined
32558 - include our own tor_timegm (Win32 doesn't have its own)
32559 - bugfix for win32 with lots of connections
32560 - fix minor bias in PRNG
32561 - make dirserver more robust to corrupt cached directory
32564 - Wrote the design document (woo)
32566 o Circuit building and exit policies:
32567 - Circuits no longer try to use nodes that the directory has told them
32569 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
32570 bitcounts (18.0.0.0/8).
32571 - Make AP connections standby for a circuit if no suitable circuit
32572 exists, rather than failing
32573 - Circuits choose exit node based on addr/port, exit policies, and
32574 which AP connections are standing by
32575 - Bump min pathlen from 2 to 3
32576 - Relay end cells have a payload to describe why the stream ended.
32577 - If the stream failed because of exit policy, try again with a new
32579 - Clients have a dns cache to remember resolved addresses.
32580 - Notice more quickly when we have no working circuits
32583 - APPort is now called SocksPort
32584 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
32586 - RecommendedVersions is now a config variable rather than
32587 hardcoded (for dirservers)
32588 - Reloads config on HUP
32589 - Usage info on -h or --help
32590 - If you set User and Group config vars, it'll setu/gid to them.
32593 Changes in version 0.0.2pre13 - 2003-10-19
32594 o General stability:
32595 - SSL_write no longer fails when it returns WANTWRITE and the number
32596 of bytes in the buf has changed by the next SSL_write call.
32597 - Fix segfault fetching directory when network is down
32598 - Fix a variety of minor memory leaks
32599 - Dirservers reload the fingerprints file on HUP, so I don't have
32600 to take down the network when I approve a new router
32601 - Default server config file has explicit Address line to specify fqdn
32604 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
32605 - Make listener connections not ever alloc bufs
32607 o Autoconf improvements:
32608 - don't clobber an external CFLAGS in ./configure
32609 - Make install now works
32610 - create var/lib/tor on make install
32611 - autocreate a tor.sh initscript to help distribs
32612 - autocreate the torrc and sample-server-torrc with correct paths
32614 o Log files and Daemonizing now work:
32615 - If --DebugLogFile is specified, log to it at -l debug
32616 - If --LogFile is specified, use it instead of commandline
32617 - If --RunAsDaemon is set, tor forks and backgrounds on startup