1 Changes in version 0.2.8.4-rc - 2016-06-15
2 Tor 0.2.8.4-rc is the first release candidate in the Tor 0.2.8 series.
3 If we find no new bugs or regressions here, the first stable 0.2.8
4 release will be identical to it. It has a few small bugfixes against
7 o Major bugfixes (user interface):
8 - Correctly give a warning in the cases where a relay is specified
9 by nickname, and one such relay is found, but it is not officially
10 Named. Fixes bug 19203; bugfix on 0.2.3.1-alpha.
12 o Minor features (build):
13 - Tor now builds once again with the recent OpenSSL 1.1 development
14 branch (tested against 1.1.0-pre5 and 1.1.0-pre6-dev).
16 o Minor features (geoip):
17 - Update geoip and geoip6 to the June 7 2016 Maxmind GeoLite2
20 o Minor bugfixes (compilation):
21 - Cause the unit tests to compile correctly on mingw64 versions that
22 lack sscanf. Fixes bug 19213; bugfix on 0.2.7.1-alpha.
24 o Minor bugfixes (downloading):
25 - Predict more correctly whether we'll be downloading over HTTP when
26 we determine the maximum length of a URL. This should avoid a
27 "BUG" warning about the Squid HTTP proxy and its URL limits. Fixes
31 Changes in version 0.2.8.3-alpha - 2016-05-26
32 Tor 0.2.8.3-alpha resolves several bugs, most of them introduced over
33 the course of the 0.2.8 development cycle. It improves the behavior of
34 directory clients, fixes several crash bugs, fixes a gap in compiler
35 hardening, and allows the full integration test suite to run on
38 o Major bugfixes (security, client, DNS proxy):
39 - Stop a crash that could occur when a client running with DNSPort
40 received a query with multiple address types, and the first
41 address type was not supported. Found and fixed by Scott Dial.
42 Fixes bug 18710; bugfix on 0.2.5.4-alpha.
44 o Major bugfixes (security, compilation):
45 - Correctly detect compiler flags on systems where _FORTIFY_SOURCE
46 is predefined. Previously, our use of -D_FORTIFY_SOURCE would
47 cause a compiler warning, thereby making other checks fail, and
48 needlessly disabling compiler-hardening support. Fixes one case of
49 bug 18841; bugfix on 0.2.3.17-beta. Patch from "trudokal".
51 o Major bugfixes (security, directory authorities):
52 - Fix a crash and out-of-bounds write during authority voting, when
53 the list of relays includes duplicate ed25519 identity keys. Fixes
54 bug 19032; bugfix on 0.2.8.2-alpha.
56 o Major bugfixes (client, bootstrapping):
57 - Check if bootstrap consensus downloads are still needed when the
58 linked connection attaches. This prevents tor making unnecessary
59 begindir-style connections, which are the only directory
60 connections tor clients make since the fix for 18483 was merged.
61 - Fix some edge cases where consensus download connections may not
62 have been closed, even though they were not needed. Related to fix
64 - Make relays retry consensus downloads the correct number of times,
65 rather than the more aggressive client retry count. Fixes part of
67 - Stop downloading consensuses when we have a consensus, even if we
68 don't have all the certificates for it yet. Fixes bug 18809;
69 bugfix on 0.2.8.1-alpha. Patches by arma and teor.
71 o Major bugfixes (directory mirrors):
72 - Decide whether to advertise begindir support in the the same way
73 we decide whether to advertise our DirPort. Allowing these
74 decisions to become out-of-sync led to surprising behavior like
75 advertising begindir support when hibernation made us not
76 advertise a DirPort. Resolves bug 18616; bugfix on 0.2.8.1-alpha.
79 o Major bugfixes (IPv6 bridges, client):
80 - Actually use IPv6 addresses when selecting directory addresses for
81 IPv6 bridges. Fixes bug 18921; bugfix on 0.2.8.1-alpha. Patch
84 o Major bugfixes (key management):
85 - If OpenSSL fails to generate an RSA key, do not retain a dangling
86 pointer to the previous (uninitialized) key value. The impact here
87 should be limited to a difficult-to-trigger crash, if OpenSSL is
88 running an engine that makes key generation failures possible, or
89 if OpenSSL runs out of memory. Fixes bug 19152; bugfix on
90 0.2.1.10-alpha. Found by Yuan Jochen Kang, Suman Jana, and
93 o Major bugfixes (testing):
94 - Fix a bug that would block 'make test-network-all' on systems where
95 IPv6 packets were lost. Fixes bug 19008; bugfix on tor-0.2.7.3-rc.
96 - Avoid "WSANOTINITIALISED" warnings in the unit tests. Fixes bug 18668;
97 bugfix on 0.2.8.1-alpha.
99 o Minor features (clients):
100 - Make clients, onion services, and bridge relays always use an
101 encrypted begindir connection for directory requests. Resolves
102 ticket 18483. Patch by "teor".
104 o Minor features (fallback directory mirrors):
105 - Give each fallback the same weight for client selection; restrict
106 fallbacks to one per operator; report fallback directory detail
107 changes when rebuilding list; add new fallback directory mirrors
108 to the whitelist; update fallback directories based on the latest
109 OnionOO data; and any other minor simplifications and fixes.
110 Closes tasks 17158, 17905, 18749, bug 18689, and fixes part of bug
111 18812 on 0.2.8.1-alpha; patch by "teor".
113 o Minor features (geoip):
114 - Update geoip and geoip6 to the May 4 2016 Maxmind GeoLite2
117 o Minor bugfixes (assert, portability):
118 - Fix an assertion failure in memarea.c on systems where "long" is
119 shorter than the size of a pointer. Fixes bug 18716; bugfix
122 o Minor bugfixes (bootstrap):
123 - Consistently use the consensus download schedule for authority
124 certificates. Fixes bug 18816; bugfix on 0.2.4.13-alpha.
126 o Minor bugfixes (build):
127 - Remove a pair of redundant AM_CONDITIONAL declarations from
128 configure.ac. Fixes one final case of bug 17744; bugfix
130 - Resolve warnings when building on systems that are concerned with
131 signed char. Fixes bug 18728; bugfix on 0.2.7.2-alpha
133 - When libscrypt.h is found, but no libscrypt library can be linked,
134 treat libscrypt as absent. Fixes bug 19161; bugfix
137 o Minor bugfixes (client):
138 - Turn all TestingClientBootstrap* into non-testing torrc options.
139 This changes simply renames them by removing "Testing" in front of
140 them and they do not require TestingTorNetwork to be enabled
141 anymore. Fixes bug 18481; bugfix on 0.2.8.1-alpha.
142 - Make directory node selection more reliable, mainly for IPv6-only
143 clients and clients with few reachable addresses. Fixes bug 18929;
144 bugfix on 0.2.8.1-alpha. Patch by "teor".
146 o Minor bugfixes (controller, microdescriptors):
147 - Make GETINFO dir/status-vote/current/consensus conform to the
148 control specification by returning "551 Could not open cached
149 consensus..." when not caching consensuses. Fixes bug 18920;
150 bugfix on 0.2.2.6-alpha.
152 o Minor bugfixes (crypto, portability):
153 - The SHA3 and SHAKE routines now produce the correct output on Big
154 Endian systems. No code calls either algorithm yet, so this is
155 primarily a build fix. Fixes bug 18943; bugfix on 0.2.8.1-alpha.
156 - Tor now builds again with the recent OpenSSL 1.1 development
157 branch (tested against 1.1.0-pre4 and 1.1.0-pre5-dev). Closes
160 o Minor bugfixes (directories):
161 - When fetching extrainfo documents, compare their SHA256 digests
162 and Ed25519 signing key certificates with the routerinfo that led
163 us to fetch them, rather than with the most recent routerinfo.
164 Otherwise we generate many spurious warnings about mismatches.
165 Fixes bug 17150; bugfix on 0.2.7.2-alpha.
167 o Minor bugfixes (logging):
168 - When we can't generate a signing key because OfflineMasterKey is
169 set, do not imply that we should have been able to load it. Fixes
170 bug 18133; bugfix on 0.2.7.2-alpha.
171 - Stop periodic_event_dispatch() from blasting twelve lines per
172 second at loglevel debug. Fixes bug 18729; fix on 0.2.8.1-alpha.
173 - When rejecting a misformed INTRODUCE2 cell, only log at
174 PROTOCOL_WARN severity. Fixes bug 18761; bugfix on 0.2.8.2-alpha.
176 o Minor bugfixes (pluggable transports):
177 - Avoid reporting a spurious error when we decide that we don't need
178 to terminate a pluggable transport because it has already exited.
179 Fixes bug 18686; bugfix on 0.2.5.5-alpha.
181 o Minor bugfixes (pointer arithmetic):
182 - Fix a bug in memarea_alloc() that could have resulted in remote
183 heap write access, if Tor had ever passed an unchecked size to
184 memarea_alloc(). Fortunately, all the sizes we pass to
185 memarea_alloc() are pre-checked to be less than 128 kilobytes.
186 Fixes bug 19150; bugfix on 0.2.1.1-alpha. Bug found by
189 o Minor bugfixes (relays):
190 - Consider more config options when relays decide whether to
191 regenerate their descriptor. Fixes more of bug 12538; bugfix
193 - Resolve some edge cases where we might launch an ORPort
194 reachability check even when DisableNetwork is set. Noticed while
195 fixing bug 18616; bugfix on 0.2.3.9-alpha.
197 o Minor bugfixes (statistics):
198 - We now include consensus downloads via IPv6 in our directory-
199 request statistics. Fixes bug 18460; bugfix on 0.2.3.14-alpha.
201 o Minor bugfixes (testing):
202 - Allow directories in small networks to bootstrap by skipping
203 DirPort checks when the consensus has no exits. Fixes bug 19003;
204 bugfix on 0.2.8.1-alpha. Patch by teor.
205 - Fix a small memory leak that would occur when the
206 TestingEnableCellStatsEvent option was turned on. Fixes bug 18673;
207 bugfix on 0.2.5.2-alpha.
209 o Minor bugfixes (time handling):
210 - When correcting a corrupt 'struct tm' value, fill in the tm_wday
211 field. Otherwise, our unit tests crash on Windows. Fixes bug
212 18977; bugfix on 0.2.2.25-alpha.
215 - Document the contents of the 'datadir/keys' subdirectory in the
216 manual page. Closes ticket 17621.
217 - Stop recommending use of nicknames to identify relays in our
218 MapAddress documentation. Closes ticket 18312.
221 Changes in version 0.2.8.2-alpha - 2016-03-28
222 Tor 0.2.8.2-alpha is the second alpha in its series. It fixes numerous
223 bugs in earlier versions of Tor, including some that prevented
224 authorities using Tor 0.2.7.x from running correctly. IPv6 and
225 directory support should also be much improved.
227 o New system requirements:
228 - Tor no longer supports versions of OpenSSL with a broken
229 implementation of counter mode. (This bug was present in OpenSSL
230 1.0.0, and was fixed in OpenSSL 1.0.0a.) Tor still detects, but no
231 longer runs with, these versions.
232 - Tor no longer attempts to support platforms where the "time_t"
233 type is unsigned. (To the best of our knowledge, only OpenVMS does
234 this, and Tor has never actually built on OpenVMS.) Closes
236 - Tor now uses Autoconf version 2.63 or later, and Automake 1.11 or
237 later (released in 2008 and 2009 respectively). If you are
238 building Tor from the git repository instead of from the source
239 distribution, and your tools are older than this, you will need to
240 upgrade. Closes ticket 17732.
242 o Major bugfixes (security, pointers):
243 - Avoid a difficult-to-trigger heap corruption attack when extending
244 a smartlist to contain over 16GB of pointers. Fixes bug 18162;
245 bugfix on 0.1.1.11-alpha, which fixed a related bug incompletely.
246 Reported by Guido Vranken.
248 o Major bugfixes (bridges, pluggable transports):
249 - Modify the check for OR connections to private addresses. Allow
250 bridges on private addresses, including pluggable transports that
251 ignore the (potentially private) address in the bridge line. Fixes
252 bug 18517; bugfix on 0.2.8.1-alpha. Reported by gk, patch by teor.
254 o Major bugfixes (compilation):
255 - Repair hardened builds under the clang compiler. Previously, our
256 use of _FORTIFY_SOURCE would conflict with clang's address
257 sanitizer. Fixes bug 14821; bugfix on 0.2.5.4-alpha.
259 o Major bugfixes (crash on shutdown):
260 - Correctly handle detaching circuits from muxes when shutting down.
261 Fixes bug 18116; bugfix on 0.2.8.1-alpha.
262 - Fix an assert-on-exit bug related to counting memory usage in
263 rephist.c. Fixes bug 18651; bugfix on 0.2.8.1-alpha.
265 o Major bugfixes (crash on startup):
266 - Fix a segfault during startup: If a Unix domain socket was
267 configured as listener (such as a ControlSocket or a SocksPort
268 "unix:" socket), and tor was started as root but not configured to
269 switch to another user, tor would segfault while trying to string
270 compare a NULL value. Fixes bug 18261; bugfix on 0.2.8.1-alpha.
273 o Major bugfixes (dns proxy mode, crash):
274 - Avoid crashing when running as a DNS proxy. Fixes bug 16248;
275 bugfix on 0.2.0.1-alpha. Patch from "cypherpunks".
277 o Major bugfixes (relays, bridge clients):
278 - Ensure relays always allow IPv4 OR and Dir connections. Ensure
279 bridge clients use the address configured in the bridge line.
280 Fixes bug 18348; bugfix on 0.2.8.1-alpha. Reported by sysrqb,
283 o Major bugfixes (voting):
284 - Actually enable support for authorities to match routers by their
285 Ed25519 identities. Previously, the code had been written, but
286 some debugging code that had accidentally been left in the
287 codebase made it stay turned off. Fixes bug 17702; bugfix
289 - When collating votes by Ed25519 identities, authorities now
290 include a "NoEdConsensus" flag if the ed25519 value (or lack
291 thereof) for a server does not reflect the majority consensus.
292 Related to bug 17668; bugfix on 0.2.7.2-alpha.
293 - When generating a vote with keypinning disabled, never include two
294 entries for the same ed25519 identity. This bug was causing
295 authorities to generate votes that they could not parse when a
296 router violated key pinning by changing its RSA identity but
297 keeping its Ed25519 identity. Fixes bug 17668; fixes part of bug
298 18318. Bugfix on 0.2.7.2-alpha.
300 o Minor features (security, win32):
301 - Set SO_EXCLUSIVEADDRUSE on Win32 to avoid a local port-stealing
302 attack. Fixes bug 18123; bugfix on all tor versions. Patch
305 o Minor features (bug-resistance):
306 - Make Tor survive errors involving connections without a
307 corresponding event object. Previously we'd fail with an
308 assertion; now we produce a log message. Related to bug 16248.
310 o Minor features (build):
311 - Detect systems with FreeBSD-derived kernels (such as GNU/kFreeBSD)
312 as having possible IPFW support. Closes ticket 18448. Patch from
315 o Minor features (code hardening):
316 - Use tor_snprintf() and tor_vsnprintf() even in external and low-
317 level code, to harden against accidental failures to NUL-
318 terminate. Part of ticket 17852. Patch from jsturgix. Found
321 o Minor features (crypto):
322 - Validate the hard-coded Diffie-Hellman parameters and ensure that
323 p is a safe prime, and g is a suitable generator. Closes
326 o Minor features (geoip):
327 - Update geoip and geoip6 to the March 3 2016 Maxmind GeoLite2
330 o Minor features (hidden service directory):
331 - Streamline relay-side hsdir handling: when relays consider whether
332 to accept an uploaded hidden service descriptor, they no longer
333 check whether they are one of the relays in the network that is
334 "supposed" to handle that descriptor. Implements ticket 18332.
336 o Minor features (IPv6):
337 - Add ClientPreferIPv6DirPort, which is set to 0 by default. If set
338 to 1, tor prefers IPv6 directory addresses.
339 - Add ClientUseIPv4, which is set to 1 by default. If set to 0, tor
340 avoids using IPv4 for client OR and directory connections.
341 - Try harder to obey the IP version restrictions "ClientUseIPv4 0",
342 "ClientUseIPv6 0", "ClientPreferIPv6ORPort", and
343 "ClientPreferIPv6DirPort". Closes ticket 17840; patch by teor.
345 o Minor features (linux seccomp2 sandbox):
346 - Reject attempts to change our Address with "Sandbox 1" enabled.
347 Changing Address with Sandbox turned on would never actually work,
348 but previously it would fail in strange and confusing ways. Found
351 o Minor features (robustness):
352 - Exit immediately with an error message if the code attempts to use
353 Libevent without having initialized it. This should resolve some
354 frequently-made mistakes in our unit tests. Closes ticket 18241.
356 o Minor features (unix domain sockets):
357 - Add a new per-socket option, RelaxDirModeCheck, to allow creating
358 Unix domain sockets without checking the permissions on the parent
359 directory. (Tor checks permissions by default because some
360 operating systems only check permissions on the parent directory.
361 However, some operating systems do look at permissions on the
362 socket, and tor's default check is unneeded.) Closes ticket 18458.
365 o Minor bugfixes (exit policies, security):
366 - Refresh an exit relay's exit policy when interface addresses
367 change. Previously, tor only refreshed the exit policy when the
368 configured external address changed. Fixes bug 18208; bugfix on
369 0.2.7.3-rc. Patch by teor.
371 o Minor bugfixes (security, hidden services):
372 - Prevent hidden services connecting to client-supplied rendezvous
373 addresses that are reserved as internal or multicast. Fixes bug
374 8976; bugfix on 0.2.3.21-rc. Patch by dgoulet and teor.
376 o Minor bugfixes (build):
377 - Do not link the unit tests against both the testing and non-
378 testing versions of the static libraries. Fixes bug 18490; bugfix
380 - Avoid spurious failures from configure files related to calling
381 exit(0) in TOR_SEARCH_LIBRARY. Fixes bug 18625; bugfix on
382 0.2.0.1-alpha. Patch from "cypherpunks".
383 - Silence spurious clang-scan warnings in the ed25519_donna code by
384 explicitly initializing some objects. Fixes bug 18384; bugfix on
385 0.2.7.2-alpha. Patch by teor.
387 o Minor bugfixes (client, bootstrap):
388 - Count receipt of new microdescriptors as progress towards
389 bootstrapping. Previously, with EntryNodes set, Tor might not
390 successfully repopulate the guard set on bootstrapping. Fixes bug
391 16825; bugfix on 0.2.3.1-alpha.
393 o Minor bugfixes (code correctness):
394 - Update to the latest version of Trunnel, which tries harder to
395 avoid generating code that can invoke memcpy(p,NULL,0). Bug found
396 by clang address sanitizer. Fixes bug 18373; bugfix
399 o Minor bugfixes (configuration):
400 - Fix a tiny memory leak when parsing a port configuration ending in
401 ":auto". Fixes bug 18374; bugfix on 0.2.3.3-alpha.
403 o Minor bugfixes (containers):
404 - If we somehow attempt to construct a heap with more than
405 1073741822 elements, avoid an integer overflow when maintaining
406 the heap property. Fixes bug 18296; bugfix on 0.1.2.1-alpha.
408 o Minor bugfixes (correctness):
409 - Fix a bad memory handling bug that would occur if we had queued a
410 cell on a channel's incoming queue. Fortunately, we can't actually
411 queue a cell like that as our code is constructed today, but it's
412 best to avoid this kind of error, even if there isn't any code
413 that triggers it today. Fixes bug 18570; bugfix on 0.2.4.4-alpha.
415 o Minor bugfixes (directory):
416 - When generating a URL for a directory server on an IPv6 address,
417 wrap the IPv6 address in square brackets. Fixes bug 18051; bugfix
418 on 0.2.3.9-alpha. Patch from Malek.
420 o Minor bugfixes (fallback directory mirrors):
421 - When requesting extrainfo descriptors from a trusted directory
422 server, check whether it is an authority or a fallback directory
423 which supports extrainfo descriptors. Fixes bug 18489; bugfix on
424 0.2.4.7-alpha. Reported by atagar, patch by teor.
426 o Minor bugfixes (hidden service, client):
427 - Handle the case where the user makes several fast consecutive
428 requests to the same .onion address. Previously, the first six
429 requests would each trigger a descriptor fetch, each picking a
430 directory (there are 6 overall) and the seventh one would fail
431 because no directories were left, thereby triggering a close on
432 all current directory connections asking for the hidden service.
433 The solution here is to not close the connections if we have
434 pending directory fetches. Fixes bug 15937; bugfix
437 o Minor bugfixes (hidden service, control port):
438 - Add the onion address to the HS_DESC event for the UPLOADED action
439 both on success or failure. It was previously hardcoded with
440 UNKNOWN. Fixes bug 16023; bugfix on 0.2.7.2-alpha.
442 o Minor bugfixes (hidden service, directory):
443 - Bridges now refuse "rendezvous2" (hidden service descriptor)
444 publish attempts. Suggested by ticket 18332.
446 o Minor bugfixes (linux seccomp2 sandbox):
447 - Allow the setrlimit syscall, and the prlimit and prlimit64
448 syscalls, which some libc implementations use under the hood.
449 Fixes bug 15221; bugfix on 0.2.5.1-alpha.
450 - Avoid a 10-second delay when starting as a client with "Sandbox 1"
451 enabled and no DNS resolvers configured. This should help TAILS
452 start up faster. Fixes bug 18548; bugfix on 0.2.5.1-alpha.
453 - Fix the sandbox's interoperability with unix domain sockets under
454 setuid. Fixes bug 18253; bugfix on 0.2.8.1-alpha.
456 o Minor bugfixes (logging):
457 - When logging information about an unparsable networkstatus vote or
458 consensus, do not say "vote" when we mean consensus. Fixes bug
459 18368; bugfix on 0.2.0.8-alpha.
460 - Scrub service name in "unrecognized service ID" log messages.
461 Fixes bug 18600; bugfix on 0.2.4.11-alpha.
462 - Downgrade logs and backtraces about IP versions to info-level.
463 Only log backtraces once each time tor runs. Assists in diagnosing
464 bug 18351; bugfix on 0.2.8.1-alpha. Reported by sysrqb and
465 Christian, patch by teor.
467 o Minor bugfixes (memory safety):
468 - Avoid freeing an uninitialized pointer when opening a socket fails
469 in get_interface_addresses_ioctl(). Fixes bug 18454; bugfix on
470 0.2.3.11-alpha. Reported by toralf and "cypherpunks", patch
472 - Correctly duplicate addresses in get_interface_address6_list().
473 Fixes bug 18454; bugfix on 0.2.8.1-alpha. Reported by toralf,
474 patch by "cypherpunks".
475 - Fix a memory leak in tor-gencert. Fixes part of bug 18672; bugfix
477 - Fix a memory leak in "tor --list-fingerprint". Fixes part of bug
478 18672; bugfix on 0.2.5.1-alpha.
480 o Minor bugfixes (private directory):
481 - Prevent a race condition when creating private directories. Fixes
482 part of bug 17852; bugfix on 0.0.2pre13. Part of ticket 17852.
483 Patch from jsturgix. Found with Flawfinder.
485 o Minor bugfixes (test networks, IPv6):
486 - Allow internal IPv6 addresses in descriptors in test networks.
487 Fixes bug 17153; bugfix on 0.2.3.16-alpha. Patch by teor, reported
490 o Minor bugfixes (testing):
491 - We no longer disable assertions in the unit tests when coverage is
492 enabled. Instead, we require you to say --disable-asserts-in-tests
493 to the configure script if you need assertions disabled in the
494 unit tests (for example, if you want to perform branch coverage).
495 Fixes bug 18242; bugfix on 0.2.7.1-alpha.
497 o Minor bugfixes (time parsing):
498 - Avoid overflow in tor_timegm when parsing dates in and after 2038
499 on platforms with 32-bit time_t. Fixes bug 18479; bugfix on
500 0.0.2pre14. Patch by teor.
502 o Minor bugfixes (tor-gencert):
503 - Correctly handle the case where an authority operator enters a
504 passphrase but sends an EOF before sending a newline. Fixes bug
505 17443; bugfix on 0.2.0.20-rc. Found by junglefowl.
507 o Code simplification and refactoring:
508 - Quote all the string interpolations in configure.ac -- even those
509 which we are pretty sure can't contain spaces. Closes ticket
510 17744. Patch from zerosion.
511 - Remove specialized code for non-inplace AES_CTR. 99% of our AES is
512 inplace, so there's no need to have a separate implementation for
513 the non-inplace code. Closes ticket 18258. Patch from Malek.
514 - Simplify return types for some crypto functions that can't
515 actually fail. Patch from Hassan Alsibyani. Closes ticket 18259.
518 - Change build messages to refer to "Fedora" instead of "Fedora
519 Core", and "dnf" instead of "yum". Closes tickets 18459 and 18426.
520 Patches from "icanhasaccount" and "cypherpunks".
523 - We no longer maintain an internal freelist in memarea.c.
524 Allocators should be good enough to make this code unnecessary,
525 and it's doubtful that it ever had any performance benefit.
528 - Fix several warnings from clang's address sanitizer produced in
530 - Treat backtrace test failures as expected on FreeBSD until we
531 solve bug 17808. Closes ticket 18204.
534 Changes in version 0.2.8.1-alpha - 2016-02-04
535 Tor 0.2.8.1-alpha is the first alpha release in its series. It
536 includes numerous small features and bugfixes against previous Tor
537 versions, and numerous small infrastructure improvements. The most
538 notable features are a set of improvements to the directory subsystem.
540 o Major features (security, Linux):
541 - When Tor starts as root on Linux and is told to switch user ID, it
542 can now retain the capability to bind to low ports. By default,
543 Tor will do this only when it's switching user ID and some low
544 ports have been configured. You can change this behavior with the
545 new option KeepBindCapabilities. Closes ticket 8195.
547 o Major features (directory system):
548 - When bootstrapping multiple consensus downloads at a time, use the
549 first one that starts downloading, and close the rest. This
550 reduces failures when authorities or fallback directories are slow
551 or down. Together with the code for feature 15775, this feature
552 should reduces failures due to fallback churn. Implements ticket
553 4483. Patch by "teor". Implements IPv4 portions of proposal 210 by
554 "mikeperry" and "teor".
555 - Include a trial list of default fallback directories, based on an
556 opt-in survey of suitable relays. Doing this should make clients
557 bootstrap more quickly and reliably, and reduce the load on the
558 directory authorities. Closes ticket 15775. Patch by "teor".
559 Candidates identified using an OnionOO script by "weasel", "teor",
560 "gsathya", and "karsten".
561 - Previously only relays that explicitly opened a directory port
562 (DirPort) accepted directory requests from clients. Now all
563 relays, with and without a DirPort, accept and serve tunneled
564 directory requests that they receive through their ORPort. You can
565 disable this behavior using the new DirCache option. Closes
569 - Update the V3 identity key for the dannenberg directory authority:
570 it was changed on 18 November 2015. Closes task 17906. Patch
573 o Minor features (security, clock):
574 - Warn when the system clock appears to move back in time (when the
575 state file was last written in the future). Tor doesn't know that
576 consensuses have expired if the clock is in the past. Patch by
577 "teor". Implements ticket 17188.
579 o Minor features (security, exit policies):
580 - ExitPolicyRejectPrivate now rejects more private addresses by
581 default. Specifically, it now rejects the relay's outbound bind
582 addresses (if configured), and the relay's configured port
583 addresses (such as ORPort and DirPort). Fixes bug 17027; bugfix on
584 0.2.0.11-alpha. Patch by "teor".
586 o Minor features (security, memory erasure):
587 - Set the unused entries in a smartlist to NULL. This helped catch
588 a (harmless) bug, and shouldn't affect performance too much.
589 Implements ticket 17026.
590 - Use SecureMemoryWipe() function to securely clean memory on
591 Windows. Previously we'd use OpenSSL's OPENSSL_cleanse() function.
592 Implements feature 17986.
593 - Use explicit_bzero or memset_s when present. Previously, we'd use
594 OpenSSL's OPENSSL_cleanse() function. Closes ticket 7419; patches
595 from <logan@hackers.mu> and <selven@hackers.mu>.
596 - Make memwipe() do nothing when passed a NULL pointer or buffer of
597 zero size. Check size argument to memwipe() for underflow. Fixes
598 bug 18089; bugfix on 0.2.3.25 and 0.2.4.6-alpha. Reported by "gk",
601 o Minor features (security, RNG):
602 - Adjust Tor's use of OpenSSL's RNG APIs so that they absolutely,
603 positively are not allowed to fail. Previously we depended on
604 internal details of OpenSSL's behavior. Closes ticket 17686.
605 - Never use the system entropy output directly for anything besides
606 seeding the PRNG. When we want to generate important keys, instead
607 of using system entropy directly, we now hash it with the PRNG
608 stream. This may help resist certain attacks based on broken OS
609 entropy implementations. Closes part of ticket 17694.
610 - Use modern system calls (like getentropy() or getrandom()) to
611 generate strong entropy on platforms that have them. Closes
614 o Minor features (accounting):
615 - Added two modes to the AccountingRule option: One for limiting
616 only the number of bytes sent ("AccountingRule out"), and one for
617 limiting only the number of bytes received ("AccountingRule in").
618 Closes ticket 15989; patch from "unixninja92".
620 o Minor features (build):
621 - Since our build process now uses "make distcheck", we no longer
622 force "make dist" to depend on "make check". Closes ticket 17893;
623 patch from "cypherpunks."
624 - Tor now builds successfully with the recent OpenSSL 1.1
625 development branch, and with the latest LibreSSL. Closes tickets
626 17549, 17921, and 17984.
628 o Minor features (controller):
629 - Adds the FallbackDir entries to 'GETINFO config/defaults'. Closes
630 tickets 16774 and 17817. Patch by George Tankersley.
631 - New 'GETINFO hs/service/desc/id/' command to retrieve a hidden
632 service descriptor from a service's local hidden service
633 descriptor cache. Closes ticket 14846.
634 - Add 'GETINFO exit-policy/reject-private/[default,relay]', so
635 controllers can examine the the reject rules added by
636 ExitPolicyRejectPrivate. This makes it easier for stem to display
639 o Minor features (crypto):
640 - Add SHA512 support to crypto.c. Closes ticket 17663; patch from
642 - Add SHA3 and SHAKE support to crypto.c. Closes ticket 17783.
643 - When allocating a digest state object, allocate no more space than
644 we actually need. Previously, we would allocate as much space as
645 the state for the largest algorithm would need. This change saves
646 up to 672 bytes per circuit. Closes ticket 17796.
647 - Improve performance when hashing non-multiple of 8 sized buffers,
648 based on Andrew Moon's public domain SipHash-2-4 implementation.
649 Fixes bug 17544; bugfix on 0.2.5.3-alpha.
651 o Minor features (directory downloads):
652 - Wait for busy authorities and fallback directories to become non-
653 busy when bootstrapping. (A similar change was made in 6c443e987d
654 for directory caches chosen from the consensus.) Closes ticket
655 17864; patch by "teor".
656 - Add UseDefaultFallbackDirs, which enables any hard-coded fallback
657 directory mirrors. The default is 1; set it to 0 to disable
658 fallbacks. Implements ticket 17576. Patch by "teor".
660 o Minor features (geoip):
661 - Update geoip and geoip6 to the January 5 2016 Maxmind GeoLite2
664 o Minor features (IPv6):
665 - Add an argument 'ipv6=address:orport' to the DirAuthority and
666 FallbackDir torrc options, to specify an IPv6 address for an
667 authority or fallback directory. Add hard-coded ipv6 addresses for
668 directory authorities that have them. Closes ticket 17327; patch
669 from Nick Mathewson and "teor".
670 - Add address policy assume_action support for IPv6 addresses.
671 - Limit IPv6 mask bits to 128.
672 - Warn when comparing against an AF_UNSPEC address in a policy, it's
673 almost always a bug. Closes ticket 17863; patch by "teor".
674 - Allow users to configure directory authorities and fallback
675 directory servers with IPv6 addresses and ORPorts. Resolves
677 - routerset_parse now accepts IPv6 literal addresses. Fixes bug
678 17060; bugfix on 0.2.1.3-alpha. Patch by "teor".
679 - Make tor_ersatz_socketpair work on IPv6-only systems. Fixes bug
680 17638; bugfix on 0.0.2pre8. Patch by "teor".
682 o Minor features (logging):
683 - When logging to syslog, allow a tag to be added to the syslog
684 identity (the string prepended to every log message). The tag can
685 be configured with SyslogIdentityTag and defaults to none. Setting
686 it to "foo" will cause logs to be tagged as "Tor-foo". Closes
689 o Minor features (portability):
690 - Use timingsafe_memcmp() where available. Closes ticket 17944;
691 patch from <logan@hackers.mu>.
693 o Minor features (relay, address discovery):
694 - Add a family argument to get_interface_addresses_raw() and
695 subfunctions to make network interface address interogation more
696 efficient. Now Tor can specifically ask for IPv4, IPv6 or both
697 types of interfaces from the operating system. Resolves
699 - When get_interface_address6_list(.,AF_UNSPEC,.) is called and
700 fails to enumerate interface addresses using the platform-specific
701 API, have it rely on the UDP socket fallback technique to try and
702 find out what IP addresses (both IPv4 and IPv6) our machine has.
703 Resolves ticket 17951.
705 o Minor features (replay cache):
706 - The replay cache now uses SHA256 instead of SHA1. Implements
707 feature 8961. Patch by "teor", issue reported by "rransom".
709 o Minor features (unix file permissions):
710 - Defer creation of Unix sockets until after setuid. This avoids
711 needing CAP_CHOWN and CAP_FOWNER when using systemd's
712 CapabilityBoundingSet, or chown and fowner when using SELinux.
713 Implements part of ticket 17562. Patch from Jamie Nguyen.
714 - If any directory created by Tor is marked as group readable, the
715 filesystem group is allowed to be either the default GID or the
716 root user. Allowing root to read the DataDirectory prevents the
717 need for CAP_READ_SEARCH when using systemd's
718 CapabilityBoundingSet, or dac_read_search when using SELinux.
719 Implements part of ticket 17562. Patch from Jamie Nguyen.
720 - Introduce a new DataDirectoryGroupReadable option. If it is set to
721 1, the DataDirectory will be made readable by the default GID.
722 Implements part of ticket 17562. Patch from Jamie Nguyen.
724 o Minor bugfixes (accounting):
725 - The max bandwidth when using 'AccountRule sum' is now correctly
726 logged. Fixes bug 18024; bugfix on 0.2.6.1-alpha. Patch
729 o Minor bugfixes (code correctness):
730 - When closing an entry connection, generate a warning if we should
731 have sent an end cell for it but we haven't. Fixes bug 17876;
732 bugfix on 0.2.3.2-alpha.
733 - Assert that allocated memory held by the reputation code is freed
734 according to its internal counters. Fixes bug 17753; bugfix
736 - Assert when the TLS contexts fail to initialize. Fixes bug 17683;
739 o Minor bugfixes (compilation):
740 - Mark all object files that include micro-revision.i as depending
741 on it, so as to make parallel builds more reliable. Fixes bug
742 17826; bugfix on 0.2.5.1-alpha.
743 - Don't try to use the pthread_condattr_setclock() function unless
744 it actually exists. Fixes compilation on NetBSD-6.x. Fixes bug
745 17819; bugfix on 0.2.6.3-alpha.
746 - Fix backtrace compilation on FreeBSD. Fixes bug 17827; bugfix
748 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
749 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
750 - Fix search for libevent libraries on OpenBSD (and other systems
751 that install libevent 1 and libevent 2 in parallel). Fixes bug
752 16651; bugfix on 0.1.0.7-rc. Patch from "rubiate".
753 - Isolate environment variables meant for tests from the rest of the
754 build system. Fixes bug 17818; bugfix on 0.2.7.3-rc.
755 - Replace usage of 'INLINE' with 'inline'. Fixes bug 17804; bugfix
757 - Remove config.log only from make distclean, not from make clean.
758 Fixes bug 17924; bugfix on 0.2.4.1-alpha.
760 o Minor bugfixes (crypto):
761 - Check the return value of HMAC() and assert on failure. Fixes bug
762 17658; bugfix on 0.2.3.6-alpha. Patch by "teor".
764 o Minor bugfixes (fallback directories):
765 - Mark fallbacks as "too busy" when they return a 503 response,
766 rather than just marking authorities. Fixes bug 17572; bugfix on
767 0.2.4.7-alpha. Patch by "teor".
769 o Minor bugfixes (IPv6):
770 - Update the limits in max_dl_per_request for IPv6 address length.
771 Fixes bug 17573; bugfix on 0.2.1.5-alpha.
773 o Minor bugfixes (linux seccomp2 sandbox):
774 - Fix a crash when using offline master ed25519 keys with the Linux
775 seccomp2 sandbox enabled. Fixes bug 17675; bugfix on 0.2.7.3-rc.
777 o Minor bugfixes (logging):
778 - In log messages that include a function name, use __FUNCTION__
779 instead of __PRETTY_FUNCTION__. In GCC, these are synonymous, but
780 with clang __PRETTY_FUNCTION__ has extra information we don't
781 need. Fixes bug 16563; bugfix on 0.0.2pre8. Fix by Tom van
783 - Remove needless quotes from a log message about unparseable
784 addresses. Fixes bug 17843; bugfix on 0.2.3.3-alpha.
786 o Minor bugfixes (portability):
787 - Remove an #endif from configure.ac so that we correctly detect the
788 presence of in6_addr.s6_addr32. Fixes bug 17923; bugfix
791 o Minor bugfixes (relays):
792 - Check that both the ORPort and DirPort (if present) are reachable
793 before publishing a relay descriptor. Otherwise, relays publish a
794 descriptor with DirPort 0 when the DirPort reachability test takes
795 longer than the ORPort reachability test. Fixes bug 18050; bugfix
796 on 0.1.0.1-rc. Reported by "starlight", patch by "teor".
798 o Minor bugfixes (relays, hidden services):
799 - Refuse connection requests to private OR addresses unless
800 ExtendAllowPrivateAddresses is set. Previously, tor would connect,
801 then refuse to send any cells to a private address. Fixes bugs
802 17674 and 8976; bugfix on 0.2.3.21-rc. Patch by "teor".
804 o Minor bugfixes (safe logging):
805 - When logging a malformed hostname received through socks4, scrub
806 it if SafeLogging says we should. Fixes bug 17419; bugfix
809 o Minor bugfixes (statistics code):
810 - Consistently check for overflow in round_*_to_next_multiple_of
811 functions, and add unit tests with additional and maximal values.
812 Fixes part of bug 13192; bugfix on 0.2.2.1-alpha.
813 - Handle edge cases in the laplace functions: avoid division by
814 zero, avoid taking the log of zero, and silence clang type
815 conversion warnings using round and trunc. Add unit tests for edge
816 cases with maximal values. Fixes part of bug 13192; bugfix
819 o Minor bugfixes (testing):
820 - The test for log_heartbeat was incorrectly failing in timezones
821 with non-integer offsets. Instead of comparing the end of the time
822 string against a constant, compare it to the output of
823 format_local_iso_time when given the correct input. Fixes bug
824 18039; bugfix on 0.2.5.4-alpha.
825 - Make unit tests pass on IPv6-only systems, and systems without
826 localhost addresses (like some FreeBSD jails). Fixes bug 17632;
827 bugfix on 0.2.7.3-rc. Patch by "teor".
828 - Fix a memory leak in the ntor test. Fixes bug 17778; bugfix
830 - Check the full results of SHA256 and SHA512 digests in the unit
831 tests. Bugfix on 0.2.2.4-alpha. Patch by "teor".
833 o Code simplification and refactoring:
834 - Move logging of redundant policy entries in
835 policies_parse_exit_policy_internal into its own function. Closes
836 ticket 17608; patch from "juce".
837 - Extract the more complicated parts of circuit_mark_for_close()
838 into a new function that we run periodically before circuits are
839 freed. This change removes more than half of the functions
840 currently in the "blob". Closes ticket 17218.
841 - Clean up a little duplicated code in
842 crypto_expand_key_material_TAP(). Closes ticket 17587; patch
844 - Decouple the list of streams waiting to be attached to circuits
845 from the overall connection list. This change makes it possible to
846 attach streams quickly while simplifying Tor's callgraph and
847 avoiding O(N) scans of the entire connection list. Closes
849 - When a direct directory request fails immediately on launch,
850 instead of relaunching that request from inside the code that
851 launches it, instead mark the connection for teardown. This change
852 simplifies Tor's callback and prevents the directory-request
853 launching code from invoking itself recursively. Closes
855 - Remove code for configuring OpenSSL dynamic locks; OpenSSL doesn't
856 use them. Closes ticket 17926.
859 - Add a description of the correct use of the '--keygen' command-
860 line option. Closes ticket 17583; based on text by 's7r'.
861 - Document the minimum HeartbeatPeriod value. Closes ticket 15638.
862 - Explain actual minima for BandwidthRate. Closes ticket 16382.
863 - Fix a minor formatting typo in the manpage. Closes ticket 17791.
864 - Mention torspec URL in the manpage and point the reader to it
865 whenever we mention a document that belongs in torspce. Fixes
869 - Remove client-side support for connecting to Tor relays running
870 versions of Tor before 0.2.3.6-alpha. These relays didn't support
871 the v3 TLS handshake protocol, and are no longer allowed on the
872 Tor network. Implements the client side of ticket 11150. Based on
873 patches by Tom van der Woerdt.
876 - Add unit tests to check for common RNG failure modes, such as
877 returning all zeroes, identical values, or incrementing values
878 (OpenSSL's rand_predictable feature). Patch by "teor".
879 - Log more information when the backtrace tests fail. Closes ticket
880 17892. Patch from "cypherpunks."
881 - Always test both ed25519 backends, so that we can be sure that our
882 batch-open replacement code works. Part of ticket 16794.
883 - Cover dns_resolve_impl() in dns.c with unit tests. Implements a
884 portion of ticket 16831.
885 - More unit tests for compat_libevent.c, procmon.c, tortls.c,
886 util_format.c, directory.c, and options_validate.c. Closes tickets
887 17075, 17082, 17084, 17003, and 17076 respectively. Patches from
889 - Unit tests for directory_handle_command_get. Closes ticket 17004.
890 Patch from Reinaldo de Souza Jr.
893 Changes in version 0.2.7.6 - 2015-12-10
894 Tor version 0.2.7.6 fixes a major bug in entry guard selection, as
895 well as a minor bug in hidden service reliability.
897 o Major bugfixes (guard selection):
898 - Actually look at the Guard flag when selecting a new directory
899 guard. When we implemented the directory guard design, we
900 accidentally started treating all relays as if they have the Guard
901 flag during guard selection, leading to weaker anonymity and worse
902 performance. Fixes bug 17772; bugfix on 0.2.4.8-alpha. Discovered
905 o Minor features (geoip):
906 - Update geoip and geoip6 to the December 1 2015 Maxmind GeoLite2
909 o Minor bugfixes (compilation):
910 - When checking for net/pfvar.h, include netinet/in.h if possible.
911 This fixes transparent proxy detection on OpenBSD. Fixes bug
912 17551; bugfix on 0.1.2.1-alpha. Patch from "rubiate".
913 - Fix a compilation warning with Clang 3.6: Do not check the
914 presence of an address which can never be NULL. Fixes bug 17781.
916 o Minor bugfixes (correctness):
917 - When displaying an IPv6 exit policy, include the mask bits
918 correctly even when the number is greater than 31. Fixes bug
919 16056; bugfix on 0.2.4.7-alpha. Patch from "gturner".
920 - The wrong list was used when looking up expired intro points in a
921 rend service object, causing what we think could be reachability
922 issues for hidden services, and triggering a BUG log. Fixes bug
923 16702; bugfix on 0.2.7.2-alpha.
924 - Fix undefined behavior in the tor_cert_checksig function. Fixes
925 bug 17722; bugfix on 0.2.7.2-alpha.
928 Changes in version 0.2.7.5 - 2015-11-20
929 The Tor 0.2.7 release series is dedicated to the memory of Tor user
930 and privacy advocate Caspar Bowden (1961-2015). Caspar worked
931 tirelessly to advocate human rights regardless of national borders,
932 and oppose the encroachments of mass surveillance. He opposed national
933 exceptionalism, he brought clarity to legal and policy debates, he
934 understood and predicted the impact of mass surveillance on the world,
935 and he laid the groundwork for resisting it. While serving on the Tor
936 Project's board of directors, he brought us his uncompromising focus
937 on technical excellence in the service of humankind. Caspar was an
938 inimitable force for good and a wonderful friend. He was kind,
939 humorous, generous, gallant, and believed we should protect one
940 another without exception. We honor him here for his ideals, his
941 efforts, and his accomplishments. Please honor his memory with works
942 that would make him proud.
944 Tor 0.2.7.5 is the first stable release in the Tor 0.2.7 series.
946 The 0.2.7 series adds a more secure identity key type for relays,
947 improves cryptography performance, resolves several longstanding
948 hidden-service performance issues, improves controller support for
949 hidden services, and includes small bugfixes and performance
950 improvements throughout the program. This release series also includes
951 more tests than before, and significant simplifications to which parts
952 of Tor invoke which others.
954 (This release contains no code changes since 0.2.7.4-rc.)
957 Changes in version 0.2.7.4-rc - 2015-10-21
958 Tor 0.2.7.4-rc is the second release candidate in the 0.2.7 series. It
959 fixes some important memory leaks, and a scary-looking (but mostly
960 harmless in practice) invalid-read bug. It also has a few small
961 bugfixes, notably fixes for compilation and portability on different
962 platforms. If no further significant bounds are found, the next
963 release will the the official stable release.
965 o Major bugfixes (security, correctness):
966 - Fix an error that could cause us to read 4 bytes before the
967 beginning of an openssl string. This bug could be used to cause
968 Tor to crash on systems with unusual malloc implementations, or
969 systems with unusual hardening installed. Fixes bug 17404; bugfix
972 o Major bugfixes (correctness):
973 - Fix a use-after-free bug in validate_intro_point_failure(). Fixes
974 bug 17401; bugfix on 0.2.7.3-rc.
976 o Major bugfixes (memory leaks):
977 - Fix a memory leak in ed25519 batch signature checking. Fixes bug
978 17398; bugfix on 0.2.6.1-alpha.
979 - Fix a memory leak in rend_cache_failure_entry_free(). Fixes bug
980 17402; bugfix on 0.2.7.3-rc.
981 - Fix a memory leak when reading an expired signing key from disk.
982 Fixes bug 17403; bugfix on 0.2.7.2-rc.
984 o Minor features (geoIP):
985 - Update geoip and geoip6 to the October 9 2015 Maxmind GeoLite2
988 o Minor bugfixes (compilation):
989 - Repair compilation with the most recent (unreleased, alpha)
990 vesions of OpenSSL 1.1. Fixes part of ticket 17237.
991 - Fix an integer overflow warning in test_crypto_slow.c. Fixes bug
992 17251; bugfix on 0.2.7.2-alpha.
993 - Fix compilation of sandbox.c with musl-libc. Fixes bug 17347;
994 bugfix on 0.2.5.1-alpha. Patch from 'jamestk'.
996 o Minor bugfixes (portability):
997 - Use libexecinfo on FreeBSD to enable backtrace support. Fixes
998 part of bug 17151; bugfix on 0.2.5.2-alpha. Patch from
1001 o Minor bugfixes (sandbox):
1002 - Add the "hidserv-stats" filename to our sandbox filter for the
1003 HiddenServiceStatistics option to work properly. Fixes bug 17354;
1004 bugfix on 0.2.6.2-alpha. Patch from David Goulet.
1006 o Minor bugfixes (testing):
1007 - Add unit tests for get_interface_address* failure cases. Fixes bug
1008 17173; bugfix on 0.2.7.3-rc. Patch by fk/teor.
1009 - Fix breakage when running 'make check' with BSD make. Fixes bug
1010 17154; bugfix on 0.2.7.3-rc. Patch by Marcin Cieślak.
1011 - Make the get_ifaddrs_* unit tests more tolerant of different
1012 network configurations. (Don't assume every test box has an IPv4
1013 address, and don't assume every test box has a non-localhost
1014 address.) Fixes bug 17255; bugfix on 0.2.7.3-rc. Patch by "teor".
1015 - Skip backtrace tests when backtrace support is not compiled in.
1016 Fixes part of bug 17151; bugfix on 0.2.7.1-alpha. Patch from
1020 - Fix capitalization of SOCKS in sample torrc. Closes ticket 15609.
1021 - Note that HiddenServicePorts can take a unix domain socket. Closes
1025 Changes in version 0.2.7.3-rc - 2015-09-25
1026 Tor 0.2.7.3-rc is the first release candidate in the 0.2.7 series. It
1027 contains numerous usability fixes for Ed25519 keys, safeguards against
1028 several misconfiguration problems, significant simplifications to
1029 Tor's callgraph, and numerous bugfixes and small features.
1031 This is the most tested release of Tor to date. The unit tests cover
1032 39.40% of the code, and the integration tests (accessible with "make
1033 test-full-online", requiring stem and chutney and a network
1034 connection) raise the coverage to 64.49%.
1036 o Major features (security, hidden services):
1037 - Hidden services, if using the EntryNodes option, are required to
1038 use more than one EntryNode, in order to avoid a guard discovery
1039 attack. (This would only affect people who had configured hidden
1040 services and manually specified the EntryNodes option with a
1041 single entry-node. The impact was that it would be easy to
1042 remotely identify the guard node used by such a hidden service.
1043 See ticket for more information.) Fixes ticket 14917.
1045 o Major features (Ed25519 keys, keypinning):
1046 - The key-pinning option on directory authorities is now advisory-
1047 only by default. In a future version, or when the AuthDirPinKeys
1048 option is set, pins are enforced again. Disabling key-pinning
1049 seemed like a good idea so that we can survive the fallout of any
1050 usability problems associated with Ed25519 keys. Closes
1053 o Major features (Ed25519 performance):
1054 - Improve the speed of Ed25519 operations and Curve25519 keypair
1055 generation when built targeting 32 bit x86 platforms with SSE2
1056 available. Implements ticket 16535.
1057 - Improve the runtime speed of Ed25519 signature verification by
1058 using Ed25519-donna's batch verification support. Implements
1061 o Major features (performance testing):
1062 - The test-network.sh script now supports performance testing.
1063 Requires corresponding chutney performance testing changes. Patch
1064 by "teor". Closes ticket 14175.
1066 o Major features (relay, Ed25519):
1067 - Significant usability improvements for Ed25519 key management. Log
1068 messages are better, and the code can recover from far more
1069 failure conditions. Thanks to "s7r" for reporting and diagnosing
1071 - Add a new OfflineMasterKey option to tell Tor never to try loading
1072 or generating a secret Ed25519 identity key. You can use this in
1073 combination with tor --keygen to manage offline and/or encrypted
1074 Ed25519 keys. Implements ticket 16944.
1075 - Add a --newpass option to allow changing or removing the
1076 passphrase of an encrypted key with tor --keygen. Implements part
1078 - On receiving a HUP signal, check to see whether the Ed25519
1079 signing key has changed, and reload it if so. Closes ticket 16790.
1081 o Major bugfixes (relay, Ed25519):
1082 - Avoid crashing on 'tor --keygen'. Fixes bug 16679; bugfix on
1083 0.2.7.2-alpha. Reported by "s7r".
1084 - Improve handling of expired signing keys with offline master keys.
1085 Fixes bug 16685; bugfix on 0.2.7.2-alpha. Reported by "s7r".
1087 o Minor features (client-side privacy):
1088 - New KeepAliveIsolateSOCKSAuth option to indefinitely extend circuit
1089 lifespan when IsolateSOCKSAuth and streams with SOCKS
1090 authentication are attached to the circuit. This allows
1091 applications like TorBrowser to manage circuit lifetime on their
1092 own. Implements feature 15482.
1093 - When logging malformed hostnames from SOCKS5 requests, respect
1094 SafeLogging configuration. Fixes bug 16891; bugfix on 0.1.1.16-rc.
1096 o Minor features (compilation):
1097 - Give a warning as early as possible when trying to build with an
1098 unsupported OpenSSL version. Closes ticket 16901.
1099 - Fail during configure if we're trying to build against an OpenSSL
1100 built without ECC support. Fixes bug 17109, bugfix on 0.2.7.1-alpha
1101 which started requiring ECC.
1103 o Minor features (geoip):
1104 - Update geoip and geoip6 to the September 3 2015 Maxmind GeoLite2
1107 o Minor features (hidden services):
1108 - Relays need to have the Fast flag to get the HSDir flag. As this
1109 is being written, we'll go from 2745 HSDirs down to 2342, a ~14%
1110 drop. This change should make some attacks against the hidden
1111 service directory system harder. Fixes ticket 15963.
1112 - Turn on hidden service statistics collection by setting the torrc
1113 option HiddenServiceStatistics to "1" by default. (This keeps
1114 track only of the fraction of traffic used by hidden services, and
1115 the total number of hidden services in existence.) Closes
1117 - Client now uses an introduction point failure cache to know when
1118 to fetch or keep a descriptor in their cache. Previously, failures
1119 were recorded implicitly, but not explicitly remembered. Closes
1122 o Minor features (testing, authorities, documentation):
1123 - New TestingDirAuthVote{Exit,Guard,HSDir}IsStrict flags to
1124 explicitly manage consensus flags in testing networks. Patch by
1125 "robgjansen", modified by "teor". Implements part of ticket 14882.
1127 o Minor bugfixes (security, exit policies):
1128 - ExitPolicyRejectPrivate now also rejects the relay's published
1129 IPv6 address (if any), and any publicly routable IPv4 or IPv6
1130 addresses on any local interfaces. ticket 17027. Patch by "teor".
1131 Fixes bug 17027; bugfix on 0.2.0.11-alpha.
1133 o Minor bug fixes (torrc exit policies):
1134 - In torrc, "accept6 *" and "reject6 *" ExitPolicy lines now only
1135 produce IPv6 wildcard addresses. Previously they would produce
1136 both IPv4 and IPv6 wildcard addresses. Patch by "teor". Fixes part
1137 of bug 16069; bugfix on 0.2.4.7-alpha.
1138 - When parsing torrc ExitPolicies, we now warn for a number of cases
1139 where the user's intent is likely to differ from Tor's actual
1140 behavior. These include: using an IPv4 address with an accept6 or
1141 reject6 line; using "private" on an accept6 or reject6 line; and
1142 including any ExitPolicy lines after accept *:* or reject *:*.
1143 Related to ticket 16069.
1144 - When parsing torrc ExitPolicies, we now issue an info-level
1145 message when expanding an "accept/reject *" line to include both
1146 IPv4 and IPv6 wildcard addresses. Related to ticket 16069.
1147 - In each instance above, usage advice is provided to avoid the
1148 message. Resolves ticket 16069. Patch by "teor". Fixes part of bug
1149 16069; bugfix on 0.2.4.7-alpha.
1151 o Minor bugfixes (authority):
1152 - Don't assign "HSDir" to a router if it isn't Valid and Running.
1153 Fixes bug 16524; bugfix on 0.2.7.2-alpha.
1154 - Downgrade log messages about Ed25519 key issues if they are in old
1155 cached router descriptors. Fixes part of bug 16286; bugfix
1157 - When we find an Ed25519 key issue in a cached descriptor, stop
1158 saying the descriptor was just "uploaded". Fixes another part of
1159 bug 16286; bugfix on 0.2.7.2-alpha.
1161 o Minor bugfixes (control port):
1162 - Repair a warning and a spurious result when getting the maximum
1163 number of file descriptors from the controller. Fixes bug 16697;
1164 bugfix on 0.2.7.2-alpha.
1166 o Minor bugfixes (correctness):
1167 - When calling channel_free_list(), avoid calling smartlist_remove()
1168 while inside a FOREACH loop. This partially reverts commit
1169 17356fe7fd96af where the correct SMARTLIST_DEL_CURRENT was
1170 incorrectly removed. Fixes bug 16924; bugfix on 0.2.4.4-alpha.
1172 o Minor bugfixes (documentation):
1173 - Advise users on how to configure separate IPv4 and IPv6 exit
1174 policies in the manpage and sample torrcs. Related to ticket 16069.
1175 - Fix the usage message of tor-resolve(1) so that it no longer lists
1176 the removed -F option. Fixes bug 16913; bugfix on 0.2.2.28-beta.
1177 - Fix an error in the manual page and comments for
1178 TestingDirAuthVoteHSDir[IsStrict], which suggested that a HSDir
1179 required "ORPort connectivity". While this is true, it is in no
1180 way unique to the HSDir flag. Of all the flags, only HSDirs need a
1181 DirPort configured in order for the authorities to assign that
1182 particular flag. Patch by "teor". Fixed as part of 14882; bugfix
1185 o Minor bugfixes (Ed25519):
1186 - Fix a memory leak when reading router descriptors with expired
1187 Ed25519 certificates. Fixes bug 16539; bugfix on 0.2.7.2-alpha.
1189 o Minor bugfixes (linux seccomp2 sandbox):
1190 - Allow bridge authorities to run correctly under the seccomp2
1191 sandbox. Fixes bug 16964; bugfix on 0.2.5.1-alpha.
1192 - Allow routers with ed25519 keys to run correctly under the
1193 seccomp2 sandbox. Fixes bug 16965; bugfix on 0.2.7.2-alpha.
1195 o Minor bugfixes (open file limit):
1196 - Fix set_max_file_descriptors() to set by default the max open file
1197 limit to the current limit when setrlimit() fails. Fixes bug
1198 16274; bugfix on 0.2.0.10-alpha. Patch by dgoulet.
1200 o Minor bugfixes (portability):
1201 - Try harder to normalize the exit status of the Tor process to the
1202 standard-provided range. Fixes bug 16975; bugfix on every version
1204 - Check correctly for Windows socket errors in the workqueue
1205 backend. Fixes bug 16741; bugfix on 0.2.6.3-alpha.
1206 - Fix the behavior of crypto_rand_time_range() when told to consider
1207 times before 1970. (These times were possible when running in a
1208 simulated network environment where time()'s output starts at
1209 zero.) Fixes bug 16980; bugfix on 0.2.7.1-alpha.
1210 - Restore correct operation of TLS client-cipher detection on
1211 OpenSSL 1.1. Fixes bug 14047; bugfix on 0.2.7.2-alpha.
1213 o Minor bugfixes (relay):
1214 - Ensure that worker threads actually exit when a fatal error or
1215 shutdown is indicated. This fix doesn't currently affect the
1216 behavior of Tor, because Tor workers never indicates fatal error
1217 or shutdown except in the unit tests. Fixes bug 16868; bugfix
1219 - Unblock threads before releasing the work queue mutex to ensure
1220 predictable scheduling behavior. Fixes bug 16644; bugfix
1223 o Code simplification and refactoring:
1224 - Change the function that's called when we need to retry all
1225 downloads so that it only reschedules the downloads to happen
1226 immediately, rather than launching them all at once itself. This
1227 further simplifies Tor's callgraph.
1228 - Move some format-parsing functions out of crypto.c and
1229 crypto_curve25519.c into crypto_format.c and/or util_format.c.
1230 - Move the client-only parts of init_keys() into a separate
1231 function. Closes ticket 16763.
1232 - Simplify the microdesc_free() implementation so that it no longer
1233 appears (to code analysis tools) to potentially invoke a huge
1234 suite of other microdesc functions.
1235 - Simply the control graph further by deferring the inner body of
1236 directory_all_unreachable() into a callback. Closes ticket 16762.
1237 - Treat the loss of an owning controller as equivalent to a SIGTERM
1238 signal. This removes a tiny amount of duplicated code, and
1239 simplifies our callgraph. Closes ticket 16788.
1240 - When generating an event to send to the controller, we no longer
1241 put the event over the network immediately. Instead, we queue
1242 these events, and use a Libevent callback to deliver them. This
1243 change simplifies Tor's callgraph by reducing the number of
1244 functions from which all other Tor functions are reachable. Closes
1246 - Wrap Windows-only C files inside '#ifdef _WIN32' so that tools
1247 that try to scan or compile every file on Unix won't decide that
1249 - Remove the unused "nulterminate" argument from buf_pullup().
1252 - Recommend a 40 GB example AccountingMax in torrc.sample rather
1253 than a 4 GB max. Closes ticket 16742.
1254 - Include the TUNING document in our source tarball. It is referred
1255 to in the ChangeLog and an error message. Fixes bug 16929; bugfix
1259 - The internal pure-C tor-fw-helper tool is now removed from the Tor
1260 distribution, in favor of the pure-Go clone available from
1261 https://gitweb.torproject.org/tor-fw-helper.git/ . The libraries
1262 used by the C tor-fw-helper are not, in our opinion, very
1263 confidence- inspiring in their secure-programming techniques.
1264 Closes ticket 13338.
1265 - Remove the code that would try to aggressively flush controller
1266 connections while writing to them. This code was introduced in
1267 0.1.2.7-alpha, in order to keep output buffers from exceeding
1268 their limits. But there is no longer a maximum output buffer size,
1269 and flushing data in this way caused some undesirable recursions
1270 in our call graph. Closes ticket 16480.
1273 - Make "bridges+hs" the default test network. This tests almost all
1274 tor functionality during make test-network, while allowing tests
1275 to succeed on non-IPv6 systems. Requires chutney commit 396da92 in
1276 test-network-bridges-hs. Closes tickets 16945 (tor) and 16946
1277 (chutney). Patches by "teor".
1278 - Autodetect CHUTNEY_PATH if the chutney and Tor sources are side-
1279 by-side in the same parent directory. Closes ticket 16903. Patch
1281 - Use environment variables rather than autoconf substitutions to
1282 send variables from the build system to the test scripts. This
1283 change should be easier to maintain, and cause 'make distcheck' to
1284 work better than before. Fixes bug 17148.
1285 - Add a new set of callgraph analysis scripts that use clang to
1286 produce a list of which Tor functions are reachable from which
1287 other Tor functions. We're planning to use these to help simplify
1288 our code structure by identifying illogical dependencies.
1289 - Add new 'test-full' and 'test-full-online' targets to run all
1290 tests, including integration tests with stem and chutney.
1291 - Make the test-workqueue test work on Windows by initializing the
1292 network before we begin.
1293 - New make target (make test-network-all) to run multiple applicable
1294 chutney test cases. Patch from Teor; closes 16953.
1295 - Unit test dns_resolve(), dns_clip_ttl() and dns_get_expiry_ttl()
1296 functions in dns.c. Implements a portion of ticket 16831.
1297 - When building Tor with testing coverage enabled, run Chutney tests
1298 (if any) using the 'tor-cov' coverage binary.
1299 - When running test-network or test-stem, check for the absence of
1300 stem/chutney before doing any build operations.
1303 Changes in version 0.2.7.2-alpha - 2015-07-27
1304 This, the second alpha in the Tor 0.2.7 series, has a number of new
1305 features, including a way to manually pick the number of introduction
1306 points for hidden services, and the much stronger Ed25519 signing key
1307 algorithm for regular Tor relays (including support for encrypted
1308 offline identity keys in the new algorithm).
1310 Support for Ed25519 on relays is currently limited to signing router
1311 descriptors; later alphas in this series will extend Ed25519 key
1312 support to more parts of the Tor protocol.
1314 o Major features (Ed25519 identity keys, Proposal 220):
1315 - All relays now maintain a stronger identity key, using the Ed25519
1316 elliptic curve signature format. This master key is designed so
1317 that it can be kept offline. Relays also generate an online
1318 signing key, and a set of other Ed25519 keys and certificates.
1319 These are all automatically regenerated and rotated as needed.
1320 Implements part of ticket 12498.
1321 - Directory authorities now vote on Ed25519 identity keys along with
1322 RSA1024 keys. Implements part of ticket 12498.
1323 - Directory authorities track which Ed25519 identity keys have been
1324 used with which RSA1024 identity keys, and do not allow them to
1325 vary freely. Implements part of ticket 12498.
1326 - Microdescriptors now include Ed25519 identity keys. Implements
1327 part of ticket 12498.
1328 - Add support for offline encrypted Ed25519 master keys. To use this
1329 feature on your tor relay, run "tor --keygen" to make a new master
1330 key (or to make a new signing key if you already have a master
1331 key). Closes ticket 13642.
1333 o Major features (Hidden services):
1334 - Add the torrc option HiddenServiceNumIntroductionPoints, to
1335 specify a fixed number of introduction points. Its maximum value
1336 is 10 and default is 3. Using this option can increase a hidden
1337 service's reliability under load, at the cost of making it more
1338 visible that the hidden service is facing extra load. Closes
1340 - Remove the adaptive algorithm for choosing the number of
1341 introduction points, which used to change the number of
1342 introduction points (poorly) depending on the number of
1343 connections the HS sees. Closes ticket 4862.
1345 o Major features (onion key cross-certification):
1346 - Relay descriptors now include signatures of their own identity
1347 keys, made using the TAP and ntor onion keys. These signatures
1348 allow relays to prove ownership of their own onion keys. Because
1349 of this change, microdescriptors will no longer need to include
1350 RSA identity keys. Implements proposal 228; closes ticket 12499.
1352 o Major features (performance):
1353 - Improve the runtime speed of Ed25519 operations by using the
1354 public-domain Ed25519-donna by Andrew M. ("floodyberry").
1355 Implements ticket 16467.
1356 - Improve the runtime speed of the ntor handshake by using an
1357 optimized curve25519 basepoint scalarmult implementation from the
1358 public-domain Ed25519-donna by Andrew M. ("floodyberry"), based on
1359 ideas by Adam Langley. Implements ticket 9663.
1361 o Major bugfixes (client-side privacy, also in 0.2.6.9):
1362 - Properly separate out each SOCKSPort when applying stream
1363 isolation. The error occurred because each port's session group
1364 was being overwritten by a default value when the listener
1365 connection was initialized. Fixes bug 16247; bugfix on
1366 0.2.6.3-alpha. Patch by "jojelino".
1368 o Major bugfixes (hidden service clients, stability, also in 0.2.6.10):
1369 - Stop refusing to store updated hidden service descriptors on a
1370 client. This reverts commit 9407040c59218 (which indeed fixed bug
1371 14219, but introduced a major hidden service reachability
1372 regression detailed in bug 16381). This is a temporary fix since
1373 we can live with the minor issue in bug 14219 (it just results in
1374 some load on the network) but the regression of 16381 is too much
1375 of a setback. First-round fix for bug 16381; bugfix
1378 o Major bugfixes (hidden services):
1379 - When cannibalizing a circuit for an introduction point, always
1380 extend to the chosen exit node (creating a 4 hop circuit).
1381 Previously Tor would use the current circuit exit node, which
1382 changed the original choice of introduction point, and could cause
1383 the hidden service to skip excluded introduction points or
1384 reconnect to a skipped introduction point. Fixes bug 16260; bugfix
1387 o Major bugfixes (open file limit):
1388 - The open file limit wasn't checked before calling
1389 tor_accept_socket_nonblocking(), which would make Tor exceed the
1390 limit. Now, before opening a new socket, Tor validates the open
1391 file limit just before, and if the max has been reached, return an
1392 error. Fixes bug 16288; bugfix on 0.1.1.1-alpha.
1394 o Major bugfixes (stability, also in 0.2.6.10):
1395 - Stop crashing with an assertion failure when parsing certain kinds
1396 of malformed or truncated microdescriptors. Fixes bug 16400;
1397 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1398 by "cypherpunks_backup".
1399 - Stop random client-side assertion failures that could occur when
1400 connecting to a busy hidden service, or connecting to a hidden
1401 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1404 o Minor features (directory authorities, security, also in 0.2.6.9):
1405 - The HSDir flag given by authorities now requires the Stable flag.
1406 For the current network, this results in going from 2887 to 2806
1407 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1408 attack by raising the effort for a relay to become Stable to
1409 require at the very least 7 days, while maintaining the 96 hours
1410 uptime requirement for HSDir. Implements ticket 8243.
1412 o Minor features (client):
1413 - Relax the validation of hostnames in SOCKS5 requests, allowing the
1414 character '_' to appear, in order to cope with domains observed in
1415 the wild that are serving non-RFC compliant records. Resolves
1417 - Relax the validation done to hostnames in SOCKS5 requests, and
1418 allow a single trailing '.' to cope with clients that pass FQDNs
1419 using that syntax to explicitly indicate that the domain name is
1420 fully-qualified. Fixes bug 16674; bugfix on 0.2.6.2-alpha.
1421 - Add GroupWritable and WorldWritable options to unix-socket based
1422 SocksPort and ControlPort options. These options apply to a single
1423 socket, and override {Control,Socks}SocketsGroupWritable. Closes
1426 o Minor features (control protocol):
1427 - Support network-liveness GETINFO key and NETWORK_LIVENESS event in
1428 the control protocol. Resolves ticket 15358.
1430 o Minor features (directory authorities):
1431 - Directory authorities no longer vote against the "Fast", "Stable",
1432 and "HSDir" flags just because they were going to vote against
1433 "Running": if the consensus turns out to be that the router was
1434 running, then the authority's vote should count. Patch from Peter
1435 Retzlaff; closes issue 8712.
1437 o Minor features (geoip, also in 0.2.6.10):
1438 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1439 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1441 o Minor features (hidden services):
1442 - Add the new options "HiddenServiceMaxStreams" and
1443 "HiddenServiceMaxStreamsCloseCircuit" to allow hidden services to
1444 limit the maximum number of simultaneous streams per circuit, and
1445 optionally tear down the circuit when the limit is exceeded. Part
1448 o Minor features (portability):
1449 - Use C99 variadic macros when the compiler is not GCC. This avoids
1450 failing compilations on MSVC, and fixes a log-file-based race
1451 condition in our old workarounds. Original patch from Gisle Vanem.
1453 o Minor bugfixes (compilation, also in 0.2.6.9):
1454 - Build with --enable-systemd correctly when libsystemd is
1455 installed, but systemd is not. Fixes bug 16164; bugfix on
1456 0.2.6.3-alpha. Patch from Peter Palfrader.
1458 o Minor bugfixes (controller):
1459 - Add the descriptor ID in each HS_DESC control event. It was
1460 missing, but specified in control-spec.txt. Fixes bug 15881;
1461 bugfix on 0.2.5.2-alpha.
1463 o Minor bugfixes (crypto error-handling, also in 0.2.6.10):
1464 - Check for failures from crypto_early_init, and refuse to continue.
1465 A previous typo meant that we could keep going with an
1466 uninitialized crypto library, and would have OpenSSL initialize
1467 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1468 when implementing ticket 4900. Patch by "teor".
1470 o Minor bugfixes (hidden services):
1471 - Fix a crash when reloading configuration while at least one
1472 configured and one ephemeral hidden service exists. Fixes bug
1473 16060; bugfix on 0.2.7.1-alpha.
1474 - Avoid crashing with a double-free bug when we create an ephemeral
1475 hidden service but adding it fails for some reason. Fixes bug
1476 16228; bugfix on 0.2.7.1-alpha.
1478 o Minor bugfixes (Linux seccomp2 sandbox):
1479 - Use the sandbox in tor_open_cloexec whether or not O_CLOEXEC is
1480 defined. Patch by "teor". Fixes bug 16515; bugfix on 0.2.3.1-alpha.
1482 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.10):
1483 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1484 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1485 on 0.2.6.3-alpha. Patch from "teor".
1487 o Minor bugfixes (Linux seccomp2 sandbox, also in 0.2.6.9):
1488 - Fix sandboxing to work when running as a relay, by allowing the
1489 renaming of secret_id_key, and allowing the eventfd2 and futex
1490 syscalls. Fixes bug 16244; bugfix on 0.2.6.1-alpha. Patch by
1492 - Allow systemd connections to work with the Linux seccomp2 sandbox
1493 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1496 o Minor bugfixes (relay):
1497 - Fix a rarely-encountered memory leak when failing to initialize
1498 the thread pool. Fixes bug 16631; bugfix on 0.2.6.3-alpha. Patch
1501 o Minor bugfixes (systemd):
1502 - Fix an accidental formatting error that broke the systemd
1503 configuration file. Fixes bug 16152; bugfix on 0.2.7.1-alpha.
1504 - Tor's systemd unit file no longer contains extraneous spaces.
1505 These spaces would sometimes confuse tools like deb-systemd-
1506 helper. Fixes bug 16162; bugfix on 0.2.5.5-alpha.
1508 o Minor bugfixes (tests):
1509 - Use the configured Python executable when running test-stem-full.
1510 Fixes bug 16470; bugfix on 0.2.7.1-alpha.
1512 o Minor bugfixes (tests, also in 0.2.6.9):
1513 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1514 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1516 o Minor bugfixes (threads, comments):
1517 - Always initialize return value in compute_desc_id in rendcommon.c
1518 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1519 - Check for NULL values in getinfo_helper_onions(). Patch by "teor".
1520 Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1521 - Remove undefined directive-in-macro in test_util_writepid clang
1522 3.7 complains that using a preprocessor directive inside a macro
1523 invocation in test_util_writepid in test_util.c is undefined.
1524 Patch by "teor". Fixes part of bug 16115; bugfix on 0.2.7.1-alpha.
1526 o Code simplification and refactoring:
1527 - Define WINVER and _WIN32_WINNT centrally, in orconfig.h, in order
1528 to ensure they remain consistent and visible everywhere.
1529 - Remove some vestigial workarounds for the MSVC6 compiler. We
1530 haven't supported that in ages.
1531 - The link authentication code has been refactored for better
1532 testability and reliability. It now uses code generated with the
1533 "trunnel" binary encoding generator, to reduce the risk of bugs
1534 due to programmer error. Done as part of ticket 12498.
1537 - Include a specific and (hopefully) accurate documentation of the
1538 torrc file's meta-format in doc/torrc_format.txt. This is mainly
1539 of interest to people writing programs to parse or generate torrc
1540 files. This document is not a commitment to long-term
1541 compatibility; some aspects of the current format are a bit
1542 ridiculous. Closes ticket 2325.
1545 - Tor no longer supports copies of OpenSSL that are missing support
1546 for Elliptic Curve Cryptography. (We began using ECC when
1547 available in 0.2.4.8-alpha, for more safe and efficient key
1548 negotiation.) In particular, support for at least one of P256 or
1549 P224 is now required, with manual configuration needed if only
1550 P224 is available. Resolves ticket 16140.
1551 - Tor no longer supports versions of OpenSSL before 1.0. (If you are
1552 on an operating system that has not upgraded to OpenSSL 1.0 or
1553 later, and you compile Tor from source, you will need to install a
1554 more recent OpenSSL to link Tor against.) These versions of
1555 OpenSSL are still supported by the OpenSSL, but the numerous
1556 cryptographic improvements in later OpenSSL releases makes them a
1557 clear choice. Resolves ticket 16034.
1558 - Remove the HidServDirectoryV2 option. Now all relays offer to
1559 store hidden service descriptors. Related to 16543.
1560 - Remove the VoteOnHidServDirectoriesV2 option, since all
1561 authorities have long set it to 1. Closes ticket 16543.
1564 - Document use of coverity, clang static analyzer, and clang dynamic
1565 undefined behavior and address sanitizers in doc/HACKING. Include
1566 detailed usage instructions in the blacklist. Patch by "teor".
1567 Closes ticket 15817.
1568 - The link authentication protocol code now has extensive tests.
1569 - The relay descriptor signature testing code now has
1571 - The test_workqueue program now runs faster, and is enabled by
1572 default as a part of "make check".
1573 - Now that OpenSSL has its own scrypt implementation, add an unit
1574 test that checks for interoperability between libscrypt_scrypt()
1575 and OpenSSL's EVP_PBE_scrypt() so that we could not use libscrypt
1576 and rely on EVP_PBE_scrypt() whenever possible. Resolves
1580 Changes in version 0.2.6.10 - 2015-07-12
1581 Tor version 0.2.6.10 fixes some significant stability and hidden
1582 service client bugs, bulletproofs the cryptography init process, and
1583 fixes a bug when using the sandbox code with some older versions of
1584 Linux. Everyone running an older version, especially an older version
1585 of 0.2.6, should upgrade.
1587 o Major bugfixes (hidden service clients, stability):
1588 - Stop refusing to store updated hidden service descriptors on a
1589 client. This reverts commit 9407040c59218 (which indeed fixed bug
1590 14219, but introduced a major hidden service reachability
1591 regression detailed in bug 16381). This is a temporary fix since
1592 we can live with the minor issue in bug 14219 (it just results in
1593 some load on the network) but the regression of 16381 is too much
1594 of a setback. First-round fix for bug 16381; bugfix
1597 o Major bugfixes (stability):
1598 - Stop crashing with an assertion failure when parsing certain kinds
1599 of malformed or truncated microdescriptors. Fixes bug 16400;
1600 bugfix on 0.2.6.1-alpha. Found by "torkeln"; fix based on a patch
1601 by "cypherpunks_backup".
1602 - Stop random client-side assertion failures that could occur when
1603 connecting to a busy hidden service, or connecting to a hidden
1604 service while a NEWNYM is in progress. Fixes bug 16013; bugfix
1607 o Minor features (geoip):
1608 - Update geoip to the June 3 2015 Maxmind GeoLite2 Country database.
1609 - Update geoip6 to the June 3 2015 Maxmind GeoLite2 Country database.
1611 o Minor bugfixes (crypto error-handling):
1612 - Check for failures from crypto_early_init, and refuse to continue.
1613 A previous typo meant that we could keep going with an
1614 uninitialized crypto library, and would have OpenSSL initialize
1615 its own PRNG. Fixes bug 16360; bugfix on 0.2.5.2-alpha, introduced
1616 when implementing ticket 4900. Patch by "teor".
1618 o Minor bugfixes (Linux seccomp2 sandbox):
1619 - Allow pipe() and pipe2() syscalls in the seccomp2 sandbox: we need
1620 these when eventfd2() support is missing. Fixes bug 16363; bugfix
1621 on 0.2.6.3-alpha. Patch from "teor".
1624 Changes in version 0.2.6.9 - 2015-06-11
1625 Tor 0.2.6.9 fixes a regression in the circuit isolation code, increases the
1626 requirements for receiving an HSDir flag, and addresses some other small
1627 bugs in the systemd and sandbox code. Clients using circuit isolation
1628 should upgrade; all directory authorities should upgrade.
1630 o Major bugfixes (client-side privacy):
1631 - Properly separate out each SOCKSPort when applying stream
1632 isolation. The error occurred because each port's session group was
1633 being overwritten by a default value when the listener connection
1634 was initialized. Fixes bug 16247; bugfix on 0.2.6.3-alpha. Patch
1637 o Minor feature (directory authorities, security):
1638 - The HSDir flag given by authorities now requires the Stable flag.
1639 For the current network, this results in going from 2887 to 2806
1640 HSDirs. Also, it makes it harder for an attacker to launch a sybil
1641 attack by raising the effort for a relay to become Stable which
1642 takes at the very least 7 days to do so and by keeping the 96
1643 hours uptime requirement for HSDir. Implements ticket 8243.
1645 o Minor bugfixes (compilation):
1646 - Build with --enable-systemd correctly when libsystemd is
1647 installed, but systemd is not. Fixes bug 16164; bugfix on
1648 0.2.6.3-alpha. Patch from Peter Palfrader.
1650 o Minor bugfixes (Linux seccomp2 sandbox):
1651 - Fix sandboxing to work when running as a relaymby renaming of
1652 secret_id_key, and allowing the eventfd2 and futex syscalls. Fixes
1653 bug 16244; bugfix on 0.2.6.1-alpha. Patch by Peter Palfrader.
1654 - Allow systemd connections to work with the Linux seccomp2 sandbox
1655 code. Fixes bug 16212; bugfix on 0.2.6.2-alpha. Patch by
1658 o Minor bugfixes (tests):
1659 - Fix a crash in the unit tests when built with MSVC2013. Fixes bug
1660 16030; bugfix on 0.2.6.2-alpha. Patch from "NewEraCracker".
1663 Changes in version 0.2.6.8 - 2015-05-21
1664 Tor 0.2.6.8 fixes a bit of dodgy code in parsing INTRODUCE2 cells, and
1665 fixes an authority-side bug in assigning the HSDir flag. All directory
1666 authorities should upgrade.
1668 o Major bugfixes (hidden services, backport from 0.2.7.1-alpha):
1669 - Revert commit that made directory authorities assign the HSDir
1670 flag to relay without a DirPort; this was bad because such relays
1671 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1674 o Minor bugfixes (hidden service, backport from 0.2.7.1-alpha):
1675 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1676 a client authorized hidden service. Fixes bug 15823; bugfix
1679 o Minor features (geoip):
1680 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1681 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1685 Changes in version 0.2.7.1-alpha - 2015-05-12
1686 Tor 0.2.7.1-alpha is the first alpha release in its series. It
1687 includes numerous small features and bugfixes against previous Tor
1688 versions, and numerous small infrastructure improvements. The most
1689 notable features are several new ways for controllers to interact with
1690 the hidden services subsystem.
1692 o New system requirements:
1693 - Tor no longer includes workarounds to support Libevent versions
1694 before 1.3e. Libevent 2.0 or later is recommended. Closes
1697 o Major features (controller):
1698 - Add the ADD_ONION and DEL_ONION commands that allow the creation
1699 and management of hidden services via the controller. Closes
1701 - New "GETINFO onions/current" and "GETINFO onions/detached"
1702 commands to get information about hidden services created via the
1703 controller. Part of ticket 6411.
1704 - New HSFETCH command to launch a request for a hidden service
1705 descriptor. Closes ticket 14847.
1706 - New HSPOST command to upload a hidden service descriptor. Closes
1707 ticket 3523. Patch by "DonnchaC".
1709 o Major bugfixes (hidden services):
1710 - Revert commit that made directory authorities assign the HSDir
1711 flag to relay without a DirPort; this was bad because such relays
1712 can't handle BEGIN_DIR cells. Fixes bug 15850; bugfix
1715 o Minor features (clock-jump tolerance):
1716 - Recover better when our clock jumps back many hours, like might
1717 happen for Tails or Whonix users who start with a very wrong
1718 hardware clock, use Tor to discover a more accurate time, and then
1719 fix their clock. Resolves part of ticket 8766.
1721 o Minor features (command-line interface):
1722 - Make --hash-password imply --hush to prevent unnecessary noise.
1723 Closes ticket 15542. Patch from "cypherpunks".
1724 - Print a warning whenever we find a relative file path being used
1725 as torrc option. Resolves issue 14018.
1727 o Minor features (controller):
1728 - Add DirAuthority lines for default directory authorities to the
1729 output of the "GETINFO config/defaults" command if not already
1730 present. Implements ticket 14840.
1731 - Controllers can now use "GETINFO hs/client/desc/id/..." to
1732 retrieve items from the client's hidden service descriptor cache.
1733 Closes ticket 14845.
1734 - Implement a new controller command "GETINFO status/fresh-relay-
1735 descs" to fetch a descriptor/extrainfo pair that was generated on
1736 demand just for the controller's use. Implements ticket 14784.
1738 o Minor features (DoS-resistance):
1739 - Make it harder for attackers to overload hidden services with
1740 introductions, by blocking multiple introduction requests on the
1741 same circuit. Resolves ticket 15515.
1743 o Minor features (geoip):
1744 - Update geoip to the April 8 2015 Maxmind GeoLite2 Country database.
1745 - Update geoip6 to the April 8 2015 Maxmind GeoLite2
1748 o Minor features (HS popularity countermeasure):
1749 - To avoid leaking HS popularity, don't cycle the introduction point
1750 when we've handled a fixed number of INTRODUCE2 cells but instead
1751 cycle it when a random number of introductions is reached, thus
1752 making it more difficult for an attacker to find out the amount of
1753 clients that have used the introduction point for a specific HS.
1754 Closes ticket 15745.
1756 o Minor features (logging):
1757 - Include the Tor version in all LD_BUG log messages, since people
1758 tend to cut and paste those into the bugtracker. Implements
1761 o Minor features (pluggable transports):
1762 - When launching managed pluggable transports on Linux systems,
1763 attempt to have the kernel deliver a SIGTERM on tor exit if the
1764 pluggable transport process is still running. Resolves
1766 - When launching managed pluggable transports, setup a valid open
1767 stdin in the child process that can be used to detect if tor has
1768 terminated. The "TOR_PT_EXIT_ON_STDIN_CLOSE" environment variable
1769 can be used by implementations to detect this new behavior.
1770 Resolves ticket 15435.
1772 o Minor features (testing):
1773 - Add a test to verify that the compiler does not eliminate our
1774 memwipe() implementation. Closes ticket 15377.
1775 - Add make rule `check-changes` to verify the format of changes
1776 files. Closes ticket 15180.
1777 - Add unit tests for control_event_is_interesting(). Add a compile-
1778 time check that the number of events doesn't exceed the capacity
1779 of control_event_t.event_mask. Closes ticket 15431, checks for
1780 bugs similar to 13085. Patch by "teor".
1781 - Command-line argument tests moved to Stem. Resolves ticket 14806.
1782 - Integrate the ntor, backtrace, and zero-length keys tests into the
1783 automake test suite. Closes ticket 15344.
1784 - Remove assertions during builds to determine Tor's test coverage.
1785 We don't want to trigger these even in assertions, so including
1786 them artificially makes our branch coverage look worse than it is.
1787 This patch provides the new test-stem-full and coverage-html-full
1788 configure options. Implements ticket 15400.
1790 o Minor bugfixes (build):
1791 - Improve out-of-tree builds by making non-standard rules work and
1792 clean up additional files and directories. Fixes bug 15053; bugfix
1795 o Minor bugfixes (command-line interface):
1796 - When "--quiet" is provided along with "--validate-config", do not
1797 write anything to stdout on success. Fixes bug 14994; bugfix
1799 - When complaining about bad arguments to "--dump-config", use
1802 o Minor bugfixes (configuration, unit tests):
1803 - Only add the default fallback directories when the DirAuthorities,
1804 AlternateDirAuthority, and FallbackDir directory config options
1805 are set to their defaults. The default fallback directory list is
1806 currently empty, this fix will only change tor's behavior when it
1807 has default fallback directories. Includes unit tests for
1808 consider_adding_dir_servers(). Fixes bug 15642; bugfix on
1809 90f6071d8dc0 in 0.2.4.7-alpha. Patch by "teor".
1811 o Minor bugfixes (correctness):
1812 - For correctness, avoid modifying a constant string in
1813 handle_control_postdescriptor. Fixes bug 15546; bugfix
1815 - Remove side-effects from tor_assert() calls. This was harmless,
1816 because we never disable assertions, but it is bad style and
1817 unnecessary. Fixes bug 15211; bugfix on 0.2.5.5, 0.2.2.36,
1820 o Minor bugfixes (hidden service):
1821 - Fix an out-of-bounds read when parsing invalid INTRODUCE2 cells on
1822 a client authorized hidden service. Fixes bug 15823; bugfix
1824 - Remove an extraneous newline character from the end of hidden
1825 service descriptors. Fixes bug 15296; bugfix on 0.2.0.10-alpha.
1827 o Minor bugfixes (interface):
1828 - Print usage information for --dump-config when it is used without
1829 an argument. Also, fix the error message to use different wording
1830 and add newline at the end. Fixes bug 15541; bugfix
1833 o Minor bugfixes (logs):
1834 - When building Tor under Clang, do not include an extra set of
1835 parentheses in log messages that include function names. Fixes bug
1836 15269; bugfix on every released version of Tor when compiled with
1837 recent enough Clang.
1839 o Minor bugfixes (network):
1840 - When attempting to use fallback technique for network interface
1841 lookup, disregard loopback and multicast addresses since they are
1842 unsuitable for public communications.
1844 o Minor bugfixes (statistics):
1845 - Disregard the ConnDirectionStatistics torrc options when Tor is
1846 not a relay since in that mode of operation no sensible data is
1847 being collected and because Tor might run into measurement hiccups
1848 when running as a client for some time, then becoming a relay.
1849 Fixes bug 15604; bugfix on 0.2.2.35.
1851 o Minor bugfixes (test networks):
1852 - When self-testing reachability, use ExtendAllowPrivateAddresses to
1853 determine if local/private addresses imply reachability. The
1854 previous fix used TestingTorNetwork, which implies
1855 ExtendAllowPrivateAddresses, but this excluded rare configurations
1856 where ExtendAllowPrivateAddresses is set but TestingTorNetwork is
1857 not. Fixes bug 15771; bugfix on 0.2.6.1-alpha. Patch by "teor",
1858 issue discovered by CJ Ess.
1860 o Minor bugfixes (testing):
1861 - Check for matching value in server response in ntor_ref.py. Fixes
1862 bug 15591; bugfix on 0.2.4.8-alpha. Reported and fixed
1864 - Set the severity correctly when testing
1865 get_interface_addresses_ifaddrs() and
1866 get_interface_addresses_win32(), so that the tests fail gracefully
1867 instead of triggering an assertion. Fixes bug 15759; bugfix on
1868 0.2.6.3-alpha. Reported by Nicolas Derive.
1870 o Code simplification and refactoring:
1871 - Move the hacky fallback code out of get_interface_address6() into
1872 separate function and get it covered with unit-tests. Resolves
1874 - Refactor hidden service client-side cache lookup to intelligently
1875 report its various failure cases, and disentangle failure cases
1876 involving a lack of introduction points. Closes ticket 14391.
1877 - Use our own Base64 encoder instead of OpenSSL's, to allow more
1878 control over the output. Part of ticket 15652.
1881 - Improve the descriptions of statistics-related torrc options in
1882 the manpage to describe rationale and possible uses cases. Fixes
1884 - Improve the layout and formatting of ./configure --help messages.
1885 Closes ticket 15024. Patch from "cypherpunks".
1886 - Standardize on the term "server descriptor" in the manual page.
1887 Previously, we had used "router descriptor", "server descriptor",
1888 and "relay descriptor" interchangeably. Part of ticket 14987.
1891 - Remove `USE_OPENSSL_BASE64` and the corresponding fallback code
1892 and always use the internal Base64 decoder. The internal decoder
1893 has been part of tor since 0.2.0.10-alpha, and no one should
1894 be using the OpenSSL one. Part of ticket 15652.
1895 - Remove the 'tor_strclear()' function; use memwipe() instead.
1896 Closes ticket 14922.
1899 - Remove the (seldom-used) DynamicDHGroups feature. For anti-
1900 fingerprinting we now recommend pluggable transports; for forward-
1901 secrecy in TLS, we now use the P-256 group. Closes ticket 13736.
1902 - Remove the undocumented "--digests" command-line option. It
1903 complicated our build process, caused subtle build issues on
1904 multiple platforms, and is now redundant since we started
1905 including git version identifiers. Closes ticket 14742.
1906 - Tor no longer contains checks for ancient directory cache versions
1907 that didn't know about microdescriptors.
1908 - Tor no longer contains workarounds for stat files generated by
1909 super-old versions of Tor that didn't choose guards sensibly.
1912 Changes in version 0.2.4.27 - 2015-04-06
1913 Tor 0.2.4.27 backports two fixes from 0.2.6.7 for security issues that
1914 could be used by an attacker to crash hidden services, or crash clients
1915 visiting hidden services. Hidden services should upgrade as soon as
1916 possible; clients should upgrade whenever packages become available.
1918 This release also backports a simple improvement to make hidden
1919 services a bit less vulnerable to denial-of-service attacks.
1921 o Major bugfixes (security, hidden service):
1922 - Fix an issue that would allow a malicious client to trigger an
1923 assertion failure and halt a hidden service. Fixes bug 15600;
1924 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1925 - Fix a bug that could cause a client to crash with an assertion
1926 failure when parsing a malformed hidden service descriptor. Fixes
1927 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1929 o Minor features (DoS-resistance, hidden service):
1930 - Introduction points no longer allow multiple INTRODUCE1 cells to
1931 arrive on the same circuit. This should make it more expensive for
1932 attackers to overwhelm hidden services with introductions.
1933 Resolves ticket 15515.
1936 Changes in version 0.2.5.12 - 2015-04-06
1937 Tor 0.2.5.12 backports two fixes from 0.2.6.7 for security issues that
1938 could be used by an attacker to crash hidden services, or crash clients
1939 visiting hidden services. Hidden services should upgrade as soon as
1940 possible; clients should upgrade whenever packages become available.
1942 This release also backports a simple improvement to make hidden
1943 services a bit less vulnerable to denial-of-service attacks.
1945 o Major bugfixes (security, hidden service):
1946 - Fix an issue that would allow a malicious client to trigger an
1947 assertion failure and halt a hidden service. Fixes bug 15600;
1948 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1949 - Fix a bug that could cause a client to crash with an assertion
1950 failure when parsing a malformed hidden service descriptor. Fixes
1951 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1953 o Minor features (DoS-resistance, hidden service):
1954 - Introduction points no longer allow multiple INTRODUCE1 cells to
1955 arrive on the same circuit. This should make it more expensive for
1956 attackers to overwhelm hidden services with introductions.
1957 Resolves ticket 15515.
1960 Changes in version 0.2.6.7 - 2015-04-06
1961 Tor 0.2.6.7 fixes two security issues that could be used by an
1962 attacker to crash hidden services, or crash clients visiting hidden
1963 services. Hidden services should upgrade as soon as possible; clients
1964 should upgrade whenever packages become available.
1966 This release also contains two simple improvements to make hidden
1967 services a bit less vulnerable to denial-of-service attacks.
1969 o Major bugfixes (security, hidden service):
1970 - Fix an issue that would allow a malicious client to trigger an
1971 assertion failure and halt a hidden service. Fixes bug 15600;
1972 bugfix on 0.2.1.6-alpha. Reported by "disgleirio".
1973 - Fix a bug that could cause a client to crash with an assertion
1974 failure when parsing a malformed hidden service descriptor. Fixes
1975 bug 15601; bugfix on 0.2.1.5-alpha. Found by "DonnchaC".
1977 o Minor features (DoS-resistance, hidden service):
1978 - Introduction points no longer allow multiple INTRODUCE1 cells to
1979 arrive on the same circuit. This should make it more expensive for
1980 attackers to overwhelm hidden services with introductions.
1981 Resolves ticket 15515.
1982 - Decrease the amount of reattempts that a hidden service performs
1983 when its rendezvous circuits fail. This reduces the computational
1984 cost for running a hidden service under heavy load. Resolves
1988 Changes in version 0.2.6.6 - 2015-03-24
1989 Tor 0.2.6.6 is the first stable release in the 0.2.6 series.
1991 It adds numerous safety, security, correctness, and performance
1992 improvements. Client programs can be configured to use more kinds of
1993 sockets, AutomapHosts works better, the multithreading backend is
1994 improved, cell transmission is refactored, test coverage is much
1995 higher, more denial-of-service attacks are handled, guard selection is
1996 improved to handle long-term guards better, pluggable transports
1997 should work a bit better, and some annoying hidden service performance
1998 bugs should be addressed.
2000 o Minor bugfixes (portability):
2001 - Use the correct datatype in the SipHash-2-4 function to prevent
2002 compilers from assuming any sort of alignment. Fixes bug 15436;
2003 bugfix on 0.2.5.3-alpha.
2005 Changes in version 0.2.6.5-rc - 2015-03-18
2006 Tor 0.2.6.5-rc is the second and (hopefully) last release candidate in
2007 the 0.2.6. It fixes a small number of bugs found in 0.2.6.4-rc.
2009 o Major bugfixes (client):
2010 - Avoid crashing when making certain configuration option changes on
2011 clients. Fixes bug 15245; bugfix on 0.2.6.3-alpha. Reported
2014 o Major bugfixes (pluggable transports):
2015 - Initialize the extended OR Port authentication cookie before
2016 launching pluggable transports. This prevents a race condition
2017 that occured when server-side pluggable transports would cache the
2018 authentication cookie before it has been (re)generated. Fixes bug
2019 15240; bugfix on 0.2.5.1-alpha.
2021 o Major bugfixes (portability):
2022 - Do not crash on startup when running on Solaris. Fixes a bug
2023 related to our fix for 9495; bugfix on 0.2.6.1-alpha. Reported
2026 o Minor features (heartbeat):
2027 - On relays, report how many connections we negotiated using each
2028 version of the Tor link protocols. This information will let us
2029 know if removing support for very old versions of the Tor
2030 protocols is harming the network. Closes ticket 15212.
2032 o Code simplification and refactoring:
2033 - Refactor main loop to extract the 'loop' part. This makes it
2034 easier to run Tor under Shadow. Closes ticket 15176.
2037 Changes in version 0.2.5.11 - 2015-03-17
2038 Tor 0.2.5.11 is the second stable release in the 0.2.5 series.
2040 It backports several bugfixes from the 0.2.6 branch, including a
2041 couple of medium-level security fixes for relays and exit nodes.
2042 It also updates the list of directory authorities.
2044 o Directory authority changes:
2045 - Remove turtles as a directory authority.
2046 - Add longclaw as a new (v3) directory authority. This implements
2047 ticket 13296. This keeps the directory authority count at 9.
2048 - The directory authority Faravahar has a new IP address. This
2049 closes ticket 14487.
2051 o Major bugfixes (crash, OSX, security):
2052 - Fix a remote denial-of-service opportunity caused by a bug in
2053 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2056 o Major bugfixes (relay, stability, possible security):
2057 - Fix a bug that could lead to a relay crashing with an assertion
2058 failure if a buffer of exactly the wrong layout was passed to
2059 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2060 0.2.0.10-alpha. Patch from 'cypherpunks'.
2061 - Do not assert if the 'data' pointer on a buffer is advanced to the
2062 very end of the buffer; log a BUG message instead. Only assert if
2063 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2065 o Major bugfixes (exit node stability):
2066 - Fix an assertion failure that could occur under high DNS load.
2067 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2068 diagnosed and fixed by "cypherpunks".
2070 o Major bugfixes (Linux seccomp2 sandbox):
2071 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2072 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2073 0.2.5.1-alpha. Patch from "sanic".
2075 o Minor features (controller):
2076 - New "GETINFO bw-event-cache" to get information about recent
2077 bandwidth events. Closes ticket 14128. Useful for controllers to
2078 get recent bandwidth history after the fix for ticket 13988.
2080 o Minor features (geoip):
2081 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2082 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2085 o Minor bugfixes (client, automapping):
2086 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2087 no value follows the option. Fixes bug 14142; bugfix on
2088 0.2.4.7-alpha. Patch by "teor".
2089 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2090 14195; bugfix on 0.1.0.1-rc.
2092 o Minor bugfixes (compilation):
2093 - Build without warnings with the stock OpenSSL srtp.h header, which
2094 has a duplicate declaration of SSL_get_selected_srtp_profile().
2095 Fixes bug 14220; this is OpenSSL's bug, not ours.
2097 o Minor bugfixes (directory authority):
2098 - Allow directory authorities to fetch more data from one another if
2099 they find themselves missing lots of votes. Previously, they had
2100 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2101 bugfix on 0.1.2.5-alpha.
2102 - Enlarge the buffer to read bwauth generated files to avoid an
2103 issue when parsing the file in dirserv_read_measured_bandwidths().
2104 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2106 o Minor bugfixes (statistics):
2107 - Increase period over which bandwidth observations are aggregated
2108 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2110 o Minor bugfixes (preventative security, C safety):
2111 - When reading a hexadecimal, base-32, or base-64 encoded value from
2112 a string, always overwrite the whole output buffer. This prevents
2113 some bugs where we would look at (but fortunately, not reveal)
2114 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2118 Changes in version 0.2.4.26 - 2015-03-17
2119 Tor 0.2.4.26 includes an updated list of directory authorities. It
2120 also backports a couple of stability and security bugfixes from 0.2.5
2123 o Directory authority changes:
2124 - Remove turtles as a directory authority.
2125 - Add longclaw as a new (v3) directory authority. This implements
2126 ticket 13296. This keeps the directory authority count at 9.
2127 - The directory authority Faravahar has a new IP address. This
2128 closes ticket 14487.
2130 o Major bugfixes (exit node stability, also in 0.2.6.3-alpha):
2131 - Fix an assertion failure that could occur under high DNS load.
2132 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2133 diagnosed and fixed by "cypherpunks".
2135 o Major bugfixes (relay, stability, possible security, also in 0.2.6.4-rc):
2136 - Fix a bug that could lead to a relay crashing with an assertion
2137 failure if a buffer of exactly the wrong layout was passed to
2138 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2139 0.2.0.10-alpha. Patch from 'cypherpunks'.
2140 - Do not assert if the 'data' pointer on a buffer is advanced to the
2141 very end of the buffer; log a BUG message instead. Only assert if
2142 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2144 o Minor features (geoip):
2145 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2146 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2149 Changes in version 0.2.6.4-rc - 2015-03-09
2150 Tor 0.2.6.4-alpha fixes an issue in the directory code that an
2151 attacker might be able to use in order to crash certain Tor
2152 directories. It also resolves some minor issues left over from, or
2153 introduced in, Tor 0.2.6.3-alpha or earlier.
2155 o Major bugfixes (crash, OSX, security):
2156 - Fix a remote denial-of-service opportunity caused by a bug in
2157 OSX's _strlcat_chk() function. Fixes bug 15205; bug first appeared
2160 o Major bugfixes (relay, stability, possible security):
2161 - Fix a bug that could lead to a relay crashing with an assertion
2162 failure if a buffer of exactly the wrong layout is passed to
2163 buf_pullup() at exactly the wrong time. Fixes bug 15083; bugfix on
2164 0.2.0.10-alpha. Patch from "cypherpunks".
2165 - Do not assert if the 'data' pointer on a buffer is advanced to the
2166 very end of the buffer; log a BUG message instead. Only assert if
2167 it is past that point. Fixes bug 15083; bugfix on 0.2.0.10-alpha.
2169 o Major bugfixes (FreeBSD IPFW transparent proxy):
2170 - Fix address detection with FreeBSD transparent proxies, when
2171 "TransProxyType ipfw" is in use. Fixes bug 15064; bugfix
2174 o Major bugfixes (Linux seccomp2 sandbox):
2175 - Pass IPPROTO_TCP rather than 0 to socket(), so that the Linux
2176 seccomp2 sandbox doesn't fail. Fixes bug 14989; bugfix
2178 - Allow AF_UNIX hidden services to be used with the seccomp2
2179 sandbox. Fixes bug 15003; bugfix on 0.2.6.3-alpha.
2180 - Upon receiving sighup with the seccomp2 sandbox enabled, do not
2181 crash during attempts to call wait4. Fixes bug 15088; bugfix on
2182 0.2.5.1-alpha. Patch from "sanic".
2184 o Minor features (controller):
2185 - Messages about problems in the bootstrap process now include
2186 information about the server we were trying to connect to when we
2187 noticed the problem. Closes ticket 15006.
2189 o Minor features (geoip):
2190 - Update geoip to the March 3 2015 Maxmind GeoLite2 Country database.
2191 - Update geoip6 to the March 3 2015 Maxmind GeoLite2
2194 o Minor features (logs):
2195 - Quiet some log messages in the heartbeat and at startup. Closes
2198 o Minor bugfixes (certificate handling):
2199 - If an authority operator accidentally makes a signing certificate
2200 with a future publication time, do not discard its real signing
2201 certificates. Fixes bug 11457; bugfix on 0.2.0.3-alpha.
2202 - Remove any old authority certificates that have been superseded
2203 for at least two days. Previously, we would keep superseded
2204 certificates until they expired, if they were published close in
2205 time to the certificate that superseded them. Fixes bug 11454;
2206 bugfix on 0.2.1.8-alpha.
2208 o Minor bugfixes (compilation):
2209 - Fix a compilation warning on s390. Fixes bug 14988; bugfix
2211 - Fix a compilation warning on FreeBSD. Fixes bug 15151; bugfix
2214 o Minor bugfixes (testing):
2215 - Fix endianness issues in unit test for resolve_my_address() to
2216 have it pass on big endian systems. Fixes bug 14980; bugfix on
2218 - Avoid a side-effect in a tor_assert() in the unit tests. Fixes bug
2219 15188; bugfix on 0.1.2.3-alpha. Patch from Tom van der Woerdt.
2220 - When running the new 'make test-stem' target, use the configured
2221 python binary. Fixes bug 15037; bugfix on 0.2.6.3-alpha. Patch
2223 - When running the zero-length-keys tests, do not use the default
2224 torrc file. Fixes bug 15033; bugfix on 0.2.6.3-alpha. Reported
2227 o Directory authority IP change:
2228 - The directory authority Faravahar has a new IP address. This
2229 closes ticket 14487.
2232 - Remove some lingering dead code that once supported mempools.
2233 Mempools were disabled by default in 0.2.5, and removed entirely
2234 in 0.2.6.3-alpha. Closes more of ticket 14848; patch
2238 Changes in version 0.2.6.3-alpha - 2015-02-19
2239 Tor 0.2.6.3-alpha is the third (and hopefully final) alpha release in
2240 the 0.2.6.x series. It introduces support for more kinds of sockets,
2241 makes it harder to accidentally run an exit, improves our
2242 multithreading backend, incorporates several fixes for the
2243 AutomapHostsOnResolve option, and fixes numerous other bugs besides.
2245 If no major regressions or security holes are found in this version,
2246 the next version will be a release candidate.
2248 o Deprecated versions:
2249 - Tor relays older than 0.2.4.18-rc are no longer allowed to
2250 advertise themselves on the network. Closes ticket 13555.
2252 o Major features (security, unix domain sockets):
2253 - Allow SocksPort to be an AF_UNIX Unix Domain Socket. Now high risk
2254 applications can reach Tor without having to create AF_INET or
2255 AF_INET6 sockets, meaning they can completely disable their
2256 ability to make non-Tor network connections. To create a socket of
2257 this type, use "SocksPort unix:/path/to/socket". Implements
2259 - Support mapping hidden service virtual ports to AF_UNIX sockets.
2260 The syntax is "HiddenServicePort 80 unix:/path/to/socket".
2261 Implements ticket 11485.
2263 o Major features (changed defaults):
2264 - Prevent relay operators from unintentionally running exits: When a
2265 relay is configured as an exit node, we now warn the user unless
2266 the "ExitRelay" option is set to 1. We warn even more loudly if
2267 the relay is configured with the default exit policy, since this
2268 can indicate accidental misconfiguration. Setting "ExitRelay 0"
2269 stops Tor from running as an exit relay. Closes ticket 10067.
2271 o Major features (directory system):
2272 - When downloading server- or microdescriptors from a directory
2273 server, we no longer launch multiple simultaneous requests to the
2274 same server. This reduces load on the directory servers,
2275 especially when directory guards are in use. Closes ticket 9969.
2276 - When downloading server- or microdescriptors over a tunneled
2277 connection, do not limit the length of our requests to what the
2278 Squid proxy is willing to handle. Part of ticket 9969.
2279 - Authorities can now vote on the correct digests and latest
2280 versions for different software packages. This allows packages
2281 that include Tor to use the Tor authority system as a way to get
2282 notified of updates and their correct digests. Implements proposal
2283 227. Closes ticket 10395.
2285 o Major features (guards):
2286 - Introduce the Guardfraction feature to improves load balancing on
2287 guard nodes. Specifically, it aims to reduce the traffic gap that
2288 guard nodes experience when they first get the Guard flag. This is
2289 a required step if we want to increase the guard lifetime to 9
2290 months or greater. Closes ticket 9321.
2292 o Major features (performance):
2293 - Make the CPU worker implementation more efficient by avoiding the
2294 kernel and lengthening pipelines. The original implementation used
2295 sockets to transfer data from the main thread to the workers, and
2296 didn't allow any thread to be assigned more than a single piece of
2297 work at once. The new implementation avoids communications
2298 overhead by making requests in shared memory, avoiding kernel IO
2299 where possible, and keeping more requests in flight at once.
2300 Implements ticket 9682.
2302 o Major features (relay):
2303 - Raise the minimum acceptable configured bandwidth rate for bridges
2304 to 50 KiB/sec and for relays to 75 KiB/sec. (The old values were
2305 20 KiB/sec.) Closes ticket 13822.
2307 o Major bugfixes (exit node stability):
2308 - Fix an assertion failure that could occur under high DNS load.
2309 Fixes bug 14129; bugfix on Tor 0.0.7rc1. Found by "jowr";
2310 diagnosed and fixed by "cypherpunks".
2312 o Major bugfixes (mixed relay-client operation):
2313 - When running as a relay and client at the same time (not
2314 recommended), if we decide not to use a new guard because we want
2315 to retry older guards, only close the locally-originating circuits
2316 passing through that guard. Previously we would close all the
2317 circuits through that guard. Fixes bug 9819; bugfix on
2318 0.2.1.1-alpha. Reported by "skruffy".
2320 o Minor features (build):
2321 - New --disable-system-torrc compile-time option to prevent Tor from
2322 looking for the system-wide torrc or torrc-defaults files.
2323 Resolves ticket 13037.
2325 o Minor features (controller):
2326 - Include SOCKS_USERNAME and SOCKS_PASSWORD values in controller
2327 events so controllers can observe circuit isolation inputs. Closes
2329 - ControlPort now supports the unix:/path/to/socket syntax as an
2330 alternative to the ControlSocket option, for consistency with
2331 SocksPort and HiddenServicePort. Closes ticket 14451.
2332 - New "GETINFO bw-event-cache" to get information about recent
2333 bandwidth events. Closes ticket 14128. Useful for controllers to
2334 get recent bandwidth history after the fix for ticket 13988.
2336 o Minor features (Denial of service resistance):
2337 - Count the total number of bytes used storing hidden service
2338 descriptors against the value of MaxMemInQueues. If we're low on
2339 memory, and more than 20% of our memory is used holding hidden
2340 service descriptors, free them until no more than 10% of our
2341 memory holds hidden service descriptors. Free the least recently
2342 fetched descriptors first. Resolves ticket 13806.
2343 - When we have recently been under memory pressure (over 3/4 of
2344 MaxMemInQueues is allocated), then allocate smaller zlib objects
2345 for small requests. Closes ticket 11791.
2347 o Minor features (geoip):
2348 - Update geoip and geoip6 files to the January 7 2015 Maxmind
2349 GeoLite2 Country database.
2351 o Minor features (guard nodes):
2352 - Reduce the time delay before saving guard status to disk from 10
2353 minutes to 30 seconds (or from one hour to 10 minutes if
2354 AvoidDiskWrites is set). Closes ticket 12485.
2356 o Minor features (hidden service):
2357 - Make Sybil attacks against hidden services harder by changing the
2358 minimum time required to get the HSDir flag from 25 hours up to 96
2359 hours. Addresses ticket 14149.
2360 - New option "HiddenServiceAllowUnknownPorts" to allow hidden
2361 services to disable the anti-scanning feature introduced in
2362 0.2.6.2-alpha. With this option not set, a connection to an
2363 unlisted port closes the circuit. With this option set, only a
2364 RELAY_DONE cell is sent. Closes ticket 14084.
2366 o Minor features (interface):
2367 - Implement "-f -" command-line option to read torrc configuration
2368 from standard input, if you don't want to store the torrc file in
2369 the file system. Implements feature 13865.
2371 o Minor features (logging):
2372 - Add a count of unique clients to the bridge heartbeat message.
2373 Resolves ticket 6852.
2374 - Suppress "router info incompatible with extra info" message when
2375 reading extrainfo documents from cache. (This message got loud
2376 around when we closed bug 9812 in 0.2.6.2-alpha.) Closes
2378 - Elevate hidden service authorized-client message from DEBUG to
2379 INFO. Closes ticket 14015.
2381 o Minor features (stability):
2382 - Add assertions in our hash-table iteration code to check for
2383 corrupted values that could cause infinite loops. Closes
2386 o Minor features (systemd):
2387 - Various improvements and modernizations in systemd hardening
2388 support. Closes ticket 13805. Patch from Craig Andrews.
2390 o Minor features (testing networks):
2391 - Drop the minimum RendPostPeriod on a testing network to 5 seconds,
2392 and the default on a testing network to 2 minutes. Drop the
2393 MIN_REND_INITIAL_POST_DELAY on a testing network to 5 seconds, but
2394 keep the default on a testing network at 30 seconds. This reduces
2395 HS bootstrap time to around 25 seconds. Also, change the default
2396 time in test-network.sh to match. Closes ticket 13401. Patch
2398 - Create TestingDirAuthVoteHSDir to correspond to
2399 TestingDirAuthVoteExit/Guard. Ensures that authorities vote the
2400 HSDir flag for the listed relays regardless of uptime or ORPort
2401 connectivity. Respects the value of VoteOnHidServDirectoriesV2.
2402 Partial implementation for ticket 14067. Patch by "teor".
2404 o Minor features (tor2web mode):
2405 - Introduce the config option Tor2webRendezvousPoints, which allows
2406 clients in Tor2webMode to select a specific Rendezvous Point to be
2407 used in HS circuits. This might allow better performance for
2408 Tor2Web nodes. Implements ticket 12844.
2410 o Minor bugfixes (client DNS):
2411 - Report the correct cached DNS expiration times on SOCKS port or in
2412 DNS replies. Previously, we would report everything as "never
2413 expires." Fixes bug 14193; bugfix on 0.2.3.17-beta.
2414 - Avoid a small memory leak when we find a cached answer for a
2415 reverse DNS lookup in a client-side DNS cache. (Remember, client-
2416 side DNS caching is off by default, and is not recommended.) Fixes
2417 bug 14259; bugfix on 0.2.0.1-alpha.
2419 o Minor bugfixes (client, automapping):
2420 - Avoid crashing on torrc lines for VirtualAddrNetworkIPv[4|6] when
2421 no value follows the option. Fixes bug 14142; bugfix on
2422 0.2.4.7-alpha. Patch by "teor".
2423 - Fix a memory leak when using AutomapHostsOnResolve. Fixes bug
2424 14195; bugfix on 0.1.0.1-rc.
2425 - Prevent changes to other options from removing the wildcard value
2426 "." from "AutomapHostsSuffixes". Fixes bug 12509; bugfix
2428 - Allow MapAddress and AutomapHostsOnResolve to work together when
2429 an address is mapped into another address type (like .onion) that
2430 must be automapped at resolve time. Fixes bug 7555; bugfix
2433 o Minor bugfixes (client, bridges):
2434 - When we are using bridges and we had a network connectivity
2435 problem, only retry connecting to our currently configured
2436 bridges, not all bridges we know about and remember using. Fixes
2437 bug 14216; bugfix on 0.2.2.17-alpha.
2439 o Minor bugfixes (client, IPv6):
2440 - Reject socks requests to literal IPv6 addresses when IPv6Traffic
2441 flag is not set; and not because the NoIPv4Traffic flag was set.
2442 Previously we'd looked at the NoIPv4Traffic flag for both types of
2443 literal addresses. Fixes bug 14280; bugfix on 0.2.4.7-alpha.
2445 o Minor bugfixes (compilation):
2446 - The address of an array in the middle of a structure will always
2447 be non-NULL. clang recognises this and complains. Disable the
2448 tautologous and redundant check to silence this warning. Fixes bug
2449 14001; bugfix on 0.2.1.2-alpha.
2450 - Avoid warnings when building with systemd 209 or later. Fixes bug
2451 14072; bugfix on 0.2.6.2-alpha. Patch from "h.venev".
2452 - Compile correctly with (unreleased) OpenSSL 1.1.0 headers.
2453 Addresses ticket 14188.
2454 - Build without warnings with the stock OpenSSL srtp.h header, which
2455 has a duplicate declaration of SSL_get_selected_srtp_profile().
2456 Fixes bug 14220; this is OpenSSL's bug, not ours.
2457 - Do not compile any code related to Tor2Web mode when Tor2Web mode
2458 is not enabled at compile time. Previously, this code was included
2459 in a disabled state. See discussion on ticket 12844.
2460 - Remove the --disable-threads configure option again. It was
2461 accidentally partially reintroduced in 29ac883606d6d. Fixes bug
2462 14819; bugfix on 0.2.6.2-alpha.
2464 o Minor bugfixes (controller):
2465 - Report "down" in response to the "GETINFO entry-guards" command
2466 when relays are down with an unreachable_since value. Previously,
2467 we would report "up". Fixes bug 14184; bugfix on 0.1.2.2-alpha.
2468 - Avoid crashing on a malformed EXTENDCIRCUIT command. Fixes bug
2469 14116; bugfix on 0.2.2.9-alpha.
2470 - Add a code for the END_CIRC_REASON_IP_NOW_REDUNDANT circuit close
2471 reason. Fixes bug 14207; bugfix on 0.2.6.2-alpha.
2473 o Minor bugfixes (directory authority):
2474 - Allow directory authorities to fetch more data from one another if
2475 they find themselves missing lots of votes. Previously, they had
2476 been bumping against the 10 MB queued data limit. Fixes bug 14261;
2477 bugfix on 0.1.2.5-alpha.
2478 - Do not attempt to download extrainfo documents which we will be
2479 unable to validate with a matching server descriptor. Fixes bug
2480 13762; bugfix on 0.2.0.1-alpha.
2481 - Fix a bug that was truncating AUTHDIR_NEWDESC events sent to the
2482 control port. Fixes bug 14953; bugfix on 0.2.0.1-alpha.
2483 - Enlarge the buffer to read bwauth generated files to avoid an
2484 issue when parsing the file in dirserv_read_measured_bandwidths().
2485 Fixes bug 14125; bugfix on 0.2.2.1-alpha.
2487 o Minor bugfixes (file handling):
2488 - Stop failing when key files are zero-length. Instead, generate new
2489 keys, and overwrite the empty key files. Fixes bug 13111; bugfix
2490 on all versions of Tor. Patch by "teor".
2491 - Stop generating a fresh .old RSA onion key file when the .old file
2492 is missing. Fixes part of 13111; bugfix on 0.0.6rc1.
2493 - Avoid overwriting .old key files with empty key files.
2494 - Skip loading zero-length extrainfo store, router store, stats,
2495 state, and key files.
2496 - Avoid crashing when trying to reload a torrc specified as a
2497 relative path with RunAsDaemon turned on. Fixes bug 13397; bugfix
2500 o Minor bugfixes (hidden services):
2501 - Close the introduction circuit when we have no more usable intro
2502 points, instead of waiting for it to time out. This also ensures
2503 that no follow-up HS descriptor fetch is triggered when the
2504 circuit eventually times out. Fixes bug 14224; bugfix on 0.0.6.
2505 - When fetching a hidden service descriptor for a down service that
2506 was recently up, do not keep refetching until we try the same
2507 replica twice in a row. Fixes bug 14219; bugfix on 0.2.0.10-alpha.
2508 - Successfully launch Tor with a nonexistent hidden service
2509 directory. Our fix for bug 13942 didn't catch this case. Fixes bug
2510 14106; bugfix on 0.2.6.2-alpha.
2512 o Minor bugfixes (logging):
2513 - Avoid crashing when there are more log domains than entries in
2514 domain_list. Bugfix on 0.2.3.1-alpha.
2515 - Add a string representation for LD_SCHED. Fixes bug 14740; bugfix
2517 - Don't log messages to stdout twice when starting up. Fixes bug
2518 13993; bugfix on 0.2.6.1-alpha.
2520 o Minor bugfixes (parsing):
2521 - Stop accepting milliseconds (or other junk) at the end of
2522 descriptor publication times. Fixes bug 9286; bugfix on 0.0.2pre25.
2523 - Support two-number and three-number version numbers correctly, in
2524 case we change the Tor versioning system in the future. Fixes bug
2525 13661; bugfix on 0.0.8pre1.
2527 o Minor bugfixes (path counting):
2528 - When deciding whether the consensus lists any exit nodes, count
2529 the number listed in the consensus, not the number we have
2530 descriptors for. Fixes part of bug 14918; bugfix on 0.2.6.2-alpha.
2531 - When deciding whether we have any exit nodes, only examine
2532 ExitNodes when the ExitNodes option is actually set. Fixes part of
2533 bug 14918; bugfix on 0.2.6.2-alpha.
2534 - Get rid of redundant and possibly scary warnings that we are
2535 missing directory information while we bootstrap. Fixes part of
2536 bug 14918; bugfix on 0.2.6.2-alpha.
2538 o Minor bugfixes (portability):
2539 - Fix the ioctl()-based network interface lookup code so that it
2540 will work on systems that have variable-length struct ifreq, for
2542 - Fix scheduler compilation on targets where char is unsigned. Fixes
2543 bug 14764; bugfix on 0.2.6.2-alpha. Reported by Christian Kujau.
2545 o Minor bugfixes (sandbox):
2546 - Allow glibc fatal errors to be sent to stderr before Tor exits.
2547 Previously, glibc would try to write them to /dev/tty, and the
2548 sandbox would trap the call and make Tor exit prematurely. Fixes
2549 bug 14759; bugfix on 0.2.5.1-alpha.
2551 o Minor bugfixes (shutdown):
2552 - When shutting down, always call event_del() on lingering read or
2553 write events before freeing them. Otherwise, we risk double-frees
2554 or read-after-frees in event_base_free(). Fixes bug 12985; bugfix
2557 o Minor bugfixes (small memory leaks):
2558 - Avoid leaking memory when using IPv6 virtual address mappings.
2559 Fixes bug 14123; bugfix on 0.2.4.7-alpha. Patch by Tom van
2562 o Minor bugfixes (statistics):
2563 - Increase period over which bandwidth observations are aggregated
2564 from 15 minutes to 4 hours. Fixes bug 13988; bugfix on 0.0.8pre1.
2566 o Minor bugfixes (systemd support):
2567 - Fix detection and operation of systemd watchdog. Fixes part of bug
2568 14141; bugfix on 0.2.6.2-alpha. Patch from Tomasz Torcz.
2569 - Run correctly under systemd with the RunAsDaemon option set. Fixes
2570 part of bug 14141; bugfix on 0.2.5.7-rc. Patch from Tomasz Torcz.
2571 - Inform the systemd supervisor about more changes in the Tor
2572 process status. Implements part of ticket 14141. Patch from
2574 - Cause the "--disable-systemd" option to actually disable systemd
2575 support. Fixes bug 14350; bugfix on 0.2.6.2-alpha. Patch
2578 o Minor bugfixes (TLS):
2579 - Check more thoroughly throughout the TLS code for possible
2580 unlogged TLS errors. Possible diagnostic or fix for bug 13319.
2582 o Minor bugfixes (transparent proxy):
2583 - Use getsockname, not getsockopt, to retrieve the address for a
2584 TPROXY-redirected connection. Fixes bug 13796; bugfix
2587 o Code simplification and refactoring:
2588 - Move fields related to isolating and configuring client ports into
2589 a shared structure. Previously, they were duplicated across
2590 port_cfg_t, listener_connection_t, and edge_connection_t. Failure
2591 to copy them correctly had been the cause of at least one bug in
2592 the past. Closes ticket 8546.
2593 - Refactor the get_interface_addresses_raw() doom-function into
2594 multiple smaller and simpler subfunctions. Cover the resulting
2595 subfunctions with unit-tests. Fixes a significant portion of
2597 - Remove workaround in dirserv_thinks_router_is_hs_dir() that was
2598 only for version <= 0.2.2.24 which is now deprecated. Closes
2600 - Remove a test for a long-defunct broken version-one
2604 - Adding section on OpenBSD to our TUNING document. Thanks to mmcc
2605 for writing the OpenBSD-specific tips. Resolves ticket 13702.
2606 - Make the tor-resolve documentation match its help string and its
2607 options. Resolves part of ticket 14325.
2608 - Log a more useful error message from tor-resolve when failing to
2609 look up a hidden service address. Resolves part of ticket 14325.
2611 o Downgraded warnings:
2612 - Don't warn when we've attempted to contact a relay using the wrong
2613 ntor onion key. Closes ticket 9635.
2616 - To avoid confusion with the "ExitRelay" option, "ExitNode" is no
2617 longer silently accepted as an alias for "ExitNodes".
2618 - The --enable-mempool and --enable-buf-freelists options, which
2619 were originally created to work around bad malloc implementations,
2620 no longer exist. They were off-by-default in 0.2.5. Closes
2624 - Make the checkdir/perms test complete successfully even if the
2625 global umask is not 022. Fixes bug 14215; bugfix on 0.2.6.2-alpha.
2626 - Test that tor does not fail when key files are zero-length. Check
2627 that tor generates new keys, and overwrites the empty key files.
2628 - Test that tor generates new keys when keys are missing
2629 (existing behavior).
2630 - Test that tor does not overwrite key files that already contain
2631 data (existing behavior). Tests bug 13111. Patch by "teor".
2632 - New "make test-stem" target to run stem integration tests.
2633 Requires that the "STEM_SOURCE_DIR" environment variable be set.
2634 Closes ticket 14107.
2635 - Make the test_cmdline_args.py script work correctly on Windows.
2636 Patch from Gisle Vanem.
2637 - Move the slower unit tests into a new "./src/test/test-slow"
2638 binary that can be run independently of the other tests. Closes
2640 - Avoid undefined behavior when sampling huge values from the
2641 Laplace distribution. This made unittests fail on Raspberry Pi.
2642 Bug found by Device. Fixes bug 14090; bugfix on 0.2.6.2-alpha.
2645 Changes in version 0.2.6.2-alpha - 2014-12-31
2646 Tor 0.2.6.2-alpha is the second alpha release in the 0.2.6.x series.
2647 It introduces a major new backend for deciding when to send cells on
2648 channels, which should lead down the road to big performance
2649 increases. It contains security and statistics features for better
2650 work on hidden services, and numerous bugfixes.
2652 This release contains many new unit tests, along with major
2653 performance improvements for running testing networks using Chutney.
2654 Thanks to a series of patches contributed by "teor", testing networks
2655 should now bootstrap in seconds, rather than minutes.
2657 o Major features (relay, infrastructure):
2658 - Complete revision of the code that relays use to decide which cell
2659 to send next. Formerly, we selected the best circuit to write on
2660 each channel, but we didn't select among channels in any
2661 sophisticated way. Now, we choose the best circuits globally from
2662 among those whose channels are ready to deliver traffic.
2664 This patch implements a new inter-cmux comparison API, a global
2665 high/low watermark mechanism and a global scheduler loop for
2666 transmission prioritization across all channels as well as among
2667 circuits on one channel. This schedule is currently tuned to
2668 (tolerantly) avoid making changes in network performance, but it
2669 should form the basis for major circuit performance increases in
2670 the future. Code by Andrea; tuning by Rob Jansen; implements
2673 o Major features (hidden services):
2674 - Make HS port scanning more difficult by immediately closing the
2675 circuit when a user attempts to connect to a nonexistent port.
2676 Closes ticket 13667.
2677 - Add a HiddenServiceStatistics option that allows Tor relays to
2678 gather and publish statistics about the overall size and volume of
2679 hidden service usage. Specifically, when this option is turned on,
2680 an HSDir will publish an approximate number of hidden services
2681 that have published descriptors to it the past 24 hours. Also, if
2682 a relay has acted as a hidden service rendezvous point, it will
2683 publish the approximate amount of rendezvous cells it has relayed
2684 the past 24 hours. The statistics themselves are obfuscated so
2685 that the exact values cannot be derived. For more details see
2686 proposal 238, "Better hidden service stats from Tor relays". This
2687 feature is currently disabled by default. Implements feature 13192.
2689 o Major bugfixes (client, automap):
2690 - Repair automapping with IPv6 addresses. This automapping should
2691 have worked previously, but one piece of debugging code that we
2692 inserted to detect a regression actually caused the regression to
2693 manifest itself again. Fixes bug 13811 and bug 12831; bugfix on
2694 0.2.4.7-alpha. Diagnosed and fixed by Francisco Blas
2697 o Major bugfixes (hidden services):
2698 - When closing an introduction circuit that was opened in parallel
2699 with others, don't mark the introduction point as unreachable.
2700 Previously, the first successful connection to an introduction
2701 point would make the other introduction points get marked as
2702 having timed out. Fixes bug 13698; bugfix on 0.0.6rc2.
2704 o Directory authority changes:
2705 - Remove turtles as a directory authority.
2706 - Add longclaw as a new (v3) directory authority. This implements
2707 ticket 13296. This keeps the directory authority count at 9.
2709 o Major removed features:
2710 - Tor clients no longer support connecting to hidden services
2711 running on Tor 0.2.2.x and earlier; the Support022HiddenServices
2712 option has been removed. (There shouldn't be any hidden services
2713 running these versions on the network.) Closes ticket 7803.
2715 o Minor features (client):
2716 - Validate hostnames in SOCKS5 requests more strictly. If SafeSocks
2717 is enabled, reject requests with IP addresses as hostnames.
2718 Resolves ticket 13315.
2720 o Minor features (controller):
2721 - Add a "SIGNAL HEARTBEAT" controller command that tells Tor to
2722 write an unscheduled heartbeat message to the log. Implements
2725 o Minor features (geoip):
2726 - Update geoip and geoip6 to the November 15 2014 Maxmind GeoLite2
2729 o Minor features (hidden services):
2730 - When re-enabling the network, don't try to build introduction
2731 circuits until we have successfully built a circuit. This makes
2732 hidden services come up faster when the network is re-enabled.
2733 Patch from "akwizgran". Closes ticket 13447.
2734 - When we fail to retrieve a hidden service descriptor, send the
2735 controller an "HS_DESC FAILED" controller event. Implements
2737 - New HiddenServiceDirGroupReadable option to cause hidden service
2738 directories and hostname files to be created group-readable. Patch
2739 from "anon", David Stainton, and "meejah". Closes ticket 11291.
2741 o Minor features (systemd):
2742 - Where supported, when running with systemd, report successful
2743 startup to systemd. Part of ticket 11016. Patch by Michael Scherer.
2744 - When running with systemd, support systemd watchdog messages. Part
2745 of ticket 11016. Patch by Michael Scherer.
2747 o Minor features (transparent proxy):
2748 - Update the transparent proxy option checks to allow for both ipfw
2749 and pf on OS X. Closes ticket 14002.
2750 - Use the correct option when using IPv6 with transparent proxy
2751 support on Linux. Resolves 13808. Patch by Francisco Blas
2754 o Minor bugfixes (preventative security, C safety):
2755 - When reading a hexadecimal, base-32, or base-64 encoded value from
2756 a string, always overwrite the whole output buffer. This prevents
2757 some bugs where we would look at (but fortunately, not reveal)
2758 uninitialized memory on the stack. Fixes bug 14013; bugfix on all
2760 - Clear all memory targetted by tor_addr_{to,from}_sockaddr(), not
2761 just the part that's used. This makes it harder for data leak bugs
2762 to occur in the event of other programming failures. Resolves
2765 o Minor bugfixes (client, microdescriptors):
2766 - Use a full 256 bits of the SHA256 digest of a microdescriptor when
2767 computing which microdescriptors to download. This keeps us from
2768 erroneous download behavior if two microdescriptor digests ever
2769 have the same first 160 bits. Fixes part of bug 13399; bugfix
2771 - Reset a router's status if its microdescriptor digest changes,
2772 even if the first 160 bits remain the same. Fixes part of bug
2773 13399; bugfix on 0.2.3.1-alpha.
2775 o Minor bugfixes (compilation):
2776 - Silence clang warnings under --enable-expensive-hardening,
2777 including implicit truncation of 64 bit values to 32 bit, const
2778 char assignment to self, tautological compare, and additional
2779 parentheses around equality tests. Fixes bug 13577; bugfix
2781 - Fix a clang warning about checking whether an address in the
2782 middle of a structure is NULL. Fixes bug 14001; bugfix
2785 o Minor bugfixes (hidden services):
2786 - Correctly send a controller event when we find that a rendezvous
2787 circuit has finished. Fixes bug 13936; bugfix on 0.1.1.5-alpha.
2788 - Pre-check directory permissions for new hidden-services to avoid
2789 at least one case of "Bug: Acting on config options left us in a
2790 broken state. Dying." Fixes bug 13942; bugfix on 0.0.6pre1.
2791 - When adding a new hidden service (for example, via SETCONF), Tor
2792 no longer congratulates the user for running a relay. Fixes bug
2793 13941; bugfix on 0.2.6.1-alpha.
2794 - When fetching hidden service descriptors, we now check not only
2795 for whether we got the hidden service we had in mind, but also
2796 whether we got the particular descriptors we wanted. This prevents
2797 a class of inefficient but annoying DoS attacks by hidden service
2798 directories. Fixes bug 13214; bugfix on 0.2.1.6-alpha. Reported
2801 o Minor bugfixes (Linux seccomp2 sandbox):
2802 - Make transparent proxy support work along with the seccomp2
2803 sandbox. Fixes part of bug 13808; bugfix on 0.2.5.1-alpha. Patch
2804 by Francisco Blas Izquierdo Riera.
2805 - Fix a memory leak in tor-resolve when running with the sandbox
2806 enabled. Fixes bug 14050; bugfix on 0.2.5.9-rc.
2808 o Minor bugfixes (logging):
2809 - Downgrade warnings about RSA signature failures to info log level.
2810 Emit a warning when an extra info document is found incompatible
2811 with a corresponding router descriptor. Fixes bug 9812; bugfix
2813 - Make connection_ap_handshake_attach_circuit() log the circuit ID
2814 correctly. Fixes bug 13701; bugfix on 0.0.6.
2816 o Minor bugfixes (misc):
2817 - Stop allowing invalid address patterns like "*/24" that contain
2818 both a wildcard address and a bit prefix length. This affects all
2819 our address-range parsing code. Fixes bug 7484; bugfix
2822 o Minor bugfixes (testing networks, fast startup):
2823 - Allow Tor to build circuits using a consensus with no exits. If
2824 the consensus has no exits (typical of a bootstrapping test
2825 network), allow Tor to build circuits once enough descriptors have
2826 been downloaded. This assists in bootstrapping a testing Tor
2827 network. Fixes bug 13718; bugfix on 0.2.4.10-alpha. Patch
2829 - When V3AuthVotingInterval is low, give a lower If-Modified-Since
2830 header to directory servers. This allows us to obtain consensuses
2831 promptly when the consensus interval is very short. This assists
2832 in bootstrapping a testing Tor network. Fixes parts of bugs 13718
2833 and 13963; bugfix on 0.2.0.3-alpha. Patch by "teor".
2834 - Stop assuming that private addresses are local when checking
2835 reachability in a TestingTorNetwork. Instead, when testing, assume
2836 all OR connections are remote. (This is necessary due to many test
2837 scenarios running all relays on localhost.) This assists in
2838 bootstrapping a testing Tor network. Fixes bug 13924; bugfix on
2839 0.1.0.1-rc. Patch by "teor".
2840 - Avoid building exit circuits from a consensus with no exits. Now
2841 thanks to our fix for 13718, we accept a no-exit network as not
2842 wholly lost, but we need to remember not to try to build exit
2843 circuits on it. Closes ticket 13814; patch by "teor".
2844 - Stop requiring exits to have non-zero bandwithcapacity in a
2845 TestingTorNetwork. Instead, when TestingMinExitFlagThreshold is 0,
2846 ignore exit bandwidthcapacity. This assists in bootstrapping a
2847 testing Tor network. Fixes parts of bugs 13718 and 13839; bugfix
2848 on 0.2.0.3-alpha. Patch by "teor".
2849 - Add "internal" to some bootstrap statuses when no exits are
2850 available. If the consensus does not contain Exits, Tor will only
2851 build internal circuits. In this case, relevant statuses will
2852 contain the word "internal" as indicated in the Tor control-
2853 spec.txt. When bootstrap completes, Tor will be ready to build
2854 internal circuits. If a future consensus contains Exits, exit
2855 circuits may become available. Fixes part of bug 13718; bugfix on
2856 0.2.4.10-alpha. Patch by "teor".
2857 - Decrease minimum consensus interval to 10 seconds when
2858 TestingTorNetwork is set, or 5 seconds for the first consensus.
2859 Fix assumptions throughout the code that assume larger intervals.
2860 Fixes bugs 13718 and 13823; bugfix on 0.2.0.3-alpha. Patch
2862 - Avoid excluding guards from path building in minimal test
2863 networks, when we're in a test network and excluding guards would
2864 exclude all relays. This typically occurs in incredibly small tor
2865 networks, and those using "TestingAuthVoteGuard *". Fixes part of
2866 bug 13718; bugfix on 0.1.1.11-alpha. Patch by "teor".
2868 o Code simplification and refactoring:
2869 - Stop using can_complete_circuits as a global variable; access it
2870 with a function instead.
2871 - Avoid using operators directly as macro arguments: this lets us
2872 apply coccinelle transformations to our codebase more directly.
2873 Closes ticket 13172.
2874 - Combine the functions used to parse ClientTransportPlugin and
2875 ServerTransportPlugin into a single function. Closes ticket 6456.
2876 - Add inline functions and convenience macros for inspecting channel
2877 state. Refactor the code to use convenience macros instead of
2878 checking channel state directly. Fixes issue 7356.
2879 - Document all members of was_router_added_t and rename
2880 ROUTER_WAS_NOT_NEW to ROUTER_IS_ALREADY_KNOWN to make it less
2881 confusable with ROUTER_WAS_TOO_OLD. Fixes issue 13644.
2882 - In connection_exit_begin_conn(), use END_CIRC_REASON_TORPROTOCOL
2883 constant instead of hardcoded value. Fixes issue 13840.
2884 - Refactor our generic strmap and digestmap types into a single
2885 implementation, so that we can add a new digest256map
2889 - Document the bridge-authority-only 'networkstatus-bridges' file.
2890 Closes ticket 13713; patch from "tom".
2891 - Fix typo in PredictedPortsRelevanceTime option description in
2892 manpage. Resolves issue 13707.
2893 - Stop suggesting that users specify relays by nickname: it isn't a
2894 good idea. Also, properly cross-reference how to specify relays in
2895 all parts of manual documenting options that take a list of
2896 relays. Closes ticket 13381.
2897 - Clarify the HiddenServiceDir option description in manpage to make
2898 it clear that relative paths are taken with respect to the current
2899 working directory. Also clarify that this behavior is not
2900 guaranteed to remain indefinitely. Fixes issue 13913.
2903 - New tests for many parts of channel, relay, and circuitmux
2904 functionality. Code by Andrea; part of 9262.
2905 - New tests for parse_transport_line(). Part of ticket 6456.
2906 - In the unit tests, use chgrp() to change the group of the unit
2907 test temporary directory to the current user, so that the sticky
2908 bit doesn't interfere with tests that check directory groups.
2910 - Add unit tests for resolve_my_addr(). Part of ticket 12376; patch
2914 Changes in version 0.2.6.1-alpha - 2014-10-30
2915 Tor 0.2.6.1-alpha is the first release in the Tor 0.2.6.x series. It
2916 includes numerous code cleanups and new tests, and fixes a large
2917 number of annoying bugs. Out-of-memory conditions are handled better
2918 than in 0.2.5, pluggable transports have improved proxy support, and
2919 clients now use optimistic data for contacting hidden services. Also,
2920 we are now more robust to changes in what we consider a parseable
2921 directory object, so that tightening restrictions does not have a risk
2922 of introducing infinite download loops.
2924 This is the first alpha release in a new series, so expect there to be
2925 bugs. Users who would rather test out a more stable branch should stay
2926 with 0.2.5.x for now.
2928 o New compiler and system requirements:
2929 - Tor 0.2.6.x requires that your compiler support more of the C99
2930 language standard than before. The 'configure' script now detects
2931 whether your compiler supports C99 mid-block declarations and
2932 designated initializers. If it does not, Tor will not compile.
2934 We may revisit this requirement if it turns out that a significant
2935 number of people need to build Tor with compilers that don't
2936 bother implementing a 15-year-old standard. Closes ticket 13233.
2937 - Tor no longer supports systems without threading support. When we
2938 began working on Tor, there were several systems that didn't have
2939 threads, or where the thread support wasn't able to run the
2940 threads of a single process on multiple CPUs. That no longer
2941 holds: every system where Tor needs to run well now has threading
2942 support. Resolves ticket 12439.
2944 o Removed platform support:
2945 - We no longer include special code to build on Windows CE; as far
2946 as we know, nobody has used Tor on Windows CE in a very long time.
2947 Closes ticket 11446.
2949 o Major features (bridges):
2950 - Expose the outgoing upstream HTTP/SOCKS proxy to pluggable
2951 transports if they are configured via the "TOR_PT_PROXY"
2952 environment variable. Implements proposal 232. Resolves
2955 o Major features (client performance, hidden services):
2956 - Allow clients to use optimistic data when connecting to a hidden
2957 service, which should remove a round-trip from hidden service
2958 initialization. See proposal 181 for details. Implements
2961 o Major features (directory system):
2962 - Upon receiving an unparseable directory object, if its digest
2963 matches what we expected, then don't try to download it again.
2964 Previously, when we got a descriptor we didn't like, we would keep
2965 trying to download it over and over. Closes ticket 11243.
2967 o Major features (sample torrc):
2968 - Add a new, infrequently-changed "torrc.minimal". This file is
2969 similar to torrc.sample, but it will change as infrequently as
2970 possible, for the benefit of users whose systems prompt them for
2971 intervention whenever a default configuration file is changed.
2972 Making this change allows us to update torrc.sample to be a more
2973 generally useful "sample torrc".
2975 o Major bugfixes (directory authorities):
2976 - Do not assign the HSDir flag to relays if they are not Valid, or
2977 currently hibernating. Fixes 12573; bugfix on 0.2.0.10-alpha.
2979 o Major bugfixes (directory bandwidth performance):
2980 - Don't flush the zlib buffer aggressively when compressing
2981 directory information for clients. This should save about 7% of
2982 the bandwidth currently used for compressed descriptors and
2983 microdescriptors. Fixes bug 11787; bugfix on 0.1.1.23.
2985 o Minor features (security, memory wiping):
2986 - Ensure we securely wipe keys from memory after
2987 crypto_digest_get_digest and init_curve25519_keypair_from_file
2988 have finished using them. Resolves ticket 13477.
2990 o Minor features (security, out-of-memory handling):
2991 - When handling an out-of-memory condition, allocate less memory for
2992 temporary data structures. Fixes issue 10115.
2993 - When handling an out-of-memory condition, consider more types of
2994 buffers, including those on directory connections, and zlib
2995 buffers. Resolves ticket 11792.
2998 - When identity keypair is generated for first time, log a
2999 congratulatory message that links to the new relay lifecycle
3000 document. Implements feature 10427.
3002 o Minor features (client):
3003 - Clients are now willing to send optimistic data (before they
3004 receive a 'connected' cell) to relays of any version. (Relays
3005 without support for optimistic data are no longer supported on the
3006 Tor network.) Resolves ticket 13153.
3008 o Minor features (directory authorities):
3009 - Don't list relays with a bandwidth estimate of 0 in the consensus.
3010 Implements a feature proposed during discussion of bug 13000.
3011 - In tor-gencert, report an error if the user provides the same
3012 argument more than once.
3013 - If a directory authority can't find a best consensus method in the
3014 votes that it holds, it now falls back to its favorite consensus
3015 method. Previously, it fell back to method 1. Neither of these is
3016 likely to get enough signatures, but "fall back to favorite"
3017 doesn't require us to maintain support an obsolete consensus
3018 method. Implements part of proposal 215.
3020 o Minor features (logging):
3021 - On Unix-like systems, you can now use named pipes as the target of
3022 the Log option, and other options that try to append to files.
3023 Closes ticket 12061. Patch from "carlo von lynX".
3024 - When opening a log file at startup, send it every log message that
3025 we generated between startup and opening it. Previously, log
3026 messages that were generated before opening the log file were only
3027 logged to stdout. Closes ticket 6938.
3028 - Add a TruncateLogFile option to overwrite logs instead of
3029 appending to them. Closes ticket 5583.
3031 o Minor features (portability, Solaris):
3032 - Threads are no longer disabled by default on Solaris; we believe
3033 that the versions of Solaris with broken threading support are all
3034 obsolete by now. Resolves ticket 9495.
3036 o Minor features (relay):
3037 - Re-check our address after we detect a changed IP address from
3038 getsockname(). This ensures that the controller command "GETINFO
3039 address" will report the correct value. Resolves ticket 11582.
3041 - A new AccountingRule option lets Relays set whether they'd like
3042 AccountingMax to be applied separately to inbound and outbound
3043 traffic, or applied to the sum of inbound and outbound traffic.
3044 Resolves ticket 961. Patch by "chobe".
3046 o Minor features (testing networks):
3047 - Add the TestingDirAuthVoteExit option, which lists nodes to assign
3048 the "Exit" flag regardless of their uptime, bandwidth, or exit
3049 policy. TestingTorNetwork must be set for this option to have any
3050 effect. Previously, authorities would take up to 35 minutes to
3051 give nodes the Exit flag in a test network. Partially implements
3054 o Minor features (validation):
3055 - Check all date/time values passed to tor_timegm and
3056 parse_rfc1123_time for validity, taking leap years into account.
3057 Improves HTTP header validation. Implemented with bug 13476.
3058 - In correct_tm(), limit the range of values returned by system
3059 localtime(_r) and gmtime(_r) to be between the years 1 and 8099.
3060 This means we don't have to deal with negative or too large dates,
3061 even if a clock is wrong. Otherwise we might fail to read a file
3062 written by us which includes such a date. Fixes bug 13476.
3064 o Minor bugfixes (bridge clients):
3065 - When configured to use a bridge without an identity digest (not
3066 recommended), avoid launching an extra channel to it when
3067 bootstrapping. Fixes bug 7733; bugfix on 0.2.4.4-alpha.
3069 o Minor bugfixes (bridges):
3070 - When DisableNetwork is set, do not launch pluggable transport
3071 plugins, and if any are running, terminate them. Fixes bug 13213;
3072 bugfix on 0.2.3.6-alpha.
3074 o Minor bugfixes (C correctness):
3075 - Fix several instances of possible integer overflow/underflow/NaN.
3076 Fixes bug 13104; bugfix on 0.2.3.1-alpha and later. Patches
3078 - In circuit_build_times_calculate_timeout() in circuitstats.c,
3079 avoid dividing by zero in the pareto calculations. This traps
3080 under clang's "undefined-trap" sanitizer. Fixes bug 13290; bugfix
3082 - Fix an integer overflow in format_time_interval(). Fixes bug
3083 13393; bugfix on 0.2.0.10-alpha.
3084 - Set the correct day of year value when the system's localtime(_r)
3085 or gmtime(_r) functions fail to set struct tm. Not externally
3086 visible. Fixes bug 13476; bugfix on 0.0.2pre14.
3087 - Avoid unlikely signed integer overflow in tor_timegm on systems
3088 with 32-bit time_t. Fixes bug 13476; bugfix on 0.0.2pre14.
3090 o Minor bugfixes (client):
3091 - Fix smartlist_choose_node_by_bandwidth() so that relays with the
3092 BadExit flag are not considered worthy candidates. Fixes bug
3093 13066; bugfix on 0.1.2.3-alpha.
3094 - Use the consensus schedule for downloading consensuses, and not
3095 the generic schedule. Fixes bug 11679; bugfix on 0.2.2.6-alpha.
3096 - Handle unsupported or malformed SOCKS5 requests properly by
3097 responding with the appropriate error message before closing the
3098 connection. Fixes bugs 12971 and 13314; bugfix on 0.0.2pre13.
3100 o Minor bugfixes (client, torrc):
3101 - Stop modifying the value of our DirReqStatistics torrc option just
3102 because we're not a bridge or relay. This bug was causing Tor
3103 Browser users to write "DirReqStatistics 0" in their torrc files
3104 as if they had chosen to change the config. Fixes bug 4244; bugfix
3106 - When GeoIPExcludeUnknown is enabled, do not incorrectly decide
3107 that our options have changed every time we SIGHUP. Fixes bug
3108 9801; bugfix on 0.2.4.10-alpha. Patch from "qwerty1".
3110 o Minor bugfixes (controller):
3111 - Return an error when the second or later arguments of the
3112 "setevents" controller command are invalid events. Previously we
3113 would return success while silently skipping invalid events. Fixes
3114 bug 13205; bugfix on 0.2.3.2-alpha. Reported by "fpxnns".
3116 o Minor bugfixes (directory system):
3117 - Always believe that v3 directory authorities serve extra-info
3118 documents, whether they advertise "caches-extra-info" or not.
3119 Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3120 - When running as a v3 directory authority, advertise that you serve
3121 extra-info documents so that clients who want them can find them
3122 from you too. Fixes part of bug 11683; bugfix on 0.2.0.1-alpha.
3123 - Check the BRIDGE_DIRINFO flag bitwise rather than using equality.
3124 Previously, directories offering BRIDGE_DIRINFO and some other
3125 flag (i.e. microdescriptors or extrainfo) would be ignored when
3126 looking for bridges. Partially fixes bug 13163; bugfix
3129 o Minor bugfixes (networking):
3130 - Check for orconns and use connection_or_close_for_error() rather
3131 than connection_mark_for_close() directly in the getsockopt()
3132 failure case of connection_handle_write_impl(). Fixes bug 11302;
3133 bugfix on 0.2.4.4-alpha.
3135 o Minor bugfixes (relay):
3136 - When generating our family list, remove spaces from around the
3137 entries. Fixes bug 12728; bugfix on 0.2.1.7-alpha.
3138 - If our previous bandwidth estimate was 0 bytes, allow publishing a
3139 new relay descriptor immediately. Fixes bug 13000; bugfix
3142 o Minor bugfixes (testing networks):
3143 - Fix TestingDirAuthVoteGuard to properly give out Guard flags in a
3144 testing network. Fixes bug 13064; bugfix on 0.2.5.2-alpha.
3145 - Stop using the default authorities in networks which provide both
3146 AlternateDirAuthority and AlternateBridgeAuthority. Partially
3147 fixes bug 13163; bugfix on 0.2.0.13-alpha.
3149 o Minor bugfixes (testing):
3150 - Stop spawn test failures due to a race condition between the
3151 SIGCHLD handler updating the process status, and the test reading
3152 it. Fixes bug 13291; bugfix on 0.2.3.3-alpha.
3154 o Minor bugfixes (testing, Windows):
3155 - Avoid passing an extra backslash when creating a temporary
3156 directory for running the unit tests on Windows. Fixes bug 12392;
3157 bugfix on 0.2.2.25-alpha. Patch from Gisle Vanem.
3159 o Minor bugfixes (windows):
3160 - Remove code to special-case handling of NTE_BAD_KEYSET when
3161 acquiring windows CryptoAPI context. This error can't actually
3162 occur for the parameters we're providing. Fixes bug 10816; bugfix
3165 o Minor bugfixes (zlib):
3166 - Avoid truncating a zlib stream when trying to finalize it with an
3167 empty output buffer. Fixes bug 11824; bugfix on 0.1.1.23.
3170 - Allow our configure script to build correctly with autoconf 2.62
3171 again. Fixes bug 12693; bugfix on 0.2.5.2-alpha.
3172 - Improve the error message from ./configure to make it clear that
3173 when asciidoc has not been found, the user will have to either add
3174 --disable-asciidoc argument or install asciidoc. Resolves
3177 o Code simplification and refactoring:
3178 - Change the entry_is_live() function to take named bitfield
3179 elements instead of an unnamed list of booleans. Closes
3181 - Refactor and unit-test entry_is_time_to_retry() in entrynodes.c.
3182 Resolves ticket 12205.
3183 - Use calloc and reallocarray functions instead of multiply-
3184 then-malloc. This makes it less likely for us to fall victim to an
3185 integer overflow attack when allocating. Resolves ticket 12855.
3186 - Use the standard macro name SIZE_MAX, instead of our
3188 - Document usage of the NO_DIRINFO and ALL_DIRINFO flags clearly in
3189 functions which take them as arguments. Replace 0 with NO_DIRINFO
3190 in a function call for clarity. Seeks to prevent future issues
3192 - Avoid 4 null pointer errors under clang static analysis by using
3193 tor_assert() to prove that the pointers aren't null. Fixes
3195 - Rework the API of policies_parse_exit_policy() to use a bitmask to
3196 represent parsing options, instead of a confusing mess of
3197 booleans. Resolves ticket 8197.
3198 - Introduce a helper function to parse ExitPolicy in
3199 or_options_t structure.
3202 - Add a doc/TUNING document with tips for handling large numbers of
3203 TCP connections when running busy Tor relay. Update the warning
3204 message to point to this file when running out of sockets
3205 operating system is allowing to use simultaneously. Resolves
3209 - We no longer remind the user about configuration options that have
3210 been obsolete since 0.2.3.x or earlier. Patch by Adrien Bak.
3211 - Remove our old, non-weighted bandwidth-based node selection code.
3212 Previously, we used it as a fallback when we couldn't perform
3213 weighted bandwidth-based node selection. But that would only
3214 happen in the cases where we had no consensus, or when we had a
3215 consensus generated by buggy or ancient directory authorities. In
3216 either case, it's better to use the more modern, better maintained
3217 algorithm, with reasonable defaults for the weights. Closes
3219 - Remove the --disable-curve25519 configure option. Relays and
3220 clients now are required to support curve25519 and the
3222 - The old "StrictEntryNodes" and "StrictExitNodes" options, which
3223 used to be deprecated synonyms for "StrictNodes", are now marked
3224 obsolete. Resolves ticket 12226.
3225 - Clients don't understand the BadDirectory flag in the consensus
3226 anymore, and ignore it.
3229 - Refactor the function that chooses guard nodes so that it can more
3230 easily be tested; write some tests for it.
3231 - Fix and re-enable the fgets_eagain unit test. Fixes bug 12503;
3232 bugfix on 0.2.3.1-alpha. Patch from "cypherpunks."
3233 - Create unit tests for format_time_interval(). With bug 13393.
3234 - Add unit tests for tor_timegm signed overflow, tor_timegm and
3235 parse_rfc1123_time validity checks, correct_tm year clamping. Unit
3236 tests (visible) fixes in bug 13476.
3237 - Add a "coverage-html" make target to generate HTML-visualized
3238 coverage results when building with --enable-coverage. (Requires
3239 lcov.) Patch from Kevin Murray.
3240 - Enable the backtrace handler (where supported) when running the
3242 - Revise all unit tests that used the legacy test_* macros to
3243 instead use the recommended tt_* macros. This patch was generated
3244 with coccinelle, to avoid manual errors. Closes ticket 13119.
3246 o Distribution (systemd):
3247 - systemd unit file: only allow tor to write to /var/lib/tor and
3248 /var/log/tor. The rest of the filesystem is accessible for reading
3249 only. Patch by intrigeri; resolves ticket 12751.
3250 - systemd unit file: ensure that the process and all its children
3251 can never gain new privileges. Patch by intrigeri; resolves
3253 - systemd unit file: set up /var/run/tor as writable for the Tor
3254 service. Patch by intrigeri; resolves ticket 13196.
3256 o Removed features (directory authorities):
3257 - Remove code that prevented authorities from listing Tor relays
3258 affected by CVE-2011-2769 as guards. These relays are already
3259 rejected altogether due to the minimum version requirement of
3260 0.2.3.16-alpha. Closes ticket 13152.
3261 - The "AuthDirRejectUnlisted" option no longer has any effect, as
3262 the fingerprints file (approved-routers) has been deprecated.
3263 - Directory authorities do not support being Naming dirauths anymore.
3264 The "NamingAuthoritativeDir" config option is now obsolete.
3265 - Directory authorities do not support giving out the BadDirectory
3267 - Directory authorities no longer advertise or support consensus
3268 methods 1 through 12 inclusive. These consensus methods were
3269 obsolete and/or insecure: maintaining the ability to support them
3270 served no good purpose. Implements part of proposal 215; closes
3273 o Testing (test-network.sh):
3274 - Stop using "echo -n", as some shells' built-in echo doesn't
3275 support "-n". Instead, use "/bin/echo -n". Partially fixes
3277 - Stop an apparent test-network hang when used with make -j2. Fixes
3279 - Add a --delay option to test-network.sh, which configures the
3280 delay before the chutney network tests for data transmission.
3281 Partially implements ticket 13161.
3284 Changes in version 0.2.5.10 - 2014-10-24
3285 Tor 0.2.5.10 is the first stable release in the 0.2.5 series.
3287 It adds several new security features, including improved
3288 denial-of-service resistance for relays, new compiler hardening
3289 options, and a system-call sandbox for hardened installations on Linux
3290 (requires seccomp2). The controller protocol has several new features,
3291 resolving IPv6 addresses should work better than before, and relays
3292 should be a little more CPU-efficient. We've added support for more
3293 OpenBSD and FreeBSD transparent proxy types. We've improved the build
3294 system and testing infrastructure to allow unit testing of more parts
3295 of the Tor codebase. Finally, we've addressed several nagging pluggable
3296 transport usability issues, and included numerous other small bugfixes
3297 and features mentioned below.
3299 This release marks end-of-life for Tor 0.2.3.x; those Tor versions
3300 have accumulated many known flaws; everyone should upgrade.
3302 o Deprecated versions:
3303 - Tor 0.2.3.x has reached end-of-life; it has received no patches or
3304 attention for some while.
3307 Changes in version 0.2.5.9-rc - 2014-10-20
3308 Tor 0.2.5.9-rc is the third release candidate for the Tor 0.2.5.x
3309 series. It disables SSL3 in response to the recent "POODLE" attack
3310 (even though POODLE does not affect Tor). It also works around a crash
3311 bug caused by some operating systems' response to the "POODLE" attack
3312 (which does affect Tor). It also contains a few miscellaneous fixes.
3314 o Major security fixes:
3315 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3316 today support TLS 1.0 or later, so we can safely turn off support
3317 for this old (and insecure) protocol. Fixes bug 13426.
3319 o Major bugfixes (openssl bug workaround):
3320 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3321 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3322 13471. This is a workaround for an OpenSSL bug.
3325 - Disable the sandbox name resolver cache when running tor-resolve:
3326 tor-resolve doesn't use the sandbox code, and turning it on was
3327 breaking attempts to do tor-resolve on a non-default server on
3328 Linux. Fixes bug 13295; bugfix on 0.2.5.3-alpha.
3330 o Compilation fixes:
3331 - Build and run correctly on systems like OpenBSD-current that have
3332 patched OpenSSL to remove get_cipher_by_char and/or its
3333 implementations. Fixes issue 13325.
3335 o Downgraded warnings:
3336 - Downgrade the severity of the 'unexpected sendme cell from client'
3337 from 'warn' to 'protocol warning'. Closes ticket 8093.
3340 Changes in version 0.2.4.25 - 2014-10-20
3341 Tor 0.2.4.25 disables SSL3 in response to the recent "POODLE" attack
3342 (even though POODLE does not affect Tor). It also works around a crash
3343 bug caused by some operating systems' response to the "POODLE" attack
3344 (which does affect Tor).
3346 o Major security fixes (also in 0.2.5.9-rc):
3347 - Disable support for SSLv3. All versions of OpenSSL in use with Tor
3348 today support TLS 1.0 or later, so we can safely turn off support
3349 for this old (and insecure) protocol. Fixes bug 13426.
3351 o Major bugfixes (openssl bug workaround, also in 0.2.5.9-rc):
3352 - Avoid crashing when using OpenSSL version 0.9.8zc, 1.0.0o, or
3353 1.0.1j, built with the 'no-ssl3' configuration option. Fixes bug
3354 13471. This is a workaround for an OpenSSL bug.
3357 Changes in version 0.2.5.8-rc - 2014-09-22
3358 Tor 0.2.5.8-rc is the second release candidate for the Tor 0.2.5.x
3359 series. It fixes a bug that affects consistency and speed when
3360 connecting to hidden services, and it updates the location of one of
3361 the directory authorities.
3364 - Clients now send the correct address for their chosen rendezvous
3365 point when trying to access a hidden service. They used to send
3366 the wrong address, which would still work some of the time because
3367 they also sent the identity digest of the rendezvous point, and if
3368 the hidden service happened to try connecting to the rendezvous
3369 point from a relay that already had a connection open to it,
3370 the relay would reuse that connection. Now connections to hidden
3371 services should be more robust and faster. Also, this bug meant
3372 that clients were leaking to the hidden service whether they were
3373 on a little-endian (common) or big-endian (rare) system, which for
3374 some users might have reduced their anonymity. Fixes bug 13151;
3375 bugfix on 0.2.1.5-alpha.
3377 o Directory authority changes:
3378 - Change IP address for gabelmoo (v3 directory authority).
3381 Changes in version 0.2.4.24 - 2014-09-22
3382 Tor 0.2.4.24 fixes a bug that affects consistency and speed when
3383 connecting to hidden services, and it updates the location of one of
3384 the directory authorities.
3387 - Clients now send the correct address for their chosen rendezvous
3388 point when trying to access a hidden service. They used to send
3389 the wrong address, which would still work some of the time because
3390 they also sent the identity digest of the rendezvous point, and if
3391 the hidden service happened to try connecting to the rendezvous
3392 point from a relay that already had a connection open to it,
3393 the relay would reuse that connection. Now connections to hidden
3394 services should be more robust and faster. Also, this bug meant
3395 that clients were leaking to the hidden service whether they were
3396 on a little-endian (common) or big-endian (rare) system, which for
3397 some users might have reduced their anonymity. Fixes bug 13151;
3398 bugfix on 0.2.1.5-alpha.
3400 o Directory authority changes:
3401 - Change IP address for gabelmoo (v3 directory authority).
3403 o Minor features (geoip):
3404 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3408 Changes in version 0.2.5.7-rc - 2014-09-11
3409 Tor 0.2.5.7-rc fixes several regressions from earlier in the 0.2.5.x
3410 release series, and some long-standing bugs related to ORPort reachability
3411 testing and failure to send CREATE cells. It is the first release
3412 candidate for the Tor 0.2.5.x series.
3414 o Major bugfixes (client, startup):
3415 - Start making circuits as soon as DisabledNetwork is turned off.
3416 When Tor started with DisabledNetwork set, it would correctly
3417 conclude that it shouldn't build circuits, but it would mistakenly
3418 cache this conclusion, and continue believing it even when
3419 DisableNetwork is set to 0. Fixes the bug introduced by the fix
3420 for bug 11200; bugfix on 0.2.5.4-alpha.
3421 - Resume expanding abbreviations for command-line options. The fix
3422 for bug 4647 accidentally removed our hack from bug 586 that
3423 rewrote HashedControlPassword to __HashedControlSessionPassword
3424 when it appears on the commandline (which allowed the user to set
3425 her own HashedControlPassword in the torrc file while the
3426 controller generates a fresh session password for each run). Fixes
3427 bug 12948; bugfix on 0.2.5.1-alpha.
3428 - Warn about attempts to run hidden services and relays in the same
3429 process: that's probably not a good idea. Closes ticket 12908.
3431 o Major bugfixes (relay):
3432 - Avoid queuing or sending destroy cells for circuit ID zero when we
3433 fail to send a CREATE cell. Fixes bug 12848; bugfix on 0.0.8pre1.
3434 Found and fixed by "cypherpunks".
3435 - Fix ORPort reachability detection on relays running behind a
3436 proxy, by correctly updating the "local" mark on the controlling
3437 channel when changing the address of an or_connection_t after the
3438 handshake. Fixes bug 12160; bugfix on 0.2.4.4-alpha.
3440 o Minor features (bridge):
3441 - Add an ExtORPortCookieAuthFileGroupReadable option to make the
3442 cookie file for the ExtORPort g+r by default.
3444 o Minor features (geoip):
3445 - Update geoip and geoip6 to the August 7 2014 Maxmind GeoLite2
3448 o Minor bugfixes (logging):
3449 - Reduce the log severity of the "Pluggable transport proxy does not
3450 provide any needed transports and will not be launched." message,
3451 since Tor Browser includes several ClientTransportPlugin lines in
3452 its torrc-defaults file, leading every Tor Browser user who looks
3453 at her logs to see these notices and wonder if they're dangerous.
3454 Resolves bug 13124; bugfix on 0.2.5.3-alpha.
3455 - Downgrade "Unexpected onionskin length after decryption" warning
3456 to a protocol-warn, since there's nothing relay operators can do
3457 about a client that sends them a malformed create cell. Resolves
3458 bug 12996; bugfix on 0.0.6rc1.
3459 - Log more specific warnings when we get an ESTABLISH_RENDEZVOUS
3460 cell on a cannibalized or non-OR circuit. Resolves ticket 12997.
3461 - When logging information about an EXTEND2 or EXTENDED2 cell, log
3462 their names correctly. Fixes part of bug 12700; bugfix
3464 - When logging information about a relay cell whose command we don't
3465 recognize, log its command as an integer. Fixes part of bug 12700;
3466 bugfix on 0.2.1.10-alpha.
3467 - Escape all strings from the directory connection before logging
3468 them. Fixes bug 13071; bugfix on 0.1.1.15. Patch from "teor".
3470 o Minor bugfixes (controller):
3471 - Restore the functionality of CookieAuthFileGroupReadable. Fixes
3472 bug 12864; bugfix on 0.2.5.1-alpha.
3473 - Actually send TRANSPORT_LAUNCHED and HS_DESC events to
3474 controllers. Fixes bug 13085; bugfix on 0.2.5.1-alpha. Patch
3477 o Minor bugfixes (compilation):
3478 - Fix compilation of test.h with MSVC. Patch from Gisle Vanem;
3479 bugfix on 0.2.5.5-alpha.
3480 - Make the nmake make files work again. Fixes bug 13081. Bugfix on
3481 0.2.5.1-alpha. Patch from "NewEraCracker".
3482 - In routerlist_assert_ok(), don't take the address of a
3483 routerinfo's cache_info member unless that routerinfo is non-NULL.
3484 Fixes bug 13096; bugfix on 0.1.1.9-alpha. Patch by "teor".
3485 - Fix a large number of false positive warnings from the clang
3486 analyzer static analysis tool. This should make real warnings
3487 easier for clang analyzer to find. Patch from "teor". Closes
3490 o Distribution (systemd):
3491 - Verify configuration file via ExecStartPre in the systemd unit
3492 file. Patch from intrigeri; resolves ticket 12730.
3493 - Explicitly disable RunAsDaemon in the systemd unit file. Our
3494 current systemd unit uses "Type = simple", so systemd does not
3495 expect tor to fork. If the user has "RunAsDaemon 1" in their
3496 torrc, then things won't work as expected. This is e.g. the case
3497 on Debian (and derivatives), since there we pass "--defaults-torrc
3498 /usr/share/tor/tor-service-defaults-torrc" (that contains
3499 "RunAsDaemon 1") by default. Patch by intrigeri; resolves
3503 - Adjust the URLs in the README to refer to the new locations of
3504 several documents on the website. Fixes bug 12830. Patch from
3506 - Document 'reject6' and 'accept6' ExitPolicy entries. Resolves
3510 Changes in version 0.2.5.6-alpha - 2014-07-28
3511 Tor 0.2.5.6-alpha brings us a big step closer to slowing down the
3512 risk from guard rotation, and fixes a variety of other issues to get
3513 us closer to a release candidate.
3515 o Major features (also in 0.2.4.23):
3516 - Make the number of entry guards configurable via a new
3517 NumEntryGuards consensus parameter, and the number of directory
3518 guards configurable via a new NumDirectoryGuards consensus
3519 parameter. Implements ticket 12688.
3521 o Major bugfixes (also in 0.2.4.23):
3522 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3523 implementation that caused incorrect results on 32-bit
3524 implementations when certain malformed inputs were used along with
3525 a small class of private ntor keys. This bug does not currently
3526 appear to allow an attacker to learn private keys or impersonate a
3527 Tor server, but it could provide a means to distinguish 32-bit Tor
3528 implementations from 64-bit Tor implementations. Fixes bug 12694;
3529 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3533 - Perform circuit cleanup operations even when circuit
3534 construction operations are disabled (because the network is
3535 disabled, or because there isn't enough directory information).
3536 Previously, when we were not building predictive circuits, we
3537 were not closing expired circuits either. Fixes bug 8387; bugfix on
3538 0.1.1.11-alpha. This bug became visible in 0.2.4.10-alpha when we
3539 became more strict about when we have "enough directory information
3543 - Authorities now assign the Guard flag to the fastest 25% of the
3544 network (it used to be the fastest 50%). Also raise the consensus
3545 weight that guarantees the Guard flag from 250 to 2000. For the
3546 current network, this results in about 1100 guards, down from 2500.
3547 This step paves the way for moving the number of entry guards
3548 down to 1 (proposal 236) while still providing reasonable expected
3549 performance for most users. Implements ticket 12690.
3550 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3552 - Slightly enhance the diagnostic message for bug 12184.
3554 o Minor bugfixes (also in 0.2.4.23):
3555 - Warn and drop the circuit if we receive an inbound 'relay early'
3556 cell. Those used to be normal to receive on hidden service circuits
3557 due to bug 1038, but the buggy Tor versions are long gone from
3558 the network so we can afford to resume watching for them. Resolves
3559 the rest of bug 1038; bugfix on 0.2.1.19.
3560 - Correct a confusing error message when trying to extend a circuit
3561 via the control protocol but we don't know a descriptor or
3562 microdescriptor for one of the specified relays. Fixes bug 12718;
3563 bugfix on 0.2.3.1-alpha.
3566 - Fix compilation when building with bufferevents enabled. (This
3567 configuration is still not expected to work, however.)
3568 Fixes bugs 12438, 12474, 11578; bugfixes on 0.2.5.1-alpha and
3569 0.2.5.3-alpha. Patches from Anthony G. Basile and Sathyanarayanan
3571 - Compile correctly with builds and forks of OpenSSL (such as
3572 LibreSSL) that disable compression. Fixes bug 12602; bugfix on
3573 0.2.1.1-alpha. Patch from "dhill".
3576 Changes in version 0.2.4.23 - 2014-07-28
3577 Tor 0.2.4.23 brings us a big step closer to slowing down the risk from
3578 guard rotation, and also backports several important fixes from the
3579 Tor 0.2.5 alpha release series.
3582 - Clients now look at the "usecreatefast" consensus parameter to
3583 decide whether to use CREATE_FAST or CREATE cells for the first hop
3584 of their circuit. This approach can improve security on connections
3585 where Tor's circuit handshake is stronger than the available TLS
3586 connection security levels, but the tradeoff is more computational
3587 load on guard relays. Implements proposal 221. Resolves ticket 9386.
3588 - Make the number of entry guards configurable via a new
3589 NumEntryGuards consensus parameter, and the number of directory
3590 guards configurable via a new NumDirectoryGuards consensus
3591 parameter. Implements ticket 12688.
3594 - Fix a bug in the bounds-checking in the 32-bit curve25519-donna
3595 implementation that caused incorrect results on 32-bit
3596 implementations when certain malformed inputs were used along with
3597 a small class of private ntor keys. This bug does not currently
3598 appear to allow an attacker to learn private keys or impersonate a
3599 Tor server, but it could provide a means to distinguish 32-bit Tor
3600 implementations from 64-bit Tor implementations. Fixes bug 12694;
3601 bugfix on 0.2.4.8-alpha. Bug found by Robert Ransom; fix from
3605 - Warn and drop the circuit if we receive an inbound 'relay early'
3606 cell. Those used to be normal to receive on hidden service circuits
3607 due to bug 1038, but the buggy Tor versions are long gone from
3608 the network so we can afford to resume watching for them. Resolves
3609 the rest of bug 1038; bugfix on 0.2.1.19.
3610 - Correct a confusing error message when trying to extend a circuit
3611 via the control protocol but we don't know a descriptor or
3612 microdescriptor for one of the specified relays. Fixes bug 12718;
3613 bugfix on 0.2.3.1-alpha.
3614 - Avoid an illegal read from stack when initializing the TLS
3615 module using a version of OpenSSL without all of the ciphers
3616 used by the v2 link handshake. Fixes bug 12227; bugfix on
3617 0.2.4.8-alpha. Found by "starlight".
3620 - Update geoip and geoip6 to the July 10 2014 Maxmind GeoLite2
3624 Changes in version 0.2.5.5-alpha - 2014-06-18
3625 Tor 0.2.5.5-alpha fixes a wide variety of remaining issues in the Tor
3626 0.2.5.x release series, including a couple of DoS issues, some
3627 performance regressions, a large number of bugs affecting the Linux
3628 seccomp2 sandbox code, and various other bugfixes. It also adds
3629 diagnostic bugfixes for a few tricky issues that we're trying to
3632 o Major features (security, traffic analysis resistance):
3633 - Several major improvements to the algorithm used to decide when to
3634 close TLS connections. Previous versions of Tor closed connections
3635 at a fixed interval after the last time a non-padding cell was
3636 sent over the connection, regardless of the target of the
3637 connection. Now, we randomize the intervals by adding up to 50% of
3638 their base value, we measure the length of time since connection
3639 last had at least one circuit, and we allow connections to known
3640 ORs to remain open a little longer (15 minutes instead of 3
3641 minutes minimum). These changes should improve Tor's resistance
3642 against some kinds of traffic analysis, and lower some overhead
3643 from needlessly closed connections. Fixes ticket 6799.
3644 Incidentally fixes ticket 12023; bugfix on 0.2.5.1-alpha.
3646 o Major bugfixes (security, OOM, new since 0.2.5.4-alpha, also in 0.2.4.22):
3647 - Fix a memory leak that could occur if a microdescriptor parse
3648 fails during the tokenizing step. This bug could enable a memory
3649 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3652 o Major bugfixes (security, directory authorities):
3653 - Directory authorities now include a digest of each relay's
3654 identity key as a part of its microdescriptor.
3656 This is a workaround for bug 11743 (reported by "cypherpunks"),
3657 where Tor clients do not support receiving multiple
3658 microdescriptors with the same SHA256 digest in the same
3659 consensus. When clients receive a consensus like this, they only
3660 use one of the relays. Without this fix, a hostile relay could
3661 selectively disable some client use of target relays by
3662 constructing a router descriptor with a different identity and the
3663 same microdescriptor parameters and getting the authorities to
3664 list it in a microdescriptor consensus. This fix prevents an
3665 attacker from causing a microdescriptor collision, because the
3666 router's identity is not forgeable.
3668 o Major bugfixes (relay):
3669 - Use a direct dirport connection when uploading non-anonymous
3670 descriptors to the directory authorities. Previously, relays would
3671 incorrectly use tunnel connections under a fairly wide variety of
3672 circumstances. Fixes bug 11469; bugfix on 0.2.4.3-alpha.
3673 - When a circuit accidentally has the same circuit ID for its
3674 forward and reverse direction, correctly detect the direction of
3675 cells using that circuit. Previously, this bug made roughly one
3676 circuit in a million non-functional. Fixes bug 12195; this is a
3677 bugfix on every version of Tor.
3679 o Major bugfixes (client, pluggable transports):
3680 - When managing pluggable transports, use OS notification facilities
3681 to learn if they have crashed, and don't attempt to kill any
3682 process that has already exited. Fixes bug 8746; bugfix
3685 o Minor features (diagnostic):
3686 - When logging a warning because of bug 7164, additionally check the
3687 hash table for consistency (as proposed on ticket 11737). This may
3688 help diagnose bug 7164.
3689 - When we log a heartbeat, log how many one-hop circuits we have
3690 that are at least 30 minutes old, and log status information about
3691 a few of them. This is an attempt to track down bug 8387.
3692 - When encountering an unexpected CR while writing text to a file on
3693 Windows, log the name of the file. Should help diagnosing
3695 - Give more specific warnings when a client notices that an onion
3696 handshake has failed. Fixes ticket 9635.
3697 - Add significant new logging code to attempt to diagnose bug 12184,
3698 where relays seem to run out of available circuit IDs.
3699 - Improve the diagnostic log message for bug 8387 even further to
3700 try to improve our odds of figuring out why one-hop directory
3701 circuits sometimes do not get closed.
3703 o Minor features (security, memory management):
3704 - Memory allocation tricks (mempools and buffer freelists) are now
3705 disabled by default. You can turn them back on with
3706 --enable-mempools and --enable-buf-freelists respectively. We're
3707 disabling these features because malloc performance is good enough
3708 on most platforms, and a similar feature in OpenSSL exacerbated
3709 exploitation of the Heartbleed attack. Resolves ticket 11476.
3711 o Minor features (security):
3712 - Apply the secure SipHash-2-4 function to the hash table mapping
3713 circuit IDs and channels to circuits. We missed this one when we
3714 were converting all the other hash functions to use SipHash back
3715 in 0.2.5.3-alpha. Resolves ticket 11750.
3717 o Minor features (build):
3718 - The configure script has a --disable-seccomp option to turn off
3719 support for libseccomp on systems that have it, in case it (or
3720 Tor's use of it) is broken. Resolves ticket 11628.
3722 o Minor features (other):
3723 - Update geoip and geoip6 to the June 4 2014 Maxmind GeoLite2
3726 o Minor bugfixes (security, new since 0.2.5.4-alpha, also in 0.2.4.22):
3727 - When running a hidden service, do not allow TunneledDirConns 0;
3728 this will keep the hidden service from running, and also
3729 make it publish its descriptors directly over HTTP. Fixes bug 10849;
3730 bugfix on 0.2.1.1-alpha.
3732 o Minor bugfixes (performance):
3733 - Avoid a bug where every successful connection made us recompute
3734 the flag telling us whether we have sufficient information to
3735 build circuits. Previously, we would forget our cached value
3736 whenever we successfully opened a channel (or marked a router as
3737 running or not running for any other reason), regardless of
3738 whether we had previously believed the router to be running. This
3739 forced us to run an expensive update operation far too often.
3740 Fixes bug 12170; bugfix on 0.1.2.1-alpha.
3741 - Avoid using tor_memeq() for checking relay cell integrity. This
3742 removes a possible performance bottleneck. Fixes part of bug
3743 12169; bugfix on 0.2.1.31.
3745 o Minor bugfixes (compilation):
3746 - Fix compilation of test_status.c when building with MVSC. Bugfix
3747 on 0.2.5.4-alpha. Patch from Gisle Vanem.
3748 - Resolve GCC complaints on OpenBSD about discarding constness in
3749 TO_{ORIGIN,OR}_CIRCUIT functions. Fixes part of bug 11633; bugfix
3750 on 0.1.1.23. Patch from Dana Koch.
3751 - Resolve clang complaints on OpenBSD with -Wshorten-64-to-32 due to
3752 treatment of long and time_t as comparable types. Fixes part of
3753 bug 11633. Patch from Dana Koch.
3754 - Make Tor compile correctly with --disable-buf-freelists. Fixes bug
3755 11623; bugfix on 0.2.5.3-alpha.
3756 - When deciding whether to build the 64-bit curve25519
3757 implementation, detect platforms where we can compile 128-bit
3758 arithmetic but cannot link it. Fixes bug 11729; bugfix on
3759 0.2.4.8-alpha. Patch from "conradev".
3760 - Fix compilation when DNS_CACHE_DEBUG is enabled. Fixes bug 11761;
3761 bugfix on 0.2.3.13-alpha. Found by "cypherpunks".
3762 - Fix compilation with dmalloc. Fixes bug 11605; bugfix
3765 o Minor bugfixes (Directory server):
3766 - When sending a compressed set of descriptors or microdescriptors,
3767 make sure to finalize the zlib stream. Previously, we would write
3768 all the compressed data, but if the last descriptor we wanted to
3769 send was missing or too old, we would not mark the stream as
3770 finished. This caused problems for decompression tools. Fixes bug
3771 11648; bugfix on 0.1.1.23.
3773 o Minor bugfixes (Linux seccomp sandbox):
3774 - Make the seccomp sandbox code compile under ARM Linux. Fixes bug
3775 11622; bugfix on 0.2.5.1-alpha.
3776 - Avoid crashing when re-opening listener ports with the seccomp
3777 sandbox active. Fixes bug 12115; bugfix on 0.2.5.1-alpha.
3778 - Avoid crashing with the seccomp sandbox enabled along with
3779 ConstrainedSockets. Fixes bug 12139; bugfix on 0.2.5.1-alpha.
3780 - When we receive a SIGHUP with the sandbox enabled, correctly
3781 support rotating our log files. Fixes bug 12032; bugfix
3783 - Avoid crash when running with sandboxing enabled and
3784 DirReqStatistics not disabled. Fixes bug 12035; bugfix
3786 - Fix a "BUG" warning when trying to write bridge-stats files with
3787 the Linux syscall sandbox filter enabled. Fixes bug 12041; bugfix
3789 - Prevent the sandbox from crashing on startup when run with the
3790 --enable-expensive-hardening configuration option. Fixes bug
3791 11477; bugfix on 0.2.5.4-alpha.
3792 - When running with DirPortFrontPage and sandboxing both enabled,
3793 reload the DirPortFrontPage correctly when restarting. Fixes bug
3794 12028; bugfix on 0.2.5.1-alpha.
3795 - Don't try to enable the sandbox when using the Tor binary to check
3796 its configuration, hash a passphrase, or so on. Doing so was
3797 crashing on startup for some users. Fixes bug 11609; bugfix
3799 - Avoid warnings when running with sandboxing and node statistics
3800 enabled at the same time. Fixes part of 12064; bugfix on
3801 0.2.5.1-alpha. Patch from Michael Wolf.
3802 - Avoid warnings when running with sandboxing enabled at the same
3803 time as cookie authentication, hidden services, or directory
3804 authority voting. Fixes part of 12064; bugfix on 0.2.5.1-alpha.
3805 - Do not allow options that require calls to exec to be enabled
3806 alongside the seccomp2 sandbox: they will inevitably crash. Fixes
3807 bug 12043; bugfix on 0.2.5.1-alpha.
3808 - Handle failures in getpwnam()/getpwuid() when running with the
3809 User option set and the Linux syscall sandbox enabled. Fixes bug
3810 11946; bugfix on 0.2.5.1-alpha.
3811 - Refactor the getaddrinfo workaround that the seccomp sandbox uses
3812 to avoid calling getaddrinfo() after installing the sandbox
3813 filters. Previously, it preloaded a cache with the IPv4 address
3814 for our hostname, and nothing else. Now, it loads the cache with
3815 every address that it used to initialize the Tor process. Fixes
3816 bug 11970; bugfix on 0.2.5.1-alpha.
3818 o Minor bugfixes (pluggable transports):
3819 - Enable the ExtORPortCookieAuthFile option, to allow changing the
3820 default location of the authentication token for the extended OR
3821 Port as used by sever-side pluggable transports. We had
3822 implemented this option before, but the code to make it settable
3823 had been omitted. Fixes bug 11635; bugfix on 0.2.5.1-alpha.
3824 - Avoid another 60-second delay when starting Tor in a pluggable-
3825 transport-using configuration when we already have cached
3826 descriptors for our bridges. Fixes bug 11965; bugfix
3829 o Minor bugfixes (client):
3830 - Avoid "Tried to open a socket with DisableNetwork set" warnings
3831 when starting a client with bridges configured and DisableNetwork
3832 set. (Tor launcher starts Tor with DisableNetwork set the first
3833 time it runs.) Fixes bug 10405; bugfix on 0.2.3.9-alpha.
3835 o Minor bugfixes (testing):
3836 - The Python parts of the test scripts now work on Python 3 as well
3837 as Python 2, so systems where '/usr/bin/python' is Python 3 will
3838 no longer have the tests break. Fixes bug 11608; bugfix
3840 - When looking for versions of python that we could run the tests
3841 with, check for "python2.7" and "python3.3"; previously we were
3842 only looking for "python", "python2", and "python3". Patch from
3843 Dana Koch. Fixes bug 11632; bugfix on 0.2.5.2-alpha.
3844 - Fix all valgrind warnings produced by the unit tests. There were
3845 over a thousand memory leak warnings previously, mostly produced
3846 by forgetting to free things in the unit test code. Fixes bug
3847 11618, bugfixes on many versions of Tor.
3849 o Minor bugfixes (tor-fw-helper):
3850 - Give a correct log message when tor-fw-helper fails to launch.
3851 (Previously, we would say something like "tor-fw-helper sent us a
3852 string we could not parse".) Fixes bug 9781; bugfix
3855 o Minor bugfixes (relay, threading):
3856 - Check return code on spawn_func() in cpuworker code, so that we
3857 don't think we've spawned a nonworking cpuworker and write junk to
3858 it forever. Fix related to bug 4345; bugfix on all released Tor
3859 versions. Found by "skruffy".
3860 - Use a pthread_attr to make sure that spawn_func() cannot return an
3861 error while at the same time launching a thread. Fix related to
3862 bug 4345; bugfix on all released Tor versions. Reported
3865 o Minor bugfixes (relay, oom prevention):
3866 - Correctly detect the total available system memory. We tried to do
3867 this in 0.2.5.4-alpha, but the code was set up to always return an
3868 error value, even on success. Fixes bug 11805; bugfix
3871 o Minor bugfixes (relay, other):
3872 - We now drop CREATE cells for already-existent circuit IDs and for
3873 zero-valued circuit IDs, regardless of other factors that might
3874 otherwise have called for DESTROY cells. Fixes bug 12191; bugfix
3876 - Avoid an illegal read from stack when initializing the TLS module
3877 using a version of OpenSSL without all of the ciphers used by the
3878 v2 link handshake. Fixes bug 12227; bugfix on 0.2.4.8-alpha. Found
3880 - When rejecting DATA cells for stream_id zero, still count them
3881 against the circuit's deliver window so that we don't fail to send
3882 a SENDME. Fixes bug 11246; bugfix on 0.2.4.10-alpha.
3884 o Minor bugfixes (logging):
3885 - Fix a misformatted log message about delayed directory fetches.
3886 Fixes bug 11654; bugfix on 0.2.5.3-alpha.
3887 - Squelch a spurious LD_BUG message "No origin circuit for
3888 successful SOCKS stream" in certain hidden service failure cases;
3892 - Include a tor.service file in contrib/dist for use with systemd.
3893 Some distributions will be able to use this file unmodified;
3894 others will need to tweak it, or write their own. Patch from Jamie
3895 Nguyen; resolves ticket 8368.
3898 - Clean up several option names in the manpage to match their real
3899 names, add the missing documentation for a couple of testing and
3900 directory authority options, remove the documentation for a
3901 V2-directory fetching option that no longer exists. Resolves
3903 - Correct the documenation so that it lists the correct directory
3904 for the stats files. (They are in a subdirectory called "stats",
3906 - In the manpage, move more authority-only options into the
3907 directory authority section so that operators of regular directory
3908 caches don't get confused.
3911 - The contrib directory has been sorted and tidied. Before, it was
3912 an unsorted dumping ground for useful and not-so-useful things.
3913 Now, it is divided based on functionality, and the items which
3914 seemed to be nonfunctional or useless have been removed. Resolves
3915 ticket 8966; based on patches from "rl1987".
3918 - Remove /tor/dbg-stability.txt URL that was meant to help debug WFU
3919 and MTBF calculations, but that nobody was using. Fixes ticket 11742.
3920 - The TunnelDirConns and PreferTunnelledDirConns options no longer
3921 exist; tunneled directory connections have been available since
3922 0.1.2.5-alpha, and turning them off is not a good idea. This is a
3923 brute-force fix for 10849, where "TunnelDirConns 0" would break
3927 Changes in version 0.2.4.22 - 2014-05-16
3928 Tor 0.2.4.22 backports numerous high-priority fixes from the Tor 0.2.5
3929 alpha release series. These include blocking all authority signing
3930 keys that may have been affected by the OpenSSL "heartbleed" bug,
3931 choosing a far more secure set of TLS ciphersuites by default, closing
3932 a couple of memory leaks that could be used to run a target relay out
3933 of RAM, and several others.
3935 o Major features (security, backport from 0.2.5.4-alpha):
3936 - Block authority signing keys that were used on authorities
3937 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
3938 don't have any evidence that these keys _were_ compromised; we're
3939 doing this to be prudent.) Resolves ticket 11464.
3941 o Major bugfixes (security, OOM):
3942 - Fix a memory leak that could occur if a microdescriptor parse
3943 fails during the tokenizing step. This bug could enable a memory
3944 exhaustion attack by directory servers. Fixes bug 11649; bugfix
3947 o Major bugfixes (TLS cipher selection, backport from 0.2.5.4-alpha):
3948 - The relay ciphersuite list is now generated automatically based on
3949 uniform criteria, and includes all OpenSSL ciphersuites with
3950 acceptable strength and forward secrecy. Previously, we had left
3951 some perfectly fine ciphersuites unsupported due to omission or
3952 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
3953 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
3954 - Relays now trust themselves to have a better view than clients of
3955 which TLS ciphersuites are better than others. (Thanks to bug
3956 11513, the relay list is now well-considered, whereas the client
3957 list has been chosen mainly for anti-fingerprinting purposes.)
3958 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
3959 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
3960 AES128. Resolves ticket 11528.
3961 - Clients now try to advertise the same list of ciphersuites as
3962 Firefox 28. This change enables selection of (fast) GCM
3963 ciphersuites, disables some strange old ciphers, and stops
3964 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
3965 Resolves ticket 11438.
3967 o Minor bugfixes (configuration, security):
3968 - When running a hidden service, do not allow TunneledDirConns 0:
3969 trying to set that option together with a hidden service would
3970 otherwise prevent the hidden service from running, and also make
3971 it publish its descriptors directly over HTTP. Fixes bug 10849;
3972 bugfix on 0.2.1.1-alpha.
3974 o Minor bugfixes (controller, backport from 0.2.5.4-alpha):
3975 - Avoid sending a garbage value to the controller when a circuit is
3976 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
3978 o Minor bugfixes (exit relay, backport from 0.2.5.4-alpha):
3979 - Stop leaking memory when we successfully resolve a PTR record.
3980 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
3982 o Minor bugfixes (bridge client, backport from 0.2.5.4-alpha):
3983 - Avoid 60-second delays in the bootstrapping process when Tor is
3984 launching for a second time while using bridges. Fixes bug 9229;
3985 bugfix on 0.2.0.3-alpha.
3987 o Minor bugfixes (relays and bridges, backport from 0.2.5.4-alpha):
3988 - Give the correct URL in the warning message when trying to run a
3989 relay on an ancient version of Windows. Fixes bug 9393.
3991 o Minor bugfixes (compilation):
3992 - Fix a compilation error when compiling with --disable-curve25519.
3993 Fixes bug 9700; bugfix on 0.2.4.17-rc.
3996 - Downgrade the warning severity for the the "md was still
3997 referenced 1 node(s)" warning. Tor 0.2.5.4-alpha has better code
3998 for trying to diagnose this bug, and the current warning in
3999 earlier versions of tor achieves nothing useful. Addresses warning
4002 o Minor features (log verbosity, backport from 0.2.5.4-alpha):
4003 - When we run out of usable circuit IDs on a channel, log only one
4004 warning for the whole channel, and describe how many circuits
4005 there were on the channel. Fixes part of ticket 11553.
4007 o Minor features (security, backport from 0.2.5.4-alpha):
4008 - Decrease the lower limit of MaxMemInCellQueues to 256 MBytes (but
4009 leave the default at 8GBytes), to better support Raspberry Pi
4010 users. Fixes bug 9686; bugfix on 0.2.4.14-alpha.
4012 o Documentation (backport from 0.2.5.4-alpha):
4013 - Correctly document that we search for a system torrc file before
4014 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4018 Changes in version 0.2.5.4-alpha - 2014-04-25
4019 Tor 0.2.5.4-alpha includes several security and performance
4020 improvements for clients and relays, including blacklisting authority
4021 signing keys that were used while susceptible to the OpenSSL
4022 "heartbleed" bug, fixing two expensive functions on busy relays,
4023 improved TLS ciphersuite preference lists, support for run-time
4024 hardening on compilers that support AddressSanitizer, and more work on
4025 the Linux sandbox code.
4027 There are also several usability fixes for clients (especially clients
4028 that use bridges), two new TransPort protocols supported (one on
4029 OpenBSD, one on FreeBSD), and various other bugfixes.
4031 This release marks end-of-life for Tor 0.2.2.x; those Tor versions
4032 have accumulated many known flaws; everyone should upgrade.
4034 o Major features (security):
4035 - If you don't specify MaxMemInQueues yourself, Tor now tries to
4036 pick a good value based on your total system memory. Previously,
4037 the default was always 8 GB. You can still override the default by
4038 setting MaxMemInQueues yourself. Resolves ticket 11396.
4039 - Block authority signing keys that were used on authorities
4040 vulnerable to the "heartbleed" bug in OpenSSL (CVE-2014-0160). (We
4041 don't have any evidence that these keys _were_ compromised; we're
4042 doing this to be prudent.) Resolves ticket 11464.
4044 o Major features (relay performance):
4045 - Speed up server-side lookups of rendezvous and introduction point
4046 circuits by using hashtables instead of linear searches. These
4047 functions previously accounted between 3 and 7% of CPU usage on
4048 some busy relays. Resolves ticket 9841.
4049 - Avoid wasting CPU when extending a circuit over a channel that is
4050 nearly out of circuit IDs. Previously, we would do a linear scan
4051 over possible circuit IDs before finding one or deciding that we
4052 had exhausted our possibilities. Now, we try at most 64 random
4053 circuit IDs before deciding that we probably won't succeed. Fixes
4054 a possible root cause of ticket 11553.
4056 o Major features (seccomp2 sandbox, Linux only):
4057 - The seccomp2 sandbox can now run a test network for multiple hours
4058 without crashing. The sandbox is still experimental, and more bugs
4059 will probably turn up. To try it, enable "Sandbox 1" on a Linux
4060 host. Resolves ticket 11351.
4061 - Strengthen sandbox code: the sandbox can now test the arguments
4062 for rename(), and blocks _sysctl() entirely. Resolves another part
4064 - When the sandbox blocks a system call, it now tries to log a stack
4065 trace before exiting. Resolves ticket 11465.
4067 o Major bugfixes (TLS cipher selection):
4068 - The relay ciphersuite list is now generated automatically based on
4069 uniform criteria, and includes all OpenSSL ciphersuites with
4070 acceptable strength and forward secrecy. Previously, we had left
4071 some perfectly fine ciphersuites unsupported due to omission or
4072 typo. Resolves bugs 11513, 11492, 11498, 11499. Bugs reported by
4073 'cypherpunks'. Bugfix on 0.2.4.8-alpha.
4074 - Relays now trust themselves to have a better view than clients of
4075 which TLS ciphersuites are better than others. (Thanks to bug
4076 11513, the relay list is now well-considered, whereas the client
4077 list has been chosen mainly for anti-fingerprinting purposes.)
4078 Relays prefer: AES over 3DES; then ECDHE over DHE; then GCM over
4079 CBC; then SHA384 over SHA256 over SHA1; and last, AES256 over
4080 AES128. Resolves ticket 11528.
4081 - Clients now try to advertise the same list of ciphersuites as
4082 Firefox 28. This change enables selection of (fast) GCM
4083 ciphersuites, disables some strange old ciphers, and stops
4084 advertising the ECDH (not to be confused with ECDHE) ciphersuites.
4085 Resolves ticket 11438.
4087 o Major bugfixes (bridge client):
4088 - Avoid 60-second delays in the bootstrapping process when Tor is
4089 launching for a second time while using bridges. Fixes bug 9229;
4090 bugfix on 0.2.0.3-alpha.
4092 o Minor features (transparent proxy, *BSD):
4093 - Support FreeBSD's ipfw firewall interface for TransPort ports on
4094 FreeBSD. To enable it, set "TransProxyType ipfw". Resolves ticket
4095 10267; patch from "yurivict".
4096 - Support OpenBSD's divert-to rules with the pf firewall for
4097 transparent proxy ports. To enable it, set "TransProxyType
4098 pf-divert". This allows Tor to run a TransPort transparent proxy
4099 port on OpenBSD 4.4 or later without root privileges. See the
4100 pf.conf(5) manual page for information on configuring pf to use
4101 divert-to rules. Closes ticket 10896; patch from Dana Koch.
4103 o Minor features (security):
4104 - New --enable-expensive-hardening option to enable security
4105 hardening options that consume nontrivial amounts of CPU and
4106 memory. Right now, this includes AddressSanitizer and UbSan, which
4107 are supported in newer versions of GCC and Clang. Closes ticket
4110 o Minor features (log verbosity):
4111 - Demote the message that we give when a flushing connection times
4112 out for too long from NOTICE to INFO. It was usually meaningless.
4113 Resolves ticket 5286.
4114 - Don't log so many notice-level bootstrapping messages at startup
4115 about downloading descriptors. Previously, we'd log a notice
4116 whenever we learned about more routers. Now, we only log a notice
4117 at every 5% of progress. Fixes bug 9963.
4118 - Warn less verbosely when receiving a malformed
4119 ESTABLISH_RENDEZVOUS cell. Fixes ticket 11279.
4120 - When we run out of usable circuit IDs on a channel, log only one
4121 warning for the whole channel, and describe how many circuits
4122 there were on the channel. Fixes part of ticket 11553.
4124 o Minor features (relay):
4125 - If a circuit timed out for at least 3 minutes, check if we have a
4126 new external IP address, and publish a new descriptor with the new
4127 IP address if it changed. Resolves ticket 2454.
4129 o Minor features (controller):
4130 - Make the entire exit policy available from the control port via
4131 GETINFO exit-policy/*. Implements enhancement 7952. Patch from
4133 - Because of the fix for ticket 11396, the real limit for memory
4134 usage may no longer match the configured MaxMemInQueues value. The
4135 real limit is now exposed via GETINFO limits/max-mem-in-queues.
4137 o Minor features (bridge client):
4138 - Report a more useful failure message when we can't connect to a
4139 bridge because we don't have the right pluggable transport
4140 configured. Resolves ticket 9665. Patch from Fábio J. Bertinatto.
4142 o Minor features (diagnostic):
4143 - Add more log messages to diagnose bug 7164, which causes
4144 intermittent "microdesc_free() called but md was still referenced"
4145 warnings. We now include more information, to figure out why we
4146 might be cleaning a microdescriptor for being too old if it's
4147 still referenced by a live node_t object.
4149 o Minor bugfixes (client, DNSPort):
4150 - When using DNSPort, try to respond to AAAA requests with AAAA
4151 answers. Previously, we hadn't looked at the request type when
4152 deciding which answer type to prefer. Fixes bug 10468; bugfix on
4154 - When receiving a DNS query for an unsupported record type, reply
4155 with no answer rather than with a NOTIMPL error. This behavior
4156 isn't correct either, but it will break fewer client programs, we
4157 hope. Fixes bug 10268; bugfix on 0.2.0.1-alpha. Original patch
4160 o Minor bugfixes (exit relay):
4161 - Stop leaking memory when we successfully resolve a PTR record.
4162 Fixes bug 11437; bugfix on 0.2.4.7-alpha.
4164 o Minor bugfixes (bridge client):
4165 - Stop accepting bridge lines containing hostnames. Doing so would
4166 cause clients to perform DNS requests on the hostnames, which was
4167 not sensible behavior. Fixes bug 10801; bugfix on 0.2.0.1-alpha.
4168 - Avoid a 60-second delay in the bootstrapping process when a Tor
4169 client with pluggable transports re-reads its configuration at
4170 just the wrong time. Re-fixes bug 11156; bugfix on 0.2.5.3-alpha.
4172 o Minor bugfixes (client, logging during bootstrap):
4173 - Warn only once if we start logging in an unsafe way. Previously,
4174 we complain as many times as we had problems. Fixes bug 9870;
4175 bugfix on 0.2.5.1-alpha.
4176 - Only report the first fatal bootstrap error on a given OR
4177 connection. This stops us from telling the controller bogus error
4178 messages like "DONE". Fixes bug 10431; bugfix on 0.2.1.1-alpha.
4179 - Be more helpful when trying to run sandboxed on Linux without
4180 libseccomp. Instead of saying "Sandbox is not implemented on this
4181 platform", we now explain that we need to be built with
4182 libseccomp. Fixes bug 11543; bugfix on 0.2.5.1-alpha.
4183 - Avoid generating spurious warnings when starting with
4184 DisableNetwork enabled. Fixes bug 11200 and bug 10405; bugfix on
4187 o Minor bugfixes (closing OR connections):
4188 - If write_to_buf() in connection_write_to_buf_impl_() ever fails,
4189 check if it's an or_connection_t and correctly call
4190 connection_or_close_for_error() rather than
4191 connection_mark_for_close() directly. Fixes bug 11304; bugfix on
4193 - When closing all connections on setting DisableNetwork to 1, use
4194 connection_or_close_normally() rather than closing OR connections
4195 out from under the channel layer. Fixes bug 11306; bugfix on
4198 o Minor bugfixes (controller):
4199 - Avoid sending a garbage value to the controller when a circuit is
4200 cannibalized. Fixes bug 11519; bugfix on 0.2.3.11-alpha.
4202 o Minor bugfixes (tor-fw-helper):
4203 - Allow tor-fw-helper to build again by adding src/ext to its
4204 CPPFLAGS. Fixes bug 11296; bugfix on 0.2.5.3-alpha.
4206 o Minor bugfixes (bridges):
4207 - Avoid potential crashes or bad behavior when launching a
4208 server-side managed proxy with ORPort or ExtORPort temporarily
4209 disabled. Fixes bug 9650; bugfix on 0.2.3.16-alpha.
4211 o Minor bugfixes (platform-specific):
4212 - Fix compilation on Solaris, which does not have <endian.h>. Fixes
4213 bug 11426; bugfix on 0.2.5.3-alpha.
4214 - When dumping a malformed directory object to disk, save it in
4215 binary mode on Windows, not text mode. Fixes bug 11342; bugfix on
4217 - Don't report failures from make_socket_reuseable() on incoming
4218 sockets on OSX: this can happen when incoming connections close
4219 early. Fixes bug 10081.
4221 o Minor bugfixes (trivial memory leaks):
4222 - Fix a small memory leak when signing a directory object. Fixes bug
4223 11275; bugfix on 0.2.4.13-alpha.
4224 - Free placeholder entries in our circuit table at exit; fixes a
4225 harmless memory leak. Fixes bug 11278; bugfix on 0.2.5.1-alpha.
4226 - Don't re-initialize a second set of OpenSSL mutexes when starting
4227 up. Previously, we'd make one set of mutexes, and then immediately
4228 replace them with another. Fixes bug 11726; bugfix on
4230 - Resolve some memory leaks found by coverity in the unit tests, on
4231 exit in tor-gencert, and on a failure to compute digests for our
4232 own keys when generating a v3 networkstatus vote. These leaks
4233 should never have affected anyone in practice.
4235 o Minor bugfixes (hidden service):
4236 - Only retry attempts to connect to a chosen rendezvous point 8
4237 times, not 30. Fixes bug 4241; bugfix on 0.1.0.1-rc.
4239 o Minor bugfixes (misc code correctness):
4240 - Fix various instances of undefined behavior in channeltls.c,
4241 tor_memmem(), and eventdns.c that would cause us to construct
4242 pointers to memory outside an allocated object. (These invalid
4243 pointers were not accessed, but C does not even allow them to
4244 exist.) Fixes bug 10363; bugfixes on 0.1.1.1-alpha, 0.1.2.1-alpha,
4245 0.2.0.10-alpha, and 0.2.3.6-alpha. Reported by "bobnomnom".
4246 - Use the AddressSanitizer and Ubsan sanitizers (in clang-3.4) to
4247 fix some miscellaneous errors in our tests and codebase. Fixes bug
4248 11232. Bugfixes on versions back as far as 0.2.1.11-alpha.
4249 - Always check return values for unlink, munmap, UnmapViewOfFile;
4250 check strftime return values more often. In some cases all we can
4251 do is report a warning, but this may help prevent deeper bugs from
4252 going unnoticed. Closes ticket 8787; bugfixes on many, many tor
4254 - Fix numerous warnings from the clang "scan-build" static analyzer.
4255 Some of these are programming style issues; some of them are false
4256 positives that indicated awkward code; some are undefined behavior
4257 cases related to constructing (but not using) invalid pointers;
4258 some are assumptions about API behavior; some are (harmlessly)
4259 logging sizeof(ptr) bytes from a token when sizeof(*ptr) would be
4260 correct; and one or two are genuine bugs that weren't reachable
4261 from the rest of the program. Fixes bug 8793; bugfixes on many,
4265 - Build the torify.1 manpage again. Previously, we were only trying
4266 to build it when also building tor-fw-helper. That's why we didn't
4267 notice that we'd broken the ability to build it. Fixes bug 11321;
4268 bugfix on 0.2.5.1-alpha.
4269 - Fix the layout of the SOCKSPort flags in the manpage. Fixes bug
4270 11061; bugfix on 0.2.4.7-alpha.
4271 - Correctly document that we search for a system torrc file before
4272 looking in ~/.torrc. Fixes documentation side of 9213; bugfix on
4274 - Resolve warnings from Doxygen.
4276 o Code simplifications and refactoring:
4277 - Remove is_internal_IP() function. Resolves ticket 4645.
4278 - Remove unused function circuit_dump_by_chan from circuitlist.c.
4279 Closes issue 9107; patch from "marek".
4280 - Change our use of the ENUM_BF macro to avoid declarations that
4283 o Deprecated versions:
4284 - Tor 0.2.2.x has reached end-of-life; it has received no patches or
4285 attention for some while. Directory authorities no longer accept
4286 descriptors from relays running any version of Tor prior to Tor
4287 0.2.3.16-alpha. Resolves ticket 11149.
4290 - New macros in test.h to simplify writing mock-functions for unit
4291 tests. Part of ticket 11507. Patch from Dana Koch.
4292 - Complete tests for the status.c module. Resolves ticket 11507.
4293 Patch from Dana Koch.
4296 - Remove all code for the long unused v1 directory protocol.
4297 Resolves ticket 11070.
4300 Changes in version 0.2.5.3-alpha - 2014-03-22
4301 Tor 0.2.5.3-alpha includes all the fixes from 0.2.4.21. It contains
4302 two new anti-DoS features for Tor relays, resolves a bug that kept
4303 SOCKS5 support for IPv6 from working, fixes several annoying usability
4304 issues for bridge users, and removes more old code for unused
4307 The Tor 0.2.5.x release series is now in patch-freeze: no feature
4308 patches not already written will be considered for inclusion in 0.2.5.x.
4310 o Major features (relay security, DoS-resistance):
4311 - When deciding whether we have run out of memory and we need to
4312 close circuits, also consider memory allocated in buffers for
4313 streams attached to each circuit.
4315 This change, which extends an anti-DoS feature introduced in
4316 0.2.4.13-alpha and improved in 0.2.4.14-alpha, lets Tor exit relays
4317 better resist more memory-based DoS attacks than before. Since the
4318 MaxMemInCellQueues option now applies to all queues, it is renamed
4319 to MaxMemInQueues. This feature fixes bug 10169.
4320 - Avoid hash-flooding denial-of-service attacks by using the secure
4321 SipHash-2-4 hash function for our hashtables. Without this
4322 feature, an attacker could degrade performance of a targeted
4323 client or server by flooding their data structures with a large
4324 number of entries to be stored at the same hash table position,
4325 thereby slowing down the Tor instance. With this feature, hash
4326 table positions are derived from a randomized cryptographic key,
4327 and an attacker cannot predict which entries will collide. Closes
4329 - Decrease the lower limit of MaxMemInQueues to 256 MBytes (but leave
4330 the default at 8GBytes), to better support Raspberry Pi users. Fixes
4331 bug 9686; bugfix on 0.2.4.14-alpha.
4333 o Minor features (bridges, pluggable transports):
4334 - Bridges now write the SHA1 digest of their identity key
4335 fingerprint (that is, a hash of a hash of their public key) to
4336 notice-level logs, and to a new hashed-fingerprint file. This
4337 information will help bridge operators look up their bridge in
4338 Globe and similar tools. Resolves ticket 10884.
4339 - Improve the message that Tor displays when running as a bridge
4340 using pluggable transports without an Extended ORPort listener.
4341 Also, log the message in the log file too. Resolves ticket 11043.
4343 o Minor features (other):
4344 - Add a new option, PredictedPortsRelevanceTime, to control how long
4345 after having received a request to connect to a given port Tor
4346 will try to keep circuits ready in anticipation of future requests
4347 for that port. Patch from "unixninja92"; implements ticket 9176.
4348 - Generate a warning if any ports are listed in the SocksPolicy,
4349 DirPolicy, AuthDirReject, AuthDirInvalid, AuthDirBadDir, or
4350 AuthDirBadExit options. (These options only support address
4351 ranges.) Fixes part of ticket 11108.
4352 - Update geoip and geoip6 to the February 7 2014 Maxmind GeoLite2
4355 o Minor bugfixes (new since 0.2.5.2-alpha, also in 0.2.4.21):
4356 - Build without warnings under clang 3.4. (We have some macros that
4357 define static functions only some of which will get used later in
4358 the module. Starting with clang 3.4, these give a warning unless the
4359 unused attribute is set on them.) Resolves ticket 10904.
4360 - Fix build warnings about missing "a2x" comment when building the
4361 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4362 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4364 o Minor bugfixes (client):
4365 - Improve the log message when we can't connect to a hidden service
4366 because all of the hidden service directory nodes hosting its
4367 descriptor are excluded. Improves on our fix for bug 10722, which
4368 was a bugfix on 0.2.0.10-alpha.
4369 - Raise a control port warning when we fail to connect to all of
4370 our bridges. Previously, we didn't inform the controller, and
4371 the bootstrap process would stall. Fixes bug 11069; bugfix on
4373 - Exit immediately when a process-owning controller exits.
4374 Previously, tor relays would wait for a little while after their
4375 controller exited, as if they had gotten an INT signal -- but this
4376 was problematic, since there was no feedback for the user. To do a
4377 clean shutdown, controllers should send an INT signal and give Tor
4378 a chance to clean up. Fixes bug 10449; bugfix on 0.2.2.28-beta.
4379 - Stop attempting to connect to bridges before our pluggable
4380 transports are configured (harmless but resulted in some erroneous
4381 log messages). Fixes bug 11156; bugfix on 0.2.3.2-alpha.
4382 - Fix connections to IPv6 addresses over SOCKS5. Previously, we were
4383 generating incorrect SOCKS5 responses, and confusing client
4384 applications. Fixes bug 10987; bugfix on 0.2.4.7-alpha.
4386 o Minor bugfixes (relays and bridges):
4387 - Avoid crashing on a malformed resolv.conf file when running a
4388 relay using Libevent 1. Fixes bug 8788; bugfix on 0.1.1.23.
4389 - Non-exit relays no longer launch mock DNS requests to check for
4390 DNS hijacking. This has been unnecessary since 0.2.1.7-alpha, when
4391 non-exit relays stopped servicing DNS requests. Fixes bug 965;
4392 bugfix on 0.2.1.7-alpha. Patch from Matt Pagan.
4393 - Bridges now report complete directory request statistics. Related
4394 to bug 5824; bugfix on 0.2.2.1-alpha.
4395 - Bridges now never collect statistics that were designed for
4396 relays. Fixes bug 5824; bugfix on 0.2.3.8-alpha.
4397 - Stop giving annoying warning messages when we decide not to launch
4398 a pluggable transport proxy that we don't need (because there are
4399 no bridges configured to use it). Resolves ticket 5018; bugfix
4401 - Give the correct URL in the warning message when trying to run a
4402 relay on an ancient version of Windows. Fixes bug 9393.
4404 o Minor bugfixes (backtrace support):
4405 - Support automatic backtraces on more platforms by using the
4406 "-fasynchronous-unwind-tables" compiler option. This option is
4407 needed for platforms like 32-bit Intel where "-fomit-frame-pointer"
4408 is on by default and table generation is not. This doesn't yet
4409 add Windows support; only Linux, OSX, and some BSDs are affected.
4410 Reported by 'cypherpunks'; fixes bug 11047; bugfix on 0.2.5.2-alpha.
4411 - Avoid strange behavior if two threads hit failed assertions at the
4412 same time and both try to log backtraces at once. (Previously, if
4413 this had happened, both threads would have stored their intermediate
4414 results in the same buffer, and generated junk outputs.) Reported by
4415 "cypherpunks". Fixes bug 11048; bugfix on 0.2.5.2-alpha.
4416 - Fix a compiler warning in format_number_sigsafe(). Bugfix on
4417 0.2.5.2-alpha; patch from Nick Hopper.
4419 o Minor bugfixes (unit tests):
4420 - Fix a small bug in the unit tests that might have made the tests
4421 call 'chmod' with an uninitialized bitmask. Fixes bug 10928;
4422 bugfix on 0.2.5.1-alpha. Patch from Dana Koch.
4425 - Remove all remaining code related to version-0 hidden service
4426 descriptors: they have not been in use since 0.2.2.1-alpha. Fixes
4427 the rest of bug 10841.
4430 - Document in the manpage that "KBytes" may also be written as
4431 "kilobytes" or "KB", that "Kbits" may also be written as
4432 "kilobits", and so forth. Closes ticket 9222.
4433 - Document that the ClientOnly config option overrides ORPort.
4434 Our old explanation made ClientOnly sound as though it did
4435 nothing at all. Resolves bug 9059.
4436 - Explain that SocksPolicy, DirPolicy, and similar options don't
4437 take port arguments. Fixes the other part of ticket 11108.
4438 - Fix a comment about the rend_server_descriptor_t.protocols field
4439 to more accurately describe its range. Also, make that field
4440 unsigned, to more accurately reflect its usage. Fixes bug 9099;
4441 bugfix on 0.2.1.5-alpha.
4442 - Fix the manpage's description of HiddenServiceAuthorizeClient:
4443 the maximum client name length is 16, not 19. Fixes bug 11118;
4444 bugfix on 0.2.1.6-alpha.
4446 o Code simplifications and refactoring:
4447 - Get rid of router->address, since in all cases it was just the
4448 string representation of router->addr. Resolves ticket 5528.
4450 o Test infrastructure:
4451 - Update to the latest version of tinytest.
4452 - Improve the tinytest implementation of string operation tests so
4453 that comparisons with NULL strings no longer crash the tests; they
4454 now just fail, normally. Fixes bug 9004; bugfix on 0.2.2.4-alpha.
4457 Changes in version 0.2.4.21 - 2014-02-28
4458 Tor 0.2.4.21 further improves security against potential adversaries who
4459 find breaking 1024-bit crypto doable, and backports several stability
4460 and robustness patches from the 0.2.5 branch.
4462 o Major features (client security):
4463 - When we choose a path for a 3-hop circuit, make sure it contains
4464 at least one relay that supports the NTor circuit extension
4465 handshake. Otherwise, there is a chance that we're building
4466 a circuit that's worth attacking by an adversary who finds
4467 breaking 1024-bit crypto doable, and that chance changes the game
4468 theory. Implements ticket 9777.
4471 - Do not treat streams that fail with reason
4472 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4473 since it could also indicate an ENETUNREACH connection error. Fixes
4474 part of bug 10777; bugfix on 0.2.4.8-alpha.
4476 o Code simplification and refactoring:
4477 - Remove data structures which were introduced to implement the
4478 CellStatistics option: they are now redundant with the new timestamp
4479 field in the regular packed_cell_t data structure, which we did
4480 in 0.2.4.18-rc in order to resolve bug 9093. Resolves ticket 10870.
4483 - Always clear OpenSSL bignums before freeing them -- even bignums
4484 that don't contain secrets. Resolves ticket 10793. Patch by
4486 - Build without warnings under clang 3.4. (We have some macros that
4487 define static functions only some of which will get used later in
4488 the module. Starting with clang 3.4, these give a warning unless the
4489 unused attribute is set on them.) Resolves ticket 10904.
4490 - Update geoip and geoip6 files to the February 7 2014 Maxmind
4491 GeoLite2 Country database.
4494 - Set the listen() backlog limit to the largest actually supported
4495 on the system, not to the value in a header file. Fixes bug 9716;
4496 bugfix on every released Tor.
4497 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4498 exit node as a NOROUTE error, not an INTERNAL error, since they
4499 can apparently happen when trying to connect to the wrong sort
4500 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4501 - Fix build warnings about missing "a2x" comment when building the
4502 manpages from scratch on OpenBSD; OpenBSD calls it "a2x.py".
4503 Fixes bug 10929; bugfix on 0.2.2.9-alpha. Patch from Dana Koch.
4504 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4505 not entirely remove it from the connection lists. Fixes bug 9602;
4506 bugfix on 0.2.4.4-alpha.
4507 - Fix a segmentation fault in our benchmark code when running with
4508 Fedora's OpenSSL package, or any other OpenSSL that provides
4509 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4510 - Turn "circuit handshake stats since last time" log messages into a
4511 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4513 o Documentation fixes:
4514 - Document that all but one DirPort entry must have the NoAdvertise
4515 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4518 Changes in version 0.2.5.2-alpha - 2014-02-13
4519 Tor 0.2.5.2-alpha includes all the fixes from 0.2.4.18-rc and 0.2.4.20,
4520 like the "poor random number generation" fix and the "building too many
4521 circuits" fix. It also further improves security against potential
4522 adversaries who find breaking 1024-bit crypto doable, and launches
4523 pluggable transports on demand (which gets us closer to integrating
4524 pluggable transport support by default -- not to be confused with Tor
4525 bundles enabling pluggable transports and bridges by default).
4527 o Major features (client security):
4528 - When we choose a path for a 3-hop circuit, make sure it contains
4529 at least one relay that supports the NTor circuit extension
4530 handshake. Otherwise, there is a chance that we're building
4531 a circuit that's worth attacking by an adversary who finds
4532 breaking 1024-bit crypto doable, and that chance changes the game
4533 theory. Implements ticket 9777.
4534 - Clients now look at the "usecreatefast" consensus parameter to
4535 decide whether to use CREATE_FAST or CREATE cells for the first hop
4536 of their circuit. This approach can improve security on connections
4537 where Tor's circuit handshake is stronger than the available TLS
4538 connection security levels, but the tradeoff is more computational
4539 load on guard relays. Implements proposal 221. Resolves ticket 9386.
4541 o Major features (bridges):
4542 - Don't launch pluggable transport proxies if we don't have any
4543 bridges configured that would use them. Now we can list many
4544 pluggable transports, and Tor will dynamically start one when it
4545 hears a bridge address that needs it. Resolves ticket 5018.
4546 - The bridge directory authority now assigns status flags (Stable,
4547 Guard, etc) to bridges based on thresholds calculated over all
4548 Running bridges. Now bridgedb can finally make use of its features
4549 to e.g. include at least one Stable bridge in its answers. Fixes
4552 o Major features (other):
4553 - Extend ORCONN controller event to include an "ID" parameter,
4554 and add four new controller event types CONN_BW, CIRC_BW,
4555 CELL_STATS, and TB_EMPTY that show connection and circuit usage.
4556 The new events are emitted in private Tor networks only, with the
4557 goal of being able to better track performance and load during
4558 full-network simulations. Implements proposal 218 and ticket 7359.
4559 - On some platforms (currently: recent OSX versions, glibc-based
4560 platforms that support the ELF format, and a few other
4561 Unix-like operating systems), Tor can now dump stack traces
4562 when a crash occurs or an assertion fails. By default, traces
4563 are dumped to stderr (if possible) and to any logs that are
4564 reporting errors. Implements ticket 9299.
4567 - Avoid a segfault on SIGUSR1, where we had freed a connection but did
4568 not entirely remove it from the connection lists. Fixes bug 9602;
4569 bugfix on 0.2.4.4-alpha.
4570 - Do not treat streams that fail with reason
4571 END_STREAM_REASON_INTERNAL as indicating a definite circuit failure,
4572 since it could also indicate an ENETUNREACH connection error. Fixes
4573 part of bug 10777; bugfix on 0.2.4.8-alpha.
4575 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4576 - Do not allow OpenSSL engines to replace the PRNG, even when
4577 HardwareAccel is set. The only default builtin PRNG engine uses
4578 the Intel RDRAND instruction to replace the entire PRNG, and
4579 ignores all attempts to seed it with more entropy. That's
4580 cryptographically stupid: the right response to a new alleged
4581 entropy source is never to discard all previously used entropy
4582 sources. Fixes bug 10402; works around behavior introduced in
4583 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4585 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4586 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4587 - Avoid launching spurious extra circuits when a stream is pending.
4588 This fixes a bug where any circuit that _wasn't_ unusable for new
4589 streams would be treated as if it were, causing extra circuits to
4590 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4592 o Major bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4593 - No longer stop reading or writing on cpuworker connections when
4594 our rate limiting buckets go empty. Now we should handle circuit
4595 handshake requests more promptly. Resolves bug 9731.
4596 - Stop trying to bootstrap all our directory information from
4597 only our first guard. Discovered while fixing bug 9946; bugfix
4600 o Minor features (bridges, pluggable transports):
4601 - Add threshold cutoffs to the networkstatus document created by
4602 the Bridge Authority. Fixes bug 1117.
4603 - On Windows, spawn background processes using the CREATE_NO_WINDOW
4604 flag. Now Tor Browser Bundle 3.5 with pluggable transports enabled
4605 doesn't pop up a blank console window. (In Tor Browser Bundle 2.x,
4606 Vidalia set this option for us.) Implements ticket 10297.
4608 o Minor features (security):
4609 - Always clear OpenSSL bignums before freeing them -- even bignums
4610 that don't contain secrets. Resolves ticket 10793. Patch by
4613 o Minor features (config options and command line):
4614 - Add an --allow-missing-torrc commandline option that tells Tor to
4615 run even if the configuration file specified by -f is not available.
4616 Implements ticket 10060.
4617 - Add support for the TPROXY transparent proxying facility on Linux.
4618 See documentation for the new TransProxyType option for more
4619 details. Implementation by "thomo". Closes ticket 10582.
4621 o Minor features (controller):
4622 - Add a new "HS_DESC" controller event that reports activities
4623 related to hidden service descriptors. Resolves ticket 8510.
4624 - New "DROPGUARDS" controller command to forget all current entry
4625 guards. Not recommended for ordinary use, since replacing guards
4626 too frequently makes several attacks easier. Resolves ticket 9934;
4629 o Minor features (build):
4630 - Assume that a user using ./configure --host wants to cross-compile,
4631 and give an error if we cannot find a properly named
4632 tool-chain. Add a --disable-tool-name-check option to proceed
4633 nevertheless. Addresses ticket 9869. Patch by Benedikt Gollatz.
4634 - If we run ./configure and the compiler recognizes -fstack-protector
4635 but the linker rejects it, warn the user about a potentially missing
4636 libssp package. Addresses ticket 9948. Patch from Benedikt Gollatz.
4638 o Minor features (testing):
4639 - If Python is installed, "make check" now runs extra tests beyond
4640 the unit test scripts.
4641 - When bootstrapping a test network, sometimes very few relays get
4642 the Guard flag. Now a new option "TestingDirAuthVoteGuard" can
4643 specify a set of relays which should be voted Guard regardless of
4644 their uptime or bandwidth. Addresses ticket 9206.
4646 o Minor features (log messages):
4647 - When ServerTransportPlugin is set on a bridge, Tor can write more
4648 useful statistics about bridge use in its extrainfo descriptors,
4649 but only if the Extended ORPort ("ExtORPort") is set too. Add a
4650 log message to inform the user in this case. Resolves ticket 9651.
4651 - When receiving a new controller connection, log the origin address.
4652 Resolves ticket 9698; patch from "sigpipe".
4653 - When logging OpenSSL engine status at startup, log the status of
4654 more engines. Fixes ticket 10043; patch from Joshua Datko.
4655 - Turn "circuit handshake stats since last time" log messages into a
4656 heartbeat message. Fixes bug 10485; bugfix on 0.2.4.17-rc.
4658 o Minor features (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4659 - Improve the circuit queue out-of-memory handler. Previously, when
4660 we ran low on memory, we'd close whichever circuits had the most
4661 queued cells. Now, we close those that have the *oldest* queued
4662 cells, on the theory that those are most responsible for us
4663 running low on memory. Based on analysis from a forthcoming paper
4664 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4665 - Generate bootstrapping status update events correctly when fetching
4666 microdescriptors. Fixes bug 9927.
4667 - Update to the October 2 2013 Maxmind GeoLite Country database.
4669 o Minor bugfixes (clients):
4670 - When closing a channel that has already been open, do not close
4671 pending circuits that were waiting to connect to the same relay.
4672 Fixes bug 9880; bugfix on 0.2.5.1-alpha. Thanks to skruffy for
4675 o Minor bugfixes (relays):
4676 - Treat ENETUNREACH, EACCES, and EPERM connection failures at an
4677 exit node as a NOROUTE error, not an INTERNAL error, since they
4678 can apparently happen when trying to connect to the wrong sort
4679 of netblocks. Fixes part of bug 10777; bugfix on 0.1.0.1-rc.
4681 o Minor bugfixes (bridges):
4682 - Fix a bug where the first connection works to a bridge that uses a
4683 pluggable transport with client-side parameters, but we don't send
4684 the client-side parameters on subsequent connections. (We don't
4685 use any pluggable transports with client-side parameters yet,
4686 but ScrambleSuit will soon become the first one.) Fixes bug 9162;
4687 bugfix on 0.2.0.3-alpha. Based on a patch from "rl1987".
4689 o Minor bugfixes (node selection):
4690 - If ExcludeNodes is set, consider non-excluded hidden service
4691 directory servers before excluded ones. Do not consider excluded
4692 hidden service directory servers at all if StrictNodes is
4693 set. (Previously, we would sometimes decide to connect to those
4694 servers, and then realize before we initiated a connection that
4695 we had excluded them.) Fixes bug 10722; bugfix on 0.2.0.10-alpha.
4697 - If we set the ExitNodes option but it doesn't include any nodes
4698 that have the Exit flag, we would choose not to bootstrap. Now we
4699 bootstrap so long as ExitNodes includes nodes which can exit to
4700 some port. Fixes bug 10543; bugfix on 0.2.4.10-alpha.
4702 o Minor bugfixes (controller and command-line):
4703 - If changing a config option via "setconf" fails in a recoverable
4704 way, we used to nonetheless write our new control ports to the
4705 file described by the "ControlPortWriteToFile" option. Now we only
4706 write out that file if we successfully switch to the new config
4707 option. Fixes bug 5605; bugfix on 0.2.2.26-beta. Patch from "Ryman".
4708 - When a command-line option such as --version or --help that
4709 ordinarily implies --hush appears on the command line along with
4710 --quiet, then actually obey --quiet. Previously, we obeyed --quiet
4711 only if it appeared later on the command line. Fixes bug 9578;
4712 bugfix on 0.2.5.1-alpha.
4714 o Minor bugfixes (code correctness):
4715 - Previously we used two temporary files when writing descriptors to
4716 disk; now we only use one. Fixes bug 1376.
4717 - Remove an erroneous (but impossible and thus harmless) pointer
4718 comparison that would have allowed compilers to skip a bounds
4719 check in channeltls.c. Fixes bugs 10313 and 9980; bugfix on
4720 0.2.0.10-alpha. Noticed by Jared L Wong and David Fifield.
4721 - Fix an always-true assertion in pluggable transports code so it
4722 actually checks what it was trying to check. Fixes bug 10046;
4723 bugfix on 0.2.3.9-alpha. Found by "dcb".
4725 o Minor bugfixes (protocol correctness):
4726 - When receiving a VERSIONS cell with an odd number of bytes, close
4727 the connection immediately since the cell is malformed. Fixes bug
4728 10365; bugfix on 0.2.0.10-alpha. Spotted by "bobnomnom"; fix by
4731 o Minor bugfixes (build):
4732 - Restore the ability to compile Tor with V2_HANDSHAKE_SERVER
4733 turned off (that is, without support for v2 link handshakes). Fixes
4734 bug 4677; bugfix on 0.2.3.2-alpha. Patch from "piet".
4735 - Fix compilation warnings and startup issues when running with
4736 "Sandbox 1" and libseccomp-2.1.0. Fixes bug 10563; bugfix on
4738 - Fix compilation on Solaris 9, which didn't like us having an
4739 identifier named "sun". Fixes bug 10565; bugfix in 0.2.5.1-alpha.
4741 o Minor bugfixes (testing):
4742 - Fix a segmentation fault in our benchmark code when running with
4743 Fedora's OpenSSL package, or any other OpenSSL that provides
4744 ECDH but not P224. Fixes bug 10835; bugfix on 0.2.4.8-alpha.
4746 o Minor bugfixes (log messages):
4747 - Fix a bug where clients using bridges would report themselves
4748 as 50% bootstrapped even without a live consensus document.
4749 Fixes bug 9922; bugfix on 0.2.1.1-alpha.
4750 - Suppress a warning where, if there's only one directory authority
4751 in the network, we would complain that votes and signatures cannot
4752 be uploaded to other directory authorities. Fixes bug 10842;
4753 bugfix on 0.2.2.26-beta.
4754 - Report bootstrapping progress correctly when we're downloading
4755 microdescriptors. We had updated our "do we have enough microdescs
4756 to begin building circuits?" logic most recently in 0.2.4.10-alpha
4757 (see bug 5956), but we left the bootstrap status event logic at
4758 "how far through getting 1/4 of them are we?" Fixes bug 9958;
4759 bugfix on 0.2.2.36, which is where they diverged (see bug 5343).
4761 o Minor bugfixes (new since 0.2.5.1-alpha, also in 0.2.4.20):
4762 - Avoid a crash bug when starting with a corrupted microdescriptor
4763 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4764 - If we fail to dump a previously cached microdescriptor to disk, avoid
4765 freeing duplicate data later on. Fixes bug 10423; bugfix on
4766 0.2.4.13-alpha. Spotted by "bobnomnom".
4768 o Minor bugfixes on 0.2.4.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4769 - Correctly log long IPv6 exit policies, instead of truncating them
4770 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4771 - Our default TLS ecdhe groups were backwards: we meant to be using
4772 P224 for relays (for performance win) and P256 for bridges (since
4773 it is more common in the wild). Instead we had it backwards. After
4774 reconsideration, we decided that the default should be P256 on all
4775 hosts, since its security is probably better, and since P224 is
4776 reportedly used quite little in the wild. Found by "skruffy" on
4777 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4778 - Free directory authority certificate download statuses on exit
4779 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4781 o Minor bugfixes on 0.2.3.x (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4782 - If the guard we choose first doesn't answer, we would try the
4783 second guard, but once we connected to the second guard we would
4784 abandon it and retry the first one, slowing down bootstrapping.
4785 The fix is to treat all our initially chosen guards as acceptable
4786 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4787 - Fix an assertion failure that would occur when disabling the
4788 ORPort setting on a running Tor process while accounting was
4789 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4790 - When examining the list of network interfaces to find our address,
4791 do not consider non-running or disabled network interfaces. Fixes
4792 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4793 - Avoid an off-by-one error when checking buffer boundaries when
4794 formatting the exit status of a pluggable transport helper.
4795 This is probably not an exploitable bug, but better safe than
4796 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4799 o Removed code and features:
4800 - Clients now reject any directory authority certificates lacking
4801 a dir-key-crosscert element. These have been included since
4802 0.2.1.9-alpha, so there's no real reason for them to be optional
4803 any longer. Completes proposal 157. Resolves ticket 10162.
4804 - Remove all code that existed to support the v2 directory system,
4805 since there are no longer any v2 directory authorities. Resolves
4807 - Remove the HSAuthoritativeDir and AlternateHSAuthority torrc
4808 options, which were used for designating authorities as "Hidden
4809 service authorities". There has been no use of hidden service
4810 authorities since 0.2.2.1-alpha, when we stopped uploading or
4811 downloading v0 hidden service descriptors. Fixes bug 10881; also
4812 part of a fix for bug 10841.
4814 o Code simplification and refactoring:
4815 - Remove some old fallback code designed to keep Tor clients working
4816 in a network with only two working relays. Elsewhere in the code we
4817 have long since stopped supporting such networks, so there wasn't
4818 much point in keeping it around. Addresses ticket 9926.
4819 - Reject 0-length EXTEND2 cells more explicitly. Fixes bug 10536;
4820 bugfix on 0.2.4.8-alpha. Reported by "cypherpunks".
4821 - Remove data structures which were introduced to implement the
4822 CellStatistics option: they are now redundant with the addition
4823 of a timestamp to the regular packed_cell_t data structure, which
4824 we did in 0.2.4.18-rc in order to resolve ticket 9093. Implements
4827 o Documentation (man page) fixes:
4828 - Update manpage to describe some of the files you can expect to
4829 find in Tor's DataDirectory. Addresses ticket 9839.
4830 - Document that all but one DirPort entry must have the NoAdvertise
4831 flag set. Fixes bug 10470; bugfix on 0.2.3.3-alpha / 0.2.3.16-alpha.
4833 o Documentation fixes (new since 0.2.5.1-alpha, also in 0.2.4.18-rc):
4834 - Clarify the usage and risks of setting the ContactInfo torrc line
4835 for your relay or bridge. Resolves ticket 9854.
4836 - Add anchors to the manpage so we can link to the html version of
4837 the documentation for specific options. Resolves ticket 9866.
4838 - Replace remaining references to DirServer in man page and
4839 log entries. Resolves ticket 10124.
4842 - Make the "tor-gencert" tool used by directory authority operators
4843 create 2048-bit signing keys by default (rather than 1024-bit, since
4844 1024-bit is uncomfortably small these days). Addresses ticket 10324.
4847 Changes in version 0.2.4.20 - 2013-12-22
4848 Tor 0.2.4.20 fixes potentially poor random number generation for users
4849 who 1) use OpenSSL 1.0.0 or later, 2) set "HardwareAccel 1" in their
4850 torrc file, 3) have "Sandy Bridge" or "Ivy Bridge" Intel processors,
4851 and 4) have no state file in their DataDirectory (as would happen on
4852 first start). Users who generated relay or hidden service identity
4853 keys in such a situation should discard them and generate new ones.
4855 This release also fixes a logic error that caused Tor clients to build
4856 many more preemptive circuits than they actually need.
4859 - Do not allow OpenSSL engines to replace the PRNG, even when
4860 HardwareAccel is set. The only default builtin PRNG engine uses
4861 the Intel RDRAND instruction to replace the entire PRNG, and
4862 ignores all attempts to seed it with more entropy. That's
4863 cryptographically stupid: the right response to a new alleged
4864 entropy source is never to discard all previously used entropy
4865 sources. Fixes bug 10402; works around behavior introduced in
4866 OpenSSL 1.0.0. Diagnosis and investigation thanks to "coderman"
4868 - Fix assertion failure when AutomapHostsOnResolve yields an IPv6
4869 address. Fixes bug 10465; bugfix on 0.2.4.7-alpha.
4870 - Avoid launching spurious extra circuits when a stream is pending.
4871 This fixes a bug where any circuit that _wasn't_ unusable for new
4872 streams would be treated as if it were, causing extra circuits to
4873 be launched. Fixes bug 10456; bugfix on 0.2.4.12-alpha.
4876 - Avoid a crash bug when starting with a corrupted microdescriptor
4877 cache file. Fixes bug 10406; bugfix on 0.2.2.6-alpha.
4878 - If we fail to dump a previously cached microdescriptor to disk, avoid
4879 freeing duplicate data later on. Fixes bug 10423; bugfix on
4880 0.2.4.13-alpha. Spotted by "bobnomnom".
4883 Changes in version 0.2.4.19 - 2013-12-11
4884 The Tor 0.2.4 release series is dedicated to the memory of Aaron Swartz
4885 (1986-2013). Aaron worked on diverse projects including helping to guide
4886 Creative Commons, playing a key role in stopping SOPA/PIPA, bringing
4887 transparency to the U.S government's PACER documents, and contributing
4888 design and development for Tor and Tor2Web. Aaron was one of the latest
4889 martyrs in our collective fight for civil liberties and human rights,
4890 and his death is all the more painful because he was one of us.
4892 Tor 0.2.4.19, the first stable release in the 0.2.4 branch, features
4893 a new circuit handshake and link encryption that use ECC to provide
4894 better security and efficiency; makes relays better manage circuit
4895 creation requests; uses "directory guards" to reduce client enumeration
4896 risks; makes bridges collect and report statistics about the pluggable
4897 transports they support; cleans up and improves our geoip database;
4898 gets much closer to IPv6 support for clients, bridges, and relays; makes
4899 directory authorities use measured bandwidths rather than advertised
4900 ones when computing flags and thresholds; disables client-side DNS
4901 caching to reduce tracking risks; and fixes a big bug in bridge
4902 reachability testing. This release introduces two new design
4903 abstractions in the code: a new "channel" abstraction between circuits
4904 and or_connections to allow for implementing alternate relay-to-relay
4905 transports, and a new "circuitmux" abstraction storing the queue of
4906 circuits for a channel. The release also includes many stability,
4907 security, and privacy fixes.
4910 Changes in version 0.2.4.18-rc - 2013-11-16
4911 Tor 0.2.4.18-rc is the fourth release candidate for the Tor 0.2.4.x
4912 series. It takes a variety of fixes from the 0.2.5.x branch to improve
4913 stability, performance, and better handling of edge cases.
4916 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
4917 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
4918 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
4919 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
4920 them to solve bug 6033.)
4923 - No longer stop reading or writing on cpuworker connections when
4924 our rate limiting buckets go empty. Now we should handle circuit
4925 handshake requests more promptly. Resolves bug 9731.
4926 - If we are unable to save a microdescriptor to the journal, do not
4927 drop it from memory and then reattempt downloading it. Fixes bug
4928 9645; bugfix on 0.2.2.6-alpha.
4929 - Stop trying to bootstrap all our directory information from
4930 only our first guard. Discovered while fixing bug 9946; bugfix
4932 - The new channel code sometimes lost track of in-progress circuits,
4933 causing long-running clients to stop building new circuits. The
4934 fix is to always call circuit_n_chan_done(chan, 0) from
4935 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
4937 o Minor bugfixes (on 0.2.4.x):
4938 - Correctly log long IPv6 exit policies, instead of truncating them
4939 or reporting an error. Fixes bug 9596; bugfix on 0.2.4.7-alpha.
4940 - Our default TLS ecdhe groups were backwards: we meant to be using
4941 P224 for relays (for performance win) and P256 for bridges (since
4942 it is more common in the wild). Instead we had it backwards. After
4943 reconsideration, we decided that the default should be P256 on all
4944 hosts, since its security is probably better, and since P224 is
4945 reportedly used quite little in the wild. Found by "skruffy" on
4946 IRC. Fix for bug 9780; bugfix on 0.2.4.8-alpha.
4947 - Free directory authority certificate download statuses on exit
4948 rather than leaking them. Fixes bug 9644; bugfix on 0.2.4.13-alpha.
4950 o Minor bugfixes (on 0.2.3.x and earlier):
4951 - If the guard we choose first doesn't answer, we would try the
4952 second guard, but once we connected to the second guard we would
4953 abandon it and retry the first one, slowing down bootstrapping.
4954 The fix is to treat all our initially chosen guards as acceptable
4955 to use. Fixes bug 9946; bugfix on 0.1.1.11-alpha.
4956 - Fix an assertion failure that would occur when disabling the
4957 ORPort setting on a running Tor process while accounting was
4958 enabled. Fixes bug 6979; bugfix on 0.2.2.18-alpha.
4959 - When examining the list of network interfaces to find our address,
4960 do not consider non-running or disabled network interfaces. Fixes
4961 bug 9904; bugfix on 0.2.3.11-alpha. Patch from "hantwister".
4962 - Avoid an off-by-one error when checking buffer boundaries when
4963 formatting the exit status of a pluggable transport helper.
4964 This is probably not an exploitable bug, but better safe than
4965 sorry. Fixes bug 9928; bugfix on 0.2.3.18-rc. Bug found by
4968 o Minor features (protecting client timestamps):
4969 - Clients no longer send timestamps in their NETINFO cells. These were
4970 not used for anything, and they provided one small way for clients
4971 to be distinguished from each other as they moved from network to
4972 network or behind NAT. Implements part of proposal 222.
4973 - Clients now round timestamps in INTRODUCE cells down to the nearest
4974 10 minutes. If a new Support022HiddenServices option is set to 0, or
4975 if it's set to "auto" and the feature is disabled in the consensus,
4976 the timestamp is sent as 0 instead. Implements part of proposal 222.
4977 - Stop sending timestamps in AUTHENTICATE cells. This is not such
4978 a big deal from a security point of view, but it achieves no actual
4979 good purpose, and isn't needed. Implements part of proposal 222.
4980 - Reduce down accuracy of timestamps in hidden service descriptors.
4981 Implements part of proposal 222.
4983 o Minor features (other):
4984 - Improve the circuit queue out-of-memory handler. Previously, when
4985 we ran low on memory, we'd close whichever circuits had the most
4986 queued cells. Now, we close those that have the *oldest* queued
4987 cells, on the theory that those are most responsible for us
4988 running low on memory. Based on analysis from a forthcoming paper
4989 by Jansen, Tschorsch, Johnson, and Scheuermann. Fixes bug 9093.
4990 - Generate bootstrapping status update events correctly when fetching
4991 microdescriptors. Fixes bug 9927.
4992 - Update to the October 2 2013 Maxmind GeoLite Country database.
4994 o Documentation fixes:
4995 - Clarify the usage and risks of setting the ContactInfo torrc line
4996 for your relay or bridge. Resolves ticket 9854.
4997 - Add anchors to the manpage so we can link to the html version of
4998 the documentation for specific options. Resolves ticket 9866.
4999 - Replace remaining references to DirServer in man page and
5000 log entries. Resolves ticket 10124.
5003 Changes in version 0.2.5.1-alpha - 2013-10-02
5004 Tor 0.2.5.1-alpha introduces experimental support for syscall sandboxing
5005 on Linux, allows bridges that offer pluggable transports to report usage
5006 statistics, fixes many issues to make testing easier, and provides
5007 a pile of minor features and bugfixes that have been waiting for a
5008 release of the new branch.
5010 This is the first alpha release in a new series, so expect there to
5011 be bugs. Users who would rather test out a more stable branch should
5012 stay with 0.2.4.x for now.
5014 o Major features (security):
5015 - Use the seccomp2 syscall filtering facility on Linux to limit
5016 which system calls Tor can invoke. This is an experimental,
5017 Linux-only feature to provide defense-in-depth against unknown
5018 attacks. To try turning it on, set "Sandbox 1" in your torrc
5019 file. Please be ready to report bugs. We hope to add support
5020 for better sandboxing in the future, including more fine-grained
5021 filters, better division of responsibility, and support for more
5022 platforms. This work has been done by Cristian-Matei Toader for
5023 Google Summer of Code.
5024 - Re-enable TLS 1.1 and 1.2 when built with OpenSSL 1.0.1e or later.
5025 Resolves ticket 6055. (OpenSSL before 1.0.1 didn't have TLS 1.1 or
5026 1.2, and OpenSSL from 1.0.1 through 1.0.1d had bugs that prevented
5027 renegotiation from working with TLS 1.1 or 1.2, so we had disabled
5028 them to solve bug 6033.)
5030 o Major features (other):
5031 - Add support for passing arguments to managed pluggable transport
5032 proxies. Implements ticket 3594.
5033 - Bridges now track GeoIP information and the number of their users
5034 even when pluggable transports are in use, and report usage
5035 statistics in their extra-info descriptors. Resolves tickets 4773
5037 - Make testing Tor networks bootstrap better: lower directory fetch
5038 retry schedules and maximum interval without directory requests,
5039 and raise maximum download tries. Implements ticket 6752.
5040 - Add make target 'test-network' to run tests on a Chutney network.
5041 Implements ticket 8530.
5042 - The ntor handshake is now on-by-default, no matter what the
5043 directory authorities recommend. Implements ticket 8561.
5046 - Instead of writing destroy cells directly to outgoing connection
5047 buffers, queue them and intersperse them with other outgoing cells.
5048 This can prevent a set of resource starvation conditions where too
5049 many pending destroy cells prevent data cells from actually getting
5050 delivered. Reported by "oftc_must_be_destroyed". Fixes bug 7912;
5051 bugfix on 0.2.0.1-alpha.
5052 - If we are unable to save a microdescriptor to the journal, do not
5053 drop it from memory and then reattempt downloading it. Fixes bug
5054 9645; bugfix on 0.2.2.6-alpha.
5055 - The new channel code sometimes lost track of in-progress circuits,
5056 causing long-running clients to stop building new circuits. The
5057 fix is to always call circuit_n_chan_done(chan, 0) from
5058 channel_closed(). Fixes bug 9776; bugfix on 0.2.4.17-rc.
5061 - Tor now builds each source file in two modes: a mode that avoids
5062 exposing identifiers needlessly, and another mode that exposes
5063 more identifiers for testing. This lets the compiler do better at
5064 optimizing the production code, while enabling us to take more
5065 radical measures to let the unit tests test things.
5066 - The production builds no longer include functions used only in
5067 the unit tests; all functions exposed from a module only for
5068 unit-testing are now static in production builds.
5069 - Add an --enable-coverage configuration option to make the unit
5070 tests (and a new src/or/tor-cov target) to build with gcov test
5074 - We now have rudimentary function mocking support that our unit
5075 tests can use to test functions in isolation. Function mocking
5076 lets the tests temporarily replace a function's dependencies with
5077 stub functions, so that the tests can check the function without
5078 invoking the other functions it calls.
5079 - Add more unit tests for the <circid,channel>->circuit map, and
5080 the destroy-cell-tracking code to fix bug 7912.
5081 - Unit tests for failing cases of the TAP onion handshake.
5082 - More unit tests for address-manipulation functions.
5084 o Minor features (protecting client timestamps):
5085 - Clients no longer send timestamps in their NETINFO cells. These were
5086 not used for anything, and they provided one small way for clients
5087 to be distinguished from each other as they moved from network to
5088 network or behind NAT. Implements part of proposal 222.
5089 - Clients now round timestamps in INTRODUCE cells down to the nearest
5090 10 minutes. If a new Support022HiddenServices option is set to 0, or
5091 if it's set to "auto" and the feature is disabled in the consensus,
5092 the timestamp is sent as 0 instead. Implements part of proposal 222.
5093 - Stop sending timestamps in AUTHENTICATE cells. This is not such
5094 a big deal from a security point of view, but it achieves no actual
5095 good purpose, and isn't needed. Implements part of proposal 222.
5096 - Reduce down accuracy of timestamps in hidden service descriptors.
5097 Implements part of proposal 222.
5099 o Minor features (config options):
5100 - Config (torrc) lines now handle fingerprints which are missing
5101 their initial '$'. Resolves ticket 4341; improvement over 0.0.9pre5.
5102 - Support a --dump-config option to print some or all of the
5103 configured options. Mainly useful for debugging the command-line
5104 option parsing code. Helps resolve ticket 4647.
5105 - Raise awareness of safer logging: notify user of potentially
5106 unsafe config options, like logging more verbosely than severity
5107 "notice" or setting SafeLogging to 0. Resolves ticket 5584.
5108 - Add a new configuration option TestingV3AuthVotingStartOffset
5109 that bootstraps a network faster by changing the timing for
5110 consensus votes. Addresses ticket 8532.
5111 - Add a new torrc option "ServerTransportOptions" that allows
5112 bridge operators to pass configuration parameters to their
5113 pluggable transports. Resolves ticket 8929.
5114 - The config (torrc) file now accepts bandwidth and space limits in
5115 bits as well as bytes. (Anywhere that you can say "2 Kilobytes",
5116 you can now say "16 kilobits", and so on.) Resolves ticket 9214.
5119 o Minor features (build):
5120 - Add support for `--library-versions` flag. Implements ticket 6384.
5121 - Return the "unexpected sendme" warnings to a warn severity, but make
5122 them rate limited, to help diagnose ticket 8093.
5123 - Detect a missing asciidoc, and warn the user about it, during
5124 configure rather than at build time. Fixes issue 6506. Patch from
5127 o Minor features (other):
5128 - Use the SOCK_NONBLOCK socket type, if supported, to open nonblocking
5129 sockets in a single system call. Implements ticket 5129.
5130 - Log current accounting state (bytes sent and received + remaining
5131 time for the current accounting period) in the relay's heartbeat
5132 message. Implements ticket 5526; patch from Peter Retzlaff.
5133 - Implement the TRANSPORT_LAUNCHED control port event that
5134 notifies controllers about new launched pluggable
5135 transports. Resolves ticket 5609.
5136 - If we're using the pure-C 32-bit curve25519_donna implementation
5137 of curve25519, build it with the -fomit-frame-pointer option to
5138 make it go faster on register-starved hosts. This improves our
5139 handshake performance by about 6% on i386 hosts without nacl.
5141 - Update to the September 4 2013 Maxmind GeoLite Country database.
5144 - Set the listen() backlog limit to the largest actually supported
5145 on the system, not to the value in a header file. Fixes bug 9716;
5146 bugfix on every released Tor.
5147 - No longer accept malformed http headers when parsing urls from
5148 headers. Now we reply with Bad Request ("400"). Fixes bug 2767;
5149 bugfix on 0.0.6pre1.
5150 - In munge_extrainfo_into_routerinfo(), check the return value of
5151 memchr(). This would have been a serious issue if we ever passed
5152 it a non-extrainfo. Fixes bug 8791; bugfix on 0.2.0.6-alpha. Patch
5154 - On the chance that somebody manages to build Tor on a
5155 platform where time_t is unsigned, correct the way that
5156 microdesc_add_to_cache() handles negative time arguments.
5157 Fixes bug 8042; bugfix on 0.2.3.1-alpha.
5158 - Reject relative control socket paths and emit a warning. Previously,
5159 single-component control socket paths would be rejected, but Tor
5160 would not log why it could not validate the config. Fixes bug 9258;
5161 bugfix on 0.2.3.16-alpha.
5163 o Minor bugfixes (command line):
5164 - Use a single command-line parser for parsing torrc options on the
5165 command line and for finding special command-line options to avoid
5166 inconsistent behavior for torrc option arguments that have the same
5167 names as command-line options. Fixes bugs 4647 and 9578; bugfix on
5169 - No longer allow 'tor --hash-password' with no arguments. Fixes bug
5170 9573; bugfix on 0.0.9pre5.
5172 o Minor fixes (build, auxiliary programs):
5173 - Stop preprocessing the "torify" script with autoconf, since
5174 it no longer refers to LOCALSTATEDIR. Fixes bug 5505; patch
5176 - The tor-fw-helper program now follows the standard convention and
5177 exits with status code "0" on success. Fixes bug 9030; bugfix on
5178 0.2.3.1-alpha. Patch by Arlo Breault.
5179 - Corrected ./configure advice for what openssl dev package you should
5180 install on Debian. Fixes bug 9207; bugfix on 0.2.0.1-alpha.
5182 o Minor code improvements:
5183 - Remove constants and tests for PKCS1 padding; it's insecure and
5184 shouldn't be used for anything new. Fixes bug 8792; patch
5186 - Remove instances of strcpy() from the unit tests. They weren't
5187 hurting anything, since they were only in the unit tests, but it's
5188 embarassing to have strcpy() in the code at all, and some analysis
5189 tools don't like it. Fixes bug 8790; bugfix on 0.2.3.6-alpha and
5190 0.2.3.8-alpha. Patch from Arlo Breault.
5193 - Remove migration code from when we renamed the "cached-routers"
5194 file to "cached-descriptors" back in 0.2.0.8-alpha. This
5195 incidentally resolves ticket 6502 by cleaning up the related code
5196 a bit. Patch from Akshay Hebbar.
5198 o Code simplification and refactoring:
5199 - Extract the common duplicated code for creating a subdirectory
5200 of the data directory and writing to a file in it. Fixes ticket
5201 4282; patch from Peter Retzlaff.
5202 - Since OpenSSL 0.9.7, the i2d_*() functions support allocating output
5203 buffer. Avoid calling twice: i2d_RSAPublicKey(), i2d_DHparams(),
5204 i2d_X509(), and i2d_PublicKey(). Resolves ticket 5170.
5205 - Add a set of accessor functions for the circuit timeout data
5206 structure. Fixes ticket 6153; patch from "piet".
5207 - Clean up exit paths from connection_listener_new(). Closes ticket
5208 8789. Patch from Arlo Breault.
5209 - Since we rely on OpenSSL 0.9.8 now, we can use EVP_PKEY_cmp()
5210 and drop our own custom pkey_eq() implementation. Fixes bug 9043.
5211 - Use a doubly-linked list to implement the global circuit list.
5212 Resolves ticket 9108. Patch from Marek Majkowski.
5213 - Remove contrib/id_to_fp.c since it wasn't used anywhere.
5216 Changes in version 0.2.4.17-rc - 2013-09-05
5217 Tor 0.2.4.17-rc is the third release candidate for the Tor 0.2.4.x
5218 series. It adds an emergency step to help us tolerate the massive
5219 influx of users: 0.2.4 clients using the new (faster and safer) "NTor"
5220 circuit-level handshakes now effectively jump the queue compared to
5221 the 0.2.3 clients using "TAP" handshakes. This release also fixes a
5222 big bug hindering bridge reachability tests.
5225 - Relays now process the new "NTor" circuit-level handshake requests
5226 with higher priority than the old "TAP" circuit-level handshake
5227 requests. We still process some TAP requests to not totally starve
5228 0.2.3 clients when NTor becomes popular. A new consensus parameter
5229 "NumNTorsPerTAP" lets us tune the balance later if we need to.
5230 Implements ticket 9574.
5233 - If the circuit build timeout logic is disabled (via the consensus,
5234 or because we are an authority), then don't build testing circuits.
5235 Fixes bug 9657; bugfix on 0.2.2.14-alpha.
5236 - Bridges now send AUTH_CHALLENGE cells during their v3 handshakes;
5237 previously they did not, which prevented them from receiving
5238 successful connections from relays for self-test or bandwidth
5239 testing. Also, when a relay is extending a circuit to a bridge,
5240 it needs to send a NETINFO cell, even when the bridge hasn't sent
5241 an AUTH_CHALLENGE cell. Fixes bug 9546; bugfix on 0.2.3.6-alpha.
5242 - If the time to download the next old-style networkstatus is in
5243 the future, do not decline to consider whether to download the
5244 next microdescriptor networkstatus. Fixes bug 9564; bugfix on
5248 - Avoid double-closing the listener socket in our socketpair()
5249 replacement (used on Windows) in the case where the addresses on
5250 our opened sockets don't match what we expected. Fixes bug 9400;
5251 bugfix on 0.0.2pre7. Found by Coverity.
5253 o Minor fixes (config options):
5254 - Avoid overflows when the user sets MaxCircuitDirtiness to a
5255 ridiculously high value, by imposing a (ridiculously high) 30-day
5256 maximum on MaxCircuitDirtiness.
5257 - Fix the documentation of HeartbeatPeriod to say that the heartbeat
5258 message is logged at notice, not at info.
5259 - Warn and fail if a server is configured not to advertise any
5260 ORPorts at all. (We need *something* to put in our descriptor,
5261 or we just won't work.)
5264 - Track how many "TAP" and "NTor" circuit handshake requests we get,
5265 and how many we complete, and log it every hour to help relay
5266 operators follow trends in network load. Addresses ticket 9658.
5267 - Update to the August 7 2013 Maxmind GeoLite Country database.
5270 Changes in version 0.2.4.16-rc - 2013-08-10
5271 Tor 0.2.4.16-rc is the second release candidate for the Tor 0.2.4.x
5272 series. It fixes several crash bugs in the 0.2.4 branch.
5275 - Fix a bug in the voting algorithm that could yield incorrect results
5276 when a non-naming authority declared too many flags. Fixes bug 9200;
5277 bugfix on 0.2.0.3-alpha.
5278 - Fix an uninitialized read that could in some cases lead to a remote
5279 crash while parsing INTRODUCE2 cells. Bugfix on 0.2.4.1-alpha.
5280 Anybody running a hidden service on the experimental 0.2.4.x
5281 branch should upgrade. (This is, so far as we know, unrelated to
5283 - Avoid an assertion failure when processing DNS replies without the
5284 answer types we expected. Fixes bug 9337; bugfix on 0.2.4.7-alpha.
5285 - Avoid a crash when using --hash-password. Fixes bug 9295; bugfix on
5286 0.2.4.15-rc. Found by stem integration tests.
5289 - Fix an invalid memory read that occured when a pluggable
5290 transport proxy failed its configuration protocol.
5291 Fixes bug 9288; bugfix on 0.2.4.1-alpha.
5292 - When evaluating whether to use a connection that we haven't
5293 decided is canonical using a recent link protocol version,
5294 decide that it's canonical only if it used address _does_
5295 match the desired address. Fixes bug 9309; bugfix on
5296 0.2.4.4-alpha. Reported by skruffy.
5297 - Make the default behavior of NumDirectoryGuards be to track
5298 NumEntryGuards. Now a user who changes only NumEntryGuards will get
5299 the behavior she expects. Fixes bug 9354; bugfix on 0.2.4.8-alpha.
5300 - Fix a spurious compilation warning with some older versions of
5301 GCC on FreeBSD. Fixes bug 9254; bugfix on 0.2.4.14-alpha.
5304 - Update to the July 3 2013 Maxmind GeoLite Country database.
5307 Changes in version 0.2.4.15-rc - 2013-07-01
5308 Tor 0.2.4.15-rc is the first release candidate for the Tor 0.2.4.x
5309 series. It fixes a few smaller bugs, but generally appears stable.
5310 Please test it and let us know whether it is!
5313 - When receiving a new configuration file via the control port's
5314 LOADCONF command, do not treat the defaults file as absent.
5315 Fixes bug 9122; bugfix on 0.2.3.9-alpha.
5318 - Issue a warning when running with the bufferevents backend enabled.
5319 It's still not stable, and people should know that they're likely
5320 to hit unexpected problems. Closes ticket 9147.
5323 Changes in version 0.2.4.14-alpha - 2013-06-18
5324 Tor 0.2.4.14-alpha fixes a pair of client guard enumeration problems
5325 present in 0.2.4.13-alpha.
5328 - When we have too much memory queued in circuits (according to a new
5329 MaxMemInCellQueues option), close the circuits consuming the most
5330 memory. This prevents us from running out of memory as a relay if
5331 circuits fill up faster than they can be drained. Fixes bug 9063;
5332 bugfix on the 54th commit of Tor. This bug is a further fix beyond
5333 bug 6252, whose fix was merged into 0.2.3.21-rc.
5335 This change also fixes an earlier approach taken in 0.2.4.13-alpha,
5336 where we tried to solve this issue simply by imposing an upper limit
5337 on the number of queued cells for a single circuit. That approach
5338 proved to be problematic, since there are ways to provoke clients to
5339 send a number of cells in excess of any such reasonable limit. Fixes
5340 bug 9072; bugfix on 0.2.4.13-alpha.
5342 - Limit hidden service descriptors to at most ten introduction
5343 points, to slow one kind of guard enumeration. Fixes bug 9002;
5344 bugfix on 0.1.1.11-alpha.
5347 Changes in version 0.2.4.13-alpha - 2013-06-14
5348 Tor 0.2.4.13-alpha fixes a variety of potential remote crash
5349 vulnerabilities, makes socks5 username/password circuit isolation
5350 actually actually work (this time for sure!), and cleans up a bunch
5351 of other issues in preparation for a release candidate.
5353 o Major bugfixes (robustness):
5354 - Close any circuit that has too many cells queued on it. Fixes
5355 bug 9063; bugfix on the 54th commit of Tor. This bug is a further
5356 fix beyond bug 6252, whose fix was merged into 0.2.3.21-rc.
5357 - Prevent the get_freelists() function from running off the end of
5358 the list of freelists if it somehow gets an unrecognized
5359 allocation. Fixes bug 8844; bugfix on 0.2.0.16-alpha. Reported by
5361 - Avoid an assertion failure on OpenBSD (and perhaps other BSDs)
5362 when an exit connection with optimistic data succeeds immediately
5363 rather than returning EINPROGRESS. Fixes bug 9017; bugfix on
5365 - Fix a directory authority crash bug when building a consensus
5366 using an older consensus as its basis. Fixes bug 8833. Bugfix
5370 - Avoid a memory leak where we would leak a consensus body when we
5371 find that a consensus which we couldn't previously verify due to
5372 missing certificates is now verifiable. Fixes bug 8719; bugfix
5374 - We used to always request authority certificates by identity digest,
5375 meaning we'd get the newest one even when we wanted one with a
5376 different signing key. Then we would complain about being given
5377 a certificate we already had, and never get the one we really
5378 wanted. Now we use the "fp-sk/" resource as well as the "fp/"
5379 resource to request the one we want. Fixes bug 5595; bugfix on
5381 - Follow the socks5 protocol when offering username/password
5382 authentication. The fix for bug 8117 exposed this bug, and it
5383 turns out real-world applications like Pidgin do care. Bugfix on
5384 0.2.3.2-alpha; fixes bug 8879.
5385 - Prevent failures on Windows Vista and later when rebuilding the
5386 microdescriptor cache. Diagnosed by Robert Ransom. Fixes bug 8822;
5387 bugfix on 0.2.4.12-alpha.
5390 - Fix an impossible buffer overrun in the AES unit tests. Fixes
5391 bug 8845; bugfix on 0.2.0.7-alpha. Found by eugenis.
5392 - If for some reason we fail to write a microdescriptor while
5393 rebuilding the cache, do not let the annotations from that
5394 microdescriptor linger in the cache file, and do not let the
5395 microdescriptor stay recorded as present in its old location.
5396 Fixes bug 9047; bugfix on 0.2.2.6-alpha.
5397 - Fix a memory leak that would occur whenever a configuration
5398 option changed. Fixes bug 8718; bugfix on 0.2.3.3-alpha.
5399 - Paste the description for PathBias parameters from the man
5400 page into or.h, so the code documents them too. Fixes bug 7982;
5401 bugfix on 0.2.3.17-beta and 0.2.4.8-alpha.
5402 - Relays now treat a changed IPv6 ORPort as sufficient reason to
5403 publish an updated descriptor. Fixes bug 6026; bugfix on
5405 - When launching a resolve request on behalf of an AF_UNIX control
5406 socket, omit the address field of the new entry connection, used in
5407 subsequent controller events, rather than letting tor_dup_addr()
5408 set it to "<unknown address type>". Fixes bug 8639; bugfix on
5411 o Minor bugfixes (log messages):
5412 - Fix a scaling issue in the path bias accounting code that
5413 resulted in "Bug:" log messages from either
5414 pathbias_scale_close_rates() or pathbias_count_build_success().
5415 This represents a bugfix on a previous bugfix: the original fix
5416 attempted in 0.2.4.10-alpha was incomplete. Fixes bug 8235; bugfix
5418 - Give a less useless error message when the user asks for an IPv4
5419 address on an IPv6-only port, or vice versa. Fixes bug 8846; bugfix
5423 - Downgrade "unexpected SENDME" warnings to protocol-warn for 0.2.4.x,
5424 to tolerate bug 8093 for now.
5425 - Add an "ignoring-advertised-bws" boolean to the flag-threshold lines
5426 in directory authority votes to describe whether they have enough
5427 measured bandwidths to ignore advertised (relay descriptor)
5428 bandwidth claims. Resolves ticket 8711.
5429 - Update to the June 5 2013 Maxmind GeoLite Country database.
5431 o Removed documentation:
5432 - Remove some of the older contents of doc/ as obsolete; move others
5433 to torspec.git. Fixes bug 8965.
5435 o Code simplification and refactoring:
5436 - Avoid using character buffers when constructing most directory
5437 objects: this approach was unwieldy and error-prone. Instead,
5438 build smartlists of strings, and concatenate them when done.
5441 Changes in version 0.2.4.12-alpha - 2013-04-18
5442 Tor 0.2.4.12-alpha moves Tor forward on several fronts: it starts the
5443 process for lengthening the guard rotation period, makes directory
5444 authority opinions in the consensus a bit less gameable, makes socks5
5445 username/password circuit isolation actually work, and fixes a wide
5446 variety of other issues.
5449 - Raise the default time that a client keeps an entry guard from
5450 "1-2 months" to "2-3 months", as suggested by Tariq Elahi's WPES
5451 2012 paper. (We would make it even longer, but we need better client
5452 load balancing first.) Also, make the guard lifetime controllable
5453 via a new GuardLifetime torrc option and a GuardLifetime consensus
5454 parameter. Start of a fix for bug 8240; bugfix on 0.1.1.11-alpha.
5455 - Directory authorities now prefer using measured bandwidths to
5456 advertised ones when computing flags and thresholds. Resolves
5458 - Directory authorities that have more than a threshold number
5459 of relays with measured bandwidths now treat relays with unmeasured
5460 bandwidths as having bandwidth 0. Resolves ticket 8435.
5462 o Major bugfixes (assert / resource use):
5463 - Avoid a bug where our response to TLS renegotiation under certain
5464 network conditions could lead to a busy-loop, with 100% CPU
5465 consumption. Fixes bug 5650; bugfix on 0.2.0.16-alpha.
5466 - Avoid an assertion when we discover that we'd like to write a cell
5467 onto a closing connection: just discard the cell. Fixes another
5468 case of bug 7350; bugfix on 0.2.4.4-alpha.
5470 o Major bugfixes (client-side privacy):
5471 - When we mark a circuit as unusable for new circuits, have it
5472 continue to be unusable for new circuits even if MaxCircuitDirtiness
5473 is increased too much at the wrong time, or the system clock jumps
5474 backwards. Fixes bug 6174; bugfix on 0.0.2pre26.
5475 - If ClientDNSRejectInternalAddresses ("do not believe DNS queries
5476 which have resolved to internal addresses") is set, apply that
5477 rule to IPv6 as well. Fixes bug 8475; bugfix on 0.2.0.7-alpha.
5478 - When an exit relay rejects a stream with reason "exit policy", but
5479 we only know an exit policy summary (e.g. from the microdesc
5480 consensus) for it, do not mark the relay as useless for all exiting.
5481 Instead, mark just the circuit as unsuitable for that particular
5482 address. Fixes part of bug 7582; bugfix on 0.2.3.2-alpha.
5483 - Allow applications to get proper stream isolation with
5484 IsolateSOCKSAuth. Many SOCKS5 clients that want to offer
5485 username/password authentication also offer "no authentication". Tor
5486 had previously preferred "no authentication", so the applications
5487 never actually sent Tor their auth details. Now Tor selects
5488 username/password authentication if it's offered. You can disable
5489 this behavior on a per-SOCKSPort basis via PreferSOCKSNoAuth. Fixes
5490 bug 8117; bugfix on 0.2.3.3-alpha.
5492 o Major bugfixes (other):
5493 - When unable to find any working directory nodes to use as a
5494 directory guard, give up rather than adding the same non-working
5495 nodes to the directory guard list over and over. Fixes bug 8231;
5496 bugfix on 0.2.4.8-alpha.
5499 - Reject as invalid most directory objects containing a NUL.
5500 Belt-and-suspender fix for bug 8037.
5501 - In our testsuite, create temporary directories with a bit more
5502 entropy in their name to make name collisions less likely. Fixes
5504 - Add CACHED keyword to ADDRMAP events in the control protocol
5505 to indicate whether a DNS result will be cached or not. Resolves
5507 - Update to the April 3 2013 Maxmind GeoLite Country database.
5509 o Minor features (build):
5510 - Detect and reject attempts to build Tor with threading support
5511 when OpenSSL has been compiled without threading support.
5513 - Clarify that when autoconf is checking for nacl, it is checking
5514 specifically for nacl with a fast curve25519 implementation.
5516 - Warn if building on a platform with an unsigned time_t: there
5517 are too many places where Tor currently assumes that time_t can
5518 hold negative values. We'd like to fix them all, but probably
5521 o Minor bugfixes (build):
5522 - Fix some bugs in tor-fw-helper-natpmp when trying to build and
5523 run it on Windows. More bugs likely remain. Patch from Gisle Vanem.
5524 Fixes bug 7280; bugfix on 0.2.3.1-alpha.
5525 - Add the old src/or/micro-revision.i filename to CLEANFILES.
5526 On the off chance that somebody has one, it will go away as soon
5527 as they run "make clean". Fix for bug 7143; bugfix on 0.2.4.1-alpha.
5528 - Build Tor correctly on 32-bit platforms where the compiler can build
5529 but not run code using the "uint128_t" construction. Fixes bug 8587;
5530 bugfix on 0.2.4.8-alpha.
5531 - Fix compilation warning with some versions of clang that would
5532 prefer the -Wswitch-enum compiler flag to warn about switch
5533 statements with missing enum values, even if those switch
5534 statements have a "default:" statement. Fixes bug 8598; bugfix
5537 o Minor bugfixes (protocol):
5538 - Fix the handling of a TRUNCATE cell when it arrives while the
5539 circuit extension is in progress. Fixes bug 7947; bugfix on 0.0.7.1.
5540 - Fix a misframing issue when reading the version numbers in a
5541 VERSIONS cell. Previously we would recognize [00 01 00 02] as
5542 'version 1, version 2, and version 0x100', when it should have
5543 only included versions 1 and 2. Fixes bug 8059; bugfix on
5544 0.2.0.10-alpha. Reported pseudonymously.
5545 - Make the format and order of STREAM events for DNS lookups
5546 consistent among the various ways to launch DNS lookups. Fixes
5547 bug 8203; bugfix on 0.2.0.24-rc. Patch by "Desoxy."
5548 - Correct our check for which versions of Tor support the EXTEND2
5549 cell. We had been willing to send it to Tor 0.2.4.7-alpha and
5550 later, when support was really added in version 0.2.4.8-alpha.
5551 Fixes bug 8464; bugfix on 0.2.4.8-alpha.
5553 o Minor bugfixes (other):
5554 - Correctly store microdescriptors and extrainfo descriptors with
5555 an internal NUL byte. Fixes bug 8037; bugfix on 0.2.0.1-alpha.
5556 Bug reported by "cypherpunks".
5557 - Increase the width of the field used to remember a connection's
5558 link protocol version to two bytes. Harmless for now, since the
5559 only currently recognized versions are one byte long. Reported
5560 pseudonymously. Fixes bug 8062; bugfix on 0.2.0.10-alpha.
5561 - If the state file's path bias counts are invalid (presumably from a
5562 buggy Tor prior to 0.2.4.10-alpha), make them correct. Also add
5563 additional checks and log messages to the scaling of Path Bias
5564 counts, in case there still are remaining issues with scaling.
5565 Should help resolve bug 8235.
5566 - Eliminate several instances where we use "Nickname=ID" to refer to
5567 nodes in logs. Use "Nickname (ID)" instead. (Elsewhere, we still use
5568 "$ID=Nickname", which is also acceptable.) Fixes bug 7065. Bugfix
5569 on 0.2.3.21-rc, 0.2.4.5-alpha, 0.2.4.8-alpha, and 0.2.4.10-alpha.
5571 o Minor bugfixes (syscalls):
5572 - Always check the return values of functions fcntl() and
5573 setsockopt(). We don't believe these are ever actually failing in
5574 practice, but better safe than sorry. Also, checking these return
5575 values should please analysis tools like Coverity. Patch from
5576 'flupzor'. Fixes bug 8206; bugfix on all versions of Tor.
5577 - Use direct writes rather than stdio when building microdescriptor
5578 caches, in an attempt to mitigate bug 8031, or at least make it
5581 o Minor bugfixes (config):
5582 - When rejecting a configuration because we were unable to parse a
5583 quoted string, log an actual error message. Fixes bug 7950; bugfix
5585 - Behave correctly when the user disables LearnCircuitBuildTimeout
5586 but doesn't tell us what they would like the timeout to be. Fixes
5587 bug 6304; bugfix on 0.2.2.14-alpha.
5588 - When autodetecting the number of CPUs, use the number of available
5589 CPUs in preference to the number of configured CPUs. Inform the
5590 user if this reduces the number of available CPUs. Fixes bug 8002;
5591 bugfix on 0.2.3.1-alpha.
5592 - Make it an error when you set EntryNodes but disable UseGuardNodes,
5593 since it will (surprisingly to some users) ignore EntryNodes. Fixes
5594 bug 8180; bugfix on 0.2.3.11-alpha.
5595 - Allow TestingTorNetworks to override the 4096-byte minimum for
5596 the Fast threshold. Otherwise they can't bootstrap until they've
5597 observed more traffic. Fixes bug 8508; bugfix on 0.2.4.10-alpha.
5598 - Fix some logic errors when the user manually overrides the
5599 PathsNeededToBuildCircuits option in torrc. Fixes bug 8599; bugfix
5602 o Minor bugfixes (log messages to help diagnose bugs):
5603 - If we fail to free a microdescriptor because of bug 7164, log
5604 the filename and line number from which we tried to free it.
5605 - Add another diagnostic to the heartbeat message: track and log
5606 overhead that TLS is adding to the data we write. If this is
5607 high, we are sending too little data to SSL_write at a time.
5608 Diagnostic for bug 7707.
5609 - Add more detail to a log message about relaxed timeouts, to help
5611 - Warn more aggressively when flushing microdescriptors to a
5612 microdescriptor cache fails, in an attempt to mitigate bug 8031,
5613 or at least make it more diagnosable.
5614 - Improve debugging output to help track down bug 8185 ("Bug:
5615 outgoing relay cell has n_chan==NULL. Dropping.")
5616 - Log the purpose of a path-bias testing circuit correctly.
5617 Improves a log message from bug 8477; bugfix on 0.2.4.8-alpha.
5619 o Minor bugfixes (0.2.4.x log messages that were too noisy):
5620 - Don't attempt to relax the timeout of already opened 1-hop circuits.
5621 They might never timeout. This should eliminate some/all cases of
5622 the relaxed timeout log message.
5623 - Use circuit creation time for network liveness evaluation. This
5624 should eliminate warning log messages about liveness caused
5625 by changes in timeout evaluation. Fixes bug 6572; bugfix on
5627 - Reduce a path bias length check from notice to info. The message
5628 is triggered when creating controller circuits. Fixes bug 8196;
5629 bugfix on 0.2.4.8-alpha.
5630 - Fix a path state issue that triggered a notice during relay startup.
5631 Fixes bug 8320; bugfix on 0.2.4.10-alpha.
5632 - Reduce occurrences of warns about circuit purpose in
5633 connection_ap_expire_building(). Fixes bug 8477; bugfix on
5636 o Minor bugfixes (pre-0.2.4.x log messages that were too noisy):
5637 - If we encounter a write failure on a SOCKS connection before we
5638 finish our SOCKS handshake, don't warn that we closed the
5639 connection before we could send a SOCKS reply. Fixes bug 8427;
5640 bugfix on 0.1.0.1-rc.
5641 - Correctly recognize that [::1] is a loopback address. Fixes
5642 bug 8377; bugfix on 0.2.1.3-alpha.
5643 - Fix a directory authority warn caused when we have a large amount
5644 of badexit bandwidth. Fixes bug 8419; bugfix on 0.2.2.10-alpha.
5645 - Don't log inappropriate heartbeat messages when hibernating: a
5646 hibernating node is _expected_ to drop out of the consensus,
5647 decide it isn't bootstrapped, and so forth. Fixes bug 7302;
5648 bugfix on 0.2.3.1-alpha.
5649 - Don't complain about bootstrapping problems while hibernating.
5650 These complaints reflect a general code problem, but not one
5651 with any problematic effects (no connections are actually
5652 opened). Fixes part of bug 7302; bugfix on 0.2.3.2-alpha.
5654 o Documentation fixes:
5655 - Update tor-fw-helper.1.txt and tor-fw-helper.c to make option
5656 names match. Fixes bug 7768.
5657 - Make the torify manpage no longer refer to tsocks; torify hasn't
5658 supported tsocks since 0.2.3.14-alpha.
5659 - Make the tor manpage no longer reference tsocks.
5660 - Fix the GeoIPExcludeUnknown documentation to refer to
5661 ExcludeExitNodes rather than the currently nonexistent
5662 ExcludeEntryNodes. Spotted by "hamahangi" on tor-talk.
5665 - The tor-tsocks.conf is no longer distributed or installed. We
5666 recommend that tsocks users use torsocks instead. Resolves
5670 Changes in version 0.2.4.11-alpha - 2013-03-11
5671 Tor 0.2.4.11-alpha makes relay measurement by directory authorities
5672 more robust, makes hidden service authentication work again, and
5673 resolves a DPI fingerprint for Tor's SSL transport.
5675 o Major features (directory authorities):
5676 - Directory authorities now support a new consensus method (17)
5677 where they cap the published bandwidth of servers for which
5678 insufficient bandwidth measurements exist. Fixes part of bug 2286.
5679 - Directory authorities that set "DisableV2DirectoryInfo_ 1" no longer
5680 serve any v2 directory information. Now we can test disabling the
5681 old deprecated v2 directory format, and see whether doing so has
5682 any effect on network load. Begins to fix bug 6783.
5683 - Directory authorities now include inside each vote a statement of
5684 the performance thresholds they used when assigning flags.
5685 Implements ticket 8151.
5687 o Major bugfixes (directory authorities):
5688 - Stop marking every relay as having been down for one hour every
5689 time we restart a directory authority. These artificial downtimes
5690 were messing with our Stable and Guard flag calculations. Fixes
5691 bug 8218 (introduced by the fix for 1035). Bugfix on 0.2.2.23-alpha.
5693 o Major bugfixes (hidden services):
5694 - Allow hidden service authentication to succeed again. When we
5695 refactored the hidden service introduction code back
5696 in 0.2.4.1-alpha, we didn't update the code that checks
5697 whether authentication information is present, causing all
5698 authentication checks to return "false". Fix for bug 8207; bugfix
5699 on 0.2.4.1-alpha. Found by Coverity; this is CID 718615.
5701 o Minor features (relays, bridges):
5702 - Make bridge relays check once a minute for whether their IP
5703 address has changed, rather than only every 15 minutes. Resolves
5705 - Refactor resolve_my_address() so it returns the method by which we
5706 decided our public IP address (explicitly configured, resolved from
5707 explicit hostname, guessed from interfaces, learned by gethostname).
5708 Now we can provide more helpful log messages when a relay guesses
5709 its IP address incorrectly (e.g. due to unexpected lines in
5710 /etc/hosts). Resolves ticket 2267.
5711 - Teach bridge-using clients to avoid 0.2.2 bridges when making
5712 microdescriptor-related dir requests, and only fall back to normal
5713 descriptors if none of their bridges can handle microdescriptors
5714 (as opposed to the fix in ticket 4013, which caused them to fall
5715 back to normal descriptors if *any* of their bridges preferred
5716 them). Resolves ticket 4994.
5717 - Randomize the lifetime of our SSL link certificate, so censors can't
5718 use the static value for filtering Tor flows. Resolves ticket 8443;
5719 related to ticket 4014 which was included in 0.2.2.33.
5720 - Support a new version of the link protocol that allows 4-byte circuit
5721 IDs. Previously, circuit IDs were limited to 2 bytes, which presented
5722 a possible resource exhaustion issue. Closes ticket 7351; implements
5725 o Minor features (portability):
5726 - Tweak the curve25519-donna*.c implementations to tolerate systems
5727 that lack stdint.h. Fixes bug 3894; bugfix on 0.2.4.8-alpha.
5728 - Use Ville Laurikari's implementation of AX_CHECK_SIGN() to determine
5729 the signs of types during autoconf. This is better than our old
5730 approach, which didn't work when cross-compiling.
5731 - Detect the sign of enum values, rather than assuming that MSC is the
5732 only compiler where enum types are all signed. Fixes bug 7727;
5733 bugfix on 0.2.4.10-alpha.
5735 o Minor features (other):
5736 - Say "KBytes" rather than "KB" in the man page (for various values
5737 of K), to further reduce confusion about whether Tor counts in
5738 units of memory or fractions of units of memory. Resolves ticket 7054.
5739 - Clear the high bit on curve25519 public keys before passing them to
5740 our backend, in case we ever wind up using a backend that doesn't do
5741 so itself. If we used such a backend, and *didn't* clear the high bit,
5742 we could wind up in a situation where users with such backends would
5743 be distinguishable from users without. Fixes bug 8121; bugfix on
5745 - Update to the March 6 2013 Maxmind GeoLite Country database.
5747 o Minor bugfixes (clients):
5748 - When we receive a RELAY_END cell with the reason DONE, or with no
5749 reason, before receiving a RELAY_CONNECTED cell, report the SOCKS
5750 status as "connection refused". Previously we reported these cases
5751 as success but then immediately closed the connection. Fixes bug
5752 7902; bugfix on 0.1.0.1-rc. Reported by "oftc_must_be_destroyed".
5753 - Downgrade an assertion in connection_ap_expire_beginning to an
5754 LD_BUG message. The fix for bug 8024 should prevent this message
5755 from displaying, but just in case, a warn that we can diagnose
5756 is better than more assert crashes. Fixes bug 8065; bugfix on
5758 - Lower path use bias thresholds to .80 for notice and .60 for warn.
5759 Also make the rate limiting flags for the path use bias log messages
5760 independent from the original path bias flags. Fixes bug 8161;
5761 bugfix on 0.2.4.10-alpha.
5763 o Minor bugfixes (relays):
5764 - Stop trying to resolve our hostname so often (e.g. every time we
5765 think about doing a directory fetch). Now we reuse the cached
5766 answer in some cases. Fixes bugs 1992 (bugfix on 0.2.0.20-rc)
5767 and 2410 (bugfix on 0.1.2.2-alpha).
5768 - Stop sending a stray "(null)" in some cases for the server status
5769 "EXTERNAL_ADDRESS" controller event. Resolves bug 8200; bugfix
5771 - When choosing which stream on a formerly stalled circuit to wake
5772 first, make better use of the platform's weak RNG. Previously,
5773 we had been using the % ("modulo") operator to try to generate a
5774 1/N chance of picking each stream, but this behaves badly with
5775 many platforms' choice of weak RNG. Fixes bug 7801; bugfix on
5777 - Use our own weak RNG when we need a weak RNG. Windows's rand() and
5778 Irix's random() only return 15 bits; Solaris's random() returns more
5779 bits but its RAND_MAX says it only returns 15, and so on. Motivated
5780 by the fix for bug 7801; bugfix on 0.2.2.20-alpha.
5782 o Minor bugfixes (directory authorities):
5783 - Directory authorities now use less space when formatting identical
5784 microdescriptor lines in directory votes. Fixes bug 8158; bugfix
5787 o Minor bugfixes (memory leaks spotted by Coverity -- bug 7816):
5788 - Avoid leaking memory if we fail to compute a consensus signature
5789 or we generate a consensus we can't parse. Bugfix on 0.2.0.5-alpha.
5790 - Fix a memory leak when receiving headers from an HTTPS proxy. Bugfix
5792 - Fix a memory leak during safe-cookie controller authentication.
5793 Bugfix on 0.2.3.13-alpha.
5794 - Avoid memory leak of IPv6 policy content if we fail to format it into
5795 a router descriptor. Bugfix on 0.2.4.7-alpha.
5797 o Minor bugfixes (other code correctness issues):
5798 - Avoid a crash if we fail to generate an extrainfo descriptor.
5799 Fixes bug 8208; bugfix on 0.2.3.16-alpha. Found by Coverity;
5801 - When detecting the largest possible file descriptor (in order to
5802 close all file descriptors when launching a new program), actually
5803 use _SC_OPEN_MAX. The old code for doing this was very, very broken.
5804 Fixes bug 8209; bugfix on 0.2.3.1-alpha. Found by Coverity; this
5806 - Fix a copy-and-paste error when adding a missing A1 to a routerset
5807 because of GeoIPExcludeUnknown. Fix for Coverity CID 980650.
5808 Bugfix on 0.2.4.10-alpha.
5809 - Fix an impossible-to-trigger integer overflow when estimating how
5810 long our onionskin queue would take. (This overflow would require us
5811 to accept 4 million onionskins before processing 100 of them.) Fixes
5812 bug 8210; bugfix on 0.2.4.10-alpha.
5814 o Code simplification and refactoring:
5815 - Add a wrapper function for the common "log a message with a
5819 Changes in version 0.2.4.10-alpha - 2013-02-04
5820 Tor 0.2.4.10-alpha adds defenses at the directory authority level from
5821 certain attacks that flood the network with relays; changes the queue
5822 for circuit create requests from a sized-based limit to a time-based
5823 limit; resumes building with MSVC on Windows; and fixes a wide variety
5826 o Major bugfixes (directory authority):
5827 - When computing directory thresholds, ignore any rejected-as-sybil
5828 nodes during the computation so that they can't influence Fast,
5829 Guard, etc. (We should have done this for proposal 109.) Fixes
5831 - When marking a node as a likely sybil, reset its uptime metrics
5832 to zero, so that it cannot time towards getting marked as Guard,
5833 Stable, or HSDir. (We should have done this for proposal 109.) Fixes
5837 - When a TLS write is partially successful but incomplete, remember
5838 that the flushed part has been flushed, and notice that bytes were
5839 actually written. Reported and fixed pseudonymously. Fixes bug
5840 7708; bugfix on Tor 0.1.0.5-rc.
5841 - Reject bogus create and relay cells with 0 circuit ID or 0 stream
5842 ID: these could be used to create unexpected streams and circuits
5843 which would count as "present" to some parts of Tor but "absent"
5844 to others, leading to zombie circuits and streams or to a bandwidth
5845 denial-of-service. Fixes bug 7889; bugfix on every released version
5846 of Tor. Reported by "oftc_must_be_destroyed".
5847 - Rename all macros in our local copy of queue.h to begin with "TOR_".
5848 This change seems the only good way to permanently prevent conflicts
5849 with queue.h on various operating systems. Fixes bug 8107; bugfix
5852 o Major features (relay):
5853 - Instead of limiting the number of queued onionskins (aka circuit
5854 create requests) to a fixed, hard-to-configure number, we limit
5855 the size of the queue based on how many we expect to be able to
5856 process in a given amount of time. We estimate the time it will
5857 take to process an onionskin based on average processing time
5858 of previous onionskins. Closes ticket 7291. You'll never have to
5859 configure MaxOnionsPending again.
5861 o Major features (portability):
5862 - Resume building correctly with MSVC and Makefile.nmake. This patch
5863 resolves numerous bugs and fixes reported by ultramage, including
5864 7305, 7308, 7309, 7310, 7312, 7313, 7315, 7316, and 7669.
5865 - Make the ntor and curve25519 code build correctly with MSVC.
5866 Fix on 0.2.4.8-alpha.
5869 - When directory authorities are computing thresholds for flags,
5870 never let the threshold for the Fast flag fall below 4096
5871 bytes. Also, do not consider nodes with extremely low bandwidths
5872 when deciding thresholds for various directory flags. This change
5873 should raise our threshold for Fast relays, possibly in turn
5874 improving overall network performance; see ticket 1854. Resolves
5876 - The Tor client now ignores sub-domain components of a .onion
5877 address. This change makes HTTP "virtual" hosting
5878 possible: http://foo.aaaaaaaaaaaaaaaa.onion/ and
5879 http://bar.aaaaaaaaaaaaaaaa.onion/ can be two different websites
5880 hosted on the same hidden service. Implements proposal 204.
5881 - We compute the overhead from passing onionskins back and forth to
5882 cpuworkers, and report it when dumping statistics in response to
5883 SIGUSR1. Supports ticket 7291.
5885 o Minor features (path selection):
5886 - When deciding whether we have enough descriptors to build circuits,
5887 instead of looking at raw relay counts, look at which fraction
5888 of (bandwidth-weighted) paths we're able to build. This approach
5889 keeps clients from building circuits if their paths are likely to
5890 stand out statistically. The default fraction of paths needed is
5891 taken from the consensus directory; you can override it with the
5892 new PathsNeededToBuildCircuits option. Fixes ticket 5956.
5893 - When any country code is listed in ExcludeNodes or ExcludeExitNodes,
5894 and we have GeoIP information, also exclude all nodes with unknown
5895 countries "??" and "A1". This behavior is controlled by the
5896 new GeoIPExcludeUnknown option: you can make such nodes always
5897 excluded with "GeoIPExcludeUnknown 1", and disable the feature
5898 with "GeoIPExcludeUnknown 0". Setting "GeoIPExcludeUnknown auto"
5899 gets you the default behavior. Implements feature 7706.
5900 - Path Use Bias: Perform separate accounting for successful circuit
5901 use. Keep separate statistics on stream attempt rates versus stream
5902 success rates for each guard. Provide configurable thresholds to
5903 determine when to emit log messages or disable use of guards that
5904 fail too many stream attempts. Resolves ticket 7802.
5906 o Minor features (log messages):
5907 - When learning a fingerprint for a bridge, log its corresponding
5908 transport type. Implements ticket 7896.
5909 - Improve the log message when "Bug/attack: unexpected sendme cell
5910 from client" occurs, to help us track bug 8093.
5913 - Remove a couple of extraneous semicolons that were upsetting the
5914 cparser library. Patch by Christian Grothoff. Fixes bug 7115;
5915 bugfix on 0.2.2.1-alpha.
5916 - Remove a source of rounding error during path bias count scaling;
5917 don't count cannibalized circuits as used for path bias until we
5918 actually try to use them; and fix a circuit_package_relay_cell()
5919 warning message about n_chan==NULL. Fixes bug 7802.
5920 - Detect nacl when its headers are in a nacl/ subdirectory. Also,
5921 actually link against nacl when we're configured to use it. Fixes
5922 bug 7972; bugfix on 0.2.4.8-alpha.
5923 - Compile correctly with the --disable-curve25519 option. Fixes
5924 bug 8153; bugfix on 0.2.4.8-alpha.
5926 o Build improvements:
5927 - Do not report status verbosely from autogen.sh unless the -v flag
5928 is specified. Fixes issue 4664. Patch from Onizuka.
5929 - Replace all calls to snprintf() outside of src/ext with
5930 tor_snprintf(). Also remove the #define to replace snprintf with
5931 _snprintf on Windows; they have different semantics, and all of
5932 our callers should be using tor_snprintf() anyway. Fixes bug 7304.
5933 - Try to detect if we are ever building on a platform where
5934 memset(...,0,...) does not set the value of a double to 0.0. Such
5935 platforms are permitted by the C standard, though in practice
5936 they're pretty rare (since IEEE 754 is nigh-ubiquitous). We don't
5937 currently support them, but it's better to detect them and fail
5938 than to perform erroneously.
5941 - Stop exporting estimates of v2 and v3 directory traffic shares
5942 in extrainfo documents. They were unneeded and sometimes inaccurate.
5943 Also stop exporting any v2 directory request statistics. Resolves
5945 - Drop support for detecting and warning about versions of Libevent
5946 before 1.3e. Nothing reasonable ships with them any longer;
5947 warning the user about them shouldn't be needed. Resolves ticket
5950 o Code simplifications and refactoring:
5951 - Rename "isin" functions to "contains", for grammar. Resolves
5953 - Rename Tor's logging function log() to tor_log(), to avoid conflicts
5954 with the natural logarithm function from the system libm. Resolves
5958 Changes in version 0.2.4.9-alpha - 2013-01-15
5959 Tor 0.2.4.9-alpha provides a quick fix to make the new ntor handshake
5963 - Fix backward compatibility logic when receiving an embedded ntor
5964 handshake tunneled in a CREATE cell. This clears up the "Bug:
5965 couldn't format CREATED cell" warning. Fixes bug 7959; bugfix
5969 Changes in version 0.2.4.8-alpha - 2013-01-14
5970 Tor 0.2.4.8-alpha introduces directory guards to reduce user enumeration
5971 risks, adds a new stronger and faster circuit handshake, and offers
5972 stronger and faster link encryption when both sides support it.
5975 - Preliminary support for directory guards (proposal 207): when
5976 possible, clients now use their entry guards for non-anonymous
5977 directory requests. This can help prevent client enumeration. Note
5978 that this behavior only works when we have a usable consensus
5979 directory, and when options about what to download are more or less
5980 standard. In the future we should re-bootstrap from our guards,
5981 rather than re-bootstrapping from the preconfigured list of
5982 directory sources that ships with Tor. Resolves ticket 6526.
5983 - Tor relays and clients now support a better CREATE/EXTEND cell
5984 format, allowing the sender to specify multiple address, identity,
5985 and handshake types. Implements Robert Ransom's proposal 200;
5988 o Major features (new circuit handshake):
5989 - Tor now supports a new circuit extension handshake designed by Ian
5990 Goldberg, Douglas Stebila, and Berkant Ustaoglu. Our original
5991 circuit extension handshake, later called "TAP", was a bit slow
5992 (especially on the relay side), had a fragile security proof, and
5993 used weaker keys than we'd now prefer. The new circuit handshake
5994 uses Dan Bernstein's "curve25519" elliptic-curve Diffie-Hellman
5995 function, making it significantly more secure than the older
5996 handshake, and significantly faster. Tor can use one of two built-in
5997 pure-C curve25519-donna implementations by Adam Langley, or it
5998 can link against the "nacl" library for a tuned version if present.
6000 The built-in version is very fast for 64-bit systems when building
6001 with GCC. The built-in 32-bit version is still faster than the
6002 old TAP protocol, but using libnacl is better on most such hosts.
6004 Clients don't currently use this protocol by default, since
6005 comparatively few clients support it so far. To try it, set
6006 UseNTorHandshake to 1.
6008 Implements proposal 216; closes ticket 7202.
6010 o Major features (better link encryption):
6011 - Relays can now enable the ECDHE TLS ciphersuites when available
6012 and appropriate. These ciphersuites let us negotiate forward-secure
6013 TLS secret keys more safely and more efficiently than with our
6014 previous use of Diffie-Hellman modulo a 1024-bit prime. By default,
6015 public relays prefer the (faster) P224 group, and bridges prefer
6016 the (more common) P256 group; you can override this with the
6019 Enabling these ciphers was a little tricky, since for a long time,
6020 clients had been claiming to support them without actually doing
6021 so, in order to foil fingerprinting. But with the client-side
6022 implementation of proposal 198 in 0.2.3.17-beta, clients can now
6023 match the ciphers from recent Firefox versions *and* list the
6024 ciphers they actually mean, so relays can believe such clients
6025 when they advertise ECDHE support in their TLS ClientHello messages.
6027 This feature requires clients running 0.2.3.17-beta or later,
6028 and requires both sides to be running OpenSSL 1.0.0 or later
6029 with ECC support. OpenSSL 1.0.1, with the compile-time option
6030 "enable-ec_nistp_64_gcc_128", is highly recommended.
6032 Implements the relay side of proposal 198; closes ticket 7200.
6035 - Avoid crashing when, as a relay without IPv6-exit support, a
6036 client insists on getting an IPv6 address or nothing. Fixes bug
6037 7814; bugfix on 0.2.4.7-alpha.
6040 - Improve circuit build timeout handling for hidden services.
6041 In particular: adjust build timeouts more accurately depending
6042 upon the number of hop-RTTs that a particular circuit type
6043 undergoes. Additionally, launch intro circuits in parallel
6044 if they timeout, and take the first one to reply as valid.
6045 - Work correctly on Unix systems where EAGAIN and EWOULDBLOCK are
6046 separate error codes; or at least, don't break for that reason.
6047 Fixes bug 7935. Reported by "oftc_must_be_destroyed".
6048 - Update to the January 2 2013 Maxmind GeoLite Country database.
6050 o Minor features (testing):
6051 - Add benchmarks for DH (1024-bit multiplicative group) and ECDH
6052 (P-256) Diffie-Hellman handshakes to src/or/bench.
6053 - Add benchmark functions to test onion handshake performance.
6055 o Minor features (path bias detection):
6056 - Alter the Path Bias log messages to be more descriptive in terms
6057 of reporting timeouts and other statistics.
6058 - Create three levels of Path Bias log messages, as opposed to just
6059 two. These are configurable via consensus as well as via the torrc
6060 options PathBiasNoticeRate, PathBiasWarnRate, PathBiasExtremeRate.
6061 The default values are 0.70, 0.50, and 0.30 respectively.
6062 - Separate the log message levels from the decision to drop guards,
6063 which also is available via torrc option PathBiasDropGuards.
6064 PathBiasDropGuards still defaults to 0 (off).
6065 - Deprecate PathBiasDisableRate in favor of PathBiasDropGuards
6066 in combination with PathBiasExtremeRate.
6067 - Increase the default values for PathBiasScaleThreshold and
6068 PathBiasCircThreshold from (200, 20) to (300, 150).
6069 - Add in circuit usage accounting to path bias. If we try to use a
6070 built circuit but fail for any reason, it counts as path bias.
6071 Certain classes of circuits where the adversary gets to pick your
6072 destination node are exempt from this accounting. Usage accounting
6073 can be specifically disabled via consensus parameter or torrc.
6074 - Convert all internal path bias state to double-precision floating
6075 point, to avoid roundoff error and other issues.
6076 - Only record path bias information for circuits that have completed
6077 *two* hops. Assuming end-to-end tagging is the attack vector, this
6078 makes us more resilient to ambient circuit failure without any
6079 detection capability loss.
6081 o Minor bugfixes (log messages):
6082 - Rate-limit the "No circuits are opened. Relaxed timeout for a
6083 circuit with channel state open..." message to once per hour to
6084 keep it from filling the notice logs. Mitigates bug 7799 but does
6085 not fix the underlying cause. Bugfix on 0.2.4.7-alpha.
6086 - Avoid spurious warnings when configuring multiple client ports of
6087 which only some are nonlocal. Previously, we had claimed that some
6088 were nonlocal when in fact they weren't. Fixes bug 7836; bugfix on
6091 o Code simplifications and refactoring:
6092 - Get rid of a couple of harmless clang warnings, where we compared
6093 enums to ints. These warnings are newly introduced in clang 3.2.
6094 - Split the onion.c file into separate modules for the onion queue
6095 and the different handshakes it supports.
6096 - Remove the marshalling/unmarshalling code for sending requests to
6097 cpuworkers over a socket, and instead just send structs. The
6098 recipient will always be the same Tor binary as the sender, so
6099 any encoding is overkill.
6102 Changes in version 0.2.4.7-alpha - 2012-12-24
6103 Tor 0.2.4.7-alpha introduces a new approach to providing fallback
6104 directory mirrors for more robust bootstrapping; fixes more issues where
6105 clients with changing network conditions refuse to make any circuits;
6106 adds initial support for exiting to IPv6 addresses; resumes being able
6107 to update our GeoIP database, and includes the geoip6 file this time;
6108 turns off the client-side DNS cache by default due to privacy risks;
6109 and fixes a variety of other issues.
6111 o Major features (client resilience):
6112 - Add a new "FallbackDir" torrc option to use when we can't use
6113 a directory mirror from the consensus (either because we lack a
6114 consensus, or because they're all down). Currently, all authorities
6115 are fallbacks by default, and there are no other default fallbacks,
6116 but that will change. This option will allow us to give clients a
6117 longer list of servers to try to get a consensus from when first
6118 connecting to the Tor network, and thereby reduce load on the
6119 directory authorities. Implements proposal 206, "Preconfigured
6120 directory sources for bootstrapping". We also removed the old
6121 "FallbackNetworkstatus" option, since we never got it working well
6122 enough to use it. Closes bug 572.
6123 - If we have no circuits open, use a relaxed timeout (the
6124 95-percentile cutoff) until a circuit succeeds. This heuristic
6125 should allow Tor to succeed at building circuits even when the
6126 network connection drastically changes. Should help with bug 3443.
6128 o Major features (IPv6):
6129 - Relays can now exit to IPv6 addresses: make sure that you have IPv6
6130 connectivity, then set the IPv6Exit flag to 1. Also make sure your
6131 exit policy reads as you would like: the address * applies to all
6132 address families, whereas *4 is IPv4 address only, and *6 is IPv6
6133 addresses only. On the client side, you'll need to wait until the
6134 authorities have upgraded, wait for enough exits to support IPv6,
6135 apply the "IPv6Traffic" flag to a SocksPort, and use Socks5. Closes
6136 ticket 5547, implements proposal 117 as revised in proposal 208.
6138 We DO NOT recommend that clients with actual anonymity needs start
6139 using IPv6 over Tor yet, since not enough exits support it yet.
6141 o Major features (geoip database):
6142 - Maxmind began labelling Tor relays as being in country "A1",
6143 which breaks by-country node selection inside Tor. Now we use a
6144 script to replace "A1" ("Anonymous Proxy") entries in our geoip
6145 file with real country codes. This script fixes about 90% of "A1"
6146 entries automatically and uses manual country code assignments to
6147 fix the remaining 10%. See src/config/README.geoip for details.
6148 Fixes bug 6266. Also update to the December 5 2012 Maxmind GeoLite
6149 Country database, as modified above.
6151 o Major bugfixes (client-side DNS):
6152 - Turn off the client-side DNS cache by default. Updating and using
6153 the DNS cache is now configurable on a per-client-port
6154 level. SOCKSPort, DNSPort, etc lines may now contain
6155 {No,}Cache{IPv4,IPv6,}DNS lines to indicate that we shouldn't
6156 cache these types of DNS answers when we receive them from an
6157 exit node in response to an application request on this port, and
6158 {No,}UseCached{IPv4,IPv6,DNS} lines to indicate that if we have
6159 cached DNS answers of these types, we shouldn't use them. It's
6160 potentially risky to use cached DNS answers at the client, since
6161 doing so can indicate to one exit what answers we've gotten
6162 for DNS lookups in the past. With IPv6, this becomes especially
6163 problematic. Using cached DNS answers for requests on the same
6164 circuit would present less linkability risk, since all traffic
6165 on a circuit is already linkable, but it would also provide
6166 little performance benefit: the exit node caches DNS replies
6167 too. Implements a simplified version of Proposal 205. Implements
6170 o Major bugfixes (other):
6171 - Alter circuit build timeout measurement to start at the point
6172 where we begin the CREATE/CREATE_FAST step (as opposed to circuit
6173 initialization). This should make our timeout measurements more
6174 uniform. Previously, we were sometimes including ORconn setup time
6175 in our circuit build time measurements. Should resolve bug 3443.
6176 - Fix an assertion that could trigger in hibernate_go_dormant() when
6177 closing an or_connection_t: call channel_mark_for_close() rather
6178 than connection_mark_for_close(). Fixes bug 7267. Bugfix on
6180 - Include the geoip6 IPv6 GeoIP database in the tarball. Fixes bug
6181 7655; bugfix on 0.2.4.6-alpha.
6184 - Add a new torrc option "ServerTransportListenAddr" to let bridge
6185 operators select the address where their pluggable transports will
6186 listen for connections. Resolves ticket 7013.
6187 - Allow an optional $ before the node identity digest in the
6188 controller command GETINFO ns/id/<identity>, for consistency with
6189 md/id/<identity> and desc/id/<identity>. Resolves ticket 7059.
6190 - Log packaged cell fullness as part of the heartbeat message.
6191 Diagnosis to try to determine the extent of bug 7743.
6193 o Minor features (IPv6):
6194 - AutomapHostsOnResolve now supports IPv6 addresses. By default, we
6195 prefer to hand out virtual IPv6 addresses, since there are more of
6196 them and we can't run out. To override this behavior and make IPv4
6197 addresses preferred, set NoPreferIPv6Automap on whatever SOCKSPort
6198 or DNSPort you're using for resolving. Implements ticket 7571.
6199 - AutomapHostsOnResolve responses are now randomized, to avoid
6200 annoying situations where Tor is restarted and applications
6201 connect to the wrong addresses.
6202 - Never try more than 1000 times to pick a new virtual address when
6203 AutomapHostsOnResolve is set. That's good enough so long as we
6204 aren't close to handing out our entire virtual address space;
6205 if you're getting there, it's best to switch to IPv6 virtual
6209 - The ADDRMAP command can no longer generate an ill-formed error
6210 code on a failed MAPADDRESS. It now says "internal" rather than
6211 an English sentence fragment with spaces in the middle. Bugfix on
6213 - Fix log messages and comments to avoid saying "GMT" when we mean
6214 "UTC". Fixes bug 6113.
6215 - Compile on win64 using mingw64. Fixes bug 7260; patches from
6217 - Fix a crash when debugging unit tests on Windows: deallocate a
6218 shared library with FreeLibrary, not CloseHandle. Fixes bug 7306;
6219 bugfix on 0.2.2.17-alpha. Reported by "ultramage".
6222 - The DirServer option is now DirAuthority, for consistency with
6223 current naming patterns. You can still use the old DirServer form.
6225 o Code simplification and refactoring:
6226 - Move the client-side address-map/virtual-address/DNS-cache code
6227 out of connection_edge.c into a new addressmap.c module.
6228 - Remove unused code for parsing v1 directories and "running routers"
6229 documents. Fixes bug 6887.
6232 Changes in version 0.2.3.25 - 2012-11-19
6233 The Tor 0.2.3 release series is dedicated to the memory of Len "rabbi"
6234 Sassaman (1980-2011), a long-time cypherpunk, anonymity researcher,
6235 Mixmaster maintainer, Pynchon Gate co-designer, CodeCon organizer,
6236 programmer, and friend. Unstinting in his dedication to the cause of
6237 freedom, he inspired and helped many of us as we began our work on
6238 anonymity, and inspires us still. Please honor his memory by writing
6239 software to protect people's freedoms, and by helping others to do so.
6241 Tor 0.2.3.25, the first stable release in the 0.2.3 branch, features
6242 significantly reduced directory overhead (via microdescriptors),
6243 enormous crypto performance improvements for fast relays on new
6244 enough hardware, a new v3 TLS handshake protocol that can better
6245 resist fingerprinting, support for protocol obfuscation plugins (aka
6246 pluggable transports), better scalability for hidden services, IPv6
6247 support for bridges, performance improvements like allowing clients
6248 to skip the first round-trip on the circuit ("optimistic data") and
6249 refilling token buckets more often, a new "stream isolation" design
6250 to isolate different applications on different circuits, and many
6251 stability, security, and privacy fixes.
6254 - Tor tries to wipe potentially sensitive data after using it, so
6255 that if some subsequent security failure exposes Tor's memory,
6256 the damage will be limited. But we had a bug where the compiler
6257 was eliminating these wipe operations when it decided that the
6258 memory was no longer visible to a (correctly running) program,
6259 hence defeating our attempt at defense in depth. We fix that
6260 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6261 is unlikely to optimize away. Future versions of Tor may use
6262 a less ridiculously heavy approach for this. Fixes bug 7352.
6263 Reported in an article by Andrey Karpov.
6266 - Fix a harmless bug when opting against publishing a relay descriptor
6267 because DisableNetwork is set. Fixes bug 7464; bugfix on
6271 Changes in version 0.2.4.6-alpha - 2012-11-13
6272 Tor 0.2.4.6-alpha fixes an assert bug that has been plaguing relays,
6273 makes our defense-in-depth memory wiping more reliable, and begins to
6274 count IPv6 addresses in bridge statistics,
6277 - Fix an assertion failure that could occur when closing a connection
6278 with a spliced rendezvous circuit. Fix for bug 7212; bugfix on
6280 - Tor tries to wipe potentially sensitive data after using it, so
6281 that if some subsequent security failure exposes Tor's memory,
6282 the damage will be limited. But we had a bug where the compiler
6283 was eliminating these wipe operations when it decided that the
6284 memory was no longer visible to a (correctly running) program,
6285 hence defeating our attempt at defense in depth. We fix that
6286 by using OpenSSL's OPENSSL_cleanse() operation, which a compiler
6287 is unlikely to optimize away. Future versions of Tor may use
6288 a less ridiculously heavy approach for this. Fixes bug 7352.
6289 Reported in an article by Andrey Karpov.
6292 - Add GeoIP database for IPv6 addresses. The new config option
6294 - Bridge statistics now count bridge clients connecting over IPv6:
6295 bridge statistics files now list "bridge-ip-versions" and
6296 extra-info documents list "geoip6-db-digest". The control protocol
6297 "CLIENTS_SEEN" and "ip-to-country" queries now support IPv6. Initial
6298 implementation by "shkoo", addressing ticket 5055.
6301 - Warn when we are binding low ports when hibernation is enabled;
6302 previously we had warned when we were _advertising_ low ports with
6303 hibernation enabled. Fixes bug 7285; bugfix on 0.2.3.9-alpha.
6304 - Fix a harmless bug when opting against publishing a relay descriptor
6305 because DisableNetwork is set. Fixes bug 7464; bugfix on
6307 - Add warning message when a managed proxy dies during configuration.
6308 Fixes bug 7195; bugfix on 0.2.4.2-alpha.
6309 - Fix a linking error when building tor-fw-helper without miniupnp.
6310 Fixes bug 7235; bugfix on 0.2.4.2-alpha. Fix by Anthony G. Basile.
6311 - Check for closing an or_connection_t without going through correct
6312 channel functions; emit a warning and then call
6313 connection_or_close_for_error() so we don't assert as in bugs 7212
6315 - Compile correctly on compilers without C99 designated initializer
6316 support. Fixes bug 7286; bugfix on 0.2.4.4-alpha.
6317 - Avoid a possible assert that can occur when channel_send_destroy() is
6318 called on a channel in CHANNEL_STATE_CLOSING, CHANNEL_STATE_CLOSED,
6319 or CHANNEL_STATE_ERROR when the Tor process is resumed after being
6320 blocked for a long interval. Fixes bug 7350; bugfix on 0.2.4.4-alpha.
6321 - Fix a memory leak on failing cases of channel_tls_process_certs_cell.
6322 Fixes bug 7422; bugfix on 0.2.4.4-alpha.
6324 o Code simplification and refactoring:
6325 - Start using OpenBSD's implementation of queue.h, so that we don't
6326 need to hand-roll our own pointer and list structures whenever we
6327 need them. (We can't rely on a sys/queue.h, since some operating
6328 systems don't have them, and the ones that do have them don't all
6329 present the same extensions.)
6332 Changes in version 0.2.4.5-alpha - 2012-10-25
6333 Tor 0.2.4.5-alpha comes hard at the heels of 0.2.4.4-alpha, to fix
6334 two important security vulnerabilities that could lead to remotely
6335 triggerable relay crashes, fix a major bug that was preventing clients
6336 from choosing suitable exit nodes, and refactor some of our code.
6338 o Major bugfixes (security, also in 0.2.3.24-rc):
6339 - Fix a group of remotely triggerable assertion failures related to
6340 incorrect link protocol negotiation. Found, diagnosed, and fixed
6341 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6343 - Fix a denial of service attack by which any directory authority
6344 could crash all the others, or by which a single v2 directory
6345 authority could crash everybody downloading v2 directory
6346 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6348 o Major bugfixes (also in 0.2.3.24-rc):
6349 - When parsing exit policy summaries from microdescriptors, we had
6350 previously been ignoring the last character in each one, so that
6351 "accept 80,443,8080" would be treated by clients as indicating
6352 a node that allows access to ports 80, 443, and 808. That would
6353 lead to clients attempting connections that could never work,
6354 and ignoring exit nodes that would support their connections. Now
6355 clients parse these exit policy summaries correctly. Fixes bug 7192;
6356 bugfix on 0.2.3.1-alpha.
6358 o Minor bugfixes (also in 0.2.3.24-rc):
6359 - Clients now consider the ClientRejectInternalAddresses config option
6360 when using a microdescriptor consensus stanza to decide whether
6361 an exit relay would allow exiting to an internal address. Fixes
6362 bug 7190; bugfix on 0.2.3.1-alpha.
6365 - Only disable TLS session ticket support when running as a TLS
6366 server. Now clients will blend better with regular Firefox
6367 connections. Fixes bug 7189; bugfix on Tor 0.2.3.23-rc.
6369 o Code simplification and refactoring:
6370 - Start using OpenBSD's implementation of queue.h (originally by
6372 - Move the entry node code from circuitbuild.c to its own file.
6373 - Move the circuit build timeout tracking code from circuitbuild.c
6377 Changes in version 0.2.3.24-rc - 2012-10-25
6378 Tor 0.2.3.24-rc fixes two important security vulnerabilities that
6379 could lead to remotely triggerable relay crashes, and fixes
6380 a major bug that was preventing clients from choosing suitable exit
6383 o Major bugfixes (security):
6384 - Fix a group of remotely triggerable assertion failures related to
6385 incorrect link protocol negotiation. Found, diagnosed, and fixed
6386 by "some guy from France". Fix for CVE-2012-2250; bugfix on
6388 - Fix a denial of service attack by which any directory authority
6389 could crash all the others, or by which a single v2 directory
6390 authority could crash everybody downloading v2 directory
6391 information. Fixes bug 7191; bugfix on 0.2.0.10-alpha.
6394 - When parsing exit policy summaries from microdescriptors, we had
6395 previously been ignoring the last character in each one, so that
6396 "accept 80,443,8080" would be treated by clients as indicating
6397 a node that allows access to ports 80, 443, and 808. That would
6398 lead to clients attempting connections that could never work,
6399 and ignoring exit nodes that would support their connections. Now
6400 clients parse these exit policy summaries correctly. Fixes bug 7192;
6401 bugfix on 0.2.3.1-alpha.
6404 - Clients now consider the ClientRejectInternalAddresses config option
6405 when using a microdescriptor consensus stanza to decide whether
6406 an exit relay would allow exiting to an internal address. Fixes
6407 bug 7190; bugfix on 0.2.3.1-alpha.
6410 Changes in version 0.2.4.4-alpha - 2012-10-20
6411 Tor 0.2.4.4-alpha adds a new v3 directory authority, fixes a privacy
6412 vulnerability introduced by a change in OpenSSL, fixes a remotely
6413 triggerable assert, and adds new channel_t and circuitmux_t abstractions
6414 that will make it easier to test new connection transport and cell
6415 scheduling algorithms.
6417 o New directory authorities (also in 0.2.3.23-rc):
6418 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6419 authority. Closes ticket 5749.
6421 o Major bugfixes (security/privacy, also in 0.2.3.23-rc):
6422 - Disable TLS session tickets. OpenSSL's implementation was giving
6423 our TLS session keys the lifetime of our TLS context objects, when
6424 perfect forward secrecy would want us to discard anything that
6425 could decrypt a link connection as soon as the link connection
6426 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6427 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6428 - Discard extraneous renegotiation attempts once the V3 link
6429 protocol has been initiated. Failure to do so left us open to
6430 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6431 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6433 o Internal abstraction features:
6434 - Introduce new channel_t abstraction between circuits and
6435 or_connection_t to allow for implementing alternate OR-to-OR
6436 transports. A channel_t is an abstract object which can either be a
6437 cell-bearing channel, which is responsible for authenticating and
6438 handshaking with the remote OR and transmitting cells to and from
6439 it, or a listening channel, which spawns new cell-bearing channels
6440 at the request of remote ORs. Implements part of ticket 6465.
6441 - Also new is the channel_tls_t subclass of channel_t, adapting it
6442 to the existing or_connection_t code. The V2/V3 protocol handshaking
6443 code which formerly resided in command.c has been moved below the
6444 channel_t abstraction layer and may be found in channeltls.c now.
6445 Implements the rest of ticket 6465.
6446 - Introduce new circuitmux_t storing the queue of circuits for
6447 a channel; this encapsulates and abstracts the queue logic and
6448 circuit selection policy, and allows the latter to be overridden
6449 easily by switching out a policy object. The existing EWMA behavior
6450 is now implemented as a circuitmux_policy_t. Resolves ticket 6816.
6452 o Required libraries:
6453 - Tor now requires OpenSSL 0.9.8 or later. OpenSSL 1.0.0 or later is
6454 strongly recommended.
6457 - Warn users who run hidden services on a Tor client with
6458 UseEntryGuards disabled that their hidden services will be
6459 vulnerable to http://freehaven.net/anonbib/#hs-attack06 (the
6460 attack which motivated Tor to support entry guards in the first
6461 place). Resolves ticket 6889.
6462 - Tor now builds correctly on Bitrig, an OpenBSD fork. Patch from
6463 dhill. Resolves ticket 6982.
6464 - Option OutboundBindAddress can be specified multiple times and
6465 accepts IPv6 addresses. Resolves ticket 6876.
6467 o Minor bugfixes (also in 0.2.3.23-rc):
6468 - Don't serve or accept v2 hidden service descriptors over a
6469 relay's DirPort. It's never correct to do so, and disabling it
6470 might make it more annoying to exploit any bugs that turn up in the
6471 descriptor-parsing code. Fixes bug 7149.
6472 - Fix two cases in src/or/transports.c where we were calling
6473 fmt_addr() twice in a parameter list. Bug found by David
6474 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6475 - Fix memory leaks whenever we logged any message about the "path
6476 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6477 - When relays refuse a "create" cell because their queue of pending
6478 create cells is too big (typically because their cpu can't keep up
6479 with the arrival rate), send back reason "resource limit" rather
6480 than reason "internal", so network measurement scripts can get a
6481 more accurate picture. Fixes bug 7037; bugfix on 0.1.1.11-alpha.
6484 - Command-line option "--version" implies "--quiet". Fixes bug 6997.
6485 - Free some more still-in-use memory at exit, to make hunting for
6486 memory leaks easier. Resolves bug 7029.
6487 - When a Tor client gets a "truncated" relay cell, the first byte of
6488 its payload specifies why the circuit was truncated. We were
6489 ignoring this 'reason' byte when tearing down the circuit, resulting
6490 in the controller not being told why the circuit closed. Now we
6491 pass the reason from the truncated cell to the controller. Bugfix
6492 on 0.1.2.3-alpha; fixes bug 7039.
6493 - Downgrade "Failed to hand off onionskin" messages to "debug"
6494 severity, since they're typically redundant with the "Your computer
6495 is too slow" messages. Fixes bug 7038; bugfix on 0.2.2.16-alpha.
6496 - Make clients running with IPv6 bridges connect over IPv6 again,
6497 even without setting new config options ClientUseIPv6 and
6498 ClientPreferIPv6ORPort. Fixes bug 6757; bugfix on 0.2.4.1-alpha.
6499 - Use square brackets around IPv6 addresses in numerous places
6500 that needed them, including log messages, HTTPS CONNECT proxy
6501 requests, TransportProxy statefile entries, and pluggable transport
6502 extra-info lines. Fixes bug 7011; patch by David Fifield.
6504 o Code refactoring and cleanup:
6505 - Source files taken from other packages now reside in src/ext;
6506 previously they were scattered around the rest of Tor.
6507 - Avoid use of reserved identifiers in our C code. The C standard
6508 doesn't like us declaring anything that starts with an
6509 underscore, so let's knock it off before we get in trouble. Fix
6510 for bug 1031; bugfix on the first Tor commit.
6513 Changes in version 0.2.3.23-rc - 2012-10-20
6514 Tor 0.2.3.23-rc adds a new v3 directory authority, fixes a privacy
6515 vulnerability introduced by a change in OpenSSL, and fixes a variety
6516 of smaller bugs in preparation for the release.
6518 o New directory authorities:
6519 - Add Faravahar (run by Sina Rabbani) as the ninth v3 directory
6520 authority. Closes ticket 5749.
6522 o Major bugfixes (security/privacy):
6523 - Disable TLS session tickets. OpenSSL's implementation was giving
6524 our TLS session keys the lifetime of our TLS context objects, when
6525 perfect forward secrecy would want us to discard anything that
6526 could decrypt a link connection as soon as the link connection
6527 was closed. Fixes bug 7139; bugfix on all versions of Tor linked
6528 against OpenSSL 1.0.0 or later. Found by Florent Daignière.
6529 - Discard extraneous renegotiation attempts once the V3 link
6530 protocol has been initiated. Failure to do so left us open to
6531 a remotely triggerable assertion failure. Fixes CVE-2012-2249;
6532 bugfix on 0.2.3.6-alpha. Reported by "some guy from France".
6535 - Fix a possible crash bug when checking for deactivated circuits
6536 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6537 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6539 o Minor bugfixes (on 0.2.3.x):
6540 - Fix two cases in src/or/transports.c where we were calling
6541 fmt_addr() twice in a parameter list. Bug found by David
6542 Fifield. Fixes bug 7014; bugfix on 0.2.3.9-alpha.
6543 - Convert an assert in the pathbias code to a log message. The assert
6544 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6545 bugfix on 0.2.3.17-beta.
6546 - Fix memory leaks whenever we logged any message about the "path
6547 bias" detection. Fixes bug 7022; bugfix on 0.2.3.21-rc.
6549 o Minor bugfixes (on 0.2.2.x and earlier):
6550 - Don't serve or accept v2 hidden service descriptors over a relay's
6551 DirPort. It's never correct to do so, and disabling it might
6552 make it more annoying to exploit any bugs that turn up in the
6553 descriptor-parsing code. Fixes bug 7149.
6554 - When relays refuse a "create" cell because their queue of pending
6555 create cells is too big (typically because their cpu can't keep up
6556 with the arrival rate), send back reason "resource limit" rather
6557 than reason "internal", so network measurement scripts can get a
6558 more accurate picture. Bugfix on 0.1.1.11-alpha; fixes bug 7037.
6559 - Correct file sizes when reading binary files on Cygwin, to avoid
6560 a bug where Tor would fail to read its state file. Fixes bug 6844;
6561 bugfix on 0.1.2.7-alpha.
6562 - Avoid undefined behavior when parsing the list of supported
6563 rendezvous/introduction protocols in a hidden service descriptor.
6564 Previously, Tor would have confused (as-yet-unused) protocol version
6565 numbers greater than 32 with lower ones on many platforms. Fixes
6566 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6568 o Documentation fixes:
6569 - Clarify that hidden services are TCP only. Fixes bug 6024.
6572 Changes in version 0.2.4.3-alpha - 2012-09-22
6573 Tor 0.2.4.3-alpha fixes another opportunity for a remotely triggerable
6574 assertion, resumes letting relays test reachability of their DirPort,
6575 and cleans up a bunch of smaller bugs.
6578 - Fix an assertion failure in tor_timegm() that could be triggered
6579 by a badly formatted directory object. Bug found by fuzzing with
6580 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6583 - Fix a possible crash bug when checking for deactivated circuits
6584 in connection_or_flush_from_first_active_circuit(). Fixes bug 6341;
6585 bugfix on 0.2.2.7-alpha. Bug report and fix received pseudonymously.
6586 - Allow routers to detect that their own DirPorts are running. When
6587 we removed support for versions_supports_begindir, we also
6588 accidentally removed the mechanism we used to self-test our
6589 DirPort. Diagnosed with help from kargig. Fixes bugs 6814 and 6815;
6590 bugfix on 0.2.4.2-alpha.
6592 o Security features:
6593 - Switch to a completely time-invariant approach for picking nodes
6594 weighted by bandwidth. Our old approach would run through the
6595 part of the loop after it had made its choice slightly slower
6596 than it ran through the part of the loop before it had made its
6597 choice. Addresses ticket 6538.
6598 - Disable the use of Guard nodes when in Tor2WebMode. Guard usage
6599 by tor2web clients allows hidden services to identify tor2web
6600 clients through their repeated selection of the same rendezvous
6601 and introduction point circuit endpoints (their guards). Resolves
6605 - Enable Tor to read configuration, state, and key information from
6606 a FIFO. Previously Tor would only read from files with a positive
6607 stat.st_size. Code from meejah; fixes bug 6044.
6610 - Correct file sizes when reading binary files on Cygwin, to avoid
6611 a bug where Tor would fail to read its state file. Fixes bug 6844;
6612 bugfix on 0.1.2.7-alpha.
6613 - Correctly handle votes with more than 31 flags. Fixes bug 6853;
6614 bugfix on 0.2.0.3-alpha.
6615 - When complaining about a client port on a public address, log
6616 which address we're complaining about. Fixes bug 4020; bugfix on
6617 0.2.3.3-alpha. Patch by Tom Fitzhenry.
6618 - Convert an assert in the pathbias code to a log message. The assert
6619 appears to only be triggerable by Tor2Web mode. Fixes bug 6866;
6620 bugfix on 0.2.3.17-beta.
6621 - Our new buildsystem was overzealous about rebuilding manpages: it
6622 would rebuild them all whenever any one of them changed. Now our
6623 dependency checking should be correct. Fixes bug 6843; bugfix on
6625 - Don't do reachability testing over IPv6 unless AuthDirPublishIPv6
6626 is set. Fixes bug 6880. Bugfix on 0.2.4.1-alpha.
6627 - Correct log printout about which address family is preferred
6628 when connecting to a bridge with both an IPv4 and IPv6 OR port.
6629 Fixes bug 6884; bugfix on 0.2.4.1-alpha.
6631 o Minor bugfixes (code cleanliness):
6632 - Fix round_to_power_of_2() so it doesn't invoke undefined behavior
6633 with large values. This situation was untriggered, but nevertheless
6634 incorrect. Fixes bug 6831; bugfix on 0.2.0.1-alpha.
6635 - Reject consensus votes with more than 64 known-flags. We aren't even
6636 close to that limit yet, and our code doesn't handle it correctly.
6637 Fixes bug 6833; bugfix on 0.2.0.1-alpha.
6638 - Avoid undefined behavior when parsing the list of supported
6639 rendezvous/introduction protocols in a hidden service descriptor.
6640 Previously, Tor would have confused (as-yet-unused) protocol version
6641 numbers greater than 32 with lower ones on many platforms. Fixes
6642 bug 6827; bugfix on 0.2.0.10-alpha. Found by George Kadianakis.
6643 - Fix handling of rendezvous client authorization types over 8.
6644 Fixes bug 6861; bugfix on 0.2.1.5-alpha.
6645 - Fix building with older versions of GCC (2.95, for one) that don't
6646 like preprocessor directives inside macro arguments. Found by
6647 grarpamp. Fixes bug 6842; bugfix on 0.2.4.2-alpha.
6648 - Switch weighted node selection rule from using a list of doubles
6649 to using a list of int64_t. This change should make the process
6650 slightly easier to debug and maintain. Needed to finish ticket 6538.
6652 o Code simplification and refactoring:
6653 - Move the generic "config" code into a new file, and have "config.c"
6654 hold only torrc- and state-related code. Resolves ticket 6823.
6655 - Move the core of our "choose a weighted element at random" logic
6656 into its own function, and give it unit tests. Now the logic is
6657 testable, and a little less fragile too.
6658 - Removed the testing_since field of node_t, which hasn't been used
6659 for anything since 0.2.0.9-alpha.
6661 o Documentation fixes:
6662 - Clarify that hidden services are TCP only. Fixes bug 6024.
6663 - Resolve a typo in torrc.sample.in. Fixes bug 6819; bugfix on
6667 Changes in version 0.2.3.22-rc - 2012-09-11
6668 Tor 0.2.3.22-rc fixes another opportunity for a remotely triggerable
6672 - Fix an assertion failure in tor_timegm() that could be triggered
6673 by a badly formatted directory object. Bug found by fuzzing with
6674 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6677 - Avoid segfault when starting up having run with an extremely old
6678 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6682 Changes in version 0.2.2.39 - 2012-09-11
6683 Tor 0.2.2.39 fixes two more opportunities for remotely triggerable
6687 - Fix an assertion failure in tor_timegm() that could be triggered
6688 by a badly formatted directory object. Bug found by fuzzing with
6689 Radamsa. Fixes bug 6811; bugfix on 0.2.0.20-rc.
6690 - Do not crash when comparing an address with port value 0 to an
6691 address policy. This bug could have been used to cause a remote
6692 assertion failure by or against directory authorities, or to
6693 allow some applications to crash clients. Fixes bug 6690; bugfix
6697 Changes in version 0.2.4.2-alpha - 2012-09-10
6698 Tor 0.2.4.2-alpha enables port forwarding for pluggable transports,
6699 raises the default rate limiting even more, and makes the bootstrapping
6700 log messages less noisy.
6703 - Automatically forward the TCP ports of pluggable transport
6704 proxies using tor-fw-helper if PortForwarding is enabled. Implements
6708 - Raise the default BandwidthRate/BandwidthBurst values from 5MB/10MB
6709 to 1GB/1GB. The previous defaults were intended to be "basically
6710 infinite", but it turns out they're now limiting our 100mbit+
6711 relays and bridges. Fixes bug 6605; bugfix on 0.2.0.10-alpha (the
6712 last time we raised it).
6715 - Detect when we're running with a version of OpenSSL other than the
6716 one we compiled with. This has occasionally given people hard-to-
6718 - Log fewer lines at level "notice" about our OpenSSL and Libevent
6719 versions and capabilities when everything is going right. Resolves
6720 part of ticket 6736.
6721 - Directory authorities no long accept descriptors for any version of
6722 Tor before 0.2.2.35, or for any 0.2.3 release before 0.2.3.10-alpha.
6723 These versions are insecure, unsupported, or both. Implements
6727 - Rename the (internal-use-only) UsingTestingNetworkDefaults option
6728 to start with a triple-underscore so the controller won't touch it.
6729 Patch by Meejah. Fixes bug 3155. Bugfix on 0.2.2.23-alpha.
6730 - Avoid segfault when starting up having run with an extremely old
6731 version of Tor and parsing its state file. Fixes bug 6801; bugfix
6733 - Rename the (testing-use-only) _UseFilteringSSLBufferevents option
6734 so it doesn't start with _. Fixes bug 3155. Bugfix on 0.2.3.1-alpha.
6735 - Don't follow the NULL pointer if microdescriptor generation fails.
6736 (This does not appear to be triggerable, but it's best to be safe.)
6737 Found by "f. tp.". Fixes bug 6797; bugfix on 0.2.4.1-alpha.
6738 - Fix mis-declared dependencies on src/common/crypto.c and
6739 src/or/tor_main.c that could break out-of-tree builds under some
6740 circumstances. Fixes bug 6778; bugfix on 0.2.4.1-alpha.
6741 - Avoid a warning when building common_sha1.i out of tree. Fixes bug
6742 6778; bugfix on 0.2.4.1-alpha.
6743 - Fix a harmless (in this case) build warning for implicitly
6744 converting a strlen() to an int. Bugfix on 0.2.4.1-alpha.
6747 - Now that all versions before 0.2.2.x are disallowed, we no longer
6748 need to work around their missing features. Thus we can remove a
6749 bunch of compatibility code.
6752 - Tweak tor-fw-helper to accept an arbitrary amount of arbitrary
6753 TCP ports to forward. In the past it only accepted two ports:
6754 the ORPort and the DirPort.
6757 Changes in version 0.2.4.1-alpha - 2012-09-05
6758 Tor 0.2.4.1-alpha lets bridges publish their pluggable transports to
6759 bridgedb; lets relays use IPv6 addresses and directory authorities
6760 advertise them; and switches to a cleaner build interface.
6762 This is the first alpha release in a new series, so expect there to
6763 be bugs. Users who would rather test out a more stable branch should
6764 stay with 0.2.3.x for now.
6766 o Major features (bridges):
6767 - Bridges now report the pluggable transports they support to the
6768 bridge authority, so it can pass the supported transports on to
6769 bridgedb and/or eventually do reachability testing. Implements
6772 o Major features (IPv6):
6773 - Bridge authorities now accept IPv6 bridge addresses and include
6774 them in network status documents. Implements ticket 5534.
6775 - Clients who set "ClientUseIPv6 1" may connect to entry nodes over
6776 IPv6. Set "ClientPreferIPv6ORPort 1" to make this even more likely
6777 to happen. Implements ticket 5535.
6778 - All kind of relays, not just bridges, can now advertise an IPv6
6779 OR port. Implements ticket 6362.
6780 - Directory authorities vote on IPv6 OR ports using the new consensus
6781 method 14. Implements ticket 6363.
6783 o Major features (build):
6784 - Switch to a nonrecursive Makefile structure. Now instead of each
6785 Makefile.am invoking other Makefile.am's, there is a master
6786 Makefile.am that includes the others. This change makes our build
6787 process slightly more maintainable, and improves parallelism for
6788 building with make -j. Original patch by Stewart Smith; various
6789 fixes by Jim Meyering.
6790 - Where available, we now use automake's "silent" make rules by
6791 default, so that warnings are easier to spot. You can get the old
6792 behavior with "make V=1". Patch by Stewart Smith for ticket 6522.
6794 o Minor features (code security and spec conformance):
6795 - Clear keys and key-derived material left on the stack in
6796 rendservice.c and rendclient.c. Check return value of
6797 crypto_pk_write_private_key_to_string() in rend_service_load_keys().
6798 These fixes should make us more forward-secure against cold-boot
6799 attacks and the like. Fixes bug 2385.
6800 - Reject EXTEND cells sent to nonexistent streams. According to the
6801 spec, an EXTEND cell sent to _any_ nonzero stream ID is invalid, but
6802 we were only checking for stream IDs that were currently in use.
6803 Found while hunting for more instances of bug 6271. Bugfix on
6804 0.0.2pre8, which introduced incremental circuit construction.
6806 o Minor features (streamlining);
6807 - No longer include the "opt" prefix when generating routerinfos
6808 or v2 directories: it has been needless since Tor 0.1.2. Closes
6810 - Remove some now-needless code that tried to aggressively flush
6811 OR connections as data was added to them. Since 0.2.0.1-alpha, our
6812 cell queue logic has saved us from the failure mode that this code
6813 was supposed to prevent. Removing this code will limit the number
6814 of baroque control flow paths through Tor's network logic. Reported
6815 pseudonymously on IRC. Fixes bug 6468; bugfix on 0.2.0.1-alpha.
6817 o Minor features (controller):
6818 - Add a "GETINFO signal/names" control port command. Implements
6820 - Provide default values for all options via "GETINFO config/defaults".
6821 Implements ticket 4971.
6823 o Minor features (IPv6):
6824 - New config option "AuthDirHasIPv6Connectivity 1" that directory
6825 authorities should set if they have IPv6 connectivity and want to
6826 do reachability tests for IPv6 relays. Implements feature 5974.
6827 - A relay with an IPv6 OR port now sends that address in NETINFO
6828 cells (in addition to its other address). Implements ticket 6364.
6830 o Minor features (log messages):
6831 - Omit the first heartbeat log message, because it never has anything
6832 useful to say, and it clutters up the bootstrapping messages.
6833 Resolves ticket 6758.
6834 - Don't log about reloading the microdescriptor cache at startup. Our
6835 bootstrap warnings are supposed to tell the user when there's a
6836 problem, and our bootstrap notices say when there isn't. Resolves
6837 ticket 6759; bugfix on 0.2.2.6-alpha.
6838 - Don't log "I learned some more directory information" when we're
6839 reading cached directory information. Reserve it for when new
6840 directory information arrives in response to a fetch. Resolves
6842 - Prevent rounding error in path bias counts when scaling
6843 them down, and use the correct scale factor default. Also demote
6844 some path bias related log messages down a level and make others
6845 less scary sounding. Fixes bug 6647. Bugfix against 0.2.3.17-beta.
6846 - We no longer warn so much when generating manpages from their
6849 o Code simplifications and refactoring:
6850 - Enhance our internal sscanf replacement so that we can eliminate
6851 the last remaining uses of the system sscanf. (Though those uses
6852 of sscanf were safe, sscanf itself is generally error prone, so
6853 we want to eliminate when we can.) Fixes ticket 4195 and Coverity
6855 - Move ipv6_preferred from routerinfo_t to node_t. Addresses bug 4620.
6856 - Move last_reachable and testing_since from routerinfo_t to node_t.
6857 Implements ticket 5529.
6858 - Add replaycache_t structure, functions and unit tests, then refactor
6859 rend_service_introduce() to be more clear to read, improve, debug,
6860 and test. Resolves bug 6177.
6861 - Finally remove support for malloc_good_size and malloc_usable_size.
6862 We had hoped that these functions would let us eke a little more
6863 memory out of our malloc implementation. Unfortunately, the only
6864 implementations that provided these functions are also ones that
6865 are already efficient about not overallocation: they never got us
6866 more than 7 or so bytes per allocation. Removing them saves us a
6867 little code complexity and a nontrivial amount of build complexity.
6870 - Tor maintainers now require Automake version 1.9 or later to build
6871 Tor from the Git repository. (Automake is not required when building
6872 from a source distribution.)
6875 Changes in version 0.2.3.21-rc - 2012-09-05
6876 Tor 0.2.3.21-rc is the fourth release candidate for the Tor 0.2.3.x
6877 series. It fixes a trio of potential security bugs, fixes a bug where
6878 we were leaving some of the fast relays out of the microdescriptor
6879 consensus, resumes interpreting "ORPort 0" and "DirPort 0" correctly,
6880 and cleans up other smaller issues.
6882 o Major bugfixes (security):
6883 - Tear down the circuit if we get an unexpected SENDME cell. Clients
6884 could use this trick to make their circuits receive cells faster
6885 than our flow control would have allowed, or to gum up the network,
6886 or possibly to do targeted memory denial-of-service attacks on
6887 entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
6888 from July 2002, before the release of Tor 0.0.0. We had committed
6889 this patch previously, but we had to revert it because of bug 6271.
6890 Now that 6271 is fixed, this patch appears to work.
6891 - Reject any attempt to extend to an internal address. Without
6892 this fix, a router could be used to probe addresses on an internal
6893 network to see whether they were accepting connections. Fixes bug
6894 6710; bugfix on 0.0.8pre1.
6895 - Do not crash when comparing an address with port value 0 to an
6896 address policy. This bug could have been used to cause a remote
6897 assertion failure by or against directory authorities, or to
6898 allow some applications to crash clients. Fixes bug 6690; bugfix
6902 - Remove the upper bound on microdescriptor length. We were hitting
6903 the limit for routers with complex exit policies or family
6904 declarations, causing clients to not use them. Fixes the first
6905 piece of bug 6404; fix on 0.2.2.6-alpha.
6906 - Detect "ORPort 0" as meaning, uniformly, that we're not running
6907 as a relay. Previously, some of our code would treat the presence
6908 of any ORPort line as meaning that we should act like a relay,
6909 even though our new listener code would correctly not open any
6910 ORPorts for ORPort 0. Similar bugs in other Port options are also
6911 fixed. Fixes the first half of bug 6507; bugfix on 0.2.3.3-alpha.
6914 - Avoid a pair of double-free and use-after-mark bugs that can
6915 occur with certain timings in canceled and re-received DNS
6916 requests. Fixes bug 6472; bugfix on 0.0.7rc1.
6917 - Fix build and 64-bit compile warnings from --enable-openbsd-malloc.
6918 Fixes bug 6379. Bugfix on 0.2.0.20-rc.
6919 - Allow one-hop directory fetching circuits the full "circuit build
6920 timeout" period, rather than just half of it, before failing them
6921 and marking the relay down. This fix should help reduce cases where
6922 clients declare relays (or worse, bridges) unreachable because
6923 the TLS handshake takes a few seconds to complete. Fixes bug 6743;
6924 bugfix on 0.2.2.2-alpha, where we changed the timeout from a static
6926 - Authorities no longer include any router in their microdescriptor
6927 consensuses for which they couldn't generate or agree on a
6928 microdescriptor. Fixes the second piece of bug 6404; fix on
6930 - Detect and reject attempts to specify both "FooPort" and
6931 "FooPort 0" in the same configuration domain. (It's still okay
6932 to have a FooPort in your configuration file, and use "FooPort 0"
6933 on the command line to disable it.) Fixes the second half of bug
6934 6507; bugfix on 0.2.3.3-alpha.
6935 - Make wildcarded addresses (that is, ones beginning with "*.") work
6936 when provided via the controller's MapAddress command. Previously,
6937 they were accepted, but we never actually noticed that they were
6938 wildcards. Fixes bug 6244; bugfix on 0.2.3.9-alpha.
6939 - Avoid crashing on a malformed state file where EntryGuardPathBias
6940 precedes EntryGuard. Fix for bug 6774; bugfix on 0.2.3.17-beta.
6941 - Add a (probably redundant) memory clear between iterations of
6942 the router status voting loop, to prevent future coding errors
6943 where data might leak between iterations of the loop. Resolves
6946 o Minor bugfixes (log messages):
6947 - Downgrade "set buildtimeout to low value" messages to "info"
6948 severity; they were never an actual problem, there was never
6949 anything reasonable to do about them, and they tended to spam logs
6950 from time to time. Fixes bug 6251; bugfix on 0.2.2.2-alpha.
6951 - Downgrade path-bias warning messages to "info". We'll try to get
6952 them working better in 0.2.4. Add internal circuit construction
6953 state to protect against the noisy warn message "Unexpectedly high
6954 circuit_successes". Also add some additional rate-limited notice
6955 messages to help determine the root cause of the warn. Fixes bug
6956 6475. Bugfix against 0.2.3.17-beta.
6957 - Move log message when unable to find a microdesc in a routerstatus
6958 entry to parse time. Previously we'd spam this warning every time
6959 we tried to figure out which microdescriptors to download. Fixes
6960 the third piece of bug 6404; fix on 0.2.3.18-rc.
6963 - Consider new, removed or changed IPv6 OR ports a non-cosmetic
6964 change when the authority is deciding whether to accept a newly
6965 uploaded descriptor. Implements ticket 6423.
6966 - Add missing documentation for consensus and microdesc files.
6967 Resolves ticket 6732.
6970 Changes in version 0.2.2.38 - 2012-08-12
6971 Tor 0.2.2.38 fixes a remotely triggerable crash bug, and fixes a timing
6972 attack that could in theory leak path information.
6975 - Avoid an uninitialized memory read when reading a vote or consensus
6976 document that has an unrecognized flavor name. This read could
6977 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
6978 - Try to leak less information about what relays a client is
6979 choosing to a side-channel attacker. Previously, a Tor client would
6980 stop iterating through the list of available relays as soon as it
6981 had chosen one, thus finishing a little earlier when it picked
6982 a router earlier in the list. If an attacker can recover this
6983 timing information (nontrivial but not proven to be impossible),
6984 they could learn some coarse-grained information about which relays
6985 a client was picking (middle nodes in particular are likelier to
6986 be affected than exits). The timing attack might be mitigated by
6987 other factors (see bug 6537 for some discussion), but it's best
6988 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
6991 Changes in version 0.2.3.20-rc - 2012-08-05
6992 Tor 0.2.3.20-rc is the third release candidate for the Tor 0.2.3.x
6993 series. It fixes a pair of code security bugs and a potential anonymity
6994 issue, updates our RPM spec files, and cleans up other smaller issues.
6997 - Avoid read-from-freed-memory and double-free bugs that could occur
6998 when a DNS request fails while launching it. Fixes bug 6480;
6999 bugfix on 0.2.0.1-alpha.
7000 - Avoid an uninitialized memory read when reading a vote or consensus
7001 document that has an unrecognized flavor name. This read could
7002 lead to a remote crash bug. Fixes bug 6530; bugfix on 0.2.2.6-alpha.
7003 - Try to leak less information about what relays a client is
7004 choosing to a side-channel attacker. Previously, a Tor client would
7005 stop iterating through the list of available relays as soon as it
7006 had chosen one, thus finishing a little earlier when it picked
7007 a router earlier in the list. If an attacker can recover this
7008 timing information (nontrivial but not proven to be impossible),
7009 they could learn some coarse-grained information about which relays
7010 a client was picking (middle nodes in particular are likelier to
7011 be affected than exits). The timing attack might be mitigated by
7012 other factors (see bug 6537 for some discussion), but it's best
7013 not to take chances. Fixes bug 6537; bugfix on 0.0.8rc1.
7016 - Try to make the warning when giving an obsolete SOCKSListenAddress
7017 a little more useful.
7018 - Terminate active server managed proxies if Tor stops being a
7019 relay. Addresses parts of bug 6274; bugfix on 0.2.3.6-alpha.
7020 - Provide a better error message about possible OSX Asciidoc failure
7021 reasons. Fixes bug 6436.
7022 - Warn when Tor is configured to use accounting in a way that can
7023 link a hidden service to some other hidden service or public
7024 address. Resolves ticket 6490.
7027 - Check return value of fputs() when writing authority certificate
7028 file. Fixes Coverity issue 709056; bugfix on 0.2.0.1-alpha.
7029 - Ignore ServerTransportPlugin lines when Tor is not configured as
7030 a relay. Fixes bug 6274; bugfix on 0.2.3.6-alpha.
7031 - When disabling guards for having too high a proportion of failed
7032 circuits, make sure to look at each guard. Fixes bug 6397; bugfix
7036 - Update our default RPM spec files to work with mock and rpmbuild
7037 on RHEL/Fedora. They have an updated set of dependencies and
7038 conflicts, a fix for an ancient typo when creating the "_tor"
7039 user, and better instructions. Thanks to Ondrej Mikle for the
7040 patch series. Fixes bug 6043.
7043 - Make it possible to set the TestingTorNetwork configuration
7044 option using AlternateDirAuthority and AlternateBridgeAuthority
7045 as an alternative to setting DirServer. Addresses ticket 6377.
7048 - Clarify the documentation for the Alternate*Authority options.
7050 - Fix some typos in the manpages. Patch from A. Costa. Fixes bug 6500.
7052 o Code simplification and refactoring:
7053 - Do not use SMARTLIST_FOREACH for any loop whose body exceeds
7054 10 lines. Also, don't nest them. Doing so in the past has
7055 led to hard-to-debug code. The new style is to use the
7056 SMARTLIST_FOREACH_{BEGIN,END} pair. Addresses issue 6400.
7059 Changes in version 0.2.3.19-rc - 2012-07-06
7060 Tor 0.2.3.19-rc is the second release candidate for the Tor 0.2.3.x
7061 series. It fixes the compile on Windows, reverts to a GeoIP database
7062 that isn't as broken, and fixes a flow control bug that has been around
7063 since the beginning of Tor.
7066 - Fix a bug handling SENDME cells on nonexistent streams that could
7067 result in bizarre window values. Report and patch contributed
7068 pseudonymously. Fixes part of bug 6271. This bug was introduced
7069 before the first Tor release, in svn commit r152.
7070 - Revert to the May 1 2012 Maxmind GeoLite Country database. In the
7071 June 2012 database, Maxmind marked many Tor relays as country "A1",
7072 which will cause risky behavior for clients that set EntryNodes
7073 or ExitNodes. Addresses bug 6334; bugfix on 0.2.3.17-beta.
7074 - Instead of ENOBUFS on Windows, say WSAENOBUFS. Fixes compilation
7075 on Windows. Fixes bug 6296; bugfix on 0.2.3.18-rc.
7078 - Fix wrong TCP port range in parse_port_range(). Fixes bug 6218;
7079 bugfix on 0.2.1.10-alpha.
7082 Changes in version 0.2.3.18-rc - 2012-06-28
7083 Tor 0.2.3.18-rc is the first release candidate for the Tor 0.2.3.x
7084 series. It fixes a few smaller bugs, but generally appears stable.
7085 Please test it and let us know whether it is!
7088 - Allow wildcarded mapaddress targets to be specified on the
7089 controlport. Partially fixes bug 6244; bugfix on 0.2.3.9-alpha.
7090 - Make our linker option detection code more robust against linkers
7091 such as on FreeBSD 8, where a bad combination of options completes
7092 successfully but makes an unrunnable binary. Fixes bug 6173;
7093 bugfix on 0.2.3.17-beta.
7095 o Minor bugfixes (on 0.2.2.x and earlier):
7096 - Avoid a false positive in the util/threads unit test by increasing
7097 the maximum timeout time. Fixes bug 6227; bugfix on 0.2.0.4-alpha.
7098 - Replace "Sending publish request" log messages with "Launching
7099 upload", so that they no longer confusingly imply that we're
7100 sending something to a directory we might not even be connected
7101 to yet. Fixes bug 3311; bugfix on 0.2.0.10-alpha.
7102 - Make sure to set *socket_error in all error cases in
7103 connection_connect(), so it can't produce a warning about
7104 errno being zero from errno_to_orconn_end_reason(). Bugfix on
7105 0.2.1.1-alpha; resolves ticket 6028.
7106 - Downgrade "Got a certificate, but we already have it" log messages
7107 from warning to info, except when we're a dirauth. Fixes bug 5238;
7108 bugfix on 0.2.1.7-alpha.
7109 - When checking for requested signatures on the latest consensus
7110 before serving it to a client, make sure to check the right
7111 consensus flavor. Bugfix on 0.2.2.6-alpha.
7112 - Downgrade "eventdns rejected address" message to LOG_PROTOCOL_WARN.
7113 Fixes bug 5932; bugfix on 0.2.2.7-alpha.
7115 o Minor bugfixes (on 0.2.3.x):
7116 - Make format_helper_exit_status() avoid unnecessary space padding
7117 and stop confusing log_from_pipe(). Fixes ticket 5557; bugfix
7119 - Downgrade a message about cleaning the microdescriptor cache to
7120 "info" from "notice". Fixes bug 6238; bugfix on 0.2.3.1-alpha.
7121 - Log a BUG message at severity INFO if we have a networkstatus with
7122 a missing entry for some microdescriptor. Continues on a patch
7124 - Improve the log message when a managed proxy fails to launch. Fixes
7125 bug 5099; bugfix on 0.2.3.6-alpha.
7126 - Don't do DNS lookups when parsing corrupted managed proxy protocol
7127 messages. Fixes bug 6226; bugfix on 0.2.3.6-alpha.
7128 - When formatting wildcarded address mappings for the controller,
7129 be sure to include "*." as appropriate. Partially fixes bug 6244;
7130 bugfix on 0.2.3.9-alpha.
7131 - Avoid a warning caused by using strcspn() from glibc with clang 3.0.
7132 Bugfix on 0.2.3.13-alpha.
7133 - Stop logging messages about running with circuit timeout learning
7134 enabled at severity LD_BUG. Fixes bug 6169; bugfix on 0.2.3.17-beta.
7135 - Disable a spurious warning about reading on a marked and flushing
7136 connection. We shouldn't be doing that, but apparently we
7137 sometimes do. Fixes bug 6203; bugfix on 0.2.3.17-beta.
7138 - Fix a bug that stopped AllowDotExit from working on addresses
7139 that had an entry in the DNS cache. Fixes bug 6211; bugfix on
7142 o Code simplification, refactoring, unit tests:
7143 - Move tor_gettimeofday_cached() into compat_libevent.c, and use
7144 Libevent's notion of cached time when possible.
7145 - Remove duplicate code for invoking getrlimit() from control.c.
7146 - Add a unit test for the environment_variable_names_equal function.
7149 - Document the --defaults-torrc option, and the new (in 0.2.3)
7150 semantics for overriding, extending, and clearing lists of
7151 options. Closes bug 4748.
7154 Changes in version 0.2.3.17-beta - 2012-06-15
7155 Tor 0.2.3.17-beta enables compiler and linker hardening by default,
7156 gets our TLS handshake back on track for being able to blend in with
7157 Firefox, fixes a big bug in 0.2.3.16-alpha that broke Tor's interaction
7158 with Vidalia, and otherwise continues to get us closer to a release
7162 - Enable gcc and ld hardening by default. Resolves ticket 5210.
7163 - Update TLS cipher list to match Firefox 8 and later. Resolves
7165 - Implement the client side of proposal 198: remove support for
7166 clients falsely claiming to support standard ciphersuites that
7167 they can actually provide. As of modern OpenSSL versions, it's not
7168 necessary to fake any standard ciphersuite, and doing so prevents
7169 us from using better ciphersuites in the future, since servers
7170 can't know whether an advertised ciphersuite is really supported or
7171 not. Some hosts -- notably, ones with very old versions of OpenSSL
7172 or where OpenSSL has been built with ECC disabled -- will stand
7173 out because of this change; TBB users should not be affected.
7176 - Change the default value for DynamicDHGroups (introduced in
7177 0.2.3.9-alpha) to 0. This feature can make Tor relays less
7178 identifiable by their use of the mod_ssl DH group, but at
7179 the cost of some usability (#4721) and bridge tracing (#6087)
7180 regressions. Resolves ticket 5598.
7181 - Send a CRLF at the end of each STATUS_* control protocol event. This
7182 bug tickled a bug in Vidalia which would make it freeze. Fixes
7183 bug 6094; bugfix on 0.2.3.16-alpha.
7186 - Disable writing on marked-for-close connections when they are
7187 blocked on bandwidth, to prevent busy-looping in Libevent. Fixes
7188 bug 5263; bugfix on 0.0.2pre13, where we first added a special
7189 case for flushing marked connections.
7190 - Detect SSL handshake even when the initial attempt to write the
7191 server hello fails. Fixes bug 4592; bugfix on 0.2.0.13-alpha.
7192 - Change the AllowDotExit rules so they should actually work.
7193 We now enforce AllowDotExit only immediately after receiving an
7194 address via SOCKS or DNSPort: other sources are free to provide
7195 .exit addresses after the resolution occurs. Fixes bug 3940;
7196 bugfix on 0.2.2.1-alpha.
7197 - Fix a (harmless) integer overflow in cell statistics reported by
7198 some fast relays. Fixes bug 5849; bugfix on 0.2.2.1-alpha.
7199 - Make sure circuitbuild.c checks LearnCircuitBuildTimeout in all the
7200 right places and never depends on the consensus parameters or
7201 computes adaptive timeouts when it is disabled. Fixes bug 5049;
7202 bugfix on 0.2.2.14-alpha.
7203 - When building Tor on Windows with -DUNICODE (not default), ensure
7204 that error messages, filenames, and DNS server names are always
7205 NUL-terminated when we convert them to a single-byte encoding.
7206 Fixes bug 5909; bugfix on 0.2.2.16-alpha.
7207 - Make Tor build correctly again with -DUNICODE -D_UNICODE defined.
7208 Fixes bug 6097; bugfix on 0.2.2.16-alpha.
7209 - Fix an edge case where TestingTorNetwork is set but the authorities
7210 and relays all have an uptime of zero, where the private Tor network
7211 could briefly lack support for hidden services. Fixes bug 3886;
7212 bugfix on 0.2.2.18-alpha.
7213 - Correct the manpage's descriptions for the default values of
7214 DirReqStatistics and ExtraInfoStatistics. Fixes bug 2865; bugfix
7216 - Fix the documentation for the --hush and --quiet command line
7217 options, which changed their behavior back in 0.2.3.3-alpha.
7218 - Fix compilation warning with clang 3.1. Fixes bug 6141; bugfix on
7222 - Rate-limit the "Weighted bandwidth is 0.000000" message, and add
7223 more information to it, so that we can track it down in case it
7224 returns again. Mitigates bug 5235.
7225 - Check CircuitBuildTimeout and LearnCircuitBuildTimeout in
7226 options_validate(); warn if LearnCircuitBuildTimeout is disabled and
7227 CircuitBuildTimeout is set unreasonably low. Resolves ticket 5452.
7228 - Warn the user when HTTPProxy, but no other proxy type, is
7229 configured. This can cause surprising behavior: it doesn't send
7230 all of Tor's traffic over the HTTPProxy -- it sends unencrypted
7231 directory traffic only. Resolves ticket 4663.
7232 - Issue a notice if a guard completes less than 40% of your circuits.
7233 Threshold is configurable by torrc option PathBiasNoticeRate and
7234 consensus parameter pb_noticepct. There is additional, off-by-
7235 default code to disable guards which fail too many circuits.
7236 Addresses ticket 5458.
7237 - Update to the June 6 2012 Maxmind GeoLite Country database.
7239 o Code simplifications and refactoring:
7240 - Remove validate_pluggable_transports_config(): its warning
7241 message is now handled by connection_or_connect().
7244 Changes in version 0.2.2.37 - 2012-06-06
7245 Tor 0.2.2.37 introduces a workaround for a critical renegotiation
7246 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7250 - Work around a bug in OpenSSL that broke renegotiation with TLS
7251 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7252 the v2 Tor connection protocol when both sides were using OpenSSL
7253 1.0.1 would fail. Resolves ticket 6033.
7254 - When waiting for a client to renegotiate, don't allow it to add
7255 any bytes to the input buffer. This fixes a potential DoS issue.
7256 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7257 - Fix an edge case where if we fetch or publish a hidden service
7258 descriptor, we might build a 4-hop circuit and then use that circuit
7259 for exiting afterwards -- even if the new last hop doesn't obey our
7260 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7263 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7264 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7267 - Tell GCC and Clang to check for any errors in format strings passed
7268 to the tor_v*(print|scan)f functions.
7271 Changes in version 0.2.3.16-alpha - 2012-06-05
7272 Tor 0.2.3.16-alpha introduces a workaround for a critical renegotiation
7273 bug in OpenSSL 1.0.1 (where 20% of the Tor network can't talk to itself
7274 currently). It also fixes a variety of smaller bugs and other cleanups
7275 that get us closer to a release candidate.
7277 o Major bugfixes (general):
7278 - Work around a bug in OpenSSL that broke renegotiation with TLS
7279 1.1 and TLS 1.2. Without this workaround, all attempts to speak
7280 the v2 Tor connection protocol when both sides were using OpenSSL
7281 1.0.1 would fail. Resolves ticket 6033.
7282 - When waiting for a client to renegotiate, don't allow it to add
7283 any bytes to the input buffer. This fixes a potential DoS issue.
7284 Fixes bugs 5934 and 6007; bugfix on 0.2.0.20-rc.
7285 - Pass correct OR address to managed proxies (like obfsproxy),
7286 even when ORListenAddress is used. Fixes bug 4865; bugfix on
7288 - The advertised platform of a router now includes only its operating
7289 system's name (e.g., "Linux", "Darwin", "Windows 7"), and not its
7290 service pack level (for Windows) or its CPU architecture (for Unix).
7291 We also no longer include the "git-XYZ" tag in the version. Resolves
7294 o Major bugfixes (clients):
7295 - If we are unable to find any exit that supports our predicted ports,
7296 stop calling them predicted, so that we don't loop and build
7297 hopeless circuits indefinitely. Fixes bug 3296; bugfix on 0.0.9pre6,
7298 which introduced predicted ports.
7299 - Fix an edge case where if we fetch or publish a hidden service
7300 descriptor, we might build a 4-hop circuit and then use that circuit
7301 for exiting afterwards -- even if the new last hop doesn't obey our
7302 ExitNodes config option. Fixes bug 5283; bugfix on 0.2.0.10-alpha.
7303 - Check at each new consensus whether our entry guards were picked
7304 long enough ago that we should rotate them. Previously, we only
7305 did this check at startup, which could lead to us holding a guard
7306 indefinitely. Fixes bug 5380; bugfix on 0.2.1.14-rc.
7307 - When fetching a bridge descriptor from a bridge authority,
7308 always do so anonymously, whether we have been able to open
7309 circuits or not. Partial fix for bug 1938; bugfix on 0.2.0.7-alpha.
7310 This behavior makes it *safer* to use UpdateBridgesFromAuthority,
7311 but we'll need to wait for bug 6010 before it's actually usable.
7313 o Major bugfixes (directory authorities):
7314 - When computing weight parameters, behave more robustly in the
7315 presence of a bad bwweightscale value. Previously, the authorities
7316 would crash if they agreed on a sufficiently broken weight_scale
7317 value: now, they use a reasonable default and carry on. Partial
7318 fix for 5786; bugfix on 0.2.2.17-alpha.
7319 - Check more thoroughly to prevent a rogue authority from
7320 double-voting on any consensus directory parameter. Previously,
7321 authorities would crash in this case if the total number of
7322 votes for any parameter exceeded the number of active voters,
7323 but would let it pass otherwise. Partial fix for bug 5786; bugfix
7327 - Rate-limit log messages when asked to connect anonymously to
7328 a private address. When these hit, they tended to hit fast and
7329 often. Also, don't bother trying to connect to addresses that we
7330 are sure will resolve to 127.0.0.1: getting 127.0.0.1 in a directory
7331 reply makes us think we have been lied to, even when the address the
7332 client tried to connect to was "localhost." Resolves ticket 2822.
7333 - Allow packagers to insert an extra string in server descriptor
7334 platform lines by setting the preprocessor variable TOR_BUILD_TAG.
7335 Resolves the rest of ticket 2988.
7336 - Raise the threshold of server descriptors needed (75%) and exit
7337 server descriptors needed (50%) before we will declare ourselves
7338 bootstrapped. This will make clients start building circuits a
7339 little later, but makes the initially constructed circuits less
7340 skewed and less in conflict with further directory fetches. Fixes
7342 - Close any connection that sends unrecognized junk before the
7343 handshake. Solves an issue noted in bug 4369.
7344 - Improve log messages about managed transports. Resolves ticket 5070.
7345 - Tag a bridge's descriptor as "never to be sent unencrypted".
7346 This shouldn't matter, since bridges don't open non-anonymous
7347 connections to the bridge authority and don't allow unencrypted
7348 directory connections from clients, but we might as well make
7349 sure. Closes bug 5139.
7350 - Expose our view of whether we have gone dormant to the controller,
7351 via a new "GETINFO dormant" value. Torbutton and other controllers
7352 can use this to avoid doing periodic requests through Tor while
7353 it's dormant (bug 4718). Fixes bug 5954.
7354 - Tell GCC and Clang to check for any errors in format strings passed
7355 to the tor_v*(print|scan)f functions.
7356 - Update to the May 1 2012 Maxmind GeoLite Country database.
7358 o Minor bugfixes (already included in 0.2.2.36):
7359 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7360 Fixes bug 5346; bugfix on 0.0.8pre3.
7361 - Correct parsing of certain date types in parse_http_time().
7362 Without this patch, If-Modified-Since would behave
7363 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7364 Esteban Manchado Velázques.
7365 - Make our number-parsing functions always treat too-large values
7366 as an error, even when those values exceed the width of the
7367 underlying type. Previously, if the caller provided these
7368 functions with minima or maxima set to the extreme values of the
7369 underlying integer type, these functions would return those
7370 values on overflow rather than treating overflow as an error.
7371 Fixes part of bug 5786; bugfix on 0.0.9.
7372 - If we hit the error case where routerlist_insert() replaces an
7373 existing (old) server descriptor, make sure to remove that
7374 server descriptor from the old_routers list. Fix related to bug
7375 1776. Bugfix on 0.2.2.18-alpha.
7376 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7377 circuits. Fixes issue 5259.
7379 o Minor bugfixes (coding cleanup, on 0.2.2.x and earlier):
7380 - Prevent a null-pointer dereference when receiving a data cell
7381 for a nonexistent stream when the circuit in question has an
7382 empty deliver window. We don't believe this is triggerable,
7383 since we don't currently allow deliver windows to become empty,
7384 but the logic is tricky enough that it's better to make the code
7385 robust. Fixes bug 5541; bugfix on 0.0.2pre14.
7386 - Fix a memory leak when trying to launch a DNS request when the
7387 network is disabled or the nameservers are unconfigurable. Fixes
7388 bug 5916; bugfix on Tor 0.1.2.1-alpha (for the unconfigurable
7389 nameserver case) and on 0.2.3.9-alpha (for the DisableNetwork case).
7390 - Don't hold a Windows file handle open for every file mapping;
7391 the file mapping handle is sufficient. Fixes bug 5951; bugfix on
7393 - Avoid O(n^2) performance characteristics when parsing a large
7394 extrainfo cache. Fixes bug 5828; bugfix on 0.2.0.1-alpha.
7395 - Format more doubles with %f, not %lf. Patch from grarpamp to make
7396 Tor build correctly on older BSDs again. Fixes bug 3894; bugfix on
7398 - Make our replacement implementation of strtok_r() compatible with
7399 the standard behavior of strtok_r(). Patch by nils. Fixes bug 5091;
7400 bugfix on 0.2.2.1-alpha.
7401 - Fix a NULL-pointer dereference on a badly formed
7402 SETCIRCUITPURPOSE command. Found by mikeyc. Fixes bug 5796;
7403 bugfix on 0.2.2.9-alpha.
7404 - Fix a build warning with Clang 3.1 related to our use of vasprintf.
7405 Fixes bug 5969. Bugfix on 0.2.2.11-alpha.
7406 - Defensively refactor rend_mid_rendezvous() so that protocol
7407 violations and length checks happen in the beginning. Fixes
7409 - Set _WIN32_WINNT to 0x0501 consistently throughout the code, so
7410 that IPv6 stuff will compile on MSVC, and compilation issues
7411 will be easier to track down. Fixes bug 5861.
7413 o Minor bugfixes (correctness, on 0.2.2.x and earlier):
7414 - Exit nodes now correctly report EADDRINUSE and EADDRNOTAVAIL as
7415 resource exhaustion, so that clients can adjust their load to
7416 try other exits. Fixes bug 4710; bugfix on 0.1.0.1-rc, which
7417 started using END_STREAM_REASON_RESOURCELIMIT.
7418 - Don't check for whether the address we're using for outbound
7419 connections has changed until after the outbound connection has
7420 completed. On Windows, getsockname() doesn't succeed until the
7421 connection is finished. Fixes bug 5374; bugfix on 0.1.1.14-alpha.
7422 - If the configuration tries to set MyFamily on a bridge, refuse to
7423 do so, and warn about the security implications. Fixes bug 4657;
7424 bugfix on 0.2.0.3-alpha.
7425 - If the client fails to set a reasonable set of ciphersuites
7426 during its v2 handshake renegotiation, allow the renegotiation to
7427 continue nevertheless (i.e. send all the required certificates).
7428 Fixes bug 4591; bugfix on 0.2.0.20-rc.
7429 - When we receive a SIGHUP and the controller __ReloadTorrcOnSIGHUP
7430 option is set to 0 (which Vidalia version 0.2.16 now does when
7431 a SAVECONF attempt fails), perform other actions that SIGHUP
7432 usually causes (like reopening the logs). Fixes bug 5095; bugfix
7434 - If we fail to write a microdescriptor to the disk cache, do not
7435 continue replacing the old microdescriptor file. Fixes bug 2954;
7436 bugfix on 0.2.2.6-alpha.
7437 - Exit nodes don't need to fetch certificates for authorities that
7438 they don't recognize; only directory authorities, bridges,
7439 and caches need to do that. Fixes part of bug 2297; bugfix on
7441 - Correctly handle checking the permissions on the parent
7442 directory of a control socket in the root directory. Bug found
7443 by Esteban Manchado Velázquez. Fixes bug 5089; bugfix on Tor
7445 - When told to add a bridge with the same digest as a preexisting
7446 bridge but a different addr:port, change the addr:port as
7447 requested. Previously we would not notice the change. Fixes half
7448 of bug 5603; fix on 0.2.2.26-beta.
7449 - End AUTHCHALLENGE error messages (in the control protocol) with
7450 a CRLF. Fixes bug 5760; bugfix on 0.2.2.36 and 0.2.3.13-alpha.
7452 o Minor bugfixes (on 0.2.3.x):
7453 - Turn an assertion (that the number of handshakes received as a
7454 server is not < 1) into a warning. Fixes bug 4873; bugfix on
7456 - Format IPv4 addresses correctly in ADDRMAP events. (Previously,
7457 we had reversed them when the answer was cached.) Fixes bug
7458 5723; bugfix on 0.2.3.1-alpha.
7459 - Work correctly on Linux systems with accept4 support advertised in
7460 their headers, but without accept4 support in the kernel. Fix
7461 by murb. Fixes bug 5762; bugfix on 0.2.3.1-alpha.
7462 - When told to add a bridge with the same addr:port as a preexisting
7463 bridge but a different transport, change the transport as
7464 requested. Previously we would not notice the change. Fixes half
7465 of bug 5603; fix on 0.2.3.2-alpha.
7466 - Avoid a "double-reply" warning when replying to a SOCKS request
7467 with a parse error. Patch from Fabian Keil. Fixes bug 4108;
7468 bugfix on 0.2.3.4-alpha.
7469 - Fix a bug where a bridge authority crashes if it has seen no
7470 directory requests when it's time to write statistics to disk.
7471 Fixes bug 5891; bugfix on 0.2.3.6-alpha. Also fixes bug 5508 in
7473 - Don't try to open non-control listeners when DisableNetwork is set.
7474 Previously, we'd open all listeners, then immediately close them.
7475 Fixes bug 5604; bugfix on 0.2.3.9-alpha.
7476 - Don't abort the managed proxy protocol if the managed proxy
7477 sends us an unrecognized line; ignore it instead. Fixes bug
7478 5910; bugfix on 0.2.3.9-alpha.
7479 - Fix a compile warning in crypto.c when compiling with clang 3.1.
7480 Fixes bug 5969, bugfix on 0.2.3.9-alpha.
7481 - Fix a compilation issue on GNU Hurd, which doesn't have PATH_MAX.
7482 Fixes bug 5355; bugfix on 0.2.3.11-alpha.
7483 - Remove bogus definition of "_WIN32" from src/win32/orconfig.h, to
7484 unbreak the MSVC build. Fixes bug 5858; bugfix on 0.2.3.12-alpha.
7485 - Resolve numerous small warnings and build issues with MSVC. Resolves
7488 o Documentation fixes:
7489 - Improve the manual's documentation for the NT Service command-line
7490 options. Addresses ticket 3964.
7491 - Clarify SessionGroup documentation slightly; resolves ticket 5437.
7492 - Document the changes to the ORPort and DirPort options, and the
7493 fact that {OR/Dir}ListenAddress is now unnecessary (and
7494 therefore deprecated). Resolves ticket 5597.
7497 - Remove the torrc.bridge file: we don't use it for anything, and
7498 it had become badly desynchronized from torrc.sample. Resolves
7502 Changes in version 0.2.2.36 - 2012-05-24
7503 Tor 0.2.2.36 updates the addresses for two of the eight directory
7504 authorities, fixes some potential anonymity and security issues,
7505 and fixes several crash bugs.
7507 Tor 0.2.1.x has reached its end-of-life. Those Tor versions have many
7508 known flaws, and nobody should be using them. You should upgrade. If
7509 you're using a Linux or BSD and its packages are obsolete, stop using
7510 those packages and upgrade anyway.
7512 o Directory authority changes:
7513 - Change IP address for maatuska (v3 directory authority).
7514 - Change IP address for ides (v3 directory authority), and rename
7518 - When building or running with any version of OpenSSL earlier
7519 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7520 versions have a bug (CVE-2011-4576) in which their block cipher
7521 padding includes uninitialized data, potentially leaking sensitive
7522 information to any peer with whom they make a SSLv3 connection. Tor
7523 does not use SSL v3 by default, but a hostile client or server
7524 could force an SSLv3 connection in order to gain information that
7525 they shouldn't have been able to get. The best solution here is to
7526 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7527 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7528 to make sure that the bug can't happen.
7529 - Never use a bridge or a controller-supplied node as an exit, even
7530 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7531 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7532 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7533 - Only build circuits if we have a sufficient threshold of the total
7534 descriptors that are marked in the consensus with the "Exit"
7535 flag. This mitigates an attack proposed by wanoskarnet, in which
7536 all of a client's bridges collude to restrict the exit nodes that
7537 the client knows about. Fixes bug 5343.
7538 - Provide controllers with a safer way to implement the cookie
7539 authentication mechanism. With the old method, if another locally
7540 running program could convince a controller that it was the Tor
7541 process, then that program could trick the controller into telling
7542 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7543 authentication method uses a challenge-response approach to prevent
7544 this attack. Fixes bug 5185; implements proposal 193.
7547 - Avoid logging uninitialized data when unable to decode a hidden
7548 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7549 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7550 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7552 - Fix builds when the path to sed, openssl, or sha1sum contains
7553 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7555 - Correct our replacements for the timeradd() and timersub() functions
7556 on platforms that lack them (for example, Windows). The timersub()
7557 function is used when expiring circuits, while timeradd() is
7558 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
7559 bugfix on 0.2.2.24-alpha.
7560 - Fix the SOCKET_OK test that we use to tell when socket
7561 creation fails so that it works on Win64. Fixes part of bug 4533;
7562 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7565 - Reject out-of-range times like 23:59:61 in parse_rfc1123_time().
7566 Fixes bug 5346; bugfix on 0.0.8pre3.
7567 - Make our number-parsing functions always treat too-large values
7568 as an error, even when those values exceed the width of the
7569 underlying type. Previously, if the caller provided these
7570 functions with minima or maxima set to the extreme values of the
7571 underlying integer type, these functions would return those
7572 values on overflow rather than treating overflow as an error.
7573 Fixes part of bug 5786; bugfix on 0.0.9.
7574 - Older Linux kernels erroneously respond to strange nmap behavior
7575 by having accept() return successfully with a zero-length
7576 socket. When this happens, just close the connection. Previously,
7577 we would try harder to learn the remote address: but there was
7578 no such remote address to learn, and our method for trying to
7579 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
7580 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
7581 - Correct parsing of certain date types in parse_http_time().
7582 Without this patch, If-Modified-Since would behave
7583 incorrectly. Fixes bug 5346; bugfix on 0.2.0.2-alpha. Patch from
7584 Esteban Manchado Velázques.
7585 - Change the BridgePassword feature (part of the "bridge community"
7586 design, which is not yet implemented) to use a time-independent
7587 comparison. The old behavior might have allowed an adversary
7588 to use timing to guess the BridgePassword value. Fixes bug 5543;
7589 bugfix on 0.2.0.14-alpha.
7590 - Detect and reject certain misformed escape sequences in
7591 configuration values. Previously, these values would cause us
7592 to crash if received in a torrc file or over an authenticated
7593 control port. Bug found by Esteban Manchado Velázquez, and
7594 independently by Robert Connolly from Matta Consulting who further
7595 noted that it allows a post-authentication heap overflow. Patch
7596 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7597 bugfix on 0.2.0.16-alpha.
7598 - Fix a compile warning when using the --enable-openbsd-malloc
7599 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7600 - During configure, detect when we're building with clang version
7601 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
7602 CFLAGS. clang doesn't support them yet.
7603 - When sending an HTTP/1.1 proxy request, include a Host header.
7604 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7605 - Fix a NULL-pointer dereference on a badly formed SETCIRCUITPURPOSE
7606 command. Found by mikeyc. Fixes bug 5796; bugfix on 0.2.2.9-alpha.
7607 - If we hit the error case where routerlist_insert() replaces an
7608 existing (old) server descriptor, make sure to remove that
7609 server descriptor from the old_routers list. Fix related to bug
7610 1776. Bugfix on 0.2.2.18-alpha.
7612 o Minor bugfixes (documentation and log messages):
7613 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
7614 Fixes bug 4856; bugfix on Tor 0.0.6.
7615 - Update "ClientOnly" man page entry to explain that there isn't
7616 really any point to messing with it. Resolves ticket 5005.
7617 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
7618 directory authority option (introduced in Tor 0.2.2.34).
7619 - Downgrade the "We're missing a certificate" message from notice
7620 to info: people kept mistaking it for a real problem, whereas it
7621 is seldom the problem even when we are failing to bootstrap. Fixes
7622 bug 5067; bugfix on 0.2.0.10-alpha.
7623 - Correctly spell "connect" in a log message on failure to create a
7624 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta.
7625 - Clarify the behavior of MaxCircuitDirtiness with hidden service
7626 circuits. Fixes issue 5259.
7629 - Directory authorities now reject versions of Tor older than
7630 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
7631 inclusive. These versions accounted for only a small fraction of
7632 the Tor network, and have numerous known security issues. Resolves
7634 - Update to the May 1 2012 Maxmind GeoLite Country database.
7637 - When sending or relaying a RELAY_EARLY cell, we used to convert
7638 it to a RELAY cell if the connection was using the v1 link
7639 protocol. This was a workaround for older versions of Tor, which
7640 didn't handle RELAY_EARLY cells properly. Now that all supported
7641 versions can handle RELAY_EARLY cells, and now that we're enforcing
7642 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
7643 remove this workaround. Addresses bug 4786.
7646 Changes in version 0.2.3.15-alpha - 2012-04-30
7647 Tor 0.2.3.15-alpha fixes a variety of smaller bugs, including making
7648 the development branch build on Windows again.
7650 o Minor bugfixes (on 0.2.2.x and earlier):
7651 - Make sure that there are no unhandled pending TLS errors before
7652 reading from a TLS stream. We had checks in 0.1.0.3-rc, but
7653 lost them in 0.1.0.5-rc when we refactored read_to_buf_tls().
7654 Bugfix on 0.1.0.5-rc; fixes bug 4528.
7655 - Fix an assert that directory authorities could trigger on sighup
7656 during some configuration state transitions. We now don't treat
7657 it as a fatal error when the new descriptor we just generated in
7658 init_keys() isn't accepted. Fixes bug 4438; bugfix on 0.2.1.9-alpha.
7659 - After we pick a directory mirror, we would refuse to use it if
7660 it's in our ExcludeExitNodes list, resulting in mysterious failures
7661 to bootstrap for people who just wanted to avoid exiting from
7662 certain locations. Fixes bug 5623; bugfix on 0.2.2.25-alpha.
7663 - When building with --enable-static-tor on OpenBSD, do not
7664 erroneously attempt to link -lrt. Fixes bug 5103.
7666 o Minor bugfixes (on 0.2.3.x):
7667 - When Tor is built with kernel headers from a recent (last few
7668 years) Linux kernel, do not fail to run on older (pre-2.6.28
7669 Linux kernels). Fixes bug 5112; bugfix on 0.2.3.1-alpha.
7670 - Fix cross-compilation issues with mingw. Bugfixes on 0.2.3.6-alpha
7672 - Fix compilation with miniupnpc version 1.6; patch from
7673 Anthony G. Basile. Fixes bug 5434; bugfix on 0.2.3.12-alpha.
7674 - Fix compilation with MSVC, which had defined MS_WINDOWS. Bugfix
7675 on 0.2.3.13-alpha; found and fixed by Gisle Vanem.
7676 - Fix compilation on platforms without unistd.h, or where environ
7677 is defined in stdlib.h. Fixes bug 5704; bugfix on 0.2.3.13-alpha.
7680 - Directory authorities are now a little more lenient at accepting
7681 older router descriptors, or newer router descriptors that don't
7682 make big changes. This should help ameliorate past and future
7683 issues where routers think they have uploaded valid descriptors,
7684 but the authorities don't think so. Fix for ticket 2479.
7685 - Make the code that clients use to detect an address change be
7686 IPv6-aware, so that it won't fill clients' logs with error
7687 messages when trying to get the IPv4 address of an IPv6
7688 connection. Implements ticket 5537.
7691 - Remove the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays option;
7692 authorities needed to use it for a while to keep the network working
7693 as people upgraded to 0.2.1.31, 0.2.2.34, or 0.2.3.6-alpha, but
7694 that was six months ago. As of now, it should no longer be needed
7698 Changes in version 0.2.3.14-alpha - 2012-04-23
7699 Tor 0.2.3.14-alpha fixes yet more bugs to get us closer to a release
7700 candidate. It also dramatically speeds up AES: fast relays should
7701 consider switching to the newer OpenSSL library.
7703 o Directory authority changes:
7704 - Change IP address for ides (v3 directory authority), and rename
7708 - Avoid logging uninitialized data when unable to decode a hidden
7709 service descriptor cookie. Fixes bug 5647; bugfix on 0.2.1.5-alpha.
7710 - Avoid a client-side assertion failure when receiving an INTRODUCE2
7711 cell on a general purpose circuit. Fixes bug 5644; bugfix on
7713 - If authorities are unable to get a v2 consensus document from other
7714 directory authorities, they no longer fall back to fetching
7715 them from regular directory caches. Fixes bug 5635; bugfix on
7716 0.2.2.26-beta, where routers stopped downloading v2 consensus
7718 - When we start a Tor client with a normal consensus already cached,
7719 be willing to download a microdescriptor consensus. Fixes bug 4011;
7720 fix on 0.2.3.1-alpha.
7722 o Major features (performance):
7723 - When built to use OpenSSL 1.0.1, and built for an x86 or x86_64
7724 instruction set, take advantage of OpenSSL's AESNI, bitsliced, or
7725 vectorized AES implementations as appropriate. These can be much,
7726 much faster than other AES implementations.
7728 o Minor bugfixes (0.2.2.x and earlier):
7729 - Don't launch more than 10 service-side introduction-point circuits
7730 for a hidden service in five minutes. Previously, we would consider
7731 launching more introduction-point circuits if at least one second
7732 had passed without any introduction-point circuits failing. Fixes
7733 bug 4607; bugfix on 0.0.7pre1.
7734 - Change the BridgePassword feature (part of the "bridge community"
7735 design, which is not yet implemented) to use a time-independent
7736 comparison. The old behavior might have allowed an adversary
7737 to use timing to guess the BridgePassword value. Fixes bug 5543;
7738 bugfix on 0.2.0.14-alpha.
7739 - Enforce correct return behavior of tor_vsscanf() when the '%%'
7740 pattern is used. Fixes bug 5558. Bugfix on 0.2.1.13.
7741 - When sending an HTTP/1.1 proxy request, include a Host header.
7742 Fixes bug 5593; bugfix on 0.2.2.1-alpha.
7743 - Don't log that we have "decided to publish new relay descriptor"
7744 unless we are actually publishing a descriptor. Fixes bug 3942;
7745 bugfix on 0.2.2.28-beta.
7747 o Minor bugfixes (0.2.3.x):
7748 - Fix a bug where a bridge authority crashes (on a failed assert)
7749 if it has seen no directory requests when it's time to write
7750 statistics to disk. Fixes bug 5508. Bugfix on 0.2.3.6-alpha.
7751 - Fix bug stomping on ORPort option NoListen and ignoring option
7752 NoAdvertise. Fixes bug 5151; bugfix on 0.2.3.9-alpha.
7753 - In the testsuite, provide a large enough buffer in the tor_sscanf
7754 unit test. Otherwise we'd overrun that buffer and crash during
7755 the unit tests. Found by weasel. Fixes bug 5449; bugfix on
7757 - Make sure we create the keys directory if it doesn't exist and we're
7758 about to store the dynamic Diffie-Hellman parameters. Fixes bug
7759 5572; bugfix on 0.2.3.13-alpha.
7760 - Fix a small memory leak when trying to decode incorrect base16
7761 authenticator during SAFECOOKIE authentication. Found by
7762 Coverity Scan. Fixes CID 507. Bugfix on 0.2.3.13-alpha.
7765 - Add more information to a log statement that might help track down
7766 bug 4091. If you're seeing "Bug: tor_addr_is_internal() called with a
7767 non-IP address" messages (or any Bug messages, for that matter!),
7768 please let us know about it.
7769 - Relays now understand an IPv6 address when they get one from a
7770 directory server. Resolves ticket 4875.
7771 - Resolve IPv6 addresses in bridge and entry statistics to country
7772 code "??" which means we at least count them. Resolves ticket 5053;
7773 improves on 0.2.3.9-alpha.
7774 - Update to the April 3 2012 Maxmind GeoLite Country database.
7775 - Begin a doc/state-contents.txt file to explain the contents of
7776 the Tor state file. Fixes bug 2987.
7778 o Default torrc changes:
7779 - Stop listing "socksport 9050" in torrc.sample. We open a socks
7780 port on 9050 by default anyway, so this should not change anything
7782 - Stop mentioning the deprecated *ListenAddress options in
7783 torrc.sample. Fixes bug 5438.
7784 - Document unit of bandwidth related options in sample torrc.
7788 - The "torify" script no longer supports the "tsocks" socksifier
7789 tool, since tsocks doesn't support DNS and UDP right for Tor.
7790 Everyone should be using torsocks instead. Fixes bugs 3530 and
7791 5180. Based on a patch by "ugh".
7794 - Change the symmetric cipher interface so that creating and
7795 initializing a stream cipher are no longer separate functions.
7796 - Remove all internal support for unpadded RSA. We never used it, and
7797 it would be a bad idea to start.
7800 Changes in version 0.2.3.13-alpha - 2012-03-26
7801 Tor 0.2.3.13-alpha fixes a variety of stability and correctness bugs
7802 in managed pluggable transports, as well as providing other cleanups
7803 that get us closer to a release candidate.
7805 o Directory authority changes:
7806 - Change IP address for maatuska (v3 directory authority).
7809 - Provide controllers with a safer way to implement the cookie
7810 authentication mechanism. With the old method, if another locally
7811 running program could convince a controller that it was the Tor
7812 process, then that program could trick the controller into telling
7813 it the contents of an arbitrary 32-byte file. The new "SAFECOOKIE"
7814 authentication method uses a challenge-response approach to prevent
7815 this attack. Fixes bug 5185, implements proposal 193.
7816 - Never use a bridge or a controller-supplied node as an exit, even
7817 if its exit policy allows it. Found by wanoskarnet. Fixes bug
7818 5342. Bugfix on 0.1.1.15-rc (for controller-purpose descriptors)
7819 and 0.2.0.3-alpha (for bridge-purpose descriptors).
7820 - Only build circuits if we have a sufficient threshold of the total
7821 descriptors that are marked in the consensus with the "Exit"
7822 flag. This mitigates an attack proposed by wanoskarnet, in which
7823 all of a client's bridges collude to restrict the exit nodes that
7824 the client knows about. Fixes bug 5343.
7826 o Major bugfixes (on Tor 0.2.3.x):
7827 - Avoid an assert when managed proxies like obfsproxy are configured,
7828 and we receive HUP signals or setconf attempts too rapidly. This
7829 situation happens most commonly when Vidalia tries to attach to
7830 Tor or tries to configure the Tor it's attached to. Fixes bug 5084;
7831 bugfix on 0.2.3.6-alpha.
7832 - Fix a relay-side pluggable transports bug where managed proxies were
7833 unreachable from the Internet, because Tor asked them to bind on
7834 localhost. Fixes bug 4725; bugfix on 0.2.3.9-alpha.
7835 - Stop discarding command-line arguments when TestingTorNetwork
7836 is set. Discovered by Kevin Bauer. Fixes bug 5373; bugfix on
7837 0.2.3.9-alpha, where task 4552 added support for two layers of
7839 - Resume allowing the unit tests to run in gdb. This was accidentally
7840 made impossible when the DisableDebuggerAttachment option was
7841 introduced. Fixes bug 5448; bugfix on 0.2.3.9-alpha.
7842 - Resume building with nat-pmp support. Fixes bug 4955; bugfix on
7843 0.2.3.11-alpha. Reported by Anthony G. Basile.
7845 o Minor bugfixes (on 0.2.2.x and earlier):
7846 - Ensure we don't cannibalize circuits that are longer than three hops
7847 already, so we don't end up making circuits with 5 or more
7848 hops. Patch contributed by wanoskarnet. Fixes bug 5231; bugfix on
7849 0.1.0.1-rc which introduced cannibalization.
7850 - Detect and reject certain misformed escape sequences in
7851 configuration values. Previously, these values would cause us
7852 to crash if received in a torrc file or over an authenticated
7853 control port. Bug found by Esteban Manchado Velázquez, and
7854 independently by Robert Connolly from Matta Consulting who further
7855 noted that it allows a post-authentication heap overflow. Patch
7856 by Alexander Schrijver. Fixes bugs 5090 and 5402 (CVE 2012-1668);
7857 bugfix on 0.2.0.16-alpha.
7858 - Fix a compile warning when using the --enable-openbsd-malloc
7859 configure option. Fixes bug 5340; bugfix on 0.2.0.20-rc.
7860 - Directory caches no longer refuse to clean out descriptors because
7861 of missing v2 networkstatus documents, unless they're configured
7862 to retrieve v2 networkstatus documents. Fixes bug 4838; bugfix on
7863 0.2.2.26-beta. Patch by Daniel Bryg.
7864 - Update to the latest version of the tinytest unit testing framework.
7865 This includes a couple of bugfixes that can be relevant for
7866 running forked unit tests on Windows, and removes all reserved
7869 o Minor bugfixes (on 0.2.3.x):
7870 - On a failed pipe() call, don't leak file descriptors. Fixes bug
7871 4296; bugfix on 0.2.3.1-alpha.
7872 - Spec conformance: on a v3 handshake, do not send a NETINFO cell
7873 until after we have received a CERTS cell. Fixes bug 4361; bugfix
7874 on 0.2.3.6-alpha. Patch by "frosty".
7875 - When binding to an IPv6 address, set the IPV6_V6ONLY socket
7876 option, so that the IP stack doesn't decide to use it for IPv4
7877 too. Fixes bug 4760; bugfix on 0.2.3.9-alpha.
7878 - Ensure that variables set in Tor's environment cannot override
7879 environment variables that Tor passes to a managed
7880 pluggable-transport proxy. Previously, Tor would pass every
7881 variable in its environment to managed proxies along with the new
7882 ones, in such a way that on many operating systems, the inherited
7883 environment variables would override those which Tor tried to
7884 explicitly set. Bugfix on 0.2.3.12-alpha for most Unixoid systems;
7885 bugfix on 0.2.3.9-alpha for Windows.
7888 - A wide variety of new unit tests by Esteban Manchado Velázquez.
7889 - Shorten links in the tor-exit-notice file. Patch by Christian Kujau.
7890 - Update to the March 6 2012 Maxmind GeoLite Country database.
7893 Changes in version 0.2.3.12-alpha - 2012-02-13
7894 Tor 0.2.3.12-alpha lets fast exit relays scale better, allows clients
7895 to use bridges that run Tor 0.2.2.x, and resolves several big bugs
7896 when Tor is configured to use a pluggable transport like obfsproxy.
7899 - Fix builds when the path to sed, openssl, or sha1sum contains
7900 spaces, which is pretty common on Windows. Fixes bug 5065; bugfix
7902 - Set the SO_REUSEADDR socket option before we call bind() on outgoing
7903 connections. This change should allow busy exit relays to stop
7904 running out of available sockets as quickly. Fixes bug 4950;
7905 bugfix on 0.2.2.26-beta.
7906 - Allow 0.2.3.x clients to use 0.2.2.x bridges. Previously the client
7907 would ask the bridge for microdescriptors, which are only supported
7908 in 0.2.3.x, and then fail to bootstrap when it didn't get the
7909 answers it wanted. Fixes bug 4013; bugfix on 0.2.3.2-alpha.
7910 - Properly set up obfsproxy's environment when in managed mode. The
7911 Tor Browser Bundle needs LD_LIBRARY_PATH to be passed to obfsproxy,
7912 and when you run your Tor as a daemon, there's no HOME. Fixes bugs
7913 5076 and 5082; bugfix on 0.2.3.6-alpha.
7916 - Use the dead_strip option when building Tor on OS X. This reduces
7917 binary size by almost 19% when linking openssl and libevent
7918 statically, which we do for Tor Browser Bundle.
7919 - Fix broken URLs in the sample torrc file, and tell readers about
7920 the OutboundBindAddress, ExitPolicyRejectPrivate, and
7921 PublishServerDescriptor options. Addresses bug 4652.
7922 - Update to the February 7 2012 Maxmind GeoLite Country database.
7925 - Downgrade the "We're missing a certificate" message from notice
7926 to info: people kept mistaking it for a real problem, whereas it
7927 is seldom the problem even when we are failing to bootstrap. Fixes
7928 bug 5067; bugfix on 0.2.0.10-alpha.
7929 - Don't put "TOR_PT_EXTENDED_SERVER_PORT=127.0.0.1:4200" in a
7930 managed pluggable transport server proxy's environment.
7931 Previously, we would put it there, even though Tor doesn't
7932 implement an 'extended server port' yet, and even though Tor
7933 almost certainly isn't listening at that address. For now, we set
7934 it to an empty string to avoid crashing older obfsproxies. Bugfix
7936 - Log the heartbeat message every HeartbeatPeriod seconds, not every
7937 HeartbeatPeriod + 1 seconds. Fixes bug 4942; bugfix on
7938 0.2.3.1-alpha. Bug reported by Scott Bennett.
7939 - Calculate absolute paths correctly on Windows. Fixes bug 4973;
7940 bugfix on 0.2.3.11-alpha.
7941 - Update "ClientOnly" man page entry to explain that there isn't
7942 really any point to messing with it. Resolves ticket 5005.
7943 - Use the correct CVE number for CVE-2011-4576 in our comments and
7944 log messages. Found by "fermenthor". Resolves bug 5066; bugfix on
7947 o Code simplifications and refactoring:
7948 - Use the _WIN32 macro throughout our code to detect Windows.
7949 (Previously we had used the obsolete 'WIN32' and the idiosyncratic
7953 Changes in version 0.2.3.11-alpha - 2012-01-22
7954 Tor 0.2.3.11-alpha marks feature-freeze for the 0.2.3 tree. It deploys
7955 the last step of the plan to limit maximum circuit length, includes
7956 a wide variety of hidden service performance and correctness fixes,
7957 works around an OpenSSL security flaw if your distro is too stubborn
7958 to upgrade, and fixes a bunch of smaller issues.
7961 - Now that Tor 0.2.0.x is completely deprecated, enable the final
7962 part of "Proposal 110: Avoiding infinite length circuits" by
7963 refusing all circuit-extend requests that do not use a relay_early
7964 cell. This change helps Tor resist a class of denial-of-service
7965 attacks by limiting the maximum circuit length.
7966 - Adjust the number of introduction points that a hidden service
7967 will try to maintain based on how long its introduction points
7968 remain in use and how many introductions they handle. Fixes
7970 - Try to use system facilities for enumerating local interface
7971 addresses, before falling back to our old approach (which was
7972 binding a UDP socket, and calling getsockname() on it). That
7973 approach was scaring OS X users whose draconian firewall
7974 software warned about binding to UDP sockets, regardless of
7975 whether packets were sent. Now we try to use getifaddrs(),
7976 SIOCGIFCONF, or GetAdaptersAddresses(), depending on what the
7977 system supports. Resolves ticket 1827.
7979 o Major security workaround:
7980 - When building or running with any version of OpenSSL earlier
7981 than 0.9.8s or 1.0.0f, disable SSLv3 support. These OpenSSL
7982 versions have a bug (CVE-2011-4576) in which their block cipher
7983 padding includes uninitialized data, potentially leaking sensitive
7984 information to any peer with whom they make a SSLv3 connection. Tor
7985 does not use SSL v3 by default, but a hostile client or server
7986 could force an SSLv3 connection in order to gain information that
7987 they shouldn't have been able to get. The best solution here is to
7988 upgrade to OpenSSL 0.9.8s or 1.0.0f (or later). But when building
7989 or running with a non-upgraded OpenSSL, we disable SSLv3 entirely
7990 to make sure that the bug can't happen.
7993 - Fix the SOCKET_OK test that we use to tell when socket
7994 creation fails so that it works on Win64. Fixes part of bug 4533;
7995 bugfix on 0.2.2.29-beta. Bug found by wanoskarnet.
7996 - Correct our replacements for the timeradd() and timersub() functions
7997 on platforms that lack them (for example, Windows). The timersub()
7998 function is used when expiring circuits, while timeradd() is
7999 currently unused. Bug report and patch by Vektor. Fixes bug 4778;
8000 bugfix on 0.2.2.24-alpha and 0.2.3.1-alpha.
8001 - Do not use OpenSSL 1.0.0's counter mode: it has a critical bug
8002 that was fixed in OpenSSL 1.0.0a. We test for the counter mode
8003 bug at runtime, not compile time, because some distributions hack
8004 their OpenSSL to mis-report its version. Fixes bug 4779; bugfix
8005 on 0.2.3.9-alpha. Found by Pascal.
8007 o Minor features (controller):
8008 - Use absolute path names when reporting the torrc filename in the
8009 control protocol, so a controller can more easily find the torrc
8010 file. Resolves bug 1101.
8011 - Extend the control protocol to report flags that control a circuit's
8012 path selection in CIRC events and in replies to 'GETINFO
8013 circuit-status'. Implements part of ticket 2411.
8014 - Extend the control protocol to report the hidden service address
8015 and current state of a hidden-service-related circuit in CIRC
8016 events and in replies to 'GETINFO circuit-status'. Implements part
8018 - When reporting the path to the cookie file to the controller,
8019 give an absolute path. Resolves ticket 4881.
8020 - Allow controllers to request an event notification whenever a
8021 circuit is cannibalized or its purpose is changed. Implements
8022 part of ticket 3457.
8023 - Include the creation time of a circuit in CIRC and CIRC2
8024 control-port events and the list produced by the 'GETINFO
8025 circuit-status' control-port command.
8027 o Minor features (directory authorities):
8028 - Directory authorities now reject versions of Tor older than
8029 0.2.1.30, and Tor versions between 0.2.2.1-alpha and 0.2.2.20-alpha
8030 inclusive. These versions accounted for only a small fraction of
8031 the Tor network, and have numerous known security issues. Resolves
8033 - Authority operators can now vote for all relays in a given
8034 set of countries to be BadDir/BadExit/Invalid/Rejected.
8035 - Provide two consensus parameters (FastFlagMinThreshold and
8036 FastFlagMaxThreshold) to control the range of allowable bandwidths
8037 for the Fast directory flag. These allow authorities to run
8038 experiments on appropriate requirements for being a "Fast" node.
8039 The AuthDirFastGuarantee config value still applies. Implements
8041 - Document the GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays
8042 directory authority option (introduced in Tor 0.2.2.34).
8044 o Minor features (other):
8045 - Don't disable the DirPort when we cannot exceed our AccountingMax
8046 limit during this interval because the effective bandwidthrate is
8047 low enough. This is useful in a situation where AccountMax is only
8048 used as an additional safeguard or to provide statistics.
8049 - Prepend an informative header to generated dynamic_dh_params files.
8050 - If EntryNodes are given, but UseEntryGuards is set to 0, warn that
8051 EntryNodes will have no effect. Resolves issue 2571.
8052 - Log more useful messages when we fail to disable debugger
8054 - Log which authority we're missing votes from when we go to fetch
8055 them from the other auths.
8056 - Log (at debug level) whenever a circuit's purpose is changed.
8057 - Add missing documentation for the MaxClientCircuitsPending,
8058 UseMicrodescriptors, UserspaceIOCPBuffers, and
8059 _UseFilteringSSLBufferevents options, all introduced during
8061 - Update to the January 3 2012 Maxmind GeoLite Country database.
8063 o Minor bugfixes (hidden services):
8064 - Don't close hidden service client circuits which have almost
8065 finished connecting to their destination when they reach
8066 the normal circuit-build timeout. Previously, we would close
8067 introduction circuits which are waiting for an acknowledgement
8068 from the introduction point, and rendezvous circuits which have
8069 been specified in an INTRODUCE1 cell sent to a hidden service,
8070 after the normal CBT. Now, we mark them as 'timed out', and launch
8071 another rendezvous attempt in parallel. This behavior change can
8072 be disabled using the new CloseHSClientCircuitsImmediatelyOnTimeout
8073 option. Fixes part of bug 1297; bugfix on 0.2.2.2-alpha.
8074 - Don't close hidden-service-side rendezvous circuits when they
8075 reach the normal circuit-build timeout. This behavior change can
8076 be disabled using the new
8077 CloseHSServiceRendCircuitsImmediatelyOnTimeout option. Fixes the
8078 remaining part of bug 1297; bugfix on 0.2.2.2-alpha.
8079 - Make sure we never mark the wrong rendezvous circuit as having
8080 had its introduction cell acknowleged by the introduction-point
8081 relay. Previously, when we received an INTRODUCE_ACK cell on a
8082 client-side hidden-service introduction circuit, we might have
8083 marked a rendezvous circuit other than the one we specified in
8084 the INTRODUCE1 cell as INTRO_ACKED, which would have produced
8085 a warning message and interfered with the hidden service
8086 connection-establishment process. Fixes bug 4759; bugfix on
8087 0.2.3.3-alpha, when we added the stream-isolation feature which
8088 might cause Tor to open multiple rendezvous circuits for the same
8090 - Don't trigger an assertion failure when we mark a new client-side
8091 hidden-service introduction circuit for close during the process
8092 of creating it. Fixes bug 4796; bugfix on 0.2.3.6-alpha. Reported
8095 o Minor bugfixes (log messages):
8096 - Correctly spell "connect" in a log message on failure to create a
8097 controlsocket. Fixes bug 4803; bugfix on 0.2.2.26-beta and
8099 - Fix a typo in a log message in rend_service_rendezvous_has_opened().
8100 Fixes bug 4856; bugfix on Tor 0.0.6.
8101 - Fix the log message describing how we work around discovering
8102 that our version is the ill-fated OpenSSL 0.9.8l. Fixes bug
8103 4837; bugfix on 0.2.2.9-alpha.
8104 - When logging about a disallowed .exit name, do not also call it
8105 an "invalid onion address". Fixes bug 3325; bugfix on 0.2.2.9-alpha.
8107 o Minor bugfixes (build fixes):
8108 - During configure, detect when we're building with clang version
8109 3.0 or lower and disable the -Wnormalized=id and -Woverride-init
8110 CFLAGS. clang doesn't support them yet.
8111 - During configure, search for library containing cos function as
8112 libm lives in libcore on some platforms (BeOS/Haiku). Linking
8113 against libm was hard-coded before. Fixes the first part of bug
8114 4727; bugfix on 0.2.2.2-alpha. Patch and analysis by Martin Hebnes
8116 - Detect attempts to build Tor on (as yet hypothetical) versions
8117 of Windows where sizeof(intptr_t) != sizeof(SOCKET). Partial
8118 fix for bug 4533. Bugfix on 0.2.2.28-beta.
8119 - Preprocessor directives should not be put inside the arguments
8120 of a macro. This would break compilation with GCC releases prior
8121 to version 3.3. We would never recommend such an old GCC version,
8122 but it is apparently required for binary compatibility on some
8123 platforms (namely, certain builds of Haiku). Fixes the other part
8124 of bug 4727; bugfix on 0.2.3.3-alpha. Patch and analysis by Martin
8127 o Minor bugfixes (other):
8128 - Older Linux kernels erroneously respond to strange nmap behavior
8129 by having accept() return successfully with a zero-length
8130 socket. When this happens, just close the connection. Previously,
8131 we would try harder to learn the remote address: but there was
8132 no such remote address to learn, and our method for trying to
8133 learn it was incorrect. Fixes bugs 1240, 4745, and 4747. Bugfix
8134 on 0.1.0.3-rc. Reported and diagnosed by "r1eo".
8135 - Fix null-pointer access that could occur if TLS allocation failed.
8136 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un". This was
8137 erroneously listed as fixed in 0.2.3.9-alpha, but the fix had
8138 accidentally been reverted.
8139 - Fix our implementation of crypto_random_hostname() so it can't
8140 overflow on ridiculously large inputs. (No Tor version has ever
8141 provided this kind of bad inputs, but let's be correct in depth.)
8142 Fixes bug 4413; bugfix on 0.2.2.9-alpha. Fix by Stephen Palmateer.
8143 - Find more places in the code that should have been testing for
8144 invalid sockets using the SOCKET_OK macro. Required for a fix
8145 for bug 4533. Bugfix on 0.2.2.28-beta.
8146 - Fix an assertion failure when, while running with bufferevents, a
8147 connection finishes connecting after it is marked for close, but
8148 before it is closed. Fixes bug 4697; bugfix on 0.2.3.1-alpha.
8149 - test_util_spawn_background_ok() hardcoded the expected value
8150 for ENOENT to 2. This isn't portable as error numbers are
8151 platform specific, and particularly the hurd has ENOENT at
8152 0x40000002. Construct expected string at runtime, using the correct
8153 value for ENOENT. Fixes bug 4733; bugfix on 0.2.3.1-alpha.
8154 - Reject attempts to disable DisableDebuggerAttachment while Tor is
8155 running. Fixes bug 4650; bugfix on 0.2.3.9-alpha.
8156 - Use an appropriate-width type for sockets in tor-fw-helper on
8157 win64. Fixes bug 1983 at last. Bugfix on 0.2.3.9-alpha.
8160 - When sending or relaying a RELAY_EARLY cell, we used to convert
8161 it to a RELAY cell if the connection was using the v1 link
8162 protocol. This was a workaround for older versions of Tor, which
8163 didn't handle RELAY_EARLY cells properly. Now that all supported
8164 versions can handle RELAY_EARLY cells, and now that we're enforcing
8165 the "no RELAY_EXTEND commands except in RELAY_EARLY cells" rule,
8166 remove this workaround. Addresses bug 4786.
8168 o Code simplifications and refactoring:
8169 - Use OpenSSL's built-in SSL_state_string_long() instead of our
8170 own homebrewed ssl_state_to_string() replacement. Patch from
8171 Emile Snyder. Fixes bug 4653.
8172 - Use macros to indicate OpenSSL versions, so we don't need to worry
8173 about accidental hexadecimal bit shifts.
8174 - Remove some workaround code for OpenSSL 0.9.6 (which is no longer
8176 - Convert more instances of tor_snprintf+tor_strdup into tor_asprintf.
8177 - Use the smartlist_add_asprintf() alias more consistently.
8178 - Use a TOR_INVALID_SOCKET macro when initializing a socket to an
8179 invalid value, rather than just -1.
8180 - Rename a handful of old identifiers, mostly related to crypto
8181 structures and crypto functions. By convention, our "create an
8182 object" functions are called "type_new()", our "free an object"
8183 functions are called "type_free()", and our types indicate that
8184 they are types only with a final "_t". But a handful of older
8185 types and functions broke these rules, with function names like
8186 "type_create" or "subsystem_op_type", or with type names like
8190 Changes in version 0.2.3.10-alpha - 2011-12-16
8191 Tor 0.2.3.10-alpha fixes a critical heap-overflow security issue in
8192 Tor's buffers code. Absolutely everybody should upgrade.
8194 The bug relied on an incorrect calculation when making data continuous
8195 in one of our IO buffers, if the first chunk of the buffer was
8196 misaligned by just the wrong amount. The miscalculation would allow an
8197 attacker to overflow a piece of heap-allocated memory. To mount this
8198 attack, the attacker would need to either open a SOCKS connection to
8199 Tor's SocksPort (usually restricted to localhost), or target a Tor
8200 instance configured to make its connections through a SOCKS proxy
8201 (which Tor does not do by default).
8203 Good security practice requires that all heap-overflow bugs should be
8204 presumed to be exploitable until proven otherwise, so we are treating
8205 this as a potential code execution attack. Please upgrade immediately!
8206 This bug does not affect bufferevents-based builds of Tor. Special
8207 thanks to "Vektor" for reporting this issue to us!
8209 This release also contains a few minor bugfixes for issues discovered
8213 - Fix a heap overflow bug that could occur when trying to pull
8214 data into the first chunk of a buffer, when that chunk had
8215 already had some data drained from it. Fixes CVE-2011-2778;
8216 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8219 - If we can't attach streams to a rendezvous circuit when we
8220 finish connecting to a hidden service, clear the rendezvous
8221 circuit's stream-isolation state and try to attach streams
8222 again. Previously, we cleared rendezvous circuits' isolation
8223 state either too early (if they were freshly built) or not at all
8224 (if they had been built earlier and were cannibalized). Bugfix on
8225 0.2.3.3-alpha; fixes bug 4655.
8226 - Fix compilation of the libnatpmp helper on non-Windows. Bugfix on
8227 0.2.3.9-alpha; fixes bug 4691. Reported by Anthony G. Basile.
8228 - Fix an assertion failure when a relay with accounting enabled
8229 starts up while dormant. Fixes bug 4702; bugfix on 0.2.3.9-alpha.
8232 - Update to the December 6 2011 Maxmind GeoLite Country database.
8235 Changes in version 0.2.2.35 - 2011-12-16
8236 Tor 0.2.2.35 fixes a critical heap-overflow security issue in Tor's
8237 buffers code. Absolutely everybody should upgrade.
8239 The bug relied on an incorrect calculation when making data continuous
8240 in one of our IO buffers, if the first chunk of the buffer was
8241 misaligned by just the wrong amount. The miscalculation would allow an
8242 attacker to overflow a piece of heap-allocated memory. To mount this
8243 attack, the attacker would need to either open a SOCKS connection to
8244 Tor's SocksPort (usually restricted to localhost), or target a Tor
8245 instance configured to make its connections through a SOCKS proxy
8246 (which Tor does not do by default).
8248 Good security practice requires that all heap-overflow bugs should be
8249 presumed to be exploitable until proven otherwise, so we are treating
8250 this as a potential code execution attack. Please upgrade immediately!
8251 This bug does not affect bufferevents-based builds of Tor. Special
8252 thanks to "Vektor" for reporting this issue to us!
8254 Tor 0.2.2.35 also fixes several bugs in previous versions, including
8255 crash bugs for unusual configurations, and a long-term bug that
8256 would prevent Tor from starting on Windows machines with draconian
8259 With this release, we remind everyone that 0.2.0.x has reached its
8260 formal end-of-life. Those Tor versions have many known flaws, and
8261 nobody should be using them. You should upgrade -- ideally to the
8262 0.2.2.x series. If you're using a Linux or BSD and its packages are
8263 obsolete, stop using those packages and upgrade anyway.
8265 The Tor 0.2.1.x series is also approaching its end-of-life: it will no
8266 longer receive support after some time in early 2012.
8269 - Fix a heap overflow bug that could occur when trying to pull
8270 data into the first chunk of a buffer, when that chunk had
8271 already had some data drained from it. Fixes CVE-2011-2778;
8272 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8273 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8274 that it doesn't attempt to allocate a socketpair. This could cause
8275 some problems on Windows systems with overzealous firewalls. Fix for
8276 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8278 - If we mark an OR connection for close based on a cell we process,
8279 don't process any further cells on it. We already avoid further
8280 reads on marked-for-close connections, but now we also discard the
8281 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8282 which was the first version where we might mark a connection for
8283 close based on processing a cell on it.
8284 - Correctly sanity-check that we don't underflow on a memory
8285 allocation (and then assert) for hidden service introduction
8286 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8287 bugfix on 0.2.1.5-alpha.
8288 - Fix a memory leak when we check whether a hidden service
8289 descriptor has any usable introduction points left. Fixes bug
8290 4424. Bugfix on 0.2.2.25-alpha.
8291 - Don't crash when we're running as a relay and don't have a GeoIP
8292 file. Bugfix on 0.2.2.34; fixes bug 4340. This backports a fix
8293 we've had in the 0.2.3.x branch already.
8294 - When running as a client, do not print a misleading (and plain
8295 wrong) log message that we're collecting "directory request"
8296 statistics: clients don't collect statistics. Also don't create a
8297 useless (because empty) stats file in the stats/ directory. Fixes
8298 bug 4353; bugfix on 0.2.2.34.
8301 - Detect failure to initialize Libevent. This fix provides better
8302 detection for future instances of bug 4457.
8303 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8304 function. This was eating up hideously large amounts of time on some
8305 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8306 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8307 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8309 - Don't warn about unused log_mutex in log.c when building with
8310 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8311 0.1.0.6-rc which introduced --disable-threads.
8312 - When configuring, starting, or stopping an NT service, stop
8313 immediately after the service configuration attempt has succeeded
8314 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8315 - When sending a NETINFO cell, include the original address
8316 received for the other side, not its canonical address. Found
8317 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8318 - Fix a typo in a hibernation-related log message. Fixes bug 4331;
8319 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8320 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8321 occurred when a client tried to fetch a descriptor for a bridge
8322 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8323 - Backport fixes for a pair of compilation warnings on Windows.
8324 Fixes bug 4521; bugfix on 0.2.2.28-beta and on 0.2.2.29-beta.
8325 - If we had ever tried to call tor_addr_to_str on an address of
8326 unknown type, we would have done a strdup on an uninitialized
8327 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8328 Reported by "troll_un".
8329 - Correctly detect and handle transient lookup failures from
8330 tor_addr_lookup. Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8331 Reported by "troll_un".
8332 - Fix null-pointer access that could occur if TLS allocation failed.
8333 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8334 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8335 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8338 - Add two new config options for directory authorities:
8339 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8340 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8341 that is always sufficient to satisfy the bandwidth requirement for
8342 the Guard flag. Now it will be easier for researchers to simulate
8343 Tor networks with different values. Resolves ticket 4484.
8344 - When Tor ignores a hidden service specified in its configuration,
8345 include the hidden service's directory in the warning message.
8346 Previously, we would only tell the user that some hidden service
8347 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8348 - Update to the December 6 2011 Maxmind GeoLite Country database.
8350 o Packaging changes:
8351 - Make it easier to automate expert package builds on Windows,
8352 by removing an absolute path from makensis.exe command.
8355 Changes in version 0.2.1.32 - 2011-12-16
8356 Tor 0.2.1.32 backports important security and privacy fixes for
8357 oldstable. This release is intended only for package maintainers and
8358 others who cannot use the 0.2.2 stable series. All others should be
8359 using Tor 0.2.2.x or newer.
8361 The Tor 0.2.1.x series will reach formal end-of-life some time in
8362 early 2012; we will stop releasing patches for it then.
8364 o Major bugfixes (also included in 0.2.2.x):
8365 - Correctly sanity-check that we don't underflow on a memory
8366 allocation (and then assert) for hidden service introduction
8367 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8368 bugfix on 0.2.1.5-alpha.
8369 - Fix a heap overflow bug that could occur when trying to pull
8370 data into the first chunk of a buffer, when that chunk had
8371 already had some data drained from it. Fixes CVE-2011-2778;
8372 bugfix on 0.2.0.16-alpha. Reported by "Vektor".
8375 - Update to the December 6 2011 Maxmind GeoLite Country database.
8378 Changes in version 0.2.3.9-alpha - 2011-12-08
8379 Tor 0.2.3.9-alpha introduces initial IPv6 support for bridges, adds
8380 a "DisableNetwork" security feature that bundles can use to avoid
8381 touching the network until bridges are configured, moves forward on
8382 the pluggable transport design, fixes a flaw in the hidden service
8383 design that unnecessarily prevented clients with wrong clocks from
8384 reaching hidden services, and fixes a wide variety of other issues.
8387 - Clients can now connect to private bridges over IPv6. Bridges
8388 still need at least one IPv4 address in order to connect to
8389 other relays. Note that we don't yet handle the case where the
8390 user has two bridge lines for the same bridge (one IPv4, one
8391 IPv6). Implements parts of proposal 186.
8392 - New "DisableNetwork" config option to prevent Tor from launching any
8393 connections or accepting any connections except on a control port.
8394 Bundles and controllers can set this option before letting Tor talk
8395 to the rest of the network, for example to prevent any connections
8396 to a non-bridge address. Packages like Orbot can also use this
8397 option to instruct Tor to save power when the network is off.
8398 - Clients and bridges can now be configured to use a separate
8399 "transport" proxy. This approach makes the censorship arms race
8400 easier by allowing bridges to use protocol obfuscation plugins. It
8401 implements the "managed proxy" part of proposal 180 (ticket 3472).
8402 - When using OpenSSL 1.0.0 or later, use OpenSSL's counter mode
8403 implementation. It makes AES_CTR about 7% faster than our old one
8404 (which was about 10% faster than the one OpenSSL used to provide).
8405 Resolves ticket 4526.
8406 - Add a "tor2web mode" for clients that want to connect to hidden
8407 services non-anonymously (and possibly more quickly). As a safety
8408 measure to try to keep users from turning this on without knowing
8409 what they are doing, tor2web mode must be explicitly enabled at
8410 compile time, and a copy of Tor compiled to run in tor2web mode
8411 cannot be used as a normal Tor client. Implements feature 2553.
8412 - Add experimental support for running on Windows with IOCP and no
8413 kernel-space socket buffers. This feature is controlled by a new
8414 "UserspaceIOCPBuffers" config option (off by default), which has
8415 no effect unless Tor has been built with support for bufferevents,
8416 is running on Windows, and has enabled IOCP. This may, in the long
8417 run, help solve or mitigate bug 98.
8418 - Use a more secure consensus parameter voting algorithm. Now at
8419 least three directory authorities or a majority of them must
8420 vote on a given parameter before it will be included in the
8421 consensus. Implements proposal 178.
8424 - Hidden services now ignore the timestamps on INTRODUCE2 cells.
8425 They used to check that the timestamp was within 30 minutes
8426 of their system clock, so they could cap the size of their
8427 replay-detection cache, but that approach unnecessarily refused
8428 service to clients with wrong clocks. Bugfix on 0.2.1.6-alpha, when
8429 the v3 intro-point protocol (the first one which sent a timestamp
8430 field in the INTRODUCE2 cell) was introduced; fixes bug 3460.
8431 - Only use the EVP interface when AES acceleration is enabled,
8432 to avoid a 5-7% performance regression. Resolves issue 4525;
8433 bugfix on 0.2.3.8-alpha.
8435 o Privacy/anonymity features (bridge detection):
8436 - Make bridge SSL certificates a bit more stealthy by using random
8437 serial numbers, in the same fashion as OpenSSL when generating
8438 self-signed certificates. Implements ticket 4584.
8439 - Introduce a new config option "DynamicDHGroups", enabled by
8440 default, which provides each bridge with a unique prime DH modulus
8441 to be used during SSL handshakes. This option attempts to help
8442 against censors who might use the Apache DH modulus as a static
8443 identifier for bridges. Addresses ticket 4548.
8445 o Minor features (new/different config options):
8446 - New configuration option "DisableDebuggerAttachment" (on by default)
8447 to prevent basic debugging attachment attempts by other processes.
8448 Supports Mac OS X and Gnu/Linux. Resolves ticket 3313.
8449 - Allow MapAddress directives to specify matches against super-domains,
8450 as in "MapAddress *.torproject.org *.torproject.org.torserver.exit".
8451 Implements issue 933.
8452 - Slightly change behavior of "list" options (that is, config
8453 options that can appear more than once) when they appear both in
8454 torrc and on the command line. Previously, the command-line options
8455 would be appended to the ones from torrc. Now, the command-line
8456 options override the torrc options entirely. This new behavior
8457 allows the user to override list options (like exit policies and
8458 ports to listen on) from the command line, rather than simply
8459 appending to the list.
8460 - You can get the old (appending) command-line behavior for "list"
8461 options by prefixing the option name with a "+".
8462 - You can remove all the values for a "list" option from the command
8463 line without adding any new ones by prefixing the option name
8465 - Add experimental support for a "defaults" torrc file to be parsed
8466 before the regular torrc. Torrc options override the defaults file's
8467 options in the same way that the command line overrides the torrc.
8468 The SAVECONF controller command saves only those options which
8469 differ between the current configuration and the defaults file. HUP
8470 reloads both files. (Note: This is an experimental feature; its
8471 behavior will probably be refined in future 0.2.3.x-alpha versions
8472 to better meet packagers' needs.) Implements task 4552.
8475 - Try to make the introductory warning message that Tor prints on
8476 startup more useful for actually finding help and information.
8477 Resolves ticket 2474.
8478 - Running "make version" now displays the version of Tor that
8479 we're about to build. Idea from katmagic; resolves issue 4400.
8480 - Expire old or over-used hidden service introduction points.
8481 Required by fix for bug 3460.
8482 - Move the replay-detection cache for the RSA-encrypted parts of
8483 INTRODUCE2 cells to the introduction point data structures.
8484 Previously, we would use one replay-detection cache per hidden
8485 service. Required by fix for bug 3460.
8486 - Reduce the lifetime of elements of hidden services' Diffie-Hellman
8487 public key replay-detection cache from 60 minutes to 5 minutes. This
8488 replay-detection cache is now used only to detect multiple
8489 INTRODUCE2 cells specifying the same rendezvous point, so we can
8490 avoid launching multiple simultaneous attempts to connect to it.
8492 o Minor bugfixes (on Tor 0.2.2.x and earlier):
8493 - Resolve an integer overflow bug in smartlist_ensure_capacity().
8494 Fixes bug 4230; bugfix on Tor 0.1.0.1-rc. Based on a patch by
8496 - Fix a minor formatting issue in one of tor-gencert's error messages.
8498 - Prevent a false positive from the check-spaces script, by disabling
8499 the "whitespace between function name and (" check for functions
8501 - Fix a log message suggesting that people contact a non-existent
8502 email address. Fixes bug 3448.
8503 - Fix null-pointer access that could occur if TLS allocation failed.
8504 Fixes bug 4531; bugfix on 0.2.0.20-rc. Found by "troll_un".
8505 - Report a real bootstrap problem to the controller on router
8506 identity mismatch. Previously we just said "foo", which probably
8507 made a lot of sense at the time. Fixes bug 4169; bugfix on
8509 - If we had ever tried to call tor_addr_to_str() on an address of
8510 unknown type, we would have done a strdup() on an uninitialized
8511 buffer. Now we won't. Fixes bug 4529; bugfix on 0.2.1.3-alpha.
8512 Reported by "troll_un".
8513 - Correctly detect and handle transient lookup failures from
8514 tor_addr_lookup(). Fixes bug 4530; bugfix on 0.2.1.5-alpha.
8515 Reported by "troll_un".
8516 - Use tor_socket_t type for listener argument to accept(). Fixes bug
8517 4535; bugfix on 0.2.2.28-beta. Found by "troll_un".
8518 - Initialize conn->addr to a valid state in spawn_cpuworker(). Fixes
8519 bug 4532; found by "troll_un".
8521 o Minor bugfixes (on Tor 0.2.3.x):
8522 - Fix a compile warning in tor_inet_pton(). Bugfix on 0.2.3.8-alpha;
8524 - Don't send two ESTABLISH_RENDEZVOUS cells when opening a new
8525 circuit for use as a hidden service client's rendezvous point.
8526 Fixes bugs 4641 and 4171; bugfix on 0.2.3.3-alpha. Diagnosed
8527 with help from wanoskarnet.
8528 - Restore behavior of overriding SocksPort, ORPort, and similar
8529 options from the command line. Bugfix on 0.2.3.3-alpha.
8532 - Properly handle the case where the build-tree is not the same
8533 as the source tree when generating src/common/common_sha1.i,
8534 src/or/micro-revision.i, and src/or/or_sha1.i. Fixes bug 3953;
8535 bugfix on 0.2.0.1-alpha.
8537 o Code simplifications, cleanups, and refactorings:
8538 - Remove the pure attribute from all functions that used it
8539 previously. In many cases we assigned it incorrectly, because the
8540 functions might assert or call impure functions, and we don't have
8541 evidence that keeping the pure attribute is worthwhile. Implements
8542 changes suggested in ticket 4421.
8543 - Remove some dead code spotted by coverity. Fixes cid 432.
8544 Bugfix on 0.2.3.1-alpha, closes bug 4637.
8547 Changes in version 0.2.3.8-alpha - 2011-11-22
8548 Tor 0.2.3.8-alpha fixes some crash and assert bugs, including a
8549 socketpair-related bug that has been bothering Windows users. It adds
8550 support to serve microdescriptors to controllers, so Vidalia's network
8551 map can resume listing relays (once Vidalia implements its side),
8552 and adds better support for hardware AES acceleration. Finally, it
8553 starts the process of adjusting the bandwidth cutoff for getting the
8554 "Fast" flag from 20KB to (currently) 32KB -- preliminary results show
8555 that tiny relays harm performance more than they help network capacity.
8558 - Initialize Libevent with the EVENT_BASE_FLAG_NOLOCK flag enabled, so
8559 that it doesn't attempt to allocate a socketpair. This could cause
8560 some problems on Windows systems with overzealous firewalls. Fix for
8561 bug 4457; workaround for Libevent versions 2.0.1-alpha through
8563 - Correctly sanity-check that we don't underflow on a memory
8564 allocation (and then assert) for hidden service introduction
8565 point decryption. Bug discovered by Dan Rosenberg. Fixes bug 4410;
8566 bugfix on 0.2.1.5-alpha.
8567 - Remove the artificially low cutoff of 20KB to guarantee the Fast
8568 flag. In the past few years the average relay speed has picked
8569 up, and while the "top 7/8 of the network get the Fast flag" and
8570 "all relays with 20KB or more of capacity get the Fast flag" rules
8571 used to have the same result, now the top 7/8 of the network has
8572 a capacity more like 32KB. Bugfix on 0.2.1.14-rc. Fixes bug 4489.
8573 - Fix a rare assertion failure when checking whether a v0 hidden
8574 service descriptor has any usable introduction points left, and
8575 we don't have enough information to build a circuit to the first
8576 intro point named in the descriptor. The HS client code in
8577 0.2.3.x no longer uses v0 HS descriptors, but this assertion can
8578 trigger on (and crash) v0 HS authorities. Fixes bug 4411.
8579 Bugfix on 0.2.3.1-alpha; diagnosed by frosty_un.
8580 - Make bridge authorities not crash when they are asked for their own
8581 descriptor. Bugfix on 0.2.3.7-alpha, reported by Lucky Green.
8582 - When running as a client, do not print a misleading (and plain
8583 wrong) log message that we're collecting "directory request"
8584 statistics: clients don't collect statistics. Also don't create a
8585 useless (because empty) stats file in the stats/ directory. Fixes
8586 bug 4353; bugfix on 0.2.2.34 and 0.2.3.7-alpha.
8589 - Allow Tor controllers like Vidalia to obtain the microdescriptor
8590 for a relay by identity digest or nickname. Previously,
8591 microdescriptors were only available by their own digests, so a
8592 controller would have to ask for and parse the whole microdescriptor
8593 consensus in order to look up a single relay's microdesc. Fixes
8594 bug 3832; bugfix on 0.2.3.1-alpha.
8595 - Use OpenSSL's EVP interface for AES encryption, so that all AES
8596 operations can use hardware acceleration (if present). Resolves
8599 o Minor bugfixes (on 0.2.2.x and earlier):
8600 - Detect failure to initialize Libevent. This fix provides better
8601 detection for future instances of bug 4457.
8602 - Avoid frequent calls to the fairly expensive cull_wedged_cpuworkers
8603 function. This was eating up hideously large amounts of time on some
8604 busy servers. Fixes bug 4518; bugfix on 0.0.9.8.
8605 - Don't warn about unused log_mutex in log.c when building with
8606 --disable-threads using a recent GCC. Fixes bug 4437; bugfix on
8607 0.1.0.6-rc which introduced --disable-threads.
8608 - Allow manual 'authenticate' commands to the controller interface
8609 from netcat (nc) as well as telnet. We were rejecting them because
8610 they didn't come with the expected whitespace at the end of the
8611 command. Bugfix on 0.1.1.1-alpha; fixes bug 2893.
8612 - Fix some (not actually triggerable) buffer size checks in usage of
8613 tor_inet_ntop. Fixes bug 4434; bugfix on Tor 0.2.0.1-alpha. Patch
8615 - Fix parsing of some corner-cases with tor_inet_pton(). Fixes
8616 bug 4515; bugfix on 0.2.0.1-alpha; fix by Anders Sundman.
8617 - When configuring, starting, or stopping an NT service, stop
8618 immediately after the service configuration attempt has succeeded
8619 or failed. Fixes bug 3963; bugfix on 0.2.0.7-alpha.
8620 - When sending a NETINFO cell, include the original address
8621 received for the other side, not its canonical address. Found
8622 by "troll_un"; fixes bug 4349; bugfix on 0.2.0.10-alpha.
8623 - Rename the bench_{aes,dmap} functions to test_*, so that tinytest
8624 can pick them up when the tests aren't disabled. Bugfix on
8625 0.2.2.4-alpha which introduced tinytest.
8626 - Fix a memory leak when we check whether a hidden service
8627 descriptor has any usable introduction points left. Fixes bug
8628 4424. Bugfix on 0.2.2.25-alpha.
8629 - Fix a memory leak in launch_direct_bridge_descriptor_fetch() that
8630 occurred when a client tried to fetch a descriptor for a bridge
8631 in ExcludeNodes. Fixes bug 4383; bugfix on 0.2.2.25-alpha.
8633 o Minor bugfixes (on 0.2.3.x):
8634 - Make util unit tests build correctly with MSVC. Bugfix on
8635 0.2.3.3-alpha. Patch by Gisle Vanem.
8636 - Successfully detect AUTH_CHALLENGE cells with no recognized
8637 authentication type listed. Fixes bug 4367; bugfix on 0.2.3.6-alpha.
8639 - If a relay receives an AUTH_CHALLENGE cell it can't answer,
8640 it should still send a NETINFO cell to allow the connection to
8641 become open. Fixes bug 4368; fix on 0.2.3.6-alpha; bug found by
8643 - Log less loudly when we get an invalid authentication certificate
8644 from a source other than a directory authority: it's not unusual
8645 to see invalid certs because of clock skew. Fixes bug 4370; bugfix
8647 - Tolerate servers with more clock skew in their authentication
8648 certificates than previously. Fixes bug 4371; bugfix on
8650 - Fix a couple of compile warnings on Windows. Fixes bug 4469; bugfix
8651 on 0.2.3.4-alpha and 0.2.3.6-alpha.
8654 - Add two new config options for directory authorities:
8655 AuthDirFastGuarantee sets a bandwidth threshold for guaranteeing the
8656 Fast flag, and AuthDirGuardBWGuarantee sets a bandwidth threshold
8657 that is always sufficient to satisfy the bandwidth requirement for
8658 the Guard flag. Now it will be easier for researchers to simulate
8659 Tor networks with different values. Resolves ticket 4484.
8660 - When Tor ignores a hidden service specified in its configuration,
8661 include the hidden service's directory in the warning message.
8662 Previously, we would only tell the user that some hidden service
8663 was ignored. Bugfix on 0.0.6; fixes bug 4426.
8664 - When we fail to initialize Libevent, retry with IOCP disabled so we
8665 don't need to turn on multi-threading support in Libevent, which in
8666 turn requires a working socketpair(). This is a workaround for bug
8667 4457, which affects Libevent versions from 2.0.1-alpha through
8669 - Detect when we try to build on a platform that doesn't define
8670 AF_UNSPEC to 0. We don't work there, so refuse to compile.
8671 - Update to the November 1 2011 Maxmind GeoLite Country database.
8673 o Packaging changes:
8674 - Make it easier to automate expert package builds on Windows,
8675 by removing an absolute path from makensis.exe command.
8677 o Code simplifications and refactoring:
8678 - Remove some redundant #include directives throughout the code.
8679 Patch from Andrea Gelmini.
8680 - Unconditionally use OpenSSL's AES implementation instead of our
8681 old built-in one. OpenSSL's AES has been better for a while, and
8682 relatively few servers should still be on any version of OpenSSL
8683 that doesn't have good optimized assembly AES.
8684 - Use the name "CERTS" consistently to refer to the new cell type;
8685 we were calling it CERT in some places and CERTS in others.
8688 - Numerous new unit tests for functions in util.c and address.c by
8690 - The long-disabled benchmark tests are now split into their own
8691 ./src/test/bench binary.
8692 - The benchmark tests can now use more accurate timers than
8693 gettimeofday() when such timers are available.
8696 Changes in version 0.2.3.7-alpha - 2011-10-30
8697 Tor 0.2.3.7-alpha fixes a crash bug in 0.2.3.6-alpha introduced by
8698 the new v3 handshake. It also resolves yet another bridge address
8702 - If we mark an OR connection for close based on a cell we process,
8703 don't process any further cells on it. We already avoid further
8704 reads on marked-for-close connections, but now we also discard the
8705 cells we'd already read. Fixes bug 4299; bugfix on 0.2.0.10-alpha,
8706 which was the first version where we might mark a connection for
8707 close based on processing a cell on it.
8708 - Fix a double-free bug that would occur when we received an invalid
8709 certificate in a CERT cell in the new v3 handshake. Fixes bug 4343;
8710 bugfix on 0.2.3.6-alpha.
8711 - Bridges no longer include their address in NETINFO cells on outgoing
8712 OR connections, to allow them to blend in better with clients.
8713 Removes another avenue for enumerating bridges. Reported by
8714 "troll_un". Fixes bug 4348; bugfix on 0.2.0.10-alpha, when NETINFO
8715 cells were introduced.
8718 - Fixed a typo in a hibernation-related log message. Fixes bug 4331;
8719 bugfix on 0.2.2.23-alpha; found by "tmpname0901".
8722 Changes in version 0.2.3.6-alpha - 2011-10-26
8723 Tor 0.2.3.6-alpha includes the fix from 0.2.2.34 for a critical
8724 anonymity vulnerability where an attacker can deanonymize Tor
8725 users. Everybody should upgrade.
8727 This release also features support for a new v3 connection handshake
8728 protocol, and fixes to make hidden service connections more robust.
8731 - Implement a new handshake protocol (v3) for authenticating Tors to
8732 each other over TLS. It should be more resistant to fingerprinting
8733 than previous protocols, and should require less TLS hacking for
8734 future Tor implementations. Implements proposal 176.
8735 - Allow variable-length padding cells to disguise the length of
8736 Tor's TLS records. Implements part of proposal 184.
8738 o Privacy/anonymity fixes (clients):
8739 - Clients and bridges no longer send TLS certificate chains on
8740 outgoing OR connections. Previously, each client or bridge would
8741 use the same cert chain for all outgoing OR connections until
8742 its IP address changes, which allowed any relay that the client
8743 or bridge contacted to determine which entry guards it is using.
8744 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8745 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8746 no longer considers that connection as suitable for satisfying a
8747 circuit EXTEND request. Now relays can protect clients from the
8748 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8749 - Directory authorities no longer assign the Guard flag to relays
8750 that haven't upgraded to the above "refuse EXTEND requests
8751 to client connections" fix. Now directory authorities can
8752 protect clients from the CVE-2011-2768 issue even if neither
8753 the clients nor the relays have upgraded yet. There's a new
8754 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8755 to let us transition smoothly, else tomorrow there would be no
8758 o Major bugfixes (hidden services):
8759 - Improve hidden service robustness: when an attempt to connect to
8760 a hidden service ends, be willing to refetch its hidden service
8761 descriptors from each of the HSDir relays responsible for them
8762 immediately. Previously, we would not consider refetching the
8763 service's descriptors from each HSDir for 15 minutes after the last
8764 fetch, which was inconvenient if the hidden service was not running
8765 during the first attempt. Bugfix on 0.2.0.18-alpha; fixes bug 3335.
8766 - When one of a hidden service's introduction points appears to be
8767 unreachable, stop trying it. Previously, we would keep trying
8768 to build circuits to the introduction point until we lost the
8769 descriptor, usually because the user gave up and restarted Tor.
8770 Partly fixes bug 3825.
8771 - Don't launch a useless circuit after failing to use one of a
8772 hidden service's introduction points. Previously, we would
8773 launch a new introduction circuit, but not set the hidden service
8774 which that circuit was intended to connect to, so it would never
8775 actually be used. A different piece of code would then create a
8776 new introduction circuit correctly. Bug reported by katmagic and
8777 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8779 o Major bugfixes (other):
8780 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8781 that they initiated. Relays could distinguish incoming bridge
8782 connections from client connections, creating another avenue for
8783 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8784 Found by "frosty_un".
8785 - Don't update the AccountingSoftLimitHitAt state file entry whenever
8786 tor gets started. This prevents a wrong average bandwidth
8787 estimate, which would cause relays to always start a new accounting
8788 interval at the earliest possible moment. Fixes bug 2003; bugfix
8789 on 0.2.2.7-alpha. Reported by BryonEldridge, who also helped
8790 immensely in tracking this bug down.
8791 - Fix a crash bug when changing node restrictions while a DNS lookup
8792 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8795 o Minor bugfixes (on 0.2.2.x and earlier):
8796 - When a hidden service turns an extra service-side introduction
8797 circuit into a general-purpose circuit, free the rend_data and
8798 intro_key fields first, so we won't leak memory if the circuit
8799 is cannibalized for use as another service-side introduction
8800 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8801 - Rephrase the log message emitted if the TestSocks check is
8802 successful. Patch from Fabian Keil; fixes bug 4094.
8803 - Bridges now skip DNS self-tests, to act a little more stealthily.
8804 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8805 bridges. Patch by "warms0x".
8806 - Remove a confusing dollar sign from the example fingerprint in the
8807 man page, and also make the example fingerprint a valid one. Fixes
8808 bug 4309; bugfix on 0.2.1.3-alpha.
8809 - Fix internal bug-checking logic that was supposed to catch
8810 failures in digest generation so that it will fail more robustly
8811 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8812 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8813 - Report any failure in init_keys() calls launched because our
8814 IP address has changed. Spotted by Coverity Scan. Bugfix on
8815 0.1.1.4-alpha; fixes CID 484.
8817 o Minor bugfixes (on 0.2.3.x):
8818 - Fix a bug in configure.in that kept it from building a configure
8819 script with autoconf versions earlier than 2.61. Fixes bug 2430;
8820 bugfix on 0.2.3.1-alpha.
8821 - Don't warn users that they are exposing a client port to the
8822 Internet if they have specified an RFC1918 address. Previously,
8823 we would warn if the user had specified any non-loopback
8824 address. Bugfix on 0.2.3.3-alpha. Fixes bug 4018; reported by Tas.
8825 - Fix memory leaks in the failing cases of the new SocksPort and
8826 ControlPort code. Found by Coverity Scan. Bugfix on 0.2.3.3-alpha;
8827 fixes coverity CIDs 485, 486, and 487.
8830 - When a hidden service's introduction point times out, consider
8831 trying it again during the next attempt to connect to the
8832 HS. Previously, we would not try it again unless a newly fetched
8833 descriptor contained it. Required by fixes for bugs 1297 and 3825.
8834 - The next version of Windows will be called Windows 8, and it has
8835 a major version of 6, minor version of 2. Correctly identify that
8836 version instead of calling it "Very recent version". Resolves
8837 ticket 4153; reported by funkstar.
8838 - The Bridge Authority now writes statistics on how many bridge
8839 descriptors it gave out in total, and how many unique descriptors
8840 it gave out. It also lists how often the most and least commonly
8841 fetched descriptors were given out, as well as the median and
8842 25th/75th percentile. Implements tickets 4200 and 4294.
8843 - Update to the October 4 2011 Maxmind GeoLite Country database.
8845 o Code simplifications and refactoring:
8846 - Remove some old code to remember statistics about which descriptors
8847 we've served as a directory mirror. The feature wasn't used and
8848 is outdated now that microdescriptors are around.
8849 - Rename Tor functions that turn strings into addresses, so that
8850 "parse" indicates that no hostname resolution occurs, and
8851 "lookup" indicates that hostname resolution may occur. This
8852 should help prevent mistakes in the future. Fixes bug 3512.
8855 Changes in version 0.2.2.34 - 2011-10-26
8856 Tor 0.2.2.34 fixes a critical anonymity vulnerability where an attacker
8857 can deanonymize Tor users. Everybody should upgrade.
8859 The attack relies on four components: 1) Clients reuse their TLS cert
8860 when talking to different relays, so relays can recognize a user by
8861 the identity key in her cert. 2) An attacker who knows the client's
8862 identity key can probe each guard relay to see if that identity key
8863 is connected to that guard relay right now. 3) A variety of active
8864 attacks in the literature (starting from "Low-Cost Traffic Analysis
8865 of Tor" by Murdoch and Danezis in 2005) allow a malicious website to
8866 discover the guard relays that a Tor user visiting the website is using.
8867 4) Clients typically pick three guards at random, so the set of guards
8868 for a given user could well be a unique fingerprint for her. This
8869 release fixes components #1 and #2, which is enough to block the attack;
8870 the other two remain as open research problems. Special thanks to
8871 "frosty_un" for reporting the issue to us!
8873 Clients should upgrade so they are no longer recognizable by the TLS
8874 certs they present. Relays should upgrade so they no longer allow a
8875 remote attacker to probe them to test whether unpatched clients are
8876 currently connected to them.
8878 This release also fixes several vulnerabilities that allow an attacker
8879 to enumerate bridge relays. Some bridge enumeration attacks still
8880 remain; see for example proposal 188.
8882 o Privacy/anonymity fixes (clients):
8883 - Clients and bridges no longer send TLS certificate chains on
8884 outgoing OR connections. Previously, each client or bridge would
8885 use the same cert chain for all outgoing OR connections until
8886 its IP address changes, which allowed any relay that the client
8887 or bridge contacted to determine which entry guards it is using.
8888 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8889 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8890 no longer considers that connection as suitable for satisfying a
8891 circuit EXTEND request. Now relays can protect clients from the
8892 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8893 - Directory authorities no longer assign the Guard flag to relays
8894 that haven't upgraded to the above "refuse EXTEND requests
8895 to client connections" fix. Now directory authorities can
8896 protect clients from the CVE-2011-2768 issue even if neither
8897 the clients nor the relays have upgraded yet. There's a new
8898 "GiveGuardFlagTo_CVE_2011_2768_VulnerableRelays" config option
8899 to let us transition smoothly, else tomorrow there would be no
8902 o Privacy/anonymity fixes (bridge enumeration):
8903 - Bridge relays now do their directory fetches inside Tor TLS
8904 connections, like all the other clients do, rather than connecting
8905 directly to the DirPort like public relays do. Removes another
8906 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
8907 - Bridges relays now build circuits for themselves in a more similar
8908 way to how clients build them. Removes another avenue for
8909 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
8910 when bridges were introduced.
8911 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8912 that they initiated. Relays could distinguish incoming bridge
8913 connections from client connections, creating another avenue for
8914 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
8915 Found by "frosty_un".
8918 - Fix a crash bug when changing node restrictions while a DNS lookup
8919 is in-progress. Fixes bug 4259; bugfix on 0.2.2.25-alpha. Bugfix
8921 - Don't launch a useless circuit after failing to use one of a
8922 hidden service's introduction points. Previously, we would
8923 launch a new introduction circuit, but not set the hidden service
8924 which that circuit was intended to connect to, so it would never
8925 actually be used. A different piece of code would then create a
8926 new introduction circuit correctly. Bug reported by katmagic and
8927 found by Sebastian Hahn. Bugfix on 0.2.1.13-alpha; fixes bug 4212.
8930 - Change an integer overflow check in the OpenBSD_Malloc code so
8931 that GCC is less likely to eliminate it as impossible. Patch
8932 from Mansour Moufid. Fixes bug 4059.
8933 - When a hidden service turns an extra service-side introduction
8934 circuit into a general-purpose circuit, free the rend_data and
8935 intro_key fields first, so we won't leak memory if the circuit
8936 is cannibalized for use as another service-side introduction
8937 circuit. Bugfix on 0.2.1.7-alpha; fixes bug 4251.
8938 - Bridges now skip DNS self-tests, to act a little more stealthily.
8939 Fixes bug 4201; bugfix on 0.2.0.3-alpha, which first introduced
8940 bridges. Patch by "warms0x".
8941 - Fix internal bug-checking logic that was supposed to catch
8942 failures in digest generation so that it will fail more robustly
8943 if we ask for a nonexistent algorithm. Found by Coverity Scan.
8944 Bugfix on 0.2.2.1-alpha; fixes Coverity CID 479.
8945 - Report any failure in init_keys() calls launched because our
8946 IP address has changed. Spotted by Coverity Scan. Bugfix on
8947 0.1.1.4-alpha; fixes CID 484.
8949 o Minor bugfixes (log messages and documentation):
8950 - Remove a confusing dollar sign from the example fingerprint in the
8951 man page, and also make the example fingerprint a valid one. Fixes
8952 bug 4309; bugfix on 0.2.1.3-alpha.
8953 - The next version of Windows will be called Windows 8, and it has
8954 a major version of 6, minor version of 2. Correctly identify that
8955 version instead of calling it "Very recent version". Resolves
8956 ticket 4153; reported by funkstar.
8957 - Downgrade log messages about circuit timeout calibration from
8958 "notice" to "info": they don't require or suggest any human
8959 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
8960 bugfix on 0.2.2.14-alpha.
8963 - Turn on directory request statistics by default and include them in
8964 extra-info descriptors. Don't break if we have no GeoIP database.
8965 Backported from 0.2.3.1-alpha; implements ticket 3951.
8966 - Update to the October 4 2011 Maxmind GeoLite Country database.
8969 Changes in version 0.2.1.31 - 2011-10-26
8970 Tor 0.2.1.31 backports important security and privacy fixes for
8971 oldstable. This release is intended only for package maintainers and
8972 others who cannot use the 0.2.2 stable series. All others should be
8973 using Tor 0.2.2.x or newer.
8975 o Security fixes (also included in 0.2.2.x):
8976 - Replace all potentially sensitive memory comparison operations
8977 with versions whose runtime does not depend on the data being
8978 compared. This will help resist a class of attacks where an
8979 adversary can use variations in timing information to learn
8980 sensitive data. Fix for one case of bug 3122. (Safe memcmp
8981 implementation by Robert Ransom based partially on code by DJB.)
8982 - Fix an assert in parsing router descriptors containing IPv6
8983 addresses. This one took down the directory authorities when
8984 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
8986 o Privacy/anonymity fixes (also included in 0.2.2.x):
8987 - Clients and bridges no longer send TLS certificate chains on
8988 outgoing OR connections. Previously, each client or bridge would
8989 use the same cert chain for all outgoing OR connections until
8990 its IP address changes, which allowed any relay that the client
8991 or bridge contacted to determine which entry guards it is using.
8992 Fixes CVE-2011-2768. Bugfix on 0.0.9pre5; found by "frosty_un".
8993 - If a relay receives a CREATE_FAST cell on a TLS connection, it
8994 no longer considers that connection as suitable for satisfying a
8995 circuit EXTEND request. Now relays can protect clients from the
8996 CVE-2011-2768 issue even if the clients haven't upgraded yet.
8997 - Bridges now refuse CREATE or CREATE_FAST cells on OR connections
8998 that they initiated. Relays could distinguish incoming bridge
8999 connections from client connections, creating another avenue for
9000 enumerating bridges. Fixes CVE-2011-2769. Bugfix on 0.2.0.3-alpha.
9001 Found by "frosty_un".
9002 - When receiving a hidden service descriptor, check that it is for
9003 the hidden service we wanted. Previously, Tor would store any
9004 hidden service descriptors that a directory gave it, whether it
9005 wanted them or not. This wouldn't have let an attacker impersonate
9006 a hidden service, but it did let directories pre-seed a client
9007 with descriptors that it didn't want. Bugfix on 0.0.6.
9008 - Avoid linkability based on cached hidden service descriptors: forget
9009 all hidden service descriptors cached as a client when processing a
9010 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
9011 - Make the bridge directory authority refuse to answer directory
9012 requests for "all" descriptors. It used to include bridge
9013 descriptors in its answer, which was a major information leak.
9014 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
9015 - Don't attach new streams to old rendezvous circuits after SIGNAL
9016 NEWNYM. Previously, we would keep using an existing rendezvous
9017 circuit if it remained open (i.e. if it were kept open by a
9018 long-lived stream, or if a new stream were attached to it before
9019 Tor could notice that it was old and no longer in use). Bugfix on
9020 0.1.1.15-rc; fixes bug 3375.
9022 o Minor bugfixes (also included in 0.2.2.x):
9023 - When we restart our relay, we might get a successful connection
9024 from the outside before we've started our reachability tests,
9025 triggering a warning: "ORPort found reachable, but I have no
9026 routerinfo yet. Failing to inform controller of success." This
9027 bug was harmless unless Tor is running under a controller
9028 like Vidalia, in which case the controller would never get a
9029 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
9031 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
9032 enabled. Fixes bug 1526.
9033 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9034 anything since 0.2.1.16-rc.
9035 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
9036 None of the cases where we did this before were wrong, but by making
9037 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
9038 - Fix a rare crash bug that could occur when a client was configured
9039 with a large number of bridges. Fixes bug 2629; bugfix on
9040 0.2.1.2-alpha. Bugfix by trac user "shitlei".
9041 - Correct the warning displayed when a rendezvous descriptor exceeds
9042 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
9044 - Fix an uncommon assertion failure when running with DNSPort under
9045 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
9046 - When warning about missing zlib development packages during compile,
9047 give the correct package names. Bugfix on 0.2.0.1-alpha.
9048 - Require that introduction point keys and onion keys have public
9049 exponent 65537. Bugfix on 0.2.0.10-alpha.
9050 - Do not crash when our configuration file becomes unreadable, for
9051 example due to a permissions change, between when we start up
9052 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9054 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9056 - Always NUL-terminate the sun_path field of a sockaddr_un before
9057 passing it to the kernel. (Not a security issue: kernels are
9058 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9059 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9060 - Don't stack-allocate the list of supplementary GIDs when we're
9061 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9062 could take up to 256K, which is way too much stack. Found by
9063 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9065 o Minor bugfixes (only in 0.2.1.x):
9066 - Resume using micro-version numbers in 0.2.1.x: our Debian packages
9067 rely on them. Bugfix on 0.2.1.30.
9068 - Use git revisions instead of svn revisions when generating our
9069 micro-version numbers. Bugfix on 0.2.1.15-rc; fixes bug 2402.
9071 o Minor features (also included in 0.2.2.x):
9072 - Adjust the expiration time on our SSL session certificates to
9073 better match SSL certs seen in the wild. Resolves ticket 4014.
9074 - Allow nameservers with IPv6 address. Resolves bug 2574.
9075 - Update to the October 4 2011 Maxmind GeoLite Country database.
9078 Changes in version 0.2.3.5-alpha - 2011-09-28
9079 Tor 0.2.3.5-alpha fixes two bugs that make it possible to enumerate
9080 bridge relays; fixes an assertion error that many users started hitting
9081 today; and adds the ability to refill token buckets more often than
9082 once per second, allowing significant performance improvements.
9085 - Bridge relays now do their directory fetches inside Tor TLS
9086 connections, like all the other clients do, rather than connecting
9087 directly to the DirPort like public relays do. Removes another
9088 avenue for enumerating bridges. Fixes bug 4115; bugfix on 0.2.0.35.
9089 - Bridges relays now build circuits for themselves in a more similar
9090 way to how clients build them. Removes another avenue for
9091 enumerating bridges. Fixes bug 4124; bugfix on 0.2.0.3-alpha,
9092 when bridges were introduced.
9095 - Fix an "Assertion md->held_by_node == 1 failed" error that could
9096 occur when the same microdescriptor was referenced by two node_t
9097 objects at once. Fix for bug 4118; bugfix on Tor 0.2.3.1-alpha.
9099 o Major features (networking):
9100 - Add a new TokenBucketRefillInterval option to refill token buckets
9101 more frequently than once per second. This should improve network
9102 performance, alleviate queueing problems, and make traffic less
9103 bursty. Implements proposal 183; closes ticket 3630. Design by
9104 Florian Tschorsch and Björn Scheuermann; implementation by
9108 - Change an integer overflow check in the OpenBSD_Malloc code so
9109 that GCC is less likely to eliminate it as impossible. Patch
9110 from Mansour Moufid. Fixes bug 4059.
9112 o Minor bugfixes (usability):
9113 - Downgrade log messages about circuit timeout calibration from
9114 "notice" to "info": they don't require or suggest any human
9115 intervention. Patch from Tom Lowenthal. Fixes bug 4063;
9116 bugfix on 0.2.2.14-alpha.
9118 o Minor features (diagnostics):
9119 - When the system call to create a listener socket fails, log the
9120 error message explaining why. This may help diagnose bug 4027.
9123 Changes in version 0.2.3.4-alpha - 2011-09-13
9124 Tor 0.2.3.4-alpha includes the fixes from 0.2.2.33, including a slight
9125 tweak to Tor's TLS handshake that makes relays and bridges that run
9126 this new version reachable from Iran again. It also fixes a few new
9127 bugs in 0.2.3.x, and teaches relays to recognize when they're not
9128 listed in the network consensus and republish.
9130 o Major bugfixes (also part of 0.2.2.33):
9131 - Avoid an assertion failure when reloading a configuration with
9132 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9133 3923; bugfix on 0.2.2.25-alpha.
9135 o Minor features (security, also part of 0.2.2.33):
9136 - Check for replays of the public-key encrypted portion of an
9137 INTRODUCE1 cell, in addition to the current check for replays of
9138 the g^x value. This prevents a possible class of active attacks
9139 by an attacker who controls both an introduction point and a
9140 rendezvous point, and who uses the malleability of AES-CTR to
9141 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9142 that these attacks are infeasible (requiring the attacker to send
9143 on the order of zettabytes of altered cells in a short interval),
9144 but we'd rather block them off in case there are any classes of
9145 this attack that we missed. Reported by Willem Pinckaers.
9147 o Minor features (also part of 0.2.2.33):
9148 - Adjust the expiration time on our SSL session certificates to
9149 better match SSL certs seen in the wild. Resolves ticket 4014.
9150 - Change the default required uptime for a relay to be accepted as
9151 a HSDir (hidden service directory) from 24 hours to 25 hours.
9152 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9153 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9154 authorities to abstain from voting on assignment of the HSDir
9155 consensus flag. Related to bug 2649.
9156 - Update to the September 6 2011 Maxmind GeoLite Country database.
9158 o Minor bugfixes (also part of 0.2.2.33):
9159 - Demote the 'replay detected' log message emitted when a hidden
9160 service receives the same Diffie-Hellman public key in two different
9161 INTRODUCE2 cells to info level. A normal Tor client can cause that
9162 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9163 fixes part of bug 2442.
9164 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9165 level. There is nothing that a hidden service's operator can do
9166 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9168 - Clarify a log message specifying the characters permitted in
9169 HiddenServiceAuthorizeClient client names. Previously, the log
9170 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9171 given the impression that every ASCII character between "+" and "_"
9172 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9174 o Build fixes (also part of 0.2.2.33):
9175 - Clean up some code issues that prevented Tor from building on older
9176 BSDs. Fixes bug 3894; reported by "grarpamp".
9177 - Search for a platform-specific version of "ar" when cross-compiling.
9178 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9181 - Fix a bug where the SocksPort option (for example) would get
9182 ignored and replaced by the default if a SocksListenAddress
9183 option was set. Bugfix on 0.2.3.3-alpha; fixes bug 3936. Fix by
9187 - Relays now try regenerating and uploading their descriptor more
9188 frequently if they are not listed in the consensus, or if the
9189 version of their descriptor listed in the consensus is too
9190 old. This fix should prevent situations where a server declines
9191 to re-publish itself because it has done so too recently, even
9192 though the authorities decided not to list its recent-enough
9193 descriptor. Fix for bug 3327.
9196 - Relays now include a reason for regenerating their descriptors
9197 in an HTTP header when uploading to the authorities. This will
9198 make it easier to debug descriptor-upload issues in the future.
9199 - When starting as root and then changing our UID via the User
9200 control option, and we have a ControlSocket configured, make sure
9201 that the ControlSocket is owned by the same account that Tor will
9202 run under. Implements ticket 3421; fix by Jérémy Bobbio.
9205 - Abort if tor_vasprintf fails in connection_printf_to_buf (a
9206 utility function used in the control-port code). This shouldn't
9207 ever happen unless Tor is completely out of memory, but if it did
9208 happen and Tor somehow recovered from it, Tor could have sent a log
9209 message to a control port in the middle of a reply to a controller
9210 command. Fixes part of bug 3428; bugfix on 0.1.2.3-alpha.
9211 - Make 'FetchUselessDescriptors' cause all descriptor types and
9212 all consensus types (including microdescriptors) to get fetched.
9213 Fixes bug 3851; bugfix on 0.2.3.1-alpha.
9216 - Make a new "entry connection" struct as an internal subtype of "edge
9217 connection", to simplify the code and make exit connections smaller.
9220 Changes in version 0.2.2.33 - 2011-09-13
9221 Tor 0.2.2.33 fixes several bugs, and includes a slight tweak to Tor's
9222 TLS handshake that makes relays and bridges that run this new version
9223 reachable from Iran again.
9226 - Avoid an assertion failure when reloading a configuration with
9227 TrackExitHosts changes. Found and fixed by 'laruldan'. Fixes bug
9228 3923; bugfix on 0.2.2.25-alpha.
9230 o Minor features (security):
9231 - Check for replays of the public-key encrypted portion of an
9232 INTRODUCE1 cell, in addition to the current check for replays of
9233 the g^x value. This prevents a possible class of active attacks
9234 by an attacker who controls both an introduction point and a
9235 rendezvous point, and who uses the malleability of AES-CTR to
9236 alter the encrypted g^x portion of the INTRODUCE1 cell. We think
9237 that these attacks are infeasible (requiring the attacker to send
9238 on the order of zettabytes of altered cells in a short interval),
9239 but we'd rather block them off in case there are any classes of
9240 this attack that we missed. Reported by Willem Pinckaers.
9243 - Adjust the expiration time on our SSL session certificates to
9244 better match SSL certs seen in the wild. Resolves ticket 4014.
9245 - Change the default required uptime for a relay to be accepted as
9246 a HSDir (hidden service directory) from 24 hours to 25 hours.
9247 Improves on 0.2.0.10-alpha; resolves ticket 2649.
9248 - Add a VoteOnHidServDirectoriesV2 config option to allow directory
9249 authorities to abstain from voting on assignment of the HSDir
9250 consensus flag. Related to bug 2649.
9251 - Update to the September 6 2011 Maxmind GeoLite Country database.
9253 o Minor bugfixes (documentation and log messages):
9254 - Correct the man page to explain that HashedControlPassword and
9255 CookieAuthentication can both be set, in which case either method
9256 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9257 when we decided to allow these config options to both be set. Issue
9259 - Demote the 'replay detected' log message emitted when a hidden
9260 service receives the same Diffie-Hellman public key in two different
9261 INTRODUCE2 cells to info level. A normal Tor client can cause that
9262 log message during its normal operation. Bugfix on 0.2.1.6-alpha;
9263 fixes part of bug 2442.
9264 - Demote the 'INTRODUCE2 cell is too {old,new}' log message to info
9265 level. There is nothing that a hidden service's operator can do
9266 to fix its clients' clocks. Bugfix on 0.2.1.6-alpha; fixes part
9268 - Clarify a log message specifying the characters permitted in
9269 HiddenServiceAuthorizeClient client names. Previously, the log
9270 message said that "[A-Za-z0-9+-_]" were permitted; that could have
9271 given the impression that every ASCII character between "+" and "_"
9272 was permitted. Now we say "[A-Za-z0-9+_-]". Bugfix on 0.2.1.5-alpha.
9275 - Provide a substitute implementation of lround() for MSVC, which
9276 apparently lacks it. Patch from Gisle Vanem.
9277 - Clean up some code issues that prevented Tor from building on older
9278 BSDs. Fixes bug 3894; reported by "grarpamp".
9279 - Search for a platform-specific version of "ar" when cross-compiling.
9280 Should fix builds on iOS. Resolves bug 3909, found by Marco Bonetti.
9283 Changes in version 0.2.3.3-alpha - 2011-09-01
9284 Tor 0.2.3.3-alpha adds a new "stream isolation" feature to improve Tor's
9285 security, and provides client-side support for the microdescriptor
9286 and optimistic data features introduced earlier in the 0.2.3.x
9287 series. It also includes numerous critical bugfixes in the (optional)
9288 bufferevent-based networking backend.
9290 o Major features (stream isolation):
9291 - You can now configure Tor so that streams from different
9292 applications are isolated on different circuits, to prevent an
9293 attacker who sees your streams as they leave an exit node from
9294 linking your sessions to one another. To do this, choose some way
9295 to distinguish the applications: have them connect to different
9296 SocksPorts, or have one of them use SOCKS4 while the other uses
9297 SOCKS5, or have them pass different authentication strings to the
9298 SOCKS proxy. Then, use the new SocksPort syntax to configure the
9299 degree of isolation you need. This implements Proposal 171.
9300 - There's a new syntax for specifying multiple client ports (such as
9301 SOCKSPort, TransPort, DNSPort, NATDPort): you can now just declare
9302 multiple *Port entries with full addr:port syntax on each.
9303 The old *ListenAddress format is still supported, but you can't
9304 mix it with the new *Port syntax.
9306 o Major features (other):
9307 - Enable microdescriptor fetching by default for clients. This allows
9308 clients to download a much smaller amount of directory information.
9309 To disable it (and go back to the old-style consensus and
9310 descriptors), set "UseMicrodescriptors 0" in your torrc file.
9311 - Tor's firewall-helper feature, introduced in 0.2.3.1-alpha (see the
9312 "PortForwarding" config option), now supports Windows.
9313 - When using an exit relay running 0.2.3.x, clients can now
9314 "optimistically" send data before the exit relay reports that
9315 the stream has opened. This saves a round trip when starting
9316 connections where the client speaks first (such as web browsing).
9317 This behavior is controlled by a consensus parameter (currently
9318 disabled). To turn it on or off manually, use the "OptimisticData"
9319 torrc option. Implements proposal 181; code by Ian Goldberg.
9321 o Major bugfixes (bufferevents, fixes on 0.2.3.1-alpha):
9322 - When using IOCP on Windows, we need to enable Libevent windows
9324 - The IOCP backend now works even when the user has not specified
9325 the (internal, debugging-only) _UseFilteringSSLBufferevents option.
9326 Fixes part of bug 3752.
9327 - Correctly record the bytes we've read and written when using
9328 bufferevents, so that we can include them in our bandwidth history
9329 and advertised bandwidth. Fixes bug 3803.
9330 - Apply rate-limiting only at the bottom of a chain of filtering
9331 bufferevents. This prevents us from filling up internal read
9332 buffers and violating rate-limits when filtering bufferevents
9333 are enabled. Fixes part of bug 3804.
9334 - Add high-watermarks to the output buffers for filtered
9335 bufferevents. This prevents us from filling up internal write
9336 buffers and wasting CPU cycles when filtering bufferevents are
9337 enabled. Fixes part of bug 3804.
9338 - Correctly notice when data has been written from a bufferevent
9339 without flushing it completely. Fixes bug 3805.
9340 - Fix a bug where server-side tunneled bufferevent-based directory
9341 streams would get closed prematurely. Fixes bug 3814.
9342 - Fix a use-after-free error with per-connection rate-limiting
9343 buckets. Fixes bug 3888.
9345 o Major bugfixes (also part of 0.2.2.31-rc):
9346 - If we're configured to write our ControlPorts to disk, only write
9347 them after switching UID and creating the data directory. This way,
9348 we don't fail when starting up with a nonexistent DataDirectory
9349 and a ControlPortWriteToFile setting based on that directory. Fixes
9350 bug 3747; bugfix on Tor 0.2.2.26-beta.
9353 - Added a new CONF_CHANGED event so that controllers can be notified
9354 of any configuration changes made by other controllers, or by the
9355 user. Implements ticket 1692.
9356 - Use evbuffer_copyout() in inspect_evbuffer(). This fixes a memory
9357 leak when using bufferevents, and lets Libevent worry about how to
9358 best copy data out of a buffer.
9359 - Replace files in stats/ rather than appending to them. Now that we
9360 include statistics in extra-info descriptors, it makes no sense to
9361 keep old statistics forever. Implements ticket 2930.
9363 o Minor features (build compatibility):
9364 - Limited, experimental support for building with nmake and MSVC.
9365 - Provide a substitute implementation of lround() for MSVC, which
9366 apparently lacks it. Patch from Gisle Vanem.
9368 o Minor features (also part of 0.2.2.31-rc):
9369 - Update to the August 2 2011 Maxmind GeoLite Country database.
9371 o Minor bugfixes (on 0.2.3.x-alpha):
9372 - Fix a spurious warning when parsing SOCKS requests with
9373 bufferevents enabled. Fixes bug 3615; bugfix on 0.2.3.2-alpha.
9374 - Get rid of a harmless warning that could happen on relays running
9375 with bufferevents. The warning was caused by someone doing an http
9376 request to a relay's orport. Also don't warn for a few related
9377 non-errors. Fixes bug 3700; bugfix on 0.2.3.1-alpha.
9379 o Minor bugfixes (on 2.2.x and earlier):
9380 - Correct the man page to explain that HashedControlPassword and
9381 CookieAuthentication can both be set, in which case either method
9382 is sufficient to authenticate to Tor. Bugfix on 0.2.0.7-alpha,
9383 when we decided to allow these config options to both be set. Issue
9385 - The "--quiet" and "--hush" options now apply not only to Tor's
9386 behavior before logs are configured, but also to Tor's behavior in
9387 the absense of configured logs. Fixes bug 3550; bugfix on
9390 o Minor bugfixes (also part of 0.2.2.31-rc):
9391 - Write several files in text mode, on OSes that distinguish text
9392 mode from binary mode (namely, Windows). These files are:
9393 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9394 that collect those statistics; 'client_keys' and 'hostname' for
9395 hidden services that use authentication; and (in the tor-gencert
9396 utility) newly generated identity and signing keys. Previously,
9397 we wouldn't specify text mode or binary mode, leading to an
9398 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9399 the DirRecordUsageByCountry option which would have triggered
9400 the assertion failure was added), although this assertion failure
9401 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9402 - Selectively disable deprecation warnings on OS X because Lion
9403 started deprecating the shipped copy of openssl. Fixes bug 3643.
9404 - Remove an extra pair of quotation marks around the error
9405 message in control-port STATUS_GENERAL BUG events. Bugfix on
9406 0.1.2.6-alpha; fixes bug 3732.
9407 - When unable to format an address as a string, report its value
9408 as "???" rather than reusing the last formatted address. Bugfix
9411 o Code simplifications and refactoring:
9412 - Rewrite the listener-selection logic so that parsing which ports
9413 we want to listen on is now separate from binding to the ports
9417 - Building Tor with bufferevent support now requires Libevent
9418 2.0.13-stable or later. Previous versions of Libevent had bugs in
9419 SSL-related bufferevents and related issues that would make Tor
9420 work badly with bufferevents. Requiring 2.0.13-stable also allows
9421 Tor with bufferevents to take advantage of Libevent APIs
9422 introduced after 2.0.8-rc.
9425 Changes in version 0.2.2.32 - 2011-08-27
9426 The Tor 0.2.2 release series is dedicated to the memory of Andreas
9427 Pfitzmann (1958-2010), a pioneer in anonymity and privacy research,
9428 a founder of the PETS community, a leader in our field, a mentor,
9429 and a friend. He left us with these words: "I had the possibility
9430 to contribute to this world that is not as it should be. I hope I
9431 could help in some areas to make the world a better place, and that
9432 I could also encourage other people to be engaged in improving the
9433 world. Please, stay engaged. This world needs you, your love, your
9434 initiative -- now I cannot be part of that anymore."
9436 Tor 0.2.2.32, the first stable release in the 0.2.2 branch, is finally
9437 ready. More than two years in the making, this release features improved
9438 client performance and hidden service reliability, better compatibility
9439 for Android, correct behavior for bridges that listen on more than
9440 one address, more extensible and flexible directory object handling,
9441 better reporting of network statistics, improved code security, and
9442 many many other features and bugfixes.
9445 Changes in version 0.2.2.31-rc - 2011-08-17
9446 Tor 0.2.2.31-rc is the second and hopefully final release candidate
9447 for the Tor 0.2.2.x series.
9450 - Remove an extra pair of quotation marks around the error
9451 message in control-port STATUS_GENERAL BUG events. Bugfix on
9452 0.1.2.6-alpha; fixes bug 3732.
9453 - If we're configured to write our ControlPorts to disk, only write
9454 them after switching UID and creating the data directory. This way,
9455 we don't fail when starting up with a nonexistent DataDirectory
9456 and a ControlPortWriteToFile setting based on that directory. Fixes
9457 bug 3747; bugfix on Tor 0.2.2.26-beta.
9460 - Update to the August 2 2011 Maxmind GeoLite Country database.
9463 - Allow GETINFO fingerprint to return a fingerprint even when
9464 we have not yet built a router descriptor. Fixes bug 3577;
9465 bugfix on 0.2.0.1-alpha.
9466 - Write several files in text mode, on OSes that distinguish text
9467 mode from binary mode (namely, Windows). These files are:
9468 'buffer-stats', 'dirreq-stats', and 'entry-stats' on relays
9469 that collect those statistics; 'client_keys' and 'hostname' for
9470 hidden services that use authentication; and (in the tor-gencert
9471 utility) newly generated identity and signing keys. Previously,
9472 we wouldn't specify text mode or binary mode, leading to an
9473 assertion failure. Fixes bug 3607. Bugfix on 0.2.1.1-alpha (when
9474 the DirRecordUsageByCountry option which would have triggered
9475 the assertion failure was added), although this assertion failure
9476 would have occurred in tor-gencert on Windows in 0.2.0.1-alpha.
9477 - Selectively disable deprecation warnings on OS X because Lion
9478 started deprecating the shipped copy of openssl. Fixes bug 3643.
9479 - When unable to format an address as a string, report its value
9480 as "???" rather than reusing the last formatted address. Bugfix
9484 Changes in version 0.2.3.2-alpha - 2011-07-18
9485 Tor 0.2.3.2-alpha introduces two new experimental features:
9486 microdescriptors and pluggable transports. It also continues cleaning
9487 up a variety of recently introduced features.
9490 - Clients can now use microdescriptors instead of regular descriptors
9491 to build circuits. Microdescriptors are authority-generated
9492 summaries of regular descriptors' contents, designed to change
9493 very rarely (see proposal 158 for details). This feature is
9494 designed to save bandwidth, especially for clients on slow internet
9495 connections. It's off by default for now, since nearly no caches
9496 support it, but it will be on-by-default for clients in a future
9497 version. You can use the UseMicrodescriptors option to turn it on.
9498 - Tor clients using bridges can now be configured to use a separate
9499 'transport' proxy for each bridge. This approach helps to resist
9500 censorship by allowing bridges to use protocol obfuscation
9501 plugins. It implements part of proposal 180. Implements ticket 2841.
9502 - While we're trying to bootstrap, record how many TLS connections
9503 fail in each state, and report which states saw the most failures
9504 in response to any bootstrap failures. This feature may speed up
9505 diagnosis of censorship events. Implements ticket 3116.
9507 o Major bugfixes (on 0.2.3.1-alpha):
9508 - When configuring a large set of nodes in EntryNodes (as with
9509 'EntryNodes {cc}' or 'EntryNodes 1.1.1.1/16'), choose only a
9510 random subset to be guards, and choose them in random
9511 order. Fixes bug 2798.
9512 - Tor could crash when remembering a consensus in a non-used consensus
9513 flavor without having a current consensus set. Fixes bug 3361.
9514 - Comparing an unknown address to a microdescriptor's shortened exit
9515 policy would always give a "rejected" result. Fixes bug 3599.
9516 - Using microdescriptors as a client no longer prevents Tor from
9517 uploading and downloading hidden service descriptors. Fixes
9521 - Allow nameservers with IPv6 address. Resolves bug 2574.
9522 - Accept attempts to include a password authenticator in the
9523 handshake, as supported by SOCKS5. This handles SOCKS clients that
9524 don't know how to omit a password when authenticating. Resolves
9526 - When configuring a large set of nodes in EntryNodes, and there are
9527 enough of them listed as Guard so that we don't need to consider
9528 the non-guard entries, prefer the ones listed with the Guard flag.
9529 - Check for and recover from inconsistency in the microdescriptor
9530 cache. This will make it harder for us to accidentally free a
9531 microdescriptor without removing it from the appropriate data
9532 structures. Fixes issue 3135; issue noted by "wanoskarnet".
9533 - Log SSL state transitions at log level DEBUG, log domain
9534 HANDSHAKE. This can be useful for debugging censorship events.
9535 Implements ticket 3264.
9536 - Add port 6523 (Gobby) to LongLivedPorts. Patch by intrigeri;
9537 implements ticket 3439.
9539 o Minor bugfixes (on 0.2.3.1-alpha):
9540 - Do not free all general-purpose regular descriptors just
9541 because microdescriptor use is enabled. Fixes bug 3113.
9542 - Correctly link libevent_openssl when --enable-static-libevent
9543 is passed to configure. Fixes bug 3118.
9544 - Bridges should not complain during their heartbeat log messages that
9545 they are unlisted in the consensus: that's more or less the point
9546 of being a bridge. Fixes bug 3183.
9547 - Report a SIGNAL event to controllers when acting on a delayed
9548 SIGNAL NEWNYM command. Previously, we would report a SIGNAL
9549 event to the controller if we acted on a SIGNAL NEWNYM command
9550 immediately, and otherwise not report a SIGNAL event for the
9551 command at all. Fixes bug 3349.
9552 - Fix a crash when handling the SIGNAL controller command or
9553 reporting ERR-level status events with bufferevents enabled. Found
9554 by Robert Ransom. Fixes bug 3367.
9555 - Always ship the tor-fw-helper manpage in our release tarballs.
9556 Fixes bug 3389. Reported by Stephen Walker.
9557 - Fix a class of double-mark-for-close bugs when bufferevents
9558 are enabled. Fixes bug 3403.
9559 - Update tor-fw-helper to support libnatpmp-20110618. Fixes bug 3434.
9560 - Add SIGNAL to the list returned by the 'GETINFO events/names'
9561 control-port command. Fixes part of bug 3465.
9562 - Prevent using negative indices during unit test runs when read_all()
9563 fails. Spotted by coverity.
9564 - Fix a rare memory leak when checking the nodelist without it being
9565 present. Found by coverity.
9566 - Only try to download a microdescriptor-flavored consensus from
9567 a directory cache that provides them.
9569 o Minor bugfixes (on 0.2.2.x and earlier):
9570 - Assert that hidden-service-related operations are not performed
9571 using single-hop circuits. Previously, Tor would assert that
9572 client-side streams are not attached to single-hop circuits,
9573 but not that other sensitive operations on the client and service
9574 side are not performed using single-hop circuits. Fixes bug 3332;
9576 - Don't publish a new relay descriptor when we reload our onion key,
9577 unless the onion key has actually changed. Fixes bug 3263 and
9578 resolves another cause of bug 1810. Bugfix on 0.1.1.11-alpha.
9579 - Allow GETINFO fingerprint to return a fingerprint even when
9580 we have not yet built a router descriptor. Fixes bug 3577;
9581 bugfix on 0.2.0.1-alpha.
9582 - Make 'tor --digests' list hashes of all Tor source files. Bugfix
9583 on 0.2.2.4-alpha; fixes bug 3427.
9585 o Code simplification and refactoring:
9586 - Use tor_sscanf() in place of scanf() in more places through the
9587 code. This makes us a little more locale-independent, and
9588 should help shut up code-analysis tools that can't tell
9589 a safe sscanf string from a dangerous one.
9590 - Use tt_assert(), not tor_assert(), for checking for test failures.
9591 This makes the unit tests more able to go on in the event that
9593 - Split connection_about_to_close() into separate functions for each
9597 - On Windows, we now define the _WIN32_WINNT macros only if they
9598 are not already defined. This lets the person building Tor decide,
9599 if they want, to require a later version of Windows.
9602 Changes in version 0.2.2.30-rc - 2011-07-07
9603 Tor 0.2.2.30-rc is the first release candidate for the Tor 0.2.2.x
9604 series. It fixes a few smaller bugs, but generally appears stable.
9605 Please test it and let us know whether it is!
9608 - Send a SUCCEEDED stream event to the controller when a reverse
9609 resolve succeeded. Fixes bug 3536; bugfix on 0.0.8pre1. Issue
9610 discovered by katmagic.
9611 - Always NUL-terminate the sun_path field of a sockaddr_un before
9612 passing it to the kernel. (Not a security issue: kernels are
9613 smart enough to reject bad sockaddr_uns.) Found by Coverity;
9614 CID #428. Bugfix on Tor 0.2.0.3-alpha.
9615 - Don't stack-allocate the list of supplementary GIDs when we're
9616 about to log them. Stack-allocating NGROUPS_MAX gid_t elements
9617 could take up to 256K, which is way too much stack. Found by
9618 Coverity; CID #450. Bugfix on 0.2.1.7-alpha.
9619 - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO
9620 events/names' control-port command. Bugfix on 0.2.2.9-alpha;
9621 fixes part of bug 3465.
9622 - Fix a memory leak when receiving a descriptor for a hidden
9623 service we didn't ask for. Found by Coverity; CID #30. Bugfix
9627 - Update to the July 1 2011 Maxmind GeoLite Country database.
9630 Changes in version 0.2.2.29-beta - 2011-06-20
9631 Tor 0.2.2.29-beta reverts an accidental behavior change for users who
9632 have bridge lines in their torrc but don't want to use them; gets
9633 us closer to having the control socket feature working on Debian;
9634 and fixes a variety of smaller bugs.
9637 - Revert the UseBridges option to its behavior before 0.2.2.28-beta.
9638 When we changed the default behavior to "use bridges if any
9639 are listed in the torrc", we surprised users who had bridges
9640 in their torrc files but who didn't actually want to use them.
9641 Partial resolution for bug 3354.
9644 - Don't attach new streams to old rendezvous circuits after SIGNAL
9645 NEWNYM. Previously, we would keep using an existing rendezvous
9646 circuit if it remained open (i.e. if it were kept open by a
9647 long-lived stream, or if a new stream were attached to it before
9648 Tor could notice that it was old and no longer in use). Bugfix on
9649 0.1.1.15-rc; fixes bug 3375.
9652 - Fix a bug when using ControlSocketsGroupWritable with User. The
9653 directory's group would be checked against the current group, not
9654 the configured group. Patch by Jérémy Bobbio. Fixes bug 3393;
9655 bugfix on 0.2.2.26-beta.
9656 - Make connection_printf_to_buf()'s behavior sane. Its callers
9657 expect it to emit a CRLF iff the format string ends with CRLF;
9658 it actually emitted a CRLF iff (a) the format string ended with
9659 CRLF or (b) the resulting string was over 1023 characters long or
9660 (c) the format string did not end with CRLF *and* the resulting
9661 string was 1021 characters long or longer. Bugfix on 0.1.1.9-alpha;
9662 fixes part of bug 3407.
9663 - Make send_control_event_impl()'s behavior sane. Its callers
9664 expect it to always emit a CRLF at the end of the string; it
9665 might have emitted extra control characters as well. Bugfix on
9666 0.1.1.9-alpha; fixes another part of bug 3407.
9667 - Make crypto_rand_int() check the value of its input correctly.
9668 Previously, it accepted values up to UINT_MAX, but could return a
9669 negative number if given a value above INT_MAX+1. Found by George
9670 Kadianakis. Fixes bug 3306; bugfix on 0.2.2pre14.
9671 - Avoid a segfault when reading a malformed circuit build state
9672 with more than INT_MAX entries. Found by wanoskarnet. Bugfix on
9674 - When asked about a DNS record type we don't support via a
9675 client DNSPort, reply with NOTIMPL rather than an empty
9676 reply. Patch by intrigeri. Fixes bug 3369; bugfix on 2.0.1-alpha.
9677 - Fix a rare memory leak during stats writing. Found by coverity.
9680 - Update to the June 1 2011 Maxmind GeoLite Country database.
9682 o Code simplifications and refactoring:
9683 - Remove some dead code as indicated by coverity.
9684 - Remove a few dead assignments during router parsing. Found by
9686 - Add some forgotten return value checks during unit tests. Found
9688 - Don't use 1-bit wide signed bit fields. Found by coverity.
9691 Changes in version 0.2.2.28-beta - 2011-06-04
9692 Tor 0.2.2.28-beta makes great progress towards a new stable release: we
9693 fixed a big bug in whether relays stay in the consensus consistently,
9694 we moved closer to handling bridges and hidden services correctly,
9695 and we started the process of better handling the dreaded "my Vidalia
9696 died, and now my Tor demands a password when I try to reconnect to it"
9700 - Don't decide to make a new descriptor when receiving a HUP signal.
9701 This bug has caused a lot of 0.2.2.x relays to disappear from the
9702 consensus periodically. Fixes the most common case of triggering
9703 bug 1810; bugfix on 0.2.2.7-alpha.
9704 - Actually allow nameservers with IPv6 addresses. Fixes bug 2574.
9705 - Don't try to build descriptors if "ORPort auto" is set and we
9706 don't know our actual ORPort yet. Fix for bug 3216; bugfix on
9708 - Resolve a crash that occurred when setting BridgeRelay to 1 with
9709 accounting enabled. Fixes bug 3228; bugfix on 0.2.2.18-alpha.
9710 - Apply circuit timeouts to opened hidden-service-related circuits
9711 based on the correct start time. Previously, we would apply the
9712 circuit build timeout based on time since the circuit's creation;
9713 it was supposed to be applied based on time since the circuit
9714 entered its current state. Bugfix on 0.0.6; fixes part of bug 1297.
9715 - Use the same circuit timeout for client-side introduction
9716 circuits as for other four-hop circuits, rather than the timeout
9717 for single-hop directory-fetch circuits; the shorter timeout may
9718 have been appropriate with the static circuit build timeout in
9719 0.2.1.x and earlier, but caused many hidden service access attempts
9720 to fail with the adaptive CBT introduced in 0.2.2.2-alpha. Bugfix
9721 on 0.2.2.2-alpha; fixes another part of bug 1297.
9722 - In ticket 2511 we fixed a case where you could use an unconfigured
9723 bridge if you had configured it as a bridge the last time you ran
9724 Tor. Now fix another edge case: if you had configured it as a bridge
9725 but then switched to a different bridge via the controller, you
9726 would still be willing to use the old one. Bugfix on 0.2.0.1-alpha;
9730 - Add an __OwningControllerProcess configuration option and a
9731 TAKEOWNERSHIP control-port command. Now a Tor controller can ensure
9732 that when it exits, Tor will shut down. Implements feature 3049.
9733 - If "UseBridges 1" is set and no bridges are configured, Tor will
9734 now refuse to build any circuits until some bridges are set.
9735 If "UseBridges auto" is set, Tor will use bridges if they are
9736 configured and we are not running as a server, but otherwise will
9737 make circuits as usual. The new default is "auto". Patch by anonym,
9738 so the Tails LiveCD can stop automatically revealing you as a Tor
9742 - Fix warnings from GCC 4.6's "-Wunused-but-set-variable" option.
9743 - Remove a trailing asterisk from "exit-policy/default" in the
9744 output of the control port command "GETINFO info/names". Bugfix
9746 - Use a wide type to hold sockets when built for 64-bit Windows builds.
9748 - Warn when the user configures two HiddenServiceDir lines that point
9749 to the same directory. Bugfix on 0.0.6 (the version introducing
9750 HiddenServiceDir); fixes bug 3289.
9751 - Remove dead code from rend_cache_lookup_v2_desc_as_dir. Fixes
9752 part of bug 2748; bugfix on 0.2.0.10-alpha.
9753 - Log malformed requests for rendezvous descriptors as protocol
9754 warnings, not warnings. Also, use a more informative log message
9755 in case someone sees it at log level warning without prior
9756 info-level messages. Fixes the other part of bug 2748; bugfix
9758 - Clear the table recording the time of the last request for each
9759 hidden service descriptor from each HS directory on SIGNAL NEWNYM.
9760 Previously, we would clear our HS descriptor cache on SIGNAL
9761 NEWNYM, but if we had previously retrieved a descriptor (or tried
9762 to) from every directory responsible for it, we would refuse to
9763 fetch it again for up to 15 minutes. Bugfix on 0.2.2.25-alpha;
9765 - Fix a log message that said "bits" while displaying a value in
9766 bytes. Found by wanoskarnet. Fixes bug 3318; bugfix on
9768 - When checking for 1024-bit keys, check for 1024 bits, not 128
9769 bytes. This allows Tor to correctly discard keys of length 1017
9770 through 1023. Bugfix on 0.0.9pre5.
9773 - Relays now log the reason for publishing a new relay descriptor,
9774 so we have a better chance of hunting down instances of bug 1810.
9775 Resolves ticket 3252.
9776 - Revise most log messages that refer to nodes by nickname to
9777 instead use the "$key=nickname at address" format. This should be
9778 more useful, especially since nicknames are less and less likely
9779 to be unique. Resolves ticket 3045.
9780 - Log (at info level) when purging pieces of hidden-service-client
9781 state because of SIGNAL NEWNYM.
9784 - Remove undocumented option "-F" from tor-resolve: it hasn't done
9785 anything since 0.2.1.16-rc.
9788 Changes in version 0.2.2.27-beta - 2011-05-18
9789 Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
9790 release, and also adds a few more general bugfixes.
9793 - Fix a crash bug when changing bridges in a running Tor process.
9794 Fixes bug 3213; bugfix on 0.2.2.26-beta.
9795 - When the controller configures a new bridge, don't wait 10 to 60
9796 seconds before trying to fetch its descriptor. Bugfix on
9797 0.2.0.3-alpha; fixes bug 3198 (suggested by 2355).
9800 - Require that onion keys have exponent 65537 in microdescriptors too.
9801 Fixes more of bug 3207; bugfix on 0.2.2.26-beta.
9802 - Tor used to limit HttpProxyAuthenticator values to 48 characters.
9803 Changed the limit to 512 characters by removing base64 newlines.
9804 Fixes bug 2752. Fix by Michael Yakubovich.
9805 - When a client starts or stops using bridges, never use a circuit
9806 that was built before the configuration change. This behavior could
9807 put at risk a user who uses bridges to ensure that her traffic
9808 only goes to the chosen addresses. Bugfix on 0.2.0.3-alpha; fixes
9812 Changes in version 0.2.2.26-beta - 2011-05-17
9813 Tor 0.2.2.26-beta fixes a variety of potential privacy problems. It
9814 also introduces a new "socksport auto" approach that should make it
9815 easier to run multiple Tors on the same system, and does a lot of
9816 cleanup to get us closer to a release candidate.
9818 o Security/privacy fixes:
9819 - Replace all potentially sensitive memory comparison operations
9820 with versions whose runtime does not depend on the data being
9821 compared. This will help resist a class of attacks where an
9822 adversary can use variations in timing information to learn
9823 sensitive data. Fix for one case of bug 3122. (Safe memcmp
9824 implementation by Robert Ransom based partially on code by DJB.)
9825 - When receiving a hidden service descriptor, check that it is for
9826 the hidden service we wanted. Previously, Tor would store any
9827 hidden service descriptors that a directory gave it, whether it
9828 wanted them or not. This wouldn't have let an attacker impersonate
9829 a hidden service, but it did let directories pre-seed a client
9830 with descriptors that it didn't want. Bugfix on 0.0.6.
9831 - On SIGHUP, do not clear out all TrackHostExits mappings, client
9832 DNS cache entries, and virtual address mappings: that's what
9833 NEWNYM is for. Fixes bug 1345; bugfix on 0.1.0.1-rc.
9836 - The options SocksPort, ControlPort, and so on now all accept a
9837 value "auto" that opens a socket on an OS-selected port. A
9838 new ControlPortWriteToFile option tells Tor to write its
9839 actual control port or ports to a chosen file. If the option
9840 ControlPortFileGroupReadable is set, the file is created as
9841 group-readable. Now users can run two Tor clients on the same
9842 system without needing to manually mess with parameters. Resolves
9843 part of ticket 3076.
9844 - Set SO_REUSEADDR on all sockets, not just listeners. This should
9845 help busy exit nodes avoid running out of useable ports just
9846 because all the ports have been used in the near past. Resolves
9850 - New "GETINFO net/listeners/(type)" controller command to return
9851 a list of addresses and ports that are bound for listeners for a
9852 given connection type. This is useful when the user has configured
9853 "SocksPort auto" and the controller needs to know which port got
9854 chosen. Resolves another part of ticket 3076.
9855 - Add a new ControlSocketsGroupWritable configuration option: when
9856 it is turned on, ControlSockets are group-writeable by the default
9857 group of the current user. Patch by Jérémy Bobbio; implements
9859 - Tor now refuses to create a ControlSocket in a directory that is
9860 world-readable (or group-readable if ControlSocketsGroupWritable
9861 is 0). This is necessary because some operating systems do not
9862 enforce permissions on an AF_UNIX sockets. Permissions on the
9863 directory holding the socket, however, seems to work everywhere.
9864 - Rate-limit a warning about failures to download v2 networkstatus
9865 documents. Resolves part of bug 1352.
9866 - Backport code from 0.2.3.x that allows directory authorities to
9867 clean their microdescriptor caches. Needed to resolve bug 2230.
9868 - When an HTTPS proxy reports "403 Forbidden", we now explain
9869 what it means rather than calling it an unexpected status code.
9870 Closes bug 2503. Patch from Michael Yakubovich.
9871 - Update to the May 1 2011 Maxmind GeoLite Country database.
9874 - Authorities now clean their microdesc cache periodically and when
9875 reading from disk initially, not only when adding new descriptors.
9876 This prevents a bug where we could lose microdescriptors. Bugfix
9877 on 0.2.2.6-alpha. Fixes bug 2230.
9878 - Do not crash when our configuration file becomes unreadable, for
9879 example due to a permissions change, between when we start up
9880 and when a controller calls SAVECONF. Fixes bug 3135; bugfix
9882 - Avoid a bug that would keep us from replacing a microdescriptor
9883 cache on Windows. (We would try to replace the file while still
9884 holding it open. That's fine on Unix, but Windows doesn't let us
9885 do that.) Bugfix on 0.2.2.6-alpha; bug found by wanoskarnet.
9886 - Add missing explanations for the authority-related torrc options
9887 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey in the
9888 man page. Resolves issue 2379.
9889 - As an authority, do not upload our own vote or signature set to
9890 ourself. It would tell us nothing new, and as of 0.2.2.24-alpha,
9891 it would get flagged as a duplicate. Resolves bug 3026.
9892 - Accept hidden service descriptors if we think we might be a hidden
9893 service directory, regardless of what our consensus says. This
9894 helps robustness, since clients and hidden services can sometimes
9895 have a more up-to-date view of the network consensus than we do,
9896 and if they think that the directory authorities list us a HSDir,
9897 we might actually be one. Related to bug 2732; bugfix on
9899 - When a controller changes TrackHostExits, remove mappings for
9900 hosts that should no longer have their exits tracked. Bugfix on
9902 - When a controller changes VirtualAddrNetwork, remove any mappings
9903 for hosts that were automapped to the old network. Bugfix on
9905 - When a controller changes one of the AutomapHosts* options, remove
9906 any mappings for hosts that should no longer be automapped. Bugfix
9908 - Do not reset the bridge descriptor download status every time we
9909 re-parse our configuration or get a configuration change. Fixes
9910 bug 3019; bugfix on 0.2.0.3-alpha.
9912 o Minor bugfixes (code cleanup):
9913 - When loading the microdesc journal, remember its current size.
9914 In 0.2.2, this helps prevent the microdesc journal from growing
9915 without limit on authorities (who are the only ones to use it in
9916 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
9917 Fix posted by "cypherpunks."
9918 - The microdesc journal is supposed to get rebuilt only if it is
9919 at least _half_ the length of the store, not _twice_ the length
9920 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
9921 - Fix a potential null-pointer dereference while computing a
9922 consensus. Bugfix on 0.2.0.3-alpha, found with the help of
9924 - Avoid a possible null-pointer dereference when rebuilding the mdesc
9925 cache without actually having any descriptors to cache. Bugfix on
9926 0.2.2.6-alpha. Issue discovered using clang's static analyzer.
9927 - If we fail to compute the identity digest of a v3 legacy keypair,
9928 warn, and don't use a buffer-full of junk instead. Bugfix on
9929 0.2.1.1-alpha; fixes bug 3106.
9930 - Resolve an untriggerable issue in smartlist_string_num_isin(),
9931 where if the function had ever in the future been used to check
9932 for the presence of a too-large number, it would have given an
9933 incorrect result. (Fortunately, we only used it for 16-bit
9934 values.) Fixes bug 3175; bugfix on 0.1.0.1-rc.
9935 - Require that introduction point keys and onion handshake keys
9936 have a public exponent of 65537. Starts to fix bug 3207; bugfix
9940 - Caches no longer download and serve v2 networkstatus documents
9941 unless FetchV2Networkstatus flag is set: these documents haven't
9942 haven't been used by clients or relays since 0.2.0.x. Resolves
9946 Changes in version 0.2.3.1-alpha - 2011-05-05
9947 Tor 0.2.3.1-alpha adds some new experimental features, including support
9948 for an improved network IO backend, IOCP networking on Windows,
9949 microdescriptor caching, "fast-start" support for streams, and automatic
9950 home router configuration. There are also numerous internal improvements
9951 to try to make the code easier for developers to work with.
9953 This is the first alpha release in a new series, so expect there to be
9954 bugs. Users who would rather test out a more stable branch should
9955 stay with 0.2.2.x for now.
9958 - Tor can now optionally build with the "bufferevents" buffered IO
9959 backend provided by Libevent 2. To use this feature, make sure you
9960 have the latest possible version of Libevent, and pass the
9961 --enable-bufferevents flag to configure when building Tor from
9962 source. This feature will make our networking code more flexible,
9963 let us stack layers on each other, and let us use more efficient
9964 zero-copy transports where available.
9965 - As an experimental feature, Tor can use IOCP for networking on Windows.
9966 Once this code is tuned and optimized, it promises much better
9967 performance than the select-based backend we've used in the past. To
9968 try this feature, you must build Tor with Libevent 2, configure Tor
9969 with the "bufferevents" buffered IO backend, and add "DisableIOCP 0" to
9970 your torrc. There are known bugs here: only try this if you can help
9971 debug it as it breaks.
9972 - The EntryNodes option can now include country codes like {de} or IP
9973 addresses or network masks. Previously we had disallowed these options
9974 because we didn't have an efficient way to keep the list up to
9975 date. Fixes bug 1982, but see bug 2798 for an unresolved issue here.
9976 - Exit nodes now accept and queue data on not-yet-connected streams.
9977 Previously, the client wasn't allowed to send data until the stream was
9978 connected, which slowed down all connections. This change will enable
9979 clients to perform a "fast-start" on streams and send data without
9980 having to wait for a confirmation that the stream has opened. (Patch
9981 from Ian Goldberg; implements the server side of Proposal 174.)
9982 - Tor now has initial support for automatic port mapping on the many
9983 home routers that support NAT-PMP or UPnP. (Not yet supported on
9984 Windows). To build the support code, you'll need to have libnatpnp
9985 library and/or the libminiupnpc library, and you'll need to enable the
9986 feature specifically by passing "--enable-upnp" and/or
9987 "--enable-natpnp" to configure. To turn it on, use the new
9988 PortForwarding option.
9989 - Caches now download, cache, and serve multiple "flavors" of the
9990 consensus, including a flavor that describes microdescriptors.
9991 - Caches now download, cache, and serve microdescriptors -- small
9992 summaries of router descriptors that are authenticated by all of the
9993 directory authorities. Once enough caches are running this code,
9994 clients will be able to save significant amounts of directory bandwidth
9995 by downloading microdescriptors instead of router descriptors.
9998 - Make logging resolution configurable with a new LogTimeGranularity
9999 option, and change the default from 1 millisecond to 1 second.
10000 Implements enhancement 1668.
10001 - We log which torrc file we're using on startup. Implements ticket
10003 - Ordinarily, Tor does not count traffic from private addresses (like
10004 127.0.0.1 or 10.0.0.1) when calculating rate limits or accounting.
10005 There is now a new option, CountPrivateBandwidth, to disable this
10006 behavior. Patch from Daniel Cagara.
10007 - New --enable-static-tor configure option for building Tor as
10008 statically as possible. Idea, general hackery and thoughts from
10009 Alexei Czeskis, John Gilmore, Jacob Appelbaum. Implements ticket
10011 - If you set the NumCPUs option to 0, Tor will now try to detect how
10012 many CPUs you have. This is the new default behavior.
10013 - Turn on directory request statistics by default and include them in
10014 extra-info descriptors. Don't break if we have no GeoIP database.
10015 - Relays that set "ConnDirectionStatistics 1" write statistics on the
10016 bidirectional use of connections to disk every 24 hours.
10017 - Add a GeoIP file digest to the extra-info descriptor. Implements
10019 - The NodeFamily option -- which let you declare that you want to
10020 consider nodes to be part of a family whether they list themselves
10021 that way or not -- now allows IP address ranges and country codes.
10022 - Add a new 'Heartbeat' log message type to periodically log a message
10023 describing Tor's status at level Notice. This feature is meant for
10024 operators who log at notice, and want to make sure that their Tor
10025 server is still working. Implementation by George Kadianakis.
10027 o Minor bugfixes (on 0.2.2.25-alpha):
10028 - When loading the microdesc journal, remember its current size.
10029 In 0.2.2, this helps prevent the microdesc journal from growing
10030 without limit on authorities (who are the only ones to use it in
10031 0.2.2). Fixes a part of bug 2230; bugfix on 0.2.2.6-alpha.
10032 Fix posted by "cypherpunks."
10033 - The microdesc journal is supposed to get rebuilt only if it is
10034 at least _half_ the length of the store, not _twice_ the length
10035 of the store. Bugfix on 0.2.2.6-alpha; fixes part of bug 2230.
10036 - If as an authority we fail to compute the identity digest of a v3
10037 legacy keypair, warn, and don't use a buffer-full of junk instead.
10038 Bugfix on 0.2.1.1-alpha; fixes bug 3106.
10039 - Authorities now clean their microdesc cache periodically and when
10040 reading from disk initially, not only when adding new descriptors.
10041 This prevents a bug where we could lose microdescriptors. Bugfix
10044 o Minor features (controller):
10045 - Add a new SIGNAL event to the controller interface so that
10046 controllers can be notified when Tor handles a signal. Resolves
10047 issue 1955. Patch by John Brooks.
10048 - Add a new GETINFO option to get total bytes read and written. Patch
10049 from pipe, revised by atagar. Resolves ticket 2345.
10050 - Implement some GETINFO controller fields to provide information about
10051 the Tor process's pid, euid, username, and resource limits.
10054 - Our build system requires automake 1.6 or later to create the
10055 Makefile.in files. Previously, you could have used 1.4.
10056 This only affects developers and people building Tor from git;
10057 people who build Tor from the source distribution without changing
10058 the Makefile.am files should be fine.
10059 - Our autogen.sh script uses autoreconf to launch autoconf, automake, and
10060 so on. This is more robust against some of the failure modes
10061 associated with running the autotools pieces on their own.
10063 o Minor packaging issues:
10064 - On OpenSUSE, create the /var/run/tor directory on startup if it is not
10065 already created. Patch from Andreas Stieger. Fixes bug 2573.
10067 o Code simplifications and refactoring:
10068 - A major revision to our internal node-selecting and listing logic.
10069 Tor already had at least two major ways to look at the question of
10070 "which Tor servers do we know about": a list of router descriptors,
10071 and a list of entries in the current consensus. With
10072 microdescriptors, we're adding a third. Having so many systems
10073 without an abstraction layer over them was hurting the codebase.
10074 Now, we have a new "node_t" abstraction that presents a consistent
10075 interface to a client's view of a Tor node, and holds (nearly) all
10076 of the mutable state formerly in routerinfo_t and routerstatus_t.
10077 - The helper programs tor-gencert, tor-resolve, and tor-checkkey
10078 no longer link against Libevent: they never used it, but
10079 our library structure used to force them to link it.
10081 o Removed features:
10082 - Remove some old code to work around even older versions of Tor that
10083 used forked processes to handle DNS requests. Such versions of Tor
10084 are no longer in use as servers.
10086 o Documentation fixes:
10087 - Correct a broken faq link in the INSTALL file. Fixes bug 2307.
10088 - Add missing documentation for the authority-related torrc options
10089 RephistTrackTime, BridgePassword, and V3AuthUseLegacyKey. Resolves
10093 Changes in version 0.2.2.25-alpha - 2011-04-29
10094 Tor 0.2.2.25-alpha fixes many bugs: hidden service clients are more
10095 robust, routers no longer overreport their bandwidth, Win7 should crash
10096 a little less, and NEWNYM (as used by Vidalia's "new identity" button)
10097 now prevents hidden service-related activity from being linkable. It
10098 provides more information to Vidalia so you can see if your bridge is
10099 working. Also, 0.2.2.25-alpha revamps the Entry/Exit/ExcludeNodes and
10100 StrictNodes configuration options to make them more reliable, more
10101 understandable, and more regularly applied. If you use those options,
10102 please see the revised documentation for them in the manual page.
10105 - Relays were publishing grossly inflated bandwidth values because
10106 they were writing their state files wrong--now they write the
10107 correct value. Also, resume reading bandwidth history from the
10108 state file correctly. Fixes bug 2704; bugfix on 0.2.2.23-alpha.
10109 - Improve hidden service robustness: When we find that we have
10110 extended a hidden service's introduction circuit to a relay not
10111 listed as an introduction point in the HS descriptor we currently
10112 have, retry with an introduction point from the current
10113 descriptor. Previously we would just give up. Fixes bugs 1024 and
10114 1930; bugfix on 0.2.0.10-alpha.
10115 - Clients now stop trying to use an exit node associated with a given
10116 destination by TrackHostExits if they fail to reach that exit node.
10117 Fixes bug 2999. Bugfix on 0.2.0.20-rc.
10118 - Fix crash bug on platforms where gmtime and localtime can return
10119 NULL. Windows 7 users were running into this one. Fixes part of bug
10120 2077. Bugfix on all versions of Tor. Found by boboper.
10122 o Security and stability fixes:
10123 - Don't double-free a parsable, but invalid, microdescriptor, even if
10124 it is followed in the blob we're parsing by an unparsable
10125 microdescriptor. Fixes an issue reported in a comment on bug 2954.
10126 Bugfix on 0.2.2.6-alpha; fix by "cypherpunks".
10127 - If the Nickname configuration option isn't given, Tor would pick a
10128 nickname based on the local hostname as the nickname for a relay.
10129 Because nicknames are not very important in today's Tor and the
10130 "Unnamed" nickname has been implemented, this is now problematic
10131 behavior: It leaks information about the hostname without being
10132 useful at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which
10133 introduced the Unnamed nickname. Reported by tagnaq.
10134 - Fix an uncommon assertion failure when running with DNSPort under
10135 heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha.
10136 - Avoid linkability based on cached hidden service descriptors: forget
10137 all hidden service descriptors cached as a client when processing a
10138 SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6.
10141 - Export GeoIP information on bridge usage to controllers even if we
10142 have not yet been running for 24 hours. Now Vidalia bridge operators
10143 can get more accurate and immediate feedback about their
10144 contributions to the network.
10146 o Major features and bugfixes (node selection):
10147 - Revise and reconcile the meaning of the ExitNodes, EntryNodes,
10148 ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes
10149 options. Previously, we had been ambiguous in describing what
10150 counted as an "exit" node, and what operations exactly "StrictNodes
10151 0" would permit. This created confusion when people saw nodes built
10152 through unexpected circuits, and made it hard to tell real bugs from
10153 surprises. Now the intended behavior is:
10154 . "Exit", in the context of ExitNodes and ExcludeExitNodes, means
10155 a node that delivers user traffic outside the Tor network.
10156 . "Entry", in the context of EntryNodes, means a node used as the
10157 first hop of a multihop circuit. It doesn't include direct
10158 connections to directory servers.
10159 . "ExcludeNodes" applies to all nodes.
10160 . "StrictNodes" changes the behavior of ExcludeNodes only. When
10161 StrictNodes is set, Tor should avoid all nodes listed in
10162 ExcludeNodes, even when it will make user requests fail. When
10163 StrictNodes is *not* set, then Tor should follow ExcludeNodes
10164 whenever it can, except when it must use an excluded node to
10165 perform self-tests, connect to a hidden service, provide a
10166 hidden service, fulfill a .exit request, upload directory
10167 information, or fetch directory information.
10168 Collectively, the changes to implement the behavior fix bug 1090.
10169 - ExcludeNodes now takes precedence over EntryNodes and ExitNodes: if
10170 a node is listed in both, it's treated as excluded.
10171 - ExcludeNodes now applies to directory nodes -- as a preference if
10172 StrictNodes is 0, or an absolute requirement if StrictNodes is 1.
10173 Don't exclude all the directory authorities and set StrictNodes to 1
10174 unless you really want your Tor to break.
10175 - ExcludeNodes and ExcludeExitNodes now override exit enclaving.
10176 - ExcludeExitNodes now overrides .exit requests.
10177 - We don't use bridges listed in ExcludeNodes.
10178 - When StrictNodes is 1:
10179 . We now apply ExcludeNodes to hidden service introduction points
10180 and to rendezvous points selected by hidden service users. This
10181 can make your hidden service less reliable: use it with caution!
10182 . If we have used ExcludeNodes on ourself, do not try relay
10183 reachability self-tests.
10184 . If we have excluded all the directory authorities, we will not
10185 even try to upload our descriptor if we're a relay.
10186 . Do not honor .exit requests to an excluded node.
10187 - Remove a misfeature that caused us to ignore the Fast/Stable flags
10188 when ExitNodes is set. Bugfix on 0.2.2.7-alpha.
10189 - When the set of permitted nodes changes, we now remove any mappings
10190 introduced via TrackExitHosts to now-excluded nodes. Bugfix on
10192 - We never cannibalize a circuit that had excluded nodes on it, even
10193 if StrictNodes is 0. Bugfix on 0.1.0.1-rc.
10194 - Revert a change where we would be laxer about attaching streams to
10195 circuits than when building the circuits. This was meant to prevent
10196 a set of bugs where streams were never attachable, but our improved
10197 code here should make this unnecessary. Bugfix on 0.2.2.7-alpha.
10198 - Keep track of how many times we launch a new circuit to handle a
10199 given stream. Too many launches could indicate an inconsistency
10200 between our "launch a circuit to handle this stream" logic and our
10201 "attach this stream to one of the available circuits" logic.
10202 - Improve log messages related to excluded nodes.
10205 - Fix a spurious warning when moving from a short month to a long
10206 month on relays with month-based BandwidthAccounting. Bugfix on
10207 0.2.2.17-alpha; fixes bug 3020.
10208 - When a client finds that an origin circuit has run out of 16-bit
10209 stream IDs, we now mark it as unusable for new streams. Previously,
10210 we would try to close the entire circuit. Bugfix on 0.0.6.
10211 - Add a forgotten cast that caused a compile warning on OS X 10.6.
10212 Bugfix on 0.2.2.24-alpha.
10213 - Be more careful about reporting the correct error from a failed
10214 connect() system call. Under some circumstances, it was possible to
10215 look at an incorrect value for errno when sending the end reason.
10216 Bugfix on 0.1.0.1-rc.
10217 - Correctly handle an "impossible" overflow cases in connection byte
10218 counting, where we write or read more than 4GB on an edge connection
10219 in a single second. Bugfix on 0.1.2.8-beta.
10220 - Correct the warning displayed when a rendezvous descriptor exceeds
10221 the maximum size. Fixes bug 2750; bugfix on 0.2.1.5-alpha. Found by
10223 - Clients and hidden services now use HSDir-flagged relays for hidden
10224 service descriptor downloads and uploads even if the relays have no
10225 DirPort set and the client has disabled TunnelDirConns. This will
10226 eventually allow us to give the HSDir flag to relays with no
10227 DirPort. Fixes bug 2722; bugfix on 0.2.1.6-alpha.
10228 - Downgrade "no current certificates known for authority" message from
10229 Notice to Info. Fixes bug 2899; bugfix on 0.2.0.10-alpha.
10230 - Make the SIGNAL DUMP control-port command work on FreeBSD. Fixes bug
10231 2917. Bugfix on 0.1.1.1-alpha.
10232 - Only limit the lengths of single HS descriptors, even when multiple
10233 HS descriptors are published to an HSDir relay in a single POST
10234 operation. Fixes bug 2948; bugfix on 0.2.1.5-alpha. Found by hsdir.
10235 - Write the current time into the LastWritten line in our state file,
10236 rather than the time from the previous write attempt. Also, stop
10237 trying to use a time of -1 in our log statements. Fixes bug 3039;
10238 bugfix on 0.2.2.14-alpha.
10239 - Be more consistent in our treatment of file system paths. "~" should
10240 get expanded to the user's home directory in the Log config option.
10241 Fixes bug 2971; bugfix on 0.2.0.1-alpha, which introduced the
10242 feature for the -f and --DataDirectory options.
10245 - Make sure every relay writes a state file at least every 12 hours.
10246 Previously, a relay could go for weeks without writing its state
10247 file, and on a crash could lose its bandwidth history, capacity
10248 estimates, client country statistics, and so on. Addresses bug 3012.
10249 - Send END_STREAM_REASON_NOROUTE in response to EHOSTUNREACH errors.
10250 Clients before 0.2.1.27 didn't handle NOROUTE correctly, but such
10251 clients are already deprecated because of security bugs.
10252 - Don't allow v0 hidden service authorities to act as clients.
10253 Required by fix for bug 3000.
10254 - Ignore SIGNAL NEWNYM commands on relay-only Tor instances. Required
10255 by fix for bug 3000.
10256 - Ensure that no empty [dirreq-](read|write)-history lines are added
10257 to an extrainfo document. Implements ticket 2497.
10259 o Code simplification and refactoring:
10260 - Remove workaround code to handle directory responses from servers
10261 that had bug 539 (they would send HTTP status 503 responses _and_
10262 send a body too). Since only server versions before
10263 0.2.0.16-alpha/0.1.2.19 were affected, there is no longer reason to
10264 keep the workaround in place.
10265 - Remove the old 'fuzzy time' logic. It was supposed to be used for
10266 handling calculations where we have a known amount of clock skew and
10267 an allowed amount of unknown skew. But we only used it in three
10268 places, and we never adjusted the known/unknown skew values. This is
10269 still something we might want to do someday, but if we do, we'll
10270 want to do it differently.
10271 - Avoid signed/unsigned comparisons by making SIZE_T_CEILING unsigned.
10272 None of the cases where we did this before were wrong, but by making
10273 this change we avoid warnings. Fixes bug 2475; bugfix on 0.2.1.28.
10274 - Use GetTempDir to find the proper temporary directory location on
10275 Windows when generating temporary files for the unit tests. Patch by
10279 Changes in version 0.2.2.24-alpha - 2011-04-08
10280 Tor 0.2.2.24-alpha fixes a variety of bugs, including a big bug that
10281 prevented Tor clients from effectively using "multihomed" bridges,
10282 that is, bridges that listen on multiple ports or IP addresses so users
10283 can continue to use some of their addresses even if others get blocked.
10286 - Fix a bug where bridge users who configure the non-canonical
10287 address of a bridge automatically switch to its canonical
10288 address. If a bridge listens at more than one address, it should be
10289 able to advertise those addresses independently and any non-blocked
10290 addresses should continue to work. Bugfix on Tor 0.2.0.x. Fixes
10292 - If you configured Tor to use bridge A, and then quit and
10293 configured Tor to use bridge B instead, it would happily continue
10294 to use bridge A if it's still reachable. While this behavior is
10295 a feature if your goal is connectivity, in some scenarios it's a
10296 dangerous bug. Bugfix on Tor 0.2.0.1-alpha; fixes bug 2511.
10297 - Directory authorities now use data collected from their own
10298 uptime observations when choosing whether to assign the HSDir flag
10299 to relays, instead of trusting the uptime value the relay reports in
10300 its descriptor. This change helps prevent an attack where a small
10301 set of nodes with frequently-changing identity keys can blackhole
10302 a hidden service. (Only authorities need upgrade; others will be
10303 fine once they do.) Bugfix on 0.2.0.10-alpha; fixes bug 2709.
10306 - When we restart our relay, we might get a successful connection
10307 from the outside before we've started our reachability tests,
10308 triggering a warning: "ORPort found reachable, but I have no
10309 routerinfo yet. Failing to inform controller of success." This
10310 bug was harmless unless Tor is running under a controller
10311 like Vidalia, in which case the controller would never get a
10312 REACHABILITY_SUCCEEDED status event. Bugfix on 0.1.2.6-alpha;
10314 - Make directory authorities more accurate at recording when
10315 relays that have failed several reachability tests became
10316 unreachable, so we can provide more accuracy at assigning Stable,
10317 Guard, HSDir, etc flags. Bugfix on 0.2.0.6-alpha. Resolves bug 2716.
10318 - Fix an issue that prevented static linking of libevent on
10319 some platforms (notably Linux). Fixes bug 2698; bugfix on
10320 versions 0.2.1.23/0.2.2.8-alpha (the versions introducing
10321 the --with-static-libevent configure option).
10322 - We now ask the other side of a stream (the client or the exit)
10323 for more data on that stream when the amount of queued data on
10324 that stream dips low enough. Previously, we wouldn't ask the
10325 other side for more data until either it sent us more data (which
10326 it wasn't supposed to do if it had exhausted its window!) or we
10327 had completely flushed all our queued data. This flow control fix
10328 should improve throughput. Fixes bug 2756; bugfix on the earliest
10329 released versions of Tor (svn commit r152).
10330 - Avoid a double-mark-for-free warning when failing to attach a
10331 transparent proxy connection. (We thought we had fixed this in
10332 0.2.2.23-alpha, but it turns out our fix was checking the wrong
10333 connection.) Fixes bug 2757; bugfix on 0.1.2.1-alpha (the original
10334 bug) and 0.2.2.23-alpha (the incorrect fix).
10335 - When warning about missing zlib development packages during compile,
10336 give the correct package names. Bugfix on 0.2.0.1-alpha.
10339 - Directory authorities now log the source of a rejected POSTed v3
10340 networkstatus vote.
10341 - Make compilation with clang possible when using
10342 --enable-gcc-warnings by removing two warning options that clang
10343 hasn't implemented yet and by fixing a few warnings. Implements
10345 - When expiring circuits, use microsecond timers rather than
10346 one-second timers. This can avoid an unpleasant situation where a
10347 circuit is launched near the end of one second and expired right
10348 near the beginning of the next, and prevent fluctuations in circuit
10350 - Use computed circuit-build timeouts to decide when to launch
10351 parallel introduction circuits for hidden services. (Previously,
10352 we would retry after 15 seconds.)
10353 - Update to the April 1 2011 Maxmind GeoLite Country database.
10356 - Create the /var/run/tor directory on startup on OpenSUSE if it is
10357 not already created. Patch from Andreas Stieger. Fixes bug 2573.
10359 o Documentation changes:
10360 - Modernize the doxygen configuration file slightly. Fixes bug 2707.
10361 - Resolve all doxygen warnings except those for missing documentation.
10363 - Add doxygen documentation for more functions, fields, and types.
10366 Changes in version 0.2.2.23-alpha - 2011-03-08
10367 Tor 0.2.2.23-alpha lets relays record their bandwidth history so when
10368 they restart they don't lose their bandwidth capacity estimate. This
10369 release also fixes a diverse set of user-facing bugs, ranging from
10370 relays overrunning their rate limiting to clients falsely warning about
10371 clock skew to bridge descriptor leaks by our bridge directory authority.
10374 - Stop sending a CLOCK_SKEW controller status event whenever
10375 we fetch directory information from a relay that has a wrong clock.
10376 Instead, only inform the controller when it's a trusted authority
10377 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10378 the rest of bug 1074.
10379 - Fix an assert in parsing router descriptors containing IPv6
10380 addresses. This one took down the directory authorities when
10381 somebody tried some experimental code. Bugfix on 0.2.1.3-alpha.
10382 - Make the bridge directory authority refuse to answer directory
10383 requests for "all" descriptors. It used to include bridge
10384 descriptors in its answer, which was a major information leak.
10385 Found by "piebeer". Bugfix on 0.2.0.3-alpha.
10386 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10387 Tor would ignore their RelayBandwidthBurst setting,
10388 potentially using more bandwidth than expected. Bugfix on
10389 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10390 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10391 hidserv" in her torrc. The 'hidserv' argument never controlled
10392 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10395 - Relays now save observed peak bandwidth throughput rates to their
10396 state file (along with total usage, which was already saved)
10397 so that they can determine their correct estimated bandwidth on
10398 restart. Resolves bug 1863, where Tor relays would reset their
10399 estimated bandwidth to 0 after restarting.
10400 - Directory authorities now take changes in router IP address and
10401 ORPort into account when determining router stability. Previously,
10402 if a router changed its IP or ORPort, the authorities would not
10403 treat it as having any downtime for the purposes of stability
10404 calculation, whereas clients would experience downtime since the
10405 change could take a while to propagate to them. Resolves issue 1035.
10406 - Enable Address Space Layout Randomization (ASLR) and Data Execution
10407 Prevention (DEP) by default on Windows to make it harder for
10408 attackers to exploit vulnerabilities. Patch from John Brooks.
10410 o Minor bugfixes (on 0.2.1.x and earlier):
10411 - Fix a rare crash bug that could occur when a client was configured
10412 with a large number of bridges. Fixes bug 2629; bugfix on
10413 0.2.1.2-alpha. Bugfix by trac user "shitlei".
10414 - Avoid a double mark-for-free warning when failing to attach a
10415 transparent proxy connection. Bugfix on 0.1.2.1-alpha. Fixes
10417 - Correctly detect failure to allocate an OpenSSL BIO. Fixes bug 2378;
10418 found by "cypherpunks". This bug was introduced before the first
10419 Tor release, in svn commit r110.
10420 - Country codes aren't supported in EntryNodes until 0.2.3.x, so
10421 don't mention them in the manpage. Fixes bug 2450; issue
10422 spotted by keb and G-Lo.
10423 - Fix a bug in bandwidth history state parsing that could have been
10424 triggered if a future version of Tor ever changed the timing
10425 granularity at which bandwidth history is measured. Bugfix on
10426 Tor 0.1.1.11-alpha.
10427 - When a relay decides that its DNS is too broken for it to serve
10428 as an exit server, it advertised itself as a non-exit, but
10429 continued to act as an exit. This could create accidental
10430 partitioning opportunities for users. Instead, if a relay is
10431 going to advertise reject *:* as its exit policy, it should
10432 really act with exit policy "reject *:*". Fixes bug 2366.
10433 Bugfix on Tor 0.1.2.5-alpha. Bugfix by user "postman" on trac.
10434 - In the special case where you configure a public exit relay as your
10435 bridge, Tor would be willing to use that exit relay as the last
10436 hop in your circuit as well. Now we fail that circuit instead.
10437 Bugfix on 0.2.0.12-alpha. Fixes bug 2403. Reported by "piebeer".
10438 - Fix a bug with our locking implementation on Windows that couldn't
10439 correctly detect when a file was already locked. Fixes bug 2504,
10440 bugfix on 0.2.1.6-alpha.
10441 - Fix IPv6-related connect() failures on some platforms (BSD, OS X).
10442 Bugfix on 0.2.0.3-alpha; fixes first part of bug 2660. Patch by
10444 - Set target port in get_interface_address6() correctly. Bugfix
10445 on 0.1.1.4-alpha and 0.2.0.3-alpha; fixes second part of bug 2660.
10446 - Directory authorities are now more robust to hops back in time
10447 when calculating router stability. Previously, if a run of uptime
10448 or downtime appeared to be negative, the calculation could give
10449 incorrect results. Bugfix on 0.2.0.6-alpha; noticed when fixing
10451 - Fix an assert that got triggered when using the TestingTorNetwork
10452 configuration option and then issuing a GETINFO config-text control
10453 command. Fixes bug 2250; bugfix on 0.2.1.2-alpha.
10455 o Minor bugfixes (on 0.2.2.x):
10456 - Clients should not weight BadExit nodes as Exits in their node
10457 selection. Similarly, directory authorities should not count BadExit
10458 bandwidth as Exit bandwidth when computing bandwidth-weights.
10459 Bugfix on 0.2.2.10-alpha; fixes bug 2203.
10460 - Correctly clear our dir_read/dir_write history when there is an
10461 error parsing any bw history value from the state file. Bugfix on
10462 Tor 0.2.2.15-alpha.
10463 - Resolve a bug in verifying signatures of directory objects
10464 with digests longer than SHA1. Bugfix on 0.2.2.20-alpha.
10465 Fixes bug 2409. Found by "piebeer".
10466 - Bridge authorities no longer crash on SIGHUP when they try to
10467 publish their relay descriptor to themselves. Fixes bug 2572. Bugfix
10471 - Log less aggressively about circuit timeout changes, and improve
10472 some other circuit timeout messages. Resolves bug 2004.
10473 - Log a little more clearly about the times at which we're no longer
10474 accepting new connections. Resolves bug 2181.
10475 - Reject attempts at the client side to open connections to private
10476 IP addresses (like 127.0.0.1, 10.0.0.1, and so on) with
10477 a randomly chosen exit node. Attempts to do so are always
10478 ill-defined, generally prevented by exit policies, and usually
10479 in error. This will also help to detect loops in transparent
10480 proxy configurations. You can disable this feature by setting
10481 "ClientRejectInternalAddresses 0" in your torrc.
10482 - Always treat failure to allocate an RSA key as an unrecoverable
10484 - Update to the March 1 2011 Maxmind GeoLite Country database.
10486 o Minor features (log subsystem):
10487 - Add documentation for configuring logging at different severities in
10488 different log domains. We've had this feature since 0.2.1.1-alpha,
10489 but for some reason it never made it into the manpage. Fixes
10491 - Make it simpler to specify "All log domains except for A and B".
10492 Previously you needed to say "[*,~A,~B]". Now you can just say
10494 - Add a "LogMessageDomains 1" option to include the domains of log
10495 messages along with the messages. Without this, there's no way
10496 to use log domains without reading the source or doing a lot
10499 o Packaging changes:
10500 - Stop shipping the Tor specs files and development proposal documents
10501 in the tarball. They are now in a separate git repository at
10502 git://git.torproject.org/torspec.git
10505 Changes in version 0.2.1.30 - 2011-02-23
10506 Tor 0.2.1.30 fixes a variety of less critical bugs. The main other
10507 change is a slight tweak to Tor's TLS handshake that makes relays
10508 and bridges that run this new version reachable from Iran again.
10509 We don't expect this tweak will win the arms race long-term, but it
10510 buys us time until we roll out a better solution.
10513 - Stop sending a CLOCK_SKEW controller status event whenever
10514 we fetch directory information from a relay that has a wrong clock.
10515 Instead, only inform the controller when it's a trusted authority
10516 that claims our clock is wrong. Bugfix on 0.1.2.6-alpha; fixes
10517 the rest of bug 1074.
10518 - Fix a bounds-checking error that could allow an attacker to
10519 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10520 Found by "piebeer".
10521 - If relays set RelayBandwidthBurst but not RelayBandwidthRate,
10522 Tor would ignore their RelayBandwidthBurst setting,
10523 potentially using more bandwidth than expected. Bugfix on
10524 0.2.0.1-alpha. Reported by Paul Wouters. Fixes bug 2470.
10525 - Ignore and warn if the user mistakenly sets "PublishServerDescriptor
10526 hidserv" in her torrc. The 'hidserv' argument never controlled
10527 publication of hidden service descriptors. Bugfix on 0.2.0.1-alpha.
10530 - Adjust our TLS Diffie-Hellman parameters to match those used by
10532 - Update to the February 1 2011 Maxmind GeoLite Country database.
10535 - Check for and reject overly long directory certificates and
10536 directory tokens before they have a chance to hit any assertions.
10537 Bugfix on 0.2.1.28. Found by "doorss".
10538 - Bring the logic that gathers routerinfos and assesses the
10539 acceptability of circuits into line. This prevents a Tor OP from
10540 getting locked in a cycle of choosing its local OR as an exit for a
10541 path (due to a .exit request) and then rejecting the circuit because
10542 its OR is not listed yet. It also prevents Tor clients from using an
10543 OR running in the same instance as an exit (due to a .exit request)
10544 if the OR does not meet the same requirements expected of an OR
10545 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10547 o Packaging changes:
10548 - Stop shipping the Tor specs files and development proposal documents
10549 in the tarball. They are now in a separate git repository at
10550 git://git.torproject.org/torspec.git
10551 - Do not include Git version tags as though they are SVN tags when
10552 generating a tarball from inside a repository that has switched
10553 between branches. Bugfix on 0.2.1.15-rc; fixes bug 2402.
10556 Changes in version 0.2.2.22-alpha - 2011-01-25
10557 Tor 0.2.2.22-alpha fixes a few more less-critical security issues. The
10558 main other change is a slight tweak to Tor's TLS handshake that makes
10559 relays and bridges that run this new version reachable from Iran again.
10560 We don't expect this tweak will win the arms race long-term, but it
10561 will buy us a bit more time until we roll out a better solution.
10564 - Fix a bounds-checking error that could allow an attacker to
10565 remotely crash a directory authority. Bugfix on 0.2.1.5-alpha.
10566 Found by "piebeer".
10567 - Don't assert when changing from bridge to relay or vice versa
10568 via the controller. The assert happened because we didn't properly
10569 initialize our keys in this case. Bugfix on 0.2.2.18-alpha; fixes
10570 bug 2433. Reported by bastik.
10573 - Adjust our TLS Diffie-Hellman parameters to match those used by
10575 - Provide a log message stating which geoip file we're parsing
10576 instead of just stating that we're parsing the geoip file.
10577 Implements ticket 2432.
10580 - Check for and reject overly long directory certificates and
10581 directory tokens before they have a chance to hit any assertions.
10582 Bugfix on 0.2.1.28 / 0.2.2.20-alpha. Found by "doorss".
10585 Changes in version 0.2.2.21-alpha - 2011-01-15
10586 Tor 0.2.2.21-alpha includes all the patches from Tor 0.2.1.29, which
10587 continues our recent code security audit work. The main fix resolves
10588 a remote heap overflow vulnerability that can allow remote code
10589 execution (CVE-2011-0427). Other fixes address a variety of assert
10590 and crash bugs, most of which we think are hard to exploit remotely.
10592 o Major bugfixes (security), also included in 0.2.1.29:
10593 - Fix a heap overflow bug where an adversary could cause heap
10594 corruption. This bug probably allows remote code execution
10595 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10597 - Prevent a denial-of-service attack by disallowing any
10598 zlib-compressed data whose compression factor is implausibly
10599 high. Fixes part of bug 2324; reported by "doorss".
10600 - Zero out a few more keys in memory before freeing them. Fixes
10601 bug 2384 and part of bug 2385. These key instances found by
10602 "cypherpunks", based on Andrew Case's report about being able
10603 to find sensitive data in Tor's memory space if you have enough
10604 permissions. Bugfix on 0.0.2pre9.
10606 o Major bugfixes (crashes), also included in 0.2.1.29:
10607 - Prevent calls to Libevent from inside Libevent log handlers.
10608 This had potential to cause a nasty set of crashes, especially
10609 if running Libevent with debug logging enabled, and running
10610 Tor with a controller watching for low-severity log messages.
10611 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10612 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10613 underflow errors there too. Fixes the other part of bug 2324.
10614 - Fix a bug where we would assert if we ever had a
10615 cached-descriptors.new file (or another file read directly into
10616 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10617 on 0.2.1.25. Found by doorss.
10618 - Fix some potential asserts and parsing issues with grossly
10619 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10622 o Minor bugfixes (other), also included in 0.2.1.29:
10623 - Fix a bug with handling misformed replies to reverse DNS lookup
10624 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10625 bug reported by doorss.
10626 - Fix compilation on mingw when a pthreads compatibility library
10627 has been installed. (We don't want to use it, so we shouldn't
10628 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10629 - Fix a bug where we would declare that we had run out of virtual
10630 addresses when the address space was only half-exhausted. Bugfix
10632 - Correctly handle the case where AutomapHostsOnResolve is set but
10633 no virtual addresses are available. Fixes bug 2328; bugfix on
10634 0.1.2.1-alpha. Bug found by doorss.
10635 - Correctly handle wrapping around when we run out of virtual
10636 address space. Found by cypherpunks; bugfix on 0.2.0.5-alpha.
10638 o Minor features, also included in 0.2.1.29:
10639 - Update to the January 1 2011 Maxmind GeoLite Country database.
10640 - Introduce output size checks on all of our decryption functions.
10642 o Build changes, also included in 0.2.1.29:
10643 - Tor does not build packages correctly with Automake 1.6 and earlier;
10644 added a check to Makefile.am to make sure that we're building with
10645 Automake 1.7 or later.
10646 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10647 because we built it with a too-old version of automake. Thus that
10648 release broke ./configure --enable-openbsd-malloc, which is popular
10649 among really fast exit relays on Linux.
10651 o Major bugfixes, new in 0.2.2.21-alpha:
10652 - Prevent crash/heap corruption when the cbtnummodes consensus
10653 parameter is set to 0 or large values. Fixes bug 2317; bugfix
10656 o Major features, new in 0.2.2.21-alpha:
10657 - Introduce minimum/maximum values that clients will believe
10658 from the consensus. Now we'll have a better chance to avoid crashes
10659 or worse when a consensus param has a weird value.
10661 o Minor features, new in 0.2.2.21-alpha:
10662 - Make sure to disable DirPort if running as a bridge. DirPorts aren't
10663 used on bridges, and it makes bridge scanning somewhat easier.
10664 - If writing the state file to disk fails, wait up to an hour before
10665 retrying again, rather than trying again each second. Fixes bug
10666 2346; bugfix on Tor 0.1.1.3-alpha.
10667 - Make Libevent log messages get delivered to controllers later,
10668 and not from inside the Libevent log handler. This prevents unsafe
10669 reentrant Libevent calls while still letting the log messages
10671 - Detect platforms that brokenly use a signed size_t, and refuse to
10672 build there. Found and analyzed by doorss and rransom.
10673 - Fix a bunch of compile warnings revealed by mingw with gcc 4.5.
10676 o Minor bugfixes, new in 0.2.2.21-alpha:
10677 - Handle SOCKS messages longer than 128 bytes long correctly, rather
10678 than waiting forever for them to finish. Fixes bug 2330; bugfix
10679 on 0.2.0.16-alpha. Found by doorss.
10680 - Add assertions to check for overflow in arguments to
10681 base32_encode() and base32_decode(); fix a signed-unsigned
10682 comparison there too. These bugs are not actually reachable in Tor,
10683 but it's good to prevent future errors too. Found by doorss.
10684 - Correctly detect failures to create DNS requests when using Libevent
10685 versions before v2. (Before Libevent 2, we used our own evdns
10686 implementation. Its return values for Libevent's evdns_resolve_*()
10687 functions are not consistent with those from Libevent.) Fixes bug
10688 2363; bugfix on 0.2.2.6-alpha. Found by "lodger".
10690 o Documentation, new in 0.2.2.21-alpha:
10691 - Document the default socks host and port (127.0.0.1:9050) for
10695 Changes in version 0.2.1.29 - 2011-01-15
10696 Tor 0.2.1.29 continues our recent code security audit work. The main
10697 fix resolves a remote heap overflow vulnerability that can allow remote
10698 code execution. Other fixes address a variety of assert and crash bugs,
10699 most of which we think are hard to exploit remotely.
10701 o Major bugfixes (security):
10702 - Fix a heap overflow bug where an adversary could cause heap
10703 corruption. This bug probably allows remote code execution
10704 attacks. Reported by "debuger". Fixes CVE-2011-0427. Bugfix on
10706 - Prevent a denial-of-service attack by disallowing any
10707 zlib-compressed data whose compression factor is implausibly
10708 high. Fixes part of bug 2324; reported by "doorss".
10709 - Zero out a few more keys in memory before freeing them. Fixes
10710 bug 2384 and part of bug 2385. These key instances found by
10711 "cypherpunks", based on Andrew Case's report about being able
10712 to find sensitive data in Tor's memory space if you have enough
10713 permissions. Bugfix on 0.0.2pre9.
10715 o Major bugfixes (crashes):
10716 - Prevent calls to Libevent from inside Libevent log handlers.
10717 This had potential to cause a nasty set of crashes, especially
10718 if running Libevent with debug logging enabled, and running
10719 Tor with a controller watching for low-severity log messages.
10720 Bugfix on 0.1.0.2-rc. Fixes bug 2190.
10721 - Add a check for SIZE_T_MAX to tor_realloc() to try to avoid
10722 underflow errors there too. Fixes the other part of bug 2324.
10723 - Fix a bug where we would assert if we ever had a
10724 cached-descriptors.new file (or another file read directly into
10725 memory) of exactly SIZE_T_CEILING bytes. Fixes bug 2326; bugfix
10726 on 0.2.1.25. Found by doorss.
10727 - Fix some potential asserts and parsing issues with grossly
10728 malformed router caches. Fixes bug 2352; bugfix on Tor 0.2.1.27.
10731 o Minor bugfixes (other):
10732 - Fix a bug with handling misformed replies to reverse DNS lookup
10733 requests in DNSPort. Bugfix on Tor 0.2.0.1-alpha. Related to a
10734 bug reported by doorss.
10735 - Fix compilation on mingw when a pthreads compatibility library
10736 has been installed. (We don't want to use it, so we shouldn't
10737 be including pthread.h.) Fixes bug 2313; bugfix on 0.1.0.1-rc.
10738 - Fix a bug where we would declare that we had run out of virtual
10739 addresses when the address space was only half-exhausted. Bugfix
10741 - Correctly handle the case where AutomapHostsOnResolve is set but
10742 no virtual addresses are available. Fixes bug 2328; bugfix on
10743 0.1.2.1-alpha. Bug found by doorss.
10744 - Correctly handle wrapping around to when we run out of virtual
10745 address space. Found by cypherpunks, bugfix on 0.2.0.5-alpha.
10746 - The 0.2.1.28 tarball was missing src/common/OpenBSD_malloc_Linux.c
10747 because we built it with a too-old version of automake. Thus that
10748 release broke ./configure --enable-openbsd-malloc, which is popular
10749 among really fast exit relays on Linux.
10752 - Update to the January 1 2011 Maxmind GeoLite Country database.
10753 - Introduce output size checks on all of our decryption functions.
10756 - Tor does not build packages correctly with Automake 1.6 and earlier;
10757 added a check to Makefile.am to make sure that we're building with
10758 Automake 1.7 or later.
10761 Changes in version 0.2.2.20-alpha - 2010-12-17
10762 Tor 0.2.2.20-alpha does some code cleanup to reduce the risk of remotely
10763 exploitable bugs. We also fix a variety of other significant bugs,
10764 change the IP address for one of our directory authorities, and update
10765 the minimum version that Tor relays must run to join the network.
10768 - Fix a remotely exploitable bug that could be used to crash instances
10769 of Tor remotely by overflowing on the heap. Remote-code execution
10770 hasn't been confirmed, but can't be ruled out. Everyone should
10771 upgrade. Bugfix on the 0.1.1 series and later.
10772 - Fix a bug that could break accounting on 64-bit systems with large
10773 time_t values, making them hibernate for impossibly long intervals.
10774 Fixes bug 2146. Bugfix on 0.0.9pre6; fix by boboper.
10775 - Fix a logic error in directory_fetches_from_authorities() that
10776 would cause all _non_-exits refusing single-hop-like circuits
10777 to fetch from authorities, when we wanted to have _exits_ fetch
10778 from authorities. Fixes more of 2097. Bugfix on 0.2.2.16-alpha;
10780 - Fix a stream fairness bug that would cause newer streams on a given
10781 circuit to get preference when reading bytes from the origin or
10782 destination. Fixes bug 2210. Fix by Mashael AlSabah. This bug was
10783 introduced before the first Tor release, in svn revision r152.
10785 o Directory authority changes:
10786 - Change IP address and ports for gabelmoo (v3 directory authority).
10789 - Avoid crashes when AccountingMax is set on clients. Fixes bug 2235.
10790 Bugfix on 0.2.2.18-alpha. Diagnosed by boboper.
10791 - Fix an off-by-one error in calculating some controller command
10792 argument lengths. Fortunately, this mistake is harmless since
10793 the controller code does redundant NUL termination too. Found by
10794 boboper. Bugfix on 0.1.1.1-alpha.
10795 - Do not dereference NULL if a bridge fails to build its
10796 extra-info descriptor. Found by an anonymous commenter on
10797 Trac. Bugfix on 0.2.2.19-alpha.
10800 - Update to the December 1 2010 Maxmind GeoLite Country database.
10801 - Directory authorities now reject relays running any versions of
10802 Tor between 0.2.1.3-alpha and 0.2.1.18 inclusive; they have
10803 known bugs that keep RELAY_EARLY cells from working on rendezvous
10804 circuits. Followup to fix for bug 2081.
10805 - Directory authorities now reject relays running any version of Tor
10806 older than 0.2.0.26-rc. That version is the earliest that fetches
10807 current directory information correctly. Fixes bug 2156.
10808 - Report only the top 10 ports in exit-port stats in order not to
10809 exceed the maximum extra-info descriptor length of 50 KB. Implements
10813 Changes in version 0.2.1.28 - 2010-12-17
10814 Tor 0.2.1.28 does some code cleanup to reduce the risk of remotely
10815 exploitable bugs. We also took this opportunity to change the IP address
10816 for one of our directory authorities, and to update the geoip database
10820 - Fix a remotely exploitable bug that could be used to crash instances
10821 of Tor remotely by overflowing on the heap. Remote-code execution
10822 hasn't been confirmed, but can't be ruled out. Everyone should
10823 upgrade. Bugfix on the 0.1.1 series and later.
10825 o Directory authority changes:
10826 - Change IP address and ports for gabelmoo (v3 directory authority).
10829 - Update to the December 1 2010 Maxmind GeoLite Country database.
10832 Changes in version 0.2.1.27 - 2010-11-23
10833 Yet another OpenSSL security patch broke its compatibility with Tor:
10834 Tor 0.2.1.27 makes relays work with openssl 0.9.8p and 1.0.0.b. We
10835 also took this opportunity to fix several crash bugs, integrate a new
10836 directory authority, and update the bundled GeoIP database.
10839 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10840 No longer set the tlsext_host_name extension on server SSL objects;
10841 but continue to set it on client SSL objects. Our goal in setting
10842 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10843 bugfix on 0.2.1.1-alpha.
10844 - Do not log messages to the controller while shrinking buffer
10845 freelists. Doing so would sometimes make the controller connection
10846 try to allocate a buffer chunk, which would mess up the internals
10847 of the freelist and cause an assertion failure. Fixes bug 1125;
10848 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10849 - Learn our external IP address when we're a relay or bridge, even if
10850 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10851 where we introduced bridge relays that don't need to publish to
10852 be useful. Fixes bug 2050.
10853 - Do even more to reject (and not just ignore) annotations on
10854 router descriptors received anywhere but from the cache. Previously
10855 we would ignore such annotations at first, but cache them to disk
10856 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10857 - When you're using bridges and your network goes away and your
10858 bridges get marked as down, recover when you attempt a new socks
10859 connection (if the network is back), rather than waiting up to an
10860 hour to try fetching new descriptors for your bridges. Bugfix on
10861 0.2.0.3-alpha; fixes bug 1981.
10864 - Move to the November 2010 Maxmind GeoLite country db (rather
10865 than the June 2009 ip-to-country GeoIP db) for our statistics that
10866 count how many users relays are seeing from each country. Now we'll
10867 have more accurate data, especially for many African countries.
10869 o New directory authorities:
10870 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
10874 - Fix an assertion failure that could occur in directory caches or
10875 bridge users when using a very short voting interval on a testing
10876 network. Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on
10878 - Enforce multiplicity rules when parsing annotations. Bugfix on
10879 0.2.0.8-alpha. Found by piebeer.
10880 - Allow handshaking OR connections to take a full KeepalivePeriod
10881 seconds to handshake. Previously, we would close them after
10882 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
10883 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
10885 - When building with --enable-gcc-warnings on OpenBSD, disable
10886 warnings in system headers. This makes --enable-gcc-warnings
10887 pass on OpenBSD 4.8.
10890 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
10891 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
10892 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
10893 Servers can start sending this code when enough clients recognize
10894 it. Bugfix on 0.1.0.1-rc; fixes part of bug 1793.
10895 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
10896 Patch from mingw-san.
10899 - Remove the old debian/ directory from the main Tor distribution.
10900 The official Tor-for-debian git repository lives at the URL
10901 https://git.torproject.org/debian/tor.git
10902 - Stop shipping the old doc/website/ directory in the tarball. We
10903 changed the website format in late 2010, and what we shipped in
10904 0.2.1.26 really wasn't that useful anyway.
10907 Changes in version 0.2.2.19-alpha - 2010-11-22
10908 Yet another OpenSSL security patch broke its compatibility with Tor:
10909 Tor 0.2.2.19-alpha makes relays work with OpenSSL 0.9.8p and 1.0.0.b.
10912 - Resolve an incompatibility with OpenSSL 0.9.8p and OpenSSL 1.0.0b:
10913 No longer set the tlsext_host_name extension on server SSL objects;
10914 but continue to set it on client SSL objects. Our goal in setting
10915 it was to imitate a browser, not a vhosting server. Fixes bug 2204;
10916 bugfix on 0.2.1.1-alpha.
10919 - Try harder not to exceed the maximum length of 50 KB when writing
10920 statistics to extra-info descriptors. This bug was triggered by very
10921 fast relays reporting exit-port, entry, and dirreq statistics.
10922 Reported by Olaf Selke. Bugfix on 0.2.2.1-alpha. Fixes bug 2183.
10923 - Publish a router descriptor even if generating an extra-info
10924 descriptor fails. Previously we would not publish a router
10925 descriptor without an extra-info descriptor; this can cause fast
10926 exit relays collecting exit-port statistics to drop from the
10927 consensus. Bugfix on 0.1.2.9-rc; fixes bug 2195.
10930 Changes in version 0.2.2.18-alpha - 2010-11-16
10931 Tor 0.2.2.18-alpha fixes several crash bugs that have been nagging
10932 us lately, makes unpublished bridge relays able to detect their IP
10933 address, and fixes a wide variety of other bugs to get us much closer
10934 to a stable release.
10937 - Do even more to reject (and not just ignore) annotations on
10938 router descriptors received anywhere but from the cache. Previously
10939 we would ignore such annotations at first, but cache them to disk
10940 anyway. Bugfix on 0.2.0.8-alpha. Found by piebeer.
10941 - Do not log messages to the controller while shrinking buffer
10942 freelists. Doing so would sometimes make the controller connection
10943 try to allocate a buffer chunk, which would mess up the internals
10944 of the freelist and cause an assertion failure. Fixes bug 1125;
10945 fixed by Robert Ransom. Bugfix on 0.2.0.16-alpha.
10946 - Learn our external IP address when we're a relay or bridge, even if
10947 we set PublishServerDescriptor to 0. Bugfix on 0.2.0.3-alpha,
10948 where we introduced bridge relays that don't need to publish to
10949 be useful. Fixes bug 2050.
10950 - Maintain separate TLS contexts and certificates for incoming and
10951 outgoing connections in bridge relays. Previously we would use the
10952 same TLS contexts and certs for incoming and outgoing connections.
10953 Bugfix on 0.2.0.3-alpha; addresses bug 988.
10954 - Maintain separate identity keys for incoming and outgoing TLS
10955 contexts in bridge relays. Previously we would use the same
10956 identity keys for incoming and outgoing TLS contexts. Bugfix on
10957 0.2.0.3-alpha; addresses the other half of bug 988.
10958 - Avoid an assertion failure when we as an authority receive a
10959 duplicate upload of a router descriptor that we already have,
10960 but which we previously considered an obsolete descriptor.
10961 Fixes another case of bug 1776. Bugfix on 0.2.2.16-alpha.
10962 - Avoid a crash bug triggered by looking at a dangling pointer while
10963 setting the network status consensus. Found by Robert Ransom.
10964 Bugfix on 0.2.2.17-alpha. Fixes bug 2097.
10965 - Fix a logic error where servers that _didn't_ act as exits would
10966 try to keep their server lists more aggressively up to date than
10967 exits, when it was supposed to be the other way around. Bugfix
10970 o Minor bugfixes (on Tor 0.2.1.x and earlier):
10971 - When we're trying to guess whether we know our IP address as
10972 a relay, we would log various ways that we failed to guess
10973 our address, but never log that we ended up guessing it
10974 successfully. Now add a log line to help confused and anxious
10975 relay operators. Bugfix on 0.1.2.1-alpha; fixes bug 1534.
10976 - Bring the logic that gathers routerinfos and assesses the
10977 acceptability of circuits into line. This prevents a Tor OP from
10978 getting locked in a cycle of choosing its local OR as an exit for a
10979 path (due to a .exit request) and then rejecting the circuit because
10980 its OR is not listed yet. It also prevents Tor clients from using an
10981 OR running in the same instance as an exit (due to a .exit request)
10982 if the OR does not meet the same requirements expected of an OR
10983 running elsewhere. Fixes bug 1859; bugfix on 0.1.0.1-rc.
10984 - Correctly describe errors that occur when generating a TLS object.
10985 Previously we would attribute them to a failure while generating a
10986 TLS context. Patch by Robert Ransom. Bugfix on 0.1.0.4-rc; fixes
10988 - Enforce multiplicity rules when parsing annotations. Bugfix on
10989 0.2.0.8-alpha. Found by piebeer.
10990 - Fix warnings that newer versions of autoconf produced during
10991 ./autogen.sh. These warnings appear to be harmless in our case,
10992 but they were extremely verbose. Fixes bug 2020.
10994 o Minor bugfixes (on Tor 0.2.2.x):
10995 - Enable protection of small arrays whenever we build with gcc
10996 hardening features, not only when also building with warnings
10997 enabled. Fixes bug 2031; bugfix on 0.2.2.14-alpha. Reported by keb.
11000 - Make hidden services work better in private Tor networks by not
11001 requiring any uptime to join the hidden service descriptor
11002 DHT. Implements ticket 2088.
11003 - Rate-limit the "your application is giving Tor only an IP address"
11004 warning. Addresses bug 2000; bugfix on 0.0.8pre2.
11005 - When AllowSingleHopExits is set, print a warning to explain to the
11006 relay operator why most clients are avoiding her relay.
11007 - Update to the November 1 2010 Maxmind GeoLite Country database.
11009 o Code simplifications and refactoring:
11010 - When we fixed bug 1038 we had to put in a restriction not to send
11011 RELAY_EARLY cells on rend circuits. This was necessary as long
11012 as relays using Tor 0.2.1.3-alpha through 0.2.1.18-alpha were
11013 active. Now remove this obsolete check. Resolves bug 2081.
11014 - Some options used different conventions for uppercasing of acronyms
11015 when comparing manpage and source. Fix those in favor of the
11016 manpage, as it makes sense to capitalize acronyms.
11017 - Remove the torrc.complete file. It hasn't been kept up to date
11018 and users will have better luck checking out the manpage.
11019 - Remove the obsolete "NoPublish" option; it has been flagged
11020 as obsolete and has produced a warning since 0.1.1.18-rc.
11021 - Remove everything related to building the expert bundle for OS X.
11022 It has confused many users, doesn't work right on OS X 10.6,
11023 and is hard to get rid of once installed. Resolves bug 1274.
11026 Changes in version 0.2.2.17-alpha - 2010-09-30
11027 Tor 0.2.2.17-alpha introduces a feature to make it harder for clients
11028 to use one-hop circuits (which can put the exit relays at higher risk,
11029 plus unbalance the network); fixes a big bug in bandwidth accounting
11030 for relays that want to limit their monthly bandwidth use; fixes a
11031 big pile of bugs in how clients tolerate temporary network failure;
11032 and makes our adaptive circuit build timeout feature (which improves
11033 client performance if your network is fast while not breaking things
11034 if your network is slow) better handle bad networks.
11037 - Exit relays now try harder to block exit attempts from unknown
11038 relays, to make it harder for people to use them as one-hop proxies
11039 a la tortunnel. Controlled by the refuseunknownexits consensus
11040 parameter (currently enabled), or you can override it on your
11041 relay with the RefuseUnknownExits torrc option. Resolves bug 1751.
11043 o Major bugfixes (0.2.1.x and earlier):
11044 - Fix a bug in bandwidth accounting that could make us use twice
11045 the intended bandwidth when our interval start changes due to
11046 daylight saving time. Now we tolerate skew in stored vs computed
11047 interval starts: if the start of the period changes by no more than
11048 50% of the period's duration, we remember bytes that we transferred
11049 in the old period. Fixes bug 1511; bugfix on 0.0.9pre5.
11050 - Always search the Windows system directory for system DLLs, and
11051 nowhere else. Bugfix on 0.1.1.23; fixes bug 1954.
11052 - When you're using bridges and your network goes away and your
11053 bridges get marked as down, recover when you attempt a new socks
11054 connection (if the network is back), rather than waiting up to an
11055 hour to try fetching new descriptors for your bridges. Bugfix on
11056 0.2.0.3-alpha; fixes bug 1981.
11058 o Major bugfixes (on 0.2.2.x):
11059 - Fix compilation on Windows. Bugfix on 0.2.2.16-alpha; related to
11061 - Fix a segfault that could happen when operating a bridge relay with
11062 no GeoIP database set. Fixes bug 1964; bugfix on 0.2.2.15-alpha.
11063 - The consensus bandwidth-weights (used by clients to choose fast
11064 relays) entered an unexpected edge case in September where
11065 Exits were much scarcer than Guards, resulting in bad weight
11066 recommendations. Now we compute them using new constraints that
11067 should succeed in all cases. Also alter directory authorities to
11068 not include the bandwidth-weights line if they fail to produce
11069 valid values. Fixes bug 1952; bugfix on 0.2.2.10-alpha.
11070 - When weighting bridges during path selection, we used to trust
11071 the bandwidths they provided in their descriptor, only capping them
11072 at 10MB/s. This turned out to be problematic for two reasons:
11073 Bridges could claim to handle a lot more traffic then they
11074 actually would, thus making more clients pick them and have a
11075 pretty effective DoS attack. The other issue is that new bridges
11076 that might not have a good estimate for their bw capacity yet
11077 would not get used at all unless no other bridges are available
11078 to a client. Fixes bug 1912; bugfix on 0.2.2.7-alpha.
11080 o Major bugfixes (on the circuit build timeout feature, 0.2.2.x):
11081 - Ignore cannibalized circuits when recording circuit build times.
11082 This should provide for a minor performance improvement for hidden
11083 service users using 0.2.2.14-alpha, and should remove two spurious
11084 notice log messages. Bugfix on 0.2.2.14-alpha; fixes bug 1740.
11085 - Simplify the logic that causes us to decide if the network is
11086 unavailable for purposes of recording circuit build times. If we
11087 receive no cells whatsoever for the entire duration of a circuit's
11088 full measured lifetime, the network is probably down. Also ignore
11089 one-hop directory fetching circuit timeouts when calculating our
11090 circuit build times. These changes should hopefully reduce the
11091 cases where we see ridiculous circuit build timeouts for people
11092 with spotty wireless connections. Fixes part of bug 1772; bugfix
11094 - Prevent the circuit build timeout from becoming larger than
11095 the maximum build time we have ever seen. Also, prevent the time
11096 period for measurement circuits from becoming larger than twice that
11097 value. Fixes the other part of bug 1772; bugfix on 0.2.2.2-alpha.
11100 - When we run out of directory information such that we can't build
11101 circuits, but then get enough that we can build circuits, log when
11102 we actually construct a circuit, so the user has a better chance of
11103 knowing what's going on. Fixes bug 1362.
11104 - Be more generous with how much bandwidth we'd use up (with
11105 accounting enabled) before entering "soft hibernation". Previously,
11106 we'd refuse new connections and circuits once we'd used up 95% of
11107 our allotment. Now, we use up 95% of our allotment, AND make sure
11108 that we have no more than 500MB (or 3 hours of expected traffic,
11109 whichever is lower) remaining before we enter soft hibernation.
11110 - If we've configured EntryNodes and our network goes away and/or all
11111 our entrynodes get marked down, optimistically retry them all when
11112 a new socks application request appears. Fixes bug 1882.
11113 - Add some more defensive programming for architectures that can't
11114 handle unaligned integer accesses. We don't know of any actual bugs
11115 right now, but that's the best time to fix them. Fixes bug 1943.
11116 - Support line continuations in the torrc config file. If a line
11117 ends with a single backslash character, the newline is ignored, and
11118 the configuration value is treated as continuing on the next line.
11121 o Minor bugfixes (on 0.2.1.x and earlier):
11122 - For bandwidth accounting, calculate our expected bandwidth rate
11123 based on the time during which we were active and not in
11124 soft-hibernation during the last interval. Previously, we were
11125 also considering the time spent in soft-hibernation. If this
11126 was a long time, we would wind up underestimating our bandwidth
11127 by a lot, and skewing our wakeup time towards the start of the
11128 accounting interval. Fixes bug 1789. Bugfix on 0.0.9pre5.
11130 o Minor bugfixes (on 0.2.2.x):
11131 - Resume generating CIRC FAILED REASON=TIMEOUT control port messages,
11132 which were disabled by the circuit build timeout changes in
11133 0.2.2.14-alpha. Bugfix on 0.2.2.14-alpha; fixes bug 1739.
11134 - Make sure we don't warn about missing bandwidth weights when
11135 choosing bridges or other relays not in the consensus. Bugfix on
11136 0.2.2.10-alpha; fixes bug 1805.
11137 - In our logs, do not double-report signatures from unrecognized
11138 authorities both as "from unknown authority" and "not
11139 present". Fixes bug 1956, bugfix on 0.2.2.16-alpha.
11142 Changes in version 0.2.2.16-alpha - 2010-09-17
11143 Tor 0.2.2.16-alpha fixes a variety of old stream fairness bugs (most
11144 evident at exit relays), and also continues to resolve all the little
11145 bugs that have been filling up trac lately.
11147 o Major bugfixes (stream-level fairness):
11148 - When receiving a circuit-level SENDME for a blocked circuit, try
11149 to package cells fairly from all the streams that had previously
11150 been blocked on that circuit. Previously, we had started with the
11151 oldest stream, and allowed each stream to potentially exhaust
11152 the circuit's package window. This gave older streams on any
11153 given circuit priority over newer ones. Fixes bug 1937. Detected
11154 originally by Camilo Viecco. This bug was introduced before the
11155 first Tor release, in svn commit r152: it is the new winner of
11156 the longest-lived bug prize.
11157 - When the exit relay got a circuit-level sendme cell, it started
11158 reading on the exit streams, even if had 500 cells queued in the
11159 circuit queue already, so the circuit queue just grew and grew in
11160 some cases. We fix this by not re-enabling reading on receipt of a
11161 sendme cell when the cell queue is blocked. Fixes bug 1653. Bugfix
11162 on 0.2.0.1-alpha. Detected by Mashael AlSabah. Original patch by
11164 - Newly created streams were allowed to read cells onto circuits,
11165 even if the circuit's cell queue was blocked and waiting to drain.
11166 This created potential unfairness, as older streams would be
11167 blocked, but newer streams would gladly fill the queue completely.
11168 We add code to detect this situation and prevent any stream from
11169 getting more than one free cell. Bugfix on 0.2.0.1-alpha. Partially
11173 - Update to the September 1 2010 Maxmind GeoLite Country database.
11174 - Warn when CookieAuthFileGroupReadable is set but CookieAuthFile is
11175 not. This would lead to a cookie that is still not group readable.
11176 Closes bug 1843. Suggested by katmagic.
11177 - When logging a rate-limited warning, we now mention how many messages
11178 got suppressed since the last warning.
11179 - Add new "perconnbwrate" and "perconnbwburst" consensus params to
11180 do individual connection-level rate limiting of clients. The torrc
11181 config options with the same names trump the consensus params, if
11182 both are present. Replaces the old "bwconnrate" and "bwconnburst"
11183 consensus params which were broken from 0.2.2.7-alpha through
11184 0.2.2.14-alpha. Closes bug 1947.
11185 - When a router changes IP address or port, authorities now launch
11186 a new reachability test for it. Implements ticket 1899.
11187 - Make the formerly ugly "2 unknown, 7 missing key, 0 good, 0 bad,
11188 2 no signature, 4 required" messages about consensus signatures
11189 easier to read, and make sure they get logged at the same severity
11190 as the messages explaining which keys are which. Fixes bug 1290.
11191 - Don't warn when we have a consensus that we can't verify because
11192 of missing certificates, unless those certificates are ones
11193 that we have been trying and failing to download. Fixes bug 1145.
11194 - If you configure your bridge with a known identity fingerprint,
11195 and the bridge authority is unreachable (as it is in at least
11196 one country now), fall back to directly requesting the descriptor
11197 from the bridge. Finishes the feature started in 0.2.0.10-alpha;
11199 - When building with --enable-gcc-warnings on OpenBSD, disable
11200 warnings in system headers. This makes --enable-gcc-warnings
11201 pass on OpenBSD 4.8.
11203 o Minor bugfixes (on 0.2.1.x and earlier):
11204 - Authorities will now attempt to download consensuses if their
11205 own efforts to make a live consensus have failed. This change
11206 means authorities that restart will fetch a valid consensus, and
11207 it means authorities that didn't agree with the current consensus
11208 will still fetch and serve it if it has enough signatures. Bugfix
11209 on 0.2.0.9-alpha; fixes bug 1300.
11210 - Ensure DNS requests launched by "RESOLVE" commands from the
11211 controller respect the __LeaveStreamsUnattached setconf options. The
11212 same goes for requests launched via DNSPort or transparent
11213 proxying. Bugfix on 0.2.0.1-alpha; fixes bug 1525.
11214 - Allow handshaking OR connections to take a full KeepalivePeriod
11215 seconds to handshake. Previously, we would close them after
11216 IDLE_OR_CONN_TIMEOUT (180) seconds, the same timeout as if they
11217 were open. Bugfix on 0.2.1.26; fixes bug 1840. Thanks to mingw-san
11219 - Rate-limit "Failed to hand off onionskin" warnings.
11220 - Never relay a cell for a circuit we have already destroyed.
11221 Between marking a circuit as closeable and finally closing it,
11222 it may have been possible for a few queued cells to get relayed,
11223 even though they would have been immediately dropped by the next
11224 OR in the circuit. Fixes bug 1184; bugfix on 0.2.0.1-alpha.
11225 - Never queue a cell for a circuit that's already been marked
11227 - Never vote for a server as "Running" if we have a descriptor for
11228 it claiming to be hibernating, and that descriptor was published
11229 more recently than our last contact with the server. Bugfix on
11230 0.2.0.3-alpha; fixes bug 911.
11231 - Squash a compile warning on OpenBSD. Reported by Tas; fixes
11234 o Minor bugfixes (on 0.2.2.x):
11235 - Fix a regression introduced in 0.2.2.7-alpha that marked relays
11236 down if a directory fetch fails and you've configured either
11237 bridges or EntryNodes. The intent was to mark the relay as down
11238 _unless_ you're using bridges or EntryNodes, since if you are
11239 then you could quickly run out of entry points.
11240 - Fix the Windows directory-listing code. A bug introduced in
11241 0.2.2.14-alpha could make Windows directory servers forget to load
11242 some of their cached v2 networkstatus files.
11243 - Really allow clients to use relays as bridges. Fixes bug 1776;
11244 bugfix on 0.2.2.15-alpha.
11245 - Demote a warn to info that happens when the CellStatistics option
11246 was just enabled. Bugfix on 0.2.2.15-alpha; fixes bug 1921.
11247 Reported by Moritz Bartl.
11248 - On Windows, build correctly either with or without Unicode support.
11249 This is necessary so that Tor can support fringe platforms like
11250 Windows 98 (which has no Unicode), or Windows CE (which has no
11251 non-Unicode). Bugfix on 0.2.2.14-alpha; fixes bug 1797.
11254 - Add a unit test for cross-platform directory-listing code.
11257 Changes in version 0.2.2.15-alpha - 2010-08-18
11258 Tor 0.2.2.15-alpha fixes a big bug in hidden service availability,
11259 fixes a variety of other bugs that were preventing performance
11260 experiments from moving forward, fixes several bothersome memory leaks,
11261 and generally closes a lot of smaller bugs that have been filling up
11265 - Stop assigning the HSDir flag to relays that disable their
11266 DirPort (and thus will refuse to answer directory requests). This
11267 fix should dramatically improve the reachability of hidden services:
11268 hidden services and hidden service clients pick six HSDir relays
11269 to store and retrieve the hidden service descriptor, and currently
11270 about half of the HSDir relays will refuse to work. Bugfix on
11271 0.2.0.10-alpha; fixes part of bug 1693.
11272 - The PerConnBWRate and Burst config options, along with the
11273 bwconnrate and bwconnburst consensus params, initialized each conn's
11274 token bucket values only when the connection is established. Now we
11275 update them if the config options change, and update them every time
11276 we get a new consensus. Otherwise we can encounter an ugly edge
11277 case where we initialize an OR conn to client-level bandwidth,
11278 but then later the relay joins the consensus and we leave it
11279 throttled. Bugfix on 0.2.2.7-alpha; fixes bug 1830.
11280 - Fix a regression that caused Tor to rebind its ports if it receives
11281 SIGHUP while hibernating. Bugfix in 0.1.1.6-alpha; closes bug 919.
11284 - Lower the maximum weighted-fractional-uptime cutoff to 98%. This
11285 should give us approximately 40-50% more Guard-flagged nodes,
11286 improving the anonymity the Tor network can provide and also
11287 decreasing the dropoff in throughput that relays experience when
11288 they first get the Guard flag.
11289 - Allow enabling or disabling the *Statistics config options while
11293 - Update to the August 1 2010 Maxmind GeoLite Country database.
11294 - Have the controller interface give a more useful message than
11295 "Internal Error" in response to failed GETINFO requests.
11296 - Warn when the same option is provided more than once in a torrc
11297 file, on the command line, or in a single SETCONF statement, and
11298 the option is one that only accepts a single line. Closes bug 1384.
11299 - Build correctly on mingw with more recent versions of OpenSSL 0.9.8.
11300 Patch from mingw-san.
11301 - Add support for the country code "{??}" in torrc options like
11302 ExcludeNodes, to indicate all routers of unknown country. Closes
11304 - Relays report the number of bytes spent on answering directory
11305 requests in extra-info descriptors similar to {read,write}-history.
11306 Implements enhancement 1790.
11308 o Minor bugfixes (on 0.2.1.x and earlier):
11309 - Complain if PublishServerDescriptor is given multiple arguments that
11310 include 0 or 1. This configuration will be rejected in the future.
11311 Bugfix on 0.2.0.1-alpha; closes bug 1107.
11312 - Disallow BridgeRelay 1 and ORPort 0 at once in the configuration.
11313 Bugfix on 0.2.0.13-alpha; closes bug 928.
11314 - Change "Application request when we're believed to be offline."
11315 notice to "Application request when we haven't used client
11316 functionality lately.", to clarify that it's not an error. Bugfix
11317 on 0.0.9.3; fixes bug 1222.
11318 - Fix a bug in the controller interface where "GETINFO ns/asdaskljkl"
11319 would return "551 Internal error" rather than "552 Unrecognized key
11320 ns/asdaskljkl". Bugfix on 0.1.2.3-alpha.
11321 - Users can't configure a regular relay to be their bridge. It didn't
11322 work because when Tor fetched the bridge descriptor, it found
11323 that it already had it, and didn't realize that the purpose of the
11324 descriptor had changed. Now we replace routers with a purpose other
11325 than bridge with bridge descriptors when fetching them. Bugfix on
11326 0.1.1.9-alpha. Bug 1776 not yet fixed because now we immediately
11327 refetch the descriptor with router purpose 'general', disabling
11329 - Fix a rare bug in rend_fn unit tests: we would fail a test when
11330 a randomly generated port is 0. Diagnosed by Matt Edman. Bugfix
11331 on 0.2.0.10-alpha; fixes bug 1808.
11332 - Exit nodes didn't recognize EHOSTUNREACH as a plausible error code,
11333 and so sent back END_STREAM_REASON_MISC. Clients now recognize a new
11334 stream ending reason for this case: END_STREAM_REASON_NOROUTE.
11335 Servers can start sending this code when enough clients recognize
11336 it. Also update the spec to reflect this new reason. Bugfix on
11337 0.1.0.1-rc; fixes part of bug 1793.
11338 - Delay geoip stats collection by bridges for 6 hours, not 2 hours,
11339 when we switch from being a public relay to a bridge. Otherwise
11340 there will still be clients that see the relay in their consensus,
11341 and the stats will end up wrong. Bugfix on 0.2.1.15-rc; fixes bug
11343 - Instead of giving an assertion failure on an internal mismatch
11344 on estimated freelist size, just log a BUG warning and try later.
11345 Mitigates but does not fix bug 1125.
11346 - Fix an assertion failure that could occur in caches or bridge users
11347 when using a very short voting interval on a testing network.
11348 Diagnosed by Robert Hogan. Fixes bug 1141; bugfix on 0.2.0.8-alpha.
11350 o Minor bugfixes (on 0.2.2.x):
11351 - Alter directory authorities to always consider Exit-flagged nodes
11352 as potential Guard nodes in their votes. The actual decision to
11353 use Exits as Guards is done in the consensus bandwidth weights.
11354 Fixes bug 1294; bugfix on 0.2.2.10-alpha.
11355 - When the controller is reporting the purpose of circuits that
11356 didn't finish building before the circuit build timeout, it was
11357 printing UNKNOWN_13. Now print EXPIRED. Bugfix on 0.2.2.14-alpha.
11358 - Our libevent version parsing code couldn't handle versions like
11359 1.4.14b-stable and incorrectly warned the user about using an
11360 old and broken version of libevent. Treat 1.4.14b-stable like
11361 1.4.14-stable when parsing the version. Fixes bug 1731; bugfix
11363 - Don't use substitution references like $(VAR:MOD) when
11364 $(asciidoc_files) is empty -- make(1) on NetBSD transforms
11365 '$(:x)' to 'x' rather than the empty string. This bites us in
11366 doc/ when configured with --disable-asciidoc. Bugfix on
11367 0.2.2.9-alpha; fixes bug 1773.
11368 - Remove a spurious hidden service server-side log notice about
11369 "Ancient non-dirty circuits". Bugfix on 0.2.2.14-alpha; fixes
11371 - Fix compilation with --with-dmalloc set. Bugfix on 0.2.2.6-alpha;
11373 - Correctly report written bytes on linked connections. Found while
11374 implementing 1790. Bugfix on 0.2.2.4-alpha.
11375 - Fix three memory leaks: one in circuit_build_times_parse_state(),
11376 one in dirvote_add_signatures_to_pending_consensus(), and one every
11377 time we parse a v3 network consensus. Bugfixes on 0.2.2.14-alpha,
11378 0.2.2.6-alpha, and 0.2.2.10-alpha respectively; fixes bug 1831.
11380 o Code simplifications and refactoring:
11381 - Take a first step towards making or.h smaller by splitting out
11382 function definitions for all source files in src/or/. Leave
11383 structures and defines in or.h for now.
11384 - Remove a bunch of unused function declarations as well as a block of
11385 #if 0'd code from the unit tests. Closes bug 1824.
11386 - New unit tests for exit-port history statistics; refactored exit
11387 statistics code to be more easily tested.
11388 - Remove the old debian/ directory from the main Tor distribution.
11389 The official Tor-for-debian git repository lives at the URL
11390 https://git.torproject.org/debian/tor.git
11393 Changes in version 0.2.2.14-alpha - 2010-07-12
11394 Tor 0.2.2.14-alpha greatly improves client-side handling of
11395 circuit build timeouts, which are used to estimate speed and improve
11396 performance. We also move to a much better GeoIP database, port Tor to
11397 Windows CE, introduce new compile flags that improve code security,
11398 add an eighth v3 directory authority, and address a lot of more
11402 - Tor directory authorities no longer crash when started with a
11403 cached-microdesc-consensus file in their data directory. Bugfix
11404 on 0.2.2.6-alpha; fixes bug 1532.
11405 - Treat an unset $HOME like an empty $HOME rather than triggering an
11406 assert. Bugfix on 0.0.8pre1; fixes bug 1522.
11407 - Ignore negative and large circuit build timeout values that can
11408 happen during a suspend or hibernate. These values caused various
11409 asserts to fire. Bugfix on 0.2.2.2-alpha; fixes bug 1245.
11410 - Alter calculation of Pareto distribution parameter 'Xm' for
11411 Circuit Build Timeout learning to use the weighted average of the
11412 top N=3 modes (because we have three entry guards). Considering
11413 multiple modes should improve the timeout calculation in some cases,
11414 and prevent extremely high timeout values. Bugfix on 0.2.2.2-alpha;
11416 - Alter calculation of Pareto distribution parameter 'Alpha' to use a
11417 right censored distribution model. This approach improves over the
11418 synthetic timeout generation approach that was producing insanely
11419 high timeout values. Now we calculate build timeouts using truncated
11420 times. Bugfix on 0.2.2.2-alpha; fixes bugs 1245 and 1335.
11421 - Do not close circuits that are under construction when they reach
11422 the circuit build timeout. Instead, leave them building (but do not
11423 use them) for up until the time corresponding to the 95th percentile
11424 on the Pareto CDF or 60 seconds, whichever is greater. This is done
11425 to provide better data for the new Pareto model. This percentile
11426 can be controlled by the consensus.
11429 - Move to the June 2010 Maxmind GeoLite country db (rather than the
11430 June 2009 ip-to-country GeoIP db) for our statistics that count
11431 how many users relays are seeing from each country. Now we have
11432 more accurate data for many African countries.
11433 - Port Tor to build and run correctly on Windows CE systems, using
11434 the wcecompat library. Contributed by Valerio Lupi.
11435 - New "--enable-gcc-hardening" ./configure flag (off by default)
11436 to turn on gcc compile time hardening options. It ensures
11437 that signed ints have defined behavior (-fwrapv), enables
11438 -D_FORTIFY_SOURCE=2 (requiring -O2), adds stack smashing protection
11439 with canaries (-fstack-protector-all), turns on ASLR protection if
11440 supported by the kernel (-fPIE, -pie), and adds additional security
11441 related warnings. Verified to work on Mac OS X and Debian Lenny.
11442 - New "--enable-linker-hardening" ./configure flag (off by default)
11443 to turn on ELF specific hardening features (relro, now). This does
11444 not work with Mac OS X or any other non-ELF binary format.
11446 o New directory authorities:
11447 - Set up maatuska (run by Linus Nordberg) as the eighth v3 directory
11451 - New config option "WarnUnsafeSocks 0" disables the warning that
11452 occurs whenever Tor receives a socks handshake using a version of
11453 the socks protocol that can only provide an IP address (rather
11454 than a hostname). Setups that do DNS locally over Tor are fine,
11455 and we shouldn't spam the logs in that case.
11456 - Convert the HACKING file to asciidoc, and add a few new sections
11457 to it, explaining how we use Git, how we make changelogs, and
11458 what should go in a patch.
11459 - Add a TIMEOUT_RATE keyword to the BUILDTIMEOUT_SET control port
11460 event, to give information on the current rate of circuit timeouts
11461 over our stored history.
11462 - Add ability to disable circuit build time learning via consensus
11463 parameter and via a LearnCircuitBuildTimeout config option. Also
11464 automatically disable circuit build time calculation if we are
11465 either a AuthoritativeDirectory, or if we fail to write our state
11466 file. Fixes bug 1296.
11467 - More gracefully handle corrupt state files, removing asserts
11468 in favor of saving a backup and resetting state.
11469 - Rename the "log.h" header to "torlog.h" so as to conflict with fewer
11473 - Build correctly on OSX with zlib 1.2.4 and higher with all warnings
11475 - When a2x fails, mention that the user could disable manpages instead
11476 of trying to fix their asciidoc installation.
11477 - Where available, use Libevent 2.0's periodic timers so that our
11478 once-per-second cleanup code gets called even more closely to
11479 once per second than it would otherwise. Fixes bug 943.
11480 - If you run a bridge that listens on multiple IP addresses, and
11481 some user configures a bridge address that uses a different IP
11482 address than your bridge writes in its router descriptor, and the
11483 user doesn't specify an identity key, their Tor would discard the
11484 descriptor because "it isn't one of our configured bridges", and
11485 fail to bootstrap. Now believe the descriptor and bootstrap anyway.
11486 Bugfix on 0.2.0.3-alpha.
11487 - If OpenSSL fails to make a duplicate of a private or public key, log
11488 an error message and try to exit cleanly. May help with debugging
11489 if bug 1209 ever remanifests.
11490 - Save a couple bytes in memory allocation every time we escape
11491 certain characters in a string. Patch from Florian Zumbiehl.
11492 - Make it explicit that we don't cannibalize one-hop circuits. This
11493 happens in the wild, but doesn't turn out to be a problem because
11494 we fortunately don't use those circuits. Many thanks to outofwords
11495 for the initial analysis and to swissknife who confirmed that
11496 two-hop circuits are actually created.
11497 - Make directory mirrors report non-zero dirreq-v[23]-shares again.
11498 Fixes bug 1564; bugfix on 0.2.2.9-alpha.
11499 - Eliminate a case where a circuit build time warning was displayed
11500 after network connectivity resumed. Bugfix on 0.2.2.2-alpha.
11503 Changes in version 0.2.1.26 - 2010-05-02
11504 Tor 0.2.1.26 addresses the recent connection and memory overload
11505 problems we've been seeing on relays, especially relays with their
11506 DirPort open. If your relay has been crashing, or you turned it off
11507 because it used too many resources, give this release a try.
11509 This release also fixes yet another instance of broken OpenSSL libraries
11510 that was causing some relays to drop out of the consensus.
11513 - Teach relays to defend themselves from connection overload. Relays
11514 now close idle circuits early if it looks like they were intended
11515 for directory fetches. Relays are also more aggressive about closing
11516 TLS connections that have no circuits on them. Such circuits are
11517 unlikely to be re-used, and tens of thousands of them were piling
11518 up at the fast relays, causing the relays to run out of sockets
11519 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11520 their directory fetches over TLS).
11521 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11522 that claim to be earlier than 0.9.8m, but which have in reality
11523 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11524 behavior. Possible fix for some cases of bug 1346.
11525 - Directory mirrors were fetching relay descriptors only from v2
11526 directory authorities, rather than v3 authorities like they should.
11527 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11528 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11531 - Finally get rid of the deprecated and now harmful notion of "clique
11532 mode", where directory authorities maintain TLS connections to
11536 - In the util/threads test, no longer free the test_mutex before all
11537 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11538 - The master thread could starve the worker threads quite badly on
11539 certain systems, causing them to run only partially in the allowed
11540 window. This resulted in test failures. Now the master thread sleeps
11541 occasionally for a few microseconds while the two worker-threads
11542 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11545 Changes in version 0.2.2.13-alpha - 2010-04-24
11546 Tor 0.2.2.13-alpha addresses the recent connection and memory overload
11547 problems we've been seeing on relays, especially relays with their
11548 DirPort open. If your relay has been crashing, or you turned it off
11549 because it used too many resources, give this release a try.
11552 - Teach relays to defend themselves from connection overload. Relays
11553 now close idle circuits early if it looks like they were intended
11554 for directory fetches. Relays are also more aggressive about closing
11555 TLS connections that have no circuits on them. Such circuits are
11556 unlikely to be re-used, and tens of thousands of them were piling
11557 up at the fast relays, causing the relays to run out of sockets
11558 and memory. Bugfix on 0.2.0.22-rc (where clients started tunneling
11559 their directory fetches over TLS).
11562 - Finally get rid of the deprecated and now harmful notion of "clique
11563 mode", where directory authorities maintain TLS connections to
11565 - Directory authorities now do an immediate reachability check as soon
11566 as they hear about a new relay. This change should slightly reduce
11567 the time between setting up a relay and getting listed as running
11568 in the consensus. It should also improve the time between setting
11569 up a bridge and seeing use by bridge users.
11570 - Directory authorities no longer launch a TLS connection to every
11571 relay as they startup. Now that we have 2k+ descriptors cached,
11572 the resulting network hiccup is becoming a burden. Besides,
11573 authorities already avoid voting about Running for the first half
11574 hour of their uptime.
11577 Changes in version 0.2.2.12-alpha - 2010-04-20
11578 Tor 0.2.2.12-alpha fixes a critical bug in how directory authorities
11579 handle and vote on descriptors. It was causing relays to drop out of
11583 - Many relays have been falling out of the consensus lately because
11584 not enough authorities know about their descriptor for them to get
11585 a majority of votes. When we deprecated the v2 directory protocol,
11586 we got rid of the only way that v3 authorities can hear from each
11587 other about other descriptors. Now authorities examine every v3
11588 vote for new descriptors, and fetch them from that authority. Bugfix
11590 - Fix two typos in tor_vasprintf() that broke the compile on Windows,
11591 and a warning in or.h related to bandwidth_weight_rule_t that
11592 prevented clean compile on OS X. Fixes bug 1363; bugfix on
11594 - Fix a segfault on relays when DirReqStatistics is enabled
11595 and 24 hours pass. Bug found by keb. Fixes bug 1365; bugfix on
11599 - Demote a confusing TLS warning that relay operators might get when
11600 someone tries to talk to their OrPort. It is neither the operator's
11601 fault nor can they do anything about it. Fixes bug 1364; bugfix
11605 Changes in version 0.2.2.11-alpha - 2010-04-15
11606 Tor 0.2.2.11-alpha fixes yet another instance of broken OpenSSL
11607 libraries that was causing some relays to drop out of the consensus.
11610 - Directory mirrors were fetching relay descriptors only from v2
11611 directory authorities, rather than v3 authorities like they should.
11612 Only 2 v2 authorities remain (compared to 7 v3 authorities), leading
11613 to a serious bottleneck. Bugfix on 0.2.0.9-alpha. Fixes bug 1324.
11614 - Fix a parsing error that made every possible value of
11615 CircPriorityHalflifeMsec get treated as "1 msec". Bugfix
11616 on 0.2.2.7-alpha. Rename CircPriorityHalflifeMsec to
11617 CircuitPriorityHalflifeMsec, so authorities can tell newer relays
11618 about the option without breaking older ones.
11619 - Fix SSL renegotiation behavior on OpenSSL versions like on Centos
11620 that claim to be earlier than 0.9.8m, but which have in reality
11621 backported huge swaths of 0.9.8m or 0.9.8n renegotiation
11622 behavior. Possible fix for some cases of bug 1346.
11625 - Experiment with a more aggressive approach to preventing clients
11626 from making one-hop exit streams. Exit relays who want to try it
11627 out can set "RefuseUnknownExits 1" in their torrc, and then look
11628 for "Attempt by %s to open a stream" log messages. Let us know
11630 - Add support for statically linking zlib by specifying
11631 --enable-static-zlib, to go with our support for statically linking
11632 openssl and libevent. Resolves bug 1358.
11635 - Fix a segfault that happens whenever a Tor client that is using
11636 libevent2's bufferevents gets a hup signal. Bugfix on 0.2.2.5-alpha;
11638 - When we cleaned up the contrib/tor-exit-notice.html file, we left
11639 out the first line. Fixes bug 1295.
11640 - When building the manpage from a tarball, we required asciidoc, but
11641 the asciidoc -> roff/html conversion was already done for the
11642 tarball. Make 'make' complain only when we need asciidoc (either
11643 because we're compiling directly from git, or because we altered
11644 the asciidoc manpage in the tarball). Bugfix on 0.2.2.9-alpha.
11645 - When none of the directory authorities vote on any params, Tor
11646 segfaulted when trying to make the consensus from the votes. We
11647 didn't trigger the bug in practice, because authorities do include
11648 params in their votes. Bugfix on 0.2.2.10-alpha; fixes bug 1322.
11651 - In the util/threads test, no longer free the test_mutex before all
11652 worker threads have finished. Bugfix on 0.2.1.6-alpha.
11653 - The master thread could starve the worker threads quite badly on
11654 certain systems, causing them to run only partially in the allowed
11655 window. This resulted in test failures. Now the master thread sleeps
11656 occasionally for a few microseconds while the two worker-threads
11657 compete for the mutex. Bugfix on 0.2.0.1-alpha.
11660 Changes in version 0.2.2.10-alpha - 2010-03-07
11661 Tor 0.2.2.10-alpha fixes a regression introduced in 0.2.2.9-alpha that
11662 could prevent relays from guessing their IP address correctly. It also
11663 starts the groundwork for another client-side performance boost, since
11664 currently we're not making efficient use of relays that have both the
11665 Guard flag and the Exit flag.
11668 - Fix a regression from our patch for bug 1244 that caused relays
11669 to guess their IP address incorrectly if they didn't set Address
11670 in their torrc and/or their address fails to resolve. Bugfix on
11671 0.2.2.9-alpha; fixes bug 1269.
11673 o Major features (performance):
11674 - Directory authorities now compute consensus weightings that instruct
11675 clients how to weight relays flagged as Guard, Exit, Guard+Exit,
11676 and no flag. Clients that use these weightings will distribute
11677 network load more evenly across these different relay types. The
11678 weightings are in the consensus so we can change them globally in
11679 the future. Extra thanks to "outofwords" for finding some nasty
11680 security bugs in the first implementation of this feature.
11682 o Minor features (performance):
11683 - Always perform router selections using weighted relay bandwidth,
11684 even if we don't need a high capacity circuit at the time. Non-fast
11685 circuits now only differ from fast ones in that they can use relays
11686 not marked with the Fast flag. This "feature" could turn out to
11687 be a horrible bug; we should investigate more before it goes into
11691 - Allow disabling building of the manpages. Skipping the manpage
11692 speeds up the build considerably.
11694 o Minor bugfixes (on 0.2.2.x):
11695 - Fix a memleak in the EXTENDCIRCUIT logic. Spotted by coverity.
11696 Bugfix on 0.2.2.9-alpha.
11697 - Disallow values larger than INT32_MAX for PerConnBWRate|Burst
11698 config option. Bugfix on 0.2.2.7-alpha.
11699 - Ship the asciidoc-helper file in the tarball, so that people can
11700 build from source if they want to, and touching the .1.txt files
11701 doesn't break the build. Bugfix on 0.2.2.9-alpha.
11703 o Minor bugfixes (on 0.2.1.x or earlier):
11704 - Fix a dereference-then-NULL-check sequence when publishing
11705 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11707 - Fix another dereference-then-NULL-check sequence. Bugfix on
11708 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11709 - Make sure we treat potentially not NUL-terminated strings correctly.
11710 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11712 o Code simplifications and refactoring:
11713 - Fix some urls in the exit notice file and make it XHTML1.1 strict
11714 compliant. Based on a patch from Christian Kujau.
11715 - Don't use sed in asciidoc-helper anymore.
11716 - Make the build process fail if asciidoc cannot be found and
11717 building with asciidoc isn't disabled.
11720 Changes in version 0.2.2.9-alpha - 2010-02-22
11721 Tor 0.2.2.9-alpha makes Tor work again on the latest OS X, updates the
11722 location of a directory authority, and cleans up a bunch of small bugs.
11724 o Directory authority changes:
11725 - Change IP address for dannenberg (v3 directory authority), and
11726 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11727 service directory authority) from the list.
11730 - Make Tor work again on the latest OS X: when deciding whether to
11731 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11732 version at run-time, not compile time. We need to do this because
11733 Apple doesn't update its dev-tools headers when it updates its
11734 libraries in a security patch.
11735 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11736 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11737 a memory leak when requesting a hidden service descriptor we've
11738 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11740 - Authorities could be tricked into giving out the Exit flag to relays
11741 that didn't allow exiting to any ports. This bug could screw
11742 with load balancing and stats. Bugfix on 0.1.1.6-alpha; fixes bug
11743 1238. Bug discovered by Martin Kowalczyk.
11744 - When freeing a session key, zero it out completely. We only zeroed
11745 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11746 patched by ekir. Fixes bug 1254.
11749 - Fix static compilation by listing the openssl libraries in the right
11750 order. Bugfix on Tor 0.2.2.8-alpha; fixes bug 1237.
11751 - Resume handling .exit hostnames in a special way: originally we
11752 stripped the .exit part and used the requested exit relay. In
11753 0.2.2.1-alpha we stopped treating them in any special way, meaning
11754 if you use a .exit address then Tor will pass it on to the exit
11755 relay. Now we reject the .exit stream outright, since that behavior
11756 might be more expected by the user. Found and diagnosed by Scott
11757 Bennett and Downie on or-talk.
11758 - Don't spam the controller with events when we have no file
11759 descriptors available. Bugfix on 0.2.1.5-alpha. (Rate-limiting
11760 for log messages was already solved from bug 748.)
11761 - Avoid a bogus overlapped memcpy in tor_addr_copy(). Reported by
11763 - Make the DNSPort option work with libevent 2.x. Don't alter the
11764 behavior for libevent 1.x. Fixes bug 1143. Found by SwissTorExit.
11765 - Emit a GUARD DROPPED controller event for a case we missed.
11766 - Make more fields in the controller protocol case-insensitive, since
11767 control-spec.txt said they were.
11768 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11769 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11770 - Fix a spec conformance issue: the network-status-version token
11771 must be the first token in a v3 consensus or vote. Discovered by
11772 parakeep. Bugfix on 0.2.0.3-alpha.
11774 o Code simplifications and refactoring:
11775 - Generate our manpage and HTML documentation using Asciidoc. This
11776 change should make it easier to maintain the documentation, and
11777 produce nicer HTML.
11778 - Remove the --enable-iphone option. According to reports from Marco
11779 Bonetti, Tor builds fine without any special tweaking on recent
11780 iPhone SDK versions.
11781 - Removed some unnecessary files from the source distribution. The
11782 AUTHORS file has now been merged into the people page on the
11783 website. The roadmaps and design doc can now be found in the
11784 projects directory in svn.
11785 - Enabled various circuit build timeout constants to be controlled
11786 by consensus parameters. Also set better defaults for these
11787 parameters based on experimentation on broadband and simulated
11788 high latency links.
11791 - The 'EXTENDCIRCUIT' control port command can now be used with
11792 a circ id of 0 and no path. This feature will cause Tor to build
11793 a new 'fast' general purpose circuit using its own path selection
11795 - Added a BUILDTIMEOUT_SET controller event to describe changes
11796 to the circuit build timeout.
11797 - Future-proof the controller protocol a bit by ignoring keyword
11798 arguments we do not recognize.
11799 - Expand homedirs passed to tor-checkkey. This should silence a
11800 coverity complaint about passing a user-supplied string into
11801 open() without checking it.
11804 Changes in version 0.2.1.25 - 2010-03-16
11805 Tor 0.2.1.25 fixes a regression introduced in 0.2.1.23 that could
11806 prevent relays from guessing their IP address correctly. It also fixes
11807 several minor potential security bugs.
11810 - Fix a regression from our patch for bug 1244 that caused relays
11811 to guess their IP address incorrectly if they didn't set Address
11812 in their torrc and/or their address fails to resolve. Bugfix on
11813 0.2.1.23; fixes bug 1269.
11814 - When freeing a session key, zero it out completely. We only zeroed
11815 the first ptrsize bytes. Bugfix on 0.0.2pre8. Discovered and
11816 patched by ekir. Fixes bug 1254.
11819 - Fix a dereference-then-NULL-check sequence when publishing
11820 descriptors. Bugfix on 0.2.1.5-alpha. Discovered by ekir; fixes
11822 - Fix another dereference-then-NULL-check sequence. Bugfix on
11823 0.2.1.14-rc. Discovered by ekir; fixes bug 1256.
11824 - Make sure we treat potentially not NUL-terminated strings correctly.
11825 Bugfix on 0.1.1.13-alpha. Discovered by rieo; fixes bug 1257.
11829 Changes in version 0.2.1.24 - 2010-02-21
11830 Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time
11834 - Work correctly out-of-the-box with even more vendor-patched versions
11835 of OpenSSL. In particular, make it so Debian and OS X don't need
11836 customized patches to run/build.
11839 Changes in version 0.2.1.23 - 2010-02-13
11840 Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work
11841 again on the latest OS X, and updates the location of a directory
11844 o Major bugfixes (performance):
11845 - We were selecting our guards uniformly at random, and then weighting
11846 which of our guards we'd use uniformly at random. This imbalance
11847 meant that Tor clients were severely limited on throughput (and
11848 probably latency too) by the first hop in their circuit. Now we
11849 select guards weighted by currently advertised bandwidth. We also
11850 automatically discard guards picked using the old algorithm. Fixes
11851 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11854 - Make Tor work again on the latest OS X: when deciding whether to
11855 use strange flags to turn TLS renegotiation on, detect the OpenSSL
11856 version at run-time, not compile time. We need to do this because
11857 Apple doesn't update its dev-tools headers when it updates its
11858 libraries in a security patch.
11859 - Fix a potential buffer overflow in lookup_last_hid_serv_request()
11860 that could happen on 32-bit platforms with 64-bit time_t. Also fix
11861 a memory leak when requesting a hidden service descriptor we've
11862 requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found
11865 o Directory authority changes:
11866 - Change IP address for dannenberg (v3 directory authority), and
11867 remove moria2 (obsolete v1, v2 directory authority and v0 hidden
11868 service directory authority) from the list.
11871 - Refactor resolve_my_address() to not use gethostbyname() anymore.
11872 Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.
11875 - Avoid a mad rush at the beginning of each month when each client
11876 rotates half of its guards. Instead we spread the rotation out
11877 throughout the month, but we still avoid leaving a precise timestamp
11878 in the state file about when we first picked the guard. Improves
11879 over the behavior introduced in 0.1.2.17.
11882 Changes in version 0.2.2.8-alpha - 2010-01-26
11883 Tor 0.2.2.8-alpha fixes a crash bug in 0.2.2.7-alpha that has been
11884 causing bridge relays to disappear. If you're running a bridge,
11888 - Fix a memory corruption bug on bridges that occured during the
11889 inclusion of stats data in extra-info descriptors. Also fix the
11890 interface for geoip_get_bridge_stats* to prevent similar bugs in
11891 the future. Diagnosis by Tas, patch by Karsten and Sebastian.
11892 Fixes bug 1208; bugfix on 0.2.2.7-alpha.
11895 - Ignore OutboundBindAddress when connecting to localhost.
11896 Connections to localhost need to come _from_ localhost, or else
11897 local servers (like DNS and outgoing HTTP/SOCKS proxies) will often
11901 Changes in version 0.2.2.7-alpha - 2010-01-19
11902 Tor 0.2.2.7-alpha fixes a huge client-side performance bug, as well
11903 as laying the groundwork for further relay-side performance fixes. It
11904 also starts cleaning up client behavior with respect to the EntryNodes,
11905 ExitNodes, and StrictNodes config options.
11907 This release also rotates two directory authority keys, due to a
11908 security breach of some of the Torproject servers.
11910 o Directory authority changes:
11911 - Rotate keys (both v3 identity and relay identity) for moria1
11914 o Major features (performance):
11915 - We were selecting our guards uniformly at random, and then weighting
11916 which of our guards we'd use uniformly at random. This imbalance
11917 meant that Tor clients were severely limited on throughput (and
11918 probably latency too) by the first hop in their circuit. Now we
11919 select guards weighted by currently advertised bandwidth. We also
11920 automatically discard guards picked using the old algorithm. Fixes
11921 bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.
11922 - When choosing which cells to relay first, relays can now favor
11923 circuits that have been quiet recently, to provide lower latency
11924 for low-volume circuits. By default, relays enable or disable this
11925 feature based on a setting in the consensus. You can override
11926 this default by using the new "CircuitPriorityHalflife" config
11927 option. Design and code by Ian Goldberg, Can Tang, and Chris
11929 - Add separate per-conn write limiting to go with the per-conn read
11930 limiting. We added a global write limit in Tor 0.1.2.5-alpha,
11931 but never per-conn write limits.
11932 - New consensus params "bwconnrate" and "bwconnburst" to let us
11933 rate-limit client connections as they enter the network. It's
11934 controlled in the consensus so we can turn it on and off for
11935 experiments. It's starting out off. Based on proposal 163.
11937 o Major features (relay selection options):
11938 - Switch to a StrictNodes config option, rather than the previous
11939 "StrictEntryNodes" / "StrictExitNodes" separation that was missing a
11940 "StrictExcludeNodes" option.
11941 - If EntryNodes, ExitNodes, ExcludeNodes, or ExcludeExitNodes
11942 change during a config reload, mark and discard all our origin
11943 circuits. This fix should address edge cases where we change the
11944 config options and but then choose a circuit that we created before
11946 - If EntryNodes or ExitNodes are set, be more willing to use an
11947 unsuitable (e.g. slow or unstable) circuit. The user asked for it,
11949 - Make EntryNodes config option much more aggressive even when
11950 StrictNodes is not set. Before it would prepend your requested
11951 entrynodes to your list of guard nodes, but feel free to use others
11952 after that. Now it chooses only from your EntryNodes if any of
11953 those are available, and only falls back to others if a) they're
11954 all down and b) StrictNodes is not set.
11955 - Now we refresh your entry guards from EntryNodes at each consensus
11956 fetch -- rather than just at startup and then they slowly rot as
11957 the network changes.
11960 - Stop bridge directory authorities from answering dbg-stability.txt
11961 directory queries, which would let people fetch a list of all
11962 bridge identities they track. Bugfix on 0.2.1.6-alpha.
11965 - Log a notice when we get a new control connection. Now it's easier
11966 for security-conscious users to recognize when a local application
11967 is knocking on their controller door. Suggested by bug 1196.
11968 - New config option "CircuitStreamTimeout" to override our internal
11969 timeout schedule for how many seconds until we detach a stream from
11970 a circuit and try a new circuit. If your network is particularly
11971 slow, you might want to set this to a number like 60.
11972 - New controller command "getinfo config-text". It returns the
11973 contents that Tor would write if you send it a SAVECONF command,
11974 so the controller can write the file to disk itself.
11975 - New options for SafeLogging to allow scrubbing only log messages
11976 generated while acting as a relay.
11977 - Ship the bridges spec file in the tarball too.
11978 - Avoid a mad rush at the beginning of each month when each client
11979 rotates half of its guards. Instead we spread the rotation out
11980 throughout the month, but we still avoid leaving a precise timestamp
11981 in the state file about when we first picked the guard. Improves
11982 over the behavior introduced in 0.1.2.17.
11984 o Minor bugfixes (compiling):
11985 - Fix compilation on OS X 10.3, which has a stub mlockall() but
11986 hides it. Bugfix on 0.2.2.6-alpha.
11987 - Fix compilation on Solaris by removing support for the
11988 DisableAllSwap config option. Solaris doesn't have an rlimit for
11989 mlockall, so we cannot use it safely. Fixes bug 1198; bugfix on
11992 o Minor bugfixes (crashes):
11993 - Do not segfault when writing buffer stats when we haven't observed
11994 a single circuit to report about. Found by Fabian Lanze. Bugfix on
11996 - If we're in the pathological case where there's no exit bandwidth
11997 but there is non-exit bandwidth, or no guard bandwidth but there
11998 is non-guard bandwidth, don't crash during path selection. Bugfix
12000 - Fix an impossible-to-actually-trigger buffer overflow in relay
12001 descriptor generation. Bugfix on 0.1.0.15.
12003 o Minor bugfixes (privacy):
12004 - Fix an instance where a Tor directory mirror might accidentally
12005 log the IP address of a misbehaving Tor client. Bugfix on
12007 - Don't list Windows capabilities in relay descriptors. We never made
12008 use of them, and maybe it's a bad idea to publish them. Bugfix
12011 o Minor bugfixes (other):
12012 - Resolve an edge case in path weighting that could make us misweight
12013 our relay selection. Fixes bug 1203; bugfix on 0.0.8rc1.
12014 - Fix statistics on client numbers by country as seen by bridges that
12015 were broken in 0.2.2.1-alpha. Also switch to reporting full 24-hour
12016 intervals instead of variable 12-to-48-hour intervals.
12017 - After we free an internal connection structure, overwrite it
12018 with a different memory value than we use for overwriting a freed
12019 internal circuit structure. Should help with debugging. Suggested
12021 - Update our OpenSSL 0.9.8l fix so that it works with OpenSSL 0.9.8m
12024 o Removed features:
12025 - Remove the HSAuthorityRecordStats option that version 0 hidden
12026 service authorities could have used to track statistics of overall
12027 hidden service usage.
12030 Changes in version 0.2.1.22 - 2010-01-19
12031 Tor 0.2.1.22 fixes a critical privacy problem in bridge directory
12032 authorities -- it would tell you its whole history of bridge descriptors
12033 if you make the right directory request. This stable update also
12034 rotates two of the seven v3 directory authority keys and locations.
12036 o Directory authority changes:
12037 - Rotate keys (both v3 identity and relay identity) for moria1
12041 - Stop bridge directory authorities from answering dbg-stability.txt
12042 directory queries, which would let people fetch a list of all
12043 bridge identities they track. Bugfix on 0.2.1.6-alpha.
12046 Changes in version 0.2.1.21 - 2009-12-21
12047 Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
12048 library. If you use Tor on Linux / Unix and you're getting SSL
12049 renegotiation errors, upgrading should help. We also recommend an
12050 upgrade if you're an exit relay.
12053 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12054 handshake from working unless we explicitly tell OpenSSL that we
12055 are using SSL renegotiation safely. We are, of course, but OpenSSL
12056 0.9.8l won't work unless we say we are.
12057 - Avoid crashing if the client is trying to upload many bytes and the
12058 circuit gets torn down at the same time, or if the flip side
12059 happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.
12062 - Do not refuse to learn about authority certs and v2 networkstatus
12063 documents that are older than the latest consensus. This bug might
12064 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12065 Spotted and fixed by xmux.
12066 - Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
12067 trigger platform-specific option misparsing case found by Coverity
12069 - Fix a compilation warning on Fedora 12 by removing an impossible-to-
12070 trigger assert. Fixes bug 1173.
12073 Changes in version 0.2.2.6-alpha - 2009-11-19
12074 Tor 0.2.2.6-alpha lays the groundwork for many upcoming features:
12075 support for the new lower-footprint "microdescriptor" directory design,
12076 future-proofing our consensus format against new hash functions or
12077 other changes, and an Android port. It also makes Tor compatible with
12078 the upcoming OpenSSL 0.9.8l release, and fixes a variety of bugs.
12081 - Directory authorities can now create, vote on, and serve multiple
12082 parallel formats of directory data as part of their voting process.
12083 Partially implements Proposal 162: "Publish the consensus in
12085 - Directory authorities can now agree on and publish small summaries
12086 of router information that clients can use in place of regular
12087 server descriptors. This transition will eventually allow clients
12088 to use far less bandwidth for downloading information about the
12089 network. Begins the implementation of Proposal 158: "Clients
12090 download consensus + microdescriptors".
12091 - The directory voting system is now extensible to use multiple hash
12092 algorithms for signatures and resource selection. Newer formats
12093 are signed with SHA256, with a possibility for moving to a better
12094 hash algorithm in the future.
12095 - New DisableAllSwap option. If set to 1, Tor will attempt to lock all
12096 current and future memory pages via mlockall(). On supported
12097 platforms (modern Linux and probably BSD but not Windows or OS X),
12098 this should effectively disable any and all attempts to page out
12099 memory. This option requires that you start your Tor as root --
12100 if you use DisableAllSwap, please consider using the User option
12101 to properly reduce the privileges of your Tor.
12102 - Numerous changes, bugfixes, and workarounds from Nathan Freitas
12103 to help Tor build correctly for Android phones.
12106 - Work around a security feature in OpenSSL 0.9.8l that prevents our
12107 handshake from working unless we explicitly tell OpenSSL that we
12108 are using SSL renegotiation safely. We are, but OpenSSL 0.9.8l
12109 won't work unless we say we are.
12112 - Fix a crash bug when trying to initialize the evdns module in
12113 Libevent 2. Bugfix on 0.2.1.16-rc.
12114 - Stop logging at severity 'warn' when some other Tor client tries
12115 to establish a circuit with us using weak DH keys. It's a protocol
12116 violation, but that doesn't mean ordinary users need to hear about
12117 it. Fixes the bug part of bug 1114. Bugfix on 0.1.0.13.
12118 - Do not refuse to learn about authority certs and v2 networkstatus
12119 documents that are older than the latest consensus. This bug might
12120 have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
12121 Spotted and fixed by xmux.
12122 - Fix numerous small code-flaws found by Coverity Scan Rung 3.
12123 - If all authorities restart at once right before a consensus vote,
12124 nobody will vote about "Running", and clients will get a consensus
12125 with no usable relays. Instead, authorities refuse to build a
12126 consensus if this happens. Bugfix on 0.2.0.10-alpha; fixes bug 1066.
12127 - If your relay can't keep up with the number of incoming create
12128 cells, it would log one warning per failure into your logs. Limit
12129 warnings to 1 per minute. Bugfix on 0.0.2pre10; fixes bug 1042.
12130 - Bridges now use "reject *:*" as their default exit policy. Bugfix
12131 on 0.2.0.3-alpha; fixes bug 1113.
12132 - Fix a memory leak on directory authorities during voting that was
12133 introduced in 0.2.2.1-alpha. Found via valgrind.
12136 Changes in version 0.2.1.20 - 2009-10-15
12137 Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden
12138 services at once, prepares for more performance improvements, and
12139 fixes a bunch of smaller bugs.
12141 The Windows and OS X bundles also include a more recent Vidalia,
12142 and switch from Privoxy to Polipo.
12144 The OS X installers are now drag and drop. It's best to un-install
12145 Tor/Vidalia and then install this new bundle, rather than upgrade. If
12146 you want to upgrade, you'll need to update the paths for Tor and Polipo
12147 in the Vidalia Settings window.
12150 - Send circuit or stream sendme cells when our window has decreased
12151 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12152 by Karsten when testing the "reduce circuit window" performance
12153 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12154 before the release of Tor 0.0.0. This is the new winner of the
12156 - Fix a remotely triggerable memory leak when a consensus document
12157 contains more than one signature from the same voter. Bugfix on
12159 - Avoid segfault in rare cases when finishing an introduction circuit
12160 as a client and finding out that we don't have an introduction key
12161 for it. Fixes bug 1073. Reported by Aaron Swartz.
12164 - Tor now reads the "circwindow" parameter out of the consensus,
12165 and uses that value for its circuit package window rather than the
12166 default of 1000 cells. Begins the implementation of proposal 168.
12168 o New directory authorities:
12169 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12171 - Move moria1 and tonga to alternate IP addresses.
12174 - Fix a signed/unsigned compile warning in 0.2.1.19.
12175 - Fix possible segmentation fault on directory authorities. Bugfix on
12177 - Fix an extremely rare infinite recursion bug that could occur if
12178 we tried to log a message after shutting down the log subsystem.
12179 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12180 - Fix an obscure bug where hidden services on 64-bit big-endian
12181 systems might mis-read the timestamp in v3 introduce cells, and
12182 refuse to connect back to the client. Discovered by "rotor".
12183 Bugfix on 0.2.1.6-alpha.
12184 - We were triggering a CLOCK_SKEW controller status event whenever
12185 we connect via the v2 connection protocol to any relay that has
12186 a wrong clock. Instead, we should only inform the controller when
12187 it's a trusted authority that claims our clock is wrong. Bugfix
12188 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12189 - We were telling the controller about CHECKING_REACHABILITY and
12190 REACHABILITY_FAILED status events whenever we launch a testing
12191 circuit or notice that one has failed. Instead, only tell the
12192 controller when we want to inform the user of overall success or
12193 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12195 - Don't warn when we're using a circuit that ends with a node
12196 excluded in ExcludeExitNodes, but the circuit is not used to access
12197 the outside world. This should help fix bug 1090. Bugfix on
12199 - Work around a small memory leak in some versions of OpenSSL that
12200 stopped the memory used by the hostname TLS extension from being
12204 - Add a "getinfo status/accepted-server-descriptor" controller
12205 command, which is the recommended way for controllers to learn
12206 whether our server descriptor has been successfully received by at
12207 least on directory authority. Un-recommend good-server-descriptor
12208 getinfo and status events until we have a better design for them.
12211 Changes in version 0.2.2.5-alpha - 2009-10-11
12212 Tor 0.2.2.5-alpha fixes a few compile problems in 0.2.2.4-alpha.
12215 - Make the tarball compile again. Oops. Bugfix on 0.2.2.4-alpha.
12217 o Directory authorities:
12218 - Temporarily (just for this release) move dizum to an alternate
12222 Changes in version 0.2.2.4-alpha - 2009-10-10
12223 Tor 0.2.2.4-alpha fixes more crash bugs in 0.2.2.2-alpha. It also
12224 introduces a new unit test framework, shifts directry authority
12225 addresses around to reduce the impact from recent blocking events,
12226 and fixes a few smaller bugs.
12229 - Fix several more asserts in the circuit_build_times code, for
12230 example one that causes Tor to fail to start once we have
12231 accumulated 5000 build times in the state file. Bugfixes on
12232 0.2.2.2-alpha; fixes bug 1108.
12234 o New directory authorities:
12235 - Move moria1 and Tonga to alternate IP addresses.
12238 - Log SSL state transitions at debug level during handshake, and
12239 include SSL states in error messages. This may help debug future
12240 SSL handshake issues.
12241 - Add a new "Handshake" log domain for activities that happen
12242 during the TLS handshake.
12243 - Revert to the "June 3 2009" ip-to-country file. The September one
12244 seems to have removed most US IP addresses.
12245 - Directory authorities now reject Tor relays with versions less than
12246 0.1.2.14. This step cuts out four relays from the current network,
12247 none of which are very big.
12250 - Fix a couple of smaller issues with gathering statistics. Bugfixes
12252 - Fix two memory leaks in the error case of
12253 circuit_build_times_parse_state(). Bugfix on 0.2.2.2-alpha.
12254 - Don't count one-hop circuits when we're estimating how long it
12255 takes circuits to build on average. Otherwise we'll set our circuit
12256 build timeout lower than we should. Bugfix on 0.2.2.2-alpha.
12257 - Directory authorities no longer change their opinion of, or vote on,
12258 whether a router is Running, unless they have themselves been
12259 online long enough to have some idea. Bugfix on 0.2.0.6-alpha.
12262 o Code simplifications and refactoring:
12263 - Revise our unit tests to use the "tinytest" framework, so we
12264 can run tests in their own processes, have smarter setup/teardown
12265 code, and so on. The unit test code has moved to its own
12266 subdirectory, and has been split into multiple modules.
12269 Changes in version 0.2.2.3-alpha - 2009-09-23
12270 Tor 0.2.2.3-alpha fixes a few crash bugs in 0.2.2.2-alpha.
12273 - Fix an overzealous assert in our new circuit build timeout code.
12274 Bugfix on 0.2.2.2-alpha; fixes bug 1103.
12277 - If the networkstatus consensus tells us that we should use a
12278 negative circuit package window, ignore it. Otherwise we'll
12279 believe it and then trigger an assert. Bugfix on 0.2.2.2-alpha.
12282 Changes in version 0.2.2.2-alpha - 2009-09-21
12283 Tor 0.2.2.2-alpha introduces our latest performance improvement for
12284 clients: Tor tracks the average time it takes to build a circuit, and
12285 avoids using circuits that take too long to build. For fast connections,
12286 this feature can cut your expected latency in half. For slow or flaky
12287 connections, it could ruin your Tor experience. Let us know if it does!
12290 - Tor now tracks how long it takes to build client-side circuits
12291 over time, and adapts its timeout to local network performance.
12292 Since a circuit that takes a long time to build will also provide
12293 bad performance, we get significant latency improvements by
12294 discarding the slowest 20% of circuits. Specifically, Tor creates
12295 circuits more aggressively than usual until it has enough data
12296 points for a good timeout estimate. Implements proposal 151.
12297 We are especially looking for reports (good and bad) from users with
12298 both EDGE and broadband connections that can move from broadband
12299 to EDGE and find out if the build-time data in the .tor/state gets
12300 reset without loss of Tor usability. You should also see a notice
12301 log message telling you that Tor has reset its timeout.
12302 - Directory authorities can now vote on arbitary integer values as
12303 part of the consensus process. This is designed to help set
12304 network-wide parameters. Implements proposal 167.
12305 - Tor now reads the "circwindow" parameter out of the consensus,
12306 and uses that value for its circuit package window rather than the
12307 default of 1000 cells. Begins the implementation of proposal 168.
12310 - Fix a remotely triggerable memory leak when a consensus document
12311 contains more than one signature from the same voter. Bugfix on
12315 - Fix an extremely rare infinite recursion bug that could occur if
12316 we tried to log a message after shutting down the log subsystem.
12317 Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
12318 - Fix parsing for memory or time units given without a space between
12319 the number and the unit. Bugfix on 0.2.2.1-alpha; fixes bug 1076.
12320 - A networkstatus vote must contain exactly one signature. Spec
12321 conformance issue. Bugfix on 0.2.0.3-alpha.
12322 - Fix an obscure bug where hidden services on 64-bit big-endian
12323 systems might mis-read the timestamp in v3 introduce cells, and
12324 refuse to connect back to the client. Discovered by "rotor".
12325 Bugfix on 0.2.1.6-alpha.
12326 - We were triggering a CLOCK_SKEW controller status event whenever
12327 we connect via the v2 connection protocol to any relay that has
12328 a wrong clock. Instead, we should only inform the controller when
12329 it's a trusted authority that claims our clock is wrong. Bugfix
12330 on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
12331 - We were telling the controller about CHECKING_REACHABILITY and
12332 REACHABILITY_FAILED status events whenever we launch a testing
12333 circuit or notice that one has failed. Instead, only tell the
12334 controller when we want to inform the user of overall success or
12335 overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
12337 - Don't warn when we're using a circuit that ends with a node
12338 excluded in ExcludeExitNodes, but the circuit is not used to access
12339 the outside world. This should help fix bug 1090, but more problems
12340 remain. Bugfix on 0.2.1.6-alpha.
12341 - Work around a small memory leak in some versions of OpenSSL that
12342 stopped the memory used by the hostname TLS extension from being
12344 - Make our 'torify' script more portable; if we have only one of
12345 'torsocks' or 'tsocks' installed, don't complain to the user;
12346 and explain our warning about tsocks better.
12349 - Add a "getinfo status/accepted-server-descriptor" controller
12350 command, which is the recommended way for controllers to learn
12351 whether our server descriptor has been successfully received by at
12352 least on directory authority. Un-recommend good-server-descriptor
12353 getinfo and status events until we have a better design for them.
12354 - Update to the "September 4 2009" ip-to-country file.
12357 Changes in version 0.2.2.1-alpha - 2009-08-26
12358 Tor 0.2.2.1-alpha disables ".exit" address notation by default, allows
12359 Tor clients to bootstrap on networks where only port 80 is reachable,
12360 makes it more straightforward to support hardware crypto accelerators,
12361 and starts the groundwork for gathering stats safely at relays.
12364 - Start the process of disabling ".exit" address notation, since it
12365 can be used for a variety of esoteric application-level attacks
12366 on users. To reenable it, set "AllowDotExit 1" in your torrc. Fix
12369 o New directory authorities:
12370 - Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
12374 - New AccelName and AccelDir options add support for dynamic OpenSSL
12375 hardware crypto acceleration engines.
12376 - Tor now supports tunneling all of its outgoing connections over
12377 a SOCKS proxy, using the SOCKS4Proxy and/or SOCKS5Proxy
12378 configuration options. Code by Christopher Davis.
12381 - Send circuit or stream sendme cells when our window has decreased
12382 by 100 cells, not when it has decreased by 101 cells. Bug uncovered
12383 by Karsten when testing the "reduce circuit window" performance
12384 patch. Bugfix on the 54th commit on Tor -- from July 2002,
12385 before the release of Tor 0.0.0. This is the new winner of the
12388 o New options for gathering stats safely:
12389 - Directory mirrors that set "DirReqStatistics 1" write statistics
12390 about directory requests to disk every 24 hours. As compared to the
12391 --enable-geoip-stats flag in 0.2.1.x, there are a few improvements:
12392 1) stats are written to disk exactly every 24 hours; 2) estimated
12393 shares of v2 and v3 requests are determined as mean values, not at
12394 the end of a measurement period; 3) unresolved requests are listed
12395 with country code '??'; 4) directories also measure download times.
12396 - Exit nodes that set "ExitPortStatistics 1" write statistics on the
12397 number of exit streams and transferred bytes per port to disk every
12399 - Relays that set "CellStatistics 1" write statistics on how long
12400 cells spend in their circuit queues to disk every 24 hours.
12401 - Entry nodes that set "EntryStatistics 1" write statistics on the
12402 rough number and origins of connecting clients to disk every 24
12404 - Relays that write any of the above statistics to disk and set
12405 "ExtraInfoStatistics 1" include the past 24 hours of statistics in
12406 their extra-info documents.
12409 - New --digests command-line switch to output the digests of the
12410 source files Tor was built with.
12411 - The "torify" script now uses torsocks where available.
12412 - The memarea code now uses a sentinel value at the end of each area
12413 to make sure nothing writes beyond the end of an area. This might
12414 help debug some conceivable causes of bug 930.
12415 - Time and memory units in the configuration file can now be set to
12416 fractional units. For example, "2.5 GB" is now a valid value for
12418 - Certain Tor clients (such as those behind check.torproject.org) may
12419 want to fetch the consensus in an extra early manner. To enable this
12420 a user may now set FetchDirInfoExtraEarly to 1. This also depends on
12421 setting FetchDirInfoEarly to 1. Previous behavior will stay the same
12422 as only certain clients who must have this information sooner should
12424 - Instead of adding the svn revision to the Tor version string, report
12425 the git commit (when we're building from a git checkout).
12428 - If any of the v3 certs we download are unparseable, we should
12429 actually notice the failure so we don't retry indefinitely. Bugfix
12430 on 0.2.0.x; reported by "rotator".
12431 - If the cached cert file is unparseable, warn but don't exit.
12432 - Fix possible segmentation fault on directory authorities. Bugfix on
12434 - When Tor fails to parse a descriptor of any kind, dump it to disk.
12435 Might help diagnosing bug 1051.
12437 o Deprecated and removed features:
12438 - The controller no longer accepts the old obsolete "addr-mappings/"
12439 or "unregistered-servers-" GETINFO values.
12440 - Hidden services no longer publish version 0 descriptors, and clients
12441 do not request or use version 0 descriptors. However, the old hidden
12442 service authorities still accept and serve version 0 descriptors
12443 when contacted by older hidden services/clients.
12444 - The EXTENDED_EVENTS and VERBOSE_NAMES controller features are now
12445 always on; using them is necessary for correct forward-compatible
12447 - Remove support for .noconnect style addresses. Nobody was using
12448 them, and they provided another avenue for detecting Tor users
12449 via application-level web tricks.
12451 o Packaging changes:
12452 - Upgrade Vidalia from 0.1.15 to 0.2.3 in the Windows and OS X
12453 installer bundles. See
12454 https://trac.vidalia-project.net/browser/vidalia/tags/vidalia-0.2.3/CHANGELOG
12455 for details of what's new in Vidalia 0.2.3.
12456 - Windows Vidalia Bundle: update Privoxy from 3.0.6 to 3.0.14-beta.
12457 - OS X Vidalia Bundle: move to Polipo 1.0.4 with Tor specific
12458 configuration file, rather than the old Privoxy.
12459 - OS X Vidalia Bundle: Vidalia, Tor, and Polipo are compiled as
12460 x86-only for better compatibility with OS X 10.6, aka Snow Leopard.
12461 - OS X Tor Expert Bundle: Tor is compiled as x86-only for
12462 better compatibility with OS X 10.6, aka Snow Leopard.
12463 - OS X Vidalia Bundle: The multi-package installer is now replaced
12464 by a simple drag and drop to the /Applications folder. This change
12465 occurred with the upgrade to Vidalia 0.2.3.
12468 Changes in version 0.2.1.19 - 2009-07-28
12469 Tor 0.2.1.19 fixes a major bug with accessing and providing hidden
12470 services on Tor 0.2.1.3-alpha through 0.2.1.18.
12473 - Make accessing hidden services on 0.2.1.x work right again.
12474 Bugfix on 0.2.1.3-alpha; workaround for bug 1038. Diagnosis and
12475 part of patch provided by "optimist".
12478 - When a relay/bridge is writing out its identity key fingerprint to
12479 the "fingerprint" file and to its logs, write it without spaces. Now
12480 it will look like the fingerprints in our bridges documentation,
12481 and confuse fewer users.
12484 - Relays no longer publish a new server descriptor if they change
12485 their MaxAdvertisedBandwidth config option but it doesn't end up
12486 changing their advertised bandwidth numbers. Bugfix on 0.2.0.28-rc;
12487 fixes bug 1026. Patch from Sebastian.
12488 - Avoid leaking memory every time we get a create cell but we have
12489 so many already queued that we refuse it. Bugfix on 0.2.0.19-alpha;
12490 fixes bug 1034. Reported by BarkerJr.
12493 Changes in version 0.2.1.18 - 2009-07-24
12494 Tor 0.2.1.18 lays the foundations for performance improvements,
12495 adds status events to help users diagnose bootstrap problems, adds
12496 optional authentication/authorization for hidden services, fixes a
12497 variety of potential anonymity problems, and includes a huge pile of
12498 other features and bug fixes.
12501 - Add LIBS=-lrt to Makefile.am so the Tor RPMs use a static libevent.
12504 Changes in version 0.2.1.17-rc - 2009-07-07
12505 Tor 0.2.1.17-rc marks the fourth -- and hopefully last -- release
12506 candidate for the 0.2.1.x series. It lays the groundwork for further
12507 client performance improvements, and also fixes a big bug with directory
12508 authorities that were causing them to assign Guard and Stable flags
12511 The Windows bundles also finally include the geoip database that we
12512 thought we'd been shipping since 0.2.0.x (oops), and the OS X bundles
12513 should actually install Torbutton rather than giving you a cryptic
12514 failure message (oops).
12517 - Clients now use the bandwidth values in the consensus, rather than
12518 the bandwidth values in each relay descriptor. This approach opens
12519 the door to more accurate bandwidth estimates once the directory
12520 authorities start doing active measurements. Implements more of
12524 - When Tor clients restart after 1-5 days, they discard all their
12525 cached descriptors as too old, but they still use the cached
12526 consensus document. This approach is good for robustness, but
12527 bad for performance: since they don't know any bandwidths, they
12528 end up choosing at random rather than weighting their choice by
12529 speed. Fixed by the above feature of putting bandwidths in the
12530 consensus. Bugfix on 0.2.0.x.
12531 - Directory authorities were neglecting to mark relays down in their
12532 internal histories if the relays fall off the routerlist without
12533 ever being found unreachable. So there were relays in the histories
12534 that haven't been seen for eight months, and are listed as being
12535 up for eight months. This wreaked havoc on the "median wfu"
12536 and "median mtbf" calculations, in turn making Guard and Stable
12537 flags very wrong, hurting network performance. Fixes bugs 696 and
12538 969. Bugfix on 0.2.0.6-alpha.
12541 - Serve the DirPortFrontPage page even when we have been approaching
12542 our quotas recently. Fixes bug 1013; bugfix on 0.2.1.8-alpha.
12543 - The control port would close the connection before flushing long
12544 replies, such as the network consensus, if a QUIT command was issued
12545 before the reply had completed. Now, the control port flushes all
12546 pending replies before closing the connection. Also fixed a spurious
12547 warning when a QUIT command is issued after a malformed or rejected
12548 AUTHENTICATE command, but before the connection was closed. Patch
12549 by Marcus Griep. Bugfix on 0.2.0.x; fixes bugs 1015 and 1016.
12550 - When we can't find an intro key for a v2 hidden service descriptor,
12551 fall back to the v0 hidden service descriptor and log a bug message.
12552 Workaround for bug 1024.
12553 - Fix a log message that did not respect the SafeLogging option.
12557 - If we're a relay and we change our IP address, be more verbose
12558 about the reason that made us change. Should help track down
12559 further bugs for relays on dynamic IP addresses.
12562 Changes in version 0.2.0.35 - 2009-06-24
12564 - Avoid crashing in the presence of certain malformed descriptors.
12565 Found by lark, and by automated fuzzing.
12566 - Fix an edge case where a malicious exit relay could convince a
12567 controller that the client's DNS question resolves to an internal IP
12568 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12571 - Finally fix the bug where dynamic-IP relays disappear when their
12572 IP address changes: directory mirrors were mistakenly telling
12573 them their old address if they asked via begin_dir, so they
12574 never got an accurate answer about their new address, so they
12575 just vanished after a day. For belt-and-suspenders, relays that
12576 don't set Address in their config now avoid using begin_dir for
12577 all direct connections. Should fix bugs 827, 883, and 900.
12578 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12579 that would occur on some exit nodes when DNS failures and timeouts
12580 occurred in certain patterns. Fix for bug 957.
12583 - When starting with a cache over a few days old, do not leak
12584 memory for the obsolete router descriptors in it. Bugfix on
12585 0.2.0.33; fixes bug 672.
12586 - Hidden service clients didn't use a cached service descriptor that
12587 was older than 15 minutes, but wouldn't fetch a new one either,
12588 because there was already one in the cache. Now, fetch a v2
12589 descriptor unless the same descriptor was added to the cache within
12590 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12593 Changes in version 0.2.1.16-rc - 2009-06-20
12594 Tor 0.2.1.16-rc speeds up performance for fast exit relays, and fixes
12595 a bunch of minor bugs.
12598 - Fix an edge case where a malicious exit relay could convince a
12599 controller that the client's DNS question resolves to an internal IP
12600 address. Bug found and fixed by "optimist"; bugfix on 0.1.2.8-beta.
12602 o Major performance improvements (on 0.2.0.x):
12603 - Disable and refactor some debugging checks that forced a linear scan
12604 over the whole server-side DNS cache. These accounted for over 50%
12605 of CPU time on a relatively busy exit node's gprof profile. Found
12607 - Disable some debugging checks that appeared in exit node profile
12611 - Update to the "June 3 2009" ip-to-country file.
12612 - Do not have tor-resolve automatically refuse all .onion addresses;
12613 if AutomapHostsOnResolve is set in your torrc, this will work fine.
12615 o Minor bugfixes (on 0.2.0.x):
12616 - Log correct error messages for DNS-related network errors on
12618 - Fix a race condition that could cause crashes or memory corruption
12619 when running as a server with a controller listening for log
12621 - Avoid crashing when we have a policy specified in a DirPolicy or
12622 SocksPolicy or ReachableAddresses option with ports set on it,
12623 and we re-load the policy. May fix bug 996.
12624 - Hidden service clients didn't use a cached service descriptor that
12625 was older than 15 minutes, but wouldn't fetch a new one either,
12626 because there was already one in the cache. Now, fetch a v2
12627 descriptor unless the same descriptor was added to the cache within
12628 the last 15 minutes. Fixes bug 997; reported by Marcus Griep.
12630 o Minor bugfixes (on 0.2.1.x):
12631 - Don't warn users about low port and hibernation mix when they
12632 provide a *ListenAddress directive to fix that. Bugfix on
12634 - When switching back and forth between bridge mode, do not start
12635 gathering GeoIP data until two hours have passed.
12636 - Do not complain that the user has requested an excluded node as
12637 an exit when the node is not really an exit. This could happen
12638 because the circuit was for testing, or an introduction point.
12642 Changes in version 0.2.1.15-rc - 2009-05-25
12643 Tor 0.2.1.15-rc marks the second release candidate for the 0.2.1.x
12644 series. It fixes a major bug on fast exit relays, as well as a variety
12645 of more minor bugs.
12647 o Major bugfixes (on 0.2.0.x):
12648 - Fix a timing-dependent, allocator-dependent, DNS-related crash bug
12649 that would occur on some exit nodes when DNS failures and timeouts
12650 occurred in certain patterns. Fix for bug 957.
12652 o Minor bugfixes (on 0.2.0.x):
12653 - Actually return -1 in the error case for read_bandwidth_usage().
12654 Harmless bug, since we currently don't care about the return value
12655 anywhere. Bugfix on 0.2.0.9-alpha.
12656 - Provide a more useful log message if bug 977 (related to buffer
12657 freelists) ever reappears, and do not crash right away.
12658 - Fix an assertion failure on 64-bit platforms when we allocated
12659 memory right up to the end of a memarea, then realigned the memory
12660 one step beyond the end. Fixes a possible cause of bug 930.
12661 - Protect the count of open sockets with a mutex, so we can't
12662 corrupt it when two threads are closing or opening sockets at once.
12663 Fix for bug 939. Bugfix on 0.2.0.1-alpha.
12664 - Don't allow a bridge to publish its router descriptor to a
12665 non-bridge directory authority. Fixes part of bug 932.
12666 - When we change to or from being a bridge, reset our counts of
12667 client usage by country. Fixes bug 932.
12668 - Fix a bug that made stream bandwidth get misreported to the
12670 - Stop using malloc_usable_size() to use more area than we had
12671 actually allocated: it was safe, but made valgrind really unhappy.
12672 - Fix a memory leak when v3 directory authorities load their keys
12673 and cert from disk. Bugfix on 0.2.0.1-alpha.
12675 o Minor bugfixes (on 0.2.1.x):
12676 - Fix use of freed memory when deciding to mark a non-addable
12677 descriptor as never-downloadable. Bugfix on 0.2.1.9-alpha.
12680 Changes in version 0.2.1.14-rc - 2009-04-12
12681 Tor 0.2.1.14-rc marks the first release candidate for the 0.2.1.x
12682 series. It begins fixing some major performance problems, and also
12683 finally addresses the bug that was causing relays on dynamic IP
12684 addresses to fall out of the directory.
12687 - Clients replace entry guards that were chosen more than a few months
12688 ago. This change should significantly improve client performance,
12689 especially once more people upgrade, since relays that have been
12690 a guard for a long time are currently overloaded.
12692 o Major bugfixes (on 0.2.0):
12693 - Finally fix the bug where dynamic-IP relays disappear when their
12694 IP address changes: directory mirrors were mistakenly telling
12695 them their old address if they asked via begin_dir, so they
12696 never got an accurate answer about their new address, so they
12697 just vanished after a day. For belt-and-suspenders, relays that
12698 don't set Address in their config now avoid using begin_dir for
12699 all direct connections. Should fix bugs 827, 883, and 900.
12700 - Relays were falling out of the networkstatus consensus for
12701 part of a day if they changed their local config but the
12702 authorities discarded their new descriptor as "not sufficiently
12703 different". Now directory authorities accept a descriptor as changed
12704 if bandwidthrate or bandwidthburst changed. Partial fix for bug 962;
12705 patch by Sebastian.
12706 - Avoid crashing in the presence of certain malformed descriptors.
12707 Found by lark, and by automated fuzzing.
12710 - When generating circuit events with verbose nicknames for
12711 controllers, try harder to look up nicknames for routers on a
12712 circuit. (Previously, we would look in the router descriptors we had
12713 for nicknames, but not in the consensus.) Partial fix for bug 941.
12714 - If the bridge config line doesn't specify a port, assume 443.
12715 This makes bridge lines a bit smaller and easier for users to
12717 - Raise the minimum bandwidth to be a relay from 20000 bytes to 20480
12718 bytes (aka 20KB/s), to match our documentation. Also update
12719 directory authorities so they always assign the Fast flag to relays
12720 with 20KB/s of capacity. Now people running relays won't suddenly
12721 find themselves not seeing any use, if the network gets faster
12723 - Update to the "April 3 2009" ip-to-country file.
12726 - Avoid trying to print raw memory to the logs when we decide to
12727 give up on downloading a given relay descriptor. Bugfix on
12729 - In tor-resolve, when the Tor client to use is specified by
12730 <hostname>:<port>, actually use the specified port rather than
12731 defaulting to 9050. Bugfix on 0.2.1.6-alpha.
12732 - Make directory usage recording work again. Bugfix on 0.2.1.6-alpha.
12733 - When starting with a cache over a few days old, do not leak
12734 memory for the obsolete router descriptors in it. Bugfix on
12736 - Avoid double-free on list of successfully uploaded hidden
12737 service discriptors. Fix for bug 948. Bugfix on 0.2.1.6-alpha.
12738 - Change memarea_strndup() implementation to work even when
12739 duplicating a string at the end of a page. This bug was
12740 harmless for now, but could have meant crashes later. Fix by
12741 lark. Bugfix on 0.2.1.1-alpha.
12742 - Limit uploaded directory documents to be 16M rather than 500K.
12743 The directory authorities were refusing v3 consensus votes from
12744 other authorities, since the votes are now 504K. Fixes bug 959;
12745 bugfix on 0.0.2pre17 (where we raised it from 50K to 500K ;).
12746 - Directory authorities should never send a 503 "busy" response to
12747 requests for votes or keys. Bugfix on 0.2.0.8-alpha; exposed by
12751 Changes in version 0.2.1.13-alpha - 2009-03-09
12752 Tor 0.2.1.13-alpha includes another big pile of minor bugfixes and
12753 cleanups. We're finally getting close to a release candidate.
12756 - Correctly update the list of which countries we exclude as
12757 exits, when the GeoIP file is loaded or reloaded. Diagnosed by
12758 lark. Bugfix on 0.2.1.6-alpha.
12760 o Minor bugfixes (on 0.2.0.x and earlier):
12761 - Automatically detect MacOSX versions earlier than 10.4.0, and
12762 disable kqueue from inside Tor when running with these versions.
12763 We previously did this from the startup script, but that was no
12764 help to people who didn't use the startup script. Resolves bug 863.
12765 - When we had picked an exit node for a connection, but marked it as
12766 "optional", and it turned out we had no onion key for the exit,
12767 stop wanting that exit and try again. This situation may not
12768 be possible now, but will probably become feasible with proposal
12769 158. Spotted by rovv. Fixes another case of bug 752.
12770 - Clients no longer cache certificates for authorities they do not
12771 recognize. Bugfix on 0.2.0.9-alpha.
12772 - When we can't transmit a DNS request due to a network error, retry
12773 it after a while, and eventually transmit a failing response to
12774 the RESOLVED cell. Bugfix on 0.1.2.5-alpha.
12775 - If the controller claimed responsibility for a stream, but that
12776 stream never finished making its connection, it would live
12777 forever in circuit_wait state. Now we close it after SocksTimeout
12778 seconds. Bugfix on 0.1.2.7-alpha; reported by Mike Perry.
12779 - Drop begin cells to a hidden service if they come from the middle
12780 of a circuit. Patch from lark.
12781 - When we erroneously receive two EXTEND cells for the same circuit
12782 ID on the same connection, drop the second. Patch from lark.
12783 - Fix a crash that occurs on exit nodes when a nameserver request
12784 timed out. Bugfix on 0.1.2.1-alpha; our CLEAR debugging code had
12785 been suppressing the bug since 0.1.2.10-alpha. Partial fix for
12787 - Do not assume that a stack-allocated character array will be
12788 64-bit aligned on platforms that demand that uint64_t access is
12789 aligned. Possible fix for bug 604.
12790 - Parse dates and IPv4 addresses in a locale- and libc-independent
12791 manner, to avoid platform-dependent behavior on malformed input.
12792 - Build correctly when configured to build outside the main source
12793 path. Patch from Michael Gold.
12794 - We were already rejecting relay begin cells with destination port
12795 of 0. Now also reject extend cells with destination port or address
12796 of 0. Suggested by lark.
12798 o Minor bugfixes (on 0.2.1.x):
12799 - Don't re-extend introduction circuits if we ran out of RELAY_EARLY
12800 cells. Bugfix on 0.2.1.3-alpha. Fixes more of bug 878.
12801 - If we're an exit node, scrub the IP address to which we are exiting
12802 in the logs. Bugfix on 0.2.1.8-alpha.
12805 - On Linux, use the prctl call to re-enable core dumps when the user
12807 - New controller event NEWCONSENSUS that lists the networkstatus
12808 lines for every recommended relay. Now controllers like Torflow
12809 can keep up-to-date on which relays they should be using.
12810 - Update to the "February 26 2009" ip-to-country file.
12813 Changes in version 0.2.0.34 - 2009-02-08
12814 Tor 0.2.0.34 features several more security-related fixes. You should
12815 upgrade, especially if you run an exit relay (remote crash) or a
12816 directory authority (remote infinite loop), or you're on an older
12817 (pre-XP) or not-recently-patched Windows (remote exploit).
12819 This release marks end-of-life for Tor 0.1.2.x. Those Tor versions
12820 have many known flaws, and nobody should be using them. You should
12821 upgrade. If you're using a Linux or BSD and its packages are obsolete,
12822 stop using those packages and upgrade anyway.
12825 - Fix an infinite-loop bug on handling corrupt votes under certain
12826 circumstances. Bugfix on 0.2.0.8-alpha.
12827 - Fix a temporary DoS vulnerability that could be performed by
12828 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12829 - Avoid a potential crash on exit nodes when processing malformed
12830 input. Remote DoS opportunity. Bugfix on 0.2.0.33.
12831 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
12832 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
12835 - Fix compilation on systems where time_t is a 64-bit integer.
12836 Patch from Matthias Drochner.
12837 - Don't consider expiring already-closed client connections. Fixes
12838 bug 893. Bugfix on 0.0.2pre20.
12841 Changes in version 0.2.1.12-alpha - 2009-02-08
12842 Tor 0.2.1.12-alpha features several more security-related fixes. You
12843 should upgrade, especially if you run an exit relay (remote crash) or
12844 a directory authority (remote infinite loop), or you're on an older
12845 (pre-XP) or not-recently-patched Windows (remote exploit). It also
12846 includes a big pile of minor bugfixes and cleanups.
12849 - Fix an infinite-loop bug on handling corrupt votes under certain
12850 circumstances. Bugfix on 0.2.0.8-alpha.
12851 - Fix a temporary DoS vulnerability that could be performed by
12852 a directory mirror. Bugfix on 0.2.0.9-alpha; reported by lark.
12853 - Avoid a potential crash on exit nodes when processing malformed
12854 input. Remote DoS opportunity. Bugfix on 0.2.1.7-alpha.
12857 - Let controllers actually ask for the "clients_seen" event for
12858 getting usage summaries on bridge relays. Bugfix on 0.2.1.10-alpha;
12859 reported by Matt Edman.
12860 - Fix a compile warning on OSX Panther. Fixes bug 913; bugfix against
12862 - Fix a bug in address parsing that was preventing bridges or hidden
12863 service targets from being at IPv6 addresses.
12864 - Solve a bug that kept hardware crypto acceleration from getting
12865 enabled when accounting was turned on. Fixes bug 907. Bugfix on
12867 - Remove a bash-ism from configure.in to build properly on non-Linux
12868 platforms. Bugfix on 0.2.1.1-alpha.
12869 - Fix code so authorities _actually_ send back X-Descriptor-Not-New
12870 headers. Bugfix on 0.2.0.10-alpha.
12871 - Don't consider expiring already-closed client connections. Fixes
12872 bug 893. Bugfix on 0.0.2pre20.
12873 - Fix another interesting corner-case of bug 891 spotted by rovv:
12874 Previously, if two hosts had different amounts of clock drift, and
12875 one of them created a new connection with just the wrong timing,
12876 the other might decide to deprecate the new connection erroneously.
12877 Bugfix on 0.1.1.13-alpha.
12878 - Resolve a very rare crash bug that could occur when the user forced
12879 a nameserver reconfiguration during the middle of a nameserver
12880 probe. Fixes bug 526. Bugfix on 0.1.2.1-alpha.
12881 - Support changing value of ServerDNSRandomizeCase during SIGHUP.
12882 Bugfix on 0.2.1.7-alpha.
12883 - If we're using bridges and our network goes away, be more willing
12884 to forgive our bridges and try again when we get an application
12885 request. Bugfix on 0.2.0.x.
12888 - Support platforms where time_t is 64 bits long. (Congratulations,
12889 NetBSD!) Patch from Matthias Drochner.
12890 - Add a 'getinfo status/clients-seen' controller command, in case
12891 controllers want to hear clients_seen events but connect late.
12894 - Disable GCC's strict alias optimization by default, to avoid the
12895 likelihood of its introducing subtle bugs whenever our code violates
12896 the letter of C99's alias rules.
12899 Changes in version 0.2.0.33 - 2009-01-21
12900 Tor 0.2.0.33 fixes a variety of bugs that were making relays less
12901 useful to users. It also finally fixes a bug where a relay or client
12902 that's been off for many days would take a long time to bootstrap.
12904 This update also fixes an important security-related bug reported by
12905 Ilja van Sprundel. You should upgrade. (We'll send out more details
12906 about the bug once people have had some time to upgrade.)
12909 - Fix a heap-corruption bug that may be remotely triggerable on
12910 some platforms. Reported by Ilja van Sprundel.
12913 - When a stream at an exit relay is in state "resolving" or
12914 "connecting" and it receives an "end" relay cell, the exit relay
12915 would silently ignore the end cell and not close the stream. If
12916 the client never closes the circuit, then the exit relay never
12917 closes the TCP connection. Bug introduced in Tor 0.1.2.1-alpha;
12918 reported by "wood".
12919 - When sending CREATED cells back for a given circuit, use a 64-bit
12920 connection ID to find the right connection, rather than an addr:port
12921 combination. Now that we can have multiple OR connections between
12922 the same ORs, it is no longer possible to use addr:port to uniquely
12923 identify a connection.
12924 - Bridge relays that had DirPort set to 0 would stop fetching
12925 descriptors shortly after startup, and then briefly resume
12926 after a new bandwidth test and/or after publishing a new bridge
12927 descriptor. Bridge users that try to bootstrap from them would
12928 get a recent networkstatus but would get descriptors from up to
12929 18 hours earlier, meaning most of the descriptors were obsolete
12930 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
12931 - Prevent bridge relays from serving their 'extrainfo' document
12932 to anybody who asks, now that extrainfo docs include potentially
12933 sensitive aggregated client geoip summaries. Bugfix on
12935 - If the cached networkstatus consensus is more than five days old,
12936 discard it rather than trying to use it. In theory it could be
12937 useful because it lists alternate directory mirrors, but in practice
12938 it just means we spend many minutes trying directory mirrors that
12939 are long gone from the network. Also discard router descriptors as
12940 we load them if they are more than five days old, since the onion
12941 key is probably wrong by now. Bugfix on 0.2.0.x. Fixes bug 887.
12944 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
12945 could make gcc generate non-functional binary search code. Bugfix
12947 - Build correctly on platforms without socklen_t.
12948 - Compile without warnings on solaris.
12949 - Avoid potential crash on internal error during signature collection.
12950 Fixes bug 864. Patch from rovv.
12951 - Correct handling of possible malformed authority signing key
12952 certificates with internal signature types. Fixes bug 880.
12953 Bugfix on 0.2.0.3-alpha.
12954 - Fix a hard-to-trigger resource leak when logging credential status.
12956 - When we can't initialize DNS because the network is down, do not
12957 automatically stop Tor from starting. Instead, we retry failed
12958 dns_init() every 10 minutes, and change the exit policy to reject
12959 *:* until one succeeds. Fixes bug 691.
12960 - Use 64 bits instead of 32 bits for connection identifiers used with
12961 the controller protocol, to greatly reduce risk of identifier reuse.
12962 - When we're choosing an exit node for a circuit, and we have
12963 no pending streams, choose a good general exit rather than one that
12964 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
12965 - Fix another case of assuming, when a specific exit is requested,
12966 that we know more than the user about what hosts it allows.
12967 Fixes one case of bug 752. Patch from rovv.
12968 - Clip the MaxCircuitDirtiness config option to a minimum of 10
12969 seconds. Warn the user if lower values are given in the
12970 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
12971 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
12972 user if lower values are given in the configuration. Bugfix on
12973 0.1.1.17-rc. Patch by Sebastian.
12974 - Fix a memory leak when we decline to add a v2 rendezvous descriptor to
12975 the cache because we already had a v0 descriptor with the same ID.
12976 Bugfix on 0.2.0.18-alpha.
12977 - Fix a race condition when freeing keys shared between main thread
12978 and CPU workers that could result in a memory leak. Bugfix on
12979 0.1.0.1-rc. Fixes bug 889.
12980 - Send a valid END cell back when a client tries to connect to a
12981 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
12982 840. Patch from rovv.
12983 - Check which hops rendezvous stream cells are associated with to
12984 prevent possible guess-the-streamid injection attacks from
12985 intermediate hops. Fixes another case of bug 446. Based on patch
12987 - If a broken client asks a non-exit router to connect somewhere,
12988 do not even do the DNS lookup before rejecting the connection.
12989 Fixes another case of bug 619. Patch from rovv.
12990 - When a relay gets a create cell it can't decrypt (e.g. because it's
12991 using the wrong onion key), we were dropping it and letting the
12992 client time out. Now actually answer with a destroy cell. Fixes
12993 bug 904. Bugfix on 0.0.2pre8.
12995 o Minor bugfixes (hidden services):
12996 - Do not throw away existing introduction points on SIGHUP. Bugfix on
12997 0.0.6pre1. Patch by Karsten. Fixes bug 874.
13000 - Report the case where all signatures in a detached set are rejected
13001 differently than the case where there is an error handling the
13003 - When we realize that another process has modified our cached
13004 descriptors, print out a more useful error message rather than
13005 triggering an assertion. Fixes bug 885. Patch from Karsten.
13006 - Implement the 0x20 hack to better resist DNS poisoning: set the
13007 case on outgoing DNS requests randomly, and reject responses that do
13008 not match the case correctly. This logic can be disabled with the
13009 ServerDNSRamdomizeCase setting, if you are using one of the 0.3%
13010 of servers that do not reliably preserve case in replies. See
13011 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13013 - Check DNS replies for more matching fields to better resist DNS
13015 - Never use OpenSSL compression: it wastes RAM and CPU trying to
13016 compress cells, which are basically all encrypted, compressed, or
13020 Changes in version 0.2.1.11-alpha - 2009-01-20
13021 Tor 0.2.1.11-alpha finishes fixing the "if your Tor is off for a
13022 week it will take a long time to bootstrap again" bug. It also fixes
13023 an important security-related bug reported by Ilja van Sprundel. You
13024 should upgrade. (We'll send out more details about the bug once people
13025 have had some time to upgrade.)
13028 - Fix a heap-corruption bug that may be remotely triggerable on
13029 some platforms. Reported by Ilja van Sprundel.
13032 - Discard router descriptors as we load them if they are more than
13033 five days old. Otherwise if Tor is off for a long time and then
13034 starts with cached descriptors, it will try to use the onion
13035 keys in those obsolete descriptors when building circuits. Bugfix
13036 on 0.2.0.x. Fixes bug 887.
13039 - Try to make sure that the version of Libevent we're running with
13040 is binary-compatible with the one we built with. May address bug
13042 - Make setting ServerDNSRandomizeCase to 0 actually work. Bugfix
13043 for bug 905. Bugfix on 0.2.1.7-alpha.
13044 - Add a new --enable-local-appdata configuration switch to change
13045 the default location of the datadir on win32 from APPDATA to
13046 LOCAL_APPDATA. In the future, we should migrate to LOCAL_APPDATA
13047 entirely. Patch from coderman.
13050 - Make outbound DNS packets respect the OutboundBindAddress setting.
13051 Fixes the bug part of bug 798. Bugfix on 0.1.2.2-alpha.
13052 - When our circuit fails at the first hop (e.g. we get a destroy
13053 cell back), avoid using that OR connection anymore, and also
13054 tell all the one-hop directory requests waiting for it that they
13055 should fail. Bugfix on 0.2.1.3-alpha.
13056 - In the torify(1) manpage, mention that tsocks will leak your
13060 Changes in version 0.2.1.10-alpha - 2009-01-06
13061 Tor 0.2.1.10-alpha fixes two major bugs in bridge relays (one that
13062 would make the bridge relay not so useful if it had DirPort set to 0,
13063 and one that could let an attacker learn a little bit of information
13064 about the bridge's users), and a bug that would cause your Tor relay
13065 to ignore a circuit create request it can't decrypt (rather than reply
13066 with an error). It also fixes a wide variety of other bugs.
13069 - If the cached networkstatus consensus is more than five days old,
13070 discard it rather than trying to use it. In theory it could
13071 be useful because it lists alternate directory mirrors, but in
13072 practice it just means we spend many minutes trying directory
13073 mirrors that are long gone from the network. Helps bug 887 a bit;
13075 - Bridge relays that had DirPort set to 0 would stop fetching
13076 descriptors shortly after startup, and then briefly resume
13077 after a new bandwidth test and/or after publishing a new bridge
13078 descriptor. Bridge users that try to bootstrap from them would
13079 get a recent networkstatus but would get descriptors from up to
13080 18 hours earlier, meaning most of the descriptors were obsolete
13081 already. Reported by Tas; bugfix on 0.2.0.13-alpha.
13082 - Prevent bridge relays from serving their 'extrainfo' document
13083 to anybody who asks, now that extrainfo docs include potentially
13084 sensitive aggregated client geoip summaries. Bugfix on
13088 - New controller event "clients_seen" to report a geoip-based summary
13089 of which countries we've seen clients from recently. Now controllers
13090 like Vidalia can show bridge operators that they're actually making
13092 - Build correctly against versions of OpenSSL 0.9.8 or later built
13093 without support for deprecated functions.
13094 - Update to the "December 19 2008" ip-to-country file.
13096 o Minor bugfixes (on 0.2.0.x):
13097 - Authorities now vote for the Stable flag for any router whose
13098 weighted MTBF is at least 5 days, regardless of the mean MTBF.
13099 - Do not remove routers as too old if we do not have any consensus
13100 document. Bugfix on 0.2.0.7-alpha.
13101 - Do not accept incomplete ipv4 addresses (like 192.168.0) as valid.
13102 Spec conformance issue. Bugfix on Tor 0.0.2pre27.
13103 - When an exit relay resolves a stream address to a local IP address,
13104 do not just keep retrying that same exit relay over and
13105 over. Instead, just close the stream. Addresses bug 872. Bugfix
13106 on 0.2.0.32. Patch from rovv.
13107 - If a hidden service sends us an END cell, do not consider
13108 retrying the connection; just close it. Patch from rovv.
13109 - When we made bridge authorities stop serving bridge descriptors over
13110 unencrypted links, we also broke DirPort reachability testing for
13111 bridges. So bridges with a non-zero DirPort were printing spurious
13112 warns to their logs. Bugfix on 0.2.0.16-alpha. Fixes bug 709.
13113 - When a relay gets a create cell it can't decrypt (e.g. because it's
13114 using the wrong onion key), we were dropping it and letting the
13115 client time out. Now actually answer with a destroy cell. Fixes
13116 bug 904. Bugfix on 0.0.2pre8.
13117 - Squeeze 2-5% out of client performance (according to oprofile) by
13118 improving the implementation of some policy-manipulation functions.
13120 o Minor bugfixes (on 0.2.1.x):
13121 - Make get_interface_address() function work properly again; stop
13122 guessing the wrong parts of our address as our address.
13123 - Do not cannibalize a circuit if we're out of RELAY_EARLY cells to
13124 send on that circuit. Otherwise we might violate the proposal-110
13125 limit. Bugfix on 0.2.1.3-alpha. Partial fix for bug 878. Diagnosis
13127 - When we're sending non-EXTEND cells to the first hop in a circuit,
13128 for example to use an encrypted directory connection, we don't need
13129 to use RELAY_EARLY cells: the first hop knows what kind of cell
13130 it is, and nobody else can even see the cell type. Conserving
13131 RELAY_EARLY cells makes it easier to cannibalize circuits like
13133 - Stop logging nameserver addresses in reverse order.
13134 - If we are retrying a directory download slowly over and over, do
13135 not automatically give up after the 254th failure. Bugfix on
13137 - Resume reporting accurate "stream end" reasons to the local control
13138 port. They were lost in the changes for Proposal 148. Bugfix on
13141 o Deprecated and removed features:
13142 - The old "tor --version --version" command, which would print out
13143 the subversion "Id" of most of the source files, is now removed. It
13144 turned out to be less useful than we'd expected, and harder to
13147 o Code simplifications and refactoring:
13148 - Change our header file guard macros to be less likely to conflict
13149 with system headers. Adam Langley noticed that we were conflicting
13150 with log.h on Android.
13151 - Tool-assisted documentation cleanup. Nearly every function or
13152 static variable in Tor should have its own documentation now.
13155 Changes in version 0.2.1.9-alpha - 2008-12-25
13156 Tor 0.2.1.9-alpha fixes many more bugs, some of them security-related.
13158 o New directory authorities:
13159 - gabelmoo (the authority run by Karsten Loesing) now has a new
13163 - Never use a connection with a mismatched address to extend a
13164 circuit, unless that connection is canonical. A canonical
13165 connection is one whose address is authenticated by the router's
13166 identity key, either in a NETINFO cell or in a router descriptor.
13167 - Avoid a possible memory corruption bug when receiving hidden service
13168 descriptors. Bugfix on 0.2.1.6-alpha.
13171 - Fix a logic error that would automatically reject all but the first
13172 configured DNS server. Bugfix on 0.2.1.5-alpha. Possible fix for
13173 part of bug 813/868. Bug spotted by coderman.
13174 - When a stream at an exit relay is in state "resolving" or
13175 "connecting" and it receives an "end" relay cell, the exit relay
13176 would silently ignore the end cell and not close the stream. If
13177 the client never closes the circuit, then the exit relay never
13178 closes the TCP connection. Bug introduced in 0.1.2.1-alpha;
13179 reported by "wood".
13180 - When we can't initialize DNS because the network is down, do not
13181 automatically stop Tor from starting. Instead, retry failed
13182 dns_init() every 10 minutes, and change the exit policy to reject
13183 *:* until one succeeds. Fixes bug 691.
13186 - Give a better error message when an overzealous init script says
13187 "sudo -u username tor --user username". Makes Bug 882 easier for
13189 - When a directory authority gives us a new guess for our IP address,
13190 log which authority we used. Hopefully this will help us debug
13191 the recent complaints about bad IP address guesses.
13192 - Detect svn revision properly when we're using git-svn.
13193 - Try not to open more than one descriptor-downloading connection
13194 to an authority at once. This should reduce load on directory
13195 authorities. Fixes bug 366.
13196 - Add cross-certification to newly generated certificates, so that
13197 a signing key is enough information to look up a certificate.
13198 Partial implementation of proposal 157.
13199 - Start serving certificates by <identity digest, signing key digest>
13200 pairs. Partial implementation of proposal 157.
13201 - Clients now never report any stream end reason except 'MISC'.
13202 Implements proposal 148.
13203 - On platforms with a maximum syslog string length, truncate syslog
13204 messages to that length ourselves, rather than relying on the
13205 system to do it for us.
13206 - Optimize out calls to time(NULL) that occur for every IO operation,
13207 or for every cell. On systems where time() is a slow syscall,
13208 this fix will be slightly helpful.
13209 - Exit servers can now answer resolve requests for ip6.arpa addresses.
13210 - When we download a descriptor that we then immediately (as
13211 a directory authority) reject, do not retry downloading it right
13212 away. Should save some bandwidth on authorities. Fix for bug
13213 888. Patch by Sebastian Hahn.
13214 - When a download gets us zero good descriptors, do not notify
13215 Tor that new directory information has arrived.
13216 - Avoid some nasty corner cases in the logic for marking connections
13217 as too old or obsolete or noncanonical for circuits. Partial
13220 o Minor features (controller):
13221 - New CONSENSUS_ARRIVED event to note when a new consensus has
13222 been fetched and validated.
13223 - When we realize that another process has modified our cached
13224 descriptors file, print out a more useful error message rather
13225 than triggering an assertion. Fixes bug 885. Patch from Karsten.
13226 - Add an internal-use-only __ReloadTorrcOnSIGHUP option for
13227 controllers to prevent SIGHUP from reloading the
13228 configuration. Fixes bug 856.
13231 - Resume using the correct "REASON=" stream when telling the
13232 controller why we closed a stream. Bugfix in 0.2.1.1-alpha.
13233 - When a canonical connection appears later in our internal list
13234 than a noncanonical one for a given OR ID, always use the
13235 canonical one. Bugfix on 0.2.0.12-alpha. Fixes bug 805.
13237 - Clip the MaxCircuitDirtiness config option to a minimum of 10
13238 seconds. Warn the user if lower values are given in the
13239 configuration. Bugfix on 0.1.0.1-rc. Patch by Sebastian.
13240 - Clip the CircuitBuildTimeout to a minimum of 30 seconds. Warn the
13241 user if lower values are given in the configuration. Bugfix on
13242 0.1.1.17-rc. Patch by Sebastian.
13243 - Fix a race condition when freeing keys shared between main thread
13244 and CPU workers that could result in a memory leak. Bugfix on
13245 0.1.0.1-rc. Fixes bug 889.
13247 o Minor bugfixes (hidden services):
13248 - Do not throw away existing introduction points on SIGHUP (bugfix on
13249 0.0.6pre1); also, do not stall hidden services because we're
13250 throwing away introduction points; bugfix on 0.2.1.7-alpha. Spotted
13251 by John Brooks. Patch by Karsten. Fixes bug 874.
13252 - Fix a memory leak when we decline to add a v2 rendezvous
13253 descriptor to the cache because we already had a v0 descriptor
13254 with the same ID. Bugfix on 0.2.0.18-alpha.
13256 o Deprecated and removed features:
13257 - RedirectExits has been removed. It was deprecated since
13259 - Finally remove deprecated "EXTENDED_FORMAT" controller feature. It
13260 has been called EXTENDED_EVENTS since 0.1.2.4-alpha.
13261 - Cell pools are now always enabled; --disable-cell-pools is ignored.
13263 o Code simplifications and refactoring:
13264 - Rename the confusing or_is_obsolete field to the more appropriate
13265 is_bad_for_new_circs, and move it to or_connection_t where it
13267 - Move edge-only flags from connection_t to edge_connection_t: not
13268 only is this better coding, but on machines of plausible alignment,
13269 it should save 4-8 bytes per connection_t. "Every little bit helps."
13270 - Rename ServerDNSAllowBrokenResolvConf to ServerDNSAllowBrokenConfig
13271 for consistency; keep old option working for backward compatibility.
13272 - Simplify the code for finding connections to use for a circuit.
13275 Changes in version 0.2.1.8-alpha - 2008-12-08
13276 Tor 0.2.1.8-alpha fixes some crash bugs in earlier alpha releases,
13277 builds better on unusual platforms like Solaris and old OS X, and
13278 fixes a variety of other issues.
13281 - New DirPortFrontPage option that takes an html file and publishes
13282 it as "/" on the DirPort. Now relay operators can provide a
13283 disclaimer without needing to set up a separate webserver. There's
13284 a sample disclaimer in contrib/tor-exit-notice.html.
13287 - When the client is choosing entry guards, now it selects at most
13288 one guard from a given relay family. Otherwise we could end up with
13289 all of our entry points into the network run by the same operator.
13290 Suggested by Camilo Viecco. Fix on 0.1.1.11-alpha.
13293 - Fix a DOS opportunity during the voting signature collection process
13294 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13295 - Fix a possible segfault when establishing an exit connection. Bugfix
13299 - Get file locking working on win32. Bugfix on 0.2.1.6-alpha. Fixes
13301 - Made Tor a little less aggressive about deleting expired
13302 certificates. Partial fix for bug 854.
13303 - Stop doing unaligned memory access that generated bus errors on
13304 sparc64. Bugfix on 0.2.0.10-alpha. Fix for bug 862.
13305 - Fix a crash bug when changing EntryNodes from the controller. Bugfix
13306 on 0.2.1.6-alpha. Fix for bug 867. Patched by Sebastian.
13307 - Make USR2 log-level switch take effect immediately. Bugfix on
13309 - If one win32 nameserver fails to get added, continue adding the
13310 rest, and don't automatically fail.
13311 - Use fcntl() for locking when flock() is not available. Should fix
13312 compilation on Solaris. Should fix Bug 873. Bugfix on 0.2.1.6-alpha.
13313 - Do not mark smartlist_bsearch_idx() function as ATTR_PURE. This bug
13314 could make gcc generate non-functional binary search code. Bugfix
13316 - Build correctly on platforms without socklen_t.
13317 - Avoid potential crash on internal error during signature collection.
13318 Fixes bug 864. Patch from rovv.
13319 - Do not use C's stdio library for writing to log files. This will
13320 improve logging performance by a minute amount, and will stop
13321 leaking fds when our disk is full. Fixes bug 861.
13322 - Stop erroneous use of O_APPEND in cases where we did not in fact
13323 want to re-seek to the end of a file before every last write().
13324 - Correct handling of possible malformed authority signing key
13325 certificates with internal signature types. Fixes bug 880. Bugfix
13327 - Fix a hard-to-trigger resource leak when logging credential status.
13331 - Directory mirrors no longer fetch the v1 directory or
13332 running-routers files. They are obsolete, and nobody asks for them
13333 anymore. This is the first step to making v1 authorities obsolete.
13335 o Minor features (controller):
13336 - Return circuit purposes in response to GETINFO circuit-status. Fixes
13340 Changes in version 0.2.0.32 - 2008-11-20
13341 Tor 0.2.0.32 fixes a major security problem in Debian and Ubuntu
13342 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13343 a smaller security flaw that might allow an attacker to access local
13344 services, further improves hidden service performance, and fixes a
13345 variety of other issues.
13348 - The "User" and "Group" config options did not clear the
13349 supplementary group entries for the Tor process. The "User" option
13350 is now more robust, and we now set the groups to the specified
13351 user's primary group. The "Group" option is now ignored. For more
13352 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13353 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13354 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848 and 857.
13355 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13356 consistently obeyed: if an exit relay refuses a stream because its
13357 exit policy doesn't allow it, we would remember what IP address
13358 the relay said the destination address resolves to, even if it's
13359 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13362 - Fix a DOS opportunity during the voting signature collection process
13363 at directory authorities. Spotted by rovv. Bugfix on 0.2.0.x.
13365 o Major bugfixes (hidden services):
13366 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13367 we were failing the whole hidden service request when the v0
13368 descriptor fetch fails, even if the v2 fetch is still pending and
13369 might succeed. Similarly, if the last v2 fetch fails, we were
13370 failing the whole hidden service request even if a v0 fetch is
13371 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13372 - When extending a circuit to a hidden service directory to upload a
13373 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13374 requests failed, because the router descriptor has not been
13375 downloaded yet. In these cases, do not attempt to upload the
13376 rendezvous descriptor, but wait until the router descriptor is
13377 downloaded and retry. Likewise, do not attempt to fetch a rendezvous
13378 descriptor from a hidden service directory for which the router
13379 descriptor has not yet been downloaded. Fixes bug 767. Bugfix
13383 - Fix several infrequent memory leaks spotted by Coverity.
13384 - When testing for libevent functions, set the LDFLAGS variable
13385 correctly. Found by Riastradh.
13386 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13387 bootstrapping with tunneled directory connections. Bugfix on
13388 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13389 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13390 and we know that server B rejects most-but-not all connections to
13391 port 80, we would previously reject the connection. Now, we assume
13392 the user knows what they were asking for. Fixes bug 752. Bugfix
13393 on 0.0.9rc5. Diagnosed by BarkerJr.
13394 - If we overrun our per-second write limits a little, count this as
13395 having used up our write allocation for the second, and choke
13396 outgoing directory writes. Previously, we had only counted this when
13397 we had met our limits precisely. Fixes bug 824. Patch from by rovv.
13398 Bugfix on 0.2.0.x (??).
13399 - Remove the old v2 directory authority 'lefkada' from the default
13400 list. It has been gone for many months.
13401 - Stop doing unaligned memory access that generated bus errors on
13402 sparc64. Bugfix on 0.2.0.10-alpha. Fixes bug 862.
13403 - Make USR2 log-level switch take effect immediately. Bugfix on
13406 o Minor bugfixes (controller):
13407 - Make DNS resolved events into "CLOSED", not "FAILED". Bugfix on
13408 0.1.2.5-alpha. Fix by Robert Hogan. Resolves bug 807.
13411 Changes in version 0.2.1.7-alpha - 2008-11-08
13412 Tor 0.2.1.7-alpha fixes a major security problem in Debian and Ubuntu
13413 packages (and maybe other packages) noticed by Theo de Raadt, fixes
13414 a smaller security flaw that might allow an attacker to access local
13415 services, adds better defense against DNS poisoning attacks on exit
13416 relays, further improves hidden service performance, and fixes a
13417 variety of other issues.
13420 - The "ClientDNSRejectInternalAddresses" config option wasn't being
13421 consistently obeyed: if an exit relay refuses a stream because its
13422 exit policy doesn't allow it, we would remember what IP address
13423 the relay said the destination address resolves to, even if it's
13424 an internal IP address. Bugfix on 0.2.0.7-alpha; patch by rovv.
13425 - The "User" and "Group" config options did not clear the
13426 supplementary group entries for the Tor process. The "User" option
13427 is now more robust, and we now set the groups to the specified
13428 user's primary group. The "Group" option is now ignored. For more
13429 detailed logging on credential switching, set CREDENTIAL_LOG_LEVEL
13430 in common/compat.c to LOG_NOTICE or higher. Patch by Jacob Appelbaum
13431 and Steven Murdoch. Bugfix on 0.0.2pre14. Fixes bug 848.
13432 - Do not use or believe expired v3 authority certificates. Patch
13433 from Karsten. Bugfix in 0.2.0.x. Fixes bug 851.
13436 - Now NodeFamily and MyFamily config options allow spaces in
13437 identity fingerprints, so it's easier to paste them in.
13438 Suggested by Lucky Green.
13439 - Implement the 0x20 hack to better resist DNS poisoning: set the
13440 case on outgoing DNS requests randomly, and reject responses that do
13441 not match the case correctly. This logic can be disabled with the
13442 ServerDNSRandomizeCase setting, if you are using one of the 0.3%
13443 of servers that do not reliably preserve case in replies. See
13444 "Increased DNS Forgery Resistance through 0x20-Bit Encoding"
13446 - Preserve case in replies to DNSPort requests in order to support
13447 the 0x20 hack for resisting DNS poisoning attacks.
13449 o Hidden service performance improvements:
13450 - When the client launches an introduction circuit, retry with a
13451 new circuit after 30 seconds rather than 60 seconds.
13452 - Launch a second client-side introduction circuit in parallel
13453 after a delay of 15 seconds (based on work by Christian Wilms).
13454 - Hidden services start out building five intro circuits rather
13455 than three, and when the first three finish they publish a service
13456 descriptor using those. Now we publish our service descriptor much
13457 faster after restart.
13460 - Minor fix in the warning messages when you're having problems
13461 bootstrapping; also, be more forgiving of bootstrap problems when
13462 we're still making incremental progress on a given bootstrap phase.
13463 - When we're choosing an exit node for a circuit, and we have
13464 no pending streams, choose a good general exit rather than one that
13465 supports "all the pending streams". Bugfix on 0.1.1.x. Fix by rovv.
13466 - Send a valid END cell back when a client tries to connect to a
13467 nonexistent hidden service port. Bugfix on 0.1.2.15. Fixes bug
13468 840. Patch from rovv.
13469 - If a broken client asks a non-exit router to connect somewhere,
13470 do not even do the DNS lookup before rejecting the connection.
13471 Fixes another case of bug 619. Patch from rovv.
13472 - Fix another case of assuming, when a specific exit is requested,
13473 that we know more than the user about what hosts it allows.
13474 Fixes another case of bug 752. Patch from rovv.
13475 - Check which hops rendezvous stream cells are associated with to
13476 prevent possible guess-the-streamid injection attacks from
13477 intermediate hops. Fixes another case of bug 446. Based on patch
13479 - Avoid using a negative right-shift when comparing 32-bit
13480 addresses. Possible fix for bug 845 and bug 811.
13481 - Make the assert_circuit_ok() function work correctly on circuits that
13482 have already been marked for close.
13483 - Fix read-off-the-end-of-string error in unit tests when decoding
13484 introduction points.
13485 - Fix uninitialized size field for memory area allocation: may improve
13486 memory performance during directory parsing.
13487 - Treat duplicate certificate fetches as failures, so that we do
13488 not try to re-fetch an expired certificate over and over and over.
13489 - Do not say we're fetching a certificate when we'll in fact skip it
13490 because of a pending download.
13493 Changes in version 0.2.1.6-alpha - 2008-09-30
13494 Tor 0.2.1.6-alpha further improves performance and robustness of
13495 hidden services, starts work on supporting per-country relay selection,
13496 and fixes a variety of smaller issues.
13499 - Implement proposal 121: make it possible to build hidden services
13500 that only certain clients are allowed to connect to. This is
13501 enforced at several points, so that unauthorized clients are unable
13502 to send INTRODUCE cells to the service, or even (depending on the
13503 type of authentication) to learn introduction points. This feature
13504 raises the bar for certain kinds of active attacks against hidden
13505 services. Code by Karsten Loesing.
13506 - Relays now store and serve v2 hidden service descriptors by default,
13507 i.e., the new default value for HidServDirectoryV2 is 1. This is
13508 the last step in proposal 114, which aims to make hidden service
13509 lookups more reliable.
13510 - Start work to allow node restrictions to include country codes. The
13511 syntax to exclude nodes in a country with country code XX is
13512 "ExcludeNodes {XX}". Patch from Robert Hogan. It still needs some
13513 refinement to decide what config options should take priority if
13514 you ask to both use a particular node and exclude it.
13515 - Allow ExitNodes list to include IP ranges and country codes, just
13516 like the Exclude*Nodes lists. Patch from Robert Hogan.
13519 - Fix a bug when parsing ports in tor_addr_port_parse() that caused
13520 Tor to fail to start if you had it configured to use a bridge
13521 relay. Fixes bug 809. Bugfix on 0.2.1.5-alpha.
13522 - When extending a circuit to a hidden service directory to upload a
13523 rendezvous descriptor using a BEGIN_DIR cell, almost 1/6 of all
13524 requests failed, because the router descriptor had not been
13525 downloaded yet. In these cases, we now wait until the router
13526 descriptor is downloaded, and then retry. Likewise, clients
13527 now skip over a hidden service directory if they don't yet have
13528 its router descriptor, rather than futilely requesting it and
13529 putting mysterious complaints in the logs. Fixes bug 767. Bugfix
13531 - When fetching v0 and v2 rendezvous service descriptors in parallel,
13532 we were failing the whole hidden service request when the v0
13533 descriptor fetch fails, even if the v2 fetch is still pending and
13534 might succeed. Similarly, if the last v2 fetch fails, we were
13535 failing the whole hidden service request even if a v0 fetch is
13536 still pending. Fixes bug 814. Bugfix on 0.2.0.10-alpha.
13537 - DNS replies need to have names matching their requests, but
13538 these names should be in the questions section, not necessarily
13539 in the answers section. Fixes bug 823. Bugfix on 0.2.1.5-alpha.
13542 - Update to the "September 1 2008" ip-to-country file.
13543 - Allow ports 465 and 587 in the default exit policy again. We had
13544 rejected them in 0.1.0.15, because back in 2005 they were commonly
13545 misconfigured and ended up as spam targets. We hear they are better
13546 locked down these days.
13547 - Use a lockfile to make sure that two Tor processes are not
13548 simultaneously running with the same datadir.
13549 - Serve the latest v3 networkstatus consensus via the control
13550 port. Use "getinfo dir/status-vote/current/consensus" to fetch it.
13551 - Better logging about stability/reliability calculations on directory
13553 - Drop the requirement to have an open dir port for storing and
13554 serving v2 hidden service descriptors.
13555 - Directory authorities now serve a /tor/dbg-stability.txt URL to
13556 help debug WFU and MTBF calculations.
13557 - Implement most of Proposal 152: allow specialized servers to permit
13558 single-hop circuits, and clients to use those servers to build
13559 single-hop circuits when using a specialized controller. Patch
13560 from Josh Albrecht. Resolves feature request 768.
13561 - Add a -p option to tor-resolve for specifying the SOCKS port: some
13562 people find host:port too confusing.
13563 - Make TrackHostExit mappings expire a while after their last use, not
13564 after their creation. Patch from Robert Hogan.
13565 - Provide circuit purposes along with circuit events to the controller.
13568 - Fix compile on OpenBSD 4.4-current. Bugfix on 0.2.1.5-alpha.
13570 - Fixed some memory leaks -- some quite frequent, some almost
13571 impossible to trigger -- based on results from Coverity.
13572 - When testing for libevent functions, set the LDFLAGS variable
13573 correctly. Found by Riastradh.
13574 - Fix an assertion bug in parsing policy-related options; possible fix
13576 - Catch and report a few more bootstrapping failure cases when Tor
13577 fails to establish a TCP connection. Cleanup on 0.2.1.x.
13578 - Avoid a bug where the FastFirstHopPK 0 option would keep Tor from
13579 bootstrapping with tunneled directory connections. Bugfix on
13580 0.1.2.5-alpha. Fixes bug 797. Found by Erwin Lam.
13581 - When asked to connect to A.B.exit:80, if we don't know the IP for A
13582 and we know that server B rejects most-but-not all connections to
13583 port 80, we would previously reject the connection. Now, we assume
13584 the user knows what they were asking for. Fixes bug 752. Bugfix
13585 on 0.0.9rc5. Diagnosed by BarkerJr.
13586 - If we are not using BEGIN_DIR cells, don't attempt to contact hidden
13587 service directories if they have no advertised dir port. Bugfix
13589 - If we overrun our per-second write limits a little, count this as
13590 having used up our write allocation for the second, and choke
13591 outgoing directory writes. Previously, we had only counted this when
13592 we had met our limits precisely. Fixes bug 824. Patch by rovv.
13593 Bugfix on 0.2.0.x (??).
13594 - Avoid a "0 divided by 0" calculation when calculating router uptime
13595 at directory authorities. Bugfix on 0.2.0.8-alpha.
13596 - Make DNS resolved controller events into "CLOSED", not
13597 "FAILED". Bugfix on 0.1.2.5-alpha. Fix by Robert Hogan. Resolves
13599 - Fix a bug where an unreachable relay would establish enough
13600 reachability testing circuits to do a bandwidth test -- if
13601 we already have a connection to the middle hop of the testing
13602 circuit, then it could establish the last hop by using the existing
13603 connection. Bugfix on 0.1.2.2-alpha, exposed when we made testing
13604 circuits no longer use entry guards in 0.2.1.3-alpha.
13605 - If we have correct permissions on $datadir, we complain to stdout
13606 and fail to start. But dangerous permissions on
13607 $datadir/cached-status/ would cause us to open a log and complain
13608 there. Now complain to stdout and fail to start in both cases. Fixes
13609 bug 820, reported by seeess.
13610 - Remove the old v2 directory authority 'lefkada' from the default
13611 list. It has been gone for many months.
13613 o Code simplifications and refactoring:
13614 - Revise the connection_new functions so that a more typesafe variant
13615 exists. This will work better with Coverity, and let us find any
13616 actual mistakes we're making here.
13617 - Refactor unit testing logic so that dmalloc can be used sensibly
13618 with unit tests to check for memory leaks.
13619 - Move all hidden-service related fields from connection and circuit
13620 structure to substructures: this way they won't eat so much memory.
13623 Changes in version 0.2.0.31 - 2008-09-03
13624 Tor 0.2.0.31 addresses two potential anonymity issues, starts to fix
13625 a big bug we're seeing where in rare cases traffic from one Tor stream
13626 gets mixed into another stream, and fixes a variety of smaller issues.
13629 - Make sure that two circuits can never exist on the same connection
13630 with the same circuit ID, even if one is marked for close. This
13631 is conceivably a bugfix for bug 779. Bugfix on 0.1.0.4-rc.
13632 - Relays now reject risky extend cells: if the extend cell includes
13633 a digest of all zeroes, or asks to extend back to the relay that
13634 sent the extend cell, tear down the circuit. Ideas suggested
13636 - If not enough of our entry guards are available so we add a new
13637 one, we might use the new one even if it overlapped with the
13638 current circuit's exit relay (or its family). Anonymity bugfix
13639 pointed out by rovv.
13642 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13643 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13644 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13645 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13646 - Pick size of default geoip filename string correctly on windows.
13647 Fixes bug 806. Bugfix on 0.2.0.30.
13648 - Make the autoconf script accept the obsolete --with-ssl-dir
13649 option as an alias for the actually-working --with-openssl-dir
13650 option. Fix the help documentation to recommend --with-openssl-dir.
13651 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13652 - When using the TransPort option on OpenBSD, and using the User
13653 option to change UID and drop privileges, make sure to open
13654 /dev/pf before dropping privileges. Fixes bug 782. Patch from
13655 Christopher Davis. Bugfix on 0.1.2.1-alpha.
13656 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13657 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13658 on the client side when connecting to a hidden service. Bugfix
13659 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13660 - When closing an application-side connection because its circuit is
13661 getting torn down, generate the stream event correctly. Bugfix on
13662 0.1.2.x. Anonymous patch.
13665 Changes in version 0.2.1.5-alpha - 2008-08-31
13666 Tor 0.2.1.5-alpha moves us closer to handling IPv6 destinations, puts
13667 in a lot of the infrastructure for adding authorization to hidden
13668 services, lays the groundwork for having clients read their load
13669 balancing information out of the networkstatus consensus rather than
13670 the individual router descriptors, addresses two potential anonymity
13671 issues, and fixes a variety of smaller issues.
13674 - Convert many internal address representations to optionally hold
13676 - Generate and accept IPv6 addresses in many protocol elements.
13677 - Make resolver code handle nameservers located at ipv6 addresses.
13678 - Begin implementation of proposal 121 ("Client authorization for
13679 hidden services"): configure hidden services with client
13680 authorization, publish descriptors for them, and configure
13681 authorization data for hidden services at clients. The next
13682 step is to actually access hidden services that perform client
13684 - More progress toward proposal 141: Network status consensus
13685 documents and votes now contain bandwidth information for each
13686 router and a summary of that router's exit policy. Eventually this
13687 will be used by clients so that they do not have to download every
13688 known descriptor before building circuits.
13690 o Major bugfixes (on 0.2.0.x and before):
13691 - When sending CREATED cells back for a given circuit, use a 64-bit
13692 connection ID to find the right connection, rather than an addr:port
13693 combination. Now that we can have multiple OR connections between
13694 the same ORs, it is no longer possible to use addr:port to uniquely
13695 identify a connection.
13696 - Relays now reject risky extend cells: if the extend cell includes
13697 a digest of all zeroes, or asks to extend back to the relay that
13698 sent the extend cell, tear down the circuit. Ideas suggested
13700 - If not enough of our entry guards are available so we add a new
13701 one, we might use the new one even if it overlapped with the
13702 current circuit's exit relay (or its family). Anonymity bugfix
13703 pointed out by rovv.
13706 - Recover 3-7 bytes that were wasted per memory chunk. Fixes bug
13707 794; bug spotted by rovv. Bugfix on 0.2.0.1-alpha.
13708 - When using the TransPort option on OpenBSD, and using the User
13709 option to change UID and drop privileges, make sure to open /dev/pf
13710 before dropping privileges. Fixes bug 782. Patch from Christopher
13711 Davis. Bugfix on 0.1.2.1-alpha.
13712 - Correctly detect the presence of the linux/netfilter_ipv4.h header
13713 when building against recent kernels. Bugfix on 0.1.2.1-alpha.
13714 - Add a missing safe_str() call for a debug log message.
13715 - Use 64 bits instead of 32 bits for connection identifiers used with
13716 the controller protocol, to greatly reduce risk of identifier reuse.
13717 - Make the autoconf script accept the obsolete --with-ssl-dir
13718 option as an alias for the actually-working --with-openssl-dir
13719 option. Fix the help documentation to recommend --with-openssl-dir.
13720 Based on a patch by "Dave". Bugfix on 0.2.0.1-alpha.
13723 - Rate-limit too-many-sockets messages: when they happen, they happen
13724 a lot. Resolves bug 748.
13725 - Resist DNS poisoning a little better by making sure that names in
13726 answer sections match.
13727 - Print the SOCKS5 error message string as well as the error code
13728 when a tor-resolve request fails. Patch from Jacob.
13731 Changes in version 0.2.1.4-alpha - 2008-08-04
13732 Tor 0.2.1.4-alpha fixes a pair of crash bugs in 0.2.1.3-alpha.
13735 - The address part of exit policies was not correctly written
13736 to router descriptors. This generated router descriptors that failed
13737 their self-checks. Noticed by phobos, fixed by Karsten. Bugfix
13739 - Tor triggered a false assert when extending a circuit to a relay
13740 but we already have a connection open to that relay. Noticed by
13741 phobos, fixed by Karsten. Bugfix on 0.2.1.3-alpha.
13744 - Fix a hidden service logging bug: in some edge cases, the router
13745 descriptor of a previously picked introduction point becomes
13746 obsolete and we need to give up on it rather than continually
13747 complaining that it has become obsolete. Observed by xiando. Bugfix
13750 o Removed features:
13751 - Take out the TestVia config option, since it was a workaround for
13752 a bug that was fixed in Tor 0.1.1.21.
13755 Changes in version 0.2.1.3-alpha - 2008-08-03
13756 Tor 0.2.1.3-alpha implements most of the pieces to prevent
13757 infinite-length circuit attacks (see proposal 110); fixes a bug that
13758 might cause exit relays to corrupt streams they send back; allows
13759 address patterns (e.g. 255.128.0.0/16) to appear in ExcludeNodes and
13760 ExcludeExitNodes config options; and fixes a big pile of bugs.
13762 o Bootstrapping bugfixes (on 0.2.1.x-alpha):
13763 - Send a bootstrap problem "warn" event on the first problem if the
13764 reason is NO_ROUTE (that is, our network is down).
13767 - Implement most of proposal 110: The first K cells to be sent
13768 along a circuit are marked as special "early" cells; only K "early"
13769 cells will be allowed. Once this code is universal, we can block
13770 certain kinds of DOS attack by requiring that EXTEND commands must
13771 be sent using an "early" cell.
13774 - Try to attach connections immediately upon receiving a RENDEZVOUS2
13775 or RENDEZVOUS_ESTABLISHED cell. This can save a second or two
13776 on the client side when connecting to a hidden service. Bugfix
13777 on 0.0.6pre1. Found and fixed by Christian Wilms; resolves bug 743.
13778 - Ensure that two circuits can never exist on the same connection
13779 with the same circuit ID, even if one is marked for close. This
13780 is conceivably a bugfix for bug 779; fixes a bug on 0.1.0.4-rc.
13783 - When relays do their initial bandwidth measurement, don't limit
13784 to just our entry guards for the test circuits. Otherwise we tend
13785 to have multiple test circuits going through a single entry guard,
13786 which makes our bandwidth test less accurate. Fixes part of bug 654;
13787 patch contributed by Josh Albrecht.
13788 - Add an ExcludeExitNodes option so users can list a set of nodes
13789 that should be be excluded from the exit node position, but
13790 allowed elsewhere. Implements proposal 151.
13791 - Allow address patterns (e.g., 255.128.0.0/16) to appear in
13792 ExcludeNodes and ExcludeExitNodes lists.
13793 - Change the implementation of ExcludeNodes and ExcludeExitNodes to
13794 be more efficient. Formerly it was quadratic in the number of
13795 servers; now it should be linear. Fixes bug 509.
13796 - Save 16-22 bytes per open circuit by moving the n_addr, n_port,
13797 and n_conn_id_digest fields into a separate structure that's
13798 only needed when the circuit has not yet attached to an n_conn.
13801 - Change the contrib/tor.logrotate script so it makes the new
13802 logs as "_tor:_tor" rather than the default, which is generally
13803 "root:wheel". Fixes bug 676, reported by Serge Koksharov.
13804 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13805 warnings (occasionally), but it can also cause the compiler to
13806 eliminate error-checking code. Suggested by Peter Gutmann.
13807 - When a hidden service is giving up on an introduction point candidate
13808 that was not included in the last published rendezvous descriptor,
13809 don't reschedule publication of the next descriptor. Fixes bug 763.
13811 - Mark RendNodes, RendExcludeNodes, HiddenServiceNodes, and
13812 HiddenServiceExcludeNodes as obsolete: they never worked properly,
13813 and nobody claims to be using them. Fixes bug 754. Bugfix on
13814 0.1.0.1-rc. Patch from Christian Wilms.
13815 - Fix a small alignment and memory-wasting bug on buffer chunks.
13818 o Minor bugfixes (controller):
13819 - When closing an application-side connection because its circuit
13820 is getting torn down, generate the stream event correctly.
13821 Bugfix on 0.1.2.x. Anonymous patch.
13823 o Removed features:
13824 - Remove all backward-compatibility code to support relays running
13825 versions of Tor so old that they no longer work at all on the
13829 Changes in version 0.2.0.30 - 2008-07-15
13831 - Stop using __attribute__((nonnull)) with GCC: it can give us useful
13832 warnings (occasionally), but it can also cause the compiler to
13833 eliminate error-checking code. Suggested by Peter Gutmann.
13836 Changes in version 0.2.0.29-rc - 2008-07-08
13837 Tor 0.2.0.29-rc fixes two big bugs with using bridges, fixes more
13838 hidden-service performance bugs, and fixes a bunch of smaller bugs.
13841 - If you have more than one bridge but don't know their keys,
13842 you would only launch a request for the descriptor of the first one
13843 on your list. (Tor considered launching requests for the others, but
13844 found that it already had a connection on the way for $0000...0000
13845 so it didn't open another.) Bugfix on 0.2.0.x.
13846 - If you have more than one bridge but don't know their keys, and the
13847 connection to one of the bridges failed, you would cancel all
13848 pending bridge connections. (After all, they all have the same
13849 digest.) Bugfix on 0.2.0.x.
13850 - When a hidden service was trying to establish an introduction point,
13851 and Tor had built circuits preemptively for such purposes, we
13852 were ignoring all the preemptive circuits and launching a new one
13853 instead. Bugfix on 0.2.0.14-alpha.
13854 - When a hidden service was trying to establish an introduction point,
13855 and Tor *did* manage to reuse one of the preemptively built
13856 circuits, it didn't correctly remember which one it used,
13857 so it asked for another one soon after, until there were no
13858 more preemptive circuits, at which point it launched one from
13859 scratch. Bugfix on 0.0.9.x.
13860 - Make directory servers include the X-Your-Address-Is: http header in
13861 their responses even for begin_dir conns. Now clients who only
13862 ever use begin_dir connections still have a way to learn their IP
13863 address. Fixes bug 737; bugfix on 0.2.0.22-rc. Reported by goldy.
13866 - Fix a macro/CPP interaction that was confusing some compilers:
13867 some GCCs don't like #if/#endif pairs inside macro arguments.
13869 - Fix macro collision between OpenSSL 0.9.8h and Windows headers.
13870 Fixes bug 704; fix from Steven Murdoch.
13871 - When opening /dev/null in finish_daemonize(), do not pass the
13872 O_CREAT flag. Fortify was complaining, and correctly so. Fixes
13873 bug 742; fix from Michael Scherer. Bugfix on 0.0.2pre19.
13874 - Correctly detect transparent proxy support on Linux hosts that
13875 require in.h to be included before netfilter_ipv4.h. Patch
13877 - Disallow session resumption attempts during the renegotiation
13878 stage of the v2 handshake protocol. Clients should never be trying
13879 session resumption at this point, but apparently some did, in
13880 ways that caused the handshake to fail. Bugfix on 0.2.0.20-rc. Bug
13881 found by Geoff Goodell.
13884 Changes in version 0.2.1.2-alpha - 2008-06-20
13885 Tor 0.2.1.2-alpha includes a new "TestingTorNetwork" config option to
13886 make it easier to set up your own private Tor network; fixes several
13887 big bugs with using more than one bridge relay; fixes a big bug with
13888 offering hidden services quickly after Tor starts; and uses a better
13889 API for reporting potential bootstrapping problems to the controller.
13892 - New TestingTorNetwork config option to allow adjustment of
13893 previously constant values that, while reasonable, could slow
13894 bootstrapping. Implements proposal 135. Patch from Karsten.
13897 - If you have more than one bridge but don't know their digests,
13898 you would only learn a request for the descriptor of the first one
13899 on your list. (Tor considered launching requests for the others, but
13900 found that it already had a connection on the way for $0000...0000
13901 so it didn't open another.) Bugfix on 0.2.0.x.
13902 - If you have more than one bridge but don't know their digests,
13903 and the connection to one of the bridges failed, you would cancel
13904 all pending bridge connections. (After all, they all have the
13905 same digest.) Bugfix on 0.2.0.x.
13906 - When establishing a hidden service, introduction points that
13907 originate from cannibalized circuits are completely ignored and not
13908 included in rendezvous service descriptors. This might be another
13909 reason for delay in making a hidden service available. Bugfix
13910 from long ago (0.0.9.x?)
13913 - Allow OpenSSL to use dynamic locks if it wants.
13914 - When building a consensus, do not include routers that are down.
13915 This will cut down 30% to 40% on consensus size. Implements
13917 - In directory authorities' approved-routers files, allow
13918 fingerprints with or without space.
13919 - Add a "GETINFO /status/bootstrap-phase" controller option, so the
13920 controller can query our current bootstrap state in case it attaches
13921 partway through and wants to catch up.
13922 - Send an initial "Starting" bootstrap status event, so we have a
13923 state to start out in.
13926 - Asking for a conditional consensus at .../consensus/<fingerprints>
13927 would crash a dirserver if it did not already have a
13928 consensus. Bugfix on 0.2.1.1-alpha.
13929 - Clean up some macro/CPP interactions: some GCC versions don't like
13930 #if/#endif pairs inside macro arguments. Fixes bug 707. Bugfix on
13933 o Bootstrapping bugfixes (on 0.2.1.1-alpha):
13934 - Directory authorities shouldn't complain about bootstrapping
13935 problems just because they do a lot of reachability testing and
13936 some of the connection attempts fail.
13937 - Start sending "count" and "recommendation" key/value pairs in
13938 bootstrap problem status events, so the controller can hear about
13939 problems even before Tor decides they're worth reporting for sure.
13940 - If you're using bridges, generate "bootstrap problem" warnings
13941 as soon as you run out of working bridges, rather than waiting
13942 for ten failures -- which will never happen if you have less than
13944 - If we close our OR connection because there's been a circuit
13945 pending on it for too long, we were telling our bootstrap status
13946 events "REASON=NONE". Now tell them "REASON=TIMEOUT".
13949 Changes in version 0.2.1.1-alpha - 2008-06-13
13950 Tor 0.2.1.1-alpha fixes a lot of memory fragmentation problems that
13951 were making the Tor process bloat especially on Linux; makes our TLS
13952 handshake blend in better; sends "bootstrap phase" status events to
13953 the controller, so it can keep the user informed of progress (and
13954 problems) fetching directory information and establishing circuits;
13955 and adds a variety of smaller features.
13958 - More work on making our TLS handshake blend in: modify the list
13959 of ciphers advertised by OpenSSL in client mode to even more
13960 closely resemble a common web browser. We cheat a little so that
13961 we can advertise ciphers that the locally installed OpenSSL doesn't
13963 - Start sending "bootstrap phase" status events to the controller,
13964 so it can keep the user informed of progress fetching directory
13965 information and establishing circuits. Also inform the controller
13966 if we think we're stuck at a particular bootstrap phase. Implements
13968 - Resume using OpenSSL's RAND_poll() for better (and more portable)
13969 cross-platform entropy collection again. We used to use it, then
13970 stopped using it because of a bug that could crash systems that
13971 called RAND_poll when they had a lot of fds open. It looks like the
13972 bug got fixed in late 2006. Our new behavior is to call RAND_poll()
13973 at startup, and to call RAND_poll() when we reseed later only if
13974 we have a non-buggy OpenSSL version.
13977 - When we choose to abandon a new entry guard because we think our
13978 older ones might be better, close any circuits pending on that
13979 new entry guard connection. This fix should make us recover much
13980 faster when our network is down and then comes back. Bugfix on
13981 0.1.2.8-beta; found by lodger.
13983 o Memory fixes and improvements:
13984 - Add a malloc_good_size implementation to OpenBSD_malloc_linux.c,
13985 to avoid unused RAM in buffer chunks and memory pools.
13986 - Speed up parsing and cut down on memory fragmentation by using
13987 stack-style allocations for parsing directory objects. Previously,
13988 this accounted for over 40% of allocations from within Tor's code
13989 on a typical directory cache.
13990 - Use a Bloom filter rather than a digest-based set to track which
13991 descriptors we need to keep around when we're cleaning out old
13992 router descriptors. This speeds up the computation significantly,
13993 and may reduce fragmentation.
13994 - Reduce the default smartlist size from 32 to 16; it turns out that
13995 most smartlists hold around 8-12 elements tops.
13996 - Make dumpstats() log the fullness and size of openssl-internal
13998 - If the user has applied the experimental SSL_MODE_RELEASE_BUFFERS
13999 patch to their OpenSSL, turn it on to save memory on servers. This
14000 patch will (with any luck) get included in a mainline distribution
14002 - Never use OpenSSL compression: it wastes RAM and CPU trying to
14003 compress cells, which are basically all encrypted, compressed,
14007 - Stop reloading the router list from disk for no reason when we
14008 run out of reachable directory mirrors. Once upon a time reloading
14009 it would set the 'is_running' flag back to 1 for them. It hasn't
14010 done that for a long time.
14011 - In very rare situations new hidden service descriptors were
14012 published earlier than 30 seconds after the last change to the
14013 service. (We currently think that a hidden service descriptor
14014 that's been stable for 30 seconds is worth publishing.)
14017 - Allow separate log levels to be configured for different logging
14018 domains. For example, this allows one to log all notices, warnings,
14019 or errors, plus all memory management messages of level debug or
14020 higher, with: Log [MM] debug-err [*] notice-err file /var/log/tor.
14021 - Add a couple of extra warnings to --enable-gcc-warnings for GCC 4.3,
14022 and stop using a warning that had become unfixably verbose under
14024 - New --hush command-line option similar to --quiet. While --quiet
14025 disables all logging to the console on startup, --hush limits the
14026 output to messages of warning and error severity.
14027 - Servers support a new URL scheme for consensus downloads that
14028 allows the client to specify which authorities are trusted.
14029 The server then only sends the consensus if the client will trust
14030 it. Otherwise a 404 error is sent back. Clients use this
14031 new scheme when the server supports it (meaning it's running
14032 0.2.1.1-alpha or later). Implements proposal 134.
14033 - New configure/torrc options (--enable-geoip-stats,
14034 DirRecordUsageByCountry) to record how many IPs we've served
14035 directory info to in each country code, how many status documents
14036 total we've sent to each country code, and what share of the total
14037 directory requests we should expect to see.
14038 - Use the TLS1 hostname extension to more closely resemble browser
14040 - Lots of new unit tests.
14041 - Add a macro to implement the common pattern of iterating through
14042 two parallel lists in lockstep.
14045 Changes in version 0.2.0.28-rc - 2008-06-13
14046 Tor 0.2.0.28-rc fixes an anonymity-related bug, fixes a hidden-service
14047 performance bug, and fixes a bunch of smaller bugs.
14050 - Fix a bug where, when we were choosing the 'end stream reason' to
14051 put in our relay end cell that we send to the exit relay, Tor
14052 clients on Windows were sometimes sending the wrong 'reason'. The
14053 anonymity problem is that exit relays may be able to guess whether
14054 the client is running Windows, thus helping partition the anonymity
14055 set. Down the road we should stop sending reasons to exit relays,
14056 or otherwise prevent future versions of this bug.
14059 - While setting up a hidden service, some valid introduction circuits
14060 were overlooked and abandoned. This might be the reason for
14061 the long delay in making a hidden service available. Bugfix on
14065 - Update to the "June 9 2008" ip-to-country file.
14066 - Run 'make test' as part of 'make dist', so we stop releasing so
14067 many development snapshots that fail their unit tests.
14070 - When we're checking if we have enough dir info for each relay
14071 to begin establishing circuits, make sure that we actually have
14072 the descriptor listed in the consensus, not just any descriptor.
14074 - Bridge relays no longer print "xx=0" in their extrainfo document
14075 for every single country code in the geoip db. Bugfix on
14077 - Only warn when we fail to load the geoip file if we were planning to
14078 include geoip stats in our extrainfo document. Bugfix on 0.2.0.27-rc.
14079 - If we change our MaxAdvertisedBandwidth and then reload torrc,
14080 Tor won't realize it should publish a new relay descriptor. Fixes
14081 bug 688, reported by mfr. Bugfix on 0.1.2.x.
14082 - When we haven't had any application requests lately, don't bother
14083 logging that we have expired a bunch of descriptors. Bugfix
14085 - Make relay cells written on a connection count as non-padding when
14086 tracking how long a connection has been in use. Bugfix on
14087 0.2.0.1-alpha. Spotted by lodger.
14088 - Fix unit tests in 0.2.0.27-rc.
14089 - Fix compile on Windows.
14092 Changes in version 0.2.0.27-rc - 2008-06-03
14093 Tor 0.2.0.27-rc adds a few features we left out of the earlier
14094 release candidates. In particular, we now include an IP-to-country
14095 GeoIP database, so controllers can easily look up what country a
14096 given relay is in, and so bridge relays can give us some sanitized
14097 summaries about which countries are making use of bridges. (See proposal
14098 126-geoip-fetching.txt for details.)
14101 - Include an IP-to-country GeoIP file in the tarball, so bridge
14102 relays can report sanitized summaries of the usage they're seeing.
14105 - Add a "PURPOSE=" argument to "STREAM NEW" events, as suggested by
14106 Robert Hogan. Fixes the first part of bug 681.
14107 - Make bridge authorities never serve extrainfo docs.
14108 - Add support to detect Libevent versions in the 1.4.x series
14110 - Fix build on gcc 4.3 with --enable-gcc-warnings set.
14111 - Include a new contrib/tor-exit-notice.html file that exit relay
14112 operators can put on their website to help reduce abuse queries.
14115 - When tunneling an encrypted directory connection, and its first
14116 circuit fails, do not leave it unattached and ask the controller
14117 to deal. Fixes the second part of bug 681.
14118 - Make bridge authorities correctly expire old extrainfo documents
14122 Changes in version 0.2.0.26-rc - 2008-05-13
14123 Tor 0.2.0.26-rc fixes a major security vulnerability caused by a bug
14124 in Debian's OpenSSL packages. All users running any 0.2.0.x version
14125 should upgrade, whether they're running Debian or not.
14127 o Major security fixes:
14128 - Use new V3 directory authority keys on the tor26, gabelmoo, and
14129 moria1 V3 directory authorities. The old keys were generated with
14130 a vulnerable version of Debian's OpenSSL package, and must be
14131 considered compromised. Other authorities' keys were not generated
14132 with an affected version of OpenSSL.
14135 - List authority signatures as "unrecognized" based on DirServer
14136 lines, not on cert cache. Bugfix on 0.2.0.x.
14139 - Add a new V3AuthUseLegacyKey option to make it easier for
14140 authorities to change their identity keys if they have to.
14143 Changes in version 0.2.0.25-rc - 2008-04-23
14144 Tor 0.2.0.25-rc makes Tor work again on OS X and certain BSDs.
14147 - Remember to initialize threading before initializing logging.
14148 Otherwise, many BSD-family implementations will crash hard on
14149 startup. Fixes bug 671. Bugfix on 0.2.0.24-rc.
14152 - Authorities correctly free policies on bad servers on
14153 exit. Fixes bug 672. Bugfix on 0.2.0.x.
14156 Changes in version 0.2.0.24-rc - 2008-04-22
14157 Tor 0.2.0.24-rc adds dizum (run by Alex de Joode) as the new sixth
14158 v3 directory authority, makes relays with dynamic IP addresses and no
14159 DirPort notice more quickly when their IP address changes, fixes a few
14160 rare crashes and memory leaks, and fixes a few other miscellaneous bugs.
14162 o New directory authorities:
14163 - Take lefkada out of the list of v3 directory authorities, since
14164 it has been down for months.
14165 - Set up dizum (run by Alex de Joode) as the new sixth v3 directory
14169 - Detect address changes more quickly on non-directory mirror
14170 relays. Bugfix on 0.2.0.18-alpha; fixes bug 652.
14172 o Minor features (security):
14173 - Reject requests for reverse-dns lookup of names that are in
14174 a private address space. Patch from lodger.
14175 - Non-exit relays no longer allow DNS requests. Fixes bug 619. Patch
14178 o Minor bugfixes (crashes):
14179 - Avoid a rare assert that can trigger when Tor doesn't have much
14180 directory information yet and it tries to fetch a v2 hidden
14181 service descriptor. Fixes bug 651, reported by nwf.
14182 - Initialize log mutex before initializing dmalloc. Otherwise,
14183 running with dmalloc would crash. Bugfix on 0.2.0.x-alpha.
14184 - Use recursive pthread mutexes in order to avoid deadlock when
14185 logging debug-level messages to a controller. Bug spotted by nwf,
14186 bugfix on 0.2.0.16-alpha.
14188 o Minor bugfixes (resource management):
14189 - Keep address policies from leaking memory: start their refcount
14190 at 1, not 2. Bugfix on 0.2.0.16-alpha.
14191 - Free authority certificates on exit, so they don't look like memory
14192 leaks. Bugfix on 0.2.0.19-alpha.
14193 - Free static hashtables for policy maps and for TLS connections on
14194 shutdown, so they don't look like memory leaks. Bugfix on 0.2.0.x.
14195 - Avoid allocating extra space when computing consensuses on 64-bit
14196 platforms. Bug spotted by aakova.
14198 o Minor bugfixes (misc):
14199 - Do not read the configuration file when we've only been told to
14200 generate a password hash. Fixes bug 643. Bugfix on 0.0.9pre5. Fix
14201 based on patch from Sebastian Hahn.
14202 - Exit relays that are used as a client can now reach themselves
14203 using the .exit notation, rather than just launching an infinite
14204 pile of circuits. Fixes bug 641. Reported by Sebastian Hahn.
14205 - When attempting to open a logfile fails, tell us why.
14206 - Fix a dumb bug that was preventing us from knowing that we should
14207 preemptively build circuits to handle expected directory requests.
14208 Fixes bug 660. Bugfix on 0.1.2.x.
14209 - Warn less verbosely about clock skew from netinfo cells from
14210 untrusted sources. Fixes bug 663.
14211 - Make controller stream events for DNS requests more consistent,
14212 by adding "new stream" events for DNS requests, and removing
14213 spurious "stream closed" events" for cached reverse resolves.
14214 Patch from mwenge. Fixes bug 646.
14215 - Correctly notify one-hop connections when a circuit build has
14216 failed. Possible fix for bug 669. Found by lodger.
14219 Changes in version 0.2.0.23-rc - 2008-03-24
14220 Tor 0.2.0.23-rc is the fourth release candidate for the 0.2.0 series. It
14221 makes bootstrapping faster if the first directory mirror you contact
14222 is down. The bundles also include the new Vidalia 0.1.2 release.
14225 - When a tunneled directory request is made to a directory server
14226 that's down, notice after 30 seconds rather than 120 seconds. Also,
14227 fail any begindir streams that are pending on it, so they can
14228 retry elsewhere. This was causing multi-minute delays on bootstrap.
14231 Changes in version 0.2.0.22-rc - 2008-03-18
14232 Tor 0.2.0.22-rc is the third release candidate for the 0.2.0 series. It
14233 enables encrypted directory connections by default for non-relays, fixes
14234 some broken TLS behavior we added in 0.2.0.20-rc, and resolves many
14235 other bugs. The bundles also include Vidalia 0.1.1 and Torbutton 1.1.17.
14238 - Enable encrypted directory connections by default for non-relays,
14239 so censor tools that block Tor directory connections based on their
14240 plaintext patterns will no longer work. This means Tor works in
14241 certain censored countries by default again.
14244 - Make sure servers always request certificates from clients during
14245 TLS renegotiation. Reported by lodger; bugfix on 0.2.0.20-rc.
14246 - Do not enter a CPU-eating loop when a connection is closed in
14247 the middle of client-side TLS renegotiation. Fixes bug 622. Bug
14248 diagnosed by lodger; bugfix on 0.2.0.20-rc.
14249 - Fix assertion failure that could occur when a blocked circuit
14250 became unblocked, and it had pending client DNS requests. Bugfix
14251 on 0.2.0.1-alpha. Fixes bug 632.
14253 o Minor bugfixes (on 0.1.2.x):
14254 - Generate "STATUS_SERVER" events rather than misspelled
14255 "STATUS_SEVER" events. Caught by mwenge.
14256 - When counting the number of bytes written on a TLS connection,
14257 look at the BIO actually used for writing to the network, not
14258 at the BIO used (sometimes) to buffer data for the network.
14259 Looking at different BIOs could result in write counts on the
14260 order of ULONG_MAX. Fixes bug 614.
14261 - On Windows, correctly detect errors when listing the contents of
14262 a directory. Fix from lodger.
14264 o Minor bugfixes (on 0.2.0.x):
14265 - Downgrade "sslv3 alert handshake failure" message to INFO.
14266 - If we set RelayBandwidthRate and RelayBandwidthBurst very high but
14267 left BandwidthRate and BandwidthBurst at the default, we would be
14268 silently limited by those defaults. Now raise them to match the
14269 RelayBandwidth* values.
14270 - Fix the SVK version detection logic to work correctly on a branch.
14271 - Make --enable-openbsd-malloc work correctly on Linux with alpha
14272 CPUs. Fixes bug 625.
14273 - Logging functions now check that the passed severity is sane.
14274 - Use proper log levels in the testsuite call of
14275 get_interface_address6().
14276 - When using a nonstandard malloc, do not use the platform values for
14277 HAVE_MALLOC_GOOD_SIZE or HAVE_MALLOC_USABLE_SIZE.
14278 - Make the openbsd malloc code use 8k pages on alpha CPUs and
14280 - Detect mismatched page sizes when using --enable-openbsd-malloc.
14281 - Avoid double-marked-for-close warning when certain kinds of invalid
14282 .in-addr.arpa addresses are passed to the DNSPort. Part of a fix
14283 for bug 617. Bugfix on 0.2.0.1-alpha.
14284 - Make sure that the "NULL-means-reject *:*" convention is followed by
14285 all the policy manipulation functions, avoiding some possible crash
14286 bugs. Bug found by lodger. Bugfix on 0.2.0.16-alpha.
14287 - Fix the implementation of ClientDNSRejectInternalAddresses so that it
14288 actually works, and doesn't warn about every single reverse lookup.
14289 Fixes the other part of bug 617. Bugfix on 0.2.0.1-alpha.
14292 - Only log guard node status when guard node status has changed.
14293 - Downgrade the 3 most common "INFO" messages to "DEBUG". This will
14294 make "INFO" 75% less verbose.
14297 Changes in version 0.2.0.21-rc - 2008-03-02
14298 Tor 0.2.0.21-rc is the second release candidate for the 0.2.0 series. It
14299 makes Tor work well with Vidalia again, fixes a rare assert bug,
14300 and fixes a pair of more minor bugs. The bundles also include Vidalia
14301 0.1.0 and Torbutton 1.1.16.
14304 - The control port should declare that it requires password auth
14305 when HashedControlSessionPassword is set too. Patch from Matt Edman;
14306 bugfix on 0.2.0.20-rc. Fixes bug 615.
14307 - Downgrade assert in connection_buckets_decrement() to a log message.
14308 This may help us solve bug 614, and in any case will make its
14309 symptoms less severe. Bugfix on 0.2.0.20-rc. Reported by fredzupy.
14310 - We were sometimes miscounting the number of bytes read from the
14311 network, causing our rate limiting to not be followed exactly.
14312 Bugfix on 0.2.0.16-alpha. Reported by lodger.
14315 - Fix compilation with OpenSSL 0.9.8 and 0.9.8a. All other supported
14316 OpenSSL versions should have been working fine. Diagnosis and patch
14317 from lodger, Karsten Loesing, and Sebastian Hahn. Fixes bug 616.
14318 Bugfix on 0.2.0.20-rc.
14321 Changes in version 0.2.0.20-rc - 2008-02-24
14322 Tor 0.2.0.20-rc is the first release candidate for the 0.2.0 series. It
14323 makes more progress towards normalizing Tor's TLS handshake, makes
14324 hidden services work better again, helps relays bootstrap if they don't
14325 know their IP address, adds optional support for linking in openbsd's
14326 allocator or tcmalloc, allows really fast relays to scale past 15000
14327 sockets, and fixes a bunch of minor bugs reported by Veracode.
14330 - Enable the revised TLS handshake based on the one designed by
14331 Steven Murdoch in proposal 124, as revised in proposal 130. It
14332 includes version negotiation for OR connections as described in
14333 proposal 105. The new handshake is meant to be harder for censors
14334 to fingerprint, and it adds the ability to detect certain kinds of
14335 man-in-the-middle traffic analysis attacks. The version negotiation
14336 feature will allow us to improve Tor's link protocol more safely
14338 - Choose which bridge to use proportional to its advertised bandwidth,
14339 rather than uniformly at random. This should speed up Tor for
14340 bridge users. Also do this for people who set StrictEntryNodes.
14341 - When a TrackHostExits-chosen exit fails too many times in a row,
14342 stop using it. Bugfix on 0.1.2.x; fixes bug 437.
14345 - Resolved problems with (re-)fetching hidden service descriptors.
14346 Patch from Karsten Loesing; fixes problems with 0.2.0.18-alpha
14347 and 0.2.0.19-alpha.
14348 - If we only ever used Tor for hidden service lookups or posts, we
14349 would stop building circuits and start refusing connections after
14350 24 hours, since we falsely believed that Tor was dormant. Reported
14351 by nwf; bugfix on 0.1.2.x.
14352 - Servers that don't know their own IP address should go to the
14353 authorities for their first directory fetch, even if their DirPort
14354 is off or if they don't know they're reachable yet. This will help
14355 them bootstrap better. Bugfix on 0.2.0.18-alpha; fixes bug 609.
14356 - When counting the number of open sockets, count not only the number
14357 of sockets we have received from the socket() call, but also
14358 the number we've gotten from accept() and socketpair(). This bug
14359 made us fail to count all sockets that we were using for incoming
14360 connections. Bugfix on 0.2.0.x.
14361 - Fix code used to find strings within buffers, when those strings
14362 are not in the first chunk of the buffer. Bugfix on 0.2.0.x.
14363 - Fix potential segfault when parsing HTTP headers. Bugfix on 0.2.0.x.
14364 - Add a new __HashedControlSessionPassword option for controllers
14365 to use for one-off session password hashes that shouldn't get
14366 saved to disk by SAVECONF --- Vidalia users were accumulating a
14367 pile of HashedControlPassword lines in their torrc files, one for
14368 each time they had restarted Tor and then clicked Save. Make Tor
14369 automatically convert "HashedControlPassword" to this new option but
14370 only when it's given on the command line. Partial fix for bug 586.
14372 o Minor features (performance):
14373 - Tune parameters for cell pool allocation to minimize amount of
14375 - Add OpenBSD malloc code from phk as an optional malloc
14376 replacement on Linux: some glibc libraries do very poorly
14377 with Tor's memory allocation patterns. Pass
14378 --enable-openbsd-malloc to get the replacement malloc code.
14379 - Add a --with-tcmalloc option to the configure script to link
14380 against tcmalloc (if present). Does not yet search for
14381 non-system include paths.
14382 - Stop imposing an arbitrary maximum on the number of file descriptors
14383 used for busy servers. Bug reported by Olaf Selke; patch from
14386 o Minor features (other):
14387 - When SafeLogging is disabled, log addresses along with all TLS
14389 - When building with --enable-gcc-warnings, check for whether Apple's
14390 warning "-Wshorten-64-to-32" is available.
14391 - Add a --passphrase-fd argument to the tor-gencert command for
14394 o Minor bugfixes (memory leaks and code problems):
14395 - We were leaking a file descriptor if Tor started with a zero-length
14396 cached-descriptors file. Patch by freddy77; bugfix on 0.1.2.
14397 - Detect size overflow in zlib code. Reported by Justin Ferguson and
14399 - We were comparing the raw BridgePassword entry with a base64'ed
14400 version of it, when handling a "/tor/networkstatus-bridges"
14401 directory request. Now compare correctly. Noticed by Veracode.
14402 - Recover from bad tracked-since value in MTBF-history file.
14403 Should fix bug 537.
14404 - Alter the code that tries to recover from unhandled write
14405 errors, to not try to flush onto a socket that's given us
14406 unhandled errors. Bugfix on 0.1.2.x.
14407 - Make Unix controlsockets work correctly on OpenBSD. Patch from
14408 tup. Bugfix on 0.2.0.3-alpha.
14410 o Minor bugfixes (other):
14411 - If we have an extra-info document for our server, always make
14412 it available on the control port, even if we haven't gotten
14413 a copy of it from an authority yet. Patch from mwenge.
14414 - Log the correct memory chunk sizes for empty RAM chunks in mempool.c.
14415 - Directory mirrors no longer include a guess at the client's IP
14416 address if the connection appears to be coming from the same /24
14417 network; it was producing too many wrong guesses.
14418 - Make the new hidden service code respect the SafeLogging setting.
14419 Bugfix on 0.2.0.x. Patch from Karsten.
14420 - When starting as an authority, do not overwrite all certificates
14421 cached from other authorities. Bugfix on 0.2.0.x. Fixes bug 606.
14422 - If we're trying to flush the last bytes on a connection (for
14423 example, when answering a directory request), reset the
14424 time-to-give-up timeout every time we manage to write something
14425 on the socket. Bugfix on 0.1.2.x.
14426 - Change the behavior of "getinfo status/good-server-descriptor"
14427 so it doesn't return failure when any authority disappears.
14428 - Even though the man page said that "TrackHostExits ." should
14429 work, nobody had ever implemented it. Bugfix on 0.1.0.x.
14430 - Report TLS "zero return" case as a "clean close" and "IO error"
14431 as a "close". Stop calling closes "unexpected closes": existing
14432 Tors don't use SSL_close(), so having a connection close without
14433 the TLS shutdown handshake is hardly unexpected.
14434 - Send NAMESERVER_STATUS messages for a single failed nameserver
14437 o Code simplifications and refactoring:
14438 - Remove the tor_strpartition function: its logic was confused,
14439 and it was only used for one thing that could be implemented far
14443 Changes in version 0.2.0.19-alpha - 2008-02-09
14444 Tor 0.2.0.19-alpha makes more progress towards normalizing Tor's TLS
14445 handshake, makes path selection for relays more secure and IP address
14446 guessing more robust, and generally fixes a lot of bugs in preparation
14447 for calling the 0.2.0 branch stable.
14450 - Do not include recognizeable strings in the commonname part of
14451 Tor's x509 certificates.
14454 - If we're a relay, avoid picking ourselves as an introduction point,
14455 a rendezvous point, or as the final hop for internal circuits. Bug
14456 reported by taranis and lodger. Bugfix on 0.1.2.x.
14457 - Patch from "Andrew S. Lists" to catch when we contact a directory
14458 mirror at IP address X and he says we look like we're coming from
14459 IP address X. Bugfix on 0.1.2.x.
14461 o Minor features (security):
14462 - Be more paranoid about overwriting sensitive memory on free(),
14463 as a defensive programming tactic to ensure forward secrecy.
14465 o Minor features (directory authority):
14466 - Actually validate the options passed to AuthDirReject,
14467 AuthDirInvalid, AuthDirBadDir, and AuthDirBadExit.
14468 - Reject router descriptors with out-of-range bandwidthcapacity or
14469 bandwidthburst values.
14471 o Minor features (controller):
14472 - Reject controller commands over 1MB in length. This keeps rogue
14473 processes from running us out of memory.
14475 o Minor features (misc):
14476 - Give more descriptive well-formedness errors for out-of-range
14477 hidden service descriptor/protocol versions.
14478 - Make memory debugging information describe more about history
14479 of cell allocation, so we can help reduce our memory use.
14481 o Deprecated features (controller):
14482 - The status/version/num-versioning and status/version/num-concurring
14483 GETINFO options are no longer useful in the v3 directory protocol:
14484 treat them as deprecated, and warn when they're used.
14487 - When our consensus networkstatus has been expired for a while, stop
14488 being willing to build circuits using it. Fixes bug 401. Bugfix
14490 - Directory caches now fetch certificates from all authorities
14491 listed in a networkstatus consensus, even when they do not
14492 recognize them. Fixes bug 571. Bugfix on 0.2.0.x.
14493 - When connecting to a bridge without specifying its key, insert
14494 the connection into the identity-to-connection map as soon as
14495 a key is learned. Fixes bug 574. Bugfix on 0.2.0.x.
14496 - Detect versions of OS X where malloc_good_size() is present in the
14497 library but never actually declared. Resolves bug 587. Bugfix
14499 - Stop incorrectly truncating zlib responses to directory authority
14500 signature download requests. Fixes bug 593. Bugfix on 0.2.0.x.
14501 - Stop recommending that every server operator send mail to tor-ops.
14502 Resolves bug 597. Bugfix on 0.1.2.x.
14503 - Don't trigger an assert if we start a directory authority with a
14504 private IP address (like 127.0.0.1).
14505 - Avoid possible failures when generating a directory with routers
14506 with over-long versions strings, or too many flags set. Bugfix
14508 - If an attempt to launch a DNS resolve request over the control
14509 port fails because we have overrun the limit on the number of
14510 connections, tell the controller that the request has failed.
14511 - Avoid using too little bandwidth when our clock skips a few
14512 seconds. Bugfix on 0.1.2.x.
14513 - Fix shell error when warning about missing packages in configure
14514 script, on Fedora or Red Hat machines. Bugfix on 0.2.0.x.
14515 - Do not become confused when receiving a spurious VERSIONS-like
14516 cell from a confused v1 client. Bugfix on 0.2.0.x.
14517 - Re-fetch v2 (as well as v0) rendezvous descriptors when all
14518 introduction points for a hidden service have failed. Patch from
14519 Karsten Loesing. Bugfix on 0.2.0.x.
14521 o Code simplifications and refactoring:
14522 - Remove some needless generality from cpuworker code, for improved
14524 - Stop overloading the circuit_t.onionskin field for both "onionskin
14525 from a CREATE cell that we are waiting for a cpuworker to be
14526 assigned" and "onionskin from an EXTEND cell that we are going to
14527 send to an OR as soon as we are connected". Might help with bug 600.
14528 - Add an in-place version of aes_crypt() so that we can avoid doing a
14529 needless memcpy() call on each cell payload.
14532 Changes in version 0.2.0.18-alpha - 2008-01-25
14533 Tor 0.2.0.18-alpha adds a sixth v3 directory authority run by CCC,
14534 fixes a big memory leak in 0.2.0.17-alpha, and adds new config options
14535 that can warn or reject connections to ports generally associated with
14536 vulnerable-plaintext protocols.
14538 o New directory authorities:
14539 - Set up dannenberg (run by CCC) as the sixth v3 directory
14543 - Fix a major memory leak when attempting to use the v2 TLS
14544 handshake code. Bugfix on 0.2.0.x; fixes bug 589.
14545 - We accidentally enabled the under-development v2 TLS handshake
14546 code, which was causing log entries like "TLS error while
14547 renegotiating handshake". Disable it again. Resolves bug 590.
14548 - We were computing the wrong Content-Length: header for directory
14549 responses that need to be compressed on the fly, causing clients
14550 asking for those items to always fail. Bugfix on 0.2.0.x; partially
14554 - Avoid going directly to the directory authorities even if you're a
14555 relay, if you haven't found yourself reachable yet or if you've
14556 decided not to advertise your dirport yet. Addresses bug 556.
14557 - If we've gone 12 hours since our last bandwidth check, and we
14558 estimate we have less than 50KB bandwidth capacity but we could
14559 handle more, do another bandwidth test.
14560 - New config options WarnPlaintextPorts and RejectPlaintextPorts so
14561 Tor can warn and/or refuse connections to ports commonly used with
14562 vulnerable-plaintext protocols. Currently we warn on ports 23,
14563 109, 110, and 143, but we don't reject any.
14566 - When we setconf ClientOnly to 1, close any current OR and Dir
14567 listeners. Reported by mwenge.
14568 - When we get a consensus that's been signed by more people than
14569 we expect, don't log about it; it's not a big deal. Reported
14573 - Don't answer "/tor/networkstatus-bridges" directory requests if
14574 the request isn't encrypted.
14575 - Make "ClientOnly 1" config option disable directory ports too.
14576 - Patches from Karsten Loesing to make v2 hidden services more
14577 robust: work even when there aren't enough HSDir relays available;
14578 retry when a v2 rend desc fetch fails; but don't retry if we
14579 already have a usable v0 rend desc.
14582 Changes in version 0.2.0.17-alpha - 2008-01-17
14583 Tor 0.2.0.17-alpha makes the tarball build cleanly again (whoops).
14586 - Make the tor-gencert man page get included correctly in the tarball.
14589 Changes in version 0.2.0.16-alpha - 2008-01-17
14590 Tor 0.2.0.16-alpha adds a fifth v3 directory authority run by Karsten
14591 Loesing, and generally cleans up a lot of features and minor bugs.
14593 o New directory authorities:
14594 - Set up gabelmoo (run by Karsten Loesing) as the fifth v3 directory
14597 o Major performance improvements:
14598 - Switch our old ring buffer implementation for one more like that
14599 used by free Unix kernels. The wasted space in a buffer with 1mb
14600 of data will now be more like 8k than 1mb. The new implementation
14601 also avoids realloc();realloc(); patterns that can contribute to
14602 memory fragmentation.
14605 - Configuration files now accept C-style strings as values. This
14606 helps encode characters not allowed in the current configuration
14607 file format, such as newline or #. Addresses bug 557.
14608 - Although we fixed bug 539 (where servers would send HTTP status 503
14609 responses _and_ send a body too), there are still servers out
14610 there that haven't upgraded. Therefore, make clients parse such
14611 bodies when they receive them.
14612 - When we're not serving v2 directory information, there is no reason
14613 to actually keep any around. Remove the obsolete files and directory
14614 on startup if they are very old and we aren't going to serve them.
14616 o Minor performance improvements:
14617 - Reference-count and share copies of address policy entries; only 5%
14618 of them were actually distinct.
14619 - Never walk through the list of logs if we know that no log is
14620 interested in a given message.
14623 - When an authority has not signed a consensus, do not try to
14624 download a nonexistent "certificate with key 00000000". Bugfix
14625 on 0.2.0.x. Fixes bug 569.
14626 - Fix a rare assert error when we're closing one of our threads:
14627 use a mutex to protect the list of logs, so we never write to the
14628 list as it's being freed. Bugfix on 0.1.2.x. Fixes the very rare
14629 bug 575, which is kind of the revenge of bug 222.
14630 - Patch from Karsten Loesing to complain less at both the client
14631 and the relay when a relay used to have the HSDir flag but doesn't
14632 anymore, and we try to upload a hidden service descriptor.
14633 - Stop leaking one cert per TLS context. Fixes bug 582. Bugfix on
14635 - Do not try to download missing certificates until we have tried
14636 to check our fallback consensus. Fixes bug 583.
14637 - Make bridges round reported GeoIP stats info up to the nearest
14638 estimate, not down. Now we can distinguish between "0 people from
14639 this country" and "1 person from this country".
14640 - Avoid a spurious free on base64 failure. Bugfix on 0.1.2.
14641 - Avoid possible segfault if key generation fails in
14642 crypto_pk_hybrid_encrypt. Bugfix on 0.2.0.
14643 - Avoid segfault in the case where a badly behaved v2 versioning
14644 directory sends a signed networkstatus with missing client-versions.
14646 - Avoid segfaults on certain complex invocations of
14647 router_get_by_hexdigest(). Bugfix on 0.1.2.
14648 - Correct bad index on array access in parse_http_time(). Bugfix
14650 - Fix possible bug in vote generation when server versions are present
14651 but client versions are not.
14652 - Fix rare bug on REDIRECTSTREAM control command when called with no
14653 port set: it could erroneously report an error when none had
14655 - Avoid bogus crash-prone, leak-prone tor_realloc when we're
14656 compressing large objects and find ourselves with more than 4k
14657 left over. Bugfix on 0.2.0.
14658 - Fix a small memory leak when setting up a hidden service.
14659 - Fix a few memory leaks that could in theory happen under bizarre
14661 - Fix an assert if we post a general-purpose descriptor via the
14662 control port but that descriptor isn't mentioned in our current
14663 network consensus. Bug reported by Jon McLachlan; bugfix on
14666 o Minor features (controller):
14667 - Get NS events working again. Patch from tup.
14668 - The GETCONF command now escapes and quotes configuration values
14669 that don't otherwise fit into the torrc file.
14670 - The SETCONF command now handles quoted values correctly.
14672 o Minor features (directory authorities):
14673 - New configuration options to override default maximum number of
14674 servers allowed on a single IP address. This is important for
14675 running a test network on a single host.
14676 - Actually implement the -s option to tor-gencert.
14677 - Add a manual page for tor-gencert.
14679 o Minor features (bridges):
14680 - Bridge authorities no longer serve bridge descriptors over
14681 unencrypted connections.
14683 o Minor features (other):
14684 - Add hidden services and DNSPorts to the list of things that make
14685 Tor accept that it has running ports. Change starting Tor with no
14686 ports from a fatal error to a warning; we might change it back if
14687 this turns out to confuse anybody. Fixes bug 579.
14690 Changes in version 0.1.2.19 - 2008-01-17
14691 Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
14692 exit policy a little bit more conservative so it's safer to run an
14693 exit relay on a home system, and fixes a variety of smaller issues.
14696 - Exit policies now reject connections that are addressed to a
14697 relay's public (external) IP address too, unless
14698 ExitPolicyRejectPrivate is turned off. We do this because too
14699 many relays are running nearby to services that trust them based
14700 on network address.
14703 - When the clock jumps forward a lot, do not allow the bandwidth
14704 buckets to become negative. Fixes bug 544.
14705 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14706 on every successful resolve. Reported by Mike Perry.
14707 - Purge old entries from the "rephist" database and the hidden
14708 service descriptor database even when DirPort is zero.
14709 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14710 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14711 crashing or mis-answering these requests.
14712 - When we decide to send a 503 response to a request for servers, do
14713 not then also send the server descriptors: this defeats the whole
14714 purpose. Fixes bug 539.
14717 - Changing the ExitPolicyRejectPrivate setting should cause us to
14718 rebuild our server descriptor.
14719 - Fix handling of hex nicknames when answering controller requests for
14720 networkstatus by name, or when deciding whether to warn about
14721 unknown routers in a config option. (Patch from mwenge.)
14722 - Fix a couple of hard-to-trigger autoconf problems that could result
14723 in really weird results on platforms whose sys/types.h files define
14724 nonstandard integer types.
14725 - Don't try to create the datadir when running --verify-config or
14726 --hash-password. Resolves bug 540.
14727 - If we were having problems getting a particular descriptor from the
14728 directory caches, and then we learned about a new descriptor for
14729 that router, we weren't resetting our failure count. Reported
14731 - Although we fixed bug 539 (where servers would send HTTP status 503
14732 responses _and_ send a body too), there are still servers out there
14733 that haven't upgraded. Therefore, make clients parse such bodies
14734 when they receive them.
14735 - Run correctly on systems where rlim_t is larger than unsigned long.
14736 This includes some 64-bit systems.
14737 - Run correctly on platforms (like some versions of OS X 10.5) where
14738 the real limit for number of open files is OPEN_FILES, not rlim_max
14739 from getrlimit(RLIMIT_NOFILES).
14740 - Avoid a spurious free on base64 failure.
14741 - Avoid segfaults on certain complex invocations of
14742 router_get_by_hexdigest().
14743 - Fix rare bug on REDIRECTSTREAM control command when called with no
14744 port set: it could erroneously report an error when none had
14748 Changes in version 0.2.0.15-alpha - 2007-12-25
14749 Tor 0.2.0.14-alpha and 0.2.0.15-alpha fix a bunch of bugs with the
14750 features added in 0.2.0.13-alpha.
14753 - Fix several remotely triggerable asserts based on DirPort requests
14754 for a v2 or v3 networkstatus object before we were prepared. This
14755 was particularly bad for 0.2.0.13 and later bridge relays, who
14756 would never have a v2 networkstatus and would thus always crash
14757 when used. Bugfixes on 0.2.0.x.
14758 - Estimate the v3 networkstatus size more accurately, rather than
14759 estimating it at zero bytes and giving it artificially high priority
14760 compared to other directory requests. Bugfix on 0.2.0.x.
14763 - Fix configure.in logic for cross-compilation.
14764 - When we load a bridge descriptor from the cache, and it was
14765 previously unreachable, mark it as retriable so we won't just
14766 ignore it. Also, try fetching a new copy immediately. Bugfixes
14768 - The bridge GeoIP stats were counting other relays, for example
14769 self-reachability and authority-reachability tests.
14772 - Support compilation to target iPhone; patch from cjacker huang.
14773 To build for iPhone, pass the --enable-iphone option to configure.
14776 Changes in version 0.2.0.14-alpha - 2007-12-23
14778 - Fix a crash on startup if you install Tor 0.2.0.13-alpha fresh
14779 without a datadirectory from a previous Tor install. Reported
14781 - Fix a crash when we fetch a descriptor that turns out to be
14782 unexpected (it used to be in our networkstatus when we started
14783 fetching it, but it isn't in our current networkstatus), and we
14784 aren't using bridges. Bugfix on 0.2.0.x.
14785 - Fix a crash when accessing hidden services: it would work the first
14786 time you use a given introduction point for your service, but
14787 on subsequent requests we'd be using garbage memory. Fixed by
14788 Karsten Loesing. Bugfix on 0.2.0.13-alpha.
14789 - Fix a crash when we load a bridge descriptor from disk but we don't
14790 currently have a Bridge line for it in our torrc. Bugfix on
14794 - If bridge authorities set BridgePassword, they will serve a
14795 snapshot of known bridge routerstatuses from their DirPort to
14796 anybody who knows that password. Unset by default.
14799 - Make the unit tests build again.
14800 - Make "GETINFO/desc-annotations/id/<OR digest>" actually work.
14801 - Make PublishServerDescriptor default to 1, so the default doesn't
14802 have to change as we invent new directory protocol versions.
14803 - Fix test for rlim_t on OSX 10.3: sys/resource.h doesn't want to
14804 be included unless sys/time.h is already included. Fixes
14805 bug 553. Bugfix on 0.2.0.x.
14806 - If we receive a general-purpose descriptor and then receive an
14807 identical bridge-purpose descriptor soon after, don't discard
14808 the next one as a duplicate.
14811 - If BridgeRelay is set to 1, then the default for
14812 PublishServerDescriptor is now "bridge" rather than "v2,v3".
14813 - If the user sets RelayBandwidthRate but doesn't set
14814 RelayBandwidthBurst, then make them equal rather than erroring out.
14817 Changes in version 0.2.0.13-alpha - 2007-12-21
14818 Tor 0.2.0.13-alpha adds a fourth v3 directory authority run by Geoff
14819 Goodell, fixes many more bugs, and adds a lot of infrastructure for
14822 o New directory authorities:
14823 - Set up lefkada (run by Geoff Goodell) as the fourth v3 directory
14827 - Only update guard status (usable / not usable) once we have
14828 enough directory information. This was causing us to always pick
14829 two new guards on startup (bugfix on 0.2.0.9-alpha), and it was
14830 causing us to discard all our guards on startup if we hadn't been
14831 running for a few weeks (bugfix on 0.1.2.x). Fixes bug 448.
14832 - Purge old entries from the "rephist" database and the hidden
14833 service descriptor databases even when DirPort is zero. Bugfix
14835 - We were ignoring our RelayBandwidthRate for the first 30 seconds
14836 after opening a circuit -- even a relayed circuit. Bugfix on
14838 - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
14839 requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
14840 crashing or mis-answering these types of requests.
14841 - Relays were publishing their server descriptor to v1 and v2
14842 directory authorities, but they didn't try publishing to v3-only
14843 authorities. Fix this; and also stop publishing to v1 authorities.
14845 - When we were reading router descriptors from cache, we were ignoring
14846 the annotations -- so for example we were reading in bridge-purpose
14847 descriptors as general-purpose descriptors. Bugfix on 0.2.0.8-alpha.
14848 - When we decided to send a 503 response to a request for servers, we
14849 were then also sending the server descriptors: this defeats the
14850 whole purpose. Fixes bug 539; bugfix on 0.1.2.x.
14853 - Bridge relays now behave like clients with respect to time
14854 intervals for downloading new consensus documents -- otherwise they
14855 stand out. Bridge users now wait until the end of the interval,
14856 so their bridge relay will be sure to have a new consensus document.
14857 - Three new config options (AlternateDirAuthority,
14858 AlternateBridgeAuthority, and AlternateHSAuthority) that let the
14859 user selectively replace the default directory authorities by type,
14860 rather than the all-or-nothing replacement that DirServer offers.
14861 - Tor can now be configured to read a GeoIP file from disk in one
14862 of two formats. This can be used by controllers to map IP addresses
14863 to countries. Eventually, it may support exit-by-country.
14864 - When possible, bridge relays remember which countries users
14865 are coming from, and report aggregate information in their
14866 extra-info documents, so that the bridge authorities can learn
14867 where Tor is blocked.
14868 - Bridge directory authorities now do reachability testing on the
14869 bridges they know. They provide router status summaries to the
14870 controller via "getinfo ns/purpose/bridge", and also dump summaries
14871 to a file periodically.
14872 - Stop fetching directory info so aggressively if your DirPort is
14873 on but your ORPort is off; stop fetching v2 dir info entirely.
14874 You can override these choices with the new FetchDirInfoEarly
14878 - The fix in 0.2.0.12-alpha cleared the "hsdir" flag in v3 network
14879 consensus documents when there are too many relays at a single
14880 IP address. Now clear it in v2 network status documents too, and
14881 also clear it in routerinfo_t when the relay is no longer listed
14882 in the relevant networkstatus document.
14883 - Don't crash if we get an unexpected value for the
14884 PublishServerDescriptor config option. Reported by Matt Edman;
14885 bugfix on 0.2.0.9-alpha.
14886 - Our new v2 hidden service descriptor format allows descriptors
14887 that have no introduction points. But Tor crashed when we tried
14888 to build a descriptor with no intro points (and it would have
14889 crashed if we had tried to parse one). Bugfix on 0.2.0.x; patch
14890 by Karsten Loesing.
14891 - Fix building with dmalloc 5.5.2 with glibc.
14892 - Reject uploaded descriptors and extrainfo documents if they're
14893 huge. Otherwise we'll cache them all over the network and it'll
14894 clog everything up. Reported by Aljosha Judmayer.
14895 - Check for presence of s6_addr16 and s6_addr32 fields in in6_addr
14896 via autoconf. Should fix compile on solaris. Bugfix on 0.2.0.x.
14897 - When the DANGEROUS_VERSION controller status event told us we're
14898 running an obsolete version, it used the string "OLD" to describe
14899 it. Yet the "getinfo" interface used the string "OBSOLETE". Now use
14900 "OBSOLETE" in both cases. Bugfix on 0.1.2.x.
14901 - If we can't expand our list of entry guards (e.g. because we're
14902 using bridges or we have StrictEntryNodes set), don't mark relays
14903 down when they fail a directory request. Otherwise we're too quick
14904 to mark all our entry points down. Bugfix on 0.1.2.x.
14905 - Fix handling of hex nicknames when answering controller requests for
14906 networkstatus by name, or when deciding whether to warn about unknown
14907 routers in a config option. Bugfix on 0.1.2.x. (Patch from mwenge.)
14908 - Fix a couple of hard-to-trigger autoconf problems that could result
14909 in really weird results on platforms whose sys/types.h files define
14910 nonstandard integer types. Bugfix on 0.1.2.x.
14911 - Fix compilation with --disable-threads set. Bugfix on 0.2.0.x.
14912 - Don't crash on name lookup when we have no current consensus. Fixes
14913 bug 538; bugfix on 0.2.0.x.
14914 - Only Tors that want to mirror the v2 directory info should
14915 create the "cached-status" directory in their datadir. (All Tors
14916 used to create it.) Bugfix on 0.2.0.9-alpha.
14917 - Directory authorities should only automatically download Extra Info
14918 documents if they're v1, v2, or v3 authorities. Bugfix on 0.1.2.x.
14921 - On the USR1 signal, when dmalloc is in use, log the top 10 memory
14922 consumers. (We already do this on HUP.)
14923 - Authorities and caches fetch the v2 networkstatus documents
14924 less often, now that v3 is encouraged.
14925 - Add a new config option BridgeRelay that specifies you want to
14926 be a bridge relay. Right now the only difference is that it makes
14927 you answer begin_dir requests, and it makes you cache dir info,
14928 even if your DirPort isn't on.
14929 - Add "GETINFO/desc-annotations/id/<OR digest>" so controllers can
14930 ask about source, timestamp of arrival, purpose, etc. We need
14931 something like this to help Vidalia not do GeoIP lookups on bridge
14933 - Allow multiple HashedControlPassword config lines, to support
14934 multiple controller passwords.
14935 - Authorities now decide whether they're authoritative for a given
14936 router based on the router's purpose.
14937 - New config options AuthDirBadDir and AuthDirListBadDirs for
14938 authorities to mark certain relays as "bad directories" in the
14939 networkstatus documents. Also supports the "!baddir" directive in
14940 the approved-routers file.
14943 Changes in version 0.2.0.12-alpha - 2007-11-16
14944 This twelfth development snapshot fixes some more build problems as
14945 well as a few minor bugs.
14948 - Make it build on OpenBSD again. Patch from tup.
14949 - Substitute BINDIR and LOCALSTATEDIR in scripts. Fixes
14950 package-building for Red Hat, OS X, etc.
14952 o Minor bugfixes (on 0.1.2.x):
14953 - Changing the ExitPolicyRejectPrivate setting should cause us to
14954 rebuild our server descriptor.
14956 o Minor bugfixes (on 0.2.0.x):
14957 - When we're lacking a consensus, don't try to perform rendezvous
14958 operations. Reported by Karsten Loesing.
14959 - Fix a small memory leak whenever we decide against using a
14960 newly picked entry guard. Reported by Mike Perry.
14961 - When authorities detected more than two relays running on the same
14962 IP address, they were clearing all the status flags but forgetting
14963 to clear the "hsdir" flag. So clients were being told that a
14964 given relay was the right choice for a v2 hsdir lookup, yet they
14965 never had its descriptor because it was marked as 'not running'
14967 - If we're trying to fetch a bridge descriptor and there's no way
14968 the bridge authority could help us (for example, we don't know
14969 a digest, or there is no bridge authority), don't be so eager to
14970 fall back to asking the bridge authority.
14971 - If we're using bridges or have strictentrynodes set, and our
14972 chosen exit is in the same family as all our bridges/entry guards,
14973 then be flexible about families.
14976 - When we negotiate a v2 link-layer connection (not yet implemented),
14977 accept RELAY_EARLY cells and turn them into RELAY cells if we've
14978 negotiated a v1 connection for their next step. Initial code for
14982 Changes in version 0.2.0.11-alpha - 2007-11-12
14983 This eleventh development snapshot fixes some build problems with
14984 the previous snapshot. It also includes a more secure-by-default exit
14985 policy for relays, fixes an enormous memory leak for exit relays, and
14986 fixes another bug where servers were falling out of the directory list.
14989 - Exit policies now reject connections that are addressed to a
14990 relay's public (external) IP address too, unless
14991 ExitPolicyRejectPrivate is turned off. We do this because too
14992 many relays are running nearby to services that trust them based
14993 on network address. Bugfix on 0.1.2.x.
14996 - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
14997 on every successful resolve. Reported by Mike Perry; bugfix
14999 - On authorities, never downgrade to old router descriptors simply
15000 because they're listed in the consensus. This created a catch-22
15001 where we wouldn't list a new descriptor because there was an
15002 old one in the consensus, and we couldn't get the new one in the
15003 consensus because we wouldn't list it. Possible fix for bug 548.
15004 Also, this might cause bug 543 to appear on authorities; if so,
15005 we'll need a band-aid for that. Bugfix on 0.2.0.9-alpha.
15007 o Packaging fixes on 0.2.0.10-alpha:
15008 - We were including instructions about what to do with the
15009 src/config/fallback-consensus file, but we weren't actually
15010 including it in the tarball. Disable all of that for now.
15013 - Allow people to say PreferTunnelledDirConns rather than
15014 PreferTunneledDirConns, for those alternate-spellers out there.
15017 - Don't reevaluate all the information from our consensus document
15018 just because we've downloaded a v2 networkstatus that we intend
15019 to cache. Fixes bug 545; bugfix on 0.2.0.x.
15022 Changes in version 0.2.0.10-alpha - 2007-11-10
15023 This tenth development snapshot adds a third v3 directory authority
15024 run by Mike Perry, adds most of Karsten Loesing's new hidden service
15025 descriptor format, fixes a bad crash bug and new bridge bugs introduced
15026 in 0.2.0.9-alpha, fixes many bugs with the v3 directory implementation,
15027 fixes some minor memory leaks in previous 0.2.0.x snapshots, and
15028 addresses many more minor issues.
15030 o New directory authorities:
15031 - Set up ides (run by Mike Perry) as the third v3 directory authority.
15034 - Allow tunnelled directory connections to ask for an encrypted
15035 "begin_dir" connection or an anonymized "uses a full Tor circuit"
15036 connection independently. Now we can make anonymized begin_dir
15037 connections for (e.g.) more secure hidden service posting and
15039 - More progress on proposal 114: code from Karsten Loesing to
15040 implement new hidden service descriptor format.
15041 - Raise the default BandwidthRate/BandwidthBurst to 5MB/10MB, to
15042 accommodate the growing number of servers that use the default
15043 and are reaching it.
15044 - Directory authorities use a new formula for selecting which nodes
15045 to advertise as Guards: they must be in the top 7/8 in terms of
15046 how long we have known about them, and above the median of those
15047 nodes in terms of weighted fractional uptime.
15048 - Make "not enough dir info yet" warnings describe *why* Tor feels
15049 it doesn't have enough directory info yet.
15052 - Stop servers from crashing if they set a Family option (or
15053 maybe in other situations too). Bugfix on 0.2.0.9-alpha; reported
15055 - Make bridge users work again -- the move to v3 directories in
15056 0.2.0.9-alpha had introduced a number of bugs that made bridges
15057 no longer work for clients.
15058 - When the clock jumps forward a lot, do not allow the bandwidth
15059 buckets to become negative. Bugfix on 0.1.2.x; fixes bug 544.
15061 o Major bugfixes (v3 dir, bugfixes on 0.2.0.9-alpha):
15062 - When the consensus lists a router descriptor that we previously were
15063 mirroring, but that we considered non-canonical, reload the
15064 descriptor as canonical. This fixes bug 543 where Tor servers
15065 would start complaining after a few days that they don't have
15066 enough directory information to build a circuit.
15067 - Consider replacing the current consensus when certificates arrive
15068 that make the pending consensus valid. Previously, we were only
15069 considering replacement when the new certs _didn't_ help.
15070 - Fix an assert error on startup if we didn't already have the
15071 consensus and certs cached in our datadirectory: we were caching
15072 the consensus in consensus_waiting_for_certs but then free'ing it
15074 - Avoid sending a request for "keys/fp" (for which we'll get a 400 Bad
15075 Request) if we need more v3 certs but we've already got pending
15076 requests for all of them.
15077 - Correctly back off from failing certificate downloads. Fixes
15079 - Authorities don't vote on the Running flag if they have been running
15080 for less than 30 minutes themselves. Fixes bug 547, where a newly
15081 started authority would vote that everyone was down.
15083 o New requirements:
15084 - Drop support for OpenSSL version 0.9.6. Just about nobody was using
15085 it, it had no AES, and it hasn't seen any security patches since
15089 - Clients now hold circuitless TLS connections open for 1.5 times
15090 MaxCircuitDirtiness (15 minutes), since it is likely that they'll
15091 rebuild a new circuit over them within that timeframe. Previously,
15092 they held them open only for KeepalivePeriod (5 minutes).
15093 - Use "If-Modified-Since" to avoid retrieving consensus
15094 networkstatuses that we already have.
15095 - When we have no consensus, check FallbackNetworkstatusFile (defaults
15096 to $PREFIX/share/tor/fallback-consensus) for a consensus. This way
15097 we start knowing some directory caches.
15098 - When we receive a consensus from the future, warn about skew.
15099 - Improve skew reporting: try to give the user a better log message
15100 about how skewed they are, and how much this matters.
15101 - When we have a certificate for an authority, believe that
15102 certificate's claims about the authority's IP address.
15103 - New --quiet command-line option to suppress the default console log.
15104 Good in combination with --hash-password.
15105 - Authorities send back an X-Descriptor-Not-New header in response to
15106 an accepted-but-discarded descriptor upload. Partially implements
15108 - Make the log message for "tls error. breaking." more useful.
15109 - Better log messages about certificate downloads, to attempt to
15110 track down the second incarnation of bug 546.
15112 o Minor features (bridges):
15113 - If bridge users set UpdateBridgesFromAuthority, but the digest
15114 they ask for is a 404 from the bridge authority, they now fall
15115 back to trying the bridge directly.
15116 - Bridges now use begin_dir to publish their server descriptor to
15117 the bridge authority, even when they haven't set TunnelDirConns.
15119 o Minor features (controller):
15120 - When reporting clock skew, and we know that the clock is _at least
15121 as skewed_ as some value, but we don't know the actual value,
15122 report the value as a "minimum skew."
15125 - Update linux-tor-prio.sh script to allow QoS based on the uid of
15126 the Tor process. Patch from Marco Bonetti with tweaks from Mike
15130 - Refuse to start if both ORPort and UseBridges are set. Bugfix
15131 on 0.2.0.x, suggested by Matt Edman.
15132 - Don't stop fetching descriptors when FetchUselessDescriptors is
15133 set, even if we stop asking for circuits. Bugfix on 0.1.2.x;
15134 reported by tup and ioerror.
15135 - Better log message on vote from unknown authority.
15136 - Don't log "Launching 0 request for 0 router" message.
15138 o Minor bugfixes (memory leaks):
15139 - Stop leaking memory every time we parse a v3 certificate. Bugfix
15141 - Stop leaking memory every time we load a v3 certificate. Bugfix
15142 on 0.2.0.1-alpha. Fixes bug 536.
15143 - Stop leaking a cached networkstatus on exit. Bugfix on
15145 - Stop leaking voter information every time we free a consensus.
15146 Bugfix on 0.2.0.3-alpha.
15147 - Stop leaking signed data every time we check a voter signature.
15148 Bugfix on 0.2.0.3-alpha.
15149 - Stop leaking a signature every time we fail to parse a consensus or
15150 a vote. Bugfix on 0.2.0.3-alpha.
15151 - Stop leaking v2_download_status_map on shutdown. Bugfix on
15153 - Stop leaking conn->nickname every time we make a connection to a
15154 Tor relay without knowing its expected identity digest (e.g. when
15155 using bridges). Bugfix on 0.2.0.3-alpha.
15157 - Minor bugfixes (portability):
15158 - Run correctly on platforms where rlim_t is larger than unsigned
15159 long, and/or where the real limit for number of open files is
15160 OPEN_FILES, not rlim_max from getrlimit(RLIMIT_NOFILES). In
15161 particular, these may be needed for OS X 10.5.
15164 Changes in version 0.1.2.18 - 2007-10-28
15165 Tor 0.1.2.18 fixes many problems including crash bugs, problems with
15166 hidden service introduction that were causing huge delays, and a big
15167 bug that was causing some servers to disappear from the network status
15168 lists for a few hours each day.
15170 o Major bugfixes (crashes):
15171 - If a connection is shut down abruptly because of something that
15172 happened inside connection_flushed_some(), do not call
15173 connection_finished_flushing(). Should fix bug 451:
15174 "connection_stop_writing: Assertion conn->write_event failed"
15175 Bugfix on 0.1.2.7-alpha.
15176 - Fix possible segfaults in functions called from
15177 rend_process_relay_cell().
15179 o Major bugfixes (hidden services):
15180 - Hidden services were choosing introduction points uniquely by
15181 hexdigest, but when constructing the hidden service descriptor
15182 they merely wrote the (potentially ambiguous) nickname.
15183 - Clients now use the v2 intro format for hidden service
15184 connections: they specify their chosen rendezvous point by identity
15185 digest rather than by (potentially ambiguous) nickname. These
15186 changes could speed up hidden service connections dramatically.
15188 o Major bugfixes (other):
15189 - Stop publishing a new server descriptor just because we get a
15190 HUP signal. This led (in a roundabout way) to some servers getting
15191 dropped from the networkstatus lists for a few hours each day.
15192 - When looking for a circuit to cannibalize, consider family as well
15193 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15194 circuit cannibalization).
15195 - When a router wasn't listed in a new networkstatus, we were leaving
15196 the flags for that router alone -- meaning it remained Named,
15197 Running, etc -- even though absence from the networkstatus means
15198 that it shouldn't be considered to exist at all anymore. Now we
15199 clear all the flags for routers that fall out of the networkstatus
15200 consensus. Fixes bug 529.
15203 - Don't try to access (or alter) the state file when running
15204 --list-fingerprint or --verify-config or --hash-password. Resolves
15206 - When generating information telling us how to extend to a given
15207 router, do not try to include the nickname if it is
15208 absent. Resolves bug 467.
15209 - Fix a user-triggerable segfault in expand_filename(). (There isn't
15210 a way to trigger this remotely.)
15211 - When sending a status event to the controller telling it that an
15212 OR address is reachable, set the port correctly. (Previously we
15213 were reporting the dir port.)
15214 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15215 command. Bugfix on 0.1.2.17.
15216 - When loading bandwidth history, do not believe any information in
15217 the future. Fixes bug 434.
15218 - When loading entry guard information, do not believe any information
15220 - When we have our clock set far in the future and generate an
15221 onion key, then re-set our clock to be correct, we should not stop
15222 the onion key from getting rotated.
15223 - On some platforms, accept() can return a broken address. Detect
15224 this more quietly, and deal accordingly. Fixes bug 483.
15225 - It's not actually an error to find a non-pending entry in the DNS
15226 cache when canceling a pending resolve. Don't log unless stuff
15227 is fishy. Resolves bug 463.
15228 - Don't reset trusted dir server list when we set a configuration
15229 option. Patch from Robert Hogan.
15230 - Don't try to create the datadir when running --verify-config or
15231 --hash-password. Resolves bug 540.
15234 Changes in version 0.2.0.9-alpha - 2007-10-24
15235 This ninth development snapshot switches clients to the new v3 directory
15236 system; allows servers to be listed in the network status even when they
15237 have the same nickname as a registered server; and fixes many other
15238 bugs including a big one that was causing some servers to disappear
15239 from the network status lists for a few hours each day.
15241 o Major features (directory system):
15242 - Clients now download v3 consensus networkstatus documents instead
15243 of v2 networkstatus documents. Clients and caches now base their
15244 opinions about routers on these consensus documents. Clients only
15245 download router descriptors listed in the consensus.
15246 - Authorities now list servers who have the same nickname as
15247 a different named server, but list them with a new flag,
15248 "Unnamed". Now we can list servers that happen to pick the same
15249 nickname as a server that registered two years ago and then
15250 disappeared. Partially implements proposal 122.
15251 - If the consensus lists a router as "Unnamed", the name is assigned
15252 to a different router: do not identify the router by that name.
15253 Partially implements proposal 122.
15254 - Authorities can now come to a consensus on which method to use to
15255 compute the consensus. This gives us forward compatibility.
15258 - Stop publishing a new server descriptor just because we HUP or
15259 when we find our DirPort to be reachable but won't actually publish
15260 it. New descriptors without any real changes are dropped by the
15261 authorities, and can screw up our "publish every 18 hours" schedule.
15263 - When a router wasn't listed in a new networkstatus, we were leaving
15264 the flags for that router alone -- meaning it remained Named,
15265 Running, etc -- even though absence from the networkstatus means
15266 that it shouldn't be considered to exist at all anymore. Now we
15267 clear all the flags for routers that fall out of the networkstatus
15268 consensus. Fixes bug 529; bugfix on 0.1.2.x.
15269 - Fix awful behavior in DownloadExtraInfo option where we'd fetch
15270 extrainfo documents and then discard them immediately for not
15271 matching the latest router. Bugfix on 0.2.0.1-alpha.
15273 o Minor features (v3 directory protocol):
15274 - Allow tor-gencert to generate a new certificate without replacing
15276 - Allow certificates to include an address.
15277 - When we change our directory-cache settings, reschedule all voting
15278 and download operations.
15279 - Reattempt certificate downloads immediately on failure, as long as
15280 we haven't failed a threshold number of times yet.
15281 - Delay retrying consensus downloads while we're downloading
15282 certificates to verify the one we just got. Also, count getting a
15283 consensus that we already have (or one that isn't valid) as a failure,
15284 and count failing to get the certificates after 20 minutes as a
15286 - Build circuits and download descriptors even if our consensus is a
15287 little expired. (This feature will go away once authorities are
15290 o Minor features (router descriptor cache):
15291 - If we find a cached-routers file that's been sitting around for more
15292 than 28 days unmodified, then most likely it's a leftover from
15293 when we upgraded to 0.2.0.8-alpha. Remove it. It has no good
15295 - When we (as a cache) download a descriptor because it was listed
15296 in a consensus, remember when the consensus was supposed to expire,
15297 and don't expire the descriptor until then.
15299 o Minor features (performance):
15300 - Call routerlist_remove_old_routers() much less often. This should
15301 speed startup, especially on directory caches.
15302 - Don't try to launch new descriptor downloads quite so often when we
15303 already have enough directory information to build circuits.
15304 - Base64 decoding was actually showing up on our profile when parsing
15305 the initial descriptor file; switch to an in-process all-at-once
15306 implementation that's about 3.5x times faster than calling out to
15309 o Minor features (compilation):
15310 - Detect non-ASCII platforms (if any still exist) and refuse to
15311 build there: some of our code assumes that 'A' is 65 and so on.
15313 o Minor bugfixes (v3 directory authorities, bugfixes on 0.2.0.x):
15314 - Make the "next period" votes into "current period" votes immediately
15315 after publishing the consensus; avoid a heisenbug that made them
15316 stick around indefinitely.
15317 - When we discard a vote as a duplicate, do not report this as
15319 - Treat missing v3 keys or certificates as an error when running as a
15320 v3 directory authority.
15321 - When we're configured to be a v3 authority, but we're only listed
15322 as a non-v3 authority in our DirServer line for ourself, correct
15324 - If an authority doesn't have a qualified hostname, just put
15325 its address in the vote. This fixes the problem where we referred to
15326 "moria on moria:9031."
15327 - Distinguish between detached signatures for the wrong period, and
15328 detached signatures for a divergent vote.
15329 - Fix a small memory leak when computing a consensus.
15330 - When there's no concensus, we were forming a vote every 30
15331 minutes, but writing the "valid-after" line in our vote based
15332 on our configured V3AuthVotingInterval: so unless the intervals
15333 matched up, we immediately rejected our own vote because it didn't
15334 start at the voting interval that caused us to construct a vote.
15336 o Minor bugfixes (v3 directory protocol, bugfixes on 0.2.0.x):
15337 - Delete unverified-consensus when the real consensus is set.
15338 - Consider retrying a consensus networkstatus fetch immediately
15339 after one fails: don't wait 60 seconds to notice.
15340 - When fetching a consensus as a cache, wait until a newer consensus
15341 should exist before trying to replace the current one.
15342 - Use a more forgiving schedule for retrying failed consensus
15343 downloads than for other types.
15345 o Minor bugfixes (other directory issues):
15346 - Correct the implementation of "download votes by digest." Bugfix on
15348 - Authorities no longer send back "400 you're unreachable please fix
15349 it" errors to Tor servers that aren't online all the time. We're
15350 supposed to tolerate these servers now. Bugfix on 0.1.2.x.
15352 o Minor bugfixes (controller):
15353 - Don't reset trusted dir server list when we set a configuration
15354 option. Patch from Robert Hogan; bugfix on 0.1.2.x.
15355 - Respond to INT and TERM SIGNAL commands before we execute the
15356 signal, in case the signal shuts us down. We had a patch in
15357 0.1.2.1-alpha that tried to do this by queueing the response on
15358 the connection's buffer before shutting down, but that really
15359 isn't the same thing at all. Bug located by Matt Edman.
15361 o Minor bugfixes (misc):
15362 - Correctly check for bad options to the "PublishServerDescriptor"
15363 config option. Bugfix on 0.2.0.1-alpha; reported by Matt Edman.
15364 - Stop leaking memory on failing case of base32_decode, and make
15365 it accept upper-case letters. Bugfixes on 0.2.0.7-alpha.
15366 - Don't try to download extrainfo documents when we're trying to
15367 fetch enough directory info to build a circuit: having enough
15368 info should get priority. Bugfix on 0.2.0.x.
15369 - Don't complain that "your server has not managed to confirm that its
15370 ports are reachable" if we haven't been able to build any circuits
15371 yet. Bug found by spending four hours without a v3 consensus. Bugfix
15373 - Detect the reason for failing to mmap a descriptor file we just
15374 wrote, and give a more useful log message. Fixes bug 533. Bugfix
15377 o Code simplifications and refactoring:
15378 - Remove support for the old bw_accounting file: we've been storing
15379 bandwidth accounting information in the state file since
15380 0.1.2.5-alpha. This may result in bandwidth accounting errors
15381 if you try to upgrade from 0.1.1.x or earlier, or if you try to
15382 downgrade to 0.1.1.x or earlier.
15383 - New convenience code to locate a file within the DataDirectory.
15384 - Move non-authority functionality out of dirvote.c.
15385 - Refactor the arguments for router_pick_{directory_|trusteddir}server
15386 so that they all take the same named flags.
15389 - Include the "tor-ctrl.sh" bash script by Stefan Behte to provide
15390 Unix users an easy way to script their Tor process (e.g. by
15391 adjusting bandwidth based on the time of the day).
15394 Changes in version 0.2.0.8-alpha - 2007-10-12
15395 This eighth development snapshot fixes a crash bug that's been bothering
15396 us since February 2007, lets bridge authorities store a list of bridge
15397 descriptors they've seen, gets v3 directory voting closer to working,
15398 starts caching v3 directory consensus documents on directory mirrors,
15399 and fixes a variety of smaller issues including some minor memory leaks.
15401 o Major features (router descriptor cache):
15402 - Store routers in a file called cached-descriptors instead of in
15403 cached-routers. Initialize cached-descriptors from cached-routers
15404 if the old format is around. The new format allows us to store
15405 annotations along with descriptors.
15406 - Use annotations to record the time we received each descriptor, its
15407 source, and its purpose.
15408 - Disable the SETROUTERPURPOSE controller command: it is now
15410 - Controllers should now specify cache=no or cache=yes when using
15411 the +POSTDESCRIPTOR command.
15412 - Bridge authorities now write bridge descriptors to disk, meaning
15413 we can export them to other programs and begin distributing them
15416 o Major features (directory authorities):
15417 - When a v3 authority is missing votes or signatures, it now tries
15419 - Directory authorities track weighted fractional uptime as well as
15420 weighted mean-time-between failures. WFU is suitable for deciding
15421 whether a node is "usually up", while MTBF is suitable for deciding
15422 whether a node is "likely to stay up." We need both, because
15423 "usually up" is a good requirement for guards, while "likely to
15424 stay up" is a good requirement for long-lived connections.
15426 o Major features (v3 directory system):
15427 - Caches now download v3 network status documents as needed,
15428 and download the descriptors listed in them.
15429 - All hosts now attempt to download and keep fresh v3 authority
15430 certificates, and re-attempt after failures.
15431 - More internal-consistency checks for vote parsing.
15433 o Major bugfixes (crashes):
15434 - If a connection is shut down abruptly because of something that
15435 happened inside connection_flushed_some(), do not call
15436 connection_finished_flushing(). Should fix bug 451. Bugfix on
15439 o Major bugfixes (performance):
15440 - Fix really bad O(n^2) performance when parsing a long list of
15441 routers: Instead of searching the entire list for an "extra-info "
15442 string which usually wasn't there, once for every routerinfo
15443 we read, just scan lines forward until we find one we like.
15445 - When we add data to a write buffer in response to the data on that
15446 write buffer getting low because of a flush, do not consider the
15447 newly added data as a candidate for immediate flushing, but rather
15448 make it wait until the next round of writing. Otherwise, we flush
15449 and refill recursively, and a single greedy TLS connection can
15450 eat all of our bandwidth. Bugfix on 0.1.2.7-alpha.
15452 o Minor features (v3 authority system):
15453 - Add more ways for tools to download the votes that lead to the
15455 - Send a 503 when low on bandwidth and a vote, consensus, or
15456 certificate is requested.
15457 - If-modified-since is now implemented properly for all kinds of
15458 certificate requests.
15460 o Minor bugfixes (network statuses):
15461 - Tweak the implementation of proposal 109 slightly: allow at most
15462 two Tor servers on the same IP address, except if it's the location
15463 of a directory authority, in which case allow five. Bugfix on
15466 o Minor bugfixes (controller):
15467 - When sending a status event to the controller telling it that an
15468 OR address is reachable, set the port correctly. (Previously we
15469 were reporting the dir port.) Bugfix on 0.1.2.x.
15471 o Minor bugfixes (v3 directory system):
15472 - Fix logic to look up a cert by its signing key digest. Bugfix on
15474 - Only change the reply to a vote to "OK" if it's not already
15475 set. This gets rid of annoying "400 OK" log messages, which may
15476 have been masking some deeper issue. Bugfix on 0.2.0.7-alpha.
15477 - When we get a valid consensus, recompute the voting schedule.
15478 - Base the valid-after time of a vote on the consensus voting
15479 schedule, not on our preferred schedule.
15480 - Make the return values and messages from signature uploads and
15481 downloads more sensible.
15482 - Fix a memory leak when serving votes and consensus documents, and
15483 another when serving certificates.
15485 o Minor bugfixes (performance):
15486 - Use a slightly simpler string hashing algorithm (copying Python's
15487 instead of Java's) and optimize our digest hashing algorithm to take
15488 advantage of 64-bit platforms and to remove some possibly-costly
15490 - Fix a minor memory leak whenever we parse guards from our state
15491 file. Bugfix on 0.2.0.7-alpha.
15492 - Fix a minor memory leak whenever we write out a file. Bugfix on
15494 - Fix a minor memory leak whenever a controller sends the PROTOCOLINFO
15495 command. Bugfix on 0.2.0.5-alpha.
15497 o Minor bugfixes (portability):
15498 - On some platforms, accept() can return a broken address. Detect
15499 this more quietly, and deal accordingly. Fixes bug 483.
15500 - Stop calling tor_strlower() on uninitialized memory in some cases.
15501 Bugfix in 0.2.0.7-alpha.
15503 o Minor bugfixes (usability):
15504 - Treat some 403 responses from directory servers as INFO rather than
15505 WARN-severity events.
15506 - It's not actually an error to find a non-pending entry in the DNS
15507 cache when canceling a pending resolve. Don't log unless stuff is
15508 fishy. Resolves bug 463.
15510 o Minor bugfixes (anonymity):
15511 - Never report that we've used more bandwidth than we're willing to
15512 relay: it leaks how much non-relay traffic we're using. Resolves
15514 - When looking for a circuit to cannibalize, consider family as well
15515 as identity. Fixes bug 438. Bugfix on 0.1.0.x (which introduced
15516 circuit cannibalization).
15518 o Code simplifications and refactoring:
15519 - Make a bunch of functions static. Remove some dead code.
15520 - Pull out about a third of the really big routerlist.c; put it in a
15521 new module, networkstatus.c.
15522 - Merge the extra fields in local_routerstatus_t back into
15523 routerstatus_t: we used to need one routerstatus_t for each
15524 authority's opinion, plus a local_routerstatus_t for the locally
15525 computed consensus opinion. To save space, we put the locally
15526 modified fields into local_routerstatus_t, and only the common
15527 stuff into routerstatus_t. But once v3 directories are in use,
15528 clients and caches will no longer need to hold authority opinions;
15529 thus, the rationale for keeping the types separate is now gone.
15530 - Make the code used to reschedule and reattempt downloads more
15532 - Turn all 'Are we a directory server/mirror?' logic into a call to
15534 - Remove the code to generate the oldest (v1) directory format.
15535 The code has been disabled since 0.2.0.5-alpha.
15538 Changes in version 0.2.0.7-alpha - 2007-09-21
15539 This seventh development snapshot makes bridges work again, makes bridge
15540 authorities work for the first time, fixes two huge performance flaws
15541 in hidden services, and fixes a variety of minor issues.
15543 o New directory authorities:
15544 - Set up moria1 and tor26 as the first v3 directory authorities. See
15545 doc/spec/dir-spec.txt for details on the new directory design.
15547 o Major bugfixes (crashes):
15548 - Fix possible segfaults in functions called from
15549 rend_process_relay_cell(). Bugfix on 0.1.2.x.
15551 o Major bugfixes (bridges):
15552 - Fix a bug that made servers send a "404 Not found" in response to
15553 attempts to fetch their server descriptor. This caused Tor servers
15554 to take many minutes to establish reachability for their DirPort,
15555 and it totally crippled bridges. Bugfix on 0.2.0.5-alpha.
15556 - Make "UpdateBridgesFromAuthority" torrc option work: when bridge
15557 users configure that and specify a bridge with an identity
15558 fingerprint, now they will lookup the bridge descriptor at the
15559 default bridge authority via a one-hop tunnel, but once circuits
15560 are established they will switch to a three-hop tunnel for later
15561 connections to the bridge authority. Bugfix in 0.2.0.3-alpha.
15563 o Major bugfixes (hidden services):
15564 - Hidden services were choosing introduction points uniquely by
15565 hexdigest, but when constructing the hidden service descriptor
15566 they merely wrote the (potentially ambiguous) nickname.
15567 - Clients now use the v2 intro format for hidden service
15568 connections: they specify their chosen rendezvous point by identity
15569 digest rather than by (potentially ambiguous) nickname. Both
15570 are bugfixes on 0.1.2.x, and they could speed up hidden service
15571 connections dramatically. Thanks to Karsten Loesing.
15573 o Minor features (security):
15574 - As a client, do not believe any server that tells us that an
15575 address maps to an internal address space.
15576 - Make it possible to enable HashedControlPassword and
15577 CookieAuthentication at the same time.
15579 o Minor features (guard nodes):
15580 - Tag every guard node in our state file with the version that
15581 we believe added it, or with our own version if we add it. This way,
15582 if a user temporarily runs an old version of Tor and then switches
15583 back to a new one, she doesn't automatically lose her guards.
15585 o Minor features (speed):
15586 - When implementing AES counter mode, update only the portions of the
15587 counter buffer that need to change, and don't keep separate
15588 network-order and host-order counters when they are the same (i.e.,
15589 on big-endian hosts.)
15591 o Minor features (controller):
15592 - Accept LF instead of CRLF on controller, since some software has a
15593 hard time generating real Internet newlines.
15594 - Add GETINFO values for the server status events
15595 "REACHABILITY_SUCCEEDED" and "GOOD_SERVER_DESCRIPTOR". Patch from
15598 o Removed features:
15599 - Routers no longer include bandwidth-history lines in their
15600 descriptors; this information is already available in extra-info
15601 documents, and including it in router descriptors took up 60%
15602 (!) of compressed router descriptor downloads. Completes
15603 implementation of proposal 104.
15604 - Remove the contrib scripts ExerciseServer.py, PathDemo.py,
15605 and TorControl.py, as they use the old v0 controller protocol,
15606 and are obsoleted by TorFlow anyway.
15607 - Drop support for v1 rendezvous descriptors, since we never used
15608 them anyway, and the code has probably rotted by now. Based on
15609 patch from Karsten Loesing.
15610 - On OSX, stop warning the user that kqueue support in libevent is
15611 "experimental", since it seems to have worked fine for ages.
15614 - When generating information telling us how to extend to a given
15615 router, do not try to include the nickname if it is absent. Fixes
15616 bug 467. Bugfix on 0.2.0.3-alpha.
15617 - Fix a user-triggerable (but not remotely-triggerable) segfault
15618 in expand_filename(). Bugfix on 0.1.2.x.
15619 - Fix a memory leak when freeing incomplete requests from DNSPort.
15620 Found by Niels Provos with valgrind. Bugfix on 0.2.0.1-alpha.
15621 - Don't try to access (or alter) the state file when running
15622 --list-fingerprint or --verify-config or --hash-password. (Resolves
15623 bug 499.) Bugfix on 0.1.2.x.
15624 - Servers used to decline to publish their DirPort if their
15625 BandwidthRate, RelayBandwidthRate, or MaxAdvertisedBandwidth
15626 were below a threshold. Now they only look at BandwidthRate and
15627 RelayBandwidthRate. Bugfix on 0.1.2.x.
15628 - Remove an optimization in the AES counter-mode code that assumed
15629 that the counter never exceeded 2^68. When the counter can be set
15630 arbitrarily as an IV (as it is by Karsten's new hidden services
15631 code), this assumption no longer holds. Bugfix on 0.1.2.x.
15632 - Resume listing "AUTHORITY" flag for authorities in network status.
15633 Bugfix on 0.2.0.3-alpha; reported by Alex de Joode.
15635 o Code simplifications and refactoring:
15636 - Revamp file-writing logic so we don't need to have the entire
15637 contents of a file in memory at once before we write to disk. Tor,
15639 - Turn "descriptor store" into a full-fledged type.
15640 - Move all NT services code into a separate source file.
15641 - Unify all code that computes medians, percentile elements, etc.
15642 - Get rid of a needless malloc when parsing address policies.
15645 Changes in version 0.1.2.17 - 2007-08-30
15646 Tor 0.1.2.17 features a new Vidalia version in the Windows and OS
15647 X bundles. Vidalia 0.0.14 makes authentication required for the
15648 ControlPort in the default configuration, which addresses important
15649 security risks. Everybody who uses Vidalia (or another controller)
15652 In addition, this Tor update fixes major load balancing problems with
15653 path selection, which should speed things up a lot once many people
15656 o Major bugfixes (security):
15657 - We removed support for the old (v0) control protocol. It has been
15658 deprecated since Tor 0.1.1.1-alpha, and keeping it secure has
15659 become more of a headache than it's worth.
15661 o Major bugfixes (load balancing):
15662 - When choosing nodes for non-guard positions, weight guards
15663 proportionally less, since they already have enough load. Patch
15665 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15666 will allow fast Tor servers to get more attention.
15667 - When we're upgrading from an old Tor version, forget our current
15668 guards and pick new ones according to the new weightings. These
15669 three load balancing patches could raise effective network capacity
15670 by a factor of four. Thanks to Mike Perry for measurements.
15672 o Major bugfixes (stream expiration):
15673 - Expire not-yet-successful application streams in all cases if
15674 they've been around longer than SocksTimeout. Right now there are
15675 some cases where the stream will live forever, demanding a new
15676 circuit every 15 seconds. Fixes bug 454; reported by lodger.
15678 o Minor features (controller):
15679 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15680 is valid before any authentication has been received. It tells
15681 a controller what kind of authentication is expected, and what
15682 protocol is spoken. Implements proposal 119.
15684 o Minor bugfixes (performance):
15685 - Save on most routerlist_assert_ok() calls in routerlist.c, thus
15686 greatly speeding up loading cached-routers from disk on startup.
15687 - Disable sentinel-based debugging for buffer code: we squashed all
15688 the bugs that this was supposed to detect a long time ago, and now
15689 its only effect is to change our buffer sizes from nice powers of
15690 two (which platform mallocs tend to like) to values slightly over
15691 powers of two (which make some platform mallocs sad).
15693 o Minor bugfixes (misc):
15694 - If exit bandwidth ever exceeds one third of total bandwidth, then
15695 use the correct formula to weight exit nodes when choosing paths.
15696 Based on patch from Mike Perry.
15697 - Choose perfectly fairly among routers when choosing by bandwidth and
15698 weighting by fraction of bandwidth provided by exits. Previously, we
15699 would choose with only approximate fairness, and correct ourselves
15700 if we ran off the end of the list.
15701 - If we require CookieAuthentication but we fail to write the
15702 cookie file, we would warn but not exit, and end up in a state
15703 where no controller could authenticate. Now we exit.
15704 - If we require CookieAuthentication, stop generating a new cookie
15705 every time we change any piece of our config.
15706 - Refuse to start with certain directory authority keys, and
15707 encourage people using them to stop.
15708 - Terminate multi-line control events properly. Original patch
15710 - Fix a minor memory leak when we fail to find enough suitable
15711 servers to choose a circuit.
15712 - Stop leaking part of the descriptor when we run into a particularly
15713 unparseable piece of it.
15716 Changes in version 0.2.0.6-alpha - 2007-08-26
15717 This sixth development snapshot features a new Vidalia version in the
15718 Windows and OS X bundles. Vidalia 0.0.14 makes authentication required for
15719 the ControlPort in the default configuration, which addresses important
15722 In addition, this snapshot fixes major load balancing problems
15723 with path selection, which should speed things up a lot once many
15724 people have upgraded. The directory authorities also use a new
15725 mean-time-between-failure approach to tracking which servers are stable,
15726 rather than just looking at the most recent uptime.
15728 o New directory authorities:
15729 - Set up Tonga as the default bridge directory authority.
15732 - Directory authorities now track servers by weighted
15733 mean-times-between-failures. When we have 4 or more days of data,
15734 use measured MTBF rather than declared uptime to decide whether
15735 to call a router Stable. Implements proposal 108.
15737 o Major bugfixes (load balancing):
15738 - When choosing nodes for non-guard positions, weight guards
15739 proportionally less, since they already have enough load. Patch
15741 - Raise the "max believable bandwidth" from 1.5MB/s to 10MB/s. This
15742 will allow fast Tor servers to get more attention.
15743 - When we're upgrading from an old Tor version, forget our current
15744 guards and pick new ones according to the new weightings. These
15745 three load balancing patches could raise effective network capacity
15746 by a factor of four. Thanks to Mike Perry for measurements.
15748 o Major bugfixes (descriptor parsing):
15749 - Handle unexpected whitespace better in malformed descriptors. Bug
15750 found using Benedikt Boss's new Tor fuzzer! Bugfix on 0.2.0.x.
15753 - There is now an ugly, temporary "desc/all-recent-extrainfo-hack"
15754 GETINFO for Torstat to use until it can switch to using extrainfos.
15755 - Optionally (if built with -DEXPORTMALLINFO) export the output
15756 of mallinfo via http, as tor/mallinfo.txt. Only accessible
15760 - Do not intermix bridge routers with controller-added
15761 routers. (Bugfix on 0.2.0.x)
15762 - Do not fail with an assert when accept() returns an unexpected
15763 address family. Addresses but does not wholly fix bug 483. (Bugfix
15765 - Let directory authorities startup even when they can't generate
15766 a descriptor immediately, e.g. because they don't know their
15768 - Stop putting the authentication cookie in a file called "0"
15769 in your working directory if you don't specify anything for the
15770 new CookieAuthFile option. Reported by Matt Edman.
15771 - Make it possible to read the PROTOCOLINFO response in a way that
15772 conforms to our control-spec. Reported by Matt Edman.
15773 - Fix a minor memory leak when we fail to find enough suitable
15774 servers to choose a circuit. Bugfix on 0.1.2.x.
15775 - Stop leaking part of the descriptor when we run into a particularly
15776 unparseable piece of it. Bugfix on 0.1.2.x.
15777 - Unmap the extrainfo cache file on exit.
15780 Changes in version 0.2.0.5-alpha - 2007-08-19
15781 This fifth development snapshot fixes compilation on Windows again;
15782 fixes an obnoxious client-side bug that slowed things down and put
15783 extra load on the network; gets us closer to using the v3 directory
15784 voting scheme; makes it easier for Tor controllers to use cookie-based
15785 authentication; and fixes a variety of other bugs.
15787 o Removed features:
15788 - Version 1 directories are no longer generated in full. Instead,
15789 authorities generate and serve "stub" v1 directories that list
15790 no servers. This will stop Tor versions 0.1.0.x and earlier from
15791 working, but (for security reasons) nobody should be running those
15794 o Major bugfixes (compilation, 0.2.0.x):
15795 - Try to fix Win32 compilation again: improve checking for IPv6 types.
15796 - Try to fix MSVC compilation: build correctly on platforms that do
15797 not define s6_addr16 or s6_addr32.
15798 - Fix compile on platforms without getaddrinfo: bug found by Li-Hui
15801 o Major bugfixes (stream expiration):
15802 - Expire not-yet-successful application streams in all cases if
15803 they've been around longer than SocksTimeout. Right now there are
15804 some cases where the stream will live forever, demanding a new
15805 circuit every 15 seconds. Bugfix on 0.1.2.7-alpha; fixes bug 454;
15806 reported by lodger.
15808 o Minor features (directory servers):
15809 - When somebody requests a list of statuses or servers, and we have
15810 none of those, return a 404 rather than an empty 200.
15812 o Minor features (directory voting):
15813 - Store v3 consensus status consensuses on disk, and reload them
15816 o Minor features (security):
15817 - Warn about unsafe ControlPort configurations.
15818 - Refuse to start with certain directory authority keys, and
15819 encourage people using them to stop.
15821 o Minor features (controller):
15822 - Add a PROTOCOLINFO controller command. Like AUTHENTICATE, it
15823 is valid before any authentication has been received. It tells
15824 a controller what kind of authentication is expected, and what
15825 protocol is spoken. Implements proposal 119.
15826 - New config option CookieAuthFile to choose a new location for the
15827 cookie authentication file, and config option
15828 CookieAuthFileGroupReadable to make it group-readable.
15830 o Minor features (unit testing):
15831 - Add command-line arguments to unit-test executable so that we can
15832 invoke any chosen test from the command line rather than having
15833 to run the whole test suite at once; and so that we can turn on
15834 logging for the unit tests.
15836 o Minor bugfixes (on 0.1.2.x):
15837 - If we require CookieAuthentication but we fail to write the
15838 cookie file, we would warn but not exit, and end up in a state
15839 where no controller could authenticate. Now we exit.
15840 - If we require CookieAuthentication, stop generating a new cookie
15841 every time we change any piece of our config.
15842 - When loading bandwidth history, do not believe any information in
15843 the future. Fixes bug 434.
15844 - When loading entry guard information, do not believe any information
15846 - When we have our clock set far in the future and generate an
15847 onion key, then re-set our clock to be correct, we should not stop
15848 the onion key from getting rotated.
15849 - Clean up torrc sample config file.
15850 - Do not automatically run configure from autogen.sh. This
15851 non-standard behavior tended to annoy people who have built other
15854 o Minor bugfixes (on 0.2.0.x):
15855 - Fix a bug with AutomapHostsOnResolve that would always cause
15856 the second request to fail. Bug reported by Kate. Bugfix on
15858 - Fix a bug in ADDRMAP controller replies that would sometimes
15859 try to print a NULL. Patch from tup.
15860 - Read v3 directory authority keys from the right location.
15861 - Numerous bugfixes to directory voting code.
15864 Changes in version 0.1.2.16 - 2007-08-01
15865 Tor 0.1.2.16 fixes a critical security vulnerability that allows a
15866 remote attacker in certain situations to rewrite the user's torrc
15867 configuration file. This can completely compromise anonymity of users
15868 in most configurations, including those running the Vidalia bundles,
15869 TorK, etc. Or worse.
15871 o Major security fixes:
15872 - Close immediately after missing authentication on control port;
15873 do not allow multiple authentication attempts.
15876 Changes in version 0.2.0.4-alpha - 2007-08-01
15877 This fourth development snapshot fixes a critical security vulnerability
15878 for most users, specifically those running Vidalia, TorK, etc. Everybody
15879 should upgrade to either 0.1.2.16 or 0.2.0.4-alpha.
15881 o Major security fixes:
15882 - Close immediately after missing authentication on control port;
15883 do not allow multiple authentication attempts.
15885 o Major bugfixes (compilation):
15886 - Fix win32 compilation: apparently IN_ADDR and IN6_ADDR are already
15889 o Minor features (performance):
15890 - Be even more aggressive about releasing RAM from small
15891 empty buffers. Thanks to our free-list code, this shouldn't be too
15892 performance-intensive.
15893 - Disable sentinel-based debugging for buffer code: we squashed all
15894 the bugs that this was supposed to detect a long time ago, and
15895 now its only effect is to change our buffer sizes from nice
15896 powers of two (which platform mallocs tend to like) to values
15897 slightly over powers of two (which make some platform mallocs sad).
15898 - Log malloc statistics from mallinfo() on platforms where it
15902 Changes in version 0.2.0.3-alpha - 2007-07-29
15903 This third development snapshot introduces new experimental
15904 blocking-resistance features and a preliminary version of the v3
15905 directory voting design, and includes many other smaller features
15909 - The first pieces of our "bridge" design for blocking-resistance
15910 are implemented. People can run bridge directory authorities;
15911 people can run bridges; and people can configure their Tor clients
15912 with a set of bridges to use as the first hop into the Tor network.
15913 See http://archives.seul.org/or/talk/Jul-2007/msg00249.html for
15915 - Create listener connections before we setuid to the configured
15916 User and Group. Now non-Windows users can choose port values
15917 under 1024, start Tor as root, and have Tor bind those ports
15918 before it changes to another UID. (Windows users could already
15920 - Added a new ConstrainedSockets config option to set SO_SNDBUF and
15921 SO_RCVBUF on TCP sockets. Hopefully useful for Tor servers running
15922 on "vserver" accounts. (Patch from coderman.)
15923 - Be even more aggressive about separating local traffic from relayed
15924 traffic when RelayBandwidthRate is set. (Refines proposal 111.)
15926 o Major features (experimental):
15927 - First cut of code for "v3 dir voting": directory authorities will
15928 vote on a common network status document rather than each publishing
15929 their own opinion. This code needs more testing and more corner-case
15930 handling before it's ready for use.
15933 - Directory authorities now call routers Fast if their bandwidth is
15934 at least 100KB/s, and consider their bandwidth adequate to be a
15935 Guard if it is at least 250KB/s, no matter the medians. This fix
15936 complements proposal 107. [Bugfix on 0.1.2.x]
15937 - Directory authorities now never mark more than 3 servers per IP as
15938 Valid and Running. (Implements proposal 109, by Kevin Bauer and
15940 - Minor change to organizationName and commonName generation
15941 procedures in TLS certificates during Tor handshakes, to invalidate
15942 some earlier censorware approaches. This is not a long-term
15943 solution, but applying it will give us a bit of time to look into
15944 the epidemiology of countermeasures as they spread.
15946 o Major bugfixes (directory):
15947 - Rewrite directory tokenization code to never run off the end of
15948 a string. Fixes bug 455. Patch from croup. [Bugfix on 0.1.2.x]
15950 o Minor features (controller):
15951 - Add a SOURCE_ADDR field to STREAM NEW events so that controllers can
15952 match requests to applications. (Patch from Robert Hogan.)
15953 - Report address and port correctly on connections to DNSPort. (Patch
15954 from Robert Hogan.)
15955 - Add a RESOLVE command to launch hostname lookups. (Original patch
15956 from Robert Hogan.)
15957 - Add GETINFO status/enough-dir-info to let controllers tell whether
15958 Tor has downloaded sufficient directory information. (Patch
15960 - You can now use the ControlSocket option to tell Tor to listen for
15961 controller connections on Unix domain sockets on systems that
15962 support them. (Patch from Peter Palfrader.)
15963 - STREAM NEW events are generated for DNSPort requests and for
15964 tunneled directory connections. (Patch from Robert Hogan.)
15965 - New "GETINFO address-mappings/*" command to get address mappings
15966 with expiry information. "addr-mappings/*" is now deprecated.
15969 o Minor features (misc):
15970 - Merge in some (as-yet-unused) IPv6 address manipulation code. (Patch
15972 - The tor-gencert tool for v3 directory authorities now creates all
15973 files as readable to the file creator only, and write-protects
15974 the authority identity key.
15975 - When dumping memory usage, list bytes used in buffer memory
15977 - When running with dmalloc, dump more stats on hup and on exit.
15978 - Directory authorities now fail quickly and (relatively) harmlessly
15979 if they generate a network status document that is somehow
15982 o Traffic load balancing improvements:
15983 - If exit bandwidth ever exceeds one third of total bandwidth, then
15984 use the correct formula to weight exit nodes when choosing paths.
15985 (Based on patch from Mike Perry.)
15986 - Choose perfectly fairly among routers when choosing by bandwidth and
15987 weighting by fraction of bandwidth provided by exits. Previously, we
15988 would choose with only approximate fairness, and correct ourselves
15989 if we ran off the end of the list. [Bugfix on 0.1.2.x]
15991 o Performance improvements:
15992 - Be more aggressive with freeing buffer RAM or putting it on the
15994 - Use Critical Sections rather than Mutexes for synchronizing threads
15995 on win32; Mutexes are heavier-weight, and designed for synchronizing
15998 o Deprecated and removed features:
15999 - RedirectExits is now deprecated.
16000 - Stop allowing address masks that do not correspond to bit prefixes.
16001 We have warned about these for a really long time; now it's time
16002 to reject them. (Patch from croup.)
16004 o Minor bugfixes (directory):
16005 - Fix another crash bug related to extra-info caching. (Bug found by
16006 Peter Palfrader.) [Bugfix on 0.2.0.2-alpha]
16007 - Directories no longer return a "304 not modified" when they don't
16008 have the networkstatus the client asked for. Also fix a memory
16009 leak when returning 304 not modified. [Bugfixes on 0.2.0.2-alpha]
16010 - We had accidentally labelled 0.1.2.x directory servers as not
16011 suitable for begin_dir requests, and had labelled no directory
16012 servers as suitable for uploading extra-info documents. [Bugfix
16015 o Minor bugfixes (dns):
16016 - Fix a crash when DNSPort is set more than once. (Patch from Robert
16017 Hogan.) [Bugfix on 0.2.0.2-alpha]
16018 - Add DNSPort connections to the global connection list, so that we
16019 can time them out correctly. (Bug found by Robert Hogan.) [Bugfix
16021 - Fix a dangling reference that could lead to a crash when DNSPort is
16022 changed or closed (Patch from Robert Hogan.) [Bugfix on
16025 o Minor bugfixes (controller):
16026 - Provide DNS expiry times in GMT, not in local time. For backward
16027 compatibility, ADDRMAP events only provide GMT expiry in an extended
16028 field. "GETINFO address-mappings" always does the right thing.
16029 - Use CRLF line endings properly in NS events.
16030 - Terminate multi-line control events properly. (Original patch
16031 from tup.) [Bugfix on 0.1.2.x-alpha]
16032 - Do not include spaces in SOURCE_ADDR fields in STREAM
16033 events. Resolves bug 472. [Bugfix on 0.2.0.x-alpha]
16036 Changes in version 0.1.2.15 - 2007-07-17
16037 Tor 0.1.2.15 fixes several crash bugs, fixes some anonymity-related
16038 problems, fixes compilation on BSD, and fixes a variety of other
16039 bugs. Everybody should upgrade.
16041 o Major bugfixes (compilation):
16042 - Fix compile on FreeBSD/NetBSD/OpenBSD. Oops.
16044 o Major bugfixes (crashes):
16045 - Try even harder not to dereference the first character after
16046 an mmap(). Reported by lodger.
16047 - Fix a crash bug in directory authorities when we re-number the
16048 routerlist while inserting a new router.
16049 - When the cached-routers file is an even multiple of the page size,
16050 don't run off the end and crash. (Fixes bug 455; based on idea
16052 - Fix eventdns.c behavior on Solaris: It is critical to include
16053 orconfig.h _before_ sys/types.h, so that we can get the expected
16054 definition of _FILE_OFFSET_BITS.
16056 o Major bugfixes (security):
16057 - Fix a possible buffer overrun when using BSD natd support. Bug
16059 - When sending destroy cells from a circuit's origin, don't include
16060 the reason for tearing down the circuit. The spec says we didn't,
16061 and now we actually don't. Reported by lodger.
16062 - Keep streamids from different exits on a circuit separate. This
16063 bug may have allowed other routers on a given circuit to inject
16064 cells into streams. Reported by lodger; fixes bug 446.
16065 - If there's a never-before-connected-to guard node in our list,
16066 never choose any guards past it. This way we don't expand our
16067 guard list unless we need to.
16069 o Minor bugfixes (guard nodes):
16070 - Weight guard selection by bandwidth, so that low-bandwidth nodes
16071 don't get overused as guards.
16073 o Minor bugfixes (directory):
16074 - Correctly count the number of authorities that recommend each
16075 version. Previously, we were under-counting by 1.
16076 - Fix a potential crash bug when we load many server descriptors at
16077 once and some of them make others of them obsolete. Fixes bug 458.
16079 o Minor bugfixes (hidden services):
16080 - Stop tearing down the whole circuit when the user asks for a
16081 connection to a port that the hidden service didn't configure.
16084 o Minor bugfixes (misc):
16085 - On Windows, we were preventing other processes from reading
16086 cached-routers while Tor was running. Reported by janbar.
16087 - Fix a possible (but very unlikely) bug in picking routers by
16088 bandwidth. Add a log message to confirm that it is in fact
16089 unlikely. Patch from lodger.
16090 - Backport a couple of memory leak fixes.
16091 - Backport miscellaneous cosmetic bugfixes.
16094 Changes in version 0.2.0.2-alpha - 2007-06-02
16095 o Major bugfixes on 0.2.0.1-alpha:
16096 - Fix an assertion failure related to servers without extra-info digests.
16097 Resolves bugs 441 and 442.
16099 o Minor features (directory):
16100 - Support "If-Modified-Since" when answering HTTP requests for
16101 directories, running-routers documents, and network-status documents.
16102 (There's no need to support it for router descriptors, since those
16103 are downloaded by descriptor digest.)
16105 o Minor build issues:
16106 - Clear up some MIPSPro compiler warnings.
16107 - When building from a tarball on a machine that happens to have SVK
16108 installed, report the micro-revision as whatever version existed
16109 in the tarball, not as "x".
16112 Changes in version 0.2.0.1-alpha - 2007-06-01
16113 This early development snapshot provides new features for people running
16114 Tor as both a client and a server (check out the new RelayBandwidth
16115 config options); lets Tor run as a DNS proxy; and generally moves us
16116 forward on a lot of fronts.
16118 o Major features, server usability:
16119 - New config options RelayBandwidthRate and RelayBandwidthBurst:
16120 a separate set of token buckets for relayed traffic. Right now
16121 relayed traffic is defined as answers to directory requests, and
16122 OR connections that don't have any local circuits on them.
16124 o Major features, client usability:
16125 - A client-side DNS proxy feature to replace the need for
16126 dns-proxy-tor: Just set "DNSPort 9999", and Tor will now listen
16127 for DNS requests on port 9999, use the Tor network to resolve them
16128 anonymously, and send the reply back like a regular DNS server.
16129 The code still only implements a subset of DNS.
16130 - Make PreferTunneledDirConns and TunnelDirConns work even when
16131 we have no cached directory info. This means Tor clients can now
16132 do all of their connections protected by TLS.
16134 o Major features, performance and efficiency:
16135 - Directory authorities accept and serve "extra info" documents for
16136 routers. These documents contain fields from router descriptors
16137 that aren't usually needed, and that use a lot of excess
16138 bandwidth. Once these fields are removed from router descriptors,
16139 the bandwidth savings should be about 60%. [Partially implements
16141 - Servers upload extra-info documents to any authority that accepts
16142 them. Authorities (and caches that have been configured to download
16143 extra-info documents) download them as needed. [Partially implements
16145 - Change the way that Tor buffers data that it is waiting to write.
16146 Instead of queueing data cells in an enormous ring buffer for each
16147 client->OR or OR->OR connection, we now queue cells on a separate
16148 queue for each circuit. This lets us use less slack memory, and
16149 will eventually let us be smarter about prioritizing different kinds
16151 - Use memory pools to allocate cells with better speed and memory
16152 efficiency, especially on platforms where malloc() is inefficient.
16153 - Stop reading on edge connections when their corresponding circuit
16154 buffers are full; start again as the circuits empty out.
16156 o Major features, other:
16157 - Add an HSAuthorityRecordStats option that hidden service authorities
16158 can use to track statistics of overall hidden service usage without
16159 logging information that would be very useful to an attacker.
16160 - Start work implementing multi-level keys for directory authorities:
16161 Add a standalone tool to generate key certificates. (Proposal 103.)
16164 - Directory authorities now call routers Stable if they have an
16165 uptime of at least 30 days, even if that's not the median uptime
16166 in the network. Implements proposal 107, suggested by Kevin Bauer
16169 o Minor fixes (resource management):
16170 - Count the number of open sockets separately from the number
16171 of active connection_t objects. This will let us avoid underusing
16172 our allocated connection limit.
16173 - We no longer use socket pairs to link an edge connection to an
16174 anonymous directory connection or a DirPort test connection.
16175 Instead, we track the link internally and transfer the data
16176 in-process. This saves two sockets per "linked" connection (at the
16177 client and at the server), and avoids the nasty Windows socketpair()
16179 - Keep unused 4k and 16k buffers on free lists, rather than wasting 8k
16180 for every single inactive connection_t. Free items from the
16181 4k/16k-buffer free lists when they haven't been used for a while.
16183 o Minor features (build):
16184 - Make autoconf search for libevent, openssl, and zlib consistently.
16185 - Update deprecated macros in configure.in.
16186 - When warning about missing headers, tell the user to let us
16187 know if the compile succeeds anyway, so we can downgrade the
16189 - Include the current subversion revision as part of the version
16190 string: either fetch it directly if we're in an SVN checkout, do
16191 some magic to guess it if we're in an SVK checkout, or use
16192 the last-detected version if we're building from a .tar.gz.
16193 Use this version consistently in log messages.
16195 o Minor features (logging):
16196 - Always prepend "Bug: " to any log message about a bug.
16197 - Put a platform string (e.g. "Linux i686") in the startup log
16198 message, so when people paste just their logs, we know if it's
16199 OpenBSD or Windows or what.
16200 - When logging memory usage, break down memory used in buffers by
16203 o Minor features (directory system):
16204 - New config option V2AuthoritativeDirectory that all directory
16205 authorities should set. This will let future authorities choose
16206 not to serve V2 directory information.
16207 - Directory authorities allow multiple router descriptors and/or extra
16208 info documents to be uploaded in a single go. This will make
16209 implementing proposal 104 simpler.
16211 o Minor features (controller):
16212 - Add a new config option __DisablePredictedCircuits designed for
16213 use by the controller, when we don't want Tor to build any circuits
16215 - Let the controller specify HOP=%d as an argument to ATTACHSTREAM,
16216 so we can exit from the middle of the circuit.
16217 - Implement "getinfo status/circuit-established".
16218 - Implement "getinfo status/version/..." so a controller can tell
16219 whether the current version is recommended, and whether any versions
16220 are good, and how many authorities agree. (Patch from shibz.)
16222 o Minor features (hidden services):
16223 - Allow multiple HiddenServicePort directives with the same virtual
16224 port; when they occur, the user is sent round-robin to one
16225 of the target ports chosen at random. Partially fixes bug 393 by
16226 adding limited ad-hoc round-robining.
16228 o Minor features (other):
16230 - Add a new AutomapHostsOnResolve option: when it is enabled, any
16231 resolve request for hosts matching a given pattern causes Tor to
16232 generate an internal virtual address mapping for that host. This
16233 allows DNSPort to work sensibly with hidden service users. By
16234 default, .exit and .onion addresses are remapped; the list of
16235 patterns can be reconfigured with AutomapHostsSuffixes.
16236 - Add an "-F" option to tor-resolve to force a resolve for a .onion
16237 address. Thanks to the AutomapHostsOnResolve option, this is no
16238 longer a completely silly thing to do.
16239 - If Tor is invoked from something that isn't a shell (e.g. Vidalia),
16240 now we expand "-f ~/.tor/torrc" correctly. Suggested by Matt Edman.
16241 - Treat "2gb" when given in torrc for a bandwidth as meaning 2gb,
16242 minus 1 byte: the actual maximum declared bandwidth.
16244 o Removed features:
16245 - Removed support for the old binary "version 0" controller protocol.
16246 This has been deprecated since 0.1.1, and warnings have been issued
16247 since 0.1.2. When we encounter a v0 control message, we now send
16248 back an error and close the connection.
16249 - Remove the old "dns worker" server DNS code: it hasn't been default
16250 since 0.1.2.2-alpha, and all the servers seem to be using the new
16253 o Minor bugfixes (portability):
16254 - Even though Windows is equally happy with / and \ as path separators,
16255 try to use \ consistently on Windows and / consistently on Unix: it
16256 makes the log messages nicer.
16257 - Correctly report platform name on Windows 95 OSR2 and Windows 98 SE.
16258 - Read resolv.conf files correctly on platforms where read() returns
16259 partial results on small file reads.
16261 o Minor bugfixes (directory):
16262 - Correctly enforce that elements of directory objects do not appear
16263 more often than they are allowed to appear.
16264 - When we are reporting the DirServer line we just parsed, we were
16265 logging the second stanza of the key fingerprint, not the first.
16267 o Minor bugfixes (logging):
16268 - When we hit an EOF on a log (probably because we're shutting down),
16269 don't try to remove the log from the list: just mark it as
16270 unusable. (Bulletproofs against bug 222.)
16272 o Minor bugfixes (other):
16273 - In the exitlist script, only consider the most recently published
16274 server descriptor for each server. Also, when the user requests
16275 a list of servers that _reject_ connections to a given address,
16276 explicitly exclude the IPs that also have servers that accept
16277 connections to that address. (Resolves bug 405.)
16278 - Stop allowing hibernating servers to be "stable" or "fast".
16279 - On Windows, we were preventing other processes from reading
16280 cached-routers while Tor was running. (Reported by janbar)
16281 - Make the NodeFamilies config option work. (Reported by
16282 lodger -- it has never actually worked, even though we added it
16284 - Check return values from pthread_mutex functions.
16285 - Don't save non-general-purpose router descriptors to the disk cache,
16286 because we have no way of remembering what their purpose was when
16288 - Add even more asserts to hunt down bug 417.
16289 - Build without verbose warnings even on (not-yet-released) gcc 4.2.
16290 - Fix a possible (but very unlikely) bug in picking routers by bandwidth.
16291 Add a log message to confirm that it is in fact unlikely.
16293 o Minor bugfixes (controller):
16294 - Make 'getinfo fingerprint' return a 551 error if we're not a
16295 server, so we match what the control spec claims we do. Reported
16297 - Fix a typo in an error message when extendcircuit fails that
16298 caused us to not follow the \r\n-based delimiter protocol. Reported
16301 o Code simplifications and refactoring:
16302 - Stop passing around circuit_t and crypt_path_t pointers that are
16303 implicit in other procedure arguments.
16304 - Drop the old code to choke directory connections when the
16305 corresponding OR connections got full: thanks to the cell queue
16306 feature, OR conns don't get full any more.
16307 - Make dns_resolve() handle attaching connections to circuits
16308 properly, so the caller doesn't have to.
16309 - Rename wants_to_read and wants_to_write to read/write_blocked_on_bw.
16310 - Keep the connection array as a dynamic smartlist_t, rather than as
16311 a fixed-sized array. This is important, as the number of connections
16312 is becoming increasingly decoupled from the number of sockets.
16315 Changes in version 0.1.2.14 - 2007-05-25
16316 Tor 0.1.2.14 changes the addresses of two directory authorities (this
16317 change especially affects those who serve or use hidden services),
16318 and fixes several other crash- and security-related bugs.
16320 o Directory authority changes:
16321 - Two directory authorities (moria1 and moria2) just moved to new
16322 IP addresses. This change will particularly affect those who serve
16323 or use hidden services.
16325 o Major bugfixes (crashes):
16326 - If a directory server runs out of space in the connection table
16327 as it's processing a begin_dir request, it will free the exit stream
16328 but leave it attached to the circuit, leading to unpredictable
16329 behavior. (Reported by seeess, fixes bug 425.)
16330 - Fix a bug in dirserv_remove_invalid() that would cause authorities
16331 to corrupt memory under some really unlikely scenarios.
16332 - Tighten router parsing rules. (Bugs reported by Benedikt Boss.)
16333 - Avoid segfaults when reading from mmaped descriptor file. (Reported
16336 o Major bugfixes (security):
16337 - When choosing an entry guard for a circuit, avoid using guards
16338 that are in the same family as the chosen exit -- not just guards
16339 that are exactly the chosen exit. (Reported by lodger.)
16341 o Major bugfixes (resource management):
16342 - If a directory authority is down, skip it when deciding where to get
16343 networkstatus objects or descriptors. Otherwise we keep asking
16344 every 10 seconds forever. Fixes bug 384.
16345 - Count it as a failure if we fetch a valid network-status but we
16346 don't want to keep it. Otherwise we'll keep fetching it and keep
16347 not wanting to keep it. Fixes part of bug 422.
16348 - If all of our dirservers have given us bad or no networkstatuses
16349 lately, then stop hammering them once per minute even when we
16350 think they're failed. Fixes another part of bug 422.
16353 - Actually set the purpose correctly for descriptors inserted with
16354 purpose=controller.
16355 - When we have k non-v2 authorities in our DirServer config,
16356 we ignored the last k authorities in the list when updating our
16358 - Correctly back-off from requesting router descriptors that we are
16359 having a hard time downloading.
16360 - Read resolv.conf files correctly on platforms where read() returns
16361 partial results on small file reads.
16362 - Don't rebuild the entire router store every time we get 32K of
16363 routers: rebuild it when the journal gets very large, or when
16364 the gaps in the store get very large.
16367 - When routers publish SVN revisions in their router descriptors,
16368 authorities now include those versions correctly in networkstatus
16370 - Warn when using a version of libevent before 1.3b to run a server on
16371 OSX or BSD: these versions interact badly with userspace threads.
16374 Changes in version 0.1.2.13 - 2007-04-24
16375 This release features some major anonymity fixes, such as safer path
16376 selection; better client performance; faster bootstrapping, better
16377 address detection, and better DNS support for servers; write limiting as
16378 well as read limiting to make servers easier to run; and a huge pile of
16379 other features and bug fixes. The bundles also ship with Vidalia 0.0.11.
16381 Tor 0.1.2.13 is released in memory of Rob Levin (1955-2006), aka lilo
16382 of the Freenode IRC network, remembering his patience and vision for
16383 free speech on the Internet.
16386 - Fix a memory leak when we ask for "all" networkstatuses and we
16387 get one we don't recognize.
16388 - Add more asserts to hunt down bug 417.
16389 - Disable kqueue on OS X 10.3 and earlier, to fix bug 371.
16392 Changes in version 0.1.2.12-rc - 2007-03-16
16394 - Fix an infinite loop introduced in 0.1.2.7-alpha when we serve
16395 directory information requested inside Tor connections (i.e. via
16396 begin_dir cells). It only triggered when the same connection was
16397 serving other data at the same time. Reported by seeess.
16400 - When creating a circuit via the controller, send a 'launched'
16401 event when we're done, so we follow the spec better.
16404 Changes in version 0.1.2.11-rc - 2007-03-15
16405 o Minor bugfixes (controller), reported by daejees:
16406 - Correct the control spec to match how the code actually responds
16407 to 'getinfo addr-mappings/*'.
16408 - The control spec described a GUARDS event, but the code
16409 implemented a GUARD event. Standardize on GUARD, but let people
16410 ask for GUARDS too.
16413 Changes in version 0.1.2.10-rc - 2007-03-07
16414 o Major bugfixes (Windows):
16415 - Do not load the NT services library functions (which may not exist)
16416 just to detect if we're a service trying to shut down. Now we run
16417 on Win98 and friends again.
16419 o Minor bugfixes (other):
16420 - Clarify a couple of log messages.
16421 - Fix a misleading socks5 error number.
16424 Changes in version 0.1.2.9-rc - 2007-03-02
16425 o Major bugfixes (Windows):
16426 - On MinGW, use "%I64u" to printf/scanf 64-bit integers, instead
16427 of the usual GCC "%llu". This prevents a bug when saving 64-bit
16428 int configuration values: the high-order 32 bits would get
16429 truncated. In particular, we were being bitten by the default
16430 MaxAdvertisedBandwidth of 128 TB turning into 0. (Fixes bug 400
16431 and maybe also bug 397.)
16433 o Minor bugfixes (performance):
16434 - Use OpenSSL's AES implementation on platforms where it's faster.
16435 This could save us as much as 10% CPU usage.
16437 o Minor bugfixes (server):
16438 - Do not rotate onion key immediately after setting it for the first
16441 o Minor bugfixes (directory authorities):
16442 - Stop calling servers that have been hibernating for a long time
16443 "stable". Also, stop letting hibernating or obsolete servers affect
16444 uptime and bandwidth cutoffs.
16445 - Stop listing hibernating servers in the v1 directory.
16447 o Minor bugfixes (hidden services):
16448 - Upload hidden service descriptors slightly less often, to reduce
16449 load on authorities.
16451 o Minor bugfixes (other):
16452 - Fix an assert that could trigger if a controller quickly set then
16453 cleared EntryNodes. Bug found by Udo van den Heuvel.
16454 - On architectures where sizeof(int)>4, still clamp declarable bandwidth
16456 - Fix a potential race condition in the rpm installer. Found by
16458 - Try to fix eventdns warnings once and for all: do not treat a dns rcode
16459 of 2 as indicating that the server is completely bad; it sometimes
16460 means that the server is just bad for the request in question. (may fix
16461 the last of bug 326.)
16462 - Disable encrypted directory connections when we don't have a server
16463 descriptor for the destination. We'll get this working again in
16467 Changes in version 0.1.2.8-beta - 2007-02-26
16468 o Major bugfixes (crashes):
16469 - Stop crashing when the controller asks us to resetconf more than
16470 one config option at once. (Vidalia 0.0.11 does this.)
16471 - Fix a crash that happened on Win98 when we're given command-line
16472 arguments: don't try to load NT service functions from advapi32.dll
16473 except when we need them. (Bug introduced in 0.1.2.7-alpha;
16475 - Fix a longstanding obscure crash bug that could occur when
16476 we run out of DNS worker processes. (Resolves bug 390.)
16478 o Major bugfixes (hidden services):
16479 - Correctly detect whether hidden service descriptor downloads are
16480 in-progress. (Suggested by Karsten Loesing; fixes bug 399.)
16482 o Major bugfixes (accounting):
16483 - When we start during an accounting interval before it's time to wake
16484 up, remember to wake up at the correct time. (May fix bug 342.)
16486 o Minor bugfixes (controller):
16487 - Give the controller END_STREAM_REASON_DESTROY events _before_ we
16488 clear the corresponding on_circuit variable, and remember later
16489 that we don't need to send a redundant CLOSED event. Resolves part
16491 - Report events where a resolve succeeded or where we got a socks
16492 protocol error correctly, rather than calling both of them
16494 - Change reported stream target addresses to IP consistently when
16495 we finally get the IP from an exit node.
16496 - Send log messages to the controller even if they happen to be very
16499 o Minor bugfixes (other):
16500 - Display correct results when reporting which versions are
16501 recommended, and how recommended they are. (Resolves bug 383.)
16502 - Improve our estimates for directory bandwidth to be less random:
16503 guess that an unrecognized directory will have the average bandwidth
16504 from all known directories, not that it will have the average
16505 bandwidth from those directories earlier than it on the list.
16506 - If we start a server with ClientOnly 1, then set ClientOnly to 0
16507 and hup, stop triggering an assert based on an empty onion_key.
16508 - On platforms with no working mmap() equivalent, don't warn the
16509 user when cached-routers doesn't exist.
16510 - Warn the user when mmap() [or its equivalent] fails for some reason
16511 other than file-not-found.
16512 - Don't warn the user when cached-routers.new doesn't exist: that's
16513 perfectly fine when starting up for the first time.
16514 - When EntryNodes are configured, rebuild the guard list to contain,
16515 in order: the EntryNodes that were guards before; the rest of the
16516 EntryNodes; the nodes that were guards before.
16517 - Mask out all signals in sub-threads; only the libevent signal
16518 handler should be processing them. This should prevent some crashes
16519 on some machines using pthreads. (Patch from coderman.)
16520 - Fix switched arguments on memset in the implementation of
16521 tor_munmap() for systems with no mmap() call.
16522 - When Tor receives a router descriptor that it asked for, but
16523 no longer wants (because it has received fresh networkstatuses
16524 in the meantime), do not warn the user. Cache the descriptor if
16525 we're a cache; drop it if we aren't.
16526 - Make earlier entry guards _really_ get retried when the network
16528 - On a malformed DNS reply, always give an error to the corresponding
16530 - Build with recent libevents on platforms that do not define the
16531 nonstandard types "u_int8_t" and friends.
16533 o Minor features (controller):
16534 - Warn the user when an application uses the obsolete binary v0
16535 control protocol. We're planning to remove support for it during
16536 the next development series, so it's good to give people some
16538 - Add STREAM_BW events to report per-entry-stream bandwidth
16539 use. (Patch from Robert Hogan.)
16540 - Rate-limit SIGNEWNYM signals in response to controllers that
16541 impolitely generate them for every single stream. (Patch from
16542 mwenge; closes bug 394.)
16543 - Make REMAP stream events have a SOURCE (cache or exit), and
16544 make them generated in every case where we get a successful
16545 connected or resolved cell.
16547 o Minor bugfixes (performance):
16548 - Call router_have_min_dir_info half as often. (This is showing up in
16549 some profiles, but not others.)
16550 - When using GCC, make log_debug never get called at all, and its
16551 arguments never get evaluated, when no debug logs are configured.
16552 (This is showing up in some profiles, but not others.)
16555 - Remove some never-implemented options. Mark PathlenCoinWeight as
16557 - Implement proposal 106: Stop requiring clients to have well-formed
16558 certificates; stop checking nicknames in certificates. (Clients
16559 have certificates so that they can look like Tor servers, but in
16560 the future we might want to allow them to look like regular TLS
16561 clients instead. Nicknames in certificates serve no purpose other
16562 than making our protocol easier to recognize on the wire.)
16563 - Revise messages on handshake failure again to be even more clear about
16564 which are incoming connections and which are outgoing.
16565 - Discard any v1 directory info that's over 1 month old (for
16566 directories) or over 1 week old (for running-routers lists).
16567 - Do not warn when individual nodes in the configuration's EntryNodes,
16568 ExitNodes, etc are down: warn only when all possible nodes
16569 are down. (Fixes bug 348.)
16570 - Always remove expired routers and networkstatus docs before checking
16571 whether we have enough information to build circuits. (Fixes
16573 - Put a lower-bound on MaxAdvertisedBandwidth.
16576 Changes in version 0.1.2.7-alpha - 2007-02-06
16577 o Major bugfixes (rate limiting):
16578 - Servers decline directory requests much more aggressively when
16579 they're low on bandwidth. Otherwise they end up queueing more and
16580 more directory responses, which can't be good for latency.
16581 - But never refuse directory requests from local addresses.
16582 - Fix a memory leak when sending a 503 response for a networkstatus
16584 - Be willing to read or write on local connections (e.g. controller
16585 connections) even when the global rate limiting buckets are empty.
16586 - If our system clock jumps back in time, don't publish a negative
16587 uptime in the descriptor. Also, don't let the global rate limiting
16588 buckets go absurdly negative.
16589 - Flush local controller connection buffers periodically as we're
16590 writing to them, so we avoid queueing 4+ megabytes of data before
16593 o Major bugfixes (NT services):
16594 - Install as NT_AUTHORITY\LocalService rather than as SYSTEM; add a
16595 command-line flag so that admins can override the default by saying
16596 "tor --service install --user "SomeUser"". This will not affect
16597 existing installed services. Also, warn the user that the service
16598 will look for its configuration file in the service user's
16599 %appdata% directory. (We can't do the 'hardwire the user's appdata
16600 directory' trick any more, since we may not have read access to that
16603 o Major bugfixes (other):
16604 - Previously, we would cache up to 16 old networkstatus documents
16605 indefinitely, if they came from nontrusted authorities. Now we
16606 discard them if they are more than 10 days old.
16607 - Fix a crash bug in the presence of DNS hijacking (reported by Andrew
16609 - Detect and reject malformed DNS responses containing circular
16611 - If exits are rare enough that we're not marking exits as guards,
16612 ignore exit bandwidth when we're deciding the required bandwidth
16614 - When we're handling a directory connection tunneled over Tor,
16615 don't fill up internal memory buffers with all the data we want
16616 to tunnel; instead, only add it if the OR connection that will
16617 eventually receive it has some room for it. (This can lead to
16618 slowdowns in tunneled dir connections; a better solution will have
16619 to wait for 0.2.0.)
16621 o Minor bugfixes (dns):
16622 - Add some defensive programming to eventdns.c in an attempt to catch
16623 possible memory-stomping bugs.
16624 - Detect and reject DNS replies containing IPv4 or IPv6 records with
16625 an incorrect number of bytes. (Previously, we would ignore the
16627 - Fix as-yet-unused reverse IPv6 lookup code so it sends nybbles
16628 in the correct order, and doesn't crash.
16629 - Free memory held in recently-completed DNS lookup attempts on exit.
16630 This was not a memory leak, but may have been hiding memory leaks.
16631 - Handle TTL values correctly on reverse DNS lookups.
16632 - Treat failure to parse resolv.conf as an error.
16634 o Minor bugfixes (other):
16635 - Fix crash with "tor --list-fingerprint" (reported by seeess).
16636 - When computing clock skew from directory HTTP headers, consider what
16637 time it was when we finished asking for the directory, not what
16639 - Expire socks connections if they spend too long waiting for the
16640 handshake to finish. Previously we would let them sit around for
16641 days, if the connecting application didn't close them either.
16642 - And if the socks handshake hasn't started, don't send a
16643 "DNS resolve socks failed" handshake reply; just close it.
16644 - Stop using C functions that OpenBSD's linker doesn't like.
16645 - Don't launch requests for descriptors unless we have networkstatuses
16646 from at least half of the authorities. This delays the first
16647 download slightly under pathological circumstances, but can prevent
16648 us from downloading a bunch of descriptors we don't need.
16649 - Do not log IPs with TLS failures for incoming TLS
16650 connections. (Fixes bug 382.)
16651 - If the user asks to use invalid exit nodes, be willing to use
16653 - Stop using the reserved ac_cv namespace in our configure script.
16654 - Call stat() slightly less often; use fstat() when possible.
16655 - Refactor the way we handle pending circuits when an OR connection
16656 completes or fails, in an attempt to fix a rare crash bug.
16657 - Only rewrite a conn's address based on X-Forwarded-For: headers
16658 if it's a parseable public IP address; and stop adding extra quotes
16659 to the resulting address.
16662 - Weight directory requests by advertised bandwidth. Now we can
16663 let servers enable write limiting but still allow most clients to
16664 succeed at their directory requests. (We still ignore weights when
16665 choosing a directory authority; I hope this is a feature.)
16668 - Create a new file ReleaseNotes which was the old ChangeLog. The
16669 new ChangeLog file now includes the summaries for all development
16671 - Check for addresses with invalid characters at the exit as well
16672 as at the client, and warn less verbosely when they fail. You can
16673 override this by setting ServerDNSAllowNonRFC953Addresses to 1.
16674 - Adapt a patch from goodell to let the contrib/exitlist script
16675 take arguments rather than require direct editing.
16676 - Inform the server operator when we decide not to advertise a
16677 DirPort due to AccountingMax enabled or a low BandwidthRate. It
16678 was confusing Zax, so now we're hopefully more helpful.
16679 - Bring us one step closer to being able to establish an encrypted
16680 directory tunnel without knowing a descriptor first. Still not
16681 ready yet. As part of the change, now assume we can use a
16682 create_fast cell if we don't know anything about a router.
16683 - Allow exit nodes to use nameservers running on ports other than 53.
16684 - Servers now cache reverse DNS replies.
16685 - Add an --ignore-missing-torrc command-line option so that we can
16686 get the "use sensible defaults if the configuration file doesn't
16687 exist" behavior even when specifying a torrc location on the command
16690 o Minor features (controller):
16691 - Track reasons for OR connection failure; make these reasons
16692 available via the controller interface. (Patch from Mike Perry.)
16693 - Add a SOCKS_BAD_HOSTNAME client status event so controllers
16694 can learn when clients are sending malformed hostnames to Tor.
16695 - Clean up documentation for controller status events.
16696 - Add a REMAP status to stream events to note that a stream's
16697 address has changed because of a cached address or a MapAddress
16701 Changes in version 0.1.2.6-alpha - 2007-01-09
16703 - Fix an assert error introduced in 0.1.2.5-alpha: if a single TLS
16704 connection handles more than 4 gigs in either direction, we crash.
16705 - Fix an assert error introduced in 0.1.2.5-alpha: if we're an
16706 advertised exit node, somebody might try to exit from us when
16707 we're bootstrapping and before we've built our descriptor yet.
16708 Refuse the connection rather than crashing.
16711 - Warn if we (as a server) find that we've resolved an address that we
16712 weren't planning to resolve.
16713 - Warn that using select() on any libevent version before 1.1 will be
16714 unnecessarily slow (even for select()).
16715 - Flush ERR-level controller status events just like we currently
16716 flush ERR-level log events, so that a Tor shutdown doesn't prevent
16717 the controller from learning about current events.
16719 o Minor features (more controller status events):
16720 - Implement EXTERNAL_ADDRESS server status event so controllers can
16721 learn when our address changes.
16722 - Implement BAD_SERVER_DESCRIPTOR server status event so controllers
16723 can learn when directories reject our descriptor.
16724 - Implement SOCKS_UNKNOWN_PROTOCOL client status event so controllers
16725 can learn when a client application is speaking a non-socks protocol
16727 - Implement DANGEROUS_SOCKS client status event so controllers
16728 can learn when a client application is leaking DNS addresses.
16729 - Implement BUG general status event so controllers can learn when
16730 Tor is unhappy about its internal invariants.
16731 - Implement CLOCK_SKEW general status event so controllers can learn
16732 when Tor thinks the system clock is set incorrectly.
16733 - Implement GOOD_SERVER_DESCRIPTOR and ACCEPTED_SERVER_DESCRIPTOR
16734 server status events so controllers can learn when their descriptors
16735 are accepted by a directory.
16736 - Implement CHECKING_REACHABILITY and REACHABILITY_{SUCCEEDED|FAILED}
16737 server status events so controllers can learn about Tor's progress in
16738 deciding whether it's reachable from the outside.
16739 - Implement BAD_LIBEVENT general status event so controllers can learn
16740 when we have a version/method combination in libevent that needs to
16742 - Implement NAMESERVER_STATUS, NAMESERVER_ALL_DOWN, DNS_HIJACKED,
16743 and DNS_USELESS server status events so controllers can learn
16744 about changes to DNS server status.
16746 o Minor features (directory):
16747 - Authorities no longer recommend exits as guards if this would shift
16748 too much load to the exit nodes.
16751 Changes in version 0.1.2.5-alpha - 2007-01-06
16753 - Enable write limiting as well as read limiting. Now we sacrifice
16754 capacity if we're pushing out lots of directory traffic, rather
16755 than overrunning the user's intended bandwidth limits.
16756 - Include TLS overhead when counting bandwidth usage; previously, we
16757 would count only the bytes sent over TLS, but not the bytes used
16759 - Support running the Tor service with a torrc not in the same
16760 directory as tor.exe and default to using the torrc located in
16761 the %appdata%\Tor\ of the user who installed the service. Patch
16763 - Servers now check for the case when common DNS requests are going to
16764 wildcarded addresses (i.e. all getting the same answer), and change
16765 their exit policy to reject *:* if it's happening.
16766 - Implement BEGIN_DIR cells, so we can connect to the directory
16767 server via TLS to do encrypted directory requests rather than
16768 plaintext. Enable via the TunnelDirConns and PreferTunneledDirConns
16769 config options if you like.
16771 o Minor features (config and docs):
16772 - Start using the state file to store bandwidth accounting data:
16773 the bw_accounting file is now obsolete. We'll keep generating it
16774 for a while for people who are still using 0.1.2.4-alpha.
16775 - Try to batch changes to the state file so that we do as few
16776 disk writes as possible while still storing important things in
16778 - The state file and the bw_accounting file get saved less often when
16779 the AvoidDiskWrites config option is set.
16780 - Make PIDFile work on Windows (untested).
16781 - Add internal descriptions for a bunch of configuration options:
16782 accessible via controller interface and in comments in saved
16784 - Reject *:563 (NNTPS) in the default exit policy. We already reject
16785 NNTP by default, so this seems like a sensible addition.
16786 - Clients now reject hostnames with invalid characters. This should
16787 avoid some inadvertent info leaks. Add an option
16788 AllowNonRFC953Hostnames to disable this behavior, in case somebody
16789 is running a private network with hosts called @, !, and #.
16790 - Add a maintainer script to tell us which options are missing
16791 documentation: "make check-docs".
16792 - Add a new address-spec.txt document to describe our special-case
16793 addresses: .exit, .onion, and .noconnnect.
16795 o Minor features (DNS):
16796 - Ongoing work on eventdns infrastructure: now it has dns server
16797 and ipv6 support. One day Tor will make use of it.
16798 - Add client-side caching for reverse DNS lookups.
16799 - Add support to tor-resolve tool for reverse lookups and SOCKS5.
16800 - When we change nameservers or IP addresses, reset and re-launch
16801 our tests for DNS hijacking.
16803 o Minor features (directory):
16804 - Authorities now specify server versions in networkstatus. This adds
16805 about 2% to the size of compressed networkstatus docs, and allows
16806 clients to tell which servers support BEGIN_DIR and which don't.
16807 The implementation is forward-compatible with a proposed future
16808 protocol version scheme not tied to Tor versions.
16809 - DirServer configuration lines now have an orport= option so
16810 clients can open encrypted tunnels to the authorities without
16811 having downloaded their descriptors yet. Enabled for moria1,
16812 moria2, tor26, and lefkada now in the default configuration.
16813 - Directory servers are more willing to send a 503 "busy" if they
16814 are near their write limit, especially for v1 directory requests.
16815 Now they can use their limited bandwidth for actual Tor traffic.
16816 - Clients track responses with status 503 from dirservers. After a
16817 dirserver has given us a 503, we try not to use it until an hour has
16818 gone by, or until we have no dirservers that haven't given us a 503.
16819 - When we get a 503 from a directory, and we're not a server, we don't
16820 count the failure against the total number of failures allowed
16821 for the thing we're trying to download.
16822 - Report X-Your-Address-Is correctly from tunneled directory
16823 connections; don't report X-Your-Address-Is when it's an internal
16824 address; and never believe reported remote addresses when they're
16826 - Protect against an unlikely DoS attack on directory servers.
16827 - Add a BadDirectory flag to network status docs so that authorities
16828 can (eventually) tell clients about caches they believe to be
16831 o Minor features (controller):
16832 - Have GETINFO dir/status/* work on hosts with DirPort disabled.
16833 - Reimplement GETINFO so that info/names stays in sync with the
16835 - Implement "GETINFO fingerprint".
16836 - Implement "SETEVENTS GUARD" so controllers can get updates on
16837 entry guard status as it changes.
16839 o Minor features (clean up obsolete pieces):
16840 - Remove some options that have been deprecated since at least
16841 0.1.0.x: AccountingMaxKB, LogFile, DebugLogFile, LogLevel, and
16842 SysLog. Use AccountingMax instead of AccountingMaxKB, and use Log
16843 to set log options.
16844 - We no longer look for identity and onion keys in "identity.key" and
16845 "onion.key" -- these were replaced by secret_id_key and
16846 secret_onion_key in 0.0.8pre1.
16847 - We no longer require unrecognized directory entries to be
16850 o Major bugfixes (security):
16851 - Stop sending the HttpProxyAuthenticator string to directory
16852 servers when directory connections are tunnelled through Tor.
16853 - Clients no longer store bandwidth history in the state file.
16854 - Do not log introduction points for hidden services if SafeLogging
16856 - When generating bandwidth history, round down to the nearest
16857 1k. When storing accounting data, round up to the nearest 1k.
16858 - When we're running as a server, remember when we last rotated onion
16859 keys, so that we will rotate keys once they're a week old even if
16860 we never stay up for a week ourselves.
16862 o Major bugfixes (other):
16863 - Fix a longstanding bug in eventdns that prevented the count of
16864 timed-out resolves from ever being reset. This bug caused us to
16865 give up on a nameserver the third time it timed out, and try it
16866 10 seconds later... and to give up on it every time it timed out
16868 - Take out the '5 second' timeout from the connection retry
16869 schedule. Now the first connect attempt will wait a full 10
16870 seconds before switching to a new circuit. Perhaps this will help
16871 a lot. Based on observations from Mike Perry.
16872 - Fix a bug on the Windows implementation of tor_mmap_file() that
16873 would prevent the cached-routers file from ever loading. Reported
16877 - Fix an assert failure when a directory authority sets
16878 AuthDirRejectUnlisted and then receives a descriptor from an
16879 unlisted router. Reported by seeess.
16880 - Avoid a double-free when parsing malformed DirServer lines.
16881 - Fix a bug when a BSD-style PF socket is first used. Patch from
16883 - Fix a bug in 0.1.2.2-alpha that prevented clients from asking
16884 to resolve an address at a given exit node even when they ask for
16886 - Servers no longer ever list themselves in their "family" line,
16887 even if configured to do so. This makes it easier to configure
16888 family lists conveniently.
16889 - When running as a server, don't fall back to 127.0.0.1 when no
16890 nameservers are configured in /etc/resolv.conf; instead, make the
16891 user fix resolv.conf or specify nameservers explicitly. (Resolves
16893 - Stop accepting certain malformed ports in configured exit policies.
16894 - Don't re-write the fingerprint file every restart, unless it has
16896 - Stop warning when a single nameserver fails: only warn when _all_ of
16897 our nameservers have failed. Also, when we only have one nameserver,
16898 raise the threshold for deciding that the nameserver is dead.
16899 - Directory authorities now only decide that routers are reachable
16900 if their identity keys are as expected.
16901 - When the user uses bad syntax in the Log config line, stop
16902 suggesting other bad syntax as a replacement.
16903 - Correctly detect ipv6 DNS capability on OpenBSD.
16905 o Minor bugfixes (controller):
16906 - Report the circuit number correctly in STREAM CLOSED events. Bug
16907 reported by Mike Perry.
16908 - Do not report bizarre values for results of accounting GETINFOs
16909 when the last second's write or read exceeds the allotted bandwidth.
16910 - Report "unrecognized key" rather than an empty string when the
16911 controller tries to fetch a networkstatus that doesn't exist.
16914 Changes in version 0.1.1.26 - 2006-12-14
16915 o Security bugfixes:
16916 - Stop sending the HttpProxyAuthenticator string to directory
16917 servers when directory connections are tunnelled through Tor.
16918 - Clients no longer store bandwidth history in the state file.
16919 - Do not log introduction points for hidden services if SafeLogging
16923 - Fix an assert failure when a directory authority sets
16924 AuthDirRejectUnlisted and then receives a descriptor from an
16925 unlisted router (reported by seeess).
16928 Changes in version 0.1.2.4-alpha - 2006-12-03
16930 - Add support for using natd; this allows FreeBSDs earlier than
16931 5.1.2 to have ipfw send connections through Tor without using
16932 SOCKS. (Patch from Zajcev Evgeny with tweaks from tup.)
16935 - Make all connections to addresses of the form ".noconnect"
16936 immediately get closed. This lets application/controller combos
16937 successfully test whether they're talking to the same Tor by
16938 watching for STREAM events.
16939 - Make cross.sh cross-compilation script work even when autogen.sh
16940 hasn't been run. (Patch from Michael Mohr.)
16941 - Statistics dumped by -USR2 now include a breakdown of public key
16942 operations, for profiling.
16945 - Fix a major leak when directory authorities parse their
16946 approved-routers list, a minor memory leak when we fail to pick
16947 an exit node, and a few rare leaks on errors.
16948 - Handle TransPort connections even when the server sends data before
16949 the client sends data. Previously, the connection would just hang
16950 until the client sent data. (Patch from tup based on patch from
16952 - Avoid assert failure when our cached-routers file is empty on
16956 - Don't log spurious warnings when we see a circuit close reason we
16957 don't recognize; it's probably just from a newer version of Tor.
16958 - Have directory authorities allow larger amounts of drift in uptime
16959 without replacing the server descriptor: previously, a server that
16960 restarted every 30 minutes could have 48 "interesting" descriptors
16962 - Start linking to the Tor specification and Tor reference manual
16963 correctly in the Windows installer.
16964 - Add Vidalia to the OS X uninstaller script, so when we uninstall
16965 Tor/Privoxy we also uninstall Vidalia.
16966 - Resume building on Irix64, and fix a lot of warnings from its
16967 MIPSpro C compiler.
16968 - Don't corrupt last_guessed_ip in router_new_address_suggestion()
16969 when we're running as a client.
16972 Changes in version 0.1.1.25 - 2006-11-04
16974 - When a client asks us to resolve (rather than connect to)
16975 an address, and we have a cached answer, give them the cached
16976 answer. Previously, we would give them no answer at all.
16977 - We were building exactly the wrong circuits when we predict
16978 hidden service requirements, meaning Tor would have to build all
16979 its circuits on demand.
16980 - If none of our live entry guards have a high uptime, but we
16981 require a guard with a high uptime, try adding a new guard before
16982 we give up on the requirement. This patch should make long-lived
16983 connections more stable on average.
16984 - When testing reachability of our DirPort, don't launch new
16985 tests when there's already one in progress -- unreachable
16986 servers were stacking up dozens of testing streams.
16988 o Security bugfixes:
16989 - When the user sends a NEWNYM signal, clear the client-side DNS
16990 cache too. Otherwise we continue to act on previous information.
16993 - Avoid a memory corruption bug when creating a hash table for
16995 - Avoid possibility of controller-triggered crash when misusing
16996 certain commands from a v0 controller on platforms that do not
16997 handle printf("%s",NULL) gracefully.
16998 - Avoid infinite loop on unexpected controller input.
16999 - Don't log spurious warnings when we see a circuit close reason we
17000 don't recognize; it's probably just from a newer version of Tor.
17001 - Add Vidalia to the OS X uninstaller script, so when we uninstall
17002 Tor/Privoxy we also uninstall Vidalia.
17005 Changes in version 0.1.2.3-alpha - 2006-10-29
17007 - Prepare for servers to publish descriptors less often: never
17008 discard a descriptor simply for being too old until either it is
17009 recommended by no authorities, or until we get a better one for
17010 the same router. Make caches consider retaining old recommended
17011 routers for even longer.
17012 - If most authorities set a BadExit flag for a server, clients
17013 don't think of it as a general-purpose exit. Clients only consider
17014 authorities that advertise themselves as listing bad exits.
17015 - Directory servers now provide 'Pragma: no-cache' and 'Expires'
17016 headers for content, so that we can work better in the presence of
17017 caching HTTP proxies.
17018 - Allow authorities to list nodes as bad exits by fingerprint or by
17021 o Minor features, controller:
17022 - Add a REASON field to CIRC events; for backward compatibility, this
17023 field is sent only to controllers that have enabled the extended
17024 event format. Also, add additional reason codes to explain why
17025 a given circuit has been destroyed or truncated. (Patches from
17027 - Add a REMOTE_REASON field to extended CIRC events to tell the
17028 controller about why a remote OR told us to close a circuit.
17029 - Stream events also now have REASON and REMOTE_REASON fields,
17030 working much like those for circuit events.
17031 - There's now a GETINFO ns/... field so that controllers can ask Tor
17032 about the current status of a router.
17033 - A new event type "NS" to inform a controller when our opinion of
17034 a router's status has changed.
17035 - Add a GETINFO events/names and GETINFO features/names so controllers
17036 can tell which events and features are supported.
17037 - A new CLEARDNSCACHE signal to allow controllers to clear the
17038 client-side DNS cache without expiring circuits.
17040 o Security bugfixes:
17041 - When the user sends a NEWNYM signal, clear the client-side DNS
17042 cache too. Otherwise we continue to act on previous information.
17045 - Avoid sending junk to controllers or segfaulting when a controller
17046 uses EVENT_NEW_DESC with verbose nicknames.
17047 - Stop triggering asserts if the controller tries to extend hidden
17048 service circuits (reported by mwenge).
17049 - Avoid infinite loop on unexpected controller input.
17050 - When the controller does a "GETINFO network-status", tell it
17051 about even those routers whose descriptors are very old, and use
17052 long nicknames where appropriate.
17053 - Change NT service functions to be loaded on demand. This lets us
17054 build with MinGW without breaking Tor for Windows 98 users.
17055 - Do DirPort reachability tests less often, since a single test
17056 chews through many circuits before giving up.
17057 - In the hidden service example in torrc.sample, stop recommending
17058 esoteric and discouraged hidden service options.
17059 - When stopping an NT service, wait up to 10 sec for it to actually
17060 stop. Patch from Matt Edman; resolves bug 295.
17061 - Fix handling of verbose nicknames with ORCONN controller events:
17062 make them show up exactly when requested, rather than exactly when
17064 - When reporting verbose nicknames in entry_guards_getinfo(), avoid
17065 printing a duplicate "$" in the keys we send (reported by mwenge).
17066 - Correctly set maximum connection limit on Cygwin. (This time
17068 - Try to detect Windows correctly when cross-compiling.
17069 - Detect the size of the routers file correctly even if it is
17070 corrupted (on systems without mmap) or not page-aligned (on systems
17071 with mmap). This bug was harmless.
17072 - Sometimes we didn't bother sending a RELAY_END cell when an attempt
17073 to open a stream fails; now we do in more cases. This should
17074 make clients able to find a good exit faster in some cases, since
17075 unhandleable requests will now get an error rather than timing out.
17076 - Resolve two memory leaks when rebuilding the on-disk router cache
17077 (reported by fookoowa).
17078 - Clean up minor code warnings suggested by the MIPSpro C compiler,
17079 and reported by some Centos users.
17080 - Controller signals now work on non-Unix platforms that don't define
17081 SIGUSR1 and SIGUSR2 the way we expect.
17082 - Patch from Michael Mohr to contrib/cross.sh, so it checks more
17083 values before failing, and always enables eventdns.
17084 - Libevent-1.2 exports, but does not define in its headers, strlcpy.
17085 Try to fix this in configure.in by checking for most functions
17086 before we check for libevent.
17089 Changes in version 0.1.2.2-alpha - 2006-10-07
17091 - Make our async eventdns library on-by-default for Tor servers,
17092 and plan to deprecate the separate dnsworker threads.
17093 - Add server-side support for "reverse" DNS lookups (using PTR
17094 records so clients can determine the canonical hostname for a given
17095 IPv4 address). Only supported by servers using eventdns; servers
17096 now announce in their descriptors whether they support eventdns.
17097 - Specify and implement client-side SOCKS5 interface for reverse DNS
17098 lookups (see doc/socks-extensions.txt).
17099 - Add a BEGIN_DIR relay cell type for an easier in-protocol way to
17100 connect to directory servers through Tor. Previously, clients needed
17101 to find Tor exits to make private connections to directory servers.
17102 - Avoid choosing Exit nodes for entry or middle hops when the
17103 total bandwidth available from non-Exit nodes is much higher than
17104 the total bandwidth available from Exit nodes.
17105 - Workaround for name servers (like Earthlink's) that hijack failing
17106 DNS requests and replace the no-such-server answer with a "helpful"
17107 redirect to an advertising-driven search portal. Also work around
17108 DNS hijackers who "helpfully" decline to hijack known-invalid
17109 RFC2606 addresses. Config option "ServerDNSDetectHijacking 0"
17110 lets you turn it off.
17111 - Send out a burst of long-range padding cells once we've established
17112 that we're reachable. Spread them over 4 circuits, so hopefully
17113 a few will be fast. This exercises our bandwidth and bootstraps
17114 us into the directory more quickly.
17116 o New/improved config options:
17117 - Add new config option "ResolvConf" to let the server operator
17118 choose an alternate resolve.conf file when using eventdns.
17119 - Add an "EnforceDistinctSubnets" option to control our "exclude
17120 servers on the same /16" behavior. It's still on by default; this
17121 is mostly for people who want to operate private test networks with
17122 all the machines on the same subnet.
17123 - If one of our entry guards is on the ExcludeNodes list, or the
17124 directory authorities don't think it's a good guard, treat it as
17125 if it were unlisted: stop using it as a guard, and throw it off
17126 the guards list if it stays that way for a long time.
17127 - Allow directory authorities to be marked separately as authorities
17128 for the v1 directory protocol, the v2 directory protocol, and
17129 as hidden service directories, to make it easier to retire old
17130 authorities. V1 authorities should set "HSAuthoritativeDir 1"
17131 to continue being hidden service authorities too.
17132 - Remove 8888 as a LongLivedPort, and add 6697 (IRCS).
17134 o Minor features, controller:
17135 - Fix CIRC controller events so that controllers can learn the
17136 identity digests of non-Named servers used in circuit paths.
17137 - Let controllers ask for more useful identifiers for servers. Instead
17138 of learning identity digests for un-Named servers and nicknames
17139 for Named servers, the new identifiers include digest, nickname,
17140 and indication of Named status. Off by default; see control-spec.txt
17141 for more information.
17142 - Add a "getinfo address" controller command so it can display Tor's
17143 best guess to the user.
17144 - New controller event to alert the controller when our server
17145 descriptor has changed.
17146 - Give more meaningful errors on controller authentication failure.
17148 o Minor features, other:
17149 - When asked to resolve a hostname, don't use non-exit servers unless
17150 requested to do so. This allows servers with broken DNS to be
17151 useful to the network.
17152 - Divide eventdns log messages into warn and info messages.
17153 - Reserve the nickname "Unnamed" for routers that can't pick
17154 a hostname: any router can call itself Unnamed; directory
17155 authorities will never allocate Unnamed to any particular router;
17156 clients won't believe that any router is the canonical Unnamed.
17157 - Only include function names in log messages for info/debug messages.
17158 For notice/warn/err, the content of the message should be clear on
17159 its own, and printing the function name only confuses users.
17160 - Avoid some false positives during reachability testing: don't try
17161 to test via a server that's on the same /24 as us.
17162 - If we fail to build a circuit to an intended enclave, and it's
17163 not mandatory that we use that enclave, stop wanting it.
17164 - When eventdns is enabled, allow multithreaded builds on NetBSD and
17165 OpenBSD. (We had previously disabled threads on these platforms
17166 because they didn't have working thread-safe resolver functions.)
17168 o Major bugfixes, anonymity/security:
17169 - If a client asked for a server by name, and there's a named server
17170 in our network-status but we don't have its descriptor yet, we
17171 could return an unnamed server instead.
17172 - Fix NetBSD bug that could allow someone to force uninitialized RAM
17173 to be sent to a server's DNS resolver. This only affects NetBSD
17174 and other platforms that do not bounds-check tolower().
17175 - Reject (most) attempts to use Tor circuits with length one. (If
17176 many people start using Tor as a one-hop proxy, exit nodes become
17177 a more attractive target for compromise.)
17178 - Just because your DirPort is open doesn't mean people should be
17179 able to remotely teach you about hidden service descriptors. Now
17180 only accept rendezvous posts if you've got HSAuthoritativeDir set.
17182 o Major bugfixes, other:
17183 - Don't crash on race condition in dns.c: tor_assert(!resolve->expire)
17184 - When a client asks the server to resolve (not connect to)
17185 an address, and it has a cached answer, give them the cached answer.
17186 Previously, the server would give them no answer at all.
17187 - Allow really slow clients to not hang up five minutes into their
17188 directory downloads (suggested by Adam J. Richter).
17189 - We were building exactly the wrong circuits when we anticipated
17190 hidden service requirements, meaning Tor would have to build all
17191 its circuits on demand.
17192 - Avoid crashing when we mmap a router cache file of size 0.
17193 - When testing reachability of our DirPort, don't launch new
17194 tests when there's already one in progress -- unreachable
17195 servers were stacking up dozens of testing streams.
17197 o Minor bugfixes, correctness:
17198 - If we're a directory mirror and we ask for "all" network status
17199 documents, we would discard status documents from authorities
17200 we don't recognize.
17201 - Avoid a memory corruption bug when creating a hash table for
17203 - Avoid controller-triggered crash when misusing certain commands
17204 from a v0 controller on platforms that do not handle
17205 printf("%s",NULL) gracefully.
17206 - Don't crash when a controller sends a third argument to an
17207 "extendcircuit" request.
17208 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17209 response; fix error code when "getinfo dir/status/" fails.
17210 - Avoid crash when telling controller stream-status and a stream
17212 - Patch from Adam Langley to fix assert() in eventdns.c.
17213 - Fix a debug log message in eventdns to say "X resolved to Y"
17214 instead of "X resolved to X".
17215 - Make eventdns give strings for DNS errors, not just error numbers.
17216 - Track unreachable entry guards correctly: don't conflate
17217 'unreachable by us right now' with 'listed as down by the directory
17218 authorities'. With the old code, if a guard was unreachable by
17219 us but listed as running, it would clog our guard list forever.
17220 - Behave correctly in case we ever have a network with more than
17221 2GB/s total advertised capacity.
17222 - Make TrackExitHosts case-insensitive, and fix the behavior of
17223 ".suffix" TrackExitHosts items to avoid matching in the middle of
17225 - Finally fix the openssl warnings from newer gccs that believe that
17226 ignoring a return value is okay, but casting a return value and
17227 then ignoring it is a sign of madness.
17228 - Prevent the contrib/exitlist script from printing the same
17229 result more than once.
17230 - Patch from Steve Hildrey: Generate network status correctly on
17231 non-versioning dirservers.
17232 - Don't listen to the X-Your-Address-Is hint if you did the lookup
17233 via Tor; otherwise you'll think you're the exit node's IP address.
17235 o Minor bugfixes, performance:
17236 - Two small performance improvements on parsing descriptors.
17237 - Major performance improvement on inserting descriptors: change
17238 algorithm from O(n^2) to O(n).
17239 - Make the common memory allocation path faster on machines where
17240 malloc(0) returns a pointer.
17241 - Start remembering X-Your-Address-Is directory hints even if you're
17242 a client, so you can become a server more smoothly.
17243 - Avoid duplicate entries on MyFamily line in server descriptor.
17245 o Packaging, features:
17246 - Remove architecture from OS X builds. The official builds are
17247 now universal binaries.
17248 - The Debian package now uses --verify-config when (re)starting,
17249 to distinguish configuration errors from other errors.
17250 - Update RPMs to require libevent 1.1b.
17252 o Packaging, bugfixes:
17253 - Patches so Tor builds with MinGW on Windows.
17254 - Patches so Tor might run on Cygwin again.
17255 - Resume building on non-gcc compilers and ancient gcc. Resume
17256 building with the -O0 compile flag. Resume building cleanly on
17258 - Run correctly on OS X platforms with case-sensitive filesystems.
17259 - Correct includes for net/if.h and net/pfvar.h on OpenBSD (from Tup).
17260 - Add autoconf checks so Tor can build on Solaris x86 again.
17263 - Documented (and renamed) ServerDNSSearchDomains and
17264 ServerDNSResolvConfFile options.
17265 - Be clearer that the *ListenAddress directives can be repeated
17269 Changes in version 0.1.1.24 - 2006-09-29
17271 - Allow really slow clients to not hang up five minutes into their
17272 directory downloads (suggested by Adam J. Richter).
17273 - Fix major performance regression from 0.1.0.x: instead of checking
17274 whether we have enough directory information every time we want to
17275 do something, only check when the directory information has changed.
17276 This should improve client CPU usage by 25-50%.
17277 - Don't crash if, after a server has been running for a while,
17278 it can't resolve its hostname.
17281 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17282 - Don't crash when the controller receives a third argument to an
17283 "extendcircuit" request.
17284 - Controller protocol fixes: fix encoding in "getinfo addr-mappings"
17285 response; fix error code when "getinfo dir/status/" fails.
17286 - Fix configure.in to not produce broken configure files with
17287 more recent versions of autoconf. Thanks to Clint for his auto*
17289 - Fix security bug on NetBSD that could allow someone to force
17290 uninitialized RAM to be sent to a server's DNS resolver. This
17291 only affects NetBSD and other platforms that do not bounds-check
17293 - Warn user when using libevent 1.1a or earlier with win32 or kqueue
17294 methods: these are known to be buggy.
17295 - If we're a directory mirror and we ask for "all" network status
17296 documents, we would discard status documents from authorities
17297 we don't recognize.
17300 Changes in version 0.1.2.1-alpha - 2006-08-27
17302 - Add "eventdns" async dns library from Adam Langley, tweaked to
17303 build on OSX and Windows. Only enabled if you pass the
17304 --enable-eventdns argument to configure.
17305 - Allow servers with no hostname or IP address to learn their
17306 IP address by asking the directory authorities. This code only
17307 kicks in when you would normally have exited with a "no address"
17308 error. Nothing's authenticated, so use with care.
17309 - Rather than waiting a fixed amount of time between retrying
17310 application connections, we wait only 5 seconds for the first,
17311 10 seconds for the second, and 15 seconds for each retry after
17312 that. Hopefully this will improve the expected user experience.
17313 - Patch from Tup to add support for transparent AP connections:
17314 this basically bundles the functionality of trans-proxy-tor
17315 into the Tor mainline. Now hosts with compliant pf/netfilter
17316 implementations can redirect TCP connections straight to Tor
17317 without diverting through SOCKS. Needs docs.
17318 - Busy directory servers save lots of memory by spooling server
17319 descriptors, v1 directories, and v2 networkstatus docs to buffers
17320 as needed rather than en masse. Also mmap the cached-routers
17321 files, so we don't need to keep the whole thing in memory too.
17322 - Automatically avoid picking more than one node from the same
17323 /16 network when constructing a circuit.
17324 - Revise and clean up the torrc.sample that we ship with; add
17325 a section for BandwidthRate and BandwidthBurst.
17328 - Split circuit_t into origin_circuit_t and or_circuit_t, and
17329 split connection_t into edge, or, dir, control, and base structs.
17330 These will save quite a bit of memory on busy servers, and they'll
17331 also help us track down bugs in the code and bugs in the spec.
17332 - Experimentally re-enable kqueue on OSX when using libevent 1.1b
17333 or later. Log when we are doing this, so we can diagnose it when
17334 it fails. (Also, recommend libevent 1.1b for kqueue and
17335 win32 methods; deprecate libevent 1.0b harder; make libevent
17336 recommendation system saner.)
17337 - Start being able to build universal binaries on OS X (thanks
17339 - Export the default exit policy via the control port, so controllers
17340 don't need to guess what it is / will be later.
17341 - Add a man page entry for ProtocolWarnings.
17342 - Add TestVia config option to the man page.
17343 - Remove even more protocol-related warnings from Tor server logs,
17344 such as bad TLS handshakes and malformed begin cells.
17345 - Stop fetching descriptors if you're not a dir mirror and you
17346 haven't tried to establish any circuits lately. [This currently
17347 causes some dangerous behavior, because when you start up again
17348 you'll use your ancient server descriptors.]
17349 - New DirPort behavior: if you have your dirport set, you download
17350 descriptors aggressively like a directory mirror, whether or not
17351 your ORPort is set.
17352 - Get rid of the router_retry_connections notion. Now routers
17353 no longer try to rebuild long-term connections to directory
17354 authorities, and directory authorities no longer try to rebuild
17355 long-term connections to all servers. We still don't hang up
17356 connections in these two cases though -- we need to look at it
17357 more carefully to avoid flapping, and we likely need to wait til
17358 0.1.1.x is obsolete.
17359 - Drop compatibility with obsolete Tors that permit create cells
17360 to have the wrong circ_id_type.
17361 - Re-enable per-connection rate limiting. Get rid of the "OP
17362 bandwidth" concept. Lay groundwork for "bandwidth classes" --
17363 separate global buckets that apply depending on what sort of conn
17365 - Start publishing one minute or so after we find our ORPort
17366 to be reachable. This will help reduce the number of descriptors
17367 we have for ourselves floating around, since it's quite likely
17368 other things (e.g. DirPort) will change during that minute too.
17369 - Fork the v1 directory protocol into its own spec document,
17370 and mark dir-spec.txt as the currently correct (v2) spec.
17373 - When we find our DirPort to be reachable, publish a new descriptor
17374 so we'll tell the world (reported by pnx).
17375 - Publish a new descriptor after we hup/reload. This is important
17376 if our config has changed such that we'll want to start advertising
17377 our DirPort now, etc.
17378 - Allow Tor to start when RunAsDaemon is set but no logs are set.
17379 - When we have a state file we cannot parse, tell the user and
17380 move it aside. Now we avoid situations where the user starts
17381 Tor in 1904, Tor writes a state file with that timestamp in it,
17382 the user fixes her clock, and Tor refuses to start.
17383 - Fix configure.in to not produce broken configure files with
17384 more recent versions of autoconf. Thanks to Clint for his auto*
17386 - "tor --verify-config" now exits with -1(255) or 0 depending on
17387 whether the config options are bad or good.
17388 - Resolve bug 321 when using dnsworkers: append a period to every
17389 address we resolve at the exit node, so that we do not accidentally
17390 pick up local addresses, and so that failing searches are retried
17391 in the resolver search domains. (This is already solved for
17392 eventdns.) (This breaks Blossom servers for now.)
17393 - If we are using an exit enclave and we can't connect, e.g. because
17394 its webserver is misconfigured to not listen on localhost, then
17395 back off and try connecting from somewhere else before we fail.
17398 - Start compiling on MinGW on Windows (patches from Mike Chiussi).
17399 - Start compiling on MSVC6 on Windows (patches from Frediano Ziglio).
17400 - Fix bug 314: Tor clients issued "unsafe socks" warnings even
17401 when the IP address is mapped through MapAddress to a hostname.
17402 - Start passing "ipv4" hints to getaddrinfo(), so servers don't do
17403 useless IPv6 DNS resolves.
17404 - Patch suggested by Karsten Loesing: respond to SIGNAL command
17405 before we execute the signal, in case the signal shuts us down.
17406 - Clean up AllowInvalidNodes man page entry.
17407 - Claim a commonname of Tor, rather than TOR, in TLS handshakes.
17408 - Add more asserts to track down an assert error on a windows Tor
17409 server with connection_add being called with socket == -1.
17410 - Handle reporting OR_CONN_EVENT_NEW events to the controller.
17411 - Fix misleading log messages: an entry guard that is "unlisted",
17412 as well as not known to be "down" (because we've never heard
17413 of it), is not therefore "up".
17414 - Remove code to special-case "-cvs" ending, since it has not
17415 actually mattered since 0.0.9.
17416 - Make our socks5 handling more robust to broken socks clients:
17417 throw out everything waiting on the buffer in between socks
17418 handshake phases, since they can't possibly (so the theory
17419 goes) have predicted what we plan to respond to them.
17422 Changes in version 0.1.1.23 - 2006-07-30
17424 - Fast Tor servers, especially exit nodes, were triggering asserts
17425 due to a bug in handling the list of pending DNS resolves. Some
17426 bugs still remain here; we're hunting them.
17427 - Entry guards could crash clients by sending unexpected input.
17428 - More fixes on reachability testing: if you find yourself reachable,
17429 then don't ever make any client requests (so you stop predicting
17430 circuits), then hup or have your clock jump, then later your IP
17431 changes, you won't think circuits are working, so you won't try to
17432 test reachability, so you won't publish.
17435 - Avoid a crash if the controller does a resetconf firewallports
17436 and then a setconf fascistfirewall=1.
17437 - Avoid an integer underflow when the dir authority decides whether
17438 a router is stable: we might wrongly label it stable, and compute
17439 a slightly wrong median stability, when a descriptor is published
17441 - Fix a place where we might trigger an assert if we can't build our
17442 own server descriptor yet.
17445 Changes in version 0.1.1.22 - 2006-07-05
17447 - Fix a big bug that was causing servers to not find themselves
17448 reachable if they changed IP addresses. Since only 0.1.1.22+
17449 servers can do reachability testing correctly, now we automatically
17450 make sure to test via one of these.
17451 - Fix to allow clients and mirrors to learn directory info from
17452 descriptor downloads that get cut off partway through.
17453 - Directory authorities had a bug in deciding if a newly published
17454 descriptor was novel enough to make everybody want a copy -- a few
17455 servers seem to be publishing new descriptors many times a minute.
17457 - Fix a rare bug that was causing some servers to complain about
17458 "closing wedged cpuworkers" and skip some circuit create requests.
17459 - Make the Exit flag in directory status documents actually work.
17462 Changes in version 0.1.1.21 - 2006-06-10
17463 o Crash and assert fixes from 0.1.1.20:
17464 - Fix a rare crash on Tor servers that have enabled hibernation.
17465 - Fix a seg fault on startup for Tor networks that use only one
17466 directory authority.
17467 - Fix an assert from a race condition that occurs on Tor servers
17468 while exiting, where various threads are trying to log that they're
17469 exiting, and delete the logs, at the same time.
17470 - Make our unit tests pass again on certain obscure platforms.
17473 - Add support for building SUSE RPM packages.
17474 - Speed up initial bootstrapping for clients: if we are making our
17475 first ever connection to any entry guard, then don't mark it down
17477 - When only one Tor server in the network is labelled as a guard,
17478 and we've already picked him, we would cycle endlessly picking him
17479 again, being unhappy about it, etc. Now we specifically exclude
17480 current guards when picking a new guard.
17481 - Servers send create cells more reliably after the TLS connection
17482 is established: we were sometimes forgetting to send half of them
17483 when we had more than one pending.
17484 - If we get a create cell that asks us to extend somewhere, but the
17485 Tor server there doesn't match the expected digest, we now send
17486 a destroy cell back, rather than silently doing nothing.
17487 - Make options->RedirectExit work again.
17488 - Make cookie authentication for the controller work again.
17489 - Stop being picky about unusual characters in the arguments to
17490 mapaddress. It's none of our business.
17491 - Add a new config option "TestVia" that lets you specify preferred
17492 middle hops to use for test circuits. Perhaps this will let me
17493 debug the reachability problems better.
17495 o Log / documentation fixes:
17496 - If we're a server and some peer has a broken TLS certificate, don't
17497 log about it unless ProtocolWarnings is set, i.e., we want to hear
17498 about protocol violations by others.
17499 - Fix spelling of VirtualAddrNetwork in man page.
17500 - Add a better explanation at the top of the autogenerated torrc file
17501 about what happened to our old torrc.
17504 Changes in version 0.1.1.20 - 2006-05-23
17506 - Downgrade a log severity where servers complain that they're
17508 - Avoid a compile warning on FreeBSD.
17509 - Remove string size limit on NEWDESC messages; solve bug 291.
17510 - Correct the RunAsDaemon entry in the man page; ignore RunAsDaemon
17511 more thoroughly when we're running on windows.
17514 Changes in version 0.1.1.19-rc - 2006-05-03
17516 - Regenerate our local descriptor if it's dirty and we try to use
17517 it locally (e.g. if it changes during reachability detection).
17518 - If we setconf our ORPort to 0, we continued to listen on the
17519 old ORPort and receive connections.
17520 - Avoid a second warning about machine/limits.h on Debian
17522 - Be willing to add our own routerinfo into the routerlist.
17523 Now authorities will include themselves in their directories
17524 and network-statuses.
17525 - Stop trying to upload rendezvous descriptors to every
17526 directory authority: only try the v1 authorities.
17527 - Servers no longer complain when they think they're not
17528 registered with the directory authorities. There were too many
17530 - Backport dist-rpm changes so rpms can be built without errors.
17533 - Implement an option, VirtualAddrMask, to set which addresses
17534 get handed out in response to mapaddress requests. This works
17535 around a bug in tsocks where 127.0.0.0/8 is never socksified.
17538 Changes in version 0.1.1.18-rc - 2006-04-10
17540 - Work harder to download live network-statuses from all the
17541 directory authorities we know about. Improve the threshold
17542 decision logic so we're more robust to edge cases.
17543 - When fetching rendezvous descriptors, we were willing to ask
17544 v2 authorities too, which would always return 404.
17547 - Stop listing down or invalid nodes in the v1 directory. This will
17548 reduce its bulk by about 1/3, and reduce load on directory
17550 - When deciding whether a router is Fast or Guard-worthy, consider
17551 his advertised BandwidthRate and not just the BandwidthCapacity.
17552 - No longer ship INSTALL and README files -- they are useless now.
17553 - Force rpmbuild to behave and honor target_cpu.
17554 - Avoid warnings about machine/limits.h on Debian GNU/kFreeBSD.
17555 - Start to include translated versions of the tor-doc-*.html
17556 files, along with the screenshots. Still needs more work.
17557 - Start sending back 512 and 451 errors if mapaddress fails,
17558 rather than not sending anything back at all.
17559 - When we fail to bind or listen on an incoming or outgoing
17560 socket, we should close it before failing. otherwise we just
17561 leak it. (thanks to weasel for finding.)
17562 - Allow "getinfo dir/status/foo" to work, as long as your DirPort
17563 is enabled. (This is a hack, and will be fixed in 0.1.2.x.)
17564 - Make NoPublish (even though deprecated) work again.
17565 - Fix a minor security flaw where a versioning auth dirserver
17566 could list a recommended version many times in a row to make
17567 clients more convinced that it's recommended.
17568 - Fix crash bug if there are two unregistered servers running
17569 with the same nickname, one of them is down, and you ask for
17570 them by nickname in your EntryNodes or ExitNodes. Also, try
17571 to pick the one that's running rather than an arbitrary one.
17572 - Fix an infinite loop we could hit if we go offline for too long.
17573 - Complain when we hit WSAENOBUFS on recv() or write() too.
17574 Perhaps this will help us hunt the bug.
17575 - If you're not a versioning dirserver, don't put the string
17576 "client-versions \nserver-versions \n" in your network-status.
17577 - Lower the minimum required number of file descriptors to 1000,
17578 so we can have some overhead for Valgrind on Linux, where the
17579 default ulimit -n is 1024.
17582 - Add tor.dizum.com as the fifth authoritative directory server.
17583 - Add a new config option FetchUselessDescriptors, off by default,
17584 for when you plan to run "exitlist" on your client and you want
17585 to know about even the non-running descriptors.
17588 Changes in version 0.1.1.17-rc - 2006-03-28
17590 - Clients and servers since 0.1.1.10-alpha have been expiring
17591 connections whenever they are idle for 5 minutes and they *do*
17592 have circuits on them. Oops. With this new version, clients will
17593 discard their previous entry guard choices and avoid choosing
17594 entry guards running these flawed versions.
17595 - Fix memory leak when uncompressing concatenated zlib streams. This
17596 was causing substantial leaks over time on Tor servers.
17597 - The v1 directory was including servers as much as 48 hours old,
17598 because that's how the new routerlist->routers works. Now only
17599 include them if they're 20 hours old or less.
17602 - Resume building on irix64, netbsd 2.0, etc.
17603 - On non-gcc compilers (e.g. solaris), use "-g -O" instead of
17605 - Stop writing the "router.desc" file, ever. Nothing uses it anymore,
17606 and it is confusing some users.
17607 - Mirrors stop caching the v1 directory so often.
17608 - Make the max number of old descriptors that a cache will hold
17609 rise with the number of directory authorities, so we can scale.
17610 - Change our win32 uname() hack to be more forgiving about what
17611 win32 versions it thinks it's found.
17614 - Add lefkada.eecs.harvard.edu as a fourth authoritative directory
17616 - When the controller's *setconf commands fail, collect an error
17617 message in a string and hand it back to the controller.
17618 - Make the v2 dir's "Fast" flag based on relative capacity, just
17619 like "Stable" is based on median uptime. Name everything in the
17620 top 7/8 Fast, and only the top 1/2 gets to be a Guard.
17621 - Log server fingerprint on startup, so new server operators don't
17622 have to go hunting around their filesystem for it.
17623 - Return a robots.txt on our dirport to discourage google indexing.
17624 - Let the controller ask for GETINFO dir/status/foo so it can ask
17625 directly rather than connecting to the dir port. Only works when
17626 dirport is set for now.
17628 o New config options rather than constants in the code:
17629 - SocksTimeout: How long do we let a socks connection wait
17630 unattached before we fail it?
17631 - CircuitBuildTimeout: Cull non-open circuits that were born
17632 at least this many seconds ago.
17633 - CircuitIdleTimeout: Cull open clean circuits that were born
17634 at least this many seconds ago.
17637 Changes in version 0.1.1.16-rc - 2006-03-18
17638 o Bugfixes on 0.1.1.15-rc:
17639 - Fix assert when the controller asks to attachstream a connect-wait
17640 or resolve-wait stream.
17641 - Now do address rewriting when the controller asks us to attach
17642 to a particular circuit too. This will let Blossom specify
17643 "moria2.exit" without having to learn what moria2's IP address is.
17644 - Make the "tor --verify-config" command-line work again, so people
17645 can automatically check if their torrc will parse.
17646 - Authoritative dirservers no longer require an open connection from
17647 a server to consider him "reachable". We need this change because
17648 when we add new auth dirservers, old servers won't know not to
17650 - Let Tor build on Sun CC again.
17651 - Fix an off-by-one buffer size in dirserv.c that magically never
17652 hit our three authorities but broke sjmurdoch's own tor network.
17653 - If we as a directory mirror don't know of any v1 directory
17654 authorities, then don't try to cache any v1 directories.
17655 - Stop warning about unknown servers in our family when they are
17656 given as hex digests.
17657 - Stop complaining as quickly to the server operator that he
17658 hasn't registered his nickname/key binding.
17659 - Various cleanups so we can add new V2 Auth Dirservers.
17660 - Change "AllowUnverifiedNodes" to "AllowInvalidNodes", to
17661 reflect the updated flags in our v2 dir protocol.
17662 - Resume allowing non-printable characters for exit streams (both
17663 for connecting and for resolving). Now we tolerate applications
17664 that don't follow the RFCs. But continue to block malformed names
17667 o Bugfixes on 0.1.0.x:
17668 - Fix assert bug in close_logs(): when we close and delete logs,
17669 remove them all from the global "logfiles" list.
17670 - Fix minor integer overflow in calculating when we expect to use up
17671 our bandwidth allocation before hibernating.
17672 - Fix a couple of bugs in OpenSSL detection. Also, deal better when
17673 there are multiple SSLs installed with different versions.
17674 - When we try to be a server and Address is not explicitly set and
17675 our hostname resolves to a private IP address, try to use an
17676 interface address if it has a public address. Now Windows machines
17677 that think of themselves as localhost can work by default.
17680 - Let the controller ask for GETINFO dir/server/foo so it can ask
17681 directly rather than connecting to the dir port.
17682 - Let the controller tell us about certain router descriptors
17683 that it doesn't want Tor to use in circuits. Implement
17684 SETROUTERPURPOSE and modify +POSTDESCRIPTOR to do this.
17685 - New config option SafeSocks to reject all application connections
17686 using unsafe socks protocols. Defaults to off.
17689 Changes in version 0.1.1.15-rc - 2006-03-11
17690 o Bugfixes and cleanups:
17691 - When we're printing strings from the network, don't try to print
17692 non-printable characters. This protects us against shell escape
17693 sequence exploits, and also against attacks to fool humans into
17694 misreading their logs.
17695 - Fix a bug where Tor would fail to establish any connections if you
17696 left it off for 24 hours and then started it: we were happy with
17697 the obsolete network statuses, but they all referred to router
17698 descriptors that were too old to fetch, so we ended up with no
17699 valid router descriptors.
17700 - Fix a seg fault in the controller's "getinfo orconn-status"
17701 command while listing status on incoming handshaking connections.
17702 Introduce a status name "NEW" for these connections.
17703 - If we get a linelist or linelist_s config option from the torrc
17704 (e.g. ExitPolicy) and it has no value, warn and skip rather than
17705 silently resetting it to its default.
17706 - Don't abandon entry guards until they've been down or gone for
17708 - Cleaner and quieter log messages.
17711 - New controller signal NEWNYM that makes new application requests
17712 use clean circuits.
17713 - Add a new circuit purpose 'controller' to let the controller ask
17714 for a circuit that Tor won't try to use. Extend the EXTENDCIRCUIT
17715 controller command to let you specify the purpose if you're
17716 starting a new circuit. Add a new SETCIRCUITPURPOSE controller
17717 command to let you change a circuit's purpose after it's been
17719 - Accept "private:*" in routerdesc exit policies; not generated yet
17720 because older Tors do not understand it.
17721 - Add BSD-style contributed startup script "rc.subr" from Peter
17725 Changes in version 0.1.1.14-alpha - 2006-02-20
17726 o Bugfixes on 0.1.1.x:
17727 - Don't die if we ask for a stdout or stderr log (even implicitly)
17728 and we're set to RunAsDaemon -- just warn.
17729 - We still had a few bugs in the OR connection rotation code that
17730 caused directory servers to slowly aggregate connections to other
17731 fast Tor servers. This time for sure!
17732 - Make log entries on Win32 include the name of the function again.
17733 - We were treating a pair of exit policies if they were equal even
17734 if one said accept and the other said reject -- causing us to
17735 not always publish a new descriptor since we thought nothing
17737 - Retry pending server downloads as well as pending networkstatus
17738 downloads when we unexpectedly get a socks request.
17739 - We were ignoring the IS_FAST flag in the directory status,
17740 meaning we were willing to pick trivial-bandwidth nodes for "fast"
17742 - If the controller's SAVECONF command fails (e.g. due to file
17743 permissions), let the controller know that it failed.
17746 - If we're trying to be a Tor server and running Windows 95/98/ME
17747 as a server, explain that we'll likely crash.
17748 - When we're a server, a client asks for an old-style directory,
17749 and our write bucket is empty, don't give it to him. This way
17750 small servers can continue to serve the directory *sometimes*,
17751 without getting overloaded.
17752 - Compress exit policies even more -- look for duplicate lines
17754 - Clients now honor the "guard" flag in the router status when
17755 picking entry guards, rather than looking at is_fast or is_stable.
17756 - Retain unrecognized lines in $DATADIR/state file, so that we can
17757 be forward-compatible.
17758 - Generate 18.0.0.0/8 address policy format in descs when we can;
17759 warn when the mask is not reducible to a bit-prefix.
17760 - Let the user set ControlListenAddress in the torrc. This can be
17761 dangerous, but there are some cases (like a secured LAN) where it
17763 - Split ReachableAddresses into ReachableDirAddresses and
17764 ReachableORAddresses, so we can restrict Dir conns to port 80
17765 and OR conns to port 443.
17766 - Now we can target arch and OS in rpm builds (contributed by
17767 Phobos). Also make the resulting dist-rpm filename match the
17769 - New config options to help controllers: FetchServerDescriptors
17770 and FetchHidServDescriptors for whether to fetch server
17771 info and hidserv info or let the controller do it, and
17772 PublishServerDescriptor and PublishHidServDescriptors.
17773 - Also let the controller set the __AllDirActionsPrivate config
17774 option if you want all directory fetches/publishes to happen via
17775 Tor (it assumes your controller bootstraps your circuits).
17778 Changes in version 0.1.0.17 - 2006-02-17
17779 o Crash bugfixes on 0.1.0.x:
17780 - When servers with a non-zero DirPort came out of hibernation,
17781 sometimes they would trigger an assert.
17783 o Other important bugfixes:
17784 - On platforms that don't have getrlimit (like Windows), we were
17785 artificially constraining ourselves to a max of 1024
17786 connections. Now just assume that we can handle as many as 15000
17787 connections. Hopefully this won't cause other problems.
17789 o Backported features:
17790 - When we're a server, a client asks for an old-style directory,
17791 and our write bucket is empty, don't give it to him. This way
17792 small servers can continue to serve the directory *sometimes*,
17793 without getting overloaded.
17794 - Whenever you get a 503 in response to a directory fetch, try
17795 once more. This will become important once servers start sending
17796 503's whenever they feel busy.
17797 - Fetch a new directory every 120 minutes, not every 40 minutes.
17798 Now that we have hundreds of thousands of users running the old
17799 directory algorithm, it's starting to hurt a lot.
17800 - Bump up the period for forcing a hidden service descriptor upload
17801 from 20 minutes to 1 hour.
17804 Changes in version 0.1.1.13-alpha - 2006-02-09
17805 o Crashes in 0.1.1.x:
17806 - When you tried to setconf ORPort via the controller, Tor would
17807 crash. So people using TorCP to become a server were sad.
17808 - Solve (I hope) the stack-smashing bug that we were seeing on fast
17809 servers. The problem appears to be something do with OpenSSL's
17810 random number generation, or how we call it, or something. Let me
17811 know if the crashes continue.
17812 - Turn crypto hardware acceleration off by default, until we find
17813 somebody smart who can test it for us. (It appears to produce
17814 seg faults in at least some cases.)
17815 - Fix a rare assert error when we've tried all intro points for
17816 a hidden service and we try fetching the service descriptor again:
17817 "Assertion conn->state != AP_CONN_STATE_RENDDESC_WAIT failed"
17820 - Fix a major load balance bug: we were round-robining in 16 KB
17821 chunks, and servers with bandwidthrate of 20 KB, while downloading
17822 a 600 KB directory, would starve their other connections. Now we
17823 try to be a bit more fair.
17824 - Dir authorities and mirrors were never expiring the newest
17825 descriptor for each server, causing memory and directory bloat.
17826 - Fix memory-bloating and connection-bloating bug on servers: We
17827 were never closing any connection that had ever had a circuit on
17828 it, because we were checking conn->n_circuits == 0, yet we had a
17829 bug that let it go negative.
17830 - Make Tor work using squid as your http proxy again -- squid
17831 returns an error if you ask for a URL that's too long, and it uses
17832 a really generic error message. Plus, many people are behind a
17833 transparent squid so they don't even realize it.
17834 - On platforms that don't have getrlimit (like Windows), we were
17835 artificially constraining ourselves to a max of 1024
17836 connections. Now just assume that we can handle as many as 15000
17837 connections. Hopefully this won't cause other problems.
17838 - Add a new config option ExitPolicyRejectPrivate which defaults to
17839 1. This means all exit policies will begin with rejecting private
17840 addresses, unless the server operator explicitly turns it off.
17843 - Clients no longer download descriptors for non-running
17845 - Before we add new directory authorities, we should make it
17846 clear that only v1 authorities should receive/publish hidden
17847 service descriptors.
17850 - As soon as we've fetched some more directory info, immediately
17851 try to download more server descriptors. This way we don't have
17852 a 10 second pause during initial bootstrapping.
17853 - Remove even more loud log messages that the server operator can't
17855 - When we're running an obsolete or un-recommended version, make
17856 the log message more clear about what the problem is and what
17857 versions *are* still recommended.
17858 - Provide a more useful warn message when our onion queue gets full:
17859 the CPU is too slow or the exit policy is too liberal.
17860 - Don't warn when we receive a 503 from a dirserver/cache -- this
17861 will pave the way for them being able to refuse if they're busy.
17862 - When we fail to bind a listener, try to provide a more useful
17863 log message: e.g., "Is Tor already running?"
17864 - Adjust tor-spec to parameterize cell and key lengths. Now Ian
17865 Goldberg can prove things about our handshake protocol more
17867 - MaxConn has been obsolete for a while now. Document the ConnLimit
17868 config option, which is a *minimum* number of file descriptors
17869 that must be available else Tor refuses to start.
17870 - Apply Matt Ghali's --with-syslog-facility patch to ./configure
17871 if you log to syslog and want something other than LOG_DAEMON.
17872 - Make dirservers generate a separate "guard" flag to mean,
17873 "would make a good entry guard". Make clients parse it and vote
17874 on it. Not used by clients yet.
17875 - Implement --with-libevent-dir option to ./configure. Also, improve
17876 search techniques to find libevent, and use those for openssl too.
17877 - Bump the default bandwidthrate to 3 MB, and burst to 6 MB
17878 - Only start testing reachability once we've established a
17879 circuit. This will make startup on dirservers less noisy.
17880 - Don't try to upload hidden service descriptors until we have
17881 established a circuit.
17882 - Fix the controller's "attachstream 0" command to treat conn like
17883 it just connected, doing address remapping, handling .exit and
17884 .onion idioms, and so on. Now we're more uniform in making sure
17885 that the controller hears about new and closing connections.
17888 Changes in version 0.1.1.12-alpha - 2006-01-11
17889 o Bugfixes on 0.1.1.x:
17890 - The fix to close duplicate server connections was closing all
17891 Tor client connections if they didn't establish a circuit
17892 quickly enough. Oops.
17893 - Fix minor memory issue (double-free) that happened on exit.
17895 o Bugfixes on 0.1.0.x:
17896 - Tor didn't warn when it failed to open a log file.
17899 Changes in version 0.1.1.11-alpha - 2006-01-10
17900 o Crashes in 0.1.1.x:
17901 - Include all the assert/crash fixes from 0.1.0.16.
17902 - If you start Tor and then quit very quickly, there were some
17903 races that tried to free things that weren't allocated yet.
17904 - Fix a rare memory stomp if you're running hidden services.
17905 - Fix segfault when specifying DirServer in config without nickname.
17906 - Fix a seg fault when you finish connecting to a server but at
17907 that moment you dump his server descriptor.
17908 - Extendcircuit and Attachstream controller commands would
17909 assert/crash if you don't give them enough arguments.
17910 - Fix an assert error when we're out of space in the connection_list
17911 and we try to post a hidden service descriptor (reported by weasel).
17912 - If you specify a relative torrc path and you set RunAsDaemon in
17913 your torrc, then it chdir()'s to the new directory. If you HUP,
17914 it tries to load the new torrc location, fails, and exits.
17915 The fix: no longer allow a relative path to torrc using -f.
17918 - Implement "entry guards": automatically choose a handful of entry
17919 nodes and stick with them for all circuits. Only pick new guards
17920 when the ones you have are unsuitable, and if the old guards
17921 become suitable again, switch back. This will increase security
17922 dramatically against certain end-point attacks. The EntryNodes
17923 config option now provides some hints about which entry guards you
17924 want to use most; and StrictEntryNodes means to only use those.
17925 - New directory logic: download by descriptor digest, not by
17926 fingerprint. Caches try to download all listed digests from
17927 authorities; clients try to download "best" digests from caches.
17928 This avoids partitioning and isolating attacks better.
17929 - Make the "stable" router flag in network-status be the median of
17930 the uptimes of running valid servers, and make clients pay
17931 attention to the network-status flags. Thus the cutoff adapts
17932 to the stability of the network as a whole, making IRC, IM, etc
17933 connections more reliable.
17936 - Tor servers with dynamic IP addresses were needing to wait 18
17937 hours before they could start doing reachability testing using
17938 the new IP address and ports. This is because they were using
17939 the internal descriptor to learn what to test, yet they were only
17940 rebuilding the descriptor once they decided they were reachable.
17941 - Tor 0.1.1.9 and 0.1.1.10 had a serious bug that caused clients
17942 to download certain server descriptors, throw them away, and then
17943 fetch them again after 30 minutes. Now mirrors throw away these
17944 server descriptors so clients can't get them.
17945 - We were leaving duplicate connections to other ORs open for a week,
17946 rather than closing them once we detect a duplicate. This only
17947 really affected authdirservers, but it affected them a lot.
17948 - Spread the authdirservers' reachability testing over the entire
17949 testing interval, so we don't try to do 500 TLS's at once every
17953 - If the network is down, and we try to connect to a conn because
17954 we have a circuit in mind, and we timeout (30 seconds) because the
17955 network never answers, we were expiring the circuit, but we weren't
17956 obsoleting the connection or telling the entry_guards functions.
17957 - Some Tor servers process billions of cells per day. These statistics
17958 need to be uint64_t's.
17959 - Check for integer overflows in more places, when adding elements
17960 to smartlists. This could possibly prevent a buffer overflow
17961 on malicious huge inputs. I don't see any, but I haven't looked
17963 - ReachableAddresses kept growing new "reject *:*" lines on every
17965 - When you "setconf log" via the controller, it should remove all
17966 logs. We were automatically adding back in a "log notice stdout".
17967 - Newly bootstrapped Tor networks couldn't establish hidden service
17968 circuits until they had nodes with high uptime. Be more tolerant.
17969 - We were marking servers down when they could not answer every piece
17970 of the directory request we sent them. This was far too harsh.
17971 - Fix the torify (tsocks) config file to not use Tor for localhost
17973 - Directory authorities now go to the proper authority when asking for
17974 a networkstatus, even when they want a compressed one.
17975 - Fix a harmless bug that was causing Tor servers to log
17976 "Got an end because of misc error, but we're not an AP. Closing."
17977 - Authorities were treating their own descriptor changes as cosmetic,
17978 meaning the descriptor available in the network-status and the
17979 descriptor that clients downloaded were different.
17980 - The OS X installer was adding a symlink for tor_resolve but
17981 the binary was called tor-resolve (reported by Thomas Hardly).
17982 - Workaround a problem with some http proxies where they refuse GET
17983 requests that specify "Content-Length: 0" (reported by Adrian).
17984 - Fix wrong log message when you add a "HiddenServiceNodes" config
17985 line without any HiddenServiceDir line (reported by Chris Thomas).
17988 - Write the TorVersion into the state file so we have a prayer of
17989 keeping forward and backward compatibility.
17990 - Revive the FascistFirewall config option rather than eliminating it:
17991 now it's a synonym for ReachableAddresses *:80,*:443.
17992 - Clients choose directory servers from the network status lists,
17993 not from their internal list of router descriptors. Now they can
17994 go to caches directly rather than needing to go to authorities
17996 - Directory authorities ignore router descriptors that have only
17997 cosmetic differences: do this for 0.1.0.x servers now too.
17998 - Add a new flag to network-status indicating whether the server
17999 can answer v2 directory requests too.
18000 - Authdirs now stop whining so loudly about bad descriptors that
18001 they fetch from other dirservers. So when there's a log complaint,
18002 it's for sure from a freshly uploaded descriptor.
18003 - Reduce memory requirements in our structs by changing the order
18005 - There used to be two ways to specify your listening ports in a
18006 server descriptor: on the "router" line and with a separate "ports"
18007 line. Remove support for the "ports" line.
18008 - New config option "AuthDirRejectUnlisted" for auth dirservers as
18009 a panic button: if we get flooded with unusable servers we can
18010 revert to only listing servers in the approved-routers file.
18011 - Auth dir servers can now mark a fingerprint as "!reject" or
18012 "!invalid" in the approved-routers file (as its nickname), to
18013 refuse descriptors outright or include them but marked as invalid.
18014 - Servers store bandwidth history across restarts/crashes.
18015 - Add reasons to DESTROY and RELAY_TRUNCATED cells, so clients can
18016 get a better idea of why their circuits failed. Not used yet.
18017 - Directory mirrors now cache up to 16 unrecognized network-status
18018 docs. Now we can add new authdirservers and they'll be cached too.
18019 - When picking a random directory, prefer non-authorities if any
18021 - New controller option "getinfo desc/all-recent" to fetch the
18022 latest server descriptor for every router that Tor knows about.
18025 Changes in version 0.1.0.16 - 2006-01-02
18026 o Crash bugfixes on 0.1.0.x:
18027 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18028 corrupting the heap, losing FDs, or crashing when we need to resize
18029 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18030 - It turns out sparc64 platforms crash on unaligned memory access
18031 too -- so detect and avoid this.
18032 - Handle truncated compressed data correctly (by detecting it and
18034 - Fix possible-but-unlikely free(NULL) in control.c.
18035 - When we were closing connections, there was a rare case that
18036 stomped on memory, triggering seg faults and asserts.
18037 - Avoid potential infinite recursion when building a descriptor. (We
18038 don't know that it ever happened, but better to fix it anyway.)
18039 - We were neglecting to unlink marked circuits from soon-to-close OR
18040 connections, which caused some rare scribbling on freed memory.
18041 - Fix a memory stomping race bug when closing the joining point of two
18042 rendezvous circuits.
18043 - Fix an assert in time parsing found by Steven Murdoch.
18045 o Other bugfixes on 0.1.0.x:
18046 - When we're doing reachability testing, provide more useful log
18047 messages so the operator knows what to expect.
18048 - Do not check whether DirPort is reachable when we are suppressing
18049 advertising it because of hibernation.
18050 - When building with -static or on Solaris, we sometimes needed -ldl.
18051 - When we're deciding whether a stream has enough circuits around
18052 that can handle it, count the freshly dirty ones and not the ones
18053 that are so dirty they won't be able to handle it.
18054 - When we're expiring old circuits, we had a logic error that caused
18055 us to close new rendezvous circuits rather than old ones.
18056 - Give a more helpful log message when you try to change ORPort via
18057 the controller: you should upgrade Tor if you want that to work.
18058 - We were failing to parse Tor versions that start with "Tor ".
18059 - Tolerate faulty streams better: when a stream fails for reason
18060 exitpolicy, stop assuming that the router is lying about his exit
18061 policy. When a stream fails for reason misc, allow it to retry just
18062 as if it was resolvefailed. When a stream has failed three times,
18063 reset its failure count so we can try again and get all three tries.
18066 Changes in version 0.1.1.10-alpha - 2005-12-11
18067 o Correctness bugfixes on 0.1.0.x:
18068 - On Windows, build with a libevent patch from "I-M Weasel" to avoid
18069 corrupting the heap, losing FDs, or crashing when we need to resize
18070 the fd_sets. (This affects the Win32 binaries, not Tor's sources.)
18071 - Stop doing the complex voodoo overkill checking for insecure
18072 Diffie-Hellman keys. Just check if it's in [2,p-2] and be happy.
18073 - When we were closing connections, there was a rare case that
18074 stomped on memory, triggering seg faults and asserts.
18075 - We were neglecting to unlink marked circuits from soon-to-close OR
18076 connections, which caused some rare scribbling on freed memory.
18077 - When we're deciding whether a stream has enough circuits around
18078 that can handle it, count the freshly dirty ones and not the ones
18079 that are so dirty they won't be able to handle it.
18080 - Recover better from TCP connections to Tor servers that are
18081 broken but don't tell you (it happens!); and rotate TLS
18082 connections once a week.
18083 - When we're expiring old circuits, we had a logic error that caused
18084 us to close new rendezvous circuits rather than old ones.
18085 - Fix a scary-looking but apparently harmless bug where circuits
18086 would sometimes start out in state CIRCUIT_STATE_OR_WAIT at
18087 servers, and never switch to state CIRCUIT_STATE_OPEN.
18088 - When building with -static or on Solaris, we sometimes needed to
18090 - Give a useful message when people run Tor as the wrong user,
18091 rather than telling them to start chowning random directories.
18092 - We were failing to inform the controller about new .onion streams.
18094 o Security bugfixes on 0.1.0.x:
18095 - Refuse server descriptors if the fingerprint line doesn't match
18096 the included identity key. Tor doesn't care, but other apps (and
18097 humans) might actually be trusting the fingerprint line.
18098 - We used to kill the circuit when we receive a relay command we
18099 don't recognize. Now we just drop it.
18100 - Start obeying our firewall options more rigorously:
18101 . If we can't get to a dirserver directly, try going via Tor.
18102 . Don't ever try to connect (as a client) to a place our
18103 firewall options forbid.
18104 . If we specify a proxy and also firewall options, obey the
18105 firewall options even when we're using the proxy: some proxies
18106 can only proxy to certain destinations.
18107 - Fix a bug found by Lasse Overlier: when we were making internal
18108 circuits (intended to be cannibalized later for rendezvous and
18109 introduction circuits), we were picking them so that they had
18110 useful exit nodes. There was no need for this, and it actually
18111 aids some statistical attacks.
18112 - Start treating internal circuits and exit circuits separately.
18113 It's important to keep them separate because internal circuits
18114 have their last hops picked like middle hops, rather than like
18115 exit hops. So exiting on them will break the user's expectations.
18117 o Bugfixes on 0.1.1.x:
18118 - Take out the mis-feature where we tried to detect IP address
18119 flapping for people with DynDNS, and chose not to upload a new
18120 server descriptor sometimes.
18121 - Try to be compatible with OpenSSL 0.9.6 again.
18122 - Log fix: when the controller is logging about .onion addresses,
18123 sometimes it didn't include the ".onion" part of the address.
18124 - Don't try to modify options->DirServers internally -- if the
18125 user didn't specify any, just add the default ones directly to
18126 the trusted dirserver list. This fixes a bug where people running
18127 controllers would use SETCONF on some totally unrelated config
18128 option, and Tor would start yelling at them about changing their
18130 - Let the controller's redirectstream command specify a port, in
18131 case the controller wants to change that too.
18132 - When we requested a pile of server descriptors, we sometimes
18133 accidentally launched a duplicate request for the first one.
18134 - Bugfix for trackhostexits: write down the fingerprint of the
18135 chosen exit, not its nickname, because the chosen exit might not
18137 - When parsing foo.exit, if foo is unknown, and we are leaving
18138 circuits unattached, set the chosen_exit field and leave the
18139 address empty. This matters because controllers got confused
18141 - Directory authorities no longer try to download server
18142 descriptors that they know they will reject.
18144 o Features and updates:
18145 - Replace balanced trees with hash tables: this should make stuff
18146 significantly faster.
18147 - Resume using the AES counter-mode implementation that we ship,
18148 rather than OpenSSL's. Ours is significantly faster.
18149 - Many other CPU and memory improvements.
18150 - Add a new config option FastFirstHopPK (on by default) so clients
18151 do a trivial crypto handshake for their first hop, since TLS has
18152 already taken care of confidentiality and authentication.
18153 - Add a new config option TestSocks so people can see if their
18154 applications are using socks4, socks4a, socks5-with-ip, or
18155 socks5-with-hostname. This way they don't have to keep mucking
18156 with tcpdump and wondering if something got cached somewhere.
18157 - Warn when listening on a public address for socks. I suspect a
18158 lot of people are setting themselves up as open socks proxies,
18159 and they have no idea that jerks on the Internet are using them,
18160 since they simply proxy the traffic into the Tor network.
18161 - Add "private:*" as an alias in configuration for policies. Now
18162 you can simplify your exit policy rather than needing to list
18163 every single internal or nonroutable network space.
18164 - Add a new controller event type that allows controllers to get
18165 all server descriptors that were uploaded to a router in its role
18166 as authoritative dirserver.
18167 - Start shipping socks-extensions.txt, tor-doc-unix.html,
18168 tor-doc-server.html, and stylesheet.css in the tarball.
18169 - Stop shipping tor-doc.html in the tarball.
18172 Changes in version 0.1.1.9-alpha - 2005-11-15
18173 o Usability improvements:
18174 - Start calling it FooListenAddress rather than FooBindAddress,
18175 since few of our users know what it means to bind an address
18177 - Reduce clutter in server logs. We're going to try to make
18178 them actually usable now. New config option ProtocolWarnings that
18179 lets you hear about how _other Tors_ are breaking the protocol. Off
18181 - Divide log messages into logging domains. Once we put some sort
18182 of interface on this, it will let people looking at more verbose
18183 log levels specify the topics they want to hear more about.
18184 - Make directory servers return better http 404 error messages
18185 instead of a generic "Servers unavailable".
18186 - Check for even more Windows version flags when writing the platform
18187 string in server descriptors, and note any we don't recognize.
18188 - Clean up more of the OpenSSL memory when exiting, so we can detect
18189 memory leaks better.
18190 - Make directory authorities be non-versioning, non-naming by
18191 default. Now we can add new directory servers without requiring
18192 their operators to pay close attention.
18193 - When logging via syslog, include the pid whenever we provide
18194 a log entry. Suggested by Todd Fries.
18196 o Performance improvements:
18197 - Directory servers now silently throw away new descriptors that
18198 haven't changed much if the timestamps are similar. We do this to
18199 tolerate older Tor servers that upload a new descriptor every 15
18200 minutes. (It seemed like a good idea at the time.)
18201 - Inline bottleneck smartlist functions; use fast versions by default.
18202 - Add a "Map from digest to void*" abstraction digestmap_t so we
18203 can do less hex encoding/decoding. Use it in router_get_by_digest()
18204 to resolve a performance bottleneck.
18205 - Allow tor_gzip_uncompress to extract as much as possible from
18206 truncated compressed data. Try to extract as many
18207 descriptors as possible from truncated http responses (when
18208 DIR_PURPOSE_FETCH_ROUTERDESC).
18209 - Make circ->onionskin a pointer, not a static array. moria2 was using
18210 125000 circuit_t's after it had been up for a few weeks, which
18211 translates to 20+ megs of wasted space.
18212 - The private half of our EDH handshake keys are now chosen out
18213 of 320 bits, not 1024 bits. (Suggested by Ian Goldberg.)
18215 o Security improvements:
18216 - Start making directory caches retain old routerinfos, so soon
18217 clients can start asking by digest of descriptor rather than by
18218 fingerprint of server.
18219 - Add half our entropy from RAND_poll in OpenSSL. This knows how
18220 to use egd (if present), openbsd weirdness (if present), vms/os2
18221 weirdness (if we ever port there), and more in the future.
18223 o Bugfixes on 0.1.0.x:
18224 - Do round-robin writes of at most 16 kB per write. This might be
18225 more fair on loaded Tor servers, and it might resolve our Windows
18226 crash bug. It might also slow things down.
18227 - Our TLS handshakes were generating a single public/private
18228 keypair for the TLS context, rather than making a new one for
18229 each new connections. Oops. (But we were still rotating them
18230 periodically, so it's not so bad.)
18231 - When we were cannibalizing a circuit with a particular exit
18232 node in mind, we weren't checking to see if that exit node was
18233 already present earlier in the circuit. Oops.
18234 - When a Tor server's IP changes (e.g. from a dyndns address),
18235 upload a new descriptor so clients will learn too.
18236 - Really busy servers were keeping enough circuits open on stable
18237 connections that they were wrapping around the circuit_id
18238 space. (It's only two bytes.) This exposed a bug where we would
18239 feel free to reuse a circuit_id even if it still exists but has
18240 been marked for close. Try to fix this bug. Some bug remains.
18241 - If we would close a stream early (e.g. it asks for a .exit that
18242 we know would refuse it) but the LeaveStreamsUnattached config
18243 option is set by the controller, then don't close it.
18245 o Bugfixes on 0.1.1.8-alpha:
18246 - Fix a big pile of memory leaks, some of them serious.
18247 - Do not try to download a routerdesc if we would immediately reject
18249 - Resume inserting a newline between all router descriptors when
18250 generating (old style) signed directories, since our spec says
18252 - When providing content-type application/octet-stream for
18253 server descriptors using .z, we were leaving out the
18254 content-encoding header. Oops. (Everything tolerated this just
18255 fine, but that doesn't mean we need to be part of the problem.)
18256 - Fix a potential seg fault in getconf and getinfo using version 1
18257 of the controller protocol.
18258 - Avoid crash: do not check whether DirPort is reachable when we
18259 are suppressing it because of hibernation.
18260 - Make --hash-password not crash on exit.
18263 Changes in version 0.1.1.8-alpha - 2005-10-07
18264 o New features (major):
18265 - Clients don't download or use the directory anymore. Now they
18266 download and use network-statuses from the trusted dirservers,
18267 and fetch individual server descriptors as needed from mirrors.
18268 See dir-spec.txt for all the gory details.
18269 - Be more conservative about whether to advertise our DirPort.
18270 The main change is to not advertise if we're running at capacity
18271 and either a) we could hibernate or b) our capacity is low and
18272 we're using a default DirPort.
18273 - Use OpenSSL's AES when OpenSSL has version 0.9.7 or later.
18275 o New features (minor):
18276 - Try to be smart about when to retry network-status and
18277 server-descriptor fetches. Still needs some tuning.
18278 - Stop parsing, storing, or using running-routers output (but
18279 mirrors still cache and serve it).
18280 - Consider a threshold of versioning dirservers (dirservers who have
18281 an opinion about which Tor versions are still recommended) before
18282 deciding whether to warn the user that he's obsolete.
18283 - Dirservers can now reject/invalidate by key and IP, with the
18284 config options "AuthDirInvalid" and "AuthDirReject". This is
18285 useful since currently we automatically list servers as running
18286 and usable even if we know they're jerks.
18287 - Provide dire warnings to any users who set DirServer; move it out
18288 of torrc.sample and into torrc.complete.
18289 - Add MyFamily to torrc.sample in the server section.
18290 - Add nicknames to the DirServer line, so we can refer to them
18291 without requiring all our users to memorize their IP addresses.
18292 - When we get an EOF or a timeout on a directory connection, note
18293 how many bytes of serverdesc we are dropping. This will help
18294 us determine whether it is smart to parse incomplete serverdesc
18296 - Add a new function to "change pseudonyms" -- that is, to stop
18297 using any currently-dirty circuits for new streams, so we don't
18298 link new actions to old actions. Currently it's only called on
18299 HUP (or SIGNAL RELOAD).
18300 - On sighup, if UseHelperNodes changed to 1, use new circuits.
18301 - Start using RAND_bytes rather than RAND_pseudo_bytes from
18302 OpenSSL. Also, reseed our entropy every hour, not just at
18303 startup. And entropy in 512-bit chunks, not 160-bit chunks.
18305 o Fixes on 0.1.1.7-alpha:
18306 - Nobody ever implemented EVENT_ADDRMAP for control protocol
18307 version 0, so don't let version 0 controllers ask for it.
18308 - If you requested something with too many newlines via the
18309 v1 controller protocol, you could crash tor.
18310 - Fix a number of memory leaks, including some pretty serious ones.
18311 - Re-enable DirPort testing again, so Tor servers will be willing
18312 to advertise their DirPort if it's reachable.
18313 - On TLS handshake, only check the other router's nickname against
18314 its expected nickname if is_named is set.
18316 o Fixes forward-ported from 0.1.0.15:
18317 - Don't crash when we don't have any spare file descriptors and we
18318 try to spawn a dns or cpu worker.
18319 - Make the numbers in read-history and write-history into uint64s,
18320 so they don't overflow and publish negatives in the descriptor.
18322 o Fixes on 0.1.0.x:
18323 - For the OS X package's modified privoxy config file, comment
18324 out the "logfile" line so we don't log everything passed
18326 - We were whining about using socks4 or socks5-with-local-lookup
18327 even when it's an IP in the "virtual" range we designed exactly
18329 - We were leaking some memory every time the client changes IPs.
18330 - Never call free() on tor_malloc()d memory. This will help us
18331 use dmalloc to detect memory leaks.
18332 - Check for named servers when looking them up by nickname;
18333 warn when we'recalling a non-named server by its nickname;
18334 don't warn twice about the same name.
18335 - Try to list MyFamily elements by key, not by nickname, and warn
18336 if we've not heard of the server.
18337 - Make windows platform detection (uname equivalent) smarter.
18338 - It turns out sparc64 doesn't like unaligned access either.
18341 Changes in version 0.1.0.15 - 2005-09-23
18342 o Bugfixes on 0.1.0.x:
18343 - Reject ports 465 and 587 (spam targets) in default exit policy.
18344 - Don't crash when we don't have any spare file descriptors and we
18345 try to spawn a dns or cpu worker.
18346 - Get rid of IgnoreVersion undocumented config option, and make us
18347 only warn, never exit, when we're running an obsolete version.
18348 - Don't try to print a null string when your server finds itself to
18349 be unreachable and the Address config option is empty.
18350 - Make the numbers in read-history and write-history into uint64s,
18351 so they don't overflow and publish negatives in the descriptor.
18352 - Fix a minor memory leak in smartlist_string_remove().
18353 - We were only allowing ourselves to upload a server descriptor at
18354 most every 20 minutes, even if it changed earlier than that.
18355 - Clean up log entries that pointed to old URLs.
18358 Changes in version 0.1.1.7-alpha - 2005-09-14
18359 o Fixes on 0.1.1.6-alpha:
18360 - Exit servers were crashing when people asked them to make a
18361 connection to an address not in their exit policy.
18362 - Looking up a non-existent stream for a v1 control connection would
18364 - Fix a seg fault if we ask a dirserver for a descriptor by
18365 fingerprint but he doesn't know about him.
18366 - SETCONF was appending items to linelists, not clearing them.
18367 - SETCONF SocksBindAddress killed Tor if it fails to bind. Now back
18368 out and refuse the setconf if it would fail.
18369 - Downgrade the dirserver log messages when whining about
18373 - Add Peter Palfrader's check-tor script to tor/contrib/
18374 It lets you easily check whether a given server (referenced by
18375 nickname) is reachable by you.
18376 - Numerous changes to move towards client-side v2 directories. Not
18379 o Fixes on 0.1.0.x:
18380 - If the user gave tor an odd number of command-line arguments,
18381 we were silently ignoring the last one. Now we complain and fail.
18382 [This wins the oldest-bug prize -- this bug has been present since
18383 November 2002, as released in Tor 0.0.0.]
18384 - Do not use unaligned memory access on alpha, mips, or mipsel.
18385 It *works*, but is very slow, so we treat them as if it doesn't.
18386 - Retry directory requests if we fail to get an answer we like
18387 from a given dirserver (we were retrying before, but only if
18388 we fail to connect).
18389 - When writing the RecommendedVersions line, sort them first.
18390 - When the client asked for a rendezvous port that the hidden
18391 service didn't want to provide, we were sending an IP address
18392 back along with the end cell. Fortunately, it was zero. But stop
18394 - Correct "your server is reachable" log entries to indicate that
18395 it was self-testing that told us so.
18398 Changes in version 0.1.1.6-alpha - 2005-09-09
18399 o Fixes on 0.1.1.5-alpha:
18400 - We broke fascistfirewall in 0.1.1.5-alpha. Oops.
18401 - Fix segfault in unit tests in 0.1.1.5-alpha. Oops.
18402 - Fix bug with tor_memmem finding a match at the end of the string.
18403 - Make unit tests run without segfaulting.
18404 - Resolve some solaris x86 compile warnings.
18405 - Handle duplicate lines in approved-routers files without warning.
18406 - Fix bug where as soon as a server refused any requests due to his
18407 exit policy (e.g. when we ask for localhost and he tells us that's
18408 127.0.0.1 and he won't do it), we decided he wasn't obeying his
18409 exit policy using him for any exits.
18410 - Only do openssl hardware accelerator stuff if openssl version is
18413 o New controller features/fixes:
18414 - Add a "RESETCONF" command so you can set config options like
18415 AllowUnverifiedNodes and LongLivedPorts to "". Also, if you give
18416 a config option in the torrc with no value, then it clears it
18417 entirely (rather than setting it to its default).
18418 - Add a "GETINFO config-file" to tell us where torrc is.
18419 - Avoid sending blank lines when GETINFO replies should be empty.
18420 - Add a QUIT command for the controller (for using it manually).
18421 - Fix a bug in SAVECONF that was adding default dirservers and
18422 other redundant entries to the torrc file.
18424 o Start on the new directory design:
18425 - Generate, publish, cache, serve new network-status format.
18426 - Publish individual descriptors (by fingerprint, by "all", and by
18428 - Publish client and server recommended versions separately.
18429 - Allow tor_gzip_uncompress() to handle multiple concatenated
18430 compressed strings. Serve compressed groups of router
18431 descriptors. The compression logic here could be more
18433 - Distinguish v1 authorities (all currently trusted directories)
18434 from v2 authorities (all trusted directories).
18435 - Change DirServers config line to note which dirs are v1 authorities.
18436 - Add configuration option "V1AuthoritativeDirectory 1" which
18437 moria1, moria2, and tor26 should set.
18438 - Remove option when getting directory cache to see whether they
18439 support running-routers; they all do now. Replace it with one
18440 to see whether caches support v2 stuff.
18443 - Dirservers now do their own external reachability testing of each
18444 Tor server, and only list them as running if they've been found to
18445 be reachable. We also send back warnings to the server's logs if
18446 it uploads a descriptor that we already believe is unreachable.
18447 - Implement exit enclaves: if we know an IP address for the
18448 destination, and there's a running Tor server at that address
18449 which allows exit to the destination, then extend the circuit to
18450 that exit first. This provides end-to-end encryption and end-to-end
18451 authentication. Also, if the user wants a .exit address or enclave,
18452 use 4 hops rather than 3, and cannibalize a general circ for it
18454 - Permit transitioning from ORPort=0 to ORPort!=0, and back, from the
18455 controller. Also, rotate dns and cpu workers if the controller
18456 changes options that will affect them; and initialize the dns
18457 worker cache tree whether or not we start out as a server.
18458 - Only upload a new server descriptor when options change, 18
18459 hours have passed, uptime is reset, or bandwidth changes a lot.
18460 - Check [X-]Forwarded-For headers in HTTP requests when generating
18461 log messages. This lets people run dirservers (and caches) behind
18462 Apache but still know which IP addresses are causing warnings.
18464 o Config option changes:
18465 - Replace (Fascist)Firewall* config options with a new
18466 ReachableAddresses option that understands address policies.
18467 For example, "ReachableAddresses *:80,*:443"
18468 - Get rid of IgnoreVersion undocumented config option, and make us
18469 only warn, never exit, when we're running an obsolete version.
18470 - Make MonthlyAccountingStart config option truly obsolete now.
18472 o Fixes on 0.1.0.x:
18473 - Reject ports 465 and 587 in the default exit policy, since
18474 people have started using them for spam too.
18475 - It turns out we couldn't bootstrap a network since we added
18476 reachability detection in 0.1.0.1-rc. Good thing the Tor network
18477 has never gone down. Add an AssumeReachable config option to let
18478 servers and dirservers bootstrap. When we're trying to build a
18479 high-uptime or high-bandwidth circuit but there aren't enough
18480 suitable servers, try being less picky rather than simply failing.
18481 - Our logic to decide if the OR we connected to was the right guy
18482 was brittle and maybe open to a mitm for unverified routers.
18483 - We weren't cannibalizing circuits correctly for
18484 CIRCUIT_PURPOSE_C_ESTABLISH_REND and
18485 CIRCUIT_PURPOSE_S_ESTABLISH_INTRO, so we were being forced to
18486 build those from scratch. This should make hidden services faster.
18487 - Predict required circuits better, with an eye toward making hidden
18488 services faster on the service end.
18489 - Retry streams if the exit node sends back a 'misc' failure. This
18490 should result in fewer random failures. Also, after failing
18491 from resolve failed or misc, reset the num failures, so we give
18492 it a fair shake next time we try.
18493 - Clean up the rendezvous warn log msgs, and downgrade some to info.
18494 - Reduce severity on logs about dns worker spawning and culling.
18495 - When we're shutting down and we do something like try to post a
18496 server descriptor or rendezvous descriptor, don't complain that
18497 we seem to be unreachable. Of course we are, we're shutting down.
18498 - Add TTLs to RESOLVED, CONNECTED, and END_REASON_EXITPOLICY cells.
18499 We don't use them yet, but maybe one day our DNS resolver will be
18500 able to discover them.
18501 - Make ContactInfo mandatory for authoritative directory servers.
18502 - Require server descriptors to list IPv4 addresses -- hostnames
18503 are no longer allowed. This also fixes some potential security
18504 problems with people providing hostnames as their address and then
18505 preferentially resolving them to partition users.
18506 - Change log line for unreachability to explicitly suggest /etc/hosts
18507 as the culprit. Also make it clearer what IP address and ports we're
18508 testing for reachability.
18509 - Put quotes around user-supplied strings when logging so users are
18510 more likely to realize if they add bad characters (like quotes)
18512 - Let auth dir servers start without specifying an Address config
18514 - Make unit tests (and other invocations that aren't the real Tor)
18515 run without launching listeners, creating subdirectories, and so on.
18518 Changes in version 0.1.1.5-alpha - 2005-08-08
18519 o Bugfixes included in 0.1.0.14.
18521 o Bugfixes on 0.1.0.x:
18522 - If you write "HiddenServicePort 6667 127.0.0.1 6668" in your
18523 torrc rather than "HiddenServicePort 6667 127.0.0.1:6668",
18524 it would silently using ignore the 6668.
18527 Changes in version 0.1.0.14 - 2005-08-08
18528 o Bugfixes on 0.1.0.x:
18529 - Fix the other half of the bug with crypto handshakes
18531 - Fix an assert trigger if you send a 'signal term' via the
18532 controller when it's listening for 'event info' messages.
18535 Changes in version 0.1.1.4-alpha - 2005-08-04
18536 o Bugfixes included in 0.1.0.13.
18539 - Improve tor_gettimeofday() granularity on windows.
18540 - Make clients regenerate their keys when their IP address changes.
18541 - Implement some more GETINFO goodness: expose helper nodes, config
18542 options, getinfo keys.
18545 Changes in version 0.1.0.13 - 2005-08-04
18546 o Bugfixes on 0.1.0.x:
18547 - Fix a critical bug in the security of our crypto handshakes.
18548 - Fix a size_t underflow in smartlist_join_strings2() that made
18549 it do bad things when you hand it an empty smartlist.
18550 - Fix Windows installer to ship Tor license (thanks to Aphex for
18551 pointing out this oversight) and put a link to the doc directory
18553 - Explicitly set no-unaligned-access for sparc: it turns out the
18554 new gcc's let you compile broken code, but that doesn't make it
18558 Changes in version 0.1.1.3-alpha - 2005-07-23
18559 o Bugfixes on 0.1.1.2-alpha:
18560 - Fix a bug in handling the controller's "post descriptor"
18562 - Fix several bugs in handling the controller's "extend circuit"
18564 - Fix a bug in handling the controller's "stream status" event.
18565 - Fix an assert failure if we have a controller listening for
18566 circuit events and we go offline.
18567 - Re-allow hidden service descriptors to publish 0 intro points.
18568 - Fix a crash when generating your hidden service descriptor if
18569 you don't have enough intro points already.
18571 o New features on 0.1.1.2-alpha:
18572 - New controller function "getinfo accounting", to ask how
18573 many bytes we've used in this time period.
18574 - Experimental support for helper nodes: a lot of the risk from
18575 a small static adversary comes because users pick new random
18576 nodes every time they rebuild a circuit. Now users will try to
18577 stick to the same small set of entry nodes if they can. Not
18578 enabled by default yet.
18580 o Bugfixes on 0.1.0.12:
18581 - If you're an auth dir server, always publish your dirport,
18582 even if you haven't yet found yourself to be reachable.
18583 - Fix a size_t underflow in smartlist_join_strings2() that made
18584 it do bad things when you hand it an empty smartlist.
18587 Changes in version 0.1.0.12 - 2005-07-18
18588 o New directory servers:
18589 - tor26 has changed IP address.
18591 o Bugfixes on 0.1.0.x:
18592 - Fix a possible double-free in tor_gzip_uncompress().
18593 - When --disable-threads is set, do not search for or link against
18594 pthreads libraries.
18595 - Don't trigger an assert if an authoritative directory server
18596 claims its dirport is 0.
18597 - Fix bug with removing Tor as an NT service: some people were
18598 getting "The service did not return an error." Thanks to Matt
18602 Changes in version 0.1.1.2-alpha - 2005-07-15
18603 o New directory servers:
18604 - tor26 has changed IP address.
18606 o Bugfixes on 0.1.0.x, crashes/leaks:
18607 - Port the servers-not-obeying-their-exit-policies fix from
18609 - Fix an fd leak in start_daemon().
18610 - On Windows, you can't always reopen a port right after you've
18611 closed it. So change retry_listeners() to only close and re-open
18612 ports that have changed.
18613 - Fix a possible double-free in tor_gzip_uncompress().
18615 o Bugfixes on 0.1.0.x, usability:
18616 - When tor_socketpair() fails in Windows, give a reasonable
18617 Windows-style errno back.
18618 - Let people type "tor --install" as well as "tor -install" when
18620 want to make it an NT service.
18621 - NT service patch from Matt Edman to improve error messages.
18622 - When the controller asks for a config option with an abbreviated
18623 name, give the full name in our response.
18624 - Correct the man page entry on TrackHostExitsExpire.
18625 - Looks like we were never delivering deflated (i.e. compressed)
18626 running-routers lists, even when asked. Oops.
18627 - When --disable-threads is set, do not search for or link against
18628 pthreads libraries.
18630 o Bugfixes on 0.1.1.x:
18631 - Fix a seg fault with autodetecting which controller version is
18635 - New hidden service descriptor format: put a version in it, and
18636 let people specify introduction/rendezvous points that aren't
18637 in "the directory" (which is subjective anyway).
18638 - Allow the DEBUG controller event to work again. Mark certain log
18639 entries as "don't tell this to controllers", so we avoid cycles.
18642 Changes in version 0.1.0.11 - 2005-06-30
18643 o Bugfixes on 0.1.0.x:
18644 - Fix major security bug: servers were disregarding their
18645 exit policies if clients behaved unexpectedly.
18646 - Make OS X init script check for missing argument, so we don't
18647 confuse users who invoke it incorrectly.
18648 - Fix a seg fault in "tor --hash-password foo".
18649 - The MAPADDRESS control command was broken.
18652 Changes in version 0.1.1.1-alpha - 2005-06-29
18654 - Make OS X init script check for missing argument, so we don't
18655 confuse users who invoke it incorrectly.
18656 - Fix a seg fault in "tor --hash-password foo".
18657 - Fix a possible way to DoS dirservers.
18658 - When we complain that your exit policy implicitly allows local or
18659 private address spaces, name them explicitly so operators can
18661 - Make the log message less scary when all the dirservers are
18662 temporarily unreachable.
18663 - We were printing the number of idle dns workers incorrectly when
18667 - Revised controller protocol (version 1) that uses ascii rather
18668 than binary. Add supporting libraries in python and java so you
18669 can use the controller from your applications without caring how
18670 our protocol works.
18671 - Spiffy new support for crypto hardware accelerators. Can somebody
18675 Changes in version 0.0.9.10 - 2005-06-16
18676 o Bugfixes on 0.0.9.x (backported from 0.1.0.10):
18677 - Refuse relay cells that claim to have a length larger than the
18678 maximum allowed. This prevents a potential attack that could read
18679 arbitrary memory (e.g. keys) from an exit server's process
18683 Changes in version 0.1.0.10 - 2005-06-14
18684 o Allow a few EINVALs from libevent before dying. Warn on kqueue with
18685 libevent before 1.1a.
18688 Changes in version 0.1.0.9-rc - 2005-06-09
18690 - Reset buf->highwater every time buf_shrink() is called, not just on
18691 a successful shrink. This was causing significant memory bloat.
18692 - Fix buffer overflow when checking hashed passwords.
18693 - Security fix: if seeding the RNG on Win32 fails, quit.
18694 - Allow seeding the RNG on Win32 even when you're not running as
18696 - Disable threading on Solaris too. Something is wonky with it,
18697 cpuworkers, and reentrant libs.
18698 - Reenable the part of the code that tries to flush as soon as an
18699 OR outbuf has a full TLS record available. Perhaps this will make
18700 OR outbufs not grow as huge except in rare cases, thus saving lots
18701 of CPU time plus memory.
18702 - Reject malformed .onion addresses rather then passing them on as
18703 normal web requests.
18704 - Adapt patch from Adam Langley: fix possible memory leak in
18705 tor_lookup_hostname().
18706 - Initialize libevent later in the startup process, so the logs are
18707 already established by the time we start logging libevent warns.
18708 - Use correct errno on win32 if libevent fails.
18709 - Check and warn about known-bad/slow libevent versions.
18710 - Pay more attention to the ClientOnly config option.
18711 - Have torctl.in/tor.sh.in check for location of su binary (needed
18713 - Correct/add man page entries for LongLivedPorts, ExitPolicy,
18714 KeepalivePeriod, ClientOnly, NoPublish, HttpProxy, HttpsProxy,
18715 HttpProxyAuthenticator
18716 - Stop warning about sigpipes in the logs. We're going to
18717 pretend that getting these occassionally is normal and fine.
18718 - Resolve OS X installer bugs: stop claiming to be 0.0.9.2 in
18720 installer screens; and don't put stuff into StartupItems unless
18721 the user asks you to.
18722 - Require servers that use the default dirservers to have public IP
18723 addresses. We have too many servers that are configured with private
18724 IPs and their admins never notice the log entries complaining that
18725 their descriptors are being rejected.
18726 - Add OSX uninstall instructions. An actual uninstall script will
18730 Changes in version 0.1.0.8-rc - 2005-05-23
18732 - It turns out that kqueue on OS X 10.3.9 was causing kernel
18733 panics. Disable kqueue on all OS X Tors.
18734 - Fix RPM: remove duplicate line accidentally added to the rpm
18736 - Disable threads on openbsd too, since its gethostaddr is not
18738 - Tolerate libevent 0.8 since it still works, even though it's
18740 - Enable building on Red Hat 9.0 again.
18741 - Allow the middle hop of the testing circuit to be running any
18742 version, now that most of them have the bugfix to let them connect
18743 to unknown servers. This will allow reachability testing to work
18744 even when 0.0.9.7-0.0.9.9 become obsolete.
18745 - Handle relay cells with rh.length too large. This prevents
18746 a potential attack that could read arbitrary memory (maybe even
18747 keys) from the exit server's process.
18748 - We screwed up the dirport reachability testing when we don't yet
18749 have a cached version of the directory. Hopefully now fixed.
18750 - Clean up router_load_single_router() (used by the controller),
18751 so it doesn't seg fault on error.
18752 - Fix a minor memory leak when somebody establishes an introduction
18753 point at your Tor server.
18754 - If a socks connection ends because read fails, don't warn that
18755 you're not sending a socks reply back.
18758 - Add HttpProxyAuthenticator config option too, that works like
18759 the HttpsProxyAuthenticator config option.
18760 - Encode hashed controller passwords in hex instead of base64,
18761 to make it easier to write controllers.
18764 Changes in version 0.1.0.7-rc - 2005-05-17
18766 - Fix a bug in the OS X package installer that prevented it from
18767 installing on Tiger.
18768 - Fix a script bug in the OS X package installer that made it
18769 complain during installation.
18770 - Find libevent even if it's hiding in /usr/local/ and your
18771 CFLAGS and LDFLAGS don't tell you to look there.
18772 - Be able to link with libevent as a shared library (the default
18773 after 1.0d), even if it's hiding in /usr/local/lib and even
18774 if you haven't added /usr/local/lib to your /etc/ld.so.conf,
18775 assuming you're running gcc. Otherwise fail and give a useful
18777 - Fix a bug in the RPM packager: set home directory for _tor to
18778 something more reasonable when first installing.
18779 - Free a minor amount of memory that is still reachable on exit.
18782 Changes in version 0.1.0.6-rc - 2005-05-14
18784 - Implement --disable-threads configure option. Disable threads on
18785 netbsd by default, because it appears to have no reentrant resolver
18787 - Apple's OS X 10.4.0 ships with a broken kqueue. The new libevent
18788 release (1.1) detects and disables kqueue if it's broken.
18789 - Append default exit policy before checking for implicit internal
18790 addresses. Now we don't log a bunch of complaints on startup
18791 when using the default exit policy.
18792 - Some people were putting "Address " in their torrc, and they had
18793 a buggy resolver that resolved " " to 0.0.0.0. Oops.
18794 - If DataDir is ~/.tor, and that expands to /.tor, then default to
18795 LOCALSTATEDIR/tor instead.
18796 - Fix fragmented-message bug in TorControl.py.
18797 - Resolve a minor bug which would prevent unreachable dirports
18798 from getting suppressed in the published descriptor.
18799 - When the controller gave us a new descriptor, we weren't resolving
18800 it immediately, so Tor would think its address was 0.0.0.0 until
18801 we fetched a new directory.
18802 - Fix an uppercase/lowercase case error in suppressing a bogus
18803 libevent warning on some Linuxes.
18806 - Begin scrubbing sensitive strings from logs by default. Turn off
18807 the config option SafeLogging if you need to do debugging.
18808 - Switch to a new buffer management algorithm, which tries to avoid
18809 reallocing and copying quite as much. In first tests it looks like
18810 it uses *more* memory on average, but less cpu.
18811 - First cut at support for "create-fast" cells. Clients can use
18812 these when extending to their first hop, since the TLS already
18813 provides forward secrecy and authentication. Not enabled on
18815 - When dirservers refuse a router descriptor, we now log its
18816 contactinfo, platform, and the poster's IP address.
18817 - Call tor_free_all instead of connections_free_all after forking, to
18818 save memory on systems that need to fork.
18819 - Whine at you if you're a server and you don't set your contactinfo.
18820 - Implement --verify-config command-line option to check if your torrc
18821 is valid without actually launching Tor.
18822 - Rewrite address "serifos.exit" to "localhost.serifos.exit"
18823 rather than just rejecting it.
18826 Changes in version 0.1.0.5-rc - 2005-04-27
18828 - Stop trying to print a null pointer if an OR conn fails because
18829 we didn't like its cert.
18831 - Switch our internal buffers implementation to use a ring buffer,
18832 to hopefully improve performance for fast servers a lot.
18833 - Add HttpsProxyAuthenticator support (basic auth only), based
18834 on patch from Adam Langley.
18835 - Bump the default BandwidthRate from 1 MB to 2 MB, to accommodate
18836 the fast servers that have been joining lately.
18837 - Give hidden service accesses extra time on the first attempt,
18838 since 60 seconds is often only barely enough. This might improve
18840 - Improve performance for dirservers: stop re-parsing the whole
18841 directory every time you regenerate it.
18842 - Add more debugging info to help us find the weird dns freebsd
18843 pthreads bug; cleaner debug messages to help track future issues.
18846 Changes in version 0.0.9.9 - 2005-04-23
18847 o Bugfixes on 0.0.9.x:
18848 - If unofficial Tor clients connect and send weird TLS certs, our
18849 Tor server triggers an assert. This release contains a minimal
18850 backport from the broader fix that we put into 0.1.0.4-rc.
18853 Changes in version 0.1.0.4-rc - 2005-04-23
18855 - If unofficial Tor clients connect and send weird TLS certs, our
18856 Tor server triggers an assert. Stop asserting, and start handling
18857 TLS errors better in other situations too.
18858 - When the controller asks us to tell it about all the debug-level
18859 logs, it turns out we were generating debug-level logs while
18860 telling it about them, which turns into a bad loop. Now keep
18861 track of whether you're sending a debug log to the controller,
18862 and don't log when you are.
18863 - Fix the "postdescriptor" feature of the controller interface: on
18864 non-complete success, only say "done" once.
18866 - Clients are now willing to load balance over up to 2mB, not 1mB,
18867 of advertised bandwidth capacity.
18868 - Add a NoPublish config option, so you can be a server (e.g. for
18869 testing running Tor servers in other Tor networks) without
18870 publishing your descriptor to the primary dirservers.
18873 Changes in version 0.1.0.3-rc - 2005-04-08
18874 o Improvements on 0.1.0.2-rc:
18875 - Client now retries when streams end early for 'hibernating' or
18876 'resource limit' reasons, rather than failing them.
18877 - More automated handling for dirserver operators:
18878 - Automatically approve nodes running 0.1.0.2-rc or later,
18879 now that the the reachability detection stuff is working.
18880 - Now we allow two unverified servers with the same nickname
18881 but different keys. But if a nickname is verified, only that
18882 nickname+key are allowed.
18883 - If you're an authdirserver connecting to an address:port,
18884 and it's not the OR you were expecting, forget about that
18885 descriptor. If he *was* the one you were expecting, then forget
18886 about all other descriptors for that address:port.
18887 - Allow servers to publish descriptors from 12 hours in the future.
18888 Corollary: only whine about clock skew from the dirserver if
18889 he's a trusted dirserver (since now even verified servers could
18890 have quite wrong clocks).
18891 - Adjust maximum skew and age for rendezvous descriptors: let skew
18892 be 48 hours rather than 90 minutes.
18893 - Efficiency improvements:
18894 - Keep a big splay tree of (circid,orconn)->circuit mappings to make
18895 it much faster to look up a circuit for each relay cell.
18896 - Remove most calls to assert_all_pending_dns_resolves_ok(),
18897 since they're eating our cpu on exit nodes.
18898 - Stop wasting time doing a case insensitive comparison for every
18899 dns name every time we do any lookup. Canonicalize the names to
18900 lowercase and be done with it.
18901 - Start sending 'truncated' cells back rather than destroy cells,
18902 if the circuit closes in front of you. This means we won't have
18903 to abandon partially built circuits.
18904 - Only warn once per nickname from add_nickname_list_to_smartlist
18905 per failure, so an entrynode or exitnode choice that's down won't
18907 - Put a note in the torrc about abuse potential with the default
18909 - Revise control spec and implementation to allow all log messages to
18910 be sent to controller with their severities intact (suggested by
18911 Matt Edman). Update TorControl to handle new log event types.
18912 - Provide better explanation messages when controller's POSTDESCRIPTOR
18914 - Stop putting nodename in the Platform string in server descriptors.
18915 It doesn't actually help, and it is confusing/upsetting some people.
18917 o Bugfixes on 0.1.0.2-rc:
18918 - We were printing the host mask wrong in exit policies in server
18919 descriptors. This isn't a critical bug though, since we were still
18920 obeying the exit policy internally.
18921 - Fix Tor when compiled with libevent but without pthreads: move
18922 connection_unregister() from _connection_free() to
18924 - Fix an assert trigger (already fixed in 0.0.9.x): when we have
18925 the rare mysterious case of accepting a conn on 0.0.0.0:0, then
18926 when we look through the connection array, we'll find any of the
18927 cpu/dnsworkers. This is no good.
18929 o Bugfixes on 0.0.9.8:
18930 - Fix possible bug on threading platforms (e.g. win32) which was
18931 leaking a file descriptor whenever a cpuworker or dnsworker died.
18932 - When using preferred entry or exit nodes, ignore whether the
18933 circuit wants uptime or capacity. They asked for the nodes, they
18935 - chdir() to your datadirectory at the *end* of the daemonize process,
18936 not the beginning. This was a problem because the first time you
18937 run tor, if your datadir isn't there, and you have runasdaemon set
18938 to 1, it will try to chdir to it before it tries to create it. Oops.
18939 - Handle changed router status correctly when dirserver reloads
18940 fingerprint file. We used to be dropping all unverified descriptors
18941 right then. The bug was hidden because we would immediately
18942 fetch a directory from another dirserver, which would include the
18943 descriptors we just dropped.
18944 - When we're connecting to an OR and he's got a different nickname/key
18945 than we were expecting, only complain loudly if we're an OP or a
18946 dirserver. Complaining loudly to the OR admins just confuses them.
18947 - Tie MAX_DIR_SIZE to MAX_BUF_SIZE, so now directory sizes won't get
18948 artificially capped at 500kB.
18951 Changes in version 0.0.9.8 - 2005-04-07
18952 o Bugfixes on 0.0.9.x:
18953 - We have a bug that I haven't found yet. Sometimes, very rarely,
18954 cpuworkers get stuck in the 'busy' state, even though the cpuworker
18955 thinks of itself as idle. This meant that no new circuits ever got
18956 established. Here's a workaround to kill any cpuworker that's been
18957 busy for more than 100 seconds.
18960 Changes in version 0.1.0.2-rc - 2005-04-01
18961 o Bugfixes on 0.1.0.1-rc:
18962 - Fixes on reachability detection:
18963 - Don't check for reachability while hibernating.
18964 - If ORPort is reachable but DirPort isn't, still publish the
18965 descriptor, but zero out DirPort until it's found reachable.
18966 - When building testing circs for ORPort testing, use only
18967 high-bandwidth nodes, so fewer circuits fail.
18968 - Complain about unreachable ORPort separately from unreachable
18969 DirPort, so the user knows what's going on.
18970 - Make sure we only conclude ORPort reachability if we didn't
18971 initiate the conn. Otherwise we could falsely conclude that
18972 we're reachable just because we connected to the guy earlier
18973 and he used that same pipe to extend to us.
18974 - Authdirservers shouldn't do ORPort reachability detection,
18975 since they're in clique mode, so it will be rare to find a
18976 server not already connected to them.
18977 - When building testing circuits, always pick middle hops running
18978 Tor 0.0.9.7, so we avoid the "can't extend to unknown routers"
18979 bug. (This is a kludge; it will go away when 0.0.9.x becomes
18981 - When we decide we're reachable, actually publish our descriptor
18983 - Fix bug in redirectstream in the controller.
18984 - Fix the state descriptor strings so logs don't claim edge streams
18985 are in a different state than they actually are.
18986 - Use recent libevent features when possible (this only really affects
18987 win32 and osx right now, because the new libevent with these
18988 features hasn't been released yet). Add code to suppress spurious
18990 - Prevent possible segfault in connection_close_unattached_ap().
18991 - Fix newlines on torrc in win32.
18992 - Improve error msgs when tor-resolve fails.
18994 o Improvements on 0.0.9.x:
18995 - New experimental script tor/contrib/ExerciseServer.py (needs more
18996 work) that uses the controller interface to build circuits and
18997 fetch pages over them. This will help us bootstrap servers that
18998 have lots of capacity but haven't noticed it yet.
18999 - New experimental script tor/contrib/PathDemo.py (needs more work)
19000 that uses the controller interface to let you choose whole paths
19002 "<hostname>.<path,separated by dots>.<length of path>.path"
19003 - When we've connected to an OR and handshaked but didn't like
19004 the result, we were closing the conn without sending destroy
19005 cells back for pending circuits. Now send those destroys.
19008 Changes in version 0.0.9.7 - 2005-04-01
19009 o Bugfixes on 0.0.9.x:
19010 - Fix another race crash bug (thanks to Glenn Fink for reporting).
19011 - Compare identity to identity, not to nickname, when extending to
19012 a router not already in the directory. This was preventing us from
19013 extending to unknown routers. Oops.
19014 - Make sure to create OS X Tor user in <500 range, so we aren't
19015 creating actual system users.
19016 - Note where connection-that-hasn't-sent-end was marked, and fix
19017 a few really loud instances of this harmless bug (it's fixed more
19021 Changes in version 0.1.0.1-rc - 2005-03-28
19023 - Add reachability testing. Your Tor server will automatically try
19024 to see if its ORPort and DirPort are reachable from the outside,
19025 and it won't upload its descriptor until it decides they are.
19026 - Handle unavailable hidden services better. Handle slow or busy
19027 hidden services better.
19028 - Add support for CONNECTing through https proxies, with "HttpsProxy"
19030 - New exit policy: accept most low-numbered ports, rather than
19031 rejecting most low-numbered ports.
19032 - More Tor controller support (still experimental). See
19033 http://tor.eff.org/doc/control-spec.txt for all the new features,
19034 including signals to emulate unix signals from any platform;
19035 redirectstream; extendcircuit; mapaddress; getinfo; postdescriptor;
19036 closestream; closecircuit; etc.
19037 - Make nt services work and start on startup on win32 (based on
19038 patch by Matt Edman).
19039 - Add a new AddressMap config directive to rewrite incoming socks
19040 addresses. This lets you, for example, declare an implicit
19041 required exit node for certain sites.
19042 - Add a new TrackHostExits config directive to trigger addressmaps
19043 for certain incoming socks addresses -- for sites that break when
19044 your exit keeps changing (based on patch by Mike Perry).
19045 - Redo the client-side dns cache so it's just an addressmap too.
19046 - Notice when our IP changes, and reset stats/uptime/reachability.
19047 - When an application is using socks5, give him the whole variety of
19048 potential socks5 responses (connect refused, host unreachable, etc),
19049 rather than just "success" or "failure".
19050 - A more sane version numbering system. See
19051 http://tor.eff.org/cvs/tor/doc/version-spec.txt for details.
19052 - New contributed script "exitlist": a simple python script to
19053 parse directories and find Tor nodes that exit to listed
19055 - New contributed script "privoxy-tor-toggle" to toggle whether
19056 Privoxy uses Tor. Seems to be configured for Debian by default.
19057 - Report HTTP reasons to client when getting a response from directory
19058 servers -- so you can actually know what went wrong.
19059 - New config option MaxAdvertisedBandwidth which lets you advertise
19060 a low bandwidthrate (to not attract as many circuits) while still
19061 allowing a higher bandwidthrate in reality.
19063 o Robustness/stability fixes:
19064 - Make Tor use Niels Provos's libevent instead of its current
19065 poll-but-sometimes-select mess. This will let us use faster async
19066 cores (like epoll, kpoll, and /dev/poll), and hopefully work better
19068 - pthread support now too. This was forced because when we forked,
19069 we ended up wasting a lot of duplicate ram over time. Also switch
19070 to foo_r versions of some library calls to allow reentry and
19072 - Better handling for heterogeneous / unreliable nodes:
19073 - Annotate circuits w/ whether they aim to contain high uptime nodes
19074 and/or high capacity nodes. When building circuits, choose
19076 - This means that every single node in an intro rend circuit,
19077 not just the last one, will have a minimum uptime.
19078 - New config option LongLivedPorts to indicate application streams
19079 that will want high uptime circuits.
19080 - Servers reset uptime when a dir fetch entirely fails. This
19081 hopefully reflects stability of the server's network connectivity.
19082 - If somebody starts his tor server in Jan 2004 and then fixes his
19083 clock, don't make his published uptime be a year.
19084 - Reset published uptime when you wake up from hibernation.
19085 - Introduce a notion of 'internal' circs, which are chosen without
19086 regard to the exit policy of the last hop. Intro and rendezvous
19087 circs must be internal circs, to avoid leaking information. Resolve
19088 and connect streams can use internal circs if they want.
19089 - New circuit pooling algorithm: make sure to have enough circs around
19090 to satisfy any predicted ports, and also make sure to have 2 internal
19091 circs around if we've required internal circs lately (and with high
19092 uptime if we've seen that lately too).
19093 - Split NewCircuitPeriod option into NewCircuitPeriod (30 secs),
19094 which describes how often we retry making new circuits if current
19095 ones are dirty, and MaxCircuitDirtiness (10 mins), which describes
19096 how long we're willing to make use of an already-dirty circuit.
19097 - Cannibalize GENERAL circs to be C_REND, C_INTRO, S_INTRO, and S_REND
19098 circ as necessary, if there are any completed ones lying around
19099 when we try to launch one.
19100 - Make hidden services try to establish a rendezvous for 30 seconds,
19101 rather than for n (where n=3) attempts to build a circuit.
19102 - Change SHUTDOWN_WAIT_LENGTH from a fixed 30 secs to a config option
19103 "ShutdownWaitLength".
19104 - Try to be more zealous about calling connection_edge_end when
19105 things go bad with edge conns in connection.c.
19106 - Revise tor-spec to add more/better stream end reasons.
19107 - Revise all calls to connection_edge_end to avoid sending "misc",
19108 and to take errno into account where possible.
19111 - Fix a race condition that can trigger an assert, when we have a
19112 pending create cell and an OR connection fails right then.
19113 - Fix several double-mark-for-close bugs, e.g. where we were finding
19114 a conn for a cell even if that conn is already marked for close.
19115 - Make sequence of log messages when starting on win32 with no config
19116 file more reasonable.
19117 - When choosing an exit node for a new non-internal circ, don't take
19118 into account whether it'll be useful for any pending x.onion
19119 addresses -- it won't.
19120 - Turn addr_policy_compare from a tristate to a quadstate; this should
19121 help address our "Ah, you allow 1.2.3.4:80. You are a good choice
19122 for google.com" problem.
19123 - Make "platform" string in descriptor more accurate for Win32 servers,
19124 so it's not just "unknown platform".
19125 - Fix an edge case in parsing config options (thanks weasel).
19126 If they say "--" on the commandline, it's not an option.
19127 - Reject odd-looking addresses at the client (e.g. addresses that
19128 contain a colon), rather than having the server drop them because
19130 - tor-resolve requests were ignoring .exit if there was a working circuit
19131 they could use instead.
19132 - REUSEADDR on normal platforms means you can rebind to the port
19133 right after somebody else has let it go. But REUSEADDR on win32
19134 means to let you bind to the port _even when somebody else
19135 already has it bound_! So, don't do that on Win32.
19136 - Change version parsing logic: a version is "obsolete" if it is not
19137 recommended and (1) there is a newer recommended version in the
19138 same series, or (2) there are no recommended versions in the same
19139 series, but there are some recommended versions in a newer series.
19140 A version is "new" if it is newer than any recommended version in
19142 - Stop most cases of hanging up on a socks connection without sending
19146 - Require BandwidthRate to be at least 20kB/s for servers.
19147 - When a dirserver causes you to give a warn, mention which dirserver
19149 - New config option DirAllowPrivateAddresses for authdirservers.
19150 Now by default they refuse router descriptors that have non-IP or
19151 private-IP addresses.
19152 - Stop publishing socksport in the directory, since it's not
19153 actually meant to be public. For compatibility, publish a 0 there
19155 - Change DirFetchPeriod/StatusFetchPeriod to have a special "Be
19156 smart" value, that is low for servers and high for clients.
19157 - If our clock jumps forward by 100 seconds or more, assume something
19158 has gone wrong with our network and abandon all not-yet-used circs.
19159 - Warn when exit policy implicitly allows local addresses.
19160 - If we get an incredibly skewed timestamp from a dirserver mirror
19161 that isn't a verified OR, don't warn -- it's probably him that's
19163 - Since we ship our own Privoxy on OS X, tweak it so it doesn't write
19164 cookies to disk and doesn't log each web request to disk. (Thanks
19165 to Brett Carrington for pointing this out.)
19166 - When a client asks us for a dir mirror and we don't have one,
19167 launch an attempt to get a fresh one.
19168 - If we're hibernating and we get a SIGINT, exit immediately.
19169 - Add --with-dmalloc ./configure option, to track memory leaks.
19170 - And try to free all memory on closing, so we can detect what
19172 - Cache local dns resolves correctly even when they're .exit
19174 - Give a better warning when some other server advertises an
19175 ORPort that is actually an apache running ssl.
19176 - Add "opt hibernating 1" to server descriptor to make it clearer
19177 whether the server is hibernating.
19180 Changes in version 0.0.9.6 - 2005-03-24
19181 o Bugfixes on 0.0.9.x (crashes and asserts):
19182 - Add new end stream reasons to maintainance branch. Fix bug where
19183 reason (8) could trigger an assert. Prevent bug from recurring.
19184 - Apparently win32 stat wants paths to not end with a slash.
19185 - Fix assert triggers in assert_cpath_layer_ok(), where we were
19186 blowing away the circuit that conn->cpath_layer points to, then
19187 checking to see if the circ is well-formed. Backport check to make
19188 sure we dont use the cpath on a closed connection.
19189 - Prevent circuit_resume_edge_reading_helper() from trying to package
19190 inbufs for marked-for-close streams.
19191 - Don't crash on hup if your options->address has become unresolvable.
19192 - Some systems (like OS X) sometimes accept() a connection and tell
19193 you the remote host is 0.0.0.0:0. If this happens, due to some
19194 other mis-features, we get confused; so refuse the conn for now.
19196 o Bugfixes on 0.0.9.x (other):
19197 - Fix harmless but scary "Unrecognized content encoding" warn message.
19198 - Add new stream error reason: TORPROTOCOL reason means "you are not
19199 speaking a version of Tor I understand; say bye-bye to your stream."
19200 - Be willing to cache directories from up to ROUTER_MAX_AGE seconds
19201 into the future, now that we are more tolerant of skew. This
19202 resolves a bug where a Tor server would refuse to cache a directory
19203 because all the directories it gets are too far in the future;
19204 yet the Tor server never logs any complaints about clock skew.
19205 - Mac packaging magic: make man pages useable, and do not overwrite
19206 existing torrc files.
19207 - Make OS X log happily to /var/log/tor/tor.log
19210 Changes in version 0.0.9.5 - 2005-02-22
19211 o Bugfixes on 0.0.9.x:
19212 - Fix an assert race at exit nodes when resolve requests fail.
19213 - Stop picking unverified dir mirrors--it only leads to misery.
19214 - Patch from Matt Edman to make NT services work better. Service
19215 support is still not compiled into the executable by default.
19216 - Patch from Dmitri Bely so the Tor service runs better under
19217 the win32 SYSTEM account.
19218 - Make tor-resolve actually work (?) on Win32.
19219 - Fix a sign bug when getrlimit claims to have 4+ billion
19220 file descriptors available.
19221 - Stop refusing to start when bandwidthburst == bandwidthrate.
19222 - When create cells have been on the onion queue more than five
19223 seconds, just send back a destroy and take them off the list.
19226 Changes in version 0.0.9.4 - 2005-02-03
19227 o Bugfixes on 0.0.9:
19228 - Fix an assert bug that took down most of our servers: when
19229 a server claims to have 1 GB of bandwidthburst, don't
19231 - Don't crash as badly if we have spawned the max allowed number
19232 of dnsworkers, or we're out of file descriptors.
19233 - Block more file-sharing ports in the default exit policy.
19234 - MaxConn is now automatically set to the hard limit of max
19235 file descriptors we're allowed (ulimit -n), minus a few for
19237 - Give a clearer message when servers need to raise their
19238 ulimit -n when they start running out of file descriptors.
19239 - SGI Compatibility patches from Jan Schaumann.
19240 - Tolerate a corrupt cached directory better.
19241 - When a dirserver hasn't approved your server, list which one.
19242 - Go into soft hibernation after 95% of the bandwidth is used,
19243 not 99%. This is especially important for daily hibernators who
19244 have a small accounting max. Hopefully it will result in fewer
19245 cut connections when the hard hibernation starts.
19246 - Load-balance better when using servers that claim more than
19247 800kB/s of capacity.
19248 - Make NT services work (experimental, only used if compiled in).
19251 Changes in version 0.0.9.3 - 2005-01-21
19252 o Bugfixes on 0.0.9:
19253 - Backport the cpu use fixes from main branch, so busy servers won't
19254 need as much processor time.
19255 - Work better when we go offline and then come back, or when we
19256 run Tor at boot before the network is up. We do this by
19257 optimistically trying to fetch a new directory whenever an
19258 application request comes in and we think we're offline -- the
19259 human is hopefully a good measure of when the network is back.
19260 - Backport some minimal hidserv bugfixes: keep rend circuits open as
19261 long as you keep using them; actually publish hidserv descriptors
19262 shortly after they change, rather than waiting 20-40 minutes.
19263 - Enable Mac startup script by default.
19264 - Fix duplicate dns_cancel_pending_resolve reported by Giorgos Pallas.
19265 - When you update AllowUnverifiedNodes or FirewallPorts via the
19266 controller's setconf feature, we were always appending, never
19268 - When you update HiddenServiceDir via setconf, it was screwing up
19269 the order of reading the lines, making it fail.
19270 - Do not rewrite a cached directory back to the cache; otherwise we
19271 will think it is recent and not fetch a newer one on startup.
19272 - Workaround for webservers that lie about Content-Encoding: Tor
19273 now tries to autodetect compressed directories and compression
19274 itself. This lets us Proxypass dir fetches through apache.
19277 Changes in version 0.0.9.2 - 2005-01-04
19278 o Bugfixes on 0.0.9 (crashes and asserts):
19279 - Fix an assert on startup when the disk is full and you're logging
19281 - If you do socks4 with an IP of 0.0.0.x but *don't* provide a socks4a
19282 style address, then we'd crash.
19283 - Fix an assert trigger when the running-routers string we get from
19284 a dirserver is broken.
19285 - Make worker threads start and run on win32. Now win32 servers
19287 - Bandaid (not actually fix, but now it doesn't crash) an assert
19288 where the dns worker dies mysteriously and the main Tor process
19289 doesn't remember anything about the address it was resolving.
19291 o Bugfixes on 0.0.9 (Win32):
19292 - Workaround for brain-damaged __FILE__ handling on MSVC: keep Nick's
19293 name out of the warning/assert messages.
19294 - Fix a superficial "unhandled error on read" bug on win32.
19295 - The win32 installer no longer requires a click-through for our
19296 license, since our Free Software license grants rights but does not
19298 - Win32: When connecting to a dirserver fails, try another one
19299 immediately. (This was already working for non-win32 Tors.)
19300 - Stop trying to parse $HOME on win32 when hunting for default
19302 - Make tor-resolve.c work on win32 by calling network_init().
19304 o Bugfixes on 0.0.9 (other):
19305 - Make 0.0.9.x build on Solaris again.
19306 - Due to a fencepost error, we were blowing away the \n when reporting
19307 confvalue items in the controller. So asking for multiple config
19308 values at once couldn't work.
19309 - When listing circuits that are pending on an opening OR connection,
19310 if we're an OR we were listing circuits that *end* at us as
19311 being pending on every listener, dns/cpu worker, etc. Stop that.
19312 - Dirservers were failing to create 'running-routers' or 'directory'
19313 strings if we had more than some threshold of routers. Fix them so
19314 they can handle any number of routers.
19315 - Fix a superficial "Duplicate mark for close" bug.
19316 - Stop checking for clock skew for OR connections, even for servers.
19317 - Fix a fencepost error that was chopping off the last letter of any
19318 nickname that is the maximum allowed nickname length.
19319 - Update URLs in log messages so they point to the new website.
19320 - Fix a potential problem in mangling server private keys while
19321 writing to disk (not triggered yet, as far as we know).
19322 - Include the licenses for other free software we include in Tor,
19323 now that we're shipping binary distributions more regularly.
19326 Changes in version 0.0.9.1 - 2004-12-15
19327 o Bugfixes on 0.0.9:
19328 - Make hibernation actually work.
19329 - Make HashedControlPassword config option work.
19330 - When we're reporting event circuit status to a controller,
19331 don't use the stream status code.
19334 Changes in version 0.0.9 - 2004-12-12
19336 - Clean up manpage and torrc.sample file.
19337 - Clean up severities and text of log warnings.
19339 - Make servers trigger an assert when they enter hibernation.
19342 Changes in version 0.0.9rc7 - 2004-12-08
19343 o Bugfixes on 0.0.9rc:
19344 - Fix a stack-trashing crash when an exit node begins hibernating.
19345 - Avoid looking at unallocated memory while considering which
19346 ports we need to build circuits to cover.
19347 - Stop a sigpipe: when an 'end' cell races with eof from the app,
19348 we shouldn't hold-open-until-flush if the eof arrived first.
19349 - Fix a bug with init_cookie_authentication() in the controller.
19350 - When recommending new-format log lines, if the upper bound is
19351 LOG_ERR, leave it implicit.
19353 o Bugfixes on 0.0.8.1:
19354 - Fix a whole slew of memory leaks.
19355 - Fix isspace() and friends so they still make Solaris happy
19356 but also so they don't trigger asserts on win32.
19357 - Fix parse_iso_time on platforms without strptime (eg win32).
19358 - win32: tolerate extra "readable" events better.
19359 - win32: when being multithreaded, leave parent fdarray open.
19360 - Make unit tests work on win32.
19363 Changes in version 0.0.9rc6 - 2004-12-06
19364 o Bugfixes on 0.0.9pre:
19365 - Clean up some more integer underflow opportunities (not exploitable
19367 - While hibernating, hup should not regrow our listeners.
19368 - Send an end to the streams we close when we hibernate, rather
19369 than just chopping them off.
19370 - React to eof immediately on non-open edge connections.
19372 o Bugfixes on 0.0.8.1:
19373 - Calculate timeout for waiting for a connected cell from the time
19374 we sent the begin cell, not from the time the stream started. If
19375 it took a long time to establish the circuit, we would time out
19376 right after sending the begin cell.
19377 - Fix router_compare_addr_to_addr_policy: it was not treating a port
19378 of * as always matching, so we were picking reject *:* nodes as
19379 exit nodes too. Oops.
19382 - New circuit building strategy: keep a list of ports that we've
19383 used in the past 6 hours, and always try to have 2 circuits open
19384 or on the way that will handle each such port. Seed us with port
19385 80 so web users won't complain that Tor is "slow to start up".
19386 - Make kill -USR1 dump more useful stats about circuits.
19387 - When warning about retrying or giving up, print the address, so
19388 the user knows which one it's talking about.
19389 - If you haven't used a clean circuit in an hour, throw it away,
19390 just to be on the safe side. (This means after 6 hours a totally
19391 unused Tor client will have no circuits open.)
19394 Changes in version 0.0.9rc5 - 2004-12-01
19395 o Bugfixes on 0.0.8.1:
19396 - Disallow NDEBUG. We don't ever want anybody to turn off debug.
19397 - Let resolve conns retry/expire also, rather than sticking around
19399 - If we are using select, make sure we stay within FD_SETSIZE.
19401 o Bugfixes on 0.0.9pre:
19402 - Fix integer underflow in tor_vsnprintf() that may be exploitable,
19403 but doesn't seem to be currently; thanks to Ilja van Sprundel for
19405 - If anybody set DirFetchPostPeriod, give them StatusFetchPeriod
19406 instead. Impose minima and maxima for all *Period options; impose
19407 even tighter maxima for fetching if we are a caching dirserver.
19408 Clip rather than rejecting.
19409 - Fetch cached running-routers from servers that serve it (that is,
19410 authdirservers and servers running 0.0.9rc5-cvs or later.)
19413 - Accept *:706 (silc) in default exit policy.
19414 - Implement new versioning format for post 0.1.
19415 - Support "foo.nickname.exit" addresses, to let Alice request the
19416 address "foo" as viewed by exit node "nickname". Based on a patch
19418 - Make tor --version --version dump the cvs Id of every file.
19421 Changes in version 0.0.9rc4 - 2004-11-28
19422 o Bugfixes on 0.0.8.1:
19423 - Make windows sockets actually non-blocking (oops), and handle
19424 win32 socket errors better.
19426 o Bugfixes on 0.0.9rc1:
19427 - Actually catch the -USR2 signal.
19430 Changes in version 0.0.9rc3 - 2004-11-25
19431 o Bugfixes on 0.0.8.1:
19432 - Flush the log file descriptor after we print "Tor opening log file",
19433 so we don't see those messages days later.
19435 o Bugfixes on 0.0.9rc1:
19436 - Make tor-resolve work again.
19437 - Avoid infinite loop in tor-resolve if tor hangs up on it.
19438 - Fix an assert trigger for clients/servers handling resolves.
19441 Changes in version 0.0.9rc2 - 2004-11-24
19442 o Bugfixes on 0.0.9rc1:
19443 - I broke socks5 support while fixing the eof bug.
19444 - Allow unitless bandwidths and intervals; they default to bytes
19446 - New servers don't start out hibernating; they are active until
19447 they run out of bytes, so they have a better estimate of how
19448 long it takes, and so their operators can know they're working.
19451 Changes in version 0.0.9rc1 - 2004-11-23
19452 o Bugfixes on 0.0.8.1:
19453 - Finally fix a bug that's been plaguing us for a year:
19454 With high load, circuit package window was reaching 0. Whenever
19455 we got a circuit-level sendme, we were reading a lot on each
19456 socket, but only writing out a bit. So we would eventually reach
19457 eof. This would be noticed and acted on even when there were still
19458 bytes sitting in the inbuf.
19459 - When poll() is interrupted, we shouldn't believe the revents values.
19461 o Bugfixes on 0.0.9pre6:
19462 - Fix hibernate bug that caused pre6 to be broken.
19463 - Don't keep rephist info for routers that haven't had activity for
19464 24 hours. (This matters now that clients have keys, since we track
19466 - Never call close_temp_logs while validating log options.
19467 - Fix backslash-escaping on tor.sh.in and torctl.in.
19470 - Implement weekly/monthly/daily accounting: now you specify your
19471 hibernation properties by
19472 AccountingMax N bytes|KB|MB|GB|TB
19473 AccountingStart day|week|month [day] HH:MM
19474 Defaults to "month 1 0:00".
19475 - Let bandwidth and interval config options be specified as 5 bytes,
19476 kb, kilobytes, etc; and as seconds, minutes, hours, days, weeks.
19477 - kill -USR2 now moves all logs to loglevel debug (kill -HUP to
19478 get back to normal.)
19479 - If your requested entry or exit node has advertised bandwidth 0,
19481 - Be more greedy about filling up relay cells -- we try reading again
19482 once we've processed the stuff we read, in case enough has arrived
19483 to fill the last cell completely.
19484 - Apply NT service patch from Osamu Fujino. Still needs more work.
19487 Changes in version 0.0.9pre6 - 2004-11-15
19488 o Bugfixes on 0.0.8.1:
19489 - Fix assert failure on malformed socks4a requests.
19490 - Use identity comparison, not nickname comparison, to choose which
19491 half of circuit-ID-space each side gets to use. This is needed
19492 because sometimes we think of a router as a nickname, and sometimes
19493 as a hex ID, and we can't predict what the other side will do.
19494 - Catch and ignore SIGXFSZ signals when log files exceed 2GB; our
19495 write() call will fail and we handle it there.
19496 - Add a FAST_SMARTLIST define to optionally inline smartlist_get
19497 and smartlist_len, which are two major profiling offenders.
19499 o Bugfixes on 0.0.9pre5:
19500 - Fix a bug in read_all that was corrupting config files on windows.
19501 - When we're raising the max number of open file descriptors to
19502 'unlimited', don't log that we just raised it to '-1'.
19503 - Include event code with events, as required by control-spec.txt.
19504 - Don't give a fingerprint when clients do --list-fingerprint:
19505 it's misleading, because it will never be the same again.
19506 - Stop using strlcpy in tor_strndup, since it was slowing us
19508 - Remove warn on startup about missing cached-directory file.
19509 - Make kill -USR1 work again.
19510 - Hibernate if we start tor during the "wait for wakeup-time" phase
19511 of an accounting interval. Log our hibernation plans better.
19512 - Authoritative dirservers now also cache their directory, so they
19513 have it on start-up.
19516 - Fetch running-routers; cache running-routers; compress
19517 running-routers; serve compressed running-routers.z
19518 - Add NSI installer script contributed by J Doe.
19519 - Commit VC6 and VC7 workspace/project files.
19520 - Commit a tor.spec for making RPM files, with help from jbash.
19521 - Add contrib/torctl.in contributed by Glenn Fink.
19522 - Implement the control-spec's SAVECONF command, to write your
19523 configuration to torrc.
19524 - Get cookie authentication for the controller closer to working.
19525 - Include control-spec.txt in the tarball.
19526 - When set_conf changes our server descriptor, upload a new copy.
19527 But don't upload it too often if there are frequent changes.
19528 - Document authentication config in man page, and document signals
19530 - Clean up confusing parts of man page and torrc.sample.
19531 - Make expand_filename handle ~ and ~username.
19532 - Use autoconf to enable largefile support where necessary. Use
19533 ftello where available, since ftell can fail at 2GB.
19534 - Distinguish between TOR_TLS_CLOSE and TOR_TLS_ERROR, so we can
19535 log more informatively.
19536 - Give a slightly more useful output for "tor -h".
19537 - Refuse application socks connections to port 0.
19538 - Check clock skew for verified servers, but allow unverified
19539 servers and clients to have any clock skew.
19540 - Break DirFetchPostPeriod into:
19541 - DirFetchPeriod for fetching full directory,
19542 - StatusFetchPeriod for fetching running-routers,
19543 - DirPostPeriod for posting server descriptor,
19544 - RendPostPeriod for posting hidden service descriptors.
19545 - Make sure the hidden service descriptors are at a random offset
19546 from each other, to hinder linkability.
19549 Changes in version 0.0.9pre5 - 2004-11-09
19550 o Bugfixes on 0.0.9pre4:
19551 - Fix a seg fault in unit tests (doesn't affect main program).
19552 - Fix an assert bug where a hidden service provider would fail if
19553 the first hop of his rendezvous circuit was down.
19554 - Hidden service operators now correctly handle version 1 style
19555 INTRODUCE1 cells (nobody generates them still, so not a critical
19557 - If do_hup fails, actually notice.
19558 - Handle more errnos from accept() without closing the listener.
19559 Some OpenBSD machines were closing their listeners because
19560 they ran out of file descriptors.
19561 - Send resolve cells to exit routers that are running a new
19562 enough version of the resolve code to work right.
19563 - Better handling of winsock includes on non-MSV win32 compilers.
19564 - Some people had wrapped their tor client/server in a script
19565 that would restart it whenever it died. This did not play well
19566 with our "shut down if your version is obsolete" code. Now people
19567 don't fetch a new directory if their local cached version is
19569 - Make our autogen.sh work on ksh as well as bash.
19572 - Hibernation: New config option "AccountingMaxKB" lets you
19573 set how many KBytes per month you want to allow your server to
19574 consume. Rather than spreading those bytes out evenly over the
19575 month, we instead hibernate for some of the month and pop up
19576 at a deterministic time, work until the bytes are consumed, then
19577 hibernate again. Config option "MonthlyAccountingStart" lets you
19578 specify which day of the month your billing cycle starts on.
19579 - Control interface: a separate program can now talk to your
19580 client/server over a socket, and get/set config options, receive
19581 notifications of circuits and streams starting/finishing/dying,
19582 bandwidth used, etc. The next step is to get some GUIs working.
19583 Let us know if you want to help out. See doc/control-spec.txt .
19584 - Ship a contrib/tor-control.py as an example script to interact
19585 with the control port.
19586 - "tor --hash-password zzyxz" will output a salted password for
19587 use in authenticating to the control interface.
19588 - New log format in config:
19589 "Log minsev[-maxsev] stdout|stderr|syslog" or
19590 "Log minsev[-maxsev] file /var/foo"
19593 - DirPolicy config option, to let people reject incoming addresses
19594 from their dirserver.
19595 - "tor --list-fingerprint" will list your identity key fingerprint
19597 - Add "pass" target for RedirectExit, to make it easier to break
19598 out of a sequence of RedirectExit rules.
19599 - Clients now generate a TLS cert too, in preparation for having
19600 them act more like real nodes.
19601 - Ship src/win32/ in the tarball, so people can use it to build.
19602 - Make old win32 fall back to CWD if SHGetSpecialFolderLocation
19604 - New "router-status" line in directory, to better bind each verified
19605 nickname to its identity key.
19606 - Deprecate unofficial config option abbreviations, and abbreviations
19607 not on the command line.
19608 - Add a pure-C tor-resolve implementation.
19609 - Use getrlimit and friends to ensure we can reach MaxConn (currently
19610 1024) file descriptors.
19612 o Code security improvements, inspired by Ilja:
19613 - Replace sprintf with snprintf. (I think they were all safe, but
19615 - Replace strcpy/strncpy with strlcpy in more places.
19616 - Avoid strcat; use snprintf or strlcat instead.
19617 - snprintf wrapper with consistent (though not C99) overflow behavior.
19620 Changes in version 0.0.9pre4 - 2004-10-17
19621 o Bugfixes on 0.0.9pre3:
19622 - If the server doesn't specify an exit policy, use the real default
19623 exit policy, not reject *:*.
19624 - Ignore fascistfirewall when uploading/downloading hidden service
19625 descriptors, since we go through Tor for those; and when using
19626 an HttpProxy, since we assume it can reach them all.
19627 - When looking for an authoritative dirserver, use only the ones
19628 configured at boot. Don't bother looking in the directory.
19629 - The rest of the fix for get_default_conf_file() on older win32.
19630 - Make 'Routerfile' config option obsolete.
19633 - New 'MyFamily nick1,...' config option for a server to
19634 specify other servers that shouldn't be used in the same circuit
19635 with it. Only believed if nick1 also specifies us.
19636 - New 'NodeFamily nick1,nick2,...' config option for a client to
19637 specify nodes that it doesn't want to use in the same circuit.
19638 - New 'Redirectexit pattern address:port' config option for a
19639 server to redirect exit connections, e.g. to a local squid.
19642 Changes in version 0.0.9pre3 - 2004-10-13
19643 o Bugfixes on 0.0.8.1:
19644 - Better torrc example lines for dirbindaddress and orbindaddress.
19645 - Improved bounds checking on parsed ints (e.g. config options and
19646 the ones we find in directories.)
19647 - Better handling of size_t vs int, so we're more robust on 64
19649 - Fix the rest of the bug where a newly started OR would appear
19650 as unverified even after we've added his fingerprint and hupped
19652 - Fix a bug from 0.0.7: when read() failed on a stream, we would
19653 close it without sending back an end. So 'connection refused'
19654 would simply be ignored and the user would get no response.
19656 o Bugfixes on 0.0.9pre2:
19657 - Serving the cached-on-disk directory to people is bad. We now
19658 provide no directory until we've fetched a fresh one.
19659 - Workaround for bug on windows where cached-directories get crlf
19661 - Make get_default_conf_file() work on older windows too.
19662 - If we write a *:* exit policy line in the descriptor, don't write
19663 any more exit policy lines.
19666 - Use only 0.0.9pre1 and later servers for resolve cells.
19667 - Make the dirservers file obsolete.
19668 - Include a dir-signing-key token in directories to tell the
19669 parsing entity which key is being used to sign.
19670 - Remove the built-in bulky default dirservers string.
19671 - New config option "Dirserver %s:%d [fingerprint]", which can be
19672 repeated as many times as needed. If no dirservers specified,
19673 default to moria1,moria2,tor26.
19674 - Make moria2 advertise a dirport of 80, so people behind firewalls
19675 will be able to get a directory.
19676 - Http proxy support
19677 - Dirservers translate requests for http://%s:%d/x to /x
19678 - You can specify "HttpProxy %s[:%d]" and all dir fetches will
19679 be routed through this host.
19680 - Clients ask for /tor/x rather than /x for new enough dirservers.
19681 This way we can one day coexist peacefully with apache.
19682 - Clients specify a "Host: %s%d" http header, to be compatible
19683 with more proxies, and so running squid on an exit node can work.
19686 Changes in version 0.0.8.1 - 2004-10-13
19688 - Fix a seg fault that can be triggered remotely for Tor
19689 clients/servers with an open dirport.
19690 - Fix a rare assert trigger, where routerinfos for entries in
19691 our cpath would expire while we're building the path.
19692 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19693 - Fix a rare seg fault for people running hidden services on
19694 intermittent connections.
19695 - Fix a bug in parsing opt keywords with objects.
19696 - Fix a stale pointer assert bug when a stream detaches and
19698 - Fix a string format vulnerability (probably not exploitable)
19699 in reporting stats locally.
19700 - Fix an assert trigger: sometimes launching circuits can fail
19701 immediately, e.g. because too many circuits have failed recently.
19702 - Fix a compile warning on 64 bit platforms.
19705 Changes in version 0.0.9pre2 - 2004-10-03
19707 - Make fetching a cached directory work for 64-bit platforms too.
19708 - Make zlib.h a required header, not an optional header.
19711 Changes in version 0.0.9pre1 - 2004-10-01
19713 - Stop using separate defaults for no-config-file and
19714 empty-config-file. Now you have to explicitly turn off SocksPort,
19715 if you don't want it open.
19716 - Fix a bug in OutboundBindAddress so it (hopefully) works.
19717 - Improve man page to mention more of the 0.0.8 features.
19718 - Fix a rare seg fault for people running hidden services on
19719 intermittent connections.
19720 - Change our file IO stuff (especially wrt OpenSSL) so win32 is
19722 - Fix more dns related bugs: send back resolve_failed and end cells
19723 more reliably when the resolve fails, rather than closing the
19724 circuit and then trying to send the cell. Also attach dummy resolve
19725 connections to a circuit *before* calling dns_resolve(), to fix
19726 a bug where cached answers would never be sent in RESOLVED cells.
19727 - When we run out of disk space, or other log writing error, don't
19728 crash. Just stop logging to that log and continue.
19729 - We were starting to daemonize before we opened our logs, so if
19730 there were any problems opening logs, we would complain to stderr,
19731 which wouldn't work, and then mysteriously exit.
19732 - Fix a rare bug where sometimes a verified OR would connect to us
19733 before he'd uploaded his descriptor, which would cause us to
19734 assign conn->nickname as though he's unverified. Now we look through
19735 the fingerprint list to see if he's there.
19736 - Fix a rare assert trigger, where routerinfos for entries in
19737 our cpath would expire while we're building the path.
19740 - Clients can ask dirservers for /dir.z to get a compressed version
19741 of the directory. Only works for servers running 0.0.9, of course.
19742 - Make clients cache directories and use them to seed their router
19743 lists at startup. This means clients have a datadir again.
19744 - Configuration infrastructure support for warning on obsolete
19746 - Respond to content-encoding headers by trying to uncompress as
19748 - Reply with a deflated directory when a client asks for "dir.z".
19749 We could use allow-encodings instead, but allow-encodings isn't
19750 specified in HTTP 1.0.
19751 - Raise the max dns workers from 50 to 100.
19752 - Discourage people from setting their dirfetchpostperiod more often
19753 than once per minute.
19754 - Protect dirservers from overzealous descriptor uploading -- wait
19755 10 seconds after directory gets dirty, before regenerating.
19758 Changes in version 0.0.8 - 2004-08-25
19759 o Port it to SunOS 5.9 / Athena
19762 Changes in version 0.0.8rc2 - 2004-08-20
19763 o Make it compile on cygwin again.
19764 o When picking unverified routers, skip those with low uptime and/or
19765 low bandwidth, depending on what properties you care about.
19768 Changes in version 0.0.8rc1 - 2004-08-18
19769 o Changes from 0.0.7.3:
19771 - Fix assert triggers: if the other side returns an address 0.0.0.0,
19772 don't put it into the client dns cache.
19773 - If a begin failed due to exit policy, but we believe the IP address
19774 should have been allowed, switch that router to exitpolicy reject *:*
19775 until we get our next directory.
19777 - Clients choose nodes proportional to advertised bandwidth.
19778 - Avoid using nodes with low uptime as introduction points.
19779 - Handle servers with dynamic IP addresses: don't replace
19780 options->Address with the resolved one at startup, and
19781 detect our address right before we make a routerinfo each time.
19782 - 'FascistFirewall' option to pick dirservers and ORs on specific
19783 ports; plus 'FirewallPorts' config option to tell FascistFirewall
19784 which ports are open. (Defaults to 80,443)
19785 - Be more aggressive about trying to make circuits when the network
19786 has changed (e.g. when you unsuspend your laptop).
19787 - Check for time skew on http headers; report date in response to
19789 - If the entrynode config line has only one node, don't pick it as
19791 - Add strict{entry|exit}nodes config options. If set to 1, then
19792 we refuse to build circuits that don't include the specified entry
19794 - OutboundBindAddress config option, to bind to a specific
19795 IP address for outgoing connect()s.
19796 - End truncated log entries (e.g. directories) with "[truncated]".
19798 o Patches to 0.0.8preX:
19800 - Patches to compile and run on win32 again (maybe)?
19801 - Fix crash when looking for ~/.torrc with no $HOME set.
19802 - Fix a race bug in the unit tests.
19803 - Handle verified/unverified name collisions better when new
19804 routerinfo's arrive in a directory.
19805 - Sometimes routers were getting entered into the stats before
19806 we'd assigned their identity_digest. Oops.
19807 - Only pick and establish intro points after we've gotten a
19810 - AllowUnverifiedNodes config option to let circuits choose no-name
19811 routers in entry,middle,exit,introduction,rendezvous positions.
19812 Allow middle and rendezvous positions by default.
19813 - Add a man page for tor-resolve.
19816 Changes in version 0.0.7.3 - 2004-08-12
19817 o Stop dnsworkers from triggering an assert failure when you
19818 ask them to resolve the host "".
19821 Changes in version 0.0.8pre3 - 2004-08-09
19822 o Changes from 0.0.7.2:
19823 - Allow multiple ORs with same nickname in routerlist -- now when
19824 people give us one identity key for a nickname, then later
19825 another, we don't constantly complain until the first expires.
19826 - Remember used bandwidth (both in and out), and publish 15-minute
19827 snapshots for the past day into our descriptor.
19828 - You can now fetch $DIRURL/running-routers to get just the
19829 running-routers line, not the whole descriptor list. (But
19830 clients don't use this yet.)
19831 - When people mistakenly use Tor as an http proxy, point them
19832 at the tor-doc.html rather than the INSTALL.
19833 - Remove our mostly unused -- and broken -- hex_encode()
19834 function. Use base16_encode() instead. (Thanks to Timo Lindfors
19835 for pointing out this bug.)
19836 - Rotate onion keys every 12 hours, not every 2 hours, so we have
19837 fewer problems with people using the wrong key.
19838 - Change the default exit policy to reject the default edonkey,
19839 kazaa, gnutella ports.
19840 - Add replace_file() to util.[ch] to handle win32's rename().
19842 o Changes from 0.0.8preX:
19843 - Fix two bugs in saving onion keys to disk when rotating, so
19844 hopefully we'll get fewer people using old onion keys.
19845 - Fix an assert error that was making SocksPolicy not work.
19846 - Be willing to expire routers that have an open dirport -- it's
19847 just the authoritative dirservers we want to not forget.
19848 - Reject tor-resolve requests for .onion addresses early, so we
19849 don't build a whole rendezvous circuit and then fail.
19850 - When you're warning a server that he's unverified, don't cry
19851 wolf unpredictably.
19852 - Fix a race condition: don't try to extend onto a connection
19853 that's still handshaking.
19854 - For servers in clique mode, require the conn to be open before
19855 you'll choose it for your path.
19856 - Fix some cosmetic bugs about duplicate mark-for-close, lack of
19857 end relay cell, etc.
19858 - Measure bandwidth capacity over the last 24 hours, not just 12
19859 - Bugfix: authoritative dirservers were making and signing a new
19860 directory for each client, rather than reusing the cached one.
19863 Changes in version 0.0.8pre2 - 2004-08-04
19864 o Changes from 0.0.7.2:
19866 - Check directory signature _before_ you decide whether you're
19867 you're running an obsolete version and should exit.
19868 - Check directory signature _before_ you parse the running-routers
19869 list to decide who's running or verified.
19870 - Bugfixes and features:
19871 - Check return value of fclose while writing to disk, so we don't
19872 end up with broken files when servers run out of disk space.
19873 - Log a warning if the user uses an unsafe socks variant, so people
19874 are more likely to learn about privoxy or socat.
19875 - Dirservers now include RFC1123-style dates in the HTTP headers,
19876 which one day we will use to better detect clock skew.
19878 o Changes from 0.0.8pre1:
19879 - Make it compile without warnings again on win32.
19880 - Log a warning if you're running an unverified server, to let you
19881 know you might want to get it verified.
19882 - Only pick a default nickname if you plan to be a server.
19885 Changes in version 0.0.8pre1 - 2004-07-23
19887 - Made our unit tests compile again on OpenBSD 3.5, and tor
19888 itself compile again on OpenBSD on a sparc64.
19889 - We were neglecting milliseconds when logging on win32, so
19890 everything appeared to happen at the beginning of each second.
19892 o Protocol changes:
19893 - 'Extend' relay cell payloads now include the digest of the
19894 intended next hop's identity key. Now we can verify that we're
19895 extending to the right router, and also extend to routers we
19896 hadn't heard of before.
19899 - Tor nodes can now act as relays (with an advertised ORPort)
19900 without being manually verified by the dirserver operators.
19901 - Uploaded descriptors of unverified routers are now accepted
19902 by the dirservers, and included in the directory.
19903 - Verified routers are listed by nickname in the running-routers
19904 list; unverified routers are listed as "$<fingerprint>".
19905 - We now use hash-of-identity-key in most places rather than
19906 nickname or addr:port, for improved security/flexibility.
19907 - To avoid Sybil attacks, paths still use only verified servers.
19908 But now we have a chance to play around with hybrid approaches.
19909 - Nodes track bandwidth usage to estimate capacity (not used yet).
19910 - ClientOnly option for nodes that never want to become servers.
19911 - Directory caching.
19912 - "AuthoritativeDir 1" option for the official dirservers.
19913 - Now other nodes (clients and servers) will cache the latest
19914 directory they've pulled down.
19915 - They can enable their DirPort to serve it to others.
19916 - Clients will pull down a directory from any node with an open
19917 DirPort, and check the signature/timestamp correctly.
19918 - Authoritative dirservers now fetch directories from other
19919 authdirservers, to stay better synced.
19920 - Running-routers list tells who's down also, along with noting
19921 if they're verified (listed by nickname) or unverified (listed
19923 - Allow dirservers to serve running-router list separately.
19924 This isn't used yet.
19925 - ORs connect-on-demand to other ORs
19926 - If you get an extend cell to an OR you're not connected to,
19927 connect, handshake, and forward the create cell.
19928 - The authoritative dirservers stay connected to everybody,
19929 and everybody stays connected to 0.0.7 servers, but otherwise
19930 clients/servers expire unused connections after 5 minutes.
19931 - When servers get a sigint, they delay 30 seconds (refusing new
19932 connections) then exit. A second sigint causes immediate exit.
19933 - File and name management:
19934 - Look for .torrc if no CONFDIR "torrc" is found.
19935 - If no datadir is defined, then choose, make, and secure ~/.tor
19937 - If torrc not found, exitpolicy reject *:*.
19938 - Expands ~/ in filenames to $HOME/ (but doesn't yet expand ~arma).
19939 - If no nickname is defined, derive default from hostname.
19940 - Rename secret key files, e.g. identity.key -> secret_id_key,
19941 to discourage people from mailing their identity key to tor-ops.
19942 - Refuse to build a circuit before the directory has arrived --
19943 it won't work anyway, since you won't know the right onion keys
19945 - Try other dirservers immediately if the one you try is down. This
19946 should tolerate down dirservers better now.
19947 - Parse tor version numbers so we can do an is-newer-than check
19948 rather than an is-in-the-list check.
19949 - New socks command 'resolve', to let us shim gethostbyname()
19951 - A 'tor_resolve' script to access the socks resolve functionality.
19952 - A new socks-extensions.txt doc file to describe our
19953 interpretation and extensions to the socks protocols.
19954 - Add a ContactInfo option, which gets published in descriptor.
19955 - Publish OR uptime in descriptor (and thus in directory) too.
19956 - Write tor version at the top of each log file
19957 - New docs in the tarball:
19959 - Document that you should proxy your SSL traffic too.
19962 Changes in version 0.0.7.2 - 2004-07-07
19963 o A better fix for the 0.0.0.0 problem, that will hopefully
19964 eliminate the remaining related assertion failures.
19967 Changes in version 0.0.7.1 - 2004-07-04
19968 o When an address resolves to 0.0.0.0, treat it as a failed resolve,
19969 since internally we use 0.0.0.0 to signify "not yet resolved".
19972 Changes in version 0.0.7 - 2004-06-07
19973 o Updated the man page to reflect the new features.
19976 Changes in version 0.0.7rc2 - 2004-06-06
19977 o Changes from 0.0.7rc1:
19978 - Make it build on Win32 again.
19979 o Changes from 0.0.6.2:
19980 - Rotate dnsworkers and cpuworkers on SIGHUP, so they get new config
19984 Changes in version 0.0.7rc1 - 2004-06-02
19986 - On sighup, we were adding another log without removing the first
19987 one. So log messages would get duplicated n times for n sighups.
19988 - Several cases of using a connection after we'd freed it. The
19989 problem was that connections that are pending resolve are in both
19990 the pending_resolve tree, and also the circuit's resolving_streams
19991 list. When you want to remove one, you must remove it from both.
19992 - Fix a double-mark-for-close where an end cell arrived for a
19993 resolving stream, and then the resolve failed.
19994 - Check directory signatures based on name of signer, not on whom
19995 we got the directory from. This will let us cache directories more
19998 - Crank up some of our constants to handle more users.
20001 Changes in version 0.0.7pre1 - 2004-06-02
20002 o Fixes for crashes and other obnoxious bugs:
20003 - Fix an epipe bug: sometimes when directory connections failed
20004 to connect, we would give them a chance to flush before closing
20006 - When we detached from a circuit because of resolvefailed, we
20007 would immediately try the same circuit twice more, and then
20008 give up on the resolve thinking we'd tried three different
20010 - Limit the number of intro circuits we'll attempt to build for a
20011 hidden service per 15-minute period.
20012 - Check recommended-software string *early*, before actually parsing
20013 the directory. Thus we can detect an obsolete version and exit,
20014 even if the new directory format doesn't parse.
20015 o Fixes for security bugs:
20016 - Remember which nodes are dirservers when you startup, and if a
20017 random OR enables his dirport, don't automatically assume he's
20018 a trusted dirserver.
20020 - Directory connections were asking the wrong poll socket to
20021 start writing, and not asking themselves to start writing.
20022 - When we detached from a circuit because we sent a begin but
20023 didn't get a connected, we would use it again the first time;
20024 but after that we would correctly switch to a different one.
20025 - Stop warning when the first onion decrypt attempt fails; they
20026 will sometimes legitimately fail now that we rotate keys.
20027 - Override unaligned-access-ok check when $host_cpu is ia64 or
20028 arm. Apparently they allow it but the kernel whines.
20029 - Dirservers try to reconnect periodically too, in case connections
20031 - Fix some memory leaks in directory servers.
20032 - Allow backslash in Win32 filenames.
20033 - Made Tor build complain-free on FreeBSD, hopefully without
20034 breaking other BSD builds. We'll see.
20036 - Doxygen markup on all functions and global variables.
20037 - Make directory functions update routerlist, not replace it. So
20038 now directory disagreements are not so critical a problem.
20039 - Remove the upper limit on number of descriptors in a dirserver's
20040 directory (not that we were anywhere close).
20041 - Allow multiple logfiles at different severity ranges.
20042 - Allow *BindAddress to specify ":port" rather than setting *Port
20043 separately. Allow multiple instances of each BindAddress config
20044 option, so you can bind to multiple interfaces if you want.
20045 - Allow multiple exit policy lines, which are processed in order.
20046 Now we don't need that huge line with all the commas in it.
20047 - Enable accept/reject policies on SOCKS connections, so you can bind
20048 to 0.0.0.0 but still control who can use your OP.
20051 Changes in version 0.0.6.2 - 2004-05-16
20052 o Our integrity-checking digest was checking only the most recent cell,
20053 not the previous cells like we'd thought.
20054 Thanks to Stefan Mark for finding the flaw!
20057 Changes in version 0.0.6.1 - 2004-05-06
20058 o Fix two bugs in our AES counter-mode implementation (this affected
20059 onion-level stream encryption, but not TLS-level). It turns
20060 out we were doing something much more akin to a 16-character
20061 polyalphabetic cipher. Oops.
20062 Thanks to Stefan Mark for finding the flaw!
20063 o Retire moria3 as a directory server, and add tor26 as a directory
20067 Changes in version 0.0.6 - 2004-05-02
20068 [version bump only]
20071 Changes in version 0.0.6rc4 - 2004-05-01
20072 o Update the built-in dirservers list to use the new directory format
20073 o Fix a rare seg fault: if a node offering a hidden service attempts
20074 to build a circuit to Alice's rendezvous point and fails before it
20075 reaches the last hop, it retries with a different circuit, but
20077 o Handle windows socket errors correctly.
20080 Changes in version 0.0.6rc3 - 2004-04-28
20081 o Don't expire non-general excess circuits (if we had enough
20082 circuits open, we were expiring rendezvous circuits -- even
20083 when they had a stream attached. oops.)
20084 o Fetch randomness from /dev/urandom better (not via fopen/fread)
20085 o Better debugging for tls errors
20086 o Some versions of openssl have an SSL_pending function that erroneously
20087 returns bytes when there is a non-application record pending.
20088 o Set Content-Type on the directory and hidserv descriptor.
20089 o Remove IVs from cipher code, since AES-ctr has none.
20090 o Win32 fixes. Tor now compiles on win32 with no warnings/errors.
20091 o We were using an array of length zero in a few places.
20092 o win32's gethostbyname can't resolve an IP to an IP.
20093 o win32's close can't close a socket.
20096 Changes in version 0.0.6rc2 - 2004-04-26
20097 o Fix a bug where we were closing tls connections intermittently.
20098 It turns out openssl keeps its errors around -- so if an error
20099 happens, and you don't ask about it, and then another openssl
20100 operation happens and succeeds, and you ask if there was an error,
20101 it tells you about the first error. Fun fun.
20102 o Fix a bug that's been lurking since 27 may 03 (!)
20103 When passing back a destroy cell, we would use the wrong circ id.
20104 'Mostly harmless', but still worth fixing.
20105 o Since we don't support truncateds much, don't bother sending them;
20106 just close the circ.
20107 o check for <machine/limits.h> so we build on NetBSD again (I hope).
20108 o don't crash if a conn that sent a begin has suddenly lost its circuit
20109 (this was quite rare).
20112 Changes in version 0.0.6rc1 - 2004-04-25
20113 o We now rotate link (tls context) keys and onion keys.
20114 o CREATE cells now include oaep padding, so you can tell
20115 if you decrypted them correctly.
20116 o Add bandwidthburst to server descriptor.
20117 o Directories now say which dirserver signed them.
20118 o Use a tor_assert macro that logs failed assertions too.
20121 Changes in version 0.0.6pre5 - 2004-04-18
20122 o changes from 0.0.6pre4:
20123 - make tor build on broken freebsd 5.2 installs
20124 - fix a failed assert when you try an intro point, get a nack, and try
20125 a second one and it works.
20126 - when alice uses a port that the hidden service doesn't accept,
20127 it now sends back an end cell (denied by exit policy). otherwise
20128 alice would just have to wait to time out.
20129 - fix another rare bug: when we had tried all the intro
20130 points for a hidden service, we fetched the descriptor
20131 again, but we left our introcirc thinking it had already
20132 sent an intro, so it kept waiting for a response...
20133 - bugfix: when you sleep your hidden-service laptop, as soon
20134 as it wakes up it tries to upload a service descriptor, but
20135 socketpair fails for some reason (localhost not up yet?).
20136 now we simply give up on that upload, and we'll try again later.
20137 i'd still like to find the bug though.
20138 - if an intro circ waiting for an ack dies before getting one, then
20140 - we were reusing stale service descriptors and refetching usable
20144 Changes in version 0.0.6pre4 - 2004-04-14
20145 o changes from 0.0.6pre3:
20146 - when bob fails to connect to the rendezvous point, and his
20147 circ didn't fail because of the rendezvous point itself, then
20148 he retries a couple of times
20149 - we expire introduction and rendezvous circs more thoroughly
20150 (sometimes they were hanging around forever)
20151 - we expire unattached rendezvous streams that have been around
20152 too long (they were sticking around forever).
20153 - fix a measly fencepost error that was crashing everybody with
20157 Changes in version 0.0.6pre3 - 2004-04-14
20158 o changes from 0.0.6pre2:
20159 - make hup work again
20160 - fix some memory leaks for dirservers
20161 - allow more skew in rendezvous descriptor timestamps, to help
20162 handle people like blanu who don't know what time it is
20163 - normal circs are 3 hops, but some rend/intro circs are 4, if
20164 the initiator doesn't get to choose the last hop
20165 - send acks for introductions, so alice can know whether to try
20167 - bob publishes intro points more correctly
20168 o changes from 0.0.5:
20169 - fix an assert trigger that's been plaguing us since the days
20170 of 0.0.2prexx (thanks weasel!)
20171 - retry stream correctly when we fail to connect because of
20172 exit-policy-reject (should try another) or can't-resolve-address
20173 (also should try another, because dns on random internet servers
20175 - when we hup a dirserver and we've *removed* a server from the
20176 approved-routers list, now we remove that server from the
20177 in-memory directories too
20180 Changes in version 0.0.6pre2 - 2004-04-08
20181 o We fixed our base32 implementation. Now it works on all architectures.
20184 Changes in version 0.0.6pre1 - 2004-04-08
20186 - Hidden services and rendezvous points are implemented. Go to
20187 http://6sxoyfb3h2nvok2d.onion/ for an index of currently available
20188 hidden services. (This only works via a socks4a proxy such as
20189 Privoxy, and currently it's quite slow.)
20192 Changes in version 0.0.5 - 2004-03-30
20193 [version bump only]
20196 Changes in version 0.0.5rc3 - 2004-03-29
20197 o Install torrc as torrc.sample -- we no longer clobber your
20199 o Re-enable recommendedversion checking (we broke it in rc2, oops)
20200 o Add in a 'notice' log level for things the operator should hear
20201 but that aren't warnings
20204 Changes in version 0.0.5rc2 - 2004-03-29
20205 o Hold socks connection open until reply is flushed (if possible)
20206 o Make exit nodes resolve IPs to IPs immediately, rather than asking
20207 the dns farm to do it.
20208 o Fix c99 aliasing warnings in rephist.c
20209 o Don't include server descriptors that are older than 24 hours in the
20211 o Give socks 'reject' replies their whole 15s to attempt to flush,
20212 rather than seeing the 60s timeout and assuming the flush had failed.
20213 o Clean automake droppings from the cvs repository
20216 Changes in version 0.0.5rc1 - 2004-03-28
20217 o Fix mangled-state bug in directory fetching (was causing sigpipes).
20218 o Only build circuits after we've fetched the directory: clients were
20219 using only the directory servers before they'd fetched a directory.
20220 This also means longer startup time; so it goes.
20221 o Fix an assert trigger where an OP would fail to handshake, and we'd
20222 expect it to have a nickname.
20223 o Work around a tsocks bug: do a socks reject when AP connection dies
20224 early, else tsocks goes into an infinite loop.
20227 Changes in version 0.0.4 - 2004-03-26
20228 o When connecting to a dirserver or OR and the network is down,
20232 Changes in version 0.0.3 - 2004-03-26
20233 o Warn and fail if server chose a nickname with illegal characters
20234 o Port to Solaris and Sparc:
20235 - include missing header fcntl.h
20236 - have autoconf find -lsocket -lnsl automatically
20237 - deal with hardware word alignment
20238 - make uname() work (solaris has a different return convention)
20239 - switch from using signal() to sigaction()
20240 o Preliminary work on reputation system:
20241 - Keep statistics on success/fail of connect attempts; they're published
20242 by kill -USR1 currently.
20243 - Add a RunTesting option to try to learn link state by creating test
20244 circuits, even when SocksPort is off.
20245 - Remove unused open circuits when there are too many.
20248 Changes in version 0.0.2 - 2004-03-19
20249 - Include strlcpy and strlcat for safer string ops
20250 - define INADDR_NONE so we compile (but still not run) on solaris
20253 Changes in version 0.0.2pre27 - 2004-03-14
20255 - Allow internal tor networks (we were rejecting internal IPs,
20256 now we allow them if they're set explicitly).
20257 - And fix a few endian issues.
20260 Changes in version 0.0.2pre26 - 2004-03-14
20262 - If a stream times out after 15s without a connected cell, don't
20263 try that circuit again: try a new one.
20264 - Retry streams at most 4 times. Then give up.
20265 - When a dirserver gets a descriptor from an unknown router, it
20266 logs its fingerprint (so the dirserver operator can choose to
20267 accept it even without mail from the server operator).
20268 - Inform unapproved servers when we reject their descriptors.
20269 - Make tor build on Windows again. It works as a client, who knows
20271 - Clearer instructions in the torrc for how to set up a server.
20272 - Be more efficient about reading fd's when our global token bucket
20273 (used for rate limiting) becomes empty.
20275 - Stop asserting that computers always go forward in time. It's
20277 - When we sent a cell (e.g. destroy) and then marked an OR connection
20278 expired, we might close it before finishing a flush if the other
20279 side isn't reading right then.
20280 - Don't allow dirservers to start if they haven't defined
20281 RecommendedVersions
20282 - We were caching transient dns failures. Oops.
20283 - Prevent servers from publishing an internal IP as their address.
20284 - Address a strcat vulnerability in circuit.c
20287 Changes in version 0.0.2pre25 - 2004-03-04
20289 - Put the OR's IP in its router descriptor, not its fqdn. That way
20290 we'll stop being stalled by gethostbyname for nodes with flaky dns,
20293 - If the user typed in an address that didn't resolve, the server
20297 Changes in version 0.0.2pre24 - 2004-03-03
20299 - Fix an assertion failure in dns.c, where we were trying to dequeue
20300 a pending dns resolve even if it wasn't pending
20301 - Fix a spurious socks5 warning about still trying to write after the
20302 connection is finished.
20303 - Hold certain marked_for_close connections open until they're finished
20304 flushing, rather than losing bytes by closing them too early.
20305 - Correctly report the reason for ending a stream
20306 - Remove some duplicate calls to connection_mark_for_close
20307 - Put switch_id and start_daemon earlier in the boot sequence, so it
20308 will actually try to chdir() to options.DataDirectory
20309 - Make 'make test' exit(1) if a test fails; fix some unit tests
20310 - Make tor fail when you use a config option it doesn't know about,
20311 rather than warn and continue.
20312 - Make --version work
20313 - Bugfixes on the rpm spec file and tor.sh, so it's more up to date
20316 Changes in version 0.0.2pre23 - 2004-02-29
20318 - Print a statement when the first circ is finished, so the user
20319 knows it's working.
20320 - If a relay cell is unrecognized at the end of the circuit,
20321 send back a destroy. (So attacks to mutate cells are more
20323 - New config option 'excludenodes' to avoid certain nodes for circuits.
20324 - When it daemonizes, it chdir's to the DataDirectory rather than "/",
20325 so you can collect coredumps there.
20327 - Fix a bug in tls flushing where sometimes data got wedged and
20328 didn't flush until more data got sent. Hopefully this bug was
20329 a big factor in the random delays we were seeing.
20330 - Make 'connected' cells include the resolved IP, so the client
20331 dns cache actually gets populated.
20332 - Disallow changing from ORPort=0 to ORPort>0 on hup.
20333 - When we time-out on a stream and detach from the circuit, send an
20334 end cell down it first.
20335 - Only warn about an unknown router (in exitnodes, entrynodes,
20336 excludenodes) after we've fetched a directory.
20339 Changes in version 0.0.2pre22 - 2004-02-26
20341 - Servers publish less revealing uname information in descriptors.
20342 - More memory tracking and assertions, to crash more usefully when
20344 - If the default torrc isn't there, just use some default defaults.
20345 Plus provide an internal dirservers file if they don't have one.
20346 - When the user tries to use Tor as an http proxy, give them an http
20347 501 failure explaining that we're a socks proxy.
20348 - Dump a new router.desc on hup, to help confused people who change
20349 their exit policies and then wonder why router.desc doesn't reflect
20351 - Clean up the generic tor.sh init script that we ship with.
20353 - If the exit stream is pending on the resolve, and a destroy arrives,
20354 then the stream wasn't getting removed from the pending list. I
20355 think this was the one causing recent server crashes.
20356 - Use a more robust poll on OSX 10.3, since their poll is flaky.
20357 - When it couldn't resolve any dirservers, it was useless from then on.
20358 Now it reloads the RouterFile (or default dirservers) if it has no
20360 - Move the 'tor' binary back to /usr/local/bin/ -- it turns out
20361 many users don't even *have* a /usr/local/sbin/.
20364 Changes in version 0.0.2pre21 - 2004-02-18
20366 - There's a ChangeLog file that actually reflects the changelog.
20367 - There's a 'torify' wrapper script, with an accompanying
20368 tor-tsocks.conf, that simplifies the process of using tsocks for
20369 tor. It even has a man page.
20370 - The tor binary gets installed to sbin rather than bin now.
20371 - Retry streams where the connected cell hasn't arrived in 15 seconds
20372 - Clean up exit policy handling -- get the default out of the torrc,
20373 so we can update it without forcing each server operator to fix
20375 - Allow imaps and pop3s in default exit policy
20377 - Prevent picking middleman nodes as the last node in the circuit
20380 Changes in version 0.0.2pre20 - 2004-01-30
20382 - We now have a deb package, and it's in debian unstable. Go to
20383 it, apt-getters. :)
20384 - I've split the TotalBandwidth option into BandwidthRate (how many
20385 bytes per second you want to allow, long-term) and
20386 BandwidthBurst (how many bytes you will allow at once before the cap
20387 kicks in). This better token bucket approach lets you, say, set
20388 BandwidthRate to 10KB/s and BandwidthBurst to 10MB, allowing good
20389 performance while not exceeding your monthly bandwidth quota.
20390 - Push out a tls record's worth of data once you've got it, rather
20391 than waiting until you've read everything waiting to be read. This
20392 may improve performance by pipelining better. We'll see.
20393 - Add an AP_CONN_STATE_CONNECTING state, to allow streams to detach
20394 from failed circuits (if they haven't been connected yet) and attach
20396 - Expire old streams that haven't managed to connect. Some day we'll
20397 have them reattach to new circuits instead.
20400 - Fix several memory leaks that were causing servers to become bloated
20402 - Fix a few very rare assert triggers. A few more remain.
20403 - Setuid to User _before_ complaining about running as root.
20406 Changes in version 0.0.2pre19 - 2004-01-07
20408 - Fix deadlock condition in dns farm. We were telling a child to die by
20409 closing the parent's file descriptor to him. But newer children were
20410 inheriting the open file descriptor from the parent, and since they
20411 weren't closing it, the socket never closed, so the child never read
20412 eof, so he never knew to exit. Similarly, dns workers were holding
20413 open other sockets, leading to all sorts of chaos.
20414 - New cleaner daemon() code for forking and backgrounding.
20415 - If you log to a file, it now prints an entry at the top of the
20416 logfile so you know it's working.
20417 - The onionskin challenge length was 30 bytes longer than necessary.
20418 - Started to patch up the spec so it's not quite so out of date.
20421 Changes in version 0.0.2pre18 - 2004-01-02
20423 - Fix endian issues with the 'integrity' field in the relay header.
20424 - Fix a potential bug where connections in state
20425 AP_CONN_STATE_CIRCUIT_WAIT might unexpectedly ask to write.
20428 Changes in version 0.0.2pre17 - 2003-12-30
20430 - Made --debuglogfile (or any second log file, actually) work.
20431 - Resolved an edge case in get_unique_circ_id_by_conn where a smart
20432 adversary could force us into an infinite loop.
20435 - Each onionskin handshake now includes a hash of the computed key,
20436 to prove the server's identity and help perfect forward secrecy.
20437 - Changed cell size from 256 to 512 bytes (working toward compatibility
20439 - Changed cell length to 2 bytes, and moved it to the relay header.
20440 - Implemented end-to-end integrity checking for the payloads of
20442 - Separated streamid from 'recognized' (otherwise circuits will get
20443 messed up when we try to have streams exit from the middle). We
20444 use the integrity-checking to confirm that a cell is addressed to
20446 - Randomize the initial circid and streamid values, so an adversary who
20447 breaks into a node can't learn how many circuits or streams have
20451 Changes in version 0.0.2pre16 - 2003-12-14
20453 - Fixed a bug that made HUP trigger an assert
20454 - Fixed a bug where a circuit that immediately failed wasn't being
20455 counted as a failed circuit in counting retries.
20458 - Now we close the circuit when we get a truncated cell: otherwise we're
20459 open to an anonymity attack where a bad node in the path truncates
20460 the circuit and then we open streams at him.
20461 - Add port ranges to exit policies
20462 - Add a conservative default exit policy
20463 - Warn if you're running tor as root
20464 - on HUP, retry OR connections and close/rebind listeners
20465 - options.EntryNodes: try these nodes first when picking the first node
20466 - options.ExitNodes: if your best choices happen to include any of
20467 your preferred exit nodes, you choose among just those preferred
20469 - options.ExcludedNodes: nodes that are never picked in path building
20472 Changes in version 0.0.2pre15 - 2003-12-03
20473 o Robustness and bugfixes:
20474 - Sometimes clients would cache incorrect DNS resolves, which would
20475 really screw things up.
20476 - An OP that goes offline would slowly leak all its sockets and stop
20478 - A wide variety of bugfixes in exit node selection, exit policy
20479 handling, and processing pending streams when a new circuit is
20481 - Pick nodes for a path only from those the directory says are up
20482 - Choose randomly from all running dirservers, not always the first one
20483 - Increase allowed http header size for directory fetch.
20484 - Stop writing to stderr (if we're daemonized it will be closed).
20485 - Enable -g always, so cores will be more useful to me.
20486 - Switch "-lcrypto -lssl" to "-lssl -lcrypto" for broken distributions.
20489 - Wrote a man page. It lists commonly used options.
20492 - Change default loglevel to warn.
20493 - Make PidFile default to null rather than littering in your CWD.
20494 - OnionRouter config option is now obsolete. Instead it just checks
20496 - Moved to a single unified torrc file for both clients and servers.
20499 Changes in version 0.0.2pre14 - 2003-11-29
20500 o Robustness and bugfixes:
20501 - Force the admin to make the DataDirectory himself
20502 - to get ownership/permissions right
20503 - so clients no longer make a DataDirectory and then never use it
20504 - fix bug where a client who was offline for 45 minutes would never
20505 pull down a directory again
20506 - fix (or at least hide really well) the dns assert bug that was
20507 causing server crashes
20508 - warnings and improved robustness wrt clockskew for certs
20509 - use the native daemon(3) to daemonize, when available
20510 - exit if bind() fails
20511 - exit if neither socksport nor orport is defined
20512 - include our own tor_timegm (Win32 doesn't have its own)
20513 - bugfix for win32 with lots of connections
20514 - fix minor bias in PRNG
20515 - make dirserver more robust to corrupt cached directory
20518 - Wrote the design document (woo)
20520 o Circuit building and exit policies:
20521 - Circuits no longer try to use nodes that the directory has told them
20523 - Exit policies now support bitmasks (18.0.0.0/255.0.0.0) and
20524 bitcounts (18.0.0.0/8).
20525 - Make AP connections standby for a circuit if no suitable circuit
20526 exists, rather than failing
20527 - Circuits choose exit node based on addr/port, exit policies, and
20528 which AP connections are standing by
20529 - Bump min pathlen from 2 to 3
20530 - Relay end cells have a payload to describe why the stream ended.
20531 - If the stream failed because of exit policy, try again with a new
20533 - Clients have a dns cache to remember resolved addresses.
20534 - Notice more quickly when we have no working circuits
20537 - APPort is now called SocksPort
20538 - SocksBindAddress, ORBindAddress, DirBindAddress let you configure
20540 - RecommendedVersions is now a config variable rather than
20541 hardcoded (for dirservers)
20542 - Reloads config on HUP
20543 - Usage info on -h or --help
20544 - If you set User and Group config vars, it'll setu/gid to them.
20547 Changes in version 0.0.2pre13 - 2003-10-19
20548 o General stability:
20549 - SSL_write no longer fails when it returns WANTWRITE and the number
20550 of bytes in the buf has changed by the next SSL_write call.
20551 - Fix segfault fetching directory when network is down
20552 - Fix a variety of minor memory leaks
20553 - Dirservers reload the fingerprints file on HUP, so I don't have
20554 to take down the network when I approve a new router
20555 - Default server config file has explicit Address line to specify fqdn
20558 - Buffers grow and shrink as needed (Cut process size from 20M to 2M)
20559 - Make listener connections not ever alloc bufs
20561 o Autoconf improvements:
20562 - don't clobber an external CFLAGS in ./configure
20563 - Make install now works
20564 - create var/lib/tor on make install
20565 - autocreate a tor.sh initscript to help distribs
20566 - autocreate the torrc and sample-server-torrc with correct paths
20568 o Log files and Daemonizing now work:
20569 - If --DebugLogFile is specified, log to it at -l debug
20570 - If --LogFile is specified, use it instead of commandline
20571 - If --RunAsDaemon is set, tor forks and backgrounds on startup