1 Changes in version 0.4.1.6 - 2019-09-19
2 This release backports several bugfixes to improve stability and
3 correctness. Anyone experiencing build problems or crashes with 0.4.1.5,
4 or experiencing reliability issues with single onion services, should
7 o Major bugfixes (crash, Linux, Android, backport from 0.4.2.1-alpha):
8 - Tolerate systems (including some Android installations) where
9 madvise and MADV_DONTDUMP are available at build-time, but not at
10 run time. Previously, these systems would notice a failed syscall
11 and abort. Fixes bug 31570; bugfix on 0.4.1.1-alpha.
12 - Tolerate systems (including some Linux installations) where
13 madvise and/or MADV_DONTFORK are available at build-time, but not
14 at run time. Previously, these systems would notice a failed
15 syscall and abort. Fixes bug 31696; bugfix on 0.4.1.1-alpha.
17 o Minor features (stem tests, backport from 0.4.2.1-alpha):
18 - Change "make test-stem" so it only runs the stem tests that use
19 tor. This change makes test-stem faster and more reliable. Closes
22 o Minor bugfixes (build system, backport form 0.4.2.1-alpha):
23 - Do not include the deprecated <sys/sysctl.h> on Linux or Windows
24 systems. Fixes bug 31673; bugfix on 0.2.5.4-alpha.
26 o Minor bugfixes (compilation, backport from 0.4.2.1-alpha):
27 - Add more stub functions to fix compilation on Android with link-
28 time optimization when --disable-module-dirauth is used.
29 Previously, these compilation settings would make the compiler
30 look for functions that didn't exist. Fixes bug 31552; bugfix
32 - Suppress spurious float-conversion warnings from GCC when calling
33 floating-point classifier functions on FreeBSD. Fixes part of bug
34 31687; bugfix on 0.3.1.5-alpha.
36 o Minor bugfixes (controller protocol):
37 - Fix the MAPADDRESS controller command to accept one or more
38 arguments. Previously, it required two or more arguments, and ignored
39 the first. Fixes bug 31772; bugfix on 0.4.1.1-alpha.
41 o Minor bugfixes (guards, backport from 0.4.2.1-alpha):
42 - When tor is missing descriptors for some primary entry guards,
43 make the log message less alarming. It's normal for descriptors to
44 expire, as long as tor fetches new ones soon after. Fixes bug
45 31657; bugfix on 0.3.3.1-alpha.
47 o Minor bugfixes (logging, backport from 0.4.2.1-alpha):
48 - Change log level of message "Hash of session info was not as
49 expected" to LOG_PROTOCOL_WARN. Fixes bug 12399; bugfix
52 o Minor bugfixes (rust, backport from 0.4.2.1-alpha):
53 - Correctly exclude a redundant rust build job in Travis. Fixes bug
54 31463; bugfix on 0.3.5.4-alpha.
56 o Minor bugfixes (v2 single onion services, backport from 0.4.2.1-alpha):
57 - Always retry v2 single onion service intro and rend circuits with
58 a 3-hop path. Previously, v2 single onion services used a 3-hop
59 path when rendezvous circuits were retried after a remote or
60 delayed failure, but a 1-hop path for immediate retries. Fixes bug
61 23818; bugfix on 0.2.9.3-alpha.
63 o Minor bugfixes (v3 single onion services, backport from 0.4.2.1-alpha):
64 - Always retry v3 single onion service intro and rend circuits with
65 a 3-hop path. Previously, v3 single onion services used a 3-hop
66 path when rend circuits were retried after a remote or delayed
67 failure, but a 1-hop path for immediate retries. Fixes bug 23818;
68 bugfix on 0.3.2.1-alpha.
69 - Make v3 single onion services fall back to a 3-hop intro, when all
70 intro points are unreachable via a 1-hop path. Previously, v3
71 single onion services failed when all intro nodes were unreachable
72 via a 1-hop path. Fixes bug 23507; bugfix on 0.3.2.1-alpha.
74 o Documentation (backport from 0.4.2.1-alpha):
75 - Use RFC 2397 data URL scheme to embed an image into tor-exit-
76 notice.html so that operators no longer have to host it
77 themselves. Closes ticket 31089.
80 Changes in version 0.4.1.5 - 2019-08-20
81 This is the first stable release in the 0.4.1.x series. This series
82 adds experimental circuit-level padding, authenticated SENDME cells to
83 defend against certain attacks, and several performance improvements
84 to save on CPU consumption. It fixes bugs in bootstrapping and v3
85 onion services. It also includes numerous smaller features and
86 bugfixes on earlier versions.
88 Per our support policy, we will support the 0.4.1.x series for nine
89 months, or until three months after the release of a stable 0.4.2.x:
90 whichever is longer. If you need longer-term support, please stick
91 with 0.3.5.x, which will we plan to support until Feb 2022.
93 Below are the changes since 0.4.1.4-rc. For a complete list of changes
94 since 0.4.0.5, see the ReleaseNotes file.
96 o Directory authority changes:
97 - The directory authority "dizum" has a new IP address. Closes
100 o Minor features (circuit padding logging):
101 - Demote noisy client-side warn logs about circuit padding to
102 protocol warnings. Add additional log messages and circuit ID
103 fields to help with bug 30992 and any other future issues.
105 o Minor bugfixes (circuit padding negotiation):
106 - Bump the circuit padding protocol version to explicitly signify
107 that the HS setup machine support is finalized in 0.4.1.x-stable.
108 This also means that 0.4.1.x-alpha clients will not negotiate
109 padding with 0.4.1.x-stable relays, and 0.4.1.x-stable clients
110 will not negotiate padding with 0.4.1.x-alpha relays (or 0.4.0.x
111 relays). Fixes bug 31356; bugfix on 0.4.1.1-alpha.
113 o Minor bugfixes (circuit padding):
114 - Ignore non-padding cells on padding circuits. This addresses
115 various warning messages from subsystems that were not expecting
116 padding circuits. Fixes bug 30942; bugfix on 0.4.1.1-alpha.
118 o Minor bugfixes (clock skew detection):
119 - Don't believe clock skew results from NETINFO cells that appear to
120 arrive before we sent the VERSIONS cells they are responding to.
121 Previously, we would accept them up to 3 minutes "in the past".
122 Fixes bug 31343; bugfix on 0.2.4.4-alpha.
124 o Minor bugfixes (compatibility, standards compliance):
125 - Fix a bug that would invoke undefined behavior on certain
126 operating systems when trying to asprintf() a string exactly
127 INT_MAX bytes long. We don't believe this is exploitable, but it's
128 better to fix it anyway. Fixes bug 31001; bugfix on 0.2.2.11-alpha.
129 Found and fixed by Tobias Stoeckmann.
131 o Minor bugfixes (compilation warning):
132 - Fix a compilation warning on Windows about casting a function
133 pointer for GetTickCount64(). Fixes bug 31374; bugfix
136 o Minor bugfixes (compilation):
137 - Avoid using labs() on time_t, which can cause compilation warnings
138 on 64-bit Windows builds. Fixes bug 31343; bugfix on 0.2.4.4-alpha.
140 o Minor bugfixes (distribution):
141 - Do not ship any temporary files found in the
142 scripts/maint/practracker directory. Fixes bug 31311; bugfix
145 o Testing (continuous integration):
146 - In Travis, make stem log a controller trace to the console, and
147 tail stem's tor log after failure. Closes ticket 30591.
148 - In Travis, only run the stem tests that use a tor binary. Closes
152 Changes in version 0.4.1.4-rc - 2019-07-25
153 Tor 0.4.1.4-rc fixes a few bugs from previous versions of Tor, and
154 updates to a new list of fallback directories. If no new bugs are
155 found, the next release in the 0.4.1.x serious should be stable.
157 o Major bugfixes (circuit build, guard):
158 - When considering upgrading circuits from "waiting for guard" to
159 "open", always ignore circuits that are marked for close. Otherwise,
160 we can end up in the situation where a subsystem is notified that
161 a closing circuit has just opened, leading to undesirable
162 behavior. Fixes bug 30871; bugfix on 0.3.0.1-alpha.
164 o Minor features (continuous integration):
165 - Our Travis configuration now uses Chutney to run some network
166 integration tests automatically. Closes ticket 29280.
168 o Minor features (fallback directory list):
169 - Replace the 157 fallbacks originally introduced in Tor 0.3.5.6-rc
170 in December 2018 (of which ~122 were still functional), with a
171 list of 148 fallbacks (70 new, 78 existing, 79 removed) generated
172 in June 2019. Closes ticket 28795.
174 o Minor bugfixes (circuit padding):
175 - On relays, properly check that a padding machine is absent before
176 logging a warning about it being absent. Fixes bug 30649; bugfix
178 - Add two NULL checks in unreachable places to silence Coverity (CID
179 144729 and 1447291) and better future-proof ourselves. Fixes bug
180 31024; bugfix on 0.4.1.1-alpha.
182 o Minor bugfixes (crash on exit):
183 - Avoid a set of possible code paths that could try to use freed
184 memory in routerlist_free() while Tor was exiting. Fixes bug
185 31003; bugfix on 0.1.2.2-alpha.
187 o Minor bugfixes (logging):
188 - Fix a conflict between the flag used for messaging-domain log
189 messages, and the LD_NO_MOCK testing flag. Fixes bug 31080; bugfix
192 o Minor bugfixes (memory leaks):
193 - Fix a trivial memory leak when parsing an invalid value from a
194 download schedule in the configuration. Fixes bug 30894; bugfix
197 o Code simplification and refactoring:
198 - Remove some dead code from circpad_machine_remove_token() to fix
199 some Coverity warnings (CID 1447298). Fixes bug 31027; bugfix
203 Changes in version 0.4.1.3-alpha - 2019-06-25
204 Tor 0.4.1.3-alpha resolves numerous bugs left over from the previous
205 alpha, most of them from earlier release series.
207 o Major bugfixes (Onion service reachability):
208 - Properly clean up the introduction point map when circuits change
209 purpose from onion service circuits to pathbias, measurement, or
210 other circuit types. This should fix some service-side instances
211 of introduction point failure. Fixes bug 29034; bugfix
214 o Minor features (geoip):
215 - Update geoip and geoip6 to the June 10 2019 Maxmind GeoLite2
216 Country database. Closes ticket 30852.
218 o Minor features (logging):
219 - Give a more useful assertion failure message if we think we have
220 minherit() but we fail to make a region non-inheritable. Give a
221 compile-time warning if our support for minherit() is incomplete.
224 o Minor bugfixes (circuit isolation):
225 - Fix a logic error that prevented the SessionGroup sub-option from
226 being accepted. Fixes bug 22619; bugfix on 0.2.7.2-alpha.
228 o Minor bugfixes (continuous integration):
229 - Allow the test-stem job to fail in Travis, because it sometimes
230 hangs. Fixes bug 30744; bugfix on 0.3.5.4-alpha.
231 - Skip test_rebind on macOS in Travis, because it is unreliable on
232 macOS on Travis. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
233 - Skip test_rebind when the TOR_SKIP_TEST_REBIND environment
234 variable is set. Fixes bug 30713; bugfix on 0.3.5.1-alpha.
236 o Minor bugfixes (directory authorities):
237 - Stop crashing after parsing an unknown descriptor purpose
238 annotation. We think this bug can only be triggered by modifying a
239 local file. Fixes bug 30781; bugfix on 0.2.0.8-alpha.
241 o Minor bugfixes (pluggable transports):
242 - When running as a bridge with pluggable transports, always publish
243 pluggable transport information in our extrainfo descriptor, even
244 if ExtraInfoStatistics is 0. This information is needed by
245 BridgeDB. Fixes bug 30956; bugfix on 0.4.1.1-alpha.
248 - Mention URLs for Travis/Appveyor/Jenkins in ReleasingTor.md.
252 Changes in version 0.4.1.2-alpha - 2019-06-06
253 Tor 0.4.1.2-alpha resolves numerous bugs--some of them from the
254 previous alpha, and some much older. It also contains minor testing
255 improvements, and an improvement to the security of our authenticated
256 SENDME implementation.
258 o Major bugfixes (bridges):
259 - Consider our directory information to have changed when our list
260 of bridges changes. Previously, Tor would not re-compute the
261 status of its directory information when bridges changed, and
262 therefore would not realize that it was no longer able to build
263 circuits. Fixes part of bug 29875.
264 - Do not count previously configured working bridges towards our
265 total of working bridges. Previously, when Tor's list of bridges
266 changed, it would think that the old bridges were still usable,
267 and delay fetching router descriptors for the new ones. Fixes part
268 of bug 29875; bugfix on 0.3.0.1-alpha.
270 o Major bugfixes (flow control, SENDME):
271 - Decrement the stream-level package window after packaging a cell.
272 Previously, it was done inside a log_debug() call, meaning that if
273 debug logs were not enabled, the decrement would never happen, and
274 thus the window would be out of sync with the other end point.
275 Fixes bug 30628; bugfix on 0.4.1.1-alpha.
277 o Major bugfixes (onion service reachability):
278 - Properly clean up the introduction point map and associated state
279 when circuits change purpose from onion service circuits to
280 pathbias, measurement, or other circuit types. This may fix some
281 instances of introduction point failure. Fixes bug 29034; bugfix
284 o Minor features (authenticated SENDME):
285 - Ensure that there is enough randomness on every circuit to prevent
286 an attacker from successfully predicting the hashes they will need
287 to include in authenticated SENDME cells. At a random interval, if
288 we have not sent randomness already, we now leave some extra space
289 at the end of a cell that we can fill with random bytes. Closes
292 o Minor features (continuous integration):
293 - When running coverage builds on Travis, we now set
294 TOR_TEST_RNG_SEED, to avoid RNG-based coverage differences. Part
297 o Minor features (maintenance):
298 - Add a new "make autostyle" target that developers can use to apply
299 all automatic Tor style and consistency conversions to the
300 codebase. Closes ticket 30539.
302 o Minor features (testing):
303 - The circuitpadding tests now use a reproducible RNG implementation,
304 so that if a test fails, we can learn why. Part of ticket 28878.
305 - Tor's tests now support an environment variable, TOR_TEST_RNG_SEED,
306 to set the RNG seed for tests that use a reproducible RNG. Part of
308 - When running tests in coverage mode, take additional care to make
309 our coverage deterministic, so that we can accurately track
310 changes in code coverage. Closes ticket 30519.
312 o Minor bugfixes (configuration, proxies):
313 - Fix a bug that prevented us from supporting SOCKS5 proxies that
314 want authentication along with configured (but unused!)
315 ClientTransportPlugins. Fixes bug 29670; bugfix on 0.2.6.1-alpha.
317 o Minor bugfixes (controller):
318 - POSTDESCRIPTOR requests should work again. Previously, they were
319 broken if a "purpose=" flag was specified. Fixes bug 30580; bugfix
321 - Repair the HSFETCH command so that it works again. Previously, it
322 expected a body when it shouldn't have. Fixes bug 30646; bugfix
325 o Minor bugfixes (developer tooling):
326 - Fix pre-push hook to allow fixup and squash commits when pushing
327 to non-upstream git remote. Fixes bug 30286; bugfix
330 o Minor bugfixes (directory authority):
331 - Move the "bandwidth-file-headers" line in directory authority
332 votes so that it conforms to dir-spec.txt. Fixes bug 30316; bugfix
335 o Minor bugfixes (NetBSD):
336 - Fix usage of minherit() on NetBSD and other platforms that define
337 MAP_INHERIT_{ZERO,NONE} instead of INHERIT_{ZERO,NONE}. Fixes bug
338 30614; bugfix on 0.4.0.2-alpha. Patch from Taylor Campbell.
340 o Minor bugfixes (out-of-memory handler):
341 - When purging the DNS cache because of an out-of-memory condition,
342 try purging just the older entries at first. Previously, we would
343 always purge the whole thing. Fixes bug 29617; bugfix
346 o Minor bugfixes (portability):
347 - Avoid crashing in our tor_vasprintf() implementation on systems
348 that define neither vasprintf() nor _vscprintf(). (This bug has
349 been here long enough that we question whether people are running
350 Tor on such systems, but we're applying the fix out of caution.)
351 Fixes bug 30561; bugfix on 0.2.8.2-alpha. Found and fixed by
354 o Minor bugfixes (shutdown, libevent, memory safety):
355 - Avoid use-after-free bugs when shutting down, by making sure that
356 we shut down libevent only after shutting down all of its users.
357 We believe these are harmless in practice, since they only occur
358 on the shutdown path, and do not involve any attacker-controlled
359 data. Fixes bug 30629; bugfix on 0.4.1.1-alpha.
361 o Minor bugfixes (static analysis):
362 - Fix several spurious Coverity warnings about the unit tests, to
363 lower our chances of missing real warnings in the future. Fixes
364 bug 30150; bugfix on 0.3.5.1-alpha and various other Tor versions.
367 - Specify torrc paths (with empty files) when launching tor in
368 integration tests; refrain from reading user and system torrcs.
369 Resolves issue 29702.
372 Changes in version 0.4.1.1-alpha - 2019-05-22
373 This is the first alpha in the 0.4.1.x series. It introduces
374 lightweight circuit padding to make some onion-service circuits harder
375 to distinguish, includes a new "authenticated SENDME" feature to make
376 certain denial-of-service attacks more difficult, and improves
377 performance in several areas.
379 o Major features (circuit padding):
380 - Onion service clients now add padding cells at the start of their
381 INTRODUCE and RENDEZVOUS circuits, to make those circuits' traffic
382 look more like general purpose Exit traffic. The overhead for this
383 is 2 extra cells in each direction for RENDEZVOUS circuits, and 1
384 extra upstream cell and 10 downstream cells for INTRODUCE
385 circuits. This feature is only enabled when also supported by the
386 circuit's middle node. (Clients may specify fixed middle nodes
387 with the MiddleNodes option, and may force-disable this feature
388 with the CircuitPadding option.) Closes ticket 28634.
390 o Major features (code organization):
391 - Tor now includes a generic publish-subscribe message-passing
392 subsystem that we can use to organize intermodule dependencies. We
393 hope to use this to reduce dependencies between modules that don't
394 need to be related, and to generally simplify our codebase. Closes
397 o Major features (controller protocol):
398 - Controller commands are now parsed using a generalized parsing
399 subsystem. Previously, each controller command was responsible for
400 parsing its own input, which led to strange inconsistencies.
403 o Major features (flow control):
404 - Implement authenticated SENDMEs as detailed in proposal 289. A
405 SENDME cell now includes the digest of the traffic that it
406 acknowledges, so that once an end point receives the SENDME, it
407 can confirm the other side's knowledge of the previous cells that
408 were sent, and prevent certain types of denial-of-service attacks.
409 This behavior is controlled by two new consensus parameters: see
410 the proposal for more details. Fixes ticket 26288.
412 o Major features (performance):
413 - Our node selection algorithm now excludes nodes in linear time.
414 Previously, the algorithm was quadratic, which could slow down
415 heavily used onion services. Closes ticket 30307.
417 o Major features (performance, RNG):
418 - Tor now constructs a fast secure pseudorandom number generator for
419 each thread, to use when performance is critical. This PRNG is
420 based on AES-CTR, using a buffering construction similar to
421 libottery and the (newer) OpenBSD arc4random() code. It
422 outperforms OpenSSL 1.1.1a's CSPRNG by roughly a factor of 100 for
423 small outputs. Although we believe it to be cryptographically
424 strong, we are only using it when necessary for performance.
425 Implements tickets 29023 and 29536.
427 o Major bugfixes (onion service v3):
428 - Fix an unreachable bug in which an introduction point could try to
429 send an INTRODUCE_ACK with a status code that Trunnel would refuse
430 to encode, leading the relay to assert(). We've consolidated the
431 ABI values into Trunnel now. Fixes bug 30454; bugfix
433 - Clients can now handle unknown status codes from INTRODUCE_ACK
434 cells. (The NACK behavior will stay the same.) This will allow us
435 to extend status codes in the future without breaking the normal
436 client behavior. Fixes another part of bug 30454; bugfix
439 o Minor features (circuit padding):
440 - We now use a fast PRNG when scheduling circuit padding. Part of
442 - Allow the padding machine designer to pick the edges of their
443 histogram instead of trying to compute them automatically using an
444 exponential formula. Resolves some undefined behavior in the case
445 of small histograms and allows greater flexibility on machine
446 design. Closes ticket 29298; bugfix on 0.4.0.1-alpha.
447 - Allow circuit padding machines to hold a circuit open until they
448 are done padding it. Closes ticket 28780.
450 o Minor features (compile-time modules):
451 - Add a "--list-modules" command to print a list of which compile-
452 time modules are enabled. Closes ticket 30452.
454 o Minor features (continuous integration):
455 - Remove sudo configuration lines from .travis.yml as they are no
456 longer needed with current Travis build environment. Resolves
458 - In Travis, show stem's tor log after failure. Closes ticket 30234.
460 o Minor features (controller):
461 - Add onion service version 3 support to the HSFETCH command.
462 Previously, only version 2 onion services were supported. Closes
463 ticket 25417. Patch by Neel Chauhan.
465 o Minor features (debugging):
466 - Introduce tor_assertf() and tor_assertf_nonfatal() to enable
467 logging of additional information during assert failure. Now we
468 can use format strings to include information for trouble
469 shooting. Resolves ticket 29662.
471 o Minor features (defense in depth):
472 - In smartlist_remove_keeporder(), set unused pointers to NULL, in
473 case a bug causes them to be used later. Closes ticket 30176.
474 Patch from Tobias Stoeckmann.
475 - Tor now uses a cryptographically strong PRNG even for decisions
476 that we do not believe are security-sensitive. Previously, for
477 performance reasons, we had used a trivially predictable linear
478 congruential generator algorithm for certain load-balancing and
479 statistical sampling decisions. Now we use our fast RNG in those
480 cases. Closes ticket 29542.
482 o Minor features (developer tools):
483 - Tor's "practracker" test script now checks for files and functions
484 that seem too long and complicated. Existing overlong functions
485 and files are accepted for now, but should eventually be
486 refactored. Closes ticket 29221.
487 - Add some scripts used for git maintenance to scripts/git. Closes
489 - Call practracker from pre-push and pre-commit git hooks to let
490 developers know if they made any code style violations. Closes
492 - Add a script to check that each header has a well-formed and
493 unique guard macro. Closes ticket 29756.
495 o Minor features (geoip):
496 - Update geoip and geoip6 to the May 13 2019 Maxmind GeoLite2
497 Country database. Closes ticket 30522.
499 o Minor features (HTTP tunnel):
500 - Return an informative web page when the HTTPTunnelPort is used as
501 an HTTP proxy. Closes ticket 27821, patch by "eighthave".
503 o Minor features (IPv6, v3 onion services):
504 - Make v3 onion services put IPv6 addresses in service descriptors.
505 Before this change, service descriptors only contained IPv4
506 addresses. Implements 26992.
508 o Minor features (modularity):
509 - The "--disable-module-dirauth" compile-time option now disables
510 even more dirauth-only code. Closes ticket 30345.
512 o Minor features (performance):
513 - Use OpenSSL's implementations of SHA3 when available (in OpenSSL
514 1.1.1 and later), since they tend to be faster than tiny-keccak.
517 o Minor features (testing):
518 - Tor's unit test code now contains helper functions to replace the
519 PRNG with a deterministic or reproducible version for testing.
520 Previously, various tests implemented this in various ways.
521 Implements ticket 29732.
522 - We now have a script, cov-test-determinism.sh, to identify places
523 where our unit test coverage has become nondeterministic. Closes
525 - Check that representative subsets of values of `int` and `unsigned
526 int` can be represented by `void *`. Resolves issue 29537.
528 o Minor bugfixes (bridge authority):
529 - Bridge authorities now set bridges as running or non-running when
530 about to dump their status to a file. Previously, they set bridges
531 as running in response to a GETINFO command, but those shouldn't
532 modify data structures. Fixes bug 24490; bugfix on 0.2.0.13-alpha.
533 Patch by Neel Chauhan.
535 o Minor bugfixes (channel padding statistics):
536 - Channel padding write totals and padding-enabled totals are now
537 counted properly in relay extrainfo descriptors. Fixes bug 29231;
538 bugfix on 0.3.1.1-alpha.
540 o Minor bugfixes (circuit padding):
541 - Add a "CircuitPadding" torrc option to disable circuit padding.
542 Fixes bug 28693; bugfix on 0.4.0.1-alpha.
543 - Allow circuit padding machines to specify that they do not
544 contribute much overhead, and provide consensus flags and torrc
545 options to force clients to only use these low overhead machines.
546 Fixes bug 29203; bugfix on 0.4.0.1-alpha.
547 - Provide a consensus parameter to fully disable circuit padding, to
548 be used in emergency network overload situations. Fixes bug 30173;
549 bugfix on 0.4.0.1-alpha.
550 - The circuit padding subsystem will no longer schedule padding if
551 dormant mode is enabled. Fixes bug 28636; bugfix on 0.4.0.1-alpha.
552 - Inspect a circuit-level cell queue before sending padding, to
553 avoid sending padding while too much data is already queued. Fixes
554 bug 29204; bugfix on 0.4.0.1-alpha.
555 - Avoid calling monotime_absolute_usec() in circuit padding machines
556 that do not use token removal or circuit RTT estimation. Fixes bug
557 29085; bugfix on 0.4.0.1-alpha.
559 o Minor bugfixes (compilation, unusual configurations):
560 - Avoid failures when building with the ALL_BUGS_ARE_FATAL option
561 due to missing declarations of abort(), and prevent other such
562 failures in the future. Fixes bug 30189; bugfix on 0.3.4.1-alpha.
564 o Minor bugfixes (controller protocol):
565 - Teach the controller parser to distinguish an object preceded by
566 an argument list from one without. Previously, it couldn't
567 distinguish an argument list from the first line of a multiline
568 object. Fixes bug 29984; bugfix on 0.2.3.8-alpha.
570 o Minor bugfixes (directory authority, ipv6):
571 - Directory authorities with IPv6 support now always mark themselves
572 as reachable via IPv6. Fixes bug 24338; bugfix on 0.2.4.1-alpha.
573 Patch by Neel Chauhan.
575 o Minor bugfixes (documentation):
576 - Improve the documentation for using MapAddress with ".exit". Fixes
577 bug 30109; bugfix on 0.1.0.1-rc.
578 - Improve the monotonic time module and function documentation to
579 explain what "monotonic" actually means, and document some results
580 that have surprised people. Fixes bug 29640; bugfix
582 - Use proper formatting when providing an example on quoting options
583 that contain whitespace. Fixes bug 29635; bugfix on 0.2.3.18-rc.
585 o Minor bugfixes (logging):
586 - Do not log a warning when running with an OpenSSL version other
587 than the one Tor was compiled with, if the two versions should be
588 compatible. Previously, we would warn whenever the version was
589 different. Fixes bug 30190; bugfix on 0.2.4.2-alpha.
590 - Warn operators when the MyFamily option is set but ContactInfo is
591 missing, as the latter should be set too. Fixes bug 25110; bugfix
594 o Minor bugfixes (memory leak):
595 - Avoid a minor memory leak that could occur on relays when failing
596 to create a "keys" directory. Fixes bug 30148; bugfix
599 o Minor bugfixes (onion services):
600 - Avoid a GCC 9.1.1 warning (and possible crash depending on libc
601 implemenation) when failing to load an onion service client
602 authorization file. Fixes bug 30475; bugfix on 0.3.5.1-alpha.
603 - When refusing to launch a controller's HSFETCH request because of
604 rate-limiting, respond to the controller with a new response,
605 "QUERY_RATE_LIMITED". Previously, we would log QUERY_NO_HSDIR for
606 this case. Fixes bug 28269; bugfix on 0.3.1.1-alpha. Patch by
608 - When relaunching a circuit to a rendezvous service, mark the
609 circuit as needing high-uptime routers as appropriate. Fixes bug
610 17357; bugfix on 0.1.0.1-rc. Patch by Neel Chauhan.
611 - Stop ignoring IPv6 link specifiers sent to v3 onion services.
612 (IPv6 support for v3 onion services is still incomplete: see
613 ticket 23493 for details.) Fixes bug 23588; bugfix on
614 0.3.2.1-alpha. Patch by Neel Chauhan.
616 o Minor bugfixes (onion services, performance):
617 - When building circuits to onion services, call tor_addr_parse()
618 less often. Previously, we called tor_addr_parse() in
619 circuit_is_acceptable() even if its output wasn't used. This
620 change should improve performance when building circuits. Fixes
621 bug 22210; bugfix on 0.2.8.12. Patch by Neel Chauhan.
623 o Minor bugfixes (performance):
624 - When checking whether a node is a bridge, use a fast check to make
625 sure that its identity is set. Previously, we used a constant-time
626 check, which is not necessary in this case. Fixes bug 30308;
627 bugfix on 0.3.5.1-alpha.
629 o Minor bugfixes (pluggable transports):
630 - Tor now sets TOR_PT_EXIT_ON_STDIN_CLOSE=1 for client transports as
631 well as servers. Fixes bug 25614; bugfix on 0.2.7.1-alpha.
633 o Minor bugfixes (probability distributions):
634 - Refactor and improve parts of the probability distribution code
635 that made Coverity complain. Fixes bug 29805; bugfix
638 o Minor bugfixes (python):
639 - Stop assuming that /usr/bin/python3 exists. For scripts that work
640 with python2, use /usr/bin/python. Otherwise, use /usr/bin/env
641 python3. Fixes bug 29913; bugfix on 0.2.5.3-alpha.
643 o Minor bugfixes (relay):
644 - When running as a relay, if IPv6Exit is set to 1 while ExitRelay
645 is auto, act as if ExitRelay is 1. Previously, we would ignore
646 IPv6Exit if ExitRelay was 0 or auto. Fixes bug 29613; bugfix on
647 0.3.5.1-alpha. Patch by Neel Chauhan.
649 o Minor bugfixes (stats):
650 - When ExtraInfoStatistics is 0, stop including bandwidth usage
651 statistics, GeoIPFile hashes, ServerTransportPlugin lines, and
652 bridge statistics by country in extra-info documents. Fixes bug
653 29018; bugfix on 0.2.4.1-alpha.
655 o Minor bugfixes (testing):
656 - Call setrlimit() to disable core dumps in test_bt_cl.c. Previously
657 we used `ulimit -c` in test_bt.sh, which violates POSIX shell
658 compatibility. Fixes bug 29061; bugfix on 0.3.5.1-alpha.
659 - Fix some incorrect code in the v3 onion service unit tests. Fixes
660 bug 29243; bugfix on 0.3.2.1-alpha.
661 - In the "routerkeys/*" tests, check the return values of mkdir()
662 for possible failures. Fixes bug 29939; bugfix on 0.2.7.2-alpha.
663 Found by Coverity as CID 1444254.
664 - Split test_utils_general() into several smaller test functions.
665 This makes it easier to perform resource deallocation on assert
666 failure, and fixes Coverity warnings CID 1444117 and CID 1444118.
667 Fixes bug 29823; bugfix on 0.2.9.1-alpha.
669 o Minor bugfixes (tor-resolve):
670 - Fix a memory leak in tor-resolve that could happen if Tor gave it
671 a malformed SOCKS response. (Memory leaks in tor-resolve don't
672 actually matter, but it's good to fix them anyway.) Fixes bug
673 30151; bugfix on 0.4.0.1-alpha.
675 o Code simplification and refactoring:
676 - Abstract out the low-level formatting of replies on the control
677 port. Implements ticket 30007.
678 - Add several assertions in an attempt to fix some Coverity
679 warnings. Closes ticket 30149.
680 - Introduce a connection_dir_buf_add() helper function that checks
681 for compress_state of dir_connection_t and automatically writes a
682 string to directory connection with or without compression.
683 Resolves issue 28816.
684 - Make the base32_decode() API return the number of bytes written,
685 for consistency with base64_decode(). Closes ticket 28913.
686 - Move most relay-only periodic events out of mainloop.c into the
687 relay subsystem. Closes ticket 30414.
688 - Refactor and encapsulate parts of the codebase that manipulate
689 crypt_path_t objects. Resolves issue 30236.
690 - Refactor several places in our code that Coverity incorrectly
691 believed might have memory leaks. Closes ticket 30147.
692 - Remove redundant return values in crypto_format, and the
693 associated return value checks elsewhere in the code. Make the
694 implementations in crypto_format consistent, and remove redundant
695 code. Resolves ticket 29660.
696 - Rename tor_mem_is_zero() to fast_mem_is_zero(), to emphasize that
697 it is not a constant-time function. Closes ticket 30309.
698 - Replace hs_desc_link_specifier_t with link_specifier_t, and remove
699 all hs_desc_link_specifier_t-specific code. Fixes bug 22781;
700 bugfix on 0.3.2.1-alpha.
701 - Simplify v3 onion service link specifier handling code. Fixes bug
702 23576; bugfix on 0.3.2.1-alpha.
703 - Split crypto_digest.c into NSS code, OpenSSL code, and shared
704 code. Resolves ticket 29108.
705 - Split control.c into several submodules, in preparation for
706 distributing its current responsibilities throughout the codebase.
708 - Start to move responsibility for knowing about periodic events to
709 the appropriate subsystems, so that the mainloop doesn't need to
710 know all the periodic events in the rest of the codebase.
711 Implements tickets 30293 and 30294.
714 - Document how to find git commits and tags for bug fixes in
715 CodingStandards.md. Update some file documentation. Closes
719 - Remove the linux-tor-prio.sh script from contrib/operator-tools
720 directory. Resolves issue 29434.
721 - Remove the obsolete OpenSUSE initscript. Resolves issue 30076.
722 - Remove the obsolete script at contrib/dist/tor.sh.in. Resolves
725 o Code simplification and refactoring (shell scripts):
726 - Clean up many of our shell scripts to fix shellcheck warnings.
727 These include autogen.sh (ticket 26069), test_keygen.sh (ticket
728 29062), test_switch_id.sh (ticket 29065), test_rebind.sh (ticket
729 29063), src/test/fuzz/minimize.sh (ticket 30079), test_rust.sh
730 (ticket 29064), torify (ticket 29070), asciidoc-helper.sh (29926),
731 fuzz_multi.sh (30077), fuzz_static_testcases.sh (ticket 29059),
732 nagios-check-tor-authority-cert (ticket 29071),
733 src/test/fuzz/fixup_filenames.sh (ticket 30078), test-network.sh
734 (ticket 29060), test_key_expiration.sh (ticket 30002),
735 zero_length_keys.sh (ticket 29068), and test_workqueue_*.sh
739 - In "make test-network-all", test IPv6-only v3 single onion
740 services, using the chutney network single-onion-v23-ipv6-md.
744 Changes in version 0.4.0.5 - 2019-05-02
745 This is the first stable release in the 0.4.0.x series. It contains
746 improvements for power management and bootstrap reporting, as well as
747 preliminary backend support for circuit padding to prevent some kinds
748 of traffic analysis. It also continues our work in refactoring Tor for
749 long-term maintainability.
751 Per our support policy, we will support the 0.4.0.x series for nine
752 months, or until three months after the release of a stable 0.4.1.x:
753 whichever is longer. If you need longer-term support, please stick
754 with 0.3.5.x, which will we plan to support until Feb 2022.
756 Below are the changes since 0.4.0.4-rc. For a complete list of changes
757 since 0.3.5.7, see the ReleaseNotes file.
759 o Minor features (continuous integration):
760 - In Travis, tell timelimit to use stem's backtrace signals, and
761 launch python directly from timelimit, so python receives the
762 signals from timelimit, rather than make. Closes ticket 30117.
764 o Minor features (diagnostic):
765 - Add more diagnostic log messages in an attempt to solve the issue
766 of NUL bytes appearing in a microdescriptor cache. Related to
769 o Minor features (testing):
770 - Use the approx_time() function when setting the "Expires" header
771 in directory replies, to make them more testable. Needed for
774 o Minor bugfixes (rust):
775 - Abort on panic in all build profiles, instead of potentially
776 unwinding into C code. Fixes bug 27199; bugfix on 0.3.3.1-alpha.
778 o Minor bugfixes (shellcheck):
779 - Look for scripts in their correct locations during "make
780 shellcheck". Previously we had looked in the wrong place during
781 out-of-tree builds. Fixes bug 30263; bugfix on 0.4.0.1-alpha.
783 o Minor bugfixes (testing):
784 - Check the time in the "Expires" header using approx_time(). Fixes
785 bug 30001; bugfix on 0.4.0.4-rc.
787 o Minor bugfixes (UI):
788 - Lower log level of unlink() errors during bootstrap. Fixes bug
789 29930; bugfix on 0.4.0.1-alpha.
792 Changes in version 0.4.0.4-rc - 2019-04-11
793 Tor 0.4.0.4-rc is the first release candidate in its series; it fixes
794 several bugs from earlier versions, including some that had affected
795 stability, and one that prevented relays from working with NSS.
797 o Major bugfixes (NSS, relay):
798 - When running with NSS, disable TLS 1.2 ciphersuites that use
799 SHA384 for their PRF. Due to an NSS bug, the TLS key exporters for
800 these ciphersuites don't work -- which caused relays to fail to
801 handshake with one another when these ciphersuites were enabled.
802 Fixes bug 29241; bugfix on 0.3.5.1-alpha.
804 o Minor features (bandwidth authority):
805 - Make bandwidth authorities ignore relays that are reported in the
806 bandwidth file with the flag "vote=0". This change allows us to
807 report unmeasured relays for diagnostic reasons without including
808 their bandwidth in the bandwidth authorities' vote. Closes
810 - When a directory authority is using a bandwidth file to obtain the
811 bandwidth values that will be included in the next vote, serve
812 this bandwidth file at /tor/status-vote/next/bandwidth. Closes
815 o Minor features (circuit padding):
816 - Stop warning about undefined behavior in the probability
817 distribution tests. Float division by zero may technically be
818 undefined behavior in C, but it's well defined in IEEE 754.
819 Partial backport of 29298. Closes ticket 29527; bugfix
822 o Minor features (continuous integration):
823 - On Travis Rust builds, cleanup Rust registry and refrain from
824 caching the "target/" directory to speed up builds. Resolves
827 o Minor features (dormant mode):
828 - Add a DormantCanceledByStartup option to tell Tor that it should
829 treat a startup event as cancelling any previous dormant state.
830 Integrators should use this option with caution: it should only be
831 used if Tor is being started because of something that the user
832 did, and not if Tor is being automatically started in the
833 background. Closes ticket 29357.
835 o Minor features (geoip):
836 - Update geoip and geoip6 to the April 2 2019 Maxmind GeoLite2
837 Country database. Closes ticket 29992.
839 o Minor features (NSS, diagnostic):
840 - Try to log an error from NSS (if there is any) and a more useful
841 description of our situation if we are using NSS and a call to
842 SSL_ExportKeyingMaterial() fails. Diagnostic for ticket 29241.
844 o Minor bugfixes (security):
845 - Fix a potential double free bug when reading huge bandwidth files.
846 The issue is not exploitable in the current Tor network because
847 the vulnerable code is only reached when directory authorities
848 read bandwidth files, but bandwidth files come from a trusted
849 source (usually the authorities themselves). Furthermore, the
850 issue is only exploitable in rare (non-POSIX) 32-bit architectures,
851 which are not used by any of the current authorities. Fixes bug
852 30040; bugfix on 0.3.5.1-alpha. Bug found and fixed by
854 - Verify in more places that we are not about to create a buffer
855 with more than INT_MAX bytes, to avoid possible OOB access in the
856 event of bugs. Fixes bug 30041; bugfix on 0.2.0.16. Found and
857 fixed by Tobias Stoeckmann.
859 o Minor bugfix (continuous integration):
860 - Reset coverage state on disk after Travis CI has finished. This
861 should prevent future coverage merge errors from causing the test
862 suite for the "process" subsystem to fail. The process subsystem
863 was introduced in 0.4.0.1-alpha. Fixes bug 29036; bugfix
865 - Terminate test-stem if it takes more than 9.5 minutes to run.
866 (Travis terminates the job after 10 minutes of no output.)
867 Diagnostic for 29437. Fixes bug 30011; bugfix on 0.3.5.4-alpha.
869 o Minor bugfixes (bootstrap reporting):
870 - During bootstrap reporting, correctly distinguish pluggable
871 transports from plain proxies. Fixes bug 28925; bugfix
874 o Minor bugfixes (C correctness):
875 - Fix an unlikely memory leak in consensus_diff_apply(). Fixes bug
876 29824; bugfix on 0.3.1.1-alpha. This is Coverity warning
879 o Minor bugfixes (circuitpadding testing):
880 - Minor tweaks to avoid rare test failures related to timers and
881 monotonic time. Fixes bug 29500; bugfix on 0.4.0.1-alpha.
883 o Minor bugfixes (directory authorities):
884 - Actually include the bandwidth-file-digest line in directory
885 authority votes. Fixes bug 29959; bugfix on 0.4.0.2-alpha.
887 o Minor bugfixes (logging):
888 - On Windows, when errors cause us to reload a consensus from disk,
889 tell the user that we are retrying at log level "notice".
890 Previously we only logged this information at "info", which was
891 confusing because the errors themselves were logged at "warning".
892 Improves previous fix for 28614. Fixes bug 30004; bugfix
895 o Minor bugfixes (pluggable transports):
896 - Restore old behavior when it comes to discovering the path of a
897 given Pluggable Transport executable file. A change in
898 0.4.0.1-alpha had broken this behavior on paths containing a
899 space. Fixes bug 29874; bugfix on 0.4.0.1-alpha.
901 o Minor bugfixes (testing):
902 - Backport the 0.3.4 src/test/test-network.sh to 0.2.9. We need a
903 recent test-network.sh to use new chutney features in CI. Fixes
904 bug 29703; bugfix on 0.2.9.1-alpha.
905 - Fix a test failure on Windows caused by an unexpected "BUG"
906 warning in our tests for tor_gmtime_r(-1). Fixes bug 29922; bugfix
909 o Minor bugfixes (TLS protocol):
910 - When classifying a client's selection of TLS ciphers, if the
911 client ciphers are not yet available, do not cache the result.
912 Previously, we had cached the unavailability of the cipher list
913 and never looked again, which in turn led us to assume that the
914 client only supported the ancient V1 link protocol. This, in turn,
915 was causing Stem integration tests to stall in some cases. Fixes
916 bug 30021; bugfix on 0.2.4.8-alpha.
918 o Code simplification and refactoring:
919 - Introduce a connection_dir_buf_add() helper function that detects
920 whether compression is in use, and adds a string accordingly.
921 Resolves issue 28816.
922 - Refactor handle_get_next_bandwidth() to use
923 connection_dir_buf_add(). Implements ticket 29897.
926 - Clarify that Tor performs stream isolation among *Port listeners
927 by default. Resolves issue 29121.
930 Changes in version 0.4.0.3-alpha - 2019-03-22
931 Tor 0.4.0.3-alpha is the third in its series; it fixes several small
932 bugs from earlier versions.
934 o Minor features (address selection):
935 - Treat the subnet 100.64.0.0/10 as public for some purposes;
936 private for others. This subnet is the RFC 6598 (Carrier Grade
937 NAT) IP range, and is deployed by many ISPs as an alternative to
938 RFC 1918 that does not break existing internal networks. Tor now
939 blocks SOCKS and control ports on these addresses and warns users
940 if client ports or ExtORPorts are listening on a RFC 6598 address.
941 Closes ticket 28525. Patch by Neel Chauhan.
943 o Minor features (geoip):
944 - Update geoip and geoip6 to the March 4 2019 Maxmind GeoLite2
945 Country database. Closes ticket 29666.
947 o Minor bugfixes (circuitpadding):
948 - Inspect the circuit-level cell queue before sending padding, to
949 avoid sending padding when too much data is queued. Fixes bug
950 29204; bugfix on 0.4.0.1-alpha.
952 o Minor bugfixes (logging):
953 - Correct a misleading error message when IPv4Only or IPv6Only is
954 used but the resolved address can not be interpreted as an address
955 of the specified IP version. Fixes bug 13221; bugfix on
956 0.2.3.9-alpha. Patch from Kris Katterjohn.
957 - Log the correct port number for listening sockets when "auto" is
958 used to let Tor pick the port number. Previously, port 0 was
959 logged instead of the actual port number. Fixes bug 29144; bugfix
960 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
961 - Stop logging a BUG() warning when Tor is waiting for exit
962 descriptors. Fixes bug 28656; bugfix on 0.3.5.1-alpha.
964 o Minor bugfixes (memory management):
965 - Refactor the shared random state's memory management so that it
966 actually takes ownership of the shared random value pointers.
967 Fixes bug 29706; bugfix on 0.2.9.1-alpha.
969 o Minor bugfixes (memory management, testing):
970 - Stop leaking parts of the shared random state in the shared-random
971 unit tests. Fixes bug 29599; bugfix on 0.2.9.1-alpha.
973 o Minor bugfixes (pluggable transports):
974 - Fix an assertion failure crash bug when a pluggable transport is
975 terminated during the bootstrap phase. Fixes bug 29562; bugfix
978 o Minor bugfixes (Rust, protover):
979 - Add a missing "Padding" value to the Rust implementation of
980 protover. Fixes bug 29631; bugfix on 0.4.0.1-alpha.
982 o Minor bugfixes (single onion services):
983 - Allow connections to single onion services to remain idle without
984 being disconnected. Previously, relays acting as rendezvous points
985 for single onion services were mistakenly closing idle rendezvous
986 circuits after 60 seconds, thinking that they were unused
987 directory-fetching circuits that had served their purpose. Fixes
988 bug 29665; bugfix on 0.2.1.26.
990 o Minor bugfixes (stats):
991 - When ExtraInfoStatistics is 0, stop including PaddingStatistics in
992 relay and bridge extra-info documents. Fixes bug 29017; bugfix
995 o Minor bugfixes (testing):
996 - Downgrade some LOG_ERR messages in the address/* tests to
997 warnings. The LOG_ERR messages were occurring when we had no
998 configured network. We were failing the unit tests, because we
999 backported 28668 to 0.3.5.8, but did not backport 29530. Fixes bug
1000 29530; bugfix on 0.3.5.8.
1001 - Fix our gcov wrapper script to look for object files at the
1002 correct locations. Fixes bug 29435; bugfix on 0.3.5.1-alpha.
1003 - Decrease the false positive rate of stochastic probability
1004 distribution tests. Fixes bug 29693; bugfix on 0.4.0.1-alpha.
1006 o Minor bugfixes (Windows, CI):
1007 - Skip the Appveyor 32-bit Windows Server 2016 job, and 64-bit
1008 Windows Server 2012 R2 job. The remaining 2 jobs still provide
1009 coverage of 64/32-bit, and Windows Server 2016/2012 R2. Also set
1010 fast_finish, so failed jobs terminate the build immediately. Fixes
1011 bug 29601; bugfix on 0.3.5.4-alpha.
1014 Changes in version 0.3.5.8 - 2019-02-21
1015 Tor 0.3.5.8 backports several fixes from later releases, including fixes
1016 for an annoying SOCKS-parsing bug that affected users in earlier 0.3.5.x
1019 It also includes a fix for a medium-severity security bug affecting Tor
1020 0.3.2.1-alpha and later. All Tor instances running an affected release
1021 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1023 o Major bugfixes (cell scheduler, KIST, security):
1024 - Make KIST consider the outbuf length when computing what it can
1025 put in the outbuf. Previously, KIST acted as though the outbuf
1026 were empty, which could lead to the outbuf becoming too full. It
1027 is possible that an attacker could exploit this bug to cause a Tor
1028 client or relay to run out of memory and crash. Fixes bug 29168;
1029 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1030 TROVE-2019-001 and CVE-2019-8955.
1032 o Major bugfixes (networking, backport from 0.4.0.2-alpha):
1033 - Gracefully handle empty username/password fields in SOCKS5
1034 username/password auth message and allow SOCKS5 handshake to
1035 continue. Previously, we had rejected these handshakes, breaking
1036 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
1038 o Minor features (compilation, backport from 0.4.0.2-alpha):
1039 - Compile correctly when OpenSSL is built with engine support
1040 disabled, or with deprecated APIs disabled. Closes ticket 29026.
1041 Patches from "Mangix".
1043 o Minor features (geoip):
1044 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1045 Country database. Closes ticket 29478.
1047 o Minor features (testing, backport from 0.4.0.2-alpha):
1048 - Treat all unexpected ERR and BUG messages as test failures. Closes
1051 o Minor bugfixes (onion service v3, client, backport from 0.4.0.1-alpha):
1052 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1053 connection waiting for a descriptor that we actually have in the
1054 cache. It turns out that this can actually happen, though it is
1055 rare. Now, tor will recover and retry the descriptor. Fixes bug
1056 28669; bugfix on 0.3.2.4-alpha.
1058 o Minor bugfixes (IPv6, backport from 0.4.0.1-alpha):
1059 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1060 IPv6 socket was bound using an address family of AF_INET instead
1061 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1064 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1065 - Update Cargo.lock file to match the version made by the latest
1066 version of Rust, so that "make distcheck" will pass again. Fixes
1067 bug 29244; bugfix on 0.3.3.4-alpha.
1069 o Minor bugfixes (client, clock skew, backport from 0.4.0.1-alpha):
1070 - Select guards even if the consensus has expired, as long as the
1071 consensus is still reasonably live. Fixes bug 24661; bugfix
1074 o Minor bugfixes (compilation, backport from 0.4.0.1-alpha):
1075 - Compile correctly on OpenBSD; previously, we were missing some
1076 headers required in order to detect it properly. Fixes bug 28938;
1077 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1079 o Minor bugfixes (documentation, backport from 0.4.0.2-alpha):
1080 - Describe the contents of the v3 onion service client authorization
1081 files correctly: They hold public keys, not private keys. Fixes
1082 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1084 o Minor bugfixes (logging, backport from 0.4.0.1-alpha):
1085 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1086 link protocol versions when logging incoming/outgoing connection
1087 counts. Tor no longer skips version 5, and we won't have to
1088 remember to update this function when new link protocol version is
1089 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1091 o Minor bugfixes (logging, backport from 0.4.0.2-alpha):
1092 - Log more information at "warning" level when unable to read a
1093 private key; log more information at "info" level when unable to
1094 read a public key. We had warnings here before, but they were lost
1095 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1097 o Minor bugfixes (misc, backport from 0.4.0.2-alpha):
1098 - The amount of total available physical memory is now determined
1099 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1100 when it is defined and a 64-bit variant is not available. Fixes
1101 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1103 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1104 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1105 than one private key for a hidden service. Fixes bug 29040; bugfix
1107 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1108 "debug" level. Tor used to log it as a warning, which caused very
1109 long log lines to appear for some users. Fixes bug 29135; bugfix
1111 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1112 as a warning. Instead, log it as a protocol warning, because there
1113 is nothing that relay operators can do to fix it. Fixes bug 29029;
1114 bugfix on 0.2.5.7-rc.
1116 o Minor bugfixes (tests, directory clients, backport from 0.4.0.1-alpha):
1117 - Mark outdated dirservers when Tor only has a reasonably live
1118 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1120 o Minor bugfixes (tests, backport from 0.4.0.2-alpha):
1121 - Detect and suppress "bug" warnings from the util/time test on
1122 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1123 - Do not log an error-level message if we fail to find an IPv6
1124 network interface from the unit tests. Fixes bug 29160; bugfix
1127 o Minor bugfixes (usability, backport from 0.4.0.1-alpha):
1128 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1129 Some users took this phrasing to mean that the mentioned guard was
1130 under their control or responsibility, which it is not. Fixes bug
1131 28895; bugfix on Tor 0.3.0.1-alpha.
1134 Changes in version 0.3.4.11 - 2019-02-21
1135 Tor 0.3.4.11 is the third stable release in its series. It includes
1136 a fix for a medium-severity security bug affecting Tor 0.3.2.1-alpha and
1137 later. All Tor instances running an affected release should upgrade to
1138 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1140 o Major bugfixes (cell scheduler, KIST, security):
1141 - Make KIST consider the outbuf length when computing what it can
1142 put in the outbuf. Previously, KIST acted as though the outbuf
1143 were empty, which could lead to the outbuf becoming too full. It
1144 is possible that an attacker could exploit this bug to cause a Tor
1145 client or relay to run out of memory and crash. Fixes bug 29168;
1146 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1147 TROVE-2019-001 and CVE-2019-8955.
1149 o Minor features (geoip):
1150 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1151 Country database. Closes ticket 29478.
1153 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1154 - Update Cargo.lock file to match the version made by the latest
1155 version of Rust, so that "make distcheck" will pass again. Fixes
1156 bug 29244; bugfix on 0.3.3.4-alpha.
1158 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1159 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1160 as a warning. Instead, log it as a protocol warning, because there
1161 is nothing that relay operators can do to fix it. Fixes bug 29029;
1162 bugfix on 0.2.5.7-rc.
1165 Changes in version 0.3.3.12 - 2019-02-21
1166 Tor 0.3.3.12 fixes a medium-severity security bug affecting Tor
1167 0.3.2.1-alpha and later. All Tor instances running an affected release
1168 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1170 This release marks the end of support for the Tor 0.3.3.x series. We
1171 recommend that users switch to either the Tor 0.3.4 series (supported
1172 until at least 10 June 2019), or the Tor 0.3.5 series, which will
1173 receive long-term support until at least 1 Feb 2022.
1175 o Major bugfixes (cell scheduler, KIST, security):
1176 - Make KIST consider the outbuf length when computing what it can
1177 put in the outbuf. Previously, KIST acted as though the outbuf
1178 were empty, which could lead to the outbuf becoming too full. It
1179 is possible that an attacker could exploit this bug to cause a Tor
1180 client or relay to run out of memory and crash. Fixes bug 29168;
1181 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1182 TROVE-2019-001 and CVE-2019-8955.
1184 o Minor features (geoip):
1185 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1186 Country database. Closes ticket 29478.
1188 o Minor bugfixes (build, compatibility, rust, backport from 0.4.0.2-alpha):
1189 - Update Cargo.lock file to match the version made by the latest
1190 version of Rust, so that "make distcheck" will pass again. Fixes
1191 bug 29244; bugfix on 0.3.3.4-alpha.
1193 o Minor bugfixes (onion services, backport from 0.4.0.2-alpha):
1194 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1195 as a warning. Instead, log it as a protocol warning, because there
1196 is nothing that relay operators can do to fix it. Fixes bug 29029;
1197 bugfix on 0.2.5.7-rc.
1200 Changes in version 0.4.0.2-alpha - 2019-02-21
1201 Tor 0.4.0.2-alpha is the second alpha in its series; it fixes several
1202 bugs from earlier versions, including several that had broken
1203 backward compatibility.
1205 It also includes a fix for a medium-severity security bug affecting Tor
1206 0.3.2.1-alpha and later. All Tor instances running an affected release
1207 should upgrade to 0.3.3.12, 0.3.4.11, 0.3.5.8, or 0.4.0.2-alpha.
1209 o Major bugfixes (cell scheduler, KIST, security):
1210 - Make KIST consider the outbuf length when computing what it can
1211 put in the outbuf. Previously, KIST acted as though the outbuf
1212 were empty, which could lead to the outbuf becoming too full. It
1213 is possible that an attacker could exploit this bug to cause a Tor
1214 client or relay to run out of memory and crash. Fixes bug 29168;
1215 bugfix on 0.3.2.1-alpha. This issue is also being tracked as
1216 TROVE-2019-001 and CVE-2019-8955.
1218 o Major bugfixes (networking):
1219 - Gracefully handle empty username/password fields in SOCKS5
1220 username/password auth messsage and allow SOCKS5 handshake to
1221 continue. Previously, we had rejected these handshakes, breaking
1222 certain applications. Fixes bug 29175; bugfix on 0.3.5.1-alpha.
1224 o Major bugfixes (windows, startup):
1225 - When reading a consensus file from disk, detect whether it was
1226 written in text mode, and re-read it in text mode if so. Always
1227 write consensus files in binary mode so that we can map them into
1228 memory later. Previously, we had written in text mode, which
1229 confused us when we tried to map the file on windows. Fixes bug
1230 28614; bugfix on 0.4.0.1-alpha.
1232 o Minor features (compilation):
1233 - Compile correctly when OpenSSL is built with engine support
1234 disabled, or with deprecated APIs disabled. Closes ticket 29026.
1235 Patches from "Mangix".
1237 o Minor features (developer tooling):
1238 - Check that bugfix versions in changes files look like Tor versions
1239 from the versions spec. Warn when bugfixes claim to be on a future
1240 release. Closes ticket 27761.
1241 - Provide a git pre-commit hook that disallows committing if we have
1242 any failures in our code and changelog formatting checks. It is
1243 now available in scripts/maint/pre-commit.git-hook. Implements
1246 o Minor features (directory authority):
1247 - When a directory authority is using a bandwidth file to obtain
1248 bandwidth values, include the digest of that file in the vote.
1249 Closes ticket 26698.
1251 o Minor features (geoip):
1252 - Update geoip and geoip6 to the February 5 2019 Maxmind GeoLite2
1253 Country database. Closes ticket 29478.
1255 o Minor features (testing):
1256 - Treat all unexpected ERR and BUG messages as test failures. Closes
1259 o Minor bugfixes (build, compatibility, rust):
1260 - Update Cargo.lock file to match the version made by the latest
1261 version of Rust, so that "make distcheck" will pass again. Fixes
1262 bug 29244; bugfix on 0.3.3.4-alpha.
1264 o Minor bugfixes (compilation):
1265 - Fix compilation warnings in test_circuitpadding.c. Fixes bug
1266 29169; bugfix on 0.4.0.1-alpha.
1267 - Silence a compiler warning in test-memwipe.c on OpenBSD. Fixes bug
1268 29145; bugfix on 0.2.9.3-alpha. Patch from Kris Katterjohn.
1270 o Minor bugfixes (documentation):
1271 - Describe the contents of the v3 onion service client authorization
1272 files correctly: They hold public keys, not private keys. Fixes
1273 bug 28979; bugfix on 0.3.5.1-alpha. Spotted by "Felixix".
1275 o Minor bugfixes (linux seccomp sandbox):
1276 - Fix startup crash when experimental sandbox support is enabled.
1277 Fixes bug 29150; bugfix on 0.4.0.1-alpha. Patch by Peter Gerber.
1279 o Minor bugfixes (logging):
1280 - Avoid logging that we are relaxing a circuit timeout when that
1281 timeout is fixed. Fixes bug 28698; bugfix on 0.2.4.7-alpha.
1282 - Log more information at "warning" level when unable to read a
1283 private key; log more information at "info" level when unable to
1284 read a public key. We had warnings here before, but they were lost
1285 during our NSS work. Fixes bug 29042; bugfix on 0.3.5.1-alpha.
1287 o Minor bugfixes (misc):
1288 - The amount of total available physical memory is now determined
1289 using the sysctl identifier HW_PHYSMEM (rather than HW_USERMEM)
1290 when it is defined and a 64-bit variant is not available. Fixes
1291 bug 28981; bugfix on 0.2.5.4-alpha. Patch from Kris Katterjohn.
1293 o Minor bugfixes (onion services):
1294 - Avoid crashing if ClientOnionAuthDir (incorrectly) contains more
1295 than one private key for a hidden service. Fixes bug 29040; bugfix
1297 - In hs_cache_store_as_client() log an HSDesc we failed to parse at
1298 "debug" level. Tor used to log it as a warning, which caused very
1299 long log lines to appear for some users. Fixes bug 29135; bugfix
1301 - Stop logging "Tried to establish rendezvous on non-OR circuit..."
1302 as a warning. Instead, log it as a protocol warning, because there
1303 is nothing that relay operators can do to fix it. Fixes bug 29029;
1304 bugfix on 0.2.5.7-rc.
1306 o Minor bugfixes (scheduler):
1307 - When re-adding channels to the pending list, check the correct
1308 channel's sched_heap_idx. This issue has had no effect in mainline
1309 Tor, but could have led to bugs down the road in improved versions
1310 of our circuit scheduling code. Fixes bug 29508; bugfix
1313 o Minor bugfixes (tests):
1314 - Fix intermittent failures on an adaptive padding test. Fixes one
1315 case of bug 29122; bugfix on 0.4.0.1-alpha.
1316 - Disable an unstable circuit-padding test that was failing
1317 intermittently because of an ill-defined small histogram. Such
1318 histograms will be allowed again after 29298 is implemented. Fixes
1319 a second case of bug 29122; bugfix on 0.4.0.1-alpha.
1320 - Detect and suppress "bug" warnings from the util/time test on
1321 Windows. Fixes bug 29161; bugfix on 0.2.9.3-alpha.
1322 - Do not log an error-level message if we fail to find an IPv6
1323 network interface from the unit tests. Fixes bug 29160; bugfix
1327 - In the manpage entry describing MapAddress torrc setting, use
1328 example IP addresses from ranges specified for use in documentation
1329 by RFC 5737. Resolves issue 28623.
1332 - Remove the old check-tor script. Resolves issue 29072.
1335 Changes in version 0.4.0.1-alpha - 2019-01-18
1336 Tor 0.4.0.1-alpha is the first release in the new 0.4.0.x series. It
1337 introduces improved features for power and bandwidth conservation,
1338 more accurate reporting of bootstrap progress for user interfaces, and
1339 an experimental backend for an exciting new adaptive padding feature.
1340 There is also the usual assortment of bugfixes and minor features, all
1343 o Major features (battery management, client, dormant mode):
1344 - When Tor is running as a client, and it is unused for a long time,
1345 it can now enter a "dormant" state. When Tor is dormant, it avoids
1346 network and CPU activity until it is reawoken either by a user
1347 request or by a controller command. For more information, see the
1348 configuration options starting with "Dormant". Implements tickets
1350 - The client's memory of whether it is "dormant", and how long it
1351 has spent idle, persists across invocations. Implements
1353 - There is a DormantOnFirstStartup option that integrators can use
1354 if they expect that in many cases, Tor will be installed but
1357 o Major features (bootstrap reporting):
1358 - When reporting bootstrap progress, report the first connection
1359 uniformly, regardless of whether it's a connection for building
1360 application circuits. This allows finer-grained reporting of early
1361 progress than previously possible, with the improvements of ticket
1362 27169. Closes tickets 27167 and 27103. Addresses ticket 27308.
1363 - When reporting bootstrap progress, treat connecting to a proxy or
1364 pluggable transport as separate from having successfully used that
1365 proxy or pluggable transport to connect to a relay. Closes tickets
1368 o Major features (circuit padding):
1369 - Implement preliminary support for the circuit padding portion of
1370 Proposal 254. The implementation supports Adaptive Padding (aka
1371 WTF-PAD) state machines for use between experimental clients and
1372 relays. Support is also provided for APE-style state machines that
1373 use probability distributions instead of histograms to specify
1374 inter-packet delay. At the moment, Tor does not provide any
1375 padding state machines that are used in normal operation: for now,
1376 this feature exists solely for experimentation. Closes
1379 o Major features (refactoring):
1380 - Tor now uses an explicit list of its own subsystems when
1381 initializing and shutting down. Previously, these systems were
1382 managed implicitly in various places throughout the codebase.
1383 (There may still be some subsystems using the old system.) Closes
1386 o Minor features (bootstrap reporting):
1387 - When reporting bootstrap progress, stop distinguishing between
1388 situations where only internal paths are available and situations
1389 where external paths are available. Previously, Tor would often
1390 erroneously report that it had only internal paths. Closes
1393 o Minor features (continuous integration):
1394 - Log Python version during each Travis CI job. Resolves
1397 o Minor features (controller):
1398 - Add a DROPOWNERSHIP command to undo the effects of TAKEOWNERSHIP.
1399 Implements ticket 28843.
1401 o Minor features (developer tooling):
1402 - Provide a git hook script to prevent "fixup!" and "squash!"
1403 commits from ending up in the master branch, as scripts/main/pre-
1404 push.git-hook. Closes ticket 27993.
1406 o Minor features (directory authority):
1407 - Directory authorities support a new consensus algorithm, under
1408 which the family lines in microdescriptors are encoded in a
1409 canonical form. This change makes family lines more compressible
1410 in transit, and on the client. Closes ticket 28266; implements
1413 o Minor features (directory authority, relay):
1414 - Authorities now vote on a "StaleDesc" flag to indicate that a
1415 relay's descriptor is so old that the relay should upload again
1416 soon. Relays treat this flag as a signal to upload a new
1417 descriptor. This flag will eventually let us remove the
1418 'published' date from routerstatus entries, and make our consensus
1419 diffs much smaller. Closes ticket 26770; implements proposal 293.
1421 o Minor features (fallback directory mirrors):
1422 - Update the fallback whitelist based on operator opt-ins and opt-
1423 outs. Closes ticket 24805, patch by Phoul.
1425 o Minor features (FreeBSD):
1426 - On FreeBSD-based systems, warn relay operators if the
1427 "net.inet.ip.random_id" sysctl (IP ID randomization) is disabled.
1428 Closes ticket 28518.
1430 o Minor features (HTTP standards compliance):
1431 - Stop sending the header "Content-type: application/octet-stream"
1432 along with transparently compressed documents: this confused
1433 browsers. Closes ticket 28100.
1435 o Minor features (IPv6):
1436 - We add an option ClientAutoIPv6ORPort, to make clients randomly
1437 prefer a node's IPv4 or IPv6 ORPort. The random preference is set
1438 every time a node is loaded from a new consensus or bridge config.
1439 We expect that this option will enable clients to bootstrap more
1440 quickly without having to determine whether they support IPv4,
1441 IPv6, or both. Closes ticket 27490. Patch by Neel Chauhan.
1442 - When using addrs_in_same_network_family(), avoid choosing circuit
1443 paths that pass through the same IPv6 subnet more than once.
1444 Previously, we only checked IPv4 subnets. Closes ticket 24393.
1445 Patch by Neel Chauhan.
1447 o Minor features (log messages):
1448 - Improve log message in v3 onion services that could print out
1449 negative revision counters. Closes ticket 27707. Patch
1452 o Minor features (memory usage):
1453 - Save memory by storing microdescriptor family lists with a more
1454 compact representation. Closes ticket 27359.
1455 - Tor clients now use mmap() to read consensus files from disk, so
1456 that they no longer need keep the full text of a consensus in
1457 memory when parsing it or applying a diff. Closes ticket 27244.
1459 o Minor features (parsing):
1460 - Directory authorities now validate that router descriptors and
1461 ExtraInfo documents are in a valid subset of UTF-8, and reject
1462 them if they are not. Closes ticket 27367.
1464 o Minor features (performance):
1465 - Cache the results of summarize_protocol_flags(), so that we don't
1466 have to parse the same protocol-versions string over and over.
1467 This should save us a huge number of malloc calls on startup, and
1468 may reduce memory fragmentation with some allocators. Closes
1470 - Remove a needless memset() call from get_token_arguments, thereby
1471 speeding up the tokenization of directory objects by about 20%.
1472 Closes ticket 28852.
1473 - Replace parse_short_policy() with a faster implementation, to
1474 improve microdescriptor parsing time. Closes ticket 28853.
1475 - Speed up directory parsing a little by avoiding use of the non-
1476 inlined strcmp_len() function. Closes ticket 28856.
1477 - Speed up microdescriptor parsing by about 30%, to help improve
1478 startup time. Closes ticket 28839.
1480 o Minor features (pluggable transports):
1481 - Add support for emitting STATUS updates to Tor's control port from
1482 a pluggable transport process. Closes ticket 28846.
1483 - Add support for logging to Tor's logging subsystem from a
1484 pluggable transport process. Closes ticket 28180.
1486 o Minor features (process management):
1487 - Add a new process API for handling child processes. This new API
1488 allows Tor to have bi-directional communication with child
1489 processes on both Unix and Windows. Closes ticket 28179.
1490 - Use the subsystem manager to initialize and shut down the process
1491 module. Closes ticket 28847.
1493 o Minor features (relay):
1494 - When listing relay families, list them in canonical form including
1495 the relay's own identity, and try to give a more useful set of
1496 warnings. Part of ticket 28266 and proposal 298.
1498 o Minor features (required protocols):
1499 - Before exiting because of a missing required protocol, Tor will
1500 now check the publication time of the consensus, and not exit
1501 unless the consensus is newer than the Tor program's own release
1502 date. Previously, Tor would not check the consensus publication
1503 time, and so might exit because of a missing protocol that might
1504 no longer be required in a current consensus. Implements proposal
1505 297; closes ticket 27735.
1507 o Minor features (testing):
1508 - Allow a HeartbeatPeriod of less than 30 minutes in testing Tor
1509 networks. Closes ticket 28840. Patch by Rob Jansen.
1511 o Minor bugfixes (client, clock skew):
1512 - Bootstrap successfully even when Tor's clock is behind the clocks
1513 on the authorities. Fixes bug 28591; bugfix on 0.2.0.9-alpha.
1514 - Select guards even if the consensus has expired, as long as the
1515 consensus is still reasonably live. Fixes bug 24661; bugfix
1518 o Minor bugfixes (compilation):
1519 - Compile correctly on OpenBSD; previously, we were missing some
1520 headers required in order to detect it properly. Fixes bug 28938;
1521 bugfix on 0.3.5.1-alpha. Patch from Kris Katterjohn.
1523 o Minor bugfixes (directory clients):
1524 - Mark outdated dirservers when Tor only has a reasonably live
1525 consensus. Fixes bug 28569; bugfix on 0.3.2.5-alpha.
1527 o Minor bugfixes (directory mirrors):
1528 - Even when a directory mirror's clock is behind the clocks on the
1529 authorities, we now allow the mirror to serve "future"
1530 consensuses. Fixes bug 28654; bugfix on 0.3.0.1-alpha.
1532 o Minor bugfixes (DNS):
1533 - Gracefully handle an empty or absent resolve.conf file by falling
1534 back to using "localhost" as a DNS server (and hoping it works).
1535 Previously, we would just stop running as an exit. Fixes bug
1536 21900; bugfix on 0.2.1.10-alpha.
1538 o Minor bugfixes (guards):
1539 - In count_acceptable_nodes(), the minimum number is now one bridge
1540 or guard node, and two non-guard nodes for a circuit. Previously,
1541 we had added up the sum of all nodes with a descriptor, but that
1542 could cause us to build failing circuits when we had either too
1543 many bridges or not enough guard nodes. Fixes bug 25885; bugfix on
1544 0.2.3.1-alpha. Patch by Neel Chauhan.
1546 o Minor bugfixes (IPv6):
1547 - Fix tor_ersatz_socketpair on IPv6-only systems. Previously, the
1548 IPv6 socket was bound using an address family of AF_INET instead
1549 of AF_INET6. Fixes bug 28995; bugfix on 0.3.5.1-alpha. Patch from
1552 o Minor bugfixes (logging):
1553 - Rework rep_hist_log_link_protocol_counts() to iterate through all
1554 link protocol versions when logging incoming/outgoing connection
1555 counts. Tor no longer skips version 5, and we won't have to
1556 remember to update this function when new link protocol version is
1557 developed. Fixes bug 28920; bugfix on 0.2.6.10.
1559 o Minor bugfixes (networking):
1560 - Introduce additional checks into tor_addr_parse() to reject
1561 certain incorrect inputs that previously were not detected. Fixes
1562 bug 23082; bugfix on 0.2.0.10-alpha.
1564 o Minor bugfixes (onion service v3, client):
1565 - Stop logging a "BUG()" warning and stacktrace when we find a SOCKS
1566 connection waiting for a descriptor that we actually have in the
1567 cache. It turns out that this can actually happen, though it is
1568 rare. Now, tor will recover and retry the descriptor. Fixes bug
1569 28669; bugfix on 0.3.2.4-alpha.
1571 o Minor bugfixes (periodic events):
1572 - Refrain from calling routerlist_remove_old_routers() from
1573 check_descriptor_callback(). Instead, create a new hourly periodic
1574 event. Fixes bug 27929; bugfix on 0.2.8.1-alpha.
1576 o Minor bugfixes (pluggable transports):
1577 - Make sure that data is continously read from standard output and
1578 standard error pipes of a pluggable transport child-process, to
1579 avoid deadlocking when a pipe's buffer is full. Fixes bug 26360;
1580 bugfix on 0.2.3.6-alpha.
1582 o Minor bugfixes (unit tests):
1583 - Instead of relying on hs_free_all() to clean up all onion service
1584 objects in test_build_descriptors(), we now deallocate them one by
1585 one. This lets Coverity know that we are not leaking memory there
1586 and fixes CID 1442277. Fixes bug 28989; bugfix on 0.3.5.1-alpha.
1588 o Minor bugfixes (usability):
1589 - Stop saying "Your Guard ..." in pathbias_measure_{use,close}_rate().
1590 Some users took this phrasing to mean that the mentioned guard was
1591 under their control or responsibility, which it is not. Fixes bug
1592 28895; bugfix on Tor 0.3.0.1-alpha.
1594 o Code simplification and refactoring:
1595 - Reimplement NETINFO cell parsing and generation to rely on
1596 trunnel-generated wire format handling code. Closes ticket 27325.
1597 - Remove unnecessary unsafe code from the Rust macro "cstr!". Closes
1599 - Rework SOCKS wire format handling to rely on trunnel-generated
1600 parsing/generation code. Resolves ticket 27620.
1601 - Split out bootstrap progress reporting from control.c into a
1602 separate file. Part of ticket 27402.
1603 - The .may_include files that we use to describe our directory-by-
1604 directory dependency structure now describe a noncircular
1605 dependency graph over the directories that they cover. Our
1606 checkIncludes.py tool now enforces this noncircularity. Closes
1610 - Mention that you cannot add a new onion service if Tor is already
1611 running with Sandbox enabled. Closes ticket 28560.
1612 - Improve ControlPort documentation. Mention that it accepts
1613 address:port pairs, and can be used multiple times. Closes
1615 - Document the exact output of "tor --version". Closes ticket 28889.
1618 - Stop responding to the 'GETINFO status/version/num-concurring' and
1619 'GETINFO status/version/num-versioning' control port commands, as
1620 those were deprecated back in 0.2.0.30. Also stop listing them in
1621 output of 'GETINFO info/names'. Resolves ticket 28757.
1622 - The scripts used to generate and maintain the list of fallback
1623 directories have been extracted into a new "fallback-scripts"
1624 repository. Closes ticket 27914.
1627 - Run shellcheck for scripts in the in scripts/ directory. Closes
1629 - Add unit tests for tokenize_string() and get_next_token()
1630 functions. Resolves ticket 27625.
1632 o Code simplification and refactoring (onion service v3):
1633 - Consolidate the authorized client descriptor cookie computation
1634 code from client and service into one function. Closes
1637 o Code simplification and refactoring (shell scripts):
1638 - Cleanup scan-build.sh to silence shellcheck warnings. Closes
1640 - Fix issues that shellcheck found in chutney-git-bisect.sh.
1641 Resolves ticket 28006.
1642 - Fix issues that shellcheck found in updateRustDependencies.sh.
1643 Resolves ticket 28012.
1644 - Fix shellcheck warnings in cov-diff script. Resolves issue 28009.
1645 - Fix shellcheck warnings in run_calltool.sh. Resolves ticket 28011.
1646 - Fix shellcheck warnings in run_trunnel.sh. Resolves issue 28010.
1647 - Fix shellcheck warnings in scripts/test/coverage. Resolves
1651 Changes in version 0.3.3.11 - 2019-01-07
1652 Tor 0.3.3.11 backports numerous fixes from later versions of Tor.
1653 numerous fixes, including an important fix for anyone using OpenSSL
1654 1.1.1. Anyone running an earlier version of Tor 0.3.3 should upgrade
1655 to this version, or to a later series.
1657 As a reminder, support the Tor 0.3.3 series will end on 22 Feb 2019.
1658 We anticipate that this will be the last release of Tor 0.3.3, unless
1659 some major bug is before then. Some time between now and then, users
1660 should switch to either the Tor 0.3.4 series (supported until at least
1661 10 June 2019), or the Tor 0.3.5 series, which will receive long-term
1662 support until at least 1 Feb 2022.
1664 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1665 - Fix our usage of named groups when running as a TLS 1.3 client in
1666 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1667 running as a relay, which caused clients to fail to negotiate TLS
1668 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1671 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
1672 - Fix a use-after-free error that could be caused by passing Tor an
1673 impossible set of options that would fail during options_act().
1674 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
1676 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
1677 - Only run one online rust build in Travis, to reduce network
1678 errors. Skip offline rust builds on Travis for Linux gcc, because
1679 they're redundant. Implements ticket 27252.
1680 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
1681 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
1682 Linux with default settings, because all the non-default builds
1683 use gcc on Linux. Implements ticket 27252.
1685 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
1686 - Use the Travis Homebrew addon to install packages on macOS during
1687 Travis CI. The package list is the same, but the Homebrew addon
1688 does not do a `brew update` by default. Implements ticket 27738.
1690 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1691 - Replace the 150 fallbacks originally introduced in Tor
1692 0.3.3.1-alpha in January 2018 (of which ~115 were still
1693 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1694 removed) generated in December 2018. Closes ticket 24803.
1696 o Minor features (geoip):
1697 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1698 Country database. Closes ticket 29012.
1700 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1701 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1702 key export function from handling long labels. When this bug is
1703 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1704 version of OpenSSL without this bug when it becomes available.
1705 Closes ticket 28973.
1707 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1708 - Update relay descriptor on bandwidth changes only when the uptime
1709 is smaller than 24h, in order to reduce the efficiency of guard
1710 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1712 o Minor bugfixes (C correctness, backport from 0.3.5.4-alpha):
1713 - Avoid undefined behavior in an end-of-string check when parsing
1714 the BEGIN line in a directory object. Fixes bug 28202; bugfix
1717 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
1718 - Rewrite our assertion macros so that they no longer suppress the
1719 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
1721 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1722 - Initialize a variable unconditionally in aes_new_cipher(), since
1723 some compilers cannot tell that we always initialize it before
1724 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1726 o Minor bugfixes (directory authority, backport from 0.3.5.4-alpha):
1727 - Log additional info when we get a relay that shares an ed25519 ID
1728 with a different relay, instead making a BUG() warning. Fixes bug
1729 27800; bugfix on 0.3.2.1-alpha.
1731 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1732 - When a user requests a group-readable DataDirectory, give it to
1733 them. Previously, when the DataDirectory and the CacheDirectory
1734 were the same, the default setting (0) for
1735 CacheDirectoryGroupReadable would override the setting for
1736 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1739 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
1740 - When the onion service directory can't be created or has the wrong
1741 permissions, do not log a stack trace. Fixes bug 27335; bugfix
1744 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
1745 - Close all SOCKS request (for the same .onion) if the newly fetched
1746 descriptor is unusable. Before that, we would close only the first
1747 one leaving the other hanging and let to time out by themselves.
1748 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
1750 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1751 - Don't warn so loudly when Tor is unable to decode an onion
1752 descriptor. This can now happen as a normal use case if a client
1753 gets a descriptor with client authorization but the client is not
1754 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1756 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1757 - When deleting an ephemeral onion service (DEL_ONION), do not close
1758 any rendezvous circuits in order to let the existing client
1759 connections finish by themselves or closed by the application. The
1760 HS v2 is doing that already so now we have the same behavior for
1761 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1763 o Minor bugfixes (HTTP tunnel):
1764 - Fix a bug warning when closing an HTTP tunnel connection due to
1765 an HTTP request we couldn't handle. Fixes bug 26470; bugfix on
1768 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1769 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1770 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1772 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
1773 - Ensure circuitmux queues are empty before scheduling or sending
1774 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
1776 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
1777 - Reject protocol names containing bytes other than alphanumeric
1778 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
1781 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
1782 - Compute protover votes correctly in the rust version of the
1783 protover code. Previously, the protover rewrite in 24031 allowed
1784 repeated votes from the same voter for the same protocol version
1785 to be counted multiple times in protover_compute_vote(). Fixes bug
1786 27649; bugfix on 0.3.3.5-rc.
1787 - Reject protover names that contain invalid characters. Fixes bug
1788 27687; bugfix on 0.3.3.1-alpha.
1790 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
1791 - protover_all_supported() would attempt to allocate up to 16GB on
1792 some inputs, leading to a potential memory DoS. Fixes bug 27206;
1793 bugfix on 0.3.3.5-rc.
1795 o Minor bugfixes (rust, backport from 0.3.5.4-alpha):
1796 - Fix a potential null dereference in protover_all_supported(). Add
1797 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
1798 - Return a string that can be safely freed by C code, not one
1799 created by the rust allocator, in protover_all_supported(). Fixes
1800 bug 27740; bugfix on 0.3.3.1-alpha.
1801 - Fix an API mismatch in the rust implementation of
1802 protover_compute_vote(). This bug could have caused crashes on any
1803 directory authorities running Tor with Rust (which we do not yet
1804 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
1806 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
1807 - If a unit test running in a subprocess exits abnormally or with a
1808 nonzero status code, treat the test as having failed, even if the
1809 test reported success. Without this fix, memory leaks don't cause
1810 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
1811 bugfix on 0.2.2.4-alpha.
1813 o Minor bugfixes (testing, backport from 0.3.5.4-alpha):
1814 - Treat backtrace test failures as expected on BSD-derived systems
1815 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
1816 (FreeBSD failures have been treated as expected since 18204 in
1817 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
1819 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1820 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1821 bugfix on 0.3.0.1-alpha.
1824 Changes in version 0.3.4.10 - 2019-01-07
1825 Tor 0.3.4.9 is the second stable release in its series; it backports
1826 numerous fixes, including an important fix for relays, and for anyone
1827 using OpenSSL 1.1.1. Anyone running an earlier version of Tor 0.3.4
1830 As a reminder, the Tor 0.3.4 series will be supported until 10 June
1831 2019. Some time between now and then, users should switch to the Tor
1832 0.3.5 series, which will receive long-term support until at least 1
1835 o Major bugfixes (OpenSSL, portability, backport from 0.3.5.5-alpha):
1836 - Fix our usage of named groups when running as a TLS 1.3 client in
1837 OpenSSL 1.1.1. Previously, we only initialized EC groups when
1838 running as a relay, which caused clients to fail to negotiate TLS
1839 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
1842 o Major bugfixes (relay, directory, backport from 0.3.5.7):
1843 - Always reactivate linked connections in the main loop so long as
1844 any linked connection has been active. Previously, connections
1845 serving directory information wouldn't get reactivated after the
1846 first chunk of data was sent (usually 32KB), which would prevent
1847 clients from bootstrapping. Fixes bug 28912; bugfix on
1848 0.3.4.1-alpha. Patch by "cypherpunks3".
1850 o Minor features (continuous integration, Windows, backport from 0.3.5.6-rc):
1851 - Always show the configure and test logs, and upload them as build
1852 artifacts, when building for Windows using Appveyor CI.
1855 o Minor features (controller, backport from 0.3.5.1-alpha):
1856 - For purposes of CIRC_BW-based dropped cell detection, track half-
1857 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
1858 bias check cells to arrive without counting it as dropped until
1859 either the END arrives, or the windows are empty. Closes
1862 o Minor features (fallback directory list, backport from 0.3.5.6-rc):
1863 - Replace the 150 fallbacks originally introduced in Tor
1864 0.3.3.1-alpha in January 2018 (of which ~115 were still
1865 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
1866 removed) generated in December 2018. Closes ticket 24803.
1868 o Minor features (geoip):
1869 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
1870 Country database. Closes ticket 28395.
1872 o Minor features (OpenSSL bug workaround, backport from 0.3.5.7):
1873 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1874 key export function from handling long labels. When this bug is
1875 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1876 version of OpenSSL without this bug when it becomes available.
1877 Closes ticket 28973.
1879 o Minor bugfixes (compilation, backport from 0.3.5.5-alpha):
1880 - Initialize a variable unconditionally in aes_new_cipher(), since
1881 some compilers cannot tell that we always initialize it before
1882 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
1884 o Minor bugfixes (connection, relay, backport from 0.3.5.5-alpha):
1885 - Avoid a logging a BUG() stacktrace when closing connection held
1886 open because the write side is rate limited but not the read side.
1887 Now, the connection read side is simply shut down until Tor is
1888 able to flush the connection and close it. Fixes bug 27750; bugfix
1891 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.5-alpha):
1892 - Manually configure the zstd compiler options, when building using
1893 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
1894 not come with a pkg-config file. Fixes bug 28454; bugfix
1896 - Stop using an external OpenSSL install, and stop installing MSYS2
1897 packages, when building using mingw on Appveyor Windows CI. Fixes
1898 bug 28399; bugfix on 0.3.4.1-alpha.
1900 o Minor bugfixes (continuous integration, Windows, backport from 0.3.5.6-rc):
1901 - Explicitly specify the path to the OpenSSL library and do not
1902 download OpenSSL from Pacman, but instead use the library that is
1903 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
1905 o Minor bugfixes (directory permissions, backport form 0.3.5.3-alpha):
1906 - When a user requests a group-readable DataDirectory, give it to
1907 them. Previously, when the DataDirectory and the CacheDirectory
1908 were the same, the default setting (0) for
1909 CacheDirectoryGroupReadable would override the setting for
1910 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
1913 o Minor bugfixes (memory leaks, backport from 0.3.5.5-alpha):
1914 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
1915 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
1917 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
1918 - Don't warn so loudly when Tor is unable to decode an onion
1919 descriptor. This can now happen as a normal use case if a client
1920 gets a descriptor with client authorization but the client is not
1921 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
1923 o Minor bugfixes (onion service v3, backport from 0.3.5.6-rc):
1924 - When deleting an ephemeral onion service (DEL_ONION), do not close
1925 any rendezvous circuits in order to let the existing client
1926 connections finish by themselves or closed by the application. The
1927 HS v2 is doing that already so now we have the same behavior for
1928 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
1930 o Minor bugfixes (relay statistics, backport from 0.3.5.7):
1931 - Update relay descriptor on bandwidth changes only when the uptime
1932 is smaller than 24h, in order to reduce the efficiency of guard
1933 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
1935 o Minor bugfixes (unit tests, guard selection, backport from 0.3.5.6-rc):
1936 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
1937 bugfix on 0.3.0.1-alpha.
1940 Changes in version 0.3.5.7 - 2019-01-07
1941 Tor 0.3.5.7 is the first stable release in its series; it includes
1942 compilation and portability fixes, and a fix for a severe problem
1943 affecting directory caches.
1945 The Tor 0.3.5 series includes several new features and performance
1946 improvements, including client authorization for v3 onion services,
1947 cleanups to bootstrap reporting, support for improved bandwidth-
1948 measurement tools, experimental support for NSS in place of OpenSSL,
1949 and much more. It also begins a full reorganization of Tor's code
1950 layout, for improved modularity and maintainability in the future.
1951 Finally, there is the usual set of performance improvements and
1952 bugfixes that we try to do in every release series.
1954 There are a couple of changes in the 0.3.5 that may affect
1955 compatibility. First, the default version for newly created onion
1956 services is now v3. Use the HiddenServiceVersion option if you want to
1957 override this. Second, some log messages related to bootstrapping have
1958 changed; if you use stem, you may need to update to the latest version
1959 so it will recognize them.
1961 We have designated 0.3.5 as a "long-term support" (LTS) series: we
1962 will continue to patch major bugs in typical configurations of 0.3.5
1963 until at least 1 Feb 2022. (We do not plan to provide long-term
1964 support for embedding, Rust support, NSS support, running a directory
1965 authority, or unsupported platforms. For these, you will need to stick
1966 with the latest stable release.)
1968 Below are the changes since 0.3.5.6-rc. For a complete list of changes
1969 since 0.3.4.9, see the ReleaseNotes file.
1971 o Major bugfixes (relay, directory):
1972 - Always reactivate linked connections in the main loop so long as
1973 any linked connection has been active. Previously, connections
1974 serving directory information wouldn't get reactivated after the
1975 first chunk of data was sent (usually 32KB), which would prevent
1976 clients from bootstrapping. Fixes bug 28912; bugfix on
1977 0.3.4.1-alpha. Patch by "cypherpunks3".
1979 o Minor features (compilation):
1980 - When possible, place our warning flags in a separate file, to
1981 avoid flooding verbose build logs. Closes ticket 28924.
1983 o Minor features (geoip):
1984 - Update geoip and geoip6 to the January 3 2019 Maxmind GeoLite2
1985 Country database. Closes ticket 29012.
1987 o Minor features (OpenSSL bug workaround):
1988 - Work around a bug in OpenSSL 1.1.1a, which prevented the TLS 1.3
1989 key export function from handling long labels. When this bug is
1990 detected, Tor will disable TLS 1.3. We recommend upgrading to a
1991 version of OpenSSL without this bug when it becomes available.
1992 Closes ticket 28973.
1994 o Minor features (performance):
1995 - Remove about 96% of the work from the function that we run at
1996 startup to test our curve25519_basepoint implementation. Since
1997 this function has yet to find an actual failure, we now only run
1998 it for 8 iterations instead of 200. Based on our profile
1999 information, this change should save around 8% of our startup time
2000 on typical desktops, and may have a similar effect on other
2001 platforms. Closes ticket 28838.
2002 - Stop re-validating our hardcoded Diffie-Hellman parameters on
2003 every startup. Doing this wasted time and cycles, especially on
2004 low-powered devices. Closes ticket 28851.
2006 o Minor bugfixes (compilation):
2007 - Fix compilation for Android by adding a missing header to
2008 freespace.c. Fixes bug 28974; bugfix on 0.3.5.1-alpha.
2010 o Minor bugfixes (correctness):
2011 - Fix an unreached code path where we checked the value of
2012 "hostname" inside send_resolved_hostname_cell(). Previously, we
2013 used it before checking it; now we check it first. Fixes bug
2014 28879; bugfix on 0.1.2.7-alpha.
2016 o Minor bugfixes (testing):
2017 - Make sure that test_rebind.py actually obeys its timeout, even
2018 when it receives a large number of log messages. Fixes bug 28883;
2019 bugfix on 0.3.5.4-alpha.
2020 - Stop running stem's unit tests as part of "make test-stem", but
2021 continue to run stem's unit and online tests during "make test-
2022 stem-full". Fixes bug 28568; bugfix on 0.2.6.3-alpha.
2024 o Minor bugfixes (windows services):
2025 - Make Tor start correctly as an NT service again: previously it was
2026 broken by refactoring. Fixes bug 28612; bugfix on 0.3.5.3-alpha.
2028 o Code simplification and refactoring:
2029 - When parsing a port configuration, make it more obvious to static
2030 analyzer tools that we always initialize the address. Closes
2034 Changes in version 0.3.5.6-rc - 2018-12-18
2035 Tor 0.3.5.6-rc fixes numerous small bugs in earlier versions of Tor.
2036 It is the first release candidate in the 0.3.5.x series; if no further
2037 huge bugs are found, our next release may be the stable 0.3.5.x.
2039 o Minor features (continuous integration, Windows):
2040 - Always show the configure and test logs, and upload them as build
2041 artifacts, when building for Windows using Appveyor CI.
2044 o Minor features (fallback directory list):
2045 - Replace the 150 fallbacks originally introduced in Tor
2046 0.3.3.1-alpha in January 2018 (of which ~115 were still
2047 functional), with a list of 157 fallbacks (92 new, 65 existing, 85
2048 removed) generated in December 2018. Closes ticket 24803.
2050 o Minor features (geoip):
2051 - Update geoip and geoip6 to the December 5 2018 Maxmind GeoLite2
2052 Country database. Closes ticket 28744.
2054 o Minor bugfixes (compilation):
2055 - Add missing dependency on libgdi32.dll for tor-print-ed-signing-
2056 cert.exe on Windows. Fixes bug 28485; bugfix on 0.3.5.1-alpha.
2058 o Minor bugfixes (continuous integration, Windows):
2059 - Explicitly specify the path to the OpenSSL library and do not
2060 download OpenSSL from Pacman, but instead use the library that is
2061 already provided by AppVeyor. Fixes bug 28574; bugfix on master.
2063 o Minor bugfixes (onion service v3):
2064 - When deleting an ephemeral onion service (DEL_ONION), do not close
2065 any rendezvous circuits in order to let the existing client
2066 connections finish by themselves or closed by the application. The
2067 HS v2 is doing that already so now we have the same behavior for
2068 all versions. Fixes bug 28619; bugfix on 0.3.3.1-alpha.
2070 o Minor bugfixes (restart-in-process, boostrap):
2071 - Add missing resets of bootstrap tracking state when shutting down
2072 (regression caused by ticket 27169). Fixes bug 28524; bugfix
2075 o Minor bugfixes (testing):
2076 - Use a separate DataDirectory for the test_rebind script.
2077 Previously, this script would run using the default DataDirectory,
2078 and sometimes fail. Fixes bug 28562; bugfix on 0.3.5.1-alpha.
2079 Patch from Taylor R Campbell.
2080 - Stop leaking memory in an entry guard unit test. Fixes bug 28554;
2081 bugfix on 0.3.0.1-alpha.
2083 o Minor bugfixes (Windows):
2084 - Correctly identify Windows 8.1, Windows 10, and Windows Server
2085 2008 and later from their NT versions. Fixes bug 28096; bugfix on
2086 0.2.2.34; reported by Keifer Bly.
2087 - On recent Windows versions, the GetVersionEx() function may report
2088 an earlier Windows version than the running OS. To avoid user
2089 confusion, add "[or later]" to Tor's version string on affected
2090 versions of Windows. Fixes bug 28096; bugfix on 0.2.2.34; reported
2092 - Remove Windows versions that were never supported by the
2093 GetVersionEx() function. Stop duplicating the latest Windows
2094 version in get_uname(). Fixes bug 28096; bugfix on 0.2.2.34;
2095 reported by Keifer Bly.
2098 - Increase logging and tag all log entries with timestamps in
2099 test_rebind.py. Provides diagnostics for issue 28229.
2101 o Code simplification and refactoring (shared random, dirauth):
2102 - Change many tor_assert() to use BUG() instead. The idea is to not
2103 crash a dirauth but rather scream loudly with a stacktrace and let
2104 it continue run. The shared random subsystem is very resilient and
2105 if anything wrong happens with it, at worst a non coherent value
2106 will be put in the vote and discarded by the other authorities.
2107 Closes ticket 19566.
2109 o Documentation (onion services):
2110 - Document in the man page that changing ClientOnionAuthDir value or
2111 adding a new file in the directory will not work at runtime upon
2112 sending a HUP if Sandbox 1. Closes ticket 28128.
2113 - Note in the man page that the only real way to fully revoke an
2114 onion service v3 client authorization is by restarting the tor
2115 process. Closes ticket 28275.
2118 Changes in version 0.3.5.5-alpha - 2018-11-16
2119 Tor 0.3.5.5-alpha includes numerous bugfixes on earlier releases,
2120 including several that we hope to backport to older release series in
2123 o Major bugfixes (OpenSSL, portability):
2124 - Fix our usage of named groups when running as a TLS 1.3 client in
2125 OpenSSL 1.1.1. Previously, we only initialized EC groups when
2126 running as a relay, which caused clients to fail to negotiate TLS
2127 1.3 with relays. Fixes bug 28245; bugfix on 0.2.9.15 (when TLS 1.3
2130 o Minor features (geoip):
2131 - Update geoip and geoip6 to the November 6 2018 Maxmind GeoLite2
2132 Country database. Closes ticket 28395.
2134 o Minor bugfixes (compilation):
2135 - Initialize a variable unconditionally in aes_new_cipher(), since
2136 some compilers cannot tell that we always initialize it before
2137 use. Fixes bug 28413; bugfix on 0.2.9.3-alpha.
2139 o Minor bugfixes (connection, relay):
2140 - Avoid a logging a BUG() stacktrace when closing connection held
2141 open because the write side is rate limited but not the read side.
2142 Now, the connection read side is simply shut down until Tor is
2143 able to flush the connection and close it. Fixes bug 27750; bugfix
2146 o Minor bugfixes (continuous integration, Windows):
2147 - Manually configure the zstd compiler options, when building using
2148 mingw on Appveyor Windows CI. The MSYS2 mingw zstd package does
2149 not come with a pkg-config file. Fixes bug 28454; bugfix
2151 - Stop using an external OpenSSL install, and stop installing MSYS2
2152 packages, when building using mingw on Appveyor Windows CI. Fixes
2153 bug 28399; bugfix on 0.3.4.1-alpha.
2155 o Minor bugfixes (documentation):
2156 - Make Doxygen work again after the code movement in the 0.3.5
2157 source tree. Fixes bug 28435; bugfix on 0.3.5.1-alpha.
2159 o Minor bugfixes (Linux seccomp2 sandbox):
2160 - Permit the "shutdown()" system call, which is apparently used by
2161 OpenSSL under some circumstances. Fixes bug 28183; bugfix
2164 o Minor bugfixes (logging):
2165 - Stop talking about the Named flag in log messages. Clients have
2166 ignored the Named flag since 0.3.2. Fixes bug 28441; bugfix
2169 o Minor bugfixes (memory leaks):
2170 - Fix a harmless memory leak in libtorrunner.a. Fixes bug 28419;
2171 bugfix on 0.3.3.1-alpha. Patch from Martin Kepplinger.
2173 o Minor bugfixes (onion services):
2174 - On an intro point for a version 3 onion service, stop closing
2175 introduction circuits on an NACK. This lets the client decide
2176 whether to reuse the circuit or discard it. Previously, we closed
2177 intro circuits when sending NACKs. Fixes bug 27841; bugfix on
2178 0.3.2.1-alpha. Patch by Neel Chaunan.
2179 - When replacing a descriptor in the client cache, make sure to
2180 close all client introduction circuits for the old descriptor, so
2181 we don't end up with unusable leftover circuits. Fixes bug 27471;
2182 bugfix on 0.3.2.1-alpha.
2185 Changes in version 0.3.5.4-alpha - 2018-11-08
2186 Tor 0.3.5.4-alpha includes numerous bugfixes on earlier versions and
2187 improves our continuous integration support. It continues our attempts
2188 to stabilize this alpha branch and build it into a foundation for an
2189 acceptable long-term-support release.
2191 o Major bugfixes (compilation, rust):
2192 - Rust tests can now build and run successfully with the
2193 --enable-fragile-hardening option enabled. Doing this currently
2194 requires the rust beta channel; it will be possible with stable
2195 rust once Rust version 1.31 is released. Patch from Alex Crichton.
2196 Fixes bugs 27272, 27273, and 27274. Bugfix on 0.3.1.1-alpha.
2198 o Major bugfixes (embedding, main loop):
2199 - When DisableNetwork becomes set, actually disable periodic events
2200 that are already enabled. (Previously, we would refrain from
2201 enabling new ones, but we would leave the old ones turned on.)
2202 Fixes bug 28348; bugfix on 0.3.4.1-alpha.
2204 o Minor features (continuous integration):
2205 - Add a Travis CI build for --enable-nss on Linux gcc. Closes
2207 - Add new CI job to Travis configuration to run stem-based
2208 integration tests. Closes ticket 27913.
2210 o Minor features (Windows, continuous integration):
2211 - Build tor on Windows Server 2012 R2 and Windows Server 2016 using
2212 Appveyor's CI. Closes ticket 28318.
2214 o Minor bugfixes (C correctness, also in 0.3.4.9):
2215 - Avoid undefined behavior in an end-of-string check when parsing
2216 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2219 o Minor bugfixes (compilation):
2220 - Fix a pair of missing headers on OpenBSD. Fixes bug 28303; bugfix
2221 on 0.3.5.1-alpha. Patch from Kris Katterjohn.
2223 o Minor bugfixes (compilation, OpenSolaris):
2224 - Fix compilation on OpenSolaris and its descendants by adding a
2225 missing include to compat_pthreads.c. Fixes bug 27963; bugfix
2228 o Minor bugfixes (configuration):
2229 - Refuse to start with relative file paths and RunAsDaemon set
2230 (regression from the fix for bug 22731). Fixes bug 28298; bugfix
2233 o Minor bugfixes (directory authority, also in 0.3.4.9):
2234 - Log additional info when we get a relay that shares an ed25519 ID
2235 with a different relay, instead of a BUG() warning with a
2236 backtrace. Fixes bug 27800; bugfix on 0.3.2.1-alpha.
2238 o Minor bugfixes (onion service v3):
2239 - Build the service descriptor's signing key certificate before
2240 uploading, so we always have a fresh one: leaving no chances for
2241 it to expire service side. Fixes bug 27838; bugfix
2244 o Minor bugfixes (onion service v3, client authorization):
2245 - Fix an assert() when adding a client authorization for the first
2246 time and then sending a HUP signal to the service. Before that,
2247 Tor would stop abruptly. Fixes bug 27995; bugfix on 0.3.5.1-alpha.
2249 o Minor bugfixes (onion services):
2250 - Unless we have explicitly set HiddenServiceVersion, detect the
2251 onion service version and then look for invalid options.
2252 Previously, we did the reverse, but that broke existing configs
2253 which were pointed to a v2 service and had options like
2254 HiddenServiceAuthorizeClient set. Fixes bug 28127; bugfix on
2255 0.3.5.1-alpha. Patch by Neel Chauhan.
2257 o Minor bugfixes (portability):
2258 - Make the OPE code (which is used for v3 onion services) run
2259 correctly on big-endian platforms. Fixes bug 28115; bugfix
2262 o Minor bugfixes (protover, rust):
2263 - Reject extra commas in version strings. Fixes bug 27197; bugfix
2266 o Minor bugfixes (relay shutdown, systemd):
2267 - Notify systemd of ShutdownWaitLength so it can be set to longer
2268 than systemd's TimeoutStopSec. In Tor's systemd service file, set
2269 TimeoutSec to 60 seconds to allow Tor some time to shut down.
2270 Fixes bug 28113; bugfix on 0.2.6.2-alpha.
2272 o Minor bugfixes (rust, also in 0.3.4.9):
2273 - Fix a potential null dereference in protover_all_supported(). Add
2274 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2275 - Return a string that can be safely freed by C code, not one
2276 created by the rust allocator, in protover_all_supported(). Fixes
2277 bug 27740; bugfix on 0.3.3.1-alpha.
2279 o Minor bugfixes (rust, directory authority, also in 0.3.4.9):
2280 - Fix an API mismatch in the rust implementation of
2281 protover_compute_vote(). This bug could have caused crashes on any
2282 directory authorities running Tor with Rust (which we do not yet
2283 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2285 o Minor bugfixes (testing):
2286 - Avoid hangs and race conditions in test_rebind.py. Fixes bug
2287 27968; bugfix on 0.3.5.1-alpha.
2289 o Minor bugfixes (testing, also in 0.3.4.9):
2290 - Treat backtrace test failures as expected on BSD-derived systems
2291 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2292 (FreeBSD failures have been treated as expected since 18204 in
2293 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2295 o Documentation (onion service manpage):
2296 - Improve HSv3 client authorization by making some options more
2297 explicit and detailed. Closes ticket 28026. Patch by Mike Tigas.
2300 Changes in version 0.3.4.9 - 2018-11-02
2301 Tor 0.3.4.9 is the second stable release in its series; it backports
2302 numerous fixes, including a fix for a bandwidth management bug that
2303 was causing memory exhaustion on relays. Anyone running an earlier
2304 version of Tor 0.3.4.9 should upgrade.
2306 o Major bugfixes (compilation, backport from 0.3.5.3-alpha):
2307 - Fix compilation on ARM (and other less-used CPUs) when compiling
2308 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2310 o Major bugfixes (mainloop, bootstrap, backport from 0.3.5.3-alpha):
2311 - Make sure Tor bootstraps and works properly if only the
2312 ControlPort is set. Prior to this fix, Tor would only bootstrap
2313 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2314 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2316 o Major bugfixes (relay, backport from 0.3.5.3-alpha):
2317 - When our write bandwidth limit is exhausted, stop writing on the
2318 connection. Previously, we had a typo in the code that would make
2319 us stop reading instead, leading to relay connections being stuck
2320 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2323 o Major bugfixes (restart-in-process, backport from 0.3.5.1-alpha):
2324 - Fix a use-after-free error that could be caused by passing Tor an
2325 impossible set of options that would fail during options_act().
2326 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2328 o Minor features (continuous integration, backport from 0.3.5.1-alpha):
2329 - Don't do a distcheck with --disable-module-dirauth in Travis.
2330 Implements ticket 27252.
2331 - Only run one online rust build in Travis, to reduce network
2332 errors. Skip offline rust builds on Travis for Linux gcc, because
2333 they're redundant. Implements ticket 27252.
2334 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2335 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2336 Linux with default settings, because all the non-default builds
2337 use gcc on Linux. Implements ticket 27252.
2339 o Minor features (continuous integration, backport from 0.3.5.3-alpha):
2340 - Use the Travis Homebrew addon to install packages on macOS during
2341 Travis CI. The package list is the same, but the Homebrew addon
2342 does not do a `brew update` by default. Implements ticket 27738.
2344 o Minor features (geoip):
2345 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2346 Country database. Closes ticket 27991.
2348 o Minor bugfixes (32-bit OSX and iOS, timing, backport from 0.3.5.2-alpha):
2349 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2350 difference algorithm for 32-bit Apple platforms. Previously, it
2351 would overflow when calculating the difference between two times
2352 more than 47 days apart. Fixes part of bug 27139; bugfix
2354 - Improve the precision of our 32-bit millisecond difference
2355 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2356 bugfix on 0.3.4.1-alpha.
2357 - Relax the tolerance on the mainloop/update_time_jumps test when
2358 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2361 o Minor bugfixes (C correctness, to appear in 0.3.5.4-alpha):
2362 - Avoid undefined behavior in an end-of-string check when parsing
2363 the BEGIN line in a directory object. Fixes bug 28202; bugfix
2366 o Minor bugfixes (CI, appveyor, to appear in 0.3.5.4-alpha):
2367 - Only install the necessary mingw packages during our appveyor
2368 builds. This change makes the build a little faster, and prevents
2369 a conflict with a preinstalled mingw openssl that appveyor now
2370 ships. Fixes bugs 27943 and 27765; bugfix on 0.3.4.2-alpha.
2372 o Minor bugfixes (code safety, backport from 0.3.5.3-alpha):
2373 - Rewrite our assertion macros so that they no longer suppress the
2374 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2376 o Minor bugfixes (continuous integration, backport from 0.3.5.1-alpha):
2377 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2378 27464; bugfix on 0.3.4.1-alpha.
2380 o Minor bugfixes (directory authority, to appear in 0.3.5.4-alpha):
2381 - Log additional info when we get a relay that shares an ed25519 ID
2382 with a different relay, instead making a BUG() warning. Fixes bug
2383 27800; bugfix on 0.3.2.1-alpha.
2385 o Minor bugfixes (directory connection shutdown, backport from 0.3.5.1-alpha):
2386 - Avoid a double-close when shutting down a stalled directory
2387 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2389 o Minor bugfixes (HTTP tunnel, backport from 0.3.5.1-alpha):
2390 - Fix a bug warning when closing an HTTP tunnel connection due to an
2391 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2394 o Minor bugfixes (netflow padding, backport from 0.3.5.1-alpha):
2395 - Ensure circuitmux queues are empty before scheduling or sending
2396 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2398 o Minor bugfixes (onion service v3, backport from 0.3.5.1-alpha):
2399 - When the onion service directory can't be created or has the wrong
2400 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2403 o Minor bugfixes (onion service v3, backport from 0.3.5.2-alpha):
2404 - Close all SOCKS request (for the same .onion) if the newly fetched
2405 descriptor is unusable. Before that, we would close only the first
2406 one leaving the other hanging and let to time out by themselves.
2407 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2409 o Minor bugfixes (onion service v3, backport from 0.3.5.3-alpha):
2410 - When selecting a v3 rendezvous point, don't only look at the
2411 protover, but also check whether the curve25519 onion key is
2412 present. This way we avoid picking a relay that supports the v3
2413 rendezvous but for which we don't have the microdescriptor. Fixes
2414 bug 27797; bugfix on 0.3.2.1-alpha.
2416 o Minor bugfixes (protover, backport from 0.3.5.3-alpha):
2417 - Reject protocol names containing bytes other than alphanumeric
2418 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2421 o Minor bugfixes (rust, backport from 0.3.5.1-alpha):
2422 - Compute protover votes correctly in the rust version of the
2423 protover code. Previously, the protover rewrite in 24031 allowed
2424 repeated votes from the same voter for the same protocol version
2425 to be counted multiple times in protover_compute_vote(). Fixes bug
2426 27649; bugfix on 0.3.3.5-rc.
2427 - Reject protover names that contain invalid characters. Fixes bug
2428 27687; bugfix on 0.3.3.1-alpha.
2430 o Minor bugfixes (rust, backport from 0.3.5.2-alpha):
2431 - protover_all_supported() would attempt to allocate up to 16GB on
2432 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2433 bugfix on 0.3.3.5-rc.
2435 o Minor bugfixes (rust, directory authority, to appear in 0.3.5.4-alpha):
2436 - Fix an API mismatch in the rust implementation of
2437 protover_compute_vote(). This bug could have caused crashes on any
2438 directory authorities running Tor with Rust (which we do not yet
2439 recommend). Fixes bug 27741; bugfix on 0.3.3.6.
2441 o Minor bugfixes (rust, to appear in 0.3.5.4-alpha):
2442 - Fix a potential null dereference in protover_all_supported(). Add
2443 a test for it. Fixes bug 27804; bugfix on 0.3.3.1-alpha.
2444 - Return a string that can be safely freed by C code, not one
2445 created by the rust allocator, in protover_all_supported(). Fixes
2446 bug 27740; bugfix on 0.3.3.1-alpha.
2448 o Minor bugfixes (testing, backport from 0.3.5.1-alpha):
2449 - If a unit test running in a subprocess exits abnormally or with a
2450 nonzero status code, treat the test as having failed, even if the
2451 test reported success. Without this fix, memory leaks don't cause
2452 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
2453 bugfix on 0.2.2.4-alpha.
2455 o Minor bugfixes (testing, backport from 0.3.5.3-alpha):
2456 - Make the hs_service tests use the same time source when creating
2457 the introduction point and when testing it. Now tests work better
2458 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2461 o Minor bugfixes (testing, to appear in 0.3.5.4-alpha):
2462 - Treat backtrace test failures as expected on BSD-derived systems
2463 (NetBSD, OpenBSD, and macOS/Darwin) until we solve bug 17808.
2464 (FreeBSD failures have been treated as expected since 18204 in
2465 0.2.8.) Fixes bug 27948; bugfix on 0.2.5.2-alpha.
2468 Changes in version 0.3.5.3-alpha - 2018-10-17
2469 Tor 0.3.5.3-alpha fixes several bugs, mostly from previous 0.3.5.x
2470 versions. One important fix for relays addresses a problem with rate-
2471 limiting code from back in 0.3.4.x: If the fix works out, we'll be
2472 backporting it soon. This release is still an alpha, but we hope it's
2473 getting closer and closer to stability.
2475 o Major features (onion services):
2476 - Version 3 onion services can now use the per-service
2477 HiddenServiceExportCircuitID option to differentiate client
2478 circuits. It communicates with the service by using the HAProxy
2479 protocol to assign virtual IP addresses to inbound client
2480 circuits. Closes ticket 4700. Patch by Mahrud Sayrafi.
2482 o Major bugfixes (compilation):
2483 - Fix compilation on ARM (and other less-used CPUs) when compiling
2484 with OpenSSL before 1.1. Fixes bug 27781; bugfix on 0.3.4.1-alpha.
2486 o Major bugfixes (initialization, crash):
2487 - Fix an assertion crash that would stop Tor from starting up if it
2488 tried to activate a periodic event too early. Fixes bug 27861;
2489 bugfix on 0.3.5.1-alpha.
2491 o Major bugfixes (mainloop, bootstrap):
2492 - Make sure Tor bootstraps and works properly if only the
2493 ControlPort is set. Prior to this fix, Tor would only bootstrap
2494 when a client port was set (Socks, Trans, NATD, DNS or HTTPTunnel
2495 port). Fixes bug 27849; bugfix on 0.3.4.1-alpha.
2497 o Major bugfixes (relay):
2498 - When our write bandwidth limit is exhausted, stop writing on the
2499 connection. Previously, we had a typo in the code that would make
2500 us stop reading instead, leading to relay connections being stuck
2501 indefinitely and consuming kernel RAM. Fixes bug 28089; bugfix
2504 o Minor features (continuous integration):
2505 - Use the Travis Homebrew addon to install packages on macOS during
2506 Travis CI. The package list is the same, but the Homebrew addon
2507 does not do a `brew update` by default. Implements ticket 27738.
2508 - Report what program produced the mysterious core file that we
2509 occasionally see on Travis CI during make distcheck. Closes
2512 o Minor features (geoip):
2513 - Update geoip and geoip6 to the October 9 2018 Maxmind GeoLite2
2514 Country database. Closes ticket 27991.
2516 o Minor bugfixes (code safety):
2517 - Rewrite our assertion macros so that they no longer suppress the
2518 compiler's -Wparentheses warnings. Fixes bug 27709; bugfix
2521 o Minor bugfixes (compilation):
2522 - Compile the ed25519-donna code with a correct declaration of
2523 crypto_strongest_rand(). Previously, we built it with one type,
2524 but linked it against another in the unit tests, which caused
2525 compilation failures with LTO enabled. This could have caused
2526 other undefined behavior in the tests. Fixes bug 27728; bugfix
2529 o Minor bugfixes (compilation, netbsd):
2530 - Add a missing include back into procmon.c. Fixes bug 27990; bugfix
2533 o Minor bugfixes (continuous integration, appveyor):
2534 - Install only the necessary mingw packages during our appveyor
2535 builds. This change makes the build a little faster, and prevents
2536 a conflict with a preinstalled mingw openssl that appveyor now
2537 ships. Fixes bugs 27765 and 27943; bugfix on 0.3.4.2-alpha.
2539 o Minor bugfixes (directory permissions):
2540 - When a user requests a group-readable DataDirectory, give it to
2541 them. Previously, when the DataDirectory and the CacheDirectory
2542 were the same, the default setting (0) for
2543 CacheDirectoryGroupReadable would override the setting for
2544 DataDirectoryGroupReadable. Fixes bug 26913; bugfix
2547 o Minor bugfixes (memory leaks):
2548 - Fix a small memory leak when calling Tor with --dump-config. Fixes
2549 bug 27893; bugfix on 0.3.2.1-alpha.
2551 o Minor bugfixes (networking):
2552 - In retry_listeners_ports(), make sure that we're removing a member
2553 of old_conns smartlist at most once. Fixes bug 27808; bugfix
2555 - Refrain from attempting socket rebinding when old and new
2556 listeners are in different address families. Fixes bug 27928;
2557 bugfix on 0.3.5.1-alpha.
2559 o Minor bugfixes (onion service v3):
2560 - Stop dumping a stack trace when trying to connect to an intro
2561 point without having a descriptor for it. Fixes bug 27774; bugfix
2563 - Don't warn so loudly when Tor is unable to decode an onion
2564 descriptor. This can now happen as a normal use case if a client
2565 gets a descriptor with client authorization but the client is not
2566 authorized. Fixes bug 27550; bugfix on 0.3.5.1-alpha.
2567 - When selecting a v3 rendezvous point, don't only look at the
2568 protover, but also check whether the curve25519 onion key is
2569 present. This way we avoid picking a relay that supports the v3
2570 rendezvous but for which we don't have the microdescriptor. Fixes
2571 bug 27797; bugfix on 0.3.2.1-alpha.
2573 o Minor bugfixes (protover):
2574 - Reject protocol names containing bytes other than alphanumeric
2575 characters and hyphens ([A-Za-z0-9-]). Fixes bug 27316; bugfix
2578 o Minor bugfixes (testing):
2579 - Make the hs_service tests use the same time source when creating
2580 the introduction point and when testing it. Now tests work better
2581 on very slow systems like ARM or Travis. Fixes bug 27810; bugfix
2583 - In test_rebind.py, check if the Python version is in the supported
2584 range. Fixes bug 27675; bugfix on 0.3.5.1-alpha.
2586 o Code simplification and refactoring:
2587 - Divide more large Tor source files -- especially ones that span
2588 multiple areas of functionality -- into smaller parts, including
2589 onion.c and main.c. Closes ticket 26747.
2590 - Divide the "routerparse.c" module into separate modules for each
2591 group of parsed objects. Closes ticket 27924.
2592 - Move protover_rust.c to the same place protover.c was moved to.
2593 Closes ticket 27814.
2594 - Split directory.c into separate pieces for client, server, and
2595 common functionality. Closes ticket 26744.
2596 - Split the non-statistics-related parts from the rephist.c and
2597 geoip.c modules. Closes ticket 27892.
2598 - Split the router.c file into relay-only and shared components, to
2599 help with future modularization. Closes ticket 27864.
2602 - In the tor-resolve(1) manpage, fix the reference to socks-
2603 extensions.txt by adding a web URL. Resolves ticket 27853.
2604 - Mention that we require Python to be 2.7 or newer for some
2605 integration tests that we ship with Tor. Resolves ticket 27677.
2608 Changes in version 0.3.5.2-alpha - 2018-09-21
2609 Tor 0.3.5.2-alpha fixes several bugs in 0.3.5.1-alpha, including one
2610 that made Tor think it had run out of sockets. Anybody running a relay
2611 or an onion service on 0.3.5.1-alpha should upgrade.
2613 o Major bugfixes (relay bandwidth statistics):
2614 - When we close relayed circuits, report the data in the circuit
2615 queues as being written in our relay bandwidth stats. This
2616 mitigates guard discovery and other attacks that close circuits
2617 for the explicit purpose of noticing this discrepancy in
2618 statistics. Fixes bug 23512; bugfix on 0.0.8pre3.
2620 o Major bugfixes (socket accounting):
2621 - In our socket accounting code, count a socket as closed even when
2622 it is closed indirectly by the TLS layer. Previously, we would
2623 count these sockets as still in use, and incorrectly believe that
2624 we had run out of sockets. Fixes bug 27795; bugfix
2627 o Minor bugfixes (32-bit OSX and iOS, timing):
2628 - Fix an integer overflow bug in our optimized 32-bit millisecond-
2629 difference algorithm for 32-bit Apple platforms. Previously, it
2630 would overflow when calculating the difference between two times
2631 more than 47 days apart. Fixes part of bug 27139; bugfix
2633 - Improve the precision of our 32-bit millisecond difference
2634 algorithm for 32-bit Apple platforms. Fixes part of bug 27139;
2635 bugfix on 0.3.4.1-alpha.
2636 - Relax the tolerance on the mainloop/update_time_jumps test when
2637 running on 32-bit Apple platforms. Fixes part of bug 27139; bugfix
2640 o Minor bugfixes (onion service v3):
2641 - Close all SOCKS request (for the same .onion) if the newly fetched
2642 descriptor is unusable. Before that, we would close only the first
2643 one leaving the other hanging and let to time out by themselves.
2644 Fixes bug 27410; bugfix on 0.3.2.1-alpha.
2646 o Minor bugfixes (memory leak):
2647 - Fix an unlikely memory leak when trying to read a private key from
2648 a ridiculously large file. Fixes bug 27764; bugfix on
2649 0.3.5.1-alpha. This is CID 1439488.
2651 o Minor bugfixes (NSS):
2652 - Correctly detect failure to open a dummy TCP socket when stealing
2653 ownership of an fd from the NSS layer. Fixes bug 27782; bugfix
2656 o Minor bugfixes (rust):
2657 - protover_all_supported() would attempt to allocate up to 16GB on
2658 some inputs, leading to a potential memory DoS. Fixes bug 27206;
2659 bugfix on 0.3.3.5-rc.
2661 o Minor bugfixes (testing):
2662 - Revise the "conditionvar_timeout" test so that it succeeds even on
2663 heavily loaded systems where the test threads are not scheduled
2664 within 200 msec. Fixes bug 27073; bugfix on 0.2.6.3-alpha.
2666 o Code simplification and refactoring:
2667 - Divide the routerlist.c and dirserv.c modules into smaller parts.
2668 Closes ticket 27799.
2671 Changes in version 0.3.5.1-alpha - 2018-09-18
2672 Tor 0.3.5.1-alpha is the first release of the 0.3.5.x series. It adds
2673 client authorization for modern (v3) onion services, improves
2674 bootstrap reporting, begins reorganizing Tor's codebase, adds optional
2675 support for NSS in place of OpenSSL, and much more.
2677 o Major features (onion services, UI change):
2678 - For a newly created onion service, the default version is now 3.
2679 Tor still supports existing version 2 services, but the operator
2680 now needs to set "HiddenServiceVersion 2" in order to create a new
2681 version 2 service. For existing services, Tor now learns the
2682 version by reading the key file. Closes ticket 27215.
2684 o Major features (relay, UI change):
2685 - Relays no longer run as exits by default. If the "ExitRelay"
2686 option is auto (or unset), and no exit policy is specified with
2687 ExitPolicy or ReducedExitPolicy, we now treat ExitRelay as 0.
2688 Previously in this case, we allowed exit traffic and logged a
2689 warning message. Closes ticket 21530. Patch by Neel Chauhan.
2690 - Tor now validates that the ContactInfo config option is valid UTF-
2691 8 when parsing torrc. Closes ticket 27428.
2693 o Major features (bootstrap):
2694 - Don't report directory progress until after a connection to a
2695 relay or bridge has succeeded. Previously, we'd report 80%
2696 progress based on cached directory information when we couldn't
2697 even connect to the network. Closes ticket 27169.
2699 o Major features (new code layout):
2700 - Nearly all of Tor's source code has been moved around into more
2701 logical places. The "common" directory is now divided into a set
2702 of libraries in "lib", and files in the "or" directory have been
2703 split into "core" (logic absolutely needed for onion routing),
2704 "feature" (independent modules in Tor), and "app" (to configure
2705 and invoke the rest of Tor). See doc/HACKING/CodeStructure.md for
2706 more information. Closes ticket 26481.
2708 This refactoring is not complete: although the libraries have been
2709 refactored to be acyclic, the main body of Tor is still too
2710 interconnected. We will attempt to improve this in the future.
2712 o Major features (onion services v3):
2713 - Implement onion service client authorization at the descriptor
2714 level: only authorized clients can decrypt a service's descriptor
2715 to find out how to contact it. A new torrc option was added to
2716 control this client side: ClientOnionAuthDir <path>. On the
2717 service side, if the "authorized_clients/" directory exists in the
2718 onion service directory path, client configurations are read from
2719 the files within. See the manpage for more details. Closes ticket
2720 27547. Patch done by Suphanat Chunhapanya (haxxpop).
2721 - Improve revision counter generation in next-gen onion services.
2722 Onion services can now scale by hosting multiple instances on
2723 different hosts without synchronization between them, which was
2724 previously impossible because descriptors would get rejected by
2725 HSDirs. Addresses ticket 25552.
2727 o Major features (portability, cryptography, experimental, TLS):
2728 - Tor now has the option to compile with the NSS library instead of
2729 OpenSSL. This feature is experimental, and we expect that bugs may
2730 remain. It is mainly intended for environments where Tor's
2731 performance is not CPU-bound, and where NSS is already known to be
2732 installed. To try it out, configure Tor with the --enable-nss
2733 flag. Closes tickets 26631, 26815, and 26816.
2735 If you are experimenting with this option and using an old cached
2736 consensus, Tor may fail to start. To solve this, delete your
2737 "cached-consensus" and "cached-microdesc-consensus" files,
2738 (if present), and restart Tor.
2740 o Major bugfixes (directory authority):
2741 - Actually check that the address we get from DirAuthority
2742 configuration line is valid IPv4. Explicitly disallow DirAuthority
2743 address to be a DNS hostname. Fixes bug 26488; bugfix
2746 o Major bugfixes (restart-in-process):
2747 - Fix a use-after-free error that could be caused by passing Tor an
2748 impossible set of options that would fail during options_act().
2749 Fixes bug 27708; bugfix on 0.3.3.1-alpha.
2751 o Minor features (admin tools):
2752 - Add a new --key-expiration option to print the expiration date of
2753 the signing cert in an ed25519_signing_cert file. Resolves
2756 o Minor features (build):
2757 - If you pass the "--enable-pic" option to configure, Tor will try
2758 to tell the compiler to build position-independent code suitable
2759 to link into a dynamic library. (The default remains -fPIE, for
2760 code suitable for a relocatable executable.) Closes ticket 23846.
2762 o Minor features (code correctness, testing):
2763 - Tor's build process now includes a "check-includes" make target to
2764 verify that no module of Tor relies on any headers from a higher-
2765 level module. We hope to use this feature over time to help
2766 refactor our codebase. Closes ticket 26447.
2768 o Minor features (code layout):
2769 - We have a new "lowest-level" error-handling API for use by code
2770 invoked from within the logging module. With this interface, the
2771 logging code is no longer at risk of calling into itself if a
2772 failure occurs while it is trying to log something. Closes
2775 o Minor features (compilation):
2776 - Tor's configure script now supports a --with-malloc= option to
2777 select your malloc implementation. Supported options are
2778 "tcmalloc", "jemalloc", "openbsd" (deprecated), and "system" (the
2779 default). Addresses part of ticket 20424. Based on a patch from
2782 o Minor features (config):
2783 - The "auto" keyword in torrc is now case-insensitive. Closes
2786 o Minor features (continuous integration):
2787 - Don't do a distcheck with --disable-module-dirauth in Travis.
2788 Implements ticket 27252.
2789 - Install libcap-dev and libseccomp2-dev so these optional
2790 dependencies get tested on Travis CI. Closes ticket 26560.
2791 - Only run one online rust build in Travis, to reduce network
2792 errors. Skip offline rust builds on Travis for Linux gcc, because
2793 they're redundant. Implements ticket 27252.
2794 - Skip gcc on OSX in Travis CI, because it's rarely used. Skip a
2795 duplicate hardening-off build in Travis on Tor 0.2.9. Skip gcc on
2796 Linux with default settings, because all the non-default builds
2797 use gcc on Linux. Implements ticket 27252.
2799 o Minor features (controller):
2800 - Emit CIRC_BW events as soon as we detect that we processed an
2801 invalid or otherwise dropped cell on a circuit. This allows
2802 vanguards and other controllers to react more quickly to dropped
2803 cells. Closes ticket 27678.
2804 - For purposes of CIRC_BW-based dropped cell detection, track half-
2805 closed stream ids, and allow their ENDs, SENDMEs, DATA and path
2806 bias check cells to arrive without counting it as dropped until
2807 either the END arrives, or the windows are empty. Closes
2809 - Implement a 'GETINFO md/all' controller command to enable getting
2810 all known microdescriptors. Closes ticket 8323.
2811 - The GETINFO command now support an "uptime" argument, to return
2812 Tor's uptime in seconds. Closes ticket 25132.
2814 o Minor features (denial-of-service avoidance):
2815 - Make our OOM handler aware of the DNS cache so that it doesn't
2816 fill up the memory. This check is important for our DoS mitigation
2817 subsystem. Closes ticket 18642. Patch by Neel Chauhan.
2819 o Minor features (development):
2820 - Tor's makefile now supports running the "clippy" Rust style tool
2821 on our Rust code. Closes ticket 22156.
2823 o Minor features (directory authority):
2824 - There is no longer an artificial upper limit on the length of
2825 bandwidth lines. Closes ticket 26223.
2826 - When a bandwidth file is used to obtain the bandwidth measurements,
2827 include this bandwidth file headers in the votes. Closes
2829 - Improved support for networks with only a single authority or a
2830 single fallback directory. Patch from Gabriel Somlo. Closes
2833 o Minor features (embedding API):
2834 - The Tor controller API now supports a function to launch Tor with
2835 a preconstructed owning controller FD, so that embedding
2836 applications don't need to manage controller ports and
2837 authentication. Closes ticket 24204.
2838 - The Tor controller API now has a function that returns the name
2839 and version of the backend implementing the API. Closes
2842 o Minor features (geoip):
2843 - Update geoip and geoip6 to the September 6 2018 Maxmind GeoLite2
2844 Country database. Closes ticket 27631.
2846 o Minor features (memory management):
2847 - Get Libevent to use the same memory allocator as Tor, by calling
2848 event_set_mem_functions() during initialization. Resolves
2851 o Minor features (memory usage):
2852 - When not using them, store legacy TAP public onion keys in DER-
2853 encoded format, rather than as expanded public keys. This should
2854 save several megabytes on typical clients. Closes ticket 27246.
2856 o Minor features (OpenSSL):
2857 - When possible, use RFC5869 HKDF implementation from OpenSSL rather
2858 than our own. Resolves ticket 19979.
2860 o Minor features (Rust, code quality):
2861 - Improve rust code quality in the rust protover implementation by
2862 making it more idiomatic. Includes changing an internal API to
2863 take &str instead of &String. Closes ticket 26492.
2865 o Minor features (testing):
2866 - Add scripts/test/chutney-git-bisect.sh, for bisecting using
2867 chutney. Implements ticket 27211.
2869 o Minor features (tor-resolve):
2870 - The tor-resolve utility can now be used with IPv6 SOCKS proxies.
2871 Side-effect of the refactoring for ticket 26526.
2873 o Minor features (UI):
2874 - Log each included configuration file or directory as we read it,
2875 to provide more visibility about where Tor is reading from. Patch
2876 from Unto Sten; closes ticket 27186.
2877 - Lower log level of "Scheduler type KIST has been enabled" to INFO.
2878 Closes ticket 26703.
2880 o Minor bugfixes (bootstrap):
2881 - Try harder to get descriptors in non-exit test networks, by using
2882 the mid weight for the third hop when there are no exits. Fixes
2883 bug 27237; bugfix on 0.2.6.2-alpha.
2885 o Minor bugfixes (C correctness):
2886 - Avoid casting smartlist index to int implicitly, as it may trigger
2887 a warning (-Wshorten-64-to-32). Fixes bug 26282; bugfix on
2888 0.2.3.13-alpha, 0.2.7.1-alpha and 0.2.1.1-alpha.
2889 - Use time_t for all values in
2890 predicted_ports_prediction_time_remaining(). Rework the code that
2891 computes difference between durations/timestamps. Fixes bug 27165;
2892 bugfix on 0.3.1.1-alpha.
2894 o Minor bugfixes (client, memory usage):
2895 - When not running as a directory cache, there is no need to store
2896 the text of the current consensus networkstatus in RAM.
2897 Previously, however, clients would store it anyway, at a cost of
2898 over 5 MB. Now, they do not. Fixes bug 27247; bugfix
2901 o Minor bugfixes (client, reachableaddresses):
2902 - Instead of adding a "reject *:*" line to ReachableAddresses when
2903 loading the configuration, add one to the policy after parsing it
2904 in parse_reachable_addresses(). This prevents extra "reject *.*"
2905 lines from accumulating on reloads. Fixes bug 20874; bugfix on
2906 0.1.1.5-alpha. Patch by Neel Chauhan.
2908 o Minor bugfixes (code quality):
2909 - Rename sandbox_getaddrinfo() and other functions to no longer
2910 misleadingly suggest that they are sandbox-only. Fixes bug 26525;
2911 bugfix on 0.2.7.1-alpha.
2913 o Minor bugfixes (configuration, Onion Services):
2914 - In rend_service_parse_port_config(), disallow any input to remain
2915 after address-port pair was parsed. This will catch address and
2916 port being whitespace-separated by mistake of the user. Fixes bug
2917 27044; bugfix on 0.2.9.10.
2919 o Minor bugfixes (continuous integration):
2920 - Stop reinstalling identical packages in our Windows CI. Fixes bug
2921 27464; bugfix on 0.3.4.1-alpha.
2923 o Minor bugfixes (controller):
2924 - Consider all routerinfo errors other than "not a server" to be
2925 transient for the purpose of "GETINFO exit-policy/*" controller
2926 request. Print stacktrace in the unlikely case of failing to
2927 recompute routerinfo digest. Fixes bug 27034; bugfix
2930 o Minor bugfixes (directory connection shutdown):
2931 - Avoid a double-close when shutting down a stalled directory
2932 connection. Fixes bug 26896; bugfix on 0.3.4.1-alpha.
2934 o Minor bugfixes (HTTP tunnel):
2935 - Fix a bug warning when closing an HTTP tunnel connection due to an
2936 HTTP request we couldn't handle. Fixes bug 26470; bugfix
2939 o Minor bugfixes (ipv6):
2940 - In addrs_in_same_network_family(), we choose the subnet size based
2941 on the IP version (IPv4 or IPv6). Previously, we chose a fixed
2942 subnet size of /16 for both IPv4 and IPv6 addresses. Fixes bug
2943 15518; bugfix on 0.2.3.1-alpha. Patch by Neel Chauhan.
2945 o Minor bugfixes (logging):
2946 - As a precaution, do an early return from log_addr_has_changed() if
2947 Tor is running as client. Also, log a stack trace for debugging as
2948 this function should only be called when Tor runs as server. Fixes
2949 bug 26892; bugfix on 0.1.1.9-alpha.
2950 - Refrain from mentioning bug 21018 in the logs, as it is already
2951 fixed. Fixes bug 25477; bugfix on 0.2.9.8.
2953 o Minor bugfixes (logging, documentation):
2954 - When SafeLogging is enabled, scrub IP address in
2955 channel_tls_process_netinfo_cell(). Also, add a note to manpage
2956 that scrubbing is not guaranteed on loglevels below Notice. Fixes
2957 bug 26882; bugfix on 0.2.4.10-alpha.
2959 o Minor bugfixes (netflow padding):
2960 - Ensure circuitmux queues are empty before scheduling or sending
2961 padding. Fixes bug 25505; bugfix on 0.3.1.1-alpha.
2963 o Minor bugfixes (onion service v2):
2964 - Log at level "info", not "warning", in the case that we do not
2965 have a consensus when a .onion request comes in. This can happen
2966 normally while bootstrapping. Fixes bug 27040; bugfix
2969 o Minor bugfixes (onion service v3):
2970 - When the onion service directory can't be created or has the wrong
2971 permissions, do not log a stack trace. Fixes bug 27335; bugfix
2974 o Minor bugfixes (OS compatibility):
2975 - Properly handle configuration changes that move a listener to/from
2976 wildcard IP address. If the first attempt to bind a socket fails,
2977 close the old listener and try binding the socket again. Fixes bug
2978 17873; bugfix on 0.0.8pre-1.
2980 o Minor bugfixes (performance)::
2981 - Rework node_is_a_configured_bridge() to no longer call
2982 node_get_all_orports(), which was performing too many memory
2983 allocations. Fixes bug 27224; bugfix on 0.2.3.9.
2985 o Minor bugfixes (relay statistics):
2986 - Update relay descriptor on bandwidth changes only when the uptime
2987 is smaller than 24h, in order to reduce the efficiency of guard
2988 discovery attacks. Fixes bug 24104; bugfix on 0.1.1.6-alpha.
2990 o Minor bugfixes (relays):
2991 - Consider the fact that we'll be making direct connections to our
2992 entry and guard nodes when computing the fraction of nodes that
2993 have their descriptors. Also, if we are using bridges and there is
2994 at least one bridge with a full descriptor, treat the fraction of
2995 guards available as 100%. Fixes bug 25886; bugfix on 0.2.4.10-alpha.
2996 Patch by Neel Chauhan.
2997 - Update the message logged on relays when DirCache is disabled.
2998 Since 0.3.3.5-rc, authorities require DirCache (V2Dir) for the
2999 Guard flag. Fixes bug 24312; bugfix on 0.3.3.5-rc.
3001 o Minor bugfixes (rust, protover):
3002 - Compute protover votes correctly in the rust version of the
3003 protover code. Previously, the protover rewrite in 24031 allowed
3004 repeated votes from the same voter for the same protocol version
3005 to be counted multiple times in protover_compute_vote(). Fixes bug
3006 27649; bugfix on 0.3.3.5-rc.
3007 - Reject protover names that contain invalid characters. Fixes bug
3008 27687; bugfix on 0.3.3.1-alpha.
3010 o Minor bugfixes (testing):
3011 - Fix two unit tests to work when HOME environment variable is not
3012 set. Fixes bug 27096; bugfix on 0.2.8.1-alpha.
3013 - If a unit test running in a subprocess exits abnormally or with a
3014 nonzero status code, treat the test as having failed, even if the
3015 test reported success. Without this fix, memory leaks don't cause
3016 the tests to fail, even with LeakSanitizer. Fixes bug 27658;
3017 bugfix on 0.2.2.4-alpha.
3018 - When logging a version mismatch in our openssl_version tests,
3019 report the actual offending version strings. Fixes bug 26152;
3020 bugfix on 0.2.9.1-alpha.
3021 - Fix forking tests on Windows when there is a space somewhere in
3022 the path. Fixes bug 26437; bugfix on 0.2.2.4-alpha.
3024 o Code simplification and refactoring:
3025 - 'updateFallbackDirs.py' now ignores the blacklist file, as it's not
3026 longer needed. Closes ticket 26502.
3027 - Include paths to header files within Tor are now qualified by
3028 directory within the top-level src directory.
3029 - Many structures have been removed from the centralized "or.h"
3030 header, and moved into their own headers. This will allow us to
3031 reduce the number of places in the code that rely on each
3032 structure's contents and layout. Closes ticket 26383.
3033 - Remove ATTR_NONNULL macro from codebase. Resolves ticket 26527.
3034 - Remove GetAdaptersAddresses_fn_t. The code that used it was
3035 removed as part of the 26481 refactor. Closes ticket 27467.
3036 - Rework Tor SOCKS server code to use Trunnel and benefit from
3037 autogenerated functions for parsing and generating SOCKS wire
3038 format. New implementation is cleaner, more maintainable and
3039 should be less prone to heartbleed-style vulnerabilities.
3040 Implements a significant fraction of ticket 3569.
3041 - Split sampled_guards_update_from_consensus() and
3042 select_entry_guard_for_circuit() into subfunctions. In
3043 entry_guards_update_primary() unite three smartlist enumerations
3044 into one and move smartlist comparison code out of the function.
3045 Closes ticket 21349.
3046 - Tor now assumes that you have standards-conformant stdint.h and
3047 inttypes.h headers when compiling. Closes ticket 26626.
3048 - Unify our bloom filter logic. Previously we had two copies of this
3049 code: one for routerlist filtering, and one for address set
3050 calculations. Closes ticket 26510.
3051 - Use the simpler strcmpstart() helper in
3052 rend_parse_v2_service_descriptor instead of strncmp(). Closes
3054 - Utility functions that can perform a DNS lookup are now wholly
3055 separated from those that can't, in separate headers and C
3056 modules. Closes ticket 26526.
3059 - Copy paragraph and URL to Tor's code of conduct document from
3060 CONTRIBUTING to new CODE_OF_CONDUCT file. Resolves ticket 26638.
3061 - Remove old instructions from INSTALL document. Closes ticket 26588.
3062 - Warn users that they should not include MyFamily line(s) in their
3063 torrc when running Tor bridge. Closes ticket 26908.
3066 - Tor no longer supports building with the dmalloc library. For
3067 debugging memory issues, we suggest using gperftools or msan
3068 instead. Closes ticket 26426.
3069 - Tor no longer attempts to run on Windows environments without the
3070 GetAdaptersAddresses() function. This function has existed since
3071 Windows XP, which is itself already older than we support.
3072 - Remove Tor2web functionality for version 2 onion services. The
3073 Tor2webMode and Tor2webRendezvousPoints options are now obsolete.
3074 (This feature was never shipped in vanilla Tor and it was only
3075 possible to use this feature by building the support at compile
3076 time. Tor2webMode is not implemented for version 3 onion services.)
3077 Closes ticket 26367.
3080 Changes in version 0.2.9.17 - 2018-09-10
3081 Tor 0.2.9.17 backports numerous bugfixes from later versions of Tor.
3083 o Minor features (compatibility, backport from 0.3.4.8):
3084 - Tell OpenSSL to maintain backward compatibility with previous
3085 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3086 ciphers are disabled by default. Closes ticket 27344.
3088 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3089 - Enable macOS builds in our Travis CI configuration. Closes
3091 - Install libcap-dev and libseccomp2-dev so these optional
3092 dependencies get tested on Travis CI. Closes ticket 26560.
3093 - Run asciidoc during Travis CI. Implements ticket 27087.
3094 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3096 o Minor features (geoip):
3097 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3098 Country database. Closes ticket 27089.
3100 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3101 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3102 tell the compiler not to include the system malloc implementation.
3103 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3105 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3106 - Silence a spurious compiler warning on the GetAdaptersAddresses
3107 function pointer cast. This issue is already fixed by 26481 in
3108 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3109 bugfix on 0.2.3.11-alpha.
3110 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3111 supported, and always fails. Some compilers warn about the
3112 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3115 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3116 - Don't link or search for pthreads when building for Windows, even
3117 if we are using build environment (like mingw) that provides a
3118 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3120 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3121 - Skip a pair of unreliable key generation tests on Windows, until
3122 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3123 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3125 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3126 - Pass the module flags to distcheck configure, and log the flags
3127 before running configure. (Backported to 0.2.9 and later as a
3128 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3130 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3131 - When a Travis build fails, and showing a log fails, keep trying to
3132 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3133 - When we use echo in Travis, don't pass a --flag as the first
3134 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3136 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3137 - When voting for recommended versions, make sure that all of the
3138 versions are well-formed and parsable. Fixes bug 26485; bugfix
3141 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3142 - Fix a bug in out sandboxing rules for the openat() syscall.
3143 Previously, no openat() call would be permitted, which would break
3144 filesystem operations on recent glibc versions. Fixes bug 25440;
3145 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3147 o Minor bugfixes (onion services, backport from 0.3.4.8):
3148 - Silence a spurious compiler warning in
3149 rend_client_send_introduction(). Fixes bug 27463; bugfix
3152 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3153 - Log a protocol warning when single onion services or Tor2web clients
3154 fail to authenticate direct connections to relays.
3155 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3157 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3158 - Disable core dumps in test_bt.sh, to avoid failures in "make
3159 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3161 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3162 - Before running make test-network-all, delete old logs and test
3163 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3166 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3167 - Our "tortls/cert_matches_key" unit test no longer relies on
3168 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3169 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3170 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3172 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3173 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3174 27185; bugfix on 0.2.2.2-alpha.
3177 Changes in version 0.3.2.12 - 2018-09-10
3178 Tor 0.3.2.12 backport numerous fixes from later versions of Tor.
3180 o Minor features (compatibility, backport from 0.3.4.8):
3181 - Tell OpenSSL to maintain backward compatibility with previous
3182 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3183 ciphers are disabled by default. Closes ticket 27344.
3185 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3186 - Enable macOS builds in our Travis CI configuration. Closes
3188 - Install libcap-dev and libseccomp2-dev so these optional
3189 dependencies get tested on Travis CI. Closes ticket 26560.
3190 - Run asciidoc during Travis CI. Implements ticket 27087.
3191 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3193 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3194 - Use cargo cache in our Travis CI configuration. Closes
3197 o Minor features (controller, backport from 0.3.4.6-rc):
3198 - The control port now exposes the list of HTTPTunnelPorts and
3199 ExtOrPorts via GETINFO net/listeners/httptunnel and
3200 net/listeners/extor respectively. Closes ticket 26647.
3202 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3203 - Authorities no longer vote to make the subprotocol version
3204 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3205 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3207 o Minor features (geoip):
3208 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3209 Country database. Closes ticket 27089.
3211 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3212 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3213 tell the compiler not to include the system malloc implementation.
3214 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3215 - Don't try to use a pragma to temporarily disable the
3216 -Wunused-const-variable warning if the compiler doesn't support
3217 it. Fixes bug 26785; bugfix on 0.3.2.11.
3219 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3220 - Silence a spurious compiler warning on the GetAdaptersAddresses
3221 function pointer cast. This issue is already fixed by 26481 in
3222 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3223 bugfix on 0.2.3.11-alpha.
3224 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3225 supported, and always fails. Some compilers warn about the
3226 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3229 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3230 - Don't link or search for pthreads when building for Windows, even
3231 if we are using build environment (like mingw) that provides a
3232 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3234 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3235 - Skip a pair of unreliable key generation tests on Windows, until
3236 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3237 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3239 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3240 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3241 - Pass the module flags to distcheck configure, and log the flags
3242 before running configure. (Backported to 0.2.9 and later as a
3243 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3245 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3246 - When a Travis build fails, and showing a log fails, keep trying to
3247 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3248 - When we use echo in Travis, don't pass a --flag as the first
3249 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3251 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3252 - When voting for recommended versions, make sure that all of the
3253 versions are well-formed and parsable. Fixes bug 26485; bugfix
3256 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3257 - Fix a bug in out sandboxing rules for the openat() syscall.
3258 Previously, no openat() call would be permitted, which would break
3259 filesystem operations on recent glibc versions. Fixes bug 25440;
3260 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3262 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3263 - Improve the log message when connection initiators fail to
3264 authenticate direct connections to relays. Fixes bug 26927; bugfix
3267 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3268 - Fix bug that causes services to not ever rotate their descriptors
3269 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3272 o Minor bugfixes (onion services, backport from 0.3.4.8):
3273 - Silence a spurious compiler warning in
3274 rend_client_send_introduction(). Fixes bug 27463; bugfix
3277 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3278 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3280 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3281 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3282 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3283 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3285 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3286 - Log a protocol warning when single onion services or Tor2web clients
3287 fail to authenticate direct connections to relays.
3288 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3290 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3291 - Disable core dumps in test_bt.sh, to avoid failures in "make
3292 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3294 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3295 - When running make test-network-all, use the mixed+hs-v2 network.
3296 (A previous fix to chutney removed v3 onion services from the
3297 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3298 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3299 - Before running make test-network-all, delete old logs and test
3300 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3303 o Minor bugfixes (testing, openssl compatibility):
3304 - Our "tortls/cert_matches_key" unit test no longer relies on OpenSSL
3305 internals. Previously, it relied on unsupported OpenSSL behavior in
3306 a way that caused it to crash with OpenSSL 1.0.2p. Fixes bug 27226;
3307 bugfix on 0.2.5.1-alpha.
3309 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3310 - Our "tortls/cert_matches_key" unit test no longer relies on
3311 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3312 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3313 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3315 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3316 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3317 27185; bugfix on 0.2.2.2-alpha.
3320 Changes in version 0.3.3.10 - 2018-09-10
3321 Tor 0.3.3.10 backports numerous fixes from later versions of Tor.
3323 o Minor features (bug workaround, backport from 0.3.4.7-rc):
3324 - Compile correctly on systems that provide the C11 stdatomic.h
3325 header, but where C11 atomic functions don't actually compile.
3326 Closes ticket 26779; workaround for Debian issue 903709.
3328 o Minor features (compatibility, backport from 0.3.4.8):
3329 - Tell OpenSSL to maintain backward compatibility with previous
3330 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3331 ciphers are disabled by default. Closes ticket 27344.
3333 o Minor features (continuous integration, backport from 0.3.4.7-rc):
3334 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3335 - Enable macOS builds in our Travis CI configuration. Closes
3337 - Install libcap-dev and libseccomp2-dev so these optional
3338 dependencies get tested on Travis CI. Closes ticket 26560.
3339 - Run asciidoc during Travis CI. Implements ticket 27087.
3340 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3342 o Minor features (continuous integration, rust, backport from 0.3.4.7-rc):
3343 - Use cargo cache in our Travis CI configuration. Closes
3346 o Minor features (controller, backport from 0.3.4.6-rc):
3347 - The control port now exposes the list of HTTPTunnelPorts and
3348 ExtOrPorts via GETINFO net/listeners/httptunnel and
3349 net/listeners/extor respectively. Closes ticket 26647.
3351 o Minor features (directory authorities, backport from 0.3.4.7-rc):
3352 - Authorities no longer vote to make the subprotocol version
3353 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3354 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3356 o Minor features (geoip):
3357 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3358 Country database. Closes ticket 27089.
3360 o Minor bugfixes (compilation, backport from 0.3.4.6-rc):
3361 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3362 tell the compiler not to include the system malloc implementation.
3363 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3364 - Don't try to use a pragma to temporarily disable the
3365 -Wunused-const-variable warning if the compiler doesn't support
3366 it. Fixes bug 26785; bugfix on 0.3.2.11.
3368 o Minor bugfixes (compilation, backport from 0.3.4.7-rc):
3369 - Silence a spurious compiler warning on the GetAdaptersAddresses
3370 function pointer cast. This issue is already fixed by 26481 in
3371 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3372 bugfix on 0.2.3.11-alpha.
3373 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3374 supported, and always fails. Some compilers warn about the
3375 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3378 o Minor bugfixes (compilation, windows, backport from 0.3.4.7-rc):
3379 - Don't link or search for pthreads when building for Windows, even
3380 if we are using build environment (like mingw) that provides a
3381 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3383 o Minor bugfixes (continuous integration, backport from 0.3.4.6-rc):
3384 - Skip a pair of unreliable key generation tests on Windows, until
3385 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3386 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3388 o Minor bugfixes (continuous integration, backport from 0.3.4.7-rc):
3389 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3390 - Pass the module flags to distcheck configure, and log the flags
3391 before running configure. (Backported to 0.2.9 and later as a
3392 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3394 o Minor bugfixes (continuous integration, backport from 0.3.4.8):
3395 - When a Travis build fails, and showing a log fails, keep trying to
3396 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3397 - When we use echo in Travis, don't pass a --flag as the first
3398 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3400 o Minor bugfixes (directory authority, backport from 0.3.4.6-rc):
3401 - When voting for recommended versions, make sure that all of the
3402 versions are well-formed and parsable. Fixes bug 26485; bugfix
3405 o Minor bugfixes (in-process restart, backport from 0.3.4.7-rc):
3406 - Always call tor_free_all() when leaving tor_run_main(). When we
3407 did not, restarting tor in-process would cause an assertion
3408 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3410 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.4.7-rc):
3411 - Fix a bug in our sandboxing rules for the openat() syscall.
3412 Previously, no openat() call would be permitted, which would break
3413 filesystem operations on recent glibc versions. Fixes bug 25440;
3414 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3416 o Minor bugfixes (logging, backport from 0.3.4.6-rc):
3417 - Improve the log message when connection initiators fail to
3418 authenticate direct connections to relays. Fixes bug 26927; bugfix
3421 o Minor bugfixes (onion services, backport from 0.3.4.7-rc):
3422 - Fix bug that causes services to not ever rotate their descriptors
3423 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3426 o Minor bugfixes (onion services, backport from 0.3.4.8):
3427 - Silence a spurious compiler warning in
3428 rend_client_send_introduction(). Fixes bug 27463; bugfix
3431 o Minor bugfixes (portability, backport from 0.3.4.6-rc):
3432 - Work around two different bugs in the OS X 10.10 and later SDKs
3433 that would prevent us from successfully targeting earlier versions
3434 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3436 o Minor bugfixes (portability, backport from 0.3.4.7-rc):
3437 - Fix compilation of the unit tests on GNU/Hurd, which does not
3438 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3441 o Minor bugfixes (rust, backport from 0.3.4.7-rc):
3442 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3444 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3445 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3446 - Protover parsing was accepting the presence of whitespace in
3447 version strings, which the C implementation would choke on, e.g.
3448 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3449 - Protover parsing was ignoring a 2nd hyphen and everything after
3450 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3452 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3453 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3454 - cd to ${abs_top_builddir}/src/rust before running cargo in
3455 src/test/test_rust.sh. This makes the working directory consistent
3456 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3458 o Minor bugfixes (single onion services, Tor2web, backport from 0.3.4.6-rc):
3459 - Log a protocol warning when single onion services or Tor2web clients
3460 fail to authenticate direct connections to relays.
3461 Fixes bug 26924; bugfix on 0.2.9.1-alpha.
3463 o Minor bugfixes (testing, backport from 0.3.4.6-rc):
3464 - Disable core dumps in test_bt.sh, to avoid failures in "make
3465 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3467 o Minor bugfixes (testing, chutney, backport from 0.3.4.8):
3468 - When running make test-network-all, use the mixed+hs-v2 network.
3469 (A previous fix to chutney removed v3 onion services from the
3470 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3471 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3472 - Before running make test-network-all, delete old logs and test
3473 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3476 o Minor bugfixes (testing, openssl compatibility, backport from 0.3.4.7-rc):
3477 - Our "tortls/cert_matches_key" unit test no longer relies on
3478 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3479 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3480 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3482 o Minor bugfixes (v3 onion services, backport from 0.3.4.6-rc):
3483 - Stop sending ed25519 link specifiers in v3 onion service introduce
3484 cells and descriptors, when the rendezvous or introduction point
3485 doesn't support ed25519 link authentication. Fixes bug 26627;
3486 bugfix on 0.3.2.4-alpha.
3488 o Minor bugfixes (Windows, compilation, backport from 0.3.4.7-rc):
3489 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3490 27185; bugfix on 0.2.2.2-alpha.
3493 Changes in version 0.3.4.8 - 2018-09-10
3494 Tor 0.3.4.8 is the first stable release in its series; it includes
3495 compilation and portability fixes.
3497 The Tor 0.3.4 series includes improvements for running Tor in
3498 low-power and embedded environments, which should help performance in
3499 general. We've begun work on better modularity, and included preliminary
3500 changes on the directory authority side to accommodate a new bandwidth
3501 measurement system. We've also integrated more continuous-integration
3502 systems into our development process, and made corresponding changes to
3503 Tor's testing infrastructure. Finally, we've continued to refine
3504 our anti-denial-of-service code.
3506 Below are the changes since 0.3.4.7-rc. For a complete list of changes
3507 since 0.3.3.9, see the ReleaseNotes file.
3509 o Minor features (compatibility):
3510 - Tell OpenSSL to maintain backward compatibility with previous
3511 RSA1024/DH1024 users in Tor. With OpenSSL 1.1.1-pre6, these
3512 ciphers are disabled by default. Closes ticket 27344.
3514 o Minor features (continuous integration):
3515 - Log the compiler path and version during Appveyor builds.
3516 Implements ticket 27449.
3517 - Show config.log and test-suite.log after failed Appveyor builds.
3518 Also upload the zipped full logs as a build artifact. Implements
3521 o Minor bugfixes (compilation):
3522 - Silence a spurious compiler warning on the GetAdaptersAddresses
3523 function pointer cast. This issue is already fixed by 26481 in
3524 0.3.5 and later, by removing the lookup and cast. Fixes bug 27465;
3525 bugfix on 0.2.3.11-alpha.
3526 - Stop calling SetProcessDEPPolicy() on 64-bit Windows. It is not
3527 supported, and always fails. Some compilers warn about the
3528 function pointer cast on 64-bit Windows. Fixes bug 27461; bugfix
3531 o Minor bugfixes (continuous integration):
3532 - Disable gcc hardening in Appveyor Windows 64-bit builds. As of
3533 August 29 2018, Appveyor images come with gcc 8.2.0 by default.
3534 Executables compiled for 64-bit Windows with this version of gcc
3535 crash when Tor's --enable-gcc-hardening flag is set. Fixes bug
3536 27460; bugfix on 0.3.4.1-alpha.
3537 - When a Travis build fails, and showing a log fails, keep trying to
3538 show the other logs. Fixes bug 27453; bugfix on 0.3.4.7-rc.
3539 - When we use echo in Travis, don't pass a --flag as the first
3540 argument. Fixes bug 27418; bugfix on 0.3.4.7-rc.
3542 o Minor bugfixes (onion services):
3543 - Silence a spurious compiler warning in
3544 rend_client_send_introduction(). Fixes bug 27463; bugfix
3547 o Minor bugfixes (testing, chutney):
3548 - When running make test-network-all, use the mixed+hs-v2 network.
3549 (A previous fix to chutney removed v3 onion services from the
3550 mixed+hs-v23 network, so seeing "mixed+hs-v23" in tests is
3551 confusing.) Fixes bug 27345; bugfix on 0.3.2.1-alpha.
3552 - Before running make test-network-all, delete old logs and test
3553 result files, to avoid spurious failures. Fixes bug 27295; bugfix
3556 Changes in version 0.3.4.7-rc - 2018-08-24
3557 Tor 0.3.4.7-rc fixes several small compilation, portability, and
3558 correctness issues in previous versions of Tor. This version is a
3559 release candidate: if no serious bugs are found, we expect that the
3560 stable 0.3.4 release will be (almost) the same as this release.
3562 o Minor features (bug workaround):
3563 - Compile correctly on systems that provide the C11 stdatomic.h
3564 header, but where C11 atomic functions don't actually compile.
3565 Closes ticket 26779; workaround for Debian issue 903709.
3567 o Minor features (continuous integration):
3568 - Backport Travis rust distcheck to 0.3.3. Closes ticket 24629.
3569 - Enable macOS builds in our Travis CI configuration. Closes
3571 - Install libcap-dev and libseccomp2-dev so these optional
3572 dependencies get tested on Travis CI. Closes ticket 26560.
3573 - Only post Appveyor IRC notifications when the build fails.
3574 Implements ticket 27275.
3575 - Run asciidoc during Travis CI. Implements ticket 27087.
3576 - Use ccache in our Travis CI configuration. Closes ticket 26952.
3578 o Minor features (continuous integration, rust):
3579 - Use cargo cache in our Travis CI configuration. Closes
3582 o Minor features (directory authorities):
3583 - Authorities no longer vote to make the subprotocol version
3584 "LinkAuth=1" a requirement: it is unsupportable with NSS, and
3585 hasn't been needed since Tor 0.3.0.1-alpha. Closes ticket 27286.
3587 o Minor features (geoip):
3588 - Update geoip and geoip6 to the August 7 2018 Maxmind GeoLite2
3589 Country database. Closes ticket 27089.
3591 o Minor bugfixes (compilation, windows):
3592 - Don't link or search for pthreads when building for Windows, even
3593 if we are using build environment (like mingw) that provides a
3594 pthreads library. Fixes bug 27081; bugfix on 0.1.0.1-rc.
3596 o Minor bugfixes (continuous integration):
3597 - Improve Appveyor CI IRC logging. Generate correct branches and
3598 URLs for pull requests and tags. Use unambiguous short commits.
3599 Fixes bug 26979; bugfix on master.
3600 - Build with zstd on macOS. Fixes bug 27090; bugfix on 0.3.1.5-alpha.
3601 - Pass the module flags to distcheck configure, and log the flags
3602 before running configure. (Backported to 0.2.9 and later as a
3603 precaution.) Fixes bug 27088; bugfix on 0.3.4.1-alpha.
3605 o Minor bugfixes (in-process restart):
3606 - Always call tor_free_all() when leaving tor_run_main(). When we
3607 did not, restarting tor in-process would cause an assertion
3608 failure. Fixes bug 26948; bugfix on 0.3.3.1-alpha.
3610 o Minor bugfixes (linux seccomp2 sandbox):
3611 - Fix a bug in out sandboxing rules for the openat() syscall.
3612 Previously, no openat() call would be permitted, which would break
3613 filesystem operations on recent glibc versions. Fixes bug 25440;
3614 bugfix on 0.2.9.15. Diagnosis and patch from Daniel Pinto.
3616 o Minor bugfixes (onion services):
3617 - Fix bug that causes services to not ever rotate their descriptors
3618 if they were getting SIGHUPed often. Fixes bug 26932; bugfix
3621 o Minor bugfixes (portability):
3622 - Fix compilation of the unit tests on GNU/Hurd, which does not
3623 define PATH_MAX. Fixes bug 26873; bugfix on 0.3.3.1-alpha. Patch
3626 o Minor bugfixes (rust):
3627 - Backport test_rust.sh from master. Fixes bug 26497; bugfix
3629 - Consistently use ../../.. as a fallback for $abs_top_srcdir in
3630 test_rust.sh. Fixes bug 27093; bugfix on 0.3.4.3-alpha.
3631 - Protover parsing was accepting the presence of whitespace in
3632 version strings, which the C implementation would choke on, e.g.
3633 "Desc=1\t,2". Fixes bug 27177; bugfix on 0.3.3.5-rc.
3634 - Protover parsing was ignoring a 2nd hyphen and everything after
3635 it, accepting entries like "Link=1-5-foo". Fixes bug 27164; bugfix
3637 - Stop setting $CARGO_HOME. cargo will use the user's $CARGO_HOME, or
3638 $HOME/.cargo by default. Fixes bug 26497; bugfix on 0.3.1.5-alpha.
3639 - cd to ${abs_top_builddir}/src/rust before running cargo in
3640 src/test/test_rust.sh. This makes the working directory consistent
3641 between builds and tests. Fixes bug 26497; bugfix on 0.3.3.2-alpha.
3643 o Minor bugfixes (testing, bootstrap):
3644 - When calculating bootstrap progress, check exit policies and the
3645 exit flag. Previously, Tor would only check the exit flag, which
3646 caused race conditions in small and fast networks like chutney.
3647 Fixes bug 27236; bugfix on 0.2.6.3-alpha.
3649 o Minor bugfixes (testing, openssl compatibility):
3650 - Our "tortls/cert_matches_key" unit test no longer relies on
3651 OpenSSL internals. Previously, it relied on unsupported OpenSSL
3652 behavior in a way that caused it to crash with OpenSSL 1.0.2p.
3653 Fixes bug 27226; bugfix on 0.2.5.1-alpha.
3655 o Minor bugfixes (Windows, compilation):
3656 - Silence a compilation warning on MSVC 2017 and clang-cl. Fixes bug
3657 27185; bugfix on 0.2.2.2-alpha.
3660 Changes in version 0.3.4.6-rc - 2018-08-06
3661 Tor 0.3.4.6-rc fixes several small compilation, portability, and
3662 correctness issues in previous versions of Tor. This version is a
3663 release candidate: if no serious bugs are found, we expect that the
3664 stable 0.3.4 release will be (almost) the same as this release.
3666 o Major bugfixes (event scheduler):
3667 - When we enable a periodic event, schedule it in the event loop
3668 rather than running it immediately. Previously, we would re-run
3669 periodic events immediately in the middle of (for example)
3670 changing our options, with unpredictable effects. Fixes bug 27003;
3671 bugfix on 0.3.4.1-alpha.
3673 o Minor features (compilation):
3674 - When building Tor, prefer to use Python 3 over Python 2, and more
3675 recent (contemplated) versions over older ones. Closes
3677 - When compiling with --enable-openbsd-malloc or --enable-tcmalloc,
3678 tell the compiler not to include the system malloc implementation.
3679 Fixes bug 20424; bugfix on 0.2.0.20-rc.
3680 - Don't try to use a pragma to temporarily disable the
3681 -Wunused-const-variable warning if the compiler doesn't support
3682 it. Fixes bug 26785; bugfix on 0.3.2.11.
3684 o Minor bugfixes (continuous integration):
3685 - Skip a pair of unreliable key generation tests on Windows, until
3686 the underlying issue in bug 26076 is resolved. Fixes bug 26830 and
3687 bug 26853; bugfix on 0.2.7.3-rc and 0.3.2.1-alpha respectively.
3689 o Minor features (controller):
3690 - The control port now exposes the list of HTTPTunnelPorts and
3691 ExtOrPorts via GETINFO net/listeners/httptunnel and
3692 net/listeners/extor respectively. Closes ticket 26647.
3694 o Minor bugfixes (directory authority):
3695 - When voting for recommended versions, make sure that all of the
3696 versions are well-formed and parsable. Fixes bug 26485; bugfix
3699 o Minor features (geoip):
3700 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3701 Country database. Closes ticket 26674.
3703 o Minor features (Rust, portability):
3704 - Rust cross-compilation is now supported. Closes ticket 25895.
3706 o Minor bugfixes (compilation):
3707 - Update build system so that tor builds again with --disable-unittests
3708 after recent refactoring. Fixes bug 26789; bugfix on 0.3.4.3-alpha.
3709 - Fix a compilation warning on some versions of GCC when building
3710 code that calls routerinfo_get_my_routerinfo() twice, assuming
3711 that the second call will succeed if the first one did. Fixes bug
3712 26269; bugfix on 0.2.8.2-alpha.
3714 o Minor bugfixes (controller):
3715 - Report the port correctly when a port is configured to bind to
3716 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
3717 - Parse the "HSADDRESS=" parameter in HSPOST commands properly.
3718 Previously, it was misparsed and ignored. Fixes bug 26523; bugfix
3719 on 0.3.3.1-alpha. Patch by "akwizgran".
3721 o Minor bugfixes (correctness, flow control):
3722 - Upon receiving a stream-level SENDME cell, verify that our window
3723 has not grown too large. Fixes bug 26214; bugfix on svn
3726 o Minor bugfixes (memory, correctness):
3727 - Fix a number of small memory leaks identified by coverity. Fixes
3728 bug 26467; bugfix on numerous Tor versions.
3730 o Minor bugfixes (logging):
3731 - Improve the log message when connection initiators fail to
3732 authenticate direct connections to relays. Fixes bug 26927; bugfix
3735 o Minor bugfixes (portability):
3736 - Avoid a compilation error in test_bwmgt.c on Solaris 10. Fixes bug
3737 26994; bugfix on 0.3.4.1-alpha.
3738 - Work around two different bugs in the OS X 10.10 and later SDKs
3739 that would prevent us from successfully targeting earlier versions
3740 of OS X. Fixes bug 26876; bugfix on 0.3.3.1-alpha.
3742 o Minor bugfixes (single onion services, Tor2web):
3743 - Log a protocol warning when single onion services or Tor2web
3744 clients fail to authenticate direct connections to relays. Fixes
3745 bug 26924; bugfix on 0.2.9.1-alpha.
3747 o Minor bugfixes (testing):
3748 - Disable core dumps in test_bt.sh, to avoid failures in "make
3749 distcheck". Fixes bug 26787; bugfix on 0.2.5.2-alpha.
3751 o Minor bugfixes (testing, compatibility):
3752 - When running the ntor_ref.py and hs_ntor_ref.py tests, make sure
3753 only to pass strings (rather than "bytes" objects) to the Python
3754 subprocess module. Python 3 on Windows seems to require this.
3755 Fixes bug 26535; bugfix on 0.2.5.5-alpha (for ntor_ref.py) and
3756 0.3.1.1-alpha (for hs_ntor_ref.py).
3758 o Minor bugfixes (v3 onion services):
3759 - Stop sending ed25519 link specifiers in v3 onion service introduce
3760 cells and descriptors, when the rendezvous or introduction point
3761 doesn't support ed25519 link authentication. Fixes bug 26627;
3762 bugfix on 0.3.2.4-alpha.
3765 Changes in version 0.3.4.5-rc - 2018-07-13
3766 Tor 0.3.4.5-rc moves to a new bridge authority, meaning people running
3767 bridge relays should upgrade.
3769 o Directory authority changes:
3770 - The "Bifroest" bridge authority has been retired; the new bridge
3771 authority is "Serge", and it is operated by George from the
3772 TorBSD project. Closes ticket 26771.
3775 Changes in version 0.3.3.9 - 2018-07-13
3776 Tor 0.3.3.9 moves to a new bridge authority, meaning people running
3777 bridge relays should upgrade.
3779 o Directory authority changes:
3780 - The "Bifroest" bridge authority has been retired; the new bridge
3781 authority is "Serge", and it is operated by George from the
3782 TorBSD project. Closes ticket 26771.
3785 Changes in version 0.3.2.11 - 2018-07-13
3786 Tor 0.3.2.11 moves to a new bridge authority, meaning people running
3787 bridge relays should upgrade. We also take this opportunity to backport
3790 o Directory authority changes:
3791 - The "Bifroest" bridge authority has been retired; the new bridge
3792 authority is "Serge", and it is operated by George from the
3793 TorBSD project. Closes ticket 26771.
3795 o Directory authority changes (backport from 0.3.3.7):
3796 - Add an IPv6 address for the "dannenberg" directory authority.
3797 Closes ticket 26343.
3799 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3800 - When directory authorities read a zero-byte bandwidth file, they
3801 would previously log a warning with the contents of an
3802 uninitialised buffer. They now log a warning about the empty file
3803 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3805 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
3806 - Correctly detect when onion services get disabled after HUP. Fixes
3807 bug 25761; bugfix on 0.3.2.1.
3809 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3810 - Explicitly permit the poll() system call when the Linux
3811 seccomp2-based sandbox is enabled: apparently, some versions of
3812 libc use poll() when calling getpwnam(). Closes ticket 25313.
3814 o Minor feature (continuous integration, backport from 0.3.3.5-rc):
3815 - Update the Travis CI configuration to use the stable Rust channel,
3816 now that we have decided to require that. Closes ticket 25714.
3818 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3819 - Our .travis.yml configuration now includes support for testing the
3820 results of "make distcheck". (It's not uncommon for "make check"
3821 to pass but "make distcheck" to fail.) Closes ticket 25814.
3822 - Our Travis CI configuration now integrates with the Coveralls
3823 coverage analysis tool. Closes ticket 25818.
3825 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
3826 - Add several checks to detect whether Tor relays are uploading
3827 their descriptors without specifying why they regenerated them.
3828 Diagnostic for ticket 25686.
3830 o Minor features (compilation, backport from 0.3.4.4-rc):
3831 - When building Tor, prefer to use Python 3 over Python 2, and more
3832 recent (contemplated) versions over older ones. Closes
3835 o Minor features (geoip):
3836 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3837 Country database. Closes ticket 26674.
3839 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3840 - Upon receiving a malformed connected cell, stop processing the
3841 cell immediately. Previously we would mark the connection for
3842 close, but continue processing the cell as if the connection were
3843 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3845 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3846 - Allow the nanosleep() system call, which glibc uses to implement
3847 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3849 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3850 - When running the hs_ntor_ref.py test, make sure only to pass
3851 strings (rather than "bytes" objects) to the Python subprocess
3852 module. Python 3 on Windows seems to require this. Fixes bug
3853 26535; bugfix on 0.3.1.1-alpha.
3854 - When running the ntor_ref.py test, make sure only to pass strings
3855 (rather than "bytes" objects) to the Python subprocess module.
3856 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3859 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3860 - Work around a change in OpenSSL 1.1.1 where return values that
3861 would previously indicate "no password" now indicate an empty
3862 password. Without this workaround, Tor instances running with
3863 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3864 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3866 o Minor bugfixes (documentation, backport from 0.3.3.5-rc):
3867 - Document that the PerConnBW{Rate,Burst} options will fall back to
3868 their corresponding consensus parameters only if those parameters
3869 are set. Previously we had claimed that these values would always
3870 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
3872 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3873 - Fix a compilation warning on some versions of GCC when building
3874 code that calls routerinfo_get_my_routerinfo() twice, assuming
3875 that the second call will succeed if the first one did. Fixes bug
3876 26269; bugfix on 0.2.8.2-alpha.
3878 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
3879 - Don't consider Tor running as a client if the ControlPort is open,
3880 but no actual client ports are open. Fixes bug 26062; bugfix
3883 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
3884 - Prevent a possible out-of-bounds smartlist read in
3885 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
3887 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
3888 - Fix a very unlikely (impossible, we believe) null pointer
3889 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
3890 Coverity; this is CID 1430932.
3892 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
3893 - Fix a memory leak when a v3 onion service is configured and gets a
3894 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
3895 - When parsing the descriptor signature, look for the token plus an
3896 extra white-space at the end. This is more correct but also will
3897 allow us to support new fields that might start with "signature".
3898 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
3900 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
3901 - Relays now correctly block attempts to re-extend to the previous
3902 relay by Ed25519 identity. Previously they would warn in this
3903 case, but not actually reject the attempt. Fixes bug 26158; bugfix
3906 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
3907 - Avoid a crash when running with DirPort set but ORPort turned off.
3908 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
3910 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
3911 - Silence unused-const-variable warnings in zstd.h with some GCC
3912 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
3914 o Minor bugfixes (testing, backport from 0.3.3.4-alpha):
3915 - Avoid intermittent test failures due to a test that had relied on
3916 onion service introduction point creation finishing within 5
3917 seconds of real clock time. Fixes bug 25450; bugfix
3920 o Minor bugfixes (compilation, backport from 0.3.3.4-alpha):
3921 - Fix a C99 compliance issue in our configuration script that caused
3922 compilation issues when compiling Tor with certain versions of
3923 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
3925 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
3926 - Fix a number of small memory leaks identified by coverity. Fixes
3927 bug 26467; bugfix on numerous Tor versions.
3929 o Code simplification and refactoring (backport from 0.3.3.5-rc):
3930 - Move the list of default directory authorities to its own file.
3931 Closes ticket 24854. Patch by "beastr0".
3934 Changes in version 0.2.9.16 - 2018-07-13
3935 Tor 0.2.9.16 moves to a new bridge authority, meaning people running
3936 bridge relays should upgrade. We also take this opportunity to backport
3939 o Directory authority changes:
3940 - The "Bifroest" bridge authority has been retired; the new bridge
3941 authority is "Serge", and it is operated by George from the
3942 TorBSD project. Closes ticket 26771.
3944 o Directory authority changes (backport from 0.3.3.7):
3945 - Add an IPv6 address for the "dannenberg" directory authority.
3946 Closes ticket 26343.
3948 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
3949 - When directory authorities read a zero-byte bandwidth file, they
3950 would previously log a warning with the contents of an
3951 uninitialised buffer. They now log a warning about the empty file
3952 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
3954 o Minor features (sandbox, backport from 0.3.3.4-alpha):
3955 - Explicitly permit the poll() system call when the Linux
3956 seccomp2-based sandbox is enabled: apparently, some versions of
3957 libc use poll() when calling getpwnam(). Closes ticket 25313.
3959 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
3960 - Our .travis.yml configuration now includes support for testing the
3961 results of "make distcheck". (It's not uncommon for "make check"
3962 to pass but "make distcheck" to fail.) Closes ticket 25814.
3963 - Our Travis CI configuration now integrates with the Coveralls
3964 coverage analysis tool. Closes ticket 25818.
3966 o Minor features (compilation, backport from 0.3.4.4-rc):
3967 - When building Tor, prefer to use Python 3 over Python 2, and more
3968 recent (contemplated) versions over older ones. Closes
3971 o Minor features (geoip):
3972 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
3973 Country database. Closes ticket 26674.
3975 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
3976 - Upon receiving a malformed connected cell, stop processing the
3977 cell immediately. Previously we would mark the connection for
3978 close, but continue processing the cell as if the connection were
3979 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
3981 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
3982 - Allow the nanosleep() system call, which glibc uses to implement
3983 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
3985 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
3986 - When running the ntor_ref.py test, make sure only to pass strings
3987 (rather than "bytes" objects) to the Python subprocess module.
3988 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
3991 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
3992 - Work around a change in OpenSSL 1.1.1 where return values that
3993 would previously indicate "no password" now indicate an empty
3994 password. Without this workaround, Tor instances running with
3995 OpenSSL 1.1.1 would accept descriptors that other Tor instances
3996 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
3998 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
3999 - Fix a compilation warning on some versions of GCC when building
4000 code that calls routerinfo_get_my_routerinfo() twice, assuming
4001 that the second call will succeed if the first one did. Fixes bug
4002 26269; bugfix on 0.2.8.2-alpha.
4004 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4005 - Don't consider Tor running as a client if the ControlPort is open,
4006 but no actual client ports are open. Fixes bug 26062; bugfix
4009 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
4010 - Prevent a possible out-of-bounds smartlist read in
4011 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4013 o Minor bugfixes (C correctness, backport from 0.3.3.4-alpha):
4014 - Fix a very unlikely (impossible, we believe) null pointer
4015 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4016 Coverity; this is CID 1430932.
4018 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
4019 - Fix a number of small memory leaks identified by coverity. Fixes
4020 bug 26467; bugfix on numerous Tor versions.
4022 o Code simplification and refactoring (backport from 0.3.3.5-rc):
4023 - Move the list of default directory authorities to its own file.
4024 Closes ticket 24854. Patch by "beastr0".
4027 Changes in version 0.3.4.4-rc - 2018-07-09
4028 Tor 0.3.4.4-rc fixes several small compilation, portability, and
4029 correctness issues in previous versions of Tor. This version is a
4030 release candidate: if no serious bugs are found, we expect that the
4031 stable 0.3.4 release will be (almost) the same as this release.
4033 o Minor features (compilation):
4034 - When building Tor, prefer to use Python 3 over Python 2, and more
4035 recent (contemplated) versions over older ones. Closes
4038 o Minor features (geoip):
4039 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
4040 Country database. Closes ticket 26674.
4042 o Minor features (Rust, portability):
4043 - Rust cross-compilation is now supported. Closes ticket 25895.
4045 o Minor bugfixes (compilation):
4046 - Fix a compilation warning on some versions of GCC when building
4047 code that calls routerinfo_get_my_routerinfo() twice, assuming
4048 that the second call will succeed if the first one did. Fixes bug
4049 26269; bugfix on 0.2.8.2-alpha.
4051 o Minor bugfixes (control port):
4052 - Report the port correctly when a port is configured to bind to
4053 "auto". Fixes bug 26568; bugfix on 0.3.4.1-alpha.
4054 - Handle the HSADDRESS= argument to the HSPOST command properly.
4055 (Previously, this argument was misparsed and thus ignored.) Fixes
4056 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
4058 o Minor bugfixes (correctness, flow control):
4059 - Upon receiving a stream-level SENDME cell, verify that our window
4060 has not grown too large. Fixes bug 26214; bugfix on svn
4063 o Minor bugfixes (memory, correctness):
4064 - Fix a number of small memory leaks identified by coverity. Fixes
4065 bug 26467; bugfix on numerous Tor versions.
4067 o Minor bugfixes (testing, compatibility):
4068 - When running the hs_ntor_ref.py test, make sure only to pass
4069 strings (rather than "bytes" objects) to the Python subprocess
4070 module. Python 3 on Windows seems to require this. Fixes bug
4071 26535; bugfix on 0.3.1.1-alpha.
4072 - When running the ntor_ref.py test, make sure only to pass strings
4073 (rather than "bytes" objects) to the Python subprocess module.
4074 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
4078 Changes in version 0.3.3.8 - 2018-07-09
4079 Tor 0.3.3.8 backports several changes from the 0.3.4.x series, including
4080 fixes for a memory leak affecting directory authorities.
4082 o Major bugfixes (directory authority, backport from 0.3.4.3-alpha):
4083 - Stop leaking memory on directory authorities when planning to
4084 vote. This bug was crashing authorities by exhausting their
4085 memory. Fixes bug 26435; bugfix on 0.3.3.6.
4087 o Major bugfixes (rust, testing, backport from 0.3.4.3-alpha):
4088 - Make sure that failing tests in Rust will actually cause the build
4089 to fail: previously, they were ignored. Fixes bug 26258; bugfix
4092 o Minor features (compilation, backport from 0.3.4.4-rc):
4093 - When building Tor, prefer to use Python 3 over Python 2, and more
4094 recent (contemplated) versions over older ones. Closes
4097 o Minor features (geoip):
4098 - Update geoip and geoip6 to the July 3 2018 Maxmind GeoLite2
4099 Country database. Closes ticket 26674.
4101 o Minor features (relay, diagnostic, backport from 0.3.4.3-alpha):
4102 - Add several checks to detect whether Tor relays are uploading
4103 their descriptors without specifying why they regenerated them.
4104 Diagnostic for ticket 25686.
4106 o Minor bugfixes (circuit path selection, backport from 0.3.4.1-alpha):
4107 - Don't count path selection failures as circuit build failures.
4108 This change should eliminate cases where Tor blames its guard or
4109 the network for situations like insufficient microdescriptors
4110 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4113 o Minor bugfixes (compilation, backport from 0.3.4.4-rc):
4114 - Fix a compilation warning on some versions of GCC when building
4115 code that calls routerinfo_get_my_routerinfo() twice, assuming
4116 that the second call will succeed if the first one did. Fixes bug
4117 26269; bugfix on 0.2.8.2-alpha.
4119 o Minor bugfixes (control port, backport from 0.3.4.4-rc):
4120 - Handle the HSADDRESS= argument to the HSPOST command properly.
4121 (Previously, this argument was misparsed and thus ignored.) Fixes
4122 bug 26523; bugfix on 0.3.3.1-alpha. Patch by "akwizgran".
4124 o Minor bugfixes (memory, correctness, backport from 0.3.4.4-rc):
4125 - Fix a number of small memory leaks identified by coverity. Fixes
4126 bug 26467; bugfix on numerous Tor versions.
4128 o Minor bugfixes (relay, backport from 0.3.4.3-alpha):
4129 - Relays now correctly block attempts to re-extend to the previous
4130 relay by Ed25519 identity. Previously they would warn in this
4131 case, but not actually reject the attempt. Fixes bug 26158; bugfix
4134 o Minor bugfixes (restart-in-process, backport from 0.3.4.1-alpha):
4135 - When shutting down, Tor now clears all the flags in the control.c
4136 module. This should prevent a bug where authentication cookies are
4137 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4139 o Minor bugfixes (testing, compatibility, backport from 0.3.4.4-rc):
4140 - When running the hs_ntor_ref.py test, make sure only to pass
4141 strings (rather than "bytes" objects) to the Python subprocess
4142 module. Python 3 on Windows seems to require this. Fixes bug
4143 26535; bugfix on 0.3.1.1-alpha.
4144 - When running the ntor_ref.py test, make sure only to pass strings
4145 (rather than "bytes" objects) to the Python subprocess module.
4146 Python 3 on Windows seems to require this. Fixes bug 26535; bugfix
4150 Changes in version 0.3.4.3-alpha - 2018-06-26
4151 Tor 0.3.4.3-alpha fixes several bugs in earlier versions, including
4152 one that was causing stability issues on directory authorities.
4154 o Major bugfixes (directory authority):
4155 - Stop leaking memory on directory authorities when planning to
4156 vote. This bug was crashing authorities by exhausting their
4157 memory. Fixes bug 26435; bugfix on 0.3.3.6.
4159 o Major bugfixes (rust, testing):
4160 - Make sure that failing tests in Rust will actually cause the build
4161 to fail: previously, they were ignored. Fixes bug 26258; bugfix
4164 o Minor feature (directory authorities):
4165 - Stop warning about incomplete bw lines before the first complete
4166 bw line has been found, so that additional header lines can be
4167 ignored. Fixes bug 25960; bugfix on 0.2.2.1-alpha
4169 o Minor features (relay, diagnostic):
4170 - Add several checks to detect whether Tor relays are uploading
4171 their descriptors without specifying why they regenerated them.
4172 Diagnostic for ticket 25686.
4174 o Minor features (unit tests):
4175 - Test complete bandwidth measurements files, and test that
4176 incomplete bandwidth lines only give warnings when the end of the
4177 header has not been detected. Fixes bug 25947; bugfix
4180 o Minor bugfixes (compilation):
4181 - Refrain from compiling unit testing related object files when
4182 --disable-unittests is set to configure script. Fixes bug 24891;
4183 bugfix on 0.2.5.1-alpha.
4184 - When linking the libtor_testing.a library, only include the
4185 dirauth object files once. Previously, they were getting added
4186 twice. Fixes bug 26402; bugfix on 0.3.4.1-alpha.
4187 - The --enable-fatal-warnings flag now affects Rust code as well.
4188 Closes ticket 26245.
4190 o Minor bugfixes (onion services):
4191 - Recompute some consensus information after detecting a clock jump,
4192 or after transitioning from a non-live consensus to a live
4193 consensus. We do this to avoid having an outdated state, and
4194 miscalculating the index for next-generation onion services. Fixes
4195 bug 24977; bugfix on 0.3.2.1-alpha.
4197 o Minor bugfixes (relay):
4198 - Relays now correctly block attempts to re-extend to the previous
4199 relay by Ed25519 identity. Previously they would warn in this
4200 case, but not actually reject the attempt. Fixes bug 26158; bugfix
4203 o Minor bugfixes (testing):
4204 - Fix compilation of the doctests in the Rust crypto crate. Fixes
4205 bug 26415; bugfix on 0.3.4.1-alpha.
4206 - Instead of trying to read the geoip configuration files from
4207 within the unit tests, instead create our own ersatz files with
4208 just enough geoip data in the format we expect. Trying to read
4209 from the source directory created problems on Windows with mingw,
4210 where the build system's paths are not the same as the platform's
4211 paths. Fixes bug 25787; bugfix on 0.3.4.1-alpha.
4212 - Refrain from trying to get an item from an empty smartlist in
4213 test_bridges_clear_bridge_list. Set DEBUG_SMARTLIST in unit tests
4214 to catch improper smartlist usage. Furthermore, enable
4215 DEBUG_SMARTLIST globally when build is configured with fragile
4216 hardening. Fixes bug 26196; bugfix on 0.3.4.1-alpha.
4219 Changes in version 0.3.3.7 - 2018-06-12
4220 Tor 0.3.3.7 backports several changes from the 0.3.4.x series, including
4221 fixes for bugs affecting compatibility and stability.
4223 o Directory authority changes:
4224 - Add an IPv6 address for the "dannenberg" directory authority.
4225 Closes ticket 26343.
4227 o Minor features (geoip):
4228 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4229 Country database. Closes ticket 26351.
4231 o Minor bugfixes (compatibility, openssl, backport from 0.3.4.2-alpha):
4232 - Work around a change in OpenSSL 1.1.1 where return values that
4233 would previously indicate "no password" now indicate an empty
4234 password. Without this workaround, Tor instances running with
4235 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4236 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4238 o Minor bugfixes (compilation, backport from 0.3.4.2-alpha):
4239 - Silence unused-const-variable warnings in zstd.h with some GCC
4240 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4242 o Minor bugfixes (controller, backport from 0.3.4.2-alpha):
4243 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4244 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4245 miscounting the total number of circuits for these field values.)
4246 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4248 o Minor bugfixes (hardening, backport from 0.3.4.2-alpha):
4249 - Prevent a possible out-of-bounds smartlist read in
4250 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4252 o Minor bugfixes (path selection, backport from 0.3.4.1-alpha):
4253 - Only select relays when they have the descriptors we prefer to use
4254 for them. This change fixes a bug where we could select a relay
4255 because it had _some_ descriptor, but reject it later with a
4256 nonfatal assertion error because it didn't have the exact one we
4257 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4260 Changes in version 0.3.4.2-alpha - 2018-06-12
4261 Tor 0.3.4.2-alpha fixes several minor bugs in the previous alpha
4262 release, and forward-ports an authority-only security fix from 0.3.3.6.
4264 o Directory authority changes:
4265 - Add an IPv6 address for the "dannenberg" directory authority.
4266 Closes ticket 26343.
4268 o Major bugfixes (security, directory authority, denial-of-service, also in 0.3.3.6):
4269 - Fix a bug that could have allowed an attacker to force a directory
4270 authority to use up all its RAM by passing it a maliciously
4271 crafted protocol versions string. Fixes bug 25517; bugfix on
4272 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4274 o Minor features (continuous integration):
4275 - Add the necessary configuration files for continuous integration
4276 testing on Windows, via the Appveyor platform. Closes ticket
4277 25549. Patches from Marcin Cieślak and Isis Lovecruft.
4279 o Minor features (geoip):
4280 - Update geoip and geoip6 to the June 7 2018 Maxmind GeoLite2
4281 Country database. Closes ticket 26351.
4283 o Minor bugfixes (compatibility, openssl):
4284 - Work around a change in OpenSSL 1.1.1 where return values that
4285 would previously indicate "no password" now indicate an empty
4286 password. Without this workaround, Tor instances running with
4287 OpenSSL 1.1.1 would accept descriptors that other Tor instances
4288 would reject. Fixes bug 26116; bugfix on 0.2.5.16.
4290 o Minor bugfixes (compilation):
4291 - Silence unused-const-variable warnings in zstd.h with some GCC
4292 versions. Fixes bug 26272; bugfix on 0.3.1.1-alpha.
4293 - Fix compilation when using OpenSSL 1.1.0 with the "no-deprecated"
4294 flag enabled. Fixes bug 26156; bugfix on 0.3.4.1-alpha.
4295 - Avoid a compiler warning when casting the return value of
4296 smartlist_len() to double with DEBUG_SMARTLIST enabled. Fixes bug
4297 26283; bugfix on 0.2.4.10-alpha.
4299 o Minor bugfixes (control port):
4300 - Do not count 0-length RELAY_COMMAND_DATA cells as valid data in
4301 CIRC_BW events. Previously, such cells were counted entirely in
4302 the OVERHEAD field. Now they are not. Fixes bug 26259; bugfix
4305 o Minor bugfixes (controller):
4306 - Improve accuracy of the BUILDTIMEOUT_SET control port event's
4307 TIMEOUT_RATE and CLOSE_RATE fields. (We were previously
4308 miscounting the total number of circuits for these field values.)
4309 Fixes bug 26121; bugfix on 0.3.3.1-alpha.
4311 o Minor bugfixes (hardening):
4312 - Prevent a possible out-of-bounds smartlist read in
4313 protover_compute_vote(). Fixes bug 26196; bugfix on 0.2.9.4-alpha.
4315 o Minor bugfixes (onion services):
4316 - Fix a bug that blocked the creation of ephemeral v3 onion
4317 services. Fixes bug 25939; bugfix on 0.3.4.1-alpha.
4319 o Minor bugfixes (test coverage tools):
4320 - Update our "cov-diff" script to handle output from the latest
4321 version of gcov, and to remove extraneous timestamp information
4322 from its output. Fixes bugs 26101 and 26102; bugfix
4326 Changes in version 0.3.3.6 - 2018-05-22
4327 Tor 0.3.3.6 is the first stable release in the 0.3.3 series. It
4328 backports several important fixes from the 0.3.4.1-alpha.
4330 The Tor 0.3.3 series includes controller support and other
4331 improvements for v3 onion services, official support for embedding Tor
4332 within other applications, and our first non-trivial module written in
4333 the Rust programming language. (Rust is still not enabled by default
4334 when building Tor.) And as usual, there are numerous other smaller
4335 bugfixes, features, and improvements.
4337 Below are the changes since 0.3.3.5-rc. For a list of all changes
4338 since 0.3.2.10, see the ReleaseNotes file.
4340 o Major bugfixes (directory authorities, security, backport from 0.3.4.1-alpha):
4341 - When directory authorities read a zero-byte bandwidth file, they
4342 would previously log a warning with the contents of an
4343 uninitialised buffer. They now log a warning about the empty file
4344 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4346 o Major bugfixes (security, directory authority, denial-of-service):
4347 - Fix a bug that could have allowed an attacker to force a directory
4348 authority to use up all its RAM by passing it a maliciously
4349 crafted protocol versions string. Fixes bug 25517; bugfix on
4350 0.2.9.4-alpha. This issue is also tracked as TROVE-2018-005.
4352 o Major bugfixes (crash, backport from 0.3.4.1-alpha):
4353 - Avoid a rare assertion failure in the circuit build timeout code
4354 if we fail to allow any circuits to actually complete. Fixes bug
4355 25733; bugfix on 0.2.2.2-alpha.
4357 o Major bugfixes (directory authorities, backport from 0.3.4.1-alpha):
4358 - Avoid a crash when testing router reachability on a router that
4359 could have an ed25519 ID, but which does not. Fixes bug 25415;
4360 bugfix on 0.3.3.2-alpha.
4362 o Major bugfixes (onion service, backport from 0.3.4.1-alpha):
4363 - Correctly detect when onion services get disabled after HUP. Fixes
4364 bug 25761; bugfix on 0.3.2.1.
4366 o Major bugfixes (relay, denial of service, backport from 0.3.4.1-alpha):
4367 - Impose a limit on circuit cell queue size. The limit can be
4368 controlled by a consensus parameter. Fixes bug 25226; bugfix
4371 o Minor features (compatibility, backport from 0.3.4.1-alpha):
4372 - Avoid some compilation warnings with recent versions of LibreSSL.
4373 Closes ticket 26006.
4375 o Minor features (continuous integration, backport from 0.3.4.1-alpha):
4376 - Our .travis.yml configuration now includes support for testing the
4377 results of "make distcheck". (It's not uncommon for "make check"
4378 to pass but "make distcheck" to fail.) Closes ticket 25814.
4379 - Our Travis CI configuration now integrates with the Coveralls
4380 coverage analysis tool. Closes ticket 25818.
4382 o Minor features (geoip):
4383 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4384 database. Closes ticket 26104.
4386 o Minor bugfixes (client, backport from 0.3.4.1-alpha):
4387 - Don't consider Tor running as a client if the ControlPort is open,
4388 but no actual client ports are open. Fixes bug 26062; bugfix
4391 o Minor bugfixes (correctness, client, backport from 0.3.4.1-alpha):
4392 - Upon receiving a malformed connected cell, stop processing the
4393 cell immediately. Previously we would mark the connection for
4394 close, but continue processing the cell as if the connection were
4395 open. Fixes bug 26072; bugfix on 0.2.4.7-alpha.
4397 o Minor bugfixes (documentation, backport from 0.3.4.1-alpha):
4398 - Stop saying in the manual that clients cache ipv4 dns answers from
4399 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4400 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4401 we forgot to say so in the man page. Fixes bug 26052; bugfix
4404 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.4.1-alpha):
4405 - Allow the nanosleep() system call, which glibc uses to implement
4406 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4408 o Minor bugfixes (onion service, backport from 0.3.4.1-alpha):
4409 - Fix a memory leak when a v3 onion service is configured and gets a
4410 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4411 - When parsing the descriptor signature, look for the token plus an
4412 extra white-space at the end. This is more correct but also will
4413 allow us to support new fields that might start with "signature".
4414 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4416 o Minor bugfixes (relay, crash, backport from 0.3.4.1-alpha):
4417 - Avoid a crash when running with DirPort set but ORPort turned off.
4418 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4420 o Documentation (backport from 0.3.4.1-alpha):
4421 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4422 ticket 25857. Patch from "CTassisF".
4425 Changes in version 0.3.4.1-alpha - 2018-05-17
4426 Tor 0.3.4.1-alpha is the first release in the 0.3.4.x series. It
4427 includes refactoring to begin reducing Tor's binary size and idle CPU
4428 usage on mobile, along with prep work for new bandwidth scanners,
4429 improvements to the experimental "vanguards" feature, and numerous
4430 other small features and bugfixes.
4432 o New system requirements:
4433 - Tor no longer tries to support old operating systems without
4434 mmap() or some local equivalent. Apparently, compilation on such
4435 systems has been broken for some time, without anybody noticing or
4436 complaining. Closes ticket 25398.
4438 o Major feature (directory authority, modularization):
4439 - The directory authority subsystem has been modularized. The code
4440 is now located in src/or/dirauth/, and is compiled in by default.
4441 To disable the module, the configure option
4442 --disable-module-dirauth has been added. This module may be
4443 disabled by default in some future release. Closes ticket 25610.
4445 o Major features (main loop, CPU usage):
4446 - When Tor is disabled (via DisableNetwork or via hibernation), it
4447 no longer needs to run any per-second events. This change should
4448 make it easier for mobile applications to disable Tor while the
4449 device is sleeping, or Tor is not running. Closes ticket 26063.
4450 - Tor no longer enables all of its periodic events by default.
4451 Previously, Tor would enable all possible main loop events,
4452 regardless of whether it needed them. Furthermore, many of these
4453 events are now disabled with Tor is hibernating or DisableNetwork
4454 is set. This is a big step towards reducing client CPU usage by
4455 reducing the amount of wake-ups the daemon does. Closes ticket
4457 - The bandwidth-limitation logic has been refactored so that
4458 bandwidth calculations are performed on-demand, rather than every
4459 TokenBucketRefillInterval milliseconds. This change should improve
4460 the granularity of our bandwidth calculations, and limit the
4461 number of times that the Tor process needs to wake up when it is
4462 idle. Closes ticket 25373.
4463 - Move responsibility for many operations from a once-per-second
4464 callback to a callback that is only scheduled as needed. Moving
4465 this functionality has allowed us to disable the callback when
4466 Tor's network is disabled. Once enough items are removed from our
4467 once-per-second callback, we can eliminate it entirely to conserve
4468 CPU when idle. The functionality removed includes: closing
4469 connections, circuits, and channels (ticket 25932); consensus
4470 voting (25937); flushing log callbacks (25951); honoring delayed
4471 SIGNEWNYM requests (25949); rescanning the consensus cache
4472 (25931); saving the state file to disk (25948); warning relay
4473 operators about unreachable ports (25952); and keeping track of
4474 Tor's uptime (26009).
4476 o Major bugfixes (directory authorities, security):
4477 - When directory authorities read a zero-byte bandwidth file, they
4478 would previously log a warning with the contents of an
4479 uninitialised buffer. They now log a warning about the empty file
4480 instead. Fixes bug 26007; bugfix on 0.2.2.1-alpha.
4482 o Major bugfixes (crash):
4483 - Avoid a rare assertion failure in the circuit build timeout code
4484 if we fail to allow any circuits to actually complete. Fixes bug
4485 25733; bugfix on 0.2.2.2-alpha.
4487 o Major bugfixes (directory authority):
4488 - Avoid a crash when testing router reachability on a router that
4489 could have an ed25519 ID, but which does not. Fixes bug 25415;
4490 bugfix on 0.3.3.2-alpha.
4492 o Major bugfixes (onion service):
4493 - Correctly detect when onion services get disabled after HUP. Fixes
4494 bug 25761; bugfix on 0.3.2.1.
4496 o Major bugfixes (protover, voting):
4497 - Revise Rust implementation of protover to use a more memory-
4498 efficient voting algorithm and corresponding data structures, thus
4499 avoiding a potential (but small impact) DoS attack where specially
4500 crafted protocol strings would expand to several potential
4501 megabytes in memory. In the process, several portions of code were
4502 revised to be methods on new, custom types, rather than functions
4503 taking interchangeable types, thus increasing type safety of the
4504 module. Custom error types and handling were added as well, in
4505 order to facilitate better error dismissal/handling in outside
4506 crates and avoid mistakenly passing an internal error string to C
4507 over the FFI boundary. Many tests were added, and some previous
4508 differences between the C and Rust implementations have been
4509 remedied. Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4511 o Major bugfixes (relay, denial of service):
4512 - Impose a limit on circuit cell queue size. The limit can be
4513 controlled by a consensus parameter. Fixes bug 25226; bugfix
4516 o Minor features (accounting):
4517 - When Tor becomes dormant, it now uses a scheduled event to wake up
4518 at the right time. Previously, we would use the per-second timer
4519 to check whether to wake up, but we no longer have any per-second
4520 timers enabled when the network is disabled. Closes ticket 26064.
4522 o Minor features (code quality):
4523 - Add optional spell-checking for the Tor codebase, using the
4524 "misspell" program. To use this feature, run "make check-typos".
4525 Closes ticket 25024.
4527 o Minor features (compatibility):
4528 - Tor now detects versions of OpenSSL 1.1.0 and later compiled with
4529 the no-deprecated option, and builds correctly with them. Closes
4530 tickets 19429, 19981, and 25353.
4531 - Avoid some compilation warnings with recent versions of LibreSSL.
4532 Closes ticket 26006.
4534 o Minor features (compression, zstd):
4535 - When running with zstd, Tor now considers using advanced functions
4536 that the zstd maintainers have labeled as potentially unstable. To
4537 prevent breakage, Tor will only use this functionality when the
4538 runtime version of the zstd library matches the version with which
4539 Tor was compiled. Closes ticket 25162.
4541 o Minor features (configuration):
4542 - The "DownloadSchedule" options have been renamed to end with
4543 "DownloadInitialDelay". The old names are still allowed, but will
4544 produce a warning. Comma-separated lists are still permitted for
4545 these options, but all values after the first are ignored (as they
4546 have been since 0.2.9). Closes ticket 23354.
4548 o Minor features (continuous integration):
4549 - Our .travis.yml configuration now includes support for testing the
4550 results of "make distcheck". (It's not uncommon for "make check"
4551 to pass but "make distcheck" to fail.) Closes ticket 25814.
4552 - Our Travis CI configuration now integrates with the Coveralls
4553 coverage analysis tool. Closes ticket 25818.
4555 o Minor features (control port):
4556 - Introduce GETINFO "current-time/{local,utc}" to return the local
4557 and UTC times respectively in ISO format. This helps a controller
4558 like Tor Browser detect a time-related error. Closes ticket 25511.
4559 Patch by Neel Chauhan.
4560 - Introduce new fields to the CIRC_BW event. There are two new
4561 fields in each of the read and written directions. The DELIVERED
4562 fields report the total valid data on the circuit, as measured by
4563 the payload sizes of verified and error-checked relay command
4564 cells. The OVERHEAD fields report the total unused bytes in each
4565 of these cells. Closes ticket 25903.
4567 o Minor features (directory authority):
4568 - Directory authorities now open their key-pinning files as O_SYNC,
4569 to limit their chances of accidentally writing partial lines.
4570 Closes ticket 23909.
4572 o Minor features (directory authority, forward compatibility):
4573 - Make the lines of the measured bandwidth file able to contain
4574 their entries in any order. Previously, the node_id entry needed
4575 to come first. Closes ticket 26004.
4577 o Minor features (entry guards):
4578 - Introduce a new torrc option NumPrimaryGuards for controlling the
4579 number of primary guards. Closes ticket 25843.
4581 o Minor features (geoip):
4582 - Update geoip and geoip6 to the May 1 2018 Maxmind GeoLite2 Country
4583 database. Closes ticket 26104.
4585 o Minor features (performance):
4586 - Avoid a needless call to malloc() when processing an incoming
4587 relay cell. Closes ticket 24914.
4588 - Make our timing-wheel code run a tiny bit faster on 32-bit
4589 platforms, by preferring 32-bit math to 64-bit. Closes
4591 - Avoid a needless malloc()/free() pair every time we handle an ntor
4592 handshake. Closes ticket 25150.
4594 o Minor features (testing):
4595 - Add a unit test for voting_schedule_get_start_of_next_interval().
4596 Closes ticket 26014, and helps make unit test coverage
4598 - A new unittests module specifically for testing the functions in
4599 the (new-ish) bridges.c module has been created with new
4600 unittests, raising the code coverage percentages. Closes 25425.
4601 - We now have improved testing for addressmap_get_virtual_address()
4602 function. This should improve our test coverage, and make our test
4603 coverage more deterministic. Closes ticket 25993.
4605 o Minor features (timekeeping, circuit scheduling):
4606 - When keeping track of how busy each circuit have been recently on
4607 a given connection, use coarse-grained monotonic timers rather
4608 than gettimeofday(). This change should marginally increase
4609 accuracy and performance. Implements part of ticket 25927.
4611 o Minor bugfixes (bandwidth management):
4612 - Consider ourselves "low on write bandwidth" if we have exhausted
4613 our write bandwidth some time in the last second. This was the
4614 documented behavior before, but the actual behavior was to change
4615 this value every TokenBucketRefillInterval. Fixes bug 25828;
4616 bugfix on 0.2.3.5-alpha.
4618 o Minor bugfixes (C correctness):
4619 - Add a missing lock acquisition in the shutdown code of the control
4620 subsystem. Fixes bug 25675; bugfix on 0.2.7.3-rc. Found by
4621 Coverity; this is CID 1433643.
4623 o Minor bugfixes (circuit path selection):
4624 - Don't count path selection failures as circuit build failures.
4625 This change should eliminate cases where Tor blames its guard or
4626 the network for situations like insufficient microdescriptors
4627 and/or overly restrictive torrc settings. Fixes bug 25705; bugfix
4630 o Minor bugfixes (client):
4631 - Don't consider Tor running as a client if the ControlPort is open,
4632 but no actual client ports are open. Fixes bug 26062; bugfix
4635 o Minor bugfixes (code style):
4636 - Fixed multiple includes of transports.h in src/or/connection.c
4637 Fixes bug 25261; bugfix on 0.2.5.1-alpha.
4638 - Remove the unused variable n_possible from the function
4639 channel_get_for_extend(). Fixes bug 25645; bugfix on 0.2.4.4-alpha
4641 o Minor bugfixes (control interface):
4642 - Respond with more human-readable error messages to GETINFO exit-
4643 policy/* requests. Also, let controller know if an error is
4644 transient (response code 551) or not (response code 552). Fixes
4645 bug 25852; bugfix on 0.2.8.1-alpha.
4647 o Minor bugfixes (controller):
4648 - Make CIRC_BW event reflect the total of all data sent on a
4649 circuit, including padding and dropped cells. Also fix a mis-
4650 counting bug when STREAM_BW events were enabled. Fixes bug 25400;
4651 bugfix on 0.2.5.2-alpha.
4653 o Minor bugfixes (correctness, client):
4654 - Upon receiving a malformed connected cell, stop processing the cell
4655 immediately. Previously we would mark the connection for close, but
4656 continue processing the cell as if the connection were open. Fixes bug
4657 26072; bugfix on 0.2.4.7-alpha.
4659 o Minor bugfixes (directory client):
4660 - When unverified-consensus is verified, rename it to cached-
4661 consenus. Fixes bug 4187; bugfix on 0.2.0.3-alpha.
4662 - Fixed launching a certificate fetch always during the scheduled
4663 periodic consensus fetch by fetching only in those cases when
4664 consensus are waiting for certs. Fixes bug 24740; bugfix
4667 o Minor bugfixes (documentation):
4668 - Stop saying in the manual that clients cache ipv4 dns answers from
4669 exit relays. We haven't used them since 0.2.6.3-alpha, and in
4670 ticket 24050 we stopped even caching them as of 0.3.2.6-alpha, but
4671 we forgot to say so in the man page. Fixes bug 26052; bugfix
4674 o Minor bugfixes (error reporting):
4675 - Improve tolerance for directory authorities with skewed clocks.
4676 Previously, an authority with a clock more than 60 seconds ahead
4677 could cause a client with a correct clock to warn that the
4678 client's clock was behind. Now the clocks of a majority of
4679 directory authorities have to be ahead of the client before this
4680 warning will occur. Fixes bug 25756; bugfix on 0.2.2.25-alpha.
4682 o Minor bugfixes (Linux seccomp2 sandbox):
4683 - Allow the nanosleep() system call, which glibc uses to implement
4684 sleep() and usleep(). Fixes bug 24969; bugfix on 0.2.5.1-alpha.
4686 o Minor bugfixes (onion service):
4687 - Fix a memory leak when a v3 onion service is configured and gets a
4688 SIGHUP signal. Fixes bug 25901; bugfix on 0.3.2.1-alpha.
4689 - When parsing the descriptor signature, look for the token plus an
4690 extra white-space at the end. This is more correct but also will
4691 allow us to support new fields that might start with "signature".
4692 Fixes bug 26069; bugfix on 0.3.0.1-alpha.
4694 o Minor bugfixes (path selection):
4695 - Only select relays when they have the descriptors we prefer to use
4696 for them. This change fixes a bug where we could select a relay
4697 because it had _some_ descriptor, but reject it later with a
4698 nonfatal assertion error because it didn't have the exact one we
4699 wanted. Fixes bugs 25691 and 25692; bugfix on 0.3.3.4-alpha.
4701 o Minor bugfixes (portability):
4702 - Do not align mmap length, as it is not required by POSIX, and the
4703 getpagesize function is deprecated. Fixes bug 25399; bugfix
4706 o Minor bugfixes (portability, FreeBSD):
4707 - In have_enough_mem_for_dircache(), the variable DIRCACHE_MIN_MEM_MB
4708 does not stringify on FreeBSD, so we switch to tor_asprintf().
4709 Fixes bug 20887; bugfix on 0.2.8.1-alpha. Patch by Neel Chauhan.
4711 o Minor bugfixes (relay statistics):
4712 - When a relay is collecting internal statistics about how many
4713 create cell requests it has seen of each type, accurately count
4714 the requests from relays that temporarily fall out of the
4715 consensus. (To be extra conservative, we were already ignoring
4716 requests from clients in our counts, and we continue ignoring them
4717 here.) Fixes bug 24910; bugfix on 0.2.4.17-rc.
4719 o Minor bugfixes (relay, crash):
4720 - Avoid a crash when running with DirPort set but ORPort turned off.
4721 Fixes a case of bug 23693; bugfix on 0.3.1.1-alpha.
4723 o Minor bugfixes (restart-in-process):
4724 - When shutting down, Tor now clears all the flags in the control.c
4725 module. This should prevent a bug where authentication cookies are
4726 not generated on restart. Fixes bug 25512; bugfix on 0.3.3.1-alpha.
4728 o Minor bugfixes (testing):
4729 - When testing workqueue event-cancellation, make sure that we
4730 actually cancel an event, and that cancel each event with equal
4731 probability. (It was previously possible, though extremely
4732 unlikely, for our event-canceling test not to cancel any events.)
4733 Fixes bug 26008; bugfix on 0.2.6.3-alpha.
4734 - Repeat part of the test in test_client_pick_intro() a number of
4735 times, to give it consistent coverage. Fixes bug 25996; bugfix
4737 - Remove randomness from the hs_common/responsible_hsdirs test, so
4738 that it always takes the same path through the function it tests.
4739 Fixes bug 25997; bugfix on 0.3.2.1-alpha.
4740 - Change the behavior of the "channel/outbound" test so that it
4741 never causes a 10-second rollover for the EWMA circuitmux code.
4742 Previously, this behavior would happen randomly, and result in
4743 fluctuating test coverage. Fixes bug 25994; bugfix
4745 - Use X509_new() to allocate certificates that will be freed later
4746 with X509_free(). Previously, some parts of the unit tests had
4747 used tor_malloc_zero(), which is incorrect, and which caused test
4748 failures on Windows when they were built with extra hardening.
4749 Fixes bugs 25943 and 25944; bugfix on 0.2.8.1-alpha. Patch by
4751 - While running the circuit_timeout test, fix the PRNG to a
4752 deterministic AES stream, so that the test coverage from this test
4753 will itself be deterministic. Fixes bug 25995; bugfix
4756 o Minor bugfixes (vanguards):
4757 - Allow the last hop in a vanguard circuit to be the same as our
4758 first, to prevent the adversary from influencing guard node choice
4759 by choice of last hop. Also prevent the creation of A - B - A
4760 paths, or A - A paths, which are forbidden by relays. Fixes bug
4761 25870; bugfix on 0.3.3.1-alpha.
4763 o Code simplification and refactoring:
4764 - Remove duplicate code in parse_{c,s}method_line and bootstrap
4765 their functionalities into a single function. Fixes bug 6236;
4766 bugfix on 0.2.3.6-alpha.
4767 - We remove the PortForwsrding and PortForwardingHelper options,
4768 related functions, and the port_forwarding tests. These options
4769 were used by the now-deprecated Vidalia to help ordinary users
4770 become Tor relays or bridges. Closes ticket 25409. Patch by
4772 - In order to make the OR and dir checking function in router.c less
4773 confusing we renamed some functions and
4774 consider_testing_reachability() has been split into
4775 router_should_check_reachability() and
4776 router_do_reachability_checks(). Also we improved the documentation
4777 in some functions. Closes ticket 18918.
4778 - Initial work to isolate Libevent usage to a handful of modules in
4779 our codebase, to simplify our call structure, and so that we can
4780 more easily change event loops in the future if needed. Closes
4782 - Introduce a function to call getsockname() and return tor_addr_t,
4783 to save a little complexity throughout the codebase. Closes
4785 - Make hsdir_index in node_t a hsdir_index_t rather than a pointer
4786 as hsdir_index is always present. Also, we move hsdir_index_t into
4787 or.h. Closes ticket 23094. Patch by Neel Chauhan.
4788 - Merge functions used for describing nodes and suppress the
4789 functions that do not allocate memory for the output buffer
4790 string. NODE_DESC_BUF_LEN constant and format_node_description()
4791 function cannot be used externally from router.c module anymore.
4792 Closes ticket 25432. Patch by valentecaio.
4793 - Our main loop has been simplified so that all important operations
4794 happen inside events. Previously, some operations had to happen
4795 outside the event loop, to prevent infinite sequences of event
4796 activations. Closes ticket 25374.
4797 - Put a SHA1 public key digest in hs_service_intro_point_t, and use
4798 it in register_intro_circ() and service_intro_point_new(). This
4799 prevents the digest from being re-calculated each time. Closes
4800 ticket 23107. Patch by Neel Chauhan.
4801 - Refactor token-bucket implementations to use a common backend.
4802 Closes ticket 25766.
4803 - Remove extern declaration of stats_n_seconds_working variable from
4804 main, protecting its accesses with get_uptime() and reset_uptime()
4805 functions. Closes ticket 25081, patch by “valentecaio”.
4806 - Remove our previous logic for "cached gettimeofday()" -- our
4807 coarse monotonic timers are fast enough for this purpose, and far
4808 less error-prone. Implements part of ticket 25927.
4809 - Remove the return value for fascist_firewall_choose_address_base(),
4810 and sister functions such as fascist_firewall_choose_address_node()
4811 and fascist_firewall_choose_address_rs(). Also, while we're here,
4812 initialize the ap argument as leaving it uninitialized can pose a
4813 security hazard. Closes ticket 24734. Patch by Neel Chauhan.
4814 - Rename two fields of connection_t struct. timestamp_lastwritten is
4815 renamed to timestamp_last_write_allowed and timestamp_lastread is
4816 renamed to timestamp_last_read_allowed. Closes ticket 24714, patch
4818 - Since Tor requires C99, remove our old workaround code for libc
4819 implementations where free(NULL) doesn't work. Closes ticket 24484.
4820 - Use our standard rate-limiting code to deal with excessive
4821 libevent failures, rather than the hand-rolled logic we had
4822 before. Closes ticket 26016.
4823 - We remove the return value of node_get_prim_orport() and
4824 node_get_prim_dirport(), and introduce node_get_prim_orport() in
4825 node_ipv6_or_preferred() and node_ipv6_dir_preferred() in order to
4826 check for a null address. Closes ticket 23873. Patch by
4828 - We switch to should_record_bridge_info() in
4829 geoip_note_client_seen() and options_need_geoip_info() instead of
4830 accessing the configuration values directly. Fixes bug 25290;
4831 bugfix on 0.2.1.6-alpha. Patch by Neel Chauhan.
4833 o Deprecated features:
4834 - As we are not recommending 0.2.5 anymore, we require relays that
4835 once had an ed25519 key associated with their RSA key to always
4836 have that key, instead of allowing them to drop back to a version
4837 that didn't support ed25519. This means they need to use a new RSA
4838 key if they want to downgrade to an older version of tor without
4839 ed25519. Closes ticket 20522.
4842 - Correct an IPv6 error in the documentation for ExitPolicy. Closes
4843 ticket 25857. Patch from "CTassisF".
4846 - Directory authorities will no longer support voting according to
4847 any consensus method before consensus method 25. This keeps
4848 authorities compatible with all authorities running 0.2.9.8 and
4849 later, and does not break any clients or relays. Implements ticket
4850 24378 and proposal 290.
4851 - The PortForwarding and PortForwardingHelper features have been
4852 removed. The reasoning is, given that implementations of NAT
4853 traversal protocols within common consumer grade routers are
4854 frequently buggy, and that the target audience for a NAT punching
4855 feature is a perhaps less-technically-inclined relay operator,
4856 when the helper fails to setup traversal the problems are usually
4857 deep, ugly, and very router specific, making them horrendously
4858 impossible for technical support to reliable assist with, and thus
4859 resulting in frustration all around. Unfortunately, relay
4860 operators who would like to run relays behind NATs will need to
4861 become more familiar with the port forwarding configurations on
4862 their local router. Closes 25409.
4863 - The TestingEnableTbEmptyEvent option has been removed. It was used
4864 in testing simulations to measure how often connection buckets
4865 were emptied, in order to improve our scheduling, but it has not
4866 been actively used in years. Closes ticket 25760.
4867 - The old "round-robin" circuit multiplexer (circuitmux)
4868 implementation has been removed, along with a fairly large set of
4869 code that existed to support it. It has not been the default
4870 circuitmux since we introduced the "EWMA" circuitmux in 0.2.4.x,
4871 but it still required an unreasonable amount of memory and CPU.
4872 Closes ticket 25268.
4875 Changes in version 0.3.3.5-rc - 2018-04-15
4876 Tor 0.3.3.5-rc fixes various bugs in earlier versions of Tor,
4877 including some that could affect reliability or correctness.
4879 This is the first release candidate in the 0.3.3 series. If we find no
4880 new bugs or regression here, then the first stable 0.3.3 release will
4881 be nearly identical to this one.
4883 o Major bugfixes (security, protover, voting):
4884 - Revise Rust implementation of protover to use a more memory-
4885 efficient voting algorithm and corresponding data structures, thus
4886 avoiding a potential memory-based DoS attack where specially
4887 crafted protocol strings would expand to fill available memory.
4888 Fixes bug 24031; bugfix on 0.3.3.1-alpha.
4890 o Major bugfixes (performance, load balancing):
4891 - Directory authorities no longer vote in favor of the Guard flag
4892 for relays without directory support. Starting in Tor
4893 0.3.0.1-alpha, clients have been avoiding using such relays in the
4894 Guard position, leading to increasingly broken load balancing for
4895 the 5%-or-so of Guards that don't advertise directory support.
4896 Fixes bug 22310; bugfix on 0.3.0.6.
4898 o Minor feature (continuous integration):
4899 - Update the Travis CI configuration to use the stable Rust channel,
4900 now that we have decided to require that. Closes ticket 25714.
4902 o Minor features (config options):
4903 - Change the way the default value for MaxMemInQueues is calculated.
4904 We now use 40% of the hardware RAM if the system has 8 GB RAM or
4905 more. Otherwise we use the former value of 75%. Closes
4908 o Minor features (geoip):
4909 - Update geoip and geoip6 to the April 3 2018 Maxmind GeoLite2
4910 Country database. Closes ticket 25718.
4912 o Minor bugfixes (client):
4913 - When using a listed relay as a bridge, and also using
4914 microdescriptors, and considering that relay as a non-bridge in a
4915 circuit, treat its microdescriptor as a valid source of
4916 information about that relay. This change should prevent a non-
4917 fatal assertion error. Fixes bug 25691; bugfix on 0.3.3.4-alpha.
4919 o Minor bugfixes (controller):
4920 - Restore the correct operation of the RESOLVE command, which had
4921 been broken since we added the ability to enable/disable DNS on
4922 specific listener ports. Fixes bug 25617; bugfix on 0.2.9.3-alpha.
4924 o Minor bugfixes (distribution, compilation, rust):
4925 - Build correctly when the rust dependencies submodule is loaded,
4926 but the TOR_RUST_DEPENDENCIES environment variable is not set.
4927 Fixes bug 25679; bugfix on 0.3.3.1-alpha.
4928 - Actually include all of our Rust source in our source
4929 distributions. (Previously, a few of the files were accidentally
4930 omitted.) Fixes bug 25732; bugfix on 0.3.3.2-alpha.
4932 o Minor bugfixes (documentation):
4933 - Document that the PerConnBW{Rate,Burst} options will fall back to
4934 their corresponding consensus parameters only if those parameters
4935 are set. Previously we had claimed that these values would always
4936 be set in the consensus. Fixes bug 25296; bugfix on 0.2.2.7-alpha.
4937 - Revert a misformatting issue in the ExitPolicy documentation.
4938 Fixes bug 25582; bugfix on 0.3.3.1-alpha.
4940 o Minor bugfixes (exit relay DNS retries):
4941 - Re-attempt timed-out DNS queries 3 times before failure, since our
4942 timeout is 5 seconds for them, but clients wait 10-15. Also allow
4943 slightly more timeouts per resolver when an exit has multiple
4944 resolvers configured. Fixes bug 21394; bugfix on 0.3.1.9.
4946 o Minor bugfixes (onion services):
4947 - Re-instate counting the client HSDir fetch circuits against the
4948 MaxClientCircuitsPending rate limit. Fixes bug 24989; bugfix
4950 - Remove underscores from the _HSLayer{2,3}Nodes options. This
4951 expert-user configuration can now be enabled as HSLayer{2,3}Nodes.
4952 Fixes bug 25581; bugfix on 0.3.3.1-alpha
4954 o Code simplification and refactoring:
4955 - Move the list of default directory authorities to its own file.
4956 Closes ticket 24854. Patch by "beastr0".
4958 o Documentation (manpage, denial of service):
4959 - Provide more detail about the denial-of-service options, by
4960 listing each mitigation and explaining how they relate. Closes
4964 Changes in version 0.3.3.4-alpha - 2018-03-29
4965 Tor 0.3.3.4-alpha includes various bugfixes for issues found during
4966 the alpha testing of earlier releases in its series. We are
4967 approaching a stable 0.3.3.4-alpha release: more testing is welcome!
4969 o New system requirements:
4970 - When built with Rust, Tor now depends on version 0.2.39 of the
4971 libc crate. Closes tickets 25310 and 25664.
4973 o Major bugfixes (relay, connection):
4974 - If we have failed to connect to a relay and received a connection
4975 refused, timeout, or similar error (at the TCP level), do not try
4976 that same address/port again for 60 seconds after the failure has
4977 occurred. Fixes bug 24767; bugfix on 0.0.6.
4979 o Minor features (geoip):
4980 - Update geoip and geoip6 to the March 8 2018 Maxmind GeoLite2
4981 Country database. Closes ticket 25469.
4983 o Minor features (log messages):
4984 - Improve log message in the out-of-memory handler to include
4985 information about memory usage from the different compression
4986 backends. Closes ticket 25372.
4988 o Minor features (sandbox):
4989 - Explicitly permit the poll() system call when the Linux
4990 seccomp2-based sandbox is enabled: apparently, some versions of
4991 libc use poll() when calling getpwnam(). Closes ticket 25313.
4993 o Minor bugfixes (C correctness):
4994 - Fix a very unlikely (impossible, we believe) null pointer
4995 dereference. Fixes bug 25629; bugfix on 0.2.9.15. Found by
4996 Coverity; this is CID 1430932.
4998 o Minor bugfixes (channel, client):
4999 - Better identify client connection when reporting to the geoip
5000 client cache. Fixes bug 24904; bugfix on 0.3.1.7.
5002 o Minor bugfixes (compilation):
5003 - Fix a C99 compliance issue in our configuration script that caused
5004 compilation issues when compiling Tor with certain versions of
5005 xtools. Fixes bug 25474; bugfix on 0.3.2.5-alpha.
5007 o Minor bugfixes (controller, reliability):
5008 - Avoid a (nonfatal) assertion failure when extending a one-hop
5009 circuit from the controller to become a multihop circuit. Fixes
5010 bug 24903; bugfix on 0.2.5.2-alpha.
5012 o Major bugfixes (networking):
5013 - Tor will no longer reject IPv6 address strings from Tor Browser
5014 when they are passed as hostnames in SOCKS5 requests. Fixes bug
5015 25036, bugfix on Tor 0.3.1.2.
5017 o Minor bugfixes (networking):
5018 - string_is_valid_hostname() will not consider IP strings to be
5019 valid hostnames. Fixes bug 25055; bugfix on Tor 0.2.5.5.
5021 o Minor bugfixes (onion service v3):
5022 - Avoid an assertion failure when the next onion service
5023 descriptor rotation type is out of sync with the consensus's
5024 valid-after time. Instead, log a warning message with extra
5025 information, so we can better hunt down the cause of this
5026 assertion. Fixes bug 25306; bugfix on 0.3.2.1-alpha.
5028 o Minor bugfixes (testing):
5029 - Avoid intermittent test failures due to a test that had relied on
5030 onion service introduction point creation finishing within 5
5031 seconds of real clock time. Fixes bug 25450; bugfix
5033 - Rust crates are now automatically detected and tested. Previously,
5034 some crates were not tested by `make test-rust` due to a static
5035 string in the `src/test/test_rust.sh` script specifying which
5036 crates to test. Fixes bug 25560; bugfix on 0.3.3.3-alpha.
5038 o Minor bugfixes (testing, benchmarks):
5039 - Fix a crash when running benchmark tests on win32 systems. The
5040 crash was due to a mutex that wasn't initialized before logging
5041 and options were initialized. Fixes bug 25479; bugfix
5044 o Minor bugfixes (warnings, ipv6):
5045 - Avoid a bug warning that could occur when trying to connect to a
5046 relay over IPv6. This warning would occur on a Tor instance that
5047 downloads router descriptors, but prefers to use microdescriptors.
5048 Fixes bug 25213; bugfix on 0.3.3.1-alpha.
5050 o Code simplification and refactoring:
5051 - Remove the old (deterministic) directory retry logic entirely:
5052 We've used exponential backoff exclusively for some time. Closes
5056 - Improved the documentation of AccountingStart parameter. Closes
5058 - Update the documentation for "Log" to include the current list of
5059 logging domains. Closes ticket 25378.
5062 Changes in version 0.3.1.10 - 2018-03-03
5063 Tor 0.3.1.10 backports a number of bugfixes, including important fixes for
5066 It includes an important security fix for a remote crash attack
5067 against directory authorities, tracked as TROVE-2018-001.
5069 This release also backports our new system for improved resistance to
5070 denial-of-service attacks against relays.
5072 This release also fixes several minor bugs and annoyances from
5075 All directory authorities should upgrade to one of the versions
5076 released today. Relays running 0.3.1.x may wish to update to one of
5077 the versions released today, for the DoS mitigations.
5079 Please note: according to our release calendar, Tor 0.3.1 will no
5080 longer be supported after 1 July 2018. If you will be running Tor
5081 after that date, you should make sure to plan to upgrade to the latest
5082 stable version, or downgrade to 0.2.9 (which will receive long-term
5085 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5086 - Fix a protocol-list handling bug that could be used to remotely crash
5087 directory authorities with a null-pointer exception. Fixes bug 25074;
5088 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5091 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5092 - Give relays some defenses against the recent network overload. We
5093 start with three defenses (default parameters in parentheses).
5094 First: if a single client address makes too many concurrent
5095 connections (>100), hang up on further connections. Second: if a
5096 single client address makes circuits too quickly (more than 3 per
5097 second, with an allowed burst of 90) while also having too many
5098 connections open (3), refuse new create cells for the next while
5099 (1-2 hours). Third: if a client asks to establish a rendezvous
5100 point to you directly, ignore the request. These defenses can be
5101 manually controlled by new torrc options, but relays will also
5102 take guidance from consensus parameters, so there's no need to
5103 configure anything manually. Implements ticket 24902.
5105 o Minor features (linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
5106 - Update the sandbox rules so that they should now work correctly
5107 with Glibc 2.26. Closes ticket 24315.
5109 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5110 - Fix an "off by 2" error in counting rendezvous failures on the
5111 onion service side. While we thought we would stop the rendezvous
5112 attempt after one failed circuit, we were actually making three
5113 circuit attempts before giving up. Now switch to a default of 2,
5114 and allow the consensus parameter "hs_service_max_rdv_failures" to
5115 override. Fixes bug 24895; bugfix on 0.0.6.
5117 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5118 - Add Link protocol version 5 to the supported protocols list. Fixes
5119 bug 25070; bugfix on 0.3.1.1-alpha.
5121 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5122 - Fix a set of false positives where relays would consider
5123 connections to other relays as being client-only connections (and
5124 thus e.g. deserving different link padding schemes) if those
5125 relays fell out of the consensus briefly. Now we look only at the
5126 initial handshake and whether the connection authenticated as a
5127 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5129 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5130 - Make our OOM handler aware of the geoip client history cache so it
5131 doesn't fill up the memory. This check is important for IPv6 and
5132 our DoS mitigation subsystem. Closes ticket 25122.
5134 o Minor feature (relay statistics, backport from 0.3.2.6-alpha):
5135 - Change relay bandwidth reporting stats interval from 4 hours to 24
5136 hours in order to reduce the efficiency of guard discovery
5137 attacks. Fixes ticket 23856.
5139 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5140 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5141 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5142 since they neither disabled TLS 1.3 nor enabled any of the
5143 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5144 Closes ticket 24978.
5146 o Minor features (fallback directory mirrors, backport from 0.3.2.9):
5147 - The fallback directory list has been re-generated based on the
5148 current status of the network. Tor uses fallback directories to
5149 bootstrap when it doesn't yet have up-to-date directory
5150 information. Closes ticket 24801.
5151 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5152 prefer to bootstrap from fallback directory mirrors. This is a
5153 follow-up to 24679, which removed weights from the default
5154 fallbacks. Implements ticket 24681.
5156 o Minor features (geoip):
5157 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5160 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5161 - Use the actual observed address of an incoming relay connection,
5162 not the canonical address of the relay from its descriptor, when
5163 making decisions about how to handle the incoming connection.
5164 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5166 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5167 - Directory authorities, when refusing a descriptor from a rejected
5168 relay, now explicitly tell the relay (in its logs) to set a valid
5169 ContactInfo address and contact the bad-relays@ mailing list.
5170 Fixes bug 25170; bugfix on 0.2.9.1.
5172 o Minor bugfixes (address selection, backport from 0.3.2.9):
5173 - When the fascist_firewall_choose_address_ functions don't find a
5174 reachable address, set the returned address to the null address
5175 and port. This is a precautionary measure, because some callers do
5176 not check the return value. Fixes bug 24736; bugfix
5179 o Major bugfixes (bootstrapping, backport from 0.3.2.5-alpha):
5180 - Fetch descriptors aggressively whenever we lack enough to build
5181 circuits, regardless of how many descriptors we are missing.
5182 Previously, we would delay launching the fetch when we had fewer
5183 than 15 missing descriptors, even if some of those descriptors
5184 were blocking circuits from building. Fixes bug 23985; bugfix on
5185 0.1.1.11-alpha. The effects of this bug became worse in
5186 0.3.0.3-alpha, when we began treating missing descriptors from our
5187 primary guards as a reason to delay circuits.
5188 - Don't try fetching microdescriptors from relays that have failed
5189 to deliver them in the past. Fixes bug 23817; bugfix
5192 o Minor bugfixes (compilation, backport from 0.3.2.7-rc):
5193 - Fix a signed/unsigned comparison warning introduced by our fix to
5194 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5196 o Minor bugfixes (control port, linux seccomp2 sandbox, backport from 0.3.2.5-alpha):
5197 - Avoid a crash when attempting to use the seccomp2 sandbox together
5198 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5201 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5202 - Fix a possible crash on malformed consensus. If a consensus had
5203 contained an unparseable protocol line, it could have made clients
5204 and relays crash with a null-pointer exception. To exploit this
5205 issue, however, an attacker would need to be able to subvert the
5206 directory authority system. Fixes bug 25251; bugfix on
5207 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5209 o Minor bugfixes (directory cache, backport from 0.3.2.5-alpha):
5210 - Recover better from empty or corrupt files in the consensus cache
5211 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
5212 - When a consensus diff calculation is only partially successful,
5213 only record the successful parts as having succeeded. Partial
5214 success can happen if (for example) one compression method fails
5215 but the others succeed. Previously we misrecorded all the
5216 calculations as having succeeded, which would later cause a
5217 nonfatal assertion failure. Fixes bug 24086; bugfix
5220 o Minor bugfixes (entry guards, backport from 0.3.2.3-alpha):
5221 - Tor now updates its guard state when it reads a consensus
5222 regardless of whether it's missing descriptors. That makes tor use
5223 its primary guards to fetch descriptors in some edge cases where
5224 it would previously have used fallback directories. Fixes bug
5225 23862; bugfix on 0.3.0.1-alpha.
5227 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5228 - Don't treat inability to store a cached consensus object as a bug:
5229 it can happen normally when we are out of disk space. Fixes bug
5230 24859; bugfix on 0.3.1.1-alpha.
5232 o Minor bugfixes (memory usage, backport from 0.3.2.8-rc):
5233 - When queuing DESTROY cells on a channel, only queue the circuit-id
5234 and reason fields: not the entire 514-byte cell. This fix should
5235 help mitigate any bugs or attacks that fill up these queues, and
5236 free more RAM for other uses. Fixes bug 24666; bugfix
5239 o Minor bugfixes (network layer, backport from 0.3.2.5-alpha):
5240 - When closing a connection via close_connection_immediately(), we
5241 mark it as "not blocked on bandwidth", to prevent later calls from
5242 trying to unblock it, and give it permission to read. This fixes a
5243 backtrace warning that can happen on relays under various
5244 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5246 o Minor bugfixes (path selection, backport from 0.3.2.4-alpha):
5247 - When selecting relays by bandwidth, avoid a rounding error that
5248 could sometimes cause load to be imbalanced incorrectly.
5249 Previously, we would always round upwards; now, we round towards
5250 the nearest integer. This had the biggest effect when a relay's
5251 weight adjustments should have given it weight 0, but it got
5252 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5253 - When calculating the fraction of nodes that have descriptors, and
5254 all nodes in the network have zero bandwidths, count the number of
5255 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5256 - Actually log the total bandwidth in compute_weighted_bandwidths().
5257 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5259 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5260 - Improve the performance of our consensus-diff application code
5261 when Tor is built with the --enable-fragile-hardening option set.
5262 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5264 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5265 - Don't exit the Tor process if setrlimit() fails to change the file
5266 limit (which can happen sometimes on some versions of OSX). Fixes
5267 bug 21074; bugfix on 0.0.9pre5.
5269 o Minor bugfixes (portability, msvc, backport from 0.3.2.9):
5270 - Fix a bug in the bit-counting parts of our timing-wheel code on
5271 MSVC. (Note that MSVC is still not a supported build platform, due
5272 to cyptographic timing channel risks.) Fixes bug 24633; bugfix
5275 o Minor bugfixes (relay, partial backport):
5276 - Make the internal channel_is_client() function look at what sort
5277 of connection handshake the other side used, rather than whether
5278 the other side ever sent a create_fast cell to us. Backports part
5279 of the fixes from bugs 22805 and 24898.
5281 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5282 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5284 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5285 bugfix on 0.2.9.4-alpha.
5287 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5288 - Update the "rust dependencies" submodule to be a project-level
5289 repository, rather than a user repository. Closes ticket 25323.
5292 Changes in version 0.2.9.15 - 2018-03-03
5293 Tor 0.2.9.15 backports important security and stability bugfixes from
5296 It includes an important security fix for a remote crash attack
5297 against directory authorities, tracked as TROVE-2018-001.
5299 This release also backports our new system for improved resistance to
5300 denial-of-service attacks against relays.
5302 This release also fixes several minor bugs and annoyances from
5305 All directory authorities should upgrade to one of the versions
5306 released today. Relays running 0.2.9.x may wish to update to one of
5307 the versions released today, for the DoS mitigations.
5309 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5310 - Fix a protocol-list handling bug that could be used to remotely crash
5311 directory authorities with a null-pointer exception. Fixes bug 25074;
5312 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5315 o Major features (denial-of-service mitigation):
5316 - Give relays some defenses against the recent network overload. We
5317 start with three defenses (default parameters in parentheses).
5318 First: if a single client address makes too many concurrent
5319 connections (>100), hang up on further connections. Second: if a
5320 single client address makes circuits too quickly (more than 3 per
5321 second, with an allowed burst of 90) while also having too many
5322 connections open (3), refuse new create cells for the next while
5323 (1-2 hours). Third: if a client asks to establish a rendezvous
5324 point to you directly, ignore the request. These defenses can be
5325 manually controlled by new torrc options, but relays will also
5326 take guidance from consensus parameters, so there's no need to
5327 configure anything manually. Implements ticket 24902.
5329 o Major bugfixes (bootstrapping):
5330 - Fetch descriptors aggressively whenever we lack enough to build
5331 circuits, regardless of how many descriptors we are missing.
5332 Previously, we would delay launching the fetch when we had fewer
5333 than 15 missing descriptors, even if some of those descriptors
5334 were blocking circuits from building. Fixes bug 23985; bugfix on
5335 0.1.1.11-alpha. The effects of this bug became worse in
5336 0.3.0.3-alpha, when we began treating missing descriptors from our
5337 primary guards as a reason to delay circuits.
5339 o Major bugfixes (onion services, retry behavior):
5340 - Fix an "off by 2" error in counting rendezvous failures on the
5341 onion service side. While we thought we would stop the rendezvous
5342 attempt after one failed circuit, we were actually making three
5343 circuit attempts before giving up. Now switch to a default of 2,
5344 and allow the consensus parameter "hs_service_max_rdv_failures" to
5345 override. Fixes bug 24895; bugfix on 0.0.6.
5347 o Minor feature (relay statistics):
5348 - Change relay bandwidth reporting stats interval from 4 hours to 24
5349 hours in order to reduce the efficiency of guard discovery
5350 attacks. Fixes ticket 23856.
5352 o Minor features (compatibility, OpenSSL):
5353 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5354 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5355 since they neither disabled TLS 1.3 nor enabled any of the
5356 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5357 Closes ticket 24978.
5359 o Minor features (denial-of-service avoidance):
5360 - Make our OOM handler aware of the geoip client history cache so it
5361 doesn't fill up the memory. This check is important for IPv6 and
5362 our DoS mitigation subsystem. Closes ticket 25122.
5364 o Minor features (fallback directory mirrors):
5365 - The fallback directory list has been re-generated based on the
5366 current status of the network. Tor uses fallback directories to
5367 bootstrap when it doesn't yet have up-to-date directory
5368 information. Closes ticket 24801.
5369 - Make the default DirAuthorityFallbackRate 0.1, so that clients
5370 prefer to bootstrap from fallback directory mirrors. This is a
5371 follow-up to 24679, which removed weights from the default
5372 fallbacks. Implements ticket 24681.
5374 o Minor features (geoip):
5375 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5378 o Minor features (linux seccomp2 sandbox):
5379 - Update the sandbox rules so that they should now work correctly
5380 with Glibc 2.26. Closes ticket 24315.
5382 o Minor bugfix (channel connection):
5383 - Use the actual observed address of an incoming relay connection,
5384 not the canonical address of the relay from its descriptor, when
5385 making decisions about how to handle the incoming connection.
5386 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5388 o Minor bugfix (directory authority):
5389 - Directory authorities, when refusing a descriptor from a rejected
5390 relay, now explicitly tell the relay (in its logs) to set a valid
5391 ContactInfo address and contact the bad-relays@ mailing list.
5392 Fixes bug 25170; bugfix on 0.2.9.1.
5394 o Minor bugfixes (address selection):
5395 - When the fascist_firewall_choose_address_ functions don't find a
5396 reachable address, set the returned address to the null address
5397 and port. This is a precautionary measure, because some callers do
5398 not check the return value. Fixes bug 24736; bugfix
5401 o Minor bugfixes (compilation):
5402 - Fix a signed/unsigned comparison warning introduced by our fix to
5403 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
5405 o Minor bugfixes (control port, linux seccomp2 sandbox):
5406 - Avoid a crash when attempting to use the seccomp2 sandbox together
5407 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
5410 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5411 - Fix a possible crash on malformed consensus. If a consensus had
5412 contained an unparseable protocol line, it could have made clients
5413 and relays crash with a null-pointer exception. To exploit this
5414 issue, however, an attacker would need to be able to subvert the
5415 directory authority system. Fixes bug 25251; bugfix on
5416 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5418 o Minor bugfixes (memory usage):
5419 - When queuing DESTROY cells on a channel, only queue the circuit-id
5420 and reason fields: not the entire 514-byte cell. This fix should
5421 help mitigate any bugs or attacks that fill up these queues, and
5422 free more RAM for other uses. Fixes bug 24666; bugfix
5425 o Minor bugfixes (network layer):
5426 - When closing a connection via close_connection_immediately(), we
5427 mark it as "not blocked on bandwidth", to prevent later calls from
5428 trying to unblock it, and give it permission to read. This fixes a
5429 backtrace warning that can happen on relays under various
5430 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
5432 o Minor bugfixes (OSX):
5433 - Don't exit the Tor process if setrlimit() fails to change the file
5434 limit (which can happen sometimes on some versions of OSX). Fixes
5435 bug 21074; bugfix on 0.0.9pre5.
5437 o Minor bugfixes (path selection):
5438 - When selecting relays by bandwidth, avoid a rounding error that
5439 could sometimes cause load to be imbalanced incorrectly.
5440 Previously, we would always round upwards; now, we round towards
5441 the nearest integer. This had the biggest effect when a relay's
5442 weight adjustments should have given it weight 0, but it got
5443 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
5444 - When calculating the fraction of nodes that have descriptors, and
5445 all nodes in the network have zero bandwidths, count the number of
5446 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
5447 - Actually log the total bandwidth in compute_weighted_bandwidths().
5448 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
5450 o Minor bugfixes (portability, msvc):
5451 - Fix a bug in the bit-counting parts of our timing-wheel code on
5452 MSVC. (Note that MSVC is still not a supported build platform, due
5453 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
5456 o Minor bugfixes (relay):
5457 - Make the internal channel_is_client() function look at what sort
5458 of connection handshake the other side used, rather than whether
5459 the other side ever sent a create_fast cell to us. Backports part
5460 of the fixes from bugs 22805 and 24898.
5462 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5463 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5465 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5466 bugfix on 0.2.9.4-alpha.
5469 Changes in version 0.3.2.10 - 2018-03-03
5470 Tor 0.3.2.10 is the second stable release in the 0.3.2 series. It
5471 backports a number of bugfixes, including important fixes for security
5474 It includes an important security fix for a remote crash attack
5475 against directory authorities, tracked as TROVE-2018-001.
5477 Additionally, it backports a fix for a bug whose severity we have
5478 upgraded: Bug 24700, which was fixed in 0.3.3.2-alpha, can be remotely
5479 triggered in order to crash relays with a use-after-free pattern. As
5480 such, we are now tracking that bug as TROVE-2018-002 and
5481 CVE-2018-0491, and backporting it to earlier releases. This bug
5482 affected versions 0.3.2.1-alpha through 0.3.2.9, as well as version
5485 This release also backports our new system for improved resistance to
5486 denial-of-service attacks against relays.
5488 This release also fixes several minor bugs and annoyances from
5491 Relays running 0.3.2.x SHOULD upgrade to one of the versions released
5492 today, for the fix to TROVE-2018-002. Directory authorities should
5493 also upgrade. (Relays on earlier versions might want to update too for
5494 the DoS mitigations.)
5496 o Major bugfixes (denial-of-service, directory authority, backport from 0.3.3.3-alpha):
5497 - Fix a protocol-list handling bug that could be used to remotely crash
5498 directory authorities with a null-pointer exception. Fixes bug 25074;
5499 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5502 o Major bugfixes (scheduler, KIST, denial-of-service, backport from 0.3.3.2-alpha):
5503 - Avoid adding the same channel twice in the KIST scheduler pending
5504 list, which could lead to remote denial-of-service use-after-free
5505 attacks against relays. Fixes bug 24700; bugfix on 0.3.2.1-alpha.
5507 o Major features (denial-of-service mitigation, backport from 0.3.3.2-alpha):
5508 - Give relays some defenses against the recent network overload. We
5509 start with three defenses (default parameters in parentheses).
5510 First: if a single client address makes too many concurrent
5511 connections (>100), hang up on further connections. Second: if a
5512 single client address makes circuits too quickly (more than 3 per
5513 second, with an allowed burst of 90) while also having too many
5514 connections open (3), refuse new create cells for the next while
5515 (1-2 hours). Third: if a client asks to establish a rendezvous
5516 point to you directly, ignore the request. These defenses can be
5517 manually controlled by new torrc options, but relays will also
5518 take guidance from consensus parameters, so there's no need to
5519 configure anything manually. Implements ticket 24902.
5521 o Major bugfixes (onion services, retry behavior, backport from 0.3.3.1-alpha):
5522 - Fix an "off by 2" error in counting rendezvous failures on the
5523 onion service side. While we thought we would stop the rendezvous
5524 attempt after one failed circuit, we were actually making three
5525 circuit attempts before giving up. Now switch to a default of 2,
5526 and allow the consensus parameter "hs_service_max_rdv_failures" to
5527 override. Fixes bug 24895; bugfix on 0.0.6.
5528 - New-style (v3) onion services now obey the "max rendezvous circuit
5529 attempts" logic. Previously they would make as many rendezvous
5530 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5531 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5533 o Major bugfixes (protocol versions, backport from 0.3.3.2-alpha):
5534 - Add Link protocol version 5 to the supported protocols list. Fixes
5535 bug 25070; bugfix on 0.3.1.1-alpha.
5537 o Major bugfixes (relay, backport from 0.3.3.1-alpha):
5538 - Fix a set of false positives where relays would consider
5539 connections to other relays as being client-only connections (and
5540 thus e.g. deserving different link padding schemes) if those
5541 relays fell out of the consensus briefly. Now we look only at the
5542 initial handshake and whether the connection authenticated as a
5543 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5545 o Major bugfixes (scheduler, consensus, backport from 0.3.3.2-alpha):
5546 - The scheduler subsystem was failing to promptly notice changes in
5547 consensus parameters, making it harder to switch schedulers
5548 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5550 o Minor features (denial-of-service avoidance, backport from 0.3.3.2-alpha):
5551 - Make our OOM handler aware of the geoip client history cache so it
5552 doesn't fill up the memory. This check is important for IPv6 and
5553 our DoS mitigation subsystem. Closes ticket 25122.
5555 o Minor features (compatibility, OpenSSL, backport from 0.3.3.3-alpha):
5556 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5557 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5558 since they neither disabled TLS 1.3 nor enabled any of the
5559 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5560 Closes ticket 24978.
5562 o Minor features (geoip):
5563 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5566 o Minor features (logging, diagnostic, backport from 0.3.3.2-alpha):
5567 - When logging a failure to create an onion service's descriptor,
5568 also log what the problem with the descriptor was. Diagnostic
5571 o Minor bugfix (channel connection, backport from 0.3.3.2-alpha):
5572 - Use the actual observed address of an incoming relay connection,
5573 not the canonical address of the relay from its descriptor, when
5574 making decisions about how to handle the incoming connection.
5575 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5577 o Minor bugfixes (denial-of-service, backport from 0.3.3.3-alpha):
5578 - Fix a possible crash on malformed consensus. If a consensus had
5579 contained an unparseable protocol line, it could have made clients
5580 and relays crash with a null-pointer exception. To exploit this
5581 issue, however, an attacker would need to be able to subvert the
5582 directory authority system. Fixes bug 25251; bugfix on
5583 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5585 o Minor bugfix (directory authority, backport from 0.3.3.2-alpha):
5586 - Directory authorities, when refusing a descriptor from a rejected
5587 relay, now explicitly tell the relay (in its logs) to set a valid
5588 ContactInfo address and contact the bad-relays@ mailing list.
5589 Fixes bug 25170; bugfix on 0.2.9.1.
5591 o Minor bugfixes (build, rust, backport from 0.3.3.1-alpha):
5592 - When building with Rust on OSX, link against libresolv, to work
5593 around the issue at https://github.com/rust-lang/rust/issues/46797.
5594 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
5596 o Minor bugfixes (onion services, backport from 0.3.3.2-alpha):
5597 - Remove a BUG() statement when a client fetches an onion descriptor
5598 that has a lower revision counter than the one in its cache. This
5599 can happen in normal circumstances due to HSDir desync. Fixes bug
5600 24976; bugfix on 0.3.2.1-alpha.
5602 o Minor bugfixes (logging, backport from 0.3.3.2-alpha):
5603 - Don't treat inability to store a cached consensus object as a bug:
5604 it can happen normally when we are out of disk space. Fixes bug
5605 24859; bugfix on 0.3.1.1-alpha.
5607 o Minor bugfixes (performance, fragile-hardening, backport from 0.3.3.1-alpha):
5608 - Improve the performance of our consensus-diff application code
5609 when Tor is built with the --enable-fragile-hardening option set.
5610 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
5612 o Minor bugfixes (OSX, backport from 0.3.3.1-alpha):
5613 - Don't exit the Tor process if setrlimit() fails to change the file
5614 limit (which can happen sometimes on some versions of OSX). Fixes
5615 bug 21074; bugfix on 0.0.9pre5.
5617 o Minor bugfixes (spec conformance, backport from 0.3.3.3-alpha):
5618 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5620 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5621 bugfix on 0.2.9.4-alpha.
5623 o Minor bugfixes (testing, backport from 0.3.3.1-alpha):
5624 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
5625 25005; bugfix on 0.3.2.7-rc.
5627 o Minor bugfixes (v3 onion services, backport from 0.3.3.2-alpha):
5628 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5629 version, when deciding whether a consensus entry can support the
5630 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5631 bugfix on 0.3.2.1-alpha.
5633 o Code simplification and refactoring (backport from 0.3.3.3-alpha):
5634 - Update the "rust dependencies" submodule to be a project-level
5635 repository, rather than a user repository. Closes ticket 25323.
5637 o Documentation (backport from 0.3.3.1-alpha)
5638 - Document that operators who run more than one relay or bridge are
5639 expected to set MyFamily and ContactInfo correctly. Closes
5643 Changes in version 0.3.3.3-alpha - 2018-03-03
5644 Tor 0.3.3.3-alpha is the third alpha release for the 0.3.3.x series.
5645 It includes an important security fix for a remote crash attack
5646 against directory authorities tracked as TROVE-2018-001.
5648 Additionally, with this release, we are upgrading the severity of a
5649 bug fixed in 0.3.3.2-alpha. Bug 24700, which was fixed in
5650 0.3.3.2-alpha, can be remotely triggered in order to crash relays with
5651 a use-after-free pattern. As such, we are now tracking that bug as
5652 TROVE-2018-002 and CVE-2018-0491. This bug affected versions
5653 0.3.2.1-alpha through 0.3.2.9, as well as 0.3.3.1-alpha.
5655 This release also fixes several minor bugs and annoyances from
5658 Relays running 0.3.2.x should upgrade to one of the versions released
5659 today, for the fix to TROVE-2018-002. Directory authorities should
5660 also upgrade. (Relays on earlier versions might want to update too for
5661 the DoS mitigations.)
5663 o Major bugfixes (denial-of-service, directory authority):
5664 - Fix a protocol-list handling bug that could be used to remotely crash
5665 directory authorities with a null-pointer exception. Fixes bug 25074;
5666 bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2018-001 and
5669 o Minor features (compatibility, OpenSSL):
5670 - Tor will now support TLS1.3 once OpenSSL 1.1.1 is released.
5671 Previous versions of Tor would not have worked with OpenSSL 1.1.1,
5672 since they neither disabled TLS 1.3 nor enabled any of the
5673 ciphersuites it requires. Now we enable the TLS 1.3 ciphersuites.
5674 Closes ticket 24978.
5676 o Minor features (logging):
5677 - Clarify the log messages produced when getrandom() or a related
5678 entropy-generation mechanism gives an error. Closes ticket 25120.
5680 o Minor features (testing):
5681 - Add a "make test-rust" target to run the rust tests only. Closes
5684 o Minor bugfixes (denial-of-service):
5685 - Fix a possible crash on malformed consensus. If a consensus had
5686 contained an unparseable protocol line, it could have made clients
5687 and relays crash with a null-pointer exception. To exploit this
5688 issue, however, an attacker would need to be able to subvert the
5689 directory authority system. Fixes bug 25251; bugfix on
5690 0.2.9.4-alpha. Also tracked as TROVE-2018-004.
5692 o Minor bugfixes (DoS mitigation):
5693 - Add extra safety checks when refilling the circuit creation bucket
5694 to ensure we never set a value above the allowed maximum burst.
5695 Fixes bug 25202; bugfix on 0.3.3.2-alpha.
5696 - When a new consensus arrives, don't update our DoS-mitigation
5697 parameters if we aren't a public relay. Fixes bug 25223; bugfix
5700 o Minor bugfixes (man page, SocksPort):
5701 - Remove dead code from the old "SocksSocket" option, and rename
5702 SocksSocketsGroupWritable to UnixSocksGroupWritable. The old option
5703 still works, but is deprecated. Fixes bug 24343; bugfix on 0.2.6.3.
5705 o Minor bugfixes (performance):
5706 - Reduce the number of circuits that will be opened at once during
5707 the circuit build timeout phase. This is done by increasing the
5708 idle timeout to 3 minutes, and lowering the maximum number of
5709 concurrent learning circuits to 10. Fixes bug 24769; bugfix
5712 o Minor bugfixes (spec conformance):
5713 - Forbid "-0" as a protocol version. Fixes part of bug 25249; bugfix on
5715 - Forbid UINT32_MAX as a protocol version. Fixes part of bug 25249;
5716 bugfix on 0.2.9.4-alpha.
5718 o Minor bugfixes (spec conformance, rust):
5719 - Resolve a denial-of-service issue caused by an infinite loop in
5720 the rust protover code. Fixes bug 25250, bugfix on 0.3.3.1-alpha.
5721 Also tracked as TROVE-2018-003.
5723 o Code simplification and refactoring:
5724 - Update the "rust dependencies" submodule to be a project-level
5725 repository, rather than a user repository. Closes ticket 25323.
5728 Changes in version 0.3.3.2-alpha - 2018-02-10
5729 Tor 0.3.3.2-alpha is the second alpha in the 0.3.3.x series. It
5730 introduces a mechanism to handle the high loads that many relay
5731 operators have been reporting recently. It also fixes several bugs in
5732 older releases. If this new code proves reliable, we plan to backport
5733 it to older supported release series.
5735 o Major features (denial-of-service mitigation):
5736 - Give relays some defenses against the recent network overload. We
5737 start with three defenses (default parameters in parentheses).
5738 First: if a single client address makes too many concurrent
5739 connections (>100), hang up on further connections. Second: if a
5740 single client address makes circuits too quickly (more than 3 per
5741 second, with an allowed burst of 90) while also having too many
5742 connections open (3), refuse new create cells for the next while
5743 (1-2 hours). Third: if a client asks to establish a rendezvous
5744 point to you directly, ignore the request. These defenses can be
5745 manually controlled by new torrc options, but relays will also
5746 take guidance from consensus parameters, so there's no need to
5747 configure anything manually. Implements ticket 24902.
5749 o Major bugfixes (netflow padding):
5750 - Stop adding unneeded channel padding right after we finish
5751 flushing to a connection that has been trying to flush for many
5752 seconds. Instead, treat all partial or complete flushes as
5753 activity on the channel, which will defer the time until we need
5754 to add padding. This fix should resolve confusing and scary log
5755 messages like "Channel padding timeout scheduled 221453ms in the
5756 past." Fixes bug 22212; bugfix on 0.3.1.1-alpha.
5758 o Major bugfixes (protocol versions):
5759 - Add Link protocol version 5 to the supported protocols list. Fixes
5760 bug 25070; bugfix on 0.3.1.1-alpha.
5762 o Major bugfixes (scheduler, consensus):
5763 - The scheduler subsystem was failing to promptly notice changes in
5764 consensus parameters, making it harder to switch schedulers
5765 network-wide. Fixes bug 24975; bugfix on 0.3.2.1-alpha.
5767 o Minor features (denial-of-service avoidance):
5768 - Make our OOM handler aware of the geoip client history cache so it
5769 doesn't fill up the memory. This check is important for IPv6 and
5770 our DoS mitigation subsystem. Closes ticket 25122.
5772 o Minor features (directory authority):
5773 - When directory authorities are unable to add signatures to a
5774 pending consensus, log the reason why. Closes ticket 24849.
5776 o Minor features (geoip):
5777 - Update geoip and geoip6 to the February 7 2018 Maxmind GeoLite2
5780 o Minor features (logging, diagnostic):
5781 - When logging a failure to create an onion service's descriptor,
5782 also log what the problem with the descriptor was. Diagnostic for
5785 o Minor bugfix (channel connection):
5786 - Use the actual observed address of an incoming relay connection,
5787 not the canonical address of the relay from its descriptor, when
5788 making decisions about how to handle the incoming connection.
5789 Fixes bug 24952; bugfix on 0.2.4.11-alpha. Patch by "ffmancera".
5791 o Minor bugfix (directory authority):
5792 - Directory authorities, when refusing a descriptor from a rejected
5793 relay, now explicitly tell the relay (in its logs) to set a valid
5794 ContactInfo address and contact the bad-relays@ mailing list.
5795 Fixes bug 25170; bugfix on 0.2.9.1.
5797 o Minor bugfixes (all versions of Tor):
5798 - Use the "misspell" tool to detect and fix typos throughout the
5799 source code. Fixes bug 23650; bugfix on various versions of Tor.
5800 Patch from Deepesh Pathak.
5802 o Minor bugfixes (circuit, cannibalization):
5803 - Don't cannibalize preemptively-built circuits if we no longer
5804 recognize their first hop. This situation can happen if our Guard
5805 relay went off the consensus after the circuit was created. Fixes
5806 bug 24469; bugfix on 0.0.6.
5808 o Minor bugfixes (correctness):
5809 - Remove a nonworking, unnecessary check to see whether a circuit
5810 hop's identity digest was set when the circuit failed. Fixes bug
5811 24927; bugfix on 0.2.4.4-alpha.
5813 o Minor bugfixes (logging):
5814 - Don't treat inability to store a cached consensus object as a bug:
5815 it can happen normally when we are out of disk space. Fixes bug
5816 24859; bugfix on 0.3.1.1-alpha.
5817 - Fix a (mostly harmless) race condition when invoking
5818 LOG_PROTOCOL_WARN message from a subthread while the torrc options
5819 are changing. Fixes bug 23954; bugfix on 0.1.1.9-alpha.
5821 o Minor bugfixes (onion services):
5822 - Remove a BUG() statement when a client fetches an onion descriptor
5823 that has a lower revision counter than the one in its cache. This
5824 can happen in normal circumstances due to HSDir desync. Fixes bug
5825 24976; bugfix on 0.3.2.1-alpha.
5826 - If we are configured to offer a single onion service, don't log
5827 long-term established one hop rendezvous points in the heartbeat.
5828 Fixes bug 25116; bugfix on 0.2.9.6-rc.
5830 o Minor bugfixes (performance):
5831 - Avoid calling protocol_list_supports_protocol() from inside tight
5832 loops when running with cached routerinfo_t objects. Instead,
5833 summarize the relevant protocols as flags in the routerinfo_t, as
5834 we do for routerstatus_t objects. This change simplifies our code
5835 a little, and saves a large amount of short-term memory allocation
5836 operations. Fixes bug 25008; bugfix on 0.2.9.4-alpha.
5838 o Minor bugfixes (Rust FFI):
5839 - Fix a minor memory leak which would happen whenever the C code
5840 would call the Rust implementation of
5841 protover_get_supported_protocols(). This was due to the C version
5842 returning a static string, whereas the Rust version newly allocated
5843 a CString to pass across the FFI boundary. Consequently, the C
5844 code was not expecting to need to free() what it was given. Fixes
5845 bug 25127; bugfix on 0.3.2.1-alpha.
5847 o Minor bugfixes (scheduler, KIST):
5848 - Avoid adding the same channel twice in the KIST scheduler pending
5849 list, which would waste CPU cycles. Fixes bug 24700; bugfix
5852 o Minor bugfixes (unit test, monotonic time):
5853 - Increase a constant (1msec to 10msec) in the monotonic time test
5854 that makes sure the nsec/usec/msec times read are synchronized.
5855 This change was needed to accommodate slow systems like armel or
5856 when the clock_gettime() is not a VDSO on the running kernel.
5857 Fixes bug 25113; bugfix on 0.2.9.1.
5859 o Minor bugfixes (v3 onion services):
5860 - Look at the "HSRend" protocol version, not the "HSDir" protocol
5861 version, when deciding whether a consensus entry can support the
5862 v3 onion service protocol as a rendezvous point. Fixes bug 25105;
5863 bugfix on 0.3.2.1-alpha.
5865 o Code simplification and refactoring:
5866 - Remove the unused nodelist_recompute_all_hsdir_indices(). Closes
5868 - Remove a series of counters used to track circuit extend attempts
5869 and connection status but that in reality we aren't using for
5870 anything other than stats logged by a SIGUSR1 signal. Closes
5873 o Documentation (man page):
5874 - The HiddenServiceVersion torrc option accepts only one number:
5875 either version 2 or 3. Closes ticket 25026; bugfix
5879 Changes in version 0.3.3.1-alpha - 2018-01-25
5880 Tor 0.3.3.1-alpha is the first release in the 0.3.3.x series. It adds
5881 several new features to Tor, including several improvements to
5882 bootstrapping, and support for an experimental "vanguards" feature to
5883 resist guard discovery attacks. This series also includes better
5884 support for applications that need to embed Tor or manage v3
5887 o Major features (embedding):
5888 - There is now a documented stable API for programs that need to
5889 embed Tor. See tor_api.h for full documentation and known bugs.
5890 Closes ticket 23684.
5891 - Tor now has support for restarting in the same process.
5892 Controllers that run Tor using the "tor_api.h" interface can now
5893 restart Tor after Tor has exited. This support is incomplete,
5894 however: we fixed crash bugs that prevented it from working at
5895 all, but many bugs probably remain, including a possibility of
5896 security issues. Implements ticket 24581.
5898 o Major features (IPv6, directory documents):
5899 - Add consensus method 27, which adds IPv6 ORPorts to the microdesc
5900 consensus. This information makes it easier for IPv6 clients to
5901 bootstrap and choose reachable entry guards. Implements ticket 23826.
5902 - Add consensus method 28, which removes IPv6 ORPorts from
5903 microdescriptors. Now that the consensus contains IPv6 ORPorts, they
5904 are redundant in microdescs. This change will be used by Tor clients
5905 on 0.2.8.x and later. (That is to say, with all Tor clients that
5906 have IPv6 bootstrap and guard support.) Implements ticket 23828.
5907 - Expand the documentation for AuthDirHasIPv6Connectivity when it is
5908 set by different numbers of authorities. Fixes 23870
5911 o Major features (onion service v3, control port):
5912 - The control port now supports commands and events for v3 onion
5913 services. It is now possible to create ephemeral v3 services using
5914 ADD_ONION. Additionally, several events (HS_DESC, HS_DESC_CONTENT,
5915 CIRC and CIRC_MINOR) and commands (GETINFO, HSPOST, ADD_ONION and
5916 DEL_ONION) have been extended to support v3 onion services. Closes
5917 ticket 20699; implements proposal 284.
5919 o Major features (onion services):
5920 - Provide torrc options to pin the second and third hops of onion
5921 service circuits to a list of nodes. The option HSLayer2Guards
5922 pins the second hop, and the option HSLayer3Guards pins the third
5923 hop. These options are for use in conjunction with experiments
5924 with "vanguards" for preventing guard enumeration attacks. Closes
5927 o Major features (rust, portability, experimental):
5928 - Tor now ships with an optional implementation of one of its
5929 smaller modules (protover.c) in the Rust programming language. To
5930 try it out, install a Rust build environment, and configure Tor
5931 with "--enable-rust --enable-cargo-online-mode". This should not
5932 cause any user-visible changes, but should help us gain more
5933 experience with Rust, and plan future Rust integration work.
5934 Implementation by Chelsea Komlo. Closes ticket 22840.
5936 o Minor features (storage, configuration):
5937 - Users can store cached directory documents somewhere other than
5938 the DataDirectory by using the CacheDirectory option. Similarly,
5939 the storage location for relay's keys can be overridden with the
5940 KeyDirectory option. Closes ticket 22703.
5942 o Major features (v3 onion services, ipv6):
5943 - When v3 onion service clients send introduce cells, they now
5944 include the IPv6 address of the rendezvous point, if it has one.
5945 Current v3 onion services running 0.3.2 ignore IPv6 addresses, but
5946 in future Tor versions, IPv6-only v3 single onion services will be
5947 able to use IPv6 addresses to connect directly to the rendezvous
5948 point. Closes ticket 23577. Patch by Neel Chauhan.
5950 o Major bugfixes (onion services, retry behavior):
5951 - Fix an "off by 2" error in counting rendezvous failures on the
5952 onion service side. While we thought we would stop the rendezvous
5953 attempt after one failed circuit, we were actually making three
5954 circuit attempts before giving up. Now switch to a default of 2,
5955 and allow the consensus parameter "hs_service_max_rdv_failures" to
5956 override. Fixes bug 24895; bugfix on 0.0.6.
5957 - New-style (v3) onion services now obey the "max rendezvous circuit
5958 attempts" logic. Previously they would make as many rendezvous
5959 circuit attempts as they could fit in the MAX_REND_TIMEOUT second
5960 window before giving up. Fixes bug 24894; bugfix on 0.3.2.1-alpha.
5962 o Major bugfixes (relays):
5963 - Fix a set of false positives where relays would consider
5964 connections to other relays as being client-only connections (and
5965 thus e.g. deserving different link padding schemes) if those
5966 relays fell out of the consensus briefly. Now we look only at the
5967 initial handshake and whether the connection authenticated as a
5968 relay. Fixes bug 24898; bugfix on 0.3.1.1-alpha.
5970 o Minor feature (IPv6):
5971 - Make IPv6-only clients wait for microdescs for relays, even if we
5972 were previously using descriptors (or were using them as a bridge)
5973 and have a cached descriptor for them. Implements ticket 23827.
5974 - When a consensus has IPv6 ORPorts, make IPv6-only clients use
5975 them, rather than waiting to download microdescriptors.
5976 Implements ticket 23827.
5978 o Minor features (cleanup):
5979 - Tor now deletes the CookieAuthFile and ExtORPortCookieAuthFile
5980 when it stops. Closes ticket 23271.
5982 o Minor features (defensive programming):
5983 - Most of the functions in Tor that free objects have been replaced
5984 with macros that free the objects and set the corresponding
5985 pointers to NULL. This change should help prevent a large class of
5986 dangling pointer bugs. Closes ticket 24337.
5987 - Where possible, the tor_free() macro now only evaluates its input
5988 once. Part of ticket 24337.
5989 - Check that microdesc ed25519 ids are non-zero in
5990 node_get_ed25519_id() before returning them. Implements ticket
5991 24001, patch by "aruna1234".
5993 o Minor features (embedding):
5994 - Tor can now start with a preauthenticated control connection
5995 created by the process that launched it. This feature is meant for
5996 use by programs that want to launch and manage a Tor process
5997 without allowing other programs to manage it as well. For more
5998 information, see the __OwningControllerFD option documented in
5999 control-spec.txt. Closes ticket 23900.
6000 - On most errors that would cause Tor to exit, it now tries to
6001 return from the tor_main() function, rather than calling the
6002 system exit() function. Most users won't notice a difference here,
6003 but it should be significant for programs that run Tor inside
6004 a separate thread: they should now be able to survive Tor's exit
6005 conditions rather than having Tor shut down the entire process.
6006 Closes ticket 23848.
6007 - Applications that want to embed Tor can now tell Tor not to
6008 register any of its own POSIX signal handlers, using the
6009 __DisableSignalHandlers option. Closes ticket 24588.
6011 o Minor features (fallback directory list):
6012 - Avoid selecting fallbacks that change their IP addresses too
6013 often. Select more fallbacks by ignoring the Guard flag, and
6014 allowing lower cutoffs for the Running and V2Dir flags. Also allow
6015 a lower bandwidth, and a higher number of fallbacks per operator
6016 (5% of the list). Implements ticket 24785.
6017 - Update the fallback whitelist and blacklist based on opt-ins and
6018 relay changes. Closes tickets 22321, 24678, 22527, 24135,
6021 o Minor features (fallback directory mirror configuration):
6022 - Add a nickname to each fallback in a C comment. This makes it
6023 easier for operators to find their relays, and allows stem to use
6024 nicknames to identify fallbacks. Implements ticket 24600.
6025 - Add a type and version header to the fallback directory mirror
6026 file. Also add a delimiter to the end of each fallback entry. This
6027 helps external parsers like stem and Relay Search. Implements
6029 - Add an extrainfo cache flag for each fallback in a C comment. This
6030 allows stem to use fallbacks to fetch extra-info documents, rather
6031 than using authorities. Implements ticket 22759.
6032 - Add the generateFallbackDirLine.py script for automatically
6033 generating fallback directory mirror lines from relay fingerprints.
6034 No more typos! Add the lookupFallbackDirContact.py script for
6035 automatically looking up operator contact info from relay
6036 fingerprints. Implements ticket 24706, patch by teor and atagar.
6037 - Reject any fallback directory mirror that serves an expired
6038 consensus. Implements ticket 20942, patch by "minik".
6039 - Remove commas and equals signs from external string inputs to the
6040 fallback list. This avoids format confusion attacks. Implements
6042 - Remove the "weight=10" line from fallback directory mirror
6043 entries. Ticket 24681 will maintain the current fallback weights
6044 by changing Tor's default fallback weight to 10. Implements
6046 - Stop logging excessive information about fallback netblocks.
6047 Implements ticket 24791.
6049 o Minor features (forward-compatibility):
6050 - If a relay supports some link authentication protocol that we do
6051 not recognize, then include that relay's ed25519 key when telling
6052 other relays to extend to it. Previously, we treated future
6053 versions as if they were too old to support ed25519 link
6054 authentication. Closes ticket 20895.
6056 o Minor features (heartbeat):
6057 - Add onion service information to our heartbeat logs, displaying
6058 stats about the activity of configured onion services. Closes
6061 o Minor features (instrumentation, development):
6062 - Add the MainloopStats option to allow developers to get
6063 instrumentation information from the main event loop via the
6064 heartbeat messages. We hope to use this to improve Tor's behavior
6065 when it's trying to sleep. Closes ticket 24605.
6067 o Minor features (log messages):
6068 - Improve a warning message that happens when we fail to re-parse an
6069 old router because of an expired certificate. Closes ticket 20020.
6070 - Make the log more quantitative when we hit MaxMemInQueues
6071 threshold exposing some values. Closes ticket 24501.
6073 o Minor features (logging, android):
6074 - Added support for the Android logging subsystem. Closes
6077 o Minor features (performance):
6078 - Support predictive circuit building for onion service circuits
6079 with multiple layers of guards. Closes ticket 23101.
6080 - Use stdatomic.h where available, rather than mutexes, to implement
6081 atomic_counter_t. Closes ticket 23953.
6083 o Minor features (performance, 32-bit):
6084 - Improve performance on 32-bit systems by avoiding 64-bit division
6085 when calculating the timestamp in milliseconds for channel padding
6086 computations. Implements ticket 24613.
6087 - Improve performance on 32-bit systems by avoiding 64-bit division
6088 when timestamping cells and buffer chunks for OOM calculations.
6089 Implements ticket 24374.
6091 o Minor features (performance, OSX, iOS):
6092 - Use the mach_approximate_time() function (when available) to
6093 implement coarse monotonic time. Having a coarse time function
6094 should avoid a large number of system calls, and improve
6095 performance slightly, especially under load. Closes ticket 24427.
6097 o Minor features (performance, windows):
6098 - Improve performance on Windows Vista and Windows 7 by adjusting
6099 TCP send window size according to the recommendation from
6100 SIO_IDEAL_SEND_BACKLOG_QUERY. Closes ticket 22798. Patch
6103 o Major features (relay):
6104 - Implement an option, ReducedExitPolicy, to allow an Tor exit relay
6105 operator to use a more reasonable ("reduced") exit policy, rather
6106 than the default one. If you want to run an exit node without
6107 thinking too hard about which ports to allow, this one is for you.
6108 Closes ticket 13605. Patch from Neel Chauhan.
6110 o Minor features (testing, debugging, embedding):
6111 - For development purposes, Tor now has a mode in which it runs for
6112 a few seconds, then stops, and starts again without exiting the
6113 process. This mode is meant to help us debug various issues with
6114 ticket 23847. To use this feature, compile with
6115 --enable-restart-debugging, and set the TOR_DEBUG_RESTART
6116 environment variable. This is expected to crash a lot, and is
6117 really meant for developers only. It will likely be removed in a
6118 future release. Implements ticket 24583.
6120 o Minor bugfix (network IPv6 test):
6121 - Tor's test scripts now check if "ping -6 ::1" works when the user
6122 runs "make test-network-all". Fixes bug 24677; bugfix on
6123 0.2.9.3-alpha. Patch by "ffmancera".
6125 o Minor bugfixes (build, rust):
6126 - Fix output of autoconf checks to display success messages for Rust
6127 dependencies and a suitable rustc compiler version. Fixes bug
6128 24612; bugfix on 0.3.1.3-alpha.
6129 - When building with Rust on OSX, link against libresolv, to work
6130 around the issue at https://github.com/rust-lang/rust/issues/46797.
6131 Fixes bug 24652; bugfix on 0.3.1.1-alpha.
6132 - Don't pass the --quiet option to cargo: it seems to suppress some
6133 errors, which is not what we want to do when building. Fixes bug
6134 24518; bugfix on 0.3.1.7.
6135 - Build correctly when building from outside Tor's source tree with
6136 the TOR_RUST_DEPENDENCIES option set. Fixes bug 22768; bugfix
6139 o Minor bugfixes (directory authorities, IPv6):
6140 - When creating a routerstatus (vote) from a routerinfo (descriptor),
6141 set the IPv6 address to the unspecified IPv6 address, and
6142 explicitly initialize the port to zero. Fixes bug 24488; bugfix
6145 o Minor bugfixes (fallback directory mirrors):
6146 - Make updateFallbackDirs.py search harder for python. (Some OSs
6147 don't put it in /usr/bin.) Fixes bug 24708; bugfix
6150 o Minor bugfixes (hibernation, bandwidth accounting, shutdown):
6151 - When hibernating, close connections normally and allow them to
6152 flush. Fixes bug 23571; bugfix on 0.2.4.7-alpha. Also fixes
6154 - Do not attempt to launch self-reachability tests when entering
6155 hibernation. Fixes a case of bug 12062; bugfix on 0.0.9pre5.
6156 - Resolve several bugs related to descriptor fetching on bridge
6157 clients with bandwidth accounting enabled. (This combination is
6158 not recommended!) Fixes a case of bug 12062; bugfix
6160 - When hibernating, do not attempt to launch DNS checks. Fixes a
6161 case of bug 12062; bugfix on 0.1.2.2-alpha.
6162 - When hibernating, do not try to upload or download descriptors.
6163 Fixes a case of bug 12062; bugfix on 0.0.9pre5.
6165 o Minor bugfixes (IPv6, bridges):
6166 - Tor now always sets IPv6 preferences for bridges. Fixes bug 24573;
6167 bugfix on 0.2.8.2-alpha.
6168 - Tor now sets IPv6 address in the routerstatus as well as in the
6169 router descriptors when updating addresses for a bridge. Closes
6170 ticket 24572; bugfix on 0.2.4.5-alpha. Patch by "ffmancera".
6172 o Minor bugfixes (linux seccomp2 sandbox):
6173 - When running with the sandbox enabled, reload configuration files
6174 correctly even when %include was used. Previously we would crash.
6175 Fixes bug 22605; bugfix on 0.3.1. Patch from Daniel Pinto.
6177 o Minor bugfixes (memory leaks):
6178 - Avoid possible at-exit memory leaks related to use of Libevent's
6179 event_base_once() function. (This function tends to leak memory if
6180 the event_base is closed before the event fires.) Fixes bug 24584;
6181 bugfix on 0.2.8.1-alpha.
6182 - Fix a harmless memory leak in tor-resolve. Fixes bug 24582; bugfix
6185 o Minor bugfixes (OSX):
6186 - Don't exit the Tor process if setrlimit() fails to change the file
6187 limit (which can happen sometimes on some versions of OSX). Fixes
6188 bug 21074; bugfix on 0.0.9pre5.
6190 o Minor bugfixes (performance, fragile-hardening):
6191 - Improve the performance of our consensus-diff application code
6192 when Tor is built with the --enable-fragile-hardening option set.
6193 Fixes bug 24826; bugfix on 0.3.1.1-alpha.
6195 o Minor bugfixes (performance, timeouts):
6196 - Consider circuits for timeout as soon as they complete a hop. This
6197 is more accurate than applying the timeout in
6198 circuit_expire_building() because that function is only called
6199 once per second, which is now too slow for typical timeouts on the
6200 current network. Fixes bug 23114; bugfix on 0.2.2.2-alpha.
6201 - Use onion service circuits (and other circuits longer than 3 hops)
6202 to calculate a circuit build timeout. Previously, Tor only
6203 calculated its build timeout based on circuits that planned to be
6204 exactly 3 hops long. With this change, we include measurements
6205 from all circuits at the point where they complete their third
6206 hop. Fixes bug 23100; bugfix on 0.2.2.2-alpha.
6208 o Minor bugfixes (testing):
6209 - Give out Exit flags in bootstrapping networks. Fixes bug 24137;
6210 bugfix on 0.2.3.1-alpha.
6211 - Fix a memory leak in the scheduler/loop_kist unit test. Fixes bug
6212 25005; bugfix on 0.3.2.7-rc.
6214 o Code simplification and refactoring:
6215 - Remove /usr/athena from search path in configure.ac. Closes
6217 - Remove duplicate code in node_has_curve25519_onion_key() and
6218 node_get_curve25519_onion_key(), and add a check for a zero
6219 microdesc curve25519 onion key. Closes ticket 23966, patch by
6220 "aruna1234" and teor.
6221 - Rewrite channel_rsa_id_group_set_badness to reduce temporary
6222 memory allocations with large numbers of OR connections (e.g.
6223 relays). Closes ticket 24119.
6224 - Separate the function that deletes ephemeral files when Tor
6226 - Small changes to Tor's buf_t API to make it suitable for use as a
6227 general-purpose safe string constructor. Closes ticket 22342.
6228 - Switch -Wnormalized=id to -Wnormalized=nfkc in configure.ac to
6229 avoid source code identifier confusion. Closes ticket 24467.
6230 - The tor_git_revision[] constant no longer needs to be redeclared
6231 by everything that links against the rest of Tor. Done as part of
6232 ticket 23845, to simplify our external API.
6233 - We make extend_info_from_node() use node_get_curve25519_onion_key()
6234 introduced in ticket 23577 to access the curve25519 public keys
6235 rather than accessing it directly. Closes ticket 23760. Patch by
6237 - Add a function to log channels' scheduler state changes to aid
6238 debugging efforts. Closes ticket 24531.
6241 - Add documentation on how to build tor with Rust dependencies
6242 without having to be online. Closes ticket 22907; bugfix
6244 - Clarify the behavior of RelayBandwidth{Rate,Burst} with client
6245 traffic. Closes ticket 24318.
6246 - Document that OutboundBindAddress doesn't apply to DNS requests.
6247 Closes ticket 22145. Patch from Aruna Maurya.
6248 - Document that operators who run more than one relay or bridge are
6249 expected to set MyFamily and ContactInfo correctly. Closes
6252 o Code simplification and refactoring (channels):
6253 - Remove the incoming and outgoing channel queues. These were never
6254 used, but still took up a step in our fast path.
6255 - The majority of the channel unit tests have been rewritten and the
6256 code coverage has now been raised to 83.6% for channel.c. Closes
6258 - Remove other dead code from the channel subsystem: All together,
6259 this cleanup has removed more than 1500 lines of code overall and
6260 adding very little except for unit test.
6262 o Code simplification and refactoring (circuit rendezvous):
6263 - Split the client-side rendezvous circuit lookup into two
6264 functions: one that returns only established circuits and another
6265 that returns all kinds of circuits. Closes ticket 23459.
6267 o Code simplification and refactoring (controller):
6268 - Make most of the variables in networkstatus_getinfo_by_purpose()
6269 const. Implements ticket 24489.
6272 Changes in version 0.3.2.9 - 2018-01-09
6273 Tor 0.3.2.9 is the first stable release in the 0.3.2 series.
6275 The 0.3.2 series includes our long-anticipated new onion service
6276 design, with numerous security features. (For more information, see
6277 our blog post at https://blog.torproject.org/fall-harvest.) We also
6278 have a new circuit scheduler algorithm for improved performance on
6279 relays everywhere (see https://blog.torproject.org/kist-and-tell),
6280 along with many smaller features and bugfixes.
6282 Per our stable release policy, we plan to support each stable release
6283 series for at least the next nine months, or for three months after
6284 the first stable release of the next series: whichever is longer. If
6285 you need a release with long-term support, we recommend that you stay
6286 with the 0.2.9 series.
6288 Below is a list of the changes since 0.3.2.8-rc. For a list of all
6289 changes since 0.3.1, see the ReleaseNotes file.
6291 o Minor features (fallback directory mirrors):
6292 - The fallback directory list has been re-generated based on the
6293 current status of the network. Tor uses fallback directories to
6294 bootstrap when it doesn't yet have up-to-date directory
6295 information. Closes ticket 24801.
6296 - Make the default DirAuthorityFallbackRate 0.1, so that clients
6297 prefer to bootstrap from fallback directory mirrors. This is a
6298 follow-up to 24679, which removed weights from the default
6299 fallbacks. Implements ticket 24681.
6301 o Minor features (geoip):
6302 - Update geoip and geoip6 to the January 5 2018 Maxmind GeoLite2
6305 o Minor bugfixes (address selection):
6306 - When the fascist_firewall_choose_address_ functions don't find a
6307 reachable address, set the returned address to the null address
6308 and port. This is a precautionary measure, because some callers do
6309 not check the return value. Fixes bug 24736; bugfix
6312 o Minor bugfixes (compilation):
6313 - Resolve a few shadowed-variable warnings in the onion service
6314 code. Fixes bug 24634; bugfix on 0.3.2.1-alpha.
6316 o Minor bugfixes (portability, msvc):
6317 - Fix a bug in the bit-counting parts of our timing-wheel code on
6318 MSVC. (Note that MSVC is still not a supported build platform, due
6319 to cryptographic timing channel risks.) Fixes bug 24633; bugfix
6323 Changes in version 0.3.2.8-rc - 2017-12-21
6324 Tor 0.3.2.8-rc fixes a pair of bugs in the KIST and KISTLite
6325 schedulers that had led servers under heavy load to overload their
6326 outgoing connections. All relay operators running earlier 0.3.2.x
6327 versions should upgrade. This version also includes a mitigation for
6328 over-full DESTROY queues leading to out-of-memory conditions: if it
6329 works, we will soon backport it to earlier release series.
6331 This is the second release candidate in the 0.3.2 series. If we find
6332 no new bugs or regression here, then the first stable 0.3.2 release
6333 will be nearly identical to this.
6335 o Major bugfixes (KIST, scheduler):
6336 - The KIST scheduler did not correctly account for data already
6337 enqueued in each connection's send socket buffer, particularly in
6338 cases when the TCP/IP congestion window was reduced between
6339 scheduler calls. This situation lead to excessive per-connection
6340 buffering in the kernel, and a potential memory DoS. Fixes bug
6341 24665; bugfix on 0.3.2.1-alpha.
6343 o Minor features (geoip):
6344 - Update geoip and geoip6 to the December 6 2017 Maxmind GeoLite2
6347 o Minor bugfixes (hidden service v3):
6348 - Bump hsdir_spread_store parameter from 3 to 4 in order to increase
6349 the probability of reaching a service for a client missing
6350 microdescriptors. Fixes bug 24425; bugfix on 0.3.2.1-alpha.
6352 o Minor bugfixes (memory usage):
6353 - When queuing DESTROY cells on a channel, only queue the circuit-id
6354 and reason fields: not the entire 514-byte cell. This fix should
6355 help mitigate any bugs or attacks that fill up these queues, and
6356 free more RAM for other uses. Fixes bug 24666; bugfix
6359 o Minor bugfixes (scheduler, KIST):
6360 - Use a sane write limit for KISTLite when writing onto a connection
6361 buffer instead of using INT_MAX and shoving as much as it can.
6362 Because the OOM handler cleans up circuit queues, we are better
6363 off at keeping them in that queue instead of the connection's
6364 buffer. Fixes bug 24671; bugfix on 0.3.2.1-alpha.
6367 Changes in version 0.3.2.7-rc - 2017-12-14
6368 Tor 0.3.2.7-rc fixes various bugs in earlier versions of Tor,
6369 including some that could affect reliability or correctness.
6371 This is the first release candidate in the 0.3.2 series. If we find no
6372 new bugs or regression here, then the first stable 0.3.2. release will
6373 be nearly identical to this.
6375 o Major bugfixes (circuit prediction):
6376 - Fix circuit prediction logic so that a client doesn't treat a port
6377 as being "handled" by a circuit if that circuit already has
6378 isolation settings on it. This change should make Tor clients more
6379 responsive by improving their chances of having a pre-created
6380 circuit ready for use when a request arrives. Fixes bug 18859;
6381 bugfix on 0.2.3.3-alpha.
6383 o Minor features (logging):
6384 - Provide better warnings when the getrandom() syscall fails. Closes
6387 o Minor features (portability):
6388 - Tor now compiles correctly on arm64 with libseccomp-dev installed.
6389 (It doesn't yet work with the sandbox enabled.) Closes
6392 o Minor bugfixes (bridge clients, bootstrap):
6393 - Retry directory downloads when we get our first bridge descriptor
6394 during bootstrap or while reconnecting to the network. Keep
6395 retrying every time we get a bridge descriptor, until we have a
6396 reachable bridge. Fixes part of bug 24367; bugfix on 0.2.0.3-alpha.
6397 - Stop delaying bridge descriptor fetches when we have cached bridge
6398 descriptors. Instead, only delay bridge descriptor fetches when we
6399 have at least one reachable bridge. Fixes part of bug 24367;
6400 bugfix on 0.2.0.3-alpha.
6401 - Stop delaying directory fetches when we have cached bridge
6402 descriptors. Instead, only delay bridge descriptor fetches when
6403 all our bridges are definitely unreachable. Fixes part of bug
6404 24367; bugfix on 0.2.0.3-alpha.
6406 o Minor bugfixes (compilation):
6407 - Fix a signed/unsigned comparison warning introduced by our fix to
6408 TROVE-2017-009. Fixes bug 24480; bugfix on 0.2.5.16.
6410 o Minor bugfixes (correctness):
6411 - Fix several places in our codebase where a C compiler would be
6412 likely to eliminate a check, based on assuming that undefined
6413 behavior had not happened elsewhere in the code. These cases are
6414 usually a sign of redundant checking or dubious arithmetic. Found
6415 by Georg Koppen using the "STACK" tool from Wang, Zeldovich,
6416 Kaashoek, and Solar-Lezama. Fixes bug 24423; bugfix on various
6419 o Minor bugfixes (onion service v3):
6420 - Fix a race where an onion service would launch a new intro circuit
6421 after closing an old one, but fail to register it before freeing
6422 the previously closed circuit. This bug was making the service
6423 unable to find the established intro circuit and thus not upload
6424 its descriptor, thus making a service unavailable for up to 24
6425 hours. Fixes bug 23603; bugfix on 0.3.2.1-alpha.
6427 o Minor bugfixes (scheduler, KIST):
6428 - Properly set the scheduler state of an unopened channel in the
6429 KIST scheduler main loop. This prevents a harmless but annoying
6430 log warning. Fixes bug 24502; bugfix on 0.3.2.4-alpha.
6431 - Avoid a possible integer overflow when computing the available
6432 space on the TCP buffer of a channel. This had no security
6433 implications; but could make KIST allow too many cells on a
6434 saturated connection. Fixes bug 24590; bugfix on 0.3.2.1-alpha.
6435 - Downgrade to "info" a harmless warning about the monotonic time
6436 moving backwards: This can happen on platform not supporting
6437 monotonic time. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
6440 Changes in version 0.3.2.6-alpha - 2017-12-01
6441 This version of Tor is the latest in the 0.3.2 alpha series. It
6442 includes fixes for several important security issues. All Tor users
6443 should upgrade to this release, or to one of the other releases coming
6446 o Major bugfixes (security):
6447 - Fix a denial of service bug where an attacker could use a
6448 malformed directory object to cause a Tor instance to pause while
6449 OpenSSL would try to read a passphrase from the terminal. (Tor
6450 instances run without a terminal, which is the case for most Tor
6451 packages, are not impacted.) Fixes bug 24246; bugfix on every
6452 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6453 Found by OSS-Fuzz as testcase 6360145429790720.
6454 - Fix a denial of service issue where an attacker could crash a
6455 directory authority using a malformed router descriptor. Fixes bug
6456 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6458 - When checking for replays in the INTRODUCE1 cell data for a
6459 (legacy) onion service, correctly detect replays in the RSA-
6460 encrypted part of the cell. We were previously checking for
6461 replays on the entire cell, but those can be circumvented due to
6462 the malleability of Tor's legacy hybrid encryption. This fix helps
6463 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6464 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6467 o Major bugfixes (security, onion service v2):
6468 - Fix a use-after-free error that could crash v2 Tor onion services
6469 when they failed to open circuits while expiring introduction
6470 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6471 also tracked as TROVE-2017-013 and CVE-2017-8823.
6473 o Major bugfixes (security, relay):
6474 - When running as a relay, make sure that we never build a path
6475 through ourselves, even in the case where we have somehow lost the
6476 version of our descriptor appearing in the consensus. Fixes part
6477 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6478 as TROVE-2017-012 and CVE-2017-8822.
6479 - When running as a relay, make sure that we never choose ourselves
6480 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6481 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6483 o Minor feature (relay statistics):
6484 - Change relay bandwidth reporting stats interval from 4 hours to 24
6485 hours in order to reduce the efficiency of guard discovery
6486 attacks. Fixes ticket 23856.
6488 o Minor features (directory authority):
6489 - Add an IPv6 address for the "bastet" directory authority. Closes
6492 o Minor bugfixes (client):
6493 - By default, do not enable storage of client-side DNS values. These
6494 values were unused by default previously, but they should not have
6495 been cached at all. Fixes bug 24050; bugfix on 0.2.6.3-alpha.
6498 Changes in version 0.3.1.9 - 2017-12-01:
6499 Tor 0.3.1.9 backports important security and stability fixes from the
6500 0.3.2 development series. All Tor users should upgrade to this
6501 release, or to another of the releases coming out today.
6503 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6504 - Fix a denial of service bug where an attacker could use a
6505 malformed directory object to cause a Tor instance to pause while
6506 OpenSSL would try to read a passphrase from the terminal. (Tor
6507 instances run without a terminal, which is the case for most Tor
6508 packages, are not impacted.) Fixes bug 24246; bugfix on every
6509 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6510 Found by OSS-Fuzz as testcase 6360145429790720.
6511 - Fix a denial of service issue where an attacker could crash a
6512 directory authority using a malformed router descriptor. Fixes bug
6513 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6515 - When checking for replays in the INTRODUCE1 cell data for a
6516 (legacy) onion service, correctly detect replays in the RSA-
6517 encrypted part of the cell. We were previously checking for
6518 replays on the entire cell, but those can be circumvented due to
6519 the malleability of Tor's legacy hybrid encryption. This fix helps
6520 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6521 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6524 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6525 - Fix a use-after-free error that could crash v2 Tor onion services
6526 when they failed to open circuits while expiring introduction
6527 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6528 also tracked as TROVE-2017-013 and CVE-2017-8823.
6530 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6531 - When running as a relay, make sure that we never build a path
6532 through ourselves, even in the case where we have somehow lost the
6533 version of our descriptor appearing in the consensus. Fixes part
6534 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6535 as TROVE-2017-012 and CVE-2017-8822.
6536 - When running as a relay, make sure that we never choose ourselves
6537 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6538 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6540 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6541 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6542 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6543 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6544 identifying and finding a workaround to this bug and to Moritz,
6545 Arthur Edelstein, and Roger for helping to track it down and
6548 o Minor features (bridge):
6549 - Bridges now include notice in their descriptors that they are
6550 bridges, and notice of their distribution status, based on their
6551 publication settings. Implements ticket 18329. For more fine-
6552 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6555 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6556 - Add an IPv6 address for the "bastet" directory authority. Closes
6559 o Minor features (geoip):
6560 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6563 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6564 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6565 relays, to prevent spurious address resolutions and descriptor
6566 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6567 bugfix on in 0.2.8.1-alpha.
6569 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6570 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6571 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6573 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6574 - When a circuit is marked for close, do not attempt to package any
6575 cells for channels on that circuit. Previously, we would detect
6576 this condition lower in the call stack, when we noticed that the
6577 circuit had no attached channel, and log an annoying message.
6578 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6580 o Minor bugfixes (onion service, backport from 0.3.2.5-alpha):
6581 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6582 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6585 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6586 - Avoid a crash when transitioning from client mode to bridge mode.
6587 Previously, we would launch the worker threads whenever our
6588 "public server" mode changed, but not when our "server" mode
6589 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6592 Changes in version 0.3.0.13 - 2017-12-01
6593 Tor 0.3.0.13 backports important security and stability bugfixes from
6594 later Tor releases. All Tor users should upgrade to this release, or
6595 to another of the releases coming out today.
6597 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
6598 2018. If you need a release with long-term support, please stick with
6599 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6601 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6602 - Fix a denial of service bug where an attacker could use a
6603 malformed directory object to cause a Tor instance to pause while
6604 OpenSSL would try to read a passphrase from the terminal. (Tor
6605 instances run without a terminal, which is the case for most Tor
6606 packages, are not impacted.) Fixes bug 24246; bugfix on every
6607 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6608 Found by OSS-Fuzz as testcase 6360145429790720.
6609 - Fix a denial of service issue where an attacker could crash a
6610 directory authority using a malformed router descriptor. Fixes bug
6611 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6613 - When checking for replays in the INTRODUCE1 cell data for a
6614 (legacy) onion service, correctly detect replays in the RSA-
6615 encrypted part of the cell. We were previously checking for
6616 replays on the entire cell, but those can be circumvented due to
6617 the malleability of Tor's legacy hybrid encryption. This fix helps
6618 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6619 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6622 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6623 - Fix a use-after-free error that could crash v2 Tor onion services
6624 when they failed to open circuits while expiring introduction
6625 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6626 also tracked as TROVE-2017-013 and CVE-2017-8823.
6628 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6629 - When running as a relay, make sure that we never build a path
6630 through ourselves, even in the case where we have somehow lost the
6631 version of our descriptor appearing in the consensus. Fixes part
6632 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6633 as TROVE-2017-012 and CVE-2017-8822.
6634 - When running as a relay, make sure that we never choose ourselves
6635 as a guard. Fixes part of bug 21534; bugfix on 0.3.0.1-alpha. This
6636 issue is also tracked as TROVE-2017-012 and CVE-2017-8822.
6638 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6639 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6640 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6641 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6642 identifying and finding a workaround to this bug and to Moritz,
6643 Arthur Edelstein, and Roger for helping to track it down and
6646 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6647 - Enable a couple of pieces of Windows hardening: one
6648 (HeapEnableTerminationOnCorruption) that has been on-by-default
6649 since Windows 8, and unavailable before Windows 7; and one
6650 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6651 affect us, but shouldn't do any harm. Closes ticket 21953.
6653 o Minor features (bridge, backport from 0.3.1.9):
6654 - Bridges now include notice in their descriptors that they are
6655 bridges, and notice of their distribution status, based on their
6656 publication settings. Implements ticket 18329. For more fine-
6657 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6660 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6661 - Add an IPv6 address for the "bastet" directory authority. Closes
6664 o Minor features (geoip):
6665 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6668 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6669 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6670 relays, to prevent spurious address resolutions and descriptor
6671 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6672 bugfix on in 0.2.8.1-alpha.
6674 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6675 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6676 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6678 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6679 - When a circuit is marked for close, do not attempt to package any
6680 cells for channels on that circuit. Previously, we would detect
6681 this condition lower in the call stack, when we noticed that the
6682 circuit had no attached channel, and log an annoying message.
6683 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6685 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6686 - Avoid a crash when transitioning from client mode to bridge mode.
6687 Previously, we would launch the worker threads whenever our
6688 "public server" mode changed, but not when our "server" mode
6689 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6691 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6692 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6693 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6696 Changes in version 0.2.9.14 - 2017-12-01
6697 Tor 0.3.0.13 backports important security and stability bugfixes from
6698 later Tor releases. All Tor users should upgrade to this release, or
6699 to another of the releases coming out today.
6701 o Major bugfixes (exit relays, DNS, backport from 0.3.2.4-alpha):
6702 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
6703 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
6704 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
6705 identifying and finding a workaround to this bug and to Moritz,
6706 Arthur Edelstein, and Roger for helping to track it down and
6709 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6710 - Fix a denial of service bug where an attacker could use a
6711 malformed directory object to cause a Tor instance to pause while
6712 OpenSSL would try to read a passphrase from the terminal. (Tor
6713 instances run without a terminal, which is the case for most Tor
6714 packages, are not impacted.) Fixes bug 24246; bugfix on every
6715 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6716 Found by OSS-Fuzz as testcase 6360145429790720.
6717 - Fix a denial of service issue where an attacker could crash a
6718 directory authority using a malformed router descriptor. Fixes bug
6719 24245; bugfix on 0.2.9.4-alpha. Also tracked as TROVE-2017-010
6721 - When checking for replays in the INTRODUCE1 cell data for a
6722 (legacy) onion service, correctly detect replays in the RSA-
6723 encrypted part of the cell. We were previously checking for
6724 replays on the entire cell, but those can be circumvented due to
6725 the malleability of Tor's legacy hybrid encryption. This fix helps
6726 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6727 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6730 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6731 - Fix a use-after-free error that could crash v2 Tor onion services
6732 when they failed to open circuits while expiring introduction
6733 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6734 also tracked as TROVE-2017-013 and CVE-2017-8823.
6736 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6737 - When running as a relay, make sure that we never build a path
6738 through ourselves, even in the case where we have somehow lost the
6739 version of our descriptor appearing in the consensus. Fixes part
6740 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6741 as TROVE-2017-012 and CVE-2017-8822.
6743 o Minor features (bridge, backport from 0.3.1.9):
6744 - Bridges now include notice in their descriptors that they are
6745 bridges, and notice of their distribution status, based on their
6746 publication settings. Implements ticket 18329. For more fine-
6747 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6750 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6751 - Add an IPv6 address for the "bastet" directory authority. Closes
6754 o Minor features (geoip):
6755 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6758 o Minor features (security, windows, backport from 0.3.1.1-alpha):
6759 - Enable a couple of pieces of Windows hardening: one
6760 (HeapEnableTerminationOnCorruption) that has been on-by-default
6761 since Windows 8, and unavailable before Windows 7; and one
6762 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
6763 affect us, but shouldn't do any harm. Closes ticket 21953.
6765 o Minor bugfix (relay address resolution, backport from 0.3.2.1-alpha):
6766 - Avoid unnecessary calls to directory_fetches_from_authorities() on
6767 relays, to prevent spurious address resolutions and descriptor
6768 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
6769 bugfix on in 0.2.8.1-alpha.
6771 o Minor bugfixes (compilation, backport from 0.3.2.1-alpha):
6772 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
6773 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
6775 o Minor bugfixes (logging, relay shutdown, annoyance, backport from 0.3.2.2-alpha):
6776 - When a circuit is marked for close, do not attempt to package any
6777 cells for channels on that circuit. Previously, we would detect
6778 this condition lower in the call stack, when we noticed that the
6779 circuit had no attached channel, and log an annoying message.
6780 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
6782 o Minor bugfixes (relay, crash, backport from 0.3.2.4-alpha):
6783 - Avoid a crash when transitioning from client mode to bridge mode.
6784 Previously, we would launch the worker threads whenever our
6785 "public server" mode changed, but not when our "server" mode
6786 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
6788 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6789 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6790 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6793 Changes in version 0.2.8.17 - 2017-12-01
6794 Tor 0.2.8.17 backports important security and stability bugfixes from
6795 later Tor releases. All Tor users should upgrade to this release, or
6796 to another of the releases coming out today.
6798 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
6799 2018. If you need a release with long-term support, please upgrade with
6800 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6802 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6803 - Fix a denial of service bug where an attacker could use a
6804 malformed directory object to cause a Tor instance to pause while
6805 OpenSSL would try to read a passphrase from the terminal. (Tor
6806 instances run without a terminal, which is the case for most Tor
6807 packages, are not impacted.) Fixes bug 24246; bugfix on every
6808 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6809 Found by OSS-Fuzz as testcase 6360145429790720.
6810 - When checking for replays in the INTRODUCE1 cell data for a
6811 (legacy) onion service, correctly detect replays in the RSA-
6812 encrypted part of the cell. We were previously checking for
6813 replays on the entire cell, but those can be circumvented due to
6814 the malleability of Tor's legacy hybrid encryption. This fix helps
6815 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6816 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6819 o Major bugfixes (security, onion service v2, backport from 0.3.2.6-alpha):
6820 - Fix a use-after-free error that could crash v2 Tor onion services
6821 when they failed to open circuits while expiring introduction
6822 points. Fixes bug 24313; bugfix on 0.2.7.2-alpha. This issue is
6823 also tracked as TROVE-2017-013 and CVE-2017-8823.
6825 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6826 - When running as a relay, make sure that we never build a path through
6827 ourselves, even in the case where we have somehow lost the version of
6828 our descriptor appearing in the consensus. Fixes part of bug 21534;
6829 bugfix on 0.2.0.1-alpha. This issue is also tracked as TROVE-2017-012
6832 o Minor features (bridge, backport from 0.3.1.9):
6833 - Bridges now include notice in their descriptors that they are
6834 bridges, and notice of their distribution status, based on their
6835 publication settings. Implements ticket 18329. For more fine-
6836 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6839 o Minor features (directory authority, backport from 0.3.2.6-alpha):
6840 - Add an IPv6 address for the "bastet" directory authority. Closes
6843 o Minor features (geoip):
6844 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6847 o Minor bugfixes (testing, backport from 0.3.1.6-rc):
6848 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
6849 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
6852 Changes in version 0.2.5.16 - 2017-12-01
6853 Tor 0.2.5.13 backports important security and stability bugfixes from
6854 later Tor releases. All Tor users should upgrade to this release, or
6855 to another of the releases coming out today.
6857 Note: the Tor 0.2.5 series will no longer be supported after 1 May
6858 2018. If you need a release with long-term support, please upgrade to
6859 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
6861 o Major bugfixes (security, backport from 0.3.2.6-alpha):
6862 - Fix a denial of service bug where an attacker could use a
6863 malformed directory object to cause a Tor instance to pause while
6864 OpenSSL would try to read a passphrase from the terminal. (Tor
6865 instances run without a terminal, which is the case for most Tor
6866 packages, are not impacted.) Fixes bug 24246; bugfix on every
6867 version of Tor. Also tracked as TROVE-2017-011 and CVE-2017-8821.
6868 Found by OSS-Fuzz as testcase 6360145429790720.
6869 - When checking for replays in the INTRODUCE1 cell data for a
6870 (legacy) onion service, correctly detect replays in the RSA-
6871 encrypted part of the cell. We were previously checking for
6872 replays on the entire cell, but those can be circumvented due to
6873 the malleability of Tor's legacy hybrid encryption. This fix helps
6874 prevent a traffic confirmation attack. Fixes bug 24244; bugfix on
6875 0.2.4.1-alpha. This issue is also tracked as TROVE-2017-009
6878 o Major bugfixes (security, relay, backport from 0.3.2.6-alpha):
6879 - When running as a relay, make sure that we never build a path
6880 through ourselves, even in the case where we have somehow lost the
6881 version of our descriptor appearing in the consensus. Fixes part
6882 of bug 21534; bugfix on 0.2.0.1-alpha. This issue is also tracked
6883 as TROVE-2017-012 and CVE-2017-8822.
6885 o Minor features (bridge, backport from 0.3.1.9):
6886 - Bridges now include notice in their descriptors that they are
6887 bridges, and notice of their distribution status, based on their
6888 publication settings. Implements ticket 18329. For more fine-
6889 grained control of how a bridge is distributed, upgrade to 0.3.2.x
6892 o Minor features (geoip):
6893 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6897 Changes in version 0.3.2.5-alpha - 2017-11-22
6898 Tor 0.3.2.5-alpha is the fifth alpha release in the 0.3.2.x series. It
6899 fixes several stability and reliability bugs, including a fix for
6900 intermittent bootstrapping failures that some people have been seeing
6901 since the 0.3.0.x series.
6903 Please test this alpha out -- many of these fixes will soon be
6904 backported to stable Tor versions if no additional bugs are found
6907 o Major bugfixes (bootstrapping):
6908 - Fetch descriptors aggressively whenever we lack enough to build
6909 circuits, regardless of how many descriptors we are missing.
6910 Previously, we would delay launching the fetch when we had fewer
6911 than 15 missing descriptors, even if some of those descriptors
6912 were blocking circuits from building. Fixes bug 23985; bugfix on
6913 0.1.1.11-alpha. The effects of this bug became worse in
6914 0.3.0.3-alpha, when we began treating missing descriptors from our
6915 primary guards as a reason to delay circuits.
6916 - Don't try fetching microdescriptors from relays that have failed
6917 to deliver them in the past. Fixes bug 23817; bugfix
6920 o Minor features (directory authority):
6921 - Make the "Exit" flag assignment only depend on whether the exit
6922 policy allows connections to ports 80 and 443. Previously relays
6923 would get the Exit flag if they allowed connections to one of
6924 these ports and also port 6667. Resolves ticket 23637.
6926 o Minor features (geoip):
6927 - Update geoip and geoip6 to the November 6 2017 Maxmind GeoLite2
6930 o Minor features (linux seccomp2 sandbox):
6931 - Update the sandbox rules so that they should now work correctly
6932 with Glibc 2.26. Closes ticket 24315.
6934 o Minor features (logging):
6935 - Downgrade a pair of log messages that could occur when an exit's
6936 resolver gave us an unusual (but not forbidden) response. Closes
6938 - Improve the message we log when re-enabling circuit build timeouts
6939 after having received a consensus. Closes ticket 20963.
6941 o Minor bugfixes (compilation):
6942 - Fix a memory leak warning in one of the libevent-related
6943 configuration tests that could occur when manually specifying
6944 -fsanitize=address. Fixes bug 24279; bugfix on 0.3.0.2-alpha.
6945 Found and patched by Alex Xu.
6946 - When detecting OpenSSL on Windows from our configure script, make
6947 sure to try linking with the ws2_32 library. Fixes bug 23783;
6948 bugfix on 0.3.2.2-alpha.
6950 o Minor bugfixes (control port, linux seccomp2 sandbox):
6951 - Avoid a crash when attempting to use the seccomp2 sandbox together
6952 with the OwningControllerProcess feature. Fixes bug 24198; bugfix
6955 o Minor bugfixes (control port, onion services):
6956 - Report "FAILED" instead of "UPLOAD_FAILED" "FAILED" for the
6957 HS_DESC event when a service is not able to upload a descriptor.
6958 Fixes bug 24230; bugfix on 0.2.7.1-alpha.
6960 o Minor bugfixes (directory cache):
6961 - Recover better from empty or corrupt files in the consensus cache
6962 directory. Fixes bug 24099; bugfix on 0.3.1.1-alpha.
6963 - When a consensus diff calculation is only partially successful,
6964 only record the successful parts as having succeeded. Partial
6965 success can happen if (for example) one compression method fails
6966 but the others succeed. Previously we misrecorded all the
6967 calculations as having succeeded, which would later cause a
6968 nonfatal assertion failure. Fixes bug 24086; bugfix
6971 o Minor bugfixes (logging):
6972 - Only log once if we notice that KIST support is gone. Fixes bug
6973 24158; bugfix on 0.3.2.1-alpha.
6974 - Suppress a log notice when relay descriptors arrive. We already
6975 have a bootstrap progress for this so no need to log notice
6976 everytime tor receives relay descriptors. Microdescriptors behave
6977 the same. Fixes bug 23861; bugfix on 0.2.8.2-alpha.
6979 o Minor bugfixes (network layer):
6980 - When closing a connection via close_connection_immediately(), we
6981 mark it as "not blocked on bandwidth", to prevent later calls from
6982 trying to unblock it, and give it permission to read. This fixes a
6983 backtrace warning that can happen on relays under various
6984 circumstances. Fixes bug 24167; bugfix on 0.1.0.1-rc.
6986 o Minor bugfixes (onion services):
6987 - The introduction circuit was being timed out too quickly while
6988 waiting for the rendezvous circuit to complete. Keep the intro
6989 circuit around longer instead of timing out and reopening new ones
6990 constantly. Fixes bug 23681; bugfix on 0.2.4.8-alpha.
6991 - Rename the consensus parameter "hsdir-interval" to "hsdir_interval"
6992 so it matches dir-spec.txt. Fixes bug 24262; bugfix
6994 - Silence a warning about failed v3 onion descriptor uploads that
6995 can happen naturally under certain edge cases. Fixes part of bug
6996 23662; bugfix on 0.3.2.1-alpha.
6998 o Minor bugfixes (tests):
6999 - Fix a memory leak in one of the bridge-distribution test cases.
7000 Fixes bug 24345; bugfix on 0.3.2.3-alpha.
7001 - Fix a bug in our fuzzing mock replacement for crypto_pk_checksig(),
7002 to correctly handle cases where a caller gives it an RSA key of
7003 under 160 bits. (This is not actually a bug in Tor itself, but
7004 rather in our fuzzing code.) Fixes bug 24247; bugfix on
7005 0.3.0.3-alpha. Found by OSS-Fuzz as issue 4177.
7008 - Add notes in man page regarding OS support for the various
7009 scheduler types. Attempt to use less jargon in the scheduler
7010 section. Closes ticket 24254.
7013 Changes in version 0.3.2.4-alpha - 2017-11-08
7014 Tor 0.3.2.4-alpha is the fourth alpha release in the 0.3.2.x series.
7015 It fixes several stability and reliability bugs, especially including
7016 a major reliability issue that has been plaguing fast exit relays in
7019 o Major bugfixes (exit relays, DNS):
7020 - Fix an issue causing DNS to fail on high-bandwidth exit nodes,
7021 making them nearly unusable. Fixes bugs 21394 and 18580; bugfix on
7022 0.1.2.2-alpha, which introduced eventdns. Thanks to Dhalgren for
7023 identifying and finding a workaround to this bug and to Moritz,
7024 Arthur Edelstein, and Roger for helping to track it down and
7027 o Major bugfixes (scheduler, channel):
7028 - Stop processing scheduled channels if they closed while flushing
7029 cells. This can happen if the write on the connection fails
7030 leading to the channel being closed while in the scheduler loop.
7031 Fixes bug 23751; bugfix on 0.3.2.1-alpha.
7033 o Minor features (logging, scheduler):
7034 - Introduce a SCHED_BUG() function to log extra information about
7035 the scheduler state if we ever catch a bug in the scheduler.
7036 Closes ticket 23753.
7038 o Minor features (removed deprecations):
7039 - The ClientDNSRejectInternalAddresses flag can once again be set in
7040 non-testing Tor networks, so long as they do not use the default
7041 directory authorities. This change also removes the deprecation of
7042 this flag from 0.2.9.2-alpha. Closes ticket 21031.
7044 o Minor features (testing):
7045 - Our fuzzing tests now test the encrypted portions of v3 onion
7046 service descriptors. Implements more of 21509.
7048 o Minor bugfixes (directory client):
7049 - On failure to download directory information, delay retry attempts
7050 by a random amount based on the "decorrelated jitter" algorithm.
7051 Our previous delay algorithm tended to produce extra-long delays
7052 too easily. Fixes bug 23816; bugfix on 0.2.9.1-alpha.
7054 o Minor bugfixes (IPv6, v3 single onion services):
7055 - Remove buggy code for IPv6-only v3 single onion services, and
7056 reject attempts to configure them. This release supports IPv4,
7057 dual-stack, and IPv6-only v3 onion services; and IPv4 and dual-
7058 stack v3 single onion services. Fixes bug 23820; bugfix
7061 o Minor bugfixes (logging, relay):
7062 - Give only a protocol warning when the ed25519 key is not
7063 consistent between the descriptor and microdescriptor of a relay.
7064 This can happen, for instance, if the relay has been flagged
7065 NoEdConsensus. Fixes bug 24025; bugfix on 0.3.2.1-alpha.
7067 o Minor bugfixes (manpage, onion service):
7068 - Document that the HiddenServiceNumIntroductionPoints option is
7069 0-10 for v2 services and 0-20 for v3 services. Fixes bug 24115;
7070 bugfix on 0.3.2.1-alpha.
7072 o Minor bugfixes (memory leaks):
7073 - Fix a minor memory leak at exit in the KIST scheduler. This bug
7074 should have no user-visible impact. Fixes bug 23774; bugfix
7076 - Fix a memory leak when decrypting a badly formatted v3 onion
7077 service descriptor. Fixes bug 24150; bugfix on 0.3.2.1-alpha.
7078 Found by OSS-Fuzz; this is OSS-Fuzz issue 3994.
7080 o Minor bugfixes (onion services):
7081 - Cache some needed onion service client information instead of
7082 constantly computing it over and over again. Fixes bug 23623;
7083 bugfix on 0.3.2.1-alpha.
7084 - Properly retry HSv3 descriptor fetches when missing required
7085 directory information. Fixes bug 23762; bugfix on 0.3.2.1-alpha.
7087 o Minor bugfixes (path selection):
7088 - When selecting relays by bandwidth, avoid a rounding error that
7089 could sometimes cause load to be imbalanced incorrectly.
7090 Previously, we would always round upwards; now, we round towards
7091 the nearest integer. This had the biggest effect when a relay's
7092 weight adjustments should have given it weight 0, but it got
7093 weight 1 instead. Fixes bug 23318; bugfix on 0.2.4.3-alpha.
7094 - When calculating the fraction of nodes that have descriptors, and
7095 all nodes in the network have zero bandwidths, count the number of
7096 nodes instead. Fixes bug 23318; bugfix on 0.2.4.10-alpha.
7097 - Actually log the total bandwidth in compute_weighted_bandwidths().
7098 Fixes bug 24170; bugfix on 0.2.4.3-alpha.
7100 o Minor bugfixes (relay, crash):
7101 - Avoid a crash when transitioning from client mode to bridge mode.
7102 Previously, we would launch the worker threads whenever our
7103 "public server" mode changed, but not when our "server" mode
7104 changed. Fixes bug 23693; bugfix on 0.2.6.3-alpha.
7106 o Minor bugfixes (testing):
7107 - Fix a spurious fuzzing-only use of an uninitialized value. Found
7108 by Brian Carpenter. Fixes bug 24082; bugfix on 0.3.0.3-alpha.
7109 - Test that IPv6-only clients can use microdescriptors when running
7110 "make test-network-all". Requires chutney master 61c28b9 or later.
7111 Closes ticket 24109.
7114 Changes in version 0.3.2.3-alpha - 2017-10-27
7115 Tor 0.3.2.3-alpha is the third release in the 0.3.2 series. It fixes
7116 numerous small bugs in earlier versions of 0.3.2.x, and adds a new
7117 directory authority, Bastet.
7119 o Directory authority changes:
7120 - Add "Bastet" as a ninth directory authority to the default list.
7121 Closes ticket 23910.
7122 - The directory authority "Longclaw" has changed its IP address.
7123 Closes ticket 23592.
7125 o Minor features (bridge):
7126 - Bridge relays can now set the BridgeDistribution config option to
7127 add a "bridge-distribution-request" line to their bridge
7128 descriptor, which tells BridgeDB how they'd like their bridge
7129 address to be given out. (Note that as of Oct 2017, BridgeDB does
7130 not yet implement this feature.) As a side benefit, this feature
7131 provides a way to distinguish bridge descriptors from non-bridge
7132 descriptors. Implements tickets 18329.
7134 o Minor features (client, entry guards):
7135 - Improve log messages when missing descriptors for primary guards.
7136 Resolves ticket 23670.
7138 o Minor features (geoip):
7139 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7142 o Minor bugfixes (bridge):
7143 - Overwrite the bridge address earlier in the process of retrieving
7144 its descriptor, to make sure we reach it on the configured
7145 address. Fixes bug 20532; bugfix on 0.2.0.10-alpha.
7147 o Minor bugfixes (documentation):
7148 - Document better how to read gcov, and what our gcov postprocessing
7149 scripts do. Fixes bug 23739; bugfix on 0.2.9.1-alpha.
7151 o Minor bugfixes (entry guards):
7152 - Tor now updates its guard state when it reads a consensus
7153 regardless of whether it's missing descriptors. That makes tor use
7154 its primary guards to fetch descriptors in some edge cases where
7155 it would previously have used fallback directories. Fixes bug
7156 23862; bugfix on 0.3.0.1-alpha.
7158 o Minor bugfixes (hidden service client):
7159 - When handling multiple SOCKS request for the same .onion address,
7160 only fetch the service descriptor once.
7161 - When a descriptor fetch fails with a non-recoverable error, close
7162 all pending SOCKS requests for that .onion. Fixes bug 23653;
7163 bugfix on 0.3.2.1-alpha.
7165 o Minor bugfixes (hidden service):
7166 - Always regenerate missing hidden service public key files. Prior
7167 to this, if the public key was deleted from disk, it wouldn't get
7168 recreated. Fixes bug 23748; bugfix on 0.3.2.2-alpha. Patch
7170 - Make sure that we have a usable ed25519 key when the intro point
7171 relay supports ed25519 link authentication. Fixes bug 24002;
7172 bugfix on 0.3.2.1-alpha.
7174 o Minor bugfixes (hidden service, v2):
7175 - When reloading configured hidden services, copy all information
7176 from the old service object. Previously, some data was omitted,
7177 causing delays in descriptor upload, and other bugs. Fixes bug
7178 23790; bugfix on 0.2.1.9-alpha.
7180 o Minor bugfixes (memory safety, defensive programming):
7181 - Clear the target address when node_get_prim_orport() returns
7182 early. Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7184 o Minor bugfixes (relay):
7185 - Avoid a BUG warning when receiving a dubious CREATE cell while an
7186 option transition is in progress. Fixes bug 23952; bugfix
7189 o Minor bugfixes (testing):
7190 - Adjust the GitLab CI configuration to more closely match that of
7191 Travis CI. Fixes bug 23757; bugfix on 0.3.2.2-alpha.
7192 - Prevent scripts/test/coverage from attempting to move gcov output
7193 to the root directory. Fixes bug 23741; bugfix on 0.2.5.1-alpha.
7194 - When running unit tests as root, skip a test that would fail
7195 because it expects a permissions error. This affects some
7196 continuous integration setups. Fixes bug 23758; bugfix
7198 - Stop unconditionally mirroring the tor repository in GitLab CI.
7199 This prevented developers from enabling GitLab CI on master. Fixes
7200 bug 23755; bugfix on 0.3.2.2-alpha.
7201 - Fix the hidden service v3 descriptor decoding fuzzing to use the
7202 latest decoding API correctly. Fixes bug 21509; bugfix
7205 o Minor bugfixes (warnings):
7206 - When we get an HTTP request on a SOCKS port, tell the user about
7207 the new HTTPTunnelPort option. Previously, we would give a "Tor is
7208 not an HTTP Proxy" message, which stopped being true when
7209 HTTPTunnelPort was introduced. Fixes bug 23678; bugfix
7213 Changes in version 0.2.5.15 - 2017-10-25
7214 Tor 0.2.5.15 backports a collection of bugfixes from later Tor release
7215 series. It also adds a new directory authority, Bastet.
7217 Note: the Tor 0.2.5 series will no longer be supported after 1 May
7218 2018. If you need a release with long-term support, please upgrade to
7219 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7221 o Directory authority changes:
7222 - Add "Bastet" as a ninth directory authority to the default list.
7223 Closes ticket 23910.
7224 - The directory authority "Longclaw" has changed its IP address.
7225 Closes ticket 23592.
7227 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7228 - Avoid an assertion failure bug affecting our implementation of
7229 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7230 handling of "0xx" differs from what we had expected. Fixes bug
7231 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7233 o Minor features (geoip):
7234 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7237 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
7238 - Fix a memset() off the end of an array when packing cells. This
7239 bug should be harmless in practice, since the corrupted bytes are
7240 still in the same structure, and are always padding bytes,
7241 ignored, or immediately overwritten, depending on compiler
7242 behavior. Nevertheless, because the memset()'s purpose is to make
7243 sure that any other cell-handling bugs can't expose bytes to the
7244 network, we need to fix it. Fixes bug 22737; bugfix on
7245 0.2.4.11-alpha. Fixes CID 1401591.
7247 o Build features (backport from 0.3.1.5-alpha):
7248 - Tor's repository now includes a Travis Continuous Integration (CI)
7249 configuration file (.travis.yml). This is meant to help new
7250 developers and contributors who fork Tor to a Github repository be
7251 better able to test their changes, and understand what we expect
7252 to pass. To use this new build feature, you must fork Tor to your
7253 Github account, then go into the "Integrations" menu in the
7254 repository settings for your fork and enable Travis, then push
7255 your changes. Closes ticket 22636.
7258 Changes in version 0.2.8.16 - 2017-10-25
7259 Tor 0.2.8.16 backports a collection of bugfixes from later Tor release
7260 series, including a bugfix for a crash issue that had affected relays
7261 under memory pressure. It also adds a new directory authority, Bastet.
7263 Note: the Tor 0.2.8 series will no longer be supported after 1 Jan
7264 2018. If you need a release with long-term support, please stick with
7265 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7267 o Directory authority changes:
7268 - Add "Bastet" as a ninth directory authority to the default list.
7269 Closes ticket 23910.
7270 - The directory authority "Longclaw" has changed its IP address.
7271 Closes ticket 23592.
7273 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7274 - Fix a timing-based assertion failure that could occur when the
7275 circuit out-of-memory handler freed a connection's output buffer.
7276 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7278 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7279 - Remove longclaw's IPv6 address, as it will soon change. Authority
7280 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7281 3/8 directory authorities with IPv6 addresses, but there are also
7282 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7284 o Minor features (geoip):
7285 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7289 Changes in version 0.2.9.13 - 2017-10-25
7290 Tor 0.2.9.13 backports a collection of bugfixes from later Tor release
7291 series, including a bugfix for a crash issue that had affected relays
7292 under memory pressure. It also adds a new directory authority, Bastet.
7294 o Directory authority changes:
7295 - Add "Bastet" as a ninth directory authority to the default list.
7296 Closes ticket 23910.
7297 - The directory authority "Longclaw" has changed its IP address.
7298 Closes ticket 23592.
7300 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7301 - Fix a timing-based assertion failure that could occur when the
7302 circuit out-of-memory handler freed a connection's output buffer.
7303 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7305 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7306 - Remove longclaw's IPv6 address, as it will soon change. Authority
7307 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7308 3/8 directory authorities with IPv6 addresses, but there are also
7309 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7311 o Minor features (geoip):
7312 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7315 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7316 - When a directory authority rejects a descriptor or extrainfo with
7317 a given digest, mark that digest as undownloadable, so that we do
7318 not attempt to download it again over and over. We previously
7319 tried to avoid downloading such descriptors by other means, but we
7320 didn't notice if we accidentally downloaded one anyway. This
7321 behavior became problematic in 0.2.7.2-alpha, when authorities
7322 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7325 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7326 - Clear the address when node_get_prim_orport() returns early.
7327 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7329 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7330 - When running as a Windows service, set the ID of the main thread
7331 correctly. Failure to do so made us fail to send log messages to
7332 the controller in 0.2.1.16-rc, slowed down controller event
7333 delivery in 0.2.7.3-rc and later, and crash with an assertion
7334 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7335 Patch and diagnosis from "Vort".
7338 Changes in version 0.3.0.12 - 2017-10-25
7339 Tor 0.3.0.12 backports a collection of bugfixes from later Tor release
7340 series, including a bugfix for a crash issue that had affected relays
7341 under memory pressure. It also adds a new directory authority, Bastet.
7343 Note: the Tor 0.3.0 series will no longer be supported after 26 Jan
7344 2018. If you need a release with long-term support, please stick with
7345 the 0.2.9 series. Otherwise, please upgrade to 0.3.1 or later.
7347 o Directory authority changes:
7348 - Add "Bastet" as a ninth directory authority to the default list.
7349 Closes ticket 23910.
7350 - The directory authority "Longclaw" has changed its IP address.
7351 Closes ticket 23592.
7353 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7354 - Fix a timing-based assertion failure that could occur when the
7355 circuit out-of-memory handler freed a connection's output buffer.
7356 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7358 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7359 - Remove longclaw's IPv6 address, as it will soon change. Authority
7360 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7361 3/8 directory authorities with IPv6 addresses, but there are also
7362 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7364 o Minor features (geoip):
7365 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7368 o Minor bugfixes (directory authority, backport from 0.3.1.5-alpha):
7369 - When a directory authority rejects a descriptor or extrainfo with
7370 a given digest, mark that digest as undownloadable, so that we do
7371 not attempt to download it again over and over. We previously
7372 tried to avoid downloading such descriptors by other means, but we
7373 didn't notice if we accidentally downloaded one anyway. This
7374 behavior became problematic in 0.2.7.2-alpha, when authorities
7375 began pinning Ed25519 keys. Fixes bug 22349; bugfix
7378 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7379 - Avoid a possible double close of a circuit by the intro point on
7380 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7381 bugfix on 0.3.0.1-alpha.
7383 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7384 - Clear the address when node_get_prim_orport() returns early.
7385 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7387 o Minor bugfixes (Windows service, backport from 0.3.1.6-rc):
7388 - When running as a Windows service, set the ID of the main thread
7389 correctly. Failure to do so made us fail to send log messages to
7390 the controller in 0.2.1.16-rc, slowed down controller event
7391 delivery in 0.2.7.3-rc and later, and crash with an assertion
7392 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
7393 Patch and diagnosis from "Vort".
7396 Changes in version 0.3.1.8 - 2017-10-25
7397 Tor 0.3.1.8 is the second stable release in the 0.3.1 series.
7398 It includes several bugfixes, including a bugfix for a crash issue
7399 that had affected relays under memory pressure. It also adds
7400 a new directory authority, Bastet.
7402 o Directory authority changes:
7403 - Add "Bastet" as a ninth directory authority to the default list.
7404 Closes ticket 23910.
7405 - The directory authority "Longclaw" has changed its IP address.
7406 Closes ticket 23592.
7408 o Major bugfixes (relay, crash, assertion failure, backport from 0.3.2.2-alpha):
7409 - Fix a timing-based assertion failure that could occur when the
7410 circuit out-of-memory handler freed a connection's output buffer.
7411 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7413 o Minor features (directory authorities, backport from 0.3.2.2-alpha):
7414 - Remove longclaw's IPv6 address, as it will soon change. Authority
7415 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7416 3/8 directory authorities with IPv6 addresses, but there are also
7417 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7419 o Minor features (geoip):
7420 - Update geoip and geoip6 to the October 4 2017 Maxmind GeoLite2
7423 o Minor bugfixes (compilation, backport from 0.3.2.2-alpha):
7424 - Fix a compilation warning when building with zstd support on
7425 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7426 and fixed by Andreas Stieger.
7428 o Minor bugfixes (compression, backport from 0.3.2.2-alpha):
7429 - Handle a pathological case when decompressing Zstandard data when
7430 the output buffer size is zero. Fixes bug 23551; bugfix
7433 o Minor bugfixes (directory authority, backport from 0.3.2.1-alpha):
7434 - Remove the length limit on HTTP status lines that authorities can
7435 send in their replies. Fixes bug 23499; bugfix on 0.3.1.6-rc.
7437 o Minor bugfixes (hidden service, relay, backport from 0.3.2.2-alpha):
7438 - Avoid a possible double close of a circuit by the intro point on
7439 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7440 bugfix on 0.3.0.1-alpha.
7442 o Minor bugfixes (memory safety, backport from 0.3.2.3-alpha):
7443 - Clear the address when node_get_prim_orport() returns early.
7444 Fixes bug 23874; bugfix on 0.2.8.2-alpha.
7446 o Minor bugfixes (unit tests, backport from 0.3.2.2-alpha):
7447 - Fix additional channelpadding unit test failures by using mocked
7448 time instead of actual time for all tests. Fixes bug 23608; bugfix
7452 Changes in version 0.3.2.2-alpha - 2017-09-29
7453 Tor 0.3.2.2-alpha is the second release in the 0.3.2 series. This
7454 release fixes several minor bugs in the new scheduler and next-
7455 generation onion services; both features were newly added in the 0.3.2
7456 series. Other fixes in this alpha include several fixes for non-fatal
7457 tracebacks which would appear in logs.
7459 With the aim to stabilise the 0.3.2 series by 15 December 2017, this
7460 alpha does not contain any substantial new features. Minor features
7461 include better testing and logging.
7463 The following comprises the complete list of changes included
7466 o Major bugfixes (relay, crash, assertion failure):
7467 - Fix a timing-based assertion failure that could occur when the
7468 circuit out-of-memory handler freed a connection's output buffer.
7469 Fixes bug 23690; bugfix on 0.2.6.1-alpha.
7471 o Major bugfixes (scheduler):
7472 - If a channel is put into the scheduler's pending list, then it
7473 starts closing, and then if the scheduler runs before it finishes
7474 closing, the scheduler will get stuck trying to flush its cells
7475 while the lower layers refuse to cooperate. Fix that race
7476 condition by giving the scheduler an escape method. Fixes bug
7477 23676; bugfix on 0.3.2.1-alpha.
7479 o Minor features (build, compilation):
7480 - The "check-changes" feature is now part of the "make check" tests;
7481 we'll use it to try to prevent misformed changes files from
7482 accumulating. Closes ticket 23564.
7483 - Tor builds should now fail if there are any mismatches between the
7484 C type representing a configuration variable and the C type the
7485 data-driven parser uses to store a value there. Previously, we
7486 needed to check these by hand, which sometimes led to mistakes.
7487 Closes ticket 23643.
7489 o Minor features (directory authorities):
7490 - Remove longclaw's IPv6 address, as it will soon change. Authority
7491 IPv6 addresses were originally added in 0.2.8.1-alpha. This leaves
7492 3/8 directory authorities with IPv6 addresses, but there are also
7493 52 fallback directory mirrors with IPv6 addresses. Resolves 19760.
7495 o Minor features (hidden service, circuit, logging):
7496 - Improve logging of many callsite in the circuit subsystem to print
7497 the circuit identifier(s).
7498 - Log when we cleanup an intro point from a service so we know when
7499 and for what reason it happened. Closes ticket 23604.
7501 o Minor features (logging):
7502 - Log more circuit information whenever we are about to try to
7503 package a relay cell on a circuit with a nonexistent n_chan.
7504 Attempt to diagnose ticket 8185.
7505 - Improve info-level log identification of particular circuits, to
7506 help with debugging. Closes ticket 23645.
7508 o Minor features (relay):
7509 - When choosing which circuits can be expired as unused, consider
7510 circuits from clients even if those clients used regular CREATE
7511 cells to make them; and do not consider circuits from relays even
7512 if they were made with CREATE_FAST. Part of ticket 22805.
7514 o Minor features (robustness):
7515 - Change several fatal assertions when flushing buffers into non-
7516 fatal assertions, to prevent any recurrence of 23690.
7518 o Minor features (spec conformance, bridge, diagnostic):
7519 - When handling the USERADDR command on an ExtOrPort, warn when the
7520 transports provides a USERADDR with no port. In a future version,
7521 USERADDR commands of this format may be rejected. Detects problems
7522 related to ticket 23080.
7524 o Minor features (testing):
7525 - Add a unit test to make sure that our own generated platform
7526 string will be accepted by directory authorities. Closes
7529 o Minor bugfixes (bootstrapping):
7530 - When warning about state file clock skew, report the correct
7531 direction for the detected skew. Fixes bug 23606; bugfix
7533 - Avoid an assertion failure when logging a state file clock skew
7534 very early in bootstrapping. Fixes bug 23607; bugfix
7537 o Minor bugfixes (build, compilation):
7538 - Fix a compilation warning when building with zstd support on
7539 32-bit platforms. Fixes bug 23568; bugfix on 0.3.1.1-alpha. Found
7540 and fixed by Andreas Stieger.
7541 - When searching for OpenSSL, don't accept any OpenSSL library that
7542 lacks TLSv1_1_method(): Tor doesn't build with those versions.
7543 Additionally, look in /usr/local/opt/openssl, if it's present.
7544 These changes together repair the default build on OSX systems
7545 with Homebrew installed. Fixes bug 23602; bugfix on 0.2.7.2-alpha.
7547 o Minor bugfixes (compression):
7548 - Handle a pathological case when decompressing Zstandard data when
7549 the output buffer size is zero. Fixes bug 23551; bugfix
7552 o Minor bugfixes (documentation):
7553 - Fix manpage to not refer to the obsolete (and misspelled)
7554 UseEntryGuardsAsDirectoryGuards parameter in the description of
7555 NumDirectoryGuards. Fixes bug 23611; bugfix on 0.2.4.8-alpha.
7557 o Minor bugfixes (hidden service v3):
7558 - Don't log an assertion failure when we can't find the right
7559 information to extend to an introduction point. In rare cases,
7560 this could happen, causing a warning, even though tor would
7561 recover gracefully. Fixes bug 23159; bugfix on 0.3.2.1-alpha.
7562 - Pad RENDEZVOUS cell up to the size of the legacy cell which is
7563 much bigger so the rendezvous point can't distinguish which hidden
7564 service protocol is being used. Fixes bug 23420; bugfix
7567 o Minor bugfixes (hidden service, relay):
7568 - Avoid a possible double close of a circuit by the intro point on
7569 error of sending the INTRO_ESTABLISHED cell. Fixes bug 23610;
7570 bugfix on 0.3.0.1-alpha.
7572 o Minor bugfixes (logging, relay shutdown, annoyance):
7573 - When a circuit is marked for close, do not attempt to package any
7574 cells for channels on that circuit. Previously, we would detect
7575 this condition lower in the call stack, when we noticed that the
7576 circuit had no attached channel, and log an annoying message.
7577 Fixes bug 8185; bugfix on 0.2.5.4-alpha.
7579 o Minor bugfixes (scheduler):
7580 - When switching schedulers due to a consensus change, we didn't
7581 give the new scheduler a chance to react to the consensus. Fix
7582 that. Fixes bug 23537; bugfix on 0.3.2.1-alpha.
7583 - Make the KISTSchedRunInterval option a non negative value. With
7584 this, the way to disable KIST through the consensus is to set it
7585 to 0. Fixes bug 23539; bugfix on 0.3.2.1-alpha.
7586 - Only notice log the selected scheduler when we switch scheduler
7587 types. Fixes bug 23552; bugfix on 0.3.2.1-alpha.
7588 - Avoid a compilation warning on macOS in scheduler_ev_add() caused
7589 by a different tv_usec data type. Fixes bug 23575; bugfix
7591 - Make a hard exit if tor is unable to pick a scheduler which can
7592 happen if the user specifies a scheduler type that is not
7593 supported and not other types in Schedulers. Fixes bug 23581;
7594 bugfix on 0.3.2.1-alpha.
7595 - Properly initialize the scheduler last run time counter so it is
7596 not 0 at the first tick. Fixes bug 23696; bugfix on 0.3.2.1-alpha.
7598 o Minor bugfixes (testing):
7599 - Capture and detect several "Result does not fit" warnings in unit
7600 tests on platforms with 32-bit time_t. Fixes bug 21800; bugfix
7602 - Fix additional channelpadding unit test failures by using mocked
7603 time instead of actual time for all tests. Fixes bug 23608; bugfix
7605 - The removal of some old scheduler options caused some tests to
7606 fail on BSD systems. Assume current behavior is correct and make
7607 the tests pass again. Fixes bug 23566; bugfix on 0.3.2.1-alpha.
7609 o Code simplification and refactoring:
7610 - Remove various ways of testing circuits and connections for
7611 "clientness"; instead, favor channel_is_client(). Part of
7614 o Deprecated features:
7615 - The ReachableDirAddresses and ClientPreferIPv6DirPort options are
7616 now deprecated; they do not apply to relays, and they have had no
7617 effect on clients since 0.2.8.x. Closes ticket 19704.
7620 - HiddenServiceVersion man page entry wasn't mentioning the now
7621 supported version 3. Fixes ticket 23580; bugfix on 0.3.2.1-alpha.
7622 - Clarify that the Address option is entirely about setting an
7623 advertised IPv4 address. Closes ticket 18891.
7624 - Clarify the manpage's use of the term "address" to clarify what
7625 kind of address is intended. Closes ticket 21405.
7626 - Document that onion service subdomains are allowed, and ignored.
7627 Closes ticket 18736.
7630 Changes in version 0.3.2.1-alpha - 2017-09-18
7631 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
7632 includes support for our next-generation ("v3") onion service
7633 protocol, and adds a new circuit scheduler for more responsive
7634 forwarding decisions from relays. There are also numerous other small
7635 features and bugfixes here.
7637 Below are the changes since Tor 0.3.1.7.
7639 o Major feature (scheduler, channel):
7640 - Tor now uses new schedulers to decide which circuits should
7641 deliver cells first, in order to improve congestion at relays. The
7642 first type is called "KIST" ("Kernel Informed Socket Transport"),
7643 and is only available on Linux-like systems: it uses feedback from
7644 the kernel to prevent the kernel's TCP buffers from growing too
7645 full. The second new scheduler type is called "KISTLite": it
7646 behaves the same as KIST, but runs on systems without kernel
7647 support for inspecting TCP implementation details. The old
7648 scheduler is still available, under the name "Vanilla". To change
7649 the default scheduler preference order, use the new "Schedulers"
7650 option. (The default preference order is "KIST,KISTLite,Vanilla".)
7652 Matt Traudt implemented KIST, based on research by Rob Jansen,
7653 John Geddes, Christ Wacek, Micah Sherr, and Paul Syverson. For
7654 more information, see the design paper at
7655 http://www.robgjansen.com/publications/kist-sec2014.pdf and the
7656 followup implementation paper at https://arxiv.org/abs/1709.01044.
7657 Closes ticket 12541.
7659 o Major features (next-generation onion services):
7660 - Tor now supports the next-generation onion services protocol for
7661 clients and services! As part of this release, the core of
7662 proposal 224 has been implemented and is available for
7663 experimentation and testing by our users. This newer version of
7664 onion services ("v3") features many improvements over the legacy
7667 a) Better crypto (replaced SHA1/DH/RSA1024
7668 with SHA3/ed25519/curve25519)
7670 b) Improved directory protocol, leaking much less information to
7673 c) Improved directory protocol, with smaller surface for
7676 d) Better onion address security against impersonation.
7678 e) More extensible introduction/rendezvous protocol.
7680 f) A cleaner and more modular codebase.
7682 You can identify a next-generation onion address by its length:
7683 they are 56 characters long, as in
7684 "4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion".
7686 In the future, we will release more options and features for v3
7687 onion services, but we first need a testing period, so that the
7688 current codebase matures and becomes more robust. Planned features
7689 include: offline keys, advanced client authorization, improved
7690 guard algorithms, and statistics. For full details, see
7693 Legacy ("v2") onion services will still work for the foreseeable
7694 future, and will remain the default until this new codebase gets
7695 tested and hardened. Service operators who want to experiment with
7696 the new system can use the 'HiddenServiceVersion 3' torrc
7697 directive along with the regular onion service configuration
7698 options. We will publish a blog post about this new feature
7701 o Major bugfixes (usability, control port):
7702 - Report trusted clock skew indications as bootstrap errors, so
7703 controllers can more easily alert users when their clocks are
7704 wrong. Fixes bug 23506; bugfix on 0.1.2.6-alpha.
7706 o Minor features (bug detection):
7707 - Log a warning message with a stack trace for any attempt to call
7708 get_options() during option validation. This pattern has caused
7709 subtle bugs in the past. Closes ticket 22281.
7711 o Minor features (client):
7712 - You can now use Tor as a tunneled HTTP proxy: use the new
7713 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
7714 requests. Closes ticket 22407.
7715 - Add an extra check to make sure that we always use the newer guard
7716 selection code for picking our guards. Closes ticket 22779.
7717 - When downloading (micro)descriptors, don't split the list into
7718 multiple requests unless we want at least 32 descriptors.
7719 Previously, we split at 4, not 32, which led to significant
7720 overhead in HTTP request size and degradation in compression
7721 performance. Closes ticket 23220.
7723 o Minor features (command line):
7724 - Add a new commandline option, --key-expiration, which prints when
7725 the current signing key is going to expire. Implements ticket
7726 17639; patch by Isis Lovecruft.
7728 o Minor features (control port):
7729 - If an application tries to use the control port as an HTTP proxy,
7730 respond with a meaningful "This is the Tor control port" message,
7731 and log the event. Closes ticket 1667. Patch from Ravi
7733 - Provide better error message for GETINFO desc/(id|name) when not
7734 fetching router descriptors. Closes ticket 5847. Patch by
7736 - Add GETINFO "{desc,md}/download-enabled", to inform the controller
7737 whether Tor will try to download router descriptors and
7738 microdescriptors respectively. Closes ticket 22684.
7739 - Added new GETINFO targets "ip-to-country/{ipv4,ipv6}-available",
7740 so controllers can tell whether the geoip databases are loaded.
7741 Closes ticket 23237.
7742 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
7743 events. Closes ticket 19254. Patch by "DonnchaC".
7745 o Minor features (development support):
7746 - Developers can now generate a call-graph for Tor using the
7747 "calltool" python program, which post-processes object dumps. It
7748 should work okay on many Linux and OSX platforms, and might work
7749 elsewhere too. To run it, install calltool from
7750 https://gitweb.torproject.org/user/nickm/calltool.git and run
7751 "make callgraph". Closes ticket 19307.
7753 o Minor features (ed25519):
7754 - Add validation function to checks for torsion components in
7755 ed25519 public keys, used by prop224 client-side code. Closes
7756 ticket 22006. Math help by Ian Goldberg.
7758 o Minor features (exit relay, DNS):
7759 - Improve the clarity and safety of the log message from evdns when
7760 receiving an apparently spoofed DNS reply. Closes ticket 3056.
7762 o Minor features (integration, hardening):
7763 - Add a new NoExec option to prevent Tor from running other
7764 programs. When this option is set to 1, Tor will never try to run
7765 another program, regardless of the settings of
7766 PortForwardingHelper, ClientTransportPlugin, or
7767 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
7768 without restarting Tor. Closes ticket 22976.
7770 o Minor features (logging):
7771 - Improve the warning message for specifying a relay by nickname.
7772 The previous message implied that nickname registration was still
7773 part of the Tor network design, which it isn't. Closes
7775 - If the sandbox filter fails to load, suggest to the user that
7776 their kernel might not support seccomp2. Closes ticket 23090.
7778 o Minor features (portability):
7779 - Check at configure time whether uint8_t is the same type as
7780 unsigned char. Lots of existing code already makes this
7781 assumption, and there could be strict aliasing issues if the
7782 assumption is violated. Closes ticket 22410.
7784 o Minor features (relay, configuration):
7785 - Reject attempts to use relative file paths when RunAsDaemon is
7786 set. Previously, Tor would accept these, but the directory-
7787 changing step of RunAsDaemon would give strange and/or confusing
7788 results. Closes ticket 22731.
7790 o Minor features (startup, safety):
7791 - When configured to write a PID file, Tor now exits if it is unable
7792 to do so. Previously, it would warn and continue. Closes
7795 o Minor features (static analysis):
7796 - The BUG() macro has been changed slightly so that Coverity no
7797 longer complains about dead code if the bug is impossible. Closes
7800 o Minor features (testing):
7801 - The default chutney network tests now include tests for the v3
7802 hidden service design. Make sure you have the latest version of
7803 chutney if you want to run these. Closes ticket 22437.
7804 - Add a unit test to verify that we can parse a hardcoded v2 hidden
7805 service descriptor. Closes ticket 15554.
7807 o Minor bugfixes (certificate handling):
7808 - Fix a time handling bug in Tor certificates set to expire after
7809 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
7810 Coverity as CID 1415728.
7812 o Minor bugfixes (client, usability):
7813 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
7814 SOCKS4a requests that contain IP address strings, even when
7815 SafeSocks in enabled, as this prevents user from connecting to
7816 known IP addresses without relying on DNS for resolving. SafeSocks
7817 still rejects SOCKS connections that connect to IP addresses when
7818 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
7819 bugfix on Tor 0.2.6.2-alpha.
7821 o Minor bugfixes (code correctness):
7822 - Call htons() in extend_cell_format() for encoding a 16-bit value.
7823 Previously we used ntohs(), which happens to behave the same on
7824 all the platforms we support, but which isn't really correct.
7825 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
7826 - For defense-in-depth, make the controller's write_escaped_data()
7827 function robust to extremely long inputs. Fixes bug 19281; bugfix
7828 on 0.1.1.1-alpha. Reported by Guido Vranken.
7830 o Minor bugfixes (compilation):
7831 - Fix unused-variable warnings in donna's Curve25519 SSE2 code.
7832 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
7834 o Minor bugfixes (consensus expiry):
7835 - Check for adequate directory information correctly. Previously, Tor
7836 would reconsider whether it had sufficient directory information
7837 every 2 minutes. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
7839 o Minor bugfixes (directory protocol):
7840 - Directory servers now include a "Date:" http header for response
7841 codes other than 200. Clients starting with a skewed clock and a
7842 recent consensus were getting "304 Not modified" responses from
7843 directory authorities, so without the Date header, the client
7844 would never hear about a wrong clock. Fixes bug 23499; bugfix
7846 - Make clients wait for 6 seconds before trying to download a
7847 consensus from an authority. Fixes bug 17750; bugfix
7850 o Minor bugfixes (DoS-resistance):
7851 - If future code asks if there are any running bridges, without
7852 checking if bridges are enabled, log a BUG warning rather than
7853 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
7855 o Minor bugfixes (format strictness):
7856 - Restrict several data formats to decimal. Previously, the
7857 BuildTimeHistogram entries in the state file, the "bw=" entries in
7858 the bandwidth authority file, and the process IDs passed to the
7859 __OwningControllerProcess option could all be specified in hex or
7860 octal as well as in decimal. This was not an intentional feature.
7861 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
7864 o Minor bugfixes (heartbeat):
7865 - If we fail to write a heartbeat message, schedule a retry for the
7866 minimum heartbeat interval number of seconds in the future. Fixes
7867 bug 19476; bugfix on 0.2.3.1-alpha.
7869 o Minor bugfixes (linux seccomp2 sandbox, logging):
7870 - Fix some messages on unexpected errors from the seccomp2 library.
7871 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
7873 o Minor bugfixes (logging):
7874 - Remove duplicate log messages regarding opening non-local
7875 SocksPorts upon parsing config and opening listeners at startup.
7876 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
7877 - Use a more comprehensible log message when telling the user
7878 they've excluded every running exit node. Fixes bug 7890; bugfix
7880 - When logging the number of descriptors we intend to download per
7881 directory request, do not log a number higher than then the number
7882 of descriptors we're fetching in total. Fixes bug 19648; bugfix
7884 - When warning about a directory owned by the wrong user, log the
7885 actual name of the user owning the directory. Previously, we'd log
7886 the name of the process owner twice. Fixes bug 23487; bugfix
7888 - The tor specification says hop counts are 1-based, so fix two log
7889 messages that mistakenly logged 0-based hop counts. Fixes bug
7890 18982; bugfix on 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor.
7891 Credit to Xiaofan Li for reporting this issue.
7893 o Minor bugfixes (portability):
7894 - Stop using the PATH_MAX variable, which is not defined on GNU
7895 Hurd. Fixes bug 23098; bugfix on 0.3.1.1-alpha.
7897 o Minor bugfixes (relay):
7898 - When uploading our descriptor for the first time after startup,
7899 report the reason for uploading as "Tor just started" rather than
7900 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
7901 - Avoid unnecessary calls to directory_fetches_from_authorities() on
7902 relays, to prevent spurious address resolutions and descriptor
7903 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
7904 bugfix on in 0.2.8.1-alpha.
7906 o Minor bugfixes (tests):
7907 - Fix a broken unit test for the OutboundAddress option: the parsing
7908 function was never returning an error on failure. Fixes bug 23366;
7909 bugfix on 0.3.0.3-alpha.
7910 - Fix a signed-integer overflow in the unit tests for
7911 dir/download_status_random_backoff, which was untriggered until we
7912 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
7914 o Minor bugfixes (usability, control port):
7915 - Stop making an unnecessary routerlist check in NETINFO clock skew
7916 detection; this was preventing clients from reporting NETINFO clock
7917 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
7919 o Code simplification and refactoring:
7920 - Extract the code for handling newly-open channels into a separate
7921 function from the general code to handle channel state
7922 transitions. This change simplifies our callgraph, reducing the
7923 size of the largest strongly connected component by roughly a
7924 factor of two. Closes ticket 22608.
7925 - Remove dead code for largely unused statistics on the number of
7926 times we've attempted various public key operations. Fixes bug
7927 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
7928 - Remove several now-obsolete functions for asking about old
7929 variants directory authority status. Closes ticket 22311; patch
7931 - Remove some of the code that once supported "Named" and "Unnamed"
7932 routers. Authorities no longer vote for these flags. Closes
7934 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
7935 and old hidden services, to indicate that they aren't suitable for
7936 new protocols or formats. Closes ticket 23026.
7937 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
7938 22521. Patch from Neel Chauhan.
7939 - Split the enormous circuit_send_next_onion_skin() function into
7940 multiple subfunctions. Closes ticket 22804.
7941 - Split the portions of the buffer.c module that handle particular
7942 protocols into separate modules. Part of ticket 23149.
7943 - Use our test macros more consistently, to produce more useful
7944 error messages when our unit tests fail. Add coccinelle patches to
7945 allow us to re-check for test macro uses. Closes ticket 22497.
7947 o Deprecated features:
7948 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
7949 only applies to direct unencrypted HTTP connections to your
7950 directory server, which your Tor probably isn't using. Closes
7954 - Clarify in the manual that "Sandbox 1" is only supported on Linux
7955 kernels. Closes ticket 22677.
7956 - Document all values of PublishServerDescriptor in the manpage.
7957 Closes ticket 15645.
7958 - Improve the documentation for the directory port part of the
7959 DirAuthority line. Closes ticket 20152.
7960 - Restore documentation for the authorities' "approved-routers"
7961 file. Closes ticket 21148.
7964 - The AllowDotExit option has been removed as unsafe. It has been
7965 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
7966 - The ClientDNSRejectInternalAddresses flag can no longer be set on
7967 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
7968 Closes ticket 21031.
7969 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
7970 nobody was using it any longer. Closes ticket 22377.
7973 Changes in version 0.2.8.15 - 2017-09-18
7974 Tor 0.2.8.15 backports a collection of bugfixes from later
7977 Most significantly, it includes a fix for TROVE-2017-008, a
7978 security bug that affects hidden services running with the
7979 SafeLogging option disabled. For more information, see
7980 https://trac.torproject.org/projects/tor/ticket/23490
7982 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
7983 2018. We suggest that you upgrade to the latest stable release if
7984 possible. If you can't, we recommend that you upgrade at least to
7985 0.2.9, which will be supported until 2020.
7987 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
7988 - Avoid an assertion failure bug affecting our implementation of
7989 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
7990 handling of "0xx" differs from what we had expected. Fixes bug
7991 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
7994 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
7997 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
7998 - Backport a fix for an "unused variable" warning that appeared
7999 in some versions of mingw. Fixes bug 22838; bugfix on
8002 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
8003 - Fix a memset() off the end of an array when packing cells. This
8004 bug should be harmless in practice, since the corrupted bytes are
8005 still in the same structure, and are always padding bytes,
8006 ignored, or immediately overwritten, depending on compiler
8007 behavior. Nevertheless, because the memset()'s purpose is to make
8008 sure that any other cell-handling bugs can't expose bytes to the
8009 network, we need to fix it. Fixes bug 22737; bugfix on
8010 0.2.4.11-alpha. Fixes CID 1401591.
8012 o Build features (backport from 0.3.1.5-alpha):
8013 - Tor's repository now includes a Travis Continuous Integration (CI)
8014 configuration file (.travis.yml). This is meant to help new
8015 developers and contributors who fork Tor to a Github repository be
8016 better able to test their changes, and understand what we expect
8017 to pass. To use this new build feature, you must fork Tor to your
8018 Github account, then go into the "Integrations" menu in the
8019 repository settings for your fork and enable Travis, then push
8020 your changes. Closes ticket 22636.
8023 Changes in version 0.2.9.12 - 2017-09-18
8024 Tor 0.2.9.12 backports a collection of bugfixes from later
8027 Most significantly, it includes a fix for TROVE-2017-008, a
8028 security bug that affects hidden services running with the
8029 SafeLogging option disabled. For more information, see
8030 https://trac.torproject.org/projects/tor/ticket/23490
8032 o Major features (security, backport from 0.3.0.2-alpha):
8033 - Change the algorithm used to decide DNS TTLs on client and server
8034 side, to better resist DNS-based correlation attacks like the
8035 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
8036 Feamster. Now relays only return one of two possible DNS TTL
8037 values, and clients are willing to believe DNS TTL values up to 3
8038 hours long. Closes ticket 19769.
8040 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
8041 - Fix a rare crash when sending a begin cell on a circuit whose
8042 linked directory connection had already been closed. Fixes bug
8043 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
8045 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
8046 - Fix a bug that prevented exit nodes from caching DNS records for
8047 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
8049 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
8050 - Fix a typo that had prevented TPROXY-based transparent proxying
8051 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8052 Patch from "d4fq0fQAgoJ".
8054 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8055 - Avoid an assertion failure bug affecting our implementation of
8056 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8057 handling of "0xx" differs from what we had expected. Fixes bug
8058 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8060 o Minor features (code style, backport from 0.3.1.3-alpha):
8061 - Add "Falls through" comments to our codebase, in order to silence
8062 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8063 Stieger. Closes ticket 22446.
8065 o Minor features (geoip):
8066 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8069 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
8070 - Roll over monthly accounting at the configured hour and minute,
8071 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8072 Found by Andrey Karpov with PVS-Studio.
8074 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
8075 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8076 bugfix on 0.2.8.1-alpha.
8077 - Fix warnings when building with libscrypt and openssl scrypt support
8078 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8079 - When building with certain versions the mingw C header files, avoid
8080 float-conversion warnings when calling the C functions isfinite(),
8081 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
8083 o Minor bugfixes (compilation, backport from 0.3.1.7):
8084 - Avoid compiler warnings in the unit tests for running tor_sscanf()
8085 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8087 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8088 - Backport a fix for an "unused variable" warning that appeared
8089 in some versions of mingw. Fixes bug 22838; bugfix on
8092 o Minor bugfixes (controller, backport from 0.3.1.7):
8093 - Do not crash when receiving a HSPOST command with an empty body.
8094 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8095 - Do not crash when receiving a POSTDESCRIPTOR command with an
8096 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8098 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8099 - Avoid Coverity build warnings related to our BUG() macro. By
8100 default, Coverity treats BUG() as the Linux kernel does: an
8101 instant abort(). We need to override that so our BUG() macro
8102 doesn't prevent Coverity from analyzing functions that use it.
8103 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8105 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
8106 - Fix a memset() off the end of an array when packing cells. This
8107 bug should be harmless in practice, since the corrupted bytes are
8108 still in the same structure, and are always padding bytes,
8109 ignored, or immediately overwritten, depending on compiler
8110 behavior. Nevertheless, because the memset()'s purpose is to make
8111 sure that any other cell-handling bugs can't expose bytes to the
8112 network, we need to fix it. Fixes bug 22737; bugfix on
8113 0.2.4.11-alpha. Fixes CID 1401591.
8115 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
8116 - When setting the maximum number of connections allowed by the OS,
8117 always allow some extra file descriptors for other files. Fixes
8118 bug 22797; bugfix on 0.2.0.10-alpha.
8120 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8121 - Avoid a sandbox failure when trying to re-bind to a socket and
8122 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8124 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8125 - Permit the fchmod system call, to avoid crashing on startup when
8126 starting with the seccomp2 sandbox and an unexpected set of
8127 permissions on the data directory or its contents. Fixes bug
8128 22516; bugfix on 0.2.5.4-alpha.
8130 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
8131 - Avoid a double-marked-circuit warning that could happen when we
8132 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
8135 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8136 - Reject version numbers with non-numeric prefixes (such as +, -, or
8137 whitespace). Disallowing whitespace prevents differential version
8138 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8139 and part of 21508; bugfix on 0.0.8pre1.
8141 o Build features (backport from 0.3.1.5-alpha):
8142 - Tor's repository now includes a Travis Continuous Integration (CI)
8143 configuration file (.travis.yml). This is meant to help new
8144 developers and contributors who fork Tor to a Github repository be
8145 better able to test their changes, and understand what we expect
8146 to pass. To use this new build feature, you must fork Tor to your
8147 Github account, then go into the "Integrations" menu in the
8148 repository settings for your fork and enable Travis, then push
8149 your changes. Closes ticket 22636.
8152 Changes in version 0.3.0.11 - 2017-09-18
8153 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
8156 Most significantly, it includes a fix for TROVE-2017-008, a
8157 security bug that affects hidden services running with the
8158 SafeLogging option disabled. For more information, see
8159 https://trac.torproject.org/projects/tor/ticket/23490
8161 o Minor features (code style, backport from 0.3.1.7):
8162 - Add "Falls through" comments to our codebase, in order to silence
8163 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8164 Stieger. Closes ticket 22446.
8167 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8170 o Minor bugfixes (compilation, backport from 0.3.1.7):
8171 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
8172 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8174 o Minor bugfixes (controller, backport from 0.3.1.7):
8175 - Do not crash when receiving a HSPOST command with an empty body.
8176 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8177 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
8178 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8180 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
8181 - When setting the maximum number of connections allowed by the OS,
8182 always allow some extra file descriptors for other files. Fixes
8183 bug 22797; bugfix on 0.2.0.10-alpha.
8185 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
8186 - Remove a forgotten debugging message when an introduction point
8187 successfully establishes a hidden service prop224 circuit with
8189 - Change three other log_warn() for an introduction point to
8190 protocol warnings, because they can be failure from the network
8191 and are not relevant to the operator. Fixes bug 23078; bugfix on
8192 0.3.0.1-alpha and 0.3.0.2-alpha.
8195 Changes in version 0.3.1.7 - 2017-09-18
8196 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
8198 With the 0.3.1 series, Tor now serves and downloads directory
8199 information in more compact formats, to save on bandwidth overhead. It
8200 also contains a new padding system to resist netflow-based traffic
8201 analysis, and experimental support for building parts of Tor in Rust
8202 (though no parts of Tor are in Rust yet). There are also numerous
8203 small features, bugfixes on earlier release series, and groundwork for
8204 the hidden services revamp of 0.3.2.
8206 This release also includes a fix for TROVE-2017-008, a security bug
8207 that affects hidden services running with the SafeLogging option
8208 disabled. For more information, see
8209 https://trac.torproject.org/projects/tor/ticket/23490
8211 Per our stable release policy, we plan to support each stable release
8212 series for at least the next nine months, or for three months after
8213 the first stable release of the next series: whichever is longer. If
8214 you need a release with long-term support, we recommend that you stay
8215 with the 0.2.9 series.
8217 Below is a list of the changes since 0.3.1.6-rc. For a list of all
8218 changes since 0.3.0, see the ReleaseNotes file.
8220 o Major bugfixes (security, hidden services, loggging):
8221 - Fix a bug where we could log uninitialized stack when a certain
8222 hidden service error occurred while SafeLogging was disabled.
8223 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
8224 TROVE-2017-008 and CVE-2017-0380.
8226 o Minor features (defensive programming):
8227 - Create a pair of consensus parameters, nf_pad_tor2web and
8228 nf_pad_single_onion, to disable netflow padding in the consensus
8229 for non-anonymous connections in case the overhead is high. Closes
8232 o Minor features (diagnostic):
8233 - Add a stack trace to the bug warnings that can be logged when
8234 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
8235 attempt for bug 23105.
8237 o Minor features (geoip):
8238 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
8241 o Minor bugfixes (compilation):
8242 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
8243 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
8245 o Minor bugfixes (controller):
8246 - Do not crash when receiving a HSPOST command with an empty body.
8247 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
8248 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
8249 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
8251 o Minor bugfixes (relay):
8252 - Inform the geoip and rephist modules about all requests, even on
8253 relays that are only fetching microdescriptors. Fixes a bug
8254 related to 21585; bugfix on 0.3.0.1-alpha.
8256 o Minor bugfixes (unit tests):
8257 - Fix a channelpadding unit test failure on slow systems by using
8258 mocked time instead of actual time. Fixes bug 23077; bugfix
8262 Changes in version 0.3.1.6-rc - 2017-09-05
8263 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
8264 release series, including a bug that produced weird behavior on
8265 Windows directory caches.
8267 This is the first release candidate in the Tor 0.3.1 series. If we
8268 find no new bugs or regressions here, the first stable 0.3.1 release
8269 will be nearly identical to it.
8271 o Major bugfixes (windows, directory cache):
8272 - On Windows, do not try to delete cached consensus documents and
8273 diffs before they are unmapped from memory--Windows won't allow
8274 that. Instead, allow the consensus cache directory to grow larger,
8275 to hold files that might need to stay around longer. Fixes bug
8276 22752; bugfix on 0.3.1.1-alpha.
8278 o Minor features (directory authority):
8279 - Improve the message that authorities report to relays that present
8280 RSA/Ed25519 keypairs that conflict with previously pinned keys.
8281 Closes ticket 22348.
8283 o Minor features (geoip):
8284 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
8287 o Minor features (testing):
8288 - Add more tests for compression backend initialization. Closes
8291 o Minor bugfixes (directory cache):
8292 - Fix a memory leak when recovering space in the consensus cache.
8293 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
8295 o Minor bugfixes (hidden service):
8296 - Increase the number of circuits that a service is allowed to
8297 open over a specific period of time. The value was lower than it
8298 should be (8 vs 12) in the normal case of 3 introduction points.
8299 Fixes bug 22159; bugfix on 0.3.0.5-rc.
8300 - Fix a BUG warning during HSv3 descriptor decoding that could be
8301 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
8302 on 0.3.0.1-alpha. Bug found by "haxxpop".
8303 - Rate-limit the log messages if we exceed the maximum number of
8304 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
8306 o Minor bugfixes (logging, relay):
8307 - Remove a forgotten debugging message when an introduction point
8308 successfully establishes a hidden service prop224 circuit with
8310 - Change three other log_warn() for an introduction point to
8311 protocol warnings, because they can be failure from the network
8312 and are not relevant to the operator. Fixes bug 23078; bugfix on
8313 0.3.0.1-alpha and 0.3.0.2-alpha.
8315 o Minor bugfixes (relay):
8316 - When a relay is not running as a directory cache, it will no
8317 longer generate compressed consensuses and consensus diff
8318 information. Previously, this was a waste of disk and CPU. Fixes
8319 bug 23275; bugfix on 0.3.1.1-alpha.
8321 o Minor bugfixes (robustness, error handling):
8322 - Improve our handling of the cases where OpenSSL encounters a
8323 memory error while encoding keys and certificates. We haven't
8324 observed these errors in the wild, but if they do happen, we now
8325 detect and respond better. Fixes bug 19418; bugfix on all versions
8326 of Tor. Reported by Guido Vranken.
8328 o Minor bugfixes (stability):
8329 - Avoid crashing on a double-free when unable to load or process an
8330 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
8331 with the clang static analyzer.
8333 o Minor bugfixes (testing):
8334 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
8335 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
8336 - Port the hs_ntor handshake test to work correctly with recent
8337 versions of the pysha3 module. Fixes bug 23071; bugfix
8340 o Minor bugfixes (Windows service):
8341 - When running as a Windows service, set the ID of the main thread
8342 correctly. Failure to do so made us fail to send log messages to
8343 the controller in 0.2.1.16-rc, slowed down controller event
8344 delivery in 0.2.7.3-rc and later, and crash with an assertion
8345 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
8346 Patch and diagnosis from "Vort".
8349 Changes in version 0.3.0.10 - 2017-08-02
8350 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
8351 from the current Tor alpha series. OpenBSD users and TPROXY users
8352 should upgrade; others are probably okay sticking with 0.3.0.9.
8354 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
8355 - Tor's repository now includes a Travis Continuous Integration (CI)
8356 configuration file (.travis.yml). This is meant to help new
8357 developers and contributors who fork Tor to a Github repository be
8358 better able to test their changes, and understand what we expect
8359 to pass. To use this new build feature, you must fork Tor to your
8360 Github account, then go into the "Integrations" menu in the
8361 repository settings for your fork and enable Travis, then push
8362 your changes. Closes ticket 22636.
8364 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
8365 - Fix a typo that had prevented TPROXY-based transparent proxying
8366 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
8367 Patch from "d4fq0fQAgoJ".
8369 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
8370 - Avoid an assertion failure bug affecting our implementation of
8371 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8372 handling of "0xbar" differs from what we had expected. Fixes bug
8373 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8375 o Minor features (backport from 0.3.1.5-alpha):
8376 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8379 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
8380 - Roll over monthly accounting at the configured hour and minute,
8381 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
8382 Found by Andrey Karpov with PVS-Studio.
8384 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
8385 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
8386 bugfix on 0.2.8.1-alpha.
8387 - Fix warnings when building with libscrypt and openssl scrypt
8388 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8389 - When building with certain versions of the mingw C header files,
8390 avoid float-conversion warnings when calling the C functions
8391 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8394 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
8395 - Backport a fix for an "unused variable" warning that appeared
8396 in some versions of mingw. Fixes bug 22838; bugfix on
8399 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
8400 - Avoid Coverity build warnings related to our BUG() macro. By
8401 default, Coverity treats BUG() as the Linux kernel does: an
8402 instant abort(). We need to override that so our BUG() macro
8403 doesn't prevent Coverity from analyzing functions that use it.
8404 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8406 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
8407 - When rejecting a router descriptor for running an obsolete version
8408 of Tor without ntor support, warn about the obsolete tor version,
8409 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
8411 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
8412 - Avoid a sandbox failure when trying to re-bind to a socket and
8413 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8415 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
8416 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8417 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8420 Changes in version 0.3.1.5-alpha - 2017-08-01
8421 Tor 0.3.1.5-alpha improves the performance of consensus diff
8422 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
8423 several other bugs. If no serious bugs are found in this version, the
8424 next version will be a release candidate.
8426 This release also marks the end of support for the Tor 0.2.4.x,
8427 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
8428 further bug or security fixes. Anyone still running or distributing
8429 one of those versions should upgrade.
8431 o Major features (build system, continuous integration):
8432 - Tor's repository now includes a Travis Continuous Integration (CI)
8433 configuration file (.travis.yml). This is meant to help new
8434 developers and contributors who fork Tor to a Github repository be
8435 better able to test their changes, and understand what we expect
8436 to pass. To use this new build feature, you must fork Tor to your
8437 Github account, then go into the "Integrations" menu in the
8438 repository settings for your fork and enable Travis, then push
8439 your changes. Closes ticket 22636.
8441 o Major bugfixes (openbsd, denial-of-service):
8442 - Avoid an assertion failure bug affecting our implementation of
8443 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
8444 handling of "0xbar" differs from what we had expected. Fixes bug
8445 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
8447 o Major bugfixes (relay, performance):
8448 - Perform circuit handshake operations at a higher priority than we
8449 use for consensus diff creation and compression. This should
8450 prevent circuits from starving when a relay or bridge receives a
8451 new consensus, especially on lower-powered machines. Fixes bug
8452 22883; bugfix on 0.3.1.1-alpha.
8454 o Minor features (bridge authority):
8455 - Add "fingerprint" lines to the networkstatus-bridges file produced
8456 by bridge authorities. Closes ticket 22207.
8458 o Minor features (directory cache, consensus diff):
8459 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
8460 operators with low-resource environments to adjust the number of
8461 consensuses they'll store and generate diffs from. Most cache
8462 operators should leave it unchanged. Helps to work around
8465 o Minor features (geoip):
8466 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
8469 o Minor features (relay, performance):
8470 - Always start relays with at least two worker threads, to prevent
8471 priority inversion on slow tasks. Part of the fix for bug 22883.
8472 - Allow background work to be queued with different priorities, so
8473 that a big pile of slow low-priority jobs will not starve out
8474 higher priority jobs. This lays the groundwork for a fix for
8477 o Minor bugfixes (build system, rust):
8478 - Fix a problem where Rust toolchains were not being found when
8479 building without --enable-cargo-online-mode, due to setting the
8480 $HOME environment variable instead of $CARGO_HOME. Fixes bug
8481 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
8483 o Minor bugfixes (compatibility, zstd):
8484 - Write zstd epilogues correctly when the epilogue requires
8485 reallocation of the output buffer, even with zstd 1.3.0.
8486 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
8487 22927; bugfix on 0.3.1.1-alpha.
8489 o Minor bugfixes (compilation warnings):
8490 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
8491 22915; bugfix on 0.2.8.1-alpha.
8492 - Fix warnings when building with libscrypt and openssl scrypt
8493 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
8494 - Compile correctly when both openssl 1.1.0 and libscrypt are
8495 detected. Previously this would cause an error. Fixes bug 22892;
8496 bugfix on 0.3.1.1-alpha.
8497 - When building with certain versions of the mingw C header files,
8498 avoid float-conversion warnings when calling the C functions
8499 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
8502 o Minor bugfixes (coverity build support):
8503 - Avoid Coverity build warnings related to our BUG() macro. By
8504 default, Coverity treats BUG() as the Linux kernel does: an
8505 instant abort(). We need to override that so our BUG() macro
8506 doesn't prevent Coverity from analyzing functions that use it.
8507 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
8509 o Minor bugfixes (directory authority):
8510 - When a directory authority rejects a descriptor or extrainfo with
8511 a given digest, mark that digest as undownloadable, so that we do
8512 not attempt to download it again over and over. We previously
8513 tried to avoid downloading such descriptors by other means, but we
8514 didn't notice if we accidentally downloaded one anyway. This
8515 behavior became problematic in 0.2.7.2-alpha, when authorities
8516 began pinning Ed25519 keys. Fixes bug 22349; bugfix
8519 o Minor bugfixes (error reporting, windows):
8520 - When formatting Windows error messages, use the English format to
8521 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
8524 o Minor bugfixes (file limits, osx):
8525 - When setting the maximum number of connections allowed by the OS,
8526 always allow some extra file descriptors for other files. Fixes
8527 bug 22797; bugfix on 0.2.0.10-alpha.
8529 o Minor bugfixes (linux seccomp2 sandbox):
8530 - Avoid a sandbox failure when trying to re-bind to a socket and
8531 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
8533 o Minor bugfixes (memory leaks):
8534 - Fix a small memory leak when validating a configuration that uses
8535 two or more AF_UNIX sockets for the same port type. Fixes bug
8536 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
8538 o Minor bugfixes (unit tests):
8539 - test_consdiff_base64cmp would fail on OS X because while OS X
8540 follows the standard of (less than zero/zero/greater than zero),
8541 it doesn't follow the convention of (-1/0/+1). Make the test
8542 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
8543 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
8544 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
8547 Changes in version 0.3.1.4-alpha - 2017-06-29
8548 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
8549 to use a guard that was in the same network family as a chosen exit
8550 relay. This is a security regression; all clients running earlier
8551 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
8554 This release also fixes several other bugs introduced in 0.3.0.x
8555 and 0.3.1.x, including others that can affect bandwidth usage
8559 - To build with zstd and lzma support, Tor now requires the
8560 pkg-config tool at build time. (This requirement was new in
8561 0.3.1.1-alpha, but was not noted at the time. Noting it here to
8562 close ticket 22623.)
8564 o Major bugfixes (path selection, security):
8565 - When choosing which guard to use for a circuit, avoid the exit's
8566 family along with the exit itself. Previously, the new guard
8567 selection logic avoided the exit, but did not consider its family.
8568 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8569 006 and CVE-2017-0377.
8571 o Major bugfixes (compression, zstd):
8572 - Correctly detect a full buffer when decompressing a large zstd-
8573 compressed input. Previously, we would sometimes treat a full
8574 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
8576 o Major bugfixes (directory protocol):
8577 - Ensure that we send "304 Not modified" as HTTP status code when a
8578 client is attempting to fetch a consensus or consensus diff, and
8579 the best one we can send them is one they already have. Fixes bug
8580 22702; bugfix on 0.3.1.1-alpha.
8582 o Major bugfixes (entry guards):
8583 - When starting with an old consensus, do not add new entry guards
8584 unless the consensus is "reasonably live" (under 1 day old). Fixes
8585 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8587 o Minor features (bug mitigation, diagnostics, logging):
8588 - Avoid an assertion failure, and log a better error message, when
8589 unable to remove a file from the consensus cache on Windows.
8590 Attempts to mitigate and diagnose bug 22752.
8592 o Minor features (geoip):
8593 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8596 o Minor bugfixes (compression):
8597 - When compressing or decompressing a buffer, check for a failure to
8598 create a compression object. Fixes bug 22626; bugfix
8600 - When decompressing a buffer, check for extra data after the end of
8601 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
8602 - When decompressing an object received over an anonymous directory
8603 connection, if we have already decompressed it using an acceptable
8604 compression method, do not reject it for looking like an
8605 unacceptable compression method. Fixes part of bug 22670; bugfix
8607 - When serving directory votes compressed with zlib, do not claim to
8608 have compressed them with zstd. Fixes bug 22669; bugfix
8610 - When spooling compressed data to an output buffer, don't try to
8611 spool more data when there is no more data to spool and we are not
8612 trying to flush the input. Previously, we would sometimes launch
8613 compression requests with nothing to do, which interferes with our
8614 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
8616 o Minor bugfixes (defensive programming):
8617 - Detect and break out of infinite loops in our compression code. We
8618 don't think that any such loops exist now, but it's best to be
8619 safe. Closes ticket 22672.
8620 - Fix a memset() off the end of an array when packing cells. This
8621 bug should be harmless in practice, since the corrupted bytes are
8622 still in the same structure, and are always padding bytes,
8623 ignored, or immediately overwritten, depending on compiler
8624 behavior. Nevertheless, because the memset()'s purpose is to make
8625 sure that any other cell-handling bugs can't expose bytes to the
8626 network, we need to fix it. Fixes bug 22737; bugfix on
8627 0.2.4.11-alpha. Fixes CID 1401591.
8629 o Minor bugfixes (linux seccomp2 sandbox):
8630 - Permit the fchmod system call, to avoid crashing on startup when
8631 starting with the seccomp2 sandbox and an unexpected set of
8632 permissions on the data directory or its contents. Fixes bug
8633 22516; bugfix on 0.2.5.4-alpha.
8634 - Fix a crash in the LZMA module, when the sandbox was enabled, and
8635 liblzma would allocate more than 16 MB of memory. We solve this by
8636 bumping the mprotect() limit in the sandbox module from 16 MB to
8637 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
8639 o Minor bugfixes (logging):
8640 - When decompressing, do not warn if we fail to decompress using a
8641 compression method that we merely guessed. Fixes part of bug
8642 22670; bugfix on 0.1.1.14-alpha.
8643 - When decompressing, treat mismatch between content-encoding and
8644 actual compression type as a protocol warning. Fixes part of bug
8645 22670; bugfix on 0.1.1.9-alpha.
8646 - Downgrade "assigned_to_cpuworker failed" message to info-level
8647 severity. In every case that can reach it, either a better warning
8648 has already been logged, or no warning is warranted. Fixes bug
8649 22356; bugfix on 0.2.6.3-alpha.
8650 - Demote a warn that was caused by libevent delays to info if
8651 netflow padding is less than 4.5 seconds late, or to notice
8652 if it is more (4.5 seconds is the amount of time that a netflow
8653 record might be emitted after, if we chose the maximum timeout).
8654 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
8656 o Minor bugfixes (process behavior):
8657 - When exiting because of an error, always exit with a nonzero exit
8658 status. Previously, we would fail to report an error in our exit
8659 status in cases related to __OwningControllerProcess failure,
8660 lockfile contention, and Ed25519 key initialization. Fixes bug
8661 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
8662 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
8666 - Add a manpage description for the key-pinning-journal file. Closes
8668 - Correctly note that bandwidth accounting values are stored in the
8669 state file, and the bw_accounting file is now obsolete. Closes
8671 - Document more of the files in the Tor data directory, including
8672 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
8673 approved-routers, sr-random, and diff-cache. Found while fixing
8677 Changes in version 0.3.0.9 - 2017-06-29
8678 Tor 0.3.0.9 fixes a path selection bug that would allow a client
8679 to use a guard that was in the same network family as a chosen exit
8680 relay. This is a security regression; all clients running earlier
8681 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
8684 This release also backports several other bugfixes from the 0.3.1.x
8687 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
8688 - When choosing which guard to use for a circuit, avoid the exit's
8689 family along with the exit itself. Previously, the new guard
8690 selection logic avoided the exit, but did not consider its family.
8691 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
8692 006 and CVE-2017-0377.
8694 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
8695 - Don't block bootstrapping when a primary bridge is offline and we
8696 can't get its descriptor. Fixes bug 22325; fixes one case of bug
8697 21969; bugfix on 0.3.0.3-alpha.
8699 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
8700 - When starting with an old consensus, do not add new entry guards
8701 unless the consensus is "reasonably live" (under 1 day old). Fixes
8702 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
8704 o Minor features (geoip):
8705 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
8708 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
8709 - Reject version numbers with non-numeric prefixes (such as +, -, or
8710 whitespace). Disallowing whitespace prevents differential version
8711 parsing between POSIX-based and Windows platforms. Fixes bug 21507
8712 and part of 21508; bugfix on 0.0.8pre1.
8714 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
8715 - Permit the fchmod system call, to avoid crashing on startup when
8716 starting with the seccomp2 sandbox and an unexpected set of
8717 permissions on the data directory or its contents. Fixes bug
8718 22516; bugfix on 0.2.5.4-alpha.
8720 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
8721 - Fix a memset() off the end of an array when packing cells. This
8722 bug should be harmless in practice, since the corrupted bytes are
8723 still in the same structure, and are always padding bytes,
8724 ignored, or immediately overwritten, depending on compiler
8725 behavior. Nevertheless, because the memset()'s purpose is to make
8726 sure that any other cell-handling bugs can't expose bytes to the
8727 network, we need to fix it. Fixes bug 22737; bugfix on
8728 0.2.4.11-alpha. Fixes CID 1401591.
8731 Changes in version 0.3.1.3-alpha - 2017-06-08
8732 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
8733 remotely crash a hidden service with an assertion failure. Anyone
8734 running a hidden service should upgrade to this version, or to some
8735 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8737 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
8738 that sometimes made relays unreliable, as well as several other
8739 bugfixes described below.
8741 o Major bugfixes (hidden service, relay, security):
8742 - Fix a remotely triggerable assertion failure when a hidden service
8743 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8744 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8745 - Fix a remotely triggerable assertion failure caused by receiving a
8746 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8747 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8750 o Major bugfixes (relay, link handshake):
8751 - When performing the v3 link handshake on a TLS connection, report
8752 that we have the x509 certificate that we actually used on that
8753 connection, even if we have changed certificates since that
8754 connection was first opened. Previously, we would claim to have
8755 used our most recent x509 link certificate, which would sometimes
8756 make the link handshake fail. Fixes one case of bug 22460; bugfix
8759 o Major bugfixes (relays, key management):
8760 - Regenerate link and authentication certificates whenever the key
8761 that signs them changes; also, regenerate link certificates
8762 whenever the signed key changes. Previously, these processes were
8763 only weakly coupled, and we relays could (for minutes to hours)
8764 wind up with an inconsistent set of keys and certificates, which
8765 other relays would not accept. Fixes two cases of bug 22460;
8766 bugfix on 0.3.0.1-alpha.
8767 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8768 send the certificate that matches the x509 certificate that we
8769 used on the TLS connection. Previously, there was a race condition
8770 if the TLS context rotated after we began the TLS handshake but
8771 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8774 o Major bugfixes (torrc, crash):
8775 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
8776 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
8778 o Minor features (code style):
8779 - Add "Falls through" comments to our codebase, in order to silence
8780 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
8781 Stieger. Closes ticket 22446.
8783 o Minor features (diagnostic):
8784 - Add logging messages to try to diagnose a rare bug that seems to
8785 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
8786 think this is happening because of incorrect system clocks, but
8787 we'd like to know for certain. Diagnostic for bug 22466.
8789 o Minor bugfixes (correctness):
8790 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8791 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8793 o Minor bugfixes (directory protocol):
8794 - Check for libzstd >= 1.1, because older versions lack the
8795 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
8797 o Minor bugfixes (link handshake):
8798 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8799 months, and regenerate it when it is within one month of expiring.
8800 Previously, we had generated this certificate at startup with a
8801 ten-year lifetime, but that could lead to weird behavior when Tor
8802 was started with a grossly inaccurate clock. Mitigates bug 22466;
8803 mitigation on 0.3.0.1-alpha.
8805 o Minor bugfixes (storage directories):
8806 - Always check for underflows in the cached storage directory usage.
8807 If the usage does underflow, re-calculate it. Also, avoid a
8808 separate underflow when the usage is not known. Fixes bug 22424;
8809 bugfix on 0.3.1.1-alpha.
8811 o Minor bugfixes (unit tests):
8812 - The unit tests now pass on systems where localhost is misconfigured
8813 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
8817 - Clarify the manpage for the (deprecated) torify script. Closes
8820 Changes in version 0.3.0.8 - 2017-06-08
8821 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
8822 remotely crash a hidden service with an assertion failure. Anyone
8823 running a hidden service should upgrade to this version, or to some
8824 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
8826 Tor 0.3.0.8 also includes 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 when a hidden service
8833 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
8834 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
8835 - Fix a remotely triggerable assertion failure caused by receiving a
8836 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8837 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8840 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8841 - When performing the v3 link handshake on a TLS connection, report
8842 that we have the x509 certificate that we actually used on that
8843 connection, even if we have changed certificates since that
8844 connection was first opened. Previously, we would claim to have
8845 used our most recent x509 link certificate, which would sometimes
8846 make the link handshake fail. Fixes one case of bug 22460; bugfix
8849 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
8850 - Regenerate link and authentication certificates whenever the key
8851 that signs them changes; also, regenerate link certificates
8852 whenever the signed key changes. Previously, these processes were
8853 only weakly coupled, and we relays could (for minutes to hours)
8854 wind up with an inconsistent set of keys and certificates, which
8855 other relays would not accept. Fixes two cases of bug 22460;
8856 bugfix on 0.3.0.1-alpha.
8857 - When sending an Ed25519 signing->link certificate in a CERTS cell,
8858 send the certificate that matches the x509 certificate that we
8859 used on the TLS connection. Previously, there was a race condition
8860 if the TLS context rotated after we began the TLS handshake but
8861 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
8864 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
8865 - Stop rejecting v3 hidden service descriptors because their size
8866 did not match an old padding rule. Fixes bug 22447; bugfix on
8869 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8870 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8871 December 2016 (of which ~126 were still functional) with a list of
8872 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8873 2017. Resolves ticket 21564.
8875 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
8876 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
8877 bug 22252; bugfix on 0.2.9.3-alpha.
8879 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8880 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8881 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8883 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
8884 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
8885 months, and regenerate it when it is within one month of expiring.
8886 Previously, we had generated this certificate at startup with a
8887 ten-year lifetime, but that could lead to weird behavior when Tor
8888 was started with a grossly inaccurate clock. Mitigates bug 22466;
8889 mitigation on 0.3.0.1-alpha.
8891 o Minor bugfixes (memory leak, directory authority, backport from
8893 - When directory authorities reject a router descriptor due to
8894 keypinning, free the router descriptor rather than leaking the
8895 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8898 Changes in version 0.2.9.11 - 2017-06-08
8899 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
8900 remotely crash a hidden service with an assertion failure. Anyone
8901 running a hidden service should upgrade to this version, or to some
8902 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8903 are not affected by TROVE-2017-004.)
8905 Tor 0.2.9.11 also backports fixes for several key management bugs
8906 that sometimes made relays unreliable, as well as several other
8907 bugfixes described below.
8909 o Major bugfixes (hidden service, relay, security, backport
8910 from 0.3.1.3-alpha):
8911 - Fix a remotely triggerable assertion failure caused by receiving a
8912 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8913 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8916 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
8917 - When performing the v3 link handshake on a TLS connection, report
8918 that we have the x509 certificate that we actually used on that
8919 connection, even if we have changed certificates since that
8920 connection was first opened. Previously, we would claim to have
8921 used our most recent x509 link certificate, which would sometimes
8922 make the link handshake fail. Fixes one case of bug 22460; bugfix
8925 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8926 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8927 December 2016 (of which ~126 were still functional) with a list of
8928 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8929 2017. Resolves ticket 21564.
8931 o Minor features (future-proofing, backport from 0.3.0.7):
8932 - Tor no longer refuses to download microdescriptors or descriptors if
8933 they are listed as "published in the future". This change will
8934 eventually allow us to stop listing meaningful "published" dates
8935 in microdescriptor consensuses, and thereby allow us to reduce the
8936 resources required to download consensus diffs by over 50%.
8937 Implements part of ticket 21642; implements part of proposal 275.
8939 o Minor features (directory authorities, backport from 0.3.0.4-rc)
8940 - Directory authorities now reject relays running versions
8941 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
8942 suffer from bug 20499 and don't keep their consensus cache
8943 up-to-date. Resolves ticket 20509.
8945 o Minor features (geoip):
8946 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8949 o Minor bugfixes (control port, backport from 0.3.0.6):
8950 - The GETINFO extra-info/digest/<digest> command was broken because
8951 of a wrong base16 decode return value check, introduced when
8952 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
8954 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
8955 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8956 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8958 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
8959 - The getpid() system call is now permitted under the Linux seccomp2
8960 sandbox, to avoid crashing with versions of OpenSSL (and other
8961 libraries) that attempt to learn the process's PID by using the
8962 syscall rather than the VDSO code. Fixes bug 21943; bugfix
8965 o Minor bugfixes (memory leak, directory authority, backport
8966 from 0.3.1.2-alpha):
8967 - When directory authorities reject a router descriptor due to
8968 keypinning, free the router descriptor rather than leaking the
8969 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
8971 Changes in version 0.2.8.14 - 2017-06-08
8972 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
8973 remotely crash a hidden service with an assertion failure. Anyone
8974 running a hidden service should upgrade to this version, or to some
8975 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
8976 are not affected by TROVE-2017-004.)
8978 o Major bugfixes (hidden service, relay, security):
8979 - Fix a remotely triggerable assertion failure caused by receiving a
8980 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
8981 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
8984 o Minor features (geoip):
8985 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
8988 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
8989 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
8990 December 2016 (of which ~126 were still functional) with a list of
8991 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
8992 2017. Resolves ticket 21564.
8994 o Minor bugfixes (correctness):
8995 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
8996 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
8998 Changes in version 0.2.7.8 - 2017-06-08
8999 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
9000 remotely crash a hidden service with an assertion failure. Anyone
9001 running a hidden service should upgrade to this version, or to some
9002 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
9003 are not affected by TROVE-2017-004.)
9005 o Major bugfixes (hidden service, relay, security):
9006 - Fix a remotely triggerable assertion failure caused by receiving a
9007 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
9008 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
9011 o Minor features (geoip):
9012 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9015 o Minor bugfixes (correctness):
9016 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
9017 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
9020 Changes in version 0.2.6.12 - 2017-06-08
9021 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
9022 remotely crash a hidden service with an assertion failure. Anyone
9023 running a hidden service should upgrade to this version, or to some
9024 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
9025 are not affected by TROVE-2017-004.)
9027 o Major bugfixes (hidden service, relay, security):
9028 - Fix a remotely triggerable assertion failure caused by receiving a
9029 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
9030 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
9033 o Minor features (geoip):
9034 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9037 o Minor bugfixes (correctness):
9038 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
9039 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
9041 Changes in version 0.2.5.14 - 2017-06-08
9042 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
9043 remotely crash a hidden service with an assertion failure. Anyone
9044 running a hidden service should upgrade to this version, or to some
9045 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
9046 are not affected by TROVE-2017-004.)
9048 o Major bugfixes (hidden service, relay, security):
9049 - Fix a remotely triggerable assertion failure caused by receiving a
9050 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
9051 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
9054 o Minor features (geoip):
9055 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9058 o Minor bugfixes (correctness):
9059 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
9060 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
9062 Changes in version 0.2.4.29 - 2017-06-08
9063 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
9064 remotely crash a hidden service with an assertion failure. Anyone
9065 running a hidden service should upgrade to this version, or to some
9066 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
9067 are not affected by TROVE-2017-004.)
9069 o Major bugfixes (hidden service, relay, security):
9070 - Fix a remotely triggerable assertion failure caused by receiving a
9071 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
9072 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
9075 o Minor features (geoip):
9076 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9079 o Minor bugfixes (correctness):
9080 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
9081 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
9084 Changes in version 0.3.1.2-alpha - 2017-05-26
9085 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
9086 fixes a few bugs found while testing 0.3.1.1-alpha, including a
9087 memory corruption bug that affected relay stability.
9089 o Major bugfixes (crash, relay):
9090 - Fix a memory-corruption bug in relays that set MyFamily.
9091 Previously, they would double-free MyFamily elements when making
9092 the next descriptor or when changing their configuration. Fixes
9093 bug 22368; bugfix on 0.3.1.1-alpha.
9095 o Minor bugfixes (logging):
9096 - Log a better message when a directory authority replies to an
9097 upload with an unexpected status code. Fixes bug 11121; bugfix
9100 o Minor bugfixes (memory leak, directory authority):
9101 - When directory authorities reject a router descriptor due to
9102 keypinning, free the router descriptor rather than leaking the
9103 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
9106 Changes in version 0.3.1.1-alpha - 2017-05-22
9107 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
9108 reduces the bandwidth usage for Tor's directory protocol, adds some
9109 basic padding to resist netflow-based traffic analysis and to serve as
9110 the basis of other padding in the future, and adds rust support to the
9113 It also contains numerous other small features and improvements to
9114 security, correctness, and performance.
9116 Below are the changes since 0.3.0.7.
9118 o Major features (directory protocol):
9119 - Tor relays and authorities can now serve clients an abbreviated
9120 version of the consensus document, containing only the changes
9121 since an older consensus document that the client holds. Clients
9122 now request these documents when available. When both client and
9123 server use this new protocol, they will use far less bandwidth (up
9124 to 94% less) to keep the client's consensus up-to-date. Implements
9125 proposal 140; closes ticket 13339. Based on work by Daniel Martí.
9126 - Tor can now compress directory traffic with lzma or with zstd
9127 compression algorithms, which can deliver better bandwidth
9128 performance. Because lzma is computationally expensive, it's only
9129 used for documents that can be compressed once and served many
9130 times. Support for these algorithms requires that tor is built
9131 with the libzstd and/or liblzma libraries available. Implements
9132 proposal 278; closes ticket 21662.
9133 - Relays now perform the more expensive compression operations, and
9134 consensus diff generation, in worker threads. This separation
9135 avoids delaying the main thread when a new consensus arrives.
9137 o Major features (experimental):
9138 - Tor can now build modules written in Rust. To turn this on, pass
9139 the "--enable-rust" flag to the configure script. It's not time to
9140 get excited yet: currently, there is no actual Rust functionality
9141 beyond some simple glue code, and a notice at startup to tell you
9142 that Rust is running. Still, we hope that programmers and
9143 packagers will try building Tor with Rust support, so that we can
9144 find issues and solve portability problems. Closes ticket 22106.
9146 o Major features (traffic analysis resistance):
9147 - Connections between clients and relays now send a padding cell in
9148 each direction every 1.5 to 9.5 seconds (tunable via consensus
9149 parameters). This padding will not resist specialized
9150 eavesdroppers, but it should be enough to make many ISPs' routine
9151 network flow logging less useful in traffic analysis against
9154 Padding is negotiated using Tor's link protocol, so both relays
9155 and clients must upgrade for this to take effect. Clients may
9156 still send padding despite the relay's version by setting
9157 ConnectionPadding 1 in torrc, and may disable padding by setting
9158 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
9159 users with the torrc option ReducedConnectionPadding. Implements
9160 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
9161 - Relays will publish 24 hour totals of padding and non-padding cell
9162 counts to their extra-info descriptors, unless PaddingStatistics 0
9163 is set in torrc. These 24 hour totals are also rounded to
9166 o Major bugfixes (connection usage):
9167 - We use NETINFO cells to try to determine if both relays involved
9168 in a connection will agree on the canonical status of that
9169 connection. We prefer the connections where this is the case for
9170 extend cells, and try to close connections where relays disagree
9171 on their canonical status early. Also, we now prefer the oldest
9172 valid connection for extend cells. These two changes should reduce
9173 the number of long-term connections that are kept open between
9174 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
9175 - Relays now log hourly statistics (look for
9176 "channel_check_for_duplicates" lines) on the total number of
9177 connections to other relays. If the number of connections per
9178 relay is unexpectedly large, this log message is at notice level.
9179 Otherwise it is at info.
9181 o Major bugfixes (entry guards):
9182 - Don't block bootstrapping when a primary bridge is offline and we
9183 can't get its descriptor. Fixes bug 22325; fixes one case of bug
9184 21969; bugfix on 0.3.0.3-alpha.
9186 o Major bugfixes (linux TPROXY support):
9187 - Fix a typo that had prevented TPROXY-based transparent proxying
9188 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
9189 Patch from "d4fq0fQAgoJ".
9191 o Minor features (security, windows):
9192 - Enable a couple of pieces of Windows hardening: one
9193 (HeapEnableTerminationOnCorruption) that has been on-by-default
9194 since Windows 8, and unavailable before Windows 7; and one
9195 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
9196 affect us, but shouldn't do any harm. Closes ticket 21953.
9198 o Minor features (config options):
9199 - Allow "%include" directives in torrc configuration files. These
9200 directives import the settings from other files, or from all the
9201 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
9202 - Make SAVECONF return an error when overwriting a torrc that has
9203 includes. Using SAVECONF with the FORCE option will allow it to
9204 overwrite torrc even if includes are used. Related to ticket 1922.
9205 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
9206 will work without the FORCE option. Related to ticket 1922.
9208 o Minor features (controller):
9209 - Warn the first time that a controller requests data in the long-
9210 deprecated 'GETINFO network-status' format. Closes ticket 21703.
9212 o Minor features (defaults):
9213 - The default value for UseCreateFast is now 0: clients which
9214 haven't yet received a consensus document will now use a proper
9215 ntor handshake to talk to their directory servers whenever they
9216 can. Closes ticket 21407.
9217 - Onion key rotation and expiry intervals are now defined as a
9218 network consensus parameter, per proposal 274. The default
9219 lifetime of an onion key is increased from 7 to 28 days. Old onion
9220 keys will expire after 7 days by default. This change will make
9221 consensus diffs much smaller, and save significant bandwidth.
9222 Closes ticket 21641.
9224 o Minor features (fallback directory list):
9225 - Update the fallback directory mirror whitelist and blacklist based
9226 on operator emails. Closes task 21121.
9227 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
9228 December 2016 (of which ~126 were still functional) with a list of
9229 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
9230 2017. Resolves ticket 21564.
9232 o Minor features (hidden services, logging):
9233 - Log a message when a hidden service descriptor has fewer
9234 introduction points than specified in
9235 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
9236 - Log a message when a hidden service reaches its introduction point
9237 circuit limit, and when that limit is reset. Follow up to ticket
9238 21594; closes ticket 21622.
9239 - Warn user if multiple entries in EntryNodes and at least one
9240 HiddenService are used together. Pinning EntryNodes along with a
9241 hidden service can be possibly harmful; for instance see ticket
9242 14917 or 21155. Closes ticket 21155.
9244 o Minor features (linux seccomp2 sandbox):
9245 - We now have a document storage backend compatible with the Linux
9246 seccomp2 sandbox. This backend is used for consensus documents and
9247 diffs between them; in the long term, we'd like to use it for
9248 unparseable directory material too. Closes ticket 21645
9249 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
9250 from 1MB to 16MB. This was necessary with the glibc allocator in
9251 order to allow worker threads to allocate more memory -- which in
9252 turn is necessary because of our new use of worker threads for
9253 compression. Closes ticket 22096.
9255 o Minor features (logging):
9256 - Log files are no longer created world-readable by default.
9257 (Previously, most distributors would store the logs in a non-
9258 world-readable location to prevent inappropriate access. This
9259 change is an extra precaution.) Closes ticket 21729; patch
9262 o Minor features (performance):
9263 - Our Keccak (SHA-3) implementation now accesses memory more
9264 efficiently, especially on little-endian systems. Closes
9266 - Add an O(1) implementation of channel_find_by_global_id(), to
9267 speed some controller functions.
9269 o Minor features (relay, configuration):
9270 - The MyFamily option may now be repeated as many times as desired,
9271 for relays that want to configure large families. Closes ticket
9272 4998; patch by Daniel Pinto.
9274 o Minor features (safety):
9275 - Add an explicit check to extrainfo_parse_entry_from_string() for
9276 NULL inputs. We don't believe this can actually happen, but it may
9277 help silence a warning from the Clang analyzer. Closes
9280 o Minor features (testing):
9281 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
9282 When Tor is compiled with this option, we disable a number of
9283 redundant memory-safety failsafes that are intended to stop bugs
9284 from becoming security issues. This makes it easier to hunt for
9285 bugs that would be security issues without the failsafes turned
9286 on. Closes ticket 21439.
9287 - Add a general event-tracing instrumentation support to Tor. This
9288 subsystem will enable developers and researchers to add fine-
9289 grained instrumentation to their Tor instances, for use when
9290 examining Tor network performance issues. There are no trace
9291 events yet, and event-tracing is off by default unless enabled at
9292 compile time. Implements ticket 13802.
9293 - Improve our version parsing tests: add tests for typical version
9294 components, add tests for invalid versions, including numeric
9295 range and non-numeric prefixes. Unit tests 21278, 21450, and
9296 21507. Partially implements 21470.
9298 o Minor bugfixes (bandwidth accounting):
9299 - Roll over monthly accounting at the configured hour and minute,
9300 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
9301 Found by Andrey Karpov with PVS-Studio.
9303 o Minor bugfixes (code correctness):
9304 - Accurately identify client connections by their lack of peer
9305 authentication. This means that we bail out earlier if asked to
9306 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
9309 o Minor bugfixes (configuration):
9310 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
9311 bug 22252; bugfix on 0.2.9.3-alpha.
9313 o Minor bugfixes (connection lifespan):
9314 - Allow more control over how long TLS connections are kept open:
9315 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
9316 single option called CircuitsAvailableTimeout. Also, allow the
9317 consensus to control the default values for both this preference
9318 and the lifespan of relay-to-relay connections. Fixes bug 17592;
9319 bugfix on 0.2.5.5-alpha.
9320 - Increase the initial circuit build timeout testing frequency, to
9321 help ensure that ReducedConnectionPadding clients finish learning
9322 a timeout before their orconn would expire. The initial testing
9323 rate was set back in the days of TAP and before the Tor Browser
9324 updater, when we had to be much more careful about new clients
9325 making lots of circuits. With this change, a circuit build timeout
9326 is learned in about 15-20 minutes, instead of 100-120 minutes.
9328 o Minor bugfixes (controller):
9329 - GETINFO onions/current and onions/detached no longer respond with
9330 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
9331 - Trigger HS descriptor events on the control port when the client
9332 fails to pick a hidden service directory for a hidden service.
9333 This can happen if all the hidden service directories are in
9334 ExcludeNodes, or they have all been queried within the last 15
9335 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
9337 o Minor bugfixes (directory authority):
9338 - When rejecting a router descriptor for running an obsolete version
9339 of Tor without ntor support, warn about the obsolete tor version,
9340 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
9341 - Prevent the shared randomness subsystem from asserting when
9342 initialized by a bridge authority with an incomplete configuration
9343 file. Fixes bug 21586; bugfix on 0.2.9.8.
9345 o Minor bugfixes (exit-side DNS):
9346 - Fix an untriggerable assertion that checked the output of a
9347 libevent DNS error, so that the assertion actually behaves as
9348 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
9349 Karpov using PVS-Studio.
9351 o Minor bugfixes (fallback directories):
9352 - Make the usage example in updateFallbackDirs.py actually work, and
9353 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
9354 - Decrease the guard flag average required to be a fallback. This
9355 allows us to keep relays that have their guard flag removed when
9356 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9357 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
9358 bugfix on 0.2.8.1-alpha.
9359 - Make sure fallback directory mirrors have the same address, port,
9360 and relay identity key for at least 30 days before they are
9361 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
9363 o Minor bugfixes (hidden services):
9364 - Stop printing a cryptic warning when a hidden service gets a
9365 request to connect to a virtual port that it hasn't configured.
9366 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
9367 - Simplify hidden service descriptor creation by using an existing
9368 flag to check if an introduction point is established. Fixes bug
9369 21599; bugfix on 0.2.7.2-alpha.
9371 o Minor bugfixes (memory leak):
9372 - Fix a small memory leak at exit from the backtrace handler code.
9373 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
9375 o Minor bugfixes (protocol, logging):
9376 - Downgrade a log statement about unexpected relay cells from "bug"
9377 to "protocol warning", because there is at least one use case
9378 where it can be triggered by a buggy tor implementation. Fixes bug
9379 21293; bugfix on 0.1.1.14-alpha.
9381 o Minor bugfixes (testing):
9382 - Use unbuffered I/O for utility functions around the
9383 process_handle_t type. This fixes unit test failures reported on
9384 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
9385 - Make display of captured unit test log messages consistent. Fixes
9386 bug 21510; bugfix on 0.2.9.3-alpha.
9387 - Make test-network.sh always call chutney's test-network.sh.
9388 Previously, this only worked on systems which had bash installed,
9389 due to some bash-specific code in the script. Fixes bug 19699;
9390 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
9392 o Minor bugfixes (voting consistency):
9393 - Reject version numbers with non-numeric prefixes (such as +, -, or
9394 whitespace). Disallowing whitespace prevents differential version
9395 parsing between POSIX-based and Windows platforms. Fixes bug 21507
9396 and part of 21508; bugfix on 0.0.8pre1.
9398 o Minor bugfixes (windows, relay):
9399 - Resolve "Failure from drain_fd: No error" warnings on Windows
9400 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
9402 o Code simplification and refactoring:
9403 - Break up the 630-line function connection_dir_client_reached_eof()
9404 into a dozen smaller functions. This change should help
9405 maintainability and readability of the client directory code.
9406 - Isolate our use of the openssl headers so that they are only
9407 included from our crypto wrapper modules, and from tests that
9408 examine those modules' internals. Closes ticket 21841.
9409 - Simplify our API to launch directory requests, making it more
9410 extensible and less error-prone. Now it's easier to add extra
9411 headers to directory requests. Closes ticket 21646.
9412 - Our base64 decoding functions no longer overestimate the output
9413 space that they need when parsing unpadded inputs. Closes
9415 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
9416 Resolves ticket 22213.
9417 - The logic that directory caches use to spool request to clients,
9418 serving them one part at a time so as not to allocate too much
9419 memory, has been refactored for consistency. Previously there was
9420 a separate spooling implementation per type of spoolable data. Now
9421 there is one common spooling implementation, with extensible data
9422 types. Closes ticket 21651.
9423 - Tor's compression module now supports multiple backends. Part of
9424 the implementation for proposal 278; closes ticket 21663.
9427 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
9428 Closes ticket 21873.
9429 - Correct documentation about the default DataDirectory value.
9430 Closes ticket 21151.
9431 - Document the default behavior of NumEntryGuards and
9432 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
9434 - Document key=value pluggable transport arguments for Bridge lines
9435 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
9436 - Note that bandwidth-limiting options don't affect TCP headers or
9437 DNS. Closes ticket 17170.
9439 o Removed features (configuration options, all in ticket 22060):
9440 - These configuration options are now marked Obsolete, and no longer
9441 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
9442 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
9443 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
9444 in 0.2.9.2-alpha and have now been removed. The previous default
9445 behavior is now always chosen; the previous (less secure) non-
9446 default behavior is now unavailable.
9447 - CloseHSClientCircuitsImmediatelyOnTimeout and
9448 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
9449 0.2.9.2-alpha and now have been removed. HS circuits never close
9450 on circuit build timeout; they have a longer timeout period.
9451 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
9452 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
9453 (and others) to configure listen-only and advertise-only addresses.
9455 o Removed features (tools):
9456 - We've removed the tor-checkkey tool from src/tools. Long ago, we
9457 used it to help people detect RSA keys that were generated by
9458 versions of Debian affected by CVE-2008-0166. But those keys have
9459 been out of circulation for ages, and this tool is no longer
9460 required. Closes ticket 21842.
9463 Changes in version 0.3.0.7 - 2017-05-15
9464 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
9465 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
9466 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
9467 clients are not affected.
9469 o Major bugfixes (hidden service directory, security):
9470 - Fix an assertion failure in the hidden service directory code, which
9471 could be used by an attacker to remotely cause a Tor relay process to
9472 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
9473 should upgrade. This security issue is tracked as TROVE-2017-002.
9474 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
9477 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
9480 o Minor features (future-proofing):
9481 - Tor no longer refuses to download microdescriptors or descriptors
9482 if they are listed as "published in the future". This change will
9483 eventually allow us to stop listing meaningful "published" dates
9484 in microdescriptor consensuses, and thereby allow us to reduce the
9485 resources required to download consensus diffs by over 50%.
9486 Implements part of ticket 21642; implements part of proposal 275.
9488 o Minor bugfixes (Linux seccomp2 sandbox):
9489 - The getpid() system call is now permitted under the Linux seccomp2
9490 sandbox, to avoid crashing with versions of OpenSSL (and other
9491 libraries) that attempt to learn the process's PID by using the
9492 syscall rather than the VDSO code. Fixes bug 21943; bugfix
9496 Changes in version 0.3.0.6 - 2017-04-26
9497 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
9499 With the 0.3.0 series, clients and relays now use Ed25519 keys to
9500 authenticate their link connections to relays, rather than the old
9501 RSA1024 keys that they used before. (Circuit crypto has been
9502 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
9503 the guard selection and replacement algorithm to behave more robustly
9504 in the presence of unreliable networks, and to resist guard-
9507 This series also includes numerous other small features and bugfixes,
9508 along with more groundwork for the upcoming hidden-services revamp.
9510 Per our stable release policy, we plan to support the Tor 0.3.0
9511 release series for at least the next nine months, or for three months
9512 after the first stable release of the 0.3.1 series: whichever is
9513 longer. If you need a release with long-term support, we recommend
9514 that you stay with the 0.2.9 series.
9516 Below are the changes since 0.3.0.5-rc. For a list of all changes
9517 since 0.2.9, see the ReleaseNotes file.
9519 o Minor features (geoip):
9520 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
9523 o Minor bugfixes (control port):
9524 - The GETINFO extra-info/digest/<digest> command was broken because
9525 of a wrong base16 decode return value check, introduced when
9526 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
9528 o Minor bugfixes (crash prevention):
9529 - Fix a (currently untriggerable, but potentially dangerous) crash
9530 bug when base32-encoding inputs whose sizes are not a multiple of
9531 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
9534 Changes in version 0.3.0.5-rc - 2017-04-05
9535 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
9536 0.3.0 release series.
9538 This is the second release candidate in the Tor 0.3.0 series, and has
9539 much fewer changes than the first. If we find no new bugs or
9540 regressions here, the first stable 0.3.0 release will be nearly
9543 o Major bugfixes (crash, directory connections):
9544 - Fix a rare crash when sending a begin cell on a circuit whose
9545 linked directory connection had already been closed. Fixes bug
9546 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
9548 o Major bugfixes (guard selection):
9549 - Fix a guard selection bug where Tor would refuse to bootstrap in
9550 some cases if the user swapped a bridge for another bridge in
9551 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
9552 Reported by "torvlnt33r".
9554 o Minor features (geoip):
9555 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
9558 o Minor bugfix (compilation):
9559 - Fix a warning when compiling hs_service.c. Previously, it had no
9560 exported symbols when compiled for libor.a, resulting in a
9561 compilation warning from clang. Fixes bug 21825; bugfix
9564 o Minor bugfixes (hidden services):
9565 - Make hidden services check for failed intro point connections,
9566 even when they have exceeded their intro point creation limit.
9567 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
9568 - Make hidden services with 8 to 10 introduction points check for
9569 failed circuits immediately after startup. Previously, they would
9570 wait for 5 minutes before performing their first checks. Fixes bug
9571 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
9573 o Minor bugfixes (memory leaks):
9574 - Fix a memory leak when using GETCONF on a port option. Fixes bug
9575 21682; bugfix on 0.3.0.3-alpha.
9577 o Minor bugfixes (relay):
9578 - Avoid a double-marked-circuit warning that could happen when we
9579 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
9582 o Minor bugfixes (tests):
9583 - Run the entry_guard_parse_from_state_full() test with the time set
9584 to a specific date. (The guard state that this test was parsing
9585 contained guards that had expired since the test was first
9586 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
9589 - Update the description of the directory server options in the
9590 manual page, to clarify that a relay no longer needs to set
9591 DirPort in order to be a directory cache. Closes ticket 21720.
9595 Changes in version 0.2.8.13 - 2017-03-03
9596 Tor 0.2.8.13 backports a security fix from later Tor
9597 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
9598 this release, if for some reason they cannot upgrade to a later
9599 release series, and if they build Tor with the --enable-expensive-hardening
9602 Note that support for Tor 0.2.8.x is ending next year: we will not issue
9603 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
9604 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9606 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9607 - Fix an integer underflow bug when comparing malformed Tor
9608 versions. This bug could crash Tor when built with
9609 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9610 0.2.9.8, which were built with -ftrapv by default. In other cases
9611 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9612 on 0.0.8pre1. Found by OSS-Fuzz.
9614 o Minor features (geoip):
9615 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9619 Changes in version 0.2.7.7 - 2017-03-03
9620 Tor 0.2.7.7 backports a number of security fixes from later Tor
9621 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
9622 this release, if for some reason they cannot upgrade to a later
9625 Note that support for Tor 0.2.7.x is ending this year: we will not issue
9626 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
9627 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9629 o Directory authority changes (backport from 0.2.8.5-rc):
9630 - Urras is no longer a directory authority. Closes ticket 19271.
9632 o Directory authority changes (backport from 0.2.9.2-alpha):
9633 - The "Tonga" bridge authority has been retired; the new bridge
9634 authority is "Bifroest". Closes tickets 19728 and 19690.
9636 o Directory authority key updates (backport from 0.2.8.1-alpha):
9637 - Update the V3 identity key for the dannenberg directory authority:
9638 it was changed on 18 November 2015. Closes task 17906. Patch
9641 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9642 - Fix a bug in parsing that could cause clients to read a single
9643 byte past the end of an allocated region. This bug could be used
9644 to cause hardened clients (built with --enable-expensive-hardening)
9645 to crash if they tried to visit a hostile hidden service. Non-
9646 hardened clients are only affected depending on the details of
9647 their platform's memory allocator. Fixes bug 21018; bugfix on
9648 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9649 2016-12-002 and as CVE-2016-1254.
9651 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9652 - Stop a crash that could occur when a client running with DNSPort
9653 received a query with multiple address types, and the first
9654 address type was not supported. Found and fixed by Scott Dial.
9655 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9656 - Prevent a class of security bugs caused by treating the contents
9657 of a buffer chunk as if they were a NUL-terminated string. At
9658 least one such bug seems to be present in all currently used
9659 versions of Tor, and would allow an attacker to remotely crash
9660 most Tor instances, especially those compiled with extra compiler
9661 hardening. With this defense in place, such bugs can't crash Tor,
9662 though we should still fix them as they occur. Closes ticket
9663 20384 (TROVE-2016-10-001).
9665 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9666 - Avoid a difficult-to-trigger heap corruption attack when extending
9667 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9668 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9669 Reported by Guido Vranken.
9671 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9672 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9673 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9675 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9676 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9677 pointer to the previous (uninitialized) key value. The impact here
9678 should be limited to a difficult-to-trigger crash, if OpenSSL is
9679 running an engine that makes key generation failures possible, or
9680 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9681 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9684 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9685 - Fix an integer underflow bug when comparing malformed Tor
9686 versions. This bug could crash Tor when built with
9687 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9688 0.2.9.8, which were built with -ftrapv by default. In other cases
9689 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9690 on 0.0.8pre1. Found by OSS-Fuzz.
9692 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9693 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9694 zero size. Check size argument to memwipe() for underflow. Fixes
9695 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9698 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9699 - Make Tor survive errors involving connections without a
9700 corresponding event object. Previously we'd fail with an
9701 assertion; now we produce a log message. Related to bug 16248.
9703 o Minor features (geoip):
9704 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9708 Changes in version 0.2.6.11 - 2017-03-03
9709 Tor 0.2.6.11 backports a number of security fixes from later Tor
9710 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
9711 this release, if for some reason they cannot upgrade to a later
9714 Note that support for Tor 0.2.6.x is ending this year: we will not issue
9715 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
9716 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9718 o Directory authority changes (backport from 0.2.8.5-rc):
9719 - Urras is no longer a directory authority. Closes ticket 19271.
9721 o Directory authority changes (backport from 0.2.9.2-alpha):
9722 - The "Tonga" bridge authority has been retired; the new bridge
9723 authority is "Bifroest". Closes tickets 19728 and 19690.
9725 o Directory authority key updates (backport from 0.2.8.1-alpha):
9726 - Update the V3 identity key for the dannenberg directory authority:
9727 it was changed on 18 November 2015. Closes task 17906. Patch
9730 o Major features (security fixes, backport from 0.2.9.4-alpha):
9731 - Prevent a class of security bugs caused by treating the contents
9732 of a buffer chunk as if they were a NUL-terminated string. At
9733 least one such bug seems to be present in all currently used
9734 versions of Tor, and would allow an attacker to remotely crash
9735 most Tor instances, especially those compiled with extra compiler
9736 hardening. With this defense in place, such bugs can't crash Tor,
9737 though we should still fix them as they occur. Closes ticket
9738 20384 (TROVE-2016-10-001).
9740 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9741 - Fix a bug in parsing that could cause clients to read a single
9742 byte past the end of an allocated region. This bug could be used
9743 to cause hardened clients (built with --enable-expensive-hardening)
9744 to crash if they tried to visit a hostile hidden service. Non-
9745 hardened clients are only affected depending on the details of
9746 their platform's memory allocator. Fixes bug 21018; bugfix on
9747 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9748 2016-12-002 and as CVE-2016-1254.
9750 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9751 - Stop a crash that could occur when a client running with DNSPort
9752 received a query with multiple address types, and the first
9753 address type was not supported. Found and fixed by Scott Dial.
9754 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9756 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9757 - Fix an error that could cause us to read 4 bytes before the
9758 beginning of an openssl string. This bug could be used to cause
9759 Tor to crash on systems with unusual malloc implementations, or
9760 systems with unusual hardening installed. Fixes bug 17404; bugfix
9763 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9764 - Avoid a difficult-to-trigger heap corruption attack when extending
9765 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9766 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9767 Reported by Guido Vranken.
9769 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9770 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9771 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9773 o Major bugfixes (guard selection, backport from 0.2.7.6):
9774 - Actually look at the Guard flag when selecting a new directory
9775 guard. When we implemented the directory guard design, we
9776 accidentally started treating all relays as if they have the Guard
9777 flag during guard selection, leading to weaker anonymity and worse
9778 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9781 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9782 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9783 pointer to the previous (uninitialized) key value. The impact here
9784 should be limited to a difficult-to-trigger crash, if OpenSSL is
9785 running an engine that makes key generation failures possible, or
9786 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9787 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9790 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9791 - Fix an integer underflow bug when comparing malformed Tor
9792 versions. This bug could crash Tor when built with
9793 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9794 0.2.9.8, which were built with -ftrapv by default. In other cases
9795 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9796 on 0.0.8pre1. Found by OSS-Fuzz.
9798 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9799 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9800 zero size. Check size argument to memwipe() for underflow. Fixes
9801 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9804 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9805 - Make Tor survive errors involving connections without a
9806 corresponding event object. Previously we'd fail with an
9807 assertion; now we produce a log message. Related to bug 16248.
9809 o Minor features (geoip):
9810 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9813 o Minor bugfixes (compilation, backport from 0.2.7.6):
9814 - Fix a compilation warning with Clang 3.6: Do not check the
9815 presence of an address which can never be NULL. Fixes bug 17781.
9818 Changes in version 0.2.5.13 - 2017-03-03
9819 Tor 0.2.5.13 backports a number of security fixes from later Tor
9820 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
9821 this release, if for some reason they cannot upgrade to a later
9824 Note that support for Tor 0.2.5.x is ending next year: we will not issue
9825 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
9826 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
9828 o Directory authority changes (backport from 0.2.8.5-rc):
9829 - Urras is no longer a directory authority. Closes ticket 19271.
9831 o Directory authority changes (backport from 0.2.9.2-alpha):
9832 - The "Tonga" bridge authority has been retired; the new bridge
9833 authority is "Bifroest". Closes tickets 19728 and 19690.
9835 o Directory authority key updates (backport from 0.2.8.1-alpha):
9836 - Update the V3 identity key for the dannenberg directory authority:
9837 it was changed on 18 November 2015. Closes task 17906. Patch
9840 o Major features (security fixes, backport from 0.2.9.4-alpha):
9841 - Prevent a class of security bugs caused by treating the contents
9842 of a buffer chunk as if they were a NUL-terminated string. At
9843 least one such bug seems to be present in all currently used
9844 versions of Tor, and would allow an attacker to remotely crash
9845 most Tor instances, especially those compiled with extra compiler
9846 hardening. With this defense in place, such bugs can't crash Tor,
9847 though we should still fix them as they occur. Closes ticket
9848 20384 (TROVE-2016-10-001).
9850 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9851 - Fix a bug in parsing that could cause clients to read a single
9852 byte past the end of an allocated region. This bug could be used
9853 to cause hardened clients (built with --enable-expensive-hardening)
9854 to crash if they tried to visit a hostile hidden service. Non-
9855 hardened clients are only affected depending on the details of
9856 their platform's memory allocator. Fixes bug 21018; bugfix on
9857 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9858 2016-12-002 and as CVE-2016-1254.
9860 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
9861 - Stop a crash that could occur when a client running with DNSPort
9862 received a query with multiple address types, and the first
9863 address type was not supported. Found and fixed by Scott Dial.
9864 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
9866 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9867 - Fix an error that could cause us to read 4 bytes before the
9868 beginning of an openssl string. This bug could be used to cause
9869 Tor to crash on systems with unusual malloc implementations, or
9870 systems with unusual hardening installed. Fixes bug 17404; bugfix
9873 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9874 - Avoid a difficult-to-trigger heap corruption attack when extending
9875 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9876 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9877 Reported by Guido Vranken.
9879 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9880 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9881 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9883 o Major bugfixes (guard selection, backport from 0.2.7.6):
9884 - Actually look at the Guard flag when selecting a new directory
9885 guard. When we implemented the directory guard design, we
9886 accidentally started treating all relays as if they have the Guard
9887 flag during guard selection, leading to weaker anonymity and worse
9888 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
9891 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
9892 - If OpenSSL fails to generate an RSA key, do not retain a dangling
9893 pointer to the previous (uninitialized) key value. The impact here
9894 should be limited to a difficult-to-trigger crash, if OpenSSL is
9895 running an engine that makes key generation failures possible, or
9896 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
9897 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
9900 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
9901 - Fix an integer underflow bug when comparing malformed Tor
9902 versions. This bug could crash Tor when built with
9903 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
9904 0.2.9.8, which were built with -ftrapv by default. In other cases
9905 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
9906 on 0.0.8pre1. Found by OSS-Fuzz.
9908 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
9909 - Make memwipe() do nothing when passed a NULL pointer or buffer of
9910 zero size. Check size argument to memwipe() for underflow. Fixes
9911 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
9914 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
9915 - Make Tor survive errors involving connections without a
9916 corresponding event object. Previously we'd fail with an
9917 assertion; now we produce a log message. Related to bug 16248.
9919 o Minor features (geoip):
9920 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
9923 o Minor bugfixes (compilation, backport from 0.2.7.6):
9924 - Fix a compilation warning with Clang 3.6: Do not check the
9925 presence of an address which can never be NULL. Fixes bug 17781.
9927 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
9928 - Check for failures from crypto_early_init, and refuse to continue.
9929 A previous typo meant that we could keep going with an
9930 uninitialized crypto library, and would have OpenSSL initialize
9931 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
9932 when implementing ticket 4900. Patch by "teor".
9934 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
9935 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
9936 a client authorized hidden service. Fixes bug 15823; bugfix
9940 Changes in version 0.2.4.28 - 2017-03-03
9941 Tor 0.2.4.28 backports a number of security fixes from later Tor
9942 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
9943 this release, if for some reason they cannot upgrade to a later
9946 Note that support for Tor 0.2.4.x is ending soon: we will not issue
9947 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
9948 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
9950 o Directory authority changes (backport from 0.2.8.5-rc):
9951 - Urras is no longer a directory authority. Closes ticket 19271.
9953 o Directory authority changes (backport from 0.2.9.2-alpha):
9954 - The "Tonga" bridge authority has been retired; the new bridge
9955 authority is "Bifroest". Closes tickets 19728 and 19690.
9957 o Directory authority key updates (backport from 0.2.8.1-alpha):
9958 - Update the V3 identity key for the dannenberg directory authority:
9959 it was changed on 18 November 2015. Closes task 17906. Patch
9962 o Major features (security fixes, backport from 0.2.9.4-alpha):
9963 - Prevent a class of security bugs caused by treating the contents
9964 of a buffer chunk as if they were a NUL-terminated string. At
9965 least one such bug seems to be present in all currently used
9966 versions of Tor, and would allow an attacker to remotely crash
9967 most Tor instances, especially those compiled with extra compiler
9968 hardening. With this defense in place, such bugs can't crash Tor,
9969 though we should still fix them as they occur. Closes ticket
9970 20384 (TROVE-2016-10-001).
9972 o Major bugfixes (parsing, security, backport from 0.2.9.8):
9973 - Fix a bug in parsing that could cause clients to read a single
9974 byte past the end of an allocated region. This bug could be used
9975 to cause hardened clients (built with --enable-expensive-hardening)
9976 to crash if they tried to visit a hostile hidden service. Non-
9977 hardened clients are only affected depending on the details of
9978 their platform's memory allocator. Fixes bug 21018; bugfix on
9979 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
9980 2016-12-002 and as CVE-2016-1254.
9982 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
9983 - Fix an error that could cause us to read 4 bytes before the
9984 beginning of an openssl string. This bug could be used to cause
9985 Tor to crash on systems with unusual malloc implementations, or
9986 systems with unusual hardening installed. Fixes bug 17404; bugfix
9989 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
9990 - Avoid a difficult-to-trigger heap corruption attack when extending
9991 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
9992 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
9993 Reported by Guido Vranken.
9995 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
9996 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
9997 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
9999 o Major bugfixes (guard selection, backport from 0.2.7.6):
10000 - Actually look at the Guard flag when selecting a new directory
10001 guard. When we implemented the directory guard design, we
10002 accidentally started treating all relays as if they have the Guard
10003 flag during guard selection, leading to weaker anonymity and worse
10004 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
10007 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
10008 - If OpenSSL fails to generate an RSA key, do not retain a dangling
10009 pointer to the previous (uninitialized) key value. The impact here
10010 should be limited to a difficult-to-trigger crash, if OpenSSL is
10011 running an engine that makes key generation failures possible, or
10012 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
10013 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
10016 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
10017 - Fix an integer underflow bug when comparing malformed Tor
10018 versions. This bug could crash Tor when built with
10019 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10020 0.2.9.8, which were built with -ftrapv by default. In other cases
10021 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10022 on 0.0.8pre1. Found by OSS-Fuzz.
10024 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
10025 - Make memwipe() do nothing when passed a NULL pointer or buffer of
10026 zero size. Check size argument to memwipe() for underflow. Fixes
10027 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
10030 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
10031 - Make Tor survive errors involving connections without a
10032 corresponding event object. Previously we'd fail with an
10033 assertion; now we produce a log message. Related to bug 16248.
10035 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
10036 - Make it harder for attackers to overload hidden services with
10037 introductions, by blocking multiple introduction requests on the
10038 same circuit. Resolves ticket 15515.
10040 o Minor features (geoip):
10041 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10044 o Minor bugfixes (compilation, backport from 0.2.7.6):
10045 - Fix a compilation warning with Clang 3.6: Do not check the
10046 presence of an address which can never be NULL. Fixes bug 17781.
10048 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
10049 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
10050 a client authorized hidden service. Fixes bug 15823; bugfix
10054 Changes in version 0.3.0.4-rc - 2017-03-01
10055 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
10056 0.3.0 release series, and introduces a few reliability features to
10057 keep them from coming back.
10059 This is the first release candidate in the Tor 0.3.0 series. If we
10060 find no new bugs or regressions here, the first stable 0.3.0 release
10061 will be nearly identical to it.
10063 o Major bugfixes (bridges):
10064 - When the same bridge is configured multiple times with the same
10065 identity, but at different address:port combinations, treat those
10066 bridge instances as separate guards. This fix restores the ability
10067 of clients to configure the same bridge with multiple pluggable
10068 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
10070 o Major bugfixes (hidden service directory v3):
10071 - Stop crashing on a failed v3 hidden service descriptor lookup
10072 failure. Fixes bug 21471; bugfixes on 0.3.0.1-alpha.
10074 o Major bugfixes (parsing):
10075 - When parsing a malformed content-length field from an HTTP
10076 message, do not read off the end of the buffer. This bug was a
10077 potential remote denial-of-service attack against Tor clients and
10078 relays. A workaround was released in October 2016, to prevent this
10079 bug from crashing Tor. This is a fix for the underlying issue,
10080 which should no longer matter (if you applied the earlier patch).
10081 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
10082 using AFL (http://lcamtuf.coredump.cx/afl/).
10083 - Fix an integer underflow bug when comparing malformed Tor
10084 versions. This bug could crash Tor when built with
10085 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10086 0.2.9.8, which were built with -ftrapv by default. In other cases
10087 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10088 on 0.0.8pre1. Found by OSS-Fuzz.
10090 o Minor feature (protocol versioning):
10091 - Add new protocol version for proposal 224. HSIntro now advertises
10092 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
10094 o Minor features (directory authorities):
10095 - Directory authorities now reject descriptors that claim to be
10096 malformed versions of Tor. Helps prevent exploitation of
10098 - Reject version numbers with components that exceed INT32_MAX.
10099 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10100 Fixes bug 21450; bugfix on 0.0.8pre1.
10101 - Directory authorities now reject relays running versions
10102 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
10103 suffer from bug 20499 and don't keep their consensus cache
10104 up-to-date. Resolves ticket 20509.
10106 o Minor features (geoip):
10107 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10110 o Minor features (reliability, crash):
10111 - Try better to detect problems in buffers where they might grow (or
10112 think they have grown) over 2 GB in size. Diagnostic for
10115 o Minor features (testing):
10116 - During 'make test-network-all', if tor logs any warnings, ask
10117 chutney to output them. Requires a recent version of chutney with
10118 the 21572 patch. Implements 21570.
10120 o Minor bugfixes (certificate expiration time):
10121 - Avoid using link certificates that don't become valid till some
10122 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
10124 o Minor bugfixes (code correctness):
10125 - Repair a couple of (unreachable or harmless) cases of the risky
10126 comparison-by-subtraction pattern that caused bug 21278.
10127 - Remove a redundant check for the UseEntryGuards option from the
10128 options_transition_affects_guards() function. Fixes bug 21492;
10129 bugfix on 0.3.0.1-alpha.
10131 o Minor bugfixes (directory mirrors):
10132 - Allow relays to use directory mirrors without a DirPort: these
10133 relays need to be contacted over their ORPorts using a begindir
10134 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
10135 - Clarify the message logged when a remote relay is unexpectedly
10136 missing an ORPort or DirPort: users were confusing this with a
10137 local port. Fixes another case of bug 20711; bugfix
10140 o Minor bugfixes (guards):
10141 - Don't warn about a missing guard state on timeout-measurement
10142 circuits: they aren't supposed to be using guards. Fixes an
10143 instance of bug 21007; bugfix on 0.3.0.1-alpha.
10144 - Silence a BUG() warning when attempting to use a guard whose
10145 descriptor we don't know, and make this scenario less likely to
10146 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
10148 o Minor bugfixes (hidden service):
10149 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
10150 cells. Previously, we were using sizeof() on a pointer, instead of
10151 the real destination buffer. Fortunately, that value was only used
10152 to double-check that there was enough room--which was already
10153 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
10155 o Minor bugfixes (testing):
10156 - Fix Raspbian build issues related to missing socket errno in
10157 test_util.c. Fixes bug 21116; bugfix on 0.2.8.2. Patch
10159 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
10160 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
10161 - Use bash in src/test/test-network.sh. This ensures we reliably
10162 call chutney's newer tools/test-network.sh when available. Fixes
10163 bug 21562; bugfix on 0.2.9.1-alpha.
10166 - Small fixes to the fuzzing documentation. Closes ticket 21472.
10169 Changes in version 0.2.9.10 - 2017-03-01
10170 Tor 0.2.9.10 backports a security fix from later Tor release. It also
10171 includes fixes for some major issues affecting directory authorities,
10172 LibreSSL compatibility, and IPv6 correctness.
10174 The Tor 0.2.9.x release series is now marked as a long-term-support
10175 series. We intend to backport security fixes to 0.2.9.x until at
10176 least January of 2020.
10178 o Major bugfixes (directory authority, 0.3.0.3-alpha):
10179 - During voting, when marking a relay as a probable sybil, do not
10180 clear its BadExit flag: sybils can still be bad in other ways
10181 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10184 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
10185 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10186 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10187 exit policy rejects that port on more than an IPv6 /16 of
10188 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10189 which rejected a relay's own IPv6 address by default. Fixes bug
10190 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10192 o Major bugfixes (parsing, also in 0.3.0.4-rc):
10193 - Fix an integer underflow bug when comparing malformed Tor
10194 versions. This bug could crash Tor when built with
10195 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
10196 0.2.9.8, which were built with -ftrapv by default. In other cases
10197 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
10198 on 0.0.8pre1. Found by OSS-Fuzz.
10200 o Minor features (directory authorities, also in 0.3.0.4-rc):
10201 - Directory authorities now reject descriptors that claim to be
10202 malformed versions of Tor. Helps prevent exploitation of
10204 - Reject version numbers with components that exceed INT32_MAX.
10205 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
10206 Fixes bug 21450; bugfix on 0.0.8pre1.
10208 o Minor features (geoip):
10209 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
10212 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
10213 - Autoconf now checks to determine if OpenSSL structures are opaque,
10214 instead of explicitly checking for OpenSSL version numbers. Part
10216 - Support building with recent LibreSSL code that uses opaque
10217 structures. Closes ticket 21359.
10219 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
10220 - Repair a couple of (unreachable or harmless) cases of the risky
10221 comparison-by-subtraction pattern that caused bug 21278.
10223 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
10224 - The tor-resolve command line tool now rejects hostnames over 255
10225 characters in length. Previously, it would silently truncate them,
10226 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10227 Patch by "junglefowl".
10230 Changes in version 0.3.0.3-alpha - 2017-02-03
10231 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
10232 0.3.0.x development series, including some that could cause
10233 authorities to behave badly. There is also a fix for a longstanding
10234 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
10235 includes some smaller features and bugfixes.
10237 The Tor 0.3.0.x release series is now in patch-freeze: no additional
10238 features will be considered for inclusion in 0.3.0.x. We suspect that
10239 some bugs will probably remain, however, and we encourage people to
10242 o Major bugfixes (directory authority):
10243 - During voting, when marking a relay as a probable sybil, do not
10244 clear its BadExit flag: sybils can still be bad in other ways
10245 too. (We still clear the other flags.) Fixes bug 21108; bugfix
10247 - When deciding whether we have just found a router to be reachable,
10248 do not penalize it for not having performed an Ed25519 link
10249 handshake if it does not claim to support an Ed25519 handshake.
10250 Previously, we would treat such relays as non-running. Fixes bug
10251 21107; bugfix on 0.3.0.1-alpha.
10253 o Major bugfixes (entry guards):
10254 - Stop trying to build circuits through entry guards for which we
10255 have no descriptor. Also, stop crashing in the case that we *do*
10256 accidentally try to build a circuit in such a state. Fixes bug
10257 21242; bugfix on 0.3.0.1-alpha.
10259 o Major bugfixes (IPv6 Exits):
10260 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
10261 any IPv6 addresses. Instead, only reject a port over IPv6 if the
10262 exit policy rejects that port on more than an IPv6 /16 of
10263 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
10264 which rejected a relay's own IPv6 address by default. Fixes bug
10265 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
10267 o Minor feature (client):
10268 - Enable IPv6 traffic on the SocksPort by default. To disable this,
10269 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
10271 o Minor feature (fallback scripts):
10272 - Add a check_existing mode to updateFallbackDirs.py, which checks
10273 if fallbacks in the hard-coded list are working. Closes ticket
10274 20174. Patch by haxxpop.
10276 o Minor features (ciphersuite selection):
10277 - Clients now advertise a list of ciphersuites closer to the ones
10278 preferred by Firefox. Closes part of ticket 15426.
10279 - Allow relays to accept a wider range of ciphersuites, including
10280 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
10282 o Minor features (controller, configuration):
10283 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
10284 and so on, now comes with a __*Port variant that will not be saved
10285 to the torrc file by the controller's SAVECONF command. This
10286 change allows TorBrowser to set up a single-use domain socket for
10287 each time it launches Tor. Closes ticket 20956.
10288 - The GETCONF command can now query options that may only be
10289 meaningful in context-sensitive lists. This allows the controller
10290 to query the mixed SocksPort/__SocksPort style options introduced
10291 in feature 20956. Implements ticket 21300.
10293 o Minor features (portability, compilation):
10294 - Autoconf now checks to determine if OpenSSL structures are opaque,
10295 instead of explicitly checking for OpenSSL version numbers. Part
10297 - Support building with recent LibreSSL code that uses opaque
10298 structures. Closes ticket 21359.
10300 o Minor features (relay):
10301 - We now allow separation of exit and relay traffic to different
10302 source IP addresses, using the OutboundBindAddressExit and
10303 OutboundBindAddressOR options respectively. Closes ticket 17975.
10304 Written by Michael Sonntag.
10306 o Minor bugfix (logging):
10307 - Don't recommend the use of Tor2web in non-anonymous mode.
10308 Recommending Tor2web is a bad idea because the client loses all
10309 anonymity. Tor2web should only be used in specific cases by users
10310 who *know* and understand the issues. Fixes bug 21294; bugfix
10313 o Minor bugfixes (client):
10314 - Always recover from failures in extend_info_from_node(), in an
10315 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
10316 bugfix on 0.2.3.1-alpha.
10318 o Minor bugfixes (client, entry guards):
10319 - Fix a bug warning (with backtrace) when we fail a channel that
10320 circuits to fallback directories on it. Fixes bug 21128; bugfix
10322 - Fix a spurious bug warning (with backtrace) when removing an
10323 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
10324 - Fix a bug of the new guard algorithm where tor could stall for up
10325 to 10 minutes before retrying a guard after a long period of no
10326 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
10327 - Do not try to build circuits until we have descriptors for our
10328 primary entry guards. Related to fix for bug 21242.
10330 o Minor bugfixes (configure, autoconf):
10331 - Rename the configure option --enable-expensive-hardening to
10332 --enable-fragile-hardening. Expensive hardening makes the tor
10333 daemon abort when some kinds of issues are detected. Thus, it
10334 makes tor more at risk of remote crashes but safer against RCE or
10335 heartbleed bug category. We now try to explain this issue in a
10336 message from the configure script. Fixes bug 21290; bugfix
10339 o Minor bugfixes (controller):
10340 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
10341 20824; bugfix on 0.3.0.1-alpha.
10343 o Minor bugfixes (hidden service):
10344 - Clean up the code for expiring intro points with no associated
10345 circuits. It was causing, rarely, a service with some expiring
10346 introduction points to not open enough additional introduction
10347 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
10348 - Stop setting the torrc option HiddenServiceStatistics to "0" just
10349 because we're not a bridge or relay. Instead, we preserve whatever
10350 value the user set (or didn't set). Fixes bug 21150; bugfix
10352 - Resolve two possible underflows which could lead to creating and
10353 closing a lot of introduction point circuits in a non-stop loop.
10354 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
10356 o Minor bugfixes (portability):
10357 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
10358 It is supported by OpenBSD itself, and also by most OpenBSD
10359 variants (such as Bitrig). Fixes bug 20980; bugfix
10361 - When mapping a file of length greater than SIZE_MAX, do not
10362 silently truncate its contents. This issue could occur on 32 bit
10363 systems with large file support and files which are larger than 4
10364 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
10366 o Minor bugfixes (tor-resolve):
10367 - The tor-resolve command line tool now rejects hostnames over 255
10368 characters in length. Previously, it would silently truncate them,
10369 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
10370 Patch by "junglefowl".
10372 o Minor bugfixes (Windows services):
10373 - Be sure to initialize the monotonic time subsystem before using
10374 it, even when running as an NT service. Fixes bug 21356; bugfix
10378 Changes in version 0.3.0.2-alpha - 2017-01-23
10379 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
10380 cause relays and clients to crash, even if they were not built with
10381 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10382 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10383 version should upgrade.
10385 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
10386 time-to-live values, makes directory authorities enforce the 1-to-1
10387 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
10388 client-side onion service reachability bug, does better at selecting
10389 the set of fallback directories, and more.
10391 o Major bugfixes (security, also in 0.2.9.9):
10392 - Downgrade the "-ftrapv" option from "always on" to "only on when
10393 --enable-expensive-hardening is provided." This hardening option, like
10394 others, can turn survivable bugs into crashes--and having it on by
10395 default made a (relatively harmless) integer overflow bug into a
10396 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
10399 o Major features (security):
10400 - Change the algorithm used to decide DNS TTLs on client and server
10401 side, to better resist DNS-based correlation attacks like the
10402 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
10403 Feamster. Now relays only return one of two possible DNS TTL
10404 values, and clients are willing to believe DNS TTL values up to 3
10405 hours long. Closes ticket 19769.
10407 o Major features (directory authority, security):
10408 - The default for AuthDirPinKeys is now 1: directory authorities
10409 will reject relays where the RSA identity key matches a previously
10410 seen value, but the Ed25519 key has changed. Closes ticket 18319.
10412 o Major bugfixes (client, guard, crash):
10413 - In circuit_get_global_origin_list(), return the actual list of
10414 origin circuits. The previous version of this code returned the
10415 list of all the circuits, and could have caused strange bugs,
10416 including possible crashes. Fixes bug 21118; bugfix
10419 o Major bugfixes (client, onion service, also in 0.2.9.9):
10420 - Fix a client-side onion service reachability bug, where multiple
10421 socks requests to an onion service (or a single slow request)
10422 could cause us to mistakenly mark some of the service's
10423 introduction points as failed, and we cache that failure so
10424 eventually we run out and can't reach the service. Also resolves a
10425 mysterious "Remote server sent bogus reason code 65021" log
10426 warning. The bug was introduced in ticket 17218, where we tried to
10427 remember the circuit end reason as a uint16_t, which mangled
10428 negative values. Partially fixes bug 21056 and fixes bug 20307;
10429 bugfix on 0.2.8.1-alpha.
10431 o Major bugfixes (DNS):
10432 - Fix a bug that prevented exit nodes from caching DNS records for
10433 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
10435 o Minor features (controller):
10436 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
10437 shared-random values to the controller. Closes ticket 19925.
10439 o Minor features (entry guards):
10440 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
10441 break regression tests.
10442 - Require UseEntryGuards when UseBridges is set, in order to make
10443 sure bridges aren't bypassed. Resolves ticket 20502.
10445 o Minor features (fallback directories):
10446 - Select 200 fallback directories for each release. Closes
10448 - Allow 3 fallback relays per operator, which is safe now that we
10449 are choosing 200 fallback relays. Closes ticket 20912.
10450 - Exclude relays affected by bug 20499 from the fallback list.
10451 Exclude relays from the fallback list if they are running versions
10452 known to be affected by bug 20499, or if in our tests they deliver
10453 a stale consensus (i.e. one that expired more than 24 hours ago).
10454 Closes ticket 20539.
10455 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
10457 - Require fallback directories to have the same address and port for
10458 7 days (now that we have enough relays with this stability).
10459 Relays whose OnionOO stability timer is reset on restart by bug
10460 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
10461 this issue. Closes ticket 20880; maintains short-term fix
10463 - Require fallbacks to have flags for 90% of the time (weighted
10464 decaying average), rather than 95%. This allows at least 73% of
10465 clients to bootstrap in the first 5 seconds without contacting an
10466 authority. Part of ticket 18828.
10467 - Annotate updateFallbackDirs.py with the bandwidth and consensus
10468 weight for each candidate fallback. Closes ticket 20878.
10469 - Make it easier to change the output sort order of fallbacks.
10470 Closes ticket 20822.
10471 - Display the relay fingerprint when downloading consensuses from
10472 fallbacks. Closes ticket 20908.
10474 o Minor features (geoip, also in 0.2.9.9):
10475 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10478 o Minor features (next-gen onion service directories):
10479 - Remove the "EnableOnionServicesV3" consensus parameter that we
10480 introduced in 0.3.0.1-alpha: relays are now always willing to act
10481 as v3 onion service directories. Resolves ticket 19899.
10483 o Minor features (linting):
10484 - Enhance the changes file linter to warn on Tor versions that are
10485 prefixed with "tor-". Closes ticket 21096.
10487 o Minor features (logging):
10488 - In several places, describe unset ed25519 keys as "<unset>",
10489 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
10491 o Minor bugfix (control protocol):
10492 - The reply to a "GETINFO config/names" request via the control
10493 protocol now spells the type "Dependent" correctly. This is a
10494 breaking change in the control protocol. (The field seems to be
10495 ignored by the most common known controllers.) Fixes bug 18146;
10496 bugfix on 0.1.1.4-alpha.
10498 o Minor bugfixes (bug resilience):
10499 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
10500 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
10501 Hans Jerry Illikainen.
10503 o Minor bugfixes (build):
10504 - Replace obsolete Autoconf macros with their modern equivalent and
10505 prevent similar issues in the future. Fixes bug 20990; bugfix
10508 o Minor bugfixes (client, guards):
10509 - Fix bug where Tor would think that there are circuits waiting for
10510 better guards even though those circuits have been freed. Fixes
10511 bug 21142; bugfix on 0.3.0.1-alpha.
10513 o Minor bugfixes (config):
10514 - Don't assert on startup when trying to get the options list and
10515 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
10516 options so of course they aren't ready yet. Fixes bug 21062;
10517 bugfix on 0.2.9.3-alpha.
10519 o Minor bugfixes (controller):
10520 - Make the GETINFO interface for inquiring about entry guards
10521 support the new guards backend. Fixes bug 20823; bugfix
10524 o Minor bugfixes (dead code):
10525 - Remove a redundant check for PidFile changes at runtime in
10526 options_transition_allowed(): this check is already performed
10527 regardless of whether the sandbox is active. Fixes bug 21123;
10528 bugfix on 0.2.5.4-alpha.
10530 o Minor bugfixes (documentation):
10531 - Update the tor manual page to document every option that can not
10532 be changed while tor is running. Fixes bug 21122.
10534 o Minor bugfixes (fallback directories):
10535 - Stop failing when a relay has no uptime data in
10536 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
10537 - Avoid checking fallback candidates' DirPorts if they are down in
10538 OnionOO. When a relay operator has multiple relays, this
10539 prioritizes relays that are up over relays that are down. Fixes
10540 bug 20926; bugfix on 0.2.8.3-alpha.
10541 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
10542 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
10544 o Minor bugfixes (guards, bootstrapping):
10545 - When connecting to a directory guard during bootstrap, do not mark
10546 the guard as successful until we receive a good-looking directory
10547 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
10549 o Minor bugfixes (onion services):
10550 - Fix the config reload pruning of old vs new services so it
10551 actually works when both ephemeral and non-ephemeral services are
10552 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
10553 - Allow the number of introduction points to be as low as 0, rather
10554 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
10556 o Minor bugfixes (IPv6):
10557 - Make IPv6-using clients try harder to find an IPv6 directory
10558 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
10559 - When IPv6 addresses have not been downloaded yet (microdesc
10560 consensus documents don't list relay IPv6 addresses), use hard-
10561 coded addresses for authorities, fallbacks, and configured
10562 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
10563 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
10565 o Minor bugfixes (memory leaks):
10566 - Fix a memory leak when configuring hidden services. Fixes bug
10567 20987; bugfix on 0.3.0.1-alpha.
10569 o Minor bugfixes (portability, also in 0.2.9.9):
10570 - Avoid crashing when Tor is built using headers that contain
10571 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10572 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10574 - Fix Libevent detection on platforms without Libevent 1 headers
10575 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10577 o Minor bugfixes (relay):
10578 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
10579 initializing the keys would reset the DataDirectory to 0700
10580 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
10581 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
10583 o Minor bugfixes (testing):
10584 - Remove undefined behavior from the backtrace generator by removing
10585 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
10587 o Minor bugfixes (unit tests):
10588 - Allow the unit tests to pass even when DNS lookups of bogus
10589 addresses do not fail as expected. Fixes bug 20862 and 20863;
10590 bugfix on unit tests introduced in 0.2.8.1-alpha
10591 through 0.2.9.4-alpha.
10593 o Code simplification and refactoring:
10594 - Refactor code to manipulate global_origin_circuit_list into
10595 separate functions. Closes ticket 20921.
10597 o Documentation (formatting):
10598 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
10599 blocks were incorrectly appearing. Closes ticket 20885.
10601 o Documentation (man page):
10602 - Clarify many options in tor.1 and add some min/max values for
10603 HiddenService options. Closes ticket 21058.
10606 Changes in version 0.2.9.9 - 2017-01-23
10607 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
10608 cause relays and clients to crash, even if they were not built with
10609 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
10610 versions, and also affects 0.3.0.1-alpha: all relays running an affected
10611 version should upgrade.
10613 This release also resolves a client-side onion service reachability
10614 bug, and resolves a pair of small portability issues.
10616 o Major bugfixes (security):
10617 - Downgrade the "-ftrapv" option from "always on" to "only on when
10618 --enable-expensive-hardening is provided." This hardening option,
10619 like others, can turn survivable bugs into crashes -- and having
10620 it on by default made a (relatively harmless) integer overflow bug
10621 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
10622 bugfix on 0.2.9.1-alpha.
10624 o Major bugfixes (client, onion service):
10625 - Fix a client-side onion service reachability bug, where multiple
10626 socks requests to an onion service (or a single slow request)
10627 could cause us to mistakenly mark some of the service's
10628 introduction points as failed, and we cache that failure so
10629 eventually we run out and can't reach the service. Also resolves a
10630 mysterious "Remote server sent bogus reason code 65021" log
10631 warning. The bug was introduced in ticket 17218, where we tried to
10632 remember the circuit end reason as a uint16_t, which mangled
10633 negative values. Partially fixes bug 21056 and fixes bug 20307;
10634 bugfix on 0.2.8.1-alpha.
10636 o Minor features (geoip):
10637 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
10640 o Minor bugfixes (portability):
10641 - Avoid crashing when Tor is built using headers that contain
10642 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
10643 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
10645 - Fix Libevent detection on platforms without Libevent 1 headers
10646 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
10649 Changes in version 0.3.0.1-alpha - 2016-12-19
10650 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
10651 series. It strengthens Tor's link and circuit handshakes by
10652 identifying relays by their Ed25519 keys, improves the algorithm that
10653 clients use to choose and maintain their list of guards, and includes
10654 additional backend support for the next-generation hidden service
10655 design. It also contains numerous other small features and
10656 improvements to security, correctness, and performance.
10658 Below are the changes since 0.2.9.8.
10660 o Major features (guard selection algorithm):
10661 - Tor's guard selection algorithm has been redesigned from the
10662 ground up, to better support unreliable networks and restrictive
10663 sets of entry nodes, and to better resist guard-capture attacks by
10664 hostile local networks. Implements proposal 271; closes
10667 o Major features (next-generation hidden services):
10668 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
10669 prop224 aka "Next Generation Hidden Services". Service and clients
10670 don't use this functionality yet. Closes ticket 19043. Based on
10671 initial code by Alec Heifetz.
10672 - Relays now support the HSDir version 3 protocol, so that they can
10673 can store and serve v3 descriptors. This is part of the next-
10674 generation onion service work detailed in proposal 224. Closes
10677 o Major features (protocol, ed25519 identity keys):
10678 - Relays now use Ed25519 to prove their Ed25519 identities and to
10679 one another, and to clients. This algorithm is faster and more
10680 secure than the RSA-based handshake we've been doing until now.
10681 Implements the second big part of proposal 220; Closes
10683 - Clients now support including Ed25519 identity keys in the EXTEND2
10684 cells they generate. By default, this is controlled by a consensus
10685 parameter, currently disabled. You can turn this feature on for
10686 testing by setting ExtendByEd25519ID in your configuration. This
10687 might make your traffic appear different than the traffic
10688 generated by other users, however. Implements part of ticket
10689 15056; part of proposal 220.
10690 - Relays now understand requests to extend to other relays by their
10691 Ed25519 identity keys. When an Ed25519 identity key is included in
10692 an EXTEND2 cell, the relay will only extend the circuit if the
10693 other relay can prove ownership of that identity. Implements part
10694 of ticket 15056; part of proposal 220.
10696 o Major bugfixes (scheduler):
10697 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
10698 caused the channel scheduler to behave more or less randomly,
10699 rather than preferring channels with higher-priority circuits.
10700 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
10702 o Minor features (controller):
10703 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
10704 rather than "unrecognized." Closes ticket 20389; patch from
10707 o Minor features (diagnostic, directory client):
10708 - Warn when we find an unexpected inconsistency in directory
10709 download status objects. Prevents some negative consequences of
10712 o Minor features (directory authority):
10713 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
10714 default) to control whether authorities should try to probe relays
10715 by their Ed25519 link keys. This option will go away in a few
10716 releases--unless we encounter major trouble in our ed25519 link
10717 protocol rollout, in which case it will serve as a safety option.
10719 o Minor features (directory cache):
10720 - Relays and bridges will now refuse to serve the consensus they
10721 have if they know it is too old for a client to use. Closes
10724 o Minor features (ed25519 link handshake):
10725 - Advertise support for the ed25519 link handshake using the
10726 subprotocol-versions mechanism, so that clients can tell which
10727 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
10729 o Minor features (fingerprinting resistance, authentication):
10730 - Extend the length of RSA keys used for TLS link authentication to
10731 2048 bits. (These weren't used for forward secrecy; for forward
10732 secrecy, we used P256.) Closes ticket 13752.
10734 o Minor features (infrastructure):
10735 - Implement smartlist_add_strdup() function. Replaces the use of
10736 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
10738 o Minor bugfixes (client):
10739 - When clients that use bridges start up with a cached consensus on
10740 disk, they were ignoring it and downloading a new one. Now they
10741 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
10743 o Minor bugfixes (configuration):
10744 - Accept non-space whitespace characters after the severity level in
10745 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
10746 - Support "TByte" and "TBytes" units in options given in bytes.
10747 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
10748 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
10750 o Minor bugfixes (consensus weight):
10751 - Add new consensus method that initializes bw weights to 1 instead
10752 of 0. This prevents a zero weight from making it all the way to
10753 the end (happens in small testing networks) and causing an error.
10754 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
10756 o Minor bugfixes (descriptors):
10757 - Correctly recognise downloaded full descriptors as valid, even
10758 when using microdescriptors as circuits. This affects clients with
10759 FetchUselessDescriptors set, and may affect directory authorities.
10760 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
10762 o Minor bugfixes (directory system):
10763 - Download all consensus flavors, descriptors, and authority
10764 certificates when FetchUselessDescriptors is set, regardless of
10765 whether tor is a directory cache or not. Fixes bug 20667; bugfix
10766 on all recent tor versions.
10767 - Bridges and relays now use microdescriptors (like clients do)
10768 rather than old-style router descriptors. Now bridges will blend
10769 in with clients in terms of the circuits they build. Fixes bug
10770 6769; bugfix on 0.2.3.2-alpha.
10772 o Minor bugfixes (ed25519 certificates):
10773 - Correctly interpret ed25519 certificates that would expire some
10774 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
10776 o Minor bugfixes (hidden services):
10777 - Stop ignoring misconfigured hidden services. Instead, refuse to
10778 start tor until the misconfigurations have been corrected. Fixes
10779 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
10782 o Minor bugfixes (memory leak at exit):
10783 - Fix a small harmless memory leak at exit of the previously unused
10784 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
10787 o Minor bugfixes (util):
10788 - When finishing writing a file to disk, if we were about to replace
10789 the file with the temporary file created before and we fail to
10790 replace it, remove the temporary file so it doesn't stay on disk.
10791 Fixes bug 20646; bugfix on 0.2.0.7-alpha. Patch by fk.
10793 o Minor bugfixes (Windows):
10794 - Check for getpagesize before using it to mmap files. This fixes
10795 compilation in some MinGW environments. Fixes bug 20530; bugfix on
10796 0.1.2.1-alpha. Reported by "ice".
10798 o Code simplification and refactoring:
10799 - Abolish all global guard context in entrynodes.c; replace with new
10800 guard_selection_t structure as preparation for proposal 271.
10801 Closes ticket 19858.
10802 - Introduce rend_service_is_ephemeral() that tells if given onion
10803 service is ephemeral. Replace unclear NULL-checkings for service
10804 directory with this function. Closes ticket 20526.
10805 - Extract magic numbers in circuituse.c into defined variables.
10806 - Refactor circuit_is_available_for_use to remove unnecessary check.
10807 - Refactor circuit_predict_and_launch_new for readability and
10808 testability. Closes ticket 18873.
10809 - Refactor large if statement in purpose_needs_anonymity to use
10810 switch statement instead. Closes part of ticket 20077.
10811 - Refactor the hashing API to return negative values for errors, as
10812 is done as throughout the codebase. Closes ticket 20717.
10813 - Remove data structures that were used to index or_connection
10814 objects by their RSA identity digests. These structures are fully
10815 redundant with the similar structures used in the
10816 channel abstraction.
10817 - Remove duplicate code in the channel_write_*cell() functions.
10818 Closes ticket 13827; patch from Pingl.
10819 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
10820 use only purpose_needs_anonymity. Closes part of ticket 20077.
10821 - The code to generate and parse EXTEND and EXTEND2 cells has been
10822 replaced with code automatically generated by the
10826 - Include the "TBits" unit in Tor's man page. Fixes part of bug
10827 20622; bugfix on 0.2.5.1-alpha.
10828 - Change '1' to 'weight_scale' in consensus bw weights calculation
10829 comments, as that is reality. Closes ticket 20273. Patch
10831 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
10832 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
10834 - Stop the man page from incorrectly stating that HiddenServiceDir
10835 must already exist. Fixes 20486.
10836 - Clarify that when ClientRejectInternalAddresses is enabled (which
10837 is the default), multicast DNS hostnames for machines on the local
10838 network (of the form *.local) are also rejected. Closes
10841 o Removed features:
10842 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
10843 limit for relays running on a single IP applies to authority IP
10844 addresses as well as to non-authority IP addresses. Closes
10846 - The UseDirectoryGuards torrc option no longer exists: all users
10847 that use entry guards will also use directory guards. Related to
10848 proposal 271; implements part of ticket 20831.
10851 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
10852 from "overcaffeinated".
10853 - Perform the coding style checks when running the tests and fail
10854 when coding style violations are found. Closes ticket 5500.
10855 - Add tests for networkstatus_compute_bw_weights_v10.
10856 - Add unit tests circuit_predict_and_launch_new.
10857 - Extract dummy_origin_circuit_new so it can be used by other
10861 Changes in version 0.2.8.12 - 2016-12-19
10862 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
10863 below) where Tor clients could crash when attempting to visit a
10864 hostile hidden service. Clients are recommended to upgrade as packages
10865 become available for their systems.
10867 It also includes an updated list of fallback directories, backported
10870 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
10871 backported to 0.2.8 in the future.
10873 o Major bugfixes (parsing, security, backported from 0.2.9.8):
10874 - Fix a bug in parsing that could cause clients to read a single
10875 byte past the end of an allocated region. This bug could be used
10876 to cause hardened clients (built with --enable-expensive-hardening)
10877 to crash if they tried to visit a hostile hidden service. Non-
10878 hardened clients are only affected depending on the details of
10879 their platform's memory allocator. Fixes bug 21018; bugfix on
10880 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10881 2016-12-002 and as CVE-2016-1254.
10883 o Minor features (fallback directory list, backported from 0.2.9.8):
10884 - Replace the 81 remaining fallbacks of the 100 originally
10885 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10886 fallbacks (123 new, 54 existing, 27 removed) generated in December
10887 2016. Resolves ticket 20170.
10889 o Minor features (geoip, backported from 0.2.9.7-rc):
10890 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10894 Changes in version 0.2.9.8 - 2016-12-19
10895 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
10897 The Tor 0.2.9 series makes mandatory a number of security features
10898 that were formerly optional. It includes support for a new shared-
10899 randomness protocol that will form the basis for next generation
10900 hidden services, includes a single-hop hidden service mode for
10901 optimizing .onion services that don't actually want to be hidden,
10902 tries harder not to overload the directory authorities with excessive
10903 downloads, and supports a better protocol versioning scheme for
10904 improved compatibility with other implementations of the Tor protocol.
10906 And of course, there are numerous other bugfixes and improvements.
10908 This release also includes a fix for a medium-severity issue (bug
10909 21018 below) where Tor clients could crash when attempting to visit a
10910 hostile hidden service. Clients are recommended to upgrade as packages
10911 become available for their systems.
10913 Below are the changes since 0.2.9.7-rc. For a list of all changes
10914 since 0.2.8, see the ReleaseNotes file.
10916 o Major bugfixes (parsing, security):
10917 - Fix a bug in parsing that could cause clients to read a single
10918 byte past the end of an allocated region. This bug could be used
10919 to cause hardened clients (built with --enable-expensive-hardening)
10920 to crash if they tried to visit a hostile hidden service. Non-
10921 hardened clients are only affected depending on the details of
10922 their platform's memory allocator. Fixes bug 21018; bugfix on
10923 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
10924 2016-12-002 and as CVE-2016-1254.
10926 o Minor features (fallback directory list):
10927 - Replace the 81 remaining fallbacks of the 100 originally
10928 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
10929 fallbacks (123 new, 54 existing, 27 removed) generated in December
10930 2016. Resolves ticket 20170.
10933 Changes in version 0.2.9.7-rc - 2016-12-12
10934 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
10935 including a few that had prevented tests from passing on
10938 o Minor features (geoip):
10939 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
10942 o Minor bugfix (build):
10943 - The current Git revision when building from a local repository is
10944 now detected correctly when using git worktrees. Fixes bug 20492;
10945 bugfix on 0.2.3.9-alpha.
10947 o Minor bugfixes (directory authority):
10948 - When computing old Tor protocol line version in protover, we were
10949 looking at 0.2.7.5 twice instead of a specific case for
10950 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
10952 o Minor bugfixes (download scheduling):
10953 - Resolve a "bug" warning when considering a download schedule whose
10954 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
10956 o Minor bugfixes (logging):
10957 - Downgrade a harmless log message about the
10958 pending_entry_connections list from "warn" to "info". Mitigates
10961 o Minor bugfixes (memory leak):
10962 - Fix a small memory leak when receiving AF_UNIX connections on a
10963 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
10964 - When moving a signed descriptor object from a source to an
10965 existing destination, free the allocated memory inside that
10966 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
10968 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
10969 - Fix a memory leak and use-after-free error when removing entries
10970 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
10971 0.2.5.5-alpha. Patch from "cypherpunks".
10973 o Minor bugfixes (portability):
10974 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
10975 Fixes bug 20935; bugfix on 0.2.9.6-rc.
10977 o Minor bugfixes (unit tests):
10978 - Stop expecting NetBSD unit tests to report success for ipfw. Part
10979 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
10980 - Fix tolerances in unit tests for monotonic time comparisons
10981 between nanoseconds and microseconds. Previously, we accepted a 10
10982 us difference only, which is not realistic on every platform's
10983 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
10984 - Remove a double-free in the single onion service unit test. Stop
10985 ignoring a return value. Make future changes less error-prone.
10986 Fixes bug 20864; bugfix on 0.2.9.6-rc.
10989 Changes in version 0.2.8.11 - 2016-12-08
10990 Tor 0.2.8.11 backports fixes for additional portability issues that
10991 could prevent Tor from building correctly on OSX Sierra, or with
10992 OpenSSL 1.1. Affected users should upgrade; others can safely stay
10995 o Minor bugfixes (portability):
10996 - Avoid compilation errors when building on OSX Sierra. Sierra began
10997 to support the getentropy() and clock_gettime() APIs, but created
10998 a few problems in doing so. Tor 0.2.9 has a more thorough set of
10999 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
11000 monotonic time interfaces. Fixes bug 20865. Bugfix
11003 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
11004 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
11005 architectures. Closes ticket 20588.
11008 Changes in version 0.2.8.10 - 2016-12-02
11009 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
11010 unusable after they left standby mode. It also backports fixes for
11011 a few portability issues and a small but problematic memory leak.
11013 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
11014 - When Tor leaves standby because of a new application request, open
11015 circuits as needed to serve that request. Previously, we would
11016 potentially wait a very long time. Fixes part of bug 19969; bugfix
11019 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
11020 - Clients now respond to new application stream requests immediately
11021 when they arrive, rather than waiting up to one second before
11022 starting to handle them. Fixes part of bug 19969; bugfix
11025 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
11026 - Work around a bug in the OSX 10.12 SDK that would prevent us from
11027 successfully targeting earlier versions of OSX. Resolves
11030 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
11031 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
11032 20551; bugfix on 0.2.1.1-alpha.
11034 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
11035 - Work around a memory leak in OpenSSL 1.1 when encoding public
11036 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
11038 o Minor features (geoip):
11039 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
11042 Changes in version 0.2.9.6-rc - 2016-12-02
11043 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
11044 version. We hope that it will be ready to become stable soon, and we
11045 encourage everyone to test this release. If no showstopper bugs are
11046 found here, the next 0.2.9 release will be stable.
11048 o Major bugfixes (relay, resolver, logging):
11049 - For relays that don't know their own address, avoid attempting a
11050 local hostname resolve for each descriptor we download. This
11051 will cut down on the number of "Success: chose address 'x.x.x.x'"
11052 log lines, and also avoid confusing clock jumps if the resolver
11053 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
11055 o Minor bugfixes (client, fascistfirewall):
11056 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
11057 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
11059 o Minor bugfixes (hidden services):
11060 - Stop ignoring the anonymity status of saved keys for hidden
11061 services and single onion services when first starting tor.
11062 Instead, refuse to start tor if any hidden service key has been
11063 used in a different hidden service anonymity mode. Fixes bug
11064 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
11066 o Minor bugfixes (portability):
11067 - Work around a bug in the OSX 10.12 SDK that would prevent us from
11068 successfully targeting earlier versions of OSX. Resolves
11070 - Run correctly when built on Windows build environments that
11071 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
11073 o Minor bugfixes (single onion services, Tor2web):
11074 - Stop complaining about long-term one-hop circuits deliberately
11075 created by single onion services and Tor2web. These log messages
11076 are intended to diagnose issue 8387, which relates to circuits
11077 hanging around forever for no reason. Fixes bug 20613; bugfix on
11078 0.2.9.1-alpha. Reported by "pastly".
11080 o Minor bugfixes (unit tests):
11081 - Stop spurious failures in the local interface address discovery
11082 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
11086 - Correct the minimum bandwidth value in torrc.sample, and queue a
11087 corresponding change for torrc.minimal. Closes ticket 20085.
11090 Changes in version 0.2.9.5-alpha - 2016-11-08
11091 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
11092 version. We believe one or two probably remain, and we encourage
11093 everyone to test this release.
11095 o Major bugfixes (client performance):
11096 - Clients now respond to new application stream requests immediately
11097 when they arrive, rather than waiting up to one second before
11098 starting to handle them. Fixes part of bug 19969; bugfix
11101 o Major bugfixes (client reliability):
11102 - When Tor leaves standby because of a new application request, open
11103 circuits as needed to serve that request. Previously, we would
11104 potentially wait a very long time. Fixes part of bug 19969; bugfix
11107 o Major bugfixes (download scheduling):
11108 - When using an exponential backoff schedule, do not give up on
11109 downloading just because we have failed a bunch of times. Since
11110 each delay is longer than the last, retrying indefinitely won't
11111 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
11112 - If a consensus expires while we are waiting for certificates to
11113 download, stop waiting for certificates.
11114 - If we stop waiting for certificates less than a minute after we
11115 started downloading them, do not consider the certificate download
11116 failure a separate failure. Fixes bug 20533; bugfix
11118 - Remove the maximum delay on exponential-backoff scheduling. Since
11119 we now allow an infinite number of failures (see ticket 20536), we
11120 must now allow the time to grow longer on each failure. Fixes part
11121 of bug 20534; bugfix on 0.2.9.1-alpha.
11122 - Make our initial download delays closer to those from 0.2.8. Fixes
11123 another part of bug 20534; bugfix on 0.2.9.1-alpha.
11124 - When determining when to download a directory object, handle times
11125 after 2038 if the operating system supports them. (Someday this
11126 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
11127 - When using exponential backoff in test networks, use a lower
11128 exponent, so the delays do not vary as much. This helps test
11129 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
11131 o Minor features (geoip):
11132 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
11135 o Minor bugfixes (client directory scheduling):
11136 - Treat "relay too busy to answer request" as a failed request and a
11137 reason to back off on our retry frequency. This is safe now that
11138 exponential backoffs retry indefinitely, and avoids a bug where we
11139 would reset our download schedule erroneously. Fixes bug 20593;
11140 bugfix on 0.2.9.1-alpha.
11142 o Minor bugfixes (client, logging):
11143 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
11144 assume all nodes support EXTEND2. Use ntor whenever a key is
11145 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
11146 - On DNSPort, stop logging a BUG warning on a failed hostname
11147 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
11149 o Minor bugfixes (hidden services):
11150 - When configuring hidden services, check every hidden service
11151 directory's permissions. Previously, we only checked the last
11152 hidden service. Fixes bug 20529; bugfix the work to fix 13942
11155 o Minor bugfixes (portability):
11156 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
11157 architectures. Closes ticket 20588.
11158 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
11159 removed the ECDH ciphers which caused the tests to fail on
11160 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
11161 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
11162 20551; bugfix on 0.2.1.1-alpha.
11164 o Minor bugfixes (relay bootstrap):
11165 - Ensure relays don't make multiple connections during bootstrap.
11166 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
11168 o Minor bugfixes (relay):
11169 - Work around a memory leak in OpenSSL 1.1 when encoding public
11170 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
11171 - Avoid a small memory leak when informing worker threads about
11172 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
11173 - Do not try to parallelize workers more than 16x without the user
11174 explicitly configuring us to do so, even if we do detect more than
11175 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
11177 o Minor bugfixes (single onion services):
11178 - Start correctly when creating a single onion service in a
11179 directory that did not previously exist. Fixes bug 20484; bugfix
11182 o Minor bugfixes (testing):
11183 - Avoid a unit test failure on systems with over 16 detectable CPU
11184 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
11187 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
11188 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
11189 - Module-level documentation for several more modules. Closes
11190 tickets 19287 and 19290.
11193 Changes in version 0.2.8.9 - 2016-10-17
11194 Tor 0.2.8.9 backports a fix for a security hole in previous versions
11195 of Tor that would allow a remote attacker to crash a Tor client,
11196 hidden service, relay, or authority. All Tor users should upgrade to
11197 this version, or to 0.2.9.4-alpha. Patches will be released for older
11200 o Major features (security fixes, also in 0.2.9.4-alpha):
11201 - Prevent a class of security bugs caused by treating the contents
11202 of a buffer chunk as if they were a NUL-terminated string. At
11203 least one such bug seems to be present in all currently used
11204 versions of Tor, and would allow an attacker to remotely crash
11205 most Tor instances, especially those compiled with extra compiler
11206 hardening. With this defense in place, such bugs can't crash Tor,
11207 though we should still fix them as they occur. Closes ticket
11208 20384 (TROVE-2016-10-001).
11210 o Minor features (geoip):
11211 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11215 Changes in version 0.2.9.4-alpha - 2016-10-17
11216 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
11217 that would allow a remote attacker to crash a Tor client, hidden
11218 service, relay, or authority. All Tor users should upgrade to this
11219 version, or to 0.2.8.9. Patches will be released for older versions
11222 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
11223 previous versions of Tor, including the implementation of a feature to
11224 future- proof the Tor ecosystem against protocol changes, some bug
11225 fixes necessary for Tor Browser to use unix domain sockets correctly,
11226 and several portability improvements. We anticipate that this will be
11227 the last alpha in the Tor 0.2.9 series, and that the next release will
11228 be a release candidate.
11230 o Major features (security fixes):
11231 - Prevent a class of security bugs caused by treating the contents
11232 of a buffer chunk as if they were a NUL-terminated string. At
11233 least one such bug seems to be present in all currently used
11234 versions of Tor, and would allow an attacker to remotely crash
11235 most Tor instances, especially those compiled with extra compiler
11236 hardening. With this defense in place, such bugs can't crash Tor,
11237 though we should still fix them as they occur. Closes ticket
11238 20384 (TROVE-2016-10-001).
11240 o Major features (subprotocol versions):
11241 - Tor directory authorities now vote on a set of recommended
11242 subprotocol versions, and on a set of required subprotocol
11243 versions. Clients and relays that lack support for a _required_
11244 subprotocol version will not start; those that lack support for a
11245 _recommended_ subprotocol version will warn the user to upgrade.
11246 Closes ticket 19958; implements part of proposal 264.
11247 - Tor now uses "subprotocol versions" to indicate compatibility.
11248 Previously, versions of Tor looked at the declared Tor version of
11249 a relay to tell whether they could use a given feature. Now, they
11250 should be able to rely on its declared subprotocol versions. This
11251 change allows compatible implementations of the Tor protocol(s) to
11252 exist without pretending to be 100% bug-compatible with particular
11253 releases of Tor itself. Closes ticket 19958; implements part of
11256 o Minor feature (fallback directories):
11257 - Remove broken fallbacks from the hard-coded fallback directory
11258 list. Closes ticket 20190; patch by teor.
11260 o Minor features (client, directory):
11261 - Since authorities now omit all routers that lack the Running and
11262 Valid flags, we assume that any relay listed in the consensus must
11263 have those flags. Closes ticket 20001; implements part of
11266 o Minor features (compilation, portability):
11267 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
11270 o Minor features (development tools, etags):
11271 - Teach the "make tags" Makefile target how to correctly find
11272 "MOCK_IMPL" function definitions. Patch from nherring; closes
11275 o Minor features (geoip):
11276 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
11279 o Minor features (unix domain sockets):
11280 - When configuring a unix domain socket for a SocksPort,
11281 ControlPort, or Hidden service, you can now wrap the address in
11282 quotes, using C-style escapes inside the quotes. This allows unix
11283 domain socket paths to contain spaces.
11285 o Minor features (virtual addresses):
11286 - Increase the maximum number of bits for the IPv6 virtual network
11287 prefix from 16 to 104. In this way, the condition for address
11288 allocation is less restrictive. Closes ticket 20151; feature
11291 o Minor bugfixes (address discovery):
11292 - Stop reordering IP addresses returned by the OS. This makes it
11293 more likely that Tor will guess the same relay IP address every
11294 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
11295 Reported by René Mayrhofer, patch by "cypherpunks".
11297 o Minor bugfixes (client, unix domain sockets):
11298 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
11299 the client address is meaningless. Fixes bug 20261; bugfix
11302 o Minor bugfixes (compilation, OpenBSD):
11303 - Detect Libevent2 functions correctly on systems that provide
11304 libevent2, but where libevent1 is linked with -levent. Fixes bug
11305 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
11307 o Minor bugfixes (configuration):
11308 - When parsing quoted configuration values from the torrc file,
11309 handle windows line endings correctly. Fixes bug 19167; bugfix on
11310 0.2.0.16-alpha. Patch from "Pingl".
11312 o Minor bugfixes (getpass):
11313 - Defensively fix a non-triggerable heap corruption at do_getpass()
11314 to protect ourselves from mistakes in the future. Fixes bug
11315 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
11318 o Minor bugfixes (hidden service):
11319 - Allow hidden services to run on IPv6 addresses even when the
11320 IPv6Exit option is not set. Fixes bug 18357; bugfix
11324 - Add module-level internal documentation for 36 C files that
11325 previously didn't have a high-level overview. Closes ticket #20385.
11327 o Required libraries:
11328 - When building with OpenSSL, Tor now requires version 1.0.1 or
11329 later. OpenSSL 1.0.0 and earlier are no longer supported by the
11330 OpenSSL team, and should not be used. Closes ticket 20303.
11333 Changes in version 0.2.9.3-alpha - 2016-09-23
11334 Tor 0.2.9.3-alpha adds improved support for entities that want to make
11335 high-performance services available through the Tor .onion mechanism
11336 without themselves receiving anonymity as they host those services. It
11337 also tries harder to ensure that all steps on a circuit are using the
11338 strongest crypto possible, strengthens some TLS properties, and
11339 resolves several bugs -- including a pair of crash bugs from the 0.2.8
11340 series. Anybody running an earlier version of 0.2.9.x should upgrade.
11342 o Major bugfixes (crash, also in 0.2.8.8):
11343 - Fix a complicated crash bug that could affect Tor clients
11344 configured to use bridges when replacing a networkstatus consensus
11345 in which one of their bridges was mentioned. OpenBSD users saw
11346 more crashes here, but all platforms were potentially affected.
11347 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11349 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
11350 - Fix a timing-dependent assertion failure that could occur when we
11351 tried to flush from a circuit after having freed its cells because
11352 of an out-of-memory condition. Fixes bug 20203; bugfix on
11353 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11356 o Major features (circuit building, security):
11357 - Authorities, relays and clients now require ntor keys in all
11358 descriptors, for all hops (except for rare hidden service protocol
11359 cases), for all circuits, and for all other roles. Part of
11361 - Tor authorities, relays, and clients only use ntor, except for
11362 rare cases in the hidden service protocol. Part of ticket 19163.
11364 o Major features (single-hop "hidden" services):
11365 - Add experimental HiddenServiceSingleHopMode and
11366 HiddenServiceNonAnonymousMode options. When both are set to 1,
11367 every hidden service on a Tor instance becomes a non-anonymous
11368 Single Onion Service. Single Onions make one-hop (direct)
11369 connections to their introduction and renzedvous points. One-hop
11370 circuits make Single Onion servers easily locatable, but clients
11371 remain location-anonymous. This is compatible with the existing
11372 hidden service implementation, and works on the current tor
11373 network without any changes to older relays or clients. Implements
11374 proposal 260, completes ticket 17178. Patch by teor and asn.
11376 o Major features (resource management):
11377 - Tor can now notice it is about to run out of sockets, and
11378 preemptively close connections of lower priority. (This feature is
11379 off by default for now, since the current prioritizing method is
11380 yet not mature enough. You can enable it by setting
11381 "DisableOOSCheck 0", but watch out: it might close some sockets
11382 you would rather have it keep.) Closes ticket 18640.
11384 o Major bugfixes (circuit building):
11385 - Hidden service client-to-intro-point and service-to-rendezvous-
11386 point circuits use the TAP key supplied by the protocol, to avoid
11387 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
11389 o Major bugfixes (compilation, OpenBSD):
11390 - Fix a Libevent-detection bug in our autoconf script that would
11391 prevent Tor from linking successfully on OpenBSD. Patch from
11392 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
11394 o Major bugfixes (hidden services):
11395 - Clients now require hidden services to include the TAP keys for
11396 their intro points in the hidden service descriptor. This prevents
11397 an inadvertent upgrade to ntor, which a malicious hidden service
11398 could use to distinguish clients by consensus version. Fixes bug
11399 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
11401 o Minor features (security, TLS):
11402 - Servers no longer support clients that without AES ciphersuites.
11403 (3DES is no longer considered an acceptable cipher.) We believe
11404 that no such Tor clients currently exist, since Tor has required
11405 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
11407 o Minor feature (fallback directories):
11408 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11409 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11410 2016. Closes ticket 20190; patch by teor.
11412 o Minor features (geoip, also in 0.2.8.8):
11413 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11416 o Minor feature (port flags):
11417 - Add new flags to the *Port options to finer control over which
11418 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
11419 and the synthetic flag OnionTrafficOnly, which is equivalent to
11420 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
11421 18693; patch by "teor".
11423 o Minor features (directory authority):
11424 - After voting, if the authorities decide that a relay is not
11425 "Valid", they no longer include it in the consensus at all. Closes
11426 ticket 20002; implements part of proposal 272.
11428 o Minor features (testing):
11429 - Disable memory protections on OpenBSD when performing our unit
11430 tests for memwipe(). The test deliberately invokes undefined
11431 behavior, and the OpenBSD protections interfere with this. Patch
11432 from "rubiate". Closes ticket 20066.
11434 o Minor features (testing, ipv6):
11435 - Add the single-onion and single-onion-ipv6 chutney targets to
11436 "make test-network-all". This requires a recent chutney version
11437 with the single onion network flavours (git c72a652 or later).
11438 Closes ticket 20072; patch by teor.
11439 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
11440 tests. Remove bridges+hs, as it's somewhat redundant. This
11441 requires a recent chutney version that supports IPv6 clients,
11442 relays, and authorities. Closes ticket 20069; patch by teor.
11444 o Minor features (Tor2web):
11445 - Make Tor2web clients respect ReachableAddresses. This feature was
11446 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
11447 0.2.8.7. Implements feature 20034. Patch by teor.
11449 o Minor features (unit tests):
11450 - We've done significant work to make the unit tests run faster.
11451 - Our link-handshake unit tests now check that when invalid
11452 handshakes fail, they fail with the error messages we expected.
11453 - Our unit testing code that captures log messages no longer
11454 prevents them from being written out if the user asked for them
11455 (by passing --debug or --info or or --notice --warn to the "test"
11456 binary). This change prevents us from missing unexpected log
11457 messages simply because we were looking for others. Related to
11459 - The unit tests now log all warning messages with the "BUG" flag.
11460 Previously, they only logged errors by default. This change will
11461 help us make our testing code more correct, and make sure that we
11462 only hit this code when we mean to. In the meantime, however,
11463 there will be more warnings in the unit test logs than before.
11464 This is preparatory work for ticket 19999.
11465 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
11466 assertion as a test failure.
11468 o Minor bug fixes (circuits):
11469 - Use the CircuitBuildTimeout option whenever
11470 LearnCircuitBuildTimeout is disabled. Previously, we would respect
11471 the option when a user disabled it, but not when it was disabled
11472 because some other option was set. Fixes bug 20073; bugfix on
11473 0.2.4.12-alpha. Patch by teor.
11475 o Minor bugfixes (allocation):
11476 - Change how we allocate memory for large chunks on buffers, to
11477 avoid a (currently impossible) integer overflow, and to waste less
11478 space when allocating unusually large chunks. Fixes bug 20081;
11479 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
11480 - Always include orconfig.h before including any other C headers.
11481 Sometimes, it includes macros that affect the behavior of the
11482 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
11483 first version to use AC_USE_SYSTEM_EXTENSIONS).
11484 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
11485 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
11486 Patch from Gisle Vanem.
11487 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
11488 They apparently require a set of annotations that we aren't
11489 currently using, and they create false positives in our pthreads
11490 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
11492 o Minor bugfixes (directory authority):
11493 - Die with a more useful error when the operator forgets to place
11494 the authority_signing_key file into the keys directory. This
11495 avoids an uninformative assert & traceback about having an invalid
11496 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
11497 - When allowing private addresses, mark Exits that only exit to
11498 private locations as such. Fixes bug 20064; bugfix
11501 o Minor bugfixes (documentation):
11502 - Document the default PathsNeededToBuildCircuits value that's used
11503 by clients when the directory authorities don't set
11504 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
11505 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
11506 - Fix manual for the User option: it takes a username, not a UID.
11507 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
11510 o Minor bugfixes (hidden services):
11511 - Stop logging intro point details to the client log on certain
11512 error conditions. Fixed as part of bug 20012; bugfix on
11513 0.2.4.8-alpha. Patch by teor.
11515 o Minor bugfixes (IPv6, testing):
11516 - Check for IPv6 correctly on Linux when running test networks.
11517 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
11519 o Minor bugfixes (Linux seccomp2 sandbox):
11520 - Add permission to run the sched_yield() and sigaltstack() system
11521 calls, in order to support versions of Tor compiled with asan or
11522 ubsan code that use these calls. Now "sandbox 1" and
11523 "--enable-expensive-hardening" should be compatible on more
11524 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
11526 o Minor bugfixes (logging):
11527 - When logging a message from the BUG() macro, be explicit about
11528 what we were asserting. Previously we were confusing what we were
11529 asserting with what the bug was. Fixes bug 20093; bugfix
11531 - When we are unable to remove the bw_accounting file, do not warn
11532 if the reason we couldn't remove it was that it didn't exist.
11533 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
11535 o Minor bugfixes (option parsing):
11536 - Count unix sockets when counting client listeners (SOCKS, Trans,
11537 NATD, and DNS). This has no user-visible behaviour changes: these
11538 options are set once, and never read. Required for correct
11539 behaviour in ticket 17178. Fixes bug 19677; bugfix on
11540 0.2.6.3-alpha. Patch by teor.
11542 o Minor bugfixes (options):
11543 - Check the consistency of UseEntryGuards and EntryNodes more
11544 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
11546 - Stop changing the configured value of UseEntryGuards on
11547 authorities and Tor2web clients. Fixes bug 20074; bugfix on
11548 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
11551 o Minor bugfixes (Tor2web):
11552 - Prevent Tor2web clients running hidden services, these services
11553 are not anonymous due to the one-hop client paths. Fixes bug
11554 19678. Patch by teor.
11556 o Minor bugfixes (unit tests):
11557 - Fix a shared-random unit test that was failing on big endian
11558 architectures due to internal representation of a integer copied
11559 to a buffer. The test is changed to take a full 32 bytes of data
11560 and use the output of a python script that make the COMMIT and
11561 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
11563 - The tor_tls_server_info_callback unit test no longer crashes when
11564 debug-level logging is turned on. Fixes bug 20041; bugfix
11568 Changes in version 0.2.8.8 - 2016-09-23
11569 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
11570 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
11571 who select public relays as their bridges.
11573 o Major bugfixes (crash):
11574 - Fix a complicated crash bug that could affect Tor clients
11575 configured to use bridges when replacing a networkstatus consensus
11576 in which one of their bridges was mentioned. OpenBSD users saw
11577 more crashes here, but all platforms were potentially affected.
11578 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
11580 o Major bugfixes (relay, OOM handler):
11581 - Fix a timing-dependent assertion failure that could occur when we
11582 tried to flush from a circuit after having freed its cells because
11583 of an out-of-memory condition. Fixes bug 20203; bugfix on
11584 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
11587 o Minor feature (fallback directories):
11588 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
11589 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
11590 2016. Closes ticket 20190; patch by teor.
11592 o Minor features (geoip):
11593 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
11597 Changes in version 0.2.9.2-alpha - 2016-08-24
11598 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
11599 several new features and bugfixes. It also includes an important
11600 authority update and an important bugfix from 0.2.8.7. Everyone who
11601 sets the ReachableAddresses option, and all bridges, are strongly
11602 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
11604 o Directory authority changes (also in 0.2.8.7):
11605 - The "Tonga" bridge authority has been retired; the new bridge
11606 authority is "Bifroest". Closes tickets 19728 and 19690.
11608 o Major bugfixes (client, security, also in 0.2.8.7):
11609 - Only use the ReachableAddresses option to restrict the first hop
11610 in a path. In earlier versions of 0.2.8.x, it would apply to
11611 every hop in the path, with a possible degradation in anonymity
11612 for anyone using an uncommon ReachableAddress setting. Fixes bug
11613 19973; bugfix on 0.2.8.2-alpha.
11615 o Major features (user interface):
11616 - Tor now supports the ability to declare options deprecated, so
11617 that we can recommend that people stop using them. Previously,
11618 this was done in an ad-hoc way. Closes ticket 19820.
11620 o Major bugfixes (directory downloads):
11621 - Avoid resetting download status for consensuses hourly, since we
11622 already have another, smarter retry mechanism. Fixes bug 8625;
11623 bugfix on 0.2.0.9-alpha.
11625 o Minor features (config):
11626 - Warn users when descriptor and port addresses are inconsistent.
11627 Mitigates bug 13953; patch by teor.
11629 o Minor features (geoip):
11630 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11633 o Minor features (user interface):
11634 - There is a new --list-deprecated-options command-line option to
11635 list all of the deprecated options. Implemented as part of
11638 o Minor bugfixes (code style):
11639 - Fix an integer signedness conversion issue in the case conversion
11640 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
11642 o Minor bugfixes (compilation):
11643 - Build correctly on versions of libevent2 without support for
11644 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
11646 - Fix a compilation warning on GCC versions before 4.6. Our
11647 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
11648 when it is also required as an argument to the compiler pragma.
11649 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
11651 o Minor bugfixes (compilation, also in 0.2.8.7):
11652 - Remove an inappropriate "inline" in tortls.c that was causing
11653 warnings on older versions of GCC. Fixes bug 19903; bugfix
11656 o Minor bugfixes (fallback directories, also in 0.2.8.7):
11657 - Avoid logging a NULL string pointer when loading fallback
11658 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11659 and 0.2.8.1-alpha. Report and patch by "rubiate".
11661 o Minor bugfixes (logging):
11662 - Log a more accurate message when we fail to dump a microdescriptor.
11663 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
11665 o Minor bugfixes (memory leak):
11666 - Fix a series of slow memory leaks related to parsing torrc files
11667 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
11669 o Deprecated features:
11670 - A number of DNS-cache-related sub-options for client ports are now
11671 deprecated for security reasons, and may be removed in a future
11672 version of Tor. (We believe that client-side DNS caching is a bad
11673 idea for anonymity, and you should not turn it on.) The options
11674 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
11675 UseIPv4Cache, and UseIPv6Cache.
11676 - A number of options are deprecated for security reasons, and may
11677 be removed in a future version of Tor. The options are:
11678 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
11679 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
11680 CloseHSClientCircuitsImmediatelyOnTimeout,
11681 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
11682 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
11683 UseNTorHandshake, and WarnUnsafeSocks.
11684 - The *ListenAddress options are now deprecated as unnecessary: the
11685 corresponding *Port options should be used instead. These options
11686 may someday be removed. The affected options are:
11687 ControlListenAddress, DNSListenAddress, DirListenAddress,
11688 NATDListenAddress, ORListenAddress, SocksListenAddress,
11689 and TransListenAddress.
11692 - Correct the IPv6 syntax in our documentation for the
11693 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
11696 - We no longer include the (dead, deprecated) bufferevent code in
11697 Tor. Closes ticket 19450. Based on a patch from U+039b.
11700 Changes in version 0.2.8.7 - 2016-08-24
11701 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
11702 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
11703 who sets the ReachableAddresses option, and all bridges, are strongly
11704 encouraged to upgrade.
11706 o Directory authority changes:
11707 - The "Tonga" bridge authority has been retired; the new bridge
11708 authority is "Bifroest". Closes tickets 19728 and 19690.
11710 o Major bugfixes (client, security):
11711 - Only use the ReachableAddresses option to restrict the first hop
11712 in a path. In earlier versions of 0.2.8.x, it would apply to
11713 every hop in the path, with a possible degradation in anonymity
11714 for anyone using an uncommon ReachableAddress setting. Fixes bug
11715 19973; bugfix on 0.2.8.2-alpha.
11717 o Minor features (geoip):
11718 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
11721 o Minor bugfixes (compilation):
11722 - Remove an inappropriate "inline" in tortls.c that was causing
11723 warnings on older versions of GCC. Fixes bug 19903; bugfix
11726 o Minor bugfixes (fallback directories):
11727 - Avoid logging a NULL string pointer when loading fallback
11728 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
11729 and 0.2.8.1-alpha. Report and patch by "rubiate".
11732 Changes in version 0.2.9.1-alpha - 2016-08-08
11733 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
11734 series. It improves our support for hardened builds and compiler
11735 warnings, deploys some critical infrastructure for improvements to
11736 hidden services, includes a new timing backend that we hope to use for
11737 better support for traffic padding, makes it easier for programmers to
11738 log unexpected events, and contains other small improvements to
11739 security, correctness, and performance.
11741 Below are the changes since 0.2.8.6.
11743 o New system requirements:
11744 - Tor now requires Libevent version 2.0.10-stable or later. Older
11745 versions of Libevent have less efficient backends for several
11746 platforms, and lack the DNS code that we use for our server-side
11747 DNS support. This implements ticket 19554.
11748 - Tor now requires zlib version 1.2 or later, for security,
11749 efficiency, and (eventually) gzip support. (Back when we started,
11750 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
11751 released in 2003. We recommend the latest version.)
11753 o Major features (build, hardening):
11754 - Tor now builds with -ftrapv by default on compilers that support
11755 it. This option detects signed integer overflow (which C forbids),
11756 and turns it into a hard-failure. We do not apply this option to
11757 code that needs to run in constant time to avoid side-channels;
11758 instead, we use -fwrapv in that code. Closes ticket 17983.
11759 - When --enable-expensive-hardening is selected, stop applying the
11760 clang/gcc sanitizers to code that needs to run in constant time.
11761 Although we are aware of no introduced side-channels, we are not
11762 able to prove that there are none. Related to ticket 17983.
11764 o Major features (compilation):
11765 - Our big list of extra GCC warnings is now enabled by default when
11766 building with GCC (or with anything like Clang that claims to be
11767 GCC-compatible). To make all warnings into fatal compilation
11768 errors, pass --enable-fatal-warnings to configure. Closes
11770 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
11771 turn on C and POSIX extensions. (Previously, we attempted to do
11772 this on an ad hoc basis.) Closes ticket 19139.
11774 o Major features (directory authorities, hidden services):
11775 - Directory authorities can now perform the shared randomness
11776 protocol specified by proposal 250. Using this protocol, directory
11777 authorities generate a global fresh random value every day. In the
11778 future, this value will be used by hidden services to select
11779 HSDirs. This release implements the directory authority feature;
11780 the hidden service side will be implemented in the future as part
11781 of proposal 224. Resolves ticket 16943; implements proposal 250.
11783 o Major features (downloading, random exponential backoff):
11784 - When we fail to download an object from a directory service, wait
11785 for an (exponentially increasing) randomized amount of time before
11786 retrying, rather than a fixed interval as we did before. This
11787 prevents a group of Tor instances from becoming too synchronized,
11788 or a single Tor instance from becoming too predictable, in its
11789 download schedule. Closes ticket 15942.
11791 o Major bugfixes (exit policies):
11792 - Avoid disclosing exit outbound bind addresses, configured port
11793 bind addresses, and local interface addresses in relay descriptors
11794 by default under ExitPolicyRejectPrivate. Instead, only reject
11795 these (otherwise unlisted) addresses if
11796 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
11797 0.2.7.2-alpha. Patch by teor.
11799 o Major bugfixes (hidden service client):
11800 - Allow Tor clients with appropriate controllers to work with
11801 FetchHidServDescriptors set to 0. Previously, this option also
11802 disabled descriptor cache lookup, thus breaking hidden services
11803 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
11805 o Minor features (build, hardening):
11806 - Detect and work around a libclang_rt problem that would prevent
11807 clang from finding __mulodi4() on some 32-bit platforms, and thus
11808 keep -ftrapv from linking on those systems. Closes ticket 19079.
11809 - When building on a system without runtime support for the runtime
11810 hardening options, try to log a useful warning at configuration
11811 time, rather than an incomprehensible warning at link time. If
11812 expensive hardening was requested, this warning becomes an error.
11813 Closes ticket 18895.
11815 o Minor features (code safety):
11816 - In our integer-parsing functions, ensure that maxiumum value we
11817 give is no smaller than the minimum value. Closes ticket 19063;
11820 o Minor features (controller):
11821 - Implement new GETINFO queries for all downloads that use
11822 download_status_t to schedule retries. This allows controllers to
11823 examine the schedule for pending downloads. Closes ticket 19323.
11824 - Allow controllers to configure basic client authorization on
11825 hidden services when they create them with the ADD_ONION control
11826 command. Implements ticket 15588. Patch by "special".
11827 - Fire a STATUS_SERVER controller event whenever the hibernation
11828 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
11830 o Minor features (directory authority):
11831 - Directory authorities now only give the Guard flag to a relay if
11832 they are also giving it the Stable flag. This change allows us to
11833 simplify path selection for clients. It should have minimal effect
11834 in practice, since >99% of Guards already have the Stable flag.
11835 Implements ticket 18624.
11836 - Directory authorities now write their v3-status-votes file out to
11837 disk earlier in the consensus process, so we have a record of the
11838 votes even if we abort the consensus process. Resolves
11841 o Minor features (hidden service):
11842 - Stop being so strict about the payload length of "rendezvous1"
11843 cells. We used to be locked in to the "TAP" handshake length, and
11844 now we can handle better handshakes like "ntor". Resolves
11847 o Minor features (infrastructure, time):
11848 - Tor now uses the operating system's monotonic timers (where
11849 available) for internal fine-grained timing. Previously we would
11850 look at the system clock, and then attempt to compensate for the
11851 clock running backwards. Closes ticket 18908.
11852 - Tor now includes an improved timer backend, so that we can
11853 efficiently support tens or hundreds of thousands of concurrent
11854 timers, as will be needed for some of our planned anti-traffic-
11855 analysis work. This code is based on William Ahern's "timeout.c"
11856 project, which implements a "tickless hierarchical timing wheel".
11857 Closes ticket 18365.
11859 o Minor features (logging):
11860 - Provide a more useful warning message when configured with an
11861 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
11862 - When dumping unparseable router descriptors, optionally store them
11863 in separate files, named by digest, up to a configurable size
11864 limit. You can change the size limit by setting the
11865 MaxUnparseableDescSizeToLog option, and disable this feature by
11866 setting that option to 0. Closes ticket 18322.
11867 - Add a set of macros to check nonfatal assertions, for internal
11868 use. Migrating more of our checks to these should help us avoid
11869 needless crash bugs. Closes ticket 18613.
11871 o Minor features (performance):
11872 - Changer the "optimistic data" extension from "off by default" to
11873 "on by default". The default was ordinarily overridden by a
11874 consensus option, but when clients were bootstrapping for the
11875 first time, they would not have a consensus to get the option
11876 from. Changing this default When fetching a consensus for the
11877 first time, use optimistic data. This saves a round-trip during
11878 startup. Closes ticket 18815.
11880 o Minor features (relay, usability):
11881 - When the directory authorities refuse a bad relay's descriptor,
11882 encourage the relay operator to contact us. Many relay operators
11883 won't notice this line in their logs, but it's a win if even a few
11884 learn why we don't like what their relay was doing. Resolves
11887 o Minor features (testing):
11888 - Let backtrace tests work correctly under AddressSanitizer. Fixes
11889 part of bug 18934; bugfix on 0.2.5.2-alpha.
11890 - Move the test-network.sh script to chutney, and modify tor's test-
11891 network.sh to call the (newer) chutney version when available.
11892 Resolves ticket 19116. Patch by teor.
11893 - Use the lcov convention for marking lines as unreachable, so that
11894 we don't count them when we're generating test coverage data.
11895 Update our coverage tools to understand this convention. Closes
11898 o Minor bugfixes (bootstrap):
11899 - Remember the directory we fetched the consensus or previous
11900 certificates from, and use it to fetch future authority
11901 certificates. This change improves bootstrapping performance.
11902 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
11904 o Minor bugfixes (build):
11905 - The test-stem and test-network makefile targets now depend only on
11906 the tor binary that they are testing. Previously, they depended on
11907 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
11908 patch from "cypherpunks".
11910 o Minor bugfixes (circuits):
11911 - Make sure extend_info_from_router() is only called on servers.
11912 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
11914 o Minor bugfixes (compilation):
11915 - When building with Clang, use a full set of GCC warnings.
11916 (Previously, we included only a subset, because of the way we
11917 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
11919 o Minor bugfixes (directory authority):
11920 - Authorities now sort the "package" lines in their votes, for ease
11921 of debugging. (They are already sorted in consensus documents.)
11922 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
11923 - When parsing a detached signature, make sure we use the length of
11924 the digest algorithm instead of an hardcoded DIGEST256_LEN in
11925 order to avoid comparing bytes out-of-bounds with a smaller digest
11926 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
11928 o Minor bugfixes (documentation):
11929 - Document the --passphrase-fd option in the tor manpage. Fixes bug
11930 19504; bugfix on 0.2.7.3-rc.
11931 - Fix the description of the --passphrase-fd option in the
11932 tor-gencert manpage. The option is used to pass the number of a
11933 file descriptor to read the passphrase from, not to read the file
11934 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
11936 o Minor bugfixes (ephemeral hidden service):
11937 - When deleting an ephemeral hidden service, close its intro points
11938 even if they are not completely open. Fixes bug 18604; bugfix
11941 o Minor bugfixes (guard selection):
11942 - Use a single entry guard even if the NumEntryGuards consensus
11943 parameter is not provided. Fixes bug 17688; bugfix
11945 - Don't mark guards as unreachable if connection_connect() fails.
11946 That function fails for local reasons, so it shouldn't reveal
11947 anything about the status of the guard. Fixes bug 14334; bugfix
11950 o Minor bugfixes (hidden service client):
11951 - Increase the minimum number of internal circuits we preemptively
11952 build from 2 to 3, so a circuit is available when a client
11953 connects to another onion service. Fixes bug 13239; bugfix
11956 o Minor bugfixes (logging):
11957 - When logging a directory ownership mismatch, log the owning
11958 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
11960 o Minor bugfixes (memory leaks):
11961 - Fix a small, uncommon memory leak that could occur when reading a
11962 truncated ed25519 key file. Fixes bug 18956; bugfix
11965 o Minor bugfixes (testing):
11966 - Allow clients to retry HSDirs much faster in test networks. Fixes
11967 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
11968 - Disable ASAN's detection of segmentation faults while running
11969 test_bt.sh, so that we can make sure that our own backtrace
11970 generation code works. Fixes another aspect of bug 18934; bugfix
11971 on 0.2.5.2-alpha. Patch from "cypherpunks".
11972 - Fix the test-network-all target on out-of-tree builds by using the
11973 correct path to the test driver script. Fixes bug 19421; bugfix
11976 o Minor bugfixes (time):
11977 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
11978 bugfix on all released tor versions.
11979 - When computing the difference between two times in milliseconds,
11980 we now round to the nearest millisecond correctly. Previously, we
11981 could sometimes round in the wrong direction. Fixes bug 19428;
11982 bugfix on 0.2.2.2-alpha.
11984 o Minor bugfixes (user interface):
11985 - Display a more accurate number of suppressed messages in the log
11986 rate-limiter. Previously, there was a potential integer overflow
11987 in the counter. Now, if the number of messages hits a maximum, the
11988 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
11990 - Fix a typo in the passphrase prompt for the ed25519 identity key.
11991 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
11993 o Code simplification and refactoring:
11994 - Remove redundant declarations of the MIN macro. Closes
11996 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
11997 Closes ticket 18462; patch from "icanhasaccount".
11998 - Split the 600-line directory_handle_command_get function into
11999 separate functions for different URL types. Closes ticket 16698.
12002 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
12003 ticket 19153. Patch from "U+039b".
12005 o Removed features:
12006 - Remove support for "GET /tor/bytes.txt" DirPort request, and
12007 "GETINFO dir-usage" controller request, which were only available
12008 via a compile-time option in Tor anyway. Feature was added in
12009 0.2.2.1-alpha. Resolves ticket 19035.
12010 - There is no longer a compile-time option to disable support for
12011 TransPort. (If you don't want TransPort; just don't use it.) Patch
12012 from "U+039b". Closes ticket 19449.
12015 - Run more workqueue tests as part of "make check". These had
12016 previously been implemented, but you needed to know special
12017 command-line options to enable them.
12018 - We now have unit tests for our code to reject zlib "compression
12019 bombs". (Fortunately, the code works fine.)
12022 Changes in version 0.2.8.6 - 2016-08-02
12024 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
12026 The Tor 0.2.8 series improves client bootstrapping performance,
12027 completes the authority-side implementation of improved identity
12028 keys for relays, and includes numerous bugfixes and performance
12029 improvements throughout the program. This release continues to
12030 improve the coverage of Tor's test suite. For a full list of
12031 changes since Tor 0.2.7, see the ReleaseNotes file.
12033 Changes since 0.2.8.5-rc:
12035 o Minor features (geoip):
12036 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
12039 o Minor bugfixes (compilation):
12040 - Fix a compilation warning in the unit tests on systems where char
12041 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
12043 o Minor bugfixes (fallback directories):
12044 - Remove 1 fallback that was on the hardcoded list, then opted-out,
12045 leaving 89 of the 100 fallbacks originally introduced in Tor
12046 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
12048 o Minor bugfixes (Linux seccomp2 sandbox):
12049 - Allow more syscalls when running with "Sandbox 1" enabled:
12050 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
12051 some systems, these are required for Tor to start. Fixes bug
12052 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
12053 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
12054 so that get_interface_address6_via_udp_socket_hack() can work.
12055 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
12058 Changes in version 0.2.8.5-rc - 2016-07-07
12059 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
12060 series. If we find no new bugs or regressions here, the first stable
12061 0.2.8 release will be identical to it. It has a few small bugfixes
12062 against previous versions.
12064 o Directory authority changes:
12065 - Urras is no longer a directory authority. Closes ticket 19271.
12067 o Major bugfixes (heartbeat):
12068 - Fix a regression that would crash Tor when the periodic
12069 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
12070 0.2.8.1-alpha. Reported by "kubaku".
12072 o Minor features (build):
12073 - Tor now again builds with the recent OpenSSL 1.1 development
12074 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
12075 - When building manual pages, set the timezone to "UTC", so that the
12076 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
12077 Patch from intrigeri.
12079 o Minor bugfixes (fallback directory selection):
12080 - Avoid errors during fallback selection if there are no eligible
12081 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
12084 o Minor bugfixes (IPv6, microdescriptors):
12085 - Don't check node addresses when we only have a routerstatus. This
12086 allows IPv6-only clients to bootstrap by fetching microdescriptors
12087 from fallback directory mirrors. (The microdescriptor consensus
12088 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
12091 o Minor bugfixes (logging):
12092 - Reduce pointlessly verbose log messages when directory servers
12093 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
12094 0.2.8.1-alpha. Patch by teor.
12095 - When a fallback directory changes its fingerprint from the hard-
12096 coded fingerprint, log a less severe, more explanatory log
12097 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
12099 o Minor bugfixes (Linux seccomp2 sandboxing):
12100 - Allow statistics to be written to disk when "Sandbox 1" is
12101 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
12102 0.2.6.1-alpha respectively.
12104 o Minor bugfixes (user interface):
12105 - Remove a warning message "Service [scrubbed] not found after
12106 descriptor upload". This message appears when one uses HSPOST
12107 control command to upload a service descriptor. Since there is
12108 only a descriptor and no service, showing this message is
12109 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
12111 o Fallback directory list:
12112 - Add a comment to the generated fallback directory list that
12113 explains how to comment out unsuitable fallbacks in a way that's
12114 compatible with the stem fallback parser.
12115 - Update fallback whitelist and blacklist based on relay operator
12116 emails. Blacklist unsuitable (non-working, over-volatile)
12117 fallbacks. Resolves ticket 19071. Patch by teor.
12118 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
12119 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
12120 ticket 19071; patch by teor.
12123 Changes in version 0.2.8.4-rc - 2016-06-15
12124 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
12125 If we find no new bugs or regressions here, the first stable 0.2.8
12126 release will be identical to it. It has a few small bugfixes against
12129 o Major bugfixes (user interface):
12130 - Correctly give a warning in the cases where a relay is specified
12131 by nickname, and one such relay is found, but it is not officially
12132 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
12134 o Minor features (build):
12135 - Tor now builds once again with the recent OpenSSL 1.1 development
12136 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
12138 o Minor features (geoip):
12139 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
12142 o Minor bugfixes (compilation):
12143 - Cause the unit tests to compile correctly on mingw64 versions that
12144 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
12146 o Minor bugfixes (downloading):
12147 - Predict more correctly whether we'll be downloading over HTTP when
12148 we determine the maximum length of a URL. This should avoid a
12149 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
12153 Changes in version 0.2.8.3-alpha - 2016-05-26
12154 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
12155 the course of the 0.2.8 development cycle. It improves the behavior of
12156 directory clients, fixes several crash bugs, fixes a gap in compiler
12157 hardening, and allows the full integration test suite to run on
12160 o Major bugfixes (security, client, DNS proxy):
12161 - Stop a crash that could occur when a client running with DNSPort
12162 received a query with multiple address types, and the first
12163 address type was not supported. Found and fixed by Scott Dial.
12164 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
12166 o Major bugfixes (security, compilation):
12167 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
12168 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
12169 cause a compiler warning, thereby making other checks fail, and
12170 needlessly disabling compiler-hardening support. Fixes one case of
12171 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
12173 o Major bugfixes (security, directory authorities):
12174 - Fix a crash and out-of-bounds write during authority voting, when
12175 the list of relays includes duplicate ed25519 identity keys. Fixes
12176 bug 19032; bugfix on 0.2.8.2-alpha.
12178 o Major bugfixes (client, bootstrapping):
12179 - Check if bootstrap consensus downloads are still needed when the
12180 linked connection attaches. This prevents tor making unnecessary
12181 begindir-style connections, which are the only directory
12182 connections tor clients make since the fix for 18483 was merged.
12183 - Fix some edge cases where consensus download connections may not
12184 have been closed, even though they were not needed. Related to fix
12186 - Make relays retry consensus downloads the correct number of times,
12187 rather than the more aggressive client retry count. Fixes part of
12189 - Stop downloading consensuses when we have a consensus, even if we
12190 don't have all the certificates for it yet. Fixes bug 18809;
12191 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
12193 o Major bugfixes (directory mirrors):
12194 - Decide whether to advertise begindir support in the the same way
12195 we decide whether to advertise our DirPort. Allowing these
12196 decisions to become out-of-sync led to surprising behavior like
12197 advertising begindir support when hibernation made us not
12198 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
12201 o Major bugfixes (IPv6 bridges, client):
12202 - Actually use IPv6 addresses when selecting directory addresses for
12203 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
12206 o Major bugfixes (key management):
12207 - If OpenSSL fails to generate an RSA key, do not retain a dangling
12208 pointer to the previous (uninitialized) key value. The impact here
12209 should be limited to a difficult-to-trigger crash, if OpenSSL is
12210 running an engine that makes key generation failures possible, or
12211 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
12212 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
12215 o Major bugfixes (testing):
12216 - Fix a bug that would block 'make test-network-all' on systems where
12217 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
12218 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
12219 bugfix on 0.2.8.1-alpha.
12221 o Minor features (clients):
12222 - Make clients, onion services, and bridge relays always use an
12223 encrypted begindir connection for directory requests. Resolves
12224 ticket 18483. Patch by "teor".
12226 o Minor features (fallback directory mirrors):
12227 - Give each fallback the same weight for client selection; restrict
12228 fallbacks to one per operator; report fallback directory detail
12229 changes when rebuilding list; add new fallback directory mirrors
12230 to the whitelist; and many other minor simplifications and fixes.
12231 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
12232 0.2.8.1-alpha; patch by "teor".
12233 - Replace the 21 fallbacks generated in January 2016 and included in
12234 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
12235 2016. Closes task 17158; patch by "teor".
12237 o Minor features (geoip):
12238 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
12241 o Minor bugfixes (assert, portability):
12242 - Fix an assertion failure in memarea.c on systems where "long" is
12243 shorter than the size of a pointer. Fixes bug 18716; bugfix
12246 o Minor bugfixes (bootstrap):
12247 - Consistently use the consensus download schedule for authority
12248 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
12250 o Minor bugfixes (build):
12251 - Remove a pair of redundant AM_CONDITIONAL declarations from
12252 configure.ac. Fixes one final case of bug 17744; bugfix
12254 - Resolve warnings when building on systems that are concerned with
12255 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
12257 - When libscrypt.h is found, but no libscrypt library can be linked,
12258 treat libscrypt as absent. Fixes bug 19161; bugfix
12261 o Minor bugfixes (client):
12262 - Turn all TestingClientBootstrap* into non-testing torrc options.
12263 This changes simply renames them by removing "Testing" in front of
12264 them and they do not require TestingTorNetwork to be enabled
12265 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
12266 - Make directory node selection more reliable, mainly for IPv6-only
12267 clients and clients with few reachable addresses. Fixes bug 18929;
12268 bugfix on 0.2.8.1-alpha. Patch by "teor".
12270 o Minor bugfixes (controller, microdescriptors):
12271 - Make GETINFO dir/status-vote/current/consensus conform to the
12272 control specification by returning "551 Could not open cached
12273 consensus..." when not caching consensuses. Fixes bug 18920;
12274 bugfix on 0.2.2.6-alpha.
12276 o Minor bugfixes (crypto, portability):
12277 - The SHA3 and SHAKE routines now produce the correct output on Big
12278 Endian systems. No code calls either algorithm yet, so this is
12279 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
12280 - Tor now builds again with the recent OpenSSL 1.1 development
12281 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
12284 o Minor bugfixes (directories):
12285 - When fetching extrainfo documents, compare their SHA256 digests
12286 and Ed25519 signing key certificates with the routerinfo that led
12287 us to fetch them, rather than with the most recent routerinfo.
12288 Otherwise we generate many spurious warnings about mismatches.
12289 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
12291 o Minor bugfixes (logging):
12292 - When we can't generate a signing key because OfflineMasterKey is
12293 set, do not imply that we should have been able to load it. Fixes
12294 bug 18133; bugfix on 0.2.7.2-alpha.
12295 - Stop periodic_event_dispatch() from blasting twelve lines per
12296 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
12297 - When rejecting a misformed INTRODUCE2 cell, only log at
12298 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
12300 o Minor bugfixes (pluggable transports):
12301 - Avoid reporting a spurious error when we decide that we don't need
12302 to terminate a pluggable transport because it has already exited.
12303 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
12305 o Minor bugfixes (pointer arithmetic):
12306 - Fix a bug in memarea_alloc() that could have resulted in remote
12307 heap write access, if Tor had ever passed an unchecked size to
12308 memarea_alloc(). Fortunately, all the sizes we pass to
12309 memarea_alloc() are pre-checked to be less than 128 kilobytes.
12310 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
12313 o Minor bugfixes (relays):
12314 - Consider more config options when relays decide whether to
12315 regenerate their descriptor. Fixes more of bug 12538; bugfix
12317 - Resolve some edge cases where we might launch an ORPort
12318 reachability check even when DisableNetwork is set. Noticed while
12319 fixing bug 18616; bugfix on 0.2.3.9-alpha.
12321 o Minor bugfixes (statistics):
12322 - We now include consensus downloads via IPv6 in our directory-
12323 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
12325 o Minor bugfixes (testing):
12326 - Allow directories in small networks to bootstrap by skipping
12327 DirPort checks when the consensus has no exits. Fixes bug 19003;
12328 bugfix on 0.2.8.1-alpha. Patch by teor.
12329 - Fix a small memory leak that would occur when the
12330 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
12331 bugfix on 0.2.5.2-alpha.
12333 o Minor bugfixes (time handling):
12334 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
12335 field. Otherwise, our unit tests crash on Windows. Fixes bug
12336 18977; bugfix on 0.2.2.25-alpha.
12339 - Document the contents of the 'datadir/keys' subdirectory in the
12340 manual page. Closes ticket 17621.
12341 - Stop recommending use of nicknames to identify relays in our
12342 MapAddress documentation. Closes ticket 18312.
12345 Changes in version 0.2.8.2-alpha - 2016-03-28
12346 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
12347 bugs in earlier versions of Tor, including some that prevented
12348 authorities using Tor 0.2.7.x from running correctly. IPv6 and
12349 directory support should also be much improved.
12351 o New system requirements:
12352 - Tor no longer supports versions of OpenSSL with a broken
12353 implementation of counter mode. (This bug was present in OpenSSL
12354 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
12355 longer runs with, these versions.
12356 - Tor no longer attempts to support platforms where the "time_t"
12357 type is unsigned. (To the best of our knowledge, only OpenVMS does
12358 this, and Tor has never actually built on OpenVMS.) Closes
12360 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
12361 later (released in 2008 and 2009 respectively). If you are
12362 building Tor from the git repository instead of from the source
12363 distribution, and your tools are older than this, you will need to
12364 upgrade. Closes ticket 17732.
12366 o Major bugfixes (security, pointers):
12367 - Avoid a difficult-to-trigger heap corruption attack when extending
12368 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
12369 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
12370 Reported by Guido Vranken.
12372 o Major bugfixes (bridges, pluggable transports):
12373 - Modify the check for OR connections to private addresses. Allow
12374 bridges on private addresses, including pluggable transports that
12375 ignore the (potentially private) address in the bridge line. Fixes
12376 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
12378 o Major bugfixes (compilation):
12379 - Repair hardened builds under the clang compiler. Previously, our
12380 use of _FORTIFY_SOURCE would conflict with clang's address
12381 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
12383 o Major bugfixes (crash on shutdown):
12384 - Correctly handle detaching circuits from muxes when shutting down.
12385 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
12386 - Fix an assert-on-exit bug related to counting memory usage in
12387 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
12389 o Major bugfixes (crash on startup):
12390 - Fix a segfault during startup: If a Unix domain socket was
12391 configured as listener (such as a ControlSocket or a SocksPort
12392 "unix:" socket), and tor was started as root but not configured to
12393 switch to another user, tor would segfault while trying to string
12394 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
12397 o Major bugfixes (dns proxy mode, crash):
12398 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
12399 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
12401 o Major bugfixes (relays, bridge clients):
12402 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
12403 bridge clients use the address configured in the bridge line.
12404 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
12407 o Major bugfixes (voting):
12408 - Actually enable support for authorities to match routers by their
12409 Ed25519 identities. Previously, the code had been written, but
12410 some debugging code that had accidentally been left in the
12411 codebase made it stay turned off. Fixes bug 17702; bugfix
12413 - When collating votes by Ed25519 identities, authorities now
12414 include a "NoEdConsensus" flag if the ed25519 value (or lack
12415 thereof) for a server does not reflect the majority consensus.
12416 Related to bug 17668; bugfix on 0.2.7.2-alpha.
12417 - When generating a vote with keypinning disabled, never include two
12418 entries for the same ed25519 identity. This bug was causing
12419 authorities to generate votes that they could not parse when a
12420 router violated key pinning by changing its RSA identity but
12421 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
12422 18318. Bugfix on 0.2.7.2-alpha.
12424 o Minor features (security, win32):
12425 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
12426 attack. Fixes bug 18123; bugfix on all tor versions. Patch
12429 o Minor features (bug-resistance):
12430 - Make Tor survive errors involving connections without a
12431 corresponding event object. Previously we'd fail with an
12432 assertion; now we produce a log message. Related to bug 16248.
12434 o Minor features (build):
12435 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
12436 as having possible IPFW support. Closes ticket 18448. Patch from
12437 Steven Chamberlain.
12439 o Minor features (code hardening):
12440 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
12441 level code, to harden against accidental failures to NUL-
12442 terminate. Part of ticket 17852. Patch from jsturgix. Found
12445 o Minor features (crypto):
12446 - Validate the hard-coded Diffie-Hellman parameters and ensure that
12447 p is a safe prime, and g is a suitable generator. Closes
12450 o Minor features (geoip):
12451 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
12454 o Minor features (hidden service directory):
12455 - Streamline relay-side hsdir handling: when relays consider whether
12456 to accept an uploaded hidden service descriptor, they no longer
12457 check whether they are one of the relays in the network that is
12458 "supposed" to handle that descriptor. Implements ticket 18332.
12460 o Minor features (IPv6):
12461 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
12462 to 1, tor prefers IPv6 directory addresses.
12463 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
12464 avoids using IPv4 for client OR and directory connections.
12465 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
12466 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
12467 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
12469 o Minor features (linux seccomp2 sandbox):
12470 - Reject attempts to change our Address with "Sandbox 1" enabled.
12471 Changing Address with Sandbox turned on would never actually work,
12472 but previously it would fail in strange and confusing ways. Found
12473 while fixing 18548.
12475 o Minor features (robustness):
12476 - Exit immediately with an error message if the code attempts to use
12477 Libevent without having initialized it. This should resolve some
12478 frequently-made mistakes in our unit tests. Closes ticket 18241.
12480 o Minor features (unix domain sockets):
12481 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
12482 Unix domain sockets without checking the permissions on the parent
12483 directory. (Tor checks permissions by default because some
12484 operating systems only check permissions on the parent directory.
12485 However, some operating systems do look at permissions on the
12486 socket, and tor's default check is unneeded.) Closes ticket 18458.
12489 o Minor bugfixes (exit policies, security):
12490 - Refresh an exit relay's exit policy when interface addresses
12491 change. Previously, tor only refreshed the exit policy when the
12492 configured external address changed. Fixes bug 18208; bugfix on
12493 0.2.7.3-rc. Patch by teor.
12495 o Minor bugfixes (security, hidden services):
12496 - Prevent hidden services connecting to client-supplied rendezvous
12497 addresses that are reserved as internal or multicast. Fixes bug
12498 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
12500 o Minor bugfixes (build):
12501 - Do not link the unit tests against both the testing and non-
12502 testing versions of the static libraries. Fixes bug 18490; bugfix
12504 - Avoid spurious failures from configure files related to calling
12505 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
12506 0.2.0.1-alpha. Patch from "cypherpunks".
12507 - Silence spurious clang-scan warnings in the ed25519_donna code by
12508 explicitly initializing some objects. Fixes bug 18384; bugfix on
12509 0.2.7.2-alpha. Patch by teor.
12511 o Minor bugfixes (client, bootstrap):
12512 - Count receipt of new microdescriptors as progress towards
12513 bootstrapping. Previously, with EntryNodes set, Tor might not
12514 successfully repopulate the guard set on bootstrapping. Fixes bug
12515 16825; bugfix on 0.2.3.1-alpha.
12517 o Minor bugfixes (code correctness):
12518 - Update to the latest version of Trunnel, which tries harder to
12519 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
12520 by clang address sanitizer. Fixes bug 18373; bugfix
12523 o Minor bugfixes (configuration):
12524 - Fix a tiny memory leak when parsing a port configuration ending in
12525 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
12527 o Minor bugfixes (containers):
12528 - If we somehow attempt to construct a heap with more than
12529 1073741822 elements, avoid an integer overflow when maintaining
12530 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
12532 o Minor bugfixes (correctness):
12533 - Fix a bad memory handling bug that would occur if we had queued a
12534 cell on a channel's incoming queue. Fortunately, we can't actually
12535 queue a cell like that as our code is constructed today, but it's
12536 best to avoid this kind of error, even if there isn't any code
12537 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
12539 o Minor bugfixes (directory):
12540 - When generating a URL for a directory server on an IPv6 address,
12541 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
12542 on 0.2.3.9-alpha. Patch from Malek.
12544 o Minor bugfixes (fallback directory mirrors):
12545 - When requesting extrainfo descriptors from a trusted directory
12546 server, check whether it is an authority or a fallback directory
12547 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
12548 0.2.4.7-alpha. Reported by atagar, patch by teor.
12550 o Minor bugfixes (hidden service, client):
12551 - Handle the case where the user makes several fast consecutive
12552 requests to the same .onion address. Previously, the first six
12553 requests would each trigger a descriptor fetch, each picking a
12554 directory (there are 6 overall) and the seventh one would fail
12555 because no directories were left, thereby triggering a close on
12556 all current directory connections asking for the hidden service.
12557 The solution here is to not close the connections if we have
12558 pending directory fetches. Fixes bug 15937; bugfix
12561 o Minor bugfixes (hidden service, control port):
12562 - Add the onion address to the HS_DESC event for the UPLOADED action
12563 both on success or failure. It was previously hardcoded with
12564 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
12566 o Minor bugfixes (hidden service, directory):
12567 - Bridges now refuse "rendezvous2" (hidden service descriptor)
12568 publish attempts. Suggested by ticket 18332.
12570 o Minor bugfixes (linux seccomp2 sandbox):
12571 - Allow the setrlimit syscall, and the prlimit and prlimit64
12572 syscalls, which some libc implementations use under the hood.
12573 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
12574 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
12575 enabled and no DNS resolvers configured. This should help TAILS
12576 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
12577 - Fix the sandbox's interoperability with unix domain sockets under
12578 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
12580 o Minor bugfixes (logging):
12581 - When logging information about an unparsable networkstatus vote or
12582 consensus, do not say "vote" when we mean consensus. Fixes bug
12583 18368; bugfix on 0.2.0.8-alpha.
12584 - Scrub service name in "unrecognized service ID" log messages.
12585 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
12586 - Downgrade logs and backtraces about IP versions to info-level.
12587 Only log backtraces once each time tor runs. Assists in diagnosing
12588 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
12589 Christian, patch by teor.
12591 o Minor bugfixes (memory safety):
12592 - Avoid freeing an uninitialized pointer when opening a socket fails
12593 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
12594 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
12596 - Correctly duplicate addresses in get_interface_address6_list().
12597 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
12598 patch by "cypherpunks".
12599 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
12601 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
12602 18672; bugfix on 0.2.5.1-alpha.
12604 o Minor bugfixes (private directory):
12605 - Prevent a race condition when creating private directories. Fixes
12606 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
12607 Patch from jsturgix. Found with Flawfinder.
12609 o Minor bugfixes (test networks, IPv6):
12610 - Allow internal IPv6 addresses in descriptors in test networks.
12611 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
12614 o Minor bugfixes (testing):
12615 - We no longer disable assertions in the unit tests when coverage is
12616 enabled. Instead, we require you to say --disable-asserts-in-tests
12617 to the configure script if you need assertions disabled in the
12618 unit tests (for example, if you want to perform branch coverage).
12619 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
12621 o Minor bugfixes (time parsing):
12622 - Avoid overflow in tor_timegm when parsing dates in and after 2038
12623 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
12624 0.0.2pre14. Patch by teor.
12626 o Minor bugfixes (tor-gencert):
12627 - Correctly handle the case where an authority operator enters a
12628 passphrase but sends an EOF before sending a newline. Fixes bug
12629 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
12631 o Code simplification and refactoring:
12632 - Quote all the string interpolations in configure.ac -- even those
12633 which we are pretty sure can't contain spaces. Closes ticket
12634 17744. Patch from zerosion.
12635 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
12636 inplace, so there's no need to have a separate implementation for
12637 the non-inplace code. Closes ticket 18258. Patch from Malek.
12638 - Simplify return types for some crypto functions that can't
12639 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
12642 - Change build messages to refer to "Fedora" instead of "Fedora
12643 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
12644 Patches from "icanhasaccount" and "cypherpunks".
12646 o Removed features:
12647 - We no longer maintain an internal freelist in memarea.c.
12648 Allocators should be good enough to make this code unnecessary,
12649 and it's doubtful that it ever had any performance benefit.
12652 - Fix several warnings from clang's address sanitizer produced in
12654 - Treat backtrace test failures as expected on FreeBSD until we
12655 solve bug 17808. Closes ticket 18204.
12658 Changes in version 0.2.8.1-alpha - 2016-02-04
12659 Tor 0.2.8.1-alpha is the first alpha release in its series. It
12660 includes numerous small features and bugfixes against previous Tor
12661 versions, and numerous small infrastructure improvements. The most
12662 notable features are a set of improvements to the directory subsystem.
12664 o Major features (security, Linux):
12665 - When Tor starts as root on Linux and is told to switch user ID, it
12666 can now retain the capability to bind to low ports. By default,
12667 Tor will do this only when it's switching user ID and some low
12668 ports have been configured. You can change this behavior with the
12669 new option KeepBindCapabilities. Closes ticket 8195.
12671 o Major features (directory system):
12672 - When bootstrapping multiple consensus downloads at a time, use the
12673 first one that starts downloading, and close the rest. This
12674 reduces failures when authorities or fallback directories are slow
12675 or down. Together with the code for feature 15775, this feature
12676 should reduces failures due to fallback churn. Implements ticket
12677 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
12678 "mikeperry" and "teor".
12679 - Include a trial list of 21 default fallback directories, generated
12680 in January 2016, based on an opt-in survey of suitable relays.
12681 Doing this should make clients bootstrap more quickly and reliably,
12682 and reduce the load on the directory authorities. Closes ticket
12683 15775. Patch by "teor".
12684 Candidates identified using an OnionOO script by "weasel", "teor",
12685 "gsathya", and "karsten".
12686 - Previously only relays that explicitly opened a directory port
12687 (DirPort) accepted directory requests from clients. Now all
12688 relays, with and without a DirPort, accept and serve tunneled
12689 directory requests that they receive through their ORPort. You can
12690 disable this behavior using the new DirCache option. Closes
12693 o Major key updates:
12694 - Update the V3 identity key for the dannenberg directory authority:
12695 it was changed on 18 November 2015. Closes task 17906. Patch
12698 o Minor features (security, clock):
12699 - Warn when the system clock appears to move back in time (when the
12700 state file was last written in the future). Tor doesn't know that
12701 consensuses have expired if the clock is in the past. Patch by
12702 "teor". Implements ticket 17188.
12704 o Minor features (security, exit policies):
12705 - ExitPolicyRejectPrivate now rejects more private addresses by
12706 default. Specifically, it now rejects the relay's outbound bind
12707 addresses (if configured), and the relay's configured port
12708 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
12709 0.2.0.11-alpha. Patch by "teor".
12711 o Minor features (security, memory erasure):
12712 - Set the unused entries in a smartlist to NULL. This helped catch
12713 a (harmless) bug, and shouldn't affect performance too much.
12714 Implements ticket 17026.
12715 - Use SecureMemoryWipe() function to securely clean memory on
12716 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
12717 Implements feature 17986.
12718 - Use explicit_bzero or memset_s when present. Previously, we'd use
12719 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
12720 from <logan@hackers.mu> and <selven@hackers.mu>.
12721 - Make memwipe() do nothing when passed a NULL pointer or buffer of
12722 zero size. Check size argument to memwipe() for underflow. Fixes
12723 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
12726 o Minor features (security, RNG):
12727 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
12728 positively are not allowed to fail. Previously we depended on
12729 internal details of OpenSSL's behavior. Closes ticket 17686.
12730 - Never use the system entropy output directly for anything besides
12731 seeding the PRNG. When we want to generate important keys, instead
12732 of using system entropy directly, we now hash it with the PRNG
12733 stream. This may help resist certain attacks based on broken OS
12734 entropy implementations. Closes part of ticket 17694.
12735 - Use modern system calls (like getentropy() or getrandom()) to
12736 generate strong entropy on platforms that have them. Closes
12739 o Minor features (accounting):
12740 - Added two modes to the AccountingRule option: One for limiting
12741 only the number of bytes sent ("AccountingRule out"), and one for
12742 limiting only the number of bytes received ("AccountingRule in").
12743 Closes ticket 15989; patch from "unixninja92".
12745 o Minor features (build):
12746 - Since our build process now uses "make distcheck", we no longer
12747 force "make dist" to depend on "make check". Closes ticket 17893;
12748 patch from "cypherpunks."
12749 - Tor now builds successfully with the recent OpenSSL 1.1
12750 development branch, and with the latest LibreSSL. Closes tickets
12751 17549, 17921, and 17984.
12753 o Minor features (controller):
12754 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
12755 tickets 16774 and 17817. Patch by George Tankersley.
12756 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
12757 service descriptor from a service's local hidden service
12758 descriptor cache. Closes ticket 14846.
12759 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
12760 controllers can examine the the reject rules added by
12761 ExitPolicyRejectPrivate. This makes it easier for stem to display
12764 o Minor features (crypto):
12765 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
12767 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
12768 - When allocating a digest state object, allocate no more space than
12769 we actually need. Previously, we would allocate as much space as
12770 the state for the largest algorithm would need. This change saves
12771 up to 672 bytes per circuit. Closes ticket 17796.
12772 - Improve performance when hashing non-multiple of 8 sized buffers,
12773 based on Andrew Moon's public domain SipHash-2-4 implementation.
12774 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
12776 o Minor features (directory downloads):
12777 - Wait for busy authorities and fallback directories to become non-
12778 busy when bootstrapping. (A similar change was made in 6c443e987d
12779 for directory caches chosen from the consensus.) Closes ticket
12780 17864; patch by "teor".
12781 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
12782 directory mirrors. The default is 1; set it to 0 to disable
12783 fallbacks. Implements ticket 17576. Patch by "teor".
12785 o Minor features (geoip):
12786 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
12789 o Minor features (IPv6):
12790 - Add an argument 'ipv6=address:orport' to the DirAuthority and
12791 FallbackDir torrc options, to specify an IPv6 address for an
12792 authority or fallback directory. Add hard-coded ipv6 addresses for
12793 directory authorities that have them. Closes ticket 17327; patch
12794 from Nick Mathewson and "teor".
12795 - Add address policy assume_action support for IPv6 addresses.
12796 - Limit IPv6 mask bits to 128.
12797 - Warn when comparing against an AF_UNSPEC address in a policy, it's
12798 almost always a bug. Closes ticket 17863; patch by "teor".
12799 - Allow users to configure directory authorities and fallback
12800 directory servers with IPv6 addresses and ORPorts. Resolves
12802 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
12803 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
12804 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
12805 17638; bugfix on 0.0.2pre8. Patch by "teor".
12807 o Minor features (logging):
12808 - When logging to syslog, allow a tag to be added to the syslog
12809 identity (the string prepended to every log message). The tag can
12810 be configured with SyslogIdentityTag and defaults to none. Setting
12811 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
12814 o Minor features (portability):
12815 - Use timingsafe_memcmp() where available. Closes ticket 17944;
12816 patch from <logan@hackers.mu>.
12818 o Minor features (relay, address discovery):
12819 - Add a family argument to get_interface_addresses_raw() and
12820 subfunctions to make network interface address interogation more
12821 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
12822 types of interfaces from the operating system. Resolves
12824 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
12825 fails to enumerate interface addresses using the platform-specific
12826 API, have it rely on the UDP socket fallback technique to try and
12827 find out what IP addresses (both IPv4 and IPv6) our machine has.
12828 Resolves ticket 17951.
12830 o Minor features (replay cache):
12831 - The replay cache now uses SHA256 instead of SHA1. Implements
12832 feature 8961. Patch by "teor", issue reported by "rransom".
12834 o Minor features (unix file permissions):
12835 - Defer creation of Unix sockets until after setuid. This avoids
12836 needing CAP_CHOWN and CAP_FOWNER when using systemd's
12837 CapabilityBoundingSet, or chown and fowner when using SELinux.
12838 Implements part of ticket 17562. Patch from Jamie Nguyen.
12839 - If any directory created by Tor is marked as group readable, the
12840 filesystem group is allowed to be either the default GID or the
12841 root user. Allowing root to read the DataDirectory prevents the
12842 need for CAP_READ_SEARCH when using systemd's
12843 CapabilityBoundingSet, or dac_read_search when using SELinux.
12844 Implements part of ticket 17562. Patch from Jamie Nguyen.
12845 - Introduce a new DataDirectoryGroupReadable option. If it is set to
12846 1, the DataDirectory will be made readable by the default GID.
12847 Implements part of ticket 17562. Patch from Jamie Nguyen.
12849 o Minor bugfixes (accounting):
12850 - The max bandwidth when using 'AccountRule sum' is now correctly
12851 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
12852 from "unixninja92".
12854 o Minor bugfixes (code correctness):
12855 - When closing an entry connection, generate a warning if we should
12856 have sent an end cell for it but we haven't. Fixes bug 17876;
12857 bugfix on 0.2.3.2-alpha.
12858 - Assert that allocated memory held by the reputation code is freed
12859 according to its internal counters. Fixes bug 17753; bugfix
12861 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
12864 o Minor bugfixes (compilation):
12865 - Mark all object files that include micro-revision.i as depending
12866 on it, so as to make parallel builds more reliable. Fixes bug
12867 17826; bugfix on 0.2.5.1-alpha.
12868 - Don't try to use the pthread_condattr_setclock() function unless
12869 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
12870 17819; bugfix on 0.2.6.3-alpha.
12871 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
12873 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
12874 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
12875 - Fix search for libevent libraries on OpenBSD (and other systems
12876 that install libevent 1 and libevent 2 in parallel). Fixes bug
12877 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
12878 - Isolate environment variables meant for tests from the rest of the
12879 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
12880 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
12882 - Remove config.log only from make distclean, not from make clean.
12883 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
12885 o Minor bugfixes (crypto):
12886 - Check the return value of HMAC() and assert on failure. Fixes bug
12887 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
12889 o Minor bugfixes (fallback directories):
12890 - Mark fallbacks as "too busy" when they return a 503 response,
12891 rather than just marking authorities. Fixes bug 17572; bugfix on
12892 0.2.4.7-alpha. Patch by "teor".
12894 o Minor bugfixes (IPv6):
12895 - Update the limits in max_dl_per_request for IPv6 address length.
12896 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
12898 o Minor bugfixes (linux seccomp2 sandbox):
12899 - Fix a crash when using offline master ed25519 keys with the Linux
12900 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
12902 o Minor bugfixes (logging):
12903 - In log messages that include a function name, use __FUNCTION__
12904 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
12905 with clang __PRETTY_FUNCTION__ has extra information we don't
12906 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
12908 - Remove needless quotes from a log message about unparseable
12909 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
12911 o Minor bugfixes (portability):
12912 - Remove an #endif from configure.ac so that we correctly detect the
12913 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
12916 o Minor bugfixes (relays):
12917 - Check that both the ORPort and DirPort (if present) are reachable
12918 before publishing a relay descriptor. Otherwise, relays publish a
12919 descriptor with DirPort 0 when the DirPort reachability test takes
12920 longer than the ORPort reachability test. Fixes bug 18050; bugfix
12921 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
12923 o Minor bugfixes (relays, hidden services):
12924 - Refuse connection requests to private OR addresses unless
12925 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
12926 then refuse to send any cells to a private address. Fixes bugs
12927 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
12929 o Minor bugfixes (safe logging):
12930 - When logging a malformed hostname received through socks4, scrub
12931 it if SafeLogging says we should. Fixes bug 17419; bugfix
12934 o Minor bugfixes (statistics code):
12935 - Consistently check for overflow in round_*_to_next_multiple_of
12936 functions, and add unit tests with additional and maximal values.
12937 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
12938 - Handle edge cases in the laplace functions: avoid division by
12939 zero, avoid taking the log of zero, and silence clang type
12940 conversion warnings using round and trunc. Add unit tests for edge
12941 cases with maximal values. Fixes part of bug 13192; bugfix
12944 o Minor bugfixes (testing):
12945 - The test for log_heartbeat was incorrectly failing in timezones
12946 with non-integer offsets. Instead of comparing the end of the time
12947 string against a constant, compare it to the output of
12948 format_local_iso_time when given the correct input. Fixes bug
12949 18039; bugfix on 0.2.5.4-alpha.
12950 - Make unit tests pass on IPv6-only systems, and systems without
12951 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
12952 bugfix on 0.2.7.3-rc. Patch by "teor".
12953 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
12955 - Check the full results of SHA256 and SHA512 digests in the unit
12956 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
12958 o Code simplification and refactoring:
12959 - Move logging of redundant policy entries in
12960 policies_parse_exit_policy_internal into its own function. Closes
12961 ticket 17608; patch from "juce".
12962 - Extract the more complicated parts of circuit_mark_for_close()
12963 into a new function that we run periodically before circuits are
12964 freed. This change removes more than half of the functions
12965 currently in the "blob". Closes ticket 17218.
12966 - Clean up a little duplicated code in
12967 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
12969 - Decouple the list of streams waiting to be attached to circuits
12970 from the overall connection list. This change makes it possible to
12971 attach streams quickly while simplifying Tor's callgraph and
12972 avoiding O(N) scans of the entire connection list. Closes
12974 - When a direct directory request fails immediately on launch,
12975 instead of relaunching that request from inside the code that
12976 launches it, instead mark the connection for teardown. This change
12977 simplifies Tor's callback and prevents the directory-request
12978 launching code from invoking itself recursively. Closes
12980 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
12981 use them. Closes ticket 17926.
12984 - Add a description of the correct use of the '--keygen' command-
12985 line option. Closes ticket 17583; based on text by 's7r'.
12986 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
12987 - Explain actual minima for BandwidthRate. Closes ticket 16382.
12988 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
12989 - Mention torspec URL in the manpage and point the reader to it
12990 whenever we mention a document that belongs in torspce. Fixes
12993 o Removed features:
12994 - Remove client-side support for connecting to Tor relays running
12995 versions of Tor before 0.2.3.6-alpha. These relays didn't support
12996 the v3 TLS handshake protocol, and are no longer allowed on the
12997 Tor network. Implements the client side of ticket 11150. Based on
12998 patches by Tom van der Woerdt.
13001 - Add unit tests to check for common RNG failure modes, such as
13002 returning all zeroes, identical values, or incrementing values
13003 (OpenSSL's rand_predictable feature). Patch by "teor".
13004 - Log more information when the backtrace tests fail. Closes ticket
13005 17892. Patch from "cypherpunks."
13006 - Always test both ed25519 backends, so that we can be sure that our
13007 batch-open replacement code works. Part of ticket 16794.
13008 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
13009 portion of ticket 16831.
13010 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
13011 util_format.c, directory.c, and options_validate.c. Closes tickets
13012 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
13014 - Unit tests for directory_handle_command_get. Closes ticket 17004.
13015 Patch from Reinaldo de Souza Jr.
13018 Changes in version 0.2.7.6 - 2015-12-10
13019 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
13020 well as a minor bug in hidden service reliability.
13022 o Major bugfixes (guard selection):
13023 - Actually look at the Guard flag when selecting a new directory
13024 guard. When we implemented the directory guard design, we
13025 accidentally started treating all relays as if they have the Guard
13026 flag during guard selection, leading to weaker anonymity and worse
13027 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
13030 o Minor features (geoip):
13031 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
13034 o Minor bugfixes (compilation):
13035 - When checking for net/pfvar.h, include netinet/in.h if possible.
13036 This fixes transparent proxy detection on OpenBSD. Fixes bug
13037 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
13038 - Fix a compilation warning with Clang 3.6: Do not check the
13039 presence of an address which can never be NULL. Fixes bug 17781.
13041 o Minor bugfixes (correctness):
13042 - When displaying an IPv6 exit policy, include the mask bits
13043 correctly even when the number is greater than 31. Fixes bug
13044 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
13045 - The wrong list was used when looking up expired intro points in a
13046 rend service object, causing what we think could be reachability
13047 issues for hidden services, and triggering a BUG log. Fixes bug
13048 16702; bugfix on 0.2.7.2-alpha.
13049 - Fix undefined behavior in the tor_cert_checksig function. Fixes
13050 bug 17722; bugfix on 0.2.7.2-alpha.
13053 Changes in version 0.2.7.5 - 2015-11-20
13054 The Tor 0.2.7 release series is dedicated to the memory of Tor user
13055 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
13056 tirelessly to advocate human rights regardless of national borders,
13057 and oppose the encroachments of mass surveillance. He opposed national
13058 exceptionalism, he brought clarity to legal and policy debates, he
13059 understood and predicted the impact of mass surveillance on the world,
13060 and he laid the groundwork for resisting it. While serving on the Tor
13061 Project's board of directors, he brought us his uncompromising focus
13062 on technical excellence in the service of humankind. Caspar was an
13063 inimitable force for good and a wonderful friend. He was kind,
13064 humorous, generous, gallant, and believed we should protect one
13065 another without exception. We honor him here for his ideals, his
13066 efforts, and his accomplishments. Please honor his memory with works
13067 that would make him proud.
13069 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
13071 The 0.2.7 series adds a more secure identity key type for relays,
13072 improves cryptography performance, resolves several longstanding
13073 hidden-service performance issues, improves controller support for
13074 hidden services, and includes small bugfixes and performance
13075 improvements throughout the program. This release series also includes
13076 more tests than before, and significant simplifications to which parts
13077 of Tor invoke which others.
13079 (This release contains no code changes since 0.2.7.4-rc.)
13082 Changes in version 0.2.7.4-rc - 2015-10-21
13083 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
13084 fixes some important memory leaks, and a scary-looking (but mostly
13085 harmless in practice) invalid-read bug. It also has a few small
13086 bugfixes, notably fixes for compilation and portability on different
13087 platforms. If no further significant bounds are found, the next
13088 release will the the official stable release.
13090 o Major bugfixes (security, correctness):
13091 - Fix an error that could cause us to read 4 bytes before the
13092 beginning of an openssl string. This bug could be used to cause
13093 Tor to crash on systems with unusual malloc implementations, or
13094 systems with unusual hardening installed. Fixes bug 17404; bugfix
13097 o Major bugfixes (correctness):
13098 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
13099 bug 17401; bugfix on 0.2.7.3-rc.
13101 o Major bugfixes (memory leaks):
13102 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
13103 17398; bugfix on 0.2.6.1-alpha.
13104 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
13105 17402; bugfix on 0.2.7.3-rc.
13106 - Fix a memory leak when reading an expired signing key from disk.
13107 Fixes bug 17403; bugfix on 0.2.7.2-rc.
13109 o Minor features (geoIP):
13110 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
13113 o Minor bugfixes (compilation):
13114 - Repair compilation with the most recent (unreleased, alpha)
13115 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
13116 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
13117 17251; bugfix on 0.2.7.2-alpha.
13118 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
13119 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
13121 o Minor bugfixes (portability):
13122 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
13123 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
13126 o Minor bugfixes (sandbox):
13127 - Add the "hidserv-stats" filename to our sandbox filter for the
13128 HiddenServiceStatistics option to work properly. Fixes bug 17354;
13129 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
13131 o Minor bugfixes (testing):
13132 - Add unit tests for get_interface_address* failure cases. Fixes bug
13133 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
13134 - Fix breakage when running 'make check' with BSD make. Fixes bug
13135 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
13136 - Make the get_ifaddrs_* unit tests more tolerant of different
13137 network configurations. (Don't assume every test box has an IPv4
13138 address, and don't assume every test box has a non-localhost
13139 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
13140 - Skip backtrace tests when backtrace support is not compiled in.
13141 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
13145 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
13146 - Note that HiddenServicePorts can take a unix domain socket. Closes
13150 Changes in version 0.2.7.3-rc - 2015-09-25
13151 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
13152 contains numerous usability fixes for Ed25519 keys, safeguards against
13153 several misconfiguration problems, significant simplifications to
13154 Tor's callgraph, and numerous bugfixes and small features.
13156 This is the most tested release of Tor to date. The unit tests cover
13157 39.40% of the code, and the integration tests (accessible with "make
13158 test-full-online", requiring stem and chutney and a network
13159 connection) raise the coverage to 64.49%.
13161 o Major features (security, hidden services):
13162 - Hidden services, if using the EntryNodes option, are required to
13163 use more than one EntryNode, in order to avoid a guard discovery
13164 attack. (This would only affect people who had configured hidden
13165 services and manually specified the EntryNodes option with a
13166 single entry-node. The impact was that it would be easy to
13167 remotely identify the guard node used by such a hidden service.
13168 See ticket for more information.) Fixes ticket 14917.
13170 o Major features (Ed25519 keys, keypinning):
13171 - The key-pinning option on directory authorities is now advisory-
13172 only by default. In a future version, or when the AuthDirPinKeys
13173 option is set, pins are enforced again. Disabling key-pinning
13174 seemed like a good idea so that we can survive the fallout of any
13175 usability problems associated with Ed25519 keys. Closes
13178 o Major features (Ed25519 performance):
13179 - Improve the speed of Ed25519 operations and Curve25519 keypair
13180 generation when built targeting 32 bit x86 platforms with SSE2
13181 available. Implements ticket 16535.
13182 - Improve the runtime speed of Ed25519 signature verification by
13183 using Ed25519-donna's batch verification support. Implements
13186 o Major features (performance testing):
13187 - The test-network.sh script now supports performance testing.
13188 Requires corresponding chutney performance testing changes. Patch
13189 by "teor". Closes ticket 14175.
13191 o Major features (relay, Ed25519):
13192 - Significant usability improvements for Ed25519 key management. Log
13193 messages are better, and the code can recover from far more
13194 failure conditions. Thanks to "s7r" for reporting and diagnosing
13196 - Add a new OfflineMasterKey option to tell Tor never to try loading
13197 or generating a secret Ed25519 identity key. You can use this in
13198 combination with tor --keygen to manage offline and/or encrypted
13199 Ed25519 keys. Implements ticket 16944.
13200 - Add a --newpass option to allow changing or removing the
13201 passphrase of an encrypted key with tor --keygen. Implements part
13203 - On receiving a HUP signal, check to see whether the Ed25519
13204 signing key has changed, and reload it if so. Closes ticket 16790.
13206 o Major bugfixes (relay, Ed25519):
13207 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
13208 0.2.7.2-alpha. Reported by "s7r".
13209 - Improve handling of expired signing keys with offline master keys.
13210 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
13212 o Minor features (client-side privacy):
13213 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
13214 lifespan when IsolateSOCKSAuth and streams with SOCKS
13215 authentication are attached to the circuit. This allows
13216 applications like TorBrowser to manage circuit lifetime on their
13217 own. Implements feature 15482.
13218 - When logging malformed hostnames from SOCKS5 requests, respect
13219 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
13221 o Minor features (compilation):
13222 - Give a warning as early as possible when trying to build with an
13223 unsupported OpenSSL version. Closes ticket 16901.
13224 - Fail during configure if we're trying to build against an OpenSSL
13225 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
13226 which started requiring ECC.
13228 o Minor features (geoip):
13229 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
13232 o Minor features (hidden services):
13233 - Relays need to have the Fast flag to get the HSDir flag. As this
13234 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
13235 drop. This change should make some attacks against the hidden
13236 service directory system harder. Fixes ticket 15963.
13237 - Turn on hidden service statistics collection by setting the torrc
13238 option HiddenServiceStatistics to "1" by default. (This keeps
13239 track only of the fraction of traffic used by hidden services, and
13240 the total number of hidden services in existence.) Closes
13242 - Client now uses an introduction point failure cache to know when
13243 to fetch or keep a descriptor in their cache. Previously, failures
13244 were recorded implicitly, but not explicitly remembered. Closes
13247 o Minor features (testing, authorities, documentation):
13248 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
13249 explicitly manage consensus flags in testing networks. Patch by
13250 "robgjansen", modified by "teor". Implements part of ticket 14882.
13252 o Minor bugfixes (security, exit policies):
13253 - ExitPolicyRejectPrivate now also rejects the relay's published
13254 IPv6 address (if any), and any publicly routable IPv4 or IPv6
13255 addresses on any local interfaces. ticket 17027. Patch by "teor".
13256 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
13258 o Minor bug fixes (torrc exit policies):
13259 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
13260 produce IPv6 wildcard addresses. Previously they would produce
13261 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
13262 of bug 16069; bugfix on 0.2.4.7-alpha.
13263 - When parsing torrc ExitPolicies, we now warn for a number of cases
13264 where the user's intent is likely to differ from Tor's actual
13265 behavior. These include: using an IPv4 address with an accept6 or
13266 reject6 line; using "private" on an accept6 or reject6 line; and
13267 including any ExitPolicy lines after accept *:* or reject *:*.
13268 Related to ticket 16069.
13269 - When parsing torrc ExitPolicies, we now issue an info-level
13270 message when expanding an "accept/reject *" line to include both
13271 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
13272 - In each instance above, usage advice is provided to avoid the
13273 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
13274 16069; bugfix on 0.2.4.7-alpha.
13276 o Minor bugfixes (authority):
13277 - Don't assign "HSDir" to a router if it isn't Valid and Running.
13278 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
13279 - Downgrade log messages about Ed25519 key issues if they are in old
13280 cached router descriptors. Fixes part of bug 16286; bugfix
13282 - When we find an Ed25519 key issue in a cached descriptor, stop
13283 saying the descriptor was just "uploaded". Fixes another part of
13284 bug 16286; bugfix on 0.2.7.2-alpha.
13286 o Minor bugfixes (control port):
13287 - Repair a warning and a spurious result when getting the maximum
13288 number of file descriptors from the controller. Fixes bug 16697;
13289 bugfix on 0.2.7.2-alpha.
13291 o Minor bugfixes (correctness):
13292 - When calling channel_free_list(), avoid calling smartlist_remove()
13293 while inside a FOREACH loop. This partially reverts commit
13294 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
13295 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
13297 o Minor bugfixes (documentation):
13298 - Advise users on how to configure separate IPv4 and IPv6 exit
13299 policies in the manpage and sample torrcs. Related to ticket 16069.
13300 - Fix the usage message of tor-resolve(1) so that it no longer lists
13301 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
13302 - Fix an error in the manual page and comments for
13303 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
13304 required "ORPort connectivity". While this is true, it is in no
13305 way unique to the HSDir flag. Of all the flags, only HSDirs need a
13306 DirPort configured in order for the authorities to assign that
13307 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
13310 o Minor bugfixes (Ed25519):
13311 - Fix a memory leak when reading router descriptors with expired
13312 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
13314 o Minor bugfixes (linux seccomp2 sandbox):
13315 - Allow bridge authorities to run correctly under the seccomp2
13316 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
13317 - Allow routers with ed25519 keys to run correctly under the
13318 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
13320 o Minor bugfixes (open file limit):
13321 - Fix set_max_file_descriptors() to set by default the max open file
13322 limit to the current limit when setrlimit() fails. Fixes bug
13323 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
13325 o Minor bugfixes (portability):
13326 - Try harder to normalize the exit status of the Tor process to the
13327 standard-provided range. Fixes bug 16975; bugfix on every version
13329 - Check correctly for Windows socket errors in the workqueue
13330 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
13331 - Fix the behavior of crypto_rand_time_range() when told to consider
13332 times before 1970. (These times were possible when running in a
13333 simulated network environment where time()'s output starts at
13334 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
13335 - Restore correct operation of TLS client-cipher detection on
13336 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
13338 o Minor bugfixes (relay):
13339 - Ensure that worker threads actually exit when a fatal error or
13340 shutdown is indicated. This fix doesn't currently affect the
13341 behavior of Tor, because Tor workers never indicates fatal error
13342 or shutdown except in the unit tests. Fixes bug 16868; bugfix
13344 - Unblock threads before releasing the work queue mutex to ensure
13345 predictable scheduling behavior. Fixes bug 16644; bugfix
13348 o Code simplification and refactoring:
13349 - Change the function that's called when we need to retry all
13350 downloads so that it only reschedules the downloads to happen
13351 immediately, rather than launching them all at once itself. This
13352 further simplifies Tor's callgraph.
13353 - Move some format-parsing functions out of crypto.c and
13354 crypto_curve25519.c into crypto_format.c and/or util_format.c.
13355 - Move the client-only parts of init_keys() into a separate
13356 function. Closes ticket 16763.
13357 - Simplify the microdesc_free() implementation so that it no longer
13358 appears (to code analysis tools) to potentially invoke a huge
13359 suite of other microdesc functions.
13360 - Simply the control graph further by deferring the inner body of
13361 directory_all_unreachable() into a callback. Closes ticket 16762.
13362 - Treat the loss of an owning controller as equivalent to a SIGTERM
13363 signal. This removes a tiny amount of duplicated code, and
13364 simplifies our callgraph. Closes ticket 16788.
13365 - When generating an event to send to the controller, we no longer
13366 put the event over the network immediately. Instead, we queue
13367 these events, and use a Libevent callback to deliver them. This
13368 change simplifies Tor's callgraph by reducing the number of
13369 functions from which all other Tor functions are reachable. Closes
13371 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
13372 that try to scan or compile every file on Unix won't decide that
13374 - Remove the unused "nulterminate" argument from buf_pullup().
13377 - Recommend a 40 GB example AccountingMax in torrc.sample rather
13378 than a 4 GB max. Closes ticket 16742.
13379 - Include the TUNING document in our source tarball. It is referred
13380 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
13384 - The internal pure-C tor-fw-helper tool is now removed from the Tor
13385 distribution, in favor of the pure-Go clone available from
13386 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
13387 used by the C tor-fw-helper are not, in our opinion, very
13388 confidence- inspiring in their secure-programming techniques.
13389 Closes ticket 13338.
13390 - Remove the code that would try to aggressively flush controller
13391 connections while writing to them. This code was introduced in
13392 0.1.2.7-alpha, in order to keep output buffers from exceeding
13393 their limits. But there is no longer a maximum output buffer size,
13394 and flushing data in this way caused some undesirable recursions
13395 in our call graph. Closes ticket 16480.
13398 - Make "bridges+hs" the default test network. This tests almost all
13399 tor functionality during make test-network, while allowing tests
13400 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
13401 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
13402 (chutney). Patches by "teor".
13403 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
13404 by-side in the same parent directory. Closes ticket 16903. Patch
13406 - Use environment variables rather than autoconf substitutions to
13407 send variables from the build system to the test scripts. This
13408 change should be easier to maintain, and cause 'make distcheck' to
13409 work better than before. Fixes bug 17148.
13410 - Add a new set of callgraph analysis scripts that use clang to
13411 produce a list of which Tor functions are reachable from which
13412 other Tor functions. We're planning to use these to help simplify
13413 our code structure by identifying illogical dependencies.
13414 - Add new 'test-full' and 'test-full-online' targets to run all
13415 tests, including integration tests with stem and chutney.
13416 - Make the test-workqueue test work on Windows by initializing the
13417 network before we begin.
13418 - New make target (make test-network-all) to run multiple applicable
13419 chutney test cases. Patch from Teor; closes 16953.
13420 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
13421 functions in dns.c. Implements a portion of ticket 16831.
13422 - When building Tor with testing coverage enabled, run Chutney tests
13423 (if any) using the 'tor-cov' coverage binary.
13424 - When running test-network or test-stem, check for the absence of
13425 stem/chutney before doing any build operations.
13428 Changes in version 0.2.7.2-alpha - 2015-07-27
13429 This, the second alpha in the Tor 0.2.7 series, has a number of new
13430 features, including a way to manually pick the number of introduction
13431 points for hidden services, and the much stronger Ed25519 signing key
13432 algorithm for regular Tor relays (including support for encrypted
13433 offline identity keys in the new algorithm).
13435 Support for Ed25519 on relays is currently limited to signing router
13436 descriptors; later alphas in this series will extend Ed25519 key
13437 support to more parts of the Tor protocol.
13439 o Major features (Ed25519 identity keys, Proposal 220):
13440 - All relays now maintain a stronger identity key, using the Ed25519
13441 elliptic curve signature format. This master key is designed so
13442 that it can be kept offline. Relays also generate an online
13443 signing key, and a set of other Ed25519 keys and certificates.
13444 These are all automatically regenerated and rotated as needed.
13445 Implements part of ticket 12498.
13446 - Directory authorities now vote on Ed25519 identity keys along with
13447 RSA1024 keys. Implements part of ticket 12498.
13448 - Directory authorities track which Ed25519 identity keys have been
13449 used with which RSA1024 identity keys, and do not allow them to
13450 vary freely. Implements part of ticket 12498.
13451 - Microdescriptors now include Ed25519 identity keys. Implements
13452 part of ticket 12498.
13453 - Add support for offline encrypted Ed25519 master keys. To use this
13454 feature on your tor relay, run "tor --keygen" to make a new master
13455 key (or to make a new signing key if you already have a master
13456 key). Closes ticket 13642.
13458 o Major features (Hidden services):
13459 - Add the torrc option HiddenServiceNumIntroductionPoints, to
13460 specify a fixed number of introduction points. Its maximum value
13461 is 10 and default is 3. Using this option can increase a hidden
13462 service's reliability under load, at the cost of making it more
13463 visible that the hidden service is facing extra load. Closes
13465 - Remove the adaptive algorithm for choosing the number of
13466 introduction points, which used to change the number of
13467 introduction points (poorly) depending on the number of
13468 connections the HS sees. Closes ticket 4862.
13470 o Major features (onion key cross-certification):
13471 - Relay descriptors now include signatures of their own identity
13472 keys, made using the TAP and ntor onion keys. These signatures
13473 allow relays to prove ownership of their own onion keys. Because
13474 of this change, microdescriptors will no longer need to include
13475 RSA identity keys. Implements proposal 228; closes ticket 12499.
13477 o Major features (performance):
13478 - Improve the runtime speed of Ed25519 operations by using the
13479 public-domain Ed25519-donna by Andrew M. ("floodyberry").
13480 Implements ticket 16467.
13481 - Improve the runtime speed of the ntor handshake by using an
13482 optimized curve25519 basepoint scalarmult implementation from the
13483 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
13484 ideas by Adam Langley. Implements ticket 9663.
13486 o Major bugfixes (client-side privacy, also in 0.2.6.9):
13487 - Properly separate out each SOCKSPort when applying stream
13488 isolation. The error occurred because each port's session group
13489 was being overwritten by a default value when the listener
13490 connection was initialized. Fixes bug 16247; bugfix on
13491 0.2.6.3-alpha. Patch by "jojelino".
13493 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
13494 - Stop refusing to store updated hidden service descriptors on a
13495 client. This reverts commit 9407040c59218 (which indeed fixed bug
13496 14219, but introduced a major hidden service reachability
13497 regression detailed in bug 16381). This is a temporary fix since
13498 we can live with the minor issue in bug 14219 (it just results in
13499 some load on the network) but the regression of 16381 is too much
13500 of a setback. First-round fix for bug 16381; bugfix
13503 o Major bugfixes (hidden services):
13504 - When cannibalizing a circuit for an introduction point, always
13505 extend to the chosen exit node (creating a 4 hop circuit).
13506 Previously Tor would use the current circuit exit node, which
13507 changed the original choice of introduction point, and could cause
13508 the hidden service to skip excluded introduction points or
13509 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
13512 o Major bugfixes (open file limit):
13513 - The open file limit wasn't checked before calling
13514 tor_accept_socket_nonblocking(), which would make Tor exceed the
13515 limit. Now, before opening a new socket, Tor validates the open
13516 file limit just before, and if the max has been reached, return an
13517 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
13519 o Major bugfixes (stability, also in 0.2.6.10):
13520 - Stop crashing with an assertion failure when parsing certain kinds
13521 of malformed or truncated microdescriptors. Fixes bug 16400;
13522 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13523 by "cypherpunks_backup".
13524 - Stop random client-side assertion failures that could occur when
13525 connecting to a busy hidden service, or connecting to a hidden
13526 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13529 o Minor features (directory authorities, security, also in 0.2.6.9):
13530 - The HSDir flag given by authorities now requires the Stable flag.
13531 For the current network, this results in going from 2887 to 2806
13532 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13533 attack by raising the effort for a relay to become Stable to
13534 require at the very least 7 days, while maintaining the 96 hours
13535 uptime requirement for HSDir. Implements ticket 8243.
13537 o Minor features (client):
13538 - Relax the validation of hostnames in SOCKS5 requests, allowing the
13539 character '_' to appear, in order to cope with domains observed in
13540 the wild that are serving non-RFC compliant records. Resolves
13542 - Relax the validation done to hostnames in SOCKS5 requests, and
13543 allow a single trailing '.' to cope with clients that pass FQDNs
13544 using that syntax to explicitly indicate that the domain name is
13545 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
13546 - Add GroupWritable and WorldWritable options to unix-socket based
13547 SocksPort and ControlPort options. These options apply to a single
13548 socket, and override {Control,Socks}SocketsGroupWritable. Closes
13551 o Minor features (control protocol):
13552 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
13553 the control protocol. Resolves ticket 15358.
13555 o Minor features (directory authorities):
13556 - Directory authorities no longer vote against the "Fast", "Stable",
13557 and "HSDir" flags just because they were going to vote against
13558 "Running": if the consensus turns out to be that the router was
13559 running, then the authority's vote should count. Patch from Peter
13560 Retzlaff; closes issue 8712.
13562 o Minor features (geoip, also in 0.2.6.10):
13563 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13564 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13566 o Minor features (hidden services):
13567 - Add the new options "HiddenServiceMaxStreams" and
13568 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
13569 limit the maximum number of simultaneous streams per circuit, and
13570 optionally tear down the circuit when the limit is exceeded. Part
13573 o Minor features (portability):
13574 - Use C99 variadic macros when the compiler is not GCC. This avoids
13575 failing compilations on MSVC, and fixes a log-file-based race
13576 condition in our old workarounds. Original patch from Gisle Vanem.
13578 o Minor bugfixes (compilation, also in 0.2.6.9):
13579 - Build with --enable-systemd correctly when libsystemd is
13580 installed, but systemd is not. Fixes bug 16164; bugfix on
13581 0.2.6.3-alpha. Patch from Peter Palfrader.
13583 o Minor bugfixes (controller):
13584 - Add the descriptor ID in each HS_DESC control event. It was
13585 missing, but specified in control-spec.txt. Fixes bug 15881;
13586 bugfix on 0.2.5.2-alpha.
13588 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
13589 - Check for failures from crypto_early_init, and refuse to continue.
13590 A previous typo meant that we could keep going with an
13591 uninitialized crypto library, and would have OpenSSL initialize
13592 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13593 when implementing ticket 4900. Patch by "teor".
13595 o Minor bugfixes (hidden services):
13596 - Fix a crash when reloading configuration while at least one
13597 configured and one ephemeral hidden service exists. Fixes bug
13598 16060; bugfix on 0.2.7.1-alpha.
13599 - Avoid crashing with a double-free bug when we create an ephemeral
13600 hidden service but adding it fails for some reason. Fixes bug
13601 16228; bugfix on 0.2.7.1-alpha.
13603 o Minor bugfixes (Linux seccomp2 sandbox):
13604 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
13605 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
13607 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
13608 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13609 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13610 on 0.2.6.3-alpha. Patch from "teor".
13612 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
13613 - Fix sandboxing to work when running as a relay, by allowing the
13614 renaming of secret_id_key, and allowing the eventfd2 and futex
13615 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
13617 - Allow systemd connections to work with the Linux seccomp2 sandbox
13618 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13621 o Minor bugfixes (relay):
13622 - Fix a rarely-encountered memory leak when failing to initialize
13623 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
13624 from "cypherpunks".
13626 o Minor bugfixes (systemd):
13627 - Fix an accidental formatting error that broke the systemd
13628 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
13629 - Tor's systemd unit file no longer contains extraneous spaces.
13630 These spaces would sometimes confuse tools like deb-systemd-
13631 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
13633 o Minor bugfixes (tests):
13634 - Use the configured Python executable when running test-stem-full.
13635 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
13637 o Minor bugfixes (tests, also in 0.2.6.9):
13638 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13639 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13641 o Minor bugfixes (threads, comments):
13642 - Always initialize return value in compute_desc_id in rendcommon.c
13643 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13644 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
13645 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13646 - Remove undefined directive-in-macro in test_util_writepid clang
13647 3.7 complains that using a preprocessor directive inside a macro
13648 invocation in test_util_writepid in test_util.c is undefined.
13649 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
13651 o Code simplification and refactoring:
13652 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
13653 to ensure they remain consistent and visible everywhere.
13654 - Remove some vestigial workarounds for the MSVC6 compiler. We
13655 haven't supported that in ages.
13656 - The link authentication code has been refactored for better
13657 testability and reliability. It now uses code generated with the
13658 "trunnel" binary encoding generator, to reduce the risk of bugs
13659 due to programmer error. Done as part of ticket 12498.
13662 - Include a specific and (hopefully) accurate documentation of the
13663 torrc file's meta-format in doc/torrc_format.txt. This is mainly
13664 of interest to people writing programs to parse or generate torrc
13665 files. This document is not a commitment to long-term
13666 compatibility; some aspects of the current format are a bit
13667 ridiculous. Closes ticket 2325.
13669 o Removed features:
13670 - Tor no longer supports copies of OpenSSL that are missing support
13671 for Elliptic Curve Cryptography. (We began using ECC when
13672 available in 0.2.4.8-alpha, for more safe and efficient key
13673 negotiation.) In particular, support for at least one of P256 or
13674 P224 is now required, with manual configuration needed if only
13675 P224 is available. Resolves ticket 16140.
13676 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
13677 on an operating system that has not upgraded to OpenSSL 1.0 or
13678 later, and you compile Tor from source, you will need to install a
13679 more recent OpenSSL to link Tor against.) These versions of
13680 OpenSSL are still supported by the OpenSSL, but the numerous
13681 cryptographic improvements in later OpenSSL releases makes them a
13682 clear choice. Resolves ticket 16034.
13683 - Remove the HidServDirectoryV2 option. Now all relays offer to
13684 store hidden service descriptors. Related to 16543.
13685 - Remove the VoteOnHidServDirectoriesV2 option, since all
13686 authorities have long set it to 1. Closes ticket 16543.
13689 - Document use of coverity, clang static analyzer, and clang dynamic
13690 undefined behavior and address sanitizers in doc/HACKING. Include
13691 detailed usage instructions in the blacklist. Patch by "teor".
13692 Closes ticket 15817.
13693 - The link authentication protocol code now has extensive tests.
13694 - The relay descriptor signature testing code now has
13696 - The test_workqueue program now runs faster, and is enabled by
13697 default as a part of "make check".
13698 - Now that OpenSSL has its own scrypt implementation, add an unit
13699 test that checks for interoperability between libscrypt_scrypt()
13700 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
13701 and rely on EVP_PBE_scrypt() whenever possible. Resolves
13705 Changes in version 0.2.6.10 - 2015-07-12
13706 Tor version 0.2.6.10 fixes some significant stability and hidden
13707 service client bugs, bulletproofs the cryptography init process, and
13708 fixes a bug when using the sandbox code with some older versions of
13709 Linux. Everyone running an older version, especially an older version
13710 of 0.2.6, should upgrade.
13712 o Major bugfixes (hidden service clients, stability):
13713 - Stop refusing to store updated hidden service descriptors on a
13714 client. This reverts commit 9407040c59218 (which indeed fixed bug
13715 14219, but introduced a major hidden service reachability
13716 regression detailed in bug 16381). This is a temporary fix since
13717 we can live with the minor issue in bug 14219 (it just results in
13718 some load on the network) but the regression of 16381 is too much
13719 of a setback. First-round fix for bug 16381; bugfix
13722 o Major bugfixes (stability):
13723 - Stop crashing with an assertion failure when parsing certain kinds
13724 of malformed or truncated microdescriptors. Fixes bug 16400;
13725 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
13726 by "cypherpunks_backup".
13727 - Stop random client-side assertion failures that could occur when
13728 connecting to a busy hidden service, or connecting to a hidden
13729 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
13732 o Minor features (geoip):
13733 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
13734 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
13736 o Minor bugfixes (crypto error-handling):
13737 - Check for failures from crypto_early_init, and refuse to continue.
13738 A previous typo meant that we could keep going with an
13739 uninitialized crypto library, and would have OpenSSL initialize
13740 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
13741 when implementing ticket 4900. Patch by "teor".
13743 o Minor bugfixes (Linux seccomp2 sandbox):
13744 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
13745 these when eventfd2() support is missing. Fixes bug 16363; bugfix
13746 on 0.2.6.3-alpha. Patch from "teor".
13749 Changes in version 0.2.6.9 - 2015-06-11
13750 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
13751 requirements for receiving an HSDir flag, and addresses some other small
13752 bugs in the systemd and sandbox code. Clients using circuit isolation
13753 should upgrade; all directory authorities should upgrade.
13755 o Major bugfixes (client-side privacy):
13756 - Properly separate out each SOCKSPort when applying stream
13757 isolation. The error occurred because each port's session group was
13758 being overwritten by a default value when the listener connection
13759 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
13762 o Minor feature (directory authorities, security):
13763 - The HSDir flag given by authorities now requires the Stable flag.
13764 For the current network, this results in going from 2887 to 2806
13765 HSDirs. Also, it makes it harder for an attacker to launch a sybil
13766 attack by raising the effort for a relay to become Stable which
13767 takes at the very least 7 days to do so and by keeping the 96
13768 hours uptime requirement for HSDir. Implements ticket 8243.
13770 o Minor bugfixes (compilation):
13771 - Build with --enable-systemd correctly when libsystemd is
13772 installed, but systemd is not. Fixes bug 16164; bugfix on
13773 0.2.6.3-alpha. Patch from Peter Palfrader.
13775 o Minor bugfixes (Linux seccomp2 sandbox):
13776 - Fix sandboxing to work when running as a relaymby renaming of
13777 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
13778 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
13779 - Allow systemd connections to work with the Linux seccomp2 sandbox
13780 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
13783 o Minor bugfixes (tests):
13784 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
13785 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
13788 Changes in version 0.2.6.8 - 2015-05-21
13789 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
13790 fixes an authority-side bug in assigning the HSDir flag. All directory
13791 authorities should upgrade.
13793 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
13794 - Revert commit that made directory authorities assign the HSDir
13795 flag to relays without a DirPort; this was bad because such relays
13796 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13799 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
13800 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13801 a client authorized hidden service. Fixes bug 15823; bugfix
13804 o Minor features (geoip):
13805 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13806 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13810 Changes in version 0.2.7.1-alpha - 2015-05-12
13811 Tor 0.2.7.1-alpha is the first alpha release in its series. It
13812 includes numerous small features and bugfixes against previous Tor
13813 versions, and numerous small infrastructure improvements. The most
13814 notable features are several new ways for controllers to interact with
13815 the hidden services subsystem.
13817 o New system requirements:
13818 - Tor no longer includes workarounds to support Libevent versions
13819 before 1.3e. Libevent 2.0 or later is recommended. Closes
13822 o Major features (controller):
13823 - Add the ADD_ONION and DEL_ONION commands that allow the creation
13824 and management of hidden services via the controller. Closes
13826 - New "GETINFO onions/current" and "GETINFO onions/detached"
13827 commands to get information about hidden services created via the
13828 controller. Part of ticket 6411.
13829 - New HSFETCH command to launch a request for a hidden service
13830 descriptor. Closes ticket 14847.
13831 - New HSPOST command to upload a hidden service descriptor. Closes
13832 ticket 3523. Patch by "DonnchaC".
13834 o Major bugfixes (hidden services):
13835 - Revert commit that made directory authorities assign the HSDir
13836 flag to relays without a DirPort; this was bad because such relays
13837 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
13840 o Minor features (clock-jump tolerance):
13841 - Recover better when our clock jumps back many hours, like might
13842 happen for Tails or Whonix users who start with a very wrong
13843 hardware clock, use Tor to discover a more accurate time, and then
13844 fix their clock. Resolves part of ticket 8766.
13846 o Minor features (command-line interface):
13847 - Make --hash-password imply --hush to prevent unnecessary noise.
13848 Closes ticket 15542. Patch from "cypherpunks".
13849 - Print a warning whenever we find a relative file path being used
13850 as torrc option. Resolves issue 14018.
13852 o Minor features (controller):
13853 - Add DirAuthority lines for default directory authorities to the
13854 output of the "GETINFO config/defaults" command if not already
13855 present. Implements ticket 14840.
13856 - Controllers can now use "GETINFO hs/client/desc/id/..." to
13857 retrieve items from the client's hidden service descriptor cache.
13858 Closes ticket 14845.
13859 - Implement a new controller command "GETINFO status/fresh-relay-
13860 descs" to fetch a descriptor/extrainfo pair that was generated on
13861 demand just for the controller's use. Implements ticket 14784.
13863 o Minor features (DoS-resistance):
13864 - Make it harder for attackers to overload hidden services with
13865 introductions, by blocking multiple introduction requests on the
13866 same circuit. Resolves ticket 15515.
13868 o Minor features (geoip):
13869 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
13870 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
13873 o Minor features (HS popularity countermeasure):
13874 - To avoid leaking HS popularity, don't cycle the introduction point
13875 when we've handled a fixed number of INTRODUCE2 cells but instead
13876 cycle it when a random number of introductions is reached, thus
13877 making it more difficult for an attacker to find out the amount of
13878 clients that have used the introduction point for a specific HS.
13879 Closes ticket 15745.
13881 o Minor features (logging):
13882 - Include the Tor version in all LD_BUG log messages, since people
13883 tend to cut and paste those into the bugtracker. Implements
13886 o Minor features (pluggable transports):
13887 - When launching managed pluggable transports on Linux systems,
13888 attempt to have the kernel deliver a SIGTERM on tor exit if the
13889 pluggable transport process is still running. Resolves
13891 - When launching managed pluggable transports, setup a valid open
13892 stdin in the child process that can be used to detect if tor has
13893 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
13894 can be used by implementations to detect this new behavior.
13895 Resolves ticket 15435.
13897 o Minor features (testing):
13898 - Add a test to verify that the compiler does not eliminate our
13899 memwipe() implementation. Closes ticket 15377.
13900 - Add make rule `check-changes` to verify the format of changes
13901 files. Closes ticket 15180.
13902 - Add unit tests for control_event_is_interesting(). Add a compile-
13903 time check that the number of events doesn't exceed the capacity
13904 of control_event_t.event_mask. Closes ticket 15431, checks for
13905 bugs similar to 13085. Patch by "teor".
13906 - Command-line argument tests moved to Stem. Resolves ticket 14806.
13907 - Integrate the ntor, backtrace, and zero-length keys tests into the
13908 automake test suite. Closes ticket 15344.
13909 - Remove assertions during builds to determine Tor's test coverage.
13910 We don't want to trigger these even in assertions, so including
13911 them artificially makes our branch coverage look worse than it is.
13912 This patch provides the new test-stem-full and coverage-html-full
13913 configure options. Implements ticket 15400.
13915 o Minor bugfixes (build):
13916 - Improve out-of-tree builds by making non-standard rules work and
13917 clean up additional files and directories. Fixes bug 15053; bugfix
13920 o Minor bugfixes (command-line interface):
13921 - When "--quiet" is provided along with "--validate-config", do not
13922 write anything to stdout on success. Fixes bug 14994; bugfix
13924 - When complaining about bad arguments to "--dump-config", use
13925 stderr, not stdout.
13927 o Minor bugfixes (configuration, unit tests):
13928 - Only add the default fallback directories when the DirAuthorities,
13929 AlternateDirAuthority, and FallbackDir directory config options
13930 are set to their defaults. The default fallback directory list is
13931 currently empty, this fix will only change tor's behavior when it
13932 has default fallback directories. Includes unit tests for
13933 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
13934 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
13936 o Minor bugfixes (correctness):
13937 - For correctness, avoid modifying a constant string in
13938 handle_control_postdescriptor. Fixes bug 15546; bugfix
13940 - Remove side-effects from tor_assert() calls. This was harmless,
13941 because we never disable assertions, but it is bad style and
13942 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
13945 o Minor bugfixes (hidden service):
13946 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
13947 a client authorized hidden service. Fixes bug 15823; bugfix
13949 - Remove an extraneous newline character from the end of hidden
13950 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
13952 o Minor bugfixes (interface):
13953 - Print usage information for --dump-config when it is used without
13954 an argument. Also, fix the error message to use different wording
13955 and add newline at the end. Fixes bug 15541; bugfix
13958 o Minor bugfixes (logs):
13959 - When building Tor under Clang, do not include an extra set of
13960 parentheses in log messages that include function names. Fixes bug
13961 15269; bugfix on every released version of Tor when compiled with
13962 recent enough Clang.
13964 o Minor bugfixes (network):
13965 - When attempting to use fallback technique for network interface
13966 lookup, disregard loopback and multicast addresses since they are
13967 unsuitable for public communications.
13969 o Minor bugfixes (statistics):
13970 - Disregard the ConnDirectionStatistics torrc options when Tor is
13971 not a relay since in that mode of operation no sensible data is
13972 being collected and because Tor might run into measurement hiccups
13973 when running as a client for some time, then becoming a relay.
13974 Fixes bug 15604; bugfix on 0.2.2.35.
13976 o Minor bugfixes (test networks):
13977 - When self-testing reachability, use ExtendAllowPrivateAddresses to
13978 determine if local/private addresses imply reachability. The
13979 previous fix used TestingTorNetwork, which implies
13980 ExtendAllowPrivateAddresses, but this excluded rare configurations
13981 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
13982 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
13983 issue discovered by CJ Ess.
13985 o Minor bugfixes (testing):
13986 - Check for matching value in server response in ntor_ref.py. Fixes
13987 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
13989 - Set the severity correctly when testing
13990 get_interface_addresses_ifaddrs() and
13991 get_interface_addresses_win32(), so that the tests fail gracefully
13992 instead of triggering an assertion. Fixes bug 15759; bugfix on
13993 0.2.6.3-alpha. Reported by Nicolas Derive.
13995 o Code simplification and refactoring:
13996 - Move the hacky fallback code out of get_interface_address6() into
13997 separate function and get it covered with unit-tests. Resolves
13999 - Refactor hidden service client-side cache lookup to intelligently
14000 report its various failure cases, and disentangle failure cases
14001 involving a lack of introduction points. Closes ticket 14391.
14002 - Use our own Base64 encoder instead of OpenSSL's, to allow more
14003 control over the output. Part of ticket 15652.
14006 - Improve the descriptions of statistics-related torrc options in
14007 the manpage to describe rationale and possible uses cases. Fixes
14009 - Improve the layout and formatting of ./configure --help messages.
14010 Closes ticket 15024. Patch from "cypherpunks".
14011 - Standardize on the term "server descriptor" in the manual page.
14012 Previously, we had used "router descriptor", "server descriptor",
14013 and "relay descriptor" interchangeably. Part of ticket 14987.
14016 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
14017 and always use the internal Base64 decoder. The internal decoder
14018 has been part of tor since 0.2.0.10-alpha, and no one should
14019 be using the OpenSSL one. Part of ticket 15652.
14020 - Remove the 'tor_strclear()' function; use memwipe() instead.
14021 Closes ticket 14922.
14023 o Removed features:
14024 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
14025 fingerprinting we now recommend pluggable transports; for forward-
14026 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
14027 - Remove the undocumented "--digests" command-line option. It
14028 complicated our build process, caused subtle build issues on
14029 multiple platforms, and is now redundant since we started
14030 including git version identifiers. Closes ticket 14742.
14031 - Tor no longer contains checks for ancient directory cache versions
14032 that didn't know about microdescriptors.
14033 - Tor no longer contains workarounds for stat files generated by
14034 super-old versions of Tor that didn't choose guards sensibly.
14037 Changes in version 0.2.4.27 - 2015-04-06
14038 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
14039 could be used by an attacker to crash hidden services, or crash clients
14040 visiting hidden services. Hidden services should upgrade as soon as
14041 possible; clients should upgrade whenever packages become available.
14043 This release also backports a simple improvement to make hidden
14044 services a bit less vulnerable to denial-of-service attacks.
14046 o Major bugfixes (security, hidden service):
14047 - Fix an issue that would allow a malicious client to trigger an
14048 assertion failure and halt a hidden service. Fixes bug 15600;
14049 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14050 - Fix a bug that could cause a client to crash with an assertion
14051 failure when parsing a malformed hidden service descriptor. Fixes
14052 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14054 o Minor features (DoS-resistance, hidden service):
14055 - Introduction points no longer allow multiple INTRODUCE1 cells to
14056 arrive on the same circuit. This should make it more expensive for
14057 attackers to overwhelm hidden services with introductions.
14058 Resolves ticket 15515.
14061 Changes in version 0.2.5.12 - 2015-04-06
14062 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
14063 could be used by an attacker to crash hidden services, or crash clients
14064 visiting hidden services. Hidden services should upgrade as soon as
14065 possible; clients should upgrade whenever packages become available.
14067 This release also backports a simple improvement to make hidden
14068 services a bit less vulnerable to denial-of-service attacks.
14070 o Major bugfixes (security, hidden service):
14071 - Fix an issue that would allow a malicious client to trigger an
14072 assertion failure and halt a hidden service. Fixes bug 15600;
14073 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14074 - Fix a bug that could cause a client to crash with an assertion
14075 failure when parsing a malformed hidden service descriptor. Fixes
14076 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14078 o Minor features (DoS-resistance, hidden service):
14079 - Introduction points no longer allow multiple INTRODUCE1 cells to
14080 arrive on the same circuit. This should make it more expensive for
14081 attackers to overwhelm hidden services with introductions.
14082 Resolves ticket 15515.
14085 Changes in version 0.2.6.7 - 2015-04-06
14086 Tor 0.2.6.7 fixes two security issues that could be used by an
14087 attacker to crash hidden services, or crash clients visiting hidden
14088 services. Hidden services should upgrade as soon as possible; clients
14089 should upgrade whenever packages become available.
14091 This release also contains two simple improvements to make hidden
14092 services a bit less vulnerable to denial-of-service attacks.
14094 o Major bugfixes (security, hidden service):
14095 - Fix an issue that would allow a malicious client to trigger an
14096 assertion failure and halt a hidden service. Fixes bug 15600;
14097 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
14098 - Fix a bug that could cause a client to crash with an assertion
14099 failure when parsing a malformed hidden service descriptor. Fixes
14100 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
14102 o Minor features (DoS-resistance, hidden service):
14103 - Introduction points no longer allow multiple INTRODUCE1 cells to
14104 arrive on the same circuit. This should make it more expensive for
14105 attackers to overwhelm hidden services with introductions.
14106 Resolves ticket 15515.
14107 - Decrease the amount of reattempts that a hidden service performs
14108 when its rendezvous circuits fail. This reduces the computational
14109 cost for running a hidden service under heavy load. Resolves
14113 Changes in version 0.2.6.6 - 2015-03-24
14114 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
14116 It adds numerous safety, security, correctness, and performance
14117 improvements. Client programs can be configured to use more kinds of
14118 sockets, AutomapHosts works better, the multithreading backend is
14119 improved, cell transmission is refactored, test coverage is much
14120 higher, more denial-of-service attacks are handled, guard selection is
14121 improved to handle long-term guards better, pluggable transports
14122 should work a bit better, and some annoying hidden service performance
14123 bugs should be addressed.
14125 o Minor bugfixes (portability):
14126 - Use the correct datatype in the SipHash-2-4 function to prevent
14127 compilers from assuming any sort of alignment. Fixes bug 15436;
14128 bugfix on 0.2.5.3-alpha.
14130 Changes in version 0.2.6.5-rc - 2015-03-18
14131 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
14132 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
14134 o Major bugfixes (client):
14135 - Avoid crashing when making certain configuration option changes on
14136 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
14139 o Major bugfixes (pluggable transports):
14140 - Initialize the extended OR Port authentication cookie before
14141 launching pluggable transports. This prevents a race condition
14142 that occurred when server-side pluggable transports would cache the
14143 authentication cookie before it has been (re)generated. Fixes bug
14144 15240; bugfix on 0.2.5.1-alpha.
14146 o Major bugfixes (portability):
14147 - Do not crash on startup when running on Solaris. Fixes a bug
14148 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
14151 o Minor features (heartbeat):
14152 - On relays, report how many connections we negotiated using each
14153 version of the Tor link protocols. This information will let us
14154 know if removing support for very old versions of the Tor
14155 protocols is harming the network. Closes ticket 15212.
14157 o Code simplification and refactoring:
14158 - Refactor main loop to extract the 'loop' part. This makes it
14159 easier to run Tor under Shadow. Closes ticket 15176.
14162 Changes in version 0.2.5.11 - 2015-03-17
14163 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
14165 It backports several bugfixes from the 0.2.6 branch, including a
14166 couple of medium-level security fixes for relays and exit nodes.
14167 It also updates the list of directory authorities.
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 (crash, OSX, security):
14177 - Fix a remote denial-of-service opportunity caused by a bug in
14178 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14181 o Major bugfixes (relay, stability, possible security):
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 Major bugfixes (exit node stability):
14191 - Fix an assertion failure that could occur under high DNS load.
14192 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14193 diagnosed and fixed by "cypherpunks".
14195 o Major bugfixes (Linux seccomp2 sandbox):
14196 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14197 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14198 0.2.5.1-alpha. Patch from "sanic".
14200 o Minor features (controller):
14201 - New "GETINFO bw-event-cache" to get information about recent
14202 bandwidth events. Closes ticket 14128. Useful for controllers to
14203 get recent bandwidth history after the fix for ticket 13988.
14205 o Minor features (geoip):
14206 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14207 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14210 o Minor bugfixes (client, automapping):
14211 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14212 no value follows the option. Fixes bug 14142; bugfix on
14213 0.2.4.7-alpha. Patch by "teor".
14214 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14215 14195; bugfix on 0.1.0.1-rc.
14217 o Minor bugfixes (compilation):
14218 - Build without warnings with the stock OpenSSL srtp.h header, which
14219 has a duplicate declaration of SSL_get_selected_srtp_profile().
14220 Fixes bug 14220; this is OpenSSL's bug, not ours.
14222 o Minor bugfixes (directory authority):
14223 - Allow directory authorities to fetch more data from one another if
14224 they find themselves missing lots of votes. Previously, they had
14225 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14226 bugfix on 0.1.2.5-alpha.
14227 - Enlarge the buffer to read bwauth generated files to avoid an
14228 issue when parsing the file in dirserv_read_measured_bandwidths().
14229 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14231 o Minor bugfixes (statistics):
14232 - Increase period over which bandwidth observations are aggregated
14233 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14235 o Minor bugfixes (preventative security, C safety):
14236 - When reading a hexadecimal, base-32, or base-64 encoded value from
14237 a string, always overwrite the whole output buffer. This prevents
14238 some bugs where we would look at (but fortunately, not reveal)
14239 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14243 Changes in version 0.2.4.26 - 2015-03-17
14244 Tor 0.2.4.26 includes an updated list of directory authorities. It
14245 also backports a couple of stability and security bugfixes from 0.2.5
14248 o Directory authority changes:
14249 - Remove turtles as a directory authority.
14250 - Add longclaw as a new (v3) directory authority. This implements
14251 ticket 13296. This keeps the directory authority count at 9.
14252 - The directory authority Faravahar has a new IP address. This
14253 closes ticket 14487.
14255 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
14256 - Fix an assertion failure that could occur under high DNS load.
14257 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14258 diagnosed and fixed by "cypherpunks".
14260 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
14261 - Fix a bug that could lead to a relay crashing with an assertion
14262 failure if a buffer of exactly the wrong layout was passed to
14263 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14264 0.2.0.10-alpha. Patch from 'cypherpunks'.
14265 - Do not assert if the 'data' pointer on a buffer is advanced to the
14266 very end of the buffer; log a BUG message instead. Only assert if
14267 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14269 o Minor features (geoip):
14270 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14271 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14274 Changes in version 0.2.6.4-rc - 2015-03-09
14275 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
14276 attacker might be able to use in order to crash certain Tor
14277 directories. It also resolves some minor issues left over from, or
14278 introduced in, Tor 0.2.6.3-alpha or earlier.
14280 o Major bugfixes (crash, OSX, security):
14281 - Fix a remote denial-of-service opportunity caused by a bug in
14282 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
14285 o Major bugfixes (relay, stability, possible security):
14286 - Fix a bug that could lead to a relay crashing with an assertion
14287 failure if a buffer of exactly the wrong layout is passed to
14288 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
14289 0.2.0.10-alpha. Patch from "cypherpunks".
14290 - Do not assert if the 'data' pointer on a buffer is advanced to the
14291 very end of the buffer; log a BUG message instead. Only assert if
14292 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
14294 o Major bugfixes (FreeBSD IPFW transparent proxy):
14295 - Fix address detection with FreeBSD transparent proxies, when
14296 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
14299 o Major bugfixes (Linux seccomp2 sandbox):
14300 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
14301 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
14303 - Allow AF_UNIX hidden services to be used with the seccomp2
14304 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
14305 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
14306 crash during attempts to call wait4. Fixes bug 15088; bugfix on
14307 0.2.5.1-alpha. Patch from "sanic".
14309 o Minor features (controller):
14310 - Messages about problems in the bootstrap process now include
14311 information about the server we were trying to connect to when we
14312 noticed the problem. Closes ticket 15006.
14314 o Minor features (geoip):
14315 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
14316 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
14319 o Minor features (logs):
14320 - Quiet some log messages in the heartbeat and at startup. Closes
14323 o Minor bugfixes (certificate handling):
14324 - If an authority operator accidentally makes a signing certificate
14325 with a future publication time, do not discard its real signing
14326 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
14327 - Remove any old authority certificates that have been superseded
14328 for at least two days. Previously, we would keep superseded
14329 certificates until they expired, if they were published close in
14330 time to the certificate that superseded them. Fixes bug 11454;
14331 bugfix on 0.2.1.8-alpha.
14333 o Minor bugfixes (compilation):
14334 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
14336 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
14339 o Minor bugfixes (testing):
14340 - Fix endianness issues in unit test for resolve_my_address() to
14341 have it pass on big endian systems. Fixes bug 14980; bugfix on
14343 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
14344 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
14345 - When running the new 'make test-stem' target, use the configured
14346 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
14347 from "cypherpunks".
14348 - When running the zero-length-keys tests, do not use the default
14349 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
14352 o Directory authority IP change:
14353 - The directory authority Faravahar has a new IP address. This
14354 closes ticket 14487.
14357 - Remove some lingering dead code that once supported mempools.
14358 Mempools were disabled by default in 0.2.5, and removed entirely
14359 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
14363 Changes in version 0.2.6.3-alpha - 2015-02-19
14364 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
14365 the 0.2.6.x series. It introduces support for more kinds of sockets,
14366 makes it harder to accidentally run an exit, improves our
14367 multithreading backend, incorporates several fixes for the
14368 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
14370 If no major regressions or security holes are found in this version,
14371 the next version will be a release candidate.
14373 o Deprecated versions:
14374 - Tor relays older than 0.2.4.18-rc are no longer allowed to
14375 advertise themselves on the network. Closes ticket 13555.
14377 o Major features (security, unix domain sockets):
14378 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
14379 applications can reach Tor without having to create AF_INET or
14380 AF_INET6 sockets, meaning they can completely disable their
14381 ability to make non-Tor network connections. To create a socket of
14382 this type, use "SocksPort unix:/path/to/socket". Implements
14384 - Support mapping hidden service virtual ports to AF_UNIX sockets.
14385 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
14386 Implements ticket 11485.
14388 o Major features (changed defaults):
14389 - Prevent relay operators from unintentionally running exits: When a
14390 relay is configured as an exit node, we now warn the user unless
14391 the "ExitRelay" option is set to 1. We warn even more loudly if
14392 the relay is configured with the default exit policy, since this
14393 can indicate accidental misconfiguration. Setting "ExitRelay 0"
14394 stops Tor from running as an exit relay. Closes ticket 10067.
14396 o Major features (directory system):
14397 - When downloading server- or microdescriptors from a directory
14398 server, we no longer launch multiple simultaneous requests to the
14399 same server. This reduces load on the directory servers,
14400 especially when directory guards are in use. Closes ticket 9969.
14401 - When downloading server- or microdescriptors over a tunneled
14402 connection, do not limit the length of our requests to what the
14403 Squid proxy is willing to handle. Part of ticket 9969.
14404 - Authorities can now vote on the correct digests and latest
14405 versions for different software packages. This allows packages
14406 that include Tor to use the Tor authority system as a way to get
14407 notified of updates and their correct digests. Implements proposal
14408 227. Closes ticket 10395.
14410 o Major features (guards):
14411 - Introduce the Guardfraction feature to improves load balancing on
14412 guard nodes. Specifically, it aims to reduce the traffic gap that
14413 guard nodes experience when they first get the Guard flag. This is
14414 a required step if we want to increase the guard lifetime to 9
14415 months or greater. Closes ticket 9321.
14417 o Major features (performance):
14418 - Make the CPU worker implementation more efficient by avoiding the
14419 kernel and lengthening pipelines. The original implementation used
14420 sockets to transfer data from the main thread to the workers, and
14421 didn't allow any thread to be assigned more than a single piece of
14422 work at once. The new implementation avoids communications
14423 overhead by making requests in shared memory, avoiding kernel IO
14424 where possible, and keeping more requests in flight at once.
14425 Implements ticket 9682.
14427 o Major features (relay):
14428 - Raise the minimum acceptable configured bandwidth rate for bridges
14429 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
14430 20 KiB/sec.) Closes ticket 13822.
14432 o Major bugfixes (exit node stability):
14433 - Fix an assertion failure that could occur under high DNS load.
14434 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
14435 diagnosed and fixed by "cypherpunks".
14437 o Major bugfixes (mixed relay-client operation):
14438 - When running as a relay and client at the same time (not
14439 recommended), if we decide not to use a new guard because we want
14440 to retry older guards, only close the locally-originating circuits
14441 passing through that guard. Previously we would close all the
14442 circuits through that guard. Fixes bug 9819; bugfix on
14443 0.2.1.1-alpha. Reported by "skruffy".
14445 o Minor features (build):
14446 - New --disable-system-torrc compile-time option to prevent Tor from
14447 looking for the system-wide torrc or torrc-defaults files.
14448 Resolves ticket 13037.
14450 o Minor features (controller):
14451 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
14452 events so controllers can observe circuit isolation inputs. Closes
14454 - ControlPort now supports the unix:/path/to/socket syntax as an
14455 alternative to the ControlSocket option, for consistency with
14456 SocksPort and HiddenServicePort. Closes ticket 14451.
14457 - New "GETINFO bw-event-cache" to get information about recent
14458 bandwidth events. Closes ticket 14128. Useful for controllers to
14459 get recent bandwidth history after the fix for ticket 13988.
14461 o Minor features (Denial of service resistance):
14462 - Count the total number of bytes used storing hidden service
14463 descriptors against the value of MaxMemInQueues. If we're low on
14464 memory, and more than 20% of our memory is used holding hidden
14465 service descriptors, free them until no more than 10% of our
14466 memory holds hidden service descriptors. Free the least recently
14467 fetched descriptors first. Resolves ticket 13806.
14468 - When we have recently been under memory pressure (over 3/4 of
14469 MaxMemInQueues is allocated), then allocate smaller zlib objects
14470 for small requests. Closes ticket 11791.
14472 o Minor features (geoip):
14473 - Update geoip and geoip6 files to the January 7 2015 Maxmind
14474 GeoLite2 Country database.
14476 o Minor features (guard nodes):
14477 - Reduce the time delay before saving guard status to disk from 10
14478 minutes to 30 seconds (or from one hour to 10 minutes if
14479 AvoidDiskWrites is set). Closes ticket 12485.
14481 o Minor features (hidden service):
14482 - Make Sybil attacks against hidden services harder by changing the
14483 minimum time required to get the HSDir flag from 25 hours up to 96
14484 hours. Addresses ticket 14149.
14485 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
14486 services to disable the anti-scanning feature introduced in
14487 0.2.6.2-alpha. With this option not set, a connection to an
14488 unlisted port closes the circuit. With this option set, only a
14489 RELAY_DONE cell is sent. Closes ticket 14084.
14491 o Minor features (interface):
14492 - Implement "-f -" command-line option to read torrc configuration
14493 from standard input, if you don't want to store the torrc file in
14494 the file system. Implements feature 13865.
14496 o Minor features (logging):
14497 - Add a count of unique clients to the bridge heartbeat message.
14498 Resolves ticket 6852.
14499 - Suppress "router info incompatible with extra info" message when
14500 reading extrainfo documents from cache. (This message got loud
14501 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
14503 - Elevate hidden service authorized-client message from DEBUG to
14504 INFO. Closes ticket 14015.
14506 o Minor features (stability):
14507 - Add assertions in our hash-table iteration code to check for
14508 corrupted values that could cause infinite loops. Closes
14511 o Minor features (systemd):
14512 - Various improvements and modernizations in systemd hardening
14513 support. Closes ticket 13805. Patch from Craig Andrews.
14515 o Minor features (testing networks):
14516 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
14517 and the default on a testing network to 2 minutes. Drop the
14518 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
14519 keep the default on a testing network at 30 seconds. This reduces
14520 HS bootstrap time to around 25 seconds. Also, change the default
14521 time in test-network.sh to match. Closes ticket 13401. Patch
14523 - Create TestingDirAuthVoteHSDir to correspond to
14524 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
14525 HSDir flag for the listed relays regardless of uptime or ORPort
14526 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
14527 Partial implementation for ticket 14067. Patch by "teor".
14529 o Minor features (tor2web mode):
14530 - Introduce the config option Tor2webRendezvousPoints, which allows
14531 clients in Tor2webMode to select a specific Rendezvous Point to be
14532 used in HS circuits. This might allow better performance for
14533 Tor2Web nodes. Implements ticket 12844.
14535 o Minor bugfixes (client DNS):
14536 - Report the correct cached DNS expiration times on SOCKS port or in
14537 DNS replies. Previously, we would report everything as "never
14538 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
14539 - Avoid a small memory leak when we find a cached answer for a
14540 reverse DNS lookup in a client-side DNS cache. (Remember, client-
14541 side DNS caching is off by default, and is not recommended.) Fixes
14542 bug 14259; bugfix on 0.2.0.1-alpha.
14544 o Minor bugfixes (client, automapping):
14545 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
14546 no value follows the option. Fixes bug 14142; bugfix on
14547 0.2.4.7-alpha. Patch by "teor".
14548 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
14549 14195; bugfix on 0.1.0.1-rc.
14550 - Prevent changes to other options from removing the wildcard value
14551 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
14553 - Allow MapAddress and AutomapHostsOnResolve to work together when
14554 an address is mapped into another address type (like .onion) that
14555 must be automapped at resolve time. Fixes bug 7555; bugfix
14558 o Minor bugfixes (client, bridges):
14559 - When we are using bridges and we had a network connectivity
14560 problem, only retry connecting to our currently configured
14561 bridges, not all bridges we know about and remember using. Fixes
14562 bug 14216; bugfix on 0.2.2.17-alpha.
14564 o Minor bugfixes (client, IPv6):
14565 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
14566 flag is not set; and not because the NoIPv4Traffic flag was set.
14567 Previously we'd looked at the NoIPv4Traffic flag for both types of
14568 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
14570 o Minor bugfixes (compilation):
14571 - The address of an array in the middle of a structure will always
14572 be non-NULL. clang recognises this and complains. Disable the
14573 tautologous and redundant check to silence this warning. Fixes bug
14574 14001; bugfix on 0.2.1.2-alpha.
14575 - Avoid warnings when building with systemd 209 or later. Fixes bug
14576 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
14577 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
14578 Addresses ticket 14188.
14579 - Build without warnings with the stock OpenSSL srtp.h header, which
14580 has a duplicate declaration of SSL_get_selected_srtp_profile().
14581 Fixes bug 14220; this is OpenSSL's bug, not ours.
14582 - Do not compile any code related to Tor2Web mode when Tor2Web mode
14583 is not enabled at compile time. Previously, this code was included
14584 in a disabled state. See discussion on ticket 12844.
14585 - Remove the --disable-threads configure option again. It was
14586 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
14587 14819; bugfix on 0.2.6.2-alpha.
14589 o Minor bugfixes (controller):
14590 - Report "down" in response to the "GETINFO entry-guards" command
14591 when relays are down with an unreachable_since value. Previously,
14592 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
14593 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
14594 14116; bugfix on 0.2.2.9-alpha.
14595 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
14596 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
14598 o Minor bugfixes (directory authority):
14599 - Allow directory authorities to fetch more data from one another if
14600 they find themselves missing lots of votes. Previously, they had
14601 been bumping against the 10 MB queued data limit. Fixes bug 14261;
14602 bugfix on 0.1.2.5-alpha.
14603 - Do not attempt to download extrainfo documents which we will be
14604 unable to validate with a matching server descriptor. Fixes bug
14605 13762; bugfix on 0.2.0.1-alpha.
14606 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
14607 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
14608 - Enlarge the buffer to read bwauth generated files to avoid an
14609 issue when parsing the file in dirserv_read_measured_bandwidths().
14610 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
14612 o Minor bugfixes (file handling):
14613 - Stop failing when key files are zero-length. Instead, generate new
14614 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
14615 on all versions of Tor. Patch by "teor".
14616 - Stop generating a fresh .old RSA onion key file when the .old file
14617 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
14618 - Avoid overwriting .old key files with empty key files.
14619 - Skip loading zero-length extrainfo store, router store, stats,
14620 state, and key files.
14621 - Avoid crashing when trying to reload a torrc specified as a
14622 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
14625 o Minor bugfixes (hidden services):
14626 - Close the introduction circuit when we have no more usable intro
14627 points, instead of waiting for it to time out. This also ensures
14628 that no follow-up HS descriptor fetch is triggered when the
14629 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
14630 - When fetching a hidden service descriptor for a down service that
14631 was recently up, do not keep refetching until we try the same
14632 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
14633 - Successfully launch Tor with a nonexistent hidden service
14634 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
14635 14106; bugfix on 0.2.6.2-alpha.
14637 o Minor bugfixes (logging):
14638 - Avoid crashing when there are more log domains than entries in
14639 domain_list. Bugfix on 0.2.3.1-alpha.
14640 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
14642 - Don't log messages to stdout twice when starting up. Fixes bug
14643 13993; bugfix on 0.2.6.1-alpha.
14645 o Minor bugfixes (parsing):
14646 - Stop accepting milliseconds (or other junk) at the end of
14647 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
14648 - Support two-number and three-number version numbers correctly, in
14649 case we change the Tor versioning system in the future. Fixes bug
14650 13661; bugfix on 0.0.8pre1.
14652 o Minor bugfixes (path counting):
14653 - When deciding whether the consensus lists any exit nodes, count
14654 the number listed in the consensus, not the number we have
14655 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
14656 - When deciding whether we have any exit nodes, only examine
14657 ExitNodes when the ExitNodes option is actually set. Fixes part of
14658 bug 14918; bugfix on 0.2.6.2-alpha.
14659 - Get rid of redundant and possibly scary warnings that we are
14660 missing directory information while we bootstrap. Fixes part of
14661 bug 14918; bugfix on 0.2.6.2-alpha.
14663 o Minor bugfixes (portability):
14664 - Fix the ioctl()-based network interface lookup code so that it
14665 will work on systems that have variable-length struct ifreq, for
14667 - Fix scheduler compilation on targets where char is unsigned. Fixes
14668 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
14670 o Minor bugfixes (sandbox):
14671 - Allow glibc fatal errors to be sent to stderr before Tor exits.
14672 Previously, glibc would try to write them to /dev/tty, and the
14673 sandbox would trap the call and make Tor exit prematurely. Fixes
14674 bug 14759; bugfix on 0.2.5.1-alpha.
14676 o Minor bugfixes (shutdown):
14677 - When shutting down, always call event_del() on lingering read or
14678 write events before freeing them. Otherwise, we risk double-frees
14679 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
14682 o Minor bugfixes (small memory leaks):
14683 - Avoid leaking memory when using IPv6 virtual address mappings.
14684 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
14687 o Minor bugfixes (statistics):
14688 - Increase period over which bandwidth observations are aggregated
14689 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
14691 o Minor bugfixes (systemd support):
14692 - Fix detection and operation of systemd watchdog. Fixes part of bug
14693 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
14694 - Run correctly under systemd with the RunAsDaemon option set. Fixes
14695 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
14696 - Inform the systemd supervisor about more changes in the Tor
14697 process status. Implements part of ticket 14141. Patch from
14699 - Cause the "--disable-systemd" option to actually disable systemd
14700 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
14703 o Minor bugfixes (TLS):
14704 - Check more thoroughly throughout the TLS code for possible
14705 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
14707 o Minor bugfixes (transparent proxy):
14708 - Use getsockname, not getsockopt, to retrieve the address for a
14709 TPROXY-redirected connection. Fixes bug 13796; bugfix
14712 o Code simplification and refactoring:
14713 - Move fields related to isolating and configuring client ports into
14714 a shared structure. Previously, they were duplicated across
14715 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
14716 to copy them correctly had been the cause of at least one bug in
14717 the past. Closes ticket 8546.
14718 - Refactor the get_interface_addresses_raw() doom-function into
14719 multiple smaller and simpler subfunctions. Cover the resulting
14720 subfunctions with unit-tests. Fixes a significant portion of
14722 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
14723 only for version <= 0.2.2.24 which is now deprecated. Closes
14725 - Remove a test for a long-defunct broken version-one
14729 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
14730 for writing the OpenBSD-specific tips. Resolves ticket 13702.
14731 - Make the tor-resolve documentation match its help string and its
14732 options. Resolves part of ticket 14325.
14733 - Log a more useful error message from tor-resolve when failing to
14734 look up a hidden service address. Resolves part of ticket 14325.
14736 o Downgraded warnings:
14737 - Don't warn when we've attempted to contact a relay using the wrong
14738 ntor onion key. Closes ticket 9635.
14740 o Removed features:
14741 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
14742 longer silently accepted as an alias for "ExitNodes".
14743 - The --enable-mempool and --enable-buf-freelists options, which
14744 were originally created to work around bad malloc implementations,
14745 no longer exist. They were off-by-default in 0.2.5. Closes
14749 - Make the checkdir/perms test complete successfully even if the
14750 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
14751 - Test that tor does not fail when key files are zero-length. Check
14752 that tor generates new keys, and overwrites the empty key files.
14753 - Test that tor generates new keys when keys are missing
14754 (existing behavior).
14755 - Test that tor does not overwrite key files that already contain
14756 data (existing behavior). Tests bug 13111. Patch by "teor".
14757 - New "make test-stem" target to run stem integration tests.
14758 Requires that the "STEM_SOURCE_DIR" environment variable be set.
14759 Closes ticket 14107.
14760 - Make the test_cmdline_args.py script work correctly on Windows.
14761 Patch from Gisle Vanem.
14762 - Move the slower unit tests into a new "./src/test/test-slow"
14763 binary that can be run independently of the other tests. Closes
14765 - Avoid undefined behavior when sampling huge values from the
14766 Laplace distribution. This made unittests fail on Raspberry Pi.
14767 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
14770 Changes in version 0.2.6.2-alpha - 2014-12-31
14771 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
14772 It introduces a major new backend for deciding when to send cells on
14773 channels, which should lead down the road to big performance
14774 increases. It contains security and statistics features for better
14775 work on hidden services, and numerous bugfixes.
14777 This release contains many new unit tests, along with major
14778 performance improvements for running testing networks using Chutney.
14779 Thanks to a series of patches contributed by "teor", testing networks
14780 should now bootstrap in seconds, rather than minutes.
14782 o Major features (relay, infrastructure):
14783 - Complete revision of the code that relays use to decide which cell
14784 to send next. Formerly, we selected the best circuit to write on
14785 each channel, but we didn't select among channels in any
14786 sophisticated way. Now, we choose the best circuits globally from
14787 among those whose channels are ready to deliver traffic.
14789 This patch implements a new inter-cmux comparison API, a global
14790 high/low watermark mechanism and a global scheduler loop for
14791 transmission prioritization across all channels as well as among
14792 circuits on one channel. This schedule is currently tuned to
14793 (tolerantly) avoid making changes in network performance, but it
14794 should form the basis for major circuit performance increases in
14795 the future. Code by Andrea; tuning by Rob Jansen; implements
14798 o Major features (hidden services):
14799 - Make HS port scanning more difficult by immediately closing the
14800 circuit when a user attempts to connect to a nonexistent port.
14801 Closes ticket 13667.
14802 - Add a HiddenServiceStatistics option that allows Tor relays to
14803 gather and publish statistics about the overall size and volume of
14804 hidden service usage. Specifically, when this option is turned on,
14805 an HSDir will publish an approximate number of hidden services
14806 that have published descriptors to it the past 24 hours. Also, if
14807 a relay has acted as a hidden service rendezvous point, it will
14808 publish the approximate amount of rendezvous cells it has relayed
14809 the past 24 hours. The statistics themselves are obfuscated so
14810 that the exact values cannot be derived. For more details see
14811 proposal 238, "Better hidden service stats from Tor relays". This
14812 feature is currently disabled by default. Implements feature 13192.
14814 o Major bugfixes (client, automap):
14815 - Repair automapping with IPv6 addresses. This automapping should
14816 have worked previously, but one piece of debugging code that we
14817 inserted to detect a regression actually caused the regression to
14818 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
14819 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
14822 o Major bugfixes (hidden services):
14823 - When closing an introduction circuit that was opened in parallel
14824 with others, don't mark the introduction point as unreachable.
14825 Previously, the first successful connection to an introduction
14826 point would make the other introduction points get marked as
14827 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
14829 o Directory authority changes:
14830 - Remove turtles as a directory authority.
14831 - Add longclaw as a new (v3) directory authority. This implements
14832 ticket 13296. This keeps the directory authority count at 9.
14834 o Major removed features:
14835 - Tor clients no longer support connecting to hidden services
14836 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
14837 option has been removed. (There shouldn't be any hidden services
14838 running these versions on the network.) Closes ticket 7803.
14840 o Minor features (client):
14841 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
14842 is enabled, reject requests with IP addresses as hostnames.
14843 Resolves ticket 13315.
14845 o Minor features (controller):
14846 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
14847 write an unscheduled heartbeat message to the log. Implements
14850 o Minor features (geoip):
14851 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
14854 o Minor features (hidden services):
14855 - When re-enabling the network, don't try to build introduction
14856 circuits until we have successfully built a circuit. This makes
14857 hidden services come up faster when the network is re-enabled.
14858 Patch from "akwizgran". Closes ticket 13447.
14859 - When we fail to retrieve a hidden service descriptor, send the
14860 controller an "HS_DESC FAILED" controller event. Implements
14862 - New HiddenServiceDirGroupReadable option to cause hidden service
14863 directories and hostname files to be created group-readable. Patch
14864 from "anon", David Stainton, and "meejah". Closes ticket 11291.
14866 o Minor features (systemd):
14867 - Where supported, when running with systemd, report successful
14868 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
14869 - When running with systemd, support systemd watchdog messages. Part
14870 of ticket 11016. Patch by Michael Scherer.
14872 o Minor features (transparent proxy):
14873 - Update the transparent proxy option checks to allow for both ipfw
14874 and pf on OS X. Closes ticket 14002.
14875 - Use the correct option when using IPv6 with transparent proxy
14876 support on Linux. Resolves 13808. Patch by Francisco Blas
14879 o Minor bugfixes (preventative security, C safety):
14880 - When reading a hexadecimal, base-32, or base-64 encoded value from
14881 a string, always overwrite the whole output buffer. This prevents
14882 some bugs where we would look at (but fortunately, not reveal)
14883 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
14885 - Clear all memory targeted by tor_addr_{to,from}_sockaddr(), not
14886 just the part that's used. This makes it harder for data leak bugs
14887 to occur in the event of other programming failures. Resolves
14890 o Minor bugfixes (client, microdescriptors):
14891 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
14892 computing which microdescriptors to download. This keeps us from
14893 erroneous download behavior if two microdescriptor digests ever
14894 have the same first 160 bits. Fixes part of bug 13399; bugfix
14896 - Reset a router's status if its microdescriptor digest changes,
14897 even if the first 160 bits remain the same. Fixes part of bug
14898 13399; bugfix on 0.2.3.1-alpha.
14900 o Minor bugfixes (compilation):
14901 - Silence clang warnings under --enable-expensive-hardening,
14902 including implicit truncation of 64 bit values to 32 bit, const
14903 char assignment to self, tautological compare, and additional
14904 parentheses around equality tests. Fixes bug 13577; bugfix
14906 - Fix a clang warning about checking whether an address in the
14907 middle of a structure is NULL. Fixes bug 14001; bugfix
14910 o Minor bugfixes (hidden services):
14911 - Correctly send a controller event when we find that a rendezvous
14912 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
14913 - Pre-check directory permissions for new hidden-services to avoid
14914 at least one case of "Bug: Acting on config options left us in a
14915 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
14916 - When adding a new hidden service (for example, via SETCONF), Tor
14917 no longer congratulates the user for running a relay. Fixes bug
14918 13941; bugfix on 0.2.6.1-alpha.
14919 - When fetching hidden service descriptors, we now check not only
14920 for whether we got the hidden service we had in mind, but also
14921 whether we got the particular descriptors we wanted. This prevents
14922 a class of inefficient but annoying DoS attacks by hidden service
14923 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
14926 o Minor bugfixes (Linux seccomp2 sandbox):
14927 - Make transparent proxy support work along with the seccomp2
14928 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
14929 by Francisco Blas Izquierdo Riera.
14930 - Fix a memory leak in tor-resolve when running with the sandbox
14931 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
14933 o Minor bugfixes (logging):
14934 - Downgrade warnings about RSA signature failures to info log level.
14935 Emit a warning when an extra info document is found incompatible
14936 with a corresponding router descriptor. Fixes bug 9812; bugfix
14938 - Make connection_ap_handshake_attach_circuit() log the circuit ID
14939 correctly. Fixes bug 13701; bugfix on 0.0.6.
14941 o Minor bugfixes (misc):
14942 - Stop allowing invalid address patterns like "*/24" that contain
14943 both a wildcard address and a bit prefix length. This affects all
14944 our address-range parsing code. Fixes bug 7484; bugfix
14947 o Minor bugfixes (testing networks, fast startup):
14948 - Allow Tor to build circuits using a consensus with no exits. If
14949 the consensus has no exits (typical of a bootstrapping test
14950 network), allow Tor to build circuits once enough descriptors have
14951 been downloaded. This assists in bootstrapping a testing Tor
14952 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
14954 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
14955 header to directory servers. This allows us to obtain consensuses
14956 promptly when the consensus interval is very short. This assists
14957 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
14958 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
14959 - Stop assuming that private addresses are local when checking
14960 reachability in a TestingTorNetwork. Instead, when testing, assume
14961 all OR connections are remote. (This is necessary due to many test
14962 scenarios running all relays on localhost.) This assists in
14963 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
14964 0.1.0.1-rc. Patch by "teor".
14965 - Avoid building exit circuits from a consensus with no exits. Now
14966 thanks to our fix for 13718, we accept a no-exit network as not
14967 wholly lost, but we need to remember not to try to build exit
14968 circuits on it. Closes ticket 13814; patch by "teor".
14969 - Stop requiring exits to have non-zero bandwithcapacity in a
14970 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
14971 ignore exit bandwidthcapacity. This assists in bootstrapping a
14972 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
14973 on 0.2.0.3-alpha. Patch by "teor".
14974 - Add "internal" to some bootstrap statuses when no exits are
14975 available. If the consensus does not contain Exits, Tor will only
14976 build internal circuits. In this case, relevant statuses will
14977 contain the word "internal" as indicated in the Tor control-
14978 spec.txt. When bootstrap completes, Tor will be ready to build
14979 internal circuits. If a future consensus contains Exits, exit
14980 circuits may become available. Fixes part of bug 13718; bugfix on
14981 0.2.4.10-alpha. Patch by "teor".
14982 - Decrease minimum consensus interval to 10 seconds when
14983 TestingTorNetwork is set, or 5 seconds for the first consensus.
14984 Fix assumptions throughout the code that assume larger intervals.
14985 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
14987 - Avoid excluding guards from path building in minimal test
14988 networks, when we're in a test network and excluding guards would
14989 exclude all relays. This typically occurs in incredibly small tor
14990 networks, and those using "TestingAuthVoteGuard *". Fixes part of
14991 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
14993 o Code simplification and refactoring:
14994 - Stop using can_complete_circuits as a global variable; access it
14995 with a function instead.
14996 - Avoid using operators directly as macro arguments: this lets us
14997 apply coccinelle transformations to our codebase more directly.
14998 Closes ticket 13172.
14999 - Combine the functions used to parse ClientTransportPlugin and
15000 ServerTransportPlugin into a single function. Closes ticket 6456.
15001 - Add inline functions and convenience macros for inspecting channel
15002 state. Refactor the code to use convenience macros instead of
15003 checking channel state directly. Fixes issue 7356.
15004 - Document all members of was_router_added_t and rename
15005 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
15006 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
15007 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
15008 constant instead of hardcoded value. Fixes issue 13840.
15009 - Refactor our generic strmap and digestmap types into a single
15010 implementation, so that we can add a new digest256map
15014 - Document the bridge-authority-only 'networkstatus-bridges' file.
15015 Closes ticket 13713; patch from "tom".
15016 - Fix typo in PredictedPortsRelevanceTime option description in
15017 manpage. Resolves issue 13707.
15018 - Stop suggesting that users specify relays by nickname: it isn't a
15019 good idea. Also, properly cross-reference how to specify relays in
15020 all parts of manual documenting options that take a list of
15021 relays. Closes ticket 13381.
15022 - Clarify the HiddenServiceDir option description in manpage to make
15023 it clear that relative paths are taken with respect to the current
15024 working directory. Also clarify that this behavior is not
15025 guaranteed to remain indefinitely. Fixes issue 13913.
15028 - New tests for many parts of channel, relay, and circuitmux
15029 functionality. Code by Andrea; part of 9262.
15030 - New tests for parse_transport_line(). Part of ticket 6456.
15031 - In the unit tests, use chgrp() to change the group of the unit
15032 test temporary directory to the current user, so that the sticky
15033 bit doesn't interfere with tests that check directory groups.
15035 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
15039 Changes in version 0.2.6.1-alpha - 2014-10-30
15040 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
15041 includes numerous code cleanups and new tests, and fixes a large
15042 number of annoying bugs. Out-of-memory conditions are handled better
15043 than in 0.2.5, pluggable transports have improved proxy support, and
15044 clients now use optimistic data for contacting hidden services. Also,
15045 we are now more robust to changes in what we consider a parseable
15046 directory object, so that tightening restrictions does not have a risk
15047 of introducing infinite download loops.
15049 This is the first alpha release in a new series, so expect there to be
15050 bugs. Users who would rather test out a more stable branch should stay
15051 with 0.2.5.x for now.
15053 o New compiler and system requirements:
15054 - Tor 0.2.6.x requires that your compiler support more of the C99
15055 language standard than before. The 'configure' script now detects
15056 whether your compiler supports C99 mid-block declarations and
15057 designated initializers. If it does not, Tor will not compile.
15059 We may revisit this requirement if it turns out that a significant
15060 number of people need to build Tor with compilers that don't
15061 bother implementing a 15-year-old standard. Closes ticket 13233.
15062 - Tor no longer supports systems without threading support. When we
15063 began working on Tor, there were several systems that didn't have
15064 threads, or where the thread support wasn't able to run the
15065 threads of a single process on multiple CPUs. That no longer
15066 holds: every system where Tor needs to run well now has threading
15067 support. Resolves ticket 12439.
15069 o Removed platform support:
15070 - We no longer include special code to build on Windows CE; as far
15071 as we know, nobody has used Tor on Windows CE in a very long time.
15072 Closes ticket 11446.
15074 o Major features (bridges):
15075 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
15076 transports if they are configured via the "TOR_PT_PROXY"
15077 environment variable. Implements proposal 232. Resolves
15080 o Major features (client performance, hidden services):
15081 - Allow clients to use optimistic data when connecting to a hidden
15082 service, which should remove a round-trip from hidden service
15083 initialization. See proposal 181 for details. Implements
15086 o Major features (directory system):
15087 - Upon receiving an unparseable directory object, if its digest
15088 matches what we expected, then don't try to download it again.
15089 Previously, when we got a descriptor we didn't like, we would keep
15090 trying to download it over and over. Closes ticket 11243.
15092 o Major features (sample torrc):
15093 - Add a new, infrequently-changed "torrc.minimal". This file is
15094 similar to torrc.sample, but it will change as infrequently as
15095 possible, for the benefit of users whose systems prompt them for
15096 intervention whenever a default configuration file is changed.
15097 Making this change allows us to update torrc.sample to be a more
15098 generally useful "sample torrc".
15100 o Major bugfixes (directory authorities):
15101 - Do not assign the HSDir flag to relays if they are not Valid, or
15102 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
15104 o Major bugfixes (directory bandwidth performance):
15105 - Don't flush the zlib buffer aggressively when compressing
15106 directory information for clients. This should save about 7% of
15107 the bandwidth currently used for compressed descriptors and
15108 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
15110 o Minor features (security, memory wiping):
15111 - Ensure we securely wipe keys from memory after
15112 crypto_digest_get_digest and init_curve25519_keypair_from_file
15113 have finished using them. Resolves ticket 13477.
15115 o Minor features (security, out-of-memory handling):
15116 - When handling an out-of-memory condition, allocate less memory for
15117 temporary data structures. Fixes issue 10115.
15118 - When handling an out-of-memory condition, consider more types of
15119 buffers, including those on directory connections, and zlib
15120 buffers. Resolves ticket 11792.
15123 - When identity keypair is generated for first time, log a
15124 congratulatory message that links to the new relay lifecycle
15125 document. Implements feature 10427.
15127 o Minor features (client):
15128 - Clients are now willing to send optimistic data (before they
15129 receive a 'connected' cell) to relays of any version. (Relays
15130 without support for optimistic data are no longer supported on the
15131 Tor network.) Resolves ticket 13153.
15133 o Minor features (directory authorities):
15134 - Don't list relays with a bandwidth estimate of 0 in the consensus.
15135 Implements a feature proposed during discussion of bug 13000.
15136 - In tor-gencert, report an error if the user provides the same
15137 argument more than once.
15138 - If a directory authority can't find a best consensus method in the
15139 votes that it holds, it now falls back to its favorite consensus
15140 method. Previously, it fell back to method 1. Neither of these is
15141 likely to get enough signatures, but "fall back to favorite"
15142 doesn't require us to maintain support an obsolete consensus
15143 method. Implements part of proposal 215.
15145 o Minor features (logging):
15146 - On Unix-like systems, you can now use named pipes as the target of
15147 the Log option, and other options that try to append to files.
15148 Closes ticket 12061. Patch from "carlo von lynX".
15149 - When opening a log file at startup, send it every log message that
15150 we generated between startup and opening it. Previously, log
15151 messages that were generated before opening the log file were only
15152 logged to stdout. Closes ticket 6938.
15153 - Add a TruncateLogFile option to overwrite logs instead of
15154 appending to them. Closes ticket 5583.
15156 o Minor features (portability, Solaris):
15157 - Threads are no longer disabled by default on Solaris; we believe
15158 that the versions of Solaris with broken threading support are all
15159 obsolete by now. Resolves ticket 9495.
15161 o Minor features (relay):
15162 - Re-check our address after we detect a changed IP address from
15163 getsockname(). This ensures that the controller command "GETINFO
15164 address" will report the correct value. Resolves ticket 11582.
15166 - A new AccountingRule option lets Relays set whether they'd like
15167 AccountingMax to be applied separately to inbound and outbound
15168 traffic, or applied to the sum of inbound and outbound traffic.
15169 Resolves ticket 961. Patch by "chobe".
15171 o Minor features (testing networks):
15172 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
15173 the "Exit" flag regardless of their uptime, bandwidth, or exit
15174 policy. TestingTorNetwork must be set for this option to have any
15175 effect. Previously, authorities would take up to 35 minutes to
15176 give nodes the Exit flag in a test network. Partially implements
15179 o Minor features (validation):
15180 - Check all date/time values passed to tor_timegm and
15181 parse_rfc1123_time for validity, taking leap years into account.
15182 Improves HTTP header validation. Implemented with bug 13476.
15183 - In correct_tm(), limit the range of values returned by system
15184 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
15185 This means we don't have to deal with negative or too large dates,
15186 even if a clock is wrong. Otherwise we might fail to read a file
15187 written by us which includes such a date. Fixes bug 13476.
15189 o Minor bugfixes (bridge clients):
15190 - When configured to use a bridge without an identity digest (not
15191 recommended), avoid launching an extra channel to it when
15192 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
15194 o Minor bugfixes (bridges):
15195 - When DisableNetwork is set, do not launch pluggable transport
15196 plugins, and if any are running, terminate them. Fixes bug 13213;
15197 bugfix on 0.2.3.6-alpha.
15199 o Minor bugfixes (C correctness):
15200 - Fix several instances of possible integer overflow/underflow/NaN.
15201 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
15203 - In circuit_build_times_calculate_timeout() in circuitstats.c,
15204 avoid dividing by zero in the pareto calculations. This traps
15205 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
15207 - Fix an integer overflow in format_time_interval(). Fixes bug
15208 13393; bugfix on 0.2.0.10-alpha.
15209 - Set the correct day of year value when the system's localtime(_r)
15210 or gmtime(_r) functions fail to set struct tm. Not externally
15211 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
15212 - Avoid unlikely signed integer overflow in tor_timegm on systems
15213 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
15215 o Minor bugfixes (client):
15216 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
15217 BadExit flag are not considered worthy candidates. Fixes bug
15218 13066; bugfix on 0.1.2.3-alpha.
15219 - Use the consensus schedule for downloading consensuses, and not
15220 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
15221 - Handle unsupported or malformed SOCKS5 requests properly by
15222 responding with the appropriate error message before closing the
15223 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
15225 o Minor bugfixes (client, torrc):
15226 - Stop modifying the value of our DirReqStatistics torrc option just
15227 because we're not a bridge or relay. This bug was causing Tor
15228 Browser users to write "DirReqStatistics 0" in their torrc files
15229 as if they had chosen to change the config. Fixes bug 4244; bugfix
15231 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
15232 that our options have changed every time we SIGHUP. Fixes bug
15233 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
15235 o Minor bugfixes (controller):
15236 - Return an error when the second or later arguments of the
15237 "setevents" controller command are invalid events. Previously we
15238 would return success while silently skipping invalid events. Fixes
15239 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
15241 o Minor bugfixes (directory system):
15242 - Always believe that v3 directory authorities serve extra-info
15243 documents, whether they advertise "caches-extra-info" or not.
15244 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15245 - When running as a v3 directory authority, advertise that you serve
15246 extra-info documents so that clients who want them can find them
15247 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
15248 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
15249 Previously, directories offering BRIDGE_DIRINFO and some other
15250 flag (i.e. microdescriptors or extrainfo) would be ignored when
15251 looking for bridges. Partially fixes bug 13163; bugfix
15254 o Minor bugfixes (networking):
15255 - Check for orconns and use connection_or_close_for_error() rather
15256 than connection_mark_for_close() directly in the getsockopt()
15257 failure case of connection_handle_write_impl(). Fixes bug 11302;
15258 bugfix on 0.2.4.4-alpha.
15260 o Minor bugfixes (relay):
15261 - When generating our family list, remove spaces from around the
15262 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
15263 - If our previous bandwidth estimate was 0 bytes, allow publishing a
15264 new relay descriptor immediately. Fixes bug 13000; bugfix
15267 o Minor bugfixes (testing networks):
15268 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
15269 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
15270 - Stop using the default authorities in networks which provide both
15271 AlternateDirAuthority and AlternateBridgeAuthority. Partially
15272 fixes bug 13163; bugfix on 0.2.0.13-alpha.
15274 o Minor bugfixes (testing):
15275 - Stop spawn test failures due to a race condition between the
15276 SIGCHLD handler updating the process status, and the test reading
15277 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
15279 o Minor bugfixes (testing, Windows):
15280 - Avoid passing an extra backslash when creating a temporary
15281 directory for running the unit tests on Windows. Fixes bug 12392;
15282 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
15284 o Minor bugfixes (windows):
15285 - Remove code to special-case handling of NTE_BAD_KEYSET when
15286 acquiring windows CryptoAPI context. This error can't actually
15287 occur for the parameters we're providing. Fixes bug 10816; bugfix
15290 o Minor bugfixes (zlib):
15291 - Avoid truncating a zlib stream when trying to finalize it with an
15292 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
15295 - Allow our configure script to build correctly with autoconf 2.62
15296 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
15297 - Improve the error message from ./configure to make it clear that
15298 when asciidoc has not been found, the user will have to either add
15299 --disable-asciidoc argument or install asciidoc. Resolves
15302 o Code simplification and refactoring:
15303 - Change the entry_is_live() function to take named bitfield
15304 elements instead of an unnamed list of booleans. Closes
15306 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
15307 Resolves ticket 12205.
15308 - Use calloc and reallocarray functions instead of multiply-
15309 then-malloc. This makes it less likely for us to fall victim to an
15310 integer overflow attack when allocating. Resolves ticket 12855.
15311 - Use the standard macro name SIZE_MAX, instead of our
15313 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
15314 functions which take them as arguments. Replace 0 with NO_DIRINFO
15315 in a function call for clarity. Seeks to prevent future issues
15317 - Avoid 4 null pointer errors under clang static analysis by using
15318 tor_assert() to prove that the pointers aren't null. Fixes
15320 - Rework the API of policies_parse_exit_policy() to use a bitmask to
15321 represent parsing options, instead of a confusing mess of
15322 booleans. Resolves ticket 8197.
15323 - Introduce a helper function to parse ExitPolicy in
15324 or_options_t structure.
15327 - Add a doc/TUNING document with tips for handling large numbers of
15328 TCP connections when running busy Tor relay. Update the warning
15329 message to point to this file when running out of sockets
15330 operating system is allowing to use simultaneously. Resolves
15333 o Removed features:
15334 - We no longer remind the user about configuration options that have
15335 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
15336 - Remove our old, non-weighted bandwidth-based node selection code.
15337 Previously, we used it as a fallback when we couldn't perform
15338 weighted bandwidth-based node selection. But that would only
15339 happen in the cases where we had no consensus, or when we had a
15340 consensus generated by buggy or ancient directory authorities. In
15341 either case, it's better to use the more modern, better maintained
15342 algorithm, with reasonable defaults for the weights. Closes
15344 - Remove the --disable-curve25519 configure option. Relays and
15345 clients now are required to support curve25519 and the
15347 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
15348 used to be deprecated synonyms for "StrictNodes", are now marked
15349 obsolete. Resolves ticket 12226.
15350 - Clients don't understand the BadDirectory flag in the consensus
15351 anymore, and ignore it.
15354 - Refactor the function that chooses guard nodes so that it can more
15355 easily be tested; write some tests for it.
15356 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
15357 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
15358 - Create unit tests for format_time_interval(). With bug 13393.
15359 - Add unit tests for tor_timegm signed overflow, tor_timegm and
15360 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
15361 tests (visible) fixes in bug 13476.
15362 - Add a "coverage-html" make target to generate HTML-visualized
15363 coverage results when building with --enable-coverage. (Requires
15364 lcov.) Patch from Kevin Murray.
15365 - Enable the backtrace handler (where supported) when running the
15367 - Revise all unit tests that used the legacy test_* macros to
15368 instead use the recommended tt_* macros. This patch was generated
15369 with coccinelle, to avoid manual errors. Closes ticket 13119.
15371 o Distribution (systemd):
15372 - systemd unit file: only allow tor to write to /var/lib/tor and
15373 /var/log/tor. The rest of the filesystem is accessible for reading
15374 only. Patch by intrigeri; resolves ticket 12751.
15375 - systemd unit file: ensure that the process and all its children
15376 can never gain new privileges. Patch by intrigeri; resolves
15378 - systemd unit file: set up /var/run/tor as writable for the Tor
15379 service. Patch by intrigeri; resolves ticket 13196.
15381 o Removed features (directory authorities):
15382 - Remove code that prevented authorities from listing Tor relays
15383 affected by CVE-2011-2769 as guards. These relays are already
15384 rejected altogether due to the minimum version requirement of
15385 0.2.3.16-alpha. Closes ticket 13152.
15386 - The "AuthDirRejectUnlisted" option no longer has any effect, as
15387 the fingerprints file (approved-routers) has been deprecated.
15388 - Directory authorities do not support being Naming dirauths anymore.
15389 The "NamingAuthoritativeDir" config option is now obsolete.
15390 - Directory authorities do not support giving out the BadDirectory
15392 - Directory authorities no longer advertise or support consensus
15393 methods 1 through 12 inclusive. These consensus methods were
15394 obsolete and/or insecure: maintaining the ability to support them
15395 served no good purpose. Implements part of proposal 215; closes
15398 o Testing (test-network.sh):
15399 - Stop using "echo -n", as some shells' built-in echo doesn't
15400 support "-n". Instead, use "/bin/echo -n". Partially fixes
15402 - Stop an apparent test-network hang when used with make -j2. Fixes
15404 - Add a --delay option to test-network.sh, which configures the
15405 delay before the chutney network tests for data transmission.
15406 Partially implements ticket 13161.
15409 Changes in version 0.2.5.10 - 2014-10-24
15410 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
15412 It adds several new security features, including improved
15413 denial-of-service resistance for relays, new compiler hardening
15414 options, and a system-call sandbox for hardened installations on Linux
15415 (requires seccomp2). The controller protocol has several new features,
15416 resolving IPv6 addresses should work better than before, and relays
15417 should be a little more CPU-efficient. We've added support for more
15418 OpenBSD and FreeBSD transparent proxy types. We've improved the build
15419 system and testing infrastructure to allow unit testing of more parts
15420 of the Tor codebase. Finally, we've addressed several nagging pluggable
15421 transport usability issues, and included numerous other small bugfixes
15422 and features mentioned below.
15424 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
15425 have accumulated many known flaws; everyone should upgrade.
15427 o Deprecated versions:
15428 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
15429 attention for some while.
15432 Changes in version 0.2.5.9-rc - 2014-10-20
15433 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
15434 series. It disables SSL3 in response to the recent "POODLE" attack
15435 (even though POODLE does not affect Tor). It also works around a crash
15436 bug caused by some operating systems' response to the "POODLE" attack
15437 (which does affect Tor). It also contains a few miscellaneous fixes.
15439 o Major security fixes:
15440 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15441 today support TLS 1.0 or later, so we can safely turn off support
15442 for this old (and insecure) protocol. Fixes bug 13426.
15444 o Major bugfixes (openssl bug workaround):
15445 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15446 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15447 13471. This is a workaround for an OpenSSL bug.
15450 - Disable the sandbox name resolver cache when running tor-resolve:
15451 tor-resolve doesn't use the sandbox code, and turning it on was
15452 breaking attempts to do tor-resolve on a non-default server on
15453 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
15455 o Compilation fixes:
15456 - Build and run correctly on systems like OpenBSD-current that have
15457 patched OpenSSL to remove get_cipher_by_char and/or its
15458 implementations. Fixes issue 13325.
15460 o Downgraded warnings:
15461 - Downgrade the severity of the 'unexpected sendme cell from client'
15462 from 'warn' to 'protocol warning'. Closes ticket 8093.
15465 Changes in version 0.2.4.25 - 2014-10-20
15466 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
15467 (even though POODLE does not affect Tor). It also works around a crash
15468 bug caused by some operating systems' response to the "POODLE" attack
15469 (which does affect Tor).
15471 o Major security fixes (also in 0.2.5.9-rc):
15472 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
15473 today support TLS 1.0 or later, so we can safely turn off support
15474 for this old (and insecure) protocol. Fixes bug 13426.
15476 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
15477 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
15478 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
15479 13471. This is a workaround for an OpenSSL bug.
15482 Changes in version 0.2.5.8-rc - 2014-09-22
15483 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
15484 series. It fixes a bug that affects consistency and speed when
15485 connecting to hidden services, and it updates the location of one of
15486 the directory authorities.
15489 - Clients now send the correct address for their chosen rendezvous
15490 point when trying to access a hidden service. They used to send
15491 the wrong address, which would still work some of the time because
15492 they also sent the identity digest of the rendezvous point, and if
15493 the hidden service happened to try connecting to the rendezvous
15494 point from a relay that already had a connection open to it,
15495 the relay would reuse that connection. Now connections to hidden
15496 services should be more robust and faster. Also, this bug meant
15497 that clients were leaking to the hidden service whether they were
15498 on a little-endian (common) or big-endian (rare) system, which for
15499 some users might have reduced their anonymity. Fixes bug 13151;
15500 bugfix on 0.2.1.5-alpha.
15502 o Directory authority changes:
15503 - Change IP address for gabelmoo (v3 directory authority).
15506 Changes in version 0.2.4.24 - 2014-09-22
15507 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
15508 connecting to hidden services, and it updates the location of one of
15509 the directory authorities.
15512 - Clients now send the correct address for their chosen rendezvous
15513 point when trying to access a hidden service. They used to send
15514 the wrong address, which would still work some of the time because
15515 they also sent the identity digest of the rendezvous point, and if
15516 the hidden service happened to try connecting to the rendezvous
15517 point from a relay that already had a connection open to it,
15518 the relay would reuse that connection. Now connections to hidden
15519 services should be more robust and faster. Also, this bug meant
15520 that clients were leaking to the hidden service whether they were
15521 on a little-endian (common) or big-endian (rare) system, which for
15522 some users might have reduced their anonymity. Fixes bug 13151;
15523 bugfix on 0.2.1.5-alpha.
15525 o Directory authority changes:
15526 - Change IP address for gabelmoo (v3 directory authority).
15528 o Minor features (geoip):
15529 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15533 Changes in version 0.2.5.7-rc - 2014-09-11
15534 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
15535 release series, and some long-standing bugs related to ORPort reachability
15536 testing and failure to send CREATE cells. It is the first release
15537 candidate for the Tor 0.2.5.x series.
15539 o Major bugfixes (client, startup):
15540 - Start making circuits as soon as DisabledNetwork is turned off.
15541 When Tor started with DisabledNetwork set, it would correctly
15542 conclude that it shouldn't build circuits, but it would mistakenly
15543 cache this conclusion, and continue believing it even when
15544 DisableNetwork is set to 0. Fixes the bug introduced by the fix
15545 for bug 11200; bugfix on 0.2.5.4-alpha.
15546 - Resume expanding abbreviations for command-line options. The fix
15547 for bug 4647 accidentally removed our hack from bug 586 that
15548 rewrote HashedControlPassword to __HashedControlSessionPassword
15549 when it appears on the commandline (which allowed the user to set
15550 her own HashedControlPassword in the torrc file while the
15551 controller generates a fresh session password for each run). Fixes
15552 bug 12948; bugfix on 0.2.5.1-alpha.
15553 - Warn about attempts to run hidden services and relays in the same
15554 process: that's probably not a good idea. Closes ticket 12908.
15556 o Major bugfixes (relay):
15557 - Avoid queuing or sending destroy cells for circuit ID zero when we
15558 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
15559 Found and fixed by "cypherpunks".
15560 - Fix ORPort reachability detection on relays running behind a
15561 proxy, by correctly updating the "local" mark on the controlling
15562 channel when changing the address of an or_connection_t after the
15563 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
15565 o Minor features (bridge):
15566 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
15567 cookie file for the ExtORPort g+r by default.
15569 o Minor features (geoip):
15570 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
15573 o Minor bugfixes (logging):
15574 - Reduce the log severity of the "Pluggable transport proxy does not
15575 provide any needed transports and will not be launched." message,
15576 since Tor Browser includes several ClientTransportPlugin lines in
15577 its torrc-defaults file, leading every Tor Browser user who looks
15578 at her logs to see these notices and wonder if they're dangerous.
15579 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
15580 - Downgrade "Unexpected onionskin length after decryption" warning
15581 to a protocol-warn, since there's nothing relay operators can do
15582 about a client that sends them a malformed create cell. Resolves
15583 bug 12996; bugfix on 0.0.6rc1.
15584 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
15585 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
15586 - When logging information about an EXTEND2 or EXTENDED2 cell, log
15587 their names correctly. Fixes part of bug 12700; bugfix
15589 - When logging information about a relay cell whose command we don't
15590 recognize, log its command as an integer. Fixes part of bug 12700;
15591 bugfix on 0.2.1.10-alpha.
15592 - Escape all strings from the directory connection before logging
15593 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
15595 o Minor bugfixes (controller):
15596 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
15597 bug 12864; bugfix on 0.2.5.1-alpha.
15598 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
15599 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
15602 o Minor bugfixes (compilation):
15603 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
15604 bugfix on 0.2.5.5-alpha.
15605 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
15606 0.2.5.1-alpha. Patch from "NewEraCracker".
15607 - In routerlist_assert_ok(), don't take the address of a
15608 routerinfo's cache_info member unless that routerinfo is non-NULL.
15609 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
15610 - Fix a large number of false positive warnings from the clang
15611 analyzer static analysis tool. This should make real warnings
15612 easier for clang analyzer to find. Patch from "teor". Closes
15615 o Distribution (systemd):
15616 - Verify configuration file via ExecStartPre in the systemd unit
15617 file. Patch from intrigeri; resolves ticket 12730.
15618 - Explicitly disable RunAsDaemon in the systemd unit file. Our
15619 current systemd unit uses "Type = simple", so systemd does not
15620 expect tor to fork. If the user has "RunAsDaemon 1" in their
15621 torrc, then things won't work as expected. This is e.g. the case
15622 on Debian (and derivatives), since there we pass "--defaults-torrc
15623 /usr/share/tor/tor-service-defaults-torrc" (that contains
15624 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
15628 - Adjust the URLs in the README to refer to the new locations of
15629 several documents on the website. Fixes bug 12830. Patch from
15631 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
15635 Changes in version 0.2.5.6-alpha - 2014-07-28
15636 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
15637 risk from guard rotation, and fixes a variety of other issues to get
15638 us closer to a release candidate.
15640 o Major features (also in 0.2.4.23):
15641 - Make the number of entry guards configurable via a new
15642 NumEntryGuards consensus parameter, and the number of directory
15643 guards configurable via a new NumDirectoryGuards consensus
15644 parameter. Implements ticket 12688.
15646 o Major bugfixes (also in 0.2.4.23):
15647 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15648 implementation that caused incorrect results on 32-bit
15649 implementations when certain malformed inputs were used along with
15650 a small class of private ntor keys. This bug does not currently
15651 appear to allow an attacker to learn private keys or impersonate a
15652 Tor server, but it could provide a means to distinguish 32-bit Tor
15653 implementations from 64-bit Tor implementations. Fixes bug 12694;
15654 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15658 - Perform circuit cleanup operations even when circuit
15659 construction operations are disabled (because the network is
15660 disabled, or because there isn't enough directory information).
15661 Previously, when we were not building predictive circuits, we
15662 were not closing expired circuits either. Fixes bug 8387; bugfix on
15663 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
15664 became more strict about when we have "enough directory information
15665 to build circuits".
15668 - Authorities now assign the Guard flag to the fastest 25% of the
15669 network (it used to be the fastest 50%). Also raise the consensus
15670 weight that guarantees the Guard flag from 250 to 2000. For the
15671 current network, this results in about 1100 guards, down from 2500.
15672 This step paves the way for moving the number of entry guards
15673 down to 1 (proposal 236) while still providing reasonable expected
15674 performance for most users. Implements ticket 12690.
15675 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15677 - Slightly enhance the diagnostic message for bug 12184.
15679 o Minor bugfixes (also in 0.2.4.23):
15680 - Warn and drop the circuit if we receive an inbound 'relay early'
15681 cell. Those used to be normal to receive on hidden service circuits
15682 due to bug 1038, but the buggy Tor versions are long gone from
15683 the network so we can afford to resume watching for them. Resolves
15684 the rest of bug 1038; bugfix on 0.2.1.19.
15685 - Correct a confusing error message when trying to extend a circuit
15686 via the control protocol but we don't know a descriptor or
15687 microdescriptor for one of the specified relays. Fixes bug 12718;
15688 bugfix on 0.2.3.1-alpha.
15691 - Fix compilation when building with bufferevents enabled. (This
15692 configuration is still not expected to work, however.)
15693 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
15694 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
15696 - Compile correctly with builds and forks of OpenSSL (such as
15697 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
15698 0.2.1.1-alpha. Patch from "dhill".
15701 Changes in version 0.2.4.23 - 2014-07-28
15702 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
15703 guard rotation, and also backports several important fixes from the
15704 Tor 0.2.5 alpha release series.
15707 - Clients now look at the "usecreatefast" consensus parameter to
15708 decide whether to use CREATE_FAST or CREATE cells for the first hop
15709 of their circuit. This approach can improve security on connections
15710 where Tor's circuit handshake is stronger than the available TLS
15711 connection security levels, but the tradeoff is more computational
15712 load on guard relays. Implements proposal 221. Resolves ticket 9386.
15713 - Make the number of entry guards configurable via a new
15714 NumEntryGuards consensus parameter, and the number of directory
15715 guards configurable via a new NumDirectoryGuards consensus
15716 parameter. Implements ticket 12688.
15719 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
15720 implementation that caused incorrect results on 32-bit
15721 implementations when certain malformed inputs were used along with
15722 a small class of private ntor keys. This bug does not currently
15723 appear to allow an attacker to learn private keys or impersonate a
15724 Tor server, but it could provide a means to distinguish 32-bit Tor
15725 implementations from 64-bit Tor implementations. Fixes bug 12694;
15726 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
15730 - Warn and drop the circuit if we receive an inbound 'relay early'
15731 cell. Those used to be normal to receive on hidden service circuits
15732 due to bug 1038, but the buggy Tor versions are long gone from
15733 the network so we can afford to resume watching for them. Resolves
15734 the rest of bug 1038; bugfix on 0.2.1.19.
15735 - Correct a confusing error message when trying to extend a circuit
15736 via the control protocol but we don't know a descriptor or
15737 microdescriptor for one of the specified relays. Fixes bug 12718;
15738 bugfix on 0.2.3.1-alpha.
15739 - Avoid an illegal read from stack when initializing the TLS
15740 module using a version of OpenSSL without all of the ciphers
15741 used by the v2 link handshake. Fixes bug 12227; bugfix on
15742 0.2.4.8-alpha. Found by "starlight".
15745 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
15749 Changes in version 0.2.5.5-alpha - 2014-06-18
15750 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
15751 0.2.5.x release series, including a couple of DoS issues, some
15752 performance regressions, a large number of bugs affecting the Linux
15753 seccomp2 sandbox code, and various other bugfixes. It also adds
15754 diagnostic bugfixes for a few tricky issues that we're trying to
15757 o Major features (security, traffic analysis resistance):
15758 - Several major improvements to the algorithm used to decide when to
15759 close TLS connections. Previous versions of Tor closed connections
15760 at a fixed interval after the last time a non-padding cell was
15761 sent over the connection, regardless of the target of the
15762 connection. Now, we randomize the intervals by adding up to 50% of
15763 their base value, we measure the length of time since connection
15764 last had at least one circuit, and we allow connections to known
15765 ORs to remain open a little longer (15 minutes instead of 3
15766 minutes minimum). These changes should improve Tor's resistance
15767 against some kinds of traffic analysis, and lower some overhead
15768 from needlessly closed connections. Fixes ticket 6799.
15769 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
15771 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
15772 - Fix a memory leak that could occur if a microdescriptor parse
15773 fails during the tokenizing step. This bug could enable a memory
15774 exhaustion attack by directory servers. Fixes bug 11649; bugfix
15777 o Major bugfixes (security, directory authorities):
15778 - Directory authorities now include a digest of each relay's
15779 identity key as a part of its microdescriptor.
15781 This is a workaround for bug 11743 (reported by "cypherpunks"),
15782 where Tor clients do not support receiving multiple
15783 microdescriptors with the same SHA256 digest in the same
15784 consensus. When clients receive a consensus like this, they only
15785 use one of the relays. Without this fix, a hostile relay could
15786 selectively disable some client use of target relays by
15787 constructing a router descriptor with a different identity and the
15788 same microdescriptor parameters and getting the authorities to
15789 list it in a microdescriptor consensus. This fix prevents an
15790 attacker from causing a microdescriptor collision, because the
15791 router's identity is not forgeable.
15793 o Major bugfixes (relay):
15794 - Use a direct dirport connection when uploading non-anonymous
15795 descriptors to the directory authorities. Previously, relays would
15796 incorrectly use tunnel connections under a fairly wide variety of
15797 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
15798 - When a circuit accidentally has the same circuit ID for its
15799 forward and reverse direction, correctly detect the direction of
15800 cells using that circuit. Previously, this bug made roughly one
15801 circuit in a million non-functional. Fixes bug 12195; this is a
15802 bugfix on every version of Tor.
15804 o Major bugfixes (client, pluggable transports):
15805 - When managing pluggable transports, use OS notification facilities
15806 to learn if they have crashed, and don't attempt to kill any
15807 process that has already exited. Fixes bug 8746; bugfix
15810 o Minor features (diagnostic):
15811 - When logging a warning because of bug 7164, additionally check the
15812 hash table for consistency (as proposed on ticket 11737). This may
15813 help diagnose bug 7164.
15814 - When we log a heartbeat, log how many one-hop circuits we have
15815 that are at least 30 minutes old, and log status information about
15816 a few of them. This is an attempt to track down bug 8387.
15817 - When encountering an unexpected CR while writing text to a file on
15818 Windows, log the name of the file. Should help diagnosing
15820 - Give more specific warnings when a client notices that an onion
15821 handshake has failed. Fixes ticket 9635.
15822 - Add significant new logging code to attempt to diagnose bug 12184,
15823 where relays seem to run out of available circuit IDs.
15824 - Improve the diagnostic log message for bug 8387 even further to
15825 try to improve our odds of figuring out why one-hop directory
15826 circuits sometimes do not get closed.
15828 o Minor features (security, memory management):
15829 - Memory allocation tricks (mempools and buffer freelists) are now
15830 disabled by default. You can turn them back on with
15831 --enable-mempools and --enable-buf-freelists respectively. We're
15832 disabling these features because malloc performance is good enough
15833 on most platforms, and a similar feature in OpenSSL exacerbated
15834 exploitation of the Heartbleed attack. Resolves ticket 11476.
15836 o Minor features (security):
15837 - Apply the secure SipHash-2-4 function to the hash table mapping
15838 circuit IDs and channels to circuits. We missed this one when we
15839 were converting all the other hash functions to use SipHash back
15840 in 0.2.5.3-alpha. Resolves ticket 11750.
15842 o Minor features (build):
15843 - The configure script has a --disable-seccomp option to turn off
15844 support for libseccomp on systems that have it, in case it (or
15845 Tor's use of it) is broken. Resolves ticket 11628.
15847 o Minor features (other):
15848 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
15851 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
15852 - When running a hidden service, do not allow TunneledDirConns 0;
15853 this will keep the hidden service from running, and also
15854 make it publish its descriptors directly over HTTP. Fixes bug 10849;
15855 bugfix on 0.2.1.1-alpha.
15857 o Minor bugfixes (performance):
15858 - Avoid a bug where every successful connection made us recompute
15859 the flag telling us whether we have sufficient information to
15860 build circuits. Previously, we would forget our cached value
15861 whenever we successfully opened a channel (or marked a router as
15862 running or not running for any other reason), regardless of
15863 whether we had previously believed the router to be running. This
15864 forced us to run an expensive update operation far too often.
15865 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
15866 - Avoid using tor_memeq() for checking relay cell integrity. This
15867 removes a possible performance bottleneck. Fixes part of bug
15868 12169; bugfix on 0.2.1.31.
15870 o Minor bugfixes (compilation):
15871 - Fix compilation of test_status.c when building with MVSC. Bugfix
15872 on 0.2.5.4-alpha. Patch from Gisle Vanem.
15873 - Resolve GCC complaints on OpenBSD about discarding constness in
15874 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
15875 on 0.1.1.23. Patch from Dana Koch.
15876 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
15877 treatment of long and time_t as comparable types. Fixes part of
15878 bug 11633. Patch from Dana Koch.
15879 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
15880 11623; bugfix on 0.2.5.3-alpha.
15881 - When deciding whether to build the 64-bit curve25519
15882 implementation, detect platforms where we can compile 128-bit
15883 arithmetic but cannot link it. Fixes bug 11729; bugfix on
15884 0.2.4.8-alpha. Patch from "conradev".
15885 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
15886 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
15887 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
15890 o Minor bugfixes (Directory server):
15891 - When sending a compressed set of descriptors or microdescriptors,
15892 make sure to finalize the zlib stream. Previously, we would write
15893 all the compressed data, but if the last descriptor we wanted to
15894 send was missing or too old, we would not mark the stream as
15895 finished. This caused problems for decompression tools. Fixes bug
15896 11648; bugfix on 0.1.1.23.
15898 o Minor bugfixes (Linux seccomp sandbox):
15899 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
15900 11622; bugfix on 0.2.5.1-alpha.
15901 - Avoid crashing when re-opening listener ports with the seccomp
15902 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
15903 - Avoid crashing with the seccomp sandbox enabled along with
15904 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
15905 - When we receive a SIGHUP with the sandbox enabled, correctly
15906 support rotating our log files. Fixes bug 12032; bugfix
15908 - Avoid crash when running with sandboxing enabled and
15909 DirReqStatistics not disabled. Fixes bug 12035; bugfix
15911 - Fix a "BUG" warning when trying to write bridge-stats files with
15912 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
15914 - Prevent the sandbox from crashing on startup when run with the
15915 --enable-expensive-hardening configuration option. Fixes bug
15916 11477; bugfix on 0.2.5.4-alpha.
15917 - When running with DirPortFrontPage and sandboxing both enabled,
15918 reload the DirPortFrontPage correctly when restarting. Fixes bug
15919 12028; bugfix on 0.2.5.1-alpha.
15920 - Don't try to enable the sandbox when using the Tor binary to check
15921 its configuration, hash a passphrase, or so on. Doing so was
15922 crashing on startup for some users. Fixes bug 11609; bugfix
15924 - Avoid warnings when running with sandboxing and node statistics
15925 enabled at the same time. Fixes part of 12064; bugfix on
15926 0.2.5.1-alpha. Patch from Michael Wolf.
15927 - Avoid warnings when running with sandboxing enabled at the same
15928 time as cookie authentication, hidden services, or directory
15929 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
15930 - Do not allow options that require calls to exec to be enabled
15931 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
15932 bug 12043; bugfix on 0.2.5.1-alpha.
15933 - Handle failures in getpwnam()/getpwuid() when running with the
15934 User option set and the Linux syscall sandbox enabled. Fixes bug
15935 11946; bugfix on 0.2.5.1-alpha.
15936 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
15937 to avoid calling getaddrinfo() after installing the sandbox
15938 filters. Previously, it preloaded a cache with the IPv4 address
15939 for our hostname, and nothing else. Now, it loads the cache with
15940 every address that it used to initialize the Tor process. Fixes
15941 bug 11970; bugfix on 0.2.5.1-alpha.
15943 o Minor bugfixes (pluggable transports):
15944 - Enable the ExtORPortCookieAuthFile option, to allow changing the
15945 default location of the authentication token for the extended OR
15946 Port as used by sever-side pluggable transports. We had
15947 implemented this option before, but the code to make it settable
15948 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
15949 - Avoid another 60-second delay when starting Tor in a pluggable-
15950 transport-using configuration when we already have cached
15951 descriptors for our bridges. Fixes bug 11965; bugfix
15954 o Minor bugfixes (client):
15955 - Avoid "Tried to open a socket with DisableNetwork set" warnings
15956 when starting a client with bridges configured and DisableNetwork
15957 set. (Tor launcher starts Tor with DisableNetwork set the first
15958 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
15960 o Minor bugfixes (testing):
15961 - The Python parts of the test scripts now work on Python 3 as well
15962 as Python 2, so systems where '/usr/bin/python' is Python 3 will
15963 no longer have the tests break. Fixes bug 11608; bugfix
15965 - When looking for versions of python that we could run the tests
15966 with, check for "python2.7" and "python3.3"; previously we were
15967 only looking for "python", "python2", and "python3". Patch from
15968 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
15969 - Fix all valgrind warnings produced by the unit tests. There were
15970 over a thousand memory leak warnings previously, mostly produced
15971 by forgetting to free things in the unit test code. Fixes bug
15972 11618, bugfixes on many versions of Tor.
15974 o Minor bugfixes (tor-fw-helper):
15975 - Give a correct log message when tor-fw-helper fails to launch.
15976 (Previously, we would say something like "tor-fw-helper sent us a
15977 string we could not parse".) Fixes bug 9781; bugfix
15980 o Minor bugfixes (relay, threading):
15981 - Check return code on spawn_func() in cpuworker code, so that we
15982 don't think we've spawned a nonworking cpuworker and write junk to
15983 it forever. Fix related to bug 4345; bugfix on all released Tor
15984 versions. Found by "skruffy".
15985 - Use a pthread_attr to make sure that spawn_func() cannot return an
15986 error while at the same time launching a thread. Fix related to
15987 bug 4345; bugfix on all released Tor versions. Reported
15990 o Minor bugfixes (relay, oom prevention):
15991 - Correctly detect the total available system memory. We tried to do
15992 this in 0.2.5.4-alpha, but the code was set up to always return an
15993 error value, even on success. Fixes bug 11805; bugfix
15996 o Minor bugfixes (relay, other):
15997 - We now drop CREATE cells for already-existent circuit IDs and for
15998 zero-valued circuit IDs, regardless of other factors that might
15999 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
16001 - Avoid an illegal read from stack when initializing the TLS module
16002 using a version of OpenSSL without all of the ciphers used by the
16003 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
16005 - When rejecting DATA cells for stream_id zero, still count them
16006 against the circuit's deliver window so that we don't fail to send
16007 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
16009 o Minor bugfixes (logging):
16010 - Fix a misformatted log message about delayed directory fetches.
16011 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
16012 - Squelch a spurious LD_BUG message "No origin circuit for
16013 successful SOCKS stream" in certain hidden service failure cases;
16017 - Include a tor.service file in contrib/dist for use with systemd.
16018 Some distributions will be able to use this file unmodified;
16019 others will need to tweak it, or write their own. Patch from Jamie
16020 Nguyen; resolves ticket 8368.
16023 - Clean up several option names in the manpage to match their real
16024 names, add the missing documentation for a couple of testing and
16025 directory authority options, remove the documentation for a
16026 V2-directory fetching option that no longer exists. Resolves
16028 - Correct the documentation so that it lists the correct directory
16029 for the stats files. (They are in a subdirectory called "stats",
16031 - In the manpage, move more authority-only options into the
16032 directory authority section so that operators of regular directory
16033 caches don't get confused.
16036 - The contrib directory has been sorted and tidied. Before, it was
16037 an unsorted dumping ground for useful and not-so-useful things.
16038 Now, it is divided based on functionality, and the items which
16039 seemed to be nonfunctional or useless have been removed. Resolves
16040 ticket 8966; based on patches from "rl1987".
16043 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
16044 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
16045 - The TunnelDirConns and PreferTunnelledDirConns options no longer
16046 exist; tunneled directory connections have been available since
16047 0.1.2.5-alpha, and turning them off is not a good idea. This is a
16048 brute-force fix for 10849, where "TunnelDirConns 0" would break
16052 Changes in version 0.2.4.22 - 2014-05-16
16053 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
16054 alpha release series. These include blocking all authority signing
16055 keys that may have been affected by the OpenSSL "heartbleed" bug,
16056 choosing a far more secure set of TLS ciphersuites by default, closing
16057 a couple of memory leaks that could be used to run a target relay out
16058 of RAM, and several others.
16060 o Major features (security, backport from 0.2.5.4-alpha):
16061 - Block authority signing keys that were used on authorities
16062 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
16063 don't have any evidence that these keys _were_ compromised; we're
16064 doing this to be prudent.) Resolves ticket 11464.
16066 o Major bugfixes (security, OOM):
16067 - Fix a memory leak that could occur if a microdescriptor parse
16068 fails during the tokenizing step. This bug could enable a memory
16069 exhaustion attack by directory servers. Fixes bug 11649; bugfix
16072 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
16073 - The relay ciphersuite list is now generated automatically based on
16074 uniform criteria, and includes all OpenSSL ciphersuites with
16075 acceptable strength and forward secrecy. Previously, we had left
16076 some perfectly fine ciphersuites unsupported due to omission or
16077 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
16078 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16079 - Relays now trust themselves to have a better view than clients of
16080 which TLS ciphersuites are better than others. (Thanks to bug
16081 11513, the relay list is now well-considered, whereas the client
16082 list has been chosen mainly for anti-fingerprinting purposes.)
16083 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16084 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16085 AES128. Resolves ticket 11528.
16086 - Clients now try to advertise the same list of ciphersuites as
16087 Firefox 28. This change enables selection of (fast) GCM
16088 ciphersuites, disables some strange old ciphers, and stops
16089 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16090 Resolves ticket 11438.
16092 o Minor bugfixes (configuration, security):
16093 - When running a hidden service, do not allow TunneledDirConns 0:
16094 trying to set that option together with a hidden service would
16095 otherwise prevent the hidden service from running, and also make
16096 it publish its descriptors directly over HTTP. Fixes bug 10849;
16097 bugfix on 0.2.1.1-alpha.
16099 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
16100 - Avoid sending a garbage value to the controller when a circuit is
16101 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16103 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
16104 - Stop leaking memory when we successfully resolve a PTR record.
16105 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16107 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
16108 - Avoid 60-second delays in the bootstrapping process when Tor is
16109 launching for a second time while using bridges. Fixes bug 9229;
16110 bugfix on 0.2.0.3-alpha.
16112 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
16113 - Give the correct URL in the warning message when trying to run a
16114 relay on an ancient version of Windows. Fixes bug 9393.
16116 o Minor bugfixes (compilation):
16117 - Fix a compilation error when compiling with --disable-curve25519.
16118 Fixes bug 9700; bugfix on 0.2.4.17-rc.
16121 - Downgrade the warning severity for the the "md was still
16122 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
16123 for trying to diagnose this bug, and the current warning in
16124 earlier versions of tor achieves nothing useful. Addresses warning
16127 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
16128 - When we run out of usable circuit IDs on a channel, log only one
16129 warning for the whole channel, and describe how many circuits
16130 there were on the channel. Fixes part of ticket 11553.
16132 o Minor features (security, backport from 0.2.5.4-alpha):
16133 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
16134 leave the default at 8GBytes), to better support Raspberry Pi
16135 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
16137 o Documentation (backport from 0.2.5.4-alpha):
16138 - Correctly document that we search for a system torrc file before
16139 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16143 Changes in version 0.2.5.4-alpha - 2014-04-25
16144 Tor 0.2.5.4-alpha includes several security and performance
16145 improvements for clients and relays, including blacklisting authority
16146 signing keys that were used while susceptible to the OpenSSL
16147 "heartbleed" bug, fixing two expensive functions on busy relays,
16148 improved TLS ciphersuite preference lists, support for run-time
16149 hardening on compilers that support AddressSanitizer, and more work on
16150 the Linux sandbox code.
16152 There are also several usability fixes for clients (especially clients
16153 that use bridges), two new TransPort protocols supported (one on
16154 OpenBSD, one on FreeBSD), and various other bugfixes.
16156 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
16157 have accumulated many known flaws; everyone should upgrade.
16159 o Major features (security):
16160 - If you don't specify MaxMemInQueues yourself, Tor now tries to
16161 pick a good value based on your total system memory. Previously,
16162 the default was always 8 GB. You can still override the default by
16163 setting MaxMemInQueues yourself. Resolves ticket 11396.
16164 - Block authority signing keys that were used on authorities
16165 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
16166 don't have any evidence that these keys _were_ compromised; we're
16167 doing this to be prudent.) Resolves ticket 11464.
16169 o Major features (relay performance):
16170 - Speed up server-side lookups of rendezvous and introduction point
16171 circuits by using hashtables instead of linear searches. These
16172 functions previously accounted between 3 and 7% of CPU usage on
16173 some busy relays. Resolves ticket 9841.
16174 - Avoid wasting CPU when extending a circuit over a channel that is
16175 nearly out of circuit IDs. Previously, we would do a linear scan
16176 over possible circuit IDs before finding one or deciding that we
16177 had exhausted our possibilities. Now, we try at most 64 random
16178 circuit IDs before deciding that we probably won't succeed. Fixes
16179 a possible root cause of ticket 11553.
16181 o Major features (seccomp2 sandbox, Linux only):
16182 - The seccomp2 sandbox can now run a test network for multiple hours
16183 without crashing. The sandbox is still experimental, and more bugs
16184 will probably turn up. To try it, enable "Sandbox 1" on a Linux
16185 host. Resolves ticket 11351.
16186 - Strengthen sandbox code: the sandbox can now test the arguments
16187 for rename(), and blocks _sysctl() entirely. Resolves another part
16189 - When the sandbox blocks a system call, it now tries to log a stack
16190 trace before exiting. Resolves ticket 11465.
16192 o Major bugfixes (TLS cipher selection):
16193 - The relay ciphersuite list is now generated automatically based on
16194 uniform criteria, and includes all OpenSSL ciphersuites with
16195 acceptable strength and forward secrecy. Previously, we had left
16196 some perfectly fine ciphersuites unsupported due to omission or
16197 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
16198 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
16199 - Relays now trust themselves to have a better view than clients of
16200 which TLS ciphersuites are better than others. (Thanks to bug
16201 11513, the relay list is now well-considered, whereas the client
16202 list has been chosen mainly for anti-fingerprinting purposes.)
16203 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
16204 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
16205 AES128. Resolves ticket 11528.
16206 - Clients now try to advertise the same list of ciphersuites as
16207 Firefox 28. This change enables selection of (fast) GCM
16208 ciphersuites, disables some strange old ciphers, and stops
16209 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
16210 Resolves ticket 11438.
16212 o Major bugfixes (bridge client):
16213 - Avoid 60-second delays in the bootstrapping process when Tor is
16214 launching for a second time while using bridges. Fixes bug 9229;
16215 bugfix on 0.2.0.3-alpha.
16217 o Minor features (transparent proxy, *BSD):
16218 - Support FreeBSD's ipfw firewall interface for TransPort ports on
16219 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
16220 10267; patch from "yurivict".
16221 - Support OpenBSD's divert-to rules with the pf firewall for
16222 transparent proxy ports. To enable it, set "TransProxyType
16223 pf-divert". This allows Tor to run a TransPort transparent proxy
16224 port on OpenBSD 4.4 or later without root privileges. See the
16225 pf.conf(5) manual page for information on configuring pf to use
16226 divert-to rules. Closes ticket 10896; patch from Dana Koch.
16228 o Minor features (security):
16229 - New --enable-expensive-hardening option to enable security
16230 hardening options that consume nontrivial amounts of CPU and
16231 memory. Right now, this includes AddressSanitizer and UbSan, which
16232 are supported in newer versions of GCC and Clang. Closes ticket
16235 o Minor features (log verbosity):
16236 - Demote the message that we give when a flushing connection times
16237 out for too long from NOTICE to INFO. It was usually meaningless.
16238 Resolves ticket 5286.
16239 - Don't log so many notice-level bootstrapping messages at startup
16240 about downloading descriptors. Previously, we'd log a notice
16241 whenever we learned about more routers. Now, we only log a notice
16242 at every 5% of progress. Fixes bug 9963.
16243 - Warn less verbosely when receiving a malformed
16244 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
16245 - When we run out of usable circuit IDs on a channel, log only one
16246 warning for the whole channel, and describe how many circuits
16247 there were on the channel. Fixes part of ticket 11553.
16249 o Minor features (relay):
16250 - If a circuit timed out for at least 3 minutes, check if we have a
16251 new external IP address, and publish a new descriptor with the new
16252 IP address if it changed. Resolves ticket 2454.
16254 o Minor features (controller):
16255 - Make the entire exit policy available from the control port via
16256 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
16258 - Because of the fix for ticket 11396, the real limit for memory
16259 usage may no longer match the configured MaxMemInQueues value. The
16260 real limit is now exposed via GETINFO limits/max-mem-in-queues.
16262 o Minor features (bridge client):
16263 - Report a more useful failure message when we can't connect to a
16264 bridge because we don't have the right pluggable transport
16265 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
16267 o Minor features (diagnostic):
16268 - Add more log messages to diagnose bug 7164, which causes
16269 intermittent "microdesc_free() called but md was still referenced"
16270 warnings. We now include more information, to figure out why we
16271 might be cleaning a microdescriptor for being too old if it's
16272 still referenced by a live node_t object.
16274 o Minor bugfixes (client, DNSPort):
16275 - When using DNSPort, try to respond to AAAA requests with AAAA
16276 answers. Previously, we hadn't looked at the request type when
16277 deciding which answer type to prefer. Fixes bug 10468; bugfix on
16279 - When receiving a DNS query for an unsupported record type, reply
16280 with no answer rather than with a NOTIMPL error. This behavior
16281 isn't correct either, but it will break fewer client programs, we
16282 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
16285 o Minor bugfixes (exit relay):
16286 - Stop leaking memory when we successfully resolve a PTR record.
16287 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
16289 o Minor bugfixes (bridge client):
16290 - Stop accepting bridge lines containing hostnames. Doing so would
16291 cause clients to perform DNS requests on the hostnames, which was
16292 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
16293 - Avoid a 60-second delay in the bootstrapping process when a Tor
16294 client with pluggable transports re-reads its configuration at
16295 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
16297 o Minor bugfixes (client, logging during bootstrap):
16298 - Warn only once if we start logging in an unsafe way. Previously,
16299 we complain as many times as we had problems. Fixes bug 9870;
16300 bugfix on 0.2.5.1-alpha.
16301 - Only report the first fatal bootstrap error on a given OR
16302 connection. This stops us from telling the controller bogus error
16303 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
16304 - Be more helpful when trying to run sandboxed on Linux without
16305 libseccomp. Instead of saying "Sandbox is not implemented on this
16306 platform", we now explain that we need to be built with
16307 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
16308 - Avoid generating spurious warnings when starting with
16309 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
16312 o Minor bugfixes (closing OR connections):
16313 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
16314 check if it's an or_connection_t and correctly call
16315 connection_or_close_for_error() rather than
16316 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
16318 - When closing all connections on setting DisableNetwork to 1, use
16319 connection_or_close_normally() rather than closing OR connections
16320 out from under the channel layer. Fixes bug 11306; bugfix on
16323 o Minor bugfixes (controller):
16324 - Avoid sending a garbage value to the controller when a circuit is
16325 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
16327 o Minor bugfixes (tor-fw-helper):
16328 - Allow tor-fw-helper to build again by adding src/ext to its
16329 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
16331 o Minor bugfixes (bridges):
16332 - Avoid potential crashes or bad behavior when launching a
16333 server-side managed proxy with ORPort or ExtORPort temporarily
16334 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
16336 o Minor bugfixes (platform-specific):
16337 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
16338 bug 11426; bugfix on 0.2.5.3-alpha.
16339 - When dumping a malformed directory object to disk, save it in
16340 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
16342 - Don't report failures from make_socket_reuseable() on incoming
16343 sockets on OSX: this can happen when incoming connections close
16344 early. Fixes bug 10081.
16346 o Minor bugfixes (trivial memory leaks):
16347 - Fix a small memory leak when signing a directory object. Fixes bug
16348 11275; bugfix on 0.2.4.13-alpha.
16349 - Free placeholder entries in our circuit table at exit; fixes a
16350 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
16351 - Don't re-initialize a second set of OpenSSL mutexes when starting
16352 up. Previously, we'd make one set of mutexes, and then immediately
16353 replace them with another. Fixes bug 11726; bugfix on
16355 - Resolve some memory leaks found by coverity in the unit tests, on
16356 exit in tor-gencert, and on a failure to compute digests for our
16357 own keys when generating a v3 networkstatus vote. These leaks
16358 should never have affected anyone in practice.
16360 o Minor bugfixes (hidden service):
16361 - Only retry attempts to connect to a chosen rendezvous point 8
16362 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
16364 o Minor bugfixes (misc code correctness):
16365 - Fix various instances of undefined behavior in channeltls.c,
16366 tor_memmem(), and eventdns.c that would cause us to construct
16367 pointers to memory outside an allocated object. (These invalid
16368 pointers were not accessed, but C does not even allow them to
16369 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
16370 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
16371 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
16372 fix some miscellaneous errors in our tests and codebase. Fixes bug
16373 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
16374 - Always check return values for unlink, munmap, UnmapViewOfFile;
16375 check strftime return values more often. In some cases all we can
16376 do is report a warning, but this may help prevent deeper bugs from
16377 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
16379 - Fix numerous warnings from the clang "scan-build" static analyzer.
16380 Some of these are programming style issues; some of them are false
16381 positives that indicated awkward code; some are undefined behavior
16382 cases related to constructing (but not using) invalid pointers;
16383 some are assumptions about API behavior; some are (harmlessly)
16384 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
16385 correct; and one or two are genuine bugs that weren't reachable
16386 from the rest of the program. Fixes bug 8793; bugfixes on many,
16390 - Build the torify.1 manpage again. Previously, we were only trying
16391 to build it when also building tor-fw-helper. That's why we didn't
16392 notice that we'd broken the ability to build it. Fixes bug 11321;
16393 bugfix on 0.2.5.1-alpha.
16394 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
16395 11061; bugfix on 0.2.4.7-alpha.
16396 - Correctly document that we search for a system torrc file before
16397 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
16399 - Resolve warnings from Doxygen.
16401 o Code simplifications and refactoring:
16402 - Remove is_internal_IP() function. Resolves ticket 4645.
16403 - Remove unused function circuit_dump_by_chan from circuitlist.c.
16404 Closes issue 9107; patch from "marek".
16405 - Change our use of the ENUM_BF macro to avoid declarations that
16408 o Deprecated versions:
16409 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
16410 attention for some while. Directory authorities no longer accept
16411 descriptors from relays running any version of Tor prior to Tor
16412 0.2.3.16-alpha. Resolves ticket 11149.
16415 - New macros in test.h to simplify writing mock-functions for unit
16416 tests. Part of ticket 11507. Patch from Dana Koch.
16417 - Complete tests for the status.c module. Resolves ticket 11507.
16418 Patch from Dana Koch.
16421 - Remove all code for the long unused v1 directory protocol.
16422 Resolves ticket 11070.
16425 Changes in version 0.2.5.3-alpha - 2014-03-22
16426 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
16427 two new anti-DoS features for Tor relays, resolves a bug that kept
16428 SOCKS5 support for IPv6 from working, fixes several annoying usability
16429 issues for bridge users, and removes more old code for unused
16432 The Tor 0.2.5.x release series is now in patch-freeze: no feature
16433 patches not already written will be considered for inclusion in 0.2.5.x.
16435 o Major features (relay security, DoS-resistance):
16436 - When deciding whether we have run out of memory and we need to
16437 close circuits, also consider memory allocated in buffers for
16438 streams attached to each circuit.
16440 This change, which extends an anti-DoS feature introduced in
16441 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
16442 better resist more memory-based DoS attacks than before. Since the
16443 MaxMemInCellQueues option now applies to all queues, it is renamed
16444 to MaxMemInQueues. This feature fixes bug 10169.
16445 - Avoid hash-flooding denial-of-service attacks by using the secure
16446 SipHash-2-4 hash function for our hashtables. Without this
16447 feature, an attacker could degrade performance of a targeted
16448 client or server by flooding their data structures with a large
16449 number of entries to be stored at the same hash table position,
16450 thereby slowing down the Tor instance. With this feature, hash
16451 table positions are derived from a randomized cryptographic key,
16452 and an attacker cannot predict which entries will collide. Closes
16454 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
16455 the default at 8GBytes), to better support Raspberry Pi users. Fixes
16456 bug 9686; bugfix on 0.2.4.14-alpha.
16458 o Minor features (bridges, pluggable transports):
16459 - Bridges now write the SHA1 digest of their identity key
16460 fingerprint (that is, a hash of a hash of their public key) to
16461 notice-level logs, and to a new hashed-fingerprint file. This
16462 information will help bridge operators look up their bridge in
16463 Globe and similar tools. Resolves ticket 10884.
16464 - Improve the message that Tor displays when running as a bridge
16465 using pluggable transports without an Extended ORPort listener.
16466 Also, log the message in the log file too. Resolves ticket 11043.
16468 o Minor features (other):
16469 - Add a new option, PredictedPortsRelevanceTime, to control how long
16470 after having received a request to connect to a given port Tor
16471 will try to keep circuits ready in anticipation of future requests
16472 for that port. Patch from "unixninja92"; implements ticket 9176.
16473 - Generate a warning if any ports are listed in the SocksPolicy,
16474 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
16475 AuthDirBadExit options. (These options only support address
16476 ranges.) Fixes part of ticket 11108.
16477 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
16480 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
16481 - Build without warnings under clang 3.4. (We have some macros that
16482 define static functions only some of which will get used later in
16483 the module. Starting with clang 3.4, these give a warning unless the
16484 unused attribute is set on them.) Resolves ticket 10904.
16485 - Fix build warnings about missing "a2x" comment when building the
16486 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16487 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16489 o Minor bugfixes (client):
16490 - Improve the log message when we can't connect to a hidden service
16491 because all of the hidden service directory nodes hosting its
16492 descriptor are excluded. Improves on our fix for bug 10722, which
16493 was a bugfix on 0.2.0.10-alpha.
16494 - Raise a control port warning when we fail to connect to all of
16495 our bridges. Previously, we didn't inform the controller, and
16496 the bootstrap process would stall. Fixes bug 11069; bugfix on
16498 - Exit immediately when a process-owning controller exits.
16499 Previously, tor relays would wait for a little while after their
16500 controller exited, as if they had gotten an INT signal -- but this
16501 was problematic, since there was no feedback for the user. To do a
16502 clean shutdown, controllers should send an INT signal and give Tor
16503 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
16504 - Stop attempting to connect to bridges before our pluggable
16505 transports are configured (harmless but resulted in some erroneous
16506 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
16507 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
16508 generating incorrect SOCKS5 responses, and confusing client
16509 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
16511 o Minor bugfixes (relays and bridges):
16512 - Avoid crashing on a malformed resolv.conf file when running a
16513 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
16514 - Non-exit relays no longer launch mock DNS requests to check for
16515 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
16516 non-exit relays stopped servicing DNS requests. Fixes bug 965;
16517 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
16518 - Bridges now report complete directory request statistics. Related
16519 to bug 5824; bugfix on 0.2.2.1-alpha.
16520 - Bridges now never collect statistics that were designed for
16521 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
16522 - Stop giving annoying warning messages when we decide not to launch
16523 a pluggable transport proxy that we don't need (because there are
16524 no bridges configured to use it). Resolves ticket 5018; bugfix
16526 - Give the correct URL in the warning message when trying to run a
16527 relay on an ancient version of Windows. Fixes bug 9393.
16529 o Minor bugfixes (backtrace support):
16530 - Support automatic backtraces on more platforms by using the
16531 "-fasynchronous-unwind-tables" compiler option. This option is
16532 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
16533 is on by default and table generation is not. This doesn't yet
16534 add Windows support; only Linux, OSX, and some BSDs are affected.
16535 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
16536 - Avoid strange behavior if two threads hit failed assertions at the
16537 same time and both try to log backtraces at once. (Previously, if
16538 this had happened, both threads would have stored their intermediate
16539 results in the same buffer, and generated junk outputs.) Reported by
16540 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
16541 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
16542 0.2.5.2-alpha; patch from Nick Hopper.
16544 o Minor bugfixes (unit tests):
16545 - Fix a small bug in the unit tests that might have made the tests
16546 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
16547 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
16550 - Remove all remaining code related to version-0 hidden service
16551 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
16552 the rest of bug 10841.
16555 - Document in the manpage that "KBytes" may also be written as
16556 "kilobytes" or "KB", that "Kbits" may also be written as
16557 "kilobits", and so forth. Closes ticket 9222.
16558 - Document that the ClientOnly config option overrides ORPort.
16559 Our old explanation made ClientOnly sound as though it did
16560 nothing at all. Resolves bug 9059.
16561 - Explain that SocksPolicy, DirPolicy, and similar options don't
16562 take port arguments. Fixes the other part of ticket 11108.
16563 - Fix a comment about the rend_server_descriptor_t.protocols field
16564 to more accurately describe its range. Also, make that field
16565 unsigned, to more accurately reflect its usage. Fixes bug 9099;
16566 bugfix on 0.2.1.5-alpha.
16567 - Fix the manpage's description of HiddenServiceAuthorizeClient:
16568 the maximum client name length is 16, not 19. Fixes bug 11118;
16569 bugfix on 0.2.1.6-alpha.
16571 o Code simplifications and refactoring:
16572 - Get rid of router->address, since in all cases it was just the
16573 string representation of router->addr. Resolves ticket 5528.
16575 o Test infrastructure:
16576 - Update to the latest version of tinytest.
16577 - Improve the tinytest implementation of string operation tests so
16578 that comparisons with NULL strings no longer crash the tests; they
16579 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
16582 Changes in version 0.2.4.21 - 2014-02-28
16583 Tor 0.2.4.21 further improves security against potential adversaries who
16584 find breaking 1024-bit crypto doable, and backports several stability
16585 and robustness patches from the 0.2.5 branch.
16587 o Major features (client security):
16588 - When we choose a path for a 3-hop circuit, make sure it contains
16589 at least one relay that supports the NTor circuit extension
16590 handshake. Otherwise, there is a chance that we're building
16591 a circuit that's worth attacking by an adversary who finds
16592 breaking 1024-bit crypto doable, and that chance changes the game
16593 theory. Implements ticket 9777.
16596 - Do not treat streams that fail with reason
16597 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16598 since it could also indicate an ENETUNREACH connection error. Fixes
16599 part of bug 10777; bugfix on 0.2.4.8-alpha.
16601 o Code simplification and refactoring:
16602 - Remove data structures which were introduced to implement the
16603 CellStatistics option: they are now redundant with the new timestamp
16604 field in the regular packed_cell_t data structure, which we did
16605 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
16608 - Always clear OpenSSL bignums before freeing them -- even bignums
16609 that don't contain secrets. Resolves ticket 10793. Patch by
16611 - Build without warnings under clang 3.4. (We have some macros that
16612 define static functions only some of which will get used later in
16613 the module. Starting with clang 3.4, these give a warning unless the
16614 unused attribute is set on them.) Resolves ticket 10904.
16615 - Update geoip and geoip6 files to the February 7 2014 Maxmind
16616 GeoLite2 Country database.
16619 - Set the listen() backlog limit to the largest actually supported
16620 on the system, not to the value in a header file. Fixes bug 9716;
16621 bugfix on every released Tor.
16622 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16623 exit node as a NOROUTE error, not an INTERNAL error, since they
16624 can apparently happen when trying to connect to the wrong sort
16625 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16626 - Fix build warnings about missing "a2x" comment when building the
16627 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
16628 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
16629 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16630 not entirely remove it from the connection lists. Fixes bug 9602;
16631 bugfix on 0.2.4.4-alpha.
16632 - Fix a segmentation fault in our benchmark code when running with
16633 Fedora's OpenSSL package, or any other OpenSSL that provides
16634 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16635 - Turn "circuit handshake stats since last time" log messages into a
16636 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16638 o Documentation fixes:
16639 - Document that all but one DirPort entry must have the NoAdvertise
16640 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16643 Changes in version 0.2.5.2-alpha - 2014-02-13
16644 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
16645 like the "poor random number generation" fix and the "building too many
16646 circuits" fix. It also further improves security against potential
16647 adversaries who find breaking 1024-bit crypto doable, and launches
16648 pluggable transports on demand (which gets us closer to integrating
16649 pluggable transport support by default -- not to be confused with Tor
16650 bundles enabling pluggable transports and bridges by default).
16652 o Major features (client security):
16653 - When we choose a path for a 3-hop circuit, make sure it contains
16654 at least one relay that supports the NTor circuit extension
16655 handshake. Otherwise, there is a chance that we're building
16656 a circuit that's worth attacking by an adversary who finds
16657 breaking 1024-bit crypto doable, and that chance changes the game
16658 theory. Implements ticket 9777.
16659 - Clients now look at the "usecreatefast" consensus parameter to
16660 decide whether to use CREATE_FAST or CREATE cells for the first hop
16661 of their circuit. This approach can improve security on connections
16662 where Tor's circuit handshake is stronger than the available TLS
16663 connection security levels, but the tradeoff is more computational
16664 load on guard relays. Implements proposal 221. Resolves ticket 9386.
16666 o Major features (bridges):
16667 - Don't launch pluggable transport proxies if we don't have any
16668 bridges configured that would use them. Now we can list many
16669 pluggable transports, and Tor will dynamically start one when it
16670 hears a bridge address that needs it. Resolves ticket 5018.
16671 - The bridge directory authority now assigns status flags (Stable,
16672 Guard, etc) to bridges based on thresholds calculated over all
16673 Running bridges. Now bridgedb can finally make use of its features
16674 to e.g. include at least one Stable bridge in its answers. Fixes
16677 o Major features (other):
16678 - Extend ORCONN controller event to include an "ID" parameter,
16679 and add four new controller event types CONN_BW, CIRC_BW,
16680 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
16681 The new events are emitted in private Tor networks only, with the
16682 goal of being able to better track performance and load during
16683 full-network simulations. Implements proposal 218 and ticket 7359.
16684 - On some platforms (currently: recent OSX versions, glibc-based
16685 platforms that support the ELF format, and a few other
16686 Unix-like operating systems), Tor can now dump stack traces
16687 when a crash occurs or an assertion fails. By default, traces
16688 are dumped to stderr (if possible) and to any logs that are
16689 reporting errors. Implements ticket 9299.
16692 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
16693 not entirely remove it from the connection lists. Fixes bug 9602;
16694 bugfix on 0.2.4.4-alpha.
16695 - Do not treat streams that fail with reason
16696 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
16697 since it could also indicate an ENETUNREACH connection error. Fixes
16698 part of bug 10777; bugfix on 0.2.4.8-alpha.
16700 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16701 - Do not allow OpenSSL engines to replace the PRNG, even when
16702 HardwareAccel is set. The only default builtin PRNG engine uses
16703 the Intel RDRAND instruction to replace the entire PRNG, and
16704 ignores all attempts to seed it with more entropy. That's
16705 cryptographically stupid: the right response to a new alleged
16706 entropy source is never to discard all previously used entropy
16707 sources. Fixes bug 10402; works around behavior introduced in
16708 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16710 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16711 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16712 - Avoid launching spurious extra circuits when a stream is pending.
16713 This fixes a bug where any circuit that _wasn't_ unusable for new
16714 streams would be treated as if it were, causing extra circuits to
16715 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
16717 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16718 - No longer stop reading or writing on cpuworker connections when
16719 our rate limiting buckets go empty. Now we should handle circuit
16720 handshake requests more promptly. Resolves bug 9731.
16721 - Stop trying to bootstrap all our directory information from
16722 only our first guard. Discovered while fixing bug 9946; bugfix
16725 o Minor features (bridges, pluggable transports):
16726 - Add threshold cutoffs to the networkstatus document created by
16727 the Bridge Authority. Fixes bug 1117.
16728 - On Windows, spawn background processes using the CREATE_NO_WINDOW
16729 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
16730 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
16731 Vidalia set this option for us.) Implements ticket 10297.
16733 o Minor features (security):
16734 - Always clear OpenSSL bignums before freeing them -- even bignums
16735 that don't contain secrets. Resolves ticket 10793. Patch by
16738 o Minor features (config options and command line):
16739 - Add an --allow-missing-torrc commandline option that tells Tor to
16740 run even if the configuration file specified by -f is not available.
16741 Implements ticket 10060.
16742 - Add support for the TPROXY transparent proxying facility on Linux.
16743 See documentation for the new TransProxyType option for more
16744 details. Implementation by "thomo". Closes ticket 10582.
16746 o Minor features (controller):
16747 - Add a new "HS_DESC" controller event that reports activities
16748 related to hidden service descriptors. Resolves ticket 8510.
16749 - New "DROPGUARDS" controller command to forget all current entry
16750 guards. Not recommended for ordinary use, since replacing guards
16751 too frequently makes several attacks easier. Resolves ticket 9934;
16754 o Minor features (build):
16755 - Assume that a user using ./configure --host wants to cross-compile,
16756 and give an error if we cannot find a properly named
16757 tool-chain. Add a --disable-tool-name-check option to proceed
16758 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
16759 - If we run ./configure and the compiler recognizes -fstack-protector
16760 but the linker rejects it, warn the user about a potentially missing
16761 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
16763 o Minor features (testing):
16764 - If Python is installed, "make check" now runs extra tests beyond
16765 the unit test scripts.
16766 - When bootstrapping a test network, sometimes very few relays get
16767 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
16768 specify a set of relays which should be voted Guard regardless of
16769 their uptime or bandwidth. Addresses ticket 9206.
16771 o Minor features (log messages):
16772 - When ServerTransportPlugin is set on a bridge, Tor can write more
16773 useful statistics about bridge use in its extrainfo descriptors,
16774 but only if the Extended ORPort ("ExtORPort") is set too. Add a
16775 log message to inform the user in this case. Resolves ticket 9651.
16776 - When receiving a new controller connection, log the origin address.
16777 Resolves ticket 9698; patch from "sigpipe".
16778 - When logging OpenSSL engine status at startup, log the status of
16779 more engines. Fixes ticket 10043; patch from Joshua Datko.
16780 - Turn "circuit handshake stats since last time" log messages into a
16781 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
16783 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16784 - Improve the circuit queue out-of-memory handler. Previously, when
16785 we ran low on memory, we'd close whichever circuits had the most
16786 queued cells. Now, we close those that have the *oldest* queued
16787 cells, on the theory that those are most responsible for us
16788 running low on memory. Based on analysis from a forthcoming paper
16789 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
16790 - Generate bootstrapping status update events correctly when fetching
16791 microdescriptors. Fixes bug 9927.
16792 - Update to the October 2 2013 Maxmind GeoLite Country database.
16794 o Minor bugfixes (clients):
16795 - When closing a channel that has already been open, do not close
16796 pending circuits that were waiting to connect to the same relay.
16797 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
16800 o Minor bugfixes (relays):
16801 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
16802 exit node as a NOROUTE error, not an INTERNAL error, since they
16803 can apparently happen when trying to connect to the wrong sort
16804 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
16806 o Minor bugfixes (bridges):
16807 - Fix a bug where the first connection works to a bridge that uses a
16808 pluggable transport with client-side parameters, but we don't send
16809 the client-side parameters on subsequent connections. (We don't
16810 use any pluggable transports with client-side parameters yet,
16811 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
16812 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
16814 o Minor bugfixes (node selection):
16815 - If ExcludeNodes is set, consider non-excluded hidden service
16816 directory servers before excluded ones. Do not consider excluded
16817 hidden service directory servers at all if StrictNodes is
16818 set. (Previously, we would sometimes decide to connect to those
16819 servers, and then realize before we initiated a connection that
16820 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
16821 Reported by "mr-4".
16822 - If we set the ExitNodes option but it doesn't include any nodes
16823 that have the Exit flag, we would choose not to bootstrap. Now we
16824 bootstrap so long as ExitNodes includes nodes which can exit to
16825 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
16827 o Minor bugfixes (controller and command-line):
16828 - If changing a config option via "setconf" fails in a recoverable
16829 way, we used to nonetheless write our new control ports to the
16830 file described by the "ControlPortWriteToFile" option. Now we only
16831 write out that file if we successfully switch to the new config
16832 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
16833 - When a command-line option such as --version or --help that
16834 ordinarily implies --hush appears on the command line along with
16835 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
16836 only if it appeared later on the command line. Fixes bug 9578;
16837 bugfix on 0.2.5.1-alpha.
16839 o Minor bugfixes (code correctness):
16840 - Previously we used two temporary files when writing descriptors to
16841 disk; now we only use one. Fixes bug 1376.
16842 - Remove an erroneous (but impossible and thus harmless) pointer
16843 comparison that would have allowed compilers to skip a bounds
16844 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
16845 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
16846 - Fix an always-true assertion in pluggable transports code so it
16847 actually checks what it was trying to check. Fixes bug 10046;
16848 bugfix on 0.2.3.9-alpha. Found by "dcb".
16850 o Minor bugfixes (protocol correctness):
16851 - When receiving a VERSIONS cell with an odd number of bytes, close
16852 the connection immediately since the cell is malformed. Fixes bug
16853 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
16856 o Minor bugfixes (build):
16857 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
16858 turned off (that is, without support for v2 link handshakes). Fixes
16859 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
16860 - Fix compilation warnings and startup issues when running with
16861 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
16863 - Fix compilation on Solaris 9, which didn't like us having an
16864 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
16866 o Minor bugfixes (testing):
16867 - Fix a segmentation fault in our benchmark code when running with
16868 Fedora's OpenSSL package, or any other OpenSSL that provides
16869 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
16871 o Minor bugfixes (log messages):
16872 - Fix a bug where clients using bridges would report themselves
16873 as 50% bootstrapped even without a live consensus document.
16874 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
16875 - Suppress a warning where, if there's only one directory authority
16876 in the network, we would complain that votes and signatures cannot
16877 be uploaded to other directory authorities. Fixes bug 10842;
16878 bugfix on 0.2.2.26-beta.
16879 - Report bootstrapping progress correctly when we're downloading
16880 microdescriptors. We had updated our "do we have enough microdescs
16881 to begin building circuits?" logic most recently in 0.2.4.10-alpha
16882 (see bug 5956), but we left the bootstrap status event logic at
16883 "how far through getting 1/4 of them are we?" Fixes bug 9958;
16884 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
16886 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
16887 - Avoid a crash bug when starting with a corrupted microdescriptor
16888 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
16889 - If we fail to dump a previously cached microdescriptor to disk, avoid
16890 freeing duplicate data later on. Fixes bug 10423; bugfix on
16891 0.2.4.13-alpha. Spotted by "bobnomnom".
16893 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16894 - Correctly log long IPv6 exit policies, instead of truncating them
16895 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
16896 - Our default TLS ecdhe groups were backwards: we meant to be using
16897 P224 for relays (for performance win) and P256 for bridges (since
16898 it is more common in the wild). Instead we had it backwards. After
16899 reconsideration, we decided that the default should be P256 on all
16900 hosts, since its security is probably better, and since P224 is
16901 reportedly used quite little in the wild. Found by "skruffy" on
16902 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
16903 - Free directory authority certificate download statuses on exit
16904 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
16906 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16907 - If the guard we choose first doesn't answer, we would try the
16908 second guard, but once we connected to the second guard we would
16909 abandon it and retry the first one, slowing down bootstrapping.
16910 The fix is to treat all our initially chosen guards as acceptable
16911 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
16912 - Fix an assertion failure that would occur when disabling the
16913 ORPort setting on a running Tor process while accounting was
16914 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
16915 - When examining the list of network interfaces to find our address,
16916 do not consider non-running or disabled network interfaces. Fixes
16917 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
16918 - Avoid an off-by-one error when checking buffer boundaries when
16919 formatting the exit status of a pluggable transport helper.
16920 This is probably not an exploitable bug, but better safe than
16921 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
16924 o Removed code and features:
16925 - Clients now reject any directory authority certificates lacking
16926 a dir-key-crosscert element. These have been included since
16927 0.2.1.9-alpha, so there's no real reason for them to be optional
16928 any longer. Completes proposal 157. Resolves ticket 10162.
16929 - Remove all code that existed to support the v2 directory system,
16930 since there are no longer any v2 directory authorities. Resolves
16932 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
16933 options, which were used for designating authorities as "Hidden
16934 service authorities". There has been no use of hidden service
16935 authorities since 0.2.2.1-alpha, when we stopped uploading or
16936 downloading v0 hidden service descriptors. Fixes bug 10881; also
16937 part of a fix for bug 10841.
16939 o Code simplification and refactoring:
16940 - Remove some old fallback code designed to keep Tor clients working
16941 in a network with only two working relays. Elsewhere in the code we
16942 have long since stopped supporting such networks, so there wasn't
16943 much point in keeping it around. Addresses ticket 9926.
16944 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
16945 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
16946 - Remove data structures which were introduced to implement the
16947 CellStatistics option: they are now redundant with the addition
16948 of a timestamp to the regular packed_cell_t data structure, which
16949 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
16952 o Documentation (man page) fixes:
16953 - Update manpage to describe some of the files you can expect to
16954 find in Tor's DataDirectory. Addresses ticket 9839.
16955 - Document that all but one DirPort entry must have the NoAdvertise
16956 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
16958 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
16959 - Clarify the usage and risks of setting the ContactInfo torrc line
16960 for your relay or bridge. Resolves ticket 9854.
16961 - Add anchors to the manpage so we can link to the html version of
16962 the documentation for specific options. Resolves ticket 9866.
16963 - Replace remaining references to DirServer in man page and
16964 log entries. Resolves ticket 10124.
16967 - Make the "tor-gencert" tool used by directory authority operators
16968 create 2048-bit signing keys by default (rather than 1024-bit, since
16969 1024-bit is uncomfortably small these days). Addresses ticket 10324.
16972 Changes in version 0.2.4.20 - 2013-12-22
16973 Tor 0.2.4.20 fixes potentially poor random number generation for users
16974 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
16975 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
16976 and 4) have no state file in their DataDirectory (as would happen on
16977 first start). Users who generated relay or hidden service identity
16978 keys in such a situation should discard them and generate new ones.
16980 This release also fixes a logic error that caused Tor clients to build
16981 many more preemptive circuits than they actually need.
16984 - Do not allow OpenSSL engines to replace the PRNG, even when
16985 HardwareAccel is set. The only default builtin PRNG engine uses
16986 the Intel RDRAND instruction to replace the entire PRNG, and
16987 ignores all attempts to seed it with more entropy. That's
16988 cryptographically stupid: the right response to a new alleged
16989 entropy source is never to discard all previously used entropy
16990 sources. Fixes bug 10402; works around behavior introduced in
16991 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
16993 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
16994 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
16995 - Avoid launching spurious extra circuits when a stream is pending.
16996 This fixes a bug where any circuit that _wasn't_ unusable for new
16997 streams would be treated as if it were, causing extra circuits to
16998 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
17001 - Avoid a crash bug when starting with a corrupted microdescriptor
17002 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
17003 - If we fail to dump a previously cached microdescriptor to disk, avoid
17004 freeing duplicate data later on. Fixes bug 10423; bugfix on
17005 0.2.4.13-alpha. Spotted by "bobnomnom".
17008 Changes in version 0.2.4.19 - 2013-12-11
17009 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
17010 (1986-2013). Aaron worked on diverse projects including helping to guide
17011 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
17012 transparency to the U.S government's PACER documents, and contributing
17013 design and development for Tor and Tor2Web. Aaron was one of the latest
17014 martyrs in our collective fight for civil liberties and human rights,
17015 and his death is all the more painful because he was one of us.
17017 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
17018 a new circuit handshake and link encryption that use ECC to provide
17019 better security and efficiency; makes relays better manage circuit
17020 creation requests; uses "directory guards" to reduce client enumeration
17021 risks; makes bridges collect and report statistics about the pluggable
17022 transports they support; cleans up and improves our geoip database;
17023 gets much closer to IPv6 support for clients, bridges, and relays; makes
17024 directory authorities use measured bandwidths rather than advertised
17025 ones when computing flags and thresholds; disables client-side DNS
17026 caching to reduce tracking risks; and fixes a big bug in bridge
17027 reachability testing. This release introduces two new design
17028 abstractions in the code: a new "channel" abstraction between circuits
17029 and or_connections to allow for implementing alternate relay-to-relay
17030 transports, and a new "circuitmux" abstraction storing the queue of
17031 circuits for a channel. The release also includes many stability,
17032 security, and privacy fixes.
17035 Changes in version 0.2.4.18-rc - 2013-11-16
17036 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
17037 series. It takes a variety of fixes from the 0.2.5.x branch to improve
17038 stability, performance, and better handling of edge cases.
17041 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
17042 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
17043 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
17044 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
17045 them to solve bug 6033.)
17048 - No longer stop reading or writing on cpuworker connections when
17049 our rate limiting buckets go empty. Now we should handle circuit
17050 handshake requests more promptly. Resolves bug 9731.
17051 - If we are unable to save a microdescriptor to the journal, do not
17052 drop it from memory and then reattempt downloading it. Fixes bug
17053 9645; bugfix on 0.2.2.6-alpha.
17054 - Stop trying to bootstrap all our directory information from
17055 only our first guard. Discovered while fixing bug 9946; bugfix
17057 - The new channel code sometimes lost track of in-progress circuits,
17058 causing long-running clients to stop building new circuits. The
17059 fix is to always call circuit_n_chan_done(chan, 0) from
17060 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
17062 o Minor bugfixes (on 0.2.4.x):
17063 - Correctly log long IPv6 exit policies, instead of truncating them
17064 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
17065 - Our default TLS ecdhe groups were backwards: we meant to be using
17066 P224 for relays (for performance win) and P256 for bridges (since
17067 it is more common in the wild). Instead we had it backwards. After
17068 reconsideration, we decided that the default should be P256 on all
17069 hosts, since its security is probably better, and since P224 is
17070 reportedly used quite little in the wild. Found by "skruffy" on
17071 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
17072 - Free directory authority certificate download statuses on exit
17073 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
17075 o Minor bugfixes (on 0.2.3.x and earlier):
17076 - If the guard we choose first doesn't answer, we would try the
17077 second guard, but once we connected to the second guard we would
17078 abandon it and retry the first one, slowing down bootstrapping.
17079 The fix is to treat all our initially chosen guards as acceptable
17080 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
17081 - Fix an assertion failure that would occur when disabling the
17082 ORPort setting on a running Tor process while accounting was
17083 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
17084 - When examining the list of network interfaces to find our address,
17085 do not consider non-running or disabled network interfaces. Fixes
17086 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
17087 - Avoid an off-by-one error when checking buffer boundaries when
17088 formatting the exit status of a pluggable transport helper.
17089 This is probably not an exploitable bug, but better safe than
17090 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
17093 o Minor features (protecting client timestamps):
17094 - Clients no longer send timestamps in their NETINFO cells. These were
17095 not used for anything, and they provided one small way for clients
17096 to be distinguished from each other as they moved from network to
17097 network or behind NAT. Implements part of proposal 222.
17098 - Clients now round timestamps in INTRODUCE cells down to the nearest
17099 10 minutes. If a new Support022HiddenServices option is set to 0, or
17100 if it's set to "auto" and the feature is disabled in the consensus,
17101 the timestamp is sent as 0 instead. Implements part of proposal 222.
17102 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17103 a big deal from a security point of view, but it achieves no actual
17104 good purpose, and isn't needed. Implements part of proposal 222.
17105 - Reduce down accuracy of timestamps in hidden service descriptors.
17106 Implements part of proposal 222.
17108 o Minor features (other):
17109 - Improve the circuit queue out-of-memory handler. Previously, when
17110 we ran low on memory, we'd close whichever circuits had the most
17111 queued cells. Now, we close those that have the *oldest* queued
17112 cells, on the theory that those are most responsible for us
17113 running low on memory. Based on analysis from a forthcoming paper
17114 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
17115 - Generate bootstrapping status update events correctly when fetching
17116 microdescriptors. Fixes bug 9927.
17117 - Update to the October 2 2013 Maxmind GeoLite Country database.
17119 o Documentation fixes:
17120 - Clarify the usage and risks of setting the ContactInfo torrc line
17121 for your relay or bridge. Resolves ticket 9854.
17122 - Add anchors to the manpage so we can link to the html version of
17123 the documentation for specific options. Resolves ticket 9866.
17124 - Replace remaining references to DirServer in man page and
17125 log entries. Resolves ticket 10124.
17128 Changes in version 0.2.5.1-alpha - 2013-10-02
17129 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
17130 on Linux, allows bridges that offer pluggable transports to report usage
17131 statistics, fixes many issues to make testing easier, and provides
17132 a pile of minor features and bugfixes that have been waiting for a
17133 release of the new branch.
17135 This is the first alpha release in a new series, so expect there to
17136 be bugs. Users who would rather test out a more stable branch should
17137 stay with 0.2.4.x for now.
17139 o Major features (security):
17140 - Use the seccomp2 syscall filtering facility on Linux to limit
17141 which system calls Tor can invoke. This is an experimental,
17142 Linux-only feature to provide defense-in-depth against unknown
17143 attacks. To try turning it on, set "Sandbox 1" in your torrc
17144 file. Please be ready to report bugs. We hope to add support
17145 for better sandboxing in the future, including more fine-grained
17146 filters, better division of responsibility, and support for more
17147 platforms. This work has been done by Cristian-Matei Toader for
17148 Google Summer of Code.
17149 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
17150 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
17151 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
17152 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
17153 them to solve bug 6033.)
17155 o Major features (other):
17156 - Add support for passing arguments to managed pluggable transport
17157 proxies. Implements ticket 3594.
17158 - Bridges now track GeoIP information and the number of their users
17159 even when pluggable transports are in use, and report usage
17160 statistics in their extra-info descriptors. Resolves tickets 4773
17162 - Make testing Tor networks bootstrap better: lower directory fetch
17163 retry schedules and maximum interval without directory requests,
17164 and raise maximum download tries. Implements ticket 6752.
17165 - Add make target 'test-network' to run tests on a Chutney network.
17166 Implements ticket 8530.
17167 - The ntor handshake is now on-by-default, no matter what the
17168 directory authorities recommend. Implements ticket 8561.
17171 - Instead of writing destroy cells directly to outgoing connection
17172 buffers, queue them and intersperse them with other outgoing cells.
17173 This can prevent a set of resource starvation conditions where too
17174 many pending destroy cells prevent data cells from actually getting
17175 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
17176 bugfix on 0.2.0.1-alpha.
17177 - If we are unable to save a microdescriptor to the journal, do not
17178 drop it from memory and then reattempt downloading it. Fixes bug
17179 9645; bugfix on 0.2.2.6-alpha.
17180 - The new channel code sometimes lost track of in-progress circuits,
17181 causing long-running clients to stop building new circuits. The
17182 fix is to always call circuit_n_chan_done(chan, 0) from
17183 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
17186 - Tor now builds each source file in two modes: a mode that avoids
17187 exposing identifiers needlessly, and another mode that exposes
17188 more identifiers for testing. This lets the compiler do better at
17189 optimizing the production code, while enabling us to take more
17190 radical measures to let the unit tests test things.
17191 - The production builds no longer include functions used only in
17192 the unit tests; all functions exposed from a module only for
17193 unit-testing are now static in production builds.
17194 - Add an --enable-coverage configuration option to make the unit
17195 tests (and a new src/or/tor-cov target) to build with gcov test
17199 - We now have rudimentary function mocking support that our unit
17200 tests can use to test functions in isolation. Function mocking
17201 lets the tests temporarily replace a function's dependencies with
17202 stub functions, so that the tests can check the function without
17203 invoking the other functions it calls.
17204 - Add more unit tests for the <circid,channel>->circuit map, and
17205 the destroy-cell-tracking code to fix bug 7912.
17206 - Unit tests for failing cases of the TAP onion handshake.
17207 - More unit tests for address-manipulation functions.
17209 o Minor features (protecting client timestamps):
17210 - Clients no longer send timestamps in their NETINFO cells. These were
17211 not used for anything, and they provided one small way for clients
17212 to be distinguished from each other as they moved from network to
17213 network or behind NAT. Implements part of proposal 222.
17214 - Clients now round timestamps in INTRODUCE cells down to the nearest
17215 10 minutes. If a new Support022HiddenServices option is set to 0, or
17216 if it's set to "auto" and the feature is disabled in the consensus,
17217 the timestamp is sent as 0 instead. Implements part of proposal 222.
17218 - Stop sending timestamps in AUTHENTICATE cells. This is not such
17219 a big deal from a security point of view, but it achieves no actual
17220 good purpose, and isn't needed. Implements part of proposal 222.
17221 - Reduce down accuracy of timestamps in hidden service descriptors.
17222 Implements part of proposal 222.
17224 o Minor features (config options):
17225 - Config (torrc) lines now handle fingerprints which are missing
17226 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
17227 - Support a --dump-config option to print some or all of the
17228 configured options. Mainly useful for debugging the command-line
17229 option parsing code. Helps resolve ticket 4647.
17230 - Raise awareness of safer logging: notify user of potentially
17231 unsafe config options, like logging more verbosely than severity
17232 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
17233 - Add a new configuration option TestingV3AuthVotingStartOffset
17234 that bootstraps a network faster by changing the timing for
17235 consensus votes. Addresses ticket 8532.
17236 - Add a new torrc option "ServerTransportOptions" that allows
17237 bridge operators to pass configuration parameters to their
17238 pluggable transports. Resolves ticket 8929.
17239 - The config (torrc) file now accepts bandwidth and space limits in
17240 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
17241 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
17244 o Minor features (build):
17245 - Add support for `--library-versions` flag. Implements ticket 6384.
17246 - Return the "unexpected sendme" warnings to a warn severity, but make
17247 them rate limited, to help diagnose ticket 8093.
17248 - Detect a missing asciidoc, and warn the user about it, during
17249 configure rather than at build time. Fixes issue 6506. Patch from
17252 o Minor features (other):
17253 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
17254 sockets in a single system call. Implements ticket 5129.
17255 - Log current accounting state (bytes sent and received + remaining
17256 time for the current accounting period) in the relay's heartbeat
17257 message. Implements ticket 5526; patch from Peter Retzlaff.
17258 - Implement the TRANSPORT_LAUNCHED control port event that
17259 notifies controllers about new launched pluggable
17260 transports. Resolves ticket 5609.
17261 - If we're using the pure-C 32-bit curve25519_donna implementation
17262 of curve25519, build it with the -fomit-frame-pointer option to
17263 make it go faster on register-starved hosts. This improves our
17264 handshake performance by about 6% on i386 hosts without nacl.
17265 Closes ticket 8109.
17266 - Update to the September 4 2013 Maxmind GeoLite Country database.
17269 - Set the listen() backlog limit to the largest actually supported
17270 on the system, not to the value in a header file. Fixes bug 9716;
17271 bugfix on every released Tor.
17272 - No longer accept malformed http headers when parsing urls from
17273 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
17274 bugfix on 0.0.6pre1.
17275 - In munge_extrainfo_into_routerinfo(), check the return value of
17276 memchr(). This would have been a serious issue if we ever passed
17277 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
17279 - On the chance that somebody manages to build Tor on a
17280 platform where time_t is unsigned, correct the way that
17281 microdesc_add_to_cache() handles negative time arguments.
17282 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
17283 - Reject relative control socket paths and emit a warning. Previously,
17284 single-component control socket paths would be rejected, but Tor
17285 would not log why it could not validate the config. Fixes bug 9258;
17286 bugfix on 0.2.3.16-alpha.
17288 o Minor bugfixes (command line):
17289 - Use a single command-line parser for parsing torrc options on the
17290 command line and for finding special command-line options to avoid
17291 inconsistent behavior for torrc option arguments that have the same
17292 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
17294 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
17295 9573; bugfix on 0.0.9pre5.
17297 o Minor fixes (build, auxiliary programs):
17298 - Stop preprocessing the "torify" script with autoconf, since
17299 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
17301 - The tor-fw-helper program now follows the standard convention and
17302 exits with status code "0" on success. Fixes bug 9030; bugfix on
17303 0.2.3.1-alpha. Patch by Arlo Breault.
17304 - Corrected ./configure advice for what openssl dev package you should
17305 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
17307 o Minor code improvements:
17308 - Remove constants and tests for PKCS1 padding; it's insecure and
17309 shouldn't be used for anything new. Fixes bug 8792; patch
17311 - Remove instances of strcpy() from the unit tests. They weren't
17312 hurting anything, since they were only in the unit tests, but it's
17313 embarrassing to have strcpy() in the code at all, and some analysis
17314 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
17315 0.2.3.8-alpha. Patch from Arlo Breault.
17317 o Removed features:
17318 - Remove migration code from when we renamed the "cached-routers"
17319 file to "cached-descriptors" back in 0.2.0.8-alpha. This
17320 incidentally resolves ticket 6502 by cleaning up the related code
17321 a bit. Patch from Akshay Hebbar.
17323 o Code simplification and refactoring:
17324 - Extract the common duplicated code for creating a subdirectory
17325 of the data directory and writing to a file in it. Fixes ticket
17326 4282; patch from Peter Retzlaff.
17327 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
17328 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
17329 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
17330 - Add a set of accessor functions for the circuit timeout data
17331 structure. Fixes ticket 6153; patch from "piet".
17332 - Clean up exit paths from connection_listener_new(). Closes ticket
17333 8789. Patch from Arlo Breault.
17334 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
17335 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
17336 - Use a doubly-linked list to implement the global circuit list.
17337 Resolves ticket 9108. Patch from Marek Majkowski.
17338 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
17341 Changes in version 0.2.4.17-rc - 2013-09-05
17342 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
17343 series. It adds an emergency step to help us tolerate the massive
17344 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
17345 circuit-level handshakes now effectively jump the queue compared to
17346 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
17347 big bug hindering bridge reachability tests.
17350 - Relays now process the new "NTor" circuit-level handshake requests
17351 with higher priority than the old "TAP" circuit-level handshake
17352 requests. We still process some TAP requests to not totally starve
17353 0.2.3 clients when NTor becomes popular. A new consensus parameter
17354 "NumNTorsPerTAP" lets us tune the balance later if we need to.
17355 Implements ticket 9574.
17358 - If the circuit build timeout logic is disabled (via the consensus,
17359 or because we are an authority), then don't build testing circuits.
17360 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
17361 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
17362 previously they did not, which prevented them from receiving
17363 successful connections from relays for self-test or bandwidth
17364 testing. Also, when a relay is extending a circuit to a bridge,
17365 it needs to send a NETINFO cell, even when the bridge hasn't sent
17366 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
17367 - If the time to download the next old-style networkstatus is in
17368 the future, do not decline to consider whether to download the
17369 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
17373 - Avoid double-closing the listener socket in our socketpair()
17374 replacement (used on Windows) in the case where the addresses on
17375 our opened sockets don't match what we expected. Fixes bug 9400;
17376 bugfix on 0.0.2pre7. Found by Coverity.
17378 o Minor fixes (config options):
17379 - Avoid overflows when the user sets MaxCircuitDirtiness to a
17380 ridiculously high value, by imposing a (ridiculously high) 30-day
17381 maximum on MaxCircuitDirtiness.
17382 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
17383 message is logged at notice, not at info.
17384 - Warn and fail if a server is configured not to advertise any
17385 ORPorts at all. (We need *something* to put in our descriptor,
17386 or we just won't work.)
17389 - Track how many "TAP" and "NTor" circuit handshake requests we get,
17390 and how many we complete, and log it every hour to help relay
17391 operators follow trends in network load. Addresses ticket 9658.
17392 - Update to the August 7 2013 Maxmind GeoLite Country database.
17395 Changes in version 0.2.4.16-rc - 2013-08-10
17396 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
17397 series. It fixes several crash bugs in the 0.2.4 branch.
17400 - Fix a bug in the voting algorithm that could yield incorrect results
17401 when a non-naming authority declared too many flags. Fixes bug 9200;
17402 bugfix on 0.2.0.3-alpha.
17403 - Fix an uninitialized read that could in some cases lead to a remote
17404 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
17405 Anybody running a hidden service on the experimental 0.2.4.x
17406 branch should upgrade. (This is, so far as we know, unrelated to
17408 - Avoid an assertion failure when processing DNS replies without the
17409 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
17410 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
17411 0.2.4.15-rc. Found by stem integration tests.
17414 - Fix an invalid memory read that occurred when a pluggable
17415 transport proxy failed its configuration protocol.
17416 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
17417 - When evaluating whether to use a connection that we haven't
17418 decided is canonical using a recent link protocol version,
17419 decide that it's canonical only if it used address _does_
17420 match the desired address. Fixes bug 9309; bugfix on
17421 0.2.4.4-alpha. Reported by skruffy.
17422 - Make the default behavior of NumDirectoryGuards be to track
17423 NumEntryGuards. Now a user who changes only NumEntryGuards will get
17424 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
17425 - Fix a spurious compilation warning with some older versions of
17426 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
17429 - Update to the July 3 2013 Maxmind GeoLite Country database.
17432 Changes in version 0.2.4.15-rc - 2013-07-01
17433 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
17434 series. It fixes a few smaller bugs, but generally appears stable.
17435 Please test it and let us know whether it is!
17438 - When receiving a new configuration file via the control port's
17439 LOADCONF command, do not treat the defaults file as absent.
17440 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
17443 - Issue a warning when running with the bufferevents backend enabled.
17444 It's still not stable, and people should know that they're likely
17445 to hit unexpected problems. Closes ticket 9147.
17448 Changes in version 0.2.4.14-alpha - 2013-06-18
17449 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
17450 present in 0.2.4.13-alpha.
17453 - When we have too much memory queued in circuits (according to a new
17454 MaxMemInCellQueues option), close the circuits consuming the most
17455 memory. This prevents us from running out of memory as a relay if
17456 circuits fill up faster than they can be drained. Fixes bug 9063;
17457 bugfix on the 54th commit of Tor. This bug is a further fix beyond
17458 bug 6252, whose fix was merged into 0.2.3.21-rc.
17460 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
17461 where we tried to solve this issue simply by imposing an upper limit
17462 on the number of queued cells for a single circuit. That approach
17463 proved to be problematic, since there are ways to provoke clients to
17464 send a number of cells in excess of any such reasonable limit. Fixes
17465 bug 9072; bugfix on 0.2.4.13-alpha.
17467 - Limit hidden service descriptors to at most ten introduction
17468 points, to slow one kind of guard enumeration. Fixes bug 9002;
17469 bugfix on 0.1.1.11-alpha.
17472 Changes in version 0.2.4.13-alpha - 2013-06-14
17473 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
17474 vulnerabilities, makes socks5 username/password circuit isolation
17475 actually actually work (this time for sure!), and cleans up a bunch
17476 of other issues in preparation for a release candidate.
17478 o Major bugfixes (robustness):
17479 - Close any circuit that has too many cells queued on it. Fixes
17480 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
17481 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
17482 - Prevent the get_freelists() function from running off the end of
17483 the list of freelists if it somehow gets an unrecognized
17484 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
17486 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
17487 when an exit connection with optimistic data succeeds immediately
17488 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
17490 - Fix a directory authority crash bug when building a consensus
17491 using an older consensus as its basis. Fixes bug 8833. Bugfix
17495 - Avoid a memory leak where we would leak a consensus body when we
17496 find that a consensus which we couldn't previously verify due to
17497 missing certificates is now verifiable. Fixes bug 8719; bugfix
17499 - We used to always request authority certificates by identity digest,
17500 meaning we'd get the newest one even when we wanted one with a
17501 different signing key. Then we would complain about being given
17502 a certificate we already had, and never get the one we really
17503 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
17504 resource to request the one we want. Fixes bug 5595; bugfix on
17506 - Follow the socks5 protocol when offering username/password
17507 authentication. The fix for bug 8117 exposed this bug, and it
17508 turns out real-world applications like Pidgin do care. Bugfix on
17509 0.2.3.2-alpha; fixes bug 8879.
17510 - Prevent failures on Windows Vista and later when rebuilding the
17511 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
17512 bugfix on 0.2.4.12-alpha.
17515 - Fix an impossible buffer overrun in the AES unit tests. Fixes
17516 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
17517 - If for some reason we fail to write a microdescriptor while
17518 rebuilding the cache, do not let the annotations from that
17519 microdescriptor linger in the cache file, and do not let the
17520 microdescriptor stay recorded as present in its old location.
17521 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
17522 - Fix a memory leak that would occur whenever a configuration
17523 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
17524 - Paste the description for PathBias parameters from the man
17525 page into or.h, so the code documents them too. Fixes bug 7982;
17526 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
17527 - Relays now treat a changed IPv6 ORPort as sufficient reason to
17528 publish an updated descriptor. Fixes bug 6026; bugfix on
17530 - When launching a resolve request on behalf of an AF_UNIX control
17531 socket, omit the address field of the new entry connection, used in
17532 subsequent controller events, rather than letting tor_dup_addr()
17533 set it to "<unknown address type>". Fixes bug 8639; bugfix on
17536 o Minor bugfixes (log messages):
17537 - Fix a scaling issue in the path bias accounting code that
17538 resulted in "Bug:" log messages from either
17539 pathbias_scale_close_rates() or pathbias_count_build_success().
17540 This represents a bugfix on a previous bugfix: the original fix
17541 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
17543 - Give a less useless error message when the user asks for an IPv4
17544 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
17548 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
17549 to tolerate bug 8093 for now.
17550 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
17551 in directory authority votes to describe whether they have enough
17552 measured bandwidths to ignore advertised (relay descriptor)
17553 bandwidth claims. Resolves ticket 8711.
17554 - Update to the June 5 2013 Maxmind GeoLite Country database.
17556 o Removed documentation:
17557 - Remove some of the older contents of doc/ as obsolete; move others
17558 to torspec.git. Fixes bug 8965.
17560 o Code simplification and refactoring:
17561 - Avoid using character buffers when constructing most directory
17562 objects: this approach was unwieldy and error-prone. Instead,
17563 build smartlists of strings, and concatenate them when done.
17566 Changes in version 0.2.4.12-alpha - 2013-04-18
17567 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
17568 process for lengthening the guard rotation period, makes directory
17569 authority opinions in the consensus a bit less gameable, makes socks5
17570 username/password circuit isolation actually work, and fixes a wide
17571 variety of other issues.
17574 - Raise the default time that a client keeps an entry guard from
17575 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
17576 2012 paper. (We would make it even longer, but we need better client
17577 load balancing first.) Also, make the guard lifetime controllable
17578 via a new GuardLifetime torrc option and a GuardLifetime consensus
17579 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
17580 - Directory authorities now prefer using measured bandwidths to
17581 advertised ones when computing flags and thresholds. Resolves
17583 - Directory authorities that have more than a threshold number
17584 of relays with measured bandwidths now treat relays with unmeasured
17585 bandwidths as having bandwidth 0. Resolves ticket 8435.
17587 o Major bugfixes (assert / resource use):
17588 - Avoid a bug where our response to TLS renegotiation under certain
17589 network conditions could lead to a busy-loop, with 100% CPU
17590 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
17591 - Avoid an assertion when we discover that we'd like to write a cell
17592 onto a closing connection: just discard the cell. Fixes another
17593 case of bug 7350; bugfix on 0.2.4.4-alpha.
17595 o Major bugfixes (client-side privacy):
17596 - When we mark a circuit as unusable for new circuits, have it
17597 continue to be unusable for new circuits even if MaxCircuitDirtiness
17598 is increased too much at the wrong time, or the system clock jumps
17599 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
17600 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
17601 which have resolved to internal addresses") is set, apply that
17602 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
17603 - When an exit relay rejects a stream with reason "exit policy", but
17604 we only know an exit policy summary (e.g. from the microdesc
17605 consensus) for it, do not mark the relay as useless for all exiting.
17606 Instead, mark just the circuit as unsuitable for that particular
17607 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
17608 - Allow applications to get proper stream isolation with
17609 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
17610 username/password authentication also offer "no authentication". Tor
17611 had previously preferred "no authentication", so the applications
17612 never actually sent Tor their auth details. Now Tor selects
17613 username/password authentication if it's offered. You can disable
17614 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
17615 bug 8117; bugfix on 0.2.3.3-alpha.
17617 o Major bugfixes (other):
17618 - When unable to find any working directory nodes to use as a
17619 directory guard, give up rather than adding the same non-working
17620 nodes to the directory guard list over and over. Fixes bug 8231;
17621 bugfix on 0.2.4.8-alpha.
17624 - Reject as invalid most directory objects containing a NUL.
17625 Belt-and-suspender fix for bug 8037.
17626 - In our testsuite, create temporary directories with a bit more
17627 entropy in their name to make name collisions less likely. Fixes
17629 - Add CACHED keyword to ADDRMAP events in the control protocol
17630 to indicate whether a DNS result will be cached or not. Resolves
17632 - Update to the April 3 2013 Maxmind GeoLite Country database.
17634 o Minor features (build):
17635 - Detect and reject attempts to build Tor with threading support
17636 when OpenSSL has been compiled without threading support.
17638 - Clarify that when autoconf is checking for nacl, it is checking
17639 specifically for nacl with a fast curve25519 implementation.
17641 - Warn if building on a platform with an unsigned time_t: there
17642 are too many places where Tor currently assumes that time_t can
17643 hold negative values. We'd like to fix them all, but probably
17646 o Minor bugfixes (build):
17647 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
17648 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
17649 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
17650 - Add the old src/or/micro-revision.i filename to CLEANFILES.
17651 On the off chance that somebody has one, it will go away as soon
17652 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
17653 - Build Tor correctly on 32-bit platforms where the compiler can build
17654 but not run code using the "uint128_t" construction. Fixes bug 8587;
17655 bugfix on 0.2.4.8-alpha.
17656 - Fix compilation warning with some versions of clang that would
17657 prefer the -Wswitch-enum compiler flag to warn about switch
17658 statements with missing enum values, even if those switch
17659 statements have a "default:" statement. Fixes bug 8598; bugfix
17662 o Minor bugfixes (protocol):
17663 - Fix the handling of a TRUNCATE cell when it arrives while the
17664 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
17665 - Fix a misframing issue when reading the version numbers in a
17666 VERSIONS cell. Previously we would recognize [00 01 00 02] as
17667 'version 1, version 2, and version 0x100', when it should have
17668 only included versions 1 and 2. Fixes bug 8059; bugfix on
17669 0.2.0.10-alpha. Reported pseudonymously.
17670 - Make the format and order of STREAM events for DNS lookups
17671 consistent among the various ways to launch DNS lookups. Fixes
17672 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy".
17673 - Correct our check for which versions of Tor support the EXTEND2
17674 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
17675 later, when support was really added in version 0.2.4.8-alpha.
17676 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
17678 o Minor bugfixes (other):
17679 - Correctly store microdescriptors and extrainfo descriptors with
17680 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
17681 Bug reported by "cypherpunks".
17682 - Increase the width of the field used to remember a connection's
17683 link protocol version to two bytes. Harmless for now, since the
17684 only currently recognized versions are one byte long. Reported
17685 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
17686 - If the state file's path bias counts are invalid (presumably from a
17687 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
17688 additional checks and log messages to the scaling of Path Bias
17689 counts, in case there still are remaining issues with scaling.
17690 Should help resolve bug 8235.
17691 - Eliminate several instances where we use "Nickname=ID" to refer to
17692 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
17693 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
17694 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
17696 o Minor bugfixes (syscalls):
17697 - Always check the return values of functions fcntl() and
17698 setsockopt(). We don't believe these are ever actually failing in
17699 practice, but better safe than sorry. Also, checking these return
17700 values should please analysis tools like Coverity. Patch from
17701 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
17702 - Use direct writes rather than stdio when building microdescriptor
17703 caches, in an attempt to mitigate bug 8031, or at least make it
17706 o Minor bugfixes (config):
17707 - When rejecting a configuration because we were unable to parse a
17708 quoted string, log an actual error message. Fixes bug 7950; bugfix
17710 - Behave correctly when the user disables LearnCircuitBuildTimeout
17711 but doesn't tell us what they would like the timeout to be. Fixes
17712 bug 6304; bugfix on 0.2.2.14-alpha.
17713 - When autodetecting the number of CPUs, use the number of available
17714 CPUs in preference to the number of configured CPUs. Inform the
17715 user if this reduces the number of available CPUs. Fixes bug 8002;
17716 bugfix on 0.2.3.1-alpha.
17717 - Make it an error when you set EntryNodes but disable UseGuardNodes,
17718 since it will (surprisingly to some users) ignore EntryNodes. Fixes
17719 bug 8180; bugfix on 0.2.3.11-alpha.
17720 - Allow TestingTorNetworks to override the 4096-byte minimum for
17721 the Fast threshold. Otherwise they can't bootstrap until they've
17722 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
17723 - Fix some logic errors when the user manually overrides the
17724 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
17727 o Minor bugfixes (log messages to help diagnose bugs):
17728 - If we fail to free a microdescriptor because of bug 7164, log
17729 the filename and line number from which we tried to free it.
17730 - Add another diagnostic to the heartbeat message: track and log
17731 overhead that TLS is adding to the data we write. If this is
17732 high, we are sending too little data to SSL_write at a time.
17733 Diagnostic for bug 7707.
17734 - Add more detail to a log message about relaxed timeouts, to help
17736 - Warn more aggressively when flushing microdescriptors to a
17737 microdescriptor cache fails, in an attempt to mitigate bug 8031,
17738 or at least make it more diagnosable.
17739 - Improve debugging output to help track down bug 8185 ("Bug:
17740 outgoing relay cell has n_chan==NULL. Dropping.")
17741 - Log the purpose of a path-bias testing circuit correctly.
17742 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
17744 o Minor bugfixes (0.2.4.x log messages that were too noisy):
17745 - Don't attempt to relax the timeout of already opened 1-hop circuits.
17746 They might never timeout. This should eliminate some/all cases of
17747 the relaxed timeout log message.
17748 - Use circuit creation time for network liveness evaluation. This
17749 should eliminate warning log messages about liveness caused
17750 by changes in timeout evaluation. Fixes bug 6572; bugfix on
17752 - Reduce a path bias length check from notice to info. The message
17753 is triggered when creating controller circuits. Fixes bug 8196;
17754 bugfix on 0.2.4.8-alpha.
17755 - Fix a path state issue that triggered a notice during relay startup.
17756 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
17757 - Reduce occurrences of warns about circuit purpose in
17758 connection_ap_expire_building(). Fixes bug 8477; bugfix on
17761 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
17762 - If we encounter a write failure on a SOCKS connection before we
17763 finish our SOCKS handshake, don't warn that we closed the
17764 connection before we could send a SOCKS reply. Fixes bug 8427;
17765 bugfix on 0.1.0.1-rc.
17766 - Correctly recognize that [::1] is a loopback address. Fixes
17767 bug 8377; bugfix on 0.2.1.3-alpha.
17768 - Fix a directory authority warn caused when we have a large amount
17769 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
17770 - Don't log inappropriate heartbeat messages when hibernating: a
17771 hibernating node is _expected_ to drop out of the consensus,
17772 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
17773 bugfix on 0.2.3.1-alpha.
17774 - Don't complain about bootstrapping problems while hibernating.
17775 These complaints reflect a general code problem, but not one
17776 with any problematic effects (no connections are actually
17777 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
17779 o Documentation fixes:
17780 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
17781 names match. Fixes bug 7768.
17782 - Make the torify manpage no longer refer to tsocks; torify hasn't
17783 supported tsocks since 0.2.3.14-alpha.
17784 - Make the tor manpage no longer reference tsocks.
17785 - Fix the GeoIPExcludeUnknown documentation to refer to
17786 ExcludeExitNodes rather than the currently nonexistent
17787 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
17790 - The tor-tsocks.conf is no longer distributed or installed. We
17791 recommend that tsocks users use torsocks instead. Resolves
17795 Changes in version 0.2.4.11-alpha - 2013-03-11
17796 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
17797 more robust, makes hidden service authentication work again, and
17798 resolves a DPI fingerprint for Tor's SSL transport.
17800 o Major features (directory authorities):
17801 - Directory authorities now support a new consensus method (17)
17802 where they cap the published bandwidth of servers for which
17803 insufficient bandwidth measurements exist. Fixes part of bug 2286.
17804 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
17805 serve any v2 directory information. Now we can test disabling the
17806 old deprecated v2 directory format, and see whether doing so has
17807 any effect on network load. Begins to fix bug 6783.
17808 - Directory authorities now include inside each vote a statement of
17809 the performance thresholds they used when assigning flags.
17810 Implements ticket 8151.
17812 o Major bugfixes (directory authorities):
17813 - Stop marking every relay as having been down for one hour every
17814 time we restart a directory authority. These artificial downtimes
17815 were messing with our Stable and Guard flag calculations. Fixes
17816 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
17818 o Major bugfixes (hidden services):
17819 - Allow hidden service authentication to succeed again. When we
17820 refactored the hidden service introduction code back
17821 in 0.2.4.1-alpha, we didn't update the code that checks
17822 whether authentication information is present, causing all
17823 authentication checks to return "false". Fix for bug 8207; bugfix
17824 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
17826 o Minor features (relays, bridges):
17827 - Make bridge relays check once a minute for whether their IP
17828 address has changed, rather than only every 15 minutes. Resolves
17829 bugs 1913 and 1992.
17830 - Refactor resolve_my_address() so it returns the method by which we
17831 decided our public IP address (explicitly configured, resolved from
17832 explicit hostname, guessed from interfaces, learned by gethostname).
17833 Now we can provide more helpful log messages when a relay guesses
17834 its IP address incorrectly (e.g. due to unexpected lines in
17835 /etc/hosts). Resolves ticket 2267.
17836 - Teach bridge-using clients to avoid 0.2.2 bridges when making
17837 microdescriptor-related dir requests, and only fall back to normal
17838 descriptors if none of their bridges can handle microdescriptors
17839 (as opposed to the fix in ticket 4013, which caused them to fall
17840 back to normal descriptors if *any* of their bridges preferred
17841 them). Resolves ticket 4994.
17842 - Randomize the lifetime of our SSL link certificate, so censors can't
17843 use the static value for filtering Tor flows. Resolves ticket 8443;
17844 related to ticket 4014 which was included in 0.2.2.33.
17845 - Support a new version of the link protocol that allows 4-byte circuit
17846 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
17847 a possible resource exhaustion issue. Closes ticket 7351; implements
17850 o Minor features (portability):
17851 - Tweak the curve25519-donna*.c implementations to tolerate systems
17852 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
17853 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
17854 the signs of types during autoconf. This is better than our old
17855 approach, which didn't work when cross-compiling.
17856 - Detect the sign of enum values, rather than assuming that MSC is the
17857 only compiler where enum types are all signed. Fixes bug 7727;
17858 bugfix on 0.2.4.10-alpha.
17860 o Minor features (other):
17861 - Say "KBytes" rather than "KB" in the man page (for various values
17862 of K), to further reduce confusion about whether Tor counts in
17863 units of memory or fractions of units of memory. Resolves ticket 7054.
17864 - Clear the high bit on curve25519 public keys before passing them to
17865 our backend, in case we ever wind up using a backend that doesn't do
17866 so itself. If we used such a backend, and *didn't* clear the high bit,
17867 we could wind up in a situation where users with such backends would
17868 be distinguishable from users without. Fixes bug 8121; bugfix on
17870 - Update to the March 6 2013 Maxmind GeoLite Country database.
17872 o Minor bugfixes (clients):
17873 - When we receive a RELAY_END cell with the reason DONE, or with no
17874 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
17875 status as "connection refused". Previously we reported these cases
17876 as success but then immediately closed the connection. Fixes bug
17877 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
17878 - Downgrade an assertion in connection_ap_expire_beginning to an
17879 LD_BUG message. The fix for bug 8024 should prevent this message
17880 from displaying, but just in case, a warn that we can diagnose
17881 is better than more assert crashes. Fixes bug 8065; bugfix on
17883 - Lower path use bias thresholds to .80 for notice and .60 for warn.
17884 Also make the rate limiting flags for the path use bias log messages
17885 independent from the original path bias flags. Fixes bug 8161;
17886 bugfix on 0.2.4.10-alpha.
17888 o Minor bugfixes (relays):
17889 - Stop trying to resolve our hostname so often (e.g. every time we
17890 think about doing a directory fetch). Now we reuse the cached
17891 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
17892 and 2410 (bugfix on 0.1.2.2-alpha).
17893 - Stop sending a stray "(null)" in some cases for the server status
17894 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
17896 - When choosing which stream on a formerly stalled circuit to wake
17897 first, make better use of the platform's weak RNG. Previously,
17898 we had been using the % ("modulo") operator to try to generate a
17899 1/N chance of picking each stream, but this behaves badly with
17900 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
17902 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
17903 Irix's random() only return 15 bits; Solaris's random() returns more
17904 bits but its RAND_MAX says it only returns 15, and so on. Motivated
17905 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
17907 o Minor bugfixes (directory authorities):
17908 - Directory authorities now use less space when formatting identical
17909 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
17912 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
17913 - Avoid leaking memory if we fail to compute a consensus signature
17914 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
17915 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
17917 - Fix a memory leak during safe-cookie controller authentication.
17918 Bugfix on 0.2.3.13-alpha.
17919 - Avoid memory leak of IPv6 policy content if we fail to format it into
17920 a router descriptor. Bugfix on 0.2.4.7-alpha.
17922 o Minor bugfixes (other code correctness issues):
17923 - Avoid a crash if we fail to generate an extrainfo descriptor.
17924 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
17925 this is CID 718634.
17926 - When detecting the largest possible file descriptor (in order to
17927 close all file descriptors when launching a new program), actually
17928 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
17929 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
17931 - Fix a copy-and-paste error when adding a missing A1 to a routerset
17932 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
17933 Bugfix on 0.2.4.10-alpha.
17934 - Fix an impossible-to-trigger integer overflow when estimating how
17935 long our onionskin queue would take. (This overflow would require us
17936 to accept 4 million onionskins before processing 100 of them.) Fixes
17937 bug 8210; bugfix on 0.2.4.10-alpha.
17939 o Code simplification and refactoring:
17940 - Add a wrapper function for the common "log a message with a
17944 Changes in version 0.2.4.10-alpha - 2013-02-04
17945 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
17946 certain attacks that flood the network with relays; changes the queue
17947 for circuit create requests from a sized-based limit to a time-based
17948 limit; resumes building with MSVC on Windows; and fixes a wide variety
17951 o Major bugfixes (directory authority):
17952 - When computing directory thresholds, ignore any rejected-as-sybil
17953 nodes during the computation so that they can't influence Fast,
17954 Guard, etc. (We should have done this for proposal 109.) Fixes
17956 - When marking a node as a likely sybil, reset its uptime metrics
17957 to zero, so that it cannot time towards getting marked as Guard,
17958 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
17962 - When a TLS write is partially successful but incomplete, remember
17963 that the flushed part has been flushed, and notice that bytes were
17964 actually written. Reported and fixed pseudonymously. Fixes bug
17965 7708; bugfix on Tor 0.1.0.5-rc.
17966 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
17967 ID: these could be used to create unexpected streams and circuits
17968 which would count as "present" to some parts of Tor but "absent"
17969 to others, leading to zombie circuits and streams or to a bandwidth
17970 denial-of-service. Fixes bug 7889; bugfix on every released version
17971 of Tor. Reported by "oftc_must_be_destroyed".
17972 - Rename all macros in our local copy of queue.h to begin with "TOR_".
17973 This change seems the only good way to permanently prevent conflicts
17974 with queue.h on various operating systems. Fixes bug 8107; bugfix
17977 o Major features (relay):
17978 - Instead of limiting the number of queued onionskins (aka circuit
17979 create requests) to a fixed, hard-to-configure number, we limit
17980 the size of the queue based on how many we expect to be able to
17981 process in a given amount of time. We estimate the time it will
17982 take to process an onionskin based on average processing time
17983 of previous onionskins. Closes ticket 7291. You'll never have to
17984 configure MaxOnionsPending again.
17986 o Major features (portability):
17987 - Resume building correctly with MSVC and Makefile.nmake. This patch
17988 resolves numerous bugs and fixes reported by ultramage, including
17989 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
17990 - Make the ntor and curve25519 code build correctly with MSVC.
17991 Fix on 0.2.4.8-alpha.
17994 - When directory authorities are computing thresholds for flags,
17995 never let the threshold for the Fast flag fall below 4096
17996 bytes. Also, do not consider nodes with extremely low bandwidths
17997 when deciding thresholds for various directory flags. This change
17998 should raise our threshold for Fast relays, possibly in turn
17999 improving overall network performance; see ticket 1854. Resolves
18001 - The Tor client now ignores sub-domain components of a .onion
18002 address. This change makes HTTP "virtual" hosting
18003 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
18004 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
18005 hosted on the same hidden service. Implements proposal 204.
18006 - We compute the overhead from passing onionskins back and forth to
18007 cpuworkers, and report it when dumping statistics in response to
18008 SIGUSR1. Supports ticket 7291.
18010 o Minor features (path selection):
18011 - When deciding whether we have enough descriptors to build circuits,
18012 instead of looking at raw relay counts, look at which fraction
18013 of (bandwidth-weighted) paths we're able to build. This approach
18014 keeps clients from building circuits if their paths are likely to
18015 stand out statistically. The default fraction of paths needed is
18016 taken from the consensus directory; you can override it with the
18017 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
18018 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
18019 and we have GeoIP information, also exclude all nodes with unknown
18020 countries "??" and "A1". This behavior is controlled by the
18021 new GeoIPExcludeUnknown option: you can make such nodes always
18022 excluded with "GeoIPExcludeUnknown 1", and disable the feature
18023 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
18024 gets you the default behavior. Implements feature 7706.
18025 - Path Use Bias: Perform separate accounting for successful circuit
18026 use. Keep separate statistics on stream attempt rates versus stream
18027 success rates for each guard. Provide configurable thresholds to
18028 determine when to emit log messages or disable use of guards that
18029 fail too many stream attempts. Resolves ticket 7802.
18031 o Minor features (log messages):
18032 - When learning a fingerprint for a bridge, log its corresponding
18033 transport type. Implements ticket 7896.
18034 - Improve the log message when "Bug/attack: unexpected sendme cell
18035 from client" occurs, to help us track bug 8093.
18038 - Remove a couple of extraneous semicolons that were upsetting the
18039 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
18040 bugfix on 0.2.2.1-alpha.
18041 - Remove a source of rounding error during path bias count scaling;
18042 don't count cannibalized circuits as used for path bias until we
18043 actually try to use them; and fix a circuit_package_relay_cell()
18044 warning message about n_chan==NULL. Fixes bug 7802.
18045 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
18046 actually link against nacl when we're configured to use it. Fixes
18047 bug 7972; bugfix on 0.2.4.8-alpha.
18048 - Compile correctly with the --disable-curve25519 option. Fixes
18049 bug 8153; bugfix on 0.2.4.8-alpha.
18051 o Build improvements:
18052 - Do not report status verbosely from autogen.sh unless the -v flag
18053 is specified. Fixes issue 4664. Patch from Onizuka.
18054 - Replace all calls to snprintf() outside of src/ext with
18055 tor_snprintf(). Also remove the #define to replace snprintf with
18056 _snprintf on Windows; they have different semantics, and all of
18057 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
18058 - Try to detect if we are ever building on a platform where
18059 memset(...,0,...) does not set the value of a double to 0.0. Such
18060 platforms are permitted by the C standard, though in practice
18061 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
18062 currently support them, but it's better to detect them and fail
18063 than to perform erroneously.
18065 o Removed features:
18066 - Stop exporting estimates of v2 and v3 directory traffic shares
18067 in extrainfo documents. They were unneeded and sometimes inaccurate.
18068 Also stop exporting any v2 directory request statistics. Resolves
18070 - Drop support for detecting and warning about versions of Libevent
18071 before 1.3e. Nothing reasonable ships with them any longer;
18072 warning the user about them shouldn't be needed. Resolves ticket
18075 o Code simplifications and refactoring:
18076 - Rename "isin" functions to "contains", for grammar. Resolves
18078 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
18079 with the natural logarithm function from the system libm. Resolves
18083 Changes in version 0.2.4.9-alpha - 2013-01-15
18084 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
18085 work more robustly.
18088 - Fix backward compatibility logic when receiving an embedded ntor
18089 handshake tunneled in a CREATE cell. This clears up the "Bug:
18090 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
18094 Changes in version 0.2.4.8-alpha - 2013-01-14
18095 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
18096 risks, adds a new stronger and faster circuit handshake, and offers
18097 stronger and faster link encryption when both sides support it.
18100 - Preliminary support for directory guards (proposal 207): when
18101 possible, clients now use their entry guards for non-anonymous
18102 directory requests. This can help prevent client enumeration. Note
18103 that this behavior only works when we have a usable consensus
18104 directory, and when options about what to download are more or less
18105 standard. In the future we should re-bootstrap from our guards,
18106 rather than re-bootstrapping from the preconfigured list of
18107 directory sources that ships with Tor. Resolves ticket 6526.
18108 - Tor relays and clients now support a better CREATE/EXTEND cell
18109 format, allowing the sender to specify multiple address, identity,
18110 and handshake types. Implements Robert Ransom's proposal 200;
18111 closes ticket 7199.
18113 o Major features (new circuit handshake):
18114 - Tor now supports a new circuit extension handshake designed by Ian
18115 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
18116 circuit extension handshake, later called "TAP", was a bit slow
18117 (especially on the relay side), had a fragile security proof, and
18118 used weaker keys than we'd now prefer. The new circuit handshake
18119 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
18120 function, making it significantly more secure than the older
18121 handshake, and significantly faster. Tor can use one of two built-in
18122 pure-C curve25519-donna implementations by Adam Langley, or it
18123 can link against the "nacl" library for a tuned version if present.
18125 The built-in version is very fast for 64-bit systems when building
18126 with GCC. The built-in 32-bit version is still faster than the
18127 old TAP protocol, but using libnacl is better on most such hosts.
18129 Clients don't currently use this protocol by default, since
18130 comparatively few clients support it so far. To try it, set
18131 UseNTorHandshake to 1.
18133 Implements proposal 216; closes ticket 7202.
18135 o Major features (better link encryption):
18136 - Relays can now enable the ECDHE TLS ciphersuites when available
18137 and appropriate. These ciphersuites let us negotiate forward-secure
18138 TLS secret keys more safely and more efficiently than with our
18139 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
18140 public relays prefer the (faster) P224 group, and bridges prefer
18141 the (more common) P256 group; you can override this with the
18144 Enabling these ciphers was a little tricky, since for a long time,
18145 clients had been claiming to support them without actually doing
18146 so, in order to foil fingerprinting. But with the client-side
18147 implementation of proposal 198 in 0.2.3.17-beta, clients can now
18148 match the ciphers from recent Firefox versions *and* list the
18149 ciphers they actually mean, so relays can believe such clients
18150 when they advertise ECDHE support in their TLS ClientHello messages.
18152 This feature requires clients running 0.2.3.17-beta or later,
18153 and requires both sides to be running OpenSSL 1.0.0 or later
18154 with ECC support. OpenSSL 1.0.1, with the compile-time option
18155 "enable-ec_nistp_64_gcc_128", is highly recommended.
18157 Implements the relay side of proposal 198; closes ticket 7200.
18160 - Avoid crashing when, as a relay without IPv6-exit support, a
18161 client insists on getting an IPv6 address or nothing. Fixes bug
18162 7814; bugfix on 0.2.4.7-alpha.
18165 - Improve circuit build timeout handling for hidden services.
18166 In particular: adjust build timeouts more accurately depending
18167 upon the number of hop-RTTs that a particular circuit type
18168 undergoes. Additionally, launch intro circuits in parallel
18169 if they timeout, and take the first one to reply as valid.
18170 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
18171 separate error codes; or at least, don't break for that reason.
18172 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
18173 - Update to the January 2 2013 Maxmind GeoLite Country database.
18175 o Minor features (testing):
18176 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
18177 (P-256) Diffie-Hellman handshakes to src/or/bench.
18178 - Add benchmark functions to test onion handshake performance.
18180 o Minor features (path bias detection):
18181 - Alter the Path Bias log messages to be more descriptive in terms
18182 of reporting timeouts and other statistics.
18183 - Create three levels of Path Bias log messages, as opposed to just
18184 two. These are configurable via consensus as well as via the torrc
18185 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
18186 The default values are 0.70, 0.50, and 0.30 respectively.
18187 - Separate the log message levels from the decision to drop guards,
18188 which also is available via torrc option PathBiasDropGuards.
18189 PathBiasDropGuards still defaults to 0 (off).
18190 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
18191 in combination with PathBiasExtremeRate.
18192 - Increase the default values for PathBiasScaleThreshold and
18193 PathBiasCircThreshold from (200, 20) to (300, 150).
18194 - Add in circuit usage accounting to path bias. If we try to use a
18195 built circuit but fail for any reason, it counts as path bias.
18196 Certain classes of circuits where the adversary gets to pick your
18197 destination node are exempt from this accounting. Usage accounting
18198 can be specifically disabled via consensus parameter or torrc.
18199 - Convert all internal path bias state to double-precision floating
18200 point, to avoid roundoff error and other issues.
18201 - Only record path bias information for circuits that have completed
18202 *two* hops. Assuming end-to-end tagging is the attack vector, this
18203 makes us more resilient to ambient circuit failure without any
18204 detection capability loss.
18206 o Minor bugfixes (log messages):
18207 - Rate-limit the "No circuits are opened. Relaxed timeout for a
18208 circuit with channel state open..." message to once per hour to
18209 keep it from filling the notice logs. Mitigates bug 7799 but does
18210 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
18211 - Avoid spurious warnings when configuring multiple client ports of
18212 which only some are nonlocal. Previously, we had claimed that some
18213 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
18216 o Code simplifications and refactoring:
18217 - Get rid of a couple of harmless clang warnings, where we compared
18218 enums to ints. These warnings are newly introduced in clang 3.2.
18219 - Split the onion.c file into separate modules for the onion queue
18220 and the different handshakes it supports.
18221 - Remove the marshalling/unmarshalling code for sending requests to
18222 cpuworkers over a socket, and instead just send structs. The
18223 recipient will always be the same Tor binary as the sender, so
18224 any encoding is overkill.
18227 Changes in version 0.2.4.7-alpha - 2012-12-24
18228 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
18229 directory mirrors for more robust bootstrapping; fixes more issues where
18230 clients with changing network conditions refuse to make any circuits;
18231 adds initial support for exiting to IPv6 addresses; resumes being able
18232 to update our GeoIP database, and includes the geoip6 file this time;
18233 turns off the client-side DNS cache by default due to privacy risks;
18234 and fixes a variety of other issues.
18236 o Major features (client resilience):
18237 - Add a new "FallbackDir" torrc option to use when we can't use
18238 a directory mirror from the consensus (either because we lack a
18239 consensus, or because they're all down). Currently, all authorities
18240 are fallbacks by default, and there are no other default fallbacks,
18241 but that will change. This option will allow us to give clients a
18242 longer list of servers to try to get a consensus from when first
18243 connecting to the Tor network, and thereby reduce load on the
18244 directory authorities. Implements proposal 206, "Preconfigured
18245 directory sources for bootstrapping". We also removed the old
18246 "FallbackNetworkstatus" option, since we never got it working well
18247 enough to use it. Closes bug 572.
18248 - If we have no circuits open, use a relaxed timeout (the
18249 95-percentile cutoff) until a circuit succeeds. This heuristic
18250 should allow Tor to succeed at building circuits even when the
18251 network connection drastically changes. Should help with bug 3443.
18253 o Major features (IPv6):
18254 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
18255 connectivity, then set the IPv6Exit flag to 1. Also make sure your
18256 exit policy reads as you would like: the address * applies to all
18257 address families, whereas *4 is IPv4 address only, and *6 is IPv6
18258 addresses only. On the client side, you'll need to wait until the
18259 authorities have upgraded, wait for enough exits to support IPv6,
18260 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
18261 ticket 5547, implements proposal 117 as revised in proposal 208.
18263 We DO NOT recommend that clients with actual anonymity needs start
18264 using IPv6 over Tor yet, since not enough exits support it yet.
18266 o Major features (geoip database):
18267 - Maxmind began labelling Tor relays as being in country "A1",
18268 which breaks by-country node selection inside Tor. Now we use a
18269 script to replace "A1" ("Anonymous Proxy") entries in our geoip
18270 file with real country codes. This script fixes about 90% of "A1"
18271 entries automatically and uses manual country code assignments to
18272 fix the remaining 10%. See src/config/README.geoip for details.
18273 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
18274 Country database, as modified above.
18276 o Major bugfixes (client-side DNS):
18277 - Turn off the client-side DNS cache by default. Updating and using
18278 the DNS cache is now configurable on a per-client-port
18279 level. SOCKSPort, DNSPort, etc lines may now contain
18280 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
18281 cache these types of DNS answers when we receive them from an
18282 exit node in response to an application request on this port, and
18283 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
18284 cached DNS answers of these types, we shouldn't use them. It's
18285 potentially risky to use cached DNS answers at the client, since
18286 doing so can indicate to one exit what answers we've gotten
18287 for DNS lookups in the past. With IPv6, this becomes especially
18288 problematic. Using cached DNS answers for requests on the same
18289 circuit would present less linkability risk, since all traffic
18290 on a circuit is already linkable, but it would also provide
18291 little performance benefit: the exit node caches DNS replies
18292 too. Implements a simplified version of Proposal 205. Implements
18295 o Major bugfixes (other):
18296 - Alter circuit build timeout measurement to start at the point
18297 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
18298 initialization). This should make our timeout measurements more
18299 uniform. Previously, we were sometimes including ORconn setup time
18300 in our circuit build time measurements. Should resolve bug 3443.
18301 - Fix an assertion that could trigger in hibernate_go_dormant() when
18302 closing an or_connection_t: call channel_mark_for_close() rather
18303 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
18305 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
18306 7655; bugfix on 0.2.4.6-alpha.
18309 - Add a new torrc option "ServerTransportListenAddr" to let bridge
18310 operators select the address where their pluggable transports will
18311 listen for connections. Resolves ticket 7013.
18312 - Allow an optional $ before the node identity digest in the
18313 controller command GETINFO ns/id/<identity>, for consistency with
18314 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
18315 - Log packaged cell fullness as part of the heartbeat message.
18316 Diagnosis to try to determine the extent of bug 7743.
18318 o Minor features (IPv6):
18319 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
18320 prefer to hand out virtual IPv6 addresses, since there are more of
18321 them and we can't run out. To override this behavior and make IPv4
18322 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
18323 or DNSPort you're using for resolving. Implements ticket 7571.
18324 - AutomapHostsOnResolve responses are now randomized, to avoid
18325 annoying situations where Tor is restarted and applications
18326 connect to the wrong addresses.
18327 - Never try more than 1000 times to pick a new virtual address when
18328 AutomapHostsOnResolve is set. That's good enough so long as we
18329 aren't close to handing out our entire virtual address space;
18330 if you're getting there, it's best to switch to IPv6 virtual
18334 - The ADDRMAP command can no longer generate an ill-formed error
18335 code on a failed MAPADDRESS. It now says "internal" rather than
18336 an English sentence fragment with spaces in the middle. Bugfix on
18337 Tor 0.2.0.19-alpha.
18338 - Fix log messages and comments to avoid saying "GMT" when we mean
18339 "UTC". Fixes bug 6113.
18340 - Compile on win64 using mingw64. Fixes bug 7260; patches from
18342 - Fix a crash when debugging unit tests on Windows: deallocate a
18343 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
18344 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
18347 - The DirServer option is now DirAuthority, for consistency with
18348 current naming patterns. You can still use the old DirServer form.
18350 o Code simplification and refactoring:
18351 - Move the client-side address-map/virtual-address/DNS-cache code
18352 out of connection_edge.c into a new addressmap.c module.
18353 - Remove unused code for parsing v1 directories and "running routers"
18354 documents. Fixes bug 6887.
18357 Changes in version 0.2.3.25 - 2012-11-19
18358 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
18359 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
18360 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
18361 programmer, and friend. Unstinting in his dedication to the cause of
18362 freedom, he inspired and helped many of us as we began our work on
18363 anonymity, and inspires us still. Please honor his memory by writing
18364 software to protect people's freedoms, and by helping others to do so.
18366 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
18367 significantly reduced directory overhead (via microdescriptors),
18368 enormous crypto performance improvements for fast relays on new
18369 enough hardware, a new v3 TLS handshake protocol that can better
18370 resist fingerprinting, support for protocol obfuscation plugins (aka
18371 pluggable transports), better scalability for hidden services, IPv6
18372 support for bridges, performance improvements like allowing clients
18373 to skip the first round-trip on the circuit ("optimistic data") and
18374 refilling token buckets more often, a new "stream isolation" design
18375 to isolate different applications on different circuits, and many
18376 stability, security, and privacy fixes.
18379 - Tor tries to wipe potentially sensitive data after using it, so
18380 that if some subsequent security failure exposes Tor's memory,
18381 the damage will be limited. But we had a bug where the compiler
18382 was eliminating these wipe operations when it decided that the
18383 memory was no longer visible to a (correctly running) program,
18384 hence defeating our attempt at defense in depth. We fix that
18385 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18386 is unlikely to optimize away. Future versions of Tor may use
18387 a less ridiculously heavy approach for this. Fixes bug 7352.
18388 Reported in an article by Andrey Karpov.
18391 - Fix a harmless bug when opting against publishing a relay descriptor
18392 because DisableNetwork is set. Fixes bug 7464; bugfix on
18396 Changes in version 0.2.4.6-alpha - 2012-11-13
18397 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
18398 makes our defense-in-depth memory wiping more reliable, and begins to
18399 count IPv6 addresses in bridge statistics,
18402 - Fix an assertion failure that could occur when closing a connection
18403 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
18405 - Tor tries to wipe potentially sensitive data after using it, so
18406 that if some subsequent security failure exposes Tor's memory,
18407 the damage will be limited. But we had a bug where the compiler
18408 was eliminating these wipe operations when it decided that the
18409 memory was no longer visible to a (correctly running) program,
18410 hence defeating our attempt at defense in depth. We fix that
18411 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
18412 is unlikely to optimize away. Future versions of Tor may use
18413 a less ridiculously heavy approach for this. Fixes bug 7352.
18414 Reported in an article by Andrey Karpov.
18417 - Add GeoIP database for IPv6 addresses. The new config option
18419 - Bridge statistics now count bridge clients connecting over IPv6:
18420 bridge statistics files now list "bridge-ip-versions" and
18421 extra-info documents list "geoip6-db-digest". The control protocol
18422 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
18423 implementation by "shkoo", addressing ticket 5055.
18426 - Warn when we are binding low ports when hibernation is enabled;
18427 previously we had warned when we were _advertising_ low ports with
18428 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
18429 - Fix a harmless bug when opting against publishing a relay descriptor
18430 because DisableNetwork is set. Fixes bug 7464; bugfix on
18432 - Add warning message when a managed proxy dies during configuration.
18433 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
18434 - Fix a linking error when building tor-fw-helper without miniupnp.
18435 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
18436 - Check for closing an or_connection_t without going through correct
18437 channel functions; emit a warning and then call
18438 connection_or_close_for_error() so we don't assert as in bugs 7212
18440 - Compile correctly on compilers without C99 designated initializer
18441 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
18442 - Avoid a possible assert that can occur when channel_send_destroy() is
18443 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
18444 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
18445 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
18446 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
18447 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
18449 o Code simplification and refactoring:
18450 - Start using OpenBSD's implementation of queue.h, so that we don't
18451 need to hand-roll our own pointer and list structures whenever we
18452 need them. (We can't rely on a sys/queue.h, since some operating
18453 systems don't have them, and the ones that do have them don't all
18454 present the same extensions.)
18457 Changes in version 0.2.4.5-alpha - 2012-10-25
18458 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
18459 two important security vulnerabilities that could lead to remotely
18460 triggerable relay crashes, fix a major bug that was preventing clients
18461 from choosing suitable exit nodes, and refactor some of our code.
18463 o Major bugfixes (security, also in 0.2.3.24-rc):
18464 - Fix a group of remotely triggerable assertion failures related to
18465 incorrect link protocol negotiation. Found, diagnosed, and fixed
18466 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18468 - Fix a denial of service attack by which any directory authority
18469 could crash all the others, or by which a single v2 directory
18470 authority could crash everybody downloading v2 directory
18471 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18473 o Major bugfixes (also in 0.2.3.24-rc):
18474 - When parsing exit policy summaries from microdescriptors, we had
18475 previously been ignoring the last character in each one, so that
18476 "accept 80,443,8080" would be treated by clients as indicating
18477 a node that allows access to ports 80, 443, and 808. That would
18478 lead to clients attempting connections that could never work,
18479 and ignoring exit nodes that would support their connections. Now
18480 clients parse these exit policy summaries correctly. Fixes bug 7192;
18481 bugfix on 0.2.3.1-alpha.
18483 o Minor bugfixes (also in 0.2.3.24-rc):
18484 - Clients now consider the ClientRejectInternalAddresses config option
18485 when using a microdescriptor consensus stanza to decide whether
18486 an exit relay would allow exiting to an internal address. Fixes
18487 bug 7190; bugfix on 0.2.3.1-alpha.
18490 - Only disable TLS session ticket support when running as a TLS
18491 server. Now clients will blend better with regular Firefox
18492 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
18494 o Code simplification and refactoring:
18495 - Start using OpenBSD's implementation of queue.h (originally by
18497 - Move the entry node code from circuitbuild.c to its own file.
18498 - Move the circuit build timeout tracking code from circuitbuild.c
18502 Changes in version 0.2.3.24-rc - 2012-10-25
18503 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
18504 could lead to remotely triggerable relay crashes, and fixes
18505 a major bug that was preventing clients from choosing suitable exit
18508 o Major bugfixes (security):
18509 - Fix a group of remotely triggerable assertion failures related to
18510 incorrect link protocol negotiation. Found, diagnosed, and fixed
18511 by "some guy from France". Fix for CVE-2012-2250; bugfix on
18513 - Fix a denial of service attack by which any directory authority
18514 could crash all the others, or by which a single v2 directory
18515 authority could crash everybody downloading v2 directory
18516 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
18519 - When parsing exit policy summaries from microdescriptors, we had
18520 previously been ignoring the last character in each one, so that
18521 "accept 80,443,8080" would be treated by clients as indicating
18522 a node that allows access to ports 80, 443, and 808. That would
18523 lead to clients attempting connections that could never work,
18524 and ignoring exit nodes that would support their connections. Now
18525 clients parse these exit policy summaries correctly. Fixes bug 7192;
18526 bugfix on 0.2.3.1-alpha.
18529 - Clients now consider the ClientRejectInternalAddresses config option
18530 when using a microdescriptor consensus stanza to decide whether
18531 an exit relay would allow exiting to an internal address. Fixes
18532 bug 7190; bugfix on 0.2.3.1-alpha.
18535 Changes in version 0.2.4.4-alpha - 2012-10-20
18536 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
18537 vulnerability introduced by a change in OpenSSL, fixes a remotely
18538 triggerable assert, and adds new channel_t and circuitmux_t abstractions
18539 that will make it easier to test new connection transport and cell
18540 scheduling algorithms.
18542 o New directory authorities (also in 0.2.3.23-rc):
18543 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18544 authority. Closes ticket 5749.
18546 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
18547 - Disable TLS session tickets. OpenSSL's implementation was giving
18548 our TLS session keys the lifetime of our TLS context objects, when
18549 perfect forward secrecy would want us to discard anything that
18550 could decrypt a link connection as soon as the link connection
18551 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18552 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18553 - Discard extraneous renegotiation attempts once the V3 link
18554 protocol has been initiated. Failure to do so left us open to
18555 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18556 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18558 o Internal abstraction features:
18559 - Introduce new channel_t abstraction between circuits and
18560 or_connection_t to allow for implementing alternate OR-to-OR
18561 transports. A channel_t is an abstract object which can either be a
18562 cell-bearing channel, which is responsible for authenticating and
18563 handshaking with the remote OR and transmitting cells to and from
18564 it, or a listening channel, which spawns new cell-bearing channels
18565 at the request of remote ORs. Implements part of ticket 6465.
18566 - Also new is the channel_tls_t subclass of channel_t, adapting it
18567 to the existing or_connection_t code. The V2/V3 protocol handshaking
18568 code which formerly resided in command.c has been moved below the
18569 channel_t abstraction layer and may be found in channeltls.c now.
18570 Implements the rest of ticket 6465.
18571 - Introduce new circuitmux_t storing the queue of circuits for
18572 a channel; this encapsulates and abstracts the queue logic and
18573 circuit selection policy, and allows the latter to be overridden
18574 easily by switching out a policy object. The existing EWMA behavior
18575 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
18577 o Required libraries:
18578 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
18579 strongly recommended.
18582 - Warn users who run hidden services on a Tor client with
18583 UseEntryGuards disabled that their hidden services will be
18584 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
18585 attack which motivated Tor to support entry guards in the first
18586 place). Resolves ticket 6889.
18587 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
18588 dhill. Resolves ticket 6982.
18589 - Option OutboundBindAddress can be specified multiple times and
18590 accepts IPv6 addresses. Resolves ticket 6876.
18592 o Minor bugfixes (also in 0.2.3.23-rc):
18593 - Don't serve or accept v2 hidden service descriptors over a
18594 relay's DirPort. It's never correct to do so, and disabling it
18595 might make it more annoying to exploit any bugs that turn up in the
18596 descriptor-parsing code. Fixes bug 7149.
18597 - Fix two cases in src/or/transports.c where we were calling
18598 fmt_addr() twice in a parameter list. Bug found by David
18599 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18600 - Fix memory leaks whenever we logged any message about the "path
18601 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18602 - When relays refuse a "create" cell because their queue of pending
18603 create cells is too big (typically because their cpu can't keep up
18604 with the arrival rate), send back reason "resource limit" rather
18605 than reason "internal", so network measurement scripts can get a
18606 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
18609 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
18610 - Free some more still-in-use memory at exit, to make hunting for
18611 memory leaks easier. Resolves bug 7029.
18612 - When a Tor client gets a "truncated" relay cell, the first byte of
18613 its payload specifies why the circuit was truncated. We were
18614 ignoring this 'reason' byte when tearing down the circuit, resulting
18615 in the controller not being told why the circuit closed. Now we
18616 pass the reason from the truncated cell to the controller. Bugfix
18617 on 0.1.2.3-alpha; fixes bug 7039.
18618 - Downgrade "Failed to hand off onionskin" messages to "debug"
18619 severity, since they're typically redundant with the "Your computer
18620 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
18621 - Make clients running with IPv6 bridges connect over IPv6 again,
18622 even without setting new config options ClientUseIPv6 and
18623 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
18624 - Use square brackets around IPv6 addresses in numerous places
18625 that needed them, including log messages, HTTPS CONNECT proxy
18626 requests, TransportProxy statefile entries, and pluggable transport
18627 extra-info lines. Fixes bug 7011; patch by David Fifield.
18629 o Code refactoring and cleanup:
18630 - Source files taken from other packages now reside in src/ext;
18631 previously they were scattered around the rest of Tor.
18632 - Avoid use of reserved identifiers in our C code. The C standard
18633 doesn't like us declaring anything that starts with an
18634 underscore, so let's knock it off before we get in trouble. Fix
18635 for bug 1031; bugfix on the first Tor commit.
18638 Changes in version 0.2.3.23-rc - 2012-10-20
18639 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
18640 vulnerability introduced by a change in OpenSSL, and fixes a variety
18641 of smaller bugs in preparation for the release.
18643 o New directory authorities:
18644 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
18645 authority. Closes ticket 5749.
18647 o Major bugfixes (security/privacy):
18648 - Disable TLS session tickets. OpenSSL's implementation was giving
18649 our TLS session keys the lifetime of our TLS context objects, when
18650 perfect forward secrecy would want us to discard anything that
18651 could decrypt a link connection as soon as the link connection
18652 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
18653 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
18654 - Discard extraneous renegotiation attempts once the V3 link
18655 protocol has been initiated. Failure to do so left us open to
18656 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
18657 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
18660 - Fix a possible crash bug when checking for deactivated circuits
18661 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18662 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18664 o Minor bugfixes (on 0.2.3.x):
18665 - Fix two cases in src/or/transports.c where we were calling
18666 fmt_addr() twice in a parameter list. Bug found by David
18667 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
18668 - Convert an assert in the pathbias code to a log message. The assert
18669 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18670 bugfix on 0.2.3.17-beta.
18671 - Fix memory leaks whenever we logged any message about the "path
18672 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
18674 o Minor bugfixes (on 0.2.2.x and earlier):
18675 - Don't serve or accept v2 hidden service descriptors over a relay's
18676 DirPort. It's never correct to do so, and disabling it might
18677 make it more annoying to exploit any bugs that turn up in the
18678 descriptor-parsing code. Fixes bug 7149.
18679 - When relays refuse a "create" cell because their queue of pending
18680 create cells is too big (typically because their cpu can't keep up
18681 with the arrival rate), send back reason "resource limit" rather
18682 than reason "internal", so network measurement scripts can get a
18683 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
18684 - Correct file sizes when reading binary files on Cygwin, to avoid
18685 a bug where Tor would fail to read its state file. Fixes bug 6844;
18686 bugfix on 0.1.2.7-alpha.
18687 - Avoid undefined behavior when parsing the list of supported
18688 rendezvous/introduction protocols in a hidden service descriptor.
18689 Previously, Tor would have confused (as-yet-unused) protocol version
18690 numbers greater than 32 with lower ones on many platforms. Fixes
18691 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18693 o Documentation fixes:
18694 - Clarify that hidden services are TCP only. Fixes bug 6024.
18697 Changes in version 0.2.4.3-alpha - 2012-09-22
18698 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
18699 assertion, resumes letting relays test reachability of their DirPort,
18700 and cleans up a bunch of smaller bugs.
18703 - Fix an assertion failure in tor_timegm() that could be triggered
18704 by a badly formatted directory object. Bug found by fuzzing with
18705 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18708 - Fix a possible crash bug when checking for deactivated circuits
18709 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
18710 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
18711 - Allow routers to detect that their own DirPorts are running. When
18712 we removed support for versions_supports_begindir, we also
18713 accidentally removed the mechanism we used to self-test our
18714 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
18715 bugfix on 0.2.4.2-alpha.
18717 o Security features:
18718 - Switch to a completely time-invariant approach for picking nodes
18719 weighted by bandwidth. Our old approach would run through the
18720 part of the loop after it had made its choice slightly slower
18721 than it ran through the part of the loop before it had made its
18722 choice. Addresses ticket 6538.
18723 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
18724 by tor2web clients allows hidden services to identify tor2web
18725 clients through their repeated selection of the same rendezvous
18726 and introduction point circuit endpoints (their guards). Resolves
18730 - Enable Tor to read configuration, state, and key information from
18731 a FIFO. Previously Tor would only read from files with a positive
18732 stat.st_size. Code from meejah; fixes bug 6044.
18735 - Correct file sizes when reading binary files on Cygwin, to avoid
18736 a bug where Tor would fail to read its state file. Fixes bug 6844;
18737 bugfix on 0.1.2.7-alpha.
18738 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
18739 bugfix on 0.2.0.3-alpha.
18740 - When complaining about a client port on a public address, log
18741 which address we're complaining about. Fixes bug 4020; bugfix on
18742 0.2.3.3-alpha. Patch by Tom Fitzhenry.
18743 - Convert an assert in the pathbias code to a log message. The assert
18744 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
18745 bugfix on 0.2.3.17-beta.
18746 - Our new buildsystem was overzealous about rebuilding manpages: it
18747 would rebuild them all whenever any one of them changed. Now our
18748 dependency checking should be correct. Fixes bug 6843; bugfix on
18750 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
18751 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
18752 - Correct log printout about which address family is preferred
18753 when connecting to a bridge with both an IPv4 and IPv6 OR port.
18754 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
18756 o Minor bugfixes (code cleanliness):
18757 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
18758 with large values. This situation was untriggered, but nevertheless
18759 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
18760 - Reject consensus votes with more than 64 known-flags. We aren't even
18761 close to that limit yet, and our code doesn't handle it correctly.
18762 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
18763 - Avoid undefined behavior when parsing the list of supported
18764 rendezvous/introduction protocols in a hidden service descriptor.
18765 Previously, Tor would have confused (as-yet-unused) protocol version
18766 numbers greater than 32 with lower ones on many platforms. Fixes
18767 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
18768 - Fix handling of rendezvous client authorization types over 8.
18769 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
18770 - Fix building with older versions of GCC (2.95, for one) that don't
18771 like preprocessor directives inside macro arguments. Found by
18772 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
18773 - Switch weighted node selection rule from using a list of doubles
18774 to using a list of int64_t. This change should make the process
18775 slightly easier to debug and maintain. Needed to finish ticket 6538.
18777 o Code simplification and refactoring:
18778 - Move the generic "config" code into a new file, and have "config.c"
18779 hold only torrc- and state-related code. Resolves ticket 6823.
18780 - Move the core of our "choose a weighted element at random" logic
18781 into its own function, and give it unit tests. Now the logic is
18782 testable, and a little less fragile too.
18783 - Removed the testing_since field of node_t, which hasn't been used
18784 for anything since 0.2.0.9-alpha.
18786 o Documentation fixes:
18787 - Clarify that hidden services are TCP only. Fixes bug 6024.
18788 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
18792 Changes in version 0.2.3.22-rc - 2012-09-11
18793 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
18797 - Fix an assertion failure in tor_timegm() that could be triggered
18798 by a badly formatted directory object. Bug found by fuzzing with
18799 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18802 - Avoid segfault when starting up having run with an extremely old
18803 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18807 Changes in version 0.2.2.39 - 2012-09-11
18808 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
18812 - Fix an assertion failure in tor_timegm() that could be triggered
18813 by a badly formatted directory object. Bug found by fuzzing with
18814 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
18815 - Do not crash when comparing an address with port value 0 to an
18816 address policy. This bug could have been used to cause a remote
18817 assertion failure by or against directory authorities, or to
18818 allow some applications to crash clients. Fixes bug 6690; bugfix
18822 Changes in version 0.2.4.2-alpha - 2012-09-10
18823 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
18824 raises the default rate limiting even more, and makes the bootstrapping
18825 log messages less noisy.
18828 - Automatically forward the TCP ports of pluggable transport
18829 proxies using tor-fw-helper if PortForwarding is enabled. Implements
18833 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
18834 to 1GB/1GB. The previous defaults were intended to be "basically
18835 infinite", but it turns out they're now limiting our 100mbit+
18836 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
18837 last time we raised it).
18840 - Detect when we're running with a version of OpenSSL other than the
18841 one we compiled with. This has occasionally given people hard-to-
18843 - Log fewer lines at level "notice" about our OpenSSL and Libevent
18844 versions and capabilities when everything is going right. Resolves
18845 part of ticket 6736.
18846 - Directory authorities no long accept descriptors for any version of
18847 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
18848 These versions are insecure, unsupported, or both. Implements
18852 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
18853 to start with a triple-underscore so the controller won't touch it.
18854 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
18855 - Avoid segfault when starting up having run with an extremely old
18856 version of Tor and parsing its state file. Fixes bug 6801; bugfix
18858 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
18859 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
18860 - Don't follow the NULL pointer if microdescriptor generation fails.
18861 (This does not appear to be triggerable, but it's best to be safe.)
18862 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
18863 - Fix mis-declared dependencies on src/common/crypto.c and
18864 src/or/tor_main.c that could break out-of-tree builds under some
18865 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
18866 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
18867 6778; bugfix on 0.2.4.1-alpha.
18868 - Fix a harmless (in this case) build warning for implicitly
18869 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
18871 o Removed features:
18872 - Now that all versions before 0.2.2.x are disallowed, we no longer
18873 need to work around their missing features. Thus we can remove a
18874 bunch of compatibility code.
18876 o Code refactoring:
18877 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
18878 TCP ports to forward. In the past it only accepted two ports:
18879 the ORPort and the DirPort.
18882 Changes in version 0.2.4.1-alpha - 2012-09-05
18883 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
18884 bridgedb; lets relays use IPv6 addresses and directory authorities
18885 advertise them; and switches to a cleaner build interface.
18887 This is the first alpha release in a new series, so expect there to
18888 be bugs. Users who would rather test out a more stable branch should
18889 stay with 0.2.3.x for now.
18891 o Major features (bridges):
18892 - Bridges now report the pluggable transports they support to the
18893 bridge authority, so it can pass the supported transports on to
18894 bridgedb and/or eventually do reachability testing. Implements
18897 o Major features (IPv6):
18898 - Bridge authorities now accept IPv6 bridge addresses and include
18899 them in network status documents. Implements ticket 5534.
18900 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
18901 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
18902 to happen. Implements ticket 5535.
18903 - All kind of relays, not just bridges, can now advertise an IPv6
18904 OR port. Implements ticket 6362.
18905 - Directory authorities vote on IPv6 OR ports using the new consensus
18906 method 14. Implements ticket 6363.
18908 o Major features (build):
18909 - Switch to a nonrecursive Makefile structure. Now instead of each
18910 Makefile.am invoking other Makefile.am's, there is a master
18911 Makefile.am that includes the others. This change makes our build
18912 process slightly more maintainable, and improves parallelism for
18913 building with make -j. Original patch by Stewart Smith; various
18914 fixes by Jim Meyering.
18915 - Where available, we now use automake's "silent" make rules by
18916 default, so that warnings are easier to spot. You can get the old
18917 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
18919 o Minor features (code security and spec conformance):
18920 - Clear keys and key-derived material left on the stack in
18921 rendservice.c and rendclient.c. Check return value of
18922 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
18923 These fixes should make us more forward-secure against cold-boot
18924 attacks and the like. Fixes bug 2385.
18925 - Reject EXTEND cells sent to nonexistent streams. According to the
18926 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
18927 we were only checking for stream IDs that were currently in use.
18928 Found while hunting for more instances of bug 6271. Bugfix on
18929 0.0.2pre8, which introduced incremental circuit construction.
18931 o Minor features (streamlining);
18932 - No longer include the "opt" prefix when generating routerinfos
18933 or v2 directories: it has been needless since Tor 0.1.2. Closes
18935 - Remove some now-needless code that tried to aggressively flush
18936 OR connections as data was added to them. Since 0.2.0.1-alpha, our
18937 cell queue logic has saved us from the failure mode that this code
18938 was supposed to prevent. Removing this code will limit the number
18939 of baroque control flow paths through Tor's network logic. Reported
18940 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
18942 o Minor features (controller):
18943 - Add a "GETINFO signal/names" control port command. Implements
18945 - Provide default values for all options via "GETINFO config/defaults".
18946 Implements ticket 4971.
18948 o Minor features (IPv6):
18949 - New config option "AuthDirHasIPv6Connectivity 1" that directory
18950 authorities should set if they have IPv6 connectivity and want to
18951 do reachability tests for IPv6 relays. Implements feature 5974.
18952 - A relay with an IPv6 OR port now sends that address in NETINFO
18953 cells (in addition to its other address). Implements ticket 6364.
18955 o Minor features (log messages):
18956 - Omit the first heartbeat log message, because it never has anything
18957 useful to say, and it clutters up the bootstrapping messages.
18958 Resolves ticket 6758.
18959 - Don't log about reloading the microdescriptor cache at startup. Our
18960 bootstrap warnings are supposed to tell the user when there's a
18961 problem, and our bootstrap notices say when there isn't. Resolves
18962 ticket 6759; bugfix on 0.2.2.6-alpha.
18963 - Don't log "I learned some more directory information" when we're
18964 reading cached directory information. Reserve it for when new
18965 directory information arrives in response to a fetch. Resolves
18967 - Prevent rounding error in path bias counts when scaling
18968 them down, and use the correct scale factor default. Also demote
18969 some path bias related log messages down a level and make others
18970 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
18971 - We no longer warn so much when generating manpages from their
18974 o Code simplifications and refactoring:
18975 - Enhance our internal sscanf replacement so that we can eliminate
18976 the last remaining uses of the system sscanf. (Though those uses
18977 of sscanf were safe, sscanf itself is generally error prone, so
18978 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
18980 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
18981 - Move last_reachable and testing_since from routerinfo_t to node_t.
18982 Implements ticket 5529.
18983 - Add replaycache_t structure, functions and unit tests, then refactor
18984 rend_service_introduce() to be more clear to read, improve, debug,
18985 and test. Resolves bug 6177.
18986 - Finally remove support for malloc_good_size and malloc_usable_size.
18987 We had hoped that these functions would let us eke a little more
18988 memory out of our malloc implementation. Unfortunately, the only
18989 implementations that provided these functions are also ones that
18990 are already efficient about not overallocation: they never got us
18991 more than 7 or so bytes per allocation. Removing them saves us a
18992 little code complexity and a nontrivial amount of build complexity.
18994 o New requirements:
18995 - Tor maintainers now require Automake version 1.9 or later to build
18996 Tor from the Git repository. (Automake is not required when building
18997 from a source distribution.)
19000 Changes in version 0.2.3.21-rc - 2012-09-05
19001 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
19002 series. It fixes a trio of potential security bugs, fixes a bug where
19003 we were leaving some of the fast relays out of the microdescriptor
19004 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
19005 and cleans up other smaller issues.
19007 o Major bugfixes (security):
19008 - Tear down the circuit if we get an unexpected SENDME cell. Clients
19009 could use this trick to make their circuits receive cells faster
19010 than our flow control would have allowed, or to gum up the network,
19011 or possibly to do targeted memory denial-of-service attacks on
19012 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
19013 from July 2002, before the release of Tor 0.0.0. We had committed
19014 this patch previously, but we had to revert it because of bug 6271.
19015 Now that 6271 is fixed, this patch appears to work.
19016 - Reject any attempt to extend to an internal address. Without
19017 this fix, a router could be used to probe addresses on an internal
19018 network to see whether they were accepting connections. Fixes bug
19019 6710; bugfix on 0.0.8pre1.
19020 - Do not crash when comparing an address with port value 0 to an
19021 address policy. This bug could have been used to cause a remote
19022 assertion failure by or against directory authorities, or to
19023 allow some applications to crash clients. Fixes bug 6690; bugfix
19027 - Remove the upper bound on microdescriptor length. We were hitting
19028 the limit for routers with complex exit policies or family
19029 declarations, causing clients to not use them. Fixes the first
19030 piece of bug 6404; fix on 0.2.2.6-alpha.
19031 - Detect "ORPort 0" as meaning, uniformly, that we're not running
19032 as a relay. Previously, some of our code would treat the presence
19033 of any ORPort line as meaning that we should act like a relay,
19034 even though our new listener code would correctly not open any
19035 ORPorts for ORPort 0. Similar bugs in other Port options are also
19036 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
19039 - Avoid a pair of double-free and use-after-mark bugs that can
19040 occur with certain timings in canceled and re-received DNS
19041 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
19042 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
19043 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
19044 - Allow one-hop directory fetching circuits the full "circuit build
19045 timeout" period, rather than just half of it, before failing them
19046 and marking the relay down. This fix should help reduce cases where
19047 clients declare relays (or worse, bridges) unreachable because
19048 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
19049 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
19051 - Authorities no longer include any router in their microdescriptor
19052 consensuses for which they couldn't generate or agree on a
19053 microdescriptor. Fixes the second piece of bug 6404; fix on
19055 - Detect and reject attempts to specify both "FooPort" and
19056 "FooPort 0" in the same configuration domain. (It's still okay
19057 to have a FooPort in your configuration file, and use "FooPort 0"
19058 on the command line to disable it.) Fixes the second half of bug
19059 6507; bugfix on 0.2.3.3-alpha.
19060 - Make wildcarded addresses (that is, ones beginning with "*.") work
19061 when provided via the controller's MapAddress command. Previously,
19062 they were accepted, but we never actually noticed that they were
19063 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
19064 - Avoid crashing on a malformed state file where EntryGuardPathBias
19065 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
19066 - Add a (probably redundant) memory clear between iterations of
19067 the router status voting loop, to prevent future coding errors
19068 where data might leak between iterations of the loop. Resolves
19071 o Minor bugfixes (log messages):
19072 - Downgrade "set buildtimeout to low value" messages to "info"
19073 severity; they were never an actual problem, there was never
19074 anything reasonable to do about them, and they tended to spam logs
19075 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
19076 - Downgrade path-bias warning messages to "info". We'll try to get
19077 them working better in 0.2.4. Add internal circuit construction
19078 state to protect against the noisy warn message "Unexpectedly high
19079 circuit_successes". Also add some additional rate-limited notice
19080 messages to help determine the root cause of the warn. Fixes bug
19081 6475. Bugfix against 0.2.3.17-beta.
19082 - Move log message when unable to find a microdesc in a routerstatus
19083 entry to parse time. Previously we'd spam this warning every time
19084 we tried to figure out which microdescriptors to download. Fixes
19085 the third piece of bug 6404; fix on 0.2.3.18-rc.
19088 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
19089 change when the authority is deciding whether to accept a newly
19090 uploaded descriptor. Implements ticket 6423.
19091 - Add missing documentation for consensus and microdesc files.
19092 Resolves ticket 6732.
19095 Changes in version 0.2.2.38 - 2012-08-12
19096 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
19097 attack that could in theory leak path information.
19100 - Avoid an uninitialized memory read when reading a vote or consensus
19101 document that has an unrecognized flavor name. This read could
19102 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19103 - Try to leak less information about what relays a client is
19104 choosing to a side-channel attacker. Previously, a Tor client would
19105 stop iterating through the list of available relays as soon as it
19106 had chosen one, thus finishing a little earlier when it picked
19107 a router earlier in the list. If an attacker can recover this
19108 timing information (nontrivial but not proven to be impossible),
19109 they could learn some coarse-grained information about which relays
19110 a client was picking (middle nodes in particular are likelier to
19111 be affected than exits). The timing attack might be mitigated by
19112 other factors (see bug 6537 for some discussion), but it's best
19113 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
19116 Changes in version 0.2.3.20-rc - 2012-08-05
19117 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
19118 series. It fixes a pair of code security bugs and a potential anonymity
19119 issue, updates our RPM spec files, and cleans up other smaller issues.
19122 - Avoid read-from-freed-memory and double-free bugs that could occur
19123 when a DNS request fails while launching it. Fixes bug 6480;
19124 bugfix on 0.2.0.1-alpha.
19125 - Avoid an uninitialized memory read when reading a vote or consensus
19126 document that has an unrecognized flavor name. This read could
19127 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
19128 - Try to leak less information about what relays a client is
19129 choosing to a side-channel attacker. Previously, a Tor client would
19130 stop iterating through the list of available relays as soon as it
19131 had chosen one, thus finishing a little earlier when it picked
19132 a router earlier in the list. If an attacker can recover this
19133 timing information (nontrivial but not proven to be impossible),
19134 they could learn some coarse-grained information about which relays
19135 a client was picking (middle nodes in particular are likelier to
19136 be affected than exits). The timing attack might be mitigated by
19137 other factors (see bug 6537 for some discussion), but it's best
19138 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
19141 - Try to make the warning when giving an obsolete SOCKSListenAddress
19142 a little more useful.
19143 - Terminate active server managed proxies if Tor stops being a
19144 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
19145 - Provide a better error message about possible OSX Asciidoc failure
19146 reasons. Fixes bug 6436.
19147 - Warn when Tor is configured to use accounting in a way that can
19148 link a hidden service to some other hidden service or public
19149 address. Resolves ticket 6490.
19152 - Check return value of fputs() when writing authority certificate
19153 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
19154 - Ignore ServerTransportPlugin lines when Tor is not configured as
19155 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
19156 - When disabling guards for having too high a proportion of failed
19157 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
19161 - Update our default RPM spec files to work with mock and rpmbuild
19162 on RHEL/Fedora. They have an updated set of dependencies and
19163 conflicts, a fix for an ancient typo when creating the "_tor"
19164 user, and better instructions. Thanks to Ondrej Mikle for the
19165 patch series. Fixes bug 6043.
19168 - Make it possible to set the TestingTorNetwork configuration
19169 option using AlternateDirAuthority and AlternateBridgeAuthority
19170 as an alternative to setting DirServer. Addresses ticket 6377.
19173 - Clarify the documentation for the Alternate*Authority options.
19175 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
19177 o Code simplification and refactoring:
19178 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
19179 10 lines. Also, don't nest them. Doing so in the past has
19180 led to hard-to-debug code. The new style is to use the
19181 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
19184 Changes in version 0.2.3.19-rc - 2012-07-06
19185 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
19186 series. It fixes the compile on Windows, reverts to a GeoIP database
19187 that isn't as broken, and fixes a flow control bug that has been around
19188 since the beginning of Tor.
19191 - Fix a bug handling SENDME cells on nonexistent streams that could
19192 result in bizarre window values. Report and patch contributed
19193 pseudonymously. Fixes part of bug 6271. This bug was introduced
19194 before the first Tor release, in svn commit r152.
19195 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
19196 June 2012 database, Maxmind marked many Tor relays as country "A1",
19197 which will cause risky behavior for clients that set EntryNodes
19198 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
19199 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
19200 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
19203 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
19204 bugfix on 0.2.1.10-alpha.
19207 Changes in version 0.2.3.18-rc - 2012-06-28
19208 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
19209 series. It fixes a few smaller bugs, but generally appears stable.
19210 Please test it and let us know whether it is!
19213 - Allow wildcarded mapaddress targets to be specified on the
19214 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
19215 - Make our linker option detection code more robust against linkers
19216 such as on FreeBSD 8, where a bad combination of options completes
19217 successfully but makes an unrunnable binary. Fixes bug 6173;
19218 bugfix on 0.2.3.17-beta.
19220 o Minor bugfixes (on 0.2.2.x and earlier):
19221 - Avoid a false positive in the util/threads unit test by increasing
19222 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
19223 - Replace "Sending publish request" log messages with "Launching
19224 upload", so that they no longer confusingly imply that we're
19225 sending something to a directory we might not even be connected
19226 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
19227 - Make sure to set *socket_error in all error cases in
19228 connection_connect(), so it can't produce a warning about
19229 errno being zero from errno_to_orconn_end_reason(). Bugfix on
19230 0.2.1.1-alpha; resolves ticket 6028.
19231 - Downgrade "Got a certificate, but we already have it" log messages
19232 from warning to info, except when we're a dirauth. Fixes bug 5238;
19233 bugfix on 0.2.1.7-alpha.
19234 - When checking for requested signatures on the latest consensus
19235 before serving it to a client, make sure to check the right
19236 consensus flavor. Bugfix on 0.2.2.6-alpha.
19237 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
19238 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
19240 o Minor bugfixes (on 0.2.3.x):
19241 - Make format_helper_exit_status() avoid unnecessary space padding
19242 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
19244 - Downgrade a message about cleaning the microdescriptor cache to
19245 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
19246 - Log a BUG message at severity INFO if we have a networkstatus with
19247 a missing entry for some microdescriptor. Continues on a patch
19249 - Improve the log message when a managed proxy fails to launch. Fixes
19250 bug 5099; bugfix on 0.2.3.6-alpha.
19251 - Don't do DNS lookups when parsing corrupted managed proxy protocol
19252 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
19253 - When formatting wildcarded address mappings for the controller,
19254 be sure to include "*." as appropriate. Partially fixes bug 6244;
19255 bugfix on 0.2.3.9-alpha.
19256 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
19257 Bugfix on 0.2.3.13-alpha.
19258 - Stop logging messages about running with circuit timeout learning
19259 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
19260 - Disable a spurious warning about reading on a marked and flushing
19261 connection. We shouldn't be doing that, but apparently we
19262 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
19263 - Fix a bug that stopped AllowDotExit from working on addresses
19264 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
19267 o Code simplification, refactoring, unit tests:
19268 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
19269 Libevent's notion of cached time when possible.
19270 - Remove duplicate code for invoking getrlimit() from control.c.
19271 - Add a unit test for the environment_variable_names_equal function.
19274 - Document the --defaults-torrc option, and the new (in 0.2.3)
19275 semantics for overriding, extending, and clearing lists of
19276 options. Closes bug 4748.
19279 Changes in version 0.2.3.17-beta - 2012-06-15
19280 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
19281 gets our TLS handshake back on track for being able to blend in with
19282 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
19283 with Vidalia, and otherwise continues to get us closer to a release
19287 - Enable gcc and ld hardening by default. Resolves ticket 5210.
19288 - Update TLS cipher list to match Firefox 8 and later. Resolves
19290 - Implement the client side of proposal 198: remove support for
19291 clients falsely claiming to support standard ciphersuites that
19292 they can actually provide. As of modern OpenSSL versions, it's not
19293 necessary to fake any standard ciphersuite, and doing so prevents
19294 us from using better ciphersuites in the future, since servers
19295 can't know whether an advertised ciphersuite is really supported or
19296 not. Some hosts -- notably, ones with very old versions of OpenSSL
19297 or where OpenSSL has been built with ECC disabled -- will stand
19298 out because of this change; TBB users should not be affected.
19301 - Change the default value for DynamicDHGroups (introduced in
19302 0.2.3.9-alpha) to 0. This feature can make Tor relays less
19303 identifiable by their use of the mod_ssl DH group, but at
19304 the cost of some usability (#4721) and bridge tracing (#6087)
19305 regressions. Resolves ticket 5598.
19306 - Send a CRLF at the end of each STATUS_* control protocol event. This
19307 bug tickled a bug in Vidalia which would make it freeze. Fixes
19308 bug 6094; bugfix on 0.2.3.16-alpha.
19311 - Disable writing on marked-for-close connections when they are
19312 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
19313 bug 5263; bugfix on 0.0.2pre13, where we first added a special
19314 case for flushing marked connections.
19315 - Detect SSL handshake even when the initial attempt to write the
19316 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
19317 - Change the AllowDotExit rules so they should actually work.
19318 We now enforce AllowDotExit only immediately after receiving an
19319 address via SOCKS or DNSPort: other sources are free to provide
19320 .exit addresses after the resolution occurs. Fixes bug 3940;
19321 bugfix on 0.2.2.1-alpha.
19322 - Fix a (harmless) integer overflow in cell statistics reported by
19323 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
19324 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
19325 right places and never depends on the consensus parameters or
19326 computes adaptive timeouts when it is disabled. Fixes bug 5049;
19327 bugfix on 0.2.2.14-alpha.
19328 - When building Tor on Windows with -DUNICODE (not default), ensure
19329 that error messages, filenames, and DNS server names are always
19330 NUL-terminated when we convert them to a single-byte encoding.
19331 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
19332 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
19333 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
19334 - Fix an edge case where TestingTorNetwork is set but the authorities
19335 and relays all have an uptime of zero, where the private Tor network
19336 could briefly lack support for hidden services. Fixes bug 3886;
19337 bugfix on 0.2.2.18-alpha.
19338 - Correct the manpage's descriptions for the default values of
19339 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
19341 - Fix the documentation for the --hush and --quiet command line
19342 options, which changed their behavior back in 0.2.3.3-alpha.
19343 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
19347 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
19348 more information to it, so that we can track it down in case it
19349 returns again. Mitigates bug 5235.
19350 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
19351 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
19352 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
19353 - Warn the user when HTTPProxy, but no other proxy type, is
19354 configured. This can cause surprising behavior: it doesn't send
19355 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
19356 directory traffic only. Resolves ticket 4663.
19357 - Issue a notice if a guard completes less than 40% of your circuits.
19358 Threshold is configurable by torrc option PathBiasNoticeRate and
19359 consensus parameter pb_noticepct. There is additional, off-by-
19360 default code to disable guards which fail too many circuits.
19361 Addresses ticket 5458.
19362 - Update to the June 6 2012 Maxmind GeoLite Country database.
19364 o Code simplifications and refactoring:
19365 - Remove validate_pluggable_transports_config(): its warning
19366 message is now handled by connection_or_connect().
19369 Changes in version 0.2.2.37 - 2012-06-06
19370 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
19371 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19375 - Work around a bug in OpenSSL that broke renegotiation with TLS
19376 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19377 the v2 Tor connection protocol when both sides were using OpenSSL
19378 1.0.1 would fail. Resolves ticket 6033.
19379 - When waiting for a client to renegotiate, don't allow it to add
19380 any bytes to the input buffer. This fixes a potential DoS issue.
19381 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19382 - Fix an edge case where if we fetch or publish a hidden service
19383 descriptor, we might build a 4-hop circuit and then use that circuit
19384 for exiting afterwards -- even if the new last hop doesn't obey our
19385 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19388 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19389 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19392 - Tell GCC and Clang to check for any errors in format strings passed
19393 to the tor_v*(print|scan)f functions.
19396 Changes in version 0.2.3.16-alpha - 2012-06-05
19397 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
19398 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
19399 currently). It also fixes a variety of smaller bugs and other cleanups
19400 that get us closer to a release candidate.
19402 o Major bugfixes (general):
19403 - Work around a bug in OpenSSL that broke renegotiation with TLS
19404 1.1 and TLS 1.2. Without this workaround, all attempts to speak
19405 the v2 Tor connection protocol when both sides were using OpenSSL
19406 1.0.1 would fail. Resolves ticket 6033.
19407 - When waiting for a client to renegotiate, don't allow it to add
19408 any bytes to the input buffer. This fixes a potential DoS issue.
19409 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
19410 - Pass correct OR address to managed proxies (like obfsproxy),
19411 even when ORListenAddress is used. Fixes bug 4865; bugfix on
19413 - The advertised platform of a router now includes only its operating
19414 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
19415 service pack level (for Windows) or its CPU architecture (for Unix).
19416 We also no longer include the "git-XYZ" tag in the version. Resolves
19419 o Major bugfixes (clients):
19420 - If we are unable to find any exit that supports our predicted ports,
19421 stop calling them predicted, so that we don't loop and build
19422 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
19423 which introduced predicted ports.
19424 - Fix an edge case where if we fetch or publish a hidden service
19425 descriptor, we might build a 4-hop circuit and then use that circuit
19426 for exiting afterwards -- even if the new last hop doesn't obey our
19427 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
19428 - Check at each new consensus whether our entry guards were picked
19429 long enough ago that we should rotate them. Previously, we only
19430 did this check at startup, which could lead to us holding a guard
19431 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
19432 - When fetching a bridge descriptor from a bridge authority,
19433 always do so anonymously, whether we have been able to open
19434 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
19435 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
19436 but we'll need to wait for bug 6010 before it's actually usable.
19438 o Major bugfixes (directory authorities):
19439 - When computing weight parameters, behave more robustly in the
19440 presence of a bad bwweightscale value. Previously, the authorities
19441 would crash if they agreed on a sufficiently broken weight_scale
19442 value: now, they use a reasonable default and carry on. Partial
19443 fix for 5786; bugfix on 0.2.2.17-alpha.
19444 - Check more thoroughly to prevent a rogue authority from
19445 double-voting on any consensus directory parameter. Previously,
19446 authorities would crash in this case if the total number of
19447 votes for any parameter exceeded the number of active voters,
19448 but would let it pass otherwise. Partial fix for bug 5786; bugfix
19452 - Rate-limit log messages when asked to connect anonymously to
19453 a private address. When these hit, they tended to hit fast and
19454 often. Also, don't bother trying to connect to addresses that we
19455 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
19456 reply makes us think we have been lied to, even when the address the
19457 client tried to connect to was "localhost." Resolves ticket 2822.
19458 - Allow packagers to insert an extra string in server descriptor
19459 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
19460 Resolves the rest of ticket 2988.
19461 - Raise the threshold of server descriptors needed (75%) and exit
19462 server descriptors needed (50%) before we will declare ourselves
19463 bootstrapped. This will make clients start building circuits a
19464 little later, but makes the initially constructed circuits less
19465 skewed and less in conflict with further directory fetches. Fixes
19467 - Close any connection that sends unrecognized junk before the
19468 handshake. Solves an issue noted in bug 4369.
19469 - Improve log messages about managed transports. Resolves ticket 5070.
19470 - Tag a bridge's descriptor as "never to be sent unencrypted".
19471 This shouldn't matter, since bridges don't open non-anonymous
19472 connections to the bridge authority and don't allow unencrypted
19473 directory connections from clients, but we might as well make
19474 sure. Closes bug 5139.
19475 - Expose our view of whether we have gone dormant to the controller,
19476 via a new "GETINFO dormant" value. Torbutton and other controllers
19477 can use this to avoid doing periodic requests through Tor while
19478 it's dormant (bug 4718). Fixes bug 5954.
19479 - Tell GCC and Clang to check for any errors in format strings passed
19480 to the tor_v*(print|scan)f functions.
19481 - Update to the May 1 2012 Maxmind GeoLite Country database.
19483 o Minor bugfixes (already included in 0.2.2.36):
19484 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19485 Fixes bug 5346; bugfix on 0.0.8pre3.
19486 - Correct parsing of certain date types in parse_http_time().
19487 Without this patch, If-Modified-Since would behave
19488 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19489 Esteban Manchado Velázques.
19490 - Make our number-parsing functions always treat too-large values
19491 as an error, even when those values exceed the width of the
19492 underlying type. Previously, if the caller provided these
19493 functions with minima or maxima set to the extreme values of the
19494 underlying integer type, these functions would return those
19495 values on overflow rather than treating overflow as an error.
19496 Fixes part of bug 5786; bugfix on 0.0.9.
19497 - If we hit the error case where routerlist_insert() replaces an
19498 existing (old) server descriptor, make sure to remove that
19499 server descriptor from the old_routers list. Fix related to bug
19500 1776. Bugfix on 0.2.2.18-alpha.
19501 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19502 circuits. Fixes issue 5259.
19504 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
19505 - Prevent a null-pointer dereference when receiving a data cell
19506 for a nonexistent stream when the circuit in question has an
19507 empty deliver window. We don't believe this is triggerable,
19508 since we don't currently allow deliver windows to become empty,
19509 but the logic is tricky enough that it's better to make the code
19510 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
19511 - Fix a memory leak when trying to launch a DNS request when the
19512 network is disabled or the nameservers are unconfigurable. Fixes
19513 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
19514 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
19515 - Don't hold a Windows file handle open for every file mapping;
19516 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
19518 - Avoid O(n^2) performance characteristics when parsing a large
19519 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
19520 - Format more doubles with %f, not %lf. Patch from grarpamp to make
19521 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
19523 - Make our replacement implementation of strtok_r() compatible with
19524 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
19525 bugfix on 0.2.2.1-alpha.
19526 - Fix a NULL-pointer dereference on a badly formed
19527 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
19528 bugfix on 0.2.2.9-alpha.
19529 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
19530 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
19531 - Defensively refactor rend_mid_rendezvous() so that protocol
19532 violations and length checks happen in the beginning. Fixes
19534 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
19535 that IPv6 stuff will compile on MSVC, and compilation issues
19536 will be easier to track down. Fixes bug 5861.
19538 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
19539 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
19540 resource exhaustion, so that clients can adjust their load to
19541 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
19542 started using END_STREAM_REASON_RESOURCELIMIT.
19543 - Don't check for whether the address we're using for outbound
19544 connections has changed until after the outbound connection has
19545 completed. On Windows, getsockname() doesn't succeed until the
19546 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
19547 - If the configuration tries to set MyFamily on a bridge, refuse to
19548 do so, and warn about the security implications. Fixes bug 4657;
19549 bugfix on 0.2.0.3-alpha.
19550 - If the client fails to set a reasonable set of ciphersuites
19551 during its v2 handshake renegotiation, allow the renegotiation to
19552 continue nevertheless (i.e. send all the required certificates).
19553 Fixes bug 4591; bugfix on 0.2.0.20-rc.
19554 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
19555 option is set to 0 (which Vidalia version 0.2.16 now does when
19556 a SAVECONF attempt fails), perform other actions that SIGHUP
19557 usually causes (like reopening the logs). Fixes bug 5095; bugfix
19559 - If we fail to write a microdescriptor to the disk cache, do not
19560 continue replacing the old microdescriptor file. Fixes bug 2954;
19561 bugfix on 0.2.2.6-alpha.
19562 - Exit nodes don't need to fetch certificates for authorities that
19563 they don't recognize; only directory authorities, bridges,
19564 and caches need to do that. Fixes part of bug 2297; bugfix on
19566 - Correctly handle checking the permissions on the parent
19567 directory of a control socket in the root directory. Bug found
19568 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
19570 - When told to add a bridge with the same digest as a preexisting
19571 bridge but a different addr:port, change the addr:port as
19572 requested. Previously we would not notice the change. Fixes half
19573 of bug 5603; fix on 0.2.2.26-beta.
19574 - End AUTHCHALLENGE error messages (in the control protocol) with
19575 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
19577 o Minor bugfixes (on 0.2.3.x):
19578 - Turn an assertion (that the number of handshakes received as a
19579 server is not < 1) into a warning. Fixes bug 4873; bugfix on
19581 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
19582 we had reversed them when the answer was cached.) Fixes bug
19583 5723; bugfix on 0.2.3.1-alpha.
19584 - Work correctly on Linux systems with accept4 support advertised in
19585 their headers, but without accept4 support in the kernel. Fix
19586 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
19587 - When told to add a bridge with the same addr:port as a preexisting
19588 bridge but a different transport, change the transport as
19589 requested. Previously we would not notice the change. Fixes half
19590 of bug 5603; fix on 0.2.3.2-alpha.
19591 - Avoid a "double-reply" warning when replying to a SOCKS request
19592 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
19593 bugfix on 0.2.3.4-alpha.
19594 - Fix a bug where a bridge authority crashes if it has seen no
19595 directory requests when it's time to write statistics to disk.
19596 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
19598 - Don't try to open non-control listeners when DisableNetwork is set.
19599 Previously, we'd open all listeners, then immediately close them.
19600 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
19601 - Don't abort the managed proxy protocol if the managed proxy
19602 sends us an unrecognized line; ignore it instead. Fixes bug
19603 5910; bugfix on 0.2.3.9-alpha.
19604 - Fix a compile warning in crypto.c when compiling with clang 3.1.
19605 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
19606 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
19607 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
19608 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
19609 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
19610 - Resolve numerous small warnings and build issues with MSVC. Resolves
19613 o Documentation fixes:
19614 - Improve the manual's documentation for the NT Service command-line
19615 options. Addresses ticket 3964.
19616 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
19617 - Document the changes to the ORPort and DirPort options, and the
19618 fact that {OR/Dir}ListenAddress is now unnecessary (and
19619 therefore deprecated). Resolves ticket 5597.
19622 - Remove the torrc.bridge file: we don't use it for anything, and
19623 it had become badly desynchronized from torrc.sample. Resolves
19627 Changes in version 0.2.2.36 - 2012-05-24
19628 Tor 0.2.2.36 updates the addresses for two of the eight directory
19629 authorities, fixes some potential anonymity and security issues,
19630 and fixes several crash bugs.
19632 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
19633 known flaws, and nobody should be using them. You should upgrade. If
19634 you're using a Linux or BSD and its packages are obsolete, stop using
19635 those packages and upgrade anyway.
19637 o Directory authority changes:
19638 - Change IP address for maatuska (v3 directory authority).
19639 - Change IP address for ides (v3 directory authority), and rename
19643 - When building or running with any version of OpenSSL earlier
19644 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
19645 versions have a bug (CVE-2011-4576) in which their block cipher
19646 padding includes uninitialized data, potentially leaking sensitive
19647 information to any peer with whom they make a SSLv3 connection. Tor
19648 does not use SSL v3 by default, but a hostile client or server
19649 could force an SSLv3 connection in order to gain information that
19650 they shouldn't have been able to get. The best solution here is to
19651 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
19652 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
19653 to make sure that the bug can't happen.
19654 - Never use a bridge or a controller-supplied node as an exit, even
19655 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19656 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19657 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19658 - Only build circuits if we have a sufficient threshold of the total
19659 descriptors that are marked in the consensus with the "Exit"
19660 flag. This mitigates an attack proposed by wanoskarnet, in which
19661 all of a client's bridges collude to restrict the exit nodes that
19662 the client knows about. Fixes bug 5343.
19663 - Provide controllers with a safer way to implement the cookie
19664 authentication mechanism. With the old method, if another locally
19665 running program could convince a controller that it was the Tor
19666 process, then that program could trick the controller into telling
19667 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19668 authentication method uses a challenge-response approach to prevent
19669 this attack. Fixes bug 5185; implements proposal 193.
19672 - Avoid logging uninitialized data when unable to decode a hidden
19673 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19674 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19675 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19677 - Fix builds when the path to sed, openssl, or sha1sum contains
19678 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
19680 - Correct our replacements for the timeradd() and timersub() functions
19681 on platforms that lack them (for example, Windows). The timersub()
19682 function is used when expiring circuits, while timeradd() is
19683 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
19684 bugfix on 0.2.2.24-alpha.
19685 - Fix the SOCKET_OK test that we use to tell when socket
19686 creation fails so that it works on Win64. Fixes part of bug 4533;
19687 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
19690 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
19691 Fixes bug 5346; bugfix on 0.0.8pre3.
19692 - Make our number-parsing functions always treat too-large values
19693 as an error, even when those values exceed the width of the
19694 underlying type. Previously, if the caller provided these
19695 functions with minima or maxima set to the extreme values of the
19696 underlying integer type, these functions would return those
19697 values on overflow rather than treating overflow as an error.
19698 Fixes part of bug 5786; bugfix on 0.0.9.
19699 - Older Linux kernels erroneously respond to strange nmap behavior
19700 by having accept() return successfully with a zero-length
19701 socket. When this happens, just close the connection. Previously,
19702 we would try harder to learn the remote address: but there was
19703 no such remote address to learn, and our method for trying to
19704 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
19705 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
19706 - Correct parsing of certain date types in parse_http_time().
19707 Without this patch, If-Modified-Since would behave
19708 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
19709 Esteban Manchado Velázques.
19710 - Change the BridgePassword feature (part of the "bridge community"
19711 design, which is not yet implemented) to use a time-independent
19712 comparison. The old behavior might have allowed an adversary
19713 to use timing to guess the BridgePassword value. Fixes bug 5543;
19714 bugfix on 0.2.0.14-alpha.
19715 - Detect and reject certain misformed escape sequences in
19716 configuration values. Previously, these values would cause us
19717 to crash if received in a torrc file or over an authenticated
19718 control port. Bug found by Esteban Manchado Velázquez, and
19719 independently by Robert Connolly from Matta Consulting who further
19720 noted that it allows a post-authentication heap overflow. Patch
19721 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19722 bugfix on 0.2.0.16-alpha.
19723 - Fix a compile warning when using the --enable-openbsd-malloc
19724 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19725 - During configure, detect when we're building with clang version
19726 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
19727 CFLAGS. clang doesn't support them yet.
19728 - When sending an HTTP/1.1 proxy request, include a Host header.
19729 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19730 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
19731 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
19732 - If we hit the error case where routerlist_insert() replaces an
19733 existing (old) server descriptor, make sure to remove that
19734 server descriptor from the old_routers list. Fix related to bug
19735 1776. Bugfix on 0.2.2.18-alpha.
19737 o Minor bugfixes (documentation and log messages):
19738 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
19739 Fixes bug 4856; bugfix on Tor 0.0.6.
19740 - Update "ClientOnly" man page entry to explain that there isn't
19741 really any point to messing with it. Resolves ticket 5005.
19742 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
19743 directory authority option (introduced in Tor 0.2.2.34).
19744 - Downgrade the "We're missing a certificate" message from notice
19745 to info: people kept mistaking it for a real problem, whereas it
19746 is seldom the problem even when we are failing to bootstrap. Fixes
19747 bug 5067; bugfix on 0.2.0.10-alpha.
19748 - Correctly spell "connect" in a log message on failure to create a
19749 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
19750 - Clarify the behavior of MaxCircuitDirtiness with hidden service
19751 circuits. Fixes issue 5259.
19754 - Directory authorities now reject versions of Tor older than
19755 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
19756 inclusive. These versions accounted for only a small fraction of
19757 the Tor network, and have numerous known security issues. Resolves
19759 - Update to the May 1 2012 Maxmind GeoLite Country database.
19762 - When sending or relaying a RELAY_EARLY cell, we used to convert
19763 it to a RELAY cell if the connection was using the v1 link
19764 protocol. This was a workaround for older versions of Tor, which
19765 didn't handle RELAY_EARLY cells properly. Now that all supported
19766 versions can handle RELAY_EARLY cells, and now that we're enforcing
19767 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
19768 remove this workaround. Addresses bug 4786.
19771 Changes in version 0.2.3.15-alpha - 2012-04-30
19772 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
19773 the development branch build on Windows again.
19775 o Minor bugfixes (on 0.2.2.x and earlier):
19776 - Make sure that there are no unhandled pending TLS errors before
19777 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
19778 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
19779 Bugfix on 0.1.0.5-rc; fixes bug 4528.
19780 - Fix an assert that directory authorities could trigger on sighup
19781 during some configuration state transitions. We now don't treat
19782 it as a fatal error when the new descriptor we just generated in
19783 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
19784 - After we pick a directory mirror, we would refuse to use it if
19785 it's in our ExcludeExitNodes list, resulting in mysterious failures
19786 to bootstrap for people who just wanted to avoid exiting from
19787 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
19788 - When building with --enable-static-tor on OpenBSD, do not
19789 erroneously attempt to link -lrt. Fixes bug 5103.
19791 o Minor bugfixes (on 0.2.3.x):
19792 - When Tor is built with kernel headers from a recent (last few
19793 years) Linux kernel, do not fail to run on older (pre-2.6.28
19794 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
19795 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
19796 and 0.2.3.12-alpha.
19797 - Fix compilation with miniupnpc version 1.6; patch from
19798 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
19799 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
19800 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
19801 - Fix compilation on platforms without unistd.h, or where environ
19802 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
19805 - Directory authorities are now a little more lenient at accepting
19806 older router descriptors, or newer router descriptors that don't
19807 make big changes. This should help ameliorate past and future
19808 issues where routers think they have uploaded valid descriptors,
19809 but the authorities don't think so. Fix for ticket 2479.
19810 - Make the code that clients use to detect an address change be
19811 IPv6-aware, so that it won't fill clients' logs with error
19812 messages when trying to get the IPv4 address of an IPv6
19813 connection. Implements ticket 5537.
19815 o Removed features:
19816 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
19817 authorities needed to use it for a while to keep the network working
19818 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
19819 that was six months ago. As of now, it should no longer be needed
19823 Changes in version 0.2.3.14-alpha - 2012-04-23
19824 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
19825 candidate. It also dramatically speeds up AES: fast relays should
19826 consider switching to the newer OpenSSL library.
19828 o Directory authority changes:
19829 - Change IP address for ides (v3 directory authority), and rename
19833 - Avoid logging uninitialized data when unable to decode a hidden
19834 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
19835 - Avoid a client-side assertion failure when receiving an INTRODUCE2
19836 cell on a general purpose circuit. Fixes bug 5644; bugfix on
19838 - If authorities are unable to get a v2 consensus document from other
19839 directory authorities, they no longer fall back to fetching
19840 them from regular directory caches. Fixes bug 5635; bugfix on
19841 0.2.2.26-beta, where routers stopped downloading v2 consensus
19842 documents entirely.
19843 - When we start a Tor client with a normal consensus already cached,
19844 be willing to download a microdescriptor consensus. Fixes bug 4011;
19845 fix on 0.2.3.1-alpha.
19847 o Major features (performance):
19848 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
19849 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
19850 vectorized AES implementations as appropriate. These can be much,
19851 much faster than other AES implementations.
19853 o Minor bugfixes (0.2.2.x and earlier):
19854 - Don't launch more than 10 service-side introduction-point circuits
19855 for a hidden service in five minutes. Previously, we would consider
19856 launching more introduction-point circuits if at least one second
19857 had passed without any introduction-point circuits failing. Fixes
19858 bug 4607; bugfix on 0.0.7pre1.
19859 - Change the BridgePassword feature (part of the "bridge community"
19860 design, which is not yet implemented) to use a time-independent
19861 comparison. The old behavior might have allowed an adversary
19862 to use timing to guess the BridgePassword value. Fixes bug 5543;
19863 bugfix on 0.2.0.14-alpha.
19864 - Enforce correct return behavior of tor_vsscanf() when the '%%'
19865 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
19866 - When sending an HTTP/1.1 proxy request, include a Host header.
19867 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
19868 - Don't log that we have "decided to publish new relay descriptor"
19869 unless we are actually publishing a descriptor. Fixes bug 3942;
19870 bugfix on 0.2.2.28-beta.
19872 o Minor bugfixes (0.2.3.x):
19873 - Fix a bug where a bridge authority crashes (on a failed assert)
19874 if it has seen no directory requests when it's time to write
19875 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
19876 - Fix bug stomping on ORPort option NoListen and ignoring option
19877 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
19878 - In the testsuite, provide a large enough buffer in the tor_sscanf
19879 unit test. Otherwise we'd overrun that buffer and crash during
19880 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
19882 - Make sure we create the keys directory if it doesn't exist and we're
19883 about to store the dynamic Diffie-Hellman parameters. Fixes bug
19884 5572; bugfix on 0.2.3.13-alpha.
19885 - Fix a small memory leak when trying to decode incorrect base16
19886 authenticator during SAFECOOKIE authentication. Found by
19887 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
19890 - Add more information to a log statement that might help track down
19891 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
19892 non-IP address" messages (or any Bug messages, for that matter!),
19893 please let us know about it.
19894 - Relays now understand an IPv6 address when they get one from a
19895 directory server. Resolves ticket 4875.
19896 - Resolve IPv6 addresses in bridge and entry statistics to country
19897 code "??" which means we at least count them. Resolves ticket 5053;
19898 improves on 0.2.3.9-alpha.
19899 - Update to the April 3 2012 Maxmind GeoLite Country database.
19900 - Begin a doc/state-contents.txt file to explain the contents of
19901 the Tor state file. Fixes bug 2987.
19903 o Default torrc changes:
19904 - Stop listing "socksport 9050" in torrc.sample. We open a socks
19905 port on 9050 by default anyway, so this should not change anything
19907 - Stop mentioning the deprecated *ListenAddress options in
19908 torrc.sample. Fixes bug 5438.
19909 - Document unit of bandwidth related options in sample torrc.
19912 o Removed features:
19913 - The "torify" script no longer supports the "tsocks" socksifier
19914 tool, since tsocks doesn't support DNS and UDP right for Tor.
19915 Everyone should be using torsocks instead. Fixes bugs 3530 and
19916 5180. Based on a patch by "ugh".
19918 o Code refactoring:
19919 - Change the symmetric cipher interface so that creating and
19920 initializing a stream cipher are no longer separate functions.
19921 - Remove all internal support for unpadded RSA. We never used it, and
19922 it would be a bad idea to start.
19925 Changes in version 0.2.3.13-alpha - 2012-03-26
19926 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
19927 in managed pluggable transports, as well as providing other cleanups
19928 that get us closer to a release candidate.
19930 o Directory authority changes:
19931 - Change IP address for maatuska (v3 directory authority).
19934 - Provide controllers with a safer way to implement the cookie
19935 authentication mechanism. With the old method, if another locally
19936 running program could convince a controller that it was the Tor
19937 process, then that program could trick the controller into telling
19938 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
19939 authentication method uses a challenge-response approach to prevent
19940 this attack. Fixes bug 5185, implements proposal 193.
19941 - Never use a bridge or a controller-supplied node as an exit, even
19942 if its exit policy allows it. Found by wanoskarnet. Fixes bug
19943 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
19944 and 0.2.0.3-alpha (for bridge-purpose descriptors).
19945 - Only build circuits if we have a sufficient threshold of the total
19946 descriptors that are marked in the consensus with the "Exit"
19947 flag. This mitigates an attack proposed by wanoskarnet, in which
19948 all of a client's bridges collude to restrict the exit nodes that
19949 the client knows about. Fixes bug 5343.
19951 o Major bugfixes (on Tor 0.2.3.x):
19952 - Avoid an assert when managed proxies like obfsproxy are configured,
19953 and we receive HUP signals or setconf attempts too rapidly. This
19954 situation happens most commonly when Vidalia tries to attach to
19955 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
19956 bugfix on 0.2.3.6-alpha.
19957 - Fix a relay-side pluggable transports bug where managed proxies were
19958 unreachable from the Internet, because Tor asked them to bind on
19959 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
19960 - Stop discarding command-line arguments when TestingTorNetwork
19961 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
19962 0.2.3.9-alpha, where task 4552 added support for two layers of
19964 - Resume allowing the unit tests to run in gdb. This was accidentally
19965 made impossible when the DisableDebuggerAttachment option was
19966 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
19967 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
19968 0.2.3.11-alpha. Reported by Anthony G. Basile.
19970 o Minor bugfixes (on 0.2.2.x and earlier):
19971 - Ensure we don't cannibalize circuits that are longer than three hops
19972 already, so we don't end up making circuits with 5 or more
19973 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
19974 0.1.0.1-rc which introduced cannibalization.
19975 - Detect and reject certain misformed escape sequences in
19976 configuration values. Previously, these values would cause us
19977 to crash if received in a torrc file or over an authenticated
19978 control port. Bug found by Esteban Manchado Velázquez, and
19979 independently by Robert Connolly from Matta Consulting who further
19980 noted that it allows a post-authentication heap overflow. Patch
19981 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
19982 bugfix on 0.2.0.16-alpha.
19983 - Fix a compile warning when using the --enable-openbsd-malloc
19984 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
19985 - Directory caches no longer refuse to clean out descriptors because
19986 of missing v2 networkstatus documents, unless they're configured
19987 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
19988 0.2.2.26-beta. Patch by Daniel Bryg.
19989 - Update to the latest version of the tinytest unit testing framework.
19990 This includes a couple of bugfixes that can be relevant for
19991 running forked unit tests on Windows, and removes all reserved
19994 o Minor bugfixes (on 0.2.3.x):
19995 - On a failed pipe() call, don't leak file descriptors. Fixes bug
19996 4296; bugfix on 0.2.3.1-alpha.
19997 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
19998 until after we have received a CERTS cell. Fixes bug 4361; bugfix
19999 on 0.2.3.6-alpha. Patch by "frosty".
20000 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
20001 option, so that the IP stack doesn't decide to use it for IPv4
20002 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
20003 - Ensure that variables set in Tor's environment cannot override
20004 environment variables that Tor passes to a managed
20005 pluggable-transport proxy. Previously, Tor would pass every
20006 variable in its environment to managed proxies along with the new
20007 ones, in such a way that on many operating systems, the inherited
20008 environment variables would override those which Tor tried to
20009 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
20010 bugfix on 0.2.3.9-alpha for Windows.
20013 - A wide variety of new unit tests by Esteban Manchado Velázquez.
20014 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
20015 - Update to the March 6 2012 Maxmind GeoLite Country database.
20018 Changes in version 0.2.3.12-alpha - 2012-02-13
20019 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
20020 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
20021 when Tor is configured to use a pluggable transport like obfsproxy.
20024 - Fix builds when the path to sed, openssl, or sha1sum contains
20025 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
20027 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
20028 connections. This change should allow busy exit relays to stop
20029 running out of available sockets as quickly. Fixes bug 4950;
20030 bugfix on 0.2.2.26-beta.
20031 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
20032 would ask the bridge for microdescriptors, which are only supported
20033 in 0.2.3.x, and then fail to bootstrap when it didn't get the
20034 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
20035 - Properly set up obfsproxy's environment when in managed mode. The
20036 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
20037 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
20038 5076 and 5082; bugfix on 0.2.3.6-alpha.
20041 - Use the dead_strip option when building Tor on OS X. This reduces
20042 binary size by almost 19% when linking openssl and libevent
20043 statically, which we do for Tor Browser Bundle.
20044 - Fix broken URLs in the sample torrc file, and tell readers about
20045 the OutboundBindAddress, ExitPolicyRejectPrivate, and
20046 PublishServerDescriptor options. Addresses bug 4652.
20047 - Update to the February 7 2012 Maxmind GeoLite Country database.
20050 - Downgrade the "We're missing a certificate" message from notice
20051 to info: people kept mistaking it for a real problem, whereas it
20052 is seldom the problem even when we are failing to bootstrap. Fixes
20053 bug 5067; bugfix on 0.2.0.10-alpha.
20054 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
20055 managed pluggable transport server proxy's environment.
20056 Previously, we would put it there, even though Tor doesn't
20057 implement an 'extended server port' yet, and even though Tor
20058 almost certainly isn't listening at that address. For now, we set
20059 it to an empty string to avoid crashing older obfsproxies. Bugfix
20061 - Log the heartbeat message every HeartbeatPeriod seconds, not every
20062 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
20063 0.2.3.1-alpha. Bug reported by Scott Bennett.
20064 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
20065 bugfix on 0.2.3.11-alpha.
20066 - Update "ClientOnly" man page entry to explain that there isn't
20067 really any point to messing with it. Resolves ticket 5005.
20068 - Use the correct CVE number for CVE-2011-4576 in our comments and
20069 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
20072 o Code simplifications and refactoring:
20073 - Use the _WIN32 macro throughout our code to detect Windows.
20074 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
20078 Changes in version 0.2.3.11-alpha - 2012-01-22
20079 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
20080 the last step of the plan to limit maximum circuit length, includes
20081 a wide variety of hidden service performance and correctness fixes,
20082 works around an OpenSSL security flaw if your distro is too stubborn
20083 to upgrade, and fixes a bunch of smaller issues.
20086 - Now that Tor 0.2.0.x is completely deprecated, enable the final
20087 part of "Proposal 110: Avoiding infinite length circuits" by
20088 refusing all circuit-extend requests that do not use a relay_early
20089 cell. This change helps Tor resist a class of denial-of-service
20090 attacks by limiting the maximum circuit length.
20091 - Adjust the number of introduction points that a hidden service
20092 will try to maintain based on how long its introduction points
20093 remain in use and how many introductions they handle. Fixes
20095 - Try to use system facilities for enumerating local interface
20096 addresses, before falling back to our old approach (which was
20097 binding a UDP socket, and calling getsockname() on it). That
20098 approach was scaring OS X users whose draconian firewall
20099 software warned about binding to UDP sockets, regardless of
20100 whether packets were sent. Now we try to use getifaddrs(),
20101 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
20102 system supports. Resolves ticket 1827.
20104 o Major security workaround:
20105 - When building or running with any version of OpenSSL earlier
20106 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
20107 versions have a bug (CVE-2011-4576) in which their block cipher
20108 padding includes uninitialized data, potentially leaking sensitive
20109 information to any peer with whom they make a SSLv3 connection. Tor
20110 does not use SSL v3 by default, but a hostile client or server
20111 could force an SSLv3 connection in order to gain information that
20112 they shouldn't have been able to get. The best solution here is to
20113 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
20114 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
20115 to make sure that the bug can't happen.
20118 - Fix the SOCKET_OK test that we use to tell when socket
20119 creation fails so that it works on Win64. Fixes part of bug 4533;
20120 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
20121 - Correct our replacements for the timeradd() and timersub() functions
20122 on platforms that lack them (for example, Windows). The timersub()
20123 function is used when expiring circuits, while timeradd() is
20124 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
20125 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
20126 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
20127 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
20128 bug at runtime, not compile time, because some distributions hack
20129 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
20130 on 0.2.3.9-alpha. Found by Pascal.
20132 o Minor features (controller):
20133 - Use absolute path names when reporting the torrc filename in the
20134 control protocol, so a controller can more easily find the torrc
20135 file. Resolves bug 1101.
20136 - Extend the control protocol to report flags that control a circuit's
20137 path selection in CIRC events and in replies to 'GETINFO
20138 circuit-status'. Implements part of ticket 2411.
20139 - Extend the control protocol to report the hidden service address
20140 and current state of a hidden-service-related circuit in CIRC
20141 events and in replies to 'GETINFO circuit-status'. Implements part
20143 - When reporting the path to the cookie file to the controller,
20144 give an absolute path. Resolves ticket 4881.
20145 - Allow controllers to request an event notification whenever a
20146 circuit is cannibalized or its purpose is changed. Implements
20147 part of ticket 3457.
20148 - Include the creation time of a circuit in CIRC and CIRC2
20149 control-port events and the list produced by the 'GETINFO
20150 circuit-status' control-port command.
20152 o Minor features (directory authorities):
20153 - Directory authorities now reject versions of Tor older than
20154 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
20155 inclusive. These versions accounted for only a small fraction of
20156 the Tor network, and have numerous known security issues. Resolves
20158 - Authority operators can now vote for all relays in a given
20159 set of countries to be BadDir/BadExit/Invalid/Rejected.
20160 - Provide two consensus parameters (FastFlagMinThreshold and
20161 FastFlagMaxThreshold) to control the range of allowable bandwidths
20162 for the Fast directory flag. These allow authorities to run
20163 experiments on appropriate requirements for being a "Fast" node.
20164 The AuthDirFastGuarantee config value still applies. Implements
20166 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
20167 directory authority option (introduced in Tor 0.2.2.34).
20169 o Minor features (other):
20170 - Don't disable the DirPort when we cannot exceed our AccountingMax
20171 limit during this interval because the effective bandwidthrate is
20172 low enough. This is useful in a situation where AccountMax is only
20173 used as an additional safeguard or to provide statistics.
20174 - Prepend an informative header to generated dynamic_dh_params files.
20175 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
20176 EntryNodes will have no effect. Resolves issue 2571.
20177 - Log more useful messages when we fail to disable debugger
20179 - Log which authority we're missing votes from when we go to fetch
20180 them from the other auths.
20181 - Log (at debug level) whenever a circuit's purpose is changed.
20182 - Add missing documentation for the MaxClientCircuitsPending,
20183 UseMicrodescriptors, UserspaceIOCPBuffers, and
20184 _UseFilteringSSLBufferevents options, all introduced during
20185 the 0.2.3.x series.
20186 - Update to the January 3 2012 Maxmind GeoLite Country database.
20188 o Minor bugfixes (hidden services):
20189 - Don't close hidden service client circuits which have almost
20190 finished connecting to their destination when they reach
20191 the normal circuit-build timeout. Previously, we would close
20192 introduction circuits which are waiting for an acknowledgement
20193 from the introduction point, and rendezvous circuits which have
20194 been specified in an INTRODUCE1 cell sent to a hidden service,
20195 after the normal CBT. Now, we mark them as 'timed out', and launch
20196 another rendezvous attempt in parallel. This behavior change can
20197 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
20198 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
20199 - Don't close hidden-service-side rendezvous circuits when they
20200 reach the normal circuit-build timeout. This behavior change can
20201 be disabled using the new
20202 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
20203 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
20204 - Make sure we never mark the wrong rendezvous circuit as having
20205 had its introduction cell acknowledged by the introduction-point
20206 relay. Previously, when we received an INTRODUCE_ACK cell on a
20207 client-side hidden-service introduction circuit, we might have
20208 marked a rendezvous circuit other than the one we specified in
20209 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
20210 a warning message and interfered with the hidden service
20211 connection-establishment process. Fixes bug 4759; bugfix on
20212 0.2.3.3-alpha, when we added the stream-isolation feature which
20213 might cause Tor to open multiple rendezvous circuits for the same
20215 - Don't trigger an assertion failure when we mark a new client-side
20216 hidden-service introduction circuit for close during the process
20217 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
20220 o Minor bugfixes (log messages):
20221 - Correctly spell "connect" in a log message on failure to create a
20222 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
20224 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
20225 Fixes bug 4856; bugfix on Tor 0.0.6.
20226 - Fix the log message describing how we work around discovering
20227 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
20228 4837; bugfix on 0.2.2.9-alpha.
20229 - When logging about a disallowed .exit name, do not also call it
20230 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
20232 o Minor bugfixes (build fixes):
20233 - During configure, detect when we're building with clang version
20234 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
20235 CFLAGS. clang doesn't support them yet.
20236 - During configure, search for library containing cos function as
20237 libm lives in libcore on some platforms (BeOS/Haiku). Linking
20238 against libm was hard-coded before. Fixes the first part of bug
20239 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
20241 - Detect attempts to build Tor on (as yet hypothetical) versions
20242 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
20243 fix for bug 4533. Bugfix on 0.2.2.28-beta.
20244 - Preprocessor directives should not be put inside the arguments
20245 of a macro. This would break compilation with GCC releases prior
20246 to version 3.3. We would never recommend such an old GCC version,
20247 but it is apparently required for binary compatibility on some
20248 platforms (namely, certain builds of Haiku). Fixes the other part
20249 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
20252 o Minor bugfixes (other):
20253 - Older Linux kernels erroneously respond to strange nmap behavior
20254 by having accept() return successfully with a zero-length
20255 socket. When this happens, just close the connection. Previously,
20256 we would try harder to learn the remote address: but there was
20257 no such remote address to learn, and our method for trying to
20258 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
20259 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
20260 - Fix null-pointer access that could occur if TLS allocation failed.
20261 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
20262 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
20263 accidentally been reverted.
20264 - Fix our implementation of crypto_random_hostname() so it can't
20265 overflow on ridiculously large inputs. (No Tor version has ever
20266 provided this kind of bad inputs, but let's be correct in depth.)
20267 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
20268 - Find more places in the code that should have been testing for
20269 invalid sockets using the SOCKET_OK macro. Required for a fix
20270 for bug 4533. Bugfix on 0.2.2.28-beta.
20271 - Fix an assertion failure when, while running with bufferevents, a
20272 connection finishes connecting after it is marked for close, but
20273 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
20274 - test_util_spawn_background_ok() hardcoded the expected value
20275 for ENOENT to 2. This isn't portable as error numbers are
20276 platform specific, and particularly the hurd has ENOENT at
20277 0x40000002. Construct expected string at runtime, using the correct
20278 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
20279 - Reject attempts to disable DisableDebuggerAttachment while Tor is
20280 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
20281 - Use an appropriate-width type for sockets in tor-fw-helper on
20282 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
20285 - When sending or relaying a RELAY_EARLY cell, we used to convert
20286 it to a RELAY cell if the connection was using the v1 link
20287 protocol. This was a workaround for older versions of Tor, which
20288 didn't handle RELAY_EARLY cells properly. Now that all supported
20289 versions can handle RELAY_EARLY cells, and now that we're enforcing
20290 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
20291 remove this workaround. Addresses bug 4786.
20293 o Code simplifications and refactoring:
20294 - Use OpenSSL's built-in SSL_state_string_long() instead of our
20295 own homebrewed ssl_state_to_string() replacement. Patch from
20296 Emile Snyder. Fixes bug 4653.
20297 - Use macros to indicate OpenSSL versions, so we don't need to worry
20298 about accidental hexadecimal bit shifts.
20299 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
20301 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
20302 - Use the smartlist_add_asprintf() alias more consistently.
20303 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
20304 invalid value, rather than just -1.
20305 - Rename a handful of old identifiers, mostly related to crypto
20306 structures and crypto functions. By convention, our "create an
20307 object" functions are called "type_new()", our "free an object"
20308 functions are called "type_free()", and our types indicate that
20309 they are types only with a final "_t". But a handful of older
20310 types and functions broke these rules, with function names like
20311 "type_create" or "subsystem_op_type", or with type names like
20315 Changes in version 0.2.3.10-alpha - 2011-12-16
20316 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
20317 Tor's buffers code. Absolutely everybody should upgrade.
20319 The bug relied on an incorrect calculation when making data continuous
20320 in one of our IO buffers, if the first chunk of the buffer was
20321 misaligned by just the wrong amount. The miscalculation would allow an
20322 attacker to overflow a piece of heap-allocated memory. To mount this
20323 attack, the attacker would need to either open a SOCKS connection to
20324 Tor's SocksPort (usually restricted to localhost), or target a Tor
20325 instance configured to make its connections through a SOCKS proxy
20326 (which Tor does not do by default).
20328 Good security practice requires that all heap-overflow bugs should be
20329 presumed to be exploitable until proven otherwise, so we are treating
20330 this as a potential code execution attack. Please upgrade immediately!
20331 This bug does not affect bufferevents-based builds of Tor. Special
20332 thanks to "Vektor" for reporting this issue to us!
20334 This release also contains a few minor bugfixes for issues discovered
20338 - Fix a heap overflow bug that could occur when trying to pull
20339 data into the first chunk of a buffer, when that chunk had
20340 already had some data drained from it. Fixes CVE-2011-2778;
20341 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20344 - If we can't attach streams to a rendezvous circuit when we
20345 finish connecting to a hidden service, clear the rendezvous
20346 circuit's stream-isolation state and try to attach streams
20347 again. Previously, we cleared rendezvous circuits' isolation
20348 state either too early (if they were freshly built) or not at all
20349 (if they had been built earlier and were cannibalized). Bugfix on
20350 0.2.3.3-alpha; fixes bug 4655.
20351 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
20352 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
20353 - Fix an assertion failure when a relay with accounting enabled
20354 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
20357 - Update to the December 6 2011 Maxmind GeoLite Country database.
20360 Changes in version 0.2.2.35 - 2011-12-16
20361 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
20362 buffers code. Absolutely everybody should upgrade.
20364 The bug relied on an incorrect calculation when making data continuous
20365 in one of our IO buffers, if the first chunk of the buffer was
20366 misaligned by just the wrong amount. The miscalculation would allow an
20367 attacker to overflow a piece of heap-allocated memory. To mount this
20368 attack, the attacker would need to either open a SOCKS connection to
20369 Tor's SocksPort (usually restricted to localhost), or target a Tor
20370 instance configured to make its connections through a SOCKS proxy
20371 (which Tor does not do by default).
20373 Good security practice requires that all heap-overflow bugs should be
20374 presumed to be exploitable until proven otherwise, so we are treating
20375 this as a potential code execution attack. Please upgrade immediately!
20376 This bug does not affect bufferevents-based builds of Tor. Special
20377 thanks to "Vektor" for reporting this issue to us!
20379 Tor 0.2.2.35 also fixes several bugs in previous versions, including
20380 crash bugs for unusual configurations, and a long-term bug that
20381 would prevent Tor from starting on Windows machines with draconian
20384 With this release, we remind everyone that 0.2.0.x has reached its
20385 formal end-of-life. Those Tor versions have many known flaws, and
20386 nobody should be using them. You should upgrade -- ideally to the
20387 0.2.2.x series. If you're using a Linux or BSD and its packages are
20388 obsolete, stop using those packages and upgrade anyway.
20390 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
20391 longer receive support after some time in early 2012.
20394 - Fix a heap overflow bug that could occur when trying to pull
20395 data into the first chunk of a buffer, when that chunk had
20396 already had some data drained from it. Fixes CVE-2011-2778;
20397 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20398 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20399 that it doesn't attempt to allocate a socketpair. This could cause
20400 some problems on Windows systems with overzealous firewalls. Fix for
20401 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20403 - If we mark an OR connection for close based on a cell we process,
20404 don't process any further cells on it. We already avoid further
20405 reads on marked-for-close connections, but now we also discard the
20406 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20407 which was the first version where we might mark a connection for
20408 close based on processing a cell on it.
20409 - Correctly sanity-check that we don't underflow on a memory
20410 allocation (and then assert) for hidden service introduction
20411 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20412 bugfix on 0.2.1.5-alpha.
20413 - Fix a memory leak when we check whether a hidden service
20414 descriptor has any usable introduction points left. Fixes bug
20415 4424. Bugfix on 0.2.2.25-alpha.
20416 - Don't crash when we're running as a relay and don't have a GeoIP
20417 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
20418 we've had in the 0.2.3.x branch already.
20419 - When running as a client, do not print a misleading (and plain
20420 wrong) log message that we're collecting "directory request"
20421 statistics: clients don't collect statistics. Also don't create a
20422 useless (because empty) stats file in the stats/ directory. Fixes
20423 bug 4353; bugfix on 0.2.2.34.
20426 - Detect failure to initialize Libevent. This fix provides better
20427 detection for future instances of bug 4457.
20428 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20429 function. This was eating up hideously large amounts of time on some
20430 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20431 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20432 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20434 - Don't warn about unused log_mutex in log.c when building with
20435 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20436 0.1.0.6-rc which introduced --disable-threads.
20437 - When configuring, starting, or stopping an NT service, stop
20438 immediately after the service configuration attempt has succeeded
20439 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20440 - When sending a NETINFO cell, include the original address
20441 received for the other side, not its canonical address. Found
20442 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20443 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
20444 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20445 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20446 occurred when a client tried to fetch a descriptor for a bridge
20447 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20448 - Backport fixes for a pair of compilation warnings on Windows.
20449 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
20450 - If we had ever tried to call tor_addr_to_str on an address of
20451 unknown type, we would have done a strdup on an uninitialized
20452 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20453 Reported by "troll_un".
20454 - Correctly detect and handle transient lookup failures from
20455 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20456 Reported by "troll_un".
20457 - Fix null-pointer access that could occur if TLS allocation failed.
20458 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20459 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20460 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20463 - Add two new config options for directory authorities:
20464 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20465 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20466 that is always sufficient to satisfy the bandwidth requirement for
20467 the Guard flag. Now it will be easier for researchers to simulate
20468 Tor networks with different values. Resolves ticket 4484.
20469 - When Tor ignores a hidden service specified in its configuration,
20470 include the hidden service's directory in the warning message.
20471 Previously, we would only tell the user that some hidden service
20472 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20473 - Update to the December 6 2011 Maxmind GeoLite Country database.
20475 o Packaging changes:
20476 - Make it easier to automate expert package builds on Windows,
20477 by removing an absolute path from makensis.exe command.
20480 Changes in version 0.2.1.32 - 2011-12-16
20481 Tor 0.2.1.32 backports important security and privacy fixes for
20482 oldstable. This release is intended only for package maintainers and
20483 others who cannot use the 0.2.2 stable series. All others should be
20484 using Tor 0.2.2.x or newer.
20486 The Tor 0.2.1.x series will reach formal end-of-life some time in
20487 early 2012; we will stop releasing patches for it then.
20489 o Major bugfixes (also included in 0.2.2.x):
20490 - Correctly sanity-check that we don't underflow on a memory
20491 allocation (and then assert) for hidden service introduction
20492 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20493 bugfix on 0.2.1.5-alpha.
20494 - Fix a heap overflow bug that could occur when trying to pull
20495 data into the first chunk of a buffer, when that chunk had
20496 already had some data drained from it. Fixes CVE-2011-2778;
20497 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
20500 - Update to the December 6 2011 Maxmind GeoLite Country database.
20503 Changes in version 0.2.3.9-alpha - 2011-12-08
20504 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
20505 a "DisableNetwork" security feature that bundles can use to avoid
20506 touching the network until bridges are configured, moves forward on
20507 the pluggable transport design, fixes a flaw in the hidden service
20508 design that unnecessarily prevented clients with wrong clocks from
20509 reaching hidden services, and fixes a wide variety of other issues.
20512 - Clients can now connect to private bridges over IPv6. Bridges
20513 still need at least one IPv4 address in order to connect to
20514 other relays. Note that we don't yet handle the case where the
20515 user has two bridge lines for the same bridge (one IPv4, one
20516 IPv6). Implements parts of proposal 186.
20517 - New "DisableNetwork" config option to prevent Tor from launching any
20518 connections or accepting any connections except on a control port.
20519 Bundles and controllers can set this option before letting Tor talk
20520 to the rest of the network, for example to prevent any connections
20521 to a non-bridge address. Packages like Orbot can also use this
20522 option to instruct Tor to save power when the network is off.
20523 - Clients and bridges can now be configured to use a separate
20524 "transport" proxy. This approach makes the censorship arms race
20525 easier by allowing bridges to use protocol obfuscation plugins. It
20526 implements the "managed proxy" part of proposal 180 (ticket 3472).
20527 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
20528 implementation. It makes AES_CTR about 7% faster than our old one
20529 (which was about 10% faster than the one OpenSSL used to provide).
20530 Resolves ticket 4526.
20531 - Add a "tor2web mode" for clients that want to connect to hidden
20532 services non-anonymously (and possibly more quickly). As a safety
20533 measure to try to keep users from turning this on without knowing
20534 what they are doing, tor2web mode must be explicitly enabled at
20535 compile time, and a copy of Tor compiled to run in tor2web mode
20536 cannot be used as a normal Tor client. Implements feature 2553.
20537 - Add experimental support for running on Windows with IOCP and no
20538 kernel-space socket buffers. This feature is controlled by a new
20539 "UserspaceIOCPBuffers" config option (off by default), which has
20540 no effect unless Tor has been built with support for bufferevents,
20541 is running on Windows, and has enabled IOCP. This may, in the long
20542 run, help solve or mitigate bug 98.
20543 - Use a more secure consensus parameter voting algorithm. Now at
20544 least three directory authorities or a majority of them must
20545 vote on a given parameter before it will be included in the
20546 consensus. Implements proposal 178.
20549 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
20550 They used to check that the timestamp was within 30 minutes
20551 of their system clock, so they could cap the size of their
20552 replay-detection cache, but that approach unnecessarily refused
20553 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
20554 the v3 intro-point protocol (the first one which sent a timestamp
20555 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
20556 - Only use the EVP interface when AES acceleration is enabled,
20557 to avoid a 5-7% performance regression. Resolves issue 4525;
20558 bugfix on 0.2.3.8-alpha.
20560 o Privacy/anonymity features (bridge detection):
20561 - Make bridge SSL certificates a bit more stealthy by using random
20562 serial numbers, in the same fashion as OpenSSL when generating
20563 self-signed certificates. Implements ticket 4584.
20564 - Introduce a new config option "DynamicDHGroups", enabled by
20565 default, which provides each bridge with a unique prime DH modulus
20566 to be used during SSL handshakes. This option attempts to help
20567 against censors who might use the Apache DH modulus as a static
20568 identifier for bridges. Addresses ticket 4548.
20570 o Minor features (new/different config options):
20571 - New configuration option "DisableDebuggerAttachment" (on by default)
20572 to prevent basic debugging attachment attempts by other processes.
20573 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
20574 - Allow MapAddress directives to specify matches against super-domains,
20575 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
20576 Implements issue 933.
20577 - Slightly change behavior of "list" options (that is, config
20578 options that can appear more than once) when they appear both in
20579 torrc and on the command line. Previously, the command-line options
20580 would be appended to the ones from torrc. Now, the command-line
20581 options override the torrc options entirely. This new behavior
20582 allows the user to override list options (like exit policies and
20583 ports to listen on) from the command line, rather than simply
20584 appending to the list.
20585 - You can get the old (appending) command-line behavior for "list"
20586 options by prefixing the option name with a "+".
20587 - You can remove all the values for a "list" option from the command
20588 line without adding any new ones by prefixing the option name
20590 - Add experimental support for a "defaults" torrc file to be parsed
20591 before the regular torrc. Torrc options override the defaults file's
20592 options in the same way that the command line overrides the torrc.
20593 The SAVECONF controller command saves only those options which
20594 differ between the current configuration and the defaults file. HUP
20595 reloads both files. (Note: This is an experimental feature; its
20596 behavior will probably be refined in future 0.2.3.x-alpha versions
20597 to better meet packagers' needs.) Implements task 4552.
20600 - Try to make the introductory warning message that Tor prints on
20601 startup more useful for actually finding help and information.
20602 Resolves ticket 2474.
20603 - Running "make version" now displays the version of Tor that
20604 we're about to build. Idea from katmagic; resolves issue 4400.
20605 - Expire old or over-used hidden service introduction points.
20606 Required by fix for bug 3460.
20607 - Move the replay-detection cache for the RSA-encrypted parts of
20608 INTRODUCE2 cells to the introduction point data structures.
20609 Previously, we would use one replay-detection cache per hidden
20610 service. Required by fix for bug 3460.
20611 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
20612 public key replay-detection cache from 60 minutes to 5 minutes. This
20613 replay-detection cache is now used only to detect multiple
20614 INTRODUCE2 cells specifying the same rendezvous point, so we can
20615 avoid launching multiple simultaneous attempts to connect to it.
20617 o Minor bugfixes (on Tor 0.2.2.x and earlier):
20618 - Resolve an integer overflow bug in smartlist_ensure_capacity().
20619 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
20621 - Fix a minor formatting issue in one of tor-gencert's error messages.
20623 - Prevent a false positive from the check-spaces script, by disabling
20624 the "whitespace between function name and (" check for functions
20626 - Fix a log message suggesting that people contact a non-existent
20627 email address. Fixes bug 3448.
20628 - Fix null-pointer access that could occur if TLS allocation failed.
20629 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
20630 - Report a real bootstrap problem to the controller on router
20631 identity mismatch. Previously we just said "foo", which probably
20632 made a lot of sense at the time. Fixes bug 4169; bugfix on
20634 - If we had ever tried to call tor_addr_to_str() on an address of
20635 unknown type, we would have done a strdup() on an uninitialized
20636 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
20637 Reported by "troll_un".
20638 - Correctly detect and handle transient lookup failures from
20639 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
20640 Reported by "troll_un".
20641 - Use tor_socket_t type for listener argument to accept(). Fixes bug
20642 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
20643 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
20644 bug 4532; found by "troll_un".
20646 o Minor bugfixes (on Tor 0.2.3.x):
20647 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
20649 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
20650 circuit for use as a hidden service client's rendezvous point.
20651 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
20652 with help from wanoskarnet.
20653 - Restore behavior of overriding SocksPort, ORPort, and similar
20654 options from the command line. Bugfix on 0.2.3.3-alpha.
20657 - Properly handle the case where the build-tree is not the same
20658 as the source tree when generating src/common/common_sha1.i,
20659 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
20660 bugfix on 0.2.0.1-alpha.
20662 o Code simplifications, cleanups, and refactorings:
20663 - Remove the pure attribute from all functions that used it
20664 previously. In many cases we assigned it incorrectly, because the
20665 functions might assert or call impure functions, and we don't have
20666 evidence that keeping the pure attribute is worthwhile. Implements
20667 changes suggested in ticket 4421.
20668 - Remove some dead code spotted by coverity. Fixes cid 432.
20669 Bugfix on 0.2.3.1-alpha, closes bug 4637.
20672 Changes in version 0.2.3.8-alpha - 2011-11-22
20673 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
20674 socketpair-related bug that has been bothering Windows users. It adds
20675 support to serve microdescriptors to controllers, so Vidalia's network
20676 map can resume listing relays (once Vidalia implements its side),
20677 and adds better support for hardware AES acceleration. Finally, it
20678 starts the process of adjusting the bandwidth cutoff for getting the
20679 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
20680 that tiny relays harm performance more than they help network capacity.
20683 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
20684 that it doesn't attempt to allocate a socketpair. This could cause
20685 some problems on Windows systems with overzealous firewalls. Fix for
20686 bug 4457; workaround for Libevent versions 2.0.1-alpha through
20688 - Correctly sanity-check that we don't underflow on a memory
20689 allocation (and then assert) for hidden service introduction
20690 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
20691 bugfix on 0.2.1.5-alpha.
20692 - Remove the artificially low cutoff of 20KB to guarantee the Fast
20693 flag. In the past few years the average relay speed has picked
20694 up, and while the "top 7/8 of the network get the Fast flag" and
20695 "all relays with 20KB or more of capacity get the Fast flag" rules
20696 used to have the same result, now the top 7/8 of the network has
20697 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
20698 - Fix a rare assertion failure when checking whether a v0 hidden
20699 service descriptor has any usable introduction points left, and
20700 we don't have enough information to build a circuit to the first
20701 intro point named in the descriptor. The HS client code in
20702 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
20703 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
20704 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
20705 - Make bridge authorities not crash when they are asked for their own
20706 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
20707 - When running as a client, do not print a misleading (and plain
20708 wrong) log message that we're collecting "directory request"
20709 statistics: clients don't collect statistics. Also don't create a
20710 useless (because empty) stats file in the stats/ directory. Fixes
20711 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
20714 - Allow Tor controllers like Vidalia to obtain the microdescriptor
20715 for a relay by identity digest or nickname. Previously,
20716 microdescriptors were only available by their own digests, so a
20717 controller would have to ask for and parse the whole microdescriptor
20718 consensus in order to look up a single relay's microdesc. Fixes
20719 bug 3832; bugfix on 0.2.3.1-alpha.
20720 - Use OpenSSL's EVP interface for AES encryption, so that all AES
20721 operations can use hardware acceleration (if present). Resolves
20724 o Minor bugfixes (on 0.2.2.x and earlier):
20725 - Detect failure to initialize Libevent. This fix provides better
20726 detection for future instances of bug 4457.
20727 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
20728 function. This was eating up hideously large amounts of time on some
20729 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
20730 - Don't warn about unused log_mutex in log.c when building with
20731 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
20732 0.1.0.6-rc which introduced --disable-threads.
20733 - Allow manual 'authenticate' commands to the controller interface
20734 from netcat (nc) as well as telnet. We were rejecting them because
20735 they didn't come with the expected whitespace at the end of the
20736 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
20737 - Fix some (not actually triggerable) buffer size checks in usage of
20738 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
20740 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
20741 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
20742 - When configuring, starting, or stopping an NT service, stop
20743 immediately after the service configuration attempt has succeeded
20744 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
20745 - When sending a NETINFO cell, include the original address
20746 received for the other side, not its canonical address. Found
20747 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
20748 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
20749 can pick them up when the tests aren't disabled. Bugfix on
20750 0.2.2.4-alpha which introduced tinytest.
20751 - Fix a memory leak when we check whether a hidden service
20752 descriptor has any usable introduction points left. Fixes bug
20753 4424. Bugfix on 0.2.2.25-alpha.
20754 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
20755 occurred when a client tried to fetch a descriptor for a bridge
20756 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
20758 o Minor bugfixes (on 0.2.3.x):
20759 - Make util unit tests build correctly with MSVC. Bugfix on
20760 0.2.3.3-alpha. Patch by Gisle Vanem.
20761 - Successfully detect AUTH_CHALLENGE cells with no recognized
20762 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
20763 Found by frosty_un.
20764 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
20765 it should still send a NETINFO cell to allow the connection to
20766 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
20768 - Log less loudly when we get an invalid authentication certificate
20769 from a source other than a directory authority: it's not unusual
20770 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
20772 - Tolerate servers with more clock skew in their authentication
20773 certificates than previously. Fixes bug 4371; bugfix on
20775 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
20776 on 0.2.3.4-alpha and 0.2.3.6-alpha.
20779 - Add two new config options for directory authorities:
20780 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
20781 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
20782 that is always sufficient to satisfy the bandwidth requirement for
20783 the Guard flag. Now it will be easier for researchers to simulate
20784 Tor networks with different values. Resolves ticket 4484.
20785 - When Tor ignores a hidden service specified in its configuration,
20786 include the hidden service's directory in the warning message.
20787 Previously, we would only tell the user that some hidden service
20788 was ignored. Bugfix on 0.0.6; fixes bug 4426.
20789 - When we fail to initialize Libevent, retry with IOCP disabled so we
20790 don't need to turn on multi-threading support in Libevent, which in
20791 turn requires a working socketpair(). This is a workaround for bug
20792 4457, which affects Libevent versions from 2.0.1-alpha through
20794 - Detect when we try to build on a platform that doesn't define
20795 AF_UNSPEC to 0. We don't work there, so refuse to compile.
20796 - Update to the November 1 2011 Maxmind GeoLite Country database.
20798 o Packaging changes:
20799 - Make it easier to automate expert package builds on Windows,
20800 by removing an absolute path from makensis.exe command.
20802 o Code simplifications and refactoring:
20803 - Remove some redundant #include directives throughout the code.
20804 Patch from Andrea Gelmini.
20805 - Unconditionally use OpenSSL's AES implementation instead of our
20806 old built-in one. OpenSSL's AES has been better for a while, and
20807 relatively few servers should still be on any version of OpenSSL
20808 that doesn't have good optimized assembly AES.
20809 - Use the name "CERTS" consistently to refer to the new cell type;
20810 we were calling it CERT in some places and CERTS in others.
20813 - Numerous new unit tests for functions in util.c and address.c by
20815 - The long-disabled benchmark tests are now split into their own
20816 ./src/test/bench binary.
20817 - The benchmark tests can now use more accurate timers than
20818 gettimeofday() when such timers are available.
20821 Changes in version 0.2.3.7-alpha - 2011-10-30
20822 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
20823 the new v3 handshake. It also resolves yet another bridge address
20827 - If we mark an OR connection for close based on a cell we process,
20828 don't process any further cells on it. We already avoid further
20829 reads on marked-for-close connections, but now we also discard the
20830 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
20831 which was the first version where we might mark a connection for
20832 close based on processing a cell on it.
20833 - Fix a double-free bug that would occur when we received an invalid
20834 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
20835 bugfix on 0.2.3.6-alpha.
20836 - Bridges no longer include their address in NETINFO cells on outgoing
20837 OR connections, to allow them to blend in better with clients.
20838 Removes another avenue for enumerating bridges. Reported by
20839 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
20840 cells were introduced.
20843 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
20844 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
20847 Changes in version 0.2.3.6-alpha - 2011-10-26
20848 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
20849 anonymity vulnerability where an attacker can deanonymize Tor
20850 users. Everybody should upgrade.
20852 This release also features support for a new v3 connection handshake
20853 protocol, and fixes to make hidden service connections more robust.
20856 - Implement a new handshake protocol (v3) for authenticating Tors to
20857 each other over TLS. It should be more resistant to fingerprinting
20858 than previous protocols, and should require less TLS hacking for
20859 future Tor implementations. Implements proposal 176.
20860 - Allow variable-length padding cells to disguise the length of
20861 Tor's TLS records. Implements part of proposal 184.
20863 o Privacy/anonymity fixes (clients):
20864 - Clients and bridges no longer send TLS certificate chains on
20865 outgoing OR connections. Previously, each client or bridge would
20866 use the same cert chain for all outgoing OR connections until
20867 its IP address changes, which allowed any relay that the client
20868 or bridge contacted to determine which entry guards it is using.
20869 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
20870 - If a relay receives a CREATE_FAST cell on a TLS connection, it
20871 no longer considers that connection as suitable for satisfying a
20872 circuit EXTEND request. Now relays can protect clients from the
20873 CVE-2011-2768 issue even if the clients haven't upgraded yet.
20874 - Directory authorities no longer assign the Guard flag to relays
20875 that haven't upgraded to the above "refuse EXTEND requests
20876 to client connections" fix. Now directory authorities can
20877 protect clients from the CVE-2011-2768 issue even if neither
20878 the clients nor the relays have upgraded yet. There's a new
20879 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
20880 to let us transition smoothly, else tomorrow there would be no
20883 o Major bugfixes (hidden services):
20884 - Improve hidden service robustness: when an attempt to connect to
20885 a hidden service ends, be willing to refetch its hidden service
20886 descriptors from each of the HSDir relays responsible for them
20887 immediately. Previously, we would not consider refetching the
20888 service's descriptors from each HSDir for 15 minutes after the last
20889 fetch, which was inconvenient if the hidden service was not running
20890 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
20891 - When one of a hidden service's introduction points appears to be
20892 unreachable, stop trying it. Previously, we would keep trying
20893 to build circuits to the introduction point until we lost the
20894 descriptor, usually because the user gave up and restarted Tor.
20895 Partly fixes bug 3825.
20896 - Don't launch a useless circuit after failing to use one of a
20897 hidden service's introduction points. Previously, we would
20898 launch a new introduction circuit, but not set the hidden service
20899 which that circuit was intended to connect to, so it would never
20900 actually be used. A different piece of code would then create a
20901 new introduction circuit correctly. Bug reported by katmagic and
20902 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
20904 o Major bugfixes (other):
20905 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
20906 that they initiated. Relays could distinguish incoming bridge
20907 connections from client connections, creating another avenue for
20908 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
20909 Found by "frosty_un".
20910 - Don't update the AccountingSoftLimitHitAt state file entry whenever
20911 tor gets started. This prevents a wrong average bandwidth
20912 estimate, which would cause relays to always start a new accounting
20913 interval at the earliest possible moment. Fixes bug 2003; bugfix
20914 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
20915 immensely in tracking this bug down.
20916 - Fix a crash bug when changing node restrictions while a DNS lookup
20917 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
20920 o Minor bugfixes (on 0.2.2.x and earlier):
20921 - When a hidden service turns an extra service-side introduction
20922 circuit into a general-purpose circuit, free the rend_data and
20923 intro_key fields first, so we won't leak memory if the circuit
20924 is cannibalized for use as another service-side introduction
20925 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
20926 - Rephrase the log message emitted if the TestSocks check is
20927 successful. Patch from Fabian Keil; fixes bug 4094.
20928 - Bridges now skip DNS self-tests, to act a little more stealthily.
20929 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
20930 bridges. Patch by "warms0x".
20931 - Remove a confusing dollar sign from the example fingerprint in the
20932 man page, and also make the example fingerprint a valid one. Fixes
20933 bug 4309; bugfix on 0.2.1.3-alpha.
20934 - Fix internal bug-checking logic that was supposed to catch
20935 failures in digest generation so that it will fail more robustly
20936 if we ask for a nonexistent algorithm. Found by Coverity Scan.
20937 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
20938 - Report any failure in init_keys() calls launched because our
20939 IP address has changed. Spotted by Coverity Scan. Bugfix on
20940 0.1.1.4-alpha; fixes CID 484.
20942 o Minor bugfixes (on 0.2.3.x):
20943 - Fix a bug in configure.in that kept it from building a configure
20944 script with autoconf versions earlier than 2.61. Fixes bug 2430;
20945 bugfix on 0.2.3.1-alpha.
20946 - Don't warn users that they are exposing a client port to the
20947 Internet if they have specified an RFC1918 address. Previously,
20948 we would warn if the user had specified any non-loopback
20949 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
20950 - Fix memory leaks in the failing cases of the new SocksPort and
20951 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
20952 fixes coverity CIDs 485, 486, and 487.
20955 - When a hidden service's introduction point times out, consider
20956 trying it again during the next attempt to connect to the
20957 HS. Previously, we would not try it again unless a newly fetched
20958 descriptor contained it. Required by fixes for bugs 1297 and 3825.
20959 - The next version of Windows will be called Windows 8, and it has
20960 a major version of 6, minor version of 2. Correctly identify that
20961 version instead of calling it "Very recent version". Resolves
20962 ticket 4153; reported by funkstar.
20963 - The Bridge Authority now writes statistics on how many bridge
20964 descriptors it gave out in total, and how many unique descriptors
20965 it gave out. It also lists how often the most and least commonly
20966 fetched descriptors were given out, as well as the median and
20967 25th/75th percentile. Implements tickets 4200 and 4294.
20968 - Update to the October 4 2011 Maxmind GeoLite Country database.
20970 o Code simplifications and refactoring:
20971 - Remove some old code to remember statistics about which descriptors
20972 we've served as a directory mirror. The feature wasn't used and
20973 is outdated now that microdescriptors are around.
20974 - Rename Tor functions that turn strings into addresses, so that
20975 "parse" indicates that no hostname resolution occurs, and
20976 "lookup" indicates that hostname resolution may occur. This
20977 should help prevent mistakes in the future. Fixes bug 3512.
20980 Changes in version 0.2.2.34 - 2011-10-26
20981 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
20982 can deanonymize Tor users. Everybody should upgrade.
20984 The attack relies on four components: 1) Clients reuse their TLS cert
20985 when talking to different relays, so relays can recognize a user by
20986 the identity key in her cert. 2) An attacker who knows the client's
20987 identity key can probe each guard relay to see if that identity key
20988 is connected to that guard relay right now. 3) A variety of active
20989 attacks in the literature (starting from "Low-Cost Traffic Analysis
20990 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
20991 discover the guard relays that a Tor user visiting the website is using.
20992 4) Clients typically pick three guards at random, so the set of guards
20993 for a given user could well be a unique fingerprint for her. This
20994 release fixes components #1 and #2, which is enough to block the attack;
20995 the other two remain as open research problems. Special thanks to
20996 "frosty_un" for reporting the issue to us!
20998 Clients should upgrade so they are no longer recognizable by the TLS
20999 certs they present. Relays should upgrade so they no longer allow a
21000 remote attacker to probe them to test whether unpatched clients are
21001 currently connected to them.
21003 This release also fixes several vulnerabilities that allow an attacker
21004 to enumerate bridge relays. Some bridge enumeration attacks still
21005 remain; see for example proposal 188.
21007 o Privacy/anonymity fixes (clients):
21008 - Clients and bridges no longer send TLS certificate chains on
21009 outgoing OR connections. Previously, each client or bridge would
21010 use the same cert chain for all outgoing OR connections until
21011 its IP address changes, which allowed any relay that the client
21012 or bridge contacted to determine which entry guards it is using.
21013 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
21014 - If a relay receives a CREATE_FAST cell on a TLS connection, it
21015 no longer considers that connection as suitable for satisfying a
21016 circuit EXTEND request. Now relays can protect clients from the
21017 CVE-2011-2768 issue even if the clients haven't upgraded yet.
21018 - Directory authorities no longer assign the Guard flag to relays
21019 that haven't upgraded to the above "refuse EXTEND requests
21020 to client connections" fix. Now directory authorities can
21021 protect clients from the CVE-2011-2768 issue even if neither
21022 the clients nor the relays have upgraded yet. There's a new
21023 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
21024 to let us transition smoothly, else tomorrow there would be no
21027 o Privacy/anonymity fixes (bridge enumeration):
21028 - Bridge relays now do their directory fetches inside Tor TLS
21029 connections, like all the other clients do, rather than connecting
21030 directly to the DirPort like public relays do. Removes another
21031 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
21032 - Bridges relays now build circuits for themselves in a more similar
21033 way to how clients build them. Removes another avenue for
21034 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
21035 when bridges were introduced.
21036 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
21037 that they initiated. Relays could distinguish incoming bridge
21038 connections from client connections, creating another avenue for
21039 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
21040 Found by "frosty_un".
21043 - Fix a crash bug when changing node restrictions while a DNS lookup
21044 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
21046 - Don't launch a useless circuit after failing to use one of a
21047 hidden service's introduction points. Previously, we would
21048 launch a new introduction circuit, but not set the hidden service
21049 which that circuit was intended to connect to, so it would never
21050 actually be used. A different piece of code would then create a
21051 new introduction circuit correctly. Bug reported by katmagic and
21052 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
21055 - Change an integer overflow check in the OpenBSD_Malloc code so
21056 that GCC is less likely to eliminate it as impossible. Patch
21057 from Mansour Moufid. Fixes bug 4059.
21058 - When a hidden service turns an extra service-side introduction
21059 circuit into a general-purpose circuit, free the rend_data and
21060 intro_key fields first, so we won't leak memory if the circuit
21061 is cannibalized for use as another service-side introduction
21062 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
21063 - Bridges now skip DNS self-tests, to act a little more stealthily.
21064 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
21065 bridges. Patch by "warms0x".
21066 - Fix internal bug-checking logic that was supposed to catch
21067 failures in digest generation so that it will fail more robustly
21068 if we ask for a nonexistent algorithm. Found by Coverity Scan.
21069 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
21070 - Report any failure in init_keys() calls launched because our
21071 IP address has changed. Spotted by Coverity Scan. Bugfix on
21072 0.1.1.4-alpha; fixes CID 484.
21074 o Minor bugfixes (log messages and documentation):
21075 - Remove a confusing dollar sign from the example fingerprint in the
21076 man page, and also make the example fingerprint a valid one. Fixes
21077 bug 4309; bugfix on 0.2.1.3-alpha.
21078 - The next version of Windows will be called Windows 8, and it has
21079 a major version of 6, minor version of 2. Correctly identify that
21080 version instead of calling it "Very recent version". Resolves
21081 ticket 4153; reported by funkstar.
21082 - Downgrade log messages about circuit timeout calibration from
21083 "notice" to "info": they don't require or suggest any human
21084 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21085 bugfix on 0.2.2.14-alpha.
21088 - Turn on directory request statistics by default and include them in
21089 extra-info descriptors. Don't break if we have no GeoIP database.
21090 Backported from 0.2.3.1-alpha; implements ticket 3951.
21091 - Update to the October 4 2011 Maxmind GeoLite Country database.
21094 Changes in version 0.2.1.31 - 2011-10-26
21095 Tor 0.2.1.31 backports important security and privacy fixes for
21096 oldstable. This release is intended only for package maintainers and
21097 others who cannot use the 0.2.2 stable series. All others should be
21098 using Tor 0.2.2.x or newer.
21100 o Security fixes (also included in 0.2.2.x):
21101 - Replace all potentially sensitive memory comparison operations
21102 with versions whose runtime does not depend on the data being
21103 compared. This will help resist a class of attacks where an
21104 adversary can use variations in timing information to learn
21105 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21106 implementation by Robert Ransom based partially on code by DJB.)
21107 - Fix an assert in parsing router descriptors containing IPv6
21108 addresses. This one took down the directory authorities when
21109 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
21111 o Privacy/anonymity fixes (also included in 0.2.2.x):
21112 - Clients and bridges no longer send TLS certificate chains on
21113 outgoing OR connections. Previously, each client or bridge would
21114 use the same cert chain for all outgoing OR connections until
21115 its IP address changes, which allowed any relay that the client
21116 or bridge contacted to determine which entry guards it is using.
21117 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
21118 - If a relay receives a CREATE_FAST cell on a TLS connection, it
21119 no longer considers that connection as suitable for satisfying a
21120 circuit EXTEND request. Now relays can protect clients from the
21121 CVE-2011-2768 issue even if the clients haven't upgraded yet.
21122 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
21123 that they initiated. Relays could distinguish incoming bridge
21124 connections from client connections, creating another avenue for
21125 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
21126 Found by "frosty_un".
21127 - When receiving a hidden service descriptor, check that it is for
21128 the hidden service we wanted. Previously, Tor would store any
21129 hidden service descriptors that a directory gave it, whether it
21130 wanted them or not. This wouldn't have let an attacker impersonate
21131 a hidden service, but it did let directories pre-seed a client
21132 with descriptors that it didn't want. Bugfix on 0.0.6.
21133 - Avoid linkability based on cached hidden service descriptors: forget
21134 all hidden service descriptors cached as a client when processing a
21135 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
21136 - Make the bridge directory authority refuse to answer directory
21137 requests for "all" descriptors. It used to include bridge
21138 descriptors in its answer, which was a major information leak.
21139 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
21140 - Don't attach new streams to old rendezvous circuits after SIGNAL
21141 NEWNYM. Previously, we would keep using an existing rendezvous
21142 circuit if it remained open (i.e. if it were kept open by a
21143 long-lived stream, or if a new stream were attached to it before
21144 Tor could notice that it was old and no longer in use). Bugfix on
21145 0.1.1.15-rc; fixes bug 3375.
21147 o Minor bugfixes (also included in 0.2.2.x):
21148 - When we restart our relay, we might get a successful connection
21149 from the outside before we've started our reachability tests,
21150 triggering a warning: "ORPort found reachable, but I have no
21151 routerinfo yet. Failing to inform controller of success." This
21152 bug was harmless unless Tor is running under a controller
21153 like Vidalia, in which case the controller would never get a
21154 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
21156 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
21157 enabled. Fixes bug 1526.
21158 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21159 anything since 0.2.1.16-rc.
21160 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
21161 None of the cases where we did this before were wrong, but by making
21162 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
21163 - Fix a rare crash bug that could occur when a client was configured
21164 with a large number of bridges. Fixes bug 2629; bugfix on
21165 0.2.1.2-alpha. Bugfix by trac user "shitlei".
21166 - Correct the warning displayed when a rendezvous descriptor exceeds
21167 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
21169 - Fix an uncommon assertion failure when running with DNSPort under
21170 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
21171 - When warning about missing zlib development packages during compile,
21172 give the correct package names. Bugfix on 0.2.0.1-alpha.
21173 - Require that introduction point keys and onion keys have public
21174 exponent 65537. Bugfix on 0.2.0.10-alpha.
21175 - Do not crash when our configuration file becomes unreadable, for
21176 example due to a permissions change, between when we start up
21177 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
21179 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21181 - Always NUL-terminate the sun_path field of a sockaddr_un before
21182 passing it to the kernel. (Not a security issue: kernels are
21183 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21184 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21185 - Don't stack-allocate the list of supplementary GIDs when we're
21186 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21187 could take up to 256K, which is way too much stack. Found by
21188 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21190 o Minor bugfixes (only in 0.2.1.x):
21191 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
21192 rely on them. Bugfix on 0.2.1.30.
21193 - Use git revisions instead of svn revisions when generating our
21194 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
21196 o Minor features (also included in 0.2.2.x):
21197 - Adjust the expiration time on our SSL session certificates to
21198 better match SSL certs seen in the wild. Resolves ticket 4014.
21199 - Allow nameservers with IPv6 address. Resolves bug 2574.
21200 - Update to the October 4 2011 Maxmind GeoLite Country database.
21203 Changes in version 0.2.3.5-alpha - 2011-09-28
21204 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
21205 bridge relays; fixes an assertion error that many users started hitting
21206 today; and adds the ability to refill token buckets more often than
21207 once per second, allowing significant performance improvements.
21210 - Bridge relays now do their directory fetches inside Tor TLS
21211 connections, like all the other clients do, rather than connecting
21212 directly to the DirPort like public relays do. Removes another
21213 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
21214 - Bridges relays now build circuits for themselves in a more similar
21215 way to how clients build them. Removes another avenue for
21216 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
21217 when bridges were introduced.
21220 - Fix an "Assertion md->held_by_node == 1 failed" error that could
21221 occur when the same microdescriptor was referenced by two node_t
21222 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
21224 o Major features (networking):
21225 - Add a new TokenBucketRefillInterval option to refill token buckets
21226 more frequently than once per second. This should improve network
21227 performance, alleviate queueing problems, and make traffic less
21228 bursty. Implements proposal 183; closes ticket 3630. Design by
21229 Florian Tschorsch and Björn Scheuermann; implementation by
21233 - Change an integer overflow check in the OpenBSD_Malloc code so
21234 that GCC is less likely to eliminate it as impossible. Patch
21235 from Mansour Moufid. Fixes bug 4059.
21237 o Minor bugfixes (usability):
21238 - Downgrade log messages about circuit timeout calibration from
21239 "notice" to "info": they don't require or suggest any human
21240 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
21241 bugfix on 0.2.2.14-alpha.
21243 o Minor features (diagnostics):
21244 - When the system call to create a listener socket fails, log the
21245 error message explaining why. This may help diagnose bug 4027.
21248 Changes in version 0.2.3.4-alpha - 2011-09-13
21249 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
21250 tweak to Tor's TLS handshake that makes relays and bridges that run
21251 this new version reachable from Iran again. It also fixes a few new
21252 bugs in 0.2.3.x, and teaches relays to recognize when they're not
21253 listed in the network consensus and republish.
21255 o Major bugfixes (also part of 0.2.2.33):
21256 - Avoid an assertion failure when reloading a configuration with
21257 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21258 3923; bugfix on 0.2.2.25-alpha.
21260 o Minor features (security, also part of 0.2.2.33):
21261 - Check for replays of the public-key encrypted portion of an
21262 INTRODUCE1 cell, in addition to the current check for replays of
21263 the g^x value. This prevents a possible class of active attacks
21264 by an attacker who controls both an introduction point and a
21265 rendezvous point, and who uses the malleability of AES-CTR to
21266 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21267 that these attacks are infeasible (requiring the attacker to send
21268 on the order of zettabytes of altered cells in a short interval),
21269 but we'd rather block them off in case there are any classes of
21270 this attack that we missed. Reported by Willem Pinckaers.
21272 o Minor features (also part of 0.2.2.33):
21273 - Adjust the expiration time on our SSL session certificates to
21274 better match SSL certs seen in the wild. Resolves ticket 4014.
21275 - Change the default required uptime for a relay to be accepted as
21276 a HSDir (hidden service directory) from 24 hours to 25 hours.
21277 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21278 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21279 authorities to abstain from voting on assignment of the HSDir
21280 consensus flag. Related to bug 2649.
21281 - Update to the September 6 2011 Maxmind GeoLite Country database.
21283 o Minor bugfixes (also part of 0.2.2.33):
21284 - Demote the 'replay detected' log message emitted when a hidden
21285 service receives the same Diffie-Hellman public key in two different
21286 INTRODUCE2 cells to info level. A normal Tor client can cause that
21287 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21288 fixes part of bug 2442.
21289 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21290 level. There is nothing that a hidden service's operator can do
21291 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21293 - Clarify a log message specifying the characters permitted in
21294 HiddenServiceAuthorizeClient client names. Previously, the log
21295 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21296 given the impression that every ASCII character between "+" and "_"
21297 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21299 o Build fixes (also part of 0.2.2.33):
21300 - Clean up some code issues that prevented Tor from building on older
21301 BSDs. Fixes bug 3894; reported by "grarpamp".
21302 - Search for a platform-specific version of "ar" when cross-compiling.
21303 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21306 - Fix a bug where the SocksPort option (for example) would get
21307 ignored and replaced by the default if a SocksListenAddress
21308 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
21312 - Relays now try regenerating and uploading their descriptor more
21313 frequently if they are not listed in the consensus, or if the
21314 version of their descriptor listed in the consensus is too
21315 old. This fix should prevent situations where a server declines
21316 to re-publish itself because it has done so too recently, even
21317 though the authorities decided not to list its recent-enough
21318 descriptor. Fix for bug 3327.
21321 - Relays now include a reason for regenerating their descriptors
21322 in an HTTP header when uploading to the authorities. This will
21323 make it easier to debug descriptor-upload issues in the future.
21324 - When starting as root and then changing our UID via the User
21325 control option, and we have a ControlSocket configured, make sure
21326 that the ControlSocket is owned by the same account that Tor will
21327 run under. Implements ticket 3421; fix by Jérémy Bobbio.
21330 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
21331 utility function used in the control-port code). This shouldn't
21332 ever happen unless Tor is completely out of memory, but if it did
21333 happen and Tor somehow recovered from it, Tor could have sent a log
21334 message to a control port in the middle of a reply to a controller
21335 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
21336 - Make 'FetchUselessDescriptors' cause all descriptor types and
21337 all consensus types (including microdescriptors) to get fetched.
21338 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
21340 o Code refactoring:
21341 - Make a new "entry connection" struct as an internal subtype of "edge
21342 connection", to simplify the code and make exit connections smaller.
21345 Changes in version 0.2.2.33 - 2011-09-13
21346 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
21347 TLS handshake that makes relays and bridges that run this new version
21348 reachable from Iran again.
21351 - Avoid an assertion failure when reloading a configuration with
21352 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
21353 3923; bugfix on 0.2.2.25-alpha.
21355 o Minor features (security):
21356 - Check for replays of the public-key encrypted portion of an
21357 INTRODUCE1 cell, in addition to the current check for replays of
21358 the g^x value. This prevents a possible class of active attacks
21359 by an attacker who controls both an introduction point and a
21360 rendezvous point, and who uses the malleability of AES-CTR to
21361 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
21362 that these attacks are infeasible (requiring the attacker to send
21363 on the order of zettabytes of altered cells in a short interval),
21364 but we'd rather block them off in case there are any classes of
21365 this attack that we missed. Reported by Willem Pinckaers.
21368 - Adjust the expiration time on our SSL session certificates to
21369 better match SSL certs seen in the wild. Resolves ticket 4014.
21370 - Change the default required uptime for a relay to be accepted as
21371 a HSDir (hidden service directory) from 24 hours to 25 hours.
21372 Improves on 0.2.0.10-alpha; resolves ticket 2649.
21373 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
21374 authorities to abstain from voting on assignment of the HSDir
21375 consensus flag. Related to bug 2649.
21376 - Update to the September 6 2011 Maxmind GeoLite Country database.
21378 o Minor bugfixes (documentation and log messages):
21379 - Correct the man page to explain that HashedControlPassword and
21380 CookieAuthentication can both be set, in which case either method
21381 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21382 when we decided to allow these config options to both be set. Issue
21383 raised by bug 3898.
21384 - Demote the 'replay detected' log message emitted when a hidden
21385 service receives the same Diffie-Hellman public key in two different
21386 INTRODUCE2 cells to info level. A normal Tor client can cause that
21387 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
21388 fixes part of bug 2442.
21389 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
21390 level. There is nothing that a hidden service's operator can do
21391 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
21393 - Clarify a log message specifying the characters permitted in
21394 HiddenServiceAuthorizeClient client names. Previously, the log
21395 message said that "[A-Za-z0-9+-_]" were permitted; that could have
21396 given the impression that every ASCII character between "+" and "_"
21397 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
21400 - Provide a substitute implementation of lround() for MSVC, which
21401 apparently lacks it. Patch from Gisle Vanem.
21402 - Clean up some code issues that prevented Tor from building on older
21403 BSDs. Fixes bug 3894; reported by "grarpamp".
21404 - Search for a platform-specific version of "ar" when cross-compiling.
21405 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
21408 Changes in version 0.2.3.3-alpha - 2011-09-01
21409 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
21410 security, and provides client-side support for the microdescriptor
21411 and optimistic data features introduced earlier in the 0.2.3.x
21412 series. It also includes numerous critical bugfixes in the (optional)
21413 bufferevent-based networking backend.
21415 o Major features (stream isolation):
21416 - You can now configure Tor so that streams from different
21417 applications are isolated on different circuits, to prevent an
21418 attacker who sees your streams as they leave an exit node from
21419 linking your sessions to one another. To do this, choose some way
21420 to distinguish the applications: have them connect to different
21421 SocksPorts, or have one of them use SOCKS4 while the other uses
21422 SOCKS5, or have them pass different authentication strings to the
21423 SOCKS proxy. Then, use the new SocksPort syntax to configure the
21424 degree of isolation you need. This implements Proposal 171.
21425 - There's a new syntax for specifying multiple client ports (such as
21426 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
21427 multiple *Port entries with full addr:port syntax on each.
21428 The old *ListenAddress format is still supported, but you can't
21429 mix it with the new *Port syntax.
21431 o Major features (other):
21432 - Enable microdescriptor fetching by default for clients. This allows
21433 clients to download a much smaller amount of directory information.
21434 To disable it (and go back to the old-style consensus and
21435 descriptors), set "UseMicrodescriptors 0" in your torrc file.
21436 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
21437 "PortForwarding" config option), now supports Windows.
21438 - When using an exit relay running 0.2.3.x, clients can now
21439 "optimistically" send data before the exit relay reports that
21440 the stream has opened. This saves a round trip when starting
21441 connections where the client speaks first (such as web browsing).
21442 This behavior is controlled by a consensus parameter (currently
21443 disabled). To turn it on or off manually, use the "OptimisticData"
21444 torrc option. Implements proposal 181; code by Ian Goldberg.
21446 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
21447 - When using IOCP on Windows, we need to enable Libevent windows
21449 - The IOCP backend now works even when the user has not specified
21450 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
21451 Fixes part of bug 3752.
21452 - Correctly record the bytes we've read and written when using
21453 bufferevents, so that we can include them in our bandwidth history
21454 and advertised bandwidth. Fixes bug 3803.
21455 - Apply rate-limiting only at the bottom of a chain of filtering
21456 bufferevents. This prevents us from filling up internal read
21457 buffers and violating rate-limits when filtering bufferevents
21458 are enabled. Fixes part of bug 3804.
21459 - Add high-watermarks to the output buffers for filtered
21460 bufferevents. This prevents us from filling up internal write
21461 buffers and wasting CPU cycles when filtering bufferevents are
21462 enabled. Fixes part of bug 3804.
21463 - Correctly notice when data has been written from a bufferevent
21464 without flushing it completely. Fixes bug 3805.
21465 - Fix a bug where server-side tunneled bufferevent-based directory
21466 streams would get closed prematurely. Fixes bug 3814.
21467 - Fix a use-after-free error with per-connection rate-limiting
21468 buckets. Fixes bug 3888.
21470 o Major bugfixes (also part of 0.2.2.31-rc):
21471 - If we're configured to write our ControlPorts to disk, only write
21472 them after switching UID and creating the data directory. This way,
21473 we don't fail when starting up with a nonexistent DataDirectory
21474 and a ControlPortWriteToFile setting based on that directory. Fixes
21475 bug 3747; bugfix on Tor 0.2.2.26-beta.
21478 - Added a new CONF_CHANGED event so that controllers can be notified
21479 of any configuration changes made by other controllers, or by the
21480 user. Implements ticket 1692.
21481 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
21482 leak when using bufferevents, and lets Libevent worry about how to
21483 best copy data out of a buffer.
21484 - Replace files in stats/ rather than appending to them. Now that we
21485 include statistics in extra-info descriptors, it makes no sense to
21486 keep old statistics forever. Implements ticket 2930.
21488 o Minor features (build compatibility):
21489 - Limited, experimental support for building with nmake and MSVC.
21490 - Provide a substitute implementation of lround() for MSVC, which
21491 apparently lacks it. Patch from Gisle Vanem.
21493 o Minor features (also part of 0.2.2.31-rc):
21494 - Update to the August 2 2011 Maxmind GeoLite Country database.
21496 o Minor bugfixes (on 0.2.3.x-alpha):
21497 - Fix a spurious warning when parsing SOCKS requests with
21498 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
21499 - Get rid of a harmless warning that could happen on relays running
21500 with bufferevents. The warning was caused by someone doing an http
21501 request to a relay's orport. Also don't warn for a few related
21502 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
21504 o Minor bugfixes (on 2.2.x and earlier):
21505 - Correct the man page to explain that HashedControlPassword and
21506 CookieAuthentication can both be set, in which case either method
21507 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
21508 when we decided to allow these config options to both be set. Issue
21509 raised by bug 3898.
21510 - The "--quiet" and "--hush" options now apply not only to Tor's
21511 behavior before logs are configured, but also to Tor's behavior in
21512 the absence of configured logs. Fixes bug 3550; bugfix on
21515 o Minor bugfixes (also part of 0.2.2.31-rc):
21516 - Write several files in text mode, on OSes that distinguish text
21517 mode from binary mode (namely, Windows). These files are:
21518 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21519 that collect those statistics; 'client_keys' and 'hostname' for
21520 hidden services that use authentication; and (in the tor-gencert
21521 utility) newly generated identity and signing keys. Previously,
21522 we wouldn't specify text mode or binary mode, leading to an
21523 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21524 the DirRecordUsageByCountry option which would have triggered
21525 the assertion failure was added), although this assertion failure
21526 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21527 - Selectively disable deprecation warnings on OS X because Lion
21528 started deprecating the shipped copy of openssl. Fixes bug 3643.
21529 - Remove an extra pair of quotation marks around the error
21530 message in control-port STATUS_GENERAL BUG events. Bugfix on
21531 0.1.2.6-alpha; fixes bug 3732.
21532 - When unable to format an address as a string, report its value
21533 as "???" rather than reusing the last formatted address. Bugfix
21536 o Code simplifications and refactoring:
21537 - Rewrite the listener-selection logic so that parsing which ports
21538 we want to listen on is now separate from binding to the ports
21542 - Building Tor with bufferevent support now requires Libevent
21543 2.0.13-stable or later. Previous versions of Libevent had bugs in
21544 SSL-related bufferevents and related issues that would make Tor
21545 work badly with bufferevents. Requiring 2.0.13-stable also allows
21546 Tor with bufferevents to take advantage of Libevent APIs
21547 introduced after 2.0.8-rc.
21550 Changes in version 0.2.2.32 - 2011-08-27
21551 The Tor 0.2.2 release series is dedicated to the memory of Andreas
21552 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
21553 a founder of the PETS community, a leader in our field, a mentor,
21554 and a friend. He left us with these words: "I had the possibility
21555 to contribute to this world that is not as it should be. I hope I
21556 could help in some areas to make the world a better place, and that
21557 I could also encourage other people to be engaged in improving the
21558 world. Please, stay engaged. This world needs you, your love, your
21559 initiative -- now I cannot be part of that anymore."
21561 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
21562 ready. More than two years in the making, this release features improved
21563 client performance and hidden service reliability, better compatibility
21564 for Android, correct behavior for bridges that listen on more than
21565 one address, more extensible and flexible directory object handling,
21566 better reporting of network statistics, improved code security, and
21567 many many other features and bugfixes.
21570 Changes in version 0.2.2.31-rc - 2011-08-17
21571 Tor 0.2.2.31-rc is the second and hopefully final release candidate
21572 for the Tor 0.2.2.x series.
21575 - Remove an extra pair of quotation marks around the error
21576 message in control-port STATUS_GENERAL BUG events. Bugfix on
21577 0.1.2.6-alpha; fixes bug 3732.
21578 - If we're configured to write our ControlPorts to disk, only write
21579 them after switching UID and creating the data directory. This way,
21580 we don't fail when starting up with a nonexistent DataDirectory
21581 and a ControlPortWriteToFile setting based on that directory. Fixes
21582 bug 3747; bugfix on Tor 0.2.2.26-beta.
21585 - Update to the August 2 2011 Maxmind GeoLite Country database.
21588 - Allow GETINFO fingerprint to return a fingerprint even when
21589 we have not yet built a router descriptor. Fixes bug 3577;
21590 bugfix on 0.2.0.1-alpha.
21591 - Write several files in text mode, on OSes that distinguish text
21592 mode from binary mode (namely, Windows). These files are:
21593 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
21594 that collect those statistics; 'client_keys' and 'hostname' for
21595 hidden services that use authentication; and (in the tor-gencert
21596 utility) newly generated identity and signing keys. Previously,
21597 we wouldn't specify text mode or binary mode, leading to an
21598 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
21599 the DirRecordUsageByCountry option which would have triggered
21600 the assertion failure was added), although this assertion failure
21601 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
21602 - Selectively disable deprecation warnings on OS X because Lion
21603 started deprecating the shipped copy of openssl. Fixes bug 3643.
21604 - When unable to format an address as a string, report its value
21605 as "???" rather than reusing the last formatted address. Bugfix
21609 Changes in version 0.2.3.2-alpha - 2011-07-18
21610 Tor 0.2.3.2-alpha introduces two new experimental features:
21611 microdescriptors and pluggable transports. It also continues cleaning
21612 up a variety of recently introduced features.
21615 - Clients can now use microdescriptors instead of regular descriptors
21616 to build circuits. Microdescriptors are authority-generated
21617 summaries of regular descriptors' contents, designed to change
21618 very rarely (see proposal 158 for details). This feature is
21619 designed to save bandwidth, especially for clients on slow internet
21620 connections. It's off by default for now, since nearly no caches
21621 support it, but it will be on-by-default for clients in a future
21622 version. You can use the UseMicrodescriptors option to turn it on.
21623 - Tor clients using bridges can now be configured to use a separate
21624 'transport' proxy for each bridge. This approach helps to resist
21625 censorship by allowing bridges to use protocol obfuscation
21626 plugins. It implements part of proposal 180. Implements ticket 2841.
21627 - While we're trying to bootstrap, record how many TLS connections
21628 fail in each state, and report which states saw the most failures
21629 in response to any bootstrap failures. This feature may speed up
21630 diagnosis of censorship events. Implements ticket 3116.
21632 o Major bugfixes (on 0.2.3.1-alpha):
21633 - When configuring a large set of nodes in EntryNodes (as with
21634 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
21635 random subset to be guards, and choose them in random
21636 order. Fixes bug 2798.
21637 - Tor could crash when remembering a consensus in a non-used consensus
21638 flavor without having a current consensus set. Fixes bug 3361.
21639 - Comparing an unknown address to a microdescriptor's shortened exit
21640 policy would always give a "rejected" result. Fixes bug 3599.
21641 - Using microdescriptors as a client no longer prevents Tor from
21642 uploading and downloading hidden service descriptors. Fixes
21646 - Allow nameservers with IPv6 address. Resolves bug 2574.
21647 - Accept attempts to include a password authenticator in the
21648 handshake, as supported by SOCKS5. This handles SOCKS clients that
21649 don't know how to omit a password when authenticating. Resolves
21651 - When configuring a large set of nodes in EntryNodes, and there are
21652 enough of them listed as Guard so that we don't need to consider
21653 the non-guard entries, prefer the ones listed with the Guard flag.
21654 - Check for and recover from inconsistency in the microdescriptor
21655 cache. This will make it harder for us to accidentally free a
21656 microdescriptor without removing it from the appropriate data
21657 structures. Fixes issue 3135; issue noted by "wanoskarnet".
21658 - Log SSL state transitions at log level DEBUG, log domain
21659 HANDSHAKE. This can be useful for debugging censorship events.
21660 Implements ticket 3264.
21661 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
21662 implements ticket 3439.
21664 o Minor bugfixes (on 0.2.3.1-alpha):
21665 - Do not free all general-purpose regular descriptors just
21666 because microdescriptor use is enabled. Fixes bug 3113.
21667 - Correctly link libevent_openssl when --enable-static-libevent
21668 is passed to configure. Fixes bug 3118.
21669 - Bridges should not complain during their heartbeat log messages that
21670 they are unlisted in the consensus: that's more or less the point
21671 of being a bridge. Fixes bug 3183.
21672 - Report a SIGNAL event to controllers when acting on a delayed
21673 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
21674 event to the controller if we acted on a SIGNAL NEWNYM command
21675 immediately, and otherwise not report a SIGNAL event for the
21676 command at all. Fixes bug 3349.
21677 - Fix a crash when handling the SIGNAL controller command or
21678 reporting ERR-level status events with bufferevents enabled. Found
21679 by Robert Ransom. Fixes bug 3367.
21680 - Always ship the tor-fw-helper manpage in our release tarballs.
21681 Fixes bug 3389. Reported by Stephen Walker.
21682 - Fix a class of double-mark-for-close bugs when bufferevents
21683 are enabled. Fixes bug 3403.
21684 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
21685 - Add SIGNAL to the list returned by the 'GETINFO events/names'
21686 control-port command. Fixes part of bug 3465.
21687 - Prevent using negative indices during unit test runs when read_all()
21688 fails. Spotted by coverity.
21689 - Fix a rare memory leak when checking the nodelist without it being
21690 present. Found by coverity.
21691 - Only try to download a microdescriptor-flavored consensus from
21692 a directory cache that provides them.
21694 o Minor bugfixes (on 0.2.2.x and earlier):
21695 - Assert that hidden-service-related operations are not performed
21696 using single-hop circuits. Previously, Tor would assert that
21697 client-side streams are not attached to single-hop circuits,
21698 but not that other sensitive operations on the client and service
21699 side are not performed using single-hop circuits. Fixes bug 3332;
21701 - Don't publish a new relay descriptor when we reload our onion key,
21702 unless the onion key has actually changed. Fixes bug 3263 and
21703 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
21704 - Allow GETINFO fingerprint to return a fingerprint even when
21705 we have not yet built a router descriptor. Fixes bug 3577;
21706 bugfix on 0.2.0.1-alpha.
21707 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
21708 on 0.2.2.4-alpha; fixes bug 3427.
21710 o Code simplification and refactoring:
21711 - Use tor_sscanf() in place of scanf() in more places through the
21712 code. This makes us a little more locale-independent, and
21713 should help shut up code-analysis tools that can't tell
21714 a safe sscanf string from a dangerous one.
21715 - Use tt_assert(), not tor_assert(), for checking for test failures.
21716 This makes the unit tests more able to go on in the event that
21718 - Split connection_about_to_close() into separate functions for each
21722 - On Windows, we now define the _WIN32_WINNT macros only if they
21723 are not already defined. This lets the person building Tor decide,
21724 if they want, to require a later version of Windows.
21727 Changes in version 0.2.2.30-rc - 2011-07-07
21728 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
21729 series. It fixes a few smaller bugs, but generally appears stable.
21730 Please test it and let us know whether it is!
21733 - Send a SUCCEEDED stream event to the controller when a reverse
21734 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
21735 discovered by katmagic.
21736 - Always NUL-terminate the sun_path field of a sockaddr_un before
21737 passing it to the kernel. (Not a security issue: kernels are
21738 smart enough to reject bad sockaddr_uns.) Found by Coverity;
21739 CID #428. Bugfix on Tor 0.2.0.3-alpha.
21740 - Don't stack-allocate the list of supplementary GIDs when we're
21741 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
21742 could take up to 256K, which is way too much stack. Found by
21743 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
21744 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
21745 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
21746 fixes part of bug 3465.
21747 - Fix a memory leak when receiving a descriptor for a hidden
21748 service we didn't ask for. Found by Coverity; CID #30. Bugfix
21752 - Update to the July 1 2011 Maxmind GeoLite Country database.
21755 Changes in version 0.2.2.29-beta - 2011-06-20
21756 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
21757 have bridge lines in their torrc but don't want to use them; gets
21758 us closer to having the control socket feature working on Debian;
21759 and fixes a variety of smaller bugs.
21762 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
21763 When we changed the default behavior to "use bridges if any
21764 are listed in the torrc", we surprised users who had bridges
21765 in their torrc files but who didn't actually want to use them.
21766 Partial resolution for bug 3354.
21769 - Don't attach new streams to old rendezvous circuits after SIGNAL
21770 NEWNYM. Previously, we would keep using an existing rendezvous
21771 circuit if it remained open (i.e. if it were kept open by a
21772 long-lived stream, or if a new stream were attached to it before
21773 Tor could notice that it was old and no longer in use). Bugfix on
21774 0.1.1.15-rc; fixes bug 3375.
21777 - Fix a bug when using ControlSocketsGroupWritable with User. The
21778 directory's group would be checked against the current group, not
21779 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
21780 bugfix on 0.2.2.26-beta.
21781 - Make connection_printf_to_buf()'s behavior sane. Its callers
21782 expect it to emit a CRLF iff the format string ends with CRLF;
21783 it actually emitted a CRLF iff (a) the format string ended with
21784 CRLF or (b) the resulting string was over 1023 characters long or
21785 (c) the format string did not end with CRLF *and* the resulting
21786 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
21787 fixes part of bug 3407.
21788 - Make send_control_event_impl()'s behavior sane. Its callers
21789 expect it to always emit a CRLF at the end of the string; it
21790 might have emitted extra control characters as well. Bugfix on
21791 0.1.1.9-alpha; fixes another part of bug 3407.
21792 - Make crypto_rand_int() check the value of its input correctly.
21793 Previously, it accepted values up to UINT_MAX, but could return a
21794 negative number if given a value above INT_MAX+1. Found by George
21795 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
21796 - Avoid a segfault when reading a malformed circuit build state
21797 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
21799 - When asked about a DNS record type we don't support via a
21800 client DNSPort, reply with NOTIMPL rather than an empty
21801 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
21802 - Fix a rare memory leak during stats writing. Found by coverity.
21805 - Update to the June 1 2011 Maxmind GeoLite Country database.
21807 o Code simplifications and refactoring:
21808 - Remove some dead code as indicated by coverity.
21809 - Remove a few dead assignments during router parsing. Found by
21811 - Add some forgotten return value checks during unit tests. Found
21813 - Don't use 1-bit wide signed bit fields. Found by coverity.
21816 Changes in version 0.2.2.28-beta - 2011-06-04
21817 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
21818 fixed a big bug in whether relays stay in the consensus consistently,
21819 we moved closer to handling bridges and hidden services correctly,
21820 and we started the process of better handling the dreaded "my Vidalia
21821 died, and now my Tor demands a password when I try to reconnect to it"
21825 - Don't decide to make a new descriptor when receiving a HUP signal.
21826 This bug has caused a lot of 0.2.2.x relays to disappear from the
21827 consensus periodically. Fixes the most common case of triggering
21828 bug 1810; bugfix on 0.2.2.7-alpha.
21829 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
21830 - Don't try to build descriptors if "ORPort auto" is set and we
21831 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
21833 - Resolve a crash that occurred when setting BridgeRelay to 1 with
21834 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
21835 - Apply circuit timeouts to opened hidden-service-related circuits
21836 based on the correct start time. Previously, we would apply the
21837 circuit build timeout based on time since the circuit's creation;
21838 it was supposed to be applied based on time since the circuit
21839 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
21840 - Use the same circuit timeout for client-side introduction
21841 circuits as for other four-hop circuits, rather than the timeout
21842 for single-hop directory-fetch circuits; the shorter timeout may
21843 have been appropriate with the static circuit build timeout in
21844 0.2.1.x and earlier, but caused many hidden service access attempts
21845 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
21846 on 0.2.2.2-alpha; fixes another part of bug 1297.
21847 - In ticket 2511 we fixed a case where you could use an unconfigured
21848 bridge if you had configured it as a bridge the last time you ran
21849 Tor. Now fix another edge case: if you had configured it as a bridge
21850 but then switched to a different bridge via the controller, you
21851 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
21855 - Add an __OwningControllerProcess configuration option and a
21856 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
21857 that when it exits, Tor will shut down. Implements feature 3049.
21858 - If "UseBridges 1" is set and no bridges are configured, Tor will
21859 now refuse to build any circuits until some bridges are set.
21860 If "UseBridges auto" is set, Tor will use bridges if they are
21861 configured and we are not running as a server, but otherwise will
21862 make circuits as usual. The new default is "auto". Patch by anonym,
21863 so the Tails LiveCD can stop automatically revealing you as a Tor
21867 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
21868 - Remove a trailing asterisk from "exit-policy/default" in the
21869 output of the control port command "GETINFO info/names". Bugfix
21871 - Use a wide type to hold sockets when built for 64-bit Windows builds.
21873 - Warn when the user configures two HiddenServiceDir lines that point
21874 to the same directory. Bugfix on 0.0.6 (the version introducing
21875 HiddenServiceDir); fixes bug 3289.
21876 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
21877 part of bug 2748; bugfix on 0.2.0.10-alpha.
21878 - Log malformed requests for rendezvous descriptors as protocol
21879 warnings, not warnings. Also, use a more informative log message
21880 in case someone sees it at log level warning without prior
21881 info-level messages. Fixes the other part of bug 2748; bugfix
21883 - Clear the table recording the time of the last request for each
21884 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
21885 Previously, we would clear our HS descriptor cache on SIGNAL
21886 NEWNYM, but if we had previously retrieved a descriptor (or tried
21887 to) from every directory responsible for it, we would refuse to
21888 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
21890 - Fix a log message that said "bits" while displaying a value in
21891 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
21893 - When checking for 1024-bit keys, check for 1024 bits, not 128
21894 bytes. This allows Tor to correctly discard keys of length 1017
21895 through 1023. Bugfix on 0.0.9pre5.
21898 - Relays now log the reason for publishing a new relay descriptor,
21899 so we have a better chance of hunting down instances of bug 1810.
21900 Resolves ticket 3252.
21901 - Revise most log messages that refer to nodes by nickname to
21902 instead use the "$key=nickname at address" format. This should be
21903 more useful, especially since nicknames are less and less likely
21904 to be unique. Resolves ticket 3045.
21905 - Log (at info level) when purging pieces of hidden-service-client
21906 state because of SIGNAL NEWNYM.
21909 - Remove undocumented option "-F" from tor-resolve: it hasn't done
21910 anything since 0.2.1.16-rc.
21913 Changes in version 0.2.2.27-beta - 2011-05-18
21914 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
21915 release, and also adds a few more general bugfixes.
21918 - Fix a crash bug when changing bridges in a running Tor process.
21919 Fixes bug 3213; bugfix on 0.2.2.26-beta.
21920 - When the controller configures a new bridge, don't wait 10 to 60
21921 seconds before trying to fetch its descriptor. Bugfix on
21922 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
21925 - Require that onion keys have exponent 65537 in microdescriptors too.
21926 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
21927 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
21928 Changed the limit to 512 characters by removing base64 newlines.
21929 Fixes bug 2752. Fix by Michael Yakubovich.
21930 - When a client starts or stops using bridges, never use a circuit
21931 that was built before the configuration change. This behavior could
21932 put at risk a user who uses bridges to ensure that her traffic
21933 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
21937 Changes in version 0.2.2.26-beta - 2011-05-17
21938 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
21939 also introduces a new "socksport auto" approach that should make it
21940 easier to run multiple Tors on the same system, and does a lot of
21941 cleanup to get us closer to a release candidate.
21943 o Security/privacy fixes:
21944 - Replace all potentially sensitive memory comparison operations
21945 with versions whose runtime does not depend on the data being
21946 compared. This will help resist a class of attacks where an
21947 adversary can use variations in timing information to learn
21948 sensitive data. Fix for one case of bug 3122. (Safe memcmp
21949 implementation by Robert Ransom based partially on code by DJB.)
21950 - When receiving a hidden service descriptor, check that it is for
21951 the hidden service we wanted. Previously, Tor would store any
21952 hidden service descriptors that a directory gave it, whether it
21953 wanted them or not. This wouldn't have let an attacker impersonate
21954 a hidden service, but it did let directories pre-seed a client
21955 with descriptors that it didn't want. Bugfix on 0.0.6.
21956 - On SIGHUP, do not clear out all TrackHostExits mappings, client
21957 DNS cache entries, and virtual address mappings: that's what
21958 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
21961 - The options SocksPort, ControlPort, and so on now all accept a
21962 value "auto" that opens a socket on an OS-selected port. A
21963 new ControlPortWriteToFile option tells Tor to write its
21964 actual control port or ports to a chosen file. If the option
21965 ControlPortFileGroupReadable is set, the file is created as
21966 group-readable. Now users can run two Tor clients on the same
21967 system without needing to manually mess with parameters. Resolves
21968 part of ticket 3076.
21969 - Set SO_REUSEADDR on all sockets, not just listeners. This should
21970 help busy exit nodes avoid running out of useable ports just
21971 because all the ports have been used in the near past. Resolves
21975 - New "GETINFO net/listeners/(type)" controller command to return
21976 a list of addresses and ports that are bound for listeners for a
21977 given connection type. This is useful when the user has configured
21978 "SocksPort auto" and the controller needs to know which port got
21979 chosen. Resolves another part of ticket 3076.
21980 - Add a new ControlSocketsGroupWritable configuration option: when
21981 it is turned on, ControlSockets are group-writeable by the default
21982 group of the current user. Patch by Jérémy Bobbio; implements
21984 - Tor now refuses to create a ControlSocket in a directory that is
21985 world-readable (or group-readable if ControlSocketsGroupWritable
21986 is 0). This is necessary because some operating systems do not
21987 enforce permissions on an AF_UNIX sockets. Permissions on the
21988 directory holding the socket, however, seems to work everywhere.
21989 - Rate-limit a warning about failures to download v2 networkstatus
21990 documents. Resolves part of bug 1352.
21991 - Backport code from 0.2.3.x that allows directory authorities to
21992 clean their microdescriptor caches. Needed to resolve bug 2230.
21993 - When an HTTPS proxy reports "403 Forbidden", we now explain
21994 what it means rather than calling it an unexpected status code.
21995 Closes bug 2503. Patch from Michael Yakubovich.
21996 - Update to the May 1 2011 Maxmind GeoLite Country database.
21999 - Authorities now clean their microdesc cache periodically and when
22000 reading from disk initially, not only when adding new descriptors.
22001 This prevents a bug where we could lose microdescriptors. Bugfix
22002 on 0.2.2.6-alpha. Fixes bug 2230.
22003 - Do not crash when our configuration file becomes unreadable, for
22004 example due to a permissions change, between when we start up
22005 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
22007 - Avoid a bug that would keep us from replacing a microdescriptor
22008 cache on Windows. (We would try to replace the file while still
22009 holding it open. That's fine on Unix, but Windows doesn't let us
22010 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
22011 - Add missing explanations for the authority-related torrc options
22012 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
22013 man page. Resolves issue 2379.
22014 - As an authority, do not upload our own vote or signature set to
22015 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
22016 it would get flagged as a duplicate. Resolves bug 3026.
22017 - Accept hidden service descriptors if we think we might be a hidden
22018 service directory, regardless of what our consensus says. This
22019 helps robustness, since clients and hidden services can sometimes
22020 have a more up-to-date view of the network consensus than we do,
22021 and if they think that the directory authorities list us a HSDir,
22022 we might actually be one. Related to bug 2732; bugfix on
22024 - When a controller changes TrackHostExits, remove mappings for
22025 hosts that should no longer have their exits tracked. Bugfix on
22027 - When a controller changes VirtualAddrNetwork, remove any mappings
22028 for hosts that were automapped to the old network. Bugfix on
22030 - When a controller changes one of the AutomapHosts* options, remove
22031 any mappings for hosts that should no longer be automapped. Bugfix
22033 - Do not reset the bridge descriptor download status every time we
22034 re-parse our configuration or get a configuration change. Fixes
22035 bug 3019; bugfix on 0.2.0.3-alpha.
22037 o Minor bugfixes (code cleanup):
22038 - When loading the microdesc journal, remember its current size.
22039 In 0.2.2, this helps prevent the microdesc journal from growing
22040 without limit on authorities (who are the only ones to use it in
22041 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
22042 Fix posted by "cypherpunks."
22043 - The microdesc journal is supposed to get rebuilt only if it is
22044 at least _half_ the length of the store, not _twice_ the length
22045 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
22046 - Fix a potential null-pointer dereference while computing a
22047 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
22049 - Avoid a possible null-pointer dereference when rebuilding the mdesc
22050 cache without actually having any descriptors to cache. Bugfix on
22051 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
22052 - If we fail to compute the identity digest of a v3 legacy keypair,
22053 warn, and don't use a buffer-full of junk instead. Bugfix on
22054 0.2.1.1-alpha; fixes bug 3106.
22055 - Resolve an untriggerable issue in smartlist_string_num_isin(),
22056 where if the function had ever in the future been used to check
22057 for the presence of a too-large number, it would have given an
22058 incorrect result. (Fortunately, we only used it for 16-bit
22059 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
22060 - Require that introduction point keys and onion handshake keys
22061 have a public exponent of 65537. Starts to fix bug 3207; bugfix
22064 o Removed features:
22065 - Caches no longer download and serve v2 networkstatus documents
22066 unless FetchV2Networkstatus flag is set: these documents haven't
22067 haven't been used by clients or relays since 0.2.0.x. Resolves
22071 Changes in version 0.2.3.1-alpha - 2011-05-05
22072 Tor 0.2.3.1-alpha adds some new experimental features, including support
22073 for an improved network IO backend, IOCP networking on Windows,
22074 microdescriptor caching, "fast-start" support for streams, and automatic
22075 home router configuration. There are also numerous internal improvements
22076 to try to make the code easier for developers to work with.
22078 This is the first alpha release in a new series, so expect there to be
22079 bugs. Users who would rather test out a more stable branch should
22080 stay with 0.2.2.x for now.
22083 - Tor can now optionally build with the "bufferevents" buffered IO
22084 backend provided by Libevent 2. To use this feature, make sure you
22085 have the latest possible version of Libevent, and pass the
22086 --enable-bufferevents flag to configure when building Tor from
22087 source. This feature will make our networking code more flexible,
22088 let us stack layers on each other, and let us use more efficient
22089 zero-copy transports where available.
22090 - As an experimental feature, Tor can use IOCP for networking on Windows.
22091 Once this code is tuned and optimized, it promises much better
22092 performance than the select-based backend we've used in the past. To
22093 try this feature, you must build Tor with Libevent 2, configure Tor
22094 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
22095 your torrc. There are known bugs here: only try this if you can help
22096 debug it as it breaks.
22097 - The EntryNodes option can now include country codes like {de} or IP
22098 addresses or network masks. Previously we had disallowed these options
22099 because we didn't have an efficient way to keep the list up to
22100 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
22101 - Exit nodes now accept and queue data on not-yet-connected streams.
22102 Previously, the client wasn't allowed to send data until the stream was
22103 connected, which slowed down all connections. This change will enable
22104 clients to perform a "fast-start" on streams and send data without
22105 having to wait for a confirmation that the stream has opened. (Patch
22106 from Ian Goldberg; implements the server side of Proposal 174.)
22107 - Tor now has initial support for automatic port mapping on the many
22108 home routers that support NAT-PMP or UPnP. (Not yet supported on
22109 Windows). To build the support code, you'll need to have libnatpnp
22110 library and/or the libminiupnpc library, and you'll need to enable the
22111 feature specifically by passing "--enable-upnp" and/or
22112 "--enable-natpnp" to configure. To turn it on, use the new
22113 PortForwarding option.
22114 - Caches now download, cache, and serve multiple "flavors" of the
22115 consensus, including a flavor that describes microdescriptors.
22116 - Caches now download, cache, and serve microdescriptors -- small
22117 summaries of router descriptors that are authenticated by all of the
22118 directory authorities. Once enough caches are running this code,
22119 clients will be able to save significant amounts of directory bandwidth
22120 by downloading microdescriptors instead of router descriptors.
22123 - Make logging resolution configurable with a new LogTimeGranularity
22124 option, and change the default from 1 millisecond to 1 second.
22125 Implements enhancement 1668.
22126 - We log which torrc file we're using on startup. Implements ticket
22128 - Ordinarily, Tor does not count traffic from private addresses (like
22129 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
22130 There is now a new option, CountPrivateBandwidth, to disable this
22131 behavior. Patch from Daniel Cagara.
22132 - New --enable-static-tor configure option for building Tor as
22133 statically as possible. Idea, general hackery and thoughts from
22134 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
22136 - If you set the NumCPUs option to 0, Tor will now try to detect how
22137 many CPUs you have. This is the new default behavior.
22138 - Turn on directory request statistics by default and include them in
22139 extra-info descriptors. Don't break if we have no GeoIP database.
22140 - Relays that set "ConnDirectionStatistics 1" write statistics on the
22141 bidirectional use of connections to disk every 24 hours.
22142 - Add a GeoIP file digest to the extra-info descriptor. Implements
22144 - The NodeFamily option -- which let you declare that you want to
22145 consider nodes to be part of a family whether they list themselves
22146 that way or not -- now allows IP address ranges and country codes.
22147 - Add a new 'Heartbeat' log message type to periodically log a message
22148 describing Tor's status at level Notice. This feature is meant for
22149 operators who log at notice, and want to make sure that their Tor
22150 server is still working. Implementation by George Kadianakis.
22152 o Minor bugfixes (on 0.2.2.25-alpha):
22153 - When loading the microdesc journal, remember its current size.
22154 In 0.2.2, this helps prevent the microdesc journal from growing
22155 without limit on authorities (who are the only ones to use it in
22156 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
22157 Fix posted by "cypherpunks."
22158 - The microdesc journal is supposed to get rebuilt only if it is
22159 at least _half_ the length of the store, not _twice_ the length
22160 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
22161 - If as an authority we fail to compute the identity digest of a v3
22162 legacy keypair, warn, and don't use a buffer-full of junk instead.
22163 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
22164 - Authorities now clean their microdesc cache periodically and when
22165 reading from disk initially, not only when adding new descriptors.
22166 This prevents a bug where we could lose microdescriptors. Bugfix
22169 o Minor features (controller):
22170 - Add a new SIGNAL event to the controller interface so that
22171 controllers can be notified when Tor handles a signal. Resolves
22172 issue 1955. Patch by John Brooks.
22173 - Add a new GETINFO option to get total bytes read and written. Patch
22174 from pipe, revised by atagar. Resolves ticket 2345.
22175 - Implement some GETINFO controller fields to provide information about
22176 the Tor process's pid, euid, username, and resource limits.
22179 - Our build system requires automake 1.6 or later to create the
22180 Makefile.in files. Previously, you could have used 1.4.
22181 This only affects developers and people building Tor from git;
22182 people who build Tor from the source distribution without changing
22183 the Makefile.am files should be fine.
22184 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
22185 so on. This is more robust against some of the failure modes
22186 associated with running the autotools pieces on their own.
22188 o Minor packaging issues:
22189 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
22190 already created. Patch from Andreas Stieger. Fixes bug 2573.
22192 o Code simplifications and refactoring:
22193 - A major revision to our internal node-selecting and listing logic.
22194 Tor already had at least two major ways to look at the question of
22195 "which Tor servers do we know about": a list of router descriptors,
22196 and a list of entries in the current consensus. With
22197 microdescriptors, we're adding a third. Having so many systems
22198 without an abstraction layer over them was hurting the codebase.
22199 Now, we have a new "node_t" abstraction that presents a consistent
22200 interface to a client's view of a Tor node, and holds (nearly) all
22201 of the mutable state formerly in routerinfo_t and routerstatus_t.
22202 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
22203 no longer link against Libevent: they never used it, but
22204 our library structure used to force them to link it.
22206 o Removed features:
22207 - Remove some old code to work around even older versions of Tor that
22208 used forked processes to handle DNS requests. Such versions of Tor
22209 are no longer in use as servers.
22211 o Documentation fixes:
22212 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
22213 - Add missing documentation for the authority-related torrc options
22214 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
22218 Changes in version 0.2.2.25-alpha - 2011-04-29
22219 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
22220 robust, routers no longer overreport their bandwidth, Win7 should crash
22221 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
22222 now prevents hidden service-related activity from being linkable. It
22223 provides more information to Vidalia so you can see if your bridge is
22224 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
22225 StrictNodes configuration options to make them more reliable, more
22226 understandable, and more regularly applied. If you use those options,
22227 please see the revised documentation for them in the manual page.
22230 - Relays were publishing grossly inflated bandwidth values because
22231 they were writing their state files wrong--now they write the
22232 correct value. Also, resume reading bandwidth history from the
22233 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
22234 - Improve hidden service robustness: When we find that we have
22235 extended a hidden service's introduction circuit to a relay not
22236 listed as an introduction point in the HS descriptor we currently
22237 have, retry with an introduction point from the current
22238 descriptor. Previously we would just give up. Fixes bugs 1024 and
22239 1930; bugfix on 0.2.0.10-alpha.
22240 - Clients now stop trying to use an exit node associated with a given
22241 destination by TrackHostExits if they fail to reach that exit node.
22242 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
22243 - Fix crash bug on platforms where gmtime and localtime can return
22244 NULL. Windows 7 users were running into this one. Fixes part of bug
22245 2077. Bugfix on all versions of Tor. Found by boboper.
22247 o Security and stability fixes:
22248 - Don't double-free a parsable, but invalid, microdescriptor, even if
22249 it is followed in the blob we're parsing by an unparsable
22250 microdescriptor. Fixes an issue reported in a comment on bug 2954.
22251 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
22252 - If the Nickname configuration option isn't given, Tor would pick a
22253 nickname based on the local hostname as the nickname for a relay.
22254 Because nicknames are not very important in today's Tor and the
22255 "Unnamed" nickname has been implemented, this is now problematic
22256 behavior: It leaks information about the hostname without being
22257 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
22258 introduced the Unnamed nickname. Reported by tagnaq.
22259 - Fix an uncommon assertion failure when running with DNSPort under
22260 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
22261 - Avoid linkability based on cached hidden service descriptors: forget
22262 all hidden service descriptors cached as a client when processing a
22263 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
22266 - Export GeoIP information on bridge usage to controllers even if we
22267 have not yet been running for 24 hours. Now Vidalia bridge operators
22268 can get more accurate and immediate feedback about their
22269 contributions to the network.
22271 o Major features and bugfixes (node selection):
22272 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
22273 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
22274 options. Previously, we had been ambiguous in describing what
22275 counted as an "exit" node, and what operations exactly "StrictNodes
22276 0" would permit. This created confusion when people saw nodes built
22277 through unexpected circuits, and made it hard to tell real bugs from
22278 surprises. Now the intended behavior is:
22279 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
22280 a node that delivers user traffic outside the Tor network.
22281 . "Entry", in the context of EntryNodes, means a node used as the
22282 first hop of a multihop circuit. It doesn't include direct
22283 connections to directory servers.
22284 . "ExcludeNodes" applies to all nodes.
22285 . "StrictNodes" changes the behavior of ExcludeNodes only. When
22286 StrictNodes is set, Tor should avoid all nodes listed in
22287 ExcludeNodes, even when it will make user requests fail. When
22288 StrictNodes is *not* set, then Tor should follow ExcludeNodes
22289 whenever it can, except when it must use an excluded node to
22290 perform self-tests, connect to a hidden service, provide a
22291 hidden service, fulfill a .exit request, upload directory
22292 information, or fetch directory information.
22293 Collectively, the changes to implement the behavior fix bug 1090.
22294 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
22295 a node is listed in both, it's treated as excluded.
22296 - ExcludeNodes now applies to directory nodes -- as a preference if
22297 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
22298 Don't exclude all the directory authorities and set StrictNodes to 1
22299 unless you really want your Tor to break.
22300 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
22301 - ExcludeExitNodes now overrides .exit requests.
22302 - We don't use bridges listed in ExcludeNodes.
22303 - When StrictNodes is 1:
22304 . We now apply ExcludeNodes to hidden service introduction points
22305 and to rendezvous points selected by hidden service users. This
22306 can make your hidden service less reliable: use it with caution!
22307 . If we have used ExcludeNodes on ourself, do not try relay
22308 reachability self-tests.
22309 . If we have excluded all the directory authorities, we will not
22310 even try to upload our descriptor if we're a relay.
22311 . Do not honor .exit requests to an excluded node.
22312 - Remove a misfeature that caused us to ignore the Fast/Stable flags
22313 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
22314 - When the set of permitted nodes changes, we now remove any mappings
22315 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
22317 - We never cannibalize a circuit that had excluded nodes on it, even
22318 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
22319 - Revert a change where we would be laxer about attaching streams to
22320 circuits than when building the circuits. This was meant to prevent
22321 a set of bugs where streams were never attachable, but our improved
22322 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
22323 - Keep track of how many times we launch a new circuit to handle a
22324 given stream. Too many launches could indicate an inconsistency
22325 between our "launch a circuit to handle this stream" logic and our
22326 "attach this stream to one of the available circuits" logic.
22327 - Improve log messages related to excluded nodes.
22330 - Fix a spurious warning when moving from a short month to a long
22331 month on relays with month-based BandwidthAccounting. Bugfix on
22332 0.2.2.17-alpha; fixes bug 3020.
22333 - When a client finds that an origin circuit has run out of 16-bit
22334 stream IDs, we now mark it as unusable for new streams. Previously,
22335 we would try to close the entire circuit. Bugfix on 0.0.6.
22336 - Add a forgotten cast that caused a compile warning on OS X 10.6.
22337 Bugfix on 0.2.2.24-alpha.
22338 - Be more careful about reporting the correct error from a failed
22339 connect() system call. Under some circumstances, it was possible to
22340 look at an incorrect value for errno when sending the end reason.
22341 Bugfix on 0.1.0.1-rc.
22342 - Correctly handle an "impossible" overflow cases in connection byte
22343 counting, where we write or read more than 4GB on an edge connection
22344 in a single second. Bugfix on 0.1.2.8-beta.
22345 - Correct the warning displayed when a rendezvous descriptor exceeds
22346 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
22348 - Clients and hidden services now use HSDir-flagged relays for hidden
22349 service descriptor downloads and uploads even if the relays have no
22350 DirPort set and the client has disabled TunnelDirConns. This will
22351 eventually allow us to give the HSDir flag to relays with no
22352 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
22353 - Downgrade "no current certificates known for authority" message from
22354 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
22355 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
22356 2917. Bugfix on 0.1.1.1-alpha.
22357 - Only limit the lengths of single HS descriptors, even when multiple
22358 HS descriptors are published to an HSDir relay in a single POST
22359 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
22360 - Write the current time into the LastWritten line in our state file,
22361 rather than the time from the previous write attempt. Also, stop
22362 trying to use a time of -1 in our log statements. Fixes bug 3039;
22363 bugfix on 0.2.2.14-alpha.
22364 - Be more consistent in our treatment of file system paths. "~" should
22365 get expanded to the user's home directory in the Log config option.
22366 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
22367 feature for the -f and --DataDirectory options.
22370 - Make sure every relay writes a state file at least every 12 hours.
22371 Previously, a relay could go for weeks without writing its state
22372 file, and on a crash could lose its bandwidth history, capacity
22373 estimates, client country statistics, and so on. Addresses bug 3012.
22374 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
22375 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
22376 clients are already deprecated because of security bugs.
22377 - Don't allow v0 hidden service authorities to act as clients.
22378 Required by fix for bug 3000.
22379 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
22380 by fix for bug 3000.
22381 - Ensure that no empty [dirreq-](read|write)-history lines are added
22382 to an extrainfo document. Implements ticket 2497.
22384 o Code simplification and refactoring:
22385 - Remove workaround code to handle directory responses from servers
22386 that had bug 539 (they would send HTTP status 503 responses _and_
22387 send a body too). Since only server versions before
22388 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
22389 keep the workaround in place.
22390 - Remove the old 'fuzzy time' logic. It was supposed to be used for
22391 handling calculations where we have a known amount of clock skew and
22392 an allowed amount of unknown skew. But we only used it in three
22393 places, and we never adjusted the known/unknown skew values. This is
22394 still something we might want to do someday, but if we do, we'll
22395 want to do it differently.
22396 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
22397 None of the cases where we did this before were wrong, but by making
22398 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
22399 - Use GetTempDir to find the proper temporary directory location on
22400 Windows when generating temporary files for the unit tests. Patch by
22404 Changes in version 0.2.2.24-alpha - 2011-04-08
22405 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
22406 prevented Tor clients from effectively using "multihomed" bridges,
22407 that is, bridges that listen on multiple ports or IP addresses so users
22408 can continue to use some of their addresses even if others get blocked.
22411 - Fix a bug where bridge users who configure the non-canonical
22412 address of a bridge automatically switch to its canonical
22413 address. If a bridge listens at more than one address, it should be
22414 able to advertise those addresses independently and any non-blocked
22415 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
22417 - If you configured Tor to use bridge A, and then quit and
22418 configured Tor to use bridge B instead, it would happily continue
22419 to use bridge A if it's still reachable. While this behavior is
22420 a feature if your goal is connectivity, in some scenarios it's a
22421 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
22422 - Directory authorities now use data collected from their own
22423 uptime observations when choosing whether to assign the HSDir flag
22424 to relays, instead of trusting the uptime value the relay reports in
22425 its descriptor. This change helps prevent an attack where a small
22426 set of nodes with frequently-changing identity keys can blackhole
22427 a hidden service. (Only authorities need upgrade; others will be
22428 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
22431 - When we restart our relay, we might get a successful connection
22432 from the outside before we've started our reachability tests,
22433 triggering a warning: "ORPort found reachable, but I have no
22434 routerinfo yet. Failing to inform controller of success." This
22435 bug was harmless unless Tor is running under a controller
22436 like Vidalia, in which case the controller would never get a
22437 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
22439 - Make directory authorities more accurate at recording when
22440 relays that have failed several reachability tests became
22441 unreachable, so we can provide more accuracy at assigning Stable,
22442 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
22443 - Fix an issue that prevented static linking of libevent on
22444 some platforms (notably Linux). Fixes bug 2698; bugfix on
22445 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
22446 the --with-static-libevent configure option).
22447 - We now ask the other side of a stream (the client or the exit)
22448 for more data on that stream when the amount of queued data on
22449 that stream dips low enough. Previously, we wouldn't ask the
22450 other side for more data until either it sent us more data (which
22451 it wasn't supposed to do if it had exhausted its window!) or we
22452 had completely flushed all our queued data. This flow control fix
22453 should improve throughput. Fixes bug 2756; bugfix on the earliest
22454 released versions of Tor (svn commit r152).
22455 - Avoid a double-mark-for-free warning when failing to attach a
22456 transparent proxy connection. (We thought we had fixed this in
22457 0.2.2.23-alpha, but it turns out our fix was checking the wrong
22458 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
22459 bug) and 0.2.2.23-alpha (the incorrect fix).
22460 - When warning about missing zlib development packages during compile,
22461 give the correct package names. Bugfix on 0.2.0.1-alpha.
22464 - Directory authorities now log the source of a rejected POSTed v3
22465 networkstatus vote.
22466 - Make compilation with clang possible when using
22467 --enable-gcc-warnings by removing two warning options that clang
22468 hasn't implemented yet and by fixing a few warnings. Implements
22470 - When expiring circuits, use microsecond timers rather than
22471 one-second timers. This can avoid an unpleasant situation where a
22472 circuit is launched near the end of one second and expired right
22473 near the beginning of the next, and prevent fluctuations in circuit
22475 - Use computed circuit-build timeouts to decide when to launch
22476 parallel introduction circuits for hidden services. (Previously,
22477 we would retry after 15 seconds.)
22478 - Update to the April 1 2011 Maxmind GeoLite Country database.
22481 - Create the /var/run/tor directory on startup on OpenSUSE if it is
22482 not already created. Patch from Andreas Stieger. Fixes bug 2573.
22484 o Documentation changes:
22485 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
22486 - Resolve all doxygen warnings except those for missing documentation.
22488 - Add doxygen documentation for more functions, fields, and types.
22491 Changes in version 0.2.2.23-alpha - 2011-03-08
22492 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
22493 they restart they don't lose their bandwidth capacity estimate. This
22494 release also fixes a diverse set of user-facing bugs, ranging from
22495 relays overrunning their rate limiting to clients falsely warning about
22496 clock skew to bridge descriptor leaks by our bridge directory authority.
22499 - Stop sending a CLOCK_SKEW controller status event whenever
22500 we fetch directory information from a relay that has a wrong clock.
22501 Instead, only inform the controller when it's a trusted authority
22502 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22503 the rest of bug 1074.
22504 - Fix an assert in parsing router descriptors containing IPv6
22505 addresses. This one took down the directory authorities when
22506 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
22507 - Make the bridge directory authority refuse to answer directory
22508 requests for "all" descriptors. It used to include bridge
22509 descriptors in its answer, which was a major information leak.
22510 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
22511 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22512 Tor would ignore their RelayBandwidthBurst setting,
22513 potentially using more bandwidth than expected. Bugfix on
22514 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22515 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22516 hidserv" in her torrc. The 'hidserv' argument never controlled
22517 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22520 - Relays now save observed peak bandwidth throughput rates to their
22521 state file (along with total usage, which was already saved)
22522 so that they can determine their correct estimated bandwidth on
22523 restart. Resolves bug 1863, where Tor relays would reset their
22524 estimated bandwidth to 0 after restarting.
22525 - Directory authorities now take changes in router IP address and
22526 ORPort into account when determining router stability. Previously,
22527 if a router changed its IP or ORPort, the authorities would not
22528 treat it as having any downtime for the purposes of stability
22529 calculation, whereas clients would experience downtime since the
22530 change could take a while to propagate to them. Resolves issue 1035.
22531 - Enable Address Space Layout Randomization (ASLR) and Data Execution
22532 Prevention (DEP) by default on Windows to make it harder for
22533 attackers to exploit vulnerabilities. Patch from John Brooks.
22535 o Minor bugfixes (on 0.2.1.x and earlier):
22536 - Fix a rare crash bug that could occur when a client was configured
22537 with a large number of bridges. Fixes bug 2629; bugfix on
22538 0.2.1.2-alpha. Bugfix by trac user "shitlei".
22539 - Avoid a double mark-for-free warning when failing to attach a
22540 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
22542 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
22543 found by "cypherpunks". This bug was introduced before the first
22544 Tor release, in svn commit r110.
22545 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
22546 don't mention them in the manpage. Fixes bug 2450; issue
22547 spotted by keb and G-Lo.
22548 - Fix a bug in bandwidth history state parsing that could have been
22549 triggered if a future version of Tor ever changed the timing
22550 granularity at which bandwidth history is measured. Bugfix on
22551 Tor 0.1.1.11-alpha.
22552 - When a relay decides that its DNS is too broken for it to serve
22553 as an exit server, it advertised itself as a non-exit, but
22554 continued to act as an exit. This could create accidental
22555 partitioning opportunities for users. Instead, if a relay is
22556 going to advertise reject *:* as its exit policy, it should
22557 really act with exit policy "reject *:*". Fixes bug 2366.
22558 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
22559 - In the special case where you configure a public exit relay as your
22560 bridge, Tor would be willing to use that exit relay as the last
22561 hop in your circuit as well. Now we fail that circuit instead.
22562 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
22563 - Fix a bug with our locking implementation on Windows that couldn't
22564 correctly detect when a file was already locked. Fixes bug 2504,
22565 bugfix on 0.2.1.6-alpha.
22566 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
22567 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
22569 - Set target port in get_interface_address6() correctly. Bugfix
22570 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
22571 - Directory authorities are now more robust to hops back in time
22572 when calculating router stability. Previously, if a run of uptime
22573 or downtime appeared to be negative, the calculation could give
22574 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
22576 - Fix an assert that got triggered when using the TestingTorNetwork
22577 configuration option and then issuing a GETINFO config-text control
22578 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
22580 o Minor bugfixes (on 0.2.2.x):
22581 - Clients should not weight BadExit nodes as Exits in their node
22582 selection. Similarly, directory authorities should not count BadExit
22583 bandwidth as Exit bandwidth when computing bandwidth-weights.
22584 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
22585 - Correctly clear our dir_read/dir_write history when there is an
22586 error parsing any bw history value from the state file. Bugfix on
22587 Tor 0.2.2.15-alpha.
22588 - Resolve a bug in verifying signatures of directory objects
22589 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
22590 Fixes bug 2409. Found by "piebeer".
22591 - Bridge authorities no longer crash on SIGHUP when they try to
22592 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
22596 - Log less aggressively about circuit timeout changes, and improve
22597 some other circuit timeout messages. Resolves bug 2004.
22598 - Log a little more clearly about the times at which we're no longer
22599 accepting new connections. Resolves bug 2181.
22600 - Reject attempts at the client side to open connections to private
22601 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
22602 a randomly chosen exit node. Attempts to do so are always
22603 ill-defined, generally prevented by exit policies, and usually
22604 in error. This will also help to detect loops in transparent
22605 proxy configurations. You can disable this feature by setting
22606 "ClientRejectInternalAddresses 0" in your torrc.
22607 - Always treat failure to allocate an RSA key as an unrecoverable
22609 - Update to the March 1 2011 Maxmind GeoLite Country database.
22611 o Minor features (log subsystem):
22612 - Add documentation for configuring logging at different severities in
22613 different log domains. We've had this feature since 0.2.1.1-alpha,
22614 but for some reason it never made it into the manpage. Fixes
22616 - Make it simpler to specify "All log domains except for A and B".
22617 Previously you needed to say "[*,~A,~B]". Now you can just say
22619 - Add a "LogMessageDomains 1" option to include the domains of log
22620 messages along with the messages. Without this, there's no way
22621 to use log domains without reading the source or doing a lot
22624 o Packaging changes:
22625 - Stop shipping the Tor specs files and development proposal documents
22626 in the tarball. They are now in a separate git repository at
22627 git://git.torproject.org/torspec.git
22630 Changes in version 0.2.1.30 - 2011-02-23
22631 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
22632 change is a slight tweak to Tor's TLS handshake that makes relays
22633 and bridges that run this new version reachable from Iran again.
22634 We don't expect this tweak will win the arms race long-term, but it
22635 buys us time until we roll out a better solution.
22638 - Stop sending a CLOCK_SKEW controller status event whenever
22639 we fetch directory information from a relay that has a wrong clock.
22640 Instead, only inform the controller when it's a trusted authority
22641 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
22642 the rest of bug 1074.
22643 - Fix a bounds-checking error that could allow an attacker to
22644 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22645 Found by "piebeer".
22646 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
22647 Tor would ignore their RelayBandwidthBurst setting,
22648 potentially using more bandwidth than expected. Bugfix on
22649 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
22650 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
22651 hidserv" in her torrc. The 'hidserv' argument never controlled
22652 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
22655 - Adjust our TLS Diffie-Hellman parameters to match those used by
22657 - Update to the February 1 2011 Maxmind GeoLite Country database.
22660 - Check for and reject overly long directory certificates and
22661 directory tokens before they have a chance to hit any assertions.
22662 Bugfix on 0.2.1.28. Found by "doorss".
22663 - Bring the logic that gathers routerinfos and assesses the
22664 acceptability of circuits into line. This prevents a Tor OP from
22665 getting locked in a cycle of choosing its local OR as an exit for a
22666 path (due to a .exit request) and then rejecting the circuit because
22667 its OR is not listed yet. It also prevents Tor clients from using an
22668 OR running in the same instance as an exit (due to a .exit request)
22669 if the OR does not meet the same requirements expected of an OR
22670 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
22672 o Packaging changes:
22673 - Stop shipping the Tor specs files and development proposal documents
22674 in the tarball. They are now in a separate git repository at
22675 git://git.torproject.org/torspec.git
22676 - Do not include Git version tags as though they are SVN tags when
22677 generating a tarball from inside a repository that has switched
22678 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
22681 Changes in version 0.2.2.22-alpha - 2011-01-25
22682 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
22683 main other change is a slight tweak to Tor's TLS handshake that makes
22684 relays and bridges that run this new version reachable from Iran again.
22685 We don't expect this tweak will win the arms race long-term, but it
22686 will buy us a bit more time until we roll out a better solution.
22689 - Fix a bounds-checking error that could allow an attacker to
22690 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
22691 Found by "piebeer".
22692 - Don't assert when changing from bridge to relay or vice versa
22693 via the controller. The assert happened because we didn't properly
22694 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
22695 bug 2433. Reported by bastik.
22698 - Adjust our TLS Diffie-Hellman parameters to match those used by
22700 - Provide a log message stating which geoip file we're parsing
22701 instead of just stating that we're parsing the geoip file.
22702 Implements ticket 2432.
22705 - Check for and reject overly long directory certificates and
22706 directory tokens before they have a chance to hit any assertions.
22707 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
22710 Changes in version 0.2.2.21-alpha - 2011-01-15
22711 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
22712 continues our recent code security audit work. The main fix resolves
22713 a remote heap overflow vulnerability that can allow remote code
22714 execution (CVE-2011-0427). Other fixes address a variety of assert
22715 and crash bugs, most of which we think are hard to exploit remotely.
22717 o Major bugfixes (security), also included in 0.2.1.29:
22718 - Fix a heap overflow bug where an adversary could cause heap
22719 corruption. This bug probably allows remote code execution
22720 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22722 - Prevent a denial-of-service attack by disallowing any
22723 zlib-compressed data whose compression factor is implausibly
22724 high. Fixes part of bug 2324; reported by "doorss".
22725 - Zero out a few more keys in memory before freeing them. Fixes
22726 bug 2384 and part of bug 2385. These key instances found by
22727 "cypherpunks", based on Andrew Case's report about being able
22728 to find sensitive data in Tor's memory space if you have enough
22729 permissions. Bugfix on 0.0.2pre9.
22731 o Major bugfixes (crashes), also included in 0.2.1.29:
22732 - Prevent calls to Libevent from inside Libevent log handlers.
22733 This had potential to cause a nasty set of crashes, especially
22734 if running Libevent with debug logging enabled, and running
22735 Tor with a controller watching for low-severity log messages.
22736 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22737 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22738 underflow errors there too. Fixes the other part of bug 2324.
22739 - Fix a bug where we would assert if we ever had a
22740 cached-descriptors.new file (or another file read directly into
22741 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22742 on 0.2.1.25. Found by doorss.
22743 - Fix some potential asserts and parsing issues with grossly
22744 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22747 o Minor bugfixes (other), also included in 0.2.1.29:
22748 - Fix a bug with handling misformed replies to reverse DNS lookup
22749 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22750 bug reported by doorss.
22751 - Fix compilation on mingw when a pthreads compatibility library
22752 has been installed. (We don't want to use it, so we shouldn't
22753 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22754 - Fix a bug where we would declare that we had run out of virtual
22755 addresses when the address space was only half-exhausted. Bugfix
22757 - Correctly handle the case where AutomapHostsOnResolve is set but
22758 no virtual addresses are available. Fixes bug 2328; bugfix on
22759 0.1.2.1-alpha. Bug found by doorss.
22760 - Correctly handle wrapping around when we run out of virtual
22761 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
22763 o Minor features, also included in 0.2.1.29:
22764 - Update to the January 1 2011 Maxmind GeoLite Country database.
22765 - Introduce output size checks on all of our decryption functions.
22767 o Build changes, also included in 0.2.1.29:
22768 - Tor does not build packages correctly with Automake 1.6 and earlier;
22769 added a check to Makefile.am to make sure that we're building with
22770 Automake 1.7 or later.
22771 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22772 because we built it with a too-old version of automake. Thus that
22773 release broke ./configure --enable-openbsd-malloc, which is popular
22774 among really fast exit relays on Linux.
22776 o Major bugfixes, new in 0.2.2.21-alpha:
22777 - Prevent crash/heap corruption when the cbtnummodes consensus
22778 parameter is set to 0 or large values. Fixes bug 2317; bugfix
22781 o Major features, new in 0.2.2.21-alpha:
22782 - Introduce minimum/maximum values that clients will believe
22783 from the consensus. Now we'll have a better chance to avoid crashes
22784 or worse when a consensus param has a weird value.
22786 o Minor features, new in 0.2.2.21-alpha:
22787 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
22788 used on bridges, and it makes bridge scanning somewhat easier.
22789 - If writing the state file to disk fails, wait up to an hour before
22790 retrying again, rather than trying again each second. Fixes bug
22791 2346; bugfix on Tor 0.1.1.3-alpha.
22792 - Make Libevent log messages get delivered to controllers later,
22793 and not from inside the Libevent log handler. This prevents unsafe
22794 reentrant Libevent calls while still letting the log messages
22796 - Detect platforms that brokenly use a signed size_t, and refuse to
22797 build there. Found and analyzed by doorss and rransom.
22798 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
22801 o Minor bugfixes, new in 0.2.2.21-alpha:
22802 - Handle SOCKS messages longer than 128 bytes long correctly, rather
22803 than waiting forever for them to finish. Fixes bug 2330; bugfix
22804 on 0.2.0.16-alpha. Found by doorss.
22805 - Add assertions to check for overflow in arguments to
22806 base32_encode() and base32_decode(); fix a signed-unsigned
22807 comparison there too. These bugs are not actually reachable in Tor,
22808 but it's good to prevent future errors too. Found by doorss.
22809 - Correctly detect failures to create DNS requests when using Libevent
22810 versions before v2. (Before Libevent 2, we used our own evdns
22811 implementation. Its return values for Libevent's evdns_resolve_*()
22812 functions are not consistent with those from Libevent.) Fixes bug
22813 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
22815 o Documentation, new in 0.2.2.21-alpha:
22816 - Document the default socks host and port (127.0.0.1:9050) for
22820 Changes in version 0.2.1.29 - 2011-01-15
22821 Tor 0.2.1.29 continues our recent code security audit work. The main
22822 fix resolves a remote heap overflow vulnerability that can allow remote
22823 code execution. Other fixes address a variety of assert and crash bugs,
22824 most of which we think are hard to exploit remotely.
22826 o Major bugfixes (security):
22827 - Fix a heap overflow bug where an adversary could cause heap
22828 corruption. This bug probably allows remote code execution
22829 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
22831 - Prevent a denial-of-service attack by disallowing any
22832 zlib-compressed data whose compression factor is implausibly
22833 high. Fixes part of bug 2324; reported by "doorss".
22834 - Zero out a few more keys in memory before freeing them. Fixes
22835 bug 2384 and part of bug 2385. These key instances found by
22836 "cypherpunks", based on Andrew Case's report about being able
22837 to find sensitive data in Tor's memory space if you have enough
22838 permissions. Bugfix on 0.0.2pre9.
22840 o Major bugfixes (crashes):
22841 - Prevent calls to Libevent from inside Libevent log handlers.
22842 This had potential to cause a nasty set of crashes, especially
22843 if running Libevent with debug logging enabled, and running
22844 Tor with a controller watching for low-severity log messages.
22845 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
22846 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
22847 underflow errors there too. Fixes the other part of bug 2324.
22848 - Fix a bug where we would assert if we ever had a
22849 cached-descriptors.new file (or another file read directly into
22850 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
22851 on 0.2.1.25. Found by doorss.
22852 - Fix some potential asserts and parsing issues with grossly
22853 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
22856 o Minor bugfixes (other):
22857 - Fix a bug with handling misformed replies to reverse DNS lookup
22858 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
22859 bug reported by doorss.
22860 - Fix compilation on mingw when a pthreads compatibility library
22861 has been installed. (We don't want to use it, so we shouldn't
22862 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
22863 - Fix a bug where we would declare that we had run out of virtual
22864 addresses when the address space was only half-exhausted. Bugfix
22866 - Correctly handle the case where AutomapHostsOnResolve is set but
22867 no virtual addresses are available. Fixes bug 2328; bugfix on
22868 0.1.2.1-alpha. Bug found by doorss.
22869 - Correctly handle wrapping around to when we run out of virtual
22870 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
22871 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
22872 because we built it with a too-old version of automake. Thus that
22873 release broke ./configure --enable-openbsd-malloc, which is popular
22874 among really fast exit relays on Linux.
22877 - Update to the January 1 2011 Maxmind GeoLite Country database.
22878 - Introduce output size checks on all of our decryption functions.
22881 - Tor does not build packages correctly with Automake 1.6 and earlier;
22882 added a check to Makefile.am to make sure that we're building with
22883 Automake 1.7 or later.
22886 Changes in version 0.2.2.20-alpha - 2010-12-17
22887 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
22888 exploitable bugs. We also fix a variety of other significant bugs,
22889 change the IP address for one of our directory authorities, and update
22890 the minimum version that Tor relays must run to join the network.
22893 - Fix a remotely exploitable bug that could be used to crash instances
22894 of Tor remotely by overflowing on the heap. Remote-code execution
22895 hasn't been confirmed, but can't be ruled out. Everyone should
22896 upgrade. Bugfix on the 0.1.1 series and later.
22897 - Fix a bug that could break accounting on 64-bit systems with large
22898 time_t values, making them hibernate for impossibly long intervals.
22899 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
22900 - Fix a logic error in directory_fetches_from_authorities() that
22901 would cause all _non_-exits refusing single-hop-like circuits
22902 to fetch from authorities, when we wanted to have _exits_ fetch
22903 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
22905 - Fix a stream fairness bug that would cause newer streams on a given
22906 circuit to get preference when reading bytes from the origin or
22907 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
22908 introduced before the first Tor release, in svn revision r152.
22910 o Directory authority changes:
22911 - Change IP address and ports for gabelmoo (v3 directory authority).
22914 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
22915 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
22916 - Fix an off-by-one error in calculating some controller command
22917 argument lengths. Fortunately, this mistake is harmless since
22918 the controller code does redundant NUL termination too. Found by
22919 boboper. Bugfix on 0.1.1.1-alpha.
22920 - Do not dereference NULL if a bridge fails to build its
22921 extra-info descriptor. Found by an anonymous commenter on
22922 Trac. Bugfix on 0.2.2.19-alpha.
22925 - Update to the December 1 2010 Maxmind GeoLite Country database.
22926 - Directory authorities now reject relays running any versions of
22927 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
22928 known bugs that keep RELAY_EARLY cells from working on rendezvous
22929 circuits. Followup to fix for bug 2081.
22930 - Directory authorities now reject relays running any version of Tor
22931 older than 0.2.0.26-rc. That version is the earliest that fetches
22932 current directory information correctly. Fixes bug 2156.
22933 - Report only the top 10 ports in exit-port stats in order not to
22934 exceed the maximum extra-info descriptor length of 50 KB. Implements
22938 Changes in version 0.2.1.28 - 2010-12-17
22939 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
22940 exploitable bugs. We also took this opportunity to change the IP address
22941 for one of our directory authorities, and to update the geoip database
22945 - Fix a remotely exploitable bug that could be used to crash instances
22946 of Tor remotely by overflowing on the heap. Remote-code execution
22947 hasn't been confirmed, but can't be ruled out. Everyone should
22948 upgrade. Bugfix on the 0.1.1 series and later.
22950 o Directory authority changes:
22951 - Change IP address and ports for gabelmoo (v3 directory authority).
22954 - Update to the December 1 2010 Maxmind GeoLite Country database.
22957 Changes in version 0.2.1.27 - 2010-11-23
22958 Yet another OpenSSL security patch broke its compatibility with Tor:
22959 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
22960 also took this opportunity to fix several crash bugs, integrate a new
22961 directory authority, and update the bundled GeoIP database.
22964 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
22965 No longer set the tlsext_host_name extension on server SSL objects;
22966 but continue to set it on client SSL objects. Our goal in setting
22967 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
22968 bugfix on 0.2.1.1-alpha.
22969 - Do not log messages to the controller while shrinking buffer
22970 freelists. Doing so would sometimes make the controller connection
22971 try to allocate a buffer chunk, which would mess up the internals
22972 of the freelist and cause an assertion failure. Fixes bug 1125;
22973 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
22974 - Learn our external IP address when we're a relay or bridge, even if
22975 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
22976 where we introduced bridge relays that don't need to publish to
22977 be useful. Fixes bug 2050.
22978 - Do even more to reject (and not just ignore) annotations on
22979 router descriptors received anywhere but from the cache. Previously
22980 we would ignore such annotations at first, but cache them to disk
22981 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
22982 - When you're using bridges and your network goes away and your
22983 bridges get marked as down, recover when you attempt a new socks
22984 connection (if the network is back), rather than waiting up to an
22985 hour to try fetching new descriptors for your bridges. Bugfix on
22986 0.2.0.3-alpha; fixes bug 1981.
22989 - Move to the November 2010 Maxmind GeoLite country db (rather
22990 than the June 2009 ip-to-country GeoIP db) for our statistics that
22991 count how many users relays are seeing from each country. Now we'll
22992 have more accurate data, especially for many African countries.
22994 o New directory authorities:
22995 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
22999 - Fix an assertion failure that could occur in directory caches or
23000 bridge users when using a very short voting interval on a testing
23001 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
23003 - Enforce multiplicity rules when parsing annotations. Bugfix on
23004 0.2.0.8-alpha. Found by piebeer.
23005 - Allow handshaking OR connections to take a full KeepalivePeriod
23006 seconds to handshake. Previously, we would close them after
23007 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23008 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23010 - When building with --enable-gcc-warnings on OpenBSD, disable
23011 warnings in system headers. This makes --enable-gcc-warnings
23012 pass on OpenBSD 4.8.
23015 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23016 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23017 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23018 Servers can start sending this code when enough clients recognize
23019 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
23020 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23021 Patch from mingw-san.
23024 - Remove the old debian/ directory from the main Tor distribution.
23025 The official Tor-for-debian git repository lives at the URL
23026 https://git.torproject.org/debian/tor.git
23027 - Stop shipping the old doc/website/ directory in the tarball. We
23028 changed the website format in late 2010, and what we shipped in
23029 0.2.1.26 really wasn't that useful anyway.
23032 Changes in version 0.2.2.19-alpha - 2010-11-22
23033 Yet another OpenSSL security patch broke its compatibility with Tor:
23034 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
23037 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
23038 No longer set the tlsext_host_name extension on server SSL objects;
23039 but continue to set it on client SSL objects. Our goal in setting
23040 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
23041 bugfix on 0.2.1.1-alpha.
23044 - Try harder not to exceed the maximum length of 50 KB when writing
23045 statistics to extra-info descriptors. This bug was triggered by very
23046 fast relays reporting exit-port, entry, and dirreq statistics.
23047 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
23048 - Publish a router descriptor even if generating an extra-info
23049 descriptor fails. Previously we would not publish a router
23050 descriptor without an extra-info descriptor; this can cause fast
23051 exit relays collecting exit-port statistics to drop from the
23052 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
23055 Changes in version 0.2.2.18-alpha - 2010-11-16
23056 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
23057 us lately, makes unpublished bridge relays able to detect their IP
23058 address, and fixes a wide variety of other bugs to get us much closer
23059 to a stable release.
23062 - Do even more to reject (and not just ignore) annotations on
23063 router descriptors received anywhere but from the cache. Previously
23064 we would ignore such annotations at first, but cache them to disk
23065 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
23066 - Do not log messages to the controller while shrinking buffer
23067 freelists. Doing so would sometimes make the controller connection
23068 try to allocate a buffer chunk, which would mess up the internals
23069 of the freelist and cause an assertion failure. Fixes bug 1125;
23070 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
23071 - Learn our external IP address when we're a relay or bridge, even if
23072 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
23073 where we introduced bridge relays that don't need to publish to
23074 be useful. Fixes bug 2050.
23075 - Maintain separate TLS contexts and certificates for incoming and
23076 outgoing connections in bridge relays. Previously we would use the
23077 same TLS contexts and certs for incoming and outgoing connections.
23078 Bugfix on 0.2.0.3-alpha; addresses bug 988.
23079 - Maintain separate identity keys for incoming and outgoing TLS
23080 contexts in bridge relays. Previously we would use the same
23081 identity keys for incoming and outgoing TLS contexts. Bugfix on
23082 0.2.0.3-alpha; addresses the other half of bug 988.
23083 - Avoid an assertion failure when we as an authority receive a
23084 duplicate upload of a router descriptor that we already have,
23085 but which we previously considered an obsolete descriptor.
23086 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
23087 - Avoid a crash bug triggered by looking at a dangling pointer while
23088 setting the network status consensus. Found by Robert Ransom.
23089 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
23090 - Fix a logic error where servers that _didn't_ act as exits would
23091 try to keep their server lists more aggressively up to date than
23092 exits, when it was supposed to be the other way around. Bugfix
23095 o Minor bugfixes (on Tor 0.2.1.x and earlier):
23096 - When we're trying to guess whether we know our IP address as
23097 a relay, we would log various ways that we failed to guess
23098 our address, but never log that we ended up guessing it
23099 successfully. Now add a log line to help confused and anxious
23100 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
23101 - Bring the logic that gathers routerinfos and assesses the
23102 acceptability of circuits into line. This prevents a Tor OP from
23103 getting locked in a cycle of choosing its local OR as an exit for a
23104 path (due to a .exit request) and then rejecting the circuit because
23105 its OR is not listed yet. It also prevents Tor clients from using an
23106 OR running in the same instance as an exit (due to a .exit request)
23107 if the OR does not meet the same requirements expected of an OR
23108 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
23109 - Correctly describe errors that occur when generating a TLS object.
23110 Previously we would attribute them to a failure while generating a
23111 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
23113 - Enforce multiplicity rules when parsing annotations. Bugfix on
23114 0.2.0.8-alpha. Found by piebeer.
23115 - Fix warnings that newer versions of autoconf produced during
23116 ./autogen.sh. These warnings appear to be harmless in our case,
23117 but they were extremely verbose. Fixes bug 2020.
23119 o Minor bugfixes (on Tor 0.2.2.x):
23120 - Enable protection of small arrays whenever we build with gcc
23121 hardening features, not only when also building with warnings
23122 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
23125 - Make hidden services work better in private Tor networks by not
23126 requiring any uptime to join the hidden service descriptor
23127 DHT. Implements ticket 2088.
23128 - Rate-limit the "your application is giving Tor only an IP address"
23129 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
23130 - When AllowSingleHopExits is set, print a warning to explain to the
23131 relay operator why most clients are avoiding her relay.
23132 - Update to the November 1 2010 Maxmind GeoLite Country database.
23134 o Code simplifications and refactoring:
23135 - When we fixed bug 1038 we had to put in a restriction not to send
23136 RELAY_EARLY cells on rend circuits. This was necessary as long
23137 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
23138 active. Now remove this obsolete check. Resolves bug 2081.
23139 - Some options used different conventions for uppercasing of acronyms
23140 when comparing manpage and source. Fix those in favor of the
23141 manpage, as it makes sense to capitalize acronyms.
23142 - Remove the torrc.complete file. It hasn't been kept up to date
23143 and users will have better luck checking out the manpage.
23144 - Remove the obsolete "NoPublish" option; it has been flagged
23145 as obsolete and has produced a warning since 0.1.1.18-rc.
23146 - Remove everything related to building the expert bundle for OS X.
23147 It has confused many users, doesn't work right on OS X 10.6,
23148 and is hard to get rid of once installed. Resolves bug 1274.
23151 Changes in version 0.2.2.17-alpha - 2010-09-30
23152 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
23153 to use one-hop circuits (which can put the exit relays at higher risk,
23154 plus unbalance the network); fixes a big bug in bandwidth accounting
23155 for relays that want to limit their monthly bandwidth use; fixes a
23156 big pile of bugs in how clients tolerate temporary network failure;
23157 and makes our adaptive circuit build timeout feature (which improves
23158 client performance if your network is fast while not breaking things
23159 if your network is slow) better handle bad networks.
23162 - Exit relays now try harder to block exit attempts from unknown
23163 relays, to make it harder for people to use them as one-hop proxies
23164 a la tortunnel. Controlled by the refuseunknownexits consensus
23165 parameter (currently enabled), or you can override it on your
23166 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
23168 o Major bugfixes (0.2.1.x and earlier):
23169 - Fix a bug in bandwidth accounting that could make us use twice
23170 the intended bandwidth when our interval start changes due to
23171 daylight saving time. Now we tolerate skew in stored vs computed
23172 interval starts: if the start of the period changes by no more than
23173 50% of the period's duration, we remember bytes that we transferred
23174 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
23175 - Always search the Windows system directory for system DLLs, and
23176 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
23177 - When you're using bridges and your network goes away and your
23178 bridges get marked as down, recover when you attempt a new socks
23179 connection (if the network is back), rather than waiting up to an
23180 hour to try fetching new descriptors for your bridges. Bugfix on
23181 0.2.0.3-alpha; fixes bug 1981.
23183 o Major bugfixes (on 0.2.2.x):
23184 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
23186 - Fix a segfault that could happen when operating a bridge relay with
23187 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
23188 - The consensus bandwidth-weights (used by clients to choose fast
23189 relays) entered an unexpected edge case in September where
23190 Exits were much scarcer than Guards, resulting in bad weight
23191 recommendations. Now we compute them using new constraints that
23192 should succeed in all cases. Also alter directory authorities to
23193 not include the bandwidth-weights line if they fail to produce
23194 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
23195 - When weighting bridges during path selection, we used to trust
23196 the bandwidths they provided in their descriptor, only capping them
23197 at 10MB/s. This turned out to be problematic for two reasons:
23198 Bridges could claim to handle a lot more traffic then they
23199 actually would, thus making more clients pick them and have a
23200 pretty effective DoS attack. The other issue is that new bridges
23201 that might not have a good estimate for their bw capacity yet
23202 would not get used at all unless no other bridges are available
23203 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
23205 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
23206 - Ignore cannibalized circuits when recording circuit build times.
23207 This should provide for a minor performance improvement for hidden
23208 service users using 0.2.2.14-alpha, and should remove two spurious
23209 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
23210 - Simplify the logic that causes us to decide if the network is
23211 unavailable for purposes of recording circuit build times. If we
23212 receive no cells whatsoever for the entire duration of a circuit's
23213 full measured lifetime, the network is probably down. Also ignore
23214 one-hop directory fetching circuit timeouts when calculating our
23215 circuit build times. These changes should hopefully reduce the
23216 cases where we see ridiculous circuit build timeouts for people
23217 with spotty wireless connections. Fixes part of bug 1772; bugfix
23219 - Prevent the circuit build timeout from becoming larger than
23220 the maximum build time we have ever seen. Also, prevent the time
23221 period for measurement circuits from becoming larger than twice that
23222 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
23225 - When we run out of directory information such that we can't build
23226 circuits, but then get enough that we can build circuits, log when
23227 we actually construct a circuit, so the user has a better chance of
23228 knowing what's going on. Fixes bug 1362.
23229 - Be more generous with how much bandwidth we'd use up (with
23230 accounting enabled) before entering "soft hibernation". Previously,
23231 we'd refuse new connections and circuits once we'd used up 95% of
23232 our allotment. Now, we use up 95% of our allotment, AND make sure
23233 that we have no more than 500MB (or 3 hours of expected traffic,
23234 whichever is lower) remaining before we enter soft hibernation.
23235 - If we've configured EntryNodes and our network goes away and/or all
23236 our entrynodes get marked down, optimistically retry them all when
23237 a new socks application request appears. Fixes bug 1882.
23238 - Add some more defensive programming for architectures that can't
23239 handle unaligned integer accesses. We don't know of any actual bugs
23240 right now, but that's the best time to fix them. Fixes bug 1943.
23241 - Support line continuations in the torrc config file. If a line
23242 ends with a single backslash character, the newline is ignored, and
23243 the configuration value is treated as continuing on the next line.
23246 o Minor bugfixes (on 0.2.1.x and earlier):
23247 - For bandwidth accounting, calculate our expected bandwidth rate
23248 based on the time during which we were active and not in
23249 soft-hibernation during the last interval. Previously, we were
23250 also considering the time spent in soft-hibernation. If this
23251 was a long time, we would wind up underestimating our bandwidth
23252 by a lot, and skewing our wakeup time towards the start of the
23253 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
23255 o Minor bugfixes (on 0.2.2.x):
23256 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
23257 which were disabled by the circuit build timeout changes in
23258 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
23259 - Make sure we don't warn about missing bandwidth weights when
23260 choosing bridges or other relays not in the consensus. Bugfix on
23261 0.2.2.10-alpha; fixes bug 1805.
23262 - In our logs, do not double-report signatures from unrecognized
23263 authorities both as "from unknown authority" and "not
23264 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
23267 Changes in version 0.2.2.16-alpha - 2010-09-17
23268 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
23269 evident at exit relays), and also continues to resolve all the little
23270 bugs that have been filling up trac lately.
23272 o Major bugfixes (stream-level fairness):
23273 - When receiving a circuit-level SENDME for a blocked circuit, try
23274 to package cells fairly from all the streams that had previously
23275 been blocked on that circuit. Previously, we had started with the
23276 oldest stream, and allowed each stream to potentially exhaust
23277 the circuit's package window. This gave older streams on any
23278 given circuit priority over newer ones. Fixes bug 1937. Detected
23279 originally by Camilo Viecco. This bug was introduced before the
23280 first Tor release, in svn commit r152: it is the new winner of
23281 the longest-lived bug prize.
23282 - When the exit relay got a circuit-level sendme cell, it started
23283 reading on the exit streams, even if had 500 cells queued in the
23284 circuit queue already, so the circuit queue just grew and grew in
23285 some cases. We fix this by not re-enabling reading on receipt of a
23286 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
23287 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
23289 - Newly created streams were allowed to read cells onto circuits,
23290 even if the circuit's cell queue was blocked and waiting to drain.
23291 This created potential unfairness, as older streams would be
23292 blocked, but newer streams would gladly fill the queue completely.
23293 We add code to detect this situation and prevent any stream from
23294 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
23298 - Update to the September 1 2010 Maxmind GeoLite Country database.
23299 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
23300 not. This would lead to a cookie that is still not group readable.
23301 Closes bug 1843. Suggested by katmagic.
23302 - When logging a rate-limited warning, we now mention how many messages
23303 got suppressed since the last warning.
23304 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
23305 do individual connection-level rate limiting of clients. The torrc
23306 config options with the same names trump the consensus params, if
23307 both are present. Replaces the old "bwconnrate" and "bwconnburst"
23308 consensus params which were broken from 0.2.2.7-alpha through
23309 0.2.2.14-alpha. Closes bug 1947.
23310 - When a router changes IP address or port, authorities now launch
23311 a new reachability test for it. Implements ticket 1899.
23312 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
23313 2 no signature, 4 required" messages about consensus signatures
23314 easier to read, and make sure they get logged at the same severity
23315 as the messages explaining which keys are which. Fixes bug 1290.
23316 - Don't warn when we have a consensus that we can't verify because
23317 of missing certificates, unless those certificates are ones
23318 that we have been trying and failing to download. Fixes bug 1145.
23319 - If you configure your bridge with a known identity fingerprint,
23320 and the bridge authority is unreachable (as it is in at least
23321 one country now), fall back to directly requesting the descriptor
23322 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
23324 - When building with --enable-gcc-warnings on OpenBSD, disable
23325 warnings in system headers. This makes --enable-gcc-warnings
23326 pass on OpenBSD 4.8.
23328 o Minor bugfixes (on 0.2.1.x and earlier):
23329 - Authorities will now attempt to download consensuses if their
23330 own efforts to make a live consensus have failed. This change
23331 means authorities that restart will fetch a valid consensus, and
23332 it means authorities that didn't agree with the current consensus
23333 will still fetch and serve it if it has enough signatures. Bugfix
23334 on 0.2.0.9-alpha; fixes bug 1300.
23335 - Ensure DNS requests launched by "RESOLVE" commands from the
23336 controller respect the __LeaveStreamsUnattached setconf options. The
23337 same goes for requests launched via DNSPort or transparent
23338 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
23339 - Allow handshaking OR connections to take a full KeepalivePeriod
23340 seconds to handshake. Previously, we would close them after
23341 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
23342 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
23344 - Rate-limit "Failed to hand off onionskin" warnings.
23345 - Never relay a cell for a circuit we have already destroyed.
23346 Between marking a circuit as closeable and finally closing it,
23347 it may have been possible for a few queued cells to get relayed,
23348 even though they would have been immediately dropped by the next
23349 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
23350 - Never queue a cell for a circuit that's already been marked
23352 - Never vote for a server as "Running" if we have a descriptor for
23353 it claiming to be hibernating, and that descriptor was published
23354 more recently than our last contact with the server. Bugfix on
23355 0.2.0.3-alpha; fixes bug 911.
23356 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
23359 o Minor bugfixes (on 0.2.2.x):
23360 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
23361 down if a directory fetch fails and you've configured either
23362 bridges or EntryNodes. The intent was to mark the relay as down
23363 _unless_ you're using bridges or EntryNodes, since if you are
23364 then you could quickly run out of entry points.
23365 - Fix the Windows directory-listing code. A bug introduced in
23366 0.2.2.14-alpha could make Windows directory servers forget to load
23367 some of their cached v2 networkstatus files.
23368 - Really allow clients to use relays as bridges. Fixes bug 1776;
23369 bugfix on 0.2.2.15-alpha.
23370 - Demote a warn to info that happens when the CellStatistics option
23371 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
23372 Reported by Moritz Bartl.
23373 - On Windows, build correctly either with or without Unicode support.
23374 This is necessary so that Tor can support fringe platforms like
23375 Windows 98 (which has no Unicode), or Windows CE (which has no
23376 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
23379 - Add a unit test for cross-platform directory-listing code.
23382 Changes in version 0.2.2.15-alpha - 2010-08-18
23383 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
23384 fixes a variety of other bugs that were preventing performance
23385 experiments from moving forward, fixes several bothersome memory leaks,
23386 and generally closes a lot of smaller bugs that have been filling up
23390 - Stop assigning the HSDir flag to relays that disable their
23391 DirPort (and thus will refuse to answer directory requests). This
23392 fix should dramatically improve the reachability of hidden services:
23393 hidden services and hidden service clients pick six HSDir relays
23394 to store and retrieve the hidden service descriptor, and currently
23395 about half of the HSDir relays will refuse to work. Bugfix on
23396 0.2.0.10-alpha; fixes part of bug 1693.
23397 - The PerConnBWRate and Burst config options, along with the
23398 bwconnrate and bwconnburst consensus params, initialized each conn's
23399 token bucket values only when the connection is established. Now we
23400 update them if the config options change, and update them every time
23401 we get a new consensus. Otherwise we can encounter an ugly edge
23402 case where we initialize an OR conn to client-level bandwidth,
23403 but then later the relay joins the consensus and we leave it
23404 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
23405 - Fix a regression that caused Tor to rebind its ports if it receives
23406 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
23409 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
23410 should give us approximately 40-50% more Guard-flagged nodes,
23411 improving the anonymity the Tor network can provide and also
23412 decreasing the dropoff in throughput that relays experience when
23413 they first get the Guard flag.
23414 - Allow enabling or disabling the *Statistics config options while
23418 - Update to the August 1 2010 Maxmind GeoLite Country database.
23419 - Have the controller interface give a more useful message than
23420 "Internal Error" in response to failed GETINFO requests.
23421 - Warn when the same option is provided more than once in a torrc
23422 file, on the command line, or in a single SETCONF statement, and
23423 the option is one that only accepts a single line. Closes bug 1384.
23424 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
23425 Patch from mingw-san.
23426 - Add support for the country code "{??}" in torrc options like
23427 ExcludeNodes, to indicate all routers of unknown country. Closes
23429 - Relays report the number of bytes spent on answering directory
23430 requests in extra-info descriptors similar to {read,write}-history.
23431 Implements enhancement 1790.
23433 o Minor bugfixes (on 0.2.1.x and earlier):
23434 - Complain if PublishServerDescriptor is given multiple arguments that
23435 include 0 or 1. This configuration will be rejected in the future.
23436 Bugfix on 0.2.0.1-alpha; closes bug 1107.
23437 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
23438 Bugfix on 0.2.0.13-alpha; closes bug 928.
23439 - Change "Application request when we're believed to be offline."
23440 notice to "Application request when we haven't used client
23441 functionality lately.", to clarify that it's not an error. Bugfix
23442 on 0.0.9.3; fixes bug 1222.
23443 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
23444 would return "551 Internal error" rather than "552 Unrecognized key
23445 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
23446 - Users can't configure a regular relay to be their bridge. It didn't
23447 work because when Tor fetched the bridge descriptor, it found
23448 that it already had it, and didn't realize that the purpose of the
23449 descriptor had changed. Now we replace routers with a purpose other
23450 than bridge with bridge descriptors when fetching them. Bugfix on
23451 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
23452 refetch the descriptor with router purpose 'general', disabling
23454 - Fix a rare bug in rend_fn unit tests: we would fail a test when
23455 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
23456 on 0.2.0.10-alpha; fixes bug 1808.
23457 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
23458 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
23459 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
23460 Servers can start sending this code when enough clients recognize
23461 it. Also update the spec to reflect this new reason. Bugfix on
23462 0.1.0.1-rc; fixes part of bug 1793.
23463 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
23464 when we switch from being a public relay to a bridge. Otherwise
23465 there will still be clients that see the relay in their consensus,
23466 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
23468 - Instead of giving an assertion failure on an internal mismatch
23469 on estimated freelist size, just log a BUG warning and try later.
23470 Mitigates but does not fix bug 1125.
23471 - Fix an assertion failure that could occur in caches or bridge users
23472 when using a very short voting interval on a testing network.
23473 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
23475 o Minor bugfixes (on 0.2.2.x):
23476 - Alter directory authorities to always consider Exit-flagged nodes
23477 as potential Guard nodes in their votes. The actual decision to
23478 use Exits as Guards is done in the consensus bandwidth weights.
23479 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
23480 - When the controller is reporting the purpose of circuits that
23481 didn't finish building before the circuit build timeout, it was
23482 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
23483 - Our libevent version parsing code couldn't handle versions like
23484 1.4.14b-stable and incorrectly warned the user about using an
23485 old and broken version of libevent. Treat 1.4.14b-stable like
23486 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
23488 - Don't use substitution references like $(VAR:MOD) when
23489 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
23490 '$(:x)' to 'x' rather than the empty string. This bites us in
23491 doc/ when configured with --disable-asciidoc. Bugfix on
23492 0.2.2.9-alpha; fixes bug 1773.
23493 - Remove a spurious hidden service server-side log notice about
23494 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
23496 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
23498 - Correctly report written bytes on linked connections. Found while
23499 implementing 1790. Bugfix on 0.2.2.4-alpha.
23500 - Fix three memory leaks: one in circuit_build_times_parse_state(),
23501 one in dirvote_add_signatures_to_pending_consensus(), and one every
23502 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
23503 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
23505 o Code simplifications and refactoring:
23506 - Take a first step towards making or.h smaller by splitting out
23507 function definitions for all source files in src/or/. Leave
23508 structures and defines in or.h for now.
23509 - Remove a bunch of unused function declarations as well as a block of
23510 #if 0'd code from the unit tests. Closes bug 1824.
23511 - New unit tests for exit-port history statistics; refactored exit
23512 statistics code to be more easily tested.
23513 - Remove the old debian/ directory from the main Tor distribution.
23514 The official Tor-for-debian git repository lives at the URL
23515 https://git.torproject.org/debian/tor.git
23518 Changes in version 0.2.2.14-alpha - 2010-07-12
23519 Tor 0.2.2.14-alpha greatly improves client-side handling of
23520 circuit build timeouts, which are used to estimate speed and improve
23521 performance. We also move to a much better GeoIP database, port Tor to
23522 Windows CE, introduce new compile flags that improve code security,
23523 add an eighth v3 directory authority, and address a lot of more
23527 - Tor directory authorities no longer crash when started with a
23528 cached-microdesc-consensus file in their data directory. Bugfix
23529 on 0.2.2.6-alpha; fixes bug 1532.
23530 - Treat an unset $HOME like an empty $HOME rather than triggering an
23531 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
23532 - Ignore negative and large circuit build timeout values that can
23533 happen during a suspend or hibernate. These values caused various
23534 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
23535 - Alter calculation of Pareto distribution parameter 'Xm' for
23536 Circuit Build Timeout learning to use the weighted average of the
23537 top N=3 modes (because we have three entry guards). Considering
23538 multiple modes should improve the timeout calculation in some cases,
23539 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
23541 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
23542 right censored distribution model. This approach improves over the
23543 synthetic timeout generation approach that was producing insanely
23544 high timeout values. Now we calculate build timeouts using truncated
23545 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
23546 - Do not close circuits that are under construction when they reach
23547 the circuit build timeout. Instead, leave them building (but do not
23548 use them) for up until the time corresponding to the 95th percentile
23549 on the Pareto CDF or 60 seconds, whichever is greater. This is done
23550 to provide better data for the new Pareto model. This percentile
23551 can be controlled by the consensus.
23554 - Move to the June 2010 Maxmind GeoLite country db (rather than the
23555 June 2009 ip-to-country GeoIP db) for our statistics that count
23556 how many users relays are seeing from each country. Now we have
23557 more accurate data for many African countries.
23558 - Port Tor to build and run correctly on Windows CE systems, using
23559 the wcecompat library. Contributed by Valerio Lupi.
23560 - New "--enable-gcc-hardening" ./configure flag (off by default)
23561 to turn on gcc compile time hardening options. It ensures
23562 that signed ints have defined behavior (-fwrapv), enables
23563 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
23564 with canaries (-fstack-protector-all), turns on ASLR protection if
23565 supported by the kernel (-fPIE, -pie), and adds additional security
23566 related warnings. Verified to work on Mac OS X and Debian Lenny.
23567 - New "--enable-linker-hardening" ./configure flag (off by default)
23568 to turn on ELF specific hardening features (relro, now). This does
23569 not work with Mac OS X or any other non-ELF binary format.
23571 o New directory authorities:
23572 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
23576 - New config option "WarnUnsafeSocks 0" disables the warning that
23577 occurs whenever Tor receives a socks handshake using a version of
23578 the socks protocol that can only provide an IP address (rather
23579 than a hostname). Setups that do DNS locally over Tor are fine,
23580 and we shouldn't spam the logs in that case.
23581 - Convert the HACKING file to asciidoc, and add a few new sections
23582 to it, explaining how we use Git, how we make changelogs, and
23583 what should go in a patch.
23584 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
23585 event, to give information on the current rate of circuit timeouts
23586 over our stored history.
23587 - Add ability to disable circuit build time learning via consensus
23588 parameter and via a LearnCircuitBuildTimeout config option. Also
23589 automatically disable circuit build time calculation if we are
23590 either a AuthoritativeDirectory, or if we fail to write our state
23591 file. Fixes bug 1296.
23592 - More gracefully handle corrupt state files, removing asserts
23593 in favor of saving a backup and resetting state.
23594 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
23598 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
23600 - When a2x fails, mention that the user could disable manpages instead
23601 of trying to fix their asciidoc installation.
23602 - Where available, use Libevent 2.0's periodic timers so that our
23603 once-per-second cleanup code gets called even more closely to
23604 once per second than it would otherwise. Fixes bug 943.
23605 - If you run a bridge that listens on multiple IP addresses, and
23606 some user configures a bridge address that uses a different IP
23607 address than your bridge writes in its router descriptor, and the
23608 user doesn't specify an identity key, their Tor would discard the
23609 descriptor because "it isn't one of our configured bridges", and
23610 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
23611 Bugfix on 0.2.0.3-alpha.
23612 - If OpenSSL fails to make a duplicate of a private or public key, log
23613 an error message and try to exit cleanly. May help with debugging
23614 if bug 1209 ever remanifests.
23615 - Save a couple bytes in memory allocation every time we escape
23616 certain characters in a string. Patch from Florian Zumbiehl.
23617 - Make it explicit that we don't cannibalize one-hop circuits. This
23618 happens in the wild, but doesn't turn out to be a problem because
23619 we fortunately don't use those circuits. Many thanks to outofwords
23620 for the initial analysis and to swissknife who confirmed that
23621 two-hop circuits are actually created.
23622 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
23623 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
23624 - Eliminate a case where a circuit build time warning was displayed
23625 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
23628 Changes in version 0.2.1.26 - 2010-05-02
23629 Tor 0.2.1.26 addresses the recent connection and memory overload
23630 problems we've been seeing on relays, especially relays with their
23631 DirPort open. If your relay has been crashing, or you turned it off
23632 because it used too many resources, give this release a try.
23634 This release also fixes yet another instance of broken OpenSSL libraries
23635 that was causing some relays to drop out of the consensus.
23638 - Teach relays to defend themselves from connection overload. Relays
23639 now close idle circuits early if it looks like they were intended
23640 for directory fetches. Relays are also more aggressive about closing
23641 TLS connections that have no circuits on them. Such circuits are
23642 unlikely to be re-used, and tens of thousands of them were piling
23643 up at the fast relays, causing the relays to run out of sockets
23644 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23645 their directory fetches over TLS).
23646 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23647 that claim to be earlier than 0.9.8m, but which have in reality
23648 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23649 behavior. Possible fix for some cases of bug 1346.
23650 - Directory mirrors were fetching relay descriptors only from v2
23651 directory authorities, rather than v3 authorities like they should.
23652 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23653 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23656 - Finally get rid of the deprecated and now harmful notion of "clique
23657 mode", where directory authorities maintain TLS connections to
23661 - In the util/threads test, no longer free the test_mutex before all
23662 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23663 - The master thread could starve the worker threads quite badly on
23664 certain systems, causing them to run only partially in the allowed
23665 window. This resulted in test failures. Now the master thread sleeps
23666 occasionally for a few microseconds while the two worker-threads
23667 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23670 Changes in version 0.2.2.13-alpha - 2010-04-24
23671 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
23672 problems we've been seeing on relays, especially relays with their
23673 DirPort open. If your relay has been crashing, or you turned it off
23674 because it used too many resources, give this release a try.
23677 - Teach relays to defend themselves from connection overload. Relays
23678 now close idle circuits early if it looks like they were intended
23679 for directory fetches. Relays are also more aggressive about closing
23680 TLS connections that have no circuits on them. Such circuits are
23681 unlikely to be re-used, and tens of thousands of them were piling
23682 up at the fast relays, causing the relays to run out of sockets
23683 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
23684 their directory fetches over TLS).
23687 - Finally get rid of the deprecated and now harmful notion of "clique
23688 mode", where directory authorities maintain TLS connections to
23690 - Directory authorities now do an immediate reachability check as soon
23691 as they hear about a new relay. This change should slightly reduce
23692 the time between setting up a relay and getting listed as running
23693 in the consensus. It should also improve the time between setting
23694 up a bridge and seeing use by bridge users.
23695 - Directory authorities no longer launch a TLS connection to every
23696 relay as they startup. Now that we have 2k+ descriptors cached,
23697 the resulting network hiccup is becoming a burden. Besides,
23698 authorities already avoid voting about Running for the first half
23699 hour of their uptime.
23702 Changes in version 0.2.2.12-alpha - 2010-04-20
23703 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
23704 handle and vote on descriptors. It was causing relays to drop out of
23708 - Many relays have been falling out of the consensus lately because
23709 not enough authorities know about their descriptor for them to get
23710 a majority of votes. When we deprecated the v2 directory protocol,
23711 we got rid of the only way that v3 authorities can hear from each
23712 other about other descriptors. Now authorities examine every v3
23713 vote for new descriptors, and fetch them from that authority. Bugfix
23715 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
23716 and a warning in or.h related to bandwidth_weight_rule_t that
23717 prevented clean compile on OS X. Fixes bug 1363; bugfix on
23719 - Fix a segfault on relays when DirReqStatistics is enabled
23720 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
23724 - Demote a confusing TLS warning that relay operators might get when
23725 someone tries to talk to their OrPort. It is neither the operator's
23726 fault nor can they do anything about it. Fixes bug 1364; bugfix
23730 Changes in version 0.2.2.11-alpha - 2010-04-15
23731 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
23732 libraries that was causing some relays to drop out of the consensus.
23735 - Directory mirrors were fetching relay descriptors only from v2
23736 directory authorities, rather than v3 authorities like they should.
23737 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
23738 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
23739 - Fix a parsing error that made every possible value of
23740 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
23741 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
23742 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
23743 about the option without breaking older ones.
23744 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
23745 that claim to be earlier than 0.9.8m, but which have in reality
23746 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
23747 behavior. Possible fix for some cases of bug 1346.
23750 - Experiment with a more aggressive approach to preventing clients
23751 from making one-hop exit streams. Exit relays who want to try it
23752 out can set "RefuseUnknownExits 1" in their torrc, and then look
23753 for "Attempt by %s to open a stream" log messages. Let us know
23755 - Add support for statically linking zlib by specifying
23756 --enable-static-zlib, to go with our support for statically linking
23757 openssl and libevent. Resolves bug 1358.
23760 - Fix a segfault that happens whenever a Tor client that is using
23761 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
23763 - When we cleaned up the contrib/tor-exit-notice.html file, we left
23764 out the first line. Fixes bug 1295.
23765 - When building the manpage from a tarball, we required asciidoc, but
23766 the asciidoc -> roff/html conversion was already done for the
23767 tarball. Make 'make' complain only when we need asciidoc (either
23768 because we're compiling directly from git, or because we altered
23769 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
23770 - When none of the directory authorities vote on any params, Tor
23771 segfaulted when trying to make the consensus from the votes. We
23772 didn't trigger the bug in practice, because authorities do include
23773 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
23776 - In the util/threads test, no longer free the test_mutex before all
23777 worker threads have finished. Bugfix on 0.2.1.6-alpha.
23778 - The master thread could starve the worker threads quite badly on
23779 certain systems, causing them to run only partially in the allowed
23780 window. This resulted in test failures. Now the master thread sleeps
23781 occasionally for a few microseconds while the two worker-threads
23782 compete for the mutex. Bugfix on 0.2.0.1-alpha.
23785 Changes in version 0.2.2.10-alpha - 2010-03-07
23786 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
23787 could prevent relays from guessing their IP address correctly. It also
23788 starts the groundwork for another client-side performance boost, since
23789 currently we're not making efficient use of relays that have both the
23790 Guard flag and the Exit flag.
23793 - Fix a regression from our patch for bug 1244 that caused relays
23794 to guess their IP address incorrectly if they didn't set Address
23795 in their torrc and/or their address fails to resolve. Bugfix on
23796 0.2.2.9-alpha; fixes bug 1269.
23798 o Major features (performance):
23799 - Directory authorities now compute consensus weightings that instruct
23800 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
23801 and no flag. Clients that use these weightings will distribute
23802 network load more evenly across these different relay types. The
23803 weightings are in the consensus so we can change them globally in
23804 the future. Extra thanks to "outofwords" for finding some nasty
23805 security bugs in the first implementation of this feature.
23807 o Minor features (performance):
23808 - Always perform router selections using weighted relay bandwidth,
23809 even if we don't need a high capacity circuit at the time. Non-fast
23810 circuits now only differ from fast ones in that they can use relays
23811 not marked with the Fast flag. This "feature" could turn out to
23812 be a horrible bug; we should investigate more before it goes into
23816 - Allow disabling building of the manpages. Skipping the manpage
23817 speeds up the build considerably.
23819 o Minor bugfixes (on 0.2.2.x):
23820 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
23821 Bugfix on 0.2.2.9-alpha.
23822 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
23823 config option. Bugfix on 0.2.2.7-alpha.
23824 - Ship the asciidoc-helper file in the tarball, so that people can
23825 build from source if they want to, and touching the .1.txt files
23826 doesn't break the build. Bugfix on 0.2.2.9-alpha.
23828 o Minor bugfixes (on 0.2.1.x or earlier):
23829 - Fix a dereference-then-NULL-check sequence when publishing
23830 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23832 - Fix another dereference-then-NULL-check sequence. Bugfix on
23833 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23834 - Make sure we treat potentially not NUL-terminated strings correctly.
23835 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23837 o Code simplifications and refactoring:
23838 - Fix some urls in the exit notice file and make it XHTML1.1 strict
23839 compliant. Based on a patch from Christian Kujau.
23840 - Don't use sed in asciidoc-helper anymore.
23841 - Make the build process fail if asciidoc cannot be found and
23842 building with asciidoc isn't disabled.
23845 Changes in version 0.2.2.9-alpha - 2010-02-22
23846 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
23847 location of a directory authority, and cleans up a bunch of small bugs.
23849 o Directory authority changes:
23850 - Change IP address for dannenberg (v3 directory authority), and
23851 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23852 service directory authority) from the list.
23855 - Make Tor work again on the latest OS X: when deciding whether to
23856 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23857 version at run-time, not compile time. We need to do this because
23858 Apple doesn't update its dev-tools headers when it updates its
23859 libraries in a security patch.
23860 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23861 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23862 a memory leak when requesting a hidden service descriptor we've
23863 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23865 - Authorities could be tricked into giving out the Exit flag to relays
23866 that didn't allow exiting to any ports. This bug could screw
23867 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
23868 1238. Bug discovered by Martin Kowalczyk.
23869 - When freeing a session key, zero it out completely. We only zeroed
23870 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23871 patched by ekir. Fixes bug 1254.
23874 - Fix static compilation by listing the openssl libraries in the right
23875 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
23876 - Resume handling .exit hostnames in a special way: originally we
23877 stripped the .exit part and used the requested exit relay. In
23878 0.2.2.1-alpha we stopped treating them in any special way, meaning
23879 if you use a .exit address then Tor will pass it on to the exit
23880 relay. Now we reject the .exit stream outright, since that behavior
23881 might be more expected by the user. Found and diagnosed by Scott
23882 Bennett and Downie on or-talk.
23883 - Don't spam the controller with events when we have no file
23884 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
23885 for log messages was already solved from bug 748.)
23886 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
23888 - Make the DNSPort option work with libevent 2.x. Don't alter the
23889 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
23890 - Emit a GUARD DROPPED controller event for a case we missed.
23891 - Make more fields in the controller protocol case-insensitive, since
23892 control-spec.txt said they were.
23893 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23894 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
23895 - Fix a spec conformance issue: the network-status-version token
23896 must be the first token in a v3 consensus or vote. Discovered by
23897 parakeep. Bugfix on 0.2.0.3-alpha.
23899 o Code simplifications and refactoring:
23900 - Generate our manpage and HTML documentation using Asciidoc. This
23901 change should make it easier to maintain the documentation, and
23902 produce nicer HTML.
23903 - Remove the --enable-iphone option. According to reports from Marco
23904 Bonetti, Tor builds fine without any special tweaking on recent
23905 iPhone SDK versions.
23906 - Removed some unnecessary files from the source distribution. The
23907 AUTHORS file has now been merged into the people page on the
23908 website. The roadmaps and design doc can now be found in the
23909 projects directory in svn.
23910 - Enabled various circuit build timeout constants to be controlled
23911 by consensus parameters. Also set better defaults for these
23912 parameters based on experimentation on broadband and simulated
23913 high latency links.
23916 - The 'EXTENDCIRCUIT' control port command can now be used with
23917 a circ id of 0 and no path. This feature will cause Tor to build
23918 a new 'fast' general purpose circuit using its own path selection
23920 - Added a BUILDTIMEOUT_SET controller event to describe changes
23921 to the circuit build timeout.
23922 - Future-proof the controller protocol a bit by ignoring keyword
23923 arguments we do not recognize.
23924 - Expand homedirs passed to tor-checkkey. This should silence a
23925 coverity complaint about passing a user-supplied string into
23926 open() without checking it.
23929 Changes in version 0.2.1.25 - 2010-03-16
23930 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
23931 prevent relays from guessing their IP address correctly. It also fixes
23932 several minor potential security bugs.
23935 - Fix a regression from our patch for bug 1244 that caused relays
23936 to guess their IP address incorrectly if they didn't set Address
23937 in their torrc and/or their address fails to resolve. Bugfix on
23938 0.2.1.23; fixes bug 1269.
23939 - When freeing a session key, zero it out completely. We only zeroed
23940 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
23941 patched by ekir. Fixes bug 1254.
23944 - Fix a dereference-then-NULL-check sequence when publishing
23945 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
23947 - Fix another dereference-then-NULL-check sequence. Bugfix on
23948 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
23949 - Make sure we treat potentially not NUL-terminated strings correctly.
23950 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
23954 Changes in version 0.2.1.24 - 2010-02-21
23955 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
23959 - Work correctly out-of-the-box with even more vendor-patched versions
23960 of OpenSSL. In particular, make it so Debian and OS X don't need
23961 customized patches to run/build.
23964 Changes in version 0.2.1.23 - 2010-02-13
23965 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
23966 again on the latest OS X, and updates the location of a directory
23969 o Major bugfixes (performance):
23970 - We were selecting our guards uniformly at random, and then weighting
23971 which of our guards we'd use uniformly at random. This imbalance
23972 meant that Tor clients were severely limited on throughput (and
23973 probably latency too) by the first hop in their circuit. Now we
23974 select guards weighted by currently advertised bandwidth. We also
23975 automatically discard guards picked using the old algorithm. Fixes
23976 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
23979 - Make Tor work again on the latest OS X: when deciding whether to
23980 use strange flags to turn TLS renegotiation on, detect the OpenSSL
23981 version at run-time, not compile time. We need to do this because
23982 Apple doesn't update its dev-tools headers when it updates its
23983 libraries in a security patch.
23984 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
23985 that could happen on 32-bit platforms with 64-bit time_t. Also fix
23986 a memory leak when requesting a hidden service descriptor we've
23987 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
23990 o Directory authority changes:
23991 - Change IP address for dannenberg (v3 directory authority), and
23992 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
23993 service directory authority) from the list.
23996 - Refactor resolve_my_address() to not use gethostbyname() anymore.
23997 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
24000 - Avoid a mad rush at the beginning of each month when each client
24001 rotates half of its guards. Instead we spread the rotation out
24002 throughout the month, but we still avoid leaving a precise timestamp
24003 in the state file about when we first picked the guard. Improves
24004 over the behavior introduced in 0.1.2.17.
24007 Changes in version 0.2.2.8-alpha - 2010-01-26
24008 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
24009 causing bridge relays to disappear. If you're running a bridge,
24013 - Fix a memory corruption bug on bridges that occurred during the
24014 inclusion of stats data in extra-info descriptors. Also fix the
24015 interface for geoip_get_bridge_stats* to prevent similar bugs in
24016 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
24017 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
24020 - Ignore OutboundBindAddress when connecting to localhost.
24021 Connections to localhost need to come _from_ localhost, or else
24022 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
24026 Changes in version 0.2.2.7-alpha - 2010-01-19
24027 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
24028 as laying the groundwork for further relay-side performance fixes. It
24029 also starts cleaning up client behavior with respect to the EntryNodes,
24030 ExitNodes, and StrictNodes config options.
24032 This release also rotates two directory authority keys, due to a
24033 security breach of some of the Torproject servers.
24035 o Directory authority changes:
24036 - Rotate keys (both v3 identity and relay identity) for moria1
24039 o Major features (performance):
24040 - We were selecting our guards uniformly at random, and then weighting
24041 which of our guards we'd use uniformly at random. This imbalance
24042 meant that Tor clients were severely limited on throughput (and
24043 probably latency too) by the first hop in their circuit. Now we
24044 select guards weighted by currently advertised bandwidth. We also
24045 automatically discard guards picked using the old algorithm. Fixes
24046 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
24047 - When choosing which cells to relay first, relays can now favor
24048 circuits that have been quiet recently, to provide lower latency
24049 for low-volume circuits. By default, relays enable or disable this
24050 feature based on a setting in the consensus. You can override
24051 this default by using the new "CircuitPriorityHalflife" config
24052 option. Design and code by Ian Goldberg, Can Tang, and Chris
24054 - Add separate per-conn write limiting to go with the per-conn read
24055 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
24056 but never per-conn write limits.
24057 - New consensus params "bwconnrate" and "bwconnburst" to let us
24058 rate-limit client connections as they enter the network. It's
24059 controlled in the consensus so we can turn it on and off for
24060 experiments. It's starting out off. Based on proposal 163.
24062 o Major features (relay selection options):
24063 - Switch to a StrictNodes config option, rather than the previous
24064 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
24065 "StrictExcludeNodes" option.
24066 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
24067 change during a config reload, mark and discard all our origin
24068 circuits. This fix should address edge cases where we change the
24069 config options and but then choose a circuit that we created before
24071 - If EntryNodes or ExitNodes are set, be more willing to use an
24072 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
24074 - Make EntryNodes config option much more aggressive even when
24075 StrictNodes is not set. Before it would prepend your requested
24076 entrynodes to your list of guard nodes, but feel free to use others
24077 after that. Now it chooses only from your EntryNodes if any of
24078 those are available, and only falls back to others if a) they're
24079 all down and b) StrictNodes is not set.
24080 - Now we refresh your entry guards from EntryNodes at each consensus
24081 fetch -- rather than just at startup and then they slowly rot as
24082 the network changes.
24085 - Stop bridge directory authorities from answering dbg-stability.txt
24086 directory queries, which would let people fetch a list of all
24087 bridge identities they track. Bugfix on 0.2.1.6-alpha.
24090 - Log a notice when we get a new control connection. Now it's easier
24091 for security-conscious users to recognize when a local application
24092 is knocking on their controller door. Suggested by bug 1196.
24093 - New config option "CircuitStreamTimeout" to override our internal
24094 timeout schedule for how many seconds until we detach a stream from
24095 a circuit and try a new circuit. If your network is particularly
24096 slow, you might want to set this to a number like 60.
24097 - New controller command "getinfo config-text". It returns the
24098 contents that Tor would write if you send it a SAVECONF command,
24099 so the controller can write the file to disk itself.
24100 - New options for SafeLogging to allow scrubbing only log messages
24101 generated while acting as a relay.
24102 - Ship the bridges spec file in the tarball too.
24103 - Avoid a mad rush at the beginning of each month when each client
24104 rotates half of its guards. Instead we spread the rotation out
24105 throughout the month, but we still avoid leaving a precise timestamp
24106 in the state file about when we first picked the guard. Improves
24107 over the behavior introduced in 0.1.2.17.
24109 o Minor bugfixes (compiling):
24110 - Fix compilation on OS X 10.3, which has a stub mlockall() but
24111 hides it. Bugfix on 0.2.2.6-alpha.
24112 - Fix compilation on Solaris by removing support for the
24113 DisableAllSwap config option. Solaris doesn't have an rlimit for
24114 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
24117 o Minor bugfixes (crashes):
24118 - Do not segfault when writing buffer stats when we haven't observed
24119 a single circuit to report about. Found by Fabian Lanze. Bugfix on
24121 - If we're in the pathological case where there's no exit bandwidth
24122 but there is non-exit bandwidth, or no guard bandwidth but there
24123 is non-guard bandwidth, don't crash during path selection. Bugfix
24125 - Fix an impossible-to-actually-trigger buffer overflow in relay
24126 descriptor generation. Bugfix on 0.1.0.15.
24128 o Minor bugfixes (privacy):
24129 - Fix an instance where a Tor directory mirror might accidentally
24130 log the IP address of a misbehaving Tor client. Bugfix on
24132 - Don't list Windows capabilities in relay descriptors. We never made
24133 use of them, and maybe it's a bad idea to publish them. Bugfix
24136 o Minor bugfixes (other):
24137 - Resolve an edge case in path weighting that could make us misweight
24138 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
24139 - Fix statistics on client numbers by country as seen by bridges that
24140 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
24141 intervals instead of variable 12-to-48-hour intervals.
24142 - After we free an internal connection structure, overwrite it
24143 with a different memory value than we use for overwriting a freed
24144 internal circuit structure. Should help with debugging. Suggested
24146 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
24149 o Removed features:
24150 - Remove the HSAuthorityRecordStats option that version 0 hidden
24151 service authorities could have used to track statistics of overall
24152 hidden service usage.
24155 Changes in version 0.2.1.22 - 2010-01-19
24156 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
24157 authorities -- it would tell you its whole history of bridge descriptors
24158 if you make the right directory request. This stable update also
24159 rotates two of the seven v3 directory authority keys and locations.
24161 o Directory authority changes:
24162 - Rotate keys (both v3 identity and relay identity) for moria1
24166 - Stop bridge directory authorities from answering dbg-stability.txt
24167 directory queries, which would let people fetch a list of all
24168 bridge identities they track. Bugfix on 0.2.1.6-alpha.
24171 Changes in version 0.2.1.21 - 2009-12-21
24172 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
24173 library. If you use Tor on Linux / Unix and you're getting SSL
24174 renegotiation errors, upgrading should help. We also recommend an
24175 upgrade if you're an exit relay.
24178 - Work around a security feature in OpenSSL 0.9.8l that prevents our
24179 handshake from working unless we explicitly tell OpenSSL that we
24180 are using SSL renegotiation safely. We are, of course, but OpenSSL
24181 0.9.8l won't work unless we say we are.
24182 - Avoid crashing if the client is trying to upload many bytes and the
24183 circuit gets torn down at the same time, or if the flip side
24184 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
24187 - Do not refuse to learn about authority certs and v2 networkstatus
24188 documents that are older than the latest consensus. This bug might
24189 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
24190 Spotted and fixed by xmux.
24191 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
24192 trigger platform-specific option misparsing case found by Coverity
24194 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
24195 trigger assert. Fixes bug 1173.
24198 Changes in version 0.2.2.6-alpha - 2009-11-19
24199 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
24200 support for the new lower-footprint "microdescriptor" directory design,
24201 future-proofing our consensus format against new hash functions or
24202 other changes, and an Android port. It also makes Tor compatible with
24203 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
24206 - Directory authorities can now create, vote on, and serve multiple
24207 parallel formats of directory data as part of their voting process.
24208 Partially implements Proposal 162: "Publish the consensus in
24210 - Directory authorities can now agree on and publish small summaries
24211 of router information that clients can use in place of regular
24212 server descriptors. This transition will eventually allow clients
24213 to use far less bandwidth for downloading information about the
24214 network. Begins the implementation of Proposal 158: "Clients
24215 download consensus + microdescriptors".
24216 - The directory voting system is now extensible to use multiple hash
24217 algorithms for signatures and resource selection. Newer formats
24218 are signed with SHA256, with a possibility for moving to a better
24219 hash algorithm in the future.
24220 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
24221 current and future memory pages via mlockall(). On supported
24222 platforms (modern Linux and probably BSD but not Windows or OS X),
24223 this should effectively disable any and all attempts to page out
24224 memory. This option requires that you start your Tor as root --
24225 if you use DisableAllSwap, please consider using the User option
24226 to properly reduce the privileges of your Tor.
24227 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
24228 to help Tor build correctly for Android phones.
24231 - Work around a security feature in OpenSSL 0.9.8l that prevents our
24232 handshake from working unless we explicitly tell OpenSSL that we
24233 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
24234 won't work unless we say we are.
24237 - Fix a crash bug when trying to initialize the evdns module in
24238 Libevent 2. Bugfix on 0.2.1.16-rc.
24239 - Stop logging at severity 'warn' when some other Tor client tries
24240 to establish a circuit with us using weak DH keys. It's a protocol
24241 violation, but that doesn't mean ordinary users need to hear about
24242 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
24243 - Do not refuse to learn about authority certs and v2 networkstatus
24244 documents that are older than the latest consensus. This bug might
24245 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
24246 Spotted and fixed by xmux.
24247 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
24248 - If all authorities restart at once right before a consensus vote,
24249 nobody will vote about "Running", and clients will get a consensus
24250 with no usable relays. Instead, authorities refuse to build a
24251 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
24252 - If your relay can't keep up with the number of incoming create
24253 cells, it would log one warning per failure into your logs. Limit
24254 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
24255 - Bridges now use "reject *:*" as their default exit policy. Bugfix
24256 on 0.2.0.3-alpha; fixes bug 1113.
24257 - Fix a memory leak on directory authorities during voting that was
24258 introduced in 0.2.2.1-alpha. Found via valgrind.
24261 Changes in version 0.2.1.20 - 2009-10-15
24262 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
24263 services at once, prepares for more performance improvements, and
24264 fixes a bunch of smaller bugs.
24266 The Windows and OS X bundles also include a more recent Vidalia,
24267 and switch from Privoxy to Polipo.
24269 The OS X installers are now drag and drop. It's best to un-install
24270 Tor/Vidalia and then install this new bundle, rather than upgrade. If
24271 you want to upgrade, you'll need to update the paths for Tor and Polipo
24272 in the Vidalia Settings window.
24275 - Send circuit or stream sendme cells when our window has decreased
24276 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24277 by Karsten when testing the "reduce circuit window" performance
24278 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24279 before the release of Tor 0.0.0. This is the new winner of the
24281 - Fix a remotely triggerable memory leak when a consensus document
24282 contains more than one signature from the same voter. Bugfix on
24284 - Avoid segfault in rare cases when finishing an introduction circuit
24285 as a client and finding out that we don't have an introduction key
24286 for it. Fixes bug 1073. Reported by Aaron Swartz.
24289 - Tor now reads the "circwindow" parameter out of the consensus,
24290 and uses that value for its circuit package window rather than the
24291 default of 1000 cells. Begins the implementation of proposal 168.
24293 o New directory authorities:
24294 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24296 - Move moria1 and tonga to alternate IP addresses.
24299 - Fix a signed/unsigned compile warning in 0.2.1.19.
24300 - Fix possible segmentation fault on directory authorities. Bugfix on
24302 - Fix an extremely rare infinite recursion bug that could occur if
24303 we tried to log a message after shutting down the log subsystem.
24304 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24305 - Fix an obscure bug where hidden services on 64-bit big-endian
24306 systems might mis-read the timestamp in v3 introduce cells, and
24307 refuse to connect back to the client. Discovered by "rotor".
24308 Bugfix on 0.2.1.6-alpha.
24309 - We were triggering a CLOCK_SKEW controller status event whenever
24310 we connect via the v2 connection protocol to any relay that has
24311 a wrong clock. Instead, we should only inform the controller when
24312 it's a trusted authority that claims our clock is wrong. Bugfix
24313 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24314 - We were telling the controller about CHECKING_REACHABILITY and
24315 REACHABILITY_FAILED status events whenever we launch a testing
24316 circuit or notice that one has failed. Instead, only tell the
24317 controller when we want to inform the user of overall success or
24318 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24320 - Don't warn when we're using a circuit that ends with a node
24321 excluded in ExcludeExitNodes, but the circuit is not used to access
24322 the outside world. This should help fix bug 1090. Bugfix on
24324 - Work around a small memory leak in some versions of OpenSSL that
24325 stopped the memory used by the hostname TLS extension from being
24329 - Add a "getinfo status/accepted-server-descriptor" controller
24330 command, which is the recommended way for controllers to learn
24331 whether our server descriptor has been successfully received by at
24332 least on directory authority. Un-recommend good-server-descriptor
24333 getinfo and status events until we have a better design for them.
24336 Changes in version 0.2.2.5-alpha - 2009-10-11
24337 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
24340 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
24342 o Directory authorities:
24343 - Temporarily (just for this release) move dizum to an alternate
24347 Changes in version 0.2.2.4-alpha - 2009-10-10
24348 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
24349 introduces a new unit test framework, shifts directry authority
24350 addresses around to reduce the impact from recent blocking events,
24351 and fixes a few smaller bugs.
24354 - Fix several more asserts in the circuit_build_times code, for
24355 example one that causes Tor to fail to start once we have
24356 accumulated 5000 build times in the state file. Bugfixes on
24357 0.2.2.2-alpha; fixes bug 1108.
24359 o New directory authorities:
24360 - Move moria1 and Tonga to alternate IP addresses.
24363 - Log SSL state transitions at debug level during handshake, and
24364 include SSL states in error messages. This may help debug future
24365 SSL handshake issues.
24366 - Add a new "Handshake" log domain for activities that happen
24367 during the TLS handshake.
24368 - Revert to the "June 3 2009" ip-to-country file. The September one
24369 seems to have removed most US IP addresses.
24370 - Directory authorities now reject Tor relays with versions less than
24371 0.1.2.14. This step cuts out four relays from the current network,
24372 none of which are very big.
24375 - Fix a couple of smaller issues with gathering statistics. Bugfixes
24377 - Fix two memory leaks in the error case of
24378 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
24379 - Don't count one-hop circuits when we're estimating how long it
24380 takes circuits to build on average. Otherwise we'll set our circuit
24381 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
24382 - Directory authorities no longer change their opinion of, or vote on,
24383 whether a router is Running, unless they have themselves been
24384 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
24387 o Code simplifications and refactoring:
24388 - Revise our unit tests to use the "tinytest" framework, so we
24389 can run tests in their own processes, have smarter setup/teardown
24390 code, and so on. The unit test code has moved to its own
24391 subdirectory, and has been split into multiple modules.
24394 Changes in version 0.2.2.3-alpha - 2009-09-23
24395 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
24398 - Fix an overzealous assert in our new circuit build timeout code.
24399 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
24402 - If the networkstatus consensus tells us that we should use a
24403 negative circuit package window, ignore it. Otherwise we'll
24404 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
24407 Changes in version 0.2.2.2-alpha - 2009-09-21
24408 Tor 0.2.2.2-alpha introduces our latest performance improvement for
24409 clients: Tor tracks the average time it takes to build a circuit, and
24410 avoids using circuits that take too long to build. For fast connections,
24411 this feature can cut your expected latency in half. For slow or flaky
24412 connections, it could ruin your Tor experience. Let us know if it does!
24415 - Tor now tracks how long it takes to build client-side circuits
24416 over time, and adapts its timeout to local network performance.
24417 Since a circuit that takes a long time to build will also provide
24418 bad performance, we get significant latency improvements by
24419 discarding the slowest 20% of circuits. Specifically, Tor creates
24420 circuits more aggressively than usual until it has enough data
24421 points for a good timeout estimate. Implements proposal 151.
24422 We are especially looking for reports (good and bad) from users with
24423 both EDGE and broadband connections that can move from broadband
24424 to EDGE and find out if the build-time data in the .tor/state gets
24425 reset without loss of Tor usability. You should also see a notice
24426 log message telling you that Tor has reset its timeout.
24427 - Directory authorities can now vote on arbitrary integer values as
24428 part of the consensus process. This is designed to help set
24429 network-wide parameters. Implements proposal 167.
24430 - Tor now reads the "circwindow" parameter out of the consensus,
24431 and uses that value for its circuit package window rather than the
24432 default of 1000 cells. Begins the implementation of proposal 168.
24435 - Fix a remotely triggerable memory leak when a consensus document
24436 contains more than one signature from the same voter. Bugfix on
24440 - Fix an extremely rare infinite recursion bug that could occur if
24441 we tried to log a message after shutting down the log subsystem.
24442 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
24443 - Fix parsing for memory or time units given without a space between
24444 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
24445 - A networkstatus vote must contain exactly one signature. Spec
24446 conformance issue. Bugfix on 0.2.0.3-alpha.
24447 - Fix an obscure bug where hidden services on 64-bit big-endian
24448 systems might mis-read the timestamp in v3 introduce cells, and
24449 refuse to connect back to the client. Discovered by "rotor".
24450 Bugfix on 0.2.1.6-alpha.
24451 - We were triggering a CLOCK_SKEW controller status event whenever
24452 we connect via the v2 connection protocol to any relay that has
24453 a wrong clock. Instead, we should only inform the controller when
24454 it's a trusted authority that claims our clock is wrong. Bugfix
24455 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
24456 - We were telling the controller about CHECKING_REACHABILITY and
24457 REACHABILITY_FAILED status events whenever we launch a testing
24458 circuit or notice that one has failed. Instead, only tell the
24459 controller when we want to inform the user of overall success or
24460 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
24462 - Don't warn when we're using a circuit that ends with a node
24463 excluded in ExcludeExitNodes, but the circuit is not used to access
24464 the outside world. This should help fix bug 1090, but more problems
24465 remain. Bugfix on 0.2.1.6-alpha.
24466 - Work around a small memory leak in some versions of OpenSSL that
24467 stopped the memory used by the hostname TLS extension from being
24469 - Make our 'torify' script more portable; if we have only one of
24470 'torsocks' or 'tsocks' installed, don't complain to the user;
24471 and explain our warning about tsocks better.
24474 - Add a "getinfo status/accepted-server-descriptor" controller
24475 command, which is the recommended way for controllers to learn
24476 whether our server descriptor has been successfully received by at
24477 least on directory authority. Un-recommend good-server-descriptor
24478 getinfo and status events until we have a better design for them.
24479 - Update to the "September 4 2009" ip-to-country file.
24482 Changes in version 0.2.2.1-alpha - 2009-08-26
24483 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
24484 Tor clients to bootstrap on networks where only port 80 is reachable,
24485 makes it more straightforward to support hardware crypto accelerators,
24486 and starts the groundwork for gathering stats safely at relays.
24489 - Start the process of disabling ".exit" address notation, since it
24490 can be used for a variety of esoteric application-level attacks
24491 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
24494 o New directory authorities:
24495 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
24499 - New AccelName and AccelDir options add support for dynamic OpenSSL
24500 hardware crypto acceleration engines.
24501 - Tor now supports tunneling all of its outgoing connections over
24502 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
24503 configuration options. Code by Christopher Davis.
24506 - Send circuit or stream sendme cells when our window has decreased
24507 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
24508 by Karsten when testing the "reduce circuit window" performance
24509 patch. Bugfix on the 54th commit on Tor -- from July 2002,
24510 before the release of Tor 0.0.0. This is the new winner of the
24513 o New options for gathering stats safely:
24514 - Directory mirrors that set "DirReqStatistics 1" write statistics
24515 about directory requests to disk every 24 hours. As compared to the
24516 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
24517 1) stats are written to disk exactly every 24 hours; 2) estimated
24518 shares of v2 and v3 requests are determined as mean values, not at
24519 the end of a measurement period; 3) unresolved requests are listed
24520 with country code '??'; 4) directories also measure download times.
24521 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
24522 number of exit streams and transferred bytes per port to disk every
24524 - Relays that set "CellStatistics 1" write statistics on how long
24525 cells spend in their circuit queues to disk every 24 hours.
24526 - Entry nodes that set "EntryStatistics 1" write statistics on the
24527 rough number and origins of connecting clients to disk every 24
24529 - Relays that write any of the above statistics to disk and set
24530 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
24531 their extra-info documents.
24534 - New --digests command-line switch to output the digests of the
24535 source files Tor was built with.
24536 - The "torify" script now uses torsocks where available.
24537 - The memarea code now uses a sentinel value at the end of each area
24538 to make sure nothing writes beyond the end of an area. This might
24539 help debug some conceivable causes of bug 930.
24540 - Time and memory units in the configuration file can now be set to
24541 fractional units. For example, "2.5 GB" is now a valid value for
24543 - Certain Tor clients (such as those behind check.torproject.org) may
24544 want to fetch the consensus in an extra early manner. To enable this
24545 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
24546 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
24547 as only certain clients who must have this information sooner should
24549 - Instead of adding the svn revision to the Tor version string, report
24550 the git commit (when we're building from a git checkout).
24553 - If any of the v3 certs we download are unparseable, we should
24554 actually notice the failure so we don't retry indefinitely. Bugfix
24555 on 0.2.0.x; reported by "rotator".
24556 - If the cached cert file is unparseable, warn but don't exit.
24557 - Fix possible segmentation fault on directory authorities. Bugfix on
24559 - When Tor fails to parse a descriptor of any kind, dump it to disk.
24560 Might help diagnosing bug 1051.
24562 o Deprecated and removed features:
24563 - The controller no longer accepts the old obsolete "addr-mappings/"
24564 or "unregistered-servers-" GETINFO values.
24565 - Hidden services no longer publish version 0 descriptors, and clients
24566 do not request or use version 0 descriptors. However, the old hidden
24567 service authorities still accept and serve version 0 descriptors
24568 when contacted by older hidden services/clients.
24569 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
24570 always on; using them is necessary for correct forward-compatible
24572 - Remove support for .noconnect style addresses. Nobody was using
24573 them, and they provided another avenue for detecting Tor users
24574 via application-level web tricks.
24576 o Packaging changes:
24577 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
24578 installer bundles. See
24579 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
24580 for details of what's new in Vidalia 0.2.3.
24581 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
24582 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
24583 configuration file, rather than the old Privoxy.
24584 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
24585 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
24586 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
24587 better compatibility with OS X 10.6, aka Snow Leopard.
24588 - OS X Vidalia Bundle: The multi-package installer is now replaced
24589 by a simple drag and drop to the /Applications folder. This change
24590 occurred with the upgrade to Vidalia 0.2.3.
24593 Changes in version 0.2.1.19 - 2009-07-28
24594 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
24595 services on Tor 0.2.1.3-alpha through 0.2.1.18.
24598 - Make accessing hidden services on 0.2.1.x work right again.
24599 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
24600 part of patch provided by "optimist".
24603 - When a relay/bridge is writing out its identity key fingerprint to
24604 the "fingerprint" file and to its logs, write it without spaces. Now
24605 it will look like the fingerprints in our bridges documentation,
24606 and confuse fewer users.
24609 - Relays no longer publish a new server descriptor if they change
24610 their MaxAdvertisedBandwidth config option but it doesn't end up
24611 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
24612 fixes bug 1026. Patch from Sebastian.
24613 - Avoid leaking memory every time we get a create cell but we have
24614 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
24615 fixes bug 1034. Reported by BarkerJr.
24618 Changes in version 0.2.1.18 - 2009-07-24
24619 Tor 0.2.1.18 lays the foundations for performance improvements,
24620 adds status events to help users diagnose bootstrap problems, adds
24621 optional authentication/authorization for hidden services, fixes a
24622 variety of potential anonymity problems, and includes a huge pile of
24623 other features and bug fixes.
24626 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
24629 Changes in version 0.2.1.17-rc - 2009-07-07
24630 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
24631 candidate for the 0.2.1.x series. It lays the groundwork for further
24632 client performance improvements, and also fixes a big bug with directory
24633 authorities that were causing them to assign Guard and Stable flags
24636 The Windows bundles also finally include the geoip database that we
24637 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
24638 should actually install Torbutton rather than giving you a cryptic
24639 failure message (oops).
24642 - Clients now use the bandwidth values in the consensus, rather than
24643 the bandwidth values in each relay descriptor. This approach opens
24644 the door to more accurate bandwidth estimates once the directory
24645 authorities start doing active measurements. Implements more of
24649 - When Tor clients restart after 1-5 days, they discard all their
24650 cached descriptors as too old, but they still use the cached
24651 consensus document. This approach is good for robustness, but
24652 bad for performance: since they don't know any bandwidths, they
24653 end up choosing at random rather than weighting their choice by
24654 speed. Fixed by the above feature of putting bandwidths in the
24655 consensus. Bugfix on 0.2.0.x.
24656 - Directory authorities were neglecting to mark relays down in their
24657 internal histories if the relays fall off the routerlist without
24658 ever being found unreachable. So there were relays in the histories
24659 that haven't been seen for eight months, and are listed as being
24660 up for eight months. This wreaked havoc on the "median wfu"
24661 and "median mtbf" calculations, in turn making Guard and Stable
24662 flags very wrong, hurting network performance. Fixes bugs 696 and
24663 969. Bugfix on 0.2.0.6-alpha.
24666 - Serve the DirPortFrontPage page even when we have been approaching
24667 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
24668 - The control port would close the connection before flushing long
24669 replies, such as the network consensus, if a QUIT command was issued
24670 before the reply had completed. Now, the control port flushes all
24671 pending replies before closing the connection. Also fixed a spurious
24672 warning when a QUIT command is issued after a malformed or rejected
24673 AUTHENTICATE command, but before the connection was closed. Patch
24674 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
24675 - When we can't find an intro key for a v2 hidden service descriptor,
24676 fall back to the v0 hidden service descriptor and log a bug message.
24677 Workaround for bug 1024.
24678 - Fix a log message that did not respect the SafeLogging option.
24682 - If we're a relay and we change our IP address, be more verbose
24683 about the reason that made us change. Should help track down
24684 further bugs for relays on dynamic IP addresses.
24687 Changes in version 0.2.0.35 - 2009-06-24
24689 - Avoid crashing in the presence of certain malformed descriptors.
24690 Found by lark, and by automated fuzzing.
24691 - Fix an edge case where a malicious exit relay could convince a
24692 controller that the client's DNS question resolves to an internal IP
24693 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24696 - Finally fix the bug where dynamic-IP relays disappear when their
24697 IP address changes: directory mirrors were mistakenly telling
24698 them their old address if they asked via begin_dir, so they
24699 never got an accurate answer about their new address, so they
24700 just vanished after a day. For belt-and-suspenders, relays that
24701 don't set Address in their config now avoid using begin_dir for
24702 all direct connections. Should fix bugs 827, 883, and 900.
24703 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24704 that would occur on some exit nodes when DNS failures and timeouts
24705 occurred in certain patterns. Fix for bug 957.
24708 - When starting with a cache over a few days old, do not leak
24709 memory for the obsolete router descriptors in it. Bugfix on
24710 0.2.0.33; fixes bug 672.
24711 - Hidden service clients didn't use a cached service descriptor that
24712 was older than 15 minutes, but wouldn't fetch a new one either,
24713 because there was already one in the cache. Now, fetch a v2
24714 descriptor unless the same descriptor was added to the cache within
24715 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24718 Changes in version 0.2.1.16-rc - 2009-06-20
24719 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
24720 a bunch of minor bugs.
24723 - Fix an edge case where a malicious exit relay could convince a
24724 controller that the client's DNS question resolves to an internal IP
24725 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
24727 o Major performance improvements (on 0.2.0.x):
24728 - Disable and refactor some debugging checks that forced a linear scan
24729 over the whole server-side DNS cache. These accounted for over 50%
24730 of CPU time on a relatively busy exit node's gprof profile. Found
24732 - Disable some debugging checks that appeared in exit node profile
24736 - Update to the "June 3 2009" ip-to-country file.
24737 - Do not have tor-resolve automatically refuse all .onion addresses;
24738 if AutomapHostsOnResolve is set in your torrc, this will work fine.
24740 o Minor bugfixes (on 0.2.0.x):
24741 - Log correct error messages for DNS-related network errors on
24743 - Fix a race condition that could cause crashes or memory corruption
24744 when running as a server with a controller listening for log
24746 - Avoid crashing when we have a policy specified in a DirPolicy or
24747 SocksPolicy or ReachableAddresses option with ports set on it,
24748 and we re-load the policy. May fix bug 996.
24749 - Hidden service clients didn't use a cached service descriptor that
24750 was older than 15 minutes, but wouldn't fetch a new one either,
24751 because there was already one in the cache. Now, fetch a v2
24752 descriptor unless the same descriptor was added to the cache within
24753 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
24755 o Minor bugfixes (on 0.2.1.x):
24756 - Don't warn users about low port and hibernation mix when they
24757 provide a *ListenAddress directive to fix that. Bugfix on
24759 - When switching back and forth between bridge mode, do not start
24760 gathering GeoIP data until two hours have passed.
24761 - Do not complain that the user has requested an excluded node as
24762 an exit when the node is not really an exit. This could happen
24763 because the circuit was for testing, or an introduction point.
24767 Changes in version 0.2.1.15-rc - 2009-05-25
24768 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
24769 series. It fixes a major bug on fast exit relays, as well as a variety
24770 of more minor bugs.
24772 o Major bugfixes (on 0.2.0.x):
24773 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
24774 that would occur on some exit nodes when DNS failures and timeouts
24775 occurred in certain patterns. Fix for bug 957.
24777 o Minor bugfixes (on 0.2.0.x):
24778 - Actually return -1 in the error case for read_bandwidth_usage().
24779 Harmless bug, since we currently don't care about the return value
24780 anywhere. Bugfix on 0.2.0.9-alpha.
24781 - Provide a more useful log message if bug 977 (related to buffer
24782 freelists) ever reappears, and do not crash right away.
24783 - Fix an assertion failure on 64-bit platforms when we allocated
24784 memory right up to the end of a memarea, then realigned the memory
24785 one step beyond the end. Fixes a possible cause of bug 930.
24786 - Protect the count of open sockets with a mutex, so we can't
24787 corrupt it when two threads are closing or opening sockets at once.
24788 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
24789 - Don't allow a bridge to publish its router descriptor to a
24790 non-bridge directory authority. Fixes part of bug 932.
24791 - When we change to or from being a bridge, reset our counts of
24792 client usage by country. Fixes bug 932.
24793 - Fix a bug that made stream bandwidth get misreported to the
24795 - Stop using malloc_usable_size() to use more area than we had
24796 actually allocated: it was safe, but made valgrind really unhappy.
24797 - Fix a memory leak when v3 directory authorities load their keys
24798 and cert from disk. Bugfix on 0.2.0.1-alpha.
24800 o Minor bugfixes (on 0.2.1.x):
24801 - Fix use of freed memory when deciding to mark a non-addable
24802 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
24805 Changes in version 0.2.1.14-rc - 2009-04-12
24806 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
24807 series. It begins fixing some major performance problems, and also
24808 finally addresses the bug that was causing relays on dynamic IP
24809 addresses to fall out of the directory.
24812 - Clients replace entry guards that were chosen more than a few months
24813 ago. This change should significantly improve client performance,
24814 especially once more people upgrade, since relays that have been
24815 a guard for a long time are currently overloaded.
24817 o Major bugfixes (on 0.2.0):
24818 - Finally fix the bug where dynamic-IP relays disappear when their
24819 IP address changes: directory mirrors were mistakenly telling
24820 them their old address if they asked via begin_dir, so they
24821 never got an accurate answer about their new address, so they
24822 just vanished after a day. For belt-and-suspenders, relays that
24823 don't set Address in their config now avoid using begin_dir for
24824 all direct connections. Should fix bugs 827, 883, and 900.
24825 - Relays were falling out of the networkstatus consensus for
24826 part of a day if they changed their local config but the
24827 authorities discarded their new descriptor as "not sufficiently
24828 different". Now directory authorities accept a descriptor as changed
24829 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
24830 patch by Sebastian.
24831 - Avoid crashing in the presence of certain malformed descriptors.
24832 Found by lark, and by automated fuzzing.
24835 - When generating circuit events with verbose nicknames for
24836 controllers, try harder to look up nicknames for routers on a
24837 circuit. (Previously, we would look in the router descriptors we had
24838 for nicknames, but not in the consensus.) Partial fix for bug 941.
24839 - If the bridge config line doesn't specify a port, assume 443.
24840 This makes bridge lines a bit smaller and easier for users to
24842 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
24843 bytes (aka 20KB/s), to match our documentation. Also update
24844 directory authorities so they always assign the Fast flag to relays
24845 with 20KB/s of capacity. Now people running relays won't suddenly
24846 find themselves not seeing any use, if the network gets faster
24848 - Update to the "April 3 2009" ip-to-country file.
24851 - Avoid trying to print raw memory to the logs when we decide to
24852 give up on downloading a given relay descriptor. Bugfix on
24854 - In tor-resolve, when the Tor client to use is specified by
24855 <hostname>:<port>, actually use the specified port rather than
24856 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
24857 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
24858 - When starting with a cache over a few days old, do not leak
24859 memory for the obsolete router descriptors in it. Bugfix on
24861 - Avoid double-free on list of successfully uploaded hidden
24862 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
24863 - Change memarea_strndup() implementation to work even when
24864 duplicating a string at the end of a page. This bug was
24865 harmless for now, but could have meant crashes later. Fix by
24866 lark. Bugfix on 0.2.1.1-alpha.
24867 - Limit uploaded directory documents to be 16M rather than 500K.
24868 The directory authorities were refusing v3 consensus votes from
24869 other authorities, since the votes are now 504K. Fixes bug 959;
24870 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
24871 - Directory authorities should never send a 503 "busy" response to
24872 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
24876 Changes in version 0.2.1.13-alpha - 2009-03-09
24877 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
24878 cleanups. We're finally getting close to a release candidate.
24881 - Correctly update the list of which countries we exclude as
24882 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
24883 lark. Bugfix on 0.2.1.6-alpha.
24885 o Minor bugfixes (on 0.2.0.x and earlier):
24886 - Automatically detect MacOSX versions earlier than 10.4.0, and
24887 disable kqueue from inside Tor when running with these versions.
24888 We previously did this from the startup script, but that was no
24889 help to people who didn't use the startup script. Resolves bug 863.
24890 - When we had picked an exit node for a connection, but marked it as
24891 "optional", and it turned out we had no onion key for the exit,
24892 stop wanting that exit and try again. This situation may not
24893 be possible now, but will probably become feasible with proposal
24894 158. Spotted by rovv. Fixes another case of bug 752.
24895 - Clients no longer cache certificates for authorities they do not
24896 recognize. Bugfix on 0.2.0.9-alpha.
24897 - When we can't transmit a DNS request due to a network error, retry
24898 it after a while, and eventually transmit a failing response to
24899 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
24900 - If the controller claimed responsibility for a stream, but that
24901 stream never finished making its connection, it would live
24902 forever in circuit_wait state. Now we close it after SocksTimeout
24903 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
24904 - Drop begin cells to a hidden service if they come from the middle
24905 of a circuit. Patch from lark.
24906 - When we erroneously receive two EXTEND cells for the same circuit
24907 ID on the same connection, drop the second. Patch from lark.
24908 - Fix a crash that occurs on exit nodes when a nameserver request
24909 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
24910 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
24912 - Do not assume that a stack-allocated character array will be
24913 64-bit aligned on platforms that demand that uint64_t access is
24914 aligned. Possible fix for bug 604.
24915 - Parse dates and IPv4 addresses in a locale- and libc-independent
24916 manner, to avoid platform-dependent behavior on malformed input.
24917 - Build correctly when configured to build outside the main source
24918 path. Patch from Michael Gold.
24919 - We were already rejecting relay begin cells with destination port
24920 of 0. Now also reject extend cells with destination port or address
24921 of 0. Suggested by lark.
24923 o Minor bugfixes (on 0.2.1.x):
24924 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
24925 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
24926 - If we're an exit node, scrub the IP address to which we are exiting
24927 in the logs. Bugfix on 0.2.1.8-alpha.
24930 - On Linux, use the prctl call to re-enable core dumps when the user
24932 - New controller event NEWCONSENSUS that lists the networkstatus
24933 lines for every recommended relay. Now controllers like Torflow
24934 can keep up-to-date on which relays they should be using.
24935 - Update to the "February 26 2009" ip-to-country file.
24938 Changes in version 0.2.0.34 - 2009-02-08
24939 Tor 0.2.0.34 features several more security-related fixes. You should
24940 upgrade, especially if you run an exit relay (remote crash) or a
24941 directory authority (remote infinite loop), or you're on an older
24942 (pre-XP) or not-recently-patched Windows (remote exploit).
24944 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
24945 have many known flaws, and nobody should be using them. You should
24946 upgrade. If you're using a Linux or BSD and its packages are obsolete,
24947 stop using those packages and upgrade anyway.
24950 - Fix an infinite-loop bug on handling corrupt votes under certain
24951 circumstances. Bugfix on 0.2.0.8-alpha.
24952 - Fix a temporary DoS vulnerability that could be performed by
24953 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24954 - Avoid a potential crash on exit nodes when processing malformed
24955 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
24956 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
24957 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
24960 - Fix compilation on systems where time_t is a 64-bit integer.
24961 Patch from Matthias Drochner.
24962 - Don't consider expiring already-closed client connections. Fixes
24963 bug 893. Bugfix on 0.0.2pre20.
24966 Changes in version 0.2.1.12-alpha - 2009-02-08
24967 Tor 0.2.1.12-alpha features several more security-related fixes. You
24968 should upgrade, especially if you run an exit relay (remote crash) or
24969 a directory authority (remote infinite loop), or you're on an older
24970 (pre-XP) or not-recently-patched Windows (remote exploit). It also
24971 includes a big pile of minor bugfixes and cleanups.
24974 - Fix an infinite-loop bug on handling corrupt votes under certain
24975 circumstances. Bugfix on 0.2.0.8-alpha.
24976 - Fix a temporary DoS vulnerability that could be performed by
24977 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
24978 - Avoid a potential crash on exit nodes when processing malformed
24979 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
24982 - Let controllers actually ask for the "clients_seen" event for
24983 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
24984 reported by Matt Edman.
24985 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
24987 - Fix a bug in address parsing that was preventing bridges or hidden
24988 service targets from being at IPv6 addresses.
24989 - Solve a bug that kept hardware crypto acceleration from getting
24990 enabled when accounting was turned on. Fixes bug 907. Bugfix on
24992 - Remove a bash-ism from configure.in to build properly on non-Linux
24993 platforms. Bugfix on 0.2.1.1-alpha.
24994 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
24995 headers. Bugfix on 0.2.0.10-alpha.
24996 - Don't consider expiring already-closed client connections. Fixes
24997 bug 893. Bugfix on 0.0.2pre20.
24998 - Fix another interesting corner-case of bug 891 spotted by rovv:
24999 Previously, if two hosts had different amounts of clock drift, and
25000 one of them created a new connection with just the wrong timing,
25001 the other might decide to deprecate the new connection erroneously.
25002 Bugfix on 0.1.1.13-alpha.
25003 - Resolve a very rare crash bug that could occur when the user forced
25004 a nameserver reconfiguration during the middle of a nameserver
25005 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
25006 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
25007 Bugfix on 0.2.1.7-alpha.
25008 - If we're using bridges and our network goes away, be more willing
25009 to forgive our bridges and try again when we get an application
25010 request. Bugfix on 0.2.0.x.
25013 - Support platforms where time_t is 64 bits long. (Congratulations,
25014 NetBSD!) Patch from Matthias Drochner.
25015 - Add a 'getinfo status/clients-seen' controller command, in case
25016 controllers want to hear clients_seen events but connect late.
25019 - Disable GCC's strict alias optimization by default, to avoid the
25020 likelihood of its introducing subtle bugs whenever our code violates
25021 the letter of C99's alias rules.
25024 Changes in version 0.2.0.33 - 2009-01-21
25025 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
25026 useful to users. It also finally fixes a bug where a relay or client
25027 that's been off for many days would take a long time to bootstrap.
25029 This update also fixes an important security-related bug reported by
25030 Ilja van Sprundel. You should upgrade. (We'll send out more details
25031 about the bug once people have had some time to upgrade.)
25034 - Fix a heap-corruption bug that may be remotely triggerable on
25035 some platforms. Reported by Ilja van Sprundel.
25038 - When a stream at an exit relay is in state "resolving" or
25039 "connecting" and it receives an "end" relay cell, the exit relay
25040 would silently ignore the end cell and not close the stream. If
25041 the client never closes the circuit, then the exit relay never
25042 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
25043 reported by "wood".
25044 - When sending CREATED cells back for a given circuit, use a 64-bit
25045 connection ID to find the right connection, rather than an addr:port
25046 combination. Now that we can have multiple OR connections between
25047 the same ORs, it is no longer possible to use addr:port to uniquely
25048 identify a connection.
25049 - Bridge relays that had DirPort set to 0 would stop fetching
25050 descriptors shortly after startup, and then briefly resume
25051 after a new bandwidth test and/or after publishing a new bridge
25052 descriptor. Bridge users that try to bootstrap from them would
25053 get a recent networkstatus but would get descriptors from up to
25054 18 hours earlier, meaning most of the descriptors were obsolete
25055 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
25056 - Prevent bridge relays from serving their 'extrainfo' document
25057 to anybody who asks, now that extrainfo docs include potentially
25058 sensitive aggregated client geoip summaries. Bugfix on
25060 - If the cached networkstatus consensus is more than five days old,
25061 discard it rather than trying to use it. In theory it could be
25062 useful because it lists alternate directory mirrors, but in practice
25063 it just means we spend many minutes trying directory mirrors that
25064 are long gone from the network. Also discard router descriptors as
25065 we load them if they are more than five days old, since the onion
25066 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
25069 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25070 could make gcc generate non-functional binary search code. Bugfix
25072 - Build correctly on platforms without socklen_t.
25073 - Compile without warnings on solaris.
25074 - Avoid potential crash on internal error during signature collection.
25075 Fixes bug 864. Patch from rovv.
25076 - Correct handling of possible malformed authority signing key
25077 certificates with internal signature types. Fixes bug 880.
25078 Bugfix on 0.2.0.3-alpha.
25079 - Fix a hard-to-trigger resource leak when logging credential status.
25081 - When we can't initialize DNS because the network is down, do not
25082 automatically stop Tor from starting. Instead, we retry failed
25083 dns_init() every 10 minutes, and change the exit policy to reject
25084 *:* until one succeeds. Fixes bug 691.
25085 - Use 64 bits instead of 32 bits for connection identifiers used with
25086 the controller protocol, to greatly reduce risk of identifier reuse.
25087 - When we're choosing an exit node for a circuit, and we have
25088 no pending streams, choose a good general exit rather than one that
25089 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25090 - Fix another case of assuming, when a specific exit is requested,
25091 that we know more than the user about what hosts it allows.
25092 Fixes one case of bug 752. Patch from rovv.
25093 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25094 seconds. Warn the user if lower values are given in the
25095 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25096 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25097 user if lower values are given in the configuration. Bugfix on
25098 0.1.1.17-rc. Patch by Sebastian.
25099 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
25100 the cache because we already had a v0 descriptor with the same ID.
25101 Bugfix on 0.2.0.18-alpha.
25102 - Fix a race condition when freeing keys shared between main thread
25103 and CPU workers that could result in a memory leak. Bugfix on
25104 0.1.0.1-rc. Fixes bug 889.
25105 - Send a valid END cell back when a client tries to connect to a
25106 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25107 840. Patch from rovv.
25108 - Check which hops rendezvous stream cells are associated with to
25109 prevent possible guess-the-streamid injection attacks from
25110 intermediate hops. Fixes another case of bug 446. Based on patch
25112 - If a broken client asks a non-exit router to connect somewhere,
25113 do not even do the DNS lookup before rejecting the connection.
25114 Fixes another case of bug 619. Patch from rovv.
25115 - When a relay gets a create cell it can't decrypt (e.g. because it's
25116 using the wrong onion key), we were dropping it and letting the
25117 client time out. Now actually answer with a destroy cell. Fixes
25118 bug 904. Bugfix on 0.0.2pre8.
25120 o Minor bugfixes (hidden services):
25121 - Do not throw away existing introduction points on SIGHUP. Bugfix on
25122 0.0.6pre1. Patch by Karsten. Fixes bug 874.
25125 - Report the case where all signatures in a detached set are rejected
25126 differently than the case where there is an error handling the
25128 - When we realize that another process has modified our cached
25129 descriptors, print out a more useful error message rather than
25130 triggering an assertion. Fixes bug 885. Patch from Karsten.
25131 - Implement the 0x20 hack to better resist DNS poisoning: set the
25132 case on outgoing DNS requests randomly, and reject responses that do
25133 not match the case correctly. This logic can be disabled with the
25134 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
25135 of servers that do not reliably preserve case in replies. See
25136 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25138 - Check DNS replies for more matching fields to better resist DNS
25140 - Never use OpenSSL compression: it wastes RAM and CPU trying to
25141 compress cells, which are basically all encrypted, compressed, or
25145 Changes in version 0.2.1.11-alpha - 2009-01-20
25146 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
25147 week it will take a long time to bootstrap again" bug. It also fixes
25148 an important security-related bug reported by Ilja van Sprundel. You
25149 should upgrade. (We'll send out more details about the bug once people
25150 have had some time to upgrade.)
25153 - Fix a heap-corruption bug that may be remotely triggerable on
25154 some platforms. Reported by Ilja van Sprundel.
25157 - Discard router descriptors as we load them if they are more than
25158 five days old. Otherwise if Tor is off for a long time and then
25159 starts with cached descriptors, it will try to use the onion
25160 keys in those obsolete descriptors when building circuits. Bugfix
25161 on 0.2.0.x. Fixes bug 887.
25164 - Try to make sure that the version of Libevent we're running with
25165 is binary-compatible with the one we built with. May address bug
25167 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
25168 for bug 905. Bugfix on 0.2.1.7-alpha.
25169 - Add a new --enable-local-appdata configuration switch to change
25170 the default location of the datadir on win32 from APPDATA to
25171 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
25172 entirely. Patch from coderman.
25175 - Make outbound DNS packets respect the OutboundBindAddress setting.
25176 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
25177 - When our circuit fails at the first hop (e.g. we get a destroy
25178 cell back), avoid using that OR connection anymore, and also
25179 tell all the one-hop directory requests waiting for it that they
25180 should fail. Bugfix on 0.2.1.3-alpha.
25181 - In the torify(1) manpage, mention that tsocks will leak your
25185 Changes in version 0.2.1.10-alpha - 2009-01-06
25186 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
25187 would make the bridge relay not so useful if it had DirPort set to 0,
25188 and one that could let an attacker learn a little bit of information
25189 about the bridge's users), and a bug that would cause your Tor relay
25190 to ignore a circuit create request it can't decrypt (rather than reply
25191 with an error). It also fixes a wide variety of other bugs.
25194 - If the cached networkstatus consensus is more than five days old,
25195 discard it rather than trying to use it. In theory it could
25196 be useful because it lists alternate directory mirrors, but in
25197 practice it just means we spend many minutes trying directory
25198 mirrors that are long gone from the network. Helps bug 887 a bit;
25200 - Bridge relays that had DirPort set to 0 would stop fetching
25201 descriptors shortly after startup, and then briefly resume
25202 after a new bandwidth test and/or after publishing a new bridge
25203 descriptor. Bridge users that try to bootstrap from them would
25204 get a recent networkstatus but would get descriptors from up to
25205 18 hours earlier, meaning most of the descriptors were obsolete
25206 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
25207 - Prevent bridge relays from serving their 'extrainfo' document
25208 to anybody who asks, now that extrainfo docs include potentially
25209 sensitive aggregated client geoip summaries. Bugfix on
25213 - New controller event "clients_seen" to report a geoip-based summary
25214 of which countries we've seen clients from recently. Now controllers
25215 like Vidalia can show bridge operators that they're actually making
25217 - Build correctly against versions of OpenSSL 0.9.8 or later built
25218 without support for deprecated functions.
25219 - Update to the "December 19 2008" ip-to-country file.
25221 o Minor bugfixes (on 0.2.0.x):
25222 - Authorities now vote for the Stable flag for any router whose
25223 weighted MTBF is at least 5 days, regardless of the mean MTBF.
25224 - Do not remove routers as too old if we do not have any consensus
25225 document. Bugfix on 0.2.0.7-alpha.
25226 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
25227 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
25228 - When an exit relay resolves a stream address to a local IP address,
25229 do not just keep retrying that same exit relay over and
25230 over. Instead, just close the stream. Addresses bug 872. Bugfix
25231 on 0.2.0.32. Patch from rovv.
25232 - If a hidden service sends us an END cell, do not consider
25233 retrying the connection; just close it. Patch from rovv.
25234 - When we made bridge authorities stop serving bridge descriptors over
25235 unencrypted links, we also broke DirPort reachability testing for
25236 bridges. So bridges with a non-zero DirPort were printing spurious
25237 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
25238 - When a relay gets a create cell it can't decrypt (e.g. because it's
25239 using the wrong onion key), we were dropping it and letting the
25240 client time out. Now actually answer with a destroy cell. Fixes
25241 bug 904. Bugfix on 0.0.2pre8.
25242 - Squeeze 2-5% out of client performance (according to oprofile) by
25243 improving the implementation of some policy-manipulation functions.
25245 o Minor bugfixes (on 0.2.1.x):
25246 - Make get_interface_address() function work properly again; stop
25247 guessing the wrong parts of our address as our address.
25248 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
25249 send on that circuit. Otherwise we might violate the proposal-110
25250 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
25252 - When we're sending non-EXTEND cells to the first hop in a circuit,
25253 for example to use an encrypted directory connection, we don't need
25254 to use RELAY_EARLY cells: the first hop knows what kind of cell
25255 it is, and nobody else can even see the cell type. Conserving
25256 RELAY_EARLY cells makes it easier to cannibalize circuits like
25258 - Stop logging nameserver addresses in reverse order.
25259 - If we are retrying a directory download slowly over and over, do
25260 not automatically give up after the 254th failure. Bugfix on
25262 - Resume reporting accurate "stream end" reasons to the local control
25263 port. They were lost in the changes for Proposal 148. Bugfix on
25266 o Deprecated and removed features:
25267 - The old "tor --version --version" command, which would print out
25268 the subversion "Id" of most of the source files, is now removed. It
25269 turned out to be less useful than we'd expected, and harder to
25272 o Code simplifications and refactoring:
25273 - Change our header file guard macros to be less likely to conflict
25274 with system headers. Adam Langley noticed that we were conflicting
25275 with log.h on Android.
25276 - Tool-assisted documentation cleanup. Nearly every function or
25277 static variable in Tor should have its own documentation now.
25280 Changes in version 0.2.1.9-alpha - 2008-12-25
25281 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
25283 o New directory authorities:
25284 - gabelmoo (the authority run by Karsten Loesing) now has a new
25288 - Never use a connection with a mismatched address to extend a
25289 circuit, unless that connection is canonical. A canonical
25290 connection is one whose address is authenticated by the router's
25291 identity key, either in a NETINFO cell or in a router descriptor.
25292 - Avoid a possible memory corruption bug when receiving hidden service
25293 descriptors. Bugfix on 0.2.1.6-alpha.
25296 - Fix a logic error that would automatically reject all but the first
25297 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
25298 part of bug 813/868. Bug spotted by coderman.
25299 - When a stream at an exit relay is in state "resolving" or
25300 "connecting" and it receives an "end" relay cell, the exit relay
25301 would silently ignore the end cell and not close the stream. If
25302 the client never closes the circuit, then the exit relay never
25303 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
25304 reported by "wood".
25305 - When we can't initialize DNS because the network is down, do not
25306 automatically stop Tor from starting. Instead, retry failed
25307 dns_init() every 10 minutes, and change the exit policy to reject
25308 *:* until one succeeds. Fixes bug 691.
25311 - Give a better error message when an overzealous init script says
25312 "sudo -u username tor --user username". Makes Bug 882 easier for
25314 - When a directory authority gives us a new guess for our IP address,
25315 log which authority we used. Hopefully this will help us debug
25316 the recent complaints about bad IP address guesses.
25317 - Detect svn revision properly when we're using git-svn.
25318 - Try not to open more than one descriptor-downloading connection
25319 to an authority at once. This should reduce load on directory
25320 authorities. Fixes bug 366.
25321 - Add cross-certification to newly generated certificates, so that
25322 a signing key is enough information to look up a certificate.
25323 Partial implementation of proposal 157.
25324 - Start serving certificates by <identity digest, signing key digest>
25325 pairs. Partial implementation of proposal 157.
25326 - Clients now never report any stream end reason except 'MISC'.
25327 Implements proposal 148.
25328 - On platforms with a maximum syslog string length, truncate syslog
25329 messages to that length ourselves, rather than relying on the
25330 system to do it for us.
25331 - Optimize out calls to time(NULL) that occur for every IO operation,
25332 or for every cell. On systems where time() is a slow syscall,
25333 this fix will be slightly helpful.
25334 - Exit servers can now answer resolve requests for ip6.arpa addresses.
25335 - When we download a descriptor that we then immediately (as
25336 a directory authority) reject, do not retry downloading it right
25337 away. Should save some bandwidth on authorities. Fix for bug
25338 888. Patch by Sebastian Hahn.
25339 - When a download gets us zero good descriptors, do not notify
25340 Tor that new directory information has arrived.
25341 - Avoid some nasty corner cases in the logic for marking connections
25342 as too old or obsolete or noncanonical for circuits. Partial
25345 o Minor features (controller):
25346 - New CONSENSUS_ARRIVED event to note when a new consensus has
25347 been fetched and validated.
25348 - When we realize that another process has modified our cached
25349 descriptors file, print out a more useful error message rather
25350 than triggering an assertion. Fixes bug 885. Patch from Karsten.
25351 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
25352 controllers to prevent SIGHUP from reloading the
25353 configuration. Fixes bug 856.
25356 - Resume using the correct "REASON=" stream when telling the
25357 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
25358 - When a canonical connection appears later in our internal list
25359 than a noncanonical one for a given OR ID, always use the
25360 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
25362 - Clip the MaxCircuitDirtiness config option to a minimum of 10
25363 seconds. Warn the user if lower values are given in the
25364 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
25365 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
25366 user if lower values are given in the configuration. Bugfix on
25367 0.1.1.17-rc. Patch by Sebastian.
25368 - Fix a race condition when freeing keys shared between main thread
25369 and CPU workers that could result in a memory leak. Bugfix on
25370 0.1.0.1-rc. Fixes bug 889.
25372 o Minor bugfixes (hidden services):
25373 - Do not throw away existing introduction points on SIGHUP (bugfix on
25374 0.0.6pre1); also, do not stall hidden services because we're
25375 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
25376 by John Brooks. Patch by Karsten. Fixes bug 874.
25377 - Fix a memory leak when we decline to add a v2 rendezvous
25378 descriptor to the cache because we already had a v0 descriptor
25379 with the same ID. Bugfix on 0.2.0.18-alpha.
25381 o Deprecated and removed features:
25382 - RedirectExits has been removed. It was deprecated since
25384 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
25385 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
25386 - Cell pools are now always enabled; --disable-cell-pools is ignored.
25388 o Code simplifications and refactoring:
25389 - Rename the confusing or_is_obsolete field to the more appropriate
25390 is_bad_for_new_circs, and move it to or_connection_t where it
25392 - Move edge-only flags from connection_t to edge_connection_t: not
25393 only is this better coding, but on machines of plausible alignment,
25394 it should save 4-8 bytes per connection_t. "Every little bit helps."
25395 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
25396 for consistency; keep old option working for backward compatibility.
25397 - Simplify the code for finding connections to use for a circuit.
25400 Changes in version 0.2.1.8-alpha - 2008-12-08
25401 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
25402 builds better on unusual platforms like Solaris and old OS X, and
25403 fixes a variety of other issues.
25406 - New DirPortFrontPage option that takes an html file and publishes
25407 it as "/" on the DirPort. Now relay operators can provide a
25408 disclaimer without needing to set up a separate webserver. There's
25409 a sample disclaimer in contrib/tor-exit-notice.html.
25412 - When the client is choosing entry guards, now it selects at most
25413 one guard from a given relay family. Otherwise we could end up with
25414 all of our entry points into the network run by the same operator.
25415 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
25418 - Fix a DOS opportunity during the voting signature collection process
25419 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25420 - Fix a possible segfault when establishing an exit connection. Bugfix
25424 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
25426 - Made Tor a little less aggressive about deleting expired
25427 certificates. Partial fix for bug 854.
25428 - Stop doing unaligned memory access that generated bus errors on
25429 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
25430 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
25431 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
25432 - Make USR2 log-level switch take effect immediately. Bugfix on
25434 - If one win32 nameserver fails to get added, continue adding the
25435 rest, and don't automatically fail.
25436 - Use fcntl() for locking when flock() is not available. Should fix
25437 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
25438 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
25439 could make gcc generate non-functional binary search code. Bugfix
25441 - Build correctly on platforms without socklen_t.
25442 - Avoid potential crash on internal error during signature collection.
25443 Fixes bug 864. Patch from rovv.
25444 - Do not use C's stdio library for writing to log files. This will
25445 improve logging performance by a minute amount, and will stop
25446 leaking fds when our disk is full. Fixes bug 861.
25447 - Stop erroneous use of O_APPEND in cases where we did not in fact
25448 want to re-seek to the end of a file before every last write().
25449 - Correct handling of possible malformed authority signing key
25450 certificates with internal signature types. Fixes bug 880. Bugfix
25452 - Fix a hard-to-trigger resource leak when logging credential status.
25456 - Directory mirrors no longer fetch the v1 directory or
25457 running-routers files. They are obsolete, and nobody asks for them
25458 anymore. This is the first step to making v1 authorities obsolete.
25460 o Minor features (controller):
25461 - Return circuit purposes in response to GETINFO circuit-status. Fixes
25465 Changes in version 0.2.0.32 - 2008-11-20
25466 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
25467 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25468 a smaller security flaw that might allow an attacker to access local
25469 services, further improves hidden service performance, and fixes a
25470 variety of other issues.
25473 - The "User" and "Group" config options did not clear the
25474 supplementary group entries for the Tor process. The "User" option
25475 is now more robust, and we now set the groups to the specified
25476 user's primary group. The "Group" option is now ignored. For more
25477 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25478 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25479 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
25480 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25481 consistently obeyed: if an exit relay refuses a stream because its
25482 exit policy doesn't allow it, we would remember what IP address
25483 the relay said the destination address resolves to, even if it's
25484 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25487 - Fix a DOS opportunity during the voting signature collection process
25488 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
25490 o Major bugfixes (hidden services):
25491 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25492 we were failing the whole hidden service request when the v0
25493 descriptor fetch fails, even if the v2 fetch is still pending and
25494 might succeed. Similarly, if the last v2 fetch fails, we were
25495 failing the whole hidden service request even if a v0 fetch is
25496 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25497 - When extending a circuit to a hidden service directory to upload a
25498 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25499 requests failed, because the router descriptor has not been
25500 downloaded yet. In these cases, do not attempt to upload the
25501 rendezvous descriptor, but wait until the router descriptor is
25502 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
25503 descriptor from a hidden service directory for which the router
25504 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
25508 - Fix several infrequent memory leaks spotted by Coverity.
25509 - When testing for libevent functions, set the LDFLAGS variable
25510 correctly. Found by Riastradh.
25511 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25512 bootstrapping with tunneled directory connections. Bugfix on
25513 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25514 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25515 and we know that server B rejects most-but-not all connections to
25516 port 80, we would previously reject the connection. Now, we assume
25517 the user knows what they were asking for. Fixes bug 752. Bugfix
25518 on 0.0.9rc5. Diagnosed by BarkerJr.
25519 - If we overrun our per-second write limits a little, count this as
25520 having used up our write allocation for the second, and choke
25521 outgoing directory writes. Previously, we had only counted this when
25522 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
25523 Bugfix on 0.2.0.x (??).
25524 - Remove the old v2 directory authority 'lefkada' from the default
25525 list. It has been gone for many months.
25526 - Stop doing unaligned memory access that generated bus errors on
25527 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
25528 - Make USR2 log-level switch take effect immediately. Bugfix on
25531 o Minor bugfixes (controller):
25532 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
25533 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
25536 Changes in version 0.2.1.7-alpha - 2008-11-08
25537 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
25538 packages (and maybe other packages) noticed by Theo de Raadt, fixes
25539 a smaller security flaw that might allow an attacker to access local
25540 services, adds better defense against DNS poisoning attacks on exit
25541 relays, further improves hidden service performance, and fixes a
25542 variety of other issues.
25545 - The "ClientDNSRejectInternalAddresses" config option wasn't being
25546 consistently obeyed: if an exit relay refuses a stream because its
25547 exit policy doesn't allow it, we would remember what IP address
25548 the relay said the destination address resolves to, even if it's
25549 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
25550 - The "User" and "Group" config options did not clear the
25551 supplementary group entries for the Tor process. The "User" option
25552 is now more robust, and we now set the groups to the specified
25553 user's primary group. The "Group" option is now ignored. For more
25554 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
25555 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
25556 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
25557 - Do not use or believe expired v3 authority certificates. Patch
25558 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
25561 - Now NodeFamily and MyFamily config options allow spaces in
25562 identity fingerprints, so it's easier to paste them in.
25563 Suggested by Lucky Green.
25564 - Implement the 0x20 hack to better resist DNS poisoning: set the
25565 case on outgoing DNS requests randomly, and reject responses that do
25566 not match the case correctly. This logic can be disabled with the
25567 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
25568 of servers that do not reliably preserve case in replies. See
25569 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
25571 - Preserve case in replies to DNSPort requests in order to support
25572 the 0x20 hack for resisting DNS poisoning attacks.
25574 o Hidden service performance improvements:
25575 - When the client launches an introduction circuit, retry with a
25576 new circuit after 30 seconds rather than 60 seconds.
25577 - Launch a second client-side introduction circuit in parallel
25578 after a delay of 15 seconds (based on work by Christian Wilms).
25579 - Hidden services start out building five intro circuits rather
25580 than three, and when the first three finish they publish a service
25581 descriptor using those. Now we publish our service descriptor much
25582 faster after restart.
25585 - Minor fix in the warning messages when you're having problems
25586 bootstrapping; also, be more forgiving of bootstrap problems when
25587 we're still making incremental progress on a given bootstrap phase.
25588 - When we're choosing an exit node for a circuit, and we have
25589 no pending streams, choose a good general exit rather than one that
25590 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
25591 - Send a valid END cell back when a client tries to connect to a
25592 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
25593 840. Patch from rovv.
25594 - If a broken client asks a non-exit router to connect somewhere,
25595 do not even do the DNS lookup before rejecting the connection.
25596 Fixes another case of bug 619. Patch from rovv.
25597 - Fix another case of assuming, when a specific exit is requested,
25598 that we know more than the user about what hosts it allows.
25599 Fixes another case of bug 752. Patch from rovv.
25600 - Check which hops rendezvous stream cells are associated with to
25601 prevent possible guess-the-streamid injection attacks from
25602 intermediate hops. Fixes another case of bug 446. Based on patch
25604 - Avoid using a negative right-shift when comparing 32-bit
25605 addresses. Possible fix for bug 845 and bug 811.
25606 - Make the assert_circuit_ok() function work correctly on circuits that
25607 have already been marked for close.
25608 - Fix read-off-the-end-of-string error in unit tests when decoding
25609 introduction points.
25610 - Fix uninitialized size field for memory area allocation: may improve
25611 memory performance during directory parsing.
25612 - Treat duplicate certificate fetches as failures, so that we do
25613 not try to re-fetch an expired certificate over and over and over.
25614 - Do not say we're fetching a certificate when we'll in fact skip it
25615 because of a pending download.
25618 Changes in version 0.2.1.6-alpha - 2008-09-30
25619 Tor 0.2.1.6-alpha further improves performance and robustness of
25620 hidden services, starts work on supporting per-country relay selection,
25621 and fixes a variety of smaller issues.
25624 - Implement proposal 121: make it possible to build hidden services
25625 that only certain clients are allowed to connect to. This is
25626 enforced at several points, so that unauthorized clients are unable
25627 to send INTRODUCE cells to the service, or even (depending on the
25628 type of authentication) to learn introduction points. This feature
25629 raises the bar for certain kinds of active attacks against hidden
25630 services. Code by Karsten Loesing.
25631 - Relays now store and serve v2 hidden service descriptors by default,
25632 i.e., the new default value for HidServDirectoryV2 is 1. This is
25633 the last step in proposal 114, which aims to make hidden service
25634 lookups more reliable.
25635 - Start work to allow node restrictions to include country codes. The
25636 syntax to exclude nodes in a country with country code XX is
25637 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
25638 refinement to decide what config options should take priority if
25639 you ask to both use a particular node and exclude it.
25640 - Allow ExitNodes list to include IP ranges and country codes, just
25641 like the Exclude*Nodes lists. Patch from Robert Hogan.
25644 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
25645 Tor to fail to start if you had it configured to use a bridge
25646 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
25647 - When extending a circuit to a hidden service directory to upload a
25648 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
25649 requests failed, because the router descriptor had not been
25650 downloaded yet. In these cases, we now wait until the router
25651 descriptor is downloaded, and then retry. Likewise, clients
25652 now skip over a hidden service directory if they don't yet have
25653 its router descriptor, rather than futilely requesting it and
25654 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
25656 - When fetching v0 and v2 rendezvous service descriptors in parallel,
25657 we were failing the whole hidden service request when the v0
25658 descriptor fetch fails, even if the v2 fetch is still pending and
25659 might succeed. Similarly, if the last v2 fetch fails, we were
25660 failing the whole hidden service request even if a v0 fetch is
25661 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
25662 - DNS replies need to have names matching their requests, but
25663 these names should be in the questions section, not necessarily
25664 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
25667 - Update to the "September 1 2008" ip-to-country file.
25668 - Allow ports 465 and 587 in the default exit policy again. We had
25669 rejected them in 0.1.0.15, because back in 2005 they were commonly
25670 misconfigured and ended up as spam targets. We hear they are better
25671 locked down these days.
25672 - Use a lockfile to make sure that two Tor processes are not
25673 simultaneously running with the same datadir.
25674 - Serve the latest v3 networkstatus consensus via the control
25675 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
25676 - Better logging about stability/reliability calculations on directory
25678 - Drop the requirement to have an open dir port for storing and
25679 serving v2 hidden service descriptors.
25680 - Directory authorities now serve a /tor/dbg-stability.txt URL to
25681 help debug WFU and MTBF calculations.
25682 - Implement most of Proposal 152: allow specialized servers to permit
25683 single-hop circuits, and clients to use those servers to build
25684 single-hop circuits when using a specialized controller. Patch
25685 from Josh Albrecht. Resolves feature request 768.
25686 - Add a -p option to tor-resolve for specifying the SOCKS port: some
25687 people find host:port too confusing.
25688 - Make TrackHostExit mappings expire a while after their last use, not
25689 after their creation. Patch from Robert Hogan.
25690 - Provide circuit purposes along with circuit events to the controller.
25693 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
25695 - Fixed some memory leaks -- some quite frequent, some almost
25696 impossible to trigger -- based on results from Coverity.
25697 - When testing for libevent functions, set the LDFLAGS variable
25698 correctly. Found by Riastradh.
25699 - Fix an assertion bug in parsing policy-related options; possible fix
25701 - Catch and report a few more bootstrapping failure cases when Tor
25702 fails to establish a TCP connection. Cleanup on 0.2.1.x.
25703 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
25704 bootstrapping with tunneled directory connections. Bugfix on
25705 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
25706 - When asked to connect to A.B.exit:80, if we don't know the IP for A
25707 and we know that server B rejects most-but-not all connections to
25708 port 80, we would previously reject the connection. Now, we assume
25709 the user knows what they were asking for. Fixes bug 752. Bugfix
25710 on 0.0.9rc5. Diagnosed by BarkerJr.
25711 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
25712 service directories if they have no advertised dir port. Bugfix
25714 - If we overrun our per-second write limits a little, count this as
25715 having used up our write allocation for the second, and choke
25716 outgoing directory writes. Previously, we had only counted this when
25717 we had met our limits precisely. Fixes bug 824. Patch by rovv.
25718 Bugfix on 0.2.0.x (??).
25719 - Avoid a "0 divided by 0" calculation when calculating router uptime
25720 at directory authorities. Bugfix on 0.2.0.8-alpha.
25721 - Make DNS resolved controller events into "CLOSED", not
25722 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
25724 - Fix a bug where an unreachable relay would establish enough
25725 reachability testing circuits to do a bandwidth test -- if
25726 we already have a connection to the middle hop of the testing
25727 circuit, then it could establish the last hop by using the existing
25728 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
25729 circuits no longer use entry guards in 0.2.1.3-alpha.
25730 - If we have correct permissions on $datadir, we complain to stdout
25731 and fail to start. But dangerous permissions on
25732 $datadir/cached-status/ would cause us to open a log and complain
25733 there. Now complain to stdout and fail to start in both cases. Fixes
25734 bug 820, reported by seeess.
25735 - Remove the old v2 directory authority 'lefkada' from the default
25736 list. It has been gone for many months.
25738 o Code simplifications and refactoring:
25739 - Revise the connection_new functions so that a more typesafe variant
25740 exists. This will work better with Coverity, and let us find any
25741 actual mistakes we're making here.
25742 - Refactor unit testing logic so that dmalloc can be used sensibly
25743 with unit tests to check for memory leaks.
25744 - Move all hidden-service related fields from connection and circuit
25745 structure to substructures: this way they won't eat so much memory.
25748 Changes in version 0.2.0.31 - 2008-09-03
25749 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
25750 a big bug we're seeing where in rare cases traffic from one Tor stream
25751 gets mixed into another stream, and fixes a variety of smaller issues.
25754 - Make sure that two circuits can never exist on the same connection
25755 with the same circuit ID, even if one is marked for close. This
25756 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
25757 - Relays now reject risky extend cells: if the extend cell includes
25758 a digest of all zeroes, or asks to extend back to the relay that
25759 sent the extend cell, tear down the circuit. Ideas suggested
25761 - If not enough of our entry guards are available so we add a new
25762 one, we might use the new one even if it overlapped with the
25763 current circuit's exit relay (or its family). Anonymity bugfix
25764 pointed out by rovv.
25767 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25768 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25769 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25770 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25771 - Pick size of default geoip filename string correctly on windows.
25772 Fixes bug 806. Bugfix on 0.2.0.30.
25773 - Make the autoconf script accept the obsolete --with-ssl-dir
25774 option as an alias for the actually-working --with-openssl-dir
25775 option. Fix the help documentation to recommend --with-openssl-dir.
25776 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25777 - When using the TransPort option on OpenBSD, and using the User
25778 option to change UID and drop privileges, make sure to open
25779 /dev/pf before dropping privileges. Fixes bug 782. Patch from
25780 Christopher Davis. Bugfix on 0.1.2.1-alpha.
25781 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25782 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25783 on the client side when connecting to a hidden service. Bugfix
25784 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25785 - When closing an application-side connection because its circuit is
25786 getting torn down, generate the stream event correctly. Bugfix on
25787 0.1.2.x. Anonymous patch.
25790 Changes in version 0.2.1.5-alpha - 2008-08-31
25791 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
25792 in a lot of the infrastructure for adding authorization to hidden
25793 services, lays the groundwork for having clients read their load
25794 balancing information out of the networkstatus consensus rather than
25795 the individual router descriptors, addresses two potential anonymity
25796 issues, and fixes a variety of smaller issues.
25799 - Convert many internal address representations to optionally hold
25801 - Generate and accept IPv6 addresses in many protocol elements.
25802 - Make resolver code handle nameservers located at ipv6 addresses.
25803 - Begin implementation of proposal 121 ("Client authorization for
25804 hidden services"): configure hidden services with client
25805 authorization, publish descriptors for them, and configure
25806 authorization data for hidden services at clients. The next
25807 step is to actually access hidden services that perform client
25809 - More progress toward proposal 141: Network status consensus
25810 documents and votes now contain bandwidth information for each
25811 router and a summary of that router's exit policy. Eventually this
25812 will be used by clients so that they do not have to download every
25813 known descriptor before building circuits.
25815 o Major bugfixes (on 0.2.0.x and before):
25816 - When sending CREATED cells back for a given circuit, use a 64-bit
25817 connection ID to find the right connection, rather than an addr:port
25818 combination. Now that we can have multiple OR connections between
25819 the same ORs, it is no longer possible to use addr:port to uniquely
25820 identify a connection.
25821 - Relays now reject risky extend cells: if the extend cell includes
25822 a digest of all zeroes, or asks to extend back to the relay that
25823 sent the extend cell, tear down the circuit. Ideas suggested
25825 - If not enough of our entry guards are available so we add a new
25826 one, we might use the new one even if it overlapped with the
25827 current circuit's exit relay (or its family). Anonymity bugfix
25828 pointed out by rovv.
25831 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
25832 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
25833 - When using the TransPort option on OpenBSD, and using the User
25834 option to change UID and drop privileges, make sure to open /dev/pf
25835 before dropping privileges. Fixes bug 782. Patch from Christopher
25836 Davis. Bugfix on 0.1.2.1-alpha.
25837 - Correctly detect the presence of the linux/netfilter_ipv4.h header
25838 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
25839 - Add a missing safe_str() call for a debug log message.
25840 - Use 64 bits instead of 32 bits for connection identifiers used with
25841 the controller protocol, to greatly reduce risk of identifier reuse.
25842 - Make the autoconf script accept the obsolete --with-ssl-dir
25843 option as an alias for the actually-working --with-openssl-dir
25844 option. Fix the help documentation to recommend --with-openssl-dir.
25845 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
25848 - Rate-limit too-many-sockets messages: when they happen, they happen
25849 a lot. Resolves bug 748.
25850 - Resist DNS poisoning a little better by making sure that names in
25851 answer sections match.
25852 - Print the SOCKS5 error message string as well as the error code
25853 when a tor-resolve request fails. Patch from Jacob.
25856 Changes in version 0.2.1.4-alpha - 2008-08-04
25857 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
25860 - The address part of exit policies was not correctly written
25861 to router descriptors. This generated router descriptors that failed
25862 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
25864 - Tor triggered a false assert when extending a circuit to a relay
25865 but we already have a connection open to that relay. Noticed by
25866 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
25869 - Fix a hidden service logging bug: in some edge cases, the router
25870 descriptor of a previously picked introduction point becomes
25871 obsolete and we need to give up on it rather than continually
25872 complaining that it has become obsolete. Observed by xiando. Bugfix
25875 o Removed features:
25876 - Take out the TestVia config option, since it was a workaround for
25877 a bug that was fixed in Tor 0.1.1.21.
25880 Changes in version 0.2.1.3-alpha - 2008-08-03
25881 Tor 0.2.1.3-alpha implements most of the pieces to prevent
25882 infinite-length circuit attacks (see proposal 110); fixes a bug that
25883 might cause exit relays to corrupt streams they send back; allows
25884 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
25885 ExcludeExitNodes config options; and fixes a big pile of bugs.
25887 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
25888 - Send a bootstrap problem "warn" event on the first problem if the
25889 reason is NO_ROUTE (that is, our network is down).
25892 - Implement most of proposal 110: The first K cells to be sent
25893 along a circuit are marked as special "early" cells; only K "early"
25894 cells will be allowed. Once this code is universal, we can block
25895 certain kinds of DOS attack by requiring that EXTEND commands must
25896 be sent using an "early" cell.
25899 - Try to attach connections immediately upon receiving a RENDEZVOUS2
25900 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
25901 on the client side when connecting to a hidden service. Bugfix
25902 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
25903 - Ensure that two circuits can never exist on the same connection
25904 with the same circuit ID, even if one is marked for close. This
25905 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
25908 - When relays do their initial bandwidth measurement, don't limit
25909 to just our entry guards for the test circuits. Otherwise we tend
25910 to have multiple test circuits going through a single entry guard,
25911 which makes our bandwidth test less accurate. Fixes part of bug 654;
25912 patch contributed by Josh Albrecht.
25913 - Add an ExcludeExitNodes option so users can list a set of nodes
25914 that should be be excluded from the exit node position, but
25915 allowed elsewhere. Implements proposal 151.
25916 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
25917 ExcludeNodes and ExcludeExitNodes lists.
25918 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
25919 be more efficient. Formerly it was quadratic in the number of
25920 servers; now it should be linear. Fixes bug 509.
25921 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
25922 and n_conn_id_digest fields into a separate structure that's
25923 only needed when the circuit has not yet attached to an n_conn.
25926 - Change the contrib/tor.logrotate script so it makes the new
25927 logs as "_tor:_tor" rather than the default, which is generally
25928 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
25929 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25930 warnings (occasionally), but it can also cause the compiler to
25931 eliminate error-checking code. Suggested by Peter Gutmann.
25932 - When a hidden service is giving up on an introduction point candidate
25933 that was not included in the last published rendezvous descriptor,
25934 don't reschedule publication of the next descriptor. Fixes bug 763.
25936 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
25937 HiddenServiceExcludeNodes as obsolete: they never worked properly,
25938 and nobody claims to be using them. Fixes bug 754. Bugfix on
25939 0.1.0.1-rc. Patch from Christian Wilms.
25940 - Fix a small alignment and memory-wasting bug on buffer chunks.
25943 o Minor bugfixes (controller):
25944 - When closing an application-side connection because its circuit
25945 is getting torn down, generate the stream event correctly.
25946 Bugfix on 0.1.2.x. Anonymous patch.
25948 o Removed features:
25949 - Remove all backward-compatibility code to support relays running
25950 versions of Tor so old that they no longer work at all on the
25954 Changes in version 0.2.0.30 - 2008-07-15
25956 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
25957 warnings (occasionally), but it can also cause the compiler to
25958 eliminate error-checking code. Suggested by Peter Gutmann.
25961 Changes in version 0.2.0.29-rc - 2008-07-08
25962 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
25963 hidden-service performance bugs, and fixes a bunch of smaller bugs.
25966 - If you have more than one bridge but don't know their keys,
25967 you would only launch a request for the descriptor of the first one
25968 on your list. (Tor considered launching requests for the others, but
25969 found that it already had a connection on the way for $0000...0000
25970 so it didn't open another.) Bugfix on 0.2.0.x.
25971 - If you have more than one bridge but don't know their keys, and the
25972 connection to one of the bridges failed, you would cancel all
25973 pending bridge connections. (After all, they all have the same
25974 digest.) Bugfix on 0.2.0.x.
25975 - When a hidden service was trying to establish an introduction point,
25976 and Tor had built circuits preemptively for such purposes, we
25977 were ignoring all the preemptive circuits and launching a new one
25978 instead. Bugfix on 0.2.0.14-alpha.
25979 - When a hidden service was trying to establish an introduction point,
25980 and Tor *did* manage to reuse one of the preemptively built
25981 circuits, it didn't correctly remember which one it used,
25982 so it asked for another one soon after, until there were no
25983 more preemptive circuits, at which point it launched one from
25984 scratch. Bugfix on 0.0.9.x.
25985 - Make directory servers include the X-Your-Address-Is: http header in
25986 their responses even for begin_dir conns. Now clients who only
25987 ever use begin_dir connections still have a way to learn their IP
25988 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
25991 - Fix a macro/CPP interaction that was confusing some compilers:
25992 some GCCs don't like #if/#endif pairs inside macro arguments.
25994 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
25995 Fixes bug 704; fix from Steven Murdoch.
25996 - When opening /dev/null in finish_daemonize(), do not pass the
25997 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
25998 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
25999 - Correctly detect transparent proxy support on Linux hosts that
26000 require in.h to be included before netfilter_ipv4.h. Patch
26002 - Disallow session resumption attempts during the renegotiation
26003 stage of the v2 handshake protocol. Clients should never be trying
26004 session resumption at this point, but apparently some did, in
26005 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
26006 found by Geoff Goodell.
26009 Changes in version 0.2.1.2-alpha - 2008-06-20
26010 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
26011 make it easier to set up your own private Tor network; fixes several
26012 big bugs with using more than one bridge relay; fixes a big bug with
26013 offering hidden services quickly after Tor starts; and uses a better
26014 API for reporting potential bootstrapping problems to the controller.
26017 - New TestingTorNetwork config option to allow adjustment of
26018 previously constant values that, while reasonable, could slow
26019 bootstrapping. Implements proposal 135. Patch from Karsten.
26022 - If you have more than one bridge but don't know their digests,
26023 you would only learn a request for the descriptor of the first one
26024 on your list. (Tor considered launching requests for the others, but
26025 found that it already had a connection on the way for $0000...0000
26026 so it didn't open another.) Bugfix on 0.2.0.x.
26027 - If you have more than one bridge but don't know their digests,
26028 and the connection to one of the bridges failed, you would cancel
26029 all pending bridge connections. (After all, they all have the
26030 same digest.) Bugfix on 0.2.0.x.
26031 - When establishing a hidden service, introduction points that
26032 originate from cannibalized circuits are completely ignored and not
26033 included in rendezvous service descriptors. This might be another
26034 reason for delay in making a hidden service available. Bugfix
26035 from long ago (0.0.9.x?)
26038 - Allow OpenSSL to use dynamic locks if it wants.
26039 - When building a consensus, do not include routers that are down.
26040 This will cut down 30% to 40% on consensus size. Implements
26042 - In directory authorities' approved-routers files, allow
26043 fingerprints with or without space.
26044 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
26045 controller can query our current bootstrap state in case it attaches
26046 partway through and wants to catch up.
26047 - Send an initial "Starting" bootstrap status event, so we have a
26048 state to start out in.
26051 - Asking for a conditional consensus at .../consensus/<fingerprints>
26052 would crash a dirserver if it did not already have a
26053 consensus. Bugfix on 0.2.1.1-alpha.
26054 - Clean up some macro/CPP interactions: some GCC versions don't like
26055 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
26058 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
26059 - Directory authorities shouldn't complain about bootstrapping
26060 problems just because they do a lot of reachability testing and
26061 some of the connection attempts fail.
26062 - Start sending "count" and "recommendation" key/value pairs in
26063 bootstrap problem status events, so the controller can hear about
26064 problems even before Tor decides they're worth reporting for sure.
26065 - If you're using bridges, generate "bootstrap problem" warnings
26066 as soon as you run out of working bridges, rather than waiting
26067 for ten failures -- which will never happen if you have less than
26069 - If we close our OR connection because there's been a circuit
26070 pending on it for too long, we were telling our bootstrap status
26071 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
26074 Changes in version 0.2.1.1-alpha - 2008-06-13
26075 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
26076 were making the Tor process bloat especially on Linux; makes our TLS
26077 handshake blend in better; sends "bootstrap phase" status events to
26078 the controller, so it can keep the user informed of progress (and
26079 problems) fetching directory information and establishing circuits;
26080 and adds a variety of smaller features.
26083 - More work on making our TLS handshake blend in: modify the list
26084 of ciphers advertised by OpenSSL in client mode to even more
26085 closely resemble a common web browser. We cheat a little so that
26086 we can advertise ciphers that the locally installed OpenSSL doesn't
26088 - Start sending "bootstrap phase" status events to the controller,
26089 so it can keep the user informed of progress fetching directory
26090 information and establishing circuits. Also inform the controller
26091 if we think we're stuck at a particular bootstrap phase. Implements
26093 - Resume using OpenSSL's RAND_poll() for better (and more portable)
26094 cross-platform entropy collection again. We used to use it, then
26095 stopped using it because of a bug that could crash systems that
26096 called RAND_poll when they had a lot of fds open. It looks like the
26097 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
26098 at startup, and to call RAND_poll() when we reseed later only if
26099 we have a non-buggy OpenSSL version.
26102 - When we choose to abandon a new entry guard because we think our
26103 older ones might be better, close any circuits pending on that
26104 new entry guard connection. This fix should make us recover much
26105 faster when our network is down and then comes back. Bugfix on
26106 0.1.2.8-beta; found by lodger.
26108 o Memory fixes and improvements:
26109 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
26110 to avoid unused RAM in buffer chunks and memory pools.
26111 - Speed up parsing and cut down on memory fragmentation by using
26112 stack-style allocations for parsing directory objects. Previously,
26113 this accounted for over 40% of allocations from within Tor's code
26114 on a typical directory cache.
26115 - Use a Bloom filter rather than a digest-based set to track which
26116 descriptors we need to keep around when we're cleaning out old
26117 router descriptors. This speeds up the computation significantly,
26118 and may reduce fragmentation.
26119 - Reduce the default smartlist size from 32 to 16; it turns out that
26120 most smartlists hold around 8-12 elements tops.
26121 - Make dumpstats() log the fullness and size of openssl-internal
26123 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
26124 patch to their OpenSSL, turn it on to save memory on servers. This
26125 patch will (with any luck) get included in a mainline distribution
26127 - Never use OpenSSL compression: it wastes RAM and CPU trying to
26128 compress cells, which are basically all encrypted, compressed,
26132 - Stop reloading the router list from disk for no reason when we
26133 run out of reachable directory mirrors. Once upon a time reloading
26134 it would set the 'is_running' flag back to 1 for them. It hasn't
26135 done that for a long time.
26136 - In very rare situations new hidden service descriptors were
26137 published earlier than 30 seconds after the last change to the
26138 service. (We currently think that a hidden service descriptor
26139 that's been stable for 30 seconds is worth publishing.)
26142 - Allow separate log levels to be configured for different logging
26143 domains. For example, this allows one to log all notices, warnings,
26144 or errors, plus all memory management messages of level debug or
26145 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
26146 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
26147 and stop using a warning that had become unfixably verbose under
26149 - New --hush command-line option similar to --quiet. While --quiet
26150 disables all logging to the console on startup, --hush limits the
26151 output to messages of warning and error severity.
26152 - Servers support a new URL scheme for consensus downloads that
26153 allows the client to specify which authorities are trusted.
26154 The server then only sends the consensus if the client will trust
26155 it. Otherwise a 404 error is sent back. Clients use this
26156 new scheme when the server supports it (meaning it's running
26157 0.2.1.1-alpha or later). Implements proposal 134.
26158 - New configure/torrc options (--enable-geoip-stats,
26159 DirRecordUsageByCountry) to record how many IPs we've served
26160 directory info to in each country code, how many status documents
26161 total we've sent to each country code, and what share of the total
26162 directory requests we should expect to see.
26163 - Use the TLS1 hostname extension to more closely resemble browser
26165 - Lots of new unit tests.
26166 - Add a macro to implement the common pattern of iterating through
26167 two parallel lists in lockstep.
26170 Changes in version 0.2.0.28-rc - 2008-06-13
26171 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
26172 performance bug, and fixes a bunch of smaller bugs.
26175 - Fix a bug where, when we were choosing the 'end stream reason' to
26176 put in our relay end cell that we send to the exit relay, Tor
26177 clients on Windows were sometimes sending the wrong 'reason'. The
26178 anonymity problem is that exit relays may be able to guess whether
26179 the client is running Windows, thus helping partition the anonymity
26180 set. Down the road we should stop sending reasons to exit relays,
26181 or otherwise prevent future versions of this bug.
26184 - While setting up a hidden service, some valid introduction circuits
26185 were overlooked and abandoned. This might be the reason for
26186 the long delay in making a hidden service available. Bugfix on
26190 - Update to the "June 9 2008" ip-to-country file.
26191 - Run 'make test' as part of 'make dist', so we stop releasing so
26192 many development snapshots that fail their unit tests.
26195 - When we're checking if we have enough dir info for each relay
26196 to begin establishing circuits, make sure that we actually have
26197 the descriptor listed in the consensus, not just any descriptor.
26199 - Bridge relays no longer print "xx=0" in their extrainfo document
26200 for every single country code in the geoip db. Bugfix on
26202 - Only warn when we fail to load the geoip file if we were planning to
26203 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
26204 - If we change our MaxAdvertisedBandwidth and then reload torrc,
26205 Tor won't realize it should publish a new relay descriptor. Fixes
26206 bug 688, reported by mfr. Bugfix on 0.1.2.x.
26207 - When we haven't had any application requests lately, don't bother
26208 logging that we have expired a bunch of descriptors. Bugfix
26210 - Make relay cells written on a connection count as non-padding when
26211 tracking how long a connection has been in use. Bugfix on
26212 0.2.0.1-alpha. Spotted by lodger.
26213 - Fix unit tests in 0.2.0.27-rc.
26214 - Fix compile on Windows.
26217 Changes in version 0.2.0.27-rc - 2008-06-03
26218 Tor 0.2.0.27-rc adds a few features we left out of the earlier
26219 release candidates. In particular, we now include an IP-to-country
26220 GeoIP database, so controllers can easily look up what country a
26221 given relay is in, and so bridge relays can give us some sanitized
26222 summaries about which countries are making use of bridges. (See proposal
26223 126-geoip-fetching.txt for details.)
26226 - Include an IP-to-country GeoIP file in the tarball, so bridge
26227 relays can report sanitized summaries of the usage they're seeing.
26230 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
26231 Robert Hogan. Fixes the first part of bug 681.
26232 - Make bridge authorities never serve extrainfo docs.
26233 - Add support to detect Libevent versions in the 1.4.x series
26235 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
26236 - Include a new contrib/tor-exit-notice.html file that exit relay
26237 operators can put on their website to help reduce abuse queries.
26240 - When tunneling an encrypted directory connection, and its first
26241 circuit fails, do not leave it unattached and ask the controller
26242 to deal. Fixes the second part of bug 681.
26243 - Make bridge authorities correctly expire old extrainfo documents
26247 Changes in version 0.2.0.26-rc - 2008-05-13
26248 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
26249 in Debian's OpenSSL packages. All users running any 0.2.0.x version
26250 should upgrade, whether they're running Debian or not.
26252 o Major security fixes:
26253 - Use new V3 directory authority keys on the tor26, gabelmoo, and
26254 moria1 V3 directory authorities. The old keys were generated with
26255 a vulnerable version of Debian's OpenSSL package, and must be
26256 considered compromised. Other authorities' keys were not generated
26257 with an affected version of OpenSSL.
26260 - List authority signatures as "unrecognized" based on DirServer
26261 lines, not on cert cache. Bugfix on 0.2.0.x.
26264 - Add a new V3AuthUseLegacyKey option to make it easier for
26265 authorities to change their identity keys if they have to.
26268 Changes in version 0.2.0.25-rc - 2008-04-23
26269 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
26272 - Remember to initialize threading before initializing logging.
26273 Otherwise, many BSD-family implementations will crash hard on
26274 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
26277 - Authorities correctly free policies on bad servers on
26278 exit. Fixes bug 672. Bugfix on 0.2.0.x.
26281 Changes in version 0.2.0.24-rc - 2008-04-22
26282 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
26283 v3 directory authority, makes relays with dynamic IP addresses and no
26284 DirPort notice more quickly when their IP address changes, fixes a few
26285 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
26287 o New directory authorities:
26288 - Take lefkada out of the list of v3 directory authorities, since
26289 it has been down for months.
26290 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
26294 - Detect address changes more quickly on non-directory mirror
26295 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
26297 o Minor features (security):
26298 - Reject requests for reverse-dns lookup of names that are in
26299 a private address space. Patch from lodger.
26300 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
26303 o Minor bugfixes (crashes):
26304 - Avoid a rare assert that can trigger when Tor doesn't have much
26305 directory information yet and it tries to fetch a v2 hidden
26306 service descriptor. Fixes bug 651, reported by nwf.
26307 - Initialize log mutex before initializing dmalloc. Otherwise,
26308 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
26309 - Use recursive pthread mutexes in order to avoid deadlock when
26310 logging debug-level messages to a controller. Bug spotted by nwf,
26311 bugfix on 0.2.0.16-alpha.
26313 o Minor bugfixes (resource management):
26314 - Keep address policies from leaking memory: start their refcount
26315 at 1, not 2. Bugfix on 0.2.0.16-alpha.
26316 - Free authority certificates on exit, so they don't look like memory
26317 leaks. Bugfix on 0.2.0.19-alpha.
26318 - Free static hashtables for policy maps and for TLS connections on
26319 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
26320 - Avoid allocating extra space when computing consensuses on 64-bit
26321 platforms. Bug spotted by aakova.
26323 o Minor bugfixes (misc):
26324 - Do not read the configuration file when we've only been told to
26325 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
26326 based on patch from Sebastian Hahn.
26327 - Exit relays that are used as a client can now reach themselves
26328 using the .exit notation, rather than just launching an infinite
26329 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
26330 - When attempting to open a logfile fails, tell us why.
26331 - Fix a dumb bug that was preventing us from knowing that we should
26332 preemptively build circuits to handle expected directory requests.
26333 Fixes bug 660. Bugfix on 0.1.2.x.
26334 - Warn less verbosely about clock skew from netinfo cells from
26335 untrusted sources. Fixes bug 663.
26336 - Make controller stream events for DNS requests more consistent,
26337 by adding "new stream" events for DNS requests, and removing
26338 spurious "stream closed" events" for cached reverse resolves.
26339 Patch from mwenge. Fixes bug 646.
26340 - Correctly notify one-hop connections when a circuit build has
26341 failed. Possible fix for bug 669. Found by lodger.
26344 Changes in version 0.2.0.23-rc - 2008-03-24
26345 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
26346 makes bootstrapping faster if the first directory mirror you contact
26347 is down. The bundles also include the new Vidalia 0.1.2 release.
26350 - When a tunneled directory request is made to a directory server
26351 that's down, notice after 30 seconds rather than 120 seconds. Also,
26352 fail any begindir streams that are pending on it, so they can
26353 retry elsewhere. This was causing multi-minute delays on bootstrap.
26356 Changes in version 0.2.0.22-rc - 2008-03-18
26357 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
26358 enables encrypted directory connections by default for non-relays, fixes
26359 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
26360 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
26363 - Enable encrypted directory connections by default for non-relays,
26364 so censor tools that block Tor directory connections based on their
26365 plaintext patterns will no longer work. This means Tor works in
26366 certain censored countries by default again.
26369 - Make sure servers always request certificates from clients during
26370 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
26371 - Do not enter a CPU-eating loop when a connection is closed in
26372 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
26373 diagnosed by lodger; bugfix on 0.2.0.20-rc.
26374 - Fix assertion failure that could occur when a blocked circuit
26375 became unblocked, and it had pending client DNS requests. Bugfix
26376 on 0.2.0.1-alpha. Fixes bug 632.
26378 o Minor bugfixes (on 0.1.2.x):
26379 - Generate "STATUS_SERVER" events rather than misspelled
26380 "STATUS_SEVER" events. Caught by mwenge.
26381 - When counting the number of bytes written on a TLS connection,
26382 look at the BIO actually used for writing to the network, not
26383 at the BIO used (sometimes) to buffer data for the network.
26384 Looking at different BIOs could result in write counts on the
26385 order of ULONG_MAX. Fixes bug 614.
26386 - On Windows, correctly detect errors when listing the contents of
26387 a directory. Fix from lodger.
26389 o Minor bugfixes (on 0.2.0.x):
26390 - Downgrade "sslv3 alert handshake failure" message to INFO.
26391 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
26392 left BandwidthRate and BandwidthBurst at the default, we would be
26393 silently limited by those defaults. Now raise them to match the
26394 RelayBandwidth* values.
26395 - Fix the SVK version detection logic to work correctly on a branch.
26396 - Make --enable-openbsd-malloc work correctly on Linux with alpha
26397 CPUs. Fixes bug 625.
26398 - Logging functions now check that the passed severity is sane.
26399 - Use proper log levels in the testsuite call of
26400 get_interface_address6().
26401 - When using a nonstandard malloc, do not use the platform values for
26402 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
26403 - Make the openbsd malloc code use 8k pages on alpha CPUs and
26405 - Detect mismatched page sizes when using --enable-openbsd-malloc.
26406 - Avoid double-marked-for-close warning when certain kinds of invalid
26407 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
26408 for bug 617. Bugfix on 0.2.0.1-alpha.
26409 - Make sure that the "NULL-means-reject *:*" convention is followed by
26410 all the policy manipulation functions, avoiding some possible crash
26411 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
26412 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
26413 actually works, and doesn't warn about every single reverse lookup.
26414 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
26417 - Only log guard node status when guard node status has changed.
26418 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
26419 make "INFO" 75% less verbose.
26422 Changes in version 0.2.0.21-rc - 2008-03-02
26423 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
26424 makes Tor work well with Vidalia again, fixes a rare assert bug,
26425 and fixes a pair of more minor bugs. The bundles also include Vidalia
26426 0.1.0 and Torbutton 1.1.16.
26429 - The control port should declare that it requires password auth
26430 when HashedControlSessionPassword is set too. Patch from Matt Edman;
26431 bugfix on 0.2.0.20-rc. Fixes bug 615.
26432 - Downgrade assert in connection_buckets_decrement() to a log message.
26433 This may help us solve bug 614, and in any case will make its
26434 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
26435 - We were sometimes miscounting the number of bytes read from the
26436 network, causing our rate limiting to not be followed exactly.
26437 Bugfix on 0.2.0.16-alpha. Reported by lodger.
26440 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
26441 OpenSSL versions should have been working fine. Diagnosis and patch
26442 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
26443 Bugfix on 0.2.0.20-rc.
26446 Changes in version 0.2.0.20-rc - 2008-02-24
26447 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
26448 makes more progress towards normalizing Tor's TLS handshake, makes
26449 hidden services work better again, helps relays bootstrap if they don't
26450 know their IP address, adds optional support for linking in openbsd's
26451 allocator or tcmalloc, allows really fast relays to scale past 15000
26452 sockets, and fixes a bunch of minor bugs reported by Veracode.
26455 - Enable the revised TLS handshake based on the one designed by
26456 Steven Murdoch in proposal 124, as revised in proposal 130. It
26457 includes version negotiation for OR connections as described in
26458 proposal 105. The new handshake is meant to be harder for censors
26459 to fingerprint, and it adds the ability to detect certain kinds of
26460 man-in-the-middle traffic analysis attacks. The version negotiation
26461 feature will allow us to improve Tor's link protocol more safely
26463 - Choose which bridge to use proportional to its advertised bandwidth,
26464 rather than uniformly at random. This should speed up Tor for
26465 bridge users. Also do this for people who set StrictEntryNodes.
26466 - When a TrackHostExits-chosen exit fails too many times in a row,
26467 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
26470 - Resolved problems with (re-)fetching hidden service descriptors.
26471 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
26472 and 0.2.0.19-alpha.
26473 - If we only ever used Tor for hidden service lookups or posts, we
26474 would stop building circuits and start refusing connections after
26475 24 hours, since we falsely believed that Tor was dormant. Reported
26476 by nwf; bugfix on 0.1.2.x.
26477 - Servers that don't know their own IP address should go to the
26478 authorities for their first directory fetch, even if their DirPort
26479 is off or if they don't know they're reachable yet. This will help
26480 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
26481 - When counting the number of open sockets, count not only the number
26482 of sockets we have received from the socket() call, but also
26483 the number we've gotten from accept() and socketpair(). This bug
26484 made us fail to count all sockets that we were using for incoming
26485 connections. Bugfix on 0.2.0.x.
26486 - Fix code used to find strings within buffers, when those strings
26487 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
26488 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
26489 - Add a new __HashedControlSessionPassword option for controllers
26490 to use for one-off session password hashes that shouldn't get
26491 saved to disk by SAVECONF --- Vidalia users were accumulating a
26492 pile of HashedControlPassword lines in their torrc files, one for
26493 each time they had restarted Tor and then clicked Save. Make Tor
26494 automatically convert "HashedControlPassword" to this new option but
26495 only when it's given on the command line. Partial fix for bug 586.
26497 o Minor features (performance):
26498 - Tune parameters for cell pool allocation to minimize amount of
26500 - Add OpenBSD malloc code from phk as an optional malloc
26501 replacement on Linux: some glibc libraries do very poorly
26502 with Tor's memory allocation patterns. Pass
26503 --enable-openbsd-malloc to get the replacement malloc code.
26504 - Add a --with-tcmalloc option to the configure script to link
26505 against tcmalloc (if present). Does not yet search for
26506 non-system include paths.
26507 - Stop imposing an arbitrary maximum on the number of file descriptors
26508 used for busy servers. Bug reported by Olaf Selke; patch from
26511 o Minor features (other):
26512 - When SafeLogging is disabled, log addresses along with all TLS
26514 - When building with --enable-gcc-warnings, check for whether Apple's
26515 warning "-Wshorten-64-to-32" is available.
26516 - Add a --passphrase-fd argument to the tor-gencert command for
26519 o Minor bugfixes (memory leaks and code problems):
26520 - We were leaking a file descriptor if Tor started with a zero-length
26521 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
26522 - Detect size overflow in zlib code. Reported by Justin Ferguson and
26524 - We were comparing the raw BridgePassword entry with a base64'ed
26525 version of it, when handling a "/tor/networkstatus-bridges"
26526 directory request. Now compare correctly. Noticed by Veracode.
26527 - Recover from bad tracked-since value in MTBF-history file.
26528 Should fix bug 537.
26529 - Alter the code that tries to recover from unhandled write
26530 errors, to not try to flush onto a socket that's given us
26531 unhandled errors. Bugfix on 0.1.2.x.
26532 - Make Unix controlsockets work correctly on OpenBSD. Patch from
26533 tup. Bugfix on 0.2.0.3-alpha.
26535 o Minor bugfixes (other):
26536 - If we have an extra-info document for our server, always make
26537 it available on the control port, even if we haven't gotten
26538 a copy of it from an authority yet. Patch from mwenge.
26539 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
26540 - Directory mirrors no longer include a guess at the client's IP
26541 address if the connection appears to be coming from the same /24
26542 network; it was producing too many wrong guesses.
26543 - Make the new hidden service code respect the SafeLogging setting.
26544 Bugfix on 0.2.0.x. Patch from Karsten.
26545 - When starting as an authority, do not overwrite all certificates
26546 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
26547 - If we're trying to flush the last bytes on a connection (for
26548 example, when answering a directory request), reset the
26549 time-to-give-up timeout every time we manage to write something
26550 on the socket. Bugfix on 0.1.2.x.
26551 - Change the behavior of "getinfo status/good-server-descriptor"
26552 so it doesn't return failure when any authority disappears.
26553 - Even though the man page said that "TrackHostExits ." should
26554 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
26555 - Report TLS "zero return" case as a "clean close" and "IO error"
26556 as a "close". Stop calling closes "unexpected closes": existing
26557 Tors don't use SSL_close(), so having a connection close without
26558 the TLS shutdown handshake is hardly unexpected.
26559 - Send NAMESERVER_STATUS messages for a single failed nameserver
26562 o Code simplifications and refactoring:
26563 - Remove the tor_strpartition function: its logic was confused,
26564 and it was only used for one thing that could be implemented far
26568 Changes in version 0.2.0.19-alpha - 2008-02-09
26569 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
26570 handshake, makes path selection for relays more secure and IP address
26571 guessing more robust, and generally fixes a lot of bugs in preparation
26572 for calling the 0.2.0 branch stable.
26575 - Do not include recognizeable strings in the commonname part of
26576 Tor's x509 certificates.
26579 - If we're a relay, avoid picking ourselves as an introduction point,
26580 a rendezvous point, or as the final hop for internal circuits. Bug
26581 reported by taranis and lodger. Bugfix on 0.1.2.x.
26582 - Patch from "Andrew S. Lists" to catch when we contact a directory
26583 mirror at IP address X and he says we look like we're coming from
26584 IP address X. Bugfix on 0.1.2.x.
26586 o Minor features (security):
26587 - Be more paranoid about overwriting sensitive memory on free(),
26588 as a defensive programming tactic to ensure forward secrecy.
26590 o Minor features (directory authority):
26591 - Actually validate the options passed to AuthDirReject,
26592 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
26593 - Reject router descriptors with out-of-range bandwidthcapacity or
26594 bandwidthburst values.
26596 o Minor features (controller):
26597 - Reject controller commands over 1MB in length. This keeps rogue
26598 processes from running us out of memory.
26600 o Minor features (misc):
26601 - Give more descriptive well-formedness errors for out-of-range
26602 hidden service descriptor/protocol versions.
26603 - Make memory debugging information describe more about history
26604 of cell allocation, so we can help reduce our memory use.
26606 o Deprecated features (controller):
26607 - The status/version/num-versioning and status/version/num-concurring
26608 GETINFO options are no longer useful in the v3 directory protocol:
26609 treat them as deprecated, and warn when they're used.
26612 - When our consensus networkstatus has been expired for a while, stop
26613 being willing to build circuits using it. Fixes bug 401. Bugfix
26615 - Directory caches now fetch certificates from all authorities
26616 listed in a networkstatus consensus, even when they do not
26617 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
26618 - When connecting to a bridge without specifying its key, insert
26619 the connection into the identity-to-connection map as soon as
26620 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
26621 - Detect versions of OS X where malloc_good_size() is present in the
26622 library but never actually declared. Resolves bug 587. Bugfix
26624 - Stop incorrectly truncating zlib responses to directory authority
26625 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
26626 - Stop recommending that every server operator send mail to tor-ops.
26627 Resolves bug 597. Bugfix on 0.1.2.x.
26628 - Don't trigger an assert if we start a directory authority with a
26629 private IP address (like 127.0.0.1).
26630 - Avoid possible failures when generating a directory with routers
26631 with over-long versions strings, or too many flags set. Bugfix
26633 - If an attempt to launch a DNS resolve request over the control
26634 port fails because we have overrun the limit on the number of
26635 connections, tell the controller that the request has failed.
26636 - Avoid using too little bandwidth when our clock skips a few
26637 seconds. Bugfix on 0.1.2.x.
26638 - Fix shell error when warning about missing packages in configure
26639 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
26640 - Do not become confused when receiving a spurious VERSIONS-like
26641 cell from a confused v1 client. Bugfix on 0.2.0.x.
26642 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
26643 introduction points for a hidden service have failed. Patch from
26644 Karsten Loesing. Bugfix on 0.2.0.x.
26646 o Code simplifications and refactoring:
26647 - Remove some needless generality from cpuworker code, for improved
26649 - Stop overloading the circuit_t.onionskin field for both "onionskin
26650 from a CREATE cell that we are waiting for a cpuworker to be
26651 assigned" and "onionskin from an EXTEND cell that we are going to
26652 send to an OR as soon as we are connected". Might help with bug 600.
26653 - Add an in-place version of aes_crypt() so that we can avoid doing a
26654 needless memcpy() call on each cell payload.
26657 Changes in version 0.2.0.18-alpha - 2008-01-25
26658 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
26659 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
26660 that can warn or reject connections to ports generally associated with
26661 vulnerable-plaintext protocols.
26663 o New directory authorities:
26664 - Set up dannenberg (run by CCC) as the sixth v3 directory
26668 - Fix a major memory leak when attempting to use the v2 TLS
26669 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
26670 - We accidentally enabled the under-development v2 TLS handshake
26671 code, which was causing log entries like "TLS error while
26672 renegotiating handshake". Disable it again. Resolves bug 590.
26673 - We were computing the wrong Content-Length: header for directory
26674 responses that need to be compressed on the fly, causing clients
26675 asking for those items to always fail. Bugfix on 0.2.0.x; partially
26679 - Avoid going directly to the directory authorities even if you're a
26680 relay, if you haven't found yourself reachable yet or if you've
26681 decided not to advertise your dirport yet. Addresses bug 556.
26682 - If we've gone 12 hours since our last bandwidth check, and we
26683 estimate we have less than 50KB bandwidth capacity but we could
26684 handle more, do another bandwidth test.
26685 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
26686 Tor can warn and/or refuse connections to ports commonly used with
26687 vulnerable-plaintext protocols. Currently we warn on ports 23,
26688 109, 110, and 143, but we don't reject any.
26691 - When we setconf ClientOnly to 1, close any current OR and Dir
26692 listeners. Reported by mwenge.
26693 - When we get a consensus that's been signed by more people than
26694 we expect, don't log about it; it's not a big deal. Reported
26698 - Don't answer "/tor/networkstatus-bridges" directory requests if
26699 the request isn't encrypted.
26700 - Make "ClientOnly 1" config option disable directory ports too.
26701 - Patches from Karsten Loesing to make v2 hidden services more
26702 robust: work even when there aren't enough HSDir relays available;
26703 retry when a v2 rend desc fetch fails; but don't retry if we
26704 already have a usable v0 rend desc.
26707 Changes in version 0.2.0.17-alpha - 2008-01-17
26708 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
26711 - Make the tor-gencert man page get included correctly in the tarball.
26714 Changes in version 0.2.0.16-alpha - 2008-01-17
26715 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
26716 Loesing, and generally cleans up a lot of features and minor bugs.
26718 o New directory authorities:
26719 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
26722 o Major performance improvements:
26723 - Switch our old ring buffer implementation for one more like that
26724 used by free Unix kernels. The wasted space in a buffer with 1mb
26725 of data will now be more like 8k than 1mb. The new implementation
26726 also avoids realloc();realloc(); patterns that can contribute to
26727 memory fragmentation.
26730 - Configuration files now accept C-style strings as values. This
26731 helps encode characters not allowed in the current configuration
26732 file format, such as newline or #. Addresses bug 557.
26733 - Although we fixed bug 539 (where servers would send HTTP status 503
26734 responses _and_ send a body too), there are still servers out
26735 there that haven't upgraded. Therefore, make clients parse such
26736 bodies when they receive them.
26737 - When we're not serving v2 directory information, there is no reason
26738 to actually keep any around. Remove the obsolete files and directory
26739 on startup if they are very old and we aren't going to serve them.
26741 o Minor performance improvements:
26742 - Reference-count and share copies of address policy entries; only 5%
26743 of them were actually distinct.
26744 - Never walk through the list of logs if we know that no log is
26745 interested in a given message.
26748 - When an authority has not signed a consensus, do not try to
26749 download a nonexistent "certificate with key 00000000". Bugfix
26750 on 0.2.0.x. Fixes bug 569.
26751 - Fix a rare assert error when we're closing one of our threads:
26752 use a mutex to protect the list of logs, so we never write to the
26753 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
26754 bug 575, which is kind of the revenge of bug 222.
26755 - Patch from Karsten Loesing to complain less at both the client
26756 and the relay when a relay used to have the HSDir flag but doesn't
26757 anymore, and we try to upload a hidden service descriptor.
26758 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
26760 - Do not try to download missing certificates until we have tried
26761 to check our fallback consensus. Fixes bug 583.
26762 - Make bridges round reported GeoIP stats info up to the nearest
26763 estimate, not down. Now we can distinguish between "0 people from
26764 this country" and "1 person from this country".
26765 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
26766 - Avoid possible segfault if key generation fails in
26767 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
26768 - Avoid segfault in the case where a badly behaved v2 versioning
26769 directory sends a signed networkstatus with missing client-versions.
26771 - Avoid segfaults on certain complex invocations of
26772 router_get_by_hexdigest(). Bugfix on 0.1.2.
26773 - Correct bad index on array access in parse_http_time(). Bugfix
26775 - Fix possible bug in vote generation when server versions are present
26776 but client versions are not.
26777 - Fix rare bug on REDIRECTSTREAM control command when called with no
26778 port set: it could erroneously report an error when none had
26780 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
26781 compressing large objects and find ourselves with more than 4k
26782 left over. Bugfix on 0.2.0.
26783 - Fix a small memory leak when setting up a hidden service.
26784 - Fix a few memory leaks that could in theory happen under bizarre
26786 - Fix an assert if we post a general-purpose descriptor via the
26787 control port but that descriptor isn't mentioned in our current
26788 network consensus. Bug reported by Jon McLachlan; bugfix on
26791 o Minor features (controller):
26792 - Get NS events working again. Patch from tup.
26793 - The GETCONF command now escapes and quotes configuration values
26794 that don't otherwise fit into the torrc file.
26795 - The SETCONF command now handles quoted values correctly.
26797 o Minor features (directory authorities):
26798 - New configuration options to override default maximum number of
26799 servers allowed on a single IP address. This is important for
26800 running a test network on a single host.
26801 - Actually implement the -s option to tor-gencert.
26802 - Add a manual page for tor-gencert.
26804 o Minor features (bridges):
26805 - Bridge authorities no longer serve bridge descriptors over
26806 unencrypted connections.
26808 o Minor features (other):
26809 - Add hidden services and DNSPorts to the list of things that make
26810 Tor accept that it has running ports. Change starting Tor with no
26811 ports from a fatal error to a warning; we might change it back if
26812 this turns out to confuse anybody. Fixes bug 579.
26815 Changes in version 0.1.2.19 - 2008-01-17
26816 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
26817 exit policy a little bit more conservative so it's safer to run an
26818 exit relay on a home system, and fixes a variety of smaller issues.
26821 - Exit policies now reject connections that are addressed to a
26822 relay's public (external) IP address too, unless
26823 ExitPolicyRejectPrivate is turned off. We do this because too
26824 many relays are running nearby to services that trust them based
26825 on network address.
26828 - When the clock jumps forward a lot, do not allow the bandwidth
26829 buckets to become negative. Fixes bug 544.
26830 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
26831 on every successful resolve. Reported by Mike Perry.
26832 - Purge old entries from the "rephist" database and the hidden
26833 service descriptor database even when DirPort is zero.
26834 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26835 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26836 crashing or mis-answering these requests.
26837 - When we decide to send a 503 response to a request for servers, do
26838 not then also send the server descriptors: this defeats the whole
26839 purpose. Fixes bug 539.
26842 - Changing the ExitPolicyRejectPrivate setting should cause us to
26843 rebuild our server descriptor.
26844 - Fix handling of hex nicknames when answering controller requests for
26845 networkstatus by name, or when deciding whether to warn about
26846 unknown routers in a config option. (Patch from mwenge.)
26847 - Fix a couple of hard-to-trigger autoconf problems that could result
26848 in really weird results on platforms whose sys/types.h files define
26849 nonstandard integer types.
26850 - Don't try to create the datadir when running --verify-config or
26851 --hash-password. Resolves bug 540.
26852 - If we were having problems getting a particular descriptor from the
26853 directory caches, and then we learned about a new descriptor for
26854 that router, we weren't resetting our failure count. Reported
26856 - Although we fixed bug 539 (where servers would send HTTP status 503
26857 responses _and_ send a body too), there are still servers out there
26858 that haven't upgraded. Therefore, make clients parse such bodies
26859 when they receive them.
26860 - Run correctly on systems where rlim_t is larger than unsigned long.
26861 This includes some 64-bit systems.
26862 - Run correctly on platforms (like some versions of OS X 10.5) where
26863 the real limit for number of open files is OPEN_FILES, not rlim_max
26864 from getrlimit(RLIMIT_NOFILES).
26865 - Avoid a spurious free on base64 failure.
26866 - Avoid segfaults on certain complex invocations of
26867 router_get_by_hexdigest().
26868 - Fix rare bug on REDIRECTSTREAM control command when called with no
26869 port set: it could erroneously report an error when none had
26873 Changes in version 0.2.0.15-alpha - 2007-12-25
26874 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
26875 features added in 0.2.0.13-alpha.
26878 - Fix several remotely triggerable asserts based on DirPort requests
26879 for a v2 or v3 networkstatus object before we were prepared. This
26880 was particularly bad for 0.2.0.13 and later bridge relays, who
26881 would never have a v2 networkstatus and would thus always crash
26882 when used. Bugfixes on 0.2.0.x.
26883 - Estimate the v3 networkstatus size more accurately, rather than
26884 estimating it at zero bytes and giving it artificially high priority
26885 compared to other directory requests. Bugfix on 0.2.0.x.
26888 - Fix configure.in logic for cross-compilation.
26889 - When we load a bridge descriptor from the cache, and it was
26890 previously unreachable, mark it as retriable so we won't just
26891 ignore it. Also, try fetching a new copy immediately. Bugfixes
26893 - The bridge GeoIP stats were counting other relays, for example
26894 self-reachability and authority-reachability tests.
26897 - Support compilation to target iPhone; patch from cjacker huang.
26898 To build for iPhone, pass the --enable-iphone option to configure.
26901 Changes in version 0.2.0.14-alpha - 2007-12-23
26903 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
26904 without a datadirectory from a previous Tor install. Reported
26906 - Fix a crash when we fetch a descriptor that turns out to be
26907 unexpected (it used to be in our networkstatus when we started
26908 fetching it, but it isn't in our current networkstatus), and we
26909 aren't using bridges. Bugfix on 0.2.0.x.
26910 - Fix a crash when accessing hidden services: it would work the first
26911 time you use a given introduction point for your service, but
26912 on subsequent requests we'd be using garbage memory. Fixed by
26913 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
26914 - Fix a crash when we load a bridge descriptor from disk but we don't
26915 currently have a Bridge line for it in our torrc. Bugfix on
26919 - If bridge authorities set BridgePassword, they will serve a
26920 snapshot of known bridge routerstatuses from their DirPort to
26921 anybody who knows that password. Unset by default.
26924 - Make the unit tests build again.
26925 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
26926 - Make PublishServerDescriptor default to 1, so the default doesn't
26927 have to change as we invent new directory protocol versions.
26928 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
26929 be included unless sys/time.h is already included. Fixes
26930 bug 553. Bugfix on 0.2.0.x.
26931 - If we receive a general-purpose descriptor and then receive an
26932 identical bridge-purpose descriptor soon after, don't discard
26933 the next one as a duplicate.
26936 - If BridgeRelay is set to 1, then the default for
26937 PublishServerDescriptor is now "bridge" rather than "v2,v3".
26938 - If the user sets RelayBandwidthRate but doesn't set
26939 RelayBandwidthBurst, then make them equal rather than erroring out.
26942 Changes in version 0.2.0.13-alpha - 2007-12-21
26943 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
26944 Goodell, fixes many more bugs, and adds a lot of infrastructure for
26947 o New directory authorities:
26948 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
26952 - Only update guard status (usable / not usable) once we have
26953 enough directory information. This was causing us to always pick
26954 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
26955 causing us to discard all our guards on startup if we hadn't been
26956 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
26957 - Purge old entries from the "rephist" database and the hidden
26958 service descriptor databases even when DirPort is zero. Bugfix
26960 - We were ignoring our RelayBandwidthRate for the first 30 seconds
26961 after opening a circuit -- even a relayed circuit. Bugfix on
26963 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
26964 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
26965 crashing or mis-answering these types of requests.
26966 - Relays were publishing their server descriptor to v1 and v2
26967 directory authorities, but they didn't try publishing to v3-only
26968 authorities. Fix this; and also stop publishing to v1 authorities.
26970 - When we were reading router descriptors from cache, we were ignoring
26971 the annotations -- so for example we were reading in bridge-purpose
26972 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
26973 - When we decided to send a 503 response to a request for servers, we
26974 were then also sending the server descriptors: this defeats the
26975 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
26978 - Bridge relays now behave like clients with respect to time
26979 intervals for downloading new consensus documents -- otherwise they
26980 stand out. Bridge users now wait until the end of the interval,
26981 so their bridge relay will be sure to have a new consensus document.
26982 - Three new config options (AlternateDirAuthority,
26983 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
26984 user selectively replace the default directory authorities by type,
26985 rather than the all-or-nothing replacement that DirServer offers.
26986 - Tor can now be configured to read a GeoIP file from disk in one
26987 of two formats. This can be used by controllers to map IP addresses
26988 to countries. Eventually, it may support exit-by-country.
26989 - When possible, bridge relays remember which countries users
26990 are coming from, and report aggregate information in their
26991 extra-info documents, so that the bridge authorities can learn
26992 where Tor is blocked.
26993 - Bridge directory authorities now do reachability testing on the
26994 bridges they know. They provide router status summaries to the
26995 controller via "getinfo ns/purpose/bridge", and also dump summaries
26996 to a file periodically.
26997 - Stop fetching directory info so aggressively if your DirPort is
26998 on but your ORPort is off; stop fetching v2 dir info entirely.
26999 You can override these choices with the new FetchDirInfoEarly
27003 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
27004 consensus documents when there are too many relays at a single
27005 IP address. Now clear it in v2 network status documents too, and
27006 also clear it in routerinfo_t when the relay is no longer listed
27007 in the relevant networkstatus document.
27008 - Don't crash if we get an unexpected value for the
27009 PublishServerDescriptor config option. Reported by Matt Edman;
27010 bugfix on 0.2.0.9-alpha.
27011 - Our new v2 hidden service descriptor format allows descriptors
27012 that have no introduction points. But Tor crashed when we tried
27013 to build a descriptor with no intro points (and it would have
27014 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
27015 by Karsten Loesing.
27016 - Fix building with dmalloc 5.5.2 with glibc.
27017 - Reject uploaded descriptors and extrainfo documents if they're
27018 huge. Otherwise we'll cache them all over the network and it'll
27019 clog everything up. Reported by Aljosha Judmayer.
27020 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
27021 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
27022 - When the DANGEROUS_VERSION controller status event told us we're
27023 running an obsolete version, it used the string "OLD" to describe
27024 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
27025 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
27026 - If we can't expand our list of entry guards (e.g. because we're
27027 using bridges or we have StrictEntryNodes set), don't mark relays
27028 down when they fail a directory request. Otherwise we're too quick
27029 to mark all our entry points down. Bugfix on 0.1.2.x.
27030 - Fix handling of hex nicknames when answering controller requests for
27031 networkstatus by name, or when deciding whether to warn about unknown
27032 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
27033 - Fix a couple of hard-to-trigger autoconf problems that could result
27034 in really weird results on platforms whose sys/types.h files define
27035 nonstandard integer types. Bugfix on 0.1.2.x.
27036 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
27037 - Don't crash on name lookup when we have no current consensus. Fixes
27038 bug 538; bugfix on 0.2.0.x.
27039 - Only Tors that want to mirror the v2 directory info should
27040 create the "cached-status" directory in their datadir. (All Tors
27041 used to create it.) Bugfix on 0.2.0.9-alpha.
27042 - Directory authorities should only automatically download Extra Info
27043 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
27046 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
27047 consumers. (We already do this on HUP.)
27048 - Authorities and caches fetch the v2 networkstatus documents
27049 less often, now that v3 is encouraged.
27050 - Add a new config option BridgeRelay that specifies you want to
27051 be a bridge relay. Right now the only difference is that it makes
27052 you answer begin_dir requests, and it makes you cache dir info,
27053 even if your DirPort isn't on.
27054 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
27055 ask about source, timestamp of arrival, purpose, etc. We need
27056 something like this to help Vidalia not do GeoIP lookups on bridge
27058 - Allow multiple HashedControlPassword config lines, to support
27059 multiple controller passwords.
27060 - Authorities now decide whether they're authoritative for a given
27061 router based on the router's purpose.
27062 - New config options AuthDirBadDir and AuthDirListBadDirs for
27063 authorities to mark certain relays as "bad directories" in the
27064 networkstatus documents. Also supports the "!baddir" directive in
27065 the approved-routers file.
27068 Changes in version 0.2.0.12-alpha - 2007-11-16
27069 This twelfth development snapshot fixes some more build problems as
27070 well as a few minor bugs.
27073 - Make it build on OpenBSD again. Patch from tup.
27074 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
27075 package-building for Red Hat, OS X, etc.
27077 o Minor bugfixes (on 0.1.2.x):
27078 - Changing the ExitPolicyRejectPrivate setting should cause us to
27079 rebuild our server descriptor.
27081 o Minor bugfixes (on 0.2.0.x):
27082 - When we're lacking a consensus, don't try to perform rendezvous
27083 operations. Reported by Karsten Loesing.
27084 - Fix a small memory leak whenever we decide against using a
27085 newly picked entry guard. Reported by Mike Perry.
27086 - When authorities detected more than two relays running on the same
27087 IP address, they were clearing all the status flags but forgetting
27088 to clear the "hsdir" flag. So clients were being told that a
27089 given relay was the right choice for a v2 hsdir lookup, yet they
27090 never had its descriptor because it was marked as 'not running'
27092 - If we're trying to fetch a bridge descriptor and there's no way
27093 the bridge authority could help us (for example, we don't know
27094 a digest, or there is no bridge authority), don't be so eager to
27095 fall back to asking the bridge authority.
27096 - If we're using bridges or have strictentrynodes set, and our
27097 chosen exit is in the same family as all our bridges/entry guards,
27098 then be flexible about families.
27101 - When we negotiate a v2 link-layer connection (not yet implemented),
27102 accept RELAY_EARLY cells and turn them into RELAY cells if we've
27103 negotiated a v1 connection for their next step. Initial code for
27107 Changes in version 0.2.0.11-alpha - 2007-11-12
27108 This eleventh development snapshot fixes some build problems with
27109 the previous snapshot. It also includes a more secure-by-default exit
27110 policy for relays, fixes an enormous memory leak for exit relays, and
27111 fixes another bug where servers were falling out of the directory list.
27114 - Exit policies now reject connections that are addressed to a
27115 relay's public (external) IP address too, unless
27116 ExitPolicyRejectPrivate is turned off. We do this because too
27117 many relays are running nearby to services that trust them based
27118 on network address. Bugfix on 0.1.2.x.
27121 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
27122 on every successful resolve. Reported by Mike Perry; bugfix
27124 - On authorities, never downgrade to old router descriptors simply
27125 because they're listed in the consensus. This created a catch-22
27126 where we wouldn't list a new descriptor because there was an
27127 old one in the consensus, and we couldn't get the new one in the
27128 consensus because we wouldn't list it. Possible fix for bug 548.
27129 Also, this might cause bug 543 to appear on authorities; if so,
27130 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
27132 o Packaging fixes on 0.2.0.10-alpha:
27133 - We were including instructions about what to do with the
27134 src/config/fallback-consensus file, but we weren't actually
27135 including it in the tarball. Disable all of that for now.
27138 - Allow people to say PreferTunnelledDirConns rather than
27139 PreferTunneledDirConns, for those alternate-spellers out there.
27142 - Don't reevaluate all the information from our consensus document
27143 just because we've downloaded a v2 networkstatus that we intend
27144 to cache. Fixes bug 545; bugfix on 0.2.0.x.
27147 Changes in version 0.2.0.10-alpha - 2007-11-10
27148 This tenth development snapshot adds a third v3 directory authority
27149 run by Mike Perry, adds most of Karsten Loesing's new hidden service
27150 descriptor format, fixes a bad crash bug and new bridge bugs introduced
27151 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
27152 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
27153 addresses many more minor issues.
27155 o New directory authorities:
27156 - Set up ides (run by Mike Perry) as the third v3 directory authority.
27159 - Allow tunnelled directory connections to ask for an encrypted
27160 "begin_dir" connection or an anonymized "uses a full Tor circuit"
27161 connection independently. Now we can make anonymized begin_dir
27162 connections for (e.g.) more secure hidden service posting and
27164 - More progress on proposal 114: code from Karsten Loesing to
27165 implement new hidden service descriptor format.
27166 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
27167 accommodate the growing number of servers that use the default
27168 and are reaching it.
27169 - Directory authorities use a new formula for selecting which nodes
27170 to advertise as Guards: they must be in the top 7/8 in terms of
27171 how long we have known about them, and above the median of those
27172 nodes in terms of weighted fractional uptime.
27173 - Make "not enough dir info yet" warnings describe *why* Tor feels
27174 it doesn't have enough directory info yet.
27177 - Stop servers from crashing if they set a Family option (or
27178 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
27180 - Make bridge users work again -- the move to v3 directories in
27181 0.2.0.9-alpha had introduced a number of bugs that made bridges
27182 no longer work for clients.
27183 - When the clock jumps forward a lot, do not allow the bandwidth
27184 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
27186 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
27187 - When the consensus lists a router descriptor that we previously were
27188 mirroring, but that we considered non-canonical, reload the
27189 descriptor as canonical. This fixes bug 543 where Tor servers
27190 would start complaining after a few days that they don't have
27191 enough directory information to build a circuit.
27192 - Consider replacing the current consensus when certificates arrive
27193 that make the pending consensus valid. Previously, we were only
27194 considering replacement when the new certs _didn't_ help.
27195 - Fix an assert error on startup if we didn't already have the
27196 consensus and certs cached in our datadirectory: we were caching
27197 the consensus in consensus_waiting_for_certs but then free'ing it
27199 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
27200 Request) if we need more v3 certs but we've already got pending
27201 requests for all of them.
27202 - Correctly back off from failing certificate downloads. Fixes
27204 - Authorities don't vote on the Running flag if they have been running
27205 for less than 30 minutes themselves. Fixes bug 547, where a newly
27206 started authority would vote that everyone was down.
27208 o New requirements:
27209 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
27210 it, it had no AES, and it hasn't seen any security patches since
27214 - Clients now hold circuitless TLS connections open for 1.5 times
27215 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
27216 rebuild a new circuit over them within that timeframe. Previously,
27217 they held them open only for KeepalivePeriod (5 minutes).
27218 - Use "If-Modified-Since" to avoid retrieving consensus
27219 networkstatuses that we already have.
27220 - When we have no consensus, check FallbackNetworkstatusFile (defaults
27221 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
27222 we start knowing some directory caches.
27223 - When we receive a consensus from the future, warn about skew.
27224 - Improve skew reporting: try to give the user a better log message
27225 about how skewed they are, and how much this matters.
27226 - When we have a certificate for an authority, believe that
27227 certificate's claims about the authority's IP address.
27228 - New --quiet command-line option to suppress the default console log.
27229 Good in combination with --hash-password.
27230 - Authorities send back an X-Descriptor-Not-New header in response to
27231 an accepted-but-discarded descriptor upload. Partially implements
27233 - Make the log message for "tls error. breaking." more useful.
27234 - Better log messages about certificate downloads, to attempt to
27235 track down the second incarnation of bug 546.
27237 o Minor features (bridges):
27238 - If bridge users set UpdateBridgesFromAuthority, but the digest
27239 they ask for is a 404 from the bridge authority, they now fall
27240 back to trying the bridge directly.
27241 - Bridges now use begin_dir to publish their server descriptor to
27242 the bridge authority, even when they haven't set TunnelDirConns.
27244 o Minor features (controller):
27245 - When reporting clock skew, and we know that the clock is _at least
27246 as skewed_ as some value, but we don't know the actual value,
27247 report the value as a "minimum skew."
27250 - Update linux-tor-prio.sh script to allow QoS based on the uid of
27251 the Tor process. Patch from Marco Bonetti with tweaks from Mike
27255 - Refuse to start if both ORPort and UseBridges are set. Bugfix
27256 on 0.2.0.x, suggested by Matt Edman.
27257 - Don't stop fetching descriptors when FetchUselessDescriptors is
27258 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
27259 reported by tup and ioerror.
27260 - Better log message on vote from unknown authority.
27261 - Don't log "Launching 0 request for 0 router" message.
27263 o Minor bugfixes (memory leaks):
27264 - Stop leaking memory every time we parse a v3 certificate. Bugfix
27266 - Stop leaking memory every time we load a v3 certificate. Bugfix
27267 on 0.2.0.1-alpha. Fixes bug 536.
27268 - Stop leaking a cached networkstatus on exit. Bugfix on
27270 - Stop leaking voter information every time we free a consensus.
27271 Bugfix on 0.2.0.3-alpha.
27272 - Stop leaking signed data every time we check a voter signature.
27273 Bugfix on 0.2.0.3-alpha.
27274 - Stop leaking a signature every time we fail to parse a consensus or
27275 a vote. Bugfix on 0.2.0.3-alpha.
27276 - Stop leaking v2_download_status_map on shutdown. Bugfix on
27278 - Stop leaking conn->nickname every time we make a connection to a
27279 Tor relay without knowing its expected identity digest (e.g. when
27280 using bridges). Bugfix on 0.2.0.3-alpha.
27282 - Minor bugfixes (portability):
27283 - Run correctly on platforms where rlim_t is larger than unsigned
27284 long, and/or where the real limit for number of open files is
27285 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
27286 particular, these may be needed for OS X 10.5.
27289 Changes in version 0.1.2.18 - 2007-10-28
27290 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
27291 hidden service introduction that were causing huge delays, and a big
27292 bug that was causing some servers to disappear from the network status
27293 lists for a few hours each day.
27295 o Major bugfixes (crashes):
27296 - If a connection is shut down abruptly because of something that
27297 happened inside connection_flushed_some(), do not call
27298 connection_finished_flushing(). Should fix bug 451:
27299 "connection_stop_writing: Assertion conn->write_event failed"
27300 Bugfix on 0.1.2.7-alpha.
27301 - Fix possible segfaults in functions called from
27302 rend_process_relay_cell().
27304 o Major bugfixes (hidden services):
27305 - Hidden services were choosing introduction points uniquely by
27306 hexdigest, but when constructing the hidden service descriptor
27307 they merely wrote the (potentially ambiguous) nickname.
27308 - Clients now use the v2 intro format for hidden service
27309 connections: they specify their chosen rendezvous point by identity
27310 digest rather than by (potentially ambiguous) nickname. These
27311 changes could speed up hidden service connections dramatically.
27313 o Major bugfixes (other):
27314 - Stop publishing a new server descriptor just because we get a
27315 HUP signal. This led (in a roundabout way) to some servers getting
27316 dropped from the networkstatus lists for a few hours each day.
27317 - When looking for a circuit to cannibalize, consider family as well
27318 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27319 circuit cannibalization).
27320 - When a router wasn't listed in a new networkstatus, we were leaving
27321 the flags for that router alone -- meaning it remained Named,
27322 Running, etc -- even though absence from the networkstatus means
27323 that it shouldn't be considered to exist at all anymore. Now we
27324 clear all the flags for routers that fall out of the networkstatus
27325 consensus. Fixes bug 529.
27328 - Don't try to access (or alter) the state file when running
27329 --list-fingerprint or --verify-config or --hash-password. Resolves
27331 - When generating information telling us how to extend to a given
27332 router, do not try to include the nickname if it is
27333 absent. Resolves bug 467.
27334 - Fix a user-triggerable segfault in expand_filename(). (There isn't
27335 a way to trigger this remotely.)
27336 - When sending a status event to the controller telling it that an
27337 OR address is reachable, set the port correctly. (Previously we
27338 were reporting the dir port.)
27339 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27340 command. Bugfix on 0.1.2.17.
27341 - When loading bandwidth history, do not believe any information in
27342 the future. Fixes bug 434.
27343 - When loading entry guard information, do not believe any information
27345 - When we have our clock set far in the future and generate an
27346 onion key, then re-set our clock to be correct, we should not stop
27347 the onion key from getting rotated.
27348 - On some platforms, accept() can return a broken address. Detect
27349 this more quietly, and deal accordingly. Fixes bug 483.
27350 - It's not actually an error to find a non-pending entry in the DNS
27351 cache when canceling a pending resolve. Don't log unless stuff
27352 is fishy. Resolves bug 463.
27353 - Don't reset trusted dir server list when we set a configuration
27354 option. Patch from Robert Hogan.
27355 - Don't try to create the datadir when running --verify-config or
27356 --hash-password. Resolves bug 540.
27359 Changes in version 0.2.0.9-alpha - 2007-10-24
27360 This ninth development snapshot switches clients to the new v3 directory
27361 system; allows servers to be listed in the network status even when they
27362 have the same nickname as a registered server; and fixes many other
27363 bugs including a big one that was causing some servers to disappear
27364 from the network status lists for a few hours each day.
27366 o Major features (directory system):
27367 - Clients now download v3 consensus networkstatus documents instead
27368 of v2 networkstatus documents. Clients and caches now base their
27369 opinions about routers on these consensus documents. Clients only
27370 download router descriptors listed in the consensus.
27371 - Authorities now list servers who have the same nickname as
27372 a different named server, but list them with a new flag,
27373 "Unnamed". Now we can list servers that happen to pick the same
27374 nickname as a server that registered two years ago and then
27375 disappeared. Partially implements proposal 122.
27376 - If the consensus lists a router as "Unnamed", the name is assigned
27377 to a different router: do not identify the router by that name.
27378 Partially implements proposal 122.
27379 - Authorities can now come to a consensus on which method to use to
27380 compute the consensus. This gives us forward compatibility.
27383 - Stop publishing a new server descriptor just because we HUP or
27384 when we find our DirPort to be reachable but won't actually publish
27385 it. New descriptors without any real changes are dropped by the
27386 authorities, and can screw up our "publish every 18 hours" schedule.
27388 - When a router wasn't listed in a new networkstatus, we were leaving
27389 the flags for that router alone -- meaning it remained Named,
27390 Running, etc -- even though absence from the networkstatus means
27391 that it shouldn't be considered to exist at all anymore. Now we
27392 clear all the flags for routers that fall out of the networkstatus
27393 consensus. Fixes bug 529; bugfix on 0.1.2.x.
27394 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
27395 extrainfo documents and then discard them immediately for not
27396 matching the latest router. Bugfix on 0.2.0.1-alpha.
27398 o Minor features (v3 directory protocol):
27399 - Allow tor-gencert to generate a new certificate without replacing
27401 - Allow certificates to include an address.
27402 - When we change our directory-cache settings, reschedule all voting
27403 and download operations.
27404 - Reattempt certificate downloads immediately on failure, as long as
27405 we haven't failed a threshold number of times yet.
27406 - Delay retrying consensus downloads while we're downloading
27407 certificates to verify the one we just got. Also, count getting a
27408 consensus that we already have (or one that isn't valid) as a failure,
27409 and count failing to get the certificates after 20 minutes as a
27411 - Build circuits and download descriptors even if our consensus is a
27412 little expired. (This feature will go away once authorities are
27415 o Minor features (router descriptor cache):
27416 - If we find a cached-routers file that's been sitting around for more
27417 than 28 days unmodified, then most likely it's a leftover from
27418 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
27420 - When we (as a cache) download a descriptor because it was listed
27421 in a consensus, remember when the consensus was supposed to expire,
27422 and don't expire the descriptor until then.
27424 o Minor features (performance):
27425 - Call routerlist_remove_old_routers() much less often. This should
27426 speed startup, especially on directory caches.
27427 - Don't try to launch new descriptor downloads quite so often when we
27428 already have enough directory information to build circuits.
27429 - Base64 decoding was actually showing up on our profile when parsing
27430 the initial descriptor file; switch to an in-process all-at-once
27431 implementation that's about 3.5x times faster than calling out to
27434 o Minor features (compilation):
27435 - Detect non-ASCII platforms (if any still exist) and refuse to
27436 build there: some of our code assumes that 'A' is 65 and so on.
27438 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
27439 - Make the "next period" votes into "current period" votes immediately
27440 after publishing the consensus; avoid a heisenbug that made them
27441 stick around indefinitely.
27442 - When we discard a vote as a duplicate, do not report this as
27444 - Treat missing v3 keys or certificates as an error when running as a
27445 v3 directory authority.
27446 - When we're configured to be a v3 authority, but we're only listed
27447 as a non-v3 authority in our DirServer line for ourself, correct
27449 - If an authority doesn't have a qualified hostname, just put
27450 its address in the vote. This fixes the problem where we referred to
27451 "moria on moria:9031."
27452 - Distinguish between detached signatures for the wrong period, and
27453 detached signatures for a divergent vote.
27454 - Fix a small memory leak when computing a consensus.
27455 - When there's no consensus, we were forming a vote every 30
27456 minutes, but writing the "valid-after" line in our vote based
27457 on our configured V3AuthVotingInterval: so unless the intervals
27458 matched up, we immediately rejected our own vote because it didn't
27459 start at the voting interval that caused us to construct a vote.
27461 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
27462 - Delete unverified-consensus when the real consensus is set.
27463 - Consider retrying a consensus networkstatus fetch immediately
27464 after one fails: don't wait 60 seconds to notice.
27465 - When fetching a consensus as a cache, wait until a newer consensus
27466 should exist before trying to replace the current one.
27467 - Use a more forgiving schedule for retrying failed consensus
27468 downloads than for other types.
27470 o Minor bugfixes (other directory issues):
27471 - Correct the implementation of "download votes by digest." Bugfix on
27473 - Authorities no longer send back "400 you're unreachable please fix
27474 it" errors to Tor servers that aren't online all the time. We're
27475 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
27477 o Minor bugfixes (controller):
27478 - Don't reset trusted dir server list when we set a configuration
27479 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
27480 - Respond to INT and TERM SIGNAL commands before we execute the
27481 signal, in case the signal shuts us down. We had a patch in
27482 0.1.2.1-alpha that tried to do this by queueing the response on
27483 the connection's buffer before shutting down, but that really
27484 isn't the same thing at all. Bug located by Matt Edman.
27486 o Minor bugfixes (misc):
27487 - Correctly check for bad options to the "PublishServerDescriptor"
27488 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
27489 - Stop leaking memory on failing case of base32_decode, and make
27490 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
27491 - Don't try to download extrainfo documents when we're trying to
27492 fetch enough directory info to build a circuit: having enough
27493 info should get priority. Bugfix on 0.2.0.x.
27494 - Don't complain that "your server has not managed to confirm that its
27495 ports are reachable" if we haven't been able to build any circuits
27496 yet. Bug found by spending four hours without a v3 consensus. Bugfix
27498 - Detect the reason for failing to mmap a descriptor file we just
27499 wrote, and give a more useful log message. Fixes bug 533. Bugfix
27502 o Code simplifications and refactoring:
27503 - Remove support for the old bw_accounting file: we've been storing
27504 bandwidth accounting information in the state file since
27505 0.1.2.5-alpha. This may result in bandwidth accounting errors
27506 if you try to upgrade from 0.1.1.x or earlier, or if you try to
27507 downgrade to 0.1.1.x or earlier.
27508 - New convenience code to locate a file within the DataDirectory.
27509 - Move non-authority functionality out of dirvote.c.
27510 - Refactor the arguments for router_pick_{directory_|trusteddir}server
27511 so that they all take the same named flags.
27514 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
27515 Unix users an easy way to script their Tor process (e.g. by
27516 adjusting bandwidth based on the time of the day).
27519 Changes in version 0.2.0.8-alpha - 2007-10-12
27520 This eighth development snapshot fixes a crash bug that's been bothering
27521 us since February 2007, lets bridge authorities store a list of bridge
27522 descriptors they've seen, gets v3 directory voting closer to working,
27523 starts caching v3 directory consensus documents on directory mirrors,
27524 and fixes a variety of smaller issues including some minor memory leaks.
27526 o Major features (router descriptor cache):
27527 - Store routers in a file called cached-descriptors instead of in
27528 cached-routers. Initialize cached-descriptors from cached-routers
27529 if the old format is around. The new format allows us to store
27530 annotations along with descriptors.
27531 - Use annotations to record the time we received each descriptor, its
27532 source, and its purpose.
27533 - Disable the SETROUTERPURPOSE controller command: it is now
27535 - Controllers should now specify cache=no or cache=yes when using
27536 the +POSTDESCRIPTOR command.
27537 - Bridge authorities now write bridge descriptors to disk, meaning
27538 we can export them to other programs and begin distributing them
27541 o Major features (directory authorities):
27542 - When a v3 authority is missing votes or signatures, it now tries
27544 - Directory authorities track weighted fractional uptime as well as
27545 weighted mean-time-between failures. WFU is suitable for deciding
27546 whether a node is "usually up", while MTBF is suitable for deciding
27547 whether a node is "likely to stay up." We need both, because
27548 "usually up" is a good requirement for guards, while "likely to
27549 stay up" is a good requirement for long-lived connections.
27551 o Major features (v3 directory system):
27552 - Caches now download v3 network status documents as needed,
27553 and download the descriptors listed in them.
27554 - All hosts now attempt to download and keep fresh v3 authority
27555 certificates, and re-attempt after failures.
27556 - More internal-consistency checks for vote parsing.
27558 o Major bugfixes (crashes):
27559 - If a connection is shut down abruptly because of something that
27560 happened inside connection_flushed_some(), do not call
27561 connection_finished_flushing(). Should fix bug 451. Bugfix on
27564 o Major bugfixes (performance):
27565 - Fix really bad O(n^2) performance when parsing a long list of
27566 routers: Instead of searching the entire list for an "extra-info "
27567 string which usually wasn't there, once for every routerinfo
27568 we read, just scan lines forward until we find one we like.
27570 - When we add data to a write buffer in response to the data on that
27571 write buffer getting low because of a flush, do not consider the
27572 newly added data as a candidate for immediate flushing, but rather
27573 make it wait until the next round of writing. Otherwise, we flush
27574 and refill recursively, and a single greedy TLS connection can
27575 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
27577 o Minor features (v3 authority system):
27578 - Add more ways for tools to download the votes that lead to the
27580 - Send a 503 when low on bandwidth and a vote, consensus, or
27581 certificate is requested.
27582 - If-modified-since is now implemented properly for all kinds of
27583 certificate requests.
27585 o Minor bugfixes (network statuses):
27586 - Tweak the implementation of proposal 109 slightly: allow at most
27587 two Tor servers on the same IP address, except if it's the location
27588 of a directory authority, in which case allow five. Bugfix on
27591 o Minor bugfixes (controller):
27592 - When sending a status event to the controller telling it that an
27593 OR address is reachable, set the port correctly. (Previously we
27594 were reporting the dir port.) Bugfix on 0.1.2.x.
27596 o Minor bugfixes (v3 directory system):
27597 - Fix logic to look up a cert by its signing key digest. Bugfix on
27599 - Only change the reply to a vote to "OK" if it's not already
27600 set. This gets rid of annoying "400 OK" log messages, which may
27601 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
27602 - When we get a valid consensus, recompute the voting schedule.
27603 - Base the valid-after time of a vote on the consensus voting
27604 schedule, not on our preferred schedule.
27605 - Make the return values and messages from signature uploads and
27606 downloads more sensible.
27607 - Fix a memory leak when serving votes and consensus documents, and
27608 another when serving certificates.
27610 o Minor bugfixes (performance):
27611 - Use a slightly simpler string hashing algorithm (copying Python's
27612 instead of Java's) and optimize our digest hashing algorithm to take
27613 advantage of 64-bit platforms and to remove some possibly-costly
27615 - Fix a minor memory leak whenever we parse guards from our state
27616 file. Bugfix on 0.2.0.7-alpha.
27617 - Fix a minor memory leak whenever we write out a file. Bugfix on
27619 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
27620 command. Bugfix on 0.2.0.5-alpha.
27622 o Minor bugfixes (portability):
27623 - On some platforms, accept() can return a broken address. Detect
27624 this more quietly, and deal accordingly. Fixes bug 483.
27625 - Stop calling tor_strlower() on uninitialized memory in some cases.
27626 Bugfix in 0.2.0.7-alpha.
27628 o Minor bugfixes (usability):
27629 - Treat some 403 responses from directory servers as INFO rather than
27630 WARN-severity events.
27631 - It's not actually an error to find a non-pending entry in the DNS
27632 cache when canceling a pending resolve. Don't log unless stuff is
27633 fishy. Resolves bug 463.
27635 o Minor bugfixes (anonymity):
27636 - Never report that we've used more bandwidth than we're willing to
27637 relay: it leaks how much non-relay traffic we're using. Resolves
27639 - When looking for a circuit to cannibalize, consider family as well
27640 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
27641 circuit cannibalization).
27643 o Code simplifications and refactoring:
27644 - Make a bunch of functions static. Remove some dead code.
27645 - Pull out about a third of the really big routerlist.c; put it in a
27646 new module, networkstatus.c.
27647 - Merge the extra fields in local_routerstatus_t back into
27648 routerstatus_t: we used to need one routerstatus_t for each
27649 authority's opinion, plus a local_routerstatus_t for the locally
27650 computed consensus opinion. To save space, we put the locally
27651 modified fields into local_routerstatus_t, and only the common
27652 stuff into routerstatus_t. But once v3 directories are in use,
27653 clients and caches will no longer need to hold authority opinions;
27654 thus, the rationale for keeping the types separate is now gone.
27655 - Make the code used to reschedule and reattempt downloads more
27657 - Turn all 'Are we a directory server/mirror?' logic into a call to
27659 - Remove the code to generate the oldest (v1) directory format.
27660 The code has been disabled since 0.2.0.5-alpha.
27663 Changes in version 0.2.0.7-alpha - 2007-09-21
27664 This seventh development snapshot makes bridges work again, makes bridge
27665 authorities work for the first time, fixes two huge performance flaws
27666 in hidden services, and fixes a variety of minor issues.
27668 o New directory authorities:
27669 - Set up moria1 and tor26 as the first v3 directory authorities. See
27670 doc/spec/dir-spec.txt for details on the new directory design.
27672 o Major bugfixes (crashes):
27673 - Fix possible segfaults in functions called from
27674 rend_process_relay_cell(). Bugfix on 0.1.2.x.
27676 o Major bugfixes (bridges):
27677 - Fix a bug that made servers send a "404 Not found" in response to
27678 attempts to fetch their server descriptor. This caused Tor servers
27679 to take many minutes to establish reachability for their DirPort,
27680 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
27681 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
27682 users configure that and specify a bridge with an identity
27683 fingerprint, now they will lookup the bridge descriptor at the
27684 default bridge authority via a one-hop tunnel, but once circuits
27685 are established they will switch to a three-hop tunnel for later
27686 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
27688 o Major bugfixes (hidden services):
27689 - Hidden services were choosing introduction points uniquely by
27690 hexdigest, but when constructing the hidden service descriptor
27691 they merely wrote the (potentially ambiguous) nickname.
27692 - Clients now use the v2 intro format for hidden service
27693 connections: they specify their chosen rendezvous point by identity
27694 digest rather than by (potentially ambiguous) nickname. Both
27695 are bugfixes on 0.1.2.x, and they could speed up hidden service
27696 connections dramatically. Thanks to Karsten Loesing.
27698 o Minor features (security):
27699 - As a client, do not believe any server that tells us that an
27700 address maps to an internal address space.
27701 - Make it possible to enable HashedControlPassword and
27702 CookieAuthentication at the same time.
27704 o Minor features (guard nodes):
27705 - Tag every guard node in our state file with the version that
27706 we believe added it, or with our own version if we add it. This way,
27707 if a user temporarily runs an old version of Tor and then switches
27708 back to a new one, she doesn't automatically lose her guards.
27710 o Minor features (speed):
27711 - When implementing AES counter mode, update only the portions of the
27712 counter buffer that need to change, and don't keep separate
27713 network-order and host-order counters when they are the same (i.e.,
27714 on big-endian hosts.)
27716 o Minor features (controller):
27717 - Accept LF instead of CRLF on controller, since some software has a
27718 hard time generating real Internet newlines.
27719 - Add GETINFO values for the server status events
27720 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
27723 o Removed features:
27724 - Routers no longer include bandwidth-history lines in their
27725 descriptors; this information is already available in extra-info
27726 documents, and including it in router descriptors took up 60%
27727 (!) of compressed router descriptor downloads. Completes
27728 implementation of proposal 104.
27729 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
27730 and TorControl.py, as they use the old v0 controller protocol,
27731 and are obsoleted by TorFlow anyway.
27732 - Drop support for v1 rendezvous descriptors, since we never used
27733 them anyway, and the code has probably rotted by now. Based on
27734 patch from Karsten Loesing.
27735 - On OSX, stop warning the user that kqueue support in libevent is
27736 "experimental", since it seems to have worked fine for ages.
27739 - When generating information telling us how to extend to a given
27740 router, do not try to include the nickname if it is absent. Fixes
27741 bug 467. Bugfix on 0.2.0.3-alpha.
27742 - Fix a user-triggerable (but not remotely-triggerable) segfault
27743 in expand_filename(). Bugfix on 0.1.2.x.
27744 - Fix a memory leak when freeing incomplete requests from DNSPort.
27745 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
27746 - Don't try to access (or alter) the state file when running
27747 --list-fingerprint or --verify-config or --hash-password. (Resolves
27748 bug 499.) Bugfix on 0.1.2.x.
27749 - Servers used to decline to publish their DirPort if their
27750 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
27751 were below a threshold. Now they only look at BandwidthRate and
27752 RelayBandwidthRate. Bugfix on 0.1.2.x.
27753 - Remove an optimization in the AES counter-mode code that assumed
27754 that the counter never exceeded 2^68. When the counter can be set
27755 arbitrarily as an IV (as it is by Karsten's new hidden services
27756 code), this assumption no longer holds. Bugfix on 0.1.2.x.
27757 - Resume listing "AUTHORITY" flag for authorities in network status.
27758 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
27760 o Code simplifications and refactoring:
27761 - Revamp file-writing logic so we don't need to have the entire
27762 contents of a file in memory at once before we write to disk. Tor,
27764 - Turn "descriptor store" into a full-fledged type.
27765 - Move all NT services code into a separate source file.
27766 - Unify all code that computes medians, percentile elements, etc.
27767 - Get rid of a needless malloc when parsing address policies.
27770 Changes in version 0.1.2.17 - 2007-08-30
27771 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
27772 X bundles. Vidalia 0.0.14 makes authentication required for the
27773 ControlPort in the default configuration, which addresses important
27774 security risks. Everybody who uses Vidalia (or another controller)
27777 In addition, this Tor update fixes major load balancing problems with
27778 path selection, which should speed things up a lot once many people
27781 o Major bugfixes (security):
27782 - We removed support for the old (v0) control protocol. It has been
27783 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
27784 become more of a headache than it's worth.
27786 o Major bugfixes (load balancing):
27787 - When choosing nodes for non-guard positions, weight guards
27788 proportionally less, since they already have enough load. Patch
27790 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27791 will allow fast Tor servers to get more attention.
27792 - When we're upgrading from an old Tor version, forget our current
27793 guards and pick new ones according to the new weightings. These
27794 three load balancing patches could raise effective network capacity
27795 by a factor of four. Thanks to Mike Perry for measurements.
27797 o Major bugfixes (stream expiration):
27798 - Expire not-yet-successful application streams in all cases if
27799 they've been around longer than SocksTimeout. Right now there are
27800 some cases where the stream will live forever, demanding a new
27801 circuit every 15 seconds. Fixes bug 454; reported by lodger.
27803 o Minor features (controller):
27804 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27805 is valid before any authentication has been received. It tells
27806 a controller what kind of authentication is expected, and what
27807 protocol is spoken. Implements proposal 119.
27809 o Minor bugfixes (performance):
27810 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
27811 greatly speeding up loading cached-routers from disk on startup.
27812 - Disable sentinel-based debugging for buffer code: we squashed all
27813 the bugs that this was supposed to detect a long time ago, and now
27814 its only effect is to change our buffer sizes from nice powers of
27815 two (which platform mallocs tend to like) to values slightly over
27816 powers of two (which make some platform mallocs sad).
27818 o Minor bugfixes (misc):
27819 - If exit bandwidth ever exceeds one third of total bandwidth, then
27820 use the correct formula to weight exit nodes when choosing paths.
27821 Based on patch from Mike Perry.
27822 - Choose perfectly fairly among routers when choosing by bandwidth and
27823 weighting by fraction of bandwidth provided by exits. Previously, we
27824 would choose with only approximate fairness, and correct ourselves
27825 if we ran off the end of the list.
27826 - If we require CookieAuthentication but we fail to write the
27827 cookie file, we would warn but not exit, and end up in a state
27828 where no controller could authenticate. Now we exit.
27829 - If we require CookieAuthentication, stop generating a new cookie
27830 every time we change any piece of our config.
27831 - Refuse to start with certain directory authority keys, and
27832 encourage people using them to stop.
27833 - Terminate multi-line control events properly. Original patch
27835 - Fix a minor memory leak when we fail to find enough suitable
27836 servers to choose a circuit.
27837 - Stop leaking part of the descriptor when we run into a particularly
27838 unparseable piece of it.
27841 Changes in version 0.2.0.6-alpha - 2007-08-26
27842 This sixth development snapshot features a new Vidalia version in the
27843 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
27844 the ControlPort in the default configuration, which addresses important
27847 In addition, this snapshot fixes major load balancing problems
27848 with path selection, which should speed things up a lot once many
27849 people have upgraded. The directory authorities also use a new
27850 mean-time-between-failure approach to tracking which servers are stable,
27851 rather than just looking at the most recent uptime.
27853 o New directory authorities:
27854 - Set up Tonga as the default bridge directory authority.
27857 - Directory authorities now track servers by weighted
27858 mean-times-between-failures. When we have 4 or more days of data,
27859 use measured MTBF rather than declared uptime to decide whether
27860 to call a router Stable. Implements proposal 108.
27862 o Major bugfixes (load balancing):
27863 - When choosing nodes for non-guard positions, weight guards
27864 proportionally less, since they already have enough load. Patch
27866 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
27867 will allow fast Tor servers to get more attention.
27868 - When we're upgrading from an old Tor version, forget our current
27869 guards and pick new ones according to the new weightings. These
27870 three load balancing patches could raise effective network capacity
27871 by a factor of four. Thanks to Mike Perry for measurements.
27873 o Major bugfixes (descriptor parsing):
27874 - Handle unexpected whitespace better in malformed descriptors. Bug
27875 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
27878 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
27879 GETINFO for Torstat to use until it can switch to using extrainfos.
27880 - Optionally (if built with -DEXPORTMALLINFO) export the output
27881 of mallinfo via http, as tor/mallinfo.txt. Only accessible
27885 - Do not intermix bridge routers with controller-added
27886 routers. (Bugfix on 0.2.0.x)
27887 - Do not fail with an assert when accept() returns an unexpected
27888 address family. Addresses but does not wholly fix bug 483. (Bugfix
27890 - Let directory authorities startup even when they can't generate
27891 a descriptor immediately, e.g. because they don't know their
27893 - Stop putting the authentication cookie in a file called "0"
27894 in your working directory if you don't specify anything for the
27895 new CookieAuthFile option. Reported by Matt Edman.
27896 - Make it possible to read the PROTOCOLINFO response in a way that
27897 conforms to our control-spec. Reported by Matt Edman.
27898 - Fix a minor memory leak when we fail to find enough suitable
27899 servers to choose a circuit. Bugfix on 0.1.2.x.
27900 - Stop leaking part of the descriptor when we run into a particularly
27901 unparseable piece of it. Bugfix on 0.1.2.x.
27902 - Unmap the extrainfo cache file on exit.
27905 Changes in version 0.2.0.5-alpha - 2007-08-19
27906 This fifth development snapshot fixes compilation on Windows again;
27907 fixes an obnoxious client-side bug that slowed things down and put
27908 extra load on the network; gets us closer to using the v3 directory
27909 voting scheme; makes it easier for Tor controllers to use cookie-based
27910 authentication; and fixes a variety of other bugs.
27912 o Removed features:
27913 - Version 1 directories are no longer generated in full. Instead,
27914 authorities generate and serve "stub" v1 directories that list
27915 no servers. This will stop Tor versions 0.1.0.x and earlier from
27916 working, but (for security reasons) nobody should be running those
27919 o Major bugfixes (compilation, 0.2.0.x):
27920 - Try to fix Win32 compilation again: improve checking for IPv6 types.
27921 - Try to fix MSVC compilation: build correctly on platforms that do
27922 not define s6_addr16 or s6_addr32.
27923 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
27926 o Major bugfixes (stream expiration):
27927 - Expire not-yet-successful application streams in all cases if
27928 they've been around longer than SocksTimeout. Right now there are
27929 some cases where the stream will live forever, demanding a new
27930 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
27931 reported by lodger.
27933 o Minor features (directory servers):
27934 - When somebody requests a list of statuses or servers, and we have
27935 none of those, return a 404 rather than an empty 200.
27937 o Minor features (directory voting):
27938 - Store v3 consensus status consensuses on disk, and reload them
27941 o Minor features (security):
27942 - Warn about unsafe ControlPort configurations.
27943 - Refuse to start with certain directory authority keys, and
27944 encourage people using them to stop.
27946 o Minor features (controller):
27947 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
27948 is valid before any authentication has been received. It tells
27949 a controller what kind of authentication is expected, and what
27950 protocol is spoken. Implements proposal 119.
27951 - New config option CookieAuthFile to choose a new location for the
27952 cookie authentication file, and config option
27953 CookieAuthFileGroupReadable to make it group-readable.
27955 o Minor features (unit testing):
27956 - Add command-line arguments to unit-test executable so that we can
27957 invoke any chosen test from the command line rather than having
27958 to run the whole test suite at once; and so that we can turn on
27959 logging for the unit tests.
27961 o Minor bugfixes (on 0.1.2.x):
27962 - If we require CookieAuthentication but we fail to write the
27963 cookie file, we would warn but not exit, and end up in a state
27964 where no controller could authenticate. Now we exit.
27965 - If we require CookieAuthentication, stop generating a new cookie
27966 every time we change any piece of our config.
27967 - When loading bandwidth history, do not believe any information in
27968 the future. Fixes bug 434.
27969 - When loading entry guard information, do not believe any information
27971 - When we have our clock set far in the future and generate an
27972 onion key, then re-set our clock to be correct, we should not stop
27973 the onion key from getting rotated.
27974 - Clean up torrc sample config file.
27975 - Do not automatically run configure from autogen.sh. This
27976 non-standard behavior tended to annoy people who have built other
27979 o Minor bugfixes (on 0.2.0.x):
27980 - Fix a bug with AutomapHostsOnResolve that would always cause
27981 the second request to fail. Bug reported by Kate. Bugfix on
27983 - Fix a bug in ADDRMAP controller replies that would sometimes
27984 try to print a NULL. Patch from tup.
27985 - Read v3 directory authority keys from the right location.
27986 - Numerous bugfixes to directory voting code.
27989 Changes in version 0.1.2.16 - 2007-08-01
27990 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
27991 remote attacker in certain situations to rewrite the user's torrc
27992 configuration file. This can completely compromise anonymity of users
27993 in most configurations, including those running the Vidalia bundles,
27994 TorK, etc. Or worse.
27996 o Major security fixes:
27997 - Close immediately after missing authentication on control port;
27998 do not allow multiple authentication attempts.
28001 Changes in version 0.2.0.4-alpha - 2007-08-01
28002 This fourth development snapshot fixes a critical security vulnerability
28003 for most users, specifically those running Vidalia, TorK, etc. Everybody
28004 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
28006 o Major security fixes:
28007 - Close immediately after missing authentication on control port;
28008 do not allow multiple authentication attempts.
28010 o Major bugfixes (compilation):
28011 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
28014 o Minor features (performance):
28015 - Be even more aggressive about releasing RAM from small
28016 empty buffers. Thanks to our free-list code, this shouldn't be too
28017 performance-intensive.
28018 - Disable sentinel-based debugging for buffer code: we squashed all
28019 the bugs that this was supposed to detect a long time ago, and
28020 now its only effect is to change our buffer sizes from nice
28021 powers of two (which platform mallocs tend to like) to values
28022 slightly over powers of two (which make some platform mallocs sad).
28023 - Log malloc statistics from mallinfo() on platforms where it
28027 Changes in version 0.2.0.3-alpha - 2007-07-29
28028 This third development snapshot introduces new experimental
28029 blocking-resistance features and a preliminary version of the v3
28030 directory voting design, and includes many other smaller features
28034 - The first pieces of our "bridge" design for blocking-resistance
28035 are implemented. People can run bridge directory authorities;
28036 people can run bridges; and people can configure their Tor clients
28037 with a set of bridges to use as the first hop into the Tor network.
28038 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
28040 - Create listener connections before we setuid to the configured
28041 User and Group. Now non-Windows users can choose port values
28042 under 1024, start Tor as root, and have Tor bind those ports
28043 before it changes to another UID. (Windows users could already
28045 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
28046 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
28047 on "vserver" accounts. (Patch from coderman.)
28048 - Be even more aggressive about separating local traffic from relayed
28049 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
28051 o Major features (experimental):
28052 - First cut of code for "v3 dir voting": directory authorities will
28053 vote on a common network status document rather than each publishing
28054 their own opinion. This code needs more testing and more corner-case
28055 handling before it's ready for use.
28058 - Directory authorities now call routers Fast if their bandwidth is
28059 at least 100KB/s, and consider their bandwidth adequate to be a
28060 Guard if it is at least 250KB/s, no matter the medians. This fix
28061 complements proposal 107. [Bugfix on 0.1.2.x]
28062 - Directory authorities now never mark more than 3 servers per IP as
28063 Valid and Running. (Implements proposal 109, by Kevin Bauer and
28065 - Minor change to organizationName and commonName generation
28066 procedures in TLS certificates during Tor handshakes, to invalidate
28067 some earlier censorware approaches. This is not a long-term
28068 solution, but applying it will give us a bit of time to look into
28069 the epidemiology of countermeasures as they spread.
28071 o Major bugfixes (directory):
28072 - Rewrite directory tokenization code to never run off the end of
28073 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
28075 o Minor features (controller):
28076 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
28077 match requests to applications. (Patch from Robert Hogan.)
28078 - Report address and port correctly on connections to DNSPort. (Patch
28079 from Robert Hogan.)
28080 - Add a RESOLVE command to launch hostname lookups. (Original patch
28081 from Robert Hogan.)
28082 - Add GETINFO status/enough-dir-info to let controllers tell whether
28083 Tor has downloaded sufficient directory information. (Patch
28085 - You can now use the ControlSocket option to tell Tor to listen for
28086 controller connections on Unix domain sockets on systems that
28087 support them. (Patch from Peter Palfrader.)
28088 - STREAM NEW events are generated for DNSPort requests and for
28089 tunneled directory connections. (Patch from Robert Hogan.)
28090 - New "GETINFO address-mappings/*" command to get address mappings
28091 with expiry information. "addr-mappings/*" is now deprecated.
28094 o Minor features (misc):
28095 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
28097 - The tor-gencert tool for v3 directory authorities now creates all
28098 files as readable to the file creator only, and write-protects
28099 the authority identity key.
28100 - When dumping memory usage, list bytes used in buffer memory
28102 - When running with dmalloc, dump more stats on hup and on exit.
28103 - Directory authorities now fail quickly and (relatively) harmlessly
28104 if they generate a network status document that is somehow
28107 o Traffic load balancing improvements:
28108 - If exit bandwidth ever exceeds one third of total bandwidth, then
28109 use the correct formula to weight exit nodes when choosing paths.
28110 (Based on patch from Mike Perry.)
28111 - Choose perfectly fairly among routers when choosing by bandwidth and
28112 weighting by fraction of bandwidth provided by exits. Previously, we
28113 would choose with only approximate fairness, and correct ourselves
28114 if we ran off the end of the list. [Bugfix on 0.1.2.x]
28116 o Performance improvements:
28117 - Be more aggressive with freeing buffer RAM or putting it on the
28119 - Use Critical Sections rather than Mutexes for synchronizing threads
28120 on win32; Mutexes are heavier-weight, and designed for synchronizing
28123 o Deprecated and removed features:
28124 - RedirectExits is now deprecated.
28125 - Stop allowing address masks that do not correspond to bit prefixes.
28126 We have warned about these for a really long time; now it's time
28127 to reject them. (Patch from croup.)
28129 o Minor bugfixes (directory):
28130 - Fix another crash bug related to extra-info caching. (Bug found by
28131 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
28132 - Directories no longer return a "304 not modified" when they don't
28133 have the networkstatus the client asked for. Also fix a memory
28134 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
28135 - We had accidentally labelled 0.1.2.x directory servers as not
28136 suitable for begin_dir requests, and had labelled no directory
28137 servers as suitable for uploading extra-info documents. [Bugfix
28140 o Minor bugfixes (dns):
28141 - Fix a crash when DNSPort is set more than once. (Patch from Robert
28142 Hogan.) [Bugfix on 0.2.0.2-alpha]
28143 - Add DNSPort connections to the global connection list, so that we
28144 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
28146 - Fix a dangling reference that could lead to a crash when DNSPort is
28147 changed or closed (Patch from Robert Hogan.) [Bugfix on
28150 o Minor bugfixes (controller):
28151 - Provide DNS expiry times in GMT, not in local time. For backward
28152 compatibility, ADDRMAP events only provide GMT expiry in an extended
28153 field. "GETINFO address-mappings" always does the right thing.
28154 - Use CRLF line endings properly in NS events.
28155 - Terminate multi-line control events properly. (Original patch
28156 from tup.) [Bugfix on 0.1.2.x-alpha]
28157 - Do not include spaces in SOURCE_ADDR fields in STREAM
28158 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
28161 Changes in version 0.1.2.15 - 2007-07-17
28162 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
28163 problems, fixes compilation on BSD, and fixes a variety of other
28164 bugs. Everybody should upgrade.
28166 o Major bugfixes (compilation):
28167 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
28169 o Major bugfixes (crashes):
28170 - Try even harder not to dereference the first character after
28171 an mmap(). Reported by lodger.
28172 - Fix a crash bug in directory authorities when we re-number the
28173 routerlist while inserting a new router.
28174 - When the cached-routers file is an even multiple of the page size,
28175 don't run off the end and crash. (Fixes bug 455; based on idea
28177 - Fix eventdns.c behavior on Solaris: It is critical to include
28178 orconfig.h _before_ sys/types.h, so that we can get the expected
28179 definition of _FILE_OFFSET_BITS.
28181 o Major bugfixes (security):
28182 - Fix a possible buffer overrun when using BSD natd support. Bug
28184 - When sending destroy cells from a circuit's origin, don't include
28185 the reason for tearing down the circuit. The spec says we didn't,
28186 and now we actually don't. Reported by lodger.
28187 - Keep streamids from different exits on a circuit separate. This
28188 bug may have allowed other routers on a given circuit to inject
28189 cells into streams. Reported by lodger; fixes bug 446.
28190 - If there's a never-before-connected-to guard node in our list,
28191 never choose any guards past it. This way we don't expand our
28192 guard list unless we need to.
28194 o Minor bugfixes (guard nodes):
28195 - Weight guard selection by bandwidth, so that low-bandwidth nodes
28196 don't get overused as guards.
28198 o Minor bugfixes (directory):
28199 - Correctly count the number of authorities that recommend each
28200 version. Previously, we were under-counting by 1.
28201 - Fix a potential crash bug when we load many server descriptors at
28202 once and some of them make others of them obsolete. Fixes bug 458.
28204 o Minor bugfixes (hidden services):
28205 - Stop tearing down the whole circuit when the user asks for a
28206 connection to a port that the hidden service didn't configure.
28209 o Minor bugfixes (misc):
28210 - On Windows, we were preventing other processes from reading
28211 cached-routers while Tor was running. Reported by janbar.
28212 - Fix a possible (but very unlikely) bug in picking routers by
28213 bandwidth. Add a log message to confirm that it is in fact
28214 unlikely. Patch from lodger.
28215 - Backport a couple of memory leak fixes.
28216 - Backport miscellaneous cosmetic bugfixes.
28219 Changes in version 0.2.0.2-alpha - 2007-06-02
28220 o Major bugfixes on 0.2.0.1-alpha:
28221 - Fix an assertion failure related to servers without extra-info digests.
28222 Resolves bugs 441 and 442.
28224 o Minor features (directory):
28225 - Support "If-Modified-Since" when answering HTTP requests for
28226 directories, running-routers documents, and network-status documents.
28227 (There's no need to support it for router descriptors, since those
28228 are downloaded by descriptor digest.)
28230 o Minor build issues:
28231 - Clear up some MIPSPro compiler warnings.
28232 - When building from a tarball on a machine that happens to have SVK
28233 installed, report the micro-revision as whatever version existed
28234 in the tarball, not as "x".
28237 Changes in version 0.2.0.1-alpha - 2007-06-01
28238 This early development snapshot provides new features for people running
28239 Tor as both a client and a server (check out the new RelayBandwidth
28240 config options); lets Tor run as a DNS proxy; and generally moves us
28241 forward on a lot of fronts.
28243 o Major features, server usability:
28244 - New config options RelayBandwidthRate and RelayBandwidthBurst:
28245 a separate set of token buckets for relayed traffic. Right now
28246 relayed traffic is defined as answers to directory requests, and
28247 OR connections that don't have any local circuits on them.
28249 o Major features, client usability:
28250 - A client-side DNS proxy feature to replace the need for
28251 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
28252 for DNS requests on port 9999, use the Tor network to resolve them
28253 anonymously, and send the reply back like a regular DNS server.
28254 The code still only implements a subset of DNS.
28255 - Make PreferTunneledDirConns and TunnelDirConns work even when
28256 we have no cached directory info. This means Tor clients can now
28257 do all of their connections protected by TLS.
28259 o Major features, performance and efficiency:
28260 - Directory authorities accept and serve "extra info" documents for
28261 routers. These documents contain fields from router descriptors
28262 that aren't usually needed, and that use a lot of excess
28263 bandwidth. Once these fields are removed from router descriptors,
28264 the bandwidth savings should be about 60%. [Partially implements
28266 - Servers upload extra-info documents to any authority that accepts
28267 them. Authorities (and caches that have been configured to download
28268 extra-info documents) download them as needed. [Partially implements
28270 - Change the way that Tor buffers data that it is waiting to write.
28271 Instead of queueing data cells in an enormous ring buffer for each
28272 client->OR or OR->OR connection, we now queue cells on a separate
28273 queue for each circuit. This lets us use less slack memory, and
28274 will eventually let us be smarter about prioritizing different kinds
28276 - Use memory pools to allocate cells with better speed and memory
28277 efficiency, especially on platforms where malloc() is inefficient.
28278 - Stop reading on edge connections when their corresponding circuit
28279 buffers are full; start again as the circuits empty out.
28281 o Major features, other:
28282 - Add an HSAuthorityRecordStats option that hidden service authorities
28283 can use to track statistics of overall hidden service usage without
28284 logging information that would be very useful to an attacker.
28285 - Start work implementing multi-level keys for directory authorities:
28286 Add a standalone tool to generate key certificates. (Proposal 103.)
28289 - Directory authorities now call routers Stable if they have an
28290 uptime of at least 30 days, even if that's not the median uptime
28291 in the network. Implements proposal 107, suggested by Kevin Bauer
28294 o Minor fixes (resource management):
28295 - Count the number of open sockets separately from the number
28296 of active connection_t objects. This will let us avoid underusing
28297 our allocated connection limit.
28298 - We no longer use socket pairs to link an edge connection to an
28299 anonymous directory connection or a DirPort test connection.
28300 Instead, we track the link internally and transfer the data
28301 in-process. This saves two sockets per "linked" connection (at the
28302 client and at the server), and avoids the nasty Windows socketpair()
28304 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
28305 for every single inactive connection_t. Free items from the
28306 4k/16k-buffer free lists when they haven't been used for a while.
28308 o Minor features (build):
28309 - Make autoconf search for libevent, openssl, and zlib consistently.
28310 - Update deprecated macros in configure.in.
28311 - When warning about missing headers, tell the user to let us
28312 know if the compile succeeds anyway, so we can downgrade the
28314 - Include the current subversion revision as part of the version
28315 string: either fetch it directly if we're in an SVN checkout, do
28316 some magic to guess it if we're in an SVK checkout, or use
28317 the last-detected version if we're building from a .tar.gz.
28318 Use this version consistently in log messages.
28320 o Minor features (logging):
28321 - Always prepend "Bug: " to any log message about a bug.
28322 - Put a platform string (e.g. "Linux i686") in the startup log
28323 message, so when people paste just their logs, we know if it's
28324 OpenBSD or Windows or what.
28325 - When logging memory usage, break down memory used in buffers by
28328 o Minor features (directory system):
28329 - New config option V2AuthoritativeDirectory that all directory
28330 authorities should set. This will let future authorities choose
28331 not to serve V2 directory information.
28332 - Directory authorities allow multiple router descriptors and/or extra
28333 info documents to be uploaded in a single go. This will make
28334 implementing proposal 104 simpler.
28336 o Minor features (controller):
28337 - Add a new config option __DisablePredictedCircuits designed for
28338 use by the controller, when we don't want Tor to build any circuits
28340 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
28341 so we can exit from the middle of the circuit.
28342 - Implement "getinfo status/circuit-established".
28343 - Implement "getinfo status/version/..." so a controller can tell
28344 whether the current version is recommended, and whether any versions
28345 are good, and how many authorities agree. (Patch from shibz.)
28347 o Minor features (hidden services):
28348 - Allow multiple HiddenServicePort directives with the same virtual
28349 port; when they occur, the user is sent round-robin to one
28350 of the target ports chosen at random. Partially fixes bug 393 by
28351 adding limited ad-hoc round-robining.
28353 o Minor features (other):
28355 - Add a new AutomapHostsOnResolve option: when it is enabled, any
28356 resolve request for hosts matching a given pattern causes Tor to
28357 generate an internal virtual address mapping for that host. This
28358 allows DNSPort to work sensibly with hidden service users. By
28359 default, .exit and .onion addresses are remapped; the list of
28360 patterns can be reconfigured with AutomapHostsSuffixes.
28361 - Add an "-F" option to tor-resolve to force a resolve for a .onion
28362 address. Thanks to the AutomapHostsOnResolve option, this is no
28363 longer a completely silly thing to do.
28364 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
28365 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
28366 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
28367 minus 1 byte: the actual maximum declared bandwidth.
28369 o Removed features:
28370 - Removed support for the old binary "version 0" controller protocol.
28371 This has been deprecated since 0.1.1, and warnings have been issued
28372 since 0.1.2. When we encounter a v0 control message, we now send
28373 back an error and close the connection.
28374 - Remove the old "dns worker" server DNS code: it hasn't been default
28375 since 0.1.2.2-alpha, and all the servers seem to be using the new
28378 o Minor bugfixes (portability):
28379 - Even though Windows is equally happy with / and \ as path separators,
28380 try to use \ consistently on Windows and / consistently on Unix: it
28381 makes the log messages nicer.
28382 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
28383 - Read resolv.conf files correctly on platforms where read() returns
28384 partial results on small file reads.
28386 o Minor bugfixes (directory):
28387 - Correctly enforce that elements of directory objects do not appear
28388 more often than they are allowed to appear.
28389 - When we are reporting the DirServer line we just parsed, we were
28390 logging the second stanza of the key fingerprint, not the first.
28392 o Minor bugfixes (logging):
28393 - When we hit an EOF on a log (probably because we're shutting down),
28394 don't try to remove the log from the list: just mark it as
28395 unusable. (Bulletproofs against bug 222.)
28397 o Minor bugfixes (other):
28398 - In the exitlist script, only consider the most recently published
28399 server descriptor for each server. Also, when the user requests
28400 a list of servers that _reject_ connections to a given address,
28401 explicitly exclude the IPs that also have servers that accept
28402 connections to that address. (Resolves bug 405.)
28403 - Stop allowing hibernating servers to be "stable" or "fast".
28404 - On Windows, we were preventing other processes from reading
28405 cached-routers while Tor was running. (Reported by janbar)
28406 - Make the NodeFamilies config option work. (Reported by
28407 lodger -- it has never actually worked, even though we added it
28409 - Check return values from pthread_mutex functions.
28410 - Don't save non-general-purpose router descriptors to the disk cache,
28411 because we have no way of remembering what their purpose was when
28413 - Add even more asserts to hunt down bug 417.
28414 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
28415 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
28416 Add a log message to confirm that it is in fact unlikely.
28418 o Minor bugfixes (controller):
28419 - Make 'getinfo fingerprint' return a 551 error if we're not a
28420 server, so we match what the control spec claims we do. Reported
28422 - Fix a typo in an error message when extendcircuit fails that
28423 caused us to not follow the \r\n-based delimiter protocol. Reported
28426 o Code simplifications and refactoring:
28427 - Stop passing around circuit_t and crypt_path_t pointers that are
28428 implicit in other procedure arguments.
28429 - Drop the old code to choke directory connections when the
28430 corresponding OR connections got full: thanks to the cell queue
28431 feature, OR conns don't get full any more.
28432 - Make dns_resolve() handle attaching connections to circuits
28433 properly, so the caller doesn't have to.
28434 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
28435 - Keep the connection array as a dynamic smartlist_t, rather than as
28436 a fixed-sized array. This is important, as the number of connections
28437 is becoming increasingly decoupled from the number of sockets.
28440 Changes in version 0.1.2.14 - 2007-05-25
28441 Tor 0.1.2.14 changes the addresses of two directory authorities (this
28442 change especially affects those who serve or use hidden services),
28443 and fixes several other crash- and security-related bugs.
28445 o Directory authority changes:
28446 - Two directory authorities (moria1 and moria2) just moved to new
28447 IP addresses. This change will particularly affect those who serve
28448 or use hidden services.
28450 o Major bugfixes (crashes):
28451 - If a directory server runs out of space in the connection table
28452 as it's processing a begin_dir request, it will free the exit stream
28453 but leave it attached to the circuit, leading to unpredictable
28454 behavior. (Reported by seeess, fixes bug 425.)
28455 - Fix a bug in dirserv_remove_invalid() that would cause authorities
28456 to corrupt memory under some really unlikely scenarios.
28457 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
28458 - Avoid segfaults when reading from mmaped descriptor file. (Reported
28461 o Major bugfixes (security):
28462 - When choosing an entry guard for a circuit, avoid using guards
28463 that are in the same family as the chosen exit -- not just guards
28464 that are exactly the chosen exit. (Reported by lodger.)
28466 o Major bugfixes (resource management):
28467 - If a directory authority is down, skip it when deciding where to get
28468 networkstatus objects or descriptors. Otherwise we keep asking
28469 every 10 seconds forever. Fixes bug 384.
28470 - Count it as a failure if we fetch a valid network-status but we
28471 don't want to keep it. Otherwise we'll keep fetching it and keep
28472 not wanting to keep it. Fixes part of bug 422.
28473 - If all of our dirservers have given us bad or no networkstatuses
28474 lately, then stop hammering them once per minute even when we
28475 think they're failed. Fixes another part of bug 422.
28478 - Actually set the purpose correctly for descriptors inserted with
28479 purpose=controller.
28480 - When we have k non-v2 authorities in our DirServer config,
28481 we ignored the last k authorities in the list when updating our
28483 - Correctly back-off from requesting router descriptors that we are
28484 having a hard time downloading.
28485 - Read resolv.conf files correctly on platforms where read() returns
28486 partial results on small file reads.
28487 - Don't rebuild the entire router store every time we get 32K of
28488 routers: rebuild it when the journal gets very large, or when
28489 the gaps in the store get very large.
28492 - When routers publish SVN revisions in their router descriptors,
28493 authorities now include those versions correctly in networkstatus
28495 - Warn when using a version of libevent before 1.3b to run a server on
28496 OSX or BSD: these versions interact badly with userspace threads.
28499 Changes in version 0.1.2.13 - 2007-04-24
28500 This release features some major anonymity fixes, such as safer path
28501 selection; better client performance; faster bootstrapping, better
28502 address detection, and better DNS support for servers; write limiting as
28503 well as read limiting to make servers easier to run; and a huge pile of
28504 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
28506 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
28507 of the Freenode IRC network, remembering his patience and vision for
28508 free speech on the Internet.
28511 - Fix a memory leak when we ask for "all" networkstatuses and we
28512 get one we don't recognize.
28513 - Add more asserts to hunt down bug 417.
28514 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
28517 Changes in version 0.1.2.12-rc - 2007-03-16
28519 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
28520 directory information requested inside Tor connections (i.e. via
28521 begin_dir cells). It only triggered when the same connection was
28522 serving other data at the same time. Reported by seeess.
28525 - When creating a circuit via the controller, send a 'launched'
28526 event when we're done, so we follow the spec better.
28529 Changes in version 0.1.2.11-rc - 2007-03-15
28530 o Minor bugfixes (controller), reported by daejees:
28531 - Correct the control spec to match how the code actually responds
28532 to 'getinfo addr-mappings/*'.
28533 - The control spec described a GUARDS event, but the code
28534 implemented a GUARD event. Standardize on GUARD, but let people
28535 ask for GUARDS too.
28538 Changes in version 0.1.2.10-rc - 2007-03-07
28539 o Major bugfixes (Windows):
28540 - Do not load the NT services library functions (which may not exist)
28541 just to detect if we're a service trying to shut down. Now we run
28542 on Win98 and friends again.
28544 o Minor bugfixes (other):
28545 - Clarify a couple of log messages.
28546 - Fix a misleading socks5 error number.
28549 Changes in version 0.1.2.9-rc - 2007-03-02
28550 o Major bugfixes (Windows):
28551 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
28552 of the usual GCC "%llu". This prevents a bug when saving 64-bit
28553 int configuration values: the high-order 32 bits would get
28554 truncated. In particular, we were being bitten by the default
28555 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
28556 and maybe also bug 397.)
28558 o Minor bugfixes (performance):
28559 - Use OpenSSL's AES implementation on platforms where it's faster.
28560 This could save us as much as 10% CPU usage.
28562 o Minor bugfixes (server):
28563 - Do not rotate onion key immediately after setting it for the first
28566 o Minor bugfixes (directory authorities):
28567 - Stop calling servers that have been hibernating for a long time
28568 "stable". Also, stop letting hibernating or obsolete servers affect
28569 uptime and bandwidth cutoffs.
28570 - Stop listing hibernating servers in the v1 directory.
28572 o Minor bugfixes (hidden services):
28573 - Upload hidden service descriptors slightly less often, to reduce
28574 load on authorities.
28576 o Minor bugfixes (other):
28577 - Fix an assert that could trigger if a controller quickly set then
28578 cleared EntryNodes. Bug found by Udo van den Heuvel.
28579 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
28581 - Fix a potential race condition in the rpm installer. Found by
28583 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
28584 of 2 as indicating that the server is completely bad; it sometimes
28585 means that the server is just bad for the request in question. (may fix
28586 the last of bug 326.)
28587 - Disable encrypted directory connections when we don't have a server
28588 descriptor for the destination. We'll get this working again in
28592 Changes in version 0.1.2.8-beta - 2007-02-26
28593 o Major bugfixes (crashes):
28594 - Stop crashing when the controller asks us to resetconf more than
28595 one config option at once. (Vidalia 0.0.11 does this.)
28596 - Fix a crash that happened on Win98 when we're given command-line
28597 arguments: don't try to load NT service functions from advapi32.dll
28598 except when we need them. (Bug introduced in 0.1.2.7-alpha;
28600 - Fix a longstanding obscure crash bug that could occur when
28601 we run out of DNS worker processes. (Resolves bug 390.)
28603 o Major bugfixes (hidden services):
28604 - Correctly detect whether hidden service descriptor downloads are
28605 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
28607 o Major bugfixes (accounting):
28608 - When we start during an accounting interval before it's time to wake
28609 up, remember to wake up at the correct time. (May fix bug 342.)
28611 o Minor bugfixes (controller):
28612 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
28613 clear the corresponding on_circuit variable, and remember later
28614 that we don't need to send a redundant CLOSED event. Resolves part
28616 - Report events where a resolve succeeded or where we got a socks
28617 protocol error correctly, rather than calling both of them
28619 - Change reported stream target addresses to IP consistently when
28620 we finally get the IP from an exit node.
28621 - Send log messages to the controller even if they happen to be very
28624 o Minor bugfixes (other):
28625 - Display correct results when reporting which versions are
28626 recommended, and how recommended they are. (Resolves bug 383.)
28627 - Improve our estimates for directory bandwidth to be less random:
28628 guess that an unrecognized directory will have the average bandwidth
28629 from all known directories, not that it will have the average
28630 bandwidth from those directories earlier than it on the list.
28631 - If we start a server with ClientOnly 1, then set ClientOnly to 0
28632 and hup, stop triggering an assert based on an empty onion_key.
28633 - On platforms with no working mmap() equivalent, don't warn the
28634 user when cached-routers doesn't exist.
28635 - Warn the user when mmap() [or its equivalent] fails for some reason
28636 other than file-not-found.
28637 - Don't warn the user when cached-routers.new doesn't exist: that's
28638 perfectly fine when starting up for the first time.
28639 - When EntryNodes are configured, rebuild the guard list to contain,
28640 in order: the EntryNodes that were guards before; the rest of the
28641 EntryNodes; the nodes that were guards before.
28642 - Mask out all signals in sub-threads; only the libevent signal
28643 handler should be processing them. This should prevent some crashes
28644 on some machines using pthreads. (Patch from coderman.)
28645 - Fix switched arguments on memset in the implementation of
28646 tor_munmap() for systems with no mmap() call.
28647 - When Tor receives a router descriptor that it asked for, but
28648 no longer wants (because it has received fresh networkstatuses
28649 in the meantime), do not warn the user. Cache the descriptor if
28650 we're a cache; drop it if we aren't.
28651 - Make earlier entry guards _really_ get retried when the network
28653 - On a malformed DNS reply, always give an error to the corresponding
28655 - Build with recent libevents on platforms that do not define the
28656 nonstandard types "u_int8_t" and friends.
28658 o Minor features (controller):
28659 - Warn the user when an application uses the obsolete binary v0
28660 control protocol. We're planning to remove support for it during
28661 the next development series, so it's good to give people some
28663 - Add STREAM_BW events to report per-entry-stream bandwidth
28664 use. (Patch from Robert Hogan.)
28665 - Rate-limit SIGNEWNYM signals in response to controllers that
28666 impolitely generate them for every single stream. (Patch from
28667 mwenge; closes bug 394.)
28668 - Make REMAP stream events have a SOURCE (cache or exit), and
28669 make them generated in every case where we get a successful
28670 connected or resolved cell.
28672 o Minor bugfixes (performance):
28673 - Call router_have_min_dir_info half as often. (This is showing up in
28674 some profiles, but not others.)
28675 - When using GCC, make log_debug never get called at all, and its
28676 arguments never get evaluated, when no debug logs are configured.
28677 (This is showing up in some profiles, but not others.)
28680 - Remove some never-implemented options. Mark PathlenCoinWeight as
28682 - Implement proposal 106: Stop requiring clients to have well-formed
28683 certificates; stop checking nicknames in certificates. (Clients
28684 have certificates so that they can look like Tor servers, but in
28685 the future we might want to allow them to look like regular TLS
28686 clients instead. Nicknames in certificates serve no purpose other
28687 than making our protocol easier to recognize on the wire.)
28688 - Revise messages on handshake failure again to be even more clear about
28689 which are incoming connections and which are outgoing.
28690 - Discard any v1 directory info that's over 1 month old (for
28691 directories) or over 1 week old (for running-routers lists).
28692 - Do not warn when individual nodes in the configuration's EntryNodes,
28693 ExitNodes, etc are down: warn only when all possible nodes
28694 are down. (Fixes bug 348.)
28695 - Always remove expired routers and networkstatus docs before checking
28696 whether we have enough information to build circuits. (Fixes
28698 - Put a lower-bound on MaxAdvertisedBandwidth.
28701 Changes in version 0.1.2.7-alpha - 2007-02-06
28702 o Major bugfixes (rate limiting):
28703 - Servers decline directory requests much more aggressively when
28704 they're low on bandwidth. Otherwise they end up queueing more and
28705 more directory responses, which can't be good for latency.
28706 - But never refuse directory requests from local addresses.
28707 - Fix a memory leak when sending a 503 response for a networkstatus
28709 - Be willing to read or write on local connections (e.g. controller
28710 connections) even when the global rate limiting buckets are empty.
28711 - If our system clock jumps back in time, don't publish a negative
28712 uptime in the descriptor. Also, don't let the global rate limiting
28713 buckets go absurdly negative.
28714 - Flush local controller connection buffers periodically as we're
28715 writing to them, so we avoid queueing 4+ megabytes of data before
28718 o Major bugfixes (NT services):
28719 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
28720 command-line flag so that admins can override the default by saying
28721 "tor --service install --user "SomeUser"". This will not affect
28722 existing installed services. Also, warn the user that the service
28723 will look for its configuration file in the service user's
28724 %appdata% directory. (We can't do the 'hardwire the user's appdata
28725 directory' trick any more, since we may not have read access to that
28728 o Major bugfixes (other):
28729 - Previously, we would cache up to 16 old networkstatus documents
28730 indefinitely, if they came from nontrusted authorities. Now we
28731 discard them if they are more than 10 days old.
28732 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
28734 - Detect and reject malformed DNS responses containing circular
28736 - If exits are rare enough that we're not marking exits as guards,
28737 ignore exit bandwidth when we're deciding the required bandwidth
28739 - When we're handling a directory connection tunneled over Tor,
28740 don't fill up internal memory buffers with all the data we want
28741 to tunnel; instead, only add it if the OR connection that will
28742 eventually receive it has some room for it. (This can lead to
28743 slowdowns in tunneled dir connections; a better solution will have
28744 to wait for 0.2.0.)
28746 o Minor bugfixes (dns):
28747 - Add some defensive programming to eventdns.c in an attempt to catch
28748 possible memory-stomping bugs.
28749 - Detect and reject DNS replies containing IPv4 or IPv6 records with
28750 an incorrect number of bytes. (Previously, we would ignore the
28752 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
28753 in the correct order, and doesn't crash.
28754 - Free memory held in recently-completed DNS lookup attempts on exit.
28755 This was not a memory leak, but may have been hiding memory leaks.
28756 - Handle TTL values correctly on reverse DNS lookups.
28757 - Treat failure to parse resolv.conf as an error.
28759 o Minor bugfixes (other):
28760 - Fix crash with "tor --list-fingerprint" (reported by seeess).
28761 - When computing clock skew from directory HTTP headers, consider what
28762 time it was when we finished asking for the directory, not what
28764 - Expire socks connections if they spend too long waiting for the
28765 handshake to finish. Previously we would let them sit around for
28766 days, if the connecting application didn't close them either.
28767 - And if the socks handshake hasn't started, don't send a
28768 "DNS resolve socks failed" handshake reply; just close it.
28769 - Stop using C functions that OpenBSD's linker doesn't like.
28770 - Don't launch requests for descriptors unless we have networkstatuses
28771 from at least half of the authorities. This delays the first
28772 download slightly under pathological circumstances, but can prevent
28773 us from downloading a bunch of descriptors we don't need.
28774 - Do not log IPs with TLS failures for incoming TLS
28775 connections. (Fixes bug 382.)
28776 - If the user asks to use invalid exit nodes, be willing to use
28778 - Stop using the reserved ac_cv namespace in our configure script.
28779 - Call stat() slightly less often; use fstat() when possible.
28780 - Refactor the way we handle pending circuits when an OR connection
28781 completes or fails, in an attempt to fix a rare crash bug.
28782 - Only rewrite a conn's address based on X-Forwarded-For: headers
28783 if it's a parseable public IP address; and stop adding extra quotes
28784 to the resulting address.
28787 - Weight directory requests by advertised bandwidth. Now we can
28788 let servers enable write limiting but still allow most clients to
28789 succeed at their directory requests. (We still ignore weights when
28790 choosing a directory authority; I hope this is a feature.)
28793 - Create a new file ReleaseNotes which was the old ChangeLog. The
28794 new ChangeLog file now includes the summaries for all development
28796 - Check for addresses with invalid characters at the exit as well
28797 as at the client, and warn less verbosely when they fail. You can
28798 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
28799 - Adapt a patch from goodell to let the contrib/exitlist script
28800 take arguments rather than require direct editing.
28801 - Inform the server operator when we decide not to advertise a
28802 DirPort due to AccountingMax enabled or a low BandwidthRate. It
28803 was confusing Zax, so now we're hopefully more helpful.
28804 - Bring us one step closer to being able to establish an encrypted
28805 directory tunnel without knowing a descriptor first. Still not
28806 ready yet. As part of the change, now assume we can use a
28807 create_fast cell if we don't know anything about a router.
28808 - Allow exit nodes to use nameservers running on ports other than 53.
28809 - Servers now cache reverse DNS replies.
28810 - Add an --ignore-missing-torrc command-line option so that we can
28811 get the "use sensible defaults if the configuration file doesn't
28812 exist" behavior even when specifying a torrc location on the command
28815 o Minor features (controller):
28816 - Track reasons for OR connection failure; make these reasons
28817 available via the controller interface. (Patch from Mike Perry.)
28818 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
28819 can learn when clients are sending malformed hostnames to Tor.
28820 - Clean up documentation for controller status events.
28821 - Add a REMAP status to stream events to note that a stream's
28822 address has changed because of a cached address or a MapAddress
28826 Changes in version 0.1.2.6-alpha - 2007-01-09
28828 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
28829 connection handles more than 4 gigs in either direction, we crash.
28830 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
28831 advertised exit node, somebody might try to exit from us when
28832 we're bootstrapping and before we've built our descriptor yet.
28833 Refuse the connection rather than crashing.
28836 - Warn if we (as a server) find that we've resolved an address that we
28837 weren't planning to resolve.
28838 - Warn that using select() on any libevent version before 1.1 will be
28839 unnecessarily slow (even for select()).
28840 - Flush ERR-level controller status events just like we currently
28841 flush ERR-level log events, so that a Tor shutdown doesn't prevent
28842 the controller from learning about current events.
28844 o Minor features (more controller status events):
28845 - Implement EXTERNAL_ADDRESS server status event so controllers can
28846 learn when our address changes.
28847 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
28848 can learn when directories reject our descriptor.
28849 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
28850 can learn when a client application is speaking a non-socks protocol
28852 - Implement DANGEROUS_SOCKS client status event so controllers
28853 can learn when a client application is leaking DNS addresses.
28854 - Implement BUG general status event so controllers can learn when
28855 Tor is unhappy about its internal invariants.
28856 - Implement CLOCK_SKEW general status event so controllers can learn
28857 when Tor thinks the system clock is set incorrectly.
28858 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
28859 server status events so controllers can learn when their descriptors
28860 are accepted by a directory.
28861 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
28862 server status events so controllers can learn about Tor's progress in
28863 deciding whether it's reachable from the outside.
28864 - Implement BAD_LIBEVENT general status event so controllers can learn
28865 when we have a version/method combination in libevent that needs to
28867 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
28868 and DNS_USELESS server status events so controllers can learn
28869 about changes to DNS server status.
28871 o Minor features (directory):
28872 - Authorities no longer recommend exits as guards if this would shift
28873 too much load to the exit nodes.
28876 Changes in version 0.1.2.5-alpha - 2007-01-06
28878 - Enable write limiting as well as read limiting. Now we sacrifice
28879 capacity if we're pushing out lots of directory traffic, rather
28880 than overrunning the user's intended bandwidth limits.
28881 - Include TLS overhead when counting bandwidth usage; previously, we
28882 would count only the bytes sent over TLS, but not the bytes used
28884 - Support running the Tor service with a torrc not in the same
28885 directory as tor.exe and default to using the torrc located in
28886 the %appdata%\Tor\ of the user who installed the service. Patch
28888 - Servers now check for the case when common DNS requests are going to
28889 wildcarded addresses (i.e. all getting the same answer), and change
28890 their exit policy to reject *:* if it's happening.
28891 - Implement BEGIN_DIR cells, so we can connect to the directory
28892 server via TLS to do encrypted directory requests rather than
28893 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
28894 config options if you like.
28896 o Minor features (config and docs):
28897 - Start using the state file to store bandwidth accounting data:
28898 the bw_accounting file is now obsolete. We'll keep generating it
28899 for a while for people who are still using 0.1.2.4-alpha.
28900 - Try to batch changes to the state file so that we do as few
28901 disk writes as possible while still storing important things in
28903 - The state file and the bw_accounting file get saved less often when
28904 the AvoidDiskWrites config option is set.
28905 - Make PIDFile work on Windows (untested).
28906 - Add internal descriptions for a bunch of configuration options:
28907 accessible via controller interface and in comments in saved
28909 - Reject *:563 (NNTPS) in the default exit policy. We already reject
28910 NNTP by default, so this seems like a sensible addition.
28911 - Clients now reject hostnames with invalid characters. This should
28912 avoid some inadvertent info leaks. Add an option
28913 AllowNonRFC953Hostnames to disable this behavior, in case somebody
28914 is running a private network with hosts called @, !, and #.
28915 - Add a maintainer script to tell us which options are missing
28916 documentation: "make check-docs".
28917 - Add a new address-spec.txt document to describe our special-case
28918 addresses: .exit, .onion, and .noconnnect.
28920 o Minor features (DNS):
28921 - Ongoing work on eventdns infrastructure: now it has dns server
28922 and ipv6 support. One day Tor will make use of it.
28923 - Add client-side caching for reverse DNS lookups.
28924 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
28925 - When we change nameservers or IP addresses, reset and re-launch
28926 our tests for DNS hijacking.
28928 o Minor features (directory):
28929 - Authorities now specify server versions in networkstatus. This adds
28930 about 2% to the size of compressed networkstatus docs, and allows
28931 clients to tell which servers support BEGIN_DIR and which don't.
28932 The implementation is forward-compatible with a proposed future
28933 protocol version scheme not tied to Tor versions.
28934 - DirServer configuration lines now have an orport= option so
28935 clients can open encrypted tunnels to the authorities without
28936 having downloaded their descriptors yet. Enabled for moria1,
28937 moria2, tor26, and lefkada now in the default configuration.
28938 - Directory servers are more willing to send a 503 "busy" if they
28939 are near their write limit, especially for v1 directory requests.
28940 Now they can use their limited bandwidth for actual Tor traffic.
28941 - Clients track responses with status 503 from dirservers. After a
28942 dirserver has given us a 503, we try not to use it until an hour has
28943 gone by, or until we have no dirservers that haven't given us a 503.
28944 - When we get a 503 from a directory, and we're not a server, we don't
28945 count the failure against the total number of failures allowed
28946 for the thing we're trying to download.
28947 - Report X-Your-Address-Is correctly from tunneled directory
28948 connections; don't report X-Your-Address-Is when it's an internal
28949 address; and never believe reported remote addresses when they're
28951 - Protect against an unlikely DoS attack on directory servers.
28952 - Add a BadDirectory flag to network status docs so that authorities
28953 can (eventually) tell clients about caches they believe to be
28956 o Minor features (controller):
28957 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
28958 - Reimplement GETINFO so that info/names stays in sync with the
28960 - Implement "GETINFO fingerprint".
28961 - Implement "SETEVENTS GUARD" so controllers can get updates on
28962 entry guard status as it changes.
28964 o Minor features (clean up obsolete pieces):
28965 - Remove some options that have been deprecated since at least
28966 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
28967 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
28968 to set log options.
28969 - We no longer look for identity and onion keys in "identity.key" and
28970 "onion.key" -- these were replaced by secret_id_key and
28971 secret_onion_key in 0.0.8pre1.
28972 - We no longer require unrecognized directory entries to be
28975 o Major bugfixes (security):
28976 - Stop sending the HttpProxyAuthenticator string to directory
28977 servers when directory connections are tunnelled through Tor.
28978 - Clients no longer store bandwidth history in the state file.
28979 - Do not log introduction points for hidden services if SafeLogging
28981 - When generating bandwidth history, round down to the nearest
28982 1k. When storing accounting data, round up to the nearest 1k.
28983 - When we're running as a server, remember when we last rotated onion
28984 keys, so that we will rotate keys once they're a week old even if
28985 we never stay up for a week ourselves.
28987 o Major bugfixes (other):
28988 - Fix a longstanding bug in eventdns that prevented the count of
28989 timed-out resolves from ever being reset. This bug caused us to
28990 give up on a nameserver the third time it timed out, and try it
28991 10 seconds later... and to give up on it every time it timed out
28993 - Take out the '5 second' timeout from the connection retry
28994 schedule. Now the first connect attempt will wait a full 10
28995 seconds before switching to a new circuit. Perhaps this will help
28996 a lot. Based on observations from Mike Perry.
28997 - Fix a bug on the Windows implementation of tor_mmap_file() that
28998 would prevent the cached-routers file from ever loading. Reported
29002 - Fix an assert failure when a directory authority sets
29003 AuthDirRejectUnlisted and then receives a descriptor from an
29004 unlisted router. Reported by seeess.
29005 - Avoid a double-free when parsing malformed DirServer lines.
29006 - Fix a bug when a BSD-style PF socket is first used. Patch from
29008 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
29009 to resolve an address at a given exit node even when they ask for
29011 - Servers no longer ever list themselves in their "family" line,
29012 even if configured to do so. This makes it easier to configure
29013 family lists conveniently.
29014 - When running as a server, don't fall back to 127.0.0.1 when no
29015 nameservers are configured in /etc/resolv.conf; instead, make the
29016 user fix resolv.conf or specify nameservers explicitly. (Resolves
29018 - Stop accepting certain malformed ports in configured exit policies.
29019 - Don't re-write the fingerprint file every restart, unless it has
29021 - Stop warning when a single nameserver fails: only warn when _all_ of
29022 our nameservers have failed. Also, when we only have one nameserver,
29023 raise the threshold for deciding that the nameserver is dead.
29024 - Directory authorities now only decide that routers are reachable
29025 if their identity keys are as expected.
29026 - When the user uses bad syntax in the Log config line, stop
29027 suggesting other bad syntax as a replacement.
29028 - Correctly detect ipv6 DNS capability on OpenBSD.
29030 o Minor bugfixes (controller):
29031 - Report the circuit number correctly in STREAM CLOSED events. Bug
29032 reported by Mike Perry.
29033 - Do not report bizarre values for results of accounting GETINFOs
29034 when the last second's write or read exceeds the allotted bandwidth.
29035 - Report "unrecognized key" rather than an empty string when the
29036 controller tries to fetch a networkstatus that doesn't exist.
29039 Changes in version 0.1.1.26 - 2006-12-14
29040 o Security bugfixes:
29041 - Stop sending the HttpProxyAuthenticator string to directory
29042 servers when directory connections are tunnelled through Tor.
29043 - Clients no longer store bandwidth history in the state file.
29044 - Do not log introduction points for hidden services if SafeLogging
29048 - Fix an assert failure when a directory authority sets
29049 AuthDirRejectUnlisted and then receives a descriptor from an
29050 unlisted router (reported by seeess).
29053 Changes in version 0.1.2.4-alpha - 2006-12-03
29055 - Add support for using natd; this allows FreeBSDs earlier than
29056 5.1.2 to have ipfw send connections through Tor without using
29057 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
29060 - Make all connections to addresses of the form ".noconnect"
29061 immediately get closed. This lets application/controller combos
29062 successfully test whether they're talking to the same Tor by
29063 watching for STREAM events.
29064 - Make cross.sh cross-compilation script work even when autogen.sh
29065 hasn't been run. (Patch from Michael Mohr.)
29066 - Statistics dumped by -USR2 now include a breakdown of public key
29067 operations, for profiling.
29070 - Fix a major leak when directory authorities parse their
29071 approved-routers list, a minor memory leak when we fail to pick
29072 an exit node, and a few rare leaks on errors.
29073 - Handle TransPort connections even when the server sends data before
29074 the client sends data. Previously, the connection would just hang
29075 until the client sent data. (Patch from tup based on patch from
29077 - Avoid assert failure when our cached-routers file is empty on
29081 - Don't log spurious warnings when we see a circuit close reason we
29082 don't recognize; it's probably just from a newer version of Tor.
29083 - Have directory authorities allow larger amounts of drift in uptime
29084 without replacing the server descriptor: previously, a server that
29085 restarted every 30 minutes could have 48 "interesting" descriptors
29087 - Start linking to the Tor specification and Tor reference manual
29088 correctly in the Windows installer.
29089 - Add Vidalia to the OS X uninstaller script, so when we uninstall
29090 Tor/Privoxy we also uninstall Vidalia.
29091 - Resume building on Irix64, and fix a lot of warnings from its
29092 MIPSpro C compiler.
29093 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
29094 when we're running as a client.
29097 Changes in version 0.1.1.25 - 2006-11-04
29099 - When a client asks us to resolve (rather than connect to)
29100 an address, and we have a cached answer, give them the cached
29101 answer. Previously, we would give them no answer at all.
29102 - We were building exactly the wrong circuits when we predict
29103 hidden service requirements, meaning Tor would have to build all
29104 its circuits on demand.
29105 - If none of our live entry guards have a high uptime, but we
29106 require a guard with a high uptime, try adding a new guard before
29107 we give up on the requirement. This patch should make long-lived
29108 connections more stable on average.
29109 - When testing reachability of our DirPort, don't launch new
29110 tests when there's already one in progress -- unreachable
29111 servers were stacking up dozens of testing streams.
29113 o Security bugfixes:
29114 - When the user sends a NEWNYM signal, clear the client-side DNS
29115 cache too. Otherwise we continue to act on previous information.
29118 - Avoid a memory corruption bug when creating a hash table for
29120 - Avoid possibility of controller-triggered crash when misusing
29121 certain commands from a v0 controller on platforms that do not
29122 handle printf("%s",NULL) gracefully.
29123 - Avoid infinite loop on unexpected controller input.
29124 - Don't log spurious warnings when we see a circuit close reason we
29125 don't recognize; it's probably just from a newer version of Tor.
29126 - Add Vidalia to the OS X uninstaller script, so when we uninstall
29127 Tor/Privoxy we also uninstall Vidalia.
29130 Changes in version 0.1.2.3-alpha - 2006-10-29
29132 - Prepare for servers to publish descriptors less often: never
29133 discard a descriptor simply for being too old until either it is
29134 recommended by no authorities, or until we get a better one for
29135 the same router. Make caches consider retaining old recommended
29136 routers for even longer.
29137 - If most authorities set a BadExit flag for a server, clients
29138 don't think of it as a general-purpose exit. Clients only consider
29139 authorities that advertise themselves as listing bad exits.
29140 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
29141 headers for content, so that we can work better in the presence of
29142 caching HTTP proxies.
29143 - Allow authorities to list nodes as bad exits by fingerprint or by
29146 o Minor features, controller:
29147 - Add a REASON field to CIRC events; for backward compatibility, this
29148 field is sent only to controllers that have enabled the extended
29149 event format. Also, add additional reason codes to explain why
29150 a given circuit has been destroyed or truncated. (Patches from
29152 - Add a REMOTE_REASON field to extended CIRC events to tell the
29153 controller about why a remote OR told us to close a circuit.
29154 - Stream events also now have REASON and REMOTE_REASON fields,
29155 working much like those for circuit events.
29156 - There's now a GETINFO ns/... field so that controllers can ask Tor
29157 about the current status of a router.
29158 - A new event type "NS" to inform a controller when our opinion of
29159 a router's status has changed.
29160 - Add a GETINFO events/names and GETINFO features/names so controllers
29161 can tell which events and features are supported.
29162 - A new CLEARDNSCACHE signal to allow controllers to clear the
29163 client-side DNS cache without expiring circuits.
29165 o Security bugfixes:
29166 - When the user sends a NEWNYM signal, clear the client-side DNS
29167 cache too. Otherwise we continue to act on previous information.
29170 - Avoid sending junk to controllers or segfaulting when a controller
29171 uses EVENT_NEW_DESC with verbose nicknames.
29172 - Stop triggering asserts if the controller tries to extend hidden
29173 service circuits (reported by mwenge).
29174 - Avoid infinite loop on unexpected controller input.
29175 - When the controller does a "GETINFO network-status", tell it
29176 about even those routers whose descriptors are very old, and use
29177 long nicknames where appropriate.
29178 - Change NT service functions to be loaded on demand. This lets us
29179 build with MinGW without breaking Tor for Windows 98 users.
29180 - Do DirPort reachability tests less often, since a single test
29181 chews through many circuits before giving up.
29182 - In the hidden service example in torrc.sample, stop recommending
29183 esoteric and discouraged hidden service options.
29184 - When stopping an NT service, wait up to 10 sec for it to actually
29185 stop. Patch from Matt Edman; resolves bug 295.
29186 - Fix handling of verbose nicknames with ORCONN controller events:
29187 make them show up exactly when requested, rather than exactly when
29189 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
29190 printing a duplicate "$" in the keys we send (reported by mwenge).
29191 - Correctly set maximum connection limit on Cygwin. (This time
29193 - Try to detect Windows correctly when cross-compiling.
29194 - Detect the size of the routers file correctly even if it is
29195 corrupted (on systems without mmap) or not page-aligned (on systems
29196 with mmap). This bug was harmless.
29197 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
29198 to open a stream fails; now we do in more cases. This should
29199 make clients able to find a good exit faster in some cases, since
29200 unhandleable requests will now get an error rather than timing out.
29201 - Resolve two memory leaks when rebuilding the on-disk router cache
29202 (reported by fookoowa).
29203 - Clean up minor code warnings suggested by the MIPSpro C compiler,
29204 and reported by some Centos users.
29205 - Controller signals now work on non-Unix platforms that don't define
29206 SIGUSR1 and SIGUSR2 the way we expect.
29207 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
29208 values before failing, and always enables eventdns.
29209 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
29210 Try to fix this in configure.in by checking for most functions
29211 before we check for libevent.
29214 Changes in version 0.1.2.2-alpha - 2006-10-07
29216 - Make our async eventdns library on-by-default for Tor servers,
29217 and plan to deprecate the separate dnsworker threads.
29218 - Add server-side support for "reverse" DNS lookups (using PTR
29219 records so clients can determine the canonical hostname for a given
29220 IPv4 address). Only supported by servers using eventdns; servers
29221 now announce in their descriptors whether they support eventdns.
29222 - Specify and implement client-side SOCKS5 interface for reverse DNS
29223 lookups (see doc/socks-extensions.txt).
29224 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
29225 connect to directory servers through Tor. Previously, clients needed
29226 to find Tor exits to make private connections to directory servers.
29227 - Avoid choosing Exit nodes for entry or middle hops when the
29228 total bandwidth available from non-Exit nodes is much higher than
29229 the total bandwidth available from Exit nodes.
29230 - Workaround for name servers (like Earthlink's) that hijack failing
29231 DNS requests and replace the no-such-server answer with a "helpful"
29232 redirect to an advertising-driven search portal. Also work around
29233 DNS hijackers who "helpfully" decline to hijack known-invalid
29234 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
29235 lets you turn it off.
29236 - Send out a burst of long-range padding cells once we've established
29237 that we're reachable. Spread them over 4 circuits, so hopefully
29238 a few will be fast. This exercises our bandwidth and bootstraps
29239 us into the directory more quickly.
29241 o New/improved config options:
29242 - Add new config option "ResolvConf" to let the server operator
29243 choose an alternate resolve.conf file when using eventdns.
29244 - Add an "EnforceDistinctSubnets" option to control our "exclude
29245 servers on the same /16" behavior. It's still on by default; this
29246 is mostly for people who want to operate private test networks with
29247 all the machines on the same subnet.
29248 - If one of our entry guards is on the ExcludeNodes list, or the
29249 directory authorities don't think it's a good guard, treat it as
29250 if it were unlisted: stop using it as a guard, and throw it off
29251 the guards list if it stays that way for a long time.
29252 - Allow directory authorities to be marked separately as authorities
29253 for the v1 directory protocol, the v2 directory protocol, and
29254 as hidden service directories, to make it easier to retire old
29255 authorities. V1 authorities should set "HSAuthoritativeDir 1"
29256 to continue being hidden service authorities too.
29257 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
29259 o Minor features, controller:
29260 - Fix CIRC controller events so that controllers can learn the
29261 identity digests of non-Named servers used in circuit paths.
29262 - Let controllers ask for more useful identifiers for servers. Instead
29263 of learning identity digests for un-Named servers and nicknames
29264 for Named servers, the new identifiers include digest, nickname,
29265 and indication of Named status. Off by default; see control-spec.txt
29266 for more information.
29267 - Add a "getinfo address" controller command so it can display Tor's
29268 best guess to the user.
29269 - New controller event to alert the controller when our server
29270 descriptor has changed.
29271 - Give more meaningful errors on controller authentication failure.
29273 o Minor features, other:
29274 - When asked to resolve a hostname, don't use non-exit servers unless
29275 requested to do so. This allows servers with broken DNS to be
29276 useful to the network.
29277 - Divide eventdns log messages into warn and info messages.
29278 - Reserve the nickname "Unnamed" for routers that can't pick
29279 a hostname: any router can call itself Unnamed; directory
29280 authorities will never allocate Unnamed to any particular router;
29281 clients won't believe that any router is the canonical Unnamed.
29282 - Only include function names in log messages for info/debug messages.
29283 For notice/warn/err, the content of the message should be clear on
29284 its own, and printing the function name only confuses users.
29285 - Avoid some false positives during reachability testing: don't try
29286 to test via a server that's on the same /24 as us.
29287 - If we fail to build a circuit to an intended enclave, and it's
29288 not mandatory that we use that enclave, stop wanting it.
29289 - When eventdns is enabled, allow multithreaded builds on NetBSD and
29290 OpenBSD. (We had previously disabled threads on these platforms
29291 because they didn't have working thread-safe resolver functions.)
29293 o Major bugfixes, anonymity/security:
29294 - If a client asked for a server by name, and there's a named server
29295 in our network-status but we don't have its descriptor yet, we
29296 could return an unnamed server instead.
29297 - Fix NetBSD bug that could allow someone to force uninitialized RAM
29298 to be sent to a server's DNS resolver. This only affects NetBSD
29299 and other platforms that do not bounds-check tolower().
29300 - Reject (most) attempts to use Tor circuits with length one. (If
29301 many people start using Tor as a one-hop proxy, exit nodes become
29302 a more attractive target for compromise.)
29303 - Just because your DirPort is open doesn't mean people should be
29304 able to remotely teach you about hidden service descriptors. Now
29305 only accept rendezvous posts if you've got HSAuthoritativeDir set.
29307 o Major bugfixes, other:
29308 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
29309 - When a client asks the server to resolve (not connect to)
29310 an address, and it has a cached answer, give them the cached answer.
29311 Previously, the server would give them no answer at all.
29312 - Allow really slow clients to not hang up five minutes into their
29313 directory downloads (suggested by Adam J. Richter).
29314 - We were building exactly the wrong circuits when we anticipated
29315 hidden service requirements, meaning Tor would have to build all
29316 its circuits on demand.
29317 - Avoid crashing when we mmap a router cache file of size 0.
29318 - When testing reachability of our DirPort, don't launch new
29319 tests when there's already one in progress -- unreachable
29320 servers were stacking up dozens of testing streams.
29322 o Minor bugfixes, correctness:
29323 - If we're a directory mirror and we ask for "all" network status
29324 documents, we would discard status documents from authorities
29325 we don't recognize.
29326 - Avoid a memory corruption bug when creating a hash table for
29328 - Avoid controller-triggered crash when misusing certain commands
29329 from a v0 controller on platforms that do not handle
29330 printf("%s",NULL) gracefully.
29331 - Don't crash when a controller sends a third argument to an
29332 "extendcircuit" request.
29333 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29334 response; fix error code when "getinfo dir/status/" fails.
29335 - Avoid crash when telling controller stream-status and a stream
29337 - Patch from Adam Langley to fix assert() in eventdns.c.
29338 - Fix a debug log message in eventdns to say "X resolved to Y"
29339 instead of "X resolved to X".
29340 - Make eventdns give strings for DNS errors, not just error numbers.
29341 - Track unreachable entry guards correctly: don't conflate
29342 'unreachable by us right now' with 'listed as down by the directory
29343 authorities'. With the old code, if a guard was unreachable by
29344 us but listed as running, it would clog our guard list forever.
29345 - Behave correctly in case we ever have a network with more than
29346 2GB/s total advertised capacity.
29347 - Make TrackExitHosts case-insensitive, and fix the behavior of
29348 ".suffix" TrackExitHosts items to avoid matching in the middle of
29350 - Finally fix the openssl warnings from newer gccs that believe that
29351 ignoring a return value is okay, but casting a return value and
29352 then ignoring it is a sign of madness.
29353 - Prevent the contrib/exitlist script from printing the same
29354 result more than once.
29355 - Patch from Steve Hildrey: Generate network status correctly on
29356 non-versioning dirservers.
29357 - Don't listen to the X-Your-Address-Is hint if you did the lookup
29358 via Tor; otherwise you'll think you're the exit node's IP address.
29360 o Minor bugfixes, performance:
29361 - Two small performance improvements on parsing descriptors.
29362 - Major performance improvement on inserting descriptors: change
29363 algorithm from O(n^2) to O(n).
29364 - Make the common memory allocation path faster on machines where
29365 malloc(0) returns a pointer.
29366 - Start remembering X-Your-Address-Is directory hints even if you're
29367 a client, so you can become a server more smoothly.
29368 - Avoid duplicate entries on MyFamily line in server descriptor.
29370 o Packaging, features:
29371 - Remove architecture from OS X builds. The official builds are
29372 now universal binaries.
29373 - The Debian package now uses --verify-config when (re)starting,
29374 to distinguish configuration errors from other errors.
29375 - Update RPMs to require libevent 1.1b.
29377 o Packaging, bugfixes:
29378 - Patches so Tor builds with MinGW on Windows.
29379 - Patches so Tor might run on Cygwin again.
29380 - Resume building on non-gcc compilers and ancient gcc. Resume
29381 building with the -O0 compile flag. Resume building cleanly on
29383 - Run correctly on OS X platforms with case-sensitive filesystems.
29384 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
29385 - Add autoconf checks so Tor can build on Solaris x86 again.
29388 - Documented (and renamed) ServerDNSSearchDomains and
29389 ServerDNSResolvConfFile options.
29390 - Be clearer that the *ListenAddress directives can be repeated
29394 Changes in version 0.1.1.24 - 2006-09-29
29396 - Allow really slow clients to not hang up five minutes into their
29397 directory downloads (suggested by Adam J. Richter).
29398 - Fix major performance regression from 0.1.0.x: instead of checking
29399 whether we have enough directory information every time we want to
29400 do something, only check when the directory information has changed.
29401 This should improve client CPU usage by 25-50%.
29402 - Don't crash if, after a server has been running for a while,
29403 it can't resolve its hostname.
29406 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29407 - Don't crash when the controller receives a third argument to an
29408 "extendcircuit" request.
29409 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
29410 response; fix error code when "getinfo dir/status/" fails.
29411 - Fix configure.in to not produce broken configure files with
29412 more recent versions of autoconf. Thanks to Clint for his auto*
29414 - Fix security bug on NetBSD that could allow someone to force
29415 uninitialized RAM to be sent to a server's DNS resolver. This
29416 only affects NetBSD and other platforms that do not bounds-check
29418 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
29419 methods: these are known to be buggy.
29420 - If we're a directory mirror and we ask for "all" network status
29421 documents, we would discard status documents from authorities
29422 we don't recognize.
29425 Changes in version 0.1.2.1-alpha - 2006-08-27
29427 - Add "eventdns" async dns library from Adam Langley, tweaked to
29428 build on OSX and Windows. Only enabled if you pass the
29429 --enable-eventdns argument to configure.
29430 - Allow servers with no hostname or IP address to learn their
29431 IP address by asking the directory authorities. This code only
29432 kicks in when you would normally have exited with a "no address"
29433 error. Nothing's authenticated, so use with care.
29434 - Rather than waiting a fixed amount of time between retrying
29435 application connections, we wait only 5 seconds for the first,
29436 10 seconds for the second, and 15 seconds for each retry after
29437 that. Hopefully this will improve the expected user experience.
29438 - Patch from Tup to add support for transparent AP connections:
29439 this basically bundles the functionality of trans-proxy-tor
29440 into the Tor mainline. Now hosts with compliant pf/netfilter
29441 implementations can redirect TCP connections straight to Tor
29442 without diverting through SOCKS. Needs docs.
29443 - Busy directory servers save lots of memory by spooling server
29444 descriptors, v1 directories, and v2 networkstatus docs to buffers
29445 as needed rather than en masse. Also mmap the cached-routers
29446 files, so we don't need to keep the whole thing in memory too.
29447 - Automatically avoid picking more than one node from the same
29448 /16 network when constructing a circuit.
29449 - Revise and clean up the torrc.sample that we ship with; add
29450 a section for BandwidthRate and BandwidthBurst.
29453 - Split circuit_t into origin_circuit_t and or_circuit_t, and
29454 split connection_t into edge, or, dir, control, and base structs.
29455 These will save quite a bit of memory on busy servers, and they'll
29456 also help us track down bugs in the code and bugs in the spec.
29457 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
29458 or later. Log when we are doing this, so we can diagnose it when
29459 it fails. (Also, recommend libevent 1.1b for kqueue and
29460 win32 methods; deprecate libevent 1.0b harder; make libevent
29461 recommendation system saner.)
29462 - Start being able to build universal binaries on OS X (thanks
29464 - Export the default exit policy via the control port, so controllers
29465 don't need to guess what it is / will be later.
29466 - Add a man page entry for ProtocolWarnings.
29467 - Add TestVia config option to the man page.
29468 - Remove even more protocol-related warnings from Tor server logs,
29469 such as bad TLS handshakes and malformed begin cells.
29470 - Stop fetching descriptors if you're not a dir mirror and you
29471 haven't tried to establish any circuits lately. [This currently
29472 causes some dangerous behavior, because when you start up again
29473 you'll use your ancient server descriptors.]
29474 - New DirPort behavior: if you have your dirport set, you download
29475 descriptors aggressively like a directory mirror, whether or not
29476 your ORPort is set.
29477 - Get rid of the router_retry_connections notion. Now routers
29478 no longer try to rebuild long-term connections to directory
29479 authorities, and directory authorities no longer try to rebuild
29480 long-term connections to all servers. We still don't hang up
29481 connections in these two cases though -- we need to look at it
29482 more carefully to avoid flapping, and we likely need to wait til
29483 0.1.1.x is obsolete.
29484 - Drop compatibility with obsolete Tors that permit create cells
29485 to have the wrong circ_id_type.
29486 - Re-enable per-connection rate limiting. Get rid of the "OP
29487 bandwidth" concept. Lay groundwork for "bandwidth classes" --
29488 separate global buckets that apply depending on what sort of conn
29490 - Start publishing one minute or so after we find our ORPort
29491 to be reachable. This will help reduce the number of descriptors
29492 we have for ourselves floating around, since it's quite likely
29493 other things (e.g. DirPort) will change during that minute too.
29494 - Fork the v1 directory protocol into its own spec document,
29495 and mark dir-spec.txt as the currently correct (v2) spec.
29498 - When we find our DirPort to be reachable, publish a new descriptor
29499 so we'll tell the world (reported by pnx).
29500 - Publish a new descriptor after we hup/reload. This is important
29501 if our config has changed such that we'll want to start advertising
29502 our DirPort now, etc.
29503 - Allow Tor to start when RunAsDaemon is set but no logs are set.
29504 - When we have a state file we cannot parse, tell the user and
29505 move it aside. Now we avoid situations where the user starts
29506 Tor in 1904, Tor writes a state file with that timestamp in it,
29507 the user fixes her clock, and Tor refuses to start.
29508 - Fix configure.in to not produce broken configure files with
29509 more recent versions of autoconf. Thanks to Clint for his auto*
29511 - "tor --verify-config" now exits with -1(255) or 0 depending on
29512 whether the config options are bad or good.
29513 - Resolve bug 321 when using dnsworkers: append a period to every
29514 address we resolve at the exit node, so that we do not accidentally
29515 pick up local addresses, and so that failing searches are retried
29516 in the resolver search domains. (This is already solved for
29517 eventdns.) (This breaks Blossom servers for now.)
29518 - If we are using an exit enclave and we can't connect, e.g. because
29519 its webserver is misconfigured to not listen on localhost, then
29520 back off and try connecting from somewhere else before we fail.
29523 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
29524 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
29525 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
29526 when the IP address is mapped through MapAddress to a hostname.
29527 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
29528 useless IPv6 DNS resolves.
29529 - Patch suggested by Karsten Loesing: respond to SIGNAL command
29530 before we execute the signal, in case the signal shuts us down.
29531 - Clean up AllowInvalidNodes man page entry.
29532 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
29533 - Add more asserts to track down an assert error on a windows Tor
29534 server with connection_add being called with socket == -1.
29535 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
29536 - Fix misleading log messages: an entry guard that is "unlisted",
29537 as well as not known to be "down" (because we've never heard
29538 of it), is not therefore "up".
29539 - Remove code to special-case "-cvs" ending, since it has not
29540 actually mattered since 0.0.9.
29541 - Make our socks5 handling more robust to broken socks clients:
29542 throw out everything waiting on the buffer in between socks
29543 handshake phases, since they can't possibly (so the theory
29544 goes) have predicted what we plan to respond to them.
29547 Changes in version 0.1.1.23 - 2006-07-30
29549 - Fast Tor servers, especially exit nodes, were triggering asserts
29550 due to a bug in handling the list of pending DNS resolves. Some
29551 bugs still remain here; we're hunting them.
29552 - Entry guards could crash clients by sending unexpected input.
29553 - More fixes on reachability testing: if you find yourself reachable,
29554 then don't ever make any client requests (so you stop predicting
29555 circuits), then hup or have your clock jump, then later your IP
29556 changes, you won't think circuits are working, so you won't try to
29557 test reachability, so you won't publish.
29560 - Avoid a crash if the controller does a resetconf firewallports
29561 and then a setconf fascistfirewall=1.
29562 - Avoid an integer underflow when the dir authority decides whether
29563 a router is stable: we might wrongly label it stable, and compute
29564 a slightly wrong median stability, when a descriptor is published
29566 - Fix a place where we might trigger an assert if we can't build our
29567 own server descriptor yet.
29570 Changes in version 0.1.1.22 - 2006-07-05
29572 - Fix a big bug that was causing servers to not find themselves
29573 reachable if they changed IP addresses. Since only 0.1.1.22+
29574 servers can do reachability testing correctly, now we automatically
29575 make sure to test via one of these.
29576 - Fix to allow clients and mirrors to learn directory info from
29577 descriptor downloads that get cut off partway through.
29578 - Directory authorities had a bug in deciding if a newly published
29579 descriptor was novel enough to make everybody want a copy -- a few
29580 servers seem to be publishing new descriptors many times a minute.
29582 - Fix a rare bug that was causing some servers to complain about
29583 "closing wedged cpuworkers" and skip some circuit create requests.
29584 - Make the Exit flag in directory status documents actually work.
29587 Changes in version 0.1.1.21 - 2006-06-10
29588 o Crash and assert fixes from 0.1.1.20:
29589 - Fix a rare crash on Tor servers that have enabled hibernation.
29590 - Fix a seg fault on startup for Tor networks that use only one
29591 directory authority.
29592 - Fix an assert from a race condition that occurs on Tor servers
29593 while exiting, where various threads are trying to log that they're
29594 exiting, and delete the logs, at the same time.
29595 - Make our unit tests pass again on certain obscure platforms.
29598 - Add support for building SUSE RPM packages.
29599 - Speed up initial bootstrapping for clients: if we are making our
29600 first ever connection to any entry guard, then don't mark it down
29602 - When only one Tor server in the network is labelled as a guard,
29603 and we've already picked him, we would cycle endlessly picking him
29604 again, being unhappy about it, etc. Now we specifically exclude
29605 current guards when picking a new guard.
29606 - Servers send create cells more reliably after the TLS connection
29607 is established: we were sometimes forgetting to send half of them
29608 when we had more than one pending.
29609 - If we get a create cell that asks us to extend somewhere, but the
29610 Tor server there doesn't match the expected digest, we now send
29611 a destroy cell back, rather than silently doing nothing.
29612 - Make options->RedirectExit work again.
29613 - Make cookie authentication for the controller work again.
29614 - Stop being picky about unusual characters in the arguments to
29615 mapaddress. It's none of our business.
29616 - Add a new config option "TestVia" that lets you specify preferred
29617 middle hops to use for test circuits. Perhaps this will let me
29618 debug the reachability problems better.
29620 o Log / documentation fixes:
29621 - If we're a server and some peer has a broken TLS certificate, don't
29622 log about it unless ProtocolWarnings is set, i.e., we want to hear
29623 about protocol violations by others.
29624 - Fix spelling of VirtualAddrNetwork in man page.
29625 - Add a better explanation at the top of the autogenerated torrc file
29626 about what happened to our old torrc.
29629 Changes in version 0.1.1.20 - 2006-05-23
29631 - Downgrade a log severity where servers complain that they're
29633 - Avoid a compile warning on FreeBSD.
29634 - Remove string size limit on NEWDESC messages; solve bug 291.
29635 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
29636 more thoroughly when we're running on windows.
29639 Changes in version 0.1.1.19-rc - 2006-05-03
29641 - Regenerate our local descriptor if it's dirty and we try to use
29642 it locally (e.g. if it changes during reachability detection).
29643 - If we setconf our ORPort to 0, we continued to listen on the
29644 old ORPort and receive connections.
29645 - Avoid a second warning about machine/limits.h on Debian
29647 - Be willing to add our own routerinfo into the routerlist.
29648 Now authorities will include themselves in their directories
29649 and network-statuses.
29650 - Stop trying to upload rendezvous descriptors to every
29651 directory authority: only try the v1 authorities.
29652 - Servers no longer complain when they think they're not
29653 registered with the directory authorities. There were too many
29655 - Backport dist-rpm changes so rpms can be built without errors.
29658 - Implement an option, VirtualAddrMask, to set which addresses
29659 get handed out in response to mapaddress requests. This works
29660 around a bug in tsocks where 127.0.0.0/8 is never socksified.
29663 Changes in version 0.1.1.18-rc - 2006-04-10
29665 - Work harder to download live network-statuses from all the
29666 directory authorities we know about. Improve the threshold
29667 decision logic so we're more robust to edge cases.
29668 - When fetching rendezvous descriptors, we were willing to ask
29669 v2 authorities too, which would always return 404.
29672 - Stop listing down or invalid nodes in the v1 directory. This will
29673 reduce its bulk by about 1/3, and reduce load on directory
29675 - When deciding whether a router is Fast or Guard-worthy, consider
29676 his advertised BandwidthRate and not just the BandwidthCapacity.
29677 - No longer ship INSTALL and README files -- they are useless now.
29678 - Force rpmbuild to behave and honor target_cpu.
29679 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
29680 - Start to include translated versions of the tor-doc-*.html
29681 files, along with the screenshots. Still needs more work.
29682 - Start sending back 512 and 451 errors if mapaddress fails,
29683 rather than not sending anything back at all.
29684 - When we fail to bind or listen on an incoming or outgoing
29685 socket, we should close it before failing. otherwise we just
29686 leak it. (thanks to weasel for finding.)
29687 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
29688 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
29689 - Make NoPublish (even though deprecated) work again.
29690 - Fix a minor security flaw where a versioning auth dirserver
29691 could list a recommended version many times in a row to make
29692 clients more convinced that it's recommended.
29693 - Fix crash bug if there are two unregistered servers running
29694 with the same nickname, one of them is down, and you ask for
29695 them by nickname in your EntryNodes or ExitNodes. Also, try
29696 to pick the one that's running rather than an arbitrary one.
29697 - Fix an infinite loop we could hit if we go offline for too long.
29698 - Complain when we hit WSAENOBUFS on recv() or write() too.
29699 Perhaps this will help us hunt the bug.
29700 - If you're not a versioning dirserver, don't put the string
29701 "client-versions \nserver-versions \n" in your network-status.
29702 - Lower the minimum required number of file descriptors to 1000,
29703 so we can have some overhead for Valgrind on Linux, where the
29704 default ulimit -n is 1024.
29707 - Add tor.dizum.com as the fifth authoritative directory server.
29708 - Add a new config option FetchUselessDescriptors, off by default,
29709 for when you plan to run "exitlist" on your client and you want
29710 to know about even the non-running descriptors.
29713 Changes in version 0.1.1.17-rc - 2006-03-28
29715 - Clients and servers since 0.1.1.10-alpha have been expiring
29716 connections whenever they are idle for 5 minutes and they *do*
29717 have circuits on them. Oops. With this new version, clients will
29718 discard their previous entry guard choices and avoid choosing
29719 entry guards running these flawed versions.
29720 - Fix memory leak when uncompressing concatenated zlib streams. This
29721 was causing substantial leaks over time on Tor servers.
29722 - The v1 directory was including servers as much as 48 hours old,
29723 because that's how the new routerlist->routers works. Now only
29724 include them if they're 20 hours old or less.
29727 - Resume building on irix64, netbsd 2.0, etc.
29728 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
29730 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
29731 and it is confusing some users.
29732 - Mirrors stop caching the v1 directory so often.
29733 - Make the max number of old descriptors that a cache will hold
29734 rise with the number of directory authorities, so we can scale.
29735 - Change our win32 uname() hack to be more forgiving about what
29736 win32 versions it thinks it's found.
29739 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
29741 - When the controller's *setconf commands fail, collect an error
29742 message in a string and hand it back to the controller.
29743 - Make the v2 dir's "Fast" flag based on relative capacity, just
29744 like "Stable" is based on median uptime. Name everything in the
29745 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
29746 - Log server fingerprint on startup, so new server operators don't
29747 have to go hunting around their filesystem for it.
29748 - Return a robots.txt on our dirport to discourage google indexing.
29749 - Let the controller ask for GETINFO dir/status/foo so it can ask
29750 directly rather than connecting to the dir port. Only works when
29751 dirport is set for now.
29753 o New config options rather than constants in the code:
29754 - SocksTimeout: How long do we let a socks connection wait
29755 unattached before we fail it?
29756 - CircuitBuildTimeout: Cull non-open circuits that were born
29757 at least this many seconds ago.
29758 - CircuitIdleTimeout: Cull open clean circuits that were born
29759 at least this many seconds ago.
29762 Changes in version 0.1.1.16-rc - 2006-03-18
29763 o Bugfixes on 0.1.1.15-rc:
29764 - Fix assert when the controller asks to attachstream a connect-wait
29765 or resolve-wait stream.
29766 - Now do address rewriting when the controller asks us to attach
29767 to a particular circuit too. This will let Blossom specify
29768 "moria2.exit" without having to learn what moria2's IP address is.
29769 - Make the "tor --verify-config" command-line work again, so people
29770 can automatically check if their torrc will parse.
29771 - Authoritative dirservers no longer require an open connection from
29772 a server to consider him "reachable". We need this change because
29773 when we add new auth dirservers, old servers won't know not to
29775 - Let Tor build on Sun CC again.
29776 - Fix an off-by-one buffer size in dirserv.c that magically never
29777 hit our three authorities but broke sjmurdoch's own tor network.
29778 - If we as a directory mirror don't know of any v1 directory
29779 authorities, then don't try to cache any v1 directories.
29780 - Stop warning about unknown servers in our family when they are
29781 given as hex digests.
29782 - Stop complaining as quickly to the server operator that he
29783 hasn't registered his nickname/key binding.
29784 - Various cleanups so we can add new V2 Auth Dirservers.
29785 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
29786 reflect the updated flags in our v2 dir protocol.
29787 - Resume allowing non-printable characters for exit streams (both
29788 for connecting and for resolving). Now we tolerate applications
29789 that don't follow the RFCs. But continue to block malformed names
29792 o Bugfixes on 0.1.0.x:
29793 - Fix assert bug in close_logs(): when we close and delete logs,
29794 remove them all from the global "logfiles" list.
29795 - Fix minor integer overflow in calculating when we expect to use up
29796 our bandwidth allocation before hibernating.
29797 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
29798 there are multiple SSLs installed with different versions.
29799 - When we try to be a server and Address is not explicitly set and
29800 our hostname resolves to a private IP address, try to use an
29801 interface address if it has a public address. Now Windows machines
29802 that think of themselves as localhost can work by default.
29805 - Let the controller ask for GETINFO dir/server/foo so it can ask
29806 directly rather than connecting to the dir port.
29807 - Let the controller tell us about certain router descriptors
29808 that it doesn't want Tor to use in circuits. Implement
29809 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
29810 - New config option SafeSocks to reject all application connections
29811 using unsafe socks protocols. Defaults to off.
29814 Changes in version 0.1.1.15-rc - 2006-03-11
29815 o Bugfixes and cleanups:
29816 - When we're printing strings from the network, don't try to print
29817 non-printable characters. This protects us against shell escape
29818 sequence exploits, and also against attacks to fool humans into
29819 misreading their logs.
29820 - Fix a bug where Tor would fail to establish any connections if you
29821 left it off for 24 hours and then started it: we were happy with
29822 the obsolete network statuses, but they all referred to router
29823 descriptors that were too old to fetch, so we ended up with no
29824 valid router descriptors.
29825 - Fix a seg fault in the controller's "getinfo orconn-status"
29826 command while listing status on incoming handshaking connections.
29827 Introduce a status name "NEW" for these connections.
29828 - If we get a linelist or linelist_s config option from the torrc
29829 (e.g. ExitPolicy) and it has no value, warn and skip rather than
29830 silently resetting it to its default.
29831 - Don't abandon entry guards until they've been down or gone for
29833 - Cleaner and quieter log messages.
29836 - New controller signal NEWNYM that makes new application requests
29837 use clean circuits.
29838 - Add a new circuit purpose 'controller' to let the controller ask
29839 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
29840 controller command to let you specify the purpose if you're
29841 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
29842 command to let you change a circuit's purpose after it's been
29844 - Accept "private:*" in routerdesc exit policies; not generated yet
29845 because older Tors do not understand it.
29846 - Add BSD-style contributed startup script "rc.subr" from Peter
29850 Changes in version 0.1.1.14-alpha - 2006-02-20
29851 o Bugfixes on 0.1.1.x:
29852 - Don't die if we ask for a stdout or stderr log (even implicitly)
29853 and we're set to RunAsDaemon -- just warn.
29854 - We still had a few bugs in the OR connection rotation code that
29855 caused directory servers to slowly aggregate connections to other
29856 fast Tor servers. This time for sure!
29857 - Make log entries on Win32 include the name of the function again.
29858 - We were treating a pair of exit policies if they were equal even
29859 if one said accept and the other said reject -- causing us to
29860 not always publish a new descriptor since we thought nothing
29862 - Retry pending server downloads as well as pending networkstatus
29863 downloads when we unexpectedly get a socks request.
29864 - We were ignoring the IS_FAST flag in the directory status,
29865 meaning we were willing to pick trivial-bandwidth nodes for "fast"
29867 - If the controller's SAVECONF command fails (e.g. due to file
29868 permissions), let the controller know that it failed.
29871 - If we're trying to be a Tor server and running Windows 95/98/ME
29872 as a server, explain that we'll likely crash.
29873 - When we're a server, a client asks for an old-style directory,
29874 and our write bucket is empty, don't give it to him. This way
29875 small servers can continue to serve the directory *sometimes*,
29876 without getting overloaded.
29877 - Compress exit policies even more -- look for duplicate lines
29879 - Clients now honor the "guard" flag in the router status when
29880 picking entry guards, rather than looking at is_fast or is_stable.
29881 - Retain unrecognized lines in $DATADIR/state file, so that we can
29882 be forward-compatible.
29883 - Generate 18.0.0.0/8 address policy format in descs when we can;
29884 warn when the mask is not reducible to a bit-prefix.
29885 - Let the user set ControlListenAddress in the torrc. This can be
29886 dangerous, but there are some cases (like a secured LAN) where it
29888 - Split ReachableAddresses into ReachableDirAddresses and
29889 ReachableORAddresses, so we can restrict Dir conns to port 80
29890 and OR conns to port 443.
29891 - Now we can target arch and OS in rpm builds (contributed by
29892 Phobos). Also make the resulting dist-rpm filename match the
29894 - New config options to help controllers: FetchServerDescriptors
29895 and FetchHidServDescriptors for whether to fetch server
29896 info and hidserv info or let the controller do it, and
29897 PublishServerDescriptor and PublishHidServDescriptors.
29898 - Also let the controller set the __AllDirActionsPrivate config
29899 option if you want all directory fetches/publishes to happen via
29900 Tor (it assumes your controller bootstraps your circuits).
29903 Changes in version 0.1.0.17 - 2006-02-17
29904 o Crash bugfixes on 0.1.0.x:
29905 - When servers with a non-zero DirPort came out of hibernation,
29906 sometimes they would trigger an assert.
29908 o Other important bugfixes:
29909 - On platforms that don't have getrlimit (like Windows), we were
29910 artificially constraining ourselves to a max of 1024
29911 connections. Now just assume that we can handle as many as 15000
29912 connections. Hopefully this won't cause other problems.
29914 o Backported features:
29915 - When we're a server, a client asks for an old-style directory,
29916 and our write bucket is empty, don't give it to him. This way
29917 small servers can continue to serve the directory *sometimes*,
29918 without getting overloaded.
29919 - Whenever you get a 503 in response to a directory fetch, try
29920 once more. This will become important once servers start sending
29921 503's whenever they feel busy.
29922 - Fetch a new directory every 120 minutes, not every 40 minutes.
29923 Now that we have hundreds of thousands of users running the old
29924 directory algorithm, it's starting to hurt a lot.
29925 - Bump up the period for forcing a hidden service descriptor upload
29926 from 20 minutes to 1 hour.
29929 Changes in version 0.1.1.13-alpha - 2006-02-09
29930 o Crashes in 0.1.1.x:
29931 - When you tried to setconf ORPort via the controller, Tor would
29932 crash. So people using TorCP to become a server were sad.
29933 - Solve (I hope) the stack-smashing bug that we were seeing on fast
29934 servers. The problem appears to be something do with OpenSSL's
29935 random number generation, or how we call it, or something. Let me
29936 know if the crashes continue.
29937 - Turn crypto hardware acceleration off by default, until we find
29938 somebody smart who can test it for us. (It appears to produce
29939 seg faults in at least some cases.)
29940 - Fix a rare assert error when we've tried all intro points for
29941 a hidden service and we try fetching the service descriptor again:
29942 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
29945 - Fix a major load balance bug: we were round-robining in 16 KB
29946 chunks, and servers with bandwidthrate of 20 KB, while downloading
29947 a 600 KB directory, would starve their other connections. Now we
29948 try to be a bit more fair.
29949 - Dir authorities and mirrors were never expiring the newest
29950 descriptor for each server, causing memory and directory bloat.
29951 - Fix memory-bloating and connection-bloating bug on servers: We
29952 were never closing any connection that had ever had a circuit on
29953 it, because we were checking conn->n_circuits == 0, yet we had a
29954 bug that let it go negative.
29955 - Make Tor work using squid as your http proxy again -- squid
29956 returns an error if you ask for a URL that's too long, and it uses
29957 a really generic error message. Plus, many people are behind a
29958 transparent squid so they don't even realize it.
29959 - On platforms that don't have getrlimit (like Windows), we were
29960 artificially constraining ourselves to a max of 1024
29961 connections. Now just assume that we can handle as many as 15000
29962 connections. Hopefully this won't cause other problems.
29963 - Add a new config option ExitPolicyRejectPrivate which defaults to
29964 1. This means all exit policies will begin with rejecting private
29965 addresses, unless the server operator explicitly turns it off.
29968 - Clients no longer download descriptors for non-running
29970 - Before we add new directory authorities, we should make it
29971 clear that only v1 authorities should receive/publish hidden
29972 service descriptors.
29975 - As soon as we've fetched some more directory info, immediately
29976 try to download more server descriptors. This way we don't have
29977 a 10 second pause during initial bootstrapping.
29978 - Remove even more loud log messages that the server operator can't
29980 - When we're running an obsolete or un-recommended version, make
29981 the log message more clear about what the problem is and what
29982 versions *are* still recommended.
29983 - Provide a more useful warn message when our onion queue gets full:
29984 the CPU is too slow or the exit policy is too liberal.
29985 - Don't warn when we receive a 503 from a dirserver/cache -- this
29986 will pave the way for them being able to refuse if they're busy.
29987 - When we fail to bind a listener, try to provide a more useful
29988 log message: e.g., "Is Tor already running?"
29989 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
29990 Goldberg can prove things about our handshake protocol more
29992 - MaxConn has been obsolete for a while now. Document the ConnLimit
29993 config option, which is a *minimum* number of file descriptors
29994 that must be available else Tor refuses to start.
29995 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
29996 if you log to syslog and want something other than LOG_DAEMON.
29997 - Make dirservers generate a separate "guard" flag to mean,
29998 "would make a good entry guard". Make clients parse it and vote
29999 on it. Not used by clients yet.
30000 - Implement --with-libevent-dir option to ./configure. Also, improve
30001 search techniques to find libevent, and use those for openssl too.
30002 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
30003 - Only start testing reachability once we've established a
30004 circuit. This will make startup on dirservers less noisy.
30005 - Don't try to upload hidden service descriptors until we have
30006 established a circuit.
30007 - Fix the controller's "attachstream 0" command to treat conn like
30008 it just connected, doing address remapping, handling .exit and
30009 .onion idioms, and so on. Now we're more uniform in making sure
30010 that the controller hears about new and closing connections.
30013 Changes in version 0.1.1.12-alpha - 2006-01-11
30014 o Bugfixes on 0.1.1.x:
30015 - The fix to close duplicate server connections was closing all
30016 Tor client connections if they didn't establish a circuit
30017 quickly enough. Oops.
30018 - Fix minor memory issue (double-free) that happened on exit.
30020 o Bugfixes on 0.1.0.x:
30021 - Tor didn't warn when it failed to open a log file.
30024 Changes in version 0.1.1.11-alpha - 2006-01-10
30025 o Crashes in 0.1.1.x:
30026 - Include all the assert/crash fixes from 0.1.0.16.
30027 - If you start Tor and then quit very quickly, there were some
30028 races that tried to free things that weren't allocated yet.
30029 - Fix a rare memory stomp if you're running hidden services.
30030 - Fix segfault when specifying DirServer in config without nickname.
30031 - Fix a seg fault when you finish connecting to a server but at
30032 that moment you dump his server descriptor.
30033 - Extendcircuit and Attachstream controller commands would
30034 assert/crash if you don't give them enough arguments.
30035 - Fix an assert error when we're out of space in the connection_list
30036 and we try to post a hidden service descriptor (reported by weasel).
30037 - If you specify a relative torrc path and you set RunAsDaemon in
30038 your torrc, then it chdir()'s to the new directory. If you HUP,
30039 it tries to load the new torrc location, fails, and exits.
30040 The fix: no longer allow a relative path to torrc using -f.
30043 - Implement "entry guards": automatically choose a handful of entry
30044 nodes and stick with them for all circuits. Only pick new guards
30045 when the ones you have are unsuitable, and if the old guards
30046 become suitable again, switch back. This will increase security
30047 dramatically against certain end-point attacks. The EntryNodes
30048 config option now provides some hints about which entry guards you
30049 want to use most; and StrictEntryNodes means to only use those.
30050 - New directory logic: download by descriptor digest, not by
30051 fingerprint. Caches try to download all listed digests from
30052 authorities; clients try to download "best" digests from caches.
30053 This avoids partitioning and isolating attacks better.
30054 - Make the "stable" router flag in network-status be the median of
30055 the uptimes of running valid servers, and make clients pay
30056 attention to the network-status flags. Thus the cutoff adapts
30057 to the stability of the network as a whole, making IRC, IM, etc
30058 connections more reliable.
30061 - Tor servers with dynamic IP addresses were needing to wait 18
30062 hours before they could start doing reachability testing using
30063 the new IP address and ports. This is because they were using
30064 the internal descriptor to learn what to test, yet they were only
30065 rebuilding the descriptor once they decided they were reachable.
30066 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
30067 to download certain server descriptors, throw them away, and then
30068 fetch them again after 30 minutes. Now mirrors throw away these
30069 server descriptors so clients can't get them.
30070 - We were leaving duplicate connections to other ORs open for a week,
30071 rather than closing them once we detect a duplicate. This only
30072 really affected authdirservers, but it affected them a lot.
30073 - Spread the authdirservers' reachability testing over the entire
30074 testing interval, so we don't try to do 500 TLS's at once every
30078 - If the network is down, and we try to connect to a conn because
30079 we have a circuit in mind, and we timeout (30 seconds) because the
30080 network never answers, we were expiring the circuit, but we weren't
30081 obsoleting the connection or telling the entry_guards functions.
30082 - Some Tor servers process billions of cells per day. These statistics
30083 need to be uint64_t's.
30084 - Check for integer overflows in more places, when adding elements
30085 to smartlists. This could possibly prevent a buffer overflow
30086 on malicious huge inputs. I don't see any, but I haven't looked
30088 - ReachableAddresses kept growing new "reject *:*" lines on every
30090 - When you "setconf log" via the controller, it should remove all
30091 logs. We were automatically adding back in a "log notice stdout".
30092 - Newly bootstrapped Tor networks couldn't establish hidden service
30093 circuits until they had nodes with high uptime. Be more tolerant.
30094 - We were marking servers down when they could not answer every piece
30095 of the directory request we sent them. This was far too harsh.
30096 - Fix the torify (tsocks) config file to not use Tor for localhost
30098 - Directory authorities now go to the proper authority when asking for
30099 a networkstatus, even when they want a compressed one.
30100 - Fix a harmless bug that was causing Tor servers to log
30101 "Got an end because of misc error, but we're not an AP. Closing."
30102 - Authorities were treating their own descriptor changes as cosmetic,
30103 meaning the descriptor available in the network-status and the
30104 descriptor that clients downloaded were different.
30105 - The OS X installer was adding a symlink for tor_resolve but
30106 the binary was called tor-resolve (reported by Thomas Hardly).
30107 - Workaround a problem with some http proxies where they refuse GET
30108 requests that specify "Content-Length: 0" (reported by Adrian).
30109 - Fix wrong log message when you add a "HiddenServiceNodes" config
30110 line without any HiddenServiceDir line (reported by Chris Thomas).
30113 - Write the TorVersion into the state file so we have a prayer of
30114 keeping forward and backward compatibility.
30115 - Revive the FascistFirewall config option rather than eliminating it:
30116 now it's a synonym for ReachableAddresses *:80,*:443.
30117 - Clients choose directory servers from the network status lists,
30118 not from their internal list of router descriptors. Now they can
30119 go to caches directly rather than needing to go to authorities
30121 - Directory authorities ignore router descriptors that have only
30122 cosmetic differences: do this for 0.1.0.x servers now too.
30123 - Add a new flag to network-status indicating whether the server
30124 can answer v2 directory requests too.
30125 - Authdirs now stop whining so loudly about bad descriptors that
30126 they fetch from other dirservers. So when there's a log complaint,
30127 it's for sure from a freshly uploaded descriptor.
30128 - Reduce memory requirements in our structs by changing the order
30130 - There used to be two ways to specify your listening ports in a
30131 server descriptor: on the "router" line and with a separate "ports"
30132 line. Remove support for the "ports" line.
30133 - New config option "AuthDirRejectUnlisted" for auth dirservers as
30134 a panic button: if we get flooded with unusable servers we can
30135 revert to only listing servers in the approved-routers file.
30136 - Auth dir servers can now mark a fingerprint as "!reject" or
30137 "!invalid" in the approved-routers file (as its nickname), to
30138 refuse descriptors outright or include them but marked as invalid.
30139 - Servers store bandwidth history across restarts/crashes.
30140 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
30141 get a better idea of why their circuits failed. Not used yet.
30142 - Directory mirrors now cache up to 16 unrecognized network-status
30143 docs. Now we can add new authdirservers and they'll be cached too.
30144 - When picking a random directory, prefer non-authorities if any
30146 - New controller option "getinfo desc/all-recent" to fetch the
30147 latest server descriptor for every router that Tor knows about.
30150 Changes in version 0.1.0.16 - 2006-01-02
30151 o Crash bugfixes on 0.1.0.x:
30152 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
30153 corrupting the heap, losing FDs, or crashing when we need to resize
30154 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
30155 - It turns out sparc64 platforms crash on unaligned memory access
30156 too -- so detect and avoid this.
30157 - Handle truncated compressed data correctly (by detecting it and
30159 - Fix possible-but-unlikely free(NULL) in control.c.
30160 - When we were closing connections, there was a rare case that
30161 stomped on memory, triggering seg faults and asserts.
30162 - Avoid potential infinite recursion when building a descriptor. (We
30163 don't know that it ever happened, but better to fix it anyway.)
30164 - We were neglecting to unlink marked circuits from soon-to-close OR
30165 connections, which caused some rare scribbling on freed memory.
30166 - Fix a memory stomping race bug when closing the joining point of two
30167 rendezvous circuits.
30168 - Fix an assert in time parsing found by Steven Murdoch.
30170 o Other bugfixes on 0.1.0.x:
30171 - When we're doing reachability testing, provide more useful log
30172 messages so the operator knows what to expect.
30173 - Do not check whether DirPort is reachable when we are suppressing
30174 advertising it because of hibernation.
30175 - When building with -static or on Solaris, we sometimes needed -ldl.
30176 - When we're deciding whether a stream has enough circuits around
30177 that can handle it, count the freshly dirty ones and not the ones
30178 that are so dirty they won't be able to handle it.
30179 - When we're expiring old circuits, we had a logic error that caused
30180 us to close new rendezvous circuits rather than old ones.
30181 - Give a more helpful log message when you try to change ORPort via
30182 the controller: you should upgrade Tor if you want that to work.
30183 - We were failing to parse Tor versions that start with "Tor ".
30184 - Tolerate faulty streams better: when a stream fails for reason
30185 exitpolicy, stop assuming that the router is lying about his exit
30186 policy. When a stream fails for reason misc, allow it to retry just
30187 as if it was resolvefailed. When a stream has failed three times,
30188 reset its failure count so we can try again and get all three tries.
30191 Changes in version 0.1.1.10-alpha - 2005-12-11
30192 o Correctness bugfixes on 0.1.0.x:
30193 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
30194 corrupting the heap, losing FDs, or crashing when we need to resize
30195 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
30196 - Stop doing the complex voodoo overkill checking for insecure
30197 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
30198 - When we were closing connections, there was a rare case that
30199 stomped on memory, triggering seg faults and asserts.
30200 - We were neglecting to unlink marked circuits from soon-to-close OR
30201 connections, which caused some rare scribbling on freed memory.
30202 - When we're deciding whether a stream has enough circuits around
30203 that can handle it, count the freshly dirty ones and not the ones
30204 that are so dirty they won't be able to handle it.
30205 - Recover better from TCP connections to Tor servers that are
30206 broken but don't tell you (it happens!); and rotate TLS
30207 connections once a week.
30208 - When we're expiring old circuits, we had a logic error that caused
30209 us to close new rendezvous circuits rather than old ones.
30210 - Fix a scary-looking but apparently harmless bug where circuits
30211 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
30212 servers, and never switch to state CIRCUIT_STATE_OPEN.
30213 - When building with -static or on Solaris, we sometimes needed to
30215 - Give a useful message when people run Tor as the wrong user,
30216 rather than telling them to start chowning random directories.
30217 - We were failing to inform the controller about new .onion streams.
30219 o Security bugfixes on 0.1.0.x:
30220 - Refuse server descriptors if the fingerprint line doesn't match
30221 the included identity key. Tor doesn't care, but other apps (and
30222 humans) might actually be trusting the fingerprint line.
30223 - We used to kill the circuit when we receive a relay command we
30224 don't recognize. Now we just drop it.
30225 - Start obeying our firewall options more rigorously:
30226 . If we can't get to a dirserver directly, try going via Tor.
30227 . Don't ever try to connect (as a client) to a place our
30228 firewall options forbid.
30229 . If we specify a proxy and also firewall options, obey the
30230 firewall options even when we're using the proxy: some proxies
30231 can only proxy to certain destinations.
30232 - Fix a bug found by Lasse Overlier: when we were making internal
30233 circuits (intended to be cannibalized later for rendezvous and
30234 introduction circuits), we were picking them so that they had
30235 useful exit nodes. There was no need for this, and it actually
30236 aids some statistical attacks.
30237 - Start treating internal circuits and exit circuits separately.
30238 It's important to keep them separate because internal circuits
30239 have their last hops picked like middle hops, rather than like
30240 exit hops. So exiting on them will break the user's expectations.
30242 o Bugfixes on 0.1.1.x:
30243 - Take out the mis-feature where we tried to detect IP address
30244 flapping for people with DynDNS, and chose not to upload a new
30245 server descriptor sometimes.
30246 - Try to be compatible with OpenSSL 0.9.6 again.
30247 - Log fix: when the controller is logging about .onion addresses,
30248 sometimes it didn't include the ".onion" part of the address.
30249 - Don't try to modify options->DirServers internally -- if the
30250 user didn't specify any, just add the default ones directly to
30251 the trusted dirserver list. This fixes a bug where people running
30252 controllers would use SETCONF on some totally unrelated config
30253 option, and Tor would start yelling at them about changing their
30255 - Let the controller's redirectstream command specify a port, in
30256 case the controller wants to change that too.
30257 - When we requested a pile of server descriptors, we sometimes
30258 accidentally launched a duplicate request for the first one.
30259 - Bugfix for trackhostexits: write down the fingerprint of the
30260 chosen exit, not its nickname, because the chosen exit might not
30262 - When parsing foo.exit, if foo is unknown, and we are leaving
30263 circuits unattached, set the chosen_exit field and leave the
30264 address empty. This matters because controllers got confused
30266 - Directory authorities no longer try to download server
30267 descriptors that they know they will reject.
30269 o Features and updates:
30270 - Replace balanced trees with hash tables: this should make stuff
30271 significantly faster.
30272 - Resume using the AES counter-mode implementation that we ship,
30273 rather than OpenSSL's. Ours is significantly faster.
30274 - Many other CPU and memory improvements.
30275 - Add a new config option FastFirstHopPK (on by default) so clients
30276 do a trivial crypto handshake for their first hop, since TLS has
30277 already taken care of confidentiality and authentication.
30278 - Add a new config option TestSocks so people can see if their
30279 applications are using socks4, socks4a, socks5-with-ip, or
30280 socks5-with-hostname. This way they don't have to keep mucking
30281 with tcpdump and wondering if something got cached somewhere.
30282 - Warn when listening on a public address for socks. I suspect a
30283 lot of people are setting themselves up as open socks proxies,
30284 and they have no idea that jerks on the Internet are using them,
30285 since they simply proxy the traffic into the Tor network.
30286 - Add "private:*" as an alias in configuration for policies. Now
30287 you can simplify your exit policy rather than needing to list
30288 every single internal or nonroutable network space.
30289 - Add a new controller event type that allows controllers to get
30290 all server descriptors that were uploaded to a router in its role
30291 as authoritative dirserver.
30292 - Start shipping socks-extensions.txt, tor-doc-unix.html,
30293 tor-doc-server.html, and stylesheet.css in the tarball.
30294 - Stop shipping tor-doc.html in the tarball.
30297 Changes in version 0.1.1.9-alpha - 2005-11-15
30298 o Usability improvements:
30299 - Start calling it FooListenAddress rather than FooBindAddress,
30300 since few of our users know what it means to bind an address
30302 - Reduce clutter in server logs. We're going to try to make
30303 them actually usable now. New config option ProtocolWarnings that
30304 lets you hear about how _other Tors_ are breaking the protocol. Off
30306 - Divide log messages into logging domains. Once we put some sort
30307 of interface on this, it will let people looking at more verbose
30308 log levels specify the topics they want to hear more about.
30309 - Make directory servers return better http 404 error messages
30310 instead of a generic "Servers unavailable".
30311 - Check for even more Windows version flags when writing the platform
30312 string in server descriptors, and note any we don't recognize.
30313 - Clean up more of the OpenSSL memory when exiting, so we can detect
30314 memory leaks better.
30315 - Make directory authorities be non-versioning, non-naming by
30316 default. Now we can add new directory servers without requiring
30317 their operators to pay close attention.
30318 - When logging via syslog, include the pid whenever we provide
30319 a log entry. Suggested by Todd Fries.
30321 o Performance improvements:
30322 - Directory servers now silently throw away new descriptors that
30323 haven't changed much if the timestamps are similar. We do this to
30324 tolerate older Tor servers that upload a new descriptor every 15
30325 minutes. (It seemed like a good idea at the time.)
30326 - Inline bottleneck smartlist functions; use fast versions by default.
30327 - Add a "Map from digest to void*" abstraction digestmap_t so we
30328 can do less hex encoding/decoding. Use it in router_get_by_digest()
30329 to resolve a performance bottleneck.
30330 - Allow tor_gzip_uncompress to extract as much as possible from
30331 truncated compressed data. Try to extract as many
30332 descriptors as possible from truncated http responses (when
30333 DIR_PURPOSE_FETCH_ROUTERDESC).
30334 - Make circ->onionskin a pointer, not a static array. moria2 was using
30335 125000 circuit_t's after it had been up for a few weeks, which
30336 translates to 20+ megs of wasted space.
30337 - The private half of our EDH handshake keys are now chosen out
30338 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
30340 o Security improvements:
30341 - Start making directory caches retain old routerinfos, so soon
30342 clients can start asking by digest of descriptor rather than by
30343 fingerprint of server.
30344 - Add half our entropy from RAND_poll in OpenSSL. This knows how
30345 to use egd (if present), openbsd weirdness (if present), vms/os2
30346 weirdness (if we ever port there), and more in the future.
30348 o Bugfixes on 0.1.0.x:
30349 - Do round-robin writes of at most 16 kB per write. This might be
30350 more fair on loaded Tor servers, and it might resolve our Windows
30351 crash bug. It might also slow things down.
30352 - Our TLS handshakes were generating a single public/private
30353 keypair for the TLS context, rather than making a new one for
30354 each new connections. Oops. (But we were still rotating them
30355 periodically, so it's not so bad.)
30356 - When we were cannibalizing a circuit with a particular exit
30357 node in mind, we weren't checking to see if that exit node was
30358 already present earlier in the circuit. Oops.
30359 - When a Tor server's IP changes (e.g. from a dyndns address),
30360 upload a new descriptor so clients will learn too.
30361 - Really busy servers were keeping enough circuits open on stable
30362 connections that they were wrapping around the circuit_id
30363 space. (It's only two bytes.) This exposed a bug where we would
30364 feel free to reuse a circuit_id even if it still exists but has
30365 been marked for close. Try to fix this bug. Some bug remains.
30366 - If we would close a stream early (e.g. it asks for a .exit that
30367 we know would refuse it) but the LeaveStreamsUnattached config
30368 option is set by the controller, then don't close it.
30370 o Bugfixes on 0.1.1.8-alpha:
30371 - Fix a big pile of memory leaks, some of them serious.
30372 - Do not try to download a routerdesc if we would immediately reject
30374 - Resume inserting a newline between all router descriptors when
30375 generating (old style) signed directories, since our spec says
30377 - When providing content-type application/octet-stream for
30378 server descriptors using .z, we were leaving out the
30379 content-encoding header. Oops. (Everything tolerated this just
30380 fine, but that doesn't mean we need to be part of the problem.)
30381 - Fix a potential seg fault in getconf and getinfo using version 1
30382 of the controller protocol.
30383 - Avoid crash: do not check whether DirPort is reachable when we
30384 are suppressing it because of hibernation.
30385 - Make --hash-password not crash on exit.
30388 Changes in version 0.1.1.8-alpha - 2005-10-07
30389 o New features (major):
30390 - Clients don't download or use the directory anymore. Now they
30391 download and use network-statuses from the trusted dirservers,
30392 and fetch individual server descriptors as needed from mirrors.
30393 See dir-spec.txt for all the gory details.
30394 - Be more conservative about whether to advertise our DirPort.
30395 The main change is to not advertise if we're running at capacity
30396 and either a) we could hibernate or b) our capacity is low and
30397 we're using a default DirPort.
30398 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
30400 o New features (minor):
30401 - Try to be smart about when to retry network-status and
30402 server-descriptor fetches. Still needs some tuning.
30403 - Stop parsing, storing, or using running-routers output (but
30404 mirrors still cache and serve it).
30405 - Consider a threshold of versioning dirservers (dirservers who have
30406 an opinion about which Tor versions are still recommended) before
30407 deciding whether to warn the user that he's obsolete.
30408 - Dirservers can now reject/invalidate by key and IP, with the
30409 config options "AuthDirInvalid" and "AuthDirReject". This is
30410 useful since currently we automatically list servers as running
30411 and usable even if we know they're jerks.
30412 - Provide dire warnings to any users who set DirServer; move it out
30413 of torrc.sample and into torrc.complete.
30414 - Add MyFamily to torrc.sample in the server section.
30415 - Add nicknames to the DirServer line, so we can refer to them
30416 without requiring all our users to memorize their IP addresses.
30417 - When we get an EOF or a timeout on a directory connection, note
30418 how many bytes of serverdesc we are dropping. This will help
30419 us determine whether it is smart to parse incomplete serverdesc
30421 - Add a new function to "change pseudonyms" -- that is, to stop
30422 using any currently-dirty circuits for new streams, so we don't
30423 link new actions to old actions. Currently it's only called on
30424 HUP (or SIGNAL RELOAD).
30425 - On sighup, if UseHelperNodes changed to 1, use new circuits.
30426 - Start using RAND_bytes rather than RAND_pseudo_bytes from
30427 OpenSSL. Also, reseed our entropy every hour, not just at
30428 startup. And entropy in 512-bit chunks, not 160-bit chunks.
30430 o Fixes on 0.1.1.7-alpha:
30431 - Nobody ever implemented EVENT_ADDRMAP for control protocol
30432 version 0, so don't let version 0 controllers ask for it.
30433 - If you requested something with too many newlines via the
30434 v1 controller protocol, you could crash tor.
30435 - Fix a number of memory leaks, including some pretty serious ones.
30436 - Re-enable DirPort testing again, so Tor servers will be willing
30437 to advertise their DirPort if it's reachable.
30438 - On TLS handshake, only check the other router's nickname against
30439 its expected nickname if is_named is set.
30441 o Fixes forward-ported from 0.1.0.15:
30442 - Don't crash when we don't have any spare file descriptors and we
30443 try to spawn a dns or cpu worker.
30444 - Make the numbers in read-history and write-history into uint64s,
30445 so they don't overflow and publish negatives in the descriptor.
30447 o Fixes on 0.1.0.x:
30448 - For the OS X package's modified privoxy config file, comment
30449 out the "logfile" line so we don't log everything passed
30451 - We were whining about using socks4 or socks5-with-local-lookup
30452 even when it's an IP in the "virtual" range we designed exactly
30454 - We were leaking some memory every time the client changes IPs.
30455 - Never call free() on tor_malloc()d memory. This will help us
30456 use dmalloc to detect memory leaks.
30457 - Check for named servers when looking them up by nickname;
30458 warn when we'recalling a non-named server by its nickname;
30459 don't warn twice about the same name.
30460 - Try to list MyFamily elements by key, not by nickname, and warn
30461 if we've not heard of the server.
30462 - Make windows platform detection (uname equivalent) smarter.
30463 - It turns out sparc64 doesn't like unaligned access either.
30466 Changes in version 0.1.0.15 - 2005-09-23
30467 o Bugfixes on 0.1.0.x:
30468 - Reject ports 465 and 587 (spam targets) in default exit policy.
30469 - Don't crash when we don't have any spare file descriptors and we
30470 try to spawn a dns or cpu worker.
30471 - Get rid of IgnoreVersion undocumented config option, and make us
30472 only warn, never exit, when we're running an obsolete version.
30473 - Don't try to print a null string when your server finds itself to
30474 be unreachable and the Address config option is empty.
30475 - Make the numbers in read-history and write-history into uint64s,
30476 so they don't overflow and publish negatives in the descriptor.
30477 - Fix a minor memory leak in smartlist_string_remove().
30478 - We were only allowing ourselves to upload a server descriptor at
30479 most every 20 minutes, even if it changed earlier than that.
30480 - Clean up log entries that pointed to old URLs.
30483 Changes in version 0.1.1.7-alpha - 2005-09-14
30484 o Fixes on 0.1.1.6-alpha:
30485 - Exit servers were crashing when people asked them to make a
30486 connection to an address not in their exit policy.
30487 - Looking up a non-existent stream for a v1 control connection would
30489 - Fix a seg fault if we ask a dirserver for a descriptor by
30490 fingerprint but he doesn't know about him.
30491 - SETCONF was appending items to linelists, not clearing them.
30492 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
30493 out and refuse the setconf if it would fail.
30494 - Downgrade the dirserver log messages when whining about
30498 - Add Peter Palfrader's check-tor script to tor/contrib/
30499 It lets you easily check whether a given server (referenced by
30500 nickname) is reachable by you.
30501 - Numerous changes to move towards client-side v2 directories. Not
30504 o Fixes on 0.1.0.x:
30505 - If the user gave tor an odd number of command-line arguments,
30506 we were silently ignoring the last one. Now we complain and fail.
30507 [This wins the oldest-bug prize -- this bug has been present since
30508 November 2002, as released in Tor 0.0.0.]
30509 - Do not use unaligned memory access on alpha, mips, or mipsel.
30510 It *works*, but is very slow, so we treat them as if it doesn't.
30511 - Retry directory requests if we fail to get an answer we like
30512 from a given dirserver (we were retrying before, but only if
30513 we fail to connect).
30514 - When writing the RecommendedVersions line, sort them first.
30515 - When the client asked for a rendezvous port that the hidden
30516 service didn't want to provide, we were sending an IP address
30517 back along with the end cell. Fortunately, it was zero. But stop
30519 - Correct "your server is reachable" log entries to indicate that
30520 it was self-testing that told us so.
30523 Changes in version 0.1.1.6-alpha - 2005-09-09
30524 o Fixes on 0.1.1.5-alpha:
30525 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
30526 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
30527 - Fix bug with tor_memmem finding a match at the end of the string.
30528 - Make unit tests run without segfaulting.
30529 - Resolve some solaris x86 compile warnings.
30530 - Handle duplicate lines in approved-routers files without warning.
30531 - Fix bug where as soon as a server refused any requests due to his
30532 exit policy (e.g. when we ask for localhost and he tells us that's
30533 127.0.0.1 and he won't do it), we decided he wasn't obeying his
30534 exit policy using him for any exits.
30535 - Only do openssl hardware accelerator stuff if openssl version is
30538 o New controller features/fixes:
30539 - Add a "RESETCONF" command so you can set config options like
30540 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
30541 a config option in the torrc with no value, then it clears it
30542 entirely (rather than setting it to its default).
30543 - Add a "GETINFO config-file" to tell us where torrc is.
30544 - Avoid sending blank lines when GETINFO replies should be empty.
30545 - Add a QUIT command for the controller (for using it manually).
30546 - Fix a bug in SAVECONF that was adding default dirservers and
30547 other redundant entries to the torrc file.
30549 o Start on the new directory design:
30550 - Generate, publish, cache, serve new network-status format.
30551 - Publish individual descriptors (by fingerprint, by "all", and by
30553 - Publish client and server recommended versions separately.
30554 - Allow tor_gzip_uncompress() to handle multiple concatenated
30555 compressed strings. Serve compressed groups of router
30556 descriptors. The compression logic here could be more
30558 - Distinguish v1 authorities (all currently trusted directories)
30559 from v2 authorities (all trusted directories).
30560 - Change DirServers config line to note which dirs are v1 authorities.
30561 - Add configuration option "V1AuthoritativeDirectory 1" which
30562 moria1, moria2, and tor26 should set.
30563 - Remove option when getting directory cache to see whether they
30564 support running-routers; they all do now. Replace it with one
30565 to see whether caches support v2 stuff.
30568 - Dirservers now do their own external reachability testing of each
30569 Tor server, and only list them as running if they've been found to
30570 be reachable. We also send back warnings to the server's logs if
30571 it uploads a descriptor that we already believe is unreachable.
30572 - Implement exit enclaves: if we know an IP address for the
30573 destination, and there's a running Tor server at that address
30574 which allows exit to the destination, then extend the circuit to
30575 that exit first. This provides end-to-end encryption and end-to-end
30576 authentication. Also, if the user wants a .exit address or enclave,
30577 use 4 hops rather than 3, and cannibalize a general circ for it
30579 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
30580 controller. Also, rotate dns and cpu workers if the controller
30581 changes options that will affect them; and initialize the dns
30582 worker cache tree whether or not we start out as a server.
30583 - Only upload a new server descriptor when options change, 18
30584 hours have passed, uptime is reset, or bandwidth changes a lot.
30585 - Check [X-]Forwarded-For headers in HTTP requests when generating
30586 log messages. This lets people run dirservers (and caches) behind
30587 Apache but still know which IP addresses are causing warnings.
30589 o Config option changes:
30590 - Replace (Fascist)Firewall* config options with a new
30591 ReachableAddresses option that understands address policies.
30592 For example, "ReachableAddresses *:80,*:443"
30593 - Get rid of IgnoreVersion undocumented config option, and make us
30594 only warn, never exit, when we're running an obsolete version.
30595 - Make MonthlyAccountingStart config option truly obsolete now.
30597 o Fixes on 0.1.0.x:
30598 - Reject ports 465 and 587 in the default exit policy, since
30599 people have started using them for spam too.
30600 - It turns out we couldn't bootstrap a network since we added
30601 reachability detection in 0.1.0.1-rc. Good thing the Tor network
30602 has never gone down. Add an AssumeReachable config option to let
30603 servers and dirservers bootstrap. When we're trying to build a
30604 high-uptime or high-bandwidth circuit but there aren't enough
30605 suitable servers, try being less picky rather than simply failing.
30606 - Our logic to decide if the OR we connected to was the right guy
30607 was brittle and maybe open to a mitm for unverified routers.
30608 - We weren't cannibalizing circuits correctly for
30609 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
30610 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
30611 build those from scratch. This should make hidden services faster.
30612 - Predict required circuits better, with an eye toward making hidden
30613 services faster on the service end.
30614 - Retry streams if the exit node sends back a 'misc' failure. This
30615 should result in fewer random failures. Also, after failing
30616 from resolve failed or misc, reset the num failures, so we give
30617 it a fair shake next time we try.
30618 - Clean up the rendezvous warn log msgs, and downgrade some to info.
30619 - Reduce severity on logs about dns worker spawning and culling.
30620 - When we're shutting down and we do something like try to post a
30621 server descriptor or rendezvous descriptor, don't complain that
30622 we seem to be unreachable. Of course we are, we're shutting down.
30623 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
30624 We don't use them yet, but maybe one day our DNS resolver will be
30625 able to discover them.
30626 - Make ContactInfo mandatory for authoritative directory servers.
30627 - Require server descriptors to list IPv4 addresses -- hostnames
30628 are no longer allowed. This also fixes some potential security
30629 problems with people providing hostnames as their address and then
30630 preferentially resolving them to partition users.
30631 - Change log line for unreachability to explicitly suggest /etc/hosts
30632 as the culprit. Also make it clearer what IP address and ports we're
30633 testing for reachability.
30634 - Put quotes around user-supplied strings when logging so users are
30635 more likely to realize if they add bad characters (like quotes)
30637 - Let auth dir servers start without specifying an Address config
30639 - Make unit tests (and other invocations that aren't the real Tor)
30640 run without launching listeners, creating subdirectories, and so on.
30643 Changes in version 0.1.1.5-alpha - 2005-08-08
30644 o Bugfixes included in 0.1.0.14.
30646 o Bugfixes on 0.1.0.x:
30647 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
30648 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
30649 it would silently using ignore the 6668.
30652 Changes in version 0.1.0.14 - 2005-08-08
30653 o Bugfixes on 0.1.0.x:
30654 - Fix the other half of the bug with crypto handshakes
30656 - Fix an assert trigger if you send a 'signal term' via the
30657 controller when it's listening for 'event info' messages.
30660 Changes in version 0.1.1.4-alpha - 2005-08-04
30661 o Bugfixes included in 0.1.0.13.
30664 - Improve tor_gettimeofday() granularity on windows.
30665 - Make clients regenerate their keys when their IP address changes.
30666 - Implement some more GETINFO goodness: expose helper nodes, config
30667 options, getinfo keys.
30670 Changes in version 0.1.0.13 - 2005-08-04
30671 o Bugfixes on 0.1.0.x:
30672 - Fix a critical bug in the security of our crypto handshakes.
30673 - Fix a size_t underflow in smartlist_join_strings2() that made
30674 it do bad things when you hand it an empty smartlist.
30675 - Fix Windows installer to ship Tor license (thanks to Aphex for
30676 pointing out this oversight) and put a link to the doc directory
30678 - Explicitly set no-unaligned-access for sparc: it turns out the
30679 new gcc's let you compile broken code, but that doesn't make it
30683 Changes in version 0.1.1.3-alpha - 2005-07-23
30684 o Bugfixes on 0.1.1.2-alpha:
30685 - Fix a bug in handling the controller's "post descriptor"
30687 - Fix several bugs in handling the controller's "extend circuit"
30689 - Fix a bug in handling the controller's "stream status" event.
30690 - Fix an assert failure if we have a controller listening for
30691 circuit events and we go offline.
30692 - Re-allow hidden service descriptors to publish 0 intro points.
30693 - Fix a crash when generating your hidden service descriptor if
30694 you don't have enough intro points already.
30696 o New features on 0.1.1.2-alpha:
30697 - New controller function "getinfo accounting", to ask how
30698 many bytes we've used in this time period.
30699 - Experimental support for helper nodes: a lot of the risk from
30700 a small static adversary comes because users pick new random
30701 nodes every time they rebuild a circuit. Now users will try to
30702 stick to the same small set of entry nodes if they can. Not
30703 enabled by default yet.
30705 o Bugfixes on 0.1.0.12:
30706 - If you're an auth dir server, always publish your dirport,
30707 even if you haven't yet found yourself to be reachable.
30708 - Fix a size_t underflow in smartlist_join_strings2() that made
30709 it do bad things when you hand it an empty smartlist.
30712 Changes in version 0.1.0.12 - 2005-07-18
30713 o New directory servers:
30714 - tor26 has changed IP address.
30716 o Bugfixes on 0.1.0.x:
30717 - Fix a possible double-free in tor_gzip_uncompress().
30718 - When --disable-threads is set, do not search for or link against
30719 pthreads libraries.
30720 - Don't trigger an assert if an authoritative directory server
30721 claims its dirport is 0.
30722 - Fix bug with removing Tor as an NT service: some people were
30723 getting "The service did not return an error." Thanks to Matt
30727 Changes in version 0.1.1.2-alpha - 2005-07-15
30728 o New directory servers:
30729 - tor26 has changed IP address.
30731 o Bugfixes on 0.1.0.x, crashes/leaks:
30732 - Port the servers-not-obeying-their-exit-policies fix from
30734 - Fix an fd leak in start_daemon().
30735 - On Windows, you can't always reopen a port right after you've
30736 closed it. So change retry_listeners() to only close and re-open
30737 ports that have changed.
30738 - Fix a possible double-free in tor_gzip_uncompress().
30740 o Bugfixes on 0.1.0.x, usability:
30741 - When tor_socketpair() fails in Windows, give a reasonable
30742 Windows-style errno back.
30743 - Let people type "tor --install" as well as "tor -install" when
30745 want to make it an NT service.
30746 - NT service patch from Matt Edman to improve error messages.
30747 - When the controller asks for a config option with an abbreviated
30748 name, give the full name in our response.
30749 - Correct the man page entry on TrackHostExitsExpire.
30750 - Looks like we were never delivering deflated (i.e. compressed)
30751 running-routers lists, even when asked. Oops.
30752 - When --disable-threads is set, do not search for or link against
30753 pthreads libraries.
30755 o Bugfixes on 0.1.1.x:
30756 - Fix a seg fault with autodetecting which controller version is
30760 - New hidden service descriptor format: put a version in it, and
30761 let people specify introduction/rendezvous points that aren't
30762 in "the directory" (which is subjective anyway).
30763 - Allow the DEBUG controller event to work again. Mark certain log
30764 entries as "don't tell this to controllers", so we avoid cycles.
30767 Changes in version 0.1.0.11 - 2005-06-30
30768 o Bugfixes on 0.1.0.x:
30769 - Fix major security bug: servers were disregarding their
30770 exit policies if clients behaved unexpectedly.
30771 - Make OS X init script check for missing argument, so we don't
30772 confuse users who invoke it incorrectly.
30773 - Fix a seg fault in "tor --hash-password foo".
30774 - The MAPADDRESS control command was broken.
30777 Changes in version 0.1.1.1-alpha - 2005-06-29
30779 - Make OS X init script check for missing argument, so we don't
30780 confuse users who invoke it incorrectly.
30781 - Fix a seg fault in "tor --hash-password foo".
30782 - Fix a possible way to DoS dirservers.
30783 - When we complain that your exit policy implicitly allows local or
30784 private address spaces, name them explicitly so operators can
30786 - Make the log message less scary when all the dirservers are
30787 temporarily unreachable.
30788 - We were printing the number of idle dns workers incorrectly when
30792 - Revised controller protocol (version 1) that uses ascii rather
30793 than binary. Add supporting libraries in python and java so you
30794 can use the controller from your applications without caring how
30795 our protocol works.
30796 - Spiffy new support for crypto hardware accelerators. Can somebody
30800 Changes in version 0.0.9.10 - 2005-06-16
30801 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
30802 - Refuse relay cells that claim to have a length larger than the
30803 maximum allowed. This prevents a potential attack that could read
30804 arbitrary memory (e.g. keys) from an exit server's process
30808 Changes in version 0.1.0.10 - 2005-06-14
30809 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
30810 libevent before 1.1a.
30813 Changes in version 0.1.0.9-rc - 2005-06-09
30815 - Reset buf->highwater every time buf_shrink() is called, not just on
30816 a successful shrink. This was causing significant memory bloat.
30817 - Fix buffer overflow when checking hashed passwords.
30818 - Security fix: if seeding the RNG on Win32 fails, quit.
30819 - Allow seeding the RNG on Win32 even when you're not running as
30821 - Disable threading on Solaris too. Something is wonky with it,
30822 cpuworkers, and reentrant libs.
30823 - Reenable the part of the code that tries to flush as soon as an
30824 OR outbuf has a full TLS record available. Perhaps this will make
30825 OR outbufs not grow as huge except in rare cases, thus saving lots
30826 of CPU time plus memory.
30827 - Reject malformed .onion addresses rather then passing them on as
30828 normal web requests.
30829 - Adapt patch from Adam Langley: fix possible memory leak in
30830 tor_lookup_hostname().
30831 - Initialize libevent later in the startup process, so the logs are
30832 already established by the time we start logging libevent warns.
30833 - Use correct errno on win32 if libevent fails.
30834 - Check and warn about known-bad/slow libevent versions.
30835 - Pay more attention to the ClientOnly config option.
30836 - Have torctl.in/tor.sh.in check for location of su binary (needed
30838 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
30839 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
30840 HttpProxyAuthenticator
30841 - Stop warning about sigpipes in the logs. We're going to
30842 pretend that getting these occasionally is normal and fine.
30843 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
30845 installer screens; and don't put stuff into StartupItems unless
30846 the user asks you to.
30847 - Require servers that use the default dirservers to have public IP
30848 addresses. We have too many servers that are configured with private
30849 IPs and their admins never notice the log entries complaining that
30850 their descriptors are being rejected.
30851 - Add OSX uninstall instructions. An actual uninstall script will
30855 Changes in version 0.1.0.8-rc - 2005-05-23
30857 - It turns out that kqueue on OS X 10.3.9 was causing kernel
30858 panics. Disable kqueue on all OS X Tors.
30859 - Fix RPM: remove duplicate line accidentally added to the rpm
30861 - Disable threads on openbsd too, since its gethostaddr is not
30863 - Tolerate libevent 0.8 since it still works, even though it's
30865 - Enable building on Red Hat 9.0 again.
30866 - Allow the middle hop of the testing circuit to be running any
30867 version, now that most of them have the bugfix to let them connect
30868 to unknown servers. This will allow reachability testing to work
30869 even when 0.0.9.7-0.0.9.9 become obsolete.
30870 - Handle relay cells with rh.length too large. This prevents
30871 a potential attack that could read arbitrary memory (maybe even
30872 keys) from the exit server's process.
30873 - We screwed up the dirport reachability testing when we don't yet
30874 have a cached version of the directory. Hopefully now fixed.
30875 - Clean up router_load_single_router() (used by the controller),
30876 so it doesn't seg fault on error.
30877 - Fix a minor memory leak when somebody establishes an introduction
30878 point at your Tor server.
30879 - If a socks connection ends because read fails, don't warn that
30880 you're not sending a socks reply back.
30883 - Add HttpProxyAuthenticator config option too, that works like
30884 the HttpsProxyAuthenticator config option.
30885 - Encode hashed controller passwords in hex instead of base64,
30886 to make it easier to write controllers.
30889 Changes in version 0.1.0.7-rc - 2005-05-17
30891 - Fix a bug in the OS X package installer that prevented it from
30892 installing on Tiger.
30893 - Fix a script bug in the OS X package installer that made it
30894 complain during installation.
30895 - Find libevent even if it's hiding in /usr/local/ and your
30896 CFLAGS and LDFLAGS don't tell you to look there.
30897 - Be able to link with libevent as a shared library (the default
30898 after 1.0d), even if it's hiding in /usr/local/lib and even
30899 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
30900 assuming you're running gcc. Otherwise fail and give a useful
30902 - Fix a bug in the RPM packager: set home directory for _tor to
30903 something more reasonable when first installing.
30904 - Free a minor amount of memory that is still reachable on exit.
30907 Changes in version 0.1.0.6-rc - 2005-05-14
30909 - Implement --disable-threads configure option. Disable threads on
30910 netbsd by default, because it appears to have no reentrant resolver
30912 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
30913 release (1.1) detects and disables kqueue if it's broken.
30914 - Append default exit policy before checking for implicit internal
30915 addresses. Now we don't log a bunch of complaints on startup
30916 when using the default exit policy.
30917 - Some people were putting "Address " in their torrc, and they had
30918 a buggy resolver that resolved " " to 0.0.0.0. Oops.
30919 - If DataDir is ~/.tor, and that expands to /.tor, then default to
30920 LOCALSTATEDIR/tor instead.
30921 - Fix fragmented-message bug in TorControl.py.
30922 - Resolve a minor bug which would prevent unreachable dirports
30923 from getting suppressed in the published descriptor.
30924 - When the controller gave us a new descriptor, we weren't resolving
30925 it immediately, so Tor would think its address was 0.0.0.0 until
30926 we fetched a new directory.
30927 - Fix an uppercase/lowercase case error in suppressing a bogus
30928 libevent warning on some Linuxes.
30931 - Begin scrubbing sensitive strings from logs by default. Turn off
30932 the config option SafeLogging if you need to do debugging.
30933 - Switch to a new buffer management algorithm, which tries to avoid
30934 reallocing and copying quite as much. In first tests it looks like
30935 it uses *more* memory on average, but less cpu.
30936 - First cut at support for "create-fast" cells. Clients can use
30937 these when extending to their first hop, since the TLS already
30938 provides forward secrecy and authentication. Not enabled on
30940 - When dirservers refuse a router descriptor, we now log its
30941 contactinfo, platform, and the poster's IP address.
30942 - Call tor_free_all instead of connections_free_all after forking, to
30943 save memory on systems that need to fork.
30944 - Whine at you if you're a server and you don't set your contactinfo.
30945 - Implement --verify-config command-line option to check if your torrc
30946 is valid without actually launching Tor.
30947 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
30948 rather than just rejecting it.
30951 Changes in version 0.1.0.5-rc - 2005-04-27
30953 - Stop trying to print a null pointer if an OR conn fails because
30954 we didn't like its cert.
30956 - Switch our internal buffers implementation to use a ring buffer,
30957 to hopefully improve performance for fast servers a lot.
30958 - Add HttpsProxyAuthenticator support (basic auth only), based
30959 on patch from Adam Langley.
30960 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
30961 the fast servers that have been joining lately.
30962 - Give hidden service accesses extra time on the first attempt,
30963 since 60 seconds is often only barely enough. This might improve
30965 - Improve performance for dirservers: stop re-parsing the whole
30966 directory every time you regenerate it.
30967 - Add more debugging info to help us find the weird dns freebsd
30968 pthreads bug; cleaner debug messages to help track future issues.
30971 Changes in version 0.0.9.9 - 2005-04-23
30972 o Bugfixes on 0.0.9.x:
30973 - If unofficial Tor clients connect and send weird TLS certs, our
30974 Tor server triggers an assert. This release contains a minimal
30975 backport from the broader fix that we put into 0.1.0.4-rc.
30978 Changes in version 0.1.0.4-rc - 2005-04-23
30980 - If unofficial Tor clients connect and send weird TLS certs, our
30981 Tor server triggers an assert. Stop asserting, and start handling
30982 TLS errors better in other situations too.
30983 - When the controller asks us to tell it about all the debug-level
30984 logs, it turns out we were generating debug-level logs while
30985 telling it about them, which turns into a bad loop. Now keep
30986 track of whether you're sending a debug log to the controller,
30987 and don't log when you are.
30988 - Fix the "postdescriptor" feature of the controller interface: on
30989 non-complete success, only say "done" once.
30991 - Clients are now willing to load balance over up to 2mB, not 1mB,
30992 of advertised bandwidth capacity.
30993 - Add a NoPublish config option, so you can be a server (e.g. for
30994 testing running Tor servers in other Tor networks) without
30995 publishing your descriptor to the primary dirservers.
30998 Changes in version 0.1.0.3-rc - 2005-04-08
30999 o Improvements on 0.1.0.2-rc:
31000 - Client now retries when streams end early for 'hibernating' or
31001 'resource limit' reasons, rather than failing them.
31002 - More automated handling for dirserver operators:
31003 - Automatically approve nodes running 0.1.0.2-rc or later,
31004 now that the the reachability detection stuff is working.
31005 - Now we allow two unverified servers with the same nickname
31006 but different keys. But if a nickname is verified, only that
31007 nickname+key are allowed.
31008 - If you're an authdirserver connecting to an address:port,
31009 and it's not the OR you were expecting, forget about that
31010 descriptor. If he *was* the one you were expecting, then forget
31011 about all other descriptors for that address:port.
31012 - Allow servers to publish descriptors from 12 hours in the future.
31013 Corollary: only whine about clock skew from the dirserver if
31014 he's a trusted dirserver (since now even verified servers could
31015 have quite wrong clocks).
31016 - Adjust maximum skew and age for rendezvous descriptors: let skew
31017 be 48 hours rather than 90 minutes.
31018 - Efficiency improvements:
31019 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
31020 it much faster to look up a circuit for each relay cell.
31021 - Remove most calls to assert_all_pending_dns_resolves_ok(),
31022 since they're eating our cpu on exit nodes.
31023 - Stop wasting time doing a case insensitive comparison for every
31024 dns name every time we do any lookup. Canonicalize the names to
31025 lowercase and be done with it.
31026 - Start sending 'truncated' cells back rather than destroy cells,
31027 if the circuit closes in front of you. This means we won't have
31028 to abandon partially built circuits.
31029 - Only warn once per nickname from add_nickname_list_to_smartlist
31030 per failure, so an entrynode or exitnode choice that's down won't
31032 - Put a note in the torrc about abuse potential with the default
31034 - Revise control spec and implementation to allow all log messages to
31035 be sent to controller with their severities intact (suggested by
31036 Matt Edman). Update TorControl to handle new log event types.
31037 - Provide better explanation messages when controller's POSTDESCRIPTOR
31039 - Stop putting nodename in the Platform string in server descriptors.
31040 It doesn't actually help, and it is confusing/upsetting some people.
31042 o Bugfixes on 0.1.0.2-rc:
31043 - We were printing the host mask wrong in exit policies in server
31044 descriptors. This isn't a critical bug though, since we were still
31045 obeying the exit policy internally.
31046 - Fix Tor when compiled with libevent but without pthreads: move
31047 connection_unregister() from _connection_free() to
31049 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
31050 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
31051 when we look through the connection array, we'll find any of the
31052 cpu/dnsworkers. This is no good.
31054 o Bugfixes on 0.0.9.8:
31055 - Fix possible bug on threading platforms (e.g. win32) which was
31056 leaking a file descriptor whenever a cpuworker or dnsworker died.
31057 - When using preferred entry or exit nodes, ignore whether the
31058 circuit wants uptime or capacity. They asked for the nodes, they
31060 - chdir() to your datadirectory at the *end* of the daemonize process,
31061 not the beginning. This was a problem because the first time you
31062 run tor, if your datadir isn't there, and you have runasdaemon set
31063 to 1, it will try to chdir to it before it tries to create it. Oops.
31064 - Handle changed router status correctly when dirserver reloads
31065 fingerprint file. We used to be dropping all unverified descriptors
31066 right then. The bug was hidden because we would immediately
31067 fetch a directory from another dirserver, which would include the
31068 descriptors we just dropped.
31069 - When we're connecting to an OR and he's got a different nickname/key
31070 than we were expecting, only complain loudly if we're an OP or a
31071 dirserver. Complaining loudly to the OR admins just confuses them.
31072 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
31073 artificially capped at 500kB.
31076 Changes in version 0.0.9.8 - 2005-04-07
31077 o Bugfixes on 0.0.9.x:
31078 - We have a bug that I haven't found yet. Sometimes, very rarely,
31079 cpuworkers get stuck in the 'busy' state, even though the cpuworker
31080 thinks of itself as idle. This meant that no new circuits ever got
31081 established. Here's a workaround to kill any cpuworker that's been
31082 busy for more than 100 seconds.
31085 Changes in version 0.1.0.2-rc - 2005-04-01
31086 o Bugfixes on 0.1.0.1-rc:
31087 - Fixes on reachability detection:
31088 - Don't check for reachability while hibernating.
31089 - If ORPort is reachable but DirPort isn't, still publish the
31090 descriptor, but zero out DirPort until it's found reachable.
31091 - When building testing circs for ORPort testing, use only
31092 high-bandwidth nodes, so fewer circuits fail.
31093 - Complain about unreachable ORPort separately from unreachable
31094 DirPort, so the user knows what's going on.
31095 - Make sure we only conclude ORPort reachability if we didn't
31096 initiate the conn. Otherwise we could falsely conclude that
31097 we're reachable just because we connected to the guy earlier
31098 and he used that same pipe to extend to us.
31099 - Authdirservers shouldn't do ORPort reachability detection,
31100 since they're in clique mode, so it will be rare to find a
31101 server not already connected to them.
31102 - When building testing circuits, always pick middle hops running
31103 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
31104 bug. (This is a kludge; it will go away when 0.0.9.x becomes
31106 - When we decide we're reachable, actually publish our descriptor
31108 - Fix bug in redirectstream in the controller.
31109 - Fix the state descriptor strings so logs don't claim edge streams
31110 are in a different state than they actually are.
31111 - Use recent libevent features when possible (this only really affects
31112 win32 and osx right now, because the new libevent with these
31113 features hasn't been released yet). Add code to suppress spurious
31115 - Prevent possible segfault in connection_close_unattached_ap().
31116 - Fix newlines on torrc in win32.
31117 - Improve error msgs when tor-resolve fails.
31119 o Improvements on 0.0.9.x:
31120 - New experimental script tor/contrib/ExerciseServer.py (needs more
31121 work) that uses the controller interface to build circuits and
31122 fetch pages over them. This will help us bootstrap servers that
31123 have lots of capacity but haven't noticed it yet.
31124 - New experimental script tor/contrib/PathDemo.py (needs more work)
31125 that uses the controller interface to let you choose whole paths
31127 "<hostname>.<path,separated by dots>.<length of path>.path"
31128 - When we've connected to an OR and handshaked but didn't like
31129 the result, we were closing the conn without sending destroy
31130 cells back for pending circuits. Now send those destroys.
31133 Changes in version 0.0.9.7 - 2005-04-01
31134 o Bugfixes on 0.0.9.x:
31135 - Fix another race crash bug (thanks to Glenn Fink for reporting).
31136 - Compare identity to identity, not to nickname, when extending to
31137 a router not already in the directory. This was preventing us from
31138 extending to unknown routers. Oops.
31139 - Make sure to create OS X Tor user in <500 range, so we aren't
31140 creating actual system users.
31141 - Note where connection-that-hasn't-sent-end was marked, and fix
31142 a few really loud instances of this harmless bug (it's fixed more
31146 Changes in version 0.1.0.1-rc - 2005-03-28
31148 - Add reachability testing. Your Tor server will automatically try
31149 to see if its ORPort and DirPort are reachable from the outside,
31150 and it won't upload its descriptor until it decides they are.
31151 - Handle unavailable hidden services better. Handle slow or busy
31152 hidden services better.
31153 - Add support for CONNECTing through https proxies, with "HttpsProxy"
31155 - New exit policy: accept most low-numbered ports, rather than
31156 rejecting most low-numbered ports.
31157 - More Tor controller support (still experimental). See
31158 http://tor.eff.org/doc/control-spec.txt for all the new features,
31159 including signals to emulate unix signals from any platform;
31160 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
31161 closestream; closecircuit; etc.
31162 - Make nt services work and start on startup on win32 (based on
31163 patch by Matt Edman).
31164 - Add a new AddressMap config directive to rewrite incoming socks
31165 addresses. This lets you, for example, declare an implicit
31166 required exit node for certain sites.
31167 - Add a new TrackHostExits config directive to trigger addressmaps
31168 for certain incoming socks addresses -- for sites that break when
31169 your exit keeps changing (based on patch by Mike Perry).
31170 - Redo the client-side dns cache so it's just an addressmap too.
31171 - Notice when our IP changes, and reset stats/uptime/reachability.
31172 - When an application is using socks5, give him the whole variety of
31173 potential socks5 responses (connect refused, host unreachable, etc),
31174 rather than just "success" or "failure".
31175 - A more sane version numbering system. See
31176 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
31177 - New contributed script "exitlist": a simple python script to
31178 parse directories and find Tor nodes that exit to listed
31180 - New contributed script "privoxy-tor-toggle" to toggle whether
31181 Privoxy uses Tor. Seems to be configured for Debian by default.
31182 - Report HTTP reasons to client when getting a response from directory
31183 servers -- so you can actually know what went wrong.
31184 - New config option MaxAdvertisedBandwidth which lets you advertise
31185 a low bandwidthrate (to not attract as many circuits) while still
31186 allowing a higher bandwidthrate in reality.
31188 o Robustness/stability fixes:
31189 - Make Tor use Niels Provos's libevent instead of its current
31190 poll-but-sometimes-select mess. This will let us use faster async
31191 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
31193 - pthread support now too. This was forced because when we forked,
31194 we ended up wasting a lot of duplicate ram over time. Also switch
31195 to foo_r versions of some library calls to allow reentry and
31197 - Better handling for heterogeneous / unreliable nodes:
31198 - Annotate circuits w/ whether they aim to contain high uptime nodes
31199 and/or high capacity nodes. When building circuits, choose
31201 - This means that every single node in an intro rend circuit,
31202 not just the last one, will have a minimum uptime.
31203 - New config option LongLivedPorts to indicate application streams
31204 that will want high uptime circuits.
31205 - Servers reset uptime when a dir fetch entirely fails. This
31206 hopefully reflects stability of the server's network connectivity.
31207 - If somebody starts his tor server in Jan 2004 and then fixes his
31208 clock, don't make his published uptime be a year.
31209 - Reset published uptime when you wake up from hibernation.
31210 - Introduce a notion of 'internal' circs, which are chosen without
31211 regard to the exit policy of the last hop. Intro and rendezvous
31212 circs must be internal circs, to avoid leaking information. Resolve
31213 and connect streams can use internal circs if they want.
31214 - New circuit pooling algorithm: make sure to have enough circs around
31215 to satisfy any predicted ports, and also make sure to have 2 internal
31216 circs around if we've required internal circs lately (and with high
31217 uptime if we've seen that lately too).
31218 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
31219 which describes how often we retry making new circuits if current
31220 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
31221 how long we're willing to make use of an already-dirty circuit.
31222 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
31223 circ as necessary, if there are any completed ones lying around
31224 when we try to launch one.
31225 - Make hidden services try to establish a rendezvous for 30 seconds,
31226 rather than for n (where n=3) attempts to build a circuit.
31227 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
31228 "ShutdownWaitLength".
31229 - Try to be more zealous about calling connection_edge_end when
31230 things go bad with edge conns in connection.c.
31231 - Revise tor-spec to add more/better stream end reasons.
31232 - Revise all calls to connection_edge_end to avoid sending "misc",
31233 and to take errno into account where possible.
31236 - Fix a race condition that can trigger an assert, when we have a
31237 pending create cell and an OR connection fails right then.
31238 - Fix several double-mark-for-close bugs, e.g. where we were finding
31239 a conn for a cell even if that conn is already marked for close.
31240 - Make sequence of log messages when starting on win32 with no config
31241 file more reasonable.
31242 - When choosing an exit node for a new non-internal circ, don't take
31243 into account whether it'll be useful for any pending x.onion
31244 addresses -- it won't.
31245 - Turn addr_policy_compare from a tristate to a quadstate; this should
31246 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
31247 for google.com" problem.
31248 - Make "platform" string in descriptor more accurate for Win32 servers,
31249 so it's not just "unknown platform".
31250 - Fix an edge case in parsing config options (thanks weasel).
31251 If they say "--" on the commandline, it's not an option.
31252 - Reject odd-looking addresses at the client (e.g. addresses that
31253 contain a colon), rather than having the server drop them because
31255 - tor-resolve requests were ignoring .exit if there was a working circuit
31256 they could use instead.
31257 - REUSEADDR on normal platforms means you can rebind to the port
31258 right after somebody else has let it go. But REUSEADDR on win32
31259 means to let you bind to the port _even when somebody else
31260 already has it bound_! So, don't do that on Win32.
31261 - Change version parsing logic: a version is "obsolete" if it is not
31262 recommended and (1) there is a newer recommended version in the
31263 same series, or (2) there are no recommended versions in the same
31264 series, but there are some recommended versions in a newer series.
31265 A version is "new" if it is newer than any recommended version in
31267 - Stop most cases of hanging up on a socks connection without sending
31271 - Require BandwidthRate to be at least 20kB/s for servers.
31272 - When a dirserver causes you to give a warn, mention which dirserver
31274 - New config option DirAllowPrivateAddresses for authdirservers.
31275 Now by default they refuse router descriptors that have non-IP or
31276 private-IP addresses.
31277 - Stop publishing socksport in the directory, since it's not
31278 actually meant to be public. For compatibility, publish a 0 there
31280 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
31281 smart" value, that is low for servers and high for clients.
31282 - If our clock jumps forward by 100 seconds or more, assume something
31283 has gone wrong with our network and abandon all not-yet-used circs.
31284 - Warn when exit policy implicitly allows local addresses.
31285 - If we get an incredibly skewed timestamp from a dirserver mirror
31286 that isn't a verified OR, don't warn -- it's probably him that's
31288 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
31289 cookies to disk and doesn't log each web request to disk. (Thanks
31290 to Brett Carrington for pointing this out.)
31291 - When a client asks us for a dir mirror and we don't have one,
31292 launch an attempt to get a fresh one.
31293 - If we're hibernating and we get a SIGINT, exit immediately.
31294 - Add --with-dmalloc ./configure option, to track memory leaks.
31295 - And try to free all memory on closing, so we can detect what
31297 - Cache local dns resolves correctly even when they're .exit
31299 - Give a better warning when some other server advertises an
31300 ORPort that is actually an apache running ssl.
31301 - Add "opt hibernating 1" to server descriptor to make it clearer
31302 whether the server is hibernating.
31305 Changes in version 0.0.9.6 - 2005-03-24
31306 o Bugfixes on 0.0.9.x (crashes and asserts):
31307 - Add new end stream reasons to maintenance branch. Fix bug where
31308 reason (8) could trigger an assert. Prevent bug from recurring.
31309 - Apparently win32 stat wants paths to not end with a slash.
31310 - Fix assert triggers in assert_cpath_layer_ok(), where we were
31311 blowing away the circuit that conn->cpath_layer points to, then
31312 checking to see if the circ is well-formed. Backport check to make
31313 sure we dont use the cpath on a closed connection.
31314 - Prevent circuit_resume_edge_reading_helper() from trying to package
31315 inbufs for marked-for-close streams.
31316 - Don't crash on hup if your options->address has become unresolvable.
31317 - Some systems (like OS X) sometimes accept() a connection and tell
31318 you the remote host is 0.0.0.0:0. If this happens, due to some
31319 other mis-features, we get confused; so refuse the conn for now.
31321 o Bugfixes on 0.0.9.x (other):
31322 - Fix harmless but scary "Unrecognized content encoding" warn message.
31323 - Add new stream error reason: TORPROTOCOL reason means "you are not
31324 speaking a version of Tor I understand; say bye-bye to your stream."
31325 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
31326 into the future, now that we are more tolerant of skew. This
31327 resolves a bug where a Tor server would refuse to cache a directory
31328 because all the directories it gets are too far in the future;
31329 yet the Tor server never logs any complaints about clock skew.
31330 - Mac packaging magic: make man pages useable, and do not overwrite
31331 existing torrc files.
31332 - Make OS X log happily to /var/log/tor/tor.log
31335 Changes in version 0.0.9.5 - 2005-02-22
31336 o Bugfixes on 0.0.9.x:
31337 - Fix an assert race at exit nodes when resolve requests fail.
31338 - Stop picking unverified dir mirrors--it only leads to misery.
31339 - Patch from Matt Edman to make NT services work better. Service
31340 support is still not compiled into the executable by default.
31341 - Patch from Dmitri Bely so the Tor service runs better under
31342 the win32 SYSTEM account.
31343 - Make tor-resolve actually work (?) on Win32.
31344 - Fix a sign bug when getrlimit claims to have 4+ billion
31345 file descriptors available.
31346 - Stop refusing to start when bandwidthburst == bandwidthrate.
31347 - When create cells have been on the onion queue more than five
31348 seconds, just send back a destroy and take them off the list.
31351 Changes in version 0.0.9.4 - 2005-02-03
31352 o Bugfixes on 0.0.9:
31353 - Fix an assert bug that took down most of our servers: when
31354 a server claims to have 1 GB of bandwidthburst, don't
31356 - Don't crash as badly if we have spawned the max allowed number
31357 of dnsworkers, or we're out of file descriptors.
31358 - Block more file-sharing ports in the default exit policy.
31359 - MaxConn is now automatically set to the hard limit of max
31360 file descriptors we're allowed (ulimit -n), minus a few for
31362 - Give a clearer message when servers need to raise their
31363 ulimit -n when they start running out of file descriptors.
31364 - SGI Compatibility patches from Jan Schaumann.
31365 - Tolerate a corrupt cached directory better.
31366 - When a dirserver hasn't approved your server, list which one.
31367 - Go into soft hibernation after 95% of the bandwidth is used,
31368 not 99%. This is especially important for daily hibernators who
31369 have a small accounting max. Hopefully it will result in fewer
31370 cut connections when the hard hibernation starts.
31371 - Load-balance better when using servers that claim more than
31372 800kB/s of capacity.
31373 - Make NT services work (experimental, only used if compiled in).
31376 Changes in version 0.0.9.3 - 2005-01-21
31377 o Bugfixes on 0.0.9:
31378 - Backport the cpu use fixes from main branch, so busy servers won't
31379 need as much processor time.
31380 - Work better when we go offline and then come back, or when we
31381 run Tor at boot before the network is up. We do this by
31382 optimistically trying to fetch a new directory whenever an
31383 application request comes in and we think we're offline -- the
31384 human is hopefully a good measure of when the network is back.
31385 - Backport some minimal hidserv bugfixes: keep rend circuits open as
31386 long as you keep using them; actually publish hidserv descriptors
31387 shortly after they change, rather than waiting 20-40 minutes.
31388 - Enable Mac startup script by default.
31389 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
31390 - When you update AllowUnverifiedNodes or FirewallPorts via the
31391 controller's setconf feature, we were always appending, never
31393 - When you update HiddenServiceDir via setconf, it was screwing up
31394 the order of reading the lines, making it fail.
31395 - Do not rewrite a cached directory back to the cache; otherwise we
31396 will think it is recent and not fetch a newer one on startup.
31397 - Workaround for webservers that lie about Content-Encoding: Tor
31398 now tries to autodetect compressed directories and compression
31399 itself. This lets us Proxypass dir fetches through apache.
31402 Changes in version 0.0.9.2 - 2005-01-04
31403 o Bugfixes on 0.0.9 (crashes and asserts):
31404 - Fix an assert on startup when the disk is full and you're logging
31406 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
31407 style address, then we'd crash.
31408 - Fix an assert trigger when the running-routers string we get from
31409 a dirserver is broken.
31410 - Make worker threads start and run on win32. Now win32 servers
31412 - Bandaid (not actually fix, but now it doesn't crash) an assert
31413 where the dns worker dies mysteriously and the main Tor process
31414 doesn't remember anything about the address it was resolving.
31416 o Bugfixes on 0.0.9 (Win32):
31417 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
31418 name out of the warning/assert messages.
31419 - Fix a superficial "unhandled error on read" bug on win32.
31420 - The win32 installer no longer requires a click-through for our
31421 license, since our Free Software license grants rights but does not
31423 - Win32: When connecting to a dirserver fails, try another one
31424 immediately. (This was already working for non-win32 Tors.)
31425 - Stop trying to parse $HOME on win32 when hunting for default
31427 - Make tor-resolve.c work on win32 by calling network_init().
31429 o Bugfixes on 0.0.9 (other):
31430 - Make 0.0.9.x build on Solaris again.
31431 - Due to a fencepost error, we were blowing away the \n when reporting
31432 confvalue items in the controller. So asking for multiple config
31433 values at once couldn't work.
31434 - When listing circuits that are pending on an opening OR connection,
31435 if we're an OR we were listing circuits that *end* at us as
31436 being pending on every listener, dns/cpu worker, etc. Stop that.
31437 - Dirservers were failing to create 'running-routers' or 'directory'
31438 strings if we had more than some threshold of routers. Fix them so
31439 they can handle any number of routers.
31440 - Fix a superficial "Duplicate mark for close" bug.
31441 - Stop checking for clock skew for OR connections, even for servers.
31442 - Fix a fencepost error that was chopping off the last letter of any
31443 nickname that is the maximum allowed nickname length.
31444 - Update URLs in log messages so they point to the new website.
31445 - Fix a potential problem in mangling server private keys while
31446 writing to disk (not triggered yet, as far as we know).
31447 - Include the licenses for other free software we include in Tor,
31448 now that we're shipping binary distributions more regularly.
31451 Changes in version 0.0.9.1 - 2004-12-15
31452 o Bugfixes on 0.0.9:
31453 - Make hibernation actually work.
31454 - Make HashedControlPassword config option work.
31455 - When we're reporting event circuit status to a controller,
31456 don't use the stream status code.
31459 Changes in version 0.0.9 - 2004-12-12
31461 - Clean up manpage and torrc.sample file.
31462 - Clean up severities and text of log warnings.
31464 - Make servers trigger an assert when they enter hibernation.
31467 Changes in version 0.0.9rc7 - 2004-12-08
31468 o Bugfixes on 0.0.9rc:
31469 - Fix a stack-trashing crash when an exit node begins hibernating.
31470 - Avoid looking at unallocated memory while considering which
31471 ports we need to build circuits to cover.
31472 - Stop a sigpipe: when an 'end' cell races with eof from the app,
31473 we shouldn't hold-open-until-flush if the eof arrived first.
31474 - Fix a bug with init_cookie_authentication() in the controller.
31475 - When recommending new-format log lines, if the upper bound is
31476 LOG_ERR, leave it implicit.
31478 o Bugfixes on 0.0.8.1:
31479 - Fix a whole slew of memory leaks.
31480 - Fix isspace() and friends so they still make Solaris happy
31481 but also so they don't trigger asserts on win32.
31482 - Fix parse_iso_time on platforms without strptime (eg win32).
31483 - win32: tolerate extra "readable" events better.
31484 - win32: when being multithreaded, leave parent fdarray open.
31485 - Make unit tests work on win32.
31488 Changes in version 0.0.9rc6 - 2004-12-06
31489 o Bugfixes on 0.0.9pre:
31490 - Clean up some more integer underflow opportunities (not exploitable
31492 - While hibernating, hup should not regrow our listeners.
31493 - Send an end to the streams we close when we hibernate, rather
31494 than just chopping them off.
31495 - React to eof immediately on non-open edge connections.
31497 o Bugfixes on 0.0.8.1:
31498 - Calculate timeout for waiting for a connected cell from the time
31499 we sent the begin cell, not from the time the stream started. If
31500 it took a long time to establish the circuit, we would time out
31501 right after sending the begin cell.
31502 - Fix router_compare_addr_to_addr_policy: it was not treating a port
31503 of * as always matching, so we were picking reject *:* nodes as
31504 exit nodes too. Oops.
31507 - New circuit building strategy: keep a list of ports that we've
31508 used in the past 6 hours, and always try to have 2 circuits open
31509 or on the way that will handle each such port. Seed us with port
31510 80 so web users won't complain that Tor is "slow to start up".
31511 - Make kill -USR1 dump more useful stats about circuits.
31512 - When warning about retrying or giving up, print the address, so
31513 the user knows which one it's talking about.
31514 - If you haven't used a clean circuit in an hour, throw it away,
31515 just to be on the safe side. (This means after 6 hours a totally
31516 unused Tor client will have no circuits open.)
31519 Changes in version 0.0.9rc5 - 2004-12-01
31520 o Bugfixes on 0.0.8.1:
31521 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
31522 - Let resolve conns retry/expire also, rather than sticking around
31524 - If we are using select, make sure we stay within FD_SETSIZE.
31526 o Bugfixes on 0.0.9pre:
31527 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
31528 but doesn't seem to be currently; thanks to Ilja van Sprundel for
31530 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
31531 instead. Impose minima and maxima for all *Period options; impose
31532 even tighter maxima for fetching if we are a caching dirserver.
31533 Clip rather than rejecting.
31534 - Fetch cached running-routers from servers that serve it (that is,
31535 authdirservers and servers running 0.0.9rc5-cvs or later.)
31538 - Accept *:706 (silc) in default exit policy.
31539 - Implement new versioning format for post 0.1.
31540 - Support "foo.nickname.exit" addresses, to let Alice request the
31541 address "foo" as viewed by exit node "nickname". Based on a patch
31543 - Make tor --version --version dump the cvs Id of every file.
31546 Changes in version 0.0.9rc4 - 2004-11-28
31547 o Bugfixes on 0.0.8.1:
31548 - Make windows sockets actually non-blocking (oops), and handle
31549 win32 socket errors better.
31551 o Bugfixes on 0.0.9rc1:
31552 - Actually catch the -USR2 signal.
31555 Changes in version 0.0.9rc3 - 2004-11-25
31556 o Bugfixes on 0.0.8.1:
31557 - Flush the log file descriptor after we print "Tor opening log file",
31558 so we don't see those messages days later.
31560 o Bugfixes on 0.0.9rc1:
31561 - Make tor-resolve work again.
31562 - Avoid infinite loop in tor-resolve if tor hangs up on it.
31563 - Fix an assert trigger for clients/servers handling resolves.
31566 Changes in version 0.0.9rc2 - 2004-11-24
31567 o Bugfixes on 0.0.9rc1:
31568 - I broke socks5 support while fixing the eof bug.
31569 - Allow unitless bandwidths and intervals; they default to bytes
31571 - New servers don't start out hibernating; they are active until
31572 they run out of bytes, so they have a better estimate of how
31573 long it takes, and so their operators can know they're working.
31576 Changes in version 0.0.9rc1 - 2004-11-23
31577 o Bugfixes on 0.0.8.1:
31578 - Finally fix a bug that's been plaguing us for a year:
31579 With high load, circuit package window was reaching 0. Whenever
31580 we got a circuit-level sendme, we were reading a lot on each
31581 socket, but only writing out a bit. So we would eventually reach
31582 eof. This would be noticed and acted on even when there were still
31583 bytes sitting in the inbuf.
31584 - When poll() is interrupted, we shouldn't believe the revents values.
31586 o Bugfixes on 0.0.9pre6:
31587 - Fix hibernate bug that caused pre6 to be broken.
31588 - Don't keep rephist info for routers that haven't had activity for
31589 24 hours. (This matters now that clients have keys, since we track
31591 - Never call close_temp_logs while validating log options.
31592 - Fix backslash-escaping on tor.sh.in and torctl.in.
31595 - Implement weekly/monthly/daily accounting: now you specify your
31596 hibernation properties by
31597 AccountingMax N bytes|KB|MB|GB|TB
31598 AccountingStart day|week|month [day] HH:MM
31599 Defaults to "month 1 0:00".
31600 - Let bandwidth and interval config options be specified as 5 bytes,
31601 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
31602 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
31603 get back to normal.)
31604 - If your requested entry or exit node has advertised bandwidth 0,
31606 - Be more greedy about filling up relay cells -- we try reading again
31607 once we've processed the stuff we read, in case enough has arrived
31608 to fill the last cell completely.
31609 - Apply NT service patch from Osamu Fujino. Still needs more work.
31612 Changes in version 0.0.9pre6 - 2004-11-15
31613 o Bugfixes on 0.0.8.1:
31614 - Fix assert failure on malformed socks4a requests.
31615 - Use identity comparison, not nickname comparison, to choose which
31616 half of circuit-ID-space each side gets to use. This is needed
31617 because sometimes we think of a router as a nickname, and sometimes
31618 as a hex ID, and we can't predict what the other side will do.
31619 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
31620 write() call will fail and we handle it there.
31621 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
31622 and smartlist_len, which are two major profiling offenders.
31624 o Bugfixes on 0.0.9pre5:
31625 - Fix a bug in read_all that was corrupting config files on windows.
31626 - When we're raising the max number of open file descriptors to
31627 'unlimited', don't log that we just raised it to '-1'.
31628 - Include event code with events, as required by control-spec.txt.
31629 - Don't give a fingerprint when clients do --list-fingerprint:
31630 it's misleading, because it will never be the same again.
31631 - Stop using strlcpy in tor_strndup, since it was slowing us
31633 - Remove warn on startup about missing cached-directory file.
31634 - Make kill -USR1 work again.
31635 - Hibernate if we start tor during the "wait for wakeup-time" phase
31636 of an accounting interval. Log our hibernation plans better.
31637 - Authoritative dirservers now also cache their directory, so they
31638 have it on start-up.
31641 - Fetch running-routers; cache running-routers; compress
31642 running-routers; serve compressed running-routers.z
31643 - Add NSI installer script contributed by J Doe.
31644 - Commit VC6 and VC7 workspace/project files.
31645 - Commit a tor.spec for making RPM files, with help from jbash.
31646 - Add contrib/torctl.in contributed by Glenn Fink.
31647 - Implement the control-spec's SAVECONF command, to write your
31648 configuration to torrc.
31649 - Get cookie authentication for the controller closer to working.
31650 - Include control-spec.txt in the tarball.
31651 - When set_conf changes our server descriptor, upload a new copy.
31652 But don't upload it too often if there are frequent changes.
31653 - Document authentication config in man page, and document signals
31655 - Clean up confusing parts of man page and torrc.sample.
31656 - Make expand_filename handle ~ and ~username.
31657 - Use autoconf to enable largefile support where necessary. Use
31658 ftello where available, since ftell can fail at 2GB.
31659 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
31660 log more informatively.
31661 - Give a slightly more useful output for "tor -h".
31662 - Refuse application socks connections to port 0.
31663 - Check clock skew for verified servers, but allow unverified
31664 servers and clients to have any clock skew.
31665 - Break DirFetchPostPeriod into:
31666 - DirFetchPeriod for fetching full directory,
31667 - StatusFetchPeriod for fetching running-routers,
31668 - DirPostPeriod for posting server descriptor,
31669 - RendPostPeriod for posting hidden service descriptors.
31670 - Make sure the hidden service descriptors are at a random offset
31671 from each other, to hinder linkability.
31674 Changes in version 0.0.9pre5 - 2004-11-09
31675 o Bugfixes on 0.0.9pre4:
31676 - Fix a seg fault in unit tests (doesn't affect main program).
31677 - Fix an assert bug where a hidden service provider would fail if
31678 the first hop of his rendezvous circuit was down.
31679 - Hidden service operators now correctly handle version 1 style
31680 INTRODUCE1 cells (nobody generates them still, so not a critical
31682 - If do_hup fails, actually notice.
31683 - Handle more errnos from accept() without closing the listener.
31684 Some OpenBSD machines were closing their listeners because
31685 they ran out of file descriptors.
31686 - Send resolve cells to exit routers that are running a new
31687 enough version of the resolve code to work right.
31688 - Better handling of winsock includes on non-MSV win32 compilers.
31689 - Some people had wrapped their tor client/server in a script
31690 that would restart it whenever it died. This did not play well
31691 with our "shut down if your version is obsolete" code. Now people
31692 don't fetch a new directory if their local cached version is
31694 - Make our autogen.sh work on ksh as well as bash.
31697 - Hibernation: New config option "AccountingMaxKB" lets you
31698 set how many KBytes per month you want to allow your server to
31699 consume. Rather than spreading those bytes out evenly over the
31700 month, we instead hibernate for some of the month and pop up
31701 at a deterministic time, work until the bytes are consumed, then
31702 hibernate again. Config option "MonthlyAccountingStart" lets you
31703 specify which day of the month your billing cycle starts on.
31704 - Control interface: a separate program can now talk to your
31705 client/server over a socket, and get/set config options, receive
31706 notifications of circuits and streams starting/finishing/dying,
31707 bandwidth used, etc. The next step is to get some GUIs working.
31708 Let us know if you want to help out. See doc/control-spec.txt .
31709 - Ship a contrib/tor-control.py as an example script to interact
31710 with the control port.
31711 - "tor --hash-password zzyxz" will output a salted password for
31712 use in authenticating to the control interface.
31713 - New log format in config:
31714 "Log minsev[-maxsev] stdout|stderr|syslog" or
31715 "Log minsev[-maxsev] file /var/foo"
31718 - DirPolicy config option, to let people reject incoming addresses
31719 from their dirserver.
31720 - "tor --list-fingerprint" will list your identity key fingerprint
31722 - Add "pass" target for RedirectExit, to make it easier to break
31723 out of a sequence of RedirectExit rules.
31724 - Clients now generate a TLS cert too, in preparation for having
31725 them act more like real nodes.
31726 - Ship src/win32/ in the tarball, so people can use it to build.
31727 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
31729 - New "router-status" line in directory, to better bind each verified
31730 nickname to its identity key.
31731 - Deprecate unofficial config option abbreviations, and abbreviations
31732 not on the command line.
31733 - Add a pure-C tor-resolve implementation.
31734 - Use getrlimit and friends to ensure we can reach MaxConn (currently
31735 1024) file descriptors.
31737 o Code security improvements, inspired by Ilja:
31738 - Replace sprintf with snprintf. (I think they were all safe, but
31740 - Replace strcpy/strncpy with strlcpy in more places.
31741 - Avoid strcat; use snprintf or strlcat instead.
31742 - snprintf wrapper with consistent (though not C99) overflow behavior.
31745 Changes in version 0.0.9pre4 - 2004-10-17
31746 o Bugfixes on 0.0.9pre3:
31747 - If the server doesn't specify an exit policy, use the real default
31748 exit policy, not reject *:*.
31749 - Ignore fascistfirewall when uploading/downloading hidden service
31750 descriptors, since we go through Tor for those; and when using
31751 an HttpProxy, since we assume it can reach them all.
31752 - When looking for an authoritative dirserver, use only the ones
31753 configured at boot. Don't bother looking in the directory.
31754 - The rest of the fix for get_default_conf_file() on older win32.
31755 - Make 'Routerfile' config option obsolete.
31758 - New 'MyFamily nick1,...' config option for a server to
31759 specify other servers that shouldn't be used in the same circuit
31760 with it. Only believed if nick1 also specifies us.
31761 - New 'NodeFamily nick1,nick2,...' config option for a client to
31762 specify nodes that it doesn't want to use in the same circuit.
31763 - New 'Redirectexit pattern address:port' config option for a
31764 server to redirect exit connections, e.g. to a local squid.
31767 Changes in version 0.0.9pre3 - 2004-10-13
31768 o Bugfixes on 0.0.8.1:
31769 - Better torrc example lines for dirbindaddress and orbindaddress.
31770 - Improved bounds checking on parsed ints (e.g. config options and
31771 the ones we find in directories.)
31772 - Better handling of size_t vs int, so we're more robust on 64
31774 - Fix the rest of the bug where a newly started OR would appear
31775 as unverified even after we've added his fingerprint and hupped
31777 - Fix a bug from 0.0.7: when read() failed on a stream, we would
31778 close it without sending back an end. So 'connection refused'
31779 would simply be ignored and the user would get no response.
31781 o Bugfixes on 0.0.9pre2:
31782 - Serving the cached-on-disk directory to people is bad. We now
31783 provide no directory until we've fetched a fresh one.
31784 - Workaround for bug on windows where cached-directories get crlf
31786 - Make get_default_conf_file() work on older windows too.
31787 - If we write a *:* exit policy line in the descriptor, don't write
31788 any more exit policy lines.
31791 - Use only 0.0.9pre1 and later servers for resolve cells.
31792 - Make the dirservers file obsolete.
31793 - Include a dir-signing-key token in directories to tell the
31794 parsing entity which key is being used to sign.
31795 - Remove the built-in bulky default dirservers string.
31796 - New config option "Dirserver %s:%d [fingerprint]", which can be
31797 repeated as many times as needed. If no dirservers specified,
31798 default to moria1,moria2,tor26.
31799 - Make moria2 advertise a dirport of 80, so people behind firewalls
31800 will be able to get a directory.
31801 - Http proxy support
31802 - Dirservers translate requests for http://%s:%d/x to /x
31803 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
31804 be routed through this host.
31805 - Clients ask for /tor/x rather than /x for new enough dirservers.
31806 This way we can one day coexist peacefully with apache.
31807 - Clients specify a "Host: %s%d" http header, to be compatible
31808 with more proxies, and so running squid on an exit node can work.
31811 Changes in version 0.0.8.1 - 2004-10-13
31813 - Fix a seg fault that can be triggered remotely for Tor
31814 clients/servers with an open dirport.
31815 - Fix a rare assert trigger, where routerinfos for entries in
31816 our cpath would expire while we're building the path.
31817 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31818 - Fix a rare seg fault for people running hidden services on
31819 intermittent connections.
31820 - Fix a bug in parsing opt keywords with objects.
31821 - Fix a stale pointer assert bug when a stream detaches and
31823 - Fix a string format vulnerability (probably not exploitable)
31824 in reporting stats locally.
31825 - Fix an assert trigger: sometimes launching circuits can fail
31826 immediately, e.g. because too many circuits have failed recently.
31827 - Fix a compile warning on 64 bit platforms.
31830 Changes in version 0.0.9pre2 - 2004-10-03
31832 - Make fetching a cached directory work for 64-bit platforms too.
31833 - Make zlib.h a required header, not an optional header.
31836 Changes in version 0.0.9pre1 - 2004-10-01
31838 - Stop using separate defaults for no-config-file and
31839 empty-config-file. Now you have to explicitly turn off SocksPort,
31840 if you don't want it open.
31841 - Fix a bug in OutboundBindAddress so it (hopefully) works.
31842 - Improve man page to mention more of the 0.0.8 features.
31843 - Fix a rare seg fault for people running hidden services on
31844 intermittent connections.
31845 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
31847 - Fix more dns related bugs: send back resolve_failed and end cells
31848 more reliably when the resolve fails, rather than closing the
31849 circuit and then trying to send the cell. Also attach dummy resolve
31850 connections to a circuit *before* calling dns_resolve(), to fix
31851 a bug where cached answers would never be sent in RESOLVED cells.
31852 - When we run out of disk space, or other log writing error, don't
31853 crash. Just stop logging to that log and continue.
31854 - We were starting to daemonize before we opened our logs, so if
31855 there were any problems opening logs, we would complain to stderr,
31856 which wouldn't work, and then mysteriously exit.
31857 - Fix a rare bug where sometimes a verified OR would connect to us
31858 before he'd uploaded his descriptor, which would cause us to
31859 assign conn->nickname as though he's unverified. Now we look through
31860 the fingerprint list to see if he's there.
31861 - Fix a rare assert trigger, where routerinfos for entries in
31862 our cpath would expire while we're building the path.
31865 - Clients can ask dirservers for /dir.z to get a compressed version
31866 of the directory. Only works for servers running 0.0.9, of course.
31867 - Make clients cache directories and use them to seed their router
31868 lists at startup. This means clients have a datadir again.
31869 - Configuration infrastructure support for warning on obsolete
31871 - Respond to content-encoding headers by trying to uncompress as
31873 - Reply with a deflated directory when a client asks for "dir.z".
31874 We could use allow-encodings instead, but allow-encodings isn't
31875 specified in HTTP 1.0.
31876 - Raise the max dns workers from 50 to 100.
31877 - Discourage people from setting their dirfetchpostperiod more often
31878 than once per minute.
31879 - Protect dirservers from overzealous descriptor uploading -- wait
31880 10 seconds after directory gets dirty, before regenerating.
31883 Changes in version 0.0.8 - 2004-08-25
31884 o Port it to SunOS 5.9 / Athena
31887 Changes in version 0.0.8rc2 - 2004-08-20
31888 o Make it compile on cygwin again.
31889 o When picking unverified routers, skip those with low uptime and/or
31890 low bandwidth, depending on what properties you care about.
31893 Changes in version 0.0.8rc1 - 2004-08-18
31894 o Changes from 0.0.7.3:
31896 - Fix assert triggers: if the other side returns an address 0.0.0.0,
31897 don't put it into the client dns cache.
31898 - If a begin failed due to exit policy, but we believe the IP address
31899 should have been allowed, switch that router to exitpolicy reject *:*
31900 until we get our next directory.
31902 - Clients choose nodes proportional to advertised bandwidth.
31903 - Avoid using nodes with low uptime as introduction points.
31904 - Handle servers with dynamic IP addresses: don't replace
31905 options->Address with the resolved one at startup, and
31906 detect our address right before we make a routerinfo each time.
31907 - 'FascistFirewall' option to pick dirservers and ORs on specific
31908 ports; plus 'FirewallPorts' config option to tell FascistFirewall
31909 which ports are open. (Defaults to 80,443)
31910 - Be more aggressive about trying to make circuits when the network
31911 has changed (e.g. when you unsuspend your laptop).
31912 - Check for time skew on http headers; report date in response to
31914 - If the entrynode config line has only one node, don't pick it as
31916 - Add strict{entry|exit}nodes config options. If set to 1, then
31917 we refuse to build circuits that don't include the specified entry
31919 - OutboundBindAddress config option, to bind to a specific
31920 IP address for outgoing connect()s.
31921 - End truncated log entries (e.g. directories) with "[truncated]".
31923 o Patches to 0.0.8preX:
31925 - Patches to compile and run on win32 again (maybe)?
31926 - Fix crash when looking for ~/.torrc with no $HOME set.
31927 - Fix a race bug in the unit tests.
31928 - Handle verified/unverified name collisions better when new
31929 routerinfo's arrive in a directory.
31930 - Sometimes routers were getting entered into the stats before
31931 we'd assigned their identity_digest. Oops.
31932 - Only pick and establish intro points after we've gotten a
31935 - AllowUnverifiedNodes config option to let circuits choose no-name
31936 routers in entry,middle,exit,introduction,rendezvous positions.
31937 Allow middle and rendezvous positions by default.
31938 - Add a man page for tor-resolve.
31941 Changes in version 0.0.7.3 - 2004-08-12
31942 o Stop dnsworkers from triggering an assert failure when you
31943 ask them to resolve the host "".
31946 Changes in version 0.0.8pre3 - 2004-08-09
31947 o Changes from 0.0.7.2:
31948 - Allow multiple ORs with same nickname in routerlist -- now when
31949 people give us one identity key for a nickname, then later
31950 another, we don't constantly complain until the first expires.
31951 - Remember used bandwidth (both in and out), and publish 15-minute
31952 snapshots for the past day into our descriptor.
31953 - You can now fetch $DIRURL/running-routers to get just the
31954 running-routers line, not the whole descriptor list. (But
31955 clients don't use this yet.)
31956 - When people mistakenly use Tor as an http proxy, point them
31957 at the tor-doc.html rather than the INSTALL.
31958 - Remove our mostly unused -- and broken -- hex_encode()
31959 function. Use base16_encode() instead. (Thanks to Timo Lindfors
31960 for pointing out this bug.)
31961 - Rotate onion keys every 12 hours, not every 2 hours, so we have
31962 fewer problems with people using the wrong key.
31963 - Change the default exit policy to reject the default edonkey,
31964 kazaa, gnutella ports.
31965 - Add replace_file() to util.[ch] to handle win32's rename().
31967 o Changes from 0.0.8preX:
31968 - Fix two bugs in saving onion keys to disk when rotating, so
31969 hopefully we'll get fewer people using old onion keys.
31970 - Fix an assert error that was making SocksPolicy not work.
31971 - Be willing to expire routers that have an open dirport -- it's
31972 just the authoritative dirservers we want to not forget.
31973 - Reject tor-resolve requests for .onion addresses early, so we
31974 don't build a whole rendezvous circuit and then fail.
31975 - When you're warning a server that he's unverified, don't cry
31976 wolf unpredictably.
31977 - Fix a race condition: don't try to extend onto a connection
31978 that's still handshaking.
31979 - For servers in clique mode, require the conn to be open before
31980 you'll choose it for your path.
31981 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
31982 end relay cell, etc.
31983 - Measure bandwidth capacity over the last 24 hours, not just 12
31984 - Bugfix: authoritative dirservers were making and signing a new
31985 directory for each client, rather than reusing the cached one.
31988 Changes in version 0.0.8pre2 - 2004-08-04
31989 o Changes from 0.0.7.2:
31991 - Check directory signature _before_ you decide whether you're
31992 you're running an obsolete version and should exit.
31993 - Check directory signature _before_ you parse the running-routers
31994 list to decide who's running or verified.
31995 - Bugfixes and features:
31996 - Check return value of fclose while writing to disk, so we don't
31997 end up with broken files when servers run out of disk space.
31998 - Log a warning if the user uses an unsafe socks variant, so people
31999 are more likely to learn about privoxy or socat.
32000 - Dirservers now include RFC1123-style dates in the HTTP headers,
32001 which one day we will use to better detect clock skew.
32003 o Changes from 0.0.8pre1:
32004 - Make it compile without warnings again on win32.
32005 - Log a warning if you're running an unverified server, to let you
32006 know you might want to get it verified.
32007 - Only pick a default nickname if you plan to be a server.
32010 Changes in version 0.0.8pre1 - 2004-07-23
32012 - Made our unit tests compile again on OpenBSD 3.5, and tor
32013 itself compile again on OpenBSD on a sparc64.
32014 - We were neglecting milliseconds when logging on win32, so
32015 everything appeared to happen at the beginning of each second.
32017 o Protocol changes:
32018 - 'Extend' relay cell payloads now include the digest of the
32019 intended next hop's identity key. Now we can verify that we're
32020 extending to the right router, and also extend to routers we
32021 hadn't heard of before.
32024 - Tor nodes can now act as relays (with an advertised ORPort)
32025 without being manually verified by the dirserver operators.
32026 - Uploaded descriptors of unverified routers are now accepted
32027 by the dirservers, and included in the directory.
32028 - Verified routers are listed by nickname in the running-routers
32029 list; unverified routers are listed as "$<fingerprint>".
32030 - We now use hash-of-identity-key in most places rather than
32031 nickname or addr:port, for improved security/flexibility.
32032 - To avoid Sybil attacks, paths still use only verified servers.
32033 But now we have a chance to play around with hybrid approaches.
32034 - Nodes track bandwidth usage to estimate capacity (not used yet).
32035 - ClientOnly option for nodes that never want to become servers.
32036 - Directory caching.
32037 - "AuthoritativeDir 1" option for the official dirservers.
32038 - Now other nodes (clients and servers) will cache the latest
32039 directory they've pulled down.
32040 - They can enable their DirPort to serve it to others.
32041 - Clients will pull down a directory from any node with an open
32042 DirPort, and check the signature/timestamp correctly.
32043 - Authoritative dirservers now fetch directories from other
32044 authdirservers, to stay better synced.
32045 - Running-routers list tells who's down also, along with noting
32046 if they're verified (listed by nickname) or unverified (listed
32048 - Allow dirservers to serve running-router list separately.
32049 This isn't used yet.
32050 - ORs connect-on-demand to other ORs
32051 - If you get an extend cell to an OR you're not connected to,
32052 connect, handshake, and forward the create cell.
32053 - The authoritative dirservers stay connected to everybody,
32054 and everybody stays connected to 0.0.7 servers, but otherwise
32055 clients/servers expire unused connections after 5 minutes.
32056 - When servers get a sigint, they delay 30 seconds (refusing new
32057 connections) then exit. A second sigint causes immediate exit.
32058 - File and name management:
32059 - Look for .torrc if no CONFDIR "torrc" is found.
32060 - If no datadir is defined, then choose, make, and secure ~/.tor
32062 - If torrc not found, exitpolicy reject *:*.
32063 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
32064 - If no nickname is defined, derive default from hostname.
32065 - Rename secret key files, e.g. identity.key -> secret_id_key,
32066 to discourage people from mailing their identity key to tor-ops.
32067 - Refuse to build a circuit before the directory has arrived --
32068 it won't work anyway, since you won't know the right onion keys
32070 - Try other dirservers immediately if the one you try is down. This
32071 should tolerate down dirservers better now.
32072 - Parse tor version numbers so we can do an is-newer-than check
32073 rather than an is-in-the-list check.
32074 - New socks command 'resolve', to let us shim gethostbyname()
32076 - A 'tor_resolve' script to access the socks resolve functionality.
32077 - A new socks-extensions.txt doc file to describe our
32078 interpretation and extensions to the socks protocols.
32079 - Add a ContactInfo option, which gets published in descriptor.
32080 - Publish OR uptime in descriptor (and thus in directory) too.
32081 - Write tor version at the top of each log file
32082 - New docs in the tarball:
32084 - Document that you should proxy your SSL traffic too.
32087 Changes in version 0.0.7.2 - 2004-07-07
32088 o A better fix for the 0.0.0.0 problem, that will hopefully
32089 eliminate the remaining related assertion failures.
32092 Changes in version 0.0.7.1 - 2004-07-04
32093 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
32094 since internally we use 0.0.0.0 to signify "not yet resolved".
32097 Changes in version 0.0.7 - 2004-06-07
32098 o Updated the man page to reflect the new features.
32101 Changes in version 0.0.7rc2 - 2004-06-06
32102 o Changes from 0.0.7rc1:
32103 - Make it build on Win32 again.
32104 o Changes from 0.0.6.2:
32105 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
32109 Changes in version 0.0.7rc1 - 2004-06-02
32111 - On sighup, we were adding another log without removing the first
32112 one. So log messages would get duplicated n times for n sighups.
32113 - Several cases of using a connection after we'd freed it. The
32114 problem was that connections that are pending resolve are in both
32115 the pending_resolve tree, and also the circuit's resolving_streams
32116 list. When you want to remove one, you must remove it from both.
32117 - Fix a double-mark-for-close where an end cell arrived for a
32118 resolving stream, and then the resolve failed.
32119 - Check directory signatures based on name of signer, not on whom
32120 we got the directory from. This will let us cache directories more
32123 - Crank up some of our constants to handle more users.
32126 Changes in version 0.0.7pre1 - 2004-06-02
32127 o Fixes for crashes and other obnoxious bugs:
32128 - Fix an epipe bug: sometimes when directory connections failed
32129 to connect, we would give them a chance to flush before closing
32131 - When we detached from a circuit because of resolvefailed, we
32132 would immediately try the same circuit twice more, and then
32133 give up on the resolve thinking we'd tried three different
32135 - Limit the number of intro circuits we'll attempt to build for a
32136 hidden service per 15-minute period.
32137 - Check recommended-software string *early*, before actually parsing
32138 the directory. Thus we can detect an obsolete version and exit,
32139 even if the new directory format doesn't parse.
32140 o Fixes for security bugs:
32141 - Remember which nodes are dirservers when you startup, and if a
32142 random OR enables his dirport, don't automatically assume he's
32143 a trusted dirserver.
32145 - Directory connections were asking the wrong poll socket to
32146 start writing, and not asking themselves to start writing.
32147 - When we detached from a circuit because we sent a begin but
32148 didn't get a connected, we would use it again the first time;
32149 but after that we would correctly switch to a different one.
32150 - Stop warning when the first onion decrypt attempt fails; they
32151 will sometimes legitimately fail now that we rotate keys.
32152 - Override unaligned-access-ok check when $host_cpu is ia64 or
32153 arm. Apparently they allow it but the kernel whines.
32154 - Dirservers try to reconnect periodically too, in case connections
32156 - Fix some memory leaks in directory servers.
32157 - Allow backslash in Win32 filenames.
32158 - Made Tor build complain-free on FreeBSD, hopefully without
32159 breaking other BSD builds. We'll see.
32161 - Doxygen markup on all functions and global variables.
32162 - Make directory functions update routerlist, not replace it. So
32163 now directory disagreements are not so critical a problem.
32164 - Remove the upper limit on number of descriptors in a dirserver's
32165 directory (not that we were anywhere close).
32166 - Allow multiple logfiles at different severity ranges.
32167 - Allow *BindAddress to specify ":port" rather than setting *Port
32168 separately. Allow multiple instances of each BindAddress config
32169 option, so you can bind to multiple interfaces if you want.
32170 - Allow multiple exit policy lines, which are processed in order.
32171 Now we don't need that huge line with all the commas in it.
32172 - Enable accept/reject policies on SOCKS connections, so you can bind
32173 to 0.0.0.0 but still control who can use your OP.
32176 Changes in version 0.0.6.2 - 2004-05-16
32177 o Our integrity-checking digest was checking only the most recent cell,
32178 not the previous cells like we'd thought.
32179 Thanks to Stefan Mark for finding the flaw!
32182 Changes in version 0.0.6.1 - 2004-05-06
32183 o Fix two bugs in our AES counter-mode implementation (this affected
32184 onion-level stream encryption, but not TLS-level). It turns
32185 out we were doing something much more akin to a 16-character
32186 polyalphabetic cipher. Oops.
32187 Thanks to Stefan Mark for finding the flaw!
32188 o Retire moria3 as a directory server, and add tor26 as a directory
32192 Changes in version 0.0.6 - 2004-05-02
32193 [version bump only]
32196 Changes in version 0.0.6rc4 - 2004-05-01
32197 o Update the built-in dirservers list to use the new directory format
32198 o Fix a rare seg fault: if a node offering a hidden service attempts
32199 to build a circuit to Alice's rendezvous point and fails before it
32200 reaches the last hop, it retries with a different circuit, but
32202 o Handle windows socket errors correctly.
32205 Changes in version 0.0.6rc3 - 2004-04-28
32206 o Don't expire non-general excess circuits (if we had enough
32207 circuits open, we were expiring rendezvous circuits -- even
32208 when they had a stream attached. oops.)
32209 o Fetch randomness from /dev/urandom better (not via fopen/fread)
32210 o Better debugging for tls errors
32211 o Some versions of openssl have an SSL_pending function that erroneously
32212 returns bytes when there is a non-application record pending.
32213 o Set Content-Type on the directory and hidserv descriptor.
32214 o Remove IVs from cipher code, since AES-ctr has none.
32215 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
32216 o We were using an array of length zero in a few places.
32217 o win32's gethostbyname can't resolve an IP to an IP.
32218 o win32's close can't close a socket.
32221 Changes in version 0.0.6rc2 - 2004-04-26
32222 o Fix a bug where we were closing tls connections intermittently.
32223 It turns out openssl keeps its errors around -- so if an error
32224 happens, and you don't ask about it, and then another openssl
32225 operation happens and succeeds, and you ask if there was an error,
32226 it tells you about the first error. Fun fun.
32227 o Fix a bug that's been lurking since 27 may 03 (!)
32228 When passing back a destroy cell, we would use the wrong circ id.
32229 'Mostly harmless', but still worth fixing.
32230 o Since we don't support truncateds much, don't bother sending them;
32231 just close the circ.
32232 o check for <machine/limits.h> so we build on NetBSD again (I hope).
32233 o don't crash if a conn that sent a begin has suddenly lost its circuit
32234 (this was quite rare).
32237 Changes in version 0.0.6rc1 - 2004-04-25
32238 o We now rotate link (tls context) keys and onion keys.
32239 o CREATE cells now include oaep padding, so you can tell
32240 if you decrypted them correctly.
32241 o Add bandwidthburst to server descriptor.
32242 o Directories now say which dirserver signed them.
32243 o Use a tor_assert macro that logs failed assertions too.
32246 Changes in version 0.0.6pre5 - 2004-04-18
32247 o changes from 0.0.6pre4:
32248 - make tor build on broken freebsd 5.2 installs
32249 - fix a failed assert when you try an intro point, get a nack, and try
32250 a second one and it works.
32251 - when alice uses a port that the hidden service doesn't accept,
32252 it now sends back an end cell (denied by exit policy). otherwise
32253 alice would just have to wait to time out.
32254 - fix another rare bug: when we had tried all the intro
32255 points for a hidden service, we fetched the descriptor
32256 again, but we left our introcirc thinking it had already
32257 sent an intro, so it kept waiting for a response...
32258 - bugfix: when you sleep your hidden-service laptop, as soon
32259 as it wakes up it tries to upload a service descriptor, but
32260 socketpair fails for some reason (localhost not up yet?).
32261 now we simply give up on that upload, and we'll try again later.
32262 i'd still like to find the bug though.
32263 - if an intro circ waiting for an ack dies before getting one, then
32265 - we were reusing stale service descriptors and refetching usable
32269 Changes in version 0.0.6pre4 - 2004-04-14
32270 o changes from 0.0.6pre3:
32271 - when bob fails to connect to the rendezvous point, and his
32272 circ didn't fail because of the rendezvous point itself, then
32273 he retries a couple of times
32274 - we expire introduction and rendezvous circs more thoroughly
32275 (sometimes they were hanging around forever)
32276 - we expire unattached rendezvous streams that have been around
32277 too long (they were sticking around forever).
32278 - fix a measly fencepost error that was crashing everybody with
32282 Changes in version 0.0.6pre3 - 2004-04-14
32283 o changes from 0.0.6pre2:
32284 - make hup work again
32285 - fix some memory leaks for dirservers
32286 - allow more skew in rendezvous descriptor timestamps, to help
32287 handle people like blanu who don't know what time it is
32288 - normal circs are 3 hops, but some rend/intro circs are 4, if
32289 the initiator doesn't get to choose the last hop
32290 - send acks for introductions, so alice can know whether to try
32292 - bob publishes intro points more correctly
32293 o changes from 0.0.5:
32294 - fix an assert trigger that's been plaguing us since the days
32295 of 0.0.2prexx (thanks weasel!)
32296 - retry stream correctly when we fail to connect because of
32297 exit-policy-reject (should try another) or can't-resolve-address
32298 (also should try another, because dns on random internet servers
32300 - when we hup a dirserver and we've *removed* a server from the
32301 approved-routers list, now we remove that server from the
32302 in-memory directories too
32305 Changes in version 0.0.6pre2 - 2004-04-08
32306 o We fixed our base32 implementation. Now it works on all architectures.
32309 Changes in version 0.0.6pre1 - 2004-04-08
32311 - Hidden services and rendezvous points are implemented. Go to
32312 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
32313 hidden services. (This only works via a socks4a proxy such as
32314 Privoxy, and currently it's quite slow.)
32317 Changes in version 0.0.5 - 2004-03-30
32318 [version bump only]
32321 Changes in version 0.0.5rc3 - 2004-03-29
32322 o Install torrc as torrc.sample -- we no longer clobber your
32324 o Re-enable recommendedversion checking (we broke it in rc2, oops)
32325 o Add in a 'notice' log level for things the operator should hear
32326 but that aren't warnings
32329 Changes in version 0.0.5rc2 - 2004-03-29
32330 o Hold socks connection open until reply is flushed (if possible)
32331 o Make exit nodes resolve IPs to IPs immediately, rather than asking
32332 the dns farm to do it.
32333 o Fix c99 aliasing warnings in rephist.c
32334 o Don't include server descriptors that are older than 24 hours in the
32336 o Give socks 'reject' replies their whole 15s to attempt to flush,
32337 rather than seeing the 60s timeout and assuming the flush had failed.
32338 o Clean automake droppings from the cvs repository
32341 Changes in version 0.0.5rc1 - 2004-03-28
32342 o Fix mangled-state bug in directory fetching (was causing sigpipes).
32343 o Only build circuits after we've fetched the directory: clients were
32344 using only the directory servers before they'd fetched a directory.
32345 This also means longer startup time; so it goes.
32346 o Fix an assert trigger where an OP would fail to handshake, and we'd
32347 expect it to have a nickname.
32348 o Work around a tsocks bug: do a socks reject when AP connection dies
32349 early, else tsocks goes into an infinite loop.
32352 Changes in version 0.0.4 - 2004-03-26
32353 o When connecting to a dirserver or OR and the network is down,
32357 Changes in version 0.0.3 - 2004-03-26
32358 o Warn and fail if server chose a nickname with illegal characters
32359 o Port to Solaris and Sparc:
32360 - include missing header fcntl.h
32361 - have autoconf find -lsocket -lnsl automatically
32362 - deal with hardware word alignment
32363 - make uname() work (solaris has a different return convention)
32364 - switch from using signal() to sigaction()
32365 o Preliminary work on reputation system:
32366 - Keep statistics on success/fail of connect attempts; they're published
32367 by kill -USR1 currently.
32368 - Add a RunTesting option to try to learn link state by creating test
32369 circuits, even when SocksPort is off.
32370 - Remove unused open circuits when there are too many.
32373 Changes in version 0.0.2 - 2004-03-19
32374 - Include strlcpy and strlcat for safer string ops
32375 - define INADDR_NONE so we compile (but still not run) on solaris
32378 Changes in version 0.0.2pre27 - 2004-03-14
32380 - Allow internal tor networks (we were rejecting internal IPs,
32381 now we allow them if they're set explicitly).
32382 - And fix a few endian issues.
32385 Changes in version 0.0.2pre26 - 2004-03-14
32387 - If a stream times out after 15s without a connected cell, don't
32388 try that circuit again: try a new one.
32389 - Retry streams at most 4 times. Then give up.
32390 - When a dirserver gets a descriptor from an unknown router, it
32391 logs its fingerprint (so the dirserver operator can choose to
32392 accept it even without mail from the server operator).
32393 - Inform unapproved servers when we reject their descriptors.
32394 - Make tor build on Windows again. It works as a client, who knows
32396 - Clearer instructions in the torrc for how to set up a server.
32397 - Be more efficient about reading fd's when our global token bucket
32398 (used for rate limiting) becomes empty.
32400 - Stop asserting that computers always go forward in time. It's
32402 - When we sent a cell (e.g. destroy) and then marked an OR connection
32403 expired, we might close it before finishing a flush if the other
32404 side isn't reading right then.
32405 - Don't allow dirservers to start if they haven't defined
32406 RecommendedVersions
32407 - We were caching transient dns failures. Oops.
32408 - Prevent servers from publishing an internal IP as their address.
32409 - Address a strcat vulnerability in circuit.c
32412 Changes in version 0.0.2pre25 - 2004-03-04
32414 - Put the OR's IP in its router descriptor, not its fqdn. That way
32415 we'll stop being stalled by gethostbyname for nodes with flaky dns,
32418 - If the user typed in an address that didn't resolve, the server
32422 Changes in version 0.0.2pre24 - 2004-03-03
32424 - Fix an assertion failure in dns.c, where we were trying to dequeue
32425 a pending dns resolve even if it wasn't pending
32426 - Fix a spurious socks5 warning about still trying to write after the
32427 connection is finished.
32428 - Hold certain marked_for_close connections open until they're finished
32429 flushing, rather than losing bytes by closing them too early.
32430 - Correctly report the reason for ending a stream
32431 - Remove some duplicate calls to connection_mark_for_close
32432 - Put switch_id and start_daemon earlier in the boot sequence, so it
32433 will actually try to chdir() to options.DataDirectory
32434 - Make 'make test' exit(1) if a test fails; fix some unit tests
32435 - Make tor fail when you use a config option it doesn't know about,
32436 rather than warn and continue.
32437 - Make --version work
32438 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
32441 Changes in version 0.0.2pre23 - 2004-02-29
32443 - Print a statement when the first circ is finished, so the user
32444 knows it's working.
32445 - If a relay cell is unrecognized at the end of the circuit,
32446 send back a destroy. (So attacks to mutate cells are more
32448 - New config option 'excludenodes' to avoid certain nodes for circuits.
32449 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
32450 so you can collect coredumps there.
32452 - Fix a bug in tls flushing where sometimes data got wedged and
32453 didn't flush until more data got sent. Hopefully this bug was
32454 a big factor in the random delays we were seeing.
32455 - Make 'connected' cells include the resolved IP, so the client
32456 dns cache actually gets populated.
32457 - Disallow changing from ORPort=0 to ORPort>0 on hup.
32458 - When we time-out on a stream and detach from the circuit, send an
32459 end cell down it first.
32460 - Only warn about an unknown router (in exitnodes, entrynodes,
32461 excludenodes) after we've fetched a directory.
32464 Changes in version 0.0.2pre22 - 2004-02-26
32466 - Servers publish less revealing uname information in descriptors.
32467 - More memory tracking and assertions, to crash more usefully when
32469 - If the default torrc isn't there, just use some default defaults.
32470 Plus provide an internal dirservers file if they don't have one.
32471 - When the user tries to use Tor as an http proxy, give them an http
32472 501 failure explaining that we're a socks proxy.
32473 - Dump a new router.desc on hup, to help confused people who change
32474 their exit policies and then wonder why router.desc doesn't reflect
32476 - Clean up the generic tor.sh init script that we ship with.
32478 - If the exit stream is pending on the resolve, and a destroy arrives,
32479 then the stream wasn't getting removed from the pending list. I
32480 think this was the one causing recent server crashes.
32481 - Use a more robust poll on OSX 10.3, since their poll is flaky.
32482 - When it couldn't resolve any dirservers, it was useless from then on.
32483 Now it reloads the RouterFile (or default dirservers) if it has no
32485 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
32486 many users don't even *have* a /usr/local/sbin/.
32489 Changes in version 0.0.2pre21 - 2004-02-18
32491 - There's a ChangeLog file that actually reflects the changelog.
32492 - There's a 'torify' wrapper script, with an accompanying
32493 tor-tsocks.conf, that simplifies the process of using tsocks for
32494 tor. It even has a man page.
32495 - The tor binary gets installed to sbin rather than bin now.
32496 - Retry streams where the connected cell hasn't arrived in 15 seconds
32497 - Clean up exit policy handling -- get the default out of the torrc,
32498 so we can update it without forcing each server operator to fix
32500 - Allow imaps and pop3s in default exit policy
32502 - Prevent picking middleman nodes as the last node in the circuit
32505 Changes in version 0.0.2pre20 - 2004-01-30
32507 - We now have a deb package, and it's in debian unstable. Go to
32508 it, apt-getters. :)
32509 - I've split the TotalBandwidth option into BandwidthRate (how many
32510 bytes per second you want to allow, long-term) and
32511 BandwidthBurst (how many bytes you will allow at once before the cap
32512 kicks in). This better token bucket approach lets you, say, set
32513 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
32514 performance while not exceeding your monthly bandwidth quota.
32515 - Push out a tls record's worth of data once you've got it, rather
32516 than waiting until you've read everything waiting to be read. This
32517 may improve performance by pipelining better. We'll see.
32518 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
32519 from failed circuits (if they haven't been connected yet) and attach
32521 - Expire old streams that haven't managed to connect. Some day we'll
32522 have them reattach to new circuits instead.
32525 - Fix several memory leaks that were causing servers to become bloated
32527 - Fix a few very rare assert triggers. A few more remain.
32528 - Setuid to User _before_ complaining about running as root.
32531 Changes in version 0.0.2pre19 - 2004-01-07
32533 - Fix deadlock condition in dns farm. We were telling a child to die by
32534 closing the parent's file descriptor to him. But newer children were
32535 inheriting the open file descriptor from the parent, and since they
32536 weren't closing it, the socket never closed, so the child never read
32537 eof, so he never knew to exit. Similarly, dns workers were holding
32538 open other sockets, leading to all sorts of chaos.
32539 - New cleaner daemon() code for forking and backgrounding.
32540 - If you log to a file, it now prints an entry at the top of the
32541 logfile so you know it's working.
32542 - The onionskin challenge length was 30 bytes longer than necessary.
32543 - Started to patch up the spec so it's not quite so out of date.
32546 Changes in version 0.0.2pre18 - 2004-01-02
32548 - Fix endian issues with the 'integrity' field in the relay header.
32549 - Fix a potential bug where connections in state
32550 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
32553 Changes in version 0.0.2pre17 - 2003-12-30
32555 - Made --debuglogfile (or any second log file, actually) work.
32556 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
32557 adversary could force us into an infinite loop.
32560 - Each onionskin handshake now includes a hash of the computed key,
32561 to prove the server's identity and help perfect forward secrecy.
32562 - Changed cell size from 256 to 512 bytes (working toward compatibility
32564 - Changed cell length to 2 bytes, and moved it to the relay header.
32565 - Implemented end-to-end integrity checking for the payloads of
32567 - Separated streamid from 'recognized' (otherwise circuits will get
32568 messed up when we try to have streams exit from the middle). We
32569 use the integrity-checking to confirm that a cell is addressed to
32571 - Randomize the initial circid and streamid values, so an adversary who
32572 breaks into a node can't learn how many circuits or streams have
32576 Changes in version 0.0.2pre16 - 2003-12-14
32578 - Fixed a bug that made HUP trigger an assert
32579 - Fixed a bug where a circuit that immediately failed wasn't being
32580 counted as a failed circuit in counting retries.
32583 - Now we close the circuit when we get a truncated cell: otherwise we're
32584 open to an anonymity attack where a bad node in the path truncates
32585 the circuit and then we open streams at him.
32586 - Add port ranges to exit policies
32587 - Add a conservative default exit policy
32588 - Warn if you're running tor as root
32589 - on HUP, retry OR connections and close/rebind listeners
32590 - options.EntryNodes: try these nodes first when picking the first node
32591 - options.ExitNodes: if your best choices happen to include any of
32592 your preferred exit nodes, you choose among just those preferred
32594 - options.ExcludedNodes: nodes that are never picked in path building
32597 Changes in version 0.0.2pre15 - 2003-12-03
32598 o Robustness and bugfixes:
32599 - Sometimes clients would cache incorrect DNS resolves, which would
32600 really screw things up.
32601 - An OP that goes offline would slowly leak all its sockets and stop
32603 - A wide variety of bugfixes in exit node selection, exit policy
32604 handling, and processing pending streams when a new circuit is
32606 - Pick nodes for a path only from those the directory says are up
32607 - Choose randomly from all running dirservers, not always the first one
32608 - Increase allowed http header size for directory fetch.
32609 - Stop writing to stderr (if we're daemonized it will be closed).
32610 - Enable -g always, so cores will be more useful to me.
32611 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
32614 - Wrote a man page. It lists commonly used options.
32617 - Change default loglevel to warn.
32618 - Make PidFile default to null rather than littering in your CWD.
32619 - OnionRouter config option is now obsolete. Instead it just checks
32621 - Moved to a single unified torrc file for both clients and servers.
32624 Changes in version 0.0.2pre14 - 2003-11-29
32625 o Robustness and bugfixes:
32626 - Force the admin to make the DataDirectory himself
32627 - to get ownership/permissions right
32628 - so clients no longer make a DataDirectory and then never use it
32629 - fix bug where a client who was offline for 45 minutes would never
32630 pull down a directory again
32631 - fix (or at least hide really well) the dns assert bug that was
32632 causing server crashes
32633 - warnings and improved robustness wrt clockskew for certs
32634 - use the native daemon(3) to daemonize, when available
32635 - exit if bind() fails
32636 - exit if neither socksport nor orport is defined
32637 - include our own tor_timegm (Win32 doesn't have its own)
32638 - bugfix for win32 with lots of connections
32639 - fix minor bias in PRNG
32640 - make dirserver more robust to corrupt cached directory
32643 - Wrote the design document (woo)
32645 o Circuit building and exit policies:
32646 - Circuits no longer try to use nodes that the directory has told them
32648 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
32649 bitcounts (18.0.0.0/8).
32650 - Make AP connections standby for a circuit if no suitable circuit
32651 exists, rather than failing
32652 - Circuits choose exit node based on addr/port, exit policies, and
32653 which AP connections are standing by
32654 - Bump min pathlen from 2 to 3
32655 - Relay end cells have a payload to describe why the stream ended.
32656 - If the stream failed because of exit policy, try again with a new
32658 - Clients have a dns cache to remember resolved addresses.
32659 - Notice more quickly when we have no working circuits
32662 - APPort is now called SocksPort
32663 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
32665 - RecommendedVersions is now a config variable rather than
32666 hardcoded (for dirservers)
32667 - Reloads config on HUP
32668 - Usage info on -h or --help
32669 - If you set User and Group config vars, it'll setu/gid to them.
32672 Changes in version 0.0.2pre13 - 2003-10-19
32673 o General stability:
32674 - SSL_write no longer fails when it returns WANTWRITE and the number
32675 of bytes in the buf has changed by the next SSL_write call.
32676 - Fix segfault fetching directory when network is down
32677 - Fix a variety of minor memory leaks
32678 - Dirservers reload the fingerprints file on HUP, so I don't have
32679 to take down the network when I approve a new router
32680 - Default server config file has explicit Address line to specify fqdn
32683 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
32684 - Make listener connections not ever alloc bufs
32686 o Autoconf improvements:
32687 - don't clobber an external CFLAGS in ./configure
32688 - Make install now works
32689 - create var/lib/tor on make install
32690 - autocreate a tor.sh initscript to help distribs
32691 - autocreate the torrc and sample-server-torrc with correct paths
32693 o Log files and Daemonizing now work:
32694 - If --DebugLogFile is specified, log to it at -l debug
32695 - If --LogFile is specified, use it instead of commandline
32696 - If --RunAsDaemon is set, tor forks and backgrounds on startup