1 Changes in version 0.3.2.1-alpha - 2017-09-18
2 Tor 0.3.2.1-alpha is the first release in the 0.3.2.x series. It
3 includes support for our next-generation ("v3") onion service
4 protocol, and adds a new circuit scheduler for more responsive
5 forwarding decisions from relays. There are also numerous other
6 small features and bugfixes here.
8 Below are the changes since Tor 0.3.1.7.
10 o Major feature (scheduler, channel):
11 - Introducing the KIST scheduler which stands for Kernel Informed
12 Socket Transport. It is only available on Linux systems. This
13 comes from a researched and published paper you can find
14 here: http://www.robgjansen.com/publications/kist-sec2014.pdf
15 https://arxiv.org/abs/1709.01044 This is also a major refactoring
16 of the entire scheduler subsystem in order for it to be more
17 modular and thus much more easier to add more scheduler type
18 later. The current scheduler has been named "Vanilla" but we favor
19 KIST if available in this version. A new torrc option has been
20 added and named "Schedulers type1,type2,..." which allows a user
21 to select which scheduler type it wants tor to use. It is also
22 possible to change it at runtime. It is an ordered list by
23 priority. KIST might not be available on all platforms so there is
24 a fallback to "KISTLite" that uses the same mechanisms but without
25 the kernel support. The current default values are: Schedulers
26 KIST,KISTLite,Vanilla. Closes ticket 12541.
28 o Major features (next-generation onion services):
29 - Tor now supports the next-generation onion services protocol for
30 clients and services! As part of this release, the core of
31 proposal 224 has been implemented and is available for
32 experimentation and testing by our users. This newer version of
33 onion services (v3) features various improvements over the legacy
34 system: a) Better crypto (replaced SHA1/DH/RSA1024 with
35 SHA3/ed25519/curve25519) b) Improved directory protocol leaking
36 less to directory servers. c) Improved directory protocol with
37 smaller surface for targeted attacks. d) Better onion address
38 security against impersonation. e) More extensible
39 introduction/rendezvous protocol. f) A cleaner and more modular
40 codebase. Furthermore, as part of this update, onion addresses
41 increase in length and are now 56 characters long:
42 4acth47i6kxnvkewtm6q7ib2s3ufpo5sqbsnzjpbi7utijcltosqemad.onion In
43 the future, we will be releasing more options and features but we
44 first need a testing period, so that the current codebase matures
45 and becomes more robust. Here are some of the features we have
46 planned: 1) Offline keys for onion services 2) Advanced client
47 authorization for onion services 3) Improved guard algorithm for
48 onion services 4) Next-gen onion service statistics Please see our
49 proposal for more details:
50 https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt
51 The default version for onion services remains v2 (the legacy
52 system) until this new codebase gets tested and hardened. Service
53 operators who want to experiment with the new system can use the
54 'HiddenServiceVersion 3' torrc directive along with the regular
55 onion service configuration options. We will publish a blog post
56 about this new feature soon! Enjoy!
58 o Major bugfixes (usability, control port):
59 - Report trusted clock skew indications as bootstrap errors, so
60 controllers can more easily alert users when their clocks are
61 wrong. Fixes bug 23506; bugfix
64 o Minor features (bug detection):
65 - Log a warning message, with stack trace, for any attempt to call
66 get_options() during option validation. Closes ticket 22281.
68 o Minor features (client):
69 - You can now use Tor as a tunneled HTTP proxy: use the
70 HTTPTunnelPort option to open a port that accepts HTTP CONNECT
71 requests. Closes ticket 22407.
72 - Add an extra check to make sure that we always use the new guard
73 selection code for picking our guards. Closes ticket 22779.
74 - When downloading (micro)descriptors, don't split the list of
75 descriptors into multiple requests unless there are at least 32
76 descriptors that we want. Previously, we split at 4, not 32, which
77 could lead to significant overhead in HTTP request size and
78 degradation in compression performance. Closes ticket 23220.
80 o Minor features (command line):
81 - Add a new commandline option, --key-expiration, which prints when
82 the current signing key is going to expire. Implements ticket
83 17639; patch by Isis Lovecruft.
85 o Minor features (control port):
86 - If the control port is used as the HTTP proxy, responds with a
87 meaningful "This is the Tor control port" message, and log the
88 event. Closes ticket 1667. Patch from Ravi Chandra Padmala.
89 - Provide better error message for GETINFO desc/(id|name) when
90 microdescriptors are in use and router descriptors are not
91 fetched. Closes ticket 5847. Patch by Kevin Butler.
92 - Add GETINFO desc/download-enabled and md/download-enabled, to
93 inform the controller whether try to download router descriptors
94 and microdescriptors respectively. Closes ticket 22684.
95 - Added new GETINFO targets ip-to-country/{ipv4,ipv6}-available, so
96 controllers can tell whether the geoip databases are loaded.
98 - Adds a timestamp field to the CIRC_BW and STREAM_BW bandwidth
99 events. Closes ticket 19254. Patch by "DonnchaC".
101 o Minor features (development support):
102 - Developers can now generate a call-graph for Tor using the
103 "calltool" python program, which post-processes object dumps. It
104 should work okay on many Linux and OSX platforms, and might work
105 elsewhere too. To run this, install calltool from
106 https://gitweb.torproject.org/user/nickm/calltool.git and run
107 "make callgraph". Closes ticket 19307.
109 o Minor features (ed25519):
110 - Add validation function to checks for torsion components in
111 ed25119 public keys, used by prop224 client-side code. Closes
112 ticket 22006. Math help by Ian Goldberg.
114 o Minor features (exit relay, DNS):
115 - Improve the clarity and safety of the log message from evdns when
116 receiving an apparent spoofed DNS reply. Closes ticket 3056.
118 o Minor features (integration, hardening):
119 - Added a new NoExec option, to prevent Tor from running other
120 programs. When this option is set to 1, Tor will never try to run
121 another program, regardless of the settings of
122 PortForwardingHelper, ClientTransportPlugin, or
123 ServerTransportPlugin. Once NoExec is set, it cannot be disabled
124 without restarting Tor. Closes ticket 22976.
126 o Minor features (linux seccomp2 sandbox):
127 - If the sandbox filter fails to load, suggest to the user that
128 their kernel might not support seccomp2. Closes ticket 23090.
130 o Minor features (logging, UI):
131 - Improve the warning message for specifying a relay by nickname.
132 The previous message implied that nickname registration was still
133 part of the Tor network design, which it isn't. Closes
136 o Minor features (portability):
137 - Check at configure time whether uint8_t is unsigned char. Lots of
138 existing code already assumes this, and there could be strict
139 aliasing issues if they aren't the same type. Closes ticket 22410.
141 o Minor features (relay, configuration):
142 - Reject attempts to use relative file paths when RunAsDaemon is
143 set. Previously, Tor would accept these, but the directory-
144 changing step of RunAsDaemon would give strange and/or confusing
145 results. Closes ticket 22731.
147 o Minor features (startup, safety):
148 - When configured to write a PID file, Tor now exits if it is unable
149 to do so. Previously, it would warn and continue. Closes
152 o Minor features (static analysis):
153 - The BUG() macro has been changed slightly so that Coverity no
154 longer complains about dead code if the bug is impossible. Closes
157 o Minor features (testing):
158 - The default chutney network tests now include tests for the v3
159 hidden service design. Make sure you have the latest version of
160 chutney if you want to run these. Closes ticket 22437.
161 - Add a unit test to verify that we can parse a hardcoded v2 hidden
162 service descriptor. Closes ticket 15554.
164 o Minor bugfixes (certificate handling):
165 - Fix a time handling bug in Tor certificates set to expire after
166 the year 2106. Fixes bug 23055; bugfix on 0.3.0.1-alpha. Found by
167 Coverity as CID 1415728.
169 o Minor bugfixes (client, usability):
170 - Refrain from needlessly rejecting SOCKS5-with-hostnames and
171 SOCKS4a requests that contain IP address strings, even when
172 SafeSocks in enabled, as this prevents user from connecting to
173 known IP addresses without relying on DNS for resolving. SafeSocks
174 still rejects SOCKS connections that connect to IP addresses when
175 those addresses are _not_ encoded as hostnames. Fixes bug 22461;
176 bugfix on Tor 0.2.6.2-alpha.
178 o Minor bugfixes (code correctness):
179 - Call htons() in extend_cell_format() for encoding a 16-bit value.
180 Previously we used ntohs(), which happens to behave the same on
181 all the platforms we support, but which isn't really correct.
182 Fixes bug 23106; bugfix on 0.2.4.8-alpha.
183 - Make the controller's write_escaped_data() function robust to
184 extremely long inputs. Right now, it doesn't actually receive any
185 extremely long inputs, so this is for defense in depth. Fixes bug
186 19281; bugfix on 0.1.1.1-alpha. Reported by Guido Vranken.
188 o Minor bugfixes (compilation):
189 - Fix unused variable warnings in donna's Curve25519 SSE2 code.
190 Fixes bug 22895; bugfix on 0.2.7.2-alpha.
192 o Minor bugfixes (consensus expiry):
193 - Tor would reconsider updating its directory information every 2
194 minutes instead of only doing it for a consensus that is more than
195 24 hours old (badly expired). This specific check is done in the
196 tor main loop callback that validates if we have an expired
197 consensus. Fixes bug 23091; bugfix on 0.2.0.19-alpha.
199 o Minor bugfixes (directory protocol):
200 - Directory servers now include a "Date:" http header for response
201 codes other than 200. Clients starting with a skewed clock and a
202 recent consensus were getting "304 Not modified" responses from
203 directory authorities, so without a Date header the client would
204 never hear about a wrong clock. Fixes bug 23499; bugfix
206 - Make clients wait for 6 seconds before trying to download their
207 consensus from an authority. Fixes bug 17750; bugfix
210 o Minor bugfixes (DoS-resistance):
211 - If future code asks if there are any running bridges, without
212 checking if bridges are enabled, log a BUG warning rather than
213 crashing. Fixes bug 23524; bugfix on 0.3.0.1-alpha.
215 o Minor bugfixes (format strictness):
216 - Restrict several data formats to decimal. Previously, the
217 BuildTimeHistogram entries in the state file, the "bw=" entries in
218 the bandwidth authority file, and process IDs passed to the
219 __OwningControllerProcess option could all be specified in hex or
220 octal as well as in decimal. This was not an intentional feature.
221 Fixes bug 22802; bugfixes on 0.2.2.1-alpha, 0.2.2.2-alpha,
224 o Minor bugfixes (heartbeat):
225 - If we fail to write a heartbeat message, schedule a retry for the
226 minimum heartbeat interval number of seconds in the future. Fixes
227 bug 19476; bugfix on 0.2.3.1-alpha.
229 o Minor bugfixes (linux seccomp2 sandbox, logging):
230 - Fix some messages on unexpected errors from the seccomp2 library.
231 Fixes bug 22750; bugfix on 0.2.5.1-alpha. Patch from "cypherpunks".
233 o Minor bugfixes (logging):
234 - Remove duplicate log messages regarding opening non-local
235 SocksPorts upon parsing config and opening listeners at startup.
236 Fixes bug 4019; bugfix on 0.2.3.3-alpha.
237 - Use a more comprehensible log message when telling the user
238 they've excluded every running exit node. Fixes bug 7890; bugfix
240 - When logging the number of descriptors we intend to download per
241 directory request, do not log a number higher than then the number
242 of descriptors we're fetching in total. Fixes bug 19648; bugfix
244 - When warning about a directory owned by the wrong user, log the
245 actual name of the user owning the directory. Previously, we'd log
246 the name of the process owner twice. Fixes bug 23487; bugfix
248 - torspec says hop counts are 1-based, so fix two log messages that
249 mistakenly logged 0-based hop counts. Fixes bug 18982; bugfix on
250 0.2.6.2-alpha and 0.2.4.5-alpha. Patch by teor. Credit to Xiaofan
251 Li for reporting this issue.
253 o Minor bugfixes (portability):
254 - Stop using the PATH_MAX variable. The variable is not defined in
255 GNU Hurd which prevents Tor from being built. Fixes bug 23098;
256 bugfix on 0.3.1.1-alpha.
258 o Minor bugfixes (relay):
259 - When uploading our descriptor for the first time after startup,
260 report the reason for uploading as "Tor just started" rather than
261 leaving it blank. Fixes bug 22885; bugfix on 0.2.3.4-alpha.
262 - Avoid unnecessary calls to directory_fetches_from_authorities() on
263 relays. This avoids spurious address resolutions and descriptor
264 rebuilds. This is a mitigation for bug 21789. Fixes bug 23470;
265 bugfix on in 0.2.8.1-alpha.
267 o Minor bugfixes (tests):
268 - Fix a broken unit test for the OutboundAddress option: the parsing
269 function was never returning an error on failure. Fixes bug 23366;
270 bugfix on 0.3.0.3-alpha.
271 - Fix a signed-integer overflow in the unit tests for
272 dir/download_status_random_backoff, which was untriggered until we
273 fixed bug 17750. Fixes bug 22924; bugfix on 0.2.9.1-alpha.
275 o Minor bugfixes (usability, control port):
276 - Stop making an unnecessary routerlist check in NETINFO clock skew
277 detection; this was preventing clients from reporting NETINFO clock
278 skew to controllers. Fixes bug 23532; bugfix on 0.2.4.4-alpha.
280 o Code simplification and refactoring:
281 - Extract the code for handling newly-open channels into a separate
282 function from the general code to handle channel state
283 transitions. This change simplifies our callgraph, reducing the
284 size of the largest strongly connected component by roughly a
285 factor of two. Closes ticket 22608
286 - Remove dead code for largely unused statistics on the number of
287 times we've attempted various public key operations. Fixes bug
288 19871; bugfix on 0.1.2.4-alpha. Fix by Isis Lovecruft.
289 - Remove several now-obsolete functions for asking about old
290 variants directory authority status. Closes ticket 22311; patch
292 - Remove some of the code that once supported "Named" and "Unnamed"
293 routers. Authorities no longer vote for these flags. Closes
295 - Rename the obsolete malleable hybrid_encrypt functions used in TAP
296 and old hidden services to indicate that they aren't suitable for
297 new protocols or formats. Closes ticket 23026.
298 - Replace our STRUCT_OFFSET() macro with offsetof(). Closes ticket
299 22521. Patch from Neel Chauhan.
300 - Split the enormous circuit_send_next_onion_skin() function into
301 multiple subfunctions. Closes ticket 22804.
302 - Split the portions of the buffer.c module that handle particular
303 protocols into separate modules. Part of ticket 23149.
304 - Use our test macros more consistently, to produce more useful
305 error messages when our unit tests fail. Add coccinelle patches to
306 allow us to re-check for test macro uses. Closes ticket 22497.
308 o Deprecated features:
309 - Deprecate HTTPProxy/HTTPProxyAuthenticator config options. They
310 only applies to direct unencrypted HTTP connections to your
311 directory server, which your Tor probably isn't using. Closes
315 - Clarify in the manual that "Sandbox 1" is only supported on Linux
316 kernels. Closes ticket 22677.
317 - Document all values of PublishServerDescriptor in the manpage.
319 - Improve the documentation for the directory port part of the
320 DirAuthority line. Closes ticket 20152.
321 - Restore documentation for the authorities' "approved-routers"
322 file. Closes ticket 21148.
325 - The AllowDotExit option has been removed as unsafe. It has been
326 deprecated since 0.2.9.2-alpha. Closes ticket 23426.
327 - The ClientDNSRejectInternalAddresses flag can no longer be set on
328 non-testing networks. It has been deprecated since 0.2.9.2-alpha.
330 - The controller API no longer includes an AUTHDIR_NEWDESCS event:
331 nobody was using it any longer. Closes ticket 22377.
334 Changes in version 0.2.8.15 - 2017-09-18
335 Tor 0.2.8.15 backports a collection of bugfixes from later
338 Most significantly, it includes a fix for TROVE-2017-008, a
339 security bug that affects hidden services running with the
340 SafeLogging option disabled. For more information, see
341 https://trac.torproject.org/projects/tor/ticket/23490
343 Note that Tor 0.2.8.x will no longer be supported after 1 Jan
344 2018. We suggest that you upgrade to the latest stable release if
345 possible. If you can't, we recommend that you upgrade at least to
346 0.2.9, which will be supported until 2020.
348 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
349 - Avoid an assertion failure bug affecting our implementation of
350 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
351 handling of "0xx" differs from what we had expected. Fixes bug
352 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
355 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
358 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
359 - Backport a fix for an "unused variable" warning that appeared
360 in some versions of mingw. Fixes bug 22838; bugfix on
363 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
364 - Fix a memset() off the end of an array when packing cells. This
365 bug should be harmless in practice, since the corrupted bytes are
366 still in the same structure, and are always padding bytes,
367 ignored, or immediately overwritten, depending on compiler
368 behavior. Nevertheless, because the memset()'s purpose is to make
369 sure that any other cell-handling bugs can't expose bytes to the
370 network, we need to fix it. Fixes bug 22737; bugfix on
371 0.2.4.11-alpha. Fixes CID 1401591.
373 o Build features (backport from 0.3.1.5-alpha):
374 - Tor's repository now includes a Travis Continuous Integration (CI)
375 configuration file (.travis.yml). This is meant to help new
376 developers and contributors who fork Tor to a Github repository be
377 better able to test their changes, and understand what we expect
378 to pass. To use this new build feature, you must fork Tor to your
379 Github account, then go into the "Integrations" menu in the
380 repository settings for your fork and enable Travis, then push
381 your changes. Closes ticket 22636.
384 Changes in version 0.2.9.12 - 2017-09-18
385 Tor 0.2.9.12 backports a collection of bugfixes from later
388 Most significantly, it includes a fix for TROVE-2017-008, a
389 security bug that affects hidden services running with the
390 SafeLogging option disabled. For more information, see
391 https://trac.torproject.org/projects/tor/ticket/23490
393 o Major features (security, backport from 0.3.0.2-alpha):
394 - Change the algorithm used to decide DNS TTLs on client and server
395 side, to better resist DNS-based correlation attacks like the
396 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
397 Feamster. Now relays only return one of two possible DNS TTL
398 values, and clients are willing to believe DNS TTL values up to 3
399 hours long. Closes ticket 19769.
401 o Major bugfixes (crash, directory connections, backport from 0.3.0.5-rc):
402 - Fix a rare crash when sending a begin cell on a circuit whose
403 linked directory connection had already been closed. Fixes bug
404 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
406 o Major bugfixes (DNS, backport from 0.3.0.2-alpha):
407 - Fix a bug that prevented exit nodes from caching DNS records for
408 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
410 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
411 - Fix a typo that had prevented TPROXY-based transparent proxying
412 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
413 Patch from "d4fq0fQAgoJ".
415 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
416 - Avoid an assertion failure bug affecting our implementation of
417 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
418 handling of "0xx" differs from what we had expected. Fixes bug
419 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
421 o Minor features (code style, backport from 0.3.1.3-alpha):
422 - Add "Falls through" comments to our codebase, in order to silence
423 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
424 Stieger. Closes ticket 22446.
426 o Minor features (geoip):
427 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
430 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.1-alpha):
431 - Roll over monthly accounting at the configured hour and minute,
432 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
433 Found by Andrey Karpov with PVS-Studio.
435 o Minor bugfixes (compilation, backport from 0.3.1.5-alpha):
436 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
437 bugfix on 0.2.8.1-alpha.
438 - Fix warnings when building with libscrypt and openssl scrypt support
439 on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
440 - When building with certain versions the mingw C header files, avoid
441 float-conversion warnings when calling the C functions isfinite(),
442 isnan(), and signbit(). Fixes bug 22801; bugfix on 0.2.8.1-alpha.
444 o Minor bugfixes (compilation, backport from 0.3.1.7):
445 - Avoid compiler warnings in the unit tests for running tor_sscanf()
446 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
448 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
449 - Backport a fix for an "unused variable" warning that appeared
450 in some versions of mingw. Fixes bug 22838; bugfix on
453 o Minor bugfixes (controller, backport from 0.3.1.7):
454 - Do not crash when receiving a HSPOST command with an empty body.
455 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
456 - Do not crash when receiving a POSTDESCRIPTOR command with an
457 empty body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
459 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
460 - Avoid Coverity build warnings related to our BUG() macro. By
461 default, Coverity treats BUG() as the Linux kernel does: an
462 instant abort(). We need to override that so our BUG() macro
463 doesn't prevent Coverity from analyzing functions that use it.
464 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
466 o Minor bugfixes (defensive programming, undefined behavior, backport from 0.3.1.4-alpha):
467 - Fix a memset() off the end of an array when packing cells. This
468 bug should be harmless in practice, since the corrupted bytes are
469 still in the same structure, and are always padding bytes,
470 ignored, or immediately overwritten, depending on compiler
471 behavior. Nevertheless, because the memset()'s purpose is to make
472 sure that any other cell-handling bugs can't expose bytes to the
473 network, we need to fix it. Fixes bug 22737; bugfix on
474 0.2.4.11-alpha. Fixes CID 1401591.
476 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
477 - When setting the maximum number of connections allowed by the OS,
478 always allow some extra file descriptors for other files. Fixes
479 bug 22797; bugfix on 0.2.0.10-alpha.
481 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
482 - Avoid a sandbox failure when trying to re-bind to a socket and
483 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
485 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
486 - Permit the fchmod system call, to avoid crashing on startup when
487 starting with the seccomp2 sandbox and an unexpected set of
488 permissions on the data directory or its contents. Fixes bug
489 22516; bugfix on 0.2.5.4-alpha.
491 o Minor bugfixes (relay, backport from 0.3.0.5-rc):
492 - Avoid a double-marked-circuit warning that could happen when we
493 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
496 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
497 - Reject version numbers with non-numeric prefixes (such as +, -, or
498 whitespace). Disallowing whitespace prevents differential version
499 parsing between POSIX-based and Windows platforms. Fixes bug 21507
500 and part of 21508; bugfix on 0.0.8pre1.
502 o Build features (backport from 0.3.1.5-alpha):
503 - Tor's repository now includes a Travis Continuous Integration (CI)
504 configuration file (.travis.yml). This is meant to help new
505 developers and contributors who fork Tor to a Github repository be
506 better able to test their changes, and understand what we expect
507 to pass. To use this new build feature, you must fork Tor to your
508 Github account, then go into the "Integrations" menu in the
509 repository settings for your fork and enable Travis, then push
510 your changes. Closes ticket 22636.
513 Changes in version 0.3.0.11 - 2017-09-18
514 Tor 0.3.0.11 backports a collection of bugfixes from Tor the 0.3.1
517 Most significantly, it includes a fix for TROVE-2017-008, a
518 security bug that affects hidden services running with the
519 SafeLogging option disabled. For more information, see
520 https://trac.torproject.org/projects/tor/ticket/23490
522 o Minor features (code style, backport from 0.3.1.7):
523 - Add "Falls through" comments to our codebase, in order to silence
524 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
525 Stieger. Closes ticket 22446.
528 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
531 o Minor bugfixes (compilation, backport from 0.3.1.7):
532 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
533 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
535 o Minor bugfixes (controller, backport from 0.3.1.7):
536 - Do not crash when receiving a HSPOST command with an empty body.
537 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
538 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
539 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
541 o Minor bugfixes (file limits, osx, backport from 0.3.1.5-alpha):
542 - When setting the maximum number of connections allowed by the OS,
543 always allow some extra file descriptors for other files. Fixes
544 bug 22797; bugfix on 0.2.0.10-alpha.
546 o Minor bugfixes (logging, relay, backport from 0.3.1.6-rc):
547 - Remove a forgotten debugging message when an introduction point
548 successfully establishes a hidden service prop224 circuit with
550 - Change three other log_warn() for an introduction point to
551 protocol warnings, because they can be failure from the network
552 and are not relevant to the operator. Fixes bug 23078; bugfix on
553 0.3.0.1-alpha and 0.3.0.2-alpha.
556 Changes in version 0.3.1.7 - 2017-09-18
557 Tor 0.3.1.7 is the first stable release in the 0.3.1 series.
559 With the 0.3.1 series, Tor now serves and downloads directory
560 information in more compact formats, to save on bandwidth overhead. It
561 also contains a new padding system to resist netflow-based traffic
562 analysis, and experimental support for building parts of Tor in Rust
563 (though no parts of Tor are in Rust yet). There are also numerous
564 small features, bugfixes on earlier release series, and groundwork for
565 the hidden services revamp of 0.3.2.
567 This release also includes a fix for TROVE-2017-008, a security bug
568 that affects hidden services running with the SafeLogging option
569 disabled. For more information, see
570 https://trac.torproject.org/projects/tor/ticket/23490
572 Per our stable release policy, we plan to support each stable release
573 series for at least the next nine months, or for three months after
574 the first stable release of the next series: whichever is longer. If
575 you need a release with long-term support, we recommend that you stay
576 with the 0.2.9 series.
578 Below is a list of the changes since 0.3.1.6-rc. For a list of all
579 changes since 0.3.0, see the ReleaseNotes file.
581 o Major bugfixes (security, hidden services, loggging):
582 - Fix a bug where we could log uninitialized stack when a certain
583 hidden service error occurred while SafeLogging was disabled.
584 Fixes bug #23490; bugfix on 0.2.7.2-alpha. This is also tracked as
585 TROVE-2017-008 and CVE-2017-0380.
587 o Minor features (defensive programming):
588 - Create a pair of consensus parameters, nf_pad_tor2web and
589 nf_pad_single_onion, to disable netflow padding in the consensus
590 for non-anonymous connections in case the overhead is high. Closes
593 o Minor features (diagnostic):
594 - Add a stack trace to the bug warnings that can be logged when
595 trying to send an outgoing relay cell with n_chan == 0. Diagnostic
596 attempt for bug 23105.
598 o Minor features (geoip):
599 - Update geoip and geoip6 to the September 6 2017 Maxmind GeoLite2
602 o Minor bugfixes (compilation):
603 - Avoid compiler warnings in the unit tests for calling tor_sscanf()
604 with wide string outputs. Fixes bug 15582; bugfix on 0.2.6.2-alpha.
606 o Minor bugfixes (controller):
607 - Do not crash when receiving a HSPOST command with an empty body.
608 Fixes part of bug 22644; bugfix on 0.2.7.1-alpha.
609 - Do not crash when receiving a POSTDESCRIPTOR command with an empty
610 body. Fixes part of bug 22644; bugfix on 0.2.0.1-alpha.
612 o Minor bugfixes (relay):
613 - Inform the geoip and rephist modules about all requests, even on
614 relays that are only fetching microdescriptors. Fixes a bug
615 related to 21585; bugfix on 0.3.0.1-alpha.
617 o Minor bugfixes (unit tests):
618 - Fix a channelpadding unit test failure on slow systems by using
619 mocked time instead of actual time. Fixes bug 23077; bugfix
623 Changes in version 0.3.1.6-rc - 2017-09-05
624 Tor 0.3.1.6-rc fixes a few small bugs and annoyances in the 0.3.1
625 release series, including a bug that produced weird behavior on
626 Windows directory caches.
628 This is the first release candidate in the Tor 0.3.1 series. If we
629 find no new bugs or regressions here, the first stable 0.3.1 release
630 will be nearly identical to it.
632 o Major bugfixes (windows, directory cache):
633 - On Windows, do not try to delete cached consensus documents and
634 diffs before they are unmapped from memory--Windows won't allow
635 that. Instead, allow the consensus cache directory to grow larger,
636 to hold files that might need to stay around longer. Fixes bug
637 22752; bugfix on 0.3.1.1-alpha.
639 o Minor features (directory authority):
640 - Improve the message that authorities report to relays that present
641 RSA/Ed25519 keypairs that conflict with previously pinned keys.
644 o Minor features (geoip):
645 - Update geoip and geoip6 to the August 3 2017 Maxmind GeoLite2
648 o Minor features (testing):
649 - Add more tests for compression backend initialization. Closes
652 o Minor bugfixes (directory cache):
653 - Fix a memory leak when recovering space in the consensus cache.
654 Fixes bug 23139; bugfix on 0.3.1.1-alpha.
656 o Minor bugfixes (hidden service):
657 - Increase the number of circuits that a service is allowed to
658 open over a specific period of time. The value was lower than it
659 should be (8 vs 12) in the normal case of 3 introduction points.
660 Fixes bug 22159; bugfix on 0.3.0.5-rc.
661 - Fix a BUG warning during HSv3 descriptor decoding that could be
662 cause by a specially crafted descriptor. Fixes bug 23233; bugfix
663 on 0.3.0.1-alpha. Bug found by "haxxpop".
664 - Rate-limit the log messages if we exceed the maximum number of
665 allowed intro circuits. Fixes bug 22159; bugfix on 0.3.1.1-alpha.
667 o Minor bugfixes (logging, relay):
668 - Remove a forgotten debugging message when an introduction point
669 successfully establishes a hidden service prop224 circuit with
671 - Change three other log_warn() for an introduction point to
672 protocol warnings, because they can be failure from the network
673 and are not relevant to the operator. Fixes bug 23078; bugfix on
674 0.3.0.1-alpha and 0.3.0.2-alpha.
676 o Minor bugfixes (relay):
677 - When a relay is not running as a directory cache, it will no
678 longer generate compressed consensuses and consensus diff
679 information. Previously, this was a waste of disk and CPU. Fixes
680 bug 23275; bugfix on 0.3.1.1-alpha.
682 o Minor bugfixes (robustness, error handling):
683 - Improve our handling of the cases where OpenSSL encounters a
684 memory error while encoding keys and certificates. We haven't
685 observed these errors in the wild, but if they do happen, we now
686 detect and respond better. Fixes bug 19418; bugfix on all versions
687 of Tor. Reported by Guido Vranken.
689 o Minor bugfixes (stability):
690 - Avoid crashing on a double-free when unable to load or process an
691 included file. Fixes bug 23155; bugfix on 0.3.1.1-alpha. Found
692 with the clang static analyzer.
694 o Minor bugfixes (testing):
695 - Fix an undersized buffer in test-memwipe.c. Fixes bug 23291;
696 bugfix on 0.2.7.2-alpha. Found and patched by Ties Stuij.
697 - Port the hs_ntor handshake test to work correctly with recent
698 versions of the pysha3 module. Fixes bug 23071; bugfix
701 o Minor bugfixes (Windows service):
702 - When running as a Windows service, set the ID of the main thread
703 correctly. Failure to do so made us fail to send log messages to
704 the controller in 0.2.1.16-rc, slowed down controller event
705 delivery in 0.2.7.3-rc and later, and crash with an assertion
706 failure in 0.3.1.1-alpha. Fixes bug 23081; bugfix on 0.2.1.6-alpha.
707 Patch and diagnosis from "Vort".
710 Changes in version 0.3.0.10 - 2017-08-02
711 Tor 0.3.0.10 backports a collection of small-to-medium bugfixes
712 from the current Tor alpha series. OpenBSD users and TPROXY users
713 should upgrade; others are probably okay sticking with 0.3.0.9.
715 o Major features (build system, continuous integration, backport from 0.3.1.5-alpha):
716 - Tor's repository now includes a Travis Continuous Integration (CI)
717 configuration file (.travis.yml). This is meant to help new
718 developers and contributors who fork Tor to a Github repository be
719 better able to test their changes, and understand what we expect
720 to pass. To use this new build feature, you must fork Tor to your
721 Github account, then go into the "Integrations" menu in the
722 repository settings for your fork and enable Travis, then push
723 your changes. Closes ticket 22636.
725 o Major bugfixes (linux TPROXY support, backport from 0.3.1.1-alpha):
726 - Fix a typo that had prevented TPROXY-based transparent proxying
727 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
728 Patch from "d4fq0fQAgoJ".
730 o Major bugfixes (openbsd, denial-of-service, backport from 0.3.1.5-alpha):
731 - Avoid an assertion failure bug affecting our implementation of
732 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
733 handling of "0xbar" differs from what we had expected. Fixes bug
734 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
736 o Minor features (backport from 0.3.1.5-alpha):
737 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
740 o Minor bugfixes (bandwidth accounting, backport from 0.3.1.2-alpha):
741 - Roll over monthly accounting at the configured hour and minute,
742 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
743 Found by Andrey Karpov with PVS-Studio.
745 o Minor bugfixes (compilation warnings, backport from 0.3.1.5-alpha):
746 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug 22915;
747 bugfix on 0.2.8.1-alpha.
748 - Fix warnings when building with libscrypt and openssl scrypt
749 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
750 - When building with certain versions of the mingw C header files,
751 avoid float-conversion warnings when calling the C functions
752 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
755 o Minor bugfixes (compilation, mingw, backport from 0.3.1.1-alpha):
756 - Backport a fix for an "unused variable" warning that appeared
757 in some versions of mingw. Fixes bug 22838; bugfix on
760 o Minor bugfixes (coverity build support, backport from 0.3.1.5-alpha):
761 - Avoid Coverity build warnings related to our BUG() macro. By
762 default, Coverity treats BUG() as the Linux kernel does: an
763 instant abort(). We need to override that so our BUG() macro
764 doesn't prevent Coverity from analyzing functions that use it.
765 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
767 o Minor bugfixes (directory authority, backport from 0.3.1.1-alpha):
768 - When rejecting a router descriptor for running an obsolete version
769 of Tor without ntor support, warn about the obsolete tor version,
770 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
772 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.5-alpha):
773 - Avoid a sandbox failure when trying to re-bind to a socket and
774 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
776 o Minor bugfixes (unit tests, backport from 0.3.1.5-alpha)
777 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
778 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
781 Changes in version 0.3.1.5-alpha - 2017-08-01
782 Tor 0.3.1.5-alpha improves the performance of consensus diff
783 calculation, fixes a crash bug on older versions of OpenBSD, and fixes
784 several other bugs. If no serious bugs are found in this version, the
785 next version will be a release candidate.
787 This release also marks the end of support for the Tor 0.2.4.x,
788 0.2.6.x, and 0.2.7.x release series. Those releases will receive no
789 further bug or security fixes. Anyone still running or distributing
790 one of those versions should upgrade.
792 o Major features (build system, continuous integration):
793 - Tor's repository now includes a Travis Continuous Integration (CI)
794 configuration file (.travis.yml). This is meant to help new
795 developers and contributors who fork Tor to a Github repository be
796 better able to test their changes, and understand what we expect
797 to pass. To use this new build feature, you must fork Tor to your
798 Github account, then go into the "Integrations" menu in the
799 repository settings for your fork and enable Travis, then push
800 your changes. Closes ticket 22636.
802 o Major bugfixes (openbsd, denial-of-service):
803 - Avoid an assertion failure bug affecting our implementation of
804 inet_pton(AF_INET6) on certain OpenBSD systems whose strtol()
805 handling of "0xbar" differs from what we had expected. Fixes bug
806 22789; bugfix on 0.2.3.8-alpha. Also tracked as TROVE-2017-007.
808 o Major bugfixes (relay, performance):
809 - Perform circuit handshake operations at a higher priority than we
810 use for consensus diff creation and compression. This should
811 prevent circuits from starving when a relay or bridge receives a
812 new consensus, especially on lower-powered machines. Fixes bug
813 22883; bugfix on 0.3.1.1-alpha.
815 o Minor features (bridge authority):
816 - Add "fingerprint" lines to the networkstatus-bridges file produced
817 by bridge authorities. Closes ticket 22207.
819 o Minor features (directory cache, consensus diff):
820 - Add a new MaxConsensusAgeForDiffs option to allow directory cache
821 operators with low-resource environments to adjust the number of
822 consensuses they'll store and generate diffs from. Most cache
823 operators should leave it unchanged. Helps to work around
826 o Minor features (geoip):
827 - Update geoip and geoip6 to the July 4 2017 Maxmind GeoLite2
830 o Minor features (relay, performance):
831 - Always start relays with at least two worker threads, to prevent
832 priority inversion on slow tasks. Part of the fix for bug 22883.
833 - Allow background work to be queued with different priorities, so
834 that a big pile of slow low-priority jobs will not starve out
835 higher priority jobs. This lays the groundwork for a fix for
838 o Minor bugfixes (build system, rust):
839 - Fix a problem where Rust toolchains were not being found when
840 building without --enable-cargo-online-mode, due to setting the
841 $HOME environment variable instead of $CARGO_HOME. Fixes bug
842 22830; bugfix on 0.3.1.1-alpha. Fix by Chelsea Komlo.
844 o Minor bugfixes (compatibility, zstd):
845 - Write zstd epilogues correctly when the epilogue requires
846 reallocation of the output buffer, even with zstd 1.3.0.
847 (Previously, we worked on 1.2.0 and failed with 1.3.0). Fixes bug
848 22927; bugfix on 0.3.1.1-alpha.
850 o Minor bugfixes (compilation warnings):
851 - Suppress -Wdouble-promotion warnings with clang 4.0. Fixes bug
852 22915; bugfix on 0.2.8.1-alpha.
853 - Fix warnings when building with libscrypt and openssl scrypt
854 support on Clang. Fixes bug 22916; bugfix on 0.2.7.2-alpha.
855 - Compile correctly when both openssl 1.1.0 and libscrypt are
856 detected. Previously this would cause an error. Fixes bug 22892;
857 bugfix on 0.3.1.1-alpha.
858 - When building with certain versions of the mingw C header files,
859 avoid float-conversion warnings when calling the C functions
860 isfinite(), isnan(), and signbit(). Fixes bug 22801; bugfix
863 o Minor bugfixes (coverity build support):
864 - Avoid Coverity build warnings related to our BUG() macro. By
865 default, Coverity treats BUG() as the Linux kernel does: an
866 instant abort(). We need to override that so our BUG() macro
867 doesn't prevent Coverity from analyzing functions that use it.
868 Fixes bug 23030; bugfix on 0.2.9.1-alpha.
870 o Minor bugfixes (directory authority):
871 - When a directory authority rejects a descriptor or extrainfo with
872 a given digest, mark that digest as undownloadable, so that we do
873 not attempt to download it again over and over. We previously
874 tried to avoid downloading such descriptors by other means, but we
875 didn't notice if we accidentally downloaded one anyway. This
876 behavior became problematic in 0.2.7.2-alpha, when authorities
877 began pinning Ed25519 keys. Fixes bug 22349; bugfix
880 o Minor bugfixes (error reporting, windows):
881 - When formatting Windows error messages, use the English format to
882 avoid codepage issues. Fixes bug 22520; bugfix on 0.1.2.8-alpha.
885 o Minor bugfixes (file limits, osx):
886 - When setting the maximum number of connections allowed by the OS,
887 always allow some extra file descriptors for other files. Fixes
888 bug 22797; bugfix on 0.2.0.10-alpha.
890 o Minor bugfixes (linux seccomp2 sandbox):
891 - Avoid a sandbox failure when trying to re-bind to a socket and
892 mark it as IPv6-only. Fixes bug 20247; bugfix on 0.2.5.1-alpha.
894 o Minor bugfixes (memory leaks):
895 - Fix a small memory leak when validating a configuration that uses
896 two or more AF_UNIX sockets for the same port type. Fixes bug
897 23053; bugfix on 0.2.6.3-alpha. This is CID 1415725.
899 o Minor bugfixes (unit tests):
900 - test_consdiff_base64cmp would fail on OS X because while OS X
901 follows the standard of (less than zero/zero/greater than zero),
902 it doesn't follow the convention of (-1/0/+1). Make the test
903 comply with the standard. Fixes bug 22870; bugfix on 0.3.1.1-alpha.
904 - Fix a memory leak in the link-handshake/certs_ok_ed25519 test.
905 Fixes bug 22803; bugfix on 0.3.0.1-alpha.
908 Changes in version 0.3.1.4-alpha - 2017-06-29
909 Tor 0.3.1.4-alpha fixes a path selection bug that would allow a client
910 to use a guard that was in the same network family as a chosen exit
911 relay. This is a security regression; all clients running earlier
912 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9
915 This release also fixes several other bugs introduced in 0.3.0.x
916 and 0.3.1.x, including others that can affect bandwidth usage
920 - To build with zstd and lzma support, Tor now requires the
921 pkg-config tool at build time. (This requirement was new in
922 0.3.1.1-alpha, but was not noted at the time. Noting it here to
925 o Major bugfixes (path selection, security):
926 - When choosing which guard to use for a circuit, avoid the exit's
927 family along with the exit itself. Previously, the new guard
928 selection logic avoided the exit, but did not consider its family.
929 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
930 006 and CVE-2017-0377.
932 o Major bugfixes (compression, zstd):
933 - Correctly detect a full buffer when decompressing a large zstd-
934 compressed input. Previously, we would sometimes treat a full
935 buffer as an error. Fixes bug 22628; bugfix on 0.3.1.1-alpha.
937 o Major bugfixes (directory protocol):
938 - Ensure that we send "304 Not modified" as HTTP status code when a
939 client is attempting to fetch a consensus or consensus diff, and
940 the best one we can send them is one they already have. Fixes bug
941 22702; bugfix on 0.3.1.1-alpha.
943 o Major bugfixes (entry guards):
944 - When starting with an old consensus, do not add new entry guards
945 unless the consensus is "reasonably live" (under 1 day old). Fixes
946 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
948 o Minor features (bug mitigation, diagnostics, logging):
949 - Avoid an assertion failure, and log a better error message, when
950 unable to remove a file from the consensus cache on Windows.
951 Attempts to mitigate and diagnose bug 22752.
953 o Minor features (geoip):
954 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
957 o Minor bugfixes (compression):
958 - When compressing or decompressing a buffer, check for a failure to
959 create a compression object. Fixes bug 22626; bugfix
961 - When decompressing a buffer, check for extra data after the end of
962 the compressed data. Fixes bug 22629; bugfix on 0.3.1.1-alpha.
963 - When decompressing an object received over an anonymous directory
964 connection, if we have already decompressed it using an acceptable
965 compression method, do not reject it for looking like an
966 unacceptable compression method. Fixes part of bug 22670; bugfix
968 - When serving directory votes compressed with zlib, do not claim to
969 have compressed them with zstd. Fixes bug 22669; bugfix
971 - When spooling compressed data to an output buffer, don't try to
972 spool more data when there is no more data to spool and we are not
973 trying to flush the input. Previously, we would sometimes launch
974 compression requests with nothing to do, which interferes with our
975 22672 checks. Fixes bug 22719; bugfix on 0.2.0.16-alpha.
977 o Minor bugfixes (defensive programming):
978 - Detect and break out of infinite loops in our compression code. We
979 don't think that any such loops exist now, but it's best to be
980 safe. Closes ticket 22672.
981 - Fix a memset() off the end of an array when packing cells. This
982 bug should be harmless in practice, since the corrupted bytes are
983 still in the same structure, and are always padding bytes,
984 ignored, or immediately overwritten, depending on compiler
985 behavior. Nevertheless, because the memset()'s purpose is to make
986 sure that any other cell-handling bugs can't expose bytes to the
987 network, we need to fix it. Fixes bug 22737; bugfix on
988 0.2.4.11-alpha. Fixes CID 1401591.
990 o Minor bugfixes (linux seccomp2 sandbox):
991 - Permit the fchmod system call, to avoid crashing on startup when
992 starting with the seccomp2 sandbox and an unexpected set of
993 permissions on the data directory or its contents. Fixes bug
994 22516; bugfix on 0.2.5.4-alpha.
995 - Fix a crash in the LZMA module, when the sandbox was enabled, and
996 liblzma would allocate more than 16 MB of memory. We solve this by
997 bumping the mprotect() limit in the sandbox module from 16 MB to
998 20 MB. Fixes bug 22751; bugfix on 0.3.1.1-alpha.
1000 o Minor bugfixes (logging):
1001 - When decompressing, do not warn if we fail to decompress using a
1002 compression method that we merely guessed. Fixes part of bug
1003 22670; bugfix on 0.1.1.14-alpha.
1004 - When decompressing, treat mismatch between content-encoding and
1005 actual compression type as a protocol warning. Fixes part of bug
1006 22670; bugfix on 0.1.1.9-alpha.
1007 - Downgrade "assigned_to_cpuworker failed" message to info-level
1008 severity. In every case that can reach it, either a better warning
1009 has already been logged, or no warning is warranted. Fixes bug
1010 22356; bugfix on 0.2.6.3-alpha.
1011 - Demote a warn that was caused by libevent delays to info if
1012 netflow padding is less than 4.5 seconds late, or to notice
1013 if it is more (4.5 seconds is the amount of time that a netflow
1014 record might be emitted after, if we chose the maximum timeout).
1015 Fixes bug 22212; bugfix on 0.3.1.1-alpha.
1017 o Minor bugfixes (process behavior):
1018 - When exiting because of an error, always exit with a nonzero exit
1019 status. Previously, we would fail to report an error in our exit
1020 status in cases related to __OwningControllerProcess failure,
1021 lockfile contention, and Ed25519 key initialization. Fixes bug
1022 22720; bugfix on versions 0.2.1.6-alpha, 0.2.2.28-beta, and
1023 0.2.7.2-alpha respectively. Reported by "f55jwk4f"; patch
1027 - Add a manpage description for the key-pinning-journal file. Closes
1029 - Correctly note that bandwidth accounting values are stored in the
1030 state file, and the bw_accounting file is now obsolete. Closes
1032 - Document more of the files in the Tor data directory, including
1033 cached-extrainfo, secret_onion_key{,_ntor}.old, hidserv-stats,
1034 approved-routers, sr-random, and diff-cache. Found while fixing
1038 Changes in version 0.3.0.9 - 2017-06-29
1039 Tor 0.3.0.9 fixes a path selection bug that would allow a client
1040 to use a guard that was in the same network family as a chosen exit
1041 relay. This is a security regression; all clients running earlier
1042 versions of 0.3.0.x or 0.3.1.x should upgrade to 0.3.0.9 or
1045 This release also backports several other bugfixes from the 0.3.1.x
1048 o Major bugfixes (path selection, security, backport from 0.3.1.4-alpha):
1049 - When choosing which guard to use for a circuit, avoid the exit's
1050 family along with the exit itself. Previously, the new guard
1051 selection logic avoided the exit, but did not consider its family.
1052 Fixes bug 22753; bugfix on 0.3.0.1-alpha. Tracked as TROVE-2017-
1053 006 and CVE-2017-0377.
1055 o Major bugfixes (entry guards, backport from 0.3.1.1-alpha):
1056 - Don't block bootstrapping when a primary bridge is offline and we
1057 can't get its descriptor. Fixes bug 22325; fixes one case of bug
1058 21969; bugfix on 0.3.0.3-alpha.
1060 o Major bugfixes (entry guards, backport from 0.3.1.4-alpha):
1061 - When starting with an old consensus, do not add new entry guards
1062 unless the consensus is "reasonably live" (under 1 day old). Fixes
1063 one root cause of bug 22400; bugfix on 0.3.0.1-alpha.
1065 o Minor features (geoip):
1066 - Update geoip and geoip6 to the June 8 2017 Maxmind GeoLite2
1069 o Minor bugfixes (voting consistency, backport from 0.3.1.1-alpha):
1070 - Reject version numbers with non-numeric prefixes (such as +, -, or
1071 whitespace). Disallowing whitespace prevents differential version
1072 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1073 and part of 21508; bugfix on 0.0.8pre1.
1075 o Minor bugfixes (linux seccomp2 sandbox, backport from 0.3.1.4-alpha):
1076 - Permit the fchmod system call, to avoid crashing on startup when
1077 starting with the seccomp2 sandbox and an unexpected set of
1078 permissions on the data directory or its contents. Fixes bug
1079 22516; bugfix on 0.2.5.4-alpha.
1081 o Minor bugfixes (defensive programming, backport from 0.3.1.4-alpha):
1082 - Fix a memset() off the end of an array when packing cells. This
1083 bug should be harmless in practice, since the corrupted bytes are
1084 still in the same structure, and are always padding bytes,
1085 ignored, or immediately overwritten, depending on compiler
1086 behavior. Nevertheless, because the memset()'s purpose is to make
1087 sure that any other cell-handling bugs can't expose bytes to the
1088 network, we need to fix it. Fixes bug 22737; bugfix on
1089 0.2.4.11-alpha. Fixes CID 1401591.
1092 Changes in version 0.3.1.3-alpha - 2017-06-08
1093 Tor 0.3.1.3-alpha fixes a pair of bugs that would allow an attacker to
1094 remotely crash a hidden service with an assertion failure. Anyone
1095 running a hidden service should upgrade to this version, or to some
1096 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
1098 Tor 0.3.1.3-alpha also includes fixes for several key management bugs
1099 that sometimes made relays unreliable, as well as several other
1100 bugfixes described below.
1102 o Major bugfixes (hidden service, relay, security):
1103 - Fix a remotely triggerable assertion failure when a hidden service
1104 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
1105 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
1106 - Fix a remotely triggerable assertion failure caused by receiving a
1107 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1108 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1111 o Major bugfixes (relay, link handshake):
1112 - When performing the v3 link handshake on a TLS connection, report
1113 that we have the x509 certificate that we actually used on that
1114 connection, even if we have changed certificates since that
1115 connection was first opened. Previously, we would claim to have
1116 used our most recent x509 link certificate, which would sometimes
1117 make the link handshake fail. Fixes one case of bug 22460; bugfix
1120 o Major bugfixes (relays, key management):
1121 - Regenerate link and authentication certificates whenever the key
1122 that signs them changes; also, regenerate link certificates
1123 whenever the signed key changes. Previously, these processes were
1124 only weakly coupled, and we relays could (for minutes to hours)
1125 wind up with an inconsistent set of keys and certificates, which
1126 other relays would not accept. Fixes two cases of bug 22460;
1127 bugfix on 0.3.0.1-alpha.
1128 - When sending an Ed25519 signing->link certificate in a CERTS cell,
1129 send the certificate that matches the x509 certificate that we
1130 used on the TLS connection. Previously, there was a race condition
1131 if the TLS context rotated after we began the TLS handshake but
1132 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
1135 o Major bugfixes (torrc, crash):
1136 - Fix a crash bug when using %include in torrc. Fixes bug 22417;
1137 bugfix on 0.3.1.1-alpha. Patch by Daniel Pinto.
1139 o Minor features (code style):
1140 - Add "Falls through" comments to our codebase, in order to silence
1141 GCC 7's -Wimplicit-fallthrough warnings. Patch from Andreas
1142 Stieger. Closes ticket 22446.
1144 o Minor features (diagnostic):
1145 - Add logging messages to try to diagnose a rare bug that seems to
1146 generate RSA->Ed25519 cross-certificates dated in the 1970s. We
1147 think this is happening because of incorrect system clocks, but
1148 we'd like to know for certain. Diagnostic for bug 22466.
1150 o Minor bugfixes (correctness):
1151 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1152 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1154 o Minor bugfixes (directory protocol):
1155 - Check for libzstd >= 1.1, because older versions lack the
1156 necessary streaming API. Fixes bug 22413; bugfix on 0.3.1.1-alpha.
1158 o Minor bugfixes (link handshake):
1159 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
1160 months, and regenerate it when it is within one month of expiring.
1161 Previously, we had generated this certificate at startup with a
1162 ten-year lifetime, but that could lead to weird behavior when Tor
1163 was started with a grossly inaccurate clock. Mitigates bug 22466;
1164 mitigation on 0.3.0.1-alpha.
1166 o Minor bugfixes (storage directories):
1167 - Always check for underflows in the cached storage directory usage.
1168 If the usage does underflow, re-calculate it. Also, avoid a
1169 separate underflow when the usage is not known. Fixes bug 22424;
1170 bugfix on 0.3.1.1-alpha.
1172 o Minor bugfixes (unit tests):
1173 - The unit tests now pass on systems where localhost is misconfigured
1174 to some IPv4 address other than 127.0.0.1. Fixes bug 6298; bugfix
1178 - Clarify the manpage for the (deprecated) torify script. Closes
1181 Changes in version 0.3.0.8 - 2017-06-08
1182 Tor 0.3.0.8 fixes a pair of bugs that would allow an attacker to
1183 remotely crash a hidden service with an assertion failure. Anyone
1184 running a hidden service should upgrade to this version, or to some
1185 other version with fixes for TROVE-2017-004 and TROVE-2017-005.
1187 Tor 0.3.0.8 also includes fixes for several key management bugs
1188 that sometimes made relays unreliable, as well as several other
1189 bugfixes described below.
1191 o Major bugfixes (hidden service, relay, security, backport
1192 from 0.3.1.3-alpha):
1193 - Fix a remotely triggerable assertion failure when a hidden service
1194 handles a malformed BEGIN cell. Fixes bug 22493, tracked as
1195 TROVE-2017-004 and as CVE-2017-0375; bugfix on 0.3.0.1-alpha.
1196 - Fix a remotely triggerable assertion failure caused by receiving a
1197 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1198 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1201 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
1202 - When performing the v3 link handshake on a TLS connection, report
1203 that we have the x509 certificate that we actually used on that
1204 connection, even if we have changed certificates since that
1205 connection was first opened. Previously, we would claim to have
1206 used our most recent x509 link certificate, which would sometimes
1207 make the link handshake fail. Fixes one case of bug 22460; bugfix
1210 o Major bugfixes (relays, key management, backport from 0.3.1.3-alpha):
1211 - Regenerate link and authentication certificates whenever the key
1212 that signs them changes; also, regenerate link certificates
1213 whenever the signed key changes. Previously, these processes were
1214 only weakly coupled, and we relays could (for minutes to hours)
1215 wind up with an inconsistent set of keys and certificates, which
1216 other relays would not accept. Fixes two cases of bug 22460;
1217 bugfix on 0.3.0.1-alpha.
1218 - When sending an Ed25519 signing->link certificate in a CERTS cell,
1219 send the certificate that matches the x509 certificate that we
1220 used on the TLS connection. Previously, there was a race condition
1221 if the TLS context rotated after we began the TLS handshake but
1222 before we sent the CERTS cell. Fixes a case of bug 22460; bugfix
1225 o Major bugfixes (hidden service v3, backport from 0.3.1.1-alpha):
1226 - Stop rejecting v3 hidden service descriptors because their size
1227 did not match an old padding rule. Fixes bug 22447; bugfix on
1230 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
1231 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1232 December 2016 (of which ~126 were still functional) with a list of
1233 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1234 2017. Resolves ticket 21564.
1236 o Minor bugfixes (configuration, backport from 0.3.1.1-alpha):
1237 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
1238 bug 22252; bugfix on 0.2.9.3-alpha.
1240 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
1241 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1242 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1244 o Minor bugfixes (link handshake, backport from 0.3.1.3-alpha):
1245 - Lower the lifetime of the RSA->Ed25519 cross-certificate to six
1246 months, and regenerate it when it is within one month of expiring.
1247 Previously, we had generated this certificate at startup with a
1248 ten-year lifetime, but that could lead to weird behavior when Tor
1249 was started with a grossly inaccurate clock. Mitigates bug 22466;
1250 mitigation on 0.3.0.1-alpha.
1252 o Minor bugfixes (memory leak, directory authority, backport from
1254 - When directory authorities reject a router descriptor due to
1255 keypinning, free the router descriptor rather than leaking the
1256 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
1259 Changes in version 0.2.9.11 - 2017-06-08
1260 Tor 0.2.9.11 backports a fix for a bug that would allow an attacker to
1261 remotely crash a hidden service with an assertion failure. Anyone
1262 running a hidden service should upgrade to this version, or to some
1263 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1264 are not affected by TROVE-2017-004.)
1266 Tor 0.2.9.11 also backports fixes for several key management bugs
1267 that sometimes made relays unreliable, as well as several other
1268 bugfixes described below.
1270 o Major bugfixes (hidden service, relay, security, backport
1271 from 0.3.1.3-alpha):
1272 - Fix a remotely triggerable assertion failure caused by receiving a
1273 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1274 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1277 o Major bugfixes (relay, link handshake, backport from 0.3.1.3-alpha):
1278 - When performing the v3 link handshake on a TLS connection, report
1279 that we have the x509 certificate that we actually used on that
1280 connection, even if we have changed certificates since that
1281 connection was first opened. Previously, we would claim to have
1282 used our most recent x509 link certificate, which would sometimes
1283 make the link handshake fail. Fixes one case of bug 22460; bugfix
1286 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
1287 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1288 December 2016 (of which ~126 were still functional) with a list of
1289 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1290 2017. Resolves ticket 21564.
1292 o Minor features (future-proofing, backport from 0.3.0.7):
1293 - Tor no longer refuses to download microdescriptors or descriptors if
1294 they are listed as "published in the future". This change will
1295 eventually allow us to stop listing meaningful "published" dates
1296 in microdescriptor consensuses, and thereby allow us to reduce the
1297 resources required to download consensus diffs by over 50%.
1298 Implements part of ticket 21642; implements part of proposal 275.
1300 o Minor features (directory authorities, backport from 0.3.0.4-rc)
1301 - Directory authorities now reject relays running versions
1302 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
1303 suffer from bug 20499 and don't keep their consensus cache
1304 up-to-date. Resolves ticket 20509.
1306 o Minor features (geoip):
1307 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1310 o Minor bugfixes (control port, backport from 0.3.0.6):
1311 - The GETINFO extra-info/digest/<digest> command was broken because
1312 of a wrong base16 decode return value check, introduced when
1313 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
1315 o Minor bugfixes (correctness, backport from 0.3.1.3-alpha):
1316 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1317 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1319 o Minor bugfixes (Linux seccomp2 sandbox, backport from 0.3.0.7):
1320 - The getpid() system call is now permitted under the Linux seccomp2
1321 sandbox, to avoid crashing with versions of OpenSSL (and other
1322 libraries) that attempt to learn the process's PID by using the
1323 syscall rather than the VDSO code. Fixes bug 21943; bugfix
1326 o Minor bugfixes (memory leak, directory authority, backport
1327 from 0.3.1.2-alpha):
1328 - When directory authorities reject a router descriptor due to
1329 keypinning, free the router descriptor rather than leaking the
1330 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
1332 Changes in version 0.2.8.14 - 2017-06-08
1333 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
1334 remotely crash a hidden service with an assertion failure. Anyone
1335 running a hidden service should upgrade to this version, or to some
1336 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1337 are not affected by TROVE-2017-004.)
1339 o Major bugfixes (hidden service, relay, security):
1340 - Fix a remotely triggerable assertion failure caused by receiving a
1341 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1342 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1345 o Minor features (geoip):
1346 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1349 o Minor features (fallback directory list, backport from 0.3.1.3-alpha):
1350 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1351 December 2016 (of which ~126 were still functional) with a list of
1352 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1353 2017. Resolves ticket 21564.
1355 o Minor bugfixes (correctness):
1356 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1357 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1359 Changes in version 0.2.7.8 - 2017-06-08
1360 Tor 0.2.7.8 backports a fix for a bug that would allow an attacker to
1361 remotely crash a hidden service with an assertion failure. Anyone
1362 running a hidden service should upgrade to this version, or to some
1363 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1364 are not affected by TROVE-2017-004.)
1366 o Major bugfixes (hidden service, relay, security):
1367 - Fix a remotely triggerable assertion failure caused by receiving a
1368 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1369 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1372 o Minor features (geoip):
1373 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1376 o Minor bugfixes (correctness):
1377 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1378 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1381 Changes in version 0.2.6.12 - 2017-06-08
1382 Tor 0.2.6.12 backports a fix for a bug that would allow an attacker to
1383 remotely crash a hidden service with an assertion failure. Anyone
1384 running a hidden service should upgrade to this version, or to some
1385 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1386 are not affected by TROVE-2017-004.)
1388 o Major bugfixes (hidden service, relay, security):
1389 - Fix a remotely triggerable assertion failure caused by receiving a
1390 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1391 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1394 o Minor features (geoip):
1395 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1398 o Minor bugfixes (correctness):
1399 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1400 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1402 Changes in version 0.2.5.14 - 2017-06-08
1403 Tor 0.2.5.14 backports a fix for a bug that would allow an attacker to
1404 remotely crash a hidden service with an assertion failure. Anyone
1405 running a hidden service should upgrade to this version, or to some
1406 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1407 are not affected by TROVE-2017-004.)
1409 o Major bugfixes (hidden service, relay, security):
1410 - Fix a remotely triggerable assertion failure caused by receiving a
1411 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1412 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1415 o Minor features (geoip):
1416 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1419 o Minor bugfixes (correctness):
1420 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1421 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1423 Changes in version 0.2.4.29 - 2017-06-08
1424 Tor 0.2.4.29 backports a fix for a bug that would allow an attacker to
1425 remotely crash a hidden service with an assertion failure. Anyone
1426 running a hidden service should upgrade to this version, or to some
1427 other version with fixes for TROVE-2017-005. (Versions before 0.3.0
1428 are not affected by TROVE-2017-004.)
1430 o Major bugfixes (hidden service, relay, security):
1431 - Fix a remotely triggerable assertion failure caused by receiving a
1432 BEGIN_DIR cell on a hidden service rendezvous circuit. Fixes bug
1433 22494, tracked as TROVE-2017-005 and CVE-2017-0376; bugfix
1436 o Minor features (geoip):
1437 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1440 o Minor bugfixes (correctness):
1441 - Avoid undefined behavior when parsing IPv6 entries from the geoip6
1442 file. Fixes bug 22490; bugfix on 0.2.4.6-alpha.
1445 Changes in version 0.3.1.2-alpha - 2017-05-26
1446 Tor 0.3.1.2-alpha is the second release in the 0.3.1.x series. It
1447 fixes a few bugs found while testing 0.3.1.1-alpha, including a
1448 memory corruption bug that affected relay stability.
1450 o Major bugfixes (crash, relay):
1451 - Fix a memory-corruption bug in relays that set MyFamily.
1452 Previously, they would double-free MyFamily elements when making
1453 the next descriptor or when changing their configuration. Fixes
1454 bug 22368; bugfix on 0.3.1.1-alpha.
1456 o Minor bugfixes (logging):
1457 - Log a better message when a directory authority replies to an
1458 upload with an unexpected status code. Fixes bug 11121; bugfix
1461 o Minor bugfixes (memory leak, directory authority):
1462 - When directory authorities reject a router descriptor due to
1463 keypinning, free the router descriptor rather than leaking the
1464 memory. Fixes bug 22370; bugfix on 0.2.7.2-alpha.
1467 Changes in version 0.3.1.1-alpha - 2017-05-22
1468 Tor 0.3.1.1-alpha is the first release in the 0.3.1.x series. It
1469 reduces the bandwidth usage for Tor's directory protocol, adds some
1470 basic padding to resist netflow-based traffic analysis and to serve as
1471 the basis of other padding in the future, and adds rust support to the
1474 It also contains numerous other small features and improvements to
1475 security, correctness, and performance.
1477 Below are the changes since 0.3.0.7.
1479 o Major features (directory protocol):
1480 - Tor relays and authorities can now serve clients an abbreviated
1481 version of the consensus document, containing only the changes
1482 since an older consensus document that the client holds. Clients
1483 now request these documents when available. When both client and
1484 server use this new protocol, they will use far less bandwidth (up
1485 to 94% less) to keep the client's consensus up-to-date. Implements
1486 proposal 140; closes ticket 13339. Based on work by Daniel MartÃ.
1487 - Tor can now compress directory traffic with lzma or with zstd
1488 compression algorithms, which can deliver better bandwidth
1489 performance. Because lzma is computationally expensive, it's only
1490 used for documents that can be compressed once and served many
1491 times. Support for these algorithms requires that tor is built
1492 with the libzstd and/or liblzma libraries available. Implements
1493 proposal 278; closes ticket 21662.
1494 - Relays now perform the more expensive compression operations, and
1495 consensus diff generation, in worker threads. This separation
1496 avoids delaying the main thread when a new consensus arrives.
1498 o Major features (experimental):
1499 - Tor can now build modules written in Rust. To turn this on, pass
1500 the "--enable-rust" flag to the configure script. It's not time to
1501 get excited yet: currently, there is no actual Rust functionality
1502 beyond some simple glue code, and a notice at startup to tell you
1503 that Rust is running. Still, we hope that programmers and
1504 packagers will try building Tor with Rust support, so that we can
1505 find issues and solve portability problems. Closes ticket 22106.
1507 o Major features (traffic analysis resistance):
1508 - Connections between clients and relays now send a padding cell in
1509 each direction every 1.5 to 9.5 seconds (tunable via consensus
1510 parameters). This padding will not resist specialized
1511 eavesdroppers, but it should be enough to make many ISPs' routine
1512 network flow logging less useful in traffic analysis against
1515 Padding is negotiated using Tor's link protocol, so both relays
1516 and clients must upgrade for this to take effect. Clients may
1517 still send padding despite the relay's version by setting
1518 ConnectionPadding 1 in torrc, and may disable padding by setting
1519 ConnectionPadding 0 in torrc. Padding may be minimized for mobile
1520 users with the torrc option ReducedConnectionPadding. Implements
1521 Proposal 251 and Section 2 of Proposal 254; closes ticket 16861.
1522 - Relays will publish 24 hour totals of padding and non-padding cell
1523 counts to their extra-info descriptors, unless PaddingStatistics 0
1524 is set in torrc. These 24 hour totals are also rounded to
1527 o Major bugfixes (connection usage):
1528 - We use NETINFO cells to try to determine if both relays involved
1529 in a connection will agree on the canonical status of that
1530 connection. We prefer the connections where this is the case for
1531 extend cells, and try to close connections where relays disagree
1532 on their canonical status early. Also, we now prefer the oldest
1533 valid connection for extend cells. These two changes should reduce
1534 the number of long-term connections that are kept open between
1535 relays. Fixes bug 17604; bugfix on 0.2.5.5-alpha.
1536 - Relays now log hourly statistics (look for
1537 "channel_check_for_duplicates" lines) on the total number of
1538 connections to other relays. If the number of connections per
1539 relay is unexpectedly large, this log message is at notice level.
1540 Otherwise it is at info.
1542 o Major bugfixes (entry guards):
1543 - Don't block bootstrapping when a primary bridge is offline and we
1544 can't get its descriptor. Fixes bug 22325; fixes one case of bug
1545 21969; bugfix on 0.3.0.3-alpha.
1547 o Major bugfixes (linux TPROXY support):
1548 - Fix a typo that had prevented TPROXY-based transparent proxying
1549 from working under Linux. Fixes bug 18100; bugfix on 0.2.6.3-alpha.
1550 Patch from "d4fq0fQAgoJ".
1552 o Minor features (security, windows):
1553 - Enable a couple of pieces of Windows hardening: one
1554 (HeapEnableTerminationOnCorruption) that has been on-by-default
1555 since Windows 8, and unavailable before Windows 7; and one
1556 (PROCESS_DEP_DISABLE_ATL_THUNK_EMULATION) which we believe doesn't
1557 affect us, but shouldn't do any harm. Closes ticket 21953.
1559 o Minor features (config options):
1560 - Allow "%include" directives in torrc configuration files. These
1561 directives import the settings from other files, or from all the
1562 files in a directory. Closes ticket 1922. Code by Daniel Pinto.
1563 - Make SAVECONF return an error when overwriting a torrc that has
1564 includes. Using SAVECONF with the FORCE option will allow it to
1565 overwrite torrc even if includes are used. Related to ticket 1922.
1566 - Add "GETINFO config-can-saveconf" to tell controllers if SAVECONF
1567 will work without the FORCE option. Related to ticket 1922.
1569 o Minor features (controller):
1570 - Warn the first time that a controller requests data in the long-
1571 deprecated 'GETINFO network-status' format. Closes ticket 21703.
1573 o Minor features (defaults):
1574 - The default value for UseCreateFast is now 0: clients which
1575 haven't yet received a consensus document will now use a proper
1576 ntor handshake to talk to their directory servers whenever they
1577 can. Closes ticket 21407.
1578 - Onion key rotation and expiry intervals are now defined as a
1579 network consensus parameter, per proposal 274. The default
1580 lifetime of an onion key is increased from 7 to 28 days. Old onion
1581 keys will expire after 7 days by default. This change will make
1582 consensus diffs much smaller, and save significant bandwidth.
1583 Closes ticket 21641.
1585 o Minor features (fallback directory list):
1586 - Update the fallback directory mirror whitelist and blacklist based
1587 on operator emails. Closes task 21121.
1588 - Replace the 177 fallbacks originally introduced in Tor 0.2.9.8 in
1589 December 2016 (of which ~126 were still functional) with a list of
1590 151 fallbacks (32 new, 119 unchanged, 58 removed) generated in May
1591 2017. Resolves ticket 21564.
1593 o Minor features (hidden services, logging):
1594 - Log a message when a hidden service descriptor has fewer
1595 introduction points than specified in
1596 HiddenServiceNumIntroductionPoints. Closes tickets 21598.
1597 - Log a message when a hidden service reaches its introduction point
1598 circuit limit, and when that limit is reset. Follow up to ticket
1599 21594; closes ticket 21622.
1600 - Warn user if multiple entries in EntryNodes and at least one
1601 HiddenService are used together. Pinning EntryNodes along with a
1602 hidden service can be possibly harmful; for instance see ticket
1603 14917 or 21155. Closes ticket 21155.
1605 o Minor features (linux seccomp2 sandbox):
1606 - We now have a document storage backend compatible with the Linux
1607 seccomp2 sandbox. This backend is used for consensus documents and
1608 diffs between them; in the long term, we'd like to use it for
1609 unparseable directory material too. Closes ticket 21645
1610 - Increase the maximum allowed size passed to mprotect(PROT_WRITE)
1611 from 1MB to 16MB. This was necessary with the glibc allocator in
1612 order to allow worker threads to allocate more memory -- which in
1613 turn is necessary because of our new use of worker threads for
1614 compression. Closes ticket 22096.
1616 o Minor features (logging):
1617 - Log files are no longer created world-readable by default.
1618 (Previously, most distributors would store the logs in a non-
1619 world-readable location to prevent inappropriate access. This
1620 change is an extra precaution.) Closes ticket 21729; patch
1623 o Minor features (performance):
1624 - Our Keccak (SHA-3) implementation now accesses memory more
1625 efficiently, especially on little-endian systems. Closes
1627 - Add an O(1) implementation of channel_find_by_global_id(), to
1628 speed some controller functions.
1630 o Minor features (relay, configuration):
1631 - The MyFamily option may now be repeated as many times as desired,
1632 for relays that want to configure large families. Closes ticket
1633 4998; patch by Daniel Pinto.
1635 o Minor features (safety):
1636 - Add an explicit check to extrainfo_parse_entry_from_string() for
1637 NULL inputs. We don't believe this can actually happen, but it may
1638 help silence a warning from the Clang analyzer. Closes
1641 o Minor features (testing):
1642 - Add a "--disable-memory-sentinels" feature to help with fuzzing.
1643 When Tor is compiled with this option, we disable a number of
1644 redundant memory-safety failsafes that are intended to stop bugs
1645 from becoming security issues. This makes it easier to hunt for
1646 bugs that would be security issues without the failsafes turned
1647 on. Closes ticket 21439.
1648 - Add a general event-tracing instrumentation support to Tor. This
1649 subsystem will enable developers and researchers to add fine-
1650 grained instrumentation to their Tor instances, for use when
1651 examining Tor network performance issues. There are no trace
1652 events yet, and event-tracing is off by default unless enabled at
1653 compile time. Implements ticket 13802.
1654 - Improve our version parsing tests: add tests for typical version
1655 components, add tests for invalid versions, including numeric
1656 range and non-numeric prefixes. Unit tests 21278, 21450, and
1657 21507. Partially implements 21470.
1659 o Minor bugfixes (bandwidth accounting):
1660 - Roll over monthly accounting at the configured hour and minute,
1661 rather than always at 00:00. Fixes bug 22245; bugfix on 0.0.9rc1.
1662 Found by Andrey Karpov with PVS-Studio.
1664 o Minor bugfixes (code correctness):
1665 - Accurately identify client connections by their lack of peer
1666 authentication. This means that we bail out earlier if asked to
1667 extend to a client. Follow-up to 21407. Fixes bug 21406; bugfix
1670 o Minor bugfixes (configuration):
1671 - Do not crash when starting with LearnCircuitBuildTimeout 0. Fixes
1672 bug 22252; bugfix on 0.2.9.3-alpha.
1674 o Minor bugfixes (connection lifespan):
1675 - Allow more control over how long TLS connections are kept open:
1676 unify CircuitIdleTimeout and PredictedPortsRelevanceTime into a
1677 single option called CircuitsAvailableTimeout. Also, allow the
1678 consensus to control the default values for both this preference
1679 and the lifespan of relay-to-relay connections. Fixes bug 17592;
1680 bugfix on 0.2.5.5-alpha.
1681 - Increase the initial circuit build timeout testing frequency, to
1682 help ensure that ReducedConnectionPadding clients finish learning
1683 a timeout before their orconn would expire. The initial testing
1684 rate was set back in the days of TAP and before the Tor Browser
1685 updater, when we had to be much more careful about new clients
1686 making lots of circuits. With this change, a circuit build timeout
1687 is learned in about 15-20 minutes, instead of 100-120 minutes.
1689 o Minor bugfixes (controller):
1690 - GETINFO onions/current and onions/detached no longer respond with
1691 551 on empty lists. Fixes bug 21329; bugfix on 0.2.7.1-alpha.
1692 - Trigger HS descriptor events on the control port when the client
1693 fails to pick a hidden service directory for a hidden service.
1694 This can happen if all the hidden service directories are in
1695 ExcludeNodes, or they have all been queried within the last 15
1696 minutes. Fixes bug 22042; bugfix on 0.2.5.2-alpha.
1698 o Minor bugfixes (directory authority):
1699 - When rejecting a router descriptor for running an obsolete version
1700 of Tor without ntor support, warn about the obsolete tor version,
1701 not the missing ntor key. Fixes bug 20270; bugfix on 0.2.9.3-alpha.
1702 - Prevent the shared randomness subsystem from asserting when
1703 initialized by a bridge authority with an incomplete configuration
1704 file. Fixes bug 21586; bugfix on 0.2.9.8.
1706 o Minor bugfixes (exit-side DNS):
1707 - Fix an untriggerable assertion that checked the output of a
1708 libevent DNS error, so that the assertion actually behaves as
1709 expected. Fixes bug 22244; bugfix on 0.2.0.20-rc. Found by Andrey
1710 Karpov using PVS-Studio.
1712 o Minor bugfixes (fallback directories):
1713 - Make the usage example in updateFallbackDirs.py actually work, and
1714 explain what it does. Fixes bug 22270; bugfix on 0.3.0.3-alpha.
1715 - Decrease the guard flag average required to be a fallback. This
1716 allows us to keep relays that have their guard flag removed when
1717 they restart. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
1718 - Decrease the minimum number of fallbacks to 100. Fixes bug 20913;
1719 bugfix on 0.2.8.1-alpha.
1720 - Make sure fallback directory mirrors have the same address, port,
1721 and relay identity key for at least 30 days before they are
1722 selected. Fixes bug 20913; bugfix on 0.2.8.1-alpha.
1724 o Minor bugfixes (hidden services):
1725 - Stop printing a cryptic warning when a hidden service gets a
1726 request to connect to a virtual port that it hasn't configured.
1727 Fixes bug 16706; bugfix on 0.2.6.3-alpha.
1728 - Simplify hidden service descriptor creation by using an existing
1729 flag to check if an introduction point is established. Fixes bug
1730 21599; bugfix on 0.2.7.2-alpha.
1732 o Minor bugfixes (memory leak):
1733 - Fix a small memory leak at exit from the backtrace handler code.
1734 Fixes bug 21788; bugfix on 0.2.5.2-alpha. Patch from Daniel Pinto.
1736 o Minor bugfixes (protocol, logging):
1737 - Downgrade a log statement about unexpected relay cells from "bug"
1738 to "protocol warning", because there is at least one use case
1739 where it can be triggered by a buggy tor implementation. Fixes bug
1740 21293; bugfix on 0.1.1.14-alpha.
1742 o Minor bugfixes (testing):
1743 - Use unbuffered I/O for utility functions around the
1744 process_handle_t type. This fixes unit test failures reported on
1745 OpenBSD and FreeBSD. Fixes bug 21654; bugfix on 0.2.3.1-alpha.
1746 - Make display of captured unit test log messages consistent. Fixes
1747 bug 21510; bugfix on 0.2.9.3-alpha.
1748 - Make test-network.sh always call chutney's test-network.sh.
1749 Previously, this only worked on systems which had bash installed,
1750 due to some bash-specific code in the script. Fixes bug 19699;
1751 bugfix on 0.3.0.4-rc. Follow-up to ticket 21581.
1753 o Minor bugfixes (voting consistency):
1754 - Reject version numbers with non-numeric prefixes (such as +, -, or
1755 whitespace). Disallowing whitespace prevents differential version
1756 parsing between POSIX-based and Windows platforms. Fixes bug 21507
1757 and part of 21508; bugfix on 0.0.8pre1.
1759 o Minor bugfixes (windows, relay):
1760 - Resolve "Failure from drain_fd: No error" warnings on Windows
1761 relays. Fixes bug 21540; bugfix on 0.2.6.3-alpha.
1763 o Code simplification and refactoring:
1764 - Break up the 630-line function connection_dir_client_reached_eof()
1765 into a dozen smaller functions. This change should help
1766 maintainability and readability of the client directory code.
1767 - Isolate our use of the openssl headers so that they are only
1768 included from our crypto wrapper modules, and from tests that
1769 examine those modules' internals. Closes ticket 21841.
1770 - Simplify our API to launch directory requests, making it more
1771 extensible and less error-prone. Now it's easier to add extra
1772 headers to directory requests. Closes ticket 21646.
1773 - Our base64 decoding functions no longer overestimate the output
1774 space that they need when parsing unpadded inputs. Closes
1776 - Remove unused "ROUTER_ADDED_NOTIFY_GENERATOR" internal value.
1777 Resolves ticket 22213.
1778 - The logic that directory caches use to spool request to clients,
1779 serving them one part at a time so as not to allocate too much
1780 memory, has been refactored for consistency. Previously there was
1781 a separate spooling implementation per type of spoolable data. Now
1782 there is one common spooling implementation, with extensible data
1783 types. Closes ticket 21651.
1784 - Tor's compression module now supports multiple backends. Part of
1785 the implementation for proposal 278; closes ticket 21663.
1788 - Clarify the behavior of the KeepAliveIsolateSOCKSAuth sub-option.
1789 Closes ticket 21873.
1790 - Correct documentation about the default DataDirectory value.
1791 Closes ticket 21151.
1792 - Document the default behavior of NumEntryGuards and
1793 NumDirectoryGuards correctly. Fixes bug 21715; bugfix
1795 - Document key=value pluggable transport arguments for Bridge lines
1796 in torrc. Fixes bug 20341; bugfix on 0.2.5.1-alpha.
1797 - Note that bandwidth-limiting options don't affect TCP headers or
1798 DNS. Closes ticket 17170.
1800 o Removed features (configuration options, all in ticket 22060):
1801 - These configuration options are now marked Obsolete, and no longer
1802 have any effect: AllowInvalidNodes, AllowSingleHopCircuits,
1803 AllowSingleHopExits, ExcludeSingleHopRelays, FastFirstHopPK,
1804 TLSECGroup, WarnUnsafeSocks. They were first marked as deprecated
1805 in 0.2.9.2-alpha and have now been removed. The previous default
1806 behavior is now always chosen; the previous (less secure) non-
1807 default behavior is now unavailable.
1808 - CloseHSClientCircuitsImmediatelyOnTimeout and
1809 CloseHSServiceRendCircuitsImmediatelyOnTimeout were deprecated in
1810 0.2.9.2-alpha and now have been removed. HS circuits never close
1811 on circuit build timeout; they have a longer timeout period.
1812 - {Control,DNS,Dir,Socks,Trans,NATD,OR}ListenAddress were deprecated
1813 in 0.2.9.2-alpha and now have been removed. Use the ORPort option
1814 (and others) to configure listen-only and advertise-only addresses.
1816 o Removed features (tools):
1817 - We've removed the tor-checkkey tool from src/tools. Long ago, we
1818 used it to help people detect RSA keys that were generated by
1819 versions of Debian affected by CVE-2008-0166. But those keys have
1820 been out of circulation for ages, and this tool is no longer
1821 required. Closes ticket 21842.
1824 Changes in version 0.3.0.7 - 2017-05-15
1825 Tor 0.3.0.7 fixes a medium-severity security bug in earlier versions
1826 of Tor 0.3.0.x, where an attacker could cause a Tor relay process
1827 to exit. Relays running earlier versions of Tor 0.3.0.x should upgrade;
1828 clients are not affected.
1830 o Major bugfixes (hidden service directory, security):
1831 - Fix an assertion failure in the hidden service directory code, which
1832 could be used by an attacker to remotely cause a Tor relay process to
1833 exit. Relays running earlier versions of Tor 0.3.0.x should upgrade.
1834 should upgrade. This security issue is tracked as TROVE-2017-002.
1835 Fixes bug 22246; bugfix on 0.3.0.1-alpha.
1838 - Update geoip and geoip6 to the May 2 2017 Maxmind GeoLite2
1841 o Minor features (future-proofing):
1842 - Tor no longer refuses to download microdescriptors or descriptors
1843 if they are listed as "published in the future". This change will
1844 eventually allow us to stop listing meaningful "published" dates
1845 in microdescriptor consensuses, and thereby allow us to reduce the
1846 resources required to download consensus diffs by over 50%.
1847 Implements part of ticket 21642; implements part of proposal 275.
1849 o Minor bugfixes (Linux seccomp2 sandbox):
1850 - The getpid() system call is now permitted under the Linux seccomp2
1851 sandbox, to avoid crashing with versions of OpenSSL (and other
1852 libraries) that attempt to learn the process's PID by using the
1853 syscall rather than the VDSO code. Fixes bug 21943; bugfix
1857 Changes in version 0.3.0.6 - 2017-04-26
1858 Tor 0.3.0.6 is the first stable release of the Tor 0.3.0 series.
1860 With the 0.3.0 series, clients and relays now use Ed25519 keys to
1861 authenticate their link connections to relays, rather than the old
1862 RSA1024 keys that they used before. (Circuit crypto has been
1863 Curve25519-authenticated since 0.2.4.8-alpha.) We have also replaced
1864 the guard selection and replacement algorithm to behave more robustly
1865 in the presence of unreliable networks, and to resist guard-
1868 This series also includes numerous other small features and bugfixes,
1869 along with more groundwork for the upcoming hidden-services revamp.
1871 Per our stable release policy, we plan to support the Tor 0.3.0
1872 release series for at least the next nine months, or for three months
1873 after the first stable release of the 0.3.1 series: whichever is
1874 longer. If you need a release with long-term support, we recommend
1875 that you stay with the 0.2.9 series.
1877 Below are the changes since 0.3.0.5-rc. For a list of all changes
1878 since 0.2.9, see the ReleaseNotes file.
1880 o Minor features (geoip):
1881 - Update geoip and geoip6 to the April 4 2017 Maxmind GeoLite2
1884 o Minor bugfixes (control port):
1885 - The GETINFO extra-info/digest/<digest> command was broken because
1886 of a wrong base16 decode return value check, introduced when
1887 refactoring that API. Fixes bug 22034; bugfix on 0.2.9.1-alpha.
1889 o Minor bugfixes (crash prevention):
1890 - Fix a (currently untriggerable, but potentially dangerous) crash
1891 bug when base32-encoding inputs whose sizes are not a multiple of
1892 5. Fixes bug 21894; bugfix on 0.2.9.1-alpha.
1895 Changes in version 0.3.0.5-rc - 2017-04-05
1896 Tor 0.3.0.5-rc fixes a few remaining bugs, large and small, in the
1897 0.3.0 release series.
1899 This is the second release candidate in the Tor 0.3.0 series, and has
1900 much fewer changes than the first. If we find no new bugs or
1901 regressions here, the first stable 0.3.0 release will be nearly
1904 o Major bugfixes (crash, directory connections):
1905 - Fix a rare crash when sending a begin cell on a circuit whose
1906 linked directory connection had already been closed. Fixes bug
1907 21576; bugfix on 0.2.9.3-alpha. Reported by Alec Muffett.
1909 o Major bugfixes (guard selection):
1910 - Fix a guard selection bug where Tor would refuse to bootstrap in
1911 some cases if the user swapped a bridge for another bridge in
1912 their configuration file. Fixes bug 21771; bugfix on 0.3.0.1-alpha.
1913 Reported by "torvlnt33r".
1915 o Minor features (geoip):
1916 - Update geoip and geoip6 to the March 7 2017 Maxmind GeoLite2
1919 o Minor bugfix (compilation):
1920 - Fix a warning when compiling hs_service.c. Previously, it had no
1921 exported symbols when compiled for libor.a, resulting in a
1922 compilation warning from clang. Fixes bug 21825; bugfix
1925 o Minor bugfixes (hidden services):
1926 - Make hidden services check for failed intro point connections,
1927 even when they have exceeded their intro point creation limit.
1928 Fixes bug 21596; bugfix on 0.2.7.2-alpha. Reported by Alec Muffett.
1929 - Make hidden services with 8 to 10 introduction points check for
1930 failed circuits immediately after startup. Previously, they would
1931 wait for 5 minutes before performing their first checks. Fixes bug
1932 21594; bugfix on 0.2.3.9-alpha. Reported by Alec Muffett.
1934 o Minor bugfixes (memory leaks):
1935 - Fix a memory leak when using GETCONF on a port option. Fixes bug
1936 21682; bugfix on 0.3.0.3-alpha.
1938 o Minor bugfixes (relay):
1939 - Avoid a double-marked-circuit warning that could happen when we
1940 receive DESTROY cells under heavy load. Fixes bug 20059; bugfix
1943 o Minor bugfixes (tests):
1944 - Run the entry_guard_parse_from_state_full() test with the time set
1945 to a specific date. (The guard state that this test was parsing
1946 contained guards that had expired since the test was first
1947 written.) Fixes bug 21799; bugfix on 0.3.0.1-alpha.
1950 - Update the description of the directory server options in the
1951 manual page, to clarify that a relay no longer needs to set
1952 DirPort in order to be a directory cache. Closes ticket 21720.
1956 Changes in version 0.2.8.13 - 2017-03-03
1957 Tor 0.2.8.13 backports a security fix from later Tor
1958 releases. Anybody running Tor 0.2.8.12 or earlier should upgrade to this
1959 this release, if for some reason they cannot upgrade to a later
1960 release series, and if they build Tor with the --enable-expensive-hardening
1963 Note that support for Tor 0.2.8.x is ending next year: we will not issue
1964 any fixes for the Tor 0.2.8.x series after 1 Jan 2018. If you need
1965 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1967 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
1968 - Fix an integer underflow bug when comparing malformed Tor
1969 versions. This bug could crash Tor when built with
1970 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
1971 0.2.9.8, which were built with -ftrapv by default. In other cases
1972 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
1973 on 0.0.8pre1. Found by OSS-Fuzz.
1975 o Minor features (geoip):
1976 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
1980 Changes in version 0.2.7.7 - 2017-03-03
1981 Tor 0.2.7.7 backports a number of security fixes from later Tor
1982 releases. Anybody running Tor 0.2.7.6 or earlier should upgrade to
1983 this release, if for some reason they cannot upgrade to a later
1986 Note that support for Tor 0.2.7.x is ending this year: we will not issue
1987 any fixes for the Tor 0.2.7.x series after 1 August 2017. If you need
1988 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
1990 o Directory authority changes (backport from 0.2.8.5-rc):
1991 - Urras is no longer a directory authority. Closes ticket 19271.
1993 o Directory authority changes (backport from 0.2.9.2-alpha):
1994 - The "Tonga" bridge authority has been retired; the new bridge
1995 authority is "Bifroest". Closes tickets 19728 and 19690.
1997 o Directory authority key updates (backport from 0.2.8.1-alpha):
1998 - Update the V3 identity key for the dannenberg directory authority:
1999 it was changed on 18 November 2015. Closes task 17906. Patch
2002 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2003 - Fix a bug in parsing that could cause clients to read a single
2004 byte past the end of an allocated region. This bug could be used
2005 to cause hardened clients (built with --enable-expensive-hardening)
2006 to crash if they tried to visit a hostile hidden service. Non-
2007 hardened clients are only affected depending on the details of
2008 their platform's memory allocator. Fixes bug 21018; bugfix on
2009 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2010 2016-12-002 and as CVE-2016-1254.
2012 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2013 - Stop a crash that could occur when a client running with DNSPort
2014 received a query with multiple address types, and the first
2015 address type was not supported. Found and fixed by Scott Dial.
2016 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2017 - Prevent a class of security bugs caused by treating the contents
2018 of a buffer chunk as if they were a NUL-terminated string. At
2019 least one such bug seems to be present in all currently used
2020 versions of Tor, and would allow an attacker to remotely crash
2021 most Tor instances, especially those compiled with extra compiler
2022 hardening. With this defense in place, such bugs can't crash Tor,
2023 though we should still fix them as they occur. Closes ticket
2024 20384 (TROVE-2016-10-001).
2026 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2027 - Avoid a difficult-to-trigger heap corruption attack when extending
2028 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2029 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2030 Reported by Guido Vranken.
2032 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2033 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2034 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2036 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2037 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2038 pointer to the previous (uninitialized) key value. The impact here
2039 should be limited to a difficult-to-trigger crash, if OpenSSL is
2040 running an engine that makes key generation failures possible, or
2041 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2042 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2045 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2046 - Fix an integer underflow bug when comparing malformed Tor
2047 versions. This bug could crash Tor when built with
2048 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2049 0.2.9.8, which were built with -ftrapv by default. In other cases
2050 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2051 on 0.0.8pre1. Found by OSS-Fuzz.
2053 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2054 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2055 zero size. Check size argument to memwipe() for underflow. Fixes
2056 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2059 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2060 - Make Tor survive errors involving connections without a
2061 corresponding event object. Previously we'd fail with an
2062 assertion; now we produce a log message. Related to bug 16248.
2064 o Minor features (geoip):
2065 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2069 Changes in version 0.2.6.11 - 2017-03-03
2070 Tor 0.2.6.11 backports a number of security fixes from later Tor
2071 releases. Anybody running Tor 0.2.6.10 or earlier should upgrade to
2072 this release, if for some reason they cannot upgrade to a later
2075 Note that support for Tor 0.2.6.x is ending this year: we will not issue
2076 any fixes for the Tor 0.2.6.x series after 1 August 2017. If you need
2077 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2079 o Directory authority changes (backport from 0.2.8.5-rc):
2080 - Urras is no longer a directory authority. Closes ticket 19271.
2082 o Directory authority changes (backport from 0.2.9.2-alpha):
2083 - The "Tonga" bridge authority has been retired; the new bridge
2084 authority is "Bifroest". Closes tickets 19728 and 19690.
2086 o Directory authority key updates (backport from 0.2.8.1-alpha):
2087 - Update the V3 identity key for the dannenberg directory authority:
2088 it was changed on 18 November 2015. Closes task 17906. Patch
2091 o Major features (security fixes, backport from 0.2.9.4-alpha):
2092 - Prevent a class of security bugs caused by treating the contents
2093 of a buffer chunk as if they were a NUL-terminated string. At
2094 least one such bug seems to be present in all currently used
2095 versions of Tor, and would allow an attacker to remotely crash
2096 most Tor instances, especially those compiled with extra compiler
2097 hardening. With this defense in place, such bugs can't crash Tor,
2098 though we should still fix them as they occur. Closes ticket
2099 20384 (TROVE-2016-10-001).
2101 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2102 - Fix a bug in parsing that could cause clients to read a single
2103 byte past the end of an allocated region. This bug could be used
2104 to cause hardened clients (built with --enable-expensive-hardening)
2105 to crash if they tried to visit a hostile hidden service. Non-
2106 hardened clients are only affected depending on the details of
2107 their platform's memory allocator. Fixes bug 21018; bugfix on
2108 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2109 2016-12-002 and as CVE-2016-1254.
2111 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2112 - Stop a crash that could occur when a client running with DNSPort
2113 received a query with multiple address types, and the first
2114 address type was not supported. Found and fixed by Scott Dial.
2115 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2117 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
2118 - Fix an error that could cause us to read 4 bytes before the
2119 beginning of an openssl string. This bug could be used to cause
2120 Tor to crash on systems with unusual malloc implementations, or
2121 systems with unusual hardening installed. Fixes bug 17404; bugfix
2124 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2125 - Avoid a difficult-to-trigger heap corruption attack when extending
2126 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2127 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2128 Reported by Guido Vranken.
2130 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2131 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2132 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2134 o Major bugfixes (guard selection, backport from 0.2.7.6):
2135 - Actually look at the Guard flag when selecting a new directory
2136 guard. When we implemented the directory guard design, we
2137 accidentally started treating all relays as if they have the Guard
2138 flag during guard selection, leading to weaker anonymity and worse
2139 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2142 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2143 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2144 pointer to the previous (uninitialized) key value. The impact here
2145 should be limited to a difficult-to-trigger crash, if OpenSSL is
2146 running an engine that makes key generation failures possible, or
2147 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2148 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2151 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2152 - Fix an integer underflow bug when comparing malformed Tor
2153 versions. This bug could crash Tor when built with
2154 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2155 0.2.9.8, which were built with -ftrapv by default. In other cases
2156 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2157 on 0.0.8pre1. Found by OSS-Fuzz.
2159 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2160 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2161 zero size. Check size argument to memwipe() for underflow. Fixes
2162 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2165 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2166 - Make Tor survive errors involving connections without a
2167 corresponding event object. Previously we'd fail with an
2168 assertion; now we produce a log message. Related to bug 16248.
2170 o Minor features (geoip):
2171 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2174 o Minor bugfixes (compilation, backport from 0.2.7.6):
2175 - Fix a compilation warning with Clang 3.6: Do not check the
2176 presence of an address which can never be NULL. Fixes bug 17781.
2179 Changes in version 0.2.5.13 - 2017-03-03
2180 Tor 0.2.5.13 backports a number of security fixes from later Tor
2181 releases. Anybody running Tor 0.2.5.13 or earlier should upgrade to
2182 this release, if for some reason they cannot upgrade to a later
2185 Note that support for Tor 0.2.5.x is ending next year: we will not issue
2186 any fixes for the Tor 0.2.5.x series after 1 May 2018. If you need
2187 a Tor release series with longer-term support, we recommend Tor 0.2.9.x.
2189 o Directory authority changes (backport from 0.2.8.5-rc):
2190 - Urras is no longer a directory authority. Closes ticket 19271.
2192 o Directory authority changes (backport from 0.2.9.2-alpha):
2193 - The "Tonga" bridge authority has been retired; the new bridge
2194 authority is "Bifroest". Closes tickets 19728 and 19690.
2196 o Directory authority key updates (backport from 0.2.8.1-alpha):
2197 - Update the V3 identity key for the dannenberg directory authority:
2198 it was changed on 18 November 2015. Closes task 17906. Patch
2201 o Major features (security fixes, backport from 0.2.9.4-alpha):
2202 - Prevent a class of security bugs caused by treating the contents
2203 of a buffer chunk as if they were a NUL-terminated string. At
2204 least one such bug seems to be present in all currently used
2205 versions of Tor, and would allow an attacker to remotely crash
2206 most Tor instances, especially those compiled with extra compiler
2207 hardening. With this defense in place, such bugs can't crash Tor,
2208 though we should still fix them as they occur. Closes ticket
2209 20384 (TROVE-2016-10-001).
2211 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2212 - Fix a bug in parsing that could cause clients to read a single
2213 byte past the end of an allocated region. This bug could be used
2214 to cause hardened clients (built with --enable-expensive-hardening)
2215 to crash if they tried to visit a hostile hidden service. Non-
2216 hardened clients are only affected depending on the details of
2217 their platform's memory allocator. Fixes bug 21018; bugfix on
2218 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2219 2016-12-002 and as CVE-2016-1254.
2221 o Major bugfixes (security, client, DNS proxy, backport from 0.2.8.3-alpha):
2222 - Stop a crash that could occur when a client running with DNSPort
2223 received a query with multiple address types, and the first
2224 address type was not supported. Found and fixed by Scott Dial.
2225 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
2227 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
2228 - Fix an error that could cause us to read 4 bytes before the
2229 beginning of an openssl string. This bug could be used to cause
2230 Tor to crash on systems with unusual malloc implementations, or
2231 systems with unusual hardening installed. Fixes bug 17404; bugfix
2234 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2235 - Avoid a difficult-to-trigger heap corruption attack when extending
2236 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2237 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2238 Reported by Guido Vranken.
2240 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2241 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2242 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2244 o Major bugfixes (guard selection, backport from 0.2.7.6):
2245 - Actually look at the Guard flag when selecting a new directory
2246 guard. When we implemented the directory guard design, we
2247 accidentally started treating all relays as if they have the Guard
2248 flag during guard selection, leading to weaker anonymity and worse
2249 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2252 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2253 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2254 pointer to the previous (uninitialized) key value. The impact here
2255 should be limited to a difficult-to-trigger crash, if OpenSSL is
2256 running an engine that makes key generation failures possible, or
2257 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2258 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2261 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2262 - Fix an integer underflow bug when comparing malformed Tor
2263 versions. This bug could crash Tor when built with
2264 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2265 0.2.9.8, which were built with -ftrapv by default. In other cases
2266 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2267 on 0.0.8pre1. Found by OSS-Fuzz.
2269 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2270 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2271 zero size. Check size argument to memwipe() for underflow. Fixes
2272 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2275 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2276 - Make Tor survive errors involving connections without a
2277 corresponding event object. Previously we'd fail with an
2278 assertion; now we produce a log message. Related to bug 16248.
2280 o Minor features (geoip):
2281 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2284 o Minor bugfixes (compilation, backport from 0.2.7.6):
2285 - Fix a compilation warning with Clang 3.6: Do not check the
2286 presence of an address which can never be NULL. Fixes bug 17781.
2288 o Minor bugfixes (crypto error-handling, backport from 0.2.7.2-alpha):
2289 - Check for failures from crypto_early_init, and refuse to continue.
2290 A previous typo meant that we could keep going with an
2291 uninitialized crypto library, and would have OpenSSL initialize
2292 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
2293 when implementing ticket 4900. Patch by "teor".
2295 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2296 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2297 a client authorized hidden service. Fixes bug 15823; bugfix
2301 Changes in version 0.2.4.28 - 2017-03-03
2302 Tor 0.2.4.28 backports a number of security fixes from later Tor
2303 releases. Anybody running Tor 0.2.4.27 or earlier should upgrade to
2304 this release, if for some reason they cannot upgrade to a later
2307 Note that support for Tor 0.2.4.x is ending soon: we will not issue
2308 any fixes for the Tor 0.2.4.x series after 1 August 2017. If you need
2309 a Tor release series with long-term support, we recommend Tor 0.2.9.x.
2311 o Directory authority changes (backport from 0.2.8.5-rc):
2312 - Urras is no longer a directory authority. Closes ticket 19271.
2314 o Directory authority changes (backport from 0.2.9.2-alpha):
2315 - The "Tonga" bridge authority has been retired; the new bridge
2316 authority is "Bifroest". Closes tickets 19728 and 19690.
2318 o Directory authority key updates (backport from 0.2.8.1-alpha):
2319 - Update the V3 identity key for the dannenberg directory authority:
2320 it was changed on 18 November 2015. Closes task 17906. Patch
2323 o Major features (security fixes, backport from 0.2.9.4-alpha):
2324 - Prevent a class of security bugs caused by treating the contents
2325 of a buffer chunk as if they were a NUL-terminated string. At
2326 least one such bug seems to be present in all currently used
2327 versions of Tor, and would allow an attacker to remotely crash
2328 most Tor instances, especially those compiled with extra compiler
2329 hardening. With this defense in place, such bugs can't crash Tor,
2330 though we should still fix them as they occur. Closes ticket
2331 20384 (TROVE-2016-10-001).
2333 o Major bugfixes (parsing, security, backport from 0.2.9.8):
2334 - Fix a bug in parsing that could cause clients to read a single
2335 byte past the end of an allocated region. This bug could be used
2336 to cause hardened clients (built with --enable-expensive-hardening)
2337 to crash if they tried to visit a hostile hidden service. Non-
2338 hardened clients are only affected depending on the details of
2339 their platform's memory allocator. Fixes bug 21018; bugfix on
2340 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
2341 2016-12-002 and as CVE-2016-1254.
2343 o Major bugfixes (security, correctness, backport from 0.2.7.4-rc):
2344 - Fix an error that could cause us to read 4 bytes before the
2345 beginning of an openssl string. This bug could be used to cause
2346 Tor to crash on systems with unusual malloc implementations, or
2347 systems with unusual hardening installed. Fixes bug 17404; bugfix
2350 o Major bugfixes (security, pointers, backport from 0.2.8.2-alpha):
2351 - Avoid a difficult-to-trigger heap corruption attack when extending
2352 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
2353 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
2354 Reported by Guido Vranken.
2356 o Major bugfixes (dns proxy mode, crash, backport from 0.2.8.2-alpha):
2357 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
2358 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
2360 o Major bugfixes (guard selection, backport from 0.2.7.6):
2361 - Actually look at the Guard flag when selecting a new directory
2362 guard. When we implemented the directory guard design, we
2363 accidentally started treating all relays as if they have the Guard
2364 flag during guard selection, leading to weaker anonymity and worse
2365 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
2368 o Major bugfixes (key management, backport from 0.2.8.3-alpha):
2369 - If OpenSSL fails to generate an RSA key, do not retain a dangling
2370 pointer to the previous (uninitialized) key value. The impact here
2371 should be limited to a difficult-to-trigger crash, if OpenSSL is
2372 running an engine that makes key generation failures possible, or
2373 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
2374 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
2377 o Major bugfixes (parsing, backported from 0.3.0.4-rc):
2378 - Fix an integer underflow bug when comparing malformed Tor
2379 versions. This bug could crash Tor when built with
2380 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2381 0.2.9.8, which were built with -ftrapv by default. In other cases
2382 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2383 on 0.0.8pre1. Found by OSS-Fuzz.
2385 o Minor features (security, memory erasure, backport from 0.2.8.1-alpha):
2386 - Make memwipe() do nothing when passed a NULL pointer or buffer of
2387 zero size. Check size argument to memwipe() for underflow. Fixes
2388 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
2391 o Minor features (bug-resistance, backport from 0.2.8.2-alpha):
2392 - Make Tor survive errors involving connections without a
2393 corresponding event object. Previously we'd fail with an
2394 assertion; now we produce a log message. Related to bug 16248.
2396 o Minor features (DoS-resistance, backport from 0.2.7.1-alpha):
2397 - Make it harder for attackers to overload hidden services with
2398 introductions, by blocking multiple introduction requests on the
2399 same circuit. Resolves ticket 15515.
2401 o Minor features (geoip):
2402 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2405 o Minor bugfixes (compilation, backport from 0.2.7.6):
2406 - Fix a compilation warning with Clang 3.6: Do not check the
2407 presence of an address which can never be NULL. Fixes bug 17781.
2409 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
2410 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
2411 a client authorized hidden service. Fixes bug 15823; bugfix
2415 Changes in version 0.3.0.4-rc - 2017-03-01
2416 Tor 0.3.0.4-rc fixes some remaining bugs, large and small, in the
2417 0.3.0 release series, and introduces a few reliability features to
2418 keep them from coming back.
2420 This is the first release candidate in the Tor 0.3.0 series. If we
2421 find no new bugs or regressions here, the first stable 0.3.0 release
2422 will be nearly identical to it.
2424 o Major bugfixes (bridges):
2425 - When the same bridge is configured multiple times with the same
2426 identity, but at different address:port combinations, treat those
2427 bridge instances as separate guards. This fix restores the ability
2428 of clients to configure the same bridge with multiple pluggable
2429 transports. Fixes bug 21027; bugfix on 0.3.0.1-alpha.
2431 o Major bugfixes (hidden service directory v3):
2432 - Stop crashing on a failed v3 hidden service descriptor lookup
2433 failure. Fixes bug 21471; bugfixes on tor-0.3.0.1-alpha.
2435 o Major bugfixes (parsing):
2436 - When parsing a malformed content-length field from an HTTP
2437 message, do not read off the end of the buffer. This bug was a
2438 potential remote denial-of-service attack against Tor clients and
2439 relays. A workaround was released in October 2016, to prevent this
2440 bug from crashing Tor. This is a fix for the underlying issue,
2441 which should no longer matter (if you applied the earlier patch).
2442 Fixes bug 20894; bugfix on 0.2.0.16-alpha. Bug found by fuzzing
2443 using AFL (http://lcamtuf.coredump.cx/afl/).
2444 - Fix an integer underflow bug when comparing malformed Tor
2445 versions. This bug could crash Tor when built with
2446 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2447 0.2.9.8, which were built with -ftrapv by default. In other cases
2448 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2449 on 0.0.8pre1. Found by OSS-Fuzz.
2451 o Minor feature (protocol versioning):
2452 - Add new protocol version for proposal 224. HSIntro now advertises
2453 version "3-4" and HSDir version "1-2". Fixes ticket 20656.
2455 o Minor features (directory authorities):
2456 - Directory authorities now reject descriptors that claim to be
2457 malformed versions of Tor. Helps prevent exploitation of
2459 - Reject version numbers with components that exceed INT32_MAX.
2460 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
2461 Fixes bug 21450; bugfix on 0.0.8pre1.
2462 - Directory authorities now reject relays running versions
2463 0.2.9.1-alpha through 0.2.9.4-alpha, because those relays
2464 suffer from bug 20499 and don't keep their consensus cache
2465 up-to-date. Resolves ticket 20509.
2467 o Minor features (geoip):
2468 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2471 o Minor features (reliability, crash):
2472 - Try better to detect problems in buffers where they might grow (or
2473 think they have grown) over 2 GB in size. Diagnostic for
2476 o Minor features (testing):
2477 - During 'make test-network-all', if tor logs any warnings, ask
2478 chutney to output them. Requires a recent version of chutney with
2479 the 21572 patch. Implements 21570.
2481 o Minor bugfixes (certificate expiration time):
2482 - Avoid using link certificates that don't become valid till some
2483 time in the future. Fixes bug 21420; bugfix on 0.2.4.11-alpha
2485 o Minor bugfixes (code correctness):
2486 - Repair a couple of (unreachable or harmless) cases of the risky
2487 comparison-by-subtraction pattern that caused bug 21278.
2488 - Remove a redundant check for the UseEntryGuards option from the
2489 options_transition_affects_guards() function. Fixes bug 21492;
2490 bugfix on 0.3.0.1-alpha.
2492 o Minor bugfixes (directory mirrors):
2493 - Allow relays to use directory mirrors without a DirPort: these
2494 relays need to be contacted over their ORPorts using a begindir
2495 connection. Fixes one case of bug 20711; bugfix on 0.2.8.2-alpha.
2496 - Clarify the message logged when a remote relay is unexpectedly
2497 missing an ORPort or DirPort: users were confusing this with a
2498 local port. Fixes another case of bug 20711; bugfix
2501 o Minor bugfixes (guards):
2502 - Don't warn about a missing guard state on timeout-measurement
2503 circuits: they aren't supposed to be using guards. Fixes an
2504 instance of bug 21007; bugfix on 0.3.0.1-alpha.
2505 - Silence a BUG() warning when attempting to use a guard whose
2506 descriptor we don't know, and make this scenario less likely to
2507 happen. Fixes bug 21415; bugfix on 0.3.0.1-alpha.
2509 o Minor bugfixes (hidden service):
2510 - Pass correct buffer length when encoding legacy ESTABLISH_INTRO
2511 cells. Previously, we were using sizeof() on a pointer, instead of
2512 the real destination buffer. Fortunately, that value was only used
2513 to double-check that there was enough room--which was already
2514 enforced elsewhere. Fixes bug 21553; bugfix on 0.3.0.1-alpha.
2516 o Minor bugfixes (testing):
2517 - Fix Raspbian build issues related to missing socket errno in
2518 test_util.c. Fixes bug 21116; bugfix on tor-0.2.8.2. Patch
2520 - Rename "make fuzz" to "make test-fuzz-corpora", since it doesn't
2521 actually fuzz anything. Fixes bug 21447; bugfix on 0.3.0.3-alpha.
2522 - Use bash in src/test/test-network.sh. This ensures we reliably
2523 call chutney's newer tools/test-network.sh when available. Fixes
2524 bug 21562; bugfix on 0.2.9.1-alpha.
2527 - Small fixes to the fuzzing documentation. Closes ticket 21472.
2530 Changes in version 0.2.9.10 - 2017-03-01
2531 Tor 0.2.9.10 backports a security fix from later Tor release. It also
2532 includes fixes for some major issues affecting directory authorities,
2533 LibreSSL compatibility, and IPv6 correctness.
2535 The Tor 0.2.9.x release series is now marked as a long-term-support
2536 series. We intend to backport security fixes to 0.2.9.x until at
2537 least January of 2020.
2539 o Major bugfixes (directory authority, 0.3.0.3-alpha):
2540 - During voting, when marking a relay as a probable sybil, do not
2541 clear its BadExit flag: sybils can still be bad in other ways
2542 too. (We still clear the other flags.) Fixes bug 21108; bugfix
2545 o Major bugfixes (IPv6 Exits, backport from 0.3.0.3-alpha):
2546 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
2547 any IPv6 addresses. Instead, only reject a port over IPv6 if the
2548 exit policy rejects that port on more than an IPv6 /16 of
2549 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
2550 which rejected a relay's own IPv6 address by default. Fixes bug
2551 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
2553 o Major bugfixes (parsing, also in 0.3.0.4-rc):
2554 - Fix an integer underflow bug when comparing malformed Tor
2555 versions. This bug could crash Tor when built with
2556 --enable-expensive-hardening, or on Tor 0.2.9.1-alpha through Tor
2557 0.2.9.8, which were built with -ftrapv by default. In other cases
2558 it was harmless. Part of TROVE-2017-001. Fixes bug 21278; bugfix
2559 on 0.0.8pre1. Found by OSS-Fuzz.
2561 o Minor features (directory authorities, also in 0.3.0.4-rc):
2562 - Directory authorities now reject descriptors that claim to be
2563 malformed versions of Tor. Helps prevent exploitation of
2565 - Reject version numbers with components that exceed INT32_MAX.
2566 Otherwise 32-bit and 64-bit platforms would behave inconsistently.
2567 Fixes bug 21450; bugfix on 0.0.8pre1.
2569 o Minor features (geoip):
2570 - Update geoip and geoip6 to the February 8 2017 Maxmind GeoLite2
2573 o Minor features (portability, compilation, backport from 0.3.0.3-alpha):
2574 - Autoconf now checks to determine if OpenSSL structures are opaque,
2575 instead of explicitly checking for OpenSSL version numbers. Part
2577 - Support building with recent LibreSSL code that uses opaque
2578 structures. Closes ticket 21359.
2580 o Minor bugfixes (code correctness, also in 0.3.0.4-rc):
2581 - Repair a couple of (unreachable or harmless) cases of the risky
2582 comparison-by-subtraction pattern that caused bug 21278.
2584 o Minor bugfixes (tor-resolve, backport from 0.3.0.3-alpha):
2585 - The tor-resolve command line tool now rejects hostnames over 255
2586 characters in length. Previously, it would silently truncate them,
2587 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
2588 Patch by "junglefowl".
2591 Changes in version 0.3.0.3-alpha - 2017-02-03
2592 Tor 0.3.0.3-alpha fixes a few significant bugs introduced over the
2593 0.3.0.x development series, including some that could cause
2594 authorities to behave badly. There is also a fix for a longstanding
2595 bug that could prevent IPv6 exits from working. Tor 0.3.0.3-alpha also
2596 includes some smaller features and bugfixes.
2598 The Tor 0.3.0.x release series is now in patch-freeze: no additional
2599 features will be considered for inclusion in 0.3.0.x. We suspect that
2600 some bugs will probably remain, however, and we encourage people to
2603 o Major bugfixes (directory authority):
2604 - During voting, when marking a relay as a probable sybil, do not
2605 clear its BadExit flag: sybils can still be bad in other ways
2606 too. (We still clear the other flags.) Fixes bug 21108; bugfix
2608 - When deciding whether we have just found a router to be reachable,
2609 do not penalize it for not having performed an Ed25519 link
2610 handshake if it does not claim to support an Ed25519 handshake.
2611 Previously, we would treat such relays as non-running. Fixes bug
2612 21107; bugfix on 0.3.0.1-alpha.
2614 o Major bugfixes (entry guards):
2615 - Stop trying to build circuits through entry guards for which we
2616 have no descriptor. Also, stop crashing in the case that we *do*
2617 accidentally try to build a circuit in such a state. Fixes bug
2618 21242; bugfix on 0.3.0.1-alpha.
2620 o Major bugfixes (IPv6 Exits):
2621 - Stop rejecting all IPv6 traffic on Exits whose exit policy rejects
2622 any IPv6 addresses. Instead, only reject a port over IPv6 if the
2623 exit policy rejects that port on more than an IPv6 /16 of
2624 addresses. This bug was made worse by 17027 in 0.2.8.1-alpha,
2625 which rejected a relay's own IPv6 address by default. Fixes bug
2626 21357; bugfix on commit 004f3f4e53 in 0.2.4.7-alpha.
2628 o Minor feature (client):
2629 - Enable IPv6 traffic on the SocksPort by default. To disable this,
2630 a user will have to specify "NoIPv6Traffic". Closes ticket 21269.
2632 o Minor feature (fallback scripts):
2633 - Add a check_existing mode to updateFallbackDirs.py, which checks
2634 if fallbacks in the hard-coded list are working. Closes ticket
2635 20174. Patch by haxxpop.
2637 o Minor features (ciphersuite selection):
2638 - Clients now advertise a list of ciphersuites closer to the ones
2639 preferred by Firefox. Closes part of ticket 15426.
2640 - Allow relays to accept a wider range of ciphersuites, including
2641 chacha20-poly1305 and AES-CCM. Closes the other part of 15426.
2643 o Minor features (controller, configuration):
2644 - Each of the *Port options, such as SocksPort, ORPort, ControlPort,
2645 and so on, now comes with a __*Port variant that will not be saved
2646 to the torrc file by the controller's SAVECONF command. This
2647 change allows TorBrowser to set up a single-use domain socket for
2648 each time it launches Tor. Closes ticket 20956.
2649 - The GETCONF command can now query options that may only be
2650 meaningful in context-sensitive lists. This allows the controller
2651 to query the mixed SocksPort/__SocksPort style options introduced
2652 in feature 20956. Implements ticket 21300.
2654 o Minor features (portability, compilation):
2655 - Autoconf now checks to determine if OpenSSL structures are opaque,
2656 instead of explicitly checking for OpenSSL version numbers. Part
2658 - Support building with recent LibreSSL code that uses opaque
2659 structures. Closes ticket 21359.
2661 o Minor features (relay):
2662 - We now allow separation of exit and relay traffic to different
2663 source IP addresses, using the OutboundBindAddressExit and
2664 OutboundBindAddressOR options respectively. Closes ticket 17975.
2665 Written by Michael Sonntag.
2667 o Minor bugfix (logging):
2668 - Don't recommend the use of Tor2web in non-anonymous mode.
2669 Recommending Tor2web is a bad idea because the client loses all
2670 anonymity. Tor2web should only be used in specific cases by users
2671 who *know* and understand the issues. Fixes bug 21294; bugfix
2674 o Minor bugfixes (client):
2675 - Always recover from failures in extend_info_from_node(), in an
2676 attempt to prevent any recurrence of bug 21242. Fixes bug 21372;
2677 bugfix on 0.2.3.1-alpha.
2679 o Minor bugfixes (client, entry guards):
2680 - Fix a bug warning (with backtrace) when we fail a channel that
2681 circuits to fallback directories on it. Fixes bug 21128; bugfix
2683 - Fix a spurious bug warning (with backtrace) when removing an
2684 expired entry guard. Fixes bug 21129; bugfix on 0.3.0.1-alpha.
2685 - Fix a bug of the new guard algorithm where tor could stall for up
2686 to 10 minutes before retrying a guard after a long period of no
2687 network. Fixes bug 21052; bugfix on 0.3.0.1-alpha.
2688 - Do not try to build circuits until we have descriptors for our
2689 primary entry guards. Related to fix for bug 21242.
2691 o Minor bugfixes (configure, autoconf):
2692 - Rename the configure option --enable-expensive-hardening to
2693 --enable-fragile-hardening. Expensive hardening makes the tor
2694 daemon abort when some kinds of issues are detected. Thus, it
2695 makes tor more at risk of remote crashes but safer against RCE or
2696 heartbleed bug category. We now try to explain this issue in a
2697 message from the configure script. Fixes bug 21290; bugfix
2700 o Minor bugfixes (controller):
2701 - Restore the (deprecated) DROPGUARDS controller command. Fixes bug
2702 20824; bugfix on 0.3.0.1-alpha.
2704 o Minor bugfixes (hidden service):
2705 - Clean up the code for expiring intro points with no associated
2706 circuits. It was causing, rarely, a service with some expiring
2707 introduction points to not open enough additional introduction
2708 points. Fixes part of bug 21302; bugfix on 0.2.7.2-alpha.
2709 - Stop setting the torrc option HiddenServiceStatistics to "0" just
2710 because we're not a bridge or relay. Instead, we preserve whatever
2711 value the user set (or didn't set). Fixes bug 21150; bugfix
2713 - Resolve two possible underflows which could lead to creating and
2714 closing a lot of introduction point circuits in a non-stop loop.
2715 Fixes bug 21302; bugfix on 0.2.7.2-alpha.
2717 o Minor bugfixes (portability):
2718 - Use "OpenBSD" compiler macro instead of "OPENBSD" or "__OpenBSD__".
2719 It is supported by OpenBSD itself, and also by most OpenBSD
2720 variants (such as Bitrig). Fixes bug 20980; bugfix
2722 - When mapping a file of length greater than SIZE_MAX, do not
2723 silently truncate its contents. This issue could occur on 32 bit
2724 systems with large file support and files which are larger than 4
2725 GB. Fixes bug 21134; bugfix on 0.3.0.1-alpha.
2727 o Minor bugfixes (tor-resolve):
2728 - The tor-resolve command line tool now rejects hostnames over 255
2729 characters in length. Previously, it would silently truncate them,
2730 which could lead to bugs. Fixes bug 21280; bugfix on 0.0.9pre5.
2731 Patch by "junglefowl".
2733 o Minor bugfixes (Windows services):
2734 - Be sure to initialize the monotonic time subsystem before using
2735 it, even when running as an NT service. Fixes bug 21356; bugfix
2739 Changes in version 0.3.0.2-alpha - 2017-01-23
2740 Tor 0.3.0.2-alpha fixes a denial-of-service bug where an attacker could
2741 cause relays and clients to crash, even if they were not built with
2742 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2743 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2744 version should upgrade.
2746 Tor 0.3.0.2-alpha also improves how exit relays and clients handle DNS
2747 time-to-live values, makes directory authorities enforce the 1-to-1
2748 mapping of relay RSA identity keys to ED25519 identity keys, fixes a
2749 client-side onion service reachability bug, does better at selecting
2750 the set of fallback directories, and more.
2752 o Major bugfixes (security, also in 0.2.9.9):
2753 - Downgrade the "-ftrapv" option from "always on" to "only on when
2754 --enable-expensive-hardening is provided." This hardening option, like
2755 others, can turn survivable bugs into crashes--and having it on by
2756 default made a (relatively harmless) integer overflow bug into a
2757 denial-of-service bug. Fixes bug 21278 (TROVE-2017-001); bugfix on
2760 o Major features (security):
2761 - Change the algorithm used to decide DNS TTLs on client and server
2762 side, to better resist DNS-based correlation attacks like the
2763 DefecTor attack of Greschbach, Pulls, Roberts, Winter, and
2764 Feamster. Now relays only return one of two possible DNS TTL
2765 values, and clients are willing to believe DNS TTL values up to 3
2766 hours long. Closes ticket 19769.
2768 o Major features (directory authority, security):
2769 - The default for AuthDirPinKeys is now 1: directory authorities
2770 will reject relays where the RSA identity key matches a previously
2771 seen value, but the Ed25519 key has changed. Closes ticket 18319.
2773 o Major bugfixes (client, guard, crash):
2774 - In circuit_get_global_origin_list(), return the actual list of
2775 origin circuits. The previous version of this code returned the
2776 list of all the circuits, and could have caused strange bugs,
2777 including possible crashes. Fixes bug 21118; bugfix
2780 o Major bugfixes (client, onion service, also in 0.2.9.9):
2781 - Fix a client-side onion service reachability bug, where multiple
2782 socks requests to an onion service (or a single slow request)
2783 could cause us to mistakenly mark some of the service's
2784 introduction points as failed, and we cache that failure so
2785 eventually we run out and can't reach the service. Also resolves a
2786 mysterious "Remote server sent bogus reason code 65021" log
2787 warning. The bug was introduced in ticket 17218, where we tried to
2788 remember the circuit end reason as a uint16_t, which mangled
2789 negative values. Partially fixes bug 21056 and fixes bug 20307;
2790 bugfix on 0.2.8.1-alpha.
2792 o Major bugfixes (DNS):
2793 - Fix a bug that prevented exit nodes from caching DNS records for
2794 more than 60 seconds. Fixes bug 19025; bugfix on 0.2.4.7-alpha.
2796 o Minor features (controller):
2797 - Add "GETINFO sr/current" and "GETINFO sr/previous" keys, to expose
2798 shared-random values to the controller. Closes ticket 19925.
2800 o Minor features (entry guards):
2801 - Add UseEntryGuards to TEST_OPTIONS_DEFAULT_VALUES in order to not
2802 break regression tests.
2803 - Require UseEntryGuards when UseBridges is set, in order to make
2804 sure bridges aren't bypassed. Resolves ticket 20502.
2806 o Minor features (fallback directories):
2807 - Select 200 fallback directories for each release. Closes
2809 - Allow 3 fallback relays per operator, which is safe now that we
2810 are choosing 200 fallback relays. Closes ticket 20912.
2811 - Exclude relays affected by bug 20499 from the fallback list.
2812 Exclude relays from the fallback list if they are running versions
2813 known to be affected by bug 20499, or if in our tests they deliver
2814 a stale consensus (i.e. one that expired more than 24 hours ago).
2815 Closes ticket 20539.
2816 - Reduce the minimum fallback bandwidth to 1 MByte/s. Part of
2818 - Require fallback directories to have the same address and port for
2819 7 days (now that we have enough relays with this stability).
2820 Relays whose OnionOO stability timer is reset on restart by bug
2821 18050 should upgrade to Tor 0.2.8.7 or later, which has a fix for
2822 this issue. Closes ticket 20880; maintains short-term fix
2824 - Require fallbacks to have flags for 90% of the time (weighted
2825 decaying average), rather than 95%. This allows at least 73% of
2826 clients to bootstrap in the first 5 seconds without contacting an
2827 authority. Part of ticket 18828.
2828 - Annotate updateFallbackDirs.py with the bandwidth and consensus
2829 weight for each candidate fallback. Closes ticket 20878.
2830 - Make it easier to change the output sort order of fallbacks.
2831 Closes ticket 20822.
2832 - Display the relay fingerprint when downloading consensuses from
2833 fallbacks. Closes ticket 20908.
2835 o Minor features (geoip, also in 0.2.9.9):
2836 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
2839 o Minor features (next-gen onion service directories):
2840 - Remove the "EnableOnionServicesV3" consensus parameter that we
2841 introduced in 0.3.0.1-alpha: relays are now always willing to act
2842 as v3 onion service directories. Resolves ticket 19899.
2844 o Minor features (linting):
2845 - Enhance the changes file linter to warn on Tor versions that are
2846 prefixed with "tor-". Closes ticket 21096.
2848 o Minor features (logging):
2849 - In several places, describe unset ed25519 keys as "<unset>",
2850 rather than the scary "AAAAAAAA...AAA". Closes ticket 21037.
2852 o Minor bugfix (control protocol):
2853 - The reply to a "GETINFO config/names" request via the control
2854 protocol now spells the type "Dependent" correctly. This is a
2855 breaking change in the control protocol. (The field seems to be
2856 ignored by the most common known controllers.) Fixes bug 18146;
2857 bugfix on 0.1.1.4-alpha.
2859 o Minor bugfixes (bug resilience):
2860 - Fix an unreachable size_t overflow in base64_decode(). Fixes bug
2861 19222; bugfix on 0.2.0.9-alpha. Found by Guido Vranken; fixed by
2862 Hans Jerry Illikainen.
2864 o Minor bugfixes (build):
2865 - Replace obsolete Autoconf macros with their modern equivalent and
2866 prevent similar issues in the future. Fixes bug 20990; bugfix
2869 o Minor bugfixes (client, guards):
2870 - Fix bug where Tor would think that there are circuits waiting for
2871 better guards even though those circuits have been freed. Fixes
2872 bug 21142; bugfix on 0.3.0.1-alpha.
2874 o Minor bugfixes (config):
2875 - Don't assert on startup when trying to get the options list and
2876 LearnCircuitBuildTimeout is set to 0: we are currently parsing the
2877 options so of course they aren't ready yet. Fixes bug 21062;
2878 bugfix on 0.2.9.3-alpha.
2880 o Minor bugfixes (controller):
2881 - Make the GETINFO interface for inquiring about entry guards
2882 support the new guards backend. Fixes bug 20823; bugfix
2885 o Minor bugfixes (dead code):
2886 - Remove a redundant check for PidFile changes at runtime in
2887 options_transition_allowed(): this check is already performed
2888 regardless of whether the sandbox is active. Fixes bug 21123;
2889 bugfix on 0.2.5.4-alpha.
2891 o Minor bugfixes (documentation):
2892 - Update the tor manual page to document every option that can not
2893 be changed while tor is running. Fixes bug 21122.
2895 o Minor bugfixes (fallback directories):
2896 - Stop failing when a relay has no uptime data in
2897 updateFallbackDirs.py. Fixes bug 20945; bugfix on 0.2.8.1-alpha.
2898 - Avoid checking fallback candidates' DirPorts if they are down in
2899 OnionOO. When a relay operator has multiple relays, this
2900 prioritizes relays that are up over relays that are down. Fixes
2901 bug 20926; bugfix on 0.2.8.3-alpha.
2902 - Stop failing when OUTPUT_COMMENTS is True in updateFallbackDirs.py.
2903 Fixes bug 20877; bugfix on 0.2.8.3-alpha.
2905 o Minor bugfixes (guards, bootstrapping):
2906 - When connecting to a directory guard during bootstrap, do not mark
2907 the guard as successful until we receive a good-looking directory
2908 response from it. Fixes bug 20974; bugfix on 0.3.0.1-alpha.
2910 o Minor bugfixes (onion services):
2911 - Fix the config reload pruning of old vs new services so it
2912 actually works when both ephemeral and non-ephemeral services are
2913 configured. Fixes bug 21054; bugfix on 0.3.0.1-alpha.
2914 - Allow the number of introduction points to be as low as 0, rather
2915 than as low as 3. Fixes bug 21033; bugfix on 0.2.7.2-alpha.
2917 o Minor bugfixes (IPv6):
2918 - Make IPv6-using clients try harder to find an IPv6 directory
2919 server. Fixes bug 20999; bugfix on 0.2.8.2-alpha.
2920 - When IPv6 addresses have not been downloaded yet (microdesc
2921 consensus documents don't list relay IPv6 addresses), use hard-
2922 coded addresses for authorities, fallbacks, and configured
2923 bridges. Now IPv6-only clients can use microdescriptors. Fixes bug
2924 20996; bugfix on b167e82 from 19608 in 0.2.8.5-alpha.
2926 o Minor bugfixes (memory leaks):
2927 - Fix a memory leak when configuring hidden services. Fixes bug
2928 20987; bugfix on 0.3.0.1-alpha.
2930 o Minor bugfixes (portability, also in 0.2.9.9):
2931 - Avoid crashing when Tor is built using headers that contain
2932 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
2933 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
2935 - Fix Libevent detection on platforms without Libevent 1 headers
2936 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
2938 o Minor bugfixes (relay):
2939 - Honor DataDirectoryGroupReadable when tor is a relay. Previously,
2940 initializing the keys would reset the DataDirectory to 0700
2941 instead of 0750 even if DataDirectoryGroupReadable was set to 1.
2942 Fixes bug 19953; bugfix on 0.0.2pre16. Patch by "redfish".
2944 o Minor bugfixes (testing):
2945 - Remove undefined behavior from the backtrace generator by removing
2946 its signal handler. Fixes bug 21026; bugfix on 0.2.5.2-alpha.
2948 o Minor bugfixes (unit tests):
2949 - Allow the unit tests to pass even when DNS lookups of bogus
2950 addresses do not fail as expected. Fixes bug 20862 and 20863;
2951 bugfix on unit tests introduced in 0.2.8.1-alpha
2952 through 0.2.9.4-alpha.
2954 o Code simplification and refactoring:
2955 - Refactor code to manipulate global_origin_circuit_list into
2956 separate functions. Closes ticket 20921.
2958 o Documentation (formatting):
2959 - Clean up formatting of tor.1 man page and HTML doc, where <pre>
2960 blocks were incorrectly appearing. Closes ticket 20885.
2962 o Documentation (man page):
2963 - Clarify many options in tor.1 and add some min/max values for
2964 HiddenService options. Closes ticket 21058.
2967 Changes in version 0.2.9.9 - 2017-01-23
2968 Tor 0.2.9.9 fixes a denial-of-service bug where an attacker could
2969 cause relays and clients to crash, even if they were not built with
2970 the --enable-expensive-hardening option. This bug affects all 0.2.9.x
2971 versions, and also affects 0.3.0.1-alpha: all relays running an affected
2972 version should upgrade.
2974 This release also resolves a client-side onion service reachability
2975 bug, and resolves a pair of small portability issues.
2977 o Major bugfixes (security):
2978 - Downgrade the "-ftrapv" option from "always on" to "only on when
2979 --enable-expensive-hardening is provided." This hardening option,
2980 like others, can turn survivable bugs into crashes -- and having
2981 it on by default made a (relatively harmless) integer overflow bug
2982 into a denial-of-service bug. Fixes bug 21278 (TROVE-2017-001);
2983 bugfix on 0.2.9.1-alpha.
2985 o Major bugfixes (client, onion service):
2986 - Fix a client-side onion service reachability bug, where multiple
2987 socks requests to an onion service (or a single slow request)
2988 could cause us to mistakenly mark some of the service's
2989 introduction points as failed, and we cache that failure so
2990 eventually we run out and can't reach the service. Also resolves a
2991 mysterious "Remote server sent bogus reason code 65021" log
2992 warning. The bug was introduced in ticket 17218, where we tried to
2993 remember the circuit end reason as a uint16_t, which mangled
2994 negative values. Partially fixes bug 21056 and fixes bug 20307;
2995 bugfix on 0.2.8.1-alpha.
2997 o Minor features (geoip):
2998 - Update geoip and geoip6 to the January 4 2017 Maxmind GeoLite2
3001 o Minor bugfixes (portability):
3002 - Avoid crashing when Tor is built using headers that contain
3003 CLOCK_MONOTONIC_COARSE, but then tries to run on an older kernel
3004 without CLOCK_MONOTONIC_COARSE. Fixes bug 21035; bugfix
3006 - Fix Libevent detection on platforms without Libevent 1 headers
3007 installed. Fixes bug 21051; bugfix on 0.2.9.1-alpha.
3010 Changes in version 0.3.0.1-alpha - 2016-12-19
3011 Tor 0.3.0.1-alpha is the first alpha release in the 0.3.0 development
3012 series. It strengthens Tor's link and circuit handshakes by
3013 identifying relays by their Ed25519 keys, improves the algorithm that
3014 clients use to choose and maintain their list of guards, and includes
3015 additional backend support for the next-generation hidden service
3016 design. It also contains numerous other small features and
3017 improvements to security, correctness, and performance.
3019 Below are the changes since 0.2.9.8.
3021 o Major features (guard selection algorithm):
3022 - Tor's guard selection algorithm has been redesigned from the
3023 ground up, to better support unreliable networks and restrictive
3024 sets of entry nodes, and to better resist guard-capture attacks by
3025 hostile local networks. Implements proposal 271; closes
3028 o Major features (next-generation hidden services):
3029 - Relays can now handle v3 ESTABLISH_INTRO cells as specified by
3030 prop224 aka "Next Generation Hidden Services". Service and clients
3031 don't use this functionality yet. Closes ticket 19043. Based on
3032 initial code by Alec Heifetz.
3033 - Relays now support the HSDir version 3 protocol, so that they can
3034 can store and serve v3 descriptors. This is part of the next-
3035 generation onion service work detailled in proposal 224. Closes
3038 o Major features (protocol, ed25519 identity keys):
3039 - Relays now use Ed25519 to prove their Ed25519 identities and to
3040 one another, and to clients. This algorithm is faster and more
3041 secure than the RSA-based handshake we've been doing until now.
3042 Implements the second big part of proposal 220; Closes
3044 - Clients now support including Ed25519 identity keys in the EXTEND2
3045 cells they generate. By default, this is controlled by a consensus
3046 parameter, currently disabled. You can turn this feature on for
3047 testing by setting ExtendByEd25519ID in your configuration. This
3048 might make your traffic appear different than the traffic
3049 generated by other users, however. Implements part of ticket
3050 15056; part of proposal 220.
3051 - Relays now understand requests to extend to other relays by their
3052 Ed25519 identity keys. When an Ed25519 identity key is included in
3053 an EXTEND2 cell, the relay will only extend the circuit if the
3054 other relay can prove ownership of that identity. Implements part
3055 of ticket 15056; part of proposal 220.
3057 o Major bugfixes (scheduler):
3058 - Actually compare circuit policies in ewma_cmp_cmux(). This bug
3059 caused the channel scheduler to behave more or less randomly,
3060 rather than preferring channels with higher-priority circuits.
3061 Fixes bug 20459; bugfix on 0.2.6.2-alpha.
3063 o Minor features (controller):
3064 - When HSFETCH arguments cannot be parsed, say "Invalid argument"
3065 rather than "unrecognized." Closes ticket 20389; patch from
3068 o Minor features (diagnostic, directory client):
3069 - Warn when we find an unexpected inconsistency in directory
3070 download status objects. Prevents some negative consequences of
3073 o Minor features (directory authority):
3074 - Add a new authority-only AuthDirTestEd25519LinkKeys option (on by
3075 default) to control whether authorities should try to probe relays
3076 by their Ed25519 link keys. This option will go away in a few
3077 releases--unless we encounter major trouble in our ed25519 link
3078 protocol rollout, in which case it will serve as a safety option.
3080 o Minor features (directory cache):
3081 - Relays and bridges will now refuse to serve the consensus they
3082 have if they know it is too old for a client to use. Closes
3085 o Minor features (ed25519 link handshake):
3086 - Advertise support for the ed25519 link handshake using the
3087 subprotocol-versions mechanism, so that clients can tell which
3088 relays can identity themselves by Ed25519 ID. Closes ticket 20552.
3090 o Minor features (fingerprinting resistance, authentication):
3091 - Extend the length of RSA keys used for TLS link authentication to
3092 2048 bits. (These weren't used for forward secrecy; for forward
3093 secrecy, we used P256.) Closes ticket 13752.
3095 o Minor features (infrastructure):
3096 - Implement smartlist_add_strdup() function. Replaces the use of
3097 smartlist_add(sl, tor_strdup(str)). Closes ticket 20048.
3099 o Minor bugfixes (client):
3100 - When clients that use bridges start up with a cached consensus on
3101 disk, they were ignoring it and downloading a new one. Now they
3102 use the cached one. Fixes bug 20269; bugfix on 0.2.3.12-alpha.
3104 o Minor bugfixes (configuration):
3105 - Accept non-space whitespace characters after the severity level in
3106 the `Log` option. Fixes bug 19965; bugfix on 0.2.1.1-alpha.
3107 - Support "TByte" and "TBytes" units in options given in bytes.
3108 "TB", "terabyte(s)", "TBit(s)" and "terabit(s)" were already
3109 supported. Fixes bug 20622; bugfix on 0.2.0.14-alpha.
3111 o Minor bugfixes (consensus weight):
3112 - Add new consensus method that initializes bw weights to 1 instead
3113 of 0. This prevents a zero weight from making it all the way to
3114 the end (happens in small testing networks) and causing an error.
3115 Fixes bug 14881; bugfix on 0.2.2.17-alpha.
3117 o Minor bugfixes (descriptors):
3118 - Correctly recognise downloaded full descriptors as valid, even
3119 when using microdescriptors as circuits. This affects clients with
3120 FetchUselessDescriptors set, and may affect directory authorities.
3121 Fixes bug 20839; bugfix on 0.2.3.2-alpha.
3123 o Minor bugfixes (directory system):
3124 - Download all consensus flavors, descriptors, and authority
3125 certificates when FetchUselessDescriptors is set, regardless of
3126 whether tor is a directory cache or not. Fixes bug 20667; bugfix
3127 on all recent tor versions.
3128 - Bridges and relays now use microdescriptors (like clients do)
3129 rather than old-style router descriptors. Now bridges will blend
3130 in with clients in terms of the circuits they build. Fixes bug
3131 6769; bugfix on 0.2.3.2-alpha.
3133 o Minor bugfixes (ed25519 certificates):
3134 - Correctly interpret ed25519 certificates that would expire some
3135 time after 19 Jan 2038. Fixes bug 20027; bugfix on 0.2.7.2-alpha.
3137 o Minor bugfixes (hidden services):
3138 - Stop ignoring misconfigured hidden services. Instead, refuse to
3139 start tor until the misconfigurations have been corrected. Fixes
3140 bug 20559; bugfix on multiple commits in 0.2.7.1-alpha
3143 o Minor bugfixes (memory leak at exit):
3144 - Fix a small harmless memory leak at exit of the previously unused
3145 RSA->Ed identity cross-certificate. Fixes bug 17779; bugfix
3148 o Minor bugfixes (util):
3149 - When finishing writing a file to disk, if we were about to replace
3150 the file with the temporary file created before and we fail to
3151 replace it, remove the temporary file so it doesn't stay on disk.
3152 Fixes bug 20646; bugfix on tor-0.2.0.7-alpha. Patch by fk.
3154 o Minor bugfixes (Windows):
3155 - Check for getpagesize before using it to mmap files. This fixes
3156 compilation in some MinGW environments. Fixes bug 20530; bugfix on
3157 0.1.2.1-alpha. Reported by "ice".
3159 o Code simplification and refactoring:
3160 - Abolish all global guard context in entrynodes.c; replace with new
3161 guard_selection_t structure as preparation for proposal 271.
3162 Closes ticket 19858.
3163 - Introduce rend_service_is_ephemeral() that tells if given onion
3164 service is ephemeral. Replace unclear NULL-checkings for service
3165 directory with this function. Closes ticket 20526.
3166 - Extract magic numbers in circuituse.c into defined variables.
3167 - Refactor circuit_is_available_for_use to remove unnecessary check.
3168 - Refactor circuit_predict_and_launch_new for readability and
3169 testability. Closes ticket 18873.
3170 - Refactor large if statement in purpose_needs_anonymity to use
3171 switch statement instead. Closes part of ticket 20077.
3172 - Refactor the hashing API to return negative values for errors, as
3173 is done as throughout the codebase. Closes ticket 20717.
3174 - Remove data structures that were used to index or_connection
3175 objects by their RSA identity digests. These structures are fully
3176 redundant with the similar structures used in the
3177 channel abstraction.
3178 - Remove duplicate code in the channel_write_*cell() functions.
3179 Closes ticket 13827; patch from Pingl.
3180 - Remove redundant behavior of is_sensitive_dir_purpose, refactor to
3181 use only purpose_needs_anonymity. Closes part of ticket 20077.
3182 - The code to generate and parse EXTEND and EXTEND2 cells has been
3183 replaced with code automatically generated by the
3187 - Include the "TBits" unit in Tor's man page. Fixes part of bug
3188 20622; bugfix on tor-0.2.5.1-alpha.
3189 - Change '1' to 'weight_scale' in consensus bw weights calculation
3190 comments, as that is reality. Closes ticket 20273. Patch
3192 - Correct the value for AuthDirGuardBWGuarantee in the manpage, from
3193 250 KBytes to 2 MBytes. Fixes bug 20435; bugfix
3194 on tor-0.2.5.6-alpha.
3195 - Stop the man page from incorrectly stating that HiddenServiceDir
3196 must already exist. Fixes 20486.
3197 - Clarify that when ClientRejectInternalAddresses is enabled (which
3198 is the default), multicast DNS hostnames for machines on the local
3199 network (of the form *.local) are also rejected. Closes
3203 - The AuthDirMaxServersPerAuthAddr option no longer exists: The same
3204 limit for relays running on a single IP applies to authority IP
3205 addresses as well as to non-authority IP addresses. Closes
3207 - The UseDirectoryGuards torrc option no longer exists: all users
3208 that use entry guards will also use directory guards. Related to
3209 proposal 271; implements part of ticket 20831.
3212 - New unit tests for tor_htonll(). Closes ticket 19563. Patch
3213 from "overcaffeinated".
3214 - Perform the coding style checks when running the tests and fail
3215 when coding style violations are found. Closes ticket 5500.
3216 - Add tests for networkstatus_compute_bw_weights_v10.
3217 - Add unit tests circuit_predict_and_launch_new.
3218 - Extract dummy_origin_circuit_new so it can be used by other
3222 Changes in version 0.2.8.12 - 2016-12-19
3223 Tor 0.2.8.12 backports a fix for a medium-severity issue (bug 21018
3224 below) where Tor clients could crash when attempting to visit a
3225 hostile hidden service. Clients are recommended to upgrade as packages
3226 become available for their systems.
3228 It also includes an updated list of fallback directories, backported
3231 Now that the Tor 0.2.9 series is stable, only major bugfixes will be
3232 backported to 0.2.8 in the future.
3234 o Major bugfixes (parsing, security, backported from 0.2.9.8):
3235 - Fix a bug in parsing that could cause clients to read a single
3236 byte past the end of an allocated region. This bug could be used
3237 to cause hardened clients (built with --enable-expensive-hardening)
3238 to crash if they tried to visit a hostile hidden service. Non-
3239 hardened clients are only affected depending on the details of
3240 their platform's memory allocator. Fixes bug 21018; bugfix on
3241 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3242 2016-12-002 and as CVE-2016-1254.
3244 o Minor features (fallback directory list, backported from 0.2.9.8):
3245 - Replace the 81 remaining fallbacks of the 100 originally
3246 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
3247 fallbacks (123 new, 54 existing, 27 removed) generated in December
3248 2016. Resolves ticket 20170.
3250 o Minor features (geoip, backported from 0.2.9.7-rc):
3251 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
3255 Changes in version 0.2.9.8 - 2016-12-19
3256 Tor 0.2.9.8 is the first stable release of the Tor 0.2.9 series.
3258 The Tor 0.2.9 series makes mandatory a number of security features
3259 that were formerly optional. It includes support for a new shared-
3260 randomness protocol that will form the basis for next generation
3261 hidden services, includes a single-hop hidden service mode for
3262 optimizing .onion services that don't actually want to be hidden,
3263 tries harder not to overload the directory authorities with excessive
3264 downloads, and supports a better protocol versioning scheme for
3265 improved compatibility with other implementations of the Tor protocol.
3267 And of course, there are numerous other bugfixes and improvements.
3269 This release also includes a fix for a medium-severity issue (bug
3270 21018 below) where Tor clients could crash when attempting to visit a
3271 hostile hidden service. Clients are recommended to upgrade as packages
3272 become available for their systems.
3274 Below are the changes since 0.2.9.7-rc. For a list of all changes
3275 since 0.2.8, see the ReleaseNotes file.
3277 o Major bugfixes (parsing, security):
3278 - Fix a bug in parsing that could cause clients to read a single
3279 byte past the end of an allocated region. This bug could be used
3280 to cause hardened clients (built with --enable-expensive-hardening)
3281 to crash if they tried to visit a hostile hidden service. Non-
3282 hardened clients are only affected depending on the details of
3283 their platform's memory allocator. Fixes bug 21018; bugfix on
3284 0.2.0.8-alpha. Found by using libFuzzer. Also tracked as TROVE-
3285 2016-12-002 and as CVE-2016-1254.
3287 o Minor features (fallback directory list):
3288 - Replace the 81 remaining fallbacks of the 100 originally
3289 introduced in Tor 0.2.8.3-alpha in March 2016, with a list of 177
3290 fallbacks (123 new, 54 existing, 27 removed) generated in December
3291 2016. Resolves ticket 20170.
3294 Changes in version 0.2.9.7-rc - 2016-12-12
3295 Tor 0.2.9.7-rc fixes a few small bugs remaining in Tor 0.2.9.6-rc,
3296 including a few that had prevented tests from passing on
3299 o Minor features (geoip):
3300 - Update geoip and geoip6 to the December 7 2016 Maxmind GeoLite2
3303 o Minor bugfix (build):
3304 - The current Git revision when building from a local repository is
3305 now detected correctly when using git worktrees. Fixes bug 20492;
3306 bugfix on 0.2.3.9-alpha.
3308 o Minor bugfixes (directory authority):
3309 - When computing old Tor protocol line version in protover, we were
3310 looking at 0.2.7.5 twice instead of a specific case for
3311 0.2.9.1-alpha. Fixes bug 20810; bugfix on 0.2.9.4-alpha.
3313 o Minor bugfixes (download scheduling):
3314 - Resolve a "bug" warning when considering a download schedule whose
3315 delay had approached INT_MAX. Fixes 20875; bugfix on 0.2.9.5-alpha.
3317 o Minor bugfixes (logging):
3318 - Downgrade a harmless log message about the
3319 pending_entry_connections list from "warn" to "info". Mitigates
3322 o Minor bugfixes (memory leak):
3323 - Fix a small memory leak when receiving AF_UNIX connections on a
3324 SocksPort. Fixes bug 20716; bugfix on 0.2.6.3-alpha.
3325 - When moving a signed descriptor object from a source to an
3326 existing destination, free the allocated memory inside that
3327 destination object. Fixes bug 20715; bugfix on 0.2.8.3-alpha.
3329 o Minor bugfixes (memory leak, use-after-free, linux seccomp2 sandbox):
3330 - Fix a memory leak and use-after-free error when removing entries
3331 from the sandbox's getaddrinfo() cache. Fixes bug 20710; bugfix on
3332 0.2.5.5-alpha. Patch from "cypherpunks".
3334 o Minor bugfixes (portability):
3335 - Use the correct spelling of MAC_OS_X_VERSION_10_12 on configure.ac
3336 Fixes bug 20935; bugfix on 0.2.9.6-rc.
3338 o Minor bugfixes (unit tests):
3339 - Stop expecting NetBSD unit tests to report success for ipfw. Part
3340 of a fix for bug 19960; bugfix on 0.2.9.5-alpha.
3341 - Fix tolerances in unit tests for monotonic time comparisons
3342 between nanoseconds and microseconds. Previously, we accepted a 10
3343 us difference only, which is not realistic on every platform's
3344 clock_gettime(). Fixes bug 19974; bugfix on 0.2.9.1-alpha.
3345 - Remove a double-free in the single onion service unit test. Stop
3346 ignoring a return value. Make future changes less error-prone.
3347 Fixes bug 20864; bugfix on 0.2.9.6-rc.
3350 Changes in version 0.2.8.11 - 2016-12-08
3351 Tor 0.2.8.11 backports fixes for additional portability issues that
3352 could prevent Tor from building correctly on OSX Sierra, or with
3353 OpenSSL 1.1. Affected users should upgrade; others can safely stay
3356 o Minor bugfixes (portability):
3357 - Avoid compilation errors when building on OSX Sierra. Sierra began
3358 to support the getentropy() and clock_gettime() APIs, but created
3359 a few problems in doing so. Tor 0.2.9 has a more thorough set of
3360 workarounds; in 0.2.8, we are just using the /dev/urandom and mach
3361 monotonic time interfaces. Fixes bug 20865. Bugfix
3364 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
3365 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
3366 architectures. Closes ticket 20588.
3369 Changes in version 0.2.8.10 - 2016-12-02
3370 Tor 0.2.8.10 backports a fix for a bug that would sometimes make clients
3371 unusable after they left standby mode. It also backports fixes for
3372 a few portability issues and a small but problematic memory leak.
3374 o Major bugfixes (client reliability, backport from 0.2.9.5-alpha):
3375 - When Tor leaves standby because of a new application request, open
3376 circuits as needed to serve that request. Previously, we would
3377 potentially wait a very long time. Fixes part of bug 19969; bugfix
3380 o Major bugfixes (client performance, backport from 0.2.9.5-alpha):
3381 - Clients now respond to new application stream requests immediately
3382 when they arrive, rather than waiting up to one second before
3383 starting to handle them. Fixes part of bug 19969; bugfix
3386 o Minor bugfixes (portability, backport from 0.2.9.6-rc):
3387 - Work around a bug in the OSX 10.12 SDK that would prevent us from
3388 successfully targeting earlier versions of OSX. Resolves
3391 o Minor bugfixes (portability, backport from 0.2.9.5-alpha):
3392 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
3393 20551; bugfix on 0.2.1.1-alpha.
3395 o Minor bugfixes (relay, backport from 0.2.9.5-alpha):
3396 - Work around a memory leak in OpenSSL 1.1 when encoding public
3397 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
3399 o Minor features (geoip):
3400 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
3403 Changes in version 0.2.9.6-rc - 2016-12-02
3404 Tor 0.2.9.6-rc fixes a few remaining bugs found in the previous alpha
3405 version. We hope that it will be ready to become stable soon, and we
3406 encourage everyone to test this release. If no showstopper bugs are
3407 found here, the next 0.2.9 release will be stable.
3409 o Major bugfixes (relay, resolver, logging):
3410 - For relays that don't know their own address, avoid attempting a
3411 local hostname resolve for each descriptor we download. This
3412 will cut down on the number of "Success: chose address 'x.x.x.x'"
3413 log lines, and also avoid confusing clock jumps if the resolver
3414 is slow. Fixes bugs 20423 and 20610; bugfix on 0.2.8.1-alpha.
3416 o Minor bugfixes (client, fascistfirewall):
3417 - Avoid spurious warnings when ReachableAddresses or FascistFirewall
3418 is set. Fixes bug 20306; bugfix on 0.2.8.2-alpha.
3420 o Minor bugfixes (hidden services):
3421 - Stop ignoring the anonymity status of saved keys for hidden
3422 services and single onion services when first starting tor.
3423 Instead, refuse to start tor if any hidden service key has been
3424 used in a different hidden service anonymity mode. Fixes bug
3425 20638; bugfix on 17178 in 0.2.9.3-alpha; reported by ahf.
3427 o Minor bugfixes (portability):
3428 - Work around a bug in the OSX 10.12 SDK that would prevent us from
3429 successfully targeting earlier versions of OSX. Resolves
3431 - Run correctly when built on Windows build environments that
3432 require _vcsprintf(). Fixes bug 20560; bugfix on 0.2.2.11-alpha.
3434 o Minor bugfixes (single onion services, Tor2web):
3435 - Stop complaining about long-term one-hop circuits deliberately
3436 created by single onion services and Tor2web. These log messages
3437 are intended to diagnose issue 8387, which relates to circuits
3438 hanging around forever for no reason. Fixes bug 20613; bugfix on
3439 0.2.9.1-alpha. Reported by "pastly".
3441 o Minor bugfixes (unit tests):
3442 - Stop spurious failures in the local interface address discovery
3443 unit tests. Fixes bug 20634; bugfix on 0.2.8.1-alpha; patch by
3447 - Correct the minimum bandwidth value in torrc.sample, and queue a
3448 corresponding change for torrc.minimal. Closes ticket 20085.
3451 Changes in version 0.2.9.5-alpha - 2016-11-08
3452 Tor 0.2.9.5-alpha fixes numerous bugs discovered in the previous alpha
3453 version. We believe one or two probably remain, and we encourage
3454 everyone to test this release.
3456 o Major bugfixes (client performance):
3457 - Clients now respond to new application stream requests immediately
3458 when they arrive, rather than waiting up to one second before
3459 starting to handle them. Fixes part of bug 19969; bugfix
3462 o Major bugfixes (client reliability):
3463 - When Tor leaves standby because of a new application request, open
3464 circuits as needed to serve that request. Previously, we would
3465 potentially wait a very long time. Fixes part of bug 19969; bugfix
3468 o Major bugfixes (download scheduling):
3469 - When using an exponential backoff schedule, do not give up on
3470 downloading just because we have failed a bunch of times. Since
3471 each delay is longer than the last, retrying indefinitely won't
3472 hurt. Fixes bug 20536; bugfix on 0.2.9.1-alpha.
3473 - If a consensus expires while we are waiting for certificates to
3474 download, stop waiting for certificates.
3475 - If we stop waiting for certificates less than a minute after we
3476 started downloading them, do not consider the certificate download
3477 failure a separate failure. Fixes bug 20533; bugfix
3479 - Remove the maximum delay on exponential-backoff scheduling. Since
3480 we now allow an infinite number of failures (see ticket 20536), we
3481 must now allow the time to grow longer on each failure. Fixes part
3482 of bug 20534; bugfix on 0.2.9.1-alpha.
3483 - Make our initial download delays closer to those from 0.2.8. Fixes
3484 another part of bug 20534; bugfix on 0.2.9.1-alpha.
3485 - When determining when to download a directory object, handle times
3486 after 2038 if the operating system supports them. (Someday this
3487 will be important!) Fixes bug 20587; bugfix on 0.2.8.1-alpha.
3488 - When using exponential backoff in test networks, use a lower
3489 exponent, so the delays do not vary as much. This helps test
3490 networks bootstrap consistently. Fixes bug 20597; bugfix on 20499.
3492 o Minor features (geoip):
3493 - Update geoip and geoip6 to the November 3 2016 Maxmind GeoLite2
3496 o Minor bugfixes (client directory scheduling):
3497 - Treat "relay too busy to answer request" as a failed request and a
3498 reason to back off on our retry frequency. This is safe now that
3499 exponential backoffs retry indefinitely, and avoids a bug where we
3500 would reset our download schedule erroneously. Fixes bug 20593;
3501 bugfix on 0.2.9.1-alpha.
3503 o Minor bugfixes (client, logging):
3504 - Remove a BUG warning in circuit_pick_extend_handshake(). Instead,
3505 assume all nodes support EXTEND2. Use ntor whenever a key is
3506 available. Fixes bug 20472; bugfix on 0.2.9.3-alpha.
3507 - On DNSPort, stop logging a BUG warning on a failed hostname
3508 lookup. Fixes bug 19869; bugfix on 0.2.9.1-alpha.
3510 o Minor bugfixes (hidden services):
3511 - When configuring hidden services, check every hidden service
3512 directory's permissions. Previously, we only checked the last
3513 hidden service. Fixes bug 20529; bugfix the work to fix 13942
3516 o Minor bugfixes (portability):
3517 - Fix compilation with OpenSSL 1.1 and less commonly-used CPU
3518 architectures. Closes ticket 20588.
3519 - Use ECDHE ciphers instead of ECDH in tortls tests. LibreSSL has
3520 removed the ECDH ciphers which caused the tests to fail on
3521 platforms which use it. Fixes bug 20460; bugfix on 0.2.8.1-alpha.
3522 - Fix implicit conversion warnings under OpenSSL 1.1. Fixes bug
3523 20551; bugfix on 0.2.1.1-alpha.
3525 o Minor bugfixes (relay bootstrap):
3526 - Ensure relays don't make multiple connections during bootstrap.
3527 Fixes bug 20591; bugfix on 0.2.8.1-alpha.
3529 o Minor bugfixes (relay):
3530 - Work around a memory leak in OpenSSL 1.1 when encoding public
3531 keys. Fixes bug 20553; bugfix on 0.0.2pre8.
3532 - Avoid a small memory leak when informing worker threads about
3533 rotated onion keys. Fixes bug 20401; bugfix on 0.2.6.3-alpha.
3534 - Do not try to parallelize workers more than 16x without the user
3535 explicitly configuring us to do so, even if we do detect more than
3536 16 CPU cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
3538 o Minor bugfixes (single onion services):
3539 - Start correctly when creating a single onion service in a
3540 directory that did not previously exist. Fixes bug 20484; bugfix
3543 o Minor bugfixes (testing):
3544 - Avoid a unit test failure on systems with over 16 detectable CPU
3545 cores. Fixes bug 19968; bugfix on 0.2.3.1-alpha.
3548 - Clarify that setting HiddenServiceNonAnonymousMode requires you to
3549 also set "SOCKSPort 0". Fixes bug 20487; bugfix on 0.2.9.3-alpha.
3550 - Module-level documentation for several more modules. Closes
3551 tickets 19287 and 19290.
3554 Changes in version 0.2.8.9 - 2016-10-17
3555 Tor 0.2.8.9 backports a fix for a security hole in previous versions
3556 of Tor that would allow a remote attacker to crash a Tor client,
3557 hidden service, relay, or authority. All Tor users should upgrade to
3558 this version, or to 0.2.9.4-alpha. Patches will be released for older
3561 o Major features (security fixes, also in 0.2.9.4-alpha):
3562 - Prevent a class of security bugs caused by treating the contents
3563 of a buffer chunk as if they were a NUL-terminated string. At
3564 least one such bug seems to be present in all currently used
3565 versions of Tor, and would allow an attacker to remotely crash
3566 most Tor instances, especially those compiled with extra compiler
3567 hardening. With this defense in place, such bugs can't crash Tor,
3568 though we should still fix them as they occur. Closes ticket
3569 20384 (TROVE-2016-10-001).
3571 o Minor features (geoip):
3572 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
3576 Changes in version 0.2.9.4-alpha - 2016-10-17
3577 Tor 0.2.9.4-alpha fixes a security hole in previous versions of Tor
3578 that would allow a remote attacker to crash a Tor client, hidden
3579 service, relay, or authority. All Tor users should upgrade to this
3580 version, or to 0.2.8.9. Patches will be released for older versions
3583 Tor 0.2.9.4-alpha also adds numerous small features and fix-ups to
3584 previous versions of Tor, including the implementation of a feature to
3585 future- proof the Tor ecosystem against protocol changes, some bug
3586 fixes necessary for Tor Browser to use unix domain sockets correctly,
3587 and several portability improvements. We anticipate that this will be
3588 the last alpha in the Tor 0.2.9 series, and that the next release will
3589 be a release candidate.
3591 o Major features (security fixes):
3592 - Prevent a class of security bugs caused by treating the contents
3593 of a buffer chunk as if they were a NUL-terminated string. At
3594 least one such bug seems to be present in all currently used
3595 versions of Tor, and would allow an attacker to remotely crash
3596 most Tor instances, especially those compiled with extra compiler
3597 hardening. With this defense in place, such bugs can't crash Tor,
3598 though we should still fix them as they occur. Closes ticket
3599 20384 (TROVE-2016-10-001).
3601 o Major features (subprotocol versions):
3602 - Tor directory authorities now vote on a set of recommended
3603 subprotocol versions, and on a set of required subprotocol
3604 versions. Clients and relays that lack support for a _required_
3605 subprotocol version will not start; those that lack support for a
3606 _recommended_ subprotocol version will warn the user to upgrade.
3607 Closes ticket 19958; implements part of proposal 264.
3608 - Tor now uses "subprotocol versions" to indicate compatibility.
3609 Previously, versions of Tor looked at the declared Tor version of
3610 a relay to tell whether they could use a given feature. Now, they
3611 should be able to rely on its declared subprotocol versions. This
3612 change allows compatible implementations of the Tor protocol(s) to
3613 exist without pretending to be 100% bug-compatible with particular
3614 releases of Tor itself. Closes ticket 19958; implements part of
3617 o Minor feature (fallback directories):
3618 - Remove broken fallbacks from the hard-coded fallback directory
3619 list. Closes ticket 20190; patch by teor.
3621 o Minor features (client, directory):
3622 - Since authorities now omit all routers that lack the Running and
3623 Valid flags, we assume that any relay listed in the consensus must
3624 have those flags. Closes ticket 20001; implements part of
3627 o Minor features (compilation, portability):
3628 - Compile correctly on MacOS 10.12 (aka "Sierra"). Closes
3631 o Minor features (development tools, etags):
3632 - Teach the "make tags" Makefile target how to correctly find
3633 "MOCK_IMPL" function definitions. Patch from nherring; closes
3636 o Minor features (geoip):
3637 - Update geoip and geoip6 to the October 4 2016 Maxmind GeoLite2
3640 o Minor features (unix domain sockets):
3641 - When configuring a unix domain socket for a SocksPort,
3642 ControlPort, or Hidden service, you can now wrap the address in
3643 quotes, using C-style escapes inside the quotes. This allows unix
3644 domain socket paths to contain spaces.
3646 o Minor features (virtual addresses):
3647 - Increase the maximum number of bits for the IPv6 virtual network
3648 prefix from 16 to 104. In this way, the condition for address
3649 allocation is less restrictive. Closes ticket 20151; feature
3652 o Minor bugfixes (address discovery):
3653 - Stop reordering IP addresses returned by the OS. This makes it
3654 more likely that Tor will guess the same relay IP address every
3655 time. Fixes issue 20163; bugfix on 0.2.7.1-alpha, ticket 17027.
3656 Reported by René Mayrhofer, patch by "cypherpunks".
3658 o Minor bugfixes (client, unix domain sockets):
3659 - Disable IsolateClientAddr when using AF_UNIX backed SocksPorts as
3660 the client address is meaningless. Fixes bug 20261; bugfix
3663 o Minor bugfixes (compilation, OpenBSD):
3664 - Detect Libevent2 functions correctly on systems that provide
3665 libevent2, but where libevent1 is linked with -levent. Fixes bug
3666 19904; bugfix on 0.2.2.24-alpha. Patch from Rubiate.
3668 o Minor bugfixes (configuration):
3669 - When parsing quoted configuration values from the torrc file,
3670 handle windows line endings correctly. Fixes bug 19167; bugfix on
3671 0.2.0.16-alpha. Patch from "Pingl".
3673 o Minor bugfixes (getpass):
3674 - Defensively fix a non-triggerable heap corruption at do_getpass()
3675 to protect ourselves from mistakes in the future. Fixes bug
3676 19223; bugfix on 0.2.7.3-rc. Bug found by Guido Vranken, patch
3679 o Minor bugfixes (hidden service):
3680 - Allow hidden services to run on IPv6 addresses even when the
3681 IPv6Exit option is not set. Fixes bug 18357; bugfix
3685 - Add module-level internal documentation for 36 C files that
3686 previously didn't have a high-level overview. Closes ticket #20385.
3688 o Required libraries:
3689 - When building with OpenSSL, Tor now requires version 1.0.1 or
3690 later. OpenSSL 1.0.0 and earlier are no longer supported by the
3691 OpenSSL team, and should not be used. Closes ticket 20303.
3694 Changes in version 0.2.9.3-alpha - 2016-09-23
3695 Tor 0.2.9.3-alpha adds improved support for entities that want to make
3696 high-performance services available through the Tor .onion mechanism
3697 without themselves receiving anonymity as they host those services. It
3698 also tries harder to ensure that all steps on a circuit are using the
3699 strongest crypto possible, strengthens some TLS properties, and
3700 resolves several bugs -- including a pair of crash bugs from the 0.2.8
3701 series. Anybody running an earlier version of 0.2.9.x should upgrade.
3703 o Major bugfixes (crash, also in 0.2.8.8):
3704 - Fix a complicated crash bug that could affect Tor clients
3705 configured to use bridges when replacing a networkstatus consensus
3706 in which one of their bridges was mentioned. OpenBSD users saw
3707 more crashes here, but all platforms were potentially affected.
3708 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
3710 o Major bugfixes (relay, OOM handler, also in 0.2.8.8):
3711 - Fix a timing-dependent assertion failure that could occur when we
3712 tried to flush from a circuit after having freed its cells because
3713 of an out-of-memory condition. Fixes bug 20203; bugfix on
3714 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
3717 o Major features (circuit building, security):
3718 - Authorities, relays and clients now require ntor keys in all
3719 descriptors, for all hops (except for rare hidden service protocol
3720 cases), for all circuits, and for all other roles. Part of
3722 - Tor authorities, relays, and clients only use ntor, except for
3723 rare cases in the hidden service protocol. Part of ticket 19163.
3725 o Major features (single-hop "hidden" services):
3726 - Add experimental HiddenServiceSingleHopMode and
3727 HiddenServiceNonAnonymousMode options. When both are set to 1,
3728 every hidden service on a Tor instance becomes a non-anonymous
3729 Single Onion Service. Single Onions make one-hop (direct)
3730 connections to their introduction and renzedvous points. One-hop
3731 circuits make Single Onion servers easily locatable, but clients
3732 remain location-anonymous. This is compatible with the existing
3733 hidden service implementation, and works on the current tor
3734 network without any changes to older relays or clients. Implements
3735 proposal 260, completes ticket 17178. Patch by teor and asn.
3737 o Major features (resource management):
3738 - Tor can now notice it is about to run out of sockets, and
3739 preemptively close connections of lower priority. (This feature is
3740 off by default for now, since the current prioritizing method is
3741 yet not mature enough. You can enable it by setting
3742 "DisableOOSCheck 0", but watch out: it might close some sockets
3743 you would rather have it keep.) Closes ticket 18640.
3745 o Major bugfixes (circuit building):
3746 - Hidden service client-to-intro-point and service-to-rendezvous-
3747 point circuits use the TAP key supplied by the protocol, to avoid
3748 epistemic attacks. Fixes bug 19163; bugfix on 0.2.4.18-rc.
3750 o Major bugfixes (compilation, OpenBSD):
3751 - Fix a Libevent-detection bug in our autoconf script that would
3752 prevent Tor from linking successfully on OpenBSD. Patch from
3753 rubiate. Fixes bug 19902; bugfix on 0.2.9.1-alpha.
3755 o Major bugfixes (hidden services):
3756 - Clients now require hidden services to include the TAP keys for
3757 their intro points in the hidden service descriptor. This prevents
3758 an inadvertent upgrade to ntor, which a malicious hidden service
3759 could use to distinguish clients by consensus version. Fixes bug
3760 20012; bugfix on 0.2.4.8-alpha. Patch by teor.
3762 o Minor features (security, TLS):
3763 - Servers no longer support clients that without AES ciphersuites.
3764 (3DES is no longer considered an acceptable cipher.) We believe
3765 that no such Tor clients currently exist, since Tor has required
3766 OpenSSL 0.9.7 or later since 2009. Closes ticket 19998.
3768 o Minor feature (fallback directories):
3769 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
3770 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
3771 2016. Closes ticket 20190; patch by teor.
3773 o Minor features (geoip, also in 0.2.8.8):
3774 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
3777 o Minor feature (port flags):
3778 - Add new flags to the *Port options to finer control over which
3779 requests are allowed. The flags are NoDNSRequest, NoOnionTraffic,
3780 and the synthetic flag OnionTrafficOnly, which is equivalent to
3781 NoDNSRequest, NoIPv4Traffic, and NoIPv6Traffic. Closes enhancement
3782 18693; patch by "teor".
3784 o Minor features (directory authority):
3785 - After voting, if the authorities decide that a relay is not
3786 "Valid", they no longer include it in the consensus at all. Closes
3787 ticket 20002; implements part of proposal 272.
3789 o Minor features (testing):
3790 - Disable memory protections on OpenBSD when performing our unit
3791 tests for memwipe(). The test deliberately invokes undefined
3792 behavior, and the OpenBSD protections interfere with this. Patch
3793 from "rubiate". Closes ticket 20066.
3795 o Minor features (testing, ipv6):
3796 - Add the single-onion and single-onion-ipv6 chutney targets to
3797 "make test-network-all". This requires a recent chutney version
3798 with the single onion network flavours (git c72a652 or later).
3799 Closes ticket 20072; patch by teor.
3800 - Add the hs-ipv6 chutney target to make test-network-all's IPv6
3801 tests. Remove bridges+hs, as it's somewhat redundant. This
3802 requires a recent chutney version that supports IPv6 clients,
3803 relays, and authorities. Closes ticket 20069; patch by teor.
3805 o Minor features (Tor2web):
3806 - Make Tor2web clients respect ReachableAddresses. This feature was
3807 inadvertently enabled in 0.2.8.6, then removed by bugfix 19973 on
3808 0.2.8.7. Implements feature 20034. Patch by teor.
3810 o Minor features (unit tests):
3811 - We've done significant work to make the unit tests run faster.
3812 - Our link-handshake unit tests now check that when invalid
3813 handshakes fail, they fail with the error messages we expected.
3814 - Our unit testing code that captures log messages no longer
3815 prevents them from being written out if the user asked for them
3816 (by passing --debug or --info or or --notice --warn to the "test"
3817 binary). This change prevents us from missing unexpected log
3818 messages simply because we were looking for others. Related to
3820 - The unit tests now log all warning messages with the "BUG" flag.
3821 Previously, they only logged errors by default. This change will
3822 help us make our testing code more correct, and make sure that we
3823 only hit this code when we mean to. In the meantime, however,
3824 there will be more warnings in the unit test logs than before.
3825 This is preparatory work for ticket 19999.
3826 - The unit tests now treat any failure of a "tor_assert_nonfatal()"
3827 assertion as a test failure.
3829 o Minor bug fixes (circuits):
3830 - Use the CircuitBuildTimeout option whenever
3831 LearnCircuitBuildTimeout is disabled. Previously, we would respect
3832 the option when a user disabled it, but not when it was disabled
3833 because some other option was set. Fixes bug 20073; bugfix on
3834 0.2.4.12-alpha. Patch by teor.
3836 o Minor bugfixes (allocation):
3837 - Change how we allocate memory for large chunks on buffers, to
3838 avoid a (currently impossible) integer overflow, and to waste less
3839 space when allocating unusually large chunks. Fixes bug 20081;
3840 bugfix on 0.2.0.16-alpha. Issue identified by Guido Vranken.
3841 - Always include orconfig.h before including any other C headers.
3842 Sometimes, it includes macros that affect the behavior of the
3843 standard headers. Fixes bug 19767; bugfix on 0.2.9.1-alpha (the
3844 first version to use AC_USE_SYSTEM_EXTENSIONS).
3845 - Fix a syntax error in the IF_BUG_ONCE__() macro in non-GCC-
3846 compatible compilers. Fixes bug 20141; bugfix on 0.2.9.1-alpha.
3847 Patch from Gisle Vanem.
3848 - Stop trying to build with Clang 4.0's -Wthread-safety warnings.
3849 They apparently require a set of annotations that we aren't
3850 currently using, and they create false positives in our pthreads
3851 wrappers. Fixes bug 20110; bugfix on 0.2.9.1-alpha.
3853 o Minor bugfixes (directory authority):
3854 - Die with a more useful error when the operator forgets to place
3855 the authority_signing_key file into the keys directory. This
3856 avoids an uninformative assert & traceback about having an invalid
3857 key. Fixes bug 20065; bugfix on 0.2.0.1-alpha.
3858 - When allowing private addresses, mark Exits that only exit to
3859 private locations as such. Fixes bug 20064; bugfix
3862 o Minor bugfixes (documentation):
3863 - Document the default PathsNeededToBuildCircuits value that's used
3864 by clients when the directory authorities don't set
3865 min_paths_for_circs_pct. Fixes bug 20117; bugfix on 02c320916e02
3866 in 0.2.4.10-alpha. Patch by teor, reported by Jesse V.
3867 - Fix manual for the User option: it takes a username, not a UID.
3868 Fixes bug 19122; bugfix on 0.0.2pre16 (the first version to have
3871 o Minor bugfixes (hidden services):
3872 - Stop logging intro point details to the client log on certain
3873 error conditions. Fixed as part of bug 20012; bugfix on
3874 0.2.4.8-alpha. Patch by teor.
3876 o Minor bugfixes (IPv6, testing):
3877 - Check for IPv6 correctly on Linux when running test networks.
3878 Fixes bug 19905; bugfix on 0.2.7.3-rc; patch by teor.
3880 o Minor bugfixes (Linux seccomp2 sandbox):
3881 - Add permission to run the sched_yield() and sigaltstack() system
3882 calls, in order to support versions of Tor compiled with asan or
3883 ubsan code that use these calls. Now "sandbox 1" and
3884 "--enable-expensive-hardening" should be compatible on more
3885 systems. Fixes bug 20063; bugfix on 0.2.5.1-alpha.
3887 o Minor bugfixes (logging):
3888 - When logging a message from the BUG() macro, be explicit about
3889 what we were asserting. Previously we were confusing what we were
3890 asserting with what the bug was. Fixes bug 20093; bugfix
3892 - When we are unable to remove the bw_accounting file, do not warn
3893 if the reason we couldn't remove it was that it didn't exist.
3894 Fixes bug 19964; bugfix on 0.2.5.4-alpha. Patch from 'pastly'.
3896 o Minor bugfixes (option parsing):
3897 - Count unix sockets when counting client listeners (SOCKS, Trans,
3898 NATD, and DNS). This has no user-visible behaviour changes: these
3899 options are set once, and never read. Required for correct
3900 behaviour in ticket 17178. Fixes bug 19677; bugfix on
3901 0.2.6.3-alpha. Patch by teor.
3903 o Minor bugfixes (options):
3904 - Check the consistency of UseEntryGuards and EntryNodes more
3905 reliably. Fixes bug 20074; bugfix on 0.2.4.12-alpha. Patch
3907 - Stop changing the configured value of UseEntryGuards on
3908 authorities and Tor2web clients. Fixes bug 20074; bugfix on
3909 commits 51fc6799 in 0.1.1.16-rc and acda1735 in 0.2.4.3-alpha.
3912 o Minor bugfixes (Tor2web):
3913 - Prevent Tor2web clients running hidden services, these services
3914 are not anonymous due to the one-hop client paths. Fixes bug
3915 19678. Patch by teor.
3917 o Minor bugfixes (unit tests):
3918 - Fix a shared-random unit test that was failing on big endian
3919 architectures due to internal representation of a integer copied
3920 to a buffer. The test is changed to take a full 32 bytes of data
3921 and use the output of a python script that make the COMMIT and
3922 REVEAL calculation according to the spec. Fixes bug 19977; bugfix
3924 - The tor_tls_server_info_callback unit test no longer crashes when
3925 debug-level logging is turned on. Fixes bug 20041; bugfix
3929 Changes in version 0.2.8.8 - 2016-09-23
3930 Tor 0.2.8.8 fixes two crash bugs present in previous versions of the
3931 0.2.8.x series. Relays running 0.2.8.x should upgrade, as should users
3932 who select public relays as their bridges.
3934 o Major bugfixes (crash):
3935 - Fix a complicated crash bug that could affect Tor clients
3936 configured to use bridges when replacing a networkstatus consensus
3937 in which one of their bridges was mentioned. OpenBSD users saw
3938 more crashes here, but all platforms were potentially affected.
3939 Fixes bug 20103; bugfix on 0.2.8.2-alpha.
3941 o Major bugfixes (relay, OOM handler):
3942 - Fix a timing-dependent assertion failure that could occur when we
3943 tried to flush from a circuit after having freed its cells because
3944 of an out-of-memory condition. Fixes bug 20203; bugfix on
3945 0.2.8.1-alpha. Thanks to "cypherpunks" for help diagnosing
3948 o Minor feature (fallback directories):
3949 - Remove 8 fallbacks that are no longer suitable, leaving 81 of the
3950 100 fallbacks originally introduced in Tor 0.2.8.2-alpha in March
3951 2016. Closes ticket 20190; patch by teor.
3953 o Minor features (geoip):
3954 - Update geoip and geoip6 to the September 6 2016 Maxmind GeoLite2
3958 Changes in version 0.2.9.2-alpha - 2016-08-24
3959 Tor 0.2.9.2-alpha continues development of the 0.2.9 series with
3960 several new features and bugfixes. It also includes an important
3961 authority update and an important bugfix from 0.2.8.7. Everyone who
3962 sets the ReachableAddresses option, and all bridges, are strongly
3963 encouraged to upgrade to 0.2.8.7, or to 0.2.9.2-alpha.
3965 o Directory authority changes (also in 0.2.8.7):
3966 - The "Tonga" bridge authority has been retired; the new bridge
3967 authority is "Bifroest". Closes tickets 19728 and 19690.
3969 o Major bugfixes (client, security, also in 0.2.8.7):
3970 - Only use the ReachableAddresses option to restrict the first hop
3971 in a path. In earlier versions of 0.2.8.x, it would apply to
3972 every hop in the path, with a possible degradation in anonymity
3973 for anyone using an uncommon ReachableAddress setting. Fixes bug
3974 19973; bugfix on 0.2.8.2-alpha.
3976 o Major features (user interface):
3977 - Tor now supports the ability to declare options deprecated, so
3978 that we can recommend that people stop using them. Previously,
3979 this was done in an ad-hoc way. Closes ticket 19820.
3981 o Major bugfixes (directory downloads):
3982 - Avoid resetting download status for consensuses hourly, since we
3983 already have another, smarter retry mechanism. Fixes bug 8625;
3984 bugfix on 0.2.0.9-alpha.
3986 o Minor features (config):
3987 - Warn users when descriptor and port addresses are inconsistent.
3988 Mitigates bug 13953; patch by teor.
3990 o Minor features (geoip):
3991 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
3994 o Minor features (user interface):
3995 - There is a new --list-deprecated-options command-line option to
3996 list all of the deprecated options. Implemented as part of
3999 o Minor bugfixes (code style):
4000 - Fix an integer signedness conversion issue in the case conversion
4001 tables. Fixes bug 19168; bugfix on 0.2.1.11-alpha.
4003 o Minor bugfixes (compilation):
4004 - Build correctly on versions of libevent2 without support for
4005 evutil_secure_rng_add_bytes(). Fixes bug 19904; bugfix
4007 - Fix a compilation warning on GCC versions before 4.6. Our
4008 ENABLE_GCC_WARNING macro used the word "warning" as an argument,
4009 when it is also required as an argument to the compiler pragma.
4010 Fixes bug 19901; bugfix on 0.2.9.1-alpha.
4012 o Minor bugfixes (compilation, also in 0.2.8.7):
4013 - Remove an inappropriate "inline" in tortls.c that was causing
4014 warnings on older versions of GCC. Fixes bug 19903; bugfix
4017 o Minor bugfixes (fallback directories, also in 0.2.8.7):
4018 - Avoid logging a NULL string pointer when loading fallback
4019 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
4020 and 0.2.8.1-alpha. Report and patch by "rubiate".
4022 o Minor bugfixes (logging):
4023 - Log a more accurate message when we fail to dump a microdescriptor.
4024 Fixes bug 17758; bugfix on 0.2.2.8-alpha. Patch from Daniel Pinto.
4026 o Minor bugfixes (memory leak):
4027 - Fix a series of slow memory leaks related to parsing torrc files
4028 and options. Fixes bug 19466; bugfix on 0.2.1.6-alpha.
4030 o Deprecated features:
4031 - A number of DNS-cache-related sub-options for client ports are now
4032 deprecated for security reasons, and may be removed in a future
4033 version of Tor. (We believe that client-side DNS cacheing is a bad
4034 idea for anonymity, and you should not turn it on.) The options
4035 are: CacheDNS, CacheIPv4DNS, CacheIPv6DNS, UseDNSCache,
4036 UseIPv4Cache, and UseIPv6Cache.
4037 - A number of options are deprecated for security reasons, and may
4038 be removed in a future version of Tor. The options are:
4039 AllowDotExit, AllowInvalidNodes, AllowSingleHopCircuits,
4040 AllowSingleHopExits, ClientDNSRejectInternalAddresses,
4041 CloseHSClientCircuitsImmediatelyOnTimeout,
4042 CloseHSServiceRendCircuitsImmediatelyOnTimeout,
4043 ExcludeSingleHopRelays, FastFirstHopPK, TLSECGroup,
4044 UseNTorHandshake, and WarnUnsafeSocks.
4045 - The *ListenAddress options are now deprecated as unnecessary: the
4046 corresponding *Port options should be used instead. These options
4047 may someday be removed. The affected options are:
4048 ControlListenAddress, DNSListenAddress, DirListenAddress,
4049 NATDListenAddress, ORListenAddress, SocksListenAddress,
4050 and TransListenAddress.
4053 - Correct the IPv6 syntax in our documentation for the
4054 VirtualAddrNetworkIPv6 torrc option. Closes ticket 19743.
4057 - We no longer include the (dead, deprecated) bufferevent code in
4058 Tor. Closes ticket 19450. Based on a patch from U+039b.
4061 Changes in version 0.2.8.7 - 2016-08-24
4062 Tor 0.2.8.7 fixes an important bug related to the ReachableAddresses
4063 option in 0.2.8.6, and replaces a retiring bridge authority. Everyone
4064 who sets the ReachableAddresses option, and all bridges, are strongly
4065 encouraged to upgrade.
4067 o Directory authority changes:
4068 - The "Tonga" bridge authority has been retired; the new bridge
4069 authority is "Bifroest". Closes tickets 19728 and 19690.
4071 o Major bugfixes (client, security):
4072 - Only use the ReachableAddresses option to restrict the first hop
4073 in a path. In earlier versions of 0.2.8.x, it would apply to
4074 every hop in the path, with a possible degradation in anonymity
4075 for anyone using an uncommon ReachableAddress setting. Fixes bug
4076 19973; bugfix on 0.2.8.2-alpha.
4078 o Minor features (geoip):
4079 - Update geoip and geoip6 to the August 2 2016 Maxmind GeoLite2
4082 o Minor bugfixes (compilation):
4083 - Remove an inappropriate "inline" in tortls.c that was causing
4084 warnings on older versions of GCC. Fixes bug 19903; bugfix
4087 o Minor bugfixes (fallback directories):
4088 - Avoid logging a NULL string pointer when loading fallback
4089 directory information. Fixes bug 19947; bugfix on 0.2.4.7-alpha
4090 and 0.2.8.1-alpha. Report and patch by "rubiate".
4093 Changes in version 0.2.9.1-alpha - 2016-08-08
4094 Tor 0.2.9.1-alpha is the first alpha release in the 0.2.9 development
4095 series. It improves our support for hardened builds and compiler
4096 warnings, deploys some critical infrastructure for improvements to
4097 hidden services, includes a new timing backend that we hope to use for
4098 better support for traffic padding, makes it easier for programmers to
4099 log unexpected events, and contains other small improvements to
4100 security, correctness, and performance.
4102 Below are the changes since 0.2.8.6.
4104 o New system requirements:
4105 - Tor now requires Libevent version 2.0.10-stable or later. Older
4106 versions of Libevent have less efficient backends for several
4107 platforms, and lack the DNS code that we use for our server-side
4108 DNS support. This implements ticket 19554.
4109 - Tor now requires zlib version 1.2 or later, for security,
4110 efficiency, and (eventually) gzip support. (Back when we started,
4111 zlib 1.1 and zlib 1.0 were still found in the wild. 1.2 was
4112 released in 2003. We recommend the latest version.)
4114 o Major features (build, hardening):
4115 - Tor now builds with -ftrapv by default on compilers that support
4116 it. This option detects signed integer overflow (which C forbids),
4117 and turns it into a hard-failure. We do not apply this option to
4118 code that needs to run in constant time to avoid side-channels;
4119 instead, we use -fwrapv in that code. Closes ticket 17983.
4120 - When --enable-expensive-hardening is selected, stop applying the
4121 clang/gcc sanitizers to code that needs to run in constant time.
4122 Although we are aware of no introduced side-channels, we are not
4123 able to prove that there are none. Related to ticket 17983.
4125 o Major features (compilation):
4126 - Our big list of extra GCC warnings is now enabled by default when
4127 building with GCC (or with anything like Clang that claims to be
4128 GCC-compatible). To make all warnings into fatal compilation
4129 errors, pass --enable-fatal-warnings to configure. Closes
4131 - Use the Autoconf macro AC_USE_SYSTEM_EXTENSIONS to automatically
4132 turn on C and POSIX extensions. (Previously, we attempted to do
4133 this on an ad hoc basis.) Closes ticket 19139.
4135 o Major features (directory authorities, hidden services):
4136 - Directory authorities can now perform the shared randomness
4137 protocol specified by proposal 250. Using this protocol, directory
4138 authorities generate a global fresh random value every day. In the
4139 future, this value will be used by hidden services to select
4140 HSDirs. This release implements the directory authority feature;
4141 the hidden service side will be implemented in the future as part
4142 of proposal 224. Resolves ticket 16943; implements proposal 250.
4144 o Major features (downloading, random exponential backoff):
4145 - When we fail to download an object from a directory service, wait
4146 for an (exponentially increasing) randomized amount of time before
4147 retrying, rather than a fixed interval as we did before. This
4148 prevents a group of Tor instances from becoming too synchronized,
4149 or a single Tor instance from becoming too predictable, in its
4150 download schedule. Closes ticket 15942.
4152 o Major bugfixes (exit policies):
4153 - Avoid disclosing exit outbound bind addresses, configured port
4154 bind addresses, and local interface addresses in relay descriptors
4155 by default under ExitPolicyRejectPrivate. Instead, only reject
4156 these (otherwise unlisted) addresses if
4157 ExitPolicyRejectLocalInterfaces is set. Fixes bug 18456; bugfix on
4158 0.2.7.2-alpha. Patch by teor.
4160 o Major bugfixes (hidden service client):
4161 - Allow Tor clients with appropriate controllers to work with
4162 FetchHidServDescriptors set to 0. Previously, this option also
4163 disabled descriptor cache lookup, thus breaking hidden services
4164 entirely. Fixes bug 18704; bugfix on 0.2.0.20-rc. Patch by "twim".
4166 o Minor features (build, hardening):
4167 - Detect and work around a libclang_rt problem that would prevent
4168 clang from finding __mulodi4() on some 32-bit platforms, and thus
4169 keep -ftrapv from linking on those systems. Closes ticket 19079.
4170 - When building on a system without runtime support for the runtime
4171 hardening options, try to log a useful warning at configuration
4172 time, rather than an incomprehensible warning at link time. If
4173 expensive hardening was requested, this warning becomes an error.
4174 Closes ticket 18895.
4176 o Minor features (code safety):
4177 - In our integer-parsing functions, ensure that maxiumum value we
4178 give is no smaller than the minimum value. Closes ticket 19063;
4181 o Minor features (controller):
4182 - Implement new GETINFO queries for all downloads that use
4183 download_status_t to schedule retries. This allows controllers to
4184 examine the schedule for pending downloads. Closes ticket 19323.
4185 - Allow controllers to configure basic client authorization on
4186 hidden services when they create them with the ADD_ONION control
4187 command. Implements ticket 15588. Patch by "special".
4188 - Fire a STATUS_SERVER controller event whenever the hibernation
4189 status changes between "awake"/"soft"/"hard". Closes ticket 18685.
4191 o Minor features (directory authority):
4192 - Directory authorities now only give the Guard flag to a relay if
4193 they are also giving it the Stable flag. This change allows us to
4194 simplify path selection for clients. It should have minimal effect
4195 in practice, since >99% of Guards already have the Stable flag.
4196 Implements ticket 18624.
4197 - Directory authorities now write their v3-status-votes file out to
4198 disk earlier in the consensus process, so we have a record of the
4199 votes even if we abort the consensus process. Resolves
4202 o Minor features (hidden service):
4203 - Stop being so strict about the payload length of "rendezvous1"
4204 cells. We used to be locked in to the "TAP" handshake length, and
4205 now we can handle better handshakes like "ntor". Resolves
4208 o Minor features (infrastructure, time):
4209 - Tor now uses the operating system's monotonic timers (where
4210 available) for internal fine-grained timing. Previously we would
4211 look at the system clock, and then attempt to compensate for the
4212 clock running backwards. Closes ticket 18908.
4213 - Tor now includes an improved timer backend, so that we can
4214 efficiently support tens or hundreds of thousands of concurrent
4215 timers, as will be needed for some of our planned anti-traffic-
4216 analysis work. This code is based on William Ahern's "timeout.c"
4217 project, which implements a "tickless hierarchical timing wheel".
4218 Closes ticket 18365.
4220 o Minor features (logging):
4221 - Provide a more useful warning message when configured with an
4222 invalid Nickname. Closes ticket 18300; patch from "icanhasaccount".
4223 - When dumping unparseable router descriptors, optionally store them
4224 in separate files, named by digest, up to a configurable size
4225 limit. You can change the size limit by setting the
4226 MaxUnparseableDescSizeToLog option, and disable this feature by
4227 setting that option to 0. Closes ticket 18322.
4228 - Add a set of macros to check nonfatal assertions, for internal
4229 use. Migrating more of our checks to these should help us avoid
4230 needless crash bugs. Closes ticket 18613.
4232 o Minor features (performance):
4233 - Changer the "optimistic data" extension from "off by default" to
4234 "on by default". The default was ordinarily overridden by a
4235 consensus option, but when clients were bootstrapping for the
4236 first time, they would not have a consensus to get the option
4237 from. Changing this default When fetching a consensus for the
4238 first time, use optimistic data. This saves a round-trip during
4239 startup. Closes ticket 18815.
4241 o Minor features (relay, usability):
4242 - When the directory authorities refuse a bad relay's descriptor,
4243 encourage the relay operator to contact us. Many relay operators
4244 won't notice this line in their logs, but it's a win if even a few
4245 learn why we don't like what their relay was doing. Resolves
4248 o Minor features (testing):
4249 - Let backtrace tests work correctly under AddressSanitizer. Fixes
4250 part of bug 18934; bugfix on 0.2.5.2-alpha.
4251 - Move the test-network.sh script to chutney, and modify tor's test-
4252 network.sh to call the (newer) chutney version when available.
4253 Resolves ticket 19116. Patch by teor.
4254 - Use the lcov convention for marking lines as unreachable, so that
4255 we don't count them when we're generating test coverage data.
4256 Update our coverage tools to understand this convention. Closes
4259 o Minor bugfixes (bootstrap):
4260 - Remember the directory we fetched the consensus or previous
4261 certificates from, and use it to fetch future authority
4262 certificates. This change improves bootstrapping performance.
4263 Fixes bug 18963; bugfix on 0.2.8.1-alpha.
4265 o Minor bugfixes (build):
4266 - The test-stem and test-network makefile targets now depend only on
4267 the tor binary that they are testing. Previously, they depended on
4268 "make all". Fixes bug 18240; bugfix on 0.2.8.2-alpha. Based on a
4269 patch from "cypherpunks".
4271 o Minor bugfixes (circuits):
4272 - Make sure extend_info_from_router() is only called on servers.
4273 Fixes bug 19639; bugfix on 0.2.8.1-alpha.
4275 o Minor bugfixes (compilation):
4276 - When building with Clang, use a full set of GCC warnings.
4277 (Previously, we included only a subset, because of the way we
4278 detected them.) Fixes bug 19216; bugfix on 0.2.0.1-alpha.
4280 o Minor bugfixes (directory authority):
4281 - Authorities now sort the "package" lines in their votes, for ease
4282 of debugging. (They are already sorted in consensus documents.)
4283 Fixes bug 18840; bugfix on 0.2.6.3-alpha.
4284 - When parsing a detached signature, make sure we use the length of
4285 the digest algorithm instead of an hardcoded DIGEST256_LEN in
4286 order to avoid comparing bytes out-of-bounds with a smaller digest
4287 length such as SHA1. Fixes bug 19066; bugfix on 0.2.2.6-alpha.
4289 o Minor bugfixes (documentation):
4290 - Document the --passphrase-fd option in the tor manpage. Fixes bug
4291 19504; bugfix on 0.2.7.3-rc.
4292 - Fix the description of the --passphrase-fd option in the
4293 tor-gencert manpage. The option is used to pass the number of a
4294 file descriptor to read the passphrase from, not to read the file
4295 descriptor from. Fixes bug 19505; bugfix on 0.2.0.20-alpha.
4297 o Minor bugfixes (ephemeral hidden service):
4298 - When deleting an ephemeral hidden service, close its intro points
4299 even if they are not completely open. Fixes bug 18604; bugfix
4302 o Minor bugfixes (guard selection):
4303 - Use a single entry guard even if the NumEntryGuards consensus
4304 parameter is not provided. Fixes bug 17688; bugfix
4306 - Don't mark guards as unreachable if connection_connect() fails.
4307 That function fails for local reasons, so it shouldn't reveal
4308 anything about the status of the guard. Fixes bug 14334; bugfix
4311 o Minor bugfixes (hidden service client):
4312 - Increase the minimum number of internal circuits we preemptively
4313 build from 2 to 3, so a circuit is available when a client
4314 connects to another onion service. Fixes bug 13239; bugfix
4317 o Minor bugfixes (logging):
4318 - When logging a directory ownership mismatch, log the owning
4319 username correctly. Fixes bug 19578; bugfix on 0.2.2.29-beta.
4321 o Minor bugfixes (memory leaks):
4322 - Fix a small, uncommon memory leak that could occur when reading a
4323 truncated ed25519 key file. Fixes bug 18956; bugfix
4326 o Minor bugfixes (testing):
4327 - Allow clients to retry HSDirs much faster in test networks. Fixes
4328 bug 19702; bugfix on 0.2.7.1-alpha. Patch by teor.
4329 - Disable ASAN's detection of segmentation faults while running
4330 test_bt.sh, so that we can make sure that our own backtrace
4331 generation code works. Fixes another aspect of bug 18934; bugfix
4332 on 0.2.5.2-alpha. Patch from "cypherpunks".
4333 - Fix the test-network-all target on out-of-tree builds by using the
4334 correct path to the test driver script. Fixes bug 19421; bugfix
4337 o Minor bugfixes (time):
4338 - Improve overflow checks in tv_udiff and tv_mdiff. Fixes bug 19483;
4339 bugfix on all released tor versions.
4340 - When computing the difference between two times in milliseconds,
4341 we now round to the nearest millisecond correctly. Previously, we
4342 could sometimes round in the wrong direction. Fixes bug 19428;
4343 bugfix on 0.2.2.2-alpha.
4345 o Minor bugfixes (user interface):
4346 - Display a more accurate number of suppressed messages in the log
4347 rate-limiter. Previously, there was a potential integer overflow
4348 in the counter. Now, if the number of messages hits a maximum, the
4349 rate-limiter doesn't count any further. Fixes bug 19435; bugfix
4351 - Fix a typo in the passphrase prompt for the ed25519 identity key.
4352 Fixes bug 19503; bugfix on 0.2.7.2-alpha.
4354 o Code simplification and refactoring:
4355 - Remove redundant declarations of the MIN macro. Closes
4357 - Rename tor_dup_addr() to tor_addr_to_str_dup() to avoid confusion.
4358 Closes ticket 18462; patch from "icanhasaccount".
4359 - Split the 600-line directory_handle_command_get function into
4360 separate functions for different URL types. Closes ticket 16698.
4363 - Fix spelling of "--enable-tor2web-mode" in the manpage. Closes
4364 ticket 19153. Patch from "U+039b".
4367 - Remove support for "GET /tor/bytes.txt" DirPort request, and
4368 "GETINFO dir-usage" controller request, which were only available
4369 via a compile-time option in Tor anyway. Feature was added in
4370 0.2.2.1-alpha. Resolves ticket 19035.
4371 - There is no longer a compile-time option to disable support for
4372 TransPort. (If you don't want TransPort; just don't use it.) Patch
4373 from "U+039b". Closes ticket 19449.
4376 - Run more workqueue tests as part of "make check". These had
4377 previously been implemented, but you needed to know special
4378 command-line options to enable them.
4379 - We now have unit tests for our code to reject zlib "compression
4380 bombs". (Fortunately, the code works fine.)
4383 Changes in version 0.2.8.6 - 2016-08-02
4385 Tor 0.2.8.6 is the first stable version of the Tor 0.2.8 series.
4387 The Tor 0.2.8 series improves client bootstrapping performance,
4388 completes the authority-side implementation of improved identity
4389 keys for relays, and includes numerous bugfixes and performance
4390 improvements throughout the program. This release continues to
4391 improve the coverage of Tor's test suite. For a full list of
4392 changes since Tor 0.2.7, see the ReleaseNotes file.
4394 Changes since 0.2.8.5-rc:
4396 o Minor features (geoip):
4397 - Update geoip and geoip6 to the July 6 2016 Maxmind GeoLite2
4400 o Minor bugfixes (compilation):
4401 - Fix a compilation warning in the unit tests on systems where char
4402 is signed. Fixes bug 19682; bugfix on 0.2.8.1-alpha.
4404 o Minor bugfixes (fallback directories):
4405 - Remove 1 fallback that was on the hardcoded list, then opted-out,
4406 leaving 89 of the 100 fallbacks originally introduced in Tor
4407 0.2.8.2-alpha in March 2016. Closes ticket 19782; patch by teor.
4409 o Minor bugfixes (Linux seccomp2 sandbox):
4410 - Allow more syscalls when running with "Sandbox 1" enabled:
4411 sysinfo, getsockopt(SO_SNDBUF), and setsockopt(SO_SNDBUFFORCE). On
4412 some systems, these are required for Tor to start. Fixes bug
4413 18397; bugfix on 0.2.5.1-alpha. Patch from Daniel Pinto.
4414 - Allow IPPROTO_UDP datagram sockets when running with "Sandbox 1",
4415 so that get_interface_address6_via_udp_socket_hack() can work.
4416 Fixes bug 19660; bugfix on 0.2.5.1-alpha.
4419 Changes in version 0.2.8.5-rc - 2016-07-07
4420 Tor 0.2.8.5-rc is the second release candidate in the Tor 0.2.8
4421 series. If we find no new bugs or regressions here, the first stable
4422 0.2.8 release will be identical to it. It has a few small bugfixes
4423 against previous versions.
4425 o Directory authority changes:
4426 - Urras is no longer a directory authority. Closes ticket 19271.
4428 o Major bugfixes (heartbeat):
4429 - Fix a regression that would crash Tor when the periodic
4430 "heartbeat" log messages were disabled. Fixes bug 19454; bugfix on
4431 0.2.8.1-alpha. Reported by "kubaku".
4433 o Minor features (build):
4434 - Tor now again builds with the recent OpenSSL 1.1 development
4435 branch (tested against 1.1.0-pre6-dev). Closes ticket 19499.
4436 - When building manual pages, set the timezone to "UTC", so that the
4437 output is reproducible. Fixes bug 19558; bugfix on 0.2.2.9-alpha.
4438 Patch from intrigeri.
4440 o Minor bugfixes (fallback directory selection):
4441 - Avoid errors during fallback selection if there are no eligible
4442 fallbacks. Fixes bug 19480; bugfix on 0.2.8.3-alpha. Patch
4445 o Minor bugfixes (IPv6, microdescriptors):
4446 - Don't check node addresses when we only have a routerstatus. This
4447 allows IPv6-only clients to bootstrap by fetching microdescriptors
4448 from fallback directory mirrors. (The microdescriptor consensus
4449 has no IPv6 addresses in it.) Fixes bug 19608; bugfix
4452 o Minor bugfixes (logging):
4453 - Reduce pointlessly verbose log messages when directory servers
4454 can't be found. Fixes bug 18849; bugfix on 0.2.8.3-alpha and
4455 0.2.8.1-alpha. Patch by teor.
4456 - When a fallback directory changes its fingerprint from the hard-
4457 coded fingerprint, log a less severe, more explanatory log
4458 message. Fixes bug 18812; bugfix on 0.2.8.1-alpha. Patch by teor.
4460 o Minor bugfixes (Linux seccomp2 sandboxing):
4461 - Allow statistics to be written to disk when "Sandbox 1" is
4462 enabled. Fixes bugs 19556 and 19957; bugfix on 0.2.5.1-alpha and
4463 0.2.6.1-alpha respectively.
4465 o Minor bugfixes (user interface):
4466 - Remove a warning message "Service [scrubbed] not found after
4467 descriptor upload". This message appears when one uses HSPOST
4468 control command to upload a service descriptor. Since there is
4469 only a descriptor and no service, showing this message is
4470 pointless and confusing. Fixes bug 19464; bugfix on 0.2.7.2-alpha.
4472 o Fallback directory list:
4473 - Add a comment to the generated fallback directory list that
4474 explains how to comment out unsuitable fallbacks in a way that's
4475 compatible with the stem fallback parser.
4476 - Update fallback whitelist and blacklist based on relay operator
4477 emails. Blacklist unsuitable (non-working, over-volatile)
4478 fallbacks. Resolves ticket 19071. Patch by teor.
4479 - Remove 10 unsuitable fallbacks, leaving 90 of the 100 fallbacks
4480 originally introduced in Tor 0.2.8.2-alpha in March 2016. Closes
4481 ticket 19071; patch by teor.
4484 Changes in version 0.2.8.4-rc - 2016-06-15
4485 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
4486 If we find no new bugs or regressions here, the first stable 0.2.8
4487 release will be identical to it. It has a few small bugfixes against
4490 o Major bugfixes (user interface):
4491 - Correctly give a warning in the cases where a relay is specified
4492 by nickname, and one such relay is found, but it is not officially
4493 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
4495 o Minor features (build):
4496 - Tor now builds once again with the recent OpenSSL 1.1 development
4497 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
4499 o Minor features (geoip):
4500 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
4503 o Minor bugfixes (compilation):
4504 - Cause the unit tests to compile correctly on mingw64 versions that
4505 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
4507 o Minor bugfixes (downloading):
4508 - Predict more correctly whether we'll be downloading over HTTP when
4509 we determine the maximum length of a URL. This should avoid a
4510 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
4514 Changes in version 0.2.8.3-alpha - 2016-05-26
4515 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
4516 the course of the 0.2.8 development cycle. It improves the behavior of
4517 directory clients, fixes several crash bugs, fixes a gap in compiler
4518 hardening, and allows the full integration test suite to run on
4521 o Major bugfixes (security, client, DNS proxy):
4522 - Stop a crash that could occur when a client running with DNSPort
4523 received a query with multiple address types, and the first
4524 address type was not supported. Found and fixed by Scott Dial.
4525 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
4527 o Major bugfixes (security, compilation):
4528 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
4529 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
4530 cause a compiler warning, thereby making other checks fail, and
4531 needlessly disabling compiler-hardening support. Fixes one case of
4532 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
4534 o Major bugfixes (security, directory authorities):
4535 - Fix a crash and out-of-bounds write during authority voting, when
4536 the list of relays includes duplicate ed25519 identity keys. Fixes
4537 bug 19032; bugfix on 0.2.8.2-alpha.
4539 o Major bugfixes (client, bootstrapping):
4540 - Check if bootstrap consensus downloads are still needed when the
4541 linked connection attaches. This prevents tor making unnecessary
4542 begindir-style connections, which are the only directory
4543 connections tor clients make since the fix for 18483 was merged.
4544 - Fix some edge cases where consensus download connections may not
4545 have been closed, even though they were not needed. Related to fix
4547 - Make relays retry consensus downloads the correct number of times,
4548 rather than the more aggressive client retry count. Fixes part of
4550 - Stop downloading consensuses when we have a consensus, even if we
4551 don't have all the certificates for it yet. Fixes bug 18809;
4552 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
4554 o Major bugfixes (directory mirrors):
4555 - Decide whether to advertise begindir support in the the same way
4556 we decide whether to advertise our DirPort. Allowing these
4557 decisions to become out-of-sync led to surprising behavior like
4558 advertising begindir support when hibernation made us not
4559 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
4562 o Major bugfixes (IPv6 bridges, client):
4563 - Actually use IPv6 addresses when selecting directory addresses for
4564 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
4567 o Major bugfixes (key management):
4568 - If OpenSSL fails to generate an RSA key, do not retain a dangling
4569 pointer to the previous (uninitialized) key value. The impact here
4570 should be limited to a difficult-to-trigger crash, if OpenSSL is
4571 running an engine that makes key generation failures possible, or
4572 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
4573 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
4576 o Major bugfixes (testing):
4577 - Fix a bug that would block 'make test-network-all' on systems where
4578 IPv6 packets were lost. Fixes bug 19008; bugfix on 0.2.7.3-rc.
4579 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
4580 bugfix on 0.2.8.1-alpha.
4582 o Minor features (clients):
4583 - Make clients, onion services, and bridge relays always use an
4584 encrypted begindir connection for directory requests. Resolves
4585 ticket 18483. Patch by "teor".
4587 o Minor features (fallback directory mirrors):
4588 - Give each fallback the same weight for client selection; restrict
4589 fallbacks to one per operator; report fallback directory detail
4590 changes when rebuilding list; add new fallback directory mirrors
4591 to the whitelist; and many other minor simplifications and fixes.
4592 Closes tasks 17905, 18749, bug 18689, and fixes part of bug 18812 on
4593 0.2.8.1-alpha; patch by "teor".
4594 - Replace the 21 fallbacks generated in January 2016 and included in
4595 Tor 0.2.8.1-alpha, with a list of 100 fallbacks generated in March
4596 2016. Closes task 17158; patch by "teor".
4598 o Minor features (geoip):
4599 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
4602 o Minor bugfixes (assert, portability):
4603 - Fix an assertion failure in memarea.c on systems where "long" is
4604 shorter than the size of a pointer. Fixes bug 18716; bugfix
4607 o Minor bugfixes (bootstrap):
4608 - Consistently use the consensus download schedule for authority
4609 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
4611 o Minor bugfixes (build):
4612 - Remove a pair of redundant AM_CONDITIONAL declarations from
4613 configure.ac. Fixes one final case of bug 17744; bugfix
4615 - Resolve warnings when building on systems that are concerned with
4616 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
4618 - When libscrypt.h is found, but no libscrypt library can be linked,
4619 treat libscrypt as absent. Fixes bug 19161; bugfix
4622 o Minor bugfixes (client):
4623 - Turn all TestingClientBootstrap* into non-testing torrc options.
4624 This changes simply renames them by removing "Testing" in front of
4625 them and they do not require TestingTorNetwork to be enabled
4626 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
4627 - Make directory node selection more reliable, mainly for IPv6-only
4628 clients and clients with few reachable addresses. Fixes bug 18929;
4629 bugfix on 0.2.8.1-alpha. Patch by "teor".
4631 o Minor bugfixes (controller, microdescriptors):
4632 - Make GETINFO dir/status-vote/current/consensus conform to the
4633 control specification by returning "551 Could not open cached
4634 consensus..." when not caching consensuses. Fixes bug 18920;
4635 bugfix on 0.2.2.6-alpha.
4637 o Minor bugfixes (crypto, portability):
4638 - The SHA3 and SHAKE routines now produce the correct output on Big
4639 Endian systems. No code calls either algorithm yet, so this is
4640 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
4641 - Tor now builds again with the recent OpenSSL 1.1 development
4642 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
4645 o Minor bugfixes (directories):
4646 - When fetching extrainfo documents, compare their SHA256 digests
4647 and Ed25519 signing key certificates with the routerinfo that led
4648 us to fetch them, rather than with the most recent routerinfo.
4649 Otherwise we generate many spurious warnings about mismatches.
4650 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
4652 o Minor bugfixes (logging):
4653 - When we can't generate a signing key because OfflineMasterKey is
4654 set, do not imply that we should have been able to load it. Fixes
4655 bug 18133; bugfix on 0.2.7.2-alpha.
4656 - Stop periodic_event_dispatch() from blasting twelve lines per
4657 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
4658 - When rejecting a misformed INTRODUCE2 cell, only log at
4659 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
4661 o Minor bugfixes (pluggable transports):
4662 - Avoid reporting a spurious error when we decide that we don't need
4663 to terminate a pluggable transport because it has already exited.
4664 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
4666 o Minor bugfixes (pointer arithmetic):
4667 - Fix a bug in memarea_alloc() that could have resulted in remote
4668 heap write access, if Tor had ever passed an unchecked size to
4669 memarea_alloc(). Fortunately, all the sizes we pass to
4670 memarea_alloc() are pre-checked to be less than 128 kilobytes.
4671 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
4674 o Minor bugfixes (relays):
4675 - Consider more config options when relays decide whether to
4676 regenerate their descriptor. Fixes more of bug 12538; bugfix
4678 - Resolve some edge cases where we might launch an ORPort
4679 reachability check even when DisableNetwork is set. Noticed while
4680 fixing bug 18616; bugfix on 0.2.3.9-alpha.
4682 o Minor bugfixes (statistics):
4683 - We now include consensus downloads via IPv6 in our directory-
4684 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
4686 o Minor bugfixes (testing):
4687 - Allow directories in small networks to bootstrap by skipping
4688 DirPort checks when the consensus has no exits. Fixes bug 19003;
4689 bugfix on 0.2.8.1-alpha. Patch by teor.
4690 - Fix a small memory leak that would occur when the
4691 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
4692 bugfix on 0.2.5.2-alpha.
4694 o Minor bugfixes (time handling):
4695 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
4696 field. Otherwise, our unit tests crash on Windows. Fixes bug
4697 18977; bugfix on 0.2.2.25-alpha.
4700 - Document the contents of the 'datadir/keys' subdirectory in the
4701 manual page. Closes ticket 17621.
4702 - Stop recommending use of nicknames to identify relays in our
4703 MapAddress documentation. Closes ticket 18312.
4706 Changes in version 0.2.8.2-alpha - 2016-03-28
4707 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
4708 bugs in earlier versions of Tor, including some that prevented
4709 authorities using Tor 0.2.7.x from running correctly. IPv6 and
4710 directory support should also be much improved.
4712 o New system requirements:
4713 - Tor no longer supports versions of OpenSSL with a broken
4714 implementation of counter mode. (This bug was present in OpenSSL
4715 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
4716 longer runs with, these versions.
4717 - Tor no longer attempts to support platforms where the "time_t"
4718 type is unsigned. (To the best of our knowledge, only OpenVMS does
4719 this, and Tor has never actually built on OpenVMS.) Closes
4721 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
4722 later (released in 2008 and 2009 respectively). If you are
4723 building Tor from the git repository instead of from the source
4724 distribution, and your tools are older than this, you will need to
4725 upgrade. Closes ticket 17732.
4727 o Major bugfixes (security, pointers):
4728 - Avoid a difficult-to-trigger heap corruption attack when extending
4729 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
4730 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
4731 Reported by Guido Vranken.
4733 o Major bugfixes (bridges, pluggable transports):
4734 - Modify the check for OR connections to private addresses. Allow
4735 bridges on private addresses, including pluggable transports that
4736 ignore the (potentially private) address in the bridge line. Fixes
4737 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
4739 o Major bugfixes (compilation):
4740 - Repair hardened builds under the clang compiler. Previously, our
4741 use of _FORTIFY_SOURCE would conflict with clang's address
4742 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
4744 o Major bugfixes (crash on shutdown):
4745 - Correctly handle detaching circuits from muxes when shutting down.
4746 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
4747 - Fix an assert-on-exit bug related to counting memory usage in
4748 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
4750 o Major bugfixes (crash on startup):
4751 - Fix a segfault during startup: If a Unix domain socket was
4752 configured as listener (such as a ControlSocket or a SocksPort
4753 "unix:" socket), and tor was started as root but not configured to
4754 switch to another user, tor would segfault while trying to string
4755 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
4758 o Major bugfixes (dns proxy mode, crash):
4759 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
4760 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
4762 o Major bugfixes (relays, bridge clients):
4763 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
4764 bridge clients use the address configured in the bridge line.
4765 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
4768 o Major bugfixes (voting):
4769 - Actually enable support for authorities to match routers by their
4770 Ed25519 identities. Previously, the code had been written, but
4771 some debugging code that had accidentally been left in the
4772 codebase made it stay turned off. Fixes bug 17702; bugfix
4774 - When collating votes by Ed25519 identities, authorities now
4775 include a "NoEdConsensus" flag if the ed25519 value (or lack
4776 thereof) for a server does not reflect the majority consensus.
4777 Related to bug 17668; bugfix on 0.2.7.2-alpha.
4778 - When generating a vote with keypinning disabled, never include two
4779 entries for the same ed25519 identity. This bug was causing
4780 authorities to generate votes that they could not parse when a
4781 router violated key pinning by changing its RSA identity but
4782 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
4783 18318. Bugfix on 0.2.7.2-alpha.
4785 o Minor features (security, win32):
4786 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
4787 attack. Fixes bug 18123; bugfix on all tor versions. Patch
4790 o Minor features (bug-resistance):
4791 - Make Tor survive errors involving connections without a
4792 corresponding event object. Previously we'd fail with an
4793 assertion; now we produce a log message. Related to bug 16248.
4795 o Minor features (build):
4796 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
4797 as having possible IPFW support. Closes ticket 18448. Patch from
4800 o Minor features (code hardening):
4801 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
4802 level code, to harden against accidental failures to NUL-
4803 terminate. Part of ticket 17852. Patch from jsturgix. Found
4806 o Minor features (crypto):
4807 - Validate the hard-coded Diffie-Hellman parameters and ensure that
4808 p is a safe prime, and g is a suitable generator. Closes
4811 o Minor features (geoip):
4812 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
4815 o Minor features (hidden service directory):
4816 - Streamline relay-side hsdir handling: when relays consider whether
4817 to accept an uploaded hidden service descriptor, they no longer
4818 check whether they are one of the relays in the network that is
4819 "supposed" to handle that descriptor. Implements ticket 18332.
4821 o Minor features (IPv6):
4822 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
4823 to 1, tor prefers IPv6 directory addresses.
4824 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
4825 avoids using IPv4 for client OR and directory connections.
4826 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
4827 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
4828 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
4830 o Minor features (linux seccomp2 sandbox):
4831 - Reject attempts to change our Address with "Sandbox 1" enabled.
4832 Changing Address with Sandbox turned on would never actually work,
4833 but previously it would fail in strange and confusing ways. Found
4836 o Minor features (robustness):
4837 - Exit immediately with an error message if the code attempts to use
4838 Libevent without having initialized it. This should resolve some
4839 frequently-made mistakes in our unit tests. Closes ticket 18241.
4841 o Minor features (unix domain sockets):
4842 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
4843 Unix domain sockets without checking the permissions on the parent
4844 directory. (Tor checks permissions by default because some
4845 operating systems only check permissions on the parent directory.
4846 However, some operating systems do look at permissions on the
4847 socket, and tor's default check is unneeded.) Closes ticket 18458.
4850 o Minor bugfixes (exit policies, security):
4851 - Refresh an exit relay's exit policy when interface addresses
4852 change. Previously, tor only refreshed the exit policy when the
4853 configured external address changed. Fixes bug 18208; bugfix on
4854 0.2.7.3-rc. Patch by teor.
4856 o Minor bugfixes (security, hidden services):
4857 - Prevent hidden services connecting to client-supplied rendezvous
4858 addresses that are reserved as internal or multicast. Fixes bug
4859 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
4861 o Minor bugfixes (build):
4862 - Do not link the unit tests against both the testing and non-
4863 testing versions of the static libraries. Fixes bug 18490; bugfix
4865 - Avoid spurious failures from configure files related to calling
4866 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18626; bugfix on
4867 0.2.0.1-alpha. Patch from "cypherpunks".
4868 - Silence spurious clang-scan warnings in the ed25519_donna code by
4869 explicitly initializing some objects. Fixes bug 18384; bugfix on
4870 0.2.7.2-alpha. Patch by teor.
4872 o Minor bugfixes (client, bootstrap):
4873 - Count receipt of new microdescriptors as progress towards
4874 bootstrapping. Previously, with EntryNodes set, Tor might not
4875 successfully repopulate the guard set on bootstrapping. Fixes bug
4876 16825; bugfix on 0.2.3.1-alpha.
4878 o Minor bugfixes (code correctness):
4879 - Update to the latest version of Trunnel, which tries harder to
4880 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
4881 by clang address sanitizer. Fixes bug 18373; bugfix
4884 o Minor bugfixes (configuration):
4885 - Fix a tiny memory leak when parsing a port configuration ending in
4886 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
4888 o Minor bugfixes (containers):
4889 - If we somehow attempt to construct a heap with more than
4890 1073741822 elements, avoid an integer overflow when maintaining
4891 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
4893 o Minor bugfixes (correctness):
4894 - Fix a bad memory handling bug that would occur if we had queued a
4895 cell on a channel's incoming queue. Fortunately, we can't actually
4896 queue a cell like that as our code is constructed today, but it's
4897 best to avoid this kind of error, even if there isn't any code
4898 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
4900 o Minor bugfixes (directory):
4901 - When generating a URL for a directory server on an IPv6 address,
4902 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
4903 on 0.2.3.9-alpha. Patch from Malek.
4905 o Minor bugfixes (fallback directory mirrors):
4906 - When requesting extrainfo descriptors from a trusted directory
4907 server, check whether it is an authority or a fallback directory
4908 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
4909 0.2.4.7-alpha. Reported by atagar, patch by teor.
4911 o Minor bugfixes (hidden service, client):
4912 - Handle the case where the user makes several fast consecutive
4913 requests to the same .onion address. Previously, the first six
4914 requests would each trigger a descriptor fetch, each picking a
4915 directory (there are 6 overall) and the seventh one would fail
4916 because no directories were left, thereby triggering a close on
4917 all current directory connections asking for the hidden service.
4918 The solution here is to not close the connections if we have
4919 pending directory fetches. Fixes bug 15937; bugfix
4922 o Minor bugfixes (hidden service, control port):
4923 - Add the onion address to the HS_DESC event for the UPLOADED action
4924 both on success or failure. It was previously hardcoded with
4925 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
4927 o Minor bugfixes (hidden service, directory):
4928 - Bridges now refuse "rendezvous2" (hidden service descriptor)
4929 publish attempts. Suggested by ticket 18332.
4931 o Minor bugfixes (linux seccomp2 sandbox):
4932 - Allow the setrlimit syscall, and the prlimit and prlimit64
4933 syscalls, which some libc implementations use under the hood.
4934 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
4935 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
4936 enabled and no DNS resolvers configured. This should help TAILS
4937 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
4938 - Fix the sandbox's interoperability with unix domain sockets under
4939 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
4941 o Minor bugfixes (logging):
4942 - When logging information about an unparsable networkstatus vote or
4943 consensus, do not say "vote" when we mean consensus. Fixes bug
4944 18368; bugfix on 0.2.0.8-alpha.
4945 - Scrub service name in "unrecognized service ID" log messages.
4946 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
4947 - Downgrade logs and backtraces about IP versions to info-level.
4948 Only log backtraces once each time tor runs. Assists in diagnosing
4949 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
4950 Christian, patch by teor.
4952 o Minor bugfixes (memory safety):
4953 - Avoid freeing an uninitialized pointer when opening a socket fails
4954 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
4955 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
4957 - Correctly duplicate addresses in get_interface_address6_list().
4958 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
4959 patch by "cypherpunks".
4960 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
4962 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
4963 18672; bugfix on 0.2.5.1-alpha.
4965 o Minor bugfixes (private directory):
4966 - Prevent a race condition when creating private directories. Fixes
4967 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
4968 Patch from jsturgix. Found with Flawfinder.
4970 o Minor bugfixes (test networks, IPv6):
4971 - Allow internal IPv6 addresses in descriptors in test networks.
4972 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
4975 o Minor bugfixes (testing):
4976 - We no longer disable assertions in the unit tests when coverage is
4977 enabled. Instead, we require you to say --disable-asserts-in-tests
4978 to the configure script if you need assertions disabled in the
4979 unit tests (for example, if you want to perform branch coverage).
4980 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
4982 o Minor bugfixes (time parsing):
4983 - Avoid overflow in tor_timegm when parsing dates in and after 2038
4984 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
4985 0.0.2pre14. Patch by teor.
4987 o Minor bugfixes (tor-gencert):
4988 - Correctly handle the case where an authority operator enters a
4989 passphrase but sends an EOF before sending a newline. Fixes bug
4990 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
4992 o Code simplification and refactoring:
4993 - Quote all the string interpolations in configure.ac -- even those
4994 which we are pretty sure can't contain spaces. Closes ticket
4995 17744. Patch from zerosion.
4996 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
4997 inplace, so there's no need to have a separate implementation for
4998 the non-inplace code. Closes ticket 18258. Patch from Malek.
4999 - Simplify return types for some crypto functions that can't
5000 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
5003 - Change build messages to refer to "Fedora" instead of "Fedora
5004 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
5005 Patches from "icanhasaccount" and "cypherpunks".
5008 - We no longer maintain an internal freelist in memarea.c.
5009 Allocators should be good enough to make this code unnecessary,
5010 and it's doubtful that it ever had any performance benefit.
5013 - Fix several warnings from clang's address sanitizer produced in
5015 - Treat backtrace test failures as expected on FreeBSD until we
5016 solve bug 17808. Closes ticket 18204.
5019 Changes in version 0.2.8.1-alpha - 2016-02-04
5020 Tor 0.2.8.1-alpha is the first alpha release in its series. It
5021 includes numerous small features and bugfixes against previous Tor
5022 versions, and numerous small infrastructure improvements. The most
5023 notable features are a set of improvements to the directory subsystem.
5025 o Major features (security, Linux):
5026 - When Tor starts as root on Linux and is told to switch user ID, it
5027 can now retain the capability to bind to low ports. By default,
5028 Tor will do this only when it's switching user ID and some low
5029 ports have been configured. You can change this behavior with the
5030 new option KeepBindCapabilities. Closes ticket 8195.
5032 o Major features (directory system):
5033 - When bootstrapping multiple consensus downloads at a time, use the
5034 first one that starts downloading, and close the rest. This
5035 reduces failures when authorities or fallback directories are slow
5036 or down. Together with the code for feature 15775, this feature
5037 should reduces failures due to fallback churn. Implements ticket
5038 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
5039 "mikeperry" and "teor".
5040 - Include a trial list of 21 default fallback directories, generated
5041 in January 2016, based on an opt-in survey of suitable relays.
5042 Doing this should make clients bootstrap more quickly and reliably,
5043 and reduce the load on the directory authorities. Closes ticket
5044 15775. Patch by "teor".
5045 Candidates identified using an OnionOO script by "weasel", "teor",
5046 "gsathya", and "karsten".
5047 - Previously only relays that explicitly opened a directory port
5048 (DirPort) accepted directory requests from clients. Now all
5049 relays, with and without a DirPort, accept and serve tunneled
5050 directory requests that they receive through their ORPort. You can
5051 disable this behavior using the new DirCache option. Closes
5054 o Major key updates:
5055 - Update the V3 identity key for the dannenberg directory authority:
5056 it was changed on 18 November 2015. Closes task 17906. Patch
5059 o Minor features (security, clock):
5060 - Warn when the system clock appears to move back in time (when the
5061 state file was last written in the future). Tor doesn't know that
5062 consensuses have expired if the clock is in the past. Patch by
5063 "teor". Implements ticket 17188.
5065 o Minor features (security, exit policies):
5066 - ExitPolicyRejectPrivate now rejects more private addresses by
5067 default. Specifically, it now rejects the relay's outbound bind
5068 addresses (if configured), and the relay's configured port
5069 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
5070 0.2.0.11-alpha. Patch by "teor".
5072 o Minor features (security, memory erasure):
5073 - Set the unused entries in a smartlist to NULL. This helped catch
5074 a (harmless) bug, and shouldn't affect performance too much.
5075 Implements ticket 17026.
5076 - Use SecureMemoryWipe() function to securely clean memory on
5077 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
5078 Implements feature 17986.
5079 - Use explicit_bzero or memset_s when present. Previously, we'd use
5080 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
5081 from <logan@hackers.mu> and <selven@hackers.mu>.
5082 - Make memwipe() do nothing when passed a NULL pointer or buffer of
5083 zero size. Check size argument to memwipe() for underflow. Fixes
5084 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
5087 o Minor features (security, RNG):
5088 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
5089 positively are not allowed to fail. Previously we depended on
5090 internal details of OpenSSL's behavior. Closes ticket 17686.
5091 - Never use the system entropy output directly for anything besides
5092 seeding the PRNG. When we want to generate important keys, instead
5093 of using system entropy directly, we now hash it with the PRNG
5094 stream. This may help resist certain attacks based on broken OS
5095 entropy implementations. Closes part of ticket 17694.
5096 - Use modern system calls (like getentropy() or getrandom()) to
5097 generate strong entropy on platforms that have them. Closes
5100 o Minor features (accounting):
5101 - Added two modes to the AccountingRule option: One for limiting
5102 only the number of bytes sent ("AccountingRule out"), and one for
5103 limiting only the number of bytes received ("AccountingRule in").
5104 Closes ticket 15989; patch from "unixninja92".
5106 o Minor features (build):
5107 - Since our build process now uses "make distcheck", we no longer
5108 force "make dist" to depend on "make check". Closes ticket 17893;
5109 patch from "cypherpunks."
5110 - Tor now builds successfully with the recent OpenSSL 1.1
5111 development branch, and with the latest LibreSSL. Closes tickets
5112 17549, 17921, and 17984.
5114 o Minor features (controller):
5115 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
5116 tickets 16774 and 17817. Patch by George Tankersley.
5117 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
5118 service descriptor from a service's local hidden service
5119 descriptor cache. Closes ticket 14846.
5120 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
5121 controllers can examine the the reject rules added by
5122 ExitPolicyRejectPrivate. This makes it easier for stem to display
5125 o Minor features (crypto):
5126 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
5128 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
5129 - When allocating a digest state object, allocate no more space than
5130 we actually need. Previously, we would allocate as much space as
5131 the state for the largest algorithm would need. This change saves
5132 up to 672 bytes per circuit. Closes ticket 17796.
5133 - Improve performance when hashing non-multiple of 8 sized buffers,
5134 based on Andrew Moon's public domain SipHash-2-4 implementation.
5135 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
5137 o Minor features (directory downloads):
5138 - Wait for busy authorities and fallback directories to become non-
5139 busy when bootstrapping. (A similar change was made in 6c443e987d
5140 for directory caches chosen from the consensus.) Closes ticket
5141 17864; patch by "teor".
5142 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
5143 directory mirrors. The default is 1; set it to 0 to disable
5144 fallbacks. Implements ticket 17576. Patch by "teor".
5146 o Minor features (geoip):
5147 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
5150 o Minor features (IPv6):
5151 - Add an argument 'ipv6=address:orport' to the DirAuthority and
5152 FallbackDir torrc options, to specify an IPv6 address for an
5153 authority or fallback directory. Add hard-coded ipv6 addresses for
5154 directory authorities that have them. Closes ticket 17327; patch
5155 from Nick Mathewson and "teor".
5156 - Add address policy assume_action support for IPv6 addresses.
5157 - Limit IPv6 mask bits to 128.
5158 - Warn when comparing against an AF_UNSPEC address in a policy, it's
5159 almost always a bug. Closes ticket 17863; patch by "teor".
5160 - Allow users to configure directory authorities and fallback
5161 directory servers with IPv6 addresses and ORPorts. Resolves
5163 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
5164 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
5165 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
5166 17638; bugfix on 0.0.2pre8. Patch by "teor".
5168 o Minor features (logging):
5169 - When logging to syslog, allow a tag to be added to the syslog
5170 identity (the string prepended to every log message). The tag can
5171 be configured with SyslogIdentityTag and defaults to none. Setting
5172 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
5175 o Minor features (portability):
5176 - Use timingsafe_memcmp() where available. Closes ticket 17944;
5177 patch from <logan@hackers.mu>.
5179 o Minor features (relay, address discovery):
5180 - Add a family argument to get_interface_addresses_raw() and
5181 subfunctions to make network interface address interogation more
5182 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
5183 types of interfaces from the operating system. Resolves
5185 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
5186 fails to enumerate interface addresses using the platform-specific
5187 API, have it rely on the UDP socket fallback technique to try and
5188 find out what IP addresses (both IPv4 and IPv6) our machine has.
5189 Resolves ticket 17951.
5191 o Minor features (replay cache):
5192 - The replay cache now uses SHA256 instead of SHA1. Implements
5193 feature 8961. Patch by "teor", issue reported by "rransom".
5195 o Minor features (unix file permissions):
5196 - Defer creation of Unix sockets until after setuid. This avoids
5197 needing CAP_CHOWN and CAP_FOWNER when using systemd's
5198 CapabilityBoundingSet, or chown and fowner when using SELinux.
5199 Implements part of ticket 17562. Patch from Jamie Nguyen.
5200 - If any directory created by Tor is marked as group readable, the
5201 filesystem group is allowed to be either the default GID or the
5202 root user. Allowing root to read the DataDirectory prevents the
5203 need for CAP_READ_SEARCH when using systemd's
5204 CapabilityBoundingSet, or dac_read_search when using SELinux.
5205 Implements part of ticket 17562. Patch from Jamie Nguyen.
5206 - Introduce a new DataDirectoryGroupReadable option. If it is set to
5207 1, the DataDirectory will be made readable by the default GID.
5208 Implements part of ticket 17562. Patch from Jamie Nguyen.
5210 o Minor bugfixes (accounting):
5211 - The max bandwidth when using 'AccountRule sum' is now correctly
5212 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
5215 o Minor bugfixes (code correctness):
5216 - When closing an entry connection, generate a warning if we should
5217 have sent an end cell for it but we haven't. Fixes bug 17876;
5218 bugfix on 0.2.3.2-alpha.
5219 - Assert that allocated memory held by the reputation code is freed
5220 according to its internal counters. Fixes bug 17753; bugfix
5222 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
5225 o Minor bugfixes (compilation):
5226 - Mark all object files that include micro-revision.i as depending
5227 on it, so as to make parallel builds more reliable. Fixes bug
5228 17826; bugfix on 0.2.5.1-alpha.
5229 - Don't try to use the pthread_condattr_setclock() function unless
5230 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
5231 17819; bugfix on 0.2.6.3-alpha.
5232 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
5234 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
5235 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
5236 - Fix search for libevent libraries on OpenBSD (and other systems
5237 that install libevent 1 and libevent 2 in parallel). Fixes bug
5238 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
5239 - Isolate environment variables meant for tests from the rest of the
5240 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
5241 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
5243 - Remove config.log only from make distclean, not from make clean.
5244 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
5246 o Minor bugfixes (crypto):
5247 - Check the return value of HMAC() and assert on failure. Fixes bug
5248 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
5250 o Minor bugfixes (fallback directories):
5251 - Mark fallbacks as "too busy" when they return a 503 response,
5252 rather than just marking authorities. Fixes bug 17572; bugfix on
5253 0.2.4.7-alpha. Patch by "teor".
5255 o Minor bugfixes (IPv6):
5256 - Update the limits in max_dl_per_request for IPv6 address length.
5257 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
5259 o Minor bugfixes (linux seccomp2 sandbox):
5260 - Fix a crash when using offline master ed25519 keys with the Linux
5261 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
5263 o Minor bugfixes (logging):
5264 - In log messages that include a function name, use __FUNCTION__
5265 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
5266 with clang __PRETTY_FUNCTION__ has extra information we don't
5267 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
5269 - Remove needless quotes from a log message about unparseable
5270 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
5272 o Minor bugfixes (portability):
5273 - Remove an #endif from configure.ac so that we correctly detect the
5274 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
5277 o Minor bugfixes (relays):
5278 - Check that both the ORPort and DirPort (if present) are reachable
5279 before publishing a relay descriptor. Otherwise, relays publish a
5280 descriptor with DirPort 0 when the DirPort reachability test takes
5281 longer than the ORPort reachability test. Fixes bug 18050; bugfix
5282 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
5284 o Minor bugfixes (relays, hidden services):
5285 - Refuse connection requests to private OR addresses unless
5286 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
5287 then refuse to send any cells to a private address. Fixes bugs
5288 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
5290 o Minor bugfixes (safe logging):
5291 - When logging a malformed hostname received through socks4, scrub
5292 it if SafeLogging says we should. Fixes bug 17419; bugfix
5295 o Minor bugfixes (statistics code):
5296 - Consistently check for overflow in round_*_to_next_multiple_of
5297 functions, and add unit tests with additional and maximal values.
5298 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
5299 - Handle edge cases in the laplace functions: avoid division by
5300 zero, avoid taking the log of zero, and silence clang type
5301 conversion warnings using round and trunc. Add unit tests for edge
5302 cases with maximal values. Fixes part of bug 13192; bugfix
5305 o Minor bugfixes (testing):
5306 - The test for log_heartbeat was incorrectly failing in timezones
5307 with non-integer offsets. Instead of comparing the end of the time
5308 string against a constant, compare it to the output of
5309 format_local_iso_time when given the correct input. Fixes bug
5310 18039; bugfix on 0.2.5.4-alpha.
5311 - Make unit tests pass on IPv6-only systems, and systems without
5312 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
5313 bugfix on 0.2.7.3-rc. Patch by "teor".
5314 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
5316 - Check the full results of SHA256 and SHA512 digests in the unit
5317 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
5319 o Code simplification and refactoring:
5320 - Move logging of redundant policy entries in
5321 policies_parse_exit_policy_internal into its own function. Closes
5322 ticket 17608; patch from "juce".
5323 - Extract the more complicated parts of circuit_mark_for_close()
5324 into a new function that we run periodically before circuits are
5325 freed. This change removes more than half of the functions
5326 currently in the "blob". Closes ticket 17218.
5327 - Clean up a little duplicated code in
5328 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
5330 - Decouple the list of streams waiting to be attached to circuits
5331 from the overall connection list. This change makes it possible to
5332 attach streams quickly while simplifying Tor's callgraph and
5333 avoiding O(N) scans of the entire connection list. Closes
5335 - When a direct directory request fails immediately on launch,
5336 instead of relaunching that request from inside the code that
5337 launches it, instead mark the connection for teardown. This change
5338 simplifies Tor's callback and prevents the directory-request
5339 launching code from invoking itself recursively. Closes
5341 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
5342 use them. Closes ticket 17926.
5345 - Add a description of the correct use of the '--keygen' command-
5346 line option. Closes ticket 17583; based on text by 's7r'.
5347 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
5348 - Explain actual minima for BandwidthRate. Closes ticket 16382.
5349 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
5350 - Mention torspec URL in the manpage and point the reader to it
5351 whenever we mention a document that belongs in torspce. Fixes
5355 - Remove client-side support for connecting to Tor relays running
5356 versions of Tor before 0.2.3.6-alpha. These relays didn't support
5357 the v3 TLS handshake protocol, and are no longer allowed on the
5358 Tor network. Implements the client side of ticket 11150. Based on
5359 patches by Tom van der Woerdt.
5362 - Add unit tests to check for common RNG failure modes, such as
5363 returning all zeroes, identical values, or incrementing values
5364 (OpenSSL's rand_predictable feature). Patch by "teor".
5365 - Log more information when the backtrace tests fail. Closes ticket
5366 17892. Patch from "cypherpunks."
5367 - Always test both ed25519 backends, so that we can be sure that our
5368 batch-open replacement code works. Part of ticket 16794.
5369 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
5370 portion of ticket 16831.
5371 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
5372 util_format.c, directory.c, and options_validate.c. Closes tickets
5373 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
5375 - Unit tests for directory_handle_command_get. Closes ticket 17004.
5376 Patch from Reinaldo de Souza Jr.
5379 Changes in version 0.2.7.6 - 2015-12-10
5380 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
5381 well as a minor bug in hidden service reliability.
5383 o Major bugfixes (guard selection):
5384 - Actually look at the Guard flag when selecting a new directory
5385 guard. When we implemented the directory guard design, we
5386 accidentally started treating all relays as if they have the Guard
5387 flag during guard selection, leading to weaker anonymity and worse
5388 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
5391 o Minor features (geoip):
5392 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
5395 o Minor bugfixes (compilation):
5396 - When checking for net/pfvar.h, include netinet/in.h if possible.
5397 This fixes transparent proxy detection on OpenBSD. Fixes bug
5398 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
5399 - Fix a compilation warning with Clang 3.6: Do not check the
5400 presence of an address which can never be NULL. Fixes bug 17781.
5402 o Minor bugfixes (correctness):
5403 - When displaying an IPv6 exit policy, include the mask bits
5404 correctly even when the number is greater than 31. Fixes bug
5405 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
5406 - The wrong list was used when looking up expired intro points in a
5407 rend service object, causing what we think could be reachability
5408 issues for hidden services, and triggering a BUG log. Fixes bug
5409 16702; bugfix on 0.2.7.2-alpha.
5410 - Fix undefined behavior in the tor_cert_checksig function. Fixes
5411 bug 17722; bugfix on 0.2.7.2-alpha.
5414 Changes in version 0.2.7.5 - 2015-11-20
5415 The Tor 0.2.7 release series is dedicated to the memory of Tor user
5416 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
5417 tirelessly to advocate human rights regardless of national borders,
5418 and oppose the encroachments of mass surveillance. He opposed national
5419 exceptionalism, he brought clarity to legal and policy debates, he
5420 understood and predicted the impact of mass surveillance on the world,
5421 and he laid the groundwork for resisting it. While serving on the Tor
5422 Project's board of directors, he brought us his uncompromising focus
5423 on technical excellence in the service of humankind. Caspar was an
5424 inimitable force for good and a wonderful friend. He was kind,
5425 humorous, generous, gallant, and believed we should protect one
5426 another without exception. We honor him here for his ideals, his
5427 efforts, and his accomplishments. Please honor his memory with works
5428 that would make him proud.
5430 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
5432 The 0.2.7 series adds a more secure identity key type for relays,
5433 improves cryptography performance, resolves several longstanding
5434 hidden-service performance issues, improves controller support for
5435 hidden services, and includes small bugfixes and performance
5436 improvements throughout the program. This release series also includes
5437 more tests than before, and significant simplifications to which parts
5438 of Tor invoke which others.
5440 (This release contains no code changes since 0.2.7.4-rc.)
5443 Changes in version 0.2.7.4-rc - 2015-10-21
5444 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
5445 fixes some important memory leaks, and a scary-looking (but mostly
5446 harmless in practice) invalid-read bug. It also has a few small
5447 bugfixes, notably fixes for compilation and portability on different
5448 platforms. If no further significant bounds are found, the next
5449 release will the the official stable release.
5451 o Major bugfixes (security, correctness):
5452 - Fix an error that could cause us to read 4 bytes before the
5453 beginning of an openssl string. This bug could be used to cause
5454 Tor to crash on systems with unusual malloc implementations, or
5455 systems with unusual hardening installed. Fixes bug 17404; bugfix
5458 o Major bugfixes (correctness):
5459 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
5460 bug 17401; bugfix on 0.2.7.3-rc.
5462 o Major bugfixes (memory leaks):
5463 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
5464 17398; bugfix on 0.2.6.1-alpha.
5465 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
5466 17402; bugfix on 0.2.7.3-rc.
5467 - Fix a memory leak when reading an expired signing key from disk.
5468 Fixes bug 17403; bugfix on 0.2.7.2-rc.
5470 o Minor features (geoIP):
5471 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
5474 o Minor bugfixes (compilation):
5475 - Repair compilation with the most recent (unreleased, alpha)
5476 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
5477 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
5478 17251; bugfix on 0.2.7.2-alpha.
5479 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
5480 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
5482 o Minor bugfixes (portability):
5483 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
5484 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
5487 o Minor bugfixes (sandbox):
5488 - Add the "hidserv-stats" filename to our sandbox filter for the
5489 HiddenServiceStatistics option to work properly. Fixes bug 17354;
5490 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
5492 o Minor bugfixes (testing):
5493 - Add unit tests for get_interface_address* failure cases. Fixes bug
5494 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
5495 - Fix breakage when running 'make check' with BSD make. Fixes bug
5496 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
5497 - Make the get_ifaddrs_* unit tests more tolerant of different
5498 network configurations. (Don't assume every test box has an IPv4
5499 address, and don't assume every test box has a non-localhost
5500 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
5501 - Skip backtrace tests when backtrace support is not compiled in.
5502 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
5506 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
5507 - Note that HiddenServicePorts can take a unix domain socket. Closes
5511 Changes in version 0.2.7.3-rc - 2015-09-25
5512 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
5513 contains numerous usability fixes for Ed25519 keys, safeguards against
5514 several misconfiguration problems, significant simplifications to
5515 Tor's callgraph, and numerous bugfixes and small features.
5517 This is the most tested release of Tor to date. The unit tests cover
5518 39.40% of the code, and the integration tests (accessible with "make
5519 test-full-online", requiring stem and chutney and a network
5520 connection) raise the coverage to 64.49%.
5522 o Major features (security, hidden services):
5523 - Hidden services, if using the EntryNodes option, are required to
5524 use more than one EntryNode, in order to avoid a guard discovery
5525 attack. (This would only affect people who had configured hidden
5526 services and manually specified the EntryNodes option with a
5527 single entry-node. The impact was that it would be easy to
5528 remotely identify the guard node used by such a hidden service.
5529 See ticket for more information.) Fixes ticket 14917.
5531 o Major features (Ed25519 keys, keypinning):
5532 - The key-pinning option on directory authorities is now advisory-
5533 only by default. In a future version, or when the AuthDirPinKeys
5534 option is set, pins are enforced again. Disabling key-pinning
5535 seemed like a good idea so that we can survive the fallout of any
5536 usability problems associated with Ed25519 keys. Closes
5539 o Major features (Ed25519 performance):
5540 - Improve the speed of Ed25519 operations and Curve25519 keypair
5541 generation when built targeting 32 bit x86 platforms with SSE2
5542 available. Implements ticket 16535.
5543 - Improve the runtime speed of Ed25519 signature verification by
5544 using Ed25519-donna's batch verification support. Implements
5547 o Major features (performance testing):
5548 - The test-network.sh script now supports performance testing.
5549 Requires corresponding chutney performance testing changes. Patch
5550 by "teor". Closes ticket 14175.
5552 o Major features (relay, Ed25519):
5553 - Significant usability improvements for Ed25519 key management. Log
5554 messages are better, and the code can recover from far more
5555 failure conditions. Thanks to "s7r" for reporting and diagnosing
5557 - Add a new OfflineMasterKey option to tell Tor never to try loading
5558 or generating a secret Ed25519 identity key. You can use this in
5559 combination with tor --keygen to manage offline and/or encrypted
5560 Ed25519 keys. Implements ticket 16944.
5561 - Add a --newpass option to allow changing or removing the
5562 passphrase of an encrypted key with tor --keygen. Implements part
5564 - On receiving a HUP signal, check to see whether the Ed25519
5565 signing key has changed, and reload it if so. Closes ticket 16790.
5567 o Major bugfixes (relay, Ed25519):
5568 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
5569 0.2.7.2-alpha. Reported by "s7r".
5570 - Improve handling of expired signing keys with offline master keys.
5571 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
5573 o Minor features (client-side privacy):
5574 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
5575 lifespan when IsolateSOCKSAuth and streams with SOCKS
5576 authentication are attached to the circuit. This allows
5577 applications like TorBrowser to manage circuit lifetime on their
5578 own. Implements feature 15482.
5579 - When logging malformed hostnames from SOCKS5 requests, respect
5580 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
5582 o Minor features (compilation):
5583 - Give a warning as early as possible when trying to build with an
5584 unsupported OpenSSL version. Closes ticket 16901.
5585 - Fail during configure if we're trying to build against an OpenSSL
5586 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
5587 which started requiring ECC.
5589 o Minor features (geoip):
5590 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
5593 o Minor features (hidden services):
5594 - Relays need to have the Fast flag to get the HSDir flag. As this
5595 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
5596 drop. This change should make some attacks against the hidden
5597 service directory system harder. Fixes ticket 15963.
5598 - Turn on hidden service statistics collection by setting the torrc
5599 option HiddenServiceStatistics to "1" by default. (This keeps
5600 track only of the fraction of traffic used by hidden services, and
5601 the total number of hidden services in existence.) Closes
5603 - Client now uses an introduction point failure cache to know when
5604 to fetch or keep a descriptor in their cache. Previously, failures
5605 were recorded implicitly, but not explicitly remembered. Closes
5608 o Minor features (testing, authorities, documentation):
5609 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
5610 explicitly manage consensus flags in testing networks. Patch by
5611 "robgjansen", modified by "teor". Implements part of ticket 14882.
5613 o Minor bugfixes (security, exit policies):
5614 - ExitPolicyRejectPrivate now also rejects the relay's published
5615 IPv6 address (if any), and any publicly routable IPv4 or IPv6
5616 addresses on any local interfaces. ticket 17027. Patch by "teor".
5617 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
5619 o Minor bug fixes (torrc exit policies):
5620 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
5621 produce IPv6 wildcard addresses. Previously they would produce
5622 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
5623 of bug 16069; bugfix on 0.2.4.7-alpha.
5624 - When parsing torrc ExitPolicies, we now warn for a number of cases
5625 where the user's intent is likely to differ from Tor's actual
5626 behavior. These include: using an IPv4 address with an accept6 or
5627 reject6 line; using "private" on an accept6 or reject6 line; and
5628 including any ExitPolicy lines after accept *:* or reject *:*.
5629 Related to ticket 16069.
5630 - When parsing torrc ExitPolicies, we now issue an info-level
5631 message when expanding an "accept/reject *" line to include both
5632 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
5633 - In each instance above, usage advice is provided to avoid the
5634 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
5635 16069; bugfix on 0.2.4.7-alpha.
5637 o Minor bugfixes (authority):
5638 - Don't assign "HSDir" to a router if it isn't Valid and Running.
5639 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
5640 - Downgrade log messages about Ed25519 key issues if they are in old
5641 cached router descriptors. Fixes part of bug 16286; bugfix
5643 - When we find an Ed25519 key issue in a cached descriptor, stop
5644 saying the descriptor was just "uploaded". Fixes another part of
5645 bug 16286; bugfix on 0.2.7.2-alpha.
5647 o Minor bugfixes (control port):
5648 - Repair a warning and a spurious result when getting the maximum
5649 number of file descriptors from the controller. Fixes bug 16697;
5650 bugfix on 0.2.7.2-alpha.
5652 o Minor bugfixes (correctness):
5653 - When calling channel_free_list(), avoid calling smartlist_remove()
5654 while inside a FOREACH loop. This partially reverts commit
5655 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
5656 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
5658 o Minor bugfixes (documentation):
5659 - Advise users on how to configure separate IPv4 and IPv6 exit
5660 policies in the manpage and sample torrcs. Related to ticket 16069.
5661 - Fix the usage message of tor-resolve(1) so that it no longer lists
5662 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
5663 - Fix an error in the manual page and comments for
5664 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
5665 required "ORPort connectivity". While this is true, it is in no
5666 way unique to the HSDir flag. Of all the flags, only HSDirs need a
5667 DirPort configured in order for the authorities to assign that
5668 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
5671 o Minor bugfixes (Ed25519):
5672 - Fix a memory leak when reading router descriptors with expired
5673 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
5675 o Minor bugfixes (linux seccomp2 sandbox):
5676 - Allow bridge authorities to run correctly under the seccomp2
5677 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
5678 - Allow routers with ed25519 keys to run correctly under the
5679 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
5681 o Minor bugfixes (open file limit):
5682 - Fix set_max_file_descriptors() to set by default the max open file
5683 limit to the current limit when setrlimit() fails. Fixes bug
5684 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
5686 o Minor bugfixes (portability):
5687 - Try harder to normalize the exit status of the Tor process to the
5688 standard-provided range. Fixes bug 16975; bugfix on every version
5690 - Check correctly for Windows socket errors in the workqueue
5691 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
5692 - Fix the behavior of crypto_rand_time_range() when told to consider
5693 times before 1970. (These times were possible when running in a
5694 simulated network environment where time()'s output starts at
5695 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
5696 - Restore correct operation of TLS client-cipher detection on
5697 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
5699 o Minor bugfixes (relay):
5700 - Ensure that worker threads actually exit when a fatal error or
5701 shutdown is indicated. This fix doesn't currently affect the
5702 behavior of Tor, because Tor workers never indicates fatal error
5703 or shutdown except in the unit tests. Fixes bug 16868; bugfix
5705 - Unblock threads before releasing the work queue mutex to ensure
5706 predictable scheduling behavior. Fixes bug 16644; bugfix
5709 o Code simplification and refactoring:
5710 - Change the function that's called when we need to retry all
5711 downloads so that it only reschedules the downloads to happen
5712 immediately, rather than launching them all at once itself. This
5713 further simplifies Tor's callgraph.
5714 - Move some format-parsing functions out of crypto.c and
5715 crypto_curve25519.c into crypto_format.c and/or util_format.c.
5716 - Move the client-only parts of init_keys() into a separate
5717 function. Closes ticket 16763.
5718 - Simplify the microdesc_free() implementation so that it no longer
5719 appears (to code analysis tools) to potentially invoke a huge
5720 suite of other microdesc functions.
5721 - Simply the control graph further by deferring the inner body of
5722 directory_all_unreachable() into a callback. Closes ticket 16762.
5723 - Treat the loss of an owning controller as equivalent to a SIGTERM
5724 signal. This removes a tiny amount of duplicated code, and
5725 simplifies our callgraph. Closes ticket 16788.
5726 - When generating an event to send to the controller, we no longer
5727 put the event over the network immediately. Instead, we queue
5728 these events, and use a Libevent callback to deliver them. This
5729 change simplifies Tor's callgraph by reducing the number of
5730 functions from which all other Tor functions are reachable. Closes
5732 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
5733 that try to scan or compile every file on Unix won't decide that
5735 - Remove the unused "nulterminate" argument from buf_pullup().
5738 - Recommend a 40 GB example AccountingMax in torrc.sample rather
5739 than a 4 GB max. Closes ticket 16742.
5740 - Include the TUNING document in our source tarball. It is referred
5741 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
5745 - The internal pure-C tor-fw-helper tool is now removed from the Tor
5746 distribution, in favor of the pure-Go clone available from
5747 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
5748 used by the C tor-fw-helper are not, in our opinion, very
5749 confidence- inspiring in their secure-programming techniques.
5750 Closes ticket 13338.
5751 - Remove the code that would try to aggressively flush controller
5752 connections while writing to them. This code was introduced in
5753 0.1.2.7-alpha, in order to keep output buffers from exceeding
5754 their limits. But there is no longer a maximum output buffer size,
5755 and flushing data in this way caused some undesirable recursions
5756 in our call graph. Closes ticket 16480.
5759 - Make "bridges+hs" the default test network. This tests almost all
5760 tor functionality during make test-network, while allowing tests
5761 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
5762 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
5763 (chutney). Patches by "teor".
5764 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
5765 by-side in the same parent directory. Closes ticket 16903. Patch
5767 - Use environment variables rather than autoconf substitutions to
5768 send variables from the build system to the test scripts. This
5769 change should be easier to maintain, and cause 'make distcheck' to
5770 work better than before. Fixes bug 17148.
5771 - Add a new set of callgraph analysis scripts that use clang to
5772 produce a list of which Tor functions are reachable from which
5773 other Tor functions. We're planning to use these to help simplify
5774 our code structure by identifying illogical dependencies.
5775 - Add new 'test-full' and 'test-full-online' targets to run all
5776 tests, including integration tests with stem and chutney.
5777 - Make the test-workqueue test work on Windows by initializing the
5778 network before we begin.
5779 - New make target (make test-network-all) to run multiple applicable
5780 chutney test cases. Patch from Teor; closes 16953.
5781 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
5782 functions in dns.c. Implements a portion of ticket 16831.
5783 - When building Tor with testing coverage enabled, run Chutney tests
5784 (if any) using the 'tor-cov' coverage binary.
5785 - When running test-network or test-stem, check for the absence of
5786 stem/chutney before doing any build operations.
5789 Changes in version 0.2.7.2-alpha - 2015-07-27
5790 This, the second alpha in the Tor 0.2.7 series, has a number of new
5791 features, including a way to manually pick the number of introduction
5792 points for hidden services, and the much stronger Ed25519 signing key
5793 algorithm for regular Tor relays (including support for encrypted
5794 offline identity keys in the new algorithm).
5796 Support for Ed25519 on relays is currently limited to signing router
5797 descriptors; later alphas in this series will extend Ed25519 key
5798 support to more parts of the Tor protocol.
5800 o Major features (Ed25519 identity keys, Proposal 220):
5801 - All relays now maintain a stronger identity key, using the Ed25519
5802 elliptic curve signature format. This master key is designed so
5803 that it can be kept offline. Relays also generate an online
5804 signing key, and a set of other Ed25519 keys and certificates.
5805 These are all automatically regenerated and rotated as needed.
5806 Implements part of ticket 12498.
5807 - Directory authorities now vote on Ed25519 identity keys along with
5808 RSA1024 keys. Implements part of ticket 12498.
5809 - Directory authorities track which Ed25519 identity keys have been
5810 used with which RSA1024 identity keys, and do not allow them to
5811 vary freely. Implements part of ticket 12498.
5812 - Microdescriptors now include Ed25519 identity keys. Implements
5813 part of ticket 12498.
5814 - Add support for offline encrypted Ed25519 master keys. To use this
5815 feature on your tor relay, run "tor --keygen" to make a new master
5816 key (or to make a new signing key if you already have a master
5817 key). Closes ticket 13642.
5819 o Major features (Hidden services):
5820 - Add the torrc option HiddenServiceNumIntroductionPoints, to
5821 specify a fixed number of introduction points. Its maximum value
5822 is 10 and default is 3. Using this option can increase a hidden
5823 service's reliability under load, at the cost of making it more
5824 visible that the hidden service is facing extra load. Closes
5826 - Remove the adaptive algorithm for choosing the number of
5827 introduction points, which used to change the number of
5828 introduction points (poorly) depending on the number of
5829 connections the HS sees. Closes ticket 4862.
5831 o Major features (onion key cross-certification):
5832 - Relay descriptors now include signatures of their own identity
5833 keys, made using the TAP and ntor onion keys. These signatures
5834 allow relays to prove ownership of their own onion keys. Because
5835 of this change, microdescriptors will no longer need to include
5836 RSA identity keys. Implements proposal 228; closes ticket 12499.
5838 o Major features (performance):
5839 - Improve the runtime speed of Ed25519 operations by using the
5840 public-domain Ed25519-donna by Andrew M. ("floodyberry").
5841 Implements ticket 16467.
5842 - Improve the runtime speed of the ntor handshake by using an
5843 optimized curve25519 basepoint scalarmult implementation from the
5844 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
5845 ideas by Adam Langley. Implements ticket 9663.
5847 o Major bugfixes (client-side privacy, also in 0.2.6.9):
5848 - Properly separate out each SOCKSPort when applying stream
5849 isolation. The error occurred because each port's session group
5850 was being overwritten by a default value when the listener
5851 connection was initialized. Fixes bug 16247; bugfix on
5852 0.2.6.3-alpha. Patch by "jojelino".
5854 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
5855 - Stop refusing to store updated hidden service descriptors on a
5856 client. This reverts commit 9407040c59218 (which indeed fixed bug
5857 14219, but introduced a major hidden service reachability
5858 regression detailed in bug 16381). This is a temporary fix since
5859 we can live with the minor issue in bug 14219 (it just results in
5860 some load on the network) but the regression of 16381 is too much
5861 of a setback. First-round fix for bug 16381; bugfix
5864 o Major bugfixes (hidden services):
5865 - When cannibalizing a circuit for an introduction point, always
5866 extend to the chosen exit node (creating a 4 hop circuit).
5867 Previously Tor would use the current circuit exit node, which
5868 changed the original choice of introduction point, and could cause
5869 the hidden service to skip excluded introduction points or
5870 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
5873 o Major bugfixes (open file limit):
5874 - The open file limit wasn't checked before calling
5875 tor_accept_socket_nonblocking(), which would make Tor exceed the
5876 limit. Now, before opening a new socket, Tor validates the open
5877 file limit just before, and if the max has been reached, return an
5878 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
5880 o Major bugfixes (stability, also in 0.2.6.10):
5881 - Stop crashing with an assertion failure when parsing certain kinds
5882 of malformed or truncated microdescriptors. Fixes bug 16400;
5883 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
5884 by "cypherpunks_backup".
5885 - Stop random client-side assertion failures that could occur when
5886 connecting to a busy hidden service, or connecting to a hidden
5887 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
5890 o Minor features (directory authorities, security, also in 0.2.6.9):
5891 - The HSDir flag given by authorities now requires the Stable flag.
5892 For the current network, this results in going from 2887 to 2806
5893 HSDirs. Also, it makes it harder for an attacker to launch a sybil
5894 attack by raising the effort for a relay to become Stable to
5895 require at the very least 7 days, while maintaining the 96 hours
5896 uptime requirement for HSDir. Implements ticket 8243.
5898 o Minor features (client):
5899 - Relax the validation of hostnames in SOCKS5 requests, allowing the
5900 character '_' to appear, in order to cope with domains observed in
5901 the wild that are serving non-RFC compliant records. Resolves
5903 - Relax the validation done to hostnames in SOCKS5 requests, and
5904 allow a single trailing '.' to cope with clients that pass FQDNs
5905 using that syntax to explicitly indicate that the domain name is
5906 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
5907 - Add GroupWritable and WorldWritable options to unix-socket based
5908 SocksPort and ControlPort options. These options apply to a single
5909 socket, and override {Control,Socks}SocketsGroupWritable. Closes
5912 o Minor features (control protocol):
5913 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
5914 the control protocol. Resolves ticket 15358.
5916 o Minor features (directory authorities):
5917 - Directory authorities no longer vote against the "Fast", "Stable",
5918 and "HSDir" flags just because they were going to vote against
5919 "Running": if the consensus turns out to be that the router was
5920 running, then the authority's vote should count. Patch from Peter
5921 Retzlaff; closes issue 8712.
5923 o Minor features (geoip, also in 0.2.6.10):
5924 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
5925 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
5927 o Minor features (hidden services):
5928 - Add the new options "HiddenServiceMaxStreams" and
5929 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
5930 limit the maximum number of simultaneous streams per circuit, and
5931 optionally tear down the circuit when the limit is exceeded. Part
5934 o Minor features (portability):
5935 - Use C99 variadic macros when the compiler is not GCC. This avoids
5936 failing compilations on MSVC, and fixes a log-file-based race
5937 condition in our old workarounds. Original patch from Gisle Vanem.
5939 o Minor bugfixes (compilation, also in 0.2.6.9):
5940 - Build with --enable-systemd correctly when libsystemd is
5941 installed, but systemd is not. Fixes bug 16164; bugfix on
5942 0.2.6.3-alpha. Patch from Peter Palfrader.
5944 o Minor bugfixes (controller):
5945 - Add the descriptor ID in each HS_DESC control event. It was
5946 missing, but specified in control-spec.txt. Fixes bug 15881;
5947 bugfix on 0.2.5.2-alpha.
5949 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
5950 - Check for failures from crypto_early_init, and refuse to continue.
5951 A previous typo meant that we could keep going with an
5952 uninitialized crypto library, and would have OpenSSL initialize
5953 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
5954 when implementing ticket 4900. Patch by "teor".
5956 o Minor bugfixes (hidden services):
5957 - Fix a crash when reloading configuration while at least one
5958 configured and one ephemeral hidden service exists. Fixes bug
5959 16060; bugfix on 0.2.7.1-alpha.
5960 - Avoid crashing with a double-free bug when we create an ephemeral
5961 hidden service but adding it fails for some reason. Fixes bug
5962 16228; bugfix on 0.2.7.1-alpha.
5964 o Minor bugfixes (Linux seccomp2 sandbox):
5965 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
5966 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
5968 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
5969 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
5970 these when eventfd2() support is missing. Fixes bug 16363; bugfix
5971 on 0.2.6.3-alpha. Patch from "teor".
5973 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
5974 - Fix sandboxing to work when running as a relay, by allowing the
5975 renaming of secret_id_key, and allowing the eventfd2 and futex
5976 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
5978 - Allow systemd connections to work with the Linux seccomp2 sandbox
5979 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
5982 o Minor bugfixes (relay):
5983 - Fix a rarely-encountered memory leak when failing to initialize
5984 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
5987 o Minor bugfixes (systemd):
5988 - Fix an accidental formatting error that broke the systemd
5989 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
5990 - Tor's systemd unit file no longer contains extraneous spaces.
5991 These spaces would sometimes confuse tools like deb-systemd-
5992 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
5994 o Minor bugfixes (tests):
5995 - Use the configured Python executable when running test-stem-full.
5996 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
5998 o Minor bugfixes (tests, also in 0.2.6.9):
5999 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6000 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6002 o Minor bugfixes (threads, comments):
6003 - Always initialize return value in compute_desc_id in rendcommon.c
6004 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6005 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
6006 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6007 - Remove undefined directive-in-macro in test_util_writepid clang
6008 3.7 complains that using a preprocessor directive inside a macro
6009 invocation in test_util_writepid in test_util.c is undefined.
6010 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
6012 o Code simplification and refactoring:
6013 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
6014 to ensure they remain consistent and visible everywhere.
6015 - Remove some vestigial workarounds for the MSVC6 compiler. We
6016 haven't supported that in ages.
6017 - The link authentication code has been refactored for better
6018 testability and reliability. It now uses code generated with the
6019 "trunnel" binary encoding generator, to reduce the risk of bugs
6020 due to programmer error. Done as part of ticket 12498.
6023 - Include a specific and (hopefully) accurate documentation of the
6024 torrc file's meta-format in doc/torrc_format.txt. This is mainly
6025 of interest to people writing programs to parse or generate torrc
6026 files. This document is not a commitment to long-term
6027 compatibility; some aspects of the current format are a bit
6028 ridiculous. Closes ticket 2325.
6031 - Tor no longer supports copies of OpenSSL that are missing support
6032 for Elliptic Curve Cryptography. (We began using ECC when
6033 available in 0.2.4.8-alpha, for more safe and efficient key
6034 negotiation.) In particular, support for at least one of P256 or
6035 P224 is now required, with manual configuration needed if only
6036 P224 is available. Resolves ticket 16140.
6037 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
6038 on an operating system that has not upgraded to OpenSSL 1.0 or
6039 later, and you compile Tor from source, you will need to install a
6040 more recent OpenSSL to link Tor against.) These versions of
6041 OpenSSL are still supported by the OpenSSL, but the numerous
6042 cryptographic improvements in later OpenSSL releases makes them a
6043 clear choice. Resolves ticket 16034.
6044 - Remove the HidServDirectoryV2 option. Now all relays offer to
6045 store hidden service descriptors. Related to 16543.
6046 - Remove the VoteOnHidServDirectoriesV2 option, since all
6047 authorities have long set it to 1. Closes ticket 16543.
6050 - Document use of coverity, clang static analyzer, and clang dynamic
6051 undefined behavior and address sanitizers in doc/HACKING. Include
6052 detailed usage instructions in the blacklist. Patch by "teor".
6053 Closes ticket 15817.
6054 - The link authentication protocol code now has extensive tests.
6055 - The relay descriptor signature testing code now has
6057 - The test_workqueue program now runs faster, and is enabled by
6058 default as a part of "make check".
6059 - Now that OpenSSL has its own scrypt implementation, add an unit
6060 test that checks for interoperability between libscrypt_scrypt()
6061 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
6062 and rely on EVP_PBE_scrypt() whenever possible. Resolves
6066 Changes in version 0.2.6.10 - 2015-07-12
6067 Tor version 0.2.6.10 fixes some significant stability and hidden
6068 service client bugs, bulletproofs the cryptography init process, and
6069 fixes a bug when using the sandbox code with some older versions of
6070 Linux. Everyone running an older version, especially an older version
6071 of 0.2.6, should upgrade.
6073 o Major bugfixes (hidden service clients, stability):
6074 - Stop refusing to store updated hidden service descriptors on a
6075 client. This reverts commit 9407040c59218 (which indeed fixed bug
6076 14219, but introduced a major hidden service reachability
6077 regression detailed in bug 16381). This is a temporary fix since
6078 we can live with the minor issue in bug 14219 (it just results in
6079 some load on the network) but the regression of 16381 is too much
6080 of a setback. First-round fix for bug 16381; bugfix
6083 o Major bugfixes (stability):
6084 - Stop crashing with an assertion failure when parsing certain kinds
6085 of malformed or truncated microdescriptors. Fixes bug 16400;
6086 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
6087 by "cypherpunks_backup".
6088 - Stop random client-side assertion failures that could occur when
6089 connecting to a busy hidden service, or connecting to a hidden
6090 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
6093 o Minor features (geoip):
6094 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
6095 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
6097 o Minor bugfixes (crypto error-handling):
6098 - Check for failures from crypto_early_init, and refuse to continue.
6099 A previous typo meant that we could keep going with an
6100 uninitialized crypto library, and would have OpenSSL initialize
6101 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
6102 when implementing ticket 4900. Patch by "teor".
6104 o Minor bugfixes (Linux seccomp2 sandbox):
6105 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
6106 these when eventfd2() support is missing. Fixes bug 16363; bugfix
6107 on 0.2.6.3-alpha. Patch from "teor".
6110 Changes in version 0.2.6.9 - 2015-06-11
6111 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
6112 requirements for receiving an HSDir flag, and addresses some other small
6113 bugs in the systemd and sandbox code. Clients using circuit isolation
6114 should upgrade; all directory authorities should upgrade.
6116 o Major bugfixes (client-side privacy):
6117 - Properly separate out each SOCKSPort when applying stream
6118 isolation. The error occurred because each port's session group was
6119 being overwritten by a default value when the listener connection
6120 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
6123 o Minor feature (directory authorities, security):
6124 - The HSDir flag given by authorities now requires the Stable flag.
6125 For the current network, this results in going from 2887 to 2806
6126 HSDirs. Also, it makes it harder for an attacker to launch a sybil
6127 attack by raising the effort for a relay to become Stable which
6128 takes at the very least 7 days to do so and by keeping the 96
6129 hours uptime requirement for HSDir. Implements ticket 8243.
6131 o Minor bugfixes (compilation):
6132 - Build with --enable-systemd correctly when libsystemd is
6133 installed, but systemd is not. Fixes bug 16164; bugfix on
6134 0.2.6.3-alpha. Patch from Peter Palfrader.
6136 o Minor bugfixes (Linux seccomp2 sandbox):
6137 - Fix sandboxing to work when running as a relaymby renaming of
6138 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
6139 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
6140 - Allow systemd connections to work with the Linux seccomp2 sandbox
6141 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
6144 o Minor bugfixes (tests):
6145 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
6146 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
6149 Changes in version 0.2.6.8 - 2015-05-21
6150 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
6151 fixes an authority-side bug in assigning the HSDir flag. All directory
6152 authorities should upgrade.
6154 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
6155 - Revert commit that made directory authorities assign the HSDir
6156 flag to relays without a DirPort; this was bad because such relays
6157 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6160 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
6161 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6162 a client authorized hidden service. Fixes bug 15823; bugfix
6165 o Minor features (geoip):
6166 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6167 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6171 Changes in version 0.2.7.1-alpha - 2015-05-12
6172 Tor 0.2.7.1-alpha is the first alpha release in its series. It
6173 includes numerous small features and bugfixes against previous Tor
6174 versions, and numerous small infrastructure improvements. The most
6175 notable features are several new ways for controllers to interact with
6176 the hidden services subsystem.
6178 o New system requirements:
6179 - Tor no longer includes workarounds to support Libevent versions
6180 before 1.3e. Libevent 2.0 or later is recommended. Closes
6183 o Major features (controller):
6184 - Add the ADD_ONION and DEL_ONION commands that allow the creation
6185 and management of hidden services via the controller. Closes
6187 - New "GETINFO onions/current" and "GETINFO onions/detached"
6188 commands to get information about hidden services created via the
6189 controller. Part of ticket 6411.
6190 - New HSFETCH command to launch a request for a hidden service
6191 descriptor. Closes ticket 14847.
6192 - New HSPOST command to upload a hidden service descriptor. Closes
6193 ticket 3523. Patch by "DonnchaC".
6195 o Major bugfixes (hidden services):
6196 - Revert commit that made directory authorities assign the HSDir
6197 flag to relays without a DirPort; this was bad because such relays
6198 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
6201 o Minor features (clock-jump tolerance):
6202 - Recover better when our clock jumps back many hours, like might
6203 happen for Tails or Whonix users who start with a very wrong
6204 hardware clock, use Tor to discover a more accurate time, and then
6205 fix their clock. Resolves part of ticket 8766.
6207 o Minor features (command-line interface):
6208 - Make --hash-password imply --hush to prevent unnecessary noise.
6209 Closes ticket 15542. Patch from "cypherpunks".
6210 - Print a warning whenever we find a relative file path being used
6211 as torrc option. Resolves issue 14018.
6213 o Minor features (controller):
6214 - Add DirAuthority lines for default directory authorities to the
6215 output of the "GETINFO config/defaults" command if not already
6216 present. Implements ticket 14840.
6217 - Controllers can now use "GETINFO hs/client/desc/id/..." to
6218 retrieve items from the client's hidden service descriptor cache.
6219 Closes ticket 14845.
6220 - Implement a new controller command "GETINFO status/fresh-relay-
6221 descs" to fetch a descriptor/extrainfo pair that was generated on
6222 demand just for the controller's use. Implements ticket 14784.
6224 o Minor features (DoS-resistance):
6225 - Make it harder for attackers to overload hidden services with
6226 introductions, by blocking multiple introduction requests on the
6227 same circuit. Resolves ticket 15515.
6229 o Minor features (geoip):
6230 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
6231 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
6234 o Minor features (HS popularity countermeasure):
6235 - To avoid leaking HS popularity, don't cycle the introduction point
6236 when we've handled a fixed number of INTRODUCE2 cells but instead
6237 cycle it when a random number of introductions is reached, thus
6238 making it more difficult for an attacker to find out the amount of
6239 clients that have used the introduction point for a specific HS.
6240 Closes ticket 15745.
6242 o Minor features (logging):
6243 - Include the Tor version in all LD_BUG log messages, since people
6244 tend to cut and paste those into the bugtracker. Implements
6247 o Minor features (pluggable transports):
6248 - When launching managed pluggable transports on Linux systems,
6249 attempt to have the kernel deliver a SIGTERM on tor exit if the
6250 pluggable transport process is still running. Resolves
6252 - When launching managed pluggable transports, setup a valid open
6253 stdin in the child process that can be used to detect if tor has
6254 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
6255 can be used by implementations to detect this new behavior.
6256 Resolves ticket 15435.
6258 o Minor features (testing):
6259 - Add a test to verify that the compiler does not eliminate our
6260 memwipe() implementation. Closes ticket 15377.
6261 - Add make rule `check-changes` to verify the format of changes
6262 files. Closes ticket 15180.
6263 - Add unit tests for control_event_is_interesting(). Add a compile-
6264 time check that the number of events doesn't exceed the capacity
6265 of control_event_t.event_mask. Closes ticket 15431, checks for
6266 bugs similar to 13085. Patch by "teor".
6267 - Command-line argument tests moved to Stem. Resolves ticket 14806.
6268 - Integrate the ntor, backtrace, and zero-length keys tests into the
6269 automake test suite. Closes ticket 15344.
6270 - Remove assertions during builds to determine Tor's test coverage.
6271 We don't want to trigger these even in assertions, so including
6272 them artificially makes our branch coverage look worse than it is.
6273 This patch provides the new test-stem-full and coverage-html-full
6274 configure options. Implements ticket 15400.
6276 o Minor bugfixes (build):
6277 - Improve out-of-tree builds by making non-standard rules work and
6278 clean up additional files and directories. Fixes bug 15053; bugfix
6281 o Minor bugfixes (command-line interface):
6282 - When "--quiet" is provided along with "--validate-config", do not
6283 write anything to stdout on success. Fixes bug 14994; bugfix
6285 - When complaining about bad arguments to "--dump-config", use
6288 o Minor bugfixes (configuration, unit tests):
6289 - Only add the default fallback directories when the DirAuthorities,
6290 AlternateDirAuthority, and FallbackDir directory config options
6291 are set to their defaults. The default fallback directory list is
6292 currently empty, this fix will only change tor's behavior when it
6293 has default fallback directories. Includes unit tests for
6294 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
6295 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
6297 o Minor bugfixes (correctness):
6298 - For correctness, avoid modifying a constant string in
6299 handle_control_postdescriptor. Fixes bug 15546; bugfix
6301 - Remove side-effects from tor_assert() calls. This was harmless,
6302 because we never disable assertions, but it is bad style and
6303 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
6306 o Minor bugfixes (hidden service):
6307 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
6308 a client authorized hidden service. Fixes bug 15823; bugfix
6310 - Remove an extraneous newline character from the end of hidden
6311 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
6313 o Minor bugfixes (interface):
6314 - Print usage information for --dump-config when it is used without
6315 an argument. Also, fix the error message to use different wording
6316 and add newline at the end. Fixes bug 15541; bugfix
6319 o Minor bugfixes (logs):
6320 - When building Tor under Clang, do not include an extra set of
6321 parentheses in log messages that include function names. Fixes bug
6322 15269; bugfix on every released version of Tor when compiled with
6323 recent enough Clang.
6325 o Minor bugfixes (network):
6326 - When attempting to use fallback technique for network interface
6327 lookup, disregard loopback and multicast addresses since they are
6328 unsuitable for public communications.
6330 o Minor bugfixes (statistics):
6331 - Disregard the ConnDirectionStatistics torrc options when Tor is
6332 not a relay since in that mode of operation no sensible data is
6333 being collected and because Tor might run into measurement hiccups
6334 when running as a client for some time, then becoming a relay.
6335 Fixes bug 15604; bugfix on 0.2.2.35.
6337 o Minor bugfixes (test networks):
6338 - When self-testing reachability, use ExtendAllowPrivateAddresses to
6339 determine if local/private addresses imply reachability. The
6340 previous fix used TestingTorNetwork, which implies
6341 ExtendAllowPrivateAddresses, but this excluded rare configurations
6342 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
6343 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
6344 issue discovered by CJ Ess.
6346 o Minor bugfixes (testing):
6347 - Check for matching value in server response in ntor_ref.py. Fixes
6348 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
6350 - Set the severity correctly when testing
6351 get_interface_addresses_ifaddrs() and
6352 get_interface_addresses_win32(), so that the tests fail gracefully
6353 instead of triggering an assertion. Fixes bug 15759; bugfix on
6354 0.2.6.3-alpha. Reported by Nicolas Derive.
6356 o Code simplification and refactoring:
6357 - Move the hacky fallback code out of get_interface_address6() into
6358 separate function and get it covered with unit-tests. Resolves
6360 - Refactor hidden service client-side cache lookup to intelligently
6361 report its various failure cases, and disentangle failure cases
6362 involving a lack of introduction points. Closes ticket 14391.
6363 - Use our own Base64 encoder instead of OpenSSL's, to allow more
6364 control over the output. Part of ticket 15652.
6367 - Improve the descriptions of statistics-related torrc options in
6368 the manpage to describe rationale and possible uses cases. Fixes
6370 - Improve the layout and formatting of ./configure --help messages.
6371 Closes ticket 15024. Patch from "cypherpunks".
6372 - Standardize on the term "server descriptor" in the manual page.
6373 Previously, we had used "router descriptor", "server descriptor",
6374 and "relay descriptor" interchangeably. Part of ticket 14987.
6377 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
6378 and always use the internal Base64 decoder. The internal decoder
6379 has been part of tor since 0.2.0.10-alpha, and no one should
6380 be using the OpenSSL one. Part of ticket 15652.
6381 - Remove the 'tor_strclear()' function; use memwipe() instead.
6382 Closes ticket 14922.
6385 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
6386 fingerprinting we now recommend pluggable transports; for forward-
6387 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
6388 - Remove the undocumented "--digests" command-line option. It
6389 complicated our build process, caused subtle build issues on
6390 multiple platforms, and is now redundant since we started
6391 including git version identifiers. Closes ticket 14742.
6392 - Tor no longer contains checks for ancient directory cache versions
6393 that didn't know about microdescriptors.
6394 - Tor no longer contains workarounds for stat files generated by
6395 super-old versions of Tor that didn't choose guards sensibly.
6398 Changes in version 0.2.4.27 - 2015-04-06
6399 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
6400 could be used by an attacker to crash hidden services, or crash clients
6401 visiting hidden services. Hidden services should upgrade as soon as
6402 possible; clients should upgrade whenever packages become available.
6404 This release also backports a simple improvement to make hidden
6405 services a bit less vulnerable to denial-of-service attacks.
6407 o Major bugfixes (security, hidden service):
6408 - Fix an issue that would allow a malicious client to trigger an
6409 assertion failure and halt a hidden service. Fixes bug 15600;
6410 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6411 - Fix a bug that could cause a client to crash with an assertion
6412 failure when parsing a malformed hidden service descriptor. Fixes
6413 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6415 o Minor features (DoS-resistance, hidden service):
6416 - Introduction points no longer allow multiple INTRODUCE1 cells to
6417 arrive on the same circuit. This should make it more expensive for
6418 attackers to overwhelm hidden services with introductions.
6419 Resolves ticket 15515.
6422 Changes in version 0.2.5.12 - 2015-04-06
6423 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
6424 could be used by an attacker to crash hidden services, or crash clients
6425 visiting hidden services. Hidden services should upgrade as soon as
6426 possible; clients should upgrade whenever packages become available.
6428 This release also backports a simple improvement to make hidden
6429 services a bit less vulnerable to denial-of-service attacks.
6431 o Major bugfixes (security, hidden service):
6432 - Fix an issue that would allow a malicious client to trigger an
6433 assertion failure and halt a hidden service. Fixes bug 15600;
6434 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6435 - Fix a bug that could cause a client to crash with an assertion
6436 failure when parsing a malformed hidden service descriptor. Fixes
6437 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6439 o Minor features (DoS-resistance, hidden service):
6440 - Introduction points no longer allow multiple INTRODUCE1 cells to
6441 arrive on the same circuit. This should make it more expensive for
6442 attackers to overwhelm hidden services with introductions.
6443 Resolves ticket 15515.
6446 Changes in version 0.2.6.7 - 2015-04-06
6447 Tor 0.2.6.7 fixes two security issues that could be used by an
6448 attacker to crash hidden services, or crash clients visiting hidden
6449 services. Hidden services should upgrade as soon as possible; clients
6450 should upgrade whenever packages become available.
6452 This release also contains two simple improvements to make hidden
6453 services a bit less vulnerable to denial-of-service attacks.
6455 o Major bugfixes (security, hidden service):
6456 - Fix an issue that would allow a malicious client to trigger an
6457 assertion failure and halt a hidden service. Fixes bug 15600;
6458 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
6459 - Fix a bug that could cause a client to crash with an assertion
6460 failure when parsing a malformed hidden service descriptor. Fixes
6461 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
6463 o Minor features (DoS-resistance, hidden service):
6464 - Introduction points no longer allow multiple INTRODUCE1 cells to
6465 arrive on the same circuit. This should make it more expensive for
6466 attackers to overwhelm hidden services with introductions.
6467 Resolves ticket 15515.
6468 - Decrease the amount of reattempts that a hidden service performs
6469 when its rendezvous circuits fail. This reduces the computational
6470 cost for running a hidden service under heavy load. Resolves
6474 Changes in version 0.2.6.6 - 2015-03-24
6475 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
6477 It adds numerous safety, security, correctness, and performance
6478 improvements. Client programs can be configured to use more kinds of
6479 sockets, AutomapHosts works better, the multithreading backend is
6480 improved, cell transmission is refactored, test coverage is much
6481 higher, more denial-of-service attacks are handled, guard selection is
6482 improved to handle long-term guards better, pluggable transports
6483 should work a bit better, and some annoying hidden service performance
6484 bugs should be addressed.
6486 o Minor bugfixes (portability):
6487 - Use the correct datatype in the SipHash-2-4 function to prevent
6488 compilers from assuming any sort of alignment. Fixes bug 15436;
6489 bugfix on 0.2.5.3-alpha.
6491 Changes in version 0.2.6.5-rc - 2015-03-18
6492 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
6493 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
6495 o Major bugfixes (client):
6496 - Avoid crashing when making certain configuration option changes on
6497 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
6500 o Major bugfixes (pluggable transports):
6501 - Initialize the extended OR Port authentication cookie before
6502 launching pluggable transports. This prevents a race condition
6503 that occured when server-side pluggable transports would cache the
6504 authentication cookie before it has been (re)generated. Fixes bug
6505 15240; bugfix on 0.2.5.1-alpha.
6507 o Major bugfixes (portability):
6508 - Do not crash on startup when running on Solaris. Fixes a bug
6509 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
6512 o Minor features (heartbeat):
6513 - On relays, report how many connections we negotiated using each
6514 version of the Tor link protocols. This information will let us
6515 know if removing support for very old versions of the Tor
6516 protocols is harming the network. Closes ticket 15212.
6518 o Code simplification and refactoring:
6519 - Refactor main loop to extract the 'loop' part. This makes it
6520 easier to run Tor under Shadow. Closes ticket 15176.
6523 Changes in version 0.2.5.11 - 2015-03-17
6524 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
6526 It backports several bugfixes from the 0.2.6 branch, including a
6527 couple of medium-level security fixes for relays and exit nodes.
6528 It also updates the list of directory authorities.
6530 o Directory authority changes:
6531 - Remove turtles as a directory authority.
6532 - Add longclaw as a new (v3) directory authority. This implements
6533 ticket 13296. This keeps the directory authority count at 9.
6534 - The directory authority Faravahar has a new IP address. This
6535 closes ticket 14487.
6537 o Major bugfixes (crash, OSX, security):
6538 - Fix a remote denial-of-service opportunity caused by a bug in
6539 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
6542 o Major bugfixes (relay, stability, possible security):
6543 - Fix a bug that could lead to a relay crashing with an assertion
6544 failure if a buffer of exactly the wrong layout was passed to
6545 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6546 0.2.0.10-alpha. Patch from 'cypherpunks'.
6547 - Do not assert if the 'data' pointer on a buffer is advanced to the
6548 very end of the buffer; log a BUG message instead. Only assert if
6549 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6551 o Major bugfixes (exit node stability):
6552 - Fix an assertion failure that could occur under high DNS load.
6553 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
6554 diagnosed and fixed by "cypherpunks".
6556 o Major bugfixes (Linux seccomp2 sandbox):
6557 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
6558 crash during attempts to call wait4. Fixes bug 15088; bugfix on
6559 0.2.5.1-alpha. Patch from "sanic".
6561 o Minor features (controller):
6562 - New "GETINFO bw-event-cache" to get information about recent
6563 bandwidth events. Closes ticket 14128. Useful for controllers to
6564 get recent bandwidth history after the fix for ticket 13988.
6566 o Minor features (geoip):
6567 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6568 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6571 o Minor bugfixes (client, automapping):
6572 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
6573 no value follows the option. Fixes bug 14142; bugfix on
6574 0.2.4.7-alpha. Patch by "teor".
6575 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
6576 14195; bugfix on 0.1.0.1-rc.
6578 o Minor bugfixes (compilation):
6579 - Build without warnings with the stock OpenSSL srtp.h header, which
6580 has a duplicate declaration of SSL_get_selected_srtp_profile().
6581 Fixes bug 14220; this is OpenSSL's bug, not ours.
6583 o Minor bugfixes (directory authority):
6584 - Allow directory authorities to fetch more data from one another if
6585 they find themselves missing lots of votes. Previously, they had
6586 been bumping against the 10 MB queued data limit. Fixes bug 14261;
6587 bugfix on 0.1.2.5-alpha.
6588 - Enlarge the buffer to read bwauth generated files to avoid an
6589 issue when parsing the file in dirserv_read_measured_bandwidths().
6590 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
6592 o Minor bugfixes (statistics):
6593 - Increase period over which bandwidth observations are aggregated
6594 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
6596 o Minor bugfixes (preventative security, C safety):
6597 - When reading a hexadecimal, base-32, or base-64 encoded value from
6598 a string, always overwrite the whole output buffer. This prevents
6599 some bugs where we would look at (but fortunately, not reveal)
6600 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
6604 Changes in version 0.2.4.26 - 2015-03-17
6605 Tor 0.2.4.26 includes an updated list of directory authorities. It
6606 also backports a couple of stability and security bugfixes from 0.2.5
6609 o Directory authority changes:
6610 - Remove turtles as a directory authority.
6611 - Add longclaw as a new (v3) directory authority. This implements
6612 ticket 13296. This keeps the directory authority count at 9.
6613 - The directory authority Faravahar has a new IP address. This
6614 closes ticket 14487.
6616 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
6617 - Fix an assertion failure that could occur under high DNS load.
6618 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
6619 diagnosed and fixed by "cypherpunks".
6621 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
6622 - Fix a bug that could lead to a relay crashing with an assertion
6623 failure if a buffer of exactly the wrong layout was passed to
6624 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6625 0.2.0.10-alpha. Patch from 'cypherpunks'.
6626 - Do not assert if the 'data' pointer on a buffer is advanced to the
6627 very end of the buffer; log a BUG message instead. Only assert if
6628 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6630 o Minor features (geoip):
6631 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6632 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6635 Changes in version 0.2.6.4-rc - 2015-03-09
6636 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
6637 attacker might be able to use in order to crash certain Tor
6638 directories. It also resolves some minor issues left over from, or
6639 introduced in, Tor 0.2.6.3-alpha or earlier.
6641 o Major bugfixes (crash, OSX, security):
6642 - Fix a remote denial-of-service opportunity caused by a bug in
6643 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
6646 o Major bugfixes (relay, stability, possible security):
6647 - Fix a bug that could lead to a relay crashing with an assertion
6648 failure if a buffer of exactly the wrong layout is passed to
6649 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
6650 0.2.0.10-alpha. Patch from "cypherpunks".
6651 - Do not assert if the 'data' pointer on a buffer is advanced to the
6652 very end of the buffer; log a BUG message instead. Only assert if
6653 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
6655 o Major bugfixes (FreeBSD IPFW transparent proxy):
6656 - Fix address detection with FreeBSD transparent proxies, when
6657 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
6660 o Major bugfixes (Linux seccomp2 sandbox):
6661 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
6662 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
6664 - Allow AF_UNIX hidden services to be used with the seccomp2
6665 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
6666 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
6667 crash during attempts to call wait4. Fixes bug 15088; bugfix on
6668 0.2.5.1-alpha. Patch from "sanic".
6670 o Minor features (controller):
6671 - Messages about problems in the bootstrap process now include
6672 information about the server we were trying to connect to when we
6673 noticed the problem. Closes ticket 15006.
6675 o Minor features (geoip):
6676 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
6677 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
6680 o Minor features (logs):
6681 - Quiet some log messages in the heartbeat and at startup. Closes
6684 o Minor bugfixes (certificate handling):
6685 - If an authority operator accidentally makes a signing certificate
6686 with a future publication time, do not discard its real signing
6687 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
6688 - Remove any old authority certificates that have been superseded
6689 for at least two days. Previously, we would keep superseded
6690 certificates until they expired, if they were published close in
6691 time to the certificate that superseded them. Fixes bug 11454;
6692 bugfix on 0.2.1.8-alpha.
6694 o Minor bugfixes (compilation):
6695 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
6697 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
6700 o Minor bugfixes (testing):
6701 - Fix endianness issues in unit test for resolve_my_address() to
6702 have it pass on big endian systems. Fixes bug 14980; bugfix on
6704 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
6705 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
6706 - When running the new 'make test-stem' target, use the configured
6707 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
6709 - When running the zero-length-keys tests, do not use the default
6710 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
6713 o Directory authority IP change:
6714 - The directory authority Faravahar has a new IP address. This
6715 closes ticket 14487.
6718 - Remove some lingering dead code that once supported mempools.
6719 Mempools were disabled by default in 0.2.5, and removed entirely
6720 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
6724 Changes in version 0.2.6.3-alpha - 2015-02-19
6725 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
6726 the 0.2.6.x series. It introduces support for more kinds of sockets,
6727 makes it harder to accidentally run an exit, improves our
6728 multithreading backend, incorporates several fixes for the
6729 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
6731 If no major regressions or security holes are found in this version,
6732 the next version will be a release candidate.
6734 o Deprecated versions:
6735 - Tor relays older than 0.2.4.18-rc are no longer allowed to
6736 advertise themselves on the network. Closes ticket 13555.
6738 o Major features (security, unix domain sockets):
6739 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
6740 applications can reach Tor without having to create AF_INET or
6741 AF_INET6 sockets, meaning they can completely disable their
6742 ability to make non-Tor network connections. To create a socket of
6743 this type, use "SocksPort unix:/path/to/socket". Implements
6745 - Support mapping hidden service virtual ports to AF_UNIX sockets.
6746 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
6747 Implements ticket 11485.
6749 o Major features (changed defaults):
6750 - Prevent relay operators from unintentionally running exits: When a
6751 relay is configured as an exit node, we now warn the user unless
6752 the "ExitRelay" option is set to 1. We warn even more loudly if
6753 the relay is configured with the default exit policy, since this
6754 can indicate accidental misconfiguration. Setting "ExitRelay 0"
6755 stops Tor from running as an exit relay. Closes ticket 10067.
6757 o Major features (directory system):
6758 - When downloading server- or microdescriptors from a directory
6759 server, we no longer launch multiple simultaneous requests to the
6760 same server. This reduces load on the directory servers,
6761 especially when directory guards are in use. Closes ticket 9969.
6762 - When downloading server- or microdescriptors over a tunneled
6763 connection, do not limit the length of our requests to what the
6764 Squid proxy is willing to handle. Part of ticket 9969.
6765 - Authorities can now vote on the correct digests and latest
6766 versions for different software packages. This allows packages
6767 that include Tor to use the Tor authority system as a way to get
6768 notified of updates and their correct digests. Implements proposal
6769 227. Closes ticket 10395.
6771 o Major features (guards):
6772 - Introduce the Guardfraction feature to improves load balancing on
6773 guard nodes. Specifically, it aims to reduce the traffic gap that
6774 guard nodes experience when they first get the Guard flag. This is
6775 a required step if we want to increase the guard lifetime to 9
6776 months or greater. Closes ticket 9321.
6778 o Major features (performance):
6779 - Make the CPU worker implementation more efficient by avoiding the
6780 kernel and lengthening pipelines. The original implementation used
6781 sockets to transfer data from the main thread to the workers, and
6782 didn't allow any thread to be assigned more than a single piece of
6783 work at once. The new implementation avoids communications
6784 overhead by making requests in shared memory, avoiding kernel IO
6785 where possible, and keeping more requests in flight at once.
6786 Implements ticket 9682.
6788 o Major features (relay):
6789 - Raise the minimum acceptable configured bandwidth rate for bridges
6790 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
6791 20 KiB/sec.) Closes ticket 13822.
6793 o Major bugfixes (exit node stability):
6794 - Fix an assertion failure that could occur under high DNS load.
6795 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
6796 diagnosed and fixed by "cypherpunks".
6798 o Major bugfixes (mixed relay-client operation):
6799 - When running as a relay and client at the same time (not
6800 recommended), if we decide not to use a new guard because we want
6801 to retry older guards, only close the locally-originating circuits
6802 passing through that guard. Previously we would close all the
6803 circuits through that guard. Fixes bug 9819; bugfix on
6804 0.2.1.1-alpha. Reported by "skruffy".
6806 o Minor features (build):
6807 - New --disable-system-torrc compile-time option to prevent Tor from
6808 looking for the system-wide torrc or torrc-defaults files.
6809 Resolves ticket 13037.
6811 o Minor features (controller):
6812 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
6813 events so controllers can observe circuit isolation inputs. Closes
6815 - ControlPort now supports the unix:/path/to/socket syntax as an
6816 alternative to the ControlSocket option, for consistency with
6817 SocksPort and HiddenServicePort. Closes ticket 14451.
6818 - New "GETINFO bw-event-cache" to get information about recent
6819 bandwidth events. Closes ticket 14128. Useful for controllers to
6820 get recent bandwidth history after the fix for ticket 13988.
6822 o Minor features (Denial of service resistance):
6823 - Count the total number of bytes used storing hidden service
6824 descriptors against the value of MaxMemInQueues. If we're low on
6825 memory, and more than 20% of our memory is used holding hidden
6826 service descriptors, free them until no more than 10% of our
6827 memory holds hidden service descriptors. Free the least recently
6828 fetched descriptors first. Resolves ticket 13806.
6829 - When we have recently been under memory pressure (over 3/4 of
6830 MaxMemInQueues is allocated), then allocate smaller zlib objects
6831 for small requests. Closes ticket 11791.
6833 o Minor features (geoip):
6834 - Update geoip and geoip6 files to the January 7 2015 Maxmind
6835 GeoLite2 Country database.
6837 o Minor features (guard nodes):
6838 - Reduce the time delay before saving guard status to disk from 10
6839 minutes to 30 seconds (or from one hour to 10 minutes if
6840 AvoidDiskWrites is set). Closes ticket 12485.
6842 o Minor features (hidden service):
6843 - Make Sybil attacks against hidden services harder by changing the
6844 minimum time required to get the HSDir flag from 25 hours up to 96
6845 hours. Addresses ticket 14149.
6846 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
6847 services to disable the anti-scanning feature introduced in
6848 0.2.6.2-alpha. With this option not set, a connection to an
6849 unlisted port closes the circuit. With this option set, only a
6850 RELAY_DONE cell is sent. Closes ticket 14084.
6852 o Minor features (interface):
6853 - Implement "-f -" command-line option to read torrc configuration
6854 from standard input, if you don't want to store the torrc file in
6855 the file system. Implements feature 13865.
6857 o Minor features (logging):
6858 - Add a count of unique clients to the bridge heartbeat message.
6859 Resolves ticket 6852.
6860 - Suppress "router info incompatible with extra info" message when
6861 reading extrainfo documents from cache. (This message got loud
6862 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
6864 - Elevate hidden service authorized-client message from DEBUG to
6865 INFO. Closes ticket 14015.
6867 o Minor features (stability):
6868 - Add assertions in our hash-table iteration code to check for
6869 corrupted values that could cause infinite loops. Closes
6872 o Minor features (systemd):
6873 - Various improvements and modernizations in systemd hardening
6874 support. Closes ticket 13805. Patch from Craig Andrews.
6876 o Minor features (testing networks):
6877 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
6878 and the default on a testing network to 2 minutes. Drop the
6879 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
6880 keep the default on a testing network at 30 seconds. This reduces
6881 HS bootstrap time to around 25 seconds. Also, change the default
6882 time in test-network.sh to match. Closes ticket 13401. Patch
6884 - Create TestingDirAuthVoteHSDir to correspond to
6885 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
6886 HSDir flag for the listed relays regardless of uptime or ORPort
6887 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
6888 Partial implementation for ticket 14067. Patch by "teor".
6890 o Minor features (tor2web mode):
6891 - Introduce the config option Tor2webRendezvousPoints, which allows
6892 clients in Tor2webMode to select a specific Rendezvous Point to be
6893 used in HS circuits. This might allow better performance for
6894 Tor2Web nodes. Implements ticket 12844.
6896 o Minor bugfixes (client DNS):
6897 - Report the correct cached DNS expiration times on SOCKS port or in
6898 DNS replies. Previously, we would report everything as "never
6899 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
6900 - Avoid a small memory leak when we find a cached answer for a
6901 reverse DNS lookup in a client-side DNS cache. (Remember, client-
6902 side DNS caching is off by default, and is not recommended.) Fixes
6903 bug 14259; bugfix on 0.2.0.1-alpha.
6905 o Minor bugfixes (client, automapping):
6906 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
6907 no value follows the option. Fixes bug 14142; bugfix on
6908 0.2.4.7-alpha. Patch by "teor".
6909 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
6910 14195; bugfix on 0.1.0.1-rc.
6911 - Prevent changes to other options from removing the wildcard value
6912 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
6914 - Allow MapAddress and AutomapHostsOnResolve to work together when
6915 an address is mapped into another address type (like .onion) that
6916 must be automapped at resolve time. Fixes bug 7555; bugfix
6919 o Minor bugfixes (client, bridges):
6920 - When we are using bridges and we had a network connectivity
6921 problem, only retry connecting to our currently configured
6922 bridges, not all bridges we know about and remember using. Fixes
6923 bug 14216; bugfix on 0.2.2.17-alpha.
6925 o Minor bugfixes (client, IPv6):
6926 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
6927 flag is not set; and not because the NoIPv4Traffic flag was set.
6928 Previously we'd looked at the NoIPv4Traffic flag for both types of
6929 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
6931 o Minor bugfixes (compilation):
6932 - The address of an array in the middle of a structure will always
6933 be non-NULL. clang recognises this and complains. Disable the
6934 tautologous and redundant check to silence this warning. Fixes bug
6935 14001; bugfix on 0.2.1.2-alpha.
6936 - Avoid warnings when building with systemd 209 or later. Fixes bug
6937 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
6938 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
6939 Addresses ticket 14188.
6940 - Build without warnings with the stock OpenSSL srtp.h header, which
6941 has a duplicate declaration of SSL_get_selected_srtp_profile().
6942 Fixes bug 14220; this is OpenSSL's bug, not ours.
6943 - Do not compile any code related to Tor2Web mode when Tor2Web mode
6944 is not enabled at compile time. Previously, this code was included
6945 in a disabled state. See discussion on ticket 12844.
6946 - Remove the --disable-threads configure option again. It was
6947 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
6948 14819; bugfix on 0.2.6.2-alpha.
6950 o Minor bugfixes (controller):
6951 - Report "down" in response to the "GETINFO entry-guards" command
6952 when relays are down with an unreachable_since value. Previously,
6953 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
6954 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
6955 14116; bugfix on 0.2.2.9-alpha.
6956 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
6957 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
6959 o Minor bugfixes (directory authority):
6960 - Allow directory authorities to fetch more data from one another if
6961 they find themselves missing lots of votes. Previously, they had
6962 been bumping against the 10 MB queued data limit. Fixes bug 14261;
6963 bugfix on 0.1.2.5-alpha.
6964 - Do not attempt to download extrainfo documents which we will be
6965 unable to validate with a matching server descriptor. Fixes bug
6966 13762; bugfix on 0.2.0.1-alpha.
6967 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
6968 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
6969 - Enlarge the buffer to read bwauth generated files to avoid an
6970 issue when parsing the file in dirserv_read_measured_bandwidths().
6971 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
6973 o Minor bugfixes (file handling):
6974 - Stop failing when key files are zero-length. Instead, generate new
6975 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
6976 on all versions of Tor. Patch by "teor".
6977 - Stop generating a fresh .old RSA onion key file when the .old file
6978 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
6979 - Avoid overwriting .old key files with empty key files.
6980 - Skip loading zero-length extrainfo store, router store, stats,
6981 state, and key files.
6982 - Avoid crashing when trying to reload a torrc specified as a
6983 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
6986 o Minor bugfixes (hidden services):
6987 - Close the introduction circuit when we have no more usable intro
6988 points, instead of waiting for it to time out. This also ensures
6989 that no follow-up HS descriptor fetch is triggered when the
6990 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
6991 - When fetching a hidden service descriptor for a down service that
6992 was recently up, do not keep refetching until we try the same
6993 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
6994 - Successfully launch Tor with a nonexistent hidden service
6995 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
6996 14106; bugfix on 0.2.6.2-alpha.
6998 o Minor bugfixes (logging):
6999 - Avoid crashing when there are more log domains than entries in
7000 domain_list. Bugfix on 0.2.3.1-alpha.
7001 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
7003 - Don't log messages to stdout twice when starting up. Fixes bug
7004 13993; bugfix on 0.2.6.1-alpha.
7006 o Minor bugfixes (parsing):
7007 - Stop accepting milliseconds (or other junk) at the end of
7008 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
7009 - Support two-number and three-number version numbers correctly, in
7010 case we change the Tor versioning system in the future. Fixes bug
7011 13661; bugfix on 0.0.8pre1.
7013 o Minor bugfixes (path counting):
7014 - When deciding whether the consensus lists any exit nodes, count
7015 the number listed in the consensus, not the number we have
7016 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
7017 - When deciding whether we have any exit nodes, only examine
7018 ExitNodes when the ExitNodes option is actually set. Fixes part of
7019 bug 14918; bugfix on 0.2.6.2-alpha.
7020 - Get rid of redundant and possibly scary warnings that we are
7021 missing directory information while we bootstrap. Fixes part of
7022 bug 14918; bugfix on 0.2.6.2-alpha.
7024 o Minor bugfixes (portability):
7025 - Fix the ioctl()-based network interface lookup code so that it
7026 will work on systems that have variable-length struct ifreq, for
7028 - Fix scheduler compilation on targets where char is unsigned. Fixes
7029 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
7031 o Minor bugfixes (sandbox):
7032 - Allow glibc fatal errors to be sent to stderr before Tor exits.
7033 Previously, glibc would try to write them to /dev/tty, and the
7034 sandbox would trap the call and make Tor exit prematurely. Fixes
7035 bug 14759; bugfix on 0.2.5.1-alpha.
7037 o Minor bugfixes (shutdown):
7038 - When shutting down, always call event_del() on lingering read or
7039 write events before freeing them. Otherwise, we risk double-frees
7040 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
7043 o Minor bugfixes (small memory leaks):
7044 - Avoid leaking memory when using IPv6 virtual address mappings.
7045 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
7048 o Minor bugfixes (statistics):
7049 - Increase period over which bandwidth observations are aggregated
7050 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
7052 o Minor bugfixes (systemd support):
7053 - Fix detection and operation of systemd watchdog. Fixes part of bug
7054 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
7055 - Run correctly under systemd with the RunAsDaemon option set. Fixes
7056 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
7057 - Inform the systemd supervisor about more changes in the Tor
7058 process status. Implements part of ticket 14141. Patch from
7060 - Cause the "--disable-systemd" option to actually disable systemd
7061 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
7064 o Minor bugfixes (TLS):
7065 - Check more thoroughly throughout the TLS code for possible
7066 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
7068 o Minor bugfixes (transparent proxy):
7069 - Use getsockname, not getsockopt, to retrieve the address for a
7070 TPROXY-redirected connection. Fixes bug 13796; bugfix
7073 o Code simplification and refactoring:
7074 - Move fields related to isolating and configuring client ports into
7075 a shared structure. Previously, they were duplicated across
7076 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
7077 to copy them correctly had been the cause of at least one bug in
7078 the past. Closes ticket 8546.
7079 - Refactor the get_interface_addresses_raw() doom-function into
7080 multiple smaller and simpler subfunctions. Cover the resulting
7081 subfunctions with unit-tests. Fixes a significant portion of
7083 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
7084 only for version <= 0.2.2.24 which is now deprecated. Closes
7086 - Remove a test for a long-defunct broken version-one
7090 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
7091 for writing the OpenBSD-specific tips. Resolves ticket 13702.
7092 - Make the tor-resolve documentation match its help string and its
7093 options. Resolves part of ticket 14325.
7094 - Log a more useful error message from tor-resolve when failing to
7095 look up a hidden service address. Resolves part of ticket 14325.
7097 o Downgraded warnings:
7098 - Don't warn when we've attempted to contact a relay using the wrong
7099 ntor onion key. Closes ticket 9635.
7102 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
7103 longer silently accepted as an alias for "ExitNodes".
7104 - The --enable-mempool and --enable-buf-freelists options, which
7105 were originally created to work around bad malloc implementations,
7106 no longer exist. They were off-by-default in 0.2.5. Closes
7110 - Make the checkdir/perms test complete successfully even if the
7111 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
7112 - Test that tor does not fail when key files are zero-length. Check
7113 that tor generates new keys, and overwrites the empty key files.
7114 - Test that tor generates new keys when keys are missing
7115 (existing behavior).
7116 - Test that tor does not overwrite key files that already contain
7117 data (existing behavior). Tests bug 13111. Patch by "teor".
7118 - New "make test-stem" target to run stem integration tests.
7119 Requires that the "STEM_SOURCE_DIR" environment variable be set.
7120 Closes ticket 14107.
7121 - Make the test_cmdline_args.py script work correctly on Windows.
7122 Patch from Gisle Vanem.
7123 - Move the slower unit tests into a new "./src/test/test-slow"
7124 binary that can be run independently of the other tests. Closes
7126 - Avoid undefined behavior when sampling huge values from the
7127 Laplace distribution. This made unittests fail on Raspberry Pi.
7128 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
7131 Changes in version 0.2.6.2-alpha - 2014-12-31
7132 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
7133 It introduces a major new backend for deciding when to send cells on
7134 channels, which should lead down the road to big performance
7135 increases. It contains security and statistics features for better
7136 work on hidden services, and numerous bugfixes.
7138 This release contains many new unit tests, along with major
7139 performance improvements for running testing networks using Chutney.
7140 Thanks to a series of patches contributed by "teor", testing networks
7141 should now bootstrap in seconds, rather than minutes.
7143 o Major features (relay, infrastructure):
7144 - Complete revision of the code that relays use to decide which cell
7145 to send next. Formerly, we selected the best circuit to write on
7146 each channel, but we didn't select among channels in any
7147 sophisticated way. Now, we choose the best circuits globally from
7148 among those whose channels are ready to deliver traffic.
7150 This patch implements a new inter-cmux comparison API, a global
7151 high/low watermark mechanism and a global scheduler loop for
7152 transmission prioritization across all channels as well as among
7153 circuits on one channel. This schedule is currently tuned to
7154 (tolerantly) avoid making changes in network performance, but it
7155 should form the basis for major circuit performance increases in
7156 the future. Code by Andrea; tuning by Rob Jansen; implements
7159 o Major features (hidden services):
7160 - Make HS port scanning more difficult by immediately closing the
7161 circuit when a user attempts to connect to a nonexistent port.
7162 Closes ticket 13667.
7163 - Add a HiddenServiceStatistics option that allows Tor relays to
7164 gather and publish statistics about the overall size and volume of
7165 hidden service usage. Specifically, when this option is turned on,
7166 an HSDir will publish an approximate number of hidden services
7167 that have published descriptors to it the past 24 hours. Also, if
7168 a relay has acted as a hidden service rendezvous point, it will
7169 publish the approximate amount of rendezvous cells it has relayed
7170 the past 24 hours. The statistics themselves are obfuscated so
7171 that the exact values cannot be derived. For more details see
7172 proposal 238, "Better hidden service stats from Tor relays". This
7173 feature is currently disabled by default. Implements feature 13192.
7175 o Major bugfixes (client, automap):
7176 - Repair automapping with IPv6 addresses. This automapping should
7177 have worked previously, but one piece of debugging code that we
7178 inserted to detect a regression actually caused the regression to
7179 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
7180 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
7183 o Major bugfixes (hidden services):
7184 - When closing an introduction circuit that was opened in parallel
7185 with others, don't mark the introduction point as unreachable.
7186 Previously, the first successful connection to an introduction
7187 point would make the other introduction points get marked as
7188 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
7190 o Directory authority changes:
7191 - Remove turtles as a directory authority.
7192 - Add longclaw as a new (v3) directory authority. This implements
7193 ticket 13296. This keeps the directory authority count at 9.
7195 o Major removed features:
7196 - Tor clients no longer support connecting to hidden services
7197 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
7198 option has been removed. (There shouldn't be any hidden services
7199 running these versions on the network.) Closes ticket 7803.
7201 o Minor features (client):
7202 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
7203 is enabled, reject requests with IP addresses as hostnames.
7204 Resolves ticket 13315.
7206 o Minor features (controller):
7207 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
7208 write an unscheduled heartbeat message to the log. Implements
7211 o Minor features (geoip):
7212 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
7215 o Minor features (hidden services):
7216 - When re-enabling the network, don't try to build introduction
7217 circuits until we have successfully built a circuit. This makes
7218 hidden services come up faster when the network is re-enabled.
7219 Patch from "akwizgran". Closes ticket 13447.
7220 - When we fail to retrieve a hidden service descriptor, send the
7221 controller an "HS_DESC FAILED" controller event. Implements
7223 - New HiddenServiceDirGroupReadable option to cause hidden service
7224 directories and hostname files to be created group-readable. Patch
7225 from "anon", David Stainton, and "meejah". Closes ticket 11291.
7227 o Minor features (systemd):
7228 - Where supported, when running with systemd, report successful
7229 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
7230 - When running with systemd, support systemd watchdog messages. Part
7231 of ticket 11016. Patch by Michael Scherer.
7233 o Minor features (transparent proxy):
7234 - Update the transparent proxy option checks to allow for both ipfw
7235 and pf on OS X. Closes ticket 14002.
7236 - Use the correct option when using IPv6 with transparent proxy
7237 support on Linux. Resolves 13808. Patch by Francisco Blas
7240 o Minor bugfixes (preventative security, C safety):
7241 - When reading a hexadecimal, base-32, or base-64 encoded value from
7242 a string, always overwrite the whole output buffer. This prevents
7243 some bugs where we would look at (but fortunately, not reveal)
7244 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
7246 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
7247 just the part that's used. This makes it harder for data leak bugs
7248 to occur in the event of other programming failures. Resolves
7251 o Minor bugfixes (client, microdescriptors):
7252 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
7253 computing which microdescriptors to download. This keeps us from
7254 erroneous download behavior if two microdescriptor digests ever
7255 have the same first 160 bits. Fixes part of bug 13399; bugfix
7257 - Reset a router's status if its microdescriptor digest changes,
7258 even if the first 160 bits remain the same. Fixes part of bug
7259 13399; bugfix on 0.2.3.1-alpha.
7261 o Minor bugfixes (compilation):
7262 - Silence clang warnings under --enable-expensive-hardening,
7263 including implicit truncation of 64 bit values to 32 bit, const
7264 char assignment to self, tautological compare, and additional
7265 parentheses around equality tests. Fixes bug 13577; bugfix
7267 - Fix a clang warning about checking whether an address in the
7268 middle of a structure is NULL. Fixes bug 14001; bugfix
7271 o Minor bugfixes (hidden services):
7272 - Correctly send a controller event when we find that a rendezvous
7273 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
7274 - Pre-check directory permissions for new hidden-services to avoid
7275 at least one case of "Bug: Acting on config options left us in a
7276 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
7277 - When adding a new hidden service (for example, via SETCONF), Tor
7278 no longer congratulates the user for running a relay. Fixes bug
7279 13941; bugfix on 0.2.6.1-alpha.
7280 - When fetching hidden service descriptors, we now check not only
7281 for whether we got the hidden service we had in mind, but also
7282 whether we got the particular descriptors we wanted. This prevents
7283 a class of inefficient but annoying DoS attacks by hidden service
7284 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
7287 o Minor bugfixes (Linux seccomp2 sandbox):
7288 - Make transparent proxy support work along with the seccomp2
7289 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
7290 by Francisco Blas Izquierdo Riera.
7291 - Fix a memory leak in tor-resolve when running with the sandbox
7292 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
7294 o Minor bugfixes (logging):
7295 - Downgrade warnings about RSA signature failures to info log level.
7296 Emit a warning when an extra info document is found incompatible
7297 with a corresponding router descriptor. Fixes bug 9812; bugfix
7299 - Make connection_ap_handshake_attach_circuit() log the circuit ID
7300 correctly. Fixes bug 13701; bugfix on 0.0.6.
7302 o Minor bugfixes (misc):
7303 - Stop allowing invalid address patterns like "*/24" that contain
7304 both a wildcard address and a bit prefix length. This affects all
7305 our address-range parsing code. Fixes bug 7484; bugfix
7308 o Minor bugfixes (testing networks, fast startup):
7309 - Allow Tor to build circuits using a consensus with no exits. If
7310 the consensus has no exits (typical of a bootstrapping test
7311 network), allow Tor to build circuits once enough descriptors have
7312 been downloaded. This assists in bootstrapping a testing Tor
7313 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
7315 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
7316 header to directory servers. This allows us to obtain consensuses
7317 promptly when the consensus interval is very short. This assists
7318 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
7319 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
7320 - Stop assuming that private addresses are local when checking
7321 reachability in a TestingTorNetwork. Instead, when testing, assume
7322 all OR connections are remote. (This is necessary due to many test
7323 scenarios running all relays on localhost.) This assists in
7324 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
7325 0.1.0.1-rc. Patch by "teor".
7326 - Avoid building exit circuits from a consensus with no exits. Now
7327 thanks to our fix for 13718, we accept a no-exit network as not
7328 wholly lost, but we need to remember not to try to build exit
7329 circuits on it. Closes ticket 13814; patch by "teor".
7330 - Stop requiring exits to have non-zero bandwithcapacity in a
7331 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
7332 ignore exit bandwidthcapacity. This assists in bootstrapping a
7333 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
7334 on 0.2.0.3-alpha. Patch by "teor".
7335 - Add "internal" to some bootstrap statuses when no exits are
7336 available. If the consensus does not contain Exits, Tor will only
7337 build internal circuits. In this case, relevant statuses will
7338 contain the word "internal" as indicated in the Tor control-
7339 spec.txt. When bootstrap completes, Tor will be ready to build
7340 internal circuits. If a future consensus contains Exits, exit
7341 circuits may become available. Fixes part of bug 13718; bugfix on
7342 0.2.4.10-alpha. Patch by "teor".
7343 - Decrease minimum consensus interval to 10 seconds when
7344 TestingTorNetwork is set, or 5 seconds for the first consensus.
7345 Fix assumptions throughout the code that assume larger intervals.
7346 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
7348 - Avoid excluding guards from path building in minimal test
7349 networks, when we're in a test network and excluding guards would
7350 exclude all relays. This typically occurs in incredibly small tor
7351 networks, and those using "TestingAuthVoteGuard *". Fixes part of
7352 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
7354 o Code simplification and refactoring:
7355 - Stop using can_complete_circuits as a global variable; access it
7356 with a function instead.
7357 - Avoid using operators directly as macro arguments: this lets us
7358 apply coccinelle transformations to our codebase more directly.
7359 Closes ticket 13172.
7360 - Combine the functions used to parse ClientTransportPlugin and
7361 ServerTransportPlugin into a single function. Closes ticket 6456.
7362 - Add inline functions and convenience macros for inspecting channel
7363 state. Refactor the code to use convenience macros instead of
7364 checking channel state directly. Fixes issue 7356.
7365 - Document all members of was_router_added_t and rename
7366 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
7367 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
7368 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
7369 constant instead of hardcoded value. Fixes issue 13840.
7370 - Refactor our generic strmap and digestmap types into a single
7371 implementation, so that we can add a new digest256map
7375 - Document the bridge-authority-only 'networkstatus-bridges' file.
7376 Closes ticket 13713; patch from "tom".
7377 - Fix typo in PredictedPortsRelevanceTime option description in
7378 manpage. Resolves issue 13707.
7379 - Stop suggesting that users specify relays by nickname: it isn't a
7380 good idea. Also, properly cross-reference how to specify relays in
7381 all parts of manual documenting options that take a list of
7382 relays. Closes ticket 13381.
7383 - Clarify the HiddenServiceDir option description in manpage to make
7384 it clear that relative paths are taken with respect to the current
7385 working directory. Also clarify that this behavior is not
7386 guaranteed to remain indefinitely. Fixes issue 13913.
7389 - New tests for many parts of channel, relay, and circuitmux
7390 functionality. Code by Andrea; part of 9262.
7391 - New tests for parse_transport_line(). Part of ticket 6456.
7392 - In the unit tests, use chgrp() to change the group of the unit
7393 test temporary directory to the current user, so that the sticky
7394 bit doesn't interfere with tests that check directory groups.
7396 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
7400 Changes in version 0.2.6.1-alpha - 2014-10-30
7401 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
7402 includes numerous code cleanups and new tests, and fixes a large
7403 number of annoying bugs. Out-of-memory conditions are handled better
7404 than in 0.2.5, pluggable transports have improved proxy support, and
7405 clients now use optimistic data for contacting hidden services. Also,
7406 we are now more robust to changes in what we consider a parseable
7407 directory object, so that tightening restrictions does not have a risk
7408 of introducing infinite download loops.
7410 This is the first alpha release in a new series, so expect there to be
7411 bugs. Users who would rather test out a more stable branch should stay
7412 with 0.2.5.x for now.
7414 o New compiler and system requirements:
7415 - Tor 0.2.6.x requires that your compiler support more of the C99
7416 language standard than before. The 'configure' script now detects
7417 whether your compiler supports C99 mid-block declarations and
7418 designated initializers. If it does not, Tor will not compile.
7420 We may revisit this requirement if it turns out that a significant
7421 number of people need to build Tor with compilers that don't
7422 bother implementing a 15-year-old standard. Closes ticket 13233.
7423 - Tor no longer supports systems without threading support. When we
7424 began working on Tor, there were several systems that didn't have
7425 threads, or where the thread support wasn't able to run the
7426 threads of a single process on multiple CPUs. That no longer
7427 holds: every system where Tor needs to run well now has threading
7428 support. Resolves ticket 12439.
7430 o Removed platform support:
7431 - We no longer include special code to build on Windows CE; as far
7432 as we know, nobody has used Tor on Windows CE in a very long time.
7433 Closes ticket 11446.
7435 o Major features (bridges):
7436 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
7437 transports if they are configured via the "TOR_PT_PROXY"
7438 environment variable. Implements proposal 232. Resolves
7441 o Major features (client performance, hidden services):
7442 - Allow clients to use optimistic data when connecting to a hidden
7443 service, which should remove a round-trip from hidden service
7444 initialization. See proposal 181 for details. Implements
7447 o Major features (directory system):
7448 - Upon receiving an unparseable directory object, if its digest
7449 matches what we expected, then don't try to download it again.
7450 Previously, when we got a descriptor we didn't like, we would keep
7451 trying to download it over and over. Closes ticket 11243.
7453 o Major features (sample torrc):
7454 - Add a new, infrequently-changed "torrc.minimal". This file is
7455 similar to torrc.sample, but it will change as infrequently as
7456 possible, for the benefit of users whose systems prompt them for
7457 intervention whenever a default configuration file is changed.
7458 Making this change allows us to update torrc.sample to be a more
7459 generally useful "sample torrc".
7461 o Major bugfixes (directory authorities):
7462 - Do not assign the HSDir flag to relays if they are not Valid, or
7463 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
7465 o Major bugfixes (directory bandwidth performance):
7466 - Don't flush the zlib buffer aggressively when compressing
7467 directory information for clients. This should save about 7% of
7468 the bandwidth currently used for compressed descriptors and
7469 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
7471 o Minor features (security, memory wiping):
7472 - Ensure we securely wipe keys from memory after
7473 crypto_digest_get_digest and init_curve25519_keypair_from_file
7474 have finished using them. Resolves ticket 13477.
7476 o Minor features (security, out-of-memory handling):
7477 - When handling an out-of-memory condition, allocate less memory for
7478 temporary data structures. Fixes issue 10115.
7479 - When handling an out-of-memory condition, consider more types of
7480 buffers, including those on directory connections, and zlib
7481 buffers. Resolves ticket 11792.
7484 - When identity keypair is generated for first time, log a
7485 congratulatory message that links to the new relay lifecycle
7486 document. Implements feature 10427.
7488 o Minor features (client):
7489 - Clients are now willing to send optimistic data (before they
7490 receive a 'connected' cell) to relays of any version. (Relays
7491 without support for optimistic data are no longer supported on the
7492 Tor network.) Resolves ticket 13153.
7494 o Minor features (directory authorities):
7495 - Don't list relays with a bandwidth estimate of 0 in the consensus.
7496 Implements a feature proposed during discussion of bug 13000.
7497 - In tor-gencert, report an error if the user provides the same
7498 argument more than once.
7499 - If a directory authority can't find a best consensus method in the
7500 votes that it holds, it now falls back to its favorite consensus
7501 method. Previously, it fell back to method 1. Neither of these is
7502 likely to get enough signatures, but "fall back to favorite"
7503 doesn't require us to maintain support an obsolete consensus
7504 method. Implements part of proposal 215.
7506 o Minor features (logging):
7507 - On Unix-like systems, you can now use named pipes as the target of
7508 the Log option, and other options that try to append to files.
7509 Closes ticket 12061. Patch from "carlo von lynX".
7510 - When opening a log file at startup, send it every log message that
7511 we generated between startup and opening it. Previously, log
7512 messages that were generated before opening the log file were only
7513 logged to stdout. Closes ticket 6938.
7514 - Add a TruncateLogFile option to overwrite logs instead of
7515 appending to them. Closes ticket 5583.
7517 o Minor features (portability, Solaris):
7518 - Threads are no longer disabled by default on Solaris; we believe
7519 that the versions of Solaris with broken threading support are all
7520 obsolete by now. Resolves ticket 9495.
7522 o Minor features (relay):
7523 - Re-check our address after we detect a changed IP address from
7524 getsockname(). This ensures that the controller command "GETINFO
7525 address" will report the correct value. Resolves ticket 11582.
7527 - A new AccountingRule option lets Relays set whether they'd like
7528 AccountingMax to be applied separately to inbound and outbound
7529 traffic, or applied to the sum of inbound and outbound traffic.
7530 Resolves ticket 961. Patch by "chobe".
7532 o Minor features (testing networks):
7533 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
7534 the "Exit" flag regardless of their uptime, bandwidth, or exit
7535 policy. TestingTorNetwork must be set for this option to have any
7536 effect. Previously, authorities would take up to 35 minutes to
7537 give nodes the Exit flag in a test network. Partially implements
7540 o Minor features (validation):
7541 - Check all date/time values passed to tor_timegm and
7542 parse_rfc1123_time for validity, taking leap years into account.
7543 Improves HTTP header validation. Implemented with bug 13476.
7544 - In correct_tm(), limit the range of values returned by system
7545 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
7546 This means we don't have to deal with negative or too large dates,
7547 even if a clock is wrong. Otherwise we might fail to read a file
7548 written by us which includes such a date. Fixes bug 13476.
7550 o Minor bugfixes (bridge clients):
7551 - When configured to use a bridge without an identity digest (not
7552 recommended), avoid launching an extra channel to it when
7553 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
7555 o Minor bugfixes (bridges):
7556 - When DisableNetwork is set, do not launch pluggable transport
7557 plugins, and if any are running, terminate them. Fixes bug 13213;
7558 bugfix on 0.2.3.6-alpha.
7560 o Minor bugfixes (C correctness):
7561 - Fix several instances of possible integer overflow/underflow/NaN.
7562 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
7564 - In circuit_build_times_calculate_timeout() in circuitstats.c,
7565 avoid dividing by zero in the pareto calculations. This traps
7566 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
7568 - Fix an integer overflow in format_time_interval(). Fixes bug
7569 13393; bugfix on 0.2.0.10-alpha.
7570 - Set the correct day of year value when the system's localtime(_r)
7571 or gmtime(_r) functions fail to set struct tm. Not externally
7572 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
7573 - Avoid unlikely signed integer overflow in tor_timegm on systems
7574 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
7576 o Minor bugfixes (client):
7577 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
7578 BadExit flag are not considered worthy candidates. Fixes bug
7579 13066; bugfix on 0.1.2.3-alpha.
7580 - Use the consensus schedule for downloading consensuses, and not
7581 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
7582 - Handle unsupported or malformed SOCKS5 requests properly by
7583 responding with the appropriate error message before closing the
7584 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
7586 o Minor bugfixes (client, torrc):
7587 - Stop modifying the value of our DirReqStatistics torrc option just
7588 because we're not a bridge or relay. This bug was causing Tor
7589 Browser users to write "DirReqStatistics 0" in their torrc files
7590 as if they had chosen to change the config. Fixes bug 4244; bugfix
7592 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
7593 that our options have changed every time we SIGHUP. Fixes bug
7594 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
7596 o Minor bugfixes (controller):
7597 - Return an error when the second or later arguments of the
7598 "setevents" controller command are invalid events. Previously we
7599 would return success while silently skipping invalid events. Fixes
7600 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
7602 o Minor bugfixes (directory system):
7603 - Always believe that v3 directory authorities serve extra-info
7604 documents, whether they advertise "caches-extra-info" or not.
7605 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7606 - When running as a v3 directory authority, advertise that you serve
7607 extra-info documents so that clients who want them can find them
7608 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
7609 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
7610 Previously, directories offering BRIDGE_DIRINFO and some other
7611 flag (i.e. microdescriptors or extrainfo) would be ignored when
7612 looking for bridges. Partially fixes bug 13163; bugfix
7615 o Minor bugfixes (networking):
7616 - Check for orconns and use connection_or_close_for_error() rather
7617 than connection_mark_for_close() directly in the getsockopt()
7618 failure case of connection_handle_write_impl(). Fixes bug 11302;
7619 bugfix on 0.2.4.4-alpha.
7621 o Minor bugfixes (relay):
7622 - When generating our family list, remove spaces from around the
7623 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
7624 - If our previous bandwidth estimate was 0 bytes, allow publishing a
7625 new relay descriptor immediately. Fixes bug 13000; bugfix
7628 o Minor bugfixes (testing networks):
7629 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
7630 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
7631 - Stop using the default authorities in networks which provide both
7632 AlternateDirAuthority and AlternateBridgeAuthority. Partially
7633 fixes bug 13163; bugfix on 0.2.0.13-alpha.
7635 o Minor bugfixes (testing):
7636 - Stop spawn test failures due to a race condition between the
7637 SIGCHLD handler updating the process status, and the test reading
7638 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
7640 o Minor bugfixes (testing, Windows):
7641 - Avoid passing an extra backslash when creating a temporary
7642 directory for running the unit tests on Windows. Fixes bug 12392;
7643 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
7645 o Minor bugfixes (windows):
7646 - Remove code to special-case handling of NTE_BAD_KEYSET when
7647 acquiring windows CryptoAPI context. This error can't actually
7648 occur for the parameters we're providing. Fixes bug 10816; bugfix
7651 o Minor bugfixes (zlib):
7652 - Avoid truncating a zlib stream when trying to finalize it with an
7653 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
7656 - Allow our configure script to build correctly with autoconf 2.62
7657 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
7658 - Improve the error message from ./configure to make it clear that
7659 when asciidoc has not been found, the user will have to either add
7660 --disable-asciidoc argument or install asciidoc. Resolves
7663 o Code simplification and refactoring:
7664 - Change the entry_is_live() function to take named bitfield
7665 elements instead of an unnamed list of booleans. Closes
7667 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
7668 Resolves ticket 12205.
7669 - Use calloc and reallocarray functions instead of multiply-
7670 then-malloc. This makes it less likely for us to fall victim to an
7671 integer overflow attack when allocating. Resolves ticket 12855.
7672 - Use the standard macro name SIZE_MAX, instead of our
7674 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
7675 functions which take them as arguments. Replace 0 with NO_DIRINFO
7676 in a function call for clarity. Seeks to prevent future issues
7678 - Avoid 4 null pointer errors under clang static analysis by using
7679 tor_assert() to prove that the pointers aren't null. Fixes
7681 - Rework the API of policies_parse_exit_policy() to use a bitmask to
7682 represent parsing options, instead of a confusing mess of
7683 booleans. Resolves ticket 8197.
7684 - Introduce a helper function to parse ExitPolicy in
7685 or_options_t structure.
7688 - Add a doc/TUNING document with tips for handling large numbers of
7689 TCP connections when running busy Tor relay. Update the warning
7690 message to point to this file when running out of sockets
7691 operating system is allowing to use simultaneously. Resolves
7695 - We no longer remind the user about configuration options that have
7696 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
7697 - Remove our old, non-weighted bandwidth-based node selection code.
7698 Previously, we used it as a fallback when we couldn't perform
7699 weighted bandwidth-based node selection. But that would only
7700 happen in the cases where we had no consensus, or when we had a
7701 consensus generated by buggy or ancient directory authorities. In
7702 either case, it's better to use the more modern, better maintained
7703 algorithm, with reasonable defaults for the weights. Closes
7705 - Remove the --disable-curve25519 configure option. Relays and
7706 clients now are required to support curve25519 and the
7708 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
7709 used to be deprecated synonyms for "StrictNodes", are now marked
7710 obsolete. Resolves ticket 12226.
7711 - Clients don't understand the BadDirectory flag in the consensus
7712 anymore, and ignore it.
7715 - Refactor the function that chooses guard nodes so that it can more
7716 easily be tested; write some tests for it.
7717 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
7718 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
7719 - Create unit tests for format_time_interval(). With bug 13393.
7720 - Add unit tests for tor_timegm signed overflow, tor_timegm and
7721 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
7722 tests (visible) fixes in bug 13476.
7723 - Add a "coverage-html" make target to generate HTML-visualized
7724 coverage results when building with --enable-coverage. (Requires
7725 lcov.) Patch from Kevin Murray.
7726 - Enable the backtrace handler (where supported) when running the
7728 - Revise all unit tests that used the legacy test_* macros to
7729 instead use the recommended tt_* macros. This patch was generated
7730 with coccinelle, to avoid manual errors. Closes ticket 13119.
7732 o Distribution (systemd):
7733 - systemd unit file: only allow tor to write to /var/lib/tor and
7734 /var/log/tor. The rest of the filesystem is accessible for reading
7735 only. Patch by intrigeri; resolves ticket 12751.
7736 - systemd unit file: ensure that the process and all its children
7737 can never gain new privileges. Patch by intrigeri; resolves
7739 - systemd unit file: set up /var/run/tor as writable for the Tor
7740 service. Patch by intrigeri; resolves ticket 13196.
7742 o Removed features (directory authorities):
7743 - Remove code that prevented authorities from listing Tor relays
7744 affected by CVE-2011-2769 as guards. These relays are already
7745 rejected altogether due to the minimum version requirement of
7746 0.2.3.16-alpha. Closes ticket 13152.
7747 - The "AuthDirRejectUnlisted" option no longer has any effect, as
7748 the fingerprints file (approved-routers) has been deprecated.
7749 - Directory authorities do not support being Naming dirauths anymore.
7750 The "NamingAuthoritativeDir" config option is now obsolete.
7751 - Directory authorities do not support giving out the BadDirectory
7753 - Directory authorities no longer advertise or support consensus
7754 methods 1 through 12 inclusive. These consensus methods were
7755 obsolete and/or insecure: maintaining the ability to support them
7756 served no good purpose. Implements part of proposal 215; closes
7759 o Testing (test-network.sh):
7760 - Stop using "echo -n", as some shells' built-in echo doesn't
7761 support "-n". Instead, use "/bin/echo -n". Partially fixes
7763 - Stop an apparent test-network hang when used with make -j2. Fixes
7765 - Add a --delay option to test-network.sh, which configures the
7766 delay before the chutney network tests for data transmission.
7767 Partially implements ticket 13161.
7770 Changes in version 0.2.5.10 - 2014-10-24
7771 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
7773 It adds several new security features, including improved
7774 denial-of-service resistance for relays, new compiler hardening
7775 options, and a system-call sandbox for hardened installations on Linux
7776 (requires seccomp2). The controller protocol has several new features,
7777 resolving IPv6 addresses should work better than before, and relays
7778 should be a little more CPU-efficient. We've added support for more
7779 OpenBSD and FreeBSD transparent proxy types. We've improved the build
7780 system and testing infrastructure to allow unit testing of more parts
7781 of the Tor codebase. Finally, we've addressed several nagging pluggable
7782 transport usability issues, and included numerous other small bugfixes
7783 and features mentioned below.
7785 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
7786 have accumulated many known flaws; everyone should upgrade.
7788 o Deprecated versions:
7789 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
7790 attention for some while.
7793 Changes in version 0.2.5.9-rc - 2014-10-20
7794 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
7795 series. It disables SSL3 in response to the recent "POODLE" attack
7796 (even though POODLE does not affect Tor). It also works around a crash
7797 bug caused by some operating systems' response to the "POODLE" attack
7798 (which does affect Tor). It also contains a few miscellaneous fixes.
7800 o Major security fixes:
7801 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7802 today support TLS 1.0 or later, so we can safely turn off support
7803 for this old (and insecure) protocol. Fixes bug 13426.
7805 o Major bugfixes (openssl bug workaround):
7806 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
7807 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
7808 13471. This is a workaround for an OpenSSL bug.
7811 - Disable the sandbox name resolver cache when running tor-resolve:
7812 tor-resolve doesn't use the sandbox code, and turning it on was
7813 breaking attempts to do tor-resolve on a non-default server on
7814 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
7816 o Compilation fixes:
7817 - Build and run correctly on systems like OpenBSD-current that have
7818 patched OpenSSL to remove get_cipher_by_char and/or its
7819 implementations. Fixes issue 13325.
7821 o Downgraded warnings:
7822 - Downgrade the severity of the 'unexpected sendme cell from client'
7823 from 'warn' to 'protocol warning'. Closes ticket 8093.
7826 Changes in version 0.2.4.25 - 2014-10-20
7827 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
7828 (even though POODLE does not affect Tor). It also works around a crash
7829 bug caused by some operating systems' response to the "POODLE" attack
7830 (which does affect Tor).
7832 o Major security fixes (also in 0.2.5.9-rc):
7833 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
7834 today support TLS 1.0 or later, so we can safely turn off support
7835 for this old (and insecure) protocol. Fixes bug 13426.
7837 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
7838 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
7839 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
7840 13471. This is a workaround for an OpenSSL bug.
7843 Changes in version 0.2.5.8-rc - 2014-09-22
7844 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
7845 series. It fixes a bug that affects consistency and speed when
7846 connecting to hidden services, and it updates the location of one of
7847 the directory authorities.
7850 - Clients now send the correct address for their chosen rendezvous
7851 point when trying to access a hidden service. They used to send
7852 the wrong address, which would still work some of the time because
7853 they also sent the identity digest of the rendezvous point, and if
7854 the hidden service happened to try connecting to the rendezvous
7855 point from a relay that already had a connection open to it,
7856 the relay would reuse that connection. Now connections to hidden
7857 services should be more robust and faster. Also, this bug meant
7858 that clients were leaking to the hidden service whether they were
7859 on a little-endian (common) or big-endian (rare) system, which for
7860 some users might have reduced their anonymity. Fixes bug 13151;
7861 bugfix on 0.2.1.5-alpha.
7863 o Directory authority changes:
7864 - Change IP address for gabelmoo (v3 directory authority).
7867 Changes in version 0.2.4.24 - 2014-09-22
7868 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
7869 connecting to hidden services, and it updates the location of one of
7870 the directory authorities.
7873 - Clients now send the correct address for their chosen rendezvous
7874 point when trying to access a hidden service. They used to send
7875 the wrong address, which would still work some of the time because
7876 they also sent the identity digest of the rendezvous point, and if
7877 the hidden service happened to try connecting to the rendezvous
7878 point from a relay that already had a connection open to it,
7879 the relay would reuse that connection. Now connections to hidden
7880 services should be more robust and faster. Also, this bug meant
7881 that clients were leaking to the hidden service whether they were
7882 on a little-endian (common) or big-endian (rare) system, which for
7883 some users might have reduced their anonymity. Fixes bug 13151;
7884 bugfix on 0.2.1.5-alpha.
7886 o Directory authority changes:
7887 - Change IP address for gabelmoo (v3 directory authority).
7889 o Minor features (geoip):
7890 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7894 Changes in version 0.2.5.7-rc - 2014-09-11
7895 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
7896 release series, and some long-standing bugs related to ORPort reachability
7897 testing and failure to send CREATE cells. It is the first release
7898 candidate for the Tor 0.2.5.x series.
7900 o Major bugfixes (client, startup):
7901 - Start making circuits as soon as DisabledNetwork is turned off.
7902 When Tor started with DisabledNetwork set, it would correctly
7903 conclude that it shouldn't build circuits, but it would mistakenly
7904 cache this conclusion, and continue believing it even when
7905 DisableNetwork is set to 0. Fixes the bug introduced by the fix
7906 for bug 11200; bugfix on 0.2.5.4-alpha.
7907 - Resume expanding abbreviations for command-line options. The fix
7908 for bug 4647 accidentally removed our hack from bug 586 that
7909 rewrote HashedControlPassword to __HashedControlSessionPassword
7910 when it appears on the commandline (which allowed the user to set
7911 her own HashedControlPassword in the torrc file while the
7912 controller generates a fresh session password for each run). Fixes
7913 bug 12948; bugfix on 0.2.5.1-alpha.
7914 - Warn about attempts to run hidden services and relays in the same
7915 process: that's probably not a good idea. Closes ticket 12908.
7917 o Major bugfixes (relay):
7918 - Avoid queuing or sending destroy cells for circuit ID zero when we
7919 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
7920 Found and fixed by "cypherpunks".
7921 - Fix ORPort reachability detection on relays running behind a
7922 proxy, by correctly updating the "local" mark on the controlling
7923 channel when changing the address of an or_connection_t after the
7924 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
7926 o Minor features (bridge):
7927 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
7928 cookie file for the ExtORPort g+r by default.
7930 o Minor features (geoip):
7931 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
7934 o Minor bugfixes (logging):
7935 - Reduce the log severity of the "Pluggable transport proxy does not
7936 provide any needed transports and will not be launched." message,
7937 since Tor Browser includes several ClientTransportPlugin lines in
7938 its torrc-defaults file, leading every Tor Browser user who looks
7939 at her logs to see these notices and wonder if they're dangerous.
7940 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
7941 - Downgrade "Unexpected onionskin length after decryption" warning
7942 to a protocol-warn, since there's nothing relay operators can do
7943 about a client that sends them a malformed create cell. Resolves
7944 bug 12996; bugfix on 0.0.6rc1.
7945 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
7946 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
7947 - When logging information about an EXTEND2 or EXTENDED2 cell, log
7948 their names correctly. Fixes part of bug 12700; bugfix
7950 - When logging information about a relay cell whose command we don't
7951 recognize, log its command as an integer. Fixes part of bug 12700;
7952 bugfix on 0.2.1.10-alpha.
7953 - Escape all strings from the directory connection before logging
7954 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
7956 o Minor bugfixes (controller):
7957 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
7958 bug 12864; bugfix on 0.2.5.1-alpha.
7959 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
7960 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
7963 o Minor bugfixes (compilation):
7964 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
7965 bugfix on 0.2.5.5-alpha.
7966 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
7967 0.2.5.1-alpha. Patch from "NewEraCracker".
7968 - In routerlist_assert_ok(), don't take the address of a
7969 routerinfo's cache_info member unless that routerinfo is non-NULL.
7970 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
7971 - Fix a large number of false positive warnings from the clang
7972 analyzer static analysis tool. This should make real warnings
7973 easier for clang analyzer to find. Patch from "teor". Closes
7976 o Distribution (systemd):
7977 - Verify configuration file via ExecStartPre in the systemd unit
7978 file. Patch from intrigeri; resolves ticket 12730.
7979 - Explicitly disable RunAsDaemon in the systemd unit file. Our
7980 current systemd unit uses "Type = simple", so systemd does not
7981 expect tor to fork. If the user has "RunAsDaemon 1" in their
7982 torrc, then things won't work as expected. This is e.g. the case
7983 on Debian (and derivatives), since there we pass "--defaults-torrc
7984 /usr/share/tor/tor-service-defaults-torrc" (that contains
7985 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
7989 - Adjust the URLs in the README to refer to the new locations of
7990 several documents on the website. Fixes bug 12830. Patch from
7992 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
7996 Changes in version 0.2.5.6-alpha - 2014-07-28
7997 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
7998 risk from guard rotation, and fixes a variety of other issues to get
7999 us closer to a release candidate.
8001 o Major features (also in 0.2.4.23):
8002 - Make the number of entry guards configurable via a new
8003 NumEntryGuards consensus parameter, and the number of directory
8004 guards configurable via a new NumDirectoryGuards consensus
8005 parameter. Implements ticket 12688.
8007 o Major bugfixes (also in 0.2.4.23):
8008 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8009 implementation that caused incorrect results on 32-bit
8010 implementations when certain malformed inputs were used along with
8011 a small class of private ntor keys. This bug does not currently
8012 appear to allow an attacker to learn private keys or impersonate a
8013 Tor server, but it could provide a means to distinguish 32-bit Tor
8014 implementations from 64-bit Tor implementations. Fixes bug 12694;
8015 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8019 - Perform circuit cleanup operations even when circuit
8020 construction operations are disabled (because the network is
8021 disabled, or because there isn't enough directory information).
8022 Previously, when we were not building predictive circuits, we
8023 were not closing expired circuits either. Fixes bug 8387; bugfix on
8024 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
8025 became more strict about when we have "enough directory information
8029 - Authorities now assign the Guard flag to the fastest 25% of the
8030 network (it used to be the fastest 50%). Also raise the consensus
8031 weight that guarantees the Guard flag from 250 to 2000. For the
8032 current network, this results in about 1100 guards, down from 2500.
8033 This step paves the way for moving the number of entry guards
8034 down to 1 (proposal 236) while still providing reasonable expected
8035 performance for most users. Implements ticket 12690.
8036 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8038 - Slightly enhance the diagnostic message for bug 12184.
8040 o Minor bugfixes (also in 0.2.4.23):
8041 - Warn and drop the circuit if we receive an inbound 'relay early'
8042 cell. Those used to be normal to receive on hidden service circuits
8043 due to bug 1038, but the buggy Tor versions are long gone from
8044 the network so we can afford to resume watching for them. Resolves
8045 the rest of bug 1038; bugfix on 0.2.1.19.
8046 - Correct a confusing error message when trying to extend a circuit
8047 via the control protocol but we don't know a descriptor or
8048 microdescriptor for one of the specified relays. Fixes bug 12718;
8049 bugfix on 0.2.3.1-alpha.
8052 - Fix compilation when building with bufferevents enabled. (This
8053 configuration is still not expected to work, however.)
8054 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
8055 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
8057 - Compile correctly with builds and forks of OpenSSL (such as
8058 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
8059 0.2.1.1-alpha. Patch from "dhill".
8062 Changes in version 0.2.4.23 - 2014-07-28
8063 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
8064 guard rotation, and also backports several important fixes from the
8065 Tor 0.2.5 alpha release series.
8068 - Clients now look at the "usecreatefast" consensus parameter to
8069 decide whether to use CREATE_FAST or CREATE cells for the first hop
8070 of their circuit. This approach can improve security on connections
8071 where Tor's circuit handshake is stronger than the available TLS
8072 connection security levels, but the tradeoff is more computational
8073 load on guard relays. Implements proposal 221. Resolves ticket 9386.
8074 - Make the number of entry guards configurable via a new
8075 NumEntryGuards consensus parameter, and the number of directory
8076 guards configurable via a new NumDirectoryGuards consensus
8077 parameter. Implements ticket 12688.
8080 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
8081 implementation that caused incorrect results on 32-bit
8082 implementations when certain malformed inputs were used along with
8083 a small class of private ntor keys. This bug does not currently
8084 appear to allow an attacker to learn private keys or impersonate a
8085 Tor server, but it could provide a means to distinguish 32-bit Tor
8086 implementations from 64-bit Tor implementations. Fixes bug 12694;
8087 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
8091 - Warn and drop the circuit if we receive an inbound 'relay early'
8092 cell. Those used to be normal to receive on hidden service circuits
8093 due to bug 1038, but the buggy Tor versions are long gone from
8094 the network so we can afford to resume watching for them. Resolves
8095 the rest of bug 1038; bugfix on 0.2.1.19.
8096 - Correct a confusing error message when trying to extend a circuit
8097 via the control protocol but we don't know a descriptor or
8098 microdescriptor for one of the specified relays. Fixes bug 12718;
8099 bugfix on 0.2.3.1-alpha.
8100 - Avoid an illegal read from stack when initializing the TLS
8101 module using a version of OpenSSL without all of the ciphers
8102 used by the v2 link handshake. Fixes bug 12227; bugfix on
8103 0.2.4.8-alpha. Found by "starlight".
8106 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
8110 Changes in version 0.2.5.5-alpha - 2014-06-18
8111 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
8112 0.2.5.x release series, including a couple of DoS issues, some
8113 performance regressions, a large number of bugs affecting the Linux
8114 seccomp2 sandbox code, and various other bugfixes. It also adds
8115 diagnostic bugfixes for a few tricky issues that we're trying to
8118 o Major features (security, traffic analysis resistance):
8119 - Several major improvements to the algorithm used to decide when to
8120 close TLS connections. Previous versions of Tor closed connections
8121 at a fixed interval after the last time a non-padding cell was
8122 sent over the connection, regardless of the target of the
8123 connection. Now, we randomize the intervals by adding up to 50% of
8124 their base value, we measure the length of time since connection
8125 last had at least one circuit, and we allow connections to known
8126 ORs to remain open a little longer (15 minutes instead of 3
8127 minutes minimum). These changes should improve Tor's resistance
8128 against some kinds of traffic analysis, and lower some overhead
8129 from needlessly closed connections. Fixes ticket 6799.
8130 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
8132 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
8133 - Fix a memory leak that could occur if a microdescriptor parse
8134 fails during the tokenizing step. This bug could enable a memory
8135 exhaustion attack by directory servers. Fixes bug 11649; bugfix
8138 o Major bugfixes (security, directory authorities):
8139 - Directory authorities now include a digest of each relay's
8140 identity key as a part of its microdescriptor.
8142 This is a workaround for bug 11743 (reported by "cypherpunks"),
8143 where Tor clients do not support receiving multiple
8144 microdescriptors with the same SHA256 digest in the same
8145 consensus. When clients receive a consensus like this, they only
8146 use one of the relays. Without this fix, a hostile relay could
8147 selectively disable some client use of target relays by
8148 constructing a router descriptor with a different identity and the
8149 same microdescriptor parameters and getting the authorities to
8150 list it in a microdescriptor consensus. This fix prevents an
8151 attacker from causing a microdescriptor collision, because the
8152 router's identity is not forgeable.
8154 o Major bugfixes (relay):
8155 - Use a direct dirport connection when uploading non-anonymous
8156 descriptors to the directory authorities. Previously, relays would
8157 incorrectly use tunnel connections under a fairly wide variety of
8158 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
8159 - When a circuit accidentally has the same circuit ID for its
8160 forward and reverse direction, correctly detect the direction of
8161 cells using that circuit. Previously, this bug made roughly one
8162 circuit in a million non-functional. Fixes bug 12195; this is a
8163 bugfix on every version of Tor.
8165 o Major bugfixes (client, pluggable transports):
8166 - When managing pluggable transports, use OS notification facilities
8167 to learn if they have crashed, and don't attempt to kill any
8168 process that has already exited. Fixes bug 8746; bugfix
8171 o Minor features (diagnostic):
8172 - When logging a warning because of bug 7164, additionally check the
8173 hash table for consistency (as proposed on ticket 11737). This may
8174 help diagnose bug 7164.
8175 - When we log a heartbeat, log how many one-hop circuits we have
8176 that are at least 30 minutes old, and log status information about
8177 a few of them. This is an attempt to track down bug 8387.
8178 - When encountering an unexpected CR while writing text to a file on
8179 Windows, log the name of the file. Should help diagnosing
8181 - Give more specific warnings when a client notices that an onion
8182 handshake has failed. Fixes ticket 9635.
8183 - Add significant new logging code to attempt to diagnose bug 12184,
8184 where relays seem to run out of available circuit IDs.
8185 - Improve the diagnostic log message for bug 8387 even further to
8186 try to improve our odds of figuring out why one-hop directory
8187 circuits sometimes do not get closed.
8189 o Minor features (security, memory management):
8190 - Memory allocation tricks (mempools and buffer freelists) are now
8191 disabled by default. You can turn them back on with
8192 --enable-mempools and --enable-buf-freelists respectively. We're
8193 disabling these features because malloc performance is good enough
8194 on most platforms, and a similar feature in OpenSSL exacerbated
8195 exploitation of the Heartbleed attack. Resolves ticket 11476.
8197 o Minor features (security):
8198 - Apply the secure SipHash-2-4 function to the hash table mapping
8199 circuit IDs and channels to circuits. We missed this one when we
8200 were converting all the other hash functions to use SipHash back
8201 in 0.2.5.3-alpha. Resolves ticket 11750.
8203 o Minor features (build):
8204 - The configure script has a --disable-seccomp option to turn off
8205 support for libseccomp on systems that have it, in case it (or
8206 Tor's use of it) is broken. Resolves ticket 11628.
8208 o Minor features (other):
8209 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
8212 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
8213 - When running a hidden service, do not allow TunneledDirConns 0;
8214 this will keep the hidden service from running, and also
8215 make it publish its descriptors directly over HTTP. Fixes bug 10849;
8216 bugfix on 0.2.1.1-alpha.
8218 o Minor bugfixes (performance):
8219 - Avoid a bug where every successful connection made us recompute
8220 the flag telling us whether we have sufficient information to
8221 build circuits. Previously, we would forget our cached value
8222 whenever we successfully opened a channel (or marked a router as
8223 running or not running for any other reason), regardless of
8224 whether we had previously believed the router to be running. This
8225 forced us to run an expensive update operation far too often.
8226 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
8227 - Avoid using tor_memeq() for checking relay cell integrity. This
8228 removes a possible performance bottleneck. Fixes part of bug
8229 12169; bugfix on 0.2.1.31.
8231 o Minor bugfixes (compilation):
8232 - Fix compilation of test_status.c when building with MVSC. Bugfix
8233 on 0.2.5.4-alpha. Patch from Gisle Vanem.
8234 - Resolve GCC complaints on OpenBSD about discarding constness in
8235 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
8236 on 0.1.1.23. Patch from Dana Koch.
8237 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
8238 treatment of long and time_t as comparable types. Fixes part of
8239 bug 11633. Patch from Dana Koch.
8240 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
8241 11623; bugfix on 0.2.5.3-alpha.
8242 - When deciding whether to build the 64-bit curve25519
8243 implementation, detect platforms where we can compile 128-bit
8244 arithmetic but cannot link it. Fixes bug 11729; bugfix on
8245 0.2.4.8-alpha. Patch from "conradev".
8246 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
8247 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
8248 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
8251 o Minor bugfixes (Directory server):
8252 - When sending a compressed set of descriptors or microdescriptors,
8253 make sure to finalize the zlib stream. Previously, we would write
8254 all the compressed data, but if the last descriptor we wanted to
8255 send was missing or too old, we would not mark the stream as
8256 finished. This caused problems for decompression tools. Fixes bug
8257 11648; bugfix on 0.1.1.23.
8259 o Minor bugfixes (Linux seccomp sandbox):
8260 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
8261 11622; bugfix on 0.2.5.1-alpha.
8262 - Avoid crashing when re-opening listener ports with the seccomp
8263 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
8264 - Avoid crashing with the seccomp sandbox enabled along with
8265 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
8266 - When we receive a SIGHUP with the sandbox enabled, correctly
8267 support rotating our log files. Fixes bug 12032; bugfix
8269 - Avoid crash when running with sandboxing enabled and
8270 DirReqStatistics not disabled. Fixes bug 12035; bugfix
8272 - Fix a "BUG" warning when trying to write bridge-stats files with
8273 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
8275 - Prevent the sandbox from crashing on startup when run with the
8276 --enable-expensive-hardening configuration option. Fixes bug
8277 11477; bugfix on 0.2.5.4-alpha.
8278 - When running with DirPortFrontPage and sandboxing both enabled,
8279 reload the DirPortFrontPage correctly when restarting. Fixes bug
8280 12028; bugfix on 0.2.5.1-alpha.
8281 - Don't try to enable the sandbox when using the Tor binary to check
8282 its configuration, hash a passphrase, or so on. Doing so was
8283 crashing on startup for some users. Fixes bug 11609; bugfix
8285 - Avoid warnings when running with sandboxing and node statistics
8286 enabled at the same time. Fixes part of 12064; bugfix on
8287 0.2.5.1-alpha. Patch from Michael Wolf.
8288 - Avoid warnings when running with sandboxing enabled at the same
8289 time as cookie authentication, hidden services, or directory
8290 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
8291 - Do not allow options that require calls to exec to be enabled
8292 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
8293 bug 12043; bugfix on 0.2.5.1-alpha.
8294 - Handle failures in getpwnam()/getpwuid() when running with the
8295 User option set and the Linux syscall sandbox enabled. Fixes bug
8296 11946; bugfix on 0.2.5.1-alpha.
8297 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
8298 to avoid calling getaddrinfo() after installing the sandbox
8299 filters. Previously, it preloaded a cache with the IPv4 address
8300 for our hostname, and nothing else. Now, it loads the cache with
8301 every address that it used to initialize the Tor process. Fixes
8302 bug 11970; bugfix on 0.2.5.1-alpha.
8304 o Minor bugfixes (pluggable transports):
8305 - Enable the ExtORPortCookieAuthFile option, to allow changing the
8306 default location of the authentication token for the extended OR
8307 Port as used by sever-side pluggable transports. We had
8308 implemented this option before, but the code to make it settable
8309 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
8310 - Avoid another 60-second delay when starting Tor in a pluggable-
8311 transport-using configuration when we already have cached
8312 descriptors for our bridges. Fixes bug 11965; bugfix
8315 o Minor bugfixes (client):
8316 - Avoid "Tried to open a socket with DisableNetwork set" warnings
8317 when starting a client with bridges configured and DisableNetwork
8318 set. (Tor launcher starts Tor with DisableNetwork set the first
8319 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
8321 o Minor bugfixes (testing):
8322 - The Python parts of the test scripts now work on Python 3 as well
8323 as Python 2, so systems where '/usr/bin/python' is Python 3 will
8324 no longer have the tests break. Fixes bug 11608; bugfix
8326 - When looking for versions of python that we could run the tests
8327 with, check for "python2.7" and "python3.3"; previously we were
8328 only looking for "python", "python2", and "python3". Patch from
8329 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
8330 - Fix all valgrind warnings produced by the unit tests. There were
8331 over a thousand memory leak warnings previously, mostly produced
8332 by forgetting to free things in the unit test code. Fixes bug
8333 11618, bugfixes on many versions of Tor.
8335 o Minor bugfixes (tor-fw-helper):
8336 - Give a correct log message when tor-fw-helper fails to launch.
8337 (Previously, we would say something like "tor-fw-helper sent us a
8338 string we could not parse".) Fixes bug 9781; bugfix
8341 o Minor bugfixes (relay, threading):
8342 - Check return code on spawn_func() in cpuworker code, so that we
8343 don't think we've spawned a nonworking cpuworker and write junk to
8344 it forever. Fix related to bug 4345; bugfix on all released Tor
8345 versions. Found by "skruffy".
8346 - Use a pthread_attr to make sure that spawn_func() cannot return an
8347 error while at the same time launching a thread. Fix related to
8348 bug 4345; bugfix on all released Tor versions. Reported
8351 o Minor bugfixes (relay, oom prevention):
8352 - Correctly detect the total available system memory. We tried to do
8353 this in 0.2.5.4-alpha, but the code was set up to always return an
8354 error value, even on success. Fixes bug 11805; bugfix
8357 o Minor bugfixes (relay, other):
8358 - We now drop CREATE cells for already-existent circuit IDs and for
8359 zero-valued circuit IDs, regardless of other factors that might
8360 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
8362 - Avoid an illegal read from stack when initializing the TLS module
8363 using a version of OpenSSL without all of the ciphers used by the
8364 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
8366 - When rejecting DATA cells for stream_id zero, still count them
8367 against the circuit's deliver window so that we don't fail to send
8368 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
8370 o Minor bugfixes (logging):
8371 - Fix a misformatted log message about delayed directory fetches.
8372 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
8373 - Squelch a spurious LD_BUG message "No origin circuit for
8374 successful SOCKS stream" in certain hidden service failure cases;
8378 - Include a tor.service file in contrib/dist for use with systemd.
8379 Some distributions will be able to use this file unmodified;
8380 others will need to tweak it, or write their own. Patch from Jamie
8381 Nguyen; resolves ticket 8368.
8384 - Clean up several option names in the manpage to match their real
8385 names, add the missing documentation for a couple of testing and
8386 directory authority options, remove the documentation for a
8387 V2-directory fetching option that no longer exists. Resolves
8389 - Correct the documenation so that it lists the correct directory
8390 for the stats files. (They are in a subdirectory called "stats",
8392 - In the manpage, move more authority-only options into the
8393 directory authority section so that operators of regular directory
8394 caches don't get confused.
8397 - The contrib directory has been sorted and tidied. Before, it was
8398 an unsorted dumping ground for useful and not-so-useful things.
8399 Now, it is divided based on functionality, and the items which
8400 seemed to be nonfunctional or useless have been removed. Resolves
8401 ticket 8966; based on patches from "rl1987".
8404 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
8405 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
8406 - The TunnelDirConns and PreferTunnelledDirConns options no longer
8407 exist; tunneled directory connections have been available since
8408 0.1.2.5-alpha, and turning them off is not a good idea. This is a
8409 brute-force fix for 10849, where "TunnelDirConns 0" would break
8413 Changes in version 0.2.4.22 - 2014-05-16
8414 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
8415 alpha release series. These include blocking all authority signing
8416 keys that may have been affected by the OpenSSL "heartbleed" bug,
8417 choosing a far more secure set of TLS ciphersuites by default, closing
8418 a couple of memory leaks that could be used to run a target relay out
8419 of RAM, and several others.
8421 o Major features (security, backport from 0.2.5.4-alpha):
8422 - Block authority signing keys that were used on authorities
8423 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
8424 don't have any evidence that these keys _were_ compromised; we're
8425 doing this to be prudent.) Resolves ticket 11464.
8427 o Major bugfixes (security, OOM):
8428 - Fix a memory leak that could occur if a microdescriptor parse
8429 fails during the tokenizing step. This bug could enable a memory
8430 exhaustion attack by directory servers. Fixes bug 11649; bugfix
8433 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
8434 - The relay ciphersuite list is now generated automatically based on
8435 uniform criteria, and includes all OpenSSL ciphersuites with
8436 acceptable strength and forward secrecy. Previously, we had left
8437 some perfectly fine ciphersuites unsupported due to omission or
8438 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
8439 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
8440 - Relays now trust themselves to have a better view than clients of
8441 which TLS ciphersuites are better than others. (Thanks to bug
8442 11513, the relay list is now well-considered, whereas the client
8443 list has been chosen mainly for anti-fingerprinting purposes.)
8444 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
8445 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
8446 AES128. Resolves ticket 11528.
8447 - Clients now try to advertise the same list of ciphersuites as
8448 Firefox 28. This change enables selection of (fast) GCM
8449 ciphersuites, disables some strange old ciphers, and stops
8450 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
8451 Resolves ticket 11438.
8453 o Minor bugfixes (configuration, security):
8454 - When running a hidden service, do not allow TunneledDirConns 0:
8455 trying to set that option together with a hidden service would
8456 otherwise prevent the hidden service from running, and also make
8457 it publish its descriptors directly over HTTP. Fixes bug 10849;
8458 bugfix on 0.2.1.1-alpha.
8460 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
8461 - Avoid sending a garbage value to the controller when a circuit is
8462 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
8464 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
8465 - Stop leaking memory when we successfully resolve a PTR record.
8466 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
8468 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
8469 - Avoid 60-second delays in the bootstrapping process when Tor is
8470 launching for a second time while using bridges. Fixes bug 9229;
8471 bugfix on 0.2.0.3-alpha.
8473 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
8474 - Give the correct URL in the warning message when trying to run a
8475 relay on an ancient version of Windows. Fixes bug 9393.
8477 o Minor bugfixes (compilation):
8478 - Fix a compilation error when compiling with --disable-curve25519.
8479 Fixes bug 9700; bugfix on 0.2.4.17-rc.
8482 - Downgrade the warning severity for the the "md was still
8483 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
8484 for trying to diagnose this bug, and the current warning in
8485 earlier versions of tor achieves nothing useful. Addresses warning
8488 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
8489 - When we run out of usable circuit IDs on a channel, log only one
8490 warning for the whole channel, and describe how many circuits
8491 there were on the channel. Fixes part of ticket 11553.
8493 o Minor features (security, backport from 0.2.5.4-alpha):
8494 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
8495 leave the default at 8GBytes), to better support Raspberry Pi
8496 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
8498 o Documentation (backport from 0.2.5.4-alpha):
8499 - Correctly document that we search for a system torrc file before
8500 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
8504 Changes in version 0.2.5.4-alpha - 2014-04-25
8505 Tor 0.2.5.4-alpha includes several security and performance
8506 improvements for clients and relays, including blacklisting authority
8507 signing keys that were used while susceptible to the OpenSSL
8508 "heartbleed" bug, fixing two expensive functions on busy relays,
8509 improved TLS ciphersuite preference lists, support for run-time
8510 hardening on compilers that support AddressSanitizer, and more work on
8511 the Linux sandbox code.
8513 There are also several usability fixes for clients (especially clients
8514 that use bridges), two new TransPort protocols supported (one on
8515 OpenBSD, one on FreeBSD), and various other bugfixes.
8517 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
8518 have accumulated many known flaws; everyone should upgrade.
8520 o Major features (security):
8521 - If you don't specify MaxMemInQueues yourself, Tor now tries to
8522 pick a good value based on your total system memory. Previously,
8523 the default was always 8 GB. You can still override the default by
8524 setting MaxMemInQueues yourself. Resolves ticket 11396.
8525 - Block authority signing keys that were used on authorities
8526 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
8527 don't have any evidence that these keys _were_ compromised; we're
8528 doing this to be prudent.) Resolves ticket 11464.
8530 o Major features (relay performance):
8531 - Speed up server-side lookups of rendezvous and introduction point
8532 circuits by using hashtables instead of linear searches. These
8533 functions previously accounted between 3 and 7% of CPU usage on
8534 some busy relays. Resolves ticket 9841.
8535 - Avoid wasting CPU when extending a circuit over a channel that is
8536 nearly out of circuit IDs. Previously, we would do a linear scan
8537 over possible circuit IDs before finding one or deciding that we
8538 had exhausted our possibilities. Now, we try at most 64 random
8539 circuit IDs before deciding that we probably won't succeed. Fixes
8540 a possible root cause of ticket 11553.
8542 o Major features (seccomp2 sandbox, Linux only):
8543 - The seccomp2 sandbox can now run a test network for multiple hours
8544 without crashing. The sandbox is still experimental, and more bugs
8545 will probably turn up. To try it, enable "Sandbox 1" on a Linux
8546 host. Resolves ticket 11351.
8547 - Strengthen sandbox code: the sandbox can now test the arguments
8548 for rename(), and blocks _sysctl() entirely. Resolves another part
8550 - When the sandbox blocks a system call, it now tries to log a stack
8551 trace before exiting. Resolves ticket 11465.
8553 o Major bugfixes (TLS cipher selection):
8554 - The relay ciphersuite list is now generated automatically based on
8555 uniform criteria, and includes all OpenSSL ciphersuites with
8556 acceptable strength and forward secrecy. Previously, we had left
8557 some perfectly fine ciphersuites unsupported due to omission or
8558 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
8559 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
8560 - Relays now trust themselves to have a better view than clients of
8561 which TLS ciphersuites are better than others. (Thanks to bug
8562 11513, the relay list is now well-considered, whereas the client
8563 list has been chosen mainly for anti-fingerprinting purposes.)
8564 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
8565 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
8566 AES128. Resolves ticket 11528.
8567 - Clients now try to advertise the same list of ciphersuites as
8568 Firefox 28. This change enables selection of (fast) GCM
8569 ciphersuites, disables some strange old ciphers, and stops
8570 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
8571 Resolves ticket 11438.
8573 o Major bugfixes (bridge client):
8574 - Avoid 60-second delays in the bootstrapping process when Tor is
8575 launching for a second time while using bridges. Fixes bug 9229;
8576 bugfix on 0.2.0.3-alpha.
8578 o Minor features (transparent proxy, *BSD):
8579 - Support FreeBSD's ipfw firewall interface for TransPort ports on
8580 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
8581 10267; patch from "yurivict".
8582 - Support OpenBSD's divert-to rules with the pf firewall for
8583 transparent proxy ports. To enable it, set "TransProxyType
8584 pf-divert". This allows Tor to run a TransPort transparent proxy
8585 port on OpenBSD 4.4 or later without root privileges. See the
8586 pf.conf(5) manual page for information on configuring pf to use
8587 divert-to rules. Closes ticket 10896; patch from Dana Koch.
8589 o Minor features (security):
8590 - New --enable-expensive-hardening option to enable security
8591 hardening options that consume nontrivial amounts of CPU and
8592 memory. Right now, this includes AddressSanitizer and UbSan, which
8593 are supported in newer versions of GCC and Clang. Closes ticket
8596 o Minor features (log verbosity):
8597 - Demote the message that we give when a flushing connection times
8598 out for too long from NOTICE to INFO. It was usually meaningless.
8599 Resolves ticket 5286.
8600 - Don't log so many notice-level bootstrapping messages at startup
8601 about downloading descriptors. Previously, we'd log a notice
8602 whenever we learned about more routers. Now, we only log a notice
8603 at every 5% of progress. Fixes bug 9963.
8604 - Warn less verbosely when receiving a malformed
8605 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
8606 - When we run out of usable circuit IDs on a channel, log only one
8607 warning for the whole channel, and describe how many circuits
8608 there were on the channel. Fixes part of ticket 11553.
8610 o Minor features (relay):
8611 - If a circuit timed out for at least 3 minutes, check if we have a
8612 new external IP address, and publish a new descriptor with the new
8613 IP address if it changed. Resolves ticket 2454.
8615 o Minor features (controller):
8616 - Make the entire exit policy available from the control port via
8617 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
8619 - Because of the fix for ticket 11396, the real limit for memory
8620 usage may no longer match the configured MaxMemInQueues value. The
8621 real limit is now exposed via GETINFO limits/max-mem-in-queues.
8623 o Minor features (bridge client):
8624 - Report a more useful failure message when we can't connect to a
8625 bridge because we don't have the right pluggable transport
8626 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
8628 o Minor features (diagnostic):
8629 - Add more log messages to diagnose bug 7164, which causes
8630 intermittent "microdesc_free() called but md was still referenced"
8631 warnings. We now include more information, to figure out why we
8632 might be cleaning a microdescriptor for being too old if it's
8633 still referenced by a live node_t object.
8635 o Minor bugfixes (client, DNSPort):
8636 - When using DNSPort, try to respond to AAAA requests with AAAA
8637 answers. Previously, we hadn't looked at the request type when
8638 deciding which answer type to prefer. Fixes bug 10468; bugfix on
8640 - When receiving a DNS query for an unsupported record type, reply
8641 with no answer rather than with a NOTIMPL error. This behavior
8642 isn't correct either, but it will break fewer client programs, we
8643 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
8646 o Minor bugfixes (exit relay):
8647 - Stop leaking memory when we successfully resolve a PTR record.
8648 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
8650 o Minor bugfixes (bridge client):
8651 - Stop accepting bridge lines containing hostnames. Doing so would
8652 cause clients to perform DNS requests on the hostnames, which was
8653 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
8654 - Avoid a 60-second delay in the bootstrapping process when a Tor
8655 client with pluggable transports re-reads its configuration at
8656 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
8658 o Minor bugfixes (client, logging during bootstrap):
8659 - Warn only once if we start logging in an unsafe way. Previously,
8660 we complain as many times as we had problems. Fixes bug 9870;
8661 bugfix on 0.2.5.1-alpha.
8662 - Only report the first fatal bootstrap error on a given OR
8663 connection. This stops us from telling the controller bogus error
8664 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
8665 - Be more helpful when trying to run sandboxed on Linux without
8666 libseccomp. Instead of saying "Sandbox is not implemented on this
8667 platform", we now explain that we need to be built with
8668 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
8669 - Avoid generating spurious warnings when starting with
8670 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
8673 o Minor bugfixes (closing OR connections):
8674 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
8675 check if it's an or_connection_t and correctly call
8676 connection_or_close_for_error() rather than
8677 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
8679 - When closing all connections on setting DisableNetwork to 1, use
8680 connection_or_close_normally() rather than closing OR connections
8681 out from under the channel layer. Fixes bug 11306; bugfix on
8684 o Minor bugfixes (controller):
8685 - Avoid sending a garbage value to the controller when a circuit is
8686 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
8688 o Minor bugfixes (tor-fw-helper):
8689 - Allow tor-fw-helper to build again by adding src/ext to its
8690 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
8692 o Minor bugfixes (bridges):
8693 - Avoid potential crashes or bad behavior when launching a
8694 server-side managed proxy with ORPort or ExtORPort temporarily
8695 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
8697 o Minor bugfixes (platform-specific):
8698 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
8699 bug 11426; bugfix on 0.2.5.3-alpha.
8700 - When dumping a malformed directory object to disk, save it in
8701 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
8703 - Don't report failures from make_socket_reuseable() on incoming
8704 sockets on OSX: this can happen when incoming connections close
8705 early. Fixes bug 10081.
8707 o Minor bugfixes (trivial memory leaks):
8708 - Fix a small memory leak when signing a directory object. Fixes bug
8709 11275; bugfix on 0.2.4.13-alpha.
8710 - Free placeholder entries in our circuit table at exit; fixes a
8711 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
8712 - Don't re-initialize a second set of OpenSSL mutexes when starting
8713 up. Previously, we'd make one set of mutexes, and then immediately
8714 replace them with another. Fixes bug 11726; bugfix on
8716 - Resolve some memory leaks found by coverity in the unit tests, on
8717 exit in tor-gencert, and on a failure to compute digests for our
8718 own keys when generating a v3 networkstatus vote. These leaks
8719 should never have affected anyone in practice.
8721 o Minor bugfixes (hidden service):
8722 - Only retry attempts to connect to a chosen rendezvous point 8
8723 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
8725 o Minor bugfixes (misc code correctness):
8726 - Fix various instances of undefined behavior in channeltls.c,
8727 tor_memmem(), and eventdns.c that would cause us to construct
8728 pointers to memory outside an allocated object. (These invalid
8729 pointers were not accessed, but C does not even allow them to
8730 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
8731 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
8732 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
8733 fix some miscellaneous errors in our tests and codebase. Fixes bug
8734 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
8735 - Always check return values for unlink, munmap, UnmapViewOfFile;
8736 check strftime return values more often. In some cases all we can
8737 do is report a warning, but this may help prevent deeper bugs from
8738 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
8740 - Fix numerous warnings from the clang "scan-build" static analyzer.
8741 Some of these are programming style issues; some of them are false
8742 positives that indicated awkward code; some are undefined behavior
8743 cases related to constructing (but not using) invalid pointers;
8744 some are assumptions about API behavior; some are (harmlessly)
8745 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
8746 correct; and one or two are genuine bugs that weren't reachable
8747 from the rest of the program. Fixes bug 8793; bugfixes on many,
8751 - Build the torify.1 manpage again. Previously, we were only trying
8752 to build it when also building tor-fw-helper. That's why we didn't
8753 notice that we'd broken the ability to build it. Fixes bug 11321;
8754 bugfix on 0.2.5.1-alpha.
8755 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
8756 11061; bugfix on 0.2.4.7-alpha.
8757 - Correctly document that we search for a system torrc file before
8758 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
8760 - Resolve warnings from Doxygen.
8762 o Code simplifications and refactoring:
8763 - Remove is_internal_IP() function. Resolves ticket 4645.
8764 - Remove unused function circuit_dump_by_chan from circuitlist.c.
8765 Closes issue 9107; patch from "marek".
8766 - Change our use of the ENUM_BF macro to avoid declarations that
8769 o Deprecated versions:
8770 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
8771 attention for some while. Directory authorities no longer accept
8772 descriptors from relays running any version of Tor prior to Tor
8773 0.2.3.16-alpha. Resolves ticket 11149.
8776 - New macros in test.h to simplify writing mock-functions for unit
8777 tests. Part of ticket 11507. Patch from Dana Koch.
8778 - Complete tests for the status.c module. Resolves ticket 11507.
8779 Patch from Dana Koch.
8782 - Remove all code for the long unused v1 directory protocol.
8783 Resolves ticket 11070.
8786 Changes in version 0.2.5.3-alpha - 2014-03-22
8787 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
8788 two new anti-DoS features for Tor relays, resolves a bug that kept
8789 SOCKS5 support for IPv6 from working, fixes several annoying usability
8790 issues for bridge users, and removes more old code for unused
8793 The Tor 0.2.5.x release series is now in patch-freeze: no feature
8794 patches not already written will be considered for inclusion in 0.2.5.x.
8796 o Major features (relay security, DoS-resistance):
8797 - When deciding whether we have run out of memory and we need to
8798 close circuits, also consider memory allocated in buffers for
8799 streams attached to each circuit.
8801 This change, which extends an anti-DoS feature introduced in
8802 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
8803 better resist more memory-based DoS attacks than before. Since the
8804 MaxMemInCellQueues option now applies to all queues, it is renamed
8805 to MaxMemInQueues. This feature fixes bug 10169.
8806 - Avoid hash-flooding denial-of-service attacks by using the secure
8807 SipHash-2-4 hash function for our hashtables. Without this
8808 feature, an attacker could degrade performance of a targeted
8809 client or server by flooding their data structures with a large
8810 number of entries to be stored at the same hash table position,
8811 thereby slowing down the Tor instance. With this feature, hash
8812 table positions are derived from a randomized cryptographic key,
8813 and an attacker cannot predict which entries will collide. Closes
8815 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
8816 the default at 8GBytes), to better support Raspberry Pi users. Fixes
8817 bug 9686; bugfix on 0.2.4.14-alpha.
8819 o Minor features (bridges, pluggable transports):
8820 - Bridges now write the SHA1 digest of their identity key
8821 fingerprint (that is, a hash of a hash of their public key) to
8822 notice-level logs, and to a new hashed-fingerprint file. This
8823 information will help bridge operators look up their bridge in
8824 Globe and similar tools. Resolves ticket 10884.
8825 - Improve the message that Tor displays when running as a bridge
8826 using pluggable transports without an Extended ORPort listener.
8827 Also, log the message in the log file too. Resolves ticket 11043.
8829 o Minor features (other):
8830 - Add a new option, PredictedPortsRelevanceTime, to control how long
8831 after having received a request to connect to a given port Tor
8832 will try to keep circuits ready in anticipation of future requests
8833 for that port. Patch from "unixninja92"; implements ticket 9176.
8834 - Generate a warning if any ports are listed in the SocksPolicy,
8835 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
8836 AuthDirBadExit options. (These options only support address
8837 ranges.) Fixes part of ticket 11108.
8838 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
8841 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
8842 - Build without warnings under clang 3.4. (We have some macros that
8843 define static functions only some of which will get used later in
8844 the module. Starting with clang 3.4, these give a warning unless the
8845 unused attribute is set on them.) Resolves ticket 10904.
8846 - Fix build warnings about missing "a2x" comment when building the
8847 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8848 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8850 o Minor bugfixes (client):
8851 - Improve the log message when we can't connect to a hidden service
8852 because all of the hidden service directory nodes hosting its
8853 descriptor are excluded. Improves on our fix for bug 10722, which
8854 was a bugfix on 0.2.0.10-alpha.
8855 - Raise a control port warning when we fail to connect to all of
8856 our bridges. Previously, we didn't inform the controller, and
8857 the bootstrap process would stall. Fixes bug 11069; bugfix on
8859 - Exit immediately when a process-owning controller exits.
8860 Previously, tor relays would wait for a little while after their
8861 controller exited, as if they had gotten an INT signal -- but this
8862 was problematic, since there was no feedback for the user. To do a
8863 clean shutdown, controllers should send an INT signal and give Tor
8864 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
8865 - Stop attempting to connect to bridges before our pluggable
8866 transports are configured (harmless but resulted in some erroneous
8867 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
8868 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
8869 generating incorrect SOCKS5 responses, and confusing client
8870 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
8872 o Minor bugfixes (relays and bridges):
8873 - Avoid crashing on a malformed resolv.conf file when running a
8874 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
8875 - Non-exit relays no longer launch mock DNS requests to check for
8876 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
8877 non-exit relays stopped servicing DNS requests. Fixes bug 965;
8878 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
8879 - Bridges now report complete directory request statistics. Related
8880 to bug 5824; bugfix on 0.2.2.1-alpha.
8881 - Bridges now never collect statistics that were designed for
8882 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
8883 - Stop giving annoying warning messages when we decide not to launch
8884 a pluggable transport proxy that we don't need (because there are
8885 no bridges configured to use it). Resolves ticket 5018; bugfix
8887 - Give the correct URL in the warning message when trying to run a
8888 relay on an ancient version of Windows. Fixes bug 9393.
8890 o Minor bugfixes (backtrace support):
8891 - Support automatic backtraces on more platforms by using the
8892 "-fasynchronous-unwind-tables" compiler option. This option is
8893 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
8894 is on by default and table generation is not. This doesn't yet
8895 add Windows support; only Linux, OSX, and some BSDs are affected.
8896 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
8897 - Avoid strange behavior if two threads hit failed assertions at the
8898 same time and both try to log backtraces at once. (Previously, if
8899 this had happened, both threads would have stored their intermediate
8900 results in the same buffer, and generated junk outputs.) Reported by
8901 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
8902 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
8903 0.2.5.2-alpha; patch from Nick Hopper.
8905 o Minor bugfixes (unit tests):
8906 - Fix a small bug in the unit tests that might have made the tests
8907 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
8908 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
8911 - Remove all remaining code related to version-0 hidden service
8912 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
8913 the rest of bug 10841.
8916 - Document in the manpage that "KBytes" may also be written as
8917 "kilobytes" or "KB", that "Kbits" may also be written as
8918 "kilobits", and so forth. Closes ticket 9222.
8919 - Document that the ClientOnly config option overrides ORPort.
8920 Our old explanation made ClientOnly sound as though it did
8921 nothing at all. Resolves bug 9059.
8922 - Explain that SocksPolicy, DirPolicy, and similar options don't
8923 take port arguments. Fixes the other part of ticket 11108.
8924 - Fix a comment about the rend_server_descriptor_t.protocols field
8925 to more accurately describe its range. Also, make that field
8926 unsigned, to more accurately reflect its usage. Fixes bug 9099;
8927 bugfix on 0.2.1.5-alpha.
8928 - Fix the manpage's description of HiddenServiceAuthorizeClient:
8929 the maximum client name length is 16, not 19. Fixes bug 11118;
8930 bugfix on 0.2.1.6-alpha.
8932 o Code simplifications and refactoring:
8933 - Get rid of router->address, since in all cases it was just the
8934 string representation of router->addr. Resolves ticket 5528.
8936 o Test infrastructure:
8937 - Update to the latest version of tinytest.
8938 - Improve the tinytest implementation of string operation tests so
8939 that comparisons with NULL strings no longer crash the tests; they
8940 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
8943 Changes in version 0.2.4.21 - 2014-02-28
8944 Tor 0.2.4.21 further improves security against potential adversaries who
8945 find breaking 1024-bit crypto doable, and backports several stability
8946 and robustness patches from the 0.2.5 branch.
8948 o Major features (client security):
8949 - When we choose a path for a 3-hop circuit, make sure it contains
8950 at least one relay that supports the NTor circuit extension
8951 handshake. Otherwise, there is a chance that we're building
8952 a circuit that's worth attacking by an adversary who finds
8953 breaking 1024-bit crypto doable, and that chance changes the game
8954 theory. Implements ticket 9777.
8957 - Do not treat streams that fail with reason
8958 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
8959 since it could also indicate an ENETUNREACH connection error. Fixes
8960 part of bug 10777; bugfix on 0.2.4.8-alpha.
8962 o Code simplification and refactoring:
8963 - Remove data structures which were introduced to implement the
8964 CellStatistics option: they are now redundant with the new timestamp
8965 field in the regular packed_cell_t data structure, which we did
8966 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
8969 - Always clear OpenSSL bignums before freeing them -- even bignums
8970 that don't contain secrets. Resolves ticket 10793. Patch by
8972 - Build without warnings under clang 3.4. (We have some macros that
8973 define static functions only some of which will get used later in
8974 the module. Starting with clang 3.4, these give a warning unless the
8975 unused attribute is set on them.) Resolves ticket 10904.
8976 - Update geoip and geoip6 files to the February 7 2014 Maxmind
8977 GeoLite2 Country database.
8980 - Set the listen() backlog limit to the largest actually supported
8981 on the system, not to the value in a header file. Fixes bug 9716;
8982 bugfix on every released Tor.
8983 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
8984 exit node as a NOROUTE error, not an INTERNAL error, since they
8985 can apparently happen when trying to connect to the wrong sort
8986 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
8987 - Fix build warnings about missing "a2x" comment when building the
8988 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
8989 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
8990 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
8991 not entirely remove it from the connection lists. Fixes bug 9602;
8992 bugfix on 0.2.4.4-alpha.
8993 - Fix a segmentation fault in our benchmark code when running with
8994 Fedora's OpenSSL package, or any other OpenSSL that provides
8995 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
8996 - Turn "circuit handshake stats since last time" log messages into a
8997 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
8999 o Documentation fixes:
9000 - Document that all but one DirPort entry must have the NoAdvertise
9001 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9004 Changes in version 0.2.5.2-alpha - 2014-02-13
9005 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
9006 like the "poor random number generation" fix and the "building too many
9007 circuits" fix. It also further improves security against potential
9008 adversaries who find breaking 1024-bit crypto doable, and launches
9009 pluggable transports on demand (which gets us closer to integrating
9010 pluggable transport support by default -- not to be confused with Tor
9011 bundles enabling pluggable transports and bridges by default).
9013 o Major features (client security):
9014 - When we choose a path for a 3-hop circuit, make sure it contains
9015 at least one relay that supports the NTor circuit extension
9016 handshake. Otherwise, there is a chance that we're building
9017 a circuit that's worth attacking by an adversary who finds
9018 breaking 1024-bit crypto doable, and that chance changes the game
9019 theory. Implements ticket 9777.
9020 - Clients now look at the "usecreatefast" consensus parameter to
9021 decide whether to use CREATE_FAST or CREATE cells for the first hop
9022 of their circuit. This approach can improve security on connections
9023 where Tor's circuit handshake is stronger than the available TLS
9024 connection security levels, but the tradeoff is more computational
9025 load on guard relays. Implements proposal 221. Resolves ticket 9386.
9027 o Major features (bridges):
9028 - Don't launch pluggable transport proxies if we don't have any
9029 bridges configured that would use them. Now we can list many
9030 pluggable transports, and Tor will dynamically start one when it
9031 hears a bridge address that needs it. Resolves ticket 5018.
9032 - The bridge directory authority now assigns status flags (Stable,
9033 Guard, etc) to bridges based on thresholds calculated over all
9034 Running bridges. Now bridgedb can finally make use of its features
9035 to e.g. include at least one Stable bridge in its answers. Fixes
9038 o Major features (other):
9039 - Extend ORCONN controller event to include an "ID" parameter,
9040 and add four new controller event types CONN_BW, CIRC_BW,
9041 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
9042 The new events are emitted in private Tor networks only, with the
9043 goal of being able to better track performance and load during
9044 full-network simulations. Implements proposal 218 and ticket 7359.
9045 - On some platforms (currently: recent OSX versions, glibc-based
9046 platforms that support the ELF format, and a few other
9047 Unix-like operating systems), Tor can now dump stack traces
9048 when a crash occurs or an assertion fails. By default, traces
9049 are dumped to stderr (if possible) and to any logs that are
9050 reporting errors. Implements ticket 9299.
9053 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
9054 not entirely remove it from the connection lists. Fixes bug 9602;
9055 bugfix on 0.2.4.4-alpha.
9056 - Do not treat streams that fail with reason
9057 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
9058 since it could also indicate an ENETUNREACH connection error. Fixes
9059 part of bug 10777; bugfix on 0.2.4.8-alpha.
9061 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
9062 - Do not allow OpenSSL engines to replace the PRNG, even when
9063 HardwareAccel is set. The only default builtin PRNG engine uses
9064 the Intel RDRAND instruction to replace the entire PRNG, and
9065 ignores all attempts to seed it with more entropy. That's
9066 cryptographically stupid: the right response to a new alleged
9067 entropy source is never to discard all previously used entropy
9068 sources. Fixes bug 10402; works around behavior introduced in
9069 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9071 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9072 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9073 - Avoid launching spurious extra circuits when a stream is pending.
9074 This fixes a bug where any circuit that _wasn't_ unusable for new
9075 streams would be treated as if it were, causing extra circuits to
9076 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9078 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9079 - No longer stop reading or writing on cpuworker connections when
9080 our rate limiting buckets go empty. Now we should handle circuit
9081 handshake requests more promptly. Resolves bug 9731.
9082 - Stop trying to bootstrap all our directory information from
9083 only our first guard. Discovered while fixing bug 9946; bugfix
9086 o Minor features (bridges, pluggable transports):
9087 - Add threshold cutoffs to the networkstatus document created by
9088 the Bridge Authority. Fixes bug 1117.
9089 - On Windows, spawn background processes using the CREATE_NO_WINDOW
9090 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
9091 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
9092 Vidalia set this option for us.) Implements ticket 10297.
9094 o Minor features (security):
9095 - Always clear OpenSSL bignums before freeing them -- even bignums
9096 that don't contain secrets. Resolves ticket 10793. Patch by
9099 o Minor features (config options and command line):
9100 - Add an --allow-missing-torrc commandline option that tells Tor to
9101 run even if the configuration file specified by -f is not available.
9102 Implements ticket 10060.
9103 - Add support for the TPROXY transparent proxying facility on Linux.
9104 See documentation for the new TransProxyType option for more
9105 details. Implementation by "thomo". Closes ticket 10582.
9107 o Minor features (controller):
9108 - Add a new "HS_DESC" controller event that reports activities
9109 related to hidden service descriptors. Resolves ticket 8510.
9110 - New "DROPGUARDS" controller command to forget all current entry
9111 guards. Not recommended for ordinary use, since replacing guards
9112 too frequently makes several attacks easier. Resolves ticket 9934;
9115 o Minor features (build):
9116 - Assume that a user using ./configure --host wants to cross-compile,
9117 and give an error if we cannot find a properly named
9118 tool-chain. Add a --disable-tool-name-check option to proceed
9119 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
9120 - If we run ./configure and the compiler recognizes -fstack-protector
9121 but the linker rejects it, warn the user about a potentially missing
9122 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
9124 o Minor features (testing):
9125 - If Python is installed, "make check" now runs extra tests beyond
9126 the unit test scripts.
9127 - When bootstrapping a test network, sometimes very few relays get
9128 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
9129 specify a set of relays which should be voted Guard regardless of
9130 their uptime or bandwidth. Addresses ticket 9206.
9132 o Minor features (log messages):
9133 - When ServerTransportPlugin is set on a bridge, Tor can write more
9134 useful statistics about bridge use in its extrainfo descriptors,
9135 but only if the Extended ORPort ("ExtORPort") is set too. Add a
9136 log message to inform the user in this case. Resolves ticket 9651.
9137 - When receiving a new controller connection, log the origin address.
9138 Resolves ticket 9698; patch from "sigpipe".
9139 - When logging OpenSSL engine status at startup, log the status of
9140 more engines. Fixes ticket 10043; patch from Joshua Datko.
9141 - Turn "circuit handshake stats since last time" log messages into a
9142 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
9144 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9145 - Improve the circuit queue out-of-memory handler. Previously, when
9146 we ran low on memory, we'd close whichever circuits had the most
9147 queued cells. Now, we close those that have the *oldest* queued
9148 cells, on the theory that those are most responsible for us
9149 running low on memory. Based on analysis from a forthcoming paper
9150 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
9151 - Generate bootstrapping status update events correctly when fetching
9152 microdescriptors. Fixes bug 9927.
9153 - Update to the October 2 2013 Maxmind GeoLite Country database.
9155 o Minor bugfixes (clients):
9156 - When closing a channel that has already been open, do not close
9157 pending circuits that were waiting to connect to the same relay.
9158 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
9161 o Minor bugfixes (relays):
9162 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
9163 exit node as a NOROUTE error, not an INTERNAL error, since they
9164 can apparently happen when trying to connect to the wrong sort
9165 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
9167 o Minor bugfixes (bridges):
9168 - Fix a bug where the first connection works to a bridge that uses a
9169 pluggable transport with client-side parameters, but we don't send
9170 the client-side parameters on subsequent connections. (We don't
9171 use any pluggable transports with client-side parameters yet,
9172 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
9173 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
9175 o Minor bugfixes (node selection):
9176 - If ExcludeNodes is set, consider non-excluded hidden service
9177 directory servers before excluded ones. Do not consider excluded
9178 hidden service directory servers at all if StrictNodes is
9179 set. (Previously, we would sometimes decide to connect to those
9180 servers, and then realize before we initiated a connection that
9181 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
9183 - If we set the ExitNodes option but it doesn't include any nodes
9184 that have the Exit flag, we would choose not to bootstrap. Now we
9185 bootstrap so long as ExitNodes includes nodes which can exit to
9186 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
9188 o Minor bugfixes (controller and command-line):
9189 - If changing a config option via "setconf" fails in a recoverable
9190 way, we used to nonetheless write our new control ports to the
9191 file described by the "ControlPortWriteToFile" option. Now we only
9192 write out that file if we successfully switch to the new config
9193 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
9194 - When a command-line option such as --version or --help that
9195 ordinarily implies --hush appears on the command line along with
9196 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
9197 only if it appeared later on the command line. Fixes bug 9578;
9198 bugfix on 0.2.5.1-alpha.
9200 o Minor bugfixes (code correctness):
9201 - Previously we used two temporary files when writing descriptors to
9202 disk; now we only use one. Fixes bug 1376.
9203 - Remove an erroneous (but impossible and thus harmless) pointer
9204 comparison that would have allowed compilers to skip a bounds
9205 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
9206 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
9207 - Fix an always-true assertion in pluggable transports code so it
9208 actually checks what it was trying to check. Fixes bug 10046;
9209 bugfix on 0.2.3.9-alpha. Found by "dcb".
9211 o Minor bugfixes (protocol correctness):
9212 - When receiving a VERSIONS cell with an odd number of bytes, close
9213 the connection immediately since the cell is malformed. Fixes bug
9214 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
9217 o Minor bugfixes (build):
9218 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
9219 turned off (that is, without support for v2 link handshakes). Fixes
9220 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
9221 - Fix compilation warnings and startup issues when running with
9222 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
9224 - Fix compilation on Solaris 9, which didn't like us having an
9225 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
9227 o Minor bugfixes (testing):
9228 - Fix a segmentation fault in our benchmark code when running with
9229 Fedora's OpenSSL package, or any other OpenSSL that provides
9230 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
9232 o Minor bugfixes (log messages):
9233 - Fix a bug where clients using bridges would report themselves
9234 as 50% bootstrapped even without a live consensus document.
9235 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
9236 - Suppress a warning where, if there's only one directory authority
9237 in the network, we would complain that votes and signatures cannot
9238 be uploaded to other directory authorities. Fixes bug 10842;
9239 bugfix on 0.2.2.26-beta.
9240 - Report bootstrapping progress correctly when we're downloading
9241 microdescriptors. We had updated our "do we have enough microdescs
9242 to begin building circuits?" logic most recently in 0.2.4.10-alpha
9243 (see bug 5956), but we left the bootstrap status event logic at
9244 "how far through getting 1/4 of them are we?" Fixes bug 9958;
9245 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
9247 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
9248 - Avoid a crash bug when starting with a corrupted microdescriptor
9249 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9250 - If we fail to dump a previously cached microdescriptor to disk, avoid
9251 freeing duplicate data later on. Fixes bug 10423; bugfix on
9252 0.2.4.13-alpha. Spotted by "bobnomnom".
9254 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9255 - Correctly log long IPv6 exit policies, instead of truncating them
9256 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
9257 - Our default TLS ecdhe groups were backwards: we meant to be using
9258 P224 for relays (for performance win) and P256 for bridges (since
9259 it is more common in the wild). Instead we had it backwards. After
9260 reconsideration, we decided that the default should be P256 on all
9261 hosts, since its security is probably better, and since P224 is
9262 reportedly used quite little in the wild. Found by "skruffy" on
9263 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
9264 - Free directory authority certificate download statuses on exit
9265 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
9267 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9268 - If the guard we choose first doesn't answer, we would try the
9269 second guard, but once we connected to the second guard we would
9270 abandon it and retry the first one, slowing down bootstrapping.
9271 The fix is to treat all our initially chosen guards as acceptable
9272 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
9273 - Fix an assertion failure that would occur when disabling the
9274 ORPort setting on a running Tor process while accounting was
9275 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
9276 - When examining the list of network interfaces to find our address,
9277 do not consider non-running or disabled network interfaces. Fixes
9278 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
9279 - Avoid an off-by-one error when checking buffer boundaries when
9280 formatting the exit status of a pluggable transport helper.
9281 This is probably not an exploitable bug, but better safe than
9282 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
9285 o Removed code and features:
9286 - Clients now reject any directory authority certificates lacking
9287 a dir-key-crosscert element. These have been included since
9288 0.2.1.9-alpha, so there's no real reason for them to be optional
9289 any longer. Completes proposal 157. Resolves ticket 10162.
9290 - Remove all code that existed to support the v2 directory system,
9291 since there are no longer any v2 directory authorities. Resolves
9293 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
9294 options, which were used for designating authorities as "Hidden
9295 service authorities". There has been no use of hidden service
9296 authorities since 0.2.2.1-alpha, when we stopped uploading or
9297 downloading v0 hidden service descriptors. Fixes bug 10881; also
9298 part of a fix for bug 10841.
9300 o Code simplification and refactoring:
9301 - Remove some old fallback code designed to keep Tor clients working
9302 in a network with only two working relays. Elsewhere in the code we
9303 have long since stopped supporting such networks, so there wasn't
9304 much point in keeping it around. Addresses ticket 9926.
9305 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
9306 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
9307 - Remove data structures which were introduced to implement the
9308 CellStatistics option: they are now redundant with the addition
9309 of a timestamp to the regular packed_cell_t data structure, which
9310 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
9313 o Documentation (man page) fixes:
9314 - Update manpage to describe some of the files you can expect to
9315 find in Tor's DataDirectory. Addresses ticket 9839.
9316 - Document that all but one DirPort entry must have the NoAdvertise
9317 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
9319 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
9320 - Clarify the usage and risks of setting the ContactInfo torrc line
9321 for your relay or bridge. Resolves ticket 9854.
9322 - Add anchors to the manpage so we can link to the html version of
9323 the documentation for specific options. Resolves ticket 9866.
9324 - Replace remaining references to DirServer in man page and
9325 log entries. Resolves ticket 10124.
9328 - Make the "tor-gencert" tool used by directory authority operators
9329 create 2048-bit signing keys by default (rather than 1024-bit, since
9330 1024-bit is uncomfortably small these days). Addresses ticket 10324.
9333 Changes in version 0.2.4.20 - 2013-12-22
9334 Tor 0.2.4.20 fixes potentially poor random number generation for users
9335 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
9336 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
9337 and 4) have no state file in their DataDirectory (as would happen on
9338 first start). Users who generated relay or hidden service identity
9339 keys in such a situation should discard them and generate new ones.
9341 This release also fixes a logic error that caused Tor clients to build
9342 many more preemptive circuits than they actually need.
9345 - Do not allow OpenSSL engines to replace the PRNG, even when
9346 HardwareAccel is set. The only default builtin PRNG engine uses
9347 the Intel RDRAND instruction to replace the entire PRNG, and
9348 ignores all attempts to seed it with more entropy. That's
9349 cryptographically stupid: the right response to a new alleged
9350 entropy source is never to discard all previously used entropy
9351 sources. Fixes bug 10402; works around behavior introduced in
9352 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
9354 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
9355 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
9356 - Avoid launching spurious extra circuits when a stream is pending.
9357 This fixes a bug where any circuit that _wasn't_ unusable for new
9358 streams would be treated as if it were, causing extra circuits to
9359 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
9362 - Avoid a crash bug when starting with a corrupted microdescriptor
9363 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
9364 - If we fail to dump a previously cached microdescriptor to disk, avoid
9365 freeing duplicate data later on. Fixes bug 10423; bugfix on
9366 0.2.4.13-alpha. Spotted by "bobnomnom".
9369 Changes in version 0.2.4.19 - 2013-12-11
9370 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
9371 (1986-2013). Aaron worked on diverse projects including helping to guide
9372 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
9373 transparency to the U.S government's PACER documents, and contributing
9374 design and development for Tor and Tor2Web. Aaron was one of the latest
9375 martyrs in our collective fight for civil liberties and human rights,
9376 and his death is all the more painful because he was one of us.
9378 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
9379 a new circuit handshake and link encryption that use ECC to provide
9380 better security and efficiency; makes relays better manage circuit
9381 creation requests; uses "directory guards" to reduce client enumeration
9382 risks; makes bridges collect and report statistics about the pluggable
9383 transports they support; cleans up and improves our geoip database;
9384 gets much closer to IPv6 support for clients, bridges, and relays; makes
9385 directory authorities use measured bandwidths rather than advertised
9386 ones when computing flags and thresholds; disables client-side DNS
9387 caching to reduce tracking risks; and fixes a big bug in bridge
9388 reachability testing. This release introduces two new design
9389 abstractions in the code: a new "channel" abstraction between circuits
9390 and or_connections to allow for implementing alternate relay-to-relay
9391 transports, and a new "circuitmux" abstraction storing the queue of
9392 circuits for a channel. The release also includes many stability,
9393 security, and privacy fixes.
9396 Changes in version 0.2.4.18-rc - 2013-11-16
9397 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
9398 series. It takes a variety of fixes from the 0.2.5.x branch to improve
9399 stability, performance, and better handling of edge cases.
9402 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
9403 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
9404 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
9405 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
9406 them to solve bug 6033.)
9409 - No longer stop reading or writing on cpuworker connections when
9410 our rate limiting buckets go empty. Now we should handle circuit
9411 handshake requests more promptly. Resolves bug 9731.
9412 - If we are unable to save a microdescriptor to the journal, do not
9413 drop it from memory and then reattempt downloading it. Fixes bug
9414 9645; bugfix on 0.2.2.6-alpha.
9415 - Stop trying to bootstrap all our directory information from
9416 only our first guard. Discovered while fixing bug 9946; bugfix
9418 - The new channel code sometimes lost track of in-progress circuits,
9419 causing long-running clients to stop building new circuits. The
9420 fix is to always call circuit_n_chan_done(chan, 0) from
9421 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
9423 o Minor bugfixes (on 0.2.4.x):
9424 - Correctly log long IPv6 exit policies, instead of truncating them
9425 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
9426 - Our default TLS ecdhe groups were backwards: we meant to be using
9427 P224 for relays (for performance win) and P256 for bridges (since
9428 it is more common in the wild). Instead we had it backwards. After
9429 reconsideration, we decided that the default should be P256 on all
9430 hosts, since its security is probably better, and since P224 is
9431 reportedly used quite little in the wild. Found by "skruffy" on
9432 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
9433 - Free directory authority certificate download statuses on exit
9434 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
9436 o Minor bugfixes (on 0.2.3.x and earlier):
9437 - If the guard we choose first doesn't answer, we would try the
9438 second guard, but once we connected to the second guard we would
9439 abandon it and retry the first one, slowing down bootstrapping.
9440 The fix is to treat all our initially chosen guards as acceptable
9441 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
9442 - Fix an assertion failure that would occur when disabling the
9443 ORPort setting on a running Tor process while accounting was
9444 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
9445 - When examining the list of network interfaces to find our address,
9446 do not consider non-running or disabled network interfaces. Fixes
9447 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
9448 - Avoid an off-by-one error when checking buffer boundaries when
9449 formatting the exit status of a pluggable transport helper.
9450 This is probably not an exploitable bug, but better safe than
9451 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
9454 o Minor features (protecting client timestamps):
9455 - Clients no longer send timestamps in their NETINFO cells. These were
9456 not used for anything, and they provided one small way for clients
9457 to be distinguished from each other as they moved from network to
9458 network or behind NAT. Implements part of proposal 222.
9459 - Clients now round timestamps in INTRODUCE cells down to the nearest
9460 10 minutes. If a new Support022HiddenServices option is set to 0, or
9461 if it's set to "auto" and the feature is disabled in the consensus,
9462 the timestamp is sent as 0 instead. Implements part of proposal 222.
9463 - Stop sending timestamps in AUTHENTICATE cells. This is not such
9464 a big deal from a security point of view, but it achieves no actual
9465 good purpose, and isn't needed. Implements part of proposal 222.
9466 - Reduce down accuracy of timestamps in hidden service descriptors.
9467 Implements part of proposal 222.
9469 o Minor features (other):
9470 - Improve the circuit queue out-of-memory handler. Previously, when
9471 we ran low on memory, we'd close whichever circuits had the most
9472 queued cells. Now, we close those that have the *oldest* queued
9473 cells, on the theory that those are most responsible for us
9474 running low on memory. Based on analysis from a forthcoming paper
9475 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
9476 - Generate bootstrapping status update events correctly when fetching
9477 microdescriptors. Fixes bug 9927.
9478 - Update to the October 2 2013 Maxmind GeoLite Country database.
9480 o Documentation fixes:
9481 - Clarify the usage and risks of setting the ContactInfo torrc line
9482 for your relay or bridge. Resolves ticket 9854.
9483 - Add anchors to the manpage so we can link to the html version of
9484 the documentation for specific options. Resolves ticket 9866.
9485 - Replace remaining references to DirServer in man page and
9486 log entries. Resolves ticket 10124.
9489 Changes in version 0.2.5.1-alpha - 2013-10-02
9490 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
9491 on Linux, allows bridges that offer pluggable transports to report usage
9492 statistics, fixes many issues to make testing easier, and provides
9493 a pile of minor features and bugfixes that have been waiting for a
9494 release of the new branch.
9496 This is the first alpha release in a new series, so expect there to
9497 be bugs. Users who would rather test out a more stable branch should
9498 stay with 0.2.4.x for now.
9500 o Major features (security):
9501 - Use the seccomp2 syscall filtering facility on Linux to limit
9502 which system calls Tor can invoke. This is an experimental,
9503 Linux-only feature to provide defense-in-depth against unknown
9504 attacks. To try turning it on, set "Sandbox 1" in your torrc
9505 file. Please be ready to report bugs. We hope to add support
9506 for better sandboxing in the future, including more fine-grained
9507 filters, better division of responsibility, and support for more
9508 platforms. This work has been done by Cristian-Matei Toader for
9509 Google Summer of Code.
9510 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
9511 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
9512 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
9513 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
9514 them to solve bug 6033.)
9516 o Major features (other):
9517 - Add support for passing arguments to managed pluggable transport
9518 proxies. Implements ticket 3594.
9519 - Bridges now track GeoIP information and the number of their users
9520 even when pluggable transports are in use, and report usage
9521 statistics in their extra-info descriptors. Resolves tickets 4773
9523 - Make testing Tor networks bootstrap better: lower directory fetch
9524 retry schedules and maximum interval without directory requests,
9525 and raise maximum download tries. Implements ticket 6752.
9526 - Add make target 'test-network' to run tests on a Chutney network.
9527 Implements ticket 8530.
9528 - The ntor handshake is now on-by-default, no matter what the
9529 directory authorities recommend. Implements ticket 8561.
9532 - Instead of writing destroy cells directly to outgoing connection
9533 buffers, queue them and intersperse them with other outgoing cells.
9534 This can prevent a set of resource starvation conditions where too
9535 many pending destroy cells prevent data cells from actually getting
9536 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
9537 bugfix on 0.2.0.1-alpha.
9538 - If we are unable to save a microdescriptor to the journal, do not
9539 drop it from memory and then reattempt downloading it. Fixes bug
9540 9645; bugfix on 0.2.2.6-alpha.
9541 - The new channel code sometimes lost track of in-progress circuits,
9542 causing long-running clients to stop building new circuits. The
9543 fix is to always call circuit_n_chan_done(chan, 0) from
9544 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
9547 - Tor now builds each source file in two modes: a mode that avoids
9548 exposing identifiers needlessly, and another mode that exposes
9549 more identifiers for testing. This lets the compiler do better at
9550 optimizing the production code, while enabling us to take more
9551 radical measures to let the unit tests test things.
9552 - The production builds no longer include functions used only in
9553 the unit tests; all functions exposed from a module only for
9554 unit-testing are now static in production builds.
9555 - Add an --enable-coverage configuration option to make the unit
9556 tests (and a new src/or/tor-cov target) to build with gcov test
9560 - We now have rudimentary function mocking support that our unit
9561 tests can use to test functions in isolation. Function mocking
9562 lets the tests temporarily replace a function's dependencies with
9563 stub functions, so that the tests can check the function without
9564 invoking the other functions it calls.
9565 - Add more unit tests for the <circid,channel>->circuit map, and
9566 the destroy-cell-tracking code to fix bug 7912.
9567 - Unit tests for failing cases of the TAP onion handshake.
9568 - More unit tests for address-manipulation functions.
9570 o Minor features (protecting client timestamps):
9571 - Clients no longer send timestamps in their NETINFO cells. These were
9572 not used for anything, and they provided one small way for clients
9573 to be distinguished from each other as they moved from network to
9574 network or behind NAT. Implements part of proposal 222.
9575 - Clients now round timestamps in INTRODUCE cells down to the nearest
9576 10 minutes. If a new Support022HiddenServices option is set to 0, or
9577 if it's set to "auto" and the feature is disabled in the consensus,
9578 the timestamp is sent as 0 instead. Implements part of proposal 222.
9579 - Stop sending timestamps in AUTHENTICATE cells. This is not such
9580 a big deal from a security point of view, but it achieves no actual
9581 good purpose, and isn't needed. Implements part of proposal 222.
9582 - Reduce down accuracy of timestamps in hidden service descriptors.
9583 Implements part of proposal 222.
9585 o Minor features (config options):
9586 - Config (torrc) lines now handle fingerprints which are missing
9587 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
9588 - Support a --dump-config option to print some or all of the
9589 configured options. Mainly useful for debugging the command-line
9590 option parsing code. Helps resolve ticket 4647.
9591 - Raise awareness of safer logging: notify user of potentially
9592 unsafe config options, like logging more verbosely than severity
9593 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
9594 - Add a new configuration option TestingV3AuthVotingStartOffset
9595 that bootstraps a network faster by changing the timing for
9596 consensus votes. Addresses ticket 8532.
9597 - Add a new torrc option "ServerTransportOptions" that allows
9598 bridge operators to pass configuration parameters to their
9599 pluggable transports. Resolves ticket 8929.
9600 - The config (torrc) file now accepts bandwidth and space limits in
9601 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
9602 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
9605 o Minor features (build):
9606 - Add support for `--library-versions` flag. Implements ticket 6384.
9607 - Return the "unexpected sendme" warnings to a warn severity, but make
9608 them rate limited, to help diagnose ticket 8093.
9609 - Detect a missing asciidoc, and warn the user about it, during
9610 configure rather than at build time. Fixes issue 6506. Patch from
9613 o Minor features (other):
9614 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
9615 sockets in a single system call. Implements ticket 5129.
9616 - Log current accounting state (bytes sent and received + remaining
9617 time for the current accounting period) in the relay's heartbeat
9618 message. Implements ticket 5526; patch from Peter Retzlaff.
9619 - Implement the TRANSPORT_LAUNCHED control port event that
9620 notifies controllers about new launched pluggable
9621 transports. Resolves ticket 5609.
9622 - If we're using the pure-C 32-bit curve25519_donna implementation
9623 of curve25519, build it with the -fomit-frame-pointer option to
9624 make it go faster on register-starved hosts. This improves our
9625 handshake performance by about 6% on i386 hosts without nacl.
9627 - Update to the September 4 2013 Maxmind GeoLite Country database.
9630 - Set the listen() backlog limit to the largest actually supported
9631 on the system, not to the value in a header file. Fixes bug 9716;
9632 bugfix on every released Tor.
9633 - No longer accept malformed http headers when parsing urls from
9634 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
9635 bugfix on 0.0.6pre1.
9636 - In munge_extrainfo_into_routerinfo(), check the return value of
9637 memchr(). This would have been a serious issue if we ever passed
9638 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
9640 - On the chance that somebody manages to build Tor on a
9641 platform where time_t is unsigned, correct the way that
9642 microdesc_add_to_cache() handles negative time arguments.
9643 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
9644 - Reject relative control socket paths and emit a warning. Previously,
9645 single-component control socket paths would be rejected, but Tor
9646 would not log why it could not validate the config. Fixes bug 9258;
9647 bugfix on 0.2.3.16-alpha.
9649 o Minor bugfixes (command line):
9650 - Use a single command-line parser for parsing torrc options on the
9651 command line and for finding special command-line options to avoid
9652 inconsistent behavior for torrc option arguments that have the same
9653 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
9655 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
9656 9573; bugfix on 0.0.9pre5.
9658 o Minor fixes (build, auxiliary programs):
9659 - Stop preprocessing the "torify" script with autoconf, since
9660 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
9662 - The tor-fw-helper program now follows the standard convention and
9663 exits with status code "0" on success. Fixes bug 9030; bugfix on
9664 0.2.3.1-alpha. Patch by Arlo Breault.
9665 - Corrected ./configure advice for what openssl dev package you should
9666 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
9668 o Minor code improvements:
9669 - Remove constants and tests for PKCS1 padding; it's insecure and
9670 shouldn't be used for anything new. Fixes bug 8792; patch
9672 - Remove instances of strcpy() from the unit tests. They weren't
9673 hurting anything, since they were only in the unit tests, but it's
9674 embarassing to have strcpy() in the code at all, and some analysis
9675 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
9676 0.2.3.8-alpha. Patch from Arlo Breault.
9679 - Remove migration code from when we renamed the "cached-routers"
9680 file to "cached-descriptors" back in 0.2.0.8-alpha. This
9681 incidentally resolves ticket 6502 by cleaning up the related code
9682 a bit. Patch from Akshay Hebbar.
9684 o Code simplification and refactoring:
9685 - Extract the common duplicated code for creating a subdirectory
9686 of the data directory and writing to a file in it. Fixes ticket
9687 4282; patch from Peter Retzlaff.
9688 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
9689 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
9690 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
9691 - Add a set of accessor functions for the circuit timeout data
9692 structure. Fixes ticket 6153; patch from "piet".
9693 - Clean up exit paths from connection_listener_new(). Closes ticket
9694 8789. Patch from Arlo Breault.
9695 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
9696 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
9697 - Use a doubly-linked list to implement the global circuit list.
9698 Resolves ticket 9108. Patch from Marek Majkowski.
9699 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
9702 Changes in version 0.2.4.17-rc - 2013-09-05
9703 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
9704 series. It adds an emergency step to help us tolerate the massive
9705 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
9706 circuit-level handshakes now effectively jump the queue compared to
9707 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
9708 big bug hindering bridge reachability tests.
9711 - Relays now process the new "NTor" circuit-level handshake requests
9712 with higher priority than the old "TAP" circuit-level handshake
9713 requests. We still process some TAP requests to not totally starve
9714 0.2.3 clients when NTor becomes popular. A new consensus parameter
9715 "NumNTorsPerTAP" lets us tune the balance later if we need to.
9716 Implements ticket 9574.
9719 - If the circuit build timeout logic is disabled (via the consensus,
9720 or because we are an authority), then don't build testing circuits.
9721 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
9722 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
9723 previously they did not, which prevented them from receiving
9724 successful connections from relays for self-test or bandwidth
9725 testing. Also, when a relay is extending a circuit to a bridge,
9726 it needs to send a NETINFO cell, even when the bridge hasn't sent
9727 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
9728 - If the time to download the next old-style networkstatus is in
9729 the future, do not decline to consider whether to download the
9730 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
9734 - Avoid double-closing the listener socket in our socketpair()
9735 replacement (used on Windows) in the case where the addresses on
9736 our opened sockets don't match what we expected. Fixes bug 9400;
9737 bugfix on 0.0.2pre7. Found by Coverity.
9739 o Minor fixes (config options):
9740 - Avoid overflows when the user sets MaxCircuitDirtiness to a
9741 ridiculously high value, by imposing a (ridiculously high) 30-day
9742 maximum on MaxCircuitDirtiness.
9743 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
9744 message is logged at notice, not at info.
9745 - Warn and fail if a server is configured not to advertise any
9746 ORPorts at all. (We need *something* to put in our descriptor,
9747 or we just won't work.)
9750 - Track how many "TAP" and "NTor" circuit handshake requests we get,
9751 and how many we complete, and log it every hour to help relay
9752 operators follow trends in network load. Addresses ticket 9658.
9753 - Update to the August 7 2013 Maxmind GeoLite Country database.
9756 Changes in version 0.2.4.16-rc - 2013-08-10
9757 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
9758 series. It fixes several crash bugs in the 0.2.4 branch.
9761 - Fix a bug in the voting algorithm that could yield incorrect results
9762 when a non-naming authority declared too many flags. Fixes bug 9200;
9763 bugfix on 0.2.0.3-alpha.
9764 - Fix an uninitialized read that could in some cases lead to a remote
9765 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
9766 Anybody running a hidden service on the experimental 0.2.4.x
9767 branch should upgrade. (This is, so far as we know, unrelated to
9769 - Avoid an assertion failure when processing DNS replies without the
9770 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
9771 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
9772 0.2.4.15-rc. Found by stem integration tests.
9775 - Fix an invalid memory read that occured when a pluggable
9776 transport proxy failed its configuration protocol.
9777 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
9778 - When evaluating whether to use a connection that we haven't
9779 decided is canonical using a recent link protocol version,
9780 decide that it's canonical only if it used address _does_
9781 match the desired address. Fixes bug 9309; bugfix on
9782 0.2.4.4-alpha. Reported by skruffy.
9783 - Make the default behavior of NumDirectoryGuards be to track
9784 NumEntryGuards. Now a user who changes only NumEntryGuards will get
9785 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
9786 - Fix a spurious compilation warning with some older versions of
9787 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
9790 - Update to the July 3 2013 Maxmind GeoLite Country database.
9793 Changes in version 0.2.4.15-rc - 2013-07-01
9794 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
9795 series. It fixes a few smaller bugs, but generally appears stable.
9796 Please test it and let us know whether it is!
9799 - When receiving a new configuration file via the control port's
9800 LOADCONF command, do not treat the defaults file as absent.
9801 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
9804 - Issue a warning when running with the bufferevents backend enabled.
9805 It's still not stable, and people should know that they're likely
9806 to hit unexpected problems. Closes ticket 9147.
9809 Changes in version 0.2.4.14-alpha - 2013-06-18
9810 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
9811 present in 0.2.4.13-alpha.
9814 - When we have too much memory queued in circuits (according to a new
9815 MaxMemInCellQueues option), close the circuits consuming the most
9816 memory. This prevents us from running out of memory as a relay if
9817 circuits fill up faster than they can be drained. Fixes bug 9063;
9818 bugfix on the 54th commit of Tor. This bug is a further fix beyond
9819 bug 6252, whose fix was merged into 0.2.3.21-rc.
9821 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
9822 where we tried to solve this issue simply by imposing an upper limit
9823 on the number of queued cells for a single circuit. That approach
9824 proved to be problematic, since there are ways to provoke clients to
9825 send a number of cells in excess of any such reasonable limit. Fixes
9826 bug 9072; bugfix on 0.2.4.13-alpha.
9828 - Limit hidden service descriptors to at most ten introduction
9829 points, to slow one kind of guard enumeration. Fixes bug 9002;
9830 bugfix on 0.1.1.11-alpha.
9833 Changes in version 0.2.4.13-alpha - 2013-06-14
9834 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
9835 vulnerabilities, makes socks5 username/password circuit isolation
9836 actually actually work (this time for sure!), and cleans up a bunch
9837 of other issues in preparation for a release candidate.
9839 o Major bugfixes (robustness):
9840 - Close any circuit that has too many cells queued on it. Fixes
9841 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
9842 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
9843 - Prevent the get_freelists() function from running off the end of
9844 the list of freelists if it somehow gets an unrecognized
9845 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
9847 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
9848 when an exit connection with optimistic data succeeds immediately
9849 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
9851 - Fix a directory authority crash bug when building a consensus
9852 using an older consensus as its basis. Fixes bug 8833. Bugfix
9856 - Avoid a memory leak where we would leak a consensus body when we
9857 find that a consensus which we couldn't previously verify due to
9858 missing certificates is now verifiable. Fixes bug 8719; bugfix
9860 - We used to always request authority certificates by identity digest,
9861 meaning we'd get the newest one even when we wanted one with a
9862 different signing key. Then we would complain about being given
9863 a certificate we already had, and never get the one we really
9864 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
9865 resource to request the one we want. Fixes bug 5595; bugfix on
9867 - Follow the socks5 protocol when offering username/password
9868 authentication. The fix for bug 8117 exposed this bug, and it
9869 turns out real-world applications like Pidgin do care. Bugfix on
9870 0.2.3.2-alpha; fixes bug 8879.
9871 - Prevent failures on Windows Vista and later when rebuilding the
9872 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
9873 bugfix on 0.2.4.12-alpha.
9876 - Fix an impossible buffer overrun in the AES unit tests. Fixes
9877 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
9878 - If for some reason we fail to write a microdescriptor while
9879 rebuilding the cache, do not let the annotations from that
9880 microdescriptor linger in the cache file, and do not let the
9881 microdescriptor stay recorded as present in its old location.
9882 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
9883 - Fix a memory leak that would occur whenever a configuration
9884 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
9885 - Paste the description for PathBias parameters from the man
9886 page into or.h, so the code documents them too. Fixes bug 7982;
9887 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
9888 - Relays now treat a changed IPv6 ORPort as sufficient reason to
9889 publish an updated descriptor. Fixes bug 6026; bugfix on
9891 - When launching a resolve request on behalf of an AF_UNIX control
9892 socket, omit the address field of the new entry connection, used in
9893 subsequent controller events, rather than letting tor_dup_addr()
9894 set it to "<unknown address type>". Fixes bug 8639; bugfix on
9897 o Minor bugfixes (log messages):
9898 - Fix a scaling issue in the path bias accounting code that
9899 resulted in "Bug:" log messages from either
9900 pathbias_scale_close_rates() or pathbias_count_build_success().
9901 This represents a bugfix on a previous bugfix: the original fix
9902 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
9904 - Give a less useless error message when the user asks for an IPv4
9905 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
9909 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
9910 to tolerate bug 8093 for now.
9911 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
9912 in directory authority votes to describe whether they have enough
9913 measured bandwidths to ignore advertised (relay descriptor)
9914 bandwidth claims. Resolves ticket 8711.
9915 - Update to the June 5 2013 Maxmind GeoLite Country database.
9917 o Removed documentation:
9918 - Remove some of the older contents of doc/ as obsolete; move others
9919 to torspec.git. Fixes bug 8965.
9921 o Code simplification and refactoring:
9922 - Avoid using character buffers when constructing most directory
9923 objects: this approach was unwieldy and error-prone. Instead,
9924 build smartlists of strings, and concatenate them when done.
9927 Changes in version 0.2.4.12-alpha - 2013-04-18
9928 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
9929 process for lengthening the guard rotation period, makes directory
9930 authority opinions in the consensus a bit less gameable, makes socks5
9931 username/password circuit isolation actually work, and fixes a wide
9932 variety of other issues.
9935 - Raise the default time that a client keeps an entry guard from
9936 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
9937 2012 paper. (We would make it even longer, but we need better client
9938 load balancing first.) Also, make the guard lifetime controllable
9939 via a new GuardLifetime torrc option and a GuardLifetime consensus
9940 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
9941 - Directory authorities now prefer using measured bandwidths to
9942 advertised ones when computing flags and thresholds. Resolves
9944 - Directory authorities that have more than a threshold number
9945 of relays with measured bandwidths now treat relays with unmeasured
9946 bandwidths as having bandwidth 0. Resolves ticket 8435.
9948 o Major bugfixes (assert / resource use):
9949 - Avoid a bug where our response to TLS renegotiation under certain
9950 network conditions could lead to a busy-loop, with 100% CPU
9951 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
9952 - Avoid an assertion when we discover that we'd like to write a cell
9953 onto a closing connection: just discard the cell. Fixes another
9954 case of bug 7350; bugfix on 0.2.4.4-alpha.
9956 o Major bugfixes (client-side privacy):
9957 - When we mark a circuit as unusable for new circuits, have it
9958 continue to be unusable for new circuits even if MaxCircuitDirtiness
9959 is increased too much at the wrong time, or the system clock jumps
9960 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
9961 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
9962 which have resolved to internal addresses") is set, apply that
9963 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
9964 - When an exit relay rejects a stream with reason "exit policy", but
9965 we only know an exit policy summary (e.g. from the microdesc
9966 consensus) for it, do not mark the relay as useless for all exiting.
9967 Instead, mark just the circuit as unsuitable for that particular
9968 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
9969 - Allow applications to get proper stream isolation with
9970 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
9971 username/password authentication also offer "no authentication". Tor
9972 had previously preferred "no authentication", so the applications
9973 never actually sent Tor their auth details. Now Tor selects
9974 username/password authentication if it's offered. You can disable
9975 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
9976 bug 8117; bugfix on 0.2.3.3-alpha.
9978 o Major bugfixes (other):
9979 - When unable to find any working directory nodes to use as a
9980 directory guard, give up rather than adding the same non-working
9981 nodes to the directory guard list over and over. Fixes bug 8231;
9982 bugfix on 0.2.4.8-alpha.
9985 - Reject as invalid most directory objects containing a NUL.
9986 Belt-and-suspender fix for bug 8037.
9987 - In our testsuite, create temporary directories with a bit more
9988 entropy in their name to make name collisions less likely. Fixes
9990 - Add CACHED keyword to ADDRMAP events in the control protocol
9991 to indicate whether a DNS result will be cached or not. Resolves
9993 - Update to the April 3 2013 Maxmind GeoLite Country database.
9995 o Minor features (build):
9996 - Detect and reject attempts to build Tor with threading support
9997 when OpenSSL has been compiled without threading support.
9999 - Clarify that when autoconf is checking for nacl, it is checking
10000 specifically for nacl with a fast curve25519 implementation.
10002 - Warn if building on a platform with an unsigned time_t: there
10003 are too many places where Tor currently assumes that time_t can
10004 hold negative values. We'd like to fix them all, but probably
10007 o Minor bugfixes (build):
10008 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
10009 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
10010 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
10011 - Add the old src/or/micro-revision.i filename to CLEANFILES.
10012 On the off chance that somebody has one, it will go away as soon
10013 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
10014 - Build Tor correctly on 32-bit platforms where the compiler can build
10015 but not run code using the "uint128_t" construction. Fixes bug 8587;
10016 bugfix on 0.2.4.8-alpha.
10017 - Fix compilation warning with some versions of clang that would
10018 prefer the -Wswitch-enum compiler flag to warn about switch
10019 statements with missing enum values, even if those switch
10020 statements have a "default:" statement. Fixes bug 8598; bugfix
10023 o Minor bugfixes (protocol):
10024 - Fix the handling of a TRUNCATE cell when it arrives while the
10025 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
10026 - Fix a misframing issue when reading the version numbers in a
10027 VERSIONS cell. Previously we would recognize [00 01 00 02] as
10028 'version 1, version 2, and version 0x100', when it should have
10029 only included versions 1 and 2. Fixes bug 8059; bugfix on
10030 0.2.0.10-alpha. Reported pseudonymously.
10031 - Make the format and order of STREAM events for DNS lookups
10032 consistent among the various ways to launch DNS lookups. Fixes
10033 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
10034 - Correct our check for which versions of Tor support the EXTEND2
10035 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
10036 later, when support was really added in version 0.2.4.8-alpha.
10037 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
10039 o Minor bugfixes (other):
10040 - Correctly store microdescriptors and extrainfo descriptors with
10041 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
10042 Bug reported by "cypherpunks".
10043 - Increase the width of the field used to remember a connection's
10044 link protocol version to two bytes. Harmless for now, since the
10045 only currently recognized versions are one byte long. Reported
10046 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
10047 - If the state file's path bias counts are invalid (presumably from a
10048 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
10049 additional checks and log messages to the scaling of Path Bias
10050 counts, in case there still are remaining issues with scaling.
10051 Should help resolve bug 8235.
10052 - Eliminate several instances where we use "Nickname=ID" to refer to
10053 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
10054 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
10055 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
10057 o Minor bugfixes (syscalls):
10058 - Always check the return values of functions fcntl() and
10059 setsockopt(). We don't believe these are ever actually failing in
10060 practice, but better safe than sorry. Also, checking these return
10061 values should please analysis tools like Coverity. Patch from
10062 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
10063 - Use direct writes rather than stdio when building microdescriptor
10064 caches, in an attempt to mitigate bug 8031, or at least make it
10067 o Minor bugfixes (config):
10068 - When rejecting a configuration because we were unable to parse a
10069 quoted string, log an actual error message. Fixes bug 7950; bugfix
10071 - Behave correctly when the user disables LearnCircuitBuildTimeout
10072 but doesn't tell us what they would like the timeout to be. Fixes
10073 bug 6304; bugfix on 0.2.2.14-alpha.
10074 - When autodetecting the number of CPUs, use the number of available
10075 CPUs in preference to the number of configured CPUs. Inform the
10076 user if this reduces the number of available CPUs. Fixes bug 8002;
10077 bugfix on 0.2.3.1-alpha.
10078 - Make it an error when you set EntryNodes but disable UseGuardNodes,
10079 since it will (surprisingly to some users) ignore EntryNodes. Fixes
10080 bug 8180; bugfix on 0.2.3.11-alpha.
10081 - Allow TestingTorNetworks to override the 4096-byte minimum for
10082 the Fast threshold. Otherwise they can't bootstrap until they've
10083 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
10084 - Fix some logic errors when the user manually overrides the
10085 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
10088 o Minor bugfixes (log messages to help diagnose bugs):
10089 - If we fail to free a microdescriptor because of bug 7164, log
10090 the filename and line number from which we tried to free it.
10091 - Add another diagnostic to the heartbeat message: track and log
10092 overhead that TLS is adding to the data we write. If this is
10093 high, we are sending too little data to SSL_write at a time.
10094 Diagnostic for bug 7707.
10095 - Add more detail to a log message about relaxed timeouts, to help
10097 - Warn more aggressively when flushing microdescriptors to a
10098 microdescriptor cache fails, in an attempt to mitigate bug 8031,
10099 or at least make it more diagnosable.
10100 - Improve debugging output to help track down bug 8185 ("Bug:
10101 outgoing relay cell has n_chan==NULL. Dropping.")
10102 - Log the purpose of a path-bias testing circuit correctly.
10103 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
10105 o Minor bugfixes (0.2.4.x log messages that were too noisy):
10106 - Don't attempt to relax the timeout of already opened 1-hop circuits.
10107 They might never timeout. This should eliminate some/all cases of
10108 the relaxed timeout log message.
10109 - Use circuit creation time for network liveness evaluation. This
10110 should eliminate warning log messages about liveness caused
10111 by changes in timeout evaluation. Fixes bug 6572; bugfix on
10113 - Reduce a path bias length check from notice to info. The message
10114 is triggered when creating controller circuits. Fixes bug 8196;
10115 bugfix on 0.2.4.8-alpha.
10116 - Fix a path state issue that triggered a notice during relay startup.
10117 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
10118 - Reduce occurrences of warns about circuit purpose in
10119 connection_ap_expire_building(). Fixes bug 8477; bugfix on
10122 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
10123 - If we encounter a write failure on a SOCKS connection before we
10124 finish our SOCKS handshake, don't warn that we closed the
10125 connection before we could send a SOCKS reply. Fixes bug 8427;
10126 bugfix on 0.1.0.1-rc.
10127 - Correctly recognize that [::1] is a loopback address. Fixes
10128 bug 8377; bugfix on 0.2.1.3-alpha.
10129 - Fix a directory authority warn caused when we have a large amount
10130 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
10131 - Don't log inappropriate heartbeat messages when hibernating: a
10132 hibernating node is _expected_ to drop out of the consensus,
10133 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
10134 bugfix on 0.2.3.1-alpha.
10135 - Don't complain about bootstrapping problems while hibernating.
10136 These complaints reflect a general code problem, but not one
10137 with any problematic effects (no connections are actually
10138 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
10140 o Documentation fixes:
10141 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
10142 names match. Fixes bug 7768.
10143 - Make the torify manpage no longer refer to tsocks; torify hasn't
10144 supported tsocks since 0.2.3.14-alpha.
10145 - Make the tor manpage no longer reference tsocks.
10146 - Fix the GeoIPExcludeUnknown documentation to refer to
10147 ExcludeExitNodes rather than the currently nonexistent
10148 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
10151 - The tor-tsocks.conf is no longer distributed or installed. We
10152 recommend that tsocks users use torsocks instead. Resolves
10156 Changes in version 0.2.4.11-alpha - 2013-03-11
10157 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
10158 more robust, makes hidden service authentication work again, and
10159 resolves a DPI fingerprint for Tor's SSL transport.
10161 o Major features (directory authorities):
10162 - Directory authorities now support a new consensus method (17)
10163 where they cap the published bandwidth of servers for which
10164 insufficient bandwidth measurements exist. Fixes part of bug 2286.
10165 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
10166 serve any v2 directory information. Now we can test disabling the
10167 old deprecated v2 directory format, and see whether doing so has
10168 any effect on network load. Begins to fix bug 6783.
10169 - Directory authorities now include inside each vote a statement of
10170 the performance thresholds they used when assigning flags.
10171 Implements ticket 8151.
10173 o Major bugfixes (directory authorities):
10174 - Stop marking every relay as having been down for one hour every
10175 time we restart a directory authority. These artificial downtimes
10176 were messing with our Stable and Guard flag calculations. Fixes
10177 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
10179 o Major bugfixes (hidden services):
10180 - Allow hidden service authentication to succeed again. When we
10181 refactored the hidden service introduction code back
10182 in 0.2.4.1-alpha, we didn't update the code that checks
10183 whether authentication information is present, causing all
10184 authentication checks to return "false". Fix for bug 8207; bugfix
10185 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
10187 o Minor features (relays, bridges):
10188 - Make bridge relays check once a minute for whether their IP
10189 address has changed, rather than only every 15 minutes. Resolves
10190 bugs 1913 and 1992.
10191 - Refactor resolve_my_address() so it returns the method by which we
10192 decided our public IP address (explicitly configured, resolved from
10193 explicit hostname, guessed from interfaces, learned by gethostname).
10194 Now we can provide more helpful log messages when a relay guesses
10195 its IP address incorrectly (e.g. due to unexpected lines in
10196 /etc/hosts). Resolves ticket 2267.
10197 - Teach bridge-using clients to avoid 0.2.2 bridges when making
10198 microdescriptor-related dir requests, and only fall back to normal
10199 descriptors if none of their bridges can handle microdescriptors
10200 (as opposed to the fix in ticket 4013, which caused them to fall
10201 back to normal descriptors if *any* of their bridges preferred
10202 them). Resolves ticket 4994.
10203 - Randomize the lifetime of our SSL link certificate, so censors can't
10204 use the static value for filtering Tor flows. Resolves ticket 8443;
10205 related to ticket 4014 which was included in 0.2.2.33.
10206 - Support a new version of the link protocol that allows 4-byte circuit
10207 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
10208 a possible resource exhaustion issue. Closes ticket 7351; implements
10211 o Minor features (portability):
10212 - Tweak the curve25519-donna*.c implementations to tolerate systems
10213 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
10214 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
10215 the signs of types during autoconf. This is better than our old
10216 approach, which didn't work when cross-compiling.
10217 - Detect the sign of enum values, rather than assuming that MSC is the
10218 only compiler where enum types are all signed. Fixes bug 7727;
10219 bugfix on 0.2.4.10-alpha.
10221 o Minor features (other):
10222 - Say "KBytes" rather than "KB" in the man page (for various values
10223 of K), to further reduce confusion about whether Tor counts in
10224 units of memory or fractions of units of memory. Resolves ticket 7054.
10225 - Clear the high bit on curve25519 public keys before passing them to
10226 our backend, in case we ever wind up using a backend that doesn't do
10227 so itself. If we used such a backend, and *didn't* clear the high bit,
10228 we could wind up in a situation where users with such backends would
10229 be distinguishable from users without. Fixes bug 8121; bugfix on
10231 - Update to the March 6 2013 Maxmind GeoLite Country database.
10233 o Minor bugfixes (clients):
10234 - When we receive a RELAY_END cell with the reason DONE, or with no
10235 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
10236 status as "connection refused". Previously we reported these cases
10237 as success but then immediately closed the connection. Fixes bug
10238 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
10239 - Downgrade an assertion in connection_ap_expire_beginning to an
10240 LD_BUG message. The fix for bug 8024 should prevent this message
10241 from displaying, but just in case, a warn that we can diagnose
10242 is better than more assert crashes. Fixes bug 8065; bugfix on
10244 - Lower path use bias thresholds to .80 for notice and .60 for warn.
10245 Also make the rate limiting flags for the path use bias log messages
10246 independent from the original path bias flags. Fixes bug 8161;
10247 bugfix on 0.2.4.10-alpha.
10249 o Minor bugfixes (relays):
10250 - Stop trying to resolve our hostname so often (e.g. every time we
10251 think about doing a directory fetch). Now we reuse the cached
10252 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
10253 and 2410 (bugfix on 0.1.2.2-alpha).
10254 - Stop sending a stray "(null)" in some cases for the server status
10255 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
10257 - When choosing which stream on a formerly stalled circuit to wake
10258 first, make better use of the platform's weak RNG. Previously,
10259 we had been using the % ("modulo") operator to try to generate a
10260 1/N chance of picking each stream, but this behaves badly with
10261 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
10263 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
10264 Irix's random() only return 15 bits; Solaris's random() returns more
10265 bits but its RAND_MAX says it only returns 15, and so on. Motivated
10266 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
10268 o Minor bugfixes (directory authorities):
10269 - Directory authorities now use less space when formatting identical
10270 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
10273 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
10274 - Avoid leaking memory if we fail to compute a consensus signature
10275 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
10276 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
10278 - Fix a memory leak during safe-cookie controller authentication.
10279 Bugfix on 0.2.3.13-alpha.
10280 - Avoid memory leak of IPv6 policy content if we fail to format it into
10281 a router descriptor. Bugfix on 0.2.4.7-alpha.
10283 o Minor bugfixes (other code correctness issues):
10284 - Avoid a crash if we fail to generate an extrainfo descriptor.
10285 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
10286 this is CID 718634.
10287 - When detecting the largest possible file descriptor (in order to
10288 close all file descriptors when launching a new program), actually
10289 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
10290 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
10292 - Fix a copy-and-paste error when adding a missing A1 to a routerset
10293 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
10294 Bugfix on 0.2.4.10-alpha.
10295 - Fix an impossible-to-trigger integer overflow when estimating how
10296 long our onionskin queue would take. (This overflow would require us
10297 to accept 4 million onionskins before processing 100 of them.) Fixes
10298 bug 8210; bugfix on 0.2.4.10-alpha.
10300 o Code simplification and refactoring:
10301 - Add a wrapper function for the common "log a message with a
10305 Changes in version 0.2.4.10-alpha - 2013-02-04
10306 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
10307 certain attacks that flood the network with relays; changes the queue
10308 for circuit create requests from a sized-based limit to a time-based
10309 limit; resumes building with MSVC on Windows; and fixes a wide variety
10312 o Major bugfixes (directory authority):
10313 - When computing directory thresholds, ignore any rejected-as-sybil
10314 nodes during the computation so that they can't influence Fast,
10315 Guard, etc. (We should have done this for proposal 109.) Fixes
10317 - When marking a node as a likely sybil, reset its uptime metrics
10318 to zero, so that it cannot time towards getting marked as Guard,
10319 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
10323 - When a TLS write is partially successful but incomplete, remember
10324 that the flushed part has been flushed, and notice that bytes were
10325 actually written. Reported and fixed pseudonymously. Fixes bug
10326 7708; bugfix on Tor 0.1.0.5-rc.
10327 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
10328 ID: these could be used to create unexpected streams and circuits
10329 which would count as "present" to some parts of Tor but "absent"
10330 to others, leading to zombie circuits and streams or to a bandwidth
10331 denial-of-service. Fixes bug 7889; bugfix on every released version
10332 of Tor. Reported by "oftc_must_be_destroyed".
10333 - Rename all macros in our local copy of queue.h to begin with "TOR_".
10334 This change seems the only good way to permanently prevent conflicts
10335 with queue.h on various operating systems. Fixes bug 8107; bugfix
10338 o Major features (relay):
10339 - Instead of limiting the number of queued onionskins (aka circuit
10340 create requests) to a fixed, hard-to-configure number, we limit
10341 the size of the queue based on how many we expect to be able to
10342 process in a given amount of time. We estimate the time it will
10343 take to process an onionskin based on average processing time
10344 of previous onionskins. Closes ticket 7291. You'll never have to
10345 configure MaxOnionsPending again.
10347 o Major features (portability):
10348 - Resume building correctly with MSVC and Makefile.nmake. This patch
10349 resolves numerous bugs and fixes reported by ultramage, including
10350 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
10351 - Make the ntor and curve25519 code build correctly with MSVC.
10352 Fix on 0.2.4.8-alpha.
10355 - When directory authorities are computing thresholds for flags,
10356 never let the threshold for the Fast flag fall below 4096
10357 bytes. Also, do not consider nodes with extremely low bandwidths
10358 when deciding thresholds for various directory flags. This change
10359 should raise our threshold for Fast relays, possibly in turn
10360 improving overall network performance; see ticket 1854. Resolves
10362 - The Tor client now ignores sub-domain components of a .onion
10363 address. This change makes HTTP "virtual" hosting
10364 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
10365 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
10366 hosted on the same hidden service. Implements proposal 204.
10367 - We compute the overhead from passing onionskins back and forth to
10368 cpuworkers, and report it when dumping statistics in response to
10369 SIGUSR1. Supports ticket 7291.
10371 o Minor features (path selection):
10372 - When deciding whether we have enough descriptors to build circuits,
10373 instead of looking at raw relay counts, look at which fraction
10374 of (bandwidth-weighted) paths we're able to build. This approach
10375 keeps clients from building circuits if their paths are likely to
10376 stand out statistically. The default fraction of paths needed is
10377 taken from the consensus directory; you can override it with the
10378 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
10379 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
10380 and we have GeoIP information, also exclude all nodes with unknown
10381 countries "??" and "A1". This behavior is controlled by the
10382 new GeoIPExcludeUnknown option: you can make such nodes always
10383 excluded with "GeoIPExcludeUnknown 1", and disable the feature
10384 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
10385 gets you the default behavior. Implements feature 7706.
10386 - Path Use Bias: Perform separate accounting for successful circuit
10387 use. Keep separate statistics on stream attempt rates versus stream
10388 success rates for each guard. Provide configurable thresholds to
10389 determine when to emit log messages or disable use of guards that
10390 fail too many stream attempts. Resolves ticket 7802.
10392 o Minor features (log messages):
10393 - When learning a fingerprint for a bridge, log its corresponding
10394 transport type. Implements ticket 7896.
10395 - Improve the log message when "Bug/attack: unexpected sendme cell
10396 from client" occurs, to help us track bug 8093.
10399 - Remove a couple of extraneous semicolons that were upsetting the
10400 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
10401 bugfix on 0.2.2.1-alpha.
10402 - Remove a source of rounding error during path bias count scaling;
10403 don't count cannibalized circuits as used for path bias until we
10404 actually try to use them; and fix a circuit_package_relay_cell()
10405 warning message about n_chan==NULL. Fixes bug 7802.
10406 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
10407 actually link against nacl when we're configured to use it. Fixes
10408 bug 7972; bugfix on 0.2.4.8-alpha.
10409 - Compile correctly with the --disable-curve25519 option. Fixes
10410 bug 8153; bugfix on 0.2.4.8-alpha.
10412 o Build improvements:
10413 - Do not report status verbosely from autogen.sh unless the -v flag
10414 is specified. Fixes issue 4664. Patch from Onizuka.
10415 - Replace all calls to snprintf() outside of src/ext with
10416 tor_snprintf(). Also remove the #define to replace snprintf with
10417 _snprintf on Windows; they have different semantics, and all of
10418 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
10419 - Try to detect if we are ever building on a platform where
10420 memset(...,0,...) does not set the value of a double to 0.0. Such
10421 platforms are permitted by the C standard, though in practice
10422 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
10423 currently support them, but it's better to detect them and fail
10424 than to perform erroneously.
10426 o Removed features:
10427 - Stop exporting estimates of v2 and v3 directory traffic shares
10428 in extrainfo documents. They were unneeded and sometimes inaccurate.
10429 Also stop exporting any v2 directory request statistics. Resolves
10431 - Drop support for detecting and warning about versions of Libevent
10432 before 1.3e. Nothing reasonable ships with them any longer;
10433 warning the user about them shouldn't be needed. Resolves ticket
10436 o Code simplifications and refactoring:
10437 - Rename "isin" functions to "contains", for grammar. Resolves
10439 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
10440 with the natural logarithm function from the system libm. Resolves
10444 Changes in version 0.2.4.9-alpha - 2013-01-15
10445 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
10446 work more robustly.
10449 - Fix backward compatibility logic when receiving an embedded ntor
10450 handshake tunneled in a CREATE cell. This clears up the "Bug:
10451 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
10455 Changes in version 0.2.4.8-alpha - 2013-01-14
10456 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
10457 risks, adds a new stronger and faster circuit handshake, and offers
10458 stronger and faster link encryption when both sides support it.
10461 - Preliminary support for directory guards (proposal 207): when
10462 possible, clients now use their entry guards for non-anonymous
10463 directory requests. This can help prevent client enumeration. Note
10464 that this behavior only works when we have a usable consensus
10465 directory, and when options about what to download are more or less
10466 standard. In the future we should re-bootstrap from our guards,
10467 rather than re-bootstrapping from the preconfigured list of
10468 directory sources that ships with Tor. Resolves ticket 6526.
10469 - Tor relays and clients now support a better CREATE/EXTEND cell
10470 format, allowing the sender to specify multiple address, identity,
10471 and handshake types. Implements Robert Ransom's proposal 200;
10472 closes ticket 7199.
10474 o Major features (new circuit handshake):
10475 - Tor now supports a new circuit extension handshake designed by Ian
10476 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
10477 circuit extension handshake, later called "TAP", was a bit slow
10478 (especially on the relay side), had a fragile security proof, and
10479 used weaker keys than we'd now prefer. The new circuit handshake
10480 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
10481 function, making it significantly more secure than the older
10482 handshake, and significantly faster. Tor can use one of two built-in
10483 pure-C curve25519-donna implementations by Adam Langley, or it
10484 can link against the "nacl" library for a tuned version if present.
10486 The built-in version is very fast for 64-bit systems when building
10487 with GCC. The built-in 32-bit version is still faster than the
10488 old TAP protocol, but using libnacl is better on most such hosts.
10490 Clients don't currently use this protocol by default, since
10491 comparatively few clients support it so far. To try it, set
10492 UseNTorHandshake to 1.
10494 Implements proposal 216; closes ticket 7202.
10496 o Major features (better link encryption):
10497 - Relays can now enable the ECDHE TLS ciphersuites when available
10498 and appropriate. These ciphersuites let us negotiate forward-secure
10499 TLS secret keys more safely and more efficiently than with our
10500 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
10501 public relays prefer the (faster) P224 group, and bridges prefer
10502 the (more common) P256 group; you can override this with the
10505 Enabling these ciphers was a little tricky, since for a long time,
10506 clients had been claiming to support them without actually doing
10507 so, in order to foil fingerprinting. But with the client-side
10508 implementation of proposal 198 in 0.2.3.17-beta, clients can now
10509 match the ciphers from recent Firefox versions *and* list the
10510 ciphers they actually mean, so relays can believe such clients
10511 when they advertise ECDHE support in their TLS ClientHello messages.
10513 This feature requires clients running 0.2.3.17-beta or later,
10514 and requires both sides to be running OpenSSL 1.0.0 or later
10515 with ECC support. OpenSSL 1.0.1, with the compile-time option
10516 "enable-ec_nistp_64_gcc_128", is highly recommended.
10518 Implements the relay side of proposal 198; closes ticket 7200.
10521 - Avoid crashing when, as a relay without IPv6-exit support, a
10522 client insists on getting an IPv6 address or nothing. Fixes bug
10523 7814; bugfix on 0.2.4.7-alpha.
10526 - Improve circuit build timeout handling for hidden services.
10527 In particular: adjust build timeouts more accurately depending
10528 upon the number of hop-RTTs that a particular circuit type
10529 undergoes. Additionally, launch intro circuits in parallel
10530 if they timeout, and take the first one to reply as valid.
10531 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
10532 separate error codes; or at least, don't break for that reason.
10533 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
10534 - Update to the January 2 2013 Maxmind GeoLite Country database.
10536 o Minor features (testing):
10537 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
10538 (P-256) Diffie-Hellman handshakes to src/or/bench.
10539 - Add benchmark functions to test onion handshake performance.
10541 o Minor features (path bias detection):
10542 - Alter the Path Bias log messages to be more descriptive in terms
10543 of reporting timeouts and other statistics.
10544 - Create three levels of Path Bias log messages, as opposed to just
10545 two. These are configurable via consensus as well as via the torrc
10546 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
10547 The default values are 0.70, 0.50, and 0.30 respectively.
10548 - Separate the log message levels from the decision to drop guards,
10549 which also is available via torrc option PathBiasDropGuards.
10550 PathBiasDropGuards still defaults to 0 (off).
10551 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
10552 in combination with PathBiasExtremeRate.
10553 - Increase the default values for PathBiasScaleThreshold and
10554 PathBiasCircThreshold from (200, 20) to (300, 150).
10555 - Add in circuit usage accounting to path bias. If we try to use a
10556 built circuit but fail for any reason, it counts as path bias.
10557 Certain classes of circuits where the adversary gets to pick your
10558 destination node are exempt from this accounting. Usage accounting
10559 can be specifically disabled via consensus parameter or torrc.
10560 - Convert all internal path bias state to double-precision floating
10561 point, to avoid roundoff error and other issues.
10562 - Only record path bias information for circuits that have completed
10563 *two* hops. Assuming end-to-end tagging is the attack vector, this
10564 makes us more resilient to ambient circuit failure without any
10565 detection capability loss.
10567 o Minor bugfixes (log messages):
10568 - Rate-limit the "No circuits are opened. Relaxed timeout for a
10569 circuit with channel state open..." message to once per hour to
10570 keep it from filling the notice logs. Mitigates bug 7799 but does
10571 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
10572 - Avoid spurious warnings when configuring multiple client ports of
10573 which only some are nonlocal. Previously, we had claimed that some
10574 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
10577 o Code simplifications and refactoring:
10578 - Get rid of a couple of harmless clang warnings, where we compared
10579 enums to ints. These warnings are newly introduced in clang 3.2.
10580 - Split the onion.c file into separate modules for the onion queue
10581 and the different handshakes it supports.
10582 - Remove the marshalling/unmarshalling code for sending requests to
10583 cpuworkers over a socket, and instead just send structs. The
10584 recipient will always be the same Tor binary as the sender, so
10585 any encoding is overkill.
10588 Changes in version 0.2.4.7-alpha - 2012-12-24
10589 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
10590 directory mirrors for more robust bootstrapping; fixes more issues where
10591 clients with changing network conditions refuse to make any circuits;
10592 adds initial support for exiting to IPv6 addresses; resumes being able
10593 to update our GeoIP database, and includes the geoip6 file this time;
10594 turns off the client-side DNS cache by default due to privacy risks;
10595 and fixes a variety of other issues.
10597 o Major features (client resilience):
10598 - Add a new "FallbackDir" torrc option to use when we can't use
10599 a directory mirror from the consensus (either because we lack a
10600 consensus, or because they're all down). Currently, all authorities
10601 are fallbacks by default, and there are no other default fallbacks,
10602 but that will change. This option will allow us to give clients a
10603 longer list of servers to try to get a consensus from when first
10604 connecting to the Tor network, and thereby reduce load on the
10605 directory authorities. Implements proposal 206, "Preconfigured
10606 directory sources for bootstrapping". We also removed the old
10607 "FallbackNetworkstatus" option, since we never got it working well
10608 enough to use it. Closes bug 572.
10609 - If we have no circuits open, use a relaxed timeout (the
10610 95-percentile cutoff) until a circuit succeeds. This heuristic
10611 should allow Tor to succeed at building circuits even when the
10612 network connection drastically changes. Should help with bug 3443.
10614 o Major features (IPv6):
10615 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
10616 connectivity, then set the IPv6Exit flag to 1. Also make sure your
10617 exit policy reads as you would like: the address * applies to all
10618 address families, whereas *4 is IPv4 address only, and *6 is IPv6
10619 addresses only. On the client side, you'll need to wait until the
10620 authorities have upgraded, wait for enough exits to support IPv6,
10621 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
10622 ticket 5547, implements proposal 117 as revised in proposal 208.
10624 We DO NOT recommend that clients with actual anonymity needs start
10625 using IPv6 over Tor yet, since not enough exits support it yet.
10627 o Major features (geoip database):
10628 - Maxmind began labelling Tor relays as being in country "A1",
10629 which breaks by-country node selection inside Tor. Now we use a
10630 script to replace "A1" ("Anonymous Proxy") entries in our geoip
10631 file with real country codes. This script fixes about 90% of "A1"
10632 entries automatically and uses manual country code assignments to
10633 fix the remaining 10%. See src/config/README.geoip for details.
10634 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
10635 Country database, as modified above.
10637 o Major bugfixes (client-side DNS):
10638 - Turn off the client-side DNS cache by default. Updating and using
10639 the DNS cache is now configurable on a per-client-port
10640 level. SOCKSPort, DNSPort, etc lines may now contain
10641 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
10642 cache these types of DNS answers when we receive them from an
10643 exit node in response to an application request on this port, and
10644 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
10645 cached DNS answers of these types, we shouldn't use them. It's
10646 potentially risky to use cached DNS answers at the client, since
10647 doing so can indicate to one exit what answers we've gotten
10648 for DNS lookups in the past. With IPv6, this becomes especially
10649 problematic. Using cached DNS answers for requests on the same
10650 circuit would present less linkability risk, since all traffic
10651 on a circuit is already linkable, but it would also provide
10652 little performance benefit: the exit node caches DNS replies
10653 too. Implements a simplified version of Proposal 205. Implements
10656 o Major bugfixes (other):
10657 - Alter circuit build timeout measurement to start at the point
10658 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
10659 initialization). This should make our timeout measurements more
10660 uniform. Previously, we were sometimes including ORconn setup time
10661 in our circuit build time measurements. Should resolve bug 3443.
10662 - Fix an assertion that could trigger in hibernate_go_dormant() when
10663 closing an or_connection_t: call channel_mark_for_close() rather
10664 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
10666 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
10667 7655; bugfix on 0.2.4.6-alpha.
10670 - Add a new torrc option "ServerTransportListenAddr" to let bridge
10671 operators select the address where their pluggable transports will
10672 listen for connections. Resolves ticket 7013.
10673 - Allow an optional $ before the node identity digest in the
10674 controller command GETINFO ns/id/<identity>, for consistency with
10675 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
10676 - Log packaged cell fullness as part of the heartbeat message.
10677 Diagnosis to try to determine the extent of bug 7743.
10679 o Minor features (IPv6):
10680 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
10681 prefer to hand out virtual IPv6 addresses, since there are more of
10682 them and we can't run out. To override this behavior and make IPv4
10683 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
10684 or DNSPort you're using for resolving. Implements ticket 7571.
10685 - AutomapHostsOnResolve responses are now randomized, to avoid
10686 annoying situations where Tor is restarted and applications
10687 connect to the wrong addresses.
10688 - Never try more than 1000 times to pick a new virtual address when
10689 AutomapHostsOnResolve is set. That's good enough so long as we
10690 aren't close to handing out our entire virtual address space;
10691 if you're getting there, it's best to switch to IPv6 virtual
10695 - The ADDRMAP command can no longer generate an ill-formed error
10696 code on a failed MAPADDRESS. It now says "internal" rather than
10697 an English sentence fragment with spaces in the middle. Bugfix on
10698 Tor 0.2.0.19-alpha.
10699 - Fix log messages and comments to avoid saying "GMT" when we mean
10700 "UTC". Fixes bug 6113.
10701 - Compile on win64 using mingw64. Fixes bug 7260; patches from
10703 - Fix a crash when debugging unit tests on Windows: deallocate a
10704 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
10705 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
10708 - The DirServer option is now DirAuthority, for consistency with
10709 current naming patterns. You can still use the old DirServer form.
10711 o Code simplification and refactoring:
10712 - Move the client-side address-map/virtual-address/DNS-cache code
10713 out of connection_edge.c into a new addressmap.c module.
10714 - Remove unused code for parsing v1 directories and "running routers"
10715 documents. Fixes bug 6887.
10718 Changes in version 0.2.3.25 - 2012-11-19
10719 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
10720 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
10721 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
10722 programmer, and friend. Unstinting in his dedication to the cause of
10723 freedom, he inspired and helped many of us as we began our work on
10724 anonymity, and inspires us still. Please honor his memory by writing
10725 software to protect people's freedoms, and by helping others to do so.
10727 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
10728 significantly reduced directory overhead (via microdescriptors),
10729 enormous crypto performance improvements for fast relays on new
10730 enough hardware, a new v3 TLS handshake protocol that can better
10731 resist fingerprinting, support for protocol obfuscation plugins (aka
10732 pluggable transports), better scalability for hidden services, IPv6
10733 support for bridges, performance improvements like allowing clients
10734 to skip the first round-trip on the circuit ("optimistic data") and
10735 refilling token buckets more often, a new "stream isolation" design
10736 to isolate different applications on different circuits, and many
10737 stability, security, and privacy fixes.
10740 - Tor tries to wipe potentially sensitive data after using it, so
10741 that if some subsequent security failure exposes Tor's memory,
10742 the damage will be limited. But we had a bug where the compiler
10743 was eliminating these wipe operations when it decided that the
10744 memory was no longer visible to a (correctly running) program,
10745 hence defeating our attempt at defense in depth. We fix that
10746 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10747 is unlikely to optimize away. Future versions of Tor may use
10748 a less ridiculously heavy approach for this. Fixes bug 7352.
10749 Reported in an article by Andrey Karpov.
10752 - Fix a harmless bug when opting against publishing a relay descriptor
10753 because DisableNetwork is set. Fixes bug 7464; bugfix on
10757 Changes in version 0.2.4.6-alpha - 2012-11-13
10758 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
10759 makes our defense-in-depth memory wiping more reliable, and begins to
10760 count IPv6 addresses in bridge statistics,
10763 - Fix an assertion failure that could occur when closing a connection
10764 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
10766 - Tor tries to wipe potentially sensitive data after using it, so
10767 that if some subsequent security failure exposes Tor's memory,
10768 the damage will be limited. But we had a bug where the compiler
10769 was eliminating these wipe operations when it decided that the
10770 memory was no longer visible to a (correctly running) program,
10771 hence defeating our attempt at defense in depth. We fix that
10772 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
10773 is unlikely to optimize away. Future versions of Tor may use
10774 a less ridiculously heavy approach for this. Fixes bug 7352.
10775 Reported in an article by Andrey Karpov.
10778 - Add GeoIP database for IPv6 addresses. The new config option
10780 - Bridge statistics now count bridge clients connecting over IPv6:
10781 bridge statistics files now list "bridge-ip-versions" and
10782 extra-info documents list "geoip6-db-digest". The control protocol
10783 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
10784 implementation by "shkoo", addressing ticket 5055.
10787 - Warn when we are binding low ports when hibernation is enabled;
10788 previously we had warned when we were _advertising_ low ports with
10789 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
10790 - Fix a harmless bug when opting against publishing a relay descriptor
10791 because DisableNetwork is set. Fixes bug 7464; bugfix on
10793 - Add warning message when a managed proxy dies during configuration.
10794 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
10795 - Fix a linking error when building tor-fw-helper without miniupnp.
10796 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
10797 - Check for closing an or_connection_t without going through correct
10798 channel functions; emit a warning and then call
10799 connection_or_close_for_error() so we don't assert as in bugs 7212
10801 - Compile correctly on compilers without C99 designated initializer
10802 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
10803 - Avoid a possible assert that can occur when channel_send_destroy() is
10804 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
10805 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
10806 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
10807 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
10808 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
10810 o Code simplification and refactoring:
10811 - Start using OpenBSD's implementation of queue.h, so that we don't
10812 need to hand-roll our own pointer and list structures whenever we
10813 need them. (We can't rely on a sys/queue.h, since some operating
10814 systems don't have them, and the ones that do have them don't all
10815 present the same extensions.)
10818 Changes in version 0.2.4.5-alpha - 2012-10-25
10819 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
10820 two important security vulnerabilities that could lead to remotely
10821 triggerable relay crashes, fix a major bug that was preventing clients
10822 from choosing suitable exit nodes, and refactor some of our code.
10824 o Major bugfixes (security, also in 0.2.3.24-rc):
10825 - Fix a group of remotely triggerable assertion failures related to
10826 incorrect link protocol negotiation. Found, diagnosed, and fixed
10827 by "some guy from France". Fix for CVE-2012-2250; bugfix on
10829 - Fix a denial of service attack by which any directory authority
10830 could crash all the others, or by which a single v2 directory
10831 authority could crash everybody downloading v2 directory
10832 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10834 o Major bugfixes (also in 0.2.3.24-rc):
10835 - When parsing exit policy summaries from microdescriptors, we had
10836 previously been ignoring the last character in each one, so that
10837 "accept 80,443,8080" would be treated by clients as indicating
10838 a node that allows access to ports 80, 443, and 808. That would
10839 lead to clients attempting connections that could never work,
10840 and ignoring exit nodes that would support their connections. Now
10841 clients parse these exit policy summaries correctly. Fixes bug 7192;
10842 bugfix on 0.2.3.1-alpha.
10844 o Minor bugfixes (also in 0.2.3.24-rc):
10845 - Clients now consider the ClientRejectInternalAddresses config option
10846 when using a microdescriptor consensus stanza to decide whether
10847 an exit relay would allow exiting to an internal address. Fixes
10848 bug 7190; bugfix on 0.2.3.1-alpha.
10851 - Only disable TLS session ticket support when running as a TLS
10852 server. Now clients will blend better with regular Firefox
10853 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
10855 o Code simplification and refactoring:
10856 - Start using OpenBSD's implementation of queue.h (originally by
10858 - Move the entry node code from circuitbuild.c to its own file.
10859 - Move the circuit build timeout tracking code from circuitbuild.c
10863 Changes in version 0.2.3.24-rc - 2012-10-25
10864 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
10865 could lead to remotely triggerable relay crashes, and fixes
10866 a major bug that was preventing clients from choosing suitable exit
10869 o Major bugfixes (security):
10870 - Fix a group of remotely triggerable assertion failures related to
10871 incorrect link protocol negotiation. Found, diagnosed, and fixed
10872 by "some guy from France". Fix for CVE-2012-2250; bugfix on
10874 - Fix a denial of service attack by which any directory authority
10875 could crash all the others, or by which a single v2 directory
10876 authority could crash everybody downloading v2 directory
10877 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
10880 - When parsing exit policy summaries from microdescriptors, we had
10881 previously been ignoring the last character in each one, so that
10882 "accept 80,443,8080" would be treated by clients as indicating
10883 a node that allows access to ports 80, 443, and 808. That would
10884 lead to clients attempting connections that could never work,
10885 and ignoring exit nodes that would support their connections. Now
10886 clients parse these exit policy summaries correctly. Fixes bug 7192;
10887 bugfix on 0.2.3.1-alpha.
10890 - Clients now consider the ClientRejectInternalAddresses config option
10891 when using a microdescriptor consensus stanza to decide whether
10892 an exit relay would allow exiting to an internal address. Fixes
10893 bug 7190; bugfix on 0.2.3.1-alpha.
10896 Changes in version 0.2.4.4-alpha - 2012-10-20
10897 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
10898 vulnerability introduced by a change in OpenSSL, fixes a remotely
10899 triggerable assert, and adds new channel_t and circuitmux_t abstractions
10900 that will make it easier to test new connection transport and cell
10901 scheduling algorithms.
10903 o New directory authorities (also in 0.2.3.23-rc):
10904 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
10905 authority. Closes ticket 5749.
10907 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
10908 - Disable TLS session tickets. OpenSSL's implementation was giving
10909 our TLS session keys the lifetime of our TLS context objects, when
10910 perfect forward secrecy would want us to discard anything that
10911 could decrypt a link connection as soon as the link connection
10912 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
10913 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
10914 - Discard extraneous renegotiation attempts once the V3 link
10915 protocol has been initiated. Failure to do so left us open to
10916 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
10917 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
10919 o Internal abstraction features:
10920 - Introduce new channel_t abstraction between circuits and
10921 or_connection_t to allow for implementing alternate OR-to-OR
10922 transports. A channel_t is an abstract object which can either be a
10923 cell-bearing channel, which is responsible for authenticating and
10924 handshaking with the remote OR and transmitting cells to and from
10925 it, or a listening channel, which spawns new cell-bearing channels
10926 at the request of remote ORs. Implements part of ticket 6465.
10927 - Also new is the channel_tls_t subclass of channel_t, adapting it
10928 to the existing or_connection_t code. The V2/V3 protocol handshaking
10929 code which formerly resided in command.c has been moved below the
10930 channel_t abstraction layer and may be found in channeltls.c now.
10931 Implements the rest of ticket 6465.
10932 - Introduce new circuitmux_t storing the queue of circuits for
10933 a channel; this encapsulates and abstracts the queue logic and
10934 circuit selection policy, and allows the latter to be overridden
10935 easily by switching out a policy object. The existing EWMA behavior
10936 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
10938 o Required libraries:
10939 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
10940 strongly recommended.
10943 - Warn users who run hidden services on a Tor client with
10944 UseEntryGuards disabled that their hidden services will be
10945 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
10946 attack which motivated Tor to support entry guards in the first
10947 place). Resolves ticket 6889.
10948 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
10949 dhill. Resolves ticket 6982.
10950 - Option OutboundBindAddress can be specified multiple times and
10951 accepts IPv6 addresses. Resolves ticket 6876.
10953 o Minor bugfixes (also in 0.2.3.23-rc):
10954 - Don't serve or accept v2 hidden service descriptors over a
10955 relay's DirPort. It's never correct to do so, and disabling it
10956 might make it more annoying to exploit any bugs that turn up in the
10957 descriptor-parsing code. Fixes bug 7149.
10958 - Fix two cases in src/or/transports.c where we were calling
10959 fmt_addr() twice in a parameter list. Bug found by David
10960 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
10961 - Fix memory leaks whenever we logged any message about the "path
10962 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
10963 - When relays refuse a "create" cell because their queue of pending
10964 create cells is too big (typically because their cpu can't keep up
10965 with the arrival rate), send back reason "resource limit" rather
10966 than reason "internal", so network measurement scripts can get a
10967 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
10970 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
10971 - Free some more still-in-use memory at exit, to make hunting for
10972 memory leaks easier. Resolves bug 7029.
10973 - When a Tor client gets a "truncated" relay cell, the first byte of
10974 its payload specifies why the circuit was truncated. We were
10975 ignoring this 'reason' byte when tearing down the circuit, resulting
10976 in the controller not being told why the circuit closed. Now we
10977 pass the reason from the truncated cell to the controller. Bugfix
10978 on 0.1.2.3-alpha; fixes bug 7039.
10979 - Downgrade "Failed to hand off onionskin" messages to "debug"
10980 severity, since they're typically redundant with the "Your computer
10981 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
10982 - Make clients running with IPv6 bridges connect over IPv6 again,
10983 even without setting new config options ClientUseIPv6 and
10984 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
10985 - Use square brackets around IPv6 addresses in numerous places
10986 that needed them, including log messages, HTTPS CONNECT proxy
10987 requests, TransportProxy statefile entries, and pluggable transport
10988 extra-info lines. Fixes bug 7011; patch by David Fifield.
10990 o Code refactoring and cleanup:
10991 - Source files taken from other packages now reside in src/ext;
10992 previously they were scattered around the rest of Tor.
10993 - Avoid use of reserved identifiers in our C code. The C standard
10994 doesn't like us declaring anything that starts with an
10995 underscore, so let's knock it off before we get in trouble. Fix
10996 for bug 1031; bugfix on the first Tor commit.
10999 Changes in version 0.2.3.23-rc - 2012-10-20
11000 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
11001 vulnerability introduced by a change in OpenSSL, and fixes a variety
11002 of smaller bugs in preparation for the release.
11004 o New directory authorities:
11005 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
11006 authority. Closes ticket 5749.
11008 o Major bugfixes (security/privacy):
11009 - Disable TLS session tickets. OpenSSL's implementation was giving
11010 our TLS session keys the lifetime of our TLS context objects, when
11011 perfect forward secrecy would want us to discard anything that
11012 could decrypt a link connection as soon as the link connection
11013 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
11014 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
11015 - Discard extraneous renegotiation attempts once the V3 link
11016 protocol has been initiated. Failure to do so left us open to
11017 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
11018 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
11021 - Fix a possible crash bug when checking for deactivated circuits
11022 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11023 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11025 o Minor bugfixes (on 0.2.3.x):
11026 - Fix two cases in src/or/transports.c where we were calling
11027 fmt_addr() twice in a parameter list. Bug found by David
11028 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
11029 - Convert an assert in the pathbias code to a log message. The assert
11030 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
11031 bugfix on 0.2.3.17-beta.
11032 - Fix memory leaks whenever we logged any message about the "path
11033 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
11035 o Minor bugfixes (on 0.2.2.x and earlier):
11036 - Don't serve or accept v2 hidden service descriptors over a relay's
11037 DirPort. It's never correct to do so, and disabling it might
11038 make it more annoying to exploit any bugs that turn up in the
11039 descriptor-parsing code. Fixes bug 7149.
11040 - When relays refuse a "create" cell because their queue of pending
11041 create cells is too big (typically because their cpu can't keep up
11042 with the arrival rate), send back reason "resource limit" rather
11043 than reason "internal", so network measurement scripts can get a
11044 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
11045 - Correct file sizes when reading binary files on Cygwin, to avoid
11046 a bug where Tor would fail to read its state file. Fixes bug 6844;
11047 bugfix on 0.1.2.7-alpha.
11048 - Avoid undefined behavior when parsing the list of supported
11049 rendezvous/introduction protocols in a hidden service descriptor.
11050 Previously, Tor would have confused (as-yet-unused) protocol version
11051 numbers greater than 32 with lower ones on many platforms. Fixes
11052 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11054 o Documentation fixes:
11055 - Clarify that hidden services are TCP only. Fixes bug 6024.
11058 Changes in version 0.2.4.3-alpha - 2012-09-22
11059 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
11060 assertion, resumes letting relays test reachability of their DirPort,
11061 and cleans up a bunch of smaller bugs.
11064 - Fix an assertion failure in tor_timegm() that could be triggered
11065 by a badly formatted directory object. Bug found by fuzzing with
11066 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11069 - Fix a possible crash bug when checking for deactivated circuits
11070 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
11071 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
11072 - Allow routers to detect that their own DirPorts are running. When
11073 we removed support for versions_supports_begindir, we also
11074 accidentally removed the mechanism we used to self-test our
11075 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
11076 bugfix on 0.2.4.2-alpha.
11078 o Security features:
11079 - Switch to a completely time-invariant approach for picking nodes
11080 weighted by bandwidth. Our old approach would run through the
11081 part of the loop after it had made its choice slightly slower
11082 than it ran through the part of the loop before it had made its
11083 choice. Addresses ticket 6538.
11084 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
11085 by tor2web clients allows hidden services to identify tor2web
11086 clients through their repeated selection of the same rendezvous
11087 and introduction point circuit endpoints (their guards). Resolves
11091 - Enable Tor to read configuration, state, and key information from
11092 a FIFO. Previously Tor would only read from files with a positive
11093 stat.st_size. Code from meejah; fixes bug 6044.
11096 - Correct file sizes when reading binary files on Cygwin, to avoid
11097 a bug where Tor would fail to read its state file. Fixes bug 6844;
11098 bugfix on 0.1.2.7-alpha.
11099 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
11100 bugfix on 0.2.0.3-alpha.
11101 - When complaining about a client port on a public address, log
11102 which address we're complaining about. Fixes bug 4020; bugfix on
11103 0.2.3.3-alpha. Patch by Tom Fitzhenry.
11104 - Convert an assert in the pathbias code to a log message. The assert
11105 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
11106 bugfix on 0.2.3.17-beta.
11107 - Our new buildsystem was overzealous about rebuilding manpages: it
11108 would rebuild them all whenever any one of them changed. Now our
11109 dependency checking should be correct. Fixes bug 6843; bugfix on
11111 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
11112 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
11113 - Correct log printout about which address family is preferred
11114 when connecting to a bridge with both an IPv4 and IPv6 OR port.
11115 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
11117 o Minor bugfixes (code cleanliness):
11118 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
11119 with large values. This situation was untriggered, but nevertheless
11120 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
11121 - Reject consensus votes with more than 64 known-flags. We aren't even
11122 close to that limit yet, and our code doesn't handle it correctly.
11123 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
11124 - Avoid undefined behavior when parsing the list of supported
11125 rendezvous/introduction protocols in a hidden service descriptor.
11126 Previously, Tor would have confused (as-yet-unused) protocol version
11127 numbers greater than 32 with lower ones on many platforms. Fixes
11128 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
11129 - Fix handling of rendezvous client authorization types over 8.
11130 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
11131 - Fix building with older versions of GCC (2.95, for one) that don't
11132 like preprocessor directives inside macro arguments. Found by
11133 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
11134 - Switch weighted node selection rule from using a list of doubles
11135 to using a list of int64_t. This change should make the process
11136 slightly easier to debug and maintain. Needed to finish ticket 6538.
11138 o Code simplification and refactoring:
11139 - Move the generic "config" code into a new file, and have "config.c"
11140 hold only torrc- and state-related code. Resolves ticket 6823.
11141 - Move the core of our "choose a weighted element at random" logic
11142 into its own function, and give it unit tests. Now the logic is
11143 testable, and a little less fragile too.
11144 - Removed the testing_since field of node_t, which hasn't been used
11145 for anything since 0.2.0.9-alpha.
11147 o Documentation fixes:
11148 - Clarify that hidden services are TCP only. Fixes bug 6024.
11149 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
11153 Changes in version 0.2.3.22-rc - 2012-09-11
11154 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
11158 - Fix an assertion failure in tor_timegm() that could be triggered
11159 by a badly formatted directory object. Bug found by fuzzing with
11160 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11163 - Avoid segfault when starting up having run with an extremely old
11164 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11168 Changes in version 0.2.2.39 - 2012-09-11
11169 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
11173 - Fix an assertion failure in tor_timegm() that could be triggered
11174 by a badly formatted directory object. Bug found by fuzzing with
11175 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
11176 - Do not crash when comparing an address with port value 0 to an
11177 address policy. This bug could have been used to cause a remote
11178 assertion failure by or against directory authorities, or to
11179 allow some applications to crash clients. Fixes bug 6690; bugfix
11183 Changes in version 0.2.4.2-alpha - 2012-09-10
11184 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
11185 raises the default rate limiting even more, and makes the bootstrapping
11186 log messages less noisy.
11189 - Automatically forward the TCP ports of pluggable transport
11190 proxies using tor-fw-helper if PortForwarding is enabled. Implements
11194 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
11195 to 1GB/1GB. The previous defaults were intended to be "basically
11196 infinite", but it turns out they're now limiting our 100mbit+
11197 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
11198 last time we raised it).
11201 - Detect when we're running with a version of OpenSSL other than the
11202 one we compiled with. This has occasionally given people hard-to-
11204 - Log fewer lines at level "notice" about our OpenSSL and Libevent
11205 versions and capabilities when everything is going right. Resolves
11206 part of ticket 6736.
11207 - Directory authorities no long accept descriptors for any version of
11208 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
11209 These versions are insecure, unsupported, or both. Implements
11213 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
11214 to start with a triple-underscore so the controller won't touch it.
11215 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
11216 - Avoid segfault when starting up having run with an extremely old
11217 version of Tor and parsing its state file. Fixes bug 6801; bugfix
11219 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
11220 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
11221 - Don't follow the NULL pointer if microdescriptor generation fails.
11222 (This does not appear to be triggerable, but it's best to be safe.)
11223 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
11224 - Fix mis-declared dependencies on src/common/crypto.c and
11225 src/or/tor_main.c that could break out-of-tree builds under some
11226 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
11227 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
11228 6778; bugfix on 0.2.4.1-alpha.
11229 - Fix a harmless (in this case) build warning for implicitly
11230 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
11232 o Removed features:
11233 - Now that all versions before 0.2.2.x are disallowed, we no longer
11234 need to work around their missing features. Thus we can remove a
11235 bunch of compatibility code.
11237 o Code refactoring:
11238 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
11239 TCP ports to forward. In the past it only accepted two ports:
11240 the ORPort and the DirPort.
11243 Changes in version 0.2.4.1-alpha - 2012-09-05
11244 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
11245 bridgedb; lets relays use IPv6 addresses and directory authorities
11246 advertise them; and switches to a cleaner build interface.
11248 This is the first alpha release in a new series, so expect there to
11249 be bugs. Users who would rather test out a more stable branch should
11250 stay with 0.2.3.x for now.
11252 o Major features (bridges):
11253 - Bridges now report the pluggable transports they support to the
11254 bridge authority, so it can pass the supported transports on to
11255 bridgedb and/or eventually do reachability testing. Implements
11258 o Major features (IPv6):
11259 - Bridge authorities now accept IPv6 bridge addresses and include
11260 them in network status documents. Implements ticket 5534.
11261 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
11262 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
11263 to happen. Implements ticket 5535.
11264 - All kind of relays, not just bridges, can now advertise an IPv6
11265 OR port. Implements ticket 6362.
11266 - Directory authorities vote on IPv6 OR ports using the new consensus
11267 method 14. Implements ticket 6363.
11269 o Major features (build):
11270 - Switch to a nonrecursive Makefile structure. Now instead of each
11271 Makefile.am invoking other Makefile.am's, there is a master
11272 Makefile.am that includes the others. This change makes our build
11273 process slightly more maintainable, and improves parallelism for
11274 building with make -j. Original patch by Stewart Smith; various
11275 fixes by Jim Meyering.
11276 - Where available, we now use automake's "silent" make rules by
11277 default, so that warnings are easier to spot. You can get the old
11278 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
11280 o Minor features (code security and spec conformance):
11281 - Clear keys and key-derived material left on the stack in
11282 rendservice.c and rendclient.c. Check return value of
11283 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
11284 These fixes should make us more forward-secure against cold-boot
11285 attacks and the like. Fixes bug 2385.
11286 - Reject EXTEND cells sent to nonexistent streams. According to the
11287 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
11288 we were only checking for stream IDs that were currently in use.
11289 Found while hunting for more instances of bug 6271. Bugfix on
11290 0.0.2pre8, which introduced incremental circuit construction.
11292 o Minor features (streamlining);
11293 - No longer include the "opt" prefix when generating routerinfos
11294 or v2 directories: it has been needless since Tor 0.1.2. Closes
11296 - Remove some now-needless code that tried to aggressively flush
11297 OR connections as data was added to them. Since 0.2.0.1-alpha, our
11298 cell queue logic has saved us from the failure mode that this code
11299 was supposed to prevent. Removing this code will limit the number
11300 of baroque control flow paths through Tor's network logic. Reported
11301 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
11303 o Minor features (controller):
11304 - Add a "GETINFO signal/names" control port command. Implements
11306 - Provide default values for all options via "GETINFO config/defaults".
11307 Implements ticket 4971.
11309 o Minor features (IPv6):
11310 - New config option "AuthDirHasIPv6Connectivity 1" that directory
11311 authorities should set if they have IPv6 connectivity and want to
11312 do reachability tests for IPv6 relays. Implements feature 5974.
11313 - A relay with an IPv6 OR port now sends that address in NETINFO
11314 cells (in addition to its other address). Implements ticket 6364.
11316 o Minor features (log messages):
11317 - Omit the first heartbeat log message, because it never has anything
11318 useful to say, and it clutters up the bootstrapping messages.
11319 Resolves ticket 6758.
11320 - Don't log about reloading the microdescriptor cache at startup. Our
11321 bootstrap warnings are supposed to tell the user when there's a
11322 problem, and our bootstrap notices say when there isn't. Resolves
11323 ticket 6759; bugfix on 0.2.2.6-alpha.
11324 - Don't log "I learned some more directory information" when we're
11325 reading cached directory information. Reserve it for when new
11326 directory information arrives in response to a fetch. Resolves
11328 - Prevent rounding error in path bias counts when scaling
11329 them down, and use the correct scale factor default. Also demote
11330 some path bias related log messages down a level and make others
11331 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
11332 - We no longer warn so much when generating manpages from their
11335 o Code simplifications and refactoring:
11336 - Enhance our internal sscanf replacement so that we can eliminate
11337 the last remaining uses of the system sscanf. (Though those uses
11338 of sscanf were safe, sscanf itself is generally error prone, so
11339 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
11341 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
11342 - Move last_reachable and testing_since from routerinfo_t to node_t.
11343 Implements ticket 5529.
11344 - Add replaycache_t structure, functions and unit tests, then refactor
11345 rend_service_introduce() to be more clear to read, improve, debug,
11346 and test. Resolves bug 6177.
11347 - Finally remove support for malloc_good_size and malloc_usable_size.
11348 We had hoped that these functions would let us eke a little more
11349 memory out of our malloc implementation. Unfortunately, the only
11350 implementations that provided these functions are also ones that
11351 are already efficient about not overallocation: they never got us
11352 more than 7 or so bytes per allocation. Removing them saves us a
11353 little code complexity and a nontrivial amount of build complexity.
11355 o New requirements:
11356 - Tor maintainers now require Automake version 1.9 or later to build
11357 Tor from the Git repository. (Automake is not required when building
11358 from a source distribution.)
11361 Changes in version 0.2.3.21-rc - 2012-09-05
11362 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
11363 series. It fixes a trio of potential security bugs, fixes a bug where
11364 we were leaving some of the fast relays out of the microdescriptor
11365 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
11366 and cleans up other smaller issues.
11368 o Major bugfixes (security):
11369 - Tear down the circuit if we get an unexpected SENDME cell. Clients
11370 could use this trick to make their circuits receive cells faster
11371 than our flow control would have allowed, or to gum up the network,
11372 or possibly to do targeted memory denial-of-service attacks on
11373 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
11374 from July 2002, before the release of Tor 0.0.0. We had committed
11375 this patch previously, but we had to revert it because of bug 6271.
11376 Now that 6271 is fixed, this patch appears to work.
11377 - Reject any attempt to extend to an internal address. Without
11378 this fix, a router could be used to probe addresses on an internal
11379 network to see whether they were accepting connections. Fixes bug
11380 6710; bugfix on 0.0.8pre1.
11381 - Do not crash when comparing an address with port value 0 to an
11382 address policy. This bug could have been used to cause a remote
11383 assertion failure by or against directory authorities, or to
11384 allow some applications to crash clients. Fixes bug 6690; bugfix
11388 - Remove the upper bound on microdescriptor length. We were hitting
11389 the limit for routers with complex exit policies or family
11390 declarations, causing clients to not use them. Fixes the first
11391 piece of bug 6404; fix on 0.2.2.6-alpha.
11392 - Detect "ORPort 0" as meaning, uniformly, that we're not running
11393 as a relay. Previously, some of our code would treat the presence
11394 of any ORPort line as meaning that we should act like a relay,
11395 even though our new listener code would correctly not open any
11396 ORPorts for ORPort 0. Similar bugs in other Port options are also
11397 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
11400 - Avoid a pair of double-free and use-after-mark bugs that can
11401 occur with certain timings in canceled and re-received DNS
11402 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
11403 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
11404 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
11405 - Allow one-hop directory fetching circuits the full "circuit build
11406 timeout" period, rather than just half of it, before failing them
11407 and marking the relay down. This fix should help reduce cases where
11408 clients declare relays (or worse, bridges) unreachable because
11409 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
11410 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
11412 - Authorities no longer include any router in their microdescriptor
11413 consensuses for which they couldn't generate or agree on a
11414 microdescriptor. Fixes the second piece of bug 6404; fix on
11416 - Detect and reject attempts to specify both "FooPort" and
11417 "FooPort 0" in the same configuration domain. (It's still okay
11418 to have a FooPort in your configuration file, and use "FooPort 0"
11419 on the command line to disable it.) Fixes the second half of bug
11420 6507; bugfix on 0.2.3.3-alpha.
11421 - Make wildcarded addresses (that is, ones beginning with "*.") work
11422 when provided via the controller's MapAddress command. Previously,
11423 they were accepted, but we never actually noticed that they were
11424 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
11425 - Avoid crashing on a malformed state file where EntryGuardPathBias
11426 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
11427 - Add a (probably redundant) memory clear between iterations of
11428 the router status voting loop, to prevent future coding errors
11429 where data might leak between iterations of the loop. Resolves
11432 o Minor bugfixes (log messages):
11433 - Downgrade "set buildtimeout to low value" messages to "info"
11434 severity; they were never an actual problem, there was never
11435 anything reasonable to do about them, and they tended to spam logs
11436 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
11437 - Downgrade path-bias warning messages to "info". We'll try to get
11438 them working better in 0.2.4. Add internal circuit construction
11439 state to protect against the noisy warn message "Unexpectedly high
11440 circuit_successes". Also add some additional rate-limited notice
11441 messages to help determine the root cause of the warn. Fixes bug
11442 6475. Bugfix against 0.2.3.17-beta.
11443 - Move log message when unable to find a microdesc in a routerstatus
11444 entry to parse time. Previously we'd spam this warning every time
11445 we tried to figure out which microdescriptors to download. Fixes
11446 the third piece of bug 6404; fix on 0.2.3.18-rc.
11449 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
11450 change when the authority is deciding whether to accept a newly
11451 uploaded descriptor. Implements ticket 6423.
11452 - Add missing documentation for consensus and microdesc files.
11453 Resolves ticket 6732.
11456 Changes in version 0.2.2.38 - 2012-08-12
11457 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
11458 attack that could in theory leak path information.
11461 - Avoid an uninitialized memory read when reading a vote or consensus
11462 document that has an unrecognized flavor name. This read could
11463 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
11464 - Try to leak less information about what relays a client is
11465 choosing to a side-channel attacker. Previously, a Tor client would
11466 stop iterating through the list of available relays as soon as it
11467 had chosen one, thus finishing a little earlier when it picked
11468 a router earlier in the list. If an attacker can recover this
11469 timing information (nontrivial but not proven to be impossible),
11470 they could learn some coarse-grained information about which relays
11471 a client was picking (middle nodes in particular are likelier to
11472 be affected than exits). The timing attack might be mitigated by
11473 other factors (see bug 6537 for some discussion), but it's best
11474 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
11477 Changes in version 0.2.3.20-rc - 2012-08-05
11478 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
11479 series. It fixes a pair of code security bugs and a potential anonymity
11480 issue, updates our RPM spec files, and cleans up other smaller issues.
11483 - Avoid read-from-freed-memory and double-free bugs that could occur
11484 when a DNS request fails while launching it. Fixes bug 6480;
11485 bugfix on 0.2.0.1-alpha.
11486 - Avoid an uninitialized memory read when reading a vote or consensus
11487 document that has an unrecognized flavor name. This read could
11488 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
11489 - Try to leak less information about what relays a client is
11490 choosing to a side-channel attacker. Previously, a Tor client would
11491 stop iterating through the list of available relays as soon as it
11492 had chosen one, thus finishing a little earlier when it picked
11493 a router earlier in the list. If an attacker can recover this
11494 timing information (nontrivial but not proven to be impossible),
11495 they could learn some coarse-grained information about which relays
11496 a client was picking (middle nodes in particular are likelier to
11497 be affected than exits). The timing attack might be mitigated by
11498 other factors (see bug 6537 for some discussion), but it's best
11499 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
11502 - Try to make the warning when giving an obsolete SOCKSListenAddress
11503 a little more useful.
11504 - Terminate active server managed proxies if Tor stops being a
11505 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
11506 - Provide a better error message about possible OSX Asciidoc failure
11507 reasons. Fixes bug 6436.
11508 - Warn when Tor is configured to use accounting in a way that can
11509 link a hidden service to some other hidden service or public
11510 address. Resolves ticket 6490.
11513 - Check return value of fputs() when writing authority certificate
11514 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
11515 - Ignore ServerTransportPlugin lines when Tor is not configured as
11516 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
11517 - When disabling guards for having too high a proportion of failed
11518 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
11522 - Update our default RPM spec files to work with mock and rpmbuild
11523 on RHEL/Fedora. They have an updated set of dependencies and
11524 conflicts, a fix for an ancient typo when creating the "_tor"
11525 user, and better instructions. Thanks to Ondrej Mikle for the
11526 patch series. Fixes bug 6043.
11529 - Make it possible to set the TestingTorNetwork configuration
11530 option using AlternateDirAuthority and AlternateBridgeAuthority
11531 as an alternative to setting DirServer. Addresses ticket 6377.
11534 - Clarify the documentation for the Alternate*Authority options.
11536 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
11538 o Code simplification and refactoring:
11539 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
11540 10 lines. Also, don't nest them. Doing so in the past has
11541 led to hard-to-debug code. The new style is to use the
11542 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
11545 Changes in version 0.2.3.19-rc - 2012-07-06
11546 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
11547 series. It fixes the compile on Windows, reverts to a GeoIP database
11548 that isn't as broken, and fixes a flow control bug that has been around
11549 since the beginning of Tor.
11552 - Fix a bug handling SENDME cells on nonexistent streams that could
11553 result in bizarre window values. Report and patch contributed
11554 pseudonymously. Fixes part of bug 6271. This bug was introduced
11555 before the first Tor release, in svn commit r152.
11556 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
11557 June 2012 database, Maxmind marked many Tor relays as country "A1",
11558 which will cause risky behavior for clients that set EntryNodes
11559 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
11560 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
11561 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
11564 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
11565 bugfix on 0.2.1.10-alpha.
11568 Changes in version 0.2.3.18-rc - 2012-06-28
11569 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
11570 series. It fixes a few smaller bugs, but generally appears stable.
11571 Please test it and let us know whether it is!
11574 - Allow wildcarded mapaddress targets to be specified on the
11575 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
11576 - Make our linker option detection code more robust against linkers
11577 such as on FreeBSD 8, where a bad combination of options completes
11578 successfully but makes an unrunnable binary. Fixes bug 6173;
11579 bugfix on 0.2.3.17-beta.
11581 o Minor bugfixes (on 0.2.2.x and earlier):
11582 - Avoid a false positive in the util/threads unit test by increasing
11583 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
11584 - Replace "Sending publish request" log messages with "Launching
11585 upload", so that they no longer confusingly imply that we're
11586 sending something to a directory we might not even be connected
11587 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
11588 - Make sure to set *socket_error in all error cases in
11589 connection_connect(), so it can't produce a warning about
11590 errno being zero from errno_to_orconn_end_reason(). Bugfix on
11591 0.2.1.1-alpha; resolves ticket 6028.
11592 - Downgrade "Got a certificate, but we already have it" log messages
11593 from warning to info, except when we're a dirauth. Fixes bug 5238;
11594 bugfix on 0.2.1.7-alpha.
11595 - When checking for requested signatures on the latest consensus
11596 before serving it to a client, make sure to check the right
11597 consensus flavor. Bugfix on 0.2.2.6-alpha.
11598 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
11599 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
11601 o Minor bugfixes (on 0.2.3.x):
11602 - Make format_helper_exit_status() avoid unnecessary space padding
11603 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
11605 - Downgrade a message about cleaning the microdescriptor cache to
11606 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
11607 - Log a BUG message at severity INFO if we have a networkstatus with
11608 a missing entry for some microdescriptor. Continues on a patch
11610 - Improve the log message when a managed proxy fails to launch. Fixes
11611 bug 5099; bugfix on 0.2.3.6-alpha.
11612 - Don't do DNS lookups when parsing corrupted managed proxy protocol
11613 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
11614 - When formatting wildcarded address mappings for the controller,
11615 be sure to include "*." as appropriate. Partially fixes bug 6244;
11616 bugfix on 0.2.3.9-alpha.
11617 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
11618 Bugfix on 0.2.3.13-alpha.
11619 - Stop logging messages about running with circuit timeout learning
11620 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
11621 - Disable a spurious warning about reading on a marked and flushing
11622 connection. We shouldn't be doing that, but apparently we
11623 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
11624 - Fix a bug that stopped AllowDotExit from working on addresses
11625 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
11628 o Code simplification, refactoring, unit tests:
11629 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
11630 Libevent's notion of cached time when possible.
11631 - Remove duplicate code for invoking getrlimit() from control.c.
11632 - Add a unit test for the environment_variable_names_equal function.
11635 - Document the --defaults-torrc option, and the new (in 0.2.3)
11636 semantics for overriding, extending, and clearing lists of
11637 options. Closes bug 4748.
11640 Changes in version 0.2.3.17-beta - 2012-06-15
11641 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
11642 gets our TLS handshake back on track for being able to blend in with
11643 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
11644 with Vidalia, and otherwise continues to get us closer to a release
11648 - Enable gcc and ld hardening by default. Resolves ticket 5210.
11649 - Update TLS cipher list to match Firefox 8 and later. Resolves
11651 - Implement the client side of proposal 198: remove support for
11652 clients falsely claiming to support standard ciphersuites that
11653 they can actually provide. As of modern OpenSSL versions, it's not
11654 necessary to fake any standard ciphersuite, and doing so prevents
11655 us from using better ciphersuites in the future, since servers
11656 can't know whether an advertised ciphersuite is really supported or
11657 not. Some hosts -- notably, ones with very old versions of OpenSSL
11658 or where OpenSSL has been built with ECC disabled -- will stand
11659 out because of this change; TBB users should not be affected.
11662 - Change the default value for DynamicDHGroups (introduced in
11663 0.2.3.9-alpha) to 0. This feature can make Tor relays less
11664 identifiable by their use of the mod_ssl DH group, but at
11665 the cost of some usability (#4721) and bridge tracing (#6087)
11666 regressions. Resolves ticket 5598.
11667 - Send a CRLF at the end of each STATUS_* control protocol event. This
11668 bug tickled a bug in Vidalia which would make it freeze. Fixes
11669 bug 6094; bugfix on 0.2.3.16-alpha.
11672 - Disable writing on marked-for-close connections when they are
11673 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
11674 bug 5263; bugfix on 0.0.2pre13, where we first added a special
11675 case for flushing marked connections.
11676 - Detect SSL handshake even when the initial attempt to write the
11677 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
11678 - Change the AllowDotExit rules so they should actually work.
11679 We now enforce AllowDotExit only immediately after receiving an
11680 address via SOCKS or DNSPort: other sources are free to provide
11681 .exit addresses after the resolution occurs. Fixes bug 3940;
11682 bugfix on 0.2.2.1-alpha.
11683 - Fix a (harmless) integer overflow in cell statistics reported by
11684 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
11685 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
11686 right places and never depends on the consensus parameters or
11687 computes adaptive timeouts when it is disabled. Fixes bug 5049;
11688 bugfix on 0.2.2.14-alpha.
11689 - When building Tor on Windows with -DUNICODE (not default), ensure
11690 that error messages, filenames, and DNS server names are always
11691 NUL-terminated when we convert them to a single-byte encoding.
11692 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
11693 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
11694 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
11695 - Fix an edge case where TestingTorNetwork is set but the authorities
11696 and relays all have an uptime of zero, where the private Tor network
11697 could briefly lack support for hidden services. Fixes bug 3886;
11698 bugfix on 0.2.2.18-alpha.
11699 - Correct the manpage's descriptions for the default values of
11700 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
11702 - Fix the documentation for the --hush and --quiet command line
11703 options, which changed their behavior back in 0.2.3.3-alpha.
11704 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
11708 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
11709 more information to it, so that we can track it down in case it
11710 returns again. Mitigates bug 5235.
11711 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
11712 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
11713 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
11714 - Warn the user when HTTPProxy, but no other proxy type, is
11715 configured. This can cause surprising behavior: it doesn't send
11716 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
11717 directory traffic only. Resolves ticket 4663.
11718 - Issue a notice if a guard completes less than 40% of your circuits.
11719 Threshold is configurable by torrc option PathBiasNoticeRate and
11720 consensus parameter pb_noticepct. There is additional, off-by-
11721 default code to disable guards which fail too many circuits.
11722 Addresses ticket 5458.
11723 - Update to the June 6 2012 Maxmind GeoLite Country database.
11725 o Code simplifications and refactoring:
11726 - Remove validate_pluggable_transports_config(): its warning
11727 message is now handled by connection_or_connect().
11730 Changes in version 0.2.2.37 - 2012-06-06
11731 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
11732 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11736 - Work around a bug in OpenSSL that broke renegotiation with TLS
11737 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11738 the v2 Tor connection protocol when both sides were using OpenSSL
11739 1.0.1 would fail. Resolves ticket 6033.
11740 - When waiting for a client to renegotiate, don't allow it to add
11741 any bytes to the input buffer. This fixes a potential DoS issue.
11742 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11743 - Fix an edge case where if we fetch or publish a hidden service
11744 descriptor, we might build a 4-hop circuit and then use that circuit
11745 for exiting afterwards -- even if the new last hop doesn't obey our
11746 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11749 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11750 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11753 - Tell GCC and Clang to check for any errors in format strings passed
11754 to the tor_v*(print|scan)f functions.
11757 Changes in version 0.2.3.16-alpha - 2012-06-05
11758 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
11759 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
11760 currently). It also fixes a variety of smaller bugs and other cleanups
11761 that get us closer to a release candidate.
11763 o Major bugfixes (general):
11764 - Work around a bug in OpenSSL that broke renegotiation with TLS
11765 1.1 and TLS 1.2. Without this workaround, all attempts to speak
11766 the v2 Tor connection protocol when both sides were using OpenSSL
11767 1.0.1 would fail. Resolves ticket 6033.
11768 - When waiting for a client to renegotiate, don't allow it to add
11769 any bytes to the input buffer. This fixes a potential DoS issue.
11770 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
11771 - Pass correct OR address to managed proxies (like obfsproxy),
11772 even when ORListenAddress is used. Fixes bug 4865; bugfix on
11774 - The advertised platform of a router now includes only its operating
11775 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
11776 service pack level (for Windows) or its CPU architecture (for Unix).
11777 We also no longer include the "git-XYZ" tag in the version. Resolves
11780 o Major bugfixes (clients):
11781 - If we are unable to find any exit that supports our predicted ports,
11782 stop calling them predicted, so that we don't loop and build
11783 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
11784 which introduced predicted ports.
11785 - Fix an edge case where if we fetch or publish a hidden service
11786 descriptor, we might build a 4-hop circuit and then use that circuit
11787 for exiting afterwards -- even if the new last hop doesn't obey our
11788 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
11789 - Check at each new consensus whether our entry guards were picked
11790 long enough ago that we should rotate them. Previously, we only
11791 did this check at startup, which could lead to us holding a guard
11792 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
11793 - When fetching a bridge descriptor from a bridge authority,
11794 always do so anonymously, whether we have been able to open
11795 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
11796 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
11797 but we'll need to wait for bug 6010 before it's actually usable.
11799 o Major bugfixes (directory authorities):
11800 - When computing weight parameters, behave more robustly in the
11801 presence of a bad bwweightscale value. Previously, the authorities
11802 would crash if they agreed on a sufficiently broken weight_scale
11803 value: now, they use a reasonable default and carry on. Partial
11804 fix for 5786; bugfix on 0.2.2.17-alpha.
11805 - Check more thoroughly to prevent a rogue authority from
11806 double-voting on any consensus directory parameter. Previously,
11807 authorities would crash in this case if the total number of
11808 votes for any parameter exceeded the number of active voters,
11809 but would let it pass otherwise. Partial fix for bug 5786; bugfix
11813 - Rate-limit log messages when asked to connect anonymously to
11814 a private address. When these hit, they tended to hit fast and
11815 often. Also, don't bother trying to connect to addresses that we
11816 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
11817 reply makes us think we have been lied to, even when the address the
11818 client tried to connect to was "localhost." Resolves ticket 2822.
11819 - Allow packagers to insert an extra string in server descriptor
11820 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
11821 Resolves the rest of ticket 2988.
11822 - Raise the threshold of server descriptors needed (75%) and exit
11823 server descriptors needed (50%) before we will declare ourselves
11824 bootstrapped. This will make clients start building circuits a
11825 little later, but makes the initially constructed circuits less
11826 skewed and less in conflict with further directory fetches. Fixes
11828 - Close any connection that sends unrecognized junk before the
11829 handshake. Solves an issue noted in bug 4369.
11830 - Improve log messages about managed transports. Resolves ticket 5070.
11831 - Tag a bridge's descriptor as "never to be sent unencrypted".
11832 This shouldn't matter, since bridges don't open non-anonymous
11833 connections to the bridge authority and don't allow unencrypted
11834 directory connections from clients, but we might as well make
11835 sure. Closes bug 5139.
11836 - Expose our view of whether we have gone dormant to the controller,
11837 via a new "GETINFO dormant" value. Torbutton and other controllers
11838 can use this to avoid doing periodic requests through Tor while
11839 it's dormant (bug 4718). Fixes bug 5954.
11840 - Tell GCC and Clang to check for any errors in format strings passed
11841 to the tor_v*(print|scan)f functions.
11842 - Update to the May 1 2012 Maxmind GeoLite Country database.
11844 o Minor bugfixes (already included in 0.2.2.36):
11845 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
11846 Fixes bug 5346; bugfix on 0.0.8pre3.
11847 - Correct parsing of certain date types in parse_http_time().
11848 Without this patch, If-Modified-Since would behave
11849 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
11850 Esteban Manchado Velázques.
11851 - Make our number-parsing functions always treat too-large values
11852 as an error, even when those values exceed the width of the
11853 underlying type. Previously, if the caller provided these
11854 functions with minima or maxima set to the extreme values of the
11855 underlying integer type, these functions would return those
11856 values on overflow rather than treating overflow as an error.
11857 Fixes part of bug 5786; bugfix on 0.0.9.
11858 - If we hit the error case where routerlist_insert() replaces an
11859 existing (old) server descriptor, make sure to remove that
11860 server descriptor from the old_routers list. Fix related to bug
11861 1776. Bugfix on 0.2.2.18-alpha.
11862 - Clarify the behavior of MaxCircuitDirtiness with hidden service
11863 circuits. Fixes issue 5259.
11865 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
11866 - Prevent a null-pointer dereference when receiving a data cell
11867 for a nonexistent stream when the circuit in question has an
11868 empty deliver window. We don't believe this is triggerable,
11869 since we don't currently allow deliver windows to become empty,
11870 but the logic is tricky enough that it's better to make the code
11871 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
11872 - Fix a memory leak when trying to launch a DNS request when the
11873 network is disabled or the nameservers are unconfigurable. Fixes
11874 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
11875 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
11876 - Don't hold a Windows file handle open for every file mapping;
11877 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
11879 - Avoid O(n^2) performance characteristics when parsing a large
11880 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
11881 - Format more doubles with %f, not %lf. Patch from grarpamp to make
11882 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
11884 - Make our replacement implementation of strtok_r() compatible with
11885 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
11886 bugfix on 0.2.2.1-alpha.
11887 - Fix a NULL-pointer dereference on a badly formed
11888 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
11889 bugfix on 0.2.2.9-alpha.
11890 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
11891 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
11892 - Defensively refactor rend_mid_rendezvous() so that protocol
11893 violations and length checks happen in the beginning. Fixes
11895 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
11896 that IPv6 stuff will compile on MSVC, and compilation issues
11897 will be easier to track down. Fixes bug 5861.
11899 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
11900 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
11901 resource exhaustion, so that clients can adjust their load to
11902 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
11903 started using END_STREAM_REASON_RESOURCELIMIT.
11904 - Don't check for whether the address we're using for outbound
11905 connections has changed until after the outbound connection has
11906 completed. On Windows, getsockname() doesn't succeed until the
11907 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
11908 - If the configuration tries to set MyFamily on a bridge, refuse to
11909 do so, and warn about the security implications. Fixes bug 4657;
11910 bugfix on 0.2.0.3-alpha.
11911 - If the client fails to set a reasonable set of ciphersuites
11912 during its v2 handshake renegotiation, allow the renegotiation to
11913 continue nevertheless (i.e. send all the required certificates).
11914 Fixes bug 4591; bugfix on 0.2.0.20-rc.
11915 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
11916 option is set to 0 (which Vidalia version 0.2.16 now does when
11917 a SAVECONF attempt fails), perform other actions that SIGHUP
11918 usually causes (like reopening the logs). Fixes bug 5095; bugfix
11920 - If we fail to write a microdescriptor to the disk cache, do not
11921 continue replacing the old microdescriptor file. Fixes bug 2954;
11922 bugfix on 0.2.2.6-alpha.
11923 - Exit nodes don't need to fetch certificates for authorities that
11924 they don't recognize; only directory authorities, bridges,
11925 and caches need to do that. Fixes part of bug 2297; bugfix on
11927 - Correctly handle checking the permissions on the parent
11928 directory of a control socket in the root directory. Bug found
11929 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
11931 - When told to add a bridge with the same digest as a preexisting
11932 bridge but a different addr:port, change the addr:port as
11933 requested. Previously we would not notice the change. Fixes half
11934 of bug 5603; fix on 0.2.2.26-beta.
11935 - End AUTHCHALLENGE error messages (in the control protocol) with
11936 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
11938 o Minor bugfixes (on 0.2.3.x):
11939 - Turn an assertion (that the number of handshakes received as a
11940 server is not < 1) into a warning. Fixes bug 4873; bugfix on
11942 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
11943 we had reversed them when the answer was cached.) Fixes bug
11944 5723; bugfix on 0.2.3.1-alpha.
11945 - Work correctly on Linux systems with accept4 support advertised in
11946 their headers, but without accept4 support in the kernel. Fix
11947 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
11948 - When told to add a bridge with the same addr:port as a preexisting
11949 bridge but a different transport, change the transport as
11950 requested. Previously we would not notice the change. Fixes half
11951 of bug 5603; fix on 0.2.3.2-alpha.
11952 - Avoid a "double-reply" warning when replying to a SOCKS request
11953 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
11954 bugfix on 0.2.3.4-alpha.
11955 - Fix a bug where a bridge authority crashes if it has seen no
11956 directory requests when it's time to write statistics to disk.
11957 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
11959 - Don't try to open non-control listeners when DisableNetwork is set.
11960 Previously, we'd open all listeners, then immediately close them.
11961 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
11962 - Don't abort the managed proxy protocol if the managed proxy
11963 sends us an unrecognized line; ignore it instead. Fixes bug
11964 5910; bugfix on 0.2.3.9-alpha.
11965 - Fix a compile warning in crypto.c when compiling with clang 3.1.
11966 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
11967 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
11968 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
11969 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
11970 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
11971 - Resolve numerous small warnings and build issues with MSVC. Resolves
11974 o Documentation fixes:
11975 - Improve the manual's documentation for the NT Service command-line
11976 options. Addresses ticket 3964.
11977 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
11978 - Document the changes to the ORPort and DirPort options, and the
11979 fact that {OR/Dir}ListenAddress is now unnecessary (and
11980 therefore deprecated). Resolves ticket 5597.
11983 - Remove the torrc.bridge file: we don't use it for anything, and
11984 it had become badly desynchronized from torrc.sample. Resolves
11988 Changes in version 0.2.2.36 - 2012-05-24
11989 Tor 0.2.2.36 updates the addresses for two of the eight directory
11990 authorities, fixes some potential anonymity and security issues,
11991 and fixes several crash bugs.
11993 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
11994 known flaws, and nobody should be using them. You should upgrade. If
11995 you're using a Linux or BSD and its packages are obsolete, stop using
11996 those packages and upgrade anyway.
11998 o Directory authority changes:
11999 - Change IP address for maatuska (v3 directory authority).
12000 - Change IP address for ides (v3 directory authority), and rename
12004 - When building or running with any version of OpenSSL earlier
12005 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
12006 versions have a bug (CVE-2011-4576) in which their block cipher
12007 padding includes uninitialized data, potentially leaking sensitive
12008 information to any peer with whom they make a SSLv3 connection. Tor
12009 does not use SSL v3 by default, but a hostile client or server
12010 could force an SSLv3 connection in order to gain information that
12011 they shouldn't have been able to get. The best solution here is to
12012 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12013 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12014 to make sure that the bug can't happen.
12015 - Never use a bridge or a controller-supplied node as an exit, even
12016 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12017 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12018 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12019 - Only build circuits if we have a sufficient threshold of the total
12020 descriptors that are marked in the consensus with the "Exit"
12021 flag. This mitigates an attack proposed by wanoskarnet, in which
12022 all of a client's bridges collude to restrict the exit nodes that
12023 the client knows about. Fixes bug 5343.
12024 - Provide controllers with a safer way to implement the cookie
12025 authentication mechanism. With the old method, if another locally
12026 running program could convince a controller that it was the Tor
12027 process, then that program could trick the controller into telling
12028 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12029 authentication method uses a challenge-response approach to prevent
12030 this attack. Fixes bug 5185; implements proposal 193.
12033 - Avoid logging uninitialized data when unable to decode a hidden
12034 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12035 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12036 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12038 - Fix builds when the path to sed, openssl, or sha1sum contains
12039 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12041 - Correct our replacements for the timeradd() and timersub() functions
12042 on platforms that lack them (for example, Windows). The timersub()
12043 function is used when expiring circuits, while timeradd() is
12044 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12045 bugfix on 0.2.2.24-alpha.
12046 - Fix the SOCKET_OK test that we use to tell when socket
12047 creation fails so that it works on Win64. Fixes part of bug 4533;
12048 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12051 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
12052 Fixes bug 5346; bugfix on 0.0.8pre3.
12053 - Make our number-parsing functions always treat too-large values
12054 as an error, even when those values exceed the width of the
12055 underlying type. Previously, if the caller provided these
12056 functions with minima or maxima set to the extreme values of the
12057 underlying integer type, these functions would return those
12058 values on overflow rather than treating overflow as an error.
12059 Fixes part of bug 5786; bugfix on 0.0.9.
12060 - Older Linux kernels erroneously respond to strange nmap behavior
12061 by having accept() return successfully with a zero-length
12062 socket. When this happens, just close the connection. Previously,
12063 we would try harder to learn the remote address: but there was
12064 no such remote address to learn, and our method for trying to
12065 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12066 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12067 - Correct parsing of certain date types in parse_http_time().
12068 Without this patch, If-Modified-Since would behave
12069 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
12070 Esteban Manchado Velázques.
12071 - Change the BridgePassword feature (part of the "bridge community"
12072 design, which is not yet implemented) to use a time-independent
12073 comparison. The old behavior might have allowed an adversary
12074 to use timing to guess the BridgePassword value. Fixes bug 5543;
12075 bugfix on 0.2.0.14-alpha.
12076 - Detect and reject certain misformed escape sequences in
12077 configuration values. Previously, these values would cause us
12078 to crash if received in a torrc file or over an authenticated
12079 control port. Bug found by Esteban Manchado Velázquez, and
12080 independently by Robert Connolly from Matta Consulting who further
12081 noted that it allows a post-authentication heap overflow. Patch
12082 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12083 bugfix on 0.2.0.16-alpha.
12084 - Fix a compile warning when using the --enable-openbsd-malloc
12085 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12086 - During configure, detect when we're building with clang version
12087 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12088 CFLAGS. clang doesn't support them yet.
12089 - When sending an HTTP/1.1 proxy request, include a Host header.
12090 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12091 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
12092 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
12093 - If we hit the error case where routerlist_insert() replaces an
12094 existing (old) server descriptor, make sure to remove that
12095 server descriptor from the old_routers list. Fix related to bug
12096 1776. Bugfix on 0.2.2.18-alpha.
12098 o Minor bugfixes (documentation and log messages):
12099 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12100 Fixes bug 4856; bugfix on Tor 0.0.6.
12101 - Update "ClientOnly" man page entry to explain that there isn't
12102 really any point to messing with it. Resolves ticket 5005.
12103 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12104 directory authority option (introduced in Tor 0.2.2.34).
12105 - Downgrade the "We're missing a certificate" message from notice
12106 to info: people kept mistaking it for a real problem, whereas it
12107 is seldom the problem even when we are failing to bootstrap. Fixes
12108 bug 5067; bugfix on 0.2.0.10-alpha.
12109 - Correctly spell "connect" in a log message on failure to create a
12110 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
12111 - Clarify the behavior of MaxCircuitDirtiness with hidden service
12112 circuits. Fixes issue 5259.
12115 - Directory authorities now reject versions of Tor older than
12116 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12117 inclusive. These versions accounted for only a small fraction of
12118 the Tor network, and have numerous known security issues. Resolves
12120 - Update to the May 1 2012 Maxmind GeoLite Country database.
12123 - When sending or relaying a RELAY_EARLY cell, we used to convert
12124 it to a RELAY cell if the connection was using the v1 link
12125 protocol. This was a workaround for older versions of Tor, which
12126 didn't handle RELAY_EARLY cells properly. Now that all supported
12127 versions can handle RELAY_EARLY cells, and now that we're enforcing
12128 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12129 remove this workaround. Addresses bug 4786.
12132 Changes in version 0.2.3.15-alpha - 2012-04-30
12133 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
12134 the development branch build on Windows again.
12136 o Minor bugfixes (on 0.2.2.x and earlier):
12137 - Make sure that there are no unhandled pending TLS errors before
12138 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
12139 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
12140 Bugfix on 0.1.0.5-rc; fixes bug 4528.
12141 - Fix an assert that directory authorities could trigger on sighup
12142 during some configuration state transitions. We now don't treat
12143 it as a fatal error when the new descriptor we just generated in
12144 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
12145 - After we pick a directory mirror, we would refuse to use it if
12146 it's in our ExcludeExitNodes list, resulting in mysterious failures
12147 to bootstrap for people who just wanted to avoid exiting from
12148 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
12149 - When building with --enable-static-tor on OpenBSD, do not
12150 erroneously attempt to link -lrt. Fixes bug 5103.
12152 o Minor bugfixes (on 0.2.3.x):
12153 - When Tor is built with kernel headers from a recent (last few
12154 years) Linux kernel, do not fail to run on older (pre-2.6.28
12155 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
12156 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
12157 and 0.2.3.12-alpha.
12158 - Fix compilation with miniupnpc version 1.6; patch from
12159 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
12160 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
12161 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
12162 - Fix compilation on platforms without unistd.h, or where environ
12163 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
12166 - Directory authorities are now a little more lenient at accepting
12167 older router descriptors, or newer router descriptors that don't
12168 make big changes. This should help ameliorate past and future
12169 issues where routers think they have uploaded valid descriptors,
12170 but the authorities don't think so. Fix for ticket 2479.
12171 - Make the code that clients use to detect an address change be
12172 IPv6-aware, so that it won't fill clients' logs with error
12173 messages when trying to get the IPv4 address of an IPv6
12174 connection. Implements ticket 5537.
12176 o Removed features:
12177 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
12178 authorities needed to use it for a while to keep the network working
12179 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
12180 that was six months ago. As of now, it should no longer be needed
12184 Changes in version 0.2.3.14-alpha - 2012-04-23
12185 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
12186 candidate. It also dramatically speeds up AES: fast relays should
12187 consider switching to the newer OpenSSL library.
12189 o Directory authority changes:
12190 - Change IP address for ides (v3 directory authority), and rename
12194 - Avoid logging uninitialized data when unable to decode a hidden
12195 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
12196 - Avoid a client-side assertion failure when receiving an INTRODUCE2
12197 cell on a general purpose circuit. Fixes bug 5644; bugfix on
12199 - If authorities are unable to get a v2 consensus document from other
12200 directory authorities, they no longer fall back to fetching
12201 them from regular directory caches. Fixes bug 5635; bugfix on
12202 0.2.2.26-beta, where routers stopped downloading v2 consensus
12203 documents entirely.
12204 - When we start a Tor client with a normal consensus already cached,
12205 be willing to download a microdescriptor consensus. Fixes bug 4011;
12206 fix on 0.2.3.1-alpha.
12208 o Major features (performance):
12209 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
12210 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
12211 vectorized AES implementations as appropriate. These can be much,
12212 much faster than other AES implementations.
12214 o Minor bugfixes (0.2.2.x and earlier):
12215 - Don't launch more than 10 service-side introduction-point circuits
12216 for a hidden service in five minutes. Previously, we would consider
12217 launching more introduction-point circuits if at least one second
12218 had passed without any introduction-point circuits failing. Fixes
12219 bug 4607; bugfix on 0.0.7pre1.
12220 - Change the BridgePassword feature (part of the "bridge community"
12221 design, which is not yet implemented) to use a time-independent
12222 comparison. The old behavior might have allowed an adversary
12223 to use timing to guess the BridgePassword value. Fixes bug 5543;
12224 bugfix on 0.2.0.14-alpha.
12225 - Enforce correct return behavior of tor_vsscanf() when the '%%'
12226 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
12227 - When sending an HTTP/1.1 proxy request, include a Host header.
12228 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
12229 - Don't log that we have "decided to publish new relay descriptor"
12230 unless we are actually publishing a descriptor. Fixes bug 3942;
12231 bugfix on 0.2.2.28-beta.
12233 o Minor bugfixes (0.2.3.x):
12234 - Fix a bug where a bridge authority crashes (on a failed assert)
12235 if it has seen no directory requests when it's time to write
12236 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
12237 - Fix bug stomping on ORPort option NoListen and ignoring option
12238 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
12239 - In the testsuite, provide a large enough buffer in the tor_sscanf
12240 unit test. Otherwise we'd overrun that buffer and crash during
12241 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
12243 - Make sure we create the keys directory if it doesn't exist and we're
12244 about to store the dynamic Diffie-Hellman parameters. Fixes bug
12245 5572; bugfix on 0.2.3.13-alpha.
12246 - Fix a small memory leak when trying to decode incorrect base16
12247 authenticator during SAFECOOKIE authentication. Found by
12248 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
12251 - Add more information to a log statement that might help track down
12252 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
12253 non-IP address" messages (or any Bug messages, for that matter!),
12254 please let us know about it.
12255 - Relays now understand an IPv6 address when they get one from a
12256 directory server. Resolves ticket 4875.
12257 - Resolve IPv6 addresses in bridge and entry statistics to country
12258 code "??" which means we at least count them. Resolves ticket 5053;
12259 improves on 0.2.3.9-alpha.
12260 - Update to the April 3 2012 Maxmind GeoLite Country database.
12261 - Begin a doc/state-contents.txt file to explain the contents of
12262 the Tor state file. Fixes bug 2987.
12264 o Default torrc changes:
12265 - Stop listing "socksport 9050" in torrc.sample. We open a socks
12266 port on 9050 by default anyway, so this should not change anything
12268 - Stop mentioning the deprecated *ListenAddress options in
12269 torrc.sample. Fixes bug 5438.
12270 - Document unit of bandwidth related options in sample torrc.
12273 o Removed features:
12274 - The "torify" script no longer supports the "tsocks" socksifier
12275 tool, since tsocks doesn't support DNS and UDP right for Tor.
12276 Everyone should be using torsocks instead. Fixes bugs 3530 and
12277 5180. Based on a patch by "ugh".
12279 o Code refactoring:
12280 - Change the symmetric cipher interface so that creating and
12281 initializing a stream cipher are no longer separate functions.
12282 - Remove all internal support for unpadded RSA. We never used it, and
12283 it would be a bad idea to start.
12286 Changes in version 0.2.3.13-alpha - 2012-03-26
12287 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
12288 in managed pluggable transports, as well as providing other cleanups
12289 that get us closer to a release candidate.
12291 o Directory authority changes:
12292 - Change IP address for maatuska (v3 directory authority).
12295 - Provide controllers with a safer way to implement the cookie
12296 authentication mechanism. With the old method, if another locally
12297 running program could convince a controller that it was the Tor
12298 process, then that program could trick the controller into telling
12299 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
12300 authentication method uses a challenge-response approach to prevent
12301 this attack. Fixes bug 5185, implements proposal 193.
12302 - Never use a bridge or a controller-supplied node as an exit, even
12303 if its exit policy allows it. Found by wanoskarnet. Fixes bug
12304 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
12305 and 0.2.0.3-alpha (for bridge-purpose descriptors).
12306 - Only build circuits if we have a sufficient threshold of the total
12307 descriptors that are marked in the consensus with the "Exit"
12308 flag. This mitigates an attack proposed by wanoskarnet, in which
12309 all of a client's bridges collude to restrict the exit nodes that
12310 the client knows about. Fixes bug 5343.
12312 o Major bugfixes (on Tor 0.2.3.x):
12313 - Avoid an assert when managed proxies like obfsproxy are configured,
12314 and we receive HUP signals or setconf attempts too rapidly. This
12315 situation happens most commonly when Vidalia tries to attach to
12316 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
12317 bugfix on 0.2.3.6-alpha.
12318 - Fix a relay-side pluggable transports bug where managed proxies were
12319 unreachable from the Internet, because Tor asked them to bind on
12320 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
12321 - Stop discarding command-line arguments when TestingTorNetwork
12322 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
12323 0.2.3.9-alpha, where task 4552 added support for two layers of
12325 - Resume allowing the unit tests to run in gdb. This was accidentally
12326 made impossible when the DisableDebuggerAttachment option was
12327 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
12328 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
12329 0.2.3.11-alpha. Reported by Anthony G. Basile.
12331 o Minor bugfixes (on 0.2.2.x and earlier):
12332 - Ensure we don't cannibalize circuits that are longer than three hops
12333 already, so we don't end up making circuits with 5 or more
12334 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
12335 0.1.0.1-rc which introduced cannibalization.
12336 - Detect and reject certain misformed escape sequences in
12337 configuration values. Previously, these values would cause us
12338 to crash if received in a torrc file or over an authenticated
12339 control port. Bug found by Esteban Manchado Velázquez, and
12340 independently by Robert Connolly from Matta Consulting who further
12341 noted that it allows a post-authentication heap overflow. Patch
12342 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
12343 bugfix on 0.2.0.16-alpha.
12344 - Fix a compile warning when using the --enable-openbsd-malloc
12345 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
12346 - Directory caches no longer refuse to clean out descriptors because
12347 of missing v2 networkstatus documents, unless they're configured
12348 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
12349 0.2.2.26-beta. Patch by Daniel Bryg.
12350 - Update to the latest version of the tinytest unit testing framework.
12351 This includes a couple of bugfixes that can be relevant for
12352 running forked unit tests on Windows, and removes all reserved
12355 o Minor bugfixes (on 0.2.3.x):
12356 - On a failed pipe() call, don't leak file descriptors. Fixes bug
12357 4296; bugfix on 0.2.3.1-alpha.
12358 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
12359 until after we have received a CERTS cell. Fixes bug 4361; bugfix
12360 on 0.2.3.6-alpha. Patch by "frosty".
12361 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
12362 option, so that the IP stack doesn't decide to use it for IPv4
12363 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
12364 - Ensure that variables set in Tor's environment cannot override
12365 environment variables that Tor passes to a managed
12366 pluggable-transport proxy. Previously, Tor would pass every
12367 variable in its environment to managed proxies along with the new
12368 ones, in such a way that on many operating systems, the inherited
12369 environment variables would override those which Tor tried to
12370 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
12371 bugfix on 0.2.3.9-alpha for Windows.
12374 - A wide variety of new unit tests by Esteban Manchado Velázquez.
12375 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
12376 - Update to the March 6 2012 Maxmind GeoLite Country database.
12379 Changes in version 0.2.3.12-alpha - 2012-02-13
12380 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
12381 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
12382 when Tor is configured to use a pluggable transport like obfsproxy.
12385 - Fix builds when the path to sed, openssl, or sha1sum contains
12386 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
12388 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
12389 connections. This change should allow busy exit relays to stop
12390 running out of available sockets as quickly. Fixes bug 4950;
12391 bugfix on 0.2.2.26-beta.
12392 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
12393 would ask the bridge for microdescriptors, which are only supported
12394 in 0.2.3.x, and then fail to bootstrap when it didn't get the
12395 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
12396 - Properly set up obfsproxy's environment when in managed mode. The
12397 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
12398 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
12399 5076 and 5082; bugfix on 0.2.3.6-alpha.
12402 - Use the dead_strip option when building Tor on OS X. This reduces
12403 binary size by almost 19% when linking openssl and libevent
12404 statically, which we do for Tor Browser Bundle.
12405 - Fix broken URLs in the sample torrc file, and tell readers about
12406 the OutboundBindAddress, ExitPolicyRejectPrivate, and
12407 PublishServerDescriptor options. Addresses bug 4652.
12408 - Update to the February 7 2012 Maxmind GeoLite Country database.
12411 - Downgrade the "We're missing a certificate" message from notice
12412 to info: people kept mistaking it for a real problem, whereas it
12413 is seldom the problem even when we are failing to bootstrap. Fixes
12414 bug 5067; bugfix on 0.2.0.10-alpha.
12415 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
12416 managed pluggable transport server proxy's environment.
12417 Previously, we would put it there, even though Tor doesn't
12418 implement an 'extended server port' yet, and even though Tor
12419 almost certainly isn't listening at that address. For now, we set
12420 it to an empty string to avoid crashing older obfsproxies. Bugfix
12422 - Log the heartbeat message every HeartbeatPeriod seconds, not every
12423 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
12424 0.2.3.1-alpha. Bug reported by Scott Bennett.
12425 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
12426 bugfix on 0.2.3.11-alpha.
12427 - Update "ClientOnly" man page entry to explain that there isn't
12428 really any point to messing with it. Resolves ticket 5005.
12429 - Use the correct CVE number for CVE-2011-4576 in our comments and
12430 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
12433 o Code simplifications and refactoring:
12434 - Use the _WIN32 macro throughout our code to detect Windows.
12435 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
12439 Changes in version 0.2.3.11-alpha - 2012-01-22
12440 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
12441 the last step of the plan to limit maximum circuit length, includes
12442 a wide variety of hidden service performance and correctness fixes,
12443 works around an OpenSSL security flaw if your distro is too stubborn
12444 to upgrade, and fixes a bunch of smaller issues.
12447 - Now that Tor 0.2.0.x is completely deprecated, enable the final
12448 part of "Proposal 110: Avoiding infinite length circuits" by
12449 refusing all circuit-extend requests that do not use a relay_early
12450 cell. This change helps Tor resist a class of denial-of-service
12451 attacks by limiting the maximum circuit length.
12452 - Adjust the number of introduction points that a hidden service
12453 will try to maintain based on how long its introduction points
12454 remain in use and how many introductions they handle. Fixes
12456 - Try to use system facilities for enumerating local interface
12457 addresses, before falling back to our old approach (which was
12458 binding a UDP socket, and calling getsockname() on it). That
12459 approach was scaring OS X users whose draconian firewall
12460 software warned about binding to UDP sockets, regardless of
12461 whether packets were sent. Now we try to use getifaddrs(),
12462 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
12463 system supports. Resolves ticket 1827.
12465 o Major security workaround:
12466 - When building or running with any version of OpenSSL earlier
12467 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
12468 versions have a bug (CVE-2011-4576) in which their block cipher
12469 padding includes uninitialized data, potentially leaking sensitive
12470 information to any peer with whom they make a SSLv3 connection. Tor
12471 does not use SSL v3 by default, but a hostile client or server
12472 could force an SSLv3 connection in order to gain information that
12473 they shouldn't have been able to get. The best solution here is to
12474 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
12475 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
12476 to make sure that the bug can't happen.
12479 - Fix the SOCKET_OK test that we use to tell when socket
12480 creation fails so that it works on Win64. Fixes part of bug 4533;
12481 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
12482 - Correct our replacements for the timeradd() and timersub() functions
12483 on platforms that lack them (for example, Windows). The timersub()
12484 function is used when expiring circuits, while timeradd() is
12485 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
12486 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
12487 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
12488 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
12489 bug at runtime, not compile time, because some distributions hack
12490 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
12491 on 0.2.3.9-alpha. Found by Pascal.
12493 o Minor features (controller):
12494 - Use absolute path names when reporting the torrc filename in the
12495 control protocol, so a controller can more easily find the torrc
12496 file. Resolves bug 1101.
12497 - Extend the control protocol to report flags that control a circuit's
12498 path selection in CIRC events and in replies to 'GETINFO
12499 circuit-status'. Implements part of ticket 2411.
12500 - Extend the control protocol to report the hidden service address
12501 and current state of a hidden-service-related circuit in CIRC
12502 events and in replies to 'GETINFO circuit-status'. Implements part
12504 - When reporting the path to the cookie file to the controller,
12505 give an absolute path. Resolves ticket 4881.
12506 - Allow controllers to request an event notification whenever a
12507 circuit is cannibalized or its purpose is changed. Implements
12508 part of ticket 3457.
12509 - Include the creation time of a circuit in CIRC and CIRC2
12510 control-port events and the list produced by the 'GETINFO
12511 circuit-status' control-port command.
12513 o Minor features (directory authorities):
12514 - Directory authorities now reject versions of Tor older than
12515 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
12516 inclusive. These versions accounted for only a small fraction of
12517 the Tor network, and have numerous known security issues. Resolves
12519 - Authority operators can now vote for all relays in a given
12520 set of countries to be BadDir/BadExit/Invalid/Rejected.
12521 - Provide two consensus parameters (FastFlagMinThreshold and
12522 FastFlagMaxThreshold) to control the range of allowable bandwidths
12523 for the Fast directory flag. These allow authorities to run
12524 experiments on appropriate requirements for being a "Fast" node.
12525 The AuthDirFastGuarantee config value still applies. Implements
12527 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
12528 directory authority option (introduced in Tor 0.2.2.34).
12530 o Minor features (other):
12531 - Don't disable the DirPort when we cannot exceed our AccountingMax
12532 limit during this interval because the effective bandwidthrate is
12533 low enough. This is useful in a situation where AccountMax is only
12534 used as an additional safeguard or to provide statistics.
12535 - Prepend an informative header to generated dynamic_dh_params files.
12536 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
12537 EntryNodes will have no effect. Resolves issue 2571.
12538 - Log more useful messages when we fail to disable debugger
12540 - Log which authority we're missing votes from when we go to fetch
12541 them from the other auths.
12542 - Log (at debug level) whenever a circuit's purpose is changed.
12543 - Add missing documentation for the MaxClientCircuitsPending,
12544 UseMicrodescriptors, UserspaceIOCPBuffers, and
12545 _UseFilteringSSLBufferevents options, all introduced during
12546 the 0.2.3.x series.
12547 - Update to the January 3 2012 Maxmind GeoLite Country database.
12549 o Minor bugfixes (hidden services):
12550 - Don't close hidden service client circuits which have almost
12551 finished connecting to their destination when they reach
12552 the normal circuit-build timeout. Previously, we would close
12553 introduction circuits which are waiting for an acknowledgement
12554 from the introduction point, and rendezvous circuits which have
12555 been specified in an INTRODUCE1 cell sent to a hidden service,
12556 after the normal CBT. Now, we mark them as 'timed out', and launch
12557 another rendezvous attempt in parallel. This behavior change can
12558 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
12559 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
12560 - Don't close hidden-service-side rendezvous circuits when they
12561 reach the normal circuit-build timeout. This behavior change can
12562 be disabled using the new
12563 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
12564 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
12565 - Make sure we never mark the wrong rendezvous circuit as having
12566 had its introduction cell acknowleged by the introduction-point
12567 relay. Previously, when we received an INTRODUCE_ACK cell on a
12568 client-side hidden-service introduction circuit, we might have
12569 marked a rendezvous circuit other than the one we specified in
12570 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
12571 a warning message and interfered with the hidden service
12572 connection-establishment process. Fixes bug 4759; bugfix on
12573 0.2.3.3-alpha, when we added the stream-isolation feature which
12574 might cause Tor to open multiple rendezvous circuits for the same
12576 - Don't trigger an assertion failure when we mark a new client-side
12577 hidden-service introduction circuit for close during the process
12578 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
12581 o Minor bugfixes (log messages):
12582 - Correctly spell "connect" in a log message on failure to create a
12583 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
12585 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
12586 Fixes bug 4856; bugfix on Tor 0.0.6.
12587 - Fix the log message describing how we work around discovering
12588 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
12589 4837; bugfix on 0.2.2.9-alpha.
12590 - When logging about a disallowed .exit name, do not also call it
12591 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
12593 o Minor bugfixes (build fixes):
12594 - During configure, detect when we're building with clang version
12595 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
12596 CFLAGS. clang doesn't support them yet.
12597 - During configure, search for library containing cos function as
12598 libm lives in libcore on some platforms (BeOS/Haiku). Linking
12599 against libm was hard-coded before. Fixes the first part of bug
12600 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
12602 - Detect attempts to build Tor on (as yet hypothetical) versions
12603 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
12604 fix for bug 4533. Bugfix on 0.2.2.28-beta.
12605 - Preprocessor directives should not be put inside the arguments
12606 of a macro. This would break compilation with GCC releases prior
12607 to version 3.3. We would never recommend such an old GCC version,
12608 but it is apparently required for binary compatibility on some
12609 platforms (namely, certain builds of Haiku). Fixes the other part
12610 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
12613 o Minor bugfixes (other):
12614 - Older Linux kernels erroneously respond to strange nmap behavior
12615 by having accept() return successfully with a zero-length
12616 socket. When this happens, just close the connection. Previously,
12617 we would try harder to learn the remote address: but there was
12618 no such remote address to learn, and our method for trying to
12619 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
12620 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
12621 - Fix null-pointer access that could occur if TLS allocation failed.
12622 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
12623 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
12624 accidentally been reverted.
12625 - Fix our implementation of crypto_random_hostname() so it can't
12626 overflow on ridiculously large inputs. (No Tor version has ever
12627 provided this kind of bad inputs, but let's be correct in depth.)
12628 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
12629 - Find more places in the code that should have been testing for
12630 invalid sockets using the SOCKET_OK macro. Required for a fix
12631 for bug 4533. Bugfix on 0.2.2.28-beta.
12632 - Fix an assertion failure when, while running with bufferevents, a
12633 connection finishes connecting after it is marked for close, but
12634 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
12635 - test_util_spawn_background_ok() hardcoded the expected value
12636 for ENOENT to 2. This isn't portable as error numbers are
12637 platform specific, and particularly the hurd has ENOENT at
12638 0x40000002. Construct expected string at runtime, using the correct
12639 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
12640 - Reject attempts to disable DisableDebuggerAttachment while Tor is
12641 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
12642 - Use an appropriate-width type for sockets in tor-fw-helper on
12643 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
12646 - When sending or relaying a RELAY_EARLY cell, we used to convert
12647 it to a RELAY cell if the connection was using the v1 link
12648 protocol. This was a workaround for older versions of Tor, which
12649 didn't handle RELAY_EARLY cells properly. Now that all supported
12650 versions can handle RELAY_EARLY cells, and now that we're enforcing
12651 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
12652 remove this workaround. Addresses bug 4786.
12654 o Code simplifications and refactoring:
12655 - Use OpenSSL's built-in SSL_state_string_long() instead of our
12656 own homebrewed ssl_state_to_string() replacement. Patch from
12657 Emile Snyder. Fixes bug 4653.
12658 - Use macros to indicate OpenSSL versions, so we don't need to worry
12659 about accidental hexadecimal bit shifts.
12660 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
12662 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
12663 - Use the smartlist_add_asprintf() alias more consistently.
12664 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
12665 invalid value, rather than just -1.
12666 - Rename a handful of old identifiers, mostly related to crypto
12667 structures and crypto functions. By convention, our "create an
12668 object" functions are called "type_new()", our "free an object"
12669 functions are called "type_free()", and our types indicate that
12670 they are types only with a final "_t". But a handful of older
12671 types and functions broke these rules, with function names like
12672 "type_create" or "subsystem_op_type", or with type names like
12676 Changes in version 0.2.3.10-alpha - 2011-12-16
12677 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
12678 Tor's buffers code. Absolutely everybody should upgrade.
12680 The bug relied on an incorrect calculation when making data continuous
12681 in one of our IO buffers, if the first chunk of the buffer was
12682 misaligned by just the wrong amount. The miscalculation would allow an
12683 attacker to overflow a piece of heap-allocated memory. To mount this
12684 attack, the attacker would need to either open a SOCKS connection to
12685 Tor's SocksPort (usually restricted to localhost), or target a Tor
12686 instance configured to make its connections through a SOCKS proxy
12687 (which Tor does not do by default).
12689 Good security practice requires that all heap-overflow bugs should be
12690 presumed to be exploitable until proven otherwise, so we are treating
12691 this as a potential code execution attack. Please upgrade immediately!
12692 This bug does not affect bufferevents-based builds of Tor. Special
12693 thanks to "Vektor" for reporting this issue to us!
12695 This release also contains a few minor bugfixes for issues discovered
12699 - Fix a heap overflow bug that could occur when trying to pull
12700 data into the first chunk of a buffer, when that chunk had
12701 already had some data drained from it. Fixes CVE-2011-2778;
12702 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12705 - If we can't attach streams to a rendezvous circuit when we
12706 finish connecting to a hidden service, clear the rendezvous
12707 circuit's stream-isolation state and try to attach streams
12708 again. Previously, we cleared rendezvous circuits' isolation
12709 state either too early (if they were freshly built) or not at all
12710 (if they had been built earlier and were cannibalized). Bugfix on
12711 0.2.3.3-alpha; fixes bug 4655.
12712 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
12713 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
12714 - Fix an assertion failure when a relay with accounting enabled
12715 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
12718 - Update to the December 6 2011 Maxmind GeoLite Country database.
12721 Changes in version 0.2.2.35 - 2011-12-16
12722 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
12723 buffers code. Absolutely everybody should upgrade.
12725 The bug relied on an incorrect calculation when making data continuous
12726 in one of our IO buffers, if the first chunk of the buffer was
12727 misaligned by just the wrong amount. The miscalculation would allow an
12728 attacker to overflow a piece of heap-allocated memory. To mount this
12729 attack, the attacker would need to either open a SOCKS connection to
12730 Tor's SocksPort (usually restricted to localhost), or target a Tor
12731 instance configured to make its connections through a SOCKS proxy
12732 (which Tor does not do by default).
12734 Good security practice requires that all heap-overflow bugs should be
12735 presumed to be exploitable until proven otherwise, so we are treating
12736 this as a potential code execution attack. Please upgrade immediately!
12737 This bug does not affect bufferevents-based builds of Tor. Special
12738 thanks to "Vektor" for reporting this issue to us!
12740 Tor 0.2.2.35 also fixes several bugs in previous versions, including
12741 crash bugs for unusual configurations, and a long-term bug that
12742 would prevent Tor from starting on Windows machines with draconian
12745 With this release, we remind everyone that 0.2.0.x has reached its
12746 formal end-of-life. Those Tor versions have many known flaws, and
12747 nobody should be using them. You should upgrade -- ideally to the
12748 0.2.2.x series. If you're using a Linux or BSD and its packages are
12749 obsolete, stop using those packages and upgrade anyway.
12751 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
12752 longer receive support after some time in early 2012.
12755 - Fix a heap overflow bug that could occur when trying to pull
12756 data into the first chunk of a buffer, when that chunk had
12757 already had some data drained from it. Fixes CVE-2011-2778;
12758 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12759 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
12760 that it doesn't attempt to allocate a socketpair. This could cause
12761 some problems on Windows systems with overzealous firewalls. Fix for
12762 bug 4457; workaround for Libevent versions 2.0.1-alpha through
12764 - If we mark an OR connection for close based on a cell we process,
12765 don't process any further cells on it. We already avoid further
12766 reads on marked-for-close connections, but now we also discard the
12767 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
12768 which was the first version where we might mark a connection for
12769 close based on processing a cell on it.
12770 - Correctly sanity-check that we don't underflow on a memory
12771 allocation (and then assert) for hidden service introduction
12772 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12773 bugfix on 0.2.1.5-alpha.
12774 - Fix a memory leak when we check whether a hidden service
12775 descriptor has any usable introduction points left. Fixes bug
12776 4424. Bugfix on 0.2.2.25-alpha.
12777 - Don't crash when we're running as a relay and don't have a GeoIP
12778 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
12779 we've had in the 0.2.3.x branch already.
12780 - When running as a client, do not print a misleading (and plain
12781 wrong) log message that we're collecting "directory request"
12782 statistics: clients don't collect statistics. Also don't create a
12783 useless (because empty) stats file in the stats/ directory. Fixes
12784 bug 4353; bugfix on 0.2.2.34.
12787 - Detect failure to initialize Libevent. This fix provides better
12788 detection for future instances of bug 4457.
12789 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
12790 function. This was eating up hideously large amounts of time on some
12791 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
12792 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12793 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12795 - Don't warn about unused log_mutex in log.c when building with
12796 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
12797 0.1.0.6-rc which introduced --disable-threads.
12798 - When configuring, starting, or stopping an NT service, stop
12799 immediately after the service configuration attempt has succeeded
12800 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
12801 - When sending a NETINFO cell, include the original address
12802 received for the other side, not its canonical address. Found
12803 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
12804 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
12805 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
12806 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
12807 occurred when a client tried to fetch a descriptor for a bridge
12808 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
12809 - Backport fixes for a pair of compilation warnings on Windows.
12810 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
12811 - If we had ever tried to call tor_addr_to_str on an address of
12812 unknown type, we would have done a strdup on an uninitialized
12813 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12814 Reported by "troll_un".
12815 - Correctly detect and handle transient lookup failures from
12816 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
12817 Reported by "troll_un".
12818 - Fix null-pointer access that could occur if TLS allocation failed.
12819 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12820 - Use tor_socket_t type for listener argument to accept(). Fixes bug
12821 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
12824 - Add two new config options for directory authorities:
12825 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
12826 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
12827 that is always sufficient to satisfy the bandwidth requirement for
12828 the Guard flag. Now it will be easier for researchers to simulate
12829 Tor networks with different values. Resolves ticket 4484.
12830 - When Tor ignores a hidden service specified in its configuration,
12831 include the hidden service's directory in the warning message.
12832 Previously, we would only tell the user that some hidden service
12833 was ignored. Bugfix on 0.0.6; fixes bug 4426.
12834 - Update to the December 6 2011 Maxmind GeoLite Country database.
12836 o Packaging changes:
12837 - Make it easier to automate expert package builds on Windows,
12838 by removing an absolute path from makensis.exe command.
12841 Changes in version 0.2.1.32 - 2011-12-16
12842 Tor 0.2.1.32 backports important security and privacy fixes for
12843 oldstable. This release is intended only for package maintainers and
12844 others who cannot use the 0.2.2 stable series. All others should be
12845 using Tor 0.2.2.x or newer.
12847 The Tor 0.2.1.x series will reach formal end-of-life some time in
12848 early 2012; we will stop releasing patches for it then.
12850 o Major bugfixes (also included in 0.2.2.x):
12851 - Correctly sanity-check that we don't underflow on a memory
12852 allocation (and then assert) for hidden service introduction
12853 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
12854 bugfix on 0.2.1.5-alpha.
12855 - Fix a heap overflow bug that could occur when trying to pull
12856 data into the first chunk of a buffer, when that chunk had
12857 already had some data drained from it. Fixes CVE-2011-2778;
12858 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
12861 - Update to the December 6 2011 Maxmind GeoLite Country database.
12864 Changes in version 0.2.3.9-alpha - 2011-12-08
12865 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
12866 a "DisableNetwork" security feature that bundles can use to avoid
12867 touching the network until bridges are configured, moves forward on
12868 the pluggable transport design, fixes a flaw in the hidden service
12869 design that unnecessarily prevented clients with wrong clocks from
12870 reaching hidden services, and fixes a wide variety of other issues.
12873 - Clients can now connect to private bridges over IPv6. Bridges
12874 still need at least one IPv4 address in order to connect to
12875 other relays. Note that we don't yet handle the case where the
12876 user has two bridge lines for the same bridge (one IPv4, one
12877 IPv6). Implements parts of proposal 186.
12878 - New "DisableNetwork" config option to prevent Tor from launching any
12879 connections or accepting any connections except on a control port.
12880 Bundles and controllers can set this option before letting Tor talk
12881 to the rest of the network, for example to prevent any connections
12882 to a non-bridge address. Packages like Orbot can also use this
12883 option to instruct Tor to save power when the network is off.
12884 - Clients and bridges can now be configured to use a separate
12885 "transport" proxy. This approach makes the censorship arms race
12886 easier by allowing bridges to use protocol obfuscation plugins. It
12887 implements the "managed proxy" part of proposal 180 (ticket 3472).
12888 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
12889 implementation. It makes AES_CTR about 7% faster than our old one
12890 (which was about 10% faster than the one OpenSSL used to provide).
12891 Resolves ticket 4526.
12892 - Add a "tor2web mode" for clients that want to connect to hidden
12893 services non-anonymously (and possibly more quickly). As a safety
12894 measure to try to keep users from turning this on without knowing
12895 what they are doing, tor2web mode must be explicitly enabled at
12896 compile time, and a copy of Tor compiled to run in tor2web mode
12897 cannot be used as a normal Tor client. Implements feature 2553.
12898 - Add experimental support for running on Windows with IOCP and no
12899 kernel-space socket buffers. This feature is controlled by a new
12900 "UserspaceIOCPBuffers" config option (off by default), which has
12901 no effect unless Tor has been built with support for bufferevents,
12902 is running on Windows, and has enabled IOCP. This may, in the long
12903 run, help solve or mitigate bug 98.
12904 - Use a more secure consensus parameter voting algorithm. Now at
12905 least three directory authorities or a majority of them must
12906 vote on a given parameter before it will be included in the
12907 consensus. Implements proposal 178.
12910 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
12911 They used to check that the timestamp was within 30 minutes
12912 of their system clock, so they could cap the size of their
12913 replay-detection cache, but that approach unnecessarily refused
12914 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
12915 the v3 intro-point protocol (the first one which sent a timestamp
12916 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
12917 - Only use the EVP interface when AES acceleration is enabled,
12918 to avoid a 5-7% performance regression. Resolves issue 4525;
12919 bugfix on 0.2.3.8-alpha.
12921 o Privacy/anonymity features (bridge detection):
12922 - Make bridge SSL certificates a bit more stealthy by using random
12923 serial numbers, in the same fashion as OpenSSL when generating
12924 self-signed certificates. Implements ticket 4584.
12925 - Introduce a new config option "DynamicDHGroups", enabled by
12926 default, which provides each bridge with a unique prime DH modulus
12927 to be used during SSL handshakes. This option attempts to help
12928 against censors who might use the Apache DH modulus as a static
12929 identifier for bridges. Addresses ticket 4548.
12931 o Minor features (new/different config options):
12932 - New configuration option "DisableDebuggerAttachment" (on by default)
12933 to prevent basic debugging attachment attempts by other processes.
12934 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
12935 - Allow MapAddress directives to specify matches against super-domains,
12936 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
12937 Implements issue 933.
12938 - Slightly change behavior of "list" options (that is, config
12939 options that can appear more than once) when they appear both in
12940 torrc and on the command line. Previously, the command-line options
12941 would be appended to the ones from torrc. Now, the command-line
12942 options override the torrc options entirely. This new behavior
12943 allows the user to override list options (like exit policies and
12944 ports to listen on) from the command line, rather than simply
12945 appending to the list.
12946 - You can get the old (appending) command-line behavior for "list"
12947 options by prefixing the option name with a "+".
12948 - You can remove all the values for a "list" option from the command
12949 line without adding any new ones by prefixing the option name
12951 - Add experimental support for a "defaults" torrc file to be parsed
12952 before the regular torrc. Torrc options override the defaults file's
12953 options in the same way that the command line overrides the torrc.
12954 The SAVECONF controller command saves only those options which
12955 differ between the current configuration and the defaults file. HUP
12956 reloads both files. (Note: This is an experimental feature; its
12957 behavior will probably be refined in future 0.2.3.x-alpha versions
12958 to better meet packagers' needs.) Implements task 4552.
12961 - Try to make the introductory warning message that Tor prints on
12962 startup more useful for actually finding help and information.
12963 Resolves ticket 2474.
12964 - Running "make version" now displays the version of Tor that
12965 we're about to build. Idea from katmagic; resolves issue 4400.
12966 - Expire old or over-used hidden service introduction points.
12967 Required by fix for bug 3460.
12968 - Move the replay-detection cache for the RSA-encrypted parts of
12969 INTRODUCE2 cells to the introduction point data structures.
12970 Previously, we would use one replay-detection cache per hidden
12971 service. Required by fix for bug 3460.
12972 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
12973 public key replay-detection cache from 60 minutes to 5 minutes. This
12974 replay-detection cache is now used only to detect multiple
12975 INTRODUCE2 cells specifying the same rendezvous point, so we can
12976 avoid launching multiple simultaneous attempts to connect to it.
12978 o Minor bugfixes (on Tor 0.2.2.x and earlier):
12979 - Resolve an integer overflow bug in smartlist_ensure_capacity().
12980 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
12982 - Fix a minor formatting issue in one of tor-gencert's error messages.
12984 - Prevent a false positive from the check-spaces script, by disabling
12985 the "whitespace between function name and (" check for functions
12987 - Fix a log message suggesting that people contact a non-existent
12988 email address. Fixes bug 3448.
12989 - Fix null-pointer access that could occur if TLS allocation failed.
12990 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
12991 - Report a real bootstrap problem to the controller on router
12992 identity mismatch. Previously we just said "foo", which probably
12993 made a lot of sense at the time. Fixes bug 4169; bugfix on
12995 - If we had ever tried to call tor_addr_to_str() on an address of
12996 unknown type, we would have done a strdup() on an uninitialized
12997 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
12998 Reported by "troll_un".
12999 - Correctly detect and handle transient lookup failures from
13000 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
13001 Reported by "troll_un".
13002 - Use tor_socket_t type for listener argument to accept(). Fixes bug
13003 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
13004 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
13005 bug 4532; found by "troll_un".
13007 o Minor bugfixes (on Tor 0.2.3.x):
13008 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
13010 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
13011 circuit for use as a hidden service client's rendezvous point.
13012 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
13013 with help from wanoskarnet.
13014 - Restore behavior of overriding SocksPort, ORPort, and similar
13015 options from the command line. Bugfix on 0.2.3.3-alpha.
13018 - Properly handle the case where the build-tree is not the same
13019 as the source tree when generating src/common/common_sha1.i,
13020 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
13021 bugfix on 0.2.0.1-alpha.
13023 o Code simplifications, cleanups, and refactorings:
13024 - Remove the pure attribute from all functions that used it
13025 previously. In many cases we assigned it incorrectly, because the
13026 functions might assert or call impure functions, and we don't have
13027 evidence that keeping the pure attribute is worthwhile. Implements
13028 changes suggested in ticket 4421.
13029 - Remove some dead code spotted by coverity. Fixes cid 432.
13030 Bugfix on 0.2.3.1-alpha, closes bug 4637.
13033 Changes in version 0.2.3.8-alpha - 2011-11-22
13034 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
13035 socketpair-related bug that has been bothering Windows users. It adds
13036 support to serve microdescriptors to controllers, so Vidalia's network
13037 map can resume listing relays (once Vidalia implements its side),
13038 and adds better support for hardware AES acceleration. Finally, it
13039 starts the process of adjusting the bandwidth cutoff for getting the
13040 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
13041 that tiny relays harm performance more than they help network capacity.
13044 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
13045 that it doesn't attempt to allocate a socketpair. This could cause
13046 some problems on Windows systems with overzealous firewalls. Fix for
13047 bug 4457; workaround for Libevent versions 2.0.1-alpha through
13049 - Correctly sanity-check that we don't underflow on a memory
13050 allocation (and then assert) for hidden service introduction
13051 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
13052 bugfix on 0.2.1.5-alpha.
13053 - Remove the artificially low cutoff of 20KB to guarantee the Fast
13054 flag. In the past few years the average relay speed has picked
13055 up, and while the "top 7/8 of the network get the Fast flag" and
13056 "all relays with 20KB or more of capacity get the Fast flag" rules
13057 used to have the same result, now the top 7/8 of the network has
13058 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
13059 - Fix a rare assertion failure when checking whether a v0 hidden
13060 service descriptor has any usable introduction points left, and
13061 we don't have enough information to build a circuit to the first
13062 intro point named in the descriptor. The HS client code in
13063 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
13064 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
13065 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
13066 - Make bridge authorities not crash when they are asked for their own
13067 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
13068 - When running as a client, do not print a misleading (and plain
13069 wrong) log message that we're collecting "directory request"
13070 statistics: clients don't collect statistics. Also don't create a
13071 useless (because empty) stats file in the stats/ directory. Fixes
13072 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
13075 - Allow Tor controllers like Vidalia to obtain the microdescriptor
13076 for a relay by identity digest or nickname. Previously,
13077 microdescriptors were only available by their own digests, so a
13078 controller would have to ask for and parse the whole microdescriptor
13079 consensus in order to look up a single relay's microdesc. Fixes
13080 bug 3832; bugfix on 0.2.3.1-alpha.
13081 - Use OpenSSL's EVP interface for AES encryption, so that all AES
13082 operations can use hardware acceleration (if present). Resolves
13085 o Minor bugfixes (on 0.2.2.x and earlier):
13086 - Detect failure to initialize Libevent. This fix provides better
13087 detection for future instances of bug 4457.
13088 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
13089 function. This was eating up hideously large amounts of time on some
13090 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
13091 - Don't warn about unused log_mutex in log.c when building with
13092 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
13093 0.1.0.6-rc which introduced --disable-threads.
13094 - Allow manual 'authenticate' commands to the controller interface
13095 from netcat (nc) as well as telnet. We were rejecting them because
13096 they didn't come with the expected whitespace at the end of the
13097 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
13098 - Fix some (not actually triggerable) buffer size checks in usage of
13099 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
13101 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
13102 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
13103 - When configuring, starting, or stopping an NT service, stop
13104 immediately after the service configuration attempt has succeeded
13105 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
13106 - When sending a NETINFO cell, include the original address
13107 received for the other side, not its canonical address. Found
13108 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
13109 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
13110 can pick them up when the tests aren't disabled. Bugfix on
13111 0.2.2.4-alpha which introduced tinytest.
13112 - Fix a memory leak when we check whether a hidden service
13113 descriptor has any usable introduction points left. Fixes bug
13114 4424. Bugfix on 0.2.2.25-alpha.
13115 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
13116 occurred when a client tried to fetch a descriptor for a bridge
13117 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
13119 o Minor bugfixes (on 0.2.3.x):
13120 - Make util unit tests build correctly with MSVC. Bugfix on
13121 0.2.3.3-alpha. Patch by Gisle Vanem.
13122 - Successfully detect AUTH_CHALLENGE cells with no recognized
13123 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
13124 Found by frosty_un.
13125 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
13126 it should still send a NETINFO cell to allow the connection to
13127 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
13129 - Log less loudly when we get an invalid authentication certificate
13130 from a source other than a directory authority: it's not unusual
13131 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
13133 - Tolerate servers with more clock skew in their authentication
13134 certificates than previously. Fixes bug 4371; bugfix on
13136 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
13137 on 0.2.3.4-alpha and 0.2.3.6-alpha.
13140 - Add two new config options for directory authorities:
13141 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
13142 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
13143 that is always sufficient to satisfy the bandwidth requirement for
13144 the Guard flag. Now it will be easier for researchers to simulate
13145 Tor networks with different values. Resolves ticket 4484.
13146 - When Tor ignores a hidden service specified in its configuration,
13147 include the hidden service's directory in the warning message.
13148 Previously, we would only tell the user that some hidden service
13149 was ignored. Bugfix on 0.0.6; fixes bug 4426.
13150 - When we fail to initialize Libevent, retry with IOCP disabled so we
13151 don't need to turn on multi-threading support in Libevent, which in
13152 turn requires a working socketpair(). This is a workaround for bug
13153 4457, which affects Libevent versions from 2.0.1-alpha through
13155 - Detect when we try to build on a platform that doesn't define
13156 AF_UNSPEC to 0. We don't work there, so refuse to compile.
13157 - Update to the November 1 2011 Maxmind GeoLite Country database.
13159 o Packaging changes:
13160 - Make it easier to automate expert package builds on Windows,
13161 by removing an absolute path from makensis.exe command.
13163 o Code simplifications and refactoring:
13164 - Remove some redundant #include directives throughout the code.
13165 Patch from Andrea Gelmini.
13166 - Unconditionally use OpenSSL's AES implementation instead of our
13167 old built-in one. OpenSSL's AES has been better for a while, and
13168 relatively few servers should still be on any version of OpenSSL
13169 that doesn't have good optimized assembly AES.
13170 - Use the name "CERTS" consistently to refer to the new cell type;
13171 we were calling it CERT in some places and CERTS in others.
13174 - Numerous new unit tests for functions in util.c and address.c by
13176 - The long-disabled benchmark tests are now split into their own
13177 ./src/test/bench binary.
13178 - The benchmark tests can now use more accurate timers than
13179 gettimeofday() when such timers are available.
13182 Changes in version 0.2.3.7-alpha - 2011-10-30
13183 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
13184 the new v3 handshake. It also resolves yet another bridge address
13188 - If we mark an OR connection for close based on a cell we process,
13189 don't process any further cells on it. We already avoid further
13190 reads on marked-for-close connections, but now we also discard the
13191 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
13192 which was the first version where we might mark a connection for
13193 close based on processing a cell on it.
13194 - Fix a double-free bug that would occur when we received an invalid
13195 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
13196 bugfix on 0.2.3.6-alpha.
13197 - Bridges no longer include their address in NETINFO cells on outgoing
13198 OR connections, to allow them to blend in better with clients.
13199 Removes another avenue for enumerating bridges. Reported by
13200 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
13201 cells were introduced.
13204 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
13205 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
13208 Changes in version 0.2.3.6-alpha - 2011-10-26
13209 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
13210 anonymity vulnerability where an attacker can deanonymize Tor
13211 users. Everybody should upgrade.
13213 This release also features support for a new v3 connection handshake
13214 protocol, and fixes to make hidden service connections more robust.
13217 - Implement a new handshake protocol (v3) for authenticating Tors to
13218 each other over TLS. It should be more resistant to fingerprinting
13219 than previous protocols, and should require less TLS hacking for
13220 future Tor implementations. Implements proposal 176.
13221 - Allow variable-length padding cells to disguise the length of
13222 Tor's TLS records. Implements part of proposal 184.
13224 o Privacy/anonymity fixes (clients):
13225 - Clients and bridges no longer send TLS certificate chains on
13226 outgoing OR connections. Previously, each client or bridge would
13227 use the same cert chain for all outgoing OR connections until
13228 its IP address changes, which allowed any relay that the client
13229 or bridge contacted to determine which entry guards it is using.
13230 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13231 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13232 no longer considers that connection as suitable for satisfying a
13233 circuit EXTEND request. Now relays can protect clients from the
13234 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13235 - Directory authorities no longer assign the Guard flag to relays
13236 that haven't upgraded to the above "refuse EXTEND requests
13237 to client connections" fix. Now directory authorities can
13238 protect clients from the CVE-2011-2768 issue even if neither
13239 the clients nor the relays have upgraded yet. There's a new
13240 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
13241 to let us transition smoothly, else tomorrow there would be no
13244 o Major bugfixes (hidden services):
13245 - Improve hidden service robustness: when an attempt to connect to
13246 a hidden service ends, be willing to refetch its hidden service
13247 descriptors from each of the HSDir relays responsible for them
13248 immediately. Previously, we would not consider refetching the
13249 service's descriptors from each HSDir for 15 minutes after the last
13250 fetch, which was inconvenient if the hidden service was not running
13251 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
13252 - When one of a hidden service's introduction points appears to be
13253 unreachable, stop trying it. Previously, we would keep trying
13254 to build circuits to the introduction point until we lost the
13255 descriptor, usually because the user gave up and restarted Tor.
13256 Partly fixes bug 3825.
13257 - Don't launch a useless circuit after failing to use one of a
13258 hidden service's introduction points. Previously, we would
13259 launch a new introduction circuit, but not set the hidden service
13260 which that circuit was intended to connect to, so it would never
13261 actually be used. A different piece of code would then create a
13262 new introduction circuit correctly. Bug reported by katmagic and
13263 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
13265 o Major bugfixes (other):
13266 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13267 that they initiated. Relays could distinguish incoming bridge
13268 connections from client connections, creating another avenue for
13269 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13270 Found by "frosty_un".
13271 - Don't update the AccountingSoftLimitHitAt state file entry whenever
13272 tor gets started. This prevents a wrong average bandwidth
13273 estimate, which would cause relays to always start a new accounting
13274 interval at the earliest possible moment. Fixes bug 2003; bugfix
13275 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
13276 immensely in tracking this bug down.
13277 - Fix a crash bug when changing node restrictions while a DNS lookup
13278 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
13281 o Minor bugfixes (on 0.2.2.x and earlier):
13282 - When a hidden service turns an extra service-side introduction
13283 circuit into a general-purpose circuit, free the rend_data and
13284 intro_key fields first, so we won't leak memory if the circuit
13285 is cannibalized for use as another service-side introduction
13286 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
13287 - Rephrase the log message emitted if the TestSocks check is
13288 successful. Patch from Fabian Keil; fixes bug 4094.
13289 - Bridges now skip DNS self-tests, to act a little more stealthily.
13290 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
13291 bridges. Patch by "warms0x".
13292 - Remove a confusing dollar sign from the example fingerprint in the
13293 man page, and also make the example fingerprint a valid one. Fixes
13294 bug 4309; bugfix on 0.2.1.3-alpha.
13295 - Fix internal bug-checking logic that was supposed to catch
13296 failures in digest generation so that it will fail more robustly
13297 if we ask for a nonexistent algorithm. Found by Coverity Scan.
13298 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
13299 - Report any failure in init_keys() calls launched because our
13300 IP address has changed. Spotted by Coverity Scan. Bugfix on
13301 0.1.1.4-alpha; fixes CID 484.
13303 o Minor bugfixes (on 0.2.3.x):
13304 - Fix a bug in configure.in that kept it from building a configure
13305 script with autoconf versions earlier than 2.61. Fixes bug 2430;
13306 bugfix on 0.2.3.1-alpha.
13307 - Don't warn users that they are exposing a client port to the
13308 Internet if they have specified an RFC1918 address. Previously,
13309 we would warn if the user had specified any non-loopback
13310 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
13311 - Fix memory leaks in the failing cases of the new SocksPort and
13312 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
13313 fixes coverity CIDs 485, 486, and 487.
13316 - When a hidden service's introduction point times out, consider
13317 trying it again during the next attempt to connect to the
13318 HS. Previously, we would not try it again unless a newly fetched
13319 descriptor contained it. Required by fixes for bugs 1297 and 3825.
13320 - The next version of Windows will be called Windows 8, and it has
13321 a major version of 6, minor version of 2. Correctly identify that
13322 version instead of calling it "Very recent version". Resolves
13323 ticket 4153; reported by funkstar.
13324 - The Bridge Authority now writes statistics on how many bridge
13325 descriptors it gave out in total, and how many unique descriptors
13326 it gave out. It also lists how often the most and least commonly
13327 fetched descriptors were given out, as well as the median and
13328 25th/75th percentile. Implements tickets 4200 and 4294.
13329 - Update to the October 4 2011 Maxmind GeoLite Country database.
13331 o Code simplifications and refactoring:
13332 - Remove some old code to remember statistics about which descriptors
13333 we've served as a directory mirror. The feature wasn't used and
13334 is outdated now that microdescriptors are around.
13335 - Rename Tor functions that turn strings into addresses, so that
13336 "parse" indicates that no hostname resolution occurs, and
13337 "lookup" indicates that hostname resolution may occur. This
13338 should help prevent mistakes in the future. Fixes bug 3512.
13341 Changes in version 0.2.2.34 - 2011-10-26
13342 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
13343 can deanonymize Tor users. Everybody should upgrade.
13345 The attack relies on four components: 1) Clients reuse their TLS cert
13346 when talking to different relays, so relays can recognize a user by
13347 the identity key in her cert. 2) An attacker who knows the client's
13348 identity key can probe each guard relay to see if that identity key
13349 is connected to that guard relay right now. 3) A variety of active
13350 attacks in the literature (starting from "Low-Cost Traffic Analysis
13351 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
13352 discover the guard relays that a Tor user visiting the website is using.
13353 4) Clients typically pick three guards at random, so the set of guards
13354 for a given user could well be a unique fingerprint for her. This
13355 release fixes components #1 and #2, which is enough to block the attack;
13356 the other two remain as open research problems. Special thanks to
13357 "frosty_un" for reporting the issue to us!
13359 Clients should upgrade so they are no longer recognizable by the TLS
13360 certs they present. Relays should upgrade so they no longer allow a
13361 remote attacker to probe them to test whether unpatched clients are
13362 currently connected to them.
13364 This release also fixes several vulnerabilities that allow an attacker
13365 to enumerate bridge relays. Some bridge enumeration attacks still
13366 remain; see for example proposal 188.
13368 o Privacy/anonymity fixes (clients):
13369 - Clients and bridges no longer send TLS certificate chains on
13370 outgoing OR connections. Previously, each client or bridge would
13371 use the same cert chain for all outgoing OR connections until
13372 its IP address changes, which allowed any relay that the client
13373 or bridge contacted to determine which entry guards it is using.
13374 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13375 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13376 no longer considers that connection as suitable for satisfying a
13377 circuit EXTEND request. Now relays can protect clients from the
13378 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13379 - Directory authorities no longer assign the Guard flag to relays
13380 that haven't upgraded to the above "refuse EXTEND requests
13381 to client connections" fix. Now directory authorities can
13382 protect clients from the CVE-2011-2768 issue even if neither
13383 the clients nor the relays have upgraded yet. There's a new
13384 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
13385 to let us transition smoothly, else tomorrow there would be no
13388 o Privacy/anonymity fixes (bridge enumeration):
13389 - Bridge relays now do their directory fetches inside Tor TLS
13390 connections, like all the other clients do, rather than connecting
13391 directly to the DirPort like public relays do. Removes another
13392 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
13393 - Bridges relays now build circuits for themselves in a more similar
13394 way to how clients build them. Removes another avenue for
13395 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
13396 when bridges were introduced.
13397 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13398 that they initiated. Relays could distinguish incoming bridge
13399 connections from client connections, creating another avenue for
13400 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13401 Found by "frosty_un".
13404 - Fix a crash bug when changing node restrictions while a DNS lookup
13405 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
13407 - Don't launch a useless circuit after failing to use one of a
13408 hidden service's introduction points. Previously, we would
13409 launch a new introduction circuit, but not set the hidden service
13410 which that circuit was intended to connect to, so it would never
13411 actually be used. A different piece of code would then create a
13412 new introduction circuit correctly. Bug reported by katmagic and
13413 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
13416 - Change an integer overflow check in the OpenBSD_Malloc code so
13417 that GCC is less likely to eliminate it as impossible. Patch
13418 from Mansour Moufid. Fixes bug 4059.
13419 - When a hidden service turns an extra service-side introduction
13420 circuit into a general-purpose circuit, free the rend_data and
13421 intro_key fields first, so we won't leak memory if the circuit
13422 is cannibalized for use as another service-side introduction
13423 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
13424 - Bridges now skip DNS self-tests, to act a little more stealthily.
13425 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
13426 bridges. Patch by "warms0x".
13427 - Fix internal bug-checking logic that was supposed to catch
13428 failures in digest generation so that it will fail more robustly
13429 if we ask for a nonexistent algorithm. Found by Coverity Scan.
13430 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
13431 - Report any failure in init_keys() calls launched because our
13432 IP address has changed. Spotted by Coverity Scan. Bugfix on
13433 0.1.1.4-alpha; fixes CID 484.
13435 o Minor bugfixes (log messages and documentation):
13436 - Remove a confusing dollar sign from the example fingerprint in the
13437 man page, and also make the example fingerprint a valid one. Fixes
13438 bug 4309; bugfix on 0.2.1.3-alpha.
13439 - The next version of Windows will be called Windows 8, and it has
13440 a major version of 6, minor version of 2. Correctly identify that
13441 version instead of calling it "Very recent version". Resolves
13442 ticket 4153; reported by funkstar.
13443 - Downgrade log messages about circuit timeout calibration from
13444 "notice" to "info": they don't require or suggest any human
13445 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
13446 bugfix on 0.2.2.14-alpha.
13449 - Turn on directory request statistics by default and include them in
13450 extra-info descriptors. Don't break if we have no GeoIP database.
13451 Backported from 0.2.3.1-alpha; implements ticket 3951.
13452 - Update to the October 4 2011 Maxmind GeoLite Country database.
13455 Changes in version 0.2.1.31 - 2011-10-26
13456 Tor 0.2.1.31 backports important security and privacy fixes for
13457 oldstable. This release is intended only for package maintainers and
13458 others who cannot use the 0.2.2 stable series. All others should be
13459 using Tor 0.2.2.x or newer.
13461 o Security fixes (also included in 0.2.2.x):
13462 - Replace all potentially sensitive memory comparison operations
13463 with versions whose runtime does not depend on the data being
13464 compared. This will help resist a class of attacks where an
13465 adversary can use variations in timing information to learn
13466 sensitive data. Fix for one case of bug 3122. (Safe memcmp
13467 implementation by Robert Ransom based partially on code by DJB.)
13468 - Fix an assert in parsing router descriptors containing IPv6
13469 addresses. This one took down the directory authorities when
13470 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
13472 o Privacy/anonymity fixes (also included in 0.2.2.x):
13473 - Clients and bridges no longer send TLS certificate chains on
13474 outgoing OR connections. Previously, each client or bridge would
13475 use the same cert chain for all outgoing OR connections until
13476 its IP address changes, which allowed any relay that the client
13477 or bridge contacted to determine which entry guards it is using.
13478 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
13479 - If a relay receives a CREATE_FAST cell on a TLS connection, it
13480 no longer considers that connection as suitable for satisfying a
13481 circuit EXTEND request. Now relays can protect clients from the
13482 CVE-2011-2768 issue even if the clients haven't upgraded yet.
13483 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
13484 that they initiated. Relays could distinguish incoming bridge
13485 connections from client connections, creating another avenue for
13486 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
13487 Found by "frosty_un".
13488 - When receiving a hidden service descriptor, check that it is for
13489 the hidden service we wanted. Previously, Tor would store any
13490 hidden service descriptors that a directory gave it, whether it
13491 wanted them or not. This wouldn't have let an attacker impersonate
13492 a hidden service, but it did let directories pre-seed a client
13493 with descriptors that it didn't want. Bugfix on 0.0.6.
13494 - Avoid linkability based on cached hidden service descriptors: forget
13495 all hidden service descriptors cached as a client when processing a
13496 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
13497 - Make the bridge directory authority refuse to answer directory
13498 requests for "all" descriptors. It used to include bridge
13499 descriptors in its answer, which was a major information leak.
13500 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
13501 - Don't attach new streams to old rendezvous circuits after SIGNAL
13502 NEWNYM. Previously, we would keep using an existing rendezvous
13503 circuit if it remained open (i.e. if it were kept open by a
13504 long-lived stream, or if a new stream were attached to it before
13505 Tor could notice that it was old and no longer in use). Bugfix on
13506 0.1.1.15-rc; fixes bug 3375.
13508 o Minor bugfixes (also included in 0.2.2.x):
13509 - When we restart our relay, we might get a successful connection
13510 from the outside before we've started our reachability tests,
13511 triggering a warning: "ORPort found reachable, but I have no
13512 routerinfo yet. Failing to inform controller of success." This
13513 bug was harmless unless Tor is running under a controller
13514 like Vidalia, in which case the controller would never get a
13515 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
13517 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
13518 enabled. Fixes bug 1526.
13519 - Remove undocumented option "-F" from tor-resolve: it hasn't done
13520 anything since 0.2.1.16-rc.
13521 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
13522 None of the cases where we did this before were wrong, but by making
13523 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
13524 - Fix a rare crash bug that could occur when a client was configured
13525 with a large number of bridges. Fixes bug 2629; bugfix on
13526 0.2.1.2-alpha. Bugfix by trac user "shitlei".
13527 - Correct the warning displayed when a rendezvous descriptor exceeds
13528 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
13530 - Fix an uncommon assertion failure when running with DNSPort under
13531 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
13532 - When warning about missing zlib development packages during compile,
13533 give the correct package names. Bugfix on 0.2.0.1-alpha.
13534 - Require that introduction point keys and onion keys have public
13535 exponent 65537. Bugfix on 0.2.0.10-alpha.
13536 - Do not crash when our configuration file becomes unreadable, for
13537 example due to a permissions change, between when we start up
13538 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
13540 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
13542 - Always NUL-terminate the sun_path field of a sockaddr_un before
13543 passing it to the kernel. (Not a security issue: kernels are
13544 smart enough to reject bad sockaddr_uns.) Found by Coverity;
13545 CID #428. Bugfix on Tor 0.2.0.3-alpha.
13546 - Don't stack-allocate the list of supplementary GIDs when we're
13547 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
13548 could take up to 256K, which is way too much stack. Found by
13549 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
13551 o Minor bugfixes (only in 0.2.1.x):
13552 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
13553 rely on them. Bugfix on 0.2.1.30.
13554 - Use git revisions instead of svn revisions when generating our
13555 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
13557 o Minor features (also included in 0.2.2.x):
13558 - Adjust the expiration time on our SSL session certificates to
13559 better match SSL certs seen in the wild. Resolves ticket 4014.
13560 - Allow nameservers with IPv6 address. Resolves bug 2574.
13561 - Update to the October 4 2011 Maxmind GeoLite Country database.
13564 Changes in version 0.2.3.5-alpha - 2011-09-28
13565 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
13566 bridge relays; fixes an assertion error that many users started hitting
13567 today; and adds the ability to refill token buckets more often than
13568 once per second, allowing significant performance improvements.
13571 - Bridge relays now do their directory fetches inside Tor TLS
13572 connections, like all the other clients do, rather than connecting
13573 directly to the DirPort like public relays do. Removes another
13574 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
13575 - Bridges relays now build circuits for themselves in a more similar
13576 way to how clients build them. Removes another avenue for
13577 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
13578 when bridges were introduced.
13581 - Fix an "Assertion md->held_by_node == 1 failed" error that could
13582 occur when the same microdescriptor was referenced by two node_t
13583 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
13585 o Major features (networking):
13586 - Add a new TokenBucketRefillInterval option to refill token buckets
13587 more frequently than once per second. This should improve network
13588 performance, alleviate queueing problems, and make traffic less
13589 bursty. Implements proposal 183; closes ticket 3630. Design by
13590 Florian Tschorsch and Björn Scheuermann; implementation by
13594 - Change an integer overflow check in the OpenBSD_Malloc code so
13595 that GCC is less likely to eliminate it as impossible. Patch
13596 from Mansour Moufid. Fixes bug 4059.
13598 o Minor bugfixes (usability):
13599 - Downgrade log messages about circuit timeout calibration from
13600 "notice" to "info": they don't require or suggest any human
13601 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
13602 bugfix on 0.2.2.14-alpha.
13604 o Minor features (diagnostics):
13605 - When the system call to create a listener socket fails, log the
13606 error message explaining why. This may help diagnose bug 4027.
13609 Changes in version 0.2.3.4-alpha - 2011-09-13
13610 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
13611 tweak to Tor's TLS handshake that makes relays and bridges that run
13612 this new version reachable from Iran again. It also fixes a few new
13613 bugs in 0.2.3.x, and teaches relays to recognize when they're not
13614 listed in the network consensus and republish.
13616 o Major bugfixes (also part of 0.2.2.33):
13617 - Avoid an assertion failure when reloading a configuration with
13618 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
13619 3923; bugfix on 0.2.2.25-alpha.
13621 o Minor features (security, also part of 0.2.2.33):
13622 - Check for replays of the public-key encrypted portion of an
13623 INTRODUCE1 cell, in addition to the current check for replays of
13624 the g^x value. This prevents a possible class of active attacks
13625 by an attacker who controls both an introduction point and a
13626 rendezvous point, and who uses the malleability of AES-CTR to
13627 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
13628 that these attacks are infeasible (requiring the attacker to send
13629 on the order of zettabytes of altered cells in a short interval),
13630 but we'd rather block them off in case there are any classes of
13631 this attack that we missed. Reported by Willem Pinckaers.
13633 o Minor features (also part of 0.2.2.33):
13634 - Adjust the expiration time on our SSL session certificates to
13635 better match SSL certs seen in the wild. Resolves ticket 4014.
13636 - Change the default required uptime for a relay to be accepted as
13637 a HSDir (hidden service directory) from 24 hours to 25 hours.
13638 Improves on 0.2.0.10-alpha; resolves ticket 2649.
13639 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
13640 authorities to abstain from voting on assignment of the HSDir
13641 consensus flag. Related to bug 2649.
13642 - Update to the September 6 2011 Maxmind GeoLite Country database.
13644 o Minor bugfixes (also part of 0.2.2.33):
13645 - Demote the 'replay detected' log message emitted when a hidden
13646 service receives the same Diffie-Hellman public key in two different
13647 INTRODUCE2 cells to info level. A normal Tor client can cause that
13648 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
13649 fixes part of bug 2442.
13650 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
13651 level. There is nothing that a hidden service's operator can do
13652 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
13654 - Clarify a log message specifying the characters permitted in
13655 HiddenServiceAuthorizeClient client names. Previously, the log
13656 message said that "[A-Za-z0-9+-_]" were permitted; that could have
13657 given the impression that every ASCII character between "+" and "_"
13658 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
13660 o Build fixes (also part of 0.2.2.33):
13661 - Clean up some code issues that prevented Tor from building on older
13662 BSDs. Fixes bug 3894; reported by "grarpamp".
13663 - Search for a platform-specific version of "ar" when cross-compiling.
13664 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
13667 - Fix a bug where the SocksPort option (for example) would get
13668 ignored and replaced by the default if a SocksListenAddress
13669 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
13673 - Relays now try regenerating and uploading their descriptor more
13674 frequently if they are not listed in the consensus, or if the
13675 version of their descriptor listed in the consensus is too
13676 old. This fix should prevent situations where a server declines
13677 to re-publish itself because it has done so too recently, even
13678 though the authorities decided not to list its recent-enough
13679 descriptor. Fix for bug 3327.
13682 - Relays now include a reason for regenerating their descriptors
13683 in an HTTP header when uploading to the authorities. This will
13684 make it easier to debug descriptor-upload issues in the future.
13685 - When starting as root and then changing our UID via the User
13686 control option, and we have a ControlSocket configured, make sure
13687 that the ControlSocket is owned by the same account that Tor will
13688 run under. Implements ticket 3421; fix by Jérémy Bobbio.
13691 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
13692 utility function used in the control-port code). This shouldn't
13693 ever happen unless Tor is completely out of memory, but if it did
13694 happen and Tor somehow recovered from it, Tor could have sent a log
13695 message to a control port in the middle of a reply to a controller
13696 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
13697 - Make 'FetchUselessDescriptors' cause all descriptor types and
13698 all consensus types (including microdescriptors) to get fetched.
13699 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
13701 o Code refactoring:
13702 - Make a new "entry connection" struct as an internal subtype of "edge
13703 connection", to simplify the code and make exit connections smaller.
13706 Changes in version 0.2.2.33 - 2011-09-13
13707 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
13708 TLS handshake that makes relays and bridges that run this new version
13709 reachable from Iran again.
13712 - Avoid an assertion failure when reloading a configuration with
13713 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
13714 3923; bugfix on 0.2.2.25-alpha.
13716 o Minor features (security):
13717 - Check for replays of the public-key encrypted portion of an
13718 INTRODUCE1 cell, in addition to the current check for replays of
13719 the g^x value. This prevents a possible class of active attacks
13720 by an attacker who controls both an introduction point and a
13721 rendezvous point, and who uses the malleability of AES-CTR to
13722 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
13723 that these attacks are infeasible (requiring the attacker to send
13724 on the order of zettabytes of altered cells in a short interval),
13725 but we'd rather block them off in case there are any classes of
13726 this attack that we missed. Reported by Willem Pinckaers.
13729 - Adjust the expiration time on our SSL session certificates to
13730 better match SSL certs seen in the wild. Resolves ticket 4014.
13731 - Change the default required uptime for a relay to be accepted as
13732 a HSDir (hidden service directory) from 24 hours to 25 hours.
13733 Improves on 0.2.0.10-alpha; resolves ticket 2649.
13734 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
13735 authorities to abstain from voting on assignment of the HSDir
13736 consensus flag. Related to bug 2649.
13737 - Update to the September 6 2011 Maxmind GeoLite Country database.
13739 o Minor bugfixes (documentation and log messages):
13740 - Correct the man page to explain that HashedControlPassword and
13741 CookieAuthentication can both be set, in which case either method
13742 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
13743 when we decided to allow these config options to both be set. Issue
13744 raised by bug 3898.
13745 - Demote the 'replay detected' log message emitted when a hidden
13746 service receives the same Diffie-Hellman public key in two different
13747 INTRODUCE2 cells to info level. A normal Tor client can cause that
13748 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
13749 fixes part of bug 2442.
13750 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
13751 level. There is nothing that a hidden service's operator can do
13752 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
13754 - Clarify a log message specifying the characters permitted in
13755 HiddenServiceAuthorizeClient client names. Previously, the log
13756 message said that "[A-Za-z0-9+-_]" were permitted; that could have
13757 given the impression that every ASCII character between "+" and "_"
13758 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
13761 - Provide a substitute implementation of lround() for MSVC, which
13762 apparently lacks it. Patch from Gisle Vanem.
13763 - Clean up some code issues that prevented Tor from building on older
13764 BSDs. Fixes bug 3894; reported by "grarpamp".
13765 - Search for a platform-specific version of "ar" when cross-compiling.
13766 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
13769 Changes in version 0.2.3.3-alpha - 2011-09-01
13770 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
13771 security, and provides client-side support for the microdescriptor
13772 and optimistic data features introduced earlier in the 0.2.3.x
13773 series. It also includes numerous critical bugfixes in the (optional)
13774 bufferevent-based networking backend.
13776 o Major features (stream isolation):
13777 - You can now configure Tor so that streams from different
13778 applications are isolated on different circuits, to prevent an
13779 attacker who sees your streams as they leave an exit node from
13780 linking your sessions to one another. To do this, choose some way
13781 to distinguish the applications: have them connect to different
13782 SocksPorts, or have one of them use SOCKS4 while the other uses
13783 SOCKS5, or have them pass different authentication strings to the
13784 SOCKS proxy. Then, use the new SocksPort syntax to configure the
13785 degree of isolation you need. This implements Proposal 171.
13786 - There's a new syntax for specifying multiple client ports (such as
13787 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
13788 multiple *Port entries with full addr:port syntax on each.
13789 The old *ListenAddress format is still supported, but you can't
13790 mix it with the new *Port syntax.
13792 o Major features (other):
13793 - Enable microdescriptor fetching by default for clients. This allows
13794 clients to download a much smaller amount of directory information.
13795 To disable it (and go back to the old-style consensus and
13796 descriptors), set "UseMicrodescriptors 0" in your torrc file.
13797 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
13798 "PortForwarding" config option), now supports Windows.
13799 - When using an exit relay running 0.2.3.x, clients can now
13800 "optimistically" send data before the exit relay reports that
13801 the stream has opened. This saves a round trip when starting
13802 connections where the client speaks first (such as web browsing).
13803 This behavior is controlled by a consensus parameter (currently
13804 disabled). To turn it on or off manually, use the "OptimisticData"
13805 torrc option. Implements proposal 181; code by Ian Goldberg.
13807 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
13808 - When using IOCP on Windows, we need to enable Libevent windows
13810 - The IOCP backend now works even when the user has not specified
13811 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
13812 Fixes part of bug 3752.
13813 - Correctly record the bytes we've read and written when using
13814 bufferevents, so that we can include them in our bandwidth history
13815 and advertised bandwidth. Fixes bug 3803.
13816 - Apply rate-limiting only at the bottom of a chain of filtering
13817 bufferevents. This prevents us from filling up internal read
13818 buffers and violating rate-limits when filtering bufferevents
13819 are enabled. Fixes part of bug 3804.
13820 - Add high-watermarks to the output buffers for filtered
13821 bufferevents. This prevents us from filling up internal write
13822 buffers and wasting CPU cycles when filtering bufferevents are
13823 enabled. Fixes part of bug 3804.
13824 - Correctly notice when data has been written from a bufferevent
13825 without flushing it completely. Fixes bug 3805.
13826 - Fix a bug where server-side tunneled bufferevent-based directory
13827 streams would get closed prematurely. Fixes bug 3814.
13828 - Fix a use-after-free error with per-connection rate-limiting
13829 buckets. Fixes bug 3888.
13831 o Major bugfixes (also part of 0.2.2.31-rc):
13832 - If we're configured to write our ControlPorts to disk, only write
13833 them after switching UID and creating the data directory. This way,
13834 we don't fail when starting up with a nonexistent DataDirectory
13835 and a ControlPortWriteToFile setting based on that directory. Fixes
13836 bug 3747; bugfix on Tor 0.2.2.26-beta.
13839 - Added a new CONF_CHANGED event so that controllers can be notified
13840 of any configuration changes made by other controllers, or by the
13841 user. Implements ticket 1692.
13842 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
13843 leak when using bufferevents, and lets Libevent worry about how to
13844 best copy data out of a buffer.
13845 - Replace files in stats/ rather than appending to them. Now that we
13846 include statistics in extra-info descriptors, it makes no sense to
13847 keep old statistics forever. Implements ticket 2930.
13849 o Minor features (build compatibility):
13850 - Limited, experimental support for building with nmake and MSVC.
13851 - Provide a substitute implementation of lround() for MSVC, which
13852 apparently lacks it. Patch from Gisle Vanem.
13854 o Minor features (also part of 0.2.2.31-rc):
13855 - Update to the August 2 2011 Maxmind GeoLite Country database.
13857 o Minor bugfixes (on 0.2.3.x-alpha):
13858 - Fix a spurious warning when parsing SOCKS requests with
13859 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
13860 - Get rid of a harmless warning that could happen on relays running
13861 with bufferevents. The warning was caused by someone doing an http
13862 request to a relay's orport. Also don't warn for a few related
13863 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
13865 o Minor bugfixes (on 2.2.x and earlier):
13866 - Correct the man page to explain that HashedControlPassword and
13867 CookieAuthentication can both be set, in which case either method
13868 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
13869 when we decided to allow these config options to both be set. Issue
13870 raised by bug 3898.
13871 - The "--quiet" and "--hush" options now apply not only to Tor's
13872 behavior before logs are configured, but also to Tor's behavior in
13873 the absense of configured logs. Fixes bug 3550; bugfix on
13876 o Minor bugfixes (also part of 0.2.2.31-rc):
13877 - Write several files in text mode, on OSes that distinguish text
13878 mode from binary mode (namely, Windows). These files are:
13879 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13880 that collect those statistics; 'client_keys' and 'hostname' for
13881 hidden services that use authentication; and (in the tor-gencert
13882 utility) newly generated identity and signing keys. Previously,
13883 we wouldn't specify text mode or binary mode, leading to an
13884 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13885 the DirRecordUsageByCountry option which would have triggered
13886 the assertion failure was added), although this assertion failure
13887 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13888 - Selectively disable deprecation warnings on OS X because Lion
13889 started deprecating the shipped copy of openssl. Fixes bug 3643.
13890 - Remove an extra pair of quotation marks around the error
13891 message in control-port STATUS_GENERAL BUG events. Bugfix on
13892 0.1.2.6-alpha; fixes bug 3732.
13893 - When unable to format an address as a string, report its value
13894 as "???" rather than reusing the last formatted address. Bugfix
13897 o Code simplifications and refactoring:
13898 - Rewrite the listener-selection logic so that parsing which ports
13899 we want to listen on is now separate from binding to the ports
13903 - Building Tor with bufferevent support now requires Libevent
13904 2.0.13-stable or later. Previous versions of Libevent had bugs in
13905 SSL-related bufferevents and related issues that would make Tor
13906 work badly with bufferevents. Requiring 2.0.13-stable also allows
13907 Tor with bufferevents to take advantage of Libevent APIs
13908 introduced after 2.0.8-rc.
13911 Changes in version 0.2.2.32 - 2011-08-27
13912 The Tor 0.2.2 release series is dedicated to the memory of Andreas
13913 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
13914 a founder of the PETS community, a leader in our field, a mentor,
13915 and a friend. He left us with these words: "I had the possibility
13916 to contribute to this world that is not as it should be. I hope I
13917 could help in some areas to make the world a better place, and that
13918 I could also encourage other people to be engaged in improving the
13919 world. Please, stay engaged. This world needs you, your love, your
13920 initiative -- now I cannot be part of that anymore."
13922 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
13923 ready. More than two years in the making, this release features improved
13924 client performance and hidden service reliability, better compatibility
13925 for Android, correct behavior for bridges that listen on more than
13926 one address, more extensible and flexible directory object handling,
13927 better reporting of network statistics, improved code security, and
13928 many many other features and bugfixes.
13931 Changes in version 0.2.2.31-rc - 2011-08-17
13932 Tor 0.2.2.31-rc is the second and hopefully final release candidate
13933 for the Tor 0.2.2.x series.
13936 - Remove an extra pair of quotation marks around the error
13937 message in control-port STATUS_GENERAL BUG events. Bugfix on
13938 0.1.2.6-alpha; fixes bug 3732.
13939 - If we're configured to write our ControlPorts to disk, only write
13940 them after switching UID and creating the data directory. This way,
13941 we don't fail when starting up with a nonexistent DataDirectory
13942 and a ControlPortWriteToFile setting based on that directory. Fixes
13943 bug 3747; bugfix on Tor 0.2.2.26-beta.
13946 - Update to the August 2 2011 Maxmind GeoLite Country database.
13949 - Allow GETINFO fingerprint to return a fingerprint even when
13950 we have not yet built a router descriptor. Fixes bug 3577;
13951 bugfix on 0.2.0.1-alpha.
13952 - Write several files in text mode, on OSes that distinguish text
13953 mode from binary mode (namely, Windows). These files are:
13954 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
13955 that collect those statistics; 'client_keys' and 'hostname' for
13956 hidden services that use authentication; and (in the tor-gencert
13957 utility) newly generated identity and signing keys. Previously,
13958 we wouldn't specify text mode or binary mode, leading to an
13959 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
13960 the DirRecordUsageByCountry option which would have triggered
13961 the assertion failure was added), although this assertion failure
13962 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
13963 - Selectively disable deprecation warnings on OS X because Lion
13964 started deprecating the shipped copy of openssl. Fixes bug 3643.
13965 - When unable to format an address as a string, report its value
13966 as "???" rather than reusing the last formatted address. Bugfix
13970 Changes in version 0.2.3.2-alpha - 2011-07-18
13971 Tor 0.2.3.2-alpha introduces two new experimental features:
13972 microdescriptors and pluggable transports. It also continues cleaning
13973 up a variety of recently introduced features.
13976 - Clients can now use microdescriptors instead of regular descriptors
13977 to build circuits. Microdescriptors are authority-generated
13978 summaries of regular descriptors' contents, designed to change
13979 very rarely (see proposal 158 for details). This feature is
13980 designed to save bandwidth, especially for clients on slow internet
13981 connections. It's off by default for now, since nearly no caches
13982 support it, but it will be on-by-default for clients in a future
13983 version. You can use the UseMicrodescriptors option to turn it on.
13984 - Tor clients using bridges can now be configured to use a separate
13985 'transport' proxy for each bridge. This approach helps to resist
13986 censorship by allowing bridges to use protocol obfuscation
13987 plugins. It implements part of proposal 180. Implements ticket 2841.
13988 - While we're trying to bootstrap, record how many TLS connections
13989 fail in each state, and report which states saw the most failures
13990 in response to any bootstrap failures. This feature may speed up
13991 diagnosis of censorship events. Implements ticket 3116.
13993 o Major bugfixes (on 0.2.3.1-alpha):
13994 - When configuring a large set of nodes in EntryNodes (as with
13995 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
13996 random subset to be guards, and choose them in random
13997 order. Fixes bug 2798.
13998 - Tor could crash when remembering a consensus in a non-used consensus
13999 flavor without having a current consensus set. Fixes bug 3361.
14000 - Comparing an unknown address to a microdescriptor's shortened exit
14001 policy would always give a "rejected" result. Fixes bug 3599.
14002 - Using microdescriptors as a client no longer prevents Tor from
14003 uploading and downloading hidden service descriptors. Fixes
14007 - Allow nameservers with IPv6 address. Resolves bug 2574.
14008 - Accept attempts to include a password authenticator in the
14009 handshake, as supported by SOCKS5. This handles SOCKS clients that
14010 don't know how to omit a password when authenticating. Resolves
14012 - When configuring a large set of nodes in EntryNodes, and there are
14013 enough of them listed as Guard so that we don't need to consider
14014 the non-guard entries, prefer the ones listed with the Guard flag.
14015 - Check for and recover from inconsistency in the microdescriptor
14016 cache. This will make it harder for us to accidentally free a
14017 microdescriptor without removing it from the appropriate data
14018 structures. Fixes issue 3135; issue noted by "wanoskarnet".
14019 - Log SSL state transitions at log level DEBUG, log domain
14020 HANDSHAKE. This can be useful for debugging censorship events.
14021 Implements ticket 3264.
14022 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
14023 implements ticket 3439.
14025 o Minor bugfixes (on 0.2.3.1-alpha):
14026 - Do not free all general-purpose regular descriptors just
14027 because microdescriptor use is enabled. Fixes bug 3113.
14028 - Correctly link libevent_openssl when --enable-static-libevent
14029 is passed to configure. Fixes bug 3118.
14030 - Bridges should not complain during their heartbeat log messages that
14031 they are unlisted in the consensus: that's more or less the point
14032 of being a bridge. Fixes bug 3183.
14033 - Report a SIGNAL event to controllers when acting on a delayed
14034 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
14035 event to the controller if we acted on a SIGNAL NEWNYM command
14036 immediately, and otherwise not report a SIGNAL event for the
14037 command at all. Fixes bug 3349.
14038 - Fix a crash when handling the SIGNAL controller command or
14039 reporting ERR-level status events with bufferevents enabled. Found
14040 by Robert Ransom. Fixes bug 3367.
14041 - Always ship the tor-fw-helper manpage in our release tarballs.
14042 Fixes bug 3389. Reported by Stephen Walker.
14043 - Fix a class of double-mark-for-close bugs when bufferevents
14044 are enabled. Fixes bug 3403.
14045 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
14046 - Add SIGNAL to the list returned by the 'GETINFO events/names'
14047 control-port command. Fixes part of bug 3465.
14048 - Prevent using negative indices during unit test runs when read_all()
14049 fails. Spotted by coverity.
14050 - Fix a rare memory leak when checking the nodelist without it being
14051 present. Found by coverity.
14052 - Only try to download a microdescriptor-flavored consensus from
14053 a directory cache that provides them.
14055 o Minor bugfixes (on 0.2.2.x and earlier):
14056 - Assert that hidden-service-related operations are not performed
14057 using single-hop circuits. Previously, Tor would assert that
14058 client-side streams are not attached to single-hop circuits,
14059 but not that other sensitive operations on the client and service
14060 side are not performed using single-hop circuits. Fixes bug 3332;
14062 - Don't publish a new relay descriptor when we reload our onion key,
14063 unless the onion key has actually changed. Fixes bug 3263 and
14064 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
14065 - Allow GETINFO fingerprint to return a fingerprint even when
14066 we have not yet built a router descriptor. Fixes bug 3577;
14067 bugfix on 0.2.0.1-alpha.
14068 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
14069 on 0.2.2.4-alpha; fixes bug 3427.
14071 o Code simplification and refactoring:
14072 - Use tor_sscanf() in place of scanf() in more places through the
14073 code. This makes us a little more locale-independent, and
14074 should help shut up code-analysis tools that can't tell
14075 a safe sscanf string from a dangerous one.
14076 - Use tt_assert(), not tor_assert(), for checking for test failures.
14077 This makes the unit tests more able to go on in the event that
14079 - Split connection_about_to_close() into separate functions for each
14083 - On Windows, we now define the _WIN32_WINNT macros only if they
14084 are not already defined. This lets the person building Tor decide,
14085 if they want, to require a later version of Windows.
14088 Changes in version 0.2.2.30-rc - 2011-07-07
14089 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
14090 series. It fixes a few smaller bugs, but generally appears stable.
14091 Please test it and let us know whether it is!
14094 - Send a SUCCEEDED stream event to the controller when a reverse
14095 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
14096 discovered by katmagic.
14097 - Always NUL-terminate the sun_path field of a sockaddr_un before
14098 passing it to the kernel. (Not a security issue: kernels are
14099 smart enough to reject bad sockaddr_uns.) Found by Coverity;
14100 CID #428. Bugfix on Tor 0.2.0.3-alpha.
14101 - Don't stack-allocate the list of supplementary GIDs when we're
14102 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
14103 could take up to 256K, which is way too much stack. Found by
14104 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
14105 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
14106 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
14107 fixes part of bug 3465.
14108 - Fix a memory leak when receiving a descriptor for a hidden
14109 service we didn't ask for. Found by Coverity; CID #30. Bugfix
14113 - Update to the July 1 2011 Maxmind GeoLite Country database.
14116 Changes in version 0.2.2.29-beta - 2011-06-20
14117 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
14118 have bridge lines in their torrc but don't want to use them; gets
14119 us closer to having the control socket feature working on Debian;
14120 and fixes a variety of smaller bugs.
14123 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
14124 When we changed the default behavior to "use bridges if any
14125 are listed in the torrc", we surprised users who had bridges
14126 in their torrc files but who didn't actually want to use them.
14127 Partial resolution for bug 3354.
14130 - Don't attach new streams to old rendezvous circuits after SIGNAL
14131 NEWNYM. Previously, we would keep using an existing rendezvous
14132 circuit if it remained open (i.e. if it were kept open by a
14133 long-lived stream, or if a new stream were attached to it before
14134 Tor could notice that it was old and no longer in use). Bugfix on
14135 0.1.1.15-rc; fixes bug 3375.
14138 - Fix a bug when using ControlSocketsGroupWritable with User. The
14139 directory's group would be checked against the current group, not
14140 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
14141 bugfix on 0.2.2.26-beta.
14142 - Make connection_printf_to_buf()'s behavior sane. Its callers
14143 expect it to emit a CRLF iff the format string ends with CRLF;
14144 it actually emitted a CRLF iff (a) the format string ended with
14145 CRLF or (b) the resulting string was over 1023 characters long or
14146 (c) the format string did not end with CRLF *and* the resulting
14147 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
14148 fixes part of bug 3407.
14149 - Make send_control_event_impl()'s behavior sane. Its callers
14150 expect it to always emit a CRLF at the end of the string; it
14151 might have emitted extra control characters as well. Bugfix on
14152 0.1.1.9-alpha; fixes another part of bug 3407.
14153 - Make crypto_rand_int() check the value of its input correctly.
14154 Previously, it accepted values up to UINT_MAX, but could return a
14155 negative number if given a value above INT_MAX+1. Found by George
14156 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
14157 - Avoid a segfault when reading a malformed circuit build state
14158 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
14160 - When asked about a DNS record type we don't support via a
14161 client DNSPort, reply with NOTIMPL rather than an empty
14162 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
14163 - Fix a rare memory leak during stats writing. Found by coverity.
14166 - Update to the June 1 2011 Maxmind GeoLite Country database.
14168 o Code simplifications and refactoring:
14169 - Remove some dead code as indicated by coverity.
14170 - Remove a few dead assignments during router parsing. Found by
14172 - Add some forgotten return value checks during unit tests. Found
14174 - Don't use 1-bit wide signed bit fields. Found by coverity.
14177 Changes in version 0.2.2.28-beta - 2011-06-04
14178 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
14179 fixed a big bug in whether relays stay in the consensus consistently,
14180 we moved closer to handling bridges and hidden services correctly,
14181 and we started the process of better handling the dreaded "my Vidalia
14182 died, and now my Tor demands a password when I try to reconnect to it"
14186 - Don't decide to make a new descriptor when receiving a HUP signal.
14187 This bug has caused a lot of 0.2.2.x relays to disappear from the
14188 consensus periodically. Fixes the most common case of triggering
14189 bug 1810; bugfix on 0.2.2.7-alpha.
14190 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
14191 - Don't try to build descriptors if "ORPort auto" is set and we
14192 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
14194 - Resolve a crash that occurred when setting BridgeRelay to 1 with
14195 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
14196 - Apply circuit timeouts to opened hidden-service-related circuits
14197 based on the correct start time. Previously, we would apply the
14198 circuit build timeout based on time since the circuit's creation;
14199 it was supposed to be applied based on time since the circuit
14200 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
14201 - Use the same circuit timeout for client-side introduction
14202 circuits as for other four-hop circuits, rather than the timeout
14203 for single-hop directory-fetch circuits; the shorter timeout may
14204 have been appropriate with the static circuit build timeout in
14205 0.2.1.x and earlier, but caused many hidden service access attempts
14206 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
14207 on 0.2.2.2-alpha; fixes another part of bug 1297.
14208 - In ticket 2511 we fixed a case where you could use an unconfigured
14209 bridge if you had configured it as a bridge the last time you ran
14210 Tor. Now fix another edge case: if you had configured it as a bridge
14211 but then switched to a different bridge via the controller, you
14212 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
14216 - Add an __OwningControllerProcess configuration option and a
14217 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
14218 that when it exits, Tor will shut down. Implements feature 3049.
14219 - If "UseBridges 1" is set and no bridges are configured, Tor will
14220 now refuse to build any circuits until some bridges are set.
14221 If "UseBridges auto" is set, Tor will use bridges if they are
14222 configured and we are not running as a server, but otherwise will
14223 make circuits as usual. The new default is "auto". Patch by anonym,
14224 so the Tails LiveCD can stop automatically revealing you as a Tor
14228 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
14229 - Remove a trailing asterisk from "exit-policy/default" in the
14230 output of the control port command "GETINFO info/names". Bugfix
14232 - Use a wide type to hold sockets when built for 64-bit Windows builds.
14234 - Warn when the user configures two HiddenServiceDir lines that point
14235 to the same directory. Bugfix on 0.0.6 (the version introducing
14236 HiddenServiceDir); fixes bug 3289.
14237 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
14238 part of bug 2748; bugfix on 0.2.0.10-alpha.
14239 - Log malformed requests for rendezvous descriptors as protocol
14240 warnings, not warnings. Also, use a more informative log message
14241 in case someone sees it at log level warning without prior
14242 info-level messages. Fixes the other part of bug 2748; bugfix
14244 - Clear the table recording the time of the last request for each
14245 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
14246 Previously, we would clear our HS descriptor cache on SIGNAL
14247 NEWNYM, but if we had previously retrieved a descriptor (or tried
14248 to) from every directory responsible for it, we would refuse to
14249 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
14251 - Fix a log message that said "bits" while displaying a value in
14252 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
14254 - When checking for 1024-bit keys, check for 1024 bits, not 128
14255 bytes. This allows Tor to correctly discard keys of length 1017
14256 through 1023. Bugfix on 0.0.9pre5.
14259 - Relays now log the reason for publishing a new relay descriptor,
14260 so we have a better chance of hunting down instances of bug 1810.
14261 Resolves ticket 3252.
14262 - Revise most log messages that refer to nodes by nickname to
14263 instead use the "$key=nickname at address" format. This should be
14264 more useful, especially since nicknames are less and less likely
14265 to be unique. Resolves ticket 3045.
14266 - Log (at info level) when purging pieces of hidden-service-client
14267 state because of SIGNAL NEWNYM.
14270 - Remove undocumented option "-F" from tor-resolve: it hasn't done
14271 anything since 0.2.1.16-rc.
14274 Changes in version 0.2.2.27-beta - 2011-05-18
14275 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
14276 release, and also adds a few more general bugfixes.
14279 - Fix a crash bug when changing bridges in a running Tor process.
14280 Fixes bug 3213; bugfix on 0.2.2.26-beta.
14281 - When the controller configures a new bridge, don't wait 10 to 60
14282 seconds before trying to fetch its descriptor. Bugfix on
14283 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
14286 - Require that onion keys have exponent 65537 in microdescriptors too.
14287 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
14288 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
14289 Changed the limit to 512 characters by removing base64 newlines.
14290 Fixes bug 2752. Fix by Michael Yakubovich.
14291 - When a client starts or stops using bridges, never use a circuit
14292 that was built before the configuration change. This behavior could
14293 put at risk a user who uses bridges to ensure that her traffic
14294 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
14298 Changes in version 0.2.2.26-beta - 2011-05-17
14299 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
14300 also introduces a new "socksport auto" approach that should make it
14301 easier to run multiple Tors on the same system, and does a lot of
14302 cleanup to get us closer to a release candidate.
14304 o Security/privacy fixes:
14305 - Replace all potentially sensitive memory comparison operations
14306 with versions whose runtime does not depend on the data being
14307 compared. This will help resist a class of attacks where an
14308 adversary can use variations in timing information to learn
14309 sensitive data. Fix for one case of bug 3122. (Safe memcmp
14310 implementation by Robert Ransom based partially on code by DJB.)
14311 - When receiving a hidden service descriptor, check that it is for
14312 the hidden service we wanted. Previously, Tor would store any
14313 hidden service descriptors that a directory gave it, whether it
14314 wanted them or not. This wouldn't have let an attacker impersonate
14315 a hidden service, but it did let directories pre-seed a client
14316 with descriptors that it didn't want. Bugfix on 0.0.6.
14317 - On SIGHUP, do not clear out all TrackHostExits mappings, client
14318 DNS cache entries, and virtual address mappings: that's what
14319 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
14322 - The options SocksPort, ControlPort, and so on now all accept a
14323 value "auto" that opens a socket on an OS-selected port. A
14324 new ControlPortWriteToFile option tells Tor to write its
14325 actual control port or ports to a chosen file. If the option
14326 ControlPortFileGroupReadable is set, the file is created as
14327 group-readable. Now users can run two Tor clients on the same
14328 system without needing to manually mess with parameters. Resolves
14329 part of ticket 3076.
14330 - Set SO_REUSEADDR on all sockets, not just listeners. This should
14331 help busy exit nodes avoid running out of useable ports just
14332 because all the ports have been used in the near past. Resolves
14336 - New "GETINFO net/listeners/(type)" controller command to return
14337 a list of addresses and ports that are bound for listeners for a
14338 given connection type. This is useful when the user has configured
14339 "SocksPort auto" and the controller needs to know which port got
14340 chosen. Resolves another part of ticket 3076.
14341 - Add a new ControlSocketsGroupWritable configuration option: when
14342 it is turned on, ControlSockets are group-writeable by the default
14343 group of the current user. Patch by Jérémy Bobbio; implements
14345 - Tor now refuses to create a ControlSocket in a directory that is
14346 world-readable (or group-readable if ControlSocketsGroupWritable
14347 is 0). This is necessary because some operating systems do not
14348 enforce permissions on an AF_UNIX sockets. Permissions on the
14349 directory holding the socket, however, seems to work everywhere.
14350 - Rate-limit a warning about failures to download v2 networkstatus
14351 documents. Resolves part of bug 1352.
14352 - Backport code from 0.2.3.x that allows directory authorities to
14353 clean their microdescriptor caches. Needed to resolve bug 2230.
14354 - When an HTTPS proxy reports "403 Forbidden", we now explain
14355 what it means rather than calling it an unexpected status code.
14356 Closes bug 2503. Patch from Michael Yakubovich.
14357 - Update to the May 1 2011 Maxmind GeoLite Country database.
14360 - Authorities now clean their microdesc cache periodically and when
14361 reading from disk initially, not only when adding new descriptors.
14362 This prevents a bug where we could lose microdescriptors. Bugfix
14363 on 0.2.2.6-alpha. Fixes bug 2230.
14364 - Do not crash when our configuration file becomes unreadable, for
14365 example due to a permissions change, between when we start up
14366 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
14368 - Avoid a bug that would keep us from replacing a microdescriptor
14369 cache on Windows. (We would try to replace the file while still
14370 holding it open. That's fine on Unix, but Windows doesn't let us
14371 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
14372 - Add missing explanations for the authority-related torrc options
14373 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
14374 man page. Resolves issue 2379.
14375 - As an authority, do not upload our own vote or signature set to
14376 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
14377 it would get flagged as a duplicate. Resolves bug 3026.
14378 - Accept hidden service descriptors if we think we might be a hidden
14379 service directory, regardless of what our consensus says. This
14380 helps robustness, since clients and hidden services can sometimes
14381 have a more up-to-date view of the network consensus than we do,
14382 and if they think that the directory authorities list us a HSDir,
14383 we might actually be one. Related to bug 2732; bugfix on
14385 - When a controller changes TrackHostExits, remove mappings for
14386 hosts that should no longer have their exits tracked. Bugfix on
14388 - When a controller changes VirtualAddrNetwork, remove any mappings
14389 for hosts that were automapped to the old network. Bugfix on
14391 - When a controller changes one of the AutomapHosts* options, remove
14392 any mappings for hosts that should no longer be automapped. Bugfix
14394 - Do not reset the bridge descriptor download status every time we
14395 re-parse our configuration or get a configuration change. Fixes
14396 bug 3019; bugfix on 0.2.0.3-alpha.
14398 o Minor bugfixes (code cleanup):
14399 - When loading the microdesc journal, remember its current size.
14400 In 0.2.2, this helps prevent the microdesc journal from growing
14401 without limit on authorities (who are the only ones to use it in
14402 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
14403 Fix posted by "cypherpunks."
14404 - The microdesc journal is supposed to get rebuilt only if it is
14405 at least _half_ the length of the store, not _twice_ the length
14406 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
14407 - Fix a potential null-pointer dereference while computing a
14408 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
14410 - Avoid a possible null-pointer dereference when rebuilding the mdesc
14411 cache without actually having any descriptors to cache. Bugfix on
14412 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
14413 - If we fail to compute the identity digest of a v3 legacy keypair,
14414 warn, and don't use a buffer-full of junk instead. Bugfix on
14415 0.2.1.1-alpha; fixes bug 3106.
14416 - Resolve an untriggerable issue in smartlist_string_num_isin(),
14417 where if the function had ever in the future been used to check
14418 for the presence of a too-large number, it would have given an
14419 incorrect result. (Fortunately, we only used it for 16-bit
14420 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
14421 - Require that introduction point keys and onion handshake keys
14422 have a public exponent of 65537. Starts to fix bug 3207; bugfix
14425 o Removed features:
14426 - Caches no longer download and serve v2 networkstatus documents
14427 unless FetchV2Networkstatus flag is set: these documents haven't
14428 haven't been used by clients or relays since 0.2.0.x. Resolves
14432 Changes in version 0.2.3.1-alpha - 2011-05-05
14433 Tor 0.2.3.1-alpha adds some new experimental features, including support
14434 for an improved network IO backend, IOCP networking on Windows,
14435 microdescriptor caching, "fast-start" support for streams, and automatic
14436 home router configuration. There are also numerous internal improvements
14437 to try to make the code easier for developers to work with.
14439 This is the first alpha release in a new series, so expect there to be
14440 bugs. Users who would rather test out a more stable branch should
14441 stay with 0.2.2.x for now.
14444 - Tor can now optionally build with the "bufferevents" buffered IO
14445 backend provided by Libevent 2. To use this feature, make sure you
14446 have the latest possible version of Libevent, and pass the
14447 --enable-bufferevents flag to configure when building Tor from
14448 source. This feature will make our networking code more flexible,
14449 let us stack layers on each other, and let us use more efficient
14450 zero-copy transports where available.
14451 - As an experimental feature, Tor can use IOCP for networking on Windows.
14452 Once this code is tuned and optimized, it promises much better
14453 performance than the select-based backend we've used in the past. To
14454 try this feature, you must build Tor with Libevent 2, configure Tor
14455 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
14456 your torrc. There are known bugs here: only try this if you can help
14457 debug it as it breaks.
14458 - The EntryNodes option can now include country codes like {de} or IP
14459 addresses or network masks. Previously we had disallowed these options
14460 because we didn't have an efficient way to keep the list up to
14461 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
14462 - Exit nodes now accept and queue data on not-yet-connected streams.
14463 Previously, the client wasn't allowed to send data until the stream was
14464 connected, which slowed down all connections. This change will enable
14465 clients to perform a "fast-start" on streams and send data without
14466 having to wait for a confirmation that the stream has opened. (Patch
14467 from Ian Goldberg; implements the server side of Proposal 174.)
14468 - Tor now has initial support for automatic port mapping on the many
14469 home routers that support NAT-PMP or UPnP. (Not yet supported on
14470 Windows). To build the support code, you'll need to have libnatpnp
14471 library and/or the libminiupnpc library, and you'll need to enable the
14472 feature specifically by passing "--enable-upnp" and/or
14473 "--enable-natpnp" to configure. To turn it on, use the new
14474 PortForwarding option.
14475 - Caches now download, cache, and serve multiple "flavors" of the
14476 consensus, including a flavor that describes microdescriptors.
14477 - Caches now download, cache, and serve microdescriptors -- small
14478 summaries of router descriptors that are authenticated by all of the
14479 directory authorities. Once enough caches are running this code,
14480 clients will be able to save significant amounts of directory bandwidth
14481 by downloading microdescriptors instead of router descriptors.
14484 - Make logging resolution configurable with a new LogTimeGranularity
14485 option, and change the default from 1 millisecond to 1 second.
14486 Implements enhancement 1668.
14487 - We log which torrc file we're using on startup. Implements ticket
14489 - Ordinarily, Tor does not count traffic from private addresses (like
14490 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
14491 There is now a new option, CountPrivateBandwidth, to disable this
14492 behavior. Patch from Daniel Cagara.
14493 - New --enable-static-tor configure option for building Tor as
14494 statically as possible. Idea, general hackery and thoughts from
14495 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
14497 - If you set the NumCPUs option to 0, Tor will now try to detect how
14498 many CPUs you have. This is the new default behavior.
14499 - Turn on directory request statistics by default and include them in
14500 extra-info descriptors. Don't break if we have no GeoIP database.
14501 - Relays that set "ConnDirectionStatistics 1" write statistics on the
14502 bidirectional use of connections to disk every 24 hours.
14503 - Add a GeoIP file digest to the extra-info descriptor. Implements
14505 - The NodeFamily option -- which let you declare that you want to
14506 consider nodes to be part of a family whether they list themselves
14507 that way or not -- now allows IP address ranges and country codes.
14508 - Add a new 'Heartbeat' log message type to periodically log a message
14509 describing Tor's status at level Notice. This feature is meant for
14510 operators who log at notice, and want to make sure that their Tor
14511 server is still working. Implementation by George Kadianakis.
14513 o Minor bugfixes (on 0.2.2.25-alpha):
14514 - When loading the microdesc journal, remember its current size.
14515 In 0.2.2, this helps prevent the microdesc journal from growing
14516 without limit on authorities (who are the only ones to use it in
14517 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
14518 Fix posted by "cypherpunks."
14519 - The microdesc journal is supposed to get rebuilt only if it is
14520 at least _half_ the length of the store, not _twice_ the length
14521 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
14522 - If as an authority we fail to compute the identity digest of a v3
14523 legacy keypair, warn, and don't use a buffer-full of junk instead.
14524 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
14525 - Authorities now clean their microdesc cache periodically and when
14526 reading from disk initially, not only when adding new descriptors.
14527 This prevents a bug where we could lose microdescriptors. Bugfix
14530 o Minor features (controller):
14531 - Add a new SIGNAL event to the controller interface so that
14532 controllers can be notified when Tor handles a signal. Resolves
14533 issue 1955. Patch by John Brooks.
14534 - Add a new GETINFO option to get total bytes read and written. Patch
14535 from pipe, revised by atagar. Resolves ticket 2345.
14536 - Implement some GETINFO controller fields to provide information about
14537 the Tor process's pid, euid, username, and resource limits.
14540 - Our build system requires automake 1.6 or later to create the
14541 Makefile.in files. Previously, you could have used 1.4.
14542 This only affects developers and people building Tor from git;
14543 people who build Tor from the source distribution without changing
14544 the Makefile.am files should be fine.
14545 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
14546 so on. This is more robust against some of the failure modes
14547 associated with running the autotools pieces on their own.
14549 o Minor packaging issues:
14550 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
14551 already created. Patch from Andreas Stieger. Fixes bug 2573.
14553 o Code simplifications and refactoring:
14554 - A major revision to our internal node-selecting and listing logic.
14555 Tor already had at least two major ways to look at the question of
14556 "which Tor servers do we know about": a list of router descriptors,
14557 and a list of entries in the current consensus. With
14558 microdescriptors, we're adding a third. Having so many systems
14559 without an abstraction layer over them was hurting the codebase.
14560 Now, we have a new "node_t" abstraction that presents a consistent
14561 interface to a client's view of a Tor node, and holds (nearly) all
14562 of the mutable state formerly in routerinfo_t and routerstatus_t.
14563 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
14564 no longer link against Libevent: they never used it, but
14565 our library structure used to force them to link it.
14567 o Removed features:
14568 - Remove some old code to work around even older versions of Tor that
14569 used forked processes to handle DNS requests. Such versions of Tor
14570 are no longer in use as servers.
14572 o Documentation fixes:
14573 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
14574 - Add missing documentation for the authority-related torrc options
14575 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
14579 Changes in version 0.2.2.25-alpha - 2011-04-29
14580 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
14581 robust, routers no longer overreport their bandwidth, Win7 should crash
14582 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
14583 now prevents hidden service-related activity from being linkable. It
14584 provides more information to Vidalia so you can see if your bridge is
14585 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
14586 StrictNodes configuration options to make them more reliable, more
14587 understandable, and more regularly applied. If you use those options,
14588 please see the revised documentation for them in the manual page.
14591 - Relays were publishing grossly inflated bandwidth values because
14592 they were writing their state files wrong--now they write the
14593 correct value. Also, resume reading bandwidth history from the
14594 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
14595 - Improve hidden service robustness: When we find that we have
14596 extended a hidden service's introduction circuit to a relay not
14597 listed as an introduction point in the HS descriptor we currently
14598 have, retry with an introduction point from the current
14599 descriptor. Previously we would just give up. Fixes bugs 1024 and
14600 1930; bugfix on 0.2.0.10-alpha.
14601 - Clients now stop trying to use an exit node associated with a given
14602 destination by TrackHostExits if they fail to reach that exit node.
14603 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
14604 - Fix crash bug on platforms where gmtime and localtime can return
14605 NULL. Windows 7 users were running into this one. Fixes part of bug
14606 2077. Bugfix on all versions of Tor. Found by boboper.
14608 o Security and stability fixes:
14609 - Don't double-free a parsable, but invalid, microdescriptor, even if
14610 it is followed in the blob we're parsing by an unparsable
14611 microdescriptor. Fixes an issue reported in a comment on bug 2954.
14612 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
14613 - If the Nickname configuration option isn't given, Tor would pick a
14614 nickname based on the local hostname as the nickname for a relay.
14615 Because nicknames are not very important in today's Tor and the
14616 "Unnamed" nickname has been implemented, this is now problematic
14617 behavior: It leaks information about the hostname without being
14618 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
14619 introduced the Unnamed nickname. Reported by tagnaq.
14620 - Fix an uncommon assertion failure when running with DNSPort under
14621 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
14622 - Avoid linkability based on cached hidden service descriptors: forget
14623 all hidden service descriptors cached as a client when processing a
14624 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
14627 - Export GeoIP information on bridge usage to controllers even if we
14628 have not yet been running for 24 hours. Now Vidalia bridge operators
14629 can get more accurate and immediate feedback about their
14630 contributions to the network.
14632 o Major features and bugfixes (node selection):
14633 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
14634 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
14635 options. Previously, we had been ambiguous in describing what
14636 counted as an "exit" node, and what operations exactly "StrictNodes
14637 0" would permit. This created confusion when people saw nodes built
14638 through unexpected circuits, and made it hard to tell real bugs from
14639 surprises. Now the intended behavior is:
14640 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
14641 a node that delivers user traffic outside the Tor network.
14642 . "Entry", in the context of EntryNodes, means a node used as the
14643 first hop of a multihop circuit. It doesn't include direct
14644 connections to directory servers.
14645 . "ExcludeNodes" applies to all nodes.
14646 . "StrictNodes" changes the behavior of ExcludeNodes only. When
14647 StrictNodes is set, Tor should avoid all nodes listed in
14648 ExcludeNodes, even when it will make user requests fail. When
14649 StrictNodes is *not* set, then Tor should follow ExcludeNodes
14650 whenever it can, except when it must use an excluded node to
14651 perform self-tests, connect to a hidden service, provide a
14652 hidden service, fulfill a .exit request, upload directory
14653 information, or fetch directory information.
14654 Collectively, the changes to implement the behavior fix bug 1090.
14655 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
14656 a node is listed in both, it's treated as excluded.
14657 - ExcludeNodes now applies to directory nodes -- as a preference if
14658 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
14659 Don't exclude all the directory authorities and set StrictNodes to 1
14660 unless you really want your Tor to break.
14661 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
14662 - ExcludeExitNodes now overrides .exit requests.
14663 - We don't use bridges listed in ExcludeNodes.
14664 - When StrictNodes is 1:
14665 . We now apply ExcludeNodes to hidden service introduction points
14666 and to rendezvous points selected by hidden service users. This
14667 can make your hidden service less reliable: use it with caution!
14668 . If we have used ExcludeNodes on ourself, do not try relay
14669 reachability self-tests.
14670 . If we have excluded all the directory authorities, we will not
14671 even try to upload our descriptor if we're a relay.
14672 . Do not honor .exit requests to an excluded node.
14673 - Remove a misfeature that caused us to ignore the Fast/Stable flags
14674 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
14675 - When the set of permitted nodes changes, we now remove any mappings
14676 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
14678 - We never cannibalize a circuit that had excluded nodes on it, even
14679 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
14680 - Revert a change where we would be laxer about attaching streams to
14681 circuits than when building the circuits. This was meant to prevent
14682 a set of bugs where streams were never attachable, but our improved
14683 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
14684 - Keep track of how many times we launch a new circuit to handle a
14685 given stream. Too many launches could indicate an inconsistency
14686 between our "launch a circuit to handle this stream" logic and our
14687 "attach this stream to one of the available circuits" logic.
14688 - Improve log messages related to excluded nodes.
14691 - Fix a spurious warning when moving from a short month to a long
14692 month on relays with month-based BandwidthAccounting. Bugfix on
14693 0.2.2.17-alpha; fixes bug 3020.
14694 - When a client finds that an origin circuit has run out of 16-bit
14695 stream IDs, we now mark it as unusable for new streams. Previously,
14696 we would try to close the entire circuit. Bugfix on 0.0.6.
14697 - Add a forgotten cast that caused a compile warning on OS X 10.6.
14698 Bugfix on 0.2.2.24-alpha.
14699 - Be more careful about reporting the correct error from a failed
14700 connect() system call. Under some circumstances, it was possible to
14701 look at an incorrect value for errno when sending the end reason.
14702 Bugfix on 0.1.0.1-rc.
14703 - Correctly handle an "impossible" overflow cases in connection byte
14704 counting, where we write or read more than 4GB on an edge connection
14705 in a single second. Bugfix on 0.1.2.8-beta.
14706 - Correct the warning displayed when a rendezvous descriptor exceeds
14707 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
14709 - Clients and hidden services now use HSDir-flagged relays for hidden
14710 service descriptor downloads and uploads even if the relays have no
14711 DirPort set and the client has disabled TunnelDirConns. This will
14712 eventually allow us to give the HSDir flag to relays with no
14713 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
14714 - Downgrade "no current certificates known for authority" message from
14715 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
14716 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
14717 2917. Bugfix on 0.1.1.1-alpha.
14718 - Only limit the lengths of single HS descriptors, even when multiple
14719 HS descriptors are published to an HSDir relay in a single POST
14720 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
14721 - Write the current time into the LastWritten line in our state file,
14722 rather than the time from the previous write attempt. Also, stop
14723 trying to use a time of -1 in our log statements. Fixes bug 3039;
14724 bugfix on 0.2.2.14-alpha.
14725 - Be more consistent in our treatment of file system paths. "~" should
14726 get expanded to the user's home directory in the Log config option.
14727 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
14728 feature for the -f and --DataDirectory options.
14731 - Make sure every relay writes a state file at least every 12 hours.
14732 Previously, a relay could go for weeks without writing its state
14733 file, and on a crash could lose its bandwidth history, capacity
14734 estimates, client country statistics, and so on. Addresses bug 3012.
14735 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
14736 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
14737 clients are already deprecated because of security bugs.
14738 - Don't allow v0 hidden service authorities to act as clients.
14739 Required by fix for bug 3000.
14740 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
14741 by fix for bug 3000.
14742 - Ensure that no empty [dirreq-](read|write)-history lines are added
14743 to an extrainfo document. Implements ticket 2497.
14745 o Code simplification and refactoring:
14746 - Remove workaround code to handle directory responses from servers
14747 that had bug 539 (they would send HTTP status 503 responses _and_
14748 send a body too). Since only server versions before
14749 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
14750 keep the workaround in place.
14751 - Remove the old 'fuzzy time' logic. It was supposed to be used for
14752 handling calculations where we have a known amount of clock skew and
14753 an allowed amount of unknown skew. But we only used it in three
14754 places, and we never adjusted the known/unknown skew values. This is
14755 still something we might want to do someday, but if we do, we'll
14756 want to do it differently.
14757 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
14758 None of the cases where we did this before were wrong, but by making
14759 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
14760 - Use GetTempDir to find the proper temporary directory location on
14761 Windows when generating temporary files for the unit tests. Patch by
14765 Changes in version 0.2.2.24-alpha - 2011-04-08
14766 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
14767 prevented Tor clients from effectively using "multihomed" bridges,
14768 that is, bridges that listen on multiple ports or IP addresses so users
14769 can continue to use some of their addresses even if others get blocked.
14772 - Fix a bug where bridge users who configure the non-canonical
14773 address of a bridge automatically switch to its canonical
14774 address. If a bridge listens at more than one address, it should be
14775 able to advertise those addresses independently and any non-blocked
14776 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
14778 - If you configured Tor to use bridge A, and then quit and
14779 configured Tor to use bridge B instead, it would happily continue
14780 to use bridge A if it's still reachable. While this behavior is
14781 a feature if your goal is connectivity, in some scenarios it's a
14782 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
14783 - Directory authorities now use data collected from their own
14784 uptime observations when choosing whether to assign the HSDir flag
14785 to relays, instead of trusting the uptime value the relay reports in
14786 its descriptor. This change helps prevent an attack where a small
14787 set of nodes with frequently-changing identity keys can blackhole
14788 a hidden service. (Only authorities need upgrade; others will be
14789 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
14792 - When we restart our relay, we might get a successful connection
14793 from the outside before we've started our reachability tests,
14794 triggering a warning: "ORPort found reachable, but I have no
14795 routerinfo yet. Failing to inform controller of success." This
14796 bug was harmless unless Tor is running under a controller
14797 like Vidalia, in which case the controller would never get a
14798 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
14800 - Make directory authorities more accurate at recording when
14801 relays that have failed several reachability tests became
14802 unreachable, so we can provide more accuracy at assigning Stable,
14803 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
14804 - Fix an issue that prevented static linking of libevent on
14805 some platforms (notably Linux). Fixes bug 2698; bugfix on
14806 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
14807 the --with-static-libevent configure option).
14808 - We now ask the other side of a stream (the client or the exit)
14809 for more data on that stream when the amount of queued data on
14810 that stream dips low enough. Previously, we wouldn't ask the
14811 other side for more data until either it sent us more data (which
14812 it wasn't supposed to do if it had exhausted its window!) or we
14813 had completely flushed all our queued data. This flow control fix
14814 should improve throughput. Fixes bug 2756; bugfix on the earliest
14815 released versions of Tor (svn commit r152).
14816 - Avoid a double-mark-for-free warning when failing to attach a
14817 transparent proxy connection. (We thought we had fixed this in
14818 0.2.2.23-alpha, but it turns out our fix was checking the wrong
14819 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
14820 bug) and 0.2.2.23-alpha (the incorrect fix).
14821 - When warning about missing zlib development packages during compile,
14822 give the correct package names. Bugfix on 0.2.0.1-alpha.
14825 - Directory authorities now log the source of a rejected POSTed v3
14826 networkstatus vote.
14827 - Make compilation with clang possible when using
14828 --enable-gcc-warnings by removing two warning options that clang
14829 hasn't implemented yet and by fixing a few warnings. Implements
14831 - When expiring circuits, use microsecond timers rather than
14832 one-second timers. This can avoid an unpleasant situation where a
14833 circuit is launched near the end of one second and expired right
14834 near the beginning of the next, and prevent fluctuations in circuit
14836 - Use computed circuit-build timeouts to decide when to launch
14837 parallel introduction circuits for hidden services. (Previously,
14838 we would retry after 15 seconds.)
14839 - Update to the April 1 2011 Maxmind GeoLite Country database.
14842 - Create the /var/run/tor directory on startup on OpenSUSE if it is
14843 not already created. Patch from Andreas Stieger. Fixes bug 2573.
14845 o Documentation changes:
14846 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
14847 - Resolve all doxygen warnings except those for missing documentation.
14849 - Add doxygen documentation for more functions, fields, and types.
14852 Changes in version 0.2.2.23-alpha - 2011-03-08
14853 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
14854 they restart they don't lose their bandwidth capacity estimate. This
14855 release also fixes a diverse set of user-facing bugs, ranging from
14856 relays overrunning their rate limiting to clients falsely warning about
14857 clock skew to bridge descriptor leaks by our bridge directory authority.
14860 - Stop sending a CLOCK_SKEW controller status event whenever
14861 we fetch directory information from a relay that has a wrong clock.
14862 Instead, only inform the controller when it's a trusted authority
14863 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
14864 the rest of bug 1074.
14865 - Fix an assert in parsing router descriptors containing IPv6
14866 addresses. This one took down the directory authorities when
14867 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
14868 - Make the bridge directory authority refuse to answer directory
14869 requests for "all" descriptors. It used to include bridge
14870 descriptors in its answer, which was a major information leak.
14871 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
14872 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
14873 Tor would ignore their RelayBandwidthBurst setting,
14874 potentially using more bandwidth than expected. Bugfix on
14875 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
14876 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
14877 hidserv" in her torrc. The 'hidserv' argument never controlled
14878 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
14881 - Relays now save observed peak bandwidth throughput rates to their
14882 state file (along with total usage, which was already saved)
14883 so that they can determine their correct estimated bandwidth on
14884 restart. Resolves bug 1863, where Tor relays would reset their
14885 estimated bandwidth to 0 after restarting.
14886 - Directory authorities now take changes in router IP address and
14887 ORPort into account when determining router stability. Previously,
14888 if a router changed its IP or ORPort, the authorities would not
14889 treat it as having any downtime for the purposes of stability
14890 calculation, whereas clients would experience downtime since the
14891 change could take a while to propagate to them. Resolves issue 1035.
14892 - Enable Address Space Layout Randomization (ASLR) and Data Execution
14893 Prevention (DEP) by default on Windows to make it harder for
14894 attackers to exploit vulnerabilities. Patch from John Brooks.
14896 o Minor bugfixes (on 0.2.1.x and earlier):
14897 - Fix a rare crash bug that could occur when a client was configured
14898 with a large number of bridges. Fixes bug 2629; bugfix on
14899 0.2.1.2-alpha. Bugfix by trac user "shitlei".
14900 - Avoid a double mark-for-free warning when failing to attach a
14901 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
14903 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
14904 found by "cypherpunks". This bug was introduced before the first
14905 Tor release, in svn commit r110.
14906 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
14907 don't mention them in the manpage. Fixes bug 2450; issue
14908 spotted by keb and G-Lo.
14909 - Fix a bug in bandwidth history state parsing that could have been
14910 triggered if a future version of Tor ever changed the timing
14911 granularity at which bandwidth history is measured. Bugfix on
14912 Tor 0.1.1.11-alpha.
14913 - When a relay decides that its DNS is too broken for it to serve
14914 as an exit server, it advertised itself as a non-exit, but
14915 continued to act as an exit. This could create accidental
14916 partitioning opportunities for users. Instead, if a relay is
14917 going to advertise reject *:* as its exit policy, it should
14918 really act with exit policy "reject *:*". Fixes bug 2366.
14919 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
14920 - In the special case where you configure a public exit relay as your
14921 bridge, Tor would be willing to use that exit relay as the last
14922 hop in your circuit as well. Now we fail that circuit instead.
14923 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
14924 - Fix a bug with our locking implementation on Windows that couldn't
14925 correctly detect when a file was already locked. Fixes bug 2504,
14926 bugfix on 0.2.1.6-alpha.
14927 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
14928 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
14930 - Set target port in get_interface_address6() correctly. Bugfix
14931 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
14932 - Directory authorities are now more robust to hops back in time
14933 when calculating router stability. Previously, if a run of uptime
14934 or downtime appeared to be negative, the calculation could give
14935 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
14937 - Fix an assert that got triggered when using the TestingTorNetwork
14938 configuration option and then issuing a GETINFO config-text control
14939 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
14941 o Minor bugfixes (on 0.2.2.x):
14942 - Clients should not weight BadExit nodes as Exits in their node
14943 selection. Similarly, directory authorities should not count BadExit
14944 bandwidth as Exit bandwidth when computing bandwidth-weights.
14945 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
14946 - Correctly clear our dir_read/dir_write history when there is an
14947 error parsing any bw history value from the state file. Bugfix on
14948 Tor 0.2.2.15-alpha.
14949 - Resolve a bug in verifying signatures of directory objects
14950 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
14951 Fixes bug 2409. Found by "piebeer".
14952 - Bridge authorities no longer crash on SIGHUP when they try to
14953 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
14957 - Log less aggressively about circuit timeout changes, and improve
14958 some other circuit timeout messages. Resolves bug 2004.
14959 - Log a little more clearly about the times at which we're no longer
14960 accepting new connections. Resolves bug 2181.
14961 - Reject attempts at the client side to open connections to private
14962 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
14963 a randomly chosen exit node. Attempts to do so are always
14964 ill-defined, generally prevented by exit policies, and usually
14965 in error. This will also help to detect loops in transparent
14966 proxy configurations. You can disable this feature by setting
14967 "ClientRejectInternalAddresses 0" in your torrc.
14968 - Always treat failure to allocate an RSA key as an unrecoverable
14970 - Update to the March 1 2011 Maxmind GeoLite Country database.
14972 o Minor features (log subsystem):
14973 - Add documentation for configuring logging at different severities in
14974 different log domains. We've had this feature since 0.2.1.1-alpha,
14975 but for some reason it never made it into the manpage. Fixes
14977 - Make it simpler to specify "All log domains except for A and B".
14978 Previously you needed to say "[*,~A,~B]". Now you can just say
14980 - Add a "LogMessageDomains 1" option to include the domains of log
14981 messages along with the messages. Without this, there's no way
14982 to use log domains without reading the source or doing a lot
14985 o Packaging changes:
14986 - Stop shipping the Tor specs files and development proposal documents
14987 in the tarball. They are now in a separate git repository at
14988 git://git.torproject.org/torspec.git
14991 Changes in version 0.2.1.30 - 2011-02-23
14992 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
14993 change is a slight tweak to Tor's TLS handshake that makes relays
14994 and bridges that run this new version reachable from Iran again.
14995 We don't expect this tweak will win the arms race long-term, but it
14996 buys us time until we roll out a better solution.
14999 - Stop sending a CLOCK_SKEW controller status event whenever
15000 we fetch directory information from a relay that has a wrong clock.
15001 Instead, only inform the controller when it's a trusted authority
15002 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
15003 the rest of bug 1074.
15004 - Fix a bounds-checking error that could allow an attacker to
15005 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
15006 Found by "piebeer".
15007 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
15008 Tor would ignore their RelayBandwidthBurst setting,
15009 potentially using more bandwidth than expected. Bugfix on
15010 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
15011 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
15012 hidserv" in her torrc. The 'hidserv' argument never controlled
15013 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
15016 - Adjust our TLS Diffie-Hellman parameters to match those used by
15018 - Update to the February 1 2011 Maxmind GeoLite Country database.
15021 - Check for and reject overly long directory certificates and
15022 directory tokens before they have a chance to hit any assertions.
15023 Bugfix on 0.2.1.28. Found by "doorss".
15024 - Bring the logic that gathers routerinfos and assesses the
15025 acceptability of circuits into line. This prevents a Tor OP from
15026 getting locked in a cycle of choosing its local OR as an exit for a
15027 path (due to a .exit request) and then rejecting the circuit because
15028 its OR is not listed yet. It also prevents Tor clients from using an
15029 OR running in the same instance as an exit (due to a .exit request)
15030 if the OR does not meet the same requirements expected of an OR
15031 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
15033 o Packaging changes:
15034 - Stop shipping the Tor specs files and development proposal documents
15035 in the tarball. They are now in a separate git repository at
15036 git://git.torproject.org/torspec.git
15037 - Do not include Git version tags as though they are SVN tags when
15038 generating a tarball from inside a repository that has switched
15039 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
15042 Changes in version 0.2.2.22-alpha - 2011-01-25
15043 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
15044 main other change is a slight tweak to Tor's TLS handshake that makes
15045 relays and bridges that run this new version reachable from Iran again.
15046 We don't expect this tweak will win the arms race long-term, but it
15047 will buy us a bit more time until we roll out a better solution.
15050 - Fix a bounds-checking error that could allow an attacker to
15051 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
15052 Found by "piebeer".
15053 - Don't assert when changing from bridge to relay or vice versa
15054 via the controller. The assert happened because we didn't properly
15055 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
15056 bug 2433. Reported by bastik.
15059 - Adjust our TLS Diffie-Hellman parameters to match those used by
15061 - Provide a log message stating which geoip file we're parsing
15062 instead of just stating that we're parsing the geoip file.
15063 Implements ticket 2432.
15066 - Check for and reject overly long directory certificates and
15067 directory tokens before they have a chance to hit any assertions.
15068 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
15071 Changes in version 0.2.2.21-alpha - 2011-01-15
15072 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
15073 continues our recent code security audit work. The main fix resolves
15074 a remote heap overflow vulnerability that can allow remote code
15075 execution (CVE-2011-0427). Other fixes address a variety of assert
15076 and crash bugs, most of which we think are hard to exploit remotely.
15078 o Major bugfixes (security), also included in 0.2.1.29:
15079 - Fix a heap overflow bug where an adversary could cause heap
15080 corruption. This bug probably allows remote code execution
15081 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
15083 - Prevent a denial-of-service attack by disallowing any
15084 zlib-compressed data whose compression factor is implausibly
15085 high. Fixes part of bug 2324; reported by "doorss".
15086 - Zero out a few more keys in memory before freeing them. Fixes
15087 bug 2384 and part of bug 2385. These key instances found by
15088 "cypherpunks", based on Andrew Case's report about being able
15089 to find sensitive data in Tor's memory space if you have enough
15090 permissions. Bugfix on 0.0.2pre9.
15092 o Major bugfixes (crashes), also included in 0.2.1.29:
15093 - Prevent calls to Libevent from inside Libevent log handlers.
15094 This had potential to cause a nasty set of crashes, especially
15095 if running Libevent with debug logging enabled, and running
15096 Tor with a controller watching for low-severity log messages.
15097 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
15098 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
15099 underflow errors there too. Fixes the other part of bug 2324.
15100 - Fix a bug where we would assert if we ever had a
15101 cached-descriptors.new file (or another file read directly into
15102 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
15103 on 0.2.1.25. Found by doorss.
15104 - Fix some potential asserts and parsing issues with grossly
15105 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
15108 o Minor bugfixes (other), also included in 0.2.1.29:
15109 - Fix a bug with handling misformed replies to reverse DNS lookup
15110 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
15111 bug reported by doorss.
15112 - Fix compilation on mingw when a pthreads compatibility library
15113 has been installed. (We don't want to use it, so we shouldn't
15114 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
15115 - Fix a bug where we would declare that we had run out of virtual
15116 addresses when the address space was only half-exhausted. Bugfix
15118 - Correctly handle the case where AutomapHostsOnResolve is set but
15119 no virtual addresses are available. Fixes bug 2328; bugfix on
15120 0.1.2.1-alpha. Bug found by doorss.
15121 - Correctly handle wrapping around when we run out of virtual
15122 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
15124 o Minor features, also included in 0.2.1.29:
15125 - Update to the January 1 2011 Maxmind GeoLite Country database.
15126 - Introduce output size checks on all of our decryption functions.
15128 o Build changes, also included in 0.2.1.29:
15129 - Tor does not build packages correctly with Automake 1.6 and earlier;
15130 added a check to Makefile.am to make sure that we're building with
15131 Automake 1.7 or later.
15132 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
15133 because we built it with a too-old version of automake. Thus that
15134 release broke ./configure --enable-openbsd-malloc, which is popular
15135 among really fast exit relays on Linux.
15137 o Major bugfixes, new in 0.2.2.21-alpha:
15138 - Prevent crash/heap corruption when the cbtnummodes consensus
15139 parameter is set to 0 or large values. Fixes bug 2317; bugfix
15142 o Major features, new in 0.2.2.21-alpha:
15143 - Introduce minimum/maximum values that clients will believe
15144 from the consensus. Now we'll have a better chance to avoid crashes
15145 or worse when a consensus param has a weird value.
15147 o Minor features, new in 0.2.2.21-alpha:
15148 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
15149 used on bridges, and it makes bridge scanning somewhat easier.
15150 - If writing the state file to disk fails, wait up to an hour before
15151 retrying again, rather than trying again each second. Fixes bug
15152 2346; bugfix on Tor 0.1.1.3-alpha.
15153 - Make Libevent log messages get delivered to controllers later,
15154 and not from inside the Libevent log handler. This prevents unsafe
15155 reentrant Libevent calls while still letting the log messages
15157 - Detect platforms that brokenly use a signed size_t, and refuse to
15158 build there. Found and analyzed by doorss and rransom.
15159 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
15162 o Minor bugfixes, new in 0.2.2.21-alpha:
15163 - Handle SOCKS messages longer than 128 bytes long correctly, rather
15164 than waiting forever for them to finish. Fixes bug 2330; bugfix
15165 on 0.2.0.16-alpha. Found by doorss.
15166 - Add assertions to check for overflow in arguments to
15167 base32_encode() and base32_decode(); fix a signed-unsigned
15168 comparison there too. These bugs are not actually reachable in Tor,
15169 but it's good to prevent future errors too. Found by doorss.
15170 - Correctly detect failures to create DNS requests when using Libevent
15171 versions before v2. (Before Libevent 2, we used our own evdns
15172 implementation. Its return values for Libevent's evdns_resolve_*()
15173 functions are not consistent with those from Libevent.) Fixes bug
15174 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
15176 o Documentation, new in 0.2.2.21-alpha:
15177 - Document the default socks host and port (127.0.0.1:9050) for
15181 Changes in version 0.2.1.29 - 2011-01-15
15182 Tor 0.2.1.29 continues our recent code security audit work. The main
15183 fix resolves a remote heap overflow vulnerability that can allow remote
15184 code execution. Other fixes address a variety of assert and crash bugs,
15185 most of which we think are hard to exploit remotely.
15187 o Major bugfixes (security):
15188 - Fix a heap overflow bug where an adversary could cause heap
15189 corruption. This bug probably allows remote code execution
15190 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
15192 - Prevent a denial-of-service attack by disallowing any
15193 zlib-compressed data whose compression factor is implausibly
15194 high. Fixes part of bug 2324; reported by "doorss".
15195 - Zero out a few more keys in memory before freeing them. Fixes
15196 bug 2384 and part of bug 2385. These key instances found by
15197 "cypherpunks", based on Andrew Case's report about being able
15198 to find sensitive data in Tor's memory space if you have enough
15199 permissions. Bugfix on 0.0.2pre9.
15201 o Major bugfixes (crashes):
15202 - Prevent calls to Libevent from inside Libevent log handlers.
15203 This had potential to cause a nasty set of crashes, especially
15204 if running Libevent with debug logging enabled, and running
15205 Tor with a controller watching for low-severity log messages.
15206 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
15207 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
15208 underflow errors there too. Fixes the other part of bug 2324.
15209 - Fix a bug where we would assert if we ever had a
15210 cached-descriptors.new file (or another file read directly into
15211 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
15212 on 0.2.1.25. Found by doorss.
15213 - Fix some potential asserts and parsing issues with grossly
15214 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
15217 o Minor bugfixes (other):
15218 - Fix a bug with handling misformed replies to reverse DNS lookup
15219 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
15220 bug reported by doorss.
15221 - Fix compilation on mingw when a pthreads compatibility library
15222 has been installed. (We don't want to use it, so we shouldn't
15223 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
15224 - Fix a bug where we would declare that we had run out of virtual
15225 addresses when the address space was only half-exhausted. Bugfix
15227 - Correctly handle the case where AutomapHostsOnResolve is set but
15228 no virtual addresses are available. Fixes bug 2328; bugfix on
15229 0.1.2.1-alpha. Bug found by doorss.
15230 - Correctly handle wrapping around to when we run out of virtual
15231 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
15232 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
15233 because we built it with a too-old version of automake. Thus that
15234 release broke ./configure --enable-openbsd-malloc, which is popular
15235 among really fast exit relays on Linux.
15238 - Update to the January 1 2011 Maxmind GeoLite Country database.
15239 - Introduce output size checks on all of our decryption functions.
15242 - Tor does not build packages correctly with Automake 1.6 and earlier;
15243 added a check to Makefile.am to make sure that we're building with
15244 Automake 1.7 or later.
15247 Changes in version 0.2.2.20-alpha - 2010-12-17
15248 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
15249 exploitable bugs. We also fix a variety of other significant bugs,
15250 change the IP address for one of our directory authorities, and update
15251 the minimum version that Tor relays must run to join the network.
15254 - Fix a remotely exploitable bug that could be used to crash instances
15255 of Tor remotely by overflowing on the heap. Remote-code execution
15256 hasn't been confirmed, but can't be ruled out. Everyone should
15257 upgrade. Bugfix on the 0.1.1 series and later.
15258 - Fix a bug that could break accounting on 64-bit systems with large
15259 time_t values, making them hibernate for impossibly long intervals.
15260 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
15261 - Fix a logic error in directory_fetches_from_authorities() that
15262 would cause all _non_-exits refusing single-hop-like circuits
15263 to fetch from authorities, when we wanted to have _exits_ fetch
15264 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
15266 - Fix a stream fairness bug that would cause newer streams on a given
15267 circuit to get preference when reading bytes from the origin or
15268 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
15269 introduced before the first Tor release, in svn revision r152.
15271 o Directory authority changes:
15272 - Change IP address and ports for gabelmoo (v3 directory authority).
15275 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
15276 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
15277 - Fix an off-by-one error in calculating some controller command
15278 argument lengths. Fortunately, this mistake is harmless since
15279 the controller code does redundant NUL termination too. Found by
15280 boboper. Bugfix on 0.1.1.1-alpha.
15281 - Do not dereference NULL if a bridge fails to build its
15282 extra-info descriptor. Found by an anonymous commenter on
15283 Trac. Bugfix on 0.2.2.19-alpha.
15286 - Update to the December 1 2010 Maxmind GeoLite Country database.
15287 - Directory authorities now reject relays running any versions of
15288 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
15289 known bugs that keep RELAY_EARLY cells from working on rendezvous
15290 circuits. Followup to fix for bug 2081.
15291 - Directory authorities now reject relays running any version of Tor
15292 older than 0.2.0.26-rc. That version is the earliest that fetches
15293 current directory information correctly. Fixes bug 2156.
15294 - Report only the top 10 ports in exit-port stats in order not to
15295 exceed the maximum extra-info descriptor length of 50 KB. Implements
15299 Changes in version 0.2.1.28 - 2010-12-17
15300 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
15301 exploitable bugs. We also took this opportunity to change the IP address
15302 for one of our directory authorities, and to update the geoip database
15306 - Fix a remotely exploitable bug that could be used to crash instances
15307 of Tor remotely by overflowing on the heap. Remote-code execution
15308 hasn't been confirmed, but can't be ruled out. Everyone should
15309 upgrade. Bugfix on the 0.1.1 series and later.
15311 o Directory authority changes:
15312 - Change IP address and ports for gabelmoo (v3 directory authority).
15315 - Update to the December 1 2010 Maxmind GeoLite Country database.
15318 Changes in version 0.2.1.27 - 2010-11-23
15319 Yet another OpenSSL security patch broke its compatibility with Tor:
15320 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
15321 also took this opportunity to fix several crash bugs, integrate a new
15322 directory authority, and update the bundled GeoIP database.
15325 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
15326 No longer set the tlsext_host_name extension on server SSL objects;
15327 but continue to set it on client SSL objects. Our goal in setting
15328 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
15329 bugfix on 0.2.1.1-alpha.
15330 - Do not log messages to the controller while shrinking buffer
15331 freelists. Doing so would sometimes make the controller connection
15332 try to allocate a buffer chunk, which would mess up the internals
15333 of the freelist and cause an assertion failure. Fixes bug 1125;
15334 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
15335 - Learn our external IP address when we're a relay or bridge, even if
15336 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
15337 where we introduced bridge relays that don't need to publish to
15338 be useful. Fixes bug 2050.
15339 - Do even more to reject (and not just ignore) annotations on
15340 router descriptors received anywhere but from the cache. Previously
15341 we would ignore such annotations at first, but cache them to disk
15342 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
15343 - When you're using bridges and your network goes away and your
15344 bridges get marked as down, recover when you attempt a new socks
15345 connection (if the network is back), rather than waiting up to an
15346 hour to try fetching new descriptors for your bridges. Bugfix on
15347 0.2.0.3-alpha; fixes bug 1981.
15350 - Move to the November 2010 Maxmind GeoLite country db (rather
15351 than the June 2009 ip-to-country GeoIP db) for our statistics that
15352 count how many users relays are seeing from each country. Now we'll
15353 have more accurate data, especially for many African countries.
15355 o New directory authorities:
15356 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
15360 - Fix an assertion failure that could occur in directory caches or
15361 bridge users when using a very short voting interval on a testing
15362 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
15364 - Enforce multiplicity rules when parsing annotations. Bugfix on
15365 0.2.0.8-alpha. Found by piebeer.
15366 - Allow handshaking OR connections to take a full KeepalivePeriod
15367 seconds to handshake. Previously, we would close them after
15368 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
15369 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
15371 - When building with --enable-gcc-warnings on OpenBSD, disable
15372 warnings in system headers. This makes --enable-gcc-warnings
15373 pass on OpenBSD 4.8.
15376 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
15377 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
15378 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
15379 Servers can start sending this code when enough clients recognize
15380 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
15381 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
15382 Patch from mingw-san.
15385 - Remove the old debian/ directory from the main Tor distribution.
15386 The official Tor-for-debian git repository lives at the URL
15387 https://git.torproject.org/debian/tor.git
15388 - Stop shipping the old doc/website/ directory in the tarball. We
15389 changed the website format in late 2010, and what we shipped in
15390 0.2.1.26 really wasn't that useful anyway.
15393 Changes in version 0.2.2.19-alpha - 2010-11-22
15394 Yet another OpenSSL security patch broke its compatibility with Tor:
15395 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
15398 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
15399 No longer set the tlsext_host_name extension on server SSL objects;
15400 but continue to set it on client SSL objects. Our goal in setting
15401 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
15402 bugfix on 0.2.1.1-alpha.
15405 - Try harder not to exceed the maximum length of 50 KB when writing
15406 statistics to extra-info descriptors. This bug was triggered by very
15407 fast relays reporting exit-port, entry, and dirreq statistics.
15408 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
15409 - Publish a router descriptor even if generating an extra-info
15410 descriptor fails. Previously we would not publish a router
15411 descriptor without an extra-info descriptor; this can cause fast
15412 exit relays collecting exit-port statistics to drop from the
15413 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
15416 Changes in version 0.2.2.18-alpha - 2010-11-16
15417 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
15418 us lately, makes unpublished bridge relays able to detect their IP
15419 address, and fixes a wide variety of other bugs to get us much closer
15420 to a stable release.
15423 - Do even more to reject (and not just ignore) annotations on
15424 router descriptors received anywhere but from the cache. Previously
15425 we would ignore such annotations at first, but cache them to disk
15426 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
15427 - Do not log messages to the controller while shrinking buffer
15428 freelists. Doing so would sometimes make the controller connection
15429 try to allocate a buffer chunk, which would mess up the internals
15430 of the freelist and cause an assertion failure. Fixes bug 1125;
15431 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
15432 - Learn our external IP address when we're a relay or bridge, even if
15433 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
15434 where we introduced bridge relays that don't need to publish to
15435 be useful. Fixes bug 2050.
15436 - Maintain separate TLS contexts and certificates for incoming and
15437 outgoing connections in bridge relays. Previously we would use the
15438 same TLS contexts and certs for incoming and outgoing connections.
15439 Bugfix on 0.2.0.3-alpha; addresses bug 988.
15440 - Maintain separate identity keys for incoming and outgoing TLS
15441 contexts in bridge relays. Previously we would use the same
15442 identity keys for incoming and outgoing TLS contexts. Bugfix on
15443 0.2.0.3-alpha; addresses the other half of bug 988.
15444 - Avoid an assertion failure when we as an authority receive a
15445 duplicate upload of a router descriptor that we already have,
15446 but which we previously considered an obsolete descriptor.
15447 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
15448 - Avoid a crash bug triggered by looking at a dangling pointer while
15449 setting the network status consensus. Found by Robert Ransom.
15450 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
15451 - Fix a logic error where servers that _didn't_ act as exits would
15452 try to keep their server lists more aggressively up to date than
15453 exits, when it was supposed to be the other way around. Bugfix
15456 o Minor bugfixes (on Tor 0.2.1.x and earlier):
15457 - When we're trying to guess whether we know our IP address as
15458 a relay, we would log various ways that we failed to guess
15459 our address, but never log that we ended up guessing it
15460 successfully. Now add a log line to help confused and anxious
15461 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
15462 - Bring the logic that gathers routerinfos and assesses the
15463 acceptability of circuits into line. This prevents a Tor OP from
15464 getting locked in a cycle of choosing its local OR as an exit for a
15465 path (due to a .exit request) and then rejecting the circuit because
15466 its OR is not listed yet. It also prevents Tor clients from using an
15467 OR running in the same instance as an exit (due to a .exit request)
15468 if the OR does not meet the same requirements expected of an OR
15469 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
15470 - Correctly describe errors that occur when generating a TLS object.
15471 Previously we would attribute them to a failure while generating a
15472 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
15474 - Enforce multiplicity rules when parsing annotations. Bugfix on
15475 0.2.0.8-alpha. Found by piebeer.
15476 - Fix warnings that newer versions of autoconf produced during
15477 ./autogen.sh. These warnings appear to be harmless in our case,
15478 but they were extremely verbose. Fixes bug 2020.
15480 o Minor bugfixes (on Tor 0.2.2.x):
15481 - Enable protection of small arrays whenever we build with gcc
15482 hardening features, not only when also building with warnings
15483 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
15486 - Make hidden services work better in private Tor networks by not
15487 requiring any uptime to join the hidden service descriptor
15488 DHT. Implements ticket 2088.
15489 - Rate-limit the "your application is giving Tor only an IP address"
15490 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
15491 - When AllowSingleHopExits is set, print a warning to explain to the
15492 relay operator why most clients are avoiding her relay.
15493 - Update to the November 1 2010 Maxmind GeoLite Country database.
15495 o Code simplifications and refactoring:
15496 - When we fixed bug 1038 we had to put in a restriction not to send
15497 RELAY_EARLY cells on rend circuits. This was necessary as long
15498 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
15499 active. Now remove this obsolete check. Resolves bug 2081.
15500 - Some options used different conventions for uppercasing of acronyms
15501 when comparing manpage and source. Fix those in favor of the
15502 manpage, as it makes sense to capitalize acronyms.
15503 - Remove the torrc.complete file. It hasn't been kept up to date
15504 and users will have better luck checking out the manpage.
15505 - Remove the obsolete "NoPublish" option; it has been flagged
15506 as obsolete and has produced a warning since 0.1.1.18-rc.
15507 - Remove everything related to building the expert bundle for OS X.
15508 It has confused many users, doesn't work right on OS X 10.6,
15509 and is hard to get rid of once installed. Resolves bug 1274.
15512 Changes in version 0.2.2.17-alpha - 2010-09-30
15513 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
15514 to use one-hop circuits (which can put the exit relays at higher risk,
15515 plus unbalance the network); fixes a big bug in bandwidth accounting
15516 for relays that want to limit their monthly bandwidth use; fixes a
15517 big pile of bugs in how clients tolerate temporary network failure;
15518 and makes our adaptive circuit build timeout feature (which improves
15519 client performance if your network is fast while not breaking things
15520 if your network is slow) better handle bad networks.
15523 - Exit relays now try harder to block exit attempts from unknown
15524 relays, to make it harder for people to use them as one-hop proxies
15525 a la tortunnel. Controlled by the refuseunknownexits consensus
15526 parameter (currently enabled), or you can override it on your
15527 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
15529 o Major bugfixes (0.2.1.x and earlier):
15530 - Fix a bug in bandwidth accounting that could make us use twice
15531 the intended bandwidth when our interval start changes due to
15532 daylight saving time. Now we tolerate skew in stored vs computed
15533 interval starts: if the start of the period changes by no more than
15534 50% of the period's duration, we remember bytes that we transferred
15535 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
15536 - Always search the Windows system directory for system DLLs, and
15537 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
15538 - When you're using bridges and your network goes away and your
15539 bridges get marked as down, recover when you attempt a new socks
15540 connection (if the network is back), rather than waiting up to an
15541 hour to try fetching new descriptors for your bridges. Bugfix on
15542 0.2.0.3-alpha; fixes bug 1981.
15544 o Major bugfixes (on 0.2.2.x):
15545 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
15547 - Fix a segfault that could happen when operating a bridge relay with
15548 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
15549 - The consensus bandwidth-weights (used by clients to choose fast
15550 relays) entered an unexpected edge case in September where
15551 Exits were much scarcer than Guards, resulting in bad weight
15552 recommendations. Now we compute them using new constraints that
15553 should succeed in all cases. Also alter directory authorities to
15554 not include the bandwidth-weights line if they fail to produce
15555 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
15556 - When weighting bridges during path selection, we used to trust
15557 the bandwidths they provided in their descriptor, only capping them
15558 at 10MB/s. This turned out to be problematic for two reasons:
15559 Bridges could claim to handle a lot more traffic then they
15560 actually would, thus making more clients pick them and have a
15561 pretty effective DoS attack. The other issue is that new bridges
15562 that might not have a good estimate for their bw capacity yet
15563 would not get used at all unless no other bridges are available
15564 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
15566 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
15567 - Ignore cannibalized circuits when recording circuit build times.
15568 This should provide for a minor performance improvement for hidden
15569 service users using 0.2.2.14-alpha, and should remove two spurious
15570 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
15571 - Simplify the logic that causes us to decide if the network is
15572 unavailable for purposes of recording circuit build times. If we
15573 receive no cells whatsoever for the entire duration of a circuit's
15574 full measured lifetime, the network is probably down. Also ignore
15575 one-hop directory fetching circuit timeouts when calculating our
15576 circuit build times. These changes should hopefully reduce the
15577 cases where we see ridiculous circuit build timeouts for people
15578 with spotty wireless connections. Fixes part of bug 1772; bugfix
15580 - Prevent the circuit build timeout from becoming larger than
15581 the maximum build time we have ever seen. Also, prevent the time
15582 period for measurement circuits from becoming larger than twice that
15583 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
15586 - When we run out of directory information such that we can't build
15587 circuits, but then get enough that we can build circuits, log when
15588 we actually construct a circuit, so the user has a better chance of
15589 knowing what's going on. Fixes bug 1362.
15590 - Be more generous with how much bandwidth we'd use up (with
15591 accounting enabled) before entering "soft hibernation". Previously,
15592 we'd refuse new connections and circuits once we'd used up 95% of
15593 our allotment. Now, we use up 95% of our allotment, AND make sure
15594 that we have no more than 500MB (or 3 hours of expected traffic,
15595 whichever is lower) remaining before we enter soft hibernation.
15596 - If we've configured EntryNodes and our network goes away and/or all
15597 our entrynodes get marked down, optimistically retry them all when
15598 a new socks application request appears. Fixes bug 1882.
15599 - Add some more defensive programming for architectures that can't
15600 handle unaligned integer accesses. We don't know of any actual bugs
15601 right now, but that's the best time to fix them. Fixes bug 1943.
15602 - Support line continuations in the torrc config file. If a line
15603 ends with a single backslash character, the newline is ignored, and
15604 the configuration value is treated as continuing on the next line.
15607 o Minor bugfixes (on 0.2.1.x and earlier):
15608 - For bandwidth accounting, calculate our expected bandwidth rate
15609 based on the time during which we were active and not in
15610 soft-hibernation during the last interval. Previously, we were
15611 also considering the time spent in soft-hibernation. If this
15612 was a long time, we would wind up underestimating our bandwidth
15613 by a lot, and skewing our wakeup time towards the start of the
15614 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
15616 o Minor bugfixes (on 0.2.2.x):
15617 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
15618 which were disabled by the circuit build timeout changes in
15619 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
15620 - Make sure we don't warn about missing bandwidth weights when
15621 choosing bridges or other relays not in the consensus. Bugfix on
15622 0.2.2.10-alpha; fixes bug 1805.
15623 - In our logs, do not double-report signatures from unrecognized
15624 authorities both as "from unknown authority" and "not
15625 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
15628 Changes in version 0.2.2.16-alpha - 2010-09-17
15629 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
15630 evident at exit relays), and also continues to resolve all the little
15631 bugs that have been filling up trac lately.
15633 o Major bugfixes (stream-level fairness):
15634 - When receiving a circuit-level SENDME for a blocked circuit, try
15635 to package cells fairly from all the streams that had previously
15636 been blocked on that circuit. Previously, we had started with the
15637 oldest stream, and allowed each stream to potentially exhaust
15638 the circuit's package window. This gave older streams on any
15639 given circuit priority over newer ones. Fixes bug 1937. Detected
15640 originally by Camilo Viecco. This bug was introduced before the
15641 first Tor release, in svn commit r152: it is the new winner of
15642 the longest-lived bug prize.
15643 - When the exit relay got a circuit-level sendme cell, it started
15644 reading on the exit streams, even if had 500 cells queued in the
15645 circuit queue already, so the circuit queue just grew and grew in
15646 some cases. We fix this by not re-enabling reading on receipt of a
15647 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
15648 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
15650 - Newly created streams were allowed to read cells onto circuits,
15651 even if the circuit's cell queue was blocked and waiting to drain.
15652 This created potential unfairness, as older streams would be
15653 blocked, but newer streams would gladly fill the queue completely.
15654 We add code to detect this situation and prevent any stream from
15655 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
15659 - Update to the September 1 2010 Maxmind GeoLite Country database.
15660 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
15661 not. This would lead to a cookie that is still not group readable.
15662 Closes bug 1843. Suggested by katmagic.
15663 - When logging a rate-limited warning, we now mention how many messages
15664 got suppressed since the last warning.
15665 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
15666 do individual connection-level rate limiting of clients. The torrc
15667 config options with the same names trump the consensus params, if
15668 both are present. Replaces the old "bwconnrate" and "bwconnburst"
15669 consensus params which were broken from 0.2.2.7-alpha through
15670 0.2.2.14-alpha. Closes bug 1947.
15671 - When a router changes IP address or port, authorities now launch
15672 a new reachability test for it. Implements ticket 1899.
15673 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
15674 2 no signature, 4 required" messages about consensus signatures
15675 easier to read, and make sure they get logged at the same severity
15676 as the messages explaining which keys are which. Fixes bug 1290.
15677 - Don't warn when we have a consensus that we can't verify because
15678 of missing certificates, unless those certificates are ones
15679 that we have been trying and failing to download. Fixes bug 1145.
15680 - If you configure your bridge with a known identity fingerprint,
15681 and the bridge authority is unreachable (as it is in at least
15682 one country now), fall back to directly requesting the descriptor
15683 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
15685 - When building with --enable-gcc-warnings on OpenBSD, disable
15686 warnings in system headers. This makes --enable-gcc-warnings
15687 pass on OpenBSD 4.8.
15689 o Minor bugfixes (on 0.2.1.x and earlier):
15690 - Authorities will now attempt to download consensuses if their
15691 own efforts to make a live consensus have failed. This change
15692 means authorities that restart will fetch a valid consensus, and
15693 it means authorities that didn't agree with the current consensus
15694 will still fetch and serve it if it has enough signatures. Bugfix
15695 on 0.2.0.9-alpha; fixes bug 1300.
15696 - Ensure DNS requests launched by "RESOLVE" commands from the
15697 controller respect the __LeaveStreamsUnattached setconf options. The
15698 same goes for requests launched via DNSPort or transparent
15699 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
15700 - Allow handshaking OR connections to take a full KeepalivePeriod
15701 seconds to handshake. Previously, we would close them after
15702 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
15703 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
15705 - Rate-limit "Failed to hand off onionskin" warnings.
15706 - Never relay a cell for a circuit we have already destroyed.
15707 Between marking a circuit as closeable and finally closing it,
15708 it may have been possible for a few queued cells to get relayed,
15709 even though they would have been immediately dropped by the next
15710 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
15711 - Never queue a cell for a circuit that's already been marked
15713 - Never vote for a server as "Running" if we have a descriptor for
15714 it claiming to be hibernating, and that descriptor was published
15715 more recently than our last contact with the server. Bugfix on
15716 0.2.0.3-alpha; fixes bug 911.
15717 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
15720 o Minor bugfixes (on 0.2.2.x):
15721 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
15722 down if a directory fetch fails and you've configured either
15723 bridges or EntryNodes. The intent was to mark the relay as down
15724 _unless_ you're using bridges or EntryNodes, since if you are
15725 then you could quickly run out of entry points.
15726 - Fix the Windows directory-listing code. A bug introduced in
15727 0.2.2.14-alpha could make Windows directory servers forget to load
15728 some of their cached v2 networkstatus files.
15729 - Really allow clients to use relays as bridges. Fixes bug 1776;
15730 bugfix on 0.2.2.15-alpha.
15731 - Demote a warn to info that happens when the CellStatistics option
15732 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
15733 Reported by Moritz Bartl.
15734 - On Windows, build correctly either with or without Unicode support.
15735 This is necessary so that Tor can support fringe platforms like
15736 Windows 98 (which has no Unicode), or Windows CE (which has no
15737 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
15740 - Add a unit test for cross-platform directory-listing code.
15743 Changes in version 0.2.2.15-alpha - 2010-08-18
15744 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
15745 fixes a variety of other bugs that were preventing performance
15746 experiments from moving forward, fixes several bothersome memory leaks,
15747 and generally closes a lot of smaller bugs that have been filling up
15751 - Stop assigning the HSDir flag to relays that disable their
15752 DirPort (and thus will refuse to answer directory requests). This
15753 fix should dramatically improve the reachability of hidden services:
15754 hidden services and hidden service clients pick six HSDir relays
15755 to store and retrieve the hidden service descriptor, and currently
15756 about half of the HSDir relays will refuse to work. Bugfix on
15757 0.2.0.10-alpha; fixes part of bug 1693.
15758 - The PerConnBWRate and Burst config options, along with the
15759 bwconnrate and bwconnburst consensus params, initialized each conn's
15760 token bucket values only when the connection is established. Now we
15761 update them if the config options change, and update them every time
15762 we get a new consensus. Otherwise we can encounter an ugly edge
15763 case where we initialize an OR conn to client-level bandwidth,
15764 but then later the relay joins the consensus and we leave it
15765 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
15766 - Fix a regression that caused Tor to rebind its ports if it receives
15767 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
15770 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
15771 should give us approximately 40-50% more Guard-flagged nodes,
15772 improving the anonymity the Tor network can provide and also
15773 decreasing the dropoff in throughput that relays experience when
15774 they first get the Guard flag.
15775 - Allow enabling or disabling the *Statistics config options while
15779 - Update to the August 1 2010 Maxmind GeoLite Country database.
15780 - Have the controller interface give a more useful message than
15781 "Internal Error" in response to failed GETINFO requests.
15782 - Warn when the same option is provided more than once in a torrc
15783 file, on the command line, or in a single SETCONF statement, and
15784 the option is one that only accepts a single line. Closes bug 1384.
15785 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
15786 Patch from mingw-san.
15787 - Add support for the country code "{??}" in torrc options like
15788 ExcludeNodes, to indicate all routers of unknown country. Closes
15790 - Relays report the number of bytes spent on answering directory
15791 requests in extra-info descriptors similar to {read,write}-history.
15792 Implements enhancement 1790.
15794 o Minor bugfixes (on 0.2.1.x and earlier):
15795 - Complain if PublishServerDescriptor is given multiple arguments that
15796 include 0 or 1. This configuration will be rejected in the future.
15797 Bugfix on 0.2.0.1-alpha; closes bug 1107.
15798 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
15799 Bugfix on 0.2.0.13-alpha; closes bug 928.
15800 - Change "Application request when we're believed to be offline."
15801 notice to "Application request when we haven't used client
15802 functionality lately.", to clarify that it's not an error. Bugfix
15803 on 0.0.9.3; fixes bug 1222.
15804 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
15805 would return "551 Internal error" rather than "552 Unrecognized key
15806 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
15807 - Users can't configure a regular relay to be their bridge. It didn't
15808 work because when Tor fetched the bridge descriptor, it found
15809 that it already had it, and didn't realize that the purpose of the
15810 descriptor had changed. Now we replace routers with a purpose other
15811 than bridge with bridge descriptors when fetching them. Bugfix on
15812 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
15813 refetch the descriptor with router purpose 'general', disabling
15815 - Fix a rare bug in rend_fn unit tests: we would fail a test when
15816 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
15817 on 0.2.0.10-alpha; fixes bug 1808.
15818 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
15819 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
15820 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
15821 Servers can start sending this code when enough clients recognize
15822 it. Also update the spec to reflect this new reason. Bugfix on
15823 0.1.0.1-rc; fixes part of bug 1793.
15824 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
15825 when we switch from being a public relay to a bridge. Otherwise
15826 there will still be clients that see the relay in their consensus,
15827 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
15829 - Instead of giving an assertion failure on an internal mismatch
15830 on estimated freelist size, just log a BUG warning and try later.
15831 Mitigates but does not fix bug 1125.
15832 - Fix an assertion failure that could occur in caches or bridge users
15833 when using a very short voting interval on a testing network.
15834 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
15836 o Minor bugfixes (on 0.2.2.x):
15837 - Alter directory authorities to always consider Exit-flagged nodes
15838 as potential Guard nodes in their votes. The actual decision to
15839 use Exits as Guards is done in the consensus bandwidth weights.
15840 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
15841 - When the controller is reporting the purpose of circuits that
15842 didn't finish building before the circuit build timeout, it was
15843 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
15844 - Our libevent version parsing code couldn't handle versions like
15845 1.4.14b-stable and incorrectly warned the user about using an
15846 old and broken version of libevent. Treat 1.4.14b-stable like
15847 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
15849 - Don't use substitution references like $(VAR:MOD) when
15850 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
15851 '$(:x)' to 'x' rather than the empty string. This bites us in
15852 doc/ when configured with --disable-asciidoc. Bugfix on
15853 0.2.2.9-alpha; fixes bug 1773.
15854 - Remove a spurious hidden service server-side log notice about
15855 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
15857 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
15859 - Correctly report written bytes on linked connections. Found while
15860 implementing 1790. Bugfix on 0.2.2.4-alpha.
15861 - Fix three memory leaks: one in circuit_build_times_parse_state(),
15862 one in dirvote_add_signatures_to_pending_consensus(), and one every
15863 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
15864 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
15866 o Code simplifications and refactoring:
15867 - Take a first step towards making or.h smaller by splitting out
15868 function definitions for all source files in src/or/. Leave
15869 structures and defines in or.h for now.
15870 - Remove a bunch of unused function declarations as well as a block of
15871 #if 0'd code from the unit tests. Closes bug 1824.
15872 - New unit tests for exit-port history statistics; refactored exit
15873 statistics code to be more easily tested.
15874 - Remove the old debian/ directory from the main Tor distribution.
15875 The official Tor-for-debian git repository lives at the URL
15876 https://git.torproject.org/debian/tor.git
15879 Changes in version 0.2.2.14-alpha - 2010-07-12
15880 Tor 0.2.2.14-alpha greatly improves client-side handling of
15881 circuit build timeouts, which are used to estimate speed and improve
15882 performance. We also move to a much better GeoIP database, port Tor to
15883 Windows CE, introduce new compile flags that improve code security,
15884 add an eighth v3 directory authority, and address a lot of more
15888 - Tor directory authorities no longer crash when started with a
15889 cached-microdesc-consensus file in their data directory. Bugfix
15890 on 0.2.2.6-alpha; fixes bug 1532.
15891 - Treat an unset $HOME like an empty $HOME rather than triggering an
15892 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
15893 - Ignore negative and large circuit build timeout values that can
15894 happen during a suspend or hibernate. These values caused various
15895 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
15896 - Alter calculation of Pareto distribution parameter 'Xm' for
15897 Circuit Build Timeout learning to use the weighted average of the
15898 top N=3 modes (because we have three entry guards). Considering
15899 multiple modes should improve the timeout calculation in some cases,
15900 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
15902 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
15903 right censored distribution model. This approach improves over the
15904 synthetic timeout generation approach that was producing insanely
15905 high timeout values. Now we calculate build timeouts using truncated
15906 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
15907 - Do not close circuits that are under construction when they reach
15908 the circuit build timeout. Instead, leave them building (but do not
15909 use them) for up until the time corresponding to the 95th percentile
15910 on the Pareto CDF or 60 seconds, whichever is greater. This is done
15911 to provide better data for the new Pareto model. This percentile
15912 can be controlled by the consensus.
15915 - Move to the June 2010 Maxmind GeoLite country db (rather than the
15916 June 2009 ip-to-country GeoIP db) for our statistics that count
15917 how many users relays are seeing from each country. Now we have
15918 more accurate data for many African countries.
15919 - Port Tor to build and run correctly on Windows CE systems, using
15920 the wcecompat library. Contributed by Valerio Lupi.
15921 - New "--enable-gcc-hardening" ./configure flag (off by default)
15922 to turn on gcc compile time hardening options. It ensures
15923 that signed ints have defined behavior (-fwrapv), enables
15924 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
15925 with canaries (-fstack-protector-all), turns on ASLR protection if
15926 supported by the kernel (-fPIE, -pie), and adds additional security
15927 related warnings. Verified to work on Mac OS X and Debian Lenny.
15928 - New "--enable-linker-hardening" ./configure flag (off by default)
15929 to turn on ELF specific hardening features (relro, now). This does
15930 not work with Mac OS X or any other non-ELF binary format.
15932 o New directory authorities:
15933 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
15937 - New config option "WarnUnsafeSocks 0" disables the warning that
15938 occurs whenever Tor receives a socks handshake using a version of
15939 the socks protocol that can only provide an IP address (rather
15940 than a hostname). Setups that do DNS locally over Tor are fine,
15941 and we shouldn't spam the logs in that case.
15942 - Convert the HACKING file to asciidoc, and add a few new sections
15943 to it, explaining how we use Git, how we make changelogs, and
15944 what should go in a patch.
15945 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
15946 event, to give information on the current rate of circuit timeouts
15947 over our stored history.
15948 - Add ability to disable circuit build time learning via consensus
15949 parameter and via a LearnCircuitBuildTimeout config option. Also
15950 automatically disable circuit build time calculation if we are
15951 either a AuthoritativeDirectory, or if we fail to write our state
15952 file. Fixes bug 1296.
15953 - More gracefully handle corrupt state files, removing asserts
15954 in favor of saving a backup and resetting state.
15955 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
15959 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
15961 - When a2x fails, mention that the user could disable manpages instead
15962 of trying to fix their asciidoc installation.
15963 - Where available, use Libevent 2.0's periodic timers so that our
15964 once-per-second cleanup code gets called even more closely to
15965 once per second than it would otherwise. Fixes bug 943.
15966 - If you run a bridge that listens on multiple IP addresses, and
15967 some user configures a bridge address that uses a different IP
15968 address than your bridge writes in its router descriptor, and the
15969 user doesn't specify an identity key, their Tor would discard the
15970 descriptor because "it isn't one of our configured bridges", and
15971 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
15972 Bugfix on 0.2.0.3-alpha.
15973 - If OpenSSL fails to make a duplicate of a private or public key, log
15974 an error message and try to exit cleanly. May help with debugging
15975 if bug 1209 ever remanifests.
15976 - Save a couple bytes in memory allocation every time we escape
15977 certain characters in a string. Patch from Florian Zumbiehl.
15978 - Make it explicit that we don't cannibalize one-hop circuits. This
15979 happens in the wild, but doesn't turn out to be a problem because
15980 we fortunately don't use those circuits. Many thanks to outofwords
15981 for the initial analysis and to swissknife who confirmed that
15982 two-hop circuits are actually created.
15983 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
15984 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
15985 - Eliminate a case where a circuit build time warning was displayed
15986 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
15989 Changes in version 0.2.1.26 - 2010-05-02
15990 Tor 0.2.1.26 addresses the recent connection and memory overload
15991 problems we've been seeing on relays, especially relays with their
15992 DirPort open. If your relay has been crashing, or you turned it off
15993 because it used too many resources, give this release a try.
15995 This release also fixes yet another instance of broken OpenSSL libraries
15996 that was causing some relays to drop out of the consensus.
15999 - Teach relays to defend themselves from connection overload. Relays
16000 now close idle circuits early if it looks like they were intended
16001 for directory fetches. Relays are also more aggressive about closing
16002 TLS connections that have no circuits on them. Such circuits are
16003 unlikely to be re-used, and tens of thousands of them were piling
16004 up at the fast relays, causing the relays to run out of sockets
16005 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
16006 their directory fetches over TLS).
16007 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
16008 that claim to be earlier than 0.9.8m, but which have in reality
16009 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
16010 behavior. Possible fix for some cases of bug 1346.
16011 - Directory mirrors were fetching relay descriptors only from v2
16012 directory authorities, rather than v3 authorities like they should.
16013 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
16014 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
16017 - Finally get rid of the deprecated and now harmful notion of "clique
16018 mode", where directory authorities maintain TLS connections to
16022 - In the util/threads test, no longer free the test_mutex before all
16023 worker threads have finished. Bugfix on 0.2.1.6-alpha.
16024 - The master thread could starve the worker threads quite badly on
16025 certain systems, causing them to run only partially in the allowed
16026 window. This resulted in test failures. Now the master thread sleeps
16027 occasionally for a few microseconds while the two worker-threads
16028 compete for the mutex. Bugfix on 0.2.0.1-alpha.
16031 Changes in version 0.2.2.13-alpha - 2010-04-24
16032 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
16033 problems we've been seeing on relays, especially relays with their
16034 DirPort open. If your relay has been crashing, or you turned it off
16035 because it used too many resources, give this release a try.
16038 - Teach relays to defend themselves from connection overload. Relays
16039 now close idle circuits early if it looks like they were intended
16040 for directory fetches. Relays are also more aggressive about closing
16041 TLS connections that have no circuits on them. Such circuits are
16042 unlikely to be re-used, and tens of thousands of them were piling
16043 up at the fast relays, causing the relays to run out of sockets
16044 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
16045 their directory fetches over TLS).
16048 - Finally get rid of the deprecated and now harmful notion of "clique
16049 mode", where directory authorities maintain TLS connections to
16051 - Directory authorities now do an immediate reachability check as soon
16052 as they hear about a new relay. This change should slightly reduce
16053 the time between setting up a relay and getting listed as running
16054 in the consensus. It should also improve the time between setting
16055 up a bridge and seeing use by bridge users.
16056 - Directory authorities no longer launch a TLS connection to every
16057 relay as they startup. Now that we have 2k+ descriptors cached,
16058 the resulting network hiccup is becoming a burden. Besides,
16059 authorities already avoid voting about Running for the first half
16060 hour of their uptime.
16063 Changes in version 0.2.2.12-alpha - 2010-04-20
16064 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
16065 handle and vote on descriptors. It was causing relays to drop out of
16069 - Many relays have been falling out of the consensus lately because
16070 not enough authorities know about their descriptor for them to get
16071 a majority of votes. When we deprecated the v2 directory protocol,
16072 we got rid of the only way that v3 authorities can hear from each
16073 other about other descriptors. Now authorities examine every v3
16074 vote for new descriptors, and fetch them from that authority. Bugfix
16076 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
16077 and a warning in or.h related to bandwidth_weight_rule_t that
16078 prevented clean compile on OS X. Fixes bug 1363; bugfix on
16080 - Fix a segfault on relays when DirReqStatistics is enabled
16081 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
16085 - Demote a confusing TLS warning that relay operators might get when
16086 someone tries to talk to their OrPort. It is neither the operator's
16087 fault nor can they do anything about it. Fixes bug 1364; bugfix
16091 Changes in version 0.2.2.11-alpha - 2010-04-15
16092 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
16093 libraries that was causing some relays to drop out of the consensus.
16096 - Directory mirrors were fetching relay descriptors only from v2
16097 directory authorities, rather than v3 authorities like they should.
16098 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
16099 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
16100 - Fix a parsing error that made every possible value of
16101 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
16102 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
16103 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
16104 about the option without breaking older ones.
16105 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
16106 that claim to be earlier than 0.9.8m, but which have in reality
16107 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
16108 behavior. Possible fix for some cases of bug 1346.
16111 - Experiment with a more aggressive approach to preventing clients
16112 from making one-hop exit streams. Exit relays who want to try it
16113 out can set "RefuseUnknownExits 1" in their torrc, and then look
16114 for "Attempt by %s to open a stream" log messages. Let us know
16116 - Add support for statically linking zlib by specifying
16117 --enable-static-zlib, to go with our support for statically linking
16118 openssl and libevent. Resolves bug 1358.
16121 - Fix a segfault that happens whenever a Tor client that is using
16122 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
16124 - When we cleaned up the contrib/tor-exit-notice.html file, we left
16125 out the first line. Fixes bug 1295.
16126 - When building the manpage from a tarball, we required asciidoc, but
16127 the asciidoc -> roff/html conversion was already done for the
16128 tarball. Make 'make' complain only when we need asciidoc (either
16129 because we're compiling directly from git, or because we altered
16130 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
16131 - When none of the directory authorities vote on any params, Tor
16132 segfaulted when trying to make the consensus from the votes. We
16133 didn't trigger the bug in practice, because authorities do include
16134 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
16137 - In the util/threads test, no longer free the test_mutex before all
16138 worker threads have finished. Bugfix on 0.2.1.6-alpha.
16139 - The master thread could starve the worker threads quite badly on
16140 certain systems, causing them to run only partially in the allowed
16141 window. This resulted in test failures. Now the master thread sleeps
16142 occasionally for a few microseconds while the two worker-threads
16143 compete for the mutex. Bugfix on 0.2.0.1-alpha.
16146 Changes in version 0.2.2.10-alpha - 2010-03-07
16147 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
16148 could prevent relays from guessing their IP address correctly. It also
16149 starts the groundwork for another client-side performance boost, since
16150 currently we're not making efficient use of relays that have both the
16151 Guard flag and the Exit flag.
16154 - Fix a regression from our patch for bug 1244 that caused relays
16155 to guess their IP address incorrectly if they didn't set Address
16156 in their torrc and/or their address fails to resolve. Bugfix on
16157 0.2.2.9-alpha; fixes bug 1269.
16159 o Major features (performance):
16160 - Directory authorities now compute consensus weightings that instruct
16161 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
16162 and no flag. Clients that use these weightings will distribute
16163 network load more evenly across these different relay types. The
16164 weightings are in the consensus so we can change them globally in
16165 the future. Extra thanks to "outofwords" for finding some nasty
16166 security bugs in the first implementation of this feature.
16168 o Minor features (performance):
16169 - Always perform router selections using weighted relay bandwidth,
16170 even if we don't need a high capacity circuit at the time. Non-fast
16171 circuits now only differ from fast ones in that they can use relays
16172 not marked with the Fast flag. This "feature" could turn out to
16173 be a horrible bug; we should investigate more before it goes into
16177 - Allow disabling building of the manpages. Skipping the manpage
16178 speeds up the build considerably.
16180 o Minor bugfixes (on 0.2.2.x):
16181 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
16182 Bugfix on 0.2.2.9-alpha.
16183 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
16184 config option. Bugfix on 0.2.2.7-alpha.
16185 - Ship the asciidoc-helper file in the tarball, so that people can
16186 build from source if they want to, and touching the .1.txt files
16187 doesn't break the build. Bugfix on 0.2.2.9-alpha.
16189 o Minor bugfixes (on 0.2.1.x or earlier):
16190 - Fix a dereference-then-NULL-check sequence when publishing
16191 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
16193 - Fix another dereference-then-NULL-check sequence. Bugfix on
16194 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
16195 - Make sure we treat potentially not NUL-terminated strings correctly.
16196 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
16198 o Code simplifications and refactoring:
16199 - Fix some urls in the exit notice file and make it XHTML1.1 strict
16200 compliant. Based on a patch from Christian Kujau.
16201 - Don't use sed in asciidoc-helper anymore.
16202 - Make the build process fail if asciidoc cannot be found and
16203 building with asciidoc isn't disabled.
16206 Changes in version 0.2.2.9-alpha - 2010-02-22
16207 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
16208 location of a directory authority, and cleans up a bunch of small bugs.
16210 o Directory authority changes:
16211 - Change IP address for dannenberg (v3 directory authority), and
16212 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
16213 service directory authority) from the list.
16216 - Make Tor work again on the latest OS X: when deciding whether to
16217 use strange flags to turn TLS renegotiation on, detect the OpenSSL
16218 version at run-time, not compile time. We need to do this because
16219 Apple doesn't update its dev-tools headers when it updates its
16220 libraries in a security patch.
16221 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
16222 that could happen on 32-bit platforms with 64-bit time_t. Also fix
16223 a memory leak when requesting a hidden service descriptor we've
16224 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
16226 - Authorities could be tricked into giving out the Exit flag to relays
16227 that didn't allow exiting to any ports. This bug could screw
16228 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
16229 1238. Bug discovered by Martin Kowalczyk.
16230 - When freeing a session key, zero it out completely. We only zeroed
16231 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
16232 patched by ekir. Fixes bug 1254.
16235 - Fix static compilation by listing the openssl libraries in the right
16236 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
16237 - Resume handling .exit hostnames in a special way: originally we
16238 stripped the .exit part and used the requested exit relay. In
16239 0.2.2.1-alpha we stopped treating them in any special way, meaning
16240 if you use a .exit address then Tor will pass it on to the exit
16241 relay. Now we reject the .exit stream outright, since that behavior
16242 might be more expected by the user. Found and diagnosed by Scott
16243 Bennett and Downie on or-talk.
16244 - Don't spam the controller with events when we have no file
16245 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
16246 for log messages was already solved from bug 748.)
16247 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
16249 - Make the DNSPort option work with libevent 2.x. Don't alter the
16250 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
16251 - Emit a GUARD DROPPED controller event for a case we missed.
16252 - Make more fields in the controller protocol case-insensitive, since
16253 control-spec.txt said they were.
16254 - Refactor resolve_my_address() to not use gethostbyname() anymore.
16255 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
16256 - Fix a spec conformance issue: the network-status-version token
16257 must be the first token in a v3 consensus or vote. Discovered by
16258 parakeep. Bugfix on 0.2.0.3-alpha.
16260 o Code simplifications and refactoring:
16261 - Generate our manpage and HTML documentation using Asciidoc. This
16262 change should make it easier to maintain the documentation, and
16263 produce nicer HTML.
16264 - Remove the --enable-iphone option. According to reports from Marco
16265 Bonetti, Tor builds fine without any special tweaking on recent
16266 iPhone SDK versions.
16267 - Removed some unnecessary files from the source distribution. The
16268 AUTHORS file has now been merged into the people page on the
16269 website. The roadmaps and design doc can now be found in the
16270 projects directory in svn.
16271 - Enabled various circuit build timeout constants to be controlled
16272 by consensus parameters. Also set better defaults for these
16273 parameters based on experimentation on broadband and simulated
16274 high latency links.
16277 - The 'EXTENDCIRCUIT' control port command can now be used with
16278 a circ id of 0 and no path. This feature will cause Tor to build
16279 a new 'fast' general purpose circuit using its own path selection
16281 - Added a BUILDTIMEOUT_SET controller event to describe changes
16282 to the circuit build timeout.
16283 - Future-proof the controller protocol a bit by ignoring keyword
16284 arguments we do not recognize.
16285 - Expand homedirs passed to tor-checkkey. This should silence a
16286 coverity complaint about passing a user-supplied string into
16287 open() without checking it.
16290 Changes in version 0.2.1.25 - 2010-03-16
16291 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
16292 prevent relays from guessing their IP address correctly. It also fixes
16293 several minor potential security bugs.
16296 - Fix a regression from our patch for bug 1244 that caused relays
16297 to guess their IP address incorrectly if they didn't set Address
16298 in their torrc and/or their address fails to resolve. Bugfix on
16299 0.2.1.23; fixes bug 1269.
16300 - When freeing a session key, zero it out completely. We only zeroed
16301 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
16302 patched by ekir. Fixes bug 1254.
16305 - Fix a dereference-then-NULL-check sequence when publishing
16306 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
16308 - Fix another dereference-then-NULL-check sequence. Bugfix on
16309 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
16310 - Make sure we treat potentially not NUL-terminated strings correctly.
16311 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
16315 Changes in version 0.2.1.24 - 2010-02-21
16316 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
16320 - Work correctly out-of-the-box with even more vendor-patched versions
16321 of OpenSSL. In particular, make it so Debian and OS X don't need
16322 customized patches to run/build.
16325 Changes in version 0.2.1.23 - 2010-02-13
16326 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
16327 again on the latest OS X, and updates the location of a directory
16330 o Major bugfixes (performance):
16331 - We were selecting our guards uniformly at random, and then weighting
16332 which of our guards we'd use uniformly at random. This imbalance
16333 meant that Tor clients were severely limited on throughput (and
16334 probably latency too) by the first hop in their circuit. Now we
16335 select guards weighted by currently advertised bandwidth. We also
16336 automatically discard guards picked using the old algorithm. Fixes
16337 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
16340 - Make Tor work again on the latest OS X: when deciding whether to
16341 use strange flags to turn TLS renegotiation on, detect the OpenSSL
16342 version at run-time, not compile time. We need to do this because
16343 Apple doesn't update its dev-tools headers when it updates its
16344 libraries in a security patch.
16345 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
16346 that could happen on 32-bit platforms with 64-bit time_t. Also fix
16347 a memory leak when requesting a hidden service descriptor we've
16348 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
16351 o Directory authority changes:
16352 - Change IP address for dannenberg (v3 directory authority), and
16353 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
16354 service directory authority) from the list.
16357 - Refactor resolve_my_address() to not use gethostbyname() anymore.
16358 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
16361 - Avoid a mad rush at the beginning of each month when each client
16362 rotates half of its guards. Instead we spread the rotation out
16363 throughout the month, but we still avoid leaving a precise timestamp
16364 in the state file about when we first picked the guard. Improves
16365 over the behavior introduced in 0.1.2.17.
16368 Changes in version 0.2.2.8-alpha - 2010-01-26
16369 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
16370 causing bridge relays to disappear. If you're running a bridge,
16374 - Fix a memory corruption bug on bridges that occured during the
16375 inclusion of stats data in extra-info descriptors. Also fix the
16376 interface for geoip_get_bridge_stats* to prevent similar bugs in
16377 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
16378 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
16381 - Ignore OutboundBindAddress when connecting to localhost.
16382 Connections to localhost need to come _from_ localhost, or else
16383 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
16387 Changes in version 0.2.2.7-alpha - 2010-01-19
16388 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
16389 as laying the groundwork for further relay-side performance fixes. It
16390 also starts cleaning up client behavior with respect to the EntryNodes,
16391 ExitNodes, and StrictNodes config options.
16393 This release also rotates two directory authority keys, due to a
16394 security breach of some of the Torproject servers.
16396 o Directory authority changes:
16397 - Rotate keys (both v3 identity and relay identity) for moria1
16400 o Major features (performance):
16401 - We were selecting our guards uniformly at random, and then weighting
16402 which of our guards we'd use uniformly at random. This imbalance
16403 meant that Tor clients were severely limited on throughput (and
16404 probably latency too) by the first hop in their circuit. Now we
16405 select guards weighted by currently advertised bandwidth. We also
16406 automatically discard guards picked using the old algorithm. Fixes
16407 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
16408 - When choosing which cells to relay first, relays can now favor
16409 circuits that have been quiet recently, to provide lower latency
16410 for low-volume circuits. By default, relays enable or disable this
16411 feature based on a setting in the consensus. You can override
16412 this default by using the new "CircuitPriorityHalflife" config
16413 option. Design and code by Ian Goldberg, Can Tang, and Chris
16415 - Add separate per-conn write limiting to go with the per-conn read
16416 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
16417 but never per-conn write limits.
16418 - New consensus params "bwconnrate" and "bwconnburst" to let us
16419 rate-limit client connections as they enter the network. It's
16420 controlled in the consensus so we can turn it on and off for
16421 experiments. It's starting out off. Based on proposal 163.
16423 o Major features (relay selection options):
16424 - Switch to a StrictNodes config option, rather than the previous
16425 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
16426 "StrictExcludeNodes" option.
16427 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
16428 change during a config reload, mark and discard all our origin
16429 circuits. This fix should address edge cases where we change the
16430 config options and but then choose a circuit that we created before
16432 - If EntryNodes or ExitNodes are set, be more willing to use an
16433 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
16435 - Make EntryNodes config option much more aggressive even when
16436 StrictNodes is not set. Before it would prepend your requested
16437 entrynodes to your list of guard nodes, but feel free to use others
16438 after that. Now it chooses only from your EntryNodes if any of
16439 those are available, and only falls back to others if a) they're
16440 all down and b) StrictNodes is not set.
16441 - Now we refresh your entry guards from EntryNodes at each consensus
16442 fetch -- rather than just at startup and then they slowly rot as
16443 the network changes.
16446 - Stop bridge directory authorities from answering dbg-stability.txt
16447 directory queries, which would let people fetch a list of all
16448 bridge identities they track. Bugfix on 0.2.1.6-alpha.
16451 - Log a notice when we get a new control connection. Now it's easier
16452 for security-conscious users to recognize when a local application
16453 is knocking on their controller door. Suggested by bug 1196.
16454 - New config option "CircuitStreamTimeout" to override our internal
16455 timeout schedule for how many seconds until we detach a stream from
16456 a circuit and try a new circuit. If your network is particularly
16457 slow, you might want to set this to a number like 60.
16458 - New controller command "getinfo config-text". It returns the
16459 contents that Tor would write if you send it a SAVECONF command,
16460 so the controller can write the file to disk itself.
16461 - New options for SafeLogging to allow scrubbing only log messages
16462 generated while acting as a relay.
16463 - Ship the bridges spec file in the tarball too.
16464 - Avoid a mad rush at the beginning of each month when each client
16465 rotates half of its guards. Instead we spread the rotation out
16466 throughout the month, but we still avoid leaving a precise timestamp
16467 in the state file about when we first picked the guard. Improves
16468 over the behavior introduced in 0.1.2.17.
16470 o Minor bugfixes (compiling):
16471 - Fix compilation on OS X 10.3, which has a stub mlockall() but
16472 hides it. Bugfix on 0.2.2.6-alpha.
16473 - Fix compilation on Solaris by removing support for the
16474 DisableAllSwap config option. Solaris doesn't have an rlimit for
16475 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
16478 o Minor bugfixes (crashes):
16479 - Do not segfault when writing buffer stats when we haven't observed
16480 a single circuit to report about. Found by Fabian Lanze. Bugfix on
16482 - If we're in the pathological case where there's no exit bandwidth
16483 but there is non-exit bandwidth, or no guard bandwidth but there
16484 is non-guard bandwidth, don't crash during path selection. Bugfix
16486 - Fix an impossible-to-actually-trigger buffer overflow in relay
16487 descriptor generation. Bugfix on 0.1.0.15.
16489 o Minor bugfixes (privacy):
16490 - Fix an instance where a Tor directory mirror might accidentally
16491 log the IP address of a misbehaving Tor client. Bugfix on
16493 - Don't list Windows capabilities in relay descriptors. We never made
16494 use of them, and maybe it's a bad idea to publish them. Bugfix
16497 o Minor bugfixes (other):
16498 - Resolve an edge case in path weighting that could make us misweight
16499 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
16500 - Fix statistics on client numbers by country as seen by bridges that
16501 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
16502 intervals instead of variable 12-to-48-hour intervals.
16503 - After we free an internal connection structure, overwrite it
16504 with a different memory value than we use for overwriting a freed
16505 internal circuit structure. Should help with debugging. Suggested
16507 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
16510 o Removed features:
16511 - Remove the HSAuthorityRecordStats option that version 0 hidden
16512 service authorities could have used to track statistics of overall
16513 hidden service usage.
16516 Changes in version 0.2.1.22 - 2010-01-19
16517 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
16518 authorities -- it would tell you its whole history of bridge descriptors
16519 if you make the right directory request. This stable update also
16520 rotates two of the seven v3 directory authority keys and locations.
16522 o Directory authority changes:
16523 - Rotate keys (both v3 identity and relay identity) for moria1
16527 - Stop bridge directory authorities from answering dbg-stability.txt
16528 directory queries, which would let people fetch a list of all
16529 bridge identities they track. Bugfix on 0.2.1.6-alpha.
16532 Changes in version 0.2.1.21 - 2009-12-21
16533 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
16534 library. If you use Tor on Linux / Unix and you're getting SSL
16535 renegotiation errors, upgrading should help. We also recommend an
16536 upgrade if you're an exit relay.
16539 - Work around a security feature in OpenSSL 0.9.8l that prevents our
16540 handshake from working unless we explicitly tell OpenSSL that we
16541 are using SSL renegotiation safely. We are, of course, but OpenSSL
16542 0.9.8l won't work unless we say we are.
16543 - Avoid crashing if the client is trying to upload many bytes and the
16544 circuit gets torn down at the same time, or if the flip side
16545 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
16548 - Do not refuse to learn about authority certs and v2 networkstatus
16549 documents that are older than the latest consensus. This bug might
16550 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
16551 Spotted and fixed by xmux.
16552 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
16553 trigger platform-specific option misparsing case found by Coverity
16555 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
16556 trigger assert. Fixes bug 1173.
16559 Changes in version 0.2.2.6-alpha - 2009-11-19
16560 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
16561 support for the new lower-footprint "microdescriptor" directory design,
16562 future-proofing our consensus format against new hash functions or
16563 other changes, and an Android port. It also makes Tor compatible with
16564 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
16567 - Directory authorities can now create, vote on, and serve multiple
16568 parallel formats of directory data as part of their voting process.
16569 Partially implements Proposal 162: "Publish the consensus in
16571 - Directory authorities can now agree on and publish small summaries
16572 of router information that clients can use in place of regular
16573 server descriptors. This transition will eventually allow clients
16574 to use far less bandwidth for downloading information about the
16575 network. Begins the implementation of Proposal 158: "Clients
16576 download consensus + microdescriptors".
16577 - The directory voting system is now extensible to use multiple hash
16578 algorithms for signatures and resource selection. Newer formats
16579 are signed with SHA256, with a possibility for moving to a better
16580 hash algorithm in the future.
16581 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
16582 current and future memory pages via mlockall(). On supported
16583 platforms (modern Linux and probably BSD but not Windows or OS X),
16584 this should effectively disable any and all attempts to page out
16585 memory. This option requires that you start your Tor as root --
16586 if you use DisableAllSwap, please consider using the User option
16587 to properly reduce the privileges of your Tor.
16588 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
16589 to help Tor build correctly for Android phones.
16592 - Work around a security feature in OpenSSL 0.9.8l that prevents our
16593 handshake from working unless we explicitly tell OpenSSL that we
16594 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
16595 won't work unless we say we are.
16598 - Fix a crash bug when trying to initialize the evdns module in
16599 Libevent 2. Bugfix on 0.2.1.16-rc.
16600 - Stop logging at severity 'warn' when some other Tor client tries
16601 to establish a circuit with us using weak DH keys. It's a protocol
16602 violation, but that doesn't mean ordinary users need to hear about
16603 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
16604 - Do not refuse to learn about authority certs and v2 networkstatus
16605 documents that are older than the latest consensus. This bug might
16606 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
16607 Spotted and fixed by xmux.
16608 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
16609 - If all authorities restart at once right before a consensus vote,
16610 nobody will vote about "Running", and clients will get a consensus
16611 with no usable relays. Instead, authorities refuse to build a
16612 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
16613 - If your relay can't keep up with the number of incoming create
16614 cells, it would log one warning per failure into your logs. Limit
16615 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
16616 - Bridges now use "reject *:*" as their default exit policy. Bugfix
16617 on 0.2.0.3-alpha; fixes bug 1113.
16618 - Fix a memory leak on directory authorities during voting that was
16619 introduced in 0.2.2.1-alpha. Found via valgrind.
16622 Changes in version 0.2.1.20 - 2009-10-15
16623 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
16624 services at once, prepares for more performance improvements, and
16625 fixes a bunch of smaller bugs.
16627 The Windows and OS X bundles also include a more recent Vidalia,
16628 and switch from Privoxy to Polipo.
16630 The OS X installers are now drag and drop. It's best to un-install
16631 Tor/Vidalia and then install this new bundle, rather than upgrade. If
16632 you want to upgrade, you'll need to update the paths for Tor and Polipo
16633 in the Vidalia Settings window.
16636 - Send circuit or stream sendme cells when our window has decreased
16637 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
16638 by Karsten when testing the "reduce circuit window" performance
16639 patch. Bugfix on the 54th commit on Tor -- from July 2002,
16640 before the release of Tor 0.0.0. This is the new winner of the
16642 - Fix a remotely triggerable memory leak when a consensus document
16643 contains more than one signature from the same voter. Bugfix on
16645 - Avoid segfault in rare cases when finishing an introduction circuit
16646 as a client and finding out that we don't have an introduction key
16647 for it. Fixes bug 1073. Reported by Aaron Swartz.
16650 - Tor now reads the "circwindow" parameter out of the consensus,
16651 and uses that value for its circuit package window rather than the
16652 default of 1000 cells. Begins the implementation of proposal 168.
16654 o New directory authorities:
16655 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
16657 - Move moria1 and tonga to alternate IP addresses.
16660 - Fix a signed/unsigned compile warning in 0.2.1.19.
16661 - Fix possible segmentation fault on directory authorities. Bugfix on
16663 - Fix an extremely rare infinite recursion bug that could occur if
16664 we tried to log a message after shutting down the log subsystem.
16665 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
16666 - Fix an obscure bug where hidden services on 64-bit big-endian
16667 systems might mis-read the timestamp in v3 introduce cells, and
16668 refuse to connect back to the client. Discovered by "rotor".
16669 Bugfix on 0.2.1.6-alpha.
16670 - We were triggering a CLOCK_SKEW controller status event whenever
16671 we connect via the v2 connection protocol to any relay that has
16672 a wrong clock. Instead, we should only inform the controller when
16673 it's a trusted authority that claims our clock is wrong. Bugfix
16674 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
16675 - We were telling the controller about CHECKING_REACHABILITY and
16676 REACHABILITY_FAILED status events whenever we launch a testing
16677 circuit or notice that one has failed. Instead, only tell the
16678 controller when we want to inform the user of overall success or
16679 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
16681 - Don't warn when we're using a circuit that ends with a node
16682 excluded in ExcludeExitNodes, but the circuit is not used to access
16683 the outside world. This should help fix bug 1090. Bugfix on
16685 - Work around a small memory leak in some versions of OpenSSL that
16686 stopped the memory used by the hostname TLS extension from being
16690 - Add a "getinfo status/accepted-server-descriptor" controller
16691 command, which is the recommended way for controllers to learn
16692 whether our server descriptor has been successfully received by at
16693 least on directory authority. Un-recommend good-server-descriptor
16694 getinfo and status events until we have a better design for them.
16697 Changes in version 0.2.2.5-alpha - 2009-10-11
16698 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
16701 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
16703 o Directory authorities:
16704 - Temporarily (just for this release) move dizum to an alternate
16708 Changes in version 0.2.2.4-alpha - 2009-10-10
16709 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
16710 introduces a new unit test framework, shifts directry authority
16711 addresses around to reduce the impact from recent blocking events,
16712 and fixes a few smaller bugs.
16715 - Fix several more asserts in the circuit_build_times code, for
16716 example one that causes Tor to fail to start once we have
16717 accumulated 5000 build times in the state file. Bugfixes on
16718 0.2.2.2-alpha; fixes bug 1108.
16720 o New directory authorities:
16721 - Move moria1 and Tonga to alternate IP addresses.
16724 - Log SSL state transitions at debug level during handshake, and
16725 include SSL states in error messages. This may help debug future
16726 SSL handshake issues.
16727 - Add a new "Handshake" log domain for activities that happen
16728 during the TLS handshake.
16729 - Revert to the "June 3 2009" ip-to-country file. The September one
16730 seems to have removed most US IP addresses.
16731 - Directory authorities now reject Tor relays with versions less than
16732 0.1.2.14. This step cuts out four relays from the current network,
16733 none of which are very big.
16736 - Fix a couple of smaller issues with gathering statistics. Bugfixes
16738 - Fix two memory leaks in the error case of
16739 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
16740 - Don't count one-hop circuits when we're estimating how long it
16741 takes circuits to build on average. Otherwise we'll set our circuit
16742 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
16743 - Directory authorities no longer change their opinion of, or vote on,
16744 whether a router is Running, unless they have themselves been
16745 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
16748 o Code simplifications and refactoring:
16749 - Revise our unit tests to use the "tinytest" framework, so we
16750 can run tests in their own processes, have smarter setup/teardown
16751 code, and so on. The unit test code has moved to its own
16752 subdirectory, and has been split into multiple modules.
16755 Changes in version 0.2.2.3-alpha - 2009-09-23
16756 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
16759 - Fix an overzealous assert in our new circuit build timeout code.
16760 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
16763 - If the networkstatus consensus tells us that we should use a
16764 negative circuit package window, ignore it. Otherwise we'll
16765 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
16768 Changes in version 0.2.2.2-alpha - 2009-09-21
16769 Tor 0.2.2.2-alpha introduces our latest performance improvement for
16770 clients: Tor tracks the average time it takes to build a circuit, and
16771 avoids using circuits that take too long to build. For fast connections,
16772 this feature can cut your expected latency in half. For slow or flaky
16773 connections, it could ruin your Tor experience. Let us know if it does!
16776 - Tor now tracks how long it takes to build client-side circuits
16777 over time, and adapts its timeout to local network performance.
16778 Since a circuit that takes a long time to build will also provide
16779 bad performance, we get significant latency improvements by
16780 discarding the slowest 20% of circuits. Specifically, Tor creates
16781 circuits more aggressively than usual until it has enough data
16782 points for a good timeout estimate. Implements proposal 151.
16783 We are especially looking for reports (good and bad) from users with
16784 both EDGE and broadband connections that can move from broadband
16785 to EDGE and find out if the build-time data in the .tor/state gets
16786 reset without loss of Tor usability. You should also see a notice
16787 log message telling you that Tor has reset its timeout.
16788 - Directory authorities can now vote on arbitary integer values as
16789 part of the consensus process. This is designed to help set
16790 network-wide parameters. Implements proposal 167.
16791 - Tor now reads the "circwindow" parameter out of the consensus,
16792 and uses that value for its circuit package window rather than the
16793 default of 1000 cells. Begins the implementation of proposal 168.
16796 - Fix a remotely triggerable memory leak when a consensus document
16797 contains more than one signature from the same voter. Bugfix on
16801 - Fix an extremely rare infinite recursion bug that could occur if
16802 we tried to log a message after shutting down the log subsystem.
16803 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
16804 - Fix parsing for memory or time units given without a space between
16805 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
16806 - A networkstatus vote must contain exactly one signature. Spec
16807 conformance issue. Bugfix on 0.2.0.3-alpha.
16808 - Fix an obscure bug where hidden services on 64-bit big-endian
16809 systems might mis-read the timestamp in v3 introduce cells, and
16810 refuse to connect back to the client. Discovered by "rotor".
16811 Bugfix on 0.2.1.6-alpha.
16812 - We were triggering a CLOCK_SKEW controller status event whenever
16813 we connect via the v2 connection protocol to any relay that has
16814 a wrong clock. Instead, we should only inform the controller when
16815 it's a trusted authority that claims our clock is wrong. Bugfix
16816 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
16817 - We were telling the controller about CHECKING_REACHABILITY and
16818 REACHABILITY_FAILED status events whenever we launch a testing
16819 circuit or notice that one has failed. Instead, only tell the
16820 controller when we want to inform the user of overall success or
16821 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
16823 - Don't warn when we're using a circuit that ends with a node
16824 excluded in ExcludeExitNodes, but the circuit is not used to access
16825 the outside world. This should help fix bug 1090, but more problems
16826 remain. Bugfix on 0.2.1.6-alpha.
16827 - Work around a small memory leak in some versions of OpenSSL that
16828 stopped the memory used by the hostname TLS extension from being
16830 - Make our 'torify' script more portable; if we have only one of
16831 'torsocks' or 'tsocks' installed, don't complain to the user;
16832 and explain our warning about tsocks better.
16835 - Add a "getinfo status/accepted-server-descriptor" controller
16836 command, which is the recommended way for controllers to learn
16837 whether our server descriptor has been successfully received by at
16838 least on directory authority. Un-recommend good-server-descriptor
16839 getinfo and status events until we have a better design for them.
16840 - Update to the "September 4 2009" ip-to-country file.
16843 Changes in version 0.2.2.1-alpha - 2009-08-26
16844 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
16845 Tor clients to bootstrap on networks where only port 80 is reachable,
16846 makes it more straightforward to support hardware crypto accelerators,
16847 and starts the groundwork for gathering stats safely at relays.
16850 - Start the process of disabling ".exit" address notation, since it
16851 can be used for a variety of esoteric application-level attacks
16852 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
16855 o New directory authorities:
16856 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
16860 - New AccelName and AccelDir options add support for dynamic OpenSSL
16861 hardware crypto acceleration engines.
16862 - Tor now supports tunneling all of its outgoing connections over
16863 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
16864 configuration options. Code by Christopher Davis.
16867 - Send circuit or stream sendme cells when our window has decreased
16868 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
16869 by Karsten when testing the "reduce circuit window" performance
16870 patch. Bugfix on the 54th commit on Tor -- from July 2002,
16871 before the release of Tor 0.0.0. This is the new winner of the
16874 o New options for gathering stats safely:
16875 - Directory mirrors that set "DirReqStatistics 1" write statistics
16876 about directory requests to disk every 24 hours. As compared to the
16877 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
16878 1) stats are written to disk exactly every 24 hours; 2) estimated
16879 shares of v2 and v3 requests are determined as mean values, not at
16880 the end of a measurement period; 3) unresolved requests are listed
16881 with country code '??'; 4) directories also measure download times.
16882 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
16883 number of exit streams and transferred bytes per port to disk every
16885 - Relays that set "CellStatistics 1" write statistics on how long
16886 cells spend in their circuit queues to disk every 24 hours.
16887 - Entry nodes that set "EntryStatistics 1" write statistics on the
16888 rough number and origins of connecting clients to disk every 24
16890 - Relays that write any of the above statistics to disk and set
16891 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
16892 their extra-info documents.
16895 - New --digests command-line switch to output the digests of the
16896 source files Tor was built with.
16897 - The "torify" script now uses torsocks where available.
16898 - The memarea code now uses a sentinel value at the end of each area
16899 to make sure nothing writes beyond the end of an area. This might
16900 help debug some conceivable causes of bug 930.
16901 - Time and memory units in the configuration file can now be set to
16902 fractional units. For example, "2.5 GB" is now a valid value for
16904 - Certain Tor clients (such as those behind check.torproject.org) may
16905 want to fetch the consensus in an extra early manner. To enable this
16906 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
16907 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
16908 as only certain clients who must have this information sooner should
16910 - Instead of adding the svn revision to the Tor version string, report
16911 the git commit (when we're building from a git checkout).
16914 - If any of the v3 certs we download are unparseable, we should
16915 actually notice the failure so we don't retry indefinitely. Bugfix
16916 on 0.2.0.x; reported by "rotator".
16917 - If the cached cert file is unparseable, warn but don't exit.
16918 - Fix possible segmentation fault on directory authorities. Bugfix on
16920 - When Tor fails to parse a descriptor of any kind, dump it to disk.
16921 Might help diagnosing bug 1051.
16923 o Deprecated and removed features:
16924 - The controller no longer accepts the old obsolete "addr-mappings/"
16925 or "unregistered-servers-" GETINFO values.
16926 - Hidden services no longer publish version 0 descriptors, and clients
16927 do not request or use version 0 descriptors. However, the old hidden
16928 service authorities still accept and serve version 0 descriptors
16929 when contacted by older hidden services/clients.
16930 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
16931 always on; using them is necessary for correct forward-compatible
16933 - Remove support for .noconnect style addresses. Nobody was using
16934 them, and they provided another avenue for detecting Tor users
16935 via application-level web tricks.
16937 o Packaging changes:
16938 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
16939 installer bundles. See
16940 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
16941 for details of what's new in Vidalia 0.2.3.
16942 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
16943 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
16944 configuration file, rather than the old Privoxy.
16945 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
16946 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
16947 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
16948 better compatibility with OS X 10.6, aka Snow Leopard.
16949 - OS X Vidalia Bundle: The multi-package installer is now replaced
16950 by a simple drag and drop to the /Applications folder. This change
16951 occurred with the upgrade to Vidalia 0.2.3.
16954 Changes in version 0.2.1.19 - 2009-07-28
16955 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
16956 services on Tor 0.2.1.3-alpha through 0.2.1.18.
16959 - Make accessing hidden services on 0.2.1.x work right again.
16960 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
16961 part of patch provided by "optimist".
16964 - When a relay/bridge is writing out its identity key fingerprint to
16965 the "fingerprint" file and to its logs, write it without spaces. Now
16966 it will look like the fingerprints in our bridges documentation,
16967 and confuse fewer users.
16970 - Relays no longer publish a new server descriptor if they change
16971 their MaxAdvertisedBandwidth config option but it doesn't end up
16972 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
16973 fixes bug 1026. Patch from Sebastian.
16974 - Avoid leaking memory every time we get a create cell but we have
16975 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
16976 fixes bug 1034. Reported by BarkerJr.
16979 Changes in version 0.2.1.18 - 2009-07-24
16980 Tor 0.2.1.18 lays the foundations for performance improvements,
16981 adds status events to help users diagnose bootstrap problems, adds
16982 optional authentication/authorization for hidden services, fixes a
16983 variety of potential anonymity problems, and includes a huge pile of
16984 other features and bug fixes.
16987 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
16990 Changes in version 0.2.1.17-rc - 2009-07-07
16991 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
16992 candidate for the 0.2.1.x series. It lays the groundwork for further
16993 client performance improvements, and also fixes a big bug with directory
16994 authorities that were causing them to assign Guard and Stable flags
16997 The Windows bundles also finally include the geoip database that we
16998 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
16999 should actually install Torbutton rather than giving you a cryptic
17000 failure message (oops).
17003 - Clients now use the bandwidth values in the consensus, rather than
17004 the bandwidth values in each relay descriptor. This approach opens
17005 the door to more accurate bandwidth estimates once the directory
17006 authorities start doing active measurements. Implements more of
17010 - When Tor clients restart after 1-5 days, they discard all their
17011 cached descriptors as too old, but they still use the cached
17012 consensus document. This approach is good for robustness, but
17013 bad for performance: since they don't know any bandwidths, they
17014 end up choosing at random rather than weighting their choice by
17015 speed. Fixed by the above feature of putting bandwidths in the
17016 consensus. Bugfix on 0.2.0.x.
17017 - Directory authorities were neglecting to mark relays down in their
17018 internal histories if the relays fall off the routerlist without
17019 ever being found unreachable. So there were relays in the histories
17020 that haven't been seen for eight months, and are listed as being
17021 up for eight months. This wreaked havoc on the "median wfu"
17022 and "median mtbf" calculations, in turn making Guard and Stable
17023 flags very wrong, hurting network performance. Fixes bugs 696 and
17024 969. Bugfix on 0.2.0.6-alpha.
17027 - Serve the DirPortFrontPage page even when we have been approaching
17028 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
17029 - The control port would close the connection before flushing long
17030 replies, such as the network consensus, if a QUIT command was issued
17031 before the reply had completed. Now, the control port flushes all
17032 pending replies before closing the connection. Also fixed a spurious
17033 warning when a QUIT command is issued after a malformed or rejected
17034 AUTHENTICATE command, but before the connection was closed. Patch
17035 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
17036 - When we can't find an intro key for a v2 hidden service descriptor,
17037 fall back to the v0 hidden service descriptor and log a bug message.
17038 Workaround for bug 1024.
17039 - Fix a log message that did not respect the SafeLogging option.
17043 - If we're a relay and we change our IP address, be more verbose
17044 about the reason that made us change. Should help track down
17045 further bugs for relays on dynamic IP addresses.
17048 Changes in version 0.2.0.35 - 2009-06-24
17050 - Avoid crashing in the presence of certain malformed descriptors.
17051 Found by lark, and by automated fuzzing.
17052 - Fix an edge case where a malicious exit relay could convince a
17053 controller that the client's DNS question resolves to an internal IP
17054 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
17057 - Finally fix the bug where dynamic-IP relays disappear when their
17058 IP address changes: directory mirrors were mistakenly telling
17059 them their old address if they asked via begin_dir, so they
17060 never got an accurate answer about their new address, so they
17061 just vanished after a day. For belt-and-suspenders, relays that
17062 don't set Address in their config now avoid using begin_dir for
17063 all direct connections. Should fix bugs 827, 883, and 900.
17064 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
17065 that would occur on some exit nodes when DNS failures and timeouts
17066 occurred in certain patterns. Fix for bug 957.
17069 - When starting with a cache over a few days old, do not leak
17070 memory for the obsolete router descriptors in it. Bugfix on
17071 0.2.0.33; fixes bug 672.
17072 - Hidden service clients didn't use a cached service descriptor that
17073 was older than 15 minutes, but wouldn't fetch a new one either,
17074 because there was already one in the cache. Now, fetch a v2
17075 descriptor unless the same descriptor was added to the cache within
17076 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
17079 Changes in version 0.2.1.16-rc - 2009-06-20
17080 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
17081 a bunch of minor bugs.
17084 - Fix an edge case where a malicious exit relay could convince a
17085 controller that the client's DNS question resolves to an internal IP
17086 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
17088 o Major performance improvements (on 0.2.0.x):
17089 - Disable and refactor some debugging checks that forced a linear scan
17090 over the whole server-side DNS cache. These accounted for over 50%
17091 of CPU time on a relatively busy exit node's gprof profile. Found
17093 - Disable some debugging checks that appeared in exit node profile
17097 - Update to the "June 3 2009" ip-to-country file.
17098 - Do not have tor-resolve automatically refuse all .onion addresses;
17099 if AutomapHostsOnResolve is set in your torrc, this will work fine.
17101 o Minor bugfixes (on 0.2.0.x):
17102 - Log correct error messages for DNS-related network errors on
17104 - Fix a race condition that could cause crashes or memory corruption
17105 when running as a server with a controller listening for log
17107 - Avoid crashing when we have a policy specified in a DirPolicy or
17108 SocksPolicy or ReachableAddresses option with ports set on it,
17109 and we re-load the policy. May fix bug 996.
17110 - Hidden service clients didn't use a cached service descriptor that
17111 was older than 15 minutes, but wouldn't fetch a new one either,
17112 because there was already one in the cache. Now, fetch a v2
17113 descriptor unless the same descriptor was added to the cache within
17114 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
17116 o Minor bugfixes (on 0.2.1.x):
17117 - Don't warn users about low port and hibernation mix when they
17118 provide a *ListenAddress directive to fix that. Bugfix on
17120 - When switching back and forth between bridge mode, do not start
17121 gathering GeoIP data until two hours have passed.
17122 - Do not complain that the user has requested an excluded node as
17123 an exit when the node is not really an exit. This could happen
17124 because the circuit was for testing, or an introduction point.
17128 Changes in version 0.2.1.15-rc - 2009-05-25
17129 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
17130 series. It fixes a major bug on fast exit relays, as well as a variety
17131 of more minor bugs.
17133 o Major bugfixes (on 0.2.0.x):
17134 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
17135 that would occur on some exit nodes when DNS failures and timeouts
17136 occurred in certain patterns. Fix for bug 957.
17138 o Minor bugfixes (on 0.2.0.x):
17139 - Actually return -1 in the error case for read_bandwidth_usage().
17140 Harmless bug, since we currently don't care about the return value
17141 anywhere. Bugfix on 0.2.0.9-alpha.
17142 - Provide a more useful log message if bug 977 (related to buffer
17143 freelists) ever reappears, and do not crash right away.
17144 - Fix an assertion failure on 64-bit platforms when we allocated
17145 memory right up to the end of a memarea, then realigned the memory
17146 one step beyond the end. Fixes a possible cause of bug 930.
17147 - Protect the count of open sockets with a mutex, so we can't
17148 corrupt it when two threads are closing or opening sockets at once.
17149 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
17150 - Don't allow a bridge to publish its router descriptor to a
17151 non-bridge directory authority. Fixes part of bug 932.
17152 - When we change to or from being a bridge, reset our counts of
17153 client usage by country. Fixes bug 932.
17154 - Fix a bug that made stream bandwidth get misreported to the
17156 - Stop using malloc_usable_size() to use more area than we had
17157 actually allocated: it was safe, but made valgrind really unhappy.
17158 - Fix a memory leak when v3 directory authorities load their keys
17159 and cert from disk. Bugfix on 0.2.0.1-alpha.
17161 o Minor bugfixes (on 0.2.1.x):
17162 - Fix use of freed memory when deciding to mark a non-addable
17163 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
17166 Changes in version 0.2.1.14-rc - 2009-04-12
17167 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
17168 series. It begins fixing some major performance problems, and also
17169 finally addresses the bug that was causing relays on dynamic IP
17170 addresses to fall out of the directory.
17173 - Clients replace entry guards that were chosen more than a few months
17174 ago. This change should significantly improve client performance,
17175 especially once more people upgrade, since relays that have been
17176 a guard for a long time are currently overloaded.
17178 o Major bugfixes (on 0.2.0):
17179 - Finally fix the bug where dynamic-IP relays disappear when their
17180 IP address changes: directory mirrors were mistakenly telling
17181 them their old address if they asked via begin_dir, so they
17182 never got an accurate answer about their new address, so they
17183 just vanished after a day. For belt-and-suspenders, relays that
17184 don't set Address in their config now avoid using begin_dir for
17185 all direct connections. Should fix bugs 827, 883, and 900.
17186 - Relays were falling out of the networkstatus consensus for
17187 part of a day if they changed their local config but the
17188 authorities discarded their new descriptor as "not sufficiently
17189 different". Now directory authorities accept a descriptor as changed
17190 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
17191 patch by Sebastian.
17192 - Avoid crashing in the presence of certain malformed descriptors.
17193 Found by lark, and by automated fuzzing.
17196 - When generating circuit events with verbose nicknames for
17197 controllers, try harder to look up nicknames for routers on a
17198 circuit. (Previously, we would look in the router descriptors we had
17199 for nicknames, but not in the consensus.) Partial fix for bug 941.
17200 - If the bridge config line doesn't specify a port, assume 443.
17201 This makes bridge lines a bit smaller and easier for users to
17203 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
17204 bytes (aka 20KB/s), to match our documentation. Also update
17205 directory authorities so they always assign the Fast flag to relays
17206 with 20KB/s of capacity. Now people running relays won't suddenly
17207 find themselves not seeing any use, if the network gets faster
17209 - Update to the "April 3 2009" ip-to-country file.
17212 - Avoid trying to print raw memory to the logs when we decide to
17213 give up on downloading a given relay descriptor. Bugfix on
17215 - In tor-resolve, when the Tor client to use is specified by
17216 <hostname>:<port>, actually use the specified port rather than
17217 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
17218 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
17219 - When starting with a cache over a few days old, do not leak
17220 memory for the obsolete router descriptors in it. Bugfix on
17222 - Avoid double-free on list of successfully uploaded hidden
17223 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
17224 - Change memarea_strndup() implementation to work even when
17225 duplicating a string at the end of a page. This bug was
17226 harmless for now, but could have meant crashes later. Fix by
17227 lark. Bugfix on 0.2.1.1-alpha.
17228 - Limit uploaded directory documents to be 16M rather than 500K.
17229 The directory authorities were refusing v3 consensus votes from
17230 other authorities, since the votes are now 504K. Fixes bug 959;
17231 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
17232 - Directory authorities should never send a 503 "busy" response to
17233 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
17237 Changes in version 0.2.1.13-alpha - 2009-03-09
17238 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
17239 cleanups. We're finally getting close to a release candidate.
17242 - Correctly update the list of which countries we exclude as
17243 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
17244 lark. Bugfix on 0.2.1.6-alpha.
17246 o Minor bugfixes (on 0.2.0.x and earlier):
17247 - Automatically detect MacOSX versions earlier than 10.4.0, and
17248 disable kqueue from inside Tor when running with these versions.
17249 We previously did this from the startup script, but that was no
17250 help to people who didn't use the startup script. Resolves bug 863.
17251 - When we had picked an exit node for a connection, but marked it as
17252 "optional", and it turned out we had no onion key for the exit,
17253 stop wanting that exit and try again. This situation may not
17254 be possible now, but will probably become feasible with proposal
17255 158. Spotted by rovv. Fixes another case of bug 752.
17256 - Clients no longer cache certificates for authorities they do not
17257 recognize. Bugfix on 0.2.0.9-alpha.
17258 - When we can't transmit a DNS request due to a network error, retry
17259 it after a while, and eventually transmit a failing response to
17260 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
17261 - If the controller claimed responsibility for a stream, but that
17262 stream never finished making its connection, it would live
17263 forever in circuit_wait state. Now we close it after SocksTimeout
17264 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
17265 - Drop begin cells to a hidden service if they come from the middle
17266 of a circuit. Patch from lark.
17267 - When we erroneously receive two EXTEND cells for the same circuit
17268 ID on the same connection, drop the second. Patch from lark.
17269 - Fix a crash that occurs on exit nodes when a nameserver request
17270 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
17271 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
17273 - Do not assume that a stack-allocated character array will be
17274 64-bit aligned on platforms that demand that uint64_t access is
17275 aligned. Possible fix for bug 604.
17276 - Parse dates and IPv4 addresses in a locale- and libc-independent
17277 manner, to avoid platform-dependent behavior on malformed input.
17278 - Build correctly when configured to build outside the main source
17279 path. Patch from Michael Gold.
17280 - We were already rejecting relay begin cells with destination port
17281 of 0. Now also reject extend cells with destination port or address
17282 of 0. Suggested by lark.
17284 o Minor bugfixes (on 0.2.1.x):
17285 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
17286 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
17287 - If we're an exit node, scrub the IP address to which we are exiting
17288 in the logs. Bugfix on 0.2.1.8-alpha.
17291 - On Linux, use the prctl call to re-enable core dumps when the user
17293 - New controller event NEWCONSENSUS that lists the networkstatus
17294 lines for every recommended relay. Now controllers like Torflow
17295 can keep up-to-date on which relays they should be using.
17296 - Update to the "February 26 2009" ip-to-country file.
17299 Changes in version 0.2.0.34 - 2009-02-08
17300 Tor 0.2.0.34 features several more security-related fixes. You should
17301 upgrade, especially if you run an exit relay (remote crash) or a
17302 directory authority (remote infinite loop), or you're on an older
17303 (pre-XP) or not-recently-patched Windows (remote exploit).
17305 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
17306 have many known flaws, and nobody should be using them. You should
17307 upgrade. If you're using a Linux or BSD and its packages are obsolete,
17308 stop using those packages and upgrade anyway.
17311 - Fix an infinite-loop bug on handling corrupt votes under certain
17312 circumstances. Bugfix on 0.2.0.8-alpha.
17313 - Fix a temporary DoS vulnerability that could be performed by
17314 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
17315 - Avoid a potential crash on exit nodes when processing malformed
17316 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
17317 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
17318 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
17321 - Fix compilation on systems where time_t is a 64-bit integer.
17322 Patch from Matthias Drochner.
17323 - Don't consider expiring already-closed client connections. Fixes
17324 bug 893. Bugfix on 0.0.2pre20.
17327 Changes in version 0.2.1.12-alpha - 2009-02-08
17328 Tor 0.2.1.12-alpha features several more security-related fixes. You
17329 should upgrade, especially if you run an exit relay (remote crash) or
17330 a directory authority (remote infinite loop), or you're on an older
17331 (pre-XP) or not-recently-patched Windows (remote exploit). It also
17332 includes a big pile of minor bugfixes and cleanups.
17335 - Fix an infinite-loop bug on handling corrupt votes under certain
17336 circumstances. Bugfix on 0.2.0.8-alpha.
17337 - Fix a temporary DoS vulnerability that could be performed by
17338 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
17339 - Avoid a potential crash on exit nodes when processing malformed
17340 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
17343 - Let controllers actually ask for the "clients_seen" event for
17344 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
17345 reported by Matt Edman.
17346 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
17348 - Fix a bug in address parsing that was preventing bridges or hidden
17349 service targets from being at IPv6 addresses.
17350 - Solve a bug that kept hardware crypto acceleration from getting
17351 enabled when accounting was turned on. Fixes bug 907. Bugfix on
17353 - Remove a bash-ism from configure.in to build properly on non-Linux
17354 platforms. Bugfix on 0.2.1.1-alpha.
17355 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
17356 headers. Bugfix on 0.2.0.10-alpha.
17357 - Don't consider expiring already-closed client connections. Fixes
17358 bug 893. Bugfix on 0.0.2pre20.
17359 - Fix another interesting corner-case of bug 891 spotted by rovv:
17360 Previously, if two hosts had different amounts of clock drift, and
17361 one of them created a new connection with just the wrong timing,
17362 the other might decide to deprecate the new connection erroneously.
17363 Bugfix on 0.1.1.13-alpha.
17364 - Resolve a very rare crash bug that could occur when the user forced
17365 a nameserver reconfiguration during the middle of a nameserver
17366 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
17367 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
17368 Bugfix on 0.2.1.7-alpha.
17369 - If we're using bridges and our network goes away, be more willing
17370 to forgive our bridges and try again when we get an application
17371 request. Bugfix on 0.2.0.x.
17374 - Support platforms where time_t is 64 bits long. (Congratulations,
17375 NetBSD!) Patch from Matthias Drochner.
17376 - Add a 'getinfo status/clients-seen' controller command, in case
17377 controllers want to hear clients_seen events but connect late.
17380 - Disable GCC's strict alias optimization by default, to avoid the
17381 likelihood of its introducing subtle bugs whenever our code violates
17382 the letter of C99's alias rules.
17385 Changes in version 0.2.0.33 - 2009-01-21
17386 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
17387 useful to users. It also finally fixes a bug where a relay or client
17388 that's been off for many days would take a long time to bootstrap.
17390 This update also fixes an important security-related bug reported by
17391 Ilja van Sprundel. You should upgrade. (We'll send out more details
17392 about the bug once people have had some time to upgrade.)
17395 - Fix a heap-corruption bug that may be remotely triggerable on
17396 some platforms. Reported by Ilja van Sprundel.
17399 - When a stream at an exit relay is in state "resolving" or
17400 "connecting" and it receives an "end" relay cell, the exit relay
17401 would silently ignore the end cell and not close the stream. If
17402 the client never closes the circuit, then the exit relay never
17403 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
17404 reported by "wood".
17405 - When sending CREATED cells back for a given circuit, use a 64-bit
17406 connection ID to find the right connection, rather than an addr:port
17407 combination. Now that we can have multiple OR connections between
17408 the same ORs, it is no longer possible to use addr:port to uniquely
17409 identify a connection.
17410 - Bridge relays that had DirPort set to 0 would stop fetching
17411 descriptors shortly after startup, and then briefly resume
17412 after a new bandwidth test and/or after publishing a new bridge
17413 descriptor. Bridge users that try to bootstrap from them would
17414 get a recent networkstatus but would get descriptors from up to
17415 18 hours earlier, meaning most of the descriptors were obsolete
17416 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
17417 - Prevent bridge relays from serving their 'extrainfo' document
17418 to anybody who asks, now that extrainfo docs include potentially
17419 sensitive aggregated client geoip summaries. Bugfix on
17421 - If the cached networkstatus consensus is more than five days old,
17422 discard it rather than trying to use it. In theory it could be
17423 useful because it lists alternate directory mirrors, but in practice
17424 it just means we spend many minutes trying directory mirrors that
17425 are long gone from the network. Also discard router descriptors as
17426 we load them if they are more than five days old, since the onion
17427 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
17430 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
17431 could make gcc generate non-functional binary search code. Bugfix
17433 - Build correctly on platforms without socklen_t.
17434 - Compile without warnings on solaris.
17435 - Avoid potential crash on internal error during signature collection.
17436 Fixes bug 864. Patch from rovv.
17437 - Correct handling of possible malformed authority signing key
17438 certificates with internal signature types. Fixes bug 880.
17439 Bugfix on 0.2.0.3-alpha.
17440 - Fix a hard-to-trigger resource leak when logging credential status.
17442 - When we can't initialize DNS because the network is down, do not
17443 automatically stop Tor from starting. Instead, we retry failed
17444 dns_init() every 10 minutes, and change the exit policy to reject
17445 *:* until one succeeds. Fixes bug 691.
17446 - Use 64 bits instead of 32 bits for connection identifiers used with
17447 the controller protocol, to greatly reduce risk of identifier reuse.
17448 - When we're choosing an exit node for a circuit, and we have
17449 no pending streams, choose a good general exit rather than one that
17450 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
17451 - Fix another case of assuming, when a specific exit is requested,
17452 that we know more than the user about what hosts it allows.
17453 Fixes one case of bug 752. Patch from rovv.
17454 - Clip the MaxCircuitDirtiness config option to a minimum of 10
17455 seconds. Warn the user if lower values are given in the
17456 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
17457 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
17458 user if lower values are given in the configuration. Bugfix on
17459 0.1.1.17-rc. Patch by Sebastian.
17460 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
17461 the cache because we already had a v0 descriptor with the same ID.
17462 Bugfix on 0.2.0.18-alpha.
17463 - Fix a race condition when freeing keys shared between main thread
17464 and CPU workers that could result in a memory leak. Bugfix on
17465 0.1.0.1-rc. Fixes bug 889.
17466 - Send a valid END cell back when a client tries to connect to a
17467 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
17468 840. Patch from rovv.
17469 - Check which hops rendezvous stream cells are associated with to
17470 prevent possible guess-the-streamid injection attacks from
17471 intermediate hops. Fixes another case of bug 446. Based on patch
17473 - If a broken client asks a non-exit router to connect somewhere,
17474 do not even do the DNS lookup before rejecting the connection.
17475 Fixes another case of bug 619. Patch from rovv.
17476 - When a relay gets a create cell it can't decrypt (e.g. because it's
17477 using the wrong onion key), we were dropping it and letting the
17478 client time out. Now actually answer with a destroy cell. Fixes
17479 bug 904. Bugfix on 0.0.2pre8.
17481 o Minor bugfixes (hidden services):
17482 - Do not throw away existing introduction points on SIGHUP. Bugfix on
17483 0.0.6pre1. Patch by Karsten. Fixes bug 874.
17486 - Report the case where all signatures in a detached set are rejected
17487 differently than the case where there is an error handling the
17489 - When we realize that another process has modified our cached
17490 descriptors, print out a more useful error message rather than
17491 triggering an assertion. Fixes bug 885. Patch from Karsten.
17492 - Implement the 0x20 hack to better resist DNS poisoning: set the
17493 case on outgoing DNS requests randomly, and reject responses that do
17494 not match the case correctly. This logic can be disabled with the
17495 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
17496 of servers that do not reliably preserve case in replies. See
17497 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
17499 - Check DNS replies for more matching fields to better resist DNS
17501 - Never use OpenSSL compression: it wastes RAM and CPU trying to
17502 compress cells, which are basically all encrypted, compressed, or
17506 Changes in version 0.2.1.11-alpha - 2009-01-20
17507 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
17508 week it will take a long time to bootstrap again" bug. It also fixes
17509 an important security-related bug reported by Ilja van Sprundel. You
17510 should upgrade. (We'll send out more details about the bug once people
17511 have had some time to upgrade.)
17514 - Fix a heap-corruption bug that may be remotely triggerable on
17515 some platforms. Reported by Ilja van Sprundel.
17518 - Discard router descriptors as we load them if they are more than
17519 five days old. Otherwise if Tor is off for a long time and then
17520 starts with cached descriptors, it will try to use the onion
17521 keys in those obsolete descriptors when building circuits. Bugfix
17522 on 0.2.0.x. Fixes bug 887.
17525 - Try to make sure that the version of Libevent we're running with
17526 is binary-compatible with the one we built with. May address bug
17528 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
17529 for bug 905. Bugfix on 0.2.1.7-alpha.
17530 - Add a new --enable-local-appdata configuration switch to change
17531 the default location of the datadir on win32 from APPDATA to
17532 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
17533 entirely. Patch from coderman.
17536 - Make outbound DNS packets respect the OutboundBindAddress setting.
17537 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
17538 - When our circuit fails at the first hop (e.g. we get a destroy
17539 cell back), avoid using that OR connection anymore, and also
17540 tell all the one-hop directory requests waiting for it that they
17541 should fail. Bugfix on 0.2.1.3-alpha.
17542 - In the torify(1) manpage, mention that tsocks will leak your
17546 Changes in version 0.2.1.10-alpha - 2009-01-06
17547 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
17548 would make the bridge relay not so useful if it had DirPort set to 0,
17549 and one that could let an attacker learn a little bit of information
17550 about the bridge's users), and a bug that would cause your Tor relay
17551 to ignore a circuit create request it can't decrypt (rather than reply
17552 with an error). It also fixes a wide variety of other bugs.
17555 - If the cached networkstatus consensus is more than five days old,
17556 discard it rather than trying to use it. In theory it could
17557 be useful because it lists alternate directory mirrors, but in
17558 practice it just means we spend many minutes trying directory
17559 mirrors that are long gone from the network. Helps bug 887 a bit;
17561 - Bridge relays that had DirPort set to 0 would stop fetching
17562 descriptors shortly after startup, and then briefly resume
17563 after a new bandwidth test and/or after publishing a new bridge
17564 descriptor. Bridge users that try to bootstrap from them would
17565 get a recent networkstatus but would get descriptors from up to
17566 18 hours earlier, meaning most of the descriptors were obsolete
17567 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
17568 - Prevent bridge relays from serving their 'extrainfo' document
17569 to anybody who asks, now that extrainfo docs include potentially
17570 sensitive aggregated client geoip summaries. Bugfix on
17574 - New controller event "clients_seen" to report a geoip-based summary
17575 of which countries we've seen clients from recently. Now controllers
17576 like Vidalia can show bridge operators that they're actually making
17578 - Build correctly against versions of OpenSSL 0.9.8 or later built
17579 without support for deprecated functions.
17580 - Update to the "December 19 2008" ip-to-country file.
17582 o Minor bugfixes (on 0.2.0.x):
17583 - Authorities now vote for the Stable flag for any router whose
17584 weighted MTBF is at least 5 days, regardless of the mean MTBF.
17585 - Do not remove routers as too old if we do not have any consensus
17586 document. Bugfix on 0.2.0.7-alpha.
17587 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
17588 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
17589 - When an exit relay resolves a stream address to a local IP address,
17590 do not just keep retrying that same exit relay over and
17591 over. Instead, just close the stream. Addresses bug 872. Bugfix
17592 on 0.2.0.32. Patch from rovv.
17593 - If a hidden service sends us an END cell, do not consider
17594 retrying the connection; just close it. Patch from rovv.
17595 - When we made bridge authorities stop serving bridge descriptors over
17596 unencrypted links, we also broke DirPort reachability testing for
17597 bridges. So bridges with a non-zero DirPort were printing spurious
17598 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
17599 - When a relay gets a create cell it can't decrypt (e.g. because it's
17600 using the wrong onion key), we were dropping it and letting the
17601 client time out. Now actually answer with a destroy cell. Fixes
17602 bug 904. Bugfix on 0.0.2pre8.
17603 - Squeeze 2-5% out of client performance (according to oprofile) by
17604 improving the implementation of some policy-manipulation functions.
17606 o Minor bugfixes (on 0.2.1.x):
17607 - Make get_interface_address() function work properly again; stop
17608 guessing the wrong parts of our address as our address.
17609 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
17610 send on that circuit. Otherwise we might violate the proposal-110
17611 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
17613 - When we're sending non-EXTEND cells to the first hop in a circuit,
17614 for example to use an encrypted directory connection, we don't need
17615 to use RELAY_EARLY cells: the first hop knows what kind of cell
17616 it is, and nobody else can even see the cell type. Conserving
17617 RELAY_EARLY cells makes it easier to cannibalize circuits like
17619 - Stop logging nameserver addresses in reverse order.
17620 - If we are retrying a directory download slowly over and over, do
17621 not automatically give up after the 254th failure. Bugfix on
17623 - Resume reporting accurate "stream end" reasons to the local control
17624 port. They were lost in the changes for Proposal 148. Bugfix on
17627 o Deprecated and removed features:
17628 - The old "tor --version --version" command, which would print out
17629 the subversion "Id" of most of the source files, is now removed. It
17630 turned out to be less useful than we'd expected, and harder to
17633 o Code simplifications and refactoring:
17634 - Change our header file guard macros to be less likely to conflict
17635 with system headers. Adam Langley noticed that we were conflicting
17636 with log.h on Android.
17637 - Tool-assisted documentation cleanup. Nearly every function or
17638 static variable in Tor should have its own documentation now.
17641 Changes in version 0.2.1.9-alpha - 2008-12-25
17642 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
17644 o New directory authorities:
17645 - gabelmoo (the authority run by Karsten Loesing) now has a new
17649 - Never use a connection with a mismatched address to extend a
17650 circuit, unless that connection is canonical. A canonical
17651 connection is one whose address is authenticated by the router's
17652 identity key, either in a NETINFO cell or in a router descriptor.
17653 - Avoid a possible memory corruption bug when receiving hidden service
17654 descriptors. Bugfix on 0.2.1.6-alpha.
17657 - Fix a logic error that would automatically reject all but the first
17658 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
17659 part of bug 813/868. Bug spotted by coderman.
17660 - When a stream at an exit relay is in state "resolving" or
17661 "connecting" and it receives an "end" relay cell, the exit relay
17662 would silently ignore the end cell and not close the stream. If
17663 the client never closes the circuit, then the exit relay never
17664 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
17665 reported by "wood".
17666 - When we can't initialize DNS because the network is down, do not
17667 automatically stop Tor from starting. Instead, retry failed
17668 dns_init() every 10 minutes, and change the exit policy to reject
17669 *:* until one succeeds. Fixes bug 691.
17672 - Give a better error message when an overzealous init script says
17673 "sudo -u username tor --user username". Makes Bug 882 easier for
17675 - When a directory authority gives us a new guess for our IP address,
17676 log which authority we used. Hopefully this will help us debug
17677 the recent complaints about bad IP address guesses.
17678 - Detect svn revision properly when we're using git-svn.
17679 - Try not to open more than one descriptor-downloading connection
17680 to an authority at once. This should reduce load on directory
17681 authorities. Fixes bug 366.
17682 - Add cross-certification to newly generated certificates, so that
17683 a signing key is enough information to look up a certificate.
17684 Partial implementation of proposal 157.
17685 - Start serving certificates by <identity digest, signing key digest>
17686 pairs. Partial implementation of proposal 157.
17687 - Clients now never report any stream end reason except 'MISC'.
17688 Implements proposal 148.
17689 - On platforms with a maximum syslog string length, truncate syslog
17690 messages to that length ourselves, rather than relying on the
17691 system to do it for us.
17692 - Optimize out calls to time(NULL) that occur for every IO operation,
17693 or for every cell. On systems where time() is a slow syscall,
17694 this fix will be slightly helpful.
17695 - Exit servers can now answer resolve requests for ip6.arpa addresses.
17696 - When we download a descriptor that we then immediately (as
17697 a directory authority) reject, do not retry downloading it right
17698 away. Should save some bandwidth on authorities. Fix for bug
17699 888. Patch by Sebastian Hahn.
17700 - When a download gets us zero good descriptors, do not notify
17701 Tor that new directory information has arrived.
17702 - Avoid some nasty corner cases in the logic for marking connections
17703 as too old or obsolete or noncanonical for circuits. Partial
17706 o Minor features (controller):
17707 - New CONSENSUS_ARRIVED event to note when a new consensus has
17708 been fetched and validated.
17709 - When we realize that another process has modified our cached
17710 descriptors file, print out a more useful error message rather
17711 than triggering an assertion. Fixes bug 885. Patch from Karsten.
17712 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
17713 controllers to prevent SIGHUP from reloading the
17714 configuration. Fixes bug 856.
17717 - Resume using the correct "REASON=" stream when telling the
17718 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
17719 - When a canonical connection appears later in our internal list
17720 than a noncanonical one for a given OR ID, always use the
17721 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
17723 - Clip the MaxCircuitDirtiness config option to a minimum of 10
17724 seconds. Warn the user if lower values are given in the
17725 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
17726 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
17727 user if lower values are given in the configuration. Bugfix on
17728 0.1.1.17-rc. Patch by Sebastian.
17729 - Fix a race condition when freeing keys shared between main thread
17730 and CPU workers that could result in a memory leak. Bugfix on
17731 0.1.0.1-rc. Fixes bug 889.
17733 o Minor bugfixes (hidden services):
17734 - Do not throw away existing introduction points on SIGHUP (bugfix on
17735 0.0.6pre1); also, do not stall hidden services because we're
17736 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
17737 by John Brooks. Patch by Karsten. Fixes bug 874.
17738 - Fix a memory leak when we decline to add a v2 rendezvous
17739 descriptor to the cache because we already had a v0 descriptor
17740 with the same ID. Bugfix on 0.2.0.18-alpha.
17742 o Deprecated and removed features:
17743 - RedirectExits has been removed. It was deprecated since
17745 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
17746 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
17747 - Cell pools are now always enabled; --disable-cell-pools is ignored.
17749 o Code simplifications and refactoring:
17750 - Rename the confusing or_is_obsolete field to the more appropriate
17751 is_bad_for_new_circs, and move it to or_connection_t where it
17753 - Move edge-only flags from connection_t to edge_connection_t: not
17754 only is this better coding, but on machines of plausible alignment,
17755 it should save 4-8 bytes per connection_t. "Every little bit helps."
17756 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
17757 for consistency; keep old option working for backward compatibility.
17758 - Simplify the code for finding connections to use for a circuit.
17761 Changes in version 0.2.1.8-alpha - 2008-12-08
17762 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
17763 builds better on unusual platforms like Solaris and old OS X, and
17764 fixes a variety of other issues.
17767 - New DirPortFrontPage option that takes an html file and publishes
17768 it as "/" on the DirPort. Now relay operators can provide a
17769 disclaimer without needing to set up a separate webserver. There's
17770 a sample disclaimer in contrib/tor-exit-notice.html.
17773 - When the client is choosing entry guards, now it selects at most
17774 one guard from a given relay family. Otherwise we could end up with
17775 all of our entry points into the network run by the same operator.
17776 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
17779 - Fix a DOS opportunity during the voting signature collection process
17780 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
17781 - Fix a possible segfault when establishing an exit connection. Bugfix
17785 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
17787 - Made Tor a little less aggressive about deleting expired
17788 certificates. Partial fix for bug 854.
17789 - Stop doing unaligned memory access that generated bus errors on
17790 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
17791 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
17792 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
17793 - Make USR2 log-level switch take effect immediately. Bugfix on
17795 - If one win32 nameserver fails to get added, continue adding the
17796 rest, and don't automatically fail.
17797 - Use fcntl() for locking when flock() is not available. Should fix
17798 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
17799 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
17800 could make gcc generate non-functional binary search code. Bugfix
17802 - Build correctly on platforms without socklen_t.
17803 - Avoid potential crash on internal error during signature collection.
17804 Fixes bug 864. Patch from rovv.
17805 - Do not use C's stdio library for writing to log files. This will
17806 improve logging performance by a minute amount, and will stop
17807 leaking fds when our disk is full. Fixes bug 861.
17808 - Stop erroneous use of O_APPEND in cases where we did not in fact
17809 want to re-seek to the end of a file before every last write().
17810 - Correct handling of possible malformed authority signing key
17811 certificates with internal signature types. Fixes bug 880. Bugfix
17813 - Fix a hard-to-trigger resource leak when logging credential status.
17817 - Directory mirrors no longer fetch the v1 directory or
17818 running-routers files. They are obsolete, and nobody asks for them
17819 anymore. This is the first step to making v1 authorities obsolete.
17821 o Minor features (controller):
17822 - Return circuit purposes in response to GETINFO circuit-status. Fixes
17826 Changes in version 0.2.0.32 - 2008-11-20
17827 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
17828 packages (and maybe other packages) noticed by Theo de Raadt, fixes
17829 a smaller security flaw that might allow an attacker to access local
17830 services, further improves hidden service performance, and fixes a
17831 variety of other issues.
17834 - The "User" and "Group" config options did not clear the
17835 supplementary group entries for the Tor process. The "User" option
17836 is now more robust, and we now set the groups to the specified
17837 user's primary group. The "Group" option is now ignored. For more
17838 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17839 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17840 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
17841 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17842 consistently obeyed: if an exit relay refuses a stream because its
17843 exit policy doesn't allow it, we would remember what IP address
17844 the relay said the destination address resolves to, even if it's
17845 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17848 - Fix a DOS opportunity during the voting signature collection process
17849 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
17851 o Major bugfixes (hidden services):
17852 - When fetching v0 and v2 rendezvous service descriptors in parallel,
17853 we were failing the whole hidden service request when the v0
17854 descriptor fetch fails, even if the v2 fetch is still pending and
17855 might succeed. Similarly, if the last v2 fetch fails, we were
17856 failing the whole hidden service request even if a v0 fetch is
17857 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
17858 - When extending a circuit to a hidden service directory to upload a
17859 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
17860 requests failed, because the router descriptor has not been
17861 downloaded yet. In these cases, do not attempt to upload the
17862 rendezvous descriptor, but wait until the router descriptor is
17863 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
17864 descriptor from a hidden service directory for which the router
17865 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
17869 - Fix several infrequent memory leaks spotted by Coverity.
17870 - When testing for libevent functions, set the LDFLAGS variable
17871 correctly. Found by Riastradh.
17872 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
17873 bootstrapping with tunneled directory connections. Bugfix on
17874 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
17875 - When asked to connect to A.B.exit:80, if we don't know the IP for A
17876 and we know that server B rejects most-but-not all connections to
17877 port 80, we would previously reject the connection. Now, we assume
17878 the user knows what they were asking for. Fixes bug 752. Bugfix
17879 on 0.0.9rc5. Diagnosed by BarkerJr.
17880 - If we overrun our per-second write limits a little, count this as
17881 having used up our write allocation for the second, and choke
17882 outgoing directory writes. Previously, we had only counted this when
17883 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
17884 Bugfix on 0.2.0.x (??).
17885 - Remove the old v2 directory authority 'lefkada' from the default
17886 list. It has been gone for many months.
17887 - Stop doing unaligned memory access that generated bus errors on
17888 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
17889 - Make USR2 log-level switch take effect immediately. Bugfix on
17892 o Minor bugfixes (controller):
17893 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
17894 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
17897 Changes in version 0.2.1.7-alpha - 2008-11-08
17898 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
17899 packages (and maybe other packages) noticed by Theo de Raadt, fixes
17900 a smaller security flaw that might allow an attacker to access local
17901 services, adds better defense against DNS poisoning attacks on exit
17902 relays, further improves hidden service performance, and fixes a
17903 variety of other issues.
17906 - The "ClientDNSRejectInternalAddresses" config option wasn't being
17907 consistently obeyed: if an exit relay refuses a stream because its
17908 exit policy doesn't allow it, we would remember what IP address
17909 the relay said the destination address resolves to, even if it's
17910 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
17911 - The "User" and "Group" config options did not clear the
17912 supplementary group entries for the Tor process. The "User" option
17913 is now more robust, and we now set the groups to the specified
17914 user's primary group. The "Group" option is now ignored. For more
17915 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
17916 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
17917 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
17918 - Do not use or believe expired v3 authority certificates. Patch
17919 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
17922 - Now NodeFamily and MyFamily config options allow spaces in
17923 identity fingerprints, so it's easier to paste them in.
17924 Suggested by Lucky Green.
17925 - Implement the 0x20 hack to better resist DNS poisoning: set the
17926 case on outgoing DNS requests randomly, and reject responses that do
17927 not match the case correctly. This logic can be disabled with the
17928 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
17929 of servers that do not reliably preserve case in replies. See
17930 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
17932 - Preserve case in replies to DNSPort requests in order to support
17933 the 0x20 hack for resisting DNS poisoning attacks.
17935 o Hidden service performance improvements:
17936 - When the client launches an introduction circuit, retry with a
17937 new circuit after 30 seconds rather than 60 seconds.
17938 - Launch a second client-side introduction circuit in parallel
17939 after a delay of 15 seconds (based on work by Christian Wilms).
17940 - Hidden services start out building five intro circuits rather
17941 than three, and when the first three finish they publish a service
17942 descriptor using those. Now we publish our service descriptor much
17943 faster after restart.
17946 - Minor fix in the warning messages when you're having problems
17947 bootstrapping; also, be more forgiving of bootstrap problems when
17948 we're still making incremental progress on a given bootstrap phase.
17949 - When we're choosing an exit node for a circuit, and we have
17950 no pending streams, choose a good general exit rather than one that
17951 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
17952 - Send a valid END cell back when a client tries to connect to a
17953 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
17954 840. Patch from rovv.
17955 - If a broken client asks a non-exit router to connect somewhere,
17956 do not even do the DNS lookup before rejecting the connection.
17957 Fixes another case of bug 619. Patch from rovv.
17958 - Fix another case of assuming, when a specific exit is requested,
17959 that we know more than the user about what hosts it allows.
17960 Fixes another case of bug 752. Patch from rovv.
17961 - Check which hops rendezvous stream cells are associated with to
17962 prevent possible guess-the-streamid injection attacks from
17963 intermediate hops. Fixes another case of bug 446. Based on patch
17965 - Avoid using a negative right-shift when comparing 32-bit
17966 addresses. Possible fix for bug 845 and bug 811.
17967 - Make the assert_circuit_ok() function work correctly on circuits that
17968 have already been marked for close.
17969 - Fix read-off-the-end-of-string error in unit tests when decoding
17970 introduction points.
17971 - Fix uninitialized size field for memory area allocation: may improve
17972 memory performance during directory parsing.
17973 - Treat duplicate certificate fetches as failures, so that we do
17974 not try to re-fetch an expired certificate over and over and over.
17975 - Do not say we're fetching a certificate when we'll in fact skip it
17976 because of a pending download.
17979 Changes in version 0.2.1.6-alpha - 2008-09-30
17980 Tor 0.2.1.6-alpha further improves performance and robustness of
17981 hidden services, starts work on supporting per-country relay selection,
17982 and fixes a variety of smaller issues.
17985 - Implement proposal 121: make it possible to build hidden services
17986 that only certain clients are allowed to connect to. This is
17987 enforced at several points, so that unauthorized clients are unable
17988 to send INTRODUCE cells to the service, or even (depending on the
17989 type of authentication) to learn introduction points. This feature
17990 raises the bar for certain kinds of active attacks against hidden
17991 services. Code by Karsten Loesing.
17992 - Relays now store and serve v2 hidden service descriptors by default,
17993 i.e., the new default value for HidServDirectoryV2 is 1. This is
17994 the last step in proposal 114, which aims to make hidden service
17995 lookups more reliable.
17996 - Start work to allow node restrictions to include country codes. The
17997 syntax to exclude nodes in a country with country code XX is
17998 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
17999 refinement to decide what config options should take priority if
18000 you ask to both use a particular node and exclude it.
18001 - Allow ExitNodes list to include IP ranges and country codes, just
18002 like the Exclude*Nodes lists. Patch from Robert Hogan.
18005 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
18006 Tor to fail to start if you had it configured to use a bridge
18007 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
18008 - When extending a circuit to a hidden service directory to upload a
18009 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
18010 requests failed, because the router descriptor had not been
18011 downloaded yet. In these cases, we now wait until the router
18012 descriptor is downloaded, and then retry. Likewise, clients
18013 now skip over a hidden service directory if they don't yet have
18014 its router descriptor, rather than futilely requesting it and
18015 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
18017 - When fetching v0 and v2 rendezvous service descriptors in parallel,
18018 we were failing the whole hidden service request when the v0
18019 descriptor fetch fails, even if the v2 fetch is still pending and
18020 might succeed. Similarly, if the last v2 fetch fails, we were
18021 failing the whole hidden service request even if a v0 fetch is
18022 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
18023 - DNS replies need to have names matching their requests, but
18024 these names should be in the questions section, not necessarily
18025 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
18028 - Update to the "September 1 2008" ip-to-country file.
18029 - Allow ports 465 and 587 in the default exit policy again. We had
18030 rejected them in 0.1.0.15, because back in 2005 they were commonly
18031 misconfigured and ended up as spam targets. We hear they are better
18032 locked down these days.
18033 - Use a lockfile to make sure that two Tor processes are not
18034 simultaneously running with the same datadir.
18035 - Serve the latest v3 networkstatus consensus via the control
18036 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
18037 - Better logging about stability/reliability calculations on directory
18039 - Drop the requirement to have an open dir port for storing and
18040 serving v2 hidden service descriptors.
18041 - Directory authorities now serve a /tor/dbg-stability.txt URL to
18042 help debug WFU and MTBF calculations.
18043 - Implement most of Proposal 152: allow specialized servers to permit
18044 single-hop circuits, and clients to use those servers to build
18045 single-hop circuits when using a specialized controller. Patch
18046 from Josh Albrecht. Resolves feature request 768.
18047 - Add a -p option to tor-resolve for specifying the SOCKS port: some
18048 people find host:port too confusing.
18049 - Make TrackHostExit mappings expire a while after their last use, not
18050 after their creation. Patch from Robert Hogan.
18051 - Provide circuit purposes along with circuit events to the controller.
18054 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
18056 - Fixed some memory leaks -- some quite frequent, some almost
18057 impossible to trigger -- based on results from Coverity.
18058 - When testing for libevent functions, set the LDFLAGS variable
18059 correctly. Found by Riastradh.
18060 - Fix an assertion bug in parsing policy-related options; possible fix
18062 - Catch and report a few more bootstrapping failure cases when Tor
18063 fails to establish a TCP connection. Cleanup on 0.2.1.x.
18064 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
18065 bootstrapping with tunneled directory connections. Bugfix on
18066 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
18067 - When asked to connect to A.B.exit:80, if we don't know the IP for A
18068 and we know that server B rejects most-but-not all connections to
18069 port 80, we would previously reject the connection. Now, we assume
18070 the user knows what they were asking for. Fixes bug 752. Bugfix
18071 on 0.0.9rc5. Diagnosed by BarkerJr.
18072 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
18073 service directories if they have no advertised dir port. Bugfix
18075 - If we overrun our per-second write limits a little, count this as
18076 having used up our write allocation for the second, and choke
18077 outgoing directory writes. Previously, we had only counted this when
18078 we had met our limits precisely. Fixes bug 824. Patch by rovv.
18079 Bugfix on 0.2.0.x (??).
18080 - Avoid a "0 divided by 0" calculation when calculating router uptime
18081 at directory authorities. Bugfix on 0.2.0.8-alpha.
18082 - Make DNS resolved controller events into "CLOSED", not
18083 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
18085 - Fix a bug where an unreachable relay would establish enough
18086 reachability testing circuits to do a bandwidth test -- if
18087 we already have a connection to the middle hop of the testing
18088 circuit, then it could establish the last hop by using the existing
18089 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
18090 circuits no longer use entry guards in 0.2.1.3-alpha.
18091 - If we have correct permissions on $datadir, we complain to stdout
18092 and fail to start. But dangerous permissions on
18093 $datadir/cached-status/ would cause us to open a log and complain
18094 there. Now complain to stdout and fail to start in both cases. Fixes
18095 bug 820, reported by seeess.
18096 - Remove the old v2 directory authority 'lefkada' from the default
18097 list. It has been gone for many months.
18099 o Code simplifications and refactoring:
18100 - Revise the connection_new functions so that a more typesafe variant
18101 exists. This will work better with Coverity, and let us find any
18102 actual mistakes we're making here.
18103 - Refactor unit testing logic so that dmalloc can be used sensibly
18104 with unit tests to check for memory leaks.
18105 - Move all hidden-service related fields from connection and circuit
18106 structure to substructures: this way they won't eat so much memory.
18109 Changes in version 0.2.0.31 - 2008-09-03
18110 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
18111 a big bug we're seeing where in rare cases traffic from one Tor stream
18112 gets mixed into another stream, and fixes a variety of smaller issues.
18115 - Make sure that two circuits can never exist on the same connection
18116 with the same circuit ID, even if one is marked for close. This
18117 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
18118 - Relays now reject risky extend cells: if the extend cell includes
18119 a digest of all zeroes, or asks to extend back to the relay that
18120 sent the extend cell, tear down the circuit. Ideas suggested
18122 - If not enough of our entry guards are available so we add a new
18123 one, we might use the new one even if it overlapped with the
18124 current circuit's exit relay (or its family). Anonymity bugfix
18125 pointed out by rovv.
18128 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18129 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18130 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18131 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18132 - Pick size of default geoip filename string correctly on windows.
18133 Fixes bug 806. Bugfix on 0.2.0.30.
18134 - Make the autoconf script accept the obsolete --with-ssl-dir
18135 option as an alias for the actually-working --with-openssl-dir
18136 option. Fix the help documentation to recommend --with-openssl-dir.
18137 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18138 - When using the TransPort option on OpenBSD, and using the User
18139 option to change UID and drop privileges, make sure to open
18140 /dev/pf before dropping privileges. Fixes bug 782. Patch from
18141 Christopher Davis. Bugfix on 0.1.2.1-alpha.
18142 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18143 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18144 on the client side when connecting to a hidden service. Bugfix
18145 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18146 - When closing an application-side connection because its circuit is
18147 getting torn down, generate the stream event correctly. Bugfix on
18148 0.1.2.x. Anonymous patch.
18151 Changes in version 0.2.1.5-alpha - 2008-08-31
18152 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
18153 in a lot of the infrastructure for adding authorization to hidden
18154 services, lays the groundwork for having clients read their load
18155 balancing information out of the networkstatus consensus rather than
18156 the individual router descriptors, addresses two potential anonymity
18157 issues, and fixes a variety of smaller issues.
18160 - Convert many internal address representations to optionally hold
18162 - Generate and accept IPv6 addresses in many protocol elements.
18163 - Make resolver code handle nameservers located at ipv6 addresses.
18164 - Begin implementation of proposal 121 ("Client authorization for
18165 hidden services"): configure hidden services with client
18166 authorization, publish descriptors for them, and configure
18167 authorization data for hidden services at clients. The next
18168 step is to actually access hidden services that perform client
18170 - More progress toward proposal 141: Network status consensus
18171 documents and votes now contain bandwidth information for each
18172 router and a summary of that router's exit policy. Eventually this
18173 will be used by clients so that they do not have to download every
18174 known descriptor before building circuits.
18176 o Major bugfixes (on 0.2.0.x and before):
18177 - When sending CREATED cells back for a given circuit, use a 64-bit
18178 connection ID to find the right connection, rather than an addr:port
18179 combination. Now that we can have multiple OR connections between
18180 the same ORs, it is no longer possible to use addr:port to uniquely
18181 identify a connection.
18182 - Relays now reject risky extend cells: if the extend cell includes
18183 a digest of all zeroes, or asks to extend back to the relay that
18184 sent the extend cell, tear down the circuit. Ideas suggested
18186 - If not enough of our entry guards are available so we add a new
18187 one, we might use the new one even if it overlapped with the
18188 current circuit's exit relay (or its family). Anonymity bugfix
18189 pointed out by rovv.
18192 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
18193 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
18194 - When using the TransPort option on OpenBSD, and using the User
18195 option to change UID and drop privileges, make sure to open /dev/pf
18196 before dropping privileges. Fixes bug 782. Patch from Christopher
18197 Davis. Bugfix on 0.1.2.1-alpha.
18198 - Correctly detect the presence of the linux/netfilter_ipv4.h header
18199 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
18200 - Add a missing safe_str() call for a debug log message.
18201 - Use 64 bits instead of 32 bits for connection identifiers used with
18202 the controller protocol, to greatly reduce risk of identifier reuse.
18203 - Make the autoconf script accept the obsolete --with-ssl-dir
18204 option as an alias for the actually-working --with-openssl-dir
18205 option. Fix the help documentation to recommend --with-openssl-dir.
18206 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
18209 - Rate-limit too-many-sockets messages: when they happen, they happen
18210 a lot. Resolves bug 748.
18211 - Resist DNS poisoning a little better by making sure that names in
18212 answer sections match.
18213 - Print the SOCKS5 error message string as well as the error code
18214 when a tor-resolve request fails. Patch from Jacob.
18217 Changes in version 0.2.1.4-alpha - 2008-08-04
18218 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
18221 - The address part of exit policies was not correctly written
18222 to router descriptors. This generated router descriptors that failed
18223 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
18225 - Tor triggered a false assert when extending a circuit to a relay
18226 but we already have a connection open to that relay. Noticed by
18227 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
18230 - Fix a hidden service logging bug: in some edge cases, the router
18231 descriptor of a previously picked introduction point becomes
18232 obsolete and we need to give up on it rather than continually
18233 complaining that it has become obsolete. Observed by xiando. Bugfix
18236 o Removed features:
18237 - Take out the TestVia config option, since it was a workaround for
18238 a bug that was fixed in Tor 0.1.1.21.
18241 Changes in version 0.2.1.3-alpha - 2008-08-03
18242 Tor 0.2.1.3-alpha implements most of the pieces to prevent
18243 infinite-length circuit attacks (see proposal 110); fixes a bug that
18244 might cause exit relays to corrupt streams they send back; allows
18245 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
18246 ExcludeExitNodes config options; and fixes a big pile of bugs.
18248 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
18249 - Send a bootstrap problem "warn" event on the first problem if the
18250 reason is NO_ROUTE (that is, our network is down).
18253 - Implement most of proposal 110: The first K cells to be sent
18254 along a circuit are marked as special "early" cells; only K "early"
18255 cells will be allowed. Once this code is universal, we can block
18256 certain kinds of DOS attack by requiring that EXTEND commands must
18257 be sent using an "early" cell.
18260 - Try to attach connections immediately upon receiving a RENDEZVOUS2
18261 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
18262 on the client side when connecting to a hidden service. Bugfix
18263 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
18264 - Ensure that two circuits can never exist on the same connection
18265 with the same circuit ID, even if one is marked for close. This
18266 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
18269 - When relays do their initial bandwidth measurement, don't limit
18270 to just our entry guards for the test circuits. Otherwise we tend
18271 to have multiple test circuits going through a single entry guard,
18272 which makes our bandwidth test less accurate. Fixes part of bug 654;
18273 patch contributed by Josh Albrecht.
18274 - Add an ExcludeExitNodes option so users can list a set of nodes
18275 that should be be excluded from the exit node position, but
18276 allowed elsewhere. Implements proposal 151.
18277 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
18278 ExcludeNodes and ExcludeExitNodes lists.
18279 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
18280 be more efficient. Formerly it was quadratic in the number of
18281 servers; now it should be linear. Fixes bug 509.
18282 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
18283 and n_conn_id_digest fields into a separate structure that's
18284 only needed when the circuit has not yet attached to an n_conn.
18287 - Change the contrib/tor.logrotate script so it makes the new
18288 logs as "_tor:_tor" rather than the default, which is generally
18289 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
18290 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
18291 warnings (occasionally), but it can also cause the compiler to
18292 eliminate error-checking code. Suggested by Peter Gutmann.
18293 - When a hidden service is giving up on an introduction point candidate
18294 that was not included in the last published rendezvous descriptor,
18295 don't reschedule publication of the next descriptor. Fixes bug 763.
18297 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
18298 HiddenServiceExcludeNodes as obsolete: they never worked properly,
18299 and nobody claims to be using them. Fixes bug 754. Bugfix on
18300 0.1.0.1-rc. Patch from Christian Wilms.
18301 - Fix a small alignment and memory-wasting bug on buffer chunks.
18304 o Minor bugfixes (controller):
18305 - When closing an application-side connection because its circuit
18306 is getting torn down, generate the stream event correctly.
18307 Bugfix on 0.1.2.x. Anonymous patch.
18309 o Removed features:
18310 - Remove all backward-compatibility code to support relays running
18311 versions of Tor so old that they no longer work at all on the
18315 Changes in version 0.2.0.30 - 2008-07-15
18317 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
18318 warnings (occasionally), but it can also cause the compiler to
18319 eliminate error-checking code. Suggested by Peter Gutmann.
18322 Changes in version 0.2.0.29-rc - 2008-07-08
18323 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
18324 hidden-service performance bugs, and fixes a bunch of smaller bugs.
18327 - If you have more than one bridge but don't know their keys,
18328 you would only launch a request for the descriptor of the first one
18329 on your list. (Tor considered launching requests for the others, but
18330 found that it already had a connection on the way for $0000...0000
18331 so it didn't open another.) Bugfix on 0.2.0.x.
18332 - If you have more than one bridge but don't know their keys, and the
18333 connection to one of the bridges failed, you would cancel all
18334 pending bridge connections. (After all, they all have the same
18335 digest.) Bugfix on 0.2.0.x.
18336 - When a hidden service was trying to establish an introduction point,
18337 and Tor had built circuits preemptively for such purposes, we
18338 were ignoring all the preemptive circuits and launching a new one
18339 instead. Bugfix on 0.2.0.14-alpha.
18340 - When a hidden service was trying to establish an introduction point,
18341 and Tor *did* manage to reuse one of the preemptively built
18342 circuits, it didn't correctly remember which one it used,
18343 so it asked for another one soon after, until there were no
18344 more preemptive circuits, at which point it launched one from
18345 scratch. Bugfix on 0.0.9.x.
18346 - Make directory servers include the X-Your-Address-Is: http header in
18347 their responses even for begin_dir conns. Now clients who only
18348 ever use begin_dir connections still have a way to learn their IP
18349 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
18352 - Fix a macro/CPP interaction that was confusing some compilers:
18353 some GCCs don't like #if/#endif pairs inside macro arguments.
18355 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
18356 Fixes bug 704; fix from Steven Murdoch.
18357 - When opening /dev/null in finish_daemonize(), do not pass the
18358 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
18359 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
18360 - Correctly detect transparent proxy support on Linux hosts that
18361 require in.h to be included before netfilter_ipv4.h. Patch
18363 - Disallow session resumption attempts during the renegotiation
18364 stage of the v2 handshake protocol. Clients should never be trying
18365 session resumption at this point, but apparently some did, in
18366 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
18367 found by Geoff Goodell.
18370 Changes in version 0.2.1.2-alpha - 2008-06-20
18371 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
18372 make it easier to set up your own private Tor network; fixes several
18373 big bugs with using more than one bridge relay; fixes a big bug with
18374 offering hidden services quickly after Tor starts; and uses a better
18375 API for reporting potential bootstrapping problems to the controller.
18378 - New TestingTorNetwork config option to allow adjustment of
18379 previously constant values that, while reasonable, could slow
18380 bootstrapping. Implements proposal 135. Patch from Karsten.
18383 - If you have more than one bridge but don't know their digests,
18384 you would only learn a request for the descriptor of the first one
18385 on your list. (Tor considered launching requests for the others, but
18386 found that it already had a connection on the way for $0000...0000
18387 so it didn't open another.) Bugfix on 0.2.0.x.
18388 - If you have more than one bridge but don't know their digests,
18389 and the connection to one of the bridges failed, you would cancel
18390 all pending bridge connections. (After all, they all have the
18391 same digest.) Bugfix on 0.2.0.x.
18392 - When establishing a hidden service, introduction points that
18393 originate from cannibalized circuits are completely ignored and not
18394 included in rendezvous service descriptors. This might be another
18395 reason for delay in making a hidden service available. Bugfix
18396 from long ago (0.0.9.x?)
18399 - Allow OpenSSL to use dynamic locks if it wants.
18400 - When building a consensus, do not include routers that are down.
18401 This will cut down 30% to 40% on consensus size. Implements
18403 - In directory authorities' approved-routers files, allow
18404 fingerprints with or without space.
18405 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
18406 controller can query our current bootstrap state in case it attaches
18407 partway through and wants to catch up.
18408 - Send an initial "Starting" bootstrap status event, so we have a
18409 state to start out in.
18412 - Asking for a conditional consensus at .../consensus/<fingerprints>
18413 would crash a dirserver if it did not already have a
18414 consensus. Bugfix on 0.2.1.1-alpha.
18415 - Clean up some macro/CPP interactions: some GCC versions don't like
18416 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
18419 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
18420 - Directory authorities shouldn't complain about bootstrapping
18421 problems just because they do a lot of reachability testing and
18422 some of the connection attempts fail.
18423 - Start sending "count" and "recommendation" key/value pairs in
18424 bootstrap problem status events, so the controller can hear about
18425 problems even before Tor decides they're worth reporting for sure.
18426 - If you're using bridges, generate "bootstrap problem" warnings
18427 as soon as you run out of working bridges, rather than waiting
18428 for ten failures -- which will never happen if you have less than
18430 - If we close our OR connection because there's been a circuit
18431 pending on it for too long, we were telling our bootstrap status
18432 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
18435 Changes in version 0.2.1.1-alpha - 2008-06-13
18436 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
18437 were making the Tor process bloat especially on Linux; makes our TLS
18438 handshake blend in better; sends "bootstrap phase" status events to
18439 the controller, so it can keep the user informed of progress (and
18440 problems) fetching directory information and establishing circuits;
18441 and adds a variety of smaller features.
18444 - More work on making our TLS handshake blend in: modify the list
18445 of ciphers advertised by OpenSSL in client mode to even more
18446 closely resemble a common web browser. We cheat a little so that
18447 we can advertise ciphers that the locally installed OpenSSL doesn't
18449 - Start sending "bootstrap phase" status events to the controller,
18450 so it can keep the user informed of progress fetching directory
18451 information and establishing circuits. Also inform the controller
18452 if we think we're stuck at a particular bootstrap phase. Implements
18454 - Resume using OpenSSL's RAND_poll() for better (and more portable)
18455 cross-platform entropy collection again. We used to use it, then
18456 stopped using it because of a bug that could crash systems that
18457 called RAND_poll when they had a lot of fds open. It looks like the
18458 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
18459 at startup, and to call RAND_poll() when we reseed later only if
18460 we have a non-buggy OpenSSL version.
18463 - When we choose to abandon a new entry guard because we think our
18464 older ones might be better, close any circuits pending on that
18465 new entry guard connection. This fix should make us recover much
18466 faster when our network is down and then comes back. Bugfix on
18467 0.1.2.8-beta; found by lodger.
18469 o Memory fixes and improvements:
18470 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
18471 to avoid unused RAM in buffer chunks and memory pools.
18472 - Speed up parsing and cut down on memory fragmentation by using
18473 stack-style allocations for parsing directory objects. Previously,
18474 this accounted for over 40% of allocations from within Tor's code
18475 on a typical directory cache.
18476 - Use a Bloom filter rather than a digest-based set to track which
18477 descriptors we need to keep around when we're cleaning out old
18478 router descriptors. This speeds up the computation significantly,
18479 and may reduce fragmentation.
18480 - Reduce the default smartlist size from 32 to 16; it turns out that
18481 most smartlists hold around 8-12 elements tops.
18482 - Make dumpstats() log the fullness and size of openssl-internal
18484 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
18485 patch to their OpenSSL, turn it on to save memory on servers. This
18486 patch will (with any luck) get included in a mainline distribution
18488 - Never use OpenSSL compression: it wastes RAM and CPU trying to
18489 compress cells, which are basically all encrypted, compressed,
18493 - Stop reloading the router list from disk for no reason when we
18494 run out of reachable directory mirrors. Once upon a time reloading
18495 it would set the 'is_running' flag back to 1 for them. It hasn't
18496 done that for a long time.
18497 - In very rare situations new hidden service descriptors were
18498 published earlier than 30 seconds after the last change to the
18499 service. (We currently think that a hidden service descriptor
18500 that's been stable for 30 seconds is worth publishing.)
18503 - Allow separate log levels to be configured for different logging
18504 domains. For example, this allows one to log all notices, warnings,
18505 or errors, plus all memory management messages of level debug or
18506 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
18507 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
18508 and stop using a warning that had become unfixably verbose under
18510 - New --hush command-line option similar to --quiet. While --quiet
18511 disables all logging to the console on startup, --hush limits the
18512 output to messages of warning and error severity.
18513 - Servers support a new URL scheme for consensus downloads that
18514 allows the client to specify which authorities are trusted.
18515 The server then only sends the consensus if the client will trust
18516 it. Otherwise a 404 error is sent back. Clients use this
18517 new scheme when the server supports it (meaning it's running
18518 0.2.1.1-alpha or later). Implements proposal 134.
18519 - New configure/torrc options (--enable-geoip-stats,
18520 DirRecordUsageByCountry) to record how many IPs we've served
18521 directory info to in each country code, how many status documents
18522 total we've sent to each country code, and what share of the total
18523 directory requests we should expect to see.
18524 - Use the TLS1 hostname extension to more closely resemble browser
18526 - Lots of new unit tests.
18527 - Add a macro to implement the common pattern of iterating through
18528 two parallel lists in lockstep.
18531 Changes in version 0.2.0.28-rc - 2008-06-13
18532 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
18533 performance bug, and fixes a bunch of smaller bugs.
18536 - Fix a bug where, when we were choosing the 'end stream reason' to
18537 put in our relay end cell that we send to the exit relay, Tor
18538 clients on Windows were sometimes sending the wrong 'reason'. The
18539 anonymity problem is that exit relays may be able to guess whether
18540 the client is running Windows, thus helping partition the anonymity
18541 set. Down the road we should stop sending reasons to exit relays,
18542 or otherwise prevent future versions of this bug.
18545 - While setting up a hidden service, some valid introduction circuits
18546 were overlooked and abandoned. This might be the reason for
18547 the long delay in making a hidden service available. Bugfix on
18551 - Update to the "June 9 2008" ip-to-country file.
18552 - Run 'make test' as part of 'make dist', so we stop releasing so
18553 many development snapshots that fail their unit tests.
18556 - When we're checking if we have enough dir info for each relay
18557 to begin establishing circuits, make sure that we actually have
18558 the descriptor listed in the consensus, not just any descriptor.
18560 - Bridge relays no longer print "xx=0" in their extrainfo document
18561 for every single country code in the geoip db. Bugfix on
18563 - Only warn when we fail to load the geoip file if we were planning to
18564 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
18565 - If we change our MaxAdvertisedBandwidth and then reload torrc,
18566 Tor won't realize it should publish a new relay descriptor. Fixes
18567 bug 688, reported by mfr. Bugfix on 0.1.2.x.
18568 - When we haven't had any application requests lately, don't bother
18569 logging that we have expired a bunch of descriptors. Bugfix
18571 - Make relay cells written on a connection count as non-padding when
18572 tracking how long a connection has been in use. Bugfix on
18573 0.2.0.1-alpha. Spotted by lodger.
18574 - Fix unit tests in 0.2.0.27-rc.
18575 - Fix compile on Windows.
18578 Changes in version 0.2.0.27-rc - 2008-06-03
18579 Tor 0.2.0.27-rc adds a few features we left out of the earlier
18580 release candidates. In particular, we now include an IP-to-country
18581 GeoIP database, so controllers can easily look up what country a
18582 given relay is in, and so bridge relays can give us some sanitized
18583 summaries about which countries are making use of bridges. (See proposal
18584 126-geoip-fetching.txt for details.)
18587 - Include an IP-to-country GeoIP file in the tarball, so bridge
18588 relays can report sanitized summaries of the usage they're seeing.
18591 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
18592 Robert Hogan. Fixes the first part of bug 681.
18593 - Make bridge authorities never serve extrainfo docs.
18594 - Add support to detect Libevent versions in the 1.4.x series
18596 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
18597 - Include a new contrib/tor-exit-notice.html file that exit relay
18598 operators can put on their website to help reduce abuse queries.
18601 - When tunneling an encrypted directory connection, and its first
18602 circuit fails, do not leave it unattached and ask the controller
18603 to deal. Fixes the second part of bug 681.
18604 - Make bridge authorities correctly expire old extrainfo documents
18608 Changes in version 0.2.0.26-rc - 2008-05-13
18609 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
18610 in Debian's OpenSSL packages. All users running any 0.2.0.x version
18611 should upgrade, whether they're running Debian or not.
18613 o Major security fixes:
18614 - Use new V3 directory authority keys on the tor26, gabelmoo, and
18615 moria1 V3 directory authorities. The old keys were generated with
18616 a vulnerable version of Debian's OpenSSL package, and must be
18617 considered compromised. Other authorities' keys were not generated
18618 with an affected version of OpenSSL.
18621 - List authority signatures as "unrecognized" based on DirServer
18622 lines, not on cert cache. Bugfix on 0.2.0.x.
18625 - Add a new V3AuthUseLegacyKey option to make it easier for
18626 authorities to change their identity keys if they have to.
18629 Changes in version 0.2.0.25-rc - 2008-04-23
18630 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
18633 - Remember to initialize threading before initializing logging.
18634 Otherwise, many BSD-family implementations will crash hard on
18635 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
18638 - Authorities correctly free policies on bad servers on
18639 exit. Fixes bug 672. Bugfix on 0.2.0.x.
18642 Changes in version 0.2.0.24-rc - 2008-04-22
18643 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
18644 v3 directory authority, makes relays with dynamic IP addresses and no
18645 DirPort notice more quickly when their IP address changes, fixes a few
18646 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
18648 o New directory authorities:
18649 - Take lefkada out of the list of v3 directory authorities, since
18650 it has been down for months.
18651 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
18655 - Detect address changes more quickly on non-directory mirror
18656 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
18658 o Minor features (security):
18659 - Reject requests for reverse-dns lookup of names that are in
18660 a private address space. Patch from lodger.
18661 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
18664 o Minor bugfixes (crashes):
18665 - Avoid a rare assert that can trigger when Tor doesn't have much
18666 directory information yet and it tries to fetch a v2 hidden
18667 service descriptor. Fixes bug 651, reported by nwf.
18668 - Initialize log mutex before initializing dmalloc. Otherwise,
18669 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
18670 - Use recursive pthread mutexes in order to avoid deadlock when
18671 logging debug-level messages to a controller. Bug spotted by nwf,
18672 bugfix on 0.2.0.16-alpha.
18674 o Minor bugfixes (resource management):
18675 - Keep address policies from leaking memory: start their refcount
18676 at 1, not 2. Bugfix on 0.2.0.16-alpha.
18677 - Free authority certificates on exit, so they don't look like memory
18678 leaks. Bugfix on 0.2.0.19-alpha.
18679 - Free static hashtables for policy maps and for TLS connections on
18680 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
18681 - Avoid allocating extra space when computing consensuses on 64-bit
18682 platforms. Bug spotted by aakova.
18684 o Minor bugfixes (misc):
18685 - Do not read the configuration file when we've only been told to
18686 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
18687 based on patch from Sebastian Hahn.
18688 - Exit relays that are used as a client can now reach themselves
18689 using the .exit notation, rather than just launching an infinite
18690 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
18691 - When attempting to open a logfile fails, tell us why.
18692 - Fix a dumb bug that was preventing us from knowing that we should
18693 preemptively build circuits to handle expected directory requests.
18694 Fixes bug 660. Bugfix on 0.1.2.x.
18695 - Warn less verbosely about clock skew from netinfo cells from
18696 untrusted sources. Fixes bug 663.
18697 - Make controller stream events for DNS requests more consistent,
18698 by adding "new stream" events for DNS requests, and removing
18699 spurious "stream closed" events" for cached reverse resolves.
18700 Patch from mwenge. Fixes bug 646.
18701 - Correctly notify one-hop connections when a circuit build has
18702 failed. Possible fix for bug 669. Found by lodger.
18705 Changes in version 0.2.0.23-rc - 2008-03-24
18706 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
18707 makes bootstrapping faster if the first directory mirror you contact
18708 is down. The bundles also include the new Vidalia 0.1.2 release.
18711 - When a tunneled directory request is made to a directory server
18712 that's down, notice after 30 seconds rather than 120 seconds. Also,
18713 fail any begindir streams that are pending on it, so they can
18714 retry elsewhere. This was causing multi-minute delays on bootstrap.
18717 Changes in version 0.2.0.22-rc - 2008-03-18
18718 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
18719 enables encrypted directory connections by default for non-relays, fixes
18720 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
18721 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
18724 - Enable encrypted directory connections by default for non-relays,
18725 so censor tools that block Tor directory connections based on their
18726 plaintext patterns will no longer work. This means Tor works in
18727 certain censored countries by default again.
18730 - Make sure servers always request certificates from clients during
18731 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
18732 - Do not enter a CPU-eating loop when a connection is closed in
18733 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
18734 diagnosed by lodger; bugfix on 0.2.0.20-rc.
18735 - Fix assertion failure that could occur when a blocked circuit
18736 became unblocked, and it had pending client DNS requests. Bugfix
18737 on 0.2.0.1-alpha. Fixes bug 632.
18739 o Minor bugfixes (on 0.1.2.x):
18740 - Generate "STATUS_SERVER" events rather than misspelled
18741 "STATUS_SEVER" events. Caught by mwenge.
18742 - When counting the number of bytes written on a TLS connection,
18743 look at the BIO actually used for writing to the network, not
18744 at the BIO used (sometimes) to buffer data for the network.
18745 Looking at different BIOs could result in write counts on the
18746 order of ULONG_MAX. Fixes bug 614.
18747 - On Windows, correctly detect errors when listing the contents of
18748 a directory. Fix from lodger.
18750 o Minor bugfixes (on 0.2.0.x):
18751 - Downgrade "sslv3 alert handshake failure" message to INFO.
18752 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
18753 left BandwidthRate and BandwidthBurst at the default, we would be
18754 silently limited by those defaults. Now raise them to match the
18755 RelayBandwidth* values.
18756 - Fix the SVK version detection logic to work correctly on a branch.
18757 - Make --enable-openbsd-malloc work correctly on Linux with alpha
18758 CPUs. Fixes bug 625.
18759 - Logging functions now check that the passed severity is sane.
18760 - Use proper log levels in the testsuite call of
18761 get_interface_address6().
18762 - When using a nonstandard malloc, do not use the platform values for
18763 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
18764 - Make the openbsd malloc code use 8k pages on alpha CPUs and
18766 - Detect mismatched page sizes when using --enable-openbsd-malloc.
18767 - Avoid double-marked-for-close warning when certain kinds of invalid
18768 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
18769 for bug 617. Bugfix on 0.2.0.1-alpha.
18770 - Make sure that the "NULL-means-reject *:*" convention is followed by
18771 all the policy manipulation functions, avoiding some possible crash
18772 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
18773 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
18774 actually works, and doesn't warn about every single reverse lookup.
18775 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
18778 - Only log guard node status when guard node status has changed.
18779 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
18780 make "INFO" 75% less verbose.
18783 Changes in version 0.2.0.21-rc - 2008-03-02
18784 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
18785 makes Tor work well with Vidalia again, fixes a rare assert bug,
18786 and fixes a pair of more minor bugs. The bundles also include Vidalia
18787 0.1.0 and Torbutton 1.1.16.
18790 - The control port should declare that it requires password auth
18791 when HashedControlSessionPassword is set too. Patch from Matt Edman;
18792 bugfix on 0.2.0.20-rc. Fixes bug 615.
18793 - Downgrade assert in connection_buckets_decrement() to a log message.
18794 This may help us solve bug 614, and in any case will make its
18795 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
18796 - We were sometimes miscounting the number of bytes read from the
18797 network, causing our rate limiting to not be followed exactly.
18798 Bugfix on 0.2.0.16-alpha. Reported by lodger.
18801 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
18802 OpenSSL versions should have been working fine. Diagnosis and patch
18803 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
18804 Bugfix on 0.2.0.20-rc.
18807 Changes in version 0.2.0.20-rc - 2008-02-24
18808 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
18809 makes more progress towards normalizing Tor's TLS handshake, makes
18810 hidden services work better again, helps relays bootstrap if they don't
18811 know their IP address, adds optional support for linking in openbsd's
18812 allocator or tcmalloc, allows really fast relays to scale past 15000
18813 sockets, and fixes a bunch of minor bugs reported by Veracode.
18816 - Enable the revised TLS handshake based on the one designed by
18817 Steven Murdoch in proposal 124, as revised in proposal 130. It
18818 includes version negotiation for OR connections as described in
18819 proposal 105. The new handshake is meant to be harder for censors
18820 to fingerprint, and it adds the ability to detect certain kinds of
18821 man-in-the-middle traffic analysis attacks. The version negotiation
18822 feature will allow us to improve Tor's link protocol more safely
18824 - Choose which bridge to use proportional to its advertised bandwidth,
18825 rather than uniformly at random. This should speed up Tor for
18826 bridge users. Also do this for people who set StrictEntryNodes.
18827 - When a TrackHostExits-chosen exit fails too many times in a row,
18828 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
18831 - Resolved problems with (re-)fetching hidden service descriptors.
18832 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
18833 and 0.2.0.19-alpha.
18834 - If we only ever used Tor for hidden service lookups or posts, we
18835 would stop building circuits and start refusing connections after
18836 24 hours, since we falsely believed that Tor was dormant. Reported
18837 by nwf; bugfix on 0.1.2.x.
18838 - Servers that don't know their own IP address should go to the
18839 authorities for their first directory fetch, even if their DirPort
18840 is off or if they don't know they're reachable yet. This will help
18841 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
18842 - When counting the number of open sockets, count not only the number
18843 of sockets we have received from the socket() call, but also
18844 the number we've gotten from accept() and socketpair(). This bug
18845 made us fail to count all sockets that we were using for incoming
18846 connections. Bugfix on 0.2.0.x.
18847 - Fix code used to find strings within buffers, when those strings
18848 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
18849 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
18850 - Add a new __HashedControlSessionPassword option for controllers
18851 to use for one-off session password hashes that shouldn't get
18852 saved to disk by SAVECONF --- Vidalia users were accumulating a
18853 pile of HashedControlPassword lines in their torrc files, one for
18854 each time they had restarted Tor and then clicked Save. Make Tor
18855 automatically convert "HashedControlPassword" to this new option but
18856 only when it's given on the command line. Partial fix for bug 586.
18858 o Minor features (performance):
18859 - Tune parameters for cell pool allocation to minimize amount of
18861 - Add OpenBSD malloc code from phk as an optional malloc
18862 replacement on Linux: some glibc libraries do very poorly
18863 with Tor's memory allocation patterns. Pass
18864 --enable-openbsd-malloc to get the replacement malloc code.
18865 - Add a --with-tcmalloc option to the configure script to link
18866 against tcmalloc (if present). Does not yet search for
18867 non-system include paths.
18868 - Stop imposing an arbitrary maximum on the number of file descriptors
18869 used for busy servers. Bug reported by Olaf Selke; patch from
18872 o Minor features (other):
18873 - When SafeLogging is disabled, log addresses along with all TLS
18875 - When building with --enable-gcc-warnings, check for whether Apple's
18876 warning "-Wshorten-64-to-32" is available.
18877 - Add a --passphrase-fd argument to the tor-gencert command for
18880 o Minor bugfixes (memory leaks and code problems):
18881 - We were leaking a file descriptor if Tor started with a zero-length
18882 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
18883 - Detect size overflow in zlib code. Reported by Justin Ferguson and
18885 - We were comparing the raw BridgePassword entry with a base64'ed
18886 version of it, when handling a "/tor/networkstatus-bridges"
18887 directory request. Now compare correctly. Noticed by Veracode.
18888 - Recover from bad tracked-since value in MTBF-history file.
18889 Should fix bug 537.
18890 - Alter the code that tries to recover from unhandled write
18891 errors, to not try to flush onto a socket that's given us
18892 unhandled errors. Bugfix on 0.1.2.x.
18893 - Make Unix controlsockets work correctly on OpenBSD. Patch from
18894 tup. Bugfix on 0.2.0.3-alpha.
18896 o Minor bugfixes (other):
18897 - If we have an extra-info document for our server, always make
18898 it available on the control port, even if we haven't gotten
18899 a copy of it from an authority yet. Patch from mwenge.
18900 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
18901 - Directory mirrors no longer include a guess at the client's IP
18902 address if the connection appears to be coming from the same /24
18903 network; it was producing too many wrong guesses.
18904 - Make the new hidden service code respect the SafeLogging setting.
18905 Bugfix on 0.2.0.x. Patch from Karsten.
18906 - When starting as an authority, do not overwrite all certificates
18907 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
18908 - If we're trying to flush the last bytes on a connection (for
18909 example, when answering a directory request), reset the
18910 time-to-give-up timeout every time we manage to write something
18911 on the socket. Bugfix on 0.1.2.x.
18912 - Change the behavior of "getinfo status/good-server-descriptor"
18913 so it doesn't return failure when any authority disappears.
18914 - Even though the man page said that "TrackHostExits ." should
18915 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
18916 - Report TLS "zero return" case as a "clean close" and "IO error"
18917 as a "close". Stop calling closes "unexpected closes": existing
18918 Tors don't use SSL_close(), so having a connection close without
18919 the TLS shutdown handshake is hardly unexpected.
18920 - Send NAMESERVER_STATUS messages for a single failed nameserver
18923 o Code simplifications and refactoring:
18924 - Remove the tor_strpartition function: its logic was confused,
18925 and it was only used for one thing that could be implemented far
18929 Changes in version 0.2.0.19-alpha - 2008-02-09
18930 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
18931 handshake, makes path selection for relays more secure and IP address
18932 guessing more robust, and generally fixes a lot of bugs in preparation
18933 for calling the 0.2.0 branch stable.
18936 - Do not include recognizeable strings in the commonname part of
18937 Tor's x509 certificates.
18940 - If we're a relay, avoid picking ourselves as an introduction point,
18941 a rendezvous point, or as the final hop for internal circuits. Bug
18942 reported by taranis and lodger. Bugfix on 0.1.2.x.
18943 - Patch from "Andrew S. Lists" to catch when we contact a directory
18944 mirror at IP address X and he says we look like we're coming from
18945 IP address X. Bugfix on 0.1.2.x.
18947 o Minor features (security):
18948 - Be more paranoid about overwriting sensitive memory on free(),
18949 as a defensive programming tactic to ensure forward secrecy.
18951 o Minor features (directory authority):
18952 - Actually validate the options passed to AuthDirReject,
18953 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
18954 - Reject router descriptors with out-of-range bandwidthcapacity or
18955 bandwidthburst values.
18957 o Minor features (controller):
18958 - Reject controller commands over 1MB in length. This keeps rogue
18959 processes from running us out of memory.
18961 o Minor features (misc):
18962 - Give more descriptive well-formedness errors for out-of-range
18963 hidden service descriptor/protocol versions.
18964 - Make memory debugging information describe more about history
18965 of cell allocation, so we can help reduce our memory use.
18967 o Deprecated features (controller):
18968 - The status/version/num-versioning and status/version/num-concurring
18969 GETINFO options are no longer useful in the v3 directory protocol:
18970 treat them as deprecated, and warn when they're used.
18973 - When our consensus networkstatus has been expired for a while, stop
18974 being willing to build circuits using it. Fixes bug 401. Bugfix
18976 - Directory caches now fetch certificates from all authorities
18977 listed in a networkstatus consensus, even when they do not
18978 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
18979 - When connecting to a bridge without specifying its key, insert
18980 the connection into the identity-to-connection map as soon as
18981 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
18982 - Detect versions of OS X where malloc_good_size() is present in the
18983 library but never actually declared. Resolves bug 587. Bugfix
18985 - Stop incorrectly truncating zlib responses to directory authority
18986 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
18987 - Stop recommending that every server operator send mail to tor-ops.
18988 Resolves bug 597. Bugfix on 0.1.2.x.
18989 - Don't trigger an assert if we start a directory authority with a
18990 private IP address (like 127.0.0.1).
18991 - Avoid possible failures when generating a directory with routers
18992 with over-long versions strings, or too many flags set. Bugfix
18994 - If an attempt to launch a DNS resolve request over the control
18995 port fails because we have overrun the limit on the number of
18996 connections, tell the controller that the request has failed.
18997 - Avoid using too little bandwidth when our clock skips a few
18998 seconds. Bugfix on 0.1.2.x.
18999 - Fix shell error when warning about missing packages in configure
19000 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
19001 - Do not become confused when receiving a spurious VERSIONS-like
19002 cell from a confused v1 client. Bugfix on 0.2.0.x.
19003 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
19004 introduction points for a hidden service have failed. Patch from
19005 Karsten Loesing. Bugfix on 0.2.0.x.
19007 o Code simplifications and refactoring:
19008 - Remove some needless generality from cpuworker code, for improved
19010 - Stop overloading the circuit_t.onionskin field for both "onionskin
19011 from a CREATE cell that we are waiting for a cpuworker to be
19012 assigned" and "onionskin from an EXTEND cell that we are going to
19013 send to an OR as soon as we are connected". Might help with bug 600.
19014 - Add an in-place version of aes_crypt() so that we can avoid doing a
19015 needless memcpy() call on each cell payload.
19018 Changes in version 0.2.0.18-alpha - 2008-01-25
19019 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
19020 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
19021 that can warn or reject connections to ports generally associated with
19022 vulnerable-plaintext protocols.
19024 o New directory authorities:
19025 - Set up dannenberg (run by CCC) as the sixth v3 directory
19029 - Fix a major memory leak when attempting to use the v2 TLS
19030 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
19031 - We accidentally enabled the under-development v2 TLS handshake
19032 code, which was causing log entries like "TLS error while
19033 renegotiating handshake". Disable it again. Resolves bug 590.
19034 - We were computing the wrong Content-Length: header for directory
19035 responses that need to be compressed on the fly, causing clients
19036 asking for those items to always fail. Bugfix on 0.2.0.x; partially
19040 - Avoid going directly to the directory authorities even if you're a
19041 relay, if you haven't found yourself reachable yet or if you've
19042 decided not to advertise your dirport yet. Addresses bug 556.
19043 - If we've gone 12 hours since our last bandwidth check, and we
19044 estimate we have less than 50KB bandwidth capacity but we could
19045 handle more, do another bandwidth test.
19046 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
19047 Tor can warn and/or refuse connections to ports commonly used with
19048 vulnerable-plaintext protocols. Currently we warn on ports 23,
19049 109, 110, and 143, but we don't reject any.
19052 - When we setconf ClientOnly to 1, close any current OR and Dir
19053 listeners. Reported by mwenge.
19054 - When we get a consensus that's been signed by more people than
19055 we expect, don't log about it; it's not a big deal. Reported
19059 - Don't answer "/tor/networkstatus-bridges" directory requests if
19060 the request isn't encrypted.
19061 - Make "ClientOnly 1" config option disable directory ports too.
19062 - Patches from Karsten Loesing to make v2 hidden services more
19063 robust: work even when there aren't enough HSDir relays available;
19064 retry when a v2 rend desc fetch fails; but don't retry if we
19065 already have a usable v0 rend desc.
19068 Changes in version 0.2.0.17-alpha - 2008-01-17
19069 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
19072 - Make the tor-gencert man page get included correctly in the tarball.
19075 Changes in version 0.2.0.16-alpha - 2008-01-17
19076 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
19077 Loesing, and generally cleans up a lot of features and minor bugs.
19079 o New directory authorities:
19080 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
19083 o Major performance improvements:
19084 - Switch our old ring buffer implementation for one more like that
19085 used by free Unix kernels. The wasted space in a buffer with 1mb
19086 of data will now be more like 8k than 1mb. The new implementation
19087 also avoids realloc();realloc(); patterns that can contribute to
19088 memory fragmentation.
19091 - Configuration files now accept C-style strings as values. This
19092 helps encode characters not allowed in the current configuration
19093 file format, such as newline or #. Addresses bug 557.
19094 - Although we fixed bug 539 (where servers would send HTTP status 503
19095 responses _and_ send a body too), there are still servers out
19096 there that haven't upgraded. Therefore, make clients parse such
19097 bodies when they receive them.
19098 - When we're not serving v2 directory information, there is no reason
19099 to actually keep any around. Remove the obsolete files and directory
19100 on startup if they are very old and we aren't going to serve them.
19102 o Minor performance improvements:
19103 - Reference-count and share copies of address policy entries; only 5%
19104 of them were actually distinct.
19105 - Never walk through the list of logs if we know that no log is
19106 interested in a given message.
19109 - When an authority has not signed a consensus, do not try to
19110 download a nonexistent "certificate with key 00000000". Bugfix
19111 on 0.2.0.x. Fixes bug 569.
19112 - Fix a rare assert error when we're closing one of our threads:
19113 use a mutex to protect the list of logs, so we never write to the
19114 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
19115 bug 575, which is kind of the revenge of bug 222.
19116 - Patch from Karsten Loesing to complain less at both the client
19117 and the relay when a relay used to have the HSDir flag but doesn't
19118 anymore, and we try to upload a hidden service descriptor.
19119 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
19121 - Do not try to download missing certificates until we have tried
19122 to check our fallback consensus. Fixes bug 583.
19123 - Make bridges round reported GeoIP stats info up to the nearest
19124 estimate, not down. Now we can distinguish between "0 people from
19125 this country" and "1 person from this country".
19126 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
19127 - Avoid possible segfault if key generation fails in
19128 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
19129 - Avoid segfault in the case where a badly behaved v2 versioning
19130 directory sends a signed networkstatus with missing client-versions.
19132 - Avoid segfaults on certain complex invocations of
19133 router_get_by_hexdigest(). Bugfix on 0.1.2.
19134 - Correct bad index on array access in parse_http_time(). Bugfix
19136 - Fix possible bug in vote generation when server versions are present
19137 but client versions are not.
19138 - Fix rare bug on REDIRECTSTREAM control command when called with no
19139 port set: it could erroneously report an error when none had
19141 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
19142 compressing large objects and find ourselves with more than 4k
19143 left over. Bugfix on 0.2.0.
19144 - Fix a small memory leak when setting up a hidden service.
19145 - Fix a few memory leaks that could in theory happen under bizarre
19147 - Fix an assert if we post a general-purpose descriptor via the
19148 control port but that descriptor isn't mentioned in our current
19149 network consensus. Bug reported by Jon McLachlan; bugfix on
19152 o Minor features (controller):
19153 - Get NS events working again. Patch from tup.
19154 - The GETCONF command now escapes and quotes configuration values
19155 that don't otherwise fit into the torrc file.
19156 - The SETCONF command now handles quoted values correctly.
19158 o Minor features (directory authorities):
19159 - New configuration options to override default maximum number of
19160 servers allowed on a single IP address. This is important for
19161 running a test network on a single host.
19162 - Actually implement the -s option to tor-gencert.
19163 - Add a manual page for tor-gencert.
19165 o Minor features (bridges):
19166 - Bridge authorities no longer serve bridge descriptors over
19167 unencrypted connections.
19169 o Minor features (other):
19170 - Add hidden services and DNSPorts to the list of things that make
19171 Tor accept that it has running ports. Change starting Tor with no
19172 ports from a fatal error to a warning; we might change it back if
19173 this turns out to confuse anybody. Fixes bug 579.
19176 Changes in version 0.1.2.19 - 2008-01-17
19177 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
19178 exit policy a little bit more conservative so it's safer to run an
19179 exit relay on a home system, and fixes a variety of smaller issues.
19182 - Exit policies now reject connections that are addressed to a
19183 relay's public (external) IP address too, unless
19184 ExitPolicyRejectPrivate is turned off. We do this because too
19185 many relays are running nearby to services that trust them based
19186 on network address.
19189 - When the clock jumps forward a lot, do not allow the bandwidth
19190 buckets to become negative. Fixes bug 544.
19191 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
19192 on every successful resolve. Reported by Mike Perry.
19193 - Purge old entries from the "rephist" database and the hidden
19194 service descriptor database even when DirPort is zero.
19195 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
19196 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
19197 crashing or mis-answering these requests.
19198 - When we decide to send a 503 response to a request for servers, do
19199 not then also send the server descriptors: this defeats the whole
19200 purpose. Fixes bug 539.
19203 - Changing the ExitPolicyRejectPrivate setting should cause us to
19204 rebuild our server descriptor.
19205 - Fix handling of hex nicknames when answering controller requests for
19206 networkstatus by name, or when deciding whether to warn about
19207 unknown routers in a config option. (Patch from mwenge.)
19208 - Fix a couple of hard-to-trigger autoconf problems that could result
19209 in really weird results on platforms whose sys/types.h files define
19210 nonstandard integer types.
19211 - Don't try to create the datadir when running --verify-config or
19212 --hash-password. Resolves bug 540.
19213 - If we were having problems getting a particular descriptor from the
19214 directory caches, and then we learned about a new descriptor for
19215 that router, we weren't resetting our failure count. Reported
19217 - Although we fixed bug 539 (where servers would send HTTP status 503
19218 responses _and_ send a body too), there are still servers out there
19219 that haven't upgraded. Therefore, make clients parse such bodies
19220 when they receive them.
19221 - Run correctly on systems where rlim_t is larger than unsigned long.
19222 This includes some 64-bit systems.
19223 - Run correctly on platforms (like some versions of OS X 10.5) where
19224 the real limit for number of open files is OPEN_FILES, not rlim_max
19225 from getrlimit(RLIMIT_NOFILES).
19226 - Avoid a spurious free on base64 failure.
19227 - Avoid segfaults on certain complex invocations of
19228 router_get_by_hexdigest().
19229 - Fix rare bug on REDIRECTSTREAM control command when called with no
19230 port set: it could erroneously report an error when none had
19234 Changes in version 0.2.0.15-alpha - 2007-12-25
19235 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
19236 features added in 0.2.0.13-alpha.
19239 - Fix several remotely triggerable asserts based on DirPort requests
19240 for a v2 or v3 networkstatus object before we were prepared. This
19241 was particularly bad for 0.2.0.13 and later bridge relays, who
19242 would never have a v2 networkstatus and would thus always crash
19243 when used. Bugfixes on 0.2.0.x.
19244 - Estimate the v3 networkstatus size more accurately, rather than
19245 estimating it at zero bytes and giving it artificially high priority
19246 compared to other directory requests. Bugfix on 0.2.0.x.
19249 - Fix configure.in logic for cross-compilation.
19250 - When we load a bridge descriptor from the cache, and it was
19251 previously unreachable, mark it as retriable so we won't just
19252 ignore it. Also, try fetching a new copy immediately. Bugfixes
19254 - The bridge GeoIP stats were counting other relays, for example
19255 self-reachability and authority-reachability tests.
19258 - Support compilation to target iPhone; patch from cjacker huang.
19259 To build for iPhone, pass the --enable-iphone option to configure.
19262 Changes in version 0.2.0.14-alpha - 2007-12-23
19264 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
19265 without a datadirectory from a previous Tor install. Reported
19267 - Fix a crash when we fetch a descriptor that turns out to be
19268 unexpected (it used to be in our networkstatus when we started
19269 fetching it, but it isn't in our current networkstatus), and we
19270 aren't using bridges. Bugfix on 0.2.0.x.
19271 - Fix a crash when accessing hidden services: it would work the first
19272 time you use a given introduction point for your service, but
19273 on subsequent requests we'd be using garbage memory. Fixed by
19274 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
19275 - Fix a crash when we load a bridge descriptor from disk but we don't
19276 currently have a Bridge line for it in our torrc. Bugfix on
19280 - If bridge authorities set BridgePassword, they will serve a
19281 snapshot of known bridge routerstatuses from their DirPort to
19282 anybody who knows that password. Unset by default.
19285 - Make the unit tests build again.
19286 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
19287 - Make PublishServerDescriptor default to 1, so the default doesn't
19288 have to change as we invent new directory protocol versions.
19289 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
19290 be included unless sys/time.h is already included. Fixes
19291 bug 553. Bugfix on 0.2.0.x.
19292 - If we receive a general-purpose descriptor and then receive an
19293 identical bridge-purpose descriptor soon after, don't discard
19294 the next one as a duplicate.
19297 - If BridgeRelay is set to 1, then the default for
19298 PublishServerDescriptor is now "bridge" rather than "v2,v3".
19299 - If the user sets RelayBandwidthRate but doesn't set
19300 RelayBandwidthBurst, then make them equal rather than erroring out.
19303 Changes in version 0.2.0.13-alpha - 2007-12-21
19304 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
19305 Goodell, fixes many more bugs, and adds a lot of infrastructure for
19308 o New directory authorities:
19309 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
19313 - Only update guard status (usable / not usable) once we have
19314 enough directory information. This was causing us to always pick
19315 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
19316 causing us to discard all our guards on startup if we hadn't been
19317 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
19318 - Purge old entries from the "rephist" database and the hidden
19319 service descriptor databases even when DirPort is zero. Bugfix
19321 - We were ignoring our RelayBandwidthRate for the first 30 seconds
19322 after opening a circuit -- even a relayed circuit. Bugfix on
19324 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
19325 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
19326 crashing or mis-answering these types of requests.
19327 - Relays were publishing their server descriptor to v1 and v2
19328 directory authorities, but they didn't try publishing to v3-only
19329 authorities. Fix this; and also stop publishing to v1 authorities.
19331 - When we were reading router descriptors from cache, we were ignoring
19332 the annotations -- so for example we were reading in bridge-purpose
19333 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
19334 - When we decided to send a 503 response to a request for servers, we
19335 were then also sending the server descriptors: this defeats the
19336 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
19339 - Bridge relays now behave like clients with respect to time
19340 intervals for downloading new consensus documents -- otherwise they
19341 stand out. Bridge users now wait until the end of the interval,
19342 so their bridge relay will be sure to have a new consensus document.
19343 - Three new config options (AlternateDirAuthority,
19344 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
19345 user selectively replace the default directory authorities by type,
19346 rather than the all-or-nothing replacement that DirServer offers.
19347 - Tor can now be configured to read a GeoIP file from disk in one
19348 of two formats. This can be used by controllers to map IP addresses
19349 to countries. Eventually, it may support exit-by-country.
19350 - When possible, bridge relays remember which countries users
19351 are coming from, and report aggregate information in their
19352 extra-info documents, so that the bridge authorities can learn
19353 where Tor is blocked.
19354 - Bridge directory authorities now do reachability testing on the
19355 bridges they know. They provide router status summaries to the
19356 controller via "getinfo ns/purpose/bridge", and also dump summaries
19357 to a file periodically.
19358 - Stop fetching directory info so aggressively if your DirPort is
19359 on but your ORPort is off; stop fetching v2 dir info entirely.
19360 You can override these choices with the new FetchDirInfoEarly
19364 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
19365 consensus documents when there are too many relays at a single
19366 IP address. Now clear it in v2 network status documents too, and
19367 also clear it in routerinfo_t when the relay is no longer listed
19368 in the relevant networkstatus document.
19369 - Don't crash if we get an unexpected value for the
19370 PublishServerDescriptor config option. Reported by Matt Edman;
19371 bugfix on 0.2.0.9-alpha.
19372 - Our new v2 hidden service descriptor format allows descriptors
19373 that have no introduction points. But Tor crashed when we tried
19374 to build a descriptor with no intro points (and it would have
19375 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
19376 by Karsten Loesing.
19377 - Fix building with dmalloc 5.5.2 with glibc.
19378 - Reject uploaded descriptors and extrainfo documents if they're
19379 huge. Otherwise we'll cache them all over the network and it'll
19380 clog everything up. Reported by Aljosha Judmayer.
19381 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
19382 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
19383 - When the DANGEROUS_VERSION controller status event told us we're
19384 running an obsolete version, it used the string "OLD" to describe
19385 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
19386 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
19387 - If we can't expand our list of entry guards (e.g. because we're
19388 using bridges or we have StrictEntryNodes set), don't mark relays
19389 down when they fail a directory request. Otherwise we're too quick
19390 to mark all our entry points down. Bugfix on 0.1.2.x.
19391 - Fix handling of hex nicknames when answering controller requests for
19392 networkstatus by name, or when deciding whether to warn about unknown
19393 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
19394 - Fix a couple of hard-to-trigger autoconf problems that could result
19395 in really weird results on platforms whose sys/types.h files define
19396 nonstandard integer types. Bugfix on 0.1.2.x.
19397 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
19398 - Don't crash on name lookup when we have no current consensus. Fixes
19399 bug 538; bugfix on 0.2.0.x.
19400 - Only Tors that want to mirror the v2 directory info should
19401 create the "cached-status" directory in their datadir. (All Tors
19402 used to create it.) Bugfix on 0.2.0.9-alpha.
19403 - Directory authorities should only automatically download Extra Info
19404 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
19407 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
19408 consumers. (We already do this on HUP.)
19409 - Authorities and caches fetch the v2 networkstatus documents
19410 less often, now that v3 is encouraged.
19411 - Add a new config option BridgeRelay that specifies you want to
19412 be a bridge relay. Right now the only difference is that it makes
19413 you answer begin_dir requests, and it makes you cache dir info,
19414 even if your DirPort isn't on.
19415 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
19416 ask about source, timestamp of arrival, purpose, etc. We need
19417 something like this to help Vidalia not do GeoIP lookups on bridge
19419 - Allow multiple HashedControlPassword config lines, to support
19420 multiple controller passwords.
19421 - Authorities now decide whether they're authoritative for a given
19422 router based on the router's purpose.
19423 - New config options AuthDirBadDir and AuthDirListBadDirs for
19424 authorities to mark certain relays as "bad directories" in the
19425 networkstatus documents. Also supports the "!baddir" directive in
19426 the approved-routers file.
19429 Changes in version 0.2.0.12-alpha - 2007-11-16
19430 This twelfth development snapshot fixes some more build problems as
19431 well as a few minor bugs.
19434 - Make it build on OpenBSD again. Patch from tup.
19435 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
19436 package-building for Red Hat, OS X, etc.
19438 o Minor bugfixes (on 0.1.2.x):
19439 - Changing the ExitPolicyRejectPrivate setting should cause us to
19440 rebuild our server descriptor.
19442 o Minor bugfixes (on 0.2.0.x):
19443 - When we're lacking a consensus, don't try to perform rendezvous
19444 operations. Reported by Karsten Loesing.
19445 - Fix a small memory leak whenever we decide against using a
19446 newly picked entry guard. Reported by Mike Perry.
19447 - When authorities detected more than two relays running on the same
19448 IP address, they were clearing all the status flags but forgetting
19449 to clear the "hsdir" flag. So clients were being told that a
19450 given relay was the right choice for a v2 hsdir lookup, yet they
19451 never had its descriptor because it was marked as 'not running'
19453 - If we're trying to fetch a bridge descriptor and there's no way
19454 the bridge authority could help us (for example, we don't know
19455 a digest, or there is no bridge authority), don't be so eager to
19456 fall back to asking the bridge authority.
19457 - If we're using bridges or have strictentrynodes set, and our
19458 chosen exit is in the same family as all our bridges/entry guards,
19459 then be flexible about families.
19462 - When we negotiate a v2 link-layer connection (not yet implemented),
19463 accept RELAY_EARLY cells and turn them into RELAY cells if we've
19464 negotiated a v1 connection for their next step. Initial code for
19468 Changes in version 0.2.0.11-alpha - 2007-11-12
19469 This eleventh development snapshot fixes some build problems with
19470 the previous snapshot. It also includes a more secure-by-default exit
19471 policy for relays, fixes an enormous memory leak for exit relays, and
19472 fixes another bug where servers were falling out of the directory list.
19475 - Exit policies now reject connections that are addressed to a
19476 relay's public (external) IP address too, unless
19477 ExitPolicyRejectPrivate is turned off. We do this because too
19478 many relays are running nearby to services that trust them based
19479 on network address. Bugfix on 0.1.2.x.
19482 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
19483 on every successful resolve. Reported by Mike Perry; bugfix
19485 - On authorities, never downgrade to old router descriptors simply
19486 because they're listed in the consensus. This created a catch-22
19487 where we wouldn't list a new descriptor because there was an
19488 old one in the consensus, and we couldn't get the new one in the
19489 consensus because we wouldn't list it. Possible fix for bug 548.
19490 Also, this might cause bug 543 to appear on authorities; if so,
19491 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
19493 o Packaging fixes on 0.2.0.10-alpha:
19494 - We were including instructions about what to do with the
19495 src/config/fallback-consensus file, but we weren't actually
19496 including it in the tarball. Disable all of that for now.
19499 - Allow people to say PreferTunnelledDirConns rather than
19500 PreferTunneledDirConns, for those alternate-spellers out there.
19503 - Don't reevaluate all the information from our consensus document
19504 just because we've downloaded a v2 networkstatus that we intend
19505 to cache. Fixes bug 545; bugfix on 0.2.0.x.
19508 Changes in version 0.2.0.10-alpha - 2007-11-10
19509 This tenth development snapshot adds a third v3 directory authority
19510 run by Mike Perry, adds most of Karsten Loesing's new hidden service
19511 descriptor format, fixes a bad crash bug and new bridge bugs introduced
19512 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
19513 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
19514 addresses many more minor issues.
19516 o New directory authorities:
19517 - Set up ides (run by Mike Perry) as the third v3 directory authority.
19520 - Allow tunnelled directory connections to ask for an encrypted
19521 "begin_dir" connection or an anonymized "uses a full Tor circuit"
19522 connection independently. Now we can make anonymized begin_dir
19523 connections for (e.g.) more secure hidden service posting and
19525 - More progress on proposal 114: code from Karsten Loesing to
19526 implement new hidden service descriptor format.
19527 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
19528 accommodate the growing number of servers that use the default
19529 and are reaching it.
19530 - Directory authorities use a new formula for selecting which nodes
19531 to advertise as Guards: they must be in the top 7/8 in terms of
19532 how long we have known about them, and above the median of those
19533 nodes in terms of weighted fractional uptime.
19534 - Make "not enough dir info yet" warnings describe *why* Tor feels
19535 it doesn't have enough directory info yet.
19538 - Stop servers from crashing if they set a Family option (or
19539 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
19541 - Make bridge users work again -- the move to v3 directories in
19542 0.2.0.9-alpha had introduced a number of bugs that made bridges
19543 no longer work for clients.
19544 - When the clock jumps forward a lot, do not allow the bandwidth
19545 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
19547 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
19548 - When the consensus lists a router descriptor that we previously were
19549 mirroring, but that we considered non-canonical, reload the
19550 descriptor as canonical. This fixes bug 543 where Tor servers
19551 would start complaining after a few days that they don't have
19552 enough directory information to build a circuit.
19553 - Consider replacing the current consensus when certificates arrive
19554 that make the pending consensus valid. Previously, we were only
19555 considering replacement when the new certs _didn't_ help.
19556 - Fix an assert error on startup if we didn't already have the
19557 consensus and certs cached in our datadirectory: we were caching
19558 the consensus in consensus_waiting_for_certs but then free'ing it
19560 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
19561 Request) if we need more v3 certs but we've already got pending
19562 requests for all of them.
19563 - Correctly back off from failing certificate downloads. Fixes
19565 - Authorities don't vote on the Running flag if they have been running
19566 for less than 30 minutes themselves. Fixes bug 547, where a newly
19567 started authority would vote that everyone was down.
19569 o New requirements:
19570 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
19571 it, it had no AES, and it hasn't seen any security patches since
19575 - Clients now hold circuitless TLS connections open for 1.5 times
19576 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
19577 rebuild a new circuit over them within that timeframe. Previously,
19578 they held them open only for KeepalivePeriod (5 minutes).
19579 - Use "If-Modified-Since" to avoid retrieving consensus
19580 networkstatuses that we already have.
19581 - When we have no consensus, check FallbackNetworkstatusFile (defaults
19582 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
19583 we start knowing some directory caches.
19584 - When we receive a consensus from the future, warn about skew.
19585 - Improve skew reporting: try to give the user a better log message
19586 about how skewed they are, and how much this matters.
19587 - When we have a certificate for an authority, believe that
19588 certificate's claims about the authority's IP address.
19589 - New --quiet command-line option to suppress the default console log.
19590 Good in combination with --hash-password.
19591 - Authorities send back an X-Descriptor-Not-New header in response to
19592 an accepted-but-discarded descriptor upload. Partially implements
19594 - Make the log message for "tls error. breaking." more useful.
19595 - Better log messages about certificate downloads, to attempt to
19596 track down the second incarnation of bug 546.
19598 o Minor features (bridges):
19599 - If bridge users set UpdateBridgesFromAuthority, but the digest
19600 they ask for is a 404 from the bridge authority, they now fall
19601 back to trying the bridge directly.
19602 - Bridges now use begin_dir to publish their server descriptor to
19603 the bridge authority, even when they haven't set TunnelDirConns.
19605 o Minor features (controller):
19606 - When reporting clock skew, and we know that the clock is _at least
19607 as skewed_ as some value, but we don't know the actual value,
19608 report the value as a "minimum skew."
19611 - Update linux-tor-prio.sh script to allow QoS based on the uid of
19612 the Tor process. Patch from Marco Bonetti with tweaks from Mike
19616 - Refuse to start if both ORPort and UseBridges are set. Bugfix
19617 on 0.2.0.x, suggested by Matt Edman.
19618 - Don't stop fetching descriptors when FetchUselessDescriptors is
19619 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
19620 reported by tup and ioerror.
19621 - Better log message on vote from unknown authority.
19622 - Don't log "Launching 0 request for 0 router" message.
19624 o Minor bugfixes (memory leaks):
19625 - Stop leaking memory every time we parse a v3 certificate. Bugfix
19627 - Stop leaking memory every time we load a v3 certificate. Bugfix
19628 on 0.2.0.1-alpha. Fixes bug 536.
19629 - Stop leaking a cached networkstatus on exit. Bugfix on
19631 - Stop leaking voter information every time we free a consensus.
19632 Bugfix on 0.2.0.3-alpha.
19633 - Stop leaking signed data every time we check a voter signature.
19634 Bugfix on 0.2.0.3-alpha.
19635 - Stop leaking a signature every time we fail to parse a consensus or
19636 a vote. Bugfix on 0.2.0.3-alpha.
19637 - Stop leaking v2_download_status_map on shutdown. Bugfix on
19639 - Stop leaking conn->nickname every time we make a connection to a
19640 Tor relay without knowing its expected identity digest (e.g. when
19641 using bridges). Bugfix on 0.2.0.3-alpha.
19643 - Minor bugfixes (portability):
19644 - Run correctly on platforms where rlim_t is larger than unsigned
19645 long, and/or where the real limit for number of open files is
19646 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
19647 particular, these may be needed for OS X 10.5.
19650 Changes in version 0.1.2.18 - 2007-10-28
19651 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
19652 hidden service introduction that were causing huge delays, and a big
19653 bug that was causing some servers to disappear from the network status
19654 lists for a few hours each day.
19656 o Major bugfixes (crashes):
19657 - If a connection is shut down abruptly because of something that
19658 happened inside connection_flushed_some(), do not call
19659 connection_finished_flushing(). Should fix bug 451:
19660 "connection_stop_writing: Assertion conn->write_event failed"
19661 Bugfix on 0.1.2.7-alpha.
19662 - Fix possible segfaults in functions called from
19663 rend_process_relay_cell().
19665 o Major bugfixes (hidden services):
19666 - Hidden services were choosing introduction points uniquely by
19667 hexdigest, but when constructing the hidden service descriptor
19668 they merely wrote the (potentially ambiguous) nickname.
19669 - Clients now use the v2 intro format for hidden service
19670 connections: they specify their chosen rendezvous point by identity
19671 digest rather than by (potentially ambiguous) nickname. These
19672 changes could speed up hidden service connections dramatically.
19674 o Major bugfixes (other):
19675 - Stop publishing a new server descriptor just because we get a
19676 HUP signal. This led (in a roundabout way) to some servers getting
19677 dropped from the networkstatus lists for a few hours each day.
19678 - When looking for a circuit to cannibalize, consider family as well
19679 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
19680 circuit cannibalization).
19681 - When a router wasn't listed in a new networkstatus, we were leaving
19682 the flags for that router alone -- meaning it remained Named,
19683 Running, etc -- even though absence from the networkstatus means
19684 that it shouldn't be considered to exist at all anymore. Now we
19685 clear all the flags for routers that fall out of the networkstatus
19686 consensus. Fixes bug 529.
19689 - Don't try to access (or alter) the state file when running
19690 --list-fingerprint or --verify-config or --hash-password. Resolves
19692 - When generating information telling us how to extend to a given
19693 router, do not try to include the nickname if it is
19694 absent. Resolves bug 467.
19695 - Fix a user-triggerable segfault in expand_filename(). (There isn't
19696 a way to trigger this remotely.)
19697 - When sending a status event to the controller telling it that an
19698 OR address is reachable, set the port correctly. (Previously we
19699 were reporting the dir port.)
19700 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19701 command. Bugfix on 0.1.2.17.
19702 - When loading bandwidth history, do not believe any information in
19703 the future. Fixes bug 434.
19704 - When loading entry guard information, do not believe any information
19706 - When we have our clock set far in the future and generate an
19707 onion key, then re-set our clock to be correct, we should not stop
19708 the onion key from getting rotated.
19709 - On some platforms, accept() can return a broken address. Detect
19710 this more quietly, and deal accordingly. Fixes bug 483.
19711 - It's not actually an error to find a non-pending entry in the DNS
19712 cache when canceling a pending resolve. Don't log unless stuff
19713 is fishy. Resolves bug 463.
19714 - Don't reset trusted dir server list when we set a configuration
19715 option. Patch from Robert Hogan.
19716 - Don't try to create the datadir when running --verify-config or
19717 --hash-password. Resolves bug 540.
19720 Changes in version 0.2.0.9-alpha - 2007-10-24
19721 This ninth development snapshot switches clients to the new v3 directory
19722 system; allows servers to be listed in the network status even when they
19723 have the same nickname as a registered server; and fixes many other
19724 bugs including a big one that was causing some servers to disappear
19725 from the network status lists for a few hours each day.
19727 o Major features (directory system):
19728 - Clients now download v3 consensus networkstatus documents instead
19729 of v2 networkstatus documents. Clients and caches now base their
19730 opinions about routers on these consensus documents. Clients only
19731 download router descriptors listed in the consensus.
19732 - Authorities now list servers who have the same nickname as
19733 a different named server, but list them with a new flag,
19734 "Unnamed". Now we can list servers that happen to pick the same
19735 nickname as a server that registered two years ago and then
19736 disappeared. Partially implements proposal 122.
19737 - If the consensus lists a router as "Unnamed", the name is assigned
19738 to a different router: do not identify the router by that name.
19739 Partially implements proposal 122.
19740 - Authorities can now come to a consensus on which method to use to
19741 compute the consensus. This gives us forward compatibility.
19744 - Stop publishing a new server descriptor just because we HUP or
19745 when we find our DirPort to be reachable but won't actually publish
19746 it. New descriptors without any real changes are dropped by the
19747 authorities, and can screw up our "publish every 18 hours" schedule.
19749 - When a router wasn't listed in a new networkstatus, we were leaving
19750 the flags for that router alone -- meaning it remained Named,
19751 Running, etc -- even though absence from the networkstatus means
19752 that it shouldn't be considered to exist at all anymore. Now we
19753 clear all the flags for routers that fall out of the networkstatus
19754 consensus. Fixes bug 529; bugfix on 0.1.2.x.
19755 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
19756 extrainfo documents and then discard them immediately for not
19757 matching the latest router. Bugfix on 0.2.0.1-alpha.
19759 o Minor features (v3 directory protocol):
19760 - Allow tor-gencert to generate a new certificate without replacing
19762 - Allow certificates to include an address.
19763 - When we change our directory-cache settings, reschedule all voting
19764 and download operations.
19765 - Reattempt certificate downloads immediately on failure, as long as
19766 we haven't failed a threshold number of times yet.
19767 - Delay retrying consensus downloads while we're downloading
19768 certificates to verify the one we just got. Also, count getting a
19769 consensus that we already have (or one that isn't valid) as a failure,
19770 and count failing to get the certificates after 20 minutes as a
19772 - Build circuits and download descriptors even if our consensus is a
19773 little expired. (This feature will go away once authorities are
19776 o Minor features (router descriptor cache):
19777 - If we find a cached-routers file that's been sitting around for more
19778 than 28 days unmodified, then most likely it's a leftover from
19779 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
19781 - When we (as a cache) download a descriptor because it was listed
19782 in a consensus, remember when the consensus was supposed to expire,
19783 and don't expire the descriptor until then.
19785 o Minor features (performance):
19786 - Call routerlist_remove_old_routers() much less often. This should
19787 speed startup, especially on directory caches.
19788 - Don't try to launch new descriptor downloads quite so often when we
19789 already have enough directory information to build circuits.
19790 - Base64 decoding was actually showing up on our profile when parsing
19791 the initial descriptor file; switch to an in-process all-at-once
19792 implementation that's about 3.5x times faster than calling out to
19795 o Minor features (compilation):
19796 - Detect non-ASCII platforms (if any still exist) and refuse to
19797 build there: some of our code assumes that 'A' is 65 and so on.
19799 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
19800 - Make the "next period" votes into "current period" votes immediately
19801 after publishing the consensus; avoid a heisenbug that made them
19802 stick around indefinitely.
19803 - When we discard a vote as a duplicate, do not report this as
19805 - Treat missing v3 keys or certificates as an error when running as a
19806 v3 directory authority.
19807 - When we're configured to be a v3 authority, but we're only listed
19808 as a non-v3 authority in our DirServer line for ourself, correct
19810 - If an authority doesn't have a qualified hostname, just put
19811 its address in the vote. This fixes the problem where we referred to
19812 "moria on moria:9031."
19813 - Distinguish between detached signatures for the wrong period, and
19814 detached signatures for a divergent vote.
19815 - Fix a small memory leak when computing a consensus.
19816 - When there's no concensus, we were forming a vote every 30
19817 minutes, but writing the "valid-after" line in our vote based
19818 on our configured V3AuthVotingInterval: so unless the intervals
19819 matched up, we immediately rejected our own vote because it didn't
19820 start at the voting interval that caused us to construct a vote.
19822 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
19823 - Delete unverified-consensus when the real consensus is set.
19824 - Consider retrying a consensus networkstatus fetch immediately
19825 after one fails: don't wait 60 seconds to notice.
19826 - When fetching a consensus as a cache, wait until a newer consensus
19827 should exist before trying to replace the current one.
19828 - Use a more forgiving schedule for retrying failed consensus
19829 downloads than for other types.
19831 o Minor bugfixes (other directory issues):
19832 - Correct the implementation of "download votes by digest." Bugfix on
19834 - Authorities no longer send back "400 you're unreachable please fix
19835 it" errors to Tor servers that aren't online all the time. We're
19836 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
19838 o Minor bugfixes (controller):
19839 - Don't reset trusted dir server list when we set a configuration
19840 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
19841 - Respond to INT and TERM SIGNAL commands before we execute the
19842 signal, in case the signal shuts us down. We had a patch in
19843 0.1.2.1-alpha that tried to do this by queueing the response on
19844 the connection's buffer before shutting down, but that really
19845 isn't the same thing at all. Bug located by Matt Edman.
19847 o Minor bugfixes (misc):
19848 - Correctly check for bad options to the "PublishServerDescriptor"
19849 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
19850 - Stop leaking memory on failing case of base32_decode, and make
19851 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
19852 - Don't try to download extrainfo documents when we're trying to
19853 fetch enough directory info to build a circuit: having enough
19854 info should get priority. Bugfix on 0.2.0.x.
19855 - Don't complain that "your server has not managed to confirm that its
19856 ports are reachable" if we haven't been able to build any circuits
19857 yet. Bug found by spending four hours without a v3 consensus. Bugfix
19859 - Detect the reason for failing to mmap a descriptor file we just
19860 wrote, and give a more useful log message. Fixes bug 533. Bugfix
19863 o Code simplifications and refactoring:
19864 - Remove support for the old bw_accounting file: we've been storing
19865 bandwidth accounting information in the state file since
19866 0.1.2.5-alpha. This may result in bandwidth accounting errors
19867 if you try to upgrade from 0.1.1.x or earlier, or if you try to
19868 downgrade to 0.1.1.x or earlier.
19869 - New convenience code to locate a file within the DataDirectory.
19870 - Move non-authority functionality out of dirvote.c.
19871 - Refactor the arguments for router_pick_{directory_|trusteddir}server
19872 so that they all take the same named flags.
19875 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
19876 Unix users an easy way to script their Tor process (e.g. by
19877 adjusting bandwidth based on the time of the day).
19880 Changes in version 0.2.0.8-alpha - 2007-10-12
19881 This eighth development snapshot fixes a crash bug that's been bothering
19882 us since February 2007, lets bridge authorities store a list of bridge
19883 descriptors they've seen, gets v3 directory voting closer to working,
19884 starts caching v3 directory consensus documents on directory mirrors,
19885 and fixes a variety of smaller issues including some minor memory leaks.
19887 o Major features (router descriptor cache):
19888 - Store routers in a file called cached-descriptors instead of in
19889 cached-routers. Initialize cached-descriptors from cached-routers
19890 if the old format is around. The new format allows us to store
19891 annotations along with descriptors.
19892 - Use annotations to record the time we received each descriptor, its
19893 source, and its purpose.
19894 - Disable the SETROUTERPURPOSE controller command: it is now
19896 - Controllers should now specify cache=no or cache=yes when using
19897 the +POSTDESCRIPTOR command.
19898 - Bridge authorities now write bridge descriptors to disk, meaning
19899 we can export them to other programs and begin distributing them
19902 o Major features (directory authorities):
19903 - When a v3 authority is missing votes or signatures, it now tries
19905 - Directory authorities track weighted fractional uptime as well as
19906 weighted mean-time-between failures. WFU is suitable for deciding
19907 whether a node is "usually up", while MTBF is suitable for deciding
19908 whether a node is "likely to stay up." We need both, because
19909 "usually up" is a good requirement for guards, while "likely to
19910 stay up" is a good requirement for long-lived connections.
19912 o Major features (v3 directory system):
19913 - Caches now download v3 network status documents as needed,
19914 and download the descriptors listed in them.
19915 - All hosts now attempt to download and keep fresh v3 authority
19916 certificates, and re-attempt after failures.
19917 - More internal-consistency checks for vote parsing.
19919 o Major bugfixes (crashes):
19920 - If a connection is shut down abruptly because of something that
19921 happened inside connection_flushed_some(), do not call
19922 connection_finished_flushing(). Should fix bug 451. Bugfix on
19925 o Major bugfixes (performance):
19926 - Fix really bad O(n^2) performance when parsing a long list of
19927 routers: Instead of searching the entire list for an "extra-info "
19928 string which usually wasn't there, once for every routerinfo
19929 we read, just scan lines forward until we find one we like.
19931 - When we add data to a write buffer in response to the data on that
19932 write buffer getting low because of a flush, do not consider the
19933 newly added data as a candidate for immediate flushing, but rather
19934 make it wait until the next round of writing. Otherwise, we flush
19935 and refill recursively, and a single greedy TLS connection can
19936 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
19938 o Minor features (v3 authority system):
19939 - Add more ways for tools to download the votes that lead to the
19941 - Send a 503 when low on bandwidth and a vote, consensus, or
19942 certificate is requested.
19943 - If-modified-since is now implemented properly for all kinds of
19944 certificate requests.
19946 o Minor bugfixes (network statuses):
19947 - Tweak the implementation of proposal 109 slightly: allow at most
19948 two Tor servers on the same IP address, except if it's the location
19949 of a directory authority, in which case allow five. Bugfix on
19952 o Minor bugfixes (controller):
19953 - When sending a status event to the controller telling it that an
19954 OR address is reachable, set the port correctly. (Previously we
19955 were reporting the dir port.) Bugfix on 0.1.2.x.
19957 o Minor bugfixes (v3 directory system):
19958 - Fix logic to look up a cert by its signing key digest. Bugfix on
19960 - Only change the reply to a vote to "OK" if it's not already
19961 set. This gets rid of annoying "400 OK" log messages, which may
19962 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
19963 - When we get a valid consensus, recompute the voting schedule.
19964 - Base the valid-after time of a vote on the consensus voting
19965 schedule, not on our preferred schedule.
19966 - Make the return values and messages from signature uploads and
19967 downloads more sensible.
19968 - Fix a memory leak when serving votes and consensus documents, and
19969 another when serving certificates.
19971 o Minor bugfixes (performance):
19972 - Use a slightly simpler string hashing algorithm (copying Python's
19973 instead of Java's) and optimize our digest hashing algorithm to take
19974 advantage of 64-bit platforms and to remove some possibly-costly
19976 - Fix a minor memory leak whenever we parse guards from our state
19977 file. Bugfix on 0.2.0.7-alpha.
19978 - Fix a minor memory leak whenever we write out a file. Bugfix on
19980 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
19981 command. Bugfix on 0.2.0.5-alpha.
19983 o Minor bugfixes (portability):
19984 - On some platforms, accept() can return a broken address. Detect
19985 this more quietly, and deal accordingly. Fixes bug 483.
19986 - Stop calling tor_strlower() on uninitialized memory in some cases.
19987 Bugfix in 0.2.0.7-alpha.
19989 o Minor bugfixes (usability):
19990 - Treat some 403 responses from directory servers as INFO rather than
19991 WARN-severity events.
19992 - It's not actually an error to find a non-pending entry in the DNS
19993 cache when canceling a pending resolve. Don't log unless stuff is
19994 fishy. Resolves bug 463.
19996 o Minor bugfixes (anonymity):
19997 - Never report that we've used more bandwidth than we're willing to
19998 relay: it leaks how much non-relay traffic we're using. Resolves
20000 - When looking for a circuit to cannibalize, consider family as well
20001 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
20002 circuit cannibalization).
20004 o Code simplifications and refactoring:
20005 - Make a bunch of functions static. Remove some dead code.
20006 - Pull out about a third of the really big routerlist.c; put it in a
20007 new module, networkstatus.c.
20008 - Merge the extra fields in local_routerstatus_t back into
20009 routerstatus_t: we used to need one routerstatus_t for each
20010 authority's opinion, plus a local_routerstatus_t for the locally
20011 computed consensus opinion. To save space, we put the locally
20012 modified fields into local_routerstatus_t, and only the common
20013 stuff into routerstatus_t. But once v3 directories are in use,
20014 clients and caches will no longer need to hold authority opinions;
20015 thus, the rationale for keeping the types separate is now gone.
20016 - Make the code used to reschedule and reattempt downloads more
20018 - Turn all 'Are we a directory server/mirror?' logic into a call to
20020 - Remove the code to generate the oldest (v1) directory format.
20021 The code has been disabled since 0.2.0.5-alpha.
20024 Changes in version 0.2.0.7-alpha - 2007-09-21
20025 This seventh development snapshot makes bridges work again, makes bridge
20026 authorities work for the first time, fixes two huge performance flaws
20027 in hidden services, and fixes a variety of minor issues.
20029 o New directory authorities:
20030 - Set up moria1 and tor26 as the first v3 directory authorities. See
20031 doc/spec/dir-spec.txt for details on the new directory design.
20033 o Major bugfixes (crashes):
20034 - Fix possible segfaults in functions called from
20035 rend_process_relay_cell(). Bugfix on 0.1.2.x.
20037 o Major bugfixes (bridges):
20038 - Fix a bug that made servers send a "404 Not found" in response to
20039 attempts to fetch their server descriptor. This caused Tor servers
20040 to take many minutes to establish reachability for their DirPort,
20041 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
20042 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
20043 users configure that and specify a bridge with an identity
20044 fingerprint, now they will lookup the bridge descriptor at the
20045 default bridge authority via a one-hop tunnel, but once circuits
20046 are established they will switch to a three-hop tunnel for later
20047 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
20049 o Major bugfixes (hidden services):
20050 - Hidden services were choosing introduction points uniquely by
20051 hexdigest, but when constructing the hidden service descriptor
20052 they merely wrote the (potentially ambiguous) nickname.
20053 - Clients now use the v2 intro format for hidden service
20054 connections: they specify their chosen rendezvous point by identity
20055 digest rather than by (potentially ambiguous) nickname. Both
20056 are bugfixes on 0.1.2.x, and they could speed up hidden service
20057 connections dramatically. Thanks to Karsten Loesing.
20059 o Minor features (security):
20060 - As a client, do not believe any server that tells us that an
20061 address maps to an internal address space.
20062 - Make it possible to enable HashedControlPassword and
20063 CookieAuthentication at the same time.
20065 o Minor features (guard nodes):
20066 - Tag every guard node in our state file with the version that
20067 we believe added it, or with our own version if we add it. This way,
20068 if a user temporarily runs an old version of Tor and then switches
20069 back to a new one, she doesn't automatically lose her guards.
20071 o Minor features (speed):
20072 - When implementing AES counter mode, update only the portions of the
20073 counter buffer that need to change, and don't keep separate
20074 network-order and host-order counters when they are the same (i.e.,
20075 on big-endian hosts.)
20077 o Minor features (controller):
20078 - Accept LF instead of CRLF on controller, since some software has a
20079 hard time generating real Internet newlines.
20080 - Add GETINFO values for the server status events
20081 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
20084 o Removed features:
20085 - Routers no longer include bandwidth-history lines in their
20086 descriptors; this information is already available in extra-info
20087 documents, and including it in router descriptors took up 60%
20088 (!) of compressed router descriptor downloads. Completes
20089 implementation of proposal 104.
20090 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
20091 and TorControl.py, as they use the old v0 controller protocol,
20092 and are obsoleted by TorFlow anyway.
20093 - Drop support for v1 rendezvous descriptors, since we never used
20094 them anyway, and the code has probably rotted by now. Based on
20095 patch from Karsten Loesing.
20096 - On OSX, stop warning the user that kqueue support in libevent is
20097 "experimental", since it seems to have worked fine for ages.
20100 - When generating information telling us how to extend to a given
20101 router, do not try to include the nickname if it is absent. Fixes
20102 bug 467. Bugfix on 0.2.0.3-alpha.
20103 - Fix a user-triggerable (but not remotely-triggerable) segfault
20104 in expand_filename(). Bugfix on 0.1.2.x.
20105 - Fix a memory leak when freeing incomplete requests from DNSPort.
20106 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
20107 - Don't try to access (or alter) the state file when running
20108 --list-fingerprint or --verify-config or --hash-password. (Resolves
20109 bug 499.) Bugfix on 0.1.2.x.
20110 - Servers used to decline to publish their DirPort if their
20111 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
20112 were below a threshold. Now they only look at BandwidthRate and
20113 RelayBandwidthRate. Bugfix on 0.1.2.x.
20114 - Remove an optimization in the AES counter-mode code that assumed
20115 that the counter never exceeded 2^68. When the counter can be set
20116 arbitrarily as an IV (as it is by Karsten's new hidden services
20117 code), this assumption no longer holds. Bugfix on 0.1.2.x.
20118 - Resume listing "AUTHORITY" flag for authorities in network status.
20119 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
20121 o Code simplifications and refactoring:
20122 - Revamp file-writing logic so we don't need to have the entire
20123 contents of a file in memory at once before we write to disk. Tor,
20125 - Turn "descriptor store" into a full-fledged type.
20126 - Move all NT services code into a separate source file.
20127 - Unify all code that computes medians, percentile elements, etc.
20128 - Get rid of a needless malloc when parsing address policies.
20131 Changes in version 0.1.2.17 - 2007-08-30
20132 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
20133 X bundles. Vidalia 0.0.14 makes authentication required for the
20134 ControlPort in the default configuration, which addresses important
20135 security risks. Everybody who uses Vidalia (or another controller)
20138 In addition, this Tor update fixes major load balancing problems with
20139 path selection, which should speed things up a lot once many people
20142 o Major bugfixes (security):
20143 - We removed support for the old (v0) control protocol. It has been
20144 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
20145 become more of a headache than it's worth.
20147 o Major bugfixes (load balancing):
20148 - When choosing nodes for non-guard positions, weight guards
20149 proportionally less, since they already have enough load. Patch
20151 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
20152 will allow fast Tor servers to get more attention.
20153 - When we're upgrading from an old Tor version, forget our current
20154 guards and pick new ones according to the new weightings. These
20155 three load balancing patches could raise effective network capacity
20156 by a factor of four. Thanks to Mike Perry for measurements.
20158 o Major bugfixes (stream expiration):
20159 - Expire not-yet-successful application streams in all cases if
20160 they've been around longer than SocksTimeout. Right now there are
20161 some cases where the stream will live forever, demanding a new
20162 circuit every 15 seconds. Fixes bug 454; reported by lodger.
20164 o Minor features (controller):
20165 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
20166 is valid before any authentication has been received. It tells
20167 a controller what kind of authentication is expected, and what
20168 protocol is spoken. Implements proposal 119.
20170 o Minor bugfixes (performance):
20171 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
20172 greatly speeding up loading cached-routers from disk on startup.
20173 - Disable sentinel-based debugging for buffer code: we squashed all
20174 the bugs that this was supposed to detect a long time ago, and now
20175 its only effect is to change our buffer sizes from nice powers of
20176 two (which platform mallocs tend to like) to values slightly over
20177 powers of two (which make some platform mallocs sad).
20179 o Minor bugfixes (misc):
20180 - If exit bandwidth ever exceeds one third of total bandwidth, then
20181 use the correct formula to weight exit nodes when choosing paths.
20182 Based on patch from Mike Perry.
20183 - Choose perfectly fairly among routers when choosing by bandwidth and
20184 weighting by fraction of bandwidth provided by exits. Previously, we
20185 would choose with only approximate fairness, and correct ourselves
20186 if we ran off the end of the list.
20187 - If we require CookieAuthentication but we fail to write the
20188 cookie file, we would warn but not exit, and end up in a state
20189 where no controller could authenticate. Now we exit.
20190 - If we require CookieAuthentication, stop generating a new cookie
20191 every time we change any piece of our config.
20192 - Refuse to start with certain directory authority keys, and
20193 encourage people using them to stop.
20194 - Terminate multi-line control events properly. Original patch
20196 - Fix a minor memory leak when we fail to find enough suitable
20197 servers to choose a circuit.
20198 - Stop leaking part of the descriptor when we run into a particularly
20199 unparseable piece of it.
20202 Changes in version 0.2.0.6-alpha - 2007-08-26
20203 This sixth development snapshot features a new Vidalia version in the
20204 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
20205 the ControlPort in the default configuration, which addresses important
20208 In addition, this snapshot fixes major load balancing problems
20209 with path selection, which should speed things up a lot once many
20210 people have upgraded. The directory authorities also use a new
20211 mean-time-between-failure approach to tracking which servers are stable,
20212 rather than just looking at the most recent uptime.
20214 o New directory authorities:
20215 - Set up Tonga as the default bridge directory authority.
20218 - Directory authorities now track servers by weighted
20219 mean-times-between-failures. When we have 4 or more days of data,
20220 use measured MTBF rather than declared uptime to decide whether
20221 to call a router Stable. Implements proposal 108.
20223 o Major bugfixes (load balancing):
20224 - When choosing nodes for non-guard positions, weight guards
20225 proportionally less, since they already have enough load. Patch
20227 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
20228 will allow fast Tor servers to get more attention.
20229 - When we're upgrading from an old Tor version, forget our current
20230 guards and pick new ones according to the new weightings. These
20231 three load balancing patches could raise effective network capacity
20232 by a factor of four. Thanks to Mike Perry for measurements.
20234 o Major bugfixes (descriptor parsing):
20235 - Handle unexpected whitespace better in malformed descriptors. Bug
20236 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
20239 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
20240 GETINFO for Torstat to use until it can switch to using extrainfos.
20241 - Optionally (if built with -DEXPORTMALLINFO) export the output
20242 of mallinfo via http, as tor/mallinfo.txt. Only accessible
20246 - Do not intermix bridge routers with controller-added
20247 routers. (Bugfix on 0.2.0.x)
20248 - Do not fail with an assert when accept() returns an unexpected
20249 address family. Addresses but does not wholly fix bug 483. (Bugfix
20251 - Let directory authorities startup even when they can't generate
20252 a descriptor immediately, e.g. because they don't know their
20254 - Stop putting the authentication cookie in a file called "0"
20255 in your working directory if you don't specify anything for the
20256 new CookieAuthFile option. Reported by Matt Edman.
20257 - Make it possible to read the PROTOCOLINFO response in a way that
20258 conforms to our control-spec. Reported by Matt Edman.
20259 - Fix a minor memory leak when we fail to find enough suitable
20260 servers to choose a circuit. Bugfix on 0.1.2.x.
20261 - Stop leaking part of the descriptor when we run into a particularly
20262 unparseable piece of it. Bugfix on 0.1.2.x.
20263 - Unmap the extrainfo cache file on exit.
20266 Changes in version 0.2.0.5-alpha - 2007-08-19
20267 This fifth development snapshot fixes compilation on Windows again;
20268 fixes an obnoxious client-side bug that slowed things down and put
20269 extra load on the network; gets us closer to using the v3 directory
20270 voting scheme; makes it easier for Tor controllers to use cookie-based
20271 authentication; and fixes a variety of other bugs.
20273 o Removed features:
20274 - Version 1 directories are no longer generated in full. Instead,
20275 authorities generate and serve "stub" v1 directories that list
20276 no servers. This will stop Tor versions 0.1.0.x and earlier from
20277 working, but (for security reasons) nobody should be running those
20280 o Major bugfixes (compilation, 0.2.0.x):
20281 - Try to fix Win32 compilation again: improve checking for IPv6 types.
20282 - Try to fix MSVC compilation: build correctly on platforms that do
20283 not define s6_addr16 or s6_addr32.
20284 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
20287 o Major bugfixes (stream expiration):
20288 - Expire not-yet-successful application streams in all cases if
20289 they've been around longer than SocksTimeout. Right now there are
20290 some cases where the stream will live forever, demanding a new
20291 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
20292 reported by lodger.
20294 o Minor features (directory servers):
20295 - When somebody requests a list of statuses or servers, and we have
20296 none of those, return a 404 rather than an empty 200.
20298 o Minor features (directory voting):
20299 - Store v3 consensus status consensuses on disk, and reload them
20302 o Minor features (security):
20303 - Warn about unsafe ControlPort configurations.
20304 - Refuse to start with certain directory authority keys, and
20305 encourage people using them to stop.
20307 o Minor features (controller):
20308 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
20309 is valid before any authentication has been received. It tells
20310 a controller what kind of authentication is expected, and what
20311 protocol is spoken. Implements proposal 119.
20312 - New config option CookieAuthFile to choose a new location for the
20313 cookie authentication file, and config option
20314 CookieAuthFileGroupReadable to make it group-readable.
20316 o Minor features (unit testing):
20317 - Add command-line arguments to unit-test executable so that we can
20318 invoke any chosen test from the command line rather than having
20319 to run the whole test suite at once; and so that we can turn on
20320 logging for the unit tests.
20322 o Minor bugfixes (on 0.1.2.x):
20323 - If we require CookieAuthentication but we fail to write the
20324 cookie file, we would warn but not exit, and end up in a state
20325 where no controller could authenticate. Now we exit.
20326 - If we require CookieAuthentication, stop generating a new cookie
20327 every time we change any piece of our config.
20328 - When loading bandwidth history, do not believe any information in
20329 the future. Fixes bug 434.
20330 - When loading entry guard information, do not believe any information
20332 - When we have our clock set far in the future and generate an
20333 onion key, then re-set our clock to be correct, we should not stop
20334 the onion key from getting rotated.
20335 - Clean up torrc sample config file.
20336 - Do not automatically run configure from autogen.sh. This
20337 non-standard behavior tended to annoy people who have built other
20340 o Minor bugfixes (on 0.2.0.x):
20341 - Fix a bug with AutomapHostsOnResolve that would always cause
20342 the second request to fail. Bug reported by Kate. Bugfix on
20344 - Fix a bug in ADDRMAP controller replies that would sometimes
20345 try to print a NULL. Patch from tup.
20346 - Read v3 directory authority keys from the right location.
20347 - Numerous bugfixes to directory voting code.
20350 Changes in version 0.1.2.16 - 2007-08-01
20351 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
20352 remote attacker in certain situations to rewrite the user's torrc
20353 configuration file. This can completely compromise anonymity of users
20354 in most configurations, including those running the Vidalia bundles,
20355 TorK, etc. Or worse.
20357 o Major security fixes:
20358 - Close immediately after missing authentication on control port;
20359 do not allow multiple authentication attempts.
20362 Changes in version 0.2.0.4-alpha - 2007-08-01
20363 This fourth development snapshot fixes a critical security vulnerability
20364 for most users, specifically those running Vidalia, TorK, etc. Everybody
20365 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
20367 o Major security fixes:
20368 - Close immediately after missing authentication on control port;
20369 do not allow multiple authentication attempts.
20371 o Major bugfixes (compilation):
20372 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
20375 o Minor features (performance):
20376 - Be even more aggressive about releasing RAM from small
20377 empty buffers. Thanks to our free-list code, this shouldn't be too
20378 performance-intensive.
20379 - Disable sentinel-based debugging for buffer code: we squashed all
20380 the bugs that this was supposed to detect a long time ago, and
20381 now its only effect is to change our buffer sizes from nice
20382 powers of two (which platform mallocs tend to like) to values
20383 slightly over powers of two (which make some platform mallocs sad).
20384 - Log malloc statistics from mallinfo() on platforms where it
20388 Changes in version 0.2.0.3-alpha - 2007-07-29
20389 This third development snapshot introduces new experimental
20390 blocking-resistance features and a preliminary version of the v3
20391 directory voting design, and includes many other smaller features
20395 - The first pieces of our "bridge" design for blocking-resistance
20396 are implemented. People can run bridge directory authorities;
20397 people can run bridges; and people can configure their Tor clients
20398 with a set of bridges to use as the first hop into the Tor network.
20399 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
20401 - Create listener connections before we setuid to the configured
20402 User and Group. Now non-Windows users can choose port values
20403 under 1024, start Tor as root, and have Tor bind those ports
20404 before it changes to another UID. (Windows users could already
20406 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
20407 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
20408 on "vserver" accounts. (Patch from coderman.)
20409 - Be even more aggressive about separating local traffic from relayed
20410 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
20412 o Major features (experimental):
20413 - First cut of code for "v3 dir voting": directory authorities will
20414 vote on a common network status document rather than each publishing
20415 their own opinion. This code needs more testing and more corner-case
20416 handling before it's ready for use.
20419 - Directory authorities now call routers Fast if their bandwidth is
20420 at least 100KB/s, and consider their bandwidth adequate to be a
20421 Guard if it is at least 250KB/s, no matter the medians. This fix
20422 complements proposal 107. [Bugfix on 0.1.2.x]
20423 - Directory authorities now never mark more than 3 servers per IP as
20424 Valid and Running. (Implements proposal 109, by Kevin Bauer and
20426 - Minor change to organizationName and commonName generation
20427 procedures in TLS certificates during Tor handshakes, to invalidate
20428 some earlier censorware approaches. This is not a long-term
20429 solution, but applying it will give us a bit of time to look into
20430 the epidemiology of countermeasures as they spread.
20432 o Major bugfixes (directory):
20433 - Rewrite directory tokenization code to never run off the end of
20434 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
20436 o Minor features (controller):
20437 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
20438 match requests to applications. (Patch from Robert Hogan.)
20439 - Report address and port correctly on connections to DNSPort. (Patch
20440 from Robert Hogan.)
20441 - Add a RESOLVE command to launch hostname lookups. (Original patch
20442 from Robert Hogan.)
20443 - Add GETINFO status/enough-dir-info to let controllers tell whether
20444 Tor has downloaded sufficient directory information. (Patch
20446 - You can now use the ControlSocket option to tell Tor to listen for
20447 controller connections on Unix domain sockets on systems that
20448 support them. (Patch from Peter Palfrader.)
20449 - STREAM NEW events are generated for DNSPort requests and for
20450 tunneled directory connections. (Patch from Robert Hogan.)
20451 - New "GETINFO address-mappings/*" command to get address mappings
20452 with expiry information. "addr-mappings/*" is now deprecated.
20455 o Minor features (misc):
20456 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
20458 - The tor-gencert tool for v3 directory authorities now creates all
20459 files as readable to the file creator only, and write-protects
20460 the authority identity key.
20461 - When dumping memory usage, list bytes used in buffer memory
20463 - When running with dmalloc, dump more stats on hup and on exit.
20464 - Directory authorities now fail quickly and (relatively) harmlessly
20465 if they generate a network status document that is somehow
20468 o Traffic load balancing improvements:
20469 - If exit bandwidth ever exceeds one third of total bandwidth, then
20470 use the correct formula to weight exit nodes when choosing paths.
20471 (Based on patch from Mike Perry.)
20472 - Choose perfectly fairly among routers when choosing by bandwidth and
20473 weighting by fraction of bandwidth provided by exits. Previously, we
20474 would choose with only approximate fairness, and correct ourselves
20475 if we ran off the end of the list. [Bugfix on 0.1.2.x]
20477 o Performance improvements:
20478 - Be more aggressive with freeing buffer RAM or putting it on the
20480 - Use Critical Sections rather than Mutexes for synchronizing threads
20481 on win32; Mutexes are heavier-weight, and designed for synchronizing
20484 o Deprecated and removed features:
20485 - RedirectExits is now deprecated.
20486 - Stop allowing address masks that do not correspond to bit prefixes.
20487 We have warned about these for a really long time; now it's time
20488 to reject them. (Patch from croup.)
20490 o Minor bugfixes (directory):
20491 - Fix another crash bug related to extra-info caching. (Bug found by
20492 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
20493 - Directories no longer return a "304 not modified" when they don't
20494 have the networkstatus the client asked for. Also fix a memory
20495 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
20496 - We had accidentally labelled 0.1.2.x directory servers as not
20497 suitable for begin_dir requests, and had labelled no directory
20498 servers as suitable for uploading extra-info documents. [Bugfix
20501 o Minor bugfixes (dns):
20502 - Fix a crash when DNSPort is set more than once. (Patch from Robert
20503 Hogan.) [Bugfix on 0.2.0.2-alpha]
20504 - Add DNSPort connections to the global connection list, so that we
20505 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
20507 - Fix a dangling reference that could lead to a crash when DNSPort is
20508 changed or closed (Patch from Robert Hogan.) [Bugfix on
20511 o Minor bugfixes (controller):
20512 - Provide DNS expiry times in GMT, not in local time. For backward
20513 compatibility, ADDRMAP events only provide GMT expiry in an extended
20514 field. "GETINFO address-mappings" always does the right thing.
20515 - Use CRLF line endings properly in NS events.
20516 - Terminate multi-line control events properly. (Original patch
20517 from tup.) [Bugfix on 0.1.2.x-alpha]
20518 - Do not include spaces in SOURCE_ADDR fields in STREAM
20519 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
20522 Changes in version 0.1.2.15 - 2007-07-17
20523 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
20524 problems, fixes compilation on BSD, and fixes a variety of other
20525 bugs. Everybody should upgrade.
20527 o Major bugfixes (compilation):
20528 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
20530 o Major bugfixes (crashes):
20531 - Try even harder not to dereference the first character after
20532 an mmap(). Reported by lodger.
20533 - Fix a crash bug in directory authorities when we re-number the
20534 routerlist while inserting a new router.
20535 - When the cached-routers file is an even multiple of the page size,
20536 don't run off the end and crash. (Fixes bug 455; based on idea
20538 - Fix eventdns.c behavior on Solaris: It is critical to include
20539 orconfig.h _before_ sys/types.h, so that we can get the expected
20540 definition of _FILE_OFFSET_BITS.
20542 o Major bugfixes (security):
20543 - Fix a possible buffer overrun when using BSD natd support. Bug
20545 - When sending destroy cells from a circuit's origin, don't include
20546 the reason for tearing down the circuit. The spec says we didn't,
20547 and now we actually don't. Reported by lodger.
20548 - Keep streamids from different exits on a circuit separate. This
20549 bug may have allowed other routers on a given circuit to inject
20550 cells into streams. Reported by lodger; fixes bug 446.
20551 - If there's a never-before-connected-to guard node in our list,
20552 never choose any guards past it. This way we don't expand our
20553 guard list unless we need to.
20555 o Minor bugfixes (guard nodes):
20556 - Weight guard selection by bandwidth, so that low-bandwidth nodes
20557 don't get overused as guards.
20559 o Minor bugfixes (directory):
20560 - Correctly count the number of authorities that recommend each
20561 version. Previously, we were under-counting by 1.
20562 - Fix a potential crash bug when we load many server descriptors at
20563 once and some of them make others of them obsolete. Fixes bug 458.
20565 o Minor bugfixes (hidden services):
20566 - Stop tearing down the whole circuit when the user asks for a
20567 connection to a port that the hidden service didn't configure.
20570 o Minor bugfixes (misc):
20571 - On Windows, we were preventing other processes from reading
20572 cached-routers while Tor was running. Reported by janbar.
20573 - Fix a possible (but very unlikely) bug in picking routers by
20574 bandwidth. Add a log message to confirm that it is in fact
20575 unlikely. Patch from lodger.
20576 - Backport a couple of memory leak fixes.
20577 - Backport miscellaneous cosmetic bugfixes.
20580 Changes in version 0.2.0.2-alpha - 2007-06-02
20581 o Major bugfixes on 0.2.0.1-alpha:
20582 - Fix an assertion failure related to servers without extra-info digests.
20583 Resolves bugs 441 and 442.
20585 o Minor features (directory):
20586 - Support "If-Modified-Since" when answering HTTP requests for
20587 directories, running-routers documents, and network-status documents.
20588 (There's no need to support it for router descriptors, since those
20589 are downloaded by descriptor digest.)
20591 o Minor build issues:
20592 - Clear up some MIPSPro compiler warnings.
20593 - When building from a tarball on a machine that happens to have SVK
20594 installed, report the micro-revision as whatever version existed
20595 in the tarball, not as "x".
20598 Changes in version 0.2.0.1-alpha - 2007-06-01
20599 This early development snapshot provides new features for people running
20600 Tor as both a client and a server (check out the new RelayBandwidth
20601 config options); lets Tor run as a DNS proxy; and generally moves us
20602 forward on a lot of fronts.
20604 o Major features, server usability:
20605 - New config options RelayBandwidthRate and RelayBandwidthBurst:
20606 a separate set of token buckets for relayed traffic. Right now
20607 relayed traffic is defined as answers to directory requests, and
20608 OR connections that don't have any local circuits on them.
20610 o Major features, client usability:
20611 - A client-side DNS proxy feature to replace the need for
20612 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
20613 for DNS requests on port 9999, use the Tor network to resolve them
20614 anonymously, and send the reply back like a regular DNS server.
20615 The code still only implements a subset of DNS.
20616 - Make PreferTunneledDirConns and TunnelDirConns work even when
20617 we have no cached directory info. This means Tor clients can now
20618 do all of their connections protected by TLS.
20620 o Major features, performance and efficiency:
20621 - Directory authorities accept and serve "extra info" documents for
20622 routers. These documents contain fields from router descriptors
20623 that aren't usually needed, and that use a lot of excess
20624 bandwidth. Once these fields are removed from router descriptors,
20625 the bandwidth savings should be about 60%. [Partially implements
20627 - Servers upload extra-info documents to any authority that accepts
20628 them. Authorities (and caches that have been configured to download
20629 extra-info documents) download them as needed. [Partially implements
20631 - Change the way that Tor buffers data that it is waiting to write.
20632 Instead of queueing data cells in an enormous ring buffer for each
20633 client->OR or OR->OR connection, we now queue cells on a separate
20634 queue for each circuit. This lets us use less slack memory, and
20635 will eventually let us be smarter about prioritizing different kinds
20637 - Use memory pools to allocate cells with better speed and memory
20638 efficiency, especially on platforms where malloc() is inefficient.
20639 - Stop reading on edge connections when their corresponding circuit
20640 buffers are full; start again as the circuits empty out.
20642 o Major features, other:
20643 - Add an HSAuthorityRecordStats option that hidden service authorities
20644 can use to track statistics of overall hidden service usage without
20645 logging information that would be very useful to an attacker.
20646 - Start work implementing multi-level keys for directory authorities:
20647 Add a standalone tool to generate key certificates. (Proposal 103.)
20650 - Directory authorities now call routers Stable if they have an
20651 uptime of at least 30 days, even if that's not the median uptime
20652 in the network. Implements proposal 107, suggested by Kevin Bauer
20655 o Minor fixes (resource management):
20656 - Count the number of open sockets separately from the number
20657 of active connection_t objects. This will let us avoid underusing
20658 our allocated connection limit.
20659 - We no longer use socket pairs to link an edge connection to an
20660 anonymous directory connection or a DirPort test connection.
20661 Instead, we track the link internally and transfer the data
20662 in-process. This saves two sockets per "linked" connection (at the
20663 client and at the server), and avoids the nasty Windows socketpair()
20665 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
20666 for every single inactive connection_t. Free items from the
20667 4k/16k-buffer free lists when they haven't been used for a while.
20669 o Minor features (build):
20670 - Make autoconf search for libevent, openssl, and zlib consistently.
20671 - Update deprecated macros in configure.in.
20672 - When warning about missing headers, tell the user to let us
20673 know if the compile succeeds anyway, so we can downgrade the
20675 - Include the current subversion revision as part of the version
20676 string: either fetch it directly if we're in an SVN checkout, do
20677 some magic to guess it if we're in an SVK checkout, or use
20678 the last-detected version if we're building from a .tar.gz.
20679 Use this version consistently in log messages.
20681 o Minor features (logging):
20682 - Always prepend "Bug: " to any log message about a bug.
20683 - Put a platform string (e.g. "Linux i686") in the startup log
20684 message, so when people paste just their logs, we know if it's
20685 OpenBSD or Windows or what.
20686 - When logging memory usage, break down memory used in buffers by
20689 o Minor features (directory system):
20690 - New config option V2AuthoritativeDirectory that all directory
20691 authorities should set. This will let future authorities choose
20692 not to serve V2 directory information.
20693 - Directory authorities allow multiple router descriptors and/or extra
20694 info documents to be uploaded in a single go. This will make
20695 implementing proposal 104 simpler.
20697 o Minor features (controller):
20698 - Add a new config option __DisablePredictedCircuits designed for
20699 use by the controller, when we don't want Tor to build any circuits
20701 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
20702 so we can exit from the middle of the circuit.
20703 - Implement "getinfo status/circuit-established".
20704 - Implement "getinfo status/version/..." so a controller can tell
20705 whether the current version is recommended, and whether any versions
20706 are good, and how many authorities agree. (Patch from shibz.)
20708 o Minor features (hidden services):
20709 - Allow multiple HiddenServicePort directives with the same virtual
20710 port; when they occur, the user is sent round-robin to one
20711 of the target ports chosen at random. Partially fixes bug 393 by
20712 adding limited ad-hoc round-robining.
20714 o Minor features (other):
20716 - Add a new AutomapHostsOnResolve option: when it is enabled, any
20717 resolve request for hosts matching a given pattern causes Tor to
20718 generate an internal virtual address mapping for that host. This
20719 allows DNSPort to work sensibly with hidden service users. By
20720 default, .exit and .onion addresses are remapped; the list of
20721 patterns can be reconfigured with AutomapHostsSuffixes.
20722 - Add an "-F" option to tor-resolve to force a resolve for a .onion
20723 address. Thanks to the AutomapHostsOnResolve option, this is no
20724 longer a completely silly thing to do.
20725 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
20726 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
20727 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
20728 minus 1 byte: the actual maximum declared bandwidth.
20730 o Removed features:
20731 - Removed support for the old binary "version 0" controller protocol.
20732 This has been deprecated since 0.1.1, and warnings have been issued
20733 since 0.1.2. When we encounter a v0 control message, we now send
20734 back an error and close the connection.
20735 - Remove the old "dns worker" server DNS code: it hasn't been default
20736 since 0.1.2.2-alpha, and all the servers seem to be using the new
20739 o Minor bugfixes (portability):
20740 - Even though Windows is equally happy with / and \ as path separators,
20741 try to use \ consistently on Windows and / consistently on Unix: it
20742 makes the log messages nicer.
20743 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
20744 - Read resolv.conf files correctly on platforms where read() returns
20745 partial results on small file reads.
20747 o Minor bugfixes (directory):
20748 - Correctly enforce that elements of directory objects do not appear
20749 more often than they are allowed to appear.
20750 - When we are reporting the DirServer line we just parsed, we were
20751 logging the second stanza of the key fingerprint, not the first.
20753 o Minor bugfixes (logging):
20754 - When we hit an EOF on a log (probably because we're shutting down),
20755 don't try to remove the log from the list: just mark it as
20756 unusable. (Bulletproofs against bug 222.)
20758 o Minor bugfixes (other):
20759 - In the exitlist script, only consider the most recently published
20760 server descriptor for each server. Also, when the user requests
20761 a list of servers that _reject_ connections to a given address,
20762 explicitly exclude the IPs that also have servers that accept
20763 connections to that address. (Resolves bug 405.)
20764 - Stop allowing hibernating servers to be "stable" or "fast".
20765 - On Windows, we were preventing other processes from reading
20766 cached-routers while Tor was running. (Reported by janbar)
20767 - Make the NodeFamilies config option work. (Reported by
20768 lodger -- it has never actually worked, even though we added it
20770 - Check return values from pthread_mutex functions.
20771 - Don't save non-general-purpose router descriptors to the disk cache,
20772 because we have no way of remembering what their purpose was when
20774 - Add even more asserts to hunt down bug 417.
20775 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
20776 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
20777 Add a log message to confirm that it is in fact unlikely.
20779 o Minor bugfixes (controller):
20780 - Make 'getinfo fingerprint' return a 551 error if we're not a
20781 server, so we match what the control spec claims we do. Reported
20783 - Fix a typo in an error message when extendcircuit fails that
20784 caused us to not follow the \r\n-based delimiter protocol. Reported
20787 o Code simplifications and refactoring:
20788 - Stop passing around circuit_t and crypt_path_t pointers that are
20789 implicit in other procedure arguments.
20790 - Drop the old code to choke directory connections when the
20791 corresponding OR connections got full: thanks to the cell queue
20792 feature, OR conns don't get full any more.
20793 - Make dns_resolve() handle attaching connections to circuits
20794 properly, so the caller doesn't have to.
20795 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
20796 - Keep the connection array as a dynamic smartlist_t, rather than as
20797 a fixed-sized array. This is important, as the number of connections
20798 is becoming increasingly decoupled from the number of sockets.
20801 Changes in version 0.1.2.14 - 2007-05-25
20802 Tor 0.1.2.14 changes the addresses of two directory authorities (this
20803 change especially affects those who serve or use hidden services),
20804 and fixes several other crash- and security-related bugs.
20806 o Directory authority changes:
20807 - Two directory authorities (moria1 and moria2) just moved to new
20808 IP addresses. This change will particularly affect those who serve
20809 or use hidden services.
20811 o Major bugfixes (crashes):
20812 - If a directory server runs out of space in the connection table
20813 as it's processing a begin_dir request, it will free the exit stream
20814 but leave it attached to the circuit, leading to unpredictable
20815 behavior. (Reported by seeess, fixes bug 425.)
20816 - Fix a bug in dirserv_remove_invalid() that would cause authorities
20817 to corrupt memory under some really unlikely scenarios.
20818 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
20819 - Avoid segfaults when reading from mmaped descriptor file. (Reported
20822 o Major bugfixes (security):
20823 - When choosing an entry guard for a circuit, avoid using guards
20824 that are in the same family as the chosen exit -- not just guards
20825 that are exactly the chosen exit. (Reported by lodger.)
20827 o Major bugfixes (resource management):
20828 - If a directory authority is down, skip it when deciding where to get
20829 networkstatus objects or descriptors. Otherwise we keep asking
20830 every 10 seconds forever. Fixes bug 384.
20831 - Count it as a failure if we fetch a valid network-status but we
20832 don't want to keep it. Otherwise we'll keep fetching it and keep
20833 not wanting to keep it. Fixes part of bug 422.
20834 - If all of our dirservers have given us bad or no networkstatuses
20835 lately, then stop hammering them once per minute even when we
20836 think they're failed. Fixes another part of bug 422.
20839 - Actually set the purpose correctly for descriptors inserted with
20840 purpose=controller.
20841 - When we have k non-v2 authorities in our DirServer config,
20842 we ignored the last k authorities in the list when updating our
20844 - Correctly back-off from requesting router descriptors that we are
20845 having a hard time downloading.
20846 - Read resolv.conf files correctly on platforms where read() returns
20847 partial results on small file reads.
20848 - Don't rebuild the entire router store every time we get 32K of
20849 routers: rebuild it when the journal gets very large, or when
20850 the gaps in the store get very large.
20853 - When routers publish SVN revisions in their router descriptors,
20854 authorities now include those versions correctly in networkstatus
20856 - Warn when using a version of libevent before 1.3b to run a server on
20857 OSX or BSD: these versions interact badly with userspace threads.
20860 Changes in version 0.1.2.13 - 2007-04-24
20861 This release features some major anonymity fixes, such as safer path
20862 selection; better client performance; faster bootstrapping, better
20863 address detection, and better DNS support for servers; write limiting as
20864 well as read limiting to make servers easier to run; and a huge pile of
20865 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
20867 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
20868 of the Freenode IRC network, remembering his patience and vision for
20869 free speech on the Internet.
20872 - Fix a memory leak when we ask for "all" networkstatuses and we
20873 get one we don't recognize.
20874 - Add more asserts to hunt down bug 417.
20875 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
20878 Changes in version 0.1.2.12-rc - 2007-03-16
20880 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
20881 directory information requested inside Tor connections (i.e. via
20882 begin_dir cells). It only triggered when the same connection was
20883 serving other data at the same time. Reported by seeess.
20886 - When creating a circuit via the controller, send a 'launched'
20887 event when we're done, so we follow the spec better.
20890 Changes in version 0.1.2.11-rc - 2007-03-15
20891 o Minor bugfixes (controller), reported by daejees:
20892 - Correct the control spec to match how the code actually responds
20893 to 'getinfo addr-mappings/*'.
20894 - The control spec described a GUARDS event, but the code
20895 implemented a GUARD event. Standardize on GUARD, but let people
20896 ask for GUARDS too.
20899 Changes in version 0.1.2.10-rc - 2007-03-07
20900 o Major bugfixes (Windows):
20901 - Do not load the NT services library functions (which may not exist)
20902 just to detect if we're a service trying to shut down. Now we run
20903 on Win98 and friends again.
20905 o Minor bugfixes (other):
20906 - Clarify a couple of log messages.
20907 - Fix a misleading socks5 error number.
20910 Changes in version 0.1.2.9-rc - 2007-03-02
20911 o Major bugfixes (Windows):
20912 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
20913 of the usual GCC "%llu". This prevents a bug when saving 64-bit
20914 int configuration values: the high-order 32 bits would get
20915 truncated. In particular, we were being bitten by the default
20916 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
20917 and maybe also bug 397.)
20919 o Minor bugfixes (performance):
20920 - Use OpenSSL's AES implementation on platforms where it's faster.
20921 This could save us as much as 10% CPU usage.
20923 o Minor bugfixes (server):
20924 - Do not rotate onion key immediately after setting it for the first
20927 o Minor bugfixes (directory authorities):
20928 - Stop calling servers that have been hibernating for a long time
20929 "stable". Also, stop letting hibernating or obsolete servers affect
20930 uptime and bandwidth cutoffs.
20931 - Stop listing hibernating servers in the v1 directory.
20933 o Minor bugfixes (hidden services):
20934 - Upload hidden service descriptors slightly less often, to reduce
20935 load on authorities.
20937 o Minor bugfixes (other):
20938 - Fix an assert that could trigger if a controller quickly set then
20939 cleared EntryNodes. Bug found by Udo van den Heuvel.
20940 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
20942 - Fix a potential race condition in the rpm installer. Found by
20944 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
20945 of 2 as indicating that the server is completely bad; it sometimes
20946 means that the server is just bad for the request in question. (may fix
20947 the last of bug 326.)
20948 - Disable encrypted directory connections when we don't have a server
20949 descriptor for the destination. We'll get this working again in
20953 Changes in version 0.1.2.8-beta - 2007-02-26
20954 o Major bugfixes (crashes):
20955 - Stop crashing when the controller asks us to resetconf more than
20956 one config option at once. (Vidalia 0.0.11 does this.)
20957 - Fix a crash that happened on Win98 when we're given command-line
20958 arguments: don't try to load NT service functions from advapi32.dll
20959 except when we need them. (Bug introduced in 0.1.2.7-alpha;
20961 - Fix a longstanding obscure crash bug that could occur when
20962 we run out of DNS worker processes. (Resolves bug 390.)
20964 o Major bugfixes (hidden services):
20965 - Correctly detect whether hidden service descriptor downloads are
20966 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
20968 o Major bugfixes (accounting):
20969 - When we start during an accounting interval before it's time to wake
20970 up, remember to wake up at the correct time. (May fix bug 342.)
20972 o Minor bugfixes (controller):
20973 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
20974 clear the corresponding on_circuit variable, and remember later
20975 that we don't need to send a redundant CLOSED event. Resolves part
20977 - Report events where a resolve succeeded or where we got a socks
20978 protocol error correctly, rather than calling both of them
20980 - Change reported stream target addresses to IP consistently when
20981 we finally get the IP from an exit node.
20982 - Send log messages to the controller even if they happen to be very
20985 o Minor bugfixes (other):
20986 - Display correct results when reporting which versions are
20987 recommended, and how recommended they are. (Resolves bug 383.)
20988 - Improve our estimates for directory bandwidth to be less random:
20989 guess that an unrecognized directory will have the average bandwidth
20990 from all known directories, not that it will have the average
20991 bandwidth from those directories earlier than it on the list.
20992 - If we start a server with ClientOnly 1, then set ClientOnly to 0
20993 and hup, stop triggering an assert based on an empty onion_key.
20994 - On platforms with no working mmap() equivalent, don't warn the
20995 user when cached-routers doesn't exist.
20996 - Warn the user when mmap() [or its equivalent] fails for some reason
20997 other than file-not-found.
20998 - Don't warn the user when cached-routers.new doesn't exist: that's
20999 perfectly fine when starting up for the first time.
21000 - When EntryNodes are configured, rebuild the guard list to contain,
21001 in order: the EntryNodes that were guards before; the rest of the
21002 EntryNodes; the nodes that were guards before.
21003 - Mask out all signals in sub-threads; only the libevent signal
21004 handler should be processing them. This should prevent some crashes
21005 on some machines using pthreads. (Patch from coderman.)
21006 - Fix switched arguments on memset in the implementation of
21007 tor_munmap() for systems with no mmap() call.
21008 - When Tor receives a router descriptor that it asked for, but
21009 no longer wants (because it has received fresh networkstatuses
21010 in the meantime), do not warn the user. Cache the descriptor if
21011 we're a cache; drop it if we aren't.
21012 - Make earlier entry guards _really_ get retried when the network
21014 - On a malformed DNS reply, always give an error to the corresponding
21016 - Build with recent libevents on platforms that do not define the
21017 nonstandard types "u_int8_t" and friends.
21019 o Minor features (controller):
21020 - Warn the user when an application uses the obsolete binary v0
21021 control protocol. We're planning to remove support for it during
21022 the next development series, so it's good to give people some
21024 - Add STREAM_BW events to report per-entry-stream bandwidth
21025 use. (Patch from Robert Hogan.)
21026 - Rate-limit SIGNEWNYM signals in response to controllers that
21027 impolitely generate them for every single stream. (Patch from
21028 mwenge; closes bug 394.)
21029 - Make REMAP stream events have a SOURCE (cache or exit), and
21030 make them generated in every case where we get a successful
21031 connected or resolved cell.
21033 o Minor bugfixes (performance):
21034 - Call router_have_min_dir_info half as often. (This is showing up in
21035 some profiles, but not others.)
21036 - When using GCC, make log_debug never get called at all, and its
21037 arguments never get evaluated, when no debug logs are configured.
21038 (This is showing up in some profiles, but not others.)
21041 - Remove some never-implemented options. Mark PathlenCoinWeight as
21043 - Implement proposal 106: Stop requiring clients to have well-formed
21044 certificates; stop checking nicknames in certificates. (Clients
21045 have certificates so that they can look like Tor servers, but in
21046 the future we might want to allow them to look like regular TLS
21047 clients instead. Nicknames in certificates serve no purpose other
21048 than making our protocol easier to recognize on the wire.)
21049 - Revise messages on handshake failure again to be even more clear about
21050 which are incoming connections and which are outgoing.
21051 - Discard any v1 directory info that's over 1 month old (for
21052 directories) or over 1 week old (for running-routers lists).
21053 - Do not warn when individual nodes in the configuration's EntryNodes,
21054 ExitNodes, etc are down: warn only when all possible nodes
21055 are down. (Fixes bug 348.)
21056 - Always remove expired routers and networkstatus docs before checking
21057 whether we have enough information to build circuits. (Fixes
21059 - Put a lower-bound on MaxAdvertisedBandwidth.
21062 Changes in version 0.1.2.7-alpha - 2007-02-06
21063 o Major bugfixes (rate limiting):
21064 - Servers decline directory requests much more aggressively when
21065 they're low on bandwidth. Otherwise they end up queueing more and
21066 more directory responses, which can't be good for latency.
21067 - But never refuse directory requests from local addresses.
21068 - Fix a memory leak when sending a 503 response for a networkstatus
21070 - Be willing to read or write on local connections (e.g. controller
21071 connections) even when the global rate limiting buckets are empty.
21072 - If our system clock jumps back in time, don't publish a negative
21073 uptime in the descriptor. Also, don't let the global rate limiting
21074 buckets go absurdly negative.
21075 - Flush local controller connection buffers periodically as we're
21076 writing to them, so we avoid queueing 4+ megabytes of data before
21079 o Major bugfixes (NT services):
21080 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
21081 command-line flag so that admins can override the default by saying
21082 "tor --service install --user "SomeUser"". This will not affect
21083 existing installed services. Also, warn the user that the service
21084 will look for its configuration file in the service user's
21085 %appdata% directory. (We can't do the 'hardwire the user's appdata
21086 directory' trick any more, since we may not have read access to that
21089 o Major bugfixes (other):
21090 - Previously, we would cache up to 16 old networkstatus documents
21091 indefinitely, if they came from nontrusted authorities. Now we
21092 discard them if they are more than 10 days old.
21093 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
21095 - Detect and reject malformed DNS responses containing circular
21097 - If exits are rare enough that we're not marking exits as guards,
21098 ignore exit bandwidth when we're deciding the required bandwidth
21100 - When we're handling a directory connection tunneled over Tor,
21101 don't fill up internal memory buffers with all the data we want
21102 to tunnel; instead, only add it if the OR connection that will
21103 eventually receive it has some room for it. (This can lead to
21104 slowdowns in tunneled dir connections; a better solution will have
21105 to wait for 0.2.0.)
21107 o Minor bugfixes (dns):
21108 - Add some defensive programming to eventdns.c in an attempt to catch
21109 possible memory-stomping bugs.
21110 - Detect and reject DNS replies containing IPv4 or IPv6 records with
21111 an incorrect number of bytes. (Previously, we would ignore the
21113 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
21114 in the correct order, and doesn't crash.
21115 - Free memory held in recently-completed DNS lookup attempts on exit.
21116 This was not a memory leak, but may have been hiding memory leaks.
21117 - Handle TTL values correctly on reverse DNS lookups.
21118 - Treat failure to parse resolv.conf as an error.
21120 o Minor bugfixes (other):
21121 - Fix crash with "tor --list-fingerprint" (reported by seeess).
21122 - When computing clock skew from directory HTTP headers, consider what
21123 time it was when we finished asking for the directory, not what
21125 - Expire socks connections if they spend too long waiting for the
21126 handshake to finish. Previously we would let them sit around for
21127 days, if the connecting application didn't close them either.
21128 - And if the socks handshake hasn't started, don't send a
21129 "DNS resolve socks failed" handshake reply; just close it.
21130 - Stop using C functions that OpenBSD's linker doesn't like.
21131 - Don't launch requests for descriptors unless we have networkstatuses
21132 from at least half of the authorities. This delays the first
21133 download slightly under pathological circumstances, but can prevent
21134 us from downloading a bunch of descriptors we don't need.
21135 - Do not log IPs with TLS failures for incoming TLS
21136 connections. (Fixes bug 382.)
21137 - If the user asks to use invalid exit nodes, be willing to use
21139 - Stop using the reserved ac_cv namespace in our configure script.
21140 - Call stat() slightly less often; use fstat() when possible.
21141 - Refactor the way we handle pending circuits when an OR connection
21142 completes or fails, in an attempt to fix a rare crash bug.
21143 - Only rewrite a conn's address based on X-Forwarded-For: headers
21144 if it's a parseable public IP address; and stop adding extra quotes
21145 to the resulting address.
21148 - Weight directory requests by advertised bandwidth. Now we can
21149 let servers enable write limiting but still allow most clients to
21150 succeed at their directory requests. (We still ignore weights when
21151 choosing a directory authority; I hope this is a feature.)
21154 - Create a new file ReleaseNotes which was the old ChangeLog. The
21155 new ChangeLog file now includes the summaries for all development
21157 - Check for addresses with invalid characters at the exit as well
21158 as at the client, and warn less verbosely when they fail. You can
21159 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
21160 - Adapt a patch from goodell to let the contrib/exitlist script
21161 take arguments rather than require direct editing.
21162 - Inform the server operator when we decide not to advertise a
21163 DirPort due to AccountingMax enabled or a low BandwidthRate. It
21164 was confusing Zax, so now we're hopefully more helpful.
21165 - Bring us one step closer to being able to establish an encrypted
21166 directory tunnel without knowing a descriptor first. Still not
21167 ready yet. As part of the change, now assume we can use a
21168 create_fast cell if we don't know anything about a router.
21169 - Allow exit nodes to use nameservers running on ports other than 53.
21170 - Servers now cache reverse DNS replies.
21171 - Add an --ignore-missing-torrc command-line option so that we can
21172 get the "use sensible defaults if the configuration file doesn't
21173 exist" behavior even when specifying a torrc location on the command
21176 o Minor features (controller):
21177 - Track reasons for OR connection failure; make these reasons
21178 available via the controller interface. (Patch from Mike Perry.)
21179 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
21180 can learn when clients are sending malformed hostnames to Tor.
21181 - Clean up documentation for controller status events.
21182 - Add a REMAP status to stream events to note that a stream's
21183 address has changed because of a cached address or a MapAddress
21187 Changes in version 0.1.2.6-alpha - 2007-01-09
21189 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
21190 connection handles more than 4 gigs in either direction, we crash.
21191 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
21192 advertised exit node, somebody might try to exit from us when
21193 we're bootstrapping and before we've built our descriptor yet.
21194 Refuse the connection rather than crashing.
21197 - Warn if we (as a server) find that we've resolved an address that we
21198 weren't planning to resolve.
21199 - Warn that using select() on any libevent version before 1.1 will be
21200 unnecessarily slow (even for select()).
21201 - Flush ERR-level controller status events just like we currently
21202 flush ERR-level log events, so that a Tor shutdown doesn't prevent
21203 the controller from learning about current events.
21205 o Minor features (more controller status events):
21206 - Implement EXTERNAL_ADDRESS server status event so controllers can
21207 learn when our address changes.
21208 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
21209 can learn when directories reject our descriptor.
21210 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
21211 can learn when a client application is speaking a non-socks protocol
21213 - Implement DANGEROUS_SOCKS client status event so controllers
21214 can learn when a client application is leaking DNS addresses.
21215 - Implement BUG general status event so controllers can learn when
21216 Tor is unhappy about its internal invariants.
21217 - Implement CLOCK_SKEW general status event so controllers can learn
21218 when Tor thinks the system clock is set incorrectly.
21219 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
21220 server status events so controllers can learn when their descriptors
21221 are accepted by a directory.
21222 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
21223 server status events so controllers can learn about Tor's progress in
21224 deciding whether it's reachable from the outside.
21225 - Implement BAD_LIBEVENT general status event so controllers can learn
21226 when we have a version/method combination in libevent that needs to
21228 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
21229 and DNS_USELESS server status events so controllers can learn
21230 about changes to DNS server status.
21232 o Minor features (directory):
21233 - Authorities no longer recommend exits as guards if this would shift
21234 too much load to the exit nodes.
21237 Changes in version 0.1.2.5-alpha - 2007-01-06
21239 - Enable write limiting as well as read limiting. Now we sacrifice
21240 capacity if we're pushing out lots of directory traffic, rather
21241 than overrunning the user's intended bandwidth limits.
21242 - Include TLS overhead when counting bandwidth usage; previously, we
21243 would count only the bytes sent over TLS, but not the bytes used
21245 - Support running the Tor service with a torrc not in the same
21246 directory as tor.exe and default to using the torrc located in
21247 the %appdata%\Tor\ of the user who installed the service. Patch
21249 - Servers now check for the case when common DNS requests are going to
21250 wildcarded addresses (i.e. all getting the same answer), and change
21251 their exit policy to reject *:* if it's happening.
21252 - Implement BEGIN_DIR cells, so we can connect to the directory
21253 server via TLS to do encrypted directory requests rather than
21254 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
21255 config options if you like.
21257 o Minor features (config and docs):
21258 - Start using the state file to store bandwidth accounting data:
21259 the bw_accounting file is now obsolete. We'll keep generating it
21260 for a while for people who are still using 0.1.2.4-alpha.
21261 - Try to batch changes to the state file so that we do as few
21262 disk writes as possible while still storing important things in
21264 - The state file and the bw_accounting file get saved less often when
21265 the AvoidDiskWrites config option is set.
21266 - Make PIDFile work on Windows (untested).
21267 - Add internal descriptions for a bunch of configuration options:
21268 accessible via controller interface and in comments in saved
21270 - Reject *:563 (NNTPS) in the default exit policy. We already reject
21271 NNTP by default, so this seems like a sensible addition.
21272 - Clients now reject hostnames with invalid characters. This should
21273 avoid some inadvertent info leaks. Add an option
21274 AllowNonRFC953Hostnames to disable this behavior, in case somebody
21275 is running a private network with hosts called @, !, and #.
21276 - Add a maintainer script to tell us which options are missing
21277 documentation: "make check-docs".
21278 - Add a new address-spec.txt document to describe our special-case
21279 addresses: .exit, .onion, and .noconnnect.
21281 o Minor features (DNS):
21282 - Ongoing work on eventdns infrastructure: now it has dns server
21283 and ipv6 support. One day Tor will make use of it.
21284 - Add client-side caching for reverse DNS lookups.
21285 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
21286 - When we change nameservers or IP addresses, reset and re-launch
21287 our tests for DNS hijacking.
21289 o Minor features (directory):
21290 - Authorities now specify server versions in networkstatus. This adds
21291 about 2% to the size of compressed networkstatus docs, and allows
21292 clients to tell which servers support BEGIN_DIR and which don't.
21293 The implementation is forward-compatible with a proposed future
21294 protocol version scheme not tied to Tor versions.
21295 - DirServer configuration lines now have an orport= option so
21296 clients can open encrypted tunnels to the authorities without
21297 having downloaded their descriptors yet. Enabled for moria1,
21298 moria2, tor26, and lefkada now in the default configuration.
21299 - Directory servers are more willing to send a 503 "busy" if they
21300 are near their write limit, especially for v1 directory requests.
21301 Now they can use their limited bandwidth for actual Tor traffic.
21302 - Clients track responses with status 503 from dirservers. After a
21303 dirserver has given us a 503, we try not to use it until an hour has
21304 gone by, or until we have no dirservers that haven't given us a 503.
21305 - When we get a 503 from a directory, and we're not a server, we don't
21306 count the failure against the total number of failures allowed
21307 for the thing we're trying to download.
21308 - Report X-Your-Address-Is correctly from tunneled directory
21309 connections; don't report X-Your-Address-Is when it's an internal
21310 address; and never believe reported remote addresses when they're
21312 - Protect against an unlikely DoS attack on directory servers.
21313 - Add a BadDirectory flag to network status docs so that authorities
21314 can (eventually) tell clients about caches they believe to be
21317 o Minor features (controller):
21318 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
21319 - Reimplement GETINFO so that info/names stays in sync with the
21321 - Implement "GETINFO fingerprint".
21322 - Implement "SETEVENTS GUARD" so controllers can get updates on
21323 entry guard status as it changes.
21325 o Minor features (clean up obsolete pieces):
21326 - Remove some options that have been deprecated since at least
21327 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
21328 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
21329 to set log options.
21330 - We no longer look for identity and onion keys in "identity.key" and
21331 "onion.key" -- these were replaced by secret_id_key and
21332 secret_onion_key in 0.0.8pre1.
21333 - We no longer require unrecognized directory entries to be
21336 o Major bugfixes (security):
21337 - Stop sending the HttpProxyAuthenticator string to directory
21338 servers when directory connections are tunnelled through Tor.
21339 - Clients no longer store bandwidth history in the state file.
21340 - Do not log introduction points for hidden services if SafeLogging
21342 - When generating bandwidth history, round down to the nearest
21343 1k. When storing accounting data, round up to the nearest 1k.
21344 - When we're running as a server, remember when we last rotated onion
21345 keys, so that we will rotate keys once they're a week old even if
21346 we never stay up for a week ourselves.
21348 o Major bugfixes (other):
21349 - Fix a longstanding bug in eventdns that prevented the count of
21350 timed-out resolves from ever being reset. This bug caused us to
21351 give up on a nameserver the third time it timed out, and try it
21352 10 seconds later... and to give up on it every time it timed out
21354 - Take out the '5 second' timeout from the connection retry
21355 schedule. Now the first connect attempt will wait a full 10
21356 seconds before switching to a new circuit. Perhaps this will help
21357 a lot. Based on observations from Mike Perry.
21358 - Fix a bug on the Windows implementation of tor_mmap_file() that
21359 would prevent the cached-routers file from ever loading. Reported
21363 - Fix an assert failure when a directory authority sets
21364 AuthDirRejectUnlisted and then receives a descriptor from an
21365 unlisted router. Reported by seeess.
21366 - Avoid a double-free when parsing malformed DirServer lines.
21367 - Fix a bug when a BSD-style PF socket is first used. Patch from
21369 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
21370 to resolve an address at a given exit node even when they ask for
21372 - Servers no longer ever list themselves in their "family" line,
21373 even if configured to do so. This makes it easier to configure
21374 family lists conveniently.
21375 - When running as a server, don't fall back to 127.0.0.1 when no
21376 nameservers are configured in /etc/resolv.conf; instead, make the
21377 user fix resolv.conf or specify nameservers explicitly. (Resolves
21379 - Stop accepting certain malformed ports in configured exit policies.
21380 - Don't re-write the fingerprint file every restart, unless it has
21382 - Stop warning when a single nameserver fails: only warn when _all_ of
21383 our nameservers have failed. Also, when we only have one nameserver,
21384 raise the threshold for deciding that the nameserver is dead.
21385 - Directory authorities now only decide that routers are reachable
21386 if their identity keys are as expected.
21387 - When the user uses bad syntax in the Log config line, stop
21388 suggesting other bad syntax as a replacement.
21389 - Correctly detect ipv6 DNS capability on OpenBSD.
21391 o Minor bugfixes (controller):
21392 - Report the circuit number correctly in STREAM CLOSED events. Bug
21393 reported by Mike Perry.
21394 - Do not report bizarre values for results of accounting GETINFOs
21395 when the last second's write or read exceeds the allotted bandwidth.
21396 - Report "unrecognized key" rather than an empty string when the
21397 controller tries to fetch a networkstatus that doesn't exist.
21400 Changes in version 0.1.1.26 - 2006-12-14
21401 o Security bugfixes:
21402 - Stop sending the HttpProxyAuthenticator string to directory
21403 servers when directory connections are tunnelled through Tor.
21404 - Clients no longer store bandwidth history in the state file.
21405 - Do not log introduction points for hidden services if SafeLogging
21409 - Fix an assert failure when a directory authority sets
21410 AuthDirRejectUnlisted and then receives a descriptor from an
21411 unlisted router (reported by seeess).
21414 Changes in version 0.1.2.4-alpha - 2006-12-03
21416 - Add support for using natd; this allows FreeBSDs earlier than
21417 5.1.2 to have ipfw send connections through Tor without using
21418 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
21421 - Make all connections to addresses of the form ".noconnect"
21422 immediately get closed. This lets application/controller combos
21423 successfully test whether they're talking to the same Tor by
21424 watching for STREAM events.
21425 - Make cross.sh cross-compilation script work even when autogen.sh
21426 hasn't been run. (Patch from Michael Mohr.)
21427 - Statistics dumped by -USR2 now include a breakdown of public key
21428 operations, for profiling.
21431 - Fix a major leak when directory authorities parse their
21432 approved-routers list, a minor memory leak when we fail to pick
21433 an exit node, and a few rare leaks on errors.
21434 - Handle TransPort connections even when the server sends data before
21435 the client sends data. Previously, the connection would just hang
21436 until the client sent data. (Patch from tup based on patch from
21438 - Avoid assert failure when our cached-routers file is empty on
21442 - Don't log spurious warnings when we see a circuit close reason we
21443 don't recognize; it's probably just from a newer version of Tor.
21444 - Have directory authorities allow larger amounts of drift in uptime
21445 without replacing the server descriptor: previously, a server that
21446 restarted every 30 minutes could have 48 "interesting" descriptors
21448 - Start linking to the Tor specification and Tor reference manual
21449 correctly in the Windows installer.
21450 - Add Vidalia to the OS X uninstaller script, so when we uninstall
21451 Tor/Privoxy we also uninstall Vidalia.
21452 - Resume building on Irix64, and fix a lot of warnings from its
21453 MIPSpro C compiler.
21454 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
21455 when we're running as a client.
21458 Changes in version 0.1.1.25 - 2006-11-04
21460 - When a client asks us to resolve (rather than connect to)
21461 an address, and we have a cached answer, give them the cached
21462 answer. Previously, we would give them no answer at all.
21463 - We were building exactly the wrong circuits when we predict
21464 hidden service requirements, meaning Tor would have to build all
21465 its circuits on demand.
21466 - If none of our live entry guards have a high uptime, but we
21467 require a guard with a high uptime, try adding a new guard before
21468 we give up on the requirement. This patch should make long-lived
21469 connections more stable on average.
21470 - When testing reachability of our DirPort, don't launch new
21471 tests when there's already one in progress -- unreachable
21472 servers were stacking up dozens of testing streams.
21474 o Security bugfixes:
21475 - When the user sends a NEWNYM signal, clear the client-side DNS
21476 cache too. Otherwise we continue to act on previous information.
21479 - Avoid a memory corruption bug when creating a hash table for
21481 - Avoid possibility of controller-triggered crash when misusing
21482 certain commands from a v0 controller on platforms that do not
21483 handle printf("%s",NULL) gracefully.
21484 - Avoid infinite loop on unexpected controller input.
21485 - Don't log spurious warnings when we see a circuit close reason we
21486 don't recognize; it's probably just from a newer version of Tor.
21487 - Add Vidalia to the OS X uninstaller script, so when we uninstall
21488 Tor/Privoxy we also uninstall Vidalia.
21491 Changes in version 0.1.2.3-alpha - 2006-10-29
21493 - Prepare for servers to publish descriptors less often: never
21494 discard a descriptor simply for being too old until either it is
21495 recommended by no authorities, or until we get a better one for
21496 the same router. Make caches consider retaining old recommended
21497 routers for even longer.
21498 - If most authorities set a BadExit flag for a server, clients
21499 don't think of it as a general-purpose exit. Clients only consider
21500 authorities that advertise themselves as listing bad exits.
21501 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
21502 headers for content, so that we can work better in the presence of
21503 caching HTTP proxies.
21504 - Allow authorities to list nodes as bad exits by fingerprint or by
21507 o Minor features, controller:
21508 - Add a REASON field to CIRC events; for backward compatibility, this
21509 field is sent only to controllers that have enabled the extended
21510 event format. Also, add additional reason codes to explain why
21511 a given circuit has been destroyed or truncated. (Patches from
21513 - Add a REMOTE_REASON field to extended CIRC events to tell the
21514 controller about why a remote OR told us to close a circuit.
21515 - Stream events also now have REASON and REMOTE_REASON fields,
21516 working much like those for circuit events.
21517 - There's now a GETINFO ns/... field so that controllers can ask Tor
21518 about the current status of a router.
21519 - A new event type "NS" to inform a controller when our opinion of
21520 a router's status has changed.
21521 - Add a GETINFO events/names and GETINFO features/names so controllers
21522 can tell which events and features are supported.
21523 - A new CLEARDNSCACHE signal to allow controllers to clear the
21524 client-side DNS cache without expiring circuits.
21526 o Security bugfixes:
21527 - When the user sends a NEWNYM signal, clear the client-side DNS
21528 cache too. Otherwise we continue to act on previous information.
21531 - Avoid sending junk to controllers or segfaulting when a controller
21532 uses EVENT_NEW_DESC with verbose nicknames.
21533 - Stop triggering asserts if the controller tries to extend hidden
21534 service circuits (reported by mwenge).
21535 - Avoid infinite loop on unexpected controller input.
21536 - When the controller does a "GETINFO network-status", tell it
21537 about even those routers whose descriptors are very old, and use
21538 long nicknames where appropriate.
21539 - Change NT service functions to be loaded on demand. This lets us
21540 build with MinGW without breaking Tor for Windows 98 users.
21541 - Do DirPort reachability tests less often, since a single test
21542 chews through many circuits before giving up.
21543 - In the hidden service example in torrc.sample, stop recommending
21544 esoteric and discouraged hidden service options.
21545 - When stopping an NT service, wait up to 10 sec for it to actually
21546 stop. Patch from Matt Edman; resolves bug 295.
21547 - Fix handling of verbose nicknames with ORCONN controller events:
21548 make them show up exactly when requested, rather than exactly when
21550 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
21551 printing a duplicate "$" in the keys we send (reported by mwenge).
21552 - Correctly set maximum connection limit on Cygwin. (This time
21554 - Try to detect Windows correctly when cross-compiling.
21555 - Detect the size of the routers file correctly even if it is
21556 corrupted (on systems without mmap) or not page-aligned (on systems
21557 with mmap). This bug was harmless.
21558 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
21559 to open a stream fails; now we do in more cases. This should
21560 make clients able to find a good exit faster in some cases, since
21561 unhandleable requests will now get an error rather than timing out.
21562 - Resolve two memory leaks when rebuilding the on-disk router cache
21563 (reported by fookoowa).
21564 - Clean up minor code warnings suggested by the MIPSpro C compiler,
21565 and reported by some Centos users.
21566 - Controller signals now work on non-Unix platforms that don't define
21567 SIGUSR1 and SIGUSR2 the way we expect.
21568 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
21569 values before failing, and always enables eventdns.
21570 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
21571 Try to fix this in configure.in by checking for most functions
21572 before we check for libevent.
21575 Changes in version 0.1.2.2-alpha - 2006-10-07
21577 - Make our async eventdns library on-by-default for Tor servers,
21578 and plan to deprecate the separate dnsworker threads.
21579 - Add server-side support for "reverse" DNS lookups (using PTR
21580 records so clients can determine the canonical hostname for a given
21581 IPv4 address). Only supported by servers using eventdns; servers
21582 now announce in their descriptors whether they support eventdns.
21583 - Specify and implement client-side SOCKS5 interface for reverse DNS
21584 lookups (see doc/socks-extensions.txt).
21585 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
21586 connect to directory servers through Tor. Previously, clients needed
21587 to find Tor exits to make private connections to directory servers.
21588 - Avoid choosing Exit nodes for entry or middle hops when the
21589 total bandwidth available from non-Exit nodes is much higher than
21590 the total bandwidth available from Exit nodes.
21591 - Workaround for name servers (like Earthlink's) that hijack failing
21592 DNS requests and replace the no-such-server answer with a "helpful"
21593 redirect to an advertising-driven search portal. Also work around
21594 DNS hijackers who "helpfully" decline to hijack known-invalid
21595 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
21596 lets you turn it off.
21597 - Send out a burst of long-range padding cells once we've established
21598 that we're reachable. Spread them over 4 circuits, so hopefully
21599 a few will be fast. This exercises our bandwidth and bootstraps
21600 us into the directory more quickly.
21602 o New/improved config options:
21603 - Add new config option "ResolvConf" to let the server operator
21604 choose an alternate resolve.conf file when using eventdns.
21605 - Add an "EnforceDistinctSubnets" option to control our "exclude
21606 servers on the same /16" behavior. It's still on by default; this
21607 is mostly for people who want to operate private test networks with
21608 all the machines on the same subnet.
21609 - If one of our entry guards is on the ExcludeNodes list, or the
21610 directory authorities don't think it's a good guard, treat it as
21611 if it were unlisted: stop using it as a guard, and throw it off
21612 the guards list if it stays that way for a long time.
21613 - Allow directory authorities to be marked separately as authorities
21614 for the v1 directory protocol, the v2 directory protocol, and
21615 as hidden service directories, to make it easier to retire old
21616 authorities. V1 authorities should set "HSAuthoritativeDir 1"
21617 to continue being hidden service authorities too.
21618 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
21620 o Minor features, controller:
21621 - Fix CIRC controller events so that controllers can learn the
21622 identity digests of non-Named servers used in circuit paths.
21623 - Let controllers ask for more useful identifiers for servers. Instead
21624 of learning identity digests for un-Named servers and nicknames
21625 for Named servers, the new identifiers include digest, nickname,
21626 and indication of Named status. Off by default; see control-spec.txt
21627 for more information.
21628 - Add a "getinfo address" controller command so it can display Tor's
21629 best guess to the user.
21630 - New controller event to alert the controller when our server
21631 descriptor has changed.
21632 - Give more meaningful errors on controller authentication failure.
21634 o Minor features, other:
21635 - When asked to resolve a hostname, don't use non-exit servers unless
21636 requested to do so. This allows servers with broken DNS to be
21637 useful to the network.
21638 - Divide eventdns log messages into warn and info messages.
21639 - Reserve the nickname "Unnamed" for routers that can't pick
21640 a hostname: any router can call itself Unnamed; directory
21641 authorities will never allocate Unnamed to any particular router;
21642 clients won't believe that any router is the canonical Unnamed.
21643 - Only include function names in log messages for info/debug messages.
21644 For notice/warn/err, the content of the message should be clear on
21645 its own, and printing the function name only confuses users.
21646 - Avoid some false positives during reachability testing: don't try
21647 to test via a server that's on the same /24 as us.
21648 - If we fail to build a circuit to an intended enclave, and it's
21649 not mandatory that we use that enclave, stop wanting it.
21650 - When eventdns is enabled, allow multithreaded builds on NetBSD and
21651 OpenBSD. (We had previously disabled threads on these platforms
21652 because they didn't have working thread-safe resolver functions.)
21654 o Major bugfixes, anonymity/security:
21655 - If a client asked for a server by name, and there's a named server
21656 in our network-status but we don't have its descriptor yet, we
21657 could return an unnamed server instead.
21658 - Fix NetBSD bug that could allow someone to force uninitialized RAM
21659 to be sent to a server's DNS resolver. This only affects NetBSD
21660 and other platforms that do not bounds-check tolower().
21661 - Reject (most) attempts to use Tor circuits with length one. (If
21662 many people start using Tor as a one-hop proxy, exit nodes become
21663 a more attractive target for compromise.)
21664 - Just because your DirPort is open doesn't mean people should be
21665 able to remotely teach you about hidden service descriptors. Now
21666 only accept rendezvous posts if you've got HSAuthoritativeDir set.
21668 o Major bugfixes, other:
21669 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
21670 - When a client asks the server to resolve (not connect to)
21671 an address, and it has a cached answer, give them the cached answer.
21672 Previously, the server would give them no answer at all.
21673 - Allow really slow clients to not hang up five minutes into their
21674 directory downloads (suggested by Adam J. Richter).
21675 - We were building exactly the wrong circuits when we anticipated
21676 hidden service requirements, meaning Tor would have to build all
21677 its circuits on demand.
21678 - Avoid crashing when we mmap a router cache file of size 0.
21679 - When testing reachability of our DirPort, don't launch new
21680 tests when there's already one in progress -- unreachable
21681 servers were stacking up dozens of testing streams.
21683 o Minor bugfixes, correctness:
21684 - If we're a directory mirror and we ask for "all" network status
21685 documents, we would discard status documents from authorities
21686 we don't recognize.
21687 - Avoid a memory corruption bug when creating a hash table for
21689 - Avoid controller-triggered crash when misusing certain commands
21690 from a v0 controller on platforms that do not handle
21691 printf("%s",NULL) gracefully.
21692 - Don't crash when a controller sends a third argument to an
21693 "extendcircuit" request.
21694 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
21695 response; fix error code when "getinfo dir/status/" fails.
21696 - Avoid crash when telling controller stream-status and a stream
21698 - Patch from Adam Langley to fix assert() in eventdns.c.
21699 - Fix a debug log message in eventdns to say "X resolved to Y"
21700 instead of "X resolved to X".
21701 - Make eventdns give strings for DNS errors, not just error numbers.
21702 - Track unreachable entry guards correctly: don't conflate
21703 'unreachable by us right now' with 'listed as down by the directory
21704 authorities'. With the old code, if a guard was unreachable by
21705 us but listed as running, it would clog our guard list forever.
21706 - Behave correctly in case we ever have a network with more than
21707 2GB/s total advertised capacity.
21708 - Make TrackExitHosts case-insensitive, and fix the behavior of
21709 ".suffix" TrackExitHosts items to avoid matching in the middle of
21711 - Finally fix the openssl warnings from newer gccs that believe that
21712 ignoring a return value is okay, but casting a return value and
21713 then ignoring it is a sign of madness.
21714 - Prevent the contrib/exitlist script from printing the same
21715 result more than once.
21716 - Patch from Steve Hildrey: Generate network status correctly on
21717 non-versioning dirservers.
21718 - Don't listen to the X-Your-Address-Is hint if you did the lookup
21719 via Tor; otherwise you'll think you're the exit node's IP address.
21721 o Minor bugfixes, performance:
21722 - Two small performance improvements on parsing descriptors.
21723 - Major performance improvement on inserting descriptors: change
21724 algorithm from O(n^2) to O(n).
21725 - Make the common memory allocation path faster on machines where
21726 malloc(0) returns a pointer.
21727 - Start remembering X-Your-Address-Is directory hints even if you're
21728 a client, so you can become a server more smoothly.
21729 - Avoid duplicate entries on MyFamily line in server descriptor.
21731 o Packaging, features:
21732 - Remove architecture from OS X builds. The official builds are
21733 now universal binaries.
21734 - The Debian package now uses --verify-config when (re)starting,
21735 to distinguish configuration errors from other errors.
21736 - Update RPMs to require libevent 1.1b.
21738 o Packaging, bugfixes:
21739 - Patches so Tor builds with MinGW on Windows.
21740 - Patches so Tor might run on Cygwin again.
21741 - Resume building on non-gcc compilers and ancient gcc. Resume
21742 building with the -O0 compile flag. Resume building cleanly on
21744 - Run correctly on OS X platforms with case-sensitive filesystems.
21745 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
21746 - Add autoconf checks so Tor can build on Solaris x86 again.
21749 - Documented (and renamed) ServerDNSSearchDomains and
21750 ServerDNSResolvConfFile options.
21751 - Be clearer that the *ListenAddress directives can be repeated
21755 Changes in version 0.1.1.24 - 2006-09-29
21757 - Allow really slow clients to not hang up five minutes into their
21758 directory downloads (suggested by Adam J. Richter).
21759 - Fix major performance regression from 0.1.0.x: instead of checking
21760 whether we have enough directory information every time we want to
21761 do something, only check when the directory information has changed.
21762 This should improve client CPU usage by 25-50%.
21763 - Don't crash if, after a server has been running for a while,
21764 it can't resolve its hostname.
21767 - Allow Tor to start when RunAsDaemon is set but no logs are set.
21768 - Don't crash when the controller receives a third argument to an
21769 "extendcircuit" request.
21770 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
21771 response; fix error code when "getinfo dir/status/" fails.
21772 - Fix configure.in to not produce broken configure files with
21773 more recent versions of autoconf. Thanks to Clint for his auto*
21775 - Fix security bug on NetBSD that could allow someone to force
21776 uninitialized RAM to be sent to a server's DNS resolver. This
21777 only affects NetBSD and other platforms that do not bounds-check
21779 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
21780 methods: these are known to be buggy.
21781 - If we're a directory mirror and we ask for "all" network status
21782 documents, we would discard status documents from authorities
21783 we don't recognize.
21786 Changes in version 0.1.2.1-alpha - 2006-08-27
21788 - Add "eventdns" async dns library from Adam Langley, tweaked to
21789 build on OSX and Windows. Only enabled if you pass the
21790 --enable-eventdns argument to configure.
21791 - Allow servers with no hostname or IP address to learn their
21792 IP address by asking the directory authorities. This code only
21793 kicks in when you would normally have exited with a "no address"
21794 error. Nothing's authenticated, so use with care.
21795 - Rather than waiting a fixed amount of time between retrying
21796 application connections, we wait only 5 seconds for the first,
21797 10 seconds for the second, and 15 seconds for each retry after
21798 that. Hopefully this will improve the expected user experience.
21799 - Patch from Tup to add support for transparent AP connections:
21800 this basically bundles the functionality of trans-proxy-tor
21801 into the Tor mainline. Now hosts with compliant pf/netfilter
21802 implementations can redirect TCP connections straight to Tor
21803 without diverting through SOCKS. Needs docs.
21804 - Busy directory servers save lots of memory by spooling server
21805 descriptors, v1 directories, and v2 networkstatus docs to buffers
21806 as needed rather than en masse. Also mmap the cached-routers
21807 files, so we don't need to keep the whole thing in memory too.
21808 - Automatically avoid picking more than one node from the same
21809 /16 network when constructing a circuit.
21810 - Revise and clean up the torrc.sample that we ship with; add
21811 a section for BandwidthRate and BandwidthBurst.
21814 - Split circuit_t into origin_circuit_t and or_circuit_t, and
21815 split connection_t into edge, or, dir, control, and base structs.
21816 These will save quite a bit of memory on busy servers, and they'll
21817 also help us track down bugs in the code and bugs in the spec.
21818 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
21819 or later. Log when we are doing this, so we can diagnose it when
21820 it fails. (Also, recommend libevent 1.1b for kqueue and
21821 win32 methods; deprecate libevent 1.0b harder; make libevent
21822 recommendation system saner.)
21823 - Start being able to build universal binaries on OS X (thanks
21825 - Export the default exit policy via the control port, so controllers
21826 don't need to guess what it is / will be later.
21827 - Add a man page entry for ProtocolWarnings.
21828 - Add TestVia config option to the man page.
21829 - Remove even more protocol-related warnings from Tor server logs,
21830 such as bad TLS handshakes and malformed begin cells.
21831 - Stop fetching descriptors if you're not a dir mirror and you
21832 haven't tried to establish any circuits lately. [This currently
21833 causes some dangerous behavior, because when you start up again
21834 you'll use your ancient server descriptors.]
21835 - New DirPort behavior: if you have your dirport set, you download
21836 descriptors aggressively like a directory mirror, whether or not
21837 your ORPort is set.
21838 - Get rid of the router_retry_connections notion. Now routers
21839 no longer try to rebuild long-term connections to directory
21840 authorities, and directory authorities no longer try to rebuild
21841 long-term connections to all servers. We still don't hang up
21842 connections in these two cases though -- we need to look at it
21843 more carefully to avoid flapping, and we likely need to wait til
21844 0.1.1.x is obsolete.
21845 - Drop compatibility with obsolete Tors that permit create cells
21846 to have the wrong circ_id_type.
21847 - Re-enable per-connection rate limiting. Get rid of the "OP
21848 bandwidth" concept. Lay groundwork for "bandwidth classes" --
21849 separate global buckets that apply depending on what sort of conn
21851 - Start publishing one minute or so after we find our ORPort
21852 to be reachable. This will help reduce the number of descriptors
21853 we have for ourselves floating around, since it's quite likely
21854 other things (e.g. DirPort) will change during that minute too.
21855 - Fork the v1 directory protocol into its own spec document,
21856 and mark dir-spec.txt as the currently correct (v2) spec.
21859 - When we find our DirPort to be reachable, publish a new descriptor
21860 so we'll tell the world (reported by pnx).
21861 - Publish a new descriptor after we hup/reload. This is important
21862 if our config has changed such that we'll want to start advertising
21863 our DirPort now, etc.
21864 - Allow Tor to start when RunAsDaemon is set but no logs are set.
21865 - When we have a state file we cannot parse, tell the user and
21866 move it aside. Now we avoid situations where the user starts
21867 Tor in 1904, Tor writes a state file with that timestamp in it,
21868 the user fixes her clock, and Tor refuses to start.
21869 - Fix configure.in to not produce broken configure files with
21870 more recent versions of autoconf. Thanks to Clint for his auto*
21872 - "tor --verify-config" now exits with -1(255) or 0 depending on
21873 whether the config options are bad or good.
21874 - Resolve bug 321 when using dnsworkers: append a period to every
21875 address we resolve at the exit node, so that we do not accidentally
21876 pick up local addresses, and so that failing searches are retried
21877 in the resolver search domains. (This is already solved for
21878 eventdns.) (This breaks Blossom servers for now.)
21879 - If we are using an exit enclave and we can't connect, e.g. because
21880 its webserver is misconfigured to not listen on localhost, then
21881 back off and try connecting from somewhere else before we fail.
21884 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
21885 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
21886 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
21887 when the IP address is mapped through MapAddress to a hostname.
21888 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
21889 useless IPv6 DNS resolves.
21890 - Patch suggested by Karsten Loesing: respond to SIGNAL command
21891 before we execute the signal, in case the signal shuts us down.
21892 - Clean up AllowInvalidNodes man page entry.
21893 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
21894 - Add more asserts to track down an assert error on a windows Tor
21895 server with connection_add being called with socket == -1.
21896 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
21897 - Fix misleading log messages: an entry guard that is "unlisted",
21898 as well as not known to be "down" (because we've never heard
21899 of it), is not therefore "up".
21900 - Remove code to special-case "-cvs" ending, since it has not
21901 actually mattered since 0.0.9.
21902 - Make our socks5 handling more robust to broken socks clients:
21903 throw out everything waiting on the buffer in between socks
21904 handshake phases, since they can't possibly (so the theory
21905 goes) have predicted what we plan to respond to them.
21908 Changes in version 0.1.1.23 - 2006-07-30
21910 - Fast Tor servers, especially exit nodes, were triggering asserts
21911 due to a bug in handling the list of pending DNS resolves. Some
21912 bugs still remain here; we're hunting them.
21913 - Entry guards could crash clients by sending unexpected input.
21914 - More fixes on reachability testing: if you find yourself reachable,
21915 then don't ever make any client requests (so you stop predicting
21916 circuits), then hup or have your clock jump, then later your IP
21917 changes, you won't think circuits are working, so you won't try to
21918 test reachability, so you won't publish.
21921 - Avoid a crash if the controller does a resetconf firewallports
21922 and then a setconf fascistfirewall=1.
21923 - Avoid an integer underflow when the dir authority decides whether
21924 a router is stable: we might wrongly label it stable, and compute
21925 a slightly wrong median stability, when a descriptor is published
21927 - Fix a place where we might trigger an assert if we can't build our
21928 own server descriptor yet.
21931 Changes in version 0.1.1.22 - 2006-07-05
21933 - Fix a big bug that was causing servers to not find themselves
21934 reachable if they changed IP addresses. Since only 0.1.1.22+
21935 servers can do reachability testing correctly, now we automatically
21936 make sure to test via one of these.
21937 - Fix to allow clients and mirrors to learn directory info from
21938 descriptor downloads that get cut off partway through.
21939 - Directory authorities had a bug in deciding if a newly published
21940 descriptor was novel enough to make everybody want a copy -- a few
21941 servers seem to be publishing new descriptors many times a minute.
21943 - Fix a rare bug that was causing some servers to complain about
21944 "closing wedged cpuworkers" and skip some circuit create requests.
21945 - Make the Exit flag in directory status documents actually work.
21948 Changes in version 0.1.1.21 - 2006-06-10
21949 o Crash and assert fixes from 0.1.1.20:
21950 - Fix a rare crash on Tor servers that have enabled hibernation.
21951 - Fix a seg fault on startup for Tor networks that use only one
21952 directory authority.
21953 - Fix an assert from a race condition that occurs on Tor servers
21954 while exiting, where various threads are trying to log that they're
21955 exiting, and delete the logs, at the same time.
21956 - Make our unit tests pass again on certain obscure platforms.
21959 - Add support for building SUSE RPM packages.
21960 - Speed up initial bootstrapping for clients: if we are making our
21961 first ever connection to any entry guard, then don't mark it down
21963 - When only one Tor server in the network is labelled as a guard,
21964 and we've already picked him, we would cycle endlessly picking him
21965 again, being unhappy about it, etc. Now we specifically exclude
21966 current guards when picking a new guard.
21967 - Servers send create cells more reliably after the TLS connection
21968 is established: we were sometimes forgetting to send half of them
21969 when we had more than one pending.
21970 - If we get a create cell that asks us to extend somewhere, but the
21971 Tor server there doesn't match the expected digest, we now send
21972 a destroy cell back, rather than silently doing nothing.
21973 - Make options->RedirectExit work again.
21974 - Make cookie authentication for the controller work again.
21975 - Stop being picky about unusual characters in the arguments to
21976 mapaddress. It's none of our business.
21977 - Add a new config option "TestVia" that lets you specify preferred
21978 middle hops to use for test circuits. Perhaps this will let me
21979 debug the reachability problems better.
21981 o Log / documentation fixes:
21982 - If we're a server and some peer has a broken TLS certificate, don't
21983 log about it unless ProtocolWarnings is set, i.e., we want to hear
21984 about protocol violations by others.
21985 - Fix spelling of VirtualAddrNetwork in man page.
21986 - Add a better explanation at the top of the autogenerated torrc file
21987 about what happened to our old torrc.
21990 Changes in version 0.1.1.20 - 2006-05-23
21992 - Downgrade a log severity where servers complain that they're
21994 - Avoid a compile warning on FreeBSD.
21995 - Remove string size limit on NEWDESC messages; solve bug 291.
21996 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
21997 more thoroughly when we're running on windows.
22000 Changes in version 0.1.1.19-rc - 2006-05-03
22002 - Regenerate our local descriptor if it's dirty and we try to use
22003 it locally (e.g. if it changes during reachability detection).
22004 - If we setconf our ORPort to 0, we continued to listen on the
22005 old ORPort and receive connections.
22006 - Avoid a second warning about machine/limits.h on Debian
22008 - Be willing to add our own routerinfo into the routerlist.
22009 Now authorities will include themselves in their directories
22010 and network-statuses.
22011 - Stop trying to upload rendezvous descriptors to every
22012 directory authority: only try the v1 authorities.
22013 - Servers no longer complain when they think they're not
22014 registered with the directory authorities. There were too many
22016 - Backport dist-rpm changes so rpms can be built without errors.
22019 - Implement an option, VirtualAddrMask, to set which addresses
22020 get handed out in response to mapaddress requests. This works
22021 around a bug in tsocks where 127.0.0.0/8 is never socksified.
22024 Changes in version 0.1.1.18-rc - 2006-04-10
22026 - Work harder to download live network-statuses from all the
22027 directory authorities we know about. Improve the threshold
22028 decision logic so we're more robust to edge cases.
22029 - When fetching rendezvous descriptors, we were willing to ask
22030 v2 authorities too, which would always return 404.
22033 - Stop listing down or invalid nodes in the v1 directory. This will
22034 reduce its bulk by about 1/3, and reduce load on directory
22036 - When deciding whether a router is Fast or Guard-worthy, consider
22037 his advertised BandwidthRate and not just the BandwidthCapacity.
22038 - No longer ship INSTALL and README files -- they are useless now.
22039 - Force rpmbuild to behave and honor target_cpu.
22040 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
22041 - Start to include translated versions of the tor-doc-*.html
22042 files, along with the screenshots. Still needs more work.
22043 - Start sending back 512 and 451 errors if mapaddress fails,
22044 rather than not sending anything back at all.
22045 - When we fail to bind or listen on an incoming or outgoing
22046 socket, we should close it before failing. otherwise we just
22047 leak it. (thanks to weasel for finding.)
22048 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
22049 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
22050 - Make NoPublish (even though deprecated) work again.
22051 - Fix a minor security flaw where a versioning auth dirserver
22052 could list a recommended version many times in a row to make
22053 clients more convinced that it's recommended.
22054 - Fix crash bug if there are two unregistered servers running
22055 with the same nickname, one of them is down, and you ask for
22056 them by nickname in your EntryNodes or ExitNodes. Also, try
22057 to pick the one that's running rather than an arbitrary one.
22058 - Fix an infinite loop we could hit if we go offline for too long.
22059 - Complain when we hit WSAENOBUFS on recv() or write() too.
22060 Perhaps this will help us hunt the bug.
22061 - If you're not a versioning dirserver, don't put the string
22062 "client-versions \nserver-versions \n" in your network-status.
22063 - Lower the minimum required number of file descriptors to 1000,
22064 so we can have some overhead for Valgrind on Linux, where the
22065 default ulimit -n is 1024.
22068 - Add tor.dizum.com as the fifth authoritative directory server.
22069 - Add a new config option FetchUselessDescriptors, off by default,
22070 for when you plan to run "exitlist" on your client and you want
22071 to know about even the non-running descriptors.
22074 Changes in version 0.1.1.17-rc - 2006-03-28
22076 - Clients and servers since 0.1.1.10-alpha have been expiring
22077 connections whenever they are idle for 5 minutes and they *do*
22078 have circuits on them. Oops. With this new version, clients will
22079 discard their previous entry guard choices and avoid choosing
22080 entry guards running these flawed versions.
22081 - Fix memory leak when uncompressing concatenated zlib streams. This
22082 was causing substantial leaks over time on Tor servers.
22083 - The v1 directory was including servers as much as 48 hours old,
22084 because that's how the new routerlist->routers works. Now only
22085 include them if they're 20 hours old or less.
22088 - Resume building on irix64, netbsd 2.0, etc.
22089 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
22091 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
22092 and it is confusing some users.
22093 - Mirrors stop caching the v1 directory so often.
22094 - Make the max number of old descriptors that a cache will hold
22095 rise with the number of directory authorities, so we can scale.
22096 - Change our win32 uname() hack to be more forgiving about what
22097 win32 versions it thinks it's found.
22100 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
22102 - When the controller's *setconf commands fail, collect an error
22103 message in a string and hand it back to the controller.
22104 - Make the v2 dir's "Fast" flag based on relative capacity, just
22105 like "Stable" is based on median uptime. Name everything in the
22106 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
22107 - Log server fingerprint on startup, so new server operators don't
22108 have to go hunting around their filesystem for it.
22109 - Return a robots.txt on our dirport to discourage google indexing.
22110 - Let the controller ask for GETINFO dir/status/foo so it can ask
22111 directly rather than connecting to the dir port. Only works when
22112 dirport is set for now.
22114 o New config options rather than constants in the code:
22115 - SocksTimeout: How long do we let a socks connection wait
22116 unattached before we fail it?
22117 - CircuitBuildTimeout: Cull non-open circuits that were born
22118 at least this many seconds ago.
22119 - CircuitIdleTimeout: Cull open clean circuits that were born
22120 at least this many seconds ago.
22123 Changes in version 0.1.1.16-rc - 2006-03-18
22124 o Bugfixes on 0.1.1.15-rc:
22125 - Fix assert when the controller asks to attachstream a connect-wait
22126 or resolve-wait stream.
22127 - Now do address rewriting when the controller asks us to attach
22128 to a particular circuit too. This will let Blossom specify
22129 "moria2.exit" without having to learn what moria2's IP address is.
22130 - Make the "tor --verify-config" command-line work again, so people
22131 can automatically check if their torrc will parse.
22132 - Authoritative dirservers no longer require an open connection from
22133 a server to consider him "reachable". We need this change because
22134 when we add new auth dirservers, old servers won't know not to
22136 - Let Tor build on Sun CC again.
22137 - Fix an off-by-one buffer size in dirserv.c that magically never
22138 hit our three authorities but broke sjmurdoch's own tor network.
22139 - If we as a directory mirror don't know of any v1 directory
22140 authorities, then don't try to cache any v1 directories.
22141 - Stop warning about unknown servers in our family when they are
22142 given as hex digests.
22143 - Stop complaining as quickly to the server operator that he
22144 hasn't registered his nickname/key binding.
22145 - Various cleanups so we can add new V2 Auth Dirservers.
22146 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
22147 reflect the updated flags in our v2 dir protocol.
22148 - Resume allowing non-printable characters for exit streams (both
22149 for connecting and for resolving). Now we tolerate applications
22150 that don't follow the RFCs. But continue to block malformed names
22153 o Bugfixes on 0.1.0.x:
22154 - Fix assert bug in close_logs(): when we close and delete logs,
22155 remove them all from the global "logfiles" list.
22156 - Fix minor integer overflow in calculating when we expect to use up
22157 our bandwidth allocation before hibernating.
22158 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
22159 there are multiple SSLs installed with different versions.
22160 - When we try to be a server and Address is not explicitly set and
22161 our hostname resolves to a private IP address, try to use an
22162 interface address if it has a public address. Now Windows machines
22163 that think of themselves as localhost can work by default.
22166 - Let the controller ask for GETINFO dir/server/foo so it can ask
22167 directly rather than connecting to the dir port.
22168 - Let the controller tell us about certain router descriptors
22169 that it doesn't want Tor to use in circuits. Implement
22170 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
22171 - New config option SafeSocks to reject all application connections
22172 using unsafe socks protocols. Defaults to off.
22175 Changes in version 0.1.1.15-rc - 2006-03-11
22176 o Bugfixes and cleanups:
22177 - When we're printing strings from the network, don't try to print
22178 non-printable characters. This protects us against shell escape
22179 sequence exploits, and also against attacks to fool humans into
22180 misreading their logs.
22181 - Fix a bug where Tor would fail to establish any connections if you
22182 left it off for 24 hours and then started it: we were happy with
22183 the obsolete network statuses, but they all referred to router
22184 descriptors that were too old to fetch, so we ended up with no
22185 valid router descriptors.
22186 - Fix a seg fault in the controller's "getinfo orconn-status"
22187 command while listing status on incoming handshaking connections.
22188 Introduce a status name "NEW" for these connections.
22189 - If we get a linelist or linelist_s config option from the torrc
22190 (e.g. ExitPolicy) and it has no value, warn and skip rather than
22191 silently resetting it to its default.
22192 - Don't abandon entry guards until they've been down or gone for
22194 - Cleaner and quieter log messages.
22197 - New controller signal NEWNYM that makes new application requests
22198 use clean circuits.
22199 - Add a new circuit purpose 'controller' to let the controller ask
22200 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
22201 controller command to let you specify the purpose if you're
22202 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
22203 command to let you change a circuit's purpose after it's been
22205 - Accept "private:*" in routerdesc exit policies; not generated yet
22206 because older Tors do not understand it.
22207 - Add BSD-style contributed startup script "rc.subr" from Peter
22211 Changes in version 0.1.1.14-alpha - 2006-02-20
22212 o Bugfixes on 0.1.1.x:
22213 - Don't die if we ask for a stdout or stderr log (even implicitly)
22214 and we're set to RunAsDaemon -- just warn.
22215 - We still had a few bugs in the OR connection rotation code that
22216 caused directory servers to slowly aggregate connections to other
22217 fast Tor servers. This time for sure!
22218 - Make log entries on Win32 include the name of the function again.
22219 - We were treating a pair of exit policies if they were equal even
22220 if one said accept and the other said reject -- causing us to
22221 not always publish a new descriptor since we thought nothing
22223 - Retry pending server downloads as well as pending networkstatus
22224 downloads when we unexpectedly get a socks request.
22225 - We were ignoring the IS_FAST flag in the directory status,
22226 meaning we were willing to pick trivial-bandwidth nodes for "fast"
22228 - If the controller's SAVECONF command fails (e.g. due to file
22229 permissions), let the controller know that it failed.
22232 - If we're trying to be a Tor server and running Windows 95/98/ME
22233 as a server, explain that we'll likely crash.
22234 - When we're a server, a client asks for an old-style directory,
22235 and our write bucket is empty, don't give it to him. This way
22236 small servers can continue to serve the directory *sometimes*,
22237 without getting overloaded.
22238 - Compress exit policies even more -- look for duplicate lines
22240 - Clients now honor the "guard" flag in the router status when
22241 picking entry guards, rather than looking at is_fast or is_stable.
22242 - Retain unrecognized lines in $DATADIR/state file, so that we can
22243 be forward-compatible.
22244 - Generate 18.0.0.0/8 address policy format in descs when we can;
22245 warn when the mask is not reducible to a bit-prefix.
22246 - Let the user set ControlListenAddress in the torrc. This can be
22247 dangerous, but there are some cases (like a secured LAN) where it
22249 - Split ReachableAddresses into ReachableDirAddresses and
22250 ReachableORAddresses, so we can restrict Dir conns to port 80
22251 and OR conns to port 443.
22252 - Now we can target arch and OS in rpm builds (contributed by
22253 Phobos). Also make the resulting dist-rpm filename match the
22255 - New config options to help controllers: FetchServerDescriptors
22256 and FetchHidServDescriptors for whether to fetch server
22257 info and hidserv info or let the controller do it, and
22258 PublishServerDescriptor and PublishHidServDescriptors.
22259 - Also let the controller set the __AllDirActionsPrivate config
22260 option if you want all directory fetches/publishes to happen via
22261 Tor (it assumes your controller bootstraps your circuits).
22264 Changes in version 0.1.0.17 - 2006-02-17
22265 o Crash bugfixes on 0.1.0.x:
22266 - When servers with a non-zero DirPort came out of hibernation,
22267 sometimes they would trigger an assert.
22269 o Other important bugfixes:
22270 - On platforms that don't have getrlimit (like Windows), we were
22271 artificially constraining ourselves to a max of 1024
22272 connections. Now just assume that we can handle as many as 15000
22273 connections. Hopefully this won't cause other problems.
22275 o Backported features:
22276 - When we're a server, a client asks for an old-style directory,
22277 and our write bucket is empty, don't give it to him. This way
22278 small servers can continue to serve the directory *sometimes*,
22279 without getting overloaded.
22280 - Whenever you get a 503 in response to a directory fetch, try
22281 once more. This will become important once servers start sending
22282 503's whenever they feel busy.
22283 - Fetch a new directory every 120 minutes, not every 40 minutes.
22284 Now that we have hundreds of thousands of users running the old
22285 directory algorithm, it's starting to hurt a lot.
22286 - Bump up the period for forcing a hidden service descriptor upload
22287 from 20 minutes to 1 hour.
22290 Changes in version 0.1.1.13-alpha - 2006-02-09
22291 o Crashes in 0.1.1.x:
22292 - When you tried to setconf ORPort via the controller, Tor would
22293 crash. So people using TorCP to become a server were sad.
22294 - Solve (I hope) the stack-smashing bug that we were seeing on fast
22295 servers. The problem appears to be something do with OpenSSL's
22296 random number generation, or how we call it, or something. Let me
22297 know if the crashes continue.
22298 - Turn crypto hardware acceleration off by default, until we find
22299 somebody smart who can test it for us. (It appears to produce
22300 seg faults in at least some cases.)
22301 - Fix a rare assert error when we've tried all intro points for
22302 a hidden service and we try fetching the service descriptor again:
22303 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
22306 - Fix a major load balance bug: we were round-robining in 16 KB
22307 chunks, and servers with bandwidthrate of 20 KB, while downloading
22308 a 600 KB directory, would starve their other connections. Now we
22309 try to be a bit more fair.
22310 - Dir authorities and mirrors were never expiring the newest
22311 descriptor for each server, causing memory and directory bloat.
22312 - Fix memory-bloating and connection-bloating bug on servers: We
22313 were never closing any connection that had ever had a circuit on
22314 it, because we were checking conn->n_circuits == 0, yet we had a
22315 bug that let it go negative.
22316 - Make Tor work using squid as your http proxy again -- squid
22317 returns an error if you ask for a URL that's too long, and it uses
22318 a really generic error message. Plus, many people are behind a
22319 transparent squid so they don't even realize it.
22320 - On platforms that don't have getrlimit (like Windows), we were
22321 artificially constraining ourselves to a max of 1024
22322 connections. Now just assume that we can handle as many as 15000
22323 connections. Hopefully this won't cause other problems.
22324 - Add a new config option ExitPolicyRejectPrivate which defaults to
22325 1. This means all exit policies will begin with rejecting private
22326 addresses, unless the server operator explicitly turns it off.
22329 - Clients no longer download descriptors for non-running
22331 - Before we add new directory authorities, we should make it
22332 clear that only v1 authorities should receive/publish hidden
22333 service descriptors.
22336 - As soon as we've fetched some more directory info, immediately
22337 try to download more server descriptors. This way we don't have
22338 a 10 second pause during initial bootstrapping.
22339 - Remove even more loud log messages that the server operator can't
22341 - When we're running an obsolete or un-recommended version, make
22342 the log message more clear about what the problem is and what
22343 versions *are* still recommended.
22344 - Provide a more useful warn message when our onion queue gets full:
22345 the CPU is too slow or the exit policy is too liberal.
22346 - Don't warn when we receive a 503 from a dirserver/cache -- this
22347 will pave the way for them being able to refuse if they're busy.
22348 - When we fail to bind a listener, try to provide a more useful
22349 log message: e.g., "Is Tor already running?"
22350 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
22351 Goldberg can prove things about our handshake protocol more
22353 - MaxConn has been obsolete for a while now. Document the ConnLimit
22354 config option, which is a *minimum* number of file descriptors
22355 that must be available else Tor refuses to start.
22356 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
22357 if you log to syslog and want something other than LOG_DAEMON.
22358 - Make dirservers generate a separate "guard" flag to mean,
22359 "would make a good entry guard". Make clients parse it and vote
22360 on it. Not used by clients yet.
22361 - Implement --with-libevent-dir option to ./configure. Also, improve
22362 search techniques to find libevent, and use those for openssl too.
22363 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
22364 - Only start testing reachability once we've established a
22365 circuit. This will make startup on dirservers less noisy.
22366 - Don't try to upload hidden service descriptors until we have
22367 established a circuit.
22368 - Fix the controller's "attachstream 0" command to treat conn like
22369 it just connected, doing address remapping, handling .exit and
22370 .onion idioms, and so on. Now we're more uniform in making sure
22371 that the controller hears about new and closing connections.
22374 Changes in version 0.1.1.12-alpha - 2006-01-11
22375 o Bugfixes on 0.1.1.x:
22376 - The fix to close duplicate server connections was closing all
22377 Tor client connections if they didn't establish a circuit
22378 quickly enough. Oops.
22379 - Fix minor memory issue (double-free) that happened on exit.
22381 o Bugfixes on 0.1.0.x:
22382 - Tor didn't warn when it failed to open a log file.
22385 Changes in version 0.1.1.11-alpha - 2006-01-10
22386 o Crashes in 0.1.1.x:
22387 - Include all the assert/crash fixes from 0.1.0.16.
22388 - If you start Tor and then quit very quickly, there were some
22389 races that tried to free things that weren't allocated yet.
22390 - Fix a rare memory stomp if you're running hidden services.
22391 - Fix segfault when specifying DirServer in config without nickname.
22392 - Fix a seg fault when you finish connecting to a server but at
22393 that moment you dump his server descriptor.
22394 - Extendcircuit and Attachstream controller commands would
22395 assert/crash if you don't give them enough arguments.
22396 - Fix an assert error when we're out of space in the connection_list
22397 and we try to post a hidden service descriptor (reported by weasel).
22398 - If you specify a relative torrc path and you set RunAsDaemon in
22399 your torrc, then it chdir()'s to the new directory. If you HUP,
22400 it tries to load the new torrc location, fails, and exits.
22401 The fix: no longer allow a relative path to torrc using -f.
22404 - Implement "entry guards": automatically choose a handful of entry
22405 nodes and stick with them for all circuits. Only pick new guards
22406 when the ones you have are unsuitable, and if the old guards
22407 become suitable again, switch back. This will increase security
22408 dramatically against certain end-point attacks. The EntryNodes
22409 config option now provides some hints about which entry guards you
22410 want to use most; and StrictEntryNodes means to only use those.
22411 - New directory logic: download by descriptor digest, not by
22412 fingerprint. Caches try to download all listed digests from
22413 authorities; clients try to download "best" digests from caches.
22414 This avoids partitioning and isolating attacks better.
22415 - Make the "stable" router flag in network-status be the median of
22416 the uptimes of running valid servers, and make clients pay
22417 attention to the network-status flags. Thus the cutoff adapts
22418 to the stability of the network as a whole, making IRC, IM, etc
22419 connections more reliable.
22422 - Tor servers with dynamic IP addresses were needing to wait 18
22423 hours before they could start doing reachability testing using
22424 the new IP address and ports. This is because they were using
22425 the internal descriptor to learn what to test, yet they were only
22426 rebuilding the descriptor once they decided they were reachable.
22427 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
22428 to download certain server descriptors, throw them away, and then
22429 fetch them again after 30 minutes. Now mirrors throw away these
22430 server descriptors so clients can't get them.
22431 - We were leaving duplicate connections to other ORs open for a week,
22432 rather than closing them once we detect a duplicate. This only
22433 really affected authdirservers, but it affected them a lot.
22434 - Spread the authdirservers' reachability testing over the entire
22435 testing interval, so we don't try to do 500 TLS's at once every
22439 - If the network is down, and we try to connect to a conn because
22440 we have a circuit in mind, and we timeout (30 seconds) because the
22441 network never answers, we were expiring the circuit, but we weren't
22442 obsoleting the connection or telling the entry_guards functions.
22443 - Some Tor servers process billions of cells per day. These statistics
22444 need to be uint64_t's.
22445 - Check for integer overflows in more places, when adding elements
22446 to smartlists. This could possibly prevent a buffer overflow
22447 on malicious huge inputs. I don't see any, but I haven't looked
22449 - ReachableAddresses kept growing new "reject *:*" lines on every
22451 - When you "setconf log" via the controller, it should remove all
22452 logs. We were automatically adding back in a "log notice stdout".
22453 - Newly bootstrapped Tor networks couldn't establish hidden service
22454 circuits until they had nodes with high uptime. Be more tolerant.
22455 - We were marking servers down when they could not answer every piece
22456 of the directory request we sent them. This was far too harsh.
22457 - Fix the torify (tsocks) config file to not use Tor for localhost
22459 - Directory authorities now go to the proper authority when asking for
22460 a networkstatus, even when they want a compressed one.
22461 - Fix a harmless bug that was causing Tor servers to log
22462 "Got an end because of misc error, but we're not an AP. Closing."
22463 - Authorities were treating their own descriptor changes as cosmetic,
22464 meaning the descriptor available in the network-status and the
22465 descriptor that clients downloaded were different.
22466 - The OS X installer was adding a symlink for tor_resolve but
22467 the binary was called tor-resolve (reported by Thomas Hardly).
22468 - Workaround a problem with some http proxies where they refuse GET
22469 requests that specify "Content-Length: 0" (reported by Adrian).
22470 - Fix wrong log message when you add a "HiddenServiceNodes" config
22471 line without any HiddenServiceDir line (reported by Chris Thomas).
22474 - Write the TorVersion into the state file so we have a prayer of
22475 keeping forward and backward compatibility.
22476 - Revive the FascistFirewall config option rather than eliminating it:
22477 now it's a synonym for ReachableAddresses *:80,*:443.
22478 - Clients choose directory servers from the network status lists,
22479 not from their internal list of router descriptors. Now they can
22480 go to caches directly rather than needing to go to authorities
22482 - Directory authorities ignore router descriptors that have only
22483 cosmetic differences: do this for 0.1.0.x servers now too.
22484 - Add a new flag to network-status indicating whether the server
22485 can answer v2 directory requests too.
22486 - Authdirs now stop whining so loudly about bad descriptors that
22487 they fetch from other dirservers. So when there's a log complaint,
22488 it's for sure from a freshly uploaded descriptor.
22489 - Reduce memory requirements in our structs by changing the order
22491 - There used to be two ways to specify your listening ports in a
22492 server descriptor: on the "router" line and with a separate "ports"
22493 line. Remove support for the "ports" line.
22494 - New config option "AuthDirRejectUnlisted" for auth dirservers as
22495 a panic button: if we get flooded with unusable servers we can
22496 revert to only listing servers in the approved-routers file.
22497 - Auth dir servers can now mark a fingerprint as "!reject" or
22498 "!invalid" in the approved-routers file (as its nickname), to
22499 refuse descriptors outright or include them but marked as invalid.
22500 - Servers store bandwidth history across restarts/crashes.
22501 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
22502 get a better idea of why their circuits failed. Not used yet.
22503 - Directory mirrors now cache up to 16 unrecognized network-status
22504 docs. Now we can add new authdirservers and they'll be cached too.
22505 - When picking a random directory, prefer non-authorities if any
22507 - New controller option "getinfo desc/all-recent" to fetch the
22508 latest server descriptor for every router that Tor knows about.
22511 Changes in version 0.1.0.16 - 2006-01-02
22512 o Crash bugfixes on 0.1.0.x:
22513 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
22514 corrupting the heap, losing FDs, or crashing when we need to resize
22515 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
22516 - It turns out sparc64 platforms crash on unaligned memory access
22517 too -- so detect and avoid this.
22518 - Handle truncated compressed data correctly (by detecting it and
22520 - Fix possible-but-unlikely free(NULL) in control.c.
22521 - When we were closing connections, there was a rare case that
22522 stomped on memory, triggering seg faults and asserts.
22523 - Avoid potential infinite recursion when building a descriptor. (We
22524 don't know that it ever happened, but better to fix it anyway.)
22525 - We were neglecting to unlink marked circuits from soon-to-close OR
22526 connections, which caused some rare scribbling on freed memory.
22527 - Fix a memory stomping race bug when closing the joining point of two
22528 rendezvous circuits.
22529 - Fix an assert in time parsing found by Steven Murdoch.
22531 o Other bugfixes on 0.1.0.x:
22532 - When we're doing reachability testing, provide more useful log
22533 messages so the operator knows what to expect.
22534 - Do not check whether DirPort is reachable when we are suppressing
22535 advertising it because of hibernation.
22536 - When building with -static or on Solaris, we sometimes needed -ldl.
22537 - When we're deciding whether a stream has enough circuits around
22538 that can handle it, count the freshly dirty ones and not the ones
22539 that are so dirty they won't be able to handle it.
22540 - When we're expiring old circuits, we had a logic error that caused
22541 us to close new rendezvous circuits rather than old ones.
22542 - Give a more helpful log message when you try to change ORPort via
22543 the controller: you should upgrade Tor if you want that to work.
22544 - We were failing to parse Tor versions that start with "Tor ".
22545 - Tolerate faulty streams better: when a stream fails for reason
22546 exitpolicy, stop assuming that the router is lying about his exit
22547 policy. When a stream fails for reason misc, allow it to retry just
22548 as if it was resolvefailed. When a stream has failed three times,
22549 reset its failure count so we can try again and get all three tries.
22552 Changes in version 0.1.1.10-alpha - 2005-12-11
22553 o Correctness bugfixes on 0.1.0.x:
22554 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
22555 corrupting the heap, losing FDs, or crashing when we need to resize
22556 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
22557 - Stop doing the complex voodoo overkill checking for insecure
22558 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
22559 - When we were closing connections, there was a rare case that
22560 stomped on memory, triggering seg faults and asserts.
22561 - We were neglecting to unlink marked circuits from soon-to-close OR
22562 connections, which caused some rare scribbling on freed memory.
22563 - When we're deciding whether a stream has enough circuits around
22564 that can handle it, count the freshly dirty ones and not the ones
22565 that are so dirty they won't be able to handle it.
22566 - Recover better from TCP connections to Tor servers that are
22567 broken but don't tell you (it happens!); and rotate TLS
22568 connections once a week.
22569 - When we're expiring old circuits, we had a logic error that caused
22570 us to close new rendezvous circuits rather than old ones.
22571 - Fix a scary-looking but apparently harmless bug where circuits
22572 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
22573 servers, and never switch to state CIRCUIT_STATE_OPEN.
22574 - When building with -static or on Solaris, we sometimes needed to
22576 - Give a useful message when people run Tor as the wrong user,
22577 rather than telling them to start chowning random directories.
22578 - We were failing to inform the controller about new .onion streams.
22580 o Security bugfixes on 0.1.0.x:
22581 - Refuse server descriptors if the fingerprint line doesn't match
22582 the included identity key. Tor doesn't care, but other apps (and
22583 humans) might actually be trusting the fingerprint line.
22584 - We used to kill the circuit when we receive a relay command we
22585 don't recognize. Now we just drop it.
22586 - Start obeying our firewall options more rigorously:
22587 . If we can't get to a dirserver directly, try going via Tor.
22588 . Don't ever try to connect (as a client) to a place our
22589 firewall options forbid.
22590 . If we specify a proxy and also firewall options, obey the
22591 firewall options even when we're using the proxy: some proxies
22592 can only proxy to certain destinations.
22593 - Fix a bug found by Lasse Overlier: when we were making internal
22594 circuits (intended to be cannibalized later for rendezvous and
22595 introduction circuits), we were picking them so that they had
22596 useful exit nodes. There was no need for this, and it actually
22597 aids some statistical attacks.
22598 - Start treating internal circuits and exit circuits separately.
22599 It's important to keep them separate because internal circuits
22600 have their last hops picked like middle hops, rather than like
22601 exit hops. So exiting on them will break the user's expectations.
22603 o Bugfixes on 0.1.1.x:
22604 - Take out the mis-feature where we tried to detect IP address
22605 flapping for people with DynDNS, and chose not to upload a new
22606 server descriptor sometimes.
22607 - Try to be compatible with OpenSSL 0.9.6 again.
22608 - Log fix: when the controller is logging about .onion addresses,
22609 sometimes it didn't include the ".onion" part of the address.
22610 - Don't try to modify options->DirServers internally -- if the
22611 user didn't specify any, just add the default ones directly to
22612 the trusted dirserver list. This fixes a bug where people running
22613 controllers would use SETCONF on some totally unrelated config
22614 option, and Tor would start yelling at them about changing their
22616 - Let the controller's redirectstream command specify a port, in
22617 case the controller wants to change that too.
22618 - When we requested a pile of server descriptors, we sometimes
22619 accidentally launched a duplicate request for the first one.
22620 - Bugfix for trackhostexits: write down the fingerprint of the
22621 chosen exit, not its nickname, because the chosen exit might not
22623 - When parsing foo.exit, if foo is unknown, and we are leaving
22624 circuits unattached, set the chosen_exit field and leave the
22625 address empty. This matters because controllers got confused
22627 - Directory authorities no longer try to download server
22628 descriptors that they know they will reject.
22630 o Features and updates:
22631 - Replace balanced trees with hash tables: this should make stuff
22632 significantly faster.
22633 - Resume using the AES counter-mode implementation that we ship,
22634 rather than OpenSSL's. Ours is significantly faster.
22635 - Many other CPU and memory improvements.
22636 - Add a new config option FastFirstHopPK (on by default) so clients
22637 do a trivial crypto handshake for their first hop, since TLS has
22638 already taken care of confidentiality and authentication.
22639 - Add a new config option TestSocks so people can see if their
22640 applications are using socks4, socks4a, socks5-with-ip, or
22641 socks5-with-hostname. This way they don't have to keep mucking
22642 with tcpdump and wondering if something got cached somewhere.
22643 - Warn when listening on a public address for socks. I suspect a
22644 lot of people are setting themselves up as open socks proxies,
22645 and they have no idea that jerks on the Internet are using them,
22646 since they simply proxy the traffic into the Tor network.
22647 - Add "private:*" as an alias in configuration for policies. Now
22648 you can simplify your exit policy rather than needing to list
22649 every single internal or nonroutable network space.
22650 - Add a new controller event type that allows controllers to get
22651 all server descriptors that were uploaded to a router in its role
22652 as authoritative dirserver.
22653 - Start shipping socks-extensions.txt, tor-doc-unix.html,
22654 tor-doc-server.html, and stylesheet.css in the tarball.
22655 - Stop shipping tor-doc.html in the tarball.
22658 Changes in version 0.1.1.9-alpha - 2005-11-15
22659 o Usability improvements:
22660 - Start calling it FooListenAddress rather than FooBindAddress,
22661 since few of our users know what it means to bind an address
22663 - Reduce clutter in server logs. We're going to try to make
22664 them actually usable now. New config option ProtocolWarnings that
22665 lets you hear about how _other Tors_ are breaking the protocol. Off
22667 - Divide log messages into logging domains. Once we put some sort
22668 of interface on this, it will let people looking at more verbose
22669 log levels specify the topics they want to hear more about.
22670 - Make directory servers return better http 404 error messages
22671 instead of a generic "Servers unavailable".
22672 - Check for even more Windows version flags when writing the platform
22673 string in server descriptors, and note any we don't recognize.
22674 - Clean up more of the OpenSSL memory when exiting, so we can detect
22675 memory leaks better.
22676 - Make directory authorities be non-versioning, non-naming by
22677 default. Now we can add new directory servers without requiring
22678 their operators to pay close attention.
22679 - When logging via syslog, include the pid whenever we provide
22680 a log entry. Suggested by Todd Fries.
22682 o Performance improvements:
22683 - Directory servers now silently throw away new descriptors that
22684 haven't changed much if the timestamps are similar. We do this to
22685 tolerate older Tor servers that upload a new descriptor every 15
22686 minutes. (It seemed like a good idea at the time.)
22687 - Inline bottleneck smartlist functions; use fast versions by default.
22688 - Add a "Map from digest to void*" abstraction digestmap_t so we
22689 can do less hex encoding/decoding. Use it in router_get_by_digest()
22690 to resolve a performance bottleneck.
22691 - Allow tor_gzip_uncompress to extract as much as possible from
22692 truncated compressed data. Try to extract as many
22693 descriptors as possible from truncated http responses (when
22694 DIR_PURPOSE_FETCH_ROUTERDESC).
22695 - Make circ->onionskin a pointer, not a static array. moria2 was using
22696 125000 circuit_t's after it had been up for a few weeks, which
22697 translates to 20+ megs of wasted space.
22698 - The private half of our EDH handshake keys are now chosen out
22699 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
22701 o Security improvements:
22702 - Start making directory caches retain old routerinfos, so soon
22703 clients can start asking by digest of descriptor rather than by
22704 fingerprint of server.
22705 - Add half our entropy from RAND_poll in OpenSSL. This knows how
22706 to use egd (if present), openbsd weirdness (if present), vms/os2
22707 weirdness (if we ever port there), and more in the future.
22709 o Bugfixes on 0.1.0.x:
22710 - Do round-robin writes of at most 16 kB per write. This might be
22711 more fair on loaded Tor servers, and it might resolve our Windows
22712 crash bug. It might also slow things down.
22713 - Our TLS handshakes were generating a single public/private
22714 keypair for the TLS context, rather than making a new one for
22715 each new connections. Oops. (But we were still rotating them
22716 periodically, so it's not so bad.)
22717 - When we were cannibalizing a circuit with a particular exit
22718 node in mind, we weren't checking to see if that exit node was
22719 already present earlier in the circuit. Oops.
22720 - When a Tor server's IP changes (e.g. from a dyndns address),
22721 upload a new descriptor so clients will learn too.
22722 - Really busy servers were keeping enough circuits open on stable
22723 connections that they were wrapping around the circuit_id
22724 space. (It's only two bytes.) This exposed a bug where we would
22725 feel free to reuse a circuit_id even if it still exists but has
22726 been marked for close. Try to fix this bug. Some bug remains.
22727 - If we would close a stream early (e.g. it asks for a .exit that
22728 we know would refuse it) but the LeaveStreamsUnattached config
22729 option is set by the controller, then don't close it.
22731 o Bugfixes on 0.1.1.8-alpha:
22732 - Fix a big pile of memory leaks, some of them serious.
22733 - Do not try to download a routerdesc if we would immediately reject
22735 - Resume inserting a newline between all router descriptors when
22736 generating (old style) signed directories, since our spec says
22738 - When providing content-type application/octet-stream for
22739 server descriptors using .z, we were leaving out the
22740 content-encoding header. Oops. (Everything tolerated this just
22741 fine, but that doesn't mean we need to be part of the problem.)
22742 - Fix a potential seg fault in getconf and getinfo using version 1
22743 of the controller protocol.
22744 - Avoid crash: do not check whether DirPort is reachable when we
22745 are suppressing it because of hibernation.
22746 - Make --hash-password not crash on exit.
22749 Changes in version 0.1.1.8-alpha - 2005-10-07
22750 o New features (major):
22751 - Clients don't download or use the directory anymore. Now they
22752 download and use network-statuses from the trusted dirservers,
22753 and fetch individual server descriptors as needed from mirrors.
22754 See dir-spec.txt for all the gory details.
22755 - Be more conservative about whether to advertise our DirPort.
22756 The main change is to not advertise if we're running at capacity
22757 and either a) we could hibernate or b) our capacity is low and
22758 we're using a default DirPort.
22759 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
22761 o New features (minor):
22762 - Try to be smart about when to retry network-status and
22763 server-descriptor fetches. Still needs some tuning.
22764 - Stop parsing, storing, or using running-routers output (but
22765 mirrors still cache and serve it).
22766 - Consider a threshold of versioning dirservers (dirservers who have
22767 an opinion about which Tor versions are still recommended) before
22768 deciding whether to warn the user that he's obsolete.
22769 - Dirservers can now reject/invalidate by key and IP, with the
22770 config options "AuthDirInvalid" and "AuthDirReject". This is
22771 useful since currently we automatically list servers as running
22772 and usable even if we know they're jerks.
22773 - Provide dire warnings to any users who set DirServer; move it out
22774 of torrc.sample and into torrc.complete.
22775 - Add MyFamily to torrc.sample in the server section.
22776 - Add nicknames to the DirServer line, so we can refer to them
22777 without requiring all our users to memorize their IP addresses.
22778 - When we get an EOF or a timeout on a directory connection, note
22779 how many bytes of serverdesc we are dropping. This will help
22780 us determine whether it is smart to parse incomplete serverdesc
22782 - Add a new function to "change pseudonyms" -- that is, to stop
22783 using any currently-dirty circuits for new streams, so we don't
22784 link new actions to old actions. Currently it's only called on
22785 HUP (or SIGNAL RELOAD).
22786 - On sighup, if UseHelperNodes changed to 1, use new circuits.
22787 - Start using RAND_bytes rather than RAND_pseudo_bytes from
22788 OpenSSL. Also, reseed our entropy every hour, not just at
22789 startup. And entropy in 512-bit chunks, not 160-bit chunks.
22791 o Fixes on 0.1.1.7-alpha:
22792 - Nobody ever implemented EVENT_ADDRMAP for control protocol
22793 version 0, so don't let version 0 controllers ask for it.
22794 - If you requested something with too many newlines via the
22795 v1 controller protocol, you could crash tor.
22796 - Fix a number of memory leaks, including some pretty serious ones.
22797 - Re-enable DirPort testing again, so Tor servers will be willing
22798 to advertise their DirPort if it's reachable.
22799 - On TLS handshake, only check the other router's nickname against
22800 its expected nickname if is_named is set.
22802 o Fixes forward-ported from 0.1.0.15:
22803 - Don't crash when we don't have any spare file descriptors and we
22804 try to spawn a dns or cpu worker.
22805 - Make the numbers in read-history and write-history into uint64s,
22806 so they don't overflow and publish negatives in the descriptor.
22808 o Fixes on 0.1.0.x:
22809 - For the OS X package's modified privoxy config file, comment
22810 out the "logfile" line so we don't log everything passed
22812 - We were whining about using socks4 or socks5-with-local-lookup
22813 even when it's an IP in the "virtual" range we designed exactly
22815 - We were leaking some memory every time the client changes IPs.
22816 - Never call free() on tor_malloc()d memory. This will help us
22817 use dmalloc to detect memory leaks.
22818 - Check for named servers when looking them up by nickname;
22819 warn when we'recalling a non-named server by its nickname;
22820 don't warn twice about the same name.
22821 - Try to list MyFamily elements by key, not by nickname, and warn
22822 if we've not heard of the server.
22823 - Make windows platform detection (uname equivalent) smarter.
22824 - It turns out sparc64 doesn't like unaligned access either.
22827 Changes in version 0.1.0.15 - 2005-09-23
22828 o Bugfixes on 0.1.0.x:
22829 - Reject ports 465 and 587 (spam targets) in default exit policy.
22830 - Don't crash when we don't have any spare file descriptors and we
22831 try to spawn a dns or cpu worker.
22832 - Get rid of IgnoreVersion undocumented config option, and make us
22833 only warn, never exit, when we're running an obsolete version.
22834 - Don't try to print a null string when your server finds itself to
22835 be unreachable and the Address config option is empty.
22836 - Make the numbers in read-history and write-history into uint64s,
22837 so they don't overflow and publish negatives in the descriptor.
22838 - Fix a minor memory leak in smartlist_string_remove().
22839 - We were only allowing ourselves to upload a server descriptor at
22840 most every 20 minutes, even if it changed earlier than that.
22841 - Clean up log entries that pointed to old URLs.
22844 Changes in version 0.1.1.7-alpha - 2005-09-14
22845 o Fixes on 0.1.1.6-alpha:
22846 - Exit servers were crashing when people asked them to make a
22847 connection to an address not in their exit policy.
22848 - Looking up a non-existent stream for a v1 control connection would
22850 - Fix a seg fault if we ask a dirserver for a descriptor by
22851 fingerprint but he doesn't know about him.
22852 - SETCONF was appending items to linelists, not clearing them.
22853 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
22854 out and refuse the setconf if it would fail.
22855 - Downgrade the dirserver log messages when whining about
22859 - Add Peter Palfrader's check-tor script to tor/contrib/
22860 It lets you easily check whether a given server (referenced by
22861 nickname) is reachable by you.
22862 - Numerous changes to move towards client-side v2 directories. Not
22865 o Fixes on 0.1.0.x:
22866 - If the user gave tor an odd number of command-line arguments,
22867 we were silently ignoring the last one. Now we complain and fail.
22868 [This wins the oldest-bug prize -- this bug has been present since
22869 November 2002, as released in Tor 0.0.0.]
22870 - Do not use unaligned memory access on alpha, mips, or mipsel.
22871 It *works*, but is very slow, so we treat them as if it doesn't.
22872 - Retry directory requests if we fail to get an answer we like
22873 from a given dirserver (we were retrying before, but only if
22874 we fail to connect).
22875 - When writing the RecommendedVersions line, sort them first.
22876 - When the client asked for a rendezvous port that the hidden
22877 service didn't want to provide, we were sending an IP address
22878 back along with the end cell. Fortunately, it was zero. But stop
22880 - Correct "your server is reachable" log entries to indicate that
22881 it was self-testing that told us so.
22884 Changes in version 0.1.1.6-alpha - 2005-09-09
22885 o Fixes on 0.1.1.5-alpha:
22886 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
22887 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
22888 - Fix bug with tor_memmem finding a match at the end of the string.
22889 - Make unit tests run without segfaulting.
22890 - Resolve some solaris x86 compile warnings.
22891 - Handle duplicate lines in approved-routers files without warning.
22892 - Fix bug where as soon as a server refused any requests due to his
22893 exit policy (e.g. when we ask for localhost and he tells us that's
22894 127.0.0.1 and he won't do it), we decided he wasn't obeying his
22895 exit policy using him for any exits.
22896 - Only do openssl hardware accelerator stuff if openssl version is
22899 o New controller features/fixes:
22900 - Add a "RESETCONF" command so you can set config options like
22901 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
22902 a config option in the torrc with no value, then it clears it
22903 entirely (rather than setting it to its default).
22904 - Add a "GETINFO config-file" to tell us where torrc is.
22905 - Avoid sending blank lines when GETINFO replies should be empty.
22906 - Add a QUIT command for the controller (for using it manually).
22907 - Fix a bug in SAVECONF that was adding default dirservers and
22908 other redundant entries to the torrc file.
22910 o Start on the new directory design:
22911 - Generate, publish, cache, serve new network-status format.
22912 - Publish individual descriptors (by fingerprint, by "all", and by
22914 - Publish client and server recommended versions separately.
22915 - Allow tor_gzip_uncompress() to handle multiple concatenated
22916 compressed strings. Serve compressed groups of router
22917 descriptors. The compression logic here could be more
22919 - Distinguish v1 authorities (all currently trusted directories)
22920 from v2 authorities (all trusted directories).
22921 - Change DirServers config line to note which dirs are v1 authorities.
22922 - Add configuration option "V1AuthoritativeDirectory 1" which
22923 moria1, moria2, and tor26 should set.
22924 - Remove option when getting directory cache to see whether they
22925 support running-routers; they all do now. Replace it with one
22926 to see whether caches support v2 stuff.
22929 - Dirservers now do their own external reachability testing of each
22930 Tor server, and only list them as running if they've been found to
22931 be reachable. We also send back warnings to the server's logs if
22932 it uploads a descriptor that we already believe is unreachable.
22933 - Implement exit enclaves: if we know an IP address for the
22934 destination, and there's a running Tor server at that address
22935 which allows exit to the destination, then extend the circuit to
22936 that exit first. This provides end-to-end encryption and end-to-end
22937 authentication. Also, if the user wants a .exit address or enclave,
22938 use 4 hops rather than 3, and cannibalize a general circ for it
22940 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
22941 controller. Also, rotate dns and cpu workers if the controller
22942 changes options that will affect them; and initialize the dns
22943 worker cache tree whether or not we start out as a server.
22944 - Only upload a new server descriptor when options change, 18
22945 hours have passed, uptime is reset, or bandwidth changes a lot.
22946 - Check [X-]Forwarded-For headers in HTTP requests when generating
22947 log messages. This lets people run dirservers (and caches) behind
22948 Apache but still know which IP addresses are causing warnings.
22950 o Config option changes:
22951 - Replace (Fascist)Firewall* config options with a new
22952 ReachableAddresses option that understands address policies.
22953 For example, "ReachableAddresses *:80,*:443"
22954 - Get rid of IgnoreVersion undocumented config option, and make us
22955 only warn, never exit, when we're running an obsolete version.
22956 - Make MonthlyAccountingStart config option truly obsolete now.
22958 o Fixes on 0.1.0.x:
22959 - Reject ports 465 and 587 in the default exit policy, since
22960 people have started using them for spam too.
22961 - It turns out we couldn't bootstrap a network since we added
22962 reachability detection in 0.1.0.1-rc. Good thing the Tor network
22963 has never gone down. Add an AssumeReachable config option to let
22964 servers and dirservers bootstrap. When we're trying to build a
22965 high-uptime or high-bandwidth circuit but there aren't enough
22966 suitable servers, try being less picky rather than simply failing.
22967 - Our logic to decide if the OR we connected to was the right guy
22968 was brittle and maybe open to a mitm for unverified routers.
22969 - We weren't cannibalizing circuits correctly for
22970 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
22971 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
22972 build those from scratch. This should make hidden services faster.
22973 - Predict required circuits better, with an eye toward making hidden
22974 services faster on the service end.
22975 - Retry streams if the exit node sends back a 'misc' failure. This
22976 should result in fewer random failures. Also, after failing
22977 from resolve failed or misc, reset the num failures, so we give
22978 it a fair shake next time we try.
22979 - Clean up the rendezvous warn log msgs, and downgrade some to info.
22980 - Reduce severity on logs about dns worker spawning and culling.
22981 - When we're shutting down and we do something like try to post a
22982 server descriptor or rendezvous descriptor, don't complain that
22983 we seem to be unreachable. Of course we are, we're shutting down.
22984 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
22985 We don't use them yet, but maybe one day our DNS resolver will be
22986 able to discover them.
22987 - Make ContactInfo mandatory for authoritative directory servers.
22988 - Require server descriptors to list IPv4 addresses -- hostnames
22989 are no longer allowed. This also fixes some potential security
22990 problems with people providing hostnames as their address and then
22991 preferentially resolving them to partition users.
22992 - Change log line for unreachability to explicitly suggest /etc/hosts
22993 as the culprit. Also make it clearer what IP address and ports we're
22994 testing for reachability.
22995 - Put quotes around user-supplied strings when logging so users are
22996 more likely to realize if they add bad characters (like quotes)
22998 - Let auth dir servers start without specifying an Address config
23000 - Make unit tests (and other invocations that aren't the real Tor)
23001 run without launching listeners, creating subdirectories, and so on.
23004 Changes in version 0.1.1.5-alpha - 2005-08-08
23005 o Bugfixes included in 0.1.0.14.
23007 o Bugfixes on 0.1.0.x:
23008 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
23009 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
23010 it would silently using ignore the 6668.
23013 Changes in version 0.1.0.14 - 2005-08-08
23014 o Bugfixes on 0.1.0.x:
23015 - Fix the other half of the bug with crypto handshakes
23017 - Fix an assert trigger if you send a 'signal term' via the
23018 controller when it's listening for 'event info' messages.
23021 Changes in version 0.1.1.4-alpha - 2005-08-04
23022 o Bugfixes included in 0.1.0.13.
23025 - Improve tor_gettimeofday() granularity on windows.
23026 - Make clients regenerate their keys when their IP address changes.
23027 - Implement some more GETINFO goodness: expose helper nodes, config
23028 options, getinfo keys.
23031 Changes in version 0.1.0.13 - 2005-08-04
23032 o Bugfixes on 0.1.0.x:
23033 - Fix a critical bug in the security of our crypto handshakes.
23034 - Fix a size_t underflow in smartlist_join_strings2() that made
23035 it do bad things when you hand it an empty smartlist.
23036 - Fix Windows installer to ship Tor license (thanks to Aphex for
23037 pointing out this oversight) and put a link to the doc directory
23039 - Explicitly set no-unaligned-access for sparc: it turns out the
23040 new gcc's let you compile broken code, but that doesn't make it
23044 Changes in version 0.1.1.3-alpha - 2005-07-23
23045 o Bugfixes on 0.1.1.2-alpha:
23046 - Fix a bug in handling the controller's "post descriptor"
23048 - Fix several bugs in handling the controller's "extend circuit"
23050 - Fix a bug in handling the controller's "stream status" event.
23051 - Fix an assert failure if we have a controller listening for
23052 circuit events and we go offline.
23053 - Re-allow hidden service descriptors to publish 0 intro points.
23054 - Fix a crash when generating your hidden service descriptor if
23055 you don't have enough intro points already.
23057 o New features on 0.1.1.2-alpha:
23058 - New controller function "getinfo accounting", to ask how
23059 many bytes we've used in this time period.
23060 - Experimental support for helper nodes: a lot of the risk from
23061 a small static adversary comes because users pick new random
23062 nodes every time they rebuild a circuit. Now users will try to
23063 stick to the same small set of entry nodes if they can. Not
23064 enabled by default yet.
23066 o Bugfixes on 0.1.0.12:
23067 - If you're an auth dir server, always publish your dirport,
23068 even if you haven't yet found yourself to be reachable.
23069 - Fix a size_t underflow in smartlist_join_strings2() that made
23070 it do bad things when you hand it an empty smartlist.
23073 Changes in version 0.1.0.12 - 2005-07-18
23074 o New directory servers:
23075 - tor26 has changed IP address.
23077 o Bugfixes on 0.1.0.x:
23078 - Fix a possible double-free in tor_gzip_uncompress().
23079 - When --disable-threads is set, do not search for or link against
23080 pthreads libraries.
23081 - Don't trigger an assert if an authoritative directory server
23082 claims its dirport is 0.
23083 - Fix bug with removing Tor as an NT service: some people were
23084 getting "The service did not return an error." Thanks to Matt
23088 Changes in version 0.1.1.2-alpha - 2005-07-15
23089 o New directory servers:
23090 - tor26 has changed IP address.
23092 o Bugfixes on 0.1.0.x, crashes/leaks:
23093 - Port the servers-not-obeying-their-exit-policies fix from
23095 - Fix an fd leak in start_daemon().
23096 - On Windows, you can't always reopen a port right after you've
23097 closed it. So change retry_listeners() to only close and re-open
23098 ports that have changed.
23099 - Fix a possible double-free in tor_gzip_uncompress().
23101 o Bugfixes on 0.1.0.x, usability:
23102 - When tor_socketpair() fails in Windows, give a reasonable
23103 Windows-style errno back.
23104 - Let people type "tor --install" as well as "tor -install" when
23106 want to make it an NT service.
23107 - NT service patch from Matt Edman to improve error messages.
23108 - When the controller asks for a config option with an abbreviated
23109 name, give the full name in our response.
23110 - Correct the man page entry on TrackHostExitsExpire.
23111 - Looks like we were never delivering deflated (i.e. compressed)
23112 running-routers lists, even when asked. Oops.
23113 - When --disable-threads is set, do not search for or link against
23114 pthreads libraries.
23116 o Bugfixes on 0.1.1.x:
23117 - Fix a seg fault with autodetecting which controller version is
23121 - New hidden service descriptor format: put a version in it, and
23122 let people specify introduction/rendezvous points that aren't
23123 in "the directory" (which is subjective anyway).
23124 - Allow the DEBUG controller event to work again. Mark certain log
23125 entries as "don't tell this to controllers", so we avoid cycles.
23128 Changes in version 0.1.0.11 - 2005-06-30
23129 o Bugfixes on 0.1.0.x:
23130 - Fix major security bug: servers were disregarding their
23131 exit policies if clients behaved unexpectedly.
23132 - Make OS X init script check for missing argument, so we don't
23133 confuse users who invoke it incorrectly.
23134 - Fix a seg fault in "tor --hash-password foo".
23135 - The MAPADDRESS control command was broken.
23138 Changes in version 0.1.1.1-alpha - 2005-06-29
23140 - Make OS X init script check for missing argument, so we don't
23141 confuse users who invoke it incorrectly.
23142 - Fix a seg fault in "tor --hash-password foo".
23143 - Fix a possible way to DoS dirservers.
23144 - When we complain that your exit policy implicitly allows local or
23145 private address spaces, name them explicitly so operators can
23147 - Make the log message less scary when all the dirservers are
23148 temporarily unreachable.
23149 - We were printing the number of idle dns workers incorrectly when
23153 - Revised controller protocol (version 1) that uses ascii rather
23154 than binary. Add supporting libraries in python and java so you
23155 can use the controller from your applications without caring how
23156 our protocol works.
23157 - Spiffy new support for crypto hardware accelerators. Can somebody
23161 Changes in version 0.0.9.10 - 2005-06-16
23162 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
23163 - Refuse relay cells that claim to have a length larger than the
23164 maximum allowed. This prevents a potential attack that could read
23165 arbitrary memory (e.g. keys) from an exit server's process
23169 Changes in version 0.1.0.10 - 2005-06-14
23170 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
23171 libevent before 1.1a.
23174 Changes in version 0.1.0.9-rc - 2005-06-09
23176 - Reset buf->highwater every time buf_shrink() is called, not just on
23177 a successful shrink. This was causing significant memory bloat.
23178 - Fix buffer overflow when checking hashed passwords.
23179 - Security fix: if seeding the RNG on Win32 fails, quit.
23180 - Allow seeding the RNG on Win32 even when you're not running as
23182 - Disable threading on Solaris too. Something is wonky with it,
23183 cpuworkers, and reentrant libs.
23184 - Reenable the part of the code that tries to flush as soon as an
23185 OR outbuf has a full TLS record available. Perhaps this will make
23186 OR outbufs not grow as huge except in rare cases, thus saving lots
23187 of CPU time plus memory.
23188 - Reject malformed .onion addresses rather then passing them on as
23189 normal web requests.
23190 - Adapt patch from Adam Langley: fix possible memory leak in
23191 tor_lookup_hostname().
23192 - Initialize libevent later in the startup process, so the logs are
23193 already established by the time we start logging libevent warns.
23194 - Use correct errno on win32 if libevent fails.
23195 - Check and warn about known-bad/slow libevent versions.
23196 - Pay more attention to the ClientOnly config option.
23197 - Have torctl.in/tor.sh.in check for location of su binary (needed
23199 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
23200 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
23201 HttpProxyAuthenticator
23202 - Stop warning about sigpipes in the logs. We're going to
23203 pretend that getting these occassionally is normal and fine.
23204 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
23206 installer screens; and don't put stuff into StartupItems unless
23207 the user asks you to.
23208 - Require servers that use the default dirservers to have public IP
23209 addresses. We have too many servers that are configured with private
23210 IPs and their admins never notice the log entries complaining that
23211 their descriptors are being rejected.
23212 - Add OSX uninstall instructions. An actual uninstall script will
23216 Changes in version 0.1.0.8-rc - 2005-05-23
23218 - It turns out that kqueue on OS X 10.3.9 was causing kernel
23219 panics. Disable kqueue on all OS X Tors.
23220 - Fix RPM: remove duplicate line accidentally added to the rpm
23222 - Disable threads on openbsd too, since its gethostaddr is not
23224 - Tolerate libevent 0.8 since it still works, even though it's
23226 - Enable building on Red Hat 9.0 again.
23227 - Allow the middle hop of the testing circuit to be running any
23228 version, now that most of them have the bugfix to let them connect
23229 to unknown servers. This will allow reachability testing to work
23230 even when 0.0.9.7-0.0.9.9 become obsolete.
23231 - Handle relay cells with rh.length too large. This prevents
23232 a potential attack that could read arbitrary memory (maybe even
23233 keys) from the exit server's process.
23234 - We screwed up the dirport reachability testing when we don't yet
23235 have a cached version of the directory. Hopefully now fixed.
23236 - Clean up router_load_single_router() (used by the controller),
23237 so it doesn't seg fault on error.
23238 - Fix a minor memory leak when somebody establishes an introduction
23239 point at your Tor server.
23240 - If a socks connection ends because read fails, don't warn that
23241 you're not sending a socks reply back.
23244 - Add HttpProxyAuthenticator config option too, that works like
23245 the HttpsProxyAuthenticator config option.
23246 - Encode hashed controller passwords in hex instead of base64,
23247 to make it easier to write controllers.
23250 Changes in version 0.1.0.7-rc - 2005-05-17
23252 - Fix a bug in the OS X package installer that prevented it from
23253 installing on Tiger.
23254 - Fix a script bug in the OS X package installer that made it
23255 complain during installation.
23256 - Find libevent even if it's hiding in /usr/local/ and your
23257 CFLAGS and LDFLAGS don't tell you to look there.
23258 - Be able to link with libevent as a shared library (the default
23259 after 1.0d), even if it's hiding in /usr/local/lib and even
23260 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
23261 assuming you're running gcc. Otherwise fail and give a useful
23263 - Fix a bug in the RPM packager: set home directory for _tor to
23264 something more reasonable when first installing.
23265 - Free a minor amount of memory that is still reachable on exit.
23268 Changes in version 0.1.0.6-rc - 2005-05-14
23270 - Implement --disable-threads configure option. Disable threads on
23271 netbsd by default, because it appears to have no reentrant resolver
23273 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
23274 release (1.1) detects and disables kqueue if it's broken.
23275 - Append default exit policy before checking for implicit internal
23276 addresses. Now we don't log a bunch of complaints on startup
23277 when using the default exit policy.
23278 - Some people were putting "Address " in their torrc, and they had
23279 a buggy resolver that resolved " " to 0.0.0.0. Oops.
23280 - If DataDir is ~/.tor, and that expands to /.tor, then default to
23281 LOCALSTATEDIR/tor instead.
23282 - Fix fragmented-message bug in TorControl.py.
23283 - Resolve a minor bug which would prevent unreachable dirports
23284 from getting suppressed in the published descriptor.
23285 - When the controller gave us a new descriptor, we weren't resolving
23286 it immediately, so Tor would think its address was 0.0.0.0 until
23287 we fetched a new directory.
23288 - Fix an uppercase/lowercase case error in suppressing a bogus
23289 libevent warning on some Linuxes.
23292 - Begin scrubbing sensitive strings from logs by default. Turn off
23293 the config option SafeLogging if you need to do debugging.
23294 - Switch to a new buffer management algorithm, which tries to avoid
23295 reallocing and copying quite as much. In first tests it looks like
23296 it uses *more* memory on average, but less cpu.
23297 - First cut at support for "create-fast" cells. Clients can use
23298 these when extending to their first hop, since the TLS already
23299 provides forward secrecy and authentication. Not enabled on
23301 - When dirservers refuse a router descriptor, we now log its
23302 contactinfo, platform, and the poster's IP address.
23303 - Call tor_free_all instead of connections_free_all after forking, to
23304 save memory on systems that need to fork.
23305 - Whine at you if you're a server and you don't set your contactinfo.
23306 - Implement --verify-config command-line option to check if your torrc
23307 is valid without actually launching Tor.
23308 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
23309 rather than just rejecting it.
23312 Changes in version 0.1.0.5-rc - 2005-04-27
23314 - Stop trying to print a null pointer if an OR conn fails because
23315 we didn't like its cert.
23317 - Switch our internal buffers implementation to use a ring buffer,
23318 to hopefully improve performance for fast servers a lot.
23319 - Add HttpsProxyAuthenticator support (basic auth only), based
23320 on patch from Adam Langley.
23321 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
23322 the fast servers that have been joining lately.
23323 - Give hidden service accesses extra time on the first attempt,
23324 since 60 seconds is often only barely enough. This might improve
23326 - Improve performance for dirservers: stop re-parsing the whole
23327 directory every time you regenerate it.
23328 - Add more debugging info to help us find the weird dns freebsd
23329 pthreads bug; cleaner debug messages to help track future issues.
23332 Changes in version 0.0.9.9 - 2005-04-23
23333 o Bugfixes on 0.0.9.x:
23334 - If unofficial Tor clients connect and send weird TLS certs, our
23335 Tor server triggers an assert. This release contains a minimal
23336 backport from the broader fix that we put into 0.1.0.4-rc.
23339 Changes in version 0.1.0.4-rc - 2005-04-23
23341 - If unofficial Tor clients connect and send weird TLS certs, our
23342 Tor server triggers an assert. Stop asserting, and start handling
23343 TLS errors better in other situations too.
23344 - When the controller asks us to tell it about all the debug-level
23345 logs, it turns out we were generating debug-level logs while
23346 telling it about them, which turns into a bad loop. Now keep
23347 track of whether you're sending a debug log to the controller,
23348 and don't log when you are.
23349 - Fix the "postdescriptor" feature of the controller interface: on
23350 non-complete success, only say "done" once.
23352 - Clients are now willing to load balance over up to 2mB, not 1mB,
23353 of advertised bandwidth capacity.
23354 - Add a NoPublish config option, so you can be a server (e.g. for
23355 testing running Tor servers in other Tor networks) without
23356 publishing your descriptor to the primary dirservers.
23359 Changes in version 0.1.0.3-rc - 2005-04-08
23360 o Improvements on 0.1.0.2-rc:
23361 - Client now retries when streams end early for 'hibernating' or
23362 'resource limit' reasons, rather than failing them.
23363 - More automated handling for dirserver operators:
23364 - Automatically approve nodes running 0.1.0.2-rc or later,
23365 now that the the reachability detection stuff is working.
23366 - Now we allow two unverified servers with the same nickname
23367 but different keys. But if a nickname is verified, only that
23368 nickname+key are allowed.
23369 - If you're an authdirserver connecting to an address:port,
23370 and it's not the OR you were expecting, forget about that
23371 descriptor. If he *was* the one you were expecting, then forget
23372 about all other descriptors for that address:port.
23373 - Allow servers to publish descriptors from 12 hours in the future.
23374 Corollary: only whine about clock skew from the dirserver if
23375 he's a trusted dirserver (since now even verified servers could
23376 have quite wrong clocks).
23377 - Adjust maximum skew and age for rendezvous descriptors: let skew
23378 be 48 hours rather than 90 minutes.
23379 - Efficiency improvements:
23380 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
23381 it much faster to look up a circuit for each relay cell.
23382 - Remove most calls to assert_all_pending_dns_resolves_ok(),
23383 since they're eating our cpu on exit nodes.
23384 - Stop wasting time doing a case insensitive comparison for every
23385 dns name every time we do any lookup. Canonicalize the names to
23386 lowercase and be done with it.
23387 - Start sending 'truncated' cells back rather than destroy cells,
23388 if the circuit closes in front of you. This means we won't have
23389 to abandon partially built circuits.
23390 - Only warn once per nickname from add_nickname_list_to_smartlist
23391 per failure, so an entrynode or exitnode choice that's down won't
23393 - Put a note in the torrc about abuse potential with the default
23395 - Revise control spec and implementation to allow all log messages to
23396 be sent to controller with their severities intact (suggested by
23397 Matt Edman). Update TorControl to handle new log event types.
23398 - Provide better explanation messages when controller's POSTDESCRIPTOR
23400 - Stop putting nodename in the Platform string in server descriptors.
23401 It doesn't actually help, and it is confusing/upsetting some people.
23403 o Bugfixes on 0.1.0.2-rc:
23404 - We were printing the host mask wrong in exit policies in server
23405 descriptors. This isn't a critical bug though, since we were still
23406 obeying the exit policy internally.
23407 - Fix Tor when compiled with libevent but without pthreads: move
23408 connection_unregister() from _connection_free() to
23410 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
23411 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
23412 when we look through the connection array, we'll find any of the
23413 cpu/dnsworkers. This is no good.
23415 o Bugfixes on 0.0.9.8:
23416 - Fix possible bug on threading platforms (e.g. win32) which was
23417 leaking a file descriptor whenever a cpuworker or dnsworker died.
23418 - When using preferred entry or exit nodes, ignore whether the
23419 circuit wants uptime or capacity. They asked for the nodes, they
23421 - chdir() to your datadirectory at the *end* of the daemonize process,
23422 not the beginning. This was a problem because the first time you
23423 run tor, if your datadir isn't there, and you have runasdaemon set
23424 to 1, it will try to chdir to it before it tries to create it. Oops.
23425 - Handle changed router status correctly when dirserver reloads
23426 fingerprint file. We used to be dropping all unverified descriptors
23427 right then. The bug was hidden because we would immediately
23428 fetch a directory from another dirserver, which would include the
23429 descriptors we just dropped.
23430 - When we're connecting to an OR and he's got a different nickname/key
23431 than we were expecting, only complain loudly if we're an OP or a
23432 dirserver. Complaining loudly to the OR admins just confuses them.
23433 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
23434 artificially capped at 500kB.
23437 Changes in version 0.0.9.8 - 2005-04-07
23438 o Bugfixes on 0.0.9.x:
23439 - We have a bug that I haven't found yet. Sometimes, very rarely,
23440 cpuworkers get stuck in the 'busy' state, even though the cpuworker
23441 thinks of itself as idle. This meant that no new circuits ever got
23442 established. Here's a workaround to kill any cpuworker that's been
23443 busy for more than 100 seconds.
23446 Changes in version 0.1.0.2-rc - 2005-04-01
23447 o Bugfixes on 0.1.0.1-rc:
23448 - Fixes on reachability detection:
23449 - Don't check for reachability while hibernating.
23450 - If ORPort is reachable but DirPort isn't, still publish the
23451 descriptor, but zero out DirPort until it's found reachable.
23452 - When building testing circs for ORPort testing, use only
23453 high-bandwidth nodes, so fewer circuits fail.
23454 - Complain about unreachable ORPort separately from unreachable
23455 DirPort, so the user knows what's going on.
23456 - Make sure we only conclude ORPort reachability if we didn't
23457 initiate the conn. Otherwise we could falsely conclude that
23458 we're reachable just because we connected to the guy earlier
23459 and he used that same pipe to extend to us.
23460 - Authdirservers shouldn't do ORPort reachability detection,
23461 since they're in clique mode, so it will be rare to find a
23462 server not already connected to them.
23463 - When building testing circuits, always pick middle hops running
23464 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
23465 bug. (This is a kludge; it will go away when 0.0.9.x becomes
23467 - When we decide we're reachable, actually publish our descriptor
23469 - Fix bug in redirectstream in the controller.
23470 - Fix the state descriptor strings so logs don't claim edge streams
23471 are in a different state than they actually are.
23472 - Use recent libevent features when possible (this only really affects
23473 win32 and osx right now, because the new libevent with these
23474 features hasn't been released yet). Add code to suppress spurious
23476 - Prevent possible segfault in connection_close_unattached_ap().
23477 - Fix newlines on torrc in win32.
23478 - Improve error msgs when tor-resolve fails.
23480 o Improvements on 0.0.9.x:
23481 - New experimental script tor/contrib/ExerciseServer.py (needs more
23482 work) that uses the controller interface to build circuits and
23483 fetch pages over them. This will help us bootstrap servers that
23484 have lots of capacity but haven't noticed it yet.
23485 - New experimental script tor/contrib/PathDemo.py (needs more work)
23486 that uses the controller interface to let you choose whole paths
23488 "<hostname>.<path,separated by dots>.<length of path>.path"
23489 - When we've connected to an OR and handshaked but didn't like
23490 the result, we were closing the conn without sending destroy
23491 cells back for pending circuits. Now send those destroys.
23494 Changes in version 0.0.9.7 - 2005-04-01
23495 o Bugfixes on 0.0.9.x:
23496 - Fix another race crash bug (thanks to Glenn Fink for reporting).
23497 - Compare identity to identity, not to nickname, when extending to
23498 a router not already in the directory. This was preventing us from
23499 extending to unknown routers. Oops.
23500 - Make sure to create OS X Tor user in <500 range, so we aren't
23501 creating actual system users.
23502 - Note where connection-that-hasn't-sent-end was marked, and fix
23503 a few really loud instances of this harmless bug (it's fixed more
23507 Changes in version 0.1.0.1-rc - 2005-03-28
23509 - Add reachability testing. Your Tor server will automatically try
23510 to see if its ORPort and DirPort are reachable from the outside,
23511 and it won't upload its descriptor until it decides they are.
23512 - Handle unavailable hidden services better. Handle slow or busy
23513 hidden services better.
23514 - Add support for CONNECTing through https proxies, with "HttpsProxy"
23516 - New exit policy: accept most low-numbered ports, rather than
23517 rejecting most low-numbered ports.
23518 - More Tor controller support (still experimental). See
23519 http://tor.eff.org/doc/control-spec.txt for all the new features,
23520 including signals to emulate unix signals from any platform;
23521 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
23522 closestream; closecircuit; etc.
23523 - Make nt services work and start on startup on win32 (based on
23524 patch by Matt Edman).
23525 - Add a new AddressMap config directive to rewrite incoming socks
23526 addresses. This lets you, for example, declare an implicit
23527 required exit node for certain sites.
23528 - Add a new TrackHostExits config directive to trigger addressmaps
23529 for certain incoming socks addresses -- for sites that break when
23530 your exit keeps changing (based on patch by Mike Perry).
23531 - Redo the client-side dns cache so it's just an addressmap too.
23532 - Notice when our IP changes, and reset stats/uptime/reachability.
23533 - When an application is using socks5, give him the whole variety of
23534 potential socks5 responses (connect refused, host unreachable, etc),
23535 rather than just "success" or "failure".
23536 - A more sane version numbering system. See
23537 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
23538 - New contributed script "exitlist": a simple python script to
23539 parse directories and find Tor nodes that exit to listed
23541 - New contributed script "privoxy-tor-toggle" to toggle whether
23542 Privoxy uses Tor. Seems to be configured for Debian by default.
23543 - Report HTTP reasons to client when getting a response from directory
23544 servers -- so you can actually know what went wrong.
23545 - New config option MaxAdvertisedBandwidth which lets you advertise
23546 a low bandwidthrate (to not attract as many circuits) while still
23547 allowing a higher bandwidthrate in reality.
23549 o Robustness/stability fixes:
23550 - Make Tor use Niels Provos's libevent instead of its current
23551 poll-but-sometimes-select mess. This will let us use faster async
23552 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
23554 - pthread support now too. This was forced because when we forked,
23555 we ended up wasting a lot of duplicate ram over time. Also switch
23556 to foo_r versions of some library calls to allow reentry and
23558 - Better handling for heterogeneous / unreliable nodes:
23559 - Annotate circuits w/ whether they aim to contain high uptime nodes
23560 and/or high capacity nodes. When building circuits, choose
23562 - This means that every single node in an intro rend circuit,
23563 not just the last one, will have a minimum uptime.
23564 - New config option LongLivedPorts to indicate application streams
23565 that will want high uptime circuits.
23566 - Servers reset uptime when a dir fetch entirely fails. This
23567 hopefully reflects stability of the server's network connectivity.
23568 - If somebody starts his tor server in Jan 2004 and then fixes his
23569 clock, don't make his published uptime be a year.
23570 - Reset published uptime when you wake up from hibernation.
23571 - Introduce a notion of 'internal' circs, which are chosen without
23572 regard to the exit policy of the last hop. Intro and rendezvous
23573 circs must be internal circs, to avoid leaking information. Resolve
23574 and connect streams can use internal circs if they want.
23575 - New circuit pooling algorithm: make sure to have enough circs around
23576 to satisfy any predicted ports, and also make sure to have 2 internal
23577 circs around if we've required internal circs lately (and with high
23578 uptime if we've seen that lately too).
23579 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
23580 which describes how often we retry making new circuits if current
23581 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
23582 how long we're willing to make use of an already-dirty circuit.
23583 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
23584 circ as necessary, if there are any completed ones lying around
23585 when we try to launch one.
23586 - Make hidden services try to establish a rendezvous for 30 seconds,
23587 rather than for n (where n=3) attempts to build a circuit.
23588 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
23589 "ShutdownWaitLength".
23590 - Try to be more zealous about calling connection_edge_end when
23591 things go bad with edge conns in connection.c.
23592 - Revise tor-spec to add more/better stream end reasons.
23593 - Revise all calls to connection_edge_end to avoid sending "misc",
23594 and to take errno into account where possible.
23597 - Fix a race condition that can trigger an assert, when we have a
23598 pending create cell and an OR connection fails right then.
23599 - Fix several double-mark-for-close bugs, e.g. where we were finding
23600 a conn for a cell even if that conn is already marked for close.
23601 - Make sequence of log messages when starting on win32 with no config
23602 file more reasonable.
23603 - When choosing an exit node for a new non-internal circ, don't take
23604 into account whether it'll be useful for any pending x.onion
23605 addresses -- it won't.
23606 - Turn addr_policy_compare from a tristate to a quadstate; this should
23607 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
23608 for google.com" problem.
23609 - Make "platform" string in descriptor more accurate for Win32 servers,
23610 so it's not just "unknown platform".
23611 - Fix an edge case in parsing config options (thanks weasel).
23612 If they say "--" on the commandline, it's not an option.
23613 - Reject odd-looking addresses at the client (e.g. addresses that
23614 contain a colon), rather than having the server drop them because
23616 - tor-resolve requests were ignoring .exit if there was a working circuit
23617 they could use instead.
23618 - REUSEADDR on normal platforms means you can rebind to the port
23619 right after somebody else has let it go. But REUSEADDR on win32
23620 means to let you bind to the port _even when somebody else
23621 already has it bound_! So, don't do that on Win32.
23622 - Change version parsing logic: a version is "obsolete" if it is not
23623 recommended and (1) there is a newer recommended version in the
23624 same series, or (2) there are no recommended versions in the same
23625 series, but there are some recommended versions in a newer series.
23626 A version is "new" if it is newer than any recommended version in
23628 - Stop most cases of hanging up on a socks connection without sending
23632 - Require BandwidthRate to be at least 20kB/s for servers.
23633 - When a dirserver causes you to give a warn, mention which dirserver
23635 - New config option DirAllowPrivateAddresses for authdirservers.
23636 Now by default they refuse router descriptors that have non-IP or
23637 private-IP addresses.
23638 - Stop publishing socksport in the directory, since it's not
23639 actually meant to be public. For compatibility, publish a 0 there
23641 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
23642 smart" value, that is low for servers and high for clients.
23643 - If our clock jumps forward by 100 seconds or more, assume something
23644 has gone wrong with our network and abandon all not-yet-used circs.
23645 - Warn when exit policy implicitly allows local addresses.
23646 - If we get an incredibly skewed timestamp from a dirserver mirror
23647 that isn't a verified OR, don't warn -- it's probably him that's
23649 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
23650 cookies to disk and doesn't log each web request to disk. (Thanks
23651 to Brett Carrington for pointing this out.)
23652 - When a client asks us for a dir mirror and we don't have one,
23653 launch an attempt to get a fresh one.
23654 - If we're hibernating and we get a SIGINT, exit immediately.
23655 - Add --with-dmalloc ./configure option, to track memory leaks.
23656 - And try to free all memory on closing, so we can detect what
23658 - Cache local dns resolves correctly even when they're .exit
23660 - Give a better warning when some other server advertises an
23661 ORPort that is actually an apache running ssl.
23662 - Add "opt hibernating 1" to server descriptor to make it clearer
23663 whether the server is hibernating.
23666 Changes in version 0.0.9.6 - 2005-03-24
23667 o Bugfixes on 0.0.9.x (crashes and asserts):
23668 - Add new end stream reasons to maintainance branch. Fix bug where
23669 reason (8) could trigger an assert. Prevent bug from recurring.
23670 - Apparently win32 stat wants paths to not end with a slash.
23671 - Fix assert triggers in assert_cpath_layer_ok(), where we were
23672 blowing away the circuit that conn->cpath_layer points to, then
23673 checking to see if the circ is well-formed. Backport check to make
23674 sure we dont use the cpath on a closed connection.
23675 - Prevent circuit_resume_edge_reading_helper() from trying to package
23676 inbufs for marked-for-close streams.
23677 - Don't crash on hup if your options->address has become unresolvable.
23678 - Some systems (like OS X) sometimes accept() a connection and tell
23679 you the remote host is 0.0.0.0:0. If this happens, due to some
23680 other mis-features, we get confused; so refuse the conn for now.
23682 o Bugfixes on 0.0.9.x (other):
23683 - Fix harmless but scary "Unrecognized content encoding" warn message.
23684 - Add new stream error reason: TORPROTOCOL reason means "you are not
23685 speaking a version of Tor I understand; say bye-bye to your stream."
23686 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
23687 into the future, now that we are more tolerant of skew. This
23688 resolves a bug where a Tor server would refuse to cache a directory
23689 because all the directories it gets are too far in the future;
23690 yet the Tor server never logs any complaints about clock skew.
23691 - Mac packaging magic: make man pages useable, and do not overwrite
23692 existing torrc files.
23693 - Make OS X log happily to /var/log/tor/tor.log
23696 Changes in version 0.0.9.5 - 2005-02-22
23697 o Bugfixes on 0.0.9.x:
23698 - Fix an assert race at exit nodes when resolve requests fail.
23699 - Stop picking unverified dir mirrors--it only leads to misery.
23700 - Patch from Matt Edman to make NT services work better. Service
23701 support is still not compiled into the executable by default.
23702 - Patch from Dmitri Bely so the Tor service runs better under
23703 the win32 SYSTEM account.
23704 - Make tor-resolve actually work (?) on Win32.
23705 - Fix a sign bug when getrlimit claims to have 4+ billion
23706 file descriptors available.
23707 - Stop refusing to start when bandwidthburst == bandwidthrate.
23708 - When create cells have been on the onion queue more than five
23709 seconds, just send back a destroy and take them off the list.
23712 Changes in version 0.0.9.4 - 2005-02-03
23713 o Bugfixes on 0.0.9:
23714 - Fix an assert bug that took down most of our servers: when
23715 a server claims to have 1 GB of bandwidthburst, don't
23717 - Don't crash as badly if we have spawned the max allowed number
23718 of dnsworkers, or we're out of file descriptors.
23719 - Block more file-sharing ports in the default exit policy.
23720 - MaxConn is now automatically set to the hard limit of max
23721 file descriptors we're allowed (ulimit -n), minus a few for
23723 - Give a clearer message when servers need to raise their
23724 ulimit -n when they start running out of file descriptors.
23725 - SGI Compatibility patches from Jan Schaumann.
23726 - Tolerate a corrupt cached directory better.
23727 - When a dirserver hasn't approved your server, list which one.
23728 - Go into soft hibernation after 95% of the bandwidth is used,
23729 not 99%. This is especially important for daily hibernators who
23730 have a small accounting max. Hopefully it will result in fewer
23731 cut connections when the hard hibernation starts.
23732 - Load-balance better when using servers that claim more than
23733 800kB/s of capacity.
23734 - Make NT services work (experimental, only used if compiled in).
23737 Changes in version 0.0.9.3 - 2005-01-21
23738 o Bugfixes on 0.0.9:
23739 - Backport the cpu use fixes from main branch, so busy servers won't
23740 need as much processor time.
23741 - Work better when we go offline and then come back, or when we
23742 run Tor at boot before the network is up. We do this by
23743 optimistically trying to fetch a new directory whenever an
23744 application request comes in and we think we're offline -- the
23745 human is hopefully a good measure of when the network is back.
23746 - Backport some minimal hidserv bugfixes: keep rend circuits open as
23747 long as you keep using them; actually publish hidserv descriptors
23748 shortly after they change, rather than waiting 20-40 minutes.
23749 - Enable Mac startup script by default.
23750 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
23751 - When you update AllowUnverifiedNodes or FirewallPorts via the
23752 controller's setconf feature, we were always appending, never
23754 - When you update HiddenServiceDir via setconf, it was screwing up
23755 the order of reading the lines, making it fail.
23756 - Do not rewrite a cached directory back to the cache; otherwise we
23757 will think it is recent and not fetch a newer one on startup.
23758 - Workaround for webservers that lie about Content-Encoding: Tor
23759 now tries to autodetect compressed directories and compression
23760 itself. This lets us Proxypass dir fetches through apache.
23763 Changes in version 0.0.9.2 - 2005-01-04
23764 o Bugfixes on 0.0.9 (crashes and asserts):
23765 - Fix an assert on startup when the disk is full and you're logging
23767 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
23768 style address, then we'd crash.
23769 - Fix an assert trigger when the running-routers string we get from
23770 a dirserver is broken.
23771 - Make worker threads start and run on win32. Now win32 servers
23773 - Bandaid (not actually fix, but now it doesn't crash) an assert
23774 where the dns worker dies mysteriously and the main Tor process
23775 doesn't remember anything about the address it was resolving.
23777 o Bugfixes on 0.0.9 (Win32):
23778 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
23779 name out of the warning/assert messages.
23780 - Fix a superficial "unhandled error on read" bug on win32.
23781 - The win32 installer no longer requires a click-through for our
23782 license, since our Free Software license grants rights but does not
23784 - Win32: When connecting to a dirserver fails, try another one
23785 immediately. (This was already working for non-win32 Tors.)
23786 - Stop trying to parse $HOME on win32 when hunting for default
23788 - Make tor-resolve.c work on win32 by calling network_init().
23790 o Bugfixes on 0.0.9 (other):
23791 - Make 0.0.9.x build on Solaris again.
23792 - Due to a fencepost error, we were blowing away the \n when reporting
23793 confvalue items in the controller. So asking for multiple config
23794 values at once couldn't work.
23795 - When listing circuits that are pending on an opening OR connection,
23796 if we're an OR we were listing circuits that *end* at us as
23797 being pending on every listener, dns/cpu worker, etc. Stop that.
23798 - Dirservers were failing to create 'running-routers' or 'directory'
23799 strings if we had more than some threshold of routers. Fix them so
23800 they can handle any number of routers.
23801 - Fix a superficial "Duplicate mark for close" bug.
23802 - Stop checking for clock skew for OR connections, even for servers.
23803 - Fix a fencepost error that was chopping off the last letter of any
23804 nickname that is the maximum allowed nickname length.
23805 - Update URLs in log messages so they point to the new website.
23806 - Fix a potential problem in mangling server private keys while
23807 writing to disk (not triggered yet, as far as we know).
23808 - Include the licenses for other free software we include in Tor,
23809 now that we're shipping binary distributions more regularly.
23812 Changes in version 0.0.9.1 - 2004-12-15
23813 o Bugfixes on 0.0.9:
23814 - Make hibernation actually work.
23815 - Make HashedControlPassword config option work.
23816 - When we're reporting event circuit status to a controller,
23817 don't use the stream status code.
23820 Changes in version 0.0.9 - 2004-12-12
23822 - Clean up manpage and torrc.sample file.
23823 - Clean up severities and text of log warnings.
23825 - Make servers trigger an assert when they enter hibernation.
23828 Changes in version 0.0.9rc7 - 2004-12-08
23829 o Bugfixes on 0.0.9rc:
23830 - Fix a stack-trashing crash when an exit node begins hibernating.
23831 - Avoid looking at unallocated memory while considering which
23832 ports we need to build circuits to cover.
23833 - Stop a sigpipe: when an 'end' cell races with eof from the app,
23834 we shouldn't hold-open-until-flush if the eof arrived first.
23835 - Fix a bug with init_cookie_authentication() in the controller.
23836 - When recommending new-format log lines, if the upper bound is
23837 LOG_ERR, leave it implicit.
23839 o Bugfixes on 0.0.8.1:
23840 - Fix a whole slew of memory leaks.
23841 - Fix isspace() and friends so they still make Solaris happy
23842 but also so they don't trigger asserts on win32.
23843 - Fix parse_iso_time on platforms without strptime (eg win32).
23844 - win32: tolerate extra "readable" events better.
23845 - win32: when being multithreaded, leave parent fdarray open.
23846 - Make unit tests work on win32.
23849 Changes in version 0.0.9rc6 - 2004-12-06
23850 o Bugfixes on 0.0.9pre:
23851 - Clean up some more integer underflow opportunities (not exploitable
23853 - While hibernating, hup should not regrow our listeners.
23854 - Send an end to the streams we close when we hibernate, rather
23855 than just chopping them off.
23856 - React to eof immediately on non-open edge connections.
23858 o Bugfixes on 0.0.8.1:
23859 - Calculate timeout for waiting for a connected cell from the time
23860 we sent the begin cell, not from the time the stream started. If
23861 it took a long time to establish the circuit, we would time out
23862 right after sending the begin cell.
23863 - Fix router_compare_addr_to_addr_policy: it was not treating a port
23864 of * as always matching, so we were picking reject *:* nodes as
23865 exit nodes too. Oops.
23868 - New circuit building strategy: keep a list of ports that we've
23869 used in the past 6 hours, and always try to have 2 circuits open
23870 or on the way that will handle each such port. Seed us with port
23871 80 so web users won't complain that Tor is "slow to start up".
23872 - Make kill -USR1 dump more useful stats about circuits.
23873 - When warning about retrying or giving up, print the address, so
23874 the user knows which one it's talking about.
23875 - If you haven't used a clean circuit in an hour, throw it away,
23876 just to be on the safe side. (This means after 6 hours a totally
23877 unused Tor client will have no circuits open.)
23880 Changes in version 0.0.9rc5 - 2004-12-01
23881 o Bugfixes on 0.0.8.1:
23882 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
23883 - Let resolve conns retry/expire also, rather than sticking around
23885 - If we are using select, make sure we stay within FD_SETSIZE.
23887 o Bugfixes on 0.0.9pre:
23888 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
23889 but doesn't seem to be currently; thanks to Ilja van Sprundel for
23891 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
23892 instead. Impose minima and maxima for all *Period options; impose
23893 even tighter maxima for fetching if we are a caching dirserver.
23894 Clip rather than rejecting.
23895 - Fetch cached running-routers from servers that serve it (that is,
23896 authdirservers and servers running 0.0.9rc5-cvs or later.)
23899 - Accept *:706 (silc) in default exit policy.
23900 - Implement new versioning format for post 0.1.
23901 - Support "foo.nickname.exit" addresses, to let Alice request the
23902 address "foo" as viewed by exit node "nickname". Based on a patch
23904 - Make tor --version --version dump the cvs Id of every file.
23907 Changes in version 0.0.9rc4 - 2004-11-28
23908 o Bugfixes on 0.0.8.1:
23909 - Make windows sockets actually non-blocking (oops), and handle
23910 win32 socket errors better.
23912 o Bugfixes on 0.0.9rc1:
23913 - Actually catch the -USR2 signal.
23916 Changes in version 0.0.9rc3 - 2004-11-25
23917 o Bugfixes on 0.0.8.1:
23918 - Flush the log file descriptor after we print "Tor opening log file",
23919 so we don't see those messages days later.
23921 o Bugfixes on 0.0.9rc1:
23922 - Make tor-resolve work again.
23923 - Avoid infinite loop in tor-resolve if tor hangs up on it.
23924 - Fix an assert trigger for clients/servers handling resolves.
23927 Changes in version 0.0.9rc2 - 2004-11-24
23928 o Bugfixes on 0.0.9rc1:
23929 - I broke socks5 support while fixing the eof bug.
23930 - Allow unitless bandwidths and intervals; they default to bytes
23932 - New servers don't start out hibernating; they are active until
23933 they run out of bytes, so they have a better estimate of how
23934 long it takes, and so their operators can know they're working.
23937 Changes in version 0.0.9rc1 - 2004-11-23
23938 o Bugfixes on 0.0.8.1:
23939 - Finally fix a bug that's been plaguing us for a year:
23940 With high load, circuit package window was reaching 0. Whenever
23941 we got a circuit-level sendme, we were reading a lot on each
23942 socket, but only writing out a bit. So we would eventually reach
23943 eof. This would be noticed and acted on even when there were still
23944 bytes sitting in the inbuf.
23945 - When poll() is interrupted, we shouldn't believe the revents values.
23947 o Bugfixes on 0.0.9pre6:
23948 - Fix hibernate bug that caused pre6 to be broken.
23949 - Don't keep rephist info for routers that haven't had activity for
23950 24 hours. (This matters now that clients have keys, since we track
23952 - Never call close_temp_logs while validating log options.
23953 - Fix backslash-escaping on tor.sh.in and torctl.in.
23956 - Implement weekly/monthly/daily accounting: now you specify your
23957 hibernation properties by
23958 AccountingMax N bytes|KB|MB|GB|TB
23959 AccountingStart day|week|month [day] HH:MM
23960 Defaults to "month 1 0:00".
23961 - Let bandwidth and interval config options be specified as 5 bytes,
23962 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
23963 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
23964 get back to normal.)
23965 - If your requested entry or exit node has advertised bandwidth 0,
23967 - Be more greedy about filling up relay cells -- we try reading again
23968 once we've processed the stuff we read, in case enough has arrived
23969 to fill the last cell completely.
23970 - Apply NT service patch from Osamu Fujino. Still needs more work.
23973 Changes in version 0.0.9pre6 - 2004-11-15
23974 o Bugfixes on 0.0.8.1:
23975 - Fix assert failure on malformed socks4a requests.
23976 - Use identity comparison, not nickname comparison, to choose which
23977 half of circuit-ID-space each side gets to use. This is needed
23978 because sometimes we think of a router as a nickname, and sometimes
23979 as a hex ID, and we can't predict what the other side will do.
23980 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
23981 write() call will fail and we handle it there.
23982 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
23983 and smartlist_len, which are two major profiling offenders.
23985 o Bugfixes on 0.0.9pre5:
23986 - Fix a bug in read_all that was corrupting config files on windows.
23987 - When we're raising the max number of open file descriptors to
23988 'unlimited', don't log that we just raised it to '-1'.
23989 - Include event code with events, as required by control-spec.txt.
23990 - Don't give a fingerprint when clients do --list-fingerprint:
23991 it's misleading, because it will never be the same again.
23992 - Stop using strlcpy in tor_strndup, since it was slowing us
23994 - Remove warn on startup about missing cached-directory file.
23995 - Make kill -USR1 work again.
23996 - Hibernate if we start tor during the "wait for wakeup-time" phase
23997 of an accounting interval. Log our hibernation plans better.
23998 - Authoritative dirservers now also cache their directory, so they
23999 have it on start-up.
24002 - Fetch running-routers; cache running-routers; compress
24003 running-routers; serve compressed running-routers.z
24004 - Add NSI installer script contributed by J Doe.
24005 - Commit VC6 and VC7 workspace/project files.
24006 - Commit a tor.spec for making RPM files, with help from jbash.
24007 - Add contrib/torctl.in contributed by Glenn Fink.
24008 - Implement the control-spec's SAVECONF command, to write your
24009 configuration to torrc.
24010 - Get cookie authentication for the controller closer to working.
24011 - Include control-spec.txt in the tarball.
24012 - When set_conf changes our server descriptor, upload a new copy.
24013 But don't upload it too often if there are frequent changes.
24014 - Document authentication config in man page, and document signals
24016 - Clean up confusing parts of man page and torrc.sample.
24017 - Make expand_filename handle ~ and ~username.
24018 - Use autoconf to enable largefile support where necessary. Use
24019 ftello where available, since ftell can fail at 2GB.
24020 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
24021 log more informatively.
24022 - Give a slightly more useful output for "tor -h".
24023 - Refuse application socks connections to port 0.
24024 - Check clock skew for verified servers, but allow unverified
24025 servers and clients to have any clock skew.
24026 - Break DirFetchPostPeriod into:
24027 - DirFetchPeriod for fetching full directory,
24028 - StatusFetchPeriod for fetching running-routers,
24029 - DirPostPeriod for posting server descriptor,
24030 - RendPostPeriod for posting hidden service descriptors.
24031 - Make sure the hidden service descriptors are at a random offset
24032 from each other, to hinder linkability.
24035 Changes in version 0.0.9pre5 - 2004-11-09
24036 o Bugfixes on 0.0.9pre4:
24037 - Fix a seg fault in unit tests (doesn't affect main program).
24038 - Fix an assert bug where a hidden service provider would fail if
24039 the first hop of his rendezvous circuit was down.
24040 - Hidden service operators now correctly handle version 1 style
24041 INTRODUCE1 cells (nobody generates them still, so not a critical
24043 - If do_hup fails, actually notice.
24044 - Handle more errnos from accept() without closing the listener.
24045 Some OpenBSD machines were closing their listeners because
24046 they ran out of file descriptors.
24047 - Send resolve cells to exit routers that are running a new
24048 enough version of the resolve code to work right.
24049 - Better handling of winsock includes on non-MSV win32 compilers.
24050 - Some people had wrapped their tor client/server in a script
24051 that would restart it whenever it died. This did not play well
24052 with our "shut down if your version is obsolete" code. Now people
24053 don't fetch a new directory if their local cached version is
24055 - Make our autogen.sh work on ksh as well as bash.
24058 - Hibernation: New config option "AccountingMaxKB" lets you
24059 set how many KBytes per month you want to allow your server to
24060 consume. Rather than spreading those bytes out evenly over the
24061 month, we instead hibernate for some of the month and pop up
24062 at a deterministic time, work until the bytes are consumed, then
24063 hibernate again. Config option "MonthlyAccountingStart" lets you
24064 specify which day of the month your billing cycle starts on.
24065 - Control interface: a separate program can now talk to your
24066 client/server over a socket, and get/set config options, receive
24067 notifications of circuits and streams starting/finishing/dying,
24068 bandwidth used, etc. The next step is to get some GUIs working.
24069 Let us know if you want to help out. See doc/control-spec.txt .
24070 - Ship a contrib/tor-control.py as an example script to interact
24071 with the control port.
24072 - "tor --hash-password zzyxz" will output a salted password for
24073 use in authenticating to the control interface.
24074 - New log format in config:
24075 "Log minsev[-maxsev] stdout|stderr|syslog" or
24076 "Log minsev[-maxsev] file /var/foo"
24079 - DirPolicy config option, to let people reject incoming addresses
24080 from their dirserver.
24081 - "tor --list-fingerprint" will list your identity key fingerprint
24083 - Add "pass" target for RedirectExit, to make it easier to break
24084 out of a sequence of RedirectExit rules.
24085 - Clients now generate a TLS cert too, in preparation for having
24086 them act more like real nodes.
24087 - Ship src/win32/ in the tarball, so people can use it to build.
24088 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
24090 - New "router-status" line in directory, to better bind each verified
24091 nickname to its identity key.
24092 - Deprecate unofficial config option abbreviations, and abbreviations
24093 not on the command line.
24094 - Add a pure-C tor-resolve implementation.
24095 - Use getrlimit and friends to ensure we can reach MaxConn (currently
24096 1024) file descriptors.
24098 o Code security improvements, inspired by Ilja:
24099 - Replace sprintf with snprintf. (I think they were all safe, but
24101 - Replace strcpy/strncpy with strlcpy in more places.
24102 - Avoid strcat; use snprintf or strlcat instead.
24103 - snprintf wrapper with consistent (though not C99) overflow behavior.
24106 Changes in version 0.0.9pre4 - 2004-10-17
24107 o Bugfixes on 0.0.9pre3:
24108 - If the server doesn't specify an exit policy, use the real default
24109 exit policy, not reject *:*.
24110 - Ignore fascistfirewall when uploading/downloading hidden service
24111 descriptors, since we go through Tor for those; and when using
24112 an HttpProxy, since we assume it can reach them all.
24113 - When looking for an authoritative dirserver, use only the ones
24114 configured at boot. Don't bother looking in the directory.
24115 - The rest of the fix for get_default_conf_file() on older win32.
24116 - Make 'Routerfile' config option obsolete.
24119 - New 'MyFamily nick1,...' config option for a server to
24120 specify other servers that shouldn't be used in the same circuit
24121 with it. Only believed if nick1 also specifies us.
24122 - New 'NodeFamily nick1,nick2,...' config option for a client to
24123 specify nodes that it doesn't want to use in the same circuit.
24124 - New 'Redirectexit pattern address:port' config option for a
24125 server to redirect exit connections, e.g. to a local squid.
24128 Changes in version 0.0.9pre3 - 2004-10-13
24129 o Bugfixes on 0.0.8.1:
24130 - Better torrc example lines for dirbindaddress and orbindaddress.
24131 - Improved bounds checking on parsed ints (e.g. config options and
24132 the ones we find in directories.)
24133 - Better handling of size_t vs int, so we're more robust on 64
24135 - Fix the rest of the bug where a newly started OR would appear
24136 as unverified even after we've added his fingerprint and hupped
24138 - Fix a bug from 0.0.7: when read() failed on a stream, we would
24139 close it without sending back an end. So 'connection refused'
24140 would simply be ignored and the user would get no response.
24142 o Bugfixes on 0.0.9pre2:
24143 - Serving the cached-on-disk directory to people is bad. We now
24144 provide no directory until we've fetched a fresh one.
24145 - Workaround for bug on windows where cached-directories get crlf
24147 - Make get_default_conf_file() work on older windows too.
24148 - If we write a *:* exit policy line in the descriptor, don't write
24149 any more exit policy lines.
24152 - Use only 0.0.9pre1 and later servers for resolve cells.
24153 - Make the dirservers file obsolete.
24154 - Include a dir-signing-key token in directories to tell the
24155 parsing entity which key is being used to sign.
24156 - Remove the built-in bulky default dirservers string.
24157 - New config option "Dirserver %s:%d [fingerprint]", which can be
24158 repeated as many times as needed. If no dirservers specified,
24159 default to moria1,moria2,tor26.
24160 - Make moria2 advertise a dirport of 80, so people behind firewalls
24161 will be able to get a directory.
24162 - Http proxy support
24163 - Dirservers translate requests for http://%s:%d/x to /x
24164 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
24165 be routed through this host.
24166 - Clients ask for /tor/x rather than /x for new enough dirservers.
24167 This way we can one day coexist peacefully with apache.
24168 - Clients specify a "Host: %s%d" http header, to be compatible
24169 with more proxies, and so running squid on an exit node can work.
24172 Changes in version 0.0.8.1 - 2004-10-13
24174 - Fix a seg fault that can be triggered remotely for Tor
24175 clients/servers with an open dirport.
24176 - Fix a rare assert trigger, where routerinfos for entries in
24177 our cpath would expire while we're building the path.
24178 - Fix a bug in OutboundBindAddress so it (hopefully) works.
24179 - Fix a rare seg fault for people running hidden services on
24180 intermittent connections.
24181 - Fix a bug in parsing opt keywords with objects.
24182 - Fix a stale pointer assert bug when a stream detaches and
24184 - Fix a string format vulnerability (probably not exploitable)
24185 in reporting stats locally.
24186 - Fix an assert trigger: sometimes launching circuits can fail
24187 immediately, e.g. because too many circuits have failed recently.
24188 - Fix a compile warning on 64 bit platforms.
24191 Changes in version 0.0.9pre2 - 2004-10-03
24193 - Make fetching a cached directory work for 64-bit platforms too.
24194 - Make zlib.h a required header, not an optional header.
24197 Changes in version 0.0.9pre1 - 2004-10-01
24199 - Stop using separate defaults for no-config-file and
24200 empty-config-file. Now you have to explicitly turn off SocksPort,
24201 if you don't want it open.
24202 - Fix a bug in OutboundBindAddress so it (hopefully) works.
24203 - Improve man page to mention more of the 0.0.8 features.
24204 - Fix a rare seg fault for people running hidden services on
24205 intermittent connections.
24206 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
24208 - Fix more dns related bugs: send back resolve_failed and end cells
24209 more reliably when the resolve fails, rather than closing the
24210 circuit and then trying to send the cell. Also attach dummy resolve
24211 connections to a circuit *before* calling dns_resolve(), to fix
24212 a bug where cached answers would never be sent in RESOLVED cells.
24213 - When we run out of disk space, or other log writing error, don't
24214 crash. Just stop logging to that log and continue.
24215 - We were starting to daemonize before we opened our logs, so if
24216 there were any problems opening logs, we would complain to stderr,
24217 which wouldn't work, and then mysteriously exit.
24218 - Fix a rare bug where sometimes a verified OR would connect to us
24219 before he'd uploaded his descriptor, which would cause us to
24220 assign conn->nickname as though he's unverified. Now we look through
24221 the fingerprint list to see if he's there.
24222 - Fix a rare assert trigger, where routerinfos for entries in
24223 our cpath would expire while we're building the path.
24226 - Clients can ask dirservers for /dir.z to get a compressed version
24227 of the directory. Only works for servers running 0.0.9, of course.
24228 - Make clients cache directories and use them to seed their router
24229 lists at startup. This means clients have a datadir again.
24230 - Configuration infrastructure support for warning on obsolete
24232 - Respond to content-encoding headers by trying to uncompress as
24234 - Reply with a deflated directory when a client asks for "dir.z".
24235 We could use allow-encodings instead, but allow-encodings isn't
24236 specified in HTTP 1.0.
24237 - Raise the max dns workers from 50 to 100.
24238 - Discourage people from setting their dirfetchpostperiod more often
24239 than once per minute.
24240 - Protect dirservers from overzealous descriptor uploading -- wait
24241 10 seconds after directory gets dirty, before regenerating.
24244 Changes in version 0.0.8 - 2004-08-25
24245 o Port it to SunOS 5.9 / Athena
24248 Changes in version 0.0.8rc2 - 2004-08-20
24249 o Make it compile on cygwin again.
24250 o When picking unverified routers, skip those with low uptime and/or
24251 low bandwidth, depending on what properties you care about.
24254 Changes in version 0.0.8rc1 - 2004-08-18
24255 o Changes from 0.0.7.3:
24257 - Fix assert triggers: if the other side returns an address 0.0.0.0,
24258 don't put it into the client dns cache.
24259 - If a begin failed due to exit policy, but we believe the IP address
24260 should have been allowed, switch that router to exitpolicy reject *:*
24261 until we get our next directory.
24263 - Clients choose nodes proportional to advertised bandwidth.
24264 - Avoid using nodes with low uptime as introduction points.
24265 - Handle servers with dynamic IP addresses: don't replace
24266 options->Address with the resolved one at startup, and
24267 detect our address right before we make a routerinfo each time.
24268 - 'FascistFirewall' option to pick dirservers and ORs on specific
24269 ports; plus 'FirewallPorts' config option to tell FascistFirewall
24270 which ports are open. (Defaults to 80,443)
24271 - Be more aggressive about trying to make circuits when the network
24272 has changed (e.g. when you unsuspend your laptop).
24273 - Check for time skew on http headers; report date in response to
24275 - If the entrynode config line has only one node, don't pick it as
24277 - Add strict{entry|exit}nodes config options. If set to 1, then
24278 we refuse to build circuits that don't include the specified entry
24280 - OutboundBindAddress config option, to bind to a specific
24281 IP address for outgoing connect()s.
24282 - End truncated log entries (e.g. directories) with "[truncated]".
24284 o Patches to 0.0.8preX:
24286 - Patches to compile and run on win32 again (maybe)?
24287 - Fix crash when looking for ~/.torrc with no $HOME set.
24288 - Fix a race bug in the unit tests.
24289 - Handle verified/unverified name collisions better when new
24290 routerinfo's arrive in a directory.
24291 - Sometimes routers were getting entered into the stats before
24292 we'd assigned their identity_digest. Oops.
24293 - Only pick and establish intro points after we've gotten a
24296 - AllowUnverifiedNodes config option to let circuits choose no-name
24297 routers in entry,middle,exit,introduction,rendezvous positions.
24298 Allow middle and rendezvous positions by default.
24299 - Add a man page for tor-resolve.
24302 Changes in version 0.0.7.3 - 2004-08-12
24303 o Stop dnsworkers from triggering an assert failure when you
24304 ask them to resolve the host "".
24307 Changes in version 0.0.8pre3 - 2004-08-09
24308 o Changes from 0.0.7.2:
24309 - Allow multiple ORs with same nickname in routerlist -- now when
24310 people give us one identity key for a nickname, then later
24311 another, we don't constantly complain until the first expires.
24312 - Remember used bandwidth (both in and out), and publish 15-minute
24313 snapshots for the past day into our descriptor.
24314 - You can now fetch $DIRURL/running-routers to get just the
24315 running-routers line, not the whole descriptor list. (But
24316 clients don't use this yet.)
24317 - When people mistakenly use Tor as an http proxy, point them
24318 at the tor-doc.html rather than the INSTALL.
24319 - Remove our mostly unused -- and broken -- hex_encode()
24320 function. Use base16_encode() instead. (Thanks to Timo Lindfors
24321 for pointing out this bug.)
24322 - Rotate onion keys every 12 hours, not every 2 hours, so we have
24323 fewer problems with people using the wrong key.
24324 - Change the default exit policy to reject the default edonkey,
24325 kazaa, gnutella ports.
24326 - Add replace_file() to util.[ch] to handle win32's rename().
24328 o Changes from 0.0.8preX:
24329 - Fix two bugs in saving onion keys to disk when rotating, so
24330 hopefully we'll get fewer people using old onion keys.
24331 - Fix an assert error that was making SocksPolicy not work.
24332 - Be willing to expire routers that have an open dirport -- it's
24333 just the authoritative dirservers we want to not forget.
24334 - Reject tor-resolve requests for .onion addresses early, so we
24335 don't build a whole rendezvous circuit and then fail.
24336 - When you're warning a server that he's unverified, don't cry
24337 wolf unpredictably.
24338 - Fix a race condition: don't try to extend onto a connection
24339 that's still handshaking.
24340 - For servers in clique mode, require the conn to be open before
24341 you'll choose it for your path.
24342 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
24343 end relay cell, etc.
24344 - Measure bandwidth capacity over the last 24 hours, not just 12
24345 - Bugfix: authoritative dirservers were making and signing a new
24346 directory for each client, rather than reusing the cached one.
24349 Changes in version 0.0.8pre2 - 2004-08-04
24350 o Changes from 0.0.7.2:
24352 - Check directory signature _before_ you decide whether you're
24353 you're running an obsolete version and should exit.
24354 - Check directory signature _before_ you parse the running-routers
24355 list to decide who's running or verified.
24356 - Bugfixes and features:
24357 - Check return value of fclose while writing to disk, so we don't
24358 end up with broken files when servers run out of disk space.
24359 - Log a warning if the user uses an unsafe socks variant, so people
24360 are more likely to learn about privoxy or socat.
24361 - Dirservers now include RFC1123-style dates in the HTTP headers,
24362 which one day we will use to better detect clock skew.
24364 o Changes from 0.0.8pre1:
24365 - Make it compile without warnings again on win32.
24366 - Log a warning if you're running an unverified server, to let you
24367 know you might want to get it verified.
24368 - Only pick a default nickname if you plan to be a server.
24371 Changes in version 0.0.8pre1 - 2004-07-23
24373 - Made our unit tests compile again on OpenBSD 3.5, and tor
24374 itself compile again on OpenBSD on a sparc64.
24375 - We were neglecting milliseconds when logging on win32, so
24376 everything appeared to happen at the beginning of each second.
24378 o Protocol changes:
24379 - 'Extend' relay cell payloads now include the digest of the
24380 intended next hop's identity key. Now we can verify that we're
24381 extending to the right router, and also extend to routers we
24382 hadn't heard of before.
24385 - Tor nodes can now act as relays (with an advertised ORPort)
24386 without being manually verified by the dirserver operators.
24387 - Uploaded descriptors of unverified routers are now accepted
24388 by the dirservers, and included in the directory.
24389 - Verified routers are listed by nickname in the running-routers
24390 list; unverified routers are listed as "$<fingerprint>".
24391 - We now use hash-of-identity-key in most places rather than
24392 nickname or addr:port, for improved security/flexibility.
24393 - To avoid Sybil attacks, paths still use only verified servers.
24394 But now we have a chance to play around with hybrid approaches.
24395 - Nodes track bandwidth usage to estimate capacity (not used yet).
24396 - ClientOnly option for nodes that never want to become servers.
24397 - Directory caching.
24398 - "AuthoritativeDir 1" option for the official dirservers.
24399 - Now other nodes (clients and servers) will cache the latest
24400 directory they've pulled down.
24401 - They can enable their DirPort to serve it to others.
24402 - Clients will pull down a directory from any node with an open
24403 DirPort, and check the signature/timestamp correctly.
24404 - Authoritative dirservers now fetch directories from other
24405 authdirservers, to stay better synced.
24406 - Running-routers list tells who's down also, along with noting
24407 if they're verified (listed by nickname) or unverified (listed
24409 - Allow dirservers to serve running-router list separately.
24410 This isn't used yet.
24411 - ORs connect-on-demand to other ORs
24412 - If you get an extend cell to an OR you're not connected to,
24413 connect, handshake, and forward the create cell.
24414 - The authoritative dirservers stay connected to everybody,
24415 and everybody stays connected to 0.0.7 servers, but otherwise
24416 clients/servers expire unused connections after 5 minutes.
24417 - When servers get a sigint, they delay 30 seconds (refusing new
24418 connections) then exit. A second sigint causes immediate exit.
24419 - File and name management:
24420 - Look for .torrc if no CONFDIR "torrc" is found.
24421 - If no datadir is defined, then choose, make, and secure ~/.tor
24423 - If torrc not found, exitpolicy reject *:*.
24424 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
24425 - If no nickname is defined, derive default from hostname.
24426 - Rename secret key files, e.g. identity.key -> secret_id_key,
24427 to discourage people from mailing their identity key to tor-ops.
24428 - Refuse to build a circuit before the directory has arrived --
24429 it won't work anyway, since you won't know the right onion keys
24431 - Try other dirservers immediately if the one you try is down. This
24432 should tolerate down dirservers better now.
24433 - Parse tor version numbers so we can do an is-newer-than check
24434 rather than an is-in-the-list check.
24435 - New socks command 'resolve', to let us shim gethostbyname()
24437 - A 'tor_resolve' script to access the socks resolve functionality.
24438 - A new socks-extensions.txt doc file to describe our
24439 interpretation and extensions to the socks protocols.
24440 - Add a ContactInfo option, which gets published in descriptor.
24441 - Publish OR uptime in descriptor (and thus in directory) too.
24442 - Write tor version at the top of each log file
24443 - New docs in the tarball:
24445 - Document that you should proxy your SSL traffic too.
24448 Changes in version 0.0.7.2 - 2004-07-07
24449 o A better fix for the 0.0.0.0 problem, that will hopefully
24450 eliminate the remaining related assertion failures.
24453 Changes in version 0.0.7.1 - 2004-07-04
24454 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
24455 since internally we use 0.0.0.0 to signify "not yet resolved".
24458 Changes in version 0.0.7 - 2004-06-07
24459 o Updated the man page to reflect the new features.
24462 Changes in version 0.0.7rc2 - 2004-06-06
24463 o Changes from 0.0.7rc1:
24464 - Make it build on Win32 again.
24465 o Changes from 0.0.6.2:
24466 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
24470 Changes in version 0.0.7rc1 - 2004-06-02
24472 - On sighup, we were adding another log without removing the first
24473 one. So log messages would get duplicated n times for n sighups.
24474 - Several cases of using a connection after we'd freed it. The
24475 problem was that connections that are pending resolve are in both
24476 the pending_resolve tree, and also the circuit's resolving_streams
24477 list. When you want to remove one, you must remove it from both.
24478 - Fix a double-mark-for-close where an end cell arrived for a
24479 resolving stream, and then the resolve failed.
24480 - Check directory signatures based on name of signer, not on whom
24481 we got the directory from. This will let us cache directories more
24484 - Crank up some of our constants to handle more users.
24487 Changes in version 0.0.7pre1 - 2004-06-02
24488 o Fixes for crashes and other obnoxious bugs:
24489 - Fix an epipe bug: sometimes when directory connections failed
24490 to connect, we would give them a chance to flush before closing
24492 - When we detached from a circuit because of resolvefailed, we
24493 would immediately try the same circuit twice more, and then
24494 give up on the resolve thinking we'd tried three different
24496 - Limit the number of intro circuits we'll attempt to build for a
24497 hidden service per 15-minute period.
24498 - Check recommended-software string *early*, before actually parsing
24499 the directory. Thus we can detect an obsolete version and exit,
24500 even if the new directory format doesn't parse.
24501 o Fixes for security bugs:
24502 - Remember which nodes are dirservers when you startup, and if a
24503 random OR enables his dirport, don't automatically assume he's
24504 a trusted dirserver.
24506 - Directory connections were asking the wrong poll socket to
24507 start writing, and not asking themselves to start writing.
24508 - When we detached from a circuit because we sent a begin but
24509 didn't get a connected, we would use it again the first time;
24510 but after that we would correctly switch to a different one.
24511 - Stop warning when the first onion decrypt attempt fails; they
24512 will sometimes legitimately fail now that we rotate keys.
24513 - Override unaligned-access-ok check when $host_cpu is ia64 or
24514 arm. Apparently they allow it but the kernel whines.
24515 - Dirservers try to reconnect periodically too, in case connections
24517 - Fix some memory leaks in directory servers.
24518 - Allow backslash in Win32 filenames.
24519 - Made Tor build complain-free on FreeBSD, hopefully without
24520 breaking other BSD builds. We'll see.
24522 - Doxygen markup on all functions and global variables.
24523 - Make directory functions update routerlist, not replace it. So
24524 now directory disagreements are not so critical a problem.
24525 - Remove the upper limit on number of descriptors in a dirserver's
24526 directory (not that we were anywhere close).
24527 - Allow multiple logfiles at different severity ranges.
24528 - Allow *BindAddress to specify ":port" rather than setting *Port
24529 separately. Allow multiple instances of each BindAddress config
24530 option, so you can bind to multiple interfaces if you want.
24531 - Allow multiple exit policy lines, which are processed in order.
24532 Now we don't need that huge line with all the commas in it.
24533 - Enable accept/reject policies on SOCKS connections, so you can bind
24534 to 0.0.0.0 but still control who can use your OP.
24537 Changes in version 0.0.6.2 - 2004-05-16
24538 o Our integrity-checking digest was checking only the most recent cell,
24539 not the previous cells like we'd thought.
24540 Thanks to Stefan Mark for finding the flaw!
24543 Changes in version 0.0.6.1 - 2004-05-06
24544 o Fix two bugs in our AES counter-mode implementation (this affected
24545 onion-level stream encryption, but not TLS-level). It turns
24546 out we were doing something much more akin to a 16-character
24547 polyalphabetic cipher. Oops.
24548 Thanks to Stefan Mark for finding the flaw!
24549 o Retire moria3 as a directory server, and add tor26 as a directory
24553 Changes in version 0.0.6 - 2004-05-02
24554 [version bump only]
24557 Changes in version 0.0.6rc4 - 2004-05-01
24558 o Update the built-in dirservers list to use the new directory format
24559 o Fix a rare seg fault: if a node offering a hidden service attempts
24560 to build a circuit to Alice's rendezvous point and fails before it
24561 reaches the last hop, it retries with a different circuit, but
24563 o Handle windows socket errors correctly.
24566 Changes in version 0.0.6rc3 - 2004-04-28
24567 o Don't expire non-general excess circuits (if we had enough
24568 circuits open, we were expiring rendezvous circuits -- even
24569 when they had a stream attached. oops.)
24570 o Fetch randomness from /dev/urandom better (not via fopen/fread)
24571 o Better debugging for tls errors
24572 o Some versions of openssl have an SSL_pending function that erroneously
24573 returns bytes when there is a non-application record pending.
24574 o Set Content-Type on the directory and hidserv descriptor.
24575 o Remove IVs from cipher code, since AES-ctr has none.
24576 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
24577 o We were using an array of length zero in a few places.
24578 o win32's gethostbyname can't resolve an IP to an IP.
24579 o win32's close can't close a socket.
24582 Changes in version 0.0.6rc2 - 2004-04-26
24583 o Fix a bug where we were closing tls connections intermittently.
24584 It turns out openssl keeps its errors around -- so if an error
24585 happens, and you don't ask about it, and then another openssl
24586 operation happens and succeeds, and you ask if there was an error,
24587 it tells you about the first error. Fun fun.
24588 o Fix a bug that's been lurking since 27 may 03 (!)
24589 When passing back a destroy cell, we would use the wrong circ id.
24590 'Mostly harmless', but still worth fixing.
24591 o Since we don't support truncateds much, don't bother sending them;
24592 just close the circ.
24593 o check for <machine/limits.h> so we build on NetBSD again (I hope).
24594 o don't crash if a conn that sent a begin has suddenly lost its circuit
24595 (this was quite rare).
24598 Changes in version 0.0.6rc1 - 2004-04-25
24599 o We now rotate link (tls context) keys and onion keys.
24600 o CREATE cells now include oaep padding, so you can tell
24601 if you decrypted them correctly.
24602 o Add bandwidthburst to server descriptor.
24603 o Directories now say which dirserver signed them.
24604 o Use a tor_assert macro that logs failed assertions too.
24607 Changes in version 0.0.6pre5 - 2004-04-18
24608 o changes from 0.0.6pre4:
24609 - make tor build on broken freebsd 5.2 installs
24610 - fix a failed assert when you try an intro point, get a nack, and try
24611 a second one and it works.
24612 - when alice uses a port that the hidden service doesn't accept,
24613 it now sends back an end cell (denied by exit policy). otherwise
24614 alice would just have to wait to time out.
24615 - fix another rare bug: when we had tried all the intro
24616 points for a hidden service, we fetched the descriptor
24617 again, but we left our introcirc thinking it had already
24618 sent an intro, so it kept waiting for a response...
24619 - bugfix: when you sleep your hidden-service laptop, as soon
24620 as it wakes up it tries to upload a service descriptor, but
24621 socketpair fails for some reason (localhost not up yet?).
24622 now we simply give up on that upload, and we'll try again later.
24623 i'd still like to find the bug though.
24624 - if an intro circ waiting for an ack dies before getting one, then
24626 - we were reusing stale service descriptors and refetching usable
24630 Changes in version 0.0.6pre4 - 2004-04-14
24631 o changes from 0.0.6pre3:
24632 - when bob fails to connect to the rendezvous point, and his
24633 circ didn't fail because of the rendezvous point itself, then
24634 he retries a couple of times
24635 - we expire introduction and rendezvous circs more thoroughly
24636 (sometimes they were hanging around forever)
24637 - we expire unattached rendezvous streams that have been around
24638 too long (they were sticking around forever).
24639 - fix a measly fencepost error that was crashing everybody with
24643 Changes in version 0.0.6pre3 - 2004-04-14
24644 o changes from 0.0.6pre2:
24645 - make hup work again
24646 - fix some memory leaks for dirservers
24647 - allow more skew in rendezvous descriptor timestamps, to help
24648 handle people like blanu who don't know what time it is
24649 - normal circs are 3 hops, but some rend/intro circs are 4, if
24650 the initiator doesn't get to choose the last hop
24651 - send acks for introductions, so alice can know whether to try
24653 - bob publishes intro points more correctly
24654 o changes from 0.0.5:
24655 - fix an assert trigger that's been plaguing us since the days
24656 of 0.0.2prexx (thanks weasel!)
24657 - retry stream correctly when we fail to connect because of
24658 exit-policy-reject (should try another) or can't-resolve-address
24659 (also should try another, because dns on random internet servers
24661 - when we hup a dirserver and we've *removed* a server from the
24662 approved-routers list, now we remove that server from the
24663 in-memory directories too
24666 Changes in version 0.0.6pre2 - 2004-04-08
24667 o We fixed our base32 implementation. Now it works on all architectures.
24670 Changes in version 0.0.6pre1 - 2004-04-08
24672 - Hidden services and rendezvous points are implemented. Go to
24673 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
24674 hidden services. (This only works via a socks4a proxy such as
24675 Privoxy, and currently it's quite slow.)
24678 Changes in version 0.0.5 - 2004-03-30
24679 [version bump only]
24682 Changes in version 0.0.5rc3 - 2004-03-29
24683 o Install torrc as torrc.sample -- we no longer clobber your
24685 o Re-enable recommendedversion checking (we broke it in rc2, oops)
24686 o Add in a 'notice' log level for things the operator should hear
24687 but that aren't warnings
24690 Changes in version 0.0.5rc2 - 2004-03-29
24691 o Hold socks connection open until reply is flushed (if possible)
24692 o Make exit nodes resolve IPs to IPs immediately, rather than asking
24693 the dns farm to do it.
24694 o Fix c99 aliasing warnings in rephist.c
24695 o Don't include server descriptors that are older than 24 hours in the
24697 o Give socks 'reject' replies their whole 15s to attempt to flush,
24698 rather than seeing the 60s timeout and assuming the flush had failed.
24699 o Clean automake droppings from the cvs repository
24702 Changes in version 0.0.5rc1 - 2004-03-28
24703 o Fix mangled-state bug in directory fetching (was causing sigpipes).
24704 o Only build circuits after we've fetched the directory: clients were
24705 using only the directory servers before they'd fetched a directory.
24706 This also means longer startup time; so it goes.
24707 o Fix an assert trigger where an OP would fail to handshake, and we'd
24708 expect it to have a nickname.
24709 o Work around a tsocks bug: do a socks reject when AP connection dies
24710 early, else tsocks goes into an infinite loop.
24713 Changes in version 0.0.4 - 2004-03-26
24714 o When connecting to a dirserver or OR and the network is down,
24718 Changes in version 0.0.3 - 2004-03-26
24719 o Warn and fail if server chose a nickname with illegal characters
24720 o Port to Solaris and Sparc:
24721 - include missing header fcntl.h
24722 - have autoconf find -lsocket -lnsl automatically
24723 - deal with hardware word alignment
24724 - make uname() work (solaris has a different return convention)
24725 - switch from using signal() to sigaction()
24726 o Preliminary work on reputation system:
24727 - Keep statistics on success/fail of connect attempts; they're published
24728 by kill -USR1 currently.
24729 - Add a RunTesting option to try to learn link state by creating test
24730 circuits, even when SocksPort is off.
24731 - Remove unused open circuits when there are too many.
24734 Changes in version 0.0.2 - 2004-03-19
24735 - Include strlcpy and strlcat for safer string ops
24736 - define INADDR_NONE so we compile (but still not run) on solaris
24739 Changes in version 0.0.2pre27 - 2004-03-14
24741 - Allow internal tor networks (we were rejecting internal IPs,
24742 now we allow them if they're set explicitly).
24743 - And fix a few endian issues.
24746 Changes in version 0.0.2pre26 - 2004-03-14
24748 - If a stream times out after 15s without a connected cell, don't
24749 try that circuit again: try a new one.
24750 - Retry streams at most 4 times. Then give up.
24751 - When a dirserver gets a descriptor from an unknown router, it
24752 logs its fingerprint (so the dirserver operator can choose to
24753 accept it even without mail from the server operator).
24754 - Inform unapproved servers when we reject their descriptors.
24755 - Make tor build on Windows again. It works as a client, who knows
24757 - Clearer instructions in the torrc for how to set up a server.
24758 - Be more efficient about reading fd's when our global token bucket
24759 (used for rate limiting) becomes empty.
24761 - Stop asserting that computers always go forward in time. It's
24763 - When we sent a cell (e.g. destroy) and then marked an OR connection
24764 expired, we might close it before finishing a flush if the other
24765 side isn't reading right then.
24766 - Don't allow dirservers to start if they haven't defined
24767 RecommendedVersions
24768 - We were caching transient dns failures. Oops.
24769 - Prevent servers from publishing an internal IP as their address.
24770 - Address a strcat vulnerability in circuit.c
24773 Changes in version 0.0.2pre25 - 2004-03-04
24775 - Put the OR's IP in its router descriptor, not its fqdn. That way
24776 we'll stop being stalled by gethostbyname for nodes with flaky dns,
24779 - If the user typed in an address that didn't resolve, the server
24783 Changes in version 0.0.2pre24 - 2004-03-03
24785 - Fix an assertion failure in dns.c, where we were trying to dequeue
24786 a pending dns resolve even if it wasn't pending
24787 - Fix a spurious socks5 warning about still trying to write after the
24788 connection is finished.
24789 - Hold certain marked_for_close connections open until they're finished
24790 flushing, rather than losing bytes by closing them too early.
24791 - Correctly report the reason for ending a stream
24792 - Remove some duplicate calls to connection_mark_for_close
24793 - Put switch_id and start_daemon earlier in the boot sequence, so it
24794 will actually try to chdir() to options.DataDirectory
24795 - Make 'make test' exit(1) if a test fails; fix some unit tests
24796 - Make tor fail when you use a config option it doesn't know about,
24797 rather than warn and continue.
24798 - Make --version work
24799 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
24802 Changes in version 0.0.2pre23 - 2004-02-29
24804 - Print a statement when the first circ is finished, so the user
24805 knows it's working.
24806 - If a relay cell is unrecognized at the end of the circuit,
24807 send back a destroy. (So attacks to mutate cells are more
24809 - New config option 'excludenodes' to avoid certain nodes for circuits.
24810 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
24811 so you can collect coredumps there.
24813 - Fix a bug in tls flushing where sometimes data got wedged and
24814 didn't flush until more data got sent. Hopefully this bug was
24815 a big factor in the random delays we were seeing.
24816 - Make 'connected' cells include the resolved IP, so the client
24817 dns cache actually gets populated.
24818 - Disallow changing from ORPort=0 to ORPort>0 on hup.
24819 - When we time-out on a stream and detach from the circuit, send an
24820 end cell down it first.
24821 - Only warn about an unknown router (in exitnodes, entrynodes,
24822 excludenodes) after we've fetched a directory.
24825 Changes in version 0.0.2pre22 - 2004-02-26
24827 - Servers publish less revealing uname information in descriptors.
24828 - More memory tracking and assertions, to crash more usefully when
24830 - If the default torrc isn't there, just use some default defaults.
24831 Plus provide an internal dirservers file if they don't have one.
24832 - When the user tries to use Tor as an http proxy, give them an http
24833 501 failure explaining that we're a socks proxy.
24834 - Dump a new router.desc on hup, to help confused people who change
24835 their exit policies and then wonder why router.desc doesn't reflect
24837 - Clean up the generic tor.sh init script that we ship with.
24839 - If the exit stream is pending on the resolve, and a destroy arrives,
24840 then the stream wasn't getting removed from the pending list. I
24841 think this was the one causing recent server crashes.
24842 - Use a more robust poll on OSX 10.3, since their poll is flaky.
24843 - When it couldn't resolve any dirservers, it was useless from then on.
24844 Now it reloads the RouterFile (or default dirservers) if it has no
24846 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
24847 many users don't even *have* a /usr/local/sbin/.
24850 Changes in version 0.0.2pre21 - 2004-02-18
24852 - There's a ChangeLog file that actually reflects the changelog.
24853 - There's a 'torify' wrapper script, with an accompanying
24854 tor-tsocks.conf, that simplifies the process of using tsocks for
24855 tor. It even has a man page.
24856 - The tor binary gets installed to sbin rather than bin now.
24857 - Retry streams where the connected cell hasn't arrived in 15 seconds
24858 - Clean up exit policy handling -- get the default out of the torrc,
24859 so we can update it without forcing each server operator to fix
24861 - Allow imaps and pop3s in default exit policy
24863 - Prevent picking middleman nodes as the last node in the circuit
24866 Changes in version 0.0.2pre20 - 2004-01-30
24868 - We now have a deb package, and it's in debian unstable. Go to
24869 it, apt-getters. :)
24870 - I've split the TotalBandwidth option into BandwidthRate (how many
24871 bytes per second you want to allow, long-term) and
24872 BandwidthBurst (how many bytes you will allow at once before the cap
24873 kicks in). This better token bucket approach lets you, say, set
24874 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
24875 performance while not exceeding your monthly bandwidth quota.
24876 - Push out a tls record's worth of data once you've got it, rather
24877 than waiting until you've read everything waiting to be read. This
24878 may improve performance by pipelining better. We'll see.
24879 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
24880 from failed circuits (if they haven't been connected yet) and attach
24882 - Expire old streams that haven't managed to connect. Some day we'll
24883 have them reattach to new circuits instead.
24886 - Fix several memory leaks that were causing servers to become bloated
24888 - Fix a few very rare assert triggers. A few more remain.
24889 - Setuid to User _before_ complaining about running as root.
24892 Changes in version 0.0.2pre19 - 2004-01-07
24894 - Fix deadlock condition in dns farm. We were telling a child to die by
24895 closing the parent's file descriptor to him. But newer children were
24896 inheriting the open file descriptor from the parent, and since they
24897 weren't closing it, the socket never closed, so the child never read
24898 eof, so he never knew to exit. Similarly, dns workers were holding
24899 open other sockets, leading to all sorts of chaos.
24900 - New cleaner daemon() code for forking and backgrounding.
24901 - If you log to a file, it now prints an entry at the top of the
24902 logfile so you know it's working.
24903 - The onionskin challenge length was 30 bytes longer than necessary.
24904 - Started to patch up the spec so it's not quite so out of date.
24907 Changes in version 0.0.2pre18 - 2004-01-02
24909 - Fix endian issues with the 'integrity' field in the relay header.
24910 - Fix a potential bug where connections in state
24911 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
24914 Changes in version 0.0.2pre17 - 2003-12-30
24916 - Made --debuglogfile (or any second log file, actually) work.
24917 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
24918 adversary could force us into an infinite loop.
24921 - Each onionskin handshake now includes a hash of the computed key,
24922 to prove the server's identity and help perfect forward secrecy.
24923 - Changed cell size from 256 to 512 bytes (working toward compatibility
24925 - Changed cell length to 2 bytes, and moved it to the relay header.
24926 - Implemented end-to-end integrity checking for the payloads of
24928 - Separated streamid from 'recognized' (otherwise circuits will get
24929 messed up when we try to have streams exit from the middle). We
24930 use the integrity-checking to confirm that a cell is addressed to
24932 - Randomize the initial circid and streamid values, so an adversary who
24933 breaks into a node can't learn how many circuits or streams have
24937 Changes in version 0.0.2pre16 - 2003-12-14
24939 - Fixed a bug that made HUP trigger an assert
24940 - Fixed a bug where a circuit that immediately failed wasn't being
24941 counted as a failed circuit in counting retries.
24944 - Now we close the circuit when we get a truncated cell: otherwise we're
24945 open to an anonymity attack where a bad node in the path truncates
24946 the circuit and then we open streams at him.
24947 - Add port ranges to exit policies
24948 - Add a conservative default exit policy
24949 - Warn if you're running tor as root
24950 - on HUP, retry OR connections and close/rebind listeners
24951 - options.EntryNodes: try these nodes first when picking the first node
24952 - options.ExitNodes: if your best choices happen to include any of
24953 your preferred exit nodes, you choose among just those preferred
24955 - options.ExcludedNodes: nodes that are never picked in path building
24958 Changes in version 0.0.2pre15 - 2003-12-03
24959 o Robustness and bugfixes:
24960 - Sometimes clients would cache incorrect DNS resolves, which would
24961 really screw things up.
24962 - An OP that goes offline would slowly leak all its sockets and stop
24964 - A wide variety of bugfixes in exit node selection, exit policy
24965 handling, and processing pending streams when a new circuit is
24967 - Pick nodes for a path only from those the directory says are up
24968 - Choose randomly from all running dirservers, not always the first one
24969 - Increase allowed http header size for directory fetch.
24970 - Stop writing to stderr (if we're daemonized it will be closed).
24971 - Enable -g always, so cores will be more useful to me.
24972 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
24975 - Wrote a man page. It lists commonly used options.
24978 - Change default loglevel to warn.
24979 - Make PidFile default to null rather than littering in your CWD.
24980 - OnionRouter config option is now obsolete. Instead it just checks
24982 - Moved to a single unified torrc file for both clients and servers.
24985 Changes in version 0.0.2pre14 - 2003-11-29
24986 o Robustness and bugfixes:
24987 - Force the admin to make the DataDirectory himself
24988 - to get ownership/permissions right
24989 - so clients no longer make a DataDirectory and then never use it
24990 - fix bug where a client who was offline for 45 minutes would never
24991 pull down a directory again
24992 - fix (or at least hide really well) the dns assert bug that was
24993 causing server crashes
24994 - warnings and improved robustness wrt clockskew for certs
24995 - use the native daemon(3) to daemonize, when available
24996 - exit if bind() fails
24997 - exit if neither socksport nor orport is defined
24998 - include our own tor_timegm (Win32 doesn't have its own)
24999 - bugfix for win32 with lots of connections
25000 - fix minor bias in PRNG
25001 - make dirserver more robust to corrupt cached directory
25004 - Wrote the design document (woo)
25006 o Circuit building and exit policies:
25007 - Circuits no longer try to use nodes that the directory has told them
25009 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
25010 bitcounts (18.0.0.0/8).
25011 - Make AP connections standby for a circuit if no suitable circuit
25012 exists, rather than failing
25013 - Circuits choose exit node based on addr/port, exit policies, and
25014 which AP connections are standing by
25015 - Bump min pathlen from 2 to 3
25016 - Relay end cells have a payload to describe why the stream ended.
25017 - If the stream failed because of exit policy, try again with a new
25019 - Clients have a dns cache to remember resolved addresses.
25020 - Notice more quickly when we have no working circuits
25023 - APPort is now called SocksPort
25024 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
25026 - RecommendedVersions is now a config variable rather than
25027 hardcoded (for dirservers)
25028 - Reloads config on HUP
25029 - Usage info on -h or --help
25030 - If you set User and Group config vars, it'll setu/gid to them.
25033 Changes in version 0.0.2pre13 - 2003-10-19
25034 o General stability:
25035 - SSL_write no longer fails when it returns WANTWRITE and the number
25036 of bytes in the buf has changed by the next SSL_write call.
25037 - Fix segfault fetching directory when network is down
25038 - Fix a variety of minor memory leaks
25039 - Dirservers reload the fingerprints file on HUP, so I don't have
25040 to take down the network when I approve a new router
25041 - Default server config file has explicit Address line to specify fqdn
25044 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
25045 - Make listener connections not ever alloc bufs
25047 o Autoconf improvements:
25048 - don't clobber an external CFLAGS in ./configure
25049 - Make install now works
25050 - create var/lib/tor on make install
25051 - autocreate a tor.sh initscript to help distribs
25052 - autocreate the torrc and sample-server-torrc with correct paths
25054 o Log files and Daemonizing now work:
25055 - If --DebugLogFile is specified, log to it at -l debug
25056 - If --LogFile is specified, use it instead of commandline
25057 - If --RunAsDaemon is set, tor forks and backgrounds on startup